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 (geoip):
13 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
16 o Minor bugfixes (compilation):
17 - Cause the unit tests to compile correctly on mingw64 versions that
18 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
20 o Minor bugfixes (downloading):
21 - Predict more correctly whether we'll be downloading over HTTP when
22 we determine the maximum length of a URL. This should avoid a
23 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
27 Changes in version 0.2.8.3-alpha - 2016-05-26
28 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
29 the course of the 0.2.8 development cycle. It improves the behavior of
30 directory clients, fixes several crash bugs, fixes a gap in compiler
31 hardening, and allows the full integration test suite to run on
34 o Major bugfixes (security, client, DNS proxy):
35 - Stop a crash that could occur when a client running with DNSPort
36 received a query with multiple address types, and the first
37 address type was not supported. Found and fixed by Scott Dial.
38 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
40 o Major bugfixes (security, compilation):
41 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
42 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
43 cause a compiler warning, thereby making other checks fail, and
44 needlessly disabling compiler-hardening support. Fixes one case of
45 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
47 o Major bugfixes (security, directory authorities):
48 - Fix a crash and out-of-bounds write during authority voting, when
49 the list of relays includes duplicate ed25519 identity keys. Fixes
50 bug 19032; bugfix on 0.2.8.2-alpha.
52 o Major bugfixes (client, bootstrapping):
53 - Check if bootstrap consensus downloads are still needed when the
54 linked connection attaches. This prevents tor making unnecessary
55 begindir-style connections, which are the only directory
56 connections tor clients make since the fix for 18483 was merged.
57 - Fix some edge cases where consensus download connections may not
58 have been closed, even though they were not needed. Related to fix
60 - Make relays retry consensus downloads the correct number of times,
61 rather than the more aggressive client retry count. Fixes part of
63 - Stop downloading consensuses when we have a consensus, even if we
64 don't have all the certificates for it yet. Fixes bug 18809;
65 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
67 o Major bugfixes (directory mirrors):
68 - Decide whether to advertise begindir support in the the same way
69 we decide whether to advertise our DirPort. Allowing these
70 decisions to become out-of-sync led to surprising behavior like
71 advertising begindir support when hibernation made us not
72 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
75 o Major bugfixes (IPv6 bridges, client):
76 - Actually use IPv6 addresses when selecting directory addresses for
77 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
80 o Major bugfixes (key management):
81 - If OpenSSL fails to generate an RSA key, do not retain a dangling
82 pointer to the previous (uninitialized) key value. The impact here
83 should be limited to a difficult-to-trigger crash, if OpenSSL is
84 running an engine that makes key generation failures possible, or
85 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
86 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
89 o Major bugfixes (testing):
90 - Fix a bug that would block 'make test-network-all' on systems where
91 IPv6 packets were lost. Fixes bug 19008; bugfix on tor-0.2.7.3-rc.
92 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
93 bugfix on 0.2.8.1-alpha.
95 o Minor features (clients):
96 - Make clients, onion services, and bridge relays always use an
97 encrypted begindir connection for directory requests. Resolves
98 ticket 18483. Patch by "teor".
100 o Minor features (fallback directory mirrors):
101 - Give each fallback the same weight for client selection; restrict
102 fallbacks to one per operator; report fallback directory detail
103 changes when rebuilding list; add new fallback directory mirrors
104 to the whitelist; update fallback directories based on the latest
105 OnionOO data; and any other minor simplifications and fixes.
106 Closes tasks 17158, 17905, 18749, bug 18689, and fixes part of bug
107 18812 on 0.2.8.1-alpha; patch by "teor".
109 o Minor features (geoip):
110 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
113 o Minor bugfixes (assert, portability):
114 - Fix an assertion failure in memarea.c on systems where "long" is
115 shorter than the size of a pointer. Fixes bug 18716; bugfix
118 o Minor bugfixes (bootstrap):
119 - Consistently use the consensus download schedule for authority
120 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
122 o Minor bugfixes (build):
123 - Remove a pair of redundant AM_CONDITIONAL declarations from
124 configure.ac. Fixes one final case of bug 17744; bugfix
126 - Resolve warnings when building on systems that are concerned with
127 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
129 - When libscrypt.h is found, but no libscrypt library can be linked,
130 treat libscrypt as absent. Fixes bug 19161; bugfix
133 o Minor bugfixes (client):
134 - Turn all TestingClientBootstrap* into non-testing torrc options.
135 This changes simply renames them by removing "Testing" in front of
136 them and they do not require TestingTorNetwork to be enabled
137 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
138 - Make directory node selection more reliable, mainly for IPv6-only
139 clients and clients with few reachable addresses. Fixes bug 18929;
140 bugfix on 0.2.8.1-alpha. Patch by "teor".
142 o Minor bugfixes (controller, microdescriptors):
143 - Make GETINFO dir/status-vote/current/consensus conform to the
144 control specification by returning "551 Could not open cached
145 consensus..." when not caching consensuses. Fixes bug 18920;
146 bugfix on 0.2.2.6-alpha.
148 o Minor bugfixes (crypto, portability):
149 - The SHA3 and SHAKE routines now produce the correct output on Big
150 Endian systems. No code calls either algorithm yet, so this is
151 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
152 - Tor now builds again with the recent OpenSSL 1.1 development
153 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
156 o Minor bugfixes (directories):
157 - When fetching extrainfo documents, compare their SHA256 digests
158 and Ed25519 signing key certificates with the routerinfo that led
159 us to fetch them, rather than with the most recent routerinfo.
160 Otherwise we generate many spurious warnings about mismatches.
161 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
163 o Minor bugfixes (logging):
164 - When we can't generate a signing key because OfflineMasterKey is
165 set, do not imply that we should have been able to load it. Fixes
166 bug 18133; bugfix on 0.2.7.2-alpha.
167 - Stop periodic_event_dispatch() from blasting twelve lines per
168 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
169 - When rejecting a misformed INTRODUCE2 cell, only log at
170 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
172 o Minor bugfixes (pluggable transports):
173 - Avoid reporting a spurious error when we decide that we don't need
174 to terminate a pluggable transport because it has already exited.
175 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
177 o Minor bugfixes (pointer arithmetic):
178 - Fix a bug in memarea_alloc() that could have resulted in remote
179 heap write access, if Tor had ever passed an unchecked size to
180 memarea_alloc(). Fortunately, all the sizes we pass to
181 memarea_alloc() are pre-checked to be less than 128 kilobytes.
182 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
185 o Minor bugfixes (relays):
186 - Consider more config options when relays decide whether to
187 regenerate their descriptor. Fixes more of bug 12538; bugfix
189 - Resolve some edge cases where we might launch an ORPort
190 reachability check even when DisableNetwork is set. Noticed while
191 fixing bug 18616; bugfix on 0.2.3.9-alpha.
193 o Minor bugfixes (statistics):
194 - We now include consensus downloads via IPv6 in our directory-
195 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
197 o Minor bugfixes (testing):
198 - Allow directories in small networks to bootstrap by skipping
199 DirPort checks when the consensus has no exits. Fixes bug 19003;
200 bugfix on 0.2.8.1-alpha. Patch by teor.
201 - Fix a small memory leak that would occur when the
202 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
203 bugfix on 0.2.5.2-alpha.
205 o Minor bugfixes (time handling):
206 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
207 field. Otherwise, our unit tests crash on Windows. Fixes bug
208 18977; bugfix on 0.2.2.25-alpha.
211 - Document the contents of the 'datadir/keys' subdirectory in the
212 manual page. Closes ticket 17621.
213 - Stop recommending use of nicknames to identify relays in our
214 MapAddress documentation. Closes ticket 18312.
217 Changes in version 0.2.8.2-alpha - 2016-03-28
218 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
219 bugs in earlier versions of Tor, including some that prevented
220 authorities using Tor 0.2.7.x from running correctly. IPv6 and
221 directory support should also be much improved.
223 o New system requirements:
224 - Tor no longer supports versions of OpenSSL with a broken
225 implementation of counter mode. (This bug was present in OpenSSL
226 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
227 longer runs with, these versions.
228 - Tor no longer attempts to support platforms where the "time_t"
229 type is unsigned. (To the best of our knowledge, only OpenVMS does
230 this, and Tor has never actually built on OpenVMS.) Closes
232 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
233 later (released in 2008 and 2009 respectively). If you are
234 building Tor from the git repository instead of from the source
235 distribution, and your tools are older than this, you will need to
236 upgrade. Closes ticket 17732.
238 o Major bugfixes (security, pointers):
239 - Avoid a difficult-to-trigger heap corruption attack when extending
240 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
241 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
242 Reported by Guido Vranken.
244 o Major bugfixes (bridges, pluggable transports):
245 - Modify the check for OR connections to private addresses. Allow
246 bridges on private addresses, including pluggable transports that
247 ignore the (potentially private) address in the bridge line. Fixes
248 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
250 o Major bugfixes (compilation):
251 - Repair hardened builds under the clang compiler. Previously, our
252 use of _FORTIFY_SOURCE would conflict with clang's address
253 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
255 o Major bugfixes (crash on shutdown):
256 - Correctly handle detaching circuits from muxes when shutting down.
257 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
258 - Fix an assert-on-exit bug related to counting memory usage in
259 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
261 o Major bugfixes (crash on startup):
262 - Fix a segfault during startup: If a Unix domain socket was
263 configured as listener (such as a ControlSocket or a SocksPort
264 "unix:" socket), and tor was started as root but not configured to
265 switch to another user, tor would segfault while trying to string
266 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
269 o Major bugfixes (dns proxy mode, crash):
270 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
271 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
273 o Major bugfixes (relays, bridge clients):
274 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
275 bridge clients use the address configured in the bridge line.
276 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
279 o Major bugfixes (voting):
280 - Actually enable support for authorities to match routers by their
281 Ed25519 identities. Previously, the code had been written, but
282 some debugging code that had accidentally been left in the
283 codebase made it stay turned off. Fixes bug 17702; bugfix
285 - When collating votes by Ed25519 identities, authorities now
286 include a "NoEdConsensus" flag if the ed25519 value (or lack
287 thereof) for a server does not reflect the majority consensus.
288 Related to bug 17668; bugfix on 0.2.7.2-alpha.
289 - When generating a vote with keypinning disabled, never include two
290 entries for the same ed25519 identity. This bug was causing
291 authorities to generate votes that they could not parse when a
292 router violated key pinning by changing its RSA identity but
293 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
294 18318. Bugfix on 0.2.7.2-alpha.
296 o Minor features (security, win32):
297 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
298 attack. Fixes bug 18123; bugfix on all tor versions. Patch
301 o Minor features (bug-resistance):
302 - Make Tor survive errors involving connections without a
303 corresponding event object. Previously we'd fail with an
304 assertion; now we produce a log message. Related to bug 16248.
306 o Minor features (build):
307 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
308 as having possible IPFW support. Closes ticket 18448. Patch from
311 o Minor features (code hardening):
312 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
313 level code, to harden against accidental failures to NUL-
314 terminate. Part of ticket 17852. Patch from jsturgix. Found
317 o Minor features (crypto):
318 - Validate the hard-coded Diffie-Hellman parameters and ensure that
319 p is a safe prime, and g is a suitable generator. Closes
322 o Minor features (geoip):
323 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
326 o Minor features (hidden service directory):
327 - Streamline relay-side hsdir handling: when relays consider whether
328 to accept an uploaded hidden service descriptor, they no longer
329 check whether they are one of the relays in the network that is
330 "supposed" to handle that descriptor. Implements ticket 18332.
332 o Minor features (IPv6):
333 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
334 to 1, tor prefers IPv6 directory addresses.
335 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
336 avoids using IPv4 for client OR and directory connections.
337 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
338 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
339 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
341 o Minor features (linux seccomp2 sandbox):
342 - Reject attempts to change our Address with "Sandbox 1" enabled.
343 Changing Address with Sandbox turned on would never actually work,
344 but previously it would fail in strange and confusing ways. Found
347 o Minor features (robustness):
348 - Exit immediately with an error message if the code attempts to use
349 Libevent without having initialized it. This should resolve some
350 frequently-made mistakes in our unit tests. Closes ticket 18241.
352 o Minor features (unix domain sockets):
353 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
354 Unix domain sockets without checking the permissions on the parent
355 directory. (Tor checks permissions by default because some
356 operating systems only check permissions on the parent directory.
357 However, some operating systems do look at permissions on the
358 socket, and tor's default check is unneeded.) Closes ticket 18458.
361 o Minor bugfixes (exit policies, security):
362 - Refresh an exit relay's exit policy when interface addresses
363 change. Previously, tor only refreshed the exit policy when the
364 configured external address changed. Fixes bug 18208; bugfix on
365 0.2.7.3-rc. Patch by teor.
367 o Minor bugfixes (security, hidden services):
368 - Prevent hidden services connecting to client-supplied rendezvous
369 addresses that are reserved as internal or multicast. Fixes bug
370 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
372 o Minor bugfixes (build):
373 - Do not link the unit tests against both the testing and non-
374 testing versions of the static libraries. Fixes bug 18490; bugfix
376 - Avoid spurious failures from configure files related to calling
377 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18625; bugfix on
378 0.2.0.1-alpha. Patch from "cypherpunks".
379 - Silence spurious clang-scan warnings in the ed25519_donna code by
380 explicitly initializing some objects. Fixes bug 18384; bugfix on
381 0.2.7.2-alpha. Patch by teor.
383 o Minor bugfixes (client, bootstrap):
384 - Count receipt of new microdescriptors as progress towards
385 bootstrapping. Previously, with EntryNodes set, Tor might not
386 successfully repopulate the guard set on bootstrapping. Fixes bug
387 16825; bugfix on 0.2.3.1-alpha.
389 o Minor bugfixes (code correctness):
390 - Update to the latest version of Trunnel, which tries harder to
391 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
392 by clang address sanitizer. Fixes bug 18373; bugfix
395 o Minor bugfixes (configuration):
396 - Fix a tiny memory leak when parsing a port configuration ending in
397 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
399 o Minor bugfixes (containers):
400 - If we somehow attempt to construct a heap with more than
401 1073741822 elements, avoid an integer overflow when maintaining
402 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
404 o Minor bugfixes (correctness):
405 - Fix a bad memory handling bug that would occur if we had queued a
406 cell on a channel's incoming queue. Fortunately, we can't actually
407 queue a cell like that as our code is constructed today, but it's
408 best to avoid this kind of error, even if there isn't any code
409 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
411 o Minor bugfixes (directory):
412 - When generating a URL for a directory server on an IPv6 address,
413 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
414 on 0.2.3.9-alpha. Patch from Malek.
416 o Minor bugfixes (fallback directory mirrors):
417 - When requesting extrainfo descriptors from a trusted directory
418 server, check whether it is an authority or a fallback directory
419 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
420 0.2.4.7-alpha. Reported by atagar, patch by teor.
422 o Minor bugfixes (hidden service, client):
423 - Handle the case where the user makes several fast consecutive
424 requests to the same .onion address. Previously, the first six
425 requests would each trigger a descriptor fetch, each picking a
426 directory (there are 6 overall) and the seventh one would fail
427 because no directories were left, thereby triggering a close on
428 all current directory connections asking for the hidden service.
429 The solution here is to not close the connections if we have
430 pending directory fetches. Fixes bug 15937; bugfix
433 o Minor bugfixes (hidden service, control port):
434 - Add the onion address to the HS_DESC event for the UPLOADED action
435 both on success or failure. It was previously hardcoded with
436 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
438 o Minor bugfixes (hidden service, directory):
439 - Bridges now refuse "rendezvous2" (hidden service descriptor)
440 publish attempts. Suggested by ticket 18332.
442 o Minor bugfixes (linux seccomp2 sandbox):
443 - Allow the setrlimit syscall, and the prlimit and prlimit64
444 syscalls, which some libc implementations use under the hood.
445 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
446 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
447 enabled and no DNS resolvers configured. This should help TAILS
448 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
449 - Fix the sandbox's interoperability with unix domain sockets under
450 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
452 o Minor bugfixes (logging):
453 - When logging information about an unparsable networkstatus vote or
454 consensus, do not say "vote" when we mean consensus. Fixes bug
455 18368; bugfix on 0.2.0.8-alpha.
456 - Scrub service name in "unrecognized service ID" log messages.
457 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
458 - Downgrade logs and backtraces about IP versions to info-level.
459 Only log backtraces once each time tor runs. Assists in diagnosing
460 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
461 Christian, patch by teor.
463 o Minor bugfixes (memory safety):
464 - Avoid freeing an uninitialized pointer when opening a socket fails
465 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
466 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
468 - Correctly duplicate addresses in get_interface_address6_list().
469 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
470 patch by "cypherpunks".
471 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
473 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
474 18672; bugfix on 0.2.5.1-alpha.
476 o Minor bugfixes (private directory):
477 - Prevent a race condition when creating private directories. Fixes
478 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
479 Patch from jsturgix. Found with Flawfinder.
481 o Minor bugfixes (test networks, IPv6):
482 - Allow internal IPv6 addresses in descriptors in test networks.
483 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
486 o Minor bugfixes (testing):
487 - We no longer disable assertions in the unit tests when coverage is
488 enabled. Instead, we require you to say --disable-asserts-in-tests
489 to the configure script if you need assertions disabled in the
490 unit tests (for example, if you want to perform branch coverage).
491 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
493 o Minor bugfixes (time parsing):
494 - Avoid overflow in tor_timegm when parsing dates in and after 2038
495 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
496 0.0.2pre14. Patch by teor.
498 o Minor bugfixes (tor-gencert):
499 - Correctly handle the case where an authority operator enters a
500 passphrase but sends an EOF before sending a newline. Fixes bug
501 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
503 o Code simplification and refactoring:
504 - Quote all the string interpolations in configure.ac -- even those
505 which we are pretty sure can't contain spaces. Closes ticket
506 17744. Patch from zerosion.
507 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
508 inplace, so there's no need to have a separate implementation for
509 the non-inplace code. Closes ticket 18258. Patch from Malek.
510 - Simplify return types for some crypto functions that can't
511 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
514 - Change build messages to refer to "Fedora" instead of "Fedora
515 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
516 Patches from "icanhasaccount" and "cypherpunks".
519 - We no longer maintain an internal freelist in memarea.c.
520 Allocators should be good enough to make this code unnecessary,
521 and it's doubtful that it ever had any performance benefit.
524 - Fix several warnings from clang's address sanitizer produced in
526 - Treat backtrace test failures as expected on FreeBSD until we
527 solve bug 17808. Closes ticket 18204.
530 Changes in version 0.2.8.1-alpha - 2016-02-04
531 Tor 0.2.8.1-alpha is the first alpha release in its series. It
532 includes numerous small features and bugfixes against previous Tor
533 versions, and numerous small infrastructure improvements. The most
534 notable features are a set of improvements to the directory subsystem.
536 o Major features (security, Linux):
537 - When Tor starts as root on Linux and is told to switch user ID, it
538 can now retain the capability to bind to low ports. By default,
539 Tor will do this only when it's switching user ID and some low
540 ports have been configured. You can change this behavior with the
541 new option KeepBindCapabilities. Closes ticket 8195.
543 o Major features (directory system):
544 - When bootstrapping multiple consensus downloads at a time, use the
545 first one that starts downloading, and close the rest. This
546 reduces failures when authorities or fallback directories are slow
547 or down. Together with the code for feature 15775, this feature
548 should reduces failures due to fallback churn. Implements ticket
549 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
550 "mikeperry" and "teor".
551 - Include a trial list of default fallback directories, based on an
552 opt-in survey of suitable relays. Doing this should make clients
553 bootstrap more quickly and reliably, and reduce the load on the
554 directory authorities. Closes ticket 15775. Patch by "teor".
555 Candidates identified using an OnionOO script by "weasel", "teor",
556 "gsathya", and "karsten".
557 - Previously only relays that explicitly opened a directory port
558 (DirPort) accepted directory requests from clients. Now all
559 relays, with and without a DirPort, accept and serve tunneled
560 directory requests that they receive through their ORPort. You can
561 disable this behavior using the new DirCache option. Closes
565 - Update the V3 identity key for the dannenberg directory authority:
566 it was changed on 18 November 2015. Closes task 17906. Patch
569 o Minor features (security, clock):
570 - Warn when the system clock appears to move back in time (when the
571 state file was last written in the future). Tor doesn't know that
572 consensuses have expired if the clock is in the past. Patch by
573 "teor". Implements ticket 17188.
575 o Minor features (security, exit policies):
576 - ExitPolicyRejectPrivate now rejects more private addresses by
577 default. Specifically, it now rejects the relay's outbound bind
578 addresses (if configured), and the relay's configured port
579 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
580 0.2.0.11-alpha. Patch by "teor".
582 o Minor features (security, memory erasure):
583 - Set the unused entries in a smartlist to NULL. This helped catch
584 a (harmless) bug, and shouldn't affect performance too much.
585 Implements ticket 17026.
586 - Use SecureMemoryWipe() function to securely clean memory on
587 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
588 Implements feature 17986.
589 - Use explicit_bzero or memset_s when present. Previously, we'd use
590 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
591 from <logan@hackers.mu> and <selven@hackers.mu>.
592 - Make memwipe() do nothing when passed a NULL pointer or buffer of
593 zero size. Check size argument to memwipe() for underflow. Fixes
594 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
597 o Minor features (security, RNG):
598 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
599 positively are not allowed to fail. Previously we depended on
600 internal details of OpenSSL's behavior. Closes ticket 17686.
601 - Never use the system entropy output directly for anything besides
602 seeding the PRNG. When we want to generate important keys, instead
603 of using system entropy directly, we now hash it with the PRNG
604 stream. This may help resist certain attacks based on broken OS
605 entropy implementations. Closes part of ticket 17694.
606 - Use modern system calls (like getentropy() or getrandom()) to
607 generate strong entropy on platforms that have them. Closes
610 o Minor features (accounting):
611 - Added two modes to the AccountingRule option: One for limiting
612 only the number of bytes sent ("AccountingRule out"), and one for
613 limiting only the number of bytes received ("AccountingRule in").
614 Closes ticket 15989; patch from "unixninja92".
616 o Minor features (build):
617 - Since our build process now uses "make distcheck", we no longer
618 force "make dist" to depend on "make check". Closes ticket 17893;
619 patch from "cypherpunks."
620 - Tor now builds successfully with the recent OpenSSL 1.1
621 development branch, and with the latest LibreSSL. Closes tickets
622 17549, 17921, and 17984.
624 o Minor features (controller):
625 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
626 tickets 16774 and 17817. Patch by George Tankersley.
627 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
628 service descriptor from a service's local hidden service
629 descriptor cache. Closes ticket 14846.
630 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
631 controllers can examine the the reject rules added by
632 ExitPolicyRejectPrivate. This makes it easier for stem to display
635 o Minor features (crypto):
636 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
638 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
639 - When allocating a digest state object, allocate no more space than
640 we actually need. Previously, we would allocate as much space as
641 the state for the largest algorithm would need. This change saves
642 up to 672 bytes per circuit. Closes ticket 17796.
643 - Improve performance when hashing non-multiple of 8 sized buffers,
644 based on Andrew Moon's public domain SipHash-2-4 implementation.
645 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
647 o Minor features (directory downloads):
648 - Wait for busy authorities and fallback directories to become non-
649 busy when bootstrapping. (A similar change was made in 6c443e987d
650 for directory caches chosen from the consensus.) Closes ticket
651 17864; patch by "teor".
652 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
653 directory mirrors. The default is 1; set it to 0 to disable
654 fallbacks. Implements ticket 17576. Patch by "teor".
656 o Minor features (geoip):
657 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
660 o Minor features (IPv6):
661 - Add an argument 'ipv6=address:orport' to the DirAuthority and
662 FallbackDir torrc options, to specify an IPv6 address for an
663 authority or fallback directory. Add hard-coded ipv6 addresses for
664 directory authorities that have them. Closes ticket 17327; patch
665 from Nick Mathewson and "teor".
666 - Add address policy assume_action support for IPv6 addresses.
667 - Limit IPv6 mask bits to 128.
668 - Warn when comparing against an AF_UNSPEC address in a policy, it's
669 almost always a bug. Closes ticket 17863; patch by "teor".
670 - Allow users to configure directory authorities and fallback
671 directory servers with IPv6 addresses and ORPorts. Resolves
673 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
674 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
675 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
676 17638; bugfix on 0.0.2pre8. Patch by "teor".
678 o Minor features (logging):
679 - When logging to syslog, allow a tag to be added to the syslog
680 identity (the string prepended to every log message). The tag can
681 be configured with SyslogIdentityTag and defaults to none. Setting
682 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
685 o Minor features (portability):
686 - Use timingsafe_memcmp() where available. Closes ticket 17944;
687 patch from <logan@hackers.mu>.
689 o Minor features (relay, address discovery):
690 - Add a family argument to get_interface_addresses_raw() and
691 subfunctions to make network interface address interogation more
692 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
693 types of interfaces from the operating system. Resolves
695 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
696 fails to enumerate interface addresses using the platform-specific
697 API, have it rely on the UDP socket fallback technique to try and
698 find out what IP addresses (both IPv4 and IPv6) our machine has.
699 Resolves ticket 17951.
701 o Minor features (replay cache):
702 - The replay cache now uses SHA256 instead of SHA1. Implements
703 feature 8961. Patch by "teor", issue reported by "rransom".
705 o Minor features (unix file permissions):
706 - Defer creation of Unix sockets until after setuid. This avoids
707 needing CAP_CHOWN and CAP_FOWNER when using systemd's
708 CapabilityBoundingSet, or chown and fowner when using SELinux.
709 Implements part of ticket 17562. Patch from Jamie Nguyen.
710 - If any directory created by Tor is marked as group readable, the
711 filesystem group is allowed to be either the default GID or the
712 root user. Allowing root to read the DataDirectory prevents the
713 need for CAP_READ_SEARCH when using systemd's
714 CapabilityBoundingSet, or dac_read_search when using SELinux.
715 Implements part of ticket 17562. Patch from Jamie Nguyen.
716 - Introduce a new DataDirectoryGroupReadable option. If it is set to
717 1, the DataDirectory will be made readable by the default GID.
718 Implements part of ticket 17562. Patch from Jamie Nguyen.
720 o Minor bugfixes (accounting):
721 - The max bandwidth when using 'AccountRule sum' is now correctly
722 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
725 o Minor bugfixes (code correctness):
726 - When closing an entry connection, generate a warning if we should
727 have sent an end cell for it but we haven't. Fixes bug 17876;
728 bugfix on 0.2.3.2-alpha.
729 - Assert that allocated memory held by the reputation code is freed
730 according to its internal counters. Fixes bug 17753; bugfix
732 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
735 o Minor bugfixes (compilation):
736 - Mark all object files that include micro-revision.i as depending
737 on it, so as to make parallel builds more reliable. Fixes bug
738 17826; bugfix on 0.2.5.1-alpha.
739 - Don't try to use the pthread_condattr_setclock() function unless
740 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
741 17819; bugfix on 0.2.6.3-alpha.
742 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
744 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
745 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
746 - Fix search for libevent libraries on OpenBSD (and other systems
747 that install libevent 1 and libevent 2 in parallel). Fixes bug
748 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
749 - Isolate environment variables meant for tests from the rest of the
750 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
751 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
753 - Remove config.log only from make distclean, not from make clean.
754 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
756 o Minor bugfixes (crypto):
757 - Check the return value of HMAC() and assert on failure. Fixes bug
758 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
760 o Minor bugfixes (fallback directories):
761 - Mark fallbacks as "too busy" when they return a 503 response,
762 rather than just marking authorities. Fixes bug 17572; bugfix on
763 0.2.4.7-alpha. Patch by "teor".
765 o Minor bugfixes (IPv6):
766 - Update the limits in max_dl_per_request for IPv6 address length.
767 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
769 o Minor bugfixes (linux seccomp2 sandbox):
770 - Fix a crash when using offline master ed25519 keys with the Linux
771 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
773 o Minor bugfixes (logging):
774 - In log messages that include a function name, use __FUNCTION__
775 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
776 with clang __PRETTY_FUNCTION__ has extra information we don't
777 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
779 - Remove needless quotes from a log message about unparseable
780 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
782 o Minor bugfixes (portability):
783 - Remove an #endif from configure.ac so that we correctly detect the
784 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
787 o Minor bugfixes (relays):
788 - Check that both the ORPort and DirPort (if present) are reachable
789 before publishing a relay descriptor. Otherwise, relays publish a
790 descriptor with DirPort 0 when the DirPort reachability test takes
791 longer than the ORPort reachability test. Fixes bug 18050; bugfix
792 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
794 o Minor bugfixes (relays, hidden services):
795 - Refuse connection requests to private OR addresses unless
796 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
797 then refuse to send any cells to a private address. Fixes bugs
798 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
800 o Minor bugfixes (safe logging):
801 - When logging a malformed hostname received through socks4, scrub
802 it if SafeLogging says we should. Fixes bug 17419; bugfix
805 o Minor bugfixes (statistics code):
806 - Consistently check for overflow in round_*_to_next_multiple_of
807 functions, and add unit tests with additional and maximal values.
808 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
809 - Handle edge cases in the laplace functions: avoid division by
810 zero, avoid taking the log of zero, and silence clang type
811 conversion warnings using round and trunc. Add unit tests for edge
812 cases with maximal values. Fixes part of bug 13192; bugfix
815 o Minor bugfixes (testing):
816 - The test for log_heartbeat was incorrectly failing in timezones
817 with non-integer offsets. Instead of comparing the end of the time
818 string against a constant, compare it to the output of
819 format_local_iso_time when given the correct input. Fixes bug
820 18039; bugfix on 0.2.5.4-alpha.
821 - Make unit tests pass on IPv6-only systems, and systems without
822 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
823 bugfix on 0.2.7.3-rc. Patch by "teor".
824 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
826 - Check the full results of SHA256 and SHA512 digests in the unit
827 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
829 o Code simplification and refactoring:
830 - Move logging of redundant policy entries in
831 policies_parse_exit_policy_internal into its own function. Closes
832 ticket 17608; patch from "juce".
833 - Extract the more complicated parts of circuit_mark_for_close()
834 into a new function that we run periodically before circuits are
835 freed. This change removes more than half of the functions
836 currently in the "blob". Closes ticket 17218.
837 - Clean up a little duplicated code in
838 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
840 - Decouple the list of streams waiting to be attached to circuits
841 from the overall connection list. This change makes it possible to
842 attach streams quickly while simplifying Tor's callgraph and
843 avoiding O(N) scans of the entire connection list. Closes
845 - When a direct directory request fails immediately on launch,
846 instead of relaunching that request from inside the code that
847 launches it, instead mark the connection for teardown. This change
848 simplifies Tor's callback and prevents the directory-request
849 launching code from invoking itself recursively. Closes
851 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
852 use them. Closes ticket 17926.
855 - Add a description of the correct use of the '--keygen' command-
856 line option. Closes ticket 17583; based on text by 's7r'.
857 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
858 - Explain actual minima for BandwidthRate. Closes ticket 16382.
859 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
860 - Mention torspec URL in the manpage and point the reader to it
861 whenever we mention a document that belongs in torspce. Fixes
865 - Remove client-side support for connecting to Tor relays running
866 versions of Tor before 0.2.3.6-alpha. These relays didn't support
867 the v3 TLS handshake protocol, and are no longer allowed on the
868 Tor network. Implements the client side of ticket 11150. Based on
869 patches by Tom van der Woerdt.
872 - Add unit tests to check for common RNG failure modes, such as
873 returning all zeroes, identical values, or incrementing values
874 (OpenSSL's rand_predictable feature). Patch by "teor".
875 - Log more information when the backtrace tests fail. Closes ticket
876 17892. Patch from "cypherpunks."
877 - Always test both ed25519 backends, so that we can be sure that our
878 batch-open replacement code works. Part of ticket 16794.
879 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
880 portion of ticket 16831.
881 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
882 util_format.c, directory.c, and options_validate.c. Closes tickets
883 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
885 - Unit tests for directory_handle_command_get. Closes ticket 17004.
886 Patch from Reinaldo de Souza Jr.
889 Changes in version 0.2.7.6 - 2015-12-10
890 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
891 well as a minor bug in hidden service reliability.
893 o Major bugfixes (guard selection):
894 - Actually look at the Guard flag when selecting a new directory
895 guard. When we implemented the directory guard design, we
896 accidentally started treating all relays as if they have the Guard
897 flag during guard selection, leading to weaker anonymity and worse
898 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
901 o Minor features (geoip):
902 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
905 o Minor bugfixes (compilation):
906 - When checking for net/pfvar.h, include netinet/in.h if possible.
907 This fixes transparent proxy detection on OpenBSD. Fixes bug
908 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
909 - Fix a compilation warning with Clang 3.6: Do not check the
910 presence of an address which can never be NULL. Fixes bug 17781.
912 o Minor bugfixes (correctness):
913 - When displaying an IPv6 exit policy, include the mask bits
914 correctly even when the number is greater than 31. Fixes bug
915 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
916 - The wrong list was used when looking up expired intro points in a
917 rend service object, causing what we think could be reachability
918 issues for hidden services, and triggering a BUG log. Fixes bug
919 16702; bugfix on 0.2.7.2-alpha.
920 - Fix undefined behavior in the tor_cert_checksig function. Fixes
921 bug 17722; bugfix on 0.2.7.2-alpha.
924 Changes in version 0.2.7.5 - 2015-11-20
925 The Tor 0.2.7 release series is dedicated to the memory of Tor user
926 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
927 tirelessly to advocate human rights regardless of national borders,
928 and oppose the encroachments of mass surveillance. He opposed national
929 exceptionalism, he brought clarity to legal and policy debates, he
930 understood and predicted the impact of mass surveillance on the world,
931 and he laid the groundwork for resisting it. While serving on the Tor
932 Project's board of directors, he brought us his uncompromising focus
933 on technical excellence in the service of humankind. Caspar was an
934 inimitable force for good and a wonderful friend. He was kind,
935 humorous, generous, gallant, and believed we should protect one
936 another without exception. We honor him here for his ideals, his
937 efforts, and his accomplishments. Please honor his memory with works
938 that would make him proud.
940 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
942 The 0.2.7 series adds a more secure identity key type for relays,
943 improves cryptography performance, resolves several longstanding
944 hidden-service performance issues, improves controller support for
945 hidden services, and includes small bugfixes and performance
946 improvements throughout the program. This release series also includes
947 more tests than before, and significant simplifications to which parts
948 of Tor invoke which others.
950 (This release contains no code changes since 0.2.7.4-rc.)
953 Changes in version 0.2.7.4-rc - 2015-10-21
954 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
955 fixes some important memory leaks, and a scary-looking (but mostly
956 harmless in practice) invalid-read bug. It also has a few small
957 bugfixes, notably fixes for compilation and portability on different
958 platforms. If no further significant bounds are found, the next
959 release will the the official stable release.
961 o Major bugfixes (security, correctness):
962 - Fix an error that could cause us to read 4 bytes before the
963 beginning of an openssl string. This bug could be used to cause
964 Tor to crash on systems with unusual malloc implementations, or
965 systems with unusual hardening installed. Fixes bug 17404; bugfix
968 o Major bugfixes (correctness):
969 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
970 bug 17401; bugfix on 0.2.7.3-rc.
972 o Major bugfixes (memory leaks):
973 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
974 17398; bugfix on 0.2.6.1-alpha.
975 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
976 17402; bugfix on 0.2.7.3-rc.
977 - Fix a memory leak when reading an expired signing key from disk.
978 Fixes bug 17403; bugfix on 0.2.7.2-rc.
980 o Minor features (geoIP):
981 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
984 o Minor bugfixes (compilation):
985 - Repair compilation with the most recent (unreleased, alpha)
986 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
987 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
988 17251; bugfix on 0.2.7.2-alpha.
989 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
990 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
992 o Minor bugfixes (portability):
993 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
994 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
997 o Minor bugfixes (sandbox):
998 - Add the "hidserv-stats" filename to our sandbox filter for the
999 HiddenServiceStatistics option to work properly. Fixes bug 17354;
1000 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
1002 o Minor bugfixes (testing):
1003 - Add unit tests for get_interface_address* failure cases. Fixes bug
1004 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
1005 - Fix breakage when running 'make check' with BSD make. Fixes bug
1006 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
1007 - Make the get_ifaddrs_* unit tests more tolerant of different
1008 network configurations. (Don't assume every test box has an IPv4
1009 address, and don't assume every test box has a non-localhost
1010 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
1011 - Skip backtrace tests when backtrace support is not compiled in.
1012 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
1016 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
1017 - Note that HiddenServicePorts can take a unix domain socket. Closes
1021 Changes in version 0.2.7.3-rc - 2015-09-25
1022 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
1023 contains numerous usability fixes for Ed25519 keys, safeguards against
1024 several misconfiguration problems, significant simplifications to
1025 Tor's callgraph, and numerous bugfixes and small features.
1027 This is the most tested release of Tor to date. The unit tests cover
1028 39.40% of the code, and the integration tests (accessible with "make
1029 test-full-online", requiring stem and chutney and a network
1030 connection) raise the coverage to 64.49%.
1032 o Major features (security, hidden services):
1033 - Hidden services, if using the EntryNodes option, are required to
1034 use more than one EntryNode, in order to avoid a guard discovery
1035 attack. (This would only affect people who had configured hidden
1036 services and manually specified the EntryNodes option with a
1037 single entry-node. The impact was that it would be easy to
1038 remotely identify the guard node used by such a hidden service.
1039 See ticket for more information.) Fixes ticket 14917.
1041 o Major features (Ed25519 keys, keypinning):
1042 - The key-pinning option on directory authorities is now advisory-
1043 only by default. In a future version, or when the AuthDirPinKeys
1044 option is set, pins are enforced again. Disabling key-pinning
1045 seemed like a good idea so that we can survive the fallout of any
1046 usability problems associated with Ed25519 keys. Closes
1049 o Major features (Ed25519 performance):
1050 - Improve the speed of Ed25519 operations and Curve25519 keypair
1051 generation when built targeting 32 bit x86 platforms with SSE2
1052 available. Implements ticket 16535.
1053 - Improve the runtime speed of Ed25519 signature verification by
1054 using Ed25519-donna's batch verification support. Implements
1057 o Major features (performance testing):
1058 - The test-network.sh script now supports performance testing.
1059 Requires corresponding chutney performance testing changes. Patch
1060 by "teor". Closes ticket 14175.
1062 o Major features (relay, Ed25519):
1063 - Significant usability improvements for Ed25519 key management. Log
1064 messages are better, and the code can recover from far more
1065 failure conditions. Thanks to "s7r" for reporting and diagnosing
1067 - Add a new OfflineMasterKey option to tell Tor never to try loading
1068 or generating a secret Ed25519 identity key. You can use this in
1069 combination with tor --keygen to manage offline and/or encrypted
1070 Ed25519 keys. Implements ticket 16944.
1071 - Add a --newpass option to allow changing or removing the
1072 passphrase of an encrypted key with tor --keygen. Implements part
1074 - On receiving a HUP signal, check to see whether the Ed25519
1075 signing key has changed, and reload it if so. Closes ticket 16790.
1077 o Major bugfixes (relay, Ed25519):
1078 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
1079 0.2.7.2-alpha. Reported by "s7r".
1080 - Improve handling of expired signing keys with offline master keys.
1081 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
1083 o Minor features (client-side privacy):
1084 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
1085 lifespan when IsolateSOCKSAuth and streams with SOCKS
1086 authentication are attached to the circuit. This allows
1087 applications like TorBrowser to manage circuit lifetime on their
1088 own. Implements feature 15482.
1089 - When logging malformed hostnames from SOCKS5 requests, respect
1090 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
1092 o Minor features (compilation):
1093 - Give a warning as early as possible when trying to build with an
1094 unsupported OpenSSL version. Closes ticket 16901.
1095 - Fail during configure if we're trying to build against an OpenSSL
1096 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
1097 which started requiring ECC.
1099 o Minor features (geoip):
1100 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
1103 o Minor features (hidden services):
1104 - Relays need to have the Fast flag to get the HSDir flag. As this
1105 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
1106 drop. This change should make some attacks against the hidden
1107 service directory system harder. Fixes ticket 15963.
1108 - Turn on hidden service statistics collection by setting the torrc
1109 option HiddenServiceStatistics to "1" by default. (This keeps
1110 track only of the fraction of traffic used by hidden services, and
1111 the total number of hidden services in existence.) Closes
1113 - Client now uses an introduction point failure cache to know when
1114 to fetch or keep a descriptor in their cache. Previously, failures
1115 were recorded implicitly, but not explicitly remembered. Closes
1118 o Minor features (testing, authorities, documentation):
1119 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
1120 explicitly manage consensus flags in testing networks. Patch by
1121 "robgjansen", modified by "teor". Implements part of ticket 14882.
1123 o Minor bugfixes (security, exit policies):
1124 - ExitPolicyRejectPrivate now also rejects the relay's published
1125 IPv6 address (if any), and any publicly routable IPv4 or IPv6
1126 addresses on any local interfaces. ticket 17027. Patch by "teor".
1127 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
1129 o Minor bug fixes (torrc exit policies):
1130 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
1131 produce IPv6 wildcard addresses. Previously they would produce
1132 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
1133 of bug 16069; bugfix on 0.2.4.7-alpha.
1134 - When parsing torrc ExitPolicies, we now warn for a number of cases
1135 where the user's intent is likely to differ from Tor's actual
1136 behavior. These include: using an IPv4 address with an accept6 or
1137 reject6 line; using "private" on an accept6 or reject6 line; and
1138 including any ExitPolicy lines after accept *:* or reject *:*.
1139 Related to ticket 16069.
1140 - When parsing torrc ExitPolicies, we now issue an info-level
1141 message when expanding an "accept/reject *" line to include both
1142 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
1143 - In each instance above, usage advice is provided to avoid the
1144 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
1145 16069; bugfix on 0.2.4.7-alpha.
1147 o Minor bugfixes (authority):
1148 - Don't assign "HSDir" to a router if it isn't Valid and Running.
1149 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
1150 - Downgrade log messages about Ed25519 key issues if they are in old
1151 cached router descriptors. Fixes part of bug 16286; bugfix
1153 - When we find an Ed25519 key issue in a cached descriptor, stop
1154 saying the descriptor was just "uploaded". Fixes another part of
1155 bug 16286; bugfix on 0.2.7.2-alpha.
1157 o Minor bugfixes (control port):
1158 - Repair a warning and a spurious result when getting the maximum
1159 number of file descriptors from the controller. Fixes bug 16697;
1160 bugfix on 0.2.7.2-alpha.
1162 o Minor bugfixes (correctness):
1163 - When calling channel_free_list(), avoid calling smartlist_remove()
1164 while inside a FOREACH loop. This partially reverts commit
1165 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
1166 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
1168 o Minor bugfixes (documentation):
1169 - Advise users on how to configure separate IPv4 and IPv6 exit
1170 policies in the manpage and sample torrcs. Related to ticket 16069.
1171 - Fix the usage message of tor-resolve(1) so that it no longer lists
1172 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
1173 - Fix an error in the manual page and comments for
1174 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
1175 required "ORPort connectivity". While this is true, it is in no
1176 way unique to the HSDir flag. Of all the flags, only HSDirs need a
1177 DirPort configured in order for the authorities to assign that
1178 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
1181 o Minor bugfixes (Ed25519):
1182 - Fix a memory leak when reading router descriptors with expired
1183 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
1185 o Minor bugfixes (linux seccomp2 sandbox):
1186 - Allow bridge authorities to run correctly under the seccomp2
1187 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
1188 - Allow routers with ed25519 keys to run correctly under the
1189 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
1191 o Minor bugfixes (open file limit):
1192 - Fix set_max_file_descriptors() to set by default the max open file
1193 limit to the current limit when setrlimit() fails. Fixes bug
1194 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
1196 o Minor bugfixes (portability):
1197 - Try harder to normalize the exit status of the Tor process to the
1198 standard-provided range. Fixes bug 16975; bugfix on every version
1200 - Check correctly for Windows socket errors in the workqueue
1201 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
1202 - Fix the behavior of crypto_rand_time_range() when told to consider
1203 times before 1970. (These times were possible when running in a
1204 simulated network environment where time()'s output starts at
1205 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
1206 - Restore correct operation of TLS client-cipher detection on
1207 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
1209 o Minor bugfixes (relay):
1210 - Ensure that worker threads actually exit when a fatal error or
1211 shutdown is indicated. This fix doesn't currently affect the
1212 behavior of Tor, because Tor workers never indicates fatal error
1213 or shutdown except in the unit tests. Fixes bug 16868; bugfix
1215 - Unblock threads before releasing the work queue mutex to ensure
1216 predictable scheduling behavior. Fixes bug 16644; bugfix
1219 o Code simplification and refactoring:
1220 - Change the function that's called when we need to retry all
1221 downloads so that it only reschedules the downloads to happen
1222 immediately, rather than launching them all at once itself. This
1223 further simplifies Tor's callgraph.
1224 - Move some format-parsing functions out of crypto.c and
1225 crypto_curve25519.c into crypto_format.c and/or util_format.c.
1226 - Move the client-only parts of init_keys() into a separate
1227 function. Closes ticket 16763.
1228 - Simplify the microdesc_free() implementation so that it no longer
1229 appears (to code analysis tools) to potentially invoke a huge
1230 suite of other microdesc functions.
1231 - Simply the control graph further by deferring the inner body of
1232 directory_all_unreachable() into a callback. Closes ticket 16762.
1233 - Treat the loss of an owning controller as equivalent to a SIGTERM
1234 signal. This removes a tiny amount of duplicated code, and
1235 simplifies our callgraph. Closes ticket 16788.
1236 - When generating an event to send to the controller, we no longer
1237 put the event over the network immediately. Instead, we queue
1238 these events, and use a Libevent callback to deliver them. This
1239 change simplifies Tor's callgraph by reducing the number of
1240 functions from which all other Tor functions are reachable. Closes
1242 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
1243 that try to scan or compile every file on Unix won't decide that
1245 - Remove the unused "nulterminate" argument from buf_pullup().
1248 - Recommend a 40 GB example AccountingMax in torrc.sample rather
1249 than a 4 GB max. Closes ticket 16742.
1250 - Include the TUNING document in our source tarball. It is referred
1251 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
1255 - The internal pure-C tor-fw-helper tool is now removed from the Tor
1256 distribution, in favor of the pure-Go clone available from
1257 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
1258 used by the C tor-fw-helper are not, in our opinion, very
1259 confidence- inspiring in their secure-programming techniques.
1260 Closes ticket 13338.
1261 - Remove the code that would try to aggressively flush controller
1262 connections while writing to them. This code was introduced in
1263 0.1.2.7-alpha, in order to keep output buffers from exceeding
1264 their limits. But there is no longer a maximum output buffer size,
1265 and flushing data in this way caused some undesirable recursions
1266 in our call graph. Closes ticket 16480.
1269 - Make "bridges+hs" the default test network. This tests almost all
1270 tor functionality during make test-network, while allowing tests
1271 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
1272 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
1273 (chutney). Patches by "teor".
1274 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
1275 by-side in the same parent directory. Closes ticket 16903. Patch
1277 - Use environment variables rather than autoconf substitutions to
1278 send variables from the build system to the test scripts. This
1279 change should be easier to maintain, and cause 'make distcheck' to
1280 work better than before. Fixes bug 17148.
1281 - Add a new set of callgraph analysis scripts that use clang to
1282 produce a list of which Tor functions are reachable from which
1283 other Tor functions. We're planning to use these to help simplify
1284 our code structure by identifying illogical dependencies.
1285 - Add new 'test-full' and 'test-full-online' targets to run all
1286 tests, including integration tests with stem and chutney.
1287 - Make the test-workqueue test work on Windows by initializing the
1288 network before we begin.
1289 - New make target (make test-network-all) to run multiple applicable
1290 chutney test cases. Patch from Teor; closes 16953.
1291 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
1292 functions in dns.c. Implements a portion of ticket 16831.
1293 - When building Tor with testing coverage enabled, run Chutney tests
1294 (if any) using the 'tor-cov' coverage binary.
1295 - When running test-network or test-stem, check for the absence of
1296 stem/chutney before doing any build operations.
1299 Changes in version 0.2.7.2-alpha - 2015-07-27
1300 This, the second alpha in the Tor 0.2.7 series, has a number of new
1301 features, including a way to manually pick the number of introduction
1302 points for hidden services, and the much stronger Ed25519 signing key
1303 algorithm for regular Tor relays (including support for encrypted
1304 offline identity keys in the new algorithm).
1306 Support for Ed25519 on relays is currently limited to signing router
1307 descriptors; later alphas in this series will extend Ed25519 key
1308 support to more parts of the Tor protocol.
1310 o Major features (Ed25519 identity keys, Proposal 220):
1311 - All relays now maintain a stronger identity key, using the Ed25519
1312 elliptic curve signature format. This master key is designed so
1313 that it can be kept offline. Relays also generate an online
1314 signing key, and a set of other Ed25519 keys and certificates.
1315 These are all automatically regenerated and rotated as needed.
1316 Implements part of ticket 12498.
1317 - Directory authorities now vote on Ed25519 identity keys along with
1318 RSA1024 keys. Implements part of ticket 12498.
1319 - Directory authorities track which Ed25519 identity keys have been
1320 used with which RSA1024 identity keys, and do not allow them to
1321 vary freely. Implements part of ticket 12498.
1322 - Microdescriptors now include Ed25519 identity keys. Implements
1323 part of ticket 12498.
1324 - Add support for offline encrypted Ed25519 master keys. To use this
1325 feature on your tor relay, run "tor --keygen" to make a new master
1326 key (or to make a new signing key if you already have a master
1327 key). Closes ticket 13642.
1329 o Major features (Hidden services):
1330 - Add the torrc option HiddenServiceNumIntroductionPoints, to
1331 specify a fixed number of introduction points. Its maximum value
1332 is 10 and default is 3. Using this option can increase a hidden
1333 service's reliability under load, at the cost of making it more
1334 visible that the hidden service is facing extra load. Closes
1336 - Remove the adaptive algorithm for choosing the number of
1337 introduction points, which used to change the number of
1338 introduction points (poorly) depending on the number of
1339 connections the HS sees. Closes ticket 4862.
1341 o Major features (onion key cross-certification):
1342 - Relay descriptors now include signatures of their own identity
1343 keys, made using the TAP and ntor onion keys. These signatures
1344 allow relays to prove ownership of their own onion keys. Because
1345 of this change, microdescriptors will no longer need to include
1346 RSA identity keys. Implements proposal 228; closes ticket 12499.
1348 o Major features (performance):
1349 - Improve the runtime speed of Ed25519 operations by using the
1350 public-domain Ed25519-donna by Andrew M. ("floodyberry").
1351 Implements ticket 16467.
1352 - Improve the runtime speed of the ntor handshake by using an
1353 optimized curve25519 basepoint scalarmult implementation from the
1354 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
1355 ideas by Adam Langley. Implements ticket 9663.
1357 o Major bugfixes (client-side privacy, also in 0.2.6.9):
1358 - Properly separate out each SOCKSPort when applying stream
1359 isolation. The error occurred because each port's session group
1360 was being overwritten by a default value when the listener
1361 connection was initialized. Fixes bug 16247; bugfix on
1362 0.2.6.3-alpha. Patch by "jojelino".
1364 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
1365 - Stop refusing to store updated hidden service descriptors on a
1366 client. This reverts commit 9407040c59218 (which indeed fixed bug
1367 14219, but introduced a major hidden service reachability
1368 regression detailed in bug 16381). This is a temporary fix since
1369 we can live with the minor issue in bug 14219 (it just results in
1370 some load on the network) but the regression of 16381 is too much
1371 of a setback. First-round fix for bug 16381; bugfix
1374 o Major bugfixes (hidden services):
1375 - When cannibalizing a circuit for an introduction point, always
1376 extend to the chosen exit node (creating a 4 hop circuit).
1377 Previously Tor would use the current circuit exit node, which
1378 changed the original choice of introduction point, and could cause
1379 the hidden service to skip excluded introduction points or
1380 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
1383 o Major bugfixes (open file limit):
1384 - The open file limit wasn't checked before calling
1385 tor_accept_socket_nonblocking(), which would make Tor exceed the
1386 limit. Now, before opening a new socket, Tor validates the open
1387 file limit just before, and if the max has been reached, return an
1388 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
1390 o Major bugfixes (stability, also in 0.2.6.10):
1391 - Stop crashing with an assertion failure when parsing certain kinds
1392 of malformed or truncated microdescriptors. Fixes bug 16400;
1393 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1394 by "cypherpunks_backup".
1395 - Stop random client-side assertion failures that could occur when
1396 connecting to a busy hidden service, or connecting to a hidden
1397 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1400 o Minor features (directory authorities, security, also in 0.2.6.9):
1401 - The HSDir flag given by authorities now requires the Stable flag.
1402 For the current network, this results in going from 2887 to 2806
1403 HSDirs. Also, it makes it harder for an attacker to launch a sybil
1404 attack by raising the effort for a relay to become Stable to
1405 require at the very least 7 days, while maintaining the 96 hours
1406 uptime requirement for HSDir. Implements ticket 8243.
1408 o Minor features (client):
1409 - Relax the validation of hostnames in SOCKS5 requests, allowing the
1410 character '_' to appear, in order to cope with domains observed in
1411 the wild that are serving non-RFC compliant records. Resolves
1413 - Relax the validation done to hostnames in SOCKS5 requests, and
1414 allow a single trailing '.' to cope with clients that pass FQDNs
1415 using that syntax to explicitly indicate that the domain name is
1416 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
1417 - Add GroupWritable and WorldWritable options to unix-socket based
1418 SocksPort and ControlPort options. These options apply to a single
1419 socket, and override {Control,Socks}SocketsGroupWritable. Closes
1422 o Minor features (control protocol):
1423 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
1424 the control protocol. Resolves ticket 15358.
1426 o Minor features (directory authorities):
1427 - Directory authorities no longer vote against the "Fast", "Stable",
1428 and "HSDir" flags just because they were going to vote against
1429 "Running": if the consensus turns out to be that the router was
1430 running, then the authority's vote should count. Patch from Peter
1431 Retzlaff; closes issue 8712.
1433 o Minor features (geoip, also in 0.2.6.10):
1434 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
1435 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
1437 o Minor features (hidden services):
1438 - Add the new options "HiddenServiceMaxStreams" and
1439 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
1440 limit the maximum number of simultaneous streams per circuit, and
1441 optionally tear down the circuit when the limit is exceeded. Part
1444 o Minor features (portability):
1445 - Use C99 variadic macros when the compiler is not GCC. This avoids
1446 failing compilations on MSVC, and fixes a log-file-based race
1447 condition in our old workarounds. Original patch from Gisle Vanem.
1449 o Minor bugfixes (compilation, also in 0.2.6.9):
1450 - Build with --enable-systemd correctly when libsystemd is
1451 installed, but systemd is not. Fixes bug 16164; bugfix on
1452 0.2.6.3-alpha. Patch from Peter Palfrader.
1454 o Minor bugfixes (controller):
1455 - Add the descriptor ID in each HS_DESC control event. It was
1456 missing, but specified in control-spec.txt. Fixes bug 15881;
1457 bugfix on 0.2.5.2-alpha.
1459 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
1460 - Check for failures from crypto_early_init, and refuse to continue.
1461 A previous typo meant that we could keep going with an
1462 uninitialized crypto library, and would have OpenSSL initialize
1463 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1464 when implementing ticket 4900. Patch by "teor".
1466 o Minor bugfixes (hidden services):
1467 - Fix a crash when reloading configuration while at least one
1468 configured and one ephemeral hidden service exists. Fixes bug
1469 16060; bugfix on 0.2.7.1-alpha.
1470 - Avoid crashing with a double-free bug when we create an ephemeral
1471 hidden service but adding it fails for some reason. Fixes bug
1472 16228; bugfix on 0.2.7.1-alpha.
1474 o Minor bugfixes (Linux seccomp2 sandbox):
1475 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
1476 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
1478 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
1479 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
1480 these when eventfd2() support is missing. Fixes bug 16363; bugfix
1481 on 0.2.6.3-alpha. Patch from "teor".
1483 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
1484 - Fix sandboxing to work when running as a relay, by allowing the
1485 renaming of secret_id_key, and allowing the eventfd2 and futex
1486 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
1488 - Allow systemd connections to work with the Linux seccomp2 sandbox
1489 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
1492 o Minor bugfixes (relay):
1493 - Fix a rarely-encountered memory leak when failing to initialize
1494 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
1497 o Minor bugfixes (systemd):
1498 - Fix an accidental formatting error that broke the systemd
1499 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
1500 - Tor's systemd unit file no longer contains extraneous spaces.
1501 These spaces would sometimes confuse tools like deb-systemd-
1502 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
1504 o Minor bugfixes (tests):
1505 - Use the configured Python executable when running test-stem-full.
1506 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
1508 o Minor bugfixes (tests, also in 0.2.6.9):
1509 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
1510 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
1512 o Minor bugfixes (threads, comments):
1513 - Always initialize return value in compute_desc_id in rendcommon.c
1514 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1515 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
1516 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1517 - Remove undefined directive-in-macro in test_util_writepid clang
1518 3.7 complains that using a preprocessor directive inside a macro
1519 invocation in test_util_writepid in test_util.c is undefined.
1520 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1522 o Code simplification and refactoring:
1523 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
1524 to ensure they remain consistent and visible everywhere.
1525 - Remove some vestigial workarounds for the MSVC6 compiler. We
1526 haven't supported that in ages.
1527 - The link authentication code has been refactored for better
1528 testability and reliability. It now uses code generated with the
1529 "trunnel" binary encoding generator, to reduce the risk of bugs
1530 due to programmer error. Done as part of ticket 12498.
1533 - Include a specific and (hopefully) accurate documentation of the
1534 torrc file's meta-format in doc/torrc_format.txt. This is mainly
1535 of interest to people writing programs to parse or generate torrc
1536 files. This document is not a commitment to long-term
1537 compatibility; some aspects of the current format are a bit
1538 ridiculous. Closes ticket 2325.
1541 - Tor no longer supports copies of OpenSSL that are missing support
1542 for Elliptic Curve Cryptography. (We began using ECC when
1543 available in 0.2.4.8-alpha, for more safe and efficient key
1544 negotiation.) In particular, support for at least one of P256 or
1545 P224 is now required, with manual configuration needed if only
1546 P224 is available. Resolves ticket 16140.
1547 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
1548 on an operating system that has not upgraded to OpenSSL 1.0 or
1549 later, and you compile Tor from source, you will need to install a
1550 more recent OpenSSL to link Tor against.) These versions of
1551 OpenSSL are still supported by the OpenSSL, but the numerous
1552 cryptographic improvements in later OpenSSL releases makes them a
1553 clear choice. Resolves ticket 16034.
1554 - Remove the HidServDirectoryV2 option. Now all relays offer to
1555 store hidden service descriptors. Related to 16543.
1556 - Remove the VoteOnHidServDirectoriesV2 option, since all
1557 authorities have long set it to 1. Closes ticket 16543.
1560 - Document use of coverity, clang static analyzer, and clang dynamic
1561 undefined behavior and address sanitizers in doc/HACKING. Include
1562 detailed usage instructions in the blacklist. Patch by "teor".
1563 Closes ticket 15817.
1564 - The link authentication protocol code now has extensive tests.
1565 - The relay descriptor signature testing code now has
1567 - The test_workqueue program now runs faster, and is enabled by
1568 default as a part of "make check".
1569 - Now that OpenSSL has its own scrypt implementation, add an unit
1570 test that checks for interoperability between libscrypt_scrypt()
1571 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
1572 and rely on EVP_PBE_scrypt() whenever possible. Resolves
1576 Changes in version 0.2.6.10 - 2015-07-12
1577 Tor version 0.2.6.10 fixes some significant stability and hidden
1578 service client bugs, bulletproofs the cryptography init process, and
1579 fixes a bug when using the sandbox code with some older versions of
1580 Linux. Everyone running an older version, especially an older version
1581 of 0.2.6, should upgrade.
1583 o Major bugfixes (hidden service clients, stability):
1584 - Stop refusing to store updated hidden service descriptors on a
1585 client. This reverts commit 9407040c59218 (which indeed fixed bug
1586 14219, but introduced a major hidden service reachability
1587 regression detailed in bug 16381). This is a temporary fix since
1588 we can live with the minor issue in bug 14219 (it just results in
1589 some load on the network) but the regression of 16381 is too much
1590 of a setback. First-round fix for bug 16381; bugfix
1593 o Major bugfixes (stability):
1594 - Stop crashing with an assertion failure when parsing certain kinds
1595 of malformed or truncated microdescriptors. Fixes bug 16400;
1596 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1597 by "cypherpunks_backup".
1598 - Stop random client-side assertion failures that could occur when
1599 connecting to a busy hidden service, or connecting to a hidden
1600 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1603 o Minor features (geoip):
1604 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
1605 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
1607 o Minor bugfixes (crypto error-handling):
1608 - Check for failures from crypto_early_init, and refuse to continue.
1609 A previous typo meant that we could keep going with an
1610 uninitialized crypto library, and would have OpenSSL initialize
1611 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1612 when implementing ticket 4900. Patch by "teor".
1614 o Minor bugfixes (Linux seccomp2 sandbox):
1615 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
1616 these when eventfd2() support is missing. Fixes bug 16363; bugfix
1617 on 0.2.6.3-alpha. Patch from "teor".
1620 Changes in version 0.2.6.9 - 2015-06-11
1621 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
1622 requirements for receiving an HSDir flag, and addresses some other small
1623 bugs in the systemd and sandbox code. Clients using circuit isolation
1624 should upgrade; all directory authorities should upgrade.
1626 o Major bugfixes (client-side privacy):
1627 - Properly separate out each SOCKSPort when applying stream
1628 isolation. The error occurred because each port's session group was
1629 being overwritten by a default value when the listener connection
1630 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
1633 o Minor feature (directory authorities, security):
1634 - The HSDir flag given by authorities now requires the Stable flag.
1635 For the current network, this results in going from 2887 to 2806
1636 HSDirs. Also, it makes it harder for an attacker to launch a sybil
1637 attack by raising the effort for a relay to become Stable which
1638 takes at the very least 7 days to do so and by keeping the 96
1639 hours uptime requirement for HSDir. Implements ticket 8243.
1641 o Minor bugfixes (compilation):
1642 - Build with --enable-systemd correctly when libsystemd is
1643 installed, but systemd is not. Fixes bug 16164; bugfix on
1644 0.2.6.3-alpha. Patch from Peter Palfrader.
1646 o Minor bugfixes (Linux seccomp2 sandbox):
1647 - Fix sandboxing to work when running as a relaymby renaming of
1648 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
1649 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
1650 - Allow systemd connections to work with the Linux seccomp2 sandbox
1651 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
1654 o Minor bugfixes (tests):
1655 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
1656 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
1659 Changes in version 0.2.6.8 - 2015-05-21
1660 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
1661 fixes an authority-side bug in assigning the HSDir flag. All directory
1662 authorities should upgrade.
1664 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
1665 - Revert commit that made directory authorities assign the HSDir
1666 flag to relay without a DirPort; this was bad because such relays
1667 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
1670 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
1671 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1672 a client authorized hidden service. Fixes bug 15823; bugfix
1675 o Minor features (geoip):
1676 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
1677 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
1681 Changes in version 0.2.7.1-alpha - 2015-05-12
1682 Tor 0.2.7.1-alpha is the first alpha release in its series. It
1683 includes numerous small features and bugfixes against previous Tor
1684 versions, and numerous small infrastructure improvements. The most
1685 notable features are several new ways for controllers to interact with
1686 the hidden services subsystem.
1688 o New system requirements:
1689 - Tor no longer includes workarounds to support Libevent versions
1690 before 1.3e. Libevent 2.0 or later is recommended. Closes
1693 o Major features (controller):
1694 - Add the ADD_ONION and DEL_ONION commands that allow the creation
1695 and management of hidden services via the controller. Closes
1697 - New "GETINFO onions/current" and "GETINFO onions/detached"
1698 commands to get information about hidden services created via the
1699 controller. Part of ticket 6411.
1700 - New HSFETCH command to launch a request for a hidden service
1701 descriptor. Closes ticket 14847.
1702 - New HSPOST command to upload a hidden service descriptor. Closes
1703 ticket 3523. Patch by "DonnchaC".
1705 o Major bugfixes (hidden services):
1706 - Revert commit that made directory authorities assign the HSDir
1707 flag to relay without a DirPort; this was bad because such relays
1708 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
1711 o Minor features (clock-jump tolerance):
1712 - Recover better when our clock jumps back many hours, like might
1713 happen for Tails or Whonix users who start with a very wrong
1714 hardware clock, use Tor to discover a more accurate time, and then
1715 fix their clock. Resolves part of ticket 8766.
1717 o Minor features (command-line interface):
1718 - Make --hash-password imply --hush to prevent unnecessary noise.
1719 Closes ticket 15542. Patch from "cypherpunks".
1720 - Print a warning whenever we find a relative file path being used
1721 as torrc option. Resolves issue 14018.
1723 o Minor features (controller):
1724 - Add DirAuthority lines for default directory authorities to the
1725 output of the "GETINFO config/defaults" command if not already
1726 present. Implements ticket 14840.
1727 - Controllers can now use "GETINFO hs/client/desc/id/..." to
1728 retrieve items from the client's hidden service descriptor cache.
1729 Closes ticket 14845.
1730 - Implement a new controller command "GETINFO status/fresh-relay-
1731 descs" to fetch a descriptor/extrainfo pair that was generated on
1732 demand just for the controller's use. Implements ticket 14784.
1734 o Minor features (DoS-resistance):
1735 - Make it harder for attackers to overload hidden services with
1736 introductions, by blocking multiple introduction requests on the
1737 same circuit. Resolves ticket 15515.
1739 o Minor features (geoip):
1740 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
1741 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
1744 o Minor features (HS popularity countermeasure):
1745 - To avoid leaking HS popularity, don't cycle the introduction point
1746 when we've handled a fixed number of INTRODUCE2 cells but instead
1747 cycle it when a random number of introductions is reached, thus
1748 making it more difficult for an attacker to find out the amount of
1749 clients that have used the introduction point for a specific HS.
1750 Closes ticket 15745.
1752 o Minor features (logging):
1753 - Include the Tor version in all LD_BUG log messages, since people
1754 tend to cut and paste those into the bugtracker. Implements
1757 o Minor features (pluggable transports):
1758 - When launching managed pluggable transports on Linux systems,
1759 attempt to have the kernel deliver a SIGTERM on tor exit if the
1760 pluggable transport process is still running. Resolves
1762 - When launching managed pluggable transports, setup a valid open
1763 stdin in the child process that can be used to detect if tor has
1764 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
1765 can be used by implementations to detect this new behavior.
1766 Resolves ticket 15435.
1768 o Minor features (testing):
1769 - Add a test to verify that the compiler does not eliminate our
1770 memwipe() implementation. Closes ticket 15377.
1771 - Add make rule `check-changes` to verify the format of changes
1772 files. Closes ticket 15180.
1773 - Add unit tests for control_event_is_interesting(). Add a compile-
1774 time check that the number of events doesn't exceed the capacity
1775 of control_event_t.event_mask. Closes ticket 15431, checks for
1776 bugs similar to 13085. Patch by "teor".
1777 - Command-line argument tests moved to Stem. Resolves ticket 14806.
1778 - Integrate the ntor, backtrace, and zero-length keys tests into the
1779 automake test suite. Closes ticket 15344.
1780 - Remove assertions during builds to determine Tor's test coverage.
1781 We don't want to trigger these even in assertions, so including
1782 them artificially makes our branch coverage look worse than it is.
1783 This patch provides the new test-stem-full and coverage-html-full
1784 configure options. Implements ticket 15400.
1786 o Minor bugfixes (build):
1787 - Improve out-of-tree builds by making non-standard rules work and
1788 clean up additional files and directories. Fixes bug 15053; bugfix
1791 o Minor bugfixes (command-line interface):
1792 - When "--quiet" is provided along with "--validate-config", do not
1793 write anything to stdout on success. Fixes bug 14994; bugfix
1795 - When complaining about bad arguments to "--dump-config", use
1798 o Minor bugfixes (configuration, unit tests):
1799 - Only add the default fallback directories when the DirAuthorities,
1800 AlternateDirAuthority, and FallbackDir directory config options
1801 are set to their defaults. The default fallback directory list is
1802 currently empty, this fix will only change tor's behavior when it
1803 has default fallback directories. Includes unit tests for
1804 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
1805 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
1807 o Minor bugfixes (correctness):
1808 - For correctness, avoid modifying a constant string in
1809 handle_control_postdescriptor. Fixes bug 15546; bugfix
1811 - Remove side-effects from tor_assert() calls. This was harmless,
1812 because we never disable assertions, but it is bad style and
1813 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
1816 o Minor bugfixes (hidden service):
1817 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1818 a client authorized hidden service. Fixes bug 15823; bugfix
1820 - Remove an extraneous newline character from the end of hidden
1821 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
1823 o Minor bugfixes (interface):
1824 - Print usage information for --dump-config when it is used without
1825 an argument. Also, fix the error message to use different wording
1826 and add newline at the end. Fixes bug 15541; bugfix
1829 o Minor bugfixes (logs):
1830 - When building Tor under Clang, do not include an extra set of
1831 parentheses in log messages that include function names. Fixes bug
1832 15269; bugfix on every released version of Tor when compiled with
1833 recent enough Clang.
1835 o Minor bugfixes (network):
1836 - When attempting to use fallback technique for network interface
1837 lookup, disregard loopback and multicast addresses since they are
1838 unsuitable for public communications.
1840 o Minor bugfixes (statistics):
1841 - Disregard the ConnDirectionStatistics torrc options when Tor is
1842 not a relay since in that mode of operation no sensible data is
1843 being collected and because Tor might run into measurement hiccups
1844 when running as a client for some time, then becoming a relay.
1845 Fixes bug 15604; bugfix on 0.2.2.35.
1847 o Minor bugfixes (test networks):
1848 - When self-testing reachability, use ExtendAllowPrivateAddresses to
1849 determine if local/private addresses imply reachability. The
1850 previous fix used TestingTorNetwork, which implies
1851 ExtendAllowPrivateAddresses, but this excluded rare configurations
1852 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
1853 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
1854 issue discovered by CJ Ess.
1856 o Minor bugfixes (testing):
1857 - Check for matching value in server response in ntor_ref.py. Fixes
1858 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
1860 - Set the severity correctly when testing
1861 get_interface_addresses_ifaddrs() and
1862 get_interface_addresses_win32(), so that the tests fail gracefully
1863 instead of triggering an assertion. Fixes bug 15759; bugfix on
1864 0.2.6.3-alpha. Reported by Nicolas Derive.
1866 o Code simplification and refactoring:
1867 - Move the hacky fallback code out of get_interface_address6() into
1868 separate function and get it covered with unit-tests. Resolves
1870 - Refactor hidden service client-side cache lookup to intelligently
1871 report its various failure cases, and disentangle failure cases
1872 involving a lack of introduction points. Closes ticket 14391.
1873 - Use our own Base64 encoder instead of OpenSSL's, to allow more
1874 control over the output. Part of ticket 15652.
1877 - Improve the descriptions of statistics-related torrc options in
1878 the manpage to describe rationale and possible uses cases. Fixes
1880 - Improve the layout and formatting of ./configure --help messages.
1881 Closes ticket 15024. Patch from "cypherpunks".
1882 - Standardize on the term "server descriptor" in the manual page.
1883 Previously, we had used "router descriptor", "server descriptor",
1884 and "relay descriptor" interchangeably. Part of ticket 14987.
1887 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
1888 and always use the internal Base64 decoder. The internal decoder
1889 has been part of tor since 0.2.0.10-alpha, and no one should
1890 be using the OpenSSL one. Part of ticket 15652.
1891 - Remove the 'tor_strclear()' function; use memwipe() instead.
1892 Closes ticket 14922.
1895 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
1896 fingerprinting we now recommend pluggable transports; for forward-
1897 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
1898 - Remove the undocumented "--digests" command-line option. It
1899 complicated our build process, caused subtle build issues on
1900 multiple platforms, and is now redundant since we started
1901 including git version identifiers. Closes ticket 14742.
1902 - Tor no longer contains checks for ancient directory cache versions
1903 that didn't know about microdescriptors.
1904 - Tor no longer contains workarounds for stat files generated by
1905 super-old versions of Tor that didn't choose guards sensibly.
1908 Changes in version 0.2.4.27 - 2015-04-06
1909 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
1910 could be used by an attacker to crash hidden services, or crash clients
1911 visiting hidden services. Hidden services should upgrade as soon as
1912 possible; clients should upgrade whenever packages become available.
1914 This release also backports a simple improvement to make hidden
1915 services a bit less vulnerable to denial-of-service attacks.
1917 o Major bugfixes (security, hidden service):
1918 - Fix an issue that would allow a malicious client to trigger an
1919 assertion failure and halt a hidden service. Fixes bug 15600;
1920 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1921 - Fix a bug that could cause a client to crash with an assertion
1922 failure when parsing a malformed hidden service descriptor. Fixes
1923 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1925 o Minor features (DoS-resistance, hidden service):
1926 - Introduction points no longer allow multiple INTRODUCE1 cells to
1927 arrive on the same circuit. This should make it more expensive for
1928 attackers to overwhelm hidden services with introductions.
1929 Resolves ticket 15515.
1932 Changes in version 0.2.5.12 - 2015-04-06
1933 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
1934 could be used by an attacker to crash hidden services, or crash clients
1935 visiting hidden services. Hidden services should upgrade as soon as
1936 possible; clients should upgrade whenever packages become available.
1938 This release also backports a simple improvement to make hidden
1939 services a bit less vulnerable to denial-of-service attacks.
1941 o Major bugfixes (security, hidden service):
1942 - Fix an issue that would allow a malicious client to trigger an
1943 assertion failure and halt a hidden service. Fixes bug 15600;
1944 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1945 - Fix a bug that could cause a client to crash with an assertion
1946 failure when parsing a malformed hidden service descriptor. Fixes
1947 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1949 o Minor features (DoS-resistance, hidden service):
1950 - Introduction points no longer allow multiple INTRODUCE1 cells to
1951 arrive on the same circuit. This should make it more expensive for
1952 attackers to overwhelm hidden services with introductions.
1953 Resolves ticket 15515.
1956 Changes in version 0.2.6.7 - 2015-04-06
1957 Tor 0.2.6.7 fixes two security issues that could be used by an
1958 attacker to crash hidden services, or crash clients visiting hidden
1959 services. Hidden services should upgrade as soon as possible; clients
1960 should upgrade whenever packages become available.
1962 This release also contains two simple improvements to make hidden
1963 services a bit less vulnerable to denial-of-service attacks.
1965 o Major bugfixes (security, hidden service):
1966 - Fix an issue that would allow a malicious client to trigger an
1967 assertion failure and halt a hidden service. Fixes bug 15600;
1968 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1969 - Fix a bug that could cause a client to crash with an assertion
1970 failure when parsing a malformed hidden service descriptor. Fixes
1971 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1973 o Minor features (DoS-resistance, hidden service):
1974 - Introduction points no longer allow multiple INTRODUCE1 cells to
1975 arrive on the same circuit. This should make it more expensive for
1976 attackers to overwhelm hidden services with introductions.
1977 Resolves ticket 15515.
1978 - Decrease the amount of reattempts that a hidden service performs
1979 when its rendezvous circuits fail. This reduces the computational
1980 cost for running a hidden service under heavy load. Resolves
1984 Changes in version 0.2.6.6 - 2015-03-24
1985 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
1987 It adds numerous safety, security, correctness, and performance
1988 improvements. Client programs can be configured to use more kinds of
1989 sockets, AutomapHosts works better, the multithreading backend is
1990 improved, cell transmission is refactored, test coverage is much
1991 higher, more denial-of-service attacks are handled, guard selection is
1992 improved to handle long-term guards better, pluggable transports
1993 should work a bit better, and some annoying hidden service performance
1994 bugs should be addressed.
1996 o Minor bugfixes (portability):
1997 - Use the correct datatype in the SipHash-2-4 function to prevent
1998 compilers from assuming any sort of alignment. Fixes bug 15436;
1999 bugfix on 0.2.5.3-alpha.
2001 Changes in version 0.2.6.5-rc - 2015-03-18
2002 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
2003 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
2005 o Major bugfixes (client):
2006 - Avoid crashing when making certain configuration option changes on
2007 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
2010 o Major bugfixes (pluggable transports):
2011 - Initialize the extended OR Port authentication cookie before
2012 launching pluggable transports. This prevents a race condition
2013 that occured when server-side pluggable transports would cache the
2014 authentication cookie before it has been (re)generated. Fixes bug
2015 15240; bugfix on 0.2.5.1-alpha.
2017 o Major bugfixes (portability):
2018 - Do not crash on startup when running on Solaris. Fixes a bug
2019 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
2022 o Minor features (heartbeat):
2023 - On relays, report how many connections we negotiated using each
2024 version of the Tor link protocols. This information will let us
2025 know if removing support for very old versions of the Tor
2026 protocols is harming the network. Closes ticket 15212.
2028 o Code simplification and refactoring:
2029 - Refactor main loop to extract the 'loop' part. This makes it
2030 easier to run Tor under Shadow. Closes ticket 15176.
2033 Changes in version 0.2.5.11 - 2015-03-17
2034 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
2036 It backports several bugfixes from the 0.2.6 branch, including a
2037 couple of medium-level security fixes for relays and exit nodes.
2038 It also updates the list of directory authorities.
2040 o Directory authority changes:
2041 - Remove turtles as a directory authority.
2042 - Add longclaw as a new (v3) directory authority. This implements
2043 ticket 13296. This keeps the directory authority count at 9.
2044 - The directory authority Faravahar has a new IP address. This
2045 closes ticket 14487.
2047 o Major bugfixes (crash, OSX, security):
2048 - Fix a remote denial-of-service opportunity caused by a bug in
2049 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
2052 o Major bugfixes (relay, stability, possible security):
2053 - Fix a bug that could lead to a relay crashing with an assertion
2054 failure if a buffer of exactly the wrong layout was passed to
2055 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2056 0.2.0.10-alpha. Patch from 'cypherpunks'.
2057 - Do not assert if the 'data' pointer on a buffer is advanced to the
2058 very end of the buffer; log a BUG message instead. Only assert if
2059 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2061 o Major bugfixes (exit node stability):
2062 - Fix an assertion failure that could occur under high DNS load.
2063 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2064 diagnosed and fixed by "cypherpunks".
2066 o Major bugfixes (Linux seccomp2 sandbox):
2067 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
2068 crash during attempts to call wait4. Fixes bug 15088; bugfix on
2069 0.2.5.1-alpha. Patch from "sanic".
2071 o Minor features (controller):
2072 - New "GETINFO bw-event-cache" to get information about recent
2073 bandwidth events. Closes ticket 14128. Useful for controllers to
2074 get recent bandwidth history after the fix for ticket 13988.
2076 o Minor features (geoip):
2077 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2078 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2081 o Minor bugfixes (client, automapping):
2082 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
2083 no value follows the option. Fixes bug 14142; bugfix on
2084 0.2.4.7-alpha. Patch by "teor".
2085 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
2086 14195; bugfix on 0.1.0.1-rc.
2088 o Minor bugfixes (compilation):
2089 - Build without warnings with the stock OpenSSL srtp.h header, which
2090 has a duplicate declaration of SSL_get_selected_srtp_profile().
2091 Fixes bug 14220; this is OpenSSL's bug, not ours.
2093 o Minor bugfixes (directory authority):
2094 - Allow directory authorities to fetch more data from one another if
2095 they find themselves missing lots of votes. Previously, they had
2096 been bumping against the 10 MB queued data limit. Fixes bug 14261;
2097 bugfix on 0.1.2.5-alpha.
2098 - Enlarge the buffer to read bwauth generated files to avoid an
2099 issue when parsing the file in dirserv_read_measured_bandwidths().
2100 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
2102 o Minor bugfixes (statistics):
2103 - Increase period over which bandwidth observations are aggregated
2104 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
2106 o Minor bugfixes (preventative security, C safety):
2107 - When reading a hexadecimal, base-32, or base-64 encoded value from
2108 a string, always overwrite the whole output buffer. This prevents
2109 some bugs where we would look at (but fortunately, not reveal)
2110 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
2114 Changes in version 0.2.4.26 - 2015-03-17
2115 Tor 0.2.4.26 includes an updated list of directory authorities. It
2116 also backports a couple of stability and security bugfixes from 0.2.5
2119 o Directory authority changes:
2120 - Remove turtles as a directory authority.
2121 - Add longclaw as a new (v3) directory authority. This implements
2122 ticket 13296. This keeps the directory authority count at 9.
2123 - The directory authority Faravahar has a new IP address. This
2124 closes ticket 14487.
2126 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
2127 - Fix an assertion failure that could occur under high DNS load.
2128 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2129 diagnosed and fixed by "cypherpunks".
2131 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
2132 - Fix a bug that could lead to a relay crashing with an assertion
2133 failure if a buffer of exactly the wrong layout was passed to
2134 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2135 0.2.0.10-alpha. Patch from 'cypherpunks'.
2136 - Do not assert if the 'data' pointer on a buffer is advanced to the
2137 very end of the buffer; log a BUG message instead. Only assert if
2138 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2140 o Minor features (geoip):
2141 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2142 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2145 Changes in version 0.2.6.4-rc - 2015-03-09
2146 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
2147 attacker might be able to use in order to crash certain Tor
2148 directories. It also resolves some minor issues left over from, or
2149 introduced in, Tor 0.2.6.3-alpha or earlier.
2151 o Major bugfixes (crash, OSX, security):
2152 - Fix a remote denial-of-service opportunity caused by a bug in
2153 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
2156 o Major bugfixes (relay, stability, possible security):
2157 - Fix a bug that could lead to a relay crashing with an assertion
2158 failure if a buffer of exactly the wrong layout is passed to
2159 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2160 0.2.0.10-alpha. Patch from "cypherpunks".
2161 - Do not assert if the 'data' pointer on a buffer is advanced to the
2162 very end of the buffer; log a BUG message instead. Only assert if
2163 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2165 o Major bugfixes (FreeBSD IPFW transparent proxy):
2166 - Fix address detection with FreeBSD transparent proxies, when
2167 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
2170 o Major bugfixes (Linux seccomp2 sandbox):
2171 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
2172 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
2174 - Allow AF_UNIX hidden services to be used with the seccomp2
2175 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
2176 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
2177 crash during attempts to call wait4. Fixes bug 15088; bugfix on
2178 0.2.5.1-alpha. Patch from "sanic".
2180 o Minor features (controller):
2181 - Messages about problems in the bootstrap process now include
2182 information about the server we were trying to connect to when we
2183 noticed the problem. Closes ticket 15006.
2185 o Minor features (geoip):
2186 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2187 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2190 o Minor features (logs):
2191 - Quiet some log messages in the heartbeat and at startup. Closes
2194 o Minor bugfixes (certificate handling):
2195 - If an authority operator accidentally makes a signing certificate
2196 with a future publication time, do not discard its real signing
2197 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
2198 - Remove any old authority certificates that have been superseded
2199 for at least two days. Previously, we would keep superseded
2200 certificates until they expired, if they were published close in
2201 time to the certificate that superseded them. Fixes bug 11454;
2202 bugfix on 0.2.1.8-alpha.
2204 o Minor bugfixes (compilation):
2205 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
2207 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
2210 o Minor bugfixes (testing):
2211 - Fix endianness issues in unit test for resolve_my_address() to
2212 have it pass on big endian systems. Fixes bug 14980; bugfix on
2214 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
2215 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
2216 - When running the new 'make test-stem' target, use the configured
2217 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
2219 - When running the zero-length-keys tests, do not use the default
2220 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
2223 o Directory authority IP change:
2224 - The directory authority Faravahar has a new IP address. This
2225 closes ticket 14487.
2228 - Remove some lingering dead code that once supported mempools.
2229 Mempools were disabled by default in 0.2.5, and removed entirely
2230 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
2234 Changes in version 0.2.6.3-alpha - 2015-02-19
2235 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
2236 the 0.2.6.x series. It introduces support for more kinds of sockets,
2237 makes it harder to accidentally run an exit, improves our
2238 multithreading backend, incorporates several fixes for the
2239 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
2241 If no major regressions or security holes are found in this version,
2242 the next version will be a release candidate.
2244 o Deprecated versions:
2245 - Tor relays older than 0.2.4.18-rc are no longer allowed to
2246 advertise themselves on the network. Closes ticket 13555.
2248 o Major features (security, unix domain sockets):
2249 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
2250 applications can reach Tor without having to create AF_INET or
2251 AF_INET6 sockets, meaning they can completely disable their
2252 ability to make non-Tor network connections. To create a socket of
2253 this type, use "SocksPort unix:/path/to/socket". Implements
2255 - Support mapping hidden service virtual ports to AF_UNIX sockets.
2256 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
2257 Implements ticket 11485.
2259 o Major features (changed defaults):
2260 - Prevent relay operators from unintentionally running exits: When a
2261 relay is configured as an exit node, we now warn the user unless
2262 the "ExitRelay" option is set to 1. We warn even more loudly if
2263 the relay is configured with the default exit policy, since this
2264 can indicate accidental misconfiguration. Setting "ExitRelay 0"
2265 stops Tor from running as an exit relay. Closes ticket 10067.
2267 o Major features (directory system):
2268 - When downloading server- or microdescriptors from a directory
2269 server, we no longer launch multiple simultaneous requests to the
2270 same server. This reduces load on the directory servers,
2271 especially when directory guards are in use. Closes ticket 9969.
2272 - When downloading server- or microdescriptors over a tunneled
2273 connection, do not limit the length of our requests to what the
2274 Squid proxy is willing to handle. Part of ticket 9969.
2275 - Authorities can now vote on the correct digests and latest
2276 versions for different software packages. This allows packages
2277 that include Tor to use the Tor authority system as a way to get
2278 notified of updates and their correct digests. Implements proposal
2279 227. Closes ticket 10395.
2281 o Major features (guards):
2282 - Introduce the Guardfraction feature to improves load balancing on
2283 guard nodes. Specifically, it aims to reduce the traffic gap that
2284 guard nodes experience when they first get the Guard flag. This is
2285 a required step if we want to increase the guard lifetime to 9
2286 months or greater. Closes ticket 9321.
2288 o Major features (performance):
2289 - Make the CPU worker implementation more efficient by avoiding the
2290 kernel and lengthening pipelines. The original implementation used
2291 sockets to transfer data from the main thread to the workers, and
2292 didn't allow any thread to be assigned more than a single piece of
2293 work at once. The new implementation avoids communications
2294 overhead by making requests in shared memory, avoiding kernel IO
2295 where possible, and keeping more requests in flight at once.
2296 Implements ticket 9682.
2298 o Major features (relay):
2299 - Raise the minimum acceptable configured bandwidth rate for bridges
2300 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
2301 20 KiB/sec.) Closes ticket 13822.
2303 o Major bugfixes (exit node stability):
2304 - Fix an assertion failure that could occur under high DNS load.
2305 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2306 diagnosed and fixed by "cypherpunks".
2308 o Major bugfixes (mixed relay-client operation):
2309 - When running as a relay and client at the same time (not
2310 recommended), if we decide not to use a new guard because we want
2311 to retry older guards, only close the locally-originating circuits
2312 passing through that guard. Previously we would close all the
2313 circuits through that guard. Fixes bug 9819; bugfix on
2314 0.2.1.1-alpha. Reported by "skruffy".
2316 o Minor features (build):
2317 - New --disable-system-torrc compile-time option to prevent Tor from
2318 looking for the system-wide torrc or torrc-defaults files.
2319 Resolves ticket 13037.
2321 o Minor features (controller):
2322 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
2323 events so controllers can observe circuit isolation inputs. Closes
2325 - ControlPort now supports the unix:/path/to/socket syntax as an
2326 alternative to the ControlSocket option, for consistency with
2327 SocksPort and HiddenServicePort. Closes ticket 14451.
2328 - New "GETINFO bw-event-cache" to get information about recent
2329 bandwidth events. Closes ticket 14128. Useful for controllers to
2330 get recent bandwidth history after the fix for ticket 13988.
2332 o Minor features (Denial of service resistance):
2333 - Count the total number of bytes used storing hidden service
2334 descriptors against the value of MaxMemInQueues. If we're low on
2335 memory, and more than 20% of our memory is used holding hidden
2336 service descriptors, free them until no more than 10% of our
2337 memory holds hidden service descriptors. Free the least recently
2338 fetched descriptors first. Resolves ticket 13806.
2339 - When we have recently been under memory pressure (over 3/4 of
2340 MaxMemInQueues is allocated), then allocate smaller zlib objects
2341 for small requests. Closes ticket 11791.
2343 o Minor features (geoip):
2344 - Update geoip and geoip6 files to the January 7 2015 Maxmind
2345 GeoLite2 Country database.
2347 o Minor features (guard nodes):
2348 - Reduce the time delay before saving guard status to disk from 10
2349 minutes to 30 seconds (or from one hour to 10 minutes if
2350 AvoidDiskWrites is set). Closes ticket 12485.
2352 o Minor features (hidden service):
2353 - Make Sybil attacks against hidden services harder by changing the
2354 minimum time required to get the HSDir flag from 25 hours up to 96
2355 hours. Addresses ticket 14149.
2356 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
2357 services to disable the anti-scanning feature introduced in
2358 0.2.6.2-alpha. With this option not set, a connection to an
2359 unlisted port closes the circuit. With this option set, only a
2360 RELAY_DONE cell is sent. Closes ticket 14084.
2362 o Minor features (interface):
2363 - Implement "-f -" command-line option to read torrc configuration
2364 from standard input, if you don't want to store the torrc file in
2365 the file system. Implements feature 13865.
2367 o Minor features (logging):
2368 - Add a count of unique clients to the bridge heartbeat message.
2369 Resolves ticket 6852.
2370 - Suppress "router info incompatible with extra info" message when
2371 reading extrainfo documents from cache. (This message got loud
2372 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
2374 - Elevate hidden service authorized-client message from DEBUG to
2375 INFO. Closes ticket 14015.
2377 o Minor features (stability):
2378 - Add assertions in our hash-table iteration code to check for
2379 corrupted values that could cause infinite loops. Closes
2382 o Minor features (systemd):
2383 - Various improvements and modernizations in systemd hardening
2384 support. Closes ticket 13805. Patch from Craig Andrews.
2386 o Minor features (testing networks):
2387 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
2388 and the default on a testing network to 2 minutes. Drop the
2389 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
2390 keep the default on a testing network at 30 seconds. This reduces
2391 HS bootstrap time to around 25 seconds. Also, change the default
2392 time in test-network.sh to match. Closes ticket 13401. Patch
2394 - Create TestingDirAuthVoteHSDir to correspond to
2395 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
2396 HSDir flag for the listed relays regardless of uptime or ORPort
2397 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
2398 Partial implementation for ticket 14067. Patch by "teor".
2400 o Minor features (tor2web mode):
2401 - Introduce the config option Tor2webRendezvousPoints, which allows
2402 clients in Tor2webMode to select a specific Rendezvous Point to be
2403 used in HS circuits. This might allow better performance for
2404 Tor2Web nodes. Implements ticket 12844.
2406 o Minor bugfixes (client DNS):
2407 - Report the correct cached DNS expiration times on SOCKS port or in
2408 DNS replies. Previously, we would report everything as "never
2409 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
2410 - Avoid a small memory leak when we find a cached answer for a
2411 reverse DNS lookup in a client-side DNS cache. (Remember, client-
2412 side DNS caching is off by default, and is not recommended.) Fixes
2413 bug 14259; bugfix on 0.2.0.1-alpha.
2415 o Minor bugfixes (client, automapping):
2416 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
2417 no value follows the option. Fixes bug 14142; bugfix on
2418 0.2.4.7-alpha. Patch by "teor".
2419 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
2420 14195; bugfix on 0.1.0.1-rc.
2421 - Prevent changes to other options from removing the wildcard value
2422 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
2424 - Allow MapAddress and AutomapHostsOnResolve to work together when
2425 an address is mapped into another address type (like .onion) that
2426 must be automapped at resolve time. Fixes bug 7555; bugfix
2429 o Minor bugfixes (client, bridges):
2430 - When we are using bridges and we had a network connectivity
2431 problem, only retry connecting to our currently configured
2432 bridges, not all bridges we know about and remember using. Fixes
2433 bug 14216; bugfix on 0.2.2.17-alpha.
2435 o Minor bugfixes (client, IPv6):
2436 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
2437 flag is not set; and not because the NoIPv4Traffic flag was set.
2438 Previously we'd looked at the NoIPv4Traffic flag for both types of
2439 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
2441 o Minor bugfixes (compilation):
2442 - The address of an array in the middle of a structure will always
2443 be non-NULL. clang recognises this and complains. Disable the
2444 tautologous and redundant check to silence this warning. Fixes bug
2445 14001; bugfix on 0.2.1.2-alpha.
2446 - Avoid warnings when building with systemd 209 or later. Fixes bug
2447 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
2448 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
2449 Addresses ticket 14188.
2450 - Build without warnings with the stock OpenSSL srtp.h header, which
2451 has a duplicate declaration of SSL_get_selected_srtp_profile().
2452 Fixes bug 14220; this is OpenSSL's bug, not ours.
2453 - Do not compile any code related to Tor2Web mode when Tor2Web mode
2454 is not enabled at compile time. Previously, this code was included
2455 in a disabled state. See discussion on ticket 12844.
2456 - Remove the --disable-threads configure option again. It was
2457 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
2458 14819; bugfix on 0.2.6.2-alpha.
2460 o Minor bugfixes (controller):
2461 - Report "down" in response to the "GETINFO entry-guards" command
2462 when relays are down with an unreachable_since value. Previously,
2463 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
2464 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
2465 14116; bugfix on 0.2.2.9-alpha.
2466 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
2467 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
2469 o Minor bugfixes (directory authority):
2470 - Allow directory authorities to fetch more data from one another if
2471 they find themselves missing lots of votes. Previously, they had
2472 been bumping against the 10 MB queued data limit. Fixes bug 14261;
2473 bugfix on 0.1.2.5-alpha.
2474 - Do not attempt to download extrainfo documents which we will be
2475 unable to validate with a matching server descriptor. Fixes bug
2476 13762; bugfix on 0.2.0.1-alpha.
2477 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
2478 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
2479 - Enlarge the buffer to read bwauth generated files to avoid an
2480 issue when parsing the file in dirserv_read_measured_bandwidths().
2481 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
2483 o Minor bugfixes (file handling):
2484 - Stop failing when key files are zero-length. Instead, generate new
2485 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
2486 on all versions of Tor. Patch by "teor".
2487 - Stop generating a fresh .old RSA onion key file when the .old file
2488 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
2489 - Avoid overwriting .old key files with empty key files.
2490 - Skip loading zero-length extrainfo store, router store, stats,
2491 state, and key files.
2492 - Avoid crashing when trying to reload a torrc specified as a
2493 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
2496 o Minor bugfixes (hidden services):
2497 - Close the introduction circuit when we have no more usable intro
2498 points, instead of waiting for it to time out. This also ensures
2499 that no follow-up HS descriptor fetch is triggered when the
2500 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
2501 - When fetching a hidden service descriptor for a down service that
2502 was recently up, do not keep refetching until we try the same
2503 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
2504 - Successfully launch Tor with a nonexistent hidden service
2505 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
2506 14106; bugfix on 0.2.6.2-alpha.
2508 o Minor bugfixes (logging):
2509 - Avoid crashing when there are more log domains than entries in
2510 domain_list. Bugfix on 0.2.3.1-alpha.
2511 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
2513 - Don't log messages to stdout twice when starting up. Fixes bug
2514 13993; bugfix on 0.2.6.1-alpha.
2516 o Minor bugfixes (parsing):
2517 - Stop accepting milliseconds (or other junk) at the end of
2518 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
2519 - Support two-number and three-number version numbers correctly, in
2520 case we change the Tor versioning system in the future. Fixes bug
2521 13661; bugfix on 0.0.8pre1.
2523 o Minor bugfixes (path counting):
2524 - When deciding whether the consensus lists any exit nodes, count
2525 the number listed in the consensus, not the number we have
2526 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
2527 - When deciding whether we have any exit nodes, only examine
2528 ExitNodes when the ExitNodes option is actually set. Fixes part of
2529 bug 14918; bugfix on 0.2.6.2-alpha.
2530 - Get rid of redundant and possibly scary warnings that we are
2531 missing directory information while we bootstrap. Fixes part of
2532 bug 14918; bugfix on 0.2.6.2-alpha.
2534 o Minor bugfixes (portability):
2535 - Fix the ioctl()-based network interface lookup code so that it
2536 will work on systems that have variable-length struct ifreq, for
2538 - Fix scheduler compilation on targets where char is unsigned. Fixes
2539 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
2541 o Minor bugfixes (sandbox):
2542 - Allow glibc fatal errors to be sent to stderr before Tor exits.
2543 Previously, glibc would try to write them to /dev/tty, and the
2544 sandbox would trap the call and make Tor exit prematurely. Fixes
2545 bug 14759; bugfix on 0.2.5.1-alpha.
2547 o Minor bugfixes (shutdown):
2548 - When shutting down, always call event_del() on lingering read or
2549 write events before freeing them. Otherwise, we risk double-frees
2550 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
2553 o Minor bugfixes (small memory leaks):
2554 - Avoid leaking memory when using IPv6 virtual address mappings.
2555 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
2558 o Minor bugfixes (statistics):
2559 - Increase period over which bandwidth observations are aggregated
2560 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
2562 o Minor bugfixes (systemd support):
2563 - Fix detection and operation of systemd watchdog. Fixes part of bug
2564 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
2565 - Run correctly under systemd with the RunAsDaemon option set. Fixes
2566 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
2567 - Inform the systemd supervisor about more changes in the Tor
2568 process status. Implements part of ticket 14141. Patch from
2570 - Cause the "--disable-systemd" option to actually disable systemd
2571 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
2574 o Minor bugfixes (TLS):
2575 - Check more thoroughly throughout the TLS code for possible
2576 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
2578 o Minor bugfixes (transparent proxy):
2579 - Use getsockname, not getsockopt, to retrieve the address for a
2580 TPROXY-redirected connection. Fixes bug 13796; bugfix
2583 o Code simplification and refactoring:
2584 - Move fields related to isolating and configuring client ports into
2585 a shared structure. Previously, they were duplicated across
2586 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
2587 to copy them correctly had been the cause of at least one bug in
2588 the past. Closes ticket 8546.
2589 - Refactor the get_interface_addresses_raw() doom-function into
2590 multiple smaller and simpler subfunctions. Cover the resulting
2591 subfunctions with unit-tests. Fixes a significant portion of
2593 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
2594 only for version <= 0.2.2.24 which is now deprecated. Closes
2596 - Remove a test for a long-defunct broken version-one
2600 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
2601 for writing the OpenBSD-specific tips. Resolves ticket 13702.
2602 - Make the tor-resolve documentation match its help string and its
2603 options. Resolves part of ticket 14325.
2604 - Log a more useful error message from tor-resolve when failing to
2605 look up a hidden service address. Resolves part of ticket 14325.
2607 o Downgraded warnings:
2608 - Don't warn when we've attempted to contact a relay using the wrong
2609 ntor onion key. Closes ticket 9635.
2612 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
2613 longer silently accepted as an alias for "ExitNodes".
2614 - The --enable-mempool and --enable-buf-freelists options, which
2615 were originally created to work around bad malloc implementations,
2616 no longer exist. They were off-by-default in 0.2.5. Closes
2620 - Make the checkdir/perms test complete successfully even if the
2621 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
2622 - Test that tor does not fail when key files are zero-length. Check
2623 that tor generates new keys, and overwrites the empty key files.
2624 - Test that tor generates new keys when keys are missing
2625 (existing behavior).
2626 - Test that tor does not overwrite key files that already contain
2627 data (existing behavior). Tests bug 13111. Patch by "teor".
2628 - New "make test-stem" target to run stem integration tests.
2629 Requires that the "STEM_SOURCE_DIR" environment variable be set.
2630 Closes ticket 14107.
2631 - Make the test_cmdline_args.py script work correctly on Windows.
2632 Patch from Gisle Vanem.
2633 - Move the slower unit tests into a new "./src/test/test-slow"
2634 binary that can be run independently of the other tests. Closes
2636 - Avoid undefined behavior when sampling huge values from the
2637 Laplace distribution. This made unittests fail on Raspberry Pi.
2638 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
2641 Changes in version 0.2.6.2-alpha - 2014-12-31
2642 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
2643 It introduces a major new backend for deciding when to send cells on
2644 channels, which should lead down the road to big performance
2645 increases. It contains security and statistics features for better
2646 work on hidden services, and numerous bugfixes.
2648 This release contains many new unit tests, along with major
2649 performance improvements for running testing networks using Chutney.
2650 Thanks to a series of patches contributed by "teor", testing networks
2651 should now bootstrap in seconds, rather than minutes.
2653 o Major features (relay, infrastructure):
2654 - Complete revision of the code that relays use to decide which cell
2655 to send next. Formerly, we selected the best circuit to write on
2656 each channel, but we didn't select among channels in any
2657 sophisticated way. Now, we choose the best circuits globally from
2658 among those whose channels are ready to deliver traffic.
2660 This patch implements a new inter-cmux comparison API, a global
2661 high/low watermark mechanism and a global scheduler loop for
2662 transmission prioritization across all channels as well as among
2663 circuits on one channel. This schedule is currently tuned to
2664 (tolerantly) avoid making changes in network performance, but it
2665 should form the basis for major circuit performance increases in
2666 the future. Code by Andrea; tuning by Rob Jansen; implements
2669 o Major features (hidden services):
2670 - Make HS port scanning more difficult by immediately closing the
2671 circuit when a user attempts to connect to a nonexistent port.
2672 Closes ticket 13667.
2673 - Add a HiddenServiceStatistics option that allows Tor relays to
2674 gather and publish statistics about the overall size and volume of
2675 hidden service usage. Specifically, when this option is turned on,
2676 an HSDir will publish an approximate number of hidden services
2677 that have published descriptors to it the past 24 hours. Also, if
2678 a relay has acted as a hidden service rendezvous point, it will
2679 publish the approximate amount of rendezvous cells it has relayed
2680 the past 24 hours. The statistics themselves are obfuscated so
2681 that the exact values cannot be derived. For more details see
2682 proposal 238, "Better hidden service stats from Tor relays". This
2683 feature is currently disabled by default. Implements feature 13192.
2685 o Major bugfixes (client, automap):
2686 - Repair automapping with IPv6 addresses. This automapping should
2687 have worked previously, but one piece of debugging code that we
2688 inserted to detect a regression actually caused the regression to
2689 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
2690 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
2693 o Major bugfixes (hidden services):
2694 - When closing an introduction circuit that was opened in parallel
2695 with others, don't mark the introduction point as unreachable.
2696 Previously, the first successful connection to an introduction
2697 point would make the other introduction points get marked as
2698 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
2700 o Directory authority changes:
2701 - Remove turtles as a directory authority.
2702 - Add longclaw as a new (v3) directory authority. This implements
2703 ticket 13296. This keeps the directory authority count at 9.
2705 o Major removed features:
2706 - Tor clients no longer support connecting to hidden services
2707 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
2708 option has been removed. (There shouldn't be any hidden services
2709 running these versions on the network.) Closes ticket 7803.
2711 o Minor features (client):
2712 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
2713 is enabled, reject requests with IP addresses as hostnames.
2714 Resolves ticket 13315.
2716 o Minor features (controller):
2717 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
2718 write an unscheduled heartbeat message to the log. Implements
2721 o Minor features (geoip):
2722 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
2725 o Minor features (hidden services):
2726 - When re-enabling the network, don't try to build introduction
2727 circuits until we have successfully built a circuit. This makes
2728 hidden services come up faster when the network is re-enabled.
2729 Patch from "akwizgran". Closes ticket 13447.
2730 - When we fail to retrieve a hidden service descriptor, send the
2731 controller an "HS_DESC FAILED" controller event. Implements
2733 - New HiddenServiceDirGroupReadable option to cause hidden service
2734 directories and hostname files to be created group-readable. Patch
2735 from "anon", David Stainton, and "meejah". Closes ticket 11291.
2737 o Minor features (systemd):
2738 - Where supported, when running with systemd, report successful
2739 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
2740 - When running with systemd, support systemd watchdog messages. Part
2741 of ticket 11016. Patch by Michael Scherer.
2743 o Minor features (transparent proxy):
2744 - Update the transparent proxy option checks to allow for both ipfw
2745 and pf on OS X. Closes ticket 14002.
2746 - Use the correct option when using IPv6 with transparent proxy
2747 support on Linux. Resolves 13808. Patch by Francisco Blas
2750 o Minor bugfixes (preventative security, C safety):
2751 - When reading a hexadecimal, base-32, or base-64 encoded value from
2752 a string, always overwrite the whole output buffer. This prevents
2753 some bugs where we would look at (but fortunately, not reveal)
2754 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
2756 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
2757 just the part that's used. This makes it harder for data leak bugs
2758 to occur in the event of other programming failures. Resolves
2761 o Minor bugfixes (client, microdescriptors):
2762 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
2763 computing which microdescriptors to download. This keeps us from
2764 erroneous download behavior if two microdescriptor digests ever
2765 have the same first 160 bits. Fixes part of bug 13399; bugfix
2767 - Reset a router's status if its microdescriptor digest changes,
2768 even if the first 160 bits remain the same. Fixes part of bug
2769 13399; bugfix on 0.2.3.1-alpha.
2771 o Minor bugfixes (compilation):
2772 - Silence clang warnings under --enable-expensive-hardening,
2773 including implicit truncation of 64 bit values to 32 bit, const
2774 char assignment to self, tautological compare, and additional
2775 parentheses around equality tests. Fixes bug 13577; bugfix
2777 - Fix a clang warning about checking whether an address in the
2778 middle of a structure is NULL. Fixes bug 14001; bugfix
2781 o Minor bugfixes (hidden services):
2782 - Correctly send a controller event when we find that a rendezvous
2783 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
2784 - Pre-check directory permissions for new hidden-services to avoid
2785 at least one case of "Bug: Acting on config options left us in a
2786 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
2787 - When adding a new hidden service (for example, via SETCONF), Tor
2788 no longer congratulates the user for running a relay. Fixes bug
2789 13941; bugfix on 0.2.6.1-alpha.
2790 - When fetching hidden service descriptors, we now check not only
2791 for whether we got the hidden service we had in mind, but also
2792 whether we got the particular descriptors we wanted. This prevents
2793 a class of inefficient but annoying DoS attacks by hidden service
2794 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
2797 o Minor bugfixes (Linux seccomp2 sandbox):
2798 - Make transparent proxy support work along with the seccomp2
2799 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
2800 by Francisco Blas Izquierdo Riera.
2801 - Fix a memory leak in tor-resolve when running with the sandbox
2802 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
2804 o Minor bugfixes (logging):
2805 - Downgrade warnings about RSA signature failures to info log level.
2806 Emit a warning when an extra info document is found incompatible
2807 with a corresponding router descriptor. Fixes bug 9812; bugfix
2809 - Make connection_ap_handshake_attach_circuit() log the circuit ID
2810 correctly. Fixes bug 13701; bugfix on 0.0.6.
2812 o Minor bugfixes (misc):
2813 - Stop allowing invalid address patterns like "*/24" that contain
2814 both a wildcard address and a bit prefix length. This affects all
2815 our address-range parsing code. Fixes bug 7484; bugfix
2818 o Minor bugfixes (testing networks, fast startup):
2819 - Allow Tor to build circuits using a consensus with no exits. If
2820 the consensus has no exits (typical of a bootstrapping test
2821 network), allow Tor to build circuits once enough descriptors have
2822 been downloaded. This assists in bootstrapping a testing Tor
2823 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
2825 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
2826 header to directory servers. This allows us to obtain consensuses
2827 promptly when the consensus interval is very short. This assists
2828 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
2829 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
2830 - Stop assuming that private addresses are local when checking
2831 reachability in a TestingTorNetwork. Instead, when testing, assume
2832 all OR connections are remote. (This is necessary due to many test
2833 scenarios running all relays on localhost.) This assists in
2834 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
2835 0.1.0.1-rc. Patch by "teor".
2836 - Avoid building exit circuits from a consensus with no exits. Now
2837 thanks to our fix for 13718, we accept a no-exit network as not
2838 wholly lost, but we need to remember not to try to build exit
2839 circuits on it. Closes ticket 13814; patch by "teor".
2840 - Stop requiring exits to have non-zero bandwithcapacity in a
2841 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
2842 ignore exit bandwidthcapacity. This assists in bootstrapping a
2843 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
2844 on 0.2.0.3-alpha. Patch by "teor".
2845 - Add "internal" to some bootstrap statuses when no exits are
2846 available. If the consensus does not contain Exits, Tor will only
2847 build internal circuits. In this case, relevant statuses will
2848 contain the word "internal" as indicated in the Tor control-
2849 spec.txt. When bootstrap completes, Tor will be ready to build
2850 internal circuits. If a future consensus contains Exits, exit
2851 circuits may become available. Fixes part of bug 13718; bugfix on
2852 0.2.4.10-alpha. Patch by "teor".
2853 - Decrease minimum consensus interval to 10 seconds when
2854 TestingTorNetwork is set, or 5 seconds for the first consensus.
2855 Fix assumptions throughout the code that assume larger intervals.
2856 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
2858 - Avoid excluding guards from path building in minimal test
2859 networks, when we're in a test network and excluding guards would
2860 exclude all relays. This typically occurs in incredibly small tor
2861 networks, and those using "TestingAuthVoteGuard *". Fixes part of
2862 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
2864 o Code simplification and refactoring:
2865 - Stop using can_complete_circuits as a global variable; access it
2866 with a function instead.
2867 - Avoid using operators directly as macro arguments: this lets us
2868 apply coccinelle transformations to our codebase more directly.
2869 Closes ticket 13172.
2870 - Combine the functions used to parse ClientTransportPlugin and
2871 ServerTransportPlugin into a single function. Closes ticket 6456.
2872 - Add inline functions and convenience macros for inspecting channel
2873 state. Refactor the code to use convenience macros instead of
2874 checking channel state directly. Fixes issue 7356.
2875 - Document all members of was_router_added_t and rename
2876 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
2877 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
2878 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
2879 constant instead of hardcoded value. Fixes issue 13840.
2880 - Refactor our generic strmap and digestmap types into a single
2881 implementation, so that we can add a new digest256map
2885 - Document the bridge-authority-only 'networkstatus-bridges' file.
2886 Closes ticket 13713; patch from "tom".
2887 - Fix typo in PredictedPortsRelevanceTime option description in
2888 manpage. Resolves issue 13707.
2889 - Stop suggesting that users specify relays by nickname: it isn't a
2890 good idea. Also, properly cross-reference how to specify relays in
2891 all parts of manual documenting options that take a list of
2892 relays. Closes ticket 13381.
2893 - Clarify the HiddenServiceDir option description in manpage to make
2894 it clear that relative paths are taken with respect to the current
2895 working directory. Also clarify that this behavior is not
2896 guaranteed to remain indefinitely. Fixes issue 13913.
2899 - New tests for many parts of channel, relay, and circuitmux
2900 functionality. Code by Andrea; part of 9262.
2901 - New tests for parse_transport_line(). Part of ticket 6456.
2902 - In the unit tests, use chgrp() to change the group of the unit
2903 test temporary directory to the current user, so that the sticky
2904 bit doesn't interfere with tests that check directory groups.
2906 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
2910 Changes in version 0.2.6.1-alpha - 2014-10-30
2911 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
2912 includes numerous code cleanups and new tests, and fixes a large
2913 number of annoying bugs. Out-of-memory conditions are handled better
2914 than in 0.2.5, pluggable transports have improved proxy support, and
2915 clients now use optimistic data for contacting hidden services. Also,
2916 we are now more robust to changes in what we consider a parseable
2917 directory object, so that tightening restrictions does not have a risk
2918 of introducing infinite download loops.
2920 This is the first alpha release in a new series, so expect there to be
2921 bugs. Users who would rather test out a more stable branch should stay
2922 with 0.2.5.x for now.
2924 o New compiler and system requirements:
2925 - Tor 0.2.6.x requires that your compiler support more of the C99
2926 language standard than before. The 'configure' script now detects
2927 whether your compiler supports C99 mid-block declarations and
2928 designated initializers. If it does not, Tor will not compile.
2930 We may revisit this requirement if it turns out that a significant
2931 number of people need to build Tor with compilers that don't
2932 bother implementing a 15-year-old standard. Closes ticket 13233.
2933 - Tor no longer supports systems without threading support. When we
2934 began working on Tor, there were several systems that didn't have
2935 threads, or where the thread support wasn't able to run the
2936 threads of a single process on multiple CPUs. That no longer
2937 holds: every system where Tor needs to run well now has threading
2938 support. Resolves ticket 12439.
2940 o Removed platform support:
2941 - We no longer include special code to build on Windows CE; as far
2942 as we know, nobody has used Tor on Windows CE in a very long time.
2943 Closes ticket 11446.
2945 o Major features (bridges):
2946 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
2947 transports if they are configured via the "TOR_PT_PROXY"
2948 environment variable. Implements proposal 232. Resolves
2951 o Major features (client performance, hidden services):
2952 - Allow clients to use optimistic data when connecting to a hidden
2953 service, which should remove a round-trip from hidden service
2954 initialization. See proposal 181 for details. Implements
2957 o Major features (directory system):
2958 - Upon receiving an unparseable directory object, if its digest
2959 matches what we expected, then don't try to download it again.
2960 Previously, when we got a descriptor we didn't like, we would keep
2961 trying to download it over and over. Closes ticket 11243.
2963 o Major features (sample torrc):
2964 - Add a new, infrequently-changed "torrc.minimal". This file is
2965 similar to torrc.sample, but it will change as infrequently as
2966 possible, for the benefit of users whose systems prompt them for
2967 intervention whenever a default configuration file is changed.
2968 Making this change allows us to update torrc.sample to be a more
2969 generally useful "sample torrc".
2971 o Major bugfixes (directory authorities):
2972 - Do not assign the HSDir flag to relays if they are not Valid, or
2973 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
2975 o Major bugfixes (directory bandwidth performance):
2976 - Don't flush the zlib buffer aggressively when compressing
2977 directory information for clients. This should save about 7% of
2978 the bandwidth currently used for compressed descriptors and
2979 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
2981 o Minor features (security, memory wiping):
2982 - Ensure we securely wipe keys from memory after
2983 crypto_digest_get_digest and init_curve25519_keypair_from_file
2984 have finished using them. Resolves ticket 13477.
2986 o Minor features (security, out-of-memory handling):
2987 - When handling an out-of-memory condition, allocate less memory for
2988 temporary data structures. Fixes issue 10115.
2989 - When handling an out-of-memory condition, consider more types of
2990 buffers, including those on directory connections, and zlib
2991 buffers. Resolves ticket 11792.
2994 - When identity keypair is generated for first time, log a
2995 congratulatory message that links to the new relay lifecycle
2996 document. Implements feature 10427.
2998 o Minor features (client):
2999 - Clients are now willing to send optimistic data (before they
3000 receive a 'connected' cell) to relays of any version. (Relays
3001 without support for optimistic data are no longer supported on the
3002 Tor network.) Resolves ticket 13153.
3004 o Minor features (directory authorities):
3005 - Don't list relays with a bandwidth estimate of 0 in the consensus.
3006 Implements a feature proposed during discussion of bug 13000.
3007 - In tor-gencert, report an error if the user provides the same
3008 argument more than once.
3009 - If a directory authority can't find a best consensus method in the
3010 votes that it holds, it now falls back to its favorite consensus
3011 method. Previously, it fell back to method 1. Neither of these is
3012 likely to get enough signatures, but "fall back to favorite"
3013 doesn't require us to maintain support an obsolete consensus
3014 method. Implements part of proposal 215.
3016 o Minor features (logging):
3017 - On Unix-like systems, you can now use named pipes as the target of
3018 the Log option, and other options that try to append to files.
3019 Closes ticket 12061. Patch from "carlo von lynX".
3020 - When opening a log file at startup, send it every log message that
3021 we generated between startup and opening it. Previously, log
3022 messages that were generated before opening the log file were only
3023 logged to stdout. Closes ticket 6938.
3024 - Add a TruncateLogFile option to overwrite logs instead of
3025 appending to them. Closes ticket 5583.
3027 o Minor features (portability, Solaris):
3028 - Threads are no longer disabled by default on Solaris; we believe
3029 that the versions of Solaris with broken threading support are all
3030 obsolete by now. Resolves ticket 9495.
3032 o Minor features (relay):
3033 - Re-check our address after we detect a changed IP address from
3034 getsockname(). This ensures that the controller command "GETINFO
3035 address" will report the correct value. Resolves ticket 11582.
3037 - A new AccountingRule option lets Relays set whether they'd like
3038 AccountingMax to be applied separately to inbound and outbound
3039 traffic, or applied to the sum of inbound and outbound traffic.
3040 Resolves ticket 961. Patch by "chobe".
3042 o Minor features (testing networks):
3043 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
3044 the "Exit" flag regardless of their uptime, bandwidth, or exit
3045 policy. TestingTorNetwork must be set for this option to have any
3046 effect. Previously, authorities would take up to 35 minutes to
3047 give nodes the Exit flag in a test network. Partially implements
3050 o Minor features (validation):
3051 - Check all date/time values passed to tor_timegm and
3052 parse_rfc1123_time for validity, taking leap years into account.
3053 Improves HTTP header validation. Implemented with bug 13476.
3054 - In correct_tm(), limit the range of values returned by system
3055 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
3056 This means we don't have to deal with negative or too large dates,
3057 even if a clock is wrong. Otherwise we might fail to read a file
3058 written by us which includes such a date. Fixes bug 13476.
3060 o Minor bugfixes (bridge clients):
3061 - When configured to use a bridge without an identity digest (not
3062 recommended), avoid launching an extra channel to it when
3063 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
3065 o Minor bugfixes (bridges):
3066 - When DisableNetwork is set, do not launch pluggable transport
3067 plugins, and if any are running, terminate them. Fixes bug 13213;
3068 bugfix on 0.2.3.6-alpha.
3070 o Minor bugfixes (C correctness):
3071 - Fix several instances of possible integer overflow/underflow/NaN.
3072 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
3074 - In circuit_build_times_calculate_timeout() in circuitstats.c,
3075 avoid dividing by zero in the pareto calculations. This traps
3076 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
3078 - Fix an integer overflow in format_time_interval(). Fixes bug
3079 13393; bugfix on 0.2.0.10-alpha.
3080 - Set the correct day of year value when the system's localtime(_r)
3081 or gmtime(_r) functions fail to set struct tm. Not externally
3082 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
3083 - Avoid unlikely signed integer overflow in tor_timegm on systems
3084 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
3086 o Minor bugfixes (client):
3087 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
3088 BadExit flag are not considered worthy candidates. Fixes bug
3089 13066; bugfix on 0.1.2.3-alpha.
3090 - Use the consensus schedule for downloading consensuses, and not
3091 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
3092 - Handle unsupported or malformed SOCKS5 requests properly by
3093 responding with the appropriate error message before closing the
3094 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
3096 o Minor bugfixes (client, torrc):
3097 - Stop modifying the value of our DirReqStatistics torrc option just
3098 because we're not a bridge or relay. This bug was causing Tor
3099 Browser users to write "DirReqStatistics 0" in their torrc files
3100 as if they had chosen to change the config. Fixes bug 4244; bugfix
3102 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
3103 that our options have changed every time we SIGHUP. Fixes bug
3104 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
3106 o Minor bugfixes (controller):
3107 - Return an error when the second or later arguments of the
3108 "setevents" controller command are invalid events. Previously we
3109 would return success while silently skipping invalid events. Fixes
3110 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
3112 o Minor bugfixes (directory system):
3113 - Always believe that v3 directory authorities serve extra-info
3114 documents, whether they advertise "caches-extra-info" or not.
3115 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3116 - When running as a v3 directory authority, advertise that you serve
3117 extra-info documents so that clients who want them can find them
3118 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3119 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
3120 Previously, directories offering BRIDGE_DIRINFO and some other
3121 flag (i.e. microdescriptors or extrainfo) would be ignored when
3122 looking for bridges. Partially fixes bug 13163; bugfix
3125 o Minor bugfixes (networking):
3126 - Check for orconns and use connection_or_close_for_error() rather
3127 than connection_mark_for_close() directly in the getsockopt()
3128 failure case of connection_handle_write_impl(). Fixes bug 11302;
3129 bugfix on 0.2.4.4-alpha.
3131 o Minor bugfixes (relay):
3132 - When generating our family list, remove spaces from around the
3133 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
3134 - If our previous bandwidth estimate was 0 bytes, allow publishing a
3135 new relay descriptor immediately. Fixes bug 13000; bugfix
3138 o Minor bugfixes (testing networks):
3139 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
3140 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
3141 - Stop using the default authorities in networks which provide both
3142 AlternateDirAuthority and AlternateBridgeAuthority. Partially
3143 fixes bug 13163; bugfix on 0.2.0.13-alpha.
3145 o Minor bugfixes (testing):
3146 - Stop spawn test failures due to a race condition between the
3147 SIGCHLD handler updating the process status, and the test reading
3148 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
3150 o Minor bugfixes (testing, Windows):
3151 - Avoid passing an extra backslash when creating a temporary
3152 directory for running the unit tests on Windows. Fixes bug 12392;
3153 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
3155 o Minor bugfixes (windows):
3156 - Remove code to special-case handling of NTE_BAD_KEYSET when
3157 acquiring windows CryptoAPI context. This error can't actually
3158 occur for the parameters we're providing. Fixes bug 10816; bugfix
3161 o Minor bugfixes (zlib):
3162 - Avoid truncating a zlib stream when trying to finalize it with an
3163 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
3166 - Allow our configure script to build correctly with autoconf 2.62
3167 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
3168 - Improve the error message from ./configure to make it clear that
3169 when asciidoc has not been found, the user will have to either add
3170 --disable-asciidoc argument or install asciidoc. Resolves
3173 o Code simplification and refactoring:
3174 - Change the entry_is_live() function to take named bitfield
3175 elements instead of an unnamed list of booleans. Closes
3177 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
3178 Resolves ticket 12205.
3179 - Use calloc and reallocarray functions instead of multiply-
3180 then-malloc. This makes it less likely for us to fall victim to an
3181 integer overflow attack when allocating. Resolves ticket 12855.
3182 - Use the standard macro name SIZE_MAX, instead of our
3184 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
3185 functions which take them as arguments. Replace 0 with NO_DIRINFO
3186 in a function call for clarity. Seeks to prevent future issues
3188 - Avoid 4 null pointer errors under clang static analysis by using
3189 tor_assert() to prove that the pointers aren't null. Fixes
3191 - Rework the API of policies_parse_exit_policy() to use a bitmask to
3192 represent parsing options, instead of a confusing mess of
3193 booleans. Resolves ticket 8197.
3194 - Introduce a helper function to parse ExitPolicy in
3195 or_options_t structure.
3198 - Add a doc/TUNING document with tips for handling large numbers of
3199 TCP connections when running busy Tor relay. Update the warning
3200 message to point to this file when running out of sockets
3201 operating system is allowing to use simultaneously. Resolves
3205 - We no longer remind the user about configuration options that have
3206 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
3207 - Remove our old, non-weighted bandwidth-based node selection code.
3208 Previously, we used it as a fallback when we couldn't perform
3209 weighted bandwidth-based node selection. But that would only
3210 happen in the cases where we had no consensus, or when we had a
3211 consensus generated by buggy or ancient directory authorities. In
3212 either case, it's better to use the more modern, better maintained
3213 algorithm, with reasonable defaults for the weights. Closes
3215 - Remove the --disable-curve25519 configure option. Relays and
3216 clients now are required to support curve25519 and the
3218 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
3219 used to be deprecated synonyms for "StrictNodes", are now marked
3220 obsolete. Resolves ticket 12226.
3221 - Clients don't understand the BadDirectory flag in the consensus
3222 anymore, and ignore it.
3225 - Refactor the function that chooses guard nodes so that it can more
3226 easily be tested; write some tests for it.
3227 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
3228 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
3229 - Create unit tests for format_time_interval(). With bug 13393.
3230 - Add unit tests for tor_timegm signed overflow, tor_timegm and
3231 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
3232 tests (visible) fixes in bug 13476.
3233 - Add a "coverage-html" make target to generate HTML-visualized
3234 coverage results when building with --enable-coverage. (Requires
3235 lcov.) Patch from Kevin Murray.
3236 - Enable the backtrace handler (where supported) when running the
3238 - Revise all unit tests that used the legacy test_* macros to
3239 instead use the recommended tt_* macros. This patch was generated
3240 with coccinelle, to avoid manual errors. Closes ticket 13119.
3242 o Distribution (systemd):
3243 - systemd unit file: only allow tor to write to /var/lib/tor and
3244 /var/log/tor. The rest of the filesystem is accessible for reading
3245 only. Patch by intrigeri; resolves ticket 12751.
3246 - systemd unit file: ensure that the process and all its children
3247 can never gain new privileges. Patch by intrigeri; resolves
3249 - systemd unit file: set up /var/run/tor as writable for the Tor
3250 service. Patch by intrigeri; resolves ticket 13196.
3252 o Removed features (directory authorities):
3253 - Remove code that prevented authorities from listing Tor relays
3254 affected by CVE-2011-2769 as guards. These relays are already
3255 rejected altogether due to the minimum version requirement of
3256 0.2.3.16-alpha. Closes ticket 13152.
3257 - The "AuthDirRejectUnlisted" option no longer has any effect, as
3258 the fingerprints file (approved-routers) has been deprecated.
3259 - Directory authorities do not support being Naming dirauths anymore.
3260 The "NamingAuthoritativeDir" config option is now obsolete.
3261 - Directory authorities do not support giving out the BadDirectory
3263 - Directory authorities no longer advertise or support consensus
3264 methods 1 through 12 inclusive. These consensus methods were
3265 obsolete and/or insecure: maintaining the ability to support them
3266 served no good purpose. Implements part of proposal 215; closes
3269 o Testing (test-network.sh):
3270 - Stop using "echo -n", as some shells' built-in echo doesn't
3271 support "-n". Instead, use "/bin/echo -n". Partially fixes
3273 - Stop an apparent test-network hang when used with make -j2. Fixes
3275 - Add a --delay option to test-network.sh, which configures the
3276 delay before the chutney network tests for data transmission.
3277 Partially implements ticket 13161.
3280 Changes in version 0.2.5.10 - 2014-10-24
3281 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
3283 It adds several new security features, including improved
3284 denial-of-service resistance for relays, new compiler hardening
3285 options, and a system-call sandbox for hardened installations on Linux
3286 (requires seccomp2). The controller protocol has several new features,
3287 resolving IPv6 addresses should work better than before, and relays
3288 should be a little more CPU-efficient. We've added support for more
3289 OpenBSD and FreeBSD transparent proxy types. We've improved the build
3290 system and testing infrastructure to allow unit testing of more parts
3291 of the Tor codebase. Finally, we've addressed several nagging pluggable
3292 transport usability issues, and included numerous other small bugfixes
3293 and features mentioned below.
3295 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
3296 have accumulated many known flaws; everyone should upgrade.
3298 o Deprecated versions:
3299 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
3300 attention for some while.
3303 Changes in version 0.2.5.9-rc - 2014-10-20
3304 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
3305 series. It disables SSL3 in response to the recent "POODLE" attack
3306 (even though POODLE does not affect Tor). It also works around a crash
3307 bug caused by some operating systems' response to the "POODLE" attack
3308 (which does affect Tor). It also contains a few miscellaneous fixes.
3310 o Major security fixes:
3311 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
3312 today support TLS 1.0 or later, so we can safely turn off support
3313 for this old (and insecure) protocol. Fixes bug 13426.
3315 o Major bugfixes (openssl bug workaround):
3316 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
3317 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
3318 13471. This is a workaround for an OpenSSL bug.
3321 - Disable the sandbox name resolver cache when running tor-resolve:
3322 tor-resolve doesn't use the sandbox code, and turning it on was
3323 breaking attempts to do tor-resolve on a non-default server on
3324 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
3326 o Compilation fixes:
3327 - Build and run correctly on systems like OpenBSD-current that have
3328 patched OpenSSL to remove get_cipher_by_char and/or its
3329 implementations. Fixes issue 13325.
3331 o Downgraded warnings:
3332 - Downgrade the severity of the 'unexpected sendme cell from client'
3333 from 'warn' to 'protocol warning'. Closes ticket 8093.
3336 Changes in version 0.2.4.25 - 2014-10-20
3337 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
3338 (even though POODLE does not affect Tor). It also works around a crash
3339 bug caused by some operating systems' response to the "POODLE" attack
3340 (which does affect Tor).
3342 o Major security fixes (also in 0.2.5.9-rc):
3343 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
3344 today support TLS 1.0 or later, so we can safely turn off support
3345 for this old (and insecure) protocol. Fixes bug 13426.
3347 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
3348 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
3349 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
3350 13471. This is a workaround for an OpenSSL bug.
3353 Changes in version 0.2.5.8-rc - 2014-09-22
3354 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
3355 series. It fixes a bug that affects consistency and speed when
3356 connecting to hidden services, and it updates the location of one of
3357 the directory authorities.
3360 - Clients now send the correct address for their chosen rendezvous
3361 point when trying to access a hidden service. They used to send
3362 the wrong address, which would still work some of the time because
3363 they also sent the identity digest of the rendezvous point, and if
3364 the hidden service happened to try connecting to the rendezvous
3365 point from a relay that already had a connection open to it,
3366 the relay would reuse that connection. Now connections to hidden
3367 services should be more robust and faster. Also, this bug meant
3368 that clients were leaking to the hidden service whether they were
3369 on a little-endian (common) or big-endian (rare) system, which for
3370 some users might have reduced their anonymity. Fixes bug 13151;
3371 bugfix on 0.2.1.5-alpha.
3373 o Directory authority changes:
3374 - Change IP address for gabelmoo (v3 directory authority).
3377 Changes in version 0.2.4.24 - 2014-09-22
3378 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
3379 connecting to hidden services, and it updates the location of one of
3380 the directory authorities.
3383 - Clients now send the correct address for their chosen rendezvous
3384 point when trying to access a hidden service. They used to send
3385 the wrong address, which would still work some of the time because
3386 they also sent the identity digest of the rendezvous point, and if
3387 the hidden service happened to try connecting to the rendezvous
3388 point from a relay that already had a connection open to it,
3389 the relay would reuse that connection. Now connections to hidden
3390 services should be more robust and faster. Also, this bug meant
3391 that clients were leaking to the hidden service whether they were
3392 on a little-endian (common) or big-endian (rare) system, which for
3393 some users might have reduced their anonymity. Fixes bug 13151;
3394 bugfix on 0.2.1.5-alpha.
3396 o Directory authority changes:
3397 - Change IP address for gabelmoo (v3 directory authority).
3399 o Minor features (geoip):
3400 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3404 Changes in version 0.2.5.7-rc - 2014-09-11
3405 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
3406 release series, and some long-standing bugs related to ORPort reachability
3407 testing and failure to send CREATE cells. It is the first release
3408 candidate for the Tor 0.2.5.x series.
3410 o Major bugfixes (client, startup):
3411 - Start making circuits as soon as DisabledNetwork is turned off.
3412 When Tor started with DisabledNetwork set, it would correctly
3413 conclude that it shouldn't build circuits, but it would mistakenly
3414 cache this conclusion, and continue believing it even when
3415 DisableNetwork is set to 0. Fixes the bug introduced by the fix
3416 for bug 11200; bugfix on 0.2.5.4-alpha.
3417 - Resume expanding abbreviations for command-line options. The fix
3418 for bug 4647 accidentally removed our hack from bug 586 that
3419 rewrote HashedControlPassword to __HashedControlSessionPassword
3420 when it appears on the commandline (which allowed the user to set
3421 her own HashedControlPassword in the torrc file while the
3422 controller generates a fresh session password for each run). Fixes
3423 bug 12948; bugfix on 0.2.5.1-alpha.
3424 - Warn about attempts to run hidden services and relays in the same
3425 process: that's probably not a good idea. Closes ticket 12908.
3427 o Major bugfixes (relay):
3428 - Avoid queuing or sending destroy cells for circuit ID zero when we
3429 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
3430 Found and fixed by "cypherpunks".
3431 - Fix ORPort reachability detection on relays running behind a
3432 proxy, by correctly updating the "local" mark on the controlling
3433 channel when changing the address of an or_connection_t after the
3434 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
3436 o Minor features (bridge):
3437 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
3438 cookie file for the ExtORPort g+r by default.
3440 o Minor features (geoip):
3441 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3444 o Minor bugfixes (logging):
3445 - Reduce the log severity of the "Pluggable transport proxy does not
3446 provide any needed transports and will not be launched." message,
3447 since Tor Browser includes several ClientTransportPlugin lines in
3448 its torrc-defaults file, leading every Tor Browser user who looks
3449 at her logs to see these notices and wonder if they're dangerous.
3450 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
3451 - Downgrade "Unexpected onionskin length after decryption" warning
3452 to a protocol-warn, since there's nothing relay operators can do
3453 about a client that sends them a malformed create cell. Resolves
3454 bug 12996; bugfix on 0.0.6rc1.
3455 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
3456 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
3457 - When logging information about an EXTEND2 or EXTENDED2 cell, log
3458 their names correctly. Fixes part of bug 12700; bugfix
3460 - When logging information about a relay cell whose command we don't
3461 recognize, log its command as an integer. Fixes part of bug 12700;
3462 bugfix on 0.2.1.10-alpha.
3463 - Escape all strings from the directory connection before logging
3464 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
3466 o Minor bugfixes (controller):
3467 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
3468 bug 12864; bugfix on 0.2.5.1-alpha.
3469 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
3470 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
3473 o Minor bugfixes (compilation):
3474 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
3475 bugfix on 0.2.5.5-alpha.
3476 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
3477 0.2.5.1-alpha. Patch from "NewEraCracker".
3478 - In routerlist_assert_ok(), don't take the address of a
3479 routerinfo's cache_info member unless that routerinfo is non-NULL.
3480 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
3481 - Fix a large number of false positive warnings from the clang
3482 analyzer static analysis tool. This should make real warnings
3483 easier for clang analyzer to find. Patch from "teor". Closes
3486 o Distribution (systemd):
3487 - Verify configuration file via ExecStartPre in the systemd unit
3488 file. Patch from intrigeri; resolves ticket 12730.
3489 - Explicitly disable RunAsDaemon in the systemd unit file. Our
3490 current systemd unit uses "Type = simple", so systemd does not
3491 expect tor to fork. If the user has "RunAsDaemon 1" in their
3492 torrc, then things won't work as expected. This is e.g. the case
3493 on Debian (and derivatives), since there we pass "--defaults-torrc
3494 /usr/share/tor/tor-service-defaults-torrc" (that contains
3495 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
3499 - Adjust the URLs in the README to refer to the new locations of
3500 several documents on the website. Fixes bug 12830. Patch from
3502 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
3506 Changes in version 0.2.5.6-alpha - 2014-07-28
3507 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
3508 risk from guard rotation, and fixes a variety of other issues to get
3509 us closer to a release candidate.
3511 o Major features (also in 0.2.4.23):
3512 - Make the number of entry guards configurable via a new
3513 NumEntryGuards consensus parameter, and the number of directory
3514 guards configurable via a new NumDirectoryGuards consensus
3515 parameter. Implements ticket 12688.
3517 o Major bugfixes (also in 0.2.4.23):
3518 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3519 implementation that caused incorrect results on 32-bit
3520 implementations when certain malformed inputs were used along with
3521 a small class of private ntor keys. This bug does not currently
3522 appear to allow an attacker to learn private keys or impersonate a
3523 Tor server, but it could provide a means to distinguish 32-bit Tor
3524 implementations from 64-bit Tor implementations. Fixes bug 12694;
3525 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3529 - Perform circuit cleanup operations even when circuit
3530 construction operations are disabled (because the network is
3531 disabled, or because there isn't enough directory information).
3532 Previously, when we were not building predictive circuits, we
3533 were not closing expired circuits either. Fixes bug 8387; bugfix on
3534 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
3535 became more strict about when we have "enough directory information
3539 - Authorities now assign the Guard flag to the fastest 25% of the
3540 network (it used to be the fastest 50%). Also raise the consensus
3541 weight that guarantees the Guard flag from 250 to 2000. For the
3542 current network, this results in about 1100 guards, down from 2500.
3543 This step paves the way for moving the number of entry guards
3544 down to 1 (proposal 236) while still providing reasonable expected
3545 performance for most users. Implements ticket 12690.
3546 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3548 - Slightly enhance the diagnostic message for bug 12184.
3550 o Minor bugfixes (also in 0.2.4.23):
3551 - Warn and drop the circuit if we receive an inbound 'relay early'
3552 cell. Those used to be normal to receive on hidden service circuits
3553 due to bug 1038, but the buggy Tor versions are long gone from
3554 the network so we can afford to resume watching for them. Resolves
3555 the rest of bug 1038; bugfix on 0.2.1.19.
3556 - Correct a confusing error message when trying to extend a circuit
3557 via the control protocol but we don't know a descriptor or
3558 microdescriptor for one of the specified relays. Fixes bug 12718;
3559 bugfix on 0.2.3.1-alpha.
3562 - Fix compilation when building with bufferevents enabled. (This
3563 configuration is still not expected to work, however.)
3564 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
3565 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
3567 - Compile correctly with builds and forks of OpenSSL (such as
3568 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
3569 0.2.1.1-alpha. Patch from "dhill".
3572 Changes in version 0.2.4.23 - 2014-07-28
3573 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
3574 guard rotation, and also backports several important fixes from the
3575 Tor 0.2.5 alpha release series.
3578 - Clients now look at the "usecreatefast" consensus parameter to
3579 decide whether to use CREATE_FAST or CREATE cells for the first hop
3580 of their circuit. This approach can improve security on connections
3581 where Tor's circuit handshake is stronger than the available TLS
3582 connection security levels, but the tradeoff is more computational
3583 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3584 - Make the number of entry guards configurable via a new
3585 NumEntryGuards consensus parameter, and the number of directory
3586 guards configurable via a new NumDirectoryGuards consensus
3587 parameter. Implements ticket 12688.
3590 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3591 implementation that caused incorrect results on 32-bit
3592 implementations when certain malformed inputs were used along with
3593 a small class of private ntor keys. This bug does not currently
3594 appear to allow an attacker to learn private keys or impersonate a
3595 Tor server, but it could provide a means to distinguish 32-bit Tor
3596 implementations from 64-bit Tor implementations. Fixes bug 12694;
3597 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3601 - Warn and drop the circuit if we receive an inbound 'relay early'
3602 cell. Those used to be normal to receive on hidden service circuits
3603 due to bug 1038, but the buggy Tor versions are long gone from
3604 the network so we can afford to resume watching for them. Resolves
3605 the rest of bug 1038; bugfix on 0.2.1.19.
3606 - Correct a confusing error message when trying to extend a circuit
3607 via the control protocol but we don't know a descriptor or
3608 microdescriptor for one of the specified relays. Fixes bug 12718;
3609 bugfix on 0.2.3.1-alpha.
3610 - Avoid an illegal read from stack when initializing the TLS
3611 module using a version of OpenSSL without all of the ciphers
3612 used by the v2 link handshake. Fixes bug 12227; bugfix on
3613 0.2.4.8-alpha. Found by "starlight".
3616 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3620 Changes in version 0.2.5.5-alpha - 2014-06-18
3621 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
3622 0.2.5.x release series, including a couple of DoS issues, some
3623 performance regressions, a large number of bugs affecting the Linux
3624 seccomp2 sandbox code, and various other bugfixes. It also adds
3625 diagnostic bugfixes for a few tricky issues that we're trying to
3628 o Major features (security, traffic analysis resistance):
3629 - Several major improvements to the algorithm used to decide when to
3630 close TLS connections. Previous versions of Tor closed connections
3631 at a fixed interval after the last time a non-padding cell was
3632 sent over the connection, regardless of the target of the
3633 connection. Now, we randomize the intervals by adding up to 50% of
3634 their base value, we measure the length of time since connection
3635 last had at least one circuit, and we allow connections to known
3636 ORs to remain open a little longer (15 minutes instead of 3
3637 minutes minimum). These changes should improve Tor's resistance
3638 against some kinds of traffic analysis, and lower some overhead
3639 from needlessly closed connections. Fixes ticket 6799.
3640 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
3642 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
3643 - Fix a memory leak that could occur if a microdescriptor parse
3644 fails during the tokenizing step. This bug could enable a memory
3645 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3648 o Major bugfixes (security, directory authorities):
3649 - Directory authorities now include a digest of each relay's
3650 identity key as a part of its microdescriptor.
3652 This is a workaround for bug 11743 (reported by "cypherpunks"),
3653 where Tor clients do not support receiving multiple
3654 microdescriptors with the same SHA256 digest in the same
3655 consensus. When clients receive a consensus like this, they only
3656 use one of the relays. Without this fix, a hostile relay could
3657 selectively disable some client use of target relays by
3658 constructing a router descriptor with a different identity and the
3659 same microdescriptor parameters and getting the authorities to
3660 list it in a microdescriptor consensus. This fix prevents an
3661 attacker from causing a microdescriptor collision, because the
3662 router's identity is not forgeable.
3664 o Major bugfixes (relay):
3665 - Use a direct dirport connection when uploading non-anonymous
3666 descriptors to the directory authorities. Previously, relays would
3667 incorrectly use tunnel connections under a fairly wide variety of
3668 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
3669 - When a circuit accidentally has the same circuit ID for its
3670 forward and reverse direction, correctly detect the direction of
3671 cells using that circuit. Previously, this bug made roughly one
3672 circuit in a million non-functional. Fixes bug 12195; this is a
3673 bugfix on every version of Tor.
3675 o Major bugfixes (client, pluggable transports):
3676 - When managing pluggable transports, use OS notification facilities
3677 to learn if they have crashed, and don't attempt to kill any
3678 process that has already exited. Fixes bug 8746; bugfix
3681 o Minor features (diagnostic):
3682 - When logging a warning because of bug 7164, additionally check the
3683 hash table for consistency (as proposed on ticket 11737). This may
3684 help diagnose bug 7164.
3685 - When we log a heartbeat, log how many one-hop circuits we have
3686 that are at least 30 minutes old, and log status information about
3687 a few of them. This is an attempt to track down bug 8387.
3688 - When encountering an unexpected CR while writing text to a file on
3689 Windows, log the name of the file. Should help diagnosing
3691 - Give more specific warnings when a client notices that an onion
3692 handshake has failed. Fixes ticket 9635.
3693 - Add significant new logging code to attempt to diagnose bug 12184,
3694 where relays seem to run out of available circuit IDs.
3695 - Improve the diagnostic log message for bug 8387 even further to
3696 try to improve our odds of figuring out why one-hop directory
3697 circuits sometimes do not get closed.
3699 o Minor features (security, memory management):
3700 - Memory allocation tricks (mempools and buffer freelists) are now
3701 disabled by default. You can turn them back on with
3702 --enable-mempools and --enable-buf-freelists respectively. We're
3703 disabling these features because malloc performance is good enough
3704 on most platforms, and a similar feature in OpenSSL exacerbated
3705 exploitation of the Heartbleed attack. Resolves ticket 11476.
3707 o Minor features (security):
3708 - Apply the secure SipHash-2-4 function to the hash table mapping
3709 circuit IDs and channels to circuits. We missed this one when we
3710 were converting all the other hash functions to use SipHash back
3711 in 0.2.5.3-alpha. Resolves ticket 11750.
3713 o Minor features (build):
3714 - The configure script has a --disable-seccomp option to turn off
3715 support for libseccomp on systems that have it, in case it (or
3716 Tor's use of it) is broken. Resolves ticket 11628.
3718 o Minor features (other):
3719 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
3722 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
3723 - When running a hidden service, do not allow TunneledDirConns 0;
3724 this will keep the hidden service from running, and also
3725 make it publish its descriptors directly over HTTP. Fixes bug 10849;
3726 bugfix on 0.2.1.1-alpha.
3728 o Minor bugfixes (performance):
3729 - Avoid a bug where every successful connection made us recompute
3730 the flag telling us whether we have sufficient information to
3731 build circuits. Previously, we would forget our cached value
3732 whenever we successfully opened a channel (or marked a router as
3733 running or not running for any other reason), regardless of
3734 whether we had previously believed the router to be running. This
3735 forced us to run an expensive update operation far too often.
3736 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
3737 - Avoid using tor_memeq() for checking relay cell integrity. This
3738 removes a possible performance bottleneck. Fixes part of bug
3739 12169; bugfix on 0.2.1.31.
3741 o Minor bugfixes (compilation):
3742 - Fix compilation of test_status.c when building with MVSC. Bugfix
3743 on 0.2.5.4-alpha. Patch from Gisle Vanem.
3744 - Resolve GCC complaints on OpenBSD about discarding constness in
3745 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
3746 on 0.1.1.23. Patch from Dana Koch.
3747 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
3748 treatment of long and time_t as comparable types. Fixes part of
3749 bug 11633. Patch from Dana Koch.
3750 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
3751 11623; bugfix on 0.2.5.3-alpha.
3752 - When deciding whether to build the 64-bit curve25519
3753 implementation, detect platforms where we can compile 128-bit
3754 arithmetic but cannot link it. Fixes bug 11729; bugfix on
3755 0.2.4.8-alpha. Patch from "conradev".
3756 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
3757 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
3758 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
3761 o Minor bugfixes (Directory server):
3762 - When sending a compressed set of descriptors or microdescriptors,
3763 make sure to finalize the zlib stream. Previously, we would write
3764 all the compressed data, but if the last descriptor we wanted to
3765 send was missing or too old, we would not mark the stream as
3766 finished. This caused problems for decompression tools. Fixes bug
3767 11648; bugfix on 0.1.1.23.
3769 o Minor bugfixes (Linux seccomp sandbox):
3770 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
3771 11622; bugfix on 0.2.5.1-alpha.
3772 - Avoid crashing when re-opening listener ports with the seccomp
3773 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
3774 - Avoid crashing with the seccomp sandbox enabled along with
3775 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
3776 - When we receive a SIGHUP with the sandbox enabled, correctly
3777 support rotating our log files. Fixes bug 12032; bugfix
3779 - Avoid crash when running with sandboxing enabled and
3780 DirReqStatistics not disabled. Fixes bug 12035; bugfix
3782 - Fix a "BUG" warning when trying to write bridge-stats files with
3783 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
3785 - Prevent the sandbox from crashing on startup when run with the
3786 --enable-expensive-hardening configuration option. Fixes bug
3787 11477; bugfix on 0.2.5.4-alpha.
3788 - When running with DirPortFrontPage and sandboxing both enabled,
3789 reload the DirPortFrontPage correctly when restarting. Fixes bug
3790 12028; bugfix on 0.2.5.1-alpha.
3791 - Don't try to enable the sandbox when using the Tor binary to check
3792 its configuration, hash a passphrase, or so on. Doing so was
3793 crashing on startup for some users. Fixes bug 11609; bugfix
3795 - Avoid warnings when running with sandboxing and node statistics
3796 enabled at the same time. Fixes part of 12064; bugfix on
3797 0.2.5.1-alpha. Patch from Michael Wolf.
3798 - Avoid warnings when running with sandboxing enabled at the same
3799 time as cookie authentication, hidden services, or directory
3800 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
3801 - Do not allow options that require calls to exec to be enabled
3802 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
3803 bug 12043; bugfix on 0.2.5.1-alpha.
3804 - Handle failures in getpwnam()/getpwuid() when running with the
3805 User option set and the Linux syscall sandbox enabled. Fixes bug
3806 11946; bugfix on 0.2.5.1-alpha.
3807 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
3808 to avoid calling getaddrinfo() after installing the sandbox
3809 filters. Previously, it preloaded a cache with the IPv4 address
3810 for our hostname, and nothing else. Now, it loads the cache with
3811 every address that it used to initialize the Tor process. Fixes
3812 bug 11970; bugfix on 0.2.5.1-alpha.
3814 o Minor bugfixes (pluggable transports):
3815 - Enable the ExtORPortCookieAuthFile option, to allow changing the
3816 default location of the authentication token for the extended OR
3817 Port as used by sever-side pluggable transports. We had
3818 implemented this option before, but the code to make it settable
3819 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
3820 - Avoid another 60-second delay when starting Tor in a pluggable-
3821 transport-using configuration when we already have cached
3822 descriptors for our bridges. Fixes bug 11965; bugfix
3825 o Minor bugfixes (client):
3826 - Avoid "Tried to open a socket with DisableNetwork set" warnings
3827 when starting a client with bridges configured and DisableNetwork
3828 set. (Tor launcher starts Tor with DisableNetwork set the first
3829 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
3831 o Minor bugfixes (testing):
3832 - The Python parts of the test scripts now work on Python 3 as well
3833 as Python 2, so systems where '/usr/bin/python' is Python 3 will
3834 no longer have the tests break. Fixes bug 11608; bugfix
3836 - When looking for versions of python that we could run the tests
3837 with, check for "python2.7" and "python3.3"; previously we were
3838 only looking for "python", "python2", and "python3". Patch from
3839 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
3840 - Fix all valgrind warnings produced by the unit tests. There were
3841 over a thousand memory leak warnings previously, mostly produced
3842 by forgetting to free things in the unit test code. Fixes bug
3843 11618, bugfixes on many versions of Tor.
3845 o Minor bugfixes (tor-fw-helper):
3846 - Give a correct log message when tor-fw-helper fails to launch.
3847 (Previously, we would say something like "tor-fw-helper sent us a
3848 string we could not parse".) Fixes bug 9781; bugfix
3851 o Minor bugfixes (relay, threading):
3852 - Check return code on spawn_func() in cpuworker code, so that we
3853 don't think we've spawned a nonworking cpuworker and write junk to
3854 it forever. Fix related to bug 4345; bugfix on all released Tor
3855 versions. Found by "skruffy".
3856 - Use a pthread_attr to make sure that spawn_func() cannot return an
3857 error while at the same time launching a thread. Fix related to
3858 bug 4345; bugfix on all released Tor versions. Reported
3861 o Minor bugfixes (relay, oom prevention):
3862 - Correctly detect the total available system memory. We tried to do
3863 this in 0.2.5.4-alpha, but the code was set up to always return an
3864 error value, even on success. Fixes bug 11805; bugfix
3867 o Minor bugfixes (relay, other):
3868 - We now drop CREATE cells for already-existent circuit IDs and for
3869 zero-valued circuit IDs, regardless of other factors that might
3870 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
3872 - Avoid an illegal read from stack when initializing the TLS module
3873 using a version of OpenSSL without all of the ciphers used by the
3874 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
3876 - When rejecting DATA cells for stream_id zero, still count them
3877 against the circuit's deliver window so that we don't fail to send
3878 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
3880 o Minor bugfixes (logging):
3881 - Fix a misformatted log message about delayed directory fetches.
3882 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
3883 - Squelch a spurious LD_BUG message "No origin circuit for
3884 successful SOCKS stream" in certain hidden service failure cases;
3888 - Include a tor.service file in contrib/dist for use with systemd.
3889 Some distributions will be able to use this file unmodified;
3890 others will need to tweak it, or write their own. Patch from Jamie
3891 Nguyen; resolves ticket 8368.
3894 - Clean up several option names in the manpage to match their real
3895 names, add the missing documentation for a couple of testing and
3896 directory authority options, remove the documentation for a
3897 V2-directory fetching option that no longer exists. Resolves
3899 - Correct the documenation so that it lists the correct directory
3900 for the stats files. (They are in a subdirectory called "stats",
3902 - In the manpage, move more authority-only options into the
3903 directory authority section so that operators of regular directory
3904 caches don't get confused.
3907 - The contrib directory has been sorted and tidied. Before, it was
3908 an unsorted dumping ground for useful and not-so-useful things.
3909 Now, it is divided based on functionality, and the items which
3910 seemed to be nonfunctional or useless have been removed. Resolves
3911 ticket 8966; based on patches from "rl1987".
3914 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
3915 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
3916 - The TunnelDirConns and PreferTunnelledDirConns options no longer
3917 exist; tunneled directory connections have been available since
3918 0.1.2.5-alpha, and turning them off is not a good idea. This is a
3919 brute-force fix for 10849, where "TunnelDirConns 0" would break
3923 Changes in version 0.2.4.22 - 2014-05-16
3924 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
3925 alpha release series. These include blocking all authority signing
3926 keys that may have been affected by the OpenSSL "heartbleed" bug,
3927 choosing a far more secure set of TLS ciphersuites by default, closing
3928 a couple of memory leaks that could be used to run a target relay out
3929 of RAM, and several others.
3931 o Major features (security, backport from 0.2.5.4-alpha):
3932 - Block authority signing keys that were used on authorities
3933 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3934 don't have any evidence that these keys _were_ compromised; we're
3935 doing this to be prudent.) Resolves ticket 11464.
3937 o Major bugfixes (security, OOM):
3938 - Fix a memory leak that could occur if a microdescriptor parse
3939 fails during the tokenizing step. This bug could enable a memory
3940 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3943 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
3944 - The relay ciphersuite list is now generated automatically based on
3945 uniform criteria, and includes all OpenSSL ciphersuites with
3946 acceptable strength and forward secrecy. Previously, we had left
3947 some perfectly fine ciphersuites unsupported due to omission or
3948 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3949 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3950 - Relays now trust themselves to have a better view than clients of
3951 which TLS ciphersuites are better than others. (Thanks to bug
3952 11513, the relay list is now well-considered, whereas the client
3953 list has been chosen mainly for anti-fingerprinting purposes.)
3954 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3955 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3956 AES128. Resolves ticket 11528.
3957 - Clients now try to advertise the same list of ciphersuites as
3958 Firefox 28. This change enables selection of (fast) GCM
3959 ciphersuites, disables some strange old ciphers, and stops
3960 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3961 Resolves ticket 11438.
3963 o Minor bugfixes (configuration, security):
3964 - When running a hidden service, do not allow TunneledDirConns 0:
3965 trying to set that option together with a hidden service would
3966 otherwise prevent the hidden service from running, and also make
3967 it publish its descriptors directly over HTTP. Fixes bug 10849;
3968 bugfix on 0.2.1.1-alpha.
3970 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
3971 - Avoid sending a garbage value to the controller when a circuit is
3972 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3974 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
3975 - Stop leaking memory when we successfully resolve a PTR record.
3976 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3978 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
3979 - Avoid 60-second delays in the bootstrapping process when Tor is
3980 launching for a second time while using bridges. Fixes bug 9229;
3981 bugfix on 0.2.0.3-alpha.
3983 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
3984 - Give the correct URL in the warning message when trying to run a
3985 relay on an ancient version of Windows. Fixes bug 9393.
3987 o Minor bugfixes (compilation):
3988 - Fix a compilation error when compiling with --disable-curve25519.
3989 Fixes bug 9700; bugfix on 0.2.4.17-rc.
3992 - Downgrade the warning severity for the the "md was still
3993 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
3994 for trying to diagnose this bug, and the current warning in
3995 earlier versions of tor achieves nothing useful. Addresses warning
3998 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
3999 - When we run out of usable circuit IDs on a channel, log only one
4000 warning for the whole channel, and describe how many circuits
4001 there were on the channel. Fixes part of ticket 11553.
4003 o Minor features (security, backport from 0.2.5.4-alpha):
4004 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
4005 leave the default at 8GBytes), to better support Raspberry Pi
4006 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
4008 o Documentation (backport from 0.2.5.4-alpha):
4009 - Correctly document that we search for a system torrc file before
4010 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
4014 Changes in version 0.2.5.4-alpha - 2014-04-25
4015 Tor 0.2.5.4-alpha includes several security and performance
4016 improvements for clients and relays, including blacklisting authority
4017 signing keys that were used while susceptible to the OpenSSL
4018 "heartbleed" bug, fixing two expensive functions on busy relays,
4019 improved TLS ciphersuite preference lists, support for run-time
4020 hardening on compilers that support AddressSanitizer, and more work on
4021 the Linux sandbox code.
4023 There are also several usability fixes for clients (especially clients
4024 that use bridges), two new TransPort protocols supported (one on
4025 OpenBSD, one on FreeBSD), and various other bugfixes.
4027 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
4028 have accumulated many known flaws; everyone should upgrade.
4030 o Major features (security):
4031 - If you don't specify MaxMemInQueues yourself, Tor now tries to
4032 pick a good value based on your total system memory. Previously,
4033 the default was always 8 GB. You can still override the default by
4034 setting MaxMemInQueues yourself. Resolves ticket 11396.
4035 - Block authority signing keys that were used on authorities
4036 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
4037 don't have any evidence that these keys _were_ compromised; we're
4038 doing this to be prudent.) Resolves ticket 11464.
4040 o Major features (relay performance):
4041 - Speed up server-side lookups of rendezvous and introduction point
4042 circuits by using hashtables instead of linear searches. These
4043 functions previously accounted between 3 and 7% of CPU usage on
4044 some busy relays. Resolves ticket 9841.
4045 - Avoid wasting CPU when extending a circuit over a channel that is
4046 nearly out of circuit IDs. Previously, we would do a linear scan
4047 over possible circuit IDs before finding one or deciding that we
4048 had exhausted our possibilities. Now, we try at most 64 random
4049 circuit IDs before deciding that we probably won't succeed. Fixes
4050 a possible root cause of ticket 11553.
4052 o Major features (seccomp2 sandbox, Linux only):
4053 - The seccomp2 sandbox can now run a test network for multiple hours
4054 without crashing. The sandbox is still experimental, and more bugs
4055 will probably turn up. To try it, enable "Sandbox 1" on a Linux
4056 host. Resolves ticket 11351.
4057 - Strengthen sandbox code: the sandbox can now test the arguments
4058 for rename(), and blocks _sysctl() entirely. Resolves another part
4060 - When the sandbox blocks a system call, it now tries to log a stack
4061 trace before exiting. Resolves ticket 11465.
4063 o Major bugfixes (TLS cipher selection):
4064 - The relay ciphersuite list is now generated automatically based on
4065 uniform criteria, and includes all OpenSSL ciphersuites with
4066 acceptable strength and forward secrecy. Previously, we had left
4067 some perfectly fine ciphersuites unsupported due to omission or
4068 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
4069 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
4070 - Relays now trust themselves to have a better view than clients of
4071 which TLS ciphersuites are better than others. (Thanks to bug
4072 11513, the relay list is now well-considered, whereas the client
4073 list has been chosen mainly for anti-fingerprinting purposes.)
4074 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
4075 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
4076 AES128. Resolves ticket 11528.
4077 - Clients now try to advertise the same list of ciphersuites as
4078 Firefox 28. This change enables selection of (fast) GCM
4079 ciphersuites, disables some strange old ciphers, and stops
4080 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
4081 Resolves ticket 11438.
4083 o Major bugfixes (bridge client):
4084 - Avoid 60-second delays in the bootstrapping process when Tor is
4085 launching for a second time while using bridges. Fixes bug 9229;
4086 bugfix on 0.2.0.3-alpha.
4088 o Minor features (transparent proxy, *BSD):
4089 - Support FreeBSD's ipfw firewall interface for TransPort ports on
4090 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
4091 10267; patch from "yurivict".
4092 - Support OpenBSD's divert-to rules with the pf firewall for
4093 transparent proxy ports. To enable it, set "TransProxyType
4094 pf-divert". This allows Tor to run a TransPort transparent proxy
4095 port on OpenBSD 4.4 or later without root privileges. See the
4096 pf.conf(5) manual page for information on configuring pf to use
4097 divert-to rules. Closes ticket 10896; patch from Dana Koch.
4099 o Minor features (security):
4100 - New --enable-expensive-hardening option to enable security
4101 hardening options that consume nontrivial amounts of CPU and
4102 memory. Right now, this includes AddressSanitizer and UbSan, which
4103 are supported in newer versions of GCC and Clang. Closes ticket
4106 o Minor features (log verbosity):
4107 - Demote the message that we give when a flushing connection times
4108 out for too long from NOTICE to INFO. It was usually meaningless.
4109 Resolves ticket 5286.
4110 - Don't log so many notice-level bootstrapping messages at startup
4111 about downloading descriptors. Previously, we'd log a notice
4112 whenever we learned about more routers. Now, we only log a notice
4113 at every 5% of progress. Fixes bug 9963.
4114 - Warn less verbosely when receiving a malformed
4115 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
4116 - When we run out of usable circuit IDs on a channel, log only one
4117 warning for the whole channel, and describe how many circuits
4118 there were on the channel. Fixes part of ticket 11553.
4120 o Minor features (relay):
4121 - If a circuit timed out for at least 3 minutes, check if we have a
4122 new external IP address, and publish a new descriptor with the new
4123 IP address if it changed. Resolves ticket 2454.
4125 o Minor features (controller):
4126 - Make the entire exit policy available from the control port via
4127 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
4129 - Because of the fix for ticket 11396, the real limit for memory
4130 usage may no longer match the configured MaxMemInQueues value. The
4131 real limit is now exposed via GETINFO limits/max-mem-in-queues.
4133 o Minor features (bridge client):
4134 - Report a more useful failure message when we can't connect to a
4135 bridge because we don't have the right pluggable transport
4136 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
4138 o Minor features (diagnostic):
4139 - Add more log messages to diagnose bug 7164, which causes
4140 intermittent "microdesc_free() called but md was still referenced"
4141 warnings. We now include more information, to figure out why we
4142 might be cleaning a microdescriptor for being too old if it's
4143 still referenced by a live node_t object.
4145 o Minor bugfixes (client, DNSPort):
4146 - When using DNSPort, try to respond to AAAA requests with AAAA
4147 answers. Previously, we hadn't looked at the request type when
4148 deciding which answer type to prefer. Fixes bug 10468; bugfix on
4150 - When receiving a DNS query for an unsupported record type, reply
4151 with no answer rather than with a NOTIMPL error. This behavior
4152 isn't correct either, but it will break fewer client programs, we
4153 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
4156 o Minor bugfixes (exit relay):
4157 - Stop leaking memory when we successfully resolve a PTR record.
4158 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
4160 o Minor bugfixes (bridge client):
4161 - Stop accepting bridge lines containing hostnames. Doing so would
4162 cause clients to perform DNS requests on the hostnames, which was
4163 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
4164 - Avoid a 60-second delay in the bootstrapping process when a Tor
4165 client with pluggable transports re-reads its configuration at
4166 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
4168 o Minor bugfixes (client, logging during bootstrap):
4169 - Warn only once if we start logging in an unsafe way. Previously,
4170 we complain as many times as we had problems. Fixes bug 9870;
4171 bugfix on 0.2.5.1-alpha.
4172 - Only report the first fatal bootstrap error on a given OR
4173 connection. This stops us from telling the controller bogus error
4174 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
4175 - Be more helpful when trying to run sandboxed on Linux without
4176 libseccomp. Instead of saying "Sandbox is not implemented on this
4177 platform", we now explain that we need to be built with
4178 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
4179 - Avoid generating spurious warnings when starting with
4180 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
4183 o Minor bugfixes (closing OR connections):
4184 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
4185 check if it's an or_connection_t and correctly call
4186 connection_or_close_for_error() rather than
4187 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
4189 - When closing all connections on setting DisableNetwork to 1, use
4190 connection_or_close_normally() rather than closing OR connections
4191 out from under the channel layer. Fixes bug 11306; bugfix on
4194 o Minor bugfixes (controller):
4195 - Avoid sending a garbage value to the controller when a circuit is
4196 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
4198 o Minor bugfixes (tor-fw-helper):
4199 - Allow tor-fw-helper to build again by adding src/ext to its
4200 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
4202 o Minor bugfixes (bridges):
4203 - Avoid potential crashes or bad behavior when launching a
4204 server-side managed proxy with ORPort or ExtORPort temporarily
4205 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
4207 o Minor bugfixes (platform-specific):
4208 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
4209 bug 11426; bugfix on 0.2.5.3-alpha.
4210 - When dumping a malformed directory object to disk, save it in
4211 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
4213 - Don't report failures from make_socket_reuseable() on incoming
4214 sockets on OSX: this can happen when incoming connections close
4215 early. Fixes bug 10081.
4217 o Minor bugfixes (trivial memory leaks):
4218 - Fix a small memory leak when signing a directory object. Fixes bug
4219 11275; bugfix on 0.2.4.13-alpha.
4220 - Free placeholder entries in our circuit table at exit; fixes a
4221 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
4222 - Don't re-initialize a second set of OpenSSL mutexes when starting
4223 up. Previously, we'd make one set of mutexes, and then immediately
4224 replace them with another. Fixes bug 11726; bugfix on
4226 - Resolve some memory leaks found by coverity in the unit tests, on
4227 exit in tor-gencert, and on a failure to compute digests for our
4228 own keys when generating a v3 networkstatus vote. These leaks
4229 should never have affected anyone in practice.
4231 o Minor bugfixes (hidden service):
4232 - Only retry attempts to connect to a chosen rendezvous point 8
4233 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
4235 o Minor bugfixes (misc code correctness):
4236 - Fix various instances of undefined behavior in channeltls.c,
4237 tor_memmem(), and eventdns.c that would cause us to construct
4238 pointers to memory outside an allocated object. (These invalid
4239 pointers were not accessed, but C does not even allow them to
4240 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
4241 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
4242 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
4243 fix some miscellaneous errors in our tests and codebase. Fixes bug
4244 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
4245 - Always check return values for unlink, munmap, UnmapViewOfFile;
4246 check strftime return values more often. In some cases all we can
4247 do is report a warning, but this may help prevent deeper bugs from
4248 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
4250 - Fix numerous warnings from the clang "scan-build" static analyzer.
4251 Some of these are programming style issues; some of them are false
4252 positives that indicated awkward code; some are undefined behavior
4253 cases related to constructing (but not using) invalid pointers;
4254 some are assumptions about API behavior; some are (harmlessly)
4255 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
4256 correct; and one or two are genuine bugs that weren't reachable
4257 from the rest of the program. Fixes bug 8793; bugfixes on many,
4261 - Build the torify.1 manpage again. Previously, we were only trying
4262 to build it when also building tor-fw-helper. That's why we didn't
4263 notice that we'd broken the ability to build it. Fixes bug 11321;
4264 bugfix on 0.2.5.1-alpha.
4265 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
4266 11061; bugfix on 0.2.4.7-alpha.
4267 - Correctly document that we search for a system torrc file before
4268 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
4270 - Resolve warnings from Doxygen.
4272 o Code simplifications and refactoring:
4273 - Remove is_internal_IP() function. Resolves ticket 4645.
4274 - Remove unused function circuit_dump_by_chan from circuitlist.c.
4275 Closes issue 9107; patch from "marek".
4276 - Change our use of the ENUM_BF macro to avoid declarations that
4279 o Deprecated versions:
4280 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
4281 attention for some while. Directory authorities no longer accept
4282 descriptors from relays running any version of Tor prior to Tor
4283 0.2.3.16-alpha. Resolves ticket 11149.
4286 - New macros in test.h to simplify writing mock-functions for unit
4287 tests. Part of ticket 11507. Patch from Dana Koch.
4288 - Complete tests for the status.c module. Resolves ticket 11507.
4289 Patch from Dana Koch.
4292 - Remove all code for the long unused v1 directory protocol.
4293 Resolves ticket 11070.
4296 Changes in version 0.2.5.3-alpha - 2014-03-22
4297 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
4298 two new anti-DoS features for Tor relays, resolves a bug that kept
4299 SOCKS5 support for IPv6 from working, fixes several annoying usability
4300 issues for bridge users, and removes more old code for unused
4303 The Tor 0.2.5.x release series is now in patch-freeze: no feature
4304 patches not already written will be considered for inclusion in 0.2.5.x.
4306 o Major features (relay security, DoS-resistance):
4307 - When deciding whether we have run out of memory and we need to
4308 close circuits, also consider memory allocated in buffers for
4309 streams attached to each circuit.
4311 This change, which extends an anti-DoS feature introduced in
4312 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
4313 better resist more memory-based DoS attacks than before. Since the
4314 MaxMemInCellQueues option now applies to all queues, it is renamed
4315 to MaxMemInQueues. This feature fixes bug 10169.
4316 - Avoid hash-flooding denial-of-service attacks by using the secure
4317 SipHash-2-4 hash function for our hashtables. Without this
4318 feature, an attacker could degrade performance of a targeted
4319 client or server by flooding their data structures with a large
4320 number of entries to be stored at the same hash table position,
4321 thereby slowing down the Tor instance. With this feature, hash
4322 table positions are derived from a randomized cryptographic key,
4323 and an attacker cannot predict which entries will collide. Closes
4325 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
4326 the default at 8GBytes), to better support Raspberry Pi users. Fixes
4327 bug 9686; bugfix on 0.2.4.14-alpha.
4329 o Minor features (bridges, pluggable transports):
4330 - Bridges now write the SHA1 digest of their identity key
4331 fingerprint (that is, a hash of a hash of their public key) to
4332 notice-level logs, and to a new hashed-fingerprint file. This
4333 information will help bridge operators look up their bridge in
4334 Globe and similar tools. Resolves ticket 10884.
4335 - Improve the message that Tor displays when running as a bridge
4336 using pluggable transports without an Extended ORPort listener.
4337 Also, log the message in the log file too. Resolves ticket 11043.
4339 o Minor features (other):
4340 - Add a new option, PredictedPortsRelevanceTime, to control how long
4341 after having received a request to connect to a given port Tor
4342 will try to keep circuits ready in anticipation of future requests
4343 for that port. Patch from "unixninja92"; implements ticket 9176.
4344 - Generate a warning if any ports are listed in the SocksPolicy,
4345 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
4346 AuthDirBadExit options. (These options only support address
4347 ranges.) Fixes part of ticket 11108.
4348 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
4351 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
4352 - Build without warnings under clang 3.4. (We have some macros that
4353 define static functions only some of which will get used later in
4354 the module. Starting with clang 3.4, these give a warning unless the
4355 unused attribute is set on them.) Resolves ticket 10904.
4356 - Fix build warnings about missing "a2x" comment when building the
4357 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
4358 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
4360 o Minor bugfixes (client):
4361 - Improve the log message when we can't connect to a hidden service
4362 because all of the hidden service directory nodes hosting its
4363 descriptor are excluded. Improves on our fix for bug 10722, which
4364 was a bugfix on 0.2.0.10-alpha.
4365 - Raise a control port warning when we fail to connect to all of
4366 our bridges. Previously, we didn't inform the controller, and
4367 the bootstrap process would stall. Fixes bug 11069; bugfix on
4369 - Exit immediately when a process-owning controller exits.
4370 Previously, tor relays would wait for a little while after their
4371 controller exited, as if they had gotten an INT signal -- but this
4372 was problematic, since there was no feedback for the user. To do a
4373 clean shutdown, controllers should send an INT signal and give Tor
4374 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
4375 - Stop attempting to connect to bridges before our pluggable
4376 transports are configured (harmless but resulted in some erroneous
4377 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
4378 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
4379 generating incorrect SOCKS5 responses, and confusing client
4380 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
4382 o Minor bugfixes (relays and bridges):
4383 - Avoid crashing on a malformed resolv.conf file when running a
4384 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
4385 - Non-exit relays no longer launch mock DNS requests to check for
4386 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
4387 non-exit relays stopped servicing DNS requests. Fixes bug 965;
4388 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
4389 - Bridges now report complete directory request statistics. Related
4390 to bug 5824; bugfix on 0.2.2.1-alpha.
4391 - Bridges now never collect statistics that were designed for
4392 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
4393 - Stop giving annoying warning messages when we decide not to launch
4394 a pluggable transport proxy that we don't need (because there are
4395 no bridges configured to use it). Resolves ticket 5018; bugfix
4397 - Give the correct URL in the warning message when trying to run a
4398 relay on an ancient version of Windows. Fixes bug 9393.
4400 o Minor bugfixes (backtrace support):
4401 - Support automatic backtraces on more platforms by using the
4402 "-fasynchronous-unwind-tables" compiler option. This option is
4403 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
4404 is on by default and table generation is not. This doesn't yet
4405 add Windows support; only Linux, OSX, and some BSDs are affected.
4406 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
4407 - Avoid strange behavior if two threads hit failed assertions at the
4408 same time and both try to log backtraces at once. (Previously, if
4409 this had happened, both threads would have stored their intermediate
4410 results in the same buffer, and generated junk outputs.) Reported by
4411 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
4412 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
4413 0.2.5.2-alpha; patch from Nick Hopper.
4415 o Minor bugfixes (unit tests):
4416 - Fix a small bug in the unit tests that might have made the tests
4417 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
4418 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
4421 - Remove all remaining code related to version-0 hidden service
4422 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
4423 the rest of bug 10841.
4426 - Document in the manpage that "KBytes" may also be written as
4427 "kilobytes" or "KB", that "Kbits" may also be written as
4428 "kilobits", and so forth. Closes ticket 9222.
4429 - Document that the ClientOnly config option overrides ORPort.
4430 Our old explanation made ClientOnly sound as though it did
4431 nothing at all. Resolves bug 9059.
4432 - Explain that SocksPolicy, DirPolicy, and similar options don't
4433 take port arguments. Fixes the other part of ticket 11108.
4434 - Fix a comment about the rend_server_descriptor_t.protocols field
4435 to more accurately describe its range. Also, make that field
4436 unsigned, to more accurately reflect its usage. Fixes bug 9099;
4437 bugfix on 0.2.1.5-alpha.
4438 - Fix the manpage's description of HiddenServiceAuthorizeClient:
4439 the maximum client name length is 16, not 19. Fixes bug 11118;
4440 bugfix on 0.2.1.6-alpha.
4442 o Code simplifications and refactoring:
4443 - Get rid of router->address, since in all cases it was just the
4444 string representation of router->addr. Resolves ticket 5528.
4446 o Test infrastructure:
4447 - Update to the latest version of tinytest.
4448 - Improve the tinytest implementation of string operation tests so
4449 that comparisons with NULL strings no longer crash the tests; they
4450 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
4453 Changes in version 0.2.4.21 - 2014-02-28
4454 Tor 0.2.4.21 further improves security against potential adversaries who
4455 find breaking 1024-bit crypto doable, and backports several stability
4456 and robustness patches from the 0.2.5 branch.
4458 o Major features (client security):
4459 - When we choose a path for a 3-hop circuit, make sure it contains
4460 at least one relay that supports the NTor circuit extension
4461 handshake. Otherwise, there is a chance that we're building
4462 a circuit that's worth attacking by an adversary who finds
4463 breaking 1024-bit crypto doable, and that chance changes the game
4464 theory. Implements ticket 9777.
4467 - Do not treat streams that fail with reason
4468 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4469 since it could also indicate an ENETUNREACH connection error. Fixes
4470 part of bug 10777; bugfix on 0.2.4.8-alpha.
4472 o Code simplification and refactoring:
4473 - Remove data structures which were introduced to implement the
4474 CellStatistics option: they are now redundant with the new timestamp
4475 field in the regular packed_cell_t data structure, which we did
4476 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
4479 - Always clear OpenSSL bignums before freeing them -- even bignums
4480 that don't contain secrets. Resolves ticket 10793. Patch by
4482 - Build without warnings under clang 3.4. (We have some macros that
4483 define static functions only some of which will get used later in
4484 the module. Starting with clang 3.4, these give a warning unless the
4485 unused attribute is set on them.) Resolves ticket 10904.
4486 - Update geoip and geoip6 files to the February 7 2014 Maxmind
4487 GeoLite2 Country database.
4490 - Set the listen() backlog limit to the largest actually supported
4491 on the system, not to the value in a header file. Fixes bug 9716;
4492 bugfix on every released Tor.
4493 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
4494 exit node as a NOROUTE error, not an INTERNAL error, since they
4495 can apparently happen when trying to connect to the wrong sort
4496 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
4497 - Fix build warnings about missing "a2x" comment when building the
4498 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
4499 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
4500 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4501 not entirely remove it from the connection lists. Fixes bug 9602;
4502 bugfix on 0.2.4.4-alpha.
4503 - Fix a segmentation fault in our benchmark code when running with
4504 Fedora's OpenSSL package, or any other OpenSSL that provides
4505 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
4506 - Turn "circuit handshake stats since last time" log messages into a
4507 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
4509 o Documentation fixes:
4510 - Document that all but one DirPort entry must have the NoAdvertise
4511 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
4514 Changes in version 0.2.5.2-alpha - 2014-02-13
4515 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
4516 like the "poor random number generation" fix and the "building too many
4517 circuits" fix. It also further improves security against potential
4518 adversaries who find breaking 1024-bit crypto doable, and launches
4519 pluggable transports on demand (which gets us closer to integrating
4520 pluggable transport support by default -- not to be confused with Tor
4521 bundles enabling pluggable transports and bridges by default).
4523 o Major features (client security):
4524 - When we choose a path for a 3-hop circuit, make sure it contains
4525 at least one relay that supports the NTor circuit extension
4526 handshake. Otherwise, there is a chance that we're building
4527 a circuit that's worth attacking by an adversary who finds
4528 breaking 1024-bit crypto doable, and that chance changes the game
4529 theory. Implements ticket 9777.
4530 - Clients now look at the "usecreatefast" consensus parameter to
4531 decide whether to use CREATE_FAST or CREATE cells for the first hop
4532 of their circuit. This approach can improve security on connections
4533 where Tor's circuit handshake is stronger than the available TLS
4534 connection security levels, but the tradeoff is more computational
4535 load on guard relays. Implements proposal 221. Resolves ticket 9386.
4537 o Major features (bridges):
4538 - Don't launch pluggable transport proxies if we don't have any
4539 bridges configured that would use them. Now we can list many
4540 pluggable transports, and Tor will dynamically start one when it
4541 hears a bridge address that needs it. Resolves ticket 5018.
4542 - The bridge directory authority now assigns status flags (Stable,
4543 Guard, etc) to bridges based on thresholds calculated over all
4544 Running bridges. Now bridgedb can finally make use of its features
4545 to e.g. include at least one Stable bridge in its answers. Fixes
4548 o Major features (other):
4549 - Extend ORCONN controller event to include an "ID" parameter,
4550 and add four new controller event types CONN_BW, CIRC_BW,
4551 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
4552 The new events are emitted in private Tor networks only, with the
4553 goal of being able to better track performance and load during
4554 full-network simulations. Implements proposal 218 and ticket 7359.
4555 - On some platforms (currently: recent OSX versions, glibc-based
4556 platforms that support the ELF format, and a few other
4557 Unix-like operating systems), Tor can now dump stack traces
4558 when a crash occurs or an assertion fails. By default, traces
4559 are dumped to stderr (if possible) and to any logs that are
4560 reporting errors. Implements ticket 9299.
4563 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4564 not entirely remove it from the connection lists. Fixes bug 9602;
4565 bugfix on 0.2.4.4-alpha.
4566 - Do not treat streams that fail with reason
4567 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4568 since it could also indicate an ENETUNREACH connection error. Fixes
4569 part of bug 10777; bugfix on 0.2.4.8-alpha.
4571 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
4572 - Do not allow OpenSSL engines to replace the PRNG, even when
4573 HardwareAccel is set. The only default builtin PRNG engine uses
4574 the Intel RDRAND instruction to replace the entire PRNG, and
4575 ignores all attempts to seed it with more entropy. That's
4576 cryptographically stupid: the right response to a new alleged
4577 entropy source is never to discard all previously used entropy
4578 sources. Fixes bug 10402; works around behavior introduced in
4579 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4581 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4582 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4583 - Avoid launching spurious extra circuits when a stream is pending.
4584 This fixes a bug where any circuit that _wasn't_ unusable for new
4585 streams would be treated as if it were, causing extra circuits to
4586 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4588 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4589 - No longer stop reading or writing on cpuworker connections when
4590 our rate limiting buckets go empty. Now we should handle circuit
4591 handshake requests more promptly. Resolves bug 9731.
4592 - Stop trying to bootstrap all our directory information from
4593 only our first guard. Discovered while fixing bug 9946; bugfix
4596 o Minor features (bridges, pluggable transports):
4597 - Add threshold cutoffs to the networkstatus document created by
4598 the Bridge Authority. Fixes bug 1117.
4599 - On Windows, spawn background processes using the CREATE_NO_WINDOW
4600 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
4601 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
4602 Vidalia set this option for us.) Implements ticket 10297.
4604 o Minor features (security):
4605 - Always clear OpenSSL bignums before freeing them -- even bignums
4606 that don't contain secrets. Resolves ticket 10793. Patch by
4609 o Minor features (config options and command line):
4610 - Add an --allow-missing-torrc commandline option that tells Tor to
4611 run even if the configuration file specified by -f is not available.
4612 Implements ticket 10060.
4613 - Add support for the TPROXY transparent proxying facility on Linux.
4614 See documentation for the new TransProxyType option for more
4615 details. Implementation by "thomo". Closes ticket 10582.
4617 o Minor features (controller):
4618 - Add a new "HS_DESC" controller event that reports activities
4619 related to hidden service descriptors. Resolves ticket 8510.
4620 - New "DROPGUARDS" controller command to forget all current entry
4621 guards. Not recommended for ordinary use, since replacing guards
4622 too frequently makes several attacks easier. Resolves ticket 9934;
4625 o Minor features (build):
4626 - Assume that a user using ./configure --host wants to cross-compile,
4627 and give an error if we cannot find a properly named
4628 tool-chain. Add a --disable-tool-name-check option to proceed
4629 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
4630 - If we run ./configure and the compiler recognizes -fstack-protector
4631 but the linker rejects it, warn the user about a potentially missing
4632 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
4634 o Minor features (testing):
4635 - If Python is installed, "make check" now runs extra tests beyond
4636 the unit test scripts.
4637 - When bootstrapping a test network, sometimes very few relays get
4638 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
4639 specify a set of relays which should be voted Guard regardless of
4640 their uptime or bandwidth. Addresses ticket 9206.
4642 o Minor features (log messages):
4643 - When ServerTransportPlugin is set on a bridge, Tor can write more
4644 useful statistics about bridge use in its extrainfo descriptors,
4645 but only if the Extended ORPort ("ExtORPort") is set too. Add a
4646 log message to inform the user in this case. Resolves ticket 9651.
4647 - When receiving a new controller connection, log the origin address.
4648 Resolves ticket 9698; patch from "sigpipe".
4649 - When logging OpenSSL engine status at startup, log the status of
4650 more engines. Fixes ticket 10043; patch from Joshua Datko.
4651 - Turn "circuit handshake stats since last time" log messages into a
4652 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
4654 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4655 - Improve the circuit queue out-of-memory handler. Previously, when
4656 we ran low on memory, we'd close whichever circuits had the most
4657 queued cells. Now, we close those that have the *oldest* queued
4658 cells, on the theory that those are most responsible for us
4659 running low on memory. Based on analysis from a forthcoming paper
4660 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4661 - Generate bootstrapping status update events correctly when fetching
4662 microdescriptors. Fixes bug 9927.
4663 - Update to the October 2 2013 Maxmind GeoLite Country database.
4665 o Minor bugfixes (clients):
4666 - When closing a channel that has already been open, do not close
4667 pending circuits that were waiting to connect to the same relay.
4668 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
4671 o Minor bugfixes (relays):
4672 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
4673 exit node as a NOROUTE error, not an INTERNAL error, since they
4674 can apparently happen when trying to connect to the wrong sort
4675 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
4677 o Minor bugfixes (bridges):
4678 - Fix a bug where the first connection works to a bridge that uses a
4679 pluggable transport with client-side parameters, but we don't send
4680 the client-side parameters on subsequent connections. (We don't
4681 use any pluggable transports with client-side parameters yet,
4682 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
4683 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
4685 o Minor bugfixes (node selection):
4686 - If ExcludeNodes is set, consider non-excluded hidden service
4687 directory servers before excluded ones. Do not consider excluded
4688 hidden service directory servers at all if StrictNodes is
4689 set. (Previously, we would sometimes decide to connect to those
4690 servers, and then realize before we initiated a connection that
4691 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
4693 - If we set the ExitNodes option but it doesn't include any nodes
4694 that have the Exit flag, we would choose not to bootstrap. Now we
4695 bootstrap so long as ExitNodes includes nodes which can exit to
4696 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
4698 o Minor bugfixes (controller and command-line):
4699 - If changing a config option via "setconf" fails in a recoverable
4700 way, we used to nonetheless write our new control ports to the
4701 file described by the "ControlPortWriteToFile" option. Now we only
4702 write out that file if we successfully switch to the new config
4703 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
4704 - When a command-line option such as --version or --help that
4705 ordinarily implies --hush appears on the command line along with
4706 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
4707 only if it appeared later on the command line. Fixes bug 9578;
4708 bugfix on 0.2.5.1-alpha.
4710 o Minor bugfixes (code correctness):
4711 - Previously we used two temporary files when writing descriptors to
4712 disk; now we only use one. Fixes bug 1376.
4713 - Remove an erroneous (but impossible and thus harmless) pointer
4714 comparison that would have allowed compilers to skip a bounds
4715 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
4716 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
4717 - Fix an always-true assertion in pluggable transports code so it
4718 actually checks what it was trying to check. Fixes bug 10046;
4719 bugfix on 0.2.3.9-alpha. Found by "dcb".
4721 o Minor bugfixes (protocol correctness):
4722 - When receiving a VERSIONS cell with an odd number of bytes, close
4723 the connection immediately since the cell is malformed. Fixes bug
4724 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
4727 o Minor bugfixes (build):
4728 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
4729 turned off (that is, without support for v2 link handshakes). Fixes
4730 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
4731 - Fix compilation warnings and startup issues when running with
4732 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
4734 - Fix compilation on Solaris 9, which didn't like us having an
4735 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
4737 o Minor bugfixes (testing):
4738 - Fix a segmentation fault in our benchmark code when running with
4739 Fedora's OpenSSL package, or any other OpenSSL that provides
4740 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
4742 o Minor bugfixes (log messages):
4743 - Fix a bug where clients using bridges would report themselves
4744 as 50% bootstrapped even without a live consensus document.
4745 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
4746 - Suppress a warning where, if there's only one directory authority
4747 in the network, we would complain that votes and signatures cannot
4748 be uploaded to other directory authorities. Fixes bug 10842;
4749 bugfix on 0.2.2.26-beta.
4750 - Report bootstrapping progress correctly when we're downloading
4751 microdescriptors. We had updated our "do we have enough microdescs
4752 to begin building circuits?" logic most recently in 0.2.4.10-alpha
4753 (see bug 5956), but we left the bootstrap status event logic at
4754 "how far through getting 1/4 of them are we?" Fixes bug 9958;
4755 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
4757 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
4758 - Avoid a crash bug when starting with a corrupted microdescriptor
4759 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
4760 - If we fail to dump a previously cached microdescriptor to disk, avoid
4761 freeing duplicate data later on. Fixes bug 10423; bugfix on
4762 0.2.4.13-alpha. Spotted by "bobnomnom".
4764 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4765 - Correctly log long IPv6 exit policies, instead of truncating them
4766 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
4767 - Our default TLS ecdhe groups were backwards: we meant to be using
4768 P224 for relays (for performance win) and P256 for bridges (since
4769 it is more common in the wild). Instead we had it backwards. After
4770 reconsideration, we decided that the default should be P256 on all
4771 hosts, since its security is probably better, and since P224 is
4772 reportedly used quite little in the wild. Found by "skruffy" on
4773 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
4774 - Free directory authority certificate download statuses on exit
4775 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
4777 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4778 - If the guard we choose first doesn't answer, we would try the
4779 second guard, but once we connected to the second guard we would
4780 abandon it and retry the first one, slowing down bootstrapping.
4781 The fix is to treat all our initially chosen guards as acceptable
4782 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4783 - Fix an assertion failure that would occur when disabling the
4784 ORPort setting on a running Tor process while accounting was
4785 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4786 - When examining the list of network interfaces to find our address,
4787 do not consider non-running or disabled network interfaces. Fixes
4788 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4789 - Avoid an off-by-one error when checking buffer boundaries when
4790 formatting the exit status of a pluggable transport helper.
4791 This is probably not an exploitable bug, but better safe than
4792 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4795 o Removed code and features:
4796 - Clients now reject any directory authority certificates lacking
4797 a dir-key-crosscert element. These have been included since
4798 0.2.1.9-alpha, so there's no real reason for them to be optional
4799 any longer. Completes proposal 157. Resolves ticket 10162.
4800 - Remove all code that existed to support the v2 directory system,
4801 since there are no longer any v2 directory authorities. Resolves
4803 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
4804 options, which were used for designating authorities as "Hidden
4805 service authorities". There has been no use of hidden service
4806 authorities since 0.2.2.1-alpha, when we stopped uploading or
4807 downloading v0 hidden service descriptors. Fixes bug 10881; also
4808 part of a fix for bug 10841.
4810 o Code simplification and refactoring:
4811 - Remove some old fallback code designed to keep Tor clients working
4812 in a network with only two working relays. Elsewhere in the code we
4813 have long since stopped supporting such networks, so there wasn't
4814 much point in keeping it around. Addresses ticket 9926.
4815 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
4816 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
4817 - Remove data structures which were introduced to implement the
4818 CellStatistics option: they are now redundant with the addition
4819 of a timestamp to the regular packed_cell_t data structure, which
4820 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
4823 o Documentation (man page) fixes:
4824 - Update manpage to describe some of the files you can expect to
4825 find in Tor's DataDirectory. Addresses ticket 9839.
4826 - Document that all but one DirPort entry must have the NoAdvertise
4827 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
4829 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4830 - Clarify the usage and risks of setting the ContactInfo torrc line
4831 for your relay or bridge. Resolves ticket 9854.
4832 - Add anchors to the manpage so we can link to the html version of
4833 the documentation for specific options. Resolves ticket 9866.
4834 - Replace remaining references to DirServer in man page and
4835 log entries. Resolves ticket 10124.
4838 - Make the "tor-gencert" tool used by directory authority operators
4839 create 2048-bit signing keys by default (rather than 1024-bit, since
4840 1024-bit is uncomfortably small these days). Addresses ticket 10324.
4843 Changes in version 0.2.4.20 - 2013-12-22
4844 Tor 0.2.4.20 fixes potentially poor random number generation for users
4845 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
4846 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
4847 and 4) have no state file in their DataDirectory (as would happen on
4848 first start). Users who generated relay or hidden service identity
4849 keys in such a situation should discard them and generate new ones.
4851 This release also fixes a logic error that caused Tor clients to build
4852 many more preemptive circuits than they actually need.
4855 - Do not allow OpenSSL engines to replace the PRNG, even when
4856 HardwareAccel is set. The only default builtin PRNG engine uses
4857 the Intel RDRAND instruction to replace the entire PRNG, and
4858 ignores all attempts to seed it with more entropy. That's
4859 cryptographically stupid: the right response to a new alleged
4860 entropy source is never to discard all previously used entropy
4861 sources. Fixes bug 10402; works around behavior introduced in
4862 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4864 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4865 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4866 - Avoid launching spurious extra circuits when a stream is pending.
4867 This fixes a bug where any circuit that _wasn't_ unusable for new
4868 streams would be treated as if it were, causing extra circuits to
4869 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4872 - Avoid a crash bug when starting with a corrupted microdescriptor
4873 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
4874 - If we fail to dump a previously cached microdescriptor to disk, avoid
4875 freeing duplicate data later on. Fixes bug 10423; bugfix on
4876 0.2.4.13-alpha. Spotted by "bobnomnom".
4879 Changes in version 0.2.4.19 - 2013-12-11
4880 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
4881 (1986-2013). Aaron worked on diverse projects including helping to guide
4882 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
4883 transparency to the U.S government's PACER documents, and contributing
4884 design and development for Tor and Tor2Web. Aaron was one of the latest
4885 martyrs in our collective fight for civil liberties and human rights,
4886 and his death is all the more painful because he was one of us.
4888 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
4889 a new circuit handshake and link encryption that use ECC to provide
4890 better security and efficiency; makes relays better manage circuit
4891 creation requests; uses "directory guards" to reduce client enumeration
4892 risks; makes bridges collect and report statistics about the pluggable
4893 transports they support; cleans up and improves our geoip database;
4894 gets much closer to IPv6 support for clients, bridges, and relays; makes
4895 directory authorities use measured bandwidths rather than advertised
4896 ones when computing flags and thresholds; disables client-side DNS
4897 caching to reduce tracking risks; and fixes a big bug in bridge
4898 reachability testing. This release introduces two new design
4899 abstractions in the code: a new "channel" abstraction between circuits
4900 and or_connections to allow for implementing alternate relay-to-relay
4901 transports, and a new "circuitmux" abstraction storing the queue of
4902 circuits for a channel. The release also includes many stability,
4903 security, and privacy fixes.
4906 Changes in version 0.2.4.18-rc - 2013-11-16
4907 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
4908 series. It takes a variety of fixes from the 0.2.5.x branch to improve
4909 stability, performance, and better handling of edge cases.
4912 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4913 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4914 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4915 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4916 them to solve bug 6033.)
4919 - No longer stop reading or writing on cpuworker connections when
4920 our rate limiting buckets go empty. Now we should handle circuit
4921 handshake requests more promptly. Resolves bug 9731.
4922 - If we are unable to save a microdescriptor to the journal, do not
4923 drop it from memory and then reattempt downloading it. Fixes bug
4924 9645; bugfix on 0.2.2.6-alpha.
4925 - Stop trying to bootstrap all our directory information from
4926 only our first guard. Discovered while fixing bug 9946; bugfix
4928 - The new channel code sometimes lost track of in-progress circuits,
4929 causing long-running clients to stop building new circuits. The
4930 fix is to always call circuit_n_chan_done(chan, 0) from
4931 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
4933 o Minor bugfixes (on 0.2.4.x):
4934 - Correctly log long IPv6 exit policies, instead of truncating them
4935 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
4936 - Our default TLS ecdhe groups were backwards: we meant to be using
4937 P224 for relays (for performance win) and P256 for bridges (since
4938 it is more common in the wild). Instead we had it backwards. After
4939 reconsideration, we decided that the default should be P256 on all
4940 hosts, since its security is probably better, and since P224 is
4941 reportedly used quite little in the wild. Found by "skruffy" on
4942 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
4943 - Free directory authority certificate download statuses on exit
4944 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
4946 o Minor bugfixes (on 0.2.3.x and earlier):
4947 - If the guard we choose first doesn't answer, we would try the
4948 second guard, but once we connected to the second guard we would
4949 abandon it and retry the first one, slowing down bootstrapping.
4950 The fix is to treat all our initially chosen guards as acceptable
4951 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4952 - Fix an assertion failure that would occur when disabling the
4953 ORPort setting on a running Tor process while accounting was
4954 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4955 - When examining the list of network interfaces to find our address,
4956 do not consider non-running or disabled network interfaces. Fixes
4957 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4958 - Avoid an off-by-one error when checking buffer boundaries when
4959 formatting the exit status of a pluggable transport helper.
4960 This is probably not an exploitable bug, but better safe than
4961 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4964 o Minor features (protecting client timestamps):
4965 - Clients no longer send timestamps in their NETINFO cells. These were
4966 not used for anything, and they provided one small way for clients
4967 to be distinguished from each other as they moved from network to
4968 network or behind NAT. Implements part of proposal 222.
4969 - Clients now round timestamps in INTRODUCE cells down to the nearest
4970 10 minutes. If a new Support022HiddenServices option is set to 0, or
4971 if it's set to "auto" and the feature is disabled in the consensus,
4972 the timestamp is sent as 0 instead. Implements part of proposal 222.
4973 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4974 a big deal from a security point of view, but it achieves no actual
4975 good purpose, and isn't needed. Implements part of proposal 222.
4976 - Reduce down accuracy of timestamps in hidden service descriptors.
4977 Implements part of proposal 222.
4979 o Minor features (other):
4980 - Improve the circuit queue out-of-memory handler. Previously, when
4981 we ran low on memory, we'd close whichever circuits had the most
4982 queued cells. Now, we close those that have the *oldest* queued
4983 cells, on the theory that those are most responsible for us
4984 running low on memory. Based on analysis from a forthcoming paper
4985 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4986 - Generate bootstrapping status update events correctly when fetching
4987 microdescriptors. Fixes bug 9927.
4988 - Update to the October 2 2013 Maxmind GeoLite Country database.
4990 o Documentation fixes:
4991 - Clarify the usage and risks of setting the ContactInfo torrc line
4992 for your relay or bridge. Resolves ticket 9854.
4993 - Add anchors to the manpage so we can link to the html version of
4994 the documentation for specific options. Resolves ticket 9866.
4995 - Replace remaining references to DirServer in man page and
4996 log entries. Resolves ticket 10124.
4999 Changes in version 0.2.5.1-alpha - 2013-10-02
5000 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
5001 on Linux, allows bridges that offer pluggable transports to report usage
5002 statistics, fixes many issues to make testing easier, and provides
5003 a pile of minor features and bugfixes that have been waiting for a
5004 release of the new branch.
5006 This is the first alpha release in a new series, so expect there to
5007 be bugs. Users who would rather test out a more stable branch should
5008 stay with 0.2.4.x for now.
5010 o Major features (security):
5011 - Use the seccomp2 syscall filtering facility on Linux to limit
5012 which system calls Tor can invoke. This is an experimental,
5013 Linux-only feature to provide defense-in-depth against unknown
5014 attacks. To try turning it on, set "Sandbox 1" in your torrc
5015 file. Please be ready to report bugs. We hope to add support
5016 for better sandboxing in the future, including more fine-grained
5017 filters, better division of responsibility, and support for more
5018 platforms. This work has been done by Cristian-Matei Toader for
5019 Google Summer of Code.
5020 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
5021 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
5022 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
5023 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
5024 them to solve bug 6033.)
5026 o Major features (other):
5027 - Add support for passing arguments to managed pluggable transport
5028 proxies. Implements ticket 3594.
5029 - Bridges now track GeoIP information and the number of their users
5030 even when pluggable transports are in use, and report usage
5031 statistics in their extra-info descriptors. Resolves tickets 4773
5033 - Make testing Tor networks bootstrap better: lower directory fetch
5034 retry schedules and maximum interval without directory requests,
5035 and raise maximum download tries. Implements ticket 6752.
5036 - Add make target 'test-network' to run tests on a Chutney network.
5037 Implements ticket 8530.
5038 - The ntor handshake is now on-by-default, no matter what the
5039 directory authorities recommend. Implements ticket 8561.
5042 - Instead of writing destroy cells directly to outgoing connection
5043 buffers, queue them and intersperse them with other outgoing cells.
5044 This can prevent a set of resource starvation conditions where too
5045 many pending destroy cells prevent data cells from actually getting
5046 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
5047 bugfix on 0.2.0.1-alpha.
5048 - If we are unable to save a microdescriptor to the journal, do not
5049 drop it from memory and then reattempt downloading it. Fixes bug
5050 9645; bugfix on 0.2.2.6-alpha.
5051 - The new channel code sometimes lost track of in-progress circuits,
5052 causing long-running clients to stop building new circuits. The
5053 fix is to always call circuit_n_chan_done(chan, 0) from
5054 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
5057 - Tor now builds each source file in two modes: a mode that avoids
5058 exposing identifiers needlessly, and another mode that exposes
5059 more identifiers for testing. This lets the compiler do better at
5060 optimizing the production code, while enabling us to take more
5061 radical measures to let the unit tests test things.
5062 - The production builds no longer include functions used only in
5063 the unit tests; all functions exposed from a module only for
5064 unit-testing are now static in production builds.
5065 - Add an --enable-coverage configuration option to make the unit
5066 tests (and a new src/or/tor-cov target) to build with gcov test
5070 - We now have rudimentary function mocking support that our unit
5071 tests can use to test functions in isolation. Function mocking
5072 lets the tests temporarily replace a function's dependencies with
5073 stub functions, so that the tests can check the function without
5074 invoking the other functions it calls.
5075 - Add more unit tests for the <circid,channel>->circuit map, and
5076 the destroy-cell-tracking code to fix bug 7912.
5077 - Unit tests for failing cases of the TAP onion handshake.
5078 - More unit tests for address-manipulation functions.
5080 o Minor features (protecting client timestamps):
5081 - Clients no longer send timestamps in their NETINFO cells. These were
5082 not used for anything, and they provided one small way for clients
5083 to be distinguished from each other as they moved from network to
5084 network or behind NAT. Implements part of proposal 222.
5085 - Clients now round timestamps in INTRODUCE cells down to the nearest
5086 10 minutes. If a new Support022HiddenServices option is set to 0, or
5087 if it's set to "auto" and the feature is disabled in the consensus,
5088 the timestamp is sent as 0 instead. Implements part of proposal 222.
5089 - Stop sending timestamps in AUTHENTICATE cells. This is not such
5090 a big deal from a security point of view, but it achieves no actual
5091 good purpose, and isn't needed. Implements part of proposal 222.
5092 - Reduce down accuracy of timestamps in hidden service descriptors.
5093 Implements part of proposal 222.
5095 o Minor features (config options):
5096 - Config (torrc) lines now handle fingerprints which are missing
5097 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
5098 - Support a --dump-config option to print some or all of the
5099 configured options. Mainly useful for debugging the command-line
5100 option parsing code. Helps resolve ticket 4647.
5101 - Raise awareness of safer logging: notify user of potentially
5102 unsafe config options, like logging more verbosely than severity
5103 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
5104 - Add a new configuration option TestingV3AuthVotingStartOffset
5105 that bootstraps a network faster by changing the timing for
5106 consensus votes. Addresses ticket 8532.
5107 - Add a new torrc option "ServerTransportOptions" that allows
5108 bridge operators to pass configuration parameters to their
5109 pluggable transports. Resolves ticket 8929.
5110 - The config (torrc) file now accepts bandwidth and space limits in
5111 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
5112 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
5115 o Minor features (build):
5116 - Add support for `--library-versions` flag. Implements ticket 6384.
5117 - Return the "unexpected sendme" warnings to a warn severity, but make
5118 them rate limited, to help diagnose ticket 8093.
5119 - Detect a missing asciidoc, and warn the user about it, during
5120 configure rather than at build time. Fixes issue 6506. Patch from
5123 o Minor features (other):
5124 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
5125 sockets in a single system call. Implements ticket 5129.
5126 - Log current accounting state (bytes sent and received + remaining
5127 time for the current accounting period) in the relay's heartbeat
5128 message. Implements ticket 5526; patch from Peter Retzlaff.
5129 - Implement the TRANSPORT_LAUNCHED control port event that
5130 notifies controllers about new launched pluggable
5131 transports. Resolves ticket 5609.
5132 - If we're using the pure-C 32-bit curve25519_donna implementation
5133 of curve25519, build it with the -fomit-frame-pointer option to
5134 make it go faster on register-starved hosts. This improves our
5135 handshake performance by about 6% on i386 hosts without nacl.
5137 - Update to the September 4 2013 Maxmind GeoLite Country database.
5140 - Set the listen() backlog limit to the largest actually supported
5141 on the system, not to the value in a header file. Fixes bug 9716;
5142 bugfix on every released Tor.
5143 - No longer accept malformed http headers when parsing urls from
5144 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
5145 bugfix on 0.0.6pre1.
5146 - In munge_extrainfo_into_routerinfo(), check the return value of
5147 memchr(). This would have been a serious issue if we ever passed
5148 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
5150 - On the chance that somebody manages to build Tor on a
5151 platform where time_t is unsigned, correct the way that
5152 microdesc_add_to_cache() handles negative time arguments.
5153 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
5154 - Reject relative control socket paths and emit a warning. Previously,
5155 single-component control socket paths would be rejected, but Tor
5156 would not log why it could not validate the config. Fixes bug 9258;
5157 bugfix on 0.2.3.16-alpha.
5159 o Minor bugfixes (command line):
5160 - Use a single command-line parser for parsing torrc options on the
5161 command line and for finding special command-line options to avoid
5162 inconsistent behavior for torrc option arguments that have the same
5163 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
5165 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
5166 9573; bugfix on 0.0.9pre5.
5168 o Minor fixes (build, auxiliary programs):
5169 - Stop preprocessing the "torify" script with autoconf, since
5170 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
5172 - The tor-fw-helper program now follows the standard convention and
5173 exits with status code "0" on success. Fixes bug 9030; bugfix on
5174 0.2.3.1-alpha. Patch by Arlo Breault.
5175 - Corrected ./configure advice for what openssl dev package you should
5176 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
5178 o Minor code improvements:
5179 - Remove constants and tests for PKCS1 padding; it's insecure and
5180 shouldn't be used for anything new. Fixes bug 8792; patch
5182 - Remove instances of strcpy() from the unit tests. They weren't
5183 hurting anything, since they were only in the unit tests, but it's
5184 embarassing to have strcpy() in the code at all, and some analysis
5185 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
5186 0.2.3.8-alpha. Patch from Arlo Breault.
5189 - Remove migration code from when we renamed the "cached-routers"
5190 file to "cached-descriptors" back in 0.2.0.8-alpha. This
5191 incidentally resolves ticket 6502 by cleaning up the related code
5192 a bit. Patch from Akshay Hebbar.
5194 o Code simplification and refactoring:
5195 - Extract the common duplicated code for creating a subdirectory
5196 of the data directory and writing to a file in it. Fixes ticket
5197 4282; patch from Peter Retzlaff.
5198 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
5199 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
5200 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
5201 - Add a set of accessor functions for the circuit timeout data
5202 structure. Fixes ticket 6153; patch from "piet".
5203 - Clean up exit paths from connection_listener_new(). Closes ticket
5204 8789. Patch from Arlo Breault.
5205 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
5206 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
5207 - Use a doubly-linked list to implement the global circuit list.
5208 Resolves ticket 9108. Patch from Marek Majkowski.
5209 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
5212 Changes in version 0.2.4.17-rc - 2013-09-05
5213 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
5214 series. It adds an emergency step to help us tolerate the massive
5215 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
5216 circuit-level handshakes now effectively jump the queue compared to
5217 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
5218 big bug hindering bridge reachability tests.
5221 - Relays now process the new "NTor" circuit-level handshake requests
5222 with higher priority than the old "TAP" circuit-level handshake
5223 requests. We still process some TAP requests to not totally starve
5224 0.2.3 clients when NTor becomes popular. A new consensus parameter
5225 "NumNTorsPerTAP" lets us tune the balance later if we need to.
5226 Implements ticket 9574.
5229 - If the circuit build timeout logic is disabled (via the consensus,
5230 or because we are an authority), then don't build testing circuits.
5231 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
5232 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
5233 previously they did not, which prevented them from receiving
5234 successful connections from relays for self-test or bandwidth
5235 testing. Also, when a relay is extending a circuit to a bridge,
5236 it needs to send a NETINFO cell, even when the bridge hasn't sent
5237 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
5238 - If the time to download the next old-style networkstatus is in
5239 the future, do not decline to consider whether to download the
5240 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
5244 - Avoid double-closing the listener socket in our socketpair()
5245 replacement (used on Windows) in the case where the addresses on
5246 our opened sockets don't match what we expected. Fixes bug 9400;
5247 bugfix on 0.0.2pre7. Found by Coverity.
5249 o Minor fixes (config options):
5250 - Avoid overflows when the user sets MaxCircuitDirtiness to a
5251 ridiculously high value, by imposing a (ridiculously high) 30-day
5252 maximum on MaxCircuitDirtiness.
5253 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
5254 message is logged at notice, not at info.
5255 - Warn and fail if a server is configured not to advertise any
5256 ORPorts at all. (We need *something* to put in our descriptor,
5257 or we just won't work.)
5260 - Track how many "TAP" and "NTor" circuit handshake requests we get,
5261 and how many we complete, and log it every hour to help relay
5262 operators follow trends in network load. Addresses ticket 9658.
5263 - Update to the August 7 2013 Maxmind GeoLite Country database.
5266 Changes in version 0.2.4.16-rc - 2013-08-10
5267 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
5268 series. It fixes several crash bugs in the 0.2.4 branch.
5271 - Fix a bug in the voting algorithm that could yield incorrect results
5272 when a non-naming authority declared too many flags. Fixes bug 9200;
5273 bugfix on 0.2.0.3-alpha.
5274 - Fix an uninitialized read that could in some cases lead to a remote
5275 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
5276 Anybody running a hidden service on the experimental 0.2.4.x
5277 branch should upgrade. (This is, so far as we know, unrelated to
5279 - Avoid an assertion failure when processing DNS replies without the
5280 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
5281 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
5282 0.2.4.15-rc. Found by stem integration tests.
5285 - Fix an invalid memory read that occured when a pluggable
5286 transport proxy failed its configuration protocol.
5287 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
5288 - When evaluating whether to use a connection that we haven't
5289 decided is canonical using a recent link protocol version,
5290 decide that it's canonical only if it used address _does_
5291 match the desired address. Fixes bug 9309; bugfix on
5292 0.2.4.4-alpha. Reported by skruffy.
5293 - Make the default behavior of NumDirectoryGuards be to track
5294 NumEntryGuards. Now a user who changes only NumEntryGuards will get
5295 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
5296 - Fix a spurious compilation warning with some older versions of
5297 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
5300 - Update to the July 3 2013 Maxmind GeoLite Country database.
5303 Changes in version 0.2.4.15-rc - 2013-07-01
5304 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
5305 series. It fixes a few smaller bugs, but generally appears stable.
5306 Please test it and let us know whether it is!
5309 - When receiving a new configuration file via the control port's
5310 LOADCONF command, do not treat the defaults file as absent.
5311 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
5314 - Issue a warning when running with the bufferevents backend enabled.
5315 It's still not stable, and people should know that they're likely
5316 to hit unexpected problems. Closes ticket 9147.
5319 Changes in version 0.2.4.14-alpha - 2013-06-18
5320 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
5321 present in 0.2.4.13-alpha.
5324 - When we have too much memory queued in circuits (according to a new
5325 MaxMemInCellQueues option), close the circuits consuming the most
5326 memory. This prevents us from running out of memory as a relay if
5327 circuits fill up faster than they can be drained. Fixes bug 9063;
5328 bugfix on the 54th commit of Tor. This bug is a further fix beyond
5329 bug 6252, whose fix was merged into 0.2.3.21-rc.
5331 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
5332 where we tried to solve this issue simply by imposing an upper limit
5333 on the number of queued cells for a single circuit. That approach
5334 proved to be problematic, since there are ways to provoke clients to
5335 send a number of cells in excess of any such reasonable limit. Fixes
5336 bug 9072; bugfix on 0.2.4.13-alpha.
5338 - Limit hidden service descriptors to at most ten introduction
5339 points, to slow one kind of guard enumeration. Fixes bug 9002;
5340 bugfix on 0.1.1.11-alpha.
5343 Changes in version 0.2.4.13-alpha - 2013-06-14
5344 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
5345 vulnerabilities, makes socks5 username/password circuit isolation
5346 actually actually work (this time for sure!), and cleans up a bunch
5347 of other issues in preparation for a release candidate.
5349 o Major bugfixes (robustness):
5350 - Close any circuit that has too many cells queued on it. Fixes
5351 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
5352 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
5353 - Prevent the get_freelists() function from running off the end of
5354 the list of freelists if it somehow gets an unrecognized
5355 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
5357 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
5358 when an exit connection with optimistic data succeeds immediately
5359 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
5361 - Fix a directory authority crash bug when building a consensus
5362 using an older consensus as its basis. Fixes bug 8833. Bugfix
5366 - Avoid a memory leak where we would leak a consensus body when we
5367 find that a consensus which we couldn't previously verify due to
5368 missing certificates is now verifiable. Fixes bug 8719; bugfix
5370 - We used to always request authority certificates by identity digest,
5371 meaning we'd get the newest one even when we wanted one with a
5372 different signing key. Then we would complain about being given
5373 a certificate we already had, and never get the one we really
5374 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
5375 resource to request the one we want. Fixes bug 5595; bugfix on
5377 - Follow the socks5 protocol when offering username/password
5378 authentication. The fix for bug 8117 exposed this bug, and it
5379 turns out real-world applications like Pidgin do care. Bugfix on
5380 0.2.3.2-alpha; fixes bug 8879.
5381 - Prevent failures on Windows Vista and later when rebuilding the
5382 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
5383 bugfix on 0.2.4.12-alpha.
5386 - Fix an impossible buffer overrun in the AES unit tests. Fixes
5387 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
5388 - If for some reason we fail to write a microdescriptor while
5389 rebuilding the cache, do not let the annotations from that
5390 microdescriptor linger in the cache file, and do not let the
5391 microdescriptor stay recorded as present in its old location.
5392 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
5393 - Fix a memory leak that would occur whenever a configuration
5394 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
5395 - Paste the description for PathBias parameters from the man
5396 page into or.h, so the code documents them too. Fixes bug 7982;
5397 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
5398 - Relays now treat a changed IPv6 ORPort as sufficient reason to
5399 publish an updated descriptor. Fixes bug 6026; bugfix on
5401 - When launching a resolve request on behalf of an AF_UNIX control
5402 socket, omit the address field of the new entry connection, used in
5403 subsequent controller events, rather than letting tor_dup_addr()
5404 set it to "<unknown address type>". Fixes bug 8639; bugfix on
5407 o Minor bugfixes (log messages):
5408 - Fix a scaling issue in the path bias accounting code that
5409 resulted in "Bug:" log messages from either
5410 pathbias_scale_close_rates() or pathbias_count_build_success().
5411 This represents a bugfix on a previous bugfix: the original fix
5412 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
5414 - Give a less useless error message when the user asks for an IPv4
5415 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
5419 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
5420 to tolerate bug 8093 for now.
5421 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
5422 in directory authority votes to describe whether they have enough
5423 measured bandwidths to ignore advertised (relay descriptor)
5424 bandwidth claims. Resolves ticket 8711.
5425 - Update to the June 5 2013 Maxmind GeoLite Country database.
5427 o Removed documentation:
5428 - Remove some of the older contents of doc/ as obsolete; move others
5429 to torspec.git. Fixes bug 8965.
5431 o Code simplification and refactoring:
5432 - Avoid using character buffers when constructing most directory
5433 objects: this approach was unwieldy and error-prone. Instead,
5434 build smartlists of strings, and concatenate them when done.
5437 Changes in version 0.2.4.12-alpha - 2013-04-18
5438 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
5439 process for lengthening the guard rotation period, makes directory
5440 authority opinions in the consensus a bit less gameable, makes socks5
5441 username/password circuit isolation actually work, and fixes a wide
5442 variety of other issues.
5445 - Raise the default time that a client keeps an entry guard from
5446 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
5447 2012 paper. (We would make it even longer, but we need better client
5448 load balancing first.) Also, make the guard lifetime controllable
5449 via a new GuardLifetime torrc option and a GuardLifetime consensus
5450 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
5451 - Directory authorities now prefer using measured bandwidths to
5452 advertised ones when computing flags and thresholds. Resolves
5454 - Directory authorities that have more than a threshold number
5455 of relays with measured bandwidths now treat relays with unmeasured
5456 bandwidths as having bandwidth 0. Resolves ticket 8435.
5458 o Major bugfixes (assert / resource use):
5459 - Avoid a bug where our response to TLS renegotiation under certain
5460 network conditions could lead to a busy-loop, with 100% CPU
5461 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
5462 - Avoid an assertion when we discover that we'd like to write a cell
5463 onto a closing connection: just discard the cell. Fixes another
5464 case of bug 7350; bugfix on 0.2.4.4-alpha.
5466 o Major bugfixes (client-side privacy):
5467 - When we mark a circuit as unusable for new circuits, have it
5468 continue to be unusable for new circuits even if MaxCircuitDirtiness
5469 is increased too much at the wrong time, or the system clock jumps
5470 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
5471 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
5472 which have resolved to internal addresses") is set, apply that
5473 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
5474 - When an exit relay rejects a stream with reason "exit policy", but
5475 we only know an exit policy summary (e.g. from the microdesc
5476 consensus) for it, do not mark the relay as useless for all exiting.
5477 Instead, mark just the circuit as unsuitable for that particular
5478 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
5479 - Allow applications to get proper stream isolation with
5480 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
5481 username/password authentication also offer "no authentication". Tor
5482 had previously preferred "no authentication", so the applications
5483 never actually sent Tor their auth details. Now Tor selects
5484 username/password authentication if it's offered. You can disable
5485 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
5486 bug 8117; bugfix on 0.2.3.3-alpha.
5488 o Major bugfixes (other):
5489 - When unable to find any working directory nodes to use as a
5490 directory guard, give up rather than adding the same non-working
5491 nodes to the directory guard list over and over. Fixes bug 8231;
5492 bugfix on 0.2.4.8-alpha.
5495 - Reject as invalid most directory objects containing a NUL.
5496 Belt-and-suspender fix for bug 8037.
5497 - In our testsuite, create temporary directories with a bit more
5498 entropy in their name to make name collisions less likely. Fixes
5500 - Add CACHED keyword to ADDRMAP events in the control protocol
5501 to indicate whether a DNS result will be cached or not. Resolves
5503 - Update to the April 3 2013 Maxmind GeoLite Country database.
5505 o Minor features (build):
5506 - Detect and reject attempts to build Tor with threading support
5507 when OpenSSL has been compiled without threading support.
5509 - Clarify that when autoconf is checking for nacl, it is checking
5510 specifically for nacl with a fast curve25519 implementation.
5512 - Warn if building on a platform with an unsigned time_t: there
5513 are too many places where Tor currently assumes that time_t can
5514 hold negative values. We'd like to fix them all, but probably
5517 o Minor bugfixes (build):
5518 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
5519 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
5520 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
5521 - Add the old src/or/micro-revision.i filename to CLEANFILES.
5522 On the off chance that somebody has one, it will go away as soon
5523 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
5524 - Build Tor correctly on 32-bit platforms where the compiler can build
5525 but not run code using the "uint128_t" construction. Fixes bug 8587;
5526 bugfix on 0.2.4.8-alpha.
5527 - Fix compilation warning with some versions of clang that would
5528 prefer the -Wswitch-enum compiler flag to warn about switch
5529 statements with missing enum values, even if those switch
5530 statements have a "default:" statement. Fixes bug 8598; bugfix
5533 o Minor bugfixes (protocol):
5534 - Fix the handling of a TRUNCATE cell when it arrives while the
5535 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
5536 - Fix a misframing issue when reading the version numbers in a
5537 VERSIONS cell. Previously we would recognize [00 01 00 02] as
5538 'version 1, version 2, and version 0x100', when it should have
5539 only included versions 1 and 2. Fixes bug 8059; bugfix on
5540 0.2.0.10-alpha. Reported pseudonymously.
5541 - Make the format and order of STREAM events for DNS lookups
5542 consistent among the various ways to launch DNS lookups. Fixes
5543 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
5544 - Correct our check for which versions of Tor support the EXTEND2
5545 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
5546 later, when support was really added in version 0.2.4.8-alpha.
5547 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
5549 o Minor bugfixes (other):
5550 - Correctly store microdescriptors and extrainfo descriptors with
5551 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
5552 Bug reported by "cypherpunks".
5553 - Increase the width of the field used to remember a connection's
5554 link protocol version to two bytes. Harmless for now, since the
5555 only currently recognized versions are one byte long. Reported
5556 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
5557 - If the state file's path bias counts are invalid (presumably from a
5558 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
5559 additional checks and log messages to the scaling of Path Bias
5560 counts, in case there still are remaining issues with scaling.
5561 Should help resolve bug 8235.
5562 - Eliminate several instances where we use "Nickname=ID" to refer to
5563 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
5564 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
5565 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
5567 o Minor bugfixes (syscalls):
5568 - Always check the return values of functions fcntl() and
5569 setsockopt(). We don't believe these are ever actually failing in
5570 practice, but better safe than sorry. Also, checking these return
5571 values should please analysis tools like Coverity. Patch from
5572 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
5573 - Use direct writes rather than stdio when building microdescriptor
5574 caches, in an attempt to mitigate bug 8031, or at least make it
5577 o Minor bugfixes (config):
5578 - When rejecting a configuration because we were unable to parse a
5579 quoted string, log an actual error message. Fixes bug 7950; bugfix
5581 - Behave correctly when the user disables LearnCircuitBuildTimeout
5582 but doesn't tell us what they would like the timeout to be. Fixes
5583 bug 6304; bugfix on 0.2.2.14-alpha.
5584 - When autodetecting the number of CPUs, use the number of available
5585 CPUs in preference to the number of configured CPUs. Inform the
5586 user if this reduces the number of available CPUs. Fixes bug 8002;
5587 bugfix on 0.2.3.1-alpha.
5588 - Make it an error when you set EntryNodes but disable UseGuardNodes,
5589 since it will (surprisingly to some users) ignore EntryNodes. Fixes
5590 bug 8180; bugfix on 0.2.3.11-alpha.
5591 - Allow TestingTorNetworks to override the 4096-byte minimum for
5592 the Fast threshold. Otherwise they can't bootstrap until they've
5593 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
5594 - Fix some logic errors when the user manually overrides the
5595 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
5598 o Minor bugfixes (log messages to help diagnose bugs):
5599 - If we fail to free a microdescriptor because of bug 7164, log
5600 the filename and line number from which we tried to free it.
5601 - Add another diagnostic to the heartbeat message: track and log
5602 overhead that TLS is adding to the data we write. If this is
5603 high, we are sending too little data to SSL_write at a time.
5604 Diagnostic for bug 7707.
5605 - Add more detail to a log message about relaxed timeouts, to help
5607 - Warn more aggressively when flushing microdescriptors to a
5608 microdescriptor cache fails, in an attempt to mitigate bug 8031,
5609 or at least make it more diagnosable.
5610 - Improve debugging output to help track down bug 8185 ("Bug:
5611 outgoing relay cell has n_chan==NULL. Dropping.")
5612 - Log the purpose of a path-bias testing circuit correctly.
5613 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
5615 o Minor bugfixes (0.2.4.x log messages that were too noisy):
5616 - Don't attempt to relax the timeout of already opened 1-hop circuits.
5617 They might never timeout. This should eliminate some/all cases of
5618 the relaxed timeout log message.
5619 - Use circuit creation time for network liveness evaluation. This
5620 should eliminate warning log messages about liveness caused
5621 by changes in timeout evaluation. Fixes bug 6572; bugfix on
5623 - Reduce a path bias length check from notice to info. The message
5624 is triggered when creating controller circuits. Fixes bug 8196;
5625 bugfix on 0.2.4.8-alpha.
5626 - Fix a path state issue that triggered a notice during relay startup.
5627 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
5628 - Reduce occurrences of warns about circuit purpose in
5629 connection_ap_expire_building(). Fixes bug 8477; bugfix on
5632 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
5633 - If we encounter a write failure on a SOCKS connection before we
5634 finish our SOCKS handshake, don't warn that we closed the
5635 connection before we could send a SOCKS reply. Fixes bug 8427;
5636 bugfix on 0.1.0.1-rc.
5637 - Correctly recognize that [::1] is a loopback address. Fixes
5638 bug 8377; bugfix on 0.2.1.3-alpha.
5639 - Fix a directory authority warn caused when we have a large amount
5640 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
5641 - Don't log inappropriate heartbeat messages when hibernating: a
5642 hibernating node is _expected_ to drop out of the consensus,
5643 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
5644 bugfix on 0.2.3.1-alpha.
5645 - Don't complain about bootstrapping problems while hibernating.
5646 These complaints reflect a general code problem, but not one
5647 with any problematic effects (no connections are actually
5648 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
5650 o Documentation fixes:
5651 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
5652 names match. Fixes bug 7768.
5653 - Make the torify manpage no longer refer to tsocks; torify hasn't
5654 supported tsocks since 0.2.3.14-alpha.
5655 - Make the tor manpage no longer reference tsocks.
5656 - Fix the GeoIPExcludeUnknown documentation to refer to
5657 ExcludeExitNodes rather than the currently nonexistent
5658 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
5661 - The tor-tsocks.conf is no longer distributed or installed. We
5662 recommend that tsocks users use torsocks instead. Resolves
5666 Changes in version 0.2.4.11-alpha - 2013-03-11
5667 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
5668 more robust, makes hidden service authentication work again, and
5669 resolves a DPI fingerprint for Tor's SSL transport.
5671 o Major features (directory authorities):
5672 - Directory authorities now support a new consensus method (17)
5673 where they cap the published bandwidth of servers for which
5674 insufficient bandwidth measurements exist. Fixes part of bug 2286.
5675 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
5676 serve any v2 directory information. Now we can test disabling the
5677 old deprecated v2 directory format, and see whether doing so has
5678 any effect on network load. Begins to fix bug 6783.
5679 - Directory authorities now include inside each vote a statement of
5680 the performance thresholds they used when assigning flags.
5681 Implements ticket 8151.
5683 o Major bugfixes (directory authorities):
5684 - Stop marking every relay as having been down for one hour every
5685 time we restart a directory authority. These artificial downtimes
5686 were messing with our Stable and Guard flag calculations. Fixes
5687 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
5689 o Major bugfixes (hidden services):
5690 - Allow hidden service authentication to succeed again. When we
5691 refactored the hidden service introduction code back
5692 in 0.2.4.1-alpha, we didn't update the code that checks
5693 whether authentication information is present, causing all
5694 authentication checks to return "false". Fix for bug 8207; bugfix
5695 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
5697 o Minor features (relays, bridges):
5698 - Make bridge relays check once a minute for whether their IP
5699 address has changed, rather than only every 15 minutes. Resolves
5701 - Refactor resolve_my_address() so it returns the method by which we
5702 decided our public IP address (explicitly configured, resolved from
5703 explicit hostname, guessed from interfaces, learned by gethostname).
5704 Now we can provide more helpful log messages when a relay guesses
5705 its IP address incorrectly (e.g. due to unexpected lines in
5706 /etc/hosts). Resolves ticket 2267.
5707 - Teach bridge-using clients to avoid 0.2.2 bridges when making
5708 microdescriptor-related dir requests, and only fall back to normal
5709 descriptors if none of their bridges can handle microdescriptors
5710 (as opposed to the fix in ticket 4013, which caused them to fall
5711 back to normal descriptors if *any* of their bridges preferred
5712 them). Resolves ticket 4994.
5713 - Randomize the lifetime of our SSL link certificate, so censors can't
5714 use the static value for filtering Tor flows. Resolves ticket 8443;
5715 related to ticket 4014 which was included in 0.2.2.33.
5716 - Support a new version of the link protocol that allows 4-byte circuit
5717 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
5718 a possible resource exhaustion issue. Closes ticket 7351; implements
5721 o Minor features (portability):
5722 - Tweak the curve25519-donna*.c implementations to tolerate systems
5723 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
5724 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
5725 the signs of types during autoconf. This is better than our old
5726 approach, which didn't work when cross-compiling.
5727 - Detect the sign of enum values, rather than assuming that MSC is the
5728 only compiler where enum types are all signed. Fixes bug 7727;
5729 bugfix on 0.2.4.10-alpha.
5731 o Minor features (other):
5732 - Say "KBytes" rather than "KB" in the man page (for various values
5733 of K), to further reduce confusion about whether Tor counts in
5734 units of memory or fractions of units of memory. Resolves ticket 7054.
5735 - Clear the high bit on curve25519 public keys before passing them to
5736 our backend, in case we ever wind up using a backend that doesn't do
5737 so itself. If we used such a backend, and *didn't* clear the high bit,
5738 we could wind up in a situation where users with such backends would
5739 be distinguishable from users without. Fixes bug 8121; bugfix on
5741 - Update to the March 6 2013 Maxmind GeoLite Country database.
5743 o Minor bugfixes (clients):
5744 - When we receive a RELAY_END cell with the reason DONE, or with no
5745 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
5746 status as "connection refused". Previously we reported these cases
5747 as success but then immediately closed the connection. Fixes bug
5748 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
5749 - Downgrade an assertion in connection_ap_expire_beginning to an
5750 LD_BUG message. The fix for bug 8024 should prevent this message
5751 from displaying, but just in case, a warn that we can diagnose
5752 is better than more assert crashes. Fixes bug 8065; bugfix on
5754 - Lower path use bias thresholds to .80 for notice and .60 for warn.
5755 Also make the rate limiting flags for the path use bias log messages
5756 independent from the original path bias flags. Fixes bug 8161;
5757 bugfix on 0.2.4.10-alpha.
5759 o Minor bugfixes (relays):
5760 - Stop trying to resolve our hostname so often (e.g. every time we
5761 think about doing a directory fetch). Now we reuse the cached
5762 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
5763 and 2410 (bugfix on 0.1.2.2-alpha).
5764 - Stop sending a stray "(null)" in some cases for the server status
5765 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
5767 - When choosing which stream on a formerly stalled circuit to wake
5768 first, make better use of the platform's weak RNG. Previously,
5769 we had been using the % ("modulo") operator to try to generate a
5770 1/N chance of picking each stream, but this behaves badly with
5771 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
5773 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
5774 Irix's random() only return 15 bits; Solaris's random() returns more
5775 bits but its RAND_MAX says it only returns 15, and so on. Motivated
5776 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
5778 o Minor bugfixes (directory authorities):
5779 - Directory authorities now use less space when formatting identical
5780 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
5783 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
5784 - Avoid leaking memory if we fail to compute a consensus signature
5785 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
5786 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
5788 - Fix a memory leak during safe-cookie controller authentication.
5789 Bugfix on 0.2.3.13-alpha.
5790 - Avoid memory leak of IPv6 policy content if we fail to format it into
5791 a router descriptor. Bugfix on 0.2.4.7-alpha.
5793 o Minor bugfixes (other code correctness issues):
5794 - Avoid a crash if we fail to generate an extrainfo descriptor.
5795 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
5797 - When detecting the largest possible file descriptor (in order to
5798 close all file descriptors when launching a new program), actually
5799 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
5800 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
5802 - Fix a copy-and-paste error when adding a missing A1 to a routerset
5803 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
5804 Bugfix on 0.2.4.10-alpha.
5805 - Fix an impossible-to-trigger integer overflow when estimating how
5806 long our onionskin queue would take. (This overflow would require us
5807 to accept 4 million onionskins before processing 100 of them.) Fixes
5808 bug 8210; bugfix on 0.2.4.10-alpha.
5810 o Code simplification and refactoring:
5811 - Add a wrapper function for the common "log a message with a
5815 Changes in version 0.2.4.10-alpha - 2013-02-04
5816 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
5817 certain attacks that flood the network with relays; changes the queue
5818 for circuit create requests from a sized-based limit to a time-based
5819 limit; resumes building with MSVC on Windows; and fixes a wide variety
5822 o Major bugfixes (directory authority):
5823 - When computing directory thresholds, ignore any rejected-as-sybil
5824 nodes during the computation so that they can't influence Fast,
5825 Guard, etc. (We should have done this for proposal 109.) Fixes
5827 - When marking a node as a likely sybil, reset its uptime metrics
5828 to zero, so that it cannot time towards getting marked as Guard,
5829 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
5833 - When a TLS write is partially successful but incomplete, remember
5834 that the flushed part has been flushed, and notice that bytes were
5835 actually written. Reported and fixed pseudonymously. Fixes bug
5836 7708; bugfix on Tor 0.1.0.5-rc.
5837 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
5838 ID: these could be used to create unexpected streams and circuits
5839 which would count as "present" to some parts of Tor but "absent"
5840 to others, leading to zombie circuits and streams or to a bandwidth
5841 denial-of-service. Fixes bug 7889; bugfix on every released version
5842 of Tor. Reported by "oftc_must_be_destroyed".
5843 - Rename all macros in our local copy of queue.h to begin with "TOR_".
5844 This change seems the only good way to permanently prevent conflicts
5845 with queue.h on various operating systems. Fixes bug 8107; bugfix
5848 o Major features (relay):
5849 - Instead of limiting the number of queued onionskins (aka circuit
5850 create requests) to a fixed, hard-to-configure number, we limit
5851 the size of the queue based on how many we expect to be able to
5852 process in a given amount of time. We estimate the time it will
5853 take to process an onionskin based on average processing time
5854 of previous onionskins. Closes ticket 7291. You'll never have to
5855 configure MaxOnionsPending again.
5857 o Major features (portability):
5858 - Resume building correctly with MSVC and Makefile.nmake. This patch
5859 resolves numerous bugs and fixes reported by ultramage, including
5860 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
5861 - Make the ntor and curve25519 code build correctly with MSVC.
5862 Fix on 0.2.4.8-alpha.
5865 - When directory authorities are computing thresholds for flags,
5866 never let the threshold for the Fast flag fall below 4096
5867 bytes. Also, do not consider nodes with extremely low bandwidths
5868 when deciding thresholds for various directory flags. This change
5869 should raise our threshold for Fast relays, possibly in turn
5870 improving overall network performance; see ticket 1854. Resolves
5872 - The Tor client now ignores sub-domain components of a .onion
5873 address. This change makes HTTP "virtual" hosting
5874 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
5875 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
5876 hosted on the same hidden service. Implements proposal 204.
5877 - We compute the overhead from passing onionskins back and forth to
5878 cpuworkers, and report it when dumping statistics in response to
5879 SIGUSR1. Supports ticket 7291.
5881 o Minor features (path selection):
5882 - When deciding whether we have enough descriptors to build circuits,
5883 instead of looking at raw relay counts, look at which fraction
5884 of (bandwidth-weighted) paths we're able to build. This approach
5885 keeps clients from building circuits if their paths are likely to
5886 stand out statistically. The default fraction of paths needed is
5887 taken from the consensus directory; you can override it with the
5888 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
5889 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
5890 and we have GeoIP information, also exclude all nodes with unknown
5891 countries "??" and "A1". This behavior is controlled by the
5892 new GeoIPExcludeUnknown option: you can make such nodes always
5893 excluded with "GeoIPExcludeUnknown 1", and disable the feature
5894 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
5895 gets you the default behavior. Implements feature 7706.
5896 - Path Use Bias: Perform separate accounting for successful circuit
5897 use. Keep separate statistics on stream attempt rates versus stream
5898 success rates for each guard. Provide configurable thresholds to
5899 determine when to emit log messages or disable use of guards that
5900 fail too many stream attempts. Resolves ticket 7802.
5902 o Minor features (log messages):
5903 - When learning a fingerprint for a bridge, log its corresponding
5904 transport type. Implements ticket 7896.
5905 - Improve the log message when "Bug/attack: unexpected sendme cell
5906 from client" occurs, to help us track bug 8093.
5909 - Remove a couple of extraneous semicolons that were upsetting the
5910 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
5911 bugfix on 0.2.2.1-alpha.
5912 - Remove a source of rounding error during path bias count scaling;
5913 don't count cannibalized circuits as used for path bias until we
5914 actually try to use them; and fix a circuit_package_relay_cell()
5915 warning message about n_chan==NULL. Fixes bug 7802.
5916 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
5917 actually link against nacl when we're configured to use it. Fixes
5918 bug 7972; bugfix on 0.2.4.8-alpha.
5919 - Compile correctly with the --disable-curve25519 option. Fixes
5920 bug 8153; bugfix on 0.2.4.8-alpha.
5922 o Build improvements:
5923 - Do not report status verbosely from autogen.sh unless the -v flag
5924 is specified. Fixes issue 4664. Patch from Onizuka.
5925 - Replace all calls to snprintf() outside of src/ext with
5926 tor_snprintf(). Also remove the #define to replace snprintf with
5927 _snprintf on Windows; they have different semantics, and all of
5928 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
5929 - Try to detect if we are ever building on a platform where
5930 memset(...,0,...) does not set the value of a double to 0.0. Such
5931 platforms are permitted by the C standard, though in practice
5932 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
5933 currently support them, but it's better to detect them and fail
5934 than to perform erroneously.
5937 - Stop exporting estimates of v2 and v3 directory traffic shares
5938 in extrainfo documents. They were unneeded and sometimes inaccurate.
5939 Also stop exporting any v2 directory request statistics. Resolves
5941 - Drop support for detecting and warning about versions of Libevent
5942 before 1.3e. Nothing reasonable ships with them any longer;
5943 warning the user about them shouldn't be needed. Resolves ticket
5946 o Code simplifications and refactoring:
5947 - Rename "isin" functions to "contains", for grammar. Resolves
5949 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
5950 with the natural logarithm function from the system libm. Resolves
5954 Changes in version 0.2.4.9-alpha - 2013-01-15
5955 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
5959 - Fix backward compatibility logic when receiving an embedded ntor
5960 handshake tunneled in a CREATE cell. This clears up the "Bug:
5961 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
5965 Changes in version 0.2.4.8-alpha - 2013-01-14
5966 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
5967 risks, adds a new stronger and faster circuit handshake, and offers
5968 stronger and faster link encryption when both sides support it.
5971 - Preliminary support for directory guards (proposal 207): when
5972 possible, clients now use their entry guards for non-anonymous
5973 directory requests. This can help prevent client enumeration. Note
5974 that this behavior only works when we have a usable consensus
5975 directory, and when options about what to download are more or less
5976 standard. In the future we should re-bootstrap from our guards,
5977 rather than re-bootstrapping from the preconfigured list of
5978 directory sources that ships with Tor. Resolves ticket 6526.
5979 - Tor relays and clients now support a better CREATE/EXTEND cell
5980 format, allowing the sender to specify multiple address, identity,
5981 and handshake types. Implements Robert Ransom's proposal 200;
5984 o Major features (new circuit handshake):
5985 - Tor now supports a new circuit extension handshake designed by Ian
5986 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
5987 circuit extension handshake, later called "TAP", was a bit slow
5988 (especially on the relay side), had a fragile security proof, and
5989 used weaker keys than we'd now prefer. The new circuit handshake
5990 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
5991 function, making it significantly more secure than the older
5992 handshake, and significantly faster. Tor can use one of two built-in
5993 pure-C curve25519-donna implementations by Adam Langley, or it
5994 can link against the "nacl" library for a tuned version if present.
5996 The built-in version is very fast for 64-bit systems when building
5997 with GCC. The built-in 32-bit version is still faster than the
5998 old TAP protocol, but using libnacl is better on most such hosts.
6000 Clients don't currently use this protocol by default, since
6001 comparatively few clients support it so far. To try it, set
6002 UseNTorHandshake to 1.
6004 Implements proposal 216; closes ticket 7202.
6006 o Major features (better link encryption):
6007 - Relays can now enable the ECDHE TLS ciphersuites when available
6008 and appropriate. These ciphersuites let us negotiate forward-secure
6009 TLS secret keys more safely and more efficiently than with our
6010 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
6011 public relays prefer the (faster) P224 group, and bridges prefer
6012 the (more common) P256 group; you can override this with the
6015 Enabling these ciphers was a little tricky, since for a long time,
6016 clients had been claiming to support them without actually doing
6017 so, in order to foil fingerprinting. But with the client-side
6018 implementation of proposal 198 in 0.2.3.17-beta, clients can now
6019 match the ciphers from recent Firefox versions *and* list the
6020 ciphers they actually mean, so relays can believe such clients
6021 when they advertise ECDHE support in their TLS ClientHello messages.
6023 This feature requires clients running 0.2.3.17-beta or later,
6024 and requires both sides to be running OpenSSL 1.0.0 or later
6025 with ECC support. OpenSSL 1.0.1, with the compile-time option
6026 "enable-ec_nistp_64_gcc_128", is highly recommended.
6028 Implements the relay side of proposal 198; closes ticket 7200.
6031 - Avoid crashing when, as a relay without IPv6-exit support, a
6032 client insists on getting an IPv6 address or nothing. Fixes bug
6033 7814; bugfix on 0.2.4.7-alpha.
6036 - Improve circuit build timeout handling for hidden services.
6037 In particular: adjust build timeouts more accurately depending
6038 upon the number of hop-RTTs that a particular circuit type
6039 undergoes. Additionally, launch intro circuits in parallel
6040 if they timeout, and take the first one to reply as valid.
6041 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
6042 separate error codes; or at least, don't break for that reason.
6043 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
6044 - Update to the January 2 2013 Maxmind GeoLite Country database.
6046 o Minor features (testing):
6047 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
6048 (P-256) Diffie-Hellman handshakes to src/or/bench.
6049 - Add benchmark functions to test onion handshake performance.
6051 o Minor features (path bias detection):
6052 - Alter the Path Bias log messages to be more descriptive in terms
6053 of reporting timeouts and other statistics.
6054 - Create three levels of Path Bias log messages, as opposed to just
6055 two. These are configurable via consensus as well as via the torrc
6056 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
6057 The default values are 0.70, 0.50, and 0.30 respectively.
6058 - Separate the log message levels from the decision to drop guards,
6059 which also is available via torrc option PathBiasDropGuards.
6060 PathBiasDropGuards still defaults to 0 (off).
6061 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
6062 in combination with PathBiasExtremeRate.
6063 - Increase the default values for PathBiasScaleThreshold and
6064 PathBiasCircThreshold from (200, 20) to (300, 150).
6065 - Add in circuit usage accounting to path bias. If we try to use a
6066 built circuit but fail for any reason, it counts as path bias.
6067 Certain classes of circuits where the adversary gets to pick your
6068 destination node are exempt from this accounting. Usage accounting
6069 can be specifically disabled via consensus parameter or torrc.
6070 - Convert all internal path bias state to double-precision floating
6071 point, to avoid roundoff error and other issues.
6072 - Only record path bias information for circuits that have completed
6073 *two* hops. Assuming end-to-end tagging is the attack vector, this
6074 makes us more resilient to ambient circuit failure without any
6075 detection capability loss.
6077 o Minor bugfixes (log messages):
6078 - Rate-limit the "No circuits are opened. Relaxed timeout for a
6079 circuit with channel state open..." message to once per hour to
6080 keep it from filling the notice logs. Mitigates bug 7799 but does
6081 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
6082 - Avoid spurious warnings when configuring multiple client ports of
6083 which only some are nonlocal. Previously, we had claimed that some
6084 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
6087 o Code simplifications and refactoring:
6088 - Get rid of a couple of harmless clang warnings, where we compared
6089 enums to ints. These warnings are newly introduced in clang 3.2.
6090 - Split the onion.c file into separate modules for the onion queue
6091 and the different handshakes it supports.
6092 - Remove the marshalling/unmarshalling code for sending requests to
6093 cpuworkers over a socket, and instead just send structs. The
6094 recipient will always be the same Tor binary as the sender, so
6095 any encoding is overkill.
6098 Changes in version 0.2.4.7-alpha - 2012-12-24
6099 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
6100 directory mirrors for more robust bootstrapping; fixes more issues where
6101 clients with changing network conditions refuse to make any circuits;
6102 adds initial support for exiting to IPv6 addresses; resumes being able
6103 to update our GeoIP database, and includes the geoip6 file this time;
6104 turns off the client-side DNS cache by default due to privacy risks;
6105 and fixes a variety of other issues.
6107 o Major features (client resilience):
6108 - Add a new "FallbackDir" torrc option to use when we can't use
6109 a directory mirror from the consensus (either because we lack a
6110 consensus, or because they're all down). Currently, all authorities
6111 are fallbacks by default, and there are no other default fallbacks,
6112 but that will change. This option will allow us to give clients a
6113 longer list of servers to try to get a consensus from when first
6114 connecting to the Tor network, and thereby reduce load on the
6115 directory authorities. Implements proposal 206, "Preconfigured
6116 directory sources for bootstrapping". We also removed the old
6117 "FallbackNetworkstatus" option, since we never got it working well
6118 enough to use it. Closes bug 572.
6119 - If we have no circuits open, use a relaxed timeout (the
6120 95-percentile cutoff) until a circuit succeeds. This heuristic
6121 should allow Tor to succeed at building circuits even when the
6122 network connection drastically changes. Should help with bug 3443.
6124 o Major features (IPv6):
6125 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
6126 connectivity, then set the IPv6Exit flag to 1. Also make sure your
6127 exit policy reads as you would like: the address * applies to all
6128 address families, whereas *4 is IPv4 address only, and *6 is IPv6
6129 addresses only. On the client side, you'll need to wait until the
6130 authorities have upgraded, wait for enough exits to support IPv6,
6131 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
6132 ticket 5547, implements proposal 117 as revised in proposal 208.
6134 We DO NOT recommend that clients with actual anonymity needs start
6135 using IPv6 over Tor yet, since not enough exits support it yet.
6137 o Major features (geoip database):
6138 - Maxmind began labelling Tor relays as being in country "A1",
6139 which breaks by-country node selection inside Tor. Now we use a
6140 script to replace "A1" ("Anonymous Proxy") entries in our geoip
6141 file with real country codes. This script fixes about 90% of "A1"
6142 entries automatically and uses manual country code assignments to
6143 fix the remaining 10%. See src/config/README.geoip for details.
6144 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
6145 Country database, as modified above.
6147 o Major bugfixes (client-side DNS):
6148 - Turn off the client-side DNS cache by default. Updating and using
6149 the DNS cache is now configurable on a per-client-port
6150 level. SOCKSPort, DNSPort, etc lines may now contain
6151 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
6152 cache these types of DNS answers when we receive them from an
6153 exit node in response to an application request on this port, and
6154 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
6155 cached DNS answers of these types, we shouldn't use them. It's
6156 potentially risky to use cached DNS answers at the client, since
6157 doing so can indicate to one exit what answers we've gotten
6158 for DNS lookups in the past. With IPv6, this becomes especially
6159 problematic. Using cached DNS answers for requests on the same
6160 circuit would present less linkability risk, since all traffic
6161 on a circuit is already linkable, but it would also provide
6162 little performance benefit: the exit node caches DNS replies
6163 too. Implements a simplified version of Proposal 205. Implements
6166 o Major bugfixes (other):
6167 - Alter circuit build timeout measurement to start at the point
6168 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
6169 initialization). This should make our timeout measurements more
6170 uniform. Previously, we were sometimes including ORconn setup time
6171 in our circuit build time measurements. Should resolve bug 3443.
6172 - Fix an assertion that could trigger in hibernate_go_dormant() when
6173 closing an or_connection_t: call channel_mark_for_close() rather
6174 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
6176 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
6177 7655; bugfix on 0.2.4.6-alpha.
6180 - Add a new torrc option "ServerTransportListenAddr" to let bridge
6181 operators select the address where their pluggable transports will
6182 listen for connections. Resolves ticket 7013.
6183 - Allow an optional $ before the node identity digest in the
6184 controller command GETINFO ns/id/<identity>, for consistency with
6185 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
6186 - Log packaged cell fullness as part of the heartbeat message.
6187 Diagnosis to try to determine the extent of bug 7743.
6189 o Minor features (IPv6):
6190 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
6191 prefer to hand out virtual IPv6 addresses, since there are more of
6192 them and we can't run out. To override this behavior and make IPv4
6193 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
6194 or DNSPort you're using for resolving. Implements ticket 7571.
6195 - AutomapHostsOnResolve responses are now randomized, to avoid
6196 annoying situations where Tor is restarted and applications
6197 connect to the wrong addresses.
6198 - Never try more than 1000 times to pick a new virtual address when
6199 AutomapHostsOnResolve is set. That's good enough so long as we
6200 aren't close to handing out our entire virtual address space;
6201 if you're getting there, it's best to switch to IPv6 virtual
6205 - The ADDRMAP command can no longer generate an ill-formed error
6206 code on a failed MAPADDRESS. It now says "internal" rather than
6207 an English sentence fragment with spaces in the middle. Bugfix on
6209 - Fix log messages and comments to avoid saying "GMT" when we mean
6210 "UTC". Fixes bug 6113.
6211 - Compile on win64 using mingw64. Fixes bug 7260; patches from
6213 - Fix a crash when debugging unit tests on Windows: deallocate a
6214 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
6215 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
6218 - The DirServer option is now DirAuthority, for consistency with
6219 current naming patterns. You can still use the old DirServer form.
6221 o Code simplification and refactoring:
6222 - Move the client-side address-map/virtual-address/DNS-cache code
6223 out of connection_edge.c into a new addressmap.c module.
6224 - Remove unused code for parsing v1 directories and "running routers"
6225 documents. Fixes bug 6887.
6228 Changes in version 0.2.3.25 - 2012-11-19
6229 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
6230 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
6231 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
6232 programmer, and friend. Unstinting in his dedication to the cause of
6233 freedom, he inspired and helped many of us as we began our work on
6234 anonymity, and inspires us still. Please honor his memory by writing
6235 software to protect people's freedoms, and by helping others to do so.
6237 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
6238 significantly reduced directory overhead (via microdescriptors),
6239 enormous crypto performance improvements for fast relays on new
6240 enough hardware, a new v3 TLS handshake protocol that can better
6241 resist fingerprinting, support for protocol obfuscation plugins (aka
6242 pluggable transports), better scalability for hidden services, IPv6
6243 support for bridges, performance improvements like allowing clients
6244 to skip the first round-trip on the circuit ("optimistic data") and
6245 refilling token buckets more often, a new "stream isolation" design
6246 to isolate different applications on different circuits, and many
6247 stability, security, and privacy fixes.
6250 - Tor tries to wipe potentially sensitive data after using it, so
6251 that if some subsequent security failure exposes Tor's memory,
6252 the damage will be limited. But we had a bug where the compiler
6253 was eliminating these wipe operations when it decided that the
6254 memory was no longer visible to a (correctly running) program,
6255 hence defeating our attempt at defense in depth. We fix that
6256 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6257 is unlikely to optimize away. Future versions of Tor may use
6258 a less ridiculously heavy approach for this. Fixes bug 7352.
6259 Reported in an article by Andrey Karpov.
6262 - Fix a harmless bug when opting against publishing a relay descriptor
6263 because DisableNetwork is set. Fixes bug 7464; bugfix on
6267 Changes in version 0.2.4.6-alpha - 2012-11-13
6268 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
6269 makes our defense-in-depth memory wiping more reliable, and begins to
6270 count IPv6 addresses in bridge statistics,
6273 - Fix an assertion failure that could occur when closing a connection
6274 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
6276 - Tor tries to wipe potentially sensitive data after using it, so
6277 that if some subsequent security failure exposes Tor's memory,
6278 the damage will be limited. But we had a bug where the compiler
6279 was eliminating these wipe operations when it decided that the
6280 memory was no longer visible to a (correctly running) program,
6281 hence defeating our attempt at defense in depth. We fix that
6282 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6283 is unlikely to optimize away. Future versions of Tor may use
6284 a less ridiculously heavy approach for this. Fixes bug 7352.
6285 Reported in an article by Andrey Karpov.
6288 - Add GeoIP database for IPv6 addresses. The new config option
6290 - Bridge statistics now count bridge clients connecting over IPv6:
6291 bridge statistics files now list "bridge-ip-versions" and
6292 extra-info documents list "geoip6-db-digest". The control protocol
6293 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
6294 implementation by "shkoo", addressing ticket 5055.
6297 - Warn when we are binding low ports when hibernation is enabled;
6298 previously we had warned when we were _advertising_ low ports with
6299 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
6300 - Fix a harmless bug when opting against publishing a relay descriptor
6301 because DisableNetwork is set. Fixes bug 7464; bugfix on
6303 - Add warning message when a managed proxy dies during configuration.
6304 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
6305 - Fix a linking error when building tor-fw-helper without miniupnp.
6306 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
6307 - Check for closing an or_connection_t without going through correct
6308 channel functions; emit a warning and then call
6309 connection_or_close_for_error() so we don't assert as in bugs 7212
6311 - Compile correctly on compilers without C99 designated initializer
6312 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
6313 - Avoid a possible assert that can occur when channel_send_destroy() is
6314 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
6315 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
6316 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
6317 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
6318 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
6320 o Code simplification and refactoring:
6321 - Start using OpenBSD's implementation of queue.h, so that we don't
6322 need to hand-roll our own pointer and list structures whenever we
6323 need them. (We can't rely on a sys/queue.h, since some operating
6324 systems don't have them, and the ones that do have them don't all
6325 present the same extensions.)
6328 Changes in version 0.2.4.5-alpha - 2012-10-25
6329 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
6330 two important security vulnerabilities that could lead to remotely
6331 triggerable relay crashes, fix a major bug that was preventing clients
6332 from choosing suitable exit nodes, and refactor some of our code.
6334 o Major bugfixes (security, also in 0.2.3.24-rc):
6335 - Fix a group of remotely triggerable assertion failures related to
6336 incorrect link protocol negotiation. Found, diagnosed, and fixed
6337 by "some guy from France". Fix for CVE-2012-2250; bugfix on
6339 - Fix a denial of service attack by which any directory authority
6340 could crash all the others, or by which a single v2 directory
6341 authority could crash everybody downloading v2 directory
6342 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6344 o Major bugfixes (also in 0.2.3.24-rc):
6345 - When parsing exit policy summaries from microdescriptors, we had
6346 previously been ignoring the last character in each one, so that
6347 "accept 80,443,8080" would be treated by clients as indicating
6348 a node that allows access to ports 80, 443, and 808. That would
6349 lead to clients attempting connections that could never work,
6350 and ignoring exit nodes that would support their connections. Now
6351 clients parse these exit policy summaries correctly. Fixes bug 7192;
6352 bugfix on 0.2.3.1-alpha.
6354 o Minor bugfixes (also in 0.2.3.24-rc):
6355 - Clients now consider the ClientRejectInternalAddresses config option
6356 when using a microdescriptor consensus stanza to decide whether
6357 an exit relay would allow exiting to an internal address. Fixes
6358 bug 7190; bugfix on 0.2.3.1-alpha.
6361 - Only disable TLS session ticket support when running as a TLS
6362 server. Now clients will blend better with regular Firefox
6363 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
6365 o Code simplification and refactoring:
6366 - Start using OpenBSD's implementation of queue.h (originally by
6368 - Move the entry node code from circuitbuild.c to its own file.
6369 - Move the circuit build timeout tracking code from circuitbuild.c
6373 Changes in version 0.2.3.24-rc - 2012-10-25
6374 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
6375 could lead to remotely triggerable relay crashes, and fixes
6376 a major bug that was preventing clients from choosing suitable exit
6379 o Major bugfixes (security):
6380 - Fix a group of remotely triggerable assertion failures related to
6381 incorrect link protocol negotiation. Found, diagnosed, and fixed
6382 by "some guy from France". Fix for CVE-2012-2250; bugfix on
6384 - Fix a denial of service attack by which any directory authority
6385 could crash all the others, or by which a single v2 directory
6386 authority could crash everybody downloading v2 directory
6387 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6390 - When parsing exit policy summaries from microdescriptors, we had
6391 previously been ignoring the last character in each one, so that
6392 "accept 80,443,8080" would be treated by clients as indicating
6393 a node that allows access to ports 80, 443, and 808. That would
6394 lead to clients attempting connections that could never work,
6395 and ignoring exit nodes that would support their connections. Now
6396 clients parse these exit policy summaries correctly. Fixes bug 7192;
6397 bugfix on 0.2.3.1-alpha.
6400 - Clients now consider the ClientRejectInternalAddresses config option
6401 when using a microdescriptor consensus stanza to decide whether
6402 an exit relay would allow exiting to an internal address. Fixes
6403 bug 7190; bugfix on 0.2.3.1-alpha.
6406 Changes in version 0.2.4.4-alpha - 2012-10-20
6407 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
6408 vulnerability introduced by a change in OpenSSL, fixes a remotely
6409 triggerable assert, and adds new channel_t and circuitmux_t abstractions
6410 that will make it easier to test new connection transport and cell
6411 scheduling algorithms.
6413 o New directory authorities (also in 0.2.3.23-rc):
6414 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6415 authority. Closes ticket 5749.
6417 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
6418 - Disable TLS session tickets. OpenSSL's implementation was giving
6419 our TLS session keys the lifetime of our TLS context objects, when
6420 perfect forward secrecy would want us to discard anything that
6421 could decrypt a link connection as soon as the link connection
6422 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6423 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6424 - Discard extraneous renegotiation attempts once the V3 link
6425 protocol has been initiated. Failure to do so left us open to
6426 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
6427 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
6429 o Internal abstraction features:
6430 - Introduce new channel_t abstraction between circuits and
6431 or_connection_t to allow for implementing alternate OR-to-OR
6432 transports. A channel_t is an abstract object which can either be a
6433 cell-bearing channel, which is responsible for authenticating and
6434 handshaking with the remote OR and transmitting cells to and from
6435 it, or a listening channel, which spawns new cell-bearing channels
6436 at the request of remote ORs. Implements part of ticket 6465.
6437 - Also new is the channel_tls_t subclass of channel_t, adapting it
6438 to the existing or_connection_t code. The V2/V3 protocol handshaking
6439 code which formerly resided in command.c has been moved below the
6440 channel_t abstraction layer and may be found in channeltls.c now.
6441 Implements the rest of ticket 6465.
6442 - Introduce new circuitmux_t storing the queue of circuits for
6443 a channel; this encapsulates and abstracts the queue logic and
6444 circuit selection policy, and allows the latter to be overridden
6445 easily by switching out a policy object. The existing EWMA behavior
6446 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
6448 o Required libraries:
6449 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
6450 strongly recommended.
6453 - Warn users who run hidden services on a Tor client with
6454 UseEntryGuards disabled that their hidden services will be
6455 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
6456 attack which motivated Tor to support entry guards in the first
6457 place). Resolves ticket 6889.
6458 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
6459 dhill. Resolves ticket 6982.
6460 - Option OutboundBindAddress can be specified multiple times and
6461 accepts IPv6 addresses. Resolves ticket 6876.
6463 o Minor bugfixes (also in 0.2.3.23-rc):
6464 - Don't serve or accept v2 hidden service descriptors over a
6465 relay's DirPort. It's never correct to do so, and disabling it
6466 might make it more annoying to exploit any bugs that turn up in the
6467 descriptor-parsing code. Fixes bug 7149.
6468 - Fix two cases in src/or/transports.c where we were calling
6469 fmt_addr() twice in a parameter list. Bug found by David
6470 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
6471 - Fix memory leaks whenever we logged any message about the "path
6472 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
6473 - When relays refuse a "create" cell because their queue of pending
6474 create cells is too big (typically because their cpu can't keep up
6475 with the arrival rate), send back reason "resource limit" rather
6476 than reason "internal", so network measurement scripts can get a
6477 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
6480 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
6481 - Free some more still-in-use memory at exit, to make hunting for
6482 memory leaks easier. Resolves bug 7029.
6483 - When a Tor client gets a "truncated" relay cell, the first byte of
6484 its payload specifies why the circuit was truncated. We were
6485 ignoring this 'reason' byte when tearing down the circuit, resulting
6486 in the controller not being told why the circuit closed. Now we
6487 pass the reason from the truncated cell to the controller. Bugfix
6488 on 0.1.2.3-alpha; fixes bug 7039.
6489 - Downgrade "Failed to hand off onionskin" messages to "debug"
6490 severity, since they're typically redundant with the "Your computer
6491 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
6492 - Make clients running with IPv6 bridges connect over IPv6 again,
6493 even without setting new config options ClientUseIPv6 and
6494 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
6495 - Use square brackets around IPv6 addresses in numerous places
6496 that needed them, including log messages, HTTPS CONNECT proxy
6497 requests, TransportProxy statefile entries, and pluggable transport
6498 extra-info lines. Fixes bug 7011; patch by David Fifield.
6500 o Code refactoring and cleanup:
6501 - Source files taken from other packages now reside in src/ext;
6502 previously they were scattered around the rest of Tor.
6503 - Avoid use of reserved identifiers in our C code. The C standard
6504 doesn't like us declaring anything that starts with an
6505 underscore, so let's knock it off before we get in trouble. Fix
6506 for bug 1031; bugfix on the first Tor commit.
6509 Changes in version 0.2.3.23-rc - 2012-10-20
6510 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
6511 vulnerability introduced by a change in OpenSSL, and fixes a variety
6512 of smaller bugs in preparation for the release.
6514 o New directory authorities:
6515 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6516 authority. Closes ticket 5749.
6518 o Major bugfixes (security/privacy):
6519 - Disable TLS session tickets. OpenSSL's implementation was giving
6520 our TLS session keys the lifetime of our TLS context objects, when
6521 perfect forward secrecy would want us to discard anything that
6522 could decrypt a link connection as soon as the link connection
6523 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6524 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6525 - Discard extraneous renegotiation attempts once the V3 link
6526 protocol has been initiated. Failure to do so left us open to
6527 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
6528 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
6531 - Fix a possible crash bug when checking for deactivated circuits
6532 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6533 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6535 o Minor bugfixes (on 0.2.3.x):
6536 - Fix two cases in src/or/transports.c where we were calling
6537 fmt_addr() twice in a parameter list. Bug found by David
6538 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
6539 - Convert an assert in the pathbias code to a log message. The assert
6540 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
6541 bugfix on 0.2.3.17-beta.
6542 - Fix memory leaks whenever we logged any message about the "path
6543 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
6545 o Minor bugfixes (on 0.2.2.x and earlier):
6546 - Don't serve or accept v2 hidden service descriptors over a relay's
6547 DirPort. It's never correct to do so, and disabling it might
6548 make it more annoying to exploit any bugs that turn up in the
6549 descriptor-parsing code. Fixes bug 7149.
6550 - When relays refuse a "create" cell because their queue of pending
6551 create cells is too big (typically because their cpu can't keep up
6552 with the arrival rate), send back reason "resource limit" rather
6553 than reason "internal", so network measurement scripts can get a
6554 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
6555 - Correct file sizes when reading binary files on Cygwin, to avoid
6556 a bug where Tor would fail to read its state file. Fixes bug 6844;
6557 bugfix on 0.1.2.7-alpha.
6558 - Avoid undefined behavior when parsing the list of supported
6559 rendezvous/introduction protocols in a hidden service descriptor.
6560 Previously, Tor would have confused (as-yet-unused) protocol version
6561 numbers greater than 32 with lower ones on many platforms. Fixes
6562 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6564 o Documentation fixes:
6565 - Clarify that hidden services are TCP only. Fixes bug 6024.
6568 Changes in version 0.2.4.3-alpha - 2012-09-22
6569 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
6570 assertion, resumes letting relays test reachability of their DirPort,
6571 and cleans up a bunch of smaller bugs.
6574 - Fix an assertion failure in tor_timegm() that could be triggered
6575 by a badly formatted directory object. Bug found by fuzzing with
6576 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6579 - Fix a possible crash bug when checking for deactivated circuits
6580 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6581 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6582 - Allow routers to detect that their own DirPorts are running. When
6583 we removed support for versions_supports_begindir, we also
6584 accidentally removed the mechanism we used to self-test our
6585 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
6586 bugfix on 0.2.4.2-alpha.
6588 o Security features:
6589 - Switch to a completely time-invariant approach for picking nodes
6590 weighted by bandwidth. Our old approach would run through the
6591 part of the loop after it had made its choice slightly slower
6592 than it ran through the part of the loop before it had made its
6593 choice. Addresses ticket 6538.
6594 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
6595 by tor2web clients allows hidden services to identify tor2web
6596 clients through their repeated selection of the same rendezvous
6597 and introduction point circuit endpoints (their guards). Resolves
6601 - Enable Tor to read configuration, state, and key information from
6602 a FIFO. Previously Tor would only read from files with a positive
6603 stat.st_size. Code from meejah; fixes bug 6044.
6606 - Correct file sizes when reading binary files on Cygwin, to avoid
6607 a bug where Tor would fail to read its state file. Fixes bug 6844;
6608 bugfix on 0.1.2.7-alpha.
6609 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
6610 bugfix on 0.2.0.3-alpha.
6611 - When complaining about a client port on a public address, log
6612 which address we're complaining about. Fixes bug 4020; bugfix on
6613 0.2.3.3-alpha. Patch by Tom Fitzhenry.
6614 - Convert an assert in the pathbias code to a log message. The assert
6615 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
6616 bugfix on 0.2.3.17-beta.
6617 - Our new buildsystem was overzealous about rebuilding manpages: it
6618 would rebuild them all whenever any one of them changed. Now our
6619 dependency checking should be correct. Fixes bug 6843; bugfix on
6621 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
6622 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
6623 - Correct log printout about which address family is preferred
6624 when connecting to a bridge with both an IPv4 and IPv6 OR port.
6625 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
6627 o Minor bugfixes (code cleanliness):
6628 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
6629 with large values. This situation was untriggered, but nevertheless
6630 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
6631 - Reject consensus votes with more than 64 known-flags. We aren't even
6632 close to that limit yet, and our code doesn't handle it correctly.
6633 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
6634 - Avoid undefined behavior when parsing the list of supported
6635 rendezvous/introduction protocols in a hidden service descriptor.
6636 Previously, Tor would have confused (as-yet-unused) protocol version
6637 numbers greater than 32 with lower ones on many platforms. Fixes
6638 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6639 - Fix handling of rendezvous client authorization types over 8.
6640 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
6641 - Fix building with older versions of GCC (2.95, for one) that don't
6642 like preprocessor directives inside macro arguments. Found by
6643 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
6644 - Switch weighted node selection rule from using a list of doubles
6645 to using a list of int64_t. This change should make the process
6646 slightly easier to debug and maintain. Needed to finish ticket 6538.
6648 o Code simplification and refactoring:
6649 - Move the generic "config" code into a new file, and have "config.c"
6650 hold only torrc- and state-related code. Resolves ticket 6823.
6651 - Move the core of our "choose a weighted element at random" logic
6652 into its own function, and give it unit tests. Now the logic is
6653 testable, and a little less fragile too.
6654 - Removed the testing_since field of node_t, which hasn't been used
6655 for anything since 0.2.0.9-alpha.
6657 o Documentation fixes:
6658 - Clarify that hidden services are TCP only. Fixes bug 6024.
6659 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
6663 Changes in version 0.2.3.22-rc - 2012-09-11
6664 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
6668 - Fix an assertion failure in tor_timegm() that could be triggered
6669 by a badly formatted directory object. Bug found by fuzzing with
6670 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6673 - Avoid segfault when starting up having run with an extremely old
6674 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6678 Changes in version 0.2.2.39 - 2012-09-11
6679 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
6683 - Fix an assertion failure in tor_timegm() that could be triggered
6684 by a badly formatted directory object. Bug found by fuzzing with
6685 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6686 - Do not crash when comparing an address with port value 0 to an
6687 address policy. This bug could have been used to cause a remote
6688 assertion failure by or against directory authorities, or to
6689 allow some applications to crash clients. Fixes bug 6690; bugfix
6693 Changes in version 0.2.4.2-alpha - 2012-09-10
6694 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
6695 raises the default rate limiting even more, and makes the bootstrapping
6696 log messages less noisy.
6699 - Automatically forward the TCP ports of pluggable transport
6700 proxies using tor-fw-helper if PortForwarding is enabled. Implements
6704 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
6705 to 1GB/1GB. The previous defaults were intended to be "basically
6706 infinite", but it turns out they're now limiting our 100mbit+
6707 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
6708 last time we raised it).
6711 - Detect when we're running with a version of OpenSSL other than the
6712 one we compiled with. This has occasionally given people hard-to-
6714 - Log fewer lines at level "notice" about our OpenSSL and Libevent
6715 versions and capabilities when everything is going right. Resolves
6716 part of ticket 6736.
6717 - Directory authorities no long accept descriptors for any version of
6718 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
6719 These versions are insecure, unsupported, or both. Implements
6723 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
6724 to start with a triple-underscore so the controller won't touch it.
6725 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
6726 - Avoid segfault when starting up having run with an extremely old
6727 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6729 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
6730 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
6731 - Don't follow the NULL pointer if microdescriptor generation fails.
6732 (This does not appear to be triggerable, but it's best to be safe.)
6733 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
6734 - Fix mis-declared dependencies on src/common/crypto.c and
6735 src/or/tor_main.c that could break out-of-tree builds under some
6736 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
6737 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
6738 6778; bugfix on 0.2.4.1-alpha.
6739 - Fix a harmless (in this case) build warning for implicitly
6740 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
6743 - Now that all versions before 0.2.2.x are disallowed, we no longer
6744 need to work around their missing features. Thus we can remove a
6745 bunch of compatibility code.
6748 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
6749 TCP ports to forward. In the past it only accepted two ports:
6750 the ORPort and the DirPort.
6753 Changes in version 0.2.4.1-alpha - 2012-09-05
6754 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
6755 bridgedb; lets relays use IPv6 addresses and directory authorities
6756 advertise them; and switches to a cleaner build interface.
6758 This is the first alpha release in a new series, so expect there to
6759 be bugs. Users who would rather test out a more stable branch should
6760 stay with 0.2.3.x for now.
6762 o Major features (bridges):
6763 - Bridges now report the pluggable transports they support to the
6764 bridge authority, so it can pass the supported transports on to
6765 bridgedb and/or eventually do reachability testing. Implements
6768 o Major features (IPv6):
6769 - Bridge authorities now accept IPv6 bridge addresses and include
6770 them in network status documents. Implements ticket 5534.
6771 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
6772 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
6773 to happen. Implements ticket 5535.
6774 - All kind of relays, not just bridges, can now advertise an IPv6
6775 OR port. Implements ticket 6362.
6776 - Directory authorities vote on IPv6 OR ports using the new consensus
6777 method 14. Implements ticket 6363.
6779 o Major features (build):
6780 - Switch to a nonrecursive Makefile structure. Now instead of each
6781 Makefile.am invoking other Makefile.am's, there is a master
6782 Makefile.am that includes the others. This change makes our build
6783 process slightly more maintainable, and improves parallelism for
6784 building with make -j. Original patch by Stewart Smith; various
6785 fixes by Jim Meyering.
6786 - Where available, we now use automake's "silent" make rules by
6787 default, so that warnings are easier to spot. You can get the old
6788 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
6790 o Minor features (code security and spec conformance):
6791 - Clear keys and key-derived material left on the stack in
6792 rendservice.c and rendclient.c. Check return value of
6793 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
6794 These fixes should make us more forward-secure against cold-boot
6795 attacks and the like. Fixes bug 2385.
6796 - Reject EXTEND cells sent to nonexistent streams. According to the
6797 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
6798 we were only checking for stream IDs that were currently in use.
6799 Found while hunting for more instances of bug 6271. Bugfix on
6800 0.0.2pre8, which introduced incremental circuit construction.
6802 o Minor features (streamlining);
6803 - No longer include the "opt" prefix when generating routerinfos
6804 or v2 directories: it has been needless since Tor 0.1.2. Closes
6806 - Remove some now-needless code that tried to aggressively flush
6807 OR connections as data was added to them. Since 0.2.0.1-alpha, our
6808 cell queue logic has saved us from the failure mode that this code
6809 was supposed to prevent. Removing this code will limit the number
6810 of baroque control flow paths through Tor's network logic. Reported
6811 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
6813 o Minor features (controller):
6814 - Add a "GETINFO signal/names" control port command. Implements
6816 - Provide default values for all options via "GETINFO config/defaults".
6817 Implements ticket 4971.
6819 o Minor features (IPv6):
6820 - New config option "AuthDirHasIPv6Connectivity 1" that directory
6821 authorities should set if they have IPv6 connectivity and want to
6822 do reachability tests for IPv6 relays. Implements feature 5974.
6823 - A relay with an IPv6 OR port now sends that address in NETINFO
6824 cells (in addition to its other address). Implements ticket 6364.
6826 o Minor features (log messages):
6827 - Omit the first heartbeat log message, because it never has anything
6828 useful to say, and it clutters up the bootstrapping messages.
6829 Resolves ticket 6758.
6830 - Don't log about reloading the microdescriptor cache at startup. Our
6831 bootstrap warnings are supposed to tell the user when there's a
6832 problem, and our bootstrap notices say when there isn't. Resolves
6833 ticket 6759; bugfix on 0.2.2.6-alpha.
6834 - Don't log "I learned some more directory information" when we're
6835 reading cached directory information. Reserve it for when new
6836 directory information arrives in response to a fetch. Resolves
6838 - Prevent rounding error in path bias counts when scaling
6839 them down, and use the correct scale factor default. Also demote
6840 some path bias related log messages down a level and make others
6841 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
6842 - We no longer warn so much when generating manpages from their
6845 o Code simplifications and refactoring:
6846 - Enhance our internal sscanf replacement so that we can eliminate
6847 the last remaining uses of the system sscanf. (Though those uses
6848 of sscanf were safe, sscanf itself is generally error prone, so
6849 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
6851 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
6852 - Move last_reachable and testing_since from routerinfo_t to node_t.
6853 Implements ticket 5529.
6854 - Add replaycache_t structure, functions and unit tests, then refactor
6855 rend_service_introduce() to be more clear to read, improve, debug,
6856 and test. Resolves bug 6177.
6857 - Finally remove support for malloc_good_size and malloc_usable_size.
6858 We had hoped that these functions would let us eke a little more
6859 memory out of our malloc implementation. Unfortunately, the only
6860 implementations that provided these functions are also ones that
6861 are already efficient about not overallocation: they never got us
6862 more than 7 or so bytes per allocation. Removing them saves us a
6863 little code complexity and a nontrivial amount of build complexity.
6866 - Tor maintainers now require Automake version 1.9 or later to build
6867 Tor from the Git repository. (Automake is not required when building
6868 from a source distribution.)
6871 Changes in version 0.2.3.21-rc - 2012-09-05
6872 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
6873 series. It fixes a trio of potential security bugs, fixes a bug where
6874 we were leaving some of the fast relays out of the microdescriptor
6875 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
6876 and cleans up other smaller issues.
6878 o Major bugfixes (security):
6879 - Tear down the circuit if we get an unexpected SENDME cell. Clients
6880 could use this trick to make their circuits receive cells faster
6881 than our flow control would have allowed, or to gum up the network,
6882 or possibly to do targeted memory denial-of-service attacks on
6883 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
6884 from July 2002, before the release of Tor 0.0.0. We had committed
6885 this patch previously, but we had to revert it because of bug 6271.
6886 Now that 6271 is fixed, this patch appears to work.
6887 - Reject any attempt to extend to an internal address. Without
6888 this fix, a router could be used to probe addresses on an internal
6889 network to see whether they were accepting connections. Fixes bug
6890 6710; bugfix on 0.0.8pre1.
6891 - Do not crash when comparing an address with port value 0 to an
6892 address policy. This bug could have been used to cause a remote
6893 assertion failure by or against directory authorities, or to
6894 allow some applications to crash clients. Fixes bug 6690; bugfix
6898 - Remove the upper bound on microdescriptor length. We were hitting
6899 the limit for routers with complex exit policies or family
6900 declarations, causing clients to not use them. Fixes the first
6901 piece of bug 6404; fix on 0.2.2.6-alpha.
6902 - Detect "ORPort 0" as meaning, uniformly, that we're not running
6903 as a relay. Previously, some of our code would treat the presence
6904 of any ORPort line as meaning that we should act like a relay,
6905 even though our new listener code would correctly not open any
6906 ORPorts for ORPort 0. Similar bugs in other Port options are also
6907 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
6910 - Avoid a pair of double-free and use-after-mark bugs that can
6911 occur with certain timings in canceled and re-received DNS
6912 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
6913 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
6914 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
6915 - Allow one-hop directory fetching circuits the full "circuit build
6916 timeout" period, rather than just half of it, before failing them
6917 and marking the relay down. This fix should help reduce cases where
6918 clients declare relays (or worse, bridges) unreachable because
6919 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
6920 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
6922 - Authorities no longer include any router in their microdescriptor
6923 consensuses for which they couldn't generate or agree on a
6924 microdescriptor. Fixes the second piece of bug 6404; fix on
6926 - Detect and reject attempts to specify both "FooPort" and
6927 "FooPort 0" in the same configuration domain. (It's still okay
6928 to have a FooPort in your configuration file, and use "FooPort 0"
6929 on the command line to disable it.) Fixes the second half of bug
6930 6507; bugfix on 0.2.3.3-alpha.
6931 - Make wildcarded addresses (that is, ones beginning with "*.") work
6932 when provided via the controller's MapAddress command. Previously,
6933 they were accepted, but we never actually noticed that they were
6934 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
6935 - Avoid crashing on a malformed state file where EntryGuardPathBias
6936 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
6937 - Add a (probably redundant) memory clear between iterations of
6938 the router status voting loop, to prevent future coding errors
6939 where data might leak between iterations of the loop. Resolves
6942 o Minor bugfixes (log messages):
6943 - Downgrade "set buildtimeout to low value" messages to "info"
6944 severity; they were never an actual problem, there was never
6945 anything reasonable to do about them, and they tended to spam logs
6946 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
6947 - Downgrade path-bias warning messages to "info". We'll try to get
6948 them working better in 0.2.4. Add internal circuit construction
6949 state to protect against the noisy warn message "Unexpectedly high
6950 circuit_successes". Also add some additional rate-limited notice
6951 messages to help determine the root cause of the warn. Fixes bug
6952 6475. Bugfix against 0.2.3.17-beta.
6953 - Move log message when unable to find a microdesc in a routerstatus
6954 entry to parse time. Previously we'd spam this warning every time
6955 we tried to figure out which microdescriptors to download. Fixes
6956 the third piece of bug 6404; fix on 0.2.3.18-rc.
6959 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
6960 change when the authority is deciding whether to accept a newly
6961 uploaded descriptor. Implements ticket 6423.
6962 - Add missing documentation for consensus and microdesc files.
6963 Resolves ticket 6732.
6966 Changes in version 0.2.2.38 - 2012-08-12
6967 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
6968 attack that could in theory leak path information.
6971 - Avoid an uninitialized memory read when reading a vote or consensus
6972 document that has an unrecognized flavor name. This read could
6973 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6974 - Try to leak less information about what relays a client is
6975 choosing to a side-channel attacker. Previously, a Tor client would
6976 stop iterating through the list of available relays as soon as it
6977 had chosen one, thus finishing a little earlier when it picked
6978 a router earlier in the list. If an attacker can recover this
6979 timing information (nontrivial but not proven to be impossible),
6980 they could learn some coarse-grained information about which relays
6981 a client was picking (middle nodes in particular are likelier to
6982 be affected than exits). The timing attack might be mitigated by
6983 other factors (see bug 6537 for some discussion), but it's best
6984 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6987 Changes in version 0.2.3.20-rc - 2012-08-05
6988 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
6989 series. It fixes a pair of code security bugs and a potential anonymity
6990 issue, updates our RPM spec files, and cleans up other smaller issues.
6993 - Avoid read-from-freed-memory and double-free bugs that could occur
6994 when a DNS request fails while launching it. Fixes bug 6480;
6995 bugfix on 0.2.0.1-alpha.
6996 - Avoid an uninitialized memory read when reading a vote or consensus
6997 document that has an unrecognized flavor name. This read could
6998 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6999 - Try to leak less information about what relays a client is
7000 choosing to a side-channel attacker. Previously, a Tor client would
7001 stop iterating through the list of available relays as soon as it
7002 had chosen one, thus finishing a little earlier when it picked
7003 a router earlier in the list. If an attacker can recover this
7004 timing information (nontrivial but not proven to be impossible),
7005 they could learn some coarse-grained information about which relays
7006 a client was picking (middle nodes in particular are likelier to
7007 be affected than exits). The timing attack might be mitigated by
7008 other factors (see bug 6537 for some discussion), but it's best
7009 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
7012 - Try to make the warning when giving an obsolete SOCKSListenAddress
7013 a little more useful.
7014 - Terminate active server managed proxies if Tor stops being a
7015 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
7016 - Provide a better error message about possible OSX Asciidoc failure
7017 reasons. Fixes bug 6436.
7018 - Warn when Tor is configured to use accounting in a way that can
7019 link a hidden service to some other hidden service or public
7020 address. Resolves ticket 6490.
7023 - Check return value of fputs() when writing authority certificate
7024 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
7025 - Ignore ServerTransportPlugin lines when Tor is not configured as
7026 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
7027 - When disabling guards for having too high a proportion of failed
7028 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
7032 - Update our default RPM spec files to work with mock and rpmbuild
7033 on RHEL/Fedora. They have an updated set of dependencies and
7034 conflicts, a fix for an ancient typo when creating the "_tor"
7035 user, and better instructions. Thanks to Ondrej Mikle for the
7036 patch series. Fixes bug 6043.
7039 - Make it possible to set the TestingTorNetwork configuration
7040 option using AlternateDirAuthority and AlternateBridgeAuthority
7041 as an alternative to setting DirServer. Addresses ticket 6377.
7044 - Clarify the documentation for the Alternate*Authority options.
7046 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
7048 o Code simplification and refactoring:
7049 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
7050 10 lines. Also, don't nest them. Doing so in the past has
7051 led to hard-to-debug code. The new style is to use the
7052 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
7055 Changes in version 0.2.3.19-rc - 2012-07-06
7056 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
7057 series. It fixes the compile on Windows, reverts to a GeoIP database
7058 that isn't as broken, and fixes a flow control bug that has been around
7059 since the beginning of Tor.
7062 - Fix a bug handling SENDME cells on nonexistent streams that could
7063 result in bizarre window values. Report and patch contributed
7064 pseudonymously. Fixes part of bug 6271. This bug was introduced
7065 before the first Tor release, in svn commit r152.
7066 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
7067 June 2012 database, Maxmind marked many Tor relays as country "A1",
7068 which will cause risky behavior for clients that set EntryNodes
7069 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
7070 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
7071 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
7074 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
7075 bugfix on 0.2.1.10-alpha.
7078 Changes in version 0.2.3.18-rc - 2012-06-28
7079 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
7080 series. It fixes a few smaller bugs, but generally appears stable.
7081 Please test it and let us know whether it is!
7084 - Allow wildcarded mapaddress targets to be specified on the
7085 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
7086 - Make our linker option detection code more robust against linkers
7087 such as on FreeBSD 8, where a bad combination of options completes
7088 successfully but makes an unrunnable binary. Fixes bug 6173;
7089 bugfix on 0.2.3.17-beta.
7091 o Minor bugfixes (on 0.2.2.x and earlier):
7092 - Avoid a false positive in the util/threads unit test by increasing
7093 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
7094 - Replace "Sending publish request" log messages with "Launching
7095 upload", so that they no longer confusingly imply that we're
7096 sending something to a directory we might not even be connected
7097 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
7098 - Make sure to set *socket_error in all error cases in
7099 connection_connect(), so it can't produce a warning about
7100 errno being zero from errno_to_orconn_end_reason(). Bugfix on
7101 0.2.1.1-alpha; resolves ticket 6028.
7102 - Downgrade "Got a certificate, but we already have it" log messages
7103 from warning to info, except when we're a dirauth. Fixes bug 5238;
7104 bugfix on 0.2.1.7-alpha.
7105 - When checking for requested signatures on the latest consensus
7106 before serving it to a client, make sure to check the right
7107 consensus flavor. Bugfix on 0.2.2.6-alpha.
7108 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
7109 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
7111 o Minor bugfixes (on 0.2.3.x):
7112 - Make format_helper_exit_status() avoid unnecessary space padding
7113 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
7115 - Downgrade a message about cleaning the microdescriptor cache to
7116 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
7117 - Log a BUG message at severity INFO if we have a networkstatus with
7118 a missing entry for some microdescriptor. Continues on a patch
7120 - Improve the log message when a managed proxy fails to launch. Fixes
7121 bug 5099; bugfix on 0.2.3.6-alpha.
7122 - Don't do DNS lookups when parsing corrupted managed proxy protocol
7123 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
7124 - When formatting wildcarded address mappings for the controller,
7125 be sure to include "*." as appropriate. Partially fixes bug 6244;
7126 bugfix on 0.2.3.9-alpha.
7127 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
7128 Bugfix on 0.2.3.13-alpha.
7129 - Stop logging messages about running with circuit timeout learning
7130 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
7131 - Disable a spurious warning about reading on a marked and flushing
7132 connection. We shouldn't be doing that, but apparently we
7133 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
7134 - Fix a bug that stopped AllowDotExit from working on addresses
7135 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
7138 o Code simplification, refactoring, unit tests:
7139 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
7140 Libevent's notion of cached time when possible.
7141 - Remove duplicate code for invoking getrlimit() from control.c.
7142 - Add a unit test for the environment_variable_names_equal function.
7145 - Document the --defaults-torrc option, and the new (in 0.2.3)
7146 semantics for overriding, extending, and clearing lists of
7147 options. Closes bug 4748.
7150 Changes in version 0.2.3.17-beta - 2012-06-15
7151 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
7152 gets our TLS handshake back on track for being able to blend in with
7153 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
7154 with Vidalia, and otherwise continues to get us closer to a release
7158 - Enable gcc and ld hardening by default. Resolves ticket 5210.
7159 - Update TLS cipher list to match Firefox 8 and later. Resolves
7161 - Implement the client side of proposal 198: remove support for
7162 clients falsely claiming to support standard ciphersuites that
7163 they can actually provide. As of modern OpenSSL versions, it's not
7164 necessary to fake any standard ciphersuite, and doing so prevents
7165 us from using better ciphersuites in the future, since servers
7166 can't know whether an advertised ciphersuite is really supported or
7167 not. Some hosts -- notably, ones with very old versions of OpenSSL
7168 or where OpenSSL has been built with ECC disabled -- will stand
7169 out because of this change; TBB users should not be affected.
7172 - Change the default value for DynamicDHGroups (introduced in
7173 0.2.3.9-alpha) to 0. This feature can make Tor relays less
7174 identifiable by their use of the mod_ssl DH group, but at
7175 the cost of some usability (#4721) and bridge tracing (#6087)
7176 regressions. Resolves ticket 5598.
7177 - Send a CRLF at the end of each STATUS_* control protocol event. This
7178 bug tickled a bug in Vidalia which would make it freeze. Fixes
7179 bug 6094; bugfix on 0.2.3.16-alpha.
7182 - Disable writing on marked-for-close connections when they are
7183 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
7184 bug 5263; bugfix on 0.0.2pre13, where we first added a special
7185 case for flushing marked connections.
7186 - Detect SSL handshake even when the initial attempt to write the
7187 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
7188 - Change the AllowDotExit rules so they should actually work.
7189 We now enforce AllowDotExit only immediately after receiving an
7190 address via SOCKS or DNSPort: other sources are free to provide
7191 .exit addresses after the resolution occurs. Fixes bug 3940;
7192 bugfix on 0.2.2.1-alpha.
7193 - Fix a (harmless) integer overflow in cell statistics reported by
7194 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
7195 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
7196 right places and never depends on the consensus parameters or
7197 computes adaptive timeouts when it is disabled. Fixes bug 5049;
7198 bugfix on 0.2.2.14-alpha.
7199 - When building Tor on Windows with -DUNICODE (not default), ensure
7200 that error messages, filenames, and DNS server names are always
7201 NUL-terminated when we convert them to a single-byte encoding.
7202 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
7203 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
7204 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
7205 - Fix an edge case where TestingTorNetwork is set but the authorities
7206 and relays all have an uptime of zero, where the private Tor network
7207 could briefly lack support for hidden services. Fixes bug 3886;
7208 bugfix on 0.2.2.18-alpha.
7209 - Correct the manpage's descriptions for the default values of
7210 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
7212 - Fix the documentation for the --hush and --quiet command line
7213 options, which changed their behavior back in 0.2.3.3-alpha.
7214 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
7218 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
7219 more information to it, so that we can track it down in case it
7220 returns again. Mitigates bug 5235.
7221 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
7222 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
7223 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
7224 - Warn the user when HTTPProxy, but no other proxy type, is
7225 configured. This can cause surprising behavior: it doesn't send
7226 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
7227 directory traffic only. Resolves ticket 4663.
7228 - Issue a notice if a guard completes less than 40% of your circuits.
7229 Threshold is configurable by torrc option PathBiasNoticeRate and
7230 consensus parameter pb_noticepct. There is additional, off-by-
7231 default code to disable guards which fail too many circuits.
7232 Addresses ticket 5458.
7233 - Update to the June 6 2012 Maxmind GeoLite Country database.
7235 o Code simplifications and refactoring:
7236 - Remove validate_pluggable_transports_config(): its warning
7237 message is now handled by connection_or_connect().
7240 Changes in version 0.2.2.37 - 2012-06-06
7241 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
7242 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7246 - Work around a bug in OpenSSL that broke renegotiation with TLS
7247 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7248 the v2 Tor connection protocol when both sides were using OpenSSL
7249 1.0.1 would fail. Resolves ticket 6033.
7250 - When waiting for a client to renegotiate, don't allow it to add
7251 any bytes to the input buffer. This fixes a potential DoS issue.
7252 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7253 - Fix an edge case where if we fetch or publish a hidden service
7254 descriptor, we might build a 4-hop circuit and then use that circuit
7255 for exiting afterwards -- even if the new last hop doesn't obey our
7256 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7259 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7260 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7263 - Tell GCC and Clang to check for any errors in format strings passed
7264 to the tor_v*(print|scan)f functions.
7267 Changes in version 0.2.3.16-alpha - 2012-06-05
7268 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
7269 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7270 currently). It also fixes a variety of smaller bugs and other cleanups
7271 that get us closer to a release candidate.
7273 o Major bugfixes (general):
7274 - Work around a bug in OpenSSL that broke renegotiation with TLS
7275 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7276 the v2 Tor connection protocol when both sides were using OpenSSL
7277 1.0.1 would fail. Resolves ticket 6033.
7278 - When waiting for a client to renegotiate, don't allow it to add
7279 any bytes to the input buffer. This fixes a potential DoS issue.
7280 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7281 - Pass correct OR address to managed proxies (like obfsproxy),
7282 even when ORListenAddress is used. Fixes bug 4865; bugfix on
7284 - The advertised platform of a router now includes only its operating
7285 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
7286 service pack level (for Windows) or its CPU architecture (for Unix).
7287 We also no longer include the "git-XYZ" tag in the version. Resolves
7290 o Major bugfixes (clients):
7291 - If we are unable to find any exit that supports our predicted ports,
7292 stop calling them predicted, so that we don't loop and build
7293 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
7294 which introduced predicted ports.
7295 - Fix an edge case where if we fetch or publish a hidden service
7296 descriptor, we might build a 4-hop circuit and then use that circuit
7297 for exiting afterwards -- even if the new last hop doesn't obey our
7298 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7299 - Check at each new consensus whether our entry guards were picked
7300 long enough ago that we should rotate them. Previously, we only
7301 did this check at startup, which could lead to us holding a guard
7302 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
7303 - When fetching a bridge descriptor from a bridge authority,
7304 always do so anonymously, whether we have been able to open
7305 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
7306 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
7307 but we'll need to wait for bug 6010 before it's actually usable.
7309 o Major bugfixes (directory authorities):
7310 - When computing weight parameters, behave more robustly in the
7311 presence of a bad bwweightscale value. Previously, the authorities
7312 would crash if they agreed on a sufficiently broken weight_scale
7313 value: now, they use a reasonable default and carry on. Partial
7314 fix for 5786; bugfix on 0.2.2.17-alpha.
7315 - Check more thoroughly to prevent a rogue authority from
7316 double-voting on any consensus directory parameter. Previously,
7317 authorities would crash in this case if the total number of
7318 votes for any parameter exceeded the number of active voters,
7319 but would let it pass otherwise. Partial fix for bug 5786; bugfix
7323 - Rate-limit log messages when asked to connect anonymously to
7324 a private address. When these hit, they tended to hit fast and
7325 often. Also, don't bother trying to connect to addresses that we
7326 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
7327 reply makes us think we have been lied to, even when the address the
7328 client tried to connect to was "localhost." Resolves ticket 2822.
7329 - Allow packagers to insert an extra string in server descriptor
7330 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
7331 Resolves the rest of ticket 2988.
7332 - Raise the threshold of server descriptors needed (75%) and exit
7333 server descriptors needed (50%) before we will declare ourselves
7334 bootstrapped. This will make clients start building circuits a
7335 little later, but makes the initially constructed circuits less
7336 skewed and less in conflict with further directory fetches. Fixes
7338 - Close any connection that sends unrecognized junk before the
7339 handshake. Solves an issue noted in bug 4369.
7340 - Improve log messages about managed transports. Resolves ticket 5070.
7341 - Tag a bridge's descriptor as "never to be sent unencrypted".
7342 This shouldn't matter, since bridges don't open non-anonymous
7343 connections to the bridge authority and don't allow unencrypted
7344 directory connections from clients, but we might as well make
7345 sure. Closes bug 5139.
7346 - Expose our view of whether we have gone dormant to the controller,
7347 via a new "GETINFO dormant" value. Torbutton and other controllers
7348 can use this to avoid doing periodic requests through Tor while
7349 it's dormant (bug 4718). Fixes bug 5954.
7350 - Tell GCC and Clang to check for any errors in format strings passed
7351 to the tor_v*(print|scan)f functions.
7352 - Update to the May 1 2012 Maxmind GeoLite Country database.
7354 o Minor bugfixes (already included in 0.2.2.36):
7355 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7356 Fixes bug 5346; bugfix on 0.0.8pre3.
7357 - Correct parsing of certain date types in parse_http_time().
7358 Without this patch, If-Modified-Since would behave
7359 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7360 Esteban Manchado Velázques.
7361 - Make our number-parsing functions always treat too-large values
7362 as an error, even when those values exceed the width of the
7363 underlying type. Previously, if the caller provided these
7364 functions with minima or maxima set to the extreme values of the
7365 underlying integer type, these functions would return those
7366 values on overflow rather than treating overflow as an error.
7367 Fixes part of bug 5786; bugfix on 0.0.9.
7368 - If we hit the error case where routerlist_insert() replaces an
7369 existing (old) server descriptor, make sure to remove that
7370 server descriptor from the old_routers list. Fix related to bug
7371 1776. Bugfix on 0.2.2.18-alpha.
7372 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7373 circuits. Fixes issue 5259.
7375 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
7376 - Prevent a null-pointer dereference when receiving a data cell
7377 for a nonexistent stream when the circuit in question has an
7378 empty deliver window. We don't believe this is triggerable,
7379 since we don't currently allow deliver windows to become empty,
7380 but the logic is tricky enough that it's better to make the code
7381 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
7382 - Fix a memory leak when trying to launch a DNS request when the
7383 network is disabled or the nameservers are unconfigurable. Fixes
7384 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
7385 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
7386 - Don't hold a Windows file handle open for every file mapping;
7387 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
7389 - Avoid O(n^2) performance characteristics when parsing a large
7390 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
7391 - Format more doubles with %f, not %lf. Patch from grarpamp to make
7392 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
7394 - Make our replacement implementation of strtok_r() compatible with
7395 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
7396 bugfix on 0.2.2.1-alpha.
7397 - Fix a NULL-pointer dereference on a badly formed
7398 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
7399 bugfix on 0.2.2.9-alpha.
7400 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7401 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7402 - Defensively refactor rend_mid_rendezvous() so that protocol
7403 violations and length checks happen in the beginning. Fixes
7405 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
7406 that IPv6 stuff will compile on MSVC, and compilation issues
7407 will be easier to track down. Fixes bug 5861.
7409 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
7410 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
7411 resource exhaustion, so that clients can adjust their load to
7412 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
7413 started using END_STREAM_REASON_RESOURCELIMIT.
7414 - Don't check for whether the address we're using for outbound
7415 connections has changed until after the outbound connection has
7416 completed. On Windows, getsockname() doesn't succeed until the
7417 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
7418 - If the configuration tries to set MyFamily on a bridge, refuse to
7419 do so, and warn about the security implications. Fixes bug 4657;
7420 bugfix on 0.2.0.3-alpha.
7421 - If the client fails to set a reasonable set of ciphersuites
7422 during its v2 handshake renegotiation, allow the renegotiation to
7423 continue nevertheless (i.e. send all the required certificates).
7424 Fixes bug 4591; bugfix on 0.2.0.20-rc.
7425 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
7426 option is set to 0 (which Vidalia version 0.2.16 now does when
7427 a SAVECONF attempt fails), perform other actions that SIGHUP
7428 usually causes (like reopening the logs). Fixes bug 5095; bugfix
7430 - If we fail to write a microdescriptor to the disk cache, do not
7431 continue replacing the old microdescriptor file. Fixes bug 2954;
7432 bugfix on 0.2.2.6-alpha.
7433 - Exit nodes don't need to fetch certificates for authorities that
7434 they don't recognize; only directory authorities, bridges,
7435 and caches need to do that. Fixes part of bug 2297; bugfix on
7437 - Correctly handle checking the permissions on the parent
7438 directory of a control socket in the root directory. Bug found
7439 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
7441 - When told to add a bridge with the same digest as a preexisting
7442 bridge but a different addr:port, change the addr:port as
7443 requested. Previously we would not notice the change. Fixes half
7444 of bug 5603; fix on 0.2.2.26-beta.
7445 - End AUTHCHALLENGE error messages (in the control protocol) with
7446 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
7448 o Minor bugfixes (on 0.2.3.x):
7449 - Turn an assertion (that the number of handshakes received as a
7450 server is not < 1) into a warning. Fixes bug 4873; bugfix on
7452 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
7453 we had reversed them when the answer was cached.) Fixes bug
7454 5723; bugfix on 0.2.3.1-alpha.
7455 - Work correctly on Linux systems with accept4 support advertised in
7456 their headers, but without accept4 support in the kernel. Fix
7457 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
7458 - When told to add a bridge with the same addr:port as a preexisting
7459 bridge but a different transport, change the transport as
7460 requested. Previously we would not notice the change. Fixes half
7461 of bug 5603; fix on 0.2.3.2-alpha.
7462 - Avoid a "double-reply" warning when replying to a SOCKS request
7463 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
7464 bugfix on 0.2.3.4-alpha.
7465 - Fix a bug where a bridge authority crashes if it has seen no
7466 directory requests when it's time to write statistics to disk.
7467 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
7469 - Don't try to open non-control listeners when DisableNetwork is set.
7470 Previously, we'd open all listeners, then immediately close them.
7471 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
7472 - Don't abort the managed proxy protocol if the managed proxy
7473 sends us an unrecognized line; ignore it instead. Fixes bug
7474 5910; bugfix on 0.2.3.9-alpha.
7475 - Fix a compile warning in crypto.c when compiling with clang 3.1.
7476 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
7477 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
7478 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
7479 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
7480 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
7481 - Resolve numerous small warnings and build issues with MSVC. Resolves
7484 o Documentation fixes:
7485 - Improve the manual's documentation for the NT Service command-line
7486 options. Addresses ticket 3964.
7487 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
7488 - Document the changes to the ORPort and DirPort options, and the
7489 fact that {OR/Dir}ListenAddress is now unnecessary (and
7490 therefore deprecated). Resolves ticket 5597.
7493 - Remove the torrc.bridge file: we don't use it for anything, and
7494 it had become badly desynchronized from torrc.sample. Resolves
7498 Changes in version 0.2.2.36 - 2012-05-24
7499 Tor 0.2.2.36 updates the addresses for two of the eight directory
7500 authorities, fixes some potential anonymity and security issues,
7501 and fixes several crash bugs.
7503 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
7504 known flaws, and nobody should be using them. You should upgrade. If
7505 you're using a Linux or BSD and its packages are obsolete, stop using
7506 those packages and upgrade anyway.
7508 o Directory authority changes:
7509 - Change IP address for maatuska (v3 directory authority).
7510 - Change IP address for ides (v3 directory authority), and rename
7514 - When building or running with any version of OpenSSL earlier
7515 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7516 versions have a bug (CVE-2011-4576) in which their block cipher
7517 padding includes uninitialized data, potentially leaking sensitive
7518 information to any peer with whom they make a SSLv3 connection. Tor
7519 does not use SSL v3 by default, but a hostile client or server
7520 could force an SSLv3 connection in order to gain information that
7521 they shouldn't have been able to get. The best solution here is to
7522 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7523 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7524 to make sure that the bug can't happen.
7525 - Never use a bridge or a controller-supplied node as an exit, even
7526 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7527 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7528 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7529 - Only build circuits if we have a sufficient threshold of the total
7530 descriptors that are marked in the consensus with the "Exit"
7531 flag. This mitigates an attack proposed by wanoskarnet, in which
7532 all of a client's bridges collude to restrict the exit nodes that
7533 the client knows about. Fixes bug 5343.
7534 - Provide controllers with a safer way to implement the cookie
7535 authentication mechanism. With the old method, if another locally
7536 running program could convince a controller that it was the Tor
7537 process, then that program could trick the controller into telling
7538 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7539 authentication method uses a challenge-response approach to prevent
7540 this attack. Fixes bug 5185; implements proposal 193.
7543 - Avoid logging uninitialized data when unable to decode a hidden
7544 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7545 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7546 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7548 - Fix builds when the path to sed, openssl, or sha1sum contains
7549 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7551 - Correct our replacements for the timeradd() and timersub() functions
7552 on platforms that lack them (for example, Windows). The timersub()
7553 function is used when expiring circuits, while timeradd() is
7554 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7555 bugfix on 0.2.2.24-alpha.
7556 - Fix the SOCKET_OK test that we use to tell when socket
7557 creation fails so that it works on Win64. Fixes part of bug 4533;
7558 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7561 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7562 Fixes bug 5346; bugfix on 0.0.8pre3.
7563 - Make our number-parsing functions always treat too-large values
7564 as an error, even when those values exceed the width of the
7565 underlying type. Previously, if the caller provided these
7566 functions with minima or maxima set to the extreme values of the
7567 underlying integer type, these functions would return those
7568 values on overflow rather than treating overflow as an error.
7569 Fixes part of bug 5786; bugfix on 0.0.9.
7570 - Older Linux kernels erroneously respond to strange nmap behavior
7571 by having accept() return successfully with a zero-length
7572 socket. When this happens, just close the connection. Previously,
7573 we would try harder to learn the remote address: but there was
7574 no such remote address to learn, and our method for trying to
7575 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7576 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7577 - Correct parsing of certain date types in parse_http_time().
7578 Without this patch, If-Modified-Since would behave
7579 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7580 Esteban Manchado Velázques.
7581 - Change the BridgePassword feature (part of the "bridge community"
7582 design, which is not yet implemented) to use a time-independent
7583 comparison. The old behavior might have allowed an adversary
7584 to use timing to guess the BridgePassword value. Fixes bug 5543;
7585 bugfix on 0.2.0.14-alpha.
7586 - Detect and reject certain misformed escape sequences in
7587 configuration values. Previously, these values would cause us
7588 to crash if received in a torrc file or over an authenticated
7589 control port. Bug found by Esteban Manchado Velázquez, and
7590 independently by Robert Connolly from Matta Consulting who further
7591 noted that it allows a post-authentication heap overflow. Patch
7592 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7593 bugfix on 0.2.0.16-alpha.
7594 - Fix a compile warning when using the --enable-openbsd-malloc
7595 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7596 - During configure, detect when we're building with clang version
7597 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7598 CFLAGS. clang doesn't support them yet.
7599 - When sending an HTTP/1.1 proxy request, include a Host header.
7600 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7601 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
7602 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
7603 - If we hit the error case where routerlist_insert() replaces an
7604 existing (old) server descriptor, make sure to remove that
7605 server descriptor from the old_routers list. Fix related to bug
7606 1776. Bugfix on 0.2.2.18-alpha.
7608 o Minor bugfixes (documentation and log messages):
7609 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7610 Fixes bug 4856; bugfix on Tor 0.0.6.
7611 - Update "ClientOnly" man page entry to explain that there isn't
7612 really any point to messing with it. Resolves ticket 5005.
7613 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7614 directory authority option (introduced in Tor 0.2.2.34).
7615 - Downgrade the "We're missing a certificate" message from notice
7616 to info: people kept mistaking it for a real problem, whereas it
7617 is seldom the problem even when we are failing to bootstrap. Fixes
7618 bug 5067; bugfix on 0.2.0.10-alpha.
7619 - Correctly spell "connect" in a log message on failure to create a
7620 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
7621 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7622 circuits. Fixes issue 5259.
7625 - Directory authorities now reject versions of Tor older than
7626 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7627 inclusive. These versions accounted for only a small fraction of
7628 the Tor network, and have numerous known security issues. Resolves
7630 - Update to the May 1 2012 Maxmind GeoLite Country database.
7633 - When sending or relaying a RELAY_EARLY cell, we used to convert
7634 it to a RELAY cell if the connection was using the v1 link
7635 protocol. This was a workaround for older versions of Tor, which
7636 didn't handle RELAY_EARLY cells properly. Now that all supported
7637 versions can handle RELAY_EARLY cells, and now that we're enforcing
7638 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7639 remove this workaround. Addresses bug 4786.
7642 Changes in version 0.2.3.15-alpha - 2012-04-30
7643 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
7644 the development branch build on Windows again.
7646 o Minor bugfixes (on 0.2.2.x and earlier):
7647 - Make sure that there are no unhandled pending TLS errors before
7648 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
7649 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
7650 Bugfix on 0.1.0.5-rc; fixes bug 4528.
7651 - Fix an assert that directory authorities could trigger on sighup
7652 during some configuration state transitions. We now don't treat
7653 it as a fatal error when the new descriptor we just generated in
7654 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
7655 - After we pick a directory mirror, we would refuse to use it if
7656 it's in our ExcludeExitNodes list, resulting in mysterious failures
7657 to bootstrap for people who just wanted to avoid exiting from
7658 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
7659 - When building with --enable-static-tor on OpenBSD, do not
7660 erroneously attempt to link -lrt. Fixes bug 5103.
7662 o Minor bugfixes (on 0.2.3.x):
7663 - When Tor is built with kernel headers from a recent (last few
7664 years) Linux kernel, do not fail to run on older (pre-2.6.28
7665 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
7666 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
7668 - Fix compilation with miniupnpc version 1.6; patch from
7669 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
7670 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
7671 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
7672 - Fix compilation on platforms without unistd.h, or where environ
7673 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
7676 - Directory authorities are now a little more lenient at accepting
7677 older router descriptors, or newer router descriptors that don't
7678 make big changes. This should help ameliorate past and future
7679 issues where routers think they have uploaded valid descriptors,
7680 but the authorities don't think so. Fix for ticket 2479.
7681 - Make the code that clients use to detect an address change be
7682 IPv6-aware, so that it won't fill clients' logs with error
7683 messages when trying to get the IPv4 address of an IPv6
7684 connection. Implements ticket 5537.
7687 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
7688 authorities needed to use it for a while to keep the network working
7689 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
7690 that was six months ago. As of now, it should no longer be needed
7694 Changes in version 0.2.3.14-alpha - 2012-04-23
7695 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
7696 candidate. It also dramatically speeds up AES: fast relays should
7697 consider switching to the newer OpenSSL library.
7699 o Directory authority changes:
7700 - Change IP address for ides (v3 directory authority), and rename
7704 - Avoid logging uninitialized data when unable to decode a hidden
7705 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7706 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7707 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7709 - If authorities are unable to get a v2 consensus document from other
7710 directory authorities, they no longer fall back to fetching
7711 them from regular directory caches. Fixes bug 5635; bugfix on
7712 0.2.2.26-beta, where routers stopped downloading v2 consensus
7714 - When we start a Tor client with a normal consensus already cached,
7715 be willing to download a microdescriptor consensus. Fixes bug 4011;
7716 fix on 0.2.3.1-alpha.
7718 o Major features (performance):
7719 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
7720 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
7721 vectorized AES implementations as appropriate. These can be much,
7722 much faster than other AES implementations.
7724 o Minor bugfixes (0.2.2.x and earlier):
7725 - Don't launch more than 10 service-side introduction-point circuits
7726 for a hidden service in five minutes. Previously, we would consider
7727 launching more introduction-point circuits if at least one second
7728 had passed without any introduction-point circuits failing. Fixes
7729 bug 4607; bugfix on 0.0.7pre1.
7730 - Change the BridgePassword feature (part of the "bridge community"
7731 design, which is not yet implemented) to use a time-independent
7732 comparison. The old behavior might have allowed an adversary
7733 to use timing to guess the BridgePassword value. Fixes bug 5543;
7734 bugfix on 0.2.0.14-alpha.
7735 - Enforce correct return behavior of tor_vsscanf() when the '%%'
7736 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
7737 - When sending an HTTP/1.1 proxy request, include a Host header.
7738 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7739 - Don't log that we have "decided to publish new relay descriptor"
7740 unless we are actually publishing a descriptor. Fixes bug 3942;
7741 bugfix on 0.2.2.28-beta.
7743 o Minor bugfixes (0.2.3.x):
7744 - Fix a bug where a bridge authority crashes (on a failed assert)
7745 if it has seen no directory requests when it's time to write
7746 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
7747 - Fix bug stomping on ORPort option NoListen and ignoring option
7748 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
7749 - In the testsuite, provide a large enough buffer in the tor_sscanf
7750 unit test. Otherwise we'd overrun that buffer and crash during
7751 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
7753 - Make sure we create the keys directory if it doesn't exist and we're
7754 about to store the dynamic Diffie-Hellman parameters. Fixes bug
7755 5572; bugfix on 0.2.3.13-alpha.
7756 - Fix a small memory leak when trying to decode incorrect base16
7757 authenticator during SAFECOOKIE authentication. Found by
7758 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
7761 - Add more information to a log statement that might help track down
7762 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
7763 non-IP address" messages (or any Bug messages, for that matter!),
7764 please let us know about it.
7765 - Relays now understand an IPv6 address when they get one from a
7766 directory server. Resolves ticket 4875.
7767 - Resolve IPv6 addresses in bridge and entry statistics to country
7768 code "??" which means we at least count them. Resolves ticket 5053;
7769 improves on 0.2.3.9-alpha.
7770 - Update to the April 3 2012 Maxmind GeoLite Country database.
7771 - Begin a doc/state-contents.txt file to explain the contents of
7772 the Tor state file. Fixes bug 2987.
7774 o Default torrc changes:
7775 - Stop listing "socksport 9050" in torrc.sample. We open a socks
7776 port on 9050 by default anyway, so this should not change anything
7778 - Stop mentioning the deprecated *ListenAddress options in
7779 torrc.sample. Fixes bug 5438.
7780 - Document unit of bandwidth related options in sample torrc.
7784 - The "torify" script no longer supports the "tsocks" socksifier
7785 tool, since tsocks doesn't support DNS and UDP right for Tor.
7786 Everyone should be using torsocks instead. Fixes bugs 3530 and
7787 5180. Based on a patch by "ugh".
7790 - Change the symmetric cipher interface so that creating and
7791 initializing a stream cipher are no longer separate functions.
7792 - Remove all internal support for unpadded RSA. We never used it, and
7793 it would be a bad idea to start.
7796 Changes in version 0.2.3.13-alpha - 2012-03-26
7797 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
7798 in managed pluggable transports, as well as providing other cleanups
7799 that get us closer to a release candidate.
7801 o Directory authority changes:
7802 - Change IP address for maatuska (v3 directory authority).
7805 - Provide controllers with a safer way to implement the cookie
7806 authentication mechanism. With the old method, if another locally
7807 running program could convince a controller that it was the Tor
7808 process, then that program could trick the controller into telling
7809 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7810 authentication method uses a challenge-response approach to prevent
7811 this attack. Fixes bug 5185, implements proposal 193.
7812 - Never use a bridge or a controller-supplied node as an exit, even
7813 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7814 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7815 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7816 - Only build circuits if we have a sufficient threshold of the total
7817 descriptors that are marked in the consensus with the "Exit"
7818 flag. This mitigates an attack proposed by wanoskarnet, in which
7819 all of a client's bridges collude to restrict the exit nodes that
7820 the client knows about. Fixes bug 5343.
7822 o Major bugfixes (on Tor 0.2.3.x):
7823 - Avoid an assert when managed proxies like obfsproxy are configured,
7824 and we receive HUP signals or setconf attempts too rapidly. This
7825 situation happens most commonly when Vidalia tries to attach to
7826 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
7827 bugfix on 0.2.3.6-alpha.
7828 - Fix a relay-side pluggable transports bug where managed proxies were
7829 unreachable from the Internet, because Tor asked them to bind on
7830 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
7831 - Stop discarding command-line arguments when TestingTorNetwork
7832 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
7833 0.2.3.9-alpha, where task 4552 added support for two layers of
7835 - Resume allowing the unit tests to run in gdb. This was accidentally
7836 made impossible when the DisableDebuggerAttachment option was
7837 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
7838 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
7839 0.2.3.11-alpha. Reported by Anthony G. Basile.
7841 o Minor bugfixes (on 0.2.2.x and earlier):
7842 - Ensure we don't cannibalize circuits that are longer than three hops
7843 already, so we don't end up making circuits with 5 or more
7844 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
7845 0.1.0.1-rc which introduced cannibalization.
7846 - Detect and reject certain misformed escape sequences in
7847 configuration values. Previously, these values would cause us
7848 to crash if received in a torrc file or over an authenticated
7849 control port. Bug found by Esteban Manchado Velázquez, and
7850 independently by Robert Connolly from Matta Consulting who further
7851 noted that it allows a post-authentication heap overflow. Patch
7852 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7853 bugfix on 0.2.0.16-alpha.
7854 - Fix a compile warning when using the --enable-openbsd-malloc
7855 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7856 - Directory caches no longer refuse to clean out descriptors because
7857 of missing v2 networkstatus documents, unless they're configured
7858 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
7859 0.2.2.26-beta. Patch by Daniel Bryg.
7860 - Update to the latest version of the tinytest unit testing framework.
7861 This includes a couple of bugfixes that can be relevant for
7862 running forked unit tests on Windows, and removes all reserved
7865 o Minor bugfixes (on 0.2.3.x):
7866 - On a failed pipe() call, don't leak file descriptors. Fixes bug
7867 4296; bugfix on 0.2.3.1-alpha.
7868 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
7869 until after we have received a CERTS cell. Fixes bug 4361; bugfix
7870 on 0.2.3.6-alpha. Patch by "frosty".
7871 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
7872 option, so that the IP stack doesn't decide to use it for IPv4
7873 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
7874 - Ensure that variables set in Tor's environment cannot override
7875 environment variables that Tor passes to a managed
7876 pluggable-transport proxy. Previously, Tor would pass every
7877 variable in its environment to managed proxies along with the new
7878 ones, in such a way that on many operating systems, the inherited
7879 environment variables would override those which Tor tried to
7880 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
7881 bugfix on 0.2.3.9-alpha for Windows.
7884 - A wide variety of new unit tests by Esteban Manchado Velázquez.
7885 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
7886 - Update to the March 6 2012 Maxmind GeoLite Country database.
7889 Changes in version 0.2.3.12-alpha - 2012-02-13
7890 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
7891 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
7892 when Tor is configured to use a pluggable transport like obfsproxy.
7895 - Fix builds when the path to sed, openssl, or sha1sum contains
7896 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7898 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
7899 connections. This change should allow busy exit relays to stop
7900 running out of available sockets as quickly. Fixes bug 4950;
7901 bugfix on 0.2.2.26-beta.
7902 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
7903 would ask the bridge for microdescriptors, which are only supported
7904 in 0.2.3.x, and then fail to bootstrap when it didn't get the
7905 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
7906 - Properly set up obfsproxy's environment when in managed mode. The
7907 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
7908 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
7909 5076 and 5082; bugfix on 0.2.3.6-alpha.
7912 - Use the dead_strip option when building Tor on OS X. This reduces
7913 binary size by almost 19% when linking openssl and libevent
7914 statically, which we do for Tor Browser Bundle.
7915 - Fix broken URLs in the sample torrc file, and tell readers about
7916 the OutboundBindAddress, ExitPolicyRejectPrivate, and
7917 PublishServerDescriptor options. Addresses bug 4652.
7918 - Update to the February 7 2012 Maxmind GeoLite Country database.
7921 - Downgrade the "We're missing a certificate" message from notice
7922 to info: people kept mistaking it for a real problem, whereas it
7923 is seldom the problem even when we are failing to bootstrap. Fixes
7924 bug 5067; bugfix on 0.2.0.10-alpha.
7925 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
7926 managed pluggable transport server proxy's environment.
7927 Previously, we would put it there, even though Tor doesn't
7928 implement an 'extended server port' yet, and even though Tor
7929 almost certainly isn't listening at that address. For now, we set
7930 it to an empty string to avoid crashing older obfsproxies. Bugfix
7932 - Log the heartbeat message every HeartbeatPeriod seconds, not every
7933 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
7934 0.2.3.1-alpha. Bug reported by Scott Bennett.
7935 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
7936 bugfix on 0.2.3.11-alpha.
7937 - Update "ClientOnly" man page entry to explain that there isn't
7938 really any point to messing with it. Resolves ticket 5005.
7939 - Use the correct CVE number for CVE-2011-4576 in our comments and
7940 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
7943 o Code simplifications and refactoring:
7944 - Use the _WIN32 macro throughout our code to detect Windows.
7945 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
7949 Changes in version 0.2.3.11-alpha - 2012-01-22
7950 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
7951 the last step of the plan to limit maximum circuit length, includes
7952 a wide variety of hidden service performance and correctness fixes,
7953 works around an OpenSSL security flaw if your distro is too stubborn
7954 to upgrade, and fixes a bunch of smaller issues.
7957 - Now that Tor 0.2.0.x is completely deprecated, enable the final
7958 part of "Proposal 110: Avoiding infinite length circuits" by
7959 refusing all circuit-extend requests that do not use a relay_early
7960 cell. This change helps Tor resist a class of denial-of-service
7961 attacks by limiting the maximum circuit length.
7962 - Adjust the number of introduction points that a hidden service
7963 will try to maintain based on how long its introduction points
7964 remain in use and how many introductions they handle. Fixes
7966 - Try to use system facilities for enumerating local interface
7967 addresses, before falling back to our old approach (which was
7968 binding a UDP socket, and calling getsockname() on it). That
7969 approach was scaring OS X users whose draconian firewall
7970 software warned about binding to UDP sockets, regardless of
7971 whether packets were sent. Now we try to use getifaddrs(),
7972 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
7973 system supports. Resolves ticket 1827.
7975 o Major security workaround:
7976 - When building or running with any version of OpenSSL earlier
7977 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7978 versions have a bug (CVE-2011-4576) in which their block cipher
7979 padding includes uninitialized data, potentially leaking sensitive
7980 information to any peer with whom they make a SSLv3 connection. Tor
7981 does not use SSL v3 by default, but a hostile client or server
7982 could force an SSLv3 connection in order to gain information that
7983 they shouldn't have been able to get. The best solution here is to
7984 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7985 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7986 to make sure that the bug can't happen.
7989 - Fix the SOCKET_OK test that we use to tell when socket
7990 creation fails so that it works on Win64. Fixes part of bug 4533;
7991 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7992 - Correct our replacements for the timeradd() and timersub() functions
7993 on platforms that lack them (for example, Windows). The timersub()
7994 function is used when expiring circuits, while timeradd() is
7995 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7996 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
7997 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
7998 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
7999 bug at runtime, not compile time, because some distributions hack
8000 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
8001 on 0.2.3.9-alpha. Found by Pascal.
8003 o Minor features (controller):
8004 - Use absolute path names when reporting the torrc filename in the
8005 control protocol, so a controller can more easily find the torrc
8006 file. Resolves bug 1101.
8007 - Extend the control protocol to report flags that control a circuit's
8008 path selection in CIRC events and in replies to 'GETINFO
8009 circuit-status'. Implements part of ticket 2411.
8010 - Extend the control protocol to report the hidden service address
8011 and current state of a hidden-service-related circuit in CIRC
8012 events and in replies to 'GETINFO circuit-status'. Implements part
8014 - When reporting the path to the cookie file to the controller,
8015 give an absolute path. Resolves ticket 4881.
8016 - Allow controllers to request an event notification whenever a
8017 circuit is cannibalized or its purpose is changed. Implements
8018 part of ticket 3457.
8019 - Include the creation time of a circuit in CIRC and CIRC2
8020 control-port events and the list produced by the 'GETINFO
8021 circuit-status' control-port command.
8023 o Minor features (directory authorities):
8024 - Directory authorities now reject versions of Tor older than
8025 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
8026 inclusive. These versions accounted for only a small fraction of
8027 the Tor network, and have numerous known security issues. Resolves
8029 - Authority operators can now vote for all relays in a given
8030 set of countries to be BadDir/BadExit/Invalid/Rejected.
8031 - Provide two consensus parameters (FastFlagMinThreshold and
8032 FastFlagMaxThreshold) to control the range of allowable bandwidths
8033 for the Fast directory flag. These allow authorities to run
8034 experiments on appropriate requirements for being a "Fast" node.
8035 The AuthDirFastGuarantee config value still applies. Implements
8037 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
8038 directory authority option (introduced in Tor 0.2.2.34).
8040 o Minor features (other):
8041 - Don't disable the DirPort when we cannot exceed our AccountingMax
8042 limit during this interval because the effective bandwidthrate is
8043 low enough. This is useful in a situation where AccountMax is only
8044 used as an additional safeguard or to provide statistics.
8045 - Prepend an informative header to generated dynamic_dh_params files.
8046 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
8047 EntryNodes will have no effect. Resolves issue 2571.
8048 - Log more useful messages when we fail to disable debugger
8050 - Log which authority we're missing votes from when we go to fetch
8051 them from the other auths.
8052 - Log (at debug level) whenever a circuit's purpose is changed.
8053 - Add missing documentation for the MaxClientCircuitsPending,
8054 UseMicrodescriptors, UserspaceIOCPBuffers, and
8055 _UseFilteringSSLBufferevents options, all introduced during
8057 - Update to the January 3 2012 Maxmind GeoLite Country database.
8059 o Minor bugfixes (hidden services):
8060 - Don't close hidden service client circuits which have almost
8061 finished connecting to their destination when they reach
8062 the normal circuit-build timeout. Previously, we would close
8063 introduction circuits which are waiting for an acknowledgement
8064 from the introduction point, and rendezvous circuits which have
8065 been specified in an INTRODUCE1 cell sent to a hidden service,
8066 after the normal CBT. Now, we mark them as 'timed out', and launch
8067 another rendezvous attempt in parallel. This behavior change can
8068 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
8069 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
8070 - Don't close hidden-service-side rendezvous circuits when they
8071 reach the normal circuit-build timeout. This behavior change can
8072 be disabled using the new
8073 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
8074 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
8075 - Make sure we never mark the wrong rendezvous circuit as having
8076 had its introduction cell acknowleged by the introduction-point
8077 relay. Previously, when we received an INTRODUCE_ACK cell on a
8078 client-side hidden-service introduction circuit, we might have
8079 marked a rendezvous circuit other than the one we specified in
8080 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
8081 a warning message and interfered with the hidden service
8082 connection-establishment process. Fixes bug 4759; bugfix on
8083 0.2.3.3-alpha, when we added the stream-isolation feature which
8084 might cause Tor to open multiple rendezvous circuits for the same
8086 - Don't trigger an assertion failure when we mark a new client-side
8087 hidden-service introduction circuit for close during the process
8088 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
8091 o Minor bugfixes (log messages):
8092 - Correctly spell "connect" in a log message on failure to create a
8093 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
8095 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
8096 Fixes bug 4856; bugfix on Tor 0.0.6.
8097 - Fix the log message describing how we work around discovering
8098 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
8099 4837; bugfix on 0.2.2.9-alpha.
8100 - When logging about a disallowed .exit name, do not also call it
8101 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
8103 o Minor bugfixes (build fixes):
8104 - During configure, detect when we're building with clang version
8105 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
8106 CFLAGS. clang doesn't support them yet.
8107 - During configure, search for library containing cos function as
8108 libm lives in libcore on some platforms (BeOS/Haiku). Linking
8109 against libm was hard-coded before. Fixes the first part of bug
8110 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
8112 - Detect attempts to build Tor on (as yet hypothetical) versions
8113 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
8114 fix for bug 4533. Bugfix on 0.2.2.28-beta.
8115 - Preprocessor directives should not be put inside the arguments
8116 of a macro. This would break compilation with GCC releases prior
8117 to version 3.3. We would never recommend such an old GCC version,
8118 but it is apparently required for binary compatibility on some
8119 platforms (namely, certain builds of Haiku). Fixes the other part
8120 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
8123 o Minor bugfixes (other):
8124 - Older Linux kernels erroneously respond to strange nmap behavior
8125 by having accept() return successfully with a zero-length
8126 socket. When this happens, just close the connection. Previously,
8127 we would try harder to learn the remote address: but there was
8128 no such remote address to learn, and our method for trying to
8129 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
8130 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
8131 - Fix null-pointer access that could occur if TLS allocation failed.
8132 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
8133 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
8134 accidentally been reverted.
8135 - Fix our implementation of crypto_random_hostname() so it can't
8136 overflow on ridiculously large inputs. (No Tor version has ever
8137 provided this kind of bad inputs, but let's be correct in depth.)
8138 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
8139 - Find more places in the code that should have been testing for
8140 invalid sockets using the SOCKET_OK macro. Required for a fix
8141 for bug 4533. Bugfix on 0.2.2.28-beta.
8142 - Fix an assertion failure when, while running with bufferevents, a
8143 connection finishes connecting after it is marked for close, but
8144 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
8145 - test_util_spawn_background_ok() hardcoded the expected value
8146 for ENOENT to 2. This isn't portable as error numbers are
8147 platform specific, and particularly the hurd has ENOENT at
8148 0x40000002. Construct expected string at runtime, using the correct
8149 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
8150 - Reject attempts to disable DisableDebuggerAttachment while Tor is
8151 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
8152 - Use an appropriate-width type for sockets in tor-fw-helper on
8153 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
8156 - When sending or relaying a RELAY_EARLY cell, we used to convert
8157 it to a RELAY cell if the connection was using the v1 link
8158 protocol. This was a workaround for older versions of Tor, which
8159 didn't handle RELAY_EARLY cells properly. Now that all supported
8160 versions can handle RELAY_EARLY cells, and now that we're enforcing
8161 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
8162 remove this workaround. Addresses bug 4786.
8164 o Code simplifications and refactoring:
8165 - Use OpenSSL's built-in SSL_state_string_long() instead of our
8166 own homebrewed ssl_state_to_string() replacement. Patch from
8167 Emile Snyder. Fixes bug 4653.
8168 - Use macros to indicate OpenSSL versions, so we don't need to worry
8169 about accidental hexadecimal bit shifts.
8170 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
8172 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
8173 - Use the smartlist_add_asprintf() alias more consistently.
8174 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
8175 invalid value, rather than just -1.
8176 - Rename a handful of old identifiers, mostly related to crypto
8177 structures and crypto functions. By convention, our "create an
8178 object" functions are called "type_new()", our "free an object"
8179 functions are called "type_free()", and our types indicate that
8180 they are types only with a final "_t". But a handful of older
8181 types and functions broke these rules, with function names like
8182 "type_create" or "subsystem_op_type", or with type names like
8186 Changes in version 0.2.3.10-alpha - 2011-12-16
8187 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
8188 Tor's buffers code. Absolutely everybody should upgrade.
8190 The bug relied on an incorrect calculation when making data continuous
8191 in one of our IO buffers, if the first chunk of the buffer was
8192 misaligned by just the wrong amount. The miscalculation would allow an
8193 attacker to overflow a piece of heap-allocated memory. To mount this
8194 attack, the attacker would need to either open a SOCKS connection to
8195 Tor's SocksPort (usually restricted to localhost), or target a Tor
8196 instance configured to make its connections through a SOCKS proxy
8197 (which Tor does not do by default).
8199 Good security practice requires that all heap-overflow bugs should be
8200 presumed to be exploitable until proven otherwise, so we are treating
8201 this as a potential code execution attack. Please upgrade immediately!
8202 This bug does not affect bufferevents-based builds of Tor. Special
8203 thanks to "Vektor" for reporting this issue to us!
8205 This release also contains a few minor bugfixes for issues discovered
8209 - Fix a heap overflow bug that could occur when trying to pull
8210 data into the first chunk of a buffer, when that chunk had
8211 already had some data drained from it. Fixes CVE-2011-2778;
8212 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8215 - If we can't attach streams to a rendezvous circuit when we
8216 finish connecting to a hidden service, clear the rendezvous
8217 circuit's stream-isolation state and try to attach streams
8218 again. Previously, we cleared rendezvous circuits' isolation
8219 state either too early (if they were freshly built) or not at all
8220 (if they had been built earlier and were cannibalized). Bugfix on
8221 0.2.3.3-alpha; fixes bug 4655.
8222 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
8223 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
8224 - Fix an assertion failure when a relay with accounting enabled
8225 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
8228 - Update to the December 6 2011 Maxmind GeoLite Country database.
8231 Changes in version 0.2.2.35 - 2011-12-16
8232 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
8233 buffers code. Absolutely everybody should upgrade.
8235 The bug relied on an incorrect calculation when making data continuous
8236 in one of our IO buffers, if the first chunk of the buffer was
8237 misaligned by just the wrong amount. The miscalculation would allow an
8238 attacker to overflow a piece of heap-allocated memory. To mount this
8239 attack, the attacker would need to either open a SOCKS connection to
8240 Tor's SocksPort (usually restricted to localhost), or target a Tor
8241 instance configured to make its connections through a SOCKS proxy
8242 (which Tor does not do by default).
8244 Good security practice requires that all heap-overflow bugs should be
8245 presumed to be exploitable until proven otherwise, so we are treating
8246 this as a potential code execution attack. Please upgrade immediately!
8247 This bug does not affect bufferevents-based builds of Tor. Special
8248 thanks to "Vektor" for reporting this issue to us!
8250 Tor 0.2.2.35 also fixes several bugs in previous versions, including
8251 crash bugs for unusual configurations, and a long-term bug that
8252 would prevent Tor from starting on Windows machines with draconian
8255 With this release, we remind everyone that 0.2.0.x has reached its
8256 formal end-of-life. Those Tor versions have many known flaws, and
8257 nobody should be using them. You should upgrade -- ideally to the
8258 0.2.2.x series. If you're using a Linux or BSD and its packages are
8259 obsolete, stop using those packages and upgrade anyway.
8261 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
8262 longer receive support after some time in early 2012.
8265 - Fix a heap overflow bug that could occur when trying to pull
8266 data into the first chunk of a buffer, when that chunk had
8267 already had some data drained from it. Fixes CVE-2011-2778;
8268 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8269 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8270 that it doesn't attempt to allocate a socketpair. This could cause
8271 some problems on Windows systems with overzealous firewalls. Fix for
8272 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8274 - If we mark an OR connection for close based on a cell we process,
8275 don't process any further cells on it. We already avoid further
8276 reads on marked-for-close connections, but now we also discard the
8277 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
8278 which was the first version where we might mark a connection for
8279 close based on processing a cell on it.
8280 - Correctly sanity-check that we don't underflow on a memory
8281 allocation (and then assert) for hidden service introduction
8282 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8283 bugfix on 0.2.1.5-alpha.
8284 - Fix a memory leak when we check whether a hidden service
8285 descriptor has any usable introduction points left. Fixes bug
8286 4424. Bugfix on 0.2.2.25-alpha.
8287 - Don't crash when we're running as a relay and don't have a GeoIP
8288 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
8289 we've had in the 0.2.3.x branch already.
8290 - When running as a client, do not print a misleading (and plain
8291 wrong) log message that we're collecting "directory request"
8292 statistics: clients don't collect statistics. Also don't create a
8293 useless (because empty) stats file in the stats/ directory. Fixes
8294 bug 4353; bugfix on 0.2.2.34.
8297 - Detect failure to initialize Libevent. This fix provides better
8298 detection for future instances of bug 4457.
8299 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8300 function. This was eating up hideously large amounts of time on some
8301 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8302 - Resolve an integer overflow bug in smartlist_ensure_capacity().
8303 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
8305 - Don't warn about unused log_mutex in log.c when building with
8306 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8307 0.1.0.6-rc which introduced --disable-threads.
8308 - When configuring, starting, or stopping an NT service, stop
8309 immediately after the service configuration attempt has succeeded
8310 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8311 - When sending a NETINFO cell, include the original address
8312 received for the other side, not its canonical address. Found
8313 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8314 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
8315 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
8316 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8317 occurred when a client tried to fetch a descriptor for a bridge
8318 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
8319 - Backport fixes for a pair of compilation warnings on Windows.
8320 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
8321 - If we had ever tried to call tor_addr_to_str on an address of
8322 unknown type, we would have done a strdup on an uninitialized
8323 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
8324 Reported by "troll_un".
8325 - Correctly detect and handle transient lookup failures from
8326 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
8327 Reported by "troll_un".
8328 - Fix null-pointer access that could occur if TLS allocation failed.
8329 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
8330 - Use tor_socket_t type for listener argument to accept(). Fixes bug
8331 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
8334 - Add two new config options for directory authorities:
8335 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
8336 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
8337 that is always sufficient to satisfy the bandwidth requirement for
8338 the Guard flag. Now it will be easier for researchers to simulate
8339 Tor networks with different values. Resolves ticket 4484.
8340 - When Tor ignores a hidden service specified in its configuration,
8341 include the hidden service's directory in the warning message.
8342 Previously, we would only tell the user that some hidden service
8343 was ignored. Bugfix on 0.0.6; fixes bug 4426.
8344 - Update to the December 6 2011 Maxmind GeoLite Country database.
8346 o Packaging changes:
8347 - Make it easier to automate expert package builds on Windows,
8348 by removing an absolute path from makensis.exe command.
8351 Changes in version 0.2.1.32 - 2011-12-16
8352 Tor 0.2.1.32 backports important security and privacy fixes for
8353 oldstable. This release is intended only for package maintainers and
8354 others who cannot use the 0.2.2 stable series. All others should be
8355 using Tor 0.2.2.x or newer.
8357 The Tor 0.2.1.x series will reach formal end-of-life some time in
8358 early 2012; we will stop releasing patches for it then.
8360 o Major bugfixes (also included in 0.2.2.x):
8361 - Correctly sanity-check that we don't underflow on a memory
8362 allocation (and then assert) for hidden service introduction
8363 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8364 bugfix on 0.2.1.5-alpha.
8365 - Fix a heap overflow bug that could occur when trying to pull
8366 data into the first chunk of a buffer, when that chunk had
8367 already had some data drained from it. Fixes CVE-2011-2778;
8368 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8371 - Update to the December 6 2011 Maxmind GeoLite Country database.
8374 Changes in version 0.2.3.9-alpha - 2011-12-08
8375 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
8376 a "DisableNetwork" security feature that bundles can use to avoid
8377 touching the network until bridges are configured, moves forward on
8378 the pluggable transport design, fixes a flaw in the hidden service
8379 design that unnecessarily prevented clients with wrong clocks from
8380 reaching hidden services, and fixes a wide variety of other issues.
8383 - Clients can now connect to private bridges over IPv6. Bridges
8384 still need at least one IPv4 address in order to connect to
8385 other relays. Note that we don't yet handle the case where the
8386 user has two bridge lines for the same bridge (one IPv4, one
8387 IPv6). Implements parts of proposal 186.
8388 - New "DisableNetwork" config option to prevent Tor from launching any
8389 connections or accepting any connections except on a control port.
8390 Bundles and controllers can set this option before letting Tor talk
8391 to the rest of the network, for example to prevent any connections
8392 to a non-bridge address. Packages like Orbot can also use this
8393 option to instruct Tor to save power when the network is off.
8394 - Clients and bridges can now be configured to use a separate
8395 "transport" proxy. This approach makes the censorship arms race
8396 easier by allowing bridges to use protocol obfuscation plugins. It
8397 implements the "managed proxy" part of proposal 180 (ticket 3472).
8398 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
8399 implementation. It makes AES_CTR about 7% faster than our old one
8400 (which was about 10% faster than the one OpenSSL used to provide).
8401 Resolves ticket 4526.
8402 - Add a "tor2web mode" for clients that want to connect to hidden
8403 services non-anonymously (and possibly more quickly). As a safety
8404 measure to try to keep users from turning this on without knowing
8405 what they are doing, tor2web mode must be explicitly enabled at
8406 compile time, and a copy of Tor compiled to run in tor2web mode
8407 cannot be used as a normal Tor client. Implements feature 2553.
8408 - Add experimental support for running on Windows with IOCP and no
8409 kernel-space socket buffers. This feature is controlled by a new
8410 "UserspaceIOCPBuffers" config option (off by default), which has
8411 no effect unless Tor has been built with support for bufferevents,
8412 is running on Windows, and has enabled IOCP. This may, in the long
8413 run, help solve or mitigate bug 98.
8414 - Use a more secure consensus parameter voting algorithm. Now at
8415 least three directory authorities or a majority of them must
8416 vote on a given parameter before it will be included in the
8417 consensus. Implements proposal 178.
8420 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
8421 They used to check that the timestamp was within 30 minutes
8422 of their system clock, so they could cap the size of their
8423 replay-detection cache, but that approach unnecessarily refused
8424 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
8425 the v3 intro-point protocol (the first one which sent a timestamp
8426 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
8427 - Only use the EVP interface when AES acceleration is enabled,
8428 to avoid a 5-7% performance regression. Resolves issue 4525;
8429 bugfix on 0.2.3.8-alpha.
8431 o Privacy/anonymity features (bridge detection):
8432 - Make bridge SSL certificates a bit more stealthy by using random
8433 serial numbers, in the same fashion as OpenSSL when generating
8434 self-signed certificates. Implements ticket 4584.
8435 - Introduce a new config option "DynamicDHGroups", enabled by
8436 default, which provides each bridge with a unique prime DH modulus
8437 to be used during SSL handshakes. This option attempts to help
8438 against censors who might use the Apache DH modulus as a static
8439 identifier for bridges. Addresses ticket 4548.
8441 o Minor features (new/different config options):
8442 - New configuration option "DisableDebuggerAttachment" (on by default)
8443 to prevent basic debugging attachment attempts by other processes.
8444 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
8445 - Allow MapAddress directives to specify matches against super-domains,
8446 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
8447 Implements issue 933.
8448 - Slightly change behavior of "list" options (that is, config
8449 options that can appear more than once) when they appear both in
8450 torrc and on the command line. Previously, the command-line options
8451 would be appended to the ones from torrc. Now, the command-line
8452 options override the torrc options entirely. This new behavior
8453 allows the user to override list options (like exit policies and
8454 ports to listen on) from the command line, rather than simply
8455 appending to the list.
8456 - You can get the old (appending) command-line behavior for "list"
8457 options by prefixing the option name with a "+".
8458 - You can remove all the values for a "list" option from the command
8459 line without adding any new ones by prefixing the option name
8461 - Add experimental support for a "defaults" torrc file to be parsed
8462 before the regular torrc. Torrc options override the defaults file's
8463 options in the same way that the command line overrides the torrc.
8464 The SAVECONF controller command saves only those options which
8465 differ between the current configuration and the defaults file. HUP
8466 reloads both files. (Note: This is an experimental feature; its
8467 behavior will probably be refined in future 0.2.3.x-alpha versions
8468 to better meet packagers' needs.) Implements task 4552.
8471 - Try to make the introductory warning message that Tor prints on
8472 startup more useful for actually finding help and information.
8473 Resolves ticket 2474.
8474 - Running "make version" now displays the version of Tor that
8475 we're about to build. Idea from katmagic; resolves issue 4400.
8476 - Expire old or over-used hidden service introduction points.
8477 Required by fix for bug 3460.
8478 - Move the replay-detection cache for the RSA-encrypted parts of
8479 INTRODUCE2 cells to the introduction point data structures.
8480 Previously, we would use one replay-detection cache per hidden
8481 service. Required by fix for bug 3460.
8482 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
8483 public key replay-detection cache from 60 minutes to 5 minutes. This
8484 replay-detection cache is now used only to detect multiple
8485 INTRODUCE2 cells specifying the same rendezvous point, so we can
8486 avoid launching multiple simultaneous attempts to connect to it.
8488 o Minor bugfixes (on Tor 0.2.2.x and earlier):
8489 - Resolve an integer overflow bug in smartlist_ensure_capacity().
8490 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
8492 - Fix a minor formatting issue in one of tor-gencert's error messages.
8494 - Prevent a false positive from the check-spaces script, by disabling
8495 the "whitespace between function name and (" check for functions
8497 - Fix a log message suggesting that people contact a non-existent
8498 email address. Fixes bug 3448.
8499 - Fix null-pointer access that could occur if TLS allocation failed.
8500 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
8501 - Report a real bootstrap problem to the controller on router
8502 identity mismatch. Previously we just said "foo", which probably
8503 made a lot of sense at the time. Fixes bug 4169; bugfix on
8505 - If we had ever tried to call tor_addr_to_str() on an address of
8506 unknown type, we would have done a strdup() on an uninitialized
8507 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
8508 Reported by "troll_un".
8509 - Correctly detect and handle transient lookup failures from
8510 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
8511 Reported by "troll_un".
8512 - Use tor_socket_t type for listener argument to accept(). Fixes bug
8513 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
8514 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
8515 bug 4532; found by "troll_un".
8517 o Minor bugfixes (on Tor 0.2.3.x):
8518 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
8520 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
8521 circuit for use as a hidden service client's rendezvous point.
8522 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
8523 with help from wanoskarnet.
8524 - Restore behavior of overriding SocksPort, ORPort, and similar
8525 options from the command line. Bugfix on 0.2.3.3-alpha.
8528 - Properly handle the case where the build-tree is not the same
8529 as the source tree when generating src/common/common_sha1.i,
8530 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
8531 bugfix on 0.2.0.1-alpha.
8533 o Code simplifications, cleanups, and refactorings:
8534 - Remove the pure attribute from all functions that used it
8535 previously. In many cases we assigned it incorrectly, because the
8536 functions might assert or call impure functions, and we don't have
8537 evidence that keeping the pure attribute is worthwhile. Implements
8538 changes suggested in ticket 4421.
8539 - Remove some dead code spotted by coverity. Fixes cid 432.
8540 Bugfix on 0.2.3.1-alpha, closes bug 4637.
8543 Changes in version 0.2.3.8-alpha - 2011-11-22
8544 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
8545 socketpair-related bug that has been bothering Windows users. It adds
8546 support to serve microdescriptors to controllers, so Vidalia's network
8547 map can resume listing relays (once Vidalia implements its side),
8548 and adds better support for hardware AES acceleration. Finally, it
8549 starts the process of adjusting the bandwidth cutoff for getting the
8550 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
8551 that tiny relays harm performance more than they help network capacity.
8554 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8555 that it doesn't attempt to allocate a socketpair. This could cause
8556 some problems on Windows systems with overzealous firewalls. Fix for
8557 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8559 - Correctly sanity-check that we don't underflow on a memory
8560 allocation (and then assert) for hidden service introduction
8561 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8562 bugfix on 0.2.1.5-alpha.
8563 - Remove the artificially low cutoff of 20KB to guarantee the Fast
8564 flag. In the past few years the average relay speed has picked
8565 up, and while the "top 7/8 of the network get the Fast flag" and
8566 "all relays with 20KB or more of capacity get the Fast flag" rules
8567 used to have the same result, now the top 7/8 of the network has
8568 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
8569 - Fix a rare assertion failure when checking whether a v0 hidden
8570 service descriptor has any usable introduction points left, and
8571 we don't have enough information to build a circuit to the first
8572 intro point named in the descriptor. The HS client code in
8573 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
8574 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
8575 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
8576 - Make bridge authorities not crash when they are asked for their own
8577 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
8578 - When running as a client, do not print a misleading (and plain
8579 wrong) log message that we're collecting "directory request"
8580 statistics: clients don't collect statistics. Also don't create a
8581 useless (because empty) stats file in the stats/ directory. Fixes
8582 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
8585 - Allow Tor controllers like Vidalia to obtain the microdescriptor
8586 for a relay by identity digest or nickname. Previously,
8587 microdescriptors were only available by their own digests, so a
8588 controller would have to ask for and parse the whole microdescriptor
8589 consensus in order to look up a single relay's microdesc. Fixes
8590 bug 3832; bugfix on 0.2.3.1-alpha.
8591 - Use OpenSSL's EVP interface for AES encryption, so that all AES
8592 operations can use hardware acceleration (if present). Resolves
8595 o Minor bugfixes (on 0.2.2.x and earlier):
8596 - Detect failure to initialize Libevent. This fix provides better
8597 detection for future instances of bug 4457.
8598 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8599 function. This was eating up hideously large amounts of time on some
8600 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8601 - Don't warn about unused log_mutex in log.c when building with
8602 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8603 0.1.0.6-rc which introduced --disable-threads.
8604 - Allow manual 'authenticate' commands to the controller interface
8605 from netcat (nc) as well as telnet. We were rejecting them because
8606 they didn't come with the expected whitespace at the end of the
8607 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
8608 - Fix some (not actually triggerable) buffer size checks in usage of
8609 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
8611 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
8612 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
8613 - When configuring, starting, or stopping an NT service, stop
8614 immediately after the service configuration attempt has succeeded
8615 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8616 - When sending a NETINFO cell, include the original address
8617 received for the other side, not its canonical address. Found
8618 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8619 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
8620 can pick them up when the tests aren't disabled. Bugfix on
8621 0.2.2.4-alpha which introduced tinytest.
8622 - Fix a memory leak when we check whether a hidden service
8623 descriptor has any usable introduction points left. Fixes bug
8624 4424. Bugfix on 0.2.2.25-alpha.
8625 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8626 occurred when a client tried to fetch a descriptor for a bridge
8627 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
8629 o Minor bugfixes (on 0.2.3.x):
8630 - Make util unit tests build correctly with MSVC. Bugfix on
8631 0.2.3.3-alpha. Patch by Gisle Vanem.
8632 - Successfully detect AUTH_CHALLENGE cells with no recognized
8633 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
8635 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
8636 it should still send a NETINFO cell to allow the connection to
8637 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
8639 - Log less loudly when we get an invalid authentication certificate
8640 from a source other than a directory authority: it's not unusual
8641 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
8643 - Tolerate servers with more clock skew in their authentication
8644 certificates than previously. Fixes bug 4371; bugfix on
8646 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
8647 on 0.2.3.4-alpha and 0.2.3.6-alpha.
8650 - Add two new config options for directory authorities:
8651 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
8652 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
8653 that is always sufficient to satisfy the bandwidth requirement for
8654 the Guard flag. Now it will be easier for researchers to simulate
8655 Tor networks with different values. Resolves ticket 4484.
8656 - When Tor ignores a hidden service specified in its configuration,
8657 include the hidden service's directory in the warning message.
8658 Previously, we would only tell the user that some hidden service
8659 was ignored. Bugfix on 0.0.6; fixes bug 4426.
8660 - When we fail to initialize Libevent, retry with IOCP disabled so we
8661 don't need to turn on multi-threading support in Libevent, which in
8662 turn requires a working socketpair(). This is a workaround for bug
8663 4457, which affects Libevent versions from 2.0.1-alpha through
8665 - Detect when we try to build on a platform that doesn't define
8666 AF_UNSPEC to 0. We don't work there, so refuse to compile.
8667 - Update to the November 1 2011 Maxmind GeoLite Country database.
8669 o Packaging changes:
8670 - Make it easier to automate expert package builds on Windows,
8671 by removing an absolute path from makensis.exe command.
8673 o Code simplifications and refactoring:
8674 - Remove some redundant #include directives throughout the code.
8675 Patch from Andrea Gelmini.
8676 - Unconditionally use OpenSSL's AES implementation instead of our
8677 old built-in one. OpenSSL's AES has been better for a while, and
8678 relatively few servers should still be on any version of OpenSSL
8679 that doesn't have good optimized assembly AES.
8680 - Use the name "CERTS" consistently to refer to the new cell type;
8681 we were calling it CERT in some places and CERTS in others.
8684 - Numerous new unit tests for functions in util.c and address.c by
8686 - The long-disabled benchmark tests are now split into their own
8687 ./src/test/bench binary.
8688 - The benchmark tests can now use more accurate timers than
8689 gettimeofday() when such timers are available.
8692 Changes in version 0.2.3.7-alpha - 2011-10-30
8693 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
8694 the new v3 handshake. It also resolves yet another bridge address
8698 - If we mark an OR connection for close based on a cell we process,
8699 don't process any further cells on it. We already avoid further
8700 reads on marked-for-close connections, but now we also discard the
8701 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
8702 which was the first version where we might mark a connection for
8703 close based on processing a cell on it.
8704 - Fix a double-free bug that would occur when we received an invalid
8705 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
8706 bugfix on 0.2.3.6-alpha.
8707 - Bridges no longer include their address in NETINFO cells on outgoing
8708 OR connections, to allow them to blend in better with clients.
8709 Removes another avenue for enumerating bridges. Reported by
8710 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
8711 cells were introduced.
8714 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
8715 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
8718 Changes in version 0.2.3.6-alpha - 2011-10-26
8719 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
8720 anonymity vulnerability where an attacker can deanonymize Tor
8721 users. Everybody should upgrade.
8723 This release also features support for a new v3 connection handshake
8724 protocol, and fixes to make hidden service connections more robust.
8727 - Implement a new handshake protocol (v3) for authenticating Tors to
8728 each other over TLS. It should be more resistant to fingerprinting
8729 than previous protocols, and should require less TLS hacking for
8730 future Tor implementations. Implements proposal 176.
8731 - Allow variable-length padding cells to disguise the length of
8732 Tor's TLS records. Implements part of proposal 184.
8734 o Privacy/anonymity fixes (clients):
8735 - Clients and bridges no longer send TLS certificate chains on
8736 outgoing OR connections. Previously, each client or bridge would
8737 use the same cert chain for all outgoing OR connections until
8738 its IP address changes, which allowed any relay that the client
8739 or bridge contacted to determine which entry guards it is using.
8740 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8741 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8742 no longer considers that connection as suitable for satisfying a
8743 circuit EXTEND request. Now relays can protect clients from the
8744 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8745 - Directory authorities no longer assign the Guard flag to relays
8746 that haven't upgraded to the above "refuse EXTEND requests
8747 to client connections" fix. Now directory authorities can
8748 protect clients from the CVE-2011-2768 issue even if neither
8749 the clients nor the relays have upgraded yet. There's a new
8750 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
8751 to let us transition smoothly, else tomorrow there would be no
8754 o Major bugfixes (hidden services):
8755 - Improve hidden service robustness: when an attempt to connect to
8756 a hidden service ends, be willing to refetch its hidden service
8757 descriptors from each of the HSDir relays responsible for them
8758 immediately. Previously, we would not consider refetching the
8759 service's descriptors from each HSDir for 15 minutes after the last
8760 fetch, which was inconvenient if the hidden service was not running
8761 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
8762 - When one of a hidden service's introduction points appears to be
8763 unreachable, stop trying it. Previously, we would keep trying
8764 to build circuits to the introduction point until we lost the
8765 descriptor, usually because the user gave up and restarted Tor.
8766 Partly fixes bug 3825.
8767 - Don't launch a useless circuit after failing to use one of a
8768 hidden service's introduction points. Previously, we would
8769 launch a new introduction circuit, but not set the hidden service
8770 which that circuit was intended to connect to, so it would never
8771 actually be used. A different piece of code would then create a
8772 new introduction circuit correctly. Bug reported by katmagic and
8773 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8775 o Major bugfixes (other):
8776 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8777 that they initiated. Relays could distinguish incoming bridge
8778 connections from client connections, creating another avenue for
8779 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8780 Found by "frosty_un".
8781 - Don't update the AccountingSoftLimitHitAt state file entry whenever
8782 tor gets started. This prevents a wrong average bandwidth
8783 estimate, which would cause relays to always start a new accounting
8784 interval at the earliest possible moment. Fixes bug 2003; bugfix
8785 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
8786 immensely in tracking this bug down.
8787 - Fix a crash bug when changing node restrictions while a DNS lookup
8788 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8791 o Minor bugfixes (on 0.2.2.x and earlier):
8792 - When a hidden service turns an extra service-side introduction
8793 circuit into a general-purpose circuit, free the rend_data and
8794 intro_key fields first, so we won't leak memory if the circuit
8795 is cannibalized for use as another service-side introduction
8796 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8797 - Rephrase the log message emitted if the TestSocks check is
8798 successful. Patch from Fabian Keil; fixes bug 4094.
8799 - Bridges now skip DNS self-tests, to act a little more stealthily.
8800 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8801 bridges. Patch by "warms0x".
8802 - Remove a confusing dollar sign from the example fingerprint in the
8803 man page, and also make the example fingerprint a valid one. Fixes
8804 bug 4309; bugfix on 0.2.1.3-alpha.
8805 - Fix internal bug-checking logic that was supposed to catch
8806 failures in digest generation so that it will fail more robustly
8807 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8808 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8809 - Report any failure in init_keys() calls launched because our
8810 IP address has changed. Spotted by Coverity Scan. Bugfix on
8811 0.1.1.4-alpha; fixes CID 484.
8813 o Minor bugfixes (on 0.2.3.x):
8814 - Fix a bug in configure.in that kept it from building a configure
8815 script with autoconf versions earlier than 2.61. Fixes bug 2430;
8816 bugfix on 0.2.3.1-alpha.
8817 - Don't warn users that they are exposing a client port to the
8818 Internet if they have specified an RFC1918 address. Previously,
8819 we would warn if the user had specified any non-loopback
8820 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
8821 - Fix memory leaks in the failing cases of the new SocksPort and
8822 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
8823 fixes coverity CIDs 485, 486, and 487.
8826 - When a hidden service's introduction point times out, consider
8827 trying it again during the next attempt to connect to the
8828 HS. Previously, we would not try it again unless a newly fetched
8829 descriptor contained it. Required by fixes for bugs 1297 and 3825.
8830 - The next version of Windows will be called Windows 8, and it has
8831 a major version of 6, minor version of 2. Correctly identify that
8832 version instead of calling it "Very recent version". Resolves
8833 ticket 4153; reported by funkstar.
8834 - The Bridge Authority now writes statistics on how many bridge
8835 descriptors it gave out in total, and how many unique descriptors
8836 it gave out. It also lists how often the most and least commonly
8837 fetched descriptors were given out, as well as the median and
8838 25th/75th percentile. Implements tickets 4200 and 4294.
8839 - Update to the October 4 2011 Maxmind GeoLite Country database.
8841 o Code simplifications and refactoring:
8842 - Remove some old code to remember statistics about which descriptors
8843 we've served as a directory mirror. The feature wasn't used and
8844 is outdated now that microdescriptors are around.
8845 - Rename Tor functions that turn strings into addresses, so that
8846 "parse" indicates that no hostname resolution occurs, and
8847 "lookup" indicates that hostname resolution may occur. This
8848 should help prevent mistakes in the future. Fixes bug 3512.
8851 Changes in version 0.2.2.34 - 2011-10-26
8852 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
8853 can deanonymize Tor users. Everybody should upgrade.
8855 The attack relies on four components: 1) Clients reuse their TLS cert
8856 when talking to different relays, so relays can recognize a user by
8857 the identity key in her cert. 2) An attacker who knows the client's
8858 identity key can probe each guard relay to see if that identity key
8859 is connected to that guard relay right now. 3) A variety of active
8860 attacks in the literature (starting from "Low-Cost Traffic Analysis
8861 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
8862 discover the guard relays that a Tor user visiting the website is using.
8863 4) Clients typically pick three guards at random, so the set of guards
8864 for a given user could well be a unique fingerprint for her. This
8865 release fixes components #1 and #2, which is enough to block the attack;
8866 the other two remain as open research problems. Special thanks to
8867 "frosty_un" for reporting the issue to us!
8869 Clients should upgrade so they are no longer recognizable by the TLS
8870 certs they present. Relays should upgrade so they no longer allow a
8871 remote attacker to probe them to test whether unpatched clients are
8872 currently connected to them.
8874 This release also fixes several vulnerabilities that allow an attacker
8875 to enumerate bridge relays. Some bridge enumeration attacks still
8876 remain; see for example proposal 188.
8878 o Privacy/anonymity fixes (clients):
8879 - Clients and bridges no longer send TLS certificate chains on
8880 outgoing OR connections. Previously, each client or bridge would
8881 use the same cert chain for all outgoing OR connections until
8882 its IP address changes, which allowed any relay that the client
8883 or bridge contacted to determine which entry guards it is using.
8884 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8885 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8886 no longer considers that connection as suitable for satisfying a
8887 circuit EXTEND request. Now relays can protect clients from the
8888 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8889 - Directory authorities no longer assign the Guard flag to relays
8890 that haven't upgraded to the above "refuse EXTEND requests
8891 to client connections" fix. Now directory authorities can
8892 protect clients from the CVE-2011-2768 issue even if neither
8893 the clients nor the relays have upgraded yet. There's a new
8894 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
8895 to let us transition smoothly, else tomorrow there would be no
8898 o Privacy/anonymity fixes (bridge enumeration):
8899 - Bridge relays now do their directory fetches inside Tor TLS
8900 connections, like all the other clients do, rather than connecting
8901 directly to the DirPort like public relays do. Removes another
8902 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8903 - Bridges relays now build circuits for themselves in a more similar
8904 way to how clients build them. Removes another avenue for
8905 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8906 when bridges were introduced.
8907 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8908 that they initiated. Relays could distinguish incoming bridge
8909 connections from client connections, creating another avenue for
8910 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8911 Found by "frosty_un".
8914 - Fix a crash bug when changing node restrictions while a DNS lookup
8915 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8917 - Don't launch a useless circuit after failing to use one of a
8918 hidden service's introduction points. Previously, we would
8919 launch a new introduction circuit, but not set the hidden service
8920 which that circuit was intended to connect to, so it would never
8921 actually be used. A different piece of code would then create a
8922 new introduction circuit correctly. Bug reported by katmagic and
8923 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8926 - Change an integer overflow check in the OpenBSD_Malloc code so
8927 that GCC is less likely to eliminate it as impossible. Patch
8928 from Mansour Moufid. Fixes bug 4059.
8929 - When a hidden service turns an extra service-side introduction
8930 circuit into a general-purpose circuit, free the rend_data and
8931 intro_key fields first, so we won't leak memory if the circuit
8932 is cannibalized for use as another service-side introduction
8933 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8934 - Bridges now skip DNS self-tests, to act a little more stealthily.
8935 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8936 bridges. Patch by "warms0x".
8937 - Fix internal bug-checking logic that was supposed to catch
8938 failures in digest generation so that it will fail more robustly
8939 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8940 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8941 - Report any failure in init_keys() calls launched because our
8942 IP address has changed. Spotted by Coverity Scan. Bugfix on
8943 0.1.1.4-alpha; fixes CID 484.
8945 o Minor bugfixes (log messages and documentation):
8946 - Remove a confusing dollar sign from the example fingerprint in the
8947 man page, and also make the example fingerprint a valid one. Fixes
8948 bug 4309; bugfix on 0.2.1.3-alpha.
8949 - The next version of Windows will be called Windows 8, and it has
8950 a major version of 6, minor version of 2. Correctly identify that
8951 version instead of calling it "Very recent version". Resolves
8952 ticket 4153; reported by funkstar.
8953 - Downgrade log messages about circuit timeout calibration from
8954 "notice" to "info": they don't require or suggest any human
8955 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8956 bugfix on 0.2.2.14-alpha.
8959 - Turn on directory request statistics by default and include them in
8960 extra-info descriptors. Don't break if we have no GeoIP database.
8961 Backported from 0.2.3.1-alpha; implements ticket 3951.
8962 - Update to the October 4 2011 Maxmind GeoLite Country database.
8965 Changes in version 0.2.1.31 - 2011-10-26
8966 Tor 0.2.1.31 backports important security and privacy fixes for
8967 oldstable. This release is intended only for package maintainers and
8968 others who cannot use the 0.2.2 stable series. All others should be
8969 using Tor 0.2.2.x or newer.
8971 o Security fixes (also included in 0.2.2.x):
8972 - Replace all potentially sensitive memory comparison operations
8973 with versions whose runtime does not depend on the data being
8974 compared. This will help resist a class of attacks where an
8975 adversary can use variations in timing information to learn
8976 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8977 implementation by Robert Ransom based partially on code by DJB.)
8978 - Fix an assert in parsing router descriptors containing IPv6
8979 addresses. This one took down the directory authorities when
8980 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8982 o Privacy/anonymity fixes (also included in 0.2.2.x):
8983 - Clients and bridges no longer send TLS certificate chains on
8984 outgoing OR connections. Previously, each client or bridge would
8985 use the same cert chain for all outgoing OR connections until
8986 its IP address changes, which allowed any relay that the client
8987 or bridge contacted to determine which entry guards it is using.
8988 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8989 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8990 no longer considers that connection as suitable for satisfying a
8991 circuit EXTEND request. Now relays can protect clients from the
8992 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8993 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8994 that they initiated. Relays could distinguish incoming bridge
8995 connections from client connections, creating another avenue for
8996 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8997 Found by "frosty_un".
8998 - When receiving a hidden service descriptor, check that it is for
8999 the hidden service we wanted. Previously, Tor would store any
9000 hidden service descriptors that a directory gave it, whether it
9001 wanted them or not. This wouldn't have let an attacker impersonate
9002 a hidden service, but it did let directories pre-seed a client
9003 with descriptors that it didn't want. Bugfix on 0.0.6.
9004 - Avoid linkability based on cached hidden service descriptors: forget
9005 all hidden service descriptors cached as a client when processing a
9006 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9007 - Make the bridge directory authority refuse to answer directory
9008 requests for "all" descriptors. It used to include bridge
9009 descriptors in its answer, which was a major information leak.
9010 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9011 - Don't attach new streams to old rendezvous circuits after SIGNAL
9012 NEWNYM. Previously, we would keep using an existing rendezvous
9013 circuit if it remained open (i.e. if it were kept open by a
9014 long-lived stream, or if a new stream were attached to it before
9015 Tor could notice that it was old and no longer in use). Bugfix on
9016 0.1.1.15-rc; fixes bug 3375.
9018 o Minor bugfixes (also included in 0.2.2.x):
9019 - When we restart our relay, we might get a successful connection
9020 from the outside before we've started our reachability tests,
9021 triggering a warning: "ORPort found reachable, but I have no
9022 routerinfo yet. Failing to inform controller of success." This
9023 bug was harmless unless Tor is running under a controller
9024 like Vidalia, in which case the controller would never get a
9025 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
9027 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9028 enabled. Fixes bug 1526.
9029 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9030 anything since 0.2.1.16-rc.
9031 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9032 None of the cases where we did this before were wrong, but by making
9033 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9034 - Fix a rare crash bug that could occur when a client was configured
9035 with a large number of bridges. Fixes bug 2629; bugfix on
9036 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9037 - Correct the warning displayed when a rendezvous descriptor exceeds
9038 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9040 - Fix an uncommon assertion failure when running with DNSPort under
9041 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9042 - When warning about missing zlib development packages during compile,
9043 give the correct package names. Bugfix on 0.2.0.1-alpha.
9044 - Require that introduction point keys and onion keys have public
9045 exponent 65537. Bugfix on 0.2.0.10-alpha.
9046 - Do not crash when our configuration file becomes unreadable, for
9047 example due to a permissions change, between when we start up
9048 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
9050 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9052 - Always NUL-terminate the sun_path field of a sockaddr_un before
9053 passing it to the kernel. (Not a security issue: kernels are
9054 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9055 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9056 - Don't stack-allocate the list of supplementary GIDs when we're
9057 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9058 could take up to 256K, which is way too much stack. Found by
9059 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9061 o Minor bugfixes (only in 0.2.1.x):
9062 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
9063 rely on them. Bugfix on 0.2.1.30.
9064 - Use git revisions instead of svn revisions when generating our
9065 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9067 o Minor features (also included in 0.2.2.x):
9068 - Adjust the expiration time on our SSL session certificates to
9069 better match SSL certs seen in the wild. Resolves ticket 4014.
9070 - Allow nameservers with IPv6 address. Resolves bug 2574.
9071 - Update to the October 4 2011 Maxmind GeoLite Country database.
9074 Changes in version 0.2.3.5-alpha - 2011-09-28
9075 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
9076 bridge relays; fixes an assertion error that many users started hitting
9077 today; and adds the ability to refill token buckets more often than
9078 once per second, allowing significant performance improvements.
9081 - Bridge relays now do their directory fetches inside Tor TLS
9082 connections, like all the other clients do, rather than connecting
9083 directly to the DirPort like public relays do. Removes another
9084 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
9085 - Bridges relays now build circuits for themselves in a more similar
9086 way to how clients build them. Removes another avenue for
9087 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
9088 when bridges were introduced.
9091 - Fix an "Assertion md->held_by_node == 1 failed" error that could
9092 occur when the same microdescriptor was referenced by two node_t
9093 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
9095 o Major features (networking):
9096 - Add a new TokenBucketRefillInterval option to refill token buckets
9097 more frequently than once per second. This should improve network
9098 performance, alleviate queueing problems, and make traffic less
9099 bursty. Implements proposal 183; closes ticket 3630. Design by
9100 Florian Tschorsch and Björn Scheuermann; implementation by
9104 - Change an integer overflow check in the OpenBSD_Malloc code so
9105 that GCC is less likely to eliminate it as impossible. Patch
9106 from Mansour Moufid. Fixes bug 4059.
9108 o Minor bugfixes (usability):
9109 - Downgrade log messages about circuit timeout calibration from
9110 "notice" to "info": they don't require or suggest any human
9111 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
9112 bugfix on 0.2.2.14-alpha.
9114 o Minor features (diagnostics):
9115 - When the system call to create a listener socket fails, log the
9116 error message explaining why. This may help diagnose bug 4027.
9119 Changes in version 0.2.3.4-alpha - 2011-09-13
9120 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
9121 tweak to Tor's TLS handshake that makes relays and bridges that run
9122 this new version reachable from Iran again. It also fixes a few new
9123 bugs in 0.2.3.x, and teaches relays to recognize when they're not
9124 listed in the network consensus and republish.
9126 o Major bugfixes (also part of 0.2.2.33):
9127 - Avoid an assertion failure when reloading a configuration with
9128 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
9129 3923; bugfix on 0.2.2.25-alpha.
9131 o Minor features (security, also part of 0.2.2.33):
9132 - Check for replays of the public-key encrypted portion of an
9133 INTRODUCE1 cell, in addition to the current check for replays of
9134 the g^x value. This prevents a possible class of active attacks
9135 by an attacker who controls both an introduction point and a
9136 rendezvous point, and who uses the malleability of AES-CTR to
9137 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
9138 that these attacks are infeasible (requiring the attacker to send
9139 on the order of zettabytes of altered cells in a short interval),
9140 but we'd rather block them off in case there are any classes of
9141 this attack that we missed. Reported by Willem Pinckaers.
9143 o Minor features (also part of 0.2.2.33):
9144 - Adjust the expiration time on our SSL session certificates to
9145 better match SSL certs seen in the wild. Resolves ticket 4014.
9146 - Change the default required uptime for a relay to be accepted as
9147 a HSDir (hidden service directory) from 24 hours to 25 hours.
9148 Improves on 0.2.0.10-alpha; resolves ticket 2649.
9149 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
9150 authorities to abstain from voting on assignment of the HSDir
9151 consensus flag. Related to bug 2649.
9152 - Update to the September 6 2011 Maxmind GeoLite Country database.
9154 o Minor bugfixes (also part of 0.2.2.33):
9155 - Demote the 'replay detected' log message emitted when a hidden
9156 service receives the same Diffie-Hellman public key in two different
9157 INTRODUCE2 cells to info level. A normal Tor client can cause that
9158 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
9159 fixes part of bug 2442.
9160 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
9161 level. There is nothing that a hidden service's operator can do
9162 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
9164 - Clarify a log message specifying the characters permitted in
9165 HiddenServiceAuthorizeClient client names. Previously, the log
9166 message said that "[A-Za-z0-9+-_]" were permitted; that could have
9167 given the impression that every ASCII character between "+" and "_"
9168 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
9170 o Build fixes (also part of 0.2.2.33):
9171 - Clean up some code issues that prevented Tor from building on older
9172 BSDs. Fixes bug 3894; reported by "grarpamp".
9173 - Search for a platform-specific version of "ar" when cross-compiling.
9174 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
9177 - Fix a bug where the SocksPort option (for example) would get
9178 ignored and replaced by the default if a SocksListenAddress
9179 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
9183 - Relays now try regenerating and uploading their descriptor more
9184 frequently if they are not listed in the consensus, or if the
9185 version of their descriptor listed in the consensus is too
9186 old. This fix should prevent situations where a server declines
9187 to re-publish itself because it has done so too recently, even
9188 though the authorities decided not to list its recent-enough
9189 descriptor. Fix for bug 3327.
9192 - Relays now include a reason for regenerating their descriptors
9193 in an HTTP header when uploading to the authorities. This will
9194 make it easier to debug descriptor-upload issues in the future.
9195 - When starting as root and then changing our UID via the User
9196 control option, and we have a ControlSocket configured, make sure
9197 that the ControlSocket is owned by the same account that Tor will
9198 run under. Implements ticket 3421; fix by Jérémy Bobbio.
9201 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
9202 utility function used in the control-port code). This shouldn't
9203 ever happen unless Tor is completely out of memory, but if it did
9204 happen and Tor somehow recovered from it, Tor could have sent a log
9205 message to a control port in the middle of a reply to a controller
9206 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
9207 - Make 'FetchUselessDescriptors' cause all descriptor types and
9208 all consensus types (including microdescriptors) to get fetched.
9209 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
9212 - Make a new "entry connection" struct as an internal subtype of "edge
9213 connection", to simplify the code and make exit connections smaller.
9216 Changes in version 0.2.2.33 - 2011-09-13
9217 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
9218 TLS handshake that makes relays and bridges that run this new version
9219 reachable from Iran again.
9222 - Avoid an assertion failure when reloading a configuration with
9223 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
9224 3923; bugfix on 0.2.2.25-alpha.
9226 o Minor features (security):
9227 - Check for replays of the public-key encrypted portion of an
9228 INTRODUCE1 cell, in addition to the current check for replays of
9229 the g^x value. This prevents a possible class of active attacks
9230 by an attacker who controls both an introduction point and a
9231 rendezvous point, and who uses the malleability of AES-CTR to
9232 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
9233 that these attacks are infeasible (requiring the attacker to send
9234 on the order of zettabytes of altered cells in a short interval),
9235 but we'd rather block them off in case there are any classes of
9236 this attack that we missed. Reported by Willem Pinckaers.
9239 - Adjust the expiration time on our SSL session certificates to
9240 better match SSL certs seen in the wild. Resolves ticket 4014.
9241 - Change the default required uptime for a relay to be accepted as
9242 a HSDir (hidden service directory) from 24 hours to 25 hours.
9243 Improves on 0.2.0.10-alpha; resolves ticket 2649.
9244 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
9245 authorities to abstain from voting on assignment of the HSDir
9246 consensus flag. Related to bug 2649.
9247 - Update to the September 6 2011 Maxmind GeoLite Country database.
9249 o Minor bugfixes (documentation and log messages):
9250 - Correct the man page to explain that HashedControlPassword and
9251 CookieAuthentication can both be set, in which case either method
9252 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
9253 when we decided to allow these config options to both be set. Issue
9255 - Demote the 'replay detected' log message emitted when a hidden
9256 service receives the same Diffie-Hellman public key in two different
9257 INTRODUCE2 cells to info level. A normal Tor client can cause that
9258 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
9259 fixes part of bug 2442.
9260 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
9261 level. There is nothing that a hidden service's operator can do
9262 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
9264 - Clarify a log message specifying the characters permitted in
9265 HiddenServiceAuthorizeClient client names. Previously, the log
9266 message said that "[A-Za-z0-9+-_]" were permitted; that could have
9267 given the impression that every ASCII character between "+" and "_"
9268 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
9271 - Provide a substitute implementation of lround() for MSVC, which
9272 apparently lacks it. Patch from Gisle Vanem.
9273 - Clean up some code issues that prevented Tor from building on older
9274 BSDs. Fixes bug 3894; reported by "grarpamp".
9275 - Search for a platform-specific version of "ar" when cross-compiling.
9276 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
9279 Changes in version 0.2.3.3-alpha - 2011-09-01
9280 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
9281 security, and provides client-side support for the microdescriptor
9282 and optimistic data features introduced earlier in the 0.2.3.x
9283 series. It also includes numerous critical bugfixes in the (optional)
9284 bufferevent-based networking backend.
9286 o Major features (stream isolation):
9287 - You can now configure Tor so that streams from different
9288 applications are isolated on different circuits, to prevent an
9289 attacker who sees your streams as they leave an exit node from
9290 linking your sessions to one another. To do this, choose some way
9291 to distinguish the applications: have them connect to different
9292 SocksPorts, or have one of them use SOCKS4 while the other uses
9293 SOCKS5, or have them pass different authentication strings to the
9294 SOCKS proxy. Then, use the new SocksPort syntax to configure the
9295 degree of isolation you need. This implements Proposal 171.
9296 - There's a new syntax for specifying multiple client ports (such as
9297 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
9298 multiple *Port entries with full addr:port syntax on each.
9299 The old *ListenAddress format is still supported, but you can't
9300 mix it with the new *Port syntax.
9302 o Major features (other):
9303 - Enable microdescriptor fetching by default for clients. This allows
9304 clients to download a much smaller amount of directory information.
9305 To disable it (and go back to the old-style consensus and
9306 descriptors), set "UseMicrodescriptors 0" in your torrc file.
9307 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
9308 "PortForwarding" config option), now supports Windows.
9309 - When using an exit relay running 0.2.3.x, clients can now
9310 "optimistically" send data before the exit relay reports that
9311 the stream has opened. This saves a round trip when starting
9312 connections where the client speaks first (such as web browsing).
9313 This behavior is controlled by a consensus parameter (currently
9314 disabled). To turn it on or off manually, use the "OptimisticData"
9315 torrc option. Implements proposal 181; code by Ian Goldberg.
9317 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
9318 - When using IOCP on Windows, we need to enable Libevent windows
9320 - The IOCP backend now works even when the user has not specified
9321 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
9322 Fixes part of bug 3752.
9323 - Correctly record the bytes we've read and written when using
9324 bufferevents, so that we can include them in our bandwidth history
9325 and advertised bandwidth. Fixes bug 3803.
9326 - Apply rate-limiting only at the bottom of a chain of filtering
9327 bufferevents. This prevents us from filling up internal read
9328 buffers and violating rate-limits when filtering bufferevents
9329 are enabled. Fixes part of bug 3804.
9330 - Add high-watermarks to the output buffers for filtered
9331 bufferevents. This prevents us from filling up internal write
9332 buffers and wasting CPU cycles when filtering bufferevents are
9333 enabled. Fixes part of bug 3804.
9334 - Correctly notice when data has been written from a bufferevent
9335 without flushing it completely. Fixes bug 3805.
9336 - Fix a bug where server-side tunneled bufferevent-based directory
9337 streams would get closed prematurely. Fixes bug 3814.
9338 - Fix a use-after-free error with per-connection rate-limiting
9339 buckets. Fixes bug 3888.
9341 o Major bugfixes (also part of 0.2.2.31-rc):
9342 - If we're configured to write our ControlPorts to disk, only write
9343 them after switching UID and creating the data directory. This way,
9344 we don't fail when starting up with a nonexistent DataDirectory
9345 and a ControlPortWriteToFile setting based on that directory. Fixes
9346 bug 3747; bugfix on Tor 0.2.2.26-beta.
9349 - Added a new CONF_CHANGED event so that controllers can be notified
9350 of any configuration changes made by other controllers, or by the
9351 user. Implements ticket 1692.
9352 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
9353 leak when using bufferevents, and lets Libevent worry about how to
9354 best copy data out of a buffer.
9355 - Replace files in stats/ rather than appending to them. Now that we
9356 include statistics in extra-info descriptors, it makes no sense to
9357 keep old statistics forever. Implements ticket 2930.
9359 o Minor features (build compatibility):
9360 - Limited, experimental support for building with nmake and MSVC.
9361 - Provide a substitute implementation of lround() for MSVC, which
9362 apparently lacks it. Patch from Gisle Vanem.
9364 o Minor features (also part of 0.2.2.31-rc):
9365 - Update to the August 2 2011 Maxmind GeoLite Country database.
9367 o Minor bugfixes (on 0.2.3.x-alpha):
9368 - Fix a spurious warning when parsing SOCKS requests with
9369 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
9370 - Get rid of a harmless warning that could happen on relays running
9371 with bufferevents. The warning was caused by someone doing an http
9372 request to a relay's orport. Also don't warn for a few related
9373 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
9375 o Minor bugfixes (on 2.2.x and earlier):
9376 - Correct the man page to explain that HashedControlPassword and
9377 CookieAuthentication can both be set, in which case either method
9378 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
9379 when we decided to allow these config options to both be set. Issue
9381 - The "--quiet" and "--hush" options now apply not only to Tor's
9382 behavior before logs are configured, but also to Tor's behavior in
9383 the absense of configured logs. Fixes bug 3550; bugfix on
9386 o Minor bugfixes (also part of 0.2.2.31-rc):
9387 - Write several files in text mode, on OSes that distinguish text
9388 mode from binary mode (namely, Windows). These files are:
9389 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9390 that collect those statistics; 'client_keys' and 'hostname' for
9391 hidden services that use authentication; and (in the tor-gencert
9392 utility) newly generated identity and signing keys. Previously,
9393 we wouldn't specify text mode or binary mode, leading to an
9394 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9395 the DirRecordUsageByCountry option which would have triggered
9396 the assertion failure was added), although this assertion failure
9397 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9398 - Selectively disable deprecation warnings on OS X because Lion
9399 started deprecating the shipped copy of openssl. Fixes bug 3643.
9400 - Remove an extra pair of quotation marks around the error
9401 message in control-port STATUS_GENERAL BUG events. Bugfix on
9402 0.1.2.6-alpha; fixes bug 3732.
9403 - When unable to format an address as a string, report its value
9404 as "???" rather than reusing the last formatted address. Bugfix
9407 o Code simplifications and refactoring:
9408 - Rewrite the listener-selection logic so that parsing which ports
9409 we want to listen on is now separate from binding to the ports
9413 - Building Tor with bufferevent support now requires Libevent
9414 2.0.13-stable or later. Previous versions of Libevent had bugs in
9415 SSL-related bufferevents and related issues that would make Tor
9416 work badly with bufferevents. Requiring 2.0.13-stable also allows
9417 Tor with bufferevents to take advantage of Libevent APIs
9418 introduced after 2.0.8-rc.
9421 Changes in version 0.2.2.32 - 2011-08-27
9422 The Tor 0.2.2 release series is dedicated to the memory of Andreas
9423 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
9424 a founder of the PETS community, a leader in our field, a mentor,
9425 and a friend. He left us with these words: "I had the possibility
9426 to contribute to this world that is not as it should be. I hope I
9427 could help in some areas to make the world a better place, and that
9428 I could also encourage other people to be engaged in improving the
9429 world. Please, stay engaged. This world needs you, your love, your
9430 initiative -- now I cannot be part of that anymore."
9432 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
9433 ready. More than two years in the making, this release features improved
9434 client performance and hidden service reliability, better compatibility
9435 for Android, correct behavior for bridges that listen on more than
9436 one address, more extensible and flexible directory object handling,
9437 better reporting of network statistics, improved code security, and
9438 many many other features and bugfixes.
9441 Changes in version 0.2.2.31-rc - 2011-08-17
9442 Tor 0.2.2.31-rc is the second and hopefully final release candidate
9443 for the Tor 0.2.2.x series.
9446 - Remove an extra pair of quotation marks around the error
9447 message in control-port STATUS_GENERAL BUG events. Bugfix on
9448 0.1.2.6-alpha; fixes bug 3732.
9449 - If we're configured to write our ControlPorts to disk, only write
9450 them after switching UID and creating the data directory. This way,
9451 we don't fail when starting up with a nonexistent DataDirectory
9452 and a ControlPortWriteToFile setting based on that directory. Fixes
9453 bug 3747; bugfix on Tor 0.2.2.26-beta.
9456 - Update to the August 2 2011 Maxmind GeoLite Country database.
9459 - Allow GETINFO fingerprint to return a fingerprint even when
9460 we have not yet built a router descriptor. Fixes bug 3577;
9461 bugfix on 0.2.0.1-alpha.
9462 - Write several files in text mode, on OSes that distinguish text
9463 mode from binary mode (namely, Windows). These files are:
9464 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9465 that collect those statistics; 'client_keys' and 'hostname' for
9466 hidden services that use authentication; and (in the tor-gencert
9467 utility) newly generated identity and signing keys. Previously,
9468 we wouldn't specify text mode or binary mode, leading to an
9469 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9470 the DirRecordUsageByCountry option which would have triggered
9471 the assertion failure was added), although this assertion failure
9472 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9473 - Selectively disable deprecation warnings on OS X because Lion
9474 started deprecating the shipped copy of openssl. Fixes bug 3643.
9475 - When unable to format an address as a string, report its value
9476 as "???" rather than reusing the last formatted address. Bugfix
9480 Changes in version 0.2.3.2-alpha - 2011-07-18
9481 Tor 0.2.3.2-alpha introduces two new experimental features:
9482 microdescriptors and pluggable transports. It also continues cleaning
9483 up a variety of recently introduced features.
9486 - Clients can now use microdescriptors instead of regular descriptors
9487 to build circuits. Microdescriptors are authority-generated
9488 summaries of regular descriptors' contents, designed to change
9489 very rarely (see proposal 158 for details). This feature is
9490 designed to save bandwidth, especially for clients on slow internet
9491 connections. It's off by default for now, since nearly no caches
9492 support it, but it will be on-by-default for clients in a future
9493 version. You can use the UseMicrodescriptors option to turn it on.
9494 - Tor clients using bridges can now be configured to use a separate
9495 'transport' proxy for each bridge. This approach helps to resist
9496 censorship by allowing bridges to use protocol obfuscation
9497 plugins. It implements part of proposal 180. Implements ticket 2841.
9498 - While we're trying to bootstrap, record how many TLS connections
9499 fail in each state, and report which states saw the most failures
9500 in response to any bootstrap failures. This feature may speed up
9501 diagnosis of censorship events. Implements ticket 3116.
9503 o Major bugfixes (on 0.2.3.1-alpha):
9504 - When configuring a large set of nodes in EntryNodes (as with
9505 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
9506 random subset to be guards, and choose them in random
9507 order. Fixes bug 2798.
9508 - Tor could crash when remembering a consensus in a non-used consensus
9509 flavor without having a current consensus set. Fixes bug 3361.
9510 - Comparing an unknown address to a microdescriptor's shortened exit
9511 policy would always give a "rejected" result. Fixes bug 3599.
9512 - Using microdescriptors as a client no longer prevents Tor from
9513 uploading and downloading hidden service descriptors. Fixes
9517 - Allow nameservers with IPv6 address. Resolves bug 2574.
9518 - Accept attempts to include a password authenticator in the
9519 handshake, as supported by SOCKS5. This handles SOCKS clients that
9520 don't know how to omit a password when authenticating. Resolves
9522 - When configuring a large set of nodes in EntryNodes, and there are
9523 enough of them listed as Guard so that we don't need to consider
9524 the non-guard entries, prefer the ones listed with the Guard flag.
9525 - Check for and recover from inconsistency in the microdescriptor
9526 cache. This will make it harder for us to accidentally free a
9527 microdescriptor without removing it from the appropriate data
9528 structures. Fixes issue 3135; issue noted by "wanoskarnet".
9529 - Log SSL state transitions at log level DEBUG, log domain
9530 HANDSHAKE. This can be useful for debugging censorship events.
9531 Implements ticket 3264.
9532 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
9533 implements ticket 3439.
9535 o Minor bugfixes (on 0.2.3.1-alpha):
9536 - Do not free all general-purpose regular descriptors just
9537 because microdescriptor use is enabled. Fixes bug 3113.
9538 - Correctly link libevent_openssl when --enable-static-libevent
9539 is passed to configure. Fixes bug 3118.
9540 - Bridges should not complain during their heartbeat log messages that
9541 they are unlisted in the consensus: that's more or less the point
9542 of being a bridge. Fixes bug 3183.
9543 - Report a SIGNAL event to controllers when acting on a delayed
9544 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
9545 event to the controller if we acted on a SIGNAL NEWNYM command
9546 immediately, and otherwise not report a SIGNAL event for the
9547 command at all. Fixes bug 3349.
9548 - Fix a crash when handling the SIGNAL controller command or
9549 reporting ERR-level status events with bufferevents enabled. Found
9550 by Robert Ransom. Fixes bug 3367.
9551 - Always ship the tor-fw-helper manpage in our release tarballs.
9552 Fixes bug 3389. Reported by Stephen Walker.
9553 - Fix a class of double-mark-for-close bugs when bufferevents
9554 are enabled. Fixes bug 3403.
9555 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
9556 - Add SIGNAL to the list returned by the 'GETINFO events/names'
9557 control-port command. Fixes part of bug 3465.
9558 - Prevent using negative indices during unit test runs when read_all()
9559 fails. Spotted by coverity.
9560 - Fix a rare memory leak when checking the nodelist without it being
9561 present. Found by coverity.
9562 - Only try to download a microdescriptor-flavored consensus from
9563 a directory cache that provides them.
9565 o Minor bugfixes (on 0.2.2.x and earlier):
9566 - Assert that hidden-service-related operations are not performed
9567 using single-hop circuits. Previously, Tor would assert that
9568 client-side streams are not attached to single-hop circuits,
9569 but not that other sensitive operations on the client and service
9570 side are not performed using single-hop circuits. Fixes bug 3332;
9572 - Don't publish a new relay descriptor when we reload our onion key,
9573 unless the onion key has actually changed. Fixes bug 3263 and
9574 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
9575 - Allow GETINFO fingerprint to return a fingerprint even when
9576 we have not yet built a router descriptor. Fixes bug 3577;
9577 bugfix on 0.2.0.1-alpha.
9578 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
9579 on 0.2.2.4-alpha; fixes bug 3427.
9581 o Code simplification and refactoring:
9582 - Use tor_sscanf() in place of scanf() in more places through the
9583 code. This makes us a little more locale-independent, and
9584 should help shut up code-analysis tools that can't tell
9585 a safe sscanf string from a dangerous one.
9586 - Use tt_assert(), not tor_assert(), for checking for test failures.
9587 This makes the unit tests more able to go on in the event that
9589 - Split connection_about_to_close() into separate functions for each
9593 - On Windows, we now define the _WIN32_WINNT macros only if they
9594 are not already defined. This lets the person building Tor decide,
9595 if they want, to require a later version of Windows.
9598 Changes in version 0.2.2.30-rc - 2011-07-07
9599 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
9600 series. It fixes a few smaller bugs, but generally appears stable.
9601 Please test it and let us know whether it is!
9604 - Send a SUCCEEDED stream event to the controller when a reverse
9605 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
9606 discovered by katmagic.
9607 - Always NUL-terminate the sun_path field of a sockaddr_un before
9608 passing it to the kernel. (Not a security issue: kernels are
9609 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9610 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9611 - Don't stack-allocate the list of supplementary GIDs when we're
9612 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9613 could take up to 256K, which is way too much stack. Found by
9614 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9615 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
9616 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
9617 fixes part of bug 3465.
9618 - Fix a memory leak when receiving a descriptor for a hidden
9619 service we didn't ask for. Found by Coverity; CID #30. Bugfix
9623 - Update to the July 1 2011 Maxmind GeoLite Country database.
9626 Changes in version 0.2.2.29-beta - 2011-06-20
9627 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
9628 have bridge lines in their torrc but don't want to use them; gets
9629 us closer to having the control socket feature working on Debian;
9630 and fixes a variety of smaller bugs.
9633 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
9634 When we changed the default behavior to "use bridges if any
9635 are listed in the torrc", we surprised users who had bridges
9636 in their torrc files but who didn't actually want to use them.
9637 Partial resolution for bug 3354.
9640 - Don't attach new streams to old rendezvous circuits after SIGNAL
9641 NEWNYM. Previously, we would keep using an existing rendezvous
9642 circuit if it remained open (i.e. if it were kept open by a
9643 long-lived stream, or if a new stream were attached to it before
9644 Tor could notice that it was old and no longer in use). Bugfix on
9645 0.1.1.15-rc; fixes bug 3375.
9648 - Fix a bug when using ControlSocketsGroupWritable with User. The
9649 directory's group would be checked against the current group, not
9650 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
9651 bugfix on 0.2.2.26-beta.
9652 - Make connection_printf_to_buf()'s behavior sane. Its callers
9653 expect it to emit a CRLF iff the format string ends with CRLF;
9654 it actually emitted a CRLF iff (a) the format string ended with
9655 CRLF or (b) the resulting string was over 1023 characters long or
9656 (c) the format string did not end with CRLF *and* the resulting
9657 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
9658 fixes part of bug 3407.
9659 - Make send_control_event_impl()'s behavior sane. Its callers
9660 expect it to always emit a CRLF at the end of the string; it
9661 might have emitted extra control characters as well. Bugfix on
9662 0.1.1.9-alpha; fixes another part of bug 3407.
9663 - Make crypto_rand_int() check the value of its input correctly.
9664 Previously, it accepted values up to UINT_MAX, but could return a
9665 negative number if given a value above INT_MAX+1. Found by George
9666 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
9667 - Avoid a segfault when reading a malformed circuit build state
9668 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
9670 - When asked about a DNS record type we don't support via a
9671 client DNSPort, reply with NOTIMPL rather than an empty
9672 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
9673 - Fix a rare memory leak during stats writing. Found by coverity.
9676 - Update to the June 1 2011 Maxmind GeoLite Country database.
9678 o Code simplifications and refactoring:
9679 - Remove some dead code as indicated by coverity.
9680 - Remove a few dead assignments during router parsing. Found by
9682 - Add some forgotten return value checks during unit tests. Found
9684 - Don't use 1-bit wide signed bit fields. Found by coverity.
9687 Changes in version 0.2.2.28-beta - 2011-06-04
9688 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
9689 fixed a big bug in whether relays stay in the consensus consistently,
9690 we moved closer to handling bridges and hidden services correctly,
9691 and we started the process of better handling the dreaded "my Vidalia
9692 died, and now my Tor demands a password when I try to reconnect to it"
9696 - Don't decide to make a new descriptor when receiving a HUP signal.
9697 This bug has caused a lot of 0.2.2.x relays to disappear from the
9698 consensus periodically. Fixes the most common case of triggering
9699 bug 1810; bugfix on 0.2.2.7-alpha.
9700 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
9701 - Don't try to build descriptors if "ORPort auto" is set and we
9702 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
9704 - Resolve a crash that occurred when setting BridgeRelay to 1 with
9705 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
9706 - Apply circuit timeouts to opened hidden-service-related circuits
9707 based on the correct start time. Previously, we would apply the
9708 circuit build timeout based on time since the circuit's creation;
9709 it was supposed to be applied based on time since the circuit
9710 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
9711 - Use the same circuit timeout for client-side introduction
9712 circuits as for other four-hop circuits, rather than the timeout
9713 for single-hop directory-fetch circuits; the shorter timeout may
9714 have been appropriate with the static circuit build timeout in
9715 0.2.1.x and earlier, but caused many hidden service access attempts
9716 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
9717 on 0.2.2.2-alpha; fixes another part of bug 1297.
9718 - In ticket 2511 we fixed a case where you could use an unconfigured
9719 bridge if you had configured it as a bridge the last time you ran
9720 Tor. Now fix another edge case: if you had configured it as a bridge
9721 but then switched to a different bridge via the controller, you
9722 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
9726 - Add an __OwningControllerProcess configuration option and a
9727 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
9728 that when it exits, Tor will shut down. Implements feature 3049.
9729 - If "UseBridges 1" is set and no bridges are configured, Tor will
9730 now refuse to build any circuits until some bridges are set.
9731 If "UseBridges auto" is set, Tor will use bridges if they are
9732 configured and we are not running as a server, but otherwise will
9733 make circuits as usual. The new default is "auto". Patch by anonym,
9734 so the Tails LiveCD can stop automatically revealing you as a Tor
9738 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9739 - Remove a trailing asterisk from "exit-policy/default" in the
9740 output of the control port command "GETINFO info/names". Bugfix
9742 - Use a wide type to hold sockets when built for 64-bit Windows builds.
9744 - Warn when the user configures two HiddenServiceDir lines that point
9745 to the same directory. Bugfix on 0.0.6 (the version introducing
9746 HiddenServiceDir); fixes bug 3289.
9747 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
9748 part of bug 2748; bugfix on 0.2.0.10-alpha.
9749 - Log malformed requests for rendezvous descriptors as protocol
9750 warnings, not warnings. Also, use a more informative log message
9751 in case someone sees it at log level warning without prior
9752 info-level messages. Fixes the other part of bug 2748; bugfix
9754 - Clear the table recording the time of the last request for each
9755 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
9756 Previously, we would clear our HS descriptor cache on SIGNAL
9757 NEWNYM, but if we had previously retrieved a descriptor (or tried
9758 to) from every directory responsible for it, we would refuse to
9759 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
9761 - Fix a log message that said "bits" while displaying a value in
9762 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
9764 - When checking for 1024-bit keys, check for 1024 bits, not 128
9765 bytes. This allows Tor to correctly discard keys of length 1017
9766 through 1023. Bugfix on 0.0.9pre5.
9769 - Relays now log the reason for publishing a new relay descriptor,
9770 so we have a better chance of hunting down instances of bug 1810.
9771 Resolves ticket 3252.
9772 - Revise most log messages that refer to nodes by nickname to
9773 instead use the "$key=nickname at address" format. This should be
9774 more useful, especially since nicknames are less and less likely
9775 to be unique. Resolves ticket 3045.
9776 - Log (at info level) when purging pieces of hidden-service-client
9777 state because of SIGNAL NEWNYM.
9780 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9781 anything since 0.2.1.16-rc.
9784 Changes in version 0.2.2.27-beta - 2011-05-18
9785 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
9786 release, and also adds a few more general bugfixes.
9789 - Fix a crash bug when changing bridges in a running Tor process.
9790 Fixes bug 3213; bugfix on 0.2.2.26-beta.
9791 - When the controller configures a new bridge, don't wait 10 to 60
9792 seconds before trying to fetch its descriptor. Bugfix on
9793 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
9796 - Require that onion keys have exponent 65537 in microdescriptors too.
9797 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
9798 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
9799 Changed the limit to 512 characters by removing base64 newlines.
9800 Fixes bug 2752. Fix by Michael Yakubovich.
9801 - When a client starts or stops using bridges, never use a circuit
9802 that was built before the configuration change. This behavior could
9803 put at risk a user who uses bridges to ensure that her traffic
9804 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
9808 Changes in version 0.2.2.26-beta - 2011-05-17
9809 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
9810 also introduces a new "socksport auto" approach that should make it
9811 easier to run multiple Tors on the same system, and does a lot of
9812 cleanup to get us closer to a release candidate.
9814 o Security/privacy fixes:
9815 - Replace all potentially sensitive memory comparison operations
9816 with versions whose runtime does not depend on the data being
9817 compared. This will help resist a class of attacks where an
9818 adversary can use variations in timing information to learn
9819 sensitive data. Fix for one case of bug 3122. (Safe memcmp
9820 implementation by Robert Ransom based partially on code by DJB.)
9821 - When receiving a hidden service descriptor, check that it is for
9822 the hidden service we wanted. Previously, Tor would store any
9823 hidden service descriptors that a directory gave it, whether it
9824 wanted them or not. This wouldn't have let an attacker impersonate
9825 a hidden service, but it did let directories pre-seed a client
9826 with descriptors that it didn't want. Bugfix on 0.0.6.
9827 - On SIGHUP, do not clear out all TrackHostExits mappings, client
9828 DNS cache entries, and virtual address mappings: that's what
9829 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
9832 - The options SocksPort, ControlPort, and so on now all accept a
9833 value "auto" that opens a socket on an OS-selected port. A
9834 new ControlPortWriteToFile option tells Tor to write its
9835 actual control port or ports to a chosen file. If the option
9836 ControlPortFileGroupReadable is set, the file is created as
9837 group-readable. Now users can run two Tor clients on the same
9838 system without needing to manually mess with parameters. Resolves
9839 part of ticket 3076.
9840 - Set SO_REUSEADDR on all sockets, not just listeners. This should
9841 help busy exit nodes avoid running out of useable ports just
9842 because all the ports have been used in the near past. Resolves
9846 - New "GETINFO net/listeners/(type)" controller command to return
9847 a list of addresses and ports that are bound for listeners for a
9848 given connection type. This is useful when the user has configured
9849 "SocksPort auto" and the controller needs to know which port got
9850 chosen. Resolves another part of ticket 3076.
9851 - Add a new ControlSocketsGroupWritable configuration option: when
9852 it is turned on, ControlSockets are group-writeable by the default
9853 group of the current user. Patch by Jérémy Bobbio; implements
9855 - Tor now refuses to create a ControlSocket in a directory that is
9856 world-readable (or group-readable if ControlSocketsGroupWritable
9857 is 0). This is necessary because some operating systems do not
9858 enforce permissions on an AF_UNIX sockets. Permissions on the
9859 directory holding the socket, however, seems to work everywhere.
9860 - Rate-limit a warning about failures to download v2 networkstatus
9861 documents. Resolves part of bug 1352.
9862 - Backport code from 0.2.3.x that allows directory authorities to
9863 clean their microdescriptor caches. Needed to resolve bug 2230.
9864 - When an HTTPS proxy reports "403 Forbidden", we now explain
9865 what it means rather than calling it an unexpected status code.
9866 Closes bug 2503. Patch from Michael Yakubovich.
9867 - Update to the May 1 2011 Maxmind GeoLite Country database.
9870 - Authorities now clean their microdesc cache periodically and when
9871 reading from disk initially, not only when adding new descriptors.
9872 This prevents a bug where we could lose microdescriptors. Bugfix
9873 on 0.2.2.6-alpha. Fixes bug 2230.
9874 - Do not crash when our configuration file becomes unreadable, for
9875 example due to a permissions change, between when we start up
9876 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
9878 - Avoid a bug that would keep us from replacing a microdescriptor
9879 cache on Windows. (We would try to replace the file while still
9880 holding it open. That's fine on Unix, but Windows doesn't let us
9881 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
9882 - Add missing explanations for the authority-related torrc options
9883 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
9884 man page. Resolves issue 2379.
9885 - As an authority, do not upload our own vote or signature set to
9886 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
9887 it would get flagged as a duplicate. Resolves bug 3026.
9888 - Accept hidden service descriptors if we think we might be a hidden
9889 service directory, regardless of what our consensus says. This
9890 helps robustness, since clients and hidden services can sometimes
9891 have a more up-to-date view of the network consensus than we do,
9892 and if they think that the directory authorities list us a HSDir,
9893 we might actually be one. Related to bug 2732; bugfix on
9895 - When a controller changes TrackHostExits, remove mappings for
9896 hosts that should no longer have their exits tracked. Bugfix on
9898 - When a controller changes VirtualAddrNetwork, remove any mappings
9899 for hosts that were automapped to the old network. Bugfix on
9901 - When a controller changes one of the AutomapHosts* options, remove
9902 any mappings for hosts that should no longer be automapped. Bugfix
9904 - Do not reset the bridge descriptor download status every time we
9905 re-parse our configuration or get a configuration change. Fixes
9906 bug 3019; bugfix on 0.2.0.3-alpha.
9908 o Minor bugfixes (code cleanup):
9909 - When loading the microdesc journal, remember its current size.
9910 In 0.2.2, this helps prevent the microdesc journal from growing
9911 without limit on authorities (who are the only ones to use it in
9912 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
9913 Fix posted by "cypherpunks."
9914 - The microdesc journal is supposed to get rebuilt only if it is
9915 at least _half_ the length of the store, not _twice_ the length
9916 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
9917 - Fix a potential null-pointer dereference while computing a
9918 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
9920 - Avoid a possible null-pointer dereference when rebuilding the mdesc
9921 cache without actually having any descriptors to cache. Bugfix on
9922 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
9923 - If we fail to compute the identity digest of a v3 legacy keypair,
9924 warn, and don't use a buffer-full of junk instead. Bugfix on
9925 0.2.1.1-alpha; fixes bug 3106.
9926 - Resolve an untriggerable issue in smartlist_string_num_isin(),
9927 where if the function had ever in the future been used to check
9928 for the presence of a too-large number, it would have given an
9929 incorrect result. (Fortunately, we only used it for 16-bit
9930 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
9931 - Require that introduction point keys and onion handshake keys
9932 have a public exponent of 65537. Starts to fix bug 3207; bugfix
9936 - Caches no longer download and serve v2 networkstatus documents
9937 unless FetchV2Networkstatus flag is set: these documents haven't
9938 haven't been used by clients or relays since 0.2.0.x. Resolves
9942 Changes in version 0.2.3.1-alpha - 2011-05-05
9943 Tor 0.2.3.1-alpha adds some new experimental features, including support
9944 for an improved network IO backend, IOCP networking on Windows,
9945 microdescriptor caching, "fast-start" support for streams, and automatic
9946 home router configuration. There are also numerous internal improvements
9947 to try to make the code easier for developers to work with.
9949 This is the first alpha release in a new series, so expect there to be
9950 bugs. Users who would rather test out a more stable branch should
9951 stay with 0.2.2.x for now.
9954 - Tor can now optionally build with the "bufferevents" buffered IO
9955 backend provided by Libevent 2. To use this feature, make sure you
9956 have the latest possible version of Libevent, and pass the
9957 --enable-bufferevents flag to configure when building Tor from
9958 source. This feature will make our networking code more flexible,
9959 let us stack layers on each other, and let us use more efficient
9960 zero-copy transports where available.
9961 - As an experimental feature, Tor can use IOCP for networking on Windows.
9962 Once this code is tuned and optimized, it promises much better
9963 performance than the select-based backend we've used in the past. To
9964 try this feature, you must build Tor with Libevent 2, configure Tor
9965 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
9966 your torrc. There are known bugs here: only try this if you can help
9967 debug it as it breaks.
9968 - The EntryNodes option can now include country codes like {de} or IP
9969 addresses or network masks. Previously we had disallowed these options
9970 because we didn't have an efficient way to keep the list up to
9971 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
9972 - Exit nodes now accept and queue data on not-yet-connected streams.
9973 Previously, the client wasn't allowed to send data until the stream was
9974 connected, which slowed down all connections. This change will enable
9975 clients to perform a "fast-start" on streams and send data without
9976 having to wait for a confirmation that the stream has opened. (Patch
9977 from Ian Goldberg; implements the server side of Proposal 174.)
9978 - Tor now has initial support for automatic port mapping on the many
9979 home routers that support NAT-PMP or UPnP. (Not yet supported on
9980 Windows). To build the support code, you'll need to have libnatpnp
9981 library and/or the libminiupnpc library, and you'll need to enable the
9982 feature specifically by passing "--enable-upnp" and/or
9983 "--enable-natpnp" to configure. To turn it on, use the new
9984 PortForwarding option.
9985 - Caches now download, cache, and serve multiple "flavors" of the
9986 consensus, including a flavor that describes microdescriptors.
9987 - Caches now download, cache, and serve microdescriptors -- small
9988 summaries of router descriptors that are authenticated by all of the
9989 directory authorities. Once enough caches are running this code,
9990 clients will be able to save significant amounts of directory bandwidth
9991 by downloading microdescriptors instead of router descriptors.
9994 - Make logging resolution configurable with a new LogTimeGranularity
9995 option, and change the default from 1 millisecond to 1 second.
9996 Implements enhancement 1668.
9997 - We log which torrc file we're using on startup. Implements ticket
9999 - Ordinarily, Tor does not count traffic from private addresses (like
10000 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
10001 There is now a new option, CountPrivateBandwidth, to disable this
10002 behavior. Patch from Daniel Cagara.
10003 - New --enable-static-tor configure option for building Tor as
10004 statically as possible. Idea, general hackery and thoughts from
10005 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
10007 - If you set the NumCPUs option to 0, Tor will now try to detect how
10008 many CPUs you have. This is the new default behavior.
10009 - Turn on directory request statistics by default and include them in
10010 extra-info descriptors. Don't break if we have no GeoIP database.
10011 - Relays that set "ConnDirectionStatistics 1" write statistics on the
10012 bidirectional use of connections to disk every 24 hours.
10013 - Add a GeoIP file digest to the extra-info descriptor. Implements
10015 - The NodeFamily option -- which let you declare that you want to
10016 consider nodes to be part of a family whether they list themselves
10017 that way or not -- now allows IP address ranges and country codes.
10018 - Add a new 'Heartbeat' log message type to periodically log a message
10019 describing Tor's status at level Notice. This feature is meant for
10020 operators who log at notice, and want to make sure that their Tor
10021 server is still working. Implementation by George Kadianakis.
10023 o Minor bugfixes (on 0.2.2.25-alpha):
10024 - When loading the microdesc journal, remember its current size.
10025 In 0.2.2, this helps prevent the microdesc journal from growing
10026 without limit on authorities (who are the only ones to use it in
10027 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
10028 Fix posted by "cypherpunks."
10029 - The microdesc journal is supposed to get rebuilt only if it is
10030 at least _half_ the length of the store, not _twice_ the length
10031 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
10032 - If as an authority we fail to compute the identity digest of a v3
10033 legacy keypair, warn, and don't use a buffer-full of junk instead.
10034 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
10035 - Authorities now clean their microdesc cache periodically and when
10036 reading from disk initially, not only when adding new descriptors.
10037 This prevents a bug where we could lose microdescriptors. Bugfix
10040 o Minor features (controller):
10041 - Add a new SIGNAL event to the controller interface so that
10042 controllers can be notified when Tor handles a signal. Resolves
10043 issue 1955. Patch by John Brooks.
10044 - Add a new GETINFO option to get total bytes read and written. Patch
10045 from pipe, revised by atagar. Resolves ticket 2345.
10046 - Implement some GETINFO controller fields to provide information about
10047 the Tor process's pid, euid, username, and resource limits.
10050 - Our build system requires automake 1.6 or later to create the
10051 Makefile.in files. Previously, you could have used 1.4.
10052 This only affects developers and people building Tor from git;
10053 people who build Tor from the source distribution without changing
10054 the Makefile.am files should be fine.
10055 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
10056 so on. This is more robust against some of the failure modes
10057 associated with running the autotools pieces on their own.
10059 o Minor packaging issues:
10060 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
10061 already created. Patch from Andreas Stieger. Fixes bug 2573.
10063 o Code simplifications and refactoring:
10064 - A major revision to our internal node-selecting and listing logic.
10065 Tor already had at least two major ways to look at the question of
10066 "which Tor servers do we know about": a list of router descriptors,
10067 and a list of entries in the current consensus. With
10068 microdescriptors, we're adding a third. Having so many systems
10069 without an abstraction layer over them was hurting the codebase.
10070 Now, we have a new "node_t" abstraction that presents a consistent
10071 interface to a client's view of a Tor node, and holds (nearly) all
10072 of the mutable state formerly in routerinfo_t and routerstatus_t.
10073 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
10074 no longer link against Libevent: they never used it, but
10075 our library structure used to force them to link it.
10077 o Removed features:
10078 - Remove some old code to work around even older versions of Tor that
10079 used forked processes to handle DNS requests. Such versions of Tor
10080 are no longer in use as servers.
10082 o Documentation fixes:
10083 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
10084 - Add missing documentation for the authority-related torrc options
10085 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
10089 Changes in version 0.2.2.25-alpha - 2011-04-29
10090 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
10091 robust, routers no longer overreport their bandwidth, Win7 should crash
10092 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
10093 now prevents hidden service-related activity from being linkable. It
10094 provides more information to Vidalia so you can see if your bridge is
10095 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
10096 StrictNodes configuration options to make them more reliable, more
10097 understandable, and more regularly applied. If you use those options,
10098 please see the revised documentation for them in the manual page.
10101 - Relays were publishing grossly inflated bandwidth values because
10102 they were writing their state files wrong--now they write the
10103 correct value. Also, resume reading bandwidth history from the
10104 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
10105 - Improve hidden service robustness: When we find that we have
10106 extended a hidden service's introduction circuit to a relay not
10107 listed as an introduction point in the HS descriptor we currently
10108 have, retry with an introduction point from the current
10109 descriptor. Previously we would just give up. Fixes bugs 1024 and
10110 1930; bugfix on 0.2.0.10-alpha.
10111 - Clients now stop trying to use an exit node associated with a given
10112 destination by TrackHostExits if they fail to reach that exit node.
10113 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
10114 - Fix crash bug on platforms where gmtime and localtime can return
10115 NULL. Windows 7 users were running into this one. Fixes part of bug
10116 2077. Bugfix on all versions of Tor. Found by boboper.
10118 o Security and stability fixes:
10119 - Don't double-free a parsable, but invalid, microdescriptor, even if
10120 it is followed in the blob we're parsing by an unparsable
10121 microdescriptor. Fixes an issue reported in a comment on bug 2954.
10122 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
10123 - If the Nickname configuration option isn't given, Tor would pick a
10124 nickname based on the local hostname as the nickname for a relay.
10125 Because nicknames are not very important in today's Tor and the
10126 "Unnamed" nickname has been implemented, this is now problematic
10127 behavior: It leaks information about the hostname without being
10128 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
10129 introduced the Unnamed nickname. Reported by tagnaq.
10130 - Fix an uncommon assertion failure when running with DNSPort under
10131 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
10132 - Avoid linkability based on cached hidden service descriptors: forget
10133 all hidden service descriptors cached as a client when processing a
10134 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
10137 - Export GeoIP information on bridge usage to controllers even if we
10138 have not yet been running for 24 hours. Now Vidalia bridge operators
10139 can get more accurate and immediate feedback about their
10140 contributions to the network.
10142 o Major features and bugfixes (node selection):
10143 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
10144 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
10145 options. Previously, we had been ambiguous in describing what
10146 counted as an "exit" node, and what operations exactly "StrictNodes
10147 0" would permit. This created confusion when people saw nodes built
10148 through unexpected circuits, and made it hard to tell real bugs from
10149 surprises. Now the intended behavior is:
10150 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
10151 a node that delivers user traffic outside the Tor network.
10152 . "Entry", in the context of EntryNodes, means a node used as the
10153 first hop of a multihop circuit. It doesn't include direct
10154 connections to directory servers.
10155 . "ExcludeNodes" applies to all nodes.
10156 . "StrictNodes" changes the behavior of ExcludeNodes only. When
10157 StrictNodes is set, Tor should avoid all nodes listed in
10158 ExcludeNodes, even when it will make user requests fail. When
10159 StrictNodes is *not* set, then Tor should follow ExcludeNodes
10160 whenever it can, except when it must use an excluded node to
10161 perform self-tests, connect to a hidden service, provide a
10162 hidden service, fulfill a .exit request, upload directory
10163 information, or fetch directory information.
10164 Collectively, the changes to implement the behavior fix bug 1090.
10165 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
10166 a node is listed in both, it's treated as excluded.
10167 - ExcludeNodes now applies to directory nodes -- as a preference if
10168 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
10169 Don't exclude all the directory authorities and set StrictNodes to 1
10170 unless you really want your Tor to break.
10171 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
10172 - ExcludeExitNodes now overrides .exit requests.
10173 - We don't use bridges listed in ExcludeNodes.
10174 - When StrictNodes is 1:
10175 . We now apply ExcludeNodes to hidden service introduction points
10176 and to rendezvous points selected by hidden service users. This
10177 can make your hidden service less reliable: use it with caution!
10178 . If we have used ExcludeNodes on ourself, do not try relay
10179 reachability self-tests.
10180 . If we have excluded all the directory authorities, we will not
10181 even try to upload our descriptor if we're a relay.
10182 . Do not honor .exit requests to an excluded node.
10183 - Remove a misfeature that caused us to ignore the Fast/Stable flags
10184 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
10185 - When the set of permitted nodes changes, we now remove any mappings
10186 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
10188 - We never cannibalize a circuit that had excluded nodes on it, even
10189 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
10190 - Revert a change where we would be laxer about attaching streams to
10191 circuits than when building the circuits. This was meant to prevent
10192 a set of bugs where streams were never attachable, but our improved
10193 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
10194 - Keep track of how many times we launch a new circuit to handle a
10195 given stream. Too many launches could indicate an inconsistency
10196 between our "launch a circuit to handle this stream" logic and our
10197 "attach this stream to one of the available circuits" logic.
10198 - Improve log messages related to excluded nodes.
10201 - Fix a spurious warning when moving from a short month to a long
10202 month on relays with month-based BandwidthAccounting. Bugfix on
10203 0.2.2.17-alpha; fixes bug 3020.
10204 - When a client finds that an origin circuit has run out of 16-bit
10205 stream IDs, we now mark it as unusable for new streams. Previously,
10206 we would try to close the entire circuit. Bugfix on 0.0.6.
10207 - Add a forgotten cast that caused a compile warning on OS X 10.6.
10208 Bugfix on 0.2.2.24-alpha.
10209 - Be more careful about reporting the correct error from a failed
10210 connect() system call. Under some circumstances, it was possible to
10211 look at an incorrect value for errno when sending the end reason.
10212 Bugfix on 0.1.0.1-rc.
10213 - Correctly handle an "impossible" overflow cases in connection byte
10214 counting, where we write or read more than 4GB on an edge connection
10215 in a single second. Bugfix on 0.1.2.8-beta.
10216 - Correct the warning displayed when a rendezvous descriptor exceeds
10217 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
10219 - Clients and hidden services now use HSDir-flagged relays for hidden
10220 service descriptor downloads and uploads even if the relays have no
10221 DirPort set and the client has disabled TunnelDirConns. This will
10222 eventually allow us to give the HSDir flag to relays with no
10223 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
10224 - Downgrade "no current certificates known for authority" message from
10225 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
10226 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
10227 2917. Bugfix on 0.1.1.1-alpha.
10228 - Only limit the lengths of single HS descriptors, even when multiple
10229 HS descriptors are published to an HSDir relay in a single POST
10230 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
10231 - Write the current time into the LastWritten line in our state file,
10232 rather than the time from the previous write attempt. Also, stop
10233 trying to use a time of -1 in our log statements. Fixes bug 3039;
10234 bugfix on 0.2.2.14-alpha.
10235 - Be more consistent in our treatment of file system paths. "~" should
10236 get expanded to the user's home directory in the Log config option.
10237 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
10238 feature for the -f and --DataDirectory options.
10241 - Make sure every relay writes a state file at least every 12 hours.
10242 Previously, a relay could go for weeks without writing its state
10243 file, and on a crash could lose its bandwidth history, capacity
10244 estimates, client country statistics, and so on. Addresses bug 3012.
10245 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
10246 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
10247 clients are already deprecated because of security bugs.
10248 - Don't allow v0 hidden service authorities to act as clients.
10249 Required by fix for bug 3000.
10250 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
10251 by fix for bug 3000.
10252 - Ensure that no empty [dirreq-](read|write)-history lines are added
10253 to an extrainfo document. Implements ticket 2497.
10255 o Code simplification and refactoring:
10256 - Remove workaround code to handle directory responses from servers
10257 that had bug 539 (they would send HTTP status 503 responses _and_
10258 send a body too). Since only server versions before
10259 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
10260 keep the workaround in place.
10261 - Remove the old 'fuzzy time' logic. It was supposed to be used for
10262 handling calculations where we have a known amount of clock skew and
10263 an allowed amount of unknown skew. But we only used it in three
10264 places, and we never adjusted the known/unknown skew values. This is
10265 still something we might want to do someday, but if we do, we'll
10266 want to do it differently.
10267 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
10268 None of the cases where we did this before were wrong, but by making
10269 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
10270 - Use GetTempDir to find the proper temporary directory location on
10271 Windows when generating temporary files for the unit tests. Patch by
10275 Changes in version 0.2.2.24-alpha - 2011-04-08
10276 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
10277 prevented Tor clients from effectively using "multihomed" bridges,
10278 that is, bridges that listen on multiple ports or IP addresses so users
10279 can continue to use some of their addresses even if others get blocked.
10282 - Fix a bug where bridge users who configure the non-canonical
10283 address of a bridge automatically switch to its canonical
10284 address. If a bridge listens at more than one address, it should be
10285 able to advertise those addresses independently and any non-blocked
10286 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
10288 - If you configured Tor to use bridge A, and then quit and
10289 configured Tor to use bridge B instead, it would happily continue
10290 to use bridge A if it's still reachable. While this behavior is
10291 a feature if your goal is connectivity, in some scenarios it's a
10292 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
10293 - Directory authorities now use data collected from their own
10294 uptime observations when choosing whether to assign the HSDir flag
10295 to relays, instead of trusting the uptime value the relay reports in
10296 its descriptor. This change helps prevent an attack where a small
10297 set of nodes with frequently-changing identity keys can blackhole
10298 a hidden service. (Only authorities need upgrade; others will be
10299 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
10302 - When we restart our relay, we might get a successful connection
10303 from the outside before we've started our reachability tests,
10304 triggering a warning: "ORPort found reachable, but I have no
10305 routerinfo yet. Failing to inform controller of success." This
10306 bug was harmless unless Tor is running under a controller
10307 like Vidalia, in which case the controller would never get a
10308 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
10310 - Make directory authorities more accurate at recording when
10311 relays that have failed several reachability tests became
10312 unreachable, so we can provide more accuracy at assigning Stable,
10313 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
10314 - Fix an issue that prevented static linking of libevent on
10315 some platforms (notably Linux). Fixes bug 2698; bugfix on
10316 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
10317 the --with-static-libevent configure option).
10318 - We now ask the other side of a stream (the client or the exit)
10319 for more data on that stream when the amount of queued data on
10320 that stream dips low enough. Previously, we wouldn't ask the
10321 other side for more data until either it sent us more data (which
10322 it wasn't supposed to do if it had exhausted its window!) or we
10323 had completely flushed all our queued data. This flow control fix
10324 should improve throughput. Fixes bug 2756; bugfix on the earliest
10325 released versions of Tor (svn commit r152).
10326 - Avoid a double-mark-for-free warning when failing to attach a
10327 transparent proxy connection. (We thought we had fixed this in
10328 0.2.2.23-alpha, but it turns out our fix was checking the wrong
10329 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
10330 bug) and 0.2.2.23-alpha (the incorrect fix).
10331 - When warning about missing zlib development packages during compile,
10332 give the correct package names. Bugfix on 0.2.0.1-alpha.
10335 - Directory authorities now log the source of a rejected POSTed v3
10336 networkstatus vote.
10337 - Make compilation with clang possible when using
10338 --enable-gcc-warnings by removing two warning options that clang
10339 hasn't implemented yet and by fixing a few warnings. Implements
10341 - When expiring circuits, use microsecond timers rather than
10342 one-second timers. This can avoid an unpleasant situation where a
10343 circuit is launched near the end of one second and expired right
10344 near the beginning of the next, and prevent fluctuations in circuit
10346 - Use computed circuit-build timeouts to decide when to launch
10347 parallel introduction circuits for hidden services. (Previously,
10348 we would retry after 15 seconds.)
10349 - Update to the April 1 2011 Maxmind GeoLite Country database.
10352 - Create the /var/run/tor directory on startup on OpenSUSE if it is
10353 not already created. Patch from Andreas Stieger. Fixes bug 2573.
10355 o Documentation changes:
10356 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
10357 - Resolve all doxygen warnings except those for missing documentation.
10359 - Add doxygen documentation for more functions, fields, and types.
10362 Changes in version 0.2.2.23-alpha - 2011-03-08
10363 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
10364 they restart they don't lose their bandwidth capacity estimate. This
10365 release also fixes a diverse set of user-facing bugs, ranging from
10366 relays overrunning their rate limiting to clients falsely warning about
10367 clock skew to bridge descriptor leaks by our bridge directory authority.
10370 - Stop sending a CLOCK_SKEW controller status event whenever
10371 we fetch directory information from a relay that has a wrong clock.
10372 Instead, only inform the controller when it's a trusted authority
10373 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
10374 the rest of bug 1074.
10375 - Fix an assert in parsing router descriptors containing IPv6
10376 addresses. This one took down the directory authorities when
10377 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
10378 - Make the bridge directory authority refuse to answer directory
10379 requests for "all" descriptors. It used to include bridge
10380 descriptors in its answer, which was a major information leak.
10381 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
10382 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
10383 Tor would ignore their RelayBandwidthBurst setting,
10384 potentially using more bandwidth than expected. Bugfix on
10385 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
10386 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
10387 hidserv" in her torrc. The 'hidserv' argument never controlled
10388 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
10391 - Relays now save observed peak bandwidth throughput rates to their
10392 state file (along with total usage, which was already saved)
10393 so that they can determine their correct estimated bandwidth on
10394 restart. Resolves bug 1863, where Tor relays would reset their
10395 estimated bandwidth to 0 after restarting.
10396 - Directory authorities now take changes in router IP address and
10397 ORPort into account when determining router stability. Previously,
10398 if a router changed its IP or ORPort, the authorities would not
10399 treat it as having any downtime for the purposes of stability
10400 calculation, whereas clients would experience downtime since the
10401 change could take a while to propagate to them. Resolves issue 1035.
10402 - Enable Address Space Layout Randomization (ASLR) and Data Execution
10403 Prevention (DEP) by default on Windows to make it harder for
10404 attackers to exploit vulnerabilities. Patch from John Brooks.
10406 o Minor bugfixes (on 0.2.1.x and earlier):
10407 - Fix a rare crash bug that could occur when a client was configured
10408 with a large number of bridges. Fixes bug 2629; bugfix on
10409 0.2.1.2-alpha. Bugfix by trac user "shitlei".
10410 - Avoid a double mark-for-free warning when failing to attach a
10411 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
10413 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
10414 found by "cypherpunks". This bug was introduced before the first
10415 Tor release, in svn commit r110.
10416 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
10417 don't mention them in the manpage. Fixes bug 2450; issue
10418 spotted by keb and G-Lo.
10419 - Fix a bug in bandwidth history state parsing that could have been
10420 triggered if a future version of Tor ever changed the timing
10421 granularity at which bandwidth history is measured. Bugfix on
10422 Tor 0.1.1.11-alpha.
10423 - When a relay decides that its DNS is too broken for it to serve
10424 as an exit server, it advertised itself as a non-exit, but
10425 continued to act as an exit. This could create accidental
10426 partitioning opportunities for users. Instead, if a relay is
10427 going to advertise reject *:* as its exit policy, it should
10428 really act with exit policy "reject *:*". Fixes bug 2366.
10429 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
10430 - In the special case where you configure a public exit relay as your
10431 bridge, Tor would be willing to use that exit relay as the last
10432 hop in your circuit as well. Now we fail that circuit instead.
10433 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
10434 - Fix a bug with our locking implementation on Windows that couldn't
10435 correctly detect when a file was already locked. Fixes bug 2504,
10436 bugfix on 0.2.1.6-alpha.
10437 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
10438 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
10440 - Set target port in get_interface_address6() correctly. Bugfix
10441 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
10442 - Directory authorities are now more robust to hops back in time
10443 when calculating router stability. Previously, if a run of uptime
10444 or downtime appeared to be negative, the calculation could give
10445 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
10447 - Fix an assert that got triggered when using the TestingTorNetwork
10448 configuration option and then issuing a GETINFO config-text control
10449 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
10451 o Minor bugfixes (on 0.2.2.x):
10452 - Clients should not weight BadExit nodes as Exits in their node
10453 selection. Similarly, directory authorities should not count BadExit
10454 bandwidth as Exit bandwidth when computing bandwidth-weights.
10455 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
10456 - Correctly clear our dir_read/dir_write history when there is an
10457 error parsing any bw history value from the state file. Bugfix on
10458 Tor 0.2.2.15-alpha.
10459 - Resolve a bug in verifying signatures of directory objects
10460 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
10461 Fixes bug 2409. Found by "piebeer".
10462 - Bridge authorities no longer crash on SIGHUP when they try to
10463 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
10467 - Log less aggressively about circuit timeout changes, and improve
10468 some other circuit timeout messages. Resolves bug 2004.
10469 - Log a little more clearly about the times at which we're no longer
10470 accepting new connections. Resolves bug 2181.
10471 - Reject attempts at the client side to open connections to private
10472 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
10473 a randomly chosen exit node. Attempts to do so are always
10474 ill-defined, generally prevented by exit policies, and usually
10475 in error. This will also help to detect loops in transparent
10476 proxy configurations. You can disable this feature by setting
10477 "ClientRejectInternalAddresses 0" in your torrc.
10478 - Always treat failure to allocate an RSA key as an unrecoverable
10480 - Update to the March 1 2011 Maxmind GeoLite Country database.
10482 o Minor features (log subsystem):
10483 - Add documentation for configuring logging at different severities in
10484 different log domains. We've had this feature since 0.2.1.1-alpha,
10485 but for some reason it never made it into the manpage. Fixes
10487 - Make it simpler to specify "All log domains except for A and B".
10488 Previously you needed to say "[*,~A,~B]". Now you can just say
10490 - Add a "LogMessageDomains 1" option to include the domains of log
10491 messages along with the messages. Without this, there's no way
10492 to use log domains without reading the source or doing a lot
10495 o Packaging changes:
10496 - Stop shipping the Tor specs files and development proposal documents
10497 in the tarball. They are now in a separate git repository at
10498 git://git.torproject.org/torspec.git
10501 Changes in version 0.2.1.30 - 2011-02-23
10502 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
10503 change is a slight tweak to Tor's TLS handshake that makes relays
10504 and bridges that run this new version reachable from Iran again.
10505 We don't expect this tweak will win the arms race long-term, but it
10506 buys us time until we roll out a better solution.
10509 - Stop sending a CLOCK_SKEW controller status event whenever
10510 we fetch directory information from a relay that has a wrong clock.
10511 Instead, only inform the controller when it's a trusted authority
10512 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
10513 the rest of bug 1074.
10514 - Fix a bounds-checking error that could allow an attacker to
10515 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10516 Found by "piebeer".
10517 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
10518 Tor would ignore their RelayBandwidthBurst setting,
10519 potentially using more bandwidth than expected. Bugfix on
10520 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
10521 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
10522 hidserv" in her torrc. The 'hidserv' argument never controlled
10523 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
10526 - Adjust our TLS Diffie-Hellman parameters to match those used by
10528 - Update to the February 1 2011 Maxmind GeoLite Country database.
10531 - Check for and reject overly long directory certificates and
10532 directory tokens before they have a chance to hit any assertions.
10533 Bugfix on 0.2.1.28. Found by "doorss".
10534 - Bring the logic that gathers routerinfos and assesses the
10535 acceptability of circuits into line. This prevents a Tor OP from
10536 getting locked in a cycle of choosing its local OR as an exit for a
10537 path (due to a .exit request) and then rejecting the circuit because
10538 its OR is not listed yet. It also prevents Tor clients from using an
10539 OR running in the same instance as an exit (due to a .exit request)
10540 if the OR does not meet the same requirements expected of an OR
10541 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10543 o Packaging changes:
10544 - Stop shipping the Tor specs files and development proposal documents
10545 in the tarball. They are now in a separate git repository at
10546 git://git.torproject.org/torspec.git
10547 - Do not include Git version tags as though they are SVN tags when
10548 generating a tarball from inside a repository that has switched
10549 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
10552 Changes in version 0.2.2.22-alpha - 2011-01-25
10553 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
10554 main other change is a slight tweak to Tor's TLS handshake that makes
10555 relays and bridges that run this new version reachable from Iran again.
10556 We don't expect this tweak will win the arms race long-term, but it
10557 will buy us a bit more time until we roll out a better solution.
10560 - Fix a bounds-checking error that could allow an attacker to
10561 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10562 Found by "piebeer".
10563 - Don't assert when changing from bridge to relay or vice versa
10564 via the controller. The assert happened because we didn't properly
10565 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
10566 bug 2433. Reported by bastik.
10569 - Adjust our TLS Diffie-Hellman parameters to match those used by
10571 - Provide a log message stating which geoip file we're parsing
10572 instead of just stating that we're parsing the geoip file.
10573 Implements ticket 2432.
10576 - Check for and reject overly long directory certificates and
10577 directory tokens before they have a chance to hit any assertions.
10578 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
10581 Changes in version 0.2.2.21-alpha - 2011-01-15
10582 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
10583 continues our recent code security audit work. The main fix resolves
10584 a remote heap overflow vulnerability that can allow remote code
10585 execution (CVE-2011-0427). Other fixes address a variety of assert
10586 and crash bugs, most of which we think are hard to exploit remotely.
10588 o Major bugfixes (security), also included in 0.2.1.29:
10589 - Fix a heap overflow bug where an adversary could cause heap
10590 corruption. This bug probably allows remote code execution
10591 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10593 - Prevent a denial-of-service attack by disallowing any
10594 zlib-compressed data whose compression factor is implausibly
10595 high. Fixes part of bug 2324; reported by "doorss".
10596 - Zero out a few more keys in memory before freeing them. Fixes
10597 bug 2384 and part of bug 2385. These key instances found by
10598 "cypherpunks", based on Andrew Case's report about being able
10599 to find sensitive data in Tor's memory space if you have enough
10600 permissions. Bugfix on 0.0.2pre9.
10602 o Major bugfixes (crashes), also included in 0.2.1.29:
10603 - Prevent calls to Libevent from inside Libevent log handlers.
10604 This had potential to cause a nasty set of crashes, especially
10605 if running Libevent with debug logging enabled, and running
10606 Tor with a controller watching for low-severity log messages.
10607 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10608 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10609 underflow errors there too. Fixes the other part of bug 2324.
10610 - Fix a bug where we would assert if we ever had a
10611 cached-descriptors.new file (or another file read directly into
10612 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10613 on 0.2.1.25. Found by doorss.
10614 - Fix some potential asserts and parsing issues with grossly
10615 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10618 o Minor bugfixes (other), also included in 0.2.1.29:
10619 - Fix a bug with handling misformed replies to reverse DNS lookup
10620 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10621 bug reported by doorss.
10622 - Fix compilation on mingw when a pthreads compatibility library
10623 has been installed. (We don't want to use it, so we shouldn't
10624 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10625 - Fix a bug where we would declare that we had run out of virtual
10626 addresses when the address space was only half-exhausted. Bugfix
10628 - Correctly handle the case where AutomapHostsOnResolve is set but
10629 no virtual addresses are available. Fixes bug 2328; bugfix on
10630 0.1.2.1-alpha. Bug found by doorss.
10631 - Correctly handle wrapping around when we run out of virtual
10632 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
10634 o Minor features, also included in 0.2.1.29:
10635 - Update to the January 1 2011 Maxmind GeoLite Country database.
10636 - Introduce output size checks on all of our decryption functions.
10638 o Build changes, also included in 0.2.1.29:
10639 - Tor does not build packages correctly with Automake 1.6 and earlier;
10640 added a check to Makefile.am to make sure that we're building with
10641 Automake 1.7 or later.
10642 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
10643 because we built it with a too-old version of automake. Thus that
10644 release broke ./configure --enable-openbsd-malloc, which is popular
10645 among really fast exit relays on Linux.
10647 o Major bugfixes, new in 0.2.2.21-alpha:
10648 - Prevent crash/heap corruption when the cbtnummodes consensus
10649 parameter is set to 0 or large values. Fixes bug 2317; bugfix
10652 o Major features, new in 0.2.2.21-alpha:
10653 - Introduce minimum/maximum values that clients will believe
10654 from the consensus. Now we'll have a better chance to avoid crashes
10655 or worse when a consensus param has a weird value.
10657 o Minor features, new in 0.2.2.21-alpha:
10658 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
10659 used on bridges, and it makes bridge scanning somewhat easier.
10660 - If writing the state file to disk fails, wait up to an hour before
10661 retrying again, rather than trying again each second. Fixes bug
10662 2346; bugfix on Tor 0.1.1.3-alpha.
10663 - Make Libevent log messages get delivered to controllers later,
10664 and not from inside the Libevent log handler. This prevents unsafe
10665 reentrant Libevent calls while still letting the log messages
10667 - Detect platforms that brokenly use a signed size_t, and refuse to
10668 build there. Found and analyzed by doorss and rransom.
10669 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
10672 o Minor bugfixes, new in 0.2.2.21-alpha:
10673 - Handle SOCKS messages longer than 128 bytes long correctly, rather
10674 than waiting forever for them to finish. Fixes bug 2330; bugfix
10675 on 0.2.0.16-alpha. Found by doorss.
10676 - Add assertions to check for overflow in arguments to
10677 base32_encode() and base32_decode(); fix a signed-unsigned
10678 comparison there too. These bugs are not actually reachable in Tor,
10679 but it's good to prevent future errors too. Found by doorss.
10680 - Correctly detect failures to create DNS requests when using Libevent
10681 versions before v2. (Before Libevent 2, we used our own evdns
10682 implementation. Its return values for Libevent's evdns_resolve_*()
10683 functions are not consistent with those from Libevent.) Fixes bug
10684 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
10686 o Documentation, new in 0.2.2.21-alpha:
10687 - Document the default socks host and port (127.0.0.1:9050) for
10691 Changes in version 0.2.1.29 - 2011-01-15
10692 Tor 0.2.1.29 continues our recent code security audit work. The main
10693 fix resolves a remote heap overflow vulnerability that can allow remote
10694 code execution. Other fixes address a variety of assert and crash bugs,
10695 most of which we think are hard to exploit remotely.
10697 o Major bugfixes (security):
10698 - Fix a heap overflow bug where an adversary could cause heap
10699 corruption. This bug probably allows remote code execution
10700 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10702 - Prevent a denial-of-service attack by disallowing any
10703 zlib-compressed data whose compression factor is implausibly
10704 high. Fixes part of bug 2324; reported by "doorss".
10705 - Zero out a few more keys in memory before freeing them. Fixes
10706 bug 2384 and part of bug 2385. These key instances found by
10707 "cypherpunks", based on Andrew Case's report about being able
10708 to find sensitive data in Tor's memory space if you have enough
10709 permissions. Bugfix on 0.0.2pre9.
10711 o Major bugfixes (crashes):
10712 - Prevent calls to Libevent from inside Libevent log handlers.
10713 This had potential to cause a nasty set of crashes, especially
10714 if running Libevent with debug logging enabled, and running
10715 Tor with a controller watching for low-severity log messages.
10716 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10717 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10718 underflow errors there too. Fixes the other part of bug 2324.
10719 - Fix a bug where we would assert if we ever had a
10720 cached-descriptors.new file (or another file read directly into
10721 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10722 on 0.2.1.25. Found by doorss.
10723 - Fix some potential asserts and parsing issues with grossly
10724 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10727 o Minor bugfixes (other):
10728 - Fix a bug with handling misformed replies to reverse DNS lookup
10729 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10730 bug reported by doorss.
10731 - Fix compilation on mingw when a pthreads compatibility library
10732 has been installed. (We don't want to use it, so we shouldn't
10733 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10734 - Fix a bug where we would declare that we had run out of virtual
10735 addresses when the address space was only half-exhausted. Bugfix
10737 - Correctly handle the case where AutomapHostsOnResolve is set but
10738 no virtual addresses are available. Fixes bug 2328; bugfix on
10739 0.1.2.1-alpha. Bug found by doorss.
10740 - Correctly handle wrapping around to when we run out of virtual
10741 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
10742 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
10743 because we built it with a too-old version of automake. Thus that
10744 release broke ./configure --enable-openbsd-malloc, which is popular
10745 among really fast exit relays on Linux.
10748 - Update to the January 1 2011 Maxmind GeoLite Country database.
10749 - Introduce output size checks on all of our decryption functions.
10752 - Tor does not build packages correctly with Automake 1.6 and earlier;
10753 added a check to Makefile.am to make sure that we're building with
10754 Automake 1.7 or later.
10757 Changes in version 0.2.2.20-alpha - 2010-12-17
10758 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
10759 exploitable bugs. We also fix a variety of other significant bugs,
10760 change the IP address for one of our directory authorities, and update
10761 the minimum version that Tor relays must run to join the network.
10764 - Fix a remotely exploitable bug that could be used to crash instances
10765 of Tor remotely by overflowing on the heap. Remote-code execution
10766 hasn't been confirmed, but can't be ruled out. Everyone should
10767 upgrade. Bugfix on the 0.1.1 series and later.
10768 - Fix a bug that could break accounting on 64-bit systems with large
10769 time_t values, making them hibernate for impossibly long intervals.
10770 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
10771 - Fix a logic error in directory_fetches_from_authorities() that
10772 would cause all _non_-exits refusing single-hop-like circuits
10773 to fetch from authorities, when we wanted to have _exits_ fetch
10774 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
10776 - Fix a stream fairness bug that would cause newer streams on a given
10777 circuit to get preference when reading bytes from the origin or
10778 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
10779 introduced before the first Tor release, in svn revision r152.
10781 o Directory authority changes:
10782 - Change IP address and ports for gabelmoo (v3 directory authority).
10785 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
10786 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
10787 - Fix an off-by-one error in calculating some controller command
10788 argument lengths. Fortunately, this mistake is harmless since
10789 the controller code does redundant NUL termination too. Found by
10790 boboper. Bugfix on 0.1.1.1-alpha.
10791 - Do not dereference NULL if a bridge fails to build its
10792 extra-info descriptor. Found by an anonymous commenter on
10793 Trac. Bugfix on 0.2.2.19-alpha.
10796 - Update to the December 1 2010 Maxmind GeoLite Country database.
10797 - Directory authorities now reject relays running any versions of
10798 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
10799 known bugs that keep RELAY_EARLY cells from working on rendezvous
10800 circuits. Followup to fix for bug 2081.
10801 - Directory authorities now reject relays running any version of Tor
10802 older than 0.2.0.26-rc. That version is the earliest that fetches
10803 current directory information correctly. Fixes bug 2156.
10804 - Report only the top 10 ports in exit-port stats in order not to
10805 exceed the maximum extra-info descriptor length of 50 KB. Implements
10809 Changes in version 0.2.1.28 - 2010-12-17
10810 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
10811 exploitable bugs. We also took this opportunity to change the IP address
10812 for one of our directory authorities, and to update the geoip database
10816 - Fix a remotely exploitable bug that could be used to crash instances
10817 of Tor remotely by overflowing on the heap. Remote-code execution
10818 hasn't been confirmed, but can't be ruled out. Everyone should
10819 upgrade. Bugfix on the 0.1.1 series and later.
10821 o Directory authority changes:
10822 - Change IP address and ports for gabelmoo (v3 directory authority).
10825 - Update to the December 1 2010 Maxmind GeoLite Country database.
10828 Changes in version 0.2.1.27 - 2010-11-23
10829 Yet another OpenSSL security patch broke its compatibility with Tor:
10830 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
10831 also took this opportunity to fix several crash bugs, integrate a new
10832 directory authority, and update the bundled GeoIP database.
10835 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
10836 No longer set the tlsext_host_name extension on server SSL objects;
10837 but continue to set it on client SSL objects. Our goal in setting
10838 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
10839 bugfix on 0.2.1.1-alpha.
10840 - Do not log messages to the controller while shrinking buffer
10841 freelists. Doing so would sometimes make the controller connection
10842 try to allocate a buffer chunk, which would mess up the internals
10843 of the freelist and cause an assertion failure. Fixes bug 1125;
10844 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10845 - Learn our external IP address when we're a relay or bridge, even if
10846 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10847 where we introduced bridge relays that don't need to publish to
10848 be useful. Fixes bug 2050.
10849 - Do even more to reject (and not just ignore) annotations on
10850 router descriptors received anywhere but from the cache. Previously
10851 we would ignore such annotations at first, but cache them to disk
10852 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10853 - When you're using bridges and your network goes away and your
10854 bridges get marked as down, recover when you attempt a new socks
10855 connection (if the network is back), rather than waiting up to an
10856 hour to try fetching new descriptors for your bridges. Bugfix on
10857 0.2.0.3-alpha; fixes bug 1981.
10860 - Move to the November 2010 Maxmind GeoLite country db (rather
10861 than the June 2009 ip-to-country GeoIP db) for our statistics that
10862 count how many users relays are seeing from each country. Now we'll
10863 have more accurate data, especially for many African countries.
10865 o New directory authorities:
10866 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
10870 - Fix an assertion failure that could occur in directory caches or
10871 bridge users when using a very short voting interval on a testing
10872 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
10874 - Enforce multiplicity rules when parsing annotations. Bugfix on
10875 0.2.0.8-alpha. Found by piebeer.
10876 - Allow handshaking OR connections to take a full KeepalivePeriod
10877 seconds to handshake. Previously, we would close them after
10878 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
10879 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
10881 - When building with --enable-gcc-warnings on OpenBSD, disable
10882 warnings in system headers. This makes --enable-gcc-warnings
10883 pass on OpenBSD 4.8.
10886 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
10887 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
10888 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
10889 Servers can start sending this code when enough clients recognize
10890 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
10891 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
10892 Patch from mingw-san.
10895 - Remove the old debian/ directory from the main Tor distribution.
10896 The official Tor-for-debian git repository lives at the URL
10897 https://git.torproject.org/debian/tor.git
10898 - Stop shipping the old doc/website/ directory in the tarball. We
10899 changed the website format in late 2010, and what we shipped in
10900 0.2.1.26 really wasn't that useful anyway.
10903 Changes in version 0.2.2.19-alpha - 2010-11-22
10904 Yet another OpenSSL security patch broke its compatibility with Tor:
10905 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
10908 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
10909 No longer set the tlsext_host_name extension on server SSL objects;
10910 but continue to set it on client SSL objects. Our goal in setting
10911 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
10912 bugfix on 0.2.1.1-alpha.
10915 - Try harder not to exceed the maximum length of 50 KB when writing
10916 statistics to extra-info descriptors. This bug was triggered by very
10917 fast relays reporting exit-port, entry, and dirreq statistics.
10918 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
10919 - Publish a router descriptor even if generating an extra-info
10920 descriptor fails. Previously we would not publish a router
10921 descriptor without an extra-info descriptor; this can cause fast
10922 exit relays collecting exit-port statistics to drop from the
10923 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
10926 Changes in version 0.2.2.18-alpha - 2010-11-16
10927 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
10928 us lately, makes unpublished bridge relays able to detect their IP
10929 address, and fixes a wide variety of other bugs to get us much closer
10930 to a stable release.
10933 - Do even more to reject (and not just ignore) annotations on
10934 router descriptors received anywhere but from the cache. Previously
10935 we would ignore such annotations at first, but cache them to disk
10936 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10937 - Do not log messages to the controller while shrinking buffer
10938 freelists. Doing so would sometimes make the controller connection
10939 try to allocate a buffer chunk, which would mess up the internals
10940 of the freelist and cause an assertion failure. Fixes bug 1125;
10941 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10942 - Learn our external IP address when we're a relay or bridge, even if
10943 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10944 where we introduced bridge relays that don't need to publish to
10945 be useful. Fixes bug 2050.
10946 - Maintain separate TLS contexts and certificates for incoming and
10947 outgoing connections in bridge relays. Previously we would use the
10948 same TLS contexts and certs for incoming and outgoing connections.
10949 Bugfix on 0.2.0.3-alpha; addresses bug 988.
10950 - Maintain separate identity keys for incoming and outgoing TLS
10951 contexts in bridge relays. Previously we would use the same
10952 identity keys for incoming and outgoing TLS contexts. Bugfix on
10953 0.2.0.3-alpha; addresses the other half of bug 988.
10954 - Avoid an assertion failure when we as an authority receive a
10955 duplicate upload of a router descriptor that we already have,
10956 but which we previously considered an obsolete descriptor.
10957 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
10958 - Avoid a crash bug triggered by looking at a dangling pointer while
10959 setting the network status consensus. Found by Robert Ransom.
10960 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
10961 - Fix a logic error where servers that _didn't_ act as exits would
10962 try to keep their server lists more aggressively up to date than
10963 exits, when it was supposed to be the other way around. Bugfix
10966 o Minor bugfixes (on Tor 0.2.1.x and earlier):
10967 - When we're trying to guess whether we know our IP address as
10968 a relay, we would log various ways that we failed to guess
10969 our address, but never log that we ended up guessing it
10970 successfully. Now add a log line to help confused and anxious
10971 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
10972 - Bring the logic that gathers routerinfos and assesses the
10973 acceptability of circuits into line. This prevents a Tor OP from
10974 getting locked in a cycle of choosing its local OR as an exit for a
10975 path (due to a .exit request) and then rejecting the circuit because
10976 its OR is not listed yet. It also prevents Tor clients from using an
10977 OR running in the same instance as an exit (due to a .exit request)
10978 if the OR does not meet the same requirements expected of an OR
10979 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10980 - Correctly describe errors that occur when generating a TLS object.
10981 Previously we would attribute them to a failure while generating a
10982 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
10984 - Enforce multiplicity rules when parsing annotations. Bugfix on
10985 0.2.0.8-alpha. Found by piebeer.
10986 - Fix warnings that newer versions of autoconf produced during
10987 ./autogen.sh. These warnings appear to be harmless in our case,
10988 but they were extremely verbose. Fixes bug 2020.
10990 o Minor bugfixes (on Tor 0.2.2.x):
10991 - Enable protection of small arrays whenever we build with gcc
10992 hardening features, not only when also building with warnings
10993 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
10996 - Make hidden services work better in private Tor networks by not
10997 requiring any uptime to join the hidden service descriptor
10998 DHT. Implements ticket 2088.
10999 - Rate-limit the "your application is giving Tor only an IP address"
11000 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
11001 - When AllowSingleHopExits is set, print a warning to explain to the
11002 relay operator why most clients are avoiding her relay.
11003 - Update to the November 1 2010 Maxmind GeoLite Country database.
11005 o Code simplifications and refactoring:
11006 - When we fixed bug 1038 we had to put in a restriction not to send
11007 RELAY_EARLY cells on rend circuits. This was necessary as long
11008 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
11009 active. Now remove this obsolete check. Resolves bug 2081.
11010 - Some options used different conventions for uppercasing of acronyms
11011 when comparing manpage and source. Fix those in favor of the
11012 manpage, as it makes sense to capitalize acronyms.
11013 - Remove the torrc.complete file. It hasn't been kept up to date
11014 and users will have better luck checking out the manpage.
11015 - Remove the obsolete "NoPublish" option; it has been flagged
11016 as obsolete and has produced a warning since 0.1.1.18-rc.
11017 - Remove everything related to building the expert bundle for OS X.
11018 It has confused many users, doesn't work right on OS X 10.6,
11019 and is hard to get rid of once installed. Resolves bug 1274.
11022 Changes in version 0.2.2.17-alpha - 2010-09-30
11023 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
11024 to use one-hop circuits (which can put the exit relays at higher risk,
11025 plus unbalance the network); fixes a big bug in bandwidth accounting
11026 for relays that want to limit their monthly bandwidth use; fixes a
11027 big pile of bugs in how clients tolerate temporary network failure;
11028 and makes our adaptive circuit build timeout feature (which improves
11029 client performance if your network is fast while not breaking things
11030 if your network is slow) better handle bad networks.
11033 - Exit relays now try harder to block exit attempts from unknown
11034 relays, to make it harder for people to use them as one-hop proxies
11035 a la tortunnel. Controlled by the refuseunknownexits consensus
11036 parameter (currently enabled), or you can override it on your
11037 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
11039 o Major bugfixes (0.2.1.x and earlier):
11040 - Fix a bug in bandwidth accounting that could make us use twice
11041 the intended bandwidth when our interval start changes due to
11042 daylight saving time. Now we tolerate skew in stored vs computed
11043 interval starts: if the start of the period changes by no more than
11044 50% of the period's duration, we remember bytes that we transferred
11045 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
11046 - Always search the Windows system directory for system DLLs, and
11047 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
11048 - When you're using bridges and your network goes away and your
11049 bridges get marked as down, recover when you attempt a new socks
11050 connection (if the network is back), rather than waiting up to an
11051 hour to try fetching new descriptors for your bridges. Bugfix on
11052 0.2.0.3-alpha; fixes bug 1981.
11054 o Major bugfixes (on 0.2.2.x):
11055 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
11057 - Fix a segfault that could happen when operating a bridge relay with
11058 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
11059 - The consensus bandwidth-weights (used by clients to choose fast
11060 relays) entered an unexpected edge case in September where
11061 Exits were much scarcer than Guards, resulting in bad weight
11062 recommendations. Now we compute them using new constraints that
11063 should succeed in all cases. Also alter directory authorities to
11064 not include the bandwidth-weights line if they fail to produce
11065 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
11066 - When weighting bridges during path selection, we used to trust
11067 the bandwidths they provided in their descriptor, only capping them
11068 at 10MB/s. This turned out to be problematic for two reasons:
11069 Bridges could claim to handle a lot more traffic then they
11070 actually would, thus making more clients pick them and have a
11071 pretty effective DoS attack. The other issue is that new bridges
11072 that might not have a good estimate for their bw capacity yet
11073 would not get used at all unless no other bridges are available
11074 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
11076 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
11077 - Ignore cannibalized circuits when recording circuit build times.
11078 This should provide for a minor performance improvement for hidden
11079 service users using 0.2.2.14-alpha, and should remove two spurious
11080 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
11081 - Simplify the logic that causes us to decide if the network is
11082 unavailable for purposes of recording circuit build times. If we
11083 receive no cells whatsoever for the entire duration of a circuit's
11084 full measured lifetime, the network is probably down. Also ignore
11085 one-hop directory fetching circuit timeouts when calculating our
11086 circuit build times. These changes should hopefully reduce the
11087 cases where we see ridiculous circuit build timeouts for people
11088 with spotty wireless connections. Fixes part of bug 1772; bugfix
11090 - Prevent the circuit build timeout from becoming larger than
11091 the maximum build time we have ever seen. Also, prevent the time
11092 period for measurement circuits from becoming larger than twice that
11093 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
11096 - When we run out of directory information such that we can't build
11097 circuits, but then get enough that we can build circuits, log when
11098 we actually construct a circuit, so the user has a better chance of
11099 knowing what's going on. Fixes bug 1362.
11100 - Be more generous with how much bandwidth we'd use up (with
11101 accounting enabled) before entering "soft hibernation". Previously,
11102 we'd refuse new connections and circuits once we'd used up 95% of
11103 our allotment. Now, we use up 95% of our allotment, AND make sure
11104 that we have no more than 500MB (or 3 hours of expected traffic,
11105 whichever is lower) remaining before we enter soft hibernation.
11106 - If we've configured EntryNodes and our network goes away and/or all
11107 our entrynodes get marked down, optimistically retry them all when
11108 a new socks application request appears. Fixes bug 1882.
11109 - Add some more defensive programming for architectures that can't
11110 handle unaligned integer accesses. We don't know of any actual bugs
11111 right now, but that's the best time to fix them. Fixes bug 1943.
11112 - Support line continuations in the torrc config file. If a line
11113 ends with a single backslash character, the newline is ignored, and
11114 the configuration value is treated as continuing on the next line.
11117 o Minor bugfixes (on 0.2.1.x and earlier):
11118 - For bandwidth accounting, calculate our expected bandwidth rate
11119 based on the time during which we were active and not in
11120 soft-hibernation during the last interval. Previously, we were
11121 also considering the time spent in soft-hibernation. If this
11122 was a long time, we would wind up underestimating our bandwidth
11123 by a lot, and skewing our wakeup time towards the start of the
11124 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
11126 o Minor bugfixes (on 0.2.2.x):
11127 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
11128 which were disabled by the circuit build timeout changes in
11129 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
11130 - Make sure we don't warn about missing bandwidth weights when
11131 choosing bridges or other relays not in the consensus. Bugfix on
11132 0.2.2.10-alpha; fixes bug 1805.
11133 - In our logs, do not double-report signatures from unrecognized
11134 authorities both as "from unknown authority" and "not
11135 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
11138 Changes in version 0.2.2.16-alpha - 2010-09-17
11139 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
11140 evident at exit relays), and also continues to resolve all the little
11141 bugs that have been filling up trac lately.
11143 o Major bugfixes (stream-level fairness):
11144 - When receiving a circuit-level SENDME for a blocked circuit, try
11145 to package cells fairly from all the streams that had previously
11146 been blocked on that circuit. Previously, we had started with the
11147 oldest stream, and allowed each stream to potentially exhaust
11148 the circuit's package window. This gave older streams on any
11149 given circuit priority over newer ones. Fixes bug 1937. Detected
11150 originally by Camilo Viecco. This bug was introduced before the
11151 first Tor release, in svn commit r152: it is the new winner of
11152 the longest-lived bug prize.
11153 - When the exit relay got a circuit-level sendme cell, it started
11154 reading on the exit streams, even if had 500 cells queued in the
11155 circuit queue already, so the circuit queue just grew and grew in
11156 some cases. We fix this by not re-enabling reading on receipt of a
11157 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
11158 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
11160 - Newly created streams were allowed to read cells onto circuits,
11161 even if the circuit's cell queue was blocked and waiting to drain.
11162 This created potential unfairness, as older streams would be
11163 blocked, but newer streams would gladly fill the queue completely.
11164 We add code to detect this situation and prevent any stream from
11165 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
11169 - Update to the September 1 2010 Maxmind GeoLite Country database.
11170 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
11171 not. This would lead to a cookie that is still not group readable.
11172 Closes bug 1843. Suggested by katmagic.
11173 - When logging a rate-limited warning, we now mention how many messages
11174 got suppressed since the last warning.
11175 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
11176 do individual connection-level rate limiting of clients. The torrc
11177 config options with the same names trump the consensus params, if
11178 both are present. Replaces the old "bwconnrate" and "bwconnburst"
11179 consensus params which were broken from 0.2.2.7-alpha through
11180 0.2.2.14-alpha. Closes bug 1947.
11181 - When a router changes IP address or port, authorities now launch
11182 a new reachability test for it. Implements ticket 1899.
11183 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
11184 2 no signature, 4 required" messages about consensus signatures
11185 easier to read, and make sure they get logged at the same severity
11186 as the messages explaining which keys are which. Fixes bug 1290.
11187 - Don't warn when we have a consensus that we can't verify because
11188 of missing certificates, unless those certificates are ones
11189 that we have been trying and failing to download. Fixes bug 1145.
11190 - If you configure your bridge with a known identity fingerprint,
11191 and the bridge authority is unreachable (as it is in at least
11192 one country now), fall back to directly requesting the descriptor
11193 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
11195 - When building with --enable-gcc-warnings on OpenBSD, disable
11196 warnings in system headers. This makes --enable-gcc-warnings
11197 pass on OpenBSD 4.8.
11199 o Minor bugfixes (on 0.2.1.x and earlier):
11200 - Authorities will now attempt to download consensuses if their
11201 own efforts to make a live consensus have failed. This change
11202 means authorities that restart will fetch a valid consensus, and
11203 it means authorities that didn't agree with the current consensus
11204 will still fetch and serve it if it has enough signatures. Bugfix
11205 on 0.2.0.9-alpha; fixes bug 1300.
11206 - Ensure DNS requests launched by "RESOLVE" commands from the
11207 controller respect the __LeaveStreamsUnattached setconf options. The
11208 same goes for requests launched via DNSPort or transparent
11209 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
11210 - Allow handshaking OR connections to take a full KeepalivePeriod
11211 seconds to handshake. Previously, we would close them after
11212 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
11213 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
11215 - Rate-limit "Failed to hand off onionskin" warnings.
11216 - Never relay a cell for a circuit we have already destroyed.
11217 Between marking a circuit as closeable and finally closing it,
11218 it may have been possible for a few queued cells to get relayed,
11219 even though they would have been immediately dropped by the next
11220 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
11221 - Never queue a cell for a circuit that's already been marked
11223 - Never vote for a server as "Running" if we have a descriptor for
11224 it claiming to be hibernating, and that descriptor was published
11225 more recently than our last contact with the server. Bugfix on
11226 0.2.0.3-alpha; fixes bug 911.
11227 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
11230 o Minor bugfixes (on 0.2.2.x):
11231 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
11232 down if a directory fetch fails and you've configured either
11233 bridges or EntryNodes. The intent was to mark the relay as down
11234 _unless_ you're using bridges or EntryNodes, since if you are
11235 then you could quickly run out of entry points.
11236 - Fix the Windows directory-listing code. A bug introduced in
11237 0.2.2.14-alpha could make Windows directory servers forget to load
11238 some of their cached v2 networkstatus files.
11239 - Really allow clients to use relays as bridges. Fixes bug 1776;
11240 bugfix on 0.2.2.15-alpha.
11241 - Demote a warn to info that happens when the CellStatistics option
11242 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
11243 Reported by Moritz Bartl.
11244 - On Windows, build correctly either with or without Unicode support.
11245 This is necessary so that Tor can support fringe platforms like
11246 Windows 98 (which has no Unicode), or Windows CE (which has no
11247 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
11250 - Add a unit test for cross-platform directory-listing code.
11253 Changes in version 0.2.2.15-alpha - 2010-08-18
11254 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
11255 fixes a variety of other bugs that were preventing performance
11256 experiments from moving forward, fixes several bothersome memory leaks,
11257 and generally closes a lot of smaller bugs that have been filling up
11261 - Stop assigning the HSDir flag to relays that disable their
11262 DirPort (and thus will refuse to answer directory requests). This
11263 fix should dramatically improve the reachability of hidden services:
11264 hidden services and hidden service clients pick six HSDir relays
11265 to store and retrieve the hidden service descriptor, and currently
11266 about half of the HSDir relays will refuse to work. Bugfix on
11267 0.2.0.10-alpha; fixes part of bug 1693.
11268 - The PerConnBWRate and Burst config options, along with the
11269 bwconnrate and bwconnburst consensus params, initialized each conn's
11270 token bucket values only when the connection is established. Now we
11271 update them if the config options change, and update them every time
11272 we get a new consensus. Otherwise we can encounter an ugly edge
11273 case where we initialize an OR conn to client-level bandwidth,
11274 but then later the relay joins the consensus and we leave it
11275 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
11276 - Fix a regression that caused Tor to rebind its ports if it receives
11277 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
11280 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
11281 should give us approximately 40-50% more Guard-flagged nodes,
11282 improving the anonymity the Tor network can provide and also
11283 decreasing the dropoff in throughput that relays experience when
11284 they first get the Guard flag.
11285 - Allow enabling or disabling the *Statistics config options while
11289 - Update to the August 1 2010 Maxmind GeoLite Country database.
11290 - Have the controller interface give a more useful message than
11291 "Internal Error" in response to failed GETINFO requests.
11292 - Warn when the same option is provided more than once in a torrc
11293 file, on the command line, or in a single SETCONF statement, and
11294 the option is one that only accepts a single line. Closes bug 1384.
11295 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
11296 Patch from mingw-san.
11297 - Add support for the country code "{??}" in torrc options like
11298 ExcludeNodes, to indicate all routers of unknown country. Closes
11300 - Relays report the number of bytes spent on answering directory
11301 requests in extra-info descriptors similar to {read,write}-history.
11302 Implements enhancement 1790.
11304 o Minor bugfixes (on 0.2.1.x and earlier):
11305 - Complain if PublishServerDescriptor is given multiple arguments that
11306 include 0 or 1. This configuration will be rejected in the future.
11307 Bugfix on 0.2.0.1-alpha; closes bug 1107.
11308 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
11309 Bugfix on 0.2.0.13-alpha; closes bug 928.
11310 - Change "Application request when we're believed to be offline."
11311 notice to "Application request when we haven't used client
11312 functionality lately.", to clarify that it's not an error. Bugfix
11313 on 0.0.9.3; fixes bug 1222.
11314 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
11315 would return "551 Internal error" rather than "552 Unrecognized key
11316 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
11317 - Users can't configure a regular relay to be their bridge. It didn't
11318 work because when Tor fetched the bridge descriptor, it found
11319 that it already had it, and didn't realize that the purpose of the
11320 descriptor had changed. Now we replace routers with a purpose other
11321 than bridge with bridge descriptors when fetching them. Bugfix on
11322 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
11323 refetch the descriptor with router purpose 'general', disabling
11325 - Fix a rare bug in rend_fn unit tests: we would fail a test when
11326 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
11327 on 0.2.0.10-alpha; fixes bug 1808.
11328 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
11329 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
11330 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
11331 Servers can start sending this code when enough clients recognize
11332 it. Also update the spec to reflect this new reason. Bugfix on
11333 0.1.0.1-rc; fixes part of bug 1793.
11334 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
11335 when we switch from being a public relay to a bridge. Otherwise
11336 there will still be clients that see the relay in their consensus,
11337 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
11339 - Instead of giving an assertion failure on an internal mismatch
11340 on estimated freelist size, just log a BUG warning and try later.
11341 Mitigates but does not fix bug 1125.
11342 - Fix an assertion failure that could occur in caches or bridge users
11343 when using a very short voting interval on a testing network.
11344 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
11346 o Minor bugfixes (on 0.2.2.x):
11347 - Alter directory authorities to always consider Exit-flagged nodes
11348 as potential Guard nodes in their votes. The actual decision to
11349 use Exits as Guards is done in the consensus bandwidth weights.
11350 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
11351 - When the controller is reporting the purpose of circuits that
11352 didn't finish building before the circuit build timeout, it was
11353 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
11354 - Our libevent version parsing code couldn't handle versions like
11355 1.4.14b-stable and incorrectly warned the user about using an
11356 old and broken version of libevent. Treat 1.4.14b-stable like
11357 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
11359 - Don't use substitution references like $(VAR:MOD) when
11360 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
11361 '$(:x)' to 'x' rather than the empty string. This bites us in
11362 doc/ when configured with --disable-asciidoc. Bugfix on
11363 0.2.2.9-alpha; fixes bug 1773.
11364 - Remove a spurious hidden service server-side log notice about
11365 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
11367 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
11369 - Correctly report written bytes on linked connections. Found while
11370 implementing 1790. Bugfix on 0.2.2.4-alpha.
11371 - Fix three memory leaks: one in circuit_build_times_parse_state(),
11372 one in dirvote_add_signatures_to_pending_consensus(), and one every
11373 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
11374 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
11376 o Code simplifications and refactoring:
11377 - Take a first step towards making or.h smaller by splitting out
11378 function definitions for all source files in src/or/. Leave
11379 structures and defines in or.h for now.
11380 - Remove a bunch of unused function declarations as well as a block of
11381 #if 0'd code from the unit tests. Closes bug 1824.
11382 - New unit tests for exit-port history statistics; refactored exit
11383 statistics code to be more easily tested.
11384 - Remove the old debian/ directory from the main Tor distribution.
11385 The official Tor-for-debian git repository lives at the URL
11386 https://git.torproject.org/debian/tor.git
11389 Changes in version 0.2.2.14-alpha - 2010-07-12
11390 Tor 0.2.2.14-alpha greatly improves client-side handling of
11391 circuit build timeouts, which are used to estimate speed and improve
11392 performance. We also move to a much better GeoIP database, port Tor to
11393 Windows CE, introduce new compile flags that improve code security,
11394 add an eighth v3 directory authority, and address a lot of more
11398 - Tor directory authorities no longer crash when started with a
11399 cached-microdesc-consensus file in their data directory. Bugfix
11400 on 0.2.2.6-alpha; fixes bug 1532.
11401 - Treat an unset $HOME like an empty $HOME rather than triggering an
11402 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
11403 - Ignore negative and large circuit build timeout values that can
11404 happen during a suspend or hibernate. These values caused various
11405 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
11406 - Alter calculation of Pareto distribution parameter 'Xm' for
11407 Circuit Build Timeout learning to use the weighted average of the
11408 top N=3 modes (because we have three entry guards). Considering
11409 multiple modes should improve the timeout calculation in some cases,
11410 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
11412 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
11413 right censored distribution model. This approach improves over the
11414 synthetic timeout generation approach that was producing insanely
11415 high timeout values. Now we calculate build timeouts using truncated
11416 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
11417 - Do not close circuits that are under construction when they reach
11418 the circuit build timeout. Instead, leave them building (but do not
11419 use them) for up until the time corresponding to the 95th percentile
11420 on the Pareto CDF or 60 seconds, whichever is greater. This is done
11421 to provide better data for the new Pareto model. This percentile
11422 can be controlled by the consensus.
11425 - Move to the June 2010 Maxmind GeoLite country db (rather than the
11426 June 2009 ip-to-country GeoIP db) for our statistics that count
11427 how many users relays are seeing from each country. Now we have
11428 more accurate data for many African countries.
11429 - Port Tor to build and run correctly on Windows CE systems, using
11430 the wcecompat library. Contributed by Valerio Lupi.
11431 - New "--enable-gcc-hardening" ./configure flag (off by default)
11432 to turn on gcc compile time hardening options. It ensures
11433 that signed ints have defined behavior (-fwrapv), enables
11434 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
11435 with canaries (-fstack-protector-all), turns on ASLR protection if
11436 supported by the kernel (-fPIE, -pie), and adds additional security
11437 related warnings. Verified to work on Mac OS X and Debian Lenny.
11438 - New "--enable-linker-hardening" ./configure flag (off by default)
11439 to turn on ELF specific hardening features (relro, now). This does
11440 not work with Mac OS X or any other non-ELF binary format.
11442 o New directory authorities:
11443 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
11447 - New config option "WarnUnsafeSocks 0" disables the warning that
11448 occurs whenever Tor receives a socks handshake using a version of
11449 the socks protocol that can only provide an IP address (rather
11450 than a hostname). Setups that do DNS locally over Tor are fine,
11451 and we shouldn't spam the logs in that case.
11452 - Convert the HACKING file to asciidoc, and add a few new sections
11453 to it, explaining how we use Git, how we make changelogs, and
11454 what should go in a patch.
11455 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
11456 event, to give information on the current rate of circuit timeouts
11457 over our stored history.
11458 - Add ability to disable circuit build time learning via consensus
11459 parameter and via a LearnCircuitBuildTimeout config option. Also
11460 automatically disable circuit build time calculation if we are
11461 either a AuthoritativeDirectory, or if we fail to write our state
11462 file. Fixes bug 1296.
11463 - More gracefully handle corrupt state files, removing asserts
11464 in favor of saving a backup and resetting state.
11465 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
11469 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
11471 - When a2x fails, mention that the user could disable manpages instead
11472 of trying to fix their asciidoc installation.
11473 - Where available, use Libevent 2.0's periodic timers so that our
11474 once-per-second cleanup code gets called even more closely to
11475 once per second than it would otherwise. Fixes bug 943.
11476 - If you run a bridge that listens on multiple IP addresses, and
11477 some user configures a bridge address that uses a different IP
11478 address than your bridge writes in its router descriptor, and the
11479 user doesn't specify an identity key, their Tor would discard the
11480 descriptor because "it isn't one of our configured bridges", and
11481 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
11482 Bugfix on 0.2.0.3-alpha.
11483 - If OpenSSL fails to make a duplicate of a private or public key, log
11484 an error message and try to exit cleanly. May help with debugging
11485 if bug 1209 ever remanifests.
11486 - Save a couple bytes in memory allocation every time we escape
11487 certain characters in a string. Patch from Florian Zumbiehl.
11488 - Make it explicit that we don't cannibalize one-hop circuits. This
11489 happens in the wild, but doesn't turn out to be a problem because
11490 we fortunately don't use those circuits. Many thanks to outofwords
11491 for the initial analysis and to swissknife who confirmed that
11492 two-hop circuits are actually created.
11493 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
11494 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
11495 - Eliminate a case where a circuit build time warning was displayed
11496 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
11499 Changes in version 0.2.1.26 - 2010-05-02
11500 Tor 0.2.1.26 addresses the recent connection and memory overload
11501 problems we've been seeing on relays, especially relays with their
11502 DirPort open. If your relay has been crashing, or you turned it off
11503 because it used too many resources, give this release a try.
11505 This release also fixes yet another instance of broken OpenSSL libraries
11506 that was causing some relays to drop out of the consensus.
11509 - Teach relays to defend themselves from connection overload. Relays
11510 now close idle circuits early if it looks like they were intended
11511 for directory fetches. Relays are also more aggressive about closing
11512 TLS connections that have no circuits on them. Such circuits are
11513 unlikely to be re-used, and tens of thousands of them were piling
11514 up at the fast relays, causing the relays to run out of sockets
11515 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11516 their directory fetches over TLS).
11517 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11518 that claim to be earlier than 0.9.8m, but which have in reality
11519 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11520 behavior. Possible fix for some cases of bug 1346.
11521 - Directory mirrors were fetching relay descriptors only from v2
11522 directory authorities, rather than v3 authorities like they should.
11523 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11524 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11527 - Finally get rid of the deprecated and now harmful notion of "clique
11528 mode", where directory authorities maintain TLS connections to
11532 - In the util/threads test, no longer free the test_mutex before all
11533 worker threads have finished. Bugfix on 0.2.1.6-alpha.
11534 - The master thread could starve the worker threads quite badly on
11535 certain systems, causing them to run only partially in the allowed
11536 window. This resulted in test failures. Now the master thread sleeps
11537 occasionally for a few microseconds while the two worker-threads
11538 compete for the mutex. Bugfix on 0.2.0.1-alpha.
11541 Changes in version 0.2.2.13-alpha - 2010-04-24
11542 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
11543 problems we've been seeing on relays, especially relays with their
11544 DirPort open. If your relay has been crashing, or you turned it off
11545 because it used too many resources, give this release a try.
11548 - Teach relays to defend themselves from connection overload. Relays
11549 now close idle circuits early if it looks like they were intended
11550 for directory fetches. Relays are also more aggressive about closing
11551 TLS connections that have no circuits on them. Such circuits are
11552 unlikely to be re-used, and tens of thousands of them were piling
11553 up at the fast relays, causing the relays to run out of sockets
11554 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11555 their directory fetches over TLS).
11558 - Finally get rid of the deprecated and now harmful notion of "clique
11559 mode", where directory authorities maintain TLS connections to
11561 - Directory authorities now do an immediate reachability check as soon
11562 as they hear about a new relay. This change should slightly reduce
11563 the time between setting up a relay and getting listed as running
11564 in the consensus. It should also improve the time between setting
11565 up a bridge and seeing use by bridge users.
11566 - Directory authorities no longer launch a TLS connection to every
11567 relay as they startup. Now that we have 2k+ descriptors cached,
11568 the resulting network hiccup is becoming a burden. Besides,
11569 authorities already avoid voting about Running for the first half
11570 hour of their uptime.
11573 Changes in version 0.2.2.12-alpha - 2010-04-20
11574 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
11575 handle and vote on descriptors. It was causing relays to drop out of
11579 - Many relays have been falling out of the consensus lately because
11580 not enough authorities know about their descriptor for them to get
11581 a majority of votes. When we deprecated the v2 directory protocol,
11582 we got rid of the only way that v3 authorities can hear from each
11583 other about other descriptors. Now authorities examine every v3
11584 vote for new descriptors, and fetch them from that authority. Bugfix
11586 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
11587 and a warning in or.h related to bandwidth_weight_rule_t that
11588 prevented clean compile on OS X. Fixes bug 1363; bugfix on
11590 - Fix a segfault on relays when DirReqStatistics is enabled
11591 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
11595 - Demote a confusing TLS warning that relay operators might get when
11596 someone tries to talk to their OrPort. It is neither the operator's
11597 fault nor can they do anything about it. Fixes bug 1364; bugfix
11601 Changes in version 0.2.2.11-alpha - 2010-04-15
11602 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
11603 libraries that was causing some relays to drop out of the consensus.
11606 - Directory mirrors were fetching relay descriptors only from v2
11607 directory authorities, rather than v3 authorities like they should.
11608 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11609 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11610 - Fix a parsing error that made every possible value of
11611 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
11612 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
11613 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
11614 about the option without breaking older ones.
11615 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11616 that claim to be earlier than 0.9.8m, but which have in reality
11617 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11618 behavior. Possible fix for some cases of bug 1346.
11621 - Experiment with a more aggressive approach to preventing clients
11622 from making one-hop exit streams. Exit relays who want to try it
11623 out can set "RefuseUnknownExits 1" in their torrc, and then look
11624 for "Attempt by %s to open a stream" log messages. Let us know
11626 - Add support for statically linking zlib by specifying
11627 --enable-static-zlib, to go with our support for statically linking
11628 openssl and libevent. Resolves bug 1358.
11631 - Fix a segfault that happens whenever a Tor client that is using
11632 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
11634 - When we cleaned up the contrib/tor-exit-notice.html file, we left
11635 out the first line. Fixes bug 1295.
11636 - When building the manpage from a tarball, we required asciidoc, but
11637 the asciidoc -> roff/html conversion was already done for the
11638 tarball. Make 'make' complain only when we need asciidoc (either
11639 because we're compiling directly from git, or because we altered
11640 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
11641 - When none of the directory authorities vote on any params, Tor
11642 segfaulted when trying to make the consensus from the votes. We
11643 didn't trigger the bug in practice, because authorities do include
11644 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
11647 - In the util/threads test, no longer free the test_mutex before all
11648 worker threads have finished. Bugfix on 0.2.1.6-alpha.
11649 - The master thread could starve the worker threads quite badly on
11650 certain systems, causing them to run only partially in the allowed
11651 window. This resulted in test failures. Now the master thread sleeps
11652 occasionally for a few microseconds while the two worker-threads
11653 compete for the mutex. Bugfix on 0.2.0.1-alpha.
11656 Changes in version 0.2.2.10-alpha - 2010-03-07
11657 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
11658 could prevent relays from guessing their IP address correctly. It also
11659 starts the groundwork for another client-side performance boost, since
11660 currently we're not making efficient use of relays that have both the
11661 Guard flag and the Exit flag.
11664 - Fix a regression from our patch for bug 1244 that caused relays
11665 to guess their IP address incorrectly if they didn't set Address
11666 in their torrc and/or their address fails to resolve. Bugfix on
11667 0.2.2.9-alpha; fixes bug 1269.
11669 o Major features (performance):
11670 - Directory authorities now compute consensus weightings that instruct
11671 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
11672 and no flag. Clients that use these weightings will distribute
11673 network load more evenly across these different relay types. The
11674 weightings are in the consensus so we can change them globally in
11675 the future. Extra thanks to "outofwords" for finding some nasty
11676 security bugs in the first implementation of this feature.
11678 o Minor features (performance):
11679 - Always perform router selections using weighted relay bandwidth,
11680 even if we don't need a high capacity circuit at the time. Non-fast
11681 circuits now only differ from fast ones in that they can use relays
11682 not marked with the Fast flag. This "feature" could turn out to
11683 be a horrible bug; we should investigate more before it goes into
11687 - Allow disabling building of the manpages. Skipping the manpage
11688 speeds up the build considerably.
11690 o Minor bugfixes (on 0.2.2.x):
11691 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
11692 Bugfix on 0.2.2.9-alpha.
11693 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
11694 config option. Bugfix on 0.2.2.7-alpha.
11695 - Ship the asciidoc-helper file in the tarball, so that people can
11696 build from source if they want to, and touching the .1.txt files
11697 doesn't break the build. Bugfix on 0.2.2.9-alpha.
11699 o Minor bugfixes (on 0.2.1.x or earlier):
11700 - Fix a dereference-then-NULL-check sequence when publishing
11701 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
11703 - Fix another dereference-then-NULL-check sequence. Bugfix on
11704 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
11705 - Make sure we treat potentially not NUL-terminated strings correctly.
11706 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
11708 o Code simplifications and refactoring:
11709 - Fix some urls in the exit notice file and make it XHTML1.1 strict
11710 compliant. Based on a patch from Christian Kujau.
11711 - Don't use sed in asciidoc-helper anymore.
11712 - Make the build process fail if asciidoc cannot be found and
11713 building with asciidoc isn't disabled.
11716 Changes in version 0.2.2.9-alpha - 2010-02-22
11717 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
11718 location of a directory authority, and cleans up a bunch of small bugs.
11720 o Directory authority changes:
11721 - Change IP address for dannenberg (v3 directory authority), and
11722 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
11723 service directory authority) from the list.
11726 - Make Tor work again on the latest OS X: when deciding whether to
11727 use strange flags to turn TLS renegotiation on, detect the OpenSSL
11728 version at run-time, not compile time. We need to do this because
11729 Apple doesn't update its dev-tools headers when it updates its
11730 libraries in a security patch.
11731 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
11732 that could happen on 32-bit platforms with 64-bit time_t. Also fix
11733 a memory leak when requesting a hidden service descriptor we've
11734 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
11736 - Authorities could be tricked into giving out the Exit flag to relays
11737 that didn't allow exiting to any ports. This bug could screw
11738 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
11739 1238. Bug discovered by Martin Kowalczyk.
11740 - When freeing a session key, zero it out completely. We only zeroed
11741 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
11742 patched by ekir. Fixes bug 1254.
11745 - Fix static compilation by listing the openssl libraries in the right
11746 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
11747 - Resume handling .exit hostnames in a special way: originally we
11748 stripped the .exit part and used the requested exit relay. In
11749 0.2.2.1-alpha we stopped treating them in any special way, meaning
11750 if you use a .exit address then Tor will pass it on to the exit
11751 relay. Now we reject the .exit stream outright, since that behavior
11752 might be more expected by the user. Found and diagnosed by Scott
11753 Bennett and Downie on or-talk.
11754 - Don't spam the controller with events when we have no file
11755 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
11756 for log messages was already solved from bug 748.)
11757 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
11759 - Make the DNSPort option work with libevent 2.x. Don't alter the
11760 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
11761 - Emit a GUARD DROPPED controller event for a case we missed.
11762 - Make more fields in the controller protocol case-insensitive, since
11763 control-spec.txt said they were.
11764 - Refactor resolve_my_address() to not use gethostbyname() anymore.
11765 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
11766 - Fix a spec conformance issue: the network-status-version token
11767 must be the first token in a v3 consensus or vote. Discovered by
11768 parakeep. Bugfix on 0.2.0.3-alpha.
11770 o Code simplifications and refactoring:
11771 - Generate our manpage and HTML documentation using Asciidoc. This
11772 change should make it easier to maintain the documentation, and
11773 produce nicer HTML.
11774 - Remove the --enable-iphone option. According to reports from Marco
11775 Bonetti, Tor builds fine without any special tweaking on recent
11776 iPhone SDK versions.
11777 - Removed some unnecessary files from the source distribution. The
11778 AUTHORS file has now been merged into the people page on the
11779 website. The roadmaps and design doc can now be found in the
11780 projects directory in svn.
11781 - Enabled various circuit build timeout constants to be controlled
11782 by consensus parameters. Also set better defaults for these
11783 parameters based on experimentation on broadband and simulated
11784 high latency links.
11787 - The 'EXTENDCIRCUIT' control port command can now be used with
11788 a circ id of 0 and no path. This feature will cause Tor to build
11789 a new 'fast' general purpose circuit using its own path selection
11791 - Added a BUILDTIMEOUT_SET controller event to describe changes
11792 to the circuit build timeout.
11793 - Future-proof the controller protocol a bit by ignoring keyword
11794 arguments we do not recognize.
11795 - Expand homedirs passed to tor-checkkey. This should silence a
11796 coverity complaint about passing a user-supplied string into
11797 open() without checking it.
11800 Changes in version 0.2.1.25 - 2010-03-16
11801 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
11802 prevent relays from guessing their IP address correctly. It also fixes
11803 several minor potential security bugs.
11806 - Fix a regression from our patch for bug 1244 that caused relays
11807 to guess their IP address incorrectly if they didn't set Address
11808 in their torrc and/or their address fails to resolve. Bugfix on
11809 0.2.1.23; fixes bug 1269.
11810 - When freeing a session key, zero it out completely. We only zeroed
11811 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
11812 patched by ekir. Fixes bug 1254.
11815 - Fix a dereference-then-NULL-check sequence when publishing
11816 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
11818 - Fix another dereference-then-NULL-check sequence. Bugfix on
11819 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
11820 - Make sure we treat potentially not NUL-terminated strings correctly.
11821 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
11825 Changes in version 0.2.1.24 - 2010-02-21
11826 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
11830 - Work correctly out-of-the-box with even more vendor-patched versions
11831 of OpenSSL. In particular, make it so Debian and OS X don't need
11832 customized patches to run/build.
11835 Changes in version 0.2.1.23 - 2010-02-13
11836 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
11837 again on the latest OS X, and updates the location of a directory
11840 o Major bugfixes (performance):
11841 - We were selecting our guards uniformly at random, and then weighting
11842 which of our guards we'd use uniformly at random. This imbalance
11843 meant that Tor clients were severely limited on throughput (and
11844 probably latency too) by the first hop in their circuit. Now we
11845 select guards weighted by currently advertised bandwidth. We also
11846 automatically discard guards picked using the old algorithm. Fixes
11847 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11850 - Make Tor work again on the latest OS X: when deciding whether to
11851 use strange flags to turn TLS renegotiation on, detect the OpenSSL
11852 version at run-time, not compile time. We need to do this because
11853 Apple doesn't update its dev-tools headers when it updates its
11854 libraries in a security patch.
11855 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
11856 that could happen on 32-bit platforms with 64-bit time_t. Also fix
11857 a memory leak when requesting a hidden service descriptor we've
11858 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
11861 o Directory authority changes:
11862 - Change IP address for dannenberg (v3 directory authority), and
11863 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
11864 service directory authority) from the list.
11867 - Refactor resolve_my_address() to not use gethostbyname() anymore.
11868 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
11871 - Avoid a mad rush at the beginning of each month when each client
11872 rotates half of its guards. Instead we spread the rotation out
11873 throughout the month, but we still avoid leaving a precise timestamp
11874 in the state file about when we first picked the guard. Improves
11875 over the behavior introduced in 0.1.2.17.
11878 Changes in version 0.2.2.8-alpha - 2010-01-26
11879 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
11880 causing bridge relays to disappear. If you're running a bridge,
11884 - Fix a memory corruption bug on bridges that occured during the
11885 inclusion of stats data in extra-info descriptors. Also fix the
11886 interface for geoip_get_bridge_stats* to prevent similar bugs in
11887 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
11888 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
11891 - Ignore OutboundBindAddress when connecting to localhost.
11892 Connections to localhost need to come _from_ localhost, or else
11893 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
11897 Changes in version 0.2.2.7-alpha - 2010-01-19
11898 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
11899 as laying the groundwork for further relay-side performance fixes. It
11900 also starts cleaning up client behavior with respect to the EntryNodes,
11901 ExitNodes, and StrictNodes config options.
11903 This release also rotates two directory authority keys, due to a
11904 security breach of some of the Torproject servers.
11906 o Directory authority changes:
11907 - Rotate keys (both v3 identity and relay identity) for moria1
11910 o Major features (performance):
11911 - We were selecting our guards uniformly at random, and then weighting
11912 which of our guards we'd use uniformly at random. This imbalance
11913 meant that Tor clients were severely limited on throughput (and
11914 probably latency too) by the first hop in their circuit. Now we
11915 select guards weighted by currently advertised bandwidth. We also
11916 automatically discard guards picked using the old algorithm. Fixes
11917 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11918 - When choosing which cells to relay first, relays can now favor
11919 circuits that have been quiet recently, to provide lower latency
11920 for low-volume circuits. By default, relays enable or disable this
11921 feature based on a setting in the consensus. You can override
11922 this default by using the new "CircuitPriorityHalflife" config
11923 option. Design and code by Ian Goldberg, Can Tang, and Chris
11925 - Add separate per-conn write limiting to go with the per-conn read
11926 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
11927 but never per-conn write limits.
11928 - New consensus params "bwconnrate" and "bwconnburst" to let us
11929 rate-limit client connections as they enter the network. It's
11930 controlled in the consensus so we can turn it on and off for
11931 experiments. It's starting out off. Based on proposal 163.
11933 o Major features (relay selection options):
11934 - Switch to a StrictNodes config option, rather than the previous
11935 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
11936 "StrictExcludeNodes" option.
11937 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
11938 change during a config reload, mark and discard all our origin
11939 circuits. This fix should address edge cases where we change the
11940 config options and but then choose a circuit that we created before
11942 - If EntryNodes or ExitNodes are set, be more willing to use an
11943 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
11945 - Make EntryNodes config option much more aggressive even when
11946 StrictNodes is not set. Before it would prepend your requested
11947 entrynodes to your list of guard nodes, but feel free to use others
11948 after that. Now it chooses only from your EntryNodes if any of
11949 those are available, and only falls back to others if a) they're
11950 all down and b) StrictNodes is not set.
11951 - Now we refresh your entry guards from EntryNodes at each consensus
11952 fetch -- rather than just at startup and then they slowly rot as
11953 the network changes.
11956 - Stop bridge directory authorities from answering dbg-stability.txt
11957 directory queries, which would let people fetch a list of all
11958 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11961 - Log a notice when we get a new control connection. Now it's easier
11962 for security-conscious users to recognize when a local application
11963 is knocking on their controller door. Suggested by bug 1196.
11964 - New config option "CircuitStreamTimeout" to override our internal
11965 timeout schedule for how many seconds until we detach a stream from
11966 a circuit and try a new circuit. If your network is particularly
11967 slow, you might want to set this to a number like 60.
11968 - New controller command "getinfo config-text". It returns the
11969 contents that Tor would write if you send it a SAVECONF command,
11970 so the controller can write the file to disk itself.
11971 - New options for SafeLogging to allow scrubbing only log messages
11972 generated while acting as a relay.
11973 - Ship the bridges spec file in the tarball too.
11974 - Avoid a mad rush at the beginning of each month when each client
11975 rotates half of its guards. Instead we spread the rotation out
11976 throughout the month, but we still avoid leaving a precise timestamp
11977 in the state file about when we first picked the guard. Improves
11978 over the behavior introduced in 0.1.2.17.
11980 o Minor bugfixes (compiling):
11981 - Fix compilation on OS X 10.3, which has a stub mlockall() but
11982 hides it. Bugfix on 0.2.2.6-alpha.
11983 - Fix compilation on Solaris by removing support for the
11984 DisableAllSwap config option. Solaris doesn't have an rlimit for
11985 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
11988 o Minor bugfixes (crashes):
11989 - Do not segfault when writing buffer stats when we haven't observed
11990 a single circuit to report about. Found by Fabian Lanze. Bugfix on
11992 - If we're in the pathological case where there's no exit bandwidth
11993 but there is non-exit bandwidth, or no guard bandwidth but there
11994 is non-guard bandwidth, don't crash during path selection. Bugfix
11996 - Fix an impossible-to-actually-trigger buffer overflow in relay
11997 descriptor generation. Bugfix on 0.1.0.15.
11999 o Minor bugfixes (privacy):
12000 - Fix an instance where a Tor directory mirror might accidentally
12001 log the IP address of a misbehaving Tor client. Bugfix on
12003 - Don't list Windows capabilities in relay descriptors. We never made
12004 use of them, and maybe it's a bad idea to publish them. Bugfix
12007 o Minor bugfixes (other):
12008 - Resolve an edge case in path weighting that could make us misweight
12009 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
12010 - Fix statistics on client numbers by country as seen by bridges that
12011 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
12012 intervals instead of variable 12-to-48-hour intervals.
12013 - After we free an internal connection structure, overwrite it
12014 with a different memory value than we use for overwriting a freed
12015 internal circuit structure. Should help with debugging. Suggested
12017 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
12020 o Removed features:
12021 - Remove the HSAuthorityRecordStats option that version 0 hidden
12022 service authorities could have used to track statistics of overall
12023 hidden service usage.
12026 Changes in version 0.2.1.22 - 2010-01-19
12027 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
12028 authorities -- it would tell you its whole history of bridge descriptors
12029 if you make the right directory request. This stable update also
12030 rotates two of the seven v3 directory authority keys and locations.
12032 o Directory authority changes:
12033 - Rotate keys (both v3 identity and relay identity) for moria1
12037 - Stop bridge directory authorities from answering dbg-stability.txt
12038 directory queries, which would let people fetch a list of all
12039 bridge identities they track. Bugfix on 0.2.1.6-alpha.
12042 Changes in version 0.2.1.21 - 2009-12-21
12043 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
12044 library. If you use Tor on Linux / Unix and you're getting SSL
12045 renegotiation errors, upgrading should help. We also recommend an
12046 upgrade if you're an exit relay.
12049 - Work around a security feature in OpenSSL 0.9.8l that prevents our
12050 handshake from working unless we explicitly tell OpenSSL that we
12051 are using SSL renegotiation safely. We are, of course, but OpenSSL
12052 0.9.8l won't work unless we say we are.
12053 - Avoid crashing if the client is trying to upload many bytes and the
12054 circuit gets torn down at the same time, or if the flip side
12055 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
12058 - Do not refuse to learn about authority certs and v2 networkstatus
12059 documents that are older than the latest consensus. This bug might
12060 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
12061 Spotted and fixed by xmux.
12062 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
12063 trigger platform-specific option misparsing case found by Coverity
12065 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
12066 trigger assert. Fixes bug 1173.
12069 Changes in version 0.2.2.6-alpha - 2009-11-19
12070 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
12071 support for the new lower-footprint "microdescriptor" directory design,
12072 future-proofing our consensus format against new hash functions or
12073 other changes, and an Android port. It also makes Tor compatible with
12074 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
12077 - Directory authorities can now create, vote on, and serve multiple
12078 parallel formats of directory data as part of their voting process.
12079 Partially implements Proposal 162: "Publish the consensus in
12081 - Directory authorities can now agree on and publish small summaries
12082 of router information that clients can use in place of regular
12083 server descriptors. This transition will eventually allow clients
12084 to use far less bandwidth for downloading information about the
12085 network. Begins the implementation of Proposal 158: "Clients
12086 download consensus + microdescriptors".
12087 - The directory voting system is now extensible to use multiple hash
12088 algorithms for signatures and resource selection. Newer formats
12089 are signed with SHA256, with a possibility for moving to a better
12090 hash algorithm in the future.
12091 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
12092 current and future memory pages via mlockall(). On supported
12093 platforms (modern Linux and probably BSD but not Windows or OS X),
12094 this should effectively disable any and all attempts to page out
12095 memory. This option requires that you start your Tor as root --
12096 if you use DisableAllSwap, please consider using the User option
12097 to properly reduce the privileges of your Tor.
12098 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
12099 to help Tor build correctly for Android phones.
12102 - Work around a security feature in OpenSSL 0.9.8l that prevents our
12103 handshake from working unless we explicitly tell OpenSSL that we
12104 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
12105 won't work unless we say we are.
12108 - Fix a crash bug when trying to initialize the evdns module in
12109 Libevent 2. Bugfix on 0.2.1.16-rc.
12110 - Stop logging at severity 'warn' when some other Tor client tries
12111 to establish a circuit with us using weak DH keys. It's a protocol
12112 violation, but that doesn't mean ordinary users need to hear about
12113 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
12114 - Do not refuse to learn about authority certs and v2 networkstatus
12115 documents that are older than the latest consensus. This bug might
12116 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
12117 Spotted and fixed by xmux.
12118 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
12119 - If all authorities restart at once right before a consensus vote,
12120 nobody will vote about "Running", and clients will get a consensus
12121 with no usable relays. Instead, authorities refuse to build a
12122 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
12123 - If your relay can't keep up with the number of incoming create
12124 cells, it would log one warning per failure into your logs. Limit
12125 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
12126 - Bridges now use "reject *:*" as their default exit policy. Bugfix
12127 on 0.2.0.3-alpha; fixes bug 1113.
12128 - Fix a memory leak on directory authorities during voting that was
12129 introduced in 0.2.2.1-alpha. Found via valgrind.
12132 Changes in version 0.2.1.20 - 2009-10-15
12133 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
12134 services at once, prepares for more performance improvements, and
12135 fixes a bunch of smaller bugs.
12137 The Windows and OS X bundles also include a more recent Vidalia,
12138 and switch from Privoxy to Polipo.
12140 The OS X installers are now drag and drop. It's best to un-install
12141 Tor/Vidalia and then install this new bundle, rather than upgrade. If
12142 you want to upgrade, you'll need to update the paths for Tor and Polipo
12143 in the Vidalia Settings window.
12146 - Send circuit or stream sendme cells when our window has decreased
12147 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
12148 by Karsten when testing the "reduce circuit window" performance
12149 patch. Bugfix on the 54th commit on Tor -- from July 2002,
12150 before the release of Tor 0.0.0. This is the new winner of the
12152 - Fix a remotely triggerable memory leak when a consensus document
12153 contains more than one signature from the same voter. Bugfix on
12155 - Avoid segfault in rare cases when finishing an introduction circuit
12156 as a client and finding out that we don't have an introduction key
12157 for it. Fixes bug 1073. Reported by Aaron Swartz.
12160 - Tor now reads the "circwindow" parameter out of the consensus,
12161 and uses that value for its circuit package window rather than the
12162 default of 1000 cells. Begins the implementation of proposal 168.
12164 o New directory authorities:
12165 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
12167 - Move moria1 and tonga to alternate IP addresses.
12170 - Fix a signed/unsigned compile warning in 0.2.1.19.
12171 - Fix possible segmentation fault on directory authorities. Bugfix on
12173 - Fix an extremely rare infinite recursion bug that could occur if
12174 we tried to log a message after shutting down the log subsystem.
12175 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
12176 - Fix an obscure bug where hidden services on 64-bit big-endian
12177 systems might mis-read the timestamp in v3 introduce cells, and
12178 refuse to connect back to the client. Discovered by "rotor".
12179 Bugfix on 0.2.1.6-alpha.
12180 - We were triggering a CLOCK_SKEW controller status event whenever
12181 we connect via the v2 connection protocol to any relay that has
12182 a wrong clock. Instead, we should only inform the controller when
12183 it's a trusted authority that claims our clock is wrong. Bugfix
12184 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
12185 - We were telling the controller about CHECKING_REACHABILITY and
12186 REACHABILITY_FAILED status events whenever we launch a testing
12187 circuit or notice that one has failed. Instead, only tell the
12188 controller when we want to inform the user of overall success or
12189 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
12191 - Don't warn when we're using a circuit that ends with a node
12192 excluded in ExcludeExitNodes, but the circuit is not used to access
12193 the outside world. This should help fix bug 1090. Bugfix on
12195 - Work around a small memory leak in some versions of OpenSSL that
12196 stopped the memory used by the hostname TLS extension from being
12200 - Add a "getinfo status/accepted-server-descriptor" controller
12201 command, which is the recommended way for controllers to learn
12202 whether our server descriptor has been successfully received by at
12203 least on directory authority. Un-recommend good-server-descriptor
12204 getinfo and status events until we have a better design for them.
12207 Changes in version 0.2.2.5-alpha - 2009-10-11
12208 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
12211 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
12213 o Directory authorities:
12214 - Temporarily (just for this release) move dizum to an alternate
12218 Changes in version 0.2.2.4-alpha - 2009-10-10
12219 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
12220 introduces a new unit test framework, shifts directry authority
12221 addresses around to reduce the impact from recent blocking events,
12222 and fixes a few smaller bugs.
12225 - Fix several more asserts in the circuit_build_times code, for
12226 example one that causes Tor to fail to start once we have
12227 accumulated 5000 build times in the state file. Bugfixes on
12228 0.2.2.2-alpha; fixes bug 1108.
12230 o New directory authorities:
12231 - Move moria1 and Tonga to alternate IP addresses.
12234 - Log SSL state transitions at debug level during handshake, and
12235 include SSL states in error messages. This may help debug future
12236 SSL handshake issues.
12237 - Add a new "Handshake" log domain for activities that happen
12238 during the TLS handshake.
12239 - Revert to the "June 3 2009" ip-to-country file. The September one
12240 seems to have removed most US IP addresses.
12241 - Directory authorities now reject Tor relays with versions less than
12242 0.1.2.14. This step cuts out four relays from the current network,
12243 none of which are very big.
12246 - Fix a couple of smaller issues with gathering statistics. Bugfixes
12248 - Fix two memory leaks in the error case of
12249 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
12250 - Don't count one-hop circuits when we're estimating how long it
12251 takes circuits to build on average. Otherwise we'll set our circuit
12252 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
12253 - Directory authorities no longer change their opinion of, or vote on,
12254 whether a router is Running, unless they have themselves been
12255 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
12258 o Code simplifications and refactoring:
12259 - Revise our unit tests to use the "tinytest" framework, so we
12260 can run tests in their own processes, have smarter setup/teardown
12261 code, and so on. The unit test code has moved to its own
12262 subdirectory, and has been split into multiple modules.
12265 Changes in version 0.2.2.3-alpha - 2009-09-23
12266 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
12269 - Fix an overzealous assert in our new circuit build timeout code.
12270 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
12273 - If the networkstatus consensus tells us that we should use a
12274 negative circuit package window, ignore it. Otherwise we'll
12275 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
12278 Changes in version 0.2.2.2-alpha - 2009-09-21
12279 Tor 0.2.2.2-alpha introduces our latest performance improvement for
12280 clients: Tor tracks the average time it takes to build a circuit, and
12281 avoids using circuits that take too long to build. For fast connections,
12282 this feature can cut your expected latency in half. For slow or flaky
12283 connections, it could ruin your Tor experience. Let us know if it does!
12286 - Tor now tracks how long it takes to build client-side circuits
12287 over time, and adapts its timeout to local network performance.
12288 Since a circuit that takes a long time to build will also provide
12289 bad performance, we get significant latency improvements by
12290 discarding the slowest 20% of circuits. Specifically, Tor creates
12291 circuits more aggressively than usual until it has enough data
12292 points for a good timeout estimate. Implements proposal 151.
12293 We are especially looking for reports (good and bad) from users with
12294 both EDGE and broadband connections that can move from broadband
12295 to EDGE and find out if the build-time data in the .tor/state gets
12296 reset without loss of Tor usability. You should also see a notice
12297 log message telling you that Tor has reset its timeout.
12298 - Directory authorities can now vote on arbitary integer values as
12299 part of the consensus process. This is designed to help set
12300 network-wide parameters. Implements proposal 167.
12301 - Tor now reads the "circwindow" parameter out of the consensus,
12302 and uses that value for its circuit package window rather than the
12303 default of 1000 cells. Begins the implementation of proposal 168.
12306 - Fix a remotely triggerable memory leak when a consensus document
12307 contains more than one signature from the same voter. Bugfix on
12311 - Fix an extremely rare infinite recursion bug that could occur if
12312 we tried to log a message after shutting down the log subsystem.
12313 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
12314 - Fix parsing for memory or time units given without a space between
12315 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
12316 - A networkstatus vote must contain exactly one signature. Spec
12317 conformance issue. Bugfix on 0.2.0.3-alpha.
12318 - Fix an obscure bug where hidden services on 64-bit big-endian
12319 systems might mis-read the timestamp in v3 introduce cells, and
12320 refuse to connect back to the client. Discovered by "rotor".
12321 Bugfix on 0.2.1.6-alpha.
12322 - We were triggering a CLOCK_SKEW controller status event whenever
12323 we connect via the v2 connection protocol to any relay that has
12324 a wrong clock. Instead, we should only inform the controller when
12325 it's a trusted authority that claims our clock is wrong. Bugfix
12326 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
12327 - We were telling the controller about CHECKING_REACHABILITY and
12328 REACHABILITY_FAILED status events whenever we launch a testing
12329 circuit or notice that one has failed. Instead, only tell the
12330 controller when we want to inform the user of overall success or
12331 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
12333 - Don't warn when we're using a circuit that ends with a node
12334 excluded in ExcludeExitNodes, but the circuit is not used to access
12335 the outside world. This should help fix bug 1090, but more problems
12336 remain. Bugfix on 0.2.1.6-alpha.
12337 - Work around a small memory leak in some versions of OpenSSL that
12338 stopped the memory used by the hostname TLS extension from being
12340 - Make our 'torify' script more portable; if we have only one of
12341 'torsocks' or 'tsocks' installed, don't complain to the user;
12342 and explain our warning about tsocks better.
12345 - Add a "getinfo status/accepted-server-descriptor" controller
12346 command, which is the recommended way for controllers to learn
12347 whether our server descriptor has been successfully received by at
12348 least on directory authority. Un-recommend good-server-descriptor
12349 getinfo and status events until we have a better design for them.
12350 - Update to the "September 4 2009" ip-to-country file.
12353 Changes in version 0.2.2.1-alpha - 2009-08-26
12354 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
12355 Tor clients to bootstrap on networks where only port 80 is reachable,
12356 makes it more straightforward to support hardware crypto accelerators,
12357 and starts the groundwork for gathering stats safely at relays.
12360 - Start the process of disabling ".exit" address notation, since it
12361 can be used for a variety of esoteric application-level attacks
12362 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
12365 o New directory authorities:
12366 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
12370 - New AccelName and AccelDir options add support for dynamic OpenSSL
12371 hardware crypto acceleration engines.
12372 - Tor now supports tunneling all of its outgoing connections over
12373 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
12374 configuration options. Code by Christopher Davis.
12377 - Send circuit or stream sendme cells when our window has decreased
12378 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
12379 by Karsten when testing the "reduce circuit window" performance
12380 patch. Bugfix on the 54th commit on Tor -- from July 2002,
12381 before the release of Tor 0.0.0. This is the new winner of the
12384 o New options for gathering stats safely:
12385 - Directory mirrors that set "DirReqStatistics 1" write statistics
12386 about directory requests to disk every 24 hours. As compared to the
12387 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
12388 1) stats are written to disk exactly every 24 hours; 2) estimated
12389 shares of v2 and v3 requests are determined as mean values, not at
12390 the end of a measurement period; 3) unresolved requests are listed
12391 with country code '??'; 4) directories also measure download times.
12392 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
12393 number of exit streams and transferred bytes per port to disk every
12395 - Relays that set "CellStatistics 1" write statistics on how long
12396 cells spend in their circuit queues to disk every 24 hours.
12397 - Entry nodes that set "EntryStatistics 1" write statistics on the
12398 rough number and origins of connecting clients to disk every 24
12400 - Relays that write any of the above statistics to disk and set
12401 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
12402 their extra-info documents.
12405 - New --digests command-line switch to output the digests of the
12406 source files Tor was built with.
12407 - The "torify" script now uses torsocks where available.
12408 - The memarea code now uses a sentinel value at the end of each area
12409 to make sure nothing writes beyond the end of an area. This might
12410 help debug some conceivable causes of bug 930.
12411 - Time and memory units in the configuration file can now be set to
12412 fractional units. For example, "2.5 GB" is now a valid value for
12414 - Certain Tor clients (such as those behind check.torproject.org) may
12415 want to fetch the consensus in an extra early manner. To enable this
12416 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
12417 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
12418 as only certain clients who must have this information sooner should
12420 - Instead of adding the svn revision to the Tor version string, report
12421 the git commit (when we're building from a git checkout).
12424 - If any of the v3 certs we download are unparseable, we should
12425 actually notice the failure so we don't retry indefinitely. Bugfix
12426 on 0.2.0.x; reported by "rotator".
12427 - If the cached cert file is unparseable, warn but don't exit.
12428 - Fix possible segmentation fault on directory authorities. Bugfix on
12430 - When Tor fails to parse a descriptor of any kind, dump it to disk.
12431 Might help diagnosing bug 1051.
12433 o Deprecated and removed features:
12434 - The controller no longer accepts the old obsolete "addr-mappings/"
12435 or "unregistered-servers-" GETINFO values.
12436 - Hidden services no longer publish version 0 descriptors, and clients
12437 do not request or use version 0 descriptors. However, the old hidden
12438 service authorities still accept and serve version 0 descriptors
12439 when contacted by older hidden services/clients.
12440 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
12441 always on; using them is necessary for correct forward-compatible
12443 - Remove support for .noconnect style addresses. Nobody was using
12444 them, and they provided another avenue for detecting Tor users
12445 via application-level web tricks.
12447 o Packaging changes:
12448 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
12449 installer bundles. See
12450 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
12451 for details of what's new in Vidalia 0.2.3.
12452 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
12453 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
12454 configuration file, rather than the old Privoxy.
12455 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
12456 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
12457 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
12458 better compatibility with OS X 10.6, aka Snow Leopard.
12459 - OS X Vidalia Bundle: The multi-package installer is now replaced
12460 by a simple drag and drop to the /Applications folder. This change
12461 occurred with the upgrade to Vidalia 0.2.3.
12464 Changes in version 0.2.1.19 - 2009-07-28
12465 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
12466 services on Tor 0.2.1.3-alpha through 0.2.1.18.
12469 - Make accessing hidden services on 0.2.1.x work right again.
12470 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
12471 part of patch provided by "optimist".
12474 - When a relay/bridge is writing out its identity key fingerprint to
12475 the "fingerprint" file and to its logs, write it without spaces. Now
12476 it will look like the fingerprints in our bridges documentation,
12477 and confuse fewer users.
12480 - Relays no longer publish a new server descriptor if they change
12481 their MaxAdvertisedBandwidth config option but it doesn't end up
12482 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
12483 fixes bug 1026. Patch from Sebastian.
12484 - Avoid leaking memory every time we get a create cell but we have
12485 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
12486 fixes bug 1034. Reported by BarkerJr.
12489 Changes in version 0.2.1.18 - 2009-07-24
12490 Tor 0.2.1.18 lays the foundations for performance improvements,
12491 adds status events to help users diagnose bootstrap problems, adds
12492 optional authentication/authorization for hidden services, fixes a
12493 variety of potential anonymity problems, and includes a huge pile of
12494 other features and bug fixes.
12497 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
12500 Changes in version 0.2.1.17-rc - 2009-07-07
12501 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
12502 candidate for the 0.2.1.x series. It lays the groundwork for further
12503 client performance improvements, and also fixes a big bug with directory
12504 authorities that were causing them to assign Guard and Stable flags
12507 The Windows bundles also finally include the geoip database that we
12508 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
12509 should actually install Torbutton rather than giving you a cryptic
12510 failure message (oops).
12513 - Clients now use the bandwidth values in the consensus, rather than
12514 the bandwidth values in each relay descriptor. This approach opens
12515 the door to more accurate bandwidth estimates once the directory
12516 authorities start doing active measurements. Implements more of
12520 - When Tor clients restart after 1-5 days, they discard all their
12521 cached descriptors as too old, but they still use the cached
12522 consensus document. This approach is good for robustness, but
12523 bad for performance: since they don't know any bandwidths, they
12524 end up choosing at random rather than weighting their choice by
12525 speed. Fixed by the above feature of putting bandwidths in the
12526 consensus. Bugfix on 0.2.0.x.
12527 - Directory authorities were neglecting to mark relays down in their
12528 internal histories if the relays fall off the routerlist without
12529 ever being found unreachable. So there were relays in the histories
12530 that haven't been seen for eight months, and are listed as being
12531 up for eight months. This wreaked havoc on the "median wfu"
12532 and "median mtbf" calculations, in turn making Guard and Stable
12533 flags very wrong, hurting network performance. Fixes bugs 696 and
12534 969. Bugfix on 0.2.0.6-alpha.
12537 - Serve the DirPortFrontPage page even when we have been approaching
12538 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
12539 - The control port would close the connection before flushing long
12540 replies, such as the network consensus, if a QUIT command was issued
12541 before the reply had completed. Now, the control port flushes all
12542 pending replies before closing the connection. Also fixed a spurious
12543 warning when a QUIT command is issued after a malformed or rejected
12544 AUTHENTICATE command, but before the connection was closed. Patch
12545 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
12546 - When we can't find an intro key for a v2 hidden service descriptor,
12547 fall back to the v0 hidden service descriptor and log a bug message.
12548 Workaround for bug 1024.
12549 - Fix a log message that did not respect the SafeLogging option.
12553 - If we're a relay and we change our IP address, be more verbose
12554 about the reason that made us change. Should help track down
12555 further bugs for relays on dynamic IP addresses.
12558 Changes in version 0.2.0.35 - 2009-06-24
12560 - Avoid crashing in the presence of certain malformed descriptors.
12561 Found by lark, and by automated fuzzing.
12562 - Fix an edge case where a malicious exit relay could convince a
12563 controller that the client's DNS question resolves to an internal IP
12564 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12567 - Finally fix the bug where dynamic-IP relays disappear when their
12568 IP address changes: directory mirrors were mistakenly telling
12569 them their old address if they asked via begin_dir, so they
12570 never got an accurate answer about their new address, so they
12571 just vanished after a day. For belt-and-suspenders, relays that
12572 don't set Address in their config now avoid using begin_dir for
12573 all direct connections. Should fix bugs 827, 883, and 900.
12574 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
12575 that would occur on some exit nodes when DNS failures and timeouts
12576 occurred in certain patterns. Fix for bug 957.
12579 - When starting with a cache over a few days old, do not leak
12580 memory for the obsolete router descriptors in it. Bugfix on
12581 0.2.0.33; fixes bug 672.
12582 - Hidden service clients didn't use a cached service descriptor that
12583 was older than 15 minutes, but wouldn't fetch a new one either,
12584 because there was already one in the cache. Now, fetch a v2
12585 descriptor unless the same descriptor was added to the cache within
12586 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12589 Changes in version 0.2.1.16-rc - 2009-06-20
12590 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
12591 a bunch of minor bugs.
12594 - Fix an edge case where a malicious exit relay could convince a
12595 controller that the client's DNS question resolves to an internal IP
12596 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12598 o Major performance improvements (on 0.2.0.x):
12599 - Disable and refactor some debugging checks that forced a linear scan
12600 over the whole server-side DNS cache. These accounted for over 50%
12601 of CPU time on a relatively busy exit node's gprof profile. Found
12603 - Disable some debugging checks that appeared in exit node profile
12607 - Update to the "June 3 2009" ip-to-country file.
12608 - Do not have tor-resolve automatically refuse all .onion addresses;
12609 if AutomapHostsOnResolve is set in your torrc, this will work fine.
12611 o Minor bugfixes (on 0.2.0.x):
12612 - Log correct error messages for DNS-related network errors on
12614 - Fix a race condition that could cause crashes or memory corruption
12615 when running as a server with a controller listening for log
12617 - Avoid crashing when we have a policy specified in a DirPolicy or
12618 SocksPolicy or ReachableAddresses option with ports set on it,
12619 and we re-load the policy. May fix bug 996.
12620 - Hidden service clients didn't use a cached service descriptor that
12621 was older than 15 minutes, but wouldn't fetch a new one either,
12622 because there was already one in the cache. Now, fetch a v2
12623 descriptor unless the same descriptor was added to the cache within
12624 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12626 o Minor bugfixes (on 0.2.1.x):
12627 - Don't warn users about low port and hibernation mix when they
12628 provide a *ListenAddress directive to fix that. Bugfix on
12630 - When switching back and forth between bridge mode, do not start
12631 gathering GeoIP data until two hours have passed.
12632 - Do not complain that the user has requested an excluded node as
12633 an exit when the node is not really an exit. This could happen
12634 because the circuit was for testing, or an introduction point.
12638 Changes in version 0.2.1.15-rc - 2009-05-25
12639 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
12640 series. It fixes a major bug on fast exit relays, as well as a variety
12641 of more minor bugs.
12643 o Major bugfixes (on 0.2.0.x):
12644 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
12645 that would occur on some exit nodes when DNS failures and timeouts
12646 occurred in certain patterns. Fix for bug 957.
12648 o Minor bugfixes (on 0.2.0.x):
12649 - Actually return -1 in the error case for read_bandwidth_usage().
12650 Harmless bug, since we currently don't care about the return value
12651 anywhere. Bugfix on 0.2.0.9-alpha.
12652 - Provide a more useful log message if bug 977 (related to buffer
12653 freelists) ever reappears, and do not crash right away.
12654 - Fix an assertion failure on 64-bit platforms when we allocated
12655 memory right up to the end of a memarea, then realigned the memory
12656 one step beyond the end. Fixes a possible cause of bug 930.
12657 - Protect the count of open sockets with a mutex, so we can't
12658 corrupt it when two threads are closing or opening sockets at once.
12659 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
12660 - Don't allow a bridge to publish its router descriptor to a
12661 non-bridge directory authority. Fixes part of bug 932.
12662 - When we change to or from being a bridge, reset our counts of
12663 client usage by country. Fixes bug 932.
12664 - Fix a bug that made stream bandwidth get misreported to the
12666 - Stop using malloc_usable_size() to use more area than we had
12667 actually allocated: it was safe, but made valgrind really unhappy.
12668 - Fix a memory leak when v3 directory authorities load their keys
12669 and cert from disk. Bugfix on 0.2.0.1-alpha.
12671 o Minor bugfixes (on 0.2.1.x):
12672 - Fix use of freed memory when deciding to mark a non-addable
12673 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
12676 Changes in version 0.2.1.14-rc - 2009-04-12
12677 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
12678 series. It begins fixing some major performance problems, and also
12679 finally addresses the bug that was causing relays on dynamic IP
12680 addresses to fall out of the directory.
12683 - Clients replace entry guards that were chosen more than a few months
12684 ago. This change should significantly improve client performance,
12685 especially once more people upgrade, since relays that have been
12686 a guard for a long time are currently overloaded.
12688 o Major bugfixes (on 0.2.0):
12689 - Finally fix the bug where dynamic-IP relays disappear when their
12690 IP address changes: directory mirrors were mistakenly telling
12691 them their old address if they asked via begin_dir, so they
12692 never got an accurate answer about their new address, so they
12693 just vanished after a day. For belt-and-suspenders, relays that
12694 don't set Address in their config now avoid using begin_dir for
12695 all direct connections. Should fix bugs 827, 883, and 900.
12696 - Relays were falling out of the networkstatus consensus for
12697 part of a day if they changed their local config but the
12698 authorities discarded their new descriptor as "not sufficiently
12699 different". Now directory authorities accept a descriptor as changed
12700 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
12701 patch by Sebastian.
12702 - Avoid crashing in the presence of certain malformed descriptors.
12703 Found by lark, and by automated fuzzing.
12706 - When generating circuit events with verbose nicknames for
12707 controllers, try harder to look up nicknames for routers on a
12708 circuit. (Previously, we would look in the router descriptors we had
12709 for nicknames, but not in the consensus.) Partial fix for bug 941.
12710 - If the bridge config line doesn't specify a port, assume 443.
12711 This makes bridge lines a bit smaller and easier for users to
12713 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
12714 bytes (aka 20KB/s), to match our documentation. Also update
12715 directory authorities so they always assign the Fast flag to relays
12716 with 20KB/s of capacity. Now people running relays won't suddenly
12717 find themselves not seeing any use, if the network gets faster
12719 - Update to the "April 3 2009" ip-to-country file.
12722 - Avoid trying to print raw memory to the logs when we decide to
12723 give up on downloading a given relay descriptor. Bugfix on
12725 - In tor-resolve, when the Tor client to use is specified by
12726 <hostname>:<port>, actually use the specified port rather than
12727 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
12728 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
12729 - When starting with a cache over a few days old, do not leak
12730 memory for the obsolete router descriptors in it. Bugfix on
12732 - Avoid double-free on list of successfully uploaded hidden
12733 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
12734 - Change memarea_strndup() implementation to work even when
12735 duplicating a string at the end of a page. This bug was
12736 harmless for now, but could have meant crashes later. Fix by
12737 lark. Bugfix on 0.2.1.1-alpha.
12738 - Limit uploaded directory documents to be 16M rather than 500K.
12739 The directory authorities were refusing v3 consensus votes from
12740 other authorities, since the votes are now 504K. Fixes bug 959;
12741 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
12742 - Directory authorities should never send a 503 "busy" response to
12743 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
12747 Changes in version 0.2.1.13-alpha - 2009-03-09
12748 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
12749 cleanups. We're finally getting close to a release candidate.
12752 - Correctly update the list of which countries we exclude as
12753 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
12754 lark. Bugfix on 0.2.1.6-alpha.
12756 o Minor bugfixes (on 0.2.0.x and earlier):
12757 - Automatically detect MacOSX versions earlier than 10.4.0, and
12758 disable kqueue from inside Tor when running with these versions.
12759 We previously did this from the startup script, but that was no
12760 help to people who didn't use the startup script. Resolves bug 863.
12761 - When we had picked an exit node for a connection, but marked it as
12762 "optional", and it turned out we had no onion key for the exit,
12763 stop wanting that exit and try again. This situation may not
12764 be possible now, but will probably become feasible with proposal
12765 158. Spotted by rovv. Fixes another case of bug 752.
12766 - Clients no longer cache certificates for authorities they do not
12767 recognize. Bugfix on 0.2.0.9-alpha.
12768 - When we can't transmit a DNS request due to a network error, retry
12769 it after a while, and eventually transmit a failing response to
12770 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
12771 - If the controller claimed responsibility for a stream, but that
12772 stream never finished making its connection, it would live
12773 forever in circuit_wait state. Now we close it after SocksTimeout
12774 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
12775 - Drop begin cells to a hidden service if they come from the middle
12776 of a circuit. Patch from lark.
12777 - When we erroneously receive two EXTEND cells for the same circuit
12778 ID on the same connection, drop the second. Patch from lark.
12779 - Fix a crash that occurs on exit nodes when a nameserver request
12780 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
12781 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
12783 - Do not assume that a stack-allocated character array will be
12784 64-bit aligned on platforms that demand that uint64_t access is
12785 aligned. Possible fix for bug 604.
12786 - Parse dates and IPv4 addresses in a locale- and libc-independent
12787 manner, to avoid platform-dependent behavior on malformed input.
12788 - Build correctly when configured to build outside the main source
12789 path. Patch from Michael Gold.
12790 - We were already rejecting relay begin cells with destination port
12791 of 0. Now also reject extend cells with destination port or address
12792 of 0. Suggested by lark.
12794 o Minor bugfixes (on 0.2.1.x):
12795 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
12796 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
12797 - If we're an exit node, scrub the IP address to which we are exiting
12798 in the logs. Bugfix on 0.2.1.8-alpha.
12801 - On Linux, use the prctl call to re-enable core dumps when the user
12803 - New controller event NEWCONSENSUS that lists the networkstatus
12804 lines for every recommended relay. Now controllers like Torflow
12805 can keep up-to-date on which relays they should be using.
12806 - Update to the "February 26 2009" ip-to-country file.
12809 Changes in version 0.2.0.34 - 2009-02-08
12810 Tor 0.2.0.34 features several more security-related fixes. You should
12811 upgrade, especially if you run an exit relay (remote crash) or a
12812 directory authority (remote infinite loop), or you're on an older
12813 (pre-XP) or not-recently-patched Windows (remote exploit).
12815 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
12816 have many known flaws, and nobody should be using them. You should
12817 upgrade. If you're using a Linux or BSD and its packages are obsolete,
12818 stop using those packages and upgrade anyway.
12821 - Fix an infinite-loop bug on handling corrupt votes under certain
12822 circumstances. Bugfix on 0.2.0.8-alpha.
12823 - Fix a temporary DoS vulnerability that could be performed by
12824 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
12825 - Avoid a potential crash on exit nodes when processing malformed
12826 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
12827 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
12828 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
12831 - Fix compilation on systems where time_t is a 64-bit integer.
12832 Patch from Matthias Drochner.
12833 - Don't consider expiring already-closed client connections. Fixes
12834 bug 893. Bugfix on 0.0.2pre20.
12837 Changes in version 0.2.1.12-alpha - 2009-02-08
12838 Tor 0.2.1.12-alpha features several more security-related fixes. You
12839 should upgrade, especially if you run an exit relay (remote crash) or
12840 a directory authority (remote infinite loop), or you're on an older
12841 (pre-XP) or not-recently-patched Windows (remote exploit). It also
12842 includes a big pile of minor bugfixes and cleanups.
12845 - Fix an infinite-loop bug on handling corrupt votes under certain
12846 circumstances. Bugfix on 0.2.0.8-alpha.
12847 - Fix a temporary DoS vulnerability that could be performed by
12848 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
12849 - Avoid a potential crash on exit nodes when processing malformed
12850 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
12853 - Let controllers actually ask for the "clients_seen" event for
12854 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
12855 reported by Matt Edman.
12856 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
12858 - Fix a bug in address parsing that was preventing bridges or hidden
12859 service targets from being at IPv6 addresses.
12860 - Solve a bug that kept hardware crypto acceleration from getting
12861 enabled when accounting was turned on. Fixes bug 907. Bugfix on
12863 - Remove a bash-ism from configure.in to build properly on non-Linux
12864 platforms. Bugfix on 0.2.1.1-alpha.
12865 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
12866 headers. Bugfix on 0.2.0.10-alpha.
12867 - Don't consider expiring already-closed client connections. Fixes
12868 bug 893. Bugfix on 0.0.2pre20.
12869 - Fix another interesting corner-case of bug 891 spotted by rovv:
12870 Previously, if two hosts had different amounts of clock drift, and
12871 one of them created a new connection with just the wrong timing,
12872 the other might decide to deprecate the new connection erroneously.
12873 Bugfix on 0.1.1.13-alpha.
12874 - Resolve a very rare crash bug that could occur when the user forced
12875 a nameserver reconfiguration during the middle of a nameserver
12876 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
12877 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
12878 Bugfix on 0.2.1.7-alpha.
12879 - If we're using bridges and our network goes away, be more willing
12880 to forgive our bridges and try again when we get an application
12881 request. Bugfix on 0.2.0.x.
12884 - Support platforms where time_t is 64 bits long. (Congratulations,
12885 NetBSD!) Patch from Matthias Drochner.
12886 - Add a 'getinfo status/clients-seen' controller command, in case
12887 controllers want to hear clients_seen events but connect late.
12890 - Disable GCC's strict alias optimization by default, to avoid the
12891 likelihood of its introducing subtle bugs whenever our code violates
12892 the letter of C99's alias rules.
12895 Changes in version 0.2.0.33 - 2009-01-21
12896 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
12897 useful to users. It also finally fixes a bug where a relay or client
12898 that's been off for many days would take a long time to bootstrap.
12900 This update also fixes an important security-related bug reported by
12901 Ilja van Sprundel. You should upgrade. (We'll send out more details
12902 about the bug once people have had some time to upgrade.)
12905 - Fix a heap-corruption bug that may be remotely triggerable on
12906 some platforms. Reported by Ilja van Sprundel.
12909 - When a stream at an exit relay is in state "resolving" or
12910 "connecting" and it receives an "end" relay cell, the exit relay
12911 would silently ignore the end cell and not close the stream. If
12912 the client never closes the circuit, then the exit relay never
12913 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
12914 reported by "wood".
12915 - When sending CREATED cells back for a given circuit, use a 64-bit
12916 connection ID to find the right connection, rather than an addr:port
12917 combination. Now that we can have multiple OR connections between
12918 the same ORs, it is no longer possible to use addr:port to uniquely
12919 identify a connection.
12920 - Bridge relays that had DirPort set to 0 would stop fetching
12921 descriptors shortly after startup, and then briefly resume
12922 after a new bandwidth test and/or after publishing a new bridge
12923 descriptor. Bridge users that try to bootstrap from them would
12924 get a recent networkstatus but would get descriptors from up to
12925 18 hours earlier, meaning most of the descriptors were obsolete
12926 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12927 - Prevent bridge relays from serving their 'extrainfo' document
12928 to anybody who asks, now that extrainfo docs include potentially
12929 sensitive aggregated client geoip summaries. Bugfix on
12931 - If the cached networkstatus consensus is more than five days old,
12932 discard it rather than trying to use it. In theory it could be
12933 useful because it lists alternate directory mirrors, but in practice
12934 it just means we spend many minutes trying directory mirrors that
12935 are long gone from the network. Also discard router descriptors as
12936 we load them if they are more than five days old, since the onion
12937 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
12940 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
12941 could make gcc generate non-functional binary search code. Bugfix
12943 - Build correctly on platforms without socklen_t.
12944 - Compile without warnings on solaris.
12945 - Avoid potential crash on internal error during signature collection.
12946 Fixes bug 864. Patch from rovv.
12947 - Correct handling of possible malformed authority signing key
12948 certificates with internal signature types. Fixes bug 880.
12949 Bugfix on 0.2.0.3-alpha.
12950 - Fix a hard-to-trigger resource leak when logging credential status.
12952 - When we can't initialize DNS because the network is down, do not
12953 automatically stop Tor from starting. Instead, we retry failed
12954 dns_init() every 10 minutes, and change the exit policy to reject
12955 *:* until one succeeds. Fixes bug 691.
12956 - Use 64 bits instead of 32 bits for connection identifiers used with
12957 the controller protocol, to greatly reduce risk of identifier reuse.
12958 - When we're choosing an exit node for a circuit, and we have
12959 no pending streams, choose a good general exit rather than one that
12960 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12961 - Fix another case of assuming, when a specific exit is requested,
12962 that we know more than the user about what hosts it allows.
12963 Fixes one case of bug 752. Patch from rovv.
12964 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12965 seconds. Warn the user if lower values are given in the
12966 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12967 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12968 user if lower values are given in the configuration. Bugfix on
12969 0.1.1.17-rc. Patch by Sebastian.
12970 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
12971 the cache because we already had a v0 descriptor with the same ID.
12972 Bugfix on 0.2.0.18-alpha.
12973 - Fix a race condition when freeing keys shared between main thread
12974 and CPU workers that could result in a memory leak. Bugfix on
12975 0.1.0.1-rc. Fixes bug 889.
12976 - Send a valid END cell back when a client tries to connect to a
12977 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12978 840. Patch from rovv.
12979 - Check which hops rendezvous stream cells are associated with to
12980 prevent possible guess-the-streamid injection attacks from
12981 intermediate hops. Fixes another case of bug 446. Based on patch
12983 - If a broken client asks a non-exit router to connect somewhere,
12984 do not even do the DNS lookup before rejecting the connection.
12985 Fixes another case of bug 619. Patch from rovv.
12986 - When a relay gets a create cell it can't decrypt (e.g. because it's
12987 using the wrong onion key), we were dropping it and letting the
12988 client time out. Now actually answer with a destroy cell. Fixes
12989 bug 904. Bugfix on 0.0.2pre8.
12991 o Minor bugfixes (hidden services):
12992 - Do not throw away existing introduction points on SIGHUP. Bugfix on
12993 0.0.6pre1. Patch by Karsten. Fixes bug 874.
12996 - Report the case where all signatures in a detached set are rejected
12997 differently than the case where there is an error handling the
12999 - When we realize that another process has modified our cached
13000 descriptors, print out a more useful error message rather than
13001 triggering an assertion. Fixes bug 885. Patch from Karsten.
13002 - Implement the 0x20 hack to better resist DNS poisoning: set the
13003 case on outgoing DNS requests randomly, and reject responses that do
13004 not match the case correctly. This logic can be disabled with the
13005 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
13006 of servers that do not reliably preserve case in replies. See
13007 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
13009 - Check DNS replies for more matching fields to better resist DNS
13011 - Never use OpenSSL compression: it wastes RAM and CPU trying to
13012 compress cells, which are basically all encrypted, compressed, or
13016 Changes in version 0.2.1.11-alpha - 2009-01-20
13017 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
13018 week it will take a long time to bootstrap again" bug. It also fixes
13019 an important security-related bug reported by Ilja van Sprundel. You
13020 should upgrade. (We'll send out more details about the bug once people
13021 have had some time to upgrade.)
13024 - Fix a heap-corruption bug that may be remotely triggerable on
13025 some platforms. Reported by Ilja van Sprundel.
13028 - Discard router descriptors as we load them if they are more than
13029 five days old. Otherwise if Tor is off for a long time and then
13030 starts with cached descriptors, it will try to use the onion
13031 keys in those obsolete descriptors when building circuits. Bugfix
13032 on 0.2.0.x. Fixes bug 887.
13035 - Try to make sure that the version of Libevent we're running with
13036 is binary-compatible with the one we built with. May address bug
13038 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
13039 for bug 905. Bugfix on 0.2.1.7-alpha.
13040 - Add a new --enable-local-appdata configuration switch to change
13041 the default location of the datadir on win32 from APPDATA to
13042 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
13043 entirely. Patch from coderman.
13046 - Make outbound DNS packets respect the OutboundBindAddress setting.
13047 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
13048 - When our circuit fails at the first hop (e.g. we get a destroy
13049 cell back), avoid using that OR connection anymore, and also
13050 tell all the one-hop directory requests waiting for it that they
13051 should fail. Bugfix on 0.2.1.3-alpha.
13052 - In the torify(1) manpage, mention that tsocks will leak your
13056 Changes in version 0.2.1.10-alpha - 2009-01-06
13057 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
13058 would make the bridge relay not so useful if it had DirPort set to 0,
13059 and one that could let an attacker learn a little bit of information
13060 about the bridge's users), and a bug that would cause your Tor relay
13061 to ignore a circuit create request it can't decrypt (rather than reply
13062 with an error). It also fixes a wide variety of other bugs.
13065 - If the cached networkstatus consensus is more than five days old,
13066 discard it rather than trying to use it. In theory it could
13067 be useful because it lists alternate directory mirrors, but in
13068 practice it just means we spend many minutes trying directory
13069 mirrors that are long gone from the network. Helps bug 887 a bit;
13071 - Bridge relays that had DirPort set to 0 would stop fetching
13072 descriptors shortly after startup, and then briefly resume
13073 after a new bandwidth test and/or after publishing a new bridge
13074 descriptor. Bridge users that try to bootstrap from them would
13075 get a recent networkstatus but would get descriptors from up to
13076 18 hours earlier, meaning most of the descriptors were obsolete
13077 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
13078 - Prevent bridge relays from serving their 'extrainfo' document
13079 to anybody who asks, now that extrainfo docs include potentially
13080 sensitive aggregated client geoip summaries. Bugfix on
13084 - New controller event "clients_seen" to report a geoip-based summary
13085 of which countries we've seen clients from recently. Now controllers
13086 like Vidalia can show bridge operators that they're actually making
13088 - Build correctly against versions of OpenSSL 0.9.8 or later built
13089 without support for deprecated functions.
13090 - Update to the "December 19 2008" ip-to-country file.
13092 o Minor bugfixes (on 0.2.0.x):
13093 - Authorities now vote for the Stable flag for any router whose
13094 weighted MTBF is at least 5 days, regardless of the mean MTBF.
13095 - Do not remove routers as too old if we do not have any consensus
13096 document. Bugfix on 0.2.0.7-alpha.
13097 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
13098 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
13099 - When an exit relay resolves a stream address to a local IP address,
13100 do not just keep retrying that same exit relay over and
13101 over. Instead, just close the stream. Addresses bug 872. Bugfix
13102 on 0.2.0.32. Patch from rovv.
13103 - If a hidden service sends us an END cell, do not consider
13104 retrying the connection; just close it. Patch from rovv.
13105 - When we made bridge authorities stop serving bridge descriptors over
13106 unencrypted links, we also broke DirPort reachability testing for
13107 bridges. So bridges with a non-zero DirPort were printing spurious
13108 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
13109 - When a relay gets a create cell it can't decrypt (e.g. because it's
13110 using the wrong onion key), we were dropping it and letting the
13111 client time out. Now actually answer with a destroy cell. Fixes
13112 bug 904. Bugfix on 0.0.2pre8.
13113 - Squeeze 2-5% out of client performance (according to oprofile) by
13114 improving the implementation of some policy-manipulation functions.
13116 o Minor bugfixes (on 0.2.1.x):
13117 - Make get_interface_address() function work properly again; stop
13118 guessing the wrong parts of our address as our address.
13119 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
13120 send on that circuit. Otherwise we might violate the proposal-110
13121 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
13123 - When we're sending non-EXTEND cells to the first hop in a circuit,
13124 for example to use an encrypted directory connection, we don't need
13125 to use RELAY_EARLY cells: the first hop knows what kind of cell
13126 it is, and nobody else can even see the cell type. Conserving
13127 RELAY_EARLY cells makes it easier to cannibalize circuits like
13129 - Stop logging nameserver addresses in reverse order.
13130 - If we are retrying a directory download slowly over and over, do
13131 not automatically give up after the 254th failure. Bugfix on
13133 - Resume reporting accurate "stream end" reasons to the local control
13134 port. They were lost in the changes for Proposal 148. Bugfix on
13137 o Deprecated and removed features:
13138 - The old "tor --version --version" command, which would print out
13139 the subversion "Id" of most of the source files, is now removed. It
13140 turned out to be less useful than we'd expected, and harder to
13143 o Code simplifications and refactoring:
13144 - Change our header file guard macros to be less likely to conflict
13145 with system headers. Adam Langley noticed that we were conflicting
13146 with log.h on Android.
13147 - Tool-assisted documentation cleanup. Nearly every function or
13148 static variable in Tor should have its own documentation now.
13151 Changes in version 0.2.1.9-alpha - 2008-12-25
13152 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
13154 o New directory authorities:
13155 - gabelmoo (the authority run by Karsten Loesing) now has a new
13159 - Never use a connection with a mismatched address to extend a
13160 circuit, unless that connection is canonical. A canonical
13161 connection is one whose address is authenticated by the router's
13162 identity key, either in a NETINFO cell or in a router descriptor.
13163 - Avoid a possible memory corruption bug when receiving hidden service
13164 descriptors. Bugfix on 0.2.1.6-alpha.
13167 - Fix a logic error that would automatically reject all but the first
13168 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
13169 part of bug 813/868. Bug spotted by coderman.
13170 - When a stream at an exit relay is in state "resolving" or
13171 "connecting" and it receives an "end" relay cell, the exit relay
13172 would silently ignore the end cell and not close the stream. If
13173 the client never closes the circuit, then the exit relay never
13174 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
13175 reported by "wood".
13176 - When we can't initialize DNS because the network is down, do not
13177 automatically stop Tor from starting. Instead, retry failed
13178 dns_init() every 10 minutes, and change the exit policy to reject
13179 *:* until one succeeds. Fixes bug 691.
13182 - Give a better error message when an overzealous init script says
13183 "sudo -u username tor --user username". Makes Bug 882 easier for
13185 - When a directory authority gives us a new guess for our IP address,
13186 log which authority we used. Hopefully this will help us debug
13187 the recent complaints about bad IP address guesses.
13188 - Detect svn revision properly when we're using git-svn.
13189 - Try not to open more than one descriptor-downloading connection
13190 to an authority at once. This should reduce load on directory
13191 authorities. Fixes bug 366.
13192 - Add cross-certification to newly generated certificates, so that
13193 a signing key is enough information to look up a certificate.
13194 Partial implementation of proposal 157.
13195 - Start serving certificates by <identity digest, signing key digest>
13196 pairs. Partial implementation of proposal 157.
13197 - Clients now never report any stream end reason except 'MISC'.
13198 Implements proposal 148.
13199 - On platforms with a maximum syslog string length, truncate syslog
13200 messages to that length ourselves, rather than relying on the
13201 system to do it for us.
13202 - Optimize out calls to time(NULL) that occur for every IO operation,
13203 or for every cell. On systems where time() is a slow syscall,
13204 this fix will be slightly helpful.
13205 - Exit servers can now answer resolve requests for ip6.arpa addresses.
13206 - When we download a descriptor that we then immediately (as
13207 a directory authority) reject, do not retry downloading it right
13208 away. Should save some bandwidth on authorities. Fix for bug
13209 888. Patch by Sebastian Hahn.
13210 - When a download gets us zero good descriptors, do not notify
13211 Tor that new directory information has arrived.
13212 - Avoid some nasty corner cases in the logic for marking connections
13213 as too old or obsolete or noncanonical for circuits. Partial
13216 o Minor features (controller):
13217 - New CONSENSUS_ARRIVED event to note when a new consensus has
13218 been fetched and validated.
13219 - When we realize that another process has modified our cached
13220 descriptors file, print out a more useful error message rather
13221 than triggering an assertion. Fixes bug 885. Patch from Karsten.
13222 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
13223 controllers to prevent SIGHUP from reloading the
13224 configuration. Fixes bug 856.
13227 - Resume using the correct "REASON=" stream when telling the
13228 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
13229 - When a canonical connection appears later in our internal list
13230 than a noncanonical one for a given OR ID, always use the
13231 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
13233 - Clip the MaxCircuitDirtiness config option to a minimum of 10
13234 seconds. Warn the user if lower values are given in the
13235 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
13236 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
13237 user if lower values are given in the configuration. Bugfix on
13238 0.1.1.17-rc. Patch by Sebastian.
13239 - Fix a race condition when freeing keys shared between main thread
13240 and CPU workers that could result in a memory leak. Bugfix on
13241 0.1.0.1-rc. Fixes bug 889.
13243 o Minor bugfixes (hidden services):
13244 - Do not throw away existing introduction points on SIGHUP (bugfix on
13245 0.0.6pre1); also, do not stall hidden services because we're
13246 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
13247 by John Brooks. Patch by Karsten. Fixes bug 874.
13248 - Fix a memory leak when we decline to add a v2 rendezvous
13249 descriptor to the cache because we already had a v0 descriptor
13250 with the same ID. Bugfix on 0.2.0.18-alpha.
13252 o Deprecated and removed features:
13253 - RedirectExits has been removed. It was deprecated since
13255 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
13256 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
13257 - Cell pools are now always enabled; --disable-cell-pools is ignored.
13259 o Code simplifications and refactoring:
13260 - Rename the confusing or_is_obsolete field to the more appropriate
13261 is_bad_for_new_circs, and move it to or_connection_t where it
13263 - Move edge-only flags from connection_t to edge_connection_t: not
13264 only is this better coding, but on machines of plausible alignment,
13265 it should save 4-8 bytes per connection_t. "Every little bit helps."
13266 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
13267 for consistency; keep old option working for backward compatibility.
13268 - Simplify the code for finding connections to use for a circuit.
13271 Changes in version 0.2.1.8-alpha - 2008-12-08
13272 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
13273 builds better on unusual platforms like Solaris and old OS X, and
13274 fixes a variety of other issues.
13277 - New DirPortFrontPage option that takes an html file and publishes
13278 it as "/" on the DirPort. Now relay operators can provide a
13279 disclaimer without needing to set up a separate webserver. There's
13280 a sample disclaimer in contrib/tor-exit-notice.html.
13283 - When the client is choosing entry guards, now it selects at most
13284 one guard from a given relay family. Otherwise we could end up with
13285 all of our entry points into the network run by the same operator.
13286 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
13289 - Fix a DOS opportunity during the voting signature collection process
13290 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
13291 - Fix a possible segfault when establishing an exit connection. Bugfix
13295 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
13297 - Made Tor a little less aggressive about deleting expired
13298 certificates. Partial fix for bug 854.
13299 - Stop doing unaligned memory access that generated bus errors on
13300 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
13301 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
13302 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
13303 - Make USR2 log-level switch take effect immediately. Bugfix on
13305 - If one win32 nameserver fails to get added, continue adding the
13306 rest, and don't automatically fail.
13307 - Use fcntl() for locking when flock() is not available. Should fix
13308 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
13309 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
13310 could make gcc generate non-functional binary search code. Bugfix
13312 - Build correctly on platforms without socklen_t.
13313 - Avoid potential crash on internal error during signature collection.
13314 Fixes bug 864. Patch from rovv.
13315 - Do not use C's stdio library for writing to log files. This will
13316 improve logging performance by a minute amount, and will stop
13317 leaking fds when our disk is full. Fixes bug 861.
13318 - Stop erroneous use of O_APPEND in cases where we did not in fact
13319 want to re-seek to the end of a file before every last write().
13320 - Correct handling of possible malformed authority signing key
13321 certificates with internal signature types. Fixes bug 880. Bugfix
13323 - Fix a hard-to-trigger resource leak when logging credential status.
13327 - Directory mirrors no longer fetch the v1 directory or
13328 running-routers files. They are obsolete, and nobody asks for them
13329 anymore. This is the first step to making v1 authorities obsolete.
13331 o Minor features (controller):
13332 - Return circuit purposes in response to GETINFO circuit-status. Fixes
13336 Changes in version 0.2.0.32 - 2008-11-20
13337 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
13338 packages (and maybe other packages) noticed by Theo de Raadt, fixes
13339 a smaller security flaw that might allow an attacker to access local
13340 services, further improves hidden service performance, and fixes a
13341 variety of other issues.
13344 - The "User" and "Group" config options did not clear the
13345 supplementary group entries for the Tor process. The "User" option
13346 is now more robust, and we now set the groups to the specified
13347 user's primary group. The "Group" option is now ignored. For more
13348 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
13349 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
13350 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
13351 - The "ClientDNSRejectInternalAddresses" config option wasn't being
13352 consistently obeyed: if an exit relay refuses a stream because its
13353 exit policy doesn't allow it, we would remember what IP address
13354 the relay said the destination address resolves to, even if it's
13355 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
13358 - Fix a DOS opportunity during the voting signature collection process
13359 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
13361 o Major bugfixes (hidden services):
13362 - When fetching v0 and v2 rendezvous service descriptors in parallel,
13363 we were failing the whole hidden service request when the v0
13364 descriptor fetch fails, even if the v2 fetch is still pending and
13365 might succeed. Similarly, if the last v2 fetch fails, we were
13366 failing the whole hidden service request even if a v0 fetch is
13367 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
13368 - When extending a circuit to a hidden service directory to upload a
13369 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
13370 requests failed, because the router descriptor has not been
13371 downloaded yet. In these cases, do not attempt to upload the
13372 rendezvous descriptor, but wait until the router descriptor is
13373 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
13374 descriptor from a hidden service directory for which the router
13375 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
13379 - Fix several infrequent memory leaks spotted by Coverity.
13380 - When testing for libevent functions, set the LDFLAGS variable
13381 correctly. Found by Riastradh.
13382 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13383 bootstrapping with tunneled directory connections. Bugfix on
13384 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13385 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13386 and we know that server B rejects most-but-not all connections to
13387 port 80, we would previously reject the connection. Now, we assume
13388 the user knows what they were asking for. Fixes bug 752. Bugfix
13389 on 0.0.9rc5. Diagnosed by BarkerJr.
13390 - If we overrun our per-second write limits a little, count this as
13391 having used up our write allocation for the second, and choke
13392 outgoing directory writes. Previously, we had only counted this when
13393 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
13394 Bugfix on 0.2.0.x (??).
13395 - Remove the old v2 directory authority 'lefkada' from the default
13396 list. It has been gone for many months.
13397 - Stop doing unaligned memory access that generated bus errors on
13398 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
13399 - Make USR2 log-level switch take effect immediately. Bugfix on
13402 o Minor bugfixes (controller):
13403 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
13404 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
13407 Changes in version 0.2.1.7-alpha - 2008-11-08
13408 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
13409 packages (and maybe other packages) noticed by Theo de Raadt, fixes
13410 a smaller security flaw that might allow an attacker to access local
13411 services, adds better defense against DNS poisoning attacks on exit
13412 relays, further improves hidden service performance, and fixes a
13413 variety of other issues.
13416 - The "ClientDNSRejectInternalAddresses" config option wasn't being
13417 consistently obeyed: if an exit relay refuses a stream because its
13418 exit policy doesn't allow it, we would remember what IP address
13419 the relay said the destination address resolves to, even if it's
13420 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
13421 - The "User" and "Group" config options did not clear the
13422 supplementary group entries for the Tor process. The "User" option
13423 is now more robust, and we now set the groups to the specified
13424 user's primary group. The "Group" option is now ignored. For more
13425 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
13426 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
13427 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
13428 - Do not use or believe expired v3 authority certificates. Patch
13429 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
13432 - Now NodeFamily and MyFamily config options allow spaces in
13433 identity fingerprints, so it's easier to paste them in.
13434 Suggested by Lucky Green.
13435 - Implement the 0x20 hack to better resist DNS poisoning: set the
13436 case on outgoing DNS requests randomly, and reject responses that do
13437 not match the case correctly. This logic can be disabled with the
13438 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
13439 of servers that do not reliably preserve case in replies. See
13440 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
13442 - Preserve case in replies to DNSPort requests in order to support
13443 the 0x20 hack for resisting DNS poisoning attacks.
13445 o Hidden service performance improvements:
13446 - When the client launches an introduction circuit, retry with a
13447 new circuit after 30 seconds rather than 60 seconds.
13448 - Launch a second client-side introduction circuit in parallel
13449 after a delay of 15 seconds (based on work by Christian Wilms).
13450 - Hidden services start out building five intro circuits rather
13451 than three, and when the first three finish they publish a service
13452 descriptor using those. Now we publish our service descriptor much
13453 faster after restart.
13456 - Minor fix in the warning messages when you're having problems
13457 bootstrapping; also, be more forgiving of bootstrap problems when
13458 we're still making incremental progress on a given bootstrap phase.
13459 - When we're choosing an exit node for a circuit, and we have
13460 no pending streams, choose a good general exit rather than one that
13461 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
13462 - Send a valid END cell back when a client tries to connect to a
13463 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
13464 840. Patch from rovv.
13465 - If a broken client asks a non-exit router to connect somewhere,
13466 do not even do the DNS lookup before rejecting the connection.
13467 Fixes another case of bug 619. Patch from rovv.
13468 - Fix another case of assuming, when a specific exit is requested,
13469 that we know more than the user about what hosts it allows.
13470 Fixes another case of bug 752. Patch from rovv.
13471 - Check which hops rendezvous stream cells are associated with to
13472 prevent possible guess-the-streamid injection attacks from
13473 intermediate hops. Fixes another case of bug 446. Based on patch
13475 - Avoid using a negative right-shift when comparing 32-bit
13476 addresses. Possible fix for bug 845 and bug 811.
13477 - Make the assert_circuit_ok() function work correctly on circuits that
13478 have already been marked for close.
13479 - Fix read-off-the-end-of-string error in unit tests when decoding
13480 introduction points.
13481 - Fix uninitialized size field for memory area allocation: may improve
13482 memory performance during directory parsing.
13483 - Treat duplicate certificate fetches as failures, so that we do
13484 not try to re-fetch an expired certificate over and over and over.
13485 - Do not say we're fetching a certificate when we'll in fact skip it
13486 because of a pending download.
13489 Changes in version 0.2.1.6-alpha - 2008-09-30
13490 Tor 0.2.1.6-alpha further improves performance and robustness of
13491 hidden services, starts work on supporting per-country relay selection,
13492 and fixes a variety of smaller issues.
13495 - Implement proposal 121: make it possible to build hidden services
13496 that only certain clients are allowed to connect to. This is
13497 enforced at several points, so that unauthorized clients are unable
13498 to send INTRODUCE cells to the service, or even (depending on the
13499 type of authentication) to learn introduction points. This feature
13500 raises the bar for certain kinds of active attacks against hidden
13501 services. Code by Karsten Loesing.
13502 - Relays now store and serve v2 hidden service descriptors by default,
13503 i.e., the new default value for HidServDirectoryV2 is 1. This is
13504 the last step in proposal 114, which aims to make hidden service
13505 lookups more reliable.
13506 - Start work to allow node restrictions to include country codes. The
13507 syntax to exclude nodes in a country with country code XX is
13508 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
13509 refinement to decide what config options should take priority if
13510 you ask to both use a particular node and exclude it.
13511 - Allow ExitNodes list to include IP ranges and country codes, just
13512 like the Exclude*Nodes lists. Patch from Robert Hogan.
13515 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
13516 Tor to fail to start if you had it configured to use a bridge
13517 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
13518 - When extending a circuit to a hidden service directory to upload a
13519 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
13520 requests failed, because the router descriptor had not been
13521 downloaded yet. In these cases, we now wait until the router
13522 descriptor is downloaded, and then retry. Likewise, clients
13523 now skip over a hidden service directory if they don't yet have
13524 its router descriptor, rather than futilely requesting it and
13525 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
13527 - When fetching v0 and v2 rendezvous service descriptors in parallel,
13528 we were failing the whole hidden service request when the v0
13529 descriptor fetch fails, even if the v2 fetch is still pending and
13530 might succeed. Similarly, if the last v2 fetch fails, we were
13531 failing the whole hidden service request even if a v0 fetch is
13532 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
13533 - DNS replies need to have names matching their requests, but
13534 these names should be in the questions section, not necessarily
13535 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
13538 - Update to the "September 1 2008" ip-to-country file.
13539 - Allow ports 465 and 587 in the default exit policy again. We had
13540 rejected them in 0.1.0.15, because back in 2005 they were commonly
13541 misconfigured and ended up as spam targets. We hear they are better
13542 locked down these days.
13543 - Use a lockfile to make sure that two Tor processes are not
13544 simultaneously running with the same datadir.
13545 - Serve the latest v3 networkstatus consensus via the control
13546 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
13547 - Better logging about stability/reliability calculations on directory
13549 - Drop the requirement to have an open dir port for storing and
13550 serving v2 hidden service descriptors.
13551 - Directory authorities now serve a /tor/dbg-stability.txt URL to
13552 help debug WFU and MTBF calculations.
13553 - Implement most of Proposal 152: allow specialized servers to permit
13554 single-hop circuits, and clients to use those servers to build
13555 single-hop circuits when using a specialized controller. Patch
13556 from Josh Albrecht. Resolves feature request 768.
13557 - Add a -p option to tor-resolve for specifying the SOCKS port: some
13558 people find host:port too confusing.
13559 - Make TrackHostExit mappings expire a while after their last use, not
13560 after their creation. Patch from Robert Hogan.
13561 - Provide circuit purposes along with circuit events to the controller.
13564 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
13566 - Fixed some memory leaks -- some quite frequent, some almost
13567 impossible to trigger -- based on results from Coverity.
13568 - When testing for libevent functions, set the LDFLAGS variable
13569 correctly. Found by Riastradh.
13570 - Fix an assertion bug in parsing policy-related options; possible fix
13572 - Catch and report a few more bootstrapping failure cases when Tor
13573 fails to establish a TCP connection. Cleanup on 0.2.1.x.
13574 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13575 bootstrapping with tunneled directory connections. Bugfix on
13576 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13577 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13578 and we know that server B rejects most-but-not all connections to
13579 port 80, we would previously reject the connection. Now, we assume
13580 the user knows what they were asking for. Fixes bug 752. Bugfix
13581 on 0.0.9rc5. Diagnosed by BarkerJr.
13582 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
13583 service directories if they have no advertised dir port. Bugfix
13585 - If we overrun our per-second write limits a little, count this as
13586 having used up our write allocation for the second, and choke
13587 outgoing directory writes. Previously, we had only counted this when
13588 we had met our limits precisely. Fixes bug 824. Patch by rovv.
13589 Bugfix on 0.2.0.x (??).
13590 - Avoid a "0 divided by 0" calculation when calculating router uptime
13591 at directory authorities. Bugfix on 0.2.0.8-alpha.
13592 - Make DNS resolved controller events into "CLOSED", not
13593 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
13595 - Fix a bug where an unreachable relay would establish enough
13596 reachability testing circuits to do a bandwidth test -- if
13597 we already have a connection to the middle hop of the testing
13598 circuit, then it could establish the last hop by using the existing
13599 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
13600 circuits no longer use entry guards in 0.2.1.3-alpha.
13601 - If we have correct permissions on $datadir, we complain to stdout
13602 and fail to start. But dangerous permissions on
13603 $datadir/cached-status/ would cause us to open a log and complain
13604 there. Now complain to stdout and fail to start in both cases. Fixes
13605 bug 820, reported by seeess.
13606 - Remove the old v2 directory authority 'lefkada' from the default
13607 list. It has been gone for many months.
13609 o Code simplifications and refactoring:
13610 - Revise the connection_new functions so that a more typesafe variant
13611 exists. This will work better with Coverity, and let us find any
13612 actual mistakes we're making here.
13613 - Refactor unit testing logic so that dmalloc can be used sensibly
13614 with unit tests to check for memory leaks.
13615 - Move all hidden-service related fields from connection and circuit
13616 structure to substructures: this way they won't eat so much memory.
13619 Changes in version 0.2.0.31 - 2008-09-03
13620 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
13621 a big bug we're seeing where in rare cases traffic from one Tor stream
13622 gets mixed into another stream, and fixes a variety of smaller issues.
13625 - Make sure that two circuits can never exist on the same connection
13626 with the same circuit ID, even if one is marked for close. This
13627 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
13628 - Relays now reject risky extend cells: if the extend cell includes
13629 a digest of all zeroes, or asks to extend back to the relay that
13630 sent the extend cell, tear down the circuit. Ideas suggested
13632 - If not enough of our entry guards are available so we add a new
13633 one, we might use the new one even if it overlapped with the
13634 current circuit's exit relay (or its family). Anonymity bugfix
13635 pointed out by rovv.
13638 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
13639 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
13640 - Correctly detect the presence of the linux/netfilter_ipv4.h header
13641 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
13642 - Pick size of default geoip filename string correctly on windows.
13643 Fixes bug 806. Bugfix on 0.2.0.30.
13644 - Make the autoconf script accept the obsolete --with-ssl-dir
13645 option as an alias for the actually-working --with-openssl-dir
13646 option. Fix the help documentation to recommend --with-openssl-dir.
13647 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
13648 - When using the TransPort option on OpenBSD, and using the User
13649 option to change UID and drop privileges, make sure to open
13650 /dev/pf before dropping privileges. Fixes bug 782. Patch from
13651 Christopher Davis. Bugfix on 0.1.2.1-alpha.
13652 - Try to attach connections immediately upon receiving a RENDEZVOUS2
13653 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
13654 on the client side when connecting to a hidden service. Bugfix
13655 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
13656 - When closing an application-side connection because its circuit is
13657 getting torn down, generate the stream event correctly. Bugfix on
13658 0.1.2.x. Anonymous patch.
13661 Changes in version 0.2.1.5-alpha - 2008-08-31
13662 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
13663 in a lot of the infrastructure for adding authorization to hidden
13664 services, lays the groundwork for having clients read their load
13665 balancing information out of the networkstatus consensus rather than
13666 the individual router descriptors, addresses two potential anonymity
13667 issues, and fixes a variety of smaller issues.
13670 - Convert many internal address representations to optionally hold
13672 - Generate and accept IPv6 addresses in many protocol elements.
13673 - Make resolver code handle nameservers located at ipv6 addresses.
13674 - Begin implementation of proposal 121 ("Client authorization for
13675 hidden services"): configure hidden services with client
13676 authorization, publish descriptors for them, and configure
13677 authorization data for hidden services at clients. The next
13678 step is to actually access hidden services that perform client
13680 - More progress toward proposal 141: Network status consensus
13681 documents and votes now contain bandwidth information for each
13682 router and a summary of that router's exit policy. Eventually this
13683 will be used by clients so that they do not have to download every
13684 known descriptor before building circuits.
13686 o Major bugfixes (on 0.2.0.x and before):
13687 - When sending CREATED cells back for a given circuit, use a 64-bit
13688 connection ID to find the right connection, rather than an addr:port
13689 combination. Now that we can have multiple OR connections between
13690 the same ORs, it is no longer possible to use addr:port to uniquely
13691 identify a connection.
13692 - Relays now reject risky extend cells: if the extend cell includes
13693 a digest of all zeroes, or asks to extend back to the relay that
13694 sent the extend cell, tear down the circuit. Ideas suggested
13696 - If not enough of our entry guards are available so we add a new
13697 one, we might use the new one even if it overlapped with the
13698 current circuit's exit relay (or its family). Anonymity bugfix
13699 pointed out by rovv.
13702 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
13703 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
13704 - When using the TransPort option on OpenBSD, and using the User
13705 option to change UID and drop privileges, make sure to open /dev/pf
13706 before dropping privileges. Fixes bug 782. Patch from Christopher
13707 Davis. Bugfix on 0.1.2.1-alpha.
13708 - Correctly detect the presence of the linux/netfilter_ipv4.h header
13709 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
13710 - Add a missing safe_str() call for a debug log message.
13711 - Use 64 bits instead of 32 bits for connection identifiers used with
13712 the controller protocol, to greatly reduce risk of identifier reuse.
13713 - Make the autoconf script accept the obsolete --with-ssl-dir
13714 option as an alias for the actually-working --with-openssl-dir
13715 option. Fix the help documentation to recommend --with-openssl-dir.
13716 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
13719 - Rate-limit too-many-sockets messages: when they happen, they happen
13720 a lot. Resolves bug 748.
13721 - Resist DNS poisoning a little better by making sure that names in
13722 answer sections match.
13723 - Print the SOCKS5 error message string as well as the error code
13724 when a tor-resolve request fails. Patch from Jacob.
13727 Changes in version 0.2.1.4-alpha - 2008-08-04
13728 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
13731 - The address part of exit policies was not correctly written
13732 to router descriptors. This generated router descriptors that failed
13733 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
13735 - Tor triggered a false assert when extending a circuit to a relay
13736 but we already have a connection open to that relay. Noticed by
13737 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
13740 - Fix a hidden service logging bug: in some edge cases, the router
13741 descriptor of a previously picked introduction point becomes
13742 obsolete and we need to give up on it rather than continually
13743 complaining that it has become obsolete. Observed by xiando. Bugfix
13746 o Removed features:
13747 - Take out the TestVia config option, since it was a workaround for
13748 a bug that was fixed in Tor 0.1.1.21.
13751 Changes in version 0.2.1.3-alpha - 2008-08-03
13752 Tor 0.2.1.3-alpha implements most of the pieces to prevent
13753 infinite-length circuit attacks (see proposal 110); fixes a bug that
13754 might cause exit relays to corrupt streams they send back; allows
13755 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
13756 ExcludeExitNodes config options; and fixes a big pile of bugs.
13758 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
13759 - Send a bootstrap problem "warn" event on the first problem if the
13760 reason is NO_ROUTE (that is, our network is down).
13763 - Implement most of proposal 110: The first K cells to be sent
13764 along a circuit are marked as special "early" cells; only K "early"
13765 cells will be allowed. Once this code is universal, we can block
13766 certain kinds of DOS attack by requiring that EXTEND commands must
13767 be sent using an "early" cell.
13770 - Try to attach connections immediately upon receiving a RENDEZVOUS2
13771 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
13772 on the client side when connecting to a hidden service. Bugfix
13773 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
13774 - Ensure that two circuits can never exist on the same connection
13775 with the same circuit ID, even if one is marked for close. This
13776 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
13779 - When relays do their initial bandwidth measurement, don't limit
13780 to just our entry guards for the test circuits. Otherwise we tend
13781 to have multiple test circuits going through a single entry guard,
13782 which makes our bandwidth test less accurate. Fixes part of bug 654;
13783 patch contributed by Josh Albrecht.
13784 - Add an ExcludeExitNodes option so users can list a set of nodes
13785 that should be be excluded from the exit node position, but
13786 allowed elsewhere. Implements proposal 151.
13787 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
13788 ExcludeNodes and ExcludeExitNodes lists.
13789 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
13790 be more efficient. Formerly it was quadratic in the number of
13791 servers; now it should be linear. Fixes bug 509.
13792 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
13793 and n_conn_id_digest fields into a separate structure that's
13794 only needed when the circuit has not yet attached to an n_conn.
13797 - Change the contrib/tor.logrotate script so it makes the new
13798 logs as "_tor:_tor" rather than the default, which is generally
13799 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
13800 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
13801 warnings (occasionally), but it can also cause the compiler to
13802 eliminate error-checking code. Suggested by Peter Gutmann.
13803 - When a hidden service is giving up on an introduction point candidate
13804 that was not included in the last published rendezvous descriptor,
13805 don't reschedule publication of the next descriptor. Fixes bug 763.
13807 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
13808 HiddenServiceExcludeNodes as obsolete: they never worked properly,
13809 and nobody claims to be using them. Fixes bug 754. Bugfix on
13810 0.1.0.1-rc. Patch from Christian Wilms.
13811 - Fix a small alignment and memory-wasting bug on buffer chunks.
13814 o Minor bugfixes (controller):
13815 - When closing an application-side connection because its circuit
13816 is getting torn down, generate the stream event correctly.
13817 Bugfix on 0.1.2.x. Anonymous patch.
13819 o Removed features:
13820 - Remove all backward-compatibility code to support relays running
13821 versions of Tor so old that they no longer work at all on the
13825 Changes in version 0.2.0.30 - 2008-07-15
13827 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
13828 warnings (occasionally), but it can also cause the compiler to
13829 eliminate error-checking code. Suggested by Peter Gutmann.
13832 Changes in version 0.2.0.29-rc - 2008-07-08
13833 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
13834 hidden-service performance bugs, and fixes a bunch of smaller bugs.
13837 - If you have more than one bridge but don't know their keys,
13838 you would only launch a request for the descriptor of the first one
13839 on your list. (Tor considered launching requests for the others, but
13840 found that it already had a connection on the way for $0000...0000
13841 so it didn't open another.) Bugfix on 0.2.0.x.
13842 - If you have more than one bridge but don't know their keys, and the
13843 connection to one of the bridges failed, you would cancel all
13844 pending bridge connections. (After all, they all have the same
13845 digest.) Bugfix on 0.2.0.x.
13846 - When a hidden service was trying to establish an introduction point,
13847 and Tor had built circuits preemptively for such purposes, we
13848 were ignoring all the preemptive circuits and launching a new one
13849 instead. Bugfix on 0.2.0.14-alpha.
13850 - When a hidden service was trying to establish an introduction point,
13851 and Tor *did* manage to reuse one of the preemptively built
13852 circuits, it didn't correctly remember which one it used,
13853 so it asked for another one soon after, until there were no
13854 more preemptive circuits, at which point it launched one from
13855 scratch. Bugfix on 0.0.9.x.
13856 - Make directory servers include the X-Your-Address-Is: http header in
13857 their responses even for begin_dir conns. Now clients who only
13858 ever use begin_dir connections still have a way to learn their IP
13859 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
13862 - Fix a macro/CPP interaction that was confusing some compilers:
13863 some GCCs don't like #if/#endif pairs inside macro arguments.
13865 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
13866 Fixes bug 704; fix from Steven Murdoch.
13867 - When opening /dev/null in finish_daemonize(), do not pass the
13868 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
13869 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
13870 - Correctly detect transparent proxy support on Linux hosts that
13871 require in.h to be included before netfilter_ipv4.h. Patch
13873 - Disallow session resumption attempts during the renegotiation
13874 stage of the v2 handshake protocol. Clients should never be trying
13875 session resumption at this point, but apparently some did, in
13876 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
13877 found by Geoff Goodell.
13880 Changes in version 0.2.1.2-alpha - 2008-06-20
13881 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
13882 make it easier to set up your own private Tor network; fixes several
13883 big bugs with using more than one bridge relay; fixes a big bug with
13884 offering hidden services quickly after Tor starts; and uses a better
13885 API for reporting potential bootstrapping problems to the controller.
13888 - New TestingTorNetwork config option to allow adjustment of
13889 previously constant values that, while reasonable, could slow
13890 bootstrapping. Implements proposal 135. Patch from Karsten.
13893 - If you have more than one bridge but don't know their digests,
13894 you would only learn a request for the descriptor of the first one
13895 on your list. (Tor considered launching requests for the others, but
13896 found that it already had a connection on the way for $0000...0000
13897 so it didn't open another.) Bugfix on 0.2.0.x.
13898 - If you have more than one bridge but don't know their digests,
13899 and the connection to one of the bridges failed, you would cancel
13900 all pending bridge connections. (After all, they all have the
13901 same digest.) Bugfix on 0.2.0.x.
13902 - When establishing a hidden service, introduction points that
13903 originate from cannibalized circuits are completely ignored and not
13904 included in rendezvous service descriptors. This might be another
13905 reason for delay in making a hidden service available. Bugfix
13906 from long ago (0.0.9.x?)
13909 - Allow OpenSSL to use dynamic locks if it wants.
13910 - When building a consensus, do not include routers that are down.
13911 This will cut down 30% to 40% on consensus size. Implements
13913 - In directory authorities' approved-routers files, allow
13914 fingerprints with or without space.
13915 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
13916 controller can query our current bootstrap state in case it attaches
13917 partway through and wants to catch up.
13918 - Send an initial "Starting" bootstrap status event, so we have a
13919 state to start out in.
13922 - Asking for a conditional consensus at .../consensus/<fingerprints>
13923 would crash a dirserver if it did not already have a
13924 consensus. Bugfix on 0.2.1.1-alpha.
13925 - Clean up some macro/CPP interactions: some GCC versions don't like
13926 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
13929 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
13930 - Directory authorities shouldn't complain about bootstrapping
13931 problems just because they do a lot of reachability testing and
13932 some of the connection attempts fail.
13933 - Start sending "count" and "recommendation" key/value pairs in
13934 bootstrap problem status events, so the controller can hear about
13935 problems even before Tor decides they're worth reporting for sure.
13936 - If you're using bridges, generate "bootstrap problem" warnings
13937 as soon as you run out of working bridges, rather than waiting
13938 for ten failures -- which will never happen if you have less than
13940 - If we close our OR connection because there's been a circuit
13941 pending on it for too long, we were telling our bootstrap status
13942 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
13945 Changes in version 0.2.1.1-alpha - 2008-06-13
13946 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
13947 were making the Tor process bloat especially on Linux; makes our TLS
13948 handshake blend in better; sends "bootstrap phase" status events to
13949 the controller, so it can keep the user informed of progress (and
13950 problems) fetching directory information and establishing circuits;
13951 and adds a variety of smaller features.
13954 - More work on making our TLS handshake blend in: modify the list
13955 of ciphers advertised by OpenSSL in client mode to even more
13956 closely resemble a common web browser. We cheat a little so that
13957 we can advertise ciphers that the locally installed OpenSSL doesn't
13959 - Start sending "bootstrap phase" status events to the controller,
13960 so it can keep the user informed of progress fetching directory
13961 information and establishing circuits. Also inform the controller
13962 if we think we're stuck at a particular bootstrap phase. Implements
13964 - Resume using OpenSSL's RAND_poll() for better (and more portable)
13965 cross-platform entropy collection again. We used to use it, then
13966 stopped using it because of a bug that could crash systems that
13967 called RAND_poll when they had a lot of fds open. It looks like the
13968 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
13969 at startup, and to call RAND_poll() when we reseed later only if
13970 we have a non-buggy OpenSSL version.
13973 - When we choose to abandon a new entry guard because we think our
13974 older ones might be better, close any circuits pending on that
13975 new entry guard connection. This fix should make us recover much
13976 faster when our network is down and then comes back. Bugfix on
13977 0.1.2.8-beta; found by lodger.
13979 o Memory fixes and improvements:
13980 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
13981 to avoid unused RAM in buffer chunks and memory pools.
13982 - Speed up parsing and cut down on memory fragmentation by using
13983 stack-style allocations for parsing directory objects. Previously,
13984 this accounted for over 40% of allocations from within Tor's code
13985 on a typical directory cache.
13986 - Use a Bloom filter rather than a digest-based set to track which
13987 descriptors we need to keep around when we're cleaning out old
13988 router descriptors. This speeds up the computation significantly,
13989 and may reduce fragmentation.
13990 - Reduce the default smartlist size from 32 to 16; it turns out that
13991 most smartlists hold around 8-12 elements tops.
13992 - Make dumpstats() log the fullness and size of openssl-internal
13994 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
13995 patch to their OpenSSL, turn it on to save memory on servers. This
13996 patch will (with any luck) get included in a mainline distribution
13998 - Never use OpenSSL compression: it wastes RAM and CPU trying to
13999 compress cells, which are basically all encrypted, compressed,
14003 - Stop reloading the router list from disk for no reason when we
14004 run out of reachable directory mirrors. Once upon a time reloading
14005 it would set the 'is_running' flag back to 1 for them. It hasn't
14006 done that for a long time.
14007 - In very rare situations new hidden service descriptors were
14008 published earlier than 30 seconds after the last change to the
14009 service. (We currently think that a hidden service descriptor
14010 that's been stable for 30 seconds is worth publishing.)
14013 - Allow separate log levels to be configured for different logging
14014 domains. For example, this allows one to log all notices, warnings,
14015 or errors, plus all memory management messages of level debug or
14016 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
14017 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
14018 and stop using a warning that had become unfixably verbose under
14020 - New --hush command-line option similar to --quiet. While --quiet
14021 disables all logging to the console on startup, --hush limits the
14022 output to messages of warning and error severity.
14023 - Servers support a new URL scheme for consensus downloads that
14024 allows the client to specify which authorities are trusted.
14025 The server then only sends the consensus if the client will trust
14026 it. Otherwise a 404 error is sent back. Clients use this
14027 new scheme when the server supports it (meaning it's running
14028 0.2.1.1-alpha or later). Implements proposal 134.
14029 - New configure/torrc options (--enable-geoip-stats,
14030 DirRecordUsageByCountry) to record how many IPs we've served
14031 directory info to in each country code, how many status documents
14032 total we've sent to each country code, and what share of the total
14033 directory requests we should expect to see.
14034 - Use the TLS1 hostname extension to more closely resemble browser
14036 - Lots of new unit tests.
14037 - Add a macro to implement the common pattern of iterating through
14038 two parallel lists in lockstep.
14041 Changes in version 0.2.0.28-rc - 2008-06-13
14042 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
14043 performance bug, and fixes a bunch of smaller bugs.
14046 - Fix a bug where, when we were choosing the 'end stream reason' to
14047 put in our relay end cell that we send to the exit relay, Tor
14048 clients on Windows were sometimes sending the wrong 'reason'. The
14049 anonymity problem is that exit relays may be able to guess whether
14050 the client is running Windows, thus helping partition the anonymity
14051 set. Down the road we should stop sending reasons to exit relays,
14052 or otherwise prevent future versions of this bug.
14055 - While setting up a hidden service, some valid introduction circuits
14056 were overlooked and abandoned. This might be the reason for
14057 the long delay in making a hidden service available. Bugfix on
14061 - Update to the "June 9 2008" ip-to-country file.
14062 - Run 'make test' as part of 'make dist', so we stop releasing so
14063 many development snapshots that fail their unit tests.
14066 - When we're checking if we have enough dir info for each relay
14067 to begin establishing circuits, make sure that we actually have
14068 the descriptor listed in the consensus, not just any descriptor.
14070 - Bridge relays no longer print "xx=0" in their extrainfo document
14071 for every single country code in the geoip db. Bugfix on
14073 - Only warn when we fail to load the geoip file if we were planning to
14074 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
14075 - If we change our MaxAdvertisedBandwidth and then reload torrc,
14076 Tor won't realize it should publish a new relay descriptor. Fixes
14077 bug 688, reported by mfr. Bugfix on 0.1.2.x.
14078 - When we haven't had any application requests lately, don't bother
14079 logging that we have expired a bunch of descriptors. Bugfix
14081 - Make relay cells written on a connection count as non-padding when
14082 tracking how long a connection has been in use. Bugfix on
14083 0.2.0.1-alpha. Spotted by lodger.
14084 - Fix unit tests in 0.2.0.27-rc.
14085 - Fix compile on Windows.
14088 Changes in version 0.2.0.27-rc - 2008-06-03
14089 Tor 0.2.0.27-rc adds a few features we left out of the earlier
14090 release candidates. In particular, we now include an IP-to-country
14091 GeoIP database, so controllers can easily look up what country a
14092 given relay is in, and so bridge relays can give us some sanitized
14093 summaries about which countries are making use of bridges. (See proposal
14094 126-geoip-fetching.txt for details.)
14097 - Include an IP-to-country GeoIP file in the tarball, so bridge
14098 relays can report sanitized summaries of the usage they're seeing.
14101 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
14102 Robert Hogan. Fixes the first part of bug 681.
14103 - Make bridge authorities never serve extrainfo docs.
14104 - Add support to detect Libevent versions in the 1.4.x series
14106 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
14107 - Include a new contrib/tor-exit-notice.html file that exit relay
14108 operators can put on their website to help reduce abuse queries.
14111 - When tunneling an encrypted directory connection, and its first
14112 circuit fails, do not leave it unattached and ask the controller
14113 to deal. Fixes the second part of bug 681.
14114 - Make bridge authorities correctly expire old extrainfo documents
14118 Changes in version 0.2.0.26-rc - 2008-05-13
14119 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
14120 in Debian's OpenSSL packages. All users running any 0.2.0.x version
14121 should upgrade, whether they're running Debian or not.
14123 o Major security fixes:
14124 - Use new V3 directory authority keys on the tor26, gabelmoo, and
14125 moria1 V3 directory authorities. The old keys were generated with
14126 a vulnerable version of Debian's OpenSSL package, and must be
14127 considered compromised. Other authorities' keys were not generated
14128 with an affected version of OpenSSL.
14131 - List authority signatures as "unrecognized" based on DirServer
14132 lines, not on cert cache. Bugfix on 0.2.0.x.
14135 - Add a new V3AuthUseLegacyKey option to make it easier for
14136 authorities to change their identity keys if they have to.
14139 Changes in version 0.2.0.25-rc - 2008-04-23
14140 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
14143 - Remember to initialize threading before initializing logging.
14144 Otherwise, many BSD-family implementations will crash hard on
14145 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
14148 - Authorities correctly free policies on bad servers on
14149 exit. Fixes bug 672. Bugfix on 0.2.0.x.
14152 Changes in version 0.2.0.24-rc - 2008-04-22
14153 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
14154 v3 directory authority, makes relays with dynamic IP addresses and no
14155 DirPort notice more quickly when their IP address changes, fixes a few
14156 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
14158 o New directory authorities:
14159 - Take lefkada out of the list of v3 directory authorities, since
14160 it has been down for months.
14161 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
14165 - Detect address changes more quickly on non-directory mirror
14166 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
14168 o Minor features (security):
14169 - Reject requests for reverse-dns lookup of names that are in
14170 a private address space. Patch from lodger.
14171 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
14174 o Minor bugfixes (crashes):
14175 - Avoid a rare assert that can trigger when Tor doesn't have much
14176 directory information yet and it tries to fetch a v2 hidden
14177 service descriptor. Fixes bug 651, reported by nwf.
14178 - Initialize log mutex before initializing dmalloc. Otherwise,
14179 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
14180 - Use recursive pthread mutexes in order to avoid deadlock when
14181 logging debug-level messages to a controller. Bug spotted by nwf,
14182 bugfix on 0.2.0.16-alpha.
14184 o Minor bugfixes (resource management):
14185 - Keep address policies from leaking memory: start their refcount
14186 at 1, not 2. Bugfix on 0.2.0.16-alpha.
14187 - Free authority certificates on exit, so they don't look like memory
14188 leaks. Bugfix on 0.2.0.19-alpha.
14189 - Free static hashtables for policy maps and for TLS connections on
14190 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
14191 - Avoid allocating extra space when computing consensuses on 64-bit
14192 platforms. Bug spotted by aakova.
14194 o Minor bugfixes (misc):
14195 - Do not read the configuration file when we've only been told to
14196 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
14197 based on patch from Sebastian Hahn.
14198 - Exit relays that are used as a client can now reach themselves
14199 using the .exit notation, rather than just launching an infinite
14200 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
14201 - When attempting to open a logfile fails, tell us why.
14202 - Fix a dumb bug that was preventing us from knowing that we should
14203 preemptively build circuits to handle expected directory requests.
14204 Fixes bug 660. Bugfix on 0.1.2.x.
14205 - Warn less verbosely about clock skew from netinfo cells from
14206 untrusted sources. Fixes bug 663.
14207 - Make controller stream events for DNS requests more consistent,
14208 by adding "new stream" events for DNS requests, and removing
14209 spurious "stream closed" events" for cached reverse resolves.
14210 Patch from mwenge. Fixes bug 646.
14211 - Correctly notify one-hop connections when a circuit build has
14212 failed. Possible fix for bug 669. Found by lodger.
14215 Changes in version 0.2.0.23-rc - 2008-03-24
14216 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
14217 makes bootstrapping faster if the first directory mirror you contact
14218 is down. The bundles also include the new Vidalia 0.1.2 release.
14221 - When a tunneled directory request is made to a directory server
14222 that's down, notice after 30 seconds rather than 120 seconds. Also,
14223 fail any begindir streams that are pending on it, so they can
14224 retry elsewhere. This was causing multi-minute delays on bootstrap.
14227 Changes in version 0.2.0.22-rc - 2008-03-18
14228 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
14229 enables encrypted directory connections by default for non-relays, fixes
14230 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
14231 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
14234 - Enable encrypted directory connections by default for non-relays,
14235 so censor tools that block Tor directory connections based on their
14236 plaintext patterns will no longer work. This means Tor works in
14237 certain censored countries by default again.
14240 - Make sure servers always request certificates from clients during
14241 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
14242 - Do not enter a CPU-eating loop when a connection is closed in
14243 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
14244 diagnosed by lodger; bugfix on 0.2.0.20-rc.
14245 - Fix assertion failure that could occur when a blocked circuit
14246 became unblocked, and it had pending client DNS requests. Bugfix
14247 on 0.2.0.1-alpha. Fixes bug 632.
14249 o Minor bugfixes (on 0.1.2.x):
14250 - Generate "STATUS_SERVER" events rather than misspelled
14251 "STATUS_SEVER" events. Caught by mwenge.
14252 - When counting the number of bytes written on a TLS connection,
14253 look at the BIO actually used for writing to the network, not
14254 at the BIO used (sometimes) to buffer data for the network.
14255 Looking at different BIOs could result in write counts on the
14256 order of ULONG_MAX. Fixes bug 614.
14257 - On Windows, correctly detect errors when listing the contents of
14258 a directory. Fix from lodger.
14260 o Minor bugfixes (on 0.2.0.x):
14261 - Downgrade "sslv3 alert handshake failure" message to INFO.
14262 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
14263 left BandwidthRate and BandwidthBurst at the default, we would be
14264 silently limited by those defaults. Now raise them to match the
14265 RelayBandwidth* values.
14266 - Fix the SVK version detection logic to work correctly on a branch.
14267 - Make --enable-openbsd-malloc work correctly on Linux with alpha
14268 CPUs. Fixes bug 625.
14269 - Logging functions now check that the passed severity is sane.
14270 - Use proper log levels in the testsuite call of
14271 get_interface_address6().
14272 - When using a nonstandard malloc, do not use the platform values for
14273 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
14274 - Make the openbsd malloc code use 8k pages on alpha CPUs and
14276 - Detect mismatched page sizes when using --enable-openbsd-malloc.
14277 - Avoid double-marked-for-close warning when certain kinds of invalid
14278 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
14279 for bug 617. Bugfix on 0.2.0.1-alpha.
14280 - Make sure that the "NULL-means-reject *:*" convention is followed by
14281 all the policy manipulation functions, avoiding some possible crash
14282 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
14283 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
14284 actually works, and doesn't warn about every single reverse lookup.
14285 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
14288 - Only log guard node status when guard node status has changed.
14289 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
14290 make "INFO" 75% less verbose.
14293 Changes in version 0.2.0.21-rc - 2008-03-02
14294 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
14295 makes Tor work well with Vidalia again, fixes a rare assert bug,
14296 and fixes a pair of more minor bugs. The bundles also include Vidalia
14297 0.1.0 and Torbutton 1.1.16.
14300 - The control port should declare that it requires password auth
14301 when HashedControlSessionPassword is set too. Patch from Matt Edman;
14302 bugfix on 0.2.0.20-rc. Fixes bug 615.
14303 - Downgrade assert in connection_buckets_decrement() to a log message.
14304 This may help us solve bug 614, and in any case will make its
14305 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
14306 - We were sometimes miscounting the number of bytes read from the
14307 network, causing our rate limiting to not be followed exactly.
14308 Bugfix on 0.2.0.16-alpha. Reported by lodger.
14311 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
14312 OpenSSL versions should have been working fine. Diagnosis and patch
14313 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
14314 Bugfix on 0.2.0.20-rc.
14317 Changes in version 0.2.0.20-rc - 2008-02-24
14318 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
14319 makes more progress towards normalizing Tor's TLS handshake, makes
14320 hidden services work better again, helps relays bootstrap if they don't
14321 know their IP address, adds optional support for linking in openbsd's
14322 allocator or tcmalloc, allows really fast relays to scale past 15000
14323 sockets, and fixes a bunch of minor bugs reported by Veracode.
14326 - Enable the revised TLS handshake based on the one designed by
14327 Steven Murdoch in proposal 124, as revised in proposal 130. It
14328 includes version negotiation for OR connections as described in
14329 proposal 105. The new handshake is meant to be harder for censors
14330 to fingerprint, and it adds the ability to detect certain kinds of
14331 man-in-the-middle traffic analysis attacks. The version negotiation
14332 feature will allow us to improve Tor's link protocol more safely
14334 - Choose which bridge to use proportional to its advertised bandwidth,
14335 rather than uniformly at random. This should speed up Tor for
14336 bridge users. Also do this for people who set StrictEntryNodes.
14337 - When a TrackHostExits-chosen exit fails too many times in a row,
14338 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
14341 - Resolved problems with (re-)fetching hidden service descriptors.
14342 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
14343 and 0.2.0.19-alpha.
14344 - If we only ever used Tor for hidden service lookups or posts, we
14345 would stop building circuits and start refusing connections after
14346 24 hours, since we falsely believed that Tor was dormant. Reported
14347 by nwf; bugfix on 0.1.2.x.
14348 - Servers that don't know their own IP address should go to the
14349 authorities for their first directory fetch, even if their DirPort
14350 is off or if they don't know they're reachable yet. This will help
14351 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
14352 - When counting the number of open sockets, count not only the number
14353 of sockets we have received from the socket() call, but also
14354 the number we've gotten from accept() and socketpair(). This bug
14355 made us fail to count all sockets that we were using for incoming
14356 connections. Bugfix on 0.2.0.x.
14357 - Fix code used to find strings within buffers, when those strings
14358 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
14359 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
14360 - Add a new __HashedControlSessionPassword option for controllers
14361 to use for one-off session password hashes that shouldn't get
14362 saved to disk by SAVECONF --- Vidalia users were accumulating a
14363 pile of HashedControlPassword lines in their torrc files, one for
14364 each time they had restarted Tor and then clicked Save. Make Tor
14365 automatically convert "HashedControlPassword" to this new option but
14366 only when it's given on the command line. Partial fix for bug 586.
14368 o Minor features (performance):
14369 - Tune parameters for cell pool allocation to minimize amount of
14371 - Add OpenBSD malloc code from phk as an optional malloc
14372 replacement on Linux: some glibc libraries do very poorly
14373 with Tor's memory allocation patterns. Pass
14374 --enable-openbsd-malloc to get the replacement malloc code.
14375 - Add a --with-tcmalloc option to the configure script to link
14376 against tcmalloc (if present). Does not yet search for
14377 non-system include paths.
14378 - Stop imposing an arbitrary maximum on the number of file descriptors
14379 used for busy servers. Bug reported by Olaf Selke; patch from
14382 o Minor features (other):
14383 - When SafeLogging is disabled, log addresses along with all TLS
14385 - When building with --enable-gcc-warnings, check for whether Apple's
14386 warning "-Wshorten-64-to-32" is available.
14387 - Add a --passphrase-fd argument to the tor-gencert command for
14390 o Minor bugfixes (memory leaks and code problems):
14391 - We were leaking a file descriptor if Tor started with a zero-length
14392 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
14393 - Detect size overflow in zlib code. Reported by Justin Ferguson and
14395 - We were comparing the raw BridgePassword entry with a base64'ed
14396 version of it, when handling a "/tor/networkstatus-bridges"
14397 directory request. Now compare correctly. Noticed by Veracode.
14398 - Recover from bad tracked-since value in MTBF-history file.
14399 Should fix bug 537.
14400 - Alter the code that tries to recover from unhandled write
14401 errors, to not try to flush onto a socket that's given us
14402 unhandled errors. Bugfix on 0.1.2.x.
14403 - Make Unix controlsockets work correctly on OpenBSD. Patch from
14404 tup. Bugfix on 0.2.0.3-alpha.
14406 o Minor bugfixes (other):
14407 - If we have an extra-info document for our server, always make
14408 it available on the control port, even if we haven't gotten
14409 a copy of it from an authority yet. Patch from mwenge.
14410 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
14411 - Directory mirrors no longer include a guess at the client's IP
14412 address if the connection appears to be coming from the same /24
14413 network; it was producing too many wrong guesses.
14414 - Make the new hidden service code respect the SafeLogging setting.
14415 Bugfix on 0.2.0.x. Patch from Karsten.
14416 - When starting as an authority, do not overwrite all certificates
14417 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
14418 - If we're trying to flush the last bytes on a connection (for
14419 example, when answering a directory request), reset the
14420 time-to-give-up timeout every time we manage to write something
14421 on the socket. Bugfix on 0.1.2.x.
14422 - Change the behavior of "getinfo status/good-server-descriptor"
14423 so it doesn't return failure when any authority disappears.
14424 - Even though the man page said that "TrackHostExits ." should
14425 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
14426 - Report TLS "zero return" case as a "clean close" and "IO error"
14427 as a "close". Stop calling closes "unexpected closes": existing
14428 Tors don't use SSL_close(), so having a connection close without
14429 the TLS shutdown handshake is hardly unexpected.
14430 - Send NAMESERVER_STATUS messages for a single failed nameserver
14433 o Code simplifications and refactoring:
14434 - Remove the tor_strpartition function: its logic was confused,
14435 and it was only used for one thing that could be implemented far
14439 Changes in version 0.2.0.19-alpha - 2008-02-09
14440 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
14441 handshake, makes path selection for relays more secure and IP address
14442 guessing more robust, and generally fixes a lot of bugs in preparation
14443 for calling the 0.2.0 branch stable.
14446 - Do not include recognizeable strings in the commonname part of
14447 Tor's x509 certificates.
14450 - If we're a relay, avoid picking ourselves as an introduction point,
14451 a rendezvous point, or as the final hop for internal circuits. Bug
14452 reported by taranis and lodger. Bugfix on 0.1.2.x.
14453 - Patch from "Andrew S. Lists" to catch when we contact a directory
14454 mirror at IP address X and he says we look like we're coming from
14455 IP address X. Bugfix on 0.1.2.x.
14457 o Minor features (security):
14458 - Be more paranoid about overwriting sensitive memory on free(),
14459 as a defensive programming tactic to ensure forward secrecy.
14461 o Minor features (directory authority):
14462 - Actually validate the options passed to AuthDirReject,
14463 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
14464 - Reject router descriptors with out-of-range bandwidthcapacity or
14465 bandwidthburst values.
14467 o Minor features (controller):
14468 - Reject controller commands over 1MB in length. This keeps rogue
14469 processes from running us out of memory.
14471 o Minor features (misc):
14472 - Give more descriptive well-formedness errors for out-of-range
14473 hidden service descriptor/protocol versions.
14474 - Make memory debugging information describe more about history
14475 of cell allocation, so we can help reduce our memory use.
14477 o Deprecated features (controller):
14478 - The status/version/num-versioning and status/version/num-concurring
14479 GETINFO options are no longer useful in the v3 directory protocol:
14480 treat them as deprecated, and warn when they're used.
14483 - When our consensus networkstatus has been expired for a while, stop
14484 being willing to build circuits using it. Fixes bug 401. Bugfix
14486 - Directory caches now fetch certificates from all authorities
14487 listed in a networkstatus consensus, even when they do not
14488 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
14489 - When connecting to a bridge without specifying its key, insert
14490 the connection into the identity-to-connection map as soon as
14491 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
14492 - Detect versions of OS X where malloc_good_size() is present in the
14493 library but never actually declared. Resolves bug 587. Bugfix
14495 - Stop incorrectly truncating zlib responses to directory authority
14496 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
14497 - Stop recommending that every server operator send mail to tor-ops.
14498 Resolves bug 597. Bugfix on 0.1.2.x.
14499 - Don't trigger an assert if we start a directory authority with a
14500 private IP address (like 127.0.0.1).
14501 - Avoid possible failures when generating a directory with routers
14502 with over-long versions strings, or too many flags set. Bugfix
14504 - If an attempt to launch a DNS resolve request over the control
14505 port fails because we have overrun the limit on the number of
14506 connections, tell the controller that the request has failed.
14507 - Avoid using too little bandwidth when our clock skips a few
14508 seconds. Bugfix on 0.1.2.x.
14509 - Fix shell error when warning about missing packages in configure
14510 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
14511 - Do not become confused when receiving a spurious VERSIONS-like
14512 cell from a confused v1 client. Bugfix on 0.2.0.x.
14513 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
14514 introduction points for a hidden service have failed. Patch from
14515 Karsten Loesing. Bugfix on 0.2.0.x.
14517 o Code simplifications and refactoring:
14518 - Remove some needless generality from cpuworker code, for improved
14520 - Stop overloading the circuit_t.onionskin field for both "onionskin
14521 from a CREATE cell that we are waiting for a cpuworker to be
14522 assigned" and "onionskin from an EXTEND cell that we are going to
14523 send to an OR as soon as we are connected". Might help with bug 600.
14524 - Add an in-place version of aes_crypt() so that we can avoid doing a
14525 needless memcpy() call on each cell payload.
14528 Changes in version 0.2.0.18-alpha - 2008-01-25
14529 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
14530 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
14531 that can warn or reject connections to ports generally associated with
14532 vulnerable-plaintext protocols.
14534 o New directory authorities:
14535 - Set up dannenberg (run by CCC) as the sixth v3 directory
14539 - Fix a major memory leak when attempting to use the v2 TLS
14540 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
14541 - We accidentally enabled the under-development v2 TLS handshake
14542 code, which was causing log entries like "TLS error while
14543 renegotiating handshake". Disable it again. Resolves bug 590.
14544 - We were computing the wrong Content-Length: header for directory
14545 responses that need to be compressed on the fly, causing clients
14546 asking for those items to always fail. Bugfix on 0.2.0.x; partially
14550 - Avoid going directly to the directory authorities even if you're a
14551 relay, if you haven't found yourself reachable yet or if you've
14552 decided not to advertise your dirport yet. Addresses bug 556.
14553 - If we've gone 12 hours since our last bandwidth check, and we
14554 estimate we have less than 50KB bandwidth capacity but we could
14555 handle more, do another bandwidth test.
14556 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
14557 Tor can warn and/or refuse connections to ports commonly used with
14558 vulnerable-plaintext protocols. Currently we warn on ports 23,
14559 109, 110, and 143, but we don't reject any.
14562 - When we setconf ClientOnly to 1, close any current OR and Dir
14563 listeners. Reported by mwenge.
14564 - When we get a consensus that's been signed by more people than
14565 we expect, don't log about it; it's not a big deal. Reported
14569 - Don't answer "/tor/networkstatus-bridges" directory requests if
14570 the request isn't encrypted.
14571 - Make "ClientOnly 1" config option disable directory ports too.
14572 - Patches from Karsten Loesing to make v2 hidden services more
14573 robust: work even when there aren't enough HSDir relays available;
14574 retry when a v2 rend desc fetch fails; but don't retry if we
14575 already have a usable v0 rend desc.
14578 Changes in version 0.2.0.17-alpha - 2008-01-17
14579 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
14582 - Make the tor-gencert man page get included correctly in the tarball.
14585 Changes in version 0.2.0.16-alpha - 2008-01-17
14586 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
14587 Loesing, and generally cleans up a lot of features and minor bugs.
14589 o New directory authorities:
14590 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
14593 o Major performance improvements:
14594 - Switch our old ring buffer implementation for one more like that
14595 used by free Unix kernels. The wasted space in a buffer with 1mb
14596 of data will now be more like 8k than 1mb. The new implementation
14597 also avoids realloc();realloc(); patterns that can contribute to
14598 memory fragmentation.
14601 - Configuration files now accept C-style strings as values. This
14602 helps encode characters not allowed in the current configuration
14603 file format, such as newline or #. Addresses bug 557.
14604 - Although we fixed bug 539 (where servers would send HTTP status 503
14605 responses _and_ send a body too), there are still servers out
14606 there that haven't upgraded. Therefore, make clients parse such
14607 bodies when they receive them.
14608 - When we're not serving v2 directory information, there is no reason
14609 to actually keep any around. Remove the obsolete files and directory
14610 on startup if they are very old and we aren't going to serve them.
14612 o Minor performance improvements:
14613 - Reference-count and share copies of address policy entries; only 5%
14614 of them were actually distinct.
14615 - Never walk through the list of logs if we know that no log is
14616 interested in a given message.
14619 - When an authority has not signed a consensus, do not try to
14620 download a nonexistent "certificate with key 00000000". Bugfix
14621 on 0.2.0.x. Fixes bug 569.
14622 - Fix a rare assert error when we're closing one of our threads:
14623 use a mutex to protect the list of logs, so we never write to the
14624 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
14625 bug 575, which is kind of the revenge of bug 222.
14626 - Patch from Karsten Loesing to complain less at both the client
14627 and the relay when a relay used to have the HSDir flag but doesn't
14628 anymore, and we try to upload a hidden service descriptor.
14629 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
14631 - Do not try to download missing certificates until we have tried
14632 to check our fallback consensus. Fixes bug 583.
14633 - Make bridges round reported GeoIP stats info up to the nearest
14634 estimate, not down. Now we can distinguish between "0 people from
14635 this country" and "1 person from this country".
14636 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
14637 - Avoid possible segfault if key generation fails in
14638 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
14639 - Avoid segfault in the case where a badly behaved v2 versioning
14640 directory sends a signed networkstatus with missing client-versions.
14642 - Avoid segfaults on certain complex invocations of
14643 router_get_by_hexdigest(). Bugfix on 0.1.2.
14644 - Correct bad index on array access in parse_http_time(). Bugfix
14646 - Fix possible bug in vote generation when server versions are present
14647 but client versions are not.
14648 - Fix rare bug on REDIRECTSTREAM control command when called with no
14649 port set: it could erroneously report an error when none had
14651 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
14652 compressing large objects and find ourselves with more than 4k
14653 left over. Bugfix on 0.2.0.
14654 - Fix a small memory leak when setting up a hidden service.
14655 - Fix a few memory leaks that could in theory happen under bizarre
14657 - Fix an assert if we post a general-purpose descriptor via the
14658 control port but that descriptor isn't mentioned in our current
14659 network consensus. Bug reported by Jon McLachlan; bugfix on
14662 o Minor features (controller):
14663 - Get NS events working again. Patch from tup.
14664 - The GETCONF command now escapes and quotes configuration values
14665 that don't otherwise fit into the torrc file.
14666 - The SETCONF command now handles quoted values correctly.
14668 o Minor features (directory authorities):
14669 - New configuration options to override default maximum number of
14670 servers allowed on a single IP address. This is important for
14671 running a test network on a single host.
14672 - Actually implement the -s option to tor-gencert.
14673 - Add a manual page for tor-gencert.
14675 o Minor features (bridges):
14676 - Bridge authorities no longer serve bridge descriptors over
14677 unencrypted connections.
14679 o Minor features (other):
14680 - Add hidden services and DNSPorts to the list of things that make
14681 Tor accept that it has running ports. Change starting Tor with no
14682 ports from a fatal error to a warning; we might change it back if
14683 this turns out to confuse anybody. Fixes bug 579.
14686 Changes in version 0.1.2.19 - 2008-01-17
14687 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
14688 exit policy a little bit more conservative so it's safer to run an
14689 exit relay on a home system, and fixes a variety of smaller issues.
14692 - Exit policies now reject connections that are addressed to a
14693 relay's public (external) IP address too, unless
14694 ExitPolicyRejectPrivate is turned off. We do this because too
14695 many relays are running nearby to services that trust them based
14696 on network address.
14699 - When the clock jumps forward a lot, do not allow the bandwidth
14700 buckets to become negative. Fixes bug 544.
14701 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14702 on every successful resolve. Reported by Mike Perry.
14703 - Purge old entries from the "rephist" database and the hidden
14704 service descriptor database even when DirPort is zero.
14705 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
14706 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
14707 crashing or mis-answering these requests.
14708 - When we decide to send a 503 response to a request for servers, do
14709 not then also send the server descriptors: this defeats the whole
14710 purpose. Fixes bug 539.
14713 - Changing the ExitPolicyRejectPrivate setting should cause us to
14714 rebuild our server descriptor.
14715 - Fix handling of hex nicknames when answering controller requests for
14716 networkstatus by name, or when deciding whether to warn about
14717 unknown routers in a config option. (Patch from mwenge.)
14718 - Fix a couple of hard-to-trigger autoconf problems that could result
14719 in really weird results on platforms whose sys/types.h files define
14720 nonstandard integer types.
14721 - Don't try to create the datadir when running --verify-config or
14722 --hash-password. Resolves bug 540.
14723 - If we were having problems getting a particular descriptor from the
14724 directory caches, and then we learned about a new descriptor for
14725 that router, we weren't resetting our failure count. Reported
14727 - Although we fixed bug 539 (where servers would send HTTP status 503
14728 responses _and_ send a body too), there are still servers out there
14729 that haven't upgraded. Therefore, make clients parse such bodies
14730 when they receive them.
14731 - Run correctly on systems where rlim_t is larger than unsigned long.
14732 This includes some 64-bit systems.
14733 - Run correctly on platforms (like some versions of OS X 10.5) where
14734 the real limit for number of open files is OPEN_FILES, not rlim_max
14735 from getrlimit(RLIMIT_NOFILES).
14736 - Avoid a spurious free on base64 failure.
14737 - Avoid segfaults on certain complex invocations of
14738 router_get_by_hexdigest().
14739 - Fix rare bug on REDIRECTSTREAM control command when called with no
14740 port set: it could erroneously report an error when none had
14744 Changes in version 0.2.0.15-alpha - 2007-12-25
14745 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
14746 features added in 0.2.0.13-alpha.
14749 - Fix several remotely triggerable asserts based on DirPort requests
14750 for a v2 or v3 networkstatus object before we were prepared. This
14751 was particularly bad for 0.2.0.13 and later bridge relays, who
14752 would never have a v2 networkstatus and would thus always crash
14753 when used. Bugfixes on 0.2.0.x.
14754 - Estimate the v3 networkstatus size more accurately, rather than
14755 estimating it at zero bytes and giving it artificially high priority
14756 compared to other directory requests. Bugfix on 0.2.0.x.
14759 - Fix configure.in logic for cross-compilation.
14760 - When we load a bridge descriptor from the cache, and it was
14761 previously unreachable, mark it as retriable so we won't just
14762 ignore it. Also, try fetching a new copy immediately. Bugfixes
14764 - The bridge GeoIP stats were counting other relays, for example
14765 self-reachability and authority-reachability tests.
14768 - Support compilation to target iPhone; patch from cjacker huang.
14769 To build for iPhone, pass the --enable-iphone option to configure.
14772 Changes in version 0.2.0.14-alpha - 2007-12-23
14774 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
14775 without a datadirectory from a previous Tor install. Reported
14777 - Fix a crash when we fetch a descriptor that turns out to be
14778 unexpected (it used to be in our networkstatus when we started
14779 fetching it, but it isn't in our current networkstatus), and we
14780 aren't using bridges. Bugfix on 0.2.0.x.
14781 - Fix a crash when accessing hidden services: it would work the first
14782 time you use a given introduction point for your service, but
14783 on subsequent requests we'd be using garbage memory. Fixed by
14784 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
14785 - Fix a crash when we load a bridge descriptor from disk but we don't
14786 currently have a Bridge line for it in our torrc. Bugfix on
14790 - If bridge authorities set BridgePassword, they will serve a
14791 snapshot of known bridge routerstatuses from their DirPort to
14792 anybody who knows that password. Unset by default.
14795 - Make the unit tests build again.
14796 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
14797 - Make PublishServerDescriptor default to 1, so the default doesn't
14798 have to change as we invent new directory protocol versions.
14799 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
14800 be included unless sys/time.h is already included. Fixes
14801 bug 553. Bugfix on 0.2.0.x.
14802 - If we receive a general-purpose descriptor and then receive an
14803 identical bridge-purpose descriptor soon after, don't discard
14804 the next one as a duplicate.
14807 - If BridgeRelay is set to 1, then the default for
14808 PublishServerDescriptor is now "bridge" rather than "v2,v3".
14809 - If the user sets RelayBandwidthRate but doesn't set
14810 RelayBandwidthBurst, then make them equal rather than erroring out.
14813 Changes in version 0.2.0.13-alpha - 2007-12-21
14814 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
14815 Goodell, fixes many more bugs, and adds a lot of infrastructure for
14818 o New directory authorities:
14819 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
14823 - Only update guard status (usable / not usable) once we have
14824 enough directory information. This was causing us to always pick
14825 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
14826 causing us to discard all our guards on startup if we hadn't been
14827 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
14828 - Purge old entries from the "rephist" database and the hidden
14829 service descriptor databases even when DirPort is zero. Bugfix
14831 - We were ignoring our RelayBandwidthRate for the first 30 seconds
14832 after opening a circuit -- even a relayed circuit. Bugfix on
14834 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
14835 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
14836 crashing or mis-answering these types of requests.
14837 - Relays were publishing their server descriptor to v1 and v2
14838 directory authorities, but they didn't try publishing to v3-only
14839 authorities. Fix this; and also stop publishing to v1 authorities.
14841 - When we were reading router descriptors from cache, we were ignoring
14842 the annotations -- so for example we were reading in bridge-purpose
14843 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
14844 - When we decided to send a 503 response to a request for servers, we
14845 were then also sending the server descriptors: this defeats the
14846 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
14849 - Bridge relays now behave like clients with respect to time
14850 intervals for downloading new consensus documents -- otherwise they
14851 stand out. Bridge users now wait until the end of the interval,
14852 so their bridge relay will be sure to have a new consensus document.
14853 - Three new config options (AlternateDirAuthority,
14854 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
14855 user selectively replace the default directory authorities by type,
14856 rather than the all-or-nothing replacement that DirServer offers.
14857 - Tor can now be configured to read a GeoIP file from disk in one
14858 of two formats. This can be used by controllers to map IP addresses
14859 to countries. Eventually, it may support exit-by-country.
14860 - When possible, bridge relays remember which countries users
14861 are coming from, and report aggregate information in their
14862 extra-info documents, so that the bridge authorities can learn
14863 where Tor is blocked.
14864 - Bridge directory authorities now do reachability testing on the
14865 bridges they know. They provide router status summaries to the
14866 controller via "getinfo ns/purpose/bridge", and also dump summaries
14867 to a file periodically.
14868 - Stop fetching directory info so aggressively if your DirPort is
14869 on but your ORPort is off; stop fetching v2 dir info entirely.
14870 You can override these choices with the new FetchDirInfoEarly
14874 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
14875 consensus documents when there are too many relays at a single
14876 IP address. Now clear it in v2 network status documents too, and
14877 also clear it in routerinfo_t when the relay is no longer listed
14878 in the relevant networkstatus document.
14879 - Don't crash if we get an unexpected value for the
14880 PublishServerDescriptor config option. Reported by Matt Edman;
14881 bugfix on 0.2.0.9-alpha.
14882 - Our new v2 hidden service descriptor format allows descriptors
14883 that have no introduction points. But Tor crashed when we tried
14884 to build a descriptor with no intro points (and it would have
14885 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
14886 by Karsten Loesing.
14887 - Fix building with dmalloc 5.5.2 with glibc.
14888 - Reject uploaded descriptors and extrainfo documents if they're
14889 huge. Otherwise we'll cache them all over the network and it'll
14890 clog everything up. Reported by Aljosha Judmayer.
14891 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
14892 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
14893 - When the DANGEROUS_VERSION controller status event told us we're
14894 running an obsolete version, it used the string "OLD" to describe
14895 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
14896 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
14897 - If we can't expand our list of entry guards (e.g. because we're
14898 using bridges or we have StrictEntryNodes set), don't mark relays
14899 down when they fail a directory request. Otherwise we're too quick
14900 to mark all our entry points down. Bugfix on 0.1.2.x.
14901 - Fix handling of hex nicknames when answering controller requests for
14902 networkstatus by name, or when deciding whether to warn about unknown
14903 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
14904 - Fix a couple of hard-to-trigger autoconf problems that could result
14905 in really weird results on platforms whose sys/types.h files define
14906 nonstandard integer types. Bugfix on 0.1.2.x.
14907 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
14908 - Don't crash on name lookup when we have no current consensus. Fixes
14909 bug 538; bugfix on 0.2.0.x.
14910 - Only Tors that want to mirror the v2 directory info should
14911 create the "cached-status" directory in their datadir. (All Tors
14912 used to create it.) Bugfix on 0.2.0.9-alpha.
14913 - Directory authorities should only automatically download Extra Info
14914 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
14917 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
14918 consumers. (We already do this on HUP.)
14919 - Authorities and caches fetch the v2 networkstatus documents
14920 less often, now that v3 is encouraged.
14921 - Add a new config option BridgeRelay that specifies you want to
14922 be a bridge relay. Right now the only difference is that it makes
14923 you answer begin_dir requests, and it makes you cache dir info,
14924 even if your DirPort isn't on.
14925 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
14926 ask about source, timestamp of arrival, purpose, etc. We need
14927 something like this to help Vidalia not do GeoIP lookups on bridge
14929 - Allow multiple HashedControlPassword config lines, to support
14930 multiple controller passwords.
14931 - Authorities now decide whether they're authoritative for a given
14932 router based on the router's purpose.
14933 - New config options AuthDirBadDir and AuthDirListBadDirs for
14934 authorities to mark certain relays as "bad directories" in the
14935 networkstatus documents. Also supports the "!baddir" directive in
14936 the approved-routers file.
14939 Changes in version 0.2.0.12-alpha - 2007-11-16
14940 This twelfth development snapshot fixes some more build problems as
14941 well as a few minor bugs.
14944 - Make it build on OpenBSD again. Patch from tup.
14945 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
14946 package-building for Red Hat, OS X, etc.
14948 o Minor bugfixes (on 0.1.2.x):
14949 - Changing the ExitPolicyRejectPrivate setting should cause us to
14950 rebuild our server descriptor.
14952 o Minor bugfixes (on 0.2.0.x):
14953 - When we're lacking a consensus, don't try to perform rendezvous
14954 operations. Reported by Karsten Loesing.
14955 - Fix a small memory leak whenever we decide against using a
14956 newly picked entry guard. Reported by Mike Perry.
14957 - When authorities detected more than two relays running on the same
14958 IP address, they were clearing all the status flags but forgetting
14959 to clear the "hsdir" flag. So clients were being told that a
14960 given relay was the right choice for a v2 hsdir lookup, yet they
14961 never had its descriptor because it was marked as 'not running'
14963 - If we're trying to fetch a bridge descriptor and there's no way
14964 the bridge authority could help us (for example, we don't know
14965 a digest, or there is no bridge authority), don't be so eager to
14966 fall back to asking the bridge authority.
14967 - If we're using bridges or have strictentrynodes set, and our
14968 chosen exit is in the same family as all our bridges/entry guards,
14969 then be flexible about families.
14972 - When we negotiate a v2 link-layer connection (not yet implemented),
14973 accept RELAY_EARLY cells and turn them into RELAY cells if we've
14974 negotiated a v1 connection for their next step. Initial code for
14978 Changes in version 0.2.0.11-alpha - 2007-11-12
14979 This eleventh development snapshot fixes some build problems with
14980 the previous snapshot. It also includes a more secure-by-default exit
14981 policy for relays, fixes an enormous memory leak for exit relays, and
14982 fixes another bug where servers were falling out of the directory list.
14985 - Exit policies now reject connections that are addressed to a
14986 relay's public (external) IP address too, unless
14987 ExitPolicyRejectPrivate is turned off. We do this because too
14988 many relays are running nearby to services that trust them based
14989 on network address. Bugfix on 0.1.2.x.
14992 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14993 on every successful resolve. Reported by Mike Perry; bugfix
14995 - On authorities, never downgrade to old router descriptors simply
14996 because they're listed in the consensus. This created a catch-22
14997 where we wouldn't list a new descriptor because there was an
14998 old one in the consensus, and we couldn't get the new one in the
14999 consensus because we wouldn't list it. Possible fix for bug 548.
15000 Also, this might cause bug 543 to appear on authorities; if so,
15001 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
15003 o Packaging fixes on 0.2.0.10-alpha:
15004 - We were including instructions about what to do with the
15005 src/config/fallback-consensus file, but we weren't actually
15006 including it in the tarball. Disable all of that for now.
15009 - Allow people to say PreferTunnelledDirConns rather than
15010 PreferTunneledDirConns, for those alternate-spellers out there.
15013 - Don't reevaluate all the information from our consensus document
15014 just because we've downloaded a v2 networkstatus that we intend
15015 to cache. Fixes bug 545; bugfix on 0.2.0.x.
15018 Changes in version 0.2.0.10-alpha - 2007-11-10
15019 This tenth development snapshot adds a third v3 directory authority
15020 run by Mike Perry, adds most of Karsten Loesing's new hidden service
15021 descriptor format, fixes a bad crash bug and new bridge bugs introduced
15022 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
15023 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
15024 addresses many more minor issues.
15026 o New directory authorities:
15027 - Set up ides (run by Mike Perry) as the third v3 directory authority.
15030 - Allow tunnelled directory connections to ask for an encrypted
15031 "begin_dir" connection or an anonymized "uses a full Tor circuit"
15032 connection independently. Now we can make anonymized begin_dir
15033 connections for (e.g.) more secure hidden service posting and
15035 - More progress on proposal 114: code from Karsten Loesing to
15036 implement new hidden service descriptor format.
15037 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
15038 accommodate the growing number of servers that use the default
15039 and are reaching it.
15040 - Directory authorities use a new formula for selecting which nodes
15041 to advertise as Guards: they must be in the top 7/8 in terms of
15042 how long we have known about them, and above the median of those
15043 nodes in terms of weighted fractional uptime.
15044 - Make "not enough dir info yet" warnings describe *why* Tor feels
15045 it doesn't have enough directory info yet.
15048 - Stop servers from crashing if they set a Family option (or
15049 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
15051 - Make bridge users work again -- the move to v3 directories in
15052 0.2.0.9-alpha had introduced a number of bugs that made bridges
15053 no longer work for clients.
15054 - When the clock jumps forward a lot, do not allow the bandwidth
15055 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
15057 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
15058 - When the consensus lists a router descriptor that we previously were
15059 mirroring, but that we considered non-canonical, reload the
15060 descriptor as canonical. This fixes bug 543 where Tor servers
15061 would start complaining after a few days that they don't have
15062 enough directory information to build a circuit.
15063 - Consider replacing the current consensus when certificates arrive
15064 that make the pending consensus valid. Previously, we were only
15065 considering replacement when the new certs _didn't_ help.
15066 - Fix an assert error on startup if we didn't already have the
15067 consensus and certs cached in our datadirectory: we were caching
15068 the consensus in consensus_waiting_for_certs but then free'ing it
15070 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
15071 Request) if we need more v3 certs but we've already got pending
15072 requests for all of them.
15073 - Correctly back off from failing certificate downloads. Fixes
15075 - Authorities don't vote on the Running flag if they have been running
15076 for less than 30 minutes themselves. Fixes bug 547, where a newly
15077 started authority would vote that everyone was down.
15079 o New requirements:
15080 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
15081 it, it had no AES, and it hasn't seen any security patches since
15085 - Clients now hold circuitless TLS connections open for 1.5 times
15086 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
15087 rebuild a new circuit over them within that timeframe. Previously,
15088 they held them open only for KeepalivePeriod (5 minutes).
15089 - Use "If-Modified-Since" to avoid retrieving consensus
15090 networkstatuses that we already have.
15091 - When we have no consensus, check FallbackNetworkstatusFile (defaults
15092 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
15093 we start knowing some directory caches.
15094 - When we receive a consensus from the future, warn about skew.
15095 - Improve skew reporting: try to give the user a better log message
15096 about how skewed they are, and how much this matters.
15097 - When we have a certificate for an authority, believe that
15098 certificate's claims about the authority's IP address.
15099 - New --quiet command-line option to suppress the default console log.
15100 Good in combination with --hash-password.
15101 - Authorities send back an X-Descriptor-Not-New header in response to
15102 an accepted-but-discarded descriptor upload. Partially implements
15104 - Make the log message for "tls error. breaking." more useful.
15105 - Better log messages about certificate downloads, to attempt to
15106 track down the second incarnation of bug 546.
15108 o Minor features (bridges):
15109 - If bridge users set UpdateBridgesFromAuthority, but the digest
15110 they ask for is a 404 from the bridge authority, they now fall
15111 back to trying the bridge directly.
15112 - Bridges now use begin_dir to publish their server descriptor to
15113 the bridge authority, even when they haven't set TunnelDirConns.
15115 o Minor features (controller):
15116 - When reporting clock skew, and we know that the clock is _at least
15117 as skewed_ as some value, but we don't know the actual value,
15118 report the value as a "minimum skew."
15121 - Update linux-tor-prio.sh script to allow QoS based on the uid of
15122 the Tor process. Patch from Marco Bonetti with tweaks from Mike
15126 - Refuse to start if both ORPort and UseBridges are set. Bugfix
15127 on 0.2.0.x, suggested by Matt Edman.
15128 - Don't stop fetching descriptors when FetchUselessDescriptors is
15129 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
15130 reported by tup and ioerror.
15131 - Better log message on vote from unknown authority.
15132 - Don't log "Launching 0 request for 0 router" message.
15134 o Minor bugfixes (memory leaks):
15135 - Stop leaking memory every time we parse a v3 certificate. Bugfix
15137 - Stop leaking memory every time we load a v3 certificate. Bugfix
15138 on 0.2.0.1-alpha. Fixes bug 536.
15139 - Stop leaking a cached networkstatus on exit. Bugfix on
15141 - Stop leaking voter information every time we free a consensus.
15142 Bugfix on 0.2.0.3-alpha.
15143 - Stop leaking signed data every time we check a voter signature.
15144 Bugfix on 0.2.0.3-alpha.
15145 - Stop leaking a signature every time we fail to parse a consensus or
15146 a vote. Bugfix on 0.2.0.3-alpha.
15147 - Stop leaking v2_download_status_map on shutdown. Bugfix on
15149 - Stop leaking conn->nickname every time we make a connection to a
15150 Tor relay without knowing its expected identity digest (e.g. when
15151 using bridges). Bugfix on 0.2.0.3-alpha.
15153 - Minor bugfixes (portability):
15154 - Run correctly on platforms where rlim_t is larger than unsigned
15155 long, and/or where the real limit for number of open files is
15156 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
15157 particular, these may be needed for OS X 10.5.
15160 Changes in version 0.1.2.18 - 2007-10-28
15161 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
15162 hidden service introduction that were causing huge delays, and a big
15163 bug that was causing some servers to disappear from the network status
15164 lists for a few hours each day.
15166 o Major bugfixes (crashes):
15167 - If a connection is shut down abruptly because of something that
15168 happened inside connection_flushed_some(), do not call
15169 connection_finished_flushing(). Should fix bug 451:
15170 "connection_stop_writing: Assertion conn->write_event failed"
15171 Bugfix on 0.1.2.7-alpha.
15172 - Fix possible segfaults in functions called from
15173 rend_process_relay_cell().
15175 o Major bugfixes (hidden services):
15176 - Hidden services were choosing introduction points uniquely by
15177 hexdigest, but when constructing the hidden service descriptor
15178 they merely wrote the (potentially ambiguous) nickname.
15179 - Clients now use the v2 intro format for hidden service
15180 connections: they specify their chosen rendezvous point by identity
15181 digest rather than by (potentially ambiguous) nickname. These
15182 changes could speed up hidden service connections dramatically.
15184 o Major bugfixes (other):
15185 - Stop publishing a new server descriptor just because we get a
15186 HUP signal. This led (in a roundabout way) to some servers getting
15187 dropped from the networkstatus lists for a few hours each day.
15188 - When looking for a circuit to cannibalize, consider family as well
15189 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15190 circuit cannibalization).
15191 - When a router wasn't listed in a new networkstatus, we were leaving
15192 the flags for that router alone -- meaning it remained Named,
15193 Running, etc -- even though absence from the networkstatus means
15194 that it shouldn't be considered to exist at all anymore. Now we
15195 clear all the flags for routers that fall out of the networkstatus
15196 consensus. Fixes bug 529.
15199 - Don't try to access (or alter) the state file when running
15200 --list-fingerprint or --verify-config or --hash-password. Resolves
15202 - When generating information telling us how to extend to a given
15203 router, do not try to include the nickname if it is
15204 absent. Resolves bug 467.
15205 - Fix a user-triggerable segfault in expand_filename(). (There isn't
15206 a way to trigger this remotely.)
15207 - When sending a status event to the controller telling it that an
15208 OR address is reachable, set the port correctly. (Previously we
15209 were reporting the dir port.)
15210 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15211 command. Bugfix on 0.1.2.17.
15212 - When loading bandwidth history, do not believe any information in
15213 the future. Fixes bug 434.
15214 - When loading entry guard information, do not believe any information
15216 - When we have our clock set far in the future and generate an
15217 onion key, then re-set our clock to be correct, we should not stop
15218 the onion key from getting rotated.
15219 - On some platforms, accept() can return a broken address. Detect
15220 this more quietly, and deal accordingly. Fixes bug 483.
15221 - It's not actually an error to find a non-pending entry in the DNS
15222 cache when canceling a pending resolve. Don't log unless stuff
15223 is fishy. Resolves bug 463.
15224 - Don't reset trusted dir server list when we set a configuration
15225 option. Patch from Robert Hogan.
15226 - Don't try to create the datadir when running --verify-config or
15227 --hash-password. Resolves bug 540.
15230 Changes in version 0.2.0.9-alpha - 2007-10-24
15231 This ninth development snapshot switches clients to the new v3 directory
15232 system; allows servers to be listed in the network status even when they
15233 have the same nickname as a registered server; and fixes many other
15234 bugs including a big one that was causing some servers to disappear
15235 from the network status lists for a few hours each day.
15237 o Major features (directory system):
15238 - Clients now download v3 consensus networkstatus documents instead
15239 of v2 networkstatus documents. Clients and caches now base their
15240 opinions about routers on these consensus documents. Clients only
15241 download router descriptors listed in the consensus.
15242 - Authorities now list servers who have the same nickname as
15243 a different named server, but list them with a new flag,
15244 "Unnamed". Now we can list servers that happen to pick the same
15245 nickname as a server that registered two years ago and then
15246 disappeared. Partially implements proposal 122.
15247 - If the consensus lists a router as "Unnamed", the name is assigned
15248 to a different router: do not identify the router by that name.
15249 Partially implements proposal 122.
15250 - Authorities can now come to a consensus on which method to use to
15251 compute the consensus. This gives us forward compatibility.
15254 - Stop publishing a new server descriptor just because we HUP or
15255 when we find our DirPort to be reachable but won't actually publish
15256 it. New descriptors without any real changes are dropped by the
15257 authorities, and can screw up our "publish every 18 hours" schedule.
15259 - When a router wasn't listed in a new networkstatus, we were leaving
15260 the flags for that router alone -- meaning it remained Named,
15261 Running, etc -- even though absence from the networkstatus means
15262 that it shouldn't be considered to exist at all anymore. Now we
15263 clear all the flags for routers that fall out of the networkstatus
15264 consensus. Fixes bug 529; bugfix on 0.1.2.x.
15265 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
15266 extrainfo documents and then discard them immediately for not
15267 matching the latest router. Bugfix on 0.2.0.1-alpha.
15269 o Minor features (v3 directory protocol):
15270 - Allow tor-gencert to generate a new certificate without replacing
15272 - Allow certificates to include an address.
15273 - When we change our directory-cache settings, reschedule all voting
15274 and download operations.
15275 - Reattempt certificate downloads immediately on failure, as long as
15276 we haven't failed a threshold number of times yet.
15277 - Delay retrying consensus downloads while we're downloading
15278 certificates to verify the one we just got. Also, count getting a
15279 consensus that we already have (or one that isn't valid) as a failure,
15280 and count failing to get the certificates after 20 minutes as a
15282 - Build circuits and download descriptors even if our consensus is a
15283 little expired. (This feature will go away once authorities are
15286 o Minor features (router descriptor cache):
15287 - If we find a cached-routers file that's been sitting around for more
15288 than 28 days unmodified, then most likely it's a leftover from
15289 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
15291 - When we (as a cache) download a descriptor because it was listed
15292 in a consensus, remember when the consensus was supposed to expire,
15293 and don't expire the descriptor until then.
15295 o Minor features (performance):
15296 - Call routerlist_remove_old_routers() much less often. This should
15297 speed startup, especially on directory caches.
15298 - Don't try to launch new descriptor downloads quite so often when we
15299 already have enough directory information to build circuits.
15300 - Base64 decoding was actually showing up on our profile when parsing
15301 the initial descriptor file; switch to an in-process all-at-once
15302 implementation that's about 3.5x times faster than calling out to
15305 o Minor features (compilation):
15306 - Detect non-ASCII platforms (if any still exist) and refuse to
15307 build there: some of our code assumes that 'A' is 65 and so on.
15309 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
15310 - Make the "next period" votes into "current period" votes immediately
15311 after publishing the consensus; avoid a heisenbug that made them
15312 stick around indefinitely.
15313 - When we discard a vote as a duplicate, do not report this as
15315 - Treat missing v3 keys or certificates as an error when running as a
15316 v3 directory authority.
15317 - When we're configured to be a v3 authority, but we're only listed
15318 as a non-v3 authority in our DirServer line for ourself, correct
15320 - If an authority doesn't have a qualified hostname, just put
15321 its address in the vote. This fixes the problem where we referred to
15322 "moria on moria:9031."
15323 - Distinguish between detached signatures for the wrong period, and
15324 detached signatures for a divergent vote.
15325 - Fix a small memory leak when computing a consensus.
15326 - When there's no concensus, we were forming a vote every 30
15327 minutes, but writing the "valid-after" line in our vote based
15328 on our configured V3AuthVotingInterval: so unless the intervals
15329 matched up, we immediately rejected our own vote because it didn't
15330 start at the voting interval that caused us to construct a vote.
15332 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
15333 - Delete unverified-consensus when the real consensus is set.
15334 - Consider retrying a consensus networkstatus fetch immediately
15335 after one fails: don't wait 60 seconds to notice.
15336 - When fetching a consensus as a cache, wait until a newer consensus
15337 should exist before trying to replace the current one.
15338 - Use a more forgiving schedule for retrying failed consensus
15339 downloads than for other types.
15341 o Minor bugfixes (other directory issues):
15342 - Correct the implementation of "download votes by digest." Bugfix on
15344 - Authorities no longer send back "400 you're unreachable please fix
15345 it" errors to Tor servers that aren't online all the time. We're
15346 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
15348 o Minor bugfixes (controller):
15349 - Don't reset trusted dir server list when we set a configuration
15350 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
15351 - Respond to INT and TERM SIGNAL commands before we execute the
15352 signal, in case the signal shuts us down. We had a patch in
15353 0.1.2.1-alpha that tried to do this by queueing the response on
15354 the connection's buffer before shutting down, but that really
15355 isn't the same thing at all. Bug located by Matt Edman.
15357 o Minor bugfixes (misc):
15358 - Correctly check for bad options to the "PublishServerDescriptor"
15359 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
15360 - Stop leaking memory on failing case of base32_decode, and make
15361 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
15362 - Don't try to download extrainfo documents when we're trying to
15363 fetch enough directory info to build a circuit: having enough
15364 info should get priority. Bugfix on 0.2.0.x.
15365 - Don't complain that "your server has not managed to confirm that its
15366 ports are reachable" if we haven't been able to build any circuits
15367 yet. Bug found by spending four hours without a v3 consensus. Bugfix
15369 - Detect the reason for failing to mmap a descriptor file we just
15370 wrote, and give a more useful log message. Fixes bug 533. Bugfix
15373 o Code simplifications and refactoring:
15374 - Remove support for the old bw_accounting file: we've been storing
15375 bandwidth accounting information in the state file since
15376 0.1.2.5-alpha. This may result in bandwidth accounting errors
15377 if you try to upgrade from 0.1.1.x or earlier, or if you try to
15378 downgrade to 0.1.1.x or earlier.
15379 - New convenience code to locate a file within the DataDirectory.
15380 - Move non-authority functionality out of dirvote.c.
15381 - Refactor the arguments for router_pick_{directory_|trusteddir}server
15382 so that they all take the same named flags.
15385 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
15386 Unix users an easy way to script their Tor process (e.g. by
15387 adjusting bandwidth based on the time of the day).
15390 Changes in version 0.2.0.8-alpha - 2007-10-12
15391 This eighth development snapshot fixes a crash bug that's been bothering
15392 us since February 2007, lets bridge authorities store a list of bridge
15393 descriptors they've seen, gets v3 directory voting closer to working,
15394 starts caching v3 directory consensus documents on directory mirrors,
15395 and fixes a variety of smaller issues including some minor memory leaks.
15397 o Major features (router descriptor cache):
15398 - Store routers in a file called cached-descriptors instead of in
15399 cached-routers. Initialize cached-descriptors from cached-routers
15400 if the old format is around. The new format allows us to store
15401 annotations along with descriptors.
15402 - Use annotations to record the time we received each descriptor, its
15403 source, and its purpose.
15404 - Disable the SETROUTERPURPOSE controller command: it is now
15406 - Controllers should now specify cache=no or cache=yes when using
15407 the +POSTDESCRIPTOR command.
15408 - Bridge authorities now write bridge descriptors to disk, meaning
15409 we can export them to other programs and begin distributing them
15412 o Major features (directory authorities):
15413 - When a v3 authority is missing votes or signatures, it now tries
15415 - Directory authorities track weighted fractional uptime as well as
15416 weighted mean-time-between failures. WFU is suitable for deciding
15417 whether a node is "usually up", while MTBF is suitable for deciding
15418 whether a node is "likely to stay up." We need both, because
15419 "usually up" is a good requirement for guards, while "likely to
15420 stay up" is a good requirement for long-lived connections.
15422 o Major features (v3 directory system):
15423 - Caches now download v3 network status documents as needed,
15424 and download the descriptors listed in them.
15425 - All hosts now attempt to download and keep fresh v3 authority
15426 certificates, and re-attempt after failures.
15427 - More internal-consistency checks for vote parsing.
15429 o Major bugfixes (crashes):
15430 - If a connection is shut down abruptly because of something that
15431 happened inside connection_flushed_some(), do not call
15432 connection_finished_flushing(). Should fix bug 451. Bugfix on
15435 o Major bugfixes (performance):
15436 - Fix really bad O(n^2) performance when parsing a long list of
15437 routers: Instead of searching the entire list for an "extra-info "
15438 string which usually wasn't there, once for every routerinfo
15439 we read, just scan lines forward until we find one we like.
15441 - When we add data to a write buffer in response to the data on that
15442 write buffer getting low because of a flush, do not consider the
15443 newly added data as a candidate for immediate flushing, but rather
15444 make it wait until the next round of writing. Otherwise, we flush
15445 and refill recursively, and a single greedy TLS connection can
15446 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
15448 o Minor features (v3 authority system):
15449 - Add more ways for tools to download the votes that lead to the
15451 - Send a 503 when low on bandwidth and a vote, consensus, or
15452 certificate is requested.
15453 - If-modified-since is now implemented properly for all kinds of
15454 certificate requests.
15456 o Minor bugfixes (network statuses):
15457 - Tweak the implementation of proposal 109 slightly: allow at most
15458 two Tor servers on the same IP address, except if it's the location
15459 of a directory authority, in which case allow five. Bugfix on
15462 o Minor bugfixes (controller):
15463 - When sending a status event to the controller telling it that an
15464 OR address is reachable, set the port correctly. (Previously we
15465 were reporting the dir port.) Bugfix on 0.1.2.x.
15467 o Minor bugfixes (v3 directory system):
15468 - Fix logic to look up a cert by its signing key digest. Bugfix on
15470 - Only change the reply to a vote to "OK" if it's not already
15471 set. This gets rid of annoying "400 OK" log messages, which may
15472 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
15473 - When we get a valid consensus, recompute the voting schedule.
15474 - Base the valid-after time of a vote on the consensus voting
15475 schedule, not on our preferred schedule.
15476 - Make the return values and messages from signature uploads and
15477 downloads more sensible.
15478 - Fix a memory leak when serving votes and consensus documents, and
15479 another when serving certificates.
15481 o Minor bugfixes (performance):
15482 - Use a slightly simpler string hashing algorithm (copying Python's
15483 instead of Java's) and optimize our digest hashing algorithm to take
15484 advantage of 64-bit platforms and to remove some possibly-costly
15486 - Fix a minor memory leak whenever we parse guards from our state
15487 file. Bugfix on 0.2.0.7-alpha.
15488 - Fix a minor memory leak whenever we write out a file. Bugfix on
15490 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15491 command. Bugfix on 0.2.0.5-alpha.
15493 o Minor bugfixes (portability):
15494 - On some platforms, accept() can return a broken address. Detect
15495 this more quietly, and deal accordingly. Fixes bug 483.
15496 - Stop calling tor_strlower() on uninitialized memory in some cases.
15497 Bugfix in 0.2.0.7-alpha.
15499 o Minor bugfixes (usability):
15500 - Treat some 403 responses from directory servers as INFO rather than
15501 WARN-severity events.
15502 - It's not actually an error to find a non-pending entry in the DNS
15503 cache when canceling a pending resolve. Don't log unless stuff is
15504 fishy. Resolves bug 463.
15506 o Minor bugfixes (anonymity):
15507 - Never report that we've used more bandwidth than we're willing to
15508 relay: it leaks how much non-relay traffic we're using. Resolves
15510 - When looking for a circuit to cannibalize, consider family as well
15511 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15512 circuit cannibalization).
15514 o Code simplifications and refactoring:
15515 - Make a bunch of functions static. Remove some dead code.
15516 - Pull out about a third of the really big routerlist.c; put it in a
15517 new module, networkstatus.c.
15518 - Merge the extra fields in local_routerstatus_t back into
15519 routerstatus_t: we used to need one routerstatus_t for each
15520 authority's opinion, plus a local_routerstatus_t for the locally
15521 computed consensus opinion. To save space, we put the locally
15522 modified fields into local_routerstatus_t, and only the common
15523 stuff into routerstatus_t. But once v3 directories are in use,
15524 clients and caches will no longer need to hold authority opinions;
15525 thus, the rationale for keeping the types separate is now gone.
15526 - Make the code used to reschedule and reattempt downloads more
15528 - Turn all 'Are we a directory server/mirror?' logic into a call to
15530 - Remove the code to generate the oldest (v1) directory format.
15531 The code has been disabled since 0.2.0.5-alpha.
15534 Changes in version 0.2.0.7-alpha - 2007-09-21
15535 This seventh development snapshot makes bridges work again, makes bridge
15536 authorities work for the first time, fixes two huge performance flaws
15537 in hidden services, and fixes a variety of minor issues.
15539 o New directory authorities:
15540 - Set up moria1 and tor26 as the first v3 directory authorities. See
15541 doc/spec/dir-spec.txt for details on the new directory design.
15543 o Major bugfixes (crashes):
15544 - Fix possible segfaults in functions called from
15545 rend_process_relay_cell(). Bugfix on 0.1.2.x.
15547 o Major bugfixes (bridges):
15548 - Fix a bug that made servers send a "404 Not found" in response to
15549 attempts to fetch their server descriptor. This caused Tor servers
15550 to take many minutes to establish reachability for their DirPort,
15551 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
15552 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
15553 users configure that and specify a bridge with an identity
15554 fingerprint, now they will lookup the bridge descriptor at the
15555 default bridge authority via a one-hop tunnel, but once circuits
15556 are established they will switch to a three-hop tunnel for later
15557 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
15559 o Major bugfixes (hidden services):
15560 - Hidden services were choosing introduction points uniquely by
15561 hexdigest, but when constructing the hidden service descriptor
15562 they merely wrote the (potentially ambiguous) nickname.
15563 - Clients now use the v2 intro format for hidden service
15564 connections: they specify their chosen rendezvous point by identity
15565 digest rather than by (potentially ambiguous) nickname. Both
15566 are bugfixes on 0.1.2.x, and they could speed up hidden service
15567 connections dramatically. Thanks to Karsten Loesing.
15569 o Minor features (security):
15570 - As a client, do not believe any server that tells us that an
15571 address maps to an internal address space.
15572 - Make it possible to enable HashedControlPassword and
15573 CookieAuthentication at the same time.
15575 o Minor features (guard nodes):
15576 - Tag every guard node in our state file with the version that
15577 we believe added it, or with our own version if we add it. This way,
15578 if a user temporarily runs an old version of Tor and then switches
15579 back to a new one, she doesn't automatically lose her guards.
15581 o Minor features (speed):
15582 - When implementing AES counter mode, update only the portions of the
15583 counter buffer that need to change, and don't keep separate
15584 network-order and host-order counters when they are the same (i.e.,
15585 on big-endian hosts.)
15587 o Minor features (controller):
15588 - Accept LF instead of CRLF on controller, since some software has a
15589 hard time generating real Internet newlines.
15590 - Add GETINFO values for the server status events
15591 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
15594 o Removed features:
15595 - Routers no longer include bandwidth-history lines in their
15596 descriptors; this information is already available in extra-info
15597 documents, and including it in router descriptors took up 60%
15598 (!) of compressed router descriptor downloads. Completes
15599 implementation of proposal 104.
15600 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
15601 and TorControl.py, as they use the old v0 controller protocol,
15602 and are obsoleted by TorFlow anyway.
15603 - Drop support for v1 rendezvous descriptors, since we never used
15604 them anyway, and the code has probably rotted by now. Based on
15605 patch from Karsten Loesing.
15606 - On OSX, stop warning the user that kqueue support in libevent is
15607 "experimental", since it seems to have worked fine for ages.
15610 - When generating information telling us how to extend to a given
15611 router, do not try to include the nickname if it is absent. Fixes
15612 bug 467. Bugfix on 0.2.0.3-alpha.
15613 - Fix a user-triggerable (but not remotely-triggerable) segfault
15614 in expand_filename(). Bugfix on 0.1.2.x.
15615 - Fix a memory leak when freeing incomplete requests from DNSPort.
15616 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
15617 - Don't try to access (or alter) the state file when running
15618 --list-fingerprint or --verify-config or --hash-password. (Resolves
15619 bug 499.) Bugfix on 0.1.2.x.
15620 - Servers used to decline to publish their DirPort if their
15621 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
15622 were below a threshold. Now they only look at BandwidthRate and
15623 RelayBandwidthRate. Bugfix on 0.1.2.x.
15624 - Remove an optimization in the AES counter-mode code that assumed
15625 that the counter never exceeded 2^68. When the counter can be set
15626 arbitrarily as an IV (as it is by Karsten's new hidden services
15627 code), this assumption no longer holds. Bugfix on 0.1.2.x.
15628 - Resume listing "AUTHORITY" flag for authorities in network status.
15629 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
15631 o Code simplifications and refactoring:
15632 - Revamp file-writing logic so we don't need to have the entire
15633 contents of a file in memory at once before we write to disk. Tor,
15635 - Turn "descriptor store" into a full-fledged type.
15636 - Move all NT services code into a separate source file.
15637 - Unify all code that computes medians, percentile elements, etc.
15638 - Get rid of a needless malloc when parsing address policies.
15641 Changes in version 0.1.2.17 - 2007-08-30
15642 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
15643 X bundles. Vidalia 0.0.14 makes authentication required for the
15644 ControlPort in the default configuration, which addresses important
15645 security risks. Everybody who uses Vidalia (or another controller)
15648 In addition, this Tor update fixes major load balancing problems with
15649 path selection, which should speed things up a lot once many people
15652 o Major bugfixes (security):
15653 - We removed support for the old (v0) control protocol. It has been
15654 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
15655 become more of a headache than it's worth.
15657 o Major bugfixes (load balancing):
15658 - When choosing nodes for non-guard positions, weight guards
15659 proportionally less, since they already have enough load. Patch
15661 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15662 will allow fast Tor servers to get more attention.
15663 - When we're upgrading from an old Tor version, forget our current
15664 guards and pick new ones according to the new weightings. These
15665 three load balancing patches could raise effective network capacity
15666 by a factor of four. Thanks to Mike Perry for measurements.
15668 o Major bugfixes (stream expiration):
15669 - Expire not-yet-successful application streams in all cases if
15670 they've been around longer than SocksTimeout. Right now there are
15671 some cases where the stream will live forever, demanding a new
15672 circuit every 15 seconds. Fixes bug 454; reported by lodger.
15674 o Minor features (controller):
15675 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15676 is valid before any authentication has been received. It tells
15677 a controller what kind of authentication is expected, and what
15678 protocol is spoken. Implements proposal 119.
15680 o Minor bugfixes (performance):
15681 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
15682 greatly speeding up loading cached-routers from disk on startup.
15683 - Disable sentinel-based debugging for buffer code: we squashed all
15684 the bugs that this was supposed to detect a long time ago, and now
15685 its only effect is to change our buffer sizes from nice powers of
15686 two (which platform mallocs tend to like) to values slightly over
15687 powers of two (which make some platform mallocs sad).
15689 o Minor bugfixes (misc):
15690 - If exit bandwidth ever exceeds one third of total bandwidth, then
15691 use the correct formula to weight exit nodes when choosing paths.
15692 Based on patch from Mike Perry.
15693 - Choose perfectly fairly among routers when choosing by bandwidth and
15694 weighting by fraction of bandwidth provided by exits. Previously, we
15695 would choose with only approximate fairness, and correct ourselves
15696 if we ran off the end of the list.
15697 - If we require CookieAuthentication but we fail to write the
15698 cookie file, we would warn but not exit, and end up in a state
15699 where no controller could authenticate. Now we exit.
15700 - If we require CookieAuthentication, stop generating a new cookie
15701 every time we change any piece of our config.
15702 - Refuse to start with certain directory authority keys, and
15703 encourage people using them to stop.
15704 - Terminate multi-line control events properly. Original patch
15706 - Fix a minor memory leak when we fail to find enough suitable
15707 servers to choose a circuit.
15708 - Stop leaking part of the descriptor when we run into a particularly
15709 unparseable piece of it.
15712 Changes in version 0.2.0.6-alpha - 2007-08-26
15713 This sixth development snapshot features a new Vidalia version in the
15714 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
15715 the ControlPort in the default configuration, which addresses important
15718 In addition, this snapshot fixes major load balancing problems
15719 with path selection, which should speed things up a lot once many
15720 people have upgraded. The directory authorities also use a new
15721 mean-time-between-failure approach to tracking which servers are stable,
15722 rather than just looking at the most recent uptime.
15724 o New directory authorities:
15725 - Set up Tonga as the default bridge directory authority.
15728 - Directory authorities now track servers by weighted
15729 mean-times-between-failures. When we have 4 or more days of data,
15730 use measured MTBF rather than declared uptime to decide whether
15731 to call a router Stable. Implements proposal 108.
15733 o Major bugfixes (load balancing):
15734 - When choosing nodes for non-guard positions, weight guards
15735 proportionally less, since they already have enough load. Patch
15737 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15738 will allow fast Tor servers to get more attention.
15739 - When we're upgrading from an old Tor version, forget our current
15740 guards and pick new ones according to the new weightings. These
15741 three load balancing patches could raise effective network capacity
15742 by a factor of four. Thanks to Mike Perry for measurements.
15744 o Major bugfixes (descriptor parsing):
15745 - Handle unexpected whitespace better in malformed descriptors. Bug
15746 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
15749 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
15750 GETINFO for Torstat to use until it can switch to using extrainfos.
15751 - Optionally (if built with -DEXPORTMALLINFO) export the output
15752 of mallinfo via http, as tor/mallinfo.txt. Only accessible
15756 - Do not intermix bridge routers with controller-added
15757 routers. (Bugfix on 0.2.0.x)
15758 - Do not fail with an assert when accept() returns an unexpected
15759 address family. Addresses but does not wholly fix bug 483. (Bugfix
15761 - Let directory authorities startup even when they can't generate
15762 a descriptor immediately, e.g. because they don't know their
15764 - Stop putting the authentication cookie in a file called "0"
15765 in your working directory if you don't specify anything for the
15766 new CookieAuthFile option. Reported by Matt Edman.
15767 - Make it possible to read the PROTOCOLINFO response in a way that
15768 conforms to our control-spec. Reported by Matt Edman.
15769 - Fix a minor memory leak when we fail to find enough suitable
15770 servers to choose a circuit. Bugfix on 0.1.2.x.
15771 - Stop leaking part of the descriptor when we run into a particularly
15772 unparseable piece of it. Bugfix on 0.1.2.x.
15773 - Unmap the extrainfo cache file on exit.
15776 Changes in version 0.2.0.5-alpha - 2007-08-19
15777 This fifth development snapshot fixes compilation on Windows again;
15778 fixes an obnoxious client-side bug that slowed things down and put
15779 extra load on the network; gets us closer to using the v3 directory
15780 voting scheme; makes it easier for Tor controllers to use cookie-based
15781 authentication; and fixes a variety of other bugs.
15783 o Removed features:
15784 - Version 1 directories are no longer generated in full. Instead,
15785 authorities generate and serve "stub" v1 directories that list
15786 no servers. This will stop Tor versions 0.1.0.x and earlier from
15787 working, but (for security reasons) nobody should be running those
15790 o Major bugfixes (compilation, 0.2.0.x):
15791 - Try to fix Win32 compilation again: improve checking for IPv6 types.
15792 - Try to fix MSVC compilation: build correctly on platforms that do
15793 not define s6_addr16 or s6_addr32.
15794 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
15797 o Major bugfixes (stream expiration):
15798 - Expire not-yet-successful application streams in all cases if
15799 they've been around longer than SocksTimeout. Right now there are
15800 some cases where the stream will live forever, demanding a new
15801 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
15802 reported by lodger.
15804 o Minor features (directory servers):
15805 - When somebody requests a list of statuses or servers, and we have
15806 none of those, return a 404 rather than an empty 200.
15808 o Minor features (directory voting):
15809 - Store v3 consensus status consensuses on disk, and reload them
15812 o Minor features (security):
15813 - Warn about unsafe ControlPort configurations.
15814 - Refuse to start with certain directory authority keys, and
15815 encourage people using them to stop.
15817 o Minor features (controller):
15818 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15819 is valid before any authentication has been received. It tells
15820 a controller what kind of authentication is expected, and what
15821 protocol is spoken. Implements proposal 119.
15822 - New config option CookieAuthFile to choose a new location for the
15823 cookie authentication file, and config option
15824 CookieAuthFileGroupReadable to make it group-readable.
15826 o Minor features (unit testing):
15827 - Add command-line arguments to unit-test executable so that we can
15828 invoke any chosen test from the command line rather than having
15829 to run the whole test suite at once; and so that we can turn on
15830 logging for the unit tests.
15832 o Minor bugfixes (on 0.1.2.x):
15833 - If we require CookieAuthentication but we fail to write the
15834 cookie file, we would warn but not exit, and end up in a state
15835 where no controller could authenticate. Now we exit.
15836 - If we require CookieAuthentication, stop generating a new cookie
15837 every time we change any piece of our config.
15838 - When loading bandwidth history, do not believe any information in
15839 the future. Fixes bug 434.
15840 - When loading entry guard information, do not believe any information
15842 - When we have our clock set far in the future and generate an
15843 onion key, then re-set our clock to be correct, we should not stop
15844 the onion key from getting rotated.
15845 - Clean up torrc sample config file.
15846 - Do not automatically run configure from autogen.sh. This
15847 non-standard behavior tended to annoy people who have built other
15850 o Minor bugfixes (on 0.2.0.x):
15851 - Fix a bug with AutomapHostsOnResolve that would always cause
15852 the second request to fail. Bug reported by Kate. Bugfix on
15854 - Fix a bug in ADDRMAP controller replies that would sometimes
15855 try to print a NULL. Patch from tup.
15856 - Read v3 directory authority keys from the right location.
15857 - Numerous bugfixes to directory voting code.
15860 Changes in version 0.1.2.16 - 2007-08-01
15861 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
15862 remote attacker in certain situations to rewrite the user's torrc
15863 configuration file. This can completely compromise anonymity of users
15864 in most configurations, including those running the Vidalia bundles,
15865 TorK, etc. Or worse.
15867 o Major security fixes:
15868 - Close immediately after missing authentication on control port;
15869 do not allow multiple authentication attempts.
15872 Changes in version 0.2.0.4-alpha - 2007-08-01
15873 This fourth development snapshot fixes a critical security vulnerability
15874 for most users, specifically those running Vidalia, TorK, etc. Everybody
15875 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
15877 o Major security fixes:
15878 - Close immediately after missing authentication on control port;
15879 do not allow multiple authentication attempts.
15881 o Major bugfixes (compilation):
15882 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
15885 o Minor features (performance):
15886 - Be even more aggressive about releasing RAM from small
15887 empty buffers. Thanks to our free-list code, this shouldn't be too
15888 performance-intensive.
15889 - Disable sentinel-based debugging for buffer code: we squashed all
15890 the bugs that this was supposed to detect a long time ago, and
15891 now its only effect is to change our buffer sizes from nice
15892 powers of two (which platform mallocs tend to like) to values
15893 slightly over powers of two (which make some platform mallocs sad).
15894 - Log malloc statistics from mallinfo() on platforms where it
15898 Changes in version 0.2.0.3-alpha - 2007-07-29
15899 This third development snapshot introduces new experimental
15900 blocking-resistance features and a preliminary version of the v3
15901 directory voting design, and includes many other smaller features
15905 - The first pieces of our "bridge" design for blocking-resistance
15906 are implemented. People can run bridge directory authorities;
15907 people can run bridges; and people can configure their Tor clients
15908 with a set of bridges to use as the first hop into the Tor network.
15909 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
15911 - Create listener connections before we setuid to the configured
15912 User and Group. Now non-Windows users can choose port values
15913 under 1024, start Tor as root, and have Tor bind those ports
15914 before it changes to another UID. (Windows users could already
15916 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
15917 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
15918 on "vserver" accounts. (Patch from coderman.)
15919 - Be even more aggressive about separating local traffic from relayed
15920 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
15922 o Major features (experimental):
15923 - First cut of code for "v3 dir voting": directory authorities will
15924 vote on a common network status document rather than each publishing
15925 their own opinion. This code needs more testing and more corner-case
15926 handling before it's ready for use.
15929 - Directory authorities now call routers Fast if their bandwidth is
15930 at least 100KB/s, and consider their bandwidth adequate to be a
15931 Guard if it is at least 250KB/s, no matter the medians. This fix
15932 complements proposal 107. [Bugfix on 0.1.2.x]
15933 - Directory authorities now never mark more than 3 servers per IP as
15934 Valid and Running. (Implements proposal 109, by Kevin Bauer and
15936 - Minor change to organizationName and commonName generation
15937 procedures in TLS certificates during Tor handshakes, to invalidate
15938 some earlier censorware approaches. This is not a long-term
15939 solution, but applying it will give us a bit of time to look into
15940 the epidemiology of countermeasures as they spread.
15942 o Major bugfixes (directory):
15943 - Rewrite directory tokenization code to never run off the end of
15944 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
15946 o Minor features (controller):
15947 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
15948 match requests to applications. (Patch from Robert Hogan.)
15949 - Report address and port correctly on connections to DNSPort. (Patch
15950 from Robert Hogan.)
15951 - Add a RESOLVE command to launch hostname lookups. (Original patch
15952 from Robert Hogan.)
15953 - Add GETINFO status/enough-dir-info to let controllers tell whether
15954 Tor has downloaded sufficient directory information. (Patch
15956 - You can now use the ControlSocket option to tell Tor to listen for
15957 controller connections on Unix domain sockets on systems that
15958 support them. (Patch from Peter Palfrader.)
15959 - STREAM NEW events are generated for DNSPort requests and for
15960 tunneled directory connections. (Patch from Robert Hogan.)
15961 - New "GETINFO address-mappings/*" command to get address mappings
15962 with expiry information. "addr-mappings/*" is now deprecated.
15965 o Minor features (misc):
15966 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
15968 - The tor-gencert tool for v3 directory authorities now creates all
15969 files as readable to the file creator only, and write-protects
15970 the authority identity key.
15971 - When dumping memory usage, list bytes used in buffer memory
15973 - When running with dmalloc, dump more stats on hup and on exit.
15974 - Directory authorities now fail quickly and (relatively) harmlessly
15975 if they generate a network status document that is somehow
15978 o Traffic load balancing improvements:
15979 - If exit bandwidth ever exceeds one third of total bandwidth, then
15980 use the correct formula to weight exit nodes when choosing paths.
15981 (Based on patch from Mike Perry.)
15982 - Choose perfectly fairly among routers when choosing by bandwidth and
15983 weighting by fraction of bandwidth provided by exits. Previously, we
15984 would choose with only approximate fairness, and correct ourselves
15985 if we ran off the end of the list. [Bugfix on 0.1.2.x]
15987 o Performance improvements:
15988 - Be more aggressive with freeing buffer RAM or putting it on the
15990 - Use Critical Sections rather than Mutexes for synchronizing threads
15991 on win32; Mutexes are heavier-weight, and designed for synchronizing
15994 o Deprecated and removed features:
15995 - RedirectExits is now deprecated.
15996 - Stop allowing address masks that do not correspond to bit prefixes.
15997 We have warned about these for a really long time; now it's time
15998 to reject them. (Patch from croup.)
16000 o Minor bugfixes (directory):
16001 - Fix another crash bug related to extra-info caching. (Bug found by
16002 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
16003 - Directories no longer return a "304 not modified" when they don't
16004 have the networkstatus the client asked for. Also fix a memory
16005 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
16006 - We had accidentally labelled 0.1.2.x directory servers as not
16007 suitable for begin_dir requests, and had labelled no directory
16008 servers as suitable for uploading extra-info documents. [Bugfix
16011 o Minor bugfixes (dns):
16012 - Fix a crash when DNSPort is set more than once. (Patch from Robert
16013 Hogan.) [Bugfix on 0.2.0.2-alpha]
16014 - Add DNSPort connections to the global connection list, so that we
16015 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
16017 - Fix a dangling reference that could lead to a crash when DNSPort is
16018 changed or closed (Patch from Robert Hogan.) [Bugfix on
16021 o Minor bugfixes (controller):
16022 - Provide DNS expiry times in GMT, not in local time. For backward
16023 compatibility, ADDRMAP events only provide GMT expiry in an extended
16024 field. "GETINFO address-mappings" always does the right thing.
16025 - Use CRLF line endings properly in NS events.
16026 - Terminate multi-line control events properly. (Original patch
16027 from tup.) [Bugfix on 0.1.2.x-alpha]
16028 - Do not include spaces in SOURCE_ADDR fields in STREAM
16029 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
16032 Changes in version 0.1.2.15 - 2007-07-17
16033 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
16034 problems, fixes compilation on BSD, and fixes a variety of other
16035 bugs. Everybody should upgrade.
16037 o Major bugfixes (compilation):
16038 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
16040 o Major bugfixes (crashes):
16041 - Try even harder not to dereference the first character after
16042 an mmap(). Reported by lodger.
16043 - Fix a crash bug in directory authorities when we re-number the
16044 routerlist while inserting a new router.
16045 - When the cached-routers file is an even multiple of the page size,
16046 don't run off the end and crash. (Fixes bug 455; based on idea
16048 - Fix eventdns.c behavior on Solaris: It is critical to include
16049 orconfig.h _before_ sys/types.h, so that we can get the expected
16050 definition of _FILE_OFFSET_BITS.
16052 o Major bugfixes (security):
16053 - Fix a possible buffer overrun when using BSD natd support. Bug
16055 - When sending destroy cells from a circuit's origin, don't include
16056 the reason for tearing down the circuit. The spec says we didn't,
16057 and now we actually don't. Reported by lodger.
16058 - Keep streamids from different exits on a circuit separate. This
16059 bug may have allowed other routers on a given circuit to inject
16060 cells into streams. Reported by lodger; fixes bug 446.
16061 - If there's a never-before-connected-to guard node in our list,
16062 never choose any guards past it. This way we don't expand our
16063 guard list unless we need to.
16065 o Minor bugfixes (guard nodes):
16066 - Weight guard selection by bandwidth, so that low-bandwidth nodes
16067 don't get overused as guards.
16069 o Minor bugfixes (directory):
16070 - Correctly count the number of authorities that recommend each
16071 version. Previously, we were under-counting by 1.
16072 - Fix a potential crash bug when we load many server descriptors at
16073 once and some of them make others of them obsolete. Fixes bug 458.
16075 o Minor bugfixes (hidden services):
16076 - Stop tearing down the whole circuit when the user asks for a
16077 connection to a port that the hidden service didn't configure.
16080 o Minor bugfixes (misc):
16081 - On Windows, we were preventing other processes from reading
16082 cached-routers while Tor was running. Reported by janbar.
16083 - Fix a possible (but very unlikely) bug in picking routers by
16084 bandwidth. Add a log message to confirm that it is in fact
16085 unlikely. Patch from lodger.
16086 - Backport a couple of memory leak fixes.
16087 - Backport miscellaneous cosmetic bugfixes.
16090 Changes in version 0.2.0.2-alpha - 2007-06-02
16091 o Major bugfixes on 0.2.0.1-alpha:
16092 - Fix an assertion failure related to servers without extra-info digests.
16093 Resolves bugs 441 and 442.
16095 o Minor features (directory):
16096 - Support "If-Modified-Since" when answering HTTP requests for
16097 directories, running-routers documents, and network-status documents.
16098 (There's no need to support it for router descriptors, since those
16099 are downloaded by descriptor digest.)
16101 o Minor build issues:
16102 - Clear up some MIPSPro compiler warnings.
16103 - When building from a tarball on a machine that happens to have SVK
16104 installed, report the micro-revision as whatever version existed
16105 in the tarball, not as "x".
16108 Changes in version 0.2.0.1-alpha - 2007-06-01
16109 This early development snapshot provides new features for people running
16110 Tor as both a client and a server (check out the new RelayBandwidth
16111 config options); lets Tor run as a DNS proxy; and generally moves us
16112 forward on a lot of fronts.
16114 o Major features, server usability:
16115 - New config options RelayBandwidthRate and RelayBandwidthBurst:
16116 a separate set of token buckets for relayed traffic. Right now
16117 relayed traffic is defined as answers to directory requests, and
16118 OR connections that don't have any local circuits on them.
16120 o Major features, client usability:
16121 - A client-side DNS proxy feature to replace the need for
16122 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
16123 for DNS requests on port 9999, use the Tor network to resolve them
16124 anonymously, and send the reply back like a regular DNS server.
16125 The code still only implements a subset of DNS.
16126 - Make PreferTunneledDirConns and TunnelDirConns work even when
16127 we have no cached directory info. This means Tor clients can now
16128 do all of their connections protected by TLS.
16130 o Major features, performance and efficiency:
16131 - Directory authorities accept and serve "extra info" documents for
16132 routers. These documents contain fields from router descriptors
16133 that aren't usually needed, and that use a lot of excess
16134 bandwidth. Once these fields are removed from router descriptors,
16135 the bandwidth savings should be about 60%. [Partially implements
16137 - Servers upload extra-info documents to any authority that accepts
16138 them. Authorities (and caches that have been configured to download
16139 extra-info documents) download them as needed. [Partially implements
16141 - Change the way that Tor buffers data that it is waiting to write.
16142 Instead of queueing data cells in an enormous ring buffer for each
16143 client->OR or OR->OR connection, we now queue cells on a separate
16144 queue for each circuit. This lets us use less slack memory, and
16145 will eventually let us be smarter about prioritizing different kinds
16147 - Use memory pools to allocate cells with better speed and memory
16148 efficiency, especially on platforms where malloc() is inefficient.
16149 - Stop reading on edge connections when their corresponding circuit
16150 buffers are full; start again as the circuits empty out.
16152 o Major features, other:
16153 - Add an HSAuthorityRecordStats option that hidden service authorities
16154 can use to track statistics of overall hidden service usage without
16155 logging information that would be very useful to an attacker.
16156 - Start work implementing multi-level keys for directory authorities:
16157 Add a standalone tool to generate key certificates. (Proposal 103.)
16160 - Directory authorities now call routers Stable if they have an
16161 uptime of at least 30 days, even if that's not the median uptime
16162 in the network. Implements proposal 107, suggested by Kevin Bauer
16165 o Minor fixes (resource management):
16166 - Count the number of open sockets separately from the number
16167 of active connection_t objects. This will let us avoid underusing
16168 our allocated connection limit.
16169 - We no longer use socket pairs to link an edge connection to an
16170 anonymous directory connection or a DirPort test connection.
16171 Instead, we track the link internally and transfer the data
16172 in-process. This saves two sockets per "linked" connection (at the
16173 client and at the server), and avoids the nasty Windows socketpair()
16175 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
16176 for every single inactive connection_t. Free items from the
16177 4k/16k-buffer free lists when they haven't been used for a while.
16179 o Minor features (build):
16180 - Make autoconf search for libevent, openssl, and zlib consistently.
16181 - Update deprecated macros in configure.in.
16182 - When warning about missing headers, tell the user to let us
16183 know if the compile succeeds anyway, so we can downgrade the
16185 - Include the current subversion revision as part of the version
16186 string: either fetch it directly if we're in an SVN checkout, do
16187 some magic to guess it if we're in an SVK checkout, or use
16188 the last-detected version if we're building from a .tar.gz.
16189 Use this version consistently in log messages.
16191 o Minor features (logging):
16192 - Always prepend "Bug: " to any log message about a bug.
16193 - Put a platform string (e.g. "Linux i686") in the startup log
16194 message, so when people paste just their logs, we know if it's
16195 OpenBSD or Windows or what.
16196 - When logging memory usage, break down memory used in buffers by
16199 o Minor features (directory system):
16200 - New config option V2AuthoritativeDirectory that all directory
16201 authorities should set. This will let future authorities choose
16202 not to serve V2 directory information.
16203 - Directory authorities allow multiple router descriptors and/or extra
16204 info documents to be uploaded in a single go. This will make
16205 implementing proposal 104 simpler.
16207 o Minor features (controller):
16208 - Add a new config option __DisablePredictedCircuits designed for
16209 use by the controller, when we don't want Tor to build any circuits
16211 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
16212 so we can exit from the middle of the circuit.
16213 - Implement "getinfo status/circuit-established".
16214 - Implement "getinfo status/version/..." so a controller can tell
16215 whether the current version is recommended, and whether any versions
16216 are good, and how many authorities agree. (Patch from shibz.)
16218 o Minor features (hidden services):
16219 - Allow multiple HiddenServicePort directives with the same virtual
16220 port; when they occur, the user is sent round-robin to one
16221 of the target ports chosen at random. Partially fixes bug 393 by
16222 adding limited ad-hoc round-robining.
16224 o Minor features (other):
16226 - Add a new AutomapHostsOnResolve option: when it is enabled, any
16227 resolve request for hosts matching a given pattern causes Tor to
16228 generate an internal virtual address mapping for that host. This
16229 allows DNSPort to work sensibly with hidden service users. By
16230 default, .exit and .onion addresses are remapped; the list of
16231 patterns can be reconfigured with AutomapHostsSuffixes.
16232 - Add an "-F" option to tor-resolve to force a resolve for a .onion
16233 address. Thanks to the AutomapHostsOnResolve option, this is no
16234 longer a completely silly thing to do.
16235 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
16236 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
16237 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
16238 minus 1 byte: the actual maximum declared bandwidth.
16240 o Removed features:
16241 - Removed support for the old binary "version 0" controller protocol.
16242 This has been deprecated since 0.1.1, and warnings have been issued
16243 since 0.1.2. When we encounter a v0 control message, we now send
16244 back an error and close the connection.
16245 - Remove the old "dns worker" server DNS code: it hasn't been default
16246 since 0.1.2.2-alpha, and all the servers seem to be using the new
16249 o Minor bugfixes (portability):
16250 - Even though Windows is equally happy with / and \ as path separators,
16251 try to use \ consistently on Windows and / consistently on Unix: it
16252 makes the log messages nicer.
16253 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
16254 - Read resolv.conf files correctly on platforms where read() returns
16255 partial results on small file reads.
16257 o Minor bugfixes (directory):
16258 - Correctly enforce that elements of directory objects do not appear
16259 more often than they are allowed to appear.
16260 - When we are reporting the DirServer line we just parsed, we were
16261 logging the second stanza of the key fingerprint, not the first.
16263 o Minor bugfixes (logging):
16264 - When we hit an EOF on a log (probably because we're shutting down),
16265 don't try to remove the log from the list: just mark it as
16266 unusable. (Bulletproofs against bug 222.)
16268 o Minor bugfixes (other):
16269 - In the exitlist script, only consider the most recently published
16270 server descriptor for each server. Also, when the user requests
16271 a list of servers that _reject_ connections to a given address,
16272 explicitly exclude the IPs that also have servers that accept
16273 connections to that address. (Resolves bug 405.)
16274 - Stop allowing hibernating servers to be "stable" or "fast".
16275 - On Windows, we were preventing other processes from reading
16276 cached-routers while Tor was running. (Reported by janbar)
16277 - Make the NodeFamilies config option work. (Reported by
16278 lodger -- it has never actually worked, even though we added it
16280 - Check return values from pthread_mutex functions.
16281 - Don't save non-general-purpose router descriptors to the disk cache,
16282 because we have no way of remembering what their purpose was when
16284 - Add even more asserts to hunt down bug 417.
16285 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
16286 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
16287 Add a log message to confirm that it is in fact unlikely.
16289 o Minor bugfixes (controller):
16290 - Make 'getinfo fingerprint' return a 551 error if we're not a
16291 server, so we match what the control spec claims we do. Reported
16293 - Fix a typo in an error message when extendcircuit fails that
16294 caused us to not follow the \r\n-based delimiter protocol. Reported
16297 o Code simplifications and refactoring:
16298 - Stop passing around circuit_t and crypt_path_t pointers that are
16299 implicit in other procedure arguments.
16300 - Drop the old code to choke directory connections when the
16301 corresponding OR connections got full: thanks to the cell queue
16302 feature, OR conns don't get full any more.
16303 - Make dns_resolve() handle attaching connections to circuits
16304 properly, so the caller doesn't have to.
16305 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
16306 - Keep the connection array as a dynamic smartlist_t, rather than as
16307 a fixed-sized array. This is important, as the number of connections
16308 is becoming increasingly decoupled from the number of sockets.
16311 Changes in version 0.1.2.14 - 2007-05-25
16312 Tor 0.1.2.14 changes the addresses of two directory authorities (this
16313 change especially affects those who serve or use hidden services),
16314 and fixes several other crash- and security-related bugs.
16316 o Directory authority changes:
16317 - Two directory authorities (moria1 and moria2) just moved to new
16318 IP addresses. This change will particularly affect those who serve
16319 or use hidden services.
16321 o Major bugfixes (crashes):
16322 - If a directory server runs out of space in the connection table
16323 as it's processing a begin_dir request, it will free the exit stream
16324 but leave it attached to the circuit, leading to unpredictable
16325 behavior. (Reported by seeess, fixes bug 425.)
16326 - Fix a bug in dirserv_remove_invalid() that would cause authorities
16327 to corrupt memory under some really unlikely scenarios.
16328 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
16329 - Avoid segfaults when reading from mmaped descriptor file. (Reported
16332 o Major bugfixes (security):
16333 - When choosing an entry guard for a circuit, avoid using guards
16334 that are in the same family as the chosen exit -- not just guards
16335 that are exactly the chosen exit. (Reported by lodger.)
16337 o Major bugfixes (resource management):
16338 - If a directory authority is down, skip it when deciding where to get
16339 networkstatus objects or descriptors. Otherwise we keep asking
16340 every 10 seconds forever. Fixes bug 384.
16341 - Count it as a failure if we fetch a valid network-status but we
16342 don't want to keep it. Otherwise we'll keep fetching it and keep
16343 not wanting to keep it. Fixes part of bug 422.
16344 - If all of our dirservers have given us bad or no networkstatuses
16345 lately, then stop hammering them once per minute even when we
16346 think they're failed. Fixes another part of bug 422.
16349 - Actually set the purpose correctly for descriptors inserted with
16350 purpose=controller.
16351 - When we have k non-v2 authorities in our DirServer config,
16352 we ignored the last k authorities in the list when updating our
16354 - Correctly back-off from requesting router descriptors that we are
16355 having a hard time downloading.
16356 - Read resolv.conf files correctly on platforms where read() returns
16357 partial results on small file reads.
16358 - Don't rebuild the entire router store every time we get 32K of
16359 routers: rebuild it when the journal gets very large, or when
16360 the gaps in the store get very large.
16363 - When routers publish SVN revisions in their router descriptors,
16364 authorities now include those versions correctly in networkstatus
16366 - Warn when using a version of libevent before 1.3b to run a server on
16367 OSX or BSD: these versions interact badly with userspace threads.
16370 Changes in version 0.1.2.13 - 2007-04-24
16371 This release features some major anonymity fixes, such as safer path
16372 selection; better client performance; faster bootstrapping, better
16373 address detection, and better DNS support for servers; write limiting as
16374 well as read limiting to make servers easier to run; and a huge pile of
16375 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
16377 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
16378 of the Freenode IRC network, remembering his patience and vision for
16379 free speech on the Internet.
16382 - Fix a memory leak when we ask for "all" networkstatuses and we
16383 get one we don't recognize.
16384 - Add more asserts to hunt down bug 417.
16385 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
16388 Changes in version 0.1.2.12-rc - 2007-03-16
16390 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
16391 directory information requested inside Tor connections (i.e. via
16392 begin_dir cells). It only triggered when the same connection was
16393 serving other data at the same time. Reported by seeess.
16396 - When creating a circuit via the controller, send a 'launched'
16397 event when we're done, so we follow the spec better.
16400 Changes in version 0.1.2.11-rc - 2007-03-15
16401 o Minor bugfixes (controller), reported by daejees:
16402 - Correct the control spec to match how the code actually responds
16403 to 'getinfo addr-mappings/*'.
16404 - The control spec described a GUARDS event, but the code
16405 implemented a GUARD event. Standardize on GUARD, but let people
16406 ask for GUARDS too.
16409 Changes in version 0.1.2.10-rc - 2007-03-07
16410 o Major bugfixes (Windows):
16411 - Do not load the NT services library functions (which may not exist)
16412 just to detect if we're a service trying to shut down. Now we run
16413 on Win98 and friends again.
16415 o Minor bugfixes (other):
16416 - Clarify a couple of log messages.
16417 - Fix a misleading socks5 error number.
16420 Changes in version 0.1.2.9-rc - 2007-03-02
16421 o Major bugfixes (Windows):
16422 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
16423 of the usual GCC "%llu". This prevents a bug when saving 64-bit
16424 int configuration values: the high-order 32 bits would get
16425 truncated. In particular, we were being bitten by the default
16426 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
16427 and maybe also bug 397.)
16429 o Minor bugfixes (performance):
16430 - Use OpenSSL's AES implementation on platforms where it's faster.
16431 This could save us as much as 10% CPU usage.
16433 o Minor bugfixes (server):
16434 - Do not rotate onion key immediately after setting it for the first
16437 o Minor bugfixes (directory authorities):
16438 - Stop calling servers that have been hibernating for a long time
16439 "stable". Also, stop letting hibernating or obsolete servers affect
16440 uptime and bandwidth cutoffs.
16441 - Stop listing hibernating servers in the v1 directory.
16443 o Minor bugfixes (hidden services):
16444 - Upload hidden service descriptors slightly less often, to reduce
16445 load on authorities.
16447 o Minor bugfixes (other):
16448 - Fix an assert that could trigger if a controller quickly set then
16449 cleared EntryNodes. Bug found by Udo van den Heuvel.
16450 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
16452 - Fix a potential race condition in the rpm installer. Found by
16454 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
16455 of 2 as indicating that the server is completely bad; it sometimes
16456 means that the server is just bad for the request in question. (may fix
16457 the last of bug 326.)
16458 - Disable encrypted directory connections when we don't have a server
16459 descriptor for the destination. We'll get this working again in
16463 Changes in version 0.1.2.8-beta - 2007-02-26
16464 o Major bugfixes (crashes):
16465 - Stop crashing when the controller asks us to resetconf more than
16466 one config option at once. (Vidalia 0.0.11 does this.)
16467 - Fix a crash that happened on Win98 when we're given command-line
16468 arguments: don't try to load NT service functions from advapi32.dll
16469 except when we need them. (Bug introduced in 0.1.2.7-alpha;
16471 - Fix a longstanding obscure crash bug that could occur when
16472 we run out of DNS worker processes. (Resolves bug 390.)
16474 o Major bugfixes (hidden services):
16475 - Correctly detect whether hidden service descriptor downloads are
16476 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
16478 o Major bugfixes (accounting):
16479 - When we start during an accounting interval before it's time to wake
16480 up, remember to wake up at the correct time. (May fix bug 342.)
16482 o Minor bugfixes (controller):
16483 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
16484 clear the corresponding on_circuit variable, and remember later
16485 that we don't need to send a redundant CLOSED event. Resolves part
16487 - Report events where a resolve succeeded or where we got a socks
16488 protocol error correctly, rather than calling both of them
16490 - Change reported stream target addresses to IP consistently when
16491 we finally get the IP from an exit node.
16492 - Send log messages to the controller even if they happen to be very
16495 o Minor bugfixes (other):
16496 - Display correct results when reporting which versions are
16497 recommended, and how recommended they are. (Resolves bug 383.)
16498 - Improve our estimates for directory bandwidth to be less random:
16499 guess that an unrecognized directory will have the average bandwidth
16500 from all known directories, not that it will have the average
16501 bandwidth from those directories earlier than it on the list.
16502 - If we start a server with ClientOnly 1, then set ClientOnly to 0
16503 and hup, stop triggering an assert based on an empty onion_key.
16504 - On platforms with no working mmap() equivalent, don't warn the
16505 user when cached-routers doesn't exist.
16506 - Warn the user when mmap() [or its equivalent] fails for some reason
16507 other than file-not-found.
16508 - Don't warn the user when cached-routers.new doesn't exist: that's
16509 perfectly fine when starting up for the first time.
16510 - When EntryNodes are configured, rebuild the guard list to contain,
16511 in order: the EntryNodes that were guards before; the rest of the
16512 EntryNodes; the nodes that were guards before.
16513 - Mask out all signals in sub-threads; only the libevent signal
16514 handler should be processing them. This should prevent some crashes
16515 on some machines using pthreads. (Patch from coderman.)
16516 - Fix switched arguments on memset in the implementation of
16517 tor_munmap() for systems with no mmap() call.
16518 - When Tor receives a router descriptor that it asked for, but
16519 no longer wants (because it has received fresh networkstatuses
16520 in the meantime), do not warn the user. Cache the descriptor if
16521 we're a cache; drop it if we aren't.
16522 - Make earlier entry guards _really_ get retried when the network
16524 - On a malformed DNS reply, always give an error to the corresponding
16526 - Build with recent libevents on platforms that do not define the
16527 nonstandard types "u_int8_t" and friends.
16529 o Minor features (controller):
16530 - Warn the user when an application uses the obsolete binary v0
16531 control protocol. We're planning to remove support for it during
16532 the next development series, so it's good to give people some
16534 - Add STREAM_BW events to report per-entry-stream bandwidth
16535 use. (Patch from Robert Hogan.)
16536 - Rate-limit SIGNEWNYM signals in response to controllers that
16537 impolitely generate them for every single stream. (Patch from
16538 mwenge; closes bug 394.)
16539 - Make REMAP stream events have a SOURCE (cache or exit), and
16540 make them generated in every case where we get a successful
16541 connected or resolved cell.
16543 o Minor bugfixes (performance):
16544 - Call router_have_min_dir_info half as often. (This is showing up in
16545 some profiles, but not others.)
16546 - When using GCC, make log_debug never get called at all, and its
16547 arguments never get evaluated, when no debug logs are configured.
16548 (This is showing up in some profiles, but not others.)
16551 - Remove some never-implemented options. Mark PathlenCoinWeight as
16553 - Implement proposal 106: Stop requiring clients to have well-formed
16554 certificates; stop checking nicknames in certificates. (Clients
16555 have certificates so that they can look like Tor servers, but in
16556 the future we might want to allow them to look like regular TLS
16557 clients instead. Nicknames in certificates serve no purpose other
16558 than making our protocol easier to recognize on the wire.)
16559 - Revise messages on handshake failure again to be even more clear about
16560 which are incoming connections and which are outgoing.
16561 - Discard any v1 directory info that's over 1 month old (for
16562 directories) or over 1 week old (for running-routers lists).
16563 - Do not warn when individual nodes in the configuration's EntryNodes,
16564 ExitNodes, etc are down: warn only when all possible nodes
16565 are down. (Fixes bug 348.)
16566 - Always remove expired routers and networkstatus docs before checking
16567 whether we have enough information to build circuits. (Fixes
16569 - Put a lower-bound on MaxAdvertisedBandwidth.
16572 Changes in version 0.1.2.7-alpha - 2007-02-06
16573 o Major bugfixes (rate limiting):
16574 - Servers decline directory requests much more aggressively when
16575 they're low on bandwidth. Otherwise they end up queueing more and
16576 more directory responses, which can't be good for latency.
16577 - But never refuse directory requests from local addresses.
16578 - Fix a memory leak when sending a 503 response for a networkstatus
16580 - Be willing to read or write on local connections (e.g. controller
16581 connections) even when the global rate limiting buckets are empty.
16582 - If our system clock jumps back in time, don't publish a negative
16583 uptime in the descriptor. Also, don't let the global rate limiting
16584 buckets go absurdly negative.
16585 - Flush local controller connection buffers periodically as we're
16586 writing to them, so we avoid queueing 4+ megabytes of data before
16589 o Major bugfixes (NT services):
16590 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
16591 command-line flag so that admins can override the default by saying
16592 "tor --service install --user "SomeUser"". This will not affect
16593 existing installed services. Also, warn the user that the service
16594 will look for its configuration file in the service user's
16595 %appdata% directory. (We can't do the 'hardwire the user's appdata
16596 directory' trick any more, since we may not have read access to that
16599 o Major bugfixes (other):
16600 - Previously, we would cache up to 16 old networkstatus documents
16601 indefinitely, if they came from nontrusted authorities. Now we
16602 discard them if they are more than 10 days old.
16603 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
16605 - Detect and reject malformed DNS responses containing circular
16607 - If exits are rare enough that we're not marking exits as guards,
16608 ignore exit bandwidth when we're deciding the required bandwidth
16610 - When we're handling a directory connection tunneled over Tor,
16611 don't fill up internal memory buffers with all the data we want
16612 to tunnel; instead, only add it if the OR connection that will
16613 eventually receive it has some room for it. (This can lead to
16614 slowdowns in tunneled dir connections; a better solution will have
16615 to wait for 0.2.0.)
16617 o Minor bugfixes (dns):
16618 - Add some defensive programming to eventdns.c in an attempt to catch
16619 possible memory-stomping bugs.
16620 - Detect and reject DNS replies containing IPv4 or IPv6 records with
16621 an incorrect number of bytes. (Previously, we would ignore the
16623 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
16624 in the correct order, and doesn't crash.
16625 - Free memory held in recently-completed DNS lookup attempts on exit.
16626 This was not a memory leak, but may have been hiding memory leaks.
16627 - Handle TTL values correctly on reverse DNS lookups.
16628 - Treat failure to parse resolv.conf as an error.
16630 o Minor bugfixes (other):
16631 - Fix crash with "tor --list-fingerprint" (reported by seeess).
16632 - When computing clock skew from directory HTTP headers, consider what
16633 time it was when we finished asking for the directory, not what
16635 - Expire socks connections if they spend too long waiting for the
16636 handshake to finish. Previously we would let them sit around for
16637 days, if the connecting application didn't close them either.
16638 - And if the socks handshake hasn't started, don't send a
16639 "DNS resolve socks failed" handshake reply; just close it.
16640 - Stop using C functions that OpenBSD's linker doesn't like.
16641 - Don't launch requests for descriptors unless we have networkstatuses
16642 from at least half of the authorities. This delays the first
16643 download slightly under pathological circumstances, but can prevent
16644 us from downloading a bunch of descriptors we don't need.
16645 - Do not log IPs with TLS failures for incoming TLS
16646 connections. (Fixes bug 382.)
16647 - If the user asks to use invalid exit nodes, be willing to use
16649 - Stop using the reserved ac_cv namespace in our configure script.
16650 - Call stat() slightly less often; use fstat() when possible.
16651 - Refactor the way we handle pending circuits when an OR connection
16652 completes or fails, in an attempt to fix a rare crash bug.
16653 - Only rewrite a conn's address based on X-Forwarded-For: headers
16654 if it's a parseable public IP address; and stop adding extra quotes
16655 to the resulting address.
16658 - Weight directory requests by advertised bandwidth. Now we can
16659 let servers enable write limiting but still allow most clients to
16660 succeed at their directory requests. (We still ignore weights when
16661 choosing a directory authority; I hope this is a feature.)
16664 - Create a new file ReleaseNotes which was the old ChangeLog. The
16665 new ChangeLog file now includes the summaries for all development
16667 - Check for addresses with invalid characters at the exit as well
16668 as at the client, and warn less verbosely when they fail. You can
16669 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
16670 - Adapt a patch from goodell to let the contrib/exitlist script
16671 take arguments rather than require direct editing.
16672 - Inform the server operator when we decide not to advertise a
16673 DirPort due to AccountingMax enabled or a low BandwidthRate. It
16674 was confusing Zax, so now we're hopefully more helpful.
16675 - Bring us one step closer to being able to establish an encrypted
16676 directory tunnel without knowing a descriptor first. Still not
16677 ready yet. As part of the change, now assume we can use a
16678 create_fast cell if we don't know anything about a router.
16679 - Allow exit nodes to use nameservers running on ports other than 53.
16680 - Servers now cache reverse DNS replies.
16681 - Add an --ignore-missing-torrc command-line option so that we can
16682 get the "use sensible defaults if the configuration file doesn't
16683 exist" behavior even when specifying a torrc location on the command
16686 o Minor features (controller):
16687 - Track reasons for OR connection failure; make these reasons
16688 available via the controller interface. (Patch from Mike Perry.)
16689 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
16690 can learn when clients are sending malformed hostnames to Tor.
16691 - Clean up documentation for controller status events.
16692 - Add a REMAP status to stream events to note that a stream's
16693 address has changed because of a cached address or a MapAddress
16697 Changes in version 0.1.2.6-alpha - 2007-01-09
16699 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
16700 connection handles more than 4 gigs in either direction, we crash.
16701 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
16702 advertised exit node, somebody might try to exit from us when
16703 we're bootstrapping and before we've built our descriptor yet.
16704 Refuse the connection rather than crashing.
16707 - Warn if we (as a server) find that we've resolved an address that we
16708 weren't planning to resolve.
16709 - Warn that using select() on any libevent version before 1.1 will be
16710 unnecessarily slow (even for select()).
16711 - Flush ERR-level controller status events just like we currently
16712 flush ERR-level log events, so that a Tor shutdown doesn't prevent
16713 the controller from learning about current events.
16715 o Minor features (more controller status events):
16716 - Implement EXTERNAL_ADDRESS server status event so controllers can
16717 learn when our address changes.
16718 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
16719 can learn when directories reject our descriptor.
16720 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
16721 can learn when a client application is speaking a non-socks protocol
16723 - Implement DANGEROUS_SOCKS client status event so controllers
16724 can learn when a client application is leaking DNS addresses.
16725 - Implement BUG general status event so controllers can learn when
16726 Tor is unhappy about its internal invariants.
16727 - Implement CLOCK_SKEW general status event so controllers can learn
16728 when Tor thinks the system clock is set incorrectly.
16729 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
16730 server status events so controllers can learn when their descriptors
16731 are accepted by a directory.
16732 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
16733 server status events so controllers can learn about Tor's progress in
16734 deciding whether it's reachable from the outside.
16735 - Implement BAD_LIBEVENT general status event so controllers can learn
16736 when we have a version/method combination in libevent that needs to
16738 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
16739 and DNS_USELESS server status events so controllers can learn
16740 about changes to DNS server status.
16742 o Minor features (directory):
16743 - Authorities no longer recommend exits as guards if this would shift
16744 too much load to the exit nodes.
16747 Changes in version 0.1.2.5-alpha - 2007-01-06
16749 - Enable write limiting as well as read limiting. Now we sacrifice
16750 capacity if we're pushing out lots of directory traffic, rather
16751 than overrunning the user's intended bandwidth limits.
16752 - Include TLS overhead when counting bandwidth usage; previously, we
16753 would count only the bytes sent over TLS, but not the bytes used
16755 - Support running the Tor service with a torrc not in the same
16756 directory as tor.exe and default to using the torrc located in
16757 the %appdata%\Tor\ of the user who installed the service. Patch
16759 - Servers now check for the case when common DNS requests are going to
16760 wildcarded addresses (i.e. all getting the same answer), and change
16761 their exit policy to reject *:* if it's happening.
16762 - Implement BEGIN_DIR cells, so we can connect to the directory
16763 server via TLS to do encrypted directory requests rather than
16764 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
16765 config options if you like.
16767 o Minor features (config and docs):
16768 - Start using the state file to store bandwidth accounting data:
16769 the bw_accounting file is now obsolete. We'll keep generating it
16770 for a while for people who are still using 0.1.2.4-alpha.
16771 - Try to batch changes to the state file so that we do as few
16772 disk writes as possible while still storing important things in
16774 - The state file and the bw_accounting file get saved less often when
16775 the AvoidDiskWrites config option is set.
16776 - Make PIDFile work on Windows (untested).
16777 - Add internal descriptions for a bunch of configuration options:
16778 accessible via controller interface and in comments in saved
16780 - Reject *:563 (NNTPS) in the default exit policy. We already reject
16781 NNTP by default, so this seems like a sensible addition.
16782 - Clients now reject hostnames with invalid characters. This should
16783 avoid some inadvertent info leaks. Add an option
16784 AllowNonRFC953Hostnames to disable this behavior, in case somebody
16785 is running a private network with hosts called @, !, and #.
16786 - Add a maintainer script to tell us which options are missing
16787 documentation: "make check-docs".
16788 - Add a new address-spec.txt document to describe our special-case
16789 addresses: .exit, .onion, and .noconnnect.
16791 o Minor features (DNS):
16792 - Ongoing work on eventdns infrastructure: now it has dns server
16793 and ipv6 support. One day Tor will make use of it.
16794 - Add client-side caching for reverse DNS lookups.
16795 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
16796 - When we change nameservers or IP addresses, reset and re-launch
16797 our tests for DNS hijacking.
16799 o Minor features (directory):
16800 - Authorities now specify server versions in networkstatus. This adds
16801 about 2% to the size of compressed networkstatus docs, and allows
16802 clients to tell which servers support BEGIN_DIR and which don't.
16803 The implementation is forward-compatible with a proposed future
16804 protocol version scheme not tied to Tor versions.
16805 - DirServer configuration lines now have an orport= option so
16806 clients can open encrypted tunnels to the authorities without
16807 having downloaded their descriptors yet. Enabled for moria1,
16808 moria2, tor26, and lefkada now in the default configuration.
16809 - Directory servers are more willing to send a 503 "busy" if they
16810 are near their write limit, especially for v1 directory requests.
16811 Now they can use their limited bandwidth for actual Tor traffic.
16812 - Clients track responses with status 503 from dirservers. After a
16813 dirserver has given us a 503, we try not to use it until an hour has
16814 gone by, or until we have no dirservers that haven't given us a 503.
16815 - When we get a 503 from a directory, and we're not a server, we don't
16816 count the failure against the total number of failures allowed
16817 for the thing we're trying to download.
16818 - Report X-Your-Address-Is correctly from tunneled directory
16819 connections; don't report X-Your-Address-Is when it's an internal
16820 address; and never believe reported remote addresses when they're
16822 - Protect against an unlikely DoS attack on directory servers.
16823 - Add a BadDirectory flag to network status docs so that authorities
16824 can (eventually) tell clients about caches they believe to be
16827 o Minor features (controller):
16828 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
16829 - Reimplement GETINFO so that info/names stays in sync with the
16831 - Implement "GETINFO fingerprint".
16832 - Implement "SETEVENTS GUARD" so controllers can get updates on
16833 entry guard status as it changes.
16835 o Minor features (clean up obsolete pieces):
16836 - Remove some options that have been deprecated since at least
16837 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
16838 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
16839 to set log options.
16840 - We no longer look for identity and onion keys in "identity.key" and
16841 "onion.key" -- these were replaced by secret_id_key and
16842 secret_onion_key in 0.0.8pre1.
16843 - We no longer require unrecognized directory entries to be
16846 o Major bugfixes (security):
16847 - Stop sending the HttpProxyAuthenticator string to directory
16848 servers when directory connections are tunnelled through Tor.
16849 - Clients no longer store bandwidth history in the state file.
16850 - Do not log introduction points for hidden services if SafeLogging
16852 - When generating bandwidth history, round down to the nearest
16853 1k. When storing accounting data, round up to the nearest 1k.
16854 - When we're running as a server, remember when we last rotated onion
16855 keys, so that we will rotate keys once they're a week old even if
16856 we never stay up for a week ourselves.
16858 o Major bugfixes (other):
16859 - Fix a longstanding bug in eventdns that prevented the count of
16860 timed-out resolves from ever being reset. This bug caused us to
16861 give up on a nameserver the third time it timed out, and try it
16862 10 seconds later... and to give up on it every time it timed out
16864 - Take out the '5 second' timeout from the connection retry
16865 schedule. Now the first connect attempt will wait a full 10
16866 seconds before switching to a new circuit. Perhaps this will help
16867 a lot. Based on observations from Mike Perry.
16868 - Fix a bug on the Windows implementation of tor_mmap_file() that
16869 would prevent the cached-routers file from ever loading. Reported
16873 - Fix an assert failure when a directory authority sets
16874 AuthDirRejectUnlisted and then receives a descriptor from an
16875 unlisted router. Reported by seeess.
16876 - Avoid a double-free when parsing malformed DirServer lines.
16877 - Fix a bug when a BSD-style PF socket is first used. Patch from
16879 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
16880 to resolve an address at a given exit node even when they ask for
16882 - Servers no longer ever list themselves in their "family" line,
16883 even if configured to do so. This makes it easier to configure
16884 family lists conveniently.
16885 - When running as a server, don't fall back to 127.0.0.1 when no
16886 nameservers are configured in /etc/resolv.conf; instead, make the
16887 user fix resolv.conf or specify nameservers explicitly. (Resolves
16889 - Stop accepting certain malformed ports in configured exit policies.
16890 - Don't re-write the fingerprint file every restart, unless it has
16892 - Stop warning when a single nameserver fails: only warn when _all_ of
16893 our nameservers have failed. Also, when we only have one nameserver,
16894 raise the threshold for deciding that the nameserver is dead.
16895 - Directory authorities now only decide that routers are reachable
16896 if their identity keys are as expected.
16897 - When the user uses bad syntax in the Log config line, stop
16898 suggesting other bad syntax as a replacement.
16899 - Correctly detect ipv6 DNS capability on OpenBSD.
16901 o Minor bugfixes (controller):
16902 - Report the circuit number correctly in STREAM CLOSED events. Bug
16903 reported by Mike Perry.
16904 - Do not report bizarre values for results of accounting GETINFOs
16905 when the last second's write or read exceeds the allotted bandwidth.
16906 - Report "unrecognized key" rather than an empty string when the
16907 controller tries to fetch a networkstatus that doesn't exist.
16910 Changes in version 0.1.1.26 - 2006-12-14
16911 o Security bugfixes:
16912 - Stop sending the HttpProxyAuthenticator string to directory
16913 servers when directory connections are tunnelled through Tor.
16914 - Clients no longer store bandwidth history in the state file.
16915 - Do not log introduction points for hidden services if SafeLogging
16919 - Fix an assert failure when a directory authority sets
16920 AuthDirRejectUnlisted and then receives a descriptor from an
16921 unlisted router (reported by seeess).
16924 Changes in version 0.1.2.4-alpha - 2006-12-03
16926 - Add support for using natd; this allows FreeBSDs earlier than
16927 5.1.2 to have ipfw send connections through Tor without using
16928 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
16931 - Make all connections to addresses of the form ".noconnect"
16932 immediately get closed. This lets application/controller combos
16933 successfully test whether they're talking to the same Tor by
16934 watching for STREAM events.
16935 - Make cross.sh cross-compilation script work even when autogen.sh
16936 hasn't been run. (Patch from Michael Mohr.)
16937 - Statistics dumped by -USR2 now include a breakdown of public key
16938 operations, for profiling.
16941 - Fix a major leak when directory authorities parse their
16942 approved-routers list, a minor memory leak when we fail to pick
16943 an exit node, and a few rare leaks on errors.
16944 - Handle TransPort connections even when the server sends data before
16945 the client sends data. Previously, the connection would just hang
16946 until the client sent data. (Patch from tup based on patch from
16948 - Avoid assert failure when our cached-routers file is empty on
16952 - Don't log spurious warnings when we see a circuit close reason we
16953 don't recognize; it's probably just from a newer version of Tor.
16954 - Have directory authorities allow larger amounts of drift in uptime
16955 without replacing the server descriptor: previously, a server that
16956 restarted every 30 minutes could have 48 "interesting" descriptors
16958 - Start linking to the Tor specification and Tor reference manual
16959 correctly in the Windows installer.
16960 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16961 Tor/Privoxy we also uninstall Vidalia.
16962 - Resume building on Irix64, and fix a lot of warnings from its
16963 MIPSpro C compiler.
16964 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
16965 when we're running as a client.
16968 Changes in version 0.1.1.25 - 2006-11-04
16970 - When a client asks us to resolve (rather than connect to)
16971 an address, and we have a cached answer, give them the cached
16972 answer. Previously, we would give them no answer at all.
16973 - We were building exactly the wrong circuits when we predict
16974 hidden service requirements, meaning Tor would have to build all
16975 its circuits on demand.
16976 - If none of our live entry guards have a high uptime, but we
16977 require a guard with a high uptime, try adding a new guard before
16978 we give up on the requirement. This patch should make long-lived
16979 connections more stable on average.
16980 - When testing reachability of our DirPort, don't launch new
16981 tests when there's already one in progress -- unreachable
16982 servers were stacking up dozens of testing streams.
16984 o Security bugfixes:
16985 - When the user sends a NEWNYM signal, clear the client-side DNS
16986 cache too. Otherwise we continue to act on previous information.
16989 - Avoid a memory corruption bug when creating a hash table for
16991 - Avoid possibility of controller-triggered crash when misusing
16992 certain commands from a v0 controller on platforms that do not
16993 handle printf("%s",NULL) gracefully.
16994 - Avoid infinite loop on unexpected controller input.
16995 - Don't log spurious warnings when we see a circuit close reason we
16996 don't recognize; it's probably just from a newer version of Tor.
16997 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16998 Tor/Privoxy we also uninstall Vidalia.
17001 Changes in version 0.1.2.3-alpha - 2006-10-29
17003 - Prepare for servers to publish descriptors less often: never
17004 discard a descriptor simply for being too old until either it is
17005 recommended by no authorities, or until we get a better one for
17006 the same router. Make caches consider retaining old recommended
17007 routers for even longer.
17008 - If most authorities set a BadExit flag for a server, clients
17009 don't think of it as a general-purpose exit. Clients only consider
17010 authorities that advertise themselves as listing bad exits.
17011 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
17012 headers for content, so that we can work better in the presence of
17013 caching HTTP proxies.
17014 - Allow authorities to list nodes as bad exits by fingerprint or by
17017 o Minor features, controller:
17018 - Add a REASON field to CIRC events; for backward compatibility, this
17019 field is sent only to controllers that have enabled the extended
17020 event format. Also, add additional reason codes to explain why
17021 a given circuit has been destroyed or truncated. (Patches from
17023 - Add a REMOTE_REASON field to extended CIRC events to tell the
17024 controller about why a remote OR told us to close a circuit.
17025 - Stream events also now have REASON and REMOTE_REASON fields,
17026 working much like those for circuit events.
17027 - There's now a GETINFO ns/... field so that controllers can ask Tor
17028 about the current status of a router.
17029 - A new event type "NS" to inform a controller when our opinion of
17030 a router's status has changed.
17031 - Add a GETINFO events/names and GETINFO features/names so controllers
17032 can tell which events and features are supported.
17033 - A new CLEARDNSCACHE signal to allow controllers to clear the
17034 client-side DNS cache without expiring circuits.
17036 o Security bugfixes:
17037 - When the user sends a NEWNYM signal, clear the client-side DNS
17038 cache too. Otherwise we continue to act on previous information.
17041 - Avoid sending junk to controllers or segfaulting when a controller
17042 uses EVENT_NEW_DESC with verbose nicknames.
17043 - Stop triggering asserts if the controller tries to extend hidden
17044 service circuits (reported by mwenge).
17045 - Avoid infinite loop on unexpected controller input.
17046 - When the controller does a "GETINFO network-status", tell it
17047 about even those routers whose descriptors are very old, and use
17048 long nicknames where appropriate.
17049 - Change NT service functions to be loaded on demand. This lets us
17050 build with MinGW without breaking Tor for Windows 98 users.
17051 - Do DirPort reachability tests less often, since a single test
17052 chews through many circuits before giving up.
17053 - In the hidden service example in torrc.sample, stop recommending
17054 esoteric and discouraged hidden service options.
17055 - When stopping an NT service, wait up to 10 sec for it to actually
17056 stop. Patch from Matt Edman; resolves bug 295.
17057 - Fix handling of verbose nicknames with ORCONN controller events:
17058 make them show up exactly when requested, rather than exactly when
17060 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
17061 printing a duplicate "$" in the keys we send (reported by mwenge).
17062 - Correctly set maximum connection limit on Cygwin. (This time
17064 - Try to detect Windows correctly when cross-compiling.
17065 - Detect the size of the routers file correctly even if it is
17066 corrupted (on systems without mmap) or not page-aligned (on systems
17067 with mmap). This bug was harmless.
17068 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
17069 to open a stream fails; now we do in more cases. This should
17070 make clients able to find a good exit faster in some cases, since
17071 unhandleable requests will now get an error rather than timing out.
17072 - Resolve two memory leaks when rebuilding the on-disk router cache
17073 (reported by fookoowa).
17074 - Clean up minor code warnings suggested by the MIPSpro C compiler,
17075 and reported by some Centos users.
17076 - Controller signals now work on non-Unix platforms that don't define
17077 SIGUSR1 and SIGUSR2 the way we expect.
17078 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
17079 values before failing, and always enables eventdns.
17080 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
17081 Try to fix this in configure.in by checking for most functions
17082 before we check for libevent.
17085 Changes in version 0.1.2.2-alpha - 2006-10-07
17087 - Make our async eventdns library on-by-default for Tor servers,
17088 and plan to deprecate the separate dnsworker threads.
17089 - Add server-side support for "reverse" DNS lookups (using PTR
17090 records so clients can determine the canonical hostname for a given
17091 IPv4 address). Only supported by servers using eventdns; servers
17092 now announce in their descriptors whether they support eventdns.
17093 - Specify and implement client-side SOCKS5 interface for reverse DNS
17094 lookups (see doc/socks-extensions.txt).
17095 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
17096 connect to directory servers through Tor. Previously, clients needed
17097 to find Tor exits to make private connections to directory servers.
17098 - Avoid choosing Exit nodes for entry or middle hops when the
17099 total bandwidth available from non-Exit nodes is much higher than
17100 the total bandwidth available from Exit nodes.
17101 - Workaround for name servers (like Earthlink's) that hijack failing
17102 DNS requests and replace the no-such-server answer with a "helpful"
17103 redirect to an advertising-driven search portal. Also work around
17104 DNS hijackers who "helpfully" decline to hijack known-invalid
17105 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
17106 lets you turn it off.
17107 - Send out a burst of long-range padding cells once we've established
17108 that we're reachable. Spread them over 4 circuits, so hopefully
17109 a few will be fast. This exercises our bandwidth and bootstraps
17110 us into the directory more quickly.
17112 o New/improved config options:
17113 - Add new config option "ResolvConf" to let the server operator
17114 choose an alternate resolve.conf file when using eventdns.
17115 - Add an "EnforceDistinctSubnets" option to control our "exclude
17116 servers on the same /16" behavior. It's still on by default; this
17117 is mostly for people who want to operate private test networks with
17118 all the machines on the same subnet.
17119 - If one of our entry guards is on the ExcludeNodes list, or the
17120 directory authorities don't think it's a good guard, treat it as
17121 if it were unlisted: stop using it as a guard, and throw it off
17122 the guards list if it stays that way for a long time.
17123 - Allow directory authorities to be marked separately as authorities
17124 for the v1 directory protocol, the v2 directory protocol, and
17125 as hidden service directories, to make it easier to retire old
17126 authorities. V1 authorities should set "HSAuthoritativeDir 1"
17127 to continue being hidden service authorities too.
17128 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
17130 o Minor features, controller:
17131 - Fix CIRC controller events so that controllers can learn the
17132 identity digests of non-Named servers used in circuit paths.
17133 - Let controllers ask for more useful identifiers for servers. Instead
17134 of learning identity digests for un-Named servers and nicknames
17135 for Named servers, the new identifiers include digest, nickname,
17136 and indication of Named status. Off by default; see control-spec.txt
17137 for more information.
17138 - Add a "getinfo address" controller command so it can display Tor's
17139 best guess to the user.
17140 - New controller event to alert the controller when our server
17141 descriptor has changed.
17142 - Give more meaningful errors on controller authentication failure.
17144 o Minor features, other:
17145 - When asked to resolve a hostname, don't use non-exit servers unless
17146 requested to do so. This allows servers with broken DNS to be
17147 useful to the network.
17148 - Divide eventdns log messages into warn and info messages.
17149 - Reserve the nickname "Unnamed" for routers that can't pick
17150 a hostname: any router can call itself Unnamed; directory
17151 authorities will never allocate Unnamed to any particular router;
17152 clients won't believe that any router is the canonical Unnamed.
17153 - Only include function names in log messages for info/debug messages.
17154 For notice/warn/err, the content of the message should be clear on
17155 its own, and printing the function name only confuses users.
17156 - Avoid some false positives during reachability testing: don't try
17157 to test via a server that's on the same /24 as us.
17158 - If we fail to build a circuit to an intended enclave, and it's
17159 not mandatory that we use that enclave, stop wanting it.
17160 - When eventdns is enabled, allow multithreaded builds on NetBSD and
17161 OpenBSD. (We had previously disabled threads on these platforms
17162 because they didn't have working thread-safe resolver functions.)
17164 o Major bugfixes, anonymity/security:
17165 - If a client asked for a server by name, and there's a named server
17166 in our network-status but we don't have its descriptor yet, we
17167 could return an unnamed server instead.
17168 - Fix NetBSD bug that could allow someone to force uninitialized RAM
17169 to be sent to a server's DNS resolver. This only affects NetBSD
17170 and other platforms that do not bounds-check tolower().
17171 - Reject (most) attempts to use Tor circuits with length one. (If
17172 many people start using Tor as a one-hop proxy, exit nodes become
17173 a more attractive target for compromise.)
17174 - Just because your DirPort is open doesn't mean people should be
17175 able to remotely teach you about hidden service descriptors. Now
17176 only accept rendezvous posts if you've got HSAuthoritativeDir set.
17178 o Major bugfixes, other:
17179 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
17180 - When a client asks the server to resolve (not connect to)
17181 an address, and it has a cached answer, give them the cached answer.
17182 Previously, the server would give them no answer at all.
17183 - Allow really slow clients to not hang up five minutes into their
17184 directory downloads (suggested by Adam J. Richter).
17185 - We were building exactly the wrong circuits when we anticipated
17186 hidden service requirements, meaning Tor would have to build all
17187 its circuits on demand.
17188 - Avoid crashing when we mmap a router cache file of size 0.
17189 - When testing reachability of our DirPort, don't launch new
17190 tests when there's already one in progress -- unreachable
17191 servers were stacking up dozens of testing streams.
17193 o Minor bugfixes, correctness:
17194 - If we're a directory mirror and we ask for "all" network status
17195 documents, we would discard status documents from authorities
17196 we don't recognize.
17197 - Avoid a memory corruption bug when creating a hash table for
17199 - Avoid controller-triggered crash when misusing certain commands
17200 from a v0 controller on platforms that do not handle
17201 printf("%s",NULL) gracefully.
17202 - Don't crash when a controller sends a third argument to an
17203 "extendcircuit" request.
17204 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
17205 response; fix error code when "getinfo dir/status/" fails.
17206 - Avoid crash when telling controller stream-status and a stream
17208 - Patch from Adam Langley to fix assert() in eventdns.c.
17209 - Fix a debug log message in eventdns to say "X resolved to Y"
17210 instead of "X resolved to X".
17211 - Make eventdns give strings for DNS errors, not just error numbers.
17212 - Track unreachable entry guards correctly: don't conflate
17213 'unreachable by us right now' with 'listed as down by the directory
17214 authorities'. With the old code, if a guard was unreachable by
17215 us but listed as running, it would clog our guard list forever.
17216 - Behave correctly in case we ever have a network with more than
17217 2GB/s total advertised capacity.
17218 - Make TrackExitHosts case-insensitive, and fix the behavior of
17219 ".suffix" TrackExitHosts items to avoid matching in the middle of
17221 - Finally fix the openssl warnings from newer gccs that believe that
17222 ignoring a return value is okay, but casting a return value and
17223 then ignoring it is a sign of madness.
17224 - Prevent the contrib/exitlist script from printing the same
17225 result more than once.
17226 - Patch from Steve Hildrey: Generate network status correctly on
17227 non-versioning dirservers.
17228 - Don't listen to the X-Your-Address-Is hint if you did the lookup
17229 via Tor; otherwise you'll think you're the exit node's IP address.
17231 o Minor bugfixes, performance:
17232 - Two small performance improvements on parsing descriptors.
17233 - Major performance improvement on inserting descriptors: change
17234 algorithm from O(n^2) to O(n).
17235 - Make the common memory allocation path faster on machines where
17236 malloc(0) returns a pointer.
17237 - Start remembering X-Your-Address-Is directory hints even if you're
17238 a client, so you can become a server more smoothly.
17239 - Avoid duplicate entries on MyFamily line in server descriptor.
17241 o Packaging, features:
17242 - Remove architecture from OS X builds. The official builds are
17243 now universal binaries.
17244 - The Debian package now uses --verify-config when (re)starting,
17245 to distinguish configuration errors from other errors.
17246 - Update RPMs to require libevent 1.1b.
17248 o Packaging, bugfixes:
17249 - Patches so Tor builds with MinGW on Windows.
17250 - Patches so Tor might run on Cygwin again.
17251 - Resume building on non-gcc compilers and ancient gcc. Resume
17252 building with the -O0 compile flag. Resume building cleanly on
17254 - Run correctly on OS X platforms with case-sensitive filesystems.
17255 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
17256 - Add autoconf checks so Tor can build on Solaris x86 again.
17259 - Documented (and renamed) ServerDNSSearchDomains and
17260 ServerDNSResolvConfFile options.
17261 - Be clearer that the *ListenAddress directives can be repeated
17265 Changes in version 0.1.1.24 - 2006-09-29
17267 - Allow really slow clients to not hang up five minutes into their
17268 directory downloads (suggested by Adam J. Richter).
17269 - Fix major performance regression from 0.1.0.x: instead of checking
17270 whether we have enough directory information every time we want to
17271 do something, only check when the directory information has changed.
17272 This should improve client CPU usage by 25-50%.
17273 - Don't crash if, after a server has been running for a while,
17274 it can't resolve its hostname.
17277 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17278 - Don't crash when the controller receives a third argument to an
17279 "extendcircuit" request.
17280 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
17281 response; fix error code when "getinfo dir/status/" fails.
17282 - Fix configure.in to not produce broken configure files with
17283 more recent versions of autoconf. Thanks to Clint for his auto*
17285 - Fix security bug on NetBSD that could allow someone to force
17286 uninitialized RAM to be sent to a server's DNS resolver. This
17287 only affects NetBSD and other platforms that do not bounds-check
17289 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
17290 methods: these are known to be buggy.
17291 - If we're a directory mirror and we ask for "all" network status
17292 documents, we would discard status documents from authorities
17293 we don't recognize.
17296 Changes in version 0.1.2.1-alpha - 2006-08-27
17298 - Add "eventdns" async dns library from Adam Langley, tweaked to
17299 build on OSX and Windows. Only enabled if you pass the
17300 --enable-eventdns argument to configure.
17301 - Allow servers with no hostname or IP address to learn their
17302 IP address by asking the directory authorities. This code only
17303 kicks in when you would normally have exited with a "no address"
17304 error. Nothing's authenticated, so use with care.
17305 - Rather than waiting a fixed amount of time between retrying
17306 application connections, we wait only 5 seconds for the first,
17307 10 seconds for the second, and 15 seconds for each retry after
17308 that. Hopefully this will improve the expected user experience.
17309 - Patch from Tup to add support for transparent AP connections:
17310 this basically bundles the functionality of trans-proxy-tor
17311 into the Tor mainline. Now hosts with compliant pf/netfilter
17312 implementations can redirect TCP connections straight to Tor
17313 without diverting through SOCKS. Needs docs.
17314 - Busy directory servers save lots of memory by spooling server
17315 descriptors, v1 directories, and v2 networkstatus docs to buffers
17316 as needed rather than en masse. Also mmap the cached-routers
17317 files, so we don't need to keep the whole thing in memory too.
17318 - Automatically avoid picking more than one node from the same
17319 /16 network when constructing a circuit.
17320 - Revise and clean up the torrc.sample that we ship with; add
17321 a section for BandwidthRate and BandwidthBurst.
17324 - Split circuit_t into origin_circuit_t and or_circuit_t, and
17325 split connection_t into edge, or, dir, control, and base structs.
17326 These will save quite a bit of memory on busy servers, and they'll
17327 also help us track down bugs in the code and bugs in the spec.
17328 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
17329 or later. Log when we are doing this, so we can diagnose it when
17330 it fails. (Also, recommend libevent 1.1b for kqueue and
17331 win32 methods; deprecate libevent 1.0b harder; make libevent
17332 recommendation system saner.)
17333 - Start being able to build universal binaries on OS X (thanks
17335 - Export the default exit policy via the control port, so controllers
17336 don't need to guess what it is / will be later.
17337 - Add a man page entry for ProtocolWarnings.
17338 - Add TestVia config option to the man page.
17339 - Remove even more protocol-related warnings from Tor server logs,
17340 such as bad TLS handshakes and malformed begin cells.
17341 - Stop fetching descriptors if you're not a dir mirror and you
17342 haven't tried to establish any circuits lately. [This currently
17343 causes some dangerous behavior, because when you start up again
17344 you'll use your ancient server descriptors.]
17345 - New DirPort behavior: if you have your dirport set, you download
17346 descriptors aggressively like a directory mirror, whether or not
17347 your ORPort is set.
17348 - Get rid of the router_retry_connections notion. Now routers
17349 no longer try to rebuild long-term connections to directory
17350 authorities, and directory authorities no longer try to rebuild
17351 long-term connections to all servers. We still don't hang up
17352 connections in these two cases though -- we need to look at it
17353 more carefully to avoid flapping, and we likely need to wait til
17354 0.1.1.x is obsolete.
17355 - Drop compatibility with obsolete Tors that permit create cells
17356 to have the wrong circ_id_type.
17357 - Re-enable per-connection rate limiting. Get rid of the "OP
17358 bandwidth" concept. Lay groundwork for "bandwidth classes" --
17359 separate global buckets that apply depending on what sort of conn
17361 - Start publishing one minute or so after we find our ORPort
17362 to be reachable. This will help reduce the number of descriptors
17363 we have for ourselves floating around, since it's quite likely
17364 other things (e.g. DirPort) will change during that minute too.
17365 - Fork the v1 directory protocol into its own spec document,
17366 and mark dir-spec.txt as the currently correct (v2) spec.
17369 - When we find our DirPort to be reachable, publish a new descriptor
17370 so we'll tell the world (reported by pnx).
17371 - Publish a new descriptor after we hup/reload. This is important
17372 if our config has changed such that we'll want to start advertising
17373 our DirPort now, etc.
17374 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17375 - When we have a state file we cannot parse, tell the user and
17376 move it aside. Now we avoid situations where the user starts
17377 Tor in 1904, Tor writes a state file with that timestamp in it,
17378 the user fixes her clock, and Tor refuses to start.
17379 - Fix configure.in to not produce broken configure files with
17380 more recent versions of autoconf. Thanks to Clint for his auto*
17382 - "tor --verify-config" now exits with -1(255) or 0 depending on
17383 whether the config options are bad or good.
17384 - Resolve bug 321 when using dnsworkers: append a period to every
17385 address we resolve at the exit node, so that we do not accidentally
17386 pick up local addresses, and so that failing searches are retried
17387 in the resolver search domains. (This is already solved for
17388 eventdns.) (This breaks Blossom servers for now.)
17389 - If we are using an exit enclave and we can't connect, e.g. because
17390 its webserver is misconfigured to not listen on localhost, then
17391 back off and try connecting from somewhere else before we fail.
17394 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
17395 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
17396 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
17397 when the IP address is mapped through MapAddress to a hostname.
17398 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
17399 useless IPv6 DNS resolves.
17400 - Patch suggested by Karsten Loesing: respond to SIGNAL command
17401 before we execute the signal, in case the signal shuts us down.
17402 - Clean up AllowInvalidNodes man page entry.
17403 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
17404 - Add more asserts to track down an assert error on a windows Tor
17405 server with connection_add being called with socket == -1.
17406 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
17407 - Fix misleading log messages: an entry guard that is "unlisted",
17408 as well as not known to be "down" (because we've never heard
17409 of it), is not therefore "up".
17410 - Remove code to special-case "-cvs" ending, since it has not
17411 actually mattered since 0.0.9.
17412 - Make our socks5 handling more robust to broken socks clients:
17413 throw out everything waiting on the buffer in between socks
17414 handshake phases, since they can't possibly (so the theory
17415 goes) have predicted what we plan to respond to them.
17418 Changes in version 0.1.1.23 - 2006-07-30
17420 - Fast Tor servers, especially exit nodes, were triggering asserts
17421 due to a bug in handling the list of pending DNS resolves. Some
17422 bugs still remain here; we're hunting them.
17423 - Entry guards could crash clients by sending unexpected input.
17424 - More fixes on reachability testing: if you find yourself reachable,
17425 then don't ever make any client requests (so you stop predicting
17426 circuits), then hup or have your clock jump, then later your IP
17427 changes, you won't think circuits are working, so you won't try to
17428 test reachability, so you won't publish.
17431 - Avoid a crash if the controller does a resetconf firewallports
17432 and then a setconf fascistfirewall=1.
17433 - Avoid an integer underflow when the dir authority decides whether
17434 a router is stable: we might wrongly label it stable, and compute
17435 a slightly wrong median stability, when a descriptor is published
17437 - Fix a place where we might trigger an assert if we can't build our
17438 own server descriptor yet.
17441 Changes in version 0.1.1.22 - 2006-07-05
17443 - Fix a big bug that was causing servers to not find themselves
17444 reachable if they changed IP addresses. Since only 0.1.1.22+
17445 servers can do reachability testing correctly, now we automatically
17446 make sure to test via one of these.
17447 - Fix to allow clients and mirrors to learn directory info from
17448 descriptor downloads that get cut off partway through.
17449 - Directory authorities had a bug in deciding if a newly published
17450 descriptor was novel enough to make everybody want a copy -- a few
17451 servers seem to be publishing new descriptors many times a minute.
17453 - Fix a rare bug that was causing some servers to complain about
17454 "closing wedged cpuworkers" and skip some circuit create requests.
17455 - Make the Exit flag in directory status documents actually work.
17458 Changes in version 0.1.1.21 - 2006-06-10
17459 o Crash and assert fixes from 0.1.1.20:
17460 - Fix a rare crash on Tor servers that have enabled hibernation.
17461 - Fix a seg fault on startup for Tor networks that use only one
17462 directory authority.
17463 - Fix an assert from a race condition that occurs on Tor servers
17464 while exiting, where various threads are trying to log that they're
17465 exiting, and delete the logs, at the same time.
17466 - Make our unit tests pass again on certain obscure platforms.
17469 - Add support for building SUSE RPM packages.
17470 - Speed up initial bootstrapping for clients: if we are making our
17471 first ever connection to any entry guard, then don't mark it down
17473 - When only one Tor server in the network is labelled as a guard,
17474 and we've already picked him, we would cycle endlessly picking him
17475 again, being unhappy about it, etc. Now we specifically exclude
17476 current guards when picking a new guard.
17477 - Servers send create cells more reliably after the TLS connection
17478 is established: we were sometimes forgetting to send half of them
17479 when we had more than one pending.
17480 - If we get a create cell that asks us to extend somewhere, but the
17481 Tor server there doesn't match the expected digest, we now send
17482 a destroy cell back, rather than silently doing nothing.
17483 - Make options->RedirectExit work again.
17484 - Make cookie authentication for the controller work again.
17485 - Stop being picky about unusual characters in the arguments to
17486 mapaddress. It's none of our business.
17487 - Add a new config option "TestVia" that lets you specify preferred
17488 middle hops to use for test circuits. Perhaps this will let me
17489 debug the reachability problems better.
17491 o Log / documentation fixes:
17492 - If we're a server and some peer has a broken TLS certificate, don't
17493 log about it unless ProtocolWarnings is set, i.e., we want to hear
17494 about protocol violations by others.
17495 - Fix spelling of VirtualAddrNetwork in man page.
17496 - Add a better explanation at the top of the autogenerated torrc file
17497 about what happened to our old torrc.
17500 Changes in version 0.1.1.20 - 2006-05-23
17502 - Downgrade a log severity where servers complain that they're
17504 - Avoid a compile warning on FreeBSD.
17505 - Remove string size limit on NEWDESC messages; solve bug 291.
17506 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
17507 more thoroughly when we're running on windows.
17510 Changes in version 0.1.1.19-rc - 2006-05-03
17512 - Regenerate our local descriptor if it's dirty and we try to use
17513 it locally (e.g. if it changes during reachability detection).
17514 - If we setconf our ORPort to 0, we continued to listen on the
17515 old ORPort and receive connections.
17516 - Avoid a second warning about machine/limits.h on Debian
17518 - Be willing to add our own routerinfo into the routerlist.
17519 Now authorities will include themselves in their directories
17520 and network-statuses.
17521 - Stop trying to upload rendezvous descriptors to every
17522 directory authority: only try the v1 authorities.
17523 - Servers no longer complain when they think they're not
17524 registered with the directory authorities. There were too many
17526 - Backport dist-rpm changes so rpms can be built without errors.
17529 - Implement an option, VirtualAddrMask, to set which addresses
17530 get handed out in response to mapaddress requests. This works
17531 around a bug in tsocks where 127.0.0.0/8 is never socksified.
17534 Changes in version 0.1.1.18-rc - 2006-04-10
17536 - Work harder to download live network-statuses from all the
17537 directory authorities we know about. Improve the threshold
17538 decision logic so we're more robust to edge cases.
17539 - When fetching rendezvous descriptors, we were willing to ask
17540 v2 authorities too, which would always return 404.
17543 - Stop listing down or invalid nodes in the v1 directory. This will
17544 reduce its bulk by about 1/3, and reduce load on directory
17546 - When deciding whether a router is Fast or Guard-worthy, consider
17547 his advertised BandwidthRate and not just the BandwidthCapacity.
17548 - No longer ship INSTALL and README files -- they are useless now.
17549 - Force rpmbuild to behave and honor target_cpu.
17550 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
17551 - Start to include translated versions of the tor-doc-*.html
17552 files, along with the screenshots. Still needs more work.
17553 - Start sending back 512 and 451 errors if mapaddress fails,
17554 rather than not sending anything back at all.
17555 - When we fail to bind or listen on an incoming or outgoing
17556 socket, we should close it before failing. otherwise we just
17557 leak it. (thanks to weasel for finding.)
17558 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
17559 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
17560 - Make NoPublish (even though deprecated) work again.
17561 - Fix a minor security flaw where a versioning auth dirserver
17562 could list a recommended version many times in a row to make
17563 clients more convinced that it's recommended.
17564 - Fix crash bug if there are two unregistered servers running
17565 with the same nickname, one of them is down, and you ask for
17566 them by nickname in your EntryNodes or ExitNodes. Also, try
17567 to pick the one that's running rather than an arbitrary one.
17568 - Fix an infinite loop we could hit if we go offline for too long.
17569 - Complain when we hit WSAENOBUFS on recv() or write() too.
17570 Perhaps this will help us hunt the bug.
17571 - If you're not a versioning dirserver, don't put the string
17572 "client-versions \nserver-versions \n" in your network-status.
17573 - Lower the minimum required number of file descriptors to 1000,
17574 so we can have some overhead for Valgrind on Linux, where the
17575 default ulimit -n is 1024.
17578 - Add tor.dizum.com as the fifth authoritative directory server.
17579 - Add a new config option FetchUselessDescriptors, off by default,
17580 for when you plan to run "exitlist" on your client and you want
17581 to know about even the non-running descriptors.
17584 Changes in version 0.1.1.17-rc - 2006-03-28
17586 - Clients and servers since 0.1.1.10-alpha have been expiring
17587 connections whenever they are idle for 5 minutes and they *do*
17588 have circuits on them. Oops. With this new version, clients will
17589 discard their previous entry guard choices and avoid choosing
17590 entry guards running these flawed versions.
17591 - Fix memory leak when uncompressing concatenated zlib streams. This
17592 was causing substantial leaks over time on Tor servers.
17593 - The v1 directory was including servers as much as 48 hours old,
17594 because that's how the new routerlist->routers works. Now only
17595 include them if they're 20 hours old or less.
17598 - Resume building on irix64, netbsd 2.0, etc.
17599 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
17601 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
17602 and it is confusing some users.
17603 - Mirrors stop caching the v1 directory so often.
17604 - Make the max number of old descriptors that a cache will hold
17605 rise with the number of directory authorities, so we can scale.
17606 - Change our win32 uname() hack to be more forgiving about what
17607 win32 versions it thinks it's found.
17610 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
17612 - When the controller's *setconf commands fail, collect an error
17613 message in a string and hand it back to the controller.
17614 - Make the v2 dir's "Fast" flag based on relative capacity, just
17615 like "Stable" is based on median uptime. Name everything in the
17616 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
17617 - Log server fingerprint on startup, so new server operators don't
17618 have to go hunting around their filesystem for it.
17619 - Return a robots.txt on our dirport to discourage google indexing.
17620 - Let the controller ask for GETINFO dir/status/foo so it can ask
17621 directly rather than connecting to the dir port. Only works when
17622 dirport is set for now.
17624 o New config options rather than constants in the code:
17625 - SocksTimeout: How long do we let a socks connection wait
17626 unattached before we fail it?
17627 - CircuitBuildTimeout: Cull non-open circuits that were born
17628 at least this many seconds ago.
17629 - CircuitIdleTimeout: Cull open clean circuits that were born
17630 at least this many seconds ago.
17633 Changes in version 0.1.1.16-rc - 2006-03-18
17634 o Bugfixes on 0.1.1.15-rc:
17635 - Fix assert when the controller asks to attachstream a connect-wait
17636 or resolve-wait stream.
17637 - Now do address rewriting when the controller asks us to attach
17638 to a particular circuit too. This will let Blossom specify
17639 "moria2.exit" without having to learn what moria2's IP address is.
17640 - Make the "tor --verify-config" command-line work again, so people
17641 can automatically check if their torrc will parse.
17642 - Authoritative dirservers no longer require an open connection from
17643 a server to consider him "reachable". We need this change because
17644 when we add new auth dirservers, old servers won't know not to
17646 - Let Tor build on Sun CC again.
17647 - Fix an off-by-one buffer size in dirserv.c that magically never
17648 hit our three authorities but broke sjmurdoch's own tor network.
17649 - If we as a directory mirror don't know of any v1 directory
17650 authorities, then don't try to cache any v1 directories.
17651 - Stop warning about unknown servers in our family when they are
17652 given as hex digests.
17653 - Stop complaining as quickly to the server operator that he
17654 hasn't registered his nickname/key binding.
17655 - Various cleanups so we can add new V2 Auth Dirservers.
17656 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
17657 reflect the updated flags in our v2 dir protocol.
17658 - Resume allowing non-printable characters for exit streams (both
17659 for connecting and for resolving). Now we tolerate applications
17660 that don't follow the RFCs. But continue to block malformed names
17663 o Bugfixes on 0.1.0.x:
17664 - Fix assert bug in close_logs(): when we close and delete logs,
17665 remove them all from the global "logfiles" list.
17666 - Fix minor integer overflow in calculating when we expect to use up
17667 our bandwidth allocation before hibernating.
17668 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
17669 there are multiple SSLs installed with different versions.
17670 - When we try to be a server and Address is not explicitly set and
17671 our hostname resolves to a private IP address, try to use an
17672 interface address if it has a public address. Now Windows machines
17673 that think of themselves as localhost can work by default.
17676 - Let the controller ask for GETINFO dir/server/foo so it can ask
17677 directly rather than connecting to the dir port.
17678 - Let the controller tell us about certain router descriptors
17679 that it doesn't want Tor to use in circuits. Implement
17680 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
17681 - New config option SafeSocks to reject all application connections
17682 using unsafe socks protocols. Defaults to off.
17685 Changes in version 0.1.1.15-rc - 2006-03-11
17686 o Bugfixes and cleanups:
17687 - When we're printing strings from the network, don't try to print
17688 non-printable characters. This protects us against shell escape
17689 sequence exploits, and also against attacks to fool humans into
17690 misreading their logs.
17691 - Fix a bug where Tor would fail to establish any connections if you
17692 left it off for 24 hours and then started it: we were happy with
17693 the obsolete network statuses, but they all referred to router
17694 descriptors that were too old to fetch, so we ended up with no
17695 valid router descriptors.
17696 - Fix a seg fault in the controller's "getinfo orconn-status"
17697 command while listing status on incoming handshaking connections.
17698 Introduce a status name "NEW" for these connections.
17699 - If we get a linelist or linelist_s config option from the torrc
17700 (e.g. ExitPolicy) and it has no value, warn and skip rather than
17701 silently resetting it to its default.
17702 - Don't abandon entry guards until they've been down or gone for
17704 - Cleaner and quieter log messages.
17707 - New controller signal NEWNYM that makes new application requests
17708 use clean circuits.
17709 - Add a new circuit purpose 'controller' to let the controller ask
17710 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
17711 controller command to let you specify the purpose if you're
17712 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
17713 command to let you change a circuit's purpose after it's been
17715 - Accept "private:*" in routerdesc exit policies; not generated yet
17716 because older Tors do not understand it.
17717 - Add BSD-style contributed startup script "rc.subr" from Peter
17721 Changes in version 0.1.1.14-alpha - 2006-02-20
17722 o Bugfixes on 0.1.1.x:
17723 - Don't die if we ask for a stdout or stderr log (even implicitly)
17724 and we're set to RunAsDaemon -- just warn.
17725 - We still had a few bugs in the OR connection rotation code that
17726 caused directory servers to slowly aggregate connections to other
17727 fast Tor servers. This time for sure!
17728 - Make log entries on Win32 include the name of the function again.
17729 - We were treating a pair of exit policies if they were equal even
17730 if one said accept and the other said reject -- causing us to
17731 not always publish a new descriptor since we thought nothing
17733 - Retry pending server downloads as well as pending networkstatus
17734 downloads when we unexpectedly get a socks request.
17735 - We were ignoring the IS_FAST flag in the directory status,
17736 meaning we were willing to pick trivial-bandwidth nodes for "fast"
17738 - If the controller's SAVECONF command fails (e.g. due to file
17739 permissions), let the controller know that it failed.
17742 - If we're trying to be a Tor server and running Windows 95/98/ME
17743 as a server, explain that we'll likely crash.
17744 - When we're a server, a client asks for an old-style directory,
17745 and our write bucket is empty, don't give it to him. This way
17746 small servers can continue to serve the directory *sometimes*,
17747 without getting overloaded.
17748 - Compress exit policies even more -- look for duplicate lines
17750 - Clients now honor the "guard" flag in the router status when
17751 picking entry guards, rather than looking at is_fast or is_stable.
17752 - Retain unrecognized lines in $DATADIR/state file, so that we can
17753 be forward-compatible.
17754 - Generate 18.0.0.0/8 address policy format in descs when we can;
17755 warn when the mask is not reducible to a bit-prefix.
17756 - Let the user set ControlListenAddress in the torrc. This can be
17757 dangerous, but there are some cases (like a secured LAN) where it
17759 - Split ReachableAddresses into ReachableDirAddresses and
17760 ReachableORAddresses, so we can restrict Dir conns to port 80
17761 and OR conns to port 443.
17762 - Now we can target arch and OS in rpm builds (contributed by
17763 Phobos). Also make the resulting dist-rpm filename match the
17765 - New config options to help controllers: FetchServerDescriptors
17766 and FetchHidServDescriptors for whether to fetch server
17767 info and hidserv info or let the controller do it, and
17768 PublishServerDescriptor and PublishHidServDescriptors.
17769 - Also let the controller set the __AllDirActionsPrivate config
17770 option if you want all directory fetches/publishes to happen via
17771 Tor (it assumes your controller bootstraps your circuits).
17774 Changes in version 0.1.0.17 - 2006-02-17
17775 o Crash bugfixes on 0.1.0.x:
17776 - When servers with a non-zero DirPort came out of hibernation,
17777 sometimes they would trigger an assert.
17779 o Other important bugfixes:
17780 - On platforms that don't have getrlimit (like Windows), we were
17781 artificially constraining ourselves to a max of 1024
17782 connections. Now just assume that we can handle as many as 15000
17783 connections. Hopefully this won't cause other problems.
17785 o Backported features:
17786 - When we're a server, a client asks for an old-style directory,
17787 and our write bucket is empty, don't give it to him. This way
17788 small servers can continue to serve the directory *sometimes*,
17789 without getting overloaded.
17790 - Whenever you get a 503 in response to a directory fetch, try
17791 once more. This will become important once servers start sending
17792 503's whenever they feel busy.
17793 - Fetch a new directory every 120 minutes, not every 40 minutes.
17794 Now that we have hundreds of thousands of users running the old
17795 directory algorithm, it's starting to hurt a lot.
17796 - Bump up the period for forcing a hidden service descriptor upload
17797 from 20 minutes to 1 hour.
17800 Changes in version 0.1.1.13-alpha - 2006-02-09
17801 o Crashes in 0.1.1.x:
17802 - When you tried to setconf ORPort via the controller, Tor would
17803 crash. So people using TorCP to become a server were sad.
17804 - Solve (I hope) the stack-smashing bug that we were seeing on fast
17805 servers. The problem appears to be something do with OpenSSL's
17806 random number generation, or how we call it, or something. Let me
17807 know if the crashes continue.
17808 - Turn crypto hardware acceleration off by default, until we find
17809 somebody smart who can test it for us. (It appears to produce
17810 seg faults in at least some cases.)
17811 - Fix a rare assert error when we've tried all intro points for
17812 a hidden service and we try fetching the service descriptor again:
17813 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
17816 - Fix a major load balance bug: we were round-robining in 16 KB
17817 chunks, and servers with bandwidthrate of 20 KB, while downloading
17818 a 600 KB directory, would starve their other connections. Now we
17819 try to be a bit more fair.
17820 - Dir authorities and mirrors were never expiring the newest
17821 descriptor for each server, causing memory and directory bloat.
17822 - Fix memory-bloating and connection-bloating bug on servers: We
17823 were never closing any connection that had ever had a circuit on
17824 it, because we were checking conn->n_circuits == 0, yet we had a
17825 bug that let it go negative.
17826 - Make Tor work using squid as your http proxy again -- squid
17827 returns an error if you ask for a URL that's too long, and it uses
17828 a really generic error message. Plus, many people are behind a
17829 transparent squid so they don't even realize it.
17830 - On platforms that don't have getrlimit (like Windows), we were
17831 artificially constraining ourselves to a max of 1024
17832 connections. Now just assume that we can handle as many as 15000
17833 connections. Hopefully this won't cause other problems.
17834 - Add a new config option ExitPolicyRejectPrivate which defaults to
17835 1. This means all exit policies will begin with rejecting private
17836 addresses, unless the server operator explicitly turns it off.
17839 - Clients no longer download descriptors for non-running
17841 - Before we add new directory authorities, we should make it
17842 clear that only v1 authorities should receive/publish hidden
17843 service descriptors.
17846 - As soon as we've fetched some more directory info, immediately
17847 try to download more server descriptors. This way we don't have
17848 a 10 second pause during initial bootstrapping.
17849 - Remove even more loud log messages that the server operator can't
17851 - When we're running an obsolete or un-recommended version, make
17852 the log message more clear about what the problem is and what
17853 versions *are* still recommended.
17854 - Provide a more useful warn message when our onion queue gets full:
17855 the CPU is too slow or the exit policy is too liberal.
17856 - Don't warn when we receive a 503 from a dirserver/cache -- this
17857 will pave the way for them being able to refuse if they're busy.
17858 - When we fail to bind a listener, try to provide a more useful
17859 log message: e.g., "Is Tor already running?"
17860 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
17861 Goldberg can prove things about our handshake protocol more
17863 - MaxConn has been obsolete for a while now. Document the ConnLimit
17864 config option, which is a *minimum* number of file descriptors
17865 that must be available else Tor refuses to start.
17866 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
17867 if you log to syslog and want something other than LOG_DAEMON.
17868 - Make dirservers generate a separate "guard" flag to mean,
17869 "would make a good entry guard". Make clients parse it and vote
17870 on it. Not used by clients yet.
17871 - Implement --with-libevent-dir option to ./configure. Also, improve
17872 search techniques to find libevent, and use those for openssl too.
17873 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
17874 - Only start testing reachability once we've established a
17875 circuit. This will make startup on dirservers less noisy.
17876 - Don't try to upload hidden service descriptors until we have
17877 established a circuit.
17878 - Fix the controller's "attachstream 0" command to treat conn like
17879 it just connected, doing address remapping, handling .exit and
17880 .onion idioms, and so on. Now we're more uniform in making sure
17881 that the controller hears about new and closing connections.
17884 Changes in version 0.1.1.12-alpha - 2006-01-11
17885 o Bugfixes on 0.1.1.x:
17886 - The fix to close duplicate server connections was closing all
17887 Tor client connections if they didn't establish a circuit
17888 quickly enough. Oops.
17889 - Fix minor memory issue (double-free) that happened on exit.
17891 o Bugfixes on 0.1.0.x:
17892 - Tor didn't warn when it failed to open a log file.
17895 Changes in version 0.1.1.11-alpha - 2006-01-10
17896 o Crashes in 0.1.1.x:
17897 - Include all the assert/crash fixes from 0.1.0.16.
17898 - If you start Tor and then quit very quickly, there were some
17899 races that tried to free things that weren't allocated yet.
17900 - Fix a rare memory stomp if you're running hidden services.
17901 - Fix segfault when specifying DirServer in config without nickname.
17902 - Fix a seg fault when you finish connecting to a server but at
17903 that moment you dump his server descriptor.
17904 - Extendcircuit and Attachstream controller commands would
17905 assert/crash if you don't give them enough arguments.
17906 - Fix an assert error when we're out of space in the connection_list
17907 and we try to post a hidden service descriptor (reported by weasel).
17908 - If you specify a relative torrc path and you set RunAsDaemon in
17909 your torrc, then it chdir()'s to the new directory. If you HUP,
17910 it tries to load the new torrc location, fails, and exits.
17911 The fix: no longer allow a relative path to torrc using -f.
17914 - Implement "entry guards": automatically choose a handful of entry
17915 nodes and stick with them for all circuits. Only pick new guards
17916 when the ones you have are unsuitable, and if the old guards
17917 become suitable again, switch back. This will increase security
17918 dramatically against certain end-point attacks. The EntryNodes
17919 config option now provides some hints about which entry guards you
17920 want to use most; and StrictEntryNodes means to only use those.
17921 - New directory logic: download by descriptor digest, not by
17922 fingerprint. Caches try to download all listed digests from
17923 authorities; clients try to download "best" digests from caches.
17924 This avoids partitioning and isolating attacks better.
17925 - Make the "stable" router flag in network-status be the median of
17926 the uptimes of running valid servers, and make clients pay
17927 attention to the network-status flags. Thus the cutoff adapts
17928 to the stability of the network as a whole, making IRC, IM, etc
17929 connections more reliable.
17932 - Tor servers with dynamic IP addresses were needing to wait 18
17933 hours before they could start doing reachability testing using
17934 the new IP address and ports. This is because they were using
17935 the internal descriptor to learn what to test, yet they were only
17936 rebuilding the descriptor once they decided they were reachable.
17937 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
17938 to download certain server descriptors, throw them away, and then
17939 fetch them again after 30 minutes. Now mirrors throw away these
17940 server descriptors so clients can't get them.
17941 - We were leaving duplicate connections to other ORs open for a week,
17942 rather than closing them once we detect a duplicate. This only
17943 really affected authdirservers, but it affected them a lot.
17944 - Spread the authdirservers' reachability testing over the entire
17945 testing interval, so we don't try to do 500 TLS's at once every
17949 - If the network is down, and we try to connect to a conn because
17950 we have a circuit in mind, and we timeout (30 seconds) because the
17951 network never answers, we were expiring the circuit, but we weren't
17952 obsoleting the connection or telling the entry_guards functions.
17953 - Some Tor servers process billions of cells per day. These statistics
17954 need to be uint64_t's.
17955 - Check for integer overflows in more places, when adding elements
17956 to smartlists. This could possibly prevent a buffer overflow
17957 on malicious huge inputs. I don't see any, but I haven't looked
17959 - ReachableAddresses kept growing new "reject *:*" lines on every
17961 - When you "setconf log" via the controller, it should remove all
17962 logs. We were automatically adding back in a "log notice stdout".
17963 - Newly bootstrapped Tor networks couldn't establish hidden service
17964 circuits until they had nodes with high uptime. Be more tolerant.
17965 - We were marking servers down when they could not answer every piece
17966 of the directory request we sent them. This was far too harsh.
17967 - Fix the torify (tsocks) config file to not use Tor for localhost
17969 - Directory authorities now go to the proper authority when asking for
17970 a networkstatus, even when they want a compressed one.
17971 - Fix a harmless bug that was causing Tor servers to log
17972 "Got an end because of misc error, but we're not an AP. Closing."
17973 - Authorities were treating their own descriptor changes as cosmetic,
17974 meaning the descriptor available in the network-status and the
17975 descriptor that clients downloaded were different.
17976 - The OS X installer was adding a symlink for tor_resolve but
17977 the binary was called tor-resolve (reported by Thomas Hardly).
17978 - Workaround a problem with some http proxies where they refuse GET
17979 requests that specify "Content-Length: 0" (reported by Adrian).
17980 - Fix wrong log message when you add a "HiddenServiceNodes" config
17981 line without any HiddenServiceDir line (reported by Chris Thomas).
17984 - Write the TorVersion into the state file so we have a prayer of
17985 keeping forward and backward compatibility.
17986 - Revive the FascistFirewall config option rather than eliminating it:
17987 now it's a synonym for ReachableAddresses *:80,*:443.
17988 - Clients choose directory servers from the network status lists,
17989 not from their internal list of router descriptors. Now they can
17990 go to caches directly rather than needing to go to authorities
17992 - Directory authorities ignore router descriptors that have only
17993 cosmetic differences: do this for 0.1.0.x servers now too.
17994 - Add a new flag to network-status indicating whether the server
17995 can answer v2 directory requests too.
17996 - Authdirs now stop whining so loudly about bad descriptors that
17997 they fetch from other dirservers. So when there's a log complaint,
17998 it's for sure from a freshly uploaded descriptor.
17999 - Reduce memory requirements in our structs by changing the order
18001 - There used to be two ways to specify your listening ports in a
18002 server descriptor: on the "router" line and with a separate "ports"
18003 line. Remove support for the "ports" line.
18004 - New config option "AuthDirRejectUnlisted" for auth dirservers as
18005 a panic button: if we get flooded with unusable servers we can
18006 revert to only listing servers in the approved-routers file.
18007 - Auth dir servers can now mark a fingerprint as "!reject" or
18008 "!invalid" in the approved-routers file (as its nickname), to
18009 refuse descriptors outright or include them but marked as invalid.
18010 - Servers store bandwidth history across restarts/crashes.
18011 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
18012 get a better idea of why their circuits failed. Not used yet.
18013 - Directory mirrors now cache up to 16 unrecognized network-status
18014 docs. Now we can add new authdirservers and they'll be cached too.
18015 - When picking a random directory, prefer non-authorities if any
18017 - New controller option "getinfo desc/all-recent" to fetch the
18018 latest server descriptor for every router that Tor knows about.
18021 Changes in version 0.1.0.16 - 2006-01-02
18022 o Crash bugfixes on 0.1.0.x:
18023 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
18024 corrupting the heap, losing FDs, or crashing when we need to resize
18025 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
18026 - It turns out sparc64 platforms crash on unaligned memory access
18027 too -- so detect and avoid this.
18028 - Handle truncated compressed data correctly (by detecting it and
18030 - Fix possible-but-unlikely free(NULL) in control.c.
18031 - When we were closing connections, there was a rare case that
18032 stomped on memory, triggering seg faults and asserts.
18033 - Avoid potential infinite recursion when building a descriptor. (We
18034 don't know that it ever happened, but better to fix it anyway.)
18035 - We were neglecting to unlink marked circuits from soon-to-close OR
18036 connections, which caused some rare scribbling on freed memory.
18037 - Fix a memory stomping race bug when closing the joining point of two
18038 rendezvous circuits.
18039 - Fix an assert in time parsing found by Steven Murdoch.
18041 o Other bugfixes on 0.1.0.x:
18042 - When we're doing reachability testing, provide more useful log
18043 messages so the operator knows what to expect.
18044 - Do not check whether DirPort is reachable when we are suppressing
18045 advertising it because of hibernation.
18046 - When building with -static or on Solaris, we sometimes needed -ldl.
18047 - When we're deciding whether a stream has enough circuits around
18048 that can handle it, count the freshly dirty ones and not the ones
18049 that are so dirty they won't be able to handle it.
18050 - When we're expiring old circuits, we had a logic error that caused
18051 us to close new rendezvous circuits rather than old ones.
18052 - Give a more helpful log message when you try to change ORPort via
18053 the controller: you should upgrade Tor if you want that to work.
18054 - We were failing to parse Tor versions that start with "Tor ".
18055 - Tolerate faulty streams better: when a stream fails for reason
18056 exitpolicy, stop assuming that the router is lying about his exit
18057 policy. When a stream fails for reason misc, allow it to retry just
18058 as if it was resolvefailed. When a stream has failed three times,
18059 reset its failure count so we can try again and get all three tries.
18062 Changes in version 0.1.1.10-alpha - 2005-12-11
18063 o Correctness bugfixes on 0.1.0.x:
18064 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
18065 corrupting the heap, losing FDs, or crashing when we need to resize
18066 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
18067 - Stop doing the complex voodoo overkill checking for insecure
18068 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
18069 - When we were closing connections, there was a rare case that
18070 stomped on memory, triggering seg faults and asserts.
18071 - We were neglecting to unlink marked circuits from soon-to-close OR
18072 connections, which caused some rare scribbling on freed memory.
18073 - When we're deciding whether a stream has enough circuits around
18074 that can handle it, count the freshly dirty ones and not the ones
18075 that are so dirty they won't be able to handle it.
18076 - Recover better from TCP connections to Tor servers that are
18077 broken but don't tell you (it happens!); and rotate TLS
18078 connections once a week.
18079 - When we're expiring old circuits, we had a logic error that caused
18080 us to close new rendezvous circuits rather than old ones.
18081 - Fix a scary-looking but apparently harmless bug where circuits
18082 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
18083 servers, and never switch to state CIRCUIT_STATE_OPEN.
18084 - When building with -static or on Solaris, we sometimes needed to
18086 - Give a useful message when people run Tor as the wrong user,
18087 rather than telling them to start chowning random directories.
18088 - We were failing to inform the controller about new .onion streams.
18090 o Security bugfixes on 0.1.0.x:
18091 - Refuse server descriptors if the fingerprint line doesn't match
18092 the included identity key. Tor doesn't care, but other apps (and
18093 humans) might actually be trusting the fingerprint line.
18094 - We used to kill the circuit when we receive a relay command we
18095 don't recognize. Now we just drop it.
18096 - Start obeying our firewall options more rigorously:
18097 . If we can't get to a dirserver directly, try going via Tor.
18098 . Don't ever try to connect (as a client) to a place our
18099 firewall options forbid.
18100 . If we specify a proxy and also firewall options, obey the
18101 firewall options even when we're using the proxy: some proxies
18102 can only proxy to certain destinations.
18103 - Fix a bug found by Lasse Overlier: when we were making internal
18104 circuits (intended to be cannibalized later for rendezvous and
18105 introduction circuits), we were picking them so that they had
18106 useful exit nodes. There was no need for this, and it actually
18107 aids some statistical attacks.
18108 - Start treating internal circuits and exit circuits separately.
18109 It's important to keep them separate because internal circuits
18110 have their last hops picked like middle hops, rather than like
18111 exit hops. So exiting on them will break the user's expectations.
18113 o Bugfixes on 0.1.1.x:
18114 - Take out the mis-feature where we tried to detect IP address
18115 flapping for people with DynDNS, and chose not to upload a new
18116 server descriptor sometimes.
18117 - Try to be compatible with OpenSSL 0.9.6 again.
18118 - Log fix: when the controller is logging about .onion addresses,
18119 sometimes it didn't include the ".onion" part of the address.
18120 - Don't try to modify options->DirServers internally -- if the
18121 user didn't specify any, just add the default ones directly to
18122 the trusted dirserver list. This fixes a bug where people running
18123 controllers would use SETCONF on some totally unrelated config
18124 option, and Tor would start yelling at them about changing their
18126 - Let the controller's redirectstream command specify a port, in
18127 case the controller wants to change that too.
18128 - When we requested a pile of server descriptors, we sometimes
18129 accidentally launched a duplicate request for the first one.
18130 - Bugfix for trackhostexits: write down the fingerprint of the
18131 chosen exit, not its nickname, because the chosen exit might not
18133 - When parsing foo.exit, if foo is unknown, and we are leaving
18134 circuits unattached, set the chosen_exit field and leave the
18135 address empty. This matters because controllers got confused
18137 - Directory authorities no longer try to download server
18138 descriptors that they know they will reject.
18140 o Features and updates:
18141 - Replace balanced trees with hash tables: this should make stuff
18142 significantly faster.
18143 - Resume using the AES counter-mode implementation that we ship,
18144 rather than OpenSSL's. Ours is significantly faster.
18145 - Many other CPU and memory improvements.
18146 - Add a new config option FastFirstHopPK (on by default) so clients
18147 do a trivial crypto handshake for their first hop, since TLS has
18148 already taken care of confidentiality and authentication.
18149 - Add a new config option TestSocks so people can see if their
18150 applications are using socks4, socks4a, socks5-with-ip, or
18151 socks5-with-hostname. This way they don't have to keep mucking
18152 with tcpdump and wondering if something got cached somewhere.
18153 - Warn when listening on a public address for socks. I suspect a
18154 lot of people are setting themselves up as open socks proxies,
18155 and they have no idea that jerks on the Internet are using them,
18156 since they simply proxy the traffic into the Tor network.
18157 - Add "private:*" as an alias in configuration for policies. Now
18158 you can simplify your exit policy rather than needing to list
18159 every single internal or nonroutable network space.
18160 - Add a new controller event type that allows controllers to get
18161 all server descriptors that were uploaded to a router in its role
18162 as authoritative dirserver.
18163 - Start shipping socks-extensions.txt, tor-doc-unix.html,
18164 tor-doc-server.html, and stylesheet.css in the tarball.
18165 - Stop shipping tor-doc.html in the tarball.
18168 Changes in version 0.1.1.9-alpha - 2005-11-15
18169 o Usability improvements:
18170 - Start calling it FooListenAddress rather than FooBindAddress,
18171 since few of our users know what it means to bind an address
18173 - Reduce clutter in server logs. We're going to try to make
18174 them actually usable now. New config option ProtocolWarnings that
18175 lets you hear about how _other Tors_ are breaking the protocol. Off
18177 - Divide log messages into logging domains. Once we put some sort
18178 of interface on this, it will let people looking at more verbose
18179 log levels specify the topics they want to hear more about.
18180 - Make directory servers return better http 404 error messages
18181 instead of a generic "Servers unavailable".
18182 - Check for even more Windows version flags when writing the platform
18183 string in server descriptors, and note any we don't recognize.
18184 - Clean up more of the OpenSSL memory when exiting, so we can detect
18185 memory leaks better.
18186 - Make directory authorities be non-versioning, non-naming by
18187 default. Now we can add new directory servers without requiring
18188 their operators to pay close attention.
18189 - When logging via syslog, include the pid whenever we provide
18190 a log entry. Suggested by Todd Fries.
18192 o Performance improvements:
18193 - Directory servers now silently throw away new descriptors that
18194 haven't changed much if the timestamps are similar. We do this to
18195 tolerate older Tor servers that upload a new descriptor every 15
18196 minutes. (It seemed like a good idea at the time.)
18197 - Inline bottleneck smartlist functions; use fast versions by default.
18198 - Add a "Map from digest to void*" abstraction digestmap_t so we
18199 can do less hex encoding/decoding. Use it in router_get_by_digest()
18200 to resolve a performance bottleneck.
18201 - Allow tor_gzip_uncompress to extract as much as possible from
18202 truncated compressed data. Try to extract as many
18203 descriptors as possible from truncated http responses (when
18204 DIR_PURPOSE_FETCH_ROUTERDESC).
18205 - Make circ->onionskin a pointer, not a static array. moria2 was using
18206 125000 circuit_t's after it had been up for a few weeks, which
18207 translates to 20+ megs of wasted space.
18208 - The private half of our EDH handshake keys are now chosen out
18209 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
18211 o Security improvements:
18212 - Start making directory caches retain old routerinfos, so soon
18213 clients can start asking by digest of descriptor rather than by
18214 fingerprint of server.
18215 - Add half our entropy from RAND_poll in OpenSSL. This knows how
18216 to use egd (if present), openbsd weirdness (if present), vms/os2
18217 weirdness (if we ever port there), and more in the future.
18219 o Bugfixes on 0.1.0.x:
18220 - Do round-robin writes of at most 16 kB per write. This might be
18221 more fair on loaded Tor servers, and it might resolve our Windows
18222 crash bug. It might also slow things down.
18223 - Our TLS handshakes were generating a single public/private
18224 keypair for the TLS context, rather than making a new one for
18225 each new connections. Oops. (But we were still rotating them
18226 periodically, so it's not so bad.)
18227 - When we were cannibalizing a circuit with a particular exit
18228 node in mind, we weren't checking to see if that exit node was
18229 already present earlier in the circuit. Oops.
18230 - When a Tor server's IP changes (e.g. from a dyndns address),
18231 upload a new descriptor so clients will learn too.
18232 - Really busy servers were keeping enough circuits open on stable
18233 connections that they were wrapping around the circuit_id
18234 space. (It's only two bytes.) This exposed a bug where we would
18235 feel free to reuse a circuit_id even if it still exists but has
18236 been marked for close. Try to fix this bug. Some bug remains.
18237 - If we would close a stream early (e.g. it asks for a .exit that
18238 we know would refuse it) but the LeaveStreamsUnattached config
18239 option is set by the controller, then don't close it.
18241 o Bugfixes on 0.1.1.8-alpha:
18242 - Fix a big pile of memory leaks, some of them serious.
18243 - Do not try to download a routerdesc if we would immediately reject
18245 - Resume inserting a newline between all router descriptors when
18246 generating (old style) signed directories, since our spec says
18248 - When providing content-type application/octet-stream for
18249 server descriptors using .z, we were leaving out the
18250 content-encoding header. Oops. (Everything tolerated this just
18251 fine, but that doesn't mean we need to be part of the problem.)
18252 - Fix a potential seg fault in getconf and getinfo using version 1
18253 of the controller protocol.
18254 - Avoid crash: do not check whether DirPort is reachable when we
18255 are suppressing it because of hibernation.
18256 - Make --hash-password not crash on exit.
18259 Changes in version 0.1.1.8-alpha - 2005-10-07
18260 o New features (major):
18261 - Clients don't download or use the directory anymore. Now they
18262 download and use network-statuses from the trusted dirservers,
18263 and fetch individual server descriptors as needed from mirrors.
18264 See dir-spec.txt for all the gory details.
18265 - Be more conservative about whether to advertise our DirPort.
18266 The main change is to not advertise if we're running at capacity
18267 and either a) we could hibernate or b) our capacity is low and
18268 we're using a default DirPort.
18269 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
18271 o New features (minor):
18272 - Try to be smart about when to retry network-status and
18273 server-descriptor fetches. Still needs some tuning.
18274 - Stop parsing, storing, or using running-routers output (but
18275 mirrors still cache and serve it).
18276 - Consider a threshold of versioning dirservers (dirservers who have
18277 an opinion about which Tor versions are still recommended) before
18278 deciding whether to warn the user that he's obsolete.
18279 - Dirservers can now reject/invalidate by key and IP, with the
18280 config options "AuthDirInvalid" and "AuthDirReject". This is
18281 useful since currently we automatically list servers as running
18282 and usable even if we know they're jerks.
18283 - Provide dire warnings to any users who set DirServer; move it out
18284 of torrc.sample and into torrc.complete.
18285 - Add MyFamily to torrc.sample in the server section.
18286 - Add nicknames to the DirServer line, so we can refer to them
18287 without requiring all our users to memorize their IP addresses.
18288 - When we get an EOF or a timeout on a directory connection, note
18289 how many bytes of serverdesc we are dropping. This will help
18290 us determine whether it is smart to parse incomplete serverdesc
18292 - Add a new function to "change pseudonyms" -- that is, to stop
18293 using any currently-dirty circuits for new streams, so we don't
18294 link new actions to old actions. Currently it's only called on
18295 HUP (or SIGNAL RELOAD).
18296 - On sighup, if UseHelperNodes changed to 1, use new circuits.
18297 - Start using RAND_bytes rather than RAND_pseudo_bytes from
18298 OpenSSL. Also, reseed our entropy every hour, not just at
18299 startup. And entropy in 512-bit chunks, not 160-bit chunks.
18301 o Fixes on 0.1.1.7-alpha:
18302 - Nobody ever implemented EVENT_ADDRMAP for control protocol
18303 version 0, so don't let version 0 controllers ask for it.
18304 - If you requested something with too many newlines via the
18305 v1 controller protocol, you could crash tor.
18306 - Fix a number of memory leaks, including some pretty serious ones.
18307 - Re-enable DirPort testing again, so Tor servers will be willing
18308 to advertise their DirPort if it's reachable.
18309 - On TLS handshake, only check the other router's nickname against
18310 its expected nickname if is_named is set.
18312 o Fixes forward-ported from 0.1.0.15:
18313 - Don't crash when we don't have any spare file descriptors and we
18314 try to spawn a dns or cpu worker.
18315 - Make the numbers in read-history and write-history into uint64s,
18316 so they don't overflow and publish negatives in the descriptor.
18318 o Fixes on 0.1.0.x:
18319 - For the OS X package's modified privoxy config file, comment
18320 out the "logfile" line so we don't log everything passed
18322 - We were whining about using socks4 or socks5-with-local-lookup
18323 even when it's an IP in the "virtual" range we designed exactly
18325 - We were leaking some memory every time the client changes IPs.
18326 - Never call free() on tor_malloc()d memory. This will help us
18327 use dmalloc to detect memory leaks.
18328 - Check for named servers when looking them up by nickname;
18329 warn when we'recalling a non-named server by its nickname;
18330 don't warn twice about the same name.
18331 - Try to list MyFamily elements by key, not by nickname, and warn
18332 if we've not heard of the server.
18333 - Make windows platform detection (uname equivalent) smarter.
18334 - It turns out sparc64 doesn't like unaligned access either.
18337 Changes in version 0.1.0.15 - 2005-09-23
18338 o Bugfixes on 0.1.0.x:
18339 - Reject ports 465 and 587 (spam targets) in default exit policy.
18340 - Don't crash when we don't have any spare file descriptors and we
18341 try to spawn a dns or cpu worker.
18342 - Get rid of IgnoreVersion undocumented config option, and make us
18343 only warn, never exit, when we're running an obsolete version.
18344 - Don't try to print a null string when your server finds itself to
18345 be unreachable and the Address config option is empty.
18346 - Make the numbers in read-history and write-history into uint64s,
18347 so they don't overflow and publish negatives in the descriptor.
18348 - Fix a minor memory leak in smartlist_string_remove().
18349 - We were only allowing ourselves to upload a server descriptor at
18350 most every 20 minutes, even if it changed earlier than that.
18351 - Clean up log entries that pointed to old URLs.
18354 Changes in version 0.1.1.7-alpha - 2005-09-14
18355 o Fixes on 0.1.1.6-alpha:
18356 - Exit servers were crashing when people asked them to make a
18357 connection to an address not in their exit policy.
18358 - Looking up a non-existent stream for a v1 control connection would
18360 - Fix a seg fault if we ask a dirserver for a descriptor by
18361 fingerprint but he doesn't know about him.
18362 - SETCONF was appending items to linelists, not clearing them.
18363 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
18364 out and refuse the setconf if it would fail.
18365 - Downgrade the dirserver log messages when whining about
18369 - Add Peter Palfrader's check-tor script to tor/contrib/
18370 It lets you easily check whether a given server (referenced by
18371 nickname) is reachable by you.
18372 - Numerous changes to move towards client-side v2 directories. Not
18375 o Fixes on 0.1.0.x:
18376 - If the user gave tor an odd number of command-line arguments,
18377 we were silently ignoring the last one. Now we complain and fail.
18378 [This wins the oldest-bug prize -- this bug has been present since
18379 November 2002, as released in Tor 0.0.0.]
18380 - Do not use unaligned memory access on alpha, mips, or mipsel.
18381 It *works*, but is very slow, so we treat them as if it doesn't.
18382 - Retry directory requests if we fail to get an answer we like
18383 from a given dirserver (we were retrying before, but only if
18384 we fail to connect).
18385 - When writing the RecommendedVersions line, sort them first.
18386 - When the client asked for a rendezvous port that the hidden
18387 service didn't want to provide, we were sending an IP address
18388 back along with the end cell. Fortunately, it was zero. But stop
18390 - Correct "your server is reachable" log entries to indicate that
18391 it was self-testing that told us so.
18394 Changes in version 0.1.1.6-alpha - 2005-09-09
18395 o Fixes on 0.1.1.5-alpha:
18396 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
18397 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
18398 - Fix bug with tor_memmem finding a match at the end of the string.
18399 - Make unit tests run without segfaulting.
18400 - Resolve some solaris x86 compile warnings.
18401 - Handle duplicate lines in approved-routers files without warning.
18402 - Fix bug where as soon as a server refused any requests due to his
18403 exit policy (e.g. when we ask for localhost and he tells us that's
18404 127.0.0.1 and he won't do it), we decided he wasn't obeying his
18405 exit policy using him for any exits.
18406 - Only do openssl hardware accelerator stuff if openssl version is
18409 o New controller features/fixes:
18410 - Add a "RESETCONF" command so you can set config options like
18411 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
18412 a config option in the torrc with no value, then it clears it
18413 entirely (rather than setting it to its default).
18414 - Add a "GETINFO config-file" to tell us where torrc is.
18415 - Avoid sending blank lines when GETINFO replies should be empty.
18416 - Add a QUIT command for the controller (for using it manually).
18417 - Fix a bug in SAVECONF that was adding default dirservers and
18418 other redundant entries to the torrc file.
18420 o Start on the new directory design:
18421 - Generate, publish, cache, serve new network-status format.
18422 - Publish individual descriptors (by fingerprint, by "all", and by
18424 - Publish client and server recommended versions separately.
18425 - Allow tor_gzip_uncompress() to handle multiple concatenated
18426 compressed strings. Serve compressed groups of router
18427 descriptors. The compression logic here could be more
18429 - Distinguish v1 authorities (all currently trusted directories)
18430 from v2 authorities (all trusted directories).
18431 - Change DirServers config line to note which dirs are v1 authorities.
18432 - Add configuration option "V1AuthoritativeDirectory 1" which
18433 moria1, moria2, and tor26 should set.
18434 - Remove option when getting directory cache to see whether they
18435 support running-routers; they all do now. Replace it with one
18436 to see whether caches support v2 stuff.
18439 - Dirservers now do their own external reachability testing of each
18440 Tor server, and only list them as running if they've been found to
18441 be reachable. We also send back warnings to the server's logs if
18442 it uploads a descriptor that we already believe is unreachable.
18443 - Implement exit enclaves: if we know an IP address for the
18444 destination, and there's a running Tor server at that address
18445 which allows exit to the destination, then extend the circuit to
18446 that exit first. This provides end-to-end encryption and end-to-end
18447 authentication. Also, if the user wants a .exit address or enclave,
18448 use 4 hops rather than 3, and cannibalize a general circ for it
18450 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
18451 controller. Also, rotate dns and cpu workers if the controller
18452 changes options that will affect them; and initialize the dns
18453 worker cache tree whether or not we start out as a server.
18454 - Only upload a new server descriptor when options change, 18
18455 hours have passed, uptime is reset, or bandwidth changes a lot.
18456 - Check [X-]Forwarded-For headers in HTTP requests when generating
18457 log messages. This lets people run dirservers (and caches) behind
18458 Apache but still know which IP addresses are causing warnings.
18460 o Config option changes:
18461 - Replace (Fascist)Firewall* config options with a new
18462 ReachableAddresses option that understands address policies.
18463 For example, "ReachableAddresses *:80,*:443"
18464 - Get rid of IgnoreVersion undocumented config option, and make us
18465 only warn, never exit, when we're running an obsolete version.
18466 - Make MonthlyAccountingStart config option truly obsolete now.
18468 o Fixes on 0.1.0.x:
18469 - Reject ports 465 and 587 in the default exit policy, since
18470 people have started using them for spam too.
18471 - It turns out we couldn't bootstrap a network since we added
18472 reachability detection in 0.1.0.1-rc. Good thing the Tor network
18473 has never gone down. Add an AssumeReachable config option to let
18474 servers and dirservers bootstrap. When we're trying to build a
18475 high-uptime or high-bandwidth circuit but there aren't enough
18476 suitable servers, try being less picky rather than simply failing.
18477 - Our logic to decide if the OR we connected to was the right guy
18478 was brittle and maybe open to a mitm for unverified routers.
18479 - We weren't cannibalizing circuits correctly for
18480 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
18481 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
18482 build those from scratch. This should make hidden services faster.
18483 - Predict required circuits better, with an eye toward making hidden
18484 services faster on the service end.
18485 - Retry streams if the exit node sends back a 'misc' failure. This
18486 should result in fewer random failures. Also, after failing
18487 from resolve failed or misc, reset the num failures, so we give
18488 it a fair shake next time we try.
18489 - Clean up the rendezvous warn log msgs, and downgrade some to info.
18490 - Reduce severity on logs about dns worker spawning and culling.
18491 - When we're shutting down and we do something like try to post a
18492 server descriptor or rendezvous descriptor, don't complain that
18493 we seem to be unreachable. Of course we are, we're shutting down.
18494 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
18495 We don't use them yet, but maybe one day our DNS resolver will be
18496 able to discover them.
18497 - Make ContactInfo mandatory for authoritative directory servers.
18498 - Require server descriptors to list IPv4 addresses -- hostnames
18499 are no longer allowed. This also fixes some potential security
18500 problems with people providing hostnames as their address and then
18501 preferentially resolving them to partition users.
18502 - Change log line for unreachability to explicitly suggest /etc/hosts
18503 as the culprit. Also make it clearer what IP address and ports we're
18504 testing for reachability.
18505 - Put quotes around user-supplied strings when logging so users are
18506 more likely to realize if they add bad characters (like quotes)
18508 - Let auth dir servers start without specifying an Address config
18510 - Make unit tests (and other invocations that aren't the real Tor)
18511 run without launching listeners, creating subdirectories, and so on.
18514 Changes in version 0.1.1.5-alpha - 2005-08-08
18515 o Bugfixes included in 0.1.0.14.
18517 o Bugfixes on 0.1.0.x:
18518 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
18519 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
18520 it would silently using ignore the 6668.
18523 Changes in version 0.1.0.14 - 2005-08-08
18524 o Bugfixes on 0.1.0.x:
18525 - Fix the other half of the bug with crypto handshakes
18527 - Fix an assert trigger if you send a 'signal term' via the
18528 controller when it's listening for 'event info' messages.
18531 Changes in version 0.1.1.4-alpha - 2005-08-04
18532 o Bugfixes included in 0.1.0.13.
18535 - Improve tor_gettimeofday() granularity on windows.
18536 - Make clients regenerate their keys when their IP address changes.
18537 - Implement some more GETINFO goodness: expose helper nodes, config
18538 options, getinfo keys.
18541 Changes in version 0.1.0.13 - 2005-08-04
18542 o Bugfixes on 0.1.0.x:
18543 - Fix a critical bug in the security of our crypto handshakes.
18544 - Fix a size_t underflow in smartlist_join_strings2() that made
18545 it do bad things when you hand it an empty smartlist.
18546 - Fix Windows installer to ship Tor license (thanks to Aphex for
18547 pointing out this oversight) and put a link to the doc directory
18549 - Explicitly set no-unaligned-access for sparc: it turns out the
18550 new gcc's let you compile broken code, but that doesn't make it
18554 Changes in version 0.1.1.3-alpha - 2005-07-23
18555 o Bugfixes on 0.1.1.2-alpha:
18556 - Fix a bug in handling the controller's "post descriptor"
18558 - Fix several bugs in handling the controller's "extend circuit"
18560 - Fix a bug in handling the controller's "stream status" event.
18561 - Fix an assert failure if we have a controller listening for
18562 circuit events and we go offline.
18563 - Re-allow hidden service descriptors to publish 0 intro points.
18564 - Fix a crash when generating your hidden service descriptor if
18565 you don't have enough intro points already.
18567 o New features on 0.1.1.2-alpha:
18568 - New controller function "getinfo accounting", to ask how
18569 many bytes we've used in this time period.
18570 - Experimental support for helper nodes: a lot of the risk from
18571 a small static adversary comes because users pick new random
18572 nodes every time they rebuild a circuit. Now users will try to
18573 stick to the same small set of entry nodes if they can. Not
18574 enabled by default yet.
18576 o Bugfixes on 0.1.0.12:
18577 - If you're an auth dir server, always publish your dirport,
18578 even if you haven't yet found yourself to be reachable.
18579 - Fix a size_t underflow in smartlist_join_strings2() that made
18580 it do bad things when you hand it an empty smartlist.
18583 Changes in version 0.1.0.12 - 2005-07-18
18584 o New directory servers:
18585 - tor26 has changed IP address.
18587 o Bugfixes on 0.1.0.x:
18588 - Fix a possible double-free in tor_gzip_uncompress().
18589 - When --disable-threads is set, do not search for or link against
18590 pthreads libraries.
18591 - Don't trigger an assert if an authoritative directory server
18592 claims its dirport is 0.
18593 - Fix bug with removing Tor as an NT service: some people were
18594 getting "The service did not return an error." Thanks to Matt
18598 Changes in version 0.1.1.2-alpha - 2005-07-15
18599 o New directory servers:
18600 - tor26 has changed IP address.
18602 o Bugfixes on 0.1.0.x, crashes/leaks:
18603 - Port the servers-not-obeying-their-exit-policies fix from
18605 - Fix an fd leak in start_daemon().
18606 - On Windows, you can't always reopen a port right after you've
18607 closed it. So change retry_listeners() to only close and re-open
18608 ports that have changed.
18609 - Fix a possible double-free in tor_gzip_uncompress().
18611 o Bugfixes on 0.1.0.x, usability:
18612 - When tor_socketpair() fails in Windows, give a reasonable
18613 Windows-style errno back.
18614 - Let people type "tor --install" as well as "tor -install" when
18616 want to make it an NT service.
18617 - NT service patch from Matt Edman to improve error messages.
18618 - When the controller asks for a config option with an abbreviated
18619 name, give the full name in our response.
18620 - Correct the man page entry on TrackHostExitsExpire.
18621 - Looks like we were never delivering deflated (i.e. compressed)
18622 running-routers lists, even when asked. Oops.
18623 - When --disable-threads is set, do not search for or link against
18624 pthreads libraries.
18626 o Bugfixes on 0.1.1.x:
18627 - Fix a seg fault with autodetecting which controller version is
18631 - New hidden service descriptor format: put a version in it, and
18632 let people specify introduction/rendezvous points that aren't
18633 in "the directory" (which is subjective anyway).
18634 - Allow the DEBUG controller event to work again. Mark certain log
18635 entries as "don't tell this to controllers", so we avoid cycles.
18638 Changes in version 0.1.0.11 - 2005-06-30
18639 o Bugfixes on 0.1.0.x:
18640 - Fix major security bug: servers were disregarding their
18641 exit policies if clients behaved unexpectedly.
18642 - Make OS X init script check for missing argument, so we don't
18643 confuse users who invoke it incorrectly.
18644 - Fix a seg fault in "tor --hash-password foo".
18645 - The MAPADDRESS control command was broken.
18648 Changes in version 0.1.1.1-alpha - 2005-06-29
18650 - Make OS X init script check for missing argument, so we don't
18651 confuse users who invoke it incorrectly.
18652 - Fix a seg fault in "tor --hash-password foo".
18653 - Fix a possible way to DoS dirservers.
18654 - When we complain that your exit policy implicitly allows local or
18655 private address spaces, name them explicitly so operators can
18657 - Make the log message less scary when all the dirservers are
18658 temporarily unreachable.
18659 - We were printing the number of idle dns workers incorrectly when
18663 - Revised controller protocol (version 1) that uses ascii rather
18664 than binary. Add supporting libraries in python and java so you
18665 can use the controller from your applications without caring how
18666 our protocol works.
18667 - Spiffy new support for crypto hardware accelerators. Can somebody
18671 Changes in version 0.0.9.10 - 2005-06-16
18672 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
18673 - Refuse relay cells that claim to have a length larger than the
18674 maximum allowed. This prevents a potential attack that could read
18675 arbitrary memory (e.g. keys) from an exit server's process
18679 Changes in version 0.1.0.10 - 2005-06-14
18680 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
18681 libevent before 1.1a.
18684 Changes in version 0.1.0.9-rc - 2005-06-09
18686 - Reset buf->highwater every time buf_shrink() is called, not just on
18687 a successful shrink. This was causing significant memory bloat.
18688 - Fix buffer overflow when checking hashed passwords.
18689 - Security fix: if seeding the RNG on Win32 fails, quit.
18690 - Allow seeding the RNG on Win32 even when you're not running as
18692 - Disable threading on Solaris too. Something is wonky with it,
18693 cpuworkers, and reentrant libs.
18694 - Reenable the part of the code that tries to flush as soon as an
18695 OR outbuf has a full TLS record available. Perhaps this will make
18696 OR outbufs not grow as huge except in rare cases, thus saving lots
18697 of CPU time plus memory.
18698 - Reject malformed .onion addresses rather then passing them on as
18699 normal web requests.
18700 - Adapt patch from Adam Langley: fix possible memory leak in
18701 tor_lookup_hostname().
18702 - Initialize libevent later in the startup process, so the logs are
18703 already established by the time we start logging libevent warns.
18704 - Use correct errno on win32 if libevent fails.
18705 - Check and warn about known-bad/slow libevent versions.
18706 - Pay more attention to the ClientOnly config option.
18707 - Have torctl.in/tor.sh.in check for location of su binary (needed
18709 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
18710 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
18711 HttpProxyAuthenticator
18712 - Stop warning about sigpipes in the logs. We're going to
18713 pretend that getting these occassionally is normal and fine.
18714 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
18716 installer screens; and don't put stuff into StartupItems unless
18717 the user asks you to.
18718 - Require servers that use the default dirservers to have public IP
18719 addresses. We have too many servers that are configured with private
18720 IPs and their admins never notice the log entries complaining that
18721 their descriptors are being rejected.
18722 - Add OSX uninstall instructions. An actual uninstall script will
18726 Changes in version 0.1.0.8-rc - 2005-05-23
18728 - It turns out that kqueue on OS X 10.3.9 was causing kernel
18729 panics. Disable kqueue on all OS X Tors.
18730 - Fix RPM: remove duplicate line accidentally added to the rpm
18732 - Disable threads on openbsd too, since its gethostaddr is not
18734 - Tolerate libevent 0.8 since it still works, even though it's
18736 - Enable building on Red Hat 9.0 again.
18737 - Allow the middle hop of the testing circuit to be running any
18738 version, now that most of them have the bugfix to let them connect
18739 to unknown servers. This will allow reachability testing to work
18740 even when 0.0.9.7-0.0.9.9 become obsolete.
18741 - Handle relay cells with rh.length too large. This prevents
18742 a potential attack that could read arbitrary memory (maybe even
18743 keys) from the exit server's process.
18744 - We screwed up the dirport reachability testing when we don't yet
18745 have a cached version of the directory. Hopefully now fixed.
18746 - Clean up router_load_single_router() (used by the controller),
18747 so it doesn't seg fault on error.
18748 - Fix a minor memory leak when somebody establishes an introduction
18749 point at your Tor server.
18750 - If a socks connection ends because read fails, don't warn that
18751 you're not sending a socks reply back.
18754 - Add HttpProxyAuthenticator config option too, that works like
18755 the HttpsProxyAuthenticator config option.
18756 - Encode hashed controller passwords in hex instead of base64,
18757 to make it easier to write controllers.
18760 Changes in version 0.1.0.7-rc - 2005-05-17
18762 - Fix a bug in the OS X package installer that prevented it from
18763 installing on Tiger.
18764 - Fix a script bug in the OS X package installer that made it
18765 complain during installation.
18766 - Find libevent even if it's hiding in /usr/local/ and your
18767 CFLAGS and LDFLAGS don't tell you to look there.
18768 - Be able to link with libevent as a shared library (the default
18769 after 1.0d), even if it's hiding in /usr/local/lib and even
18770 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
18771 assuming you're running gcc. Otherwise fail and give a useful
18773 - Fix a bug in the RPM packager: set home directory for _tor to
18774 something more reasonable when first installing.
18775 - Free a minor amount of memory that is still reachable on exit.
18778 Changes in version 0.1.0.6-rc - 2005-05-14
18780 - Implement --disable-threads configure option. Disable threads on
18781 netbsd by default, because it appears to have no reentrant resolver
18783 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
18784 release (1.1) detects and disables kqueue if it's broken.
18785 - Append default exit policy before checking for implicit internal
18786 addresses. Now we don't log a bunch of complaints on startup
18787 when using the default exit policy.
18788 - Some people were putting "Address " in their torrc, and they had
18789 a buggy resolver that resolved " " to 0.0.0.0. Oops.
18790 - If DataDir is ~/.tor, and that expands to /.tor, then default to
18791 LOCALSTATEDIR/tor instead.
18792 - Fix fragmented-message bug in TorControl.py.
18793 - Resolve a minor bug which would prevent unreachable dirports
18794 from getting suppressed in the published descriptor.
18795 - When the controller gave us a new descriptor, we weren't resolving
18796 it immediately, so Tor would think its address was 0.0.0.0 until
18797 we fetched a new directory.
18798 - Fix an uppercase/lowercase case error in suppressing a bogus
18799 libevent warning on some Linuxes.
18802 - Begin scrubbing sensitive strings from logs by default. Turn off
18803 the config option SafeLogging if you need to do debugging.
18804 - Switch to a new buffer management algorithm, which tries to avoid
18805 reallocing and copying quite as much. In first tests it looks like
18806 it uses *more* memory on average, but less cpu.
18807 - First cut at support for "create-fast" cells. Clients can use
18808 these when extending to their first hop, since the TLS already
18809 provides forward secrecy and authentication. Not enabled on
18811 - When dirservers refuse a router descriptor, we now log its
18812 contactinfo, platform, and the poster's IP address.
18813 - Call tor_free_all instead of connections_free_all after forking, to
18814 save memory on systems that need to fork.
18815 - Whine at you if you're a server and you don't set your contactinfo.
18816 - Implement --verify-config command-line option to check if your torrc
18817 is valid without actually launching Tor.
18818 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
18819 rather than just rejecting it.
18822 Changes in version 0.1.0.5-rc - 2005-04-27
18824 - Stop trying to print a null pointer if an OR conn fails because
18825 we didn't like its cert.
18827 - Switch our internal buffers implementation to use a ring buffer,
18828 to hopefully improve performance for fast servers a lot.
18829 - Add HttpsProxyAuthenticator support (basic auth only), based
18830 on patch from Adam Langley.
18831 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
18832 the fast servers that have been joining lately.
18833 - Give hidden service accesses extra time on the first attempt,
18834 since 60 seconds is often only barely enough. This might improve
18836 - Improve performance for dirservers: stop re-parsing the whole
18837 directory every time you regenerate it.
18838 - Add more debugging info to help us find the weird dns freebsd
18839 pthreads bug; cleaner debug messages to help track future issues.
18842 Changes in version 0.0.9.9 - 2005-04-23
18843 o Bugfixes on 0.0.9.x:
18844 - If unofficial Tor clients connect and send weird TLS certs, our
18845 Tor server triggers an assert. This release contains a minimal
18846 backport from the broader fix that we put into 0.1.0.4-rc.
18849 Changes in version 0.1.0.4-rc - 2005-04-23
18851 - If unofficial Tor clients connect and send weird TLS certs, our
18852 Tor server triggers an assert. Stop asserting, and start handling
18853 TLS errors better in other situations too.
18854 - When the controller asks us to tell it about all the debug-level
18855 logs, it turns out we were generating debug-level logs while
18856 telling it about them, which turns into a bad loop. Now keep
18857 track of whether you're sending a debug log to the controller,
18858 and don't log when you are.
18859 - Fix the "postdescriptor" feature of the controller interface: on
18860 non-complete success, only say "done" once.
18862 - Clients are now willing to load balance over up to 2mB, not 1mB,
18863 of advertised bandwidth capacity.
18864 - Add a NoPublish config option, so you can be a server (e.g. for
18865 testing running Tor servers in other Tor networks) without
18866 publishing your descriptor to the primary dirservers.
18869 Changes in version 0.1.0.3-rc - 2005-04-08
18870 o Improvements on 0.1.0.2-rc:
18871 - Client now retries when streams end early for 'hibernating' or
18872 'resource limit' reasons, rather than failing them.
18873 - More automated handling for dirserver operators:
18874 - Automatically approve nodes running 0.1.0.2-rc or later,
18875 now that the the reachability detection stuff is working.
18876 - Now we allow two unverified servers with the same nickname
18877 but different keys. But if a nickname is verified, only that
18878 nickname+key are allowed.
18879 - If you're an authdirserver connecting to an address:port,
18880 and it's not the OR you were expecting, forget about that
18881 descriptor. If he *was* the one you were expecting, then forget
18882 about all other descriptors for that address:port.
18883 - Allow servers to publish descriptors from 12 hours in the future.
18884 Corollary: only whine about clock skew from the dirserver if
18885 he's a trusted dirserver (since now even verified servers could
18886 have quite wrong clocks).
18887 - Adjust maximum skew and age for rendezvous descriptors: let skew
18888 be 48 hours rather than 90 minutes.
18889 - Efficiency improvements:
18890 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
18891 it much faster to look up a circuit for each relay cell.
18892 - Remove most calls to assert_all_pending_dns_resolves_ok(),
18893 since they're eating our cpu on exit nodes.
18894 - Stop wasting time doing a case insensitive comparison for every
18895 dns name every time we do any lookup. Canonicalize the names to
18896 lowercase and be done with it.
18897 - Start sending 'truncated' cells back rather than destroy cells,
18898 if the circuit closes in front of you. This means we won't have
18899 to abandon partially built circuits.
18900 - Only warn once per nickname from add_nickname_list_to_smartlist
18901 per failure, so an entrynode or exitnode choice that's down won't
18903 - Put a note in the torrc about abuse potential with the default
18905 - Revise control spec and implementation to allow all log messages to
18906 be sent to controller with their severities intact (suggested by
18907 Matt Edman). Update TorControl to handle new log event types.
18908 - Provide better explanation messages when controller's POSTDESCRIPTOR
18910 - Stop putting nodename in the Platform string in server descriptors.
18911 It doesn't actually help, and it is confusing/upsetting some people.
18913 o Bugfixes on 0.1.0.2-rc:
18914 - We were printing the host mask wrong in exit policies in server
18915 descriptors. This isn't a critical bug though, since we were still
18916 obeying the exit policy internally.
18917 - Fix Tor when compiled with libevent but without pthreads: move
18918 connection_unregister() from _connection_free() to
18920 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
18921 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
18922 when we look through the connection array, we'll find any of the
18923 cpu/dnsworkers. This is no good.
18925 o Bugfixes on 0.0.9.8:
18926 - Fix possible bug on threading platforms (e.g. win32) which was
18927 leaking a file descriptor whenever a cpuworker or dnsworker died.
18928 - When using preferred entry or exit nodes, ignore whether the
18929 circuit wants uptime or capacity. They asked for the nodes, they
18931 - chdir() to your datadirectory at the *end* of the daemonize process,
18932 not the beginning. This was a problem because the first time you
18933 run tor, if your datadir isn't there, and you have runasdaemon set
18934 to 1, it will try to chdir to it before it tries to create it. Oops.
18935 - Handle changed router status correctly when dirserver reloads
18936 fingerprint file. We used to be dropping all unverified descriptors
18937 right then. The bug was hidden because we would immediately
18938 fetch a directory from another dirserver, which would include the
18939 descriptors we just dropped.
18940 - When we're connecting to an OR and he's got a different nickname/key
18941 than we were expecting, only complain loudly if we're an OP or a
18942 dirserver. Complaining loudly to the OR admins just confuses them.
18943 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
18944 artificially capped at 500kB.
18947 Changes in version 0.0.9.8 - 2005-04-07
18948 o Bugfixes on 0.0.9.x:
18949 - We have a bug that I haven't found yet. Sometimes, very rarely,
18950 cpuworkers get stuck in the 'busy' state, even though the cpuworker
18951 thinks of itself as idle. This meant that no new circuits ever got
18952 established. Here's a workaround to kill any cpuworker that's been
18953 busy for more than 100 seconds.
18956 Changes in version 0.1.0.2-rc - 2005-04-01
18957 o Bugfixes on 0.1.0.1-rc:
18958 - Fixes on reachability detection:
18959 - Don't check for reachability while hibernating.
18960 - If ORPort is reachable but DirPort isn't, still publish the
18961 descriptor, but zero out DirPort until it's found reachable.
18962 - When building testing circs for ORPort testing, use only
18963 high-bandwidth nodes, so fewer circuits fail.
18964 - Complain about unreachable ORPort separately from unreachable
18965 DirPort, so the user knows what's going on.
18966 - Make sure we only conclude ORPort reachability if we didn't
18967 initiate the conn. Otherwise we could falsely conclude that
18968 we're reachable just because we connected to the guy earlier
18969 and he used that same pipe to extend to us.
18970 - Authdirservers shouldn't do ORPort reachability detection,
18971 since they're in clique mode, so it will be rare to find a
18972 server not already connected to them.
18973 - When building testing circuits, always pick middle hops running
18974 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
18975 bug. (This is a kludge; it will go away when 0.0.9.x becomes
18977 - When we decide we're reachable, actually publish our descriptor
18979 - Fix bug in redirectstream in the controller.
18980 - Fix the state descriptor strings so logs don't claim edge streams
18981 are in a different state than they actually are.
18982 - Use recent libevent features when possible (this only really affects
18983 win32 and osx right now, because the new libevent with these
18984 features hasn't been released yet). Add code to suppress spurious
18986 - Prevent possible segfault in connection_close_unattached_ap().
18987 - Fix newlines on torrc in win32.
18988 - Improve error msgs when tor-resolve fails.
18990 o Improvements on 0.0.9.x:
18991 - New experimental script tor/contrib/ExerciseServer.py (needs more
18992 work) that uses the controller interface to build circuits and
18993 fetch pages over them. This will help us bootstrap servers that
18994 have lots of capacity but haven't noticed it yet.
18995 - New experimental script tor/contrib/PathDemo.py (needs more work)
18996 that uses the controller interface to let you choose whole paths
18998 "<hostname>.<path,separated by dots>.<length of path>.path"
18999 - When we've connected to an OR and handshaked but didn't like
19000 the result, we were closing the conn without sending destroy
19001 cells back for pending circuits. Now send those destroys.
19004 Changes in version 0.0.9.7 - 2005-04-01
19005 o Bugfixes on 0.0.9.x:
19006 - Fix another race crash bug (thanks to Glenn Fink for reporting).
19007 - Compare identity to identity, not to nickname, when extending to
19008 a router not already in the directory. This was preventing us from
19009 extending to unknown routers. Oops.
19010 - Make sure to create OS X Tor user in <500 range, so we aren't
19011 creating actual system users.
19012 - Note where connection-that-hasn't-sent-end was marked, and fix
19013 a few really loud instances of this harmless bug (it's fixed more
19017 Changes in version 0.1.0.1-rc - 2005-03-28
19019 - Add reachability testing. Your Tor server will automatically try
19020 to see if its ORPort and DirPort are reachable from the outside,
19021 and it won't upload its descriptor until it decides they are.
19022 - Handle unavailable hidden services better. Handle slow or busy
19023 hidden services better.
19024 - Add support for CONNECTing through https proxies, with "HttpsProxy"
19026 - New exit policy: accept most low-numbered ports, rather than
19027 rejecting most low-numbered ports.
19028 - More Tor controller support (still experimental). See
19029 http://tor.eff.org/doc/control-spec.txt for all the new features,
19030 including signals to emulate unix signals from any platform;
19031 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
19032 closestream; closecircuit; etc.
19033 - Make nt services work and start on startup on win32 (based on
19034 patch by Matt Edman).
19035 - Add a new AddressMap config directive to rewrite incoming socks
19036 addresses. This lets you, for example, declare an implicit
19037 required exit node for certain sites.
19038 - Add a new TrackHostExits config directive to trigger addressmaps
19039 for certain incoming socks addresses -- for sites that break when
19040 your exit keeps changing (based on patch by Mike Perry).
19041 - Redo the client-side dns cache so it's just an addressmap too.
19042 - Notice when our IP changes, and reset stats/uptime/reachability.
19043 - When an application is using socks5, give him the whole variety of
19044 potential socks5 responses (connect refused, host unreachable, etc),
19045 rather than just "success" or "failure".
19046 - A more sane version numbering system. See
19047 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
19048 - New contributed script "exitlist": a simple python script to
19049 parse directories and find Tor nodes that exit to listed
19051 - New contributed script "privoxy-tor-toggle" to toggle whether
19052 Privoxy uses Tor. Seems to be configured for Debian by default.
19053 - Report HTTP reasons to client when getting a response from directory
19054 servers -- so you can actually know what went wrong.
19055 - New config option MaxAdvertisedBandwidth which lets you advertise
19056 a low bandwidthrate (to not attract as many circuits) while still
19057 allowing a higher bandwidthrate in reality.
19059 o Robustness/stability fixes:
19060 - Make Tor use Niels Provos's libevent instead of its current
19061 poll-but-sometimes-select mess. This will let us use faster async
19062 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
19064 - pthread support now too. This was forced because when we forked,
19065 we ended up wasting a lot of duplicate ram over time. Also switch
19066 to foo_r versions of some library calls to allow reentry and
19068 - Better handling for heterogeneous / unreliable nodes:
19069 - Annotate circuits w/ whether they aim to contain high uptime nodes
19070 and/or high capacity nodes. When building circuits, choose
19072 - This means that every single node in an intro rend circuit,
19073 not just the last one, will have a minimum uptime.
19074 - New config option LongLivedPorts to indicate application streams
19075 that will want high uptime circuits.
19076 - Servers reset uptime when a dir fetch entirely fails. This
19077 hopefully reflects stability of the server's network connectivity.
19078 - If somebody starts his tor server in Jan 2004 and then fixes his
19079 clock, don't make his published uptime be a year.
19080 - Reset published uptime when you wake up from hibernation.
19081 - Introduce a notion of 'internal' circs, which are chosen without
19082 regard to the exit policy of the last hop. Intro and rendezvous
19083 circs must be internal circs, to avoid leaking information. Resolve
19084 and connect streams can use internal circs if they want.
19085 - New circuit pooling algorithm: make sure to have enough circs around
19086 to satisfy any predicted ports, and also make sure to have 2 internal
19087 circs around if we've required internal circs lately (and with high
19088 uptime if we've seen that lately too).
19089 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
19090 which describes how often we retry making new circuits if current
19091 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
19092 how long we're willing to make use of an already-dirty circuit.
19093 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
19094 circ as necessary, if there are any completed ones lying around
19095 when we try to launch one.
19096 - Make hidden services try to establish a rendezvous for 30 seconds,
19097 rather than for n (where n=3) attempts to build a circuit.
19098 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
19099 "ShutdownWaitLength".
19100 - Try to be more zealous about calling connection_edge_end when
19101 things go bad with edge conns in connection.c.
19102 - Revise tor-spec to add more/better stream end reasons.
19103 - Revise all calls to connection_edge_end to avoid sending "misc",
19104 and to take errno into account where possible.
19107 - Fix a race condition that can trigger an assert, when we have a
19108 pending create cell and an OR connection fails right then.
19109 - Fix several double-mark-for-close bugs, e.g. where we were finding
19110 a conn for a cell even if that conn is already marked for close.
19111 - Make sequence of log messages when starting on win32 with no config
19112 file more reasonable.
19113 - When choosing an exit node for a new non-internal circ, don't take
19114 into account whether it'll be useful for any pending x.onion
19115 addresses -- it won't.
19116 - Turn addr_policy_compare from a tristate to a quadstate; this should
19117 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
19118 for google.com" problem.
19119 - Make "platform" string in descriptor more accurate for Win32 servers,
19120 so it's not just "unknown platform".
19121 - Fix an edge case in parsing config options (thanks weasel).
19122 If they say "--" on the commandline, it's not an option.
19123 - Reject odd-looking addresses at the client (e.g. addresses that
19124 contain a colon), rather than having the server drop them because
19126 - tor-resolve requests were ignoring .exit if there was a working circuit
19127 they could use instead.
19128 - REUSEADDR on normal platforms means you can rebind to the port
19129 right after somebody else has let it go. But REUSEADDR on win32
19130 means to let you bind to the port _even when somebody else
19131 already has it bound_! So, don't do that on Win32.
19132 - Change version parsing logic: a version is "obsolete" if it is not
19133 recommended and (1) there is a newer recommended version in the
19134 same series, or (2) there are no recommended versions in the same
19135 series, but there are some recommended versions in a newer series.
19136 A version is "new" if it is newer than any recommended version in
19138 - Stop most cases of hanging up on a socks connection without sending
19142 - Require BandwidthRate to be at least 20kB/s for servers.
19143 - When a dirserver causes you to give a warn, mention which dirserver
19145 - New config option DirAllowPrivateAddresses for authdirservers.
19146 Now by default they refuse router descriptors that have non-IP or
19147 private-IP addresses.
19148 - Stop publishing socksport in the directory, since it's not
19149 actually meant to be public. For compatibility, publish a 0 there
19151 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
19152 smart" value, that is low for servers and high for clients.
19153 - If our clock jumps forward by 100 seconds or more, assume something
19154 has gone wrong with our network and abandon all not-yet-used circs.
19155 - Warn when exit policy implicitly allows local addresses.
19156 - If we get an incredibly skewed timestamp from a dirserver mirror
19157 that isn't a verified OR, don't warn -- it's probably him that's
19159 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
19160 cookies to disk and doesn't log each web request to disk. (Thanks
19161 to Brett Carrington for pointing this out.)
19162 - When a client asks us for a dir mirror and we don't have one,
19163 launch an attempt to get a fresh one.
19164 - If we're hibernating and we get a SIGINT, exit immediately.
19165 - Add --with-dmalloc ./configure option, to track memory leaks.
19166 - And try to free all memory on closing, so we can detect what
19168 - Cache local dns resolves correctly even when they're .exit
19170 - Give a better warning when some other server advertises an
19171 ORPort that is actually an apache running ssl.
19172 - Add "opt hibernating 1" to server descriptor to make it clearer
19173 whether the server is hibernating.
19176 Changes in version 0.0.9.6 - 2005-03-24
19177 o Bugfixes on 0.0.9.x (crashes and asserts):
19178 - Add new end stream reasons to maintainance branch. Fix bug where
19179 reason (8) could trigger an assert. Prevent bug from recurring.
19180 - Apparently win32 stat wants paths to not end with a slash.
19181 - Fix assert triggers in assert_cpath_layer_ok(), where we were
19182 blowing away the circuit that conn->cpath_layer points to, then
19183 checking to see if the circ is well-formed. Backport check to make
19184 sure we dont use the cpath on a closed connection.
19185 - Prevent circuit_resume_edge_reading_helper() from trying to package
19186 inbufs for marked-for-close streams.
19187 - Don't crash on hup if your options->address has become unresolvable.
19188 - Some systems (like OS X) sometimes accept() a connection and tell
19189 you the remote host is 0.0.0.0:0. If this happens, due to some
19190 other mis-features, we get confused; so refuse the conn for now.
19192 o Bugfixes on 0.0.9.x (other):
19193 - Fix harmless but scary "Unrecognized content encoding" warn message.
19194 - Add new stream error reason: TORPROTOCOL reason means "you are not
19195 speaking a version of Tor I understand; say bye-bye to your stream."
19196 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
19197 into the future, now that we are more tolerant of skew. This
19198 resolves a bug where a Tor server would refuse to cache a directory
19199 because all the directories it gets are too far in the future;
19200 yet the Tor server never logs any complaints about clock skew.
19201 - Mac packaging magic: make man pages useable, and do not overwrite
19202 existing torrc files.
19203 - Make OS X log happily to /var/log/tor/tor.log
19206 Changes in version 0.0.9.5 - 2005-02-22
19207 o Bugfixes on 0.0.9.x:
19208 - Fix an assert race at exit nodes when resolve requests fail.
19209 - Stop picking unverified dir mirrors--it only leads to misery.
19210 - Patch from Matt Edman to make NT services work better. Service
19211 support is still not compiled into the executable by default.
19212 - Patch from Dmitri Bely so the Tor service runs better under
19213 the win32 SYSTEM account.
19214 - Make tor-resolve actually work (?) on Win32.
19215 - Fix a sign bug when getrlimit claims to have 4+ billion
19216 file descriptors available.
19217 - Stop refusing to start when bandwidthburst == bandwidthrate.
19218 - When create cells have been on the onion queue more than five
19219 seconds, just send back a destroy and take them off the list.
19222 Changes in version 0.0.9.4 - 2005-02-03
19223 o Bugfixes on 0.0.9:
19224 - Fix an assert bug that took down most of our servers: when
19225 a server claims to have 1 GB of bandwidthburst, don't
19227 - Don't crash as badly if we have spawned the max allowed number
19228 of dnsworkers, or we're out of file descriptors.
19229 - Block more file-sharing ports in the default exit policy.
19230 - MaxConn is now automatically set to the hard limit of max
19231 file descriptors we're allowed (ulimit -n), minus a few for
19233 - Give a clearer message when servers need to raise their
19234 ulimit -n when they start running out of file descriptors.
19235 - SGI Compatibility patches from Jan Schaumann.
19236 - Tolerate a corrupt cached directory better.
19237 - When a dirserver hasn't approved your server, list which one.
19238 - Go into soft hibernation after 95% of the bandwidth is used,
19239 not 99%. This is especially important for daily hibernators who
19240 have a small accounting max. Hopefully it will result in fewer
19241 cut connections when the hard hibernation starts.
19242 - Load-balance better when using servers that claim more than
19243 800kB/s of capacity.
19244 - Make NT services work (experimental, only used if compiled in).
19247 Changes in version 0.0.9.3 - 2005-01-21
19248 o Bugfixes on 0.0.9:
19249 - Backport the cpu use fixes from main branch, so busy servers won't
19250 need as much processor time.
19251 - Work better when we go offline and then come back, or when we
19252 run Tor at boot before the network is up. We do this by
19253 optimistically trying to fetch a new directory whenever an
19254 application request comes in and we think we're offline -- the
19255 human is hopefully a good measure of when the network is back.
19256 - Backport some minimal hidserv bugfixes: keep rend circuits open as
19257 long as you keep using them; actually publish hidserv descriptors
19258 shortly after they change, rather than waiting 20-40 minutes.
19259 - Enable Mac startup script by default.
19260 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
19261 - When you update AllowUnverifiedNodes or FirewallPorts via the
19262 controller's setconf feature, we were always appending, never
19264 - When you update HiddenServiceDir via setconf, it was screwing up
19265 the order of reading the lines, making it fail.
19266 - Do not rewrite a cached directory back to the cache; otherwise we
19267 will think it is recent and not fetch a newer one on startup.
19268 - Workaround for webservers that lie about Content-Encoding: Tor
19269 now tries to autodetect compressed directories and compression
19270 itself. This lets us Proxypass dir fetches through apache.
19273 Changes in version 0.0.9.2 - 2005-01-04
19274 o Bugfixes on 0.0.9 (crashes and asserts):
19275 - Fix an assert on startup when the disk is full and you're logging
19277 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
19278 style address, then we'd crash.
19279 - Fix an assert trigger when the running-routers string we get from
19280 a dirserver is broken.
19281 - Make worker threads start and run on win32. Now win32 servers
19283 - Bandaid (not actually fix, but now it doesn't crash) an assert
19284 where the dns worker dies mysteriously and the main Tor process
19285 doesn't remember anything about the address it was resolving.
19287 o Bugfixes on 0.0.9 (Win32):
19288 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
19289 name out of the warning/assert messages.
19290 - Fix a superficial "unhandled error on read" bug on win32.
19291 - The win32 installer no longer requires a click-through for our
19292 license, since our Free Software license grants rights but does not
19294 - Win32: When connecting to a dirserver fails, try another one
19295 immediately. (This was already working for non-win32 Tors.)
19296 - Stop trying to parse $HOME on win32 when hunting for default
19298 - Make tor-resolve.c work on win32 by calling network_init().
19300 o Bugfixes on 0.0.9 (other):
19301 - Make 0.0.9.x build on Solaris again.
19302 - Due to a fencepost error, we were blowing away the \n when reporting
19303 confvalue items in the controller. So asking for multiple config
19304 values at once couldn't work.
19305 - When listing circuits that are pending on an opening OR connection,
19306 if we're an OR we were listing circuits that *end* at us as
19307 being pending on every listener, dns/cpu worker, etc. Stop that.
19308 - Dirservers were failing to create 'running-routers' or 'directory'
19309 strings if we had more than some threshold of routers. Fix them so
19310 they can handle any number of routers.
19311 - Fix a superficial "Duplicate mark for close" bug.
19312 - Stop checking for clock skew for OR connections, even for servers.
19313 - Fix a fencepost error that was chopping off the last letter of any
19314 nickname that is the maximum allowed nickname length.
19315 - Update URLs in log messages so they point to the new website.
19316 - Fix a potential problem in mangling server private keys while
19317 writing to disk (not triggered yet, as far as we know).
19318 - Include the licenses for other free software we include in Tor,
19319 now that we're shipping binary distributions more regularly.
19322 Changes in version 0.0.9.1 - 2004-12-15
19323 o Bugfixes on 0.0.9:
19324 - Make hibernation actually work.
19325 - Make HashedControlPassword config option work.
19326 - When we're reporting event circuit status to a controller,
19327 don't use the stream status code.
19330 Changes in version 0.0.9 - 2004-12-12
19332 - Clean up manpage and torrc.sample file.
19333 - Clean up severities and text of log warnings.
19335 - Make servers trigger an assert when they enter hibernation.
19338 Changes in version 0.0.9rc7 - 2004-12-08
19339 o Bugfixes on 0.0.9rc:
19340 - Fix a stack-trashing crash when an exit node begins hibernating.
19341 - Avoid looking at unallocated memory while considering which
19342 ports we need to build circuits to cover.
19343 - Stop a sigpipe: when an 'end' cell races with eof from the app,
19344 we shouldn't hold-open-until-flush if the eof arrived first.
19345 - Fix a bug with init_cookie_authentication() in the controller.
19346 - When recommending new-format log lines, if the upper bound is
19347 LOG_ERR, leave it implicit.
19349 o Bugfixes on 0.0.8.1:
19350 - Fix a whole slew of memory leaks.
19351 - Fix isspace() and friends so they still make Solaris happy
19352 but also so they don't trigger asserts on win32.
19353 - Fix parse_iso_time on platforms without strptime (eg win32).
19354 - win32: tolerate extra "readable" events better.
19355 - win32: when being multithreaded, leave parent fdarray open.
19356 - Make unit tests work on win32.
19359 Changes in version 0.0.9rc6 - 2004-12-06
19360 o Bugfixes on 0.0.9pre:
19361 - Clean up some more integer underflow opportunities (not exploitable
19363 - While hibernating, hup should not regrow our listeners.
19364 - Send an end to the streams we close when we hibernate, rather
19365 than just chopping them off.
19366 - React to eof immediately on non-open edge connections.
19368 o Bugfixes on 0.0.8.1:
19369 - Calculate timeout for waiting for a connected cell from the time
19370 we sent the begin cell, not from the time the stream started. If
19371 it took a long time to establish the circuit, we would time out
19372 right after sending the begin cell.
19373 - Fix router_compare_addr_to_addr_policy: it was not treating a port
19374 of * as always matching, so we were picking reject *:* nodes as
19375 exit nodes too. Oops.
19378 - New circuit building strategy: keep a list of ports that we've
19379 used in the past 6 hours, and always try to have 2 circuits open
19380 or on the way that will handle each such port. Seed us with port
19381 80 so web users won't complain that Tor is "slow to start up".
19382 - Make kill -USR1 dump more useful stats about circuits.
19383 - When warning about retrying or giving up, print the address, so
19384 the user knows which one it's talking about.
19385 - If you haven't used a clean circuit in an hour, throw it away,
19386 just to be on the safe side. (This means after 6 hours a totally
19387 unused Tor client will have no circuits open.)
19390 Changes in version 0.0.9rc5 - 2004-12-01
19391 o Bugfixes on 0.0.8.1:
19392 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
19393 - Let resolve conns retry/expire also, rather than sticking around
19395 - If we are using select, make sure we stay within FD_SETSIZE.
19397 o Bugfixes on 0.0.9pre:
19398 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
19399 but doesn't seem to be currently; thanks to Ilja van Sprundel for
19401 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
19402 instead. Impose minima and maxima for all *Period options; impose
19403 even tighter maxima for fetching if we are a caching dirserver.
19404 Clip rather than rejecting.
19405 - Fetch cached running-routers from servers that serve it (that is,
19406 authdirservers and servers running 0.0.9rc5-cvs or later.)
19409 - Accept *:706 (silc) in default exit policy.
19410 - Implement new versioning format for post 0.1.
19411 - Support "foo.nickname.exit" addresses, to let Alice request the
19412 address "foo" as viewed by exit node "nickname". Based on a patch
19414 - Make tor --version --version dump the cvs Id of every file.
19417 Changes in version 0.0.9rc4 - 2004-11-28
19418 o Bugfixes on 0.0.8.1:
19419 - Make windows sockets actually non-blocking (oops), and handle
19420 win32 socket errors better.
19422 o Bugfixes on 0.0.9rc1:
19423 - Actually catch the -USR2 signal.
19426 Changes in version 0.0.9rc3 - 2004-11-25
19427 o Bugfixes on 0.0.8.1:
19428 - Flush the log file descriptor after we print "Tor opening log file",
19429 so we don't see those messages days later.
19431 o Bugfixes on 0.0.9rc1:
19432 - Make tor-resolve work again.
19433 - Avoid infinite loop in tor-resolve if tor hangs up on it.
19434 - Fix an assert trigger for clients/servers handling resolves.
19437 Changes in version 0.0.9rc2 - 2004-11-24
19438 o Bugfixes on 0.0.9rc1:
19439 - I broke socks5 support while fixing the eof bug.
19440 - Allow unitless bandwidths and intervals; they default to bytes
19442 - New servers don't start out hibernating; they are active until
19443 they run out of bytes, so they have a better estimate of how
19444 long it takes, and so their operators can know they're working.
19447 Changes in version 0.0.9rc1 - 2004-11-23
19448 o Bugfixes on 0.0.8.1:
19449 - Finally fix a bug that's been plaguing us for a year:
19450 With high load, circuit package window was reaching 0. Whenever
19451 we got a circuit-level sendme, we were reading a lot on each
19452 socket, but only writing out a bit. So we would eventually reach
19453 eof. This would be noticed and acted on even when there were still
19454 bytes sitting in the inbuf.
19455 - When poll() is interrupted, we shouldn't believe the revents values.
19457 o Bugfixes on 0.0.9pre6:
19458 - Fix hibernate bug that caused pre6 to be broken.
19459 - Don't keep rephist info for routers that haven't had activity for
19460 24 hours. (This matters now that clients have keys, since we track
19462 - Never call close_temp_logs while validating log options.
19463 - Fix backslash-escaping on tor.sh.in and torctl.in.
19466 - Implement weekly/monthly/daily accounting: now you specify your
19467 hibernation properties by
19468 AccountingMax N bytes|KB|MB|GB|TB
19469 AccountingStart day|week|month [day] HH:MM
19470 Defaults to "month 1 0:00".
19471 - Let bandwidth and interval config options be specified as 5 bytes,
19472 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
19473 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
19474 get back to normal.)
19475 - If your requested entry or exit node has advertised bandwidth 0,
19477 - Be more greedy about filling up relay cells -- we try reading again
19478 once we've processed the stuff we read, in case enough has arrived
19479 to fill the last cell completely.
19480 - Apply NT service patch from Osamu Fujino. Still needs more work.
19483 Changes in version 0.0.9pre6 - 2004-11-15
19484 o Bugfixes on 0.0.8.1:
19485 - Fix assert failure on malformed socks4a requests.
19486 - Use identity comparison, not nickname comparison, to choose which
19487 half of circuit-ID-space each side gets to use. This is needed
19488 because sometimes we think of a router as a nickname, and sometimes
19489 as a hex ID, and we can't predict what the other side will do.
19490 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
19491 write() call will fail and we handle it there.
19492 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
19493 and smartlist_len, which are two major profiling offenders.
19495 o Bugfixes on 0.0.9pre5:
19496 - Fix a bug in read_all that was corrupting config files on windows.
19497 - When we're raising the max number of open file descriptors to
19498 'unlimited', don't log that we just raised it to '-1'.
19499 - Include event code with events, as required by control-spec.txt.
19500 - Don't give a fingerprint when clients do --list-fingerprint:
19501 it's misleading, because it will never be the same again.
19502 - Stop using strlcpy in tor_strndup, since it was slowing us
19504 - Remove warn on startup about missing cached-directory file.
19505 - Make kill -USR1 work again.
19506 - Hibernate if we start tor during the "wait for wakeup-time" phase
19507 of an accounting interval. Log our hibernation plans better.
19508 - Authoritative dirservers now also cache their directory, so they
19509 have it on start-up.
19512 - Fetch running-routers; cache running-routers; compress
19513 running-routers; serve compressed running-routers.z
19514 - Add NSI installer script contributed by J Doe.
19515 - Commit VC6 and VC7 workspace/project files.
19516 - Commit a tor.spec for making RPM files, with help from jbash.
19517 - Add contrib/torctl.in contributed by Glenn Fink.
19518 - Implement the control-spec's SAVECONF command, to write your
19519 configuration to torrc.
19520 - Get cookie authentication for the controller closer to working.
19521 - Include control-spec.txt in the tarball.
19522 - When set_conf changes our server descriptor, upload a new copy.
19523 But don't upload it too often if there are frequent changes.
19524 - Document authentication config in man page, and document signals
19526 - Clean up confusing parts of man page and torrc.sample.
19527 - Make expand_filename handle ~ and ~username.
19528 - Use autoconf to enable largefile support where necessary. Use
19529 ftello where available, since ftell can fail at 2GB.
19530 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
19531 log more informatively.
19532 - Give a slightly more useful output for "tor -h".
19533 - Refuse application socks connections to port 0.
19534 - Check clock skew for verified servers, but allow unverified
19535 servers and clients to have any clock skew.
19536 - Break DirFetchPostPeriod into:
19537 - DirFetchPeriod for fetching full directory,
19538 - StatusFetchPeriod for fetching running-routers,
19539 - DirPostPeriod for posting server descriptor,
19540 - RendPostPeriod for posting hidden service descriptors.
19541 - Make sure the hidden service descriptors are at a random offset
19542 from each other, to hinder linkability.
19545 Changes in version 0.0.9pre5 - 2004-11-09
19546 o Bugfixes on 0.0.9pre4:
19547 - Fix a seg fault in unit tests (doesn't affect main program).
19548 - Fix an assert bug where a hidden service provider would fail if
19549 the first hop of his rendezvous circuit was down.
19550 - Hidden service operators now correctly handle version 1 style
19551 INTRODUCE1 cells (nobody generates them still, so not a critical
19553 - If do_hup fails, actually notice.
19554 - Handle more errnos from accept() without closing the listener.
19555 Some OpenBSD machines were closing their listeners because
19556 they ran out of file descriptors.
19557 - Send resolve cells to exit routers that are running a new
19558 enough version of the resolve code to work right.
19559 - Better handling of winsock includes on non-MSV win32 compilers.
19560 - Some people had wrapped their tor client/server in a script
19561 that would restart it whenever it died. This did not play well
19562 with our "shut down if your version is obsolete" code. Now people
19563 don't fetch a new directory if their local cached version is
19565 - Make our autogen.sh work on ksh as well as bash.
19568 - Hibernation: New config option "AccountingMaxKB" lets you
19569 set how many KBytes per month you want to allow your server to
19570 consume. Rather than spreading those bytes out evenly over the
19571 month, we instead hibernate for some of the month and pop up
19572 at a deterministic time, work until the bytes are consumed, then
19573 hibernate again. Config option "MonthlyAccountingStart" lets you
19574 specify which day of the month your billing cycle starts on.
19575 - Control interface: a separate program can now talk to your
19576 client/server over a socket, and get/set config options, receive
19577 notifications of circuits and streams starting/finishing/dying,
19578 bandwidth used, etc. The next step is to get some GUIs working.
19579 Let us know if you want to help out. See doc/control-spec.txt .
19580 - Ship a contrib/tor-control.py as an example script to interact
19581 with the control port.
19582 - "tor --hash-password zzyxz" will output a salted password for
19583 use in authenticating to the control interface.
19584 - New log format in config:
19585 "Log minsev[-maxsev] stdout|stderr|syslog" or
19586 "Log minsev[-maxsev] file /var/foo"
19589 - DirPolicy config option, to let people reject incoming addresses
19590 from their dirserver.
19591 - "tor --list-fingerprint" will list your identity key fingerprint
19593 - Add "pass" target for RedirectExit, to make it easier to break
19594 out of a sequence of RedirectExit rules.
19595 - Clients now generate a TLS cert too, in preparation for having
19596 them act more like real nodes.
19597 - Ship src/win32/ in the tarball, so people can use it to build.
19598 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
19600 - New "router-status" line in directory, to better bind each verified
19601 nickname to its identity key.
19602 - Deprecate unofficial config option abbreviations, and abbreviations
19603 not on the command line.
19604 - Add a pure-C tor-resolve implementation.
19605 - Use getrlimit and friends to ensure we can reach MaxConn (currently
19606 1024) file descriptors.
19608 o Code security improvements, inspired by Ilja:
19609 - Replace sprintf with snprintf. (I think they were all safe, but
19611 - Replace strcpy/strncpy with strlcpy in more places.
19612 - Avoid strcat; use snprintf or strlcat instead.
19613 - snprintf wrapper with consistent (though not C99) overflow behavior.
19616 Changes in version 0.0.9pre4 - 2004-10-17
19617 o Bugfixes on 0.0.9pre3:
19618 - If the server doesn't specify an exit policy, use the real default
19619 exit policy, not reject *:*.
19620 - Ignore fascistfirewall when uploading/downloading hidden service
19621 descriptors, since we go through Tor for those; and when using
19622 an HttpProxy, since we assume it can reach them all.
19623 - When looking for an authoritative dirserver, use only the ones
19624 configured at boot. Don't bother looking in the directory.
19625 - The rest of the fix for get_default_conf_file() on older win32.
19626 - Make 'Routerfile' config option obsolete.
19629 - New 'MyFamily nick1,...' config option for a server to
19630 specify other servers that shouldn't be used in the same circuit
19631 with it. Only believed if nick1 also specifies us.
19632 - New 'NodeFamily nick1,nick2,...' config option for a client to
19633 specify nodes that it doesn't want to use in the same circuit.
19634 - New 'Redirectexit pattern address:port' config option for a
19635 server to redirect exit connections, e.g. to a local squid.
19638 Changes in version 0.0.9pre3 - 2004-10-13
19639 o Bugfixes on 0.0.8.1:
19640 - Better torrc example lines for dirbindaddress and orbindaddress.
19641 - Improved bounds checking on parsed ints (e.g. config options and
19642 the ones we find in directories.)
19643 - Better handling of size_t vs int, so we're more robust on 64
19645 - Fix the rest of the bug where a newly started OR would appear
19646 as unverified even after we've added his fingerprint and hupped
19648 - Fix a bug from 0.0.7: when read() failed on a stream, we would
19649 close it without sending back an end. So 'connection refused'
19650 would simply be ignored and the user would get no response.
19652 o Bugfixes on 0.0.9pre2:
19653 - Serving the cached-on-disk directory to people is bad. We now
19654 provide no directory until we've fetched a fresh one.
19655 - Workaround for bug on windows where cached-directories get crlf
19657 - Make get_default_conf_file() work on older windows too.
19658 - If we write a *:* exit policy line in the descriptor, don't write
19659 any more exit policy lines.
19662 - Use only 0.0.9pre1 and later servers for resolve cells.
19663 - Make the dirservers file obsolete.
19664 - Include a dir-signing-key token in directories to tell the
19665 parsing entity which key is being used to sign.
19666 - Remove the built-in bulky default dirservers string.
19667 - New config option "Dirserver %s:%d [fingerprint]", which can be
19668 repeated as many times as needed. If no dirservers specified,
19669 default to moria1,moria2,tor26.
19670 - Make moria2 advertise a dirport of 80, so people behind firewalls
19671 will be able to get a directory.
19672 - Http proxy support
19673 - Dirservers translate requests for http://%s:%d/x to /x
19674 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
19675 be routed through this host.
19676 - Clients ask for /tor/x rather than /x for new enough dirservers.
19677 This way we can one day coexist peacefully with apache.
19678 - Clients specify a "Host: %s%d" http header, to be compatible
19679 with more proxies, and so running squid on an exit node can work.
19682 Changes in version 0.0.8.1 - 2004-10-13
19684 - Fix a seg fault that can be triggered remotely for Tor
19685 clients/servers with an open dirport.
19686 - Fix a rare assert trigger, where routerinfos for entries in
19687 our cpath would expire while we're building the path.
19688 - Fix a bug in OutboundBindAddress so it (hopefully) works.
19689 - Fix a rare seg fault for people running hidden services on
19690 intermittent connections.
19691 - Fix a bug in parsing opt keywords with objects.
19692 - Fix a stale pointer assert bug when a stream detaches and
19694 - Fix a string format vulnerability (probably not exploitable)
19695 in reporting stats locally.
19696 - Fix an assert trigger: sometimes launching circuits can fail
19697 immediately, e.g. because too many circuits have failed recently.
19698 - Fix a compile warning on 64 bit platforms.
19701 Changes in version 0.0.9pre2 - 2004-10-03
19703 - Make fetching a cached directory work for 64-bit platforms too.
19704 - Make zlib.h a required header, not an optional header.
19707 Changes in version 0.0.9pre1 - 2004-10-01
19709 - Stop using separate defaults for no-config-file and
19710 empty-config-file. Now you have to explicitly turn off SocksPort,
19711 if you don't want it open.
19712 - Fix a bug in OutboundBindAddress so it (hopefully) works.
19713 - Improve man page to mention more of the 0.0.8 features.
19714 - Fix a rare seg fault for people running hidden services on
19715 intermittent connections.
19716 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
19718 - Fix more dns related bugs: send back resolve_failed and end cells
19719 more reliably when the resolve fails, rather than closing the
19720 circuit and then trying to send the cell. Also attach dummy resolve
19721 connections to a circuit *before* calling dns_resolve(), to fix
19722 a bug where cached answers would never be sent in RESOLVED cells.
19723 - When we run out of disk space, or other log writing error, don't
19724 crash. Just stop logging to that log and continue.
19725 - We were starting to daemonize before we opened our logs, so if
19726 there were any problems opening logs, we would complain to stderr,
19727 which wouldn't work, and then mysteriously exit.
19728 - Fix a rare bug where sometimes a verified OR would connect to us
19729 before he'd uploaded his descriptor, which would cause us to
19730 assign conn->nickname as though he's unverified. Now we look through
19731 the fingerprint list to see if he's there.
19732 - Fix a rare assert trigger, where routerinfos for entries in
19733 our cpath would expire while we're building the path.
19736 - Clients can ask dirservers for /dir.z to get a compressed version
19737 of the directory. Only works for servers running 0.0.9, of course.
19738 - Make clients cache directories and use them to seed their router
19739 lists at startup. This means clients have a datadir again.
19740 - Configuration infrastructure support for warning on obsolete
19742 - Respond to content-encoding headers by trying to uncompress as
19744 - Reply with a deflated directory when a client asks for "dir.z".
19745 We could use allow-encodings instead, but allow-encodings isn't
19746 specified in HTTP 1.0.
19747 - Raise the max dns workers from 50 to 100.
19748 - Discourage people from setting their dirfetchpostperiod more often
19749 than once per minute.
19750 - Protect dirservers from overzealous descriptor uploading -- wait
19751 10 seconds after directory gets dirty, before regenerating.
19754 Changes in version 0.0.8 - 2004-08-25
19755 o Port it to SunOS 5.9 / Athena
19758 Changes in version 0.0.8rc2 - 2004-08-20
19759 o Make it compile on cygwin again.
19760 o When picking unverified routers, skip those with low uptime and/or
19761 low bandwidth, depending on what properties you care about.
19764 Changes in version 0.0.8rc1 - 2004-08-18
19765 o Changes from 0.0.7.3:
19767 - Fix assert triggers: if the other side returns an address 0.0.0.0,
19768 don't put it into the client dns cache.
19769 - If a begin failed due to exit policy, but we believe the IP address
19770 should have been allowed, switch that router to exitpolicy reject *:*
19771 until we get our next directory.
19773 - Clients choose nodes proportional to advertised bandwidth.
19774 - Avoid using nodes with low uptime as introduction points.
19775 - Handle servers with dynamic IP addresses: don't replace
19776 options->Address with the resolved one at startup, and
19777 detect our address right before we make a routerinfo each time.
19778 - 'FascistFirewall' option to pick dirservers and ORs on specific
19779 ports; plus 'FirewallPorts' config option to tell FascistFirewall
19780 which ports are open. (Defaults to 80,443)
19781 - Be more aggressive about trying to make circuits when the network
19782 has changed (e.g. when you unsuspend your laptop).
19783 - Check for time skew on http headers; report date in response to
19785 - If the entrynode config line has only one node, don't pick it as
19787 - Add strict{entry|exit}nodes config options. If set to 1, then
19788 we refuse to build circuits that don't include the specified entry
19790 - OutboundBindAddress config option, to bind to a specific
19791 IP address for outgoing connect()s.
19792 - End truncated log entries (e.g. directories) with "[truncated]".
19794 o Patches to 0.0.8preX:
19796 - Patches to compile and run on win32 again (maybe)?
19797 - Fix crash when looking for ~/.torrc with no $HOME set.
19798 - Fix a race bug in the unit tests.
19799 - Handle verified/unverified name collisions better when new
19800 routerinfo's arrive in a directory.
19801 - Sometimes routers were getting entered into the stats before
19802 we'd assigned their identity_digest. Oops.
19803 - Only pick and establish intro points after we've gotten a
19806 - AllowUnverifiedNodes config option to let circuits choose no-name
19807 routers in entry,middle,exit,introduction,rendezvous positions.
19808 Allow middle and rendezvous positions by default.
19809 - Add a man page for tor-resolve.
19812 Changes in version 0.0.7.3 - 2004-08-12
19813 o Stop dnsworkers from triggering an assert failure when you
19814 ask them to resolve the host "".
19817 Changes in version 0.0.8pre3 - 2004-08-09
19818 o Changes from 0.0.7.2:
19819 - Allow multiple ORs with same nickname in routerlist -- now when
19820 people give us one identity key for a nickname, then later
19821 another, we don't constantly complain until the first expires.
19822 - Remember used bandwidth (both in and out), and publish 15-minute
19823 snapshots for the past day into our descriptor.
19824 - You can now fetch $DIRURL/running-routers to get just the
19825 running-routers line, not the whole descriptor list. (But
19826 clients don't use this yet.)
19827 - When people mistakenly use Tor as an http proxy, point them
19828 at the tor-doc.html rather than the INSTALL.
19829 - Remove our mostly unused -- and broken -- hex_encode()
19830 function. Use base16_encode() instead. (Thanks to Timo Lindfors
19831 for pointing out this bug.)
19832 - Rotate onion keys every 12 hours, not every 2 hours, so we have
19833 fewer problems with people using the wrong key.
19834 - Change the default exit policy to reject the default edonkey,
19835 kazaa, gnutella ports.
19836 - Add replace_file() to util.[ch] to handle win32's rename().
19838 o Changes from 0.0.8preX:
19839 - Fix two bugs in saving onion keys to disk when rotating, so
19840 hopefully we'll get fewer people using old onion keys.
19841 - Fix an assert error that was making SocksPolicy not work.
19842 - Be willing to expire routers that have an open dirport -- it's
19843 just the authoritative dirservers we want to not forget.
19844 - Reject tor-resolve requests for .onion addresses early, so we
19845 don't build a whole rendezvous circuit and then fail.
19846 - When you're warning a server that he's unverified, don't cry
19847 wolf unpredictably.
19848 - Fix a race condition: don't try to extend onto a connection
19849 that's still handshaking.
19850 - For servers in clique mode, require the conn to be open before
19851 you'll choose it for your path.
19852 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
19853 end relay cell, etc.
19854 - Measure bandwidth capacity over the last 24 hours, not just 12
19855 - Bugfix: authoritative dirservers were making and signing a new
19856 directory for each client, rather than reusing the cached one.
19859 Changes in version 0.0.8pre2 - 2004-08-04
19860 o Changes from 0.0.7.2:
19862 - Check directory signature _before_ you decide whether you're
19863 you're running an obsolete version and should exit.
19864 - Check directory signature _before_ you parse the running-routers
19865 list to decide who's running or verified.
19866 - Bugfixes and features:
19867 - Check return value of fclose while writing to disk, so we don't
19868 end up with broken files when servers run out of disk space.
19869 - Log a warning if the user uses an unsafe socks variant, so people
19870 are more likely to learn about privoxy or socat.
19871 - Dirservers now include RFC1123-style dates in the HTTP headers,
19872 which one day we will use to better detect clock skew.
19874 o Changes from 0.0.8pre1:
19875 - Make it compile without warnings again on win32.
19876 - Log a warning if you're running an unverified server, to let you
19877 know you might want to get it verified.
19878 - Only pick a default nickname if you plan to be a server.
19881 Changes in version 0.0.8pre1 - 2004-07-23
19883 - Made our unit tests compile again on OpenBSD 3.5, and tor
19884 itself compile again on OpenBSD on a sparc64.
19885 - We were neglecting milliseconds when logging on win32, so
19886 everything appeared to happen at the beginning of each second.
19888 o Protocol changes:
19889 - 'Extend' relay cell payloads now include the digest of the
19890 intended next hop's identity key. Now we can verify that we're
19891 extending to the right router, and also extend to routers we
19892 hadn't heard of before.
19895 - Tor nodes can now act as relays (with an advertised ORPort)
19896 without being manually verified by the dirserver operators.
19897 - Uploaded descriptors of unverified routers are now accepted
19898 by the dirservers, and included in the directory.
19899 - Verified routers are listed by nickname in the running-routers
19900 list; unverified routers are listed as "$<fingerprint>".
19901 - We now use hash-of-identity-key in most places rather than
19902 nickname or addr:port, for improved security/flexibility.
19903 - To avoid Sybil attacks, paths still use only verified servers.
19904 But now we have a chance to play around with hybrid approaches.
19905 - Nodes track bandwidth usage to estimate capacity (not used yet).
19906 - ClientOnly option for nodes that never want to become servers.
19907 - Directory caching.
19908 - "AuthoritativeDir 1" option for the official dirservers.
19909 - Now other nodes (clients and servers) will cache the latest
19910 directory they've pulled down.
19911 - They can enable their DirPort to serve it to others.
19912 - Clients will pull down a directory from any node with an open
19913 DirPort, and check the signature/timestamp correctly.
19914 - Authoritative dirservers now fetch directories from other
19915 authdirservers, to stay better synced.
19916 - Running-routers list tells who's down also, along with noting
19917 if they're verified (listed by nickname) or unverified (listed
19919 - Allow dirservers to serve running-router list separately.
19920 This isn't used yet.
19921 - ORs connect-on-demand to other ORs
19922 - If you get an extend cell to an OR you're not connected to,
19923 connect, handshake, and forward the create cell.
19924 - The authoritative dirservers stay connected to everybody,
19925 and everybody stays connected to 0.0.7 servers, but otherwise
19926 clients/servers expire unused connections after 5 minutes.
19927 - When servers get a sigint, they delay 30 seconds (refusing new
19928 connections) then exit. A second sigint causes immediate exit.
19929 - File and name management:
19930 - Look for .torrc if no CONFDIR "torrc" is found.
19931 - If no datadir is defined, then choose, make, and secure ~/.tor
19933 - If torrc not found, exitpolicy reject *:*.
19934 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
19935 - If no nickname is defined, derive default from hostname.
19936 - Rename secret key files, e.g. identity.key -> secret_id_key,
19937 to discourage people from mailing their identity key to tor-ops.
19938 - Refuse to build a circuit before the directory has arrived --
19939 it won't work anyway, since you won't know the right onion keys
19941 - Try other dirservers immediately if the one you try is down. This
19942 should tolerate down dirservers better now.
19943 - Parse tor version numbers so we can do an is-newer-than check
19944 rather than an is-in-the-list check.
19945 - New socks command 'resolve', to let us shim gethostbyname()
19947 - A 'tor_resolve' script to access the socks resolve functionality.
19948 - A new socks-extensions.txt doc file to describe our
19949 interpretation and extensions to the socks protocols.
19950 - Add a ContactInfo option, which gets published in descriptor.
19951 - Publish OR uptime in descriptor (and thus in directory) too.
19952 - Write tor version at the top of each log file
19953 - New docs in the tarball:
19955 - Document that you should proxy your SSL traffic too.
19958 Changes in version 0.0.7.2 - 2004-07-07
19959 o A better fix for the 0.0.0.0 problem, that will hopefully
19960 eliminate the remaining related assertion failures.
19963 Changes in version 0.0.7.1 - 2004-07-04
19964 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
19965 since internally we use 0.0.0.0 to signify "not yet resolved".
19968 Changes in version 0.0.7 - 2004-06-07
19969 o Updated the man page to reflect the new features.
19972 Changes in version 0.0.7rc2 - 2004-06-06
19973 o Changes from 0.0.7rc1:
19974 - Make it build on Win32 again.
19975 o Changes from 0.0.6.2:
19976 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
19980 Changes in version 0.0.7rc1 - 2004-06-02
19982 - On sighup, we were adding another log without removing the first
19983 one. So log messages would get duplicated n times for n sighups.
19984 - Several cases of using a connection after we'd freed it. The
19985 problem was that connections that are pending resolve are in both
19986 the pending_resolve tree, and also the circuit's resolving_streams
19987 list. When you want to remove one, you must remove it from both.
19988 - Fix a double-mark-for-close where an end cell arrived for a
19989 resolving stream, and then the resolve failed.
19990 - Check directory signatures based on name of signer, not on whom
19991 we got the directory from. This will let us cache directories more
19994 - Crank up some of our constants to handle more users.
19997 Changes in version 0.0.7pre1 - 2004-06-02
19998 o Fixes for crashes and other obnoxious bugs:
19999 - Fix an epipe bug: sometimes when directory connections failed
20000 to connect, we would give them a chance to flush before closing
20002 - When we detached from a circuit because of resolvefailed, we
20003 would immediately try the same circuit twice more, and then
20004 give up on the resolve thinking we'd tried three different
20006 - Limit the number of intro circuits we'll attempt to build for a
20007 hidden service per 15-minute period.
20008 - Check recommended-software string *early*, before actually parsing
20009 the directory. Thus we can detect an obsolete version and exit,
20010 even if the new directory format doesn't parse.
20011 o Fixes for security bugs:
20012 - Remember which nodes are dirservers when you startup, and if a
20013 random OR enables his dirport, don't automatically assume he's
20014 a trusted dirserver.
20016 - Directory connections were asking the wrong poll socket to
20017 start writing, and not asking themselves to start writing.
20018 - When we detached from a circuit because we sent a begin but
20019 didn't get a connected, we would use it again the first time;
20020 but after that we would correctly switch to a different one.
20021 - Stop warning when the first onion decrypt attempt fails; they
20022 will sometimes legitimately fail now that we rotate keys.
20023 - Override unaligned-access-ok check when $host_cpu is ia64 or
20024 arm. Apparently they allow it but the kernel whines.
20025 - Dirservers try to reconnect periodically too, in case connections
20027 - Fix some memory leaks in directory servers.
20028 - Allow backslash in Win32 filenames.
20029 - Made Tor build complain-free on FreeBSD, hopefully without
20030 breaking other BSD builds. We'll see.
20032 - Doxygen markup on all functions and global variables.
20033 - Make directory functions update routerlist, not replace it. So
20034 now directory disagreements are not so critical a problem.
20035 - Remove the upper limit on number of descriptors in a dirserver's
20036 directory (not that we were anywhere close).
20037 - Allow multiple logfiles at different severity ranges.
20038 - Allow *BindAddress to specify ":port" rather than setting *Port
20039 separately. Allow multiple instances of each BindAddress config
20040 option, so you can bind to multiple interfaces if you want.
20041 - Allow multiple exit policy lines, which are processed in order.
20042 Now we don't need that huge line with all the commas in it.
20043 - Enable accept/reject policies on SOCKS connections, so you can bind
20044 to 0.0.0.0 but still control who can use your OP.
20047 Changes in version 0.0.6.2 - 2004-05-16
20048 o Our integrity-checking digest was checking only the most recent cell,
20049 not the previous cells like we'd thought.
20050 Thanks to Stefan Mark for finding the flaw!
20053 Changes in version 0.0.6.1 - 2004-05-06
20054 o Fix two bugs in our AES counter-mode implementation (this affected
20055 onion-level stream encryption, but not TLS-level). It turns
20056 out we were doing something much more akin to a 16-character
20057 polyalphabetic cipher. Oops.
20058 Thanks to Stefan Mark for finding the flaw!
20059 o Retire moria3 as a directory server, and add tor26 as a directory
20063 Changes in version 0.0.6 - 2004-05-02
20064 [version bump only]
20067 Changes in version 0.0.6rc4 - 2004-05-01
20068 o Update the built-in dirservers list to use the new directory format
20069 o Fix a rare seg fault: if a node offering a hidden service attempts
20070 to build a circuit to Alice's rendezvous point and fails before it
20071 reaches the last hop, it retries with a different circuit, but
20073 o Handle windows socket errors correctly.
20076 Changes in version 0.0.6rc3 - 2004-04-28
20077 o Don't expire non-general excess circuits (if we had enough
20078 circuits open, we were expiring rendezvous circuits -- even
20079 when they had a stream attached. oops.)
20080 o Fetch randomness from /dev/urandom better (not via fopen/fread)
20081 o Better debugging for tls errors
20082 o Some versions of openssl have an SSL_pending function that erroneously
20083 returns bytes when there is a non-application record pending.
20084 o Set Content-Type on the directory and hidserv descriptor.
20085 o Remove IVs from cipher code, since AES-ctr has none.
20086 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
20087 o We were using an array of length zero in a few places.
20088 o win32's gethostbyname can't resolve an IP to an IP.
20089 o win32's close can't close a socket.
20092 Changes in version 0.0.6rc2 - 2004-04-26
20093 o Fix a bug where we were closing tls connections intermittently.
20094 It turns out openssl keeps its errors around -- so if an error
20095 happens, and you don't ask about it, and then another openssl
20096 operation happens and succeeds, and you ask if there was an error,
20097 it tells you about the first error. Fun fun.
20098 o Fix a bug that's been lurking since 27 may 03 (!)
20099 When passing back a destroy cell, we would use the wrong circ id.
20100 'Mostly harmless', but still worth fixing.
20101 o Since we don't support truncateds much, don't bother sending them;
20102 just close the circ.
20103 o check for <machine/limits.h> so we build on NetBSD again (I hope).
20104 o don't crash if a conn that sent a begin has suddenly lost its circuit
20105 (this was quite rare).
20108 Changes in version 0.0.6rc1 - 2004-04-25
20109 o We now rotate link (tls context) keys and onion keys.
20110 o CREATE cells now include oaep padding, so you can tell
20111 if you decrypted them correctly.
20112 o Add bandwidthburst to server descriptor.
20113 o Directories now say which dirserver signed them.
20114 o Use a tor_assert macro that logs failed assertions too.
20117 Changes in version 0.0.6pre5 - 2004-04-18
20118 o changes from 0.0.6pre4:
20119 - make tor build on broken freebsd 5.2 installs
20120 - fix a failed assert when you try an intro point, get a nack, and try
20121 a second one and it works.
20122 - when alice uses a port that the hidden service doesn't accept,
20123 it now sends back an end cell (denied by exit policy). otherwise
20124 alice would just have to wait to time out.
20125 - fix another rare bug: when we had tried all the intro
20126 points for a hidden service, we fetched the descriptor
20127 again, but we left our introcirc thinking it had already
20128 sent an intro, so it kept waiting for a response...
20129 - bugfix: when you sleep your hidden-service laptop, as soon
20130 as it wakes up it tries to upload a service descriptor, but
20131 socketpair fails for some reason (localhost not up yet?).
20132 now we simply give up on that upload, and we'll try again later.
20133 i'd still like to find the bug though.
20134 - if an intro circ waiting for an ack dies before getting one, then
20136 - we were reusing stale service descriptors and refetching usable
20140 Changes in version 0.0.6pre4 - 2004-04-14
20141 o changes from 0.0.6pre3:
20142 - when bob fails to connect to the rendezvous point, and his
20143 circ didn't fail because of the rendezvous point itself, then
20144 he retries a couple of times
20145 - we expire introduction and rendezvous circs more thoroughly
20146 (sometimes they were hanging around forever)
20147 - we expire unattached rendezvous streams that have been around
20148 too long (they were sticking around forever).
20149 - fix a measly fencepost error that was crashing everybody with
20153 Changes in version 0.0.6pre3 - 2004-04-14
20154 o changes from 0.0.6pre2:
20155 - make hup work again
20156 - fix some memory leaks for dirservers
20157 - allow more skew in rendezvous descriptor timestamps, to help
20158 handle people like blanu who don't know what time it is
20159 - normal circs are 3 hops, but some rend/intro circs are 4, if
20160 the initiator doesn't get to choose the last hop
20161 - send acks for introductions, so alice can know whether to try
20163 - bob publishes intro points more correctly
20164 o changes from 0.0.5:
20165 - fix an assert trigger that's been plaguing us since the days
20166 of 0.0.2prexx (thanks weasel!)
20167 - retry stream correctly when we fail to connect because of
20168 exit-policy-reject (should try another) or can't-resolve-address
20169 (also should try another, because dns on random internet servers
20171 - when we hup a dirserver and we've *removed* a server from the
20172 approved-routers list, now we remove that server from the
20173 in-memory directories too
20176 Changes in version 0.0.6pre2 - 2004-04-08
20177 o We fixed our base32 implementation. Now it works on all architectures.
20180 Changes in version 0.0.6pre1 - 2004-04-08
20182 - Hidden services and rendezvous points are implemented. Go to
20183 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
20184 hidden services. (This only works via a socks4a proxy such as
20185 Privoxy, and currently it's quite slow.)
20188 Changes in version 0.0.5 - 2004-03-30
20189 [version bump only]
20192 Changes in version 0.0.5rc3 - 2004-03-29
20193 o Install torrc as torrc.sample -- we no longer clobber your
20195 o Re-enable recommendedversion checking (we broke it in rc2, oops)
20196 o Add in a 'notice' log level for things the operator should hear
20197 but that aren't warnings
20200 Changes in version 0.0.5rc2 - 2004-03-29
20201 o Hold socks connection open until reply is flushed (if possible)
20202 o Make exit nodes resolve IPs to IPs immediately, rather than asking
20203 the dns farm to do it.
20204 o Fix c99 aliasing warnings in rephist.c
20205 o Don't include server descriptors that are older than 24 hours in the
20207 o Give socks 'reject' replies their whole 15s to attempt to flush,
20208 rather than seeing the 60s timeout and assuming the flush had failed.
20209 o Clean automake droppings from the cvs repository
20212 Changes in version 0.0.5rc1 - 2004-03-28
20213 o Fix mangled-state bug in directory fetching (was causing sigpipes).
20214 o Only build circuits after we've fetched the directory: clients were
20215 using only the directory servers before they'd fetched a directory.
20216 This also means longer startup time; so it goes.
20217 o Fix an assert trigger where an OP would fail to handshake, and we'd
20218 expect it to have a nickname.
20219 o Work around a tsocks bug: do a socks reject when AP connection dies
20220 early, else tsocks goes into an infinite loop.
20223 Changes in version 0.0.4 - 2004-03-26
20224 o When connecting to a dirserver or OR and the network is down,
20228 Changes in version 0.0.3 - 2004-03-26
20229 o Warn and fail if server chose a nickname with illegal characters
20230 o Port to Solaris and Sparc:
20231 - include missing header fcntl.h
20232 - have autoconf find -lsocket -lnsl automatically
20233 - deal with hardware word alignment
20234 - make uname() work (solaris has a different return convention)
20235 - switch from using signal() to sigaction()
20236 o Preliminary work on reputation system:
20237 - Keep statistics on success/fail of connect attempts; they're published
20238 by kill -USR1 currently.
20239 - Add a RunTesting option to try to learn link state by creating test
20240 circuits, even when SocksPort is off.
20241 - Remove unused open circuits when there are too many.
20244 Changes in version 0.0.2 - 2004-03-19
20245 - Include strlcpy and strlcat for safer string ops
20246 - define INADDR_NONE so we compile (but still not run) on solaris
20249 Changes in version 0.0.2pre27 - 2004-03-14
20251 - Allow internal tor networks (we were rejecting internal IPs,
20252 now we allow them if they're set explicitly).
20253 - And fix a few endian issues.
20256 Changes in version 0.0.2pre26 - 2004-03-14
20258 - If a stream times out after 15s without a connected cell, don't
20259 try that circuit again: try a new one.
20260 - Retry streams at most 4 times. Then give up.
20261 - When a dirserver gets a descriptor from an unknown router, it
20262 logs its fingerprint (so the dirserver operator can choose to
20263 accept it even without mail from the server operator).
20264 - Inform unapproved servers when we reject their descriptors.
20265 - Make tor build on Windows again. It works as a client, who knows
20267 - Clearer instructions in the torrc for how to set up a server.
20268 - Be more efficient about reading fd's when our global token bucket
20269 (used for rate limiting) becomes empty.
20271 - Stop asserting that computers always go forward in time. It's
20273 - When we sent a cell (e.g. destroy) and then marked an OR connection
20274 expired, we might close it before finishing a flush if the other
20275 side isn't reading right then.
20276 - Don't allow dirservers to start if they haven't defined
20277 RecommendedVersions
20278 - We were caching transient dns failures. Oops.
20279 - Prevent servers from publishing an internal IP as their address.
20280 - Address a strcat vulnerability in circuit.c
20283 Changes in version 0.0.2pre25 - 2004-03-04
20285 - Put the OR's IP in its router descriptor, not its fqdn. That way
20286 we'll stop being stalled by gethostbyname for nodes with flaky dns,
20289 - If the user typed in an address that didn't resolve, the server
20293 Changes in version 0.0.2pre24 - 2004-03-03
20295 - Fix an assertion failure in dns.c, where we were trying to dequeue
20296 a pending dns resolve even if it wasn't pending
20297 - Fix a spurious socks5 warning about still trying to write after the
20298 connection is finished.
20299 - Hold certain marked_for_close connections open until they're finished
20300 flushing, rather than losing bytes by closing them too early.
20301 - Correctly report the reason for ending a stream
20302 - Remove some duplicate calls to connection_mark_for_close
20303 - Put switch_id and start_daemon earlier in the boot sequence, so it
20304 will actually try to chdir() to options.DataDirectory
20305 - Make 'make test' exit(1) if a test fails; fix some unit tests
20306 - Make tor fail when you use a config option it doesn't know about,
20307 rather than warn and continue.
20308 - Make --version work
20309 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
20312 Changes in version 0.0.2pre23 - 2004-02-29
20314 - Print a statement when the first circ is finished, so the user
20315 knows it's working.
20316 - If a relay cell is unrecognized at the end of the circuit,
20317 send back a destroy. (So attacks to mutate cells are more
20319 - New config option 'excludenodes' to avoid certain nodes for circuits.
20320 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
20321 so you can collect coredumps there.
20323 - Fix a bug in tls flushing where sometimes data got wedged and
20324 didn't flush until more data got sent. Hopefully this bug was
20325 a big factor in the random delays we were seeing.
20326 - Make 'connected' cells include the resolved IP, so the client
20327 dns cache actually gets populated.
20328 - Disallow changing from ORPort=0 to ORPort>0 on hup.
20329 - When we time-out on a stream and detach from the circuit, send an
20330 end cell down it first.
20331 - Only warn about an unknown router (in exitnodes, entrynodes,
20332 excludenodes) after we've fetched a directory.
20335 Changes in version 0.0.2pre22 - 2004-02-26
20337 - Servers publish less revealing uname information in descriptors.
20338 - More memory tracking and assertions, to crash more usefully when
20340 - If the default torrc isn't there, just use some default defaults.
20341 Plus provide an internal dirservers file if they don't have one.
20342 - When the user tries to use Tor as an http proxy, give them an http
20343 501 failure explaining that we're a socks proxy.
20344 - Dump a new router.desc on hup, to help confused people who change
20345 their exit policies and then wonder why router.desc doesn't reflect
20347 - Clean up the generic tor.sh init script that we ship with.
20349 - If the exit stream is pending on the resolve, and a destroy arrives,
20350 then the stream wasn't getting removed from the pending list. I
20351 think this was the one causing recent server crashes.
20352 - Use a more robust poll on OSX 10.3, since their poll is flaky.
20353 - When it couldn't resolve any dirservers, it was useless from then on.
20354 Now it reloads the RouterFile (or default dirservers) if it has no
20356 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
20357 many users don't even *have* a /usr/local/sbin/.
20360 Changes in version 0.0.2pre21 - 2004-02-18
20362 - There's a ChangeLog file that actually reflects the changelog.
20363 - There's a 'torify' wrapper script, with an accompanying
20364 tor-tsocks.conf, that simplifies the process of using tsocks for
20365 tor. It even has a man page.
20366 - The tor binary gets installed to sbin rather than bin now.
20367 - Retry streams where the connected cell hasn't arrived in 15 seconds
20368 - Clean up exit policy handling -- get the default out of the torrc,
20369 so we can update it without forcing each server operator to fix
20371 - Allow imaps and pop3s in default exit policy
20373 - Prevent picking middleman nodes as the last node in the circuit
20376 Changes in version 0.0.2pre20 - 2004-01-30
20378 - We now have a deb package, and it's in debian unstable. Go to
20379 it, apt-getters. :)
20380 - I've split the TotalBandwidth option into BandwidthRate (how many
20381 bytes per second you want to allow, long-term) and
20382 BandwidthBurst (how many bytes you will allow at once before the cap
20383 kicks in). This better token bucket approach lets you, say, set
20384 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
20385 performance while not exceeding your monthly bandwidth quota.
20386 - Push out a tls record's worth of data once you've got it, rather
20387 than waiting until you've read everything waiting to be read. This
20388 may improve performance by pipelining better. We'll see.
20389 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
20390 from failed circuits (if they haven't been connected yet) and attach
20392 - Expire old streams that haven't managed to connect. Some day we'll
20393 have them reattach to new circuits instead.
20396 - Fix several memory leaks that were causing servers to become bloated
20398 - Fix a few very rare assert triggers. A few more remain.
20399 - Setuid to User _before_ complaining about running as root.
20402 Changes in version 0.0.2pre19 - 2004-01-07
20404 - Fix deadlock condition in dns farm. We were telling a child to die by
20405 closing the parent's file descriptor to him. But newer children were
20406 inheriting the open file descriptor from the parent, and since they
20407 weren't closing it, the socket never closed, so the child never read
20408 eof, so he never knew to exit. Similarly, dns workers were holding
20409 open other sockets, leading to all sorts of chaos.
20410 - New cleaner daemon() code for forking and backgrounding.
20411 - If you log to a file, it now prints an entry at the top of the
20412 logfile so you know it's working.
20413 - The onionskin challenge length was 30 bytes longer than necessary.
20414 - Started to patch up the spec so it's not quite so out of date.
20417 Changes in version 0.0.2pre18 - 2004-01-02
20419 - Fix endian issues with the 'integrity' field in the relay header.
20420 - Fix a potential bug where connections in state
20421 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
20424 Changes in version 0.0.2pre17 - 2003-12-30
20426 - Made --debuglogfile (or any second log file, actually) work.
20427 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
20428 adversary could force us into an infinite loop.
20431 - Each onionskin handshake now includes a hash of the computed key,
20432 to prove the server's identity and help perfect forward secrecy.
20433 - Changed cell size from 256 to 512 bytes (working toward compatibility
20435 - Changed cell length to 2 bytes, and moved it to the relay header.
20436 - Implemented end-to-end integrity checking for the payloads of
20438 - Separated streamid from 'recognized' (otherwise circuits will get
20439 messed up when we try to have streams exit from the middle). We
20440 use the integrity-checking to confirm that a cell is addressed to
20442 - Randomize the initial circid and streamid values, so an adversary who
20443 breaks into a node can't learn how many circuits or streams have
20447 Changes in version 0.0.2pre16 - 2003-12-14
20449 - Fixed a bug that made HUP trigger an assert
20450 - Fixed a bug where a circuit that immediately failed wasn't being
20451 counted as a failed circuit in counting retries.
20454 - Now we close the circuit when we get a truncated cell: otherwise we're
20455 open to an anonymity attack where a bad node in the path truncates
20456 the circuit and then we open streams at him.
20457 - Add port ranges to exit policies
20458 - Add a conservative default exit policy
20459 - Warn if you're running tor as root
20460 - on HUP, retry OR connections and close/rebind listeners
20461 - options.EntryNodes: try these nodes first when picking the first node
20462 - options.ExitNodes: if your best choices happen to include any of
20463 your preferred exit nodes, you choose among just those preferred
20465 - options.ExcludedNodes: nodes that are never picked in path building
20468 Changes in version 0.0.2pre15 - 2003-12-03
20469 o Robustness and bugfixes:
20470 - Sometimes clients would cache incorrect DNS resolves, which would
20471 really screw things up.
20472 - An OP that goes offline would slowly leak all its sockets and stop
20474 - A wide variety of bugfixes in exit node selection, exit policy
20475 handling, and processing pending streams when a new circuit is
20477 - Pick nodes for a path only from those the directory says are up
20478 - Choose randomly from all running dirservers, not always the first one
20479 - Increase allowed http header size for directory fetch.
20480 - Stop writing to stderr (if we're daemonized it will be closed).
20481 - Enable -g always, so cores will be more useful to me.
20482 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
20485 - Wrote a man page. It lists commonly used options.
20488 - Change default loglevel to warn.
20489 - Make PidFile default to null rather than littering in your CWD.
20490 - OnionRouter config option is now obsolete. Instead it just checks
20492 - Moved to a single unified torrc file for both clients and servers.
20495 Changes in version 0.0.2pre14 - 2003-11-29
20496 o Robustness and bugfixes:
20497 - Force the admin to make the DataDirectory himself
20498 - to get ownership/permissions right
20499 - so clients no longer make a DataDirectory and then never use it
20500 - fix bug where a client who was offline for 45 minutes would never
20501 pull down a directory again
20502 - fix (or at least hide really well) the dns assert bug that was
20503 causing server crashes
20504 - warnings and improved robustness wrt clockskew for certs
20505 - use the native daemon(3) to daemonize, when available
20506 - exit if bind() fails
20507 - exit if neither socksport nor orport is defined
20508 - include our own tor_timegm (Win32 doesn't have its own)
20509 - bugfix for win32 with lots of connections
20510 - fix minor bias in PRNG
20511 - make dirserver more robust to corrupt cached directory
20514 - Wrote the design document (woo)
20516 o Circuit building and exit policies:
20517 - Circuits no longer try to use nodes that the directory has told them
20519 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
20520 bitcounts (18.0.0.0/8).
20521 - Make AP connections standby for a circuit if no suitable circuit
20522 exists, rather than failing
20523 - Circuits choose exit node based on addr/port, exit policies, and
20524 which AP connections are standing by
20525 - Bump min pathlen from 2 to 3
20526 - Relay end cells have a payload to describe why the stream ended.
20527 - If the stream failed because of exit policy, try again with a new
20529 - Clients have a dns cache to remember resolved addresses.
20530 - Notice more quickly when we have no working circuits
20533 - APPort is now called SocksPort
20534 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
20536 - RecommendedVersions is now a config variable rather than
20537 hardcoded (for dirservers)
20538 - Reloads config on HUP
20539 - Usage info on -h or --help
20540 - If you set User and Group config vars, it'll setu/gid to them.
20543 Changes in version 0.0.2pre13 - 2003-10-19
20544 o General stability:
20545 - SSL_write no longer fails when it returns WANTWRITE and the number
20546 of bytes in the buf has changed by the next SSL_write call.
20547 - Fix segfault fetching directory when network is down
20548 - Fix a variety of minor memory leaks
20549 - Dirservers reload the fingerprints file on HUP, so I don't have
20550 to take down the network when I approve a new router
20551 - Default server config file has explicit Address line to specify fqdn
20554 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
20555 - Make listener connections not ever alloc bufs
20557 o Autoconf improvements:
20558 - don't clobber an external CFLAGS in ./configure
20559 - Make install now works
20560 - create var/lib/tor on make install
20561 - autocreate a tor.sh initscript to help distribs
20562 - autocreate the torrc and sample-server-torrc with correct paths
20564 o Log files and Daemonizing now work:
20565 - If --DebugLogFile is specified, log to it at -l debug
20566 - If --LogFile is specified, use it instead of commandline
20567 - If --RunAsDaemon is set, tor forks and backgrounds on startup