2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.4.28 - 2017-03-03
7 Tor 0.2.4.28 backports a number of security fixes from later Tor
8 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
9 this release, if for some reason they cannot upgrade to a later
12 Note that support for Tor 0.2.4.x is ending soon: we will not issue
13 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
14 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
16 o Directory authority changes (backport from 0.2.8.5-rc):
17 - Urras is no longer a directory authority. Closes ticket 19271.
19 o Directory authority changes (backport from 0.2.9.2-alpha):
20 - The "Tonga" bridge authority has been retired; the new bridge
21 authority is "Bifroest". Closes tickets 19728 and 19690.
23 o Directory authority key updates (backport from 0.2.8.1-alpha):
24 - Update the V3 identity key for the dannenberg directory authority:
25 it was changed on 18 November 2015. Closes task 17906. Patch
28 o Major features (security fixes, backport from 0.2.9.4-alpha):
29 - Prevent a class of security bugs caused by treating the contents
30 of a buffer chunk as if they were a NUL-terminated string. At
31 least one such bug seems to be present in all currently used
32 versions of Tor, and would allow an attacker to remotely crash
33 most Tor instances, especially those compiled with extra compiler
34 hardening. With this defense in place, such bugs can't crash Tor,
35 though we should still fix them as they occur. Closes ticket
36 20384 (TROVE-2016-10-001).
38 o Major bugfixes (parsing, security, backport from 0.2.9.8):
39 - Fix a bug in parsing that could cause clients to read a single
40 byte past the end of an allocated region. This bug could be used
41 to cause hardened clients (built with --enable-expensive-hardening)
42 to crash if they tried to visit a hostile hidden service. Non-
43 hardened clients are only affected depending on the details of
44 their platform's memory allocator. Fixes bug 21018; bugfix on
45 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
46 2016-12-002 and as CVE-2016-1254.
48 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
49 - Fix an error that could cause us to read 4 bytes before the
50 beginning of an openssl string. This bug could be used to cause
51 Tor to crash on systems with unusual malloc implementations, or
52 systems with unusual hardening installed. Fixes bug 17404; bugfix
55 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
56 - Avoid a difficult-to-trigger heap corruption attack when extending
57 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
58 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
59 Reported by Guido Vranken.
61 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
62 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
63 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
65 o Major bugfixes (guard selection, backport from 0.2.7.6):
66 - Actually look at the Guard flag when selecting a new directory
67 guard. When we implemented the directory guard design, we
68 accidentally started treating all relays as if they have the Guard
69 flag during guard selection, leading to weaker anonymity and worse
70 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
73 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
74 - If OpenSSL fails to generate an RSA key, do not retain a dangling
75 pointer to the previous (uninitialized) key value. The impact here
76 should be limited to a difficult-to-trigger crash, if OpenSSL is
77 running an engine that makes key generation failures possible, or
78 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
79 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
82 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
83 - Fix an integer underflow bug when comparing malformed Tor
84 versions. This bug could crash Tor when built with
85 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
86 0.2.9.8, which were built with -ftrapv by default. In other cases
87 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
88 on 0.0.8pre1. Found by OSS-Fuzz.
90 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
91 - Make memwipe() do nothing when passed a NULL pointer or buffer of
92 zero size. Check size argument to memwipe() for underflow. Fixes
93 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
96 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
97 - Make Tor survive errors involving connections without a
98 corresponding event object. Previously we'd fail with an
99 assertion; now we produce a log message. Related to bug 16248.
101 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
102 - Make it harder for attackers to overload hidden services with
103 introductions, by blocking multiple introduction requests on the
104 same circuit. Resolves ticket 15515.
106 o Minor features (geoip):
107 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
110 o Minor bugfixes (compilation, backport from 0.2.7.6):
111 - Fix a compilation warning with Clang 3.6: Do not check the
112 presence of an address which can never be NULL. Fixes bug 17781.
114 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
115 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
116 a client authorized hidden service. Fixes bug 15823; bugfix
120 Changes in version 0.2.4.27 - 2015-04-06
121 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
122 could be used by an attacker to crash hidden services, or crash clients
123 visiting hidden services. Hidden services should upgrade as soon as
124 possible; clients should upgrade whenever packages become available.
126 This release also backports a simple improvement to make hidden
127 services a bit less vulnerable to denial-of-service attacks.
129 o Major bugfixes (security, hidden service):
130 - Fix an issue that would allow a malicious client to trigger an
131 assertion failure and halt a hidden service. Fixes bug 15600;
132 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
133 - Fix a bug that could cause a client to crash with an assertion
134 failure when parsing a malformed hidden service descriptor. Fixes
135 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
137 o Minor features (DoS-resistance, hidden service):
138 - Introduction points no longer allow multiple INTRODUCE1 cells to
139 arrive on the same circuit. This should make it more expensive for
140 attackers to overwhelm hidden services with introductions.
141 Resolves ticket 15515.
144 Changes in version 0.2.4.26 - 2015-03-17
145 Tor 0.2.4.26 includes an updated list of directory authorities. It
146 also backports a couple of stability and security bugfixes from 0.2.5
149 o Directory authority changes:
150 - Remove turtles as a directory authority.
151 - Add longclaw as a new (v3) directory authority. This implements
152 ticket 13296. This keeps the directory authority count at 9.
153 - The directory authority Faravahar has a new IP address. This
156 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
157 - Fix an assertion failure that could occur under high DNS load.
158 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
159 diagnosed and fixed by "cypherpunks".
161 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
162 - Fix a bug that could lead to a relay crashing with an assertion
163 failure if a buffer of exactly the wrong layout was passed to
164 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
165 0.2.0.10-alpha. Patch from 'cypherpunks'.
166 - Do not assert if the 'data' pointer on a buffer is advanced to the
167 very end of the buffer; log a BUG message instead. Only assert if
168 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
170 o Minor features (geoip):
171 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
172 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
176 Changes in version 0.2.4.25 - 2014-10-20
177 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
178 (even though POODLE does not affect Tor). It also works around a crash
179 bug caused by some operating systems' response to the "POODLE" attack
180 (which does affect Tor).
182 o Major security fixes (also in 0.2.5.9-rc):
183 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
184 today support TLS 1.0 or later, so we can safely turn off support
185 for this old (and insecure) protocol. Fixes bug 13426.
187 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
188 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
189 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
190 13471. This is a workaround for an OpenSSL bug.
193 Changes in version 0.2.4.24 - 2014-09-22
194 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
195 connecting to hidden services, and it updates the location of one of
196 the directory authorities.
199 - Clients now send the correct address for their chosen rendezvous
200 point when trying to access a hidden service. They used to send
201 the wrong address, which would still work some of the time because
202 they also sent the identity digest of the rendezvous point, and if
203 the hidden service happened to try connecting to the rendezvous
204 point from a relay that already had a connection open to it,
205 the relay would reuse that connection. Now connections to hidden
206 services should be more robust and faster. Also, this bug meant
207 that clients were leaking to the hidden service whether they were
208 on a little-endian (common) or big-endian (rare) system, which for
209 some users might have reduced their anonymity. Fixes bug 13151;
210 bugfix on 0.2.1.5-alpha.
212 o Directory authority changes:
213 - Change IP address for gabelmoo (v3 directory authority).
215 o Minor features (geoip):
216 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
220 Changes in version 0.2.4.23 - 2014-07-28
221 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
222 guard rotation, and also backports several important fixes from the
223 Tor 0.2.5 alpha release series.
226 - Clients now look at the "usecreatefast" consensus parameter to
227 decide whether to use CREATE_FAST or CREATE cells for the first hop
228 of their circuit. This approach can improve security on connections
229 where Tor's circuit handshake is stronger than the available TLS
230 connection security levels, but the tradeoff is more computational
231 load on guard relays. Implements proposal 221. Resolves ticket 9386.
232 - Make the number of entry guards configurable via a new
233 NumEntryGuards consensus parameter, and the number of directory
234 guards configurable via a new NumDirectoryGuards consensus
235 parameter. Implements ticket 12688.
238 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
239 implementation that caused incorrect results on 32-bit
240 implementations when certain malformed inputs were used along with
241 a small class of private ntor keys. This bug does not currently
242 appear to allow an attacker to learn private keys or impersonate a
243 Tor server, but it could provide a means to distinguish 32-bit Tor
244 implementations from 64-bit Tor implementations. Fixes bug 12694;
245 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
249 - Warn and drop the circuit if we receive an inbound 'relay early'
250 cell. Those used to be normal to receive on hidden service circuits
251 due to bug 1038, but the buggy Tor versions are long gone from
252 the network so we can afford to resume watching for them. Resolves
253 the rest of bug 1038; bugfix on 0.2.1.19.
254 - Correct a confusing error message when trying to extend a circuit
255 via the control protocol but we don't know a descriptor or
256 microdescriptor for one of the specified relays. Fixes bug 12718;
257 bugfix on 0.2.3.1-alpha.
258 - Avoid an illegal read from stack when initializing the TLS
259 module using a version of OpenSSL without all of the ciphers
260 used by the v2 link handshake. Fixes bug 12227; bugfix on
261 0.2.4.8-alpha. Found by "starlight".
264 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
268 Changes in version 0.2.4.22 - 2014-05-16
269 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
270 alpha release series. These include blocking all authority signing
271 keys that may have been affected by the OpenSSL "heartbleed" bug,
272 choosing a far more secure set of TLS ciphersuites by default, closing
273 a couple of memory leaks that could be used to run a target relay out
274 of RAM, and several others.
276 o Major features (security, backport from 0.2.5.4-alpha):
277 - Block authority signing keys that were used on authorities
278 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
279 don't have any evidence that these keys _were_ compromised; we're
280 doing this to be prudent.) Resolves ticket 11464.
282 o Major bugfixes (security, OOM):
283 - Fix a memory leak that could occur if a microdescriptor parse
284 fails during the tokenizing step. This bug could enable a memory
285 exhaustion attack by directory servers. Fixes bug 11649; bugfix
288 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
289 - The relay ciphersuite list is now generated automatically based on
290 uniform criteria, and includes all OpenSSL ciphersuites with
291 acceptable strength and forward secrecy. Previously, we had left
292 some perfectly fine ciphersuites unsupported due to omission or
293 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
294 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
295 - Relays now trust themselves to have a better view than clients of
296 which TLS ciphersuites are better than others. (Thanks to bug
297 11513, the relay list is now well-considered, whereas the client
298 list has been chosen mainly for anti-fingerprinting purposes.)
299 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
300 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
301 AES128. Resolves ticket 11528.
302 - Clients now try to advertise the same list of ciphersuites as
303 Firefox 28. This change enables selection of (fast) GCM
304 ciphersuites, disables some strange old ciphers, and stops
305 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
306 Resolves ticket 11438.
308 o Minor bugfixes (configuration, security):
309 - When running a hidden service, do not allow TunneledDirConns 0:
310 trying to set that option together with a hidden service would
311 otherwise prevent the hidden service from running, and also make
312 it publish its descriptors directly over HTTP. Fixes bug 10849;
313 bugfix on 0.2.1.1-alpha.
315 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
316 - Avoid sending a garbage value to the controller when a circuit is
317 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
319 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
320 - Stop leaking memory when we successfully resolve a PTR record.
321 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
323 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
324 - Avoid 60-second delays in the bootstrapping process when Tor is
325 launching for a second time while using bridges. Fixes bug 9229;
326 bugfix on 0.2.0.3-alpha.
328 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
329 - Give the correct URL in the warning message when trying to run a
330 relay on an ancient version of Windows. Fixes bug 9393.
332 o Minor bugfixes (compilation):
333 - Fix a compilation error when compiling with --disable-curve25519.
334 Fixes bug 9700; bugfix on 0.2.4.17-rc.
337 - Downgrade the warning severity for the the "md was still
338 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
339 for trying to diagnose this bug, and the current warning in
340 earlier versions of tor achieves nothing useful. Addresses warning
343 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
344 - When we run out of usable circuit IDs on a channel, log only one
345 warning for the whole channel, and describe how many circuits
346 there were on the channel. Fixes part of ticket 11553.
348 o Minor features (security, backport from 0.2.5.4-alpha):
349 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
350 leave the default at 8GBytes), to better support Raspberry Pi
351 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
353 o Documentation (backport from 0.2.5.4-alpha):
354 - Correctly document that we search for a system torrc file before
355 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
359 Changes in version 0.2.4.21 - 2014-02-28
360 Tor 0.2.4.21 further improves security against potential adversaries who
361 find breaking 1024-bit crypto doable, and backports several stability
362 and robustness patches from the 0.2.5 branch.
364 o Major features (client security):
365 - When we choose a path for a 3-hop circuit, make sure it contains
366 at least one relay that supports the NTor circuit extension
367 handshake. Otherwise, there is a chance that we're building
368 a circuit that's worth attacking by an adversary who finds
369 breaking 1024-bit crypto doable, and that chance changes the game
370 theory. Implements ticket 9777.
373 - Do not treat streams that fail with reason
374 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
375 since it could also indicate an ENETUNREACH connection error. Fixes
376 part of bug 10777; bugfix on 0.2.4.8-alpha.
378 o Code simplification and refactoring:
379 - Remove data structures which were introduced to implement the
380 CellStatistics option: they are now redundant with the new timestamp
381 field in the regular packed_cell_t data structure, which we did
382 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
385 - Always clear OpenSSL bignums before freeing them -- even bignums
386 that don't contain secrets. Resolves ticket 10793. Patch by
388 - Build without warnings under clang 3.4. (We have some macros that
389 define static functions only some of which will get used later in
390 the module. Starting with clang 3.4, these give a warning unless the
391 unused attribute is set on them.) Resolves ticket 10904.
392 - Update geoip and geoip6 files to the February 7 2014 Maxmind
393 GeoLite2 Country database.
396 - Set the listen() backlog limit to the largest actually supported
397 on the system, not to the value in a header file. Fixes bug 9716;
398 bugfix on every released Tor.
399 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
400 exit node as a NOROUTE error, not an INTERNAL error, since they
401 can apparently happen when trying to connect to the wrong sort
402 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
403 - Fix build warnings about missing "a2x" comment when building the
404 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
405 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
406 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
407 not entirely remove it from the connection lists. Fixes bug 9602;
408 bugfix on 0.2.4.4-alpha.
409 - Fix a segmentation fault in our benchmark code when running with
410 Fedora's OpenSSL package, or any other OpenSSL that provides
411 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
412 - Turn "circuit handshake stats since last time" log messages into a
413 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
415 o Documentation fixes:
416 - Document that all but one DirPort entry must have the NoAdvertise
417 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
420 Changes in version 0.2.4.20 - 2013-12-22
421 Tor 0.2.4.20 fixes potentially poor random number generation for users
422 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
423 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
424 and 4) have no state file in their DataDirectory (as would happen on
425 first start). Users who generated relay or hidden service identity
426 keys in such a situation should discard them and generate new ones.
428 This release also fixes a logic error that caused Tor clients to build
429 many more preemptive circuits than they actually need.
432 - Do not allow OpenSSL engines to replace the PRNG, even when
433 HardwareAccel is set. The only default builtin PRNG engine uses
434 the Intel RDRAND instruction to replace the entire PRNG, and
435 ignores all attempts to seed it with more entropy. That's
436 cryptographically stupid: the right response to a new alleged
437 entropy source is never to discard all previously used entropy
438 sources. Fixes bug 10402; works around behavior introduced in
439 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
441 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
442 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
443 - Avoid launching spurious extra circuits when a stream is pending.
444 This fixes a bug where any circuit that _wasn't_ unusable for new
445 streams would be treated as if it were, causing extra circuits to
446 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
449 - Avoid a crash bug when starting with a corrupted microdescriptor
450 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
451 - If we fail to dump a previously cached microdescriptor to disk, avoid
452 freeing duplicate data later on. Fixes bug 10423; bugfix on
453 0.2.4.13-alpha. Spotted by "bobnomnom".
456 Changes in version 0.2.4.19 - 2013-12-11
457 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
458 (1986-2013). Aaron worked on diverse projects including helping to guide
459 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
460 transparency to the U.S government's PACER documents, and contributing
461 design and development for Tor and Tor2Web. Aaron was one of the latest
462 martyrs in our collective fight for civil liberties and human rights,
463 and his death is all the more painful because he was one of us.
465 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
466 a new circuit handshake and link encryption that use ECC to provide
467 better security and efficiency; makes relays better manage circuit
468 creation requests; uses "directory guards" to reduce client enumeration
469 risks; makes bridges collect and report statistics about the pluggable
470 transports they support; cleans up and improves our geoip database;
471 gets much closer to IPv6 support for clients, bridges, and relays; makes
472 directory authorities use measured bandwidths rather than advertised
473 ones when computing flags and thresholds; disables client-side DNS
474 caching to reduce tracking risks; and fixes a big bug in bridge
475 reachability testing. This release introduces two new design
476 abstractions in the code: a new "channel" abstraction between circuits
477 and or_connections to allow for implementing alternate relay-to-relay
478 transports, and a new "circuitmux" abstraction storing the queue of
479 circuits for a channel. The release also includes many stability,
480 security, and privacy fixes.
482 o Major features (new circuit handshake):
483 - Tor now supports a new circuit extension handshake designed by Ian
484 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
485 circuit extension handshake, later called "TAP", was a bit slow
486 (especially on the relay side), had a fragile security proof, and
487 used weaker keys than we'd now prefer. The new circuit handshake
488 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
489 function, making it significantly more secure than the older
490 handshake, and significantly faster. Tor can use one of two built-in
491 pure-C curve25519-donna implementations by Adam Langley, or it
492 can link against the "nacl" library for a tuned version if present.
494 The built-in version is very fast for 64-bit systems when building
495 with GCC. The built-in 32-bit version is still faster than the
496 old TAP protocol, but using libnacl is better on most such hosts.
498 Implements proposal 216; closes ticket 7202.
500 o Major features (better link encryption):
501 - Relays can now enable the ECDHE TLS ciphersuites when available
502 and appropriate. These ciphersuites let us negotiate forward-secure
503 TLS secret keys more safely and more efficiently than with our
504 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
505 public relays prefer the (faster) P224 group, and bridges prefer
506 the (more common) P256 group; you can override this with the
509 This feature requires clients running 0.2.3.17-beta or later,
510 and requires both sides to be running OpenSSL 1.0.0 or later
511 with ECC support. OpenSSL 1.0.1, with the compile-time option
512 "enable-ec_nistp_64_gcc_128", is highly recommended.
514 Implements the relay side of proposal 198; closes ticket 7200.
516 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
517 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
518 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
519 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
520 them to solve bug 6033.)
522 o Major features (relay performance):
523 - Instead of limiting the number of queued onionskins (aka circuit
524 create requests) to a fixed, hard-to-configure number, we limit
525 the size of the queue based on how many we expect to be able to
526 process in a given amount of time. We estimate the time it will
527 take to process an onionskin based on average processing time
528 of previous onionskins. Closes ticket 7291. You'll never have to
529 configure MaxOnionsPending again.
530 - Relays process the new "NTor" circuit-level handshake requests
531 with higher priority than the old "TAP" circuit-level handshake
532 requests. We still process some TAP requests to not totally starve
533 0.2.3 clients when NTor becomes popular. A new consensus parameter
534 "NumNTorsPerTAP" lets us tune the balance later if we need to.
535 Implements ticket 9574.
537 o Major features (client bootstrapping resilience):
538 - Add a new "FallbackDir" torrc option to use when we can't use
539 a directory mirror from the consensus (either because we lack a
540 consensus, or because they're all down). Currently, all authorities
541 are fallbacks by default, and there are no other default fallbacks,
542 but that will change. This option will allow us to give clients a
543 longer list of servers to try to get a consensus from when first
544 connecting to the Tor network, and thereby reduce load on the
545 directory authorities. Implements proposal 206, "Preconfigured
546 directory sources for bootstrapping". We also removed the old
547 "FallbackNetworkstatus" option, since we never got it working well
548 enough to use it. Closes bug 572.
549 - If we have no circuits open, use a relaxed timeout (the
550 95th-percentile cutoff) until a circuit succeeds. This heuristic
551 should allow Tor to succeed at building circuits even when the
552 network connection drastically changes. Should help with bug 3443.
554 o Major features (use of guards):
555 - Support directory guards (proposal 207): when possible, clients now
556 use their entry guards for non-anonymous directory requests. This
557 can help prevent client enumeration. Note that this behavior only
558 works when we have a usable consensus directory, and when options
559 about what to download are more or less standard. In the future we
560 should re-bootstrap from our guards, rather than re-bootstrapping
561 from the preconfigured list of directory sources that ships with
562 Tor. Resolves ticket 6526.
563 - Raise the default time that a client keeps an entry guard from
564 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
565 2012 paper. (We would make it even longer, but we need better client
566 load balancing first.) Also, make the guard lifetime controllable
567 via a new GuardLifetime torrc option and a GuardLifetime consensus
568 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
570 o Major features (bridges with pluggable transports):
571 - Bridges now report the pluggable transports they support to the
572 bridge authority, so it can pass the supported transports on to
573 bridgedb and/or eventually do reachability testing. Implements
575 - Automatically forward the TCP ports of pluggable transport
576 proxies using tor-fw-helper if PortForwarding is enabled. Implements
579 o Major features (geoip database):
580 - Maxmind began labelling Tor relays as being in country "A1",
581 which breaks by-country node selection inside Tor. Now we use a
582 script to replace "A1" ("Anonymous Proxy") entries in our geoip
583 file with real country codes. This script fixes about 90% of "A1"
584 entries automatically and uses manual country code assignments to
585 fix the remaining 10%. See src/config/README.geoip for details.
587 - Add GeoIP database for IPv6 addresses. The new config option
589 - Update to the October 2 2013 Maxmind GeoLite Country database.
591 o Major features (IPv6):
592 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
593 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
594 to happen. Implements ticket 5535.
595 - All kind of relays, not just bridges, can now advertise an IPv6
596 OR port. Implements ticket 6362.
597 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
598 connectivity, then set the IPv6Exit flag to 1. Also make sure your
599 exit policy reads as you would like: the address * applies to all
600 address families, whereas *4 is IPv4 address only, and *6 is IPv6
601 addresses only. On the client side, you'll need to wait for enough
602 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
603 and use Socks5. Closes ticket 5547, implements proposal 117 as
604 revised in proposal 208.
605 - Bridge authorities now accept IPv6 bridge addresses and include
606 them in network status documents. Implements ticket 5534.
607 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
609 o Major features (directory authorities):
610 - Directory authorities now prefer using measured bandwidths to
611 advertised ones when computing flags and thresholds. Resolves
613 - Directory authorities that vote measured bandwidths about more
614 than a threshold number of relays now treat relays with
615 unmeasured bandwidths as having bandwidth 0 when computing their
616 flags. Resolves ticket 8435.
617 - Directory authorities now support a new consensus method (17)
618 where they cap the published bandwidth of relays for which
619 insufficient bandwidth measurements exist. Fixes part of bug 2286.
620 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
621 serve any v2 directory information. Now we can test disabling the
622 old deprecated v2 directory format, and see whether doing so has
623 any effect on network load. Begins to fix bug 6783.
625 o Major features (build and portability):
626 - Switch to a nonrecursive Makefile structure. Now instead of each
627 Makefile.am invoking other Makefile.am's, there is a master
628 Makefile.am that includes the others. This change makes our build
629 process slightly more maintainable, and improves parallelism for
630 building with make -j. Original patch by Stewart Smith; various
631 fixes by Jim Meyering.
632 - Where available, we now use automake's "silent" make rules by
633 default, so that warnings are easier to spot. You can get the old
634 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
635 - Resume building correctly with MSVC and Makefile.nmake. This patch
636 resolves numerous bugs and fixes reported by ultramage, including
637 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
640 - Switch to a completely time-invariant approach for picking nodes
641 weighted by bandwidth. Our old approach would run through the
642 part of the loop after it had made its choice slightly slower
643 than it ran through the part of the loop before it had made its
644 choice. Addresses ticket 6538.
645 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
646 by tor2web clients allows hidden services to identify tor2web
647 clients through their repeated selection of the same rendezvous
648 and introduction point circuit endpoints (their guards). Resolves
651 o Major bugfixes (relay denial of service):
652 - When we have too much memory queued in circuits (according to a new
653 MaxMemInCellQueues option), close the circuits that have the oldest
654 queued cells, on the theory that those are most responsible for
655 us running low on memory. This prevents us from running out of
656 memory as a relay if circuits fill up faster than they can be
657 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
658 Tor. This bug is a further fix beyond bug 6252, whose fix was
659 merged into 0.2.3.21-rc.
660 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
661 ID: these could be used to create unexpected streams and circuits
662 which would count as "present" to some parts of Tor but "absent"
663 to others, leading to zombie circuits and streams or to a bandwidth
664 denial-of-service. Fixes bug 7889; bugfix on every released version
665 of Tor. Reported by "oftc_must_be_destroyed".
666 - Avoid a bug where our response to TLS renegotiation under certain
667 network conditions could lead to a busy-loop, with 100% CPU
668 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
670 o Major bugfixes (asserts, crashes, leaks):
671 - Prevent the get_freelists() function from running off the end of
672 the list of freelists if it somehow gets an unrecognized
673 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
675 - Avoid a memory leak where we would leak a consensus body when we
676 find that a consensus which we couldn't previously verify due to
677 missing certificates is now verifiable. Fixes bug 8719; bugfix
679 - If we are unable to save a microdescriptor to the journal, do not
680 drop it from memory and then reattempt downloading it. Fixes bug
681 9645; bugfix on 0.2.2.6-alpha.
682 - Fix an assertion failure that would occur when disabling the
683 ORPort setting on a running Tor process while accounting was
684 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
685 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
686 when an exit connection with optimistic data succeeds immediately
687 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
689 - Fix a memory leak that would occur whenever a configuration
690 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
692 o Major bugfixes (relay rate limiting):
693 - When a TLS write is partially successful but incomplete, remember
694 that the flushed part has been flushed, and notice that bytes were
695 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
696 bugfix on Tor 0.1.0.5-rc.
697 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
698 to 1GB/1GB. The previous defaults were intended to be "basically
699 infinite", but it turns out they're now limiting our 100mbit+
700 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
701 last time we raised it).
702 - No longer stop reading or writing on cpuworker connections when
703 our rate limiting buckets go empty. Now we should handle circuit
704 handshake requests more promptly. Resolves bug 9731.
706 o Major bugfixes (client-side privacy):
707 - When we mark a circuit as unusable for new circuits, have it
708 continue to be unusable for new circuits even if MaxCircuitDirtiness
709 is increased too much at the wrong time, or the system clock jumps
710 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
711 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
712 which have resolved to internal addresses") is set, apply that
713 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
714 - When an exit relay rejects a stream with reason "exit policy", but
715 we only know an exit policy summary (e.g. from the microdesc
716 consensus) for it, do not mark the relay as useless for all exiting.
717 Instead, mark just the circuit as unsuitable for that particular
718 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
720 o Major bugfixes (stream isolation):
721 - Allow applications to get proper stream isolation with
722 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
723 username/password authentication also offer "no authentication". Tor
724 had previously preferred "no authentication", so the applications
725 never actually sent Tor their auth details. Now Tor selects
726 username/password authentication if it's offered. You can disable
727 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
728 bug 8117; bugfix on 0.2.3.3-alpha.
729 - Follow the socks5 protocol when offering username/password
730 authentication. The fix for bug 8117 exposed this bug, and it
731 turns out real-world applications like Pidgin do care. Bugfix on
732 0.2.3.2-alpha; fixes bug 8879.
734 o Major bugfixes (client circuit building):
735 - Alter circuit build timeout measurement to start at the point
736 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
737 initialization). This should make our timeout measurements more
738 uniform. Previously, we were sometimes including ORconn setup time
739 in our circuit build time measurements. Should resolve bug 3443.
740 - If the circuit build timeout logic is disabled (via the consensus,
741 or because we are an authority), then don't build testing circuits.
742 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
744 o Major bugfixes (client-side DNS):
745 - Turn off the client-side DNS cache by default. Updating and using
746 the DNS cache is now configurable on a per-client-port
747 level. SOCKSPort, DNSPort, etc lines may now contain
748 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
749 cache these types of DNS answers when we receive them from an
750 exit node in response to an application request on this port, and
751 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
752 cached DNS answers of these types, we shouldn't use them. It's
753 potentially risky to use cached DNS answers at the client, since
754 doing so can indicate to one exit what answers we've gotten
755 for DNS lookups in the past. With IPv6, this becomes especially
756 problematic. Using cached DNS answers for requests on the same
757 circuit would present less linkability risk, since all traffic
758 on a circuit is already linkable, but it would also provide
759 little performance benefit: the exit node caches DNS replies
760 too. Implements a simplified version of Proposal 205. Implements
763 o Major bugfixes (hidden service privacy):
764 - Limit hidden service descriptors to at most ten introduction
765 points, to slow one kind of guard enumeration. Fixes bug 9002;
766 bugfix on 0.1.1.11-alpha.
768 o Major bugfixes (directory fetching):
769 - If the time to download the next old-style networkstatus is in
770 the future, do not decline to consider whether to download the
771 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
773 - We used to always request authority certificates by identity digest,
774 meaning we'd get the newest one even when we wanted one with a
775 different signing key. Then we would complain about being given
776 a certificate we already had, and never get the one we really
777 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
778 resource to request the one we want. Fixes bug 5595; bugfix on
781 o Major bugfixes (bridge reachability):
782 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
783 previously they did not, which prevented them from receiving
784 successful connections from relays for self-test or bandwidth
785 testing. Also, when a relay is extending a circuit to a bridge,
786 it needs to send a NETINFO cell, even when the bridge hasn't sent
787 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
789 o Major bugfixes (control interface):
790 - When receiving a new configuration file via the control port's
791 LOADCONF command, do not treat the defaults file as absent.
792 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
794 o Major bugfixes (directory authorities):
795 - Stop marking every relay as having been down for one hour every
796 time we restart a directory authority. These artificial downtimes
797 were messing with our Stable and Guard flag calculations. Fixes
798 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
799 - When computing directory thresholds, ignore any rejected-as-sybil
800 nodes during the computation so that they can't influence Fast,
801 Guard, etc. (We should have done this for proposal 109.) Fixes
803 - When marking a node as a likely sybil, reset its uptime metrics
804 to zero, so that it cannot time towards getting marked as Guard,
805 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
807 - Fix a bug in the voting algorithm that could yield incorrect results
808 when a non-naming authority declared too many flags. Fixes bug 9200;
809 bugfix on 0.2.0.3-alpha.
811 o Internal abstraction features:
812 - Introduce new channel_t abstraction between circuits and
813 or_connection_t to allow for implementing alternate OR-to-OR
814 transports. A channel_t is an abstract object which can either be a
815 cell-bearing channel, which is responsible for authenticating and
816 handshaking with the remote OR and transmitting cells to and from
817 it, or a listening channel, which spawns new cell-bearing channels
818 at the request of remote ORs. Implements part of ticket 6465.
819 - Make a channel_tls_t subclass of channel_t, adapting it to the
820 existing or_connection_t code. The V2/V3 protocol handshaking
821 code which formerly resided in command.c has been moved below the
822 channel_t abstraction layer and may be found in channeltls.c now.
823 Implements the rest of ticket 6465.
824 - Introduce new circuitmux_t storing the queue of circuits for
825 a channel; this encapsulates and abstracts the queue logic and
826 circuit selection policy, and allows the latter to be overridden
827 easily by switching out a policy object. The existing EWMA behavior
828 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
830 o New build requirements:
831 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
832 strongly recommended.
833 - Tor maintainers now require Automake version 1.9 or later to build
834 Tor from the Git repository. (Automake is not required when building
835 from a source distribution.)
837 o Minor features (protocol):
838 - No longer include the "opt" prefix when generating routerinfos
839 or v2 directories: it has been needless since Tor 0.1.2. Closes
841 - Reject EXTEND cells sent to nonexistent streams. According to the
842 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
843 we were only checking for stream IDs that were currently in use.
844 Found while hunting for more instances of bug 6271. Bugfix on
845 0.0.2pre8, which introduced incremental circuit construction.
846 - Tor relays and clients now support a better CREATE/EXTEND cell
847 format, allowing the sender to specify multiple address, identity,
848 and handshake types. Implements Robert Ransom's proposal 200;
850 - Reject as invalid most directory objects containing a NUL.
851 Belt-and-suspender fix for bug 8037.
853 o Minor features (security):
854 - Clear keys and key-derived material left on the stack in
855 rendservice.c and rendclient.c. Check return value of
856 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
857 These fixes should make us more forward-secure against cold-boot
858 attacks and the like. Fixes bug 2385.
859 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
860 Irix's random() only return 15 bits; Solaris's random() returns more
861 bits but its RAND_MAX says it only returns 15, and so on. Motivated
862 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
864 o Minor features (control protocol):
865 - Add a "GETINFO signal/names" control port command. Implements
867 - Provide default values for all options via "GETINFO config/defaults".
868 Implements ticket 4971.
869 - Allow an optional $ before the node identity digest in the
870 controller command GETINFO ns/id/<identity>, for consistency with
871 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
872 - Add CACHED keyword to ADDRMAP events in the control protocol
873 to indicate whether a DNS result will be cached or not. Resolves
875 - Generate bootstrapping status update events correctly when fetching
876 microdescriptors. Fixes bug 9927.
878 o Minor features (path selection):
879 - When deciding whether we have enough descriptors to build circuits,
880 instead of looking at raw relay counts, look at which fraction
881 of (bandwidth-weighted) paths we're able to build. This approach
882 keeps clients from building circuits if their paths are likely to
883 stand out statistically. The default fraction of paths needed is
884 taken from the consensus directory; you can override it with the
885 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
886 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
887 and we have GeoIP information, also exclude all nodes with unknown
888 countries "??" and "A1". This behavior is controlled by the
889 new GeoIPExcludeUnknown option: you can make such nodes always
890 excluded with "GeoIPExcludeUnknown 1", and disable the feature
891 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
892 gets you the default behavior. Implements feature 7706.
894 o Minor features (hidden services):
895 - Improve circuit build timeout handling for hidden services.
896 In particular: adjust build timeouts more accurately depending
897 upon the number of hop-RTTs that a particular circuit type
898 undergoes. Additionally, launch intro circuits in parallel
899 if they timeout, and take the first one to reply as valid.
900 - The Tor client now ignores sub-domain components of a .onion
901 address. This change makes HTTP "virtual" hosting
902 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
903 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
904 hosted on the same hidden service. Implements proposal 204.
905 - Enable Tor to read configuration, state, and key information from
906 a FIFO. Previously Tor would only read from files with a positive
907 stat.st_size. Code from meejah; fixes bug 6044.
909 o Minor features (clients):
910 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
911 microdescriptor-related dir requests, and only fall back to normal
912 descriptors if none of their bridges can handle microdescriptors
913 (as opposed to the fix in ticket 4013, which caused them to fall
914 back to normal descriptors if *any* of their bridges preferred
915 them). Resolves ticket 4994.
916 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
917 TCP ports to forward. In the past it only accepted two ports:
918 the ORPort and the DirPort.
920 o Minor features (protecting client timestamps):
921 - Clients no longer send timestamps in their NETINFO cells. These were
922 not used for anything, and they provided one small way for clients
923 to be distinguished from each other as they moved from network to
924 network or behind NAT. Implements part of proposal 222.
925 - Clients now round timestamps in INTRODUCE cells down to the nearest
926 10 minutes. If a new Support022HiddenServices option is set to 0, or
927 if it's set to "auto" and the feature is disabled in the consensus,
928 the timestamp is sent as 0 instead. Implements part of proposal 222.
929 - Stop sending timestamps in AUTHENTICATE cells. This is not such
930 a big deal from a security point of view, but it achieves no actual
931 good purpose, and isn't needed. Implements part of proposal 222.
932 - Reduce down accuracy of timestamps in hidden service descriptors.
933 Implements part of proposal 222.
935 o Minor features (bridges):
936 - Make bridge relays check once a minute for whether their IP
937 address has changed, rather than only every 15 minutes. Resolves
939 - Bridge statistics now count bridge clients connecting over IPv6:
940 bridge statistics files now list "bridge-ip-versions" and
941 extra-info documents list "geoip6-db-digest". The control protocol
942 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
943 implementation by "shkoo", addressing ticket 5055.
944 - Add a new torrc option "ServerTransportListenAddr" to let bridge
945 operators select the address where their pluggable transports will
946 listen for connections. Resolves ticket 7013.
947 - Randomize the lifetime of our SSL link certificate, so censors can't
948 use the static value for filtering Tor flows. Resolves ticket 8443;
949 related to ticket 4014 which was included in 0.2.2.33.
951 o Minor features (relays):
952 - Option OutboundBindAddress can be specified multiple times and
953 accepts IPv6 addresses. Resolves ticket 6876.
955 o Minor features (IPv6, client side):
956 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
957 prefer to hand out virtual IPv6 addresses, since there are more of
958 them and we can't run out. To override this behavior and make IPv4
959 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
960 or DNSPort you're using for resolving. Implements ticket 7571.
961 - AutomapHostsOnResolve responses are now randomized, to avoid
962 annoying situations where Tor is restarted and applications
963 connect to the wrong addresses.
964 - Never try more than 1000 times to pick a new virtual address when
965 AutomapHostsOnResolve is set. That's good enough so long as we
966 aren't close to handing out our entire virtual address space;
967 if you're getting there, it's best to switch to IPv6 virtual
970 o Minor features (IPv6, relay/authority side):
971 - New config option "AuthDirHasIPv6Connectivity 1" that directory
972 authorities should set if they have IPv6 connectivity and want to
973 do reachability tests for IPv6 relays. Implements feature 5974.
974 - A relay with an IPv6 OR port now sends that address in NETINFO
975 cells (in addition to its other address). Implements ticket 6364.
977 o Minor features (directory authorities):
978 - Directory authorities no long accept descriptors for any version of
979 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
980 These versions are insecure, unsupported, or both. Implements
982 - When directory authorities are computing thresholds for flags,
983 never let the threshold for the Fast flag fall below 4096
984 bytes. Also, do not consider nodes with extremely low bandwidths
985 when deciding thresholds for various directory flags. This change
986 should raise our threshold for Fast relays, possibly in turn
987 improving overall network performance; see ticket 1854. Resolves
989 - Directory authorities now include inside each vote a statement of
990 the performance thresholds they used when assigning flags.
991 Implements ticket 8151.
992 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
993 in directory authority votes to describe whether they have enough
994 measured bandwidths to ignore advertised (relay descriptor)
995 bandwidth claims. Resolves ticket 8711.
997 o Minor features (path bias detection):
998 - Path Use Bias: Perform separate accounting for successful circuit
999 use. Keep separate statistics on stream attempt rates versus stream
1000 success rates for each guard. Provide configurable thresholds to
1001 determine when to emit log messages or disable use of guards that
1002 fail too many stream attempts. Resolves ticket 7802.
1003 - Create three levels of Path Bias log messages, as opposed to just
1004 two. These are configurable via consensus as well as via the torrc
1005 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
1006 The default values are 0.70, 0.50, and 0.30 respectively.
1007 - Separate the log message levels from the decision to drop guards,
1008 which also is available via torrc option PathBiasDropGuards.
1009 PathBiasDropGuards still defaults to 0 (off).
1010 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1011 in combination with PathBiasExtremeRate.
1012 - Increase the default values for PathBiasScaleThreshold and
1013 PathBiasCircThreshold from (200, 20) to (300, 150).
1014 - Add in circuit usage accounting to path bias. If we try to use a
1015 built circuit but fail for any reason, it counts as path bias.
1016 Certain classes of circuits where the adversary gets to pick your
1017 destination node are exempt from this accounting. Usage accounting
1018 can be specifically disabled via consensus parameter or torrc.
1019 - Convert all internal path bias state to double-precision floating
1020 point, to avoid roundoff error and other issues.
1021 - Only record path bias information for circuits that have completed
1022 *two* hops. Assuming end-to-end tagging is the attack vector, this
1023 makes us more resilient to ambient circuit failure without any
1024 detection capability loss.
1026 o Minor features (build):
1027 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1028 dhill. Resolves ticket 6982.
1029 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1031 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
1032 separate error codes; or at least, don't break for that reason.
1033 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
1035 o Build improvements (autotools):
1036 - Warn if building on a platform with an unsigned time_t: there
1037 are too many places where Tor currently assumes that time_t can
1038 hold negative values. We'd like to fix them all, but probably
1040 - Do not report status verbosely from autogen.sh unless the -v flag
1041 is specified. Fixes issue 4664. Patch from Onizuka.
1042 - Detect and reject attempts to build Tor with threading support
1043 when OpenSSL has been compiled without threading support.
1045 - Try to detect if we are ever building on a platform where
1046 memset(...,0,...) does not set the value of a double to 0.0. Such
1047 platforms are permitted by the C standard, though in practice
1048 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
1049 currently support them, but it's better to detect them and fail
1050 than to perform erroneously.
1051 - We no longer warn so much when generating manpages from their
1053 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
1054 the signs of types during autoconf. This is better than our old
1055 approach, which didn't work when cross-compiling.
1057 o Minor features (log messages, warnings):
1058 - Detect when we're running with a version of OpenSSL other than the
1059 one we compiled with. This conflict has occasionally given people
1060 hard-to-track-down errors.
1061 - Warn users who run hidden services on a Tor client with
1062 UseEntryGuards disabled that their hidden services will be
1063 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1064 attack which motivated Tor to support entry guards in the first
1065 place). Resolves ticket 6889.
1066 - Warn when we are binding low ports when hibernation is enabled;
1067 previously we had warned when we were _advertising_ low ports with
1068 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1069 - Issue a warning when running with the bufferevents backend enabled.
1070 It's still not stable, and people should know that they're likely
1071 to hit unexpected problems. Closes ticket 9147.
1073 o Minor features (log messages, notices):
1074 - Refactor resolve_my_address() so it returns the method by which we
1075 decided our public IP address (explicitly configured, resolved from
1076 explicit hostname, guessed from interfaces, learned by gethostname).
1077 Now we can provide more helpful log messages when a relay guesses
1078 its IP address incorrectly (e.g. due to unexpected lines in
1079 /etc/hosts). Resolves ticket 2267.
1080 - Track how many "TAP" and "NTor" circuit handshake requests we get,
1081 and how many we complete, and log it every hour to help relay
1082 operators follow trends in network load. Addresses ticket 9658.
1084 o Minor features (log messages, diagnostics):
1085 - If we fail to free a microdescriptor because of bug 7164, log
1086 the filename and line number from which we tried to free it.
1087 - We compute the overhead from passing onionskins back and forth to
1088 cpuworkers, and report it when dumping statistics in response to
1089 SIGUSR1. Supports ticket 7291.
1090 - Add another diagnostic to the heartbeat message: track and log
1091 overhead that TLS is adding to the data we write. If this is
1092 high, we are sending too little data to SSL_write at a time.
1093 Diagnostic for bug 7707.
1094 - Log packaged cell fullness as part of the heartbeat message.
1095 Diagnosis to try to determine the extent of bug 7743.
1096 - Add more detail to a log message about relaxed timeouts, to help
1098 - When learning a fingerprint for a bridge, log its corresponding
1099 transport type. Implements ticket 7896.
1100 - Warn more aggressively when flushing microdescriptors to a
1101 microdescriptor cache fails, in an attempt to mitigate bug 8031,
1102 or at least make it more diagnosable.
1103 - Improve the log message when "Bug/attack: unexpected sendme cell
1104 from client" occurs, to help us track bug 8093.
1105 - Improve debugging output to help track down bug 8185 ("Bug:
1106 outgoing relay cell has n_chan==NULL. Dropping.")
1108 o Minor features (log messages, quieter bootstrapping):
1109 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1110 versions and capabilities when everything is going right. Resolves
1111 part of ticket 6736.
1112 - Omit the first heartbeat log message, because it never has anything
1113 useful to say, and it clutters up the bootstrapping messages.
1114 Resolves ticket 6758.
1115 - Don't log about reloading the microdescriptor cache at startup. Our
1116 bootstrap warnings are supposed to tell the user when there's a
1117 problem, and our bootstrap notices say when there isn't. Resolves
1118 ticket 6759; bugfix on 0.2.2.6-alpha.
1119 - Don't log "I learned some more directory information" when we're
1120 reading cached directory information. Reserve it for when new
1121 directory information arrives in response to a fetch. Resolves
1123 - Don't complain about bootstrapping problems while hibernating.
1124 These complaints reflect a general code problem, but not one
1125 with any problematic effects (no connections are actually
1126 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
1128 o Minor features (testing):
1129 - In our testsuite, create temporary directories with a bit more
1130 entropy in their name to make name collisions less likely. Fixes
1132 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
1133 (P-256) Diffie-Hellman handshakes to src/or/bench.
1134 - Add benchmark functions to test onion handshake performance.
1137 - The DirServer option is now DirAuthority, for consistency with
1138 current naming patterns. You can still use the old DirServer form.
1140 o Minor bugfixes (protocol):
1141 - Fix the handling of a TRUNCATE cell when it arrives while the
1142 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
1143 - When a Tor client gets a "truncated" relay cell, the first byte of
1144 its payload specifies why the circuit was truncated. We were
1145 ignoring this 'reason' byte when tearing down the circuit, resulting
1146 in the controller not being told why the circuit closed. Now we
1147 pass the reason from the truncated cell to the controller. Bugfix
1148 on 0.1.2.3-alpha; fixes bug 7039.
1149 - Fix a misframing issue when reading the version numbers in a
1150 VERSIONS cell. Previously we would recognize [00 01 00 02] as
1151 'version 1, version 2, and version 0x100', when it should have
1152 only included versions 1 and 2. Fixes bug 8059; bugfix on
1153 0.2.0.10-alpha. Reported pseudonymously.
1154 - Make the format and order of STREAM events for DNS lookups
1155 consistent among the various ways to launch DNS lookups. Fixes
1156 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
1158 o Minor bugfixes (syscalls and disk interaction):
1159 - Always check the return values of functions fcntl() and
1160 setsockopt(). We don't believe these are ever actually failing in
1161 practice, but better safe than sorry. Also, checking these return
1162 values should please analysis tools like Coverity. Patch from
1163 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
1164 - Avoid double-closing the listener socket in our socketpair()
1165 replacement (used on Windows) in the case where the addresses on
1166 our opened sockets don't match what we expected. Fixes bug 9400;
1167 bugfix on 0.0.2pre7. Found by Coverity.
1168 - Correctly store microdescriptors and extrainfo descriptors that
1169 include an internal NUL byte. Fixes bug 8037; bugfix on
1170 0.2.0.1-alpha. Bug reported by "cypherpunks".
1171 - If for some reason we fail to write a microdescriptor while
1172 rebuilding the cache, do not let the annotations from that
1173 microdescriptor linger in the cache file, and do not let the
1174 microdescriptor stay recorded as present in its old location.
1175 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
1176 - Use direct writes rather than stdio when building microdescriptor
1177 caches, in an attempt to mitigate bug 8031, or at least make it
1180 o Minor fixes (config options):
1181 - Warn and fail if a server is configured not to advertise any
1182 ORPorts at all. (We need *something* to put in our descriptor,
1183 or we just won't work.)
1184 - Behave correctly when the user disables LearnCircuitBuildTimeout
1185 but doesn't tell us what they would like the timeout to be. Fixes
1186 bug 6304; bugfix on 0.2.2.14-alpha.
1187 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1188 to start with a triple-underscore so the controller won't touch it.
1189 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1190 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1191 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1192 - When autodetecting the number of CPUs, use the number of available
1193 CPUs in preference to the number of configured CPUs. Inform the
1194 user if this reduces the number of available CPUs. Fixes bug 8002;
1195 bugfix on 0.2.3.1-alpha.
1196 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1197 - Make it an error when you set EntryNodes but disable UseGuardNodes,
1198 since it will (surprisingly to some users) ignore EntryNodes. Fixes
1199 bug 8180; bugfix on 0.2.3.11-alpha.
1200 - Avoid overflows when the user sets MaxCircuitDirtiness to a
1201 ridiculously high value, by imposing a (ridiculously high) 30-day
1202 maximum on MaxCircuitDirtiness.
1204 o Minor bugfixes (control protocol):
1205 - Stop sending a stray "(null)" in some cases for the server status
1206 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
1208 - The ADDRMAP command can no longer generate an ill-formed error
1209 code on a failed MAPADDRESS. It now says "internal" rather than
1210 an English sentence fragment with spaces in the middle. Bugfix on
1213 o Minor bugfixes (clients / edges):
1214 - When we receive a RELAY_END cell with the reason DONE, or with no
1215 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
1216 status as "connection refused". Previously we reported these cases
1217 as success but then immediately closed the connection. Fixes bug
1218 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
1219 - If the guard we choose first doesn't answer, we would try the
1220 second guard, but once we connected to the second guard we would
1221 abandon it and retry the first one, slowing down bootstrapping.
1222 The fix is to treat all our initially chosen guards as acceptable
1223 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
1224 - When choosing which stream on a formerly stalled circuit to wake
1225 first, make better use of the platform's weak RNG. Previously,
1226 we had been using the % ("modulo") operator to try to generate a
1227 1/N chance of picking each stream, but this behaves badly with
1228 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
1231 o Minor bugfixes (path bias detection):
1232 - If the state file's path bias counts are invalid (presumably from a
1233 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
1234 additional checks and log messages to the scaling of Path Bias
1235 counts, in case there still are remaining issues with scaling.
1236 Should help resolve bug 8235.
1237 - Prevent rounding error in path bias counts when scaling
1238 them down, and use the correct scale factor default. Also demote
1239 some path bias related log messages down a level and make others
1240 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
1241 - Remove a source of rounding error during path bias count scaling;
1242 don't count cannibalized circuits as used for path bias until we
1243 actually try to use them; and fix a circuit_package_relay_cell()
1244 warning message about n_chan==NULL. Fixes bug 7802.
1245 - Paste the description for PathBias parameters from the man
1246 page into or.h, so the code documents them too. Fixes bug 7982;
1247 bugfix on 0.2.3.17-beta.
1249 o Minor bugfixes (relays):
1250 - Stop trying to resolve our hostname so often (e.g. every time we
1251 think about doing a directory fetch). Now we reuse the cached
1252 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
1253 and 2410 (bugfix on 0.1.2.2-alpha).
1254 - When examining the list of network interfaces to find our address,
1255 do not consider non-running or disabled network interfaces. Fixes
1256 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
1258 o Minor bugfixes (blocking resistance):
1259 - Only disable TLS session ticket support when running as a TLS
1260 server. Now clients will blend better with regular Firefox
1261 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1263 o Minor bugfixes (IPv6):
1264 - Use square brackets around IPv6 addresses in numerous places
1265 that needed them, including log messages, HTTPS CONNECT proxy
1266 requests, TransportProxy statefile entries, and pluggable transport
1267 extra-info lines. Fixes bug 7011; patch by David Fifield.
1269 o Minor bugfixes (directory authorities):
1270 - Reject consensus votes with more than 64 known-flags. We aren't even
1271 close to that limit yet, and our code doesn't handle it correctly.
1272 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1273 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1274 bugfix on 0.2.0.3-alpha.
1276 o Minor bugfixes (memory leaks):
1277 - Avoid leaking memory if we fail to compute a consensus signature
1278 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
1279 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
1280 on 0.2.1.1-alpha; fixes bug 7816.
1281 - Fix a memory leak during safe-cookie controller authentication.
1282 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
1283 - Free some more still-in-use memory at exit, to make hunting for
1284 memory leaks easier. Resolves bug 7029.
1286 o Minor bugfixes (code correctness):
1287 - Increase the width of the field used to remember a connection's
1288 link protocol version to two bytes. Harmless for now, since the
1289 only currently recognized versions are one byte long. Reported
1290 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
1291 - Fix a crash when debugging unit tests on Windows: deallocate a
1292 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1293 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1294 - When detecting the largest possible file descriptor (in order to
1295 close all file descriptors when launching a new program), actually
1296 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
1297 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
1299 - Avoid a crash if we fail to generate an extrainfo descriptor.
1300 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
1302 - Avoid an off-by-one error when checking buffer boundaries when
1303 formatting the exit status of a pluggable transport helper.
1304 This is probably not an exploitable bug, but better safe than
1305 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
1307 - Get rid of a couple of harmless clang warnings, where we compared
1308 enums to ints. These warnings are newly introduced in clang 3.2.
1310 o Minor bugfixes (code cleanliness):
1311 - Avoid use of reserved identifiers in our C code. The C standard
1312 doesn't like us declaring anything that starts with an
1313 underscore, so let's knock it off before we get in trouble. Fix
1314 for bug 1031; bugfix on the first Tor commit.
1315 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1316 with large values. This situation was untriggered, but nevertheless
1317 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1318 - Fix an impossible buffer overrun in the AES unit tests. Fixes
1319 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
1320 - Fix handling of rendezvous client authorization types over 8.
1321 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1322 - Remove a couple of extraneous semicolons that were upsetting the
1323 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
1324 bugfix on 0.2.2.1-alpha.
1325 - When complaining about a client port on a public address, log
1326 which address we're complaining about. Fixes bug 4020; bugfix on
1327 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1329 o Minor bugfixes (log messages, warnings):
1330 - If we encounter a write failure on a SOCKS connection before we
1331 finish our SOCKS handshake, don't warn that we closed the
1332 connection before we could send a SOCKS reply. Fixes bug 8427;
1333 bugfix on 0.1.0.1-rc.
1334 - Fix a directory authority warn caused when we have a large amount
1335 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
1336 - Downgrade "Failed to hand off onionskin" messages to "debug"
1337 severity, since they're typically redundant with the "Your computer
1338 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1339 - Avoid spurious warnings when configuring multiple client ports of
1340 which only some are nonlocal. Previously, we had claimed that some
1341 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
1344 o Minor bugfixes (log messages, other):
1345 - Fix log messages and comments to avoid saying "GMT" when we mean
1346 "UTC". Fixes bug 6113.
1347 - When rejecting a configuration because we were unable to parse a
1348 quoted string, log an actual error message. Fixes bug 7950; bugfix
1350 - Correctly recognize that [::1] is a loopback address. Fixes
1351 bug 8377; bugfix on 0.2.1.3-alpha.
1352 - Don't log inappropriate heartbeat messages when hibernating: a
1353 hibernating node is _expected_ to drop out of the consensus,
1354 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
1355 bugfix on 0.2.3.1-alpha.
1356 - Eliminate several instances where we use "Nickname=ID" to refer to
1357 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
1358 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
1361 o Minor bugfixes (build):
1362 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
1363 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
1364 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
1366 o Documentation fixes:
1367 - Make the torify manpage no longer refer to tsocks; torify hasn't
1368 supported tsocks since 0.2.3.14-alpha.
1369 - Make the tor manpage no longer reference tsocks.
1370 - Fix the GeoIPExcludeUnknown documentation to refer to
1371 ExcludeExitNodes rather than the currently nonexistent
1372 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
1373 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1375 - Say "KBytes" rather than "KB" in the man page (for various values
1376 of K), to further reduce confusion about whether Tor counts in
1377 units of memory or fractions of units of memory. Resolves ticket 7054.
1378 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
1379 names match. Fixes bug 7768.
1380 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
1381 message is logged at notice, not at info.
1382 - Clarify the usage and risks of setting the ContactInfo torrc line
1383 for your relay or bridge. Resolves ticket 9854.
1384 - Add anchors to the manpage so we can link to the html version of
1385 the documentation for specific options. Resolves ticket 9866.
1386 - Replace remaining references to DirServer in man page and
1387 log entries. Resolves ticket 10124.
1390 - Stop exporting estimates of v2 and v3 directory traffic shares
1391 in extrainfo documents. They were unneeded and sometimes inaccurate.
1392 Also stop exporting any v2 directory request statistics. Resolves
1394 - Drop support for detecting and warning about versions of Libevent
1395 before 1.3e. Nothing reasonable ships with them any longer; warning
1396 the user about them shouldn't be needed. Resolves ticket 6826.
1397 - Now that all versions before 0.2.2.x are disallowed, we no longer
1398 need to work around their missing features. Remove a bunch of
1402 - The tor-tsocks.conf is no longer distributed or installed. We
1403 recommend that tsocks users use torsocks instead. Resolves
1405 - Remove some of the older contents of doc/ as obsolete; move others
1406 to torspec.git. Fixes bug 8965.
1408 o Code simplification:
1409 - Avoid using character buffers when constructing most directory
1410 objects: this approach was unwieldy and error-prone. Instead,
1411 build smartlists of strings, and concatenate them when done.
1412 - Rename "isin" functions to "contains", for grammar. Resolves
1414 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
1415 with the natural logarithm function from the system libm. Resolves
1417 - Start using OpenBSD's implementation of queue.h, so that we don't
1418 need to hand-roll our own pointer and list structures whenever we
1419 need them. (We can't rely on a sys/queue.h, since some operating
1420 systems don't have them, and the ones that do have them don't all
1421 present the same extensions.)
1422 - Start using OpenBSD's implementation of queue.h (originally by
1424 - Enhance our internal sscanf replacement so that we can eliminate
1425 the last remaining uses of the system sscanf. (Though those uses
1426 of sscanf were safe, sscanf itself is generally error prone, so
1427 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1429 - Replace all calls to snprintf() outside of src/ext with
1430 tor_snprintf(). Also remove the #define to replace snprintf with
1431 _snprintf on Windows; they have different semantics, and all of
1432 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
1435 - Add a wrapper function for the common "log a message with a
1437 - Split the onion.c file into separate modules for the onion queue
1438 and the different handshakes it supports.
1439 - Move the client-side address-map/virtual-address/DNS-cache code
1440 out of connection_edge.c into a new addressmap.c module.
1441 - Move the entry node code from circuitbuild.c to its own file.
1442 - Move the circuit build timeout tracking code from circuitbuild.c
1444 - Source files taken from other packages now reside in src/ext;
1445 previously they were scattered around the rest of Tor.
1446 - Move the generic "config" code into a new file, and have "config.c"
1447 hold only torrc- and state-related code. Resolves ticket 6823.
1448 - Move the core of our "choose a weighted element at random" logic
1449 into its own function, and give it unit tests. Now the logic is
1450 testable, and a little less fragile too.
1451 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1452 - Move last_reachable and testing_since from routerinfo_t to node_t.
1453 Implements ticket 5529.
1454 - Add replaycache_t structure, functions and unit tests, then refactor
1455 rend_service_introduce() to be more clear to read, improve, debug,
1456 and test. Resolves bug 6177.
1459 - Remove some now-needless code that tried to aggressively flush
1460 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1461 cell queue logic has saved us from the failure mode that this code
1462 was supposed to prevent. Removing this code will limit the number
1463 of baroque control flow paths through Tor's network logic. Reported
1464 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1465 - Remove unused code for parsing v1 directories and "running routers"
1466 documents. Fixes bug 6887.
1467 - Remove the marshalling/unmarshalling code for sending requests to
1468 cpuworkers over a socket, and instead just send structs. The
1469 recipient will always be the same Tor binary as the sender, so
1470 any encoding is overkill.
1471 - Remove the testing_since field of node_t, which hasn't been used
1472 for anything since 0.2.0.9-alpha.
1473 - Finally remove support for malloc_good_size and malloc_usable_size.
1474 We had hoped that these functions would let us eke a little more
1475 memory out of our malloc implementation. Unfortunately, the only
1476 implementations that provided these functions are also ones that
1477 are already efficient about not overallocation: they never got us
1478 more than 7 or so bytes per allocation. Removing them saves us a
1479 little code complexity and a nontrivial amount of build complexity.
1482 Changes in version 0.2.3.25 - 2012-11-19
1483 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1484 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1485 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1486 programmer, and friend. Unstinting in his dedication to the cause of
1487 freedom, he inspired and helped many of us as we began our work on
1488 anonymity, and inspires us still. Please honor his memory by writing
1489 software to protect people's freedoms, and by helping others to do so.
1491 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1492 significantly reduced directory overhead (via microdescriptors),
1493 enormous crypto performance improvements for fast relays on new
1494 enough hardware, a new v3 TLS handshake protocol that can better
1495 resist fingerprinting, support for protocol obfuscation plugins (aka
1496 pluggable transports), better scalability for hidden services, IPv6
1497 support for bridges, performance improvements like allowing clients
1498 to skip the first round-trip on the circuit ("optimistic data") and
1499 refilling token buckets more often, a new "stream isolation" design
1500 to isolate different applications on different circuits, and many
1501 stability, security, and privacy fixes.
1503 Major features (v3 directory protocol):
1504 - Clients now use microdescriptors instead of regular descriptors
1505 to build circuits. Microdescriptors are authority-generated
1506 summaries of regular descriptors' contents, designed to change very
1507 rarely (see proposal 158 for details). This feature is designed
1508 to save bandwidth, especially for clients on slow internet
1509 connections. Use "UseMicrodescriptors 0" to disable it.
1510 - Caches now download, cache, and serve microdescriptors, as well
1511 as multiple "flavors" of the consensus, including a flavor that
1512 describes microdescriptors.
1514 o Major features (build hardening):
1515 - Enable gcc and ld hardening by default. Resolves ticket 5210.
1517 o Major features (relay scaling):
1518 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
1519 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
1520 vectorized AES implementations as appropriate. These can be much,
1521 much faster than other AES implementations.
1522 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1523 implementation. It makes AES_CTR about 7% faster than our old one
1524 (which was about 10% faster than the one OpenSSL used to provide).
1525 Resolves ticket 4526.
1526 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1527 operations can use hardware acceleration (if present). Resolves
1529 - Unconditionally use OpenSSL's AES implementation instead of our
1530 old built-in one. OpenSSL's AES has been better for a while, and
1531 relatively few servers should still be on any version of OpenSSL
1532 that doesn't have good optimized assembly AES.
1534 o Major features (blocking resistance):
1535 - Update TLS cipher list to match Firefox 8 and later. Resolves
1537 - Remove support for clients falsely claiming to support standard
1538 ciphersuites that they can actually provide. As of modern OpenSSL
1539 versions, it's not necessary to fake any standard ciphersuite,
1540 and doing so prevents us from using better ciphersuites in the
1541 future, since servers can't know whether an advertised ciphersuite
1542 is really supported or not. Some hosts -- notably, ones with very
1543 old versions of OpenSSL or where OpenSSL has been built with ECC
1544 disabled -- will stand out because of this change; TBB users should
1545 not be affected. Implements the client side of proposal 198.
1546 - Implement a new handshake protocol (v3) for authenticating Tors to
1547 each other over TLS. It should be more resistant to fingerprinting
1548 than previous protocols, and should require less TLS hacking for
1549 future Tor implementations. Implements proposal 176.
1550 - Allow variable-length padding cells, to disguise the length of
1551 Tor's TLS records. Implements part of proposal 184.
1552 - While we're trying to bootstrap, record how many TLS connections
1553 fail in each state, and report which states saw the most failures
1554 in response to any bootstrap failures. This feature may speed up
1555 diagnosis of censorship events. Implements ticket 3116.
1557 o Major features (pluggable transports):
1558 - Clients and bridges can now be configured to use a separate
1559 "transport" proxy. This approach makes the censorship arms race
1560 easier by allowing bridges to use protocol obfuscation plugins.
1561 Implements proposal 180 (tickets 2841 and 3472).
1563 o Major features (DoS resistance):
1564 - Now that Tor 0.2.0.x is completely deprecated, enable the final
1565 part of "Proposal 110: Avoiding infinite length circuits" by
1566 refusing all circuit-extend requests that do not use a relay_early
1567 cell. This change helps Tor resist a class of denial-of-service
1568 attacks by limiting the maximum circuit length.
1569 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1570 could use this trick to make their circuits receive cells faster
1571 than our flow control would have allowed, or to gum up the network,
1572 or possibly to do targeted memory denial-of-service attacks on
1573 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1574 from July 2002, before the release of Tor 0.0.0.
1576 o Major features (hidden services):
1577 - Adjust the number of introduction points that a hidden service
1578 will try to maintain based on how long its introduction points
1579 remain in use and how many introductions they handle. Fixes
1581 - Add a "tor2web mode" for clients that want to connect to hidden
1582 services non-anonymously (and possibly more quickly). As a safety
1583 measure to try to keep users from turning this on without knowing
1584 what they are doing, tor2web mode must be explicitly enabled at
1585 compile time, and a copy of Tor compiled to run in tor2web mode
1586 cannot be used as a normal Tor client. Implements feature 2553.
1588 o Major features (IPv6):
1589 - Clients can now connect to private bridges over IPv6. Bridges
1590 still need at least one IPv4 address in order to connect to
1591 other relays. Note that we don't yet handle the case where the
1592 user has two bridge lines for the same bridge (one IPv4, one
1593 IPv6). Implements parts of proposal 186.
1595 o Major features (directory authorities):
1596 - Use a more secure consensus parameter voting algorithm. Now at
1597 least three directory authorities or a majority of them must
1598 vote on a given parameter before it will be included in the
1599 consensus. Implements proposal 178.
1600 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1601 flag. In the past few years the average relay speed has picked
1602 up, and while the "top 7/8 of the network get the Fast flag" and
1603 "all relays with 20KB or more of capacity get the Fast flag" rules
1604 used to have the same result, now the top 7/8 of the network has
1605 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1607 o Major features (performance):
1608 - Exit nodes now accept and queue data on not-yet-connected streams.
1609 Previously, the client wasn't allowed to send data until the
1610 stream was connected, which slowed down all connections. This
1611 change will enable clients to perform a "fast-start" on streams
1612 and send data without having to wait for a confirmation that the
1613 stream has opened. Patch from Ian Goldberg; implements the server
1614 side of Proposal 174.
1615 - When using an exit relay running 0.2.3.x, clients can now
1616 "optimistically" send data before the exit relay reports that
1617 the stream has opened. This saves a round trip when starting
1618 connections where the client speaks first (such as web browsing).
1619 This behavior is controlled by a consensus parameter (currently
1620 disabled). To turn it on or off manually, use the "OptimisticData"
1621 torrc option. Implements proposal 181; code by Ian Goldberg.
1622 - Add a new TokenBucketRefillInterval option to refill token buckets
1623 more frequently than once per second. This should improve network
1624 performance, alleviate queueing problems, and make traffic less
1625 bursty. Implements proposal 183; closes ticket 3630. Design by
1626 Florian Tschorsch and Björn Scheuermann; implementation by
1628 - Raise the threshold of server descriptors needed (75%) and exit
1629 server descriptors needed (50%) before we will declare ourselves
1630 bootstrapped. This will make clients start building circuits a
1631 little later, but makes the initially constructed circuits less
1632 skewed and less in conflict with further directory fetches. Fixes
1635 o Major features (relays):
1636 - Relays now try regenerating and uploading their descriptor more
1637 frequently if they are not listed in the consensus, or if the
1638 version of their descriptor listed in the consensus is too
1639 old. This fix should prevent situations where a server declines
1640 to re-publish itself because it has done so too recently, even
1641 though the authorities decided not to list its recent-enough
1642 descriptor. Fix for bug 3327.
1644 o Major features (stream isolation):
1645 - You can now configure Tor so that streams from different
1646 applications are isolated on different circuits, to prevent an
1647 attacker who sees your streams as they leave an exit node from
1648 linking your sessions to one another. To do this, choose some way
1649 to distinguish the applications: have them connect to different
1650 SocksPorts, or have one of them use SOCKS4 while the other uses
1651 SOCKS5, or have them pass different authentication strings to the
1652 SOCKS proxy. Then, use the new SocksPort syntax to configure the
1653 degree of isolation you need. This implements Proposal 171.
1654 - There's a new syntax for specifying multiple client ports (such as
1655 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
1656 multiple *Port entries with full addr:port syntax on each.
1657 The old *ListenAddress format is still supported, but you can't
1658 mix it with the new *Port syntax.
1660 o Major features (bufferevents):
1661 - Tor can now optionally build with the "bufferevents" buffered IO
1662 backend provided by Libevent 2. To use this feature, make sure you
1663 have the latest possible version of Libevent, and pass the
1664 --enable-bufferevents flag to configure when building Tor from
1665 source. This feature will make our networking code more flexible,
1666 let us stack layers on each other, and let us use more efficient
1667 zero-copy transports where available.
1668 - Add experimental support for running on Windows with IOCP and no
1669 kernel-space socket buffers. This feature is controlled by a new
1670 "UserspaceIOCPBuffers" config option (off by default), which has
1671 no effect unless Tor has been built with bufferevents enabled,
1672 you're running on Windows, and you've set "DisableIOCP 0". In the
1673 long run, this may help solve or mitigate bug 98.
1675 o Major features (path selection):
1676 - The EntryNodes option can now include country codes like {de} or IP
1677 addresses or network masks. Previously we had disallowed these
1678 options because we didn't have an efficient way to keep the list up
1679 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
1682 o Major features (port forwarding):
1683 - Add support for automatic port mapping on the many home routers
1684 that support NAT-PMP or UPnP. To build the support code, you'll
1685 need to have the libnatpnp library and/or the libminiupnpc library,
1686 and you'll need to enable the feature specifically by passing
1687 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
1688 it on, use the new PortForwarding option.
1690 o Major features (logging):
1691 - Add a new 'Heartbeat' log message type to periodically log a message
1692 describing Tor's status at level Notice. This feature is meant for
1693 operators who log at notice, and want to make sure that their Tor
1694 server is still working. Implementation by George Kadianakis.
1695 - Make logging resolution configurable with a new LogTimeGranularity
1696 option, and change the default from 1 millisecond to 1 second.
1697 Implements enhancement 1668.
1699 o Major features (other):
1700 - New "DisableNetwork" config option to prevent Tor from launching any
1701 connections or accepting any connections except on a control port.
1702 Bundles and controllers can set this option before letting Tor talk
1703 to the rest of the network, for example to prevent any connections
1704 to a non-bridge address. Packages like Orbot can also use this
1705 option to instruct Tor to save power when the network is off.
1706 - Try to use system facilities for enumerating local interface
1707 addresses, before falling back to our old approach (which was
1708 binding a UDP socket, and calling getsockname() on it). That
1709 approach was scaring OS X users whose draconian firewall
1710 software warned about binding to UDP sockets regardless of
1711 whether packets were sent. Now we try to use getifaddrs(),
1712 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
1713 system supports. Resolves ticket 1827.
1714 - Add experimental support for a "defaults" torrc file to be parsed
1715 before the regular torrc. Torrc options override the defaults file's
1716 options in the same way that the command line overrides the torrc.
1717 The SAVECONF controller command saves only those options which
1718 differ between the current configuration and the defaults file. HUP
1719 reloads both files. Implements task 4552.
1721 o New directory authorities:
1722 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1723 authority. Closes ticket 5749.
1725 o Security/privacy fixes:
1726 - Avoid read-from-freed-memory and double-free bugs that could occur
1727 when a DNS request fails while launching it. Fixes bug 6480;
1728 bugfix on 0.2.0.1-alpha.
1729 - Reject any attempt to extend to an internal address. Without
1730 this fix, a router could be used to probe addresses on an internal
1731 network to see whether they were accepting connections. Fixes bug
1732 6710; bugfix on 0.0.8pre1.
1733 - Close any connection that sends unrecognized junk before the TLS
1734 handshake. Solves an issue noted in bug 4369.
1735 - The advertised platform of a relay now includes only its operating
1736 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
1737 its service pack level (for Windows) or its CPU architecture
1738 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
1739 can insert an extra string in the platform line by setting the
1740 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
1741 - Disable TLS session tickets. OpenSSL's implementation was giving
1742 our TLS session keys the lifetime of our TLS context objects, when
1743 perfect forward secrecy would want us to discard anything that
1744 could decrypt a link connection as soon as the link connection
1745 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1746 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1747 - Tor tries to wipe potentially sensitive data after using it, so
1748 that if some subsequent security failure exposes Tor's memory,
1749 the damage will be limited. But we had a bug where the compiler
1750 was eliminating these wipe operations when it decided that the
1751 memory was no longer visible to a (correctly running) program,
1752 hence defeating our attempt at defense in depth. We fix that
1753 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1754 is unlikely to optimize away. Future versions of Tor may use
1755 a less ridiculously heavy approach for this. Fixes bug 7352.
1756 Reported in an article by Andrey Karpov.
1758 o Major bugfixes (crashes and asserts):
1759 - Avoid a pair of double-free and use-after-mark bugs that can
1760 occur with certain timings in canceled and re-received DNS
1761 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1762 - Fix a denial of service attack by which any directory authority
1763 could crash all the others, or by which a single v2 directory
1764 authority could crash everybody downloading v2 directory
1765 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1766 - Fix an assert that directory authorities could trigger on sighup
1767 during some configuration state transitions. We now don't treat
1768 it as a fatal error when the new descriptor we just generated in
1769 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
1770 - Avoid segfault when starting up having run with an extremely old
1771 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1774 o Major bugfixes (clients):
1775 - If we are unable to find any exit that supports our predicted ports,
1776 stop calling them predicted, so that we don't loop and build
1777 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
1778 which introduced predicted ports.
1779 - Check at each new consensus whether our entry guards were picked
1780 long enough ago that we should rotate them. Previously, we only
1781 did this check at startup, which could lead to us holding a guard
1782 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
1783 - When fetching a bridge descriptor from a bridge authority,
1784 always do so anonymously, whether we have been able to open
1785 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
1786 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
1787 but we'll need to wait for bug 6010 before it's actually usable.
1789 o Major bugfixes (directory voting):
1790 - Check more thoroughly to prevent a rogue authority from
1791 double-voting on any consensus directory parameter. Previously,
1792 authorities would crash in this case if the total number of
1793 votes for any parameter exceeded the number of active voters,
1794 but would let it pass otherwise. Partially fixes bug 5786; bugfix
1796 - When computing weight parameters, behave more robustly in the
1797 presence of a bad bwweightscale value. Previously, the authorities
1798 would crash if they agreed on a sufficiently broken weight_scale
1799 value; now, they use a reasonable default and carry on. Fixes the
1800 rest of bug 5786; bugfix on 0.2.2.17-alpha.
1801 - If authorities are unable to get a v2 consensus document from other
1802 directory authorities, they no longer fall back to fetching
1803 them from regular directory caches. Fixes bug 5635; bugfix on
1804 0.2.2.26-beta, where routers stopped downloading v2 consensus
1807 o Major bugfixes (relays):
1808 - Fix a bug handling SENDME cells on nonexistent streams that could
1809 result in bizarre window values. Report and patch contributed
1810 pseudonymously. Fixes part of bug 6271. This bug was introduced
1811 before the first Tor release, in svn commit r152.
1812 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1813 tor gets started. This prevents a wrong average bandwidth
1814 estimate, which would cause relays to always start a new accounting
1815 interval at the earliest possible moment. Fixes bug 2003; bugfix
1816 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
1817 immensely in tracking this bug down.
1818 - Fix a possible crash bug when checking for deactivated circuits
1819 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1820 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1821 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
1822 connections. This change should allow busy exit relays to stop
1823 running out of available sockets as quickly. Fixes bug 4950;
1824 bugfix on 0.2.2.26-beta.
1826 o Major bugfixes (blocking resistance):
1827 - Bridges no longer include their address in NETINFO cells on outgoing
1828 OR connections, to allow them to blend in better with clients.
1829 Removes another avenue for enumerating bridges. Reported by
1830 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1831 cells were introduced.
1832 - Warn the user when HTTPProxy, but no other proxy type, is
1833 configured. This can cause surprising behavior: it doesn't send
1834 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
1835 directory traffic only. Resolves ticket 4663.
1837 o Major bugfixes (hidden services):
1838 - Improve hidden service robustness: when an attempt to connect to
1839 a hidden service ends, be willing to refetch its hidden service
1840 descriptors from each of the HSDir relays responsible for them
1841 immediately. Previously, we would not consider refetching the
1842 service's descriptors from each HSDir for 15 minutes after the last
1843 fetch, which was inconvenient if the hidden service was not running
1844 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1845 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1846 They used to check that the timestamp was within 30 minutes
1847 of their system clock, so they could cap the size of their
1848 replay-detection cache, but that approach unnecessarily refused
1849 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1850 the v3 intro-point protocol (the first one which sent a timestamp
1851 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1852 - When one of a hidden service's introduction points appears to be
1853 unreachable, stop trying it. Previously, we would keep trying
1854 to build circuits to the introduction point until we lost the
1855 descriptor, usually because the user gave up and restarted Tor.
1856 Fixes part of bug 3825.
1858 o Changes to default torrc file:
1859 - Stop listing "socksport 9050" in torrc.sample. We open a socks
1860 port on 9050 by default anyway, so this should not change anything
1862 - Stop mentioning the deprecated *ListenAddress options in
1863 torrc.sample. Fixes bug 5438.
1864 - Document unit of bandwidth-related options in sample torrc.
1866 - Fix broken URLs in the sample torrc file, and tell readers about
1867 the OutboundBindAddress, ExitPolicyRejectPrivate, and
1868 PublishServerDescriptor options. Addresses bug 4652.
1870 o Minor features (directory authorities):
1871 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1872 change when the authority is deciding whether to accept a newly
1873 uploaded descriptor. Implements ticket 6423.
1874 - Directory authorities are now a little more lenient at accepting
1875 older router descriptors, or newer router descriptors that don't
1876 make big changes. This should help ameliorate past and future
1877 issues where routers think they have uploaded valid descriptors,
1878 but the authorities don't think so. Fix for ticket 2479.
1879 - Authority operators can now vote for all relays in a given
1880 set of countries to be BadDir/BadExit/Invalid/Rejected.
1881 - Provide two consensus parameters (FastFlagMinThreshold and
1882 FastFlagMaxThreshold) to control the range of allowable bandwidths
1883 for the Fast directory flag. These allow authorities to run
1884 experiments on appropriate requirements for being a "Fast" node.
1885 The AuthDirFastGuarantee config value still applies. Implements
1888 o Minor features (bridges / bridge authorities):
1889 - Make bridge SSL certificates a bit more stealthy by using random
1890 serial numbers, in the same fashion as OpenSSL when generating
1891 self-signed certificates. Implements ticket 4584.
1892 - Tag a bridge's descriptor as "never to be sent unencrypted".
1893 This shouldn't matter, since bridges don't open non-anonymous
1894 connections to the bridge authority and don't allow unencrypted
1895 directory connections from clients, but we might as well make
1896 sure. Closes bug 5139.
1897 - The Bridge Authority now writes statistics on how many bridge
1898 descriptors it gave out in total, and how many unique descriptors
1899 it gave out. It also lists how often the most and least commonly
1900 fetched descriptors were given out, as well as the median and
1901 25th/75th percentile. Implements tickets 4200 and 4294.
1903 o Minor features (IPv6):
1904 - Make the code that clients use to detect an address change be
1905 IPv6-aware, so that it won't fill clients' logs with error
1906 messages when trying to get the IPv4 address of an IPv6
1907 connection. Implements ticket 5537.
1908 - Relays now understand an IPv6 address when they get one from a
1909 directory server. Resolves ticket 4875.
1911 o Minor features (hidden services):
1912 - Expire old or over-used hidden service introduction points.
1913 Required by fix for bug 3460.
1914 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1915 public key replay-detection cache from 60 minutes to 5 minutes. This
1916 replay-detection cache is now used only to detect multiple
1917 INTRODUCE2 cells specifying the same rendezvous point, so we can
1918 avoid launching multiple simultaneous attempts to connect to it.
1919 - When a hidden service's introduction point times out, consider
1920 trying it again during the next attempt to connect to the
1921 HS. Previously, we would not try it again unless a newly fetched
1922 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1924 o Minor features (relays):
1925 - Relays now include a reason for regenerating their descriptors
1926 in an HTTP header when uploading to the authorities. This will
1927 make it easier to debug descriptor-upload issues in the future.
1928 - Turn on directory request statistics by default and include them in
1929 extra-info descriptors. Don't break if we have no GeoIP database.
1930 - Replace files in stats/ rather than appending to them. Now that we
1931 include statistics in extra-info descriptors, it makes no sense to
1932 keep old statistics forever. Implements ticket 2930.
1933 - Relays that set "ConnDirectionStatistics 1" write statistics on the
1934 bidirectional use of connections to disk every 24 hours.
1935 - Add a GeoIP file digest to the extra-info descriptor. Implements
1938 o Minor features (new config options):
1939 - New config option "DynamicDHGroups" (disabled by default) provides
1940 each bridge with a unique prime DH modulus to be used during
1941 SSL handshakes. This option attempts to help against censors
1942 who might use the Apache DH modulus as a static identifier for
1943 bridges. Addresses ticket 4548.
1944 - New config option "DisableDebuggerAttachment" (on by default)
1945 to prevent basic debugging attachment attempts by other processes.
1946 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1947 - Ordinarily, Tor does not count traffic from private addresses (like
1948 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
1949 There is now a new option, CountPrivateBandwidth, to disable this
1950 behavior. Patch from Daniel Cagara.
1952 o Minor features (different behavior for old config options):
1953 - Allow MapAddress directives to specify matches against super-domains,
1954 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1955 Implements issue 933.
1956 - Don't disable the DirPort when we cannot exceed our AccountingMax
1957 limit during this interval because the effective bandwidthrate is
1958 low enough. This is useful in a situation where AccountMax is only
1959 used as an additional safeguard or to provide statistics.
1960 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
1961 implements ticket 3439.
1962 - When configuring a large set of nodes in EntryNodes, and there are
1963 enough of them listed as Guard so that we don't need to consider
1964 the non-guard entries, prefer the ones listed with the Guard flag.
1965 - If you set the NumCPUs option to 0, Tor will now try to detect how
1966 many CPUs you have. This is the new default behavior.
1967 - The NodeFamily option -- which let you declare that you want to
1968 consider nodes to be part of a family whether they list themselves
1969 that way or not -- now allows IP address ranges and country codes.
1971 o Minor features (new command-line config behavior):
1972 - Slightly change behavior of "list" options (that is, config
1973 options that can appear more than once) when they appear both in
1974 torrc and on the command line. Previously, the command-line options
1975 would be appended to the ones from torrc. Now, the command-line
1976 options override the torrc options entirely. This new behavior
1977 allows the user to override list options (like exit policies and
1978 ports to listen on) from the command line, rather than simply
1979 appending to the list.
1980 - You can get the old (appending) command-line behavior for "list"
1981 options by prefixing the option name with a "+".
1982 - You can remove all the values for a "list" option from the command
1983 line without adding any new ones by prefixing the option name
1986 o Minor features (controller, new events):
1987 - Extend the control protocol to report flags that control a circuit's
1988 path selection in CIRC events and in replies to 'GETINFO
1989 circuit-status'. Implements part of ticket 2411.
1990 - Extend the control protocol to report the hidden service address
1991 and current state of a hidden-service-related circuit in CIRC
1992 events and in replies to 'GETINFO circuit-status'. Implements part
1994 - Include the creation time of a circuit in CIRC and CIRC2
1995 control-port events and the list produced by the 'GETINFO
1996 circuit-status' control-port command.
1997 - Add a new CONF_CHANGED event so that controllers can be notified
1998 of any configuration changes made by other controllers, or by the
1999 user. Implements ticket 1692.
2000 - Add a new SIGNAL event to the controller interface so that
2001 controllers can be notified when Tor handles a signal. Resolves
2002 issue 1955. Patch by John Brooks.
2004 o Minor features (controller, new getinfo options):
2005 - Expose our view of whether we have gone dormant to the controller,
2006 via a new "GETINFO dormant" value. Torbutton and other controllers
2007 can use this to avoid doing periodic requests through Tor while
2008 it's dormant (bug 4718). Resolves ticket 5954.
2009 - Add a new GETINFO option to get total bytes read and written. Patch
2010 from pipe, revised by atagar. Resolves ticket 2345.
2011 - Implement new GETINFO controller fields to provide information about
2012 the Tor process's pid, euid, username, and resource limits.
2014 o Minor features (controller, other):
2015 - Allow controllers to request an event notification whenever a
2016 circuit is cannibalized or its purpose is changed. Implements
2017 part of ticket 3457.
2018 - Use absolute path names when reporting the torrc filename in the
2019 control protocol, so a controller can more easily find the torrc
2020 file. Resolves bug 1101.
2021 - When reporting the path to the cookie file to the controller,
2022 give an absolute path. Resolves ticket 4881.
2024 o Minor features (log messages):
2025 - Add more information to a log statement that might help track down
2026 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2027 non-IP address" messages (or any Bug messages, for that matter!),
2028 please let us know about it.
2029 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2030 EntryNodes will have no effect. Resolves issue 2571.
2031 - Try to make the introductory warning message that Tor prints on
2032 startup more useful for actually finding help and information.
2033 Resolves ticket 2474.
2034 - When the system call to create a listener socket fails, log the
2035 error message explaining why. This may help diagnose bug 4027.
2037 o Minor features (other):
2038 - When we fail to initialize Libevent, retry with IOCP disabled so we
2039 don't need to turn on multi-threading support in Libevent, which in
2040 turn requires a working socketpair(). This is a workaround for bug
2041 4457, which affects Libevent versions from 2.0.1-alpha through
2043 - When starting as root and then changing our UID via the User
2044 control option, and we have a ControlSocket configured, make sure
2045 that the ControlSocket is owned by the same account that Tor will
2046 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2047 - Accept attempts to include a password authenticator in the
2048 handshake, as supported by SOCKS5. This handles SOCKS clients that
2049 don't know how to omit a password when authenticating. Resolves
2051 - Check for and recover from inconsistency in the microdescriptor
2052 cache. This will make it harder for us to accidentally free a
2053 microdescriptor without removing it from the appropriate data
2054 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2055 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2057 o Minor bugfixes (code security):
2058 - Prevent a null-pointer dereference when receiving a data cell
2059 for a nonexistent stream when the circuit in question has an
2060 empty deliver window. We don't believe this is triggerable,
2061 since we don't currently allow deliver windows to become empty,
2062 but the logic is tricky enough that it's better to make the code
2063 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2064 - Fix a (harmless) integer overflow in cell statistics reported by
2065 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2066 - Fix our implementation of crypto_random_hostname() so it can't
2067 overflow on ridiculously large inputs. (No Tor version has ever
2068 provided this kind of bad inputs, but let's be correct in depth.)
2069 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
2070 - Add a (probably redundant) memory clear between iterations of
2071 the router status voting loop, to prevent future coding errors
2072 where data might leak between iterations of the loop. Resolves
2075 o Minor bugfixes (wrapper functions):
2076 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
2077 utility function used in the control-port code). This shouldn't
2078 ever happen unless Tor is completely out of memory, but if it did
2079 happen and Tor somehow recovered from it, Tor could have sent a log
2080 message to a control port in the middle of a reply to a controller
2081 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2082 - Fix some (not actually triggerable) buffer size checks in usage of
2083 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
2085 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
2086 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
2087 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2088 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2089 - Make our replacement implementation of strtok_r() compatible with
2090 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2091 bugfix on 0.2.2.1-alpha.
2092 - Find more places in the code that should have been testing for
2093 invalid sockets using the SOCKET_OK macro. Required for a fix
2094 for bug 4533. Bugfix on 0.2.2.28-beta.
2096 o Minor bugfixes (code correctness):
2097 - Check return value of fputs() when writing authority certificate
2098 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
2099 - When building Tor on Windows with -DUNICODE (not default), ensure
2100 that error messages, filenames, and DNS server names are always
2101 NUL-terminated when we convert them to a single-byte encoding.
2102 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2103 - Fix a memory leak when trying to launch a DNS request when the
2104 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
2106 - Correct file sizes when reading binary files on Cygwin, to avoid
2107 a bug where Tor would fail to read its state file. Fixes bug 6844;
2108 bugfix on 0.1.2.7-alpha.
2109 - Make sure to set *socket_error in all error cases in
2110 connection_connect(), so it can't produce a warning about
2111 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2112 0.2.1.1-alpha; resolves ticket 6028.
2113 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
2114 bug 4532; found by "troll_un".
2116 o Minor bugfixes (clients):
2117 - Allow one-hop directory-fetching circuits the full "circuit build
2118 timeout" period, rather than just half of it, before failing them
2119 and marking the relay down. This fix should help reduce cases where
2120 clients declare relays (or worse, bridges) unreachable because
2121 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
2122 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
2124 - Ensure we don't cannibalize circuits that are longer than three hops
2125 already, so we don't end up making circuits with 5 or more
2126 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2127 0.1.0.1-rc which introduced cannibalization.
2129 o Minor bugfixes (relays):
2130 - Don't publish a new relay descriptor when we reload our onion key,
2131 unless the onion key has actually changed. Fixes bug 3263 and
2132 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2133 - When relays refuse a "create" cell because their queue of pending
2134 create cells is too big (typically because their cpu can't keep up
2135 with the arrival rate), send back reason "resource limit" rather
2136 than reason "internal", so network measurement scripts can get a
2137 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
2138 - Exit nodes don't need to fetch certificates for authorities that
2139 they don't recognize; only directory authorities, bridges,
2140 and caches need to do that. Fixes part of bug 2297; bugfix on
2143 o Minor bugfixes (directory authority / mirrors):
2144 - Avoid O(n^2) performance characteristics when parsing a large
2145 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2146 - Authorities no longer include any router in their microdescriptor
2147 consensuses for which they couldn't generate or agree on a
2148 microdescriptor. Fixes the second piece of bug 6404; fix on
2150 - When checking for requested signatures on the latest consensus
2151 before serving it to a client, make sure to check the right
2152 consensus flavor. Bugfix on 0.2.2.6-alpha.
2153 - Fix an edge case where TestingTorNetwork is set but the authorities
2154 and relays all have an uptime of zero, so the private Tor network
2155 could briefly lack support for hidden services. Fixes bug 3886;
2156 bugfix on 0.2.2.18-alpha.
2157 - Directory caches no longer refuse to clean out descriptors because
2158 of missing v2 networkstatus documents, unless they're configured
2159 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2160 0.2.2.26-beta. Patch by Daniel Bryg.
2161 - Don't serve or accept v2 hidden service descriptors over a relay's
2162 DirPort. It's never correct to do so, and disabling it might
2163 make it more annoying to exploit any bugs that turn up in the
2164 descriptor-parsing code. Fixes bug 7149.
2166 o Minor bugfixes (hidden services, client-side):
2167 - Assert that hidden-service-related operations are not performed
2168 using single-hop circuits. Previously, Tor would assert that
2169 client-side streams are not attached to single-hop circuits,
2170 but not that other sensitive operations on the client and service
2171 side are not performed using single-hop circuits. Fixes bug 3332;
2173 - Avoid undefined behaviour when parsing the list of supported
2174 rendezvous/introduction protocols in a hidden service descriptor.
2175 Previously, Tor would have confused (as-yet-unused) protocol version
2176 numbers greater than 32 with lower ones on many platforms. Fixes
2177 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2178 - Don't close hidden service client circuits which have almost
2179 finished connecting to their destination when they reach
2180 the normal circuit-build timeout. Previously, we would close
2181 introduction circuits which are waiting for an acknowledgement
2182 from the introduction point, and rendezvous circuits which have
2183 been specified in an INTRODUCE1 cell sent to a hidden service,
2184 after the normal CBT. Now, we mark them as 'timed out', and launch
2185 another rendezvous attempt in parallel. This behavior change can
2186 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
2187 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
2189 o Minor bugfixes (hidden services, service-side):
2190 - Don't close hidden-service-side rendezvous circuits when they
2191 reach the normal circuit-build timeout. This behaviour change can
2192 be disabled using the new
2193 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
2194 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
2195 - Don't launch more than 10 service-side introduction-point circuits
2196 for a hidden service in five minutes. Previously, we would consider
2197 launching more introduction-point circuits if at least one second
2198 had passed without any introduction-point circuits failing. Fixes
2199 bug 4607; bugfix on 0.0.7pre1.
2201 o Minor bugfixes (config option behavior):
2202 - If the user tries to set MyFamily on a bridge, refuse to
2203 do so, and warn about the security implications. Fixes bug 4657;
2204 bugfix on 0.2.0.3-alpha.
2205 - The "--quiet" and "--hush" options now apply not only to Tor's
2206 behavior before logs are configured, but also to Tor's behavior in
2207 the absense of configured logs. Fixes bug 3550; bugfix on
2209 - Change the AllowDotExit rules so they should actually work.
2210 We now enforce AllowDotExit only immediately after receiving an
2211 address via SOCKS or DNSPort: other sources are free to provide
2212 .exit addresses after the resolution occurs. Fixes bug 3940;
2213 bugfix on 0.2.2.1-alpha.
2214 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
2215 don't depend on the consensus parameters or compute adaptive
2216 timeouts when it is disabled. Fixes bug 5049; bugfix on
2218 - After we pick a directory mirror, we would refuse to use it if
2219 it's in our ExcludeExitNodes list, resulting in mysterious failures
2220 to bootstrap for people who just wanted to avoid exiting from
2221 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2222 - When told to add a bridge with the same digest as a preexisting
2223 bridge but a different addr:port, change the addr:port as
2224 requested. Previously we would not notice the change. Fixes half
2225 of bug 5603; fix on 0.2.2.26-beta.
2227 o Minor bugfixes (controller):
2228 - Allow manual 'authenticate' commands to the controller interface
2229 from netcat (nc) as well as telnet. We were rejecting them because
2230 they didn't come with the expected whitespace at the end of the
2231 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
2232 - Report a real bootstrap problem to the controller on router
2233 identity mismatch. Previously we just said "foo", which probably
2234 made a lot of sense at the time. Fixes bug 4169; bugfix on
2236 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2237 option is set to 0 (which Vidalia version 0.2.16 now does when
2238 a SAVECONF attempt fails), perform other actions that SIGHUP
2239 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2241 - Correctly handle checking the permissions on the parent
2242 directory of a control socket in the root directory. Bug found
2243 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2245 - End AUTHCHALLENGE error messages (in the control protocol) with
2246 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
2248 o Minor bugfixes (network reading/writing):
2249 - Disable writing on marked-for-close connections when they are
2250 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
2251 bug 5263; bugfix on 0.0.2pre13, where we first added a special
2252 case for flushing marked connections.
2253 - Make sure that there are no unhandled pending TLS errors before
2254 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2255 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2256 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2257 - Detect SSL handshake even when the initial attempt to write the
2258 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2259 - If the client fails to set a reasonable set of ciphersuites
2260 during its v2 handshake renegotiation, allow the renegotiation to
2261 continue nevertheless (i.e. send all the required certificates).
2262 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2264 o Minor bugfixes (other):
2265 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2266 resource exhaustion, so that clients can adjust their load to
2267 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2268 started using END_STREAM_REASON_RESOURCELIMIT.
2269 - Don't check for whether the address we're using for outbound
2270 connections has changed until after the outbound connection has
2271 completed. On Windows, getsockname() doesn't succeed until the
2272 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2273 - Don't hold a Windows file handle open for every file mapping;
2274 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2276 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
2277 bugfix on 0.2.1.10-alpha.
2278 - If we fail to write a microdescriptor to the disk cache, do not
2279 continue replacing the old microdescriptor file. Fixes bug 2954;
2280 bugfix on 0.2.2.6-alpha.
2282 o Minor bugfixes (log messages, path selection):
2283 - Downgrade "set buildtimeout to low value" messages to "info"
2284 severity; they were never an actual problem, there was never
2285 anything reasonable to do about them, and they tended to spam logs
2286 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
2287 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2288 more information to it, so that we can track it down in case it
2289 returns again. Mitigates bug 5235.
2290 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2291 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2292 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2293 - Issue a log message if a guard completes less than 40% of your
2294 circuits. Threshold is configurable by torrc option
2295 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
2296 additional, off-by-default code to disable guards which fail too
2297 many circuits. Addresses ticket 5458.
2299 o Minor bugfixes (log messages, client):
2300 - Downgrade "Got a certificate, but we already have it" log messages
2301 from warning to info, except when we're a dirauth. Fixes bug 5238;
2302 bugfix on 0.2.1.7-alpha.
2303 - Fix the log message describing how we work around discovering
2304 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
2305 4837; bugfix on 0.2.2.9-alpha.
2306 - When logging about a disallowed .exit name, do not also call it
2307 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
2308 - Fix a log message suggesting that people contact a non-existent
2309 email address. Fixes bug 3448.
2310 - Rephrase the log message emitted if the TestSocks check is
2311 successful. Patch from Fabian Keil; fixes bug 4094.
2312 - Log (at debug level) whenever a circuit's purpose is changed.
2313 - Log SSL state transitions at log level DEBUG, log domain
2314 HANDSHAKE. This can be useful for debugging censorship events.
2315 Implements ticket 3264.
2316 - We now log which torrc file we're using on startup. Implements
2318 - Rate-limit log messages when asked to connect anonymously to
2319 a private address. When these hit, they tended to hit fast and
2320 often. Also, don't bother trying to connect to addresses that we
2321 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2322 reply makes us think we have been lied to, even when the address the
2323 client tried to connect to was "localhost." Resolves ticket 2822.
2325 o Minor bugfixes (log messages, non-client):
2326 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
2327 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
2328 - Don't log that we have "decided to publish new relay descriptor"
2329 unless we are actually publishing a descriptor. Fixes bug 3942;
2330 bugfix on 0.2.2.28-beta.
2331 - Log which authority we're missing votes from when we go to fetch
2332 them from the other auths.
2333 - Replace "Sending publish request" log messages with "Launching
2334 upload", so that they no longer confusingly imply that we're
2335 sending something to a directory we might not even be connected
2336 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
2337 - Warn when Tor is configured to use accounting in a way that can
2338 link a hidden service to some other hidden service or public
2339 address. Resolves ticket 6490.
2340 - Fix a minor formatting issue in one of tor-gencert's error messages.
2344 - Update to the latest version of the tinytest unit testing framework.
2345 This includes a couple of bugfixes that can be relevant for
2346 running forked unit tests on Windows, and removes all reserved
2348 - Avoid a false positive in the util/threads unit test by increasing
2349 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
2350 - Make it possible to set the TestingTorNetwork configuration
2351 option using AlternateDirAuthority and AlternateBridgeAuthority
2352 as an alternative to setting DirServer. Addresses ticket 6377.
2353 - Add a unit test for the environment_variable_names_equal() function.
2354 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2355 - Numerous new unit tests for functions in util.c and address.c by
2357 - The long-disabled benchmark tests are now split into their own
2358 ./src/test/bench binary.
2359 - The benchmark tests can now use more accurate timers than
2360 gettimeofday() when such timers are available.
2361 - Use tt_assert(), not tor_assert(), for checking for test failures.
2362 This makes the unit tests more able to go on in the event that
2365 o Build improvements:
2366 - Use the dead_strip option when building Tor on OS X. This reduces
2367 binary size by almost 19% when linking openssl and libevent
2368 statically, which we do for Tor Browser Bundle.
2369 - Provide a better error message about possible OSX Asciidoc failure
2370 reasons. Fixes bug 6436.
2371 - Detect attempts to build Tor on (as yet hypothetical) versions
2372 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
2373 fix for bug 4533. Bugfix on 0.2.2.28-beta.
2374 - On Windows, we now define the _WIN32_WINNT macros only if they
2375 are not already defined. This lets the person building Tor decide,
2376 if they want, to require a later version of Windows.
2377 - Our autogen.sh script now uses autoreconf to launch autoconf,
2378 automake, and so on. This is more robust against some of the failure
2379 modes associated with running the autotools pieces on their own.
2380 - Running "make version" now displays the version of Tor that
2381 we're about to build. Idea from katmagic; resolves issue 4400.
2382 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
2383 on 0.2.2.4-alpha; fixes bug 3427.
2384 - New --enable-static-tor configure option for building Tor as
2385 statically as possible. Idea, general hackery and thoughts from
2386 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
2388 - Limited, experimental support for building with nmake and MSVC.
2390 o Build requirements:
2391 - Building Tor with bufferevent support now requires Libevent
2392 2.0.13-stable or later. Previous versions of Libevent had bugs in
2393 SSL-related bufferevents and related issues that would make Tor
2394 work badly with bufferevents. Requiring 2.0.13-stable also allows
2395 Tor with bufferevents to take advantage of Libevent APIs
2396 introduced after 2.0.8-rc.
2397 - Our build system requires automake 1.6 or later to create the
2398 Makefile.in files. Previously, you could have used 1.4.
2399 This only affects developers and people building Tor from git;
2400 people who build Tor from the source distribution without changing
2401 the Makefile.am files should be fine.
2402 - Detect when we try to build on a platform that doesn't define
2403 AF_UNSPEC to 0. We don't work there, so refuse to compile.
2405 o Build fixes (compile/link):
2406 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2407 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2409 - When building with --enable-static-tor on OpenBSD, do not
2410 erroneously attempt to link -lrt. Fixes bug 5103.
2411 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2412 that IPv6 stuff will compile on MSVC, and compilation issues
2413 will be easier to track down. Fixes bug 5861.
2414 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
2415 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
2416 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
2417 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
2419 o Build fixes (other):
2420 - Use the _WIN32 macro throughout our code to detect Windows.
2421 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2423 - Properly handle the case where the build-tree is not the same
2424 as the source tree when generating src/common/common_sha1.i,
2425 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
2426 bugfix on 0.2.0.1-alpha.
2427 - During configure, search for library containing cos function as
2428 libm lives in libcore on some platforms (BeOS/Haiku). Linking
2429 against libm was hard-coded before. Fixes the first part of bug
2430 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
2432 - Prevent a false positive from the check-spaces script, by disabling
2433 the "whitespace between function name and (" check for functions
2436 o Packaging (RPM) changes:
2437 - Update our default RPM spec files to work with mock and rpmbuild
2438 on RHEL/Fedora. They have an updated set of dependencies and
2439 conflicts, a fix for an ancient typo when creating the "_tor"
2440 user, and better instructions. Thanks to Ondrej Mikle for the
2441 patch series. Fixes bug 6043.
2442 - On OpenSUSE, create the /var/run/tor directory on startup if it
2443 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
2445 o Code refactoring (safety):
2446 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
2447 10 lines. Also, don't nest them. Doing so in the past has
2448 led to hard-to-debug code. The new style is to use the
2449 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
2450 - Use macros to indicate OpenSSL versions, so we don't need to worry
2451 about accidental hexadecimal bit shifts.
2452 - Use tor_sscanf() in place of scanf() in more places through the
2453 code. This makes us a little more locale-independent, and
2454 should help shut up code-analysis tools that can't tell
2455 a safe sscanf string from a dangerous one.
2456 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
2457 - Use the smartlist_add_asprintf() alias more consistently.
2459 o Code refactoring (consolidate):
2460 - A major revision to our internal node-selecting and listing logic.
2461 Tor already had at least two major ways to look at the question of
2462 "which Tor servers do we know about": a list of router descriptors,
2463 and a list of entries in the current consensus. With
2464 microdescriptors, we're adding a third. Having so many systems
2465 without an abstraction layer over them was hurting the codebase.
2466 Now, we have a new "node_t" abstraction that presents a consistent
2467 interface to a client's view of a Tor node, and holds (nearly) all
2468 of the mutable state formerly in routerinfo_t and routerstatus_t.
2469 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
2470 Libevent's notion of cached time when possible.
2471 - Remove duplicate code for invoking getrlimit() from control.c.
2472 - Use OpenSSL's built-in SSL_state_string_long() instead of our
2473 own homebrewed ssl_state_to_string() replacement. Patch from
2474 Emile Snyder. Fixes bug 4653.
2475 - Change the symmetric cipher interface so that creating and
2476 initializing a stream cipher are no longer separate functions.
2478 o Code refactoring (separate):
2479 - Make a new "entry connection" struct as an internal subtype of "edge
2480 connection", to simplify the code and make exit connections smaller.
2481 - Split connection_about_to_close() into separate functions for each
2483 - Rewrite the listener-selection logic so that parsing which ports
2484 we want to listen on is now separate from binding to the ports
2487 o Code refactoring (name changes):
2488 - Rename a handful of old identifiers, mostly related to crypto
2489 structures and crypto functions. By convention, our "create an
2490 object" functions are called "type_new()", our "free an object"
2491 functions are called "type_free()", and our types indicate that
2492 they are types only with a final "_t". But a handful of older
2493 types and functions broke these rules, with function names like
2494 "type_create" or "subsystem_op_type", or with type names like
2496 - Rename Tor functions that turn strings into addresses, so that
2497 "parse" indicates that no hostname resolution occurs, and
2498 "lookup" indicates that hostname resolution may occur. This
2499 should help prevent mistakes in the future. Fixes bug 3512.
2500 - Use the name "CERTS" consistently to refer to the new cell type;
2501 we were calling it CERT in some places and CERTS in others.
2502 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
2503 invalid value, rather than just -1.
2504 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
2505 can pick them up when the tests aren't disabled. Bugfix on
2506 0.2.2.4-alpha which introduced tinytest.
2508 o Code refactoring (other):
2509 - Defensively refactor rend_mid_rendezvous() so that protocol
2510 violations and length checks happen in the beginning. Fixes
2512 - Remove the pure attribute from all functions that used it
2513 previously. In many cases we assigned it incorrectly, because the
2514 functions might assert or call impure functions, and we don't have
2515 evidence that keeping the pure attribute is worthwhile. Implements
2516 changes suggested in ticket 4421.
2517 - Move the replay-detection cache for the RSA-encrypted parts of
2518 INTRODUCE2 cells to the introduction point data structures.
2519 Previously, we would use one replay-detection cache per hidden
2520 service. Required by fix for bug 3460.
2521 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
2522 no longer link against Libevent: they never used it, but
2523 our library structure used to force them to link it.
2525 o Removed features and files:
2526 - Remove all internal support for unpadded RSA. We never used it, and
2527 it would be a bad idea to start.
2528 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
2530 - Remove some redundant #include directives throughout the code.
2531 Patch from Andrea Gelmini.
2532 - Remove some old code to remember statistics about which descriptors
2533 we've served as a directory mirror. The feature wasn't used and
2534 is outdated now that microdescriptors are around.
2535 - Remove some old code to work around even older versions of Tor that
2536 used forked processes to handle DNS requests. Such versions of Tor
2537 are no longer in use as relays.
2538 - The "torify" script no longer supports the "tsocks" socksifier
2539 tool, since tsocks doesn't support DNS and UDP right for Tor.
2540 Everyone should be using torsocks instead. Fixes bugs 3530 and
2541 5180. Based on a patch by "ugh".
2542 - Remove the torrc.bridge file: we don't use it for anything, and
2543 it had become badly desynchronized from torrc.sample. Resolves
2547 - Begin a doc/state-contents.txt file to explain the contents of
2548 the Tor state file. Fixes bug 2987.
2549 - Clarify the documentation for the Alternate*Authority options.
2551 - Document the --defaults-torrc option, and the new semantics for
2552 overriding, extending, and clearing lists of options. Closes
2554 - Add missing man page documentation for consensus and microdesc
2555 files. Resolves ticket 6732.
2556 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
2558 o Documentation fixes:
2559 - Improve the manual's documentation for the NT Service command-line
2560 options. Addresses ticket 3964.
2561 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2562 - Document the changes to the ORPort and DirPort options, and the
2563 fact that {OR/Dir}ListenAddress is now unnecessary (and
2564 therefore deprecated). Resolves ticket 5597.
2565 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
2566 - Clarify that hidden services are TCP only. Fixes bug 6024.
2569 Changes in version 0.2.2.39 - 2012-09-11
2570 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
2574 - Fix an assertion failure in tor_timegm() that could be triggered
2575 by a badly formatted directory object. Bug found by fuzzing with
2576 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2577 - Do not crash when comparing an address with port value 0 to an
2578 address policy. This bug could have been used to cause a remote
2579 assertion failure by or against directory authorities, or to
2580 allow some applications to crash clients. Fixes bug 6690; bugfix
2584 Changes in version 0.2.2.38 - 2012-08-12
2585 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
2586 attack that could in theory leak path information.
2589 - Avoid an uninitialized memory read when reading a vote or consensus
2590 document that has an unrecognized flavor name. This read could
2591 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2592 - Try to leak less information about what relays a client is
2593 choosing to a side-channel attacker. Previously, a Tor client would
2594 stop iterating through the list of available relays as soon as it
2595 had chosen one, thus finishing a little earlier when it picked
2596 a router earlier in the list. If an attacker can recover this
2597 timing information (nontrivial but not proven to be impossible),
2598 they could learn some coarse-grained information about which relays
2599 a client was picking (middle nodes in particular are likelier to
2600 be affected than exits). The timing attack might be mitigated by
2601 other factors (see bug 6537 for some discussion), but it's best
2602 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2605 Changes in version 0.2.2.37 - 2012-06-06
2606 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2607 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2611 - Work around a bug in OpenSSL that broke renegotiation with TLS
2612 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2613 the v2 Tor connection protocol when both sides were using OpenSSL
2614 1.0.1 would fail. Resolves ticket 6033.
2615 - When waiting for a client to renegotiate, don't allow it to add
2616 any bytes to the input buffer. This fixes a potential DoS issue.
2617 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2618 - Fix an edge case where if we fetch or publish a hidden service
2619 descriptor, we might build a 4-hop circuit and then use that circuit
2620 for exiting afterwards -- even if the new last hop doesn't obey our
2621 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2624 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2625 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2628 - Tell GCC and Clang to check for any errors in format strings passed
2629 to the tor_v*(print|scan)f functions.
2632 Changes in version 0.2.2.36 - 2012-05-24
2633 Tor 0.2.2.36 updates the addresses for two of the eight directory
2634 authorities, fixes some potential anonymity and security issues,
2635 and fixes several crash bugs.
2637 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2638 known flaws, and nobody should be using them. You should upgrade. If
2639 you're using a Linux or BSD and its packages are obsolete, stop using
2640 those packages and upgrade anyway.
2642 o Directory authority changes:
2643 - Change IP address for maatuska (v3 directory authority).
2644 - Change IP address for ides (v3 directory authority), and rename
2648 - When building or running with any version of OpenSSL earlier
2649 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2650 versions have a bug (CVE-2011-4576) in which their block cipher
2651 padding includes uninitialized data, potentially leaking sensitive
2652 information to any peer with whom they make a SSLv3 connection. Tor
2653 does not use SSL v3 by default, but a hostile client or server
2654 could force an SSLv3 connection in order to gain information that
2655 they shouldn't have been able to get. The best solution here is to
2656 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2657 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2658 to make sure that the bug can't happen.
2659 - Never use a bridge or a controller-supplied node as an exit, even
2660 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2661 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2662 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2663 - Only build circuits if we have a sufficient threshold of the total
2664 descriptors that are marked in the consensus with the "Exit"
2665 flag. This mitigates an attack proposed by wanoskarnet, in which
2666 all of a client's bridges collude to restrict the exit nodes that
2667 the client knows about. Fixes bug 5343.
2668 - Provide controllers with a safer way to implement the cookie
2669 authentication mechanism. With the old method, if another locally
2670 running program could convince a controller that it was the Tor
2671 process, then that program could trick the controller into telling
2672 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2673 authentication method uses a challenge-response approach to prevent
2674 this attack. Fixes bug 5185; implements proposal 193.
2677 - Avoid logging uninitialized data when unable to decode a hidden
2678 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2679 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2680 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2682 - Fix builds when the path to sed, openssl, or sha1sum contains
2683 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2685 - Correct our replacements for the timeradd() and timersub() functions
2686 on platforms that lack them (for example, Windows). The timersub()
2687 function is used when expiring circuits, while timeradd() is
2688 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2689 bugfix on 0.2.2.24-alpha.
2690 - Fix the SOCKET_OK test that we use to tell when socket
2691 creation fails so that it works on Win64. Fixes part of bug 4533;
2692 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2695 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2696 Fixes bug 5346; bugfix on 0.0.8pre3.
2697 - Make our number-parsing functions always treat too-large values
2698 as an error, even when those values exceed the width of the
2699 underlying type. Previously, if the caller provided these
2700 functions with minima or maxima set to the extreme values of the
2701 underlying integer type, these functions would return those
2702 values on overflow rather than treating overflow as an error.
2703 Fixes part of bug 5786; bugfix on 0.0.9.
2704 - Older Linux kernels erroneously respond to strange nmap behavior
2705 by having accept() return successfully with a zero-length
2706 socket. When this happens, just close the connection. Previously,
2707 we would try harder to learn the remote address: but there was
2708 no such remote address to learn, and our method for trying to
2709 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2710 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2711 - Correct parsing of certain date types in parse_http_time().
2712 Without this patch, If-Modified-Since would behave
2713 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2714 Esteban Manchado Velázques.
2715 - Change the BridgePassword feature (part of the "bridge community"
2716 design, which is not yet implemented) to use a time-independent
2717 comparison. The old behavior might have allowed an adversary
2718 to use timing to guess the BridgePassword value. Fixes bug 5543;
2719 bugfix on 0.2.0.14-alpha.
2720 - Detect and reject certain misformed escape sequences in
2721 configuration values. Previously, these values would cause us
2722 to crash if received in a torrc file or over an authenticated
2723 control port. Bug found by Esteban Manchado Velázquez, and
2724 independently by Robert Connolly from Matta Consulting who further
2725 noted that it allows a post-authentication heap overflow. Patch
2726 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2727 bugfix on 0.2.0.16-alpha.
2728 - Fix a compile warning when using the --enable-openbsd-malloc
2729 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2730 - During configure, detect when we're building with clang version
2731 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2732 CFLAGS. clang doesn't support them yet.
2733 - When sending an HTTP/1.1 proxy request, include a Host header.
2734 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2735 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2736 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2737 - If we hit the error case where routerlist_insert() replaces an
2738 existing (old) server descriptor, make sure to remove that
2739 server descriptor from the old_routers list. Fix related to bug
2740 1776. Bugfix on 0.2.2.18-alpha.
2742 o Minor bugfixes (documentation and log messages):
2743 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2744 Fixes bug 4856; bugfix on Tor 0.0.6.
2745 - Update "ClientOnly" man page entry to explain that there isn't
2746 really any point to messing with it. Resolves ticket 5005.
2747 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2748 directory authority option (introduced in Tor 0.2.2.34).
2749 - Downgrade the "We're missing a certificate" message from notice
2750 to info: people kept mistaking it for a real problem, whereas it
2751 is seldom the problem even when we are failing to bootstrap. Fixes
2752 bug 5067; bugfix on 0.2.0.10-alpha.
2753 - Correctly spell "connect" in a log message on failure to create a
2754 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2755 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2756 circuits. Fixes issue 5259.
2759 - Directory authorities now reject versions of Tor older than
2760 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2761 inclusive. These versions accounted for only a small fraction of
2762 the Tor network, and have numerous known security issues. Resolves
2764 - Update to the May 1 2012 Maxmind GeoLite Country database.
2767 - When sending or relaying a RELAY_EARLY cell, we used to convert
2768 it to a RELAY cell if the connection was using the v1 link
2769 protocol. This was a workaround for older versions of Tor, which
2770 didn't handle RELAY_EARLY cells properly. Now that all supported
2771 versions can handle RELAY_EARLY cells, and now that we're enforcing
2772 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2773 remove this workaround. Addresses bug 4786.
2776 Changes in version 0.2.2.35 - 2011-12-16
2777 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
2778 buffers code. Absolutely everybody should upgrade.
2780 The bug relied on an incorrect calculation when making data continuous
2781 in one of our IO buffers, if the first chunk of the buffer was
2782 misaligned by just the wrong amount. The miscalculation would allow an
2783 attacker to overflow a piece of heap-allocated memory. To mount this
2784 attack, the attacker would need to either open a SOCKS connection to
2785 Tor's SocksPort (usually restricted to localhost), or target a Tor
2786 instance configured to make its connections through a SOCKS proxy
2787 (which Tor does not do by default).
2789 Good security practice requires that all heap-overflow bugs should be
2790 presumed to be exploitable until proven otherwise, so we are treating
2791 this as a potential code execution attack. Please upgrade immediately!
2792 This bug does not affect bufferevents-based builds of Tor. Special
2793 thanks to "Vektor" for reporting this issue to us!
2795 Tor 0.2.2.35 also fixes several bugs in previous versions, including
2796 crash bugs for unusual configurations, and a long-term bug that
2797 would prevent Tor from starting on Windows machines with draconian
2800 With this release, we remind everyone that 0.2.0.x has reached its
2801 formal end-of-life. Those Tor versions have many known flaws, and
2802 nobody should be using them. You should upgrade -- ideally to the
2803 0.2.2.x series. If you're using a Linux or BSD and its packages are
2804 obsolete, stop using those packages and upgrade anyway.
2806 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
2807 longer receive support after some time in early 2012.
2810 - Fix a heap overflow bug that could occur when trying to pull
2811 data into the first chunk of a buffer, when that chunk had
2812 already had some data drained from it. Fixes CVE-2011-2778;
2813 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2814 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2815 that it doesn't attempt to allocate a socketpair. This could cause
2816 some problems on Windows systems with overzealous firewalls. Fix for
2817 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2819 - If we mark an OR connection for close based on a cell we process,
2820 don't process any further cells on it. We already avoid further
2821 reads on marked-for-close connections, but now we also discard the
2822 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2823 which was the first version where we might mark a connection for
2824 close based on processing a cell on it.
2825 - Correctly sanity-check that we don't underflow on a memory
2826 allocation (and then assert) for hidden service introduction
2827 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2828 bugfix on 0.2.1.5-alpha.
2829 - Fix a memory leak when we check whether a hidden service
2830 descriptor has any usable introduction points left. Fixes bug
2831 4424. Bugfix on 0.2.2.25-alpha.
2832 - Don't crash when we're running as a relay and don't have a GeoIP
2833 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
2834 we've had in the 0.2.3.x branch already.
2835 - When running as a client, do not print a misleading (and plain
2836 wrong) log message that we're collecting "directory request"
2837 statistics: clients don't collect statistics. Also don't create a
2838 useless (because empty) stats file in the stats/ directory. Fixes
2839 bug 4353; bugfix on 0.2.2.34.
2842 - Detect failure to initialize Libevent. This fix provides better
2843 detection for future instances of bug 4457.
2844 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2845 function. This was eating up hideously large amounts of time on some
2846 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2847 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2848 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2850 - Don't warn about unused log_mutex in log.c when building with
2851 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2852 0.1.0.6-rc which introduced --disable-threads.
2853 - When configuring, starting, or stopping an NT service, stop
2854 immediately after the service configuration attempt has succeeded
2855 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2856 - When sending a NETINFO cell, include the original address
2857 received for the other side, not its canonical address. Found
2858 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2859 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
2860 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2861 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2862 occurred when a client tried to fetch a descriptor for a bridge
2863 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2864 - Backport fixes for a pair of compilation warnings on Windows.
2865 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
2866 - If we had ever tried to call tor_addr_to_str on an address of
2867 unknown type, we would have done a strdup on an uninitialized
2868 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
2869 Reported by "troll_un".
2870 - Correctly detect and handle transient lookup failures from
2871 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2872 Reported by "troll_un".
2873 - Fix null-pointer access that could occur if TLS allocation failed.
2874 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2875 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2876 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2879 - Add two new config options for directory authorities:
2880 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2881 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2882 that is always sufficient to satisfy the bandwidth requirement for
2883 the Guard flag. Now it will be easier for researchers to simulate
2884 Tor networks with different values. Resolves ticket 4484.
2885 - When Tor ignores a hidden service specified in its configuration,
2886 include the hidden service's directory in the warning message.
2887 Previously, we would only tell the user that some hidden service
2888 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2889 - Update to the December 6 2011 Maxmind GeoLite Country database.
2891 o Packaging changes:
2892 - Make it easier to automate expert package builds on Windows,
2893 by removing an absolute path from makensis.exe command.
2896 Changes in version 0.2.1.32 - 2011-12-16
2897 Tor 0.2.1.32 backports important security and privacy fixes for
2898 oldstable. This release is intended only for package maintainers and
2899 others who cannot use the 0.2.2 stable series. All others should be
2900 using Tor 0.2.2.x or newer.
2902 The Tor 0.2.1.x series will reach formal end-of-life some time in
2903 early 2012; we will stop releasing patches for it then.
2905 o Major bugfixes (also included in 0.2.2.x):
2906 - Correctly sanity-check that we don't underflow on a memory
2907 allocation (and then assert) for hidden service introduction
2908 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2909 bugfix on 0.2.1.5-alpha.
2910 - Fix a heap overflow bug that could occur when trying to pull
2911 data into the first chunk of a buffer, when that chunk had
2912 already had some data drained from it. Fixes CVE-2011-2778;
2913 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2916 - Update to the December 6 2011 Maxmind GeoLite Country database.
2919 Changes in version 0.2.2.34 - 2011-10-26
2920 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
2921 can deanonymize Tor users. Everybody should upgrade.
2923 The attack relies on four components: 1) Clients reuse their TLS cert
2924 when talking to different relays, so relays can recognize a user by
2925 the identity key in her cert. 2) An attacker who knows the client's
2926 identity key can probe each guard relay to see if that identity key
2927 is connected to that guard relay right now. 3) A variety of active
2928 attacks in the literature (starting from "Low-Cost Traffic Analysis
2929 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
2930 discover the guard relays that a Tor user visiting the website is using.
2931 4) Clients typically pick three guards at random, so the set of guards
2932 for a given user could well be a unique fingerprint for her. This
2933 release fixes components #1 and #2, which is enough to block the attack;
2934 the other two remain as open research problems. Special thanks to
2935 "frosty_un" for reporting the issue to us!
2937 Clients should upgrade so they are no longer recognizable by the TLS
2938 certs they present. Relays should upgrade so they no longer allow a
2939 remote attacker to probe them to test whether unpatched clients are
2940 currently connected to them.
2942 This release also fixes several vulnerabilities that allow an attacker
2943 to enumerate bridge relays. Some bridge enumeration attacks still
2944 remain; see for example proposal 188.
2946 o Privacy/anonymity fixes (clients):
2947 - Clients and bridges no longer send TLS certificate chains on
2948 outgoing OR connections. Previously, each client or bridge would
2949 use the same cert chain for all outgoing OR connections until
2950 its IP address changes, which allowed any relay that the client
2951 or bridge contacted to determine which entry guards it is using.
2952 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2953 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2954 no longer considers that connection as suitable for satisfying a
2955 circuit EXTEND request. Now relays can protect clients from the
2956 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2957 - Directory authorities no longer assign the Guard flag to relays
2958 that haven't upgraded to the above "refuse EXTEND requests
2959 to client connections" fix. Now directory authorities can
2960 protect clients from the CVE-2011-2768 issue even if neither
2961 the clients nor the relays have upgraded yet. There's a new
2962 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2963 to let us transition smoothly, else tomorrow there would be no
2966 o Privacy/anonymity fixes (bridge enumeration):
2967 - Bridge relays now do their directory fetches inside Tor TLS
2968 connections, like all the other clients do, rather than connecting
2969 directly to the DirPort like public relays do. Removes another
2970 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2971 - Bridges relays now build circuits for themselves in a more similar
2972 way to how clients build them. Removes another avenue for
2973 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2974 when bridges were introduced.
2975 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2976 that they initiated. Relays could distinguish incoming bridge
2977 connections from client connections, creating another avenue for
2978 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2979 Found by "frosty_un".
2982 - Fix a crash bug when changing node restrictions while a DNS lookup
2983 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2985 - Don't launch a useless circuit after failing to use one of a
2986 hidden service's introduction points. Previously, we would
2987 launch a new introduction circuit, but not set the hidden service
2988 which that circuit was intended to connect to, so it would never
2989 actually be used. A different piece of code would then create a
2990 new introduction circuit correctly. Bug reported by katmagic and
2991 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2994 - Change an integer overflow check in the OpenBSD_Malloc code so
2995 that GCC is less likely to eliminate it as impossible. Patch
2996 from Mansour Moufid. Fixes bug 4059.
2997 - When a hidden service turns an extra service-side introduction
2998 circuit into a general-purpose circuit, free the rend_data and
2999 intro_key fields first, so we won't leak memory if the circuit
3000 is cannibalized for use as another service-side introduction
3001 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3002 - Bridges now skip DNS self-tests, to act a little more stealthily.
3003 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3004 bridges. Patch by "warms0x".
3005 - Fix internal bug-checking logic that was supposed to catch
3006 failures in digest generation so that it will fail more robustly
3007 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3008 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3009 - Report any failure in init_keys() calls launched because our
3010 IP address has changed. Spotted by Coverity Scan. Bugfix on
3011 0.1.1.4-alpha; fixes CID 484.
3013 o Minor bugfixes (log messages and documentation):
3014 - Remove a confusing dollar sign from the example fingerprint in the
3015 man page, and also make the example fingerprint a valid one. Fixes
3016 bug 4309; bugfix on 0.2.1.3-alpha.
3017 - The next version of Windows will be called Windows 8, and it has
3018 a major version of 6, minor version of 2. Correctly identify that
3019 version instead of calling it "Very recent version". Resolves
3020 ticket 4153; reported by funkstar.
3021 - Downgrade log messages about circuit timeout calibration from
3022 "notice" to "info": they don't require or suggest any human
3023 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3024 bugfix on 0.2.2.14-alpha.
3027 - Turn on directory request statistics by default and include them in
3028 extra-info descriptors. Don't break if we have no GeoIP database.
3029 Backported from 0.2.3.1-alpha; implements ticket 3951.
3030 - Update to the October 4 2011 Maxmind GeoLite Country database.
3033 Changes in version 0.2.1.31 - 2011-10-26
3034 Tor 0.2.1.31 backports important security and privacy fixes for
3035 oldstable. This release is intended only for package maintainers and
3036 others who cannot use the 0.2.2 stable series. All others should be
3037 using Tor 0.2.2.x or newer.
3039 o Security fixes (also included in 0.2.2.x):
3040 - Replace all potentially sensitive memory comparison operations
3041 with versions whose runtime does not depend on the data being
3042 compared. This will help resist a class of attacks where an
3043 adversary can use variations in timing information to learn
3044 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3045 implementation by Robert Ransom based partially on code by DJB.)
3046 - Fix an assert in parsing router descriptors containing IPv6
3047 addresses. This one took down the directory authorities when
3048 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3050 o Privacy/anonymity fixes (also included in 0.2.2.x):
3051 - Clients and bridges no longer send TLS certificate chains on
3052 outgoing OR connections. Previously, each client or bridge would
3053 use the same cert chain for all outgoing OR connections until
3054 its IP address changes, which allowed any relay that the client
3055 or bridge contacted to determine which entry guards it is using.
3056 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3057 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3058 no longer considers that connection as suitable for satisfying a
3059 circuit EXTEND request. Now relays can protect clients from the
3060 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3061 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3062 that they initiated. Relays could distinguish incoming bridge
3063 connections from client connections, creating another avenue for
3064 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3065 Found by "frosty_un".
3066 - When receiving a hidden service descriptor, check that it is for
3067 the hidden service we wanted. Previously, Tor would store any
3068 hidden service descriptors that a directory gave it, whether it
3069 wanted them or not. This wouldn't have let an attacker impersonate
3070 a hidden service, but it did let directories pre-seed a client
3071 with descriptors that it didn't want. Bugfix on 0.0.6.
3072 - Avoid linkability based on cached hidden service descriptors: forget
3073 all hidden service descriptors cached as a client when processing a
3074 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3075 - Make the bridge directory authority refuse to answer directory
3076 requests for "all" descriptors. It used to include bridge
3077 descriptors in its answer, which was a major information leak.
3078 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3079 - Don't attach new streams to old rendezvous circuits after SIGNAL
3080 NEWNYM. Previously, we would keep using an existing rendezvous
3081 circuit if it remained open (i.e. if it were kept open by a
3082 long-lived stream, or if a new stream were attached to it before
3083 Tor could notice that it was old and no longer in use). Bugfix on
3084 0.1.1.15-rc; fixes bug 3375.
3086 o Minor bugfixes (also included in 0.2.2.x):
3087 - When we restart our relay, we might get a successful connection
3088 from the outside before we've started our reachability tests,
3089 triggering a warning: "ORPort found reachable, but I have no
3090 routerinfo yet. Failing to inform controller of success." This
3091 bug was harmless unless Tor is running under a controller
3092 like Vidalia, in which case the controller would never get a
3093 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3095 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3096 enabled. Fixes bug 1526.
3097 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3098 anything since 0.2.1.16-rc.
3099 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3100 None of the cases where we did this before were wrong, but by making
3101 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3102 - Fix a rare crash bug that could occur when a client was configured
3103 with a large number of bridges. Fixes bug 2629; bugfix on
3104 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3105 - Correct the warning displayed when a rendezvous descriptor exceeds
3106 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3108 - Fix an uncommon assertion failure when running with DNSPort under
3109 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3110 - When warning about missing zlib development packages during compile,
3111 give the correct package names. Bugfix on 0.2.0.1-alpha.
3112 - Require that introduction point keys and onion keys have public
3113 exponent 65537. Bugfix on 0.2.0.10-alpha.
3114 - Do not crash when our configuration file becomes unreadable, for
3115 example due to a permissions change, between when we start up
3116 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3118 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3120 - Always NUL-terminate the sun_path field of a sockaddr_un before
3121 passing it to the kernel. (Not a security issue: kernels are
3122 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3123 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3124 - Don't stack-allocate the list of supplementary GIDs when we're
3125 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3126 could take up to 256K, which is way too much stack. Found by
3127 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3129 o Minor bugfixes (only in 0.2.1.x):
3130 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
3131 rely on them. Bugfix on 0.2.1.30.
3132 - Use git revisions instead of svn revisions when generating our
3133 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3135 o Minor features (also included in 0.2.2.x):
3136 - Adjust the expiration time on our SSL session certificates to
3137 better match SSL certs seen in the wild. Resolves ticket 4014.
3138 - Allow nameservers with IPv6 address. Resolves bug 2574.
3139 - Update to the October 4 2011 Maxmind GeoLite Country database.
3142 Changes in version 0.2.2.33 - 2011-09-13
3143 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
3144 TLS handshake that makes relays and bridges that run this new version
3145 reachable from Iran again.
3148 - Avoid an assertion failure when reloading a configuration with
3149 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3150 3923; bugfix on 0.2.2.25-alpha.
3152 o Minor features (security):
3153 - Check for replays of the public-key encrypted portion of an
3154 INTRODUCE1 cell, in addition to the current check for replays of
3155 the g^x value. This prevents a possible class of active attacks
3156 by an attacker who controls both an introduction point and a
3157 rendezvous point, and who uses the malleability of AES-CTR to
3158 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3159 that these attacks are infeasible (requiring the attacker to send
3160 on the order of zettabytes of altered cells in a short interval),
3161 but we'd rather block them off in case there are any classes of
3162 this attack that we missed. Reported by Willem Pinckaers.
3165 - Adjust the expiration time on our SSL session certificates to
3166 better match SSL certs seen in the wild. Resolves ticket 4014.
3167 - Change the default required uptime for a relay to be accepted as
3168 a HSDir (hidden service directory) from 24 hours to 25 hours.
3169 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3170 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3171 authorities to abstain from voting on assignment of the HSDir
3172 consensus flag. Related to bug 2649.
3173 - Update to the September 6 2011 Maxmind GeoLite Country database.
3175 o Minor bugfixes (documentation and log messages):
3176 - Correct the man page to explain that HashedControlPassword and
3177 CookieAuthentication can both be set, in which case either method
3178 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3179 when we decided to allow these config options to both be set. Issue
3181 - Demote the 'replay detected' log message emitted when a hidden
3182 service receives the same Diffie-Hellman public key in two different
3183 INTRODUCE2 cells to info level. A normal Tor client can cause that
3184 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3185 fixes part of bug 2442.
3186 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3187 level. There is nothing that a hidden service's operator can do
3188 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3190 - Clarify a log message specifying the characters permitted in
3191 HiddenServiceAuthorizeClient client names. Previously, the log
3192 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3193 given the impression that every ASCII character between "+" and "_"
3194 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3197 - Provide a substitute implementation of lround() for MSVC, which
3198 apparently lacks it. Patch from Gisle Vanem.
3199 - Clean up some code issues that prevented Tor from building on older
3200 BSDs. Fixes bug 3894; reported by "grarpamp".
3201 - Search for a platform-specific version of "ar" when cross-compiling.
3202 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3205 Changes in version 0.2.2.32 - 2011-08-27
3206 The Tor 0.2.2 release series is dedicated to the memory of Andreas
3207 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
3208 a founder of the PETS community, a leader in our field, a mentor,
3209 and a friend. He left us with these words: "I had the possibility
3210 to contribute to this world that is not as it should be. I hope I
3211 could help in some areas to make the world a better place, and that
3212 I could also encourage other people to be engaged in improving the
3213 world. Please, stay engaged. This world needs you, your love, your
3214 initiative -- now I cannot be part of that anymore."
3216 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
3217 ready. More than two years in the making, this release features improved
3218 client performance and hidden service reliability, better compatibility
3219 for Android, correct behavior for bridges that listen on more than
3220 one address, more extensible and flexible directory object handling,
3221 better reporting of network statistics, improved code security, and
3222 many many other features and bugfixes.
3224 o Major features (client performance):
3225 - When choosing which cells to relay first, relays now favor circuits
3226 that have been quiet recently, to provide lower latency for
3227 low-volume circuits. By default, relays enable or disable this
3228 feature based on a setting in the consensus. They can override
3229 this default by using the new "CircuitPriorityHalflife" config
3230 option. Design and code by Ian Goldberg, Can Tang, and Chris
3232 - Directory authorities now compute consensus weightings that instruct
3233 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
3234 and no flag. Clients use these weightings to distribute network load
3235 more evenly across these different relay types. The weightings are
3236 in the consensus so we can change them globally in the future. Extra
3237 thanks to "outofwords" for finding some nasty security bugs in
3238 the first implementation of this feature.
3240 o Major features (client performance, circuit build timeout):
3241 - Tor now tracks how long it takes to build client-side circuits
3242 over time, and adapts its timeout to local network performance.
3243 Since a circuit that takes a long time to build will also provide
3244 bad performance, we get significant latency improvements by
3245 discarding the slowest 20% of circuits. Specifically, Tor creates
3246 circuits more aggressively than usual until it has enough data
3247 points for a good timeout estimate. Implements proposal 151.
3248 - Circuit build timeout constants can be controlled by consensus
3249 parameters. We set good defaults for these parameters based on
3250 experimentation on broadband and simulated high-latency links.
3251 - Circuit build time learning can be disabled via consensus parameter
3252 or by the client via a LearnCircuitBuildTimeout config option. We
3253 also automatically disable circuit build time calculation if either
3254 AuthoritativeDirectory is set, or if we fail to write our state
3255 file. Implements ticket 1296.
3257 o Major features (relays use their capacity better):
3258 - Set SO_REUSEADDR socket option on all sockets, not just
3259 listeners. This should help busy exit nodes avoid running out of
3260 useable ports just because all the ports have been used in the
3261 near past. Resolves issue 2850.
3262 - Relays now save observed peak bandwidth throughput rates to their
3263 state file (along with total usage, which was already saved),
3264 so that they can determine their correct estimated bandwidth on
3265 restart. Resolves bug 1863, where Tor relays would reset their
3266 estimated bandwidth to 0 after restarting.
3267 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
3268 should give us approximately 40-50% more Guard-flagged nodes,
3269 improving the anonymity the Tor network can provide and also
3270 decreasing the dropoff in throughput that relays experience when
3271 they first get the Guard flag.
3272 - Directory authorities now take changes in router IP address and
3273 ORPort into account when determining router stability. Previously,
3274 if a router changed its IP or ORPort, the authorities would not
3275 treat it as having any downtime for the purposes of stability
3276 calculation, whereas clients would experience downtime since the
3277 change would take a while to propagate to them. Resolves issue 1035.
3278 - New AccelName and AccelDir options add support for dynamic OpenSSL
3279 hardware crypto acceleration engines.
3281 o Major features (relays control their load better):
3282 - Exit relays now try harder to block exit attempts from unknown
3283 relays, to make it harder for people to use them as one-hop proxies
3284 a la tortunnel. Controlled by the refuseunknownexits consensus
3285 parameter (currently enabled), or you can override it on your
3286 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
3287 based on a variant of proposal 163.
3288 - Add separate per-conn write limiting to go with the per-conn read
3289 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
3290 but never per-conn write limits.
3291 - New consensus params "bwconnrate" and "bwconnburst" to let us
3292 rate-limit client connections as they enter the network. It's
3293 controlled in the consensus so we can turn it on and off for
3294 experiments. It's starting out off. Based on proposal 163.
3296 o Major features (controllers):
3297 - Export GeoIP information on bridge usage to controllers even if we
3298 have not yet been running for 24 hours. Now Vidalia bridge operators
3299 can get more accurate and immediate feedback about their
3300 contributions to the network.
3301 - Add an __OwningControllerProcess configuration option and a
3302 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
3303 that when it exits, Tor will shut down. Implements feature 3049.
3305 o Major features (directory authorities):
3306 - Directory authorities now create, vote on, and serve multiple
3307 parallel formats of directory data as part of their voting process.
3308 Partially implements Proposal 162: "Publish the consensus in
3310 - Directory authorities now agree on and publish small summaries
3311 of router information that clients can use in place of regular
3312 server descriptors. This transition will allow Tor 0.2.3 clients
3313 to use far less bandwidth for downloading information about the
3314 network. Begins the implementation of Proposal 158: "Clients
3315 download consensus + microdescriptors".
3316 - The directory voting system is now extensible to use multiple hash
3317 algorithms for signatures and resource selection. Newer formats
3318 are signed with SHA256, with a possibility for moving to a better
3319 hash algorithm in the future.
3320 - Directory authorities can now vote on arbitary integer values as
3321 part of the consensus process. This is designed to help set
3322 network-wide parameters. Implements proposal 167.
3324 o Major features and bugfixes (node selection):
3325 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
3326 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
3327 options. Previously, we had been ambiguous in describing what
3328 counted as an "exit" node, and what operations exactly "StrictNodes
3329 0" would permit. This created confusion when people saw nodes built
3330 through unexpected circuits, and made it hard to tell real bugs from
3331 surprises. Now the intended behavior is:
3332 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
3333 a node that delivers user traffic outside the Tor network.
3334 . "Entry", in the context of EntryNodes, means a node used as the
3335 first hop of a multihop circuit. It doesn't include direct
3336 connections to directory servers.
3337 . "ExcludeNodes" applies to all nodes.
3338 . "StrictNodes" changes the behavior of ExcludeNodes only. When
3339 StrictNodes is set, Tor should avoid all nodes listed in
3340 ExcludeNodes, even when it will make user requests fail. When
3341 StrictNodes is *not* set, then Tor should follow ExcludeNodes
3342 whenever it can, except when it must use an excluded node to
3343 perform self-tests, connect to a hidden service, provide a
3344 hidden service, fulfill a .exit request, upload directory
3345 information, or fetch directory information.
3346 Collectively, the changes to implement the behavior fix bug 1090.
3347 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
3348 change during a config reload, mark and discard all our origin
3349 circuits. This fix should address edge cases where we change the
3350 config options and but then choose a circuit that we created before
3352 - Make EntryNodes config option much more aggressive even when
3353 StrictNodes is not set. Before it would prepend your requested
3354 entrynodes to your list of guard nodes, but feel free to use others
3355 after that. Now it chooses only from your EntryNodes if any of
3356 those are available, and only falls back to others if a) they're
3357 all down and b) StrictNodes is not set.
3358 - Now we refresh your entry guards from EntryNodes at each consensus
3359 fetch -- rather than just at startup and then they slowly rot as
3360 the network changes.
3361 - Add support for the country code "{??}" in torrc options like
3362 ExcludeNodes, to indicate all routers of unknown country. Closes
3364 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
3365 a node is listed in both, it's treated as excluded.
3366 - ExcludeNodes now applies to directory nodes -- as a preference if
3367 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
3368 Don't exclude all the directory authorities and set StrictNodes to 1
3369 unless you really want your Tor to break.
3370 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
3371 - ExcludeExitNodes now overrides .exit requests.
3372 - We don't use bridges listed in ExcludeNodes.
3373 - When StrictNodes is 1:
3374 . We now apply ExcludeNodes to hidden service introduction points
3375 and to rendezvous points selected by hidden service users. This
3376 can make your hidden service less reliable: use it with caution!
3377 . If we have used ExcludeNodes on ourself, do not try relay
3378 reachability self-tests.
3379 . If we have excluded all the directory authorities, we will not
3380 even try to upload our descriptor if we're a relay.
3381 . Do not honor .exit requests to an excluded node.
3382 - When the set of permitted nodes changes, we now remove any mappings
3383 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
3385 - We never cannibalize a circuit that had excluded nodes on it, even
3386 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
3387 - Improve log messages related to excluded nodes.
3389 o Major features (misc):
3390 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
3391 to help Tor build correctly for Android phones.
3392 - The options SocksPort, ControlPort, and so on now all accept a
3393 value "auto" that opens a socket on an OS-selected port. A
3394 new ControlPortWriteToFile option tells Tor to write its
3395 actual control port or ports to a chosen file. If the option
3396 ControlPortFileGroupReadable is set, the file is created as
3397 group-readable. Now users can run two Tor clients on the same
3398 system without needing to manually mess with parameters. Resolves
3399 part of ticket 3076.
3400 - Tor now supports tunneling all of its outgoing connections over
3401 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
3402 configuration options. Code by Christopher Davis.
3404 o Code security improvements:
3405 - Replace all potentially sensitive memory comparison operations
3406 with versions whose runtime does not depend on the data being
3407 compared. This will help resist a class of attacks where an
3408 adversary can use variations in timing information to learn
3409 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3410 implementation by Robert Ransom based partially on code by DJB.)
3411 - Enable Address Space Layout Randomization (ASLR) and Data Execution
3412 Prevention (DEP) by default on Windows to make it harder for
3413 attackers to exploit vulnerabilities. Patch from John Brooks.
3414 - New "--enable-gcc-hardening" ./configure flag (off by default)
3415 to turn on gcc compile time hardening options. It ensures
3416 that signed ints have defined behavior (-fwrapv), enables
3417 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
3418 with canaries (-fstack-protector-all), turns on ASLR protection if
3419 supported by the kernel (-fPIE, -pie), and adds additional security
3420 related warnings. Verified to work on Mac OS X and Debian Lenny.
3421 - New "--enable-linker-hardening" ./configure flag (off by default)
3422 to turn on ELF specific hardening features (relro, now). This does
3423 not work with Mac OS X or any other non-ELF binary format.
3424 - Always search the Windows system directory for system DLLs, and
3425 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
3426 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
3427 current and future memory pages via mlockall(). On supported
3428 platforms (modern Linux and probably BSD but not Windows or OS X),
3429 this should effectively disable any and all attempts to page out
3430 memory. This option requires that you start your Tor as root --
3431 if you use DisableAllSwap, please consider using the User option
3432 to properly reduce the privileges of your Tor.
3434 o Major bugfixes (crashes):
3435 - Fix crash bug on platforms where gmtime and localtime can return
3436 NULL. Windows 7 users were running into this one. Fixes part of bug
3437 2077. Bugfix on all versions of Tor. Found by boboper.
3438 - Introduce minimum/maximum values that clients will believe
3439 from the consensus. Now we'll have a better chance to avoid crashes
3440 or worse when a consensus param has a weird value.
3441 - Fix a rare crash bug that could occur when a client was configured
3442 with a large number of bridges. Fixes bug 2629; bugfix on
3443 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3444 - Do not crash when our configuration file becomes unreadable, for
3445 example due to a permissions change, between when we start up
3446 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3448 - If we're in the pathological case where there's no exit bandwidth
3449 but there is non-exit bandwidth, or no guard bandwidth but there
3450 is non-guard bandwidth, don't crash during path selection. Bugfix
3452 - Fix a crash bug when trying to initialize the evdns module in
3453 Libevent 2. Bugfix on 0.2.1.16-rc.
3455 o Major bugfixes (stability):
3456 - Fix an assert in parsing router descriptors containing IPv6
3457 addresses. This one took down the directory authorities when
3458 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3459 - Fix an uncommon assertion failure when running with DNSPort under
3460 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3461 - Treat an unset $HOME like an empty $HOME rather than triggering an
3462 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
3463 - More gracefully handle corrupt state files, removing asserts
3464 in favor of saving a backup and resetting state.
3465 - Instead of giving an assertion failure on an internal mismatch
3466 on estimated freelist size, just log a BUG warning and try later.
3467 Mitigates but does not fix bug 1125.
3468 - Fix an assert that got triggered when using the TestingTorNetwork
3469 configuration option and then issuing a GETINFO config-text control
3470 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
3471 - If the cached cert file is unparseable, warn but don't exit.
3473 o Privacy fixes (relays/bridges):
3474 - Don't list Windows capabilities in relay descriptors. We never made
3475 use of them, and maybe it's a bad idea to publish them. Bugfix
3477 - If the Nickname configuration option isn't given, Tor would pick a
3478 nickname based on the local hostname as the nickname for a relay.
3479 Because nicknames are not very important in today's Tor and the
3480 "Unnamed" nickname has been implemented, this is now problematic
3481 behavior: It leaks information about the hostname without being
3482 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
3483 introduced the Unnamed nickname. Reported by tagnaq.
3484 - Maintain separate TLS contexts and certificates for incoming and
3485 outgoing connections in bridge relays. Previously we would use the
3486 same TLS contexts and certs for incoming and outgoing connections.
3487 Bugfix on 0.2.0.3-alpha; addresses bug 988.
3488 - Maintain separate identity keys for incoming and outgoing TLS
3489 contexts in bridge relays. Previously we would use the same
3490 identity keys for incoming and outgoing TLS contexts. Bugfix on
3491 0.2.0.3-alpha; addresses the other half of bug 988.
3492 - Make the bridge directory authority refuse to answer directory
3493 requests for "all descriptors". It used to include bridge
3494 descriptors in its answer, which was a major information leak.
3495 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3497 o Privacy fixes (clients):
3498 - When receiving a hidden service descriptor, check that it is for
3499 the hidden service we wanted. Previously, Tor would store any
3500 hidden service descriptors that a directory gave it, whether it
3501 wanted them or not. This wouldn't have let an attacker impersonate
3502 a hidden service, but it did let directories pre-seed a client
3503 with descriptors that it didn't want. Bugfix on 0.0.6.
3504 - Start the process of disabling ".exit" address notation, since it
3505 can be used for a variety of esoteric application-level attacks
3506 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
3508 - Reject attempts at the client side to open connections to private
3509 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
3510 a randomly chosen exit node. Attempts to do so are always
3511 ill-defined, generally prevented by exit policies, and usually
3512 in error. This will also help to detect loops in transparent
3513 proxy configurations. You can disable this feature by setting
3514 "ClientRejectInternalAddresses 0" in your torrc.
3515 - Log a notice when we get a new control connection. Now it's easier
3516 for security-conscious users to recognize when a local application
3517 is knocking on their controller door. Suggested by bug 1196.
3519 o Privacy fixes (newnym):
3520 - Avoid linkability based on cached hidden service descriptors: forget
3521 all hidden service descriptors cached as a client when processing a
3522 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3523 - On SIGHUP, do not clear out all TrackHostExits mappings, client
3524 DNS cache entries, and virtual address mappings: that's what
3525 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
3526 - Don't attach new streams to old rendezvous circuits after SIGNAL
3527 NEWNYM. Previously, we would keep using an existing rendezvous
3528 circuit if it remained open (i.e. if it were kept open by a
3529 long-lived stream, or if a new stream were attached to it before
3530 Tor could notice that it was old and no longer in use). Bugfix on
3531 0.1.1.15-rc; fixes bug 3375.
3533 o Major bugfixes (relay bandwidth accounting):
3534 - Fix a bug that could break accounting on 64-bit systems with large
3535 time_t values, making them hibernate for impossibly long intervals.
3536 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3537 - Fix a bug in bandwidth accounting that could make us use twice
3538 the intended bandwidth when our interval start changes due to
3539 daylight saving time. Now we tolerate skew in stored vs computed
3540 interval starts: if the start of the period changes by no more than
3541 50% of the period's duration, we remember bytes that we transferred
3542 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
3544 o Major bugfixes (bridges):
3545 - Bridges now use "reject *:*" as their default exit policy. Bugfix
3546 on 0.2.0.3-alpha. Fixes bug 1113.
3547 - If you configure your bridge with a known identity fingerprint,
3548 and the bridge authority is unreachable (as it is in at least
3549 one country now), fall back to directly requesting the descriptor
3550 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
3552 - Fix a bug where bridge users who configure the non-canonical
3553 address of a bridge automatically switch to its canonical
3554 address. If a bridge listens at more than one address, it
3555 should be able to advertise those addresses independently and
3556 any non-blocked addresses should continue to work. Bugfix on Tor
3557 0.2.0.3-alpha. Fixes bug 2510.
3558 - If you configure Tor to use bridge A, and then quit and
3559 configure Tor to use bridge B instead (or if you change Tor
3560 to use bridge B via the controller), it would happily continue
3561 to use bridge A if it's still reachable. While this behavior is
3562 a feature if your goal is connectivity, in some scenarios it's a
3563 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3564 - When the controller configures a new bridge, don't wait 10 to 60
3565 seconds before trying to fetch its descriptor. Bugfix on
3566 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
3568 o Major bugfixes (directory authorities):
3569 - Many relays have been falling out of the consensus lately because
3570 not enough authorities know about their descriptor for them to get
3571 a majority of votes. When we deprecated the v2 directory protocol,
3572 we got rid of the only way that v3 authorities can hear from each
3573 other about other descriptors. Now authorities examine every v3
3574 vote for new descriptors, and fetch them from that authority. Bugfix
3576 - Authorities could be tricked into giving out the Exit flag to relays
3577 that didn't allow exiting to any ports. This bug could screw
3578 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
3579 1238. Bug discovered by Martin Kowalczyk.
3580 - If all authorities restart at once right before a consensus vote,
3581 nobody will vote about "Running", and clients will get a consensus
3582 with no usable relays. Instead, authorities refuse to build a
3583 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
3585 o Major bugfixes (stream-level fairness):
3586 - When receiving a circuit-level SENDME for a blocked circuit, try
3587 to package cells fairly from all the streams that had previously
3588 been blocked on that circuit. Previously, we had started with the
3589 oldest stream, and allowed each stream to potentially exhaust
3590 the circuit's package window. This gave older streams on any
3591 given circuit priority over newer ones. Fixes bug 1937. Detected
3592 originally by Camilo Viecco. This bug was introduced before the
3593 first Tor release, in svn commit r152: it is the new winner of
3594 the longest-lived bug prize.
3595 - Fix a stream fairness bug that would cause newer streams on a given
3596 circuit to get preference when reading bytes from the origin or
3597 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3598 introduced before the first Tor release, in svn revision r152.
3599 - When the exit relay got a circuit-level sendme cell, it started
3600 reading on the exit streams, even if had 500 cells queued in the
3601 circuit queue already, so the circuit queue just grew and grew in
3602 some cases. We fix this by not re-enabling reading on receipt of a
3603 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
3604 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
3606 - Newly created streams were allowed to read cells onto circuits,
3607 even if the circuit's cell queue was blocked and waiting to drain.
3608 This created potential unfairness, as older streams would be
3609 blocked, but newer streams would gladly fill the queue completely.
3610 We add code to detect this situation and prevent any stream from
3611 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
3614 o Major bugfixes (hidden services):
3615 - Apply circuit timeouts to opened hidden-service-related circuits
3616 based on the correct start time. Previously, we would apply the
3617 circuit build timeout based on time since the circuit's creation;
3618 it was supposed to be applied based on time since the circuit
3619 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
3620 - Improve hidden service robustness: When we find that we have
3621 extended a hidden service's introduction circuit to a relay not
3622 listed as an introduction point in the HS descriptor we currently
3623 have, retry with an introduction point from the current
3624 descriptor. Previously we would just give up. Fixes bugs 1024 and
3625 1930; bugfix on 0.2.0.10-alpha.
3626 - Directory authorities now use data collected from their own
3627 uptime observations when choosing whether to assign the HSDir flag
3628 to relays, instead of trusting the uptime value the relay reports in
3629 its descriptor. This change helps prevent an attack where a small
3630 set of nodes with frequently-changing identity keys can blackhole
3631 a hidden service. (Only authorities need upgrade; others will be
3632 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3633 - Stop assigning the HSDir flag to relays that disable their
3634 DirPort (and thus will refuse to answer directory requests). This
3635 fix should dramatically improve the reachability of hidden services:
3636 hidden services and hidden service clients pick six HSDir relays
3637 to store and retrieve the hidden service descriptor, and currently
3638 about half of the HSDir relays will refuse to work. Bugfix on
3639 0.2.0.10-alpha; fixes part of bug 1693.
3641 o Major bugfixes (misc):
3642 - Clients now stop trying to use an exit node associated with a given
3643 destination by TrackHostExits if they fail to reach that exit node.
3644 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
3645 - Fix a regression that caused Tor to rebind its ports if it receives
3646 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
3647 - Remove an extra pair of quotation marks around the error
3648 message in control-port STATUS_GENERAL BUG events. Bugfix on
3649 0.1.2.6-alpha; fixes bug 3732.
3651 o Minor features (relays):
3652 - Ensure that no empty [dirreq-](read|write)-history lines are added
3653 to an extrainfo document. Implements ticket 2497.
3654 - When bandwidth accounting is enabled, be more generous with how
3655 much bandwidth we'll use up before entering "soft hibernation".
3656 Previously, we'd refuse new connections and circuits once we'd
3657 used up 95% of our allotment. Now, we use up 95% of our allotment,
3658 AND make sure that we have no more than 500MB (or 3 hours of
3659 expected traffic, whichever is lower) remaining before we enter
3661 - Relays now log the reason for publishing a new relay descriptor,
3662 so we have a better chance of hunting down instances of bug 1810.
3663 Resolves ticket 3252.
3664 - Log a little more clearly about the times at which we're no longer
3665 accepting new connections (e.g. due to hibernating). Resolves
3667 - When AllowSingleHopExits is set, print a warning to explain to the
3668 relay operator why most clients are avoiding her relay.
3669 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3670 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3671 clients are already deprecated because of security bugs.
3673 o Minor features (network statistics):
3674 - Directory mirrors that set "DirReqStatistics 1" write statistics
3675 about directory requests to disk every 24 hours. As compared to the
3676 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
3677 improvements: 1) stats are written to disk exactly every 24 hours;
3678 2) estimated shares of v2 and v3 requests are determined as mean
3679 values, not at the end of a measurement period; 3) unresolved
3680 requests are listed with country code '??'; 4) directories also
3681 measure download times.
3682 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
3683 number of exit streams and transferred bytes per port to disk every
3685 - Relays that set "CellStatistics 1" write statistics on how long
3686 cells spend in their circuit queues to disk every 24 hours.
3687 - Entry nodes that set "EntryStatistics 1" write statistics on the
3688 rough number and origins of connecting clients to disk every 24
3690 - Relays that write any of the above statistics to disk and set
3691 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
3692 their extra-info documents. Implements proposal 166.
3694 o Minor features (GeoIP and statistics):
3695 - Provide a log message stating which geoip file we're parsing
3696 instead of just stating that we're parsing the geoip file.
3697 Implements ticket 2432.
3698 - Make sure every relay writes a state file at least every 12 hours.
3699 Previously, a relay could go for weeks without writing its state
3700 file, and on a crash could lose its bandwidth history, capacity
3701 estimates, client country statistics, and so on. Addresses bug 3012.
3702 - Relays report the number of bytes spent on answering directory
3703 requests in extra-info descriptors similar to {read,write}-history.
3704 Implements enhancement 1790.
3705 - Report only the top 10 ports in exit-port stats in order not to
3706 exceed the maximum extra-info descriptor length of 50 KB. Implements
3708 - If writing the state file to disk fails, wait up to an hour before
3709 retrying again, rather than trying again each second. Fixes bug
3710 2346; bugfix on Tor 0.1.1.3-alpha.
3711 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
3712 when we switch from being a public relay to a bridge. Otherwise
3713 there will still be clients that see the relay in their consensus,
3714 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
3716 - Update to the August 2 2011 Maxmind GeoLite Country database.
3718 o Minor features (clients):
3719 - When expiring circuits, use microsecond timers rather than
3720 one-second timers. This can avoid an unpleasant situation where a
3721 circuit is launched near the end of one second and expired right
3722 near the beginning of the next, and prevent fluctuations in circuit
3724 - If we've configured EntryNodes and our network goes away and/or all
3725 our entrynodes get marked down, optimistically retry them all when
3726 a new socks application request appears. Fixes bug 1882.
3727 - Always perform router selections using weighted relay bandwidth,
3728 even if we don't need a high capacity circuit at the time. Non-fast
3729 circuits now only differ from fast ones in that they can use relays
3730 not marked with the Fast flag. This "feature" could turn out to
3731 be a horrible bug; we should investigate more before it goes into
3733 - When we run out of directory information such that we can't build
3734 circuits, but then get enough that we can build circuits, log when
3735 we actually construct a circuit, so the user has a better chance of
3736 knowing what's going on. Fixes bug 1362.
3737 - Log SSL state transitions at debug level during handshake, and
3738 include SSL states in error messages. This may help debug future
3739 SSL handshake issues.
3741 o Minor features (directory authorities):
3742 - When a router changes IP address or port, authorities now launch
3743 a new reachability test for it. Implements ticket 1899.
3744 - Directory authorities now reject relays running any versions of
3745 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3746 known bugs that keep RELAY_EARLY cells from working on rendezvous
3747 circuits. Followup to fix for bug 2081.
3748 - Directory authorities now reject relays running any version of Tor
3749 older than 0.2.0.26-rc. That version is the earliest that fetches
3750 current directory information correctly. Fixes bug 2156.
3751 - Directory authorities now do an immediate reachability check as soon
3752 as they hear about a new relay. This change should slightly reduce
3753 the time between setting up a relay and getting listed as running
3754 in the consensus. It should also improve the time between setting
3755 up a bridge and seeing use by bridge users.
3756 - Directory authorities no longer launch a TLS connection to every
3757 relay as they startup. Now that we have 2k+ descriptors cached,
3758 the resulting network hiccup is becoming a burden. Besides,
3759 authorities already avoid voting about Running for the first half
3760 hour of their uptime.
3761 - Directory authorities now log the source of a rejected POSTed v3
3762 networkstatus vote, so we can track failures better.
3763 - Backport code from 0.2.3.x that allows directory authorities to
3764 clean their microdescriptor caches. Needed to resolve bug 2230.
3766 o Minor features (hidden services):
3767 - Use computed circuit-build timeouts to decide when to launch
3768 parallel introduction circuits for hidden services. (Previously,
3769 we would retry after 15 seconds.)
3770 - Don't allow v0 hidden service authorities to act as clients.
3771 Required by fix for bug 3000.
3772 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3773 by fix for bug 3000.
3774 - Make hidden services work better in private Tor networks by not
3775 requiring any uptime to join the hidden service descriptor
3776 DHT. Implements ticket 2088.
3777 - Log (at info level) when purging pieces of hidden-service-client
3778 state because of SIGNAL NEWNYM.
3780 o Minor features (controller interface):
3781 - New "GETINFO net/listeners/(type)" controller command to return
3782 a list of addresses and ports that are bound for listeners for a
3783 given connection type. This is useful when the user has configured
3784 "SocksPort auto" and the controller needs to know which port got
3785 chosen. Resolves another part of ticket 3076.
3786 - Have the controller interface give a more useful message than
3787 "Internal Error" in response to failed GETINFO requests.
3788 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
3789 event, to give information on the current rate of circuit timeouts
3790 over our stored history.
3791 - The 'EXTENDCIRCUIT' control port command can now be used with
3792 a circ id of 0 and no path. This feature will cause Tor to build
3793 a new 'fast' general purpose circuit using its own path selection
3795 - Added a BUILDTIMEOUT_SET controller event to describe changes
3796 to the circuit build timeout.
3797 - New controller command "getinfo config-text". It returns the
3798 contents that Tor would write if you send it a SAVECONF command,
3799 so the controller can write the file to disk itself.
3801 o Minor features (controller protocol):
3802 - Add a new ControlSocketsGroupWritable configuration option: when
3803 it is turned on, ControlSockets are group-writeable by the default
3804 group of the current user. Patch by Jérémy Bobbio; implements
3806 - Tor now refuses to create a ControlSocket in a directory that is
3807 world-readable (or group-readable if ControlSocketsGroupWritable
3808 is 0). This is necessary because some operating systems do not
3809 enforce permissions on an AF_UNIX sockets. Permissions on the
3810 directory holding the socket, however, seems to work everywhere.
3811 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
3812 not. This would lead to a cookie that is still not group readable.
3813 Closes bug 1843. Suggested by katmagic.
3814 - Future-proof the controller protocol a bit by ignoring keyword
3815 arguments we do not recognize.
3817 o Minor features (more useful logging):
3818 - Revise most log messages that refer to nodes by nickname to
3819 instead use the "$key=nickname at address" format. This should be
3820 more useful, especially since nicknames are less and less likely
3821 to be unique. Resolves ticket 3045.
3822 - When an HTTPS proxy reports "403 Forbidden", we now explain
3823 what it means rather than calling it an unexpected status code.
3824 Closes bug 2503. Patch from Michael Yakubovich.
3825 - Rate-limit a warning about failures to download v2 networkstatus
3826 documents. Resolves part of bug 1352.
3827 - Rate-limit the "your application is giving Tor only an IP address"
3828 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
3829 - Rate-limit "Failed to hand off onionskin" warnings.
3830 - When logging a rate-limited warning, we now mention how many messages
3831 got suppressed since the last warning.
3832 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
3833 2 no signature, 4 required" messages about consensus signatures
3834 easier to read, and make sure they get logged at the same severity
3835 as the messages explaining which keys are which. Fixes bug 1290.
3836 - Don't warn when we have a consensus that we can't verify because
3837 of missing certificates, unless those certificates are ones
3838 that we have been trying and failing to download. Fixes bug 1145.
3840 o Minor features (log domains):
3841 - Add documentation for configuring logging at different severities in
3842 different log domains. We've had this feature since 0.2.1.1-alpha,
3843 but for some reason it never made it into the manpage. Fixes
3845 - Make it simpler to specify "All log domains except for A and B".
3846 Previously you needed to say "[*,~A,~B]". Now you can just say
3848 - Add a "LogMessageDomains 1" option to include the domains of log
3849 messages along with the messages. Without this, there's no way
3850 to use log domains without reading the source or doing a lot
3852 - Add a new "Handshake" log domain for activities that happen
3853 during the TLS handshake.
3855 o Minor features (build process):
3856 - Make compilation with clang possible when using
3857 "--enable-gcc-warnings" by removing two warning options that clang
3858 hasn't implemented yet and by fixing a few warnings. Resolves
3860 - Detect platforms that brokenly use a signed size_t, and refuse to
3861 build there. Found and analyzed by doorss and rransom.
3862 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3864 - Add support for statically linking zlib by specifying
3865 "--enable-static-zlib", to go with our support for statically
3866 linking openssl and libevent. Resolves bug 1358.
3867 - Instead of adding the svn revision to the Tor version string, report
3868 the git commit (when we're building from a git checkout).
3869 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
3871 - New --digests command-line switch to output the digests of the
3872 source files Tor was built with.
3873 - Generate our manpage and HTML documentation using Asciidoc. This
3874 change should make it easier to maintain the documentation, and
3875 produce nicer HTML. The build process fails if asciidoc cannot
3876 be found and building with asciidoc isn't disabled (via the
3877 "--disable-asciidoc" argument to ./configure. Skipping the manpage
3878 speeds up the build considerably.
3880 o Minor features (options / torrc):
3881 - Warn when the same option is provided more than once in a torrc
3882 file, on the command line, or in a single SETCONF statement, and
3883 the option is one that only accepts a single line. Closes bug 1384.
3884 - Warn when the user configures two HiddenServiceDir lines that point
3885 to the same directory. Bugfix on 0.0.6 (the version introducing
3886 HiddenServiceDir); fixes bug 3289.
3887 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
3888 do individual connection-level rate limiting of clients. The torrc
3889 config options with the same names trump the consensus params, if
3890 both are present. Replaces the old "bwconnrate" and "bwconnburst"
3891 consensus params which were broken from 0.2.2.7-alpha through
3892 0.2.2.14-alpha. Closes bug 1947.
3893 - New config option "WarnUnsafeSocks 0" disables the warning that
3894 occurs whenever Tor receives a socks handshake using a version of
3895 the socks protocol that can only provide an IP address (rather
3896 than a hostname). Setups that do DNS locally over Tor are fine,
3897 and we shouldn't spam the logs in that case.
3898 - New config option "CircuitStreamTimeout" to override our internal
3899 timeout schedule for how many seconds until we detach a stream from
3900 a circuit and try a new circuit. If your network is particularly
3901 slow, you might want to set this to a number like 60.
3902 - New options for SafeLogging to allow scrubbing only log messages
3903 generated while acting as a relay. Specify "SafeLogging relay" if
3904 you want to ensure that only messages known to originate from
3905 client use of the Tor process will be logged unsafely.
3906 - Time and memory units in the configuration file can now be set to
3907 fractional units. For example, "2.5 GB" is now a valid value for
3909 - Support line continuations in the torrc config file. If a line
3910 ends with a single backslash character, the newline is ignored, and
3911 the configuration value is treated as continuing on the next line.
3914 o Minor features (unit tests):
3915 - Revise our unit tests to use the "tinytest" framework, so we
3916 can run tests in their own processes, have smarter setup/teardown
3917 code, and so on. The unit test code has moved to its own
3918 subdirectory, and has been split into multiple modules.
3919 - Add a unit test for cross-platform directory-listing code.
3920 - Add some forgotten return value checks during unit tests. Found
3922 - Use GetTempDir to find the proper temporary directory location on
3923 Windows when generating temporary files for the unit tests. Patch
3926 o Minor features (misc):
3927 - The "torify" script now uses torsocks where available.
3928 - Make Libevent log messages get delivered to controllers later,
3929 and not from inside the Libevent log handler. This prevents unsafe
3930 reentrant Libevent calls while still letting the log messages
3932 - Certain Tor clients (such as those behind check.torproject.org) may
3933 want to fetch the consensus in an extra early manner. To enable this
3934 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
3935 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
3936 as only certain clients who must have this information sooner should
3938 - Expand homedirs passed to tor-checkkey. This should silence a
3939 coverity complaint about passing a user-supplied string into
3940 open() without checking it.
3941 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
3942 used on bridges, and it makes bridge scanning somewhat easier.
3943 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3944 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3946 o Minor bugfixes (relays):
3947 - When a relay decides that its DNS is too broken for it to serve
3948 as an exit server, it advertised itself as a non-exit, but
3949 continued to act as an exit. This could create accidental
3950 partitioning opportunities for users. Instead, if a relay is
3951 going to advertise reject *:* as its exit policy, it should
3952 really act with exit policy "reject *:*". Fixes bug 2366.
3953 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3954 - Publish a router descriptor even if generating an extra-info
3955 descriptor fails. Previously we would not publish a router
3956 descriptor without an extra-info descriptor; this can cause fast
3957 exit relays collecting exit-port statistics to drop from the
3958 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
3959 - When we're trying to guess whether we know our IP address as
3960 a relay, we would log various ways that we failed to guess
3961 our address, but never log that we ended up guessing it
3962 successfully. Now add a log line to help confused and anxious
3963 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
3964 - For bandwidth accounting, calculate our expected bandwidth rate
3965 based on the time during which we were active and not in
3966 soft-hibernation during the last interval. Previously, we were
3967 also considering the time spent in soft-hibernation. If this
3968 was a long time, we would wind up underestimating our bandwidth
3969 by a lot, and skewing our wakeup time towards the start of the
3970 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
3971 - Demote a confusing TLS warning that relay operators might get when
3972 someone tries to talk to their ORPort. It is not the operator's
3973 fault, nor can they do anything about it. Fixes bug 1364; bugfix
3975 - Change "Application request when we're believed to be offline."
3976 notice to "Application request when we haven't used client
3977 functionality lately.", to clarify that it's not an error. Bugfix
3978 on 0.0.9.3; fixes bug 1222.
3980 o Minor bugfixes (bridges):
3981 - When a client starts or stops using bridges, never use a circuit
3982 that was built before the configuration change. This behavior could
3983 put at risk a user who uses bridges to ensure that her traffic
3984 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
3986 - Do not reset the bridge descriptor download status every time we
3987 re-parse our configuration or get a configuration change. Fixes
3988 bug 3019; bugfix on 0.2.0.3-alpha.
3989 - Users couldn't configure a regular relay to be their bridge. It
3990 didn't work because when Tor fetched the bridge descriptor, it found
3991 that it already had it, and didn't realize that the purpose of the
3992 descriptor had changed. Now we replace routers with a purpose other
3993 than bridge with bridge descriptors when fetching them. Bugfix on
3994 0.1.1.9-alpha. Fixes bug 1776.
3995 - In the special case where you configure a public exit relay as your
3996 bridge, Tor would be willing to use that exit relay as the last
3997 hop in your circuit as well. Now we fail that circuit instead.
3998 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
4000 o Minor bugfixes (clients):
4001 - We now ask the other side of a stream (the client or the exit)
4002 for more data on that stream when the amount of queued data on
4003 that stream dips low enough. Previously, we wouldn't ask the
4004 other side for more data until either it sent us more data (which
4005 it wasn't supposed to do if it had exhausted its window!) or we
4006 had completely flushed all our queued data. This flow control fix
4007 should improve throughput. Fixes bug 2756; bugfix on the earliest
4008 released versions of Tor (svn commit r152).
4009 - When a client finds that an origin circuit has run out of 16-bit
4010 stream IDs, we now mark it as unusable for new streams. Previously,
4011 we would try to close the entire circuit. Bugfix on 0.0.6.
4012 - Make it explicit that we don't cannibalize one-hop circuits. This
4013 happens in the wild, but doesn't turn out to be a problem because
4014 we fortunately don't use those circuits. Many thanks to outofwords
4015 for the initial analysis and to swissknife who confirmed that
4016 two-hop circuits are actually created.
4017 - Resolve an edge case in path weighting that could make us misweight
4018 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
4019 - Make the DNSPort option work with libevent 2.x. Don't alter the
4020 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4022 o Minor bugfixes (directory authorities):
4023 - Make directory authorities more accurate at recording when
4024 relays that have failed several reachability tests became
4025 unreachable, so we can provide more accuracy at assigning Stable,
4026 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
4027 - Directory authorities are now more robust to hops back in time
4028 when calculating router stability. Previously, if a run of uptime
4029 or downtime appeared to be negative, the calculation could give
4030 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
4032 - Directory authorities will now attempt to download consensuses
4033 if their own efforts to make a live consensus have failed. This
4034 change means authorities that restart will fetch a valid
4035 consensus, and it means authorities that didn't agree with the
4036 current consensus will still fetch and serve it if it has enough
4037 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
4038 - Never vote for a server as "Running" if we have a descriptor for
4039 it claiming to be hibernating, and that descriptor was published
4040 more recently than our last contact with the server. Bugfix on
4041 0.2.0.3-alpha; fixes bug 911.
4042 - Directory authorities no longer change their opinion of, or vote on,
4043 whether a router is Running, unless they have themselves been
4044 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
4047 o Minor bugfixes (hidden services):
4048 - Log malformed requests for rendezvous descriptors as protocol
4049 warnings, not warnings. Also, use a more informative log message
4050 in case someone sees it at log level warning without prior
4051 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
4052 - Accept hidden service descriptors if we think we might be a hidden
4053 service directory, regardless of what our consensus says. This
4054 helps robustness, since clients and hidden services can sometimes
4055 have a more up-to-date view of the network consensus than we do,
4056 and if they think that the directory authorities list us a HSDir,
4057 we might actually be one. Related to bug 2732; bugfix on
4059 - Correct the warning displayed when a rendezvous descriptor exceeds
4060 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4062 - Clients and hidden services now use HSDir-flagged relays for hidden
4063 service descriptor downloads and uploads even if the relays have no
4064 DirPort set and the client has disabled TunnelDirConns. This will
4065 eventually allow us to give the HSDir flag to relays with no
4066 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
4067 - Only limit the lengths of single HS descriptors, even when multiple
4068 HS descriptors are published to an HSDir relay in a single POST
4069 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
4071 o Minor bugfixes (controllers):
4072 - Allow GETINFO fingerprint to return a fingerprint even when
4073 we have not yet built a router descriptor. Fixes bug 3577;
4074 bugfix on 0.2.0.1-alpha.
4075 - Send a SUCCEEDED stream event to the controller when a reverse
4076 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4077 discovered by katmagic.
4078 - Remove a trailing asterisk from "exit-policy/default" in the
4079 output of the control port command "GETINFO info/names". Bugfix
4081 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
4082 2917. Bugfix on 0.1.1.1-alpha.
4083 - When we restart our relay, we might get a successful connection
4084 from the outside before we've started our reachability tests,
4085 triggering a warning: "ORPort found reachable, but I have no
4086 routerinfo yet. Failing to inform controller of success." This
4087 bug was harmless unless Tor is running under a controller
4088 like Vidalia, in which case the controller would never get a
4089 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4091 - When a controller changes TrackHostExits, remove mappings for
4092 hosts that should no longer have their exits tracked. Bugfix on
4094 - When a controller changes VirtualAddrNetwork, remove any mappings
4095 for hosts that were automapped to the old network. Bugfix on
4097 - When a controller changes one of the AutomapHosts* options, remove
4098 any mappings for hosts that should no longer be automapped. Bugfix
4100 - Fix an off-by-one error in calculating some controller command
4101 argument lengths. Fortunately, this mistake is harmless since
4102 the controller code does redundant NUL termination too. Found by
4103 boboper. Bugfix on 0.1.1.1-alpha.
4104 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4105 would return "551 Internal error" rather than "552 Unrecognized key
4106 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4107 - Don't spam the controller with events when we have no file
4108 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4109 for log messages was already solved from bug 748.)
4110 - Emit a GUARD DROPPED controller event for a case we missed.
4111 - Ensure DNS requests launched by "RESOLVE" commands from the
4112 controller respect the __LeaveStreamsUnattached setconf options. The
4113 same goes for requests launched via DNSPort or transparent
4114 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4116 o Minor bugfixes (config options):
4117 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4118 Change the limit to 512 characters by removing base64 newlines.
4119 Fixes bug 2752. Fix by Michael Yakubovich.
4120 - Complain if PublishServerDescriptor is given multiple arguments that
4121 include 0 or 1. This configuration will be rejected in the future.
4122 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4123 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4124 Bugfix on 0.2.0.13-alpha; closes bug 928.
4126 o Minor bugfixes (log subsystem fixes):
4127 - When unable to format an address as a string, report its value
4128 as "???" rather than reusing the last formatted address. Bugfix
4130 - Be more consistent in our treatment of file system paths. "~" should
4131 get expanded to the user's home directory in the Log config option.
4132 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
4133 feature for the -f and --DataDirectory options.
4135 o Minor bugfixes (memory management):
4136 - Don't stack-allocate the list of supplementary GIDs when we're
4137 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4138 could take up to 256K, which is way too much stack. Found by
4139 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4140 - Save a couple bytes in memory allocation every time we escape
4141 certain characters in a string. Patch from Florian Zumbiehl.
4143 o Minor bugfixes (protocol correctness):
4144 - When checking for 1024-bit keys, check for 1024 bits, not 128
4145 bytes. This allows Tor to correctly discard keys of length 1017
4146 through 1023. Bugfix on 0.0.9pre5.
4147 - Require that introduction point keys and onion handshake keys
4148 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4150 - Handle SOCKS messages longer than 128 bytes long correctly, rather
4151 than waiting forever for them to finish. Fixes bug 2330; bugfix
4152 on 0.2.0.16-alpha. Found by doorss.
4153 - Never relay a cell for a circuit we have already destroyed.
4154 Between marking a circuit as closeable and finally closing it,
4155 it may have been possible for a few queued cells to get relayed,
4156 even though they would have been immediately dropped by the next
4157 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4158 - Never queue a cell for a circuit that's already been marked
4160 - Fix a spec conformance issue: the network-status-version token
4161 must be the first token in a v3 consensus or vote. Discovered by
4162 "parakeep". Bugfix on 0.2.0.3-alpha.
4163 - A networkstatus vote must contain exactly one signature. Spec
4164 conformance issue. Bugfix on 0.2.0.3-alpha.
4165 - When asked about a DNS record type we don't support via a
4166 client DNSPort, reply with NOTIMPL rather than an empty
4167 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4168 - Make more fields in the controller protocol case-insensitive, since
4169 control-spec.txt said they were.
4171 o Minor bugfixes (log messages):
4172 - Fix a log message that said "bits" while displaying a value in
4173 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4175 - Downgrade "no current certificates known for authority" message from
4176 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
4177 - Correctly describe errors that occur when generating a TLS object.
4178 Previously we would attribute them to a failure while generating a
4179 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
4181 - Fix an instance where a Tor directory mirror might accidentally
4182 log the IP address of a misbehaving Tor client. Bugfix on
4184 - Stop logging at severity 'warn' when some other Tor client tries
4185 to establish a circuit with us using weak DH keys. It's a protocol
4186 violation, but that doesn't mean ordinary users need to hear about
4187 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
4188 - If your relay can't keep up with the number of incoming create
4189 cells, it would log one warning per failure into your logs. Limit
4190 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
4192 o Minor bugfixes (build fixes):
4193 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4194 - When warning about missing zlib development packages during compile,
4195 give the correct package names. Bugfix on 0.2.0.1-alpha.
4196 - Fix warnings that newer versions of autoconf produce during
4197 ./autogen.sh. These warnings appear to be harmless in our case,
4198 but they were extremely verbose. Fixes bug 2020.
4199 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
4202 o Minor bugfixes (portability):
4203 - Write several files in text mode, on OSes that distinguish text
4204 mode from binary mode (namely, Windows). These files are:
4205 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4206 that collect those statistics; 'client_keys' and 'hostname' for
4207 hidden services that use authentication; and (in the tor-gencert
4208 utility) newly generated identity and signing keys. Previously,
4209 we wouldn't specify text mode or binary mode, leading to an
4210 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4211 the DirRecordUsageByCountry option which would have triggered
4212 the assertion failure was added), although this assertion failure
4213 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4214 - Selectively disable deprecation warnings on OS X because Lion
4215 started deprecating the shipped copy of openssl. Fixes bug 3643.
4216 - Use a wide type to hold sockets when built for 64-bit Windows.
4218 - Fix an issue that prevented static linking of libevent on
4219 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
4220 where we introduced the "--with-static-libevent" configure option.
4221 - Fix a bug with our locking implementation on Windows that couldn't
4222 correctly detect when a file was already locked. Fixes bug 2504,
4223 bugfix on 0.2.1.6-alpha.
4224 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4226 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
4227 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
4230 o Minor bugfixes (code correctness):
4231 - Always NUL-terminate the sun_path field of a sockaddr_un before
4232 passing it to the kernel. (Not a security issue: kernels are
4233 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4234 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4235 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4236 expect it to emit a CRLF iff the format string ends with CRLF;
4237 it actually emitted a CRLF iff (a) the format string ended with
4238 CRLF or (b) the resulting string was over 1023 characters long or
4239 (c) the format string did not end with CRLF *and* the resulting
4240 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4241 fixes part of bug 3407.
4242 - Make send_control_event_impl()'s behaviour sane. Its callers
4243 expect it to always emit a CRLF at the end of the string; it
4244 might have emitted extra control characters as well. Bugfix on
4245 0.1.1.9-alpha; fixes another part of bug 3407.
4246 - Make crypto_rand_int() check the value of its input correctly.
4247 Previously, it accepted values up to UINT_MAX, but could return a
4248 negative number if given a value above INT_MAX+1. Found by George
4249 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4250 - Fix a potential null-pointer dereference while computing a
4251 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4253 - If we fail to compute the identity digest of a v3 legacy keypair,
4254 warn, and don't use a buffer-full of junk instead. Bugfix on
4255 0.2.1.1-alpha; fixes bug 3106.
4256 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4257 where if the function had ever in the future been used to check
4258 for the presence of a too-large number, it would have given an
4259 incorrect result. (Fortunately, we only used it for 16-bit
4260 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4261 - Be more careful about reporting the correct error from a failed
4262 connect() system call. Under some circumstances, it was possible to
4263 look at an incorrect value for errno when sending the end reason.
4264 Bugfix on 0.1.0.1-rc.
4265 - Correctly handle an "impossible" overflow cases in connection byte
4266 counting, where we write or read more than 4GB on an edge connection
4267 in a single second. Bugfix on 0.1.2.8-beta.
4268 - Avoid a double mark-for-free warning when failing to attach a
4269 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
4271 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
4272 found by "cypherpunks". This bug was introduced before the first
4273 Tor release, in svn commit r110.
4274 - Fix a bug in bandwidth history state parsing that could have been
4275 triggered if a future version of Tor ever changed the timing
4276 granularity at which bandwidth history is measured. Bugfix on
4278 - Add assertions to check for overflow in arguments to
4279 base32_encode() and base32_decode(); fix a signed-unsigned
4280 comparison there too. These bugs are not actually reachable in Tor,
4281 but it's good to prevent future errors too. Found by doorss.
4282 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4284 - Set target port in get_interface_address6() correctly. Bugfix
4285 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
4286 - Fix an impossible-to-actually-trigger buffer overflow in relay
4287 descriptor generation. Bugfix on 0.1.0.15.
4288 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
4290 o Minor bugfixes (code improvements):
4291 - After we free an internal connection structure, overwrite it
4292 with a different memory value than we use for overwriting a freed
4293 internal circuit structure. Should help with debugging. Suggested
4295 - If OpenSSL fails to make a duplicate of a private or public key, log
4296 an error message and try to exit cleanly. May help with debugging
4297 if bug 1209 ever remanifests.
4298 - Some options used different conventions for uppercasing of acronyms
4299 when comparing manpage and source. Fix those in favor of the
4300 manpage, as it makes sense to capitalize acronyms.
4301 - Take a first step towards making or.h smaller by splitting out
4302 function definitions for all source files in src/or/. Leave
4303 structures and defines in or.h for now.
4304 - Remove a few dead assignments during router parsing. Found by
4306 - Don't use 1-bit wide signed bit fields. Found by coverity.
4307 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4308 None of the cases where we did this before were wrong, but by making
4309 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4310 - The memarea code now uses a sentinel value at the end of each area
4311 to make sure nothing writes beyond the end of an area. This might
4312 help debug some conceivable causes of bug 930.
4313 - Always treat failure to allocate an RSA key as an unrecoverable
4315 - Add some more defensive programming for architectures that can't
4316 handle unaligned integer accesses. We don't know of any actual bugs
4317 right now, but that's the best time to fix them. Fixes bug 1943.
4319 o Minor bugfixes (misc):
4320 - Fix a rare bug in rend_fn unit tests: we would fail a test when
4321 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
4322 on 0.2.0.10-alpha; fixes bug 1808.
4323 - Where available, use Libevent 2.0's periodic timers so that our
4324 once-per-second cleanup code gets called even more closely to
4325 once per second than it would otherwise. Fixes bug 943.
4326 - Ignore OutboundBindAddress when connecting to localhost.
4327 Connections to localhost need to come _from_ localhost, or else
4328 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
4330 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
4332 - If any of the v3 certs we download are unparseable, we should
4333 actually notice the failure so we don't retry indefinitely. Bugfix
4334 on 0.2.0.x; reported by "rotator".
4335 - When Tor fails to parse a descriptor of any kind, dump it to disk.
4336 Might help diagnosing bug 1051.
4337 - Make our 'torify' script more portable; if we have only one of
4338 'torsocks' or 'tsocks' installed, don't complain to the user;
4339 and explain our warning about tsocks better.
4340 - Fix some urls in the exit notice file and make it XHTML1.1 strict
4341 compliant. Based on a patch from Christian Kujau.
4343 o Documentation changes:
4344 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
4345 - Resolve all doxygen warnings except those for missing documentation.
4347 - Add doxygen documentation for more functions, fields, and types.
4348 - Convert the HACKING file to asciidoc, and add a few new sections
4349 to it, explaining how we use Git, how we make changelogs, and
4350 what should go in a patch.
4351 - Document the default socks host and port (127.0.0.1:9050) for
4353 - Removed some unnecessary files from the source distribution. The
4354 AUTHORS file has now been merged into the people page on the
4355 website. The roadmaps and design doc can now be found in the
4356 projects directory in svn.
4358 o Deprecated and removed features (config):
4359 - Remove the torrc.complete file. It hasn't been kept up to date
4360 and users will have better luck checking out the manpage.
4361 - Remove the HSAuthorityRecordStats option that version 0 hidden
4362 service authorities could use to track statistics of overall v0
4363 hidden service usage.
4364 - Remove the obsolete "NoPublish" option; it has been flagged
4365 as obsolete and has produced a warning since 0.1.1.18-rc.
4366 - Caches no longer download and serve v2 networkstatus documents
4367 unless FetchV2Networkstatus flag is set: these documents haven't
4368 haven't been used by clients or relays since 0.2.0.x. Resolves
4371 o Deprecated and removed features (controller):
4372 - The controller no longer accepts the old obsolete "addr-mappings/"
4373 or "unregistered-servers-" GETINFO values.
4374 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
4375 always on; using them is necessary for correct forward-compatible
4378 o Deprecated and removed features (misc):
4379 - Hidden services no longer publish version 0 descriptors, and clients
4380 do not request or use version 0 descriptors. However, the old hidden
4381 service authorities still accept and serve version 0 descriptors
4382 when contacted by older hidden services/clients.
4383 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4384 anything since 0.2.1.16-rc.
4385 - Remove everything related to building the expert bundle for OS X.
4386 It has confused many users, doesn't work right on OS X 10.6,
4387 and is hard to get rid of once installed. Resolves bug 1274.
4388 - Remove support for .noconnect style addresses. Nobody was using
4389 them, and they provided another avenue for detecting Tor users
4390 via application-level web tricks.
4391 - When we fixed bug 1038 we had to put in a restriction not to send
4392 RELAY_EARLY cells on rend circuits. This was necessary as long
4393 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
4394 active. Now remove this obsolete check. Resolves bug 2081.
4395 - Remove workaround code to handle directory responses from servers
4396 that had bug 539 (they would send HTTP status 503 responses _and_
4397 send a body too). Since only server versions before
4398 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
4399 keep the workaround in place.
4400 - Remove the old 'fuzzy time' logic. It was supposed to be used for
4401 handling calculations where we have a known amount of clock skew and
4402 an allowed amount of unknown skew. But we only used it in three
4403 places, and we never adjusted the known/unknown skew values. This is
4404 still something we might want to do someday, but if we do, we'll
4405 want to do it differently.
4406 - Remove the "--enable-iphone" option to ./configure. According to
4407 reports from Marco Bonetti, Tor builds fine without any special
4408 tweaking on recent iPhone SDK versions.
4411 Changes in version 0.2.1.30 - 2011-02-23
4412 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
4413 change is a slight tweak to Tor's TLS handshake that makes relays
4414 and bridges that run this new version reachable from Iran again.
4415 We don't expect this tweak will win the arms race long-term, but it
4416 buys us time until we roll out a better solution.
4419 - Stop sending a CLOCK_SKEW controller status event whenever
4420 we fetch directory information from a relay that has a wrong clock.
4421 Instead, only inform the controller when it's a trusted authority
4422 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
4423 the rest of bug 1074.
4424 - Fix a bounds-checking error that could allow an attacker to
4425 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
4427 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
4428 Tor would ignore their RelayBandwidthBurst setting,
4429 potentially using more bandwidth than expected. Bugfix on
4430 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
4431 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
4432 hidserv" in her torrc. The 'hidserv' argument never controlled
4433 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
4436 - Adjust our TLS Diffie-Hellman parameters to match those used by
4438 - Update to the February 1 2011 Maxmind GeoLite Country database.
4441 - Check for and reject overly long directory certificates and
4442 directory tokens before they have a chance to hit any assertions.
4443 Bugfix on 0.2.1.28. Found by "doorss".
4444 - Bring the logic that gathers routerinfos and assesses the
4445 acceptability of circuits into line. This prevents a Tor OP from
4446 getting locked in a cycle of choosing its local OR as an exit for a
4447 path (due to a .exit request) and then rejecting the circuit because
4448 its OR is not listed yet. It also prevents Tor clients from using an
4449 OR running in the same instance as an exit (due to a .exit request)
4450 if the OR does not meet the same requirements expected of an OR
4451 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4453 o Packaging changes:
4454 - Stop shipping the Tor specs files and development proposal documents
4455 in the tarball. They are now in a separate git repository at
4456 git://git.torproject.org/torspec.git
4457 - Do not include Git version tags as though they are SVN tags when
4458 generating a tarball from inside a repository that has switched
4459 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4462 Changes in version 0.2.1.29 - 2011-01-15
4463 Tor 0.2.1.29 continues our recent code security audit work. The main
4464 fix resolves a remote heap overflow vulnerability that can allow remote
4465 code execution. Other fixes address a variety of assert and crash bugs,
4466 most of which we think are hard to exploit remotely.
4468 o Major bugfixes (security):
4469 - Fix a heap overflow bug where an adversary could cause heap
4470 corruption. This bug probably allows remote code execution
4471 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
4473 - Prevent a denial-of-service attack by disallowing any
4474 zlib-compressed data whose compression factor is implausibly
4475 high. Fixes part of bug 2324; reported by "doorss".
4476 - Zero out a few more keys in memory before freeing them. Fixes
4477 bug 2384 and part of bug 2385. These key instances found by
4478 "cypherpunks", based on Andrew Case's report about being able
4479 to find sensitive data in Tor's memory space if you have enough
4480 permissions. Bugfix on 0.0.2pre9.
4482 o Major bugfixes (crashes):
4483 - Prevent calls to Libevent from inside Libevent log handlers.
4484 This had potential to cause a nasty set of crashes, especially
4485 if running Libevent with debug logging enabled, and running
4486 Tor with a controller watching for low-severity log messages.
4487 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
4488 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
4489 underflow errors there too. Fixes the other part of bug 2324.
4490 - Fix a bug where we would assert if we ever had a
4491 cached-descriptors.new file (or another file read directly into
4492 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
4493 on 0.2.1.25. Found by doorss.
4494 - Fix some potential asserts and parsing issues with grossly
4495 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
4498 o Minor bugfixes (other):
4499 - Fix a bug with handling misformed replies to reverse DNS lookup
4500 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
4501 bug reported by doorss.
4502 - Fix compilation on mingw when a pthreads compatibility library
4503 has been installed. (We don't want to use it, so we shouldn't
4504 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
4505 - Fix a bug where we would declare that we had run out of virtual
4506 addresses when the address space was only half-exhausted. Bugfix
4508 - Correctly handle the case where AutomapHostsOnResolve is set but
4509 no virtual addresses are available. Fixes bug 2328; bugfix on
4510 0.1.2.1-alpha. Bug found by doorss.
4511 - Correctly handle wrapping around when we run out of virtual
4512 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
4515 - Update to the January 1 2011 Maxmind GeoLite Country database.
4516 - Introduce output size checks on all of our decryption functions.
4519 - Tor does not build packages correctly with Automake 1.6 and earlier;
4520 added a check to Makefile.am to make sure that we're building with
4521 Automake 1.7 or later.
4522 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4523 because we built it with a too-old version of automake. Thus that
4524 release broke ./configure --enable-openbsd-malloc, which is popular
4525 among really fast exit relays on Linux.
4528 Changes in version 0.2.1.28 - 2010-12-17
4529 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
4530 exploitable bugs. We also took this opportunity to change the IP address
4531 for one of our directory authorities, and to update the geoip database
4535 - Fix a remotely exploitable bug that could be used to crash instances
4536 of Tor remotely by overflowing on the heap. Remote-code execution
4537 hasn't been confirmed, but can't be ruled out. Everyone should
4538 upgrade. Bugfix on the 0.1.1 series and later.
4540 o Directory authority changes:
4541 - Change IP address and ports for gabelmoo (v3 directory authority).
4544 - Update to the December 1 2010 Maxmind GeoLite Country database.
4547 Changes in version 0.2.1.27 - 2010-11-23
4548 Yet another OpenSSL security patch broke its compatibility with Tor:
4549 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
4550 also took this opportunity to fix several crash bugs, integrate a new
4551 directory authority, and update the bundled GeoIP database.
4554 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4555 No longer set the tlsext_host_name extension on server SSL objects;
4556 but continue to set it on client SSL objects. Our goal in setting
4557 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4558 bugfix on 0.2.1.1-alpha.
4559 - Do not log messages to the controller while shrinking buffer
4560 freelists. Doing so would sometimes make the controller connection
4561 try to allocate a buffer chunk, which would mess up the internals
4562 of the freelist and cause an assertion failure. Fixes bug 1125;
4563 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4564 - Learn our external IP address when we're a relay or bridge, even if
4565 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4566 where we introduced bridge relays that don't need to publish to
4567 be useful. Fixes bug 2050.
4568 - Do even more to reject (and not just ignore) annotations on
4569 router descriptors received anywhere but from the cache. Previously
4570 we would ignore such annotations at first, but cache them to disk
4571 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4572 - When you're using bridges and your network goes away and your
4573 bridges get marked as down, recover when you attempt a new socks
4574 connection (if the network is back), rather than waiting up to an
4575 hour to try fetching new descriptors for your bridges. Bugfix on
4576 0.2.0.3-alpha; fixes bug 1981.
4579 - Move to the November 2010 Maxmind GeoLite country db (rather
4580 than the June 2009 ip-to-country GeoIP db) for our statistics that
4581 count how many users relays are seeing from each country. Now we'll
4582 have more accurate data, especially for many African countries.
4584 o New directory authorities:
4585 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4589 - Fix an assertion failure that could occur in directory caches or
4590 bridge users when using a very short voting interval on a testing
4591 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
4593 - Enforce multiplicity rules when parsing annotations. Bugfix on
4594 0.2.0.8-alpha. Found by piebeer.
4595 - Allow handshaking OR connections to take a full KeepalivePeriod
4596 seconds to handshake. Previously, we would close them after
4597 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4598 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4600 - When building with --enable-gcc-warnings on OpenBSD, disable
4601 warnings in system headers. This makes --enable-gcc-warnings
4602 pass on OpenBSD 4.8.
4605 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4606 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4607 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4608 Servers can start sending this code when enough clients recognize
4609 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
4610 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4611 Patch from mingw-san.
4614 - Remove the old debian/ directory from the main Tor distribution.
4615 The official Tor-for-debian git repository lives at the URL
4616 https://git.torproject.org/debian/tor.git
4617 - Stop shipping the old doc/website/ directory in the tarball. We
4618 changed the website format in late 2010, and what we shipped in
4619 0.2.1.26 really wasn't that useful anyway.
4622 Changes in version 0.2.1.26 - 2010-05-02
4623 Tor 0.2.1.26 addresses the recent connection and memory overload
4624 problems we've been seeing on relays, especially relays with their
4625 DirPort open. If your relay has been crashing, or you turned it off
4626 because it used too many resources, give this release a try.
4628 This release also fixes yet another instance of broken OpenSSL libraries
4629 that was causing some relays to drop out of the consensus.
4632 - Teach relays to defend themselves from connection overload. Relays
4633 now close idle circuits early if it looks like they were intended
4634 for directory fetches. Relays are also more aggressive about closing
4635 TLS connections that have no circuits on them. Such circuits are
4636 unlikely to be re-used, and tens of thousands of them were piling
4637 up at the fast relays, causing the relays to run out of sockets
4638 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4639 their directory fetches over TLS).
4640 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4641 that claim to be earlier than 0.9.8m, but which have in reality
4642 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4643 behavior. Possible fix for some cases of bug 1346.
4644 - Directory mirrors were fetching relay descriptors only from v2
4645 directory authorities, rather than v3 authorities like they should.
4646 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4647 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4650 - Finally get rid of the deprecated and now harmful notion of "clique
4651 mode", where directory authorities maintain TLS connections to
4655 - In the util/threads test, no longer free the test_mutex before all
4656 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4657 - The master thread could starve the worker threads quite badly on
4658 certain systems, causing them to run only partially in the allowed
4659 window. This resulted in test failures. Now the master thread sleeps
4660 occasionally for a few microseconds while the two worker-threads
4661 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4664 Changes in version 0.2.1.25 - 2010-03-16
4665 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4666 prevent relays from guessing their IP address correctly. It also fixes
4667 several minor potential security bugs.
4670 - Fix a regression from our patch for bug 1244 that caused relays
4671 to guess their IP address incorrectly if they didn't set Address
4672 in their torrc and/or their address fails to resolve. Bugfix on
4673 0.2.1.23; fixes bug 1269.
4674 - When freeing a session key, zero it out completely. We only zeroed
4675 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4676 patched by ekir. Fixes bug 1254.
4679 - Fix a dereference-then-NULL-check sequence when publishing
4680 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4682 - Fix another dereference-then-NULL-check sequence. Bugfix on
4683 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4684 - Make sure we treat potentially not NUL-terminated strings correctly.
4685 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4688 Changes in version 0.2.1.24 - 2010-02-21
4689 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4693 - Work correctly out-of-the-box with even more vendor-patched versions
4694 of OpenSSL. In particular, make it so Debian and OS X don't need
4695 customized patches to run/build.
4698 Changes in version 0.2.1.23 - 2010-02-13
4699 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4700 again on the latest OS X, and updates the location of a directory
4703 o Major bugfixes (performance):
4704 - We were selecting our guards uniformly at random, and then weighting
4705 which of our guards we'd use uniformly at random. This imbalance
4706 meant that Tor clients were severely limited on throughput (and
4707 probably latency too) by the first hop in their circuit. Now we
4708 select guards weighted by currently advertised bandwidth. We also
4709 automatically discard guards picked using the old algorithm. Fixes
4710 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4713 - Make Tor work again on the latest OS X: when deciding whether to
4714 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4715 version at run-time, not compile time. We need to do this because
4716 Apple doesn't update its dev-tools headers when it updates its
4717 libraries in a security patch.
4718 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4719 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4720 a memory leak when requesting a hidden service descriptor we've
4721 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4725 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4726 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4729 - Avoid a mad rush at the beginning of each month when each client
4730 rotates half of its guards. Instead we spread the rotation out
4731 throughout the month, but we still avoid leaving a precise timestamp
4732 in the state file about when we first picked the guard. Improves
4733 over the behavior introduced in 0.1.2.17.
4736 Changes in version 0.2.1.22 - 2010-01-19
4737 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
4738 authorities -- it would tell you its whole history of bridge descriptors
4739 if you make the right directory request. This stable update also
4740 rotates two of the seven v3 directory authority keys and locations.
4742 o Directory authority changes:
4743 - Rotate keys (both v3 identity and relay identity) for moria1
4747 - Stop bridge directory authorities from answering dbg-stability.txt
4748 directory queries, which would let people fetch a list of all
4749 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4752 Changes in version 0.2.1.21 - 2009-12-21
4753 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
4754 library. If you use Tor on Linux / Unix and you're getting SSL
4755 renegotiation errors, upgrading should help. We also recommend an
4756 upgrade if you're an exit relay.
4759 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4760 handshake from working unless we explicitly tell OpenSSL that we
4761 are using SSL renegotiation safely. We are, of course, but OpenSSL
4762 0.9.8l won't work unless we say we are.
4763 - Avoid crashing if the client is trying to upload many bytes and the
4764 circuit gets torn down at the same time, or if the flip side
4765 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
4768 - Do not refuse to learn about authority certs and v2 networkstatus
4769 documents that are older than the latest consensus. This bug might
4770 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4771 Spotted and fixed by xmux.
4772 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
4773 trigger platform-specific option misparsing case found by Coverity
4775 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
4776 trigger assert. Fixes bug 1173.
4779 Changes in version 0.2.1.20 - 2009-10-15
4780 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
4781 services at once, prepares for more performance improvements, and
4782 fixes a bunch of smaller bugs.
4784 The Windows and OS X bundles also include a more recent Vidalia,
4785 and switch from Privoxy to Polipo.
4787 The OS X installers are now drag and drop. It's best to un-install
4788 Tor/Vidalia and then install this new bundle, rather than upgrade. If
4789 you want to upgrade, you'll need to update the paths for Tor and Polipo
4790 in the Vidalia Settings window.
4793 - Send circuit or stream sendme cells when our window has decreased
4794 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4795 by Karsten when testing the "reduce circuit window" performance
4796 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4797 before the release of Tor 0.0.0. This is the new winner of the
4799 - Fix a remotely triggerable memory leak when a consensus document
4800 contains more than one signature from the same voter. Bugfix on
4802 - Avoid segfault in rare cases when finishing an introduction circuit
4803 as a client and finding out that we don't have an introduction key
4804 for it. Fixes bug 1073. Reported by Aaron Swartz.
4807 - Tor now reads the "circwindow" parameter out of the consensus,
4808 and uses that value for its circuit package window rather than the
4809 default of 1000 cells. Begins the implementation of proposal 168.
4811 o New directory authorities:
4812 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4814 - Move moria1 and tonga to alternate IP addresses.
4817 - Fix a signed/unsigned compile warning in 0.2.1.19.
4818 - Fix possible segmentation fault on directory authorities. Bugfix on
4820 - Fix an extremely rare infinite recursion bug that could occur if
4821 we tried to log a message after shutting down the log subsystem.
4822 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4823 - Fix an obscure bug where hidden services on 64-bit big-endian
4824 systems might mis-read the timestamp in v3 introduce cells, and
4825 refuse to connect back to the client. Discovered by "rotor".
4826 Bugfix on 0.2.1.6-alpha.
4827 - We were triggering a CLOCK_SKEW controller status event whenever
4828 we connect via the v2 connection protocol to any relay that has
4829 a wrong clock. Instead, we should only inform the controller when
4830 it's a trusted authority that claims our clock is wrong. Bugfix
4831 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4832 - We were telling the controller about CHECKING_REACHABILITY and
4833 REACHABILITY_FAILED status events whenever we launch a testing
4834 circuit or notice that one has failed. Instead, only tell the
4835 controller when we want to inform the user of overall success or
4836 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
4838 - Don't warn when we're using a circuit that ends with a node
4839 excluded in ExcludeExitNodes, but the circuit is not used to access
4840 the outside world. This should help fix bug 1090. Bugfix on
4842 - Work around a small memory leak in some versions of OpenSSL that
4843 stopped the memory used by the hostname TLS extension from being
4847 - Add a "getinfo status/accepted-server-descriptor" controller
4848 command, which is the recommended way for controllers to learn
4849 whether our server descriptor has been successfully received by at
4850 least on directory authority. Un-recommend good-server-descriptor
4851 getinfo and status events until we have a better design for them.
4854 Changes in version 0.2.1.19 - 2009-07-28
4855 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
4859 - Make accessing hidden services on 0.2.1.x work right again.
4860 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
4861 part of patch provided by "optimist".
4864 - When a relay/bridge is writing out its identity key fingerprint to
4865 the "fingerprint" file and to its logs, write it without spaces. Now
4866 it will look like the fingerprints in our bridges documentation,
4867 and confuse fewer users.
4870 - Relays no longer publish a new server descriptor if they change
4871 their MaxAdvertisedBandwidth config option but it doesn't end up
4872 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
4873 fixes bug 1026. Patch from Sebastian.
4874 - Avoid leaking memory every time we get a create cell but we have
4875 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
4876 fixes bug 1034. Reported by BarkerJr.
4879 Changes in version 0.2.1.18 - 2009-07-24
4880 Tor 0.2.1.18 lays the foundations for performance improvements,
4881 adds status events to help users diagnose bootstrap problems, adds
4882 optional authentication/authorization for hidden services, fixes a
4883 variety of potential anonymity problems, and includes a huge pile of
4884 other features and bug fixes.
4886 o Major features (clients):
4887 - Start sending "bootstrap phase" status events to the controller,
4888 so it can keep the user informed of progress fetching directory
4889 information and establishing circuits. Also inform the controller
4890 if we think we're stuck at a particular bootstrap phase. Implements
4892 - Clients replace entry guards that were chosen more than a few months
4893 ago. This change should significantly improve client performance,
4894 especially once more people upgrade, since relays that have been
4895 a guard for a long time are currently overloaded.
4896 - Network status consensus documents and votes now contain bandwidth
4897 information for each relay. Clients use the bandwidth values
4898 in the consensus, rather than the bandwidth values in each
4899 relay descriptor. This approach opens the door to more accurate
4900 bandwidth estimates once the directory authorities start doing
4901 active measurements. Implements part of proposal 141.
4903 o Major features (relays):
4904 - Disable and refactor some debugging checks that forced a linear scan
4905 over the whole server-side DNS cache. These accounted for over 50%
4906 of CPU time on a relatively busy exit node's gprof profile. Also,
4907 disable some debugging checks that appeared in exit node profile
4908 data. Found by Jacob.
4909 - New DirPortFrontPage option that takes an html file and publishes
4910 it as "/" on the DirPort. Now relay operators can provide a
4911 disclaimer without needing to set up a separate webserver. There's
4912 a sample disclaimer in contrib/tor-exit-notice.html.
4914 o Major features (hidden services):
4915 - Make it possible to build hidden services that only certain clients
4916 are allowed to connect to. This is enforced at several points,
4917 so that unauthorized clients are unable to send INTRODUCE cells
4918 to the service, or even (depending on the type of authentication)
4919 to learn introduction points. This feature raises the bar for
4920 certain kinds of active attacks against hidden services. Design
4921 and code by Karsten Loesing. Implements proposal 121.
4922 - Relays now store and serve v2 hidden service descriptors by default,
4923 i.e., the new default value for HidServDirectoryV2 is 1. This is
4924 the last step in proposal 114, which aims to make hidden service
4925 lookups more reliable.
4927 o Major features (path selection):
4928 - ExitNodes and Exclude*Nodes config options now allow you to restrict
4929 by country code ("{US}") or IP address or address pattern
4930 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
4931 refinement to decide what config options should take priority if
4932 you ask to both use a particular node and exclude it.
4934 o Major features (misc):
4935 - When building a consensus, do not include routers that are down.
4936 This cuts down 30% to 40% on consensus size. Implements proposal
4938 - New TestingTorNetwork config option to allow adjustment of
4939 previously constant values that could slow bootstrapping. Implements
4940 proposal 135. Patch from Karsten.
4941 - Convert many internal address representations to optionally hold
4942 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
4943 elements. Make resolver code handle nameservers located at IPv6
4945 - More work on making our TLS handshake blend in: modify the list
4946 of ciphers advertised by OpenSSL in client mode to even more
4947 closely resemble a common web browser. We cheat a little so that
4948 we can advertise ciphers that the locally installed OpenSSL doesn't
4950 - Use the TLS1 hostname extension to more closely resemble browser
4953 o Security fixes (anonymity/entropy):
4954 - Never use a connection with a mismatched address to extend a
4955 circuit, unless that connection is canonical. A canonical
4956 connection is one whose address is authenticated by the router's
4957 identity key, either in a NETINFO cell or in a router descriptor.
4958 - Implement most of proposal 110: The first K cells to be sent
4959 along a circuit are marked as special "early" cells; only K "early"
4960 cells will be allowed. Once this code is universal, we can block
4961 certain kinds of denial-of-service attack by requiring that EXTEND
4962 commands must be sent using an "early" cell.
4963 - Resume using OpenSSL's RAND_poll() for better (and more portable)
4964 cross-platform entropy collection again. We used to use it, then
4965 stopped using it because of a bug that could crash systems that
4966 called RAND_poll when they had a lot of fds open. It looks like the
4967 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
4968 at startup, and to call RAND_poll() when we reseed later only if
4969 we have a non-buggy OpenSSL version.
4970 - When the client is choosing entry guards, now it selects at most
4971 one guard from a given relay family. Otherwise we could end up with
4972 all of our entry points into the network run by the same operator.
4973 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
4974 - Do not use or believe expired v3 authority certificates. Patch
4975 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
4976 - Drop begin cells to a hidden service if they come from the middle
4977 of a circuit. Patch from lark.
4978 - When we erroneously receive two EXTEND cells for the same circuit
4979 ID on the same connection, drop the second. Patch from lark.
4980 - Authorities now vote for the Stable flag for any router whose
4981 weighted MTBF is at least 5 days, regardless of the mean MTBF.
4982 - Clients now never report any stream end reason except 'MISC'.
4983 Implements proposal 148.
4985 o Major bugfixes (crashes):
4986 - Parse dates and IPv4 addresses in a locale- and libc-independent
4987 manner, to avoid platform-dependent behavior on malformed input.
4988 - Fix a crash that occurs on exit nodes when a nameserver request
4989 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
4990 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
4992 - Do not assume that a stack-allocated character array will be
4993 64-bit aligned on platforms that demand that uint64_t access is
4994 aligned. Possible fix for bug 604.
4995 - Resolve a very rare crash bug that could occur when the user forced
4996 a nameserver reconfiguration during the middle of a nameserver
4997 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
4998 - Avoid a "0 divided by 0" calculation when calculating router uptime
4999 at directory authorities. Bugfix on 0.2.0.8-alpha.
5000 - Fix an assertion bug in parsing policy-related options; possible fix
5002 - Rate-limit too-many-sockets messages: when they happen, they happen
5003 a lot and end up filling up the disk. Resolves bug 748.
5004 - Fix a race condition that could cause crashes or memory corruption
5005 when running as a server with a controller listening for log
5007 - Avoid crashing when we have a policy specified in a DirPolicy or
5008 SocksPolicy or ReachableAddresses option with ports set on it,
5009 and we re-load the policy. May fix bug 996.
5010 - Fix an assertion failure on 64-bit platforms when we allocated
5011 memory right up to the end of a memarea, then realigned the memory
5012 one step beyond the end. Fixes a possible cause of bug 930.
5013 - Protect the count of open sockets with a mutex, so we can't
5014 corrupt it when two threads are closing or opening sockets at once.
5015 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
5017 o Major bugfixes (clients):
5018 - Discard router descriptors as we load them if they are more than
5019 five days old. Otherwise if Tor is off for a long time and then
5020 starts with cached descriptors, it will try to use the onion keys
5021 in those obsolete descriptors when building circuits. Fixes bug 887.
5022 - When we choose to abandon a new entry guard because we think our
5023 older ones might be better, close any circuits pending on that
5024 new entry guard connection. This fix should make us recover much
5025 faster when our network is down and then comes back. Bugfix on
5026 0.1.2.8-beta; found by lodger.
5027 - When Tor clients restart after 1-5 days, they discard all their
5028 cached descriptors as too old, but they still use the cached
5029 consensus document. This approach is good for robustness, but
5030 bad for performance: since they don't know any bandwidths, they
5031 end up choosing at random rather than weighting their choice by
5032 speed. Fixed by the above feature of putting bandwidths in the
5035 o Major bugfixes (relays):
5036 - Relays were falling out of the networkstatus consensus for
5037 part of a day if they changed their local config but the
5038 authorities discarded their new descriptor as "not sufficiently
5039 different". Now directory authorities accept a descriptor as changed
5040 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
5042 - Ensure that two circuits can never exist on the same connection
5043 with the same circuit ID, even if one is marked for close. This
5044 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
5045 - Directory authorities were neglecting to mark relays down in their
5046 internal histories if the relays fall off the routerlist without
5047 ever being found unreachable. So there were relays in the histories
5048 that haven't been seen for eight months, and are listed as being
5049 up for eight months. This wreaked havoc on the "median wfu" and
5050 "median mtbf" calculations, in turn making Guard and Stable flags
5051 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
5054 o Major bugfixes (hidden services):
5055 - When establishing a hidden service, introduction points that
5056 originate from cannibalized circuits were completely ignored
5057 and not included in rendezvous service descriptors. This might
5058 have been another reason for delay in making a hidden service
5059 available. Bugfix from long ago (0.0.9.x?)
5061 o Major bugfixes (memory and resource management):
5062 - Fixed some memory leaks -- some quite frequent, some almost
5063 impossible to trigger -- based on results from Coverity.
5064 - Speed up parsing and cut down on memory fragmentation by using
5065 stack-style allocations for parsing directory objects. Previously,
5066 this accounted for over 40% of allocations from within Tor's code
5067 on a typical directory cache.
5068 - Use a Bloom filter rather than a digest-based set to track which
5069 descriptors we need to keep around when we're cleaning out old
5070 router descriptors. This speeds up the computation significantly,
5071 and may reduce fragmentation.
5073 o New/changed config options:
5074 - Now NodeFamily and MyFamily config options allow spaces in
5075 identity fingerprints, so it's easier to paste them in.
5076 Suggested by Lucky Green.
5077 - Allow ports 465 and 587 in the default exit policy again. We had
5078 rejected them in 0.1.0.15, because back in 2005 they were commonly
5079 misconfigured and ended up as spam targets. We hear they are better
5080 locked down these days.
5081 - Make TrackHostExit mappings expire a while after their last use, not
5082 after their creation. Patch from Robert Hogan.
5083 - Add an ExcludeExitNodes option so users can list a set of nodes
5084 that should be be excluded from the exit node position, but
5085 allowed elsewhere. Implements proposal 151.
5086 - New --hush command-line option similar to --quiet. While --quiet
5087 disables all logging to the console on startup, --hush limits the
5088 output to messages of warning and error severity.
5089 - New configure/torrc options (--enable-geoip-stats,
5090 DirRecordUsageByCountry) to record how many IPs we've served
5091 directory info to in each country code, how many status documents
5092 total we've sent to each country code, and what share of the total
5093 directory requests we should expect to see.
5094 - Make outbound DNS packets respect the OutboundBindAddress setting.
5095 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
5096 - Allow separate log levels to be configured for different logging
5097 domains. For example, this allows one to log all notices, warnings,
5098 or errors, plus all memory management messages of level debug or
5099 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
5100 - Update to the "June 3 2009" ip-to-country file.
5102 o Minor features (relays):
5103 - Raise the minimum rate limiting to be a relay from 20000 bytes
5104 to 20480 bytes (aka 20KB/s), to match our documentation. Also
5105 update directory authorities so they always assign the Fast flag
5106 to relays with 20KB/s of capacity. Now people running relays won't
5107 suddenly find themselves not seeing any use, if the network gets
5109 - If we're a relay and we change our IP address, be more verbose
5110 about the reason that made us change. Should help track down
5111 further bugs for relays on dynamic IP addresses.
5112 - Exit servers can now answer resolve requests for ip6.arpa addresses.
5113 - Implement most of Proposal 152: allow specialized servers to permit
5114 single-hop circuits, and clients to use those servers to build
5115 single-hop circuits when using a specialized controller. Patch
5116 from Josh Albrecht. Resolves feature request 768.
5117 - When relays do their initial bandwidth measurement, don't limit
5118 to just our entry guards for the test circuits. Otherwise we tend
5119 to have multiple test circuits going through a single entry guard,
5120 which makes our bandwidth test less accurate. Fixes part of bug 654;
5121 patch contributed by Josh Albrecht.
5123 o Minor features (directory authorities):
5124 - Try not to open more than one descriptor-downloading connection
5125 to an authority at once. This should reduce load on directory
5126 authorities. Fixes bug 366.
5127 - Add cross-certification to newly generated certificates, so that
5128 a signing key is enough information to look up a certificate. Start
5129 serving certificates by <identity digest, signing key digest>
5130 pairs. Implements proposal 157.
5131 - When a directory authority downloads a descriptor that it then
5132 immediately rejects, do not retry downloading it right away. Should
5133 save some bandwidth on authorities. Fix for bug 888. Patch by
5135 - Directory authorities now serve a /tor/dbg-stability.txt URL to
5136 help debug WFU and MTBF calculations.
5137 - In directory authorities' approved-routers files, allow
5138 fingerprints with or without space.
5140 o Minor features (directory mirrors):
5141 - When a download gets us zero good descriptors, do not notify
5142 Tor that new directory information has arrived.
5143 - Servers support a new URL scheme for consensus downloads that
5144 allows the client to specify which authorities are trusted.
5145 The server then only sends the consensus if the client will trust
5146 it. Otherwise a 404 error is sent back. Clients use this
5147 new scheme when the server supports it (meaning it's running
5148 0.2.1.1-alpha or later). Implements proposal 134.
5150 o Minor features (bridges):
5151 - If the bridge config line doesn't specify a port, assume 443.
5152 This makes bridge lines a bit smaller and easier for users to
5154 - If we're using bridges and our network goes away, be more willing
5155 to forgive our bridges and try again when we get an application
5158 o Minor features (hidden services):
5159 - When the client launches an introduction circuit, retry with a
5160 new circuit after 30 seconds rather than 60 seconds.
5161 - Launch a second client-side introduction circuit in parallel
5162 after a delay of 15 seconds (based on work by Christian Wilms).
5163 - Hidden services start out building five intro circuits rather
5164 than three, and when the first three finish they publish a service
5165 descriptor using those. Now we publish our service descriptor much
5166 faster after restart.
5167 - Drop the requirement to have an open dir port for storing and
5168 serving v2 hidden service descriptors.
5170 o Minor features (build and packaging):
5171 - On Linux, use the prctl call to re-enable core dumps when the User
5173 - Try to make sure that the version of Libevent we're running with
5174 is binary-compatible with the one we built with. May address bug
5176 - Add a new --enable-local-appdata configuration switch to change
5177 the default location of the datadir on win32 from APPDATA to
5178 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
5179 entirely. Patch from coderman.
5180 - Build correctly against versions of OpenSSL 0.9.8 or later that
5181 are built without support for deprecated functions.
5182 - On platforms with a maximum syslog string length, truncate syslog
5183 messages to that length ourselves, rather than relying on the
5184 system to do it for us.
5185 - Automatically detect MacOSX versions earlier than 10.4.0, and
5186 disable kqueue from inside Tor when running with these versions.
5187 We previously did this from the startup script, but that was no
5188 help to people who didn't use the startup script. Resolves bug 863.
5189 - Build correctly when configured to build outside the main source
5190 path. Patch from Michael Gold.
5191 - Disable GCC's strict alias optimization by default, to avoid the
5192 likelihood of its introducing subtle bugs whenever our code violates
5193 the letter of C99's alias rules.
5194 - Change the contrib/tor.logrotate script so it makes the new
5195 logs as "_tor:_tor" rather than the default, which is generally
5196 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
5197 - Change our header file guard macros to be less likely to conflict
5198 with system headers. Adam Langley noticed that we were conflicting
5199 with log.h on Android.
5200 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
5201 and stop using a warning that had become unfixably verbose under
5203 - Use a lockfile to make sure that two Tor processes are not
5204 simultaneously running with the same datadir.
5205 - Allow OpenSSL to use dynamic locks if it wants.
5206 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
5208 o Minor features (controllers):
5209 - When generating circuit events with verbose nicknames for
5210 controllers, try harder to look up nicknames for routers on a
5211 circuit. (Previously, we would look in the router descriptors we had
5212 for nicknames, but not in the consensus.) Partial fix for bug 941.
5213 - New controller event NEWCONSENSUS that lists the networkstatus
5214 lines for every recommended relay. Now controllers like Torflow
5215 can keep up-to-date on which relays they should be using.
5216 - New controller event "clients_seen" to report a geoip-based summary
5217 of which countries we've seen clients from recently. Now controllers
5218 like Vidalia can show bridge operators that they're actually making
5220 - Add a 'getinfo status/clients-seen' controller command, in case
5221 controllers want to hear clients_seen events but connect late.
5222 - New CONSENSUS_ARRIVED event to note when a new consensus has
5223 been fetched and validated.
5224 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
5225 controllers to prevent SIGHUP from reloading the configuration.
5227 - Return circuit purposes in response to GETINFO circuit-status.
5229 - Serve the latest v3 networkstatus consensus via the control
5230 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
5231 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
5232 controller can query our current bootstrap state in case it attaches
5233 partway through and wants to catch up.
5234 - Provide circuit purposes along with circuit events to the controller.
5236 o Minor features (tools):
5237 - Do not have tor-resolve automatically refuse all .onion addresses;
5238 if AutomapHostsOnResolve is set in your torrc, this will work fine.
5239 - Add a -p option to tor-resolve for specifying the SOCKS port: some
5240 people find host:port too confusing.
5241 - Print the SOCKS5 error message string as well as the error code
5242 when a tor-resolve request fails. Patch from Jacob.
5244 o Minor bugfixes (memory and resource management):
5245 - Clients no longer cache certificates for authorities they do not
5246 recognize. Bugfix on 0.2.0.9-alpha.
5247 - Do not use C's stdio library for writing to log files. This will
5248 improve logging performance by a minute amount, and will stop
5249 leaking fds when our disk is full. Fixes bug 861.
5250 - Stop erroneous use of O_APPEND in cases where we did not in fact
5251 want to re-seek to the end of a file before every last write().
5252 - Fix a small alignment and memory-wasting bug on buffer chunks.
5254 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
5255 to avoid unused RAM in buffer chunks and memory pools.
5256 - Reduce the default smartlist size from 32 to 16; it turns out that
5257 most smartlists hold around 8-12 elements tops.
5258 - Make dumpstats() log the fullness and size of openssl-internal
5260 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
5261 patch to their OpenSSL, turn it on to save memory on servers. This
5262 patch will (with any luck) get included in a mainline distribution
5264 - Fix a memory leak when v3 directory authorities load their keys
5265 and cert from disk. Bugfix on 0.2.0.1-alpha.
5266 - Stop using malloc_usable_size() to use more area than we had
5267 actually allocated: it was safe, but made valgrind really unhappy.
5268 - Make the assert_circuit_ok() function work correctly on circuits that
5269 have already been marked for close.
5270 - Fix uninitialized size field for memory area allocation: may improve
5271 memory performance during directory parsing.
5273 o Minor bugfixes (clients):
5274 - Stop reloading the router list from disk for no reason when we
5275 run out of reachable directory mirrors. Once upon a time reloading
5276 it would set the 'is_running' flag back to 1 for them. It hasn't
5277 done that for a long time.
5278 - When we had picked an exit node for a connection, but marked it as
5279 "optional", and it turned out we had no onion key for the exit,
5280 stop wanting that exit and try again. This situation may not
5281 be possible now, but will probably become feasible with proposal
5282 158. Spotted by rovv. Fixes another case of bug 752.
5283 - Fix a bug in address parsing that was preventing bridges or hidden
5284 service targets from being at IPv6 addresses.
5285 - Do not remove routers as too old if we do not have any consensus
5286 document. Bugfix on 0.2.0.7-alpha.
5287 - When an exit relay resolves a stream address to a local IP address,
5288 do not just keep retrying that same exit relay over and
5289 over. Instead, just close the stream. Addresses bug 872. Bugfix
5290 on 0.2.0.32. Patch from rovv.
5291 - Made Tor a little less aggressive about deleting expired
5292 certificates. Partial fix for bug 854.
5293 - Treat duplicate certificate fetches as failures, so that we do
5294 not try to re-fetch an expired certificate over and over and over.
5295 - Do not say we're fetching a certificate when we'll in fact skip it
5296 because of a pending download.
5297 - If we have correct permissions on $datadir, we complain to stdout
5298 and fail to start. But dangerous permissions on
5299 $datadir/cached-status/ would cause us to open a log and complain
5300 there. Now complain to stdout and fail to start in both cases. Fixes
5301 bug 820, reported by seeess.
5303 o Minor bugfixes (bridges):
5304 - When we made bridge authorities stop serving bridge descriptors over
5305 unencrypted links, we also broke DirPort reachability testing for
5306 bridges. So bridges with a non-zero DirPort were printing spurious
5307 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
5308 - Don't allow a bridge to publish its router descriptor to a
5309 non-bridge directory authority. Fixes part of bug 932.
5310 - When we change to or from being a bridge, reset our counts of
5311 client usage by country. Fixes bug 932.
5313 o Minor bugfixes (relays):
5314 - Log correct error messages for DNS-related network errors on
5316 - Actually return -1 in the error case for read_bandwidth_usage().
5317 Harmless bug, since we currently don't care about the return value
5318 anywhere. Bugfix on 0.2.0.9-alpha.
5319 - Provide a more useful log message if bug 977 (related to buffer
5320 freelists) ever reappears, and do not crash right away.
5321 - We were already rejecting relay begin cells with destination port
5322 of 0. Now also reject extend cells with destination port or address
5323 of 0. Suggested by lark.
5324 - When we can't transmit a DNS request due to a network error, retry
5325 it after a while, and eventually transmit a failing response to
5326 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
5327 - Solve a bug that kept hardware crypto acceleration from getting
5328 enabled when accounting was turned on. Fixes bug 907. Bugfix on
5330 - When a canonical connection appears later in our internal list
5331 than a noncanonical one for a given OR ID, always use the
5332 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
5334 - Avoid some nasty corner cases in the logic for marking connections
5335 as too old or obsolete or noncanonical for circuits. Partial
5337 - Fix another interesting corner-case of bug 891 spotted by rovv:
5338 Previously, if two hosts had different amounts of clock drift, and
5339 one of them created a new connection with just the wrong timing,
5340 the other might decide to deprecate the new connection erroneously.
5341 Bugfix on 0.1.1.13-alpha.
5342 - If one win32 nameserver fails to get added, continue adding the
5343 rest, and don't automatically fail.
5344 - Fix a bug where an unreachable relay would establish enough
5345 reachability testing circuits to do a bandwidth test -- if
5346 we already have a connection to the middle hop of the testing
5347 circuit, then it could establish the last hop by using the existing
5348 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
5349 circuits no longer use entry guards in 0.2.1.3-alpha.
5351 o Minor bugfixes (directory authorities):
5352 - Limit uploaded directory documents to be 16M rather than 500K.
5353 The directory authorities were refusing v3 consensus votes from
5354 other authorities, since the votes are now 504K. Fixes bug 959;
5355 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
5356 - Directory authorities should never send a 503 "busy" response to
5357 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
5359 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
5360 headers. Bugfix on 0.2.0.10-alpha.
5362 o Minor bugfixes (hidden services):
5363 - When we can't find an intro key for a v2 hidden service descriptor,
5364 fall back to the v0 hidden service descriptor and log a bug message.
5365 Workaround for bug 1024.
5366 - In very rare situations new hidden service descriptors were
5367 published earlier than 30 seconds after the last change to the
5368 service. (We currently think that a hidden service descriptor
5369 that's been stable for 30 seconds is worth publishing.)
5370 - If a hidden service sends us an END cell, do not consider
5371 retrying the connection; just close it. Patch from rovv.
5372 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
5373 service directories if they have no advertised dir port. Bugfix
5376 o Minor bugfixes (tools):
5377 - In the torify(1) manpage, mention that tsocks will leak your
5380 o Minor bugfixes (controllers):
5381 - If the controller claimed responsibility for a stream, but that
5382 stream never finished making its connection, it would live
5383 forever in circuit_wait state. Now we close it after SocksTimeout
5384 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
5385 - Make DNS resolved controller events into "CLOSED", not
5386 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
5388 - The control port would close the connection before flushing long
5389 replies, such as the network consensus, if a QUIT command was issued
5390 before the reply had completed. Now, the control port flushes all
5391 pending replies before closing the connection. Also fix a spurious
5392 warning when a QUIT command is issued after a malformed or rejected
5393 AUTHENTICATE command, but before the connection was closed. Patch
5394 by Marcus Griep. Fixes bugs 1015 and 1016.
5395 - Fix a bug that made stream bandwidth get misreported to the
5398 o Deprecated and removed features:
5399 - The old "tor --version --version" command, which would print out
5400 the subversion "Id" of most of the source files, is now removed. It
5401 turned out to be less useful than we'd expected, and harder to
5403 - RedirectExits has been removed. It was deprecated since
5405 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
5406 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
5407 - Cell pools are now always enabled; --disable-cell-pools is ignored.
5408 - Directory mirrors no longer fetch the v1 directory or
5409 running-routers files. They are obsolete, and nobody asks for them
5410 anymore. This is the first step to making v1 authorities obsolete.
5411 - Take out the TestVia config option, since it was a workaround for
5412 a bug that was fixed in Tor 0.1.1.21.
5413 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
5414 HiddenServiceExcludeNodes as obsolete: they never worked properly,
5415 and nobody seems to be using them. Fixes bug 754. Bugfix on
5416 0.1.0.1-rc. Patch from Christian Wilms.
5417 - Remove all backward-compatibility code for relays running
5418 versions of Tor so old that they no longer work at all on the
5421 o Code simplifications and refactoring:
5422 - Tool-assisted documentation cleanup. Nearly every function or
5423 static variable in Tor should have its own documentation now.
5424 - Rename the confusing or_is_obsolete field to the more appropriate
5425 is_bad_for_new_circs, and move it to or_connection_t where it
5427 - Move edge-only flags from connection_t to edge_connection_t: not
5428 only is this better coding, but on machines of plausible alignment,
5429 it should save 4-8 bytes per connection_t. "Every little bit helps."
5430 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
5431 for consistency; keep old option working for backward compatibility.
5432 - Simplify the code for finding connections to use for a circuit.
5433 - Revise the connection_new functions so that a more typesafe variant
5434 exists. This will work better with Coverity, and let us find any
5435 actual mistakes we're making here.
5436 - Refactor unit testing logic so that dmalloc can be used sensibly
5437 with unit tests to check for memory leaks.
5438 - Move all hidden-service related fields from connection and circuit
5439 structure to substructures: this way they won't eat so much memory.
5440 - Squeeze 2-5% out of client performance (according to oprofile) by
5441 improving the implementation of some policy-manipulation functions.
5442 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
5443 be more efficient. Formerly it was quadratic in the number of
5444 servers; now it should be linear. Fixes bug 509.
5445 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
5446 and n_conn_id_digest fields into a separate structure that's
5447 only needed when the circuit has not yet attached to an n_conn.
5448 - Optimize out calls to time(NULL) that occur for every IO operation,
5449 or for every cell. On systems like Windows where time() is a
5450 slow syscall, this fix will be slightly helpful.
5453 Changes in version 0.2.0.35 - 2009-06-24
5455 - Avoid crashing in the presence of certain malformed descriptors.
5456 Found by lark, and by automated fuzzing.
5457 - Fix an edge case where a malicious exit relay could convince a
5458 controller that the client's DNS question resolves to an internal IP
5459 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5462 - Finally fix the bug where dynamic-IP relays disappear when their
5463 IP address changes: directory mirrors were mistakenly telling
5464 them their old address if they asked via begin_dir, so they
5465 never got an accurate answer about their new address, so they
5466 just vanished after a day. For belt-and-suspenders, relays that
5467 don't set Address in their config now avoid using begin_dir for
5468 all direct connections. Should fix bugs 827, 883, and 900.
5469 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5470 that would occur on some exit nodes when DNS failures and timeouts
5471 occurred in certain patterns. Fix for bug 957.
5474 - When starting with a cache over a few days old, do not leak
5475 memory for the obsolete router descriptors in it. Bugfix on
5476 0.2.0.33; fixes bug 672.
5477 - Hidden service clients didn't use a cached service descriptor that
5478 was older than 15 minutes, but wouldn't fetch a new one either,
5479 because there was already one in the cache. Now, fetch a v2
5480 descriptor unless the same descriptor was added to the cache within
5481 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5484 Changes in version 0.2.0.34 - 2009-02-08
5485 Tor 0.2.0.34 features several more security-related fixes. You should
5486 upgrade, especially if you run an exit relay (remote crash) or a
5487 directory authority (remote infinite loop), or you're on an older
5488 (pre-XP) or not-recently-patched Windows (remote exploit).
5490 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
5491 have many known flaws, and nobody should be using them. You should
5492 upgrade. If you're using a Linux or BSD and its packages are obsolete,
5493 stop using those packages and upgrade anyway.
5496 - Fix an infinite-loop bug on handling corrupt votes under certain
5497 circumstances. Bugfix on 0.2.0.8-alpha.
5498 - Fix a temporary DoS vulnerability that could be performed by
5499 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5500 - Avoid a potential crash on exit nodes when processing malformed
5501 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
5502 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5503 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5506 - Fix compilation on systems where time_t is a 64-bit integer.
5507 Patch from Matthias Drochner.
5508 - Don't consider expiring already-closed client connections. Fixes
5509 bug 893. Bugfix on 0.0.2pre20.
5512 Changes in version 0.2.0.33 - 2009-01-21
5513 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
5514 useful to users. It also finally fixes a bug where a relay or client
5515 that's been off for many days would take a long time to bootstrap.
5517 This update also fixes an important security-related bug reported by
5518 Ilja van Sprundel. You should upgrade. (We'll send out more details
5519 about the bug once people have had some time to upgrade.)
5522 - Fix a heap-corruption bug that may be remotely triggerable on
5523 some platforms. Reported by Ilja van Sprundel.
5526 - When a stream at an exit relay is in state "resolving" or
5527 "connecting" and it receives an "end" relay cell, the exit relay
5528 would silently ignore the end cell and not close the stream. If
5529 the client never closes the circuit, then the exit relay never
5530 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
5532 - When sending CREATED cells back for a given circuit, use a 64-bit
5533 connection ID to find the right connection, rather than an addr:port
5534 combination. Now that we can have multiple OR connections between
5535 the same ORs, it is no longer possible to use addr:port to uniquely
5536 identify a connection.
5537 - Bridge relays that had DirPort set to 0 would stop fetching
5538 descriptors shortly after startup, and then briefly resume
5539 after a new bandwidth test and/or after publishing a new bridge
5540 descriptor. Bridge users that try to bootstrap from them would
5541 get a recent networkstatus but would get descriptors from up to
5542 18 hours earlier, meaning most of the descriptors were obsolete
5543 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5544 - Prevent bridge relays from serving their 'extrainfo' document
5545 to anybody who asks, now that extrainfo docs include potentially
5546 sensitive aggregated client geoip summaries. Bugfix on
5548 - If the cached networkstatus consensus is more than five days old,
5549 discard it rather than trying to use it. In theory it could be
5550 useful because it lists alternate directory mirrors, but in practice
5551 it just means we spend many minutes trying directory mirrors that
5552 are long gone from the network. Also discard router descriptors as
5553 we load them if they are more than five days old, since the onion
5554 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
5557 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5558 could make gcc generate non-functional binary search code. Bugfix
5560 - Build correctly on platforms without socklen_t.
5561 - Compile without warnings on solaris.
5562 - Avoid potential crash on internal error during signature collection.
5563 Fixes bug 864. Patch from rovv.
5564 - Correct handling of possible malformed authority signing key
5565 certificates with internal signature types. Fixes bug 880.
5566 Bugfix on 0.2.0.3-alpha.
5567 - Fix a hard-to-trigger resource leak when logging credential status.
5569 - When we can't initialize DNS because the network is down, do not
5570 automatically stop Tor from starting. Instead, we retry failed
5571 dns_init() every 10 minutes, and change the exit policy to reject
5572 *:* until one succeeds. Fixes bug 691.
5573 - Use 64 bits instead of 32 bits for connection identifiers used with
5574 the controller protocol, to greatly reduce risk of identifier reuse.
5575 - When we're choosing an exit node for a circuit, and we have
5576 no pending streams, choose a good general exit rather than one that
5577 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5578 - Fix another case of assuming, when a specific exit is requested,
5579 that we know more than the user about what hosts it allows.
5580 Fixes one case of bug 752. Patch from rovv.
5581 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5582 seconds. Warn the user if lower values are given in the
5583 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5584 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5585 user if lower values are given in the configuration. Bugfix on
5586 0.1.1.17-rc. Patch by Sebastian.
5587 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
5588 the cache because we already had a v0 descriptor with the same ID.
5589 Bugfix on 0.2.0.18-alpha.
5590 - Fix a race condition when freeing keys shared between main thread
5591 and CPU workers that could result in a memory leak. Bugfix on
5592 0.1.0.1-rc. Fixes bug 889.
5593 - Send a valid END cell back when a client tries to connect to a
5594 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5595 840. Patch from rovv.
5596 - Check which hops rendezvous stream cells are associated with to
5597 prevent possible guess-the-streamid injection attacks from
5598 intermediate hops. Fixes another case of bug 446. Based on patch
5600 - If a broken client asks a non-exit router to connect somewhere,
5601 do not even do the DNS lookup before rejecting the connection.
5602 Fixes another case of bug 619. Patch from rovv.
5603 - When a relay gets a create cell it can't decrypt (e.g. because it's
5604 using the wrong onion key), we were dropping it and letting the
5605 client time out. Now actually answer with a destroy cell. Fixes
5606 bug 904. Bugfix on 0.0.2pre8.
5608 o Minor bugfixes (hidden services):
5609 - Do not throw away existing introduction points on SIGHUP. Bugfix on
5610 0.0.6pre1. Patch by Karsten. Fixes bug 874.
5613 - Report the case where all signatures in a detached set are rejected
5614 differently than the case where there is an error handling the
5616 - When we realize that another process has modified our cached
5617 descriptors, print out a more useful error message rather than
5618 triggering an assertion. Fixes bug 885. Patch from Karsten.
5619 - Implement the 0x20 hack to better resist DNS poisoning: set the
5620 case on outgoing DNS requests randomly, and reject responses that do
5621 not match the case correctly. This logic can be disabled with the
5622 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
5623 of servers that do not reliably preserve case in replies. See
5624 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5626 - Check DNS replies for more matching fields to better resist DNS
5628 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5629 compress cells, which are basically all encrypted, compressed, or
5633 Changes in version 0.2.0.32 - 2008-11-20
5634 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
5635 packages (and maybe other packages) noticed by Theo de Raadt, fixes
5636 a smaller security flaw that might allow an attacker to access local
5637 services, further improves hidden service performance, and fixes a
5638 variety of other issues.
5641 - The "User" and "Group" config options did not clear the
5642 supplementary group entries for the Tor process. The "User" option
5643 is now more robust, and we now set the groups to the specified
5644 user's primary group. The "Group" option is now ignored. For more
5645 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
5646 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
5647 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
5648 - The "ClientDNSRejectInternalAddresses" config option wasn't being
5649 consistently obeyed: if an exit relay refuses a stream because its
5650 exit policy doesn't allow it, we would remember what IP address
5651 the relay said the destination address resolves to, even if it's
5652 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
5655 - Fix a DOS opportunity during the voting signature collection process
5656 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5658 o Major bugfixes (hidden services):
5659 - When fetching v0 and v2 rendezvous service descriptors in parallel,
5660 we were failing the whole hidden service request when the v0
5661 descriptor fetch fails, even if the v2 fetch is still pending and
5662 might succeed. Similarly, if the last v2 fetch fails, we were
5663 failing the whole hidden service request even if a v0 fetch is
5664 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
5665 - When extending a circuit to a hidden service directory to upload a
5666 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
5667 requests failed, because the router descriptor has not been
5668 downloaded yet. In these cases, do not attempt to upload the
5669 rendezvous descriptor, but wait until the router descriptor is
5670 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
5671 descriptor from a hidden service directory for which the router
5672 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
5676 - Fix several infrequent memory leaks spotted by Coverity.
5677 - When testing for libevent functions, set the LDFLAGS variable
5678 correctly. Found by Riastradh.
5679 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
5680 bootstrapping with tunneled directory connections. Bugfix on
5681 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
5682 - When asked to connect to A.B.exit:80, if we don't know the IP for A
5683 and we know that server B rejects most-but-not all connections to
5684 port 80, we would previously reject the connection. Now, we assume
5685 the user knows what they were asking for. Fixes bug 752. Bugfix
5686 on 0.0.9rc5. Diagnosed by BarkerJr.
5687 - If we overrun our per-second write limits a little, count this as
5688 having used up our write allocation for the second, and choke
5689 outgoing directory writes. Previously, we had only counted this when
5690 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
5691 Bugfix on 0.2.0.x (??).
5692 - Remove the old v2 directory authority 'lefkada' from the default
5693 list. It has been gone for many months.
5694 - Stop doing unaligned memory access that generated bus errors on
5695 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
5696 - Make USR2 log-level switch take effect immediately. Bugfix on
5699 o Minor bugfixes (controller):
5700 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
5701 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
5704 Changes in version 0.2.0.31 - 2008-09-03
5705 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
5706 a big bug we're seeing where in rare cases traffic from one Tor stream
5707 gets mixed into another stream, and fixes a variety of smaller issues.
5710 - Make sure that two circuits can never exist on the same connection
5711 with the same circuit ID, even if one is marked for close. This
5712 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
5713 - Relays now reject risky extend cells: if the extend cell includes
5714 a digest of all zeroes, or asks to extend back to the relay that
5715 sent the extend cell, tear down the circuit. Ideas suggested
5717 - If not enough of our entry guards are available so we add a new
5718 one, we might use the new one even if it overlapped with the
5719 current circuit's exit relay (or its family). Anonymity bugfix
5720 pointed out by rovv.
5723 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
5724 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
5725 - Correctly detect the presence of the linux/netfilter_ipv4.h header
5726 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
5727 - Pick size of default geoip filename string correctly on windows.
5728 Fixes bug 806. Bugfix on 0.2.0.30.
5729 - Make the autoconf script accept the obsolete --with-ssl-dir
5730 option as an alias for the actually-working --with-openssl-dir
5731 option. Fix the help documentation to recommend --with-openssl-dir.
5732 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
5733 - When using the TransPort option on OpenBSD, and using the User
5734 option to change UID and drop privileges, make sure to open
5735 /dev/pf before dropping privileges. Fixes bug 782. Patch from
5736 Christopher Davis. Bugfix on 0.1.2.1-alpha.
5737 - Try to attach connections immediately upon receiving a RENDEZVOUS2
5738 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
5739 on the client side when connecting to a hidden service. Bugfix
5740 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
5741 - When closing an application-side connection because its circuit is
5742 getting torn down, generate the stream event correctly. Bugfix on
5743 0.1.2.x. Anonymous patch.
5746 Changes in version 0.2.0.30 - 2008-07-15
5747 This new stable release switches to a more efficient directory
5748 distribution design, adds features to make connections to the Tor
5749 network harder to block, allows Tor to act as a DNS proxy, adds separate
5750 rate limiting for relayed traffic to make it easier for clients to
5751 become relays, fixes a variety of potential anonymity problems, and
5752 includes the usual huge pile of other features and bug fixes.
5754 o New v3 directory design:
5755 - Tor now uses a new way to learn about and distribute information
5756 about the network: the directory authorities vote on a common
5757 network status document rather than each publishing their own
5758 opinion. Now clients and caches download only one networkstatus
5759 document to bootstrap, rather than downloading one for each
5760 authority. Clients only download router descriptors listed in
5761 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
5763 - Set up moria1, tor26, and dizum as v3 directory authorities
5764 in addition to being v2 authorities. Also add three new ones:
5765 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
5766 dannenberg (run by CCC).
5767 - Switch to multi-level keys for directory authorities: now their
5768 long-term identity key can be kept offline, and they periodically
5769 generate a new signing key. Clients fetch the "key certificates"
5770 to keep up to date on the right keys. Add a standalone tool
5771 "tor-gencert" to generate key certificates. Implements proposal 103.
5772 - Add a new V3AuthUseLegacyKey config option to make it easier for
5773 v3 authorities to change their identity keys if another bug like
5774 Debian's OpenSSL RNG flaw appears.
5775 - Authorities and caches fetch the v2 networkstatus documents
5776 less often, now that v3 is recommended.
5778 o Make Tor connections stand out less on the wire:
5779 - Use an improved TLS handshake designed by Steven Murdoch in proposal
5780 124, as revised in proposal 130. The new handshake is meant to
5781 be harder for censors to fingerprint, and it adds the ability
5782 to detect certain kinds of man-in-the-middle traffic analysis
5783 attacks. The new handshake format includes version negotiation for
5784 OR connections as described in proposal 105, which will allow us
5785 to improve Tor's link protocol more safely in the future.
5786 - Enable encrypted directory connections by default for non-relays,
5787 so censor tools that block Tor directory connections based on their
5788 plaintext patterns will no longer work. This means Tor works in
5789 certain censored countries by default again.
5790 - Stop including recognizeable strings in the commonname part of
5791 Tor's x509 certificates.
5793 o Implement bridge relays:
5794 - Bridge relays (or "bridges" for short) are Tor relays that aren't
5795 listed in the main Tor directory. Since there is no complete public
5796 list of them, even an ISP that is filtering connections to all the
5797 known Tor relays probably won't be able to block all the bridges.
5798 See doc/design-paper/blocking.pdf and proposal 125 for details.
5799 - New config option BridgeRelay that specifies you want to be a
5800 bridge relay rather than a normal relay. When BridgeRelay is set
5801 to 1, then a) you cache dir info even if your DirPort ins't on,
5802 and b) the default for PublishServerDescriptor is now "bridge"
5803 rather than "v2,v3".
5804 - New config option "UseBridges 1" for clients that want to use bridge
5805 relays instead of ordinary entry guards. Clients then specify
5806 bridge relays by adding "Bridge" lines to their config file. Users
5807 can learn about a bridge relay either manually through word of
5808 mouth, or by one of our rate-limited mechanisms for giving out
5809 bridge addresses without letting an attacker easily enumerate them
5810 all. See https://www.torproject.org/bridges for details.
5811 - Bridge relays behave like clients with respect to time intervals
5812 for downloading new v3 consensus documents -- otherwise they
5813 stand out. Bridge users now wait until the end of the interval,
5814 so their bridge relay will be sure to have a new consensus document.
5816 o Implement bridge directory authorities:
5817 - Bridge authorities are like normal directory authorities, except
5818 they don't serve a list of known bridges. Therefore users that know
5819 a bridge's fingerprint can fetch a relay descriptor for that bridge,
5820 including fetching updates e.g. if the bridge changes IP address,
5821 yet an attacker can't just fetch a list of all the bridges.
5822 - Set up Tonga as the default bridge directory authority.
5823 - Bridge authorities refuse to serve bridge descriptors or other
5824 bridge information over unencrypted connections (that is, when
5825 responding to direct DirPort requests rather than begin_dir cells.)
5826 - Bridge directory authorities do reachability testing on the
5827 bridges they know. They provide router status summaries to the
5828 controller via "getinfo ns/purpose/bridge", and also dump summaries
5829 to a file periodically, so we can keep internal stats about which
5830 bridges are functioning.
5831 - If bridge users set the UpdateBridgesFromAuthority config option,
5832 but the digest they ask for is a 404 on the bridge authority,
5833 they fall back to contacting the bridge directly.
5834 - Bridges always use begin_dir to publish their server descriptor to
5835 the bridge authority using an anonymous encrypted tunnel.
5836 - Early work on a "bridge community" design: if bridge authorities set
5837 the BridgePassword config option, they will serve a snapshot of
5838 known bridge routerstatuses from their DirPort to anybody who
5839 knows that password. Unset by default.
5840 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
5841 report sanitized aggregated summaries in their extra-info documents
5842 privately to the bridge authority, listing which countries are
5843 able to reach them. We hope this mechanism will let us learn when
5844 certain countries start trying to block bridges.
5845 - Bridge authorities write bridge descriptors to disk, so they can
5846 reload them after a reboot. They can also export the descriptors
5847 to other programs, so we can distribute them to blocked users via
5848 the BridgeDB interface, e.g. via https://bridges.torproject.org/
5849 and bridges@torproject.org.
5851 o Tor can be a DNS proxy:
5852 - The new client-side DNS proxy feature replaces the need for
5853 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
5854 for DNS requests on port 9999, use the Tor network to resolve them
5855 anonymously, and send the reply back like a regular DNS server.
5856 The code still only implements a subset of DNS.
5857 - Add a new AutomapHostsOnResolve option: when it is enabled, any
5858 resolve request for hosts matching a given pattern causes Tor to
5859 generate an internal virtual address mapping for that host. This
5860 allows DNSPort to work sensibly with hidden service users. By
5861 default, .exit and .onion addresses are remapped; the list of
5862 patterns can be reconfigured with AutomapHostsSuffixes.
5863 - Add an "-F" option to tor-resolve to force a resolve for a .onion
5864 address. Thanks to the AutomapHostsOnResolve option, this is no
5865 longer a completely silly thing to do.
5867 o Major features (relay usability):
5868 - New config options RelayBandwidthRate and RelayBandwidthBurst:
5869 a separate set of token buckets for relayed traffic. Right now
5870 relayed traffic is defined as answers to directory requests, and
5871 OR connections that don't have any local circuits on them. See
5872 proposal 111 for details.
5873 - Create listener connections before we setuid to the configured
5874 User and Group. Now non-Windows users can choose port values
5875 under 1024, start Tor as root, and have Tor bind those ports
5876 before it changes to another UID. (Windows users could already
5878 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
5879 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
5880 on "vserver" accounts. Patch from coderman.
5882 o Major features (directory authorities):
5883 - Directory authorities track weighted fractional uptime and weighted
5884 mean-time-between failures for relays. WFU is suitable for deciding
5885 whether a node is "usually up", while MTBF is suitable for deciding
5886 whether a node is "likely to stay up." We need both, because
5887 "usually up" is a good requirement for guards, while "likely to
5888 stay up" is a good requirement for long-lived connections.
5889 - Directory authorities use a new formula for selecting which relays
5890 to advertise as Guards: they must be in the top 7/8 in terms of
5891 how long we have known about them, and above the median of those
5892 nodes in terms of weighted fractional uptime.
5893 - Directory authorities use a new formula for selecting which relays
5894 to advertise as Stable: when we have 4 or more days of data, use
5895 median measured MTBF rather than median declared uptime. Implements
5897 - Directory authorities accept and serve "extra info" documents for
5898 routers. Routers now publish their bandwidth-history lines in the
5899 extra-info docs rather than the main descriptor. This step saves
5900 60% (!) on compressed router descriptor downloads. Servers upload
5901 extra-info docs to any authority that accepts them; directory
5902 authorities now allow multiple router descriptors and/or extra
5903 info documents to be uploaded in a single go. Authorities, and
5904 caches that have been configured to download extra-info documents,
5905 download them as needed. Implements proposal 104.
5906 - Authorities now list relays who have the same nickname as
5907 a different named relay, but list them with a new flag:
5908 "Unnamed". Now we can make use of relays that happen to pick the
5909 same nickname as a server that registered two years ago and then
5910 disappeared. Implements proposal 122.
5911 - Store routers in a file called cached-descriptors instead of in
5912 cached-routers. Initialize cached-descriptors from cached-routers
5913 if the old format is around. The new format allows us to store
5914 annotations along with descriptors, to record the time we received
5915 each descriptor, its source, and its purpose: currently one of
5916 general, controller, or bridge.
5918 o Major features (other):
5919 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
5920 Tor can warn and/or refuse connections to ports commonly used with
5921 vulnerable-plaintext protocols. Currently we warn on ports 23,
5922 109, 110, and 143, but we don't reject any. Based on proposal 129
5923 by Kevin Bauer and Damon McCoy.
5924 - Integrate Karsten Loesing's Google Summer of Code project to publish
5925 hidden service descriptors on a set of redundant relays that are a
5926 function of the hidden service address. Now we don't have to rely
5927 on three central hidden service authorities for publishing and
5928 fetching every hidden service descriptor. Implements proposal 114.
5929 - Allow tunnelled directory connections to ask for an encrypted
5930 "begin_dir" connection or an anonymized "uses a full Tor circuit"
5931 connection independently. Now we can make anonymized begin_dir
5932 connections for (e.g.) more secure hidden service posting and
5935 o Major bugfixes (crashes and assert failures):
5936 - Stop imposing an arbitrary maximum on the number of file descriptors
5937 used for busy servers. Bug reported by Olaf Selke; patch from
5939 - Avoid possible failures when generating a directory with routers
5940 with over-long versions strings, or too many flags set.
5941 - Fix a rare assert error when we're closing one of our threads:
5942 use a mutex to protect the list of logs, so we never write to the
5943 list as it's being freed. Fixes the very rare bug 575, which is
5944 kind of the revenge of bug 222.
5945 - Avoid segfault in the case where a badly behaved v2 versioning
5946 directory sends a signed networkstatus with missing client-versions.
5947 - When we hit an EOF on a log (probably because we're shutting down),
5948 don't try to remove the log from the list: just mark it as
5949 unusable. (Bulletproofs against bug 222.)
5951 o Major bugfixes (code security fixes):
5952 - Detect size overflow in zlib code. Reported by Justin Ferguson and
5954 - Rewrite directory tokenization code to never run off the end of
5955 a string. Fixes bug 455. Patch from croup.
5956 - Be more paranoid about overwriting sensitive memory on free(),
5957 as a defensive programming tactic to ensure forward secrecy.
5959 o Major bugfixes (anonymity fixes):
5960 - Reject requests for reverse-dns lookup of names that are in
5961 a private address space. Patch from lodger.
5962 - Never report that we've used more bandwidth than we're willing to
5963 relay: it leaks how much non-relay traffic we're using. Resolves
5965 - As a client, do not believe any server that tells us that an
5966 address maps to an internal address space.
5967 - Warn about unsafe ControlPort configurations.
5968 - Directory authorities now call routers Fast if their bandwidth is
5969 at least 100KB/s, and consider their bandwidth adequate to be a
5970 Guard if it is at least 250KB/s, no matter the medians. This fix
5971 complements proposal 107.
5972 - Directory authorities now never mark more than 2 servers per IP as
5973 Valid and Running (or 5 on addresses shared by authorities).
5974 Implements proposal 109, by Kevin Bauer and Damon McCoy.
5975 - If we're a relay, avoid picking ourselves as an introduction point,
5976 a rendezvous point, or as the final hop for internal circuits. Bug
5977 reported by taranis and lodger.
5978 - Exit relays that are used as a client can now reach themselves
5979 using the .exit notation, rather than just launching an infinite
5980 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
5981 - Fix a bug where, when we were choosing the 'end stream reason' to
5982 put in our relay end cell that we send to the exit relay, Tor
5983 clients on Windows were sometimes sending the wrong 'reason'. The
5984 anonymity problem is that exit relays may be able to guess whether
5985 the client is running Windows, thus helping partition the anonymity
5986 set. Down the road we should stop sending reasons to exit relays,
5987 or otherwise prevent future versions of this bug.
5988 - Only update guard status (usable / not usable) once we have
5989 enough directory information. This was causing us to discard all our
5990 guards on startup if we hadn't been running for a few weeks. Fixes
5992 - When our directory information has been expired for a while, stop
5993 being willing to build circuits using it. Fixes bug 401.
5995 o Major bugfixes (peace of mind for relay operators)
5996 - Non-exit relays no longer answer "resolve" relay cells, so they
5997 can't be induced to do arbitrary DNS requests. (Tor clients already
5998 avoid using non-exit relays for resolve cells, but now servers
5999 enforce this too.) Fixes bug 619. Patch from lodger.
6000 - When we setconf ClientOnly to 1, close any current OR and Dir
6001 listeners. Reported by mwenge.
6003 o Major bugfixes (other):
6004 - If we only ever used Tor for hidden service lookups or posts, we
6005 would stop building circuits and start refusing connections after
6006 24 hours, since we falsely believed that Tor was dormant. Reported
6008 - Add a new __HashedControlSessionPassword option for controllers
6009 to use for one-off session password hashes that shouldn't get
6010 saved to disk by SAVECONF --- Vidalia users were accumulating a
6011 pile of HashedControlPassword lines in their torrc files, one for
6012 each time they had restarted Tor and then clicked Save. Make Tor
6013 automatically convert "HashedControlPassword" to this new option but
6014 only when it's given on the command line. Partial fix for bug 586.
6015 - Patch from "Andrew S. Lists" to catch when we contact a directory
6016 mirror at IP address X and he says we look like we're coming from
6017 IP address X. Otherwise this would screw up our address detection.
6018 - Reject uploaded descriptors and extrainfo documents if they're
6019 huge. Otherwise we'll cache them all over the network and it'll
6020 clog everything up. Suggested by Aljosha Judmayer.
6021 - When a hidden service was trying to establish an introduction point,
6022 and Tor *did* manage to reuse one of the preemptively built
6023 circuits, it didn't correctly remember which one it used,
6024 so it asked for another one soon after, until there were no
6025 more preemptive circuits, at which point it launched one from
6026 scratch. Bugfix on 0.0.9.x.
6028 o Rate limiting and load balancing improvements:
6029 - When we add data to a write buffer in response to the data on that
6030 write buffer getting low because of a flush, do not consider the
6031 newly added data as a candidate for immediate flushing, but rather
6032 make it wait until the next round of writing. Otherwise, we flush
6033 and refill recursively, and a single greedy TLS connection can
6034 eat all of our bandwidth.
6035 - When counting the number of bytes written on a TLS connection,
6036 look at the BIO actually used for writing to the network, not
6037 at the BIO used (sometimes) to buffer data for the network.
6038 Looking at different BIOs could result in write counts on the
6039 order of ULONG_MAX. Fixes bug 614.
6040 - If we change our MaxAdvertisedBandwidth and then reload torrc,
6041 Tor won't realize it should publish a new relay descriptor. Fixes
6042 bug 688, reported by mfr.
6043 - Avoid using too little bandwidth when our clock skips a few seconds.
6044 - Choose which bridge to use proportional to its advertised bandwidth,
6045 rather than uniformly at random. This should speed up Tor for
6046 bridge users. Also do this for people who set StrictEntryNodes.
6048 o Bootstrapping faster and building circuits more intelligently:
6049 - Fix bug 660 that was preventing us from knowing that we should
6050 preemptively build circuits to handle expected directory requests.
6051 - When we're checking if we have enough dir info for each relay
6052 to begin establishing circuits, make sure that we actually have
6053 the descriptor listed in the consensus, not just any descriptor.
6054 - Correctly notify one-hop connections when a circuit build has
6055 failed. Possible fix for bug 669. Found by lodger.
6056 - Clients now hold circuitless TLS connections open for 1.5 times
6057 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
6058 rebuild a new circuit over them within that timeframe. Previously,
6059 they held them open only for KeepalivePeriod (5 minutes).
6061 o Performance improvements (memory):
6062 - Add OpenBSD malloc code from "phk" as an optional malloc
6063 replacement on Linux: some glibc libraries do very poorly with
6064 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
6065 ./configure to get the replacement malloc code.
6066 - Switch our old ring buffer implementation for one more like that
6067 used by free Unix kernels. The wasted space in a buffer with 1mb
6068 of data will now be more like 8k than 1mb. The new implementation
6069 also avoids realloc();realloc(); patterns that can contribute to
6070 memory fragmentation.
6071 - Change the way that Tor buffers data that it is waiting to write.
6072 Instead of queueing data cells in an enormous ring buffer for each
6073 client->OR or OR->OR connection, we now queue cells on a separate
6074 queue for each circuit. This lets us use less slack memory, and
6075 will eventually let us be smarter about prioritizing different kinds
6077 - Reference-count and share copies of address policy entries; only 5%
6078 of them were actually distinct.
6079 - Tune parameters for cell pool allocation to minimize amount of
6081 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
6082 for every single inactive connection_t. Free items from the
6083 4k/16k-buffer free lists when they haven't been used for a while.
6084 - Make memory debugging information describe more about history
6085 of cell allocation, so we can help reduce our memory use.
6086 - Be even more aggressive about releasing RAM from small
6087 empty buffers. Thanks to our free-list code, this shouldn't be too
6088 performance-intensive.
6089 - Log malloc statistics from mallinfo() on platforms where it exists.
6090 - Use memory pools to allocate cells with better speed and memory
6091 efficiency, especially on platforms where malloc() is inefficient.
6092 - Add a --with-tcmalloc option to the configure script to link
6093 against tcmalloc (if present). Does not yet search for non-system
6096 o Performance improvements (socket management):
6097 - Count the number of open sockets separately from the number of
6098 active connection_t objects. This will let us avoid underusing
6099 our allocated connection limit.
6100 - We no longer use socket pairs to link an edge connection to an
6101 anonymous directory connection or a DirPort test connection.
6102 Instead, we track the link internally and transfer the data
6103 in-process. This saves two sockets per "linked" connection (at the
6104 client and at the server), and avoids the nasty Windows socketpair()
6106 - We were leaking a file descriptor if Tor started with a zero-length
6107 cached-descriptors file. Patch by "freddy77".
6109 o Performance improvements (CPU use):
6110 - Never walk through the list of logs if we know that no log target
6111 is interested in a given message.
6112 - Call routerlist_remove_old_routers() much less often. This should
6113 speed startup, especially on directory caches.
6114 - Base64 decoding was actually showing up on our profile when parsing
6115 the initial descriptor file; switch to an in-process all-at-once
6116 implementation that's about 3.5x times faster than calling out to
6118 - Use a slightly simpler string hashing algorithm (copying Python's
6119 instead of Java's) and optimize our digest hashing algorithm to take
6120 advantage of 64-bit platforms and to remove some possibly-costly
6122 - When implementing AES counter mode, update only the portions of the
6123 counter buffer that need to change, and don't keep separate
6124 network-order and host-order counters on big-endian hosts (where
6126 - Add an in-place version of aes_crypt() so that we can avoid doing a
6127 needless memcpy() call on each cell payload.
6128 - Use Critical Sections rather than Mutexes for synchronizing threads
6129 on win32; Mutexes are heavier-weight, and designed for synchronizing
6132 o Performance improvements (bandwidth use):
6133 - Don't try to launch new descriptor downloads quite so often when we
6134 already have enough directory information to build circuits.
6135 - Version 1 directories are no longer generated in full. Instead,
6136 authorities generate and serve "stub" v1 directories that list
6137 no servers. This will stop Tor versions 0.1.0.x and earlier from
6138 working, but (for security reasons) nobody should be running those
6140 - Avoid going directly to the directory authorities even if you're a
6141 relay, if you haven't found yourself reachable yet or if you've
6142 decided not to advertise your dirport yet. Addresses bug 556.
6143 - If we've gone 12 hours since our last bandwidth check, and we
6144 estimate we have less than 50KB bandwidth capacity but we could
6145 handle more, do another bandwidth test.
6146 - Support "If-Modified-Since" when answering HTTP requests for
6147 directories, running-routers documents, and v2 and v3 networkstatus
6148 documents. (There's no need to support it for router descriptors,
6149 since those are downloaded by descriptor digest.)
6150 - Stop fetching directory info so aggressively if your DirPort is
6151 on but your ORPort is off; stop fetching v2 dir info entirely.
6152 You can override these choices with the new FetchDirInfoEarly
6155 o Changed config option behavior (features):
6156 - Configuration files now accept C-style strings as values. This
6157 helps encode characters not allowed in the current configuration
6158 file format, such as newline or #. Addresses bug 557.
6159 - Add hidden services and DNSPorts to the list of things that make
6160 Tor accept that it has running ports. Change starting Tor with no
6161 ports from a fatal error to a warning; we might change it back if
6162 this turns out to confuse anybody. Fixes bug 579.
6163 - Make PublishServerDescriptor default to 1, so the default doesn't
6164 have to change as we invent new directory protocol versions.
6165 - Allow people to say PreferTunnelledDirConns rather than
6166 PreferTunneledDirConns, for those alternate-spellers out there.
6167 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
6168 accommodate the growing number of servers that use the default
6169 and are reaching it.
6170 - Make it possible to enable HashedControlPassword and
6171 CookieAuthentication at the same time.
6172 - When a TrackHostExits-chosen exit fails too many times in a row,
6173 stop using it. Fixes bug 437.
6175 o Changed config option behavior (bugfixes):
6176 - Do not read the configuration file when we've only been told to
6177 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
6178 based on patch from Sebastian Hahn.
6179 - Actually validate the options passed to AuthDirReject,
6180 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
6181 - Make "ClientOnly 1" config option disable directory ports too.
6182 - Don't stop fetching descriptors when FetchUselessDescriptors is
6183 set, even if we stop asking for circuits. Bug reported by tup
6185 - Servers used to decline to publish their DirPort if their
6186 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
6187 they look only at BandwidthRate and RelayBandwidthRate.
6188 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
6189 minus 1 byte: the actual maximum declared bandwidth.
6190 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
6191 - Make the NodeFamilies config option work. (Reported by
6192 lodger -- it has never actually worked, even though we added it
6194 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
6195 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
6197 o New config options:
6198 - New configuration options AuthDirMaxServersPerAddr and
6199 AuthDirMaxServersperAuthAddr to override default maximum number
6200 of servers allowed on a single IP address. This is important for
6201 running a test network on a single host.
6202 - Three new config options (AlternateDirAuthority,
6203 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
6204 user selectively replace the default directory authorities by type,
6205 rather than the all-or-nothing replacement that DirServer offers.
6206 - New config options AuthDirBadDir and AuthDirListBadDirs for
6207 authorities to mark certain relays as "bad directories" in the
6208 networkstatus documents. Also supports the "!baddir" directive in
6209 the approved-routers file.
6210 - New config option V2AuthoritativeDirectory that all v2 directory
6211 authorities must set. This lets v3 authorities choose not to serve
6212 v2 directory information.
6214 o Minor features (other):
6215 - When we're not serving v2 directory information, there is no reason
6216 to actually keep any around. Remove the obsolete files and directory
6217 on startup if they are very old and we aren't going to serve them.
6218 - When we negotiate a v2 link-layer connection (not yet implemented),
6219 accept RELAY_EARLY cells and turn them into RELAY cells if we've
6220 negotiated a v1 connection for their next step. Initial steps for
6222 - When we have no consensus, check FallbackNetworkstatusFile (defaults
6223 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
6224 we can start out knowing some directory caches. We don't ship with
6225 a fallback consensus by default though, because it was making
6226 bootstrapping take too long while we tried many down relays.
6227 - Authorities send back an X-Descriptor-Not-New header in response to
6228 an accepted-but-discarded descriptor upload. Partially implements
6230 - If we find a cached-routers file that's been sitting around for more
6231 than 28 days unmodified, then most likely it's a leftover from
6232 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
6234 - When we (as a cache) download a descriptor because it was listed
6235 in a consensus, remember when the consensus was supposed to expire,
6236 and don't expire the descriptor until then.
6237 - Optionally (if built with -DEXPORTMALLINFO) export the output
6238 of mallinfo via http, as tor/mallinfo.txt. Only accessible
6240 - Tag every guard node in our state file with the version that
6241 we believe added it, or with our own version if we add it. This way,
6242 if a user temporarily runs an old version of Tor and then switches
6243 back to a new one, she doesn't automatically lose her guards.
6244 - When somebody requests a list of statuses or servers, and we have
6245 none of those, return a 404 rather than an empty 200.
6246 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
6248 - Add an HSAuthorityRecordStats option that hidden service authorities
6249 can use to track statistics of overall hidden service usage without
6250 logging information that would be as useful to an attacker.
6251 - Allow multiple HiddenServicePort directives with the same virtual
6252 port; when they occur, the user is sent round-robin to one
6253 of the target ports chosen at random. Partially fixes bug 393 by
6254 adding limited ad-hoc round-robining.
6255 - Revamp file-writing logic so we don't need to have the entire
6256 contents of a file in memory at once before we write to disk. Tor,
6259 o Minor bugfixes (other):
6260 - Alter the code that tries to recover from unhandled write
6261 errors, to not try to flush onto a socket that's given us
6263 - Directory mirrors no longer include a guess at the client's IP
6264 address if the connection appears to be coming from the same /24
6265 network; it was producing too many wrong guesses.
6266 - If we're trying to flush the last bytes on a connection (for
6267 example, when answering a directory request), reset the
6268 time-to-give-up timeout every time we manage to write something
6270 - Reject router descriptors with out-of-range bandwidthcapacity or
6271 bandwidthburst values.
6272 - If we can't expand our list of entry guards (e.g. because we're
6273 using bridges or we have StrictEntryNodes set), don't mark relays
6274 down when they fail a directory request. Otherwise we're too quick
6275 to mark all our entry points down.
6276 - Authorities no longer send back "400 you're unreachable please fix
6277 it" errors to Tor servers that aren't online all the time. We're
6278 supposed to tolerate these servers now.
6279 - Let directory authorities startup even when they can't generate
6280 a descriptor immediately, e.g. because they don't know their
6282 - Correctly enforce that elements of directory objects do not appear
6283 more often than they are allowed to appear.
6284 - Stop allowing hibernating servers to be "stable" or "fast".
6285 - On Windows, we were preventing other processes from reading
6286 cached-routers while Tor was running. (Reported by janbar)
6287 - Check return values from pthread_mutex functions.
6288 - When opening /dev/null in finish_daemonize(), do not pass the
6289 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
6290 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
6292 o Controller features:
6293 - The GETCONF command now escapes and quotes configuration values
6294 that don't otherwise fit into the torrc file.
6295 - The SETCONF command now handles quoted values correctly.
6296 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
6297 ask about source, timestamp of arrival, purpose, etc. We need
6298 something like this to help Vidalia not do GeoIP lookups on bridge
6300 - Allow multiple HashedControlPassword config lines, to support
6301 multiple controller passwords.
6302 - Accept LF instead of CRLF on controller, since some software has a
6303 hard time generating real Internet newlines.
6304 - Add GETINFO values for the server status events
6305 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
6307 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
6308 GETINFO for Torstat to use until it can switch to using extrainfos.
6309 - New config option CookieAuthFile to choose a new location for the
6310 cookie authentication file, and config option
6311 CookieAuthFileGroupReadable to make it group-readable.
6312 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
6313 match requests to applications. Patch from Robert Hogan.
6314 - Add a RESOLVE command to launch hostname lookups. Original patch
6316 - Add GETINFO status/enough-dir-info to let controllers tell whether
6317 Tor has downloaded sufficient directory information. Patch from Tup.
6318 - You can now use the ControlSocket option to tell Tor to listen for
6319 controller connections on Unix domain sockets on systems that
6320 support them. Patch from Peter Palfrader.
6321 - New "GETINFO address-mappings/*" command to get address mappings
6322 with expiry information. "addr-mappings/*" is now deprecated.
6324 - Add a new config option __DisablePredictedCircuits designed for
6325 use by the controller, when we don't want Tor to build any circuits
6327 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
6328 so we can exit from the middle of the circuit.
6329 - Implement "getinfo status/circuit-established".
6330 - Implement "getinfo status/version/..." so a controller can tell
6331 whether the current version is recommended, and whether any versions
6332 are good, and how many authorities agree. Patch from "shibz".
6333 - Controllers should now specify cache=no or cache=yes when using
6334 the +POSTDESCRIPTOR command.
6335 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
6336 Robert Hogan. Fixes the first part of bug 681.
6337 - When reporting clock skew, and we know that the clock is _at least
6338 as skewed_ as some value, but we don't know the actual value,
6339 report the value as a "minimum skew."
6341 o Controller bugfixes:
6342 - Generate "STATUS_SERVER" events rather than misspelled
6343 "STATUS_SEVER" events. Caught by mwenge.
6344 - Reject controller commands over 1MB in length, so rogue
6345 processes can't run us out of memory.
6346 - Change the behavior of "getinfo status/good-server-descriptor"
6347 so it doesn't return failure when any authority disappears.
6348 - Send NAMESERVER_STATUS messages for a single failed nameserver
6350 - When the DANGEROUS_VERSION controller status event told us we're
6351 running an obsolete version, it used the string "OLD" to describe
6352 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
6353 "OBSOLETE" in both cases.
6354 - Respond to INT and TERM SIGNAL commands before we execute the
6355 signal, in case the signal shuts us down. We had a patch in
6356 0.1.2.1-alpha that tried to do this by queueing the response on
6357 the connection's buffer before shutting down, but that really
6358 isn't the same thing at all. Bug located by Matt Edman.
6359 - Provide DNS expiry times in GMT, not in local time. For backward
6360 compatibility, ADDRMAP events only provide GMT expiry in an extended
6361 field. "GETINFO address-mappings" always does the right thing.
6362 - Use CRLF line endings properly in NS events.
6363 - Make 'getinfo fingerprint' return a 551 error if we're not a
6364 server, so we match what the control spec claims we do. Reported
6366 - Fix a typo in an error message when extendcircuit fails that
6367 caused us to not follow the \r\n-based delimiter protocol. Reported
6369 - When tunneling an encrypted directory connection, and its first
6370 circuit fails, do not leave it unattached and ask the controller
6371 to deal. Fixes the second part of bug 681.
6372 - Treat some 403 responses from directory servers as INFO rather than
6373 WARN-severity events.
6375 o Portability / building / compiling:
6376 - When building with --enable-gcc-warnings, check for whether Apple's
6377 warning "-Wshorten-64-to-32" is available.
6378 - Support compilation to target iPhone; patch from cjacker huang.
6379 To build for iPhone, pass the --enable-iphone option to configure.
6380 - Port Tor to build and run correctly on Windows CE systems, using
6381 the wcecompat library. Contributed by Valerio Lupi.
6382 - Detect non-ASCII platforms (if any still exist) and refuse to
6383 build there: some of our code assumes that 'A' is 65 and so on.
6384 - Clear up some MIPSPro compiler warnings.
6385 - Make autoconf search for libevent, openssl, and zlib consistently.
6386 - Update deprecated macros in configure.in.
6387 - When warning about missing headers, tell the user to let us
6388 know if the compile succeeds anyway, so we can downgrade the
6390 - Include the current subversion revision as part of the version
6391 string: either fetch it directly if we're in an SVN checkout, do
6392 some magic to guess it if we're in an SVK checkout, or use
6393 the last-detected version if we're building from a .tar.gz.
6394 Use this version consistently in log messages.
6395 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
6396 - Read resolv.conf files correctly on platforms where read() returns
6397 partial results on small file reads.
6398 - Build without verbose warnings even on gcc 4.2 and 4.3.
6399 - On Windows, correctly detect errors when listing the contents of
6400 a directory. Fix from lodger.
6401 - Run 'make test' as part of 'make dist', so we stop releasing so
6402 many development snapshots that fail their unit tests.
6403 - Add support to detect Libevent versions in the 1.4.x series
6405 - Add command-line arguments to unit-test executable so that we can
6406 invoke any chosen test from the command line rather than having
6407 to run the whole test suite at once; and so that we can turn on
6408 logging for the unit tests.
6409 - Do not automatically run configure from autogen.sh. This
6410 non-standard behavior tended to annoy people who have built other
6412 - Fix a macro/CPP interaction that was confusing some compilers:
6413 some GCCs don't like #if/#endif pairs inside macro arguments.
6415 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
6416 Fixes bug 704; fix from Steven Murdoch.
6417 - Correctly detect transparent proxy support on Linux hosts that
6418 require in.h to be included before netfilter_ipv4.h. Patch
6421 o Logging improvements:
6422 - When we haven't had any application requests lately, don't bother
6423 logging that we have expired a bunch of descriptors.
6424 - When attempting to open a logfile fails, tell us why.
6425 - Only log guard node status when guard node status has changed.
6426 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
6427 make "INFO" 75% less verbose.
6428 - When SafeLogging is disabled, log addresses along with all TLS
6430 - Report TLS "zero return" case as a "clean close" and "IO error"
6431 as a "close". Stop calling closes "unexpected closes": existing
6432 Tors don't use SSL_close(), so having a connection close without
6433 the TLS shutdown handshake is hardly unexpected.
6434 - When we receive a consensus from the future, warn about skew.
6435 - Make "not enough dir info yet" warnings describe *why* Tor feels
6436 it doesn't have enough directory info yet.
6437 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
6438 consumers. (We already do this on HUP.)
6439 - Give more descriptive well-formedness errors for out-of-range
6440 hidden service descriptor/protocol versions.
6441 - Stop recommending that every server operator send mail to tor-ops.
6442 Resolves bug 597. Bugfix on 0.1.2.x.
6443 - Improve skew reporting: try to give the user a better log message
6444 about how skewed they are, and how much this matters.
6445 - New --quiet command-line option to suppress the default console log.
6446 Good in combination with --hash-password.
6447 - Don't complain that "your server has not managed to confirm that its
6448 ports are reachable" if we haven't been able to build any circuits
6450 - Detect the reason for failing to mmap a descriptor file we just
6451 wrote, and give a more useful log message. Fixes bug 533.
6452 - Always prepend "Bug: " to any log message about a bug.
6453 - When dumping memory usage, list bytes used in buffer memory
6455 - When running with dmalloc, dump more stats on hup and on exit.
6456 - Put a platform string (e.g. "Linux i686") in the startup log
6457 message, so when people paste just their logs, we know if it's
6458 OpenBSD or Windows or what.
6459 - When logging memory usage, break down memory used in buffers by
6461 - When we are reporting the DirServer line we just parsed, we were
6462 logging the second stanza of the key fingerprint, not the first.
6463 - Even though Windows is equally happy with / and \ as path separators,
6464 try to use \ consistently on Windows and / consistently on Unix: it
6465 makes the log messages nicer.
6466 - On OSX, stop warning the user that kqueue support in libevent is
6467 "experimental", since it seems to have worked fine for ages.
6469 o Contributed scripts and tools:
6470 - Update linux-tor-prio.sh script to allow QoS based on the uid of
6471 the Tor process. Patch from Marco Bonetti with tweaks from Mike
6473 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
6474 Unix users an easy way to script their Tor process (e.g. by
6475 adjusting bandwidth based on the time of the day).
6476 - In the exitlist script, only consider the most recently published
6477 server descriptor for each server. Also, when the user requests
6478 a list of servers that _reject_ connections to a given address,
6479 explicitly exclude the IPs that also have servers that accept
6480 connections to that address. Resolves bug 405.
6481 - Include a new contrib/tor-exit-notice.html file that exit relay
6482 operators can put on their website to help reduce abuse queries.
6484 o Newly deprecated features:
6485 - The status/version/num-versioning and status/version/num-concurring
6486 GETINFO controller options are no longer useful in the v3 directory
6487 protocol: treat them as deprecated, and warn when they're used.
6488 - The RedirectExits config option is now deprecated.
6491 - Drop the old code to choke directory connections when the
6492 corresponding OR connections got full: thanks to the cell queue
6493 feature, OR conns don't get full any more.
6494 - Remove the old "dns worker" server DNS code: it hasn't been default
6495 since 0.1.2.2-alpha, and all the servers are using the new
6497 - Remove the code to generate the oldest (v1) directory format.
6498 - Remove support for the old bw_accounting file: we've been storing
6499 bandwidth accounting information in the state file since
6500 0.1.2.5-alpha. This may result in bandwidth accounting errors
6501 if you try to upgrade from 0.1.1.x or earlier, or if you try to
6502 downgrade to 0.1.1.x or earlier.
6503 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
6504 it, it had no AES, and it hasn't seen any security patches since
6506 - Stop overloading the circuit_t.onionskin field for both "onionskin
6507 from a CREATE cell that we are waiting for a cpuworker to be
6508 assigned" and "onionskin from an EXTEND cell that we are going to
6509 send to an OR as soon as we are connected". Might help with bug 600.
6510 - Remove the tor_strpartition() function: its logic was confused,
6511 and it was only used for one thing that could be implemented far
6513 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
6514 and TorControl.py, as they use the old v0 controller protocol,
6515 and are obsoleted by TorFlow anyway.
6516 - Drop support for v1 rendezvous descriptors, since we never used
6517 them anyway, and the code has probably rotted by now. Based on
6518 patch from Karsten Loesing.
6519 - Stop allowing address masks that do not correspond to bit prefixes.
6520 We have warned about these for a really long time; now it's time
6521 to reject them. (Patch from croup.)
6522 - Remove an optimization in the AES counter-mode code that assumed
6523 that the counter never exceeded 2^68. When the counter can be set
6524 arbitrarily as an IV (as it is by Karsten's new hidden services
6525 code), this assumption no longer holds.
6526 - Disable the SETROUTERPURPOSE controller command: it is now
6530 Changes in version 0.1.2.19 - 2008-01-17
6531 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
6532 exit policy a little bit more conservative so it's safer to run an
6533 exit relay on a home system, and fixes a variety of smaller issues.
6536 - Exit policies now reject connections that are addressed to a
6537 relay's public (external) IP address too, unless
6538 ExitPolicyRejectPrivate is turned off. We do this because too
6539 many relays are running nearby to services that trust them based
6543 - When the clock jumps forward a lot, do not allow the bandwidth
6544 buckets to become negative. Fixes bug 544.
6545 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
6546 on every successful resolve. Reported by Mike Perry.
6547 - Purge old entries from the "rephist" database and the hidden
6548 service descriptor database even when DirPort is zero.
6549 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
6550 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
6551 crashing or mis-answering these requests.
6552 - When we decide to send a 503 response to a request for servers, do
6553 not then also send the server descriptors: this defeats the whole
6554 purpose. Fixes bug 539.
6557 - Changing the ExitPolicyRejectPrivate setting should cause us to
6558 rebuild our server descriptor.
6559 - Fix handling of hex nicknames when answering controller requests for
6560 networkstatus by name, or when deciding whether to warn about
6561 unknown routers in a config option. (Patch from mwenge.)
6562 - Fix a couple of hard-to-trigger autoconf problems that could result
6563 in really weird results on platforms whose sys/types.h files define
6564 nonstandard integer types.
6565 - Don't try to create the datadir when running --verify-config or
6566 --hash-password. Resolves bug 540.
6567 - If we were having problems getting a particular descriptor from the
6568 directory caches, and then we learned about a new descriptor for
6569 that router, we weren't resetting our failure count. Reported
6571 - Although we fixed bug 539 (where servers would send HTTP status 503
6572 responses _and_ send a body too), there are still servers out there
6573 that haven't upgraded. Therefore, make clients parse such bodies
6574 when they receive them.
6575 - Run correctly on systems where rlim_t is larger than unsigned long.
6576 This includes some 64-bit systems.
6577 - Run correctly on platforms (like some versions of OS X 10.5) where
6578 the real limit for number of open files is OPEN_FILES, not rlim_max
6579 from getrlimit(RLIMIT_NOFILES).
6580 - Avoid a spurious free on base64 failure.
6581 - Avoid segfaults on certain complex invocations of
6582 router_get_by_hexdigest().
6583 - Fix rare bug on REDIRECTSTREAM control command when called with no
6584 port set: it could erroneously report an error when none had
6588 Changes in version 0.1.2.18 - 2007-10-28
6589 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
6590 hidden service introduction that were causing huge delays, and a big
6591 bug that was causing some servers to disappear from the network status
6592 lists for a few hours each day.
6594 o Major bugfixes (crashes):
6595 - If a connection is shut down abruptly because of something that
6596 happened inside connection_flushed_some(), do not call
6597 connection_finished_flushing(). Should fix bug 451:
6598 "connection_stop_writing: Assertion conn->write_event failed"
6599 Bugfix on 0.1.2.7-alpha.
6600 - Fix possible segfaults in functions called from
6601 rend_process_relay_cell().
6603 o Major bugfixes (hidden services):
6604 - Hidden services were choosing introduction points uniquely by
6605 hexdigest, but when constructing the hidden service descriptor
6606 they merely wrote the (potentially ambiguous) nickname.
6607 - Clients now use the v2 intro format for hidden service
6608 connections: they specify their chosen rendezvous point by identity
6609 digest rather than by (potentially ambiguous) nickname. These
6610 changes could speed up hidden service connections dramatically.
6612 o Major bugfixes (other):
6613 - Stop publishing a new server descriptor just because we get a
6614 HUP signal. This led (in a roundabout way) to some servers getting
6615 dropped from the networkstatus lists for a few hours each day.
6616 - When looking for a circuit to cannibalize, consider family as well
6617 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
6618 circuit cannibalization).
6619 - When a router wasn't listed in a new networkstatus, we were leaving
6620 the flags for that router alone -- meaning it remained Named,
6621 Running, etc -- even though absence from the networkstatus means
6622 that it shouldn't be considered to exist at all anymore. Now we
6623 clear all the flags for routers that fall out of the networkstatus
6624 consensus. Fixes bug 529.
6627 - Don't try to access (or alter) the state file when running
6628 --list-fingerprint or --verify-config or --hash-password. Resolves
6630 - When generating information telling us how to extend to a given
6631 router, do not try to include the nickname if it is
6632 absent. Resolves bug 467.
6633 - Fix a user-triggerable segfault in expand_filename(). (There isn't
6634 a way to trigger this remotely.)
6635 - When sending a status event to the controller telling it that an
6636 OR address is reachable, set the port correctly. (Previously we
6637 were reporting the dir port.)
6638 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
6639 command. Bugfix on 0.1.2.17.
6640 - When loading bandwidth history, do not believe any information in
6641 the future. Fixes bug 434.
6642 - When loading entry guard information, do not believe any information
6644 - When we have our clock set far in the future and generate an
6645 onion key, then re-set our clock to be correct, we should not stop
6646 the onion key from getting rotated.
6647 - On some platforms, accept() can return a broken address. Detect
6648 this more quietly, and deal accordingly. Fixes bug 483.
6649 - It's not actually an error to find a non-pending entry in the DNS
6650 cache when canceling a pending resolve. Don't log unless stuff
6651 is fishy. Resolves bug 463.
6652 - Don't reset trusted dir server list when we set a configuration
6653 option. Patch from Robert Hogan.
6656 Changes in version 0.1.2.17 - 2007-08-30
6657 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
6658 X bundles. Vidalia 0.0.14 makes authentication required for the
6659 ControlPort in the default configuration, which addresses important
6660 security risks. Everybody who uses Vidalia (or another controller)
6663 In addition, this Tor update fixes major load balancing problems with
6664 path selection, which should speed things up a lot once many people
6667 o Major bugfixes (security):
6668 - We removed support for the old (v0) control protocol. It has been
6669 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
6670 become more of a headache than it's worth.
6672 o Major bugfixes (load balancing):
6673 - When choosing nodes for non-guard positions, weight guards
6674 proportionally less, since they already have enough load. Patch
6676 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
6677 will allow fast Tor servers to get more attention.
6678 - When we're upgrading from an old Tor version, forget our current
6679 guards and pick new ones according to the new weightings. These
6680 three load balancing patches could raise effective network capacity
6681 by a factor of four. Thanks to Mike Perry for measurements.
6683 o Major bugfixes (stream expiration):
6684 - Expire not-yet-successful application streams in all cases if
6685 they've been around longer than SocksTimeout. Right now there are
6686 some cases where the stream will live forever, demanding a new
6687 circuit every 15 seconds. Fixes bug 454; reported by lodger.
6689 o Minor features (controller):
6690 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
6691 is valid before any authentication has been received. It tells
6692 a controller what kind of authentication is expected, and what
6693 protocol is spoken. Implements proposal 119.
6695 o Minor bugfixes (performance):
6696 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
6697 greatly speeding up loading cached-routers from disk on startup.
6698 - Disable sentinel-based debugging for buffer code: we squashed all
6699 the bugs that this was supposed to detect a long time ago, and now
6700 its only effect is to change our buffer sizes from nice powers of
6701 two (which platform mallocs tend to like) to values slightly over
6702 powers of two (which make some platform mallocs sad).
6704 o Minor bugfixes (misc):
6705 - If exit bandwidth ever exceeds one third of total bandwidth, then
6706 use the correct formula to weight exit nodes when choosing paths.
6707 Based on patch from Mike Perry.
6708 - Choose perfectly fairly among routers when choosing by bandwidth and
6709 weighting by fraction of bandwidth provided by exits. Previously, we
6710 would choose with only approximate fairness, and correct ourselves
6711 if we ran off the end of the list.
6712 - If we require CookieAuthentication but we fail to write the
6713 cookie file, we would warn but not exit, and end up in a state
6714 where no controller could authenticate. Now we exit.
6715 - If we require CookieAuthentication, stop generating a new cookie
6716 every time we change any piece of our config.
6717 - Refuse to start with certain directory authority keys, and
6718 encourage people using them to stop.
6719 - Terminate multi-line control events properly. Original patch
6721 - Fix a minor memory leak when we fail to find enough suitable
6722 servers to choose a circuit.
6723 - Stop leaking part of the descriptor when we run into a particularly
6724 unparseable piece of it.
6727 Changes in version 0.1.2.16 - 2007-08-01
6728 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
6729 remote attacker in certain situations to rewrite the user's torrc
6730 configuration file. This can completely compromise anonymity of users
6731 in most configurations, including those running the Vidalia bundles,
6732 TorK, etc. Or worse.
6734 o Major security fixes:
6735 - Close immediately after missing authentication on control port;
6736 do not allow multiple authentication attempts.
6739 Changes in version 0.1.2.15 - 2007-07-17
6740 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
6741 problems, fixes compilation on BSD, and fixes a variety of other
6742 bugs. Everybody should upgrade.
6744 o Major bugfixes (compilation):
6745 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
6747 o Major bugfixes (crashes):
6748 - Try even harder not to dereference the first character after
6749 an mmap(). Reported by lodger.
6750 - Fix a crash bug in directory authorities when we re-number the
6751 routerlist while inserting a new router.
6752 - When the cached-routers file is an even multiple of the page size,
6753 don't run off the end and crash. (Fixes bug 455; based on idea
6755 - Fix eventdns.c behavior on Solaris: It is critical to include
6756 orconfig.h _before_ sys/types.h, so that we can get the expected
6757 definition of _FILE_OFFSET_BITS.
6759 o Major bugfixes (security):
6760 - Fix a possible buffer overrun when using BSD natd support. Bug
6762 - When sending destroy cells from a circuit's origin, don't include
6763 the reason for tearing down the circuit. The spec says we didn't,
6764 and now we actually don't. Reported by lodger.
6765 - Keep streamids from different exits on a circuit separate. This
6766 bug may have allowed other routers on a given circuit to inject
6767 cells into streams. Reported by lodger; fixes bug 446.
6768 - If there's a never-before-connected-to guard node in our list,
6769 never choose any guards past it. This way we don't expand our
6770 guard list unless we need to.
6772 o Minor bugfixes (guard nodes):
6773 - Weight guard selection by bandwidth, so that low-bandwidth nodes
6774 don't get overused as guards.
6776 o Minor bugfixes (directory):
6777 - Correctly count the number of authorities that recommend each
6778 version. Previously, we were under-counting by 1.
6779 - Fix a potential crash bug when we load many server descriptors at
6780 once and some of them make others of them obsolete. Fixes bug 458.
6782 o Minor bugfixes (hidden services):
6783 - Stop tearing down the whole circuit when the user asks for a
6784 connection to a port that the hidden service didn't configure.
6787 o Minor bugfixes (misc):
6788 - On Windows, we were preventing other processes from reading
6789 cached-routers while Tor was running. Reported by janbar.
6790 - Fix a possible (but very unlikely) bug in picking routers by
6791 bandwidth. Add a log message to confirm that it is in fact
6792 unlikely. Patch from lodger.
6793 - Backport a couple of memory leak fixes.
6794 - Backport miscellaneous cosmetic bugfixes.
6797 Changes in version 0.1.2.14 - 2007-05-25
6798 Tor 0.1.2.14 changes the addresses of two directory authorities (this
6799 change especially affects those who serve or use hidden services),
6800 and fixes several other crash- and security-related bugs.
6802 o Directory authority changes:
6803 - Two directory authorities (moria1 and moria2) just moved to new
6804 IP addresses. This change will particularly affect those who serve
6805 or use hidden services.
6807 o Major bugfixes (crashes):
6808 - If a directory server runs out of space in the connection table
6809 as it's processing a begin_dir request, it will free the exit stream
6810 but leave it attached to the circuit, leading to unpredictable
6811 behavior. (Reported by seeess, fixes bug 425.)
6812 - Fix a bug in dirserv_remove_invalid() that would cause authorities
6813 to corrupt memory under some really unlikely scenarios.
6814 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
6815 - Avoid segfaults when reading from mmaped descriptor file. (Reported
6818 o Major bugfixes (security):
6819 - When choosing an entry guard for a circuit, avoid using guards
6820 that are in the same family as the chosen exit -- not just guards
6821 that are exactly the chosen exit. (Reported by lodger.)
6823 o Major bugfixes (resource management):
6824 - If a directory authority is down, skip it when deciding where to get
6825 networkstatus objects or descriptors. Otherwise we keep asking
6826 every 10 seconds forever. Fixes bug 384.
6827 - Count it as a failure if we fetch a valid network-status but we
6828 don't want to keep it. Otherwise we'll keep fetching it and keep
6829 not wanting to keep it. Fixes part of bug 422.
6830 - If all of our dirservers have given us bad or no networkstatuses
6831 lately, then stop hammering them once per minute even when we
6832 think they're failed. Fixes another part of bug 422.
6835 - Actually set the purpose correctly for descriptors inserted with
6837 - When we have k non-v2 authorities in our DirServer config,
6838 we ignored the last k authorities in the list when updating our
6840 - Correctly back-off from requesting router descriptors that we are
6841 having a hard time downloading.
6842 - Read resolv.conf files correctly on platforms where read() returns
6843 partial results on small file reads.
6844 - Don't rebuild the entire router store every time we get 32K of
6845 routers: rebuild it when the journal gets very large, or when
6846 the gaps in the store get very large.
6849 - When routers publish SVN revisions in their router descriptors,
6850 authorities now include those versions correctly in networkstatus
6852 - Warn when using a version of libevent before 1.3b to run a server on
6853 OSX or BSD: these versions interact badly with userspace threads.
6856 Changes in version 0.1.2.13 - 2007-04-24
6857 This release features some major anonymity fixes, such as safer path
6858 selection; better client performance; faster bootstrapping, better
6859 address detection, and better DNS support for servers; write limiting as
6860 well as read limiting to make servers easier to run; and a huge pile of
6861 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
6863 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
6864 of the Freenode IRC network, remembering his patience and vision for
6865 free speech on the Internet.
6867 o Major features, client performance:
6868 - Weight directory requests by advertised bandwidth. Now we can
6869 let servers enable write limiting but still allow most clients to
6870 succeed at their directory requests. (We still ignore weights when
6871 choosing a directory authority; I hope this is a feature.)
6872 - Stop overloading exit nodes -- avoid choosing them for entry or
6873 middle hops when the total bandwidth available from non-exit nodes
6874 is much higher than the total bandwidth available from exit nodes.
6875 - Rather than waiting a fixed amount of time between retrying
6876 application connections, we wait only 10 seconds for the first,
6877 10 seconds for the second, and 15 seconds for each retry after
6878 that. Hopefully this will improve the expected user experience.
6879 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
6880 to open a stream fails; now we do in more cases. This should
6881 make clients able to find a good exit faster in some cases, since
6882 unhandleable requests will now get an error rather than timing out.
6884 o Major features, client functionality:
6885 - Implement BEGIN_DIR cells, so we can connect to a directory
6886 server via TLS to do encrypted directory requests rather than
6887 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
6888 config options if you like. For now, this feature only works if
6889 you already have a descriptor for the destination dirserver.
6890 - Add support for transparent application connections: this basically
6891 bundles the functionality of trans-proxy-tor into the Tor
6892 mainline. Now hosts with compliant pf/netfilter implementations
6893 can redirect TCP connections straight to Tor without diverting
6894 through SOCKS. (Based on patch from tup.)
6895 - Add support for using natd; this allows FreeBSDs earlier than
6896 5.1.2 to have ipfw send connections through Tor without using
6897 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
6899 o Major features, servers:
6900 - Setting up a dyndns name for your server is now optional: servers
6901 with no hostname or IP address will learn their IP address by
6902 asking the directory authorities. This code only kicks in when you
6903 would normally have exited with a "no address" error. Nothing's
6904 authenticated, so use with care.
6905 - Directory servers now spool server descriptors, v1 directories,
6906 and v2 networkstatus objects to buffers as needed rather than en
6907 masse. They also mmap the cached-routers files. These steps save
6909 - Stop requiring clients to have well-formed certificates, and stop
6910 checking nicknames in certificates. (Clients have certificates so
6911 that they can look like Tor servers, but in the future we might want
6912 to allow them to look like regular TLS clients instead. Nicknames
6913 in certificates serve no purpose other than making our protocol
6914 easier to recognize on the wire.) Implements proposal 106.
6916 o Improvements on DNS support:
6917 - Add "eventdns" asynchronous dns library originally based on code
6918 from Adam Langley. Now we can discard the old rickety dnsworker
6919 concept, and support a wider variety of DNS functions. Allows
6920 multithreaded builds on NetBSD and OpenBSD again.
6921 - Add server-side support for "reverse" DNS lookups (using PTR
6922 records so clients can determine the canonical hostname for a given
6923 IPv4 address). Only supported by servers using eventdns; servers
6924 now announce in their descriptors if they don't support eventdns.
6925 - Workaround for name servers (like Earthlink's) that hijack failing
6926 DNS requests and replace the no-such-server answer with a "helpful"
6927 redirect to an advertising-driven search portal. Also work around
6928 DNS hijackers who "helpfully" decline to hijack known-invalid
6929 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
6930 lets you turn it off.
6931 - Servers now check for the case when common DNS requests are going to
6932 wildcarded addresses (i.e. all getting the same answer), and change
6933 their exit policy to reject *:* if it's happening.
6934 - When asked to resolve a hostname, don't use non-exit servers unless
6935 requested to do so. This allows servers with broken DNS to be
6936 useful to the network.
6937 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
6938 useless IPv6 DNS resolves.
6939 - Specify and implement client-side SOCKS5 interface for reverse DNS
6940 lookups (see doc/socks-extensions.txt). Also cache them.
6941 - When we change nameservers or IP addresses, reset and re-launch
6942 our tests for DNS hijacking.
6944 o Improvements on reachability testing:
6945 - Servers send out a burst of long-range padding cells once they've
6946 established that they're reachable. Spread them over 4 circuits,
6947 so hopefully a few will be fast. This exercises bandwidth and
6948 bootstraps them into the directory more quickly.
6949 - When we find our DirPort to be reachable, publish a new descriptor
6950 so we'll tell the world (reported by pnx).
6951 - Directory authorities now only decide that routers are reachable
6952 if their identity keys are as expected.
6953 - Do DirPort reachability tests less often, since a single test
6954 chews through many circuits before giving up.
6955 - Avoid some false positives during reachability testing: don't try
6956 to test via a server that's on the same /24 network as us.
6957 - Start publishing one minute or so after we find our ORPort
6958 to be reachable. This will help reduce the number of descriptors
6959 we have for ourselves floating around, since it's quite likely
6960 other things (e.g. DirPort) will change during that minute too.
6961 - Routers no longer try to rebuild long-term connections to directory
6962 authorities, and directory authorities no longer try to rebuild
6963 long-term connections to all servers. We still don't hang up
6964 connections in these two cases though -- we need to look at it
6965 more carefully to avoid flapping, and we likely need to wait til
6966 0.1.1.x is obsolete.
6968 o Improvements on rate limiting:
6969 - Enable write limiting as well as read limiting. Now we sacrifice
6970 capacity if we're pushing out lots of directory traffic, rather
6971 than overrunning the user's intended bandwidth limits.
6972 - Include TLS overhead when counting bandwidth usage; previously, we
6973 would count only the bytes sent over TLS, but not the bytes used
6975 - Servers decline directory requests much more aggressively when
6976 they're low on bandwidth. Otherwise they end up queueing more and
6977 more directory responses, which can't be good for latency.
6978 - But never refuse directory requests from local addresses.
6979 - Be willing to read or write on local connections (e.g. controller
6980 connections) even when the global rate limiting buckets are empty.
6981 - Flush local controller connection buffers periodically as we're
6982 writing to them, so we avoid queueing 4+ megabytes of data before
6984 - Revise and clean up the torrc.sample that we ship with; add
6985 a section for BandwidthRate and BandwidthBurst.
6987 o Major features, NT services:
6988 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
6989 command-line flag so that admins can override the default by saying
6990 "tor --service install --user "SomeUser"". This will not affect
6991 existing installed services. Also, warn the user that the service
6992 will look for its configuration file in the service user's
6993 %appdata% directory. (We can't do the "hardwire the user's appdata
6994 directory" trick any more, since we may not have read access to that
6996 - Support running the Tor service with a torrc not in the same
6997 directory as tor.exe and default to using the torrc located in
6998 the %appdata%\Tor\ of the user who installed the service. Patch
7000 - Add an --ignore-missing-torrc command-line option so that we can
7001 get the "use sensible defaults if the configuration file doesn't
7002 exist" behavior even when specifying a torrc location on the
7004 - When stopping an NT service, wait up to 10 sec for it to actually
7005 stop. (Patch from Matt Edman; resolves bug 295.)
7007 o Directory authority improvements:
7008 - Stop letting hibernating or obsolete servers affect uptime and
7010 - Stop listing hibernating servers in the v1 directory.
7011 - Authorities no longer recommend exits as guards if this would shift
7012 too much load to the exit nodes.
7013 - Authorities now specify server versions in networkstatus. This adds
7014 about 2% to the size of compressed networkstatus docs, and allows
7015 clients to tell which servers support BEGIN_DIR and which don't.
7016 The implementation is forward-compatible with a proposed future
7017 protocol version scheme not tied to Tor versions.
7018 - DirServer configuration lines now have an orport= option so
7019 clients can open encrypted tunnels to the authorities without
7020 having downloaded their descriptors yet. Enabled for moria1,
7021 moria2, tor26, and lefkada now in the default configuration.
7022 - Add a BadDirectory flag to network status docs so that authorities
7023 can (eventually) tell clients about caches they believe to be
7024 broken. Not used yet.
7025 - Allow authorities to list nodes as bad exits in their
7026 approved-routers file by fingerprint or by address. If most
7027 authorities set a BadExit flag for a server, clients don't think
7028 of it as a general-purpose exit. Clients only consider authorities
7029 that advertise themselves as listing bad exits.
7030 - Patch from Steve Hildrey: Generate network status correctly on
7031 non-versioning dirservers.
7032 - Have directory authorities allow larger amounts of drift in uptime
7033 without replacing the server descriptor: previously, a server that
7034 restarted every 30 minutes could have 48 "interesting" descriptors
7036 - Reserve the nickname "Unnamed" for routers that can't pick
7037 a hostname: any router can call itself Unnamed; directory
7038 authorities will never allocate Unnamed to any particular router;
7039 clients won't believe that any router is the canonical Unnamed.
7041 o Directory mirrors and clients:
7042 - Discard any v1 directory info that's over 1 month old (for
7043 directories) or over 1 week old (for running-routers lists).
7044 - Clients track responses with status 503 from dirservers. After a
7045 dirserver has given us a 503, we try not to use it until an hour has
7046 gone by, or until we have no dirservers that haven't given us a 503.
7047 - When we get a 503 from a directory, and we're not a server, we no
7048 longer count the failure against the total number of failures
7049 allowed for the object we're trying to download.
7050 - Prepare for servers to publish descriptors less often: never
7051 discard a descriptor simply for being too old until either it is
7052 recommended by no authorities, or until we get a better one for
7053 the same router. Make caches consider retaining old recommended
7054 routers for even longer.
7055 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
7056 headers for content, so that we can work better in the presence of
7057 caching HTTP proxies.
7058 - Stop fetching descriptors if you're not a dir mirror and you
7059 haven't tried to establish any circuits lately. (This currently
7060 causes some dangerous behavior, because when you start up again
7061 you'll use your ancient server descriptors.)
7063 o Major fixes, crashes:
7064 - Stop crashing when the controller asks us to resetconf more than
7065 one config option at once. (Vidalia 0.0.11 does this.)
7066 - Fix a longstanding obscure crash bug that could occur when we run
7067 out of DNS worker processes, if we're not using eventdns. (Resolves
7069 - Fix an assert that could trigger if a controller quickly set then
7070 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
7071 - Avoid crash when telling controller about stream-status and a
7073 - Avoid sending junk to controllers or segfaulting when a controller
7074 uses EVENT_NEW_DESC with verbose nicknames.
7075 - Stop triggering asserts if the controller tries to extend hidden
7076 service circuits (reported by mwenge).
7077 - If we start a server with ClientOnly 1, then set ClientOnly to 0
7078 and hup, stop triggering an assert based on an empty onion_key.
7079 - Mask out all signals in sub-threads; only the libevent signal
7080 handler should be processing them. This should prevent some crashes
7081 on some machines using pthreads. (Patch from coderman.)
7082 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
7084 o Major fixes, anonymity/security:
7085 - Automatically avoid picking more than one node from the same
7086 /16 network when constructing a circuit. Add an
7087 "EnforceDistinctSubnets" option to let people disable it if they
7088 want to operate private test networks on a single subnet.
7089 - When generating bandwidth history, round down to the nearest
7090 1k. When storing accounting data, round up to the nearest 1k.
7091 - When we're running as a server, remember when we last rotated onion
7092 keys, so that we will rotate keys once they're a week old even if
7093 we never stay up for a week ourselves.
7094 - If a client asked for a server by name, and there's a named server
7095 in our network-status but we don't have its descriptor yet, we
7096 could return an unnamed server instead.
7097 - Reject (most) attempts to use Tor circuits with length one. (If
7098 many people start using Tor as a one-hop proxy, exit nodes become
7099 a more attractive target for compromise.)
7100 - Just because your DirPort is open doesn't mean people should be
7101 able to remotely teach you about hidden service descriptors. Now
7102 only accept rendezvous posts if you've got HSAuthoritativeDir set.
7103 - Fix a potential race condition in the rpm installer. Found by
7105 - Do not log IPs with TLS failures for incoming TLS
7106 connections. (Fixes bug 382.)
7108 o Major fixes, other:
7109 - If our system clock jumps back in time, don't publish a negative
7110 uptime in the descriptor.
7111 - When we start during an accounting interval before it's time to wake
7112 up, remember to wake up at the correct time. (May fix bug 342.)
7113 - Previously, we would cache up to 16 old networkstatus documents
7114 indefinitely, if they came from nontrusted authorities. Now we
7115 discard them if they are more than 10 days old.
7116 - When we have a state file we cannot parse, tell the user and
7117 move it aside. Now we avoid situations where the user starts
7118 Tor in 1904, Tor writes a state file with that timestamp in it,
7119 the user fixes her clock, and Tor refuses to start.
7120 - Publish a new descriptor after we hup/reload. This is important
7121 if our config has changed such that we'll want to start advertising
7122 our DirPort now, etc.
7123 - If we are using an exit enclave and we can't connect, e.g. because
7124 its webserver is misconfigured to not listen on localhost, then
7125 back off and try connecting from somewhere else before we fail.
7127 o New config options or behaviors:
7128 - When EntryNodes are configured, rebuild the guard list to contain,
7129 in order: the EntryNodes that were guards before; the rest of the
7130 EntryNodes; the nodes that were guards before.
7131 - Do not warn when individual nodes in the configuration's EntryNodes,
7132 ExitNodes, etc are down: warn only when all possible nodes
7133 are down. (Fixes bug 348.)
7134 - Put a lower-bound on MaxAdvertisedBandwidth.
7135 - Start using the state file to store bandwidth accounting data:
7136 the bw_accounting file is now obsolete. We'll keep generating it
7137 for a while for people who are still using 0.1.2.4-alpha.
7138 - Try to batch changes to the state file so that we do as few
7139 disk writes as possible while still storing important things in
7141 - The state file and the bw_accounting file get saved less often when
7142 the AvoidDiskWrites config option is set.
7143 - Make PIDFile work on Windows.
7144 - Add internal descriptions for a bunch of configuration options:
7145 accessible via controller interface and in comments in saved
7147 - Reject *:563 (NNTPS) in the default exit policy. We already reject
7148 NNTP by default, so this seems like a sensible addition.
7149 - Clients now reject hostnames with invalid characters. This should
7150 avoid some inadvertent info leaks. Add an option
7151 AllowNonRFC953Hostnames to disable this behavior, in case somebody
7152 is running a private network with hosts called @, !, and #.
7153 - Check for addresses with invalid characters at the exit as well,
7154 and warn less verbosely when they fail. You can override this by
7155 setting ServerDNSAllowNonRFC953Addresses to 1.
7156 - Remove some options that have been deprecated since at least
7157 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
7158 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
7159 to set log options. Mark PathlenCoinWeight as obsolete.
7160 - Stop accepting certain malformed ports in configured exit policies.
7161 - When the user uses bad syntax in the Log config line, stop
7162 suggesting other bad syntax as a replacement.
7163 - Add new config option "ResolvConf" to let the server operator
7164 choose an alternate resolve.conf file when using eventdns.
7165 - If one of our entry guards is on the ExcludeNodes list, or the
7166 directory authorities don't think it's a good guard, treat it as
7167 if it were unlisted: stop using it as a guard, and throw it off
7168 the guards list if it stays that way for a long time.
7169 - Allow directory authorities to be marked separately as authorities
7170 for the v1 directory protocol, the v2 directory protocol, and
7171 as hidden service directories, to make it easier to retire old
7172 authorities. V1 authorities should set "HSAuthoritativeDir 1"
7173 to continue being hidden service authorities too.
7174 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
7175 - Make TrackExitHosts case-insensitive, and fix the behavior of
7176 ".suffix" TrackExitHosts items to avoid matching in the middle of
7178 - New DirPort behavior: if you have your dirport set, you download
7179 descriptors aggressively like a directory mirror, whether or not
7183 - Create a new file ReleaseNotes which was the old ChangeLog. The
7184 new ChangeLog file now includes the notes for all development
7186 - Add a new address-spec.txt document to describe our special-case
7187 addresses: .exit, .onion, and .noconnnect.
7188 - Fork the v1 directory protocol into its own spec document,
7189 and mark dir-spec.txt as the currently correct (v2) spec.
7191 o Packaging, porting, and contrib
7192 - "tor --verify-config" now exits with -1(255) or 0 depending on
7193 whether the config options are bad or good.
7194 - The Debian package now uses --verify-config when (re)starting,
7195 to distinguish configuration errors from other errors.
7196 - Adapt a patch from goodell to let the contrib/exitlist script
7197 take arguments rather than require direct editing.
7198 - Prevent the contrib/exitlist script from printing the same
7199 result more than once.
7200 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
7201 - In the hidden service example in torrc.sample, stop recommending
7202 esoteric and discouraged hidden service options.
7203 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
7204 values before failing, and always enables eventdns.
7205 - Try to detect Windows correctly when cross-compiling.
7206 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
7207 Try to fix this in configure.in by checking for most functions
7208 before we check for libevent.
7209 - Update RPMs to require libevent 1.2.
7210 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
7211 or later. Log when we are doing this, so we can diagnose it when
7212 it fails. (Also, recommend libevent 1.1b for kqueue and
7213 win32 methods; deprecate libevent 1.0b harder; make libevent
7214 recommendation system saner.)
7215 - Build with recent (1.3+) libevents on platforms that do not
7216 define the nonstandard types "u_int8_t" and friends.
7217 - Remove architecture from OS X builds. The official builds are
7218 now universal binaries.
7219 - Run correctly on OS X platforms with case-sensitive filesystems.
7220 - Correctly set maximum connection limit on Cygwin. (This time
7222 - Start compiling on MinGW on Windows (patches from Mike Chiussi
7224 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
7225 - Finally fix the openssl warnings from newer gccs that believe that
7226 ignoring a return value is okay, but casting a return value and
7227 then ignoring it is a sign of madness.
7228 - On architectures where sizeof(int)>4, still clamp declarable
7229 bandwidth to INT32_MAX.
7231 o Minor features, controller:
7232 - Warn the user when an application uses the obsolete binary v0
7233 control protocol. We're planning to remove support for it during
7234 the next development series, so it's good to give people some
7236 - Add STREAM_BW events to report per-entry-stream bandwidth
7237 use. (Patch from Robert Hogan.)
7238 - Rate-limit SIGNEWNYM signals in response to controllers that
7239 impolitely generate them for every single stream. (Patch from
7240 mwenge; closes bug 394.)
7241 - Add a REMAP status to stream events to note that a stream's
7242 address has changed because of a cached address or a MapAddress
7244 - Make REMAP stream events have a SOURCE (cache or exit), and
7245 make them generated in every case where we get a successful
7246 connected or resolved cell.
7247 - Track reasons for OR connection failure; make these reasons
7248 available via the controller interface. (Patch from Mike Perry.)
7249 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
7250 can learn when clients are sending malformed hostnames to Tor.
7251 - Specify and implement some of the controller status events.
7252 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
7253 - Reimplement GETINFO so that info/names stays in sync with the
7255 - Implement "GETINFO fingerprint".
7256 - Implement "SETEVENTS GUARD" so controllers can get updates on
7257 entry guard status as it changes.
7258 - Make all connections to addresses of the form ".noconnect"
7259 immediately get closed. This lets application/controller combos
7260 successfully test whether they're talking to the same Tor by
7261 watching for STREAM events.
7262 - Add a REASON field to CIRC events; for backward compatibility, this
7263 field is sent only to controllers that have enabled the extended
7264 event format. Also, add additional reason codes to explain why
7265 a given circuit has been destroyed or truncated. (Patches from
7267 - Add a REMOTE_REASON field to extended CIRC events to tell the
7268 controller why a remote OR told us to close a circuit.
7269 - Stream events also now have REASON and REMOTE_REASON fields,
7270 working much like those for circuit events.
7271 - There's now a GETINFO ns/... field so that controllers can ask Tor
7272 about the current status of a router.
7273 - A new event type "NS" to inform a controller when our opinion of
7274 a router's status has changed.
7275 - Add a GETINFO events/names and GETINFO features/names so controllers
7276 can tell which events and features are supported.
7277 - A new CLEARDNSCACHE signal to allow controllers to clear the
7278 client-side DNS cache without expiring circuits.
7279 - Fix CIRC controller events so that controllers can learn the
7280 identity digests of non-Named servers used in circuit paths.
7281 - Let controllers ask for more useful identifiers for servers. Instead
7282 of learning identity digests for un-Named servers and nicknames
7283 for Named servers, the new identifiers include digest, nickname,
7284 and indication of Named status. Off by default; see control-spec.txt
7285 for more information.
7286 - Add a "getinfo address" controller command so it can display Tor's
7287 best guess to the user.
7288 - New controller event to alert the controller when our server
7289 descriptor has changed.
7290 - Give more meaningful errors on controller authentication failure.
7291 - Export the default exit policy via the control port, so controllers
7292 don't need to guess what it is / will be later.
7294 o Minor bugfixes, controller:
7295 - When creating a circuit via the controller, send a 'launched'
7296 event when we're done, so we follow the spec better.
7297 - Correct the control spec to match how the code actually responds
7298 to 'getinfo addr-mappings/*'. Reported by daejees.
7299 - The control spec described a GUARDS event, but the code
7300 implemented a GUARD event. Standardize on GUARD, but let people
7301 ask for GUARDS too. Reported by daejees.
7302 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
7303 clear the corresponding on_circuit variable, and remember later
7304 that we don't need to send a redundant CLOSED event. (Resolves part
7306 - Report events where a resolve succeeded or where we got a socks
7307 protocol error correctly, rather than calling both of them
7309 - Change reported stream target addresses to IP consistently when
7310 we finally get the IP from an exit node.
7311 - Send log messages to the controller even if they happen to be very
7313 - Flush ERR-level controller status events just like we currently
7314 flush ERR-level log events, so that a Tor shutdown doesn't prevent
7315 the controller from learning about current events.
7316 - Report the circuit number correctly in STREAM CLOSED events. Bug
7317 reported by Mike Perry.
7318 - Do not report bizarre values for results of accounting GETINFOs
7319 when the last second's write or read exceeds the allotted bandwidth.
7320 - Report "unrecognized key" rather than an empty string when the
7321 controller tries to fetch a networkstatus that doesn't exist.
7322 - When the controller does a "GETINFO network-status", tell it
7323 about even those routers whose descriptors are very old, and use
7324 long nicknames where appropriate.
7325 - Fix handling of verbose nicknames with ORCONN controller events:
7326 make them show up exactly when requested, rather than exactly when
7328 - Controller signals now work on non-Unix platforms that don't define
7329 SIGUSR1 and SIGUSR2 the way we expect.
7330 - Respond to SIGNAL command before we execute the signal, in case
7331 the signal shuts us down. Suggested by Karsten Loesing.
7332 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
7334 o Minor features, code performance:
7335 - Major performance improvement on inserting descriptors: change
7336 algorithm from O(n^2) to O(n).
7337 - Do not rotate onion key immediately after setting it for the first
7339 - Call router_have_min_dir_info half as often. (This is showing up in
7340 some profiles, but not others.)
7341 - When using GCC, make log_debug never get called at all, and its
7342 arguments never get evaluated, when no debug logs are configured.
7343 (This is showing up in some profiles, but not others.)
7344 - Statistics dumped by -USR2 now include a breakdown of public key
7345 operations, for profiling.
7346 - Make the common memory allocation path faster on machines where
7347 malloc(0) returns a pointer.
7348 - Split circuit_t into origin_circuit_t and or_circuit_t, and
7349 split connection_t into edge, or, dir, control, and base structs.
7350 These will save quite a bit of memory on busy servers, and they'll
7351 also help us track down bugs in the code and bugs in the spec.
7352 - Use OpenSSL's AES implementation on platforms where it's faster.
7353 This could save us as much as 10% CPU usage.
7355 o Minor features, descriptors and descriptor handling:
7356 - Avoid duplicate entries on MyFamily line in server descriptor.
7357 - When Tor receives a router descriptor that it asked for, but
7358 no longer wants (because it has received fresh networkstatuses
7359 in the meantime), do not warn the user. Cache the descriptor if
7360 we're a cache; drop it if we aren't.
7361 - Servers no longer ever list themselves in their "family" line,
7362 even if configured to do so. This makes it easier to configure
7363 family lists conveniently.
7365 o Minor fixes, confusing/misleading log messages:
7366 - Display correct results when reporting which versions are
7367 recommended, and how recommended they are. (Resolves bug 383.)
7368 - Inform the server operator when we decide not to advertise a
7369 DirPort due to AccountingMax enabled or a low BandwidthRate.
7370 - Only include function names in log messages for info/debug messages.
7371 For notice/warn/err, the content of the message should be clear on
7372 its own, and printing the function name only confuses users.
7373 - Remove even more protocol-related warnings from Tor server logs,
7374 such as bad TLS handshakes and malformed begin cells.
7375 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
7376 when the IP address is mapped through MapAddress to a hostname.
7377 - Fix misleading log messages: an entry guard that is "unlisted",
7378 as well as not known to be "down" (because we've never heard
7379 of it), is not therefore "up".
7381 o Minor fixes, old/obsolete behavior:
7382 - Start assuming we can use a create_fast cell if we don't know
7383 what version a router is running.
7384 - We no longer look for identity and onion keys in "identity.key" and
7385 "onion.key" -- these were replaced by secret_id_key and
7386 secret_onion_key in 0.0.8pre1.
7387 - We no longer require unrecognized directory entries to be
7389 - Drop compatibility with obsolete Tors that permit create cells
7390 to have the wrong circ_id_type.
7391 - Remove code to special-case "-cvs" ending, since it has not
7392 actually mattered since 0.0.9.
7393 - Don't re-write the fingerprint file every restart, unless it has
7396 o Minor fixes, misc client-side behavior:
7397 - Always remove expired routers and networkstatus docs before checking
7398 whether we have enough information to build circuits. (Fixes
7400 - When computing clock skew from directory HTTP headers, consider what
7401 time it was when we finished asking for the directory, not what
7403 - Make our socks5 handling more robust to broken socks clients:
7404 throw out everything waiting on the buffer in between socks
7405 handshake phases, since they can't possibly (so the theory
7406 goes) have predicted what we plan to respond to them.
7407 - Expire socks connections if they spend too long waiting for the
7408 handshake to finish. Previously we would let them sit around for
7409 days, if the connecting application didn't close them either.
7410 - And if the socks handshake hasn't started, don't send a
7411 "DNS resolve socks failed" handshake reply; just close it.
7412 - If the user asks to use invalid exit nodes, be willing to use
7414 - Track unreachable entry guards correctly: don't conflate
7415 'unreachable by us right now' with 'listed as down by the directory
7416 authorities'. With the old code, if a guard was unreachable by us
7417 but listed as running, it would clog our guard list forever.
7418 - Behave correctly in case we ever have a network with more than
7419 2GB/s total advertised capacity.
7420 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
7421 - Fix a memory leak when we ask for "all" networkstatuses and we
7422 get one we don't recognize.
7425 Changes in version 0.1.1.26 - 2006-12-14
7426 o Security bugfixes:
7427 - Stop sending the HttpProxyAuthenticator string to directory
7428 servers when directory connections are tunnelled through Tor.
7429 - Clients no longer store bandwidth history in the state file.
7430 - Do not log introduction points for hidden services if SafeLogging
7434 - Fix an assert failure when a directory authority sets
7435 AuthDirRejectUnlisted and then receives a descriptor from an
7436 unlisted router (reported by seeess).
7439 Changes in version 0.1.1.25 - 2006-11-04
7441 - When a client asks us to resolve (rather than connect to)
7442 an address, and we have a cached answer, give them the cached
7443 answer. Previously, we would give them no answer at all.
7444 - We were building exactly the wrong circuits when we predict
7445 hidden service requirements, meaning Tor would have to build all
7446 its circuits on demand.
7447 - If none of our live entry guards have a high uptime, but we
7448 require a guard with a high uptime, try adding a new guard before
7449 we give up on the requirement. This patch should make long-lived
7450 connections more stable on average.
7451 - When testing reachability of our DirPort, don't launch new
7452 tests when there's already one in progress -- unreachable
7453 servers were stacking up dozens of testing streams.
7455 o Security bugfixes:
7456 - When the user sends a NEWNYM signal, clear the client-side DNS
7457 cache too. Otherwise we continue to act on previous information.
7460 - Avoid a memory corruption bug when creating a hash table for
7462 - Avoid possibility of controller-triggered crash when misusing
7463 certain commands from a v0 controller on platforms that do not
7464 handle printf("%s",NULL) gracefully.
7465 - Avoid infinite loop on unexpected controller input.
7466 - Don't log spurious warnings when we see a circuit close reason we
7467 don't recognize; it's probably just from a newer version of Tor.
7468 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7469 Tor/Privoxy we also uninstall Vidalia.
7472 Changes in version 0.1.1.24 - 2006-09-29
7474 - Allow really slow clients to not hang up five minutes into their
7475 directory downloads (suggested by Adam J. Richter).
7476 - Fix major performance regression from 0.1.0.x: instead of checking
7477 whether we have enough directory information every time we want to
7478 do something, only check when the directory information has changed.
7479 This should improve client CPU usage by 25-50%.
7480 - Don't crash if, after a server has been running for a while,
7481 it can't resolve its hostname.
7482 - When a client asks us to resolve (not connect to) an address,
7483 and we have a cached answer, give them the cached answer.
7484 Previously, we would give them no answer at all.
7487 - Allow Tor to start when RunAsDaemon is set but no logs are set.
7488 - Don't crash when the controller receives a third argument to an
7489 "extendcircuit" request.
7490 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
7491 response; fix error code when "getinfo dir/status/" fails.
7492 - Fix configure.in to not produce broken configure files with
7493 more recent versions of autoconf. Thanks to Clint for his auto*
7495 - Fix security bug on NetBSD that could allow someone to force
7496 uninitialized RAM to be sent to a server's DNS resolver. This
7497 only affects NetBSD and other platforms that do not bounds-check
7499 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
7500 methods: these are known to be buggy.
7501 - If we're a directory mirror and we ask for "all" network status
7502 documents, we would discard status documents from authorities
7506 Changes in version 0.1.1.23 - 2006-07-30
7508 - Fast Tor servers, especially exit nodes, were triggering asserts
7509 due to a bug in handling the list of pending DNS resolves. Some
7510 bugs still remain here; we're hunting them.
7511 - Entry guards could crash clients by sending unexpected input.
7512 - More fixes on reachability testing: if you find yourself reachable,
7513 then don't ever make any client requests (so you stop predicting
7514 circuits), then hup or have your clock jump, then later your IP
7515 changes, you won't think circuits are working, so you won't try to
7516 test reachability, so you won't publish.
7519 - Avoid a crash if the controller does a resetconf firewallports
7520 and then a setconf fascistfirewall=1.
7521 - Avoid an integer underflow when the dir authority decides whether
7522 a router is stable: we might wrongly label it stable, and compute
7523 a slightly wrong median stability, when a descriptor is published
7525 - Fix a place where we might trigger an assert if we can't build our
7526 own server descriptor yet.
7529 Changes in version 0.1.1.22 - 2006-07-05
7531 - Fix a big bug that was causing servers to not find themselves
7532 reachable if they changed IP addresses. Since only 0.1.1.22+
7533 servers can do reachability testing correctly, now we automatically
7534 make sure to test via one of these.
7535 - Fix to allow clients and mirrors to learn directory info from
7536 descriptor downloads that get cut off partway through.
7537 - Directory authorities had a bug in deciding if a newly published
7538 descriptor was novel enough to make everybody want a copy -- a few
7539 servers seem to be publishing new descriptors many times a minute.
7541 - Fix a rare bug that was causing some servers to complain about
7542 "closing wedged cpuworkers" and skip some circuit create requests.
7543 - Make the Exit flag in directory status documents actually work.
7546 Changes in version 0.1.1.21 - 2006-06-10
7547 o Crash and assert fixes from 0.1.1.20:
7548 - Fix a rare crash on Tor servers that have enabled hibernation.
7549 - Fix a seg fault on startup for Tor networks that use only one
7550 directory authority.
7551 - Fix an assert from a race condition that occurs on Tor servers
7552 while exiting, where various threads are trying to log that they're
7553 exiting, and delete the logs, at the same time.
7554 - Make our unit tests pass again on certain obscure platforms.
7557 - Add support for building SUSE RPM packages.
7558 - Speed up initial bootstrapping for clients: if we are making our
7559 first ever connection to any entry guard, then don't mark it down
7561 - When only one Tor server in the network is labelled as a guard,
7562 and we've already picked him, we would cycle endlessly picking him
7563 again, being unhappy about it, etc. Now we specifically exclude
7564 current guards when picking a new guard.
7565 - Servers send create cells more reliably after the TLS connection
7566 is established: we were sometimes forgetting to send half of them
7567 when we had more than one pending.
7568 - If we get a create cell that asks us to extend somewhere, but the
7569 Tor server there doesn't match the expected digest, we now send
7570 a destroy cell back, rather than silently doing nothing.
7571 - Make options->RedirectExit work again.
7572 - Make cookie authentication for the controller work again.
7573 - Stop being picky about unusual characters in the arguments to
7574 mapaddress. It's none of our business.
7575 - Add a new config option "TestVia" that lets you specify preferred
7576 middle hops to use for test circuits. Perhaps this will let me
7577 debug the reachability problems better.
7579 o Log / documentation fixes:
7580 - If we're a server and some peer has a broken TLS certificate, don't
7581 log about it unless ProtocolWarnings is set, i.e., we want to hear
7582 about protocol violations by others.
7583 - Fix spelling of VirtualAddrNetwork in man page.
7584 - Add a better explanation at the top of the autogenerated torrc file
7585 about what happened to our old torrc.
7588 Changes in version 0.1.1.20 - 2006-05-23
7589 o Crash and assert fixes from 0.1.0.17:
7590 - Fix assert bug in close_logs() on exit: when we close and delete
7591 logs, remove them all from the global "logfiles" list.
7592 - Fix an assert error when we're out of space in the connection_list
7593 and we try to post a hidden service descriptor (reported by Peter
7595 - Fix a rare assert error when we've tried all intro points for
7596 a hidden service and we try fetching the service descriptor again:
7597 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
7598 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
7599 out and refuse the setconf if it would fail.
7600 - If you specify a relative torrc path and you set RunAsDaemon in
7601 your torrc, then it chdir()'s to the new directory. If you then
7602 HUP, it tries to load the new torrc location, fails, and exits.
7603 The fix: no longer allow a relative path to torrc when using -f.
7604 - Check for integer overflows in more places, when adding elements
7605 to smartlists. This could possibly prevent a buffer overflow
7606 on malicious huge inputs.
7608 o Security fixes, major:
7609 - When we're printing strings from the network, don't try to print
7610 non-printable characters. Now we're safer against shell escape
7611 sequence exploits, and also against attacks to fool users into
7612 misreading their logs.
7613 - Implement entry guards: automatically choose a handful of entry
7614 nodes and stick with them for all circuits. Only pick new guards
7615 when the ones you have are unsuitable, and if the old guards
7616 become suitable again, switch back. This will increase security
7617 dramatically against certain end-point attacks. The EntryNodes
7618 config option now provides some hints about which entry guards you
7619 want to use most; and StrictEntryNodes means to only use those.
7620 Fixes CVE-2006-0414.
7621 - Implement exit enclaves: if we know an IP address for the
7622 destination, and there's a running Tor server at that address
7623 which allows exit to the destination, then extend the circuit to
7624 that exit first. This provides end-to-end encryption and end-to-end
7625 authentication. Also, if the user wants a .exit address or enclave,
7626 use 4 hops rather than 3, and cannibalize a general circ for it
7628 - Obey our firewall options more faithfully:
7629 . If we can't get to a dirserver directly, try going via Tor.
7630 . Don't ever try to connect (as a client) to a place our
7631 firewall options forbid.
7632 . If we specify a proxy and also firewall options, obey the
7633 firewall options even when we're using the proxy: some proxies
7634 can only proxy to certain destinations.
7635 - Make clients regenerate their keys when their IP address changes.
7636 - For the OS X package's modified privoxy config file, comment
7637 out the "logfile" line so we don't log everything passed
7639 - Our TLS handshakes were generating a single public/private
7640 keypair for the TLS context, rather than making a new one for
7641 each new connection. Oops. (But we were still rotating them
7642 periodically, so it's not so bad.)
7643 - When we were cannibalizing a circuit with a particular exit
7644 node in mind, we weren't checking to see if that exit node was
7645 already present earlier in the circuit. Now we are.
7646 - Require server descriptors to list IPv4 addresses -- hostnames
7647 are no longer allowed. This also fixes potential vulnerabilities
7648 to servers providing hostnames as their address and then
7649 preferentially resolving them so they can partition users.
7650 - Our logic to decide if the OR we connected to was the right guy
7651 was brittle and maybe open to a mitm for invalid routers.
7653 o Security fixes, minor:
7654 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
7655 Ian Goldberg can prove things about our handshake protocol more
7657 - Make directory authorities generate a separate "guard" flag to
7658 mean "would make a good entry guard". Clients now honor the
7659 is_guard flag rather than looking at is_fast or is_stable.
7660 - Try to list MyFamily elements by key, not by nickname, and warn
7661 if we've not heard of a server.
7662 - Start using RAND_bytes rather than RAND_pseudo_bytes from
7663 OpenSSL. Also, reseed our entropy every hour, not just at
7664 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
7665 - Refuse server descriptors where the fingerprint line doesn't match
7666 the included identity key. Tor doesn't care, but other apps (and
7667 humans) might actually be trusting the fingerprint line.
7668 - We used to kill the circuit when we receive a relay command we
7669 don't recognize. Now we just drop that cell.
7670 - Fix a bug found by Lasse Overlier: when we were making internal
7671 circuits (intended to be cannibalized later for rendezvous and
7672 introduction circuits), we were picking them so that they had
7673 useful exit nodes. There was no need for this, and it actually
7674 aids some statistical attacks.
7675 - Start treating internal circuits and exit circuits separately.
7676 It's important to keep them separate because internal circuits
7677 have their last hops picked like middle hops, rather than like
7678 exit hops. So exiting on them will break the user's expectations.
7679 - Fix a possible way to DoS dirservers.
7680 - When the client asked for a rendezvous port that the hidden
7681 service didn't want to provide, we were sending an IP address
7682 back along with the end cell. Fortunately, it was zero. But stop
7685 o Packaging improvements:
7686 - Implement --with-libevent-dir option to ./configure. Improve
7687 search techniques to find libevent, and use those for openssl too.
7688 - Fix a couple of bugs in OpenSSL detection. Deal better when
7689 there are multiple SSLs installed with different versions.
7690 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
7691 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
7693 - Make unit tests (and other invocations that aren't the real Tor)
7694 run without launching listeners, creating subdirectories, and so on.
7695 - The OS X installer was adding a symlink for tor_resolve but
7696 the binary was called tor-resolve (reported by Thomas Hardly).
7697 - Now we can target arch and OS in rpm builds (contributed by
7698 Phobos). Also make the resulting dist-rpm filename match the
7700 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
7701 if you log to syslog and want something other than LOG_DAEMON.
7702 - Fix the torify (tsocks) config file to not use Tor for localhost
7704 - Start shipping socks-extensions.txt, tor-doc-unix.html,
7705 tor-doc-server.html, and stylesheet.css in the tarball.
7706 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
7707 They are useless now.
7708 - Add Peter Palfrader's contributed check-tor script. It lets you
7709 easily check whether a given server (referenced by nickname)
7710 is reachable by you.
7711 - Add BSD-style contributed startup script "rc.subr" from Peter
7714 o Directory improvements -- new directory protocol:
7715 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
7716 - Authorities and caches publish individual descriptors (by
7717 digest, by fingerprint, by "all", and by "tell me yours").
7718 - Clients don't download or use the old directory anymore. Now they
7719 download network-statuses from the directory authorities, and
7720 fetch individual server descriptors as needed from mirrors.
7721 - Clients don't download descriptors of non-running servers.
7722 - Download descriptors by digest, not by fingerprint. Caches try to
7723 download all listed digests from authorities; clients try to
7724 download "best" digests from caches. This avoids partitioning
7725 and isolating attacks better.
7726 - Only upload a new server descriptor when options change, 18
7727 hours have passed, uptime is reset, or bandwidth changes a lot.
7728 - Directory authorities silently throw away new descriptors that
7729 haven't changed much if the timestamps are similar. We do this to
7730 tolerate older Tor servers that upload a new descriptor every 15
7731 minutes. (It seemed like a good idea at the time.)
7732 - Clients choose directory servers from the network status lists,
7733 not from their internal list of router descriptors. Now they can
7734 go to caches directly rather than needing to go to authorities
7735 to bootstrap the first set of descriptors.
7736 - When picking a random directory, prefer non-authorities if any
7738 - Add a new flag to network-status indicating whether the server
7739 can answer v2 directory requests too.
7740 - Directory mirrors now cache up to 16 unrecognized network-status
7741 docs, so new directory authorities will be cached too.
7742 - Stop parsing, storing, or using running-routers output (but
7743 mirrors still cache and serve it).
7744 - Clients consider a threshold of "versioning" directory authorities
7745 before deciding whether to warn the user that he's obsolete.
7746 - Authorities publish separate sorted lists of recommended versions
7747 for clients and for servers.
7748 - Change DirServers config line to note which dirs are v1 authorities.
7749 - Put nicknames on the DirServer line, so we can refer to them
7750 without requiring all our users to memorize their IP addresses.
7751 - Remove option when getting directory cache to see whether they
7752 support running-routers; they all do now. Replace it with one
7753 to see whether caches support v2 stuff.
7754 - Stop listing down or invalid nodes in the v1 directory. This
7755 reduces its bulk by about 1/3, and reduces load on mirrors.
7756 - Mirrors no longer cache the v1 directory as often.
7757 - If we as a directory mirror don't know of any v1 directory
7758 authorities, then don't try to cache any v1 directories.
7760 o Other directory improvements:
7761 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
7762 fifth authoritative directory servers.
7763 - Directory authorities no longer require an open connection from
7764 a server to consider him "reachable". We need this change because
7765 when we add new directory authorities, old servers won't know not
7767 - Dir authorities now do their own external reachability testing
7768 of each server, and only list as running the ones they found to
7769 be reachable. We also send back warnings to the server's logs if
7770 it uploads a descriptor that we already believe is unreachable.
7771 - Spread the directory authorities' reachability testing over the
7772 entire testing interval, so we don't try to do 500 TLS's at once
7774 - Make the "stable" router flag in network-status be the median of
7775 the uptimes of running valid servers, and make clients pay
7776 attention to the network-status flags. Thus the cutoff adapts
7777 to the stability of the network as a whole, making IRC, IM, etc
7778 connections more reliable.
7779 - Make the v2 dir's "Fast" flag based on relative capacity, just
7780 like "Stable" is based on median uptime. Name everything in the
7781 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
7782 - Retry directory requests if we fail to get an answer we like
7783 from a given dirserver (we were retrying before, but only if
7784 we fail to connect).
7785 - Return a robots.txt on our dirport to discourage google indexing.
7787 o Controller protocol improvements:
7788 - Revised controller protocol (version 1) that uses ascii rather
7789 than binary: tor/doc/control-spec.txt. Add supporting libraries
7790 in python and java and c# so you can use the controller from your
7791 applications without caring how our protocol works.
7792 - Allow the DEBUG controller event to work again. Mark certain log
7793 entries as "don't tell this to controllers", so we avoid cycles.
7794 - New controller function "getinfo accounting", to ask how
7795 many bytes we've used in this time period.
7796 - Add a "resetconf" command so you can set config options like
7797 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
7798 a config option in the torrc with no value, then it clears it
7799 entirely (rather than setting it to its default).
7800 - Add a "getinfo config-file" to tell us where torrc is. Also
7801 expose guard nodes, config options/names.
7802 - Add a "quit" command (when when using the controller manually).
7803 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
7804 stop using any currently-dirty circuits for new streams, so we
7805 don't link new actions to old actions. This also occurs on HUP
7807 - If we would close a stream early (e.g. it asks for a .exit that
7808 we know would refuse it) but the LeaveStreamsUnattached config
7809 option is set by the controller, then don't close it.
7810 - Add a new controller event type "authdir_newdescs" that allows
7811 controllers to get all server descriptors that were uploaded to
7812 a router in its role as directory authority.
7813 - New controller option "getinfo desc/all-recent" to fetch the
7814 latest server descriptor for every router that Tor knows about.
7815 - Fix the controller's "attachstream 0" command to treat conn like
7816 it just connected, doing address remapping, handling .exit and
7817 .onion idioms, and so on. Now we're more uniform in making sure
7818 that the controller hears about new and closing connections.
7819 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
7820 the controller. Also, rotate dns and cpu workers if the controller
7821 changes options that will affect them; and initialize the dns
7822 worker cache tree whether or not we start out as a server.
7823 - Add a new circuit purpose 'controller' to let the controller ask
7824 for a circuit that Tor won't try to use. Extend the "extendcircuit"
7825 controller command to let you specify the purpose if you're starting
7826 a new circuit. Add a new "setcircuitpurpose" controller command to
7827 let you change a circuit's purpose after it's been created.
7828 - Let the controller ask for "getinfo dir/server/foo" so it can ask
7829 directly rather than connecting to the dir port. "getinfo
7830 dir/status/foo" also works, but currently only if your DirPort
7832 - Let the controller tell us about certain router descriptors
7833 that it doesn't want Tor to use in circuits. Implement
7834 "setrouterpurpose" and modify "+postdescriptor" to do this.
7835 - If the controller's *setconf commands fail, collect an error
7836 message in a string and hand it back to the controller -- don't
7837 just tell them to go read their logs.
7839 o Scalability, resource management, and performance:
7840 - Fix a major load balance bug: we were round-robin reading in 16 KB
7841 chunks, and servers with bandwidthrate of 20 KB, while downloading
7842 a 600 KB directory, would starve their other connections. Now we
7843 try to be a bit more fair.
7844 - Be more conservative about whether to advertise our DirPort.
7845 The main change is to not advertise if we're running at capacity
7846 and either a) we could hibernate ever or b) our capacity is low
7847 and we're using a default DirPort.
7848 - We weren't cannibalizing circuits correctly for
7849 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
7850 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
7851 build those from scratch. This should make hidden services faster.
7852 - Predict required circuits better, with an eye toward making hidden
7853 services faster on the service end.
7854 - Compress exit policies even more: look for duplicate lines and
7856 - Generate 18.0.0.0/8 address policy format in descs when we can;
7857 warn when the mask is not reducible to a bit-prefix.
7858 - There used to be two ways to specify your listening ports in a
7859 server descriptor: on the "router" line and with a separate "ports"
7860 line. Remove support for the "ports" line.
7861 - Reduce memory requirements in our structs by changing the order
7862 of fields. Replace balanced trees with hash tables. Inline
7863 bottleneck smartlist functions. Add a "Map from digest to void*"
7864 abstraction so we can do less hex encoding/decoding, and use it
7865 in router_get_by_digest(). Many other CPU and memory improvements.
7866 - Allow tor_gzip_uncompress to extract as much as possible from
7867 truncated compressed data. Try to extract as many
7868 descriptors as possible from truncated http responses (when
7869 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
7870 - Make circ->onionskin a pointer, not a static array. moria2 was using
7871 125000 circuit_t's after it had been up for a few weeks, which
7872 translates to 20+ megs of wasted space.
7873 - The private half of our EDH handshake keys are now chosen out
7874 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
7875 - Stop doing the complex voodoo overkill checking for insecure
7876 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
7877 - Do round-robin writes for TLS of at most 16 kB per write. This
7878 might be more fair on loaded Tor servers.
7879 - Do not use unaligned memory access on alpha, mips, or mipsel.
7880 It *works*, but is very slow, so we treat them as if it doesn't.
7882 o Other bugfixes and improvements:
7883 - Start storing useful information to $DATADIR/state, so we can
7884 remember things across invocations of Tor. Retain unrecognized
7885 lines so we can be forward-compatible, and write a TorVersion line
7886 so we can be backward-compatible.
7887 - If ORPort is set, Address is not explicitly set, and our hostname
7888 resolves to a private IP address, try to use an interface address
7889 if it has a public address. Now Windows machines that think of
7890 themselves as localhost can guess their address.
7891 - Regenerate our local descriptor if it's dirty and we try to use
7892 it locally (e.g. if it changes during reachability detection).
7893 This was causing some Tor servers to keep publishing the same
7894 initial descriptor forever.
7895 - Tor servers with dynamic IP addresses were needing to wait 18
7896 hours before they could start doing reachability testing using
7897 the new IP address and ports. This is because they were using
7898 the internal descriptor to learn what to test, yet they were only
7899 rebuilding the descriptor once they decided they were reachable.
7900 - It turns out we couldn't bootstrap a network since we added
7901 reachability detection in 0.1.0.1-rc. Good thing the Tor network
7902 has never gone down. Add an AssumeReachable config option to let
7903 servers and authorities bootstrap. When we're trying to build a
7904 high-uptime or high-bandwidth circuit but there aren't enough
7905 suitable servers, try being less picky rather than simply failing.
7906 - Newly bootstrapped Tor networks couldn't establish hidden service
7907 circuits until they had nodes with high uptime. Be more tolerant.
7908 - Really busy servers were keeping enough circuits open on stable
7909 connections that they were wrapping around the circuit_id
7910 space. (It's only two bytes.) This exposed a bug where we would
7911 feel free to reuse a circuit_id even if it still exists but has
7912 been marked for close. Try to fix this bug. Some bug remains.
7913 - When we fail to bind or listen on an incoming or outgoing
7914 socket, we now close it before refusing, rather than just
7915 leaking it. (Thanks to Peter Palfrader for finding.)
7916 - Fix a file descriptor leak in start_daemon().
7917 - On Windows, you can't always reopen a port right after you've
7918 closed it. So change retry_listeners() to only close and re-open
7919 ports that have changed.
7920 - Workaround a problem with some http proxies that refuse GET
7921 requests that specify "Content-Length: 0". Reported by Adrian.
7922 - Recover better from TCP connections to Tor servers that are
7923 broken but don't tell you (it happens!); and rotate TLS
7924 connections once a week.
7925 - Fix a scary-looking but apparently harmless bug where circuits
7926 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
7927 servers, and never switch to state CIRCUIT_STATE_OPEN.
7928 - Check for even more Windows version flags when writing the platform
7929 string in server descriptors, and note any we don't recognize.
7930 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
7931 get a better idea of why their circuits failed. Not used yet.
7932 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
7933 We don't use them yet, but maybe one day our DNS resolver will be
7934 able to discover them.
7935 - Let people type "tor --install" as well as "tor -install" when they
7936 want to make it an NT service.
7937 - Looks like we were never delivering deflated (i.e. compressed)
7938 running-routers lists, even when asked. Oops.
7939 - We were leaking some memory every time the client changed IPs.
7940 - Clean up more of the OpenSSL memory when exiting, so we can detect
7941 memory leaks better.
7942 - Never call free() on tor_malloc()d memory. This will help us
7943 use dmalloc to detect memory leaks.
7944 - Some Tor servers process billions of cells per day. These
7945 statistics are now uint64_t's.
7946 - Check [X-]Forwarded-For headers in HTTP requests when generating
7947 log messages. This lets people run dirservers (and caches) behind
7948 Apache but still know which IP addresses are causing warnings.
7949 - Fix minor integer overflow in calculating when we expect to use up
7950 our bandwidth allocation before hibernating.
7951 - Lower the minimum required number of file descriptors to 1000,
7952 so we can have some overhead for Valgrind on Linux, where the
7953 default ulimit -n is 1024.
7954 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
7955 and its existence is confusing some users.
7957 o Config option fixes:
7958 - Add a new config option ExitPolicyRejectPrivate which defaults
7959 to on. Now all exit policies will begin with rejecting private
7960 addresses, unless the server operator explicitly turns it off.
7961 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
7962 - Add new ReachableORAddresses and ReachableDirAddresses options
7963 that understand address policies. FascistFirewall is now a synonym
7964 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
7965 - Start calling it FooListenAddress rather than FooBindAddress,
7966 since few of our users know what it means to bind an address
7968 - If the user gave Tor an odd number of command-line arguments,
7969 we were silently ignoring the last one. Now we complain and fail.
7970 This wins the oldest-bug prize -- this bug has been present since
7971 November 2002, as released in Tor 0.0.0.
7972 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
7973 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
7974 it would silently ignore the 6668.
7975 - If we get a linelist or linelist_s config option from the torrc,
7976 e.g. ExitPolicy, and it has no value, warn and skip rather than
7977 silently resetting it to its default.
7978 - Setconf was appending items to linelists, not clearing them.
7979 - Add MyFamily to torrc.sample in the server section, so operators
7980 will be more likely to learn that it exists.
7981 - Make ContactInfo mandatory for authoritative directory servers.
7982 - MaxConn has been obsolete for a while now. Document the ConnLimit
7983 config option, which is a *minimum* number of file descriptors
7984 that must be available else Tor refuses to start.
7985 - Get rid of IgnoreVersion undocumented config option, and make us
7986 only warn, never exit, when we're running an obsolete version.
7987 - Make MonthlyAccountingStart config option truly obsolete now.
7988 - Correct the man page entry on TrackHostExitsExpire.
7989 - Let directory authorities start even if they don't specify an
7990 Address config option.
7991 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
7992 reflect the updated flags in our v2 dir protocol.
7994 o Config option features:
7995 - Add a new config option FastFirstHopPK (on by default) so clients
7996 do a trivial crypto handshake for their first hop, since TLS has
7997 already taken care of confidentiality and authentication.
7998 - Let the user set ControlListenAddress in the torrc. This can be
7999 dangerous, but there are some cases (like a secured LAN) where it
8001 - New config options to help controllers: FetchServerDescriptors
8002 and FetchHidServDescriptors for whether to fetch server
8003 info and hidserv info or let the controller do it, and
8004 PublishServerDescriptor and PublishHidServDescriptors.
8005 - Also let the controller set the __AllDirActionsPrivate config
8006 option if you want all directory fetches/publishes to happen via
8007 Tor (it assumes your controller bootstraps your circuits).
8008 - Add "HardwareAccel" config option: support for crypto hardware
8009 accelerators via OpenSSL. Off by default, until we find somebody
8010 smart who can test it for us. (It appears to produce seg faults
8011 in at least some cases.)
8012 - New config option "AuthDirRejectUnlisted" for directory authorities
8013 as a panic button: if we get flooded with unusable servers we can
8014 revert to only listing servers in the approved-routers file.
8015 - Directory authorities can now reject/invalidate by key and IP,
8016 with the config options "AuthDirInvalid" and "AuthDirReject", or
8017 by marking a fingerprint as "!reject" or "!invalid" (as its
8018 nickname) in the approved-routers file. This is useful since
8019 currently we automatically list servers as running and usable
8020 even if we know they're jerks.
8021 - Add a new config option TestSocks so people can see whether their
8022 applications are using socks4, socks4a, socks5-with-ip, or
8023 socks5-with-fqdn. This way they don't have to keep mucking
8024 with tcpdump and wondering if something got cached somewhere.
8025 - Add "private:*" as an alias in configuration for policies. Now
8026 you can simplify your exit policy rather than needing to list
8027 every single internal or nonroutable network space.
8028 - Accept "private:*" in routerdesc exit policies; not generated yet
8029 because older Tors do not understand it.
8030 - Add configuration option "V1AuthoritativeDirectory 1" which
8031 moria1, moria2, and tor26 have set.
8032 - Implement an option, VirtualAddrMask, to set which addresses
8033 get handed out in response to mapaddress requests. This works
8034 around a bug in tsocks where 127.0.0.0/8 is never socksified.
8035 - Add a new config option FetchUselessDescriptors, off by default,
8036 for when you plan to run "exitlist" on your client and you want
8037 to know about even the non-running descriptors.
8038 - SocksTimeout: How long do we let a socks connection wait
8039 unattached before we fail it?
8040 - CircuitBuildTimeout: Cull non-open circuits that were born
8041 at least this many seconds ago.
8042 - CircuitIdleTimeout: Cull open clean circuits that were born
8043 at least this many seconds ago.
8044 - New config option SafeSocks to reject all application connections
8045 using unsafe socks protocols. Defaults to off.
8047 o Improved and clearer log messages:
8048 - Reduce clutter in server logs. We're going to try to make
8049 them actually usable now. New config option ProtocolWarnings that
8050 lets you hear about how _other Tors_ are breaking the protocol. Off
8052 - Divide log messages into logging domains. Once we put some sort
8053 of interface on this, it will let people looking at more verbose
8054 log levels specify the topics they want to hear more about.
8055 - Log server fingerprint on startup, so new server operators don't
8056 have to go hunting around their filesystem for it.
8057 - Provide dire warnings to any users who set DirServer manually;
8058 move it out of torrc.sample and into torrc.complete.
8059 - Make the log message less scary when all the dirservers are
8060 temporarily unreachable.
8061 - When tor_socketpair() fails in Windows, give a reasonable
8062 Windows-style errno back.
8063 - Improve tor_gettimeofday() granularity on windows.
8064 - We were printing the number of idle dns workers incorrectly when
8066 - Handle duplicate lines in approved-routers files without warning.
8067 - We were whining about using socks4 or socks5-with-local-lookup
8068 even when it's an IP address in the "virtual" range we designed
8069 exactly for this case.
8070 - Check for named servers when looking them up by nickname;
8071 warn when we're calling a non-named server by its nickname;
8072 don't warn twice about the same name.
8073 - Downgrade the dirserver log messages when whining about
8075 - Correct "your server is reachable" log entries to indicate that
8076 it was self-testing that told us so.
8077 - If we're trying to be a Tor server and running Windows 95/98/ME
8078 as a server, explain that we'll likely crash.
8079 - Provide a more useful warn message when our onion queue gets full:
8080 the CPU is too slow or the exit policy is too liberal.
8081 - Don't warn when we receive a 503 from a dirserver/cache -- this
8082 will pave the way for them being able to refuse if they're busy.
8083 - When we fail to bind a listener, try to provide a more useful
8084 log message: e.g., "Is Tor already running?"
8085 - Only start testing reachability once we've established a
8086 circuit. This will make startup on dir authorities less noisy.
8087 - Don't try to upload hidden service descriptors until we have
8088 established a circuit.
8089 - Tor didn't warn when it failed to open a log file.
8090 - Warn when listening on a public address for socks. We suspect a
8091 lot of people are setting themselves up as open socks proxies,
8092 and they have no idea that jerks on the Internet are using them,
8093 since they simply proxy the traffic into the Tor network.
8094 - Give a useful message when people run Tor as the wrong user,
8095 rather than telling them to start chowning random directories.
8096 - Fix a harmless bug that was causing Tor servers to log
8097 "Got an end because of misc error, but we're not an AP. Closing."
8098 - Fix wrong log message when you add a "HiddenServiceNodes" config
8099 line without any HiddenServiceDir line (reported by Chris Thomas).
8100 - Directory authorities now stop whining so loudly about bad
8101 descriptors that they fetch from other dirservers. So when there's
8102 a log complaint, it's for sure from a freshly uploaded descriptor.
8103 - When logging via syslog, include the pid whenever we provide
8104 a log entry. Suggested by Todd Fries.
8105 - When we're shutting down and we do something like try to post a
8106 server descriptor or rendezvous descriptor, don't complain that
8107 we seem to be unreachable. Of course we are, we're shutting down.
8108 - Change log line for unreachability to explicitly suggest /etc/hosts
8109 as the culprit. Also make it clearer what IP address and ports we're
8110 testing for reachability.
8111 - Put quotes around user-supplied strings when logging so users are
8112 more likely to realize if they add bad characters (like quotes)
8114 - NT service patch from Matt Edman to improve error messages on Win32.
8117 Changes in version 0.1.0.17 - 2006-02-17
8118 o Crash bugfixes on 0.1.0.x:
8119 - When servers with a non-zero DirPort came out of hibernation,
8120 sometimes they would trigger an assert.
8122 o Other important bugfixes:
8123 - On platforms that don't have getrlimit (like Windows), we were
8124 artificially constraining ourselves to a max of 1024
8125 connections. Now just assume that we can handle as many as 15000
8126 connections. Hopefully this won't cause other problems.
8128 o Backported features:
8129 - When we're a server, a client asks for an old-style directory,
8130 and our write bucket is empty, don't give it to him. This way
8131 small servers can continue to serve the directory *sometimes*,
8132 without getting overloaded.
8133 - Whenever you get a 503 in response to a directory fetch, try
8134 once more. This will become important once servers start sending
8135 503's whenever they feel busy.
8136 - Fetch a new directory every 120 minutes, not every 40 minutes.
8137 Now that we have hundreds of thousands of users running the old
8138 directory algorithm, it's starting to hurt a lot.
8139 - Bump up the period for forcing a hidden service descriptor upload
8140 from 20 minutes to 1 hour.
8143 Changes in version 0.1.0.16 - 2006-01-02
8144 o Crash bugfixes on 0.1.0.x:
8145 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8146 corrupting the heap, losing FDs, or crashing when we need to resize
8147 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8148 - It turns out sparc64 platforms crash on unaligned memory access
8149 too -- so detect and avoid this.
8150 - Handle truncated compressed data correctly (by detecting it and
8152 - Fix possible-but-unlikely free(NULL) in control.c.
8153 - When we were closing connections, there was a rare case that
8154 stomped on memory, triggering seg faults and asserts.
8155 - Avoid potential infinite recursion when building a descriptor. (We
8156 don't know that it ever happened, but better to fix it anyway.)
8157 - We were neglecting to unlink marked circuits from soon-to-close OR
8158 connections, which caused some rare scribbling on freed memory.
8159 - Fix a memory stomping race bug when closing the joining point of two
8160 rendezvous circuits.
8161 - Fix an assert in time parsing found by Steven Murdoch.
8163 o Other bugfixes on 0.1.0.x:
8164 - When we're doing reachability testing, provide more useful log
8165 messages so the operator knows what to expect.
8166 - Do not check whether DirPort is reachable when we are suppressing
8167 advertising it because of hibernation.
8168 - When building with -static or on Solaris, we sometimes needed -ldl.
8169 - One of the dirservers (tor26) changed its IP address.
8170 - When we're deciding whether a stream has enough circuits around
8171 that can handle it, count the freshly dirty ones and not the ones
8172 that are so dirty they won't be able to handle it.
8173 - When we're expiring old circuits, we had a logic error that caused
8174 us to close new rendezvous circuits rather than old ones.
8175 - Give a more helpful log message when you try to change ORPort via
8176 the controller: you should upgrade Tor if you want that to work.
8177 - We were failing to parse Tor versions that start with "Tor ".
8178 - Tolerate faulty streams better: when a stream fails for reason
8179 exitpolicy, stop assuming that the router is lying about his exit
8180 policy. When a stream fails for reason misc, allow it to retry just
8181 as if it was resolvefailed. When a stream has failed three times,
8182 reset its failure count so we can try again and get all three tries.
8185 Changes in version 0.1.0.15 - 2005-09-23
8186 o Bugfixes on 0.1.0.x:
8187 - Reject ports 465 and 587 (spam targets) in default exit policy.
8188 - Don't crash when we don't have any spare file descriptors and we
8189 try to spawn a dns or cpu worker.
8190 - Get rid of IgnoreVersion undocumented config option, and make us
8191 only warn, never exit, when we're running an obsolete version.
8192 - Don't try to print a null string when your server finds itself to
8193 be unreachable and the Address config option is empty.
8194 - Make the numbers in read-history and write-history into uint64s,
8195 so they don't overflow and publish negatives in the descriptor.
8196 - Fix a minor memory leak in smartlist_string_remove().
8197 - We were only allowing ourselves to upload a server descriptor at
8198 most every 20 minutes, even if it changed earlier than that.
8199 - Clean up log entries that pointed to old URLs.
8202 Changes in version 0.1.0.14 - 2005-08-08
8203 o Bugfixes on 0.1.0.x:
8204 - Fix the other half of the bug with crypto handshakes
8206 - Fix an assert trigger if you send a 'signal term' via the
8207 controller when it's listening for 'event info' messages.
8210 Changes in version 0.1.0.13 - 2005-08-04
8211 o Bugfixes on 0.1.0.x:
8212 - Fix a critical bug in the security of our crypto handshakes.
8213 - Fix a size_t underflow in smartlist_join_strings2() that made
8214 it do bad things when you hand it an empty smartlist.
8215 - Fix Windows installer to ship Tor license (thanks to Aphex for
8216 pointing out this oversight) and put a link to the doc directory
8218 - Explicitly set no-unaligned-access for sparc: it turns out the
8219 new gcc's let you compile broken code, but that doesn't make it
8223 Changes in version 0.1.0.12 - 2005-07-18
8224 o New directory servers:
8225 - tor26 has changed IP address.
8227 o Bugfixes on 0.1.0.x:
8228 - Fix a possible double-free in tor_gzip_uncompress().
8229 - When --disable-threads is set, do not search for or link against
8231 - Don't trigger an assert if an authoritative directory server
8232 claims its dirport is 0.
8233 - Fix bug with removing Tor as an NT service: some people were
8234 getting "The service did not return an error." Thanks to Matt
8238 Changes in version 0.1.0.11 - 2005-06-30
8239 o Bugfixes on 0.1.0.x:
8240 - Fix major security bug: servers were disregarding their
8241 exit policies if clients behaved unexpectedly.
8242 - Make OS X init script check for missing argument, so we don't
8243 confuse users who invoke it incorrectly.
8244 - Fix a seg fault in "tor --hash-password foo".
8245 - The MAPADDRESS control command was broken.
8248 Changes in version 0.1.0.10 - 2005-06-14
8250 - Make NT services work and start on startup on Win32 (based on
8251 patch by Matt Edman). See the FAQ entry for details.
8252 - Make 'platform' string in descriptor more accurate for Win32
8253 servers, so it's not just "unknown platform".
8254 - REUSEADDR on normal platforms means you can rebind to the port
8255 right after somebody else has let it go. But REUSEADDR on Win32
8256 means you can bind to the port _even when somebody else already
8257 has it bound_! So, don't do that on Win32.
8258 - Clean up the log messages when starting on Win32 with no config
8260 - Allow seeding the RNG on Win32 even when you're not running as
8261 Administrator. If seeding the RNG on Win32 fails, quit.
8263 o Assert / crash bugs:
8264 - Refuse relay cells that claim to have a length larger than the
8265 maximum allowed. This prevents a potential attack that could read
8266 arbitrary memory (e.g. keys) from an exit server's process
8268 - If unofficial Tor clients connect and send weird TLS certs, our
8269 Tor server triggers an assert. Stop asserting, and start handling
8270 TLS errors better in other situations too.
8271 - Fix a race condition that can trigger an assert when we have a
8272 pending create cell and an OR connection attempt fails.
8275 - Use pthreads for worker processes rather than forking. This was
8276 forced because when we forked, we ended up wasting a lot of
8277 duplicate ram over time.
8278 - Also switch to foo_r versions of some library calls to allow
8279 reentry and threadsafeness.
8280 - Implement --disable-threads configure option. Disable threads on
8281 netbsd and openbsd by default, because they have no reentrant
8282 resolver functions (!), and on solaris since it has other
8284 - Fix possible bug on threading platforms (e.g. win32) which was
8285 leaking a file descriptor whenever a cpuworker or dnsworker died.
8286 - Fix a minor memory leak when somebody establishes an introduction
8287 point at your Tor server.
8288 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
8290 - Add ./configure --with-dmalloc option, to track memory leaks.
8291 - And try to free all memory on closing, so we can detect what
8294 o Protocol correctness:
8295 - When we've connected to an OR and handshaked but didn't like
8296 the result, we were closing the conn without sending destroy
8297 cells back for pending circuits. Now send those destroys.
8298 - Start sending 'truncated' cells back rather than destroy cells
8299 if the circuit closes in front of you. This means we won't have
8300 to abandon partially built circuits.
8301 - Handle changed router status correctly when dirserver reloads
8302 fingerprint file. We used to be dropping all unverified descriptors
8303 right then. The bug was hidden because we would immediately
8304 fetch a directory from another dirserver, which would include the
8305 descriptors we just dropped.
8306 - Revise tor-spec to add more/better stream end reasons.
8307 - Revise all calls to connection_edge_end to avoid sending 'misc',
8308 and to take errno into account where possible.
8309 - Client now retries when streams end early for 'hibernating' or
8310 'resource limit' reasons, rather than failing them.
8311 - Try to be more zealous about calling connection_edge_end when
8312 things go bad with edge conns in connection.c.
8314 o Robustness improvements:
8315 - Better handling for heterogeneous / unreliable nodes:
8316 - Annotate circuits with whether they aim to contain high uptime
8317 nodes and/or high capacity nodes. When building circuits, choose
8319 - This means that every single node in an intro rend circuit,
8320 not just the last one, will have a minimum uptime.
8321 - New config option LongLivedPorts to indicate application streams
8322 that will want high uptime circuits.
8323 - Servers reset uptime when a dir fetch entirely fails. This
8324 hopefully reflects stability of the server's network connectivity.
8325 - If somebody starts his tor server in Jan 2004 and then fixes his
8326 clock, don't make his published uptime be a year.
8327 - Reset published uptime when we wake up from hibernation.
8328 - Introduce a notion of 'internal' circs, which are chosen without
8329 regard to the exit policy of the last hop. Intro and rendezvous
8330 circs must be internal circs, to avoid leaking information. Resolve
8331 and connect streams can use internal circs if they want.
8332 - New circuit pooling algorithm: keep track of what destination ports
8333 we've used recently (start out assuming we'll want to use 80), and
8334 make sure to have enough circs around to satisfy these ports. Also
8335 make sure to have 2 internal circs around if we've required internal
8336 circs lately (and with high uptime if we've seen that lately too).
8337 - Turn addr_policy_compare from a tristate to a quadstate; this should
8338 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
8339 for google.com" problem.
8340 - When a client asks us for a dir mirror and we don't have one,
8341 launch an attempt to get a fresh one.
8342 - First cut at support for "create-fast" cells. Clients can use
8343 these when extending to their first hop, since the TLS already
8344 provides forward secrecy and authentication. Not enabled on
8347 o Reachability testing.
8348 - Your Tor server will automatically try to see if its ORPort and
8349 DirPort are reachable from the outside, and it won't upload its
8350 descriptor until it decides at least ORPort is reachable (when
8351 DirPort is not yet found reachable, publish it as zero).
8352 - When building testing circs for ORPort testing, use only
8353 high-bandwidth nodes, so fewer circuits fail.
8354 - Notice when our IP changes, and reset stats/uptime/reachability.
8355 - Authdirservers don't do ORPort reachability detection, since
8356 they're in clique mode, so it will be rare to find a server not
8357 already connected to them.
8358 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
8362 - Now we allow two unverified servers with the same nickname
8363 but different keys. But if a nickname is verified, only that
8364 nickname+key are allowed.
8365 - If you're an authdirserver connecting to an address:port,
8366 and it's not the OR you were expecting, forget about that
8367 descriptor. If he *was* the one you were expecting, then forget
8368 about all other descriptors for that address:port.
8369 - Allow servers to publish descriptors from 12 hours in the future.
8370 Corollary: only whine about clock skew from the dirserver if
8371 he's a trusted dirserver (since now even verified servers could
8372 have quite wrong clocks).
8373 - Require servers that use the default dirservers to have public IP
8374 addresses. We have too many servers that are configured with private
8375 IPs and their admins never notice the log entries complaining that
8376 their descriptors are being rejected.
8378 o Efficiency improvements:
8379 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
8380 and /dev/poll), and hopefully work better on Windows too.
8381 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
8382 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
8383 - Find libevent even if it's hiding in /usr/local/ and your
8384 CFLAGS and LDFLAGS don't tell you to look there.
8385 - Be able to link with libevent as a shared library (the default
8386 after 1.0d), even if it's hiding in /usr/local/lib and even
8387 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
8388 assuming you're running gcc. Otherwise fail and give a useful
8390 - Switch to a new buffer management algorithm, which tries to avoid
8391 reallocing and copying quite as much. In first tests it looks like
8392 it uses *more* memory on average, but less cpu.
8393 - Switch our internal buffers implementation to use a ring buffer,
8394 to hopefully improve performance for fast servers a lot.
8395 - Reenable the part of the code that tries to flush as soon as an
8396 OR outbuf has a full TLS record available. Perhaps this will make
8397 OR outbufs not grow as huge except in rare cases, thus saving lots
8398 of CPU time plus memory.
8399 - Improve performance for dirservers: stop re-parsing the whole
8400 directory every time you regenerate it.
8401 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
8402 it much faster to look up a circuit for each relay cell.
8403 - Remove most calls to assert_all_pending_dns_resolves_ok(),
8404 since they're eating our cpu on exit nodes.
8405 - Stop wasting time doing a case insensitive comparison for every
8406 dns name every time we do any lookup. Canonicalize the names to
8407 lowercase when you first see them.
8410 - Handle unavailable hidden services better. Handle slow or busy
8411 hidden services better.
8412 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
8413 circ as necessary, if there are any completed ones lying around
8414 when we try to launch one.
8415 - Make hidden services try to establish a rendezvous for 30 seconds
8416 after fetching the descriptor, rather than for n (where n=3)
8417 attempts to build a circuit.
8418 - Adjust maximum skew and age for rendezvous descriptors: let skew
8419 be 48 hours rather than 90 minutes.
8420 - Reject malformed .onion addresses rather then passing them on as
8421 normal web requests.
8424 - More Tor controller support. See
8425 http://tor.eff.org/doc/control-spec.txt for all the new features,
8426 including signals to emulate unix signals from any platform;
8427 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
8428 closestream; closecircuit; etc.
8429 - Encode hashed controller passwords in hex instead of base64,
8430 to make it easier to write controllers.
8431 - Revise control spec and implementation to allow all log messages to
8432 be sent to controller with their severities intact (suggested by
8433 Matt Edman). Disable debug-level logs while delivering a debug-level
8434 log to the controller, to prevent loop. Update TorControl to handle
8435 new log event types.
8437 o New config options/defaults:
8438 - Begin scrubbing sensitive strings from logs by default. Turn off
8439 the config option SafeLogging if you need to do debugging.
8440 - New exit policy: accept most low-numbered ports, rather than
8441 rejecting most low-numbered ports.
8442 - Put a note in the torrc about abuse potential with the default
8444 - Add support for CONNECTing through https proxies, with "HttpsProxy"
8446 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
8447 based on patch from Adam Langley (basic auth only).
8448 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
8449 the fast servers that have been joining lately. (Clients are now
8450 willing to load balance over up to 2 MB of advertised bandwidth
8452 - New config option MaxAdvertisedBandwidth which lets you advertise
8453 a low bandwidthrate (to not attract as many circuits) while still
8454 allowing a higher bandwidthrate in reality.
8455 - Require BandwidthRate to be at least 20kB/s for servers.
8456 - Add a NoPublish config option, so you can be a server (e.g. for
8457 testing running Tor servers in other Tor networks) without
8458 publishing your descriptor to the primary dirservers.
8459 - Add a new AddressMap config directive to rewrite incoming socks
8460 addresses. This lets you, for example, declare an implicit
8461 required exit node for certain sites.
8462 - Add a new TrackHostExits config directive to trigger addressmaps
8463 for certain incoming socks addresses -- for sites that break when
8464 your exit keeps changing (based on patch from Mike Perry).
8465 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
8466 which describes how often we retry making new circuits if current
8467 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
8468 how long we're willing to make use of an already-dirty circuit.
8469 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
8470 a config option "ShutdownWaitLength" (when using kill -INT on
8472 - Fix an edge case in parsing config options: if they say "--"
8473 on the commandline, it's not a config option (thanks weasel).
8474 - New config option DirAllowPrivateAddresses for authdirservers.
8475 Now by default they refuse router descriptors that have non-IP or
8476 private-IP addresses.
8477 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
8478 smart" default value: low for servers and high for clients.
8479 - Some people were putting "Address " in their torrc, and they had
8480 a buggy resolver that resolved " " to 0.0.0.0. Oops.
8481 - If DataDir is ~/.tor, and that expands to /.tor, then default to
8482 LOCALSTATEDIR/tor instead.
8483 - Implement --verify-config command-line option to check if your torrc
8484 is valid without actually launching Tor.
8486 o Logging improvements:
8487 - When dirservers refuse a server descriptor, we now log its
8488 contactinfo, platform, and the poster's IP address.
8489 - Only warn once per nickname from add_nickname_list_to_smartlist()
8490 per failure, so an entrynode or exitnode choice that's down won't
8492 - When we're connecting to an OR and he's got a different nickname/key
8493 than we were expecting, only complain loudly if we're an OP or a
8494 dirserver. Complaining loudly to the OR admins just confuses them.
8495 - Whine at you if you're a server and you don't set your contactinfo.
8496 - Warn when exit policy implicitly allows local addresses.
8497 - Give a better warning when some other server advertises an
8498 ORPort that is actually an apache running ssl.
8499 - If we get an incredibly skewed timestamp from a dirserver mirror
8500 that isn't a verified OR, don't warn -- it's probably him that's
8502 - When a dirserver causes you to give a warn, mention which dirserver
8504 - Initialize libevent later in the startup process, so the logs are
8505 already established by the time we start logging libevent warns.
8506 - Use correct errno on win32 if libevent fails.
8507 - Check and warn about known-bad/slow libevent versions.
8508 - Stop warning about sigpipes in the logs. We're going to
8509 pretend that getting these occassionally is normal and fine.
8511 o New contrib scripts:
8512 - New experimental script tor/contrib/exitlist: a simple python
8513 script to parse directories and find Tor nodes that exit to listed
8515 - New experimental script tor/contrib/ExerciseServer.py (needs more
8516 work) that uses the controller interface to build circuits and
8517 fetch pages over them. This will help us bootstrap servers that
8518 have lots of capacity but haven't noticed it yet.
8519 - New experimental script tor/contrib/PathDemo.py (needs more work)
8520 that uses the controller interface to let you choose whole paths
8522 "<hostname>.<path,separated by dots>.<length of path>.path"
8523 - New contributed script "privoxy-tor-toggle" to toggle whether
8524 Privoxy uses Tor. Seems to be configured for Debian by default.
8525 - Have torctl.in/tor.sh.in check for location of su binary (needed
8529 - chdir() to your datadirectory at the *end* of the daemonize process,
8530 not the beginning. This was a problem because the first time you
8531 run tor, if your datadir isn't there, and you have runasdaemon set
8532 to 1, it will try to chdir to it before it tries to create it. Oops.
8533 - Fix several double-mark-for-close bugs, e.g. where we were finding
8534 a conn for a cell even if that conn is already marked for close.
8535 - Stop most cases of hanging up on a socks connection without sending
8537 - Fix a bug in the RPM package: set home directory for _tor to
8538 something more reasonable when first installing.
8539 - Stop putting nodename in the Platform string in server descriptors.
8540 It doesn't actually help, and it is confusing/upsetting some people.
8541 - When using preferred entry or exit nodes, ignore whether the
8542 circuit wants uptime or capacity. They asked for the nodes, they
8544 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
8545 artificially capped at 500kB.
8546 - Cache local dns resolves correctly even when they're .exit
8548 - If we're hibernating and we get a SIGINT, exit immediately.
8549 - tor-resolve requests were ignoring .exit if there was a working circuit
8550 they could use instead.
8551 - Pay more attention to the ClientOnly config option.
8552 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
8553 installer screens; and don't put stuff into StartupItems unless
8554 the user asks you to.
8557 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
8558 rather than just rejecting it.
8559 - If our clock jumps forward by 100 seconds or more, assume something
8560 has gone wrong with our network and abandon all not-yet-used circs.
8561 - When an application is using socks5, give him the whole variety of
8562 potential socks5 responses (connect refused, host unreachable, etc),
8563 rather than just "success" or "failure".
8564 - A more sane version numbering system. See
8565 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
8566 - Change version parsing logic: a version is "obsolete" if it is not
8567 recommended and (1) there is a newer recommended version in the
8568 same series, or (2) there are no recommended versions in the same
8569 series, but there are some recommended versions in a newer series.
8570 A version is "new" if it is newer than any recommended version in
8572 - Report HTTP reasons to client when getting a response from directory
8573 servers -- so you can actually know what went wrong.
8574 - Reject odd-looking addresses at the client (e.g. addresses that
8575 contain a colon), rather than having the server drop them because
8577 - Stop publishing socksport in the directory, since it's not
8578 actually meant to be public. For compatibility, publish a 0 there
8580 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
8581 cookies to disk and doesn't log each web request to disk. (Thanks
8582 to Brett Carrington for pointing this out.)
8583 - Add OSX uninstall instructions. An actual uninstall script will
8585 - Add "opt hibernating 1" to server descriptor to make it clearer
8586 whether the server is hibernating.
8589 Changes in version 0.0.9.10 - 2005-06-16
8590 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
8591 - Refuse relay cells that claim to have a length larger than the
8592 maximum allowed. This prevents a potential attack that could read
8593 arbitrary memory (e.g. keys) from an exit server's process
8597 Changes in version 0.0.9.9 - 2005-04-23
8598 o Bugfixes on 0.0.9.x:
8599 - If unofficial Tor clients connect and send weird TLS certs, our
8600 Tor server triggers an assert. This release contains a minimal
8601 backport from the broader fix that we put into 0.1.0.4-rc.
8604 Changes in version 0.0.9.8 - 2005-04-07
8605 o Bugfixes on 0.0.9.x:
8606 - We have a bug that I haven't found yet. Sometimes, very rarely,
8607 cpuworkers get stuck in the 'busy' state, even though the cpuworker
8608 thinks of itself as idle. This meant that no new circuits ever got
8609 established. Here's a workaround to kill any cpuworker that's been
8610 busy for more than 100 seconds.
8613 Changes in version 0.0.9.7 - 2005-04-01
8614 o Bugfixes on 0.0.9.x:
8615 - Fix another race crash bug (thanks to Glenn Fink for reporting).
8616 - Compare identity to identity, not to nickname, when extending to
8617 a router not already in the directory. This was preventing us from
8618 extending to unknown routers. Oops.
8619 - Make sure to create OS X Tor user in <500 range, so we aren't
8620 creating actual system users.
8621 - Note where connection-that-hasn't-sent-end was marked, and fix
8622 a few really loud instances of this harmless bug (it's fixed more
8626 Changes in version 0.0.9.6 - 2005-03-24
8627 o Bugfixes on 0.0.9.x (crashes and asserts):
8628 - Add new end stream reasons to maintainance branch. Fix bug where
8629 reason (8) could trigger an assert. Prevent bug from recurring.
8630 - Apparently win32 stat wants paths to not end with a slash.
8631 - Fix assert triggers in assert_cpath_layer_ok(), where we were
8632 blowing away the circuit that conn->cpath_layer points to, then
8633 checking to see if the circ is well-formed. Backport check to make
8634 sure we dont use the cpath on a closed connection.
8635 - Prevent circuit_resume_edge_reading_helper() from trying to package
8636 inbufs for marked-for-close streams.
8637 - Don't crash on hup if your options->address has become unresolvable.
8638 - Some systems (like OS X) sometimes accept() a connection and tell
8639 you the remote host is 0.0.0.0:0. If this happens, due to some
8640 other mis-features, we get confused; so refuse the conn for now.
8642 o Bugfixes on 0.0.9.x (other):
8643 - Fix harmless but scary "Unrecognized content encoding" warn message.
8644 - Add new stream error reason: TORPROTOCOL reason means "you are not
8645 speaking a version of Tor I understand; say bye-bye to your stream."
8646 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
8647 into the future, now that we are more tolerant of skew. This
8648 resolves a bug where a Tor server would refuse to cache a directory
8649 because all the directories it gets are too far in the future;
8650 yet the Tor server never logs any complaints about clock skew.
8651 - Mac packaging magic: make man pages useable, and do not overwrite
8652 existing torrc files.
8653 - Make OS X log happily to /var/log/tor/tor.log
8656 Changes in version 0.0.9.5 - 2005-02-22
8657 o Bugfixes on 0.0.9.x:
8658 - Fix an assert race at exit nodes when resolve requests fail.
8659 - Stop picking unverified dir mirrors--it only leads to misery.
8660 - Patch from Matt Edman to make NT services work better. Service
8661 support is still not compiled into the executable by default.
8662 - Patch from Dmitri Bely so the Tor service runs better under
8663 the win32 SYSTEM account.
8664 - Make tor-resolve actually work (?) on Win32.
8665 - Fix a sign bug when getrlimit claims to have 4+ billion
8666 file descriptors available.
8667 - Stop refusing to start when bandwidthburst == bandwidthrate.
8668 - When create cells have been on the onion queue more than five
8669 seconds, just send back a destroy and take them off the list.
8672 Changes in version 0.0.9.4 - 2005-02-03
8673 o Bugfixes on 0.0.9:
8674 - Fix an assert bug that took down most of our servers: when
8675 a server claims to have 1 GB of bandwidthburst, don't
8677 - Don't crash as badly if we have spawned the max allowed number
8678 of dnsworkers, or we're out of file descriptors.
8679 - Block more file-sharing ports in the default exit policy.
8680 - MaxConn is now automatically set to the hard limit of max
8681 file descriptors we're allowed (ulimit -n), minus a few for
8683 - Give a clearer message when servers need to raise their
8684 ulimit -n when they start running out of file descriptors.
8685 - SGI Compatibility patches from Jan Schaumann.
8686 - Tolerate a corrupt cached directory better.
8687 - When a dirserver hasn't approved your server, list which one.
8688 - Go into soft hibernation after 95% of the bandwidth is used,
8689 not 99%. This is especially important for daily hibernators who
8690 have a small accounting max. Hopefully it will result in fewer
8691 cut connections when the hard hibernation starts.
8692 - Load-balance better when using servers that claim more than
8693 800kB/s of capacity.
8694 - Make NT services work (experimental, only used if compiled in).
8697 Changes in version 0.0.9.3 - 2005-01-21
8698 o Bugfixes on 0.0.9:
8699 - Backport the cpu use fixes from main branch, so busy servers won't
8700 need as much processor time.
8701 - Work better when we go offline and then come back, or when we
8702 run Tor at boot before the network is up. We do this by
8703 optimistically trying to fetch a new directory whenever an
8704 application request comes in and we think we're offline -- the
8705 human is hopefully a good measure of when the network is back.
8706 - Backport some minimal hidserv bugfixes: keep rend circuits open as
8707 long as you keep using them; actually publish hidserv descriptors
8708 shortly after they change, rather than waiting 20-40 minutes.
8709 - Enable Mac startup script by default.
8710 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
8711 - When you update AllowUnverifiedNodes or FirewallPorts via the
8712 controller's setconf feature, we were always appending, never
8714 - When you update HiddenServiceDir via setconf, it was screwing up
8715 the order of reading the lines, making it fail.
8716 - Do not rewrite a cached directory back to the cache; otherwise we
8717 will think it is recent and not fetch a newer one on startup.
8718 - Workaround for webservers that lie about Content-Encoding: Tor
8719 now tries to autodetect compressed directories and compression
8720 itself. This lets us Proxypass dir fetches through apache.
8723 Changes in version 0.0.9.2 - 2005-01-04
8724 o Bugfixes on 0.0.9 (crashes and asserts):
8725 - Fix an assert on startup when the disk is full and you're logging
8727 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
8728 style address, then we'd crash.
8729 - Fix an assert trigger when the running-routers string we get from
8730 a dirserver is broken.
8731 - Make worker threads start and run on win32. Now win32 servers
8733 - Bandaid (not actually fix, but now it doesn't crash) an assert
8734 where the dns worker dies mysteriously and the main Tor process
8735 doesn't remember anything about the address it was resolving.
8737 o Bugfixes on 0.0.9 (Win32):
8738 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
8739 name out of the warning/assert messages.
8740 - Fix a superficial "unhandled error on read" bug on win32.
8741 - The win32 installer no longer requires a click-through for our
8742 license, since our Free Software license grants rights but does not
8744 - Win32: When connecting to a dirserver fails, try another one
8745 immediately. (This was already working for non-win32 Tors.)
8746 - Stop trying to parse $HOME on win32 when hunting for default
8748 - Make tor-resolve.c work on win32 by calling network_init().
8750 o Bugfixes on 0.0.9 (other):
8751 - Make 0.0.9.x build on Solaris again.
8752 - Due to a fencepost error, we were blowing away the \n when reporting
8753 confvalue items in the controller. So asking for multiple config
8754 values at once couldn't work.
8755 - When listing circuits that are pending on an opening OR connection,
8756 if we're an OR we were listing circuits that *end* at us as
8757 being pending on every listener, dns/cpu worker, etc. Stop that.
8758 - Dirservers were failing to create 'running-routers' or 'directory'
8759 strings if we had more than some threshold of routers. Fix them so
8760 they can handle any number of routers.
8761 - Fix a superficial "Duplicate mark for close" bug.
8762 - Stop checking for clock skew for OR connections, even for servers.
8763 - Fix a fencepost error that was chopping off the last letter of any
8764 nickname that is the maximum allowed nickname length.
8765 - Update URLs in log messages so they point to the new website.
8766 - Fix a potential problem in mangling server private keys while
8767 writing to disk (not triggered yet, as far as we know).
8768 - Include the licenses for other free software we include in Tor,
8769 now that we're shipping binary distributions more regularly.
8772 Changes in version 0.0.9.1 - 2004-12-15
8773 o Bugfixes on 0.0.9:
8774 - Make hibernation actually work.
8775 - Make HashedControlPassword config option work.
8776 - When we're reporting event circuit status to a controller,
8777 don't use the stream status code.
8780 Changes in version 0.0.9 - 2004-12-12
8781 o Bugfixes on 0.0.8.1 (Crashes and asserts):
8782 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
8783 write() call will fail and we handle it there.
8784 - When we run out of disk space, or other log writing error, don't
8785 crash. Just stop logging to that log and continue.
8786 - Fix isspace() and friends so they still make Solaris happy
8787 but also so they don't trigger asserts on win32.
8788 - Fix assert failure on malformed socks4a requests.
8789 - Fix an assert bug where a hidden service provider would fail if
8790 the first hop of his rendezvous circuit was down.
8791 - Better handling of size_t vs int, so we're more robust on 64
8794 o Bugfixes on 0.0.8.1 (Win32):
8795 - Make windows sockets actually non-blocking (oops), and handle
8796 win32 socket errors better.
8797 - Fix parse_iso_time on platforms without strptime (eg win32).
8798 - win32: when being multithreaded, leave parent fdarray open.
8799 - Better handling of winsock includes on non-MSV win32 compilers.
8800 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
8802 - Make unit tests work on win32.
8804 o Bugfixes on 0.0.8.1 (Path selection and streams):
8805 - Calculate timeout for waiting for a connected cell from the time
8806 we sent the begin cell, not from the time the stream started. If
8807 it took a long time to establish the circuit, we would time out
8808 right after sending the begin cell.
8809 - Fix router_compare_addr_to_addr_policy: it was not treating a port
8810 of * as always matching, so we were picking reject *:* nodes as
8811 exit nodes too. Oops.
8812 - When read() failed on a stream, we would close it without sending
8813 back an end. So 'connection refused' would simply be ignored and
8814 the user would get no response.
8815 - Stop a sigpipe: when an 'end' cell races with eof from the app,
8816 we shouldn't hold-open-until-flush if the eof arrived first.
8817 - Let resolve conns retry/expire also, rather than sticking around
8819 - Fix more dns related bugs: send back resolve_failed and end cells
8820 more reliably when the resolve fails, rather than closing the
8821 circuit and then trying to send the cell. Also attach dummy resolve
8822 connections to a circuit *before* calling dns_resolve(), to fix
8823 a bug where cached answers would never be sent in RESOLVED cells.
8825 o Bugfixes on 0.0.8.1 (Circuits):
8826 - Finally fix a bug that's been plaguing us for a year:
8827 With high load, circuit package window was reaching 0. Whenever
8828 we got a circuit-level sendme, we were reading a lot on each
8829 socket, but only writing out a bit. So we would eventually reach
8830 eof. This would be noticed and acted on even when there were still
8831 bytes sitting in the inbuf.
8832 - Use identity comparison, not nickname comparison, to choose which
8833 half of circuit-ID-space each side gets to use. This is needed
8834 because sometimes we think of a router as a nickname, and sometimes
8835 as a hex ID, and we can't predict what the other side will do.
8837 o Bugfixes on 0.0.8.1 (Other):
8838 - Fix a whole slew of memory leaks.
8839 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
8840 - If we are using select, make sure we stay within FD_SETSIZE.
8841 - When poll() is interrupted, we shouldn't believe the revents values.
8842 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
8843 and smartlist_len, which are two major profiling offenders.
8844 - If do_hup fails, actually notice.
8845 - Flush the log file descriptor after we print "Tor opening log file",
8846 so we don't see those messages days later.
8847 - Hidden service operators now correctly handle version 1 style
8848 INTRODUCE1 cells (nobody generates them still, so not a critical
8850 - Handle more errnos from accept() without closing the listener.
8851 Some OpenBSD machines were closing their listeners because
8852 they ran out of file descriptors.
8853 - Some people had wrapped their tor client/server in a script
8854 that would restart it whenever it died. This did not play well
8855 with our "shut down if your version is obsolete" code. Now people
8856 don't fetch a new directory if their local cached version is
8858 - Make our autogen.sh work on ksh as well as bash.
8859 - Better torrc example lines for dirbindaddress and orbindaddress.
8860 - Improved bounds checking on parsed ints (e.g. config options and
8861 the ones we find in directories.)
8862 - Stop using separate defaults for no-config-file and
8863 empty-config-file. Now you have to explicitly turn off SocksPort,
8864 if you don't want it open.
8865 - We were starting to daemonize before we opened our logs, so if
8866 there were any problems opening logs, we would complain to stderr,
8867 which wouldn't work, and then mysteriously exit.
8868 - If a verified OR connects to us before he's uploaded his descriptor,
8869 or we verify him and hup but he still has the original TLS
8870 connection, then conn->nickname is still set like he's unverified.
8872 o Code security improvements, inspired by Ilja:
8873 - tor_snprintf wrapper over snprintf with consistent (though not C99)
8875 - Replace sprintf with tor_snprintf. (I think they were all safe, but
8877 - Replace strcpy/strncpy with strlcpy in more places.
8878 - Avoid strcat; use tor_snprintf or strlcat instead.
8880 o Features (circuits and streams):
8881 - New circuit building strategy: keep a list of ports that we've
8882 used in the past 6 hours, and always try to have 2 circuits open
8883 or on the way that will handle each such port. Seed us with port
8884 80 so web users won't complain that Tor is "slow to start up".
8885 - Make kill -USR1 dump more useful stats about circuits.
8886 - When warning about retrying or giving up, print the address, so
8887 the user knows which one it's talking about.
8888 - If you haven't used a clean circuit in an hour, throw it away,
8889 just to be on the safe side. (This means after 6 hours a totally
8890 unused Tor client will have no circuits open.)
8891 - Support "foo.nickname.exit" addresses, to let Alice request the
8892 address "foo" as viewed by exit node "nickname". Based on a patch
8894 - If your requested entry or exit node has advertised bandwidth 0,
8896 - Be more greedy about filling up relay cells -- we try reading again
8897 once we've processed the stuff we read, in case enough has arrived
8898 to fill the last cell completely.
8899 - Refuse application socks connections to port 0.
8900 - Use only 0.0.9pre1 and later servers for resolve cells.
8902 o Features (bandwidth):
8903 - Hibernation: New config option "AccountingMax" lets you
8904 set how many bytes per month (in each direction) you want to
8905 allow your server to consume. Rather than spreading those
8906 bytes out evenly over the month, we instead hibernate for some
8907 of the month and pop up at a deterministic time, work until
8908 the bytes are consumed, then hibernate again. Config option
8909 "MonthlyAccountingStart" lets you specify which day of the month
8910 your billing cycle starts on.
8911 - Implement weekly/monthly/daily accounting: now you specify your
8912 hibernation properties by
8913 AccountingMax N bytes|KB|MB|GB|TB
8914 AccountingStart day|week|month [day] HH:MM
8915 Defaults to "month 1 0:00".
8916 - Let bandwidth and interval config options be specified as 5 bytes,
8917 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
8919 o Features (directories):
8920 - New "router-status" line in directory, to better bind each verified
8921 nickname to its identity key.
8922 - Clients can ask dirservers for /dir.z to get a compressed version
8923 of the directory. Only works for servers running 0.0.9, of course.
8924 - Make clients cache directories and use them to seed their router
8925 lists at startup. This means clients have a datadir again.
8926 - Respond to content-encoding headers by trying to uncompress as
8928 - Clients and servers now fetch running-routers; cache
8929 running-routers; compress running-routers; serve compressed
8931 - Make moria2 advertise a dirport of 80, so people behind firewalls
8932 will be able to get a directory.
8933 - Http proxy support
8934 - Dirservers translate requests for http://%s:%d/x to /x
8935 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
8936 be routed through this host.
8937 - Clients ask for /tor/x rather than /x for new enough dirservers.
8938 This way we can one day coexist peacefully with apache.
8939 - Clients specify a "Host: %s%d" http header, to be compatible
8940 with more proxies, and so running squid on an exit node can work.
8941 - Protect dirservers from overzealous descriptor uploading -- wait
8942 10 seconds after directory gets dirty, before regenerating.
8944 o Features (packages and install):
8945 - Add NSI installer contributed by J Doe.
8946 - Apply NT service patch from Osamu Fujino. Still needs more work.
8947 - Commit VC6 and VC7 workspace/project files.
8948 - Commit a tor.spec for making RPM files, with help from jbash.
8949 - Add contrib/torctl.in contributed by Glenn Fink.
8950 - Make expand_filename handle ~ and ~username.
8951 - Use autoconf to enable largefile support where necessary. Use
8952 ftello where available, since ftell can fail at 2GB.
8953 - Ship src/win32/ in the tarball, so people can use it to build.
8954 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
8957 o Features (ui controller):
8958 - Control interface: a separate program can now talk to your
8959 client/server over a socket, and get/set config options, receive
8960 notifications of circuits and streams starting/finishing/dying,
8961 bandwidth used, etc. The next step is to get some GUIs working.
8962 Let us know if you want to help out. See doc/control-spec.txt .
8963 - Ship a contrib/tor-control.py as an example script to interact
8964 with the control port.
8965 - "tor --hash-password zzyxz" will output a salted password for
8966 use in authenticating to the control interface.
8967 - Implement the control-spec's SAVECONF command, to write your
8968 configuration to torrc.
8969 - Get cookie authentication for the controller closer to working.
8970 - When set_conf changes our server descriptor, upload a new copy.
8971 But don't upload it too often if there are frequent changes.
8973 o Features (config and command-line):
8974 - Deprecate unofficial config option abbreviations, and abbreviations
8975 not on the command line.
8976 - Configuration infrastructure support for warning on obsolete
8978 - Give a slightly more useful output for "tor -h".
8979 - Break DirFetchPostPeriod into:
8980 - DirFetchPeriod for fetching full directory,
8981 - StatusFetchPeriod for fetching running-routers,
8982 - DirPostPeriod for posting server descriptor,
8983 - RendPostPeriod for posting hidden service descriptors.
8984 - New log format in config:
8985 "Log minsev[-maxsev] stdout|stderr|syslog" or
8986 "Log minsev[-maxsev] file /var/foo"
8987 - DirPolicy config option, to let people reject incoming addresses
8988 from their dirserver.
8989 - "tor --list-fingerprint" will list your identity key fingerprint
8991 - Make tor --version --version dump the cvs Id of every file.
8992 - New 'MyFamily nick1,...' config option for a server to
8993 specify other servers that shouldn't be used in the same circuit
8994 with it. Only believed if nick1 also specifies us.
8995 - New 'NodeFamily nick1,nick2,...' config option for a client to
8996 specify nodes that it doesn't want to use in the same circuit.
8997 - New 'Redirectexit pattern address:port' config option for a
8998 server to redirect exit connections, e.g. to a local squid.
8999 - Add "pass" target for RedirectExit, to make it easier to break
9000 out of a sequence of RedirectExit rules.
9001 - Make the dirservers file obsolete.
9002 - Include a dir-signing-key token in directories to tell the
9003 parsing entity which key is being used to sign.
9004 - Remove the built-in bulky default dirservers string.
9005 - New config option "Dirserver %s:%d [fingerprint]", which can be
9006 repeated as many times as needed. If no dirservers specified,
9007 default to moria1,moria2,tor26.
9008 - Make 'Routerfile' config option obsolete.
9009 - Discourage people from setting their dirfetchpostperiod more often
9010 than once per minute.
9013 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
9014 get back to normal.)
9015 - Accept *:706 (silc) in default exit policy.
9016 - Implement new versioning format for post 0.1.
9017 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
9018 log more informatively.
9019 - Check clock skew for verified servers, but allow unverified
9020 servers and clients to have any clock skew.
9021 - Make sure the hidden service descriptors are at a random offset
9022 from each other, to hinder linkability.
9023 - Clients now generate a TLS cert too, in preparation for having
9024 them act more like real nodes.
9025 - Add a pure-C tor-resolve implementation.
9026 - Use getrlimit and friends to ensure we can reach MaxConn (currently
9027 1024) file descriptors.
9028 - Raise the max dns workers from 50 to 100.
9031 Changes in version 0.0.8.1 - 2004-10-13
9033 - Fix a seg fault that can be triggered remotely for Tor
9034 clients/servers with an open dirport.
9035 - Fix a rare assert trigger, where routerinfos for entries in
9036 our cpath would expire while we're building the path.
9037 - Fix a bug in OutboundBindAddress so it (hopefully) works.
9038 - Fix a rare seg fault for people running hidden services on
9039 intermittent connections.
9040 - Fix a bug in parsing opt keywords with objects.
9041 - Fix a stale pointer assert bug when a stream detaches and
9043 - Fix a string format vulnerability (probably not exploitable)
9044 in reporting stats locally.
9045 - Fix an assert trigger: sometimes launching circuits can fail
9046 immediately, e.g. because too many circuits have failed recently.
9047 - Fix a compile warning on 64 bit platforms.
9050 Changes in version 0.0.8 - 2004-08-25
9052 - Made our unit tests compile again on OpenBSD 3.5, and tor
9053 itself compile again on OpenBSD on a sparc64.
9054 - We were neglecting milliseconds when logging on win32, so
9055 everything appeared to happen at the beginning of each second.
9056 - Check directory signature _before_ you decide whether you're
9057 you're running an obsolete version and should exit.
9058 - Check directory signature _before_ you parse the running-routers
9059 list to decide who's running.
9060 - Check return value of fclose while writing to disk, so we don't
9061 end up with broken files when servers run out of disk space.
9062 - Port it to SunOS 5.9 / Athena
9063 - Fix two bugs in saving onion keys to disk when rotating, so
9064 hopefully we'll get fewer people using old onion keys.
9065 - Remove our mostly unused -- and broken -- hex_encode()
9066 function. Use base16_encode() instead. (Thanks to Timo Lindfors
9067 for pointing out this bug.)
9068 - Only pick and establish intro points after we've gotten a
9070 - Fix assert triggers: if the other side returns an address 0.0.0.0,
9071 don't put it into the client dns cache.
9072 - If a begin failed due to exit policy, but we believe the IP
9073 address should have been allowed, switch that router to exitpolicy
9074 reject *:* until we get our next directory.
9077 - 'Extend' relay cell payloads now include the digest of the
9078 intended next hop's identity key. Now we can verify that we're
9079 extending to the right router, and also extend to routers we
9080 hadn't heard of before.
9083 - Tor nodes can now act as relays (with an advertised ORPort)
9084 without being manually verified by the dirserver operators.
9085 - Uploaded descriptors of unverified routers are now accepted
9086 by the dirservers, and included in the directory.
9087 - Verified routers are listed by nickname in the running-routers
9088 list; unverified routers are listed as "$<fingerprint>".
9089 - We now use hash-of-identity-key in most places rather than
9090 nickname or addr:port, for improved security/flexibility.
9091 - AllowUnverifiedNodes config option to let circuits choose no-name
9092 routers in entry,middle,exit,introduction,rendezvous positions.
9093 Allow middle and rendezvous positions by default.
9094 - When picking unverified routers, skip those with low uptime and/or
9095 low bandwidth, depending on what properties you care about.
9096 - ClientOnly option for nodes that never want to become servers.
9097 - Directory caching.
9098 - "AuthoritativeDir 1" option for the official dirservers.
9099 - Now other nodes (clients and servers) will cache the latest
9100 directory they've pulled down.
9101 - They can enable their DirPort to serve it to others.
9102 - Clients will pull down a directory from any node with an open
9103 DirPort, and check the signature/timestamp correctly.
9104 - Authoritative dirservers now fetch directories from other
9105 authdirservers, to stay better synced.
9106 - Running-routers list tells who's down also, along with noting
9107 if they're verified (listed by nickname) or unverified (listed
9109 - Allow dirservers to serve running-router list separately.
9110 This isn't used yet.
9111 - You can now fetch $DIRURL/running-routers to get just the
9112 running-routers line, not the whole descriptor list. (But
9113 clients don't use this yet.)
9114 - Clients choose nodes proportional to advertised bandwidth.
9115 - Clients avoid using nodes with low uptime as introduction points.
9116 - Handle servers with dynamic IP addresses: don't just replace
9117 options->Address with the resolved one at startup, and
9118 detect our address right before we make a routerinfo each time.
9119 - 'FascistFirewall' option to pick dirservers and ORs on specific
9120 ports; plus 'FirewallPorts' config option to tell FascistFirewall
9121 which ports are open. (Defaults to 80,443)
9122 - Try other dirservers immediately if the one you try is down. This
9123 should tolerate down dirservers better now.
9124 - ORs connect-on-demand to other ORs
9125 - If you get an extend cell to an OR you're not connected to,
9126 connect, handshake, and forward the create cell.
9127 - The authoritative dirservers stay connected to everybody,
9128 and everybody stays connected to 0.0.7 servers, but otherwise
9129 clients/servers expire unused connections after 5 minutes.
9130 - When servers get a sigint, they delay 30 seconds (refusing new
9131 connections) then exit. A second sigint causes immediate exit.
9132 - File and name management:
9133 - Look for .torrc if no CONFDIR "torrc" is found.
9134 - If no datadir is defined, then choose, make, and secure ~/.tor
9136 - If torrc not found, exitpolicy reject *:*.
9137 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
9138 - If no nickname is defined, derive default from hostname.
9139 - Rename secret key files, e.g. identity.key -> secret_id_key,
9140 to discourage people from mailing their identity key to tor-ops.
9141 - Refuse to build a circuit before the directory has arrived --
9142 it won't work anyway, since you won't know the right onion keys
9144 - Parse tor version numbers so we can do an is-newer-than check
9145 rather than an is-in-the-list check.
9146 - New socks command 'resolve', to let us shim gethostbyname()
9148 - A 'tor_resolve' script to access the socks resolve functionality.
9149 - A new socks-extensions.txt doc file to describe our
9150 interpretation and extensions to the socks protocols.
9151 - Add a ContactInfo option, which gets published in descriptor.
9152 - Write tor version at the top of each log file
9153 - New docs in the tarball:
9155 - Document that you should proxy your SSL traffic too.
9156 - Log a warning if the user uses an unsafe socks variant, so people
9157 are more likely to learn about privoxy or socat.
9158 - Log a warning if you're running an unverified server, to let you
9159 know you might want to get it verified.
9160 - Change the default exit policy to reject the default edonkey,
9161 kazaa, gnutella ports.
9162 - Add replace_file() to util.[ch] to handle win32's rename().
9163 - Publish OR uptime in descriptor (and thus in directory) too.
9164 - Remember used bandwidth (both in and out), and publish 15-minute
9165 snapshots for the past day into our descriptor.
9166 - Be more aggressive about trying to make circuits when the network
9167 has changed (e.g. when you unsuspend your laptop).
9168 - Check for time skew on http headers; report date in response to
9170 - If the entrynode config line has only one node, don't pick it as
9172 - Add strict{entry|exit}nodes config options. If set to 1, then
9173 we refuse to build circuits that don't include the specified entry
9175 - OutboundBindAddress config option, to bind to a specific
9176 IP address for outgoing connect()s.
9177 - End truncated log entries (e.g. directories) with "[truncated]".
9180 Changes in version 0.0.7.3 - 2004-08-12
9181 o Stop dnsworkers from triggering an assert failure when you
9182 ask them to resolve the host "".
9185 Changes in version 0.0.7.2 - 2004-07-07
9186 o A better fix for the 0.0.0.0 problem, that will hopefully
9187 eliminate the remaining related assertion failures.
9190 Changes in version 0.0.7.1 - 2004-07-04
9191 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
9192 since internally we use 0.0.0.0 to signify "not yet resolved".
9195 Changes in version 0.0.7 - 2004-06-07
9196 o Fixes for crashes and other obnoxious bugs:
9197 - Fix an epipe bug: sometimes when directory connections failed
9198 to connect, we would give them a chance to flush before closing
9200 - When we detached from a circuit because of resolvefailed, we
9201 would immediately try the same circuit twice more, and then
9202 give up on the resolve thinking we'd tried three different
9204 - Limit the number of intro circuits we'll attempt to build for a
9205 hidden service per 15-minute period.
9206 - Check recommended-software string *early*, before actually parsing
9207 the directory. Thus we can detect an obsolete version and exit,
9208 even if the new directory format doesn't parse.
9209 o Fixes for security bugs:
9210 - Remember which nodes are dirservers when you startup, and if a
9211 random OR enables his dirport, don't automatically assume he's
9212 a trusted dirserver.
9214 - Directory connections were asking the wrong poll socket to
9215 start writing, and not asking themselves to start writing.
9216 - When we detached from a circuit because we sent a begin but
9217 didn't get a connected, we would use it again the first time;
9218 but after that we would correctly switch to a different one.
9219 - Stop warning when the first onion decrypt attempt fails; they
9220 will sometimes legitimately fail now that we rotate keys.
9221 - Override unaligned-access-ok check when $host_cpu is ia64 or
9222 arm. Apparently they allow it but the kernel whines.
9223 - Dirservers try to reconnect periodically too, in case connections
9225 - Fix some memory leaks in directory servers.
9226 - Allow backslash in Win32 filenames.
9227 - Made Tor build complain-free on FreeBSD, hopefully without
9228 breaking other BSD builds. We'll see.
9229 - Check directory signatures based on name of signer, not on whom
9230 we got the directory from. This will let us cache directories more
9232 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
9235 - Doxygen markup on all functions and global variables.
9236 - Make directory functions update routerlist, not replace it. So
9237 now directory disagreements are not so critical a problem.
9238 - Remove the upper limit on number of descriptors in a dirserver's
9239 directory (not that we were anywhere close).
9240 - Allow multiple logfiles at different severity ranges.
9241 - Allow *BindAddress to specify ":port" rather than setting *Port
9242 separately. Allow multiple instances of each BindAddress config
9243 option, so you can bind to multiple interfaces if you want.
9244 - Allow multiple exit policy lines, which are processed in order.
9245 Now we don't need that huge line with all the commas in it.
9246 - Enable accept/reject policies on SOCKS connections, so you can bind
9247 to 0.0.0.0 but still control who can use your OP.
9248 - Updated the man page to reflect these features.
9251 Changes in version 0.0.6.2 - 2004-05-16
9252 o Our integrity-checking digest was checking only the most recent cell,
9253 not the previous cells like we'd thought.
9254 Thanks to Stefan Mark for finding the flaw!
9257 Changes in version 0.0.6.1 - 2004-05-06
9258 o Fix two bugs in our AES counter-mode implementation (this affected
9259 onion-level stream encryption, but not TLS-level). It turns
9260 out we were doing something much more akin to a 16-character
9261 polyalphabetic cipher. Oops.
9262 Thanks to Stefan Mark for finding the flaw!
9263 o Retire moria3 as a directory server, and add tor26 as a directory
9267 Changes in version 0.0.6 - 2004-05-02
9269 - Hidden services and rendezvous points are implemented. Go to
9270 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
9271 hidden services. (This only works via a socks4a proxy such as
9272 Privoxy, and currently it's quite slow.)
9273 - We now rotate link (tls context) keys and onion keys.
9274 - CREATE cells now include oaep padding, so you can tell
9275 if you decrypted them correctly.
9276 - Retry stream correctly when we fail to connect because of
9277 exit-policy-reject (should try another) or can't-resolve-address.
9278 - When we hup a dirserver and we've *removed* a server from the
9279 approved-routers list, now we remove that server from the
9280 in-memory directories too.
9281 - Add bandwidthburst to server descriptor.
9282 - Directories now say which dirserver signed them.
9283 - Use a tor_assert macro that logs failed assertions too.
9284 - Since we don't support truncateds much, don't bother sending them;
9285 just close the circ.
9286 - Fetch randomness from /dev/urandom better (not via fopen/fread)
9287 - Better debugging for tls errors
9288 - Set Content-Type on the directory and hidserv descriptor.
9289 - Remove IVs from cipher code, since AES-ctr has none.
9291 - Fix an assert trigger for exit nodes that's been plaguing us since
9292 the days of 0.0.2prexx (thanks weasel!)
9293 - Fix a bug where we were closing tls connections intermittently.
9294 It turns out openssl keeps its errors around -- so if an error
9295 happens, and you don't ask about it, and then another openssl
9296 operation happens and succeeds, and you ask if there was an error,
9297 it tells you about the first error.
9298 - Fix a bug that's been lurking since 27 may 03 (!)
9299 When passing back a destroy cell, we would use the wrong circ id.
9300 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
9301 - Some versions of openssl have an SSL_pending function that erroneously
9302 returns bytes when there is a non-application record pending.
9303 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
9304 o We were using an array of length zero in a few places.
9305 o Win32's gethostbyname can't resolve an IP to an IP.
9306 o Win32's close can't close a socket.
9307 o Handle windows socket errors correctly.
9309 - check for <sys/limits.h> so we build on FreeBSD again, and
9310 <machine/limits.h> for NetBSD.
9313 Changes in version 0.0.5 - 2004-03-30
9314 o Install torrc as torrc.sample -- we no longer clobber your
9316 o Fix mangled-state bug in directory fetching (was causing sigpipes).
9317 o Only build circuits after we've fetched the directory: clients were
9318 using only the directory servers before they'd fetched a directory.
9319 This also means longer startup time; so it goes.
9320 o Fix an assert trigger where an OP would fail to handshake, and we'd
9321 expect it to have a nickname.
9322 o Work around a tsocks bug: do a socks reject when AP connection dies
9323 early, else tsocks goes into an infinite loop.
9324 o Hold socks connection open until reply is flushed (if possible)
9325 o Make exit nodes resolve IPs to IPs immediately, rather than asking
9326 the dns farm to do it.
9327 o Fix c99 aliasing warnings in rephist.c
9328 o Don't include server descriptors that are older than 24 hours in the
9330 o Give socks 'reject' replies their whole 15s to attempt to flush,
9331 rather than seeing the 60s timeout and assuming the flush had failed.
9332 o Clean automake droppings from the cvs repository
9333 o Add in a 'notice' log level for things the operator should hear
9334 but that aren't warnings
9337 Changes in version 0.0.4 - 2004-03-26
9338 o When connecting to a dirserver or OR and the network is down,
9342 Changes in version 0.0.3 - 2004-03-26
9343 o Warn and fail if server chose a nickname with illegal characters
9344 o Port to Solaris and Sparc:
9345 - include missing header fcntl.h
9346 - have autoconf find -lsocket -lnsl automatically
9347 - deal with hardware word alignment
9348 - make uname() work (solaris has a different return convention)
9349 - switch from using signal() to sigaction()
9350 o Preliminary work on reputation system:
9351 - Keep statistics on success/fail of connect attempts; they're published
9352 by kill -USR1 currently.
9353 - Add a RunTesting option to try to learn link state by creating test
9354 circuits, even when SocksPort is off.
9355 - Remove unused open circuits when there are too many.
9358 Changes in version 0.0.2 - 2004-03-19
9359 - Include strlcpy and strlcat for safer string ops
9360 - define INADDR_NONE so we compile (but still not run) on solaris
9363 Changes in version 0.0.2pre27 - 2004-03-14
9365 - Allow internal tor networks (we were rejecting internal IPs,
9366 now we allow them if they're set explicitly).
9367 - And fix a few endian issues.
9370 Changes in version 0.0.2pre26 - 2004-03-14
9372 - If a stream times out after 15s without a connected cell, don't
9373 try that circuit again: try a new one.
9374 - Retry streams at most 4 times. Then give up.
9375 - When a dirserver gets a descriptor from an unknown router, it
9376 logs its fingerprint (so the dirserver operator can choose to
9377 accept it even without mail from the server operator).
9378 - Inform unapproved servers when we reject their descriptors.
9379 - Make tor build on Windows again. It works as a client, who knows
9381 - Clearer instructions in the torrc for how to set up a server.
9382 - Be more efficient about reading fd's when our global token bucket
9383 (used for rate limiting) becomes empty.
9385 - Stop asserting that computers always go forward in time. It's
9387 - When we sent a cell (e.g. destroy) and then marked an OR connection
9388 expired, we might close it before finishing a flush if the other
9389 side isn't reading right then.
9390 - Don't allow dirservers to start if they haven't defined
9392 - We were caching transient dns failures. Oops.
9393 - Prevent servers from publishing an internal IP as their address.
9394 - Address a strcat vulnerability in circuit.c
9397 Changes in version 0.0.2pre25 - 2004-03-04
9399 - Put the OR's IP in its router descriptor, not its fqdn. That way
9400 we'll stop being stalled by gethostbyname for nodes with flaky dns,
9403 - If the user typed in an address that didn't resolve, the server
9407 Changes in version 0.0.2pre24 - 2004-03-03
9409 - Fix an assertion failure in dns.c, where we were trying to dequeue
9410 a pending dns resolve even if it wasn't pending
9411 - Fix a spurious socks5 warning about still trying to write after the
9412 connection is finished.
9413 - Hold certain marked_for_close connections open until they're finished
9414 flushing, rather than losing bytes by closing them too early.
9415 - Correctly report the reason for ending a stream
9416 - Remove some duplicate calls to connection_mark_for_close
9417 - Put switch_id and start_daemon earlier in the boot sequence, so it
9418 will actually try to chdir() to options.DataDirectory
9419 - Make 'make test' exit(1) if a test fails; fix some unit tests
9420 - Make tor fail when you use a config option it doesn't know about,
9421 rather than warn and continue.
9422 - Make --version work
9423 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
9426 Changes in version 0.0.2pre23 - 2004-02-29
9428 - Print a statement when the first circ is finished, so the user
9430 - If a relay cell is unrecognized at the end of the circuit,
9431 send back a destroy. (So attacks to mutate cells are more
9433 - New config option 'excludenodes' to avoid certain nodes for circuits.
9434 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
9435 so you can collect coredumps there.
9437 - Fix a bug in tls flushing where sometimes data got wedged and
9438 didn't flush until more data got sent. Hopefully this bug was
9439 a big factor in the random delays we were seeing.
9440 - Make 'connected' cells include the resolved IP, so the client
9441 dns cache actually gets populated.
9442 - Disallow changing from ORPort=0 to ORPort>0 on hup.
9443 - When we time-out on a stream and detach from the circuit, send an
9444 end cell down it first.
9445 - Only warn about an unknown router (in exitnodes, entrynodes,
9446 excludenodes) after we've fetched a directory.
9449 Changes in version 0.0.2pre22 - 2004-02-26
9451 - Servers publish less revealing uname information in descriptors.
9452 - More memory tracking and assertions, to crash more usefully when
9454 - If the default torrc isn't there, just use some default defaults.
9455 Plus provide an internal dirservers file if they don't have one.
9456 - When the user tries to use Tor as an http proxy, give them an http
9457 501 failure explaining that we're a socks proxy.
9458 - Dump a new router.desc on hup, to help confused people who change
9459 their exit policies and then wonder why router.desc doesn't reflect
9461 - Clean up the generic tor.sh init script that we ship with.
9463 - If the exit stream is pending on the resolve, and a destroy arrives,
9464 then the stream wasn't getting removed from the pending list. I
9465 think this was the one causing recent server crashes.
9466 - Use a more robust poll on OSX 10.3, since their poll is flaky.
9467 - When it couldn't resolve any dirservers, it was useless from then on.
9468 Now it reloads the RouterFile (or default dirservers) if it has no
9470 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
9471 many users don't even *have* a /usr/local/sbin/.
9474 Changes in version 0.0.2pre21 - 2004-02-18
9476 - There's a ChangeLog file that actually reflects the changelog.
9477 - There's a 'torify' wrapper script, with an accompanying
9478 tor-tsocks.conf, that simplifies the process of using tsocks for
9479 tor. It even has a man page.
9480 - The tor binary gets installed to sbin rather than bin now.
9481 - Retry streams where the connected cell hasn't arrived in 15 seconds
9482 - Clean up exit policy handling -- get the default out of the torrc,
9483 so we can update it without forcing each server operator to fix
9485 - Allow imaps and pop3s in default exit policy
9487 - Prevent picking middleman nodes as the last node in the circuit
9490 Changes in version 0.0.2pre20 - 2004-01-30
9492 - We now have a deb package, and it's in debian unstable. Go to
9494 - I've split the TotalBandwidth option into BandwidthRate (how many
9495 bytes per second you want to allow, long-term) and
9496 BandwidthBurst (how many bytes you will allow at once before the cap
9497 kicks in). This better token bucket approach lets you, say, set
9498 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
9499 performance while not exceeding your monthly bandwidth quota.
9500 - Push out a tls record's worth of data once you've got it, rather
9501 than waiting until you've read everything waiting to be read. This
9502 may improve performance by pipelining better. We'll see.
9503 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
9504 from failed circuits (if they haven't been connected yet) and attach
9506 - Expire old streams that haven't managed to connect. Some day we'll
9507 have them reattach to new circuits instead.
9510 - Fix several memory leaks that were causing servers to become bloated
9512 - Fix a few very rare assert triggers. A few more remain.
9513 - Setuid to User _before_ complaining about running as root.
9516 Changes in version 0.0.2pre19 - 2004-01-07
9518 - Fix deadlock condition in dns farm. We were telling a child to die by
9519 closing the parent's file descriptor to him. But newer children were
9520 inheriting the open file descriptor from the parent, and since they
9521 weren't closing it, the socket never closed, so the child never read
9522 eof, so he never knew to exit. Similarly, dns workers were holding
9523 open other sockets, leading to all sorts of chaos.
9524 - New cleaner daemon() code for forking and backgrounding.
9525 - If you log to a file, it now prints an entry at the top of the
9526 logfile so you know it's working.
9527 - The onionskin challenge length was 30 bytes longer than necessary.
9528 - Started to patch up the spec so it's not quite so out of date.
9531 Changes in version 0.0.2pre18 - 2004-01-02
9533 - Fix endian issues with the 'integrity' field in the relay header.
9534 - Fix a potential bug where connections in state
9535 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
9538 Changes in version 0.0.2pre17 - 2003-12-30
9540 - Made --debuglogfile (or any second log file, actually) work.
9541 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
9542 adversary could force us into an infinite loop.
9545 - Each onionskin handshake now includes a hash of the computed key,
9546 to prove the server's identity and help perfect forward secrecy.
9547 - Changed cell size from 256 to 512 bytes (working toward compatibility
9549 - Changed cell length to 2 bytes, and moved it to the relay header.
9550 - Implemented end-to-end integrity checking for the payloads of
9552 - Separated streamid from 'recognized' (otherwise circuits will get
9553 messed up when we try to have streams exit from the middle). We
9554 use the integrity-checking to confirm that a cell is addressed to
9556 - Randomize the initial circid and streamid values, so an adversary who
9557 breaks into a node can't learn how many circuits or streams have
9561 Changes in version 0.0.2pre16 - 2003-12-14
9563 - Fixed a bug that made HUP trigger an assert
9564 - Fixed a bug where a circuit that immediately failed wasn't being
9565 counted as a failed circuit in counting retries.
9568 - Now we close the circuit when we get a truncated cell: otherwise we're
9569 open to an anonymity attack where a bad node in the path truncates
9570 the circuit and then we open streams at him.
9571 - Add port ranges to exit policies
9572 - Add a conservative default exit policy
9573 - Warn if you're running tor as root
9574 - on HUP, retry OR connections and close/rebind listeners
9575 - options.EntryNodes: try these nodes first when picking the first node
9576 - options.ExitNodes: if your best choices happen to include any of
9577 your preferred exit nodes, you choose among just those preferred
9579 - options.ExcludedNodes: nodes that are never picked in path building
9582 Changes in version 0.0.2pre15 - 2003-12-03
9583 o Robustness and bugfixes:
9584 - Sometimes clients would cache incorrect DNS resolves, which would
9585 really screw things up.
9586 - An OP that goes offline would slowly leak all its sockets and stop
9588 - A wide variety of bugfixes in exit node selection, exit policy
9589 handling, and processing pending streams when a new circuit is
9591 - Pick nodes for a path only from those the directory says are up
9592 - Choose randomly from all running dirservers, not always the first one
9593 - Increase allowed http header size for directory fetch.
9594 - Stop writing to stderr (if we're daemonized it will be closed).
9595 - Enable -g always, so cores will be more useful to me.
9596 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
9599 - Wrote a man page. It lists commonly used options.
9602 - Change default loglevel to warn.
9603 - Make PidFile default to null rather than littering in your CWD.
9604 - OnionRouter config option is now obsolete. Instead it just checks
9606 - Moved to a single unified torrc file for both clients and servers.
9609 Changes in version 0.0.2pre14 - 2003-11-29
9610 o Robustness and bugfixes:
9611 - Force the admin to make the DataDirectory himself
9612 - to get ownership/permissions right
9613 - so clients no longer make a DataDirectory and then never use it
9614 - fix bug where a client who was offline for 45 minutes would never
9615 pull down a directory again
9616 - fix (or at least hide really well) the dns assert bug that was
9617 causing server crashes
9618 - warnings and improved robustness wrt clockskew for certs
9619 - use the native daemon(3) to daemonize, when available
9620 - exit if bind() fails
9621 - exit if neither socksport nor orport is defined
9622 - include our own tor_timegm (Win32 doesn't have its own)
9623 - bugfix for win32 with lots of connections
9624 - fix minor bias in PRNG
9625 - make dirserver more robust to corrupt cached directory
9628 - Wrote the design document (woo)
9630 o Circuit building and exit policies:
9631 - Circuits no longer try to use nodes that the directory has told them
9633 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
9634 bitcounts (18.0.0.0/8).
9635 - Make AP connections standby for a circuit if no suitable circuit
9636 exists, rather than failing
9637 - Circuits choose exit node based on addr/port, exit policies, and
9638 which AP connections are standing by
9639 - Bump min pathlen from 2 to 3
9640 - Relay end cells have a payload to describe why the stream ended.
9641 - If the stream failed because of exit policy, try again with a new
9643 - Clients have a dns cache to remember resolved addresses.
9644 - Notice more quickly when we have no working circuits
9647 - APPort is now called SocksPort
9648 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
9650 - RecommendedVersions is now a config variable rather than
9651 hardcoded (for dirservers)
9652 - Reloads config on HUP
9653 - Usage info on -h or --help
9654 - If you set User and Group config vars, it'll setu/gid to them.
9656 Changes in version 0.0.2pre13 - 2003-10-19
9657 o General stability:
9658 - SSL_write no longer fails when it returns WANTWRITE and the number
9659 of bytes in the buf has changed by the next SSL_write call.
9660 - Fix segfault fetching directory when network is down
9661 - Fix a variety of minor memory leaks
9662 - Dirservers reload the fingerprints file on HUP, so I don't have
9663 to take down the network when I approve a new router
9664 - Default server config file has explicit Address line to specify fqdn
9667 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9668 - Make listener connections not ever alloc bufs
9670 o Autoconf improvements:
9671 - don't clobber an external CFLAGS in ./configure
9672 - Make install now works
9673 - create var/lib/tor on make install
9674 - autocreate a tor.sh initscript to help distribs
9675 - autocreate the torrc and sample-server-torrc with correct paths
9677 o Log files and Daemonizing now work:
9678 - If --DebugLogFile is specified, log to it at -l debug
9679 - If --LogFile is specified, use it instead of commandline
9680 - If --RunAsDaemon is set, tor forks and backgrounds on startup