1 Changes in version 0.3.1.4-alpha - 2017-06-29
2 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
3 to use a guard that was in the same network family as a chosen exit
4 relay. This is a security regression; all clients running earlier
5 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
8 This release also fixes several other bugs introduced in 0.3.0.x
9 and 0.3.1.x, including others that can affect bandwidth usage
13 - To build with zstd and lzma support, Tor now requires the
14 pkg-config tool at build time. (This requirement was new in
15 0.3.1.1-alpha, but was not noted at the time. Noting it here to
18 o Major bugfixes (path selection, security):
19 - When choosing which guard to use for a circuit, avoid the exit's
20 family along with the exit itself. Previously, the new guard
21 selection logic avoided the exit, but did not consider its family.
22 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2016-
23 006 and CVE-2017-0377.
25 o Major bugfixes (compression, zstd):
26 - Correctly detect a full buffer when decompressing a large zstd-
27 compressed input. Previously, we would sometimes treat a full
28 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
30 o Major bugfixes (directory protocol):
31 - Ensure that we send "304 Not modified" as HTTP status code when a
32 client is attempting to fetch a consensus or consensus diff, and
33 the best one we can send them is one they already have. Fixes bug
34 22702; bugfix on 0.3.1.1-alpha.
36 o Major bugfixes (entry guards):
37 - When starting with an old consensus, do not add new entry guards
38 unless the consensus is "reasonably live" (under 1 day old). Fixes
39 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
41 o Minor features (bug mitigation, diagnostics, logging):
42 - Avoid an assertion failure, and log a better error message, when
43 unable to remove a file from the consensus cache on Windows.
44 Attempts to mitigate and diagnose bug 22752.
46 o Minor features (geoip):
47 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
50 o Minor bugfixes (compression):
51 - When compressing or decompressing a buffer, check for a failure to
52 create a compression object. Fixes bug 22626; bugfix
54 - When decompressing a buffer, check for extra data after the end of
55 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
56 - When decompressing an object received over an anonymous directory
57 connection, if we have already decompressed it using an acceptable
58 compression method, do not reject it for looking like an
59 unacceptable compression method. Fixes part of bug 22670; bugfix
61 - When serving directory votes compressed with zlib, do not claim to
62 have compressed them with zstd. Fixes bug 22669; bugfix
64 - When spooling compressed data to an output buffer, don't try to
65 spool more data when there is no more data to spool and we are not
66 trying to flush the input. Previously, we would sometimes launch
67 compression requests with nothing to do, which interferes with our
68 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
70 o Minor bugfixes (defensive programming):
71 - Detect and break out of infinite loops in our compression code. We
72 don't think that any such loops exist now, but it's best to be
73 safe. Closes ticket 22672.
74 - Fix a memset() off the end of an array when packing cells. This
75 bug should be harmless in practice, since the corrupted bytes are
76 still in the same structure, and are always padding bytes,
77 ignored, or immediately overwritten, depending on compiler
78 behavior. Nevertheless, because the memset()'s purpose is to make
79 sure that any other cell-handling bugs can't expose bytes to the
80 network, we need to fix it. Fixes bug 22737; bugfix on
81 0.2.4.11-alpha. Fixes CID 1401591.
83 o Minor bugfixes (linux seccomp2 sandbox):
84 - Permit the fchmod system call, to avoid crashing on startup when
85 starting with the seccomp2 sandbox and an unexpected set of
86 permissions on the data directory or its contents. Fixes bug
87 22516; bugfix on 0.2.5.4-alpha.
88 - Fix a crash in the LZMA module, when the sandbox was enabled, and
89 liblzma would allocate more than 16 MB of memory. We solve this by
90 bumping the mprotect() limit in the sandbox module from 16 MB to
91 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
93 o Minor bugfixes (logging):
94 - When decompressing, do not warn if we fail to decompress using a
95 compression method that we merely guessed. Fixes part of bug
96 22670; bugfix on 0.1.1.14-alpha.
97 - When decompressing, treat mismatch between content-encoding and
98 actual compression type as a protocol warning. Fixes part of bug
99 22670; bugfix on 0.1.1.9-alpha.
100 - Downgrade "assigned_to_cpuworker failed" message to info-level
101 severity. In every case that can reach it, either a better warning
102 has already been logged, or no warning is warranted. Fixes bug
103 22356; bugfix on 0.2.6.3-alpha.
104 - Demote a warn that was caused by libevent delays to info if
105 netflow padding is less than 4.5 seconds late, or to notice
106 if it is more (4.5 seconds is the amount of time that a netflow
107 record might be emitted after, if we chose the maximum timeout).
108 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
110 o Minor bugfixes (process behavior):
111 - When exiting because of an error, always exit with a nonzero exit
112 status. Previously, we would fail to report an error in our exit
113 status in cases related to __OwningControllerProcess failure,
114 lockfile contention, and Ed25519 key initialization. Fixes bug
115 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
116 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
120 - Add a manpage description for the key-pinning-journal file. Closes
122 - Correctly note that bandwidth accounting values are stored in the
123 state file, and the bw_accounting file is now obsolete. Closes
125 - Document more of the files in the Tor data directory, including
126 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
127 approved-routers, sr-random, and diff-cache. Found while fixing
131 Changes in version 0.3.0.9 - 2017-06-29
132 Tor 0.3.0.9 fixes a path selection bug that would allow a client
133 to use a guard that was in the same network family as a chosen exit
134 relay. This is a security regression; all clients running earlier
135 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
138 This release also backports several other bugfixes from the 0.3.1.x
141 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
142 - When choosing which guard to use for a circuit, avoid the exit's
143 family along with the exit itself. Previously, the new guard
144 selection logic avoided the exit, but did not consider its family.
145 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2016-
146 006 and CVE-2017-0377.
148 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
149 - Don't block bootstrapping when a primary bridge is offline and we
150 can't get its descriptor. Fixes bug 22325; fixes one case of bug
151 21969; bugfix on 0.3.0.3-alpha.
153 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
154 - When starting with an old consensus, do not add new entry guards
155 unless the consensus is "reasonably live" (under 1 day old). Fixes
156 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
158 o Minor features (geoip):
159 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
162 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
163 - Reject version numbers with non-numeric prefixes (such as +, -, or
164 whitespace). Disallowing whitespace prevents differential version
165 parsing between POSIX-based and Windows platforms. Fixes bug 21507
166 and part of 21508; bugfix on 0.0.8pre1.
168 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
169 - Permit the fchmod system call, to avoid crashing on startup when
170 starting with the seccomp2 sandbox and an unexpected set of
171 permissions on the data directory or its contents. Fixes bug
172 22516; bugfix on 0.2.5.4-alpha.
174 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
175 - Fix a memset() off the end of an array when packing cells. This
176 bug should be harmless in practice, since the corrupted bytes are
177 still in the same structure, and are always padding bytes,
178 ignored, or immediately overwritten, depending on compiler
179 behavior. Nevertheless, because the memset()'s purpose is to make
180 sure that any other cell-handling bugs can't expose bytes to the
181 network, we need to fix it. Fixes bug 22737; bugfix on
182 0.2.4.11-alpha. Fixes CID 1401591.
185 Changes in version 0.3.1.3-alpha - 2017-06-08
186 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
187 remotely crash a hidden service with an assertion failure. Anyone
188 running a hidden service should upgrade to this version, or to some
189 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
191 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
192 that sometimes made relays unreliable, as well as several other
193 bugfixes described below.
195 o Major bugfixes (hidden service, relay, security):
196 - Fix a remotely triggerable assertion failure when a hidden service
197 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
198 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
199 - Fix a remotely triggerable assertion failure caused by receiving a
200 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
201 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
204 o Major bugfixes (relay, link handshake):
205 - When performing the v3 link handshake on a TLS connection, report
206 that we have the x509 certificate that we actually used on that
207 connection, even if we have changed certificates since that
208 connection was first opened. Previously, we would claim to have
209 used our most recent x509 link certificate, which would sometimes
210 make the link handshake fail. Fixes one case of bug 22460; bugfix
213 o Major bugfixes (relays, key management):
214 - Regenerate link and authentication certificates whenever the key
215 that signs them changes; also, regenerate link certificates
216 whenever the signed key changes. Previously, these processes were
217 only weakly coupled, and we relays could (for minutes to hours)
218 wind up with an inconsistent set of keys and certificates, which
219 other relays would not accept. Fixes two cases of bug 22460;
220 bugfix on 0.3.0.1-alpha.
221 - When sending an Ed25519 signing->link certificate in a CERTS cell,
222 send the certificate that matches the x509 certificate that we
223 used on the TLS connection. Previously, there was a race condition
224 if the TLS context rotated after we began the TLS handshake but
225 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
228 o Major bugfixes (torrc, crash):
229 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
230 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
232 o Minor features (code style):
233 - Add "Falls through" comments to our codebase, in order to silence
234 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
235 Stieger. Closes ticket 22446.
237 o Minor features (diagnostic):
238 - Add logging messages to try to diagnose a rare bug that seems to
239 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
240 think this is happening because of incorrect system clocks, but
241 we'd like to know for certain. Diagnostic for bug 22466.
243 o Minor bugfixes (correctness):
244 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
245 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
247 o Minor bugfixes (directory protocol):
248 - Check for libzstd >= 1.1, because older versions lack the
249 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
251 o Minor bugfixes (link handshake):
252 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
253 months, and regenerate it when it is within one month of expiring.
254 Previously, we had generated this certificate at startup with a
255 ten-year lifetime, but that could lead to weird behavior when Tor
256 was started with a grossly inaccurate clock. Mitigates bug 22466;
257 mitigation on 0.3.0.1-alpha.
259 o Minor bugfixes (storage directories):
260 - Always check for underflows in the cached storage directory usage.
261 If the usage does underflow, re-calculate it. Also, avoid a
262 separate underflow when the usage is not known. Fixes bug 22424;
263 bugfix on 0.3.1.1-alpha.
265 o Minor bugfixes (unit tests):
266 - The unit tests now pass on systems where localhost is misconfigured
267 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
271 - Clarify the manpage for the (deprecated) torify script. Closes
274 Changes in version 0.3.0.8 - 2017-06-08
275 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
276 remotely crash a hidden service with an assertion failure. Anyone
277 running a hidden service should upgrade to this version, or to some
278 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
280 Tor 0.3.0.8 also includes fixes for several key management bugs
281 that sometimes made relays unreliable, as well as several other
282 bugfixes described below.
284 o Major bugfixes (hidden service, relay, security, backport
286 - Fix a remotely triggerable assertion failure when a hidden service
287 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
288 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
289 - Fix a remotely triggerable assertion failure caused by receiving a
290 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
291 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
294 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
295 - When performing the v3 link handshake on a TLS connection, report
296 that we have the x509 certificate that we actually used on that
297 connection, even if we have changed certificates since that
298 connection was first opened. Previously, we would claim to have
299 used our most recent x509 link certificate, which would sometimes
300 make the link handshake fail. Fixes one case of bug 22460; bugfix
303 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
304 - Regenerate link and authentication certificates whenever the key
305 that signs them changes; also, regenerate link certificates
306 whenever the signed key changes. Previously, these processes were
307 only weakly coupled, and we relays could (for minutes to hours)
308 wind up with an inconsistent set of keys and certificates, which
309 other relays would not accept. Fixes two cases of bug 22460;
310 bugfix on 0.3.0.1-alpha.
311 - When sending an Ed25519 signing->link certificate in a CERTS cell,
312 send the certificate that matches the x509 certificate that we
313 used on the TLS connection. Previously, there was a race condition
314 if the TLS context rotated after we began the TLS handshake but
315 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
318 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
319 - Stop rejecting v3 hidden service descriptors because their size
320 did not match an old padding rule. Fixes bug 22447; bugfix on
323 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
324 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
325 December 2016 (of which ~126 were still functional) with a list of
326 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
327 2017. Resolves ticket 21564.
329 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
330 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
331 bug 22252; bugfix on 0.2.9.3-alpha.
333 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
334 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
335 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
337 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
338 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
339 months, and regenerate it when it is within one month of expiring.
340 Previously, we had generated this certificate at startup with a
341 ten-year lifetime, but that could lead to weird behavior when Tor
342 was started with a grossly inaccurate clock. Mitigates bug 22466;
343 mitigation on 0.3.0.1-alpha.
345 o Minor bugfixes (memory leak, directory authority, backport from
347 - When directory authorities reject a router descriptor due to
348 keypinning, free the router descriptor rather than leaking the
349 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
352 Changes in version 0.2.9.11 - 2017-06-08
353 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
354 remotely crash a hidden service with an assertion failure. Anyone
355 running a hidden service should upgrade to this version, or to some
356 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
357 are not affected by TROVE-2017-004.)
359 Tor 0.2.9.11 also backports fixes for several key management bugs
360 that sometimes made relays unreliable, as well as several other
361 bugfixes described below.
363 o Major bugfixes (hidden service, relay, security, backport
365 - Fix a remotely triggerable assertion failure caused by receiving a
366 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
367 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
370 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
371 - When performing the v3 link handshake on a TLS connection, report
372 that we have the x509 certificate that we actually used on that
373 connection, even if we have changed certificates since that
374 connection was first opened. Previously, we would claim to have
375 used our most recent x509 link certificate, which would sometimes
376 make the link handshake fail. Fixes one case of bug 22460; bugfix
379 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
380 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
381 December 2016 (of which ~126 were still functional) with a list of
382 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
383 2017. Resolves ticket 21564.
385 o Minor features (future-proofing, backport from 0.3.0.7):
386 - Tor no longer refuses to download microdescriptors or descriptors if
387 they are listed as "published in the future". This change will
388 eventually allow us to stop listing meaningful "published" dates
389 in microdescriptor consensuses, and thereby allow us to reduce the
390 resources required to download consensus diffs by over 50%.
391 Implements part of ticket 21642; implements part of proposal 275.
393 o Minor features (directory authorities, backport from 0.3.0.4-rc)
394 - Directory authorities now reject relays running versions
395 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
396 suffer from bug 20499 and don't keep their consensus cache
397 up-to-date. Resolves ticket 20509.
399 o Minor features (geoip):
400 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
403 o Minor bugfixes (control port, backport from 0.3.0.6):
404 - The GETINFO extra-info/digest/<digest> command was broken because
405 of a wrong base16 decode return value check, introduced when
406 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
408 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
409 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
410 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
412 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
413 - The getpid() system call is now permitted under the Linux seccomp2
414 sandbox, to avoid crashing with versions of OpenSSL (and other
415 libraries) that attempt to learn the process's PID by using the
416 syscall rather than the VDSO code. Fixes bug 21943; bugfix
419 o Minor bugfixes (memory leak, directory authority, backport
421 - When directory authorities reject a router descriptor due to
422 keypinning, free the router descriptor rather than leaking the
423 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
425 Changes in version 0.2.8.14 - 2017-06-08
426 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
427 remotely crash a hidden service with an assertion failure. Anyone
428 running a hidden service should upgrade to this version, or to some
429 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
430 are not affected by TROVE-2017-004.)
432 o Major bugfixes (hidden service, relay, security):
433 - Fix a remotely triggerable assertion failure caused by receiving a
434 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
435 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
438 o Minor features (geoip):
439 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
442 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
443 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
444 December 2016 (of which ~126 were still functional) with a list of
445 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
446 2017. Resolves ticket 21564.
448 o Minor bugfixes (correctness):
449 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
450 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
452 Changes in version 0.2.7.8 - 2017-06-08
453 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
454 remotely crash a hidden service with an assertion failure. Anyone
455 running a hidden service should upgrade to this version, or to some
456 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
457 are not affected by TROVE-2017-004.)
459 o Major bugfixes (hidden service, relay, security):
460 - Fix a remotely triggerable assertion failure caused by receiving a
461 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
462 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
465 o Minor features (geoip):
466 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
469 o Minor bugfixes (correctness):
470 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
471 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
474 Changes in version 0.2.6.12 - 2017-06-08
475 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
476 remotely crash a hidden service with an assertion failure. Anyone
477 running a hidden service should upgrade to this version, or to some
478 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
479 are not affected by TROVE-2017-004.)
481 o Major bugfixes (hidden service, relay, security):
482 - Fix a remotely triggerable assertion failure caused by receiving a
483 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
484 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
487 o Minor features (geoip):
488 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
491 o Minor bugfixes (correctness):
492 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
493 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
495 Changes in version 0.2.5.14 - 2017-06-08
496 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
497 remotely crash a hidden service with an assertion failure. Anyone
498 running a hidden service should upgrade to this version, or to some
499 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
500 are not affected by TROVE-2017-004.)
502 o Major bugfixes (hidden service, relay, security):
503 - Fix a remotely triggerable assertion failure caused by receiving a
504 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
505 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
508 o Minor features (geoip):
509 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
512 o Minor bugfixes (correctness):
513 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
514 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
516 Changes in version 0.2.4.29 - 2017-06-08
517 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
518 remotely crash a hidden service with an assertion failure. Anyone
519 running a hidden service should upgrade to this version, or to some
520 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
521 are not affected by TROVE-2017-004.)
523 o Major bugfixes (hidden service, relay, security):
524 - Fix a remotely triggerable assertion failure caused by receiving a
525 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
526 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
529 o Minor features (geoip):
530 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
533 o Minor bugfixes (correctness):
534 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
535 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
538 Changes in version 0.3.1.2-alpha - 2017-05-26
539 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
540 fixes a few bugs found while testing 0.3.1.1-alpha, including a
541 memory corruption bug that affected relay stability.
543 o Major bugfixes (crash, relay):
544 - Fix a memory-corruption bug in relays that set MyFamily.
545 Previously, they would double-free MyFamily elements when making
546 the next descriptor or when changing their configuration. Fixes
547 bug 22368; bugfix on 0.3.1.1-alpha.
549 o Minor bugfixes (logging):
550 - Log a better message when a directory authority replies to an
551 upload with an unexpected status code. Fixes bug 11121; bugfix
554 o Minor bugfixes (memory leak, directory authority):
555 - When directory authorities reject a router descriptor due to
556 keypinning, free the router descriptor rather than leaking the
557 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
560 Changes in version 0.3.1.1-alpha - 2017-05-22
561 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
562 reduces the bandwidth usage for Tor's directory protocol, adds some
563 basic padding to resist netflow-based traffic analysis and to serve as
564 the basis of other padding in the future, and adds rust support to the
567 It also contains numerous other small features and improvements to
568 security, correctness, and performance.
570 Below are the changes since 0.3.0.7.
572 o Major features (directory protocol):
573 - Tor relays and authorities can now serve clients an abbreviated
574 version of the consensus document, containing only the changes
575 since an older consensus document that the client holds. Clients
576 now request these documents when available. When both client and
577 server use this new protocol, they will use far less bandwidth (up
578 to 94% less) to keep the client's consensus up-to-date. Implements
579 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
580 - Tor can now compress directory traffic with lzma or with zstd
581 compression algorithms, which can deliver better bandwidth
582 performance. Because lzma is computationally expensive, it's only
583 used for documents that can be compressed once and served many
584 times. Support for these algorithms requires that tor is built
585 with the libzstd and/or liblzma libraries available. Implements
586 proposal 278; closes ticket 21662.
587 - Relays now perform the more expensive compression operations, and
588 consensus diff generation, in worker threads. This separation
589 avoids delaying the main thread when a new consensus arrives.
591 o Major features (experimental):
592 - Tor can now build modules written in Rust. To turn this on, pass
593 the "--enable-rust" flag to the configure script. It's not time to
594 get excited yet: currently, there is no actual Rust functionality
595 beyond some simple glue code, and a notice at startup to tell you
596 that Rust is running. Still, we hope that programmers and
597 packagers will try building Tor with Rust support, so that we can
598 find issues and solve portability problems. Closes ticket 22106.
600 o Major features (traffic analysis resistance):
601 - Connections between clients and relays now send a padding cell in
602 each direction every 1.5 to 9.5 seconds (tunable via consensus
603 parameters). This padding will not resist specialized
604 eavesdroppers, but it should be enough to make many ISPs' routine
605 network flow logging less useful in traffic analysis against
608 Padding is negotiated using Tor's link protocol, so both relays
609 and clients must upgrade for this to take effect. Clients may
610 still send padding despite the relay's version by setting
611 ConnectionPadding 1 in torrc, and may disable padding by setting
612 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
613 users with the torrc option ReducedConnectionPadding. Implements
614 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
615 - Relays will publish 24 hour totals of padding and non-padding cell
616 counts to their extra-info descriptors, unless PaddingStatistics 0
617 is set in torrc. These 24 hour totals are also rounded to
620 o Major bugfixes (connection usage):
621 - We use NETINFO cells to try to determine if both relays involved
622 in a connection will agree on the canonical status of that
623 connection. We prefer the connections where this is the case for
624 extend cells, and try to close connections where relays disagree
625 on their canonical status early. Also, we now prefer the oldest
626 valid connection for extend cells. These two changes should reduce
627 the number of long-term connections that are kept open between
628 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
629 - Relays now log hourly statistics (look for
630 "channel_check_for_duplicates" lines) on the total number of
631 connections to other relays. If the number of connections per
632 relay is unexpectedly large, this log message is at notice level.
633 Otherwise it is at info.
635 o Major bugfixes (entry guards):
636 - Don't block bootstrapping when a primary bridge is offline and we
637 can't get its descriptor. Fixes bug 22325; fixes one case of bug
638 21969; bugfix on 0.3.0.3-alpha.
640 o Major bugfixes (linux TPROXY support):
641 - Fix a typo that had prevented TPROXY-based transparent proxying
642 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
643 Patch from "d4fq0fQAgoJ".
645 o Minor features (security, windows):
646 - Enable a couple of pieces of Windows hardening: one
647 (HeapEnableTerminationOnCorruption) that has been on-by-default
648 since Windows 8, and unavailable before Windows 7; and one
649 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
650 affect us, but shouldn't do any harm. Closes ticket 21953.
652 o Minor features (config options):
653 - Allow "%include" directives in torrc configuration files. These
654 directives import the settings from other files, or from all the
655 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
656 - Make SAVECONF return an error when overwriting a torrc that has
657 includes. Using SAVECONF with the FORCE option will allow it to
658 overwrite torrc even if includes are used. Related to ticket 1922.
659 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
660 will work without the FORCE option. Related to ticket 1922.
662 o Minor features (controller):
663 - Warn the first time that a controller requests data in the long-
664 deprecated 'GETINFO network-status' format. Closes ticket 21703.
666 o Minor features (defaults):
667 - The default value for UseCreateFast is now 0: clients which
668 haven't yet received a consensus document will now use a proper
669 ntor handshake to talk to their directory servers whenever they
670 can. Closes ticket 21407.
671 - Onion key rotation and expiry intervals are now defined as a
672 network consensus parameter, per proposal 274. The default
673 lifetime of an onion key is increased from 7 to 28 days. Old onion
674 keys will expire after 7 days by default. This change will make
675 consensus diffs much smaller, and save significant bandwidth.
678 o Minor features (fallback directory list):
679 - Update the fallback directory mirror whitelist and blacklist based
680 on operator emails. Closes task 21121.
681 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
682 December 2016 (of which ~126 were still functional) with a list of
683 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
684 2017. Resolves ticket 21564.
686 o Minor features (hidden services, logging):
687 - Log a message when a hidden service descriptor has fewer
688 introduction points than specified in
689 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
690 - Log a message when a hidden service reaches its introduction point
691 circuit limit, and when that limit is reset. Follow up to ticket
692 21594; closes ticket 21622.
693 - Warn user if multiple entries in EntryNodes and at least one
694 HiddenService are used together. Pinning EntryNodes along with a
695 hidden service can be possibly harmful; for instance see ticket
696 14917 or 21155. Closes ticket 21155.
698 o Minor features (linux seccomp2 sandbox):
699 - We now have a document storage backend compatible with the Linux
700 seccomp2 sandbox. This backend is used for consensus documents and
701 diffs between them; in the long term, we'd like to use it for
702 unparseable directory material too. Closes ticket 21645
703 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
704 from 1MB to 16MB. This was necessary with the glibc allocator in
705 order to allow worker threads to allocate more memory -- which in
706 turn is necessary because of our new use of worker threads for
707 compression. Closes ticket 22096.
709 o Minor features (logging):
710 - Log files are no longer created world-readable by default.
711 (Previously, most distributors would store the logs in a non-
712 world-readable location to prevent inappropriate access. This
713 change is an extra precaution.) Closes ticket 21729; patch
716 o Minor features (performance):
717 - Our Keccak (SHA-3) implementation now accesses memory more
718 efficiently, especially on little-endian systems. Closes
720 - Add an O(1) implementation of channel_find_by_global_id(), to
721 speed some controller functions.
723 o Minor features (relay, configuration):
724 - The MyFamily option may now be repeated as many times as desired,
725 for relays that want to configure large families. Closes ticket
726 4998; patch by Daniel Pinto.
728 o Minor features (safety):
729 - Add an explicit check to extrainfo_parse_entry_from_string() for
730 NULL inputs. We don't believe this can actually happen, but it may
731 help silence a warning from the Clang analyzer. Closes
734 o Minor features (testing):
735 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
736 When Tor is compiled with this option, we disable a number of
737 redundant memory-safety failsafes that are intended to stop bugs
738 from becoming security issues. This makes it easier to hunt for
739 bugs that would be security issues without the failsafes turned
740 on. Closes ticket 21439.
741 - Add a general event-tracing instrumentation support to Tor. This
742 subsystem will enable developers and researchers to add fine-
743 grained instrumentation to their Tor instances, for use when
744 examining Tor network performance issues. There are no trace
745 events yet, and event-tracing is off by default unless enabled at
746 compile time. Implements ticket 13802.
747 - Improve our version parsing tests: add tests for typical version
748 components, add tests for invalid versions, including numeric
749 range and non-numeric prefixes. Unit tests 21278, 21450, and
750 21507. Partially implements 21470.
752 o Minor bugfixes (bandwidth accounting):
753 - Roll over monthly accounting at the configured hour and minute,
754 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
755 Found by Andrey Karpov with PVS-Studio.
757 o Minor bugfixes (code correctness):
758 - Accurately identify client connections by their lack of peer
759 authentication. This means that we bail out earlier if asked to
760 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
763 o Minor bugfixes (configuration):
764 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
765 bug 22252; bugfix on 0.2.9.3-alpha.
767 o Minor bugfixes (connection lifespan):
768 - Allow more control over how long TLS connections are kept open:
769 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
770 single option called CircuitsAvailableTimeout. Also, allow the
771 consensus to control the default values for both this preference
772 and the lifespan of relay-to-relay connections. Fixes bug 17592;
773 bugfix on 0.2.5.5-alpha.
774 - Increase the initial circuit build timeout testing frequency, to
775 help ensure that ReducedConnectionPadding clients finish learning
776 a timeout before their orconn would expire. The initial testing
777 rate was set back in the days of TAP and before the Tor Browser
778 updater, when we had to be much more careful about new clients
779 making lots of circuits. With this change, a circuit build timeout
780 is learned in about 15-20 minutes, instead of 100-120 minutes.
782 o Minor bugfixes (controller):
783 - GETINFO onions/current and onions/detached no longer respond with
784 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
785 - Trigger HS descriptor events on the control port when the client
786 fails to pick a hidden service directory for a hidden service.
787 This can happen if all the hidden service directories are in
788 ExcludeNodes, or they have all been queried within the last 15
789 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
791 o Minor bugfixes (directory authority):
792 - When rejecting a router descriptor for running an obsolete version
793 of Tor without ntor support, warn about the obsolete tor version,
794 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
795 - Prevent the shared randomness subsystem from asserting when
796 initialized by a bridge authority with an incomplete configuration
797 file. Fixes bug 21586; bugfix on 0.2.9.8.
799 o Minor bugfixes (exit-side DNS):
800 - Fix an untriggerable assertion that checked the output of a
801 libevent DNS error, so that the assertion actually behaves as
802 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
803 Karpov using PVS-Studio.
805 o Minor bugfixes (fallback directories):
806 - Make the usage example in updateFallbackDirs.py actually work, and
807 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
808 - Decrease the guard flag average required to be a fallback. This
809 allows us to keep relays that have their guard flag removed when
810 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
811 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
812 bugfix on 0.2.8.1-alpha.
813 - Make sure fallback directory mirrors have the same address, port,
814 and relay identity key for at least 30 days before they are
815 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
817 o Minor bugfixes (hidden services):
818 - Stop printing a cryptic warning when a hidden service gets a
819 request to connect to a virtual port that it hasn't configured.
820 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
821 - Simplify hidden service descriptor creation by using an existing
822 flag to check if an introduction point is established. Fixes bug
823 21599; bugfix on 0.2.7.2-alpha.
825 o Minor bugfixes (memory leak):
826 - Fix a small memory leak at exit from the backtrace handler code.
827 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
829 o Minor bugfixes (protocol, logging):
830 - Downgrade a log statement about unexpected relay cells from "bug"
831 to "protocol warning", because there is at least one use case
832 where it can be triggered by a buggy tor implementation. Fixes bug
833 21293; bugfix on 0.1.1.14-alpha.
835 o Minor bugfixes (testing):
836 - Use unbuffered I/O for utility functions around the
837 process_handle_t type. This fixes unit test failures reported on
838 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
839 - Make display of captured unit test log messages consistent. Fixes
840 bug 21510; bugfix on 0.2.9.3-alpha.
841 - Make test-network.sh always call chutney's test-network.sh.
842 Previously, this only worked on systems which had bash installed,
843 due to some bash-specific code in the script. Fixes bug 19699;
844 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
846 o Minor bugfixes (voting consistency):
847 - Reject version numbers with non-numeric prefixes (such as +, -, or
848 whitespace). Disallowing whitespace prevents differential version
849 parsing between POSIX-based and Windows platforms. Fixes bug 21507
850 and part of 21508; bugfix on 0.0.8pre1.
852 o Minor bugfixes (windows, relay):
853 - Resolve "Failure from drain_fd: No error" warnings on Windows
854 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
856 o Code simplification and refactoring:
857 - Break up the 630-line function connection_dir_client_reached_eof()
858 into a dozen smaller functions. This change should help
859 maintainability and readability of the client directory code.
860 - Isolate our use of the openssl headers so that they are only
861 included from our crypto wrapper modules, and from tests that
862 examine those modules' internals. Closes ticket 21841.
863 - Simplify our API to launch directory requests, making it more
864 extensible and less error-prone. Now it's easier to add extra
865 headers to directory requests. Closes ticket 21646.
866 - Our base64 decoding functions no longer overestimate the output
867 space that they need when parsing unpadded inputs. Closes
869 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
870 Resolves ticket 22213.
871 - The logic that directory caches use to spool request to clients,
872 serving them one part at a time so as not to allocate too much
873 memory, has been refactored for consistency. Previously there was
874 a separate spooling implementation per type of spoolable data. Now
875 there is one common spooling implementation, with extensible data
876 types. Closes ticket 21651.
877 - Tor's compression module now supports multiple backends. Part of
878 the implementation for proposal 278; closes ticket 21663.
881 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
883 - Correct documentation about the default DataDirectory value.
885 - Document the default behavior of NumEntryGuards and
886 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
888 - Document key=value pluggable transport arguments for Bridge lines
889 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
890 - Note that bandwidth-limiting options don't affect TCP headers or
891 DNS. Closes ticket 17170.
893 o Removed features (configuration options, all in ticket 22060):
894 - These configuration options are now marked Obsolete, and no longer
895 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
896 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
897 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
898 in 0.2.9.2-alpha and have now been removed. The previous default
899 behavior is now always chosen; the previous (less secure) non-
900 default behavior is now unavailable.
901 - CloseHSClientCircuitsImmediatelyOnTimeout and
902 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
903 0.2.9.2-alpha and now have been removed. HS circuits never close
904 on circuit build timeout; they have a longer timeout period.
905 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
906 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
907 (and others) to configure listen-only and advertise-only addresses.
909 o Removed features (tools):
910 - We've removed the tor-checkkey tool from src/tools. Long ago, we
911 used it to help people detect RSA keys that were generated by
912 versions of Debian affected by CVE-2008-0166. But those keys have
913 been out of circulation for ages, and this tool is no longer
914 required. Closes ticket 21842.
917 Changes in version 0.3.0.7 - 2017-05-15
918 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
919 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
920 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
921 clients are not affected.
923 o Major bugfixes (hidden service directory, security):
924 - Fix an assertion failure in the hidden service directory code, which
925 could be used by an attacker to remotely cause a Tor relay process to
926 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
927 should upgrade. This security issue is tracked as TROVE-2017-002.
928 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
931 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
934 o Minor features (future-proofing):
935 - Tor no longer refuses to download microdescriptors or descriptors
936 if they are listed as "published in the future". This change will
937 eventually allow us to stop listing meaningful "published" dates
938 in microdescriptor consensuses, and thereby allow us to reduce the
939 resources required to download consensus diffs by over 50%.
940 Implements part of ticket 21642; implements part of proposal 275.
942 o Minor bugfixes (Linux seccomp2 sandbox):
943 - The getpid() system call is now permitted under the Linux seccomp2
944 sandbox, to avoid crashing with versions of OpenSSL (and other
945 libraries) that attempt to learn the process's PID by using the
946 syscall rather than the VDSO code. Fixes bug 21943; bugfix
950 Changes in version 0.3.0.6 - 2017-04-26
951 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
953 With the 0.3.0 series, clients and relays now use Ed25519 keys to
954 authenticate their link connections to relays, rather than the old
955 RSA1024 keys that they used before. (Circuit crypto has been
956 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
957 the guard selection and replacement algorithm to behave more robustly
958 in the presence of unreliable networks, and to resist guard-
961 This series also includes numerous other small features and bugfixes,
962 along with more groundwork for the upcoming hidden-services revamp.
964 Per our stable release policy, we plan to support the Tor 0.3.0
965 release series for at least the next nine months, or for three months
966 after the first stable release of the 0.3.1 series: whichever is
967 longer. If you need a release with long-term support, we recommend
968 that you stay with the 0.2.9 series.
970 Below are the changes since 0.3.0.5-rc. For a list of all changes
971 since 0.2.9, see the ReleaseNotes file.
973 o Minor features (geoip):
974 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
977 o Minor bugfixes (control port):
978 - The GETINFO extra-info/digest/<digest> command was broken because
979 of a wrong base16 decode return value check, introduced when
980 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
982 o Minor bugfixes (crash prevention):
983 - Fix a (currently untriggerable, but potentially dangerous) crash
984 bug when base32-encoding inputs whose sizes are not a multiple of
985 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
988 Changes in version 0.3.0.5-rc - 2017-04-05
989 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
990 0.3.0 release series.
992 This is the second release candidate in the Tor 0.3.0 series, and has
993 much fewer changes than the first. If we find no new bugs or
994 regressions here, the first stable 0.3.0 release will be nearly
997 o Major bugfixes (crash, directory connections):
998 - Fix a rare crash when sending a begin cell on a circuit whose
999 linked directory connection had already been closed. Fixes bug
1000 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
1002 o Major bugfixes (guard selection):
1003 - Fix a guard selection bug where Tor would refuse to bootstrap in
1004 some cases if the user swapped a bridge for another bridge in
1005 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
1006 Reported by "torvlnt33r".
1008 o Minor features (geoip):
1009 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
1012 o Minor bugfix (compilation):
1013 - Fix a warning when compiling hs_service.c. Previously, it had no
1014 exported symbols when compiled for libor.a, resulting in a
1015 compilation warning from clang. Fixes bug 21825; bugfix
1018 o Minor bugfixes (hidden services):
1019 - Make hidden services check for failed intro point connections,
1020 even when they have exceeded their intro point creation limit.
1021 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
1022 - Make hidden services with 8 to 10 introduction points check for
1023 failed circuits immediately after startup. Previously, they would
1024 wait for 5 minutes before performing their first checks. Fixes bug
1025 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
1027 o Minor bugfixes (memory leaks):
1028 - Fix a memory leak when using GETCONF on a port option. Fixes bug
1029 21682; bugfix on 0.3.0.3-alpha.
1031 o Minor bugfixes (relay):
1032 - Avoid a double-marked-circuit warning that could happen when we
1033 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
1036 o Minor bugfixes (tests):
1037 - Run the entry_guard_parse_from_state_full() test with the time set
1038 to a specific date. (The guard state that this test was parsing
1039 contained guards that had expired since the test was first
1040 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
1043 - Update the description of the directory server options in the
1044 manual page, to clarify that a relay no longer needs to set
1045 DirPort in order to be a directory cache. Closes ticket 21720.
1049 Changes in version 0.2.8.13 - 2017-03-03
1050 Tor 0.2.8.13 backports a security fix from later Tor
1051 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
1052 this release, if for some reason they cannot upgrade to a later
1053 release series, and if they build Tor with the --enable-expensive-hardening
1056 Note that support for Tor 0.2.8.x is ending next year: we will not issue
1057 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
1058 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1060 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1061 - Fix an integer underflow bug when comparing malformed Tor
1062 versions. This bug could crash Tor when built with
1063 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1064 0.2.9.8, which were built with -ftrapv by default. In other cases
1065 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1066 on 0.0.8pre1. Found by OSS-Fuzz.
1068 o Minor features (geoip):
1069 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1073 Changes in version 0.2.7.7 - 2017-03-03
1074 Tor 0.2.7.7 backports a number of security fixes from later Tor
1075 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
1076 this release, if for some reason they cannot upgrade to a later
1079 Note that support for Tor 0.2.7.x is ending this year: we will not issue
1080 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
1081 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1083 o Directory authority changes (backport from 0.2.8.5-rc):
1084 - Urras is no longer a directory authority. Closes ticket 19271.
1086 o Directory authority changes (backport from 0.2.9.2-alpha):
1087 - The "Tonga" bridge authority has been retired; the new bridge
1088 authority is "Bifroest". Closes tickets 19728 and 19690.
1090 o Directory authority key updates (backport from 0.2.8.1-alpha):
1091 - Update the V3 identity key for the dannenberg directory authority:
1092 it was changed on 18 November 2015. Closes task 17906. Patch
1095 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1096 - Fix a bug in parsing that could cause clients to read a single
1097 byte past the end of an allocated region. This bug could be used
1098 to cause hardened clients (built with --enable-expensive-hardening)
1099 to crash if they tried to visit a hostile hidden service. Non-
1100 hardened clients are only affected depending on the details of
1101 their platform's memory allocator. Fixes bug 21018; bugfix on
1102 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1103 2016-12-002 and as CVE-2016-1254.
1105 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
1106 - Stop a crash that could occur when a client running with DNSPort
1107 received a query with multiple address types, and the first
1108 address type was not supported. Found and fixed by Scott Dial.
1109 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1110 - Prevent a class of security bugs caused by treating the contents
1111 of a buffer chunk as if they were a NUL-terminated string. At
1112 least one such bug seems to be present in all currently used
1113 versions of Tor, and would allow an attacker to remotely crash
1114 most Tor instances, especially those compiled with extra compiler
1115 hardening. With this defense in place, such bugs can't crash Tor,
1116 though we should still fix them as they occur. Closes ticket
1117 20384 (TROVE-2016-10-001).
1119 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1120 - Avoid a difficult-to-trigger heap corruption attack when extending
1121 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1122 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1123 Reported by Guido Vranken.
1125 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1126 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1127 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1129 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1130 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1131 pointer to the previous (uninitialized) key value. The impact here
1132 should be limited to a difficult-to-trigger crash, if OpenSSL is
1133 running an engine that makes key generation failures possible, or
1134 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1135 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1138 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1139 - Fix an integer underflow bug when comparing malformed Tor
1140 versions. This bug could crash Tor when built with
1141 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1142 0.2.9.8, which were built with -ftrapv by default. In other cases
1143 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1144 on 0.0.8pre1. Found by OSS-Fuzz.
1146 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1147 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1148 zero size. Check size argument to memwipe() for underflow. Fixes
1149 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1152 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1153 - Make Tor survive errors involving connections without a
1154 corresponding event object. Previously we'd fail with an
1155 assertion; now we produce a log message. Related to bug 16248.
1157 o Minor features (geoip):
1158 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1162 Changes in version 0.2.6.11 - 2017-03-03
1163 Tor 0.2.6.11 backports a number of security fixes from later Tor
1164 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
1165 this release, if for some reason they cannot upgrade to a later
1168 Note that support for Tor 0.2.6.x is ending this year: we will not issue
1169 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
1170 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1172 o Directory authority changes (backport from 0.2.8.5-rc):
1173 - Urras is no longer a directory authority. Closes ticket 19271.
1175 o Directory authority changes (backport from 0.2.9.2-alpha):
1176 - The "Tonga" bridge authority has been retired; the new bridge
1177 authority is "Bifroest". Closes tickets 19728 and 19690.
1179 o Directory authority key updates (backport from 0.2.8.1-alpha):
1180 - Update the V3 identity key for the dannenberg directory authority:
1181 it was changed on 18 November 2015. Closes task 17906. Patch
1184 o Major features (security fixes, backport from 0.2.9.4-alpha):
1185 - Prevent a class of security bugs caused by treating the contents
1186 of a buffer chunk as if they were a NUL-terminated string. At
1187 least one such bug seems to be present in all currently used
1188 versions of Tor, and would allow an attacker to remotely crash
1189 most Tor instances, especially those compiled with extra compiler
1190 hardening. With this defense in place, such bugs can't crash Tor,
1191 though we should still fix them as they occur. Closes ticket
1192 20384 (TROVE-2016-10-001).
1194 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1195 - Fix a bug in parsing that could cause clients to read a single
1196 byte past the end of an allocated region. This bug could be used
1197 to cause hardened clients (built with --enable-expensive-hardening)
1198 to crash if they tried to visit a hostile hidden service. Non-
1199 hardened clients are only affected depending on the details of
1200 their platform's memory allocator. Fixes bug 21018; bugfix on
1201 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1202 2016-12-002 and as CVE-2016-1254.
1204 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
1205 - Stop a crash that could occur when a client running with DNSPort
1206 received a query with multiple address types, and the first
1207 address type was not supported. Found and fixed by Scott Dial.
1208 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1210 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
1211 - Fix an error that could cause us to read 4 bytes before the
1212 beginning of an openssl string. This bug could be used to cause
1213 Tor to crash on systems with unusual malloc implementations, or
1214 systems with unusual hardening installed. Fixes bug 17404; bugfix
1217 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1218 - Avoid a difficult-to-trigger heap corruption attack when extending
1219 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1220 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1221 Reported by Guido Vranken.
1223 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1224 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1225 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1227 o Major bugfixes (guard selection, backport from 0.2.7.6):
1228 - Actually look at the Guard flag when selecting a new directory
1229 guard. When we implemented the directory guard design, we
1230 accidentally started treating all relays as if they have the Guard
1231 flag during guard selection, leading to weaker anonymity and worse
1232 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1235 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1236 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1237 pointer to the previous (uninitialized) key value. The impact here
1238 should be limited to a difficult-to-trigger crash, if OpenSSL is
1239 running an engine that makes key generation failures possible, or
1240 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1241 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1244 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1245 - Fix an integer underflow bug when comparing malformed Tor
1246 versions. This bug could crash Tor when built with
1247 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1248 0.2.9.8, which were built with -ftrapv by default. In other cases
1249 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1250 on 0.0.8pre1. Found by OSS-Fuzz.
1252 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1253 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1254 zero size. Check size argument to memwipe() for underflow. Fixes
1255 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1258 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1259 - Make Tor survive errors involving connections without a
1260 corresponding event object. Previously we'd fail with an
1261 assertion; now we produce a log message. Related to bug 16248.
1263 o Minor features (geoip):
1264 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1267 o Minor bugfixes (compilation, backport from 0.2.7.6):
1268 - Fix a compilation warning with Clang 3.6: Do not check the
1269 presence of an address which can never be NULL. Fixes bug 17781.
1272 Changes in version 0.2.5.13 - 2017-03-03
1273 Tor 0.2.5.13 backports a number of security fixes from later Tor
1274 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
1275 this release, if for some reason they cannot upgrade to a later
1278 Note that support for Tor 0.2.5.x is ending next year: we will not issue
1279 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
1280 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1282 o Directory authority changes (backport from 0.2.8.5-rc):
1283 - Urras is no longer a directory authority. Closes ticket 19271.
1285 o Directory authority changes (backport from 0.2.9.2-alpha):
1286 - The "Tonga" bridge authority has been retired; the new bridge
1287 authority is "Bifroest". Closes tickets 19728 and 19690.
1289 o Directory authority key updates (backport from 0.2.8.1-alpha):
1290 - Update the V3 identity key for the dannenberg directory authority:
1291 it was changed on 18 November 2015. Closes task 17906. Patch
1294 o Major features (security fixes, backport from 0.2.9.4-alpha):
1295 - Prevent a class of security bugs caused by treating the contents
1296 of a buffer chunk as if they were a NUL-terminated string. At
1297 least one such bug seems to be present in all currently used
1298 versions of Tor, and would allow an attacker to remotely crash
1299 most Tor instances, especially those compiled with extra compiler
1300 hardening. With this defense in place, such bugs can't crash Tor,
1301 though we should still fix them as they occur. Closes ticket
1302 20384 (TROVE-2016-10-001).
1304 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1305 - Fix a bug in parsing that could cause clients to read a single
1306 byte past the end of an allocated region. This bug could be used
1307 to cause hardened clients (built with --enable-expensive-hardening)
1308 to crash if they tried to visit a hostile hidden service. Non-
1309 hardened clients are only affected depending on the details of
1310 their platform's memory allocator. Fixes bug 21018; bugfix on
1311 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1312 2016-12-002 and as CVE-2016-1254.
1314 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
1315 - Stop a crash that could occur when a client running with DNSPort
1316 received a query with multiple address types, and the first
1317 address type was not supported. Found and fixed by Scott Dial.
1318 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1320 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
1321 - Fix an error that could cause us to read 4 bytes before the
1322 beginning of an openssl string. This bug could be used to cause
1323 Tor to crash on systems with unusual malloc implementations, or
1324 systems with unusual hardening installed. Fixes bug 17404; bugfix
1327 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1328 - Avoid a difficult-to-trigger heap corruption attack when extending
1329 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1330 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1331 Reported by Guido Vranken.
1333 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1334 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1335 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1337 o Major bugfixes (guard selection, backport from 0.2.7.6):
1338 - Actually look at the Guard flag when selecting a new directory
1339 guard. When we implemented the directory guard design, we
1340 accidentally started treating all relays as if they have the Guard
1341 flag during guard selection, leading to weaker anonymity and worse
1342 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1345 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1346 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1347 pointer to the previous (uninitialized) key value. The impact here
1348 should be limited to a difficult-to-trigger crash, if OpenSSL is
1349 running an engine that makes key generation failures possible, or
1350 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1351 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1354 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1355 - Fix an integer underflow bug when comparing malformed Tor
1356 versions. This bug could crash Tor when built with
1357 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1358 0.2.9.8, which were built with -ftrapv by default. In other cases
1359 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1360 on 0.0.8pre1. Found by OSS-Fuzz.
1362 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1363 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1364 zero size. Check size argument to memwipe() for underflow. Fixes
1365 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1368 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1369 - Make Tor survive errors involving connections without a
1370 corresponding event object. Previously we'd fail with an
1371 assertion; now we produce a log message. Related to bug 16248.
1373 o Minor features (geoip):
1374 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1377 o Minor bugfixes (compilation, backport from 0.2.7.6):
1378 - Fix a compilation warning with Clang 3.6: Do not check the
1379 presence of an address which can never be NULL. Fixes bug 17781.
1381 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
1382 - Check for failures from crypto_early_init, and refuse to continue.
1383 A previous typo meant that we could keep going with an
1384 uninitialized crypto library, and would have OpenSSL initialize
1385 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1386 when implementing ticket 4900. Patch by "teor".
1388 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
1389 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1390 a client authorized hidden service. Fixes bug 15823; bugfix
1394 Changes in version 0.2.4.28 - 2017-03-03
1395 Tor 0.2.4.28 backports a number of security fixes from later Tor
1396 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
1397 this release, if for some reason they cannot upgrade to a later
1400 Note that support for Tor 0.2.4.x is ending soon: we will not issue
1401 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
1402 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
1404 o Directory authority changes (backport from 0.2.8.5-rc):
1405 - Urras is no longer a directory authority. Closes ticket 19271.
1407 o Directory authority changes (backport from 0.2.9.2-alpha):
1408 - The "Tonga" bridge authority has been retired; the new bridge
1409 authority is "Bifroest". Closes tickets 19728 and 19690.
1411 o Directory authority key updates (backport from 0.2.8.1-alpha):
1412 - Update the V3 identity key for the dannenberg directory authority:
1413 it was changed on 18 November 2015. Closes task 17906. Patch
1416 o Major features (security fixes, backport from 0.2.9.4-alpha):
1417 - Prevent a class of security bugs caused by treating the contents
1418 of a buffer chunk as if they were a NUL-terminated string. At
1419 least one such bug seems to be present in all currently used
1420 versions of Tor, and would allow an attacker to remotely crash
1421 most Tor instances, especially those compiled with extra compiler
1422 hardening. With this defense in place, such bugs can't crash Tor,
1423 though we should still fix them as they occur. Closes ticket
1424 20384 (TROVE-2016-10-001).
1426 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1427 - Fix a bug in parsing that could cause clients to read a single
1428 byte past the end of an allocated region. This bug could be used
1429 to cause hardened clients (built with --enable-expensive-hardening)
1430 to crash if they tried to visit a hostile hidden service. Non-
1431 hardened clients are only affected depending on the details of
1432 their platform's memory allocator. Fixes bug 21018; bugfix on
1433 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1434 2016-12-002 and as CVE-2016-1254.
1436 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
1437 - Fix an error that could cause us to read 4 bytes before the
1438 beginning of an openssl string. This bug could be used to cause
1439 Tor to crash on systems with unusual malloc implementations, or
1440 systems with unusual hardening installed. Fixes bug 17404; bugfix
1443 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1444 - Avoid a difficult-to-trigger heap corruption attack when extending
1445 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1446 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1447 Reported by Guido Vranken.
1449 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1450 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1451 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1453 o Major bugfixes (guard selection, backport from 0.2.7.6):
1454 - Actually look at the Guard flag when selecting a new directory
1455 guard. When we implemented the directory guard design, we
1456 accidentally started treating all relays as if they have the Guard
1457 flag during guard selection, leading to weaker anonymity and worse
1458 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1461 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1462 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1463 pointer to the previous (uninitialized) key value. The impact here
1464 should be limited to a difficult-to-trigger crash, if OpenSSL is
1465 running an engine that makes key generation failures possible, or
1466 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1467 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1470 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1471 - Fix an integer underflow bug when comparing malformed Tor
1472 versions. This bug could crash Tor when built with
1473 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1474 0.2.9.8, which were built with -ftrapv by default. In other cases
1475 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1476 on 0.0.8pre1. Found by OSS-Fuzz.
1478 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1479 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1480 zero size. Check size argument to memwipe() for underflow. Fixes
1481 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1484 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1485 - Make Tor survive errors involving connections without a
1486 corresponding event object. Previously we'd fail with an
1487 assertion; now we produce a log message. Related to bug 16248.
1489 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
1490 - Make it harder for attackers to overload hidden services with
1491 introductions, by blocking multiple introduction requests on the
1492 same circuit. Resolves ticket 15515.
1494 o Minor features (geoip):
1495 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1498 o Minor bugfixes (compilation, backport from 0.2.7.6):
1499 - Fix a compilation warning with Clang 3.6: Do not check the
1500 presence of an address which can never be NULL. Fixes bug 17781.
1502 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
1503 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1504 a client authorized hidden service. Fixes bug 15823; bugfix
1508 Changes in version 0.3.0.4-rc - 2017-03-01
1509 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
1510 0.3.0 release series, and introduces a few reliability features to
1511 keep them from coming back.
1513 This is the first release candidate in the Tor 0.3.0 series. If we
1514 find no new bugs or regressions here, the first stable 0.3.0 release
1515 will be nearly identical to it.
1517 o Major bugfixes (bridges):
1518 - When the same bridge is configured multiple times with the same
1519 identity, but at different address:port combinations, treat those
1520 bridge instances as separate guards. This fix restores the ability
1521 of clients to configure the same bridge with multiple pluggable
1522 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
1524 o Major bugfixes (hidden service directory v3):
1525 - Stop crashing on a failed v3 hidden service descriptor lookup
1526 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
1528 o Major bugfixes (parsing):
1529 - When parsing a malformed content-length field from an HTTP
1530 message, do not read off the end of the buffer. This bug was a
1531 potential remote denial-of-service attack against Tor clients and
1532 relays. A workaround was released in October 2016, to prevent this
1533 bug from crashing Tor. This is a fix for the underlying issue,
1534 which should no longer matter (if you applied the earlier patch).
1535 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
1536 using AFL (http://lcamtuf.coredump.cx/afl/).
1537 - Fix an integer underflow bug when comparing malformed Tor
1538 versions. This bug could crash Tor when built with
1539 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1540 0.2.9.8, which were built with -ftrapv by default. In other cases
1541 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1542 on 0.0.8pre1. Found by OSS-Fuzz.
1544 o Minor feature (protocol versioning):
1545 - Add new protocol version for proposal 224. HSIntro now advertises
1546 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
1548 o Minor features (directory authorities):
1549 - Directory authorities now reject descriptors that claim to be
1550 malformed versions of Tor. Helps prevent exploitation of
1552 - Reject version numbers with components that exceed INT32_MAX.
1553 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
1554 Fixes bug 21450; bugfix on 0.0.8pre1.
1555 - Directory authorities now reject relays running versions
1556 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
1557 suffer from bug 20499 and don't keep their consensus cache
1558 up-to-date. Resolves ticket 20509.
1560 o Minor features (geoip):
1561 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1564 o Minor features (reliability, crash):
1565 - Try better to detect problems in buffers where they might grow (or
1566 think they have grown) over 2 GB in size. Diagnostic for
1569 o Minor features (testing):
1570 - During 'make test-network-all', if tor logs any warnings, ask
1571 chutney to output them. Requires a recent version of chutney with
1572 the 21572 patch. Implements 21570.
1574 o Minor bugfixes (certificate expiration time):
1575 - Avoid using link certificates that don't become valid till some
1576 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
1578 o Minor bugfixes (code correctness):
1579 - Repair a couple of (unreachable or harmless) cases of the risky
1580 comparison-by-subtraction pattern that caused bug 21278.
1581 - Remove a redundant check for the UseEntryGuards option from the
1582 options_transition_affects_guards() function. Fixes bug 21492;
1583 bugfix on 0.3.0.1-alpha.
1585 o Minor bugfixes (directory mirrors):
1586 - Allow relays to use directory mirrors without a DirPort: these
1587 relays need to be contacted over their ORPorts using a begindir
1588 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
1589 - Clarify the message logged when a remote relay is unexpectedly
1590 missing an ORPort or DirPort: users were confusing this with a
1591 local port. Fixes another case of bug 20711; bugfix
1594 o Minor bugfixes (guards):
1595 - Don't warn about a missing guard state on timeout-measurement
1596 circuits: they aren't supposed to be using guards. Fixes an
1597 instance of bug 21007; bugfix on 0.3.0.1-alpha.
1598 - Silence a BUG() warning when attempting to use a guard whose
1599 descriptor we don't know, and make this scenario less likely to
1600 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
1602 o Minor bugfixes (hidden service):
1603 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
1604 cells. Previously, we were using sizeof() on a pointer, instead of
1605 the real destination buffer. Fortunately, that value was only used
1606 to double-check that there was enough room--which was already
1607 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
1609 o Minor bugfixes (testing):
1610 - Fix Raspbian build issues related to missing socket errno in
1611 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
1613 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
1614 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
1615 - Use bash in src/test/test-network.sh. This ensures we reliably
1616 call chutney's newer tools/test-network.sh when available. Fixes
1617 bug 21562; bugfix on 0.2.9.1-alpha.
1620 - Small fixes to the fuzzing documentation. Closes ticket 21472.
1623 Changes in version 0.2.9.10 - 2017-03-01
1624 Tor 0.2.9.10 backports a security fix from later Tor release. It also
1625 includes fixes for some major issues affecting directory authorities,
1626 LibreSSL compatibility, and IPv6 correctness.
1628 The Tor 0.2.9.x release series is now marked as a long-term-support
1629 series. We intend to backport security fixes to 0.2.9.x until at
1630 least January of 2020.
1632 o Major bugfixes (directory authority, 0.3.0.3-alpha):
1633 - During voting, when marking a relay as a probable sybil, do not
1634 clear its BadExit flag: sybils can still be bad in other ways
1635 too. (We still clear the other flags.) Fixes bug 21108; bugfix
1638 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
1639 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
1640 any IPv6 addresses. Instead, only reject a port over IPv6 if the
1641 exit policy rejects that port on more than an IPv6 /16 of
1642 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
1643 which rejected a relay's own IPv6 address by default. Fixes bug
1644 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
1646 o Major bugfixes (parsing, also in 0.3.0.4-rc):
1647 - Fix an integer underflow bug when comparing malformed Tor
1648 versions. This bug could crash Tor when built with
1649 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1650 0.2.9.8, which were built with -ftrapv by default. In other cases
1651 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1652 on 0.0.8pre1. Found by OSS-Fuzz.
1654 o Minor features (directory authorities, also in 0.3.0.4-rc):
1655 - Directory authorities now reject descriptors that claim to be
1656 malformed versions of Tor. Helps prevent exploitation of
1658 - Reject version numbers with components that exceed INT32_MAX.
1659 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
1660 Fixes bug 21450; bugfix on 0.0.8pre1.
1662 o Minor features (geoip):
1663 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1666 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
1667 - Autoconf now checks to determine if OpenSSL structures are opaque,
1668 instead of explicitly checking for OpenSSL version numbers. Part
1670 - Support building with recent LibreSSL code that uses opaque
1671 structures. Closes ticket 21359.
1673 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
1674 - Repair a couple of (unreachable or harmless) cases of the risky
1675 comparison-by-subtraction pattern that caused bug 21278.
1677 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
1678 - The tor-resolve command line tool now rejects hostnames over 255
1679 characters in length. Previously, it would silently truncate them,
1680 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
1681 Patch by "junglefowl".
1684 Changes in version 0.3.0.3-alpha - 2017-02-03
1685 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
1686 0.3.0.x development series, including some that could cause
1687 authorities to behave badly. There is also a fix for a longstanding
1688 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
1689 includes some smaller features and bugfixes.
1691 The Tor 0.3.0.x release series is now in patch-freeze: no additional
1692 features will be considered for inclusion in 0.3.0.x. We suspect that
1693 some bugs will probably remain, however, and we encourage people to
1696 o Major bugfixes (directory authority):
1697 - During voting, when marking a relay as a probable sybil, do not
1698 clear its BadExit flag: sybils can still be bad in other ways
1699 too. (We still clear the other flags.) Fixes bug 21108; bugfix
1701 - When deciding whether we have just found a router to be reachable,
1702 do not penalize it for not having performed an Ed25519 link
1703 handshake if it does not claim to support an Ed25519 handshake.
1704 Previously, we would treat such relays as non-running. Fixes bug
1705 21107; bugfix on 0.3.0.1-alpha.
1707 o Major bugfixes (entry guards):
1708 - Stop trying to build circuits through entry guards for which we
1709 have no descriptor. Also, stop crashing in the case that we *do*
1710 accidentally try to build a circuit in such a state. Fixes bug
1711 21242; bugfix on 0.3.0.1-alpha.
1713 o Major bugfixes (IPv6 Exits):
1714 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
1715 any IPv6 addresses. Instead, only reject a port over IPv6 if the
1716 exit policy rejects that port on more than an IPv6 /16 of
1717 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
1718 which rejected a relay's own IPv6 address by default. Fixes bug
1719 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
1721 o Minor feature (client):
1722 - Enable IPv6 traffic on the SocksPort by default. To disable this,
1723 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
1725 o Minor feature (fallback scripts):
1726 - Add a check_existing mode to updateFallbackDirs.py, which checks
1727 if fallbacks in the hard-coded list are working. Closes ticket
1728 20174. Patch by haxxpop.
1730 o Minor features (ciphersuite selection):
1731 - Clients now advertise a list of ciphersuites closer to the ones
1732 preferred by Firefox. Closes part of ticket 15426.
1733 - Allow relays to accept a wider range of ciphersuites, including
1734 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
1736 o Minor features (controller, configuration):
1737 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
1738 and so on, now comes with a __*Port variant that will not be saved
1739 to the torrc file by the controller's SAVECONF command. This
1740 change allows TorBrowser to set up a single-use domain socket for
1741 each time it launches Tor. Closes ticket 20956.
1742 - The GETCONF command can now query options that may only be
1743 meaningful in context-sensitive lists. This allows the controller
1744 to query the mixed SocksPort/__SocksPort style options introduced
1745 in feature 20956. Implements ticket 21300.
1747 o Minor features (portability, compilation):
1748 - Autoconf now checks to determine if OpenSSL structures are opaque,
1749 instead of explicitly checking for OpenSSL version numbers. Part
1751 - Support building with recent LibreSSL code that uses opaque
1752 structures. Closes ticket 21359.
1754 o Minor features (relay):
1755 - We now allow separation of exit and relay traffic to different
1756 source IP addresses, using the OutboundBindAddressExit and
1757 OutboundBindAddressOR options respectively. Closes ticket 17975.
1758 Written by Michael Sonntag.
1760 o Minor bugfix (logging):
1761 - Don't recommend the use of Tor2web in non-anonymous mode.
1762 Recommending Tor2web is a bad idea because the client loses all
1763 anonymity. Tor2web should only be used in specific cases by users
1764 who *know* and understand the issues. Fixes bug 21294; bugfix
1767 o Minor bugfixes (client):
1768 - Always recover from failures in extend_info_from_node(), in an
1769 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
1770 bugfix on 0.2.3.1-alpha.
1772 o Minor bugfixes (client, entry guards):
1773 - Fix a bug warning (with backtrace) when we fail a channel that
1774 circuits to fallback directories on it. Fixes bug 21128; bugfix
1776 - Fix a spurious bug warning (with backtrace) when removing an
1777 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
1778 - Fix a bug of the new guard algorithm where tor could stall for up
1779 to 10 minutes before retrying a guard after a long period of no
1780 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
1781 - Do not try to build circuits until we have descriptors for our
1782 primary entry guards. Related to fix for bug 21242.
1784 o Minor bugfixes (configure, autoconf):
1785 - Rename the configure option --enable-expensive-hardening to
1786 --enable-fragile-hardening. Expensive hardening makes the tor
1787 daemon abort when some kinds of issues are detected. Thus, it
1788 makes tor more at risk of remote crashes but safer against RCE or
1789 heartbleed bug category. We now try to explain this issue in a
1790 message from the configure script. Fixes bug 21290; bugfix
1793 o Minor bugfixes (controller):
1794 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
1795 20824; bugfix on 0.3.0.1-alpha.
1797 o Minor bugfixes (hidden service):
1798 - Clean up the code for expiring intro points with no associated
1799 circuits. It was causing, rarely, a service with some expiring
1800 introduction points to not open enough additional introduction
1801 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
1802 - Stop setting the torrc option HiddenServiceStatistics to "0" just
1803 because we're not a bridge or relay. Instead, we preserve whatever
1804 value the user set (or didn't set). Fixes bug 21150; bugfix
1806 - Resolve two possible underflows which could lead to creating and
1807 closing a lot of introduction point circuits in a non-stop loop.
1808 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
1810 o Minor bugfixes (portability):
1811 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
1812 It is supported by OpenBSD itself, and also by most OpenBSD
1813 variants (such as Bitrig). Fixes bug 20980; bugfix
1815 - When mapping a file of length greater than SIZE_MAX, do not
1816 silently truncate its contents. This issue could occur on 32 bit
1817 systems with large file support and files which are larger than 4
1818 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
1820 o Minor bugfixes (tor-resolve):
1821 - The tor-resolve command line tool now rejects hostnames over 255
1822 characters in length. Previously, it would silently truncate them,
1823 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
1824 Patch by "junglefowl".
1826 o Minor bugfixes (Windows services):
1827 - Be sure to initialize the monotonic time subsystem before using
1828 it, even when running as an NT service. Fixes bug 21356; bugfix
1832 Changes in version 0.3.0.2-alpha - 2017-01-23
1833 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
1834 cause relays and clients to crash, even if they were not built with
1835 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
1836 versions, and also affects 0.3.0.1-alpha: all relays running an affected
1837 version should upgrade.
1839 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
1840 time-to-live values, makes directory authorities enforce the 1-to-1
1841 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
1842 client-side onion service reachability bug, does better at selecting
1843 the set of fallback directories, and more.
1845 o Major bugfixes (security, also in 0.2.9.9):
1846 - Downgrade the "-ftrapv" option from "always on" to "only on when
1847 --enable-expensive-hardening is provided." This hardening option, like
1848 others, can turn survivable bugs into crashes--and having it on by
1849 default made a (relatively harmless) integer overflow bug into a
1850 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
1853 o Major features (security):
1854 - Change the algorithm used to decide DNS TTLs on client and server
1855 side, to better resist DNS-based correlation attacks like the
1856 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
1857 Feamster. Now relays only return one of two possible DNS TTL
1858 values, and clients are willing to believe DNS TTL values up to 3
1859 hours long. Closes ticket 19769.
1861 o Major features (directory authority, security):
1862 - The default for AuthDirPinKeys is now 1: directory authorities
1863 will reject relays where the RSA identity key matches a previously
1864 seen value, but the Ed25519 key has changed. Closes ticket 18319.
1866 o Major bugfixes (client, guard, crash):
1867 - In circuit_get_global_origin_list(), return the actual list of
1868 origin circuits. The previous version of this code returned the
1869 list of all the circuits, and could have caused strange bugs,
1870 including possible crashes. Fixes bug 21118; bugfix
1873 o Major bugfixes (client, onion service, also in 0.2.9.9):
1874 - Fix a client-side onion service reachability bug, where multiple
1875 socks requests to an onion service (or a single slow request)
1876 could cause us to mistakenly mark some of the service's
1877 introduction points as failed, and we cache that failure so
1878 eventually we run out and can't reach the service. Also resolves a
1879 mysterious "Remote server sent bogus reason code 65021" log
1880 warning. The bug was introduced in ticket 17218, where we tried to
1881 remember the circuit end reason as a uint16_t, which mangled
1882 negative values. Partially fixes bug 21056 and fixes bug 20307;
1883 bugfix on 0.2.8.1-alpha.
1885 o Major bugfixes (DNS):
1886 - Fix a bug that prevented exit nodes from caching DNS records for
1887 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
1889 o Minor features (controller):
1890 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
1891 shared-random values to the controller. Closes ticket 19925.
1893 o Minor features (entry guards):
1894 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
1895 break regression tests.
1896 - Require UseEntryGuards when UseBridges is set, in order to make
1897 sure bridges aren't bypassed. Resolves ticket 20502.
1899 o Minor features (fallback directories):
1900 - Select 200 fallback directories for each release. Closes
1902 - Allow 3 fallback relays per operator, which is safe now that we
1903 are choosing 200 fallback relays. Closes ticket 20912.
1904 - Exclude relays affected by bug 20499 from the fallback list.
1905 Exclude relays from the fallback list if they are running versions
1906 known to be affected by bug 20499, or if in our tests they deliver
1907 a stale consensus (i.e. one that expired more than 24 hours ago).
1908 Closes ticket 20539.
1909 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
1911 - Require fallback directories to have the same address and port for
1912 7 days (now that we have enough relays with this stability).
1913 Relays whose OnionOO stability timer is reset on restart by bug
1914 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
1915 this issue. Closes ticket 20880; maintains short-term fix
1917 - Require fallbacks to have flags for 90% of the time (weighted
1918 decaying average), rather than 95%. This allows at least 73% of
1919 clients to bootstrap in the first 5 seconds without contacting an
1920 authority. Part of ticket 18828.
1921 - Annotate updateFallbackDirs.py with the bandwidth and consensus
1922 weight for each candidate fallback. Closes ticket 20878.
1923 - Make it easier to change the output sort order of fallbacks.
1924 Closes ticket 20822.
1925 - Display the relay fingerprint when downloading consensuses from
1926 fallbacks. Closes ticket 20908.
1928 o Minor features (geoip, also in 0.2.9.9):
1929 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
1932 o Minor features (next-gen onion service directories):
1933 - Remove the "EnableOnionServicesV3" consensus parameter that we
1934 introduced in 0.3.0.1-alpha: relays are now always willing to act
1935 as v3 onion service directories. Resolves ticket 19899.
1937 o Minor features (linting):
1938 - Enhance the changes file linter to warn on Tor versions that are
1939 prefixed with "tor-". Closes ticket 21096.
1941 o Minor features (logging):
1942 - In several places, describe unset ed25519 keys as "<unset>",
1943 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
1945 o Minor bugfix (control protocol):
1946 - The reply to a "GETINFO config/names" request via the control
1947 protocol now spells the type "Dependent" correctly. This is a
1948 breaking change in the control protocol. (The field seems to be
1949 ignored by the most common known controllers.) Fixes bug 18146;
1950 bugfix on 0.1.1.4-alpha.
1952 o Minor bugfixes (bug resilience):
1953 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
1954 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
1955 Hans Jerry Illikainen.
1957 o Minor bugfixes (build):
1958 - Replace obsolete Autoconf macros with their modern equivalent and
1959 prevent similar issues in the future. Fixes bug 20990; bugfix
1962 o Minor bugfixes (client, guards):
1963 - Fix bug where Tor would think that there are circuits waiting for
1964 better guards even though those circuits have been freed. Fixes
1965 bug 21142; bugfix on 0.3.0.1-alpha.
1967 o Minor bugfixes (config):
1968 - Don't assert on startup when trying to get the options list and
1969 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
1970 options so of course they aren't ready yet. Fixes bug 21062;
1971 bugfix on 0.2.9.3-alpha.
1973 o Minor bugfixes (controller):
1974 - Make the GETINFO interface for inquiring about entry guards
1975 support the new guards backend. Fixes bug 20823; bugfix
1978 o Minor bugfixes (dead code):
1979 - Remove a redundant check for PidFile changes at runtime in
1980 options_transition_allowed(): this check is already performed
1981 regardless of whether the sandbox is active. Fixes bug 21123;
1982 bugfix on 0.2.5.4-alpha.
1984 o Minor bugfixes (documentation):
1985 - Update the tor manual page to document every option that can not
1986 be changed while tor is running. Fixes bug 21122.
1988 o Minor bugfixes (fallback directories):
1989 - Stop failing when a relay has no uptime data in
1990 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
1991 - Avoid checking fallback candidates' DirPorts if they are down in
1992 OnionOO. When a relay operator has multiple relays, this
1993 prioritizes relays that are up over relays that are down. Fixes
1994 bug 20926; bugfix on 0.2.8.3-alpha.
1995 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
1996 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
1998 o Minor bugfixes (guards, bootstrapping):
1999 - When connecting to a directory guard during bootstrap, do not mark
2000 the guard as successful until we receive a good-looking directory
2001 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
2003 o Minor bugfixes (onion services):
2004 - Fix the config reload pruning of old vs new services so it
2005 actually works when both ephemeral and non-ephemeral services are
2006 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
2007 - Allow the number of introduction points to be as low as 0, rather
2008 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
2010 o Minor bugfixes (IPv6):
2011 - Make IPv6-using clients try harder to find an IPv6 directory
2012 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
2013 - When IPv6 addresses have not been downloaded yet (microdesc
2014 consensus documents don't list relay IPv6 addresses), use hard-
2015 coded addresses for authorities, fallbacks, and configured
2016 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
2017 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
2019 o Minor bugfixes (memory leaks):
2020 - Fix a memory leak when configuring hidden services. Fixes bug
2021 20987; bugfix on 0.3.0.1-alpha.
2023 o Minor bugfixes (portability, also in 0.2.9.9):
2024 - Avoid crashing when Tor is built using headers that contain
2025 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
2026 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
2028 - Fix Libevent detection on platforms without Libevent 1 headers
2029 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
2031 o Minor bugfixes (relay):
2032 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
2033 initializing the keys would reset the DataDirectory to 0700
2034 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
2035 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
2037 o Minor bugfixes (testing):
2038 - Remove undefined behavior from the backtrace generator by removing
2039 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
2041 o Minor bugfixes (unit tests):
2042 - Allow the unit tests to pass even when DNS lookups of bogus
2043 addresses do not fail as expected. Fixes bug 20862 and 20863;
2044 bugfix on unit tests introduced in 0.2.8.1-alpha
2045 through 0.2.9.4-alpha.
2047 o Code simplification and refactoring:
2048 - Refactor code to manipulate global_origin_circuit_list into
2049 separate functions. Closes ticket 20921.
2051 o Documentation (formatting):
2052 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
2053 blocks were incorrectly appearing. Closes ticket 20885.
2055 o Documentation (man page):
2056 - Clarify many options in tor.1 and add some min/max values for
2057 HiddenService options. Closes ticket 21058.
2060 Changes in version 0.2.9.9 - 2017-01-23
2061 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
2062 cause relays and clients to crash, even if they were not built with
2063 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
2064 versions, and also affects 0.3.0.1-alpha: all relays running an affected
2065 version should upgrade.
2067 This release also resolves a client-side onion service reachability
2068 bug, and resolves a pair of small portability issues.
2070 o Major bugfixes (security):
2071 - Downgrade the "-ftrapv" option from "always on" to "only on when
2072 --enable-expensive-hardening is provided." This hardening option,
2073 like others, can turn survivable bugs into crashes -- and having
2074 it on by default made a (relatively harmless) integer overflow bug
2075 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
2076 bugfix on 0.2.9.1-alpha.
2078 o Major bugfixes (client, onion service):
2079 - Fix a client-side onion service reachability bug, where multiple
2080 socks requests to an onion service (or a single slow request)
2081 could cause us to mistakenly mark some of the service's
2082 introduction points as failed, and we cache that failure so
2083 eventually we run out and can't reach the service. Also resolves a
2084 mysterious "Remote server sent bogus reason code 65021" log
2085 warning. The bug was introduced in ticket 17218, where we tried to
2086 remember the circuit end reason as a uint16_t, which mangled
2087 negative values. Partially fixes bug 21056 and fixes bug 20307;
2088 bugfix on 0.2.8.1-alpha.
2090 o Minor features (geoip):
2091 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
2094 o Minor bugfixes (portability):
2095 - Avoid crashing when Tor is built using headers that contain
2096 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
2097 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
2099 - Fix Libevent detection on platforms without Libevent 1 headers
2100 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
2103 Changes in version 0.3.0.1-alpha - 2016-12-19
2104 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
2105 series. It strengthens Tor's link and circuit handshakes by
2106 identifying relays by their Ed25519 keys, improves the algorithm that
2107 clients use to choose and maintain their list of guards, and includes
2108 additional backend support for the next-generation hidden service
2109 design. It also contains numerous other small features and
2110 improvements to security, correctness, and performance.
2112 Below are the changes since 0.2.9.8.
2114 o Major features (guard selection algorithm):
2115 - Tor's guard selection algorithm has been redesigned from the
2116 ground up, to better support unreliable networks and restrictive
2117 sets of entry nodes, and to better resist guard-capture attacks by
2118 hostile local networks. Implements proposal 271; closes
2121 o Major features (next-generation hidden services):
2122 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
2123 prop224 aka "Next Generation Hidden Services". Service and clients
2124 don't use this functionality yet. Closes ticket 19043. Based on
2125 initial code by Alec Heifetz.
2126 - Relays now support the HSDir version 3 protocol, so that they can
2127 can store and serve v3 descriptors. This is part of the next-
2128 generation onion service work detailled in proposal 224. Closes
2131 o Major features (protocol, ed25519 identity keys):
2132 - Relays now use Ed25519 to prove their Ed25519 identities and to
2133 one another, and to clients. This algorithm is faster and more
2134 secure than the RSA-based handshake we've been doing until now.
2135 Implements the second big part of proposal 220; Closes
2137 - Clients now support including Ed25519 identity keys in the EXTEND2
2138 cells they generate. By default, this is controlled by a consensus
2139 parameter, currently disabled. You can turn this feature on for
2140 testing by setting ExtendByEd25519ID in your configuration. This
2141 might make your traffic appear different than the traffic
2142 generated by other users, however. Implements part of ticket
2143 15056; part of proposal 220.
2144 - Relays now understand requests to extend to other relays by their
2145 Ed25519 identity keys. When an Ed25519 identity key is included in
2146 an EXTEND2 cell, the relay will only extend the circuit if the
2147 other relay can prove ownership of that identity. Implements part
2148 of ticket 15056; part of proposal 220.
2150 o Major bugfixes (scheduler):
2151 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
2152 caused the channel scheduler to behave more or less randomly,
2153 rather than preferring channels with higher-priority circuits.
2154 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
2156 o Minor features (controller):
2157 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
2158 rather than "unrecognized." Closes ticket 20389; patch from
2161 o Minor features (diagnostic, directory client):
2162 - Warn when we find an unexpected inconsistency in directory
2163 download status objects. Prevents some negative consequences of
2166 o Minor features (directory authority):
2167 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
2168 default) to control whether authorities should try to probe relays
2169 by their Ed25519 link keys. This option will go away in a few
2170 releases--unless we encounter major trouble in our ed25519 link
2171 protocol rollout, in which case it will serve as a safety option.
2173 o Minor features (directory cache):
2174 - Relays and bridges will now refuse to serve the consensus they
2175 have if they know it is too old for a client to use. Closes
2178 o Minor features (ed25519 link handshake):
2179 - Advertise support for the ed25519 link handshake using the
2180 subprotocol-versions mechanism, so that clients can tell which
2181 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
2183 o Minor features (fingerprinting resistance, authentication):
2184 - Extend the length of RSA keys used for TLS link authentication to
2185 2048 bits. (These weren't used for forward secrecy; for forward
2186 secrecy, we used P256.) Closes ticket 13752.
2188 o Minor features (infrastructure):
2189 - Implement smartlist_add_strdup() function. Replaces the use of
2190 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
2192 o Minor bugfixes (client):
2193 - When clients that use bridges start up with a cached consensus on
2194 disk, they were ignoring it and downloading a new one. Now they
2195 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
2197 o Minor bugfixes (configuration):
2198 - Accept non-space whitespace characters after the severity level in
2199 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
2200 - Support "TByte" and "TBytes" units in options given in bytes.
2201 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
2202 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
2204 o Minor bugfixes (consensus weight):
2205 - Add new consensus method that initializes bw weights to 1 instead
2206 of 0. This prevents a zero weight from making it all the way to
2207 the end (happens in small testing networks) and causing an error.
2208 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
2210 o Minor bugfixes (descriptors):
2211 - Correctly recognise downloaded full descriptors as valid, even
2212 when using microdescriptors as circuits. This affects clients with
2213 FetchUselessDescriptors set, and may affect directory authorities.
2214 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
2216 o Minor bugfixes (directory system):
2217 - Download all consensus flavors, descriptors, and authority
2218 certificates when FetchUselessDescriptors is set, regardless of
2219 whether tor is a directory cache or not. Fixes bug 20667; bugfix
2220 on all recent tor versions.
2221 - Bridges and relays now use microdescriptors (like clients do)
2222 rather than old-style router descriptors. Now bridges will blend
2223 in with clients in terms of the circuits they build. Fixes bug
2224 6769; bugfix on 0.2.3.2-alpha.
2226 o Minor bugfixes (ed25519 certificates):
2227 - Correctly interpret ed25519 certificates that would expire some
2228 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
2230 o Minor bugfixes (hidden services):
2231 - Stop ignoring misconfigured hidden services. Instead, refuse to
2232 start tor until the misconfigurations have been corrected. Fixes
2233 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
2236 o Minor bugfixes (memory leak at exit):
2237 - Fix a small harmless memory leak at exit of the previously unused
2238 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
2241 o Minor bugfixes (util):
2242 - When finishing writing a file to disk, if we were about to replace
2243 the file with the temporary file created before and we fail to
2244 replace it, remove the temporary file so it doesn't stay on disk.
2245 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
2247 o Minor bugfixes (Windows):
2248 - Check for getpagesize before using it to mmap files. This fixes
2249 compilation in some MinGW environments. Fixes bug 20530; bugfix on
2250 0.1.2.1-alpha. Reported by "ice".
2252 o Code simplification and refactoring:
2253 - Abolish all global guard context in entrynodes.c; replace with new
2254 guard_selection_t structure as preparation for proposal 271.
2255 Closes ticket 19858.
2256 - Introduce rend_service_is_ephemeral() that tells if given onion
2257 service is ephemeral. Replace unclear NULL-checkings for service
2258 directory with this function. Closes ticket 20526.
2259 - Extract magic numbers in circuituse.c into defined variables.
2260 - Refactor circuit_is_available_for_use to remove unnecessary check.
2261 - Refactor circuit_predict_and_launch_new for readability and
2262 testability. Closes ticket 18873.
2263 - Refactor large if statement in purpose_needs_anonymity to use
2264 switch statement instead. Closes part of ticket 20077.
2265 - Refactor the hashing API to return negative values for errors, as
2266 is done as throughout the codebase. Closes ticket 20717.
2267 - Remove data structures that were used to index or_connection
2268 objects by their RSA identity digests. These structures are fully
2269 redundant with the similar structures used in the
2270 channel abstraction.
2271 - Remove duplicate code in the channel_write_*cell() functions.
2272 Closes ticket 13827; patch from Pingl.
2273 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
2274 use only purpose_needs_anonymity. Closes part of ticket 20077.
2275 - The code to generate and parse EXTEND and EXTEND2 cells has been
2276 replaced with code automatically generated by the
2280 - Include the "TBits" unit in Tor's man page. Fixes part of bug
2281 20622; bugfix on tor-0.2.5.1-alpha.
2282 - Change '1' to 'weight_scale' in consensus bw weights calculation
2283 comments, as that is reality. Closes ticket 20273. Patch
2285 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
2286 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
2287 on tor-0.2.5.6-alpha.
2288 - Stop the man page from incorrectly stating that HiddenServiceDir
2289 must already exist. Fixes 20486.
2290 - Clarify that when ClientRejectInternalAddresses is enabled (which
2291 is the default), multicast DNS hostnames for machines on the local
2292 network (of the form *.local) are also rejected. Closes
2296 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
2297 limit for relays running on a single IP applies to authority IP
2298 addresses as well as to non-authority IP addresses. Closes
2300 - The UseDirectoryGuards torrc option no longer exists: all users
2301 that use entry guards will also use directory guards. Related to
2302 proposal 271; implements part of ticket 20831.
2305 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
2306 from "overcaffeinated".
2307 - Perform the coding style checks when running the tests and fail
2308 when coding style violations are found. Closes ticket 5500.
2309 - Add tests for networkstatus_compute_bw_weights_v10.
2310 - Add unit tests circuit_predict_and_launch_new.
2311 - Extract dummy_origin_circuit_new so it can be used by other
2315 Changes in version 0.2.8.12 - 2016-12-19
2316 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
2317 below) where Tor clients could crash when attempting to visit a
2318 hostile hidden service. Clients are recommended to upgrade as packages
2319 become available for their systems.
2321 It also includes an updated list of fallback directories, backported
2324 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
2325 backported to 0.2.8 in the future.
2327 o Major bugfixes (parsing, security, backported from 0.2.9.8):
2328 - Fix a bug in parsing that could cause clients to read a single
2329 byte past the end of an allocated region. This bug could be used
2330 to cause hardened clients (built with --enable-expensive-hardening)
2331 to crash if they tried to visit a hostile hidden service. Non-
2332 hardened clients are only affected depending on the details of
2333 their platform's memory allocator. Fixes bug 21018; bugfix on
2334 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2335 2016-12-002 and as CVE-2016-1254.
2337 o Minor features (fallback directory list, backported from 0.2.9.8):
2338 - Replace the 81 remaining fallbacks of the 100 originally
2339 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
2340 fallbacks (123 new, 54 existing, 27 removed) generated in December
2341 2016. Resolves ticket 20170.
2343 o Minor features (geoip, backported from 0.2.9.7-rc):
2344 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
2348 Changes in version 0.2.9.8 - 2016-12-19
2349 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
2351 The Tor 0.2.9 series makes mandatory a number of security features
2352 that were formerly optional. It includes support for a new shared-
2353 randomness protocol that will form the basis for next generation
2354 hidden services, includes a single-hop hidden service mode for
2355 optimizing .onion services that don't actually want to be hidden,
2356 tries harder not to overload the directory authorities with excessive
2357 downloads, and supports a better protocol versioning scheme for
2358 improved compatibility with other implementations of the Tor protocol.
2360 And of course, there are numerous other bugfixes and improvements.
2362 This release also includes a fix for a medium-severity issue (bug
2363 21018 below) where Tor clients could crash when attempting to visit a
2364 hostile hidden service. Clients are recommended to upgrade as packages
2365 become available for their systems.
2367 Below are the changes since 0.2.9.7-rc. For a list of all changes
2368 since 0.2.8, see the ReleaseNotes file.
2370 o Major bugfixes (parsing, security):
2371 - Fix a bug in parsing that could cause clients to read a single
2372 byte past the end of an allocated region. This bug could be used
2373 to cause hardened clients (built with --enable-expensive-hardening)
2374 to crash if they tried to visit a hostile hidden service. Non-
2375 hardened clients are only affected depending on the details of
2376 their platform's memory allocator. Fixes bug 21018; bugfix on
2377 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2378 2016-12-002 and as CVE-2016-1254.
2380 o Minor features (fallback directory list):
2381 - Replace the 81 remaining fallbacks of the 100 originally
2382 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
2383 fallbacks (123 new, 54 existing, 27 removed) generated in December
2384 2016. Resolves ticket 20170.
2387 Changes in version 0.2.9.7-rc - 2016-12-12
2388 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
2389 including a few that had prevented tests from passing on
2392 o Minor features (geoip):
2393 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
2396 o Minor bugfix (build):
2397 - The current Git revision when building from a local repository is
2398 now detected correctly when using git worktrees. Fixes bug 20492;
2399 bugfix on 0.2.3.9-alpha.
2401 o Minor bugfixes (directory authority):
2402 - When computing old Tor protocol line version in protover, we were
2403 looking at 0.2.7.5 twice instead of a specific case for
2404 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
2406 o Minor bugfixes (download scheduling):
2407 - Resolve a "bug" warning when considering a download schedule whose
2408 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
2410 o Minor bugfixes (logging):
2411 - Downgrade a harmless log message about the
2412 pending_entry_connections list from "warn" to "info". Mitigates
2415 o Minor bugfixes (memory leak):
2416 - Fix a small memory leak when receiving AF_UNIX connections on a
2417 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
2418 - When moving a signed descriptor object from a source to an
2419 existing destination, free the allocated memory inside that
2420 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
2422 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
2423 - Fix a memory leak and use-after-free error when removing entries
2424 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
2425 0.2.5.5-alpha. Patch from "cypherpunks".
2427 o Minor bugfixes (portability):
2428 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
2429 Fixes bug 20935; bugfix on 0.2.9.6-rc.
2431 o Minor bugfixes (unit tests):
2432 - Stop expecting NetBSD unit tests to report success for ipfw. Part
2433 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
2434 - Fix tolerances in unit tests for monotonic time comparisons
2435 between nanoseconds and microseconds. Previously, we accepted a 10
2436 us difference only, which is not realistic on every platform's
2437 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
2438 - Remove a double-free in the single onion service unit test. Stop
2439 ignoring a return value. Make future changes less error-prone.
2440 Fixes bug 20864; bugfix on 0.2.9.6-rc.
2443 Changes in version 0.2.8.11 - 2016-12-08
2444 Tor 0.2.8.11 backports fixes for additional portability issues that
2445 could prevent Tor from building correctly on OSX Sierra, or with
2446 OpenSSL 1.1. Affected users should upgrade; others can safely stay
2449 o Minor bugfixes (portability):
2450 - Avoid compilation errors when building on OSX Sierra. Sierra began
2451 to support the getentropy() and clock_gettime() APIs, but created
2452 a few problems in doing so. Tor 0.2.9 has a more thorough set of
2453 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
2454 monotonic time interfaces. Fixes bug 20865. Bugfix
2457 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
2458 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
2459 architectures. Closes ticket 20588.
2462 Changes in version 0.2.8.10 - 2016-12-02
2463 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
2464 unusable after they left standby mode. It also backports fixes for
2465 a few portability issues and a small but problematic memory leak.
2467 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
2468 - When Tor leaves standby because of a new application request, open
2469 circuits as needed to serve that request. Previously, we would
2470 potentially wait a very long time. Fixes part of bug 19969; bugfix
2473 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
2474 - Clients now respond to new application stream requests immediately
2475 when they arrive, rather than waiting up to one second before
2476 starting to handle them. Fixes part of bug 19969; bugfix
2479 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
2480 - Work around a bug in the OSX 10.12 SDK that would prevent us from
2481 successfully targeting earlier versions of OSX. Resolves
2484 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
2485 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
2486 20551; bugfix on 0.2.1.1-alpha.
2488 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
2489 - Work around a memory leak in OpenSSL 1.1 when encoding public
2490 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
2492 o Minor features (geoip):
2493 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
2496 Changes in version 0.2.9.6-rc - 2016-12-02
2497 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
2498 version. We hope that it will be ready to become stable soon, and we
2499 encourage everyone to test this release. If no showstopper bugs are
2500 found here, the next 0.2.9 release will be stable.
2502 o Major bugfixes (relay, resolver, logging):
2503 - For relays that don't know their own address, avoid attempting a
2504 local hostname resolve for each descriptor we download. This
2505 will cut down on the number of "Success: chose address 'x.x.x.x'"
2506 log lines, and also avoid confusing clock jumps if the resolver
2507 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
2509 o Minor bugfixes (client, fascistfirewall):
2510 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
2511 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
2513 o Minor bugfixes (hidden services):
2514 - Stop ignoring the anonymity status of saved keys for hidden
2515 services and single onion services when first starting tor.
2516 Instead, refuse to start tor if any hidden service key has been
2517 used in a different hidden service anonymity mode. Fixes bug
2518 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
2520 o Minor bugfixes (portability):
2521 - Work around a bug in the OSX 10.12 SDK that would prevent us from
2522 successfully targeting earlier versions of OSX. Resolves
2524 - Run correctly when built on Windows build environments that
2525 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
2527 o Minor bugfixes (single onion services, Tor2web):
2528 - Stop complaining about long-term one-hop circuits deliberately
2529 created by single onion services and Tor2web. These log messages
2530 are intended to diagnose issue 8387, which relates to circuits
2531 hanging around forever for no reason. Fixes bug 20613; bugfix on
2532 0.2.9.1-alpha. Reported by "pastly".
2534 o Minor bugfixes (unit tests):
2535 - Stop spurious failures in the local interface address discovery
2536 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
2540 - Correct the minimum bandwidth value in torrc.sample, and queue a
2541 corresponding change for torrc.minimal. Closes ticket 20085.
2544 Changes in version 0.2.9.5-alpha - 2016-11-08
2545 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
2546 version. We believe one or two probably remain, and we encourage
2547 everyone to test this release.
2549 o Major bugfixes (client performance):
2550 - Clients now respond to new application stream requests immediately
2551 when they arrive, rather than waiting up to one second before
2552 starting to handle them. Fixes part of bug 19969; bugfix
2555 o Major bugfixes (client reliability):
2556 - When Tor leaves standby because of a new application request, open
2557 circuits as needed to serve that request. Previously, we would
2558 potentially wait a very long time. Fixes part of bug 19969; bugfix
2561 o Major bugfixes (download scheduling):
2562 - When using an exponential backoff schedule, do not give up on
2563 downloading just because we have failed a bunch of times. Since
2564 each delay is longer than the last, retrying indefinitely won't
2565 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
2566 - If a consensus expires while we are waiting for certificates to
2567 download, stop waiting for certificates.
2568 - If we stop waiting for certificates less than a minute after we
2569 started downloading them, do not consider the certificate download
2570 failure a separate failure. Fixes bug 20533; bugfix
2572 - Remove the maximum delay on exponential-backoff scheduling. Since
2573 we now allow an infinite number of failures (see ticket 20536), we
2574 must now allow the time to grow longer on each failure. Fixes part
2575 of bug 20534; bugfix on 0.2.9.1-alpha.
2576 - Make our initial download delays closer to those from 0.2.8. Fixes
2577 another part of bug 20534; bugfix on 0.2.9.1-alpha.
2578 - When determining when to download a directory object, handle times
2579 after 2038 if the operating system supports them. (Someday this
2580 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
2581 - When using exponential backoff in test networks, use a lower
2582 exponent, so the delays do not vary as much. This helps test
2583 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
2585 o Minor features (geoip):
2586 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
2589 o Minor bugfixes (client directory scheduling):
2590 - Treat "relay too busy to answer request" as a failed request and a
2591 reason to back off on our retry frequency. This is safe now that
2592 exponential backoffs retry indefinitely, and avoids a bug where we
2593 would reset our download schedule erroneously. Fixes bug 20593;
2594 bugfix on 0.2.9.1-alpha.
2596 o Minor bugfixes (client, logging):
2597 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
2598 assume all nodes support EXTEND2. Use ntor whenever a key is
2599 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
2600 - On DNSPort, stop logging a BUG warning on a failed hostname
2601 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
2603 o Minor bugfixes (hidden services):
2604 - When configuring hidden services, check every hidden service
2605 directory's permissions. Previously, we only checked the last
2606 hidden service. Fixes bug 20529; bugfix the work to fix 13942
2609 o Minor bugfixes (portability):
2610 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
2611 architectures. Closes ticket 20588.
2612 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
2613 removed the ECDH ciphers which caused the tests to fail on
2614 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
2615 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
2616 20551; bugfix on 0.2.1.1-alpha.
2618 o Minor bugfixes (relay bootstrap):
2619 - Ensure relays don't make multiple connections during bootstrap.
2620 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
2622 o Minor bugfixes (relay):
2623 - Work around a memory leak in OpenSSL 1.1 when encoding public
2624 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
2625 - Avoid a small memory leak when informing worker threads about
2626 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
2627 - Do not try to parallelize workers more than 16x without the user
2628 explicitly configuring us to do so, even if we do detect more than
2629 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
2631 o Minor bugfixes (single onion services):
2632 - Start correctly when creating a single onion service in a
2633 directory that did not previously exist. Fixes bug 20484; bugfix
2636 o Minor bugfixes (testing):
2637 - Avoid a unit test failure on systems with over 16 detectable CPU
2638 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
2641 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
2642 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
2643 - Module-level documentation for several more modules. Closes
2644 tickets 19287 and 19290.
2647 Changes in version 0.2.8.9 - 2016-10-17
2648 Tor 0.2.8.9 backports a fix for a security hole in previous versions
2649 of Tor that would allow a remote attacker to crash a Tor client,
2650 hidden service, relay, or authority. All Tor users should upgrade to
2651 this version, or to 0.2.9.4-alpha. Patches will be released for older
2654 o Major features (security fixes, also in 0.2.9.4-alpha):
2655 - Prevent a class of security bugs caused by treating the contents
2656 of a buffer chunk as if they were a NUL-terminated string. At
2657 least one such bug seems to be present in all currently used
2658 versions of Tor, and would allow an attacker to remotely crash
2659 most Tor instances, especially those compiled with extra compiler
2660 hardening. With this defense in place, such bugs can't crash Tor,
2661 though we should still fix them as they occur. Closes ticket
2662 20384 (TROVE-2016-10-001).
2664 o Minor features (geoip):
2665 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
2669 Changes in version 0.2.9.4-alpha - 2016-10-17
2670 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
2671 that would allow a remote attacker to crash a Tor client, hidden
2672 service, relay, or authority. All Tor users should upgrade to this
2673 version, or to 0.2.8.9. Patches will be released for older versions
2676 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
2677 previous versions of Tor, including the implementation of a feature to
2678 future- proof the Tor ecosystem against protocol changes, some bug
2679 fixes necessary for Tor Browser to use unix domain sockets correctly,
2680 and several portability improvements. We anticipate that this will be
2681 the last alpha in the Tor 0.2.9 series, and that the next release will
2682 be a release candidate.
2684 o Major features (security fixes):
2685 - Prevent a class of security bugs caused by treating the contents
2686 of a buffer chunk as if they were a NUL-terminated string. At
2687 least one such bug seems to be present in all currently used
2688 versions of Tor, and would allow an attacker to remotely crash
2689 most Tor instances, especially those compiled with extra compiler
2690 hardening. With this defense in place, such bugs can't crash Tor,
2691 though we should still fix them as they occur. Closes ticket
2692 20384 (TROVE-2016-10-001).
2694 o Major features (subprotocol versions):
2695 - Tor directory authorities now vote on a set of recommended
2696 subprotocol versions, and on a set of required subprotocol
2697 versions. Clients and relays that lack support for a _required_
2698 subprotocol version will not start; those that lack support for a
2699 _recommended_ subprotocol version will warn the user to upgrade.
2700 Closes ticket 19958; implements part of proposal 264.
2701 - Tor now uses "subprotocol versions" to indicate compatibility.
2702 Previously, versions of Tor looked at the declared Tor version of
2703 a relay to tell whether they could use a given feature. Now, they
2704 should be able to rely on its declared subprotocol versions. This
2705 change allows compatible implementations of the Tor protocol(s) to
2706 exist without pretending to be 100% bug-compatible with particular
2707 releases of Tor itself. Closes ticket 19958; implements part of
2710 o Minor feature (fallback directories):
2711 - Remove broken fallbacks from the hard-coded fallback directory
2712 list. Closes ticket 20190; patch by teor.
2714 o Minor features (client, directory):
2715 - Since authorities now omit all routers that lack the Running and
2716 Valid flags, we assume that any relay listed in the consensus must
2717 have those flags. Closes ticket 20001; implements part of
2720 o Minor features (compilation, portability):
2721 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
2724 o Minor features (development tools, etags):
2725 - Teach the "make tags" Makefile target how to correctly find
2726 "MOCK_IMPL" function definitions. Patch from nherring; closes
2729 o Minor features (geoip):
2730 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
2733 o Minor features (unix domain sockets):
2734 - When configuring a unix domain socket for a SocksPort,
2735 ControlPort, or Hidden service, you can now wrap the address in
2736 quotes, using C-style escapes inside the quotes. This allows unix
2737 domain socket paths to contain spaces.
2739 o Minor features (virtual addresses):
2740 - Increase the maximum number of bits for the IPv6 virtual network
2741 prefix from 16 to 104. In this way, the condition for address
2742 allocation is less restrictive. Closes ticket 20151; feature
2745 o Minor bugfixes (address discovery):
2746 - Stop reordering IP addresses returned by the OS. This makes it
2747 more likely that Tor will guess the same relay IP address every
2748 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
2749 Reported by René Mayrhofer, patch by "cypherpunks".
2751 o Minor bugfixes (client, unix domain sockets):
2752 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
2753 the client address is meaningless. Fixes bug 20261; bugfix
2756 o Minor bugfixes (compilation, OpenBSD):
2757 - Detect Libevent2 functions correctly on systems that provide
2758 libevent2, but where libevent1 is linked with -levent. Fixes bug
2759 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
2761 o Minor bugfixes (configuration):
2762 - When parsing quoted configuration values from the torrc file,
2763 handle windows line endings correctly. Fixes bug 19167; bugfix on
2764 0.2.0.16-alpha. Patch from "Pingl".
2766 o Minor bugfixes (getpass):
2767 - Defensively fix a non-triggerable heap corruption at do_getpass()
2768 to protect ourselves from mistakes in the future. Fixes bug
2769 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
2772 o Minor bugfixes (hidden service):
2773 - Allow hidden services to run on IPv6 addresses even when the
2774 IPv6Exit option is not set. Fixes bug 18357; bugfix
2778 - Add module-level internal documentation for 36 C files that
2779 previously didn't have a high-level overview. Closes ticket #20385.
2781 o Required libraries:
2782 - When building with OpenSSL, Tor now requires version 1.0.1 or
2783 later. OpenSSL 1.0.0 and earlier are no longer supported by the
2784 OpenSSL team, and should not be used. Closes ticket 20303.
2787 Changes in version 0.2.9.3-alpha - 2016-09-23
2788 Tor 0.2.9.3-alpha adds improved support for entities that want to make
2789 high-performance services available through the Tor .onion mechanism
2790 without themselves receiving anonymity as they host those services. It
2791 also tries harder to ensure that all steps on a circuit are using the
2792 strongest crypto possible, strengthens some TLS properties, and
2793 resolves several bugs -- including a pair of crash bugs from the 0.2.8
2794 series. Anybody running an earlier version of 0.2.9.x should upgrade.
2796 o Major bugfixes (crash, also in 0.2.8.8):
2797 - Fix a complicated crash bug that could affect Tor clients
2798 configured to use bridges when replacing a networkstatus consensus
2799 in which one of their bridges was mentioned. OpenBSD users saw
2800 more crashes here, but all platforms were potentially affected.
2801 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
2803 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
2804 - Fix a timing-dependent assertion failure that could occur when we
2805 tried to flush from a circuit after having freed its cells because
2806 of an out-of-memory condition. Fixes bug 20203; bugfix on
2807 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
2810 o Major features (circuit building, security):
2811 - Authorities, relays and clients now require ntor keys in all
2812 descriptors, for all hops (except for rare hidden service protocol
2813 cases), for all circuits, and for all other roles. Part of
2815 - Tor authorities, relays, and clients only use ntor, except for
2816 rare cases in the hidden service protocol. Part of ticket 19163.
2818 o Major features (single-hop "hidden" services):
2819 - Add experimental HiddenServiceSingleHopMode and
2820 HiddenServiceNonAnonymousMode options. When both are set to 1,
2821 every hidden service on a Tor instance becomes a non-anonymous
2822 Single Onion Service. Single Onions make one-hop (direct)
2823 connections to their introduction and renzedvous points. One-hop
2824 circuits make Single Onion servers easily locatable, but clients
2825 remain location-anonymous. This is compatible with the existing
2826 hidden service implementation, and works on the current tor
2827 network without any changes to older relays or clients. Implements
2828 proposal 260, completes ticket 17178. Patch by teor and asn.
2830 o Major features (resource management):
2831 - Tor can now notice it is about to run out of sockets, and
2832 preemptively close connections of lower priority. (This feature is
2833 off by default for now, since the current prioritizing method is
2834 yet not mature enough. You can enable it by setting
2835 "DisableOOSCheck 0", but watch out: it might close some sockets
2836 you would rather have it keep.) Closes ticket 18640.
2838 o Major bugfixes (circuit building):
2839 - Hidden service client-to-intro-point and service-to-rendezvous-
2840 point circuits use the TAP key supplied by the protocol, to avoid
2841 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
2843 o Major bugfixes (compilation, OpenBSD):
2844 - Fix a Libevent-detection bug in our autoconf script that would
2845 prevent Tor from linking successfully on OpenBSD. Patch from
2846 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
2848 o Major bugfixes (hidden services):
2849 - Clients now require hidden services to include the TAP keys for
2850 their intro points in the hidden service descriptor. This prevents
2851 an inadvertent upgrade to ntor, which a malicious hidden service
2852 could use to distinguish clients by consensus version. Fixes bug
2853 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
2855 o Minor features (security, TLS):
2856 - Servers no longer support clients that without AES ciphersuites.
2857 (3DES is no longer considered an acceptable cipher.) We believe
2858 that no such Tor clients currently exist, since Tor has required
2859 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
2861 o Minor feature (fallback directories):
2862 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
2863 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
2864 2016. Closes ticket 20190; patch by teor.
2866 o Minor features (geoip, also in 0.2.8.8):
2867 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
2870 o Minor feature (port flags):
2871 - Add new flags to the *Port options to finer control over which
2872 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
2873 and the synthetic flag OnionTrafficOnly, which is equivalent to
2874 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
2875 18693; patch by "teor".
2877 o Minor features (directory authority):
2878 - After voting, if the authorities decide that a relay is not
2879 "Valid", they no longer include it in the consensus at all. Closes
2880 ticket 20002; implements part of proposal 272.
2882 o Minor features (testing):
2883 - Disable memory protections on OpenBSD when performing our unit
2884 tests for memwipe(). The test deliberately invokes undefined
2885 behavior, and the OpenBSD protections interfere with this. Patch
2886 from "rubiate". Closes ticket 20066.
2888 o Minor features (testing, ipv6):
2889 - Add the single-onion and single-onion-ipv6 chutney targets to
2890 "make test-network-all". This requires a recent chutney version
2891 with the single onion network flavours (git c72a652 or later).
2892 Closes ticket 20072; patch by teor.
2893 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
2894 tests. Remove bridges+hs, as it's somewhat redundant. This
2895 requires a recent chutney version that supports IPv6 clients,
2896 relays, and authorities. Closes ticket 20069; patch by teor.
2898 o Minor features (Tor2web):
2899 - Make Tor2web clients respect ReachableAddresses. This feature was
2900 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
2901 0.2.8.7. Implements feature 20034. Patch by teor.
2903 o Minor features (unit tests):
2904 - We've done significant work to make the unit tests run faster.
2905 - Our link-handshake unit tests now check that when invalid
2906 handshakes fail, they fail with the error messages we expected.
2907 - Our unit testing code that captures log messages no longer
2908 prevents them from being written out if the user asked for them
2909 (by passing --debug or --info or or --notice --warn to the "test"
2910 binary). This change prevents us from missing unexpected log
2911 messages simply because we were looking for others. Related to
2913 - The unit tests now log all warning messages with the "BUG" flag.
2914 Previously, they only logged errors by default. This change will
2915 help us make our testing code more correct, and make sure that we
2916 only hit this code when we mean to. In the meantime, however,
2917 there will be more warnings in the unit test logs than before.
2918 This is preparatory work for ticket 19999.
2919 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
2920 assertion as a test failure.
2922 o Minor bug fixes (circuits):
2923 - Use the CircuitBuildTimeout option whenever
2924 LearnCircuitBuildTimeout is disabled. Previously, we would respect
2925 the option when a user disabled it, but not when it was disabled
2926 because some other option was set. Fixes bug 20073; bugfix on
2927 0.2.4.12-alpha. Patch by teor.
2929 o Minor bugfixes (allocation):
2930 - Change how we allocate memory for large chunks on buffers, to
2931 avoid a (currently impossible) integer overflow, and to waste less
2932 space when allocating unusually large chunks. Fixes bug 20081;
2933 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
2934 - Always include orconfig.h before including any other C headers.
2935 Sometimes, it includes macros that affect the behavior of the
2936 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
2937 first version to use AC_USE_SYSTEM_EXTENSIONS).
2938 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
2939 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
2940 Patch from Gisle Vanem.
2941 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
2942 They apparently require a set of annotations that we aren't
2943 currently using, and they create false positives in our pthreads
2944 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
2946 o Minor bugfixes (directory authority):
2947 - Die with a more useful error when the operator forgets to place
2948 the authority_signing_key file into the keys directory. This
2949 avoids an uninformative assert & traceback about having an invalid
2950 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
2951 - When allowing private addresses, mark Exits that only exit to
2952 private locations as such. Fixes bug 20064; bugfix
2955 o Minor bugfixes (documentation):
2956 - Document the default PathsNeededToBuildCircuits value that's used
2957 by clients when the directory authorities don't set
2958 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
2959 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
2960 - Fix manual for the User option: it takes a username, not a UID.
2961 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
2964 o Minor bugfixes (hidden services):
2965 - Stop logging intro point details to the client log on certain
2966 error conditions. Fixed as part of bug 20012; bugfix on
2967 0.2.4.8-alpha. Patch by teor.
2969 o Minor bugfixes (IPv6, testing):
2970 - Check for IPv6 correctly on Linux when running test networks.
2971 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
2973 o Minor bugfixes (Linux seccomp2 sandbox):
2974 - Add permission to run the sched_yield() and sigaltstack() system
2975 calls, in order to support versions of Tor compiled with asan or
2976 ubsan code that use these calls. Now "sandbox 1" and
2977 "--enable-expensive-hardening" should be compatible on more
2978 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
2980 o Minor bugfixes (logging):
2981 - When logging a message from the BUG() macro, be explicit about
2982 what we were asserting. Previously we were confusing what we were
2983 asserting with what the bug was. Fixes bug 20093; bugfix
2985 - When we are unable to remove the bw_accounting file, do not warn
2986 if the reason we couldn't remove it was that it didn't exist.
2987 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
2989 o Minor bugfixes (option parsing):
2990 - Count unix sockets when counting client listeners (SOCKS, Trans,
2991 NATD, and DNS). This has no user-visible behaviour changes: these
2992 options are set once, and never read. Required for correct
2993 behaviour in ticket 17178. Fixes bug 19677; bugfix on
2994 0.2.6.3-alpha. Patch by teor.
2996 o Minor bugfixes (options):
2997 - Check the consistency of UseEntryGuards and EntryNodes more
2998 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
3000 - Stop changing the configured value of UseEntryGuards on
3001 authorities and Tor2web clients. Fixes bug 20074; bugfix on
3002 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
3005 o Minor bugfixes (Tor2web):
3006 - Prevent Tor2web clients running hidden services, these services
3007 are not anonymous due to the one-hop client paths. Fixes bug
3008 19678. Patch by teor.
3010 o Minor bugfixes (unit tests):
3011 - Fix a shared-random unit test that was failing on big endian
3012 architectures due to internal representation of a integer copied
3013 to a buffer. The test is changed to take a full 32 bytes of data
3014 and use the output of a python script that make the COMMIT and
3015 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
3017 - The tor_tls_server_info_callback unit test no longer crashes when
3018 debug-level logging is turned on. Fixes bug 20041; bugfix
3022 Changes in version 0.2.8.8 - 2016-09-23
3023 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
3024 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
3025 who select public relays as their bridges.
3027 o Major bugfixes (crash):
3028 - Fix a complicated crash bug that could affect Tor clients
3029 configured to use bridges when replacing a networkstatus consensus
3030 in which one of their bridges was mentioned. OpenBSD users saw
3031 more crashes here, but all platforms were potentially affected.
3032 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
3034 o Major bugfixes (relay, OOM handler):
3035 - Fix a timing-dependent assertion failure that could occur when we
3036 tried to flush from a circuit after having freed its cells because
3037 of an out-of-memory condition. Fixes bug 20203; bugfix on
3038 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
3041 o Minor feature (fallback directories):
3042 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
3043 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
3044 2016. Closes ticket 20190; patch by teor.
3046 o Minor features (geoip):
3047 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
3051 Changes in version 0.2.9.2-alpha - 2016-08-24
3052 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
3053 several new features and bugfixes. It also includes an important
3054 authority update and an important bugfix from 0.2.8.7. Everyone who
3055 sets the ReachableAddresses option, and all bridges, are strongly
3056 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
3058 o Directory authority changes (also in 0.2.8.7):
3059 - The "Tonga" bridge authority has been retired; the new bridge
3060 authority is "Bifroest". Closes tickets 19728 and 19690.
3062 o Major bugfixes (client, security, also in 0.2.8.7):
3063 - Only use the ReachableAddresses option to restrict the first hop
3064 in a path. In earlier versions of 0.2.8.x, it would apply to
3065 every hop in the path, with a possible degradation in anonymity
3066 for anyone using an uncommon ReachableAddress setting. Fixes bug
3067 19973; bugfix on 0.2.8.2-alpha.
3069 o Major features (user interface):
3070 - Tor now supports the ability to declare options deprecated, so
3071 that we can recommend that people stop using them. Previously,
3072 this was done in an ad-hoc way. Closes ticket 19820.
3074 o Major bugfixes (directory downloads):
3075 - Avoid resetting download status for consensuses hourly, since we
3076 already have another, smarter retry mechanism. Fixes bug 8625;
3077 bugfix on 0.2.0.9-alpha.
3079 o Minor features (config):
3080 - Warn users when descriptor and port addresses are inconsistent.
3081 Mitigates bug 13953; patch by teor.
3083 o Minor features (geoip):
3084 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
3087 o Minor features (user interface):
3088 - There is a new --list-deprecated-options command-line option to
3089 list all of the deprecated options. Implemented as part of
3092 o Minor bugfixes (code style):
3093 - Fix an integer signedness conversion issue in the case conversion
3094 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
3096 o Minor bugfixes (compilation):
3097 - Build correctly on versions of libevent2 without support for
3098 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
3100 - Fix a compilation warning on GCC versions before 4.6. Our
3101 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
3102 when it is also required as an argument to the compiler pragma.
3103 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
3105 o Minor bugfixes (compilation, also in 0.2.8.7):
3106 - Remove an inappropriate "inline" in tortls.c that was causing
3107 warnings on older versions of GCC. Fixes bug 19903; bugfix
3110 o Minor bugfixes (fallback directories, also in 0.2.8.7):
3111 - Avoid logging a NULL string pointer when loading fallback
3112 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
3113 and 0.2.8.1-alpha. Report and patch by "rubiate".
3115 o Minor bugfixes (logging):
3116 - Log a more accurate message when we fail to dump a microdescriptor.
3117 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
3119 o Minor bugfixes (memory leak):
3120 - Fix a series of slow memory leaks related to parsing torrc files
3121 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
3123 o Deprecated features:
3124 - A number of DNS-cache-related sub-options for client ports are now
3125 deprecated for security reasons, and may be removed in a future
3126 version of Tor. (We believe that client-side DNS cacheing is a bad
3127 idea for anonymity, and you should not turn it on.) The options
3128 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
3129 UseIPv4Cache, and UseIPv6Cache.
3130 - A number of options are deprecated for security reasons, and may
3131 be removed in a future version of Tor. The options are:
3132 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
3133 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
3134 CloseHSClientCircuitsImmediatelyOnTimeout,
3135 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
3136 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
3137 UseNTorHandshake, and WarnUnsafeSocks.
3138 - The *ListenAddress options are now deprecated as unnecessary: the
3139 corresponding *Port options should be used instead. These options
3140 may someday be removed. The affected options are:
3141 ControlListenAddress, DNSListenAddress, DirListenAddress,
3142 NATDListenAddress, ORListenAddress, SocksListenAddress,
3143 and TransListenAddress.
3146 - Correct the IPv6 syntax in our documentation for the
3147 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
3150 - We no longer include the (dead, deprecated) bufferevent code in
3151 Tor. Closes ticket 19450. Based on a patch from U+039b.
3154 Changes in version 0.2.8.7 - 2016-08-24
3155 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
3156 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
3157 who sets the ReachableAddresses option, and all bridges, are strongly
3158 encouraged to upgrade.
3160 o Directory authority changes:
3161 - The "Tonga" bridge authority has been retired; the new bridge
3162 authority is "Bifroest". Closes tickets 19728 and 19690.
3164 o Major bugfixes (client, security):
3165 - Only use the ReachableAddresses option to restrict the first hop
3166 in a path. In earlier versions of 0.2.8.x, it would apply to
3167 every hop in the path, with a possible degradation in anonymity
3168 for anyone using an uncommon ReachableAddress setting. Fixes bug
3169 19973; bugfix on 0.2.8.2-alpha.
3171 o Minor features (geoip):
3172 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
3175 o Minor bugfixes (compilation):
3176 - Remove an inappropriate "inline" in tortls.c that was causing
3177 warnings on older versions of GCC. Fixes bug 19903; bugfix
3180 o Minor bugfixes (fallback directories):
3181 - Avoid logging a NULL string pointer when loading fallback
3182 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
3183 and 0.2.8.1-alpha. Report and patch by "rubiate".
3186 Changes in version 0.2.9.1-alpha - 2016-08-08
3187 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
3188 series. It improves our support for hardened builds and compiler
3189 warnings, deploys some critical infrastructure for improvements to
3190 hidden services, includes a new timing backend that we hope to use for
3191 better support for traffic padding, makes it easier for programmers to
3192 log unexpected events, and contains other small improvements to
3193 security, correctness, and performance.
3195 Below are the changes since 0.2.8.6.
3197 o New system requirements:
3198 - Tor now requires Libevent version 2.0.10-stable or later. Older
3199 versions of Libevent have less efficient backends for several
3200 platforms, and lack the DNS code that we use for our server-side
3201 DNS support. This implements ticket 19554.
3202 - Tor now requires zlib version 1.2 or later, for security,
3203 efficiency, and (eventually) gzip support. (Back when we started,
3204 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
3205 released in 2003. We recommend the latest version.)
3207 o Major features (build, hardening):
3208 - Tor now builds with -ftrapv by default on compilers that support
3209 it. This option detects signed integer overflow (which C forbids),
3210 and turns it into a hard-failure. We do not apply this option to
3211 code that needs to run in constant time to avoid side-channels;
3212 instead, we use -fwrapv in that code. Closes ticket 17983.
3213 - When --enable-expensive-hardening is selected, stop applying the
3214 clang/gcc sanitizers to code that needs to run in constant time.
3215 Although we are aware of no introduced side-channels, we are not
3216 able to prove that there are none. Related to ticket 17983.
3218 o Major features (compilation):
3219 - Our big list of extra GCC warnings is now enabled by default when
3220 building with GCC (or with anything like Clang that claims to be
3221 GCC-compatible). To make all warnings into fatal compilation
3222 errors, pass --enable-fatal-warnings to configure. Closes
3224 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
3225 turn on C and POSIX extensions. (Previously, we attempted to do
3226 this on an ad hoc basis.) Closes ticket 19139.
3228 o Major features (directory authorities, hidden services):
3229 - Directory authorities can now perform the shared randomness
3230 protocol specified by proposal 250. Using this protocol, directory
3231 authorities generate a global fresh random value every day. In the
3232 future, this value will be used by hidden services to select
3233 HSDirs. This release implements the directory authority feature;
3234 the hidden service side will be implemented in the future as part
3235 of proposal 224. Resolves ticket 16943; implements proposal 250.
3237 o Major features (downloading, random exponential backoff):
3238 - When we fail to download an object from a directory service, wait
3239 for an (exponentially increasing) randomized amount of time before
3240 retrying, rather than a fixed interval as we did before. This
3241 prevents a group of Tor instances from becoming too synchronized,
3242 or a single Tor instance from becoming too predictable, in its
3243 download schedule. Closes ticket 15942.
3245 o Major bugfixes (exit policies):
3246 - Avoid disclosing exit outbound bind addresses, configured port
3247 bind addresses, and local interface addresses in relay descriptors
3248 by default under ExitPolicyRejectPrivate. Instead, only reject
3249 these (otherwise unlisted) addresses if
3250 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
3251 0.2.7.2-alpha. Patch by teor.
3253 o Major bugfixes (hidden service client):
3254 - Allow Tor clients with appropriate controllers to work with
3255 FetchHidServDescriptors set to 0. Previously, this option also
3256 disabled descriptor cache lookup, thus breaking hidden services
3257 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
3259 o Minor features (build, hardening):
3260 - Detect and work around a libclang_rt problem that would prevent
3261 clang from finding __mulodi4() on some 32-bit platforms, and thus
3262 keep -ftrapv from linking on those systems. Closes ticket 19079.
3263 - When building on a system without runtime support for the runtime
3264 hardening options, try to log a useful warning at configuration
3265 time, rather than an incomprehensible warning at link time. If
3266 expensive hardening was requested, this warning becomes an error.
3267 Closes ticket 18895.
3269 o Minor features (code safety):
3270 - In our integer-parsing functions, ensure that maxiumum value we
3271 give is no smaller than the minimum value. Closes ticket 19063;
3274 o Minor features (controller):
3275 - Implement new GETINFO queries for all downloads that use
3276 download_status_t to schedule retries. This allows controllers to
3277 examine the schedule for pending downloads. Closes ticket 19323.
3278 - Allow controllers to configure basic client authorization on
3279 hidden services when they create them with the ADD_ONION control
3280 command. Implements ticket 15588. Patch by "special".
3281 - Fire a STATUS_SERVER controller event whenever the hibernation
3282 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
3284 o Minor features (directory authority):
3285 - Directory authorities now only give the Guard flag to a relay if
3286 they are also giving it the Stable flag. This change allows us to
3287 simplify path selection for clients. It should have minimal effect
3288 in practice, since >99% of Guards already have the Stable flag.
3289 Implements ticket 18624.
3290 - Directory authorities now write their v3-status-votes file out to
3291 disk earlier in the consensus process, so we have a record of the
3292 votes even if we abort the consensus process. Resolves
3295 o Minor features (hidden service):
3296 - Stop being so strict about the payload length of "rendezvous1"
3297 cells. We used to be locked in to the "TAP" handshake length, and
3298 now we can handle better handshakes like "ntor". Resolves
3301 o Minor features (infrastructure, time):
3302 - Tor now uses the operating system's monotonic timers (where
3303 available) for internal fine-grained timing. Previously we would
3304 look at the system clock, and then attempt to compensate for the
3305 clock running backwards. Closes ticket 18908.
3306 - Tor now includes an improved timer backend, so that we can
3307 efficiently support tens or hundreds of thousands of concurrent
3308 timers, as will be needed for some of our planned anti-traffic-
3309 analysis work. This code is based on William Ahern's "timeout.c"
3310 project, which implements a "tickless hierarchical timing wheel".
3311 Closes ticket 18365.
3313 o Minor features (logging):
3314 - Provide a more useful warning message when configured with an
3315 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
3316 - When dumping unparseable router descriptors, optionally store them
3317 in separate files, named by digest, up to a configurable size
3318 limit. You can change the size limit by setting the
3319 MaxUnparseableDescSizeToLog option, and disable this feature by
3320 setting that option to 0. Closes ticket 18322.
3321 - Add a set of macros to check nonfatal assertions, for internal
3322 use. Migrating more of our checks to these should help us avoid
3323 needless crash bugs. Closes ticket 18613.
3325 o Minor features (performance):
3326 - Changer the "optimistic data" extension from "off by default" to
3327 "on by default". The default was ordinarily overridden by a
3328 consensus option, but when clients were bootstrapping for the
3329 first time, they would not have a consensus to get the option
3330 from. Changing this default When fetching a consensus for the
3331 first time, use optimistic data. This saves a round-trip during
3332 startup. Closes ticket 18815.
3334 o Minor features (relay, usability):
3335 - When the directory authorities refuse a bad relay's descriptor,
3336 encourage the relay operator to contact us. Many relay operators
3337 won't notice this line in their logs, but it's a win if even a few
3338 learn why we don't like what their relay was doing. Resolves
3341 o Minor features (testing):
3342 - Let backtrace tests work correctly under AddressSanitizer. Fixes
3343 part of bug 18934; bugfix on 0.2.5.2-alpha.
3344 - Move the test-network.sh script to chutney, and modify tor's test-
3345 network.sh to call the (newer) chutney version when available.
3346 Resolves ticket 19116. Patch by teor.
3347 - Use the lcov convention for marking lines as unreachable, so that
3348 we don't count them when we're generating test coverage data.
3349 Update our coverage tools to understand this convention. Closes
3352 o Minor bugfixes (bootstrap):
3353 - Remember the directory we fetched the consensus or previous
3354 certificates from, and use it to fetch future authority
3355 certificates. This change improves bootstrapping performance.
3356 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
3358 o Minor bugfixes (build):
3359 - The test-stem and test-network makefile targets now depend only on
3360 the tor binary that they are testing. Previously, they depended on
3361 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
3362 patch from "cypherpunks".
3364 o Minor bugfixes (circuits):
3365 - Make sure extend_info_from_router() is only called on servers.
3366 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
3368 o Minor bugfixes (compilation):
3369 - When building with Clang, use a full set of GCC warnings.
3370 (Previously, we included only a subset, because of the way we
3371 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
3373 o Minor bugfixes (directory authority):
3374 - Authorities now sort the "package" lines in their votes, for ease
3375 of debugging. (They are already sorted in consensus documents.)
3376 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
3377 - When parsing a detached signature, make sure we use the length of
3378 the digest algorithm instead of an hardcoded DIGEST256_LEN in
3379 order to avoid comparing bytes out-of-bounds with a smaller digest
3380 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
3382 o Minor bugfixes (documentation):
3383 - Document the --passphrase-fd option in the tor manpage. Fixes bug
3384 19504; bugfix on 0.2.7.3-rc.
3385 - Fix the description of the --passphrase-fd option in the
3386 tor-gencert manpage. The option is used to pass the number of a
3387 file descriptor to read the passphrase from, not to read the file
3388 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
3390 o Minor bugfixes (ephemeral hidden service):
3391 - When deleting an ephemeral hidden service, close its intro points
3392 even if they are not completely open. Fixes bug 18604; bugfix
3395 o Minor bugfixes (guard selection):
3396 - Use a single entry guard even if the NumEntryGuards consensus
3397 parameter is not provided. Fixes bug 17688; bugfix
3399 - Don't mark guards as unreachable if connection_connect() fails.
3400 That function fails for local reasons, so it shouldn't reveal
3401 anything about the status of the guard. Fixes bug 14334; bugfix
3404 o Minor bugfixes (hidden service client):
3405 - Increase the minimum number of internal circuits we preemptively
3406 build from 2 to 3, so a circuit is available when a client
3407 connects to another onion service. Fixes bug 13239; bugfix
3410 o Minor bugfixes (logging):
3411 - When logging a directory ownership mismatch, log the owning
3412 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
3414 o Minor bugfixes (memory leaks):
3415 - Fix a small, uncommon memory leak that could occur when reading a
3416 truncated ed25519 key file. Fixes bug 18956; bugfix
3419 o Minor bugfixes (testing):
3420 - Allow clients to retry HSDirs much faster in test networks. Fixes
3421 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
3422 - Disable ASAN's detection of segmentation faults while running
3423 test_bt.sh, so that we can make sure that our own backtrace
3424 generation code works. Fixes another aspect of bug 18934; bugfix
3425 on 0.2.5.2-alpha. Patch from "cypherpunks".
3426 - Fix the test-network-all target on out-of-tree builds by using the
3427 correct path to the test driver script. Fixes bug 19421; bugfix
3430 o Minor bugfixes (time):
3431 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
3432 bugfix on all released tor versions.
3433 - When computing the difference between two times in milliseconds,
3434 we now round to the nearest millisecond correctly. Previously, we
3435 could sometimes round in the wrong direction. Fixes bug 19428;
3436 bugfix on 0.2.2.2-alpha.
3438 o Minor bugfixes (user interface):
3439 - Display a more accurate number of suppressed messages in the log
3440 rate-limiter. Previously, there was a potential integer overflow
3441 in the counter. Now, if the number of messages hits a maximum, the
3442 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
3444 - Fix a typo in the passphrase prompt for the ed25519 identity key.
3445 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
3447 o Code simplification and refactoring:
3448 - Remove redundant declarations of the MIN macro. Closes
3450 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
3451 Closes ticket 18462; patch from "icanhasaccount".
3452 - Split the 600-line directory_handle_command_get function into
3453 separate functions for different URL types. Closes ticket 16698.
3456 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
3457 ticket 19153. Patch from "U+039b".
3460 - Remove support for "GET /tor/bytes.txt" DirPort request, and
3461 "GETINFO dir-usage" controller request, which were only available
3462 via a compile-time option in Tor anyway. Feature was added in
3463 0.2.2.1-alpha. Resolves ticket 19035.
3464 - There is no longer a compile-time option to disable support for
3465 TransPort. (If you don't want TransPort; just don't use it.) Patch
3466 from "U+039b". Closes ticket 19449.
3469 - Run more workqueue tests as part of "make check". These had
3470 previously been implemented, but you needed to know special
3471 command-line options to enable them.
3472 - We now have unit tests for our code to reject zlib "compression
3473 bombs". (Fortunately, the code works fine.)
3476 Changes in version 0.2.8.6 - 2016-08-02
3478 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
3480 The Tor 0.2.8 series improves client bootstrapping performance,
3481 completes the authority-side implementation of improved identity
3482 keys for relays, and includes numerous bugfixes and performance
3483 improvements throughout the program. This release continues to
3484 improve the coverage of Tor's test suite. For a full list of
3485 changes since Tor 0.2.7, see the ReleaseNotes file.
3487 Changes since 0.2.8.5-rc:
3489 o Minor features (geoip):
3490 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
3493 o Minor bugfixes (compilation):
3494 - Fix a compilation warning in the unit tests on systems where char
3495 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
3497 o Minor bugfixes (fallback directories):
3498 - Remove 1 fallback that was on the hardcoded list, then opted-out,
3499 leaving 89 of the 100 fallbacks originally introduced in Tor
3500 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
3502 o Minor bugfixes (Linux seccomp2 sandbox):
3503 - Allow more syscalls when running with "Sandbox 1" enabled:
3504 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
3505 some systems, these are required for Tor to start. Fixes bug
3506 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
3507 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
3508 so that get_interface_address6_via_udp_socket_hack() can work.
3509 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
3512 Changes in version 0.2.8.5-rc - 2016-07-07
3513 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
3514 series. If we find no new bugs or regressions here, the first stable
3515 0.2.8 release will be identical to it. It has a few small bugfixes
3516 against previous versions.
3518 o Directory authority changes:
3519 - Urras is no longer a directory authority. Closes ticket 19271.
3521 o Major bugfixes (heartbeat):
3522 - Fix a regression that would crash Tor when the periodic
3523 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
3524 0.2.8.1-alpha. Reported by "kubaku".
3526 o Minor features (build):
3527 - Tor now again builds with the recent OpenSSL 1.1 development
3528 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
3529 - When building manual pages, set the timezone to "UTC", so that the
3530 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
3531 Patch from intrigeri.
3533 o Minor bugfixes (fallback directory selection):
3534 - Avoid errors during fallback selection if there are no eligible
3535 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
3538 o Minor bugfixes (IPv6, microdescriptors):
3539 - Don't check node addresses when we only have a routerstatus. This
3540 allows IPv6-only clients to bootstrap by fetching microdescriptors
3541 from fallback directory mirrors. (The microdescriptor consensus
3542 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
3545 o Minor bugfixes (logging):
3546 - Reduce pointlessly verbose log messages when directory servers
3547 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
3548 0.2.8.1-alpha. Patch by teor.
3549 - When a fallback directory changes its fingerprint from the hard-
3550 coded fingerprint, log a less severe, more explanatory log
3551 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
3553 o Minor bugfixes (Linux seccomp2 sandboxing):
3554 - Allow statistics to be written to disk when "Sandbox 1" is
3555 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
3556 0.2.6.1-alpha respectively.
3558 o Minor bugfixes (user interface):
3559 - Remove a warning message "Service [scrubbed] not found after
3560 descriptor upload". This message appears when one uses HSPOST
3561 control command to upload a service descriptor. Since there is
3562 only a descriptor and no service, showing this message is
3563 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
3565 o Fallback directory list:
3566 - Add a comment to the generated fallback directory list that
3567 explains how to comment out unsuitable fallbacks in a way that's
3568 compatible with the stem fallback parser.
3569 - Update fallback whitelist and blacklist based on relay operator
3570 emails. Blacklist unsuitable (non-working, over-volatile)
3571 fallbacks. Resolves ticket 19071. Patch by teor.
3572 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
3573 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
3574 ticket 19071; patch by teor.
3577 Changes in version 0.2.8.4-rc - 2016-06-15
3578 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
3579 If we find no new bugs or regressions here, the first stable 0.2.8
3580 release will be identical to it. It has a few small bugfixes against
3583 o Major bugfixes (user interface):
3584 - Correctly give a warning in the cases where a relay is specified
3585 by nickname, and one such relay is found, but it is not officially
3586 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
3588 o Minor features (build):
3589 - Tor now builds once again with the recent OpenSSL 1.1 development
3590 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
3592 o Minor features (geoip):
3593 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
3596 o Minor bugfixes (compilation):
3597 - Cause the unit tests to compile correctly on mingw64 versions that
3598 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
3600 o Minor bugfixes (downloading):
3601 - Predict more correctly whether we'll be downloading over HTTP when
3602 we determine the maximum length of a URL. This should avoid a
3603 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
3607 Changes in version 0.2.8.3-alpha - 2016-05-26
3608 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
3609 the course of the 0.2.8 development cycle. It improves the behavior of
3610 directory clients, fixes several crash bugs, fixes a gap in compiler
3611 hardening, and allows the full integration test suite to run on
3614 o Major bugfixes (security, client, DNS proxy):
3615 - Stop a crash that could occur when a client running with DNSPort
3616 received a query with multiple address types, and the first
3617 address type was not supported. Found and fixed by Scott Dial.
3618 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3620 o Major bugfixes (security, compilation):
3621 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
3622 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
3623 cause a compiler warning, thereby making other checks fail, and
3624 needlessly disabling compiler-hardening support. Fixes one case of
3625 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
3627 o Major bugfixes (security, directory authorities):
3628 - Fix a crash and out-of-bounds write during authority voting, when
3629 the list of relays includes duplicate ed25519 identity keys. Fixes
3630 bug 19032; bugfix on 0.2.8.2-alpha.
3632 o Major bugfixes (client, bootstrapping):
3633 - Check if bootstrap consensus downloads are still needed when the
3634 linked connection attaches. This prevents tor making unnecessary
3635 begindir-style connections, which are the only directory
3636 connections tor clients make since the fix for 18483 was merged.
3637 - Fix some edge cases where consensus download connections may not
3638 have been closed, even though they were not needed. Related to fix
3640 - Make relays retry consensus downloads the correct number of times,
3641 rather than the more aggressive client retry count. Fixes part of
3643 - Stop downloading consensuses when we have a consensus, even if we
3644 don't have all the certificates for it yet. Fixes bug 18809;
3645 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
3647 o Major bugfixes (directory mirrors):
3648 - Decide whether to advertise begindir support in the the same way
3649 we decide whether to advertise our DirPort. Allowing these
3650 decisions to become out-of-sync led to surprising behavior like
3651 advertising begindir support when hibernation made us not
3652 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
3655 o Major bugfixes (IPv6 bridges, client):
3656 - Actually use IPv6 addresses when selecting directory addresses for
3657 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
3660 o Major bugfixes (key management):
3661 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3662 pointer to the previous (uninitialized) key value. The impact here
3663 should be limited to a difficult-to-trigger crash, if OpenSSL is
3664 running an engine that makes key generation failures possible, or
3665 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3666 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3669 o Major bugfixes (testing):
3670 - Fix a bug that would block 'make test-network-all' on systems where
3671 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
3672 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
3673 bugfix on 0.2.8.1-alpha.
3675 o Minor features (clients):
3676 - Make clients, onion services, and bridge relays always use an
3677 encrypted begindir connection for directory requests. Resolves
3678 ticket 18483. Patch by "teor".
3680 o Minor features (fallback directory mirrors):
3681 - Give each fallback the same weight for client selection; restrict
3682 fallbacks to one per operator; report fallback directory detail
3683 changes when rebuilding list; add new fallback directory mirrors
3684 to the whitelist; and many other minor simplifications and fixes.
3685 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
3686 0.2.8.1-alpha; patch by "teor".
3687 - Replace the 21 fallbacks generated in January 2016 and included in
3688 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
3689 2016. Closes task 17158; patch by "teor".
3691 o Minor features (geoip):
3692 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
3695 o Minor bugfixes (assert, portability):
3696 - Fix an assertion failure in memarea.c on systems where "long" is
3697 shorter than the size of a pointer. Fixes bug 18716; bugfix
3700 o Minor bugfixes (bootstrap):
3701 - Consistently use the consensus download schedule for authority
3702 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
3704 o Minor bugfixes (build):
3705 - Remove a pair of redundant AM_CONDITIONAL declarations from
3706 configure.ac. Fixes one final case of bug 17744; bugfix
3708 - Resolve warnings when building on systems that are concerned with
3709 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
3711 - When libscrypt.h is found, but no libscrypt library can be linked,
3712 treat libscrypt as absent. Fixes bug 19161; bugfix
3715 o Minor bugfixes (client):
3716 - Turn all TestingClientBootstrap* into non-testing torrc options.
3717 This changes simply renames them by removing "Testing" in front of
3718 them and they do not require TestingTorNetwork to be enabled
3719 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
3720 - Make directory node selection more reliable, mainly for IPv6-only
3721 clients and clients with few reachable addresses. Fixes bug 18929;
3722 bugfix on 0.2.8.1-alpha. Patch by "teor".
3724 o Minor bugfixes (controller, microdescriptors):
3725 - Make GETINFO dir/status-vote/current/consensus conform to the
3726 control specification by returning "551 Could not open cached
3727 consensus..." when not caching consensuses. Fixes bug 18920;
3728 bugfix on 0.2.2.6-alpha.
3730 o Minor bugfixes (crypto, portability):
3731 - The SHA3 and SHAKE routines now produce the correct output on Big
3732 Endian systems. No code calls either algorithm yet, so this is
3733 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
3734 - Tor now builds again with the recent OpenSSL 1.1 development
3735 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
3738 o Minor bugfixes (directories):
3739 - When fetching extrainfo documents, compare their SHA256 digests
3740 and Ed25519 signing key certificates with the routerinfo that led
3741 us to fetch them, rather than with the most recent routerinfo.
3742 Otherwise we generate many spurious warnings about mismatches.
3743 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
3745 o Minor bugfixes (logging):
3746 - When we can't generate a signing key because OfflineMasterKey is
3747 set, do not imply that we should have been able to load it. Fixes
3748 bug 18133; bugfix on 0.2.7.2-alpha.
3749 - Stop periodic_event_dispatch() from blasting twelve lines per
3750 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
3751 - When rejecting a misformed INTRODUCE2 cell, only log at
3752 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
3754 o Minor bugfixes (pluggable transports):
3755 - Avoid reporting a spurious error when we decide that we don't need
3756 to terminate a pluggable transport because it has already exited.
3757 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
3759 o Minor bugfixes (pointer arithmetic):
3760 - Fix a bug in memarea_alloc() that could have resulted in remote
3761 heap write access, if Tor had ever passed an unchecked size to
3762 memarea_alloc(). Fortunately, all the sizes we pass to
3763 memarea_alloc() are pre-checked to be less than 128 kilobytes.
3764 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
3767 o Minor bugfixes (relays):
3768 - Consider more config options when relays decide whether to
3769 regenerate their descriptor. Fixes more of bug 12538; bugfix
3771 - Resolve some edge cases where we might launch an ORPort
3772 reachability check even when DisableNetwork is set. Noticed while
3773 fixing bug 18616; bugfix on 0.2.3.9-alpha.
3775 o Minor bugfixes (statistics):
3776 - We now include consensus downloads via IPv6 in our directory-
3777 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
3779 o Minor bugfixes (testing):
3780 - Allow directories in small networks to bootstrap by skipping
3781 DirPort checks when the consensus has no exits. Fixes bug 19003;
3782 bugfix on 0.2.8.1-alpha. Patch by teor.
3783 - Fix a small memory leak that would occur when the
3784 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
3785 bugfix on 0.2.5.2-alpha.
3787 o Minor bugfixes (time handling):
3788 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
3789 field. Otherwise, our unit tests crash on Windows. Fixes bug
3790 18977; bugfix on 0.2.2.25-alpha.
3793 - Document the contents of the 'datadir/keys' subdirectory in the
3794 manual page. Closes ticket 17621.
3795 - Stop recommending use of nicknames to identify relays in our
3796 MapAddress documentation. Closes ticket 18312.
3799 Changes in version 0.2.8.2-alpha - 2016-03-28
3800 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
3801 bugs in earlier versions of Tor, including some that prevented
3802 authorities using Tor 0.2.7.x from running correctly. IPv6 and
3803 directory support should also be much improved.
3805 o New system requirements:
3806 - Tor no longer supports versions of OpenSSL with a broken
3807 implementation of counter mode. (This bug was present in OpenSSL
3808 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
3809 longer runs with, these versions.
3810 - Tor no longer attempts to support platforms where the "time_t"
3811 type is unsigned. (To the best of our knowledge, only OpenVMS does
3812 this, and Tor has never actually built on OpenVMS.) Closes
3814 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
3815 later (released in 2008 and 2009 respectively). If you are
3816 building Tor from the git repository instead of from the source
3817 distribution, and your tools are older than this, you will need to
3818 upgrade. Closes ticket 17732.
3820 o Major bugfixes (security, pointers):
3821 - Avoid a difficult-to-trigger heap corruption attack when extending
3822 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3823 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3824 Reported by Guido Vranken.
3826 o Major bugfixes (bridges, pluggable transports):
3827 - Modify the check for OR connections to private addresses. Allow
3828 bridges on private addresses, including pluggable transports that
3829 ignore the (potentially private) address in the bridge line. Fixes
3830 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
3832 o Major bugfixes (compilation):
3833 - Repair hardened builds under the clang compiler. Previously, our
3834 use of _FORTIFY_SOURCE would conflict with clang's address
3835 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
3837 o Major bugfixes (crash on shutdown):
3838 - Correctly handle detaching circuits from muxes when shutting down.
3839 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
3840 - Fix an assert-on-exit bug related to counting memory usage in
3841 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
3843 o Major bugfixes (crash on startup):
3844 - Fix a segfault during startup: If a Unix domain socket was
3845 configured as listener (such as a ControlSocket or a SocksPort
3846 "unix:" socket), and tor was started as root but not configured to
3847 switch to another user, tor would segfault while trying to string
3848 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
3851 o Major bugfixes (dns proxy mode, crash):
3852 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3853 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3855 o Major bugfixes (relays, bridge clients):
3856 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
3857 bridge clients use the address configured in the bridge line.
3858 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
3861 o Major bugfixes (voting):
3862 - Actually enable support for authorities to match routers by their
3863 Ed25519 identities. Previously, the code had been written, but
3864 some debugging code that had accidentally been left in the
3865 codebase made it stay turned off. Fixes bug 17702; bugfix
3867 - When collating votes by Ed25519 identities, authorities now
3868 include a "NoEdConsensus" flag if the ed25519 value (or lack
3869 thereof) for a server does not reflect the majority consensus.
3870 Related to bug 17668; bugfix on 0.2.7.2-alpha.
3871 - When generating a vote with keypinning disabled, never include two
3872 entries for the same ed25519 identity. This bug was causing
3873 authorities to generate votes that they could not parse when a
3874 router violated key pinning by changing its RSA identity but
3875 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
3876 18318. Bugfix on 0.2.7.2-alpha.
3878 o Minor features (security, win32):
3879 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
3880 attack. Fixes bug 18123; bugfix on all tor versions. Patch
3883 o Minor features (bug-resistance):
3884 - Make Tor survive errors involving connections without a
3885 corresponding event object. Previously we'd fail with an
3886 assertion; now we produce a log message. Related to bug 16248.
3888 o Minor features (build):
3889 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
3890 as having possible IPFW support. Closes ticket 18448. Patch from
3893 o Minor features (code hardening):
3894 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
3895 level code, to harden against accidental failures to NUL-
3896 terminate. Part of ticket 17852. Patch from jsturgix. Found
3899 o Minor features (crypto):
3900 - Validate the hard-coded Diffie-Hellman parameters and ensure that
3901 p is a safe prime, and g is a suitable generator. Closes
3904 o Minor features (geoip):
3905 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
3908 o Minor features (hidden service directory):
3909 - Streamline relay-side hsdir handling: when relays consider whether
3910 to accept an uploaded hidden service descriptor, they no longer
3911 check whether they are one of the relays in the network that is
3912 "supposed" to handle that descriptor. Implements ticket 18332.
3914 o Minor features (IPv6):
3915 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
3916 to 1, tor prefers IPv6 directory addresses.
3917 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
3918 avoids using IPv4 for client OR and directory connections.
3919 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
3920 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
3921 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
3923 o Minor features (linux seccomp2 sandbox):
3924 - Reject attempts to change our Address with "Sandbox 1" enabled.
3925 Changing Address with Sandbox turned on would never actually work,
3926 but previously it would fail in strange and confusing ways. Found
3929 o Minor features (robustness):
3930 - Exit immediately with an error message if the code attempts to use
3931 Libevent without having initialized it. This should resolve some
3932 frequently-made mistakes in our unit tests. Closes ticket 18241.
3934 o Minor features (unix domain sockets):
3935 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
3936 Unix domain sockets without checking the permissions on the parent
3937 directory. (Tor checks permissions by default because some
3938 operating systems only check permissions on the parent directory.
3939 However, some operating systems do look at permissions on the
3940 socket, and tor's default check is unneeded.) Closes ticket 18458.
3943 o Minor bugfixes (exit policies, security):
3944 - Refresh an exit relay's exit policy when interface addresses
3945 change. Previously, tor only refreshed the exit policy when the
3946 configured external address changed. Fixes bug 18208; bugfix on
3947 0.2.7.3-rc. Patch by teor.
3949 o Minor bugfixes (security, hidden services):
3950 - Prevent hidden services connecting to client-supplied rendezvous
3951 addresses that are reserved as internal or multicast. Fixes bug
3952 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
3954 o Minor bugfixes (build):
3955 - Do not link the unit tests against both the testing and non-
3956 testing versions of the static libraries. Fixes bug 18490; bugfix
3958 - Avoid spurious failures from configure files related to calling
3959 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
3960 0.2.0.1-alpha. Patch from "cypherpunks".
3961 - Silence spurious clang-scan warnings in the ed25519_donna code by
3962 explicitly initializing some objects. Fixes bug 18384; bugfix on
3963 0.2.7.2-alpha. Patch by teor.
3965 o Minor bugfixes (client, bootstrap):
3966 - Count receipt of new microdescriptors as progress towards
3967 bootstrapping. Previously, with EntryNodes set, Tor might not
3968 successfully repopulate the guard set on bootstrapping. Fixes bug
3969 16825; bugfix on 0.2.3.1-alpha.
3971 o Minor bugfixes (code correctness):
3972 - Update to the latest version of Trunnel, which tries harder to
3973 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
3974 by clang address sanitizer. Fixes bug 18373; bugfix
3977 o Minor bugfixes (configuration):
3978 - Fix a tiny memory leak when parsing a port configuration ending in
3979 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
3981 o Minor bugfixes (containers):
3982 - If we somehow attempt to construct a heap with more than
3983 1073741822 elements, avoid an integer overflow when maintaining
3984 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
3986 o Minor bugfixes (correctness):
3987 - Fix a bad memory handling bug that would occur if we had queued a
3988 cell on a channel's incoming queue. Fortunately, we can't actually
3989 queue a cell like that as our code is constructed today, but it's
3990 best to avoid this kind of error, even if there isn't any code
3991 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
3993 o Minor bugfixes (directory):
3994 - When generating a URL for a directory server on an IPv6 address,
3995 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
3996 on 0.2.3.9-alpha. Patch from Malek.
3998 o Minor bugfixes (fallback directory mirrors):
3999 - When requesting extrainfo descriptors from a trusted directory
4000 server, check whether it is an authority or a fallback directory
4001 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
4002 0.2.4.7-alpha. Reported by atagar, patch by teor.
4004 o Minor bugfixes (hidden service, client):
4005 - Handle the case where the user makes several fast consecutive
4006 requests to the same .onion address. Previously, the first six
4007 requests would each trigger a descriptor fetch, each picking a
4008 directory (there are 6 overall) and the seventh one would fail
4009 because no directories were left, thereby triggering a close on
4010 all current directory connections asking for the hidden service.
4011 The solution here is to not close the connections if we have
4012 pending directory fetches. Fixes bug 15937; bugfix
4015 o Minor bugfixes (hidden service, control port):
4016 - Add the onion address to the HS_DESC event for the UPLOADED action
4017 both on success or failure. It was previously hardcoded with
4018 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
4020 o Minor bugfixes (hidden service, directory):
4021 - Bridges now refuse "rendezvous2" (hidden service descriptor)
4022 publish attempts. Suggested by ticket 18332.
4024 o Minor bugfixes (linux seccomp2 sandbox):
4025 - Allow the setrlimit syscall, and the prlimit and prlimit64
4026 syscalls, which some libc implementations use under the hood.
4027 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
4028 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
4029 enabled and no DNS resolvers configured. This should help TAILS
4030 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
4031 - Fix the sandbox's interoperability with unix domain sockets under
4032 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
4034 o Minor bugfixes (logging):
4035 - When logging information about an unparsable networkstatus vote or
4036 consensus, do not say "vote" when we mean consensus. Fixes bug
4037 18368; bugfix on 0.2.0.8-alpha.
4038 - Scrub service name in "unrecognized service ID" log messages.
4039 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
4040 - Downgrade logs and backtraces about IP versions to info-level.
4041 Only log backtraces once each time tor runs. Assists in diagnosing
4042 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
4043 Christian, patch by teor.
4045 o Minor bugfixes (memory safety):
4046 - Avoid freeing an uninitialized pointer when opening a socket fails
4047 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
4048 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
4050 - Correctly duplicate addresses in get_interface_address6_list().
4051 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
4052 patch by "cypherpunks".
4053 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
4055 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
4056 18672; bugfix on 0.2.5.1-alpha.
4058 o Minor bugfixes (private directory):
4059 - Prevent a race condition when creating private directories. Fixes
4060 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
4061 Patch from jsturgix. Found with Flawfinder.
4063 o Minor bugfixes (test networks, IPv6):
4064 - Allow internal IPv6 addresses in descriptors in test networks.
4065 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
4068 o Minor bugfixes (testing):
4069 - We no longer disable assertions in the unit tests when coverage is
4070 enabled. Instead, we require you to say --disable-asserts-in-tests
4071 to the configure script if you need assertions disabled in the
4072 unit tests (for example, if you want to perform branch coverage).
4073 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
4075 o Minor bugfixes (time parsing):
4076 - Avoid overflow in tor_timegm when parsing dates in and after 2038
4077 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
4078 0.0.2pre14. Patch by teor.
4080 o Minor bugfixes (tor-gencert):
4081 - Correctly handle the case where an authority operator enters a
4082 passphrase but sends an EOF before sending a newline. Fixes bug
4083 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
4085 o Code simplification and refactoring:
4086 - Quote all the string interpolations in configure.ac -- even those
4087 which we are pretty sure can't contain spaces. Closes ticket
4088 17744. Patch from zerosion.
4089 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
4090 inplace, so there's no need to have a separate implementation for
4091 the non-inplace code. Closes ticket 18258. Patch from Malek.
4092 - Simplify return types for some crypto functions that can't
4093 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
4096 - Change build messages to refer to "Fedora" instead of "Fedora
4097 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
4098 Patches from "icanhasaccount" and "cypherpunks".
4101 - We no longer maintain an internal freelist in memarea.c.
4102 Allocators should be good enough to make this code unnecessary,
4103 and it's doubtful that it ever had any performance benefit.
4106 - Fix several warnings from clang's address sanitizer produced in
4108 - Treat backtrace test failures as expected on FreeBSD until we
4109 solve bug 17808. Closes ticket 18204.
4112 Changes in version 0.2.8.1-alpha - 2016-02-04
4113 Tor 0.2.8.1-alpha is the first alpha release in its series. It
4114 includes numerous small features and bugfixes against previous Tor
4115 versions, and numerous small infrastructure improvements. The most
4116 notable features are a set of improvements to the directory subsystem.
4118 o Major features (security, Linux):
4119 - When Tor starts as root on Linux and is told to switch user ID, it
4120 can now retain the capability to bind to low ports. By default,
4121 Tor will do this only when it's switching user ID and some low
4122 ports have been configured. You can change this behavior with the
4123 new option KeepBindCapabilities. Closes ticket 8195.
4125 o Major features (directory system):
4126 - When bootstrapping multiple consensus downloads at a time, use the
4127 first one that starts downloading, and close the rest. This
4128 reduces failures when authorities or fallback directories are slow
4129 or down. Together with the code for feature 15775, this feature
4130 should reduces failures due to fallback churn. Implements ticket
4131 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
4132 "mikeperry" and "teor".
4133 - Include a trial list of 21 default fallback directories, generated
4134 in January 2016, based on an opt-in survey of suitable relays.
4135 Doing this should make clients bootstrap more quickly and reliably,
4136 and reduce the load on the directory authorities. Closes ticket
4137 15775. Patch by "teor".
4138 Candidates identified using an OnionOO script by "weasel", "teor",
4139 "gsathya", and "karsten".
4140 - Previously only relays that explicitly opened a directory port
4141 (DirPort) accepted directory requests from clients. Now all
4142 relays, with and without a DirPort, accept and serve tunneled
4143 directory requests that they receive through their ORPort. You can
4144 disable this behavior using the new DirCache option. Closes
4147 o Major key updates:
4148 - Update the V3 identity key for the dannenberg directory authority:
4149 it was changed on 18 November 2015. Closes task 17906. Patch
4152 o Minor features (security, clock):
4153 - Warn when the system clock appears to move back in time (when the
4154 state file was last written in the future). Tor doesn't know that
4155 consensuses have expired if the clock is in the past. Patch by
4156 "teor". Implements ticket 17188.
4158 o Minor features (security, exit policies):
4159 - ExitPolicyRejectPrivate now rejects more private addresses by
4160 default. Specifically, it now rejects the relay's outbound bind
4161 addresses (if configured), and the relay's configured port
4162 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
4163 0.2.0.11-alpha. Patch by "teor".
4165 o Minor features (security, memory erasure):
4166 - Set the unused entries in a smartlist to NULL. This helped catch
4167 a (harmless) bug, and shouldn't affect performance too much.
4168 Implements ticket 17026.
4169 - Use SecureMemoryWipe() function to securely clean memory on
4170 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
4171 Implements feature 17986.
4172 - Use explicit_bzero or memset_s when present. Previously, we'd use
4173 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
4174 from <logan@hackers.mu> and <selven@hackers.mu>.
4175 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4176 zero size. Check size argument to memwipe() for underflow. Fixes
4177 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4180 o Minor features (security, RNG):
4181 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
4182 positively are not allowed to fail. Previously we depended on
4183 internal details of OpenSSL's behavior. Closes ticket 17686.
4184 - Never use the system entropy output directly for anything besides
4185 seeding the PRNG. When we want to generate important keys, instead
4186 of using system entropy directly, we now hash it with the PRNG
4187 stream. This may help resist certain attacks based on broken OS
4188 entropy implementations. Closes part of ticket 17694.
4189 - Use modern system calls (like getentropy() or getrandom()) to
4190 generate strong entropy on platforms that have them. Closes
4193 o Minor features (accounting):
4194 - Added two modes to the AccountingRule option: One for limiting
4195 only the number of bytes sent ("AccountingRule out"), and one for
4196 limiting only the number of bytes received ("AccountingRule in").
4197 Closes ticket 15989; patch from "unixninja92".
4199 o Minor features (build):
4200 - Since our build process now uses "make distcheck", we no longer
4201 force "make dist" to depend on "make check". Closes ticket 17893;
4202 patch from "cypherpunks."
4203 - Tor now builds successfully with the recent OpenSSL 1.1
4204 development branch, and with the latest LibreSSL. Closes tickets
4205 17549, 17921, and 17984.
4207 o Minor features (controller):
4208 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
4209 tickets 16774 and 17817. Patch by George Tankersley.
4210 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
4211 service descriptor from a service's local hidden service
4212 descriptor cache. Closes ticket 14846.
4213 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
4214 controllers can examine the the reject rules added by
4215 ExitPolicyRejectPrivate. This makes it easier for stem to display
4218 o Minor features (crypto):
4219 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
4221 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
4222 - When allocating a digest state object, allocate no more space than
4223 we actually need. Previously, we would allocate as much space as
4224 the state for the largest algorithm would need. This change saves
4225 up to 672 bytes per circuit. Closes ticket 17796.
4226 - Improve performance when hashing non-multiple of 8 sized buffers,
4227 based on Andrew Moon's public domain SipHash-2-4 implementation.
4228 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
4230 o Minor features (directory downloads):
4231 - Wait for busy authorities and fallback directories to become non-
4232 busy when bootstrapping. (A similar change was made in 6c443e987d
4233 for directory caches chosen from the consensus.) Closes ticket
4234 17864; patch by "teor".
4235 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
4236 directory mirrors. The default is 1; set it to 0 to disable
4237 fallbacks. Implements ticket 17576. Patch by "teor".
4239 o Minor features (geoip):
4240 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
4243 o Minor features (IPv6):
4244 - Add an argument 'ipv6=address:orport' to the DirAuthority and
4245 FallbackDir torrc options, to specify an IPv6 address for an
4246 authority or fallback directory. Add hard-coded ipv6 addresses for
4247 directory authorities that have them. Closes ticket 17327; patch
4248 from Nick Mathewson and "teor".
4249 - Add address policy assume_action support for IPv6 addresses.
4250 - Limit IPv6 mask bits to 128.
4251 - Warn when comparing against an AF_UNSPEC address in a policy, it's
4252 almost always a bug. Closes ticket 17863; patch by "teor".
4253 - Allow users to configure directory authorities and fallback
4254 directory servers with IPv6 addresses and ORPorts. Resolves
4256 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
4257 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
4258 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
4259 17638; bugfix on 0.0.2pre8. Patch by "teor".
4261 o Minor features (logging):
4262 - When logging to syslog, allow a tag to be added to the syslog
4263 identity (the string prepended to every log message). The tag can
4264 be configured with SyslogIdentityTag and defaults to none. Setting
4265 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
4268 o Minor features (portability):
4269 - Use timingsafe_memcmp() where available. Closes ticket 17944;
4270 patch from <logan@hackers.mu>.
4272 o Minor features (relay, address discovery):
4273 - Add a family argument to get_interface_addresses_raw() and
4274 subfunctions to make network interface address interogation more
4275 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
4276 types of interfaces from the operating system. Resolves
4278 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
4279 fails to enumerate interface addresses using the platform-specific
4280 API, have it rely on the UDP socket fallback technique to try and
4281 find out what IP addresses (both IPv4 and IPv6) our machine has.
4282 Resolves ticket 17951.
4284 o Minor features (replay cache):
4285 - The replay cache now uses SHA256 instead of SHA1. Implements
4286 feature 8961. Patch by "teor", issue reported by "rransom".
4288 o Minor features (unix file permissions):
4289 - Defer creation of Unix sockets until after setuid. This avoids
4290 needing CAP_CHOWN and CAP_FOWNER when using systemd's
4291 CapabilityBoundingSet, or chown and fowner when using SELinux.
4292 Implements part of ticket 17562. Patch from Jamie Nguyen.
4293 - If any directory created by Tor is marked as group readable, the
4294 filesystem group is allowed to be either the default GID or the
4295 root user. Allowing root to read the DataDirectory prevents the
4296 need for CAP_READ_SEARCH when using systemd's
4297 CapabilityBoundingSet, or dac_read_search when using SELinux.
4298 Implements part of ticket 17562. Patch from Jamie Nguyen.
4299 - Introduce a new DataDirectoryGroupReadable option. If it is set to
4300 1, the DataDirectory will be made readable by the default GID.
4301 Implements part of ticket 17562. Patch from Jamie Nguyen.
4303 o Minor bugfixes (accounting):
4304 - The max bandwidth when using 'AccountRule sum' is now correctly
4305 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
4308 o Minor bugfixes (code correctness):
4309 - When closing an entry connection, generate a warning if we should
4310 have sent an end cell for it but we haven't. Fixes bug 17876;
4311 bugfix on 0.2.3.2-alpha.
4312 - Assert that allocated memory held by the reputation code is freed
4313 according to its internal counters. Fixes bug 17753; bugfix
4315 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
4318 o Minor bugfixes (compilation):
4319 - Mark all object files that include micro-revision.i as depending
4320 on it, so as to make parallel builds more reliable. Fixes bug
4321 17826; bugfix on 0.2.5.1-alpha.
4322 - Don't try to use the pthread_condattr_setclock() function unless
4323 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
4324 17819; bugfix on 0.2.6.3-alpha.
4325 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
4327 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
4328 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
4329 - Fix search for libevent libraries on OpenBSD (and other systems
4330 that install libevent 1 and libevent 2 in parallel). Fixes bug
4331 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
4332 - Isolate environment variables meant for tests from the rest of the
4333 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
4334 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
4336 - Remove config.log only from make distclean, not from make clean.
4337 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
4339 o Minor bugfixes (crypto):
4340 - Check the return value of HMAC() and assert on failure. Fixes bug
4341 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
4343 o Minor bugfixes (fallback directories):
4344 - Mark fallbacks as "too busy" when they return a 503 response,
4345 rather than just marking authorities. Fixes bug 17572; bugfix on
4346 0.2.4.7-alpha. Patch by "teor".
4348 o Minor bugfixes (IPv6):
4349 - Update the limits in max_dl_per_request for IPv6 address length.
4350 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
4352 o Minor bugfixes (linux seccomp2 sandbox):
4353 - Fix a crash when using offline master ed25519 keys with the Linux
4354 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
4356 o Minor bugfixes (logging):
4357 - In log messages that include a function name, use __FUNCTION__
4358 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
4359 with clang __PRETTY_FUNCTION__ has extra information we don't
4360 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
4362 - Remove needless quotes from a log message about unparseable
4363 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
4365 o Minor bugfixes (portability):
4366 - Remove an #endif from configure.ac so that we correctly detect the
4367 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
4370 o Minor bugfixes (relays):
4371 - Check that both the ORPort and DirPort (if present) are reachable
4372 before publishing a relay descriptor. Otherwise, relays publish a
4373 descriptor with DirPort 0 when the DirPort reachability test takes
4374 longer than the ORPort reachability test. Fixes bug 18050; bugfix
4375 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
4377 o Minor bugfixes (relays, hidden services):
4378 - Refuse connection requests to private OR addresses unless
4379 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
4380 then refuse to send any cells to a private address. Fixes bugs
4381 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
4383 o Minor bugfixes (safe logging):
4384 - When logging a malformed hostname received through socks4, scrub
4385 it if SafeLogging says we should. Fixes bug 17419; bugfix
4388 o Minor bugfixes (statistics code):
4389 - Consistently check for overflow in round_*_to_next_multiple_of
4390 functions, and add unit tests with additional and maximal values.
4391 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
4392 - Handle edge cases in the laplace functions: avoid division by
4393 zero, avoid taking the log of zero, and silence clang type
4394 conversion warnings using round and trunc. Add unit tests for edge
4395 cases with maximal values. Fixes part of bug 13192; bugfix
4398 o Minor bugfixes (testing):
4399 - The test for log_heartbeat was incorrectly failing in timezones
4400 with non-integer offsets. Instead of comparing the end of the time
4401 string against a constant, compare it to the output of
4402 format_local_iso_time when given the correct input. Fixes bug
4403 18039; bugfix on 0.2.5.4-alpha.
4404 - Make unit tests pass on IPv6-only systems, and systems without
4405 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
4406 bugfix on 0.2.7.3-rc. Patch by "teor".
4407 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
4409 - Check the full results of SHA256 and SHA512 digests in the unit
4410 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
4412 o Code simplification and refactoring:
4413 - Move logging of redundant policy entries in
4414 policies_parse_exit_policy_internal into its own function. Closes
4415 ticket 17608; patch from "juce".
4416 - Extract the more complicated parts of circuit_mark_for_close()
4417 into a new function that we run periodically before circuits are
4418 freed. This change removes more than half of the functions
4419 currently in the "blob". Closes ticket 17218.
4420 - Clean up a little duplicated code in
4421 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
4423 - Decouple the list of streams waiting to be attached to circuits
4424 from the overall connection list. This change makes it possible to
4425 attach streams quickly while simplifying Tor's callgraph and
4426 avoiding O(N) scans of the entire connection list. Closes
4428 - When a direct directory request fails immediately on launch,
4429 instead of relaunching that request from inside the code that
4430 launches it, instead mark the connection for teardown. This change
4431 simplifies Tor's callback and prevents the directory-request
4432 launching code from invoking itself recursively. Closes
4434 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
4435 use them. Closes ticket 17926.
4438 - Add a description of the correct use of the '--keygen' command-
4439 line option. Closes ticket 17583; based on text by 's7r'.
4440 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
4441 - Explain actual minima for BandwidthRate. Closes ticket 16382.
4442 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
4443 - Mention torspec URL in the manpage and point the reader to it
4444 whenever we mention a document that belongs in torspce. Fixes
4448 - Remove client-side support for connecting to Tor relays running
4449 versions of Tor before 0.2.3.6-alpha. These relays didn't support
4450 the v3 TLS handshake protocol, and are no longer allowed on the
4451 Tor network. Implements the client side of ticket 11150. Based on
4452 patches by Tom van der Woerdt.
4455 - Add unit tests to check for common RNG failure modes, such as
4456 returning all zeroes, identical values, or incrementing values
4457 (OpenSSL's rand_predictable feature). Patch by "teor".
4458 - Log more information when the backtrace tests fail. Closes ticket
4459 17892. Patch from "cypherpunks."
4460 - Always test both ed25519 backends, so that we can be sure that our
4461 batch-open replacement code works. Part of ticket 16794.
4462 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
4463 portion of ticket 16831.
4464 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
4465 util_format.c, directory.c, and options_validate.c. Closes tickets
4466 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
4468 - Unit tests for directory_handle_command_get. Closes ticket 17004.
4469 Patch from Reinaldo de Souza Jr.
4472 Changes in version 0.2.7.6 - 2015-12-10
4473 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
4474 well as a minor bug in hidden service reliability.
4476 o Major bugfixes (guard selection):
4477 - Actually look at the Guard flag when selecting a new directory
4478 guard. When we implemented the directory guard design, we
4479 accidentally started treating all relays as if they have the Guard
4480 flag during guard selection, leading to weaker anonymity and worse
4481 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4484 o Minor features (geoip):
4485 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
4488 o Minor bugfixes (compilation):
4489 - When checking for net/pfvar.h, include netinet/in.h if possible.
4490 This fixes transparent proxy detection on OpenBSD. Fixes bug
4491 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
4492 - Fix a compilation warning with Clang 3.6: Do not check the
4493 presence of an address which can never be NULL. Fixes bug 17781.
4495 o Minor bugfixes (correctness):
4496 - When displaying an IPv6 exit policy, include the mask bits
4497 correctly even when the number is greater than 31. Fixes bug
4498 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
4499 - The wrong list was used when looking up expired intro points in a
4500 rend service object, causing what we think could be reachability
4501 issues for hidden services, and triggering a BUG log. Fixes bug
4502 16702; bugfix on 0.2.7.2-alpha.
4503 - Fix undefined behavior in the tor_cert_checksig function. Fixes
4504 bug 17722; bugfix on 0.2.7.2-alpha.
4507 Changes in version 0.2.7.5 - 2015-11-20
4508 The Tor 0.2.7 release series is dedicated to the memory of Tor user
4509 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
4510 tirelessly to advocate human rights regardless of national borders,
4511 and oppose the encroachments of mass surveillance. He opposed national
4512 exceptionalism, he brought clarity to legal and policy debates, he
4513 understood and predicted the impact of mass surveillance on the world,
4514 and he laid the groundwork for resisting it. While serving on the Tor
4515 Project's board of directors, he brought us his uncompromising focus
4516 on technical excellence in the service of humankind. Caspar was an
4517 inimitable force for good and a wonderful friend. He was kind,
4518 humorous, generous, gallant, and believed we should protect one
4519 another without exception. We honor him here for his ideals, his
4520 efforts, and his accomplishments. Please honor his memory with works
4521 that would make him proud.
4523 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
4525 The 0.2.7 series adds a more secure identity key type for relays,
4526 improves cryptography performance, resolves several longstanding
4527 hidden-service performance issues, improves controller support for
4528 hidden services, and includes small bugfixes and performance
4529 improvements throughout the program. This release series also includes
4530 more tests than before, and significant simplifications to which parts
4531 of Tor invoke which others.
4533 (This release contains no code changes since 0.2.7.4-rc.)
4536 Changes in version 0.2.7.4-rc - 2015-10-21
4537 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
4538 fixes some important memory leaks, and a scary-looking (but mostly
4539 harmless in practice) invalid-read bug. It also has a few small
4540 bugfixes, notably fixes for compilation and portability on different
4541 platforms. If no further significant bounds are found, the next
4542 release will the the official stable release.
4544 o Major bugfixes (security, correctness):
4545 - Fix an error that could cause us to read 4 bytes before the
4546 beginning of an openssl string. This bug could be used to cause
4547 Tor to crash on systems with unusual malloc implementations, or
4548 systems with unusual hardening installed. Fixes bug 17404; bugfix
4551 o Major bugfixes (correctness):
4552 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
4553 bug 17401; bugfix on 0.2.7.3-rc.
4555 o Major bugfixes (memory leaks):
4556 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
4557 17398; bugfix on 0.2.6.1-alpha.
4558 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
4559 17402; bugfix on 0.2.7.3-rc.
4560 - Fix a memory leak when reading an expired signing key from disk.
4561 Fixes bug 17403; bugfix on 0.2.7.2-rc.
4563 o Minor features (geoIP):
4564 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
4567 o Minor bugfixes (compilation):
4568 - Repair compilation with the most recent (unreleased, alpha)
4569 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
4570 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
4571 17251; bugfix on 0.2.7.2-alpha.
4572 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
4573 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
4575 o Minor bugfixes (portability):
4576 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
4577 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
4580 o Minor bugfixes (sandbox):
4581 - Add the "hidserv-stats" filename to our sandbox filter for the
4582 HiddenServiceStatistics option to work properly. Fixes bug 17354;
4583 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
4585 o Minor bugfixes (testing):
4586 - Add unit tests for get_interface_address* failure cases. Fixes bug
4587 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
4588 - Fix breakage when running 'make check' with BSD make. Fixes bug
4589 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
4590 - Make the get_ifaddrs_* unit tests more tolerant of different
4591 network configurations. (Don't assume every test box has an IPv4
4592 address, and don't assume every test box has a non-localhost
4593 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
4594 - Skip backtrace tests when backtrace support is not compiled in.
4595 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
4599 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
4600 - Note that HiddenServicePorts can take a unix domain socket. Closes
4604 Changes in version 0.2.7.3-rc - 2015-09-25
4605 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
4606 contains numerous usability fixes for Ed25519 keys, safeguards against
4607 several misconfiguration problems, significant simplifications to
4608 Tor's callgraph, and numerous bugfixes and small features.
4610 This is the most tested release of Tor to date. The unit tests cover
4611 39.40% of the code, and the integration tests (accessible with "make
4612 test-full-online", requiring stem and chutney and a network
4613 connection) raise the coverage to 64.49%.
4615 o Major features (security, hidden services):
4616 - Hidden services, if using the EntryNodes option, are required to
4617 use more than one EntryNode, in order to avoid a guard discovery
4618 attack. (This would only affect people who had configured hidden
4619 services and manually specified the EntryNodes option with a
4620 single entry-node. The impact was that it would be easy to
4621 remotely identify the guard node used by such a hidden service.
4622 See ticket for more information.) Fixes ticket 14917.
4624 o Major features (Ed25519 keys, keypinning):
4625 - The key-pinning option on directory authorities is now advisory-
4626 only by default. In a future version, or when the AuthDirPinKeys
4627 option is set, pins are enforced again. Disabling key-pinning
4628 seemed like a good idea so that we can survive the fallout of any
4629 usability problems associated with Ed25519 keys. Closes
4632 o Major features (Ed25519 performance):
4633 - Improve the speed of Ed25519 operations and Curve25519 keypair
4634 generation when built targeting 32 bit x86 platforms with SSE2
4635 available. Implements ticket 16535.
4636 - Improve the runtime speed of Ed25519 signature verification by
4637 using Ed25519-donna's batch verification support. Implements
4640 o Major features (performance testing):
4641 - The test-network.sh script now supports performance testing.
4642 Requires corresponding chutney performance testing changes. Patch
4643 by "teor". Closes ticket 14175.
4645 o Major features (relay, Ed25519):
4646 - Significant usability improvements for Ed25519 key management. Log
4647 messages are better, and the code can recover from far more
4648 failure conditions. Thanks to "s7r" for reporting and diagnosing
4650 - Add a new OfflineMasterKey option to tell Tor never to try loading
4651 or generating a secret Ed25519 identity key. You can use this in
4652 combination with tor --keygen to manage offline and/or encrypted
4653 Ed25519 keys. Implements ticket 16944.
4654 - Add a --newpass option to allow changing or removing the
4655 passphrase of an encrypted key with tor --keygen. Implements part
4657 - On receiving a HUP signal, check to see whether the Ed25519
4658 signing key has changed, and reload it if so. Closes ticket 16790.
4660 o Major bugfixes (relay, Ed25519):
4661 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
4662 0.2.7.2-alpha. Reported by "s7r".
4663 - Improve handling of expired signing keys with offline master keys.
4664 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
4666 o Minor features (client-side privacy):
4667 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
4668 lifespan when IsolateSOCKSAuth and streams with SOCKS
4669 authentication are attached to the circuit. This allows
4670 applications like TorBrowser to manage circuit lifetime on their
4671 own. Implements feature 15482.
4672 - When logging malformed hostnames from SOCKS5 requests, respect
4673 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
4675 o Minor features (compilation):
4676 - Give a warning as early as possible when trying to build with an
4677 unsupported OpenSSL version. Closes ticket 16901.
4678 - Fail during configure if we're trying to build against an OpenSSL
4679 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
4680 which started requiring ECC.
4682 o Minor features (geoip):
4683 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
4686 o Minor features (hidden services):
4687 - Relays need to have the Fast flag to get the HSDir flag. As this
4688 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
4689 drop. This change should make some attacks against the hidden
4690 service directory system harder. Fixes ticket 15963.
4691 - Turn on hidden service statistics collection by setting the torrc
4692 option HiddenServiceStatistics to "1" by default. (This keeps
4693 track only of the fraction of traffic used by hidden services, and
4694 the total number of hidden services in existence.) Closes
4696 - Client now uses an introduction point failure cache to know when
4697 to fetch or keep a descriptor in their cache. Previously, failures
4698 were recorded implicitly, but not explicitly remembered. Closes
4701 o Minor features (testing, authorities, documentation):
4702 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
4703 explicitly manage consensus flags in testing networks. Patch by
4704 "robgjansen", modified by "teor". Implements part of ticket 14882.
4706 o Minor bugfixes (security, exit policies):
4707 - ExitPolicyRejectPrivate now also rejects the relay's published
4708 IPv6 address (if any), and any publicly routable IPv4 or IPv6
4709 addresses on any local interfaces. ticket 17027. Patch by "teor".
4710 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
4712 o Minor bug fixes (torrc exit policies):
4713 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
4714 produce IPv6 wildcard addresses. Previously they would produce
4715 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
4716 of bug 16069; bugfix on 0.2.4.7-alpha.
4717 - When parsing torrc ExitPolicies, we now warn for a number of cases
4718 where the user's intent is likely to differ from Tor's actual
4719 behavior. These include: using an IPv4 address with an accept6 or
4720 reject6 line; using "private" on an accept6 or reject6 line; and
4721 including any ExitPolicy lines after accept *:* or reject *:*.
4722 Related to ticket 16069.
4723 - When parsing torrc ExitPolicies, we now issue an info-level
4724 message when expanding an "accept/reject *" line to include both
4725 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
4726 - In each instance above, usage advice is provided to avoid the
4727 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
4728 16069; bugfix on 0.2.4.7-alpha.
4730 o Minor bugfixes (authority):
4731 - Don't assign "HSDir" to a router if it isn't Valid and Running.
4732 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
4733 - Downgrade log messages about Ed25519 key issues if they are in old
4734 cached router descriptors. Fixes part of bug 16286; bugfix
4736 - When we find an Ed25519 key issue in a cached descriptor, stop
4737 saying the descriptor was just "uploaded". Fixes another part of
4738 bug 16286; bugfix on 0.2.7.2-alpha.
4740 o Minor bugfixes (control port):
4741 - Repair a warning and a spurious result when getting the maximum
4742 number of file descriptors from the controller. Fixes bug 16697;
4743 bugfix on 0.2.7.2-alpha.
4745 o Minor bugfixes (correctness):
4746 - When calling channel_free_list(), avoid calling smartlist_remove()
4747 while inside a FOREACH loop. This partially reverts commit
4748 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
4749 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
4751 o Minor bugfixes (documentation):
4752 - Advise users on how to configure separate IPv4 and IPv6 exit
4753 policies in the manpage and sample torrcs. Related to ticket 16069.
4754 - Fix the usage message of tor-resolve(1) so that it no longer lists
4755 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
4756 - Fix an error in the manual page and comments for
4757 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
4758 required "ORPort connectivity". While this is true, it is in no
4759 way unique to the HSDir flag. Of all the flags, only HSDirs need a
4760 DirPort configured in order for the authorities to assign that
4761 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
4764 o Minor bugfixes (Ed25519):
4765 - Fix a memory leak when reading router descriptors with expired
4766 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
4768 o Minor bugfixes (linux seccomp2 sandbox):
4769 - Allow bridge authorities to run correctly under the seccomp2
4770 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
4771 - Allow routers with ed25519 keys to run correctly under the
4772 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
4774 o Minor bugfixes (open file limit):
4775 - Fix set_max_file_descriptors() to set by default the max open file
4776 limit to the current limit when setrlimit() fails. Fixes bug
4777 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
4779 o Minor bugfixes (portability):
4780 - Try harder to normalize the exit status of the Tor process to the
4781 standard-provided range. Fixes bug 16975; bugfix on every version
4783 - Check correctly for Windows socket errors in the workqueue
4784 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
4785 - Fix the behavior of crypto_rand_time_range() when told to consider
4786 times before 1970. (These times were possible when running in a
4787 simulated network environment where time()'s output starts at
4788 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
4789 - Restore correct operation of TLS client-cipher detection on
4790 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
4792 o Minor bugfixes (relay):
4793 - Ensure that worker threads actually exit when a fatal error or
4794 shutdown is indicated. This fix doesn't currently affect the
4795 behavior of Tor, because Tor workers never indicates fatal error
4796 or shutdown except in the unit tests. Fixes bug 16868; bugfix
4798 - Unblock threads before releasing the work queue mutex to ensure
4799 predictable scheduling behavior. Fixes bug 16644; bugfix
4802 o Code simplification and refactoring:
4803 - Change the function that's called when we need to retry all
4804 downloads so that it only reschedules the downloads to happen
4805 immediately, rather than launching them all at once itself. This
4806 further simplifies Tor's callgraph.
4807 - Move some format-parsing functions out of crypto.c and
4808 crypto_curve25519.c into crypto_format.c and/or util_format.c.
4809 - Move the client-only parts of init_keys() into a separate
4810 function. Closes ticket 16763.
4811 - Simplify the microdesc_free() implementation so that it no longer
4812 appears (to code analysis tools) to potentially invoke a huge
4813 suite of other microdesc functions.
4814 - Simply the control graph further by deferring the inner body of
4815 directory_all_unreachable() into a callback. Closes ticket 16762.
4816 - Treat the loss of an owning controller as equivalent to a SIGTERM
4817 signal. This removes a tiny amount of duplicated code, and
4818 simplifies our callgraph. Closes ticket 16788.
4819 - When generating an event to send to the controller, we no longer
4820 put the event over the network immediately. Instead, we queue
4821 these events, and use a Libevent callback to deliver them. This
4822 change simplifies Tor's callgraph by reducing the number of
4823 functions from which all other Tor functions are reachable. Closes
4825 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
4826 that try to scan or compile every file on Unix won't decide that
4828 - Remove the unused "nulterminate" argument from buf_pullup().
4831 - Recommend a 40 GB example AccountingMax in torrc.sample rather
4832 than a 4 GB max. Closes ticket 16742.
4833 - Include the TUNING document in our source tarball. It is referred
4834 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
4838 - The internal pure-C tor-fw-helper tool is now removed from the Tor
4839 distribution, in favor of the pure-Go clone available from
4840 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
4841 used by the C tor-fw-helper are not, in our opinion, very
4842 confidence- inspiring in their secure-programming techniques.
4843 Closes ticket 13338.
4844 - Remove the code that would try to aggressively flush controller
4845 connections while writing to them. This code was introduced in
4846 0.1.2.7-alpha, in order to keep output buffers from exceeding
4847 their limits. But there is no longer a maximum output buffer size,
4848 and flushing data in this way caused some undesirable recursions
4849 in our call graph. Closes ticket 16480.
4852 - Make "bridges+hs" the default test network. This tests almost all
4853 tor functionality during make test-network, while allowing tests
4854 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
4855 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
4856 (chutney). Patches by "teor".
4857 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
4858 by-side in the same parent directory. Closes ticket 16903. Patch
4860 - Use environment variables rather than autoconf substitutions to
4861 send variables from the build system to the test scripts. This
4862 change should be easier to maintain, and cause 'make distcheck' to
4863 work better than before. Fixes bug 17148.
4864 - Add a new set of callgraph analysis scripts that use clang to
4865 produce a list of which Tor functions are reachable from which
4866 other Tor functions. We're planning to use these to help simplify
4867 our code structure by identifying illogical dependencies.
4868 - Add new 'test-full' and 'test-full-online' targets to run all
4869 tests, including integration tests with stem and chutney.
4870 - Make the test-workqueue test work on Windows by initializing the
4871 network before we begin.
4872 - New make target (make test-network-all) to run multiple applicable
4873 chutney test cases. Patch from Teor; closes 16953.
4874 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
4875 functions in dns.c. Implements a portion of ticket 16831.
4876 - When building Tor with testing coverage enabled, run Chutney tests
4877 (if any) using the 'tor-cov' coverage binary.
4878 - When running test-network or test-stem, check for the absence of
4879 stem/chutney before doing any build operations.
4882 Changes in version 0.2.7.2-alpha - 2015-07-27
4883 This, the second alpha in the Tor 0.2.7 series, has a number of new
4884 features, including a way to manually pick the number of introduction
4885 points for hidden services, and the much stronger Ed25519 signing key
4886 algorithm for regular Tor relays (including support for encrypted
4887 offline identity keys in the new algorithm).
4889 Support for Ed25519 on relays is currently limited to signing router
4890 descriptors; later alphas in this series will extend Ed25519 key
4891 support to more parts of the Tor protocol.
4893 o Major features (Ed25519 identity keys, Proposal 220):
4894 - All relays now maintain a stronger identity key, using the Ed25519
4895 elliptic curve signature format. This master key is designed so
4896 that it can be kept offline. Relays also generate an online
4897 signing key, and a set of other Ed25519 keys and certificates.
4898 These are all automatically regenerated and rotated as needed.
4899 Implements part of ticket 12498.
4900 - Directory authorities now vote on Ed25519 identity keys along with
4901 RSA1024 keys. Implements part of ticket 12498.
4902 - Directory authorities track which Ed25519 identity keys have been
4903 used with which RSA1024 identity keys, and do not allow them to
4904 vary freely. Implements part of ticket 12498.
4905 - Microdescriptors now include Ed25519 identity keys. Implements
4906 part of ticket 12498.
4907 - Add support for offline encrypted Ed25519 master keys. To use this
4908 feature on your tor relay, run "tor --keygen" to make a new master
4909 key (or to make a new signing key if you already have a master
4910 key). Closes ticket 13642.
4912 o Major features (Hidden services):
4913 - Add the torrc option HiddenServiceNumIntroductionPoints, to
4914 specify a fixed number of introduction points. Its maximum value
4915 is 10 and default is 3. Using this option can increase a hidden
4916 service's reliability under load, at the cost of making it more
4917 visible that the hidden service is facing extra load. Closes
4919 - Remove the adaptive algorithm for choosing the number of
4920 introduction points, which used to change the number of
4921 introduction points (poorly) depending on the number of
4922 connections the HS sees. Closes ticket 4862.
4924 o Major features (onion key cross-certification):
4925 - Relay descriptors now include signatures of their own identity
4926 keys, made using the TAP and ntor onion keys. These signatures
4927 allow relays to prove ownership of their own onion keys. Because
4928 of this change, microdescriptors will no longer need to include
4929 RSA identity keys. Implements proposal 228; closes ticket 12499.
4931 o Major features (performance):
4932 - Improve the runtime speed of Ed25519 operations by using the
4933 public-domain Ed25519-donna by Andrew M. ("floodyberry").
4934 Implements ticket 16467.
4935 - Improve the runtime speed of the ntor handshake by using an
4936 optimized curve25519 basepoint scalarmult implementation from the
4937 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
4938 ideas by Adam Langley. Implements ticket 9663.
4940 o Major bugfixes (client-side privacy, also in 0.2.6.9):
4941 - Properly separate out each SOCKSPort when applying stream
4942 isolation. The error occurred because each port's session group
4943 was being overwritten by a default value when the listener
4944 connection was initialized. Fixes bug 16247; bugfix on
4945 0.2.6.3-alpha. Patch by "jojelino".
4947 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
4948 - Stop refusing to store updated hidden service descriptors on a
4949 client. This reverts commit 9407040c59218 (which indeed fixed bug
4950 14219, but introduced a major hidden service reachability
4951 regression detailed in bug 16381). This is a temporary fix since
4952 we can live with the minor issue in bug 14219 (it just results in
4953 some load on the network) but the regression of 16381 is too much
4954 of a setback. First-round fix for bug 16381; bugfix
4957 o Major bugfixes (hidden services):
4958 - When cannibalizing a circuit for an introduction point, always
4959 extend to the chosen exit node (creating a 4 hop circuit).
4960 Previously Tor would use the current circuit exit node, which
4961 changed the original choice of introduction point, and could cause
4962 the hidden service to skip excluded introduction points or
4963 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
4966 o Major bugfixes (open file limit):
4967 - The open file limit wasn't checked before calling
4968 tor_accept_socket_nonblocking(), which would make Tor exceed the
4969 limit. Now, before opening a new socket, Tor validates the open
4970 file limit just before, and if the max has been reached, return an
4971 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
4973 o Major bugfixes (stability, also in 0.2.6.10):
4974 - Stop crashing with an assertion failure when parsing certain kinds
4975 of malformed or truncated microdescriptors. Fixes bug 16400;
4976 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
4977 by "cypherpunks_backup".
4978 - Stop random client-side assertion failures that could occur when
4979 connecting to a busy hidden service, or connecting to a hidden
4980 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
4983 o Minor features (directory authorities, security, also in 0.2.6.9):
4984 - The HSDir flag given by authorities now requires the Stable flag.
4985 For the current network, this results in going from 2887 to 2806
4986 HSDirs. Also, it makes it harder for an attacker to launch a sybil
4987 attack by raising the effort for a relay to become Stable to
4988 require at the very least 7 days, while maintaining the 96 hours
4989 uptime requirement for HSDir. Implements ticket 8243.
4991 o Minor features (client):
4992 - Relax the validation of hostnames in SOCKS5 requests, allowing the
4993 character '_' to appear, in order to cope with domains observed in
4994 the wild that are serving non-RFC compliant records. Resolves
4996 - Relax the validation done to hostnames in SOCKS5 requests, and
4997 allow a single trailing '.' to cope with clients that pass FQDNs
4998 using that syntax to explicitly indicate that the domain name is
4999 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
5000 - Add GroupWritable and WorldWritable options to unix-socket based
5001 SocksPort and ControlPort options. These options apply to a single
5002 socket, and override {Control,Socks}SocketsGroupWritable. Closes
5005 o Minor features (control protocol):
5006 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
5007 the control protocol. Resolves ticket 15358.
5009 o Minor features (directory authorities):
5010 - Directory authorities no longer vote against the "Fast", "Stable",
5011 and "HSDir" flags just because they were going to vote against
5012 "Running": if the consensus turns out to be that the router was
5013 running, then the authority's vote should count. Patch from Peter
5014 Retzlaff; closes issue 8712.
5016 o Minor features (geoip, also in 0.2.6.10):
5017 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
5018 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
5020 o Minor features (hidden services):
5021 - Add the new options "HiddenServiceMaxStreams" and
5022 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
5023 limit the maximum number of simultaneous streams per circuit, and
5024 optionally tear down the circuit when the limit is exceeded. Part
5027 o Minor features (portability):
5028 - Use C99 variadic macros when the compiler is not GCC. This avoids
5029 failing compilations on MSVC, and fixes a log-file-based race
5030 condition in our old workarounds. Original patch from Gisle Vanem.
5032 o Minor bugfixes (compilation, also in 0.2.6.9):
5033 - Build with --enable-systemd correctly when libsystemd is
5034 installed, but systemd is not. Fixes bug 16164; bugfix on
5035 0.2.6.3-alpha. Patch from Peter Palfrader.
5037 o Minor bugfixes (controller):
5038 - Add the descriptor ID in each HS_DESC control event. It was
5039 missing, but specified in control-spec.txt. Fixes bug 15881;
5040 bugfix on 0.2.5.2-alpha.
5042 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
5043 - Check for failures from crypto_early_init, and refuse to continue.
5044 A previous typo meant that we could keep going with an
5045 uninitialized crypto library, and would have OpenSSL initialize
5046 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5047 when implementing ticket 4900. Patch by "teor".
5049 o Minor bugfixes (hidden services):
5050 - Fix a crash when reloading configuration while at least one
5051 configured and one ephemeral hidden service exists. Fixes bug
5052 16060; bugfix on 0.2.7.1-alpha.
5053 - Avoid crashing with a double-free bug when we create an ephemeral
5054 hidden service but adding it fails for some reason. Fixes bug
5055 16228; bugfix on 0.2.7.1-alpha.
5057 o Minor bugfixes (Linux seccomp2 sandbox):
5058 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
5059 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
5061 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
5062 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
5063 these when eventfd2() support is missing. Fixes bug 16363; bugfix
5064 on 0.2.6.3-alpha. Patch from "teor".
5066 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
5067 - Fix sandboxing to work when running as a relay, by allowing the
5068 renaming of secret_id_key, and allowing the eventfd2 and futex
5069 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
5071 - Allow systemd connections to work with the Linux seccomp2 sandbox
5072 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
5075 o Minor bugfixes (relay):
5076 - Fix a rarely-encountered memory leak when failing to initialize
5077 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
5080 o Minor bugfixes (systemd):
5081 - Fix an accidental formatting error that broke the systemd
5082 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
5083 - Tor's systemd unit file no longer contains extraneous spaces.
5084 These spaces would sometimes confuse tools like deb-systemd-
5085 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
5087 o Minor bugfixes (tests):
5088 - Use the configured Python executable when running test-stem-full.
5089 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
5091 o Minor bugfixes (tests, also in 0.2.6.9):
5092 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
5093 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
5095 o Minor bugfixes (threads, comments):
5096 - Always initialize return value in compute_desc_id in rendcommon.c
5097 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
5098 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
5099 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
5100 - Remove undefined directive-in-macro in test_util_writepid clang
5101 3.7 complains that using a preprocessor directive inside a macro
5102 invocation in test_util_writepid in test_util.c is undefined.
5103 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
5105 o Code simplification and refactoring:
5106 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
5107 to ensure they remain consistent and visible everywhere.
5108 - Remove some vestigial workarounds for the MSVC6 compiler. We
5109 haven't supported that in ages.
5110 - The link authentication code has been refactored for better
5111 testability and reliability. It now uses code generated with the
5112 "trunnel" binary encoding generator, to reduce the risk of bugs
5113 due to programmer error. Done as part of ticket 12498.
5116 - Include a specific and (hopefully) accurate documentation of the
5117 torrc file's meta-format in doc/torrc_format.txt. This is mainly
5118 of interest to people writing programs to parse or generate torrc
5119 files. This document is not a commitment to long-term
5120 compatibility; some aspects of the current format are a bit
5121 ridiculous. Closes ticket 2325.
5124 - Tor no longer supports copies of OpenSSL that are missing support
5125 for Elliptic Curve Cryptography. (We began using ECC when
5126 available in 0.2.4.8-alpha, for more safe and efficient key
5127 negotiation.) In particular, support for at least one of P256 or
5128 P224 is now required, with manual configuration needed if only
5129 P224 is available. Resolves ticket 16140.
5130 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
5131 on an operating system that has not upgraded to OpenSSL 1.0 or
5132 later, and you compile Tor from source, you will need to install a
5133 more recent OpenSSL to link Tor against.) These versions of
5134 OpenSSL are still supported by the OpenSSL, but the numerous
5135 cryptographic improvements in later OpenSSL releases makes them a
5136 clear choice. Resolves ticket 16034.
5137 - Remove the HidServDirectoryV2 option. Now all relays offer to
5138 store hidden service descriptors. Related to 16543.
5139 - Remove the VoteOnHidServDirectoriesV2 option, since all
5140 authorities have long set it to 1. Closes ticket 16543.
5143 - Document use of coverity, clang static analyzer, and clang dynamic
5144 undefined behavior and address sanitizers in doc/HACKING. Include
5145 detailed usage instructions in the blacklist. Patch by "teor".
5146 Closes ticket 15817.
5147 - The link authentication protocol code now has extensive tests.
5148 - The relay descriptor signature testing code now has
5150 - The test_workqueue program now runs faster, and is enabled by
5151 default as a part of "make check".
5152 - Now that OpenSSL has its own scrypt implementation, add an unit
5153 test that checks for interoperability between libscrypt_scrypt()
5154 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
5155 and rely on EVP_PBE_scrypt() whenever possible. Resolves
5159 Changes in version 0.2.6.10 - 2015-07-12
5160 Tor version 0.2.6.10 fixes some significant stability and hidden
5161 service client bugs, bulletproofs the cryptography init process, and
5162 fixes a bug when using the sandbox code with some older versions of
5163 Linux. Everyone running an older version, especially an older version
5164 of 0.2.6, should upgrade.
5166 o Major bugfixes (hidden service clients, stability):
5167 - Stop refusing to store updated hidden service descriptors on a
5168 client. This reverts commit 9407040c59218 (which indeed fixed bug
5169 14219, but introduced a major hidden service reachability
5170 regression detailed in bug 16381). This is a temporary fix since
5171 we can live with the minor issue in bug 14219 (it just results in
5172 some load on the network) but the regression of 16381 is too much
5173 of a setback. First-round fix for bug 16381; bugfix
5176 o Major bugfixes (stability):
5177 - Stop crashing with an assertion failure when parsing certain kinds
5178 of malformed or truncated microdescriptors. Fixes bug 16400;
5179 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
5180 by "cypherpunks_backup".
5181 - Stop random client-side assertion failures that could occur when
5182 connecting to a busy hidden service, or connecting to a hidden
5183 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
5186 o Minor features (geoip):
5187 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
5188 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
5190 o Minor bugfixes (crypto error-handling):
5191 - Check for failures from crypto_early_init, and refuse to continue.
5192 A previous typo meant that we could keep going with an
5193 uninitialized crypto library, and would have OpenSSL initialize
5194 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5195 when implementing ticket 4900. Patch by "teor".
5197 o Minor bugfixes (Linux seccomp2 sandbox):
5198 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
5199 these when eventfd2() support is missing. Fixes bug 16363; bugfix
5200 on 0.2.6.3-alpha. Patch from "teor".
5203 Changes in version 0.2.6.9 - 2015-06-11
5204 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
5205 requirements for receiving an HSDir flag, and addresses some other small
5206 bugs in the systemd and sandbox code. Clients using circuit isolation
5207 should upgrade; all directory authorities should upgrade.
5209 o Major bugfixes (client-side privacy):
5210 - Properly separate out each SOCKSPort when applying stream
5211 isolation. The error occurred because each port's session group was
5212 being overwritten by a default value when the listener connection
5213 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
5216 o Minor feature (directory authorities, security):
5217 - The HSDir flag given by authorities now requires the Stable flag.
5218 For the current network, this results in going from 2887 to 2806
5219 HSDirs. Also, it makes it harder for an attacker to launch a sybil
5220 attack by raising the effort for a relay to become Stable which
5221 takes at the very least 7 days to do so and by keeping the 96
5222 hours uptime requirement for HSDir. Implements ticket 8243.
5224 o Minor bugfixes (compilation):
5225 - Build with --enable-systemd correctly when libsystemd is
5226 installed, but systemd is not. Fixes bug 16164; bugfix on
5227 0.2.6.3-alpha. Patch from Peter Palfrader.
5229 o Minor bugfixes (Linux seccomp2 sandbox):
5230 - Fix sandboxing to work when running as a relaymby renaming of
5231 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
5232 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
5233 - Allow systemd connections to work with the Linux seccomp2 sandbox
5234 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
5237 o Minor bugfixes (tests):
5238 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
5239 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
5242 Changes in version 0.2.6.8 - 2015-05-21
5243 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
5244 fixes an authority-side bug in assigning the HSDir flag. All directory
5245 authorities should upgrade.
5247 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
5248 - Revert commit that made directory authorities assign the HSDir
5249 flag to relays without a DirPort; this was bad because such relays
5250 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
5253 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5254 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5255 a client authorized hidden service. Fixes bug 15823; bugfix
5258 o Minor features (geoip):
5259 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
5260 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
5264 Changes in version 0.2.7.1-alpha - 2015-05-12
5265 Tor 0.2.7.1-alpha is the first alpha release in its series. It
5266 includes numerous small features and bugfixes against previous Tor
5267 versions, and numerous small infrastructure improvements. The most
5268 notable features are several new ways for controllers to interact with
5269 the hidden services subsystem.
5271 o New system requirements:
5272 - Tor no longer includes workarounds to support Libevent versions
5273 before 1.3e. Libevent 2.0 or later is recommended. Closes
5276 o Major features (controller):
5277 - Add the ADD_ONION and DEL_ONION commands that allow the creation
5278 and management of hidden services via the controller. Closes
5280 - New "GETINFO onions/current" and "GETINFO onions/detached"
5281 commands to get information about hidden services created via the
5282 controller. Part of ticket 6411.
5283 - New HSFETCH command to launch a request for a hidden service
5284 descriptor. Closes ticket 14847.
5285 - New HSPOST command to upload a hidden service descriptor. Closes
5286 ticket 3523. Patch by "DonnchaC".
5288 o Major bugfixes (hidden services):
5289 - Revert commit that made directory authorities assign the HSDir
5290 flag to relays without a DirPort; this was bad because such relays
5291 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
5294 o Minor features (clock-jump tolerance):
5295 - Recover better when our clock jumps back many hours, like might
5296 happen for Tails or Whonix users who start with a very wrong
5297 hardware clock, use Tor to discover a more accurate time, and then
5298 fix their clock. Resolves part of ticket 8766.
5300 o Minor features (command-line interface):
5301 - Make --hash-password imply --hush to prevent unnecessary noise.
5302 Closes ticket 15542. Patch from "cypherpunks".
5303 - Print a warning whenever we find a relative file path being used
5304 as torrc option. Resolves issue 14018.
5306 o Minor features (controller):
5307 - Add DirAuthority lines for default directory authorities to the
5308 output of the "GETINFO config/defaults" command if not already
5309 present. Implements ticket 14840.
5310 - Controllers can now use "GETINFO hs/client/desc/id/..." to
5311 retrieve items from the client's hidden service descriptor cache.
5312 Closes ticket 14845.
5313 - Implement a new controller command "GETINFO status/fresh-relay-
5314 descs" to fetch a descriptor/extrainfo pair that was generated on
5315 demand just for the controller's use. Implements ticket 14784.
5317 o Minor features (DoS-resistance):
5318 - Make it harder for attackers to overload hidden services with
5319 introductions, by blocking multiple introduction requests on the
5320 same circuit. Resolves ticket 15515.
5322 o Minor features (geoip):
5323 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
5324 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
5327 o Minor features (HS popularity countermeasure):
5328 - To avoid leaking HS popularity, don't cycle the introduction point
5329 when we've handled a fixed number of INTRODUCE2 cells but instead
5330 cycle it when a random number of introductions is reached, thus
5331 making it more difficult for an attacker to find out the amount of
5332 clients that have used the introduction point for a specific HS.
5333 Closes ticket 15745.
5335 o Minor features (logging):
5336 - Include the Tor version in all LD_BUG log messages, since people
5337 tend to cut and paste those into the bugtracker. Implements
5340 o Minor features (pluggable transports):
5341 - When launching managed pluggable transports on Linux systems,
5342 attempt to have the kernel deliver a SIGTERM on tor exit if the
5343 pluggable transport process is still running. Resolves
5345 - When launching managed pluggable transports, setup a valid open
5346 stdin in the child process that can be used to detect if tor has
5347 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
5348 can be used by implementations to detect this new behavior.
5349 Resolves ticket 15435.
5351 o Minor features (testing):
5352 - Add a test to verify that the compiler does not eliminate our
5353 memwipe() implementation. Closes ticket 15377.
5354 - Add make rule `check-changes` to verify the format of changes
5355 files. Closes ticket 15180.
5356 - Add unit tests for control_event_is_interesting(). Add a compile-
5357 time check that the number of events doesn't exceed the capacity
5358 of control_event_t.event_mask. Closes ticket 15431, checks for
5359 bugs similar to 13085. Patch by "teor".
5360 - Command-line argument tests moved to Stem. Resolves ticket 14806.
5361 - Integrate the ntor, backtrace, and zero-length keys tests into the
5362 automake test suite. Closes ticket 15344.
5363 - Remove assertions during builds to determine Tor's test coverage.
5364 We don't want to trigger these even in assertions, so including
5365 them artificially makes our branch coverage look worse than it is.
5366 This patch provides the new test-stem-full and coverage-html-full
5367 configure options. Implements ticket 15400.
5369 o Minor bugfixes (build):
5370 - Improve out-of-tree builds by making non-standard rules work and
5371 clean up additional files and directories. Fixes bug 15053; bugfix
5374 o Minor bugfixes (command-line interface):
5375 - When "--quiet" is provided along with "--validate-config", do not
5376 write anything to stdout on success. Fixes bug 14994; bugfix
5378 - When complaining about bad arguments to "--dump-config", use
5381 o Minor bugfixes (configuration, unit tests):
5382 - Only add the default fallback directories when the DirAuthorities,
5383 AlternateDirAuthority, and FallbackDir directory config options
5384 are set to their defaults. The default fallback directory list is
5385 currently empty, this fix will only change tor's behavior when it
5386 has default fallback directories. Includes unit tests for
5387 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
5388 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
5390 o Minor bugfixes (correctness):
5391 - For correctness, avoid modifying a constant string in
5392 handle_control_postdescriptor. Fixes bug 15546; bugfix
5394 - Remove side-effects from tor_assert() calls. This was harmless,
5395 because we never disable assertions, but it is bad style and
5396 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
5399 o Minor bugfixes (hidden service):
5400 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5401 a client authorized hidden service. Fixes bug 15823; bugfix
5403 - Remove an extraneous newline character from the end of hidden
5404 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
5406 o Minor bugfixes (interface):
5407 - Print usage information for --dump-config when it is used without
5408 an argument. Also, fix the error message to use different wording
5409 and add newline at the end. Fixes bug 15541; bugfix
5412 o Minor bugfixes (logs):
5413 - When building Tor under Clang, do not include an extra set of
5414 parentheses in log messages that include function names. Fixes bug
5415 15269; bugfix on every released version of Tor when compiled with
5416 recent enough Clang.
5418 o Minor bugfixes (network):
5419 - When attempting to use fallback technique for network interface
5420 lookup, disregard loopback and multicast addresses since they are
5421 unsuitable for public communications.
5423 o Minor bugfixes (statistics):
5424 - Disregard the ConnDirectionStatistics torrc options when Tor is
5425 not a relay since in that mode of operation no sensible data is
5426 being collected and because Tor might run into measurement hiccups
5427 when running as a client for some time, then becoming a relay.
5428 Fixes bug 15604; bugfix on 0.2.2.35.
5430 o Minor bugfixes (test networks):
5431 - When self-testing reachability, use ExtendAllowPrivateAddresses to
5432 determine if local/private addresses imply reachability. The
5433 previous fix used TestingTorNetwork, which implies
5434 ExtendAllowPrivateAddresses, but this excluded rare configurations
5435 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
5436 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
5437 issue discovered by CJ Ess.
5439 o Minor bugfixes (testing):
5440 - Check for matching value in server response in ntor_ref.py. Fixes
5441 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
5443 - Set the severity correctly when testing
5444 get_interface_addresses_ifaddrs() and
5445 get_interface_addresses_win32(), so that the tests fail gracefully
5446 instead of triggering an assertion. Fixes bug 15759; bugfix on
5447 0.2.6.3-alpha. Reported by Nicolas Derive.
5449 o Code simplification and refactoring:
5450 - Move the hacky fallback code out of get_interface_address6() into
5451 separate function and get it covered with unit-tests. Resolves
5453 - Refactor hidden service client-side cache lookup to intelligently
5454 report its various failure cases, and disentangle failure cases
5455 involving a lack of introduction points. Closes ticket 14391.
5456 - Use our own Base64 encoder instead of OpenSSL's, to allow more
5457 control over the output. Part of ticket 15652.
5460 - Improve the descriptions of statistics-related torrc options in
5461 the manpage to describe rationale and possible uses cases. Fixes
5463 - Improve the layout and formatting of ./configure --help messages.
5464 Closes ticket 15024. Patch from "cypherpunks".
5465 - Standardize on the term "server descriptor" in the manual page.
5466 Previously, we had used "router descriptor", "server descriptor",
5467 and "relay descriptor" interchangeably. Part of ticket 14987.
5470 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
5471 and always use the internal Base64 decoder. The internal decoder
5472 has been part of tor since 0.2.0.10-alpha, and no one should
5473 be using the OpenSSL one. Part of ticket 15652.
5474 - Remove the 'tor_strclear()' function; use memwipe() instead.
5475 Closes ticket 14922.
5478 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
5479 fingerprinting we now recommend pluggable transports; for forward-
5480 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
5481 - Remove the undocumented "--digests" command-line option. It
5482 complicated our build process, caused subtle build issues on
5483 multiple platforms, and is now redundant since we started
5484 including git version identifiers. Closes ticket 14742.
5485 - Tor no longer contains checks for ancient directory cache versions
5486 that didn't know about microdescriptors.
5487 - Tor no longer contains workarounds for stat files generated by
5488 super-old versions of Tor that didn't choose guards sensibly.
5491 Changes in version 0.2.4.27 - 2015-04-06
5492 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
5493 could be used by an attacker to crash hidden services, or crash clients
5494 visiting hidden services. Hidden services should upgrade as soon as
5495 possible; clients should upgrade whenever packages become available.
5497 This release also backports a simple improvement to make hidden
5498 services a bit less vulnerable to denial-of-service attacks.
5500 o Major bugfixes (security, hidden service):
5501 - Fix an issue that would allow a malicious client to trigger an
5502 assertion failure and halt a hidden service. Fixes bug 15600;
5503 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
5504 - Fix a bug that could cause a client to crash with an assertion
5505 failure when parsing a malformed hidden service descriptor. Fixes
5506 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
5508 o Minor features (DoS-resistance, hidden service):
5509 - Introduction points no longer allow multiple INTRODUCE1 cells to
5510 arrive on the same circuit. This should make it more expensive for
5511 attackers to overwhelm hidden services with introductions.
5512 Resolves ticket 15515.
5515 Changes in version 0.2.5.12 - 2015-04-06
5516 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
5517 could be used by an attacker to crash hidden services, or crash clients
5518 visiting hidden services. Hidden services should upgrade as soon as
5519 possible; clients should upgrade whenever packages become available.
5521 This release also backports a simple improvement to make hidden
5522 services a bit less vulnerable to denial-of-service attacks.
5524 o Major bugfixes (security, hidden service):
5525 - Fix an issue that would allow a malicious client to trigger an
5526 assertion failure and halt a hidden service. Fixes bug 15600;
5527 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
5528 - Fix a bug that could cause a client to crash with an assertion
5529 failure when parsing a malformed hidden service descriptor. Fixes
5530 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
5532 o Minor features (DoS-resistance, hidden service):
5533 - Introduction points no longer allow multiple INTRODUCE1 cells to
5534 arrive on the same circuit. This should make it more expensive for
5535 attackers to overwhelm hidden services with introductions.
5536 Resolves ticket 15515.
5539 Changes in version 0.2.6.7 - 2015-04-06
5540 Tor 0.2.6.7 fixes two security issues that could be used by an
5541 attacker to crash hidden services, or crash clients visiting hidden
5542 services. Hidden services should upgrade as soon as possible; clients
5543 should upgrade whenever packages become available.
5545 This release also contains two simple improvements to make hidden
5546 services a bit less vulnerable to denial-of-service attacks.
5548 o Major bugfixes (security, hidden service):
5549 - Fix an issue that would allow a malicious client to trigger an
5550 assertion failure and halt a hidden service. Fixes bug 15600;
5551 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
5552 - Fix a bug that could cause a client to crash with an assertion
5553 failure when parsing a malformed hidden service descriptor. Fixes
5554 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
5556 o Minor features (DoS-resistance, hidden service):
5557 - Introduction points no longer allow multiple INTRODUCE1 cells to
5558 arrive on the same circuit. This should make it more expensive for
5559 attackers to overwhelm hidden services with introductions.
5560 Resolves ticket 15515.
5561 - Decrease the amount of reattempts that a hidden service performs
5562 when its rendezvous circuits fail. This reduces the computational
5563 cost for running a hidden service under heavy load. Resolves
5567 Changes in version 0.2.6.6 - 2015-03-24
5568 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
5570 It adds numerous safety, security, correctness, and performance
5571 improvements. Client programs can be configured to use more kinds of
5572 sockets, AutomapHosts works better, the multithreading backend is
5573 improved, cell transmission is refactored, test coverage is much
5574 higher, more denial-of-service attacks are handled, guard selection is
5575 improved to handle long-term guards better, pluggable transports
5576 should work a bit better, and some annoying hidden service performance
5577 bugs should be addressed.
5579 o Minor bugfixes (portability):
5580 - Use the correct datatype in the SipHash-2-4 function to prevent
5581 compilers from assuming any sort of alignment. Fixes bug 15436;
5582 bugfix on 0.2.5.3-alpha.
5584 Changes in version 0.2.6.5-rc - 2015-03-18
5585 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
5586 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
5588 o Major bugfixes (client):
5589 - Avoid crashing when making certain configuration option changes on
5590 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
5593 o Major bugfixes (pluggable transports):
5594 - Initialize the extended OR Port authentication cookie before
5595 launching pluggable transports. This prevents a race condition
5596 that occured when server-side pluggable transports would cache the
5597 authentication cookie before it has been (re)generated. Fixes bug
5598 15240; bugfix on 0.2.5.1-alpha.
5600 o Major bugfixes (portability):
5601 - Do not crash on startup when running on Solaris. Fixes a bug
5602 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
5605 o Minor features (heartbeat):
5606 - On relays, report how many connections we negotiated using each
5607 version of the Tor link protocols. This information will let us
5608 know if removing support for very old versions of the Tor
5609 protocols is harming the network. Closes ticket 15212.
5611 o Code simplification and refactoring:
5612 - Refactor main loop to extract the 'loop' part. This makes it
5613 easier to run Tor under Shadow. Closes ticket 15176.
5616 Changes in version 0.2.5.11 - 2015-03-17
5617 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
5619 It backports several bugfixes from the 0.2.6 branch, including a
5620 couple of medium-level security fixes for relays and exit nodes.
5621 It also updates the list of directory authorities.
5623 o Directory authority changes:
5624 - Remove turtles as a directory authority.
5625 - Add longclaw as a new (v3) directory authority. This implements
5626 ticket 13296. This keeps the directory authority count at 9.
5627 - The directory authority Faravahar has a new IP address. This
5628 closes ticket 14487.
5630 o Major bugfixes (crash, OSX, security):
5631 - Fix a remote denial-of-service opportunity caused by a bug in
5632 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
5635 o Major bugfixes (relay, stability, possible security):
5636 - Fix a bug that could lead to a relay crashing with an assertion
5637 failure if a buffer of exactly the wrong layout was passed to
5638 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
5639 0.2.0.10-alpha. Patch from 'cypherpunks'.
5640 - Do not assert if the 'data' pointer on a buffer is advanced to the
5641 very end of the buffer; log a BUG message instead. Only assert if
5642 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
5644 o Major bugfixes (exit node stability):
5645 - Fix an assertion failure that could occur under high DNS load.
5646 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
5647 diagnosed and fixed by "cypherpunks".
5649 o Major bugfixes (Linux seccomp2 sandbox):
5650 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
5651 crash during attempts to call wait4. Fixes bug 15088; bugfix on
5652 0.2.5.1-alpha. Patch from "sanic".
5654 o Minor features (controller):
5655 - New "GETINFO bw-event-cache" to get information about recent
5656 bandwidth events. Closes ticket 14128. Useful for controllers to
5657 get recent bandwidth history after the fix for ticket 13988.
5659 o Minor features (geoip):
5660 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
5661 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
5664 o Minor bugfixes (client, automapping):
5665 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
5666 no value follows the option. Fixes bug 14142; bugfix on
5667 0.2.4.7-alpha. Patch by "teor".
5668 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
5669 14195; bugfix on 0.1.0.1-rc.
5671 o Minor bugfixes (compilation):
5672 - Build without warnings with the stock OpenSSL srtp.h header, which
5673 has a duplicate declaration of SSL_get_selected_srtp_profile().
5674 Fixes bug 14220; this is OpenSSL's bug, not ours.
5676 o Minor bugfixes (directory authority):
5677 - Allow directory authorities to fetch more data from one another if
5678 they find themselves missing lots of votes. Previously, they had
5679 been bumping against the 10 MB queued data limit. Fixes bug 14261;
5680 bugfix on 0.1.2.5-alpha.
5681 - Enlarge the buffer to read bwauth generated files to avoid an
5682 issue when parsing the file in dirserv_read_measured_bandwidths().
5683 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
5685 o Minor bugfixes (statistics):
5686 - Increase period over which bandwidth observations are aggregated
5687 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
5689 o Minor bugfixes (preventative security, C safety):
5690 - When reading a hexadecimal, base-32, or base-64 encoded value from
5691 a string, always overwrite the whole output buffer. This prevents
5692 some bugs where we would look at (but fortunately, not reveal)
5693 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
5697 Changes in version 0.2.4.26 - 2015-03-17
5698 Tor 0.2.4.26 includes an updated list of directory authorities. It
5699 also backports a couple of stability and security bugfixes from 0.2.5
5702 o Directory authority changes:
5703 - Remove turtles as a directory authority.
5704 - Add longclaw as a new (v3) directory authority. This implements
5705 ticket 13296. This keeps the directory authority count at 9.
5706 - The directory authority Faravahar has a new IP address. This
5707 closes ticket 14487.
5709 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
5710 - Fix an assertion failure that could occur under high DNS load.
5711 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
5712 diagnosed and fixed by "cypherpunks".
5714 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
5715 - Fix a bug that could lead to a relay crashing with an assertion
5716 failure if a buffer of exactly the wrong layout was passed to
5717 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
5718 0.2.0.10-alpha. Patch from 'cypherpunks'.
5719 - Do not assert if the 'data' pointer on a buffer is advanced to the
5720 very end of the buffer; log a BUG message instead. Only assert if
5721 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
5723 o Minor features (geoip):
5724 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
5725 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
5728 Changes in version 0.2.6.4-rc - 2015-03-09
5729 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
5730 attacker might be able to use in order to crash certain Tor
5731 directories. It also resolves some minor issues left over from, or
5732 introduced in, Tor 0.2.6.3-alpha or earlier.
5734 o Major bugfixes (crash, OSX, security):
5735 - Fix a remote denial-of-service opportunity caused by a bug in
5736 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
5739 o Major bugfixes (relay, stability, possible security):
5740 - Fix a bug that could lead to a relay crashing with an assertion
5741 failure if a buffer of exactly the wrong layout is passed to
5742 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
5743 0.2.0.10-alpha. Patch from "cypherpunks".
5744 - Do not assert if the 'data' pointer on a buffer is advanced to the
5745 very end of the buffer; log a BUG message instead. Only assert if
5746 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
5748 o Major bugfixes (FreeBSD IPFW transparent proxy):
5749 - Fix address detection with FreeBSD transparent proxies, when
5750 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
5753 o Major bugfixes (Linux seccomp2 sandbox):
5754 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
5755 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
5757 - Allow AF_UNIX hidden services to be used with the seccomp2
5758 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
5759 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
5760 crash during attempts to call wait4. Fixes bug 15088; bugfix on
5761 0.2.5.1-alpha. Patch from "sanic".
5763 o Minor features (controller):
5764 - Messages about problems in the bootstrap process now include
5765 information about the server we were trying to connect to when we
5766 noticed the problem. Closes ticket 15006.
5768 o Minor features (geoip):
5769 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
5770 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
5773 o Minor features (logs):
5774 - Quiet some log messages in the heartbeat and at startup. Closes
5777 o Minor bugfixes (certificate handling):
5778 - If an authority operator accidentally makes a signing certificate
5779 with a future publication time, do not discard its real signing
5780 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
5781 - Remove any old authority certificates that have been superseded
5782 for at least two days. Previously, we would keep superseded
5783 certificates until they expired, if they were published close in
5784 time to the certificate that superseded them. Fixes bug 11454;
5785 bugfix on 0.2.1.8-alpha.
5787 o Minor bugfixes (compilation):
5788 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
5790 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
5793 o Minor bugfixes (testing):
5794 - Fix endianness issues in unit test for resolve_my_address() to
5795 have it pass on big endian systems. Fixes bug 14980; bugfix on
5797 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
5798 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
5799 - When running the new 'make test-stem' target, use the configured
5800 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
5802 - When running the zero-length-keys tests, do not use the default
5803 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
5806 o Directory authority IP change:
5807 - The directory authority Faravahar has a new IP address. This
5808 closes ticket 14487.
5811 - Remove some lingering dead code that once supported mempools.
5812 Mempools were disabled by default in 0.2.5, and removed entirely
5813 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
5817 Changes in version 0.2.6.3-alpha - 2015-02-19
5818 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
5819 the 0.2.6.x series. It introduces support for more kinds of sockets,
5820 makes it harder to accidentally run an exit, improves our
5821 multithreading backend, incorporates several fixes for the
5822 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
5824 If no major regressions or security holes are found in this version,
5825 the next version will be a release candidate.
5827 o Deprecated versions:
5828 - Tor relays older than 0.2.4.18-rc are no longer allowed to
5829 advertise themselves on the network. Closes ticket 13555.
5831 o Major features (security, unix domain sockets):
5832 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
5833 applications can reach Tor without having to create AF_INET or
5834 AF_INET6 sockets, meaning they can completely disable their
5835 ability to make non-Tor network connections. To create a socket of
5836 this type, use "SocksPort unix:/path/to/socket". Implements
5838 - Support mapping hidden service virtual ports to AF_UNIX sockets.
5839 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
5840 Implements ticket 11485.
5842 o Major features (changed defaults):
5843 - Prevent relay operators from unintentionally running exits: When a
5844 relay is configured as an exit node, we now warn the user unless
5845 the "ExitRelay" option is set to 1. We warn even more loudly if
5846 the relay is configured with the default exit policy, since this
5847 can indicate accidental misconfiguration. Setting "ExitRelay 0"
5848 stops Tor from running as an exit relay. Closes ticket 10067.
5850 o Major features (directory system):
5851 - When downloading server- or microdescriptors from a directory
5852 server, we no longer launch multiple simultaneous requests to the
5853 same server. This reduces load on the directory servers,
5854 especially when directory guards are in use. Closes ticket 9969.
5855 - When downloading server- or microdescriptors over a tunneled
5856 connection, do not limit the length of our requests to what the
5857 Squid proxy is willing to handle. Part of ticket 9969.
5858 - Authorities can now vote on the correct digests and latest
5859 versions for different software packages. This allows packages
5860 that include Tor to use the Tor authority system as a way to get
5861 notified of updates and their correct digests. Implements proposal
5862 227. Closes ticket 10395.
5864 o Major features (guards):
5865 - Introduce the Guardfraction feature to improves load balancing on
5866 guard nodes. Specifically, it aims to reduce the traffic gap that
5867 guard nodes experience when they first get the Guard flag. This is
5868 a required step if we want to increase the guard lifetime to 9
5869 months or greater. Closes ticket 9321.
5871 o Major features (performance):
5872 - Make the CPU worker implementation more efficient by avoiding the
5873 kernel and lengthening pipelines. The original implementation used
5874 sockets to transfer data from the main thread to the workers, and
5875 didn't allow any thread to be assigned more than a single piece of
5876 work at once. The new implementation avoids communications
5877 overhead by making requests in shared memory, avoiding kernel IO
5878 where possible, and keeping more requests in flight at once.
5879 Implements ticket 9682.
5881 o Major features (relay):
5882 - Raise the minimum acceptable configured bandwidth rate for bridges
5883 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
5884 20 KiB/sec.) Closes ticket 13822.
5886 o Major bugfixes (exit node stability):
5887 - Fix an assertion failure that could occur under high DNS load.
5888 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
5889 diagnosed and fixed by "cypherpunks".
5891 o Major bugfixes (mixed relay-client operation):
5892 - When running as a relay and client at the same time (not
5893 recommended), if we decide not to use a new guard because we want
5894 to retry older guards, only close the locally-originating circuits
5895 passing through that guard. Previously we would close all the
5896 circuits through that guard. Fixes bug 9819; bugfix on
5897 0.2.1.1-alpha. Reported by "skruffy".
5899 o Minor features (build):
5900 - New --disable-system-torrc compile-time option to prevent Tor from
5901 looking for the system-wide torrc or torrc-defaults files.
5902 Resolves ticket 13037.
5904 o Minor features (controller):
5905 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
5906 events so controllers can observe circuit isolation inputs. Closes
5908 - ControlPort now supports the unix:/path/to/socket syntax as an
5909 alternative to the ControlSocket option, for consistency with
5910 SocksPort and HiddenServicePort. Closes ticket 14451.
5911 - New "GETINFO bw-event-cache" to get information about recent
5912 bandwidth events. Closes ticket 14128. Useful for controllers to
5913 get recent bandwidth history after the fix for ticket 13988.
5915 o Minor features (Denial of service resistance):
5916 - Count the total number of bytes used storing hidden service
5917 descriptors against the value of MaxMemInQueues. If we're low on
5918 memory, and more than 20% of our memory is used holding hidden
5919 service descriptors, free them until no more than 10% of our
5920 memory holds hidden service descriptors. Free the least recently
5921 fetched descriptors first. Resolves ticket 13806.
5922 - When we have recently been under memory pressure (over 3/4 of
5923 MaxMemInQueues is allocated), then allocate smaller zlib objects
5924 for small requests. Closes ticket 11791.
5926 o Minor features (geoip):
5927 - Update geoip and geoip6 files to the January 7 2015 Maxmind
5928 GeoLite2 Country database.
5930 o Minor features (guard nodes):
5931 - Reduce the time delay before saving guard status to disk from 10
5932 minutes to 30 seconds (or from one hour to 10 minutes if
5933 AvoidDiskWrites is set). Closes ticket 12485.
5935 o Minor features (hidden service):
5936 - Make Sybil attacks against hidden services harder by changing the
5937 minimum time required to get the HSDir flag from 25 hours up to 96
5938 hours. Addresses ticket 14149.
5939 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
5940 services to disable the anti-scanning feature introduced in
5941 0.2.6.2-alpha. With this option not set, a connection to an
5942 unlisted port closes the circuit. With this option set, only a
5943 RELAY_DONE cell is sent. Closes ticket 14084.
5945 o Minor features (interface):
5946 - Implement "-f -" command-line option to read torrc configuration
5947 from standard input, if you don't want to store the torrc file in
5948 the file system. Implements feature 13865.
5950 o Minor features (logging):
5951 - Add a count of unique clients to the bridge heartbeat message.
5952 Resolves ticket 6852.
5953 - Suppress "router info incompatible with extra info" message when
5954 reading extrainfo documents from cache. (This message got loud
5955 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
5957 - Elevate hidden service authorized-client message from DEBUG to
5958 INFO. Closes ticket 14015.
5960 o Minor features (stability):
5961 - Add assertions in our hash-table iteration code to check for
5962 corrupted values that could cause infinite loops. Closes
5965 o Minor features (systemd):
5966 - Various improvements and modernizations in systemd hardening
5967 support. Closes ticket 13805. Patch from Craig Andrews.
5969 o Minor features (testing networks):
5970 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
5971 and the default on a testing network to 2 minutes. Drop the
5972 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
5973 keep the default on a testing network at 30 seconds. This reduces
5974 HS bootstrap time to around 25 seconds. Also, change the default
5975 time in test-network.sh to match. Closes ticket 13401. Patch
5977 - Create TestingDirAuthVoteHSDir to correspond to
5978 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
5979 HSDir flag for the listed relays regardless of uptime or ORPort
5980 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
5981 Partial implementation for ticket 14067. Patch by "teor".
5983 o Minor features (tor2web mode):
5984 - Introduce the config option Tor2webRendezvousPoints, which allows
5985 clients in Tor2webMode to select a specific Rendezvous Point to be
5986 used in HS circuits. This might allow better performance for
5987 Tor2Web nodes. Implements ticket 12844.
5989 o Minor bugfixes (client DNS):
5990 - Report the correct cached DNS expiration times on SOCKS port or in
5991 DNS replies. Previously, we would report everything as "never
5992 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
5993 - Avoid a small memory leak when we find a cached answer for a
5994 reverse DNS lookup in a client-side DNS cache. (Remember, client-
5995 side DNS caching is off by default, and is not recommended.) Fixes
5996 bug 14259; bugfix on 0.2.0.1-alpha.
5998 o Minor bugfixes (client, automapping):
5999 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
6000 no value follows the option. Fixes bug 14142; bugfix on
6001 0.2.4.7-alpha. Patch by "teor".
6002 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
6003 14195; bugfix on 0.1.0.1-rc.
6004 - Prevent changes to other options from removing the wildcard value
6005 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
6007 - Allow MapAddress and AutomapHostsOnResolve to work together when
6008 an address is mapped into another address type (like .onion) that
6009 must be automapped at resolve time. Fixes bug 7555; bugfix
6012 o Minor bugfixes (client, bridges):
6013 - When we are using bridges and we had a network connectivity
6014 problem, only retry connecting to our currently configured
6015 bridges, not all bridges we know about and remember using. Fixes
6016 bug 14216; bugfix on 0.2.2.17-alpha.
6018 o Minor bugfixes (client, IPv6):
6019 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
6020 flag is not set; and not because the NoIPv4Traffic flag was set.
6021 Previously we'd looked at the NoIPv4Traffic flag for both types of
6022 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
6024 o Minor bugfixes (compilation):
6025 - The address of an array in the middle of a structure will always
6026 be non-NULL. clang recognises this and complains. Disable the
6027 tautologous and redundant check to silence this warning. Fixes bug
6028 14001; bugfix on 0.2.1.2-alpha.
6029 - Avoid warnings when building with systemd 209 or later. Fixes bug
6030 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
6031 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
6032 Addresses ticket 14188.
6033 - Build without warnings with the stock OpenSSL srtp.h header, which
6034 has a duplicate declaration of SSL_get_selected_srtp_profile().
6035 Fixes bug 14220; this is OpenSSL's bug, not ours.
6036 - Do not compile any code related to Tor2Web mode when Tor2Web mode
6037 is not enabled at compile time. Previously, this code was included
6038 in a disabled state. See discussion on ticket 12844.
6039 - Remove the --disable-threads configure option again. It was
6040 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
6041 14819; bugfix on 0.2.6.2-alpha.
6043 o Minor bugfixes (controller):
6044 - Report "down" in response to the "GETINFO entry-guards" command
6045 when relays are down with an unreachable_since value. Previously,
6046 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
6047 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
6048 14116; bugfix on 0.2.2.9-alpha.
6049 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
6050 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
6052 o Minor bugfixes (directory authority):
6053 - Allow directory authorities to fetch more data from one another if
6054 they find themselves missing lots of votes. Previously, they had
6055 been bumping against the 10 MB queued data limit. Fixes bug 14261;
6056 bugfix on 0.1.2.5-alpha.
6057 - Do not attempt to download extrainfo documents which we will be
6058 unable to validate with a matching server descriptor. Fixes bug
6059 13762; bugfix on 0.2.0.1-alpha.
6060 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
6061 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
6062 - Enlarge the buffer to read bwauth generated files to avoid an
6063 issue when parsing the file in dirserv_read_measured_bandwidths().
6064 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
6066 o Minor bugfixes (file handling):
6067 - Stop failing when key files are zero-length. Instead, generate new
6068 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
6069 on all versions of Tor. Patch by "teor".
6070 - Stop generating a fresh .old RSA onion key file when the .old file
6071 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
6072 - Avoid overwriting .old key files with empty key files.
6073 - Skip loading zero-length extrainfo store, router store, stats,
6074 state, and key files.
6075 - Avoid crashing when trying to reload a torrc specified as a
6076 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
6079 o Minor bugfixes (hidden services):
6080 - Close the introduction circuit when we have no more usable intro
6081 points, instead of waiting for it to time out. This also ensures
6082 that no follow-up HS descriptor fetch is triggered when the
6083 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
6084 - When fetching a hidden service descriptor for a down service that
6085 was recently up, do not keep refetching until we try the same
6086 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
6087 - Successfully launch Tor with a nonexistent hidden service
6088 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
6089 14106; bugfix on 0.2.6.2-alpha.
6091 o Minor bugfixes (logging):
6092 - Avoid crashing when there are more log domains than entries in
6093 domain_list. Bugfix on 0.2.3.1-alpha.
6094 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
6096 - Don't log messages to stdout twice when starting up. Fixes bug
6097 13993; bugfix on 0.2.6.1-alpha.
6099 o Minor bugfixes (parsing):
6100 - Stop accepting milliseconds (or other junk) at the end of
6101 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
6102 - Support two-number and three-number version numbers correctly, in
6103 case we change the Tor versioning system in the future. Fixes bug
6104 13661; bugfix on 0.0.8pre1.
6106 o Minor bugfixes (path counting):
6107 - When deciding whether the consensus lists any exit nodes, count
6108 the number listed in the consensus, not the number we have
6109 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
6110 - When deciding whether we have any exit nodes, only examine
6111 ExitNodes when the ExitNodes option is actually set. Fixes part of
6112 bug 14918; bugfix on 0.2.6.2-alpha.
6113 - Get rid of redundant and possibly scary warnings that we are
6114 missing directory information while we bootstrap. Fixes part of
6115 bug 14918; bugfix on 0.2.6.2-alpha.
6117 o Minor bugfixes (portability):
6118 - Fix the ioctl()-based network interface lookup code so that it
6119 will work on systems that have variable-length struct ifreq, for
6121 - Fix scheduler compilation on targets where char is unsigned. Fixes
6122 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
6124 o Minor bugfixes (sandbox):
6125 - Allow glibc fatal errors to be sent to stderr before Tor exits.
6126 Previously, glibc would try to write them to /dev/tty, and the
6127 sandbox would trap the call and make Tor exit prematurely. Fixes
6128 bug 14759; bugfix on 0.2.5.1-alpha.
6130 o Minor bugfixes (shutdown):
6131 - When shutting down, always call event_del() on lingering read or
6132 write events before freeing them. Otherwise, we risk double-frees
6133 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
6136 o Minor bugfixes (small memory leaks):
6137 - Avoid leaking memory when using IPv6 virtual address mappings.
6138 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
6141 o Minor bugfixes (statistics):
6142 - Increase period over which bandwidth observations are aggregated
6143 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
6145 o Minor bugfixes (systemd support):
6146 - Fix detection and operation of systemd watchdog. Fixes part of bug
6147 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
6148 - Run correctly under systemd with the RunAsDaemon option set. Fixes
6149 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
6150 - Inform the systemd supervisor about more changes in the Tor
6151 process status. Implements part of ticket 14141. Patch from
6153 - Cause the "--disable-systemd" option to actually disable systemd
6154 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
6157 o Minor bugfixes (TLS):
6158 - Check more thoroughly throughout the TLS code for possible
6159 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
6161 o Minor bugfixes (transparent proxy):
6162 - Use getsockname, not getsockopt, to retrieve the address for a
6163 TPROXY-redirected connection. Fixes bug 13796; bugfix
6166 o Code simplification and refactoring:
6167 - Move fields related to isolating and configuring client ports into
6168 a shared structure. Previously, they were duplicated across
6169 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
6170 to copy them correctly had been the cause of at least one bug in
6171 the past. Closes ticket 8546.
6172 - Refactor the get_interface_addresses_raw() doom-function into
6173 multiple smaller and simpler subfunctions. Cover the resulting
6174 subfunctions with unit-tests. Fixes a significant portion of
6176 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
6177 only for version <= 0.2.2.24 which is now deprecated. Closes
6179 - Remove a test for a long-defunct broken version-one
6183 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
6184 for writing the OpenBSD-specific tips. Resolves ticket 13702.
6185 - Make the tor-resolve documentation match its help string and its
6186 options. Resolves part of ticket 14325.
6187 - Log a more useful error message from tor-resolve when failing to
6188 look up a hidden service address. Resolves part of ticket 14325.
6190 o Downgraded warnings:
6191 - Don't warn when we've attempted to contact a relay using the wrong
6192 ntor onion key. Closes ticket 9635.
6195 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
6196 longer silently accepted as an alias for "ExitNodes".
6197 - The --enable-mempool and --enable-buf-freelists options, which
6198 were originally created to work around bad malloc implementations,
6199 no longer exist. They were off-by-default in 0.2.5. Closes
6203 - Make the checkdir/perms test complete successfully even if the
6204 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
6205 - Test that tor does not fail when key files are zero-length. Check
6206 that tor generates new keys, and overwrites the empty key files.
6207 - Test that tor generates new keys when keys are missing
6208 (existing behavior).
6209 - Test that tor does not overwrite key files that already contain
6210 data (existing behavior). Tests bug 13111. Patch by "teor".
6211 - New "make test-stem" target to run stem integration tests.
6212 Requires that the "STEM_SOURCE_DIR" environment variable be set.
6213 Closes ticket 14107.
6214 - Make the test_cmdline_args.py script work correctly on Windows.
6215 Patch from Gisle Vanem.
6216 - Move the slower unit tests into a new "./src/test/test-slow"
6217 binary that can be run independently of the other tests. Closes
6219 - Avoid undefined behavior when sampling huge values from the
6220 Laplace distribution. This made unittests fail on Raspberry Pi.
6221 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
6224 Changes in version 0.2.6.2-alpha - 2014-12-31
6225 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
6226 It introduces a major new backend for deciding when to send cells on
6227 channels, which should lead down the road to big performance
6228 increases. It contains security and statistics features for better
6229 work on hidden services, and numerous bugfixes.
6231 This release contains many new unit tests, along with major
6232 performance improvements for running testing networks using Chutney.
6233 Thanks to a series of patches contributed by "teor", testing networks
6234 should now bootstrap in seconds, rather than minutes.
6236 o Major features (relay, infrastructure):
6237 - Complete revision of the code that relays use to decide which cell
6238 to send next. Formerly, we selected the best circuit to write on
6239 each channel, but we didn't select among channels in any
6240 sophisticated way. Now, we choose the best circuits globally from
6241 among those whose channels are ready to deliver traffic.
6243 This patch implements a new inter-cmux comparison API, a global
6244 high/low watermark mechanism and a global scheduler loop for
6245 transmission prioritization across all channels as well as among
6246 circuits on one channel. This schedule is currently tuned to
6247 (tolerantly) avoid making changes in network performance, but it
6248 should form the basis for major circuit performance increases in
6249 the future. Code by Andrea; tuning by Rob Jansen; implements
6252 o Major features (hidden services):
6253 - Make HS port scanning more difficult by immediately closing the
6254 circuit when a user attempts to connect to a nonexistent port.
6255 Closes ticket 13667.
6256 - Add a HiddenServiceStatistics option that allows Tor relays to
6257 gather and publish statistics about the overall size and volume of
6258 hidden service usage. Specifically, when this option is turned on,
6259 an HSDir will publish an approximate number of hidden services
6260 that have published descriptors to it the past 24 hours. Also, if
6261 a relay has acted as a hidden service rendezvous point, it will
6262 publish the approximate amount of rendezvous cells it has relayed
6263 the past 24 hours. The statistics themselves are obfuscated so
6264 that the exact values cannot be derived. For more details see
6265 proposal 238, "Better hidden service stats from Tor relays". This
6266 feature is currently disabled by default. Implements feature 13192.
6268 o Major bugfixes (client, automap):
6269 - Repair automapping with IPv6 addresses. This automapping should
6270 have worked previously, but one piece of debugging code that we
6271 inserted to detect a regression actually caused the regression to
6272 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
6273 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
6276 o Major bugfixes (hidden services):
6277 - When closing an introduction circuit that was opened in parallel
6278 with others, don't mark the introduction point as unreachable.
6279 Previously, the first successful connection to an introduction
6280 point would make the other introduction points get marked as
6281 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
6283 o Directory authority changes:
6284 - Remove turtles as a directory authority.
6285 - Add longclaw as a new (v3) directory authority. This implements
6286 ticket 13296. This keeps the directory authority count at 9.
6288 o Major removed features:
6289 - Tor clients no longer support connecting to hidden services
6290 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
6291 option has been removed. (There shouldn't be any hidden services
6292 running these versions on the network.) Closes ticket 7803.
6294 o Minor features (client):
6295 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
6296 is enabled, reject requests with IP addresses as hostnames.
6297 Resolves ticket 13315.
6299 o Minor features (controller):
6300 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
6301 write an unscheduled heartbeat message to the log. Implements
6304 o Minor features (geoip):
6305 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
6308 o Minor features (hidden services):
6309 - When re-enabling the network, don't try to build introduction
6310 circuits until we have successfully built a circuit. This makes
6311 hidden services come up faster when the network is re-enabled.
6312 Patch from "akwizgran". Closes ticket 13447.
6313 - When we fail to retrieve a hidden service descriptor, send the
6314 controller an "HS_DESC FAILED" controller event. Implements
6316 - New HiddenServiceDirGroupReadable option to cause hidden service
6317 directories and hostname files to be created group-readable. Patch
6318 from "anon", David Stainton, and "meejah". Closes ticket 11291.
6320 o Minor features (systemd):
6321 - Where supported, when running with systemd, report successful
6322 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
6323 - When running with systemd, support systemd watchdog messages. Part
6324 of ticket 11016. Patch by Michael Scherer.
6326 o Minor features (transparent proxy):
6327 - Update the transparent proxy option checks to allow for both ipfw
6328 and pf on OS X. Closes ticket 14002.
6329 - Use the correct option when using IPv6 with transparent proxy
6330 support on Linux. Resolves 13808. Patch by Francisco Blas
6333 o Minor bugfixes (preventative security, C safety):
6334 - When reading a hexadecimal, base-32, or base-64 encoded value from
6335 a string, always overwrite the whole output buffer. This prevents
6336 some bugs where we would look at (but fortunately, not reveal)
6337 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
6339 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
6340 just the part that's used. This makes it harder for data leak bugs
6341 to occur in the event of other programming failures. Resolves
6344 o Minor bugfixes (client, microdescriptors):
6345 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
6346 computing which microdescriptors to download. This keeps us from
6347 erroneous download behavior if two microdescriptor digests ever
6348 have the same first 160 bits. Fixes part of bug 13399; bugfix
6350 - Reset a router's status if its microdescriptor digest changes,
6351 even if the first 160 bits remain the same. Fixes part of bug
6352 13399; bugfix on 0.2.3.1-alpha.
6354 o Minor bugfixes (compilation):
6355 - Silence clang warnings under --enable-expensive-hardening,
6356 including implicit truncation of 64 bit values to 32 bit, const
6357 char assignment to self, tautological compare, and additional
6358 parentheses around equality tests. Fixes bug 13577; bugfix
6360 - Fix a clang warning about checking whether an address in the
6361 middle of a structure is NULL. Fixes bug 14001; bugfix
6364 o Minor bugfixes (hidden services):
6365 - Correctly send a controller event when we find that a rendezvous
6366 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
6367 - Pre-check directory permissions for new hidden-services to avoid
6368 at least one case of "Bug: Acting on config options left us in a
6369 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
6370 - When adding a new hidden service (for example, via SETCONF), Tor
6371 no longer congratulates the user for running a relay. Fixes bug
6372 13941; bugfix on 0.2.6.1-alpha.
6373 - When fetching hidden service descriptors, we now check not only
6374 for whether we got the hidden service we had in mind, but also
6375 whether we got the particular descriptors we wanted. This prevents
6376 a class of inefficient but annoying DoS attacks by hidden service
6377 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
6380 o Minor bugfixes (Linux seccomp2 sandbox):
6381 - Make transparent proxy support work along with the seccomp2
6382 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
6383 by Francisco Blas Izquierdo Riera.
6384 - Fix a memory leak in tor-resolve when running with the sandbox
6385 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
6387 o Minor bugfixes (logging):
6388 - Downgrade warnings about RSA signature failures to info log level.
6389 Emit a warning when an extra info document is found incompatible
6390 with a corresponding router descriptor. Fixes bug 9812; bugfix
6392 - Make connection_ap_handshake_attach_circuit() log the circuit ID
6393 correctly. Fixes bug 13701; bugfix on 0.0.6.
6395 o Minor bugfixes (misc):
6396 - Stop allowing invalid address patterns like "*/24" that contain
6397 both a wildcard address and a bit prefix length. This affects all
6398 our address-range parsing code. Fixes bug 7484; bugfix
6401 o Minor bugfixes (testing networks, fast startup):
6402 - Allow Tor to build circuits using a consensus with no exits. If
6403 the consensus has no exits (typical of a bootstrapping test
6404 network), allow Tor to build circuits once enough descriptors have
6405 been downloaded. This assists in bootstrapping a testing Tor
6406 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
6408 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
6409 header to directory servers. This allows us to obtain consensuses
6410 promptly when the consensus interval is very short. This assists
6411 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
6412 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
6413 - Stop assuming that private addresses are local when checking
6414 reachability in a TestingTorNetwork. Instead, when testing, assume
6415 all OR connections are remote. (This is necessary due to many test
6416 scenarios running all relays on localhost.) This assists in
6417 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
6418 0.1.0.1-rc. Patch by "teor".
6419 - Avoid building exit circuits from a consensus with no exits. Now
6420 thanks to our fix for 13718, we accept a no-exit network as not
6421 wholly lost, but we need to remember not to try to build exit
6422 circuits on it. Closes ticket 13814; patch by "teor".
6423 - Stop requiring exits to have non-zero bandwithcapacity in a
6424 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
6425 ignore exit bandwidthcapacity. This assists in bootstrapping a
6426 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
6427 on 0.2.0.3-alpha. Patch by "teor".
6428 - Add "internal" to some bootstrap statuses when no exits are
6429 available. If the consensus does not contain Exits, Tor will only
6430 build internal circuits. In this case, relevant statuses will
6431 contain the word "internal" as indicated in the Tor control-
6432 spec.txt. When bootstrap completes, Tor will be ready to build
6433 internal circuits. If a future consensus contains Exits, exit
6434 circuits may become available. Fixes part of bug 13718; bugfix on
6435 0.2.4.10-alpha. Patch by "teor".
6436 - Decrease minimum consensus interval to 10 seconds when
6437 TestingTorNetwork is set, or 5 seconds for the first consensus.
6438 Fix assumptions throughout the code that assume larger intervals.
6439 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
6441 - Avoid excluding guards from path building in minimal test
6442 networks, when we're in a test network and excluding guards would
6443 exclude all relays. This typically occurs in incredibly small tor
6444 networks, and those using "TestingAuthVoteGuard *". Fixes part of
6445 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
6447 o Code simplification and refactoring:
6448 - Stop using can_complete_circuits as a global variable; access it
6449 with a function instead.
6450 - Avoid using operators directly as macro arguments: this lets us
6451 apply coccinelle transformations to our codebase more directly.
6452 Closes ticket 13172.
6453 - Combine the functions used to parse ClientTransportPlugin and
6454 ServerTransportPlugin into a single function. Closes ticket 6456.
6455 - Add inline functions and convenience macros for inspecting channel
6456 state. Refactor the code to use convenience macros instead of
6457 checking channel state directly. Fixes issue 7356.
6458 - Document all members of was_router_added_t and rename
6459 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
6460 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
6461 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
6462 constant instead of hardcoded value. Fixes issue 13840.
6463 - Refactor our generic strmap and digestmap types into a single
6464 implementation, so that we can add a new digest256map
6468 - Document the bridge-authority-only 'networkstatus-bridges' file.
6469 Closes ticket 13713; patch from "tom".
6470 - Fix typo in PredictedPortsRelevanceTime option description in
6471 manpage. Resolves issue 13707.
6472 - Stop suggesting that users specify relays by nickname: it isn't a
6473 good idea. Also, properly cross-reference how to specify relays in
6474 all parts of manual documenting options that take a list of
6475 relays. Closes ticket 13381.
6476 - Clarify the HiddenServiceDir option description in manpage to make
6477 it clear that relative paths are taken with respect to the current
6478 working directory. Also clarify that this behavior is not
6479 guaranteed to remain indefinitely. Fixes issue 13913.
6482 - New tests for many parts of channel, relay, and circuitmux
6483 functionality. Code by Andrea; part of 9262.
6484 - New tests for parse_transport_line(). Part of ticket 6456.
6485 - In the unit tests, use chgrp() to change the group of the unit
6486 test temporary directory to the current user, so that the sticky
6487 bit doesn't interfere with tests that check directory groups.
6489 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
6493 Changes in version 0.2.6.1-alpha - 2014-10-30
6494 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
6495 includes numerous code cleanups and new tests, and fixes a large
6496 number of annoying bugs. Out-of-memory conditions are handled better
6497 than in 0.2.5, pluggable transports have improved proxy support, and
6498 clients now use optimistic data for contacting hidden services. Also,
6499 we are now more robust to changes in what we consider a parseable
6500 directory object, so that tightening restrictions does not have a risk
6501 of introducing infinite download loops.
6503 This is the first alpha release in a new series, so expect there to be
6504 bugs. Users who would rather test out a more stable branch should stay
6505 with 0.2.5.x for now.
6507 o New compiler and system requirements:
6508 - Tor 0.2.6.x requires that your compiler support more of the C99
6509 language standard than before. The 'configure' script now detects
6510 whether your compiler supports C99 mid-block declarations and
6511 designated initializers. If it does not, Tor will not compile.
6513 We may revisit this requirement if it turns out that a significant
6514 number of people need to build Tor with compilers that don't
6515 bother implementing a 15-year-old standard. Closes ticket 13233.
6516 - Tor no longer supports systems without threading support. When we
6517 began working on Tor, there were several systems that didn't have
6518 threads, or where the thread support wasn't able to run the
6519 threads of a single process on multiple CPUs. That no longer
6520 holds: every system where Tor needs to run well now has threading
6521 support. Resolves ticket 12439.
6523 o Removed platform support:
6524 - We no longer include special code to build on Windows CE; as far
6525 as we know, nobody has used Tor on Windows CE in a very long time.
6526 Closes ticket 11446.
6528 o Major features (bridges):
6529 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
6530 transports if they are configured via the "TOR_PT_PROXY"
6531 environment variable. Implements proposal 232. Resolves
6534 o Major features (client performance, hidden services):
6535 - Allow clients to use optimistic data when connecting to a hidden
6536 service, which should remove a round-trip from hidden service
6537 initialization. See proposal 181 for details. Implements
6540 o Major features (directory system):
6541 - Upon receiving an unparseable directory object, if its digest
6542 matches what we expected, then don't try to download it again.
6543 Previously, when we got a descriptor we didn't like, we would keep
6544 trying to download it over and over. Closes ticket 11243.
6546 o Major features (sample torrc):
6547 - Add a new, infrequently-changed "torrc.minimal". This file is
6548 similar to torrc.sample, but it will change as infrequently as
6549 possible, for the benefit of users whose systems prompt them for
6550 intervention whenever a default configuration file is changed.
6551 Making this change allows us to update torrc.sample to be a more
6552 generally useful "sample torrc".
6554 o Major bugfixes (directory authorities):
6555 - Do not assign the HSDir flag to relays if they are not Valid, or
6556 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
6558 o Major bugfixes (directory bandwidth performance):
6559 - Don't flush the zlib buffer aggressively when compressing
6560 directory information for clients. This should save about 7% of
6561 the bandwidth currently used for compressed descriptors and
6562 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
6564 o Minor features (security, memory wiping):
6565 - Ensure we securely wipe keys from memory after
6566 crypto_digest_get_digest and init_curve25519_keypair_from_file
6567 have finished using them. Resolves ticket 13477.
6569 o Minor features (security, out-of-memory handling):
6570 - When handling an out-of-memory condition, allocate less memory for
6571 temporary data structures. Fixes issue 10115.
6572 - When handling an out-of-memory condition, consider more types of
6573 buffers, including those on directory connections, and zlib
6574 buffers. Resolves ticket 11792.
6577 - When identity keypair is generated for first time, log a
6578 congratulatory message that links to the new relay lifecycle
6579 document. Implements feature 10427.
6581 o Minor features (client):
6582 - Clients are now willing to send optimistic data (before they
6583 receive a 'connected' cell) to relays of any version. (Relays
6584 without support for optimistic data are no longer supported on the
6585 Tor network.) Resolves ticket 13153.
6587 o Minor features (directory authorities):
6588 - Don't list relays with a bandwidth estimate of 0 in the consensus.
6589 Implements a feature proposed during discussion of bug 13000.
6590 - In tor-gencert, report an error if the user provides the same
6591 argument more than once.
6592 - If a directory authority can't find a best consensus method in the
6593 votes that it holds, it now falls back to its favorite consensus
6594 method. Previously, it fell back to method 1. Neither of these is
6595 likely to get enough signatures, but "fall back to favorite"
6596 doesn't require us to maintain support an obsolete consensus
6597 method. Implements part of proposal 215.
6599 o Minor features (logging):
6600 - On Unix-like systems, you can now use named pipes as the target of
6601 the Log option, and other options that try to append to files.
6602 Closes ticket 12061. Patch from "carlo von lynX".
6603 - When opening a log file at startup, send it every log message that
6604 we generated between startup and opening it. Previously, log
6605 messages that were generated before opening the log file were only
6606 logged to stdout. Closes ticket 6938.
6607 - Add a TruncateLogFile option to overwrite logs instead of
6608 appending to them. Closes ticket 5583.
6610 o Minor features (portability, Solaris):
6611 - Threads are no longer disabled by default on Solaris; we believe
6612 that the versions of Solaris with broken threading support are all
6613 obsolete by now. Resolves ticket 9495.
6615 o Minor features (relay):
6616 - Re-check our address after we detect a changed IP address from
6617 getsockname(). This ensures that the controller command "GETINFO
6618 address" will report the correct value. Resolves ticket 11582.
6620 - A new AccountingRule option lets Relays set whether they'd like
6621 AccountingMax to be applied separately to inbound and outbound
6622 traffic, or applied to the sum of inbound and outbound traffic.
6623 Resolves ticket 961. Patch by "chobe".
6625 o Minor features (testing networks):
6626 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
6627 the "Exit" flag regardless of their uptime, bandwidth, or exit
6628 policy. TestingTorNetwork must be set for this option to have any
6629 effect. Previously, authorities would take up to 35 minutes to
6630 give nodes the Exit flag in a test network. Partially implements
6633 o Minor features (validation):
6634 - Check all date/time values passed to tor_timegm and
6635 parse_rfc1123_time for validity, taking leap years into account.
6636 Improves HTTP header validation. Implemented with bug 13476.
6637 - In correct_tm(), limit the range of values returned by system
6638 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
6639 This means we don't have to deal with negative or too large dates,
6640 even if a clock is wrong. Otherwise we might fail to read a file
6641 written by us which includes such a date. Fixes bug 13476.
6643 o Minor bugfixes (bridge clients):
6644 - When configured to use a bridge without an identity digest (not
6645 recommended), avoid launching an extra channel to it when
6646 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
6648 o Minor bugfixes (bridges):
6649 - When DisableNetwork is set, do not launch pluggable transport
6650 plugins, and if any are running, terminate them. Fixes bug 13213;
6651 bugfix on 0.2.3.6-alpha.
6653 o Minor bugfixes (C correctness):
6654 - Fix several instances of possible integer overflow/underflow/NaN.
6655 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
6657 - In circuit_build_times_calculate_timeout() in circuitstats.c,
6658 avoid dividing by zero in the pareto calculations. This traps
6659 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
6661 - Fix an integer overflow in format_time_interval(). Fixes bug
6662 13393; bugfix on 0.2.0.10-alpha.
6663 - Set the correct day of year value when the system's localtime(_r)
6664 or gmtime(_r) functions fail to set struct tm. Not externally
6665 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
6666 - Avoid unlikely signed integer overflow in tor_timegm on systems
6667 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
6669 o Minor bugfixes (client):
6670 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
6671 BadExit flag are not considered worthy candidates. Fixes bug
6672 13066; bugfix on 0.1.2.3-alpha.
6673 - Use the consensus schedule for downloading consensuses, and not
6674 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
6675 - Handle unsupported or malformed SOCKS5 requests properly by
6676 responding with the appropriate error message before closing the
6677 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
6679 o Minor bugfixes (client, torrc):
6680 - Stop modifying the value of our DirReqStatistics torrc option just
6681 because we're not a bridge or relay. This bug was causing Tor
6682 Browser users to write "DirReqStatistics 0" in their torrc files
6683 as if they had chosen to change the config. Fixes bug 4244; bugfix
6685 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
6686 that our options have changed every time we SIGHUP. Fixes bug
6687 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
6689 o Minor bugfixes (controller):
6690 - Return an error when the second or later arguments of the
6691 "setevents" controller command are invalid events. Previously we
6692 would return success while silently skipping invalid events. Fixes
6693 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
6695 o Minor bugfixes (directory system):
6696 - Always believe that v3 directory authorities serve extra-info
6697 documents, whether they advertise "caches-extra-info" or not.
6698 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
6699 - When running as a v3 directory authority, advertise that you serve
6700 extra-info documents so that clients who want them can find them
6701 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
6702 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
6703 Previously, directories offering BRIDGE_DIRINFO and some other
6704 flag (i.e. microdescriptors or extrainfo) would be ignored when
6705 looking for bridges. Partially fixes bug 13163; bugfix
6708 o Minor bugfixes (networking):
6709 - Check for orconns and use connection_or_close_for_error() rather
6710 than connection_mark_for_close() directly in the getsockopt()
6711 failure case of connection_handle_write_impl(). Fixes bug 11302;
6712 bugfix on 0.2.4.4-alpha.
6714 o Minor bugfixes (relay):
6715 - When generating our family list, remove spaces from around the
6716 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
6717 - If our previous bandwidth estimate was 0 bytes, allow publishing a
6718 new relay descriptor immediately. Fixes bug 13000; bugfix
6721 o Minor bugfixes (testing networks):
6722 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
6723 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
6724 - Stop using the default authorities in networks which provide both
6725 AlternateDirAuthority and AlternateBridgeAuthority. Partially
6726 fixes bug 13163; bugfix on 0.2.0.13-alpha.
6728 o Minor bugfixes (testing):
6729 - Stop spawn test failures due to a race condition between the
6730 SIGCHLD handler updating the process status, and the test reading
6731 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
6733 o Minor bugfixes (testing, Windows):
6734 - Avoid passing an extra backslash when creating a temporary
6735 directory for running the unit tests on Windows. Fixes bug 12392;
6736 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
6738 o Minor bugfixes (windows):
6739 - Remove code to special-case handling of NTE_BAD_KEYSET when
6740 acquiring windows CryptoAPI context. This error can't actually
6741 occur for the parameters we're providing. Fixes bug 10816; bugfix
6744 o Minor bugfixes (zlib):
6745 - Avoid truncating a zlib stream when trying to finalize it with an
6746 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
6749 - Allow our configure script to build correctly with autoconf 2.62
6750 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
6751 - Improve the error message from ./configure to make it clear that
6752 when asciidoc has not been found, the user will have to either add
6753 --disable-asciidoc argument or install asciidoc. Resolves
6756 o Code simplification and refactoring:
6757 - Change the entry_is_live() function to take named bitfield
6758 elements instead of an unnamed list of booleans. Closes
6760 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
6761 Resolves ticket 12205.
6762 - Use calloc and reallocarray functions instead of multiply-
6763 then-malloc. This makes it less likely for us to fall victim to an
6764 integer overflow attack when allocating. Resolves ticket 12855.
6765 - Use the standard macro name SIZE_MAX, instead of our
6767 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
6768 functions which take them as arguments. Replace 0 with NO_DIRINFO
6769 in a function call for clarity. Seeks to prevent future issues
6771 - Avoid 4 null pointer errors under clang static analysis by using
6772 tor_assert() to prove that the pointers aren't null. Fixes
6774 - Rework the API of policies_parse_exit_policy() to use a bitmask to
6775 represent parsing options, instead of a confusing mess of
6776 booleans. Resolves ticket 8197.
6777 - Introduce a helper function to parse ExitPolicy in
6778 or_options_t structure.
6781 - Add a doc/TUNING document with tips for handling large numbers of
6782 TCP connections when running busy Tor relay. Update the warning
6783 message to point to this file when running out of sockets
6784 operating system is allowing to use simultaneously. Resolves
6788 - We no longer remind the user about configuration options that have
6789 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
6790 - Remove our old, non-weighted bandwidth-based node selection code.
6791 Previously, we used it as a fallback when we couldn't perform
6792 weighted bandwidth-based node selection. But that would only
6793 happen in the cases where we had no consensus, or when we had a
6794 consensus generated by buggy or ancient directory authorities. In
6795 either case, it's better to use the more modern, better maintained
6796 algorithm, with reasonable defaults for the weights. Closes
6798 - Remove the --disable-curve25519 configure option. Relays and
6799 clients now are required to support curve25519 and the
6801 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
6802 used to be deprecated synonyms for "StrictNodes", are now marked
6803 obsolete. Resolves ticket 12226.
6804 - Clients don't understand the BadDirectory flag in the consensus
6805 anymore, and ignore it.
6808 - Refactor the function that chooses guard nodes so that it can more
6809 easily be tested; write some tests for it.
6810 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
6811 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
6812 - Create unit tests for format_time_interval(). With bug 13393.
6813 - Add unit tests for tor_timegm signed overflow, tor_timegm and
6814 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
6815 tests (visible) fixes in bug 13476.
6816 - Add a "coverage-html" make target to generate HTML-visualized
6817 coverage results when building with --enable-coverage. (Requires
6818 lcov.) Patch from Kevin Murray.
6819 - Enable the backtrace handler (where supported) when running the
6821 - Revise all unit tests that used the legacy test_* macros to
6822 instead use the recommended tt_* macros. This patch was generated
6823 with coccinelle, to avoid manual errors. Closes ticket 13119.
6825 o Distribution (systemd):
6826 - systemd unit file: only allow tor to write to /var/lib/tor and
6827 /var/log/tor. The rest of the filesystem is accessible for reading
6828 only. Patch by intrigeri; resolves ticket 12751.
6829 - systemd unit file: ensure that the process and all its children
6830 can never gain new privileges. Patch by intrigeri; resolves
6832 - systemd unit file: set up /var/run/tor as writable for the Tor
6833 service. Patch by intrigeri; resolves ticket 13196.
6835 o Removed features (directory authorities):
6836 - Remove code that prevented authorities from listing Tor relays
6837 affected by CVE-2011-2769 as guards. These relays are already
6838 rejected altogether due to the minimum version requirement of
6839 0.2.3.16-alpha. Closes ticket 13152.
6840 - The "AuthDirRejectUnlisted" option no longer has any effect, as
6841 the fingerprints file (approved-routers) has been deprecated.
6842 - Directory authorities do not support being Naming dirauths anymore.
6843 The "NamingAuthoritativeDir" config option is now obsolete.
6844 - Directory authorities do not support giving out the BadDirectory
6846 - Directory authorities no longer advertise or support consensus
6847 methods 1 through 12 inclusive. These consensus methods were
6848 obsolete and/or insecure: maintaining the ability to support them
6849 served no good purpose. Implements part of proposal 215; closes
6852 o Testing (test-network.sh):
6853 - Stop using "echo -n", as some shells' built-in echo doesn't
6854 support "-n". Instead, use "/bin/echo -n". Partially fixes
6856 - Stop an apparent test-network hang when used with make -j2. Fixes
6858 - Add a --delay option to test-network.sh, which configures the
6859 delay before the chutney network tests for data transmission.
6860 Partially implements ticket 13161.
6863 Changes in version 0.2.5.10 - 2014-10-24
6864 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
6866 It adds several new security features, including improved
6867 denial-of-service resistance for relays, new compiler hardening
6868 options, and a system-call sandbox for hardened installations on Linux
6869 (requires seccomp2). The controller protocol has several new features,
6870 resolving IPv6 addresses should work better than before, and relays
6871 should be a little more CPU-efficient. We've added support for more
6872 OpenBSD and FreeBSD transparent proxy types. We've improved the build
6873 system and testing infrastructure to allow unit testing of more parts
6874 of the Tor codebase. Finally, we've addressed several nagging pluggable
6875 transport usability issues, and included numerous other small bugfixes
6876 and features mentioned below.
6878 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
6879 have accumulated many known flaws; everyone should upgrade.
6881 o Deprecated versions:
6882 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
6883 attention for some while.
6886 Changes in version 0.2.5.9-rc - 2014-10-20
6887 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
6888 series. It disables SSL3 in response to the recent "POODLE" attack
6889 (even though POODLE does not affect Tor). It also works around a crash
6890 bug caused by some operating systems' response to the "POODLE" attack
6891 (which does affect Tor). It also contains a few miscellaneous fixes.
6893 o Major security fixes:
6894 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
6895 today support TLS 1.0 or later, so we can safely turn off support
6896 for this old (and insecure) protocol. Fixes bug 13426.
6898 o Major bugfixes (openssl bug workaround):
6899 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
6900 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
6901 13471. This is a workaround for an OpenSSL bug.
6904 - Disable the sandbox name resolver cache when running tor-resolve:
6905 tor-resolve doesn't use the sandbox code, and turning it on was
6906 breaking attempts to do tor-resolve on a non-default server on
6907 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
6909 o Compilation fixes:
6910 - Build and run correctly on systems like OpenBSD-current that have
6911 patched OpenSSL to remove get_cipher_by_char and/or its
6912 implementations. Fixes issue 13325.
6914 o Downgraded warnings:
6915 - Downgrade the severity of the 'unexpected sendme cell from client'
6916 from 'warn' to 'protocol warning'. Closes ticket 8093.
6919 Changes in version 0.2.4.25 - 2014-10-20
6920 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
6921 (even though POODLE does not affect Tor). It also works around a crash
6922 bug caused by some operating systems' response to the "POODLE" attack
6923 (which does affect Tor).
6925 o Major security fixes (also in 0.2.5.9-rc):
6926 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
6927 today support TLS 1.0 or later, so we can safely turn off support
6928 for this old (and insecure) protocol. Fixes bug 13426.
6930 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
6931 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
6932 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
6933 13471. This is a workaround for an OpenSSL bug.
6936 Changes in version 0.2.5.8-rc - 2014-09-22
6937 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
6938 series. It fixes a bug that affects consistency and speed when
6939 connecting to hidden services, and it updates the location of one of
6940 the directory authorities.
6943 - Clients now send the correct address for their chosen rendezvous
6944 point when trying to access a hidden service. They used to send
6945 the wrong address, which would still work some of the time because
6946 they also sent the identity digest of the rendezvous point, and if
6947 the hidden service happened to try connecting to the rendezvous
6948 point from a relay that already had a connection open to it,
6949 the relay would reuse that connection. Now connections to hidden
6950 services should be more robust and faster. Also, this bug meant
6951 that clients were leaking to the hidden service whether they were
6952 on a little-endian (common) or big-endian (rare) system, which for
6953 some users might have reduced their anonymity. Fixes bug 13151;
6954 bugfix on 0.2.1.5-alpha.
6956 o Directory authority changes:
6957 - Change IP address for gabelmoo (v3 directory authority).
6960 Changes in version 0.2.4.24 - 2014-09-22
6961 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
6962 connecting to hidden services, and it updates the location of one of
6963 the directory authorities.
6966 - Clients now send the correct address for their chosen rendezvous
6967 point when trying to access a hidden service. They used to send
6968 the wrong address, which would still work some of the time because
6969 they also sent the identity digest of the rendezvous point, and if
6970 the hidden service happened to try connecting to the rendezvous
6971 point from a relay that already had a connection open to it,
6972 the relay would reuse that connection. Now connections to hidden
6973 services should be more robust and faster. Also, this bug meant
6974 that clients were leaking to the hidden service whether they were
6975 on a little-endian (common) or big-endian (rare) system, which for
6976 some users might have reduced their anonymity. Fixes bug 13151;
6977 bugfix on 0.2.1.5-alpha.
6979 o Directory authority changes:
6980 - Change IP address for gabelmoo (v3 directory authority).
6982 o Minor features (geoip):
6983 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
6987 Changes in version 0.2.5.7-rc - 2014-09-11
6988 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
6989 release series, and some long-standing bugs related to ORPort reachability
6990 testing and failure to send CREATE cells. It is the first release
6991 candidate for the Tor 0.2.5.x series.
6993 o Major bugfixes (client, startup):
6994 - Start making circuits as soon as DisabledNetwork is turned off.
6995 When Tor started with DisabledNetwork set, it would correctly
6996 conclude that it shouldn't build circuits, but it would mistakenly
6997 cache this conclusion, and continue believing it even when
6998 DisableNetwork is set to 0. Fixes the bug introduced by the fix
6999 for bug 11200; bugfix on 0.2.5.4-alpha.
7000 - Resume expanding abbreviations for command-line options. The fix
7001 for bug 4647 accidentally removed our hack from bug 586 that
7002 rewrote HashedControlPassword to __HashedControlSessionPassword
7003 when it appears on the commandline (which allowed the user to set
7004 her own HashedControlPassword in the torrc file while the
7005 controller generates a fresh session password for each run). Fixes
7006 bug 12948; bugfix on 0.2.5.1-alpha.
7007 - Warn about attempts to run hidden services and relays in the same
7008 process: that's probably not a good idea. Closes ticket 12908.
7010 o Major bugfixes (relay):
7011 - Avoid queuing or sending destroy cells for circuit ID zero when we
7012 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
7013 Found and fixed by "cypherpunks".
7014 - Fix ORPort reachability detection on relays running behind a
7015 proxy, by correctly updating the "local" mark on the controlling
7016 channel when changing the address of an or_connection_t after the
7017 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
7019 o Minor features (bridge):
7020 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
7021 cookie file for the ExtORPort g+r by default.
7023 o Minor features (geoip):
7024 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
7027 o Minor bugfixes (logging):
7028 - Reduce the log severity of the "Pluggable transport proxy does not
7029 provide any needed transports and will not be launched." message,
7030 since Tor Browser includes several ClientTransportPlugin lines in
7031 its torrc-defaults file, leading every Tor Browser user who looks
7032 at her logs to see these notices and wonder if they're dangerous.
7033 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
7034 - Downgrade "Unexpected onionskin length after decryption" warning
7035 to a protocol-warn, since there's nothing relay operators can do
7036 about a client that sends them a malformed create cell. Resolves
7037 bug 12996; bugfix on 0.0.6rc1.
7038 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
7039 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
7040 - When logging information about an EXTEND2 or EXTENDED2 cell, log
7041 their names correctly. Fixes part of bug 12700; bugfix
7043 - When logging information about a relay cell whose command we don't
7044 recognize, log its command as an integer. Fixes part of bug 12700;
7045 bugfix on 0.2.1.10-alpha.
7046 - Escape all strings from the directory connection before logging
7047 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
7049 o Minor bugfixes (controller):
7050 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
7051 bug 12864; bugfix on 0.2.5.1-alpha.
7052 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
7053 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
7056 o Minor bugfixes (compilation):
7057 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
7058 bugfix on 0.2.5.5-alpha.
7059 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
7060 0.2.5.1-alpha. Patch from "NewEraCracker".
7061 - In routerlist_assert_ok(), don't take the address of a
7062 routerinfo's cache_info member unless that routerinfo is non-NULL.
7063 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
7064 - Fix a large number of false positive warnings from the clang
7065 analyzer static analysis tool. This should make real warnings
7066 easier for clang analyzer to find. Patch from "teor". Closes
7069 o Distribution (systemd):
7070 - Verify configuration file via ExecStartPre in the systemd unit
7071 file. Patch from intrigeri; resolves ticket 12730.
7072 - Explicitly disable RunAsDaemon in the systemd unit file. Our
7073 current systemd unit uses "Type = simple", so systemd does not
7074 expect tor to fork. If the user has "RunAsDaemon 1" in their
7075 torrc, then things won't work as expected. This is e.g. the case
7076 on Debian (and derivatives), since there we pass "--defaults-torrc
7077 /usr/share/tor/tor-service-defaults-torrc" (that contains
7078 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
7082 - Adjust the URLs in the README to refer to the new locations of
7083 several documents on the website. Fixes bug 12830. Patch from
7085 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
7089 Changes in version 0.2.5.6-alpha - 2014-07-28
7090 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
7091 risk from guard rotation, and fixes a variety of other issues to get
7092 us closer to a release candidate.
7094 o Major features (also in 0.2.4.23):
7095 - Make the number of entry guards configurable via a new
7096 NumEntryGuards consensus parameter, and the number of directory
7097 guards configurable via a new NumDirectoryGuards consensus
7098 parameter. Implements ticket 12688.
7100 o Major bugfixes (also in 0.2.4.23):
7101 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
7102 implementation that caused incorrect results on 32-bit
7103 implementations when certain malformed inputs were used along with
7104 a small class of private ntor keys. This bug does not currently
7105 appear to allow an attacker to learn private keys or impersonate a
7106 Tor server, but it could provide a means to distinguish 32-bit Tor
7107 implementations from 64-bit Tor implementations. Fixes bug 12694;
7108 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
7112 - Perform circuit cleanup operations even when circuit
7113 construction operations are disabled (because the network is
7114 disabled, or because there isn't enough directory information).
7115 Previously, when we were not building predictive circuits, we
7116 were not closing expired circuits either. Fixes bug 8387; bugfix on
7117 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
7118 became more strict about when we have "enough directory information
7122 - Authorities now assign the Guard flag to the fastest 25% of the
7123 network (it used to be the fastest 50%). Also raise the consensus
7124 weight that guarantees the Guard flag from 250 to 2000. For the
7125 current network, this results in about 1100 guards, down from 2500.
7126 This step paves the way for moving the number of entry guards
7127 down to 1 (proposal 236) while still providing reasonable expected
7128 performance for most users. Implements ticket 12690.
7129 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
7131 - Slightly enhance the diagnostic message for bug 12184.
7133 o Minor bugfixes (also in 0.2.4.23):
7134 - Warn and drop the circuit if we receive an inbound 'relay early'
7135 cell. Those used to be normal to receive on hidden service circuits
7136 due to bug 1038, but the buggy Tor versions are long gone from
7137 the network so we can afford to resume watching for them. Resolves
7138 the rest of bug 1038; bugfix on 0.2.1.19.
7139 - Correct a confusing error message when trying to extend a circuit
7140 via the control protocol but we don't know a descriptor or
7141 microdescriptor for one of the specified relays. Fixes bug 12718;
7142 bugfix on 0.2.3.1-alpha.
7145 - Fix compilation when building with bufferevents enabled. (This
7146 configuration is still not expected to work, however.)
7147 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
7148 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
7150 - Compile correctly with builds and forks of OpenSSL (such as
7151 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
7152 0.2.1.1-alpha. Patch from "dhill".
7155 Changes in version 0.2.4.23 - 2014-07-28
7156 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
7157 guard rotation, and also backports several important fixes from the
7158 Tor 0.2.5 alpha release series.
7161 - Clients now look at the "usecreatefast" consensus parameter to
7162 decide whether to use CREATE_FAST or CREATE cells for the first hop
7163 of their circuit. This approach can improve security on connections
7164 where Tor's circuit handshake is stronger than the available TLS
7165 connection security levels, but the tradeoff is more computational
7166 load on guard relays. Implements proposal 221. Resolves ticket 9386.
7167 - Make the number of entry guards configurable via a new
7168 NumEntryGuards consensus parameter, and the number of directory
7169 guards configurable via a new NumDirectoryGuards consensus
7170 parameter. Implements ticket 12688.
7173 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
7174 implementation that caused incorrect results on 32-bit
7175 implementations when certain malformed inputs were used along with
7176 a small class of private ntor keys. This bug does not currently
7177 appear to allow an attacker to learn private keys or impersonate a
7178 Tor server, but it could provide a means to distinguish 32-bit Tor
7179 implementations from 64-bit Tor implementations. Fixes bug 12694;
7180 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
7184 - Warn and drop the circuit if we receive an inbound 'relay early'
7185 cell. Those used to be normal to receive on hidden service circuits
7186 due to bug 1038, but the buggy Tor versions are long gone from
7187 the network so we can afford to resume watching for them. Resolves
7188 the rest of bug 1038; bugfix on 0.2.1.19.
7189 - Correct a confusing error message when trying to extend a circuit
7190 via the control protocol but we don't know a descriptor or
7191 microdescriptor for one of the specified relays. Fixes bug 12718;
7192 bugfix on 0.2.3.1-alpha.
7193 - Avoid an illegal read from stack when initializing the TLS
7194 module using a version of OpenSSL without all of the ciphers
7195 used by the v2 link handshake. Fixes bug 12227; bugfix on
7196 0.2.4.8-alpha. Found by "starlight".
7199 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
7203 Changes in version 0.2.5.5-alpha - 2014-06-18
7204 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
7205 0.2.5.x release series, including a couple of DoS issues, some
7206 performance regressions, a large number of bugs affecting the Linux
7207 seccomp2 sandbox code, and various other bugfixes. It also adds
7208 diagnostic bugfixes for a few tricky issues that we're trying to
7211 o Major features (security, traffic analysis resistance):
7212 - Several major improvements to the algorithm used to decide when to
7213 close TLS connections. Previous versions of Tor closed connections
7214 at a fixed interval after the last time a non-padding cell was
7215 sent over the connection, regardless of the target of the
7216 connection. Now, we randomize the intervals by adding up to 50% of
7217 their base value, we measure the length of time since connection
7218 last had at least one circuit, and we allow connections to known
7219 ORs to remain open a little longer (15 minutes instead of 3
7220 minutes minimum). These changes should improve Tor's resistance
7221 against some kinds of traffic analysis, and lower some overhead
7222 from needlessly closed connections. Fixes ticket 6799.
7223 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
7225 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
7226 - Fix a memory leak that could occur if a microdescriptor parse
7227 fails during the tokenizing step. This bug could enable a memory
7228 exhaustion attack by directory servers. Fixes bug 11649; bugfix
7231 o Major bugfixes (security, directory authorities):
7232 - Directory authorities now include a digest of each relay's
7233 identity key as a part of its microdescriptor.
7235 This is a workaround for bug 11743 (reported by "cypherpunks"),
7236 where Tor clients do not support receiving multiple
7237 microdescriptors with the same SHA256 digest in the same
7238 consensus. When clients receive a consensus like this, they only
7239 use one of the relays. Without this fix, a hostile relay could
7240 selectively disable some client use of target relays by
7241 constructing a router descriptor with a different identity and the
7242 same microdescriptor parameters and getting the authorities to
7243 list it in a microdescriptor consensus. This fix prevents an
7244 attacker from causing a microdescriptor collision, because the
7245 router's identity is not forgeable.
7247 o Major bugfixes (relay):
7248 - Use a direct dirport connection when uploading non-anonymous
7249 descriptors to the directory authorities. Previously, relays would
7250 incorrectly use tunnel connections under a fairly wide variety of
7251 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
7252 - When a circuit accidentally has the same circuit ID for its
7253 forward and reverse direction, correctly detect the direction of
7254 cells using that circuit. Previously, this bug made roughly one
7255 circuit in a million non-functional. Fixes bug 12195; this is a
7256 bugfix on every version of Tor.
7258 o Major bugfixes (client, pluggable transports):
7259 - When managing pluggable transports, use OS notification facilities
7260 to learn if they have crashed, and don't attempt to kill any
7261 process that has already exited. Fixes bug 8746; bugfix
7264 o Minor features (diagnostic):
7265 - When logging a warning because of bug 7164, additionally check the
7266 hash table for consistency (as proposed on ticket 11737). This may
7267 help diagnose bug 7164.
7268 - When we log a heartbeat, log how many one-hop circuits we have
7269 that are at least 30 minutes old, and log status information about
7270 a few of them. This is an attempt to track down bug 8387.
7271 - When encountering an unexpected CR while writing text to a file on
7272 Windows, log the name of the file. Should help diagnosing
7274 - Give more specific warnings when a client notices that an onion
7275 handshake has failed. Fixes ticket 9635.
7276 - Add significant new logging code to attempt to diagnose bug 12184,
7277 where relays seem to run out of available circuit IDs.
7278 - Improve the diagnostic log message for bug 8387 even further to
7279 try to improve our odds of figuring out why one-hop directory
7280 circuits sometimes do not get closed.
7282 o Minor features (security, memory management):
7283 - Memory allocation tricks (mempools and buffer freelists) are now
7284 disabled by default. You can turn them back on with
7285 --enable-mempools and --enable-buf-freelists respectively. We're
7286 disabling these features because malloc performance is good enough
7287 on most platforms, and a similar feature in OpenSSL exacerbated
7288 exploitation of the Heartbleed attack. Resolves ticket 11476.
7290 o Minor features (security):
7291 - Apply the secure SipHash-2-4 function to the hash table mapping
7292 circuit IDs and channels to circuits. We missed this one when we
7293 were converting all the other hash functions to use SipHash back
7294 in 0.2.5.3-alpha. Resolves ticket 11750.
7296 o Minor features (build):
7297 - The configure script has a --disable-seccomp option to turn off
7298 support for libseccomp on systems that have it, in case it (or
7299 Tor's use of it) is broken. Resolves ticket 11628.
7301 o Minor features (other):
7302 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
7305 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
7306 - When running a hidden service, do not allow TunneledDirConns 0;
7307 this will keep the hidden service from running, and also
7308 make it publish its descriptors directly over HTTP. Fixes bug 10849;
7309 bugfix on 0.2.1.1-alpha.
7311 o Minor bugfixes (performance):
7312 - Avoid a bug where every successful connection made us recompute
7313 the flag telling us whether we have sufficient information to
7314 build circuits. Previously, we would forget our cached value
7315 whenever we successfully opened a channel (or marked a router as
7316 running or not running for any other reason), regardless of
7317 whether we had previously believed the router to be running. This
7318 forced us to run an expensive update operation far too often.
7319 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
7320 - Avoid using tor_memeq() for checking relay cell integrity. This
7321 removes a possible performance bottleneck. Fixes part of bug
7322 12169; bugfix on 0.2.1.31.
7324 o Minor bugfixes (compilation):
7325 - Fix compilation of test_status.c when building with MVSC. Bugfix
7326 on 0.2.5.4-alpha. Patch from Gisle Vanem.
7327 - Resolve GCC complaints on OpenBSD about discarding constness in
7328 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
7329 on 0.1.1.23. Patch from Dana Koch.
7330 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
7331 treatment of long and time_t as comparable types. Fixes part of
7332 bug 11633. Patch from Dana Koch.
7333 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
7334 11623; bugfix on 0.2.5.3-alpha.
7335 - When deciding whether to build the 64-bit curve25519
7336 implementation, detect platforms where we can compile 128-bit
7337 arithmetic but cannot link it. Fixes bug 11729; bugfix on
7338 0.2.4.8-alpha. Patch from "conradev".
7339 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
7340 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
7341 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
7344 o Minor bugfixes (Directory server):
7345 - When sending a compressed set of descriptors or microdescriptors,
7346 make sure to finalize the zlib stream. Previously, we would write
7347 all the compressed data, but if the last descriptor we wanted to
7348 send was missing or too old, we would not mark the stream as
7349 finished. This caused problems for decompression tools. Fixes bug
7350 11648; bugfix on 0.1.1.23.
7352 o Minor bugfixes (Linux seccomp sandbox):
7353 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
7354 11622; bugfix on 0.2.5.1-alpha.
7355 - Avoid crashing when re-opening listener ports with the seccomp
7356 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
7357 - Avoid crashing with the seccomp sandbox enabled along with
7358 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
7359 - When we receive a SIGHUP with the sandbox enabled, correctly
7360 support rotating our log files. Fixes bug 12032; bugfix
7362 - Avoid crash when running with sandboxing enabled and
7363 DirReqStatistics not disabled. Fixes bug 12035; bugfix
7365 - Fix a "BUG" warning when trying to write bridge-stats files with
7366 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
7368 - Prevent the sandbox from crashing on startup when run with the
7369 --enable-expensive-hardening configuration option. Fixes bug
7370 11477; bugfix on 0.2.5.4-alpha.
7371 - When running with DirPortFrontPage and sandboxing both enabled,
7372 reload the DirPortFrontPage correctly when restarting. Fixes bug
7373 12028; bugfix on 0.2.5.1-alpha.
7374 - Don't try to enable the sandbox when using the Tor binary to check
7375 its configuration, hash a passphrase, or so on. Doing so was
7376 crashing on startup for some users. Fixes bug 11609; bugfix
7378 - Avoid warnings when running with sandboxing and node statistics
7379 enabled at the same time. Fixes part of 12064; bugfix on
7380 0.2.5.1-alpha. Patch from Michael Wolf.
7381 - Avoid warnings when running with sandboxing enabled at the same
7382 time as cookie authentication, hidden services, or directory
7383 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
7384 - Do not allow options that require calls to exec to be enabled
7385 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
7386 bug 12043; bugfix on 0.2.5.1-alpha.
7387 - Handle failures in getpwnam()/getpwuid() when running with the
7388 User option set and the Linux syscall sandbox enabled. Fixes bug
7389 11946; bugfix on 0.2.5.1-alpha.
7390 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
7391 to avoid calling getaddrinfo() after installing the sandbox
7392 filters. Previously, it preloaded a cache with the IPv4 address
7393 for our hostname, and nothing else. Now, it loads the cache with
7394 every address that it used to initialize the Tor process. Fixes
7395 bug 11970; bugfix on 0.2.5.1-alpha.
7397 o Minor bugfixes (pluggable transports):
7398 - Enable the ExtORPortCookieAuthFile option, to allow changing the
7399 default location of the authentication token for the extended OR
7400 Port as used by sever-side pluggable transports. We had
7401 implemented this option before, but the code to make it settable
7402 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
7403 - Avoid another 60-second delay when starting Tor in a pluggable-
7404 transport-using configuration when we already have cached
7405 descriptors for our bridges. Fixes bug 11965; bugfix
7408 o Minor bugfixes (client):
7409 - Avoid "Tried to open a socket with DisableNetwork set" warnings
7410 when starting a client with bridges configured and DisableNetwork
7411 set. (Tor launcher starts Tor with DisableNetwork set the first
7412 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
7414 o Minor bugfixes (testing):
7415 - The Python parts of the test scripts now work on Python 3 as well
7416 as Python 2, so systems where '/usr/bin/python' is Python 3 will
7417 no longer have the tests break. Fixes bug 11608; bugfix
7419 - When looking for versions of python that we could run the tests
7420 with, check for "python2.7" and "python3.3"; previously we were
7421 only looking for "python", "python2", and "python3". Patch from
7422 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
7423 - Fix all valgrind warnings produced by the unit tests. There were
7424 over a thousand memory leak warnings previously, mostly produced
7425 by forgetting to free things in the unit test code. Fixes bug
7426 11618, bugfixes on many versions of Tor.
7428 o Minor bugfixes (tor-fw-helper):
7429 - Give a correct log message when tor-fw-helper fails to launch.
7430 (Previously, we would say something like "tor-fw-helper sent us a
7431 string we could not parse".) Fixes bug 9781; bugfix
7434 o Minor bugfixes (relay, threading):
7435 - Check return code on spawn_func() in cpuworker code, so that we
7436 don't think we've spawned a nonworking cpuworker and write junk to
7437 it forever. Fix related to bug 4345; bugfix on all released Tor
7438 versions. Found by "skruffy".
7439 - Use a pthread_attr to make sure that spawn_func() cannot return an
7440 error while at the same time launching a thread. Fix related to
7441 bug 4345; bugfix on all released Tor versions. Reported
7444 o Minor bugfixes (relay, oom prevention):
7445 - Correctly detect the total available system memory. We tried to do
7446 this in 0.2.5.4-alpha, but the code was set up to always return an
7447 error value, even on success. Fixes bug 11805; bugfix
7450 o Minor bugfixes (relay, other):
7451 - We now drop CREATE cells for already-existent circuit IDs and for
7452 zero-valued circuit IDs, regardless of other factors that might
7453 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
7455 - Avoid an illegal read from stack when initializing the TLS module
7456 using a version of OpenSSL without all of the ciphers used by the
7457 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
7459 - When rejecting DATA cells for stream_id zero, still count them
7460 against the circuit's deliver window so that we don't fail to send
7461 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
7463 o Minor bugfixes (logging):
7464 - Fix a misformatted log message about delayed directory fetches.
7465 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
7466 - Squelch a spurious LD_BUG message "No origin circuit for
7467 successful SOCKS stream" in certain hidden service failure cases;
7471 - Include a tor.service file in contrib/dist for use with systemd.
7472 Some distributions will be able to use this file unmodified;
7473 others will need to tweak it, or write their own. Patch from Jamie
7474 Nguyen; resolves ticket 8368.
7477 - Clean up several option names in the manpage to match their real
7478 names, add the missing documentation for a couple of testing and
7479 directory authority options, remove the documentation for a
7480 V2-directory fetching option that no longer exists. Resolves
7482 - Correct the documenation so that it lists the correct directory
7483 for the stats files. (They are in a subdirectory called "stats",
7485 - In the manpage, move more authority-only options into the
7486 directory authority section so that operators of regular directory
7487 caches don't get confused.
7490 - The contrib directory has been sorted and tidied. Before, it was
7491 an unsorted dumping ground for useful and not-so-useful things.
7492 Now, it is divided based on functionality, and the items which
7493 seemed to be nonfunctional or useless have been removed. Resolves
7494 ticket 8966; based on patches from "rl1987".
7497 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
7498 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
7499 - The TunnelDirConns and PreferTunnelledDirConns options no longer
7500 exist; tunneled directory connections have been available since
7501 0.1.2.5-alpha, and turning them off is not a good idea. This is a
7502 brute-force fix for 10849, where "TunnelDirConns 0" would break
7506 Changes in version 0.2.4.22 - 2014-05-16
7507 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
7508 alpha release series. These include blocking all authority signing
7509 keys that may have been affected by the OpenSSL "heartbleed" bug,
7510 choosing a far more secure set of TLS ciphersuites by default, closing
7511 a couple of memory leaks that could be used to run a target relay out
7512 of RAM, and several others.
7514 o Major features (security, backport from 0.2.5.4-alpha):
7515 - Block authority signing keys that were used on authorities
7516 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
7517 don't have any evidence that these keys _were_ compromised; we're
7518 doing this to be prudent.) Resolves ticket 11464.
7520 o Major bugfixes (security, OOM):
7521 - Fix a memory leak that could occur if a microdescriptor parse
7522 fails during the tokenizing step. This bug could enable a memory
7523 exhaustion attack by directory servers. Fixes bug 11649; bugfix
7526 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
7527 - The relay ciphersuite list is now generated automatically based on
7528 uniform criteria, and includes all OpenSSL ciphersuites with
7529 acceptable strength and forward secrecy. Previously, we had left
7530 some perfectly fine ciphersuites unsupported due to omission or
7531 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
7532 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
7533 - Relays now trust themselves to have a better view than clients of
7534 which TLS ciphersuites are better than others. (Thanks to bug
7535 11513, the relay list is now well-considered, whereas the client
7536 list has been chosen mainly for anti-fingerprinting purposes.)
7537 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
7538 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
7539 AES128. Resolves ticket 11528.
7540 - Clients now try to advertise the same list of ciphersuites as
7541 Firefox 28. This change enables selection of (fast) GCM
7542 ciphersuites, disables some strange old ciphers, and stops
7543 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
7544 Resolves ticket 11438.
7546 o Minor bugfixes (configuration, security):
7547 - When running a hidden service, do not allow TunneledDirConns 0:
7548 trying to set that option together with a hidden service would
7549 otherwise prevent the hidden service from running, and also make
7550 it publish its descriptors directly over HTTP. Fixes bug 10849;
7551 bugfix on 0.2.1.1-alpha.
7553 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
7554 - Avoid sending a garbage value to the controller when a circuit is
7555 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
7557 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
7558 - Stop leaking memory when we successfully resolve a PTR record.
7559 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
7561 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
7562 - Avoid 60-second delays in the bootstrapping process when Tor is
7563 launching for a second time while using bridges. Fixes bug 9229;
7564 bugfix on 0.2.0.3-alpha.
7566 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
7567 - Give the correct URL in the warning message when trying to run a
7568 relay on an ancient version of Windows. Fixes bug 9393.
7570 o Minor bugfixes (compilation):
7571 - Fix a compilation error when compiling with --disable-curve25519.
7572 Fixes bug 9700; bugfix on 0.2.4.17-rc.
7575 - Downgrade the warning severity for the the "md was still
7576 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
7577 for trying to diagnose this bug, and the current warning in
7578 earlier versions of tor achieves nothing useful. Addresses warning
7581 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
7582 - When we run out of usable circuit IDs on a channel, log only one
7583 warning for the whole channel, and describe how many circuits
7584 there were on the channel. Fixes part of ticket 11553.
7586 o Minor features (security, backport from 0.2.5.4-alpha):
7587 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
7588 leave the default at 8GBytes), to better support Raspberry Pi
7589 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
7591 o Documentation (backport from 0.2.5.4-alpha):
7592 - Correctly document that we search for a system torrc file before
7593 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
7597 Changes in version 0.2.5.4-alpha - 2014-04-25
7598 Tor 0.2.5.4-alpha includes several security and performance
7599 improvements for clients and relays, including blacklisting authority
7600 signing keys that were used while susceptible to the OpenSSL
7601 "heartbleed" bug, fixing two expensive functions on busy relays,
7602 improved TLS ciphersuite preference lists, support for run-time
7603 hardening on compilers that support AddressSanitizer, and more work on
7604 the Linux sandbox code.
7606 There are also several usability fixes for clients (especially clients
7607 that use bridges), two new TransPort protocols supported (one on
7608 OpenBSD, one on FreeBSD), and various other bugfixes.
7610 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
7611 have accumulated many known flaws; everyone should upgrade.
7613 o Major features (security):
7614 - If you don't specify MaxMemInQueues yourself, Tor now tries to
7615 pick a good value based on your total system memory. Previously,
7616 the default was always 8 GB. You can still override the default by
7617 setting MaxMemInQueues yourself. Resolves ticket 11396.
7618 - Block authority signing keys that were used on authorities
7619 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
7620 don't have any evidence that these keys _were_ compromised; we're
7621 doing this to be prudent.) Resolves ticket 11464.
7623 o Major features (relay performance):
7624 - Speed up server-side lookups of rendezvous and introduction point
7625 circuits by using hashtables instead of linear searches. These
7626 functions previously accounted between 3 and 7% of CPU usage on
7627 some busy relays. Resolves ticket 9841.
7628 - Avoid wasting CPU when extending a circuit over a channel that is
7629 nearly out of circuit IDs. Previously, we would do a linear scan
7630 over possible circuit IDs before finding one or deciding that we
7631 had exhausted our possibilities. Now, we try at most 64 random
7632 circuit IDs before deciding that we probably won't succeed. Fixes
7633 a possible root cause of ticket 11553.
7635 o Major features (seccomp2 sandbox, Linux only):
7636 - The seccomp2 sandbox can now run a test network for multiple hours
7637 without crashing. The sandbox is still experimental, and more bugs
7638 will probably turn up. To try it, enable "Sandbox 1" on a Linux
7639 host. Resolves ticket 11351.
7640 - Strengthen sandbox code: the sandbox can now test the arguments
7641 for rename(), and blocks _sysctl() entirely. Resolves another part
7643 - When the sandbox blocks a system call, it now tries to log a stack
7644 trace before exiting. Resolves ticket 11465.
7646 o Major bugfixes (TLS cipher selection):
7647 - The relay ciphersuite list is now generated automatically based on
7648 uniform criteria, and includes all OpenSSL ciphersuites with
7649 acceptable strength and forward secrecy. Previously, we had left
7650 some perfectly fine ciphersuites unsupported due to omission or
7651 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
7652 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
7653 - Relays now trust themselves to have a better view than clients of
7654 which TLS ciphersuites are better than others. (Thanks to bug
7655 11513, the relay list is now well-considered, whereas the client
7656 list has been chosen mainly for anti-fingerprinting purposes.)
7657 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
7658 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
7659 AES128. Resolves ticket 11528.
7660 - Clients now try to advertise the same list of ciphersuites as
7661 Firefox 28. This change enables selection of (fast) GCM
7662 ciphersuites, disables some strange old ciphers, and stops
7663 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
7664 Resolves ticket 11438.
7666 o Major bugfixes (bridge client):
7667 - Avoid 60-second delays in the bootstrapping process when Tor is
7668 launching for a second time while using bridges. Fixes bug 9229;
7669 bugfix on 0.2.0.3-alpha.
7671 o Minor features (transparent proxy, *BSD):
7672 - Support FreeBSD's ipfw firewall interface for TransPort ports on
7673 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
7674 10267; patch from "yurivict".
7675 - Support OpenBSD's divert-to rules with the pf firewall for
7676 transparent proxy ports. To enable it, set "TransProxyType
7677 pf-divert". This allows Tor to run a TransPort transparent proxy
7678 port on OpenBSD 4.4 or later without root privileges. See the
7679 pf.conf(5) manual page for information on configuring pf to use
7680 divert-to rules. Closes ticket 10896; patch from Dana Koch.
7682 o Minor features (security):
7683 - New --enable-expensive-hardening option to enable security
7684 hardening options that consume nontrivial amounts of CPU and
7685 memory. Right now, this includes AddressSanitizer and UbSan, which
7686 are supported in newer versions of GCC and Clang. Closes ticket
7689 o Minor features (log verbosity):
7690 - Demote the message that we give when a flushing connection times
7691 out for too long from NOTICE to INFO. It was usually meaningless.
7692 Resolves ticket 5286.
7693 - Don't log so many notice-level bootstrapping messages at startup
7694 about downloading descriptors. Previously, we'd log a notice
7695 whenever we learned about more routers. Now, we only log a notice
7696 at every 5% of progress. Fixes bug 9963.
7697 - Warn less verbosely when receiving a malformed
7698 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
7699 - When we run out of usable circuit IDs on a channel, log only one
7700 warning for the whole channel, and describe how many circuits
7701 there were on the channel. Fixes part of ticket 11553.
7703 o Minor features (relay):
7704 - If a circuit timed out for at least 3 minutes, check if we have a
7705 new external IP address, and publish a new descriptor with the new
7706 IP address if it changed. Resolves ticket 2454.
7708 o Minor features (controller):
7709 - Make the entire exit policy available from the control port via
7710 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
7712 - Because of the fix for ticket 11396, the real limit for memory
7713 usage may no longer match the configured MaxMemInQueues value. The
7714 real limit is now exposed via GETINFO limits/max-mem-in-queues.
7716 o Minor features (bridge client):
7717 - Report a more useful failure message when we can't connect to a
7718 bridge because we don't have the right pluggable transport
7719 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
7721 o Minor features (diagnostic):
7722 - Add more log messages to diagnose bug 7164, which causes
7723 intermittent "microdesc_free() called but md was still referenced"
7724 warnings. We now include more information, to figure out why we
7725 might be cleaning a microdescriptor for being too old if it's
7726 still referenced by a live node_t object.
7728 o Minor bugfixes (client, DNSPort):
7729 - When using DNSPort, try to respond to AAAA requests with AAAA
7730 answers. Previously, we hadn't looked at the request type when
7731 deciding which answer type to prefer. Fixes bug 10468; bugfix on
7733 - When receiving a DNS query for an unsupported record type, reply
7734 with no answer rather than with a NOTIMPL error. This behavior
7735 isn't correct either, but it will break fewer client programs, we
7736 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
7739 o Minor bugfixes (exit relay):
7740 - Stop leaking memory when we successfully resolve a PTR record.
7741 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
7743 o Minor bugfixes (bridge client):
7744 - Stop accepting bridge lines containing hostnames. Doing so would
7745 cause clients to perform DNS requests on the hostnames, which was
7746 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
7747 - Avoid a 60-second delay in the bootstrapping process when a Tor
7748 client with pluggable transports re-reads its configuration at
7749 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
7751 o Minor bugfixes (client, logging during bootstrap):
7752 - Warn only once if we start logging in an unsafe way. Previously,
7753 we complain as many times as we had problems. Fixes bug 9870;
7754 bugfix on 0.2.5.1-alpha.
7755 - Only report the first fatal bootstrap error on a given OR
7756 connection. This stops us from telling the controller bogus error
7757 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
7758 - Be more helpful when trying to run sandboxed on Linux without
7759 libseccomp. Instead of saying "Sandbox is not implemented on this
7760 platform", we now explain that we need to be built with
7761 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
7762 - Avoid generating spurious warnings when starting with
7763 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
7766 o Minor bugfixes (closing OR connections):
7767 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
7768 check if it's an or_connection_t and correctly call
7769 connection_or_close_for_error() rather than
7770 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
7772 - When closing all connections on setting DisableNetwork to 1, use
7773 connection_or_close_normally() rather than closing OR connections
7774 out from under the channel layer. Fixes bug 11306; bugfix on
7777 o Minor bugfixes (controller):
7778 - Avoid sending a garbage value to the controller when a circuit is
7779 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
7781 o Minor bugfixes (tor-fw-helper):
7782 - Allow tor-fw-helper to build again by adding src/ext to its
7783 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
7785 o Minor bugfixes (bridges):
7786 - Avoid potential crashes or bad behavior when launching a
7787 server-side managed proxy with ORPort or ExtORPort temporarily
7788 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
7790 o Minor bugfixes (platform-specific):
7791 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
7792 bug 11426; bugfix on 0.2.5.3-alpha.
7793 - When dumping a malformed directory object to disk, save it in
7794 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
7796 - Don't report failures from make_socket_reuseable() on incoming
7797 sockets on OSX: this can happen when incoming connections close
7798 early. Fixes bug 10081.
7800 o Minor bugfixes (trivial memory leaks):
7801 - Fix a small memory leak when signing a directory object. Fixes bug
7802 11275; bugfix on 0.2.4.13-alpha.
7803 - Free placeholder entries in our circuit table at exit; fixes a
7804 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
7805 - Don't re-initialize a second set of OpenSSL mutexes when starting
7806 up. Previously, we'd make one set of mutexes, and then immediately
7807 replace them with another. Fixes bug 11726; bugfix on
7809 - Resolve some memory leaks found by coverity in the unit tests, on
7810 exit in tor-gencert, and on a failure to compute digests for our
7811 own keys when generating a v3 networkstatus vote. These leaks
7812 should never have affected anyone in practice.
7814 o Minor bugfixes (hidden service):
7815 - Only retry attempts to connect to a chosen rendezvous point 8
7816 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
7818 o Minor bugfixes (misc code correctness):
7819 - Fix various instances of undefined behavior in channeltls.c,
7820 tor_memmem(), and eventdns.c that would cause us to construct
7821 pointers to memory outside an allocated object. (These invalid
7822 pointers were not accessed, but C does not even allow them to
7823 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
7824 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
7825 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
7826 fix some miscellaneous errors in our tests and codebase. Fixes bug
7827 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
7828 - Always check return values for unlink, munmap, UnmapViewOfFile;
7829 check strftime return values more often. In some cases all we can
7830 do is report a warning, but this may help prevent deeper bugs from
7831 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
7833 - Fix numerous warnings from the clang "scan-build" static analyzer.
7834 Some of these are programming style issues; some of them are false
7835 positives that indicated awkward code; some are undefined behavior
7836 cases related to constructing (but not using) invalid pointers;
7837 some are assumptions about API behavior; some are (harmlessly)
7838 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
7839 correct; and one or two are genuine bugs that weren't reachable
7840 from the rest of the program. Fixes bug 8793; bugfixes on many,
7844 - Build the torify.1 manpage again. Previously, we were only trying
7845 to build it when also building tor-fw-helper. That's why we didn't
7846 notice that we'd broken the ability to build it. Fixes bug 11321;
7847 bugfix on 0.2.5.1-alpha.
7848 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
7849 11061; bugfix on 0.2.4.7-alpha.
7850 - Correctly document that we search for a system torrc file before
7851 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
7853 - Resolve warnings from Doxygen.
7855 o Code simplifications and refactoring:
7856 - Remove is_internal_IP() function. Resolves ticket 4645.
7857 - Remove unused function circuit_dump_by_chan from circuitlist.c.
7858 Closes issue 9107; patch from "marek".
7859 - Change our use of the ENUM_BF macro to avoid declarations that
7862 o Deprecated versions:
7863 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
7864 attention for some while. Directory authorities no longer accept
7865 descriptors from relays running any version of Tor prior to Tor
7866 0.2.3.16-alpha. Resolves ticket 11149.
7869 - New macros in test.h to simplify writing mock-functions for unit
7870 tests. Part of ticket 11507. Patch from Dana Koch.
7871 - Complete tests for the status.c module. Resolves ticket 11507.
7872 Patch from Dana Koch.
7875 - Remove all code for the long unused v1 directory protocol.
7876 Resolves ticket 11070.
7879 Changes in version 0.2.5.3-alpha - 2014-03-22
7880 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
7881 two new anti-DoS features for Tor relays, resolves a bug that kept
7882 SOCKS5 support for IPv6 from working, fixes several annoying usability
7883 issues for bridge users, and removes more old code for unused
7886 The Tor 0.2.5.x release series is now in patch-freeze: no feature
7887 patches not already written will be considered for inclusion in 0.2.5.x.
7889 o Major features (relay security, DoS-resistance):
7890 - When deciding whether we have run out of memory and we need to
7891 close circuits, also consider memory allocated in buffers for
7892 streams attached to each circuit.
7894 This change, which extends an anti-DoS feature introduced in
7895 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
7896 better resist more memory-based DoS attacks than before. Since the
7897 MaxMemInCellQueues option now applies to all queues, it is renamed
7898 to MaxMemInQueues. This feature fixes bug 10169.
7899 - Avoid hash-flooding denial-of-service attacks by using the secure
7900 SipHash-2-4 hash function for our hashtables. Without this
7901 feature, an attacker could degrade performance of a targeted
7902 client or server by flooding their data structures with a large
7903 number of entries to be stored at the same hash table position,
7904 thereby slowing down the Tor instance. With this feature, hash
7905 table positions are derived from a randomized cryptographic key,
7906 and an attacker cannot predict which entries will collide. Closes
7908 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
7909 the default at 8GBytes), to better support Raspberry Pi users. Fixes
7910 bug 9686; bugfix on 0.2.4.14-alpha.
7912 o Minor features (bridges, pluggable transports):
7913 - Bridges now write the SHA1 digest of their identity key
7914 fingerprint (that is, a hash of a hash of their public key) to
7915 notice-level logs, and to a new hashed-fingerprint file. This
7916 information will help bridge operators look up their bridge in
7917 Globe and similar tools. Resolves ticket 10884.
7918 - Improve the message that Tor displays when running as a bridge
7919 using pluggable transports without an Extended ORPort listener.
7920 Also, log the message in the log file too. Resolves ticket 11043.
7922 o Minor features (other):
7923 - Add a new option, PredictedPortsRelevanceTime, to control how long
7924 after having received a request to connect to a given port Tor
7925 will try to keep circuits ready in anticipation of future requests
7926 for that port. Patch from "unixninja92"; implements ticket 9176.
7927 - Generate a warning if any ports are listed in the SocksPolicy,
7928 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
7929 AuthDirBadExit options. (These options only support address
7930 ranges.) Fixes part of ticket 11108.
7931 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
7934 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
7935 - Build without warnings under clang 3.4. (We have some macros that
7936 define static functions only some of which will get used later in
7937 the module. Starting with clang 3.4, these give a warning unless the
7938 unused attribute is set on them.) Resolves ticket 10904.
7939 - Fix build warnings about missing "a2x" comment when building the
7940 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
7941 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
7943 o Minor bugfixes (client):
7944 - Improve the log message when we can't connect to a hidden service
7945 because all of the hidden service directory nodes hosting its
7946 descriptor are excluded. Improves on our fix for bug 10722, which
7947 was a bugfix on 0.2.0.10-alpha.
7948 - Raise a control port warning when we fail to connect to all of
7949 our bridges. Previously, we didn't inform the controller, and
7950 the bootstrap process would stall. Fixes bug 11069; bugfix on
7952 - Exit immediately when a process-owning controller exits.
7953 Previously, tor relays would wait for a little while after their
7954 controller exited, as if they had gotten an INT signal -- but this
7955 was problematic, since there was no feedback for the user. To do a
7956 clean shutdown, controllers should send an INT signal and give Tor
7957 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
7958 - Stop attempting to connect to bridges before our pluggable
7959 transports are configured (harmless but resulted in some erroneous
7960 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
7961 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
7962 generating incorrect SOCKS5 responses, and confusing client
7963 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
7965 o Minor bugfixes (relays and bridges):
7966 - Avoid crashing on a malformed resolv.conf file when running a
7967 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
7968 - Non-exit relays no longer launch mock DNS requests to check for
7969 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
7970 non-exit relays stopped servicing DNS requests. Fixes bug 965;
7971 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
7972 - Bridges now report complete directory request statistics. Related
7973 to bug 5824; bugfix on 0.2.2.1-alpha.
7974 - Bridges now never collect statistics that were designed for
7975 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
7976 - Stop giving annoying warning messages when we decide not to launch
7977 a pluggable transport proxy that we don't need (because there are
7978 no bridges configured to use it). Resolves ticket 5018; bugfix
7980 - Give the correct URL in the warning message when trying to run a
7981 relay on an ancient version of Windows. Fixes bug 9393.
7983 o Minor bugfixes (backtrace support):
7984 - Support automatic backtraces on more platforms by using the
7985 "-fasynchronous-unwind-tables" compiler option. This option is
7986 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
7987 is on by default and table generation is not. This doesn't yet
7988 add Windows support; only Linux, OSX, and some BSDs are affected.
7989 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
7990 - Avoid strange behavior if two threads hit failed assertions at the
7991 same time and both try to log backtraces at once. (Previously, if
7992 this had happened, both threads would have stored their intermediate
7993 results in the same buffer, and generated junk outputs.) Reported by
7994 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
7995 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
7996 0.2.5.2-alpha; patch from Nick Hopper.
7998 o Minor bugfixes (unit tests):
7999 - Fix a small bug in the unit tests that might have made the tests
8000 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
8001 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
8004 - Remove all remaining code related to version-0 hidden service
8005 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
8006 the rest of bug 10841.
8009 - Document in the manpage that "KBytes" may also be written as
8010 "kilobytes" or "KB", that "Kbits" may also be written as
8011 "kilobits", and so forth. Closes ticket 9222.
8012 - Document that the ClientOnly config option overrides ORPort.
8013 Our old explanation made ClientOnly sound as though it did
8014 nothing at all. Resolves bug 9059.
8015 - Explain that SocksPolicy, DirPolicy, and similar options don't
8016 take port arguments. Fixes the other part of ticket 11108.
8017 - Fix a comment about the rend_server_descriptor_t.protocols field
8018 to more accurately describe its range. Also, make that field
8019 unsigned, to more accurately reflect its usage. Fixes bug 9099;
8020 bugfix on 0.2.1.5-alpha.
8021 - Fix the manpage's description of HiddenServiceAuthorizeClient:
8022 the maximum client name length is 16, not 19. Fixes bug 11118;
8023 bugfix on 0.2.1.6-alpha.
8025 o Code simplifications and refactoring:
8026 - Get rid of router->address, since in all cases it was just the
8027 string representation of router->addr. Resolves ticket 5528.
8029 o Test infrastructure:
8030 - Update to the latest version of tinytest.
8031 - Improve the tinytest implementation of string operation tests so
8032 that comparisons with NULL strings no longer crash the tests; they
8033 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
8036 Changes in version 0.2.4.21 - 2014-02-28
8037 Tor 0.2.4.21 further improves security against potential adversaries who
8038 find breaking 1024-bit crypto doable, and backports several stability
8039 and robustness patches from the 0.2.5 branch.
8041 o Major features (client security):
8042 - When we choose a path for a 3-hop circuit, make sure it contains
8043 at least one relay that supports the NTor circuit extension
8044 handshake. Otherwise, there is a chance that we're building
8045 a circuit that's worth attacking by an adversary who finds
8046 breaking 1024-bit crypto doable, and that chance changes the game
8047 theory. Implements ticket 9777.
8050 - Do not treat streams that fail with reason
8051 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
8052 since it could also indicate an ENETUNREACH connection error. Fixes
8053 part of bug 10777; bugfix on 0.2.4.8-alpha.
8055 o Code simplification and refactoring:
8056 - Remove data structures which were introduced to implement the
8057 CellStatistics option: they are now redundant with the new timestamp
8058 field in the regular packed_cell_t data structure, which we did
8059 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
8062 - Always clear OpenSSL bignums before freeing them -- even bignums
8063 that don't contain secrets. Resolves ticket 10793. Patch by
8065 - Build without warnings under clang 3.4. (We have some macros that
8066 define static functions only some of which will get used later in
8067 the module. Starting with clang 3.4, these give a warning unless the
8068 unused attribute is set on them.) Resolves ticket 10904.
8069 - Update geoip and geoip6 files to the February 7 2014 Maxmind
8070 GeoLite2 Country database.
8073 - Set the listen() backlog limit to the largest actually supported
8074 on the system, not to the value in a header file. Fixes bug 9716;
8075 bugfix on every released Tor.
8076 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
8077 exit node as a NOROUTE error, not an INTERNAL error, since they
8078 can apparently happen when trying to connect to the wrong sort
8079 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
8080 - Fix build warnings about missing "a2x" comment when building the
8081 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
8082 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
8083 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
8084 not entirely remove it from the connection lists. Fixes bug 9602;
8085 bugfix on 0.2.4.4-alpha.
8086 - Fix a segmentation fault in our benchmark code when running with
8087 Fedora's OpenSSL package, or any other OpenSSL that provides
8088 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
8089 - Turn "circuit handshake stats since last time" log messages into a
8090 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
8092 o Documentation fixes:
8093 - Document that all but one DirPort entry must have the NoAdvertise
8094 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
8097 Changes in version 0.2.5.2-alpha - 2014-02-13
8098 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
8099 like the "poor random number generation" fix and the "building too many
8100 circuits" fix. It also further improves security against potential
8101 adversaries who find breaking 1024-bit crypto doable, and launches
8102 pluggable transports on demand (which gets us closer to integrating
8103 pluggable transport support by default -- not to be confused with Tor
8104 bundles enabling pluggable transports and bridges by default).
8106 o Major features (client security):
8107 - When we choose a path for a 3-hop circuit, make sure it contains
8108 at least one relay that supports the NTor circuit extension
8109 handshake. Otherwise, there is a chance that we're building
8110 a circuit that's worth attacking by an adversary who finds
8111 breaking 1024-bit crypto doable, and that chance changes the game
8112 theory. Implements ticket 9777.
8113 - Clients now look at the "usecreatefast" consensus parameter to
8114 decide whether to use CREATE_FAST or CREATE cells for the first hop
8115 of their circuit. This approach can improve security on connections
8116 where Tor's circuit handshake is stronger than the available TLS
8117 connection security levels, but the tradeoff is more computational
8118 load on guard relays. Implements proposal 221. Resolves ticket 9386.
8120 o Major features (bridges):
8121 - Don't launch pluggable transport proxies if we don't have any
8122 bridges configured that would use them. Now we can list many
8123 pluggable transports, and Tor will dynamically start one when it
8124 hears a bridge address that needs it. Resolves ticket 5018.
8125 - The bridge directory authority now assigns status flags (Stable,
8126 Guard, etc) to bridges based on thresholds calculated over all
8127 Running bridges. Now bridgedb can finally make use of its features
8128 to e.g. include at least one Stable bridge in its answers. Fixes
8131 o Major features (other):
8132 - Extend ORCONN controller event to include an "ID" parameter,
8133 and add four new controller event types CONN_BW, CIRC_BW,
8134 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
8135 The new events are emitted in private Tor networks only, with the
8136 goal of being able to better track performance and load during
8137 full-network simulations. Implements proposal 218 and ticket 7359.
8138 - On some platforms (currently: recent OSX versions, glibc-based
8139 platforms that support the ELF format, and a few other
8140 Unix-like operating systems), Tor can now dump stack traces
8141 when a crash occurs or an assertion fails. By default, traces
8142 are dumped to stderr (if possible) and to any logs that are
8143 reporting errors. Implements ticket 9299.
8146 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
8147 not entirely remove it from the connection lists. Fixes bug 9602;
8148 bugfix on 0.2.4.4-alpha.
8149 - Do not treat streams that fail with reason
8150 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
8151 since it could also indicate an ENETUNREACH connection error. Fixes
8152 part of bug 10777; bugfix on 0.2.4.8-alpha.
8154 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
8155 - Do not allow OpenSSL engines to replace the PRNG, even when
8156 HardwareAccel is set. The only default builtin PRNG engine uses
8157 the Intel RDRAND instruction to replace the entire PRNG, and
8158 ignores all attempts to seed it with more entropy. That's
8159 cryptographically stupid: the right response to a new alleged
8160 entropy source is never to discard all previously used entropy
8161 sources. Fixes bug 10402; works around behavior introduced in
8162 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
8164 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
8165 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
8166 - Avoid launching spurious extra circuits when a stream is pending.
8167 This fixes a bug where any circuit that _wasn't_ unusable for new
8168 streams would be treated as if it were, causing extra circuits to
8169 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
8171 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8172 - No longer stop reading or writing on cpuworker connections when
8173 our rate limiting buckets go empty. Now we should handle circuit
8174 handshake requests more promptly. Resolves bug 9731.
8175 - Stop trying to bootstrap all our directory information from
8176 only our first guard. Discovered while fixing bug 9946; bugfix
8179 o Minor features (bridges, pluggable transports):
8180 - Add threshold cutoffs to the networkstatus document created by
8181 the Bridge Authority. Fixes bug 1117.
8182 - On Windows, spawn background processes using the CREATE_NO_WINDOW
8183 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
8184 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
8185 Vidalia set this option for us.) Implements ticket 10297.
8187 o Minor features (security):
8188 - Always clear OpenSSL bignums before freeing them -- even bignums
8189 that don't contain secrets. Resolves ticket 10793. Patch by
8192 o Minor features (config options and command line):
8193 - Add an --allow-missing-torrc commandline option that tells Tor to
8194 run even if the configuration file specified by -f is not available.
8195 Implements ticket 10060.
8196 - Add support for the TPROXY transparent proxying facility on Linux.
8197 See documentation for the new TransProxyType option for more
8198 details. Implementation by "thomo". Closes ticket 10582.
8200 o Minor features (controller):
8201 - Add a new "HS_DESC" controller event that reports activities
8202 related to hidden service descriptors. Resolves ticket 8510.
8203 - New "DROPGUARDS" controller command to forget all current entry
8204 guards. Not recommended for ordinary use, since replacing guards
8205 too frequently makes several attacks easier. Resolves ticket 9934;
8208 o Minor features (build):
8209 - Assume that a user using ./configure --host wants to cross-compile,
8210 and give an error if we cannot find a properly named
8211 tool-chain. Add a --disable-tool-name-check option to proceed
8212 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
8213 - If we run ./configure and the compiler recognizes -fstack-protector
8214 but the linker rejects it, warn the user about a potentially missing
8215 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
8217 o Minor features (testing):
8218 - If Python is installed, "make check" now runs extra tests beyond
8219 the unit test scripts.
8220 - When bootstrapping a test network, sometimes very few relays get
8221 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
8222 specify a set of relays which should be voted Guard regardless of
8223 their uptime or bandwidth. Addresses ticket 9206.
8225 o Minor features (log messages):
8226 - When ServerTransportPlugin is set on a bridge, Tor can write more
8227 useful statistics about bridge use in its extrainfo descriptors,
8228 but only if the Extended ORPort ("ExtORPort") is set too. Add a
8229 log message to inform the user in this case. Resolves ticket 9651.
8230 - When receiving a new controller connection, log the origin address.
8231 Resolves ticket 9698; patch from "sigpipe".
8232 - When logging OpenSSL engine status at startup, log the status of
8233 more engines. Fixes ticket 10043; patch from Joshua Datko.
8234 - Turn "circuit handshake stats since last time" log messages into a
8235 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
8237 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8238 - Improve the circuit queue out-of-memory handler. Previously, when
8239 we ran low on memory, we'd close whichever circuits had the most
8240 queued cells. Now, we close those that have the *oldest* queued
8241 cells, on the theory that those are most responsible for us
8242 running low on memory. Based on analysis from a forthcoming paper
8243 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
8244 - Generate bootstrapping status update events correctly when fetching
8245 microdescriptors. Fixes bug 9927.
8246 - Update to the October 2 2013 Maxmind GeoLite Country database.
8248 o Minor bugfixes (clients):
8249 - When closing a channel that has already been open, do not close
8250 pending circuits that were waiting to connect to the same relay.
8251 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
8254 o Minor bugfixes (relays):
8255 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
8256 exit node as a NOROUTE error, not an INTERNAL error, since they
8257 can apparently happen when trying to connect to the wrong sort
8258 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
8260 o Minor bugfixes (bridges):
8261 - Fix a bug where the first connection works to a bridge that uses a
8262 pluggable transport with client-side parameters, but we don't send
8263 the client-side parameters on subsequent connections. (We don't
8264 use any pluggable transports with client-side parameters yet,
8265 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
8266 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
8268 o Minor bugfixes (node selection):
8269 - If ExcludeNodes is set, consider non-excluded hidden service
8270 directory servers before excluded ones. Do not consider excluded
8271 hidden service directory servers at all if StrictNodes is
8272 set. (Previously, we would sometimes decide to connect to those
8273 servers, and then realize before we initiated a connection that
8274 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
8276 - If we set the ExitNodes option but it doesn't include any nodes
8277 that have the Exit flag, we would choose not to bootstrap. Now we
8278 bootstrap so long as ExitNodes includes nodes which can exit to
8279 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
8281 o Minor bugfixes (controller and command-line):
8282 - If changing a config option via "setconf" fails in a recoverable
8283 way, we used to nonetheless write our new control ports to the
8284 file described by the "ControlPortWriteToFile" option. Now we only
8285 write out that file if we successfully switch to the new config
8286 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
8287 - When a command-line option such as --version or --help that
8288 ordinarily implies --hush appears on the command line along with
8289 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
8290 only if it appeared later on the command line. Fixes bug 9578;
8291 bugfix on 0.2.5.1-alpha.
8293 o Minor bugfixes (code correctness):
8294 - Previously we used two temporary files when writing descriptors to
8295 disk; now we only use one. Fixes bug 1376.
8296 - Remove an erroneous (but impossible and thus harmless) pointer
8297 comparison that would have allowed compilers to skip a bounds
8298 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
8299 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
8300 - Fix an always-true assertion in pluggable transports code so it
8301 actually checks what it was trying to check. Fixes bug 10046;
8302 bugfix on 0.2.3.9-alpha. Found by "dcb".
8304 o Minor bugfixes (protocol correctness):
8305 - When receiving a VERSIONS cell with an odd number of bytes, close
8306 the connection immediately since the cell is malformed. Fixes bug
8307 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
8310 o Minor bugfixes (build):
8311 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
8312 turned off (that is, without support for v2 link handshakes). Fixes
8313 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
8314 - Fix compilation warnings and startup issues when running with
8315 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
8317 - Fix compilation on Solaris 9, which didn't like us having an
8318 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
8320 o Minor bugfixes (testing):
8321 - Fix a segmentation fault in our benchmark code when running with
8322 Fedora's OpenSSL package, or any other OpenSSL that provides
8323 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
8325 o Minor bugfixes (log messages):
8326 - Fix a bug where clients using bridges would report themselves
8327 as 50% bootstrapped even without a live consensus document.
8328 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
8329 - Suppress a warning where, if there's only one directory authority
8330 in the network, we would complain that votes and signatures cannot
8331 be uploaded to other directory authorities. Fixes bug 10842;
8332 bugfix on 0.2.2.26-beta.
8333 - Report bootstrapping progress correctly when we're downloading
8334 microdescriptors. We had updated our "do we have enough microdescs
8335 to begin building circuits?" logic most recently in 0.2.4.10-alpha
8336 (see bug 5956), but we left the bootstrap status event logic at
8337 "how far through getting 1/4 of them are we?" Fixes bug 9958;
8338 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
8340 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
8341 - Avoid a crash bug when starting with a corrupted microdescriptor
8342 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
8343 - If we fail to dump a previously cached microdescriptor to disk, avoid
8344 freeing duplicate data later on. Fixes bug 10423; bugfix on
8345 0.2.4.13-alpha. Spotted by "bobnomnom".
8347 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8348 - Correctly log long IPv6 exit policies, instead of truncating them
8349 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
8350 - Our default TLS ecdhe groups were backwards: we meant to be using
8351 P224 for relays (for performance win) and P256 for bridges (since
8352 it is more common in the wild). Instead we had it backwards. After
8353 reconsideration, we decided that the default should be P256 on all
8354 hosts, since its security is probably better, and since P224 is
8355 reportedly used quite little in the wild. Found by "skruffy" on
8356 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
8357 - Free directory authority certificate download statuses on exit
8358 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
8360 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8361 - If the guard we choose first doesn't answer, we would try the
8362 second guard, but once we connected to the second guard we would
8363 abandon it and retry the first one, slowing down bootstrapping.
8364 The fix is to treat all our initially chosen guards as acceptable
8365 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
8366 - Fix an assertion failure that would occur when disabling the
8367 ORPort setting on a running Tor process while accounting was
8368 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
8369 - When examining the list of network interfaces to find our address,
8370 do not consider non-running or disabled network interfaces. Fixes
8371 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
8372 - Avoid an off-by-one error when checking buffer boundaries when
8373 formatting the exit status of a pluggable transport helper.
8374 This is probably not an exploitable bug, but better safe than
8375 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
8378 o Removed code and features:
8379 - Clients now reject any directory authority certificates lacking
8380 a dir-key-crosscert element. These have been included since
8381 0.2.1.9-alpha, so there's no real reason for them to be optional
8382 any longer. Completes proposal 157. Resolves ticket 10162.
8383 - Remove all code that existed to support the v2 directory system,
8384 since there are no longer any v2 directory authorities. Resolves
8386 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
8387 options, which were used for designating authorities as "Hidden
8388 service authorities". There has been no use of hidden service
8389 authorities since 0.2.2.1-alpha, when we stopped uploading or
8390 downloading v0 hidden service descriptors. Fixes bug 10881; also
8391 part of a fix for bug 10841.
8393 o Code simplification and refactoring:
8394 - Remove some old fallback code designed to keep Tor clients working
8395 in a network with only two working relays. Elsewhere in the code we
8396 have long since stopped supporting such networks, so there wasn't
8397 much point in keeping it around. Addresses ticket 9926.
8398 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
8399 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
8400 - Remove data structures which were introduced to implement the
8401 CellStatistics option: they are now redundant with the addition
8402 of a timestamp to the regular packed_cell_t data structure, which
8403 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
8406 o Documentation (man page) fixes:
8407 - Update manpage to describe some of the files you can expect to
8408 find in Tor's DataDirectory. Addresses ticket 9839.
8409 - Document that all but one DirPort entry must have the NoAdvertise
8410 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
8412 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8413 - Clarify the usage and risks of setting the ContactInfo torrc line
8414 for your relay or bridge. Resolves ticket 9854.
8415 - Add anchors to the manpage so we can link to the html version of
8416 the documentation for specific options. Resolves ticket 9866.
8417 - Replace remaining references to DirServer in man page and
8418 log entries. Resolves ticket 10124.
8421 - Make the "tor-gencert" tool used by directory authority operators
8422 create 2048-bit signing keys by default (rather than 1024-bit, since
8423 1024-bit is uncomfortably small these days). Addresses ticket 10324.
8426 Changes in version 0.2.4.20 - 2013-12-22
8427 Tor 0.2.4.20 fixes potentially poor random number generation for users
8428 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
8429 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
8430 and 4) have no state file in their DataDirectory (as would happen on
8431 first start). Users who generated relay or hidden service identity
8432 keys in such a situation should discard them and generate new ones.
8434 This release also fixes a logic error that caused Tor clients to build
8435 many more preemptive circuits than they actually need.
8438 - Do not allow OpenSSL engines to replace the PRNG, even when
8439 HardwareAccel is set. The only default builtin PRNG engine uses
8440 the Intel RDRAND instruction to replace the entire PRNG, and
8441 ignores all attempts to seed it with more entropy. That's
8442 cryptographically stupid: the right response to a new alleged
8443 entropy source is never to discard all previously used entropy
8444 sources. Fixes bug 10402; works around behavior introduced in
8445 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
8447 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
8448 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
8449 - Avoid launching spurious extra circuits when a stream is pending.
8450 This fixes a bug where any circuit that _wasn't_ unusable for new
8451 streams would be treated as if it were, causing extra circuits to
8452 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
8455 - Avoid a crash bug when starting with a corrupted microdescriptor
8456 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
8457 - If we fail to dump a previously cached microdescriptor to disk, avoid
8458 freeing duplicate data later on. Fixes bug 10423; bugfix on
8459 0.2.4.13-alpha. Spotted by "bobnomnom".
8462 Changes in version 0.2.4.19 - 2013-12-11
8463 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
8464 (1986-2013). Aaron worked on diverse projects including helping to guide
8465 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
8466 transparency to the U.S government's PACER documents, and contributing
8467 design and development for Tor and Tor2Web. Aaron was one of the latest
8468 martyrs in our collective fight for civil liberties and human rights,
8469 and his death is all the more painful because he was one of us.
8471 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
8472 a new circuit handshake and link encryption that use ECC to provide
8473 better security and efficiency; makes relays better manage circuit
8474 creation requests; uses "directory guards" to reduce client enumeration
8475 risks; makes bridges collect and report statistics about the pluggable
8476 transports they support; cleans up and improves our geoip database;
8477 gets much closer to IPv6 support for clients, bridges, and relays; makes
8478 directory authorities use measured bandwidths rather than advertised
8479 ones when computing flags and thresholds; disables client-side DNS
8480 caching to reduce tracking risks; and fixes a big bug in bridge
8481 reachability testing. This release introduces two new design
8482 abstractions in the code: a new "channel" abstraction between circuits
8483 and or_connections to allow for implementing alternate relay-to-relay
8484 transports, and a new "circuitmux" abstraction storing the queue of
8485 circuits for a channel. The release also includes many stability,
8486 security, and privacy fixes.
8489 Changes in version 0.2.4.18-rc - 2013-11-16
8490 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
8491 series. It takes a variety of fixes from the 0.2.5.x branch to improve
8492 stability, performance, and better handling of edge cases.
8495 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
8496 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
8497 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
8498 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
8499 them to solve bug 6033.)
8502 - No longer stop reading or writing on cpuworker connections when
8503 our rate limiting buckets go empty. Now we should handle circuit
8504 handshake requests more promptly. Resolves bug 9731.
8505 - If we are unable to save a microdescriptor to the journal, do not
8506 drop it from memory and then reattempt downloading it. Fixes bug
8507 9645; bugfix on 0.2.2.6-alpha.
8508 - Stop trying to bootstrap all our directory information from
8509 only our first guard. Discovered while fixing bug 9946; bugfix
8511 - The new channel code sometimes lost track of in-progress circuits,
8512 causing long-running clients to stop building new circuits. The
8513 fix is to always call circuit_n_chan_done(chan, 0) from
8514 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
8516 o Minor bugfixes (on 0.2.4.x):
8517 - Correctly log long IPv6 exit policies, instead of truncating them
8518 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
8519 - Our default TLS ecdhe groups were backwards: we meant to be using
8520 P224 for relays (for performance win) and P256 for bridges (since
8521 it is more common in the wild). Instead we had it backwards. After
8522 reconsideration, we decided that the default should be P256 on all
8523 hosts, since its security is probably better, and since P224 is
8524 reportedly used quite little in the wild. Found by "skruffy" on
8525 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
8526 - Free directory authority certificate download statuses on exit
8527 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
8529 o Minor bugfixes (on 0.2.3.x and earlier):
8530 - If the guard we choose first doesn't answer, we would try the
8531 second guard, but once we connected to the second guard we would
8532 abandon it and retry the first one, slowing down bootstrapping.
8533 The fix is to treat all our initially chosen guards as acceptable
8534 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
8535 - Fix an assertion failure that would occur when disabling the
8536 ORPort setting on a running Tor process while accounting was
8537 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
8538 - When examining the list of network interfaces to find our address,
8539 do not consider non-running or disabled network interfaces. Fixes
8540 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
8541 - Avoid an off-by-one error when checking buffer boundaries when
8542 formatting the exit status of a pluggable transport helper.
8543 This is probably not an exploitable bug, but better safe than
8544 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
8547 o Minor features (protecting client timestamps):
8548 - Clients no longer send timestamps in their NETINFO cells. These were
8549 not used for anything, and they provided one small way for clients
8550 to be distinguished from each other as they moved from network to
8551 network or behind NAT. Implements part of proposal 222.
8552 - Clients now round timestamps in INTRODUCE cells down to the nearest
8553 10 minutes. If a new Support022HiddenServices option is set to 0, or
8554 if it's set to "auto" and the feature is disabled in the consensus,
8555 the timestamp is sent as 0 instead. Implements part of proposal 222.
8556 - Stop sending timestamps in AUTHENTICATE cells. This is not such
8557 a big deal from a security point of view, but it achieves no actual
8558 good purpose, and isn't needed. Implements part of proposal 222.
8559 - Reduce down accuracy of timestamps in hidden service descriptors.
8560 Implements part of proposal 222.
8562 o Minor features (other):
8563 - Improve the circuit queue out-of-memory handler. Previously, when
8564 we ran low on memory, we'd close whichever circuits had the most
8565 queued cells. Now, we close those that have the *oldest* queued
8566 cells, on the theory that those are most responsible for us
8567 running low on memory. Based on analysis from a forthcoming paper
8568 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
8569 - Generate bootstrapping status update events correctly when fetching
8570 microdescriptors. Fixes bug 9927.
8571 - Update to the October 2 2013 Maxmind GeoLite Country database.
8573 o Documentation fixes:
8574 - Clarify the usage and risks of setting the ContactInfo torrc line
8575 for your relay or bridge. Resolves ticket 9854.
8576 - Add anchors to the manpage so we can link to the html version of
8577 the documentation for specific options. Resolves ticket 9866.
8578 - Replace remaining references to DirServer in man page and
8579 log entries. Resolves ticket 10124.
8582 Changes in version 0.2.5.1-alpha - 2013-10-02
8583 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
8584 on Linux, allows bridges that offer pluggable transports to report usage
8585 statistics, fixes many issues to make testing easier, and provides
8586 a pile of minor features and bugfixes that have been waiting for a
8587 release of the new branch.
8589 This is the first alpha release in a new series, so expect there to
8590 be bugs. Users who would rather test out a more stable branch should
8591 stay with 0.2.4.x for now.
8593 o Major features (security):
8594 - Use the seccomp2 syscall filtering facility on Linux to limit
8595 which system calls Tor can invoke. This is an experimental,
8596 Linux-only feature to provide defense-in-depth against unknown
8597 attacks. To try turning it on, set "Sandbox 1" in your torrc
8598 file. Please be ready to report bugs. We hope to add support
8599 for better sandboxing in the future, including more fine-grained
8600 filters, better division of responsibility, and support for more
8601 platforms. This work has been done by Cristian-Matei Toader for
8602 Google Summer of Code.
8603 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
8604 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
8605 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
8606 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
8607 them to solve bug 6033.)
8609 o Major features (other):
8610 - Add support for passing arguments to managed pluggable transport
8611 proxies. Implements ticket 3594.
8612 - Bridges now track GeoIP information and the number of their users
8613 even when pluggable transports are in use, and report usage
8614 statistics in their extra-info descriptors. Resolves tickets 4773
8616 - Make testing Tor networks bootstrap better: lower directory fetch
8617 retry schedules and maximum interval without directory requests,
8618 and raise maximum download tries. Implements ticket 6752.
8619 - Add make target 'test-network' to run tests on a Chutney network.
8620 Implements ticket 8530.
8621 - The ntor handshake is now on-by-default, no matter what the
8622 directory authorities recommend. Implements ticket 8561.
8625 - Instead of writing destroy cells directly to outgoing connection
8626 buffers, queue them and intersperse them with other outgoing cells.
8627 This can prevent a set of resource starvation conditions where too
8628 many pending destroy cells prevent data cells from actually getting
8629 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
8630 bugfix on 0.2.0.1-alpha.
8631 - If we are unable to save a microdescriptor to the journal, do not
8632 drop it from memory and then reattempt downloading it. Fixes bug
8633 9645; bugfix on 0.2.2.6-alpha.
8634 - The new channel code sometimes lost track of in-progress circuits,
8635 causing long-running clients to stop building new circuits. The
8636 fix is to always call circuit_n_chan_done(chan, 0) from
8637 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
8640 - Tor now builds each source file in two modes: a mode that avoids
8641 exposing identifiers needlessly, and another mode that exposes
8642 more identifiers for testing. This lets the compiler do better at
8643 optimizing the production code, while enabling us to take more
8644 radical measures to let the unit tests test things.
8645 - The production builds no longer include functions used only in
8646 the unit tests; all functions exposed from a module only for
8647 unit-testing are now static in production builds.
8648 - Add an --enable-coverage configuration option to make the unit
8649 tests (and a new src/or/tor-cov target) to build with gcov test
8653 - We now have rudimentary function mocking support that our unit
8654 tests can use to test functions in isolation. Function mocking
8655 lets the tests temporarily replace a function's dependencies with
8656 stub functions, so that the tests can check the function without
8657 invoking the other functions it calls.
8658 - Add more unit tests for the <circid,channel>->circuit map, and
8659 the destroy-cell-tracking code to fix bug 7912.
8660 - Unit tests for failing cases of the TAP onion handshake.
8661 - More unit tests for address-manipulation functions.
8663 o Minor features (protecting client timestamps):
8664 - Clients no longer send timestamps in their NETINFO cells. These were
8665 not used for anything, and they provided one small way for clients
8666 to be distinguished from each other as they moved from network to
8667 network or behind NAT. Implements part of proposal 222.
8668 - Clients now round timestamps in INTRODUCE cells down to the nearest
8669 10 minutes. If a new Support022HiddenServices option is set to 0, or
8670 if it's set to "auto" and the feature is disabled in the consensus,
8671 the timestamp is sent as 0 instead. Implements part of proposal 222.
8672 - Stop sending timestamps in AUTHENTICATE cells. This is not such
8673 a big deal from a security point of view, but it achieves no actual
8674 good purpose, and isn't needed. Implements part of proposal 222.
8675 - Reduce down accuracy of timestamps in hidden service descriptors.
8676 Implements part of proposal 222.
8678 o Minor features (config options):
8679 - Config (torrc) lines now handle fingerprints which are missing
8680 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
8681 - Support a --dump-config option to print some or all of the
8682 configured options. Mainly useful for debugging the command-line
8683 option parsing code. Helps resolve ticket 4647.
8684 - Raise awareness of safer logging: notify user of potentially
8685 unsafe config options, like logging more verbosely than severity
8686 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
8687 - Add a new configuration option TestingV3AuthVotingStartOffset
8688 that bootstraps a network faster by changing the timing for
8689 consensus votes. Addresses ticket 8532.
8690 - Add a new torrc option "ServerTransportOptions" that allows
8691 bridge operators to pass configuration parameters to their
8692 pluggable transports. Resolves ticket 8929.
8693 - The config (torrc) file now accepts bandwidth and space limits in
8694 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
8695 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
8698 o Minor features (build):
8699 - Add support for `--library-versions` flag. Implements ticket 6384.
8700 - Return the "unexpected sendme" warnings to a warn severity, but make
8701 them rate limited, to help diagnose ticket 8093.
8702 - Detect a missing asciidoc, and warn the user about it, during
8703 configure rather than at build time. Fixes issue 6506. Patch from
8706 o Minor features (other):
8707 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
8708 sockets in a single system call. Implements ticket 5129.
8709 - Log current accounting state (bytes sent and received + remaining
8710 time for the current accounting period) in the relay's heartbeat
8711 message. Implements ticket 5526; patch from Peter Retzlaff.
8712 - Implement the TRANSPORT_LAUNCHED control port event that
8713 notifies controllers about new launched pluggable
8714 transports. Resolves ticket 5609.
8715 - If we're using the pure-C 32-bit curve25519_donna implementation
8716 of curve25519, build it with the -fomit-frame-pointer option to
8717 make it go faster on register-starved hosts. This improves our
8718 handshake performance by about 6% on i386 hosts without nacl.
8720 - Update to the September 4 2013 Maxmind GeoLite Country database.
8723 - Set the listen() backlog limit to the largest actually supported
8724 on the system, not to the value in a header file. Fixes bug 9716;
8725 bugfix on every released Tor.
8726 - No longer accept malformed http headers when parsing urls from
8727 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
8728 bugfix on 0.0.6pre1.
8729 - In munge_extrainfo_into_routerinfo(), check the return value of
8730 memchr(). This would have been a serious issue if we ever passed
8731 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
8733 - On the chance that somebody manages to build Tor on a
8734 platform where time_t is unsigned, correct the way that
8735 microdesc_add_to_cache() handles negative time arguments.
8736 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
8737 - Reject relative control socket paths and emit a warning. Previously,
8738 single-component control socket paths would be rejected, but Tor
8739 would not log why it could not validate the config. Fixes bug 9258;
8740 bugfix on 0.2.3.16-alpha.
8742 o Minor bugfixes (command line):
8743 - Use a single command-line parser for parsing torrc options on the
8744 command line and for finding special command-line options to avoid
8745 inconsistent behavior for torrc option arguments that have the same
8746 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
8748 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
8749 9573; bugfix on 0.0.9pre5.
8751 o Minor fixes (build, auxiliary programs):
8752 - Stop preprocessing the "torify" script with autoconf, since
8753 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
8755 - The tor-fw-helper program now follows the standard convention and
8756 exits with status code "0" on success. Fixes bug 9030; bugfix on
8757 0.2.3.1-alpha. Patch by Arlo Breault.
8758 - Corrected ./configure advice for what openssl dev package you should
8759 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
8761 o Minor code improvements:
8762 - Remove constants and tests for PKCS1 padding; it's insecure and
8763 shouldn't be used for anything new. Fixes bug 8792; patch
8765 - Remove instances of strcpy() from the unit tests. They weren't
8766 hurting anything, since they were only in the unit tests, but it's
8767 embarassing to have strcpy() in the code at all, and some analysis
8768 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
8769 0.2.3.8-alpha. Patch from Arlo Breault.
8772 - Remove migration code from when we renamed the "cached-routers"
8773 file to "cached-descriptors" back in 0.2.0.8-alpha. This
8774 incidentally resolves ticket 6502 by cleaning up the related code
8775 a bit. Patch from Akshay Hebbar.
8777 o Code simplification and refactoring:
8778 - Extract the common duplicated code for creating a subdirectory
8779 of the data directory and writing to a file in it. Fixes ticket
8780 4282; patch from Peter Retzlaff.
8781 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
8782 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
8783 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
8784 - Add a set of accessor functions for the circuit timeout data
8785 structure. Fixes ticket 6153; patch from "piet".
8786 - Clean up exit paths from connection_listener_new(). Closes ticket
8787 8789. Patch from Arlo Breault.
8788 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
8789 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
8790 - Use a doubly-linked list to implement the global circuit list.
8791 Resolves ticket 9108. Patch from Marek Majkowski.
8792 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
8795 Changes in version 0.2.4.17-rc - 2013-09-05
8796 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
8797 series. It adds an emergency step to help us tolerate the massive
8798 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
8799 circuit-level handshakes now effectively jump the queue compared to
8800 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
8801 big bug hindering bridge reachability tests.
8804 - Relays now process the new "NTor" circuit-level handshake requests
8805 with higher priority than the old "TAP" circuit-level handshake
8806 requests. We still process some TAP requests to not totally starve
8807 0.2.3 clients when NTor becomes popular. A new consensus parameter
8808 "NumNTorsPerTAP" lets us tune the balance later if we need to.
8809 Implements ticket 9574.
8812 - If the circuit build timeout logic is disabled (via the consensus,
8813 or because we are an authority), then don't build testing circuits.
8814 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
8815 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
8816 previously they did not, which prevented them from receiving
8817 successful connections from relays for self-test or bandwidth
8818 testing. Also, when a relay is extending a circuit to a bridge,
8819 it needs to send a NETINFO cell, even when the bridge hasn't sent
8820 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
8821 - If the time to download the next old-style networkstatus is in
8822 the future, do not decline to consider whether to download the
8823 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
8827 - Avoid double-closing the listener socket in our socketpair()
8828 replacement (used on Windows) in the case where the addresses on
8829 our opened sockets don't match what we expected. Fixes bug 9400;
8830 bugfix on 0.0.2pre7. Found by Coverity.
8832 o Minor fixes (config options):
8833 - Avoid overflows when the user sets MaxCircuitDirtiness to a
8834 ridiculously high value, by imposing a (ridiculously high) 30-day
8835 maximum on MaxCircuitDirtiness.
8836 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
8837 message is logged at notice, not at info.
8838 - Warn and fail if a server is configured not to advertise any
8839 ORPorts at all. (We need *something* to put in our descriptor,
8840 or we just won't work.)
8843 - Track how many "TAP" and "NTor" circuit handshake requests we get,
8844 and how many we complete, and log it every hour to help relay
8845 operators follow trends in network load. Addresses ticket 9658.
8846 - Update to the August 7 2013 Maxmind GeoLite Country database.
8849 Changes in version 0.2.4.16-rc - 2013-08-10
8850 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
8851 series. It fixes several crash bugs in the 0.2.4 branch.
8854 - Fix a bug in the voting algorithm that could yield incorrect results
8855 when a non-naming authority declared too many flags. Fixes bug 9200;
8856 bugfix on 0.2.0.3-alpha.
8857 - Fix an uninitialized read that could in some cases lead to a remote
8858 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
8859 Anybody running a hidden service on the experimental 0.2.4.x
8860 branch should upgrade. (This is, so far as we know, unrelated to
8862 - Avoid an assertion failure when processing DNS replies without the
8863 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
8864 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
8865 0.2.4.15-rc. Found by stem integration tests.
8868 - Fix an invalid memory read that occured when a pluggable
8869 transport proxy failed its configuration protocol.
8870 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
8871 - When evaluating whether to use a connection that we haven't
8872 decided is canonical using a recent link protocol version,
8873 decide that it's canonical only if it used address _does_
8874 match the desired address. Fixes bug 9309; bugfix on
8875 0.2.4.4-alpha. Reported by skruffy.
8876 - Make the default behavior of NumDirectoryGuards be to track
8877 NumEntryGuards. Now a user who changes only NumEntryGuards will get
8878 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
8879 - Fix a spurious compilation warning with some older versions of
8880 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
8883 - Update to the July 3 2013 Maxmind GeoLite Country database.
8886 Changes in version 0.2.4.15-rc - 2013-07-01
8887 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
8888 series. It fixes a few smaller bugs, but generally appears stable.
8889 Please test it and let us know whether it is!
8892 - When receiving a new configuration file via the control port's
8893 LOADCONF command, do not treat the defaults file as absent.
8894 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
8897 - Issue a warning when running with the bufferevents backend enabled.
8898 It's still not stable, and people should know that they're likely
8899 to hit unexpected problems. Closes ticket 9147.
8902 Changes in version 0.2.4.14-alpha - 2013-06-18
8903 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
8904 present in 0.2.4.13-alpha.
8907 - When we have too much memory queued in circuits (according to a new
8908 MaxMemInCellQueues option), close the circuits consuming the most
8909 memory. This prevents us from running out of memory as a relay if
8910 circuits fill up faster than they can be drained. Fixes bug 9063;
8911 bugfix on the 54th commit of Tor. This bug is a further fix beyond
8912 bug 6252, whose fix was merged into 0.2.3.21-rc.
8914 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
8915 where we tried to solve this issue simply by imposing an upper limit
8916 on the number of queued cells for a single circuit. That approach
8917 proved to be problematic, since there are ways to provoke clients to
8918 send a number of cells in excess of any such reasonable limit. Fixes
8919 bug 9072; bugfix on 0.2.4.13-alpha.
8921 - Limit hidden service descriptors to at most ten introduction
8922 points, to slow one kind of guard enumeration. Fixes bug 9002;
8923 bugfix on 0.1.1.11-alpha.
8926 Changes in version 0.2.4.13-alpha - 2013-06-14
8927 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
8928 vulnerabilities, makes socks5 username/password circuit isolation
8929 actually actually work (this time for sure!), and cleans up a bunch
8930 of other issues in preparation for a release candidate.
8932 o Major bugfixes (robustness):
8933 - Close any circuit that has too many cells queued on it. Fixes
8934 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
8935 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
8936 - Prevent the get_freelists() function from running off the end of
8937 the list of freelists if it somehow gets an unrecognized
8938 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
8940 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
8941 when an exit connection with optimistic data succeeds immediately
8942 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
8944 - Fix a directory authority crash bug when building a consensus
8945 using an older consensus as its basis. Fixes bug 8833. Bugfix
8949 - Avoid a memory leak where we would leak a consensus body when we
8950 find that a consensus which we couldn't previously verify due to
8951 missing certificates is now verifiable. Fixes bug 8719; bugfix
8953 - We used to always request authority certificates by identity digest,
8954 meaning we'd get the newest one even when we wanted one with a
8955 different signing key. Then we would complain about being given
8956 a certificate we already had, and never get the one we really
8957 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
8958 resource to request the one we want. Fixes bug 5595; bugfix on
8960 - Follow the socks5 protocol when offering username/password
8961 authentication. The fix for bug 8117 exposed this bug, and it
8962 turns out real-world applications like Pidgin do care. Bugfix on
8963 0.2.3.2-alpha; fixes bug 8879.
8964 - Prevent failures on Windows Vista and later when rebuilding the
8965 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
8966 bugfix on 0.2.4.12-alpha.
8969 - Fix an impossible buffer overrun in the AES unit tests. Fixes
8970 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
8971 - If for some reason we fail to write a microdescriptor while
8972 rebuilding the cache, do not let the annotations from that
8973 microdescriptor linger in the cache file, and do not let the
8974 microdescriptor stay recorded as present in its old location.
8975 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
8976 - Fix a memory leak that would occur whenever a configuration
8977 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
8978 - Paste the description for PathBias parameters from the man
8979 page into or.h, so the code documents them too. Fixes bug 7982;
8980 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
8981 - Relays now treat a changed IPv6 ORPort as sufficient reason to
8982 publish an updated descriptor. Fixes bug 6026; bugfix on
8984 - When launching a resolve request on behalf of an AF_UNIX control
8985 socket, omit the address field of the new entry connection, used in
8986 subsequent controller events, rather than letting tor_dup_addr()
8987 set it to "<unknown address type>". Fixes bug 8639; bugfix on
8990 o Minor bugfixes (log messages):
8991 - Fix a scaling issue in the path bias accounting code that
8992 resulted in "Bug:" log messages from either
8993 pathbias_scale_close_rates() or pathbias_count_build_success().
8994 This represents a bugfix on a previous bugfix: the original fix
8995 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
8997 - Give a less useless error message when the user asks for an IPv4
8998 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
9002 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
9003 to tolerate bug 8093 for now.
9004 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
9005 in directory authority votes to describe whether they have enough
9006 measured bandwidths to ignore advertised (relay descriptor)
9007 bandwidth claims. Resolves ticket 8711.
9008 - Update to the June 5 2013 Maxmind GeoLite Country database.
9010 o Removed documentation:
9011 - Remove some of the older contents of doc/ as obsolete; move others
9012 to torspec.git. Fixes bug 8965.
9014 o Code simplification and refactoring:
9015 - Avoid using character buffers when constructing most directory
9016 objects: this approach was unwieldy and error-prone. Instead,
9017 build smartlists of strings, and concatenate them when done.
9020 Changes in version 0.2.4.12-alpha - 2013-04-18
9021 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
9022 process for lengthening the guard rotation period, makes directory
9023 authority opinions in the consensus a bit less gameable, makes socks5
9024 username/password circuit isolation actually work, and fixes a wide
9025 variety of other issues.
9028 - Raise the default time that a client keeps an entry guard from
9029 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
9030 2012 paper. (We would make it even longer, but we need better client
9031 load balancing first.) Also, make the guard lifetime controllable
9032 via a new GuardLifetime torrc option and a GuardLifetime consensus
9033 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
9034 - Directory authorities now prefer using measured bandwidths to
9035 advertised ones when computing flags and thresholds. Resolves
9037 - Directory authorities that have more than a threshold number
9038 of relays with measured bandwidths now treat relays with unmeasured
9039 bandwidths as having bandwidth 0. Resolves ticket 8435.
9041 o Major bugfixes (assert / resource use):
9042 - Avoid a bug where our response to TLS renegotiation under certain
9043 network conditions could lead to a busy-loop, with 100% CPU
9044 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
9045 - Avoid an assertion when we discover that we'd like to write a cell
9046 onto a closing connection: just discard the cell. Fixes another
9047 case of bug 7350; bugfix on 0.2.4.4-alpha.
9049 o Major bugfixes (client-side privacy):
9050 - When we mark a circuit as unusable for new circuits, have it
9051 continue to be unusable for new circuits even if MaxCircuitDirtiness
9052 is increased too much at the wrong time, or the system clock jumps
9053 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
9054 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
9055 which have resolved to internal addresses") is set, apply that
9056 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
9057 - When an exit relay rejects a stream with reason "exit policy", but
9058 we only know an exit policy summary (e.g. from the microdesc
9059 consensus) for it, do not mark the relay as useless for all exiting.
9060 Instead, mark just the circuit as unsuitable for that particular
9061 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
9062 - Allow applications to get proper stream isolation with
9063 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
9064 username/password authentication also offer "no authentication". Tor
9065 had previously preferred "no authentication", so the applications
9066 never actually sent Tor their auth details. Now Tor selects
9067 username/password authentication if it's offered. You can disable
9068 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
9069 bug 8117; bugfix on 0.2.3.3-alpha.
9071 o Major bugfixes (other):
9072 - When unable to find any working directory nodes to use as a
9073 directory guard, give up rather than adding the same non-working
9074 nodes to the directory guard list over and over. Fixes bug 8231;
9075 bugfix on 0.2.4.8-alpha.
9078 - Reject as invalid most directory objects containing a NUL.
9079 Belt-and-suspender fix for bug 8037.
9080 - In our testsuite, create temporary directories with a bit more
9081 entropy in their name to make name collisions less likely. Fixes
9083 - Add CACHED keyword to ADDRMAP events in the control protocol
9084 to indicate whether a DNS result will be cached or not. Resolves
9086 - Update to the April 3 2013 Maxmind GeoLite Country database.
9088 o Minor features (build):
9089 - Detect and reject attempts to build Tor with threading support
9090 when OpenSSL has been compiled without threading support.
9092 - Clarify that when autoconf is checking for nacl, it is checking
9093 specifically for nacl with a fast curve25519 implementation.
9095 - Warn if building on a platform with an unsigned time_t: there
9096 are too many places where Tor currently assumes that time_t can
9097 hold negative values. We'd like to fix them all, but probably
9100 o Minor bugfixes (build):
9101 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
9102 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
9103 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
9104 - Add the old src/or/micro-revision.i filename to CLEANFILES.
9105 On the off chance that somebody has one, it will go away as soon
9106 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
9107 - Build Tor correctly on 32-bit platforms where the compiler can build
9108 but not run code using the "uint128_t" construction. Fixes bug 8587;
9109 bugfix on 0.2.4.8-alpha.
9110 - Fix compilation warning with some versions of clang that would
9111 prefer the -Wswitch-enum compiler flag to warn about switch
9112 statements with missing enum values, even if those switch
9113 statements have a "default:" statement. Fixes bug 8598; bugfix
9116 o Minor bugfixes (protocol):
9117 - Fix the handling of a TRUNCATE cell when it arrives while the
9118 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
9119 - Fix a misframing issue when reading the version numbers in a
9120 VERSIONS cell. Previously we would recognize [00 01 00 02] as
9121 'version 1, version 2, and version 0x100', when it should have
9122 only included versions 1 and 2. Fixes bug 8059; bugfix on
9123 0.2.0.10-alpha. Reported pseudonymously.
9124 - Make the format and order of STREAM events for DNS lookups
9125 consistent among the various ways to launch DNS lookups. Fixes
9126 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
9127 - Correct our check for which versions of Tor support the EXTEND2
9128 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
9129 later, when support was really added in version 0.2.4.8-alpha.
9130 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
9132 o Minor bugfixes (other):
9133 - Correctly store microdescriptors and extrainfo descriptors with
9134 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
9135 Bug reported by "cypherpunks".
9136 - Increase the width of the field used to remember a connection's
9137 link protocol version to two bytes. Harmless for now, since the
9138 only currently recognized versions are one byte long. Reported
9139 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
9140 - If the state file's path bias counts are invalid (presumably from a
9141 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
9142 additional checks and log messages to the scaling of Path Bias
9143 counts, in case there still are remaining issues with scaling.
9144 Should help resolve bug 8235.
9145 - Eliminate several instances where we use "Nickname=ID" to refer to
9146 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
9147 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
9148 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
9150 o Minor bugfixes (syscalls):
9151 - Always check the return values of functions fcntl() and
9152 setsockopt(). We don't believe these are ever actually failing in
9153 practice, but better safe than sorry. Also, checking these return
9154 values should please analysis tools like Coverity. Patch from
9155 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
9156 - Use direct writes rather than stdio when building microdescriptor
9157 caches, in an attempt to mitigate bug 8031, or at least make it
9160 o Minor bugfixes (config):
9161 - When rejecting a configuration because we were unable to parse a
9162 quoted string, log an actual error message. Fixes bug 7950; bugfix
9164 - Behave correctly when the user disables LearnCircuitBuildTimeout
9165 but doesn't tell us what they would like the timeout to be. Fixes
9166 bug 6304; bugfix on 0.2.2.14-alpha.
9167 - When autodetecting the number of CPUs, use the number of available
9168 CPUs in preference to the number of configured CPUs. Inform the
9169 user if this reduces the number of available CPUs. Fixes bug 8002;
9170 bugfix on 0.2.3.1-alpha.
9171 - Make it an error when you set EntryNodes but disable UseGuardNodes,
9172 since it will (surprisingly to some users) ignore EntryNodes. Fixes
9173 bug 8180; bugfix on 0.2.3.11-alpha.
9174 - Allow TestingTorNetworks to override the 4096-byte minimum for
9175 the Fast threshold. Otherwise they can't bootstrap until they've
9176 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
9177 - Fix some logic errors when the user manually overrides the
9178 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
9181 o Minor bugfixes (log messages to help diagnose bugs):
9182 - If we fail to free a microdescriptor because of bug 7164, log
9183 the filename and line number from which we tried to free it.
9184 - Add another diagnostic to the heartbeat message: track and log
9185 overhead that TLS is adding to the data we write. If this is
9186 high, we are sending too little data to SSL_write at a time.
9187 Diagnostic for bug 7707.
9188 - Add more detail to a log message about relaxed timeouts, to help
9190 - Warn more aggressively when flushing microdescriptors to a
9191 microdescriptor cache fails, in an attempt to mitigate bug 8031,
9192 or at least make it more diagnosable.
9193 - Improve debugging output to help track down bug 8185 ("Bug:
9194 outgoing relay cell has n_chan==NULL. Dropping.")
9195 - Log the purpose of a path-bias testing circuit correctly.
9196 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
9198 o Minor bugfixes (0.2.4.x log messages that were too noisy):
9199 - Don't attempt to relax the timeout of already opened 1-hop circuits.
9200 They might never timeout. This should eliminate some/all cases of
9201 the relaxed timeout log message.
9202 - Use circuit creation time for network liveness evaluation. This
9203 should eliminate warning log messages about liveness caused
9204 by changes in timeout evaluation. Fixes bug 6572; bugfix on
9206 - Reduce a path bias length check from notice to info. The message
9207 is triggered when creating controller circuits. Fixes bug 8196;
9208 bugfix on 0.2.4.8-alpha.
9209 - Fix a path state issue that triggered a notice during relay startup.
9210 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
9211 - Reduce occurrences of warns about circuit purpose in
9212 connection_ap_expire_building(). Fixes bug 8477; bugfix on
9215 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
9216 - If we encounter a write failure on a SOCKS connection before we
9217 finish our SOCKS handshake, don't warn that we closed the
9218 connection before we could send a SOCKS reply. Fixes bug 8427;
9219 bugfix on 0.1.0.1-rc.
9220 - Correctly recognize that [::1] is a loopback address. Fixes
9221 bug 8377; bugfix on 0.2.1.3-alpha.
9222 - Fix a directory authority warn caused when we have a large amount
9223 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
9224 - Don't log inappropriate heartbeat messages when hibernating: a
9225 hibernating node is _expected_ to drop out of the consensus,
9226 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
9227 bugfix on 0.2.3.1-alpha.
9228 - Don't complain about bootstrapping problems while hibernating.
9229 These complaints reflect a general code problem, but not one
9230 with any problematic effects (no connections are actually
9231 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
9233 o Documentation fixes:
9234 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
9235 names match. Fixes bug 7768.
9236 - Make the torify manpage no longer refer to tsocks; torify hasn't
9237 supported tsocks since 0.2.3.14-alpha.
9238 - Make the tor manpage no longer reference tsocks.
9239 - Fix the GeoIPExcludeUnknown documentation to refer to
9240 ExcludeExitNodes rather than the currently nonexistent
9241 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
9244 - The tor-tsocks.conf is no longer distributed or installed. We
9245 recommend that tsocks users use torsocks instead. Resolves
9249 Changes in version 0.2.4.11-alpha - 2013-03-11
9250 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
9251 more robust, makes hidden service authentication work again, and
9252 resolves a DPI fingerprint for Tor's SSL transport.
9254 o Major features (directory authorities):
9255 - Directory authorities now support a new consensus method (17)
9256 where they cap the published bandwidth of servers for which
9257 insufficient bandwidth measurements exist. Fixes part of bug 2286.
9258 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
9259 serve any v2 directory information. Now we can test disabling the
9260 old deprecated v2 directory format, and see whether doing so has
9261 any effect on network load. Begins to fix bug 6783.
9262 - Directory authorities now include inside each vote a statement of
9263 the performance thresholds they used when assigning flags.
9264 Implements ticket 8151.
9266 o Major bugfixes (directory authorities):
9267 - Stop marking every relay as having been down for one hour every
9268 time we restart a directory authority. These artificial downtimes
9269 were messing with our Stable and Guard flag calculations. Fixes
9270 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
9272 o Major bugfixes (hidden services):
9273 - Allow hidden service authentication to succeed again. When we
9274 refactored the hidden service introduction code back
9275 in 0.2.4.1-alpha, we didn't update the code that checks
9276 whether authentication information is present, causing all
9277 authentication checks to return "false". Fix for bug 8207; bugfix
9278 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
9280 o Minor features (relays, bridges):
9281 - Make bridge relays check once a minute for whether their IP
9282 address has changed, rather than only every 15 minutes. Resolves
9284 - Refactor resolve_my_address() so it returns the method by which we
9285 decided our public IP address (explicitly configured, resolved from
9286 explicit hostname, guessed from interfaces, learned by gethostname).
9287 Now we can provide more helpful log messages when a relay guesses
9288 its IP address incorrectly (e.g. due to unexpected lines in
9289 /etc/hosts). Resolves ticket 2267.
9290 - Teach bridge-using clients to avoid 0.2.2 bridges when making
9291 microdescriptor-related dir requests, and only fall back to normal
9292 descriptors if none of their bridges can handle microdescriptors
9293 (as opposed to the fix in ticket 4013, which caused them to fall
9294 back to normal descriptors if *any* of their bridges preferred
9295 them). Resolves ticket 4994.
9296 - Randomize the lifetime of our SSL link certificate, so censors can't
9297 use the static value for filtering Tor flows. Resolves ticket 8443;
9298 related to ticket 4014 which was included in 0.2.2.33.
9299 - Support a new version of the link protocol that allows 4-byte circuit
9300 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
9301 a possible resource exhaustion issue. Closes ticket 7351; implements
9304 o Minor features (portability):
9305 - Tweak the curve25519-donna*.c implementations to tolerate systems
9306 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
9307 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
9308 the signs of types during autoconf. This is better than our old
9309 approach, which didn't work when cross-compiling.
9310 - Detect the sign of enum values, rather than assuming that MSC is the
9311 only compiler where enum types are all signed. Fixes bug 7727;
9312 bugfix on 0.2.4.10-alpha.
9314 o Minor features (other):
9315 - Say "KBytes" rather than "KB" in the man page (for various values
9316 of K), to further reduce confusion about whether Tor counts in
9317 units of memory or fractions of units of memory. Resolves ticket 7054.
9318 - Clear the high bit on curve25519 public keys before passing them to
9319 our backend, in case we ever wind up using a backend that doesn't do
9320 so itself. If we used such a backend, and *didn't* clear the high bit,
9321 we could wind up in a situation where users with such backends would
9322 be distinguishable from users without. Fixes bug 8121; bugfix on
9324 - Update to the March 6 2013 Maxmind GeoLite Country database.
9326 o Minor bugfixes (clients):
9327 - When we receive a RELAY_END cell with the reason DONE, or with no
9328 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
9329 status as "connection refused". Previously we reported these cases
9330 as success but then immediately closed the connection. Fixes bug
9331 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
9332 - Downgrade an assertion in connection_ap_expire_beginning to an
9333 LD_BUG message. The fix for bug 8024 should prevent this message
9334 from displaying, but just in case, a warn that we can diagnose
9335 is better than more assert crashes. Fixes bug 8065; bugfix on
9337 - Lower path use bias thresholds to .80 for notice and .60 for warn.
9338 Also make the rate limiting flags for the path use bias log messages
9339 independent from the original path bias flags. Fixes bug 8161;
9340 bugfix on 0.2.4.10-alpha.
9342 o Minor bugfixes (relays):
9343 - Stop trying to resolve our hostname so often (e.g. every time we
9344 think about doing a directory fetch). Now we reuse the cached
9345 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
9346 and 2410 (bugfix on 0.1.2.2-alpha).
9347 - Stop sending a stray "(null)" in some cases for the server status
9348 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
9350 - When choosing which stream on a formerly stalled circuit to wake
9351 first, make better use of the platform's weak RNG. Previously,
9352 we had been using the % ("modulo") operator to try to generate a
9353 1/N chance of picking each stream, but this behaves badly with
9354 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
9356 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
9357 Irix's random() only return 15 bits; Solaris's random() returns more
9358 bits but its RAND_MAX says it only returns 15, and so on. Motivated
9359 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
9361 o Minor bugfixes (directory authorities):
9362 - Directory authorities now use less space when formatting identical
9363 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
9366 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
9367 - Avoid leaking memory if we fail to compute a consensus signature
9368 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
9369 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
9371 - Fix a memory leak during safe-cookie controller authentication.
9372 Bugfix on 0.2.3.13-alpha.
9373 - Avoid memory leak of IPv6 policy content if we fail to format it into
9374 a router descriptor. Bugfix on 0.2.4.7-alpha.
9376 o Minor bugfixes (other code correctness issues):
9377 - Avoid a crash if we fail to generate an extrainfo descriptor.
9378 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
9380 - When detecting the largest possible file descriptor (in order to
9381 close all file descriptors when launching a new program), actually
9382 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
9383 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
9385 - Fix a copy-and-paste error when adding a missing A1 to a routerset
9386 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
9387 Bugfix on 0.2.4.10-alpha.
9388 - Fix an impossible-to-trigger integer overflow when estimating how
9389 long our onionskin queue would take. (This overflow would require us
9390 to accept 4 million onionskins before processing 100 of them.) Fixes
9391 bug 8210; bugfix on 0.2.4.10-alpha.
9393 o Code simplification and refactoring:
9394 - Add a wrapper function for the common "log a message with a
9398 Changes in version 0.2.4.10-alpha - 2013-02-04
9399 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
9400 certain attacks that flood the network with relays; changes the queue
9401 for circuit create requests from a sized-based limit to a time-based
9402 limit; resumes building with MSVC on Windows; and fixes a wide variety
9405 o Major bugfixes (directory authority):
9406 - When computing directory thresholds, ignore any rejected-as-sybil
9407 nodes during the computation so that they can't influence Fast,
9408 Guard, etc. (We should have done this for proposal 109.) Fixes
9410 - When marking a node as a likely sybil, reset its uptime metrics
9411 to zero, so that it cannot time towards getting marked as Guard,
9412 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
9416 - When a TLS write is partially successful but incomplete, remember
9417 that the flushed part has been flushed, and notice that bytes were
9418 actually written. Reported and fixed pseudonymously. Fixes bug
9419 7708; bugfix on Tor 0.1.0.5-rc.
9420 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
9421 ID: these could be used to create unexpected streams and circuits
9422 which would count as "present" to some parts of Tor but "absent"
9423 to others, leading to zombie circuits and streams or to a bandwidth
9424 denial-of-service. Fixes bug 7889; bugfix on every released version
9425 of Tor. Reported by "oftc_must_be_destroyed".
9426 - Rename all macros in our local copy of queue.h to begin with "TOR_".
9427 This change seems the only good way to permanently prevent conflicts
9428 with queue.h on various operating systems. Fixes bug 8107; bugfix
9431 o Major features (relay):
9432 - Instead of limiting the number of queued onionskins (aka circuit
9433 create requests) to a fixed, hard-to-configure number, we limit
9434 the size of the queue based on how many we expect to be able to
9435 process in a given amount of time. We estimate the time it will
9436 take to process an onionskin based on average processing time
9437 of previous onionskins. Closes ticket 7291. You'll never have to
9438 configure MaxOnionsPending again.
9440 o Major features (portability):
9441 - Resume building correctly with MSVC and Makefile.nmake. This patch
9442 resolves numerous bugs and fixes reported by ultramage, including
9443 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
9444 - Make the ntor and curve25519 code build correctly with MSVC.
9445 Fix on 0.2.4.8-alpha.
9448 - When directory authorities are computing thresholds for flags,
9449 never let the threshold for the Fast flag fall below 4096
9450 bytes. Also, do not consider nodes with extremely low bandwidths
9451 when deciding thresholds for various directory flags. This change
9452 should raise our threshold for Fast relays, possibly in turn
9453 improving overall network performance; see ticket 1854. Resolves
9455 - The Tor client now ignores sub-domain components of a .onion
9456 address. This change makes HTTP "virtual" hosting
9457 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
9458 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
9459 hosted on the same hidden service. Implements proposal 204.
9460 - We compute the overhead from passing onionskins back and forth to
9461 cpuworkers, and report it when dumping statistics in response to
9462 SIGUSR1. Supports ticket 7291.
9464 o Minor features (path selection):
9465 - When deciding whether we have enough descriptors to build circuits,
9466 instead of looking at raw relay counts, look at which fraction
9467 of (bandwidth-weighted) paths we're able to build. This approach
9468 keeps clients from building circuits if their paths are likely to
9469 stand out statistically. The default fraction of paths needed is
9470 taken from the consensus directory; you can override it with the
9471 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
9472 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
9473 and we have GeoIP information, also exclude all nodes with unknown
9474 countries "??" and "A1". This behavior is controlled by the
9475 new GeoIPExcludeUnknown option: you can make such nodes always
9476 excluded with "GeoIPExcludeUnknown 1", and disable the feature
9477 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
9478 gets you the default behavior. Implements feature 7706.
9479 - Path Use Bias: Perform separate accounting for successful circuit
9480 use. Keep separate statistics on stream attempt rates versus stream
9481 success rates for each guard. Provide configurable thresholds to
9482 determine when to emit log messages or disable use of guards that
9483 fail too many stream attempts. Resolves ticket 7802.
9485 o Minor features (log messages):
9486 - When learning a fingerprint for a bridge, log its corresponding
9487 transport type. Implements ticket 7896.
9488 - Improve the log message when "Bug/attack: unexpected sendme cell
9489 from client" occurs, to help us track bug 8093.
9492 - Remove a couple of extraneous semicolons that were upsetting the
9493 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
9494 bugfix on 0.2.2.1-alpha.
9495 - Remove a source of rounding error during path bias count scaling;
9496 don't count cannibalized circuits as used for path bias until we
9497 actually try to use them; and fix a circuit_package_relay_cell()
9498 warning message about n_chan==NULL. Fixes bug 7802.
9499 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
9500 actually link against nacl when we're configured to use it. Fixes
9501 bug 7972; bugfix on 0.2.4.8-alpha.
9502 - Compile correctly with the --disable-curve25519 option. Fixes
9503 bug 8153; bugfix on 0.2.4.8-alpha.
9505 o Build improvements:
9506 - Do not report status verbosely from autogen.sh unless the -v flag
9507 is specified. Fixes issue 4664. Patch from Onizuka.
9508 - Replace all calls to snprintf() outside of src/ext with
9509 tor_snprintf(). Also remove the #define to replace snprintf with
9510 _snprintf on Windows; they have different semantics, and all of
9511 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
9512 - Try to detect if we are ever building on a platform where
9513 memset(...,0,...) does not set the value of a double to 0.0. Such
9514 platforms are permitted by the C standard, though in practice
9515 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
9516 currently support them, but it's better to detect them and fail
9517 than to perform erroneously.
9520 - Stop exporting estimates of v2 and v3 directory traffic shares
9521 in extrainfo documents. They were unneeded and sometimes inaccurate.
9522 Also stop exporting any v2 directory request statistics. Resolves
9524 - Drop support for detecting and warning about versions of Libevent
9525 before 1.3e. Nothing reasonable ships with them any longer;
9526 warning the user about them shouldn't be needed. Resolves ticket
9529 o Code simplifications and refactoring:
9530 - Rename "isin" functions to "contains", for grammar. Resolves
9532 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
9533 with the natural logarithm function from the system libm. Resolves
9537 Changes in version 0.2.4.9-alpha - 2013-01-15
9538 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
9542 - Fix backward compatibility logic when receiving an embedded ntor
9543 handshake tunneled in a CREATE cell. This clears up the "Bug:
9544 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
9548 Changes in version 0.2.4.8-alpha - 2013-01-14
9549 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
9550 risks, adds a new stronger and faster circuit handshake, and offers
9551 stronger and faster link encryption when both sides support it.
9554 - Preliminary support for directory guards (proposal 207): when
9555 possible, clients now use their entry guards for non-anonymous
9556 directory requests. This can help prevent client enumeration. Note
9557 that this behavior only works when we have a usable consensus
9558 directory, and when options about what to download are more or less
9559 standard. In the future we should re-bootstrap from our guards,
9560 rather than re-bootstrapping from the preconfigured list of
9561 directory sources that ships with Tor. Resolves ticket 6526.
9562 - Tor relays and clients now support a better CREATE/EXTEND cell
9563 format, allowing the sender to specify multiple address, identity,
9564 and handshake types. Implements Robert Ransom's proposal 200;
9567 o Major features (new circuit handshake):
9568 - Tor now supports a new circuit extension handshake designed by Ian
9569 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
9570 circuit extension handshake, later called "TAP", was a bit slow
9571 (especially on the relay side), had a fragile security proof, and
9572 used weaker keys than we'd now prefer. The new circuit handshake
9573 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
9574 function, making it significantly more secure than the older
9575 handshake, and significantly faster. Tor can use one of two built-in
9576 pure-C curve25519-donna implementations by Adam Langley, or it
9577 can link against the "nacl" library for a tuned version if present.
9579 The built-in version is very fast for 64-bit systems when building
9580 with GCC. The built-in 32-bit version is still faster than the
9581 old TAP protocol, but using libnacl is better on most such hosts.
9583 Clients don't currently use this protocol by default, since
9584 comparatively few clients support it so far. To try it, set
9585 UseNTorHandshake to 1.
9587 Implements proposal 216; closes ticket 7202.
9589 o Major features (better link encryption):
9590 - Relays can now enable the ECDHE TLS ciphersuites when available
9591 and appropriate. These ciphersuites let us negotiate forward-secure
9592 TLS secret keys more safely and more efficiently than with our
9593 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
9594 public relays prefer the (faster) P224 group, and bridges prefer
9595 the (more common) P256 group; you can override this with the
9598 Enabling these ciphers was a little tricky, since for a long time,
9599 clients had been claiming to support them without actually doing
9600 so, in order to foil fingerprinting. But with the client-side
9601 implementation of proposal 198 in 0.2.3.17-beta, clients can now
9602 match the ciphers from recent Firefox versions *and* list the
9603 ciphers they actually mean, so relays can believe such clients
9604 when they advertise ECDHE support in their TLS ClientHello messages.
9606 This feature requires clients running 0.2.3.17-beta or later,
9607 and requires both sides to be running OpenSSL 1.0.0 or later
9608 with ECC support. OpenSSL 1.0.1, with the compile-time option
9609 "enable-ec_nistp_64_gcc_128", is highly recommended.
9611 Implements the relay side of proposal 198; closes ticket 7200.
9614 - Avoid crashing when, as a relay without IPv6-exit support, a
9615 client insists on getting an IPv6 address or nothing. Fixes bug
9616 7814; bugfix on 0.2.4.7-alpha.
9619 - Improve circuit build timeout handling for hidden services.
9620 In particular: adjust build timeouts more accurately depending
9621 upon the number of hop-RTTs that a particular circuit type
9622 undergoes. Additionally, launch intro circuits in parallel
9623 if they timeout, and take the first one to reply as valid.
9624 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
9625 separate error codes; or at least, don't break for that reason.
9626 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
9627 - Update to the January 2 2013 Maxmind GeoLite Country database.
9629 o Minor features (testing):
9630 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
9631 (P-256) Diffie-Hellman handshakes to src/or/bench.
9632 - Add benchmark functions to test onion handshake performance.
9634 o Minor features (path bias detection):
9635 - Alter the Path Bias log messages to be more descriptive in terms
9636 of reporting timeouts and other statistics.
9637 - Create three levels of Path Bias log messages, as opposed to just
9638 two. These are configurable via consensus as well as via the torrc
9639 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
9640 The default values are 0.70, 0.50, and 0.30 respectively.
9641 - Separate the log message levels from the decision to drop guards,
9642 which also is available via torrc option PathBiasDropGuards.
9643 PathBiasDropGuards still defaults to 0 (off).
9644 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
9645 in combination with PathBiasExtremeRate.
9646 - Increase the default values for PathBiasScaleThreshold and
9647 PathBiasCircThreshold from (200, 20) to (300, 150).
9648 - Add in circuit usage accounting to path bias. If we try to use a
9649 built circuit but fail for any reason, it counts as path bias.
9650 Certain classes of circuits where the adversary gets to pick your
9651 destination node are exempt from this accounting. Usage accounting
9652 can be specifically disabled via consensus parameter or torrc.
9653 - Convert all internal path bias state to double-precision floating
9654 point, to avoid roundoff error and other issues.
9655 - Only record path bias information for circuits that have completed
9656 *two* hops. Assuming end-to-end tagging is the attack vector, this
9657 makes us more resilient to ambient circuit failure without any
9658 detection capability loss.
9660 o Minor bugfixes (log messages):
9661 - Rate-limit the "No circuits are opened. Relaxed timeout for a
9662 circuit with channel state open..." message to once per hour to
9663 keep it from filling the notice logs. Mitigates bug 7799 but does
9664 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
9665 - Avoid spurious warnings when configuring multiple client ports of
9666 which only some are nonlocal. Previously, we had claimed that some
9667 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
9670 o Code simplifications and refactoring:
9671 - Get rid of a couple of harmless clang warnings, where we compared
9672 enums to ints. These warnings are newly introduced in clang 3.2.
9673 - Split the onion.c file into separate modules for the onion queue
9674 and the different handshakes it supports.
9675 - Remove the marshalling/unmarshalling code for sending requests to
9676 cpuworkers over a socket, and instead just send structs. The
9677 recipient will always be the same Tor binary as the sender, so
9678 any encoding is overkill.
9681 Changes in version 0.2.4.7-alpha - 2012-12-24
9682 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
9683 directory mirrors for more robust bootstrapping; fixes more issues where
9684 clients with changing network conditions refuse to make any circuits;
9685 adds initial support for exiting to IPv6 addresses; resumes being able
9686 to update our GeoIP database, and includes the geoip6 file this time;
9687 turns off the client-side DNS cache by default due to privacy risks;
9688 and fixes a variety of other issues.
9690 o Major features (client resilience):
9691 - Add a new "FallbackDir" torrc option to use when we can't use
9692 a directory mirror from the consensus (either because we lack a
9693 consensus, or because they're all down). Currently, all authorities
9694 are fallbacks by default, and there are no other default fallbacks,
9695 but that will change. This option will allow us to give clients a
9696 longer list of servers to try to get a consensus from when first
9697 connecting to the Tor network, and thereby reduce load on the
9698 directory authorities. Implements proposal 206, "Preconfigured
9699 directory sources for bootstrapping". We also removed the old
9700 "FallbackNetworkstatus" option, since we never got it working well
9701 enough to use it. Closes bug 572.
9702 - If we have no circuits open, use a relaxed timeout (the
9703 95-percentile cutoff) until a circuit succeeds. This heuristic
9704 should allow Tor to succeed at building circuits even when the
9705 network connection drastically changes. Should help with bug 3443.
9707 o Major features (IPv6):
9708 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
9709 connectivity, then set the IPv6Exit flag to 1. Also make sure your
9710 exit policy reads as you would like: the address * applies to all
9711 address families, whereas *4 is IPv4 address only, and *6 is IPv6
9712 addresses only. On the client side, you'll need to wait until the
9713 authorities have upgraded, wait for enough exits to support IPv6,
9714 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
9715 ticket 5547, implements proposal 117 as revised in proposal 208.
9717 We DO NOT recommend that clients with actual anonymity needs start
9718 using IPv6 over Tor yet, since not enough exits support it yet.
9720 o Major features (geoip database):
9721 - Maxmind began labelling Tor relays as being in country "A1",
9722 which breaks by-country node selection inside Tor. Now we use a
9723 script to replace "A1" ("Anonymous Proxy") entries in our geoip
9724 file with real country codes. This script fixes about 90% of "A1"
9725 entries automatically and uses manual country code assignments to
9726 fix the remaining 10%. See src/config/README.geoip for details.
9727 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
9728 Country database, as modified above.
9730 o Major bugfixes (client-side DNS):
9731 - Turn off the client-side DNS cache by default. Updating and using
9732 the DNS cache is now configurable on a per-client-port
9733 level. SOCKSPort, DNSPort, etc lines may now contain
9734 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
9735 cache these types of DNS answers when we receive them from an
9736 exit node in response to an application request on this port, and
9737 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
9738 cached DNS answers of these types, we shouldn't use them. It's
9739 potentially risky to use cached DNS answers at the client, since
9740 doing so can indicate to one exit what answers we've gotten
9741 for DNS lookups in the past. With IPv6, this becomes especially
9742 problematic. Using cached DNS answers for requests on the same
9743 circuit would present less linkability risk, since all traffic
9744 on a circuit is already linkable, but it would also provide
9745 little performance benefit: the exit node caches DNS replies
9746 too. Implements a simplified version of Proposal 205. Implements
9749 o Major bugfixes (other):
9750 - Alter circuit build timeout measurement to start at the point
9751 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
9752 initialization). This should make our timeout measurements more
9753 uniform. Previously, we were sometimes including ORconn setup time
9754 in our circuit build time measurements. Should resolve bug 3443.
9755 - Fix an assertion that could trigger in hibernate_go_dormant() when
9756 closing an or_connection_t: call channel_mark_for_close() rather
9757 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
9759 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
9760 7655; bugfix on 0.2.4.6-alpha.
9763 - Add a new torrc option "ServerTransportListenAddr" to let bridge
9764 operators select the address where their pluggable transports will
9765 listen for connections. Resolves ticket 7013.
9766 - Allow an optional $ before the node identity digest in the
9767 controller command GETINFO ns/id/<identity>, for consistency with
9768 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
9769 - Log packaged cell fullness as part of the heartbeat message.
9770 Diagnosis to try to determine the extent of bug 7743.
9772 o Minor features (IPv6):
9773 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
9774 prefer to hand out virtual IPv6 addresses, since there are more of
9775 them and we can't run out. To override this behavior and make IPv4
9776 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
9777 or DNSPort you're using for resolving. Implements ticket 7571.
9778 - AutomapHostsOnResolve responses are now randomized, to avoid
9779 annoying situations where Tor is restarted and applications
9780 connect to the wrong addresses.
9781 - Never try more than 1000 times to pick a new virtual address when
9782 AutomapHostsOnResolve is set. That's good enough so long as we
9783 aren't close to handing out our entire virtual address space;
9784 if you're getting there, it's best to switch to IPv6 virtual
9788 - The ADDRMAP command can no longer generate an ill-formed error
9789 code on a failed MAPADDRESS. It now says "internal" rather than
9790 an English sentence fragment with spaces in the middle. Bugfix on
9792 - Fix log messages and comments to avoid saying "GMT" when we mean
9793 "UTC". Fixes bug 6113.
9794 - Compile on win64 using mingw64. Fixes bug 7260; patches from
9796 - Fix a crash when debugging unit tests on Windows: deallocate a
9797 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
9798 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
9801 - The DirServer option is now DirAuthority, for consistency with
9802 current naming patterns. You can still use the old DirServer form.
9804 o Code simplification and refactoring:
9805 - Move the client-side address-map/virtual-address/DNS-cache code
9806 out of connection_edge.c into a new addressmap.c module.
9807 - Remove unused code for parsing v1 directories and "running routers"
9808 documents. Fixes bug 6887.
9811 Changes in version 0.2.3.25 - 2012-11-19
9812 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
9813 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
9814 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
9815 programmer, and friend. Unstinting in his dedication to the cause of
9816 freedom, he inspired and helped many of us as we began our work on
9817 anonymity, and inspires us still. Please honor his memory by writing
9818 software to protect people's freedoms, and by helping others to do so.
9820 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
9821 significantly reduced directory overhead (via microdescriptors),
9822 enormous crypto performance improvements for fast relays on new
9823 enough hardware, a new v3 TLS handshake protocol that can better
9824 resist fingerprinting, support for protocol obfuscation plugins (aka
9825 pluggable transports), better scalability for hidden services, IPv6
9826 support for bridges, performance improvements like allowing clients
9827 to skip the first round-trip on the circuit ("optimistic data") and
9828 refilling token buckets more often, a new "stream isolation" design
9829 to isolate different applications on different circuits, and many
9830 stability, security, and privacy fixes.
9833 - Tor tries to wipe potentially sensitive data after using it, so
9834 that if some subsequent security failure exposes Tor's memory,
9835 the damage will be limited. But we had a bug where the compiler
9836 was eliminating these wipe operations when it decided that the
9837 memory was no longer visible to a (correctly running) program,
9838 hence defeating our attempt at defense in depth. We fix that
9839 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
9840 is unlikely to optimize away. Future versions of Tor may use
9841 a less ridiculously heavy approach for this. Fixes bug 7352.
9842 Reported in an article by Andrey Karpov.
9845 - Fix a harmless bug when opting against publishing a relay descriptor
9846 because DisableNetwork is set. Fixes bug 7464; bugfix on
9850 Changes in version 0.2.4.6-alpha - 2012-11-13
9851 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
9852 makes our defense-in-depth memory wiping more reliable, and begins to
9853 count IPv6 addresses in bridge statistics,
9856 - Fix an assertion failure that could occur when closing a connection
9857 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
9859 - Tor tries to wipe potentially sensitive data after using it, so
9860 that if some subsequent security failure exposes Tor's memory,
9861 the damage will be limited. But we had a bug where the compiler
9862 was eliminating these wipe operations when it decided that the
9863 memory was no longer visible to a (correctly running) program,
9864 hence defeating our attempt at defense in depth. We fix that
9865 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
9866 is unlikely to optimize away. Future versions of Tor may use
9867 a less ridiculously heavy approach for this. Fixes bug 7352.
9868 Reported in an article by Andrey Karpov.
9871 - Add GeoIP database for IPv6 addresses. The new config option
9873 - Bridge statistics now count bridge clients connecting over IPv6:
9874 bridge statistics files now list "bridge-ip-versions" and
9875 extra-info documents list "geoip6-db-digest". The control protocol
9876 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
9877 implementation by "shkoo", addressing ticket 5055.
9880 - Warn when we are binding low ports when hibernation is enabled;
9881 previously we had warned when we were _advertising_ low ports with
9882 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
9883 - Fix a harmless bug when opting against publishing a relay descriptor
9884 because DisableNetwork is set. Fixes bug 7464; bugfix on
9886 - Add warning message when a managed proxy dies during configuration.
9887 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
9888 - Fix a linking error when building tor-fw-helper without miniupnp.
9889 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
9890 - Check for closing an or_connection_t without going through correct
9891 channel functions; emit a warning and then call
9892 connection_or_close_for_error() so we don't assert as in bugs 7212
9894 - Compile correctly on compilers without C99 designated initializer
9895 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
9896 - Avoid a possible assert that can occur when channel_send_destroy() is
9897 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
9898 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
9899 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
9900 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
9901 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
9903 o Code simplification and refactoring:
9904 - Start using OpenBSD's implementation of queue.h, so that we don't
9905 need to hand-roll our own pointer and list structures whenever we
9906 need them. (We can't rely on a sys/queue.h, since some operating
9907 systems don't have them, and the ones that do have them don't all
9908 present the same extensions.)
9911 Changes in version 0.2.4.5-alpha - 2012-10-25
9912 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
9913 two important security vulnerabilities that could lead to remotely
9914 triggerable relay crashes, fix a major bug that was preventing clients
9915 from choosing suitable exit nodes, and refactor some of our code.
9917 o Major bugfixes (security, also in 0.2.3.24-rc):
9918 - Fix a group of remotely triggerable assertion failures related to
9919 incorrect link protocol negotiation. Found, diagnosed, and fixed
9920 by "some guy from France". Fix for CVE-2012-2250; bugfix on
9922 - Fix a denial of service attack by which any directory authority
9923 could crash all the others, or by which a single v2 directory
9924 authority could crash everybody downloading v2 directory
9925 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
9927 o Major bugfixes (also in 0.2.3.24-rc):
9928 - When parsing exit policy summaries from microdescriptors, we had
9929 previously been ignoring the last character in each one, so that
9930 "accept 80,443,8080" would be treated by clients as indicating
9931 a node that allows access to ports 80, 443, and 808. That would
9932 lead to clients attempting connections that could never work,
9933 and ignoring exit nodes that would support their connections. Now
9934 clients parse these exit policy summaries correctly. Fixes bug 7192;
9935 bugfix on 0.2.3.1-alpha.
9937 o Minor bugfixes (also in 0.2.3.24-rc):
9938 - Clients now consider the ClientRejectInternalAddresses config option
9939 when using a microdescriptor consensus stanza to decide whether
9940 an exit relay would allow exiting to an internal address. Fixes
9941 bug 7190; bugfix on 0.2.3.1-alpha.
9944 - Only disable TLS session ticket support when running as a TLS
9945 server. Now clients will blend better with regular Firefox
9946 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
9948 o Code simplification and refactoring:
9949 - Start using OpenBSD's implementation of queue.h (originally by
9951 - Move the entry node code from circuitbuild.c to its own file.
9952 - Move the circuit build timeout tracking code from circuitbuild.c
9956 Changes in version 0.2.3.24-rc - 2012-10-25
9957 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
9958 could lead to remotely triggerable relay crashes, and fixes
9959 a major bug that was preventing clients from choosing suitable exit
9962 o Major bugfixes (security):
9963 - Fix a group of remotely triggerable assertion failures related to
9964 incorrect link protocol negotiation. Found, diagnosed, and fixed
9965 by "some guy from France". Fix for CVE-2012-2250; bugfix on
9967 - Fix a denial of service attack by which any directory authority
9968 could crash all the others, or by which a single v2 directory
9969 authority could crash everybody downloading v2 directory
9970 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
9973 - When parsing exit policy summaries from microdescriptors, we had
9974 previously been ignoring the last character in each one, so that
9975 "accept 80,443,8080" would be treated by clients as indicating
9976 a node that allows access to ports 80, 443, and 808. That would
9977 lead to clients attempting connections that could never work,
9978 and ignoring exit nodes that would support their connections. Now
9979 clients parse these exit policy summaries correctly. Fixes bug 7192;
9980 bugfix on 0.2.3.1-alpha.
9983 - Clients now consider the ClientRejectInternalAddresses config option
9984 when using a microdescriptor consensus stanza to decide whether
9985 an exit relay would allow exiting to an internal address. Fixes
9986 bug 7190; bugfix on 0.2.3.1-alpha.
9989 Changes in version 0.2.4.4-alpha - 2012-10-20
9990 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
9991 vulnerability introduced by a change in OpenSSL, fixes a remotely
9992 triggerable assert, and adds new channel_t and circuitmux_t abstractions
9993 that will make it easier to test new connection transport and cell
9994 scheduling algorithms.
9996 o New directory authorities (also in 0.2.3.23-rc):
9997 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
9998 authority. Closes ticket 5749.
10000 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
10001 - Disable TLS session tickets. OpenSSL's implementation was giving
10002 our TLS session keys the lifetime of our TLS context objects, when
10003 perfect forward secrecy would want us to discard anything that
10004 could decrypt a link connection as soon as the link connection
10005 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
10006 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
10007 - Discard extraneous renegotiation attempts once the V3 link
10008 protocol has been initiated. Failure to do so left us open to
10009 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
10010 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
10012 o Internal abstraction features:
10013 - Introduce new channel_t abstraction between circuits and
10014 or_connection_t to allow for implementing alternate OR-to-OR
10015 transports. A channel_t is an abstract object which can either be a
10016 cell-bearing channel, which is responsible for authenticating and
10017 handshaking with the remote OR and transmitting cells to and from
10018 it, or a listening channel, which spawns new cell-bearing channels
10019 at the request of remote ORs. Implements part of ticket 6465.
10020 - Also new is the channel_tls_t subclass of channel_t, adapting it
10021 to the existing or_connection_t code. The V2/V3 protocol handshaking
10022 code which formerly resided in command.c has been moved below the
10023 channel_t abstraction layer and may be found in channeltls.c now.
10024 Implements the rest of ticket 6465.
10025 - Introduce new circuitmux_t storing the queue of circuits for
10026 a channel; this encapsulates and abstracts the queue logic and
10027 circuit selection policy, and allows the latter to be overridden
10028 easily by switching out a policy object. The existing EWMA behavior
10029 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
10031 o Required libraries:
10032 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
10033 strongly recommended.
10036 - Warn users who run hidden services on a Tor client with
10037 UseEntryGuards disabled that their hidden services will be
10038 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
10039 attack which motivated Tor to support entry guards in the first
10040 place). Resolves ticket 6889.
10041 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
10042 dhill. Resolves ticket 6982.
10043 - Option OutboundBindAddress can be specified multiple times and
10044 accepts IPv6 addresses. Resolves ticket 6876.
10046 o Minor bugfixes (also in 0.2.3.23-rc):
10047 - Don't serve or accept v2 hidden service descriptors over a
10048 relay's DirPort. It's never correct to do so, and disabling it
10049 might make it more annoying to exploit any bugs that turn up in the
10050 descriptor-parsing code. Fixes bug 7149.
10051 - Fix two cases in src/or/transports.c where we were calling
10052 fmt_addr() twice in a parameter list. Bug found by David
10053 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
10054 - Fix memory leaks whenever we logged any message about the "path
10055 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
10056 - When relays refuse a "create" cell because their queue of pending
10057 create cells is too big (typically because their cpu can't keep up
10058 with the arrival rate), send back reason "resource limit" rather
10059 than reason "internal", so network measurement scripts can get a
10060 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
10063 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
10064 - Free some more still-in-use memory at exit, to make hunting for
10065 memory leaks easier. Resolves bug 7029.
10066 - When a Tor client gets a "truncated" relay cell, the first byte of
10067 its payload specifies why the circuit was truncated. We were
10068 ignoring this 'reason' byte when tearing down the circuit, resulting
10069 in the controller not being told why the circuit closed. Now we
10070 pass the reason from the truncated cell to the controller. Bugfix
10071 on 0.1.2.3-alpha; fixes bug 7039.
10072 - Downgrade "Failed to hand off onionskin" messages to "debug"
10073 severity, since they're typically redundant with the "Your computer
10074 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
10075 - Make clients running with IPv6 bridges connect over IPv6 again,
10076 even without setting new config options ClientUseIPv6 and
10077 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
10078 - Use square brackets around IPv6 addresses in numerous places
10079 that needed them, including log messages, HTTPS CONNECT proxy
10080 requests, TransportProxy statefile entries, and pluggable transport
10081 extra-info lines. Fixes bug 7011; patch by David Fifield.
10083 o Code refactoring and cleanup:
10084 - Source files taken from other packages now reside in src/ext;
10085 previously they were scattered around the rest of Tor.
10086 - Avoid use of reserved identifiers in our C code. The C standard
10087 doesn't like us declaring anything that starts with an
10088 underscore, so let's knock it off before we get in trouble. Fix
10089 for bug 1031; bugfix on the first Tor commit.
10092 Changes in version 0.2.3.23-rc - 2012-10-20
10093 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
10094 vulnerability introduced by a change in OpenSSL, and fixes a variety
10095 of smaller bugs in preparation for the release.
10097 o New directory authorities:
10098 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
10099 authority. Closes ticket 5749.
10101 o Major bugfixes (security/privacy):
10102 - Disable TLS session tickets. OpenSSL's implementation was giving
10103 our TLS session keys the lifetime of our TLS context objects, when
10104 perfect forward secrecy would want us to discard anything that
10105 could decrypt a link connection as soon as the link connection
10106 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
10107 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
10108 - Discard extraneous renegotiation attempts once the V3 link
10109 protocol has been initiated. Failure to do so left us open to
10110 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
10111 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
10114 - Fix a possible crash bug when checking for deactivated circuits
10115 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
10116 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
10118 o Minor bugfixes (on 0.2.3.x):
10119 - Fix two cases in src/or/transports.c where we were calling
10120 fmt_addr() twice in a parameter list. Bug found by David
10121 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
10122 - Convert an assert in the pathbias code to a log message. The assert
10123 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
10124 bugfix on 0.2.3.17-beta.
10125 - Fix memory leaks whenever we logged any message about the "path
10126 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
10128 o Minor bugfixes (on 0.2.2.x and earlier):
10129 - Don't serve or accept v2 hidden service descriptors over a relay's
10130 DirPort. It's never correct to do so, and disabling it might
10131 make it more annoying to exploit any bugs that turn up in the
10132 descriptor-parsing code. Fixes bug 7149.
10133 - When relays refuse a "create" cell because their queue of pending
10134 create cells is too big (typically because their cpu can't keep up
10135 with the arrival rate), send back reason "resource limit" rather
10136 than reason "internal", so network measurement scripts can get a
10137 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
10138 - Correct file sizes when reading binary files on Cygwin, to avoid
10139 a bug where Tor would fail to read its state file. Fixes bug 6844;
10140 bugfix on 0.1.2.7-alpha.
10141 - Avoid undefined behavior when parsing the list of supported
10142 rendezvous/introduction protocols in a hidden service descriptor.
10143 Previously, Tor would have confused (as-yet-unused) protocol version
10144 numbers greater than 32 with lower ones on many platforms. Fixes
10145 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
10147 o Documentation fixes:
10148 - Clarify that hidden services are TCP only. Fixes bug 6024.
10151 Changes in version 0.2.4.3-alpha - 2012-09-22
10152 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
10153 assertion, resumes letting relays test reachability of their DirPort,
10154 and cleans up a bunch of smaller bugs.
10157 - Fix an assertion failure in tor_timegm() that could be triggered
10158 by a badly formatted directory object. Bug found by fuzzing with
10159 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
10162 - Fix a possible crash bug when checking for deactivated circuits
10163 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
10164 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
10165 - Allow routers to detect that their own DirPorts are running. When
10166 we removed support for versions_supports_begindir, we also
10167 accidentally removed the mechanism we used to self-test our
10168 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
10169 bugfix on 0.2.4.2-alpha.
10171 o Security features:
10172 - Switch to a completely time-invariant approach for picking nodes
10173 weighted by bandwidth. Our old approach would run through the
10174 part of the loop after it had made its choice slightly slower
10175 than it ran through the part of the loop before it had made its
10176 choice. Addresses ticket 6538.
10177 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
10178 by tor2web clients allows hidden services to identify tor2web
10179 clients through their repeated selection of the same rendezvous
10180 and introduction point circuit endpoints (their guards). Resolves
10184 - Enable Tor to read configuration, state, and key information from
10185 a FIFO. Previously Tor would only read from files with a positive
10186 stat.st_size. Code from meejah; fixes bug 6044.
10189 - Correct file sizes when reading binary files on Cygwin, to avoid
10190 a bug where Tor would fail to read its state file. Fixes bug 6844;
10191 bugfix on 0.1.2.7-alpha.
10192 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
10193 bugfix on 0.2.0.3-alpha.
10194 - When complaining about a client port on a public address, log
10195 which address we're complaining about. Fixes bug 4020; bugfix on
10196 0.2.3.3-alpha. Patch by Tom Fitzhenry.
10197 - Convert an assert in the pathbias code to a log message. The assert
10198 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
10199 bugfix on 0.2.3.17-beta.
10200 - Our new buildsystem was overzealous about rebuilding manpages: it
10201 would rebuild them all whenever any one of them changed. Now our
10202 dependency checking should be correct. Fixes bug 6843; bugfix on
10204 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
10205 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
10206 - Correct log printout about which address family is preferred
10207 when connecting to a bridge with both an IPv4 and IPv6 OR port.
10208 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
10210 o Minor bugfixes (code cleanliness):
10211 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
10212 with large values. This situation was untriggered, but nevertheless
10213 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
10214 - Reject consensus votes with more than 64 known-flags. We aren't even
10215 close to that limit yet, and our code doesn't handle it correctly.
10216 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
10217 - Avoid undefined behavior when parsing the list of supported
10218 rendezvous/introduction protocols in a hidden service descriptor.
10219 Previously, Tor would have confused (as-yet-unused) protocol version
10220 numbers greater than 32 with lower ones on many platforms. Fixes
10221 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
10222 - Fix handling of rendezvous client authorization types over 8.
10223 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
10224 - Fix building with older versions of GCC (2.95, for one) that don't
10225 like preprocessor directives inside macro arguments. Found by
10226 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
10227 - Switch weighted node selection rule from using a list of doubles
10228 to using a list of int64_t. This change should make the process
10229 slightly easier to debug and maintain. Needed to finish ticket 6538.
10231 o Code simplification and refactoring:
10232 - Move the generic "config" code into a new file, and have "config.c"
10233 hold only torrc- and state-related code. Resolves ticket 6823.
10234 - Move the core of our "choose a weighted element at random" logic
10235 into its own function, and give it unit tests. Now the logic is
10236 testable, and a little less fragile too.
10237 - Removed the testing_since field of node_t, which hasn't been used
10238 for anything since 0.2.0.9-alpha.
10240 o Documentation fixes:
10241 - Clarify that hidden services are TCP only. Fixes bug 6024.
10242 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
10246 Changes in version 0.2.3.22-rc - 2012-09-11
10247 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
10251 - Fix an assertion failure in tor_timegm() that could be triggered
10252 by a badly formatted directory object. Bug found by fuzzing with
10253 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
10256 - Avoid segfault when starting up having run with an extremely old
10257 version of Tor and parsing its state file. Fixes bug 6801; bugfix
10261 Changes in version 0.2.2.39 - 2012-09-11
10262 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
10266 - Fix an assertion failure in tor_timegm() that could be triggered
10267 by a badly formatted directory object. Bug found by fuzzing with
10268 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
10269 - Do not crash when comparing an address with port value 0 to an
10270 address policy. This bug could have been used to cause a remote
10271 assertion failure by or against directory authorities, or to
10272 allow some applications to crash clients. Fixes bug 6690; bugfix
10276 Changes in version 0.2.4.2-alpha - 2012-09-10
10277 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
10278 raises the default rate limiting even more, and makes the bootstrapping
10279 log messages less noisy.
10282 - Automatically forward the TCP ports of pluggable transport
10283 proxies using tor-fw-helper if PortForwarding is enabled. Implements
10287 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
10288 to 1GB/1GB. The previous defaults were intended to be "basically
10289 infinite", but it turns out they're now limiting our 100mbit+
10290 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
10291 last time we raised it).
10294 - Detect when we're running with a version of OpenSSL other than the
10295 one we compiled with. This has occasionally given people hard-to-
10297 - Log fewer lines at level "notice" about our OpenSSL and Libevent
10298 versions and capabilities when everything is going right. Resolves
10299 part of ticket 6736.
10300 - Directory authorities no long accept descriptors for any version of
10301 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
10302 These versions are insecure, unsupported, or both. Implements
10306 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
10307 to start with a triple-underscore so the controller won't touch it.
10308 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
10309 - Avoid segfault when starting up having run with an extremely old
10310 version of Tor and parsing its state file. Fixes bug 6801; bugfix
10312 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
10313 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
10314 - Don't follow the NULL pointer if microdescriptor generation fails.
10315 (This does not appear to be triggerable, but it's best to be safe.)
10316 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
10317 - Fix mis-declared dependencies on src/common/crypto.c and
10318 src/or/tor_main.c that could break out-of-tree builds under some
10319 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
10320 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
10321 6778; bugfix on 0.2.4.1-alpha.
10322 - Fix a harmless (in this case) build warning for implicitly
10323 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
10325 o Removed features:
10326 - Now that all versions before 0.2.2.x are disallowed, we no longer
10327 need to work around their missing features. Thus we can remove a
10328 bunch of compatibility code.
10330 o Code refactoring:
10331 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
10332 TCP ports to forward. In the past it only accepted two ports:
10333 the ORPort and the DirPort.
10336 Changes in version 0.2.4.1-alpha - 2012-09-05
10337 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
10338 bridgedb; lets relays use IPv6 addresses and directory authorities
10339 advertise them; and switches to a cleaner build interface.
10341 This is the first alpha release in a new series, so expect there to
10342 be bugs. Users who would rather test out a more stable branch should
10343 stay with 0.2.3.x for now.
10345 o Major features (bridges):
10346 - Bridges now report the pluggable transports they support to the
10347 bridge authority, so it can pass the supported transports on to
10348 bridgedb and/or eventually do reachability testing. Implements
10351 o Major features (IPv6):
10352 - Bridge authorities now accept IPv6 bridge addresses and include
10353 them in network status documents. Implements ticket 5534.
10354 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
10355 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
10356 to happen. Implements ticket 5535.
10357 - All kind of relays, not just bridges, can now advertise an IPv6
10358 OR port. Implements ticket 6362.
10359 - Directory authorities vote on IPv6 OR ports using the new consensus
10360 method 14. Implements ticket 6363.
10362 o Major features (build):
10363 - Switch to a nonrecursive Makefile structure. Now instead of each
10364 Makefile.am invoking other Makefile.am's, there is a master
10365 Makefile.am that includes the others. This change makes our build
10366 process slightly more maintainable, and improves parallelism for
10367 building with make -j. Original patch by Stewart Smith; various
10368 fixes by Jim Meyering.
10369 - Where available, we now use automake's "silent" make rules by
10370 default, so that warnings are easier to spot. You can get the old
10371 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
10373 o Minor features (code security and spec conformance):
10374 - Clear keys and key-derived material left on the stack in
10375 rendservice.c and rendclient.c. Check return value of
10376 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
10377 These fixes should make us more forward-secure against cold-boot
10378 attacks and the like. Fixes bug 2385.
10379 - Reject EXTEND cells sent to nonexistent streams. According to the
10380 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
10381 we were only checking for stream IDs that were currently in use.
10382 Found while hunting for more instances of bug 6271. Bugfix on
10383 0.0.2pre8, which introduced incremental circuit construction.
10385 o Minor features (streamlining);
10386 - No longer include the "opt" prefix when generating routerinfos
10387 or v2 directories: it has been needless since Tor 0.1.2. Closes
10389 - Remove some now-needless code that tried to aggressively flush
10390 OR connections as data was added to them. Since 0.2.0.1-alpha, our
10391 cell queue logic has saved us from the failure mode that this code
10392 was supposed to prevent. Removing this code will limit the number
10393 of baroque control flow paths through Tor's network logic. Reported
10394 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
10396 o Minor features (controller):
10397 - Add a "GETINFO signal/names" control port command. Implements
10399 - Provide default values for all options via "GETINFO config/defaults".
10400 Implements ticket 4971.
10402 o Minor features (IPv6):
10403 - New config option "AuthDirHasIPv6Connectivity 1" that directory
10404 authorities should set if they have IPv6 connectivity and want to
10405 do reachability tests for IPv6 relays. Implements feature 5974.
10406 - A relay with an IPv6 OR port now sends that address in NETINFO
10407 cells (in addition to its other address). Implements ticket 6364.
10409 o Minor features (log messages):
10410 - Omit the first heartbeat log message, because it never has anything
10411 useful to say, and it clutters up the bootstrapping messages.
10412 Resolves ticket 6758.
10413 - Don't log about reloading the microdescriptor cache at startup. Our
10414 bootstrap warnings are supposed to tell the user when there's a
10415 problem, and our bootstrap notices say when there isn't. Resolves
10416 ticket 6759; bugfix on 0.2.2.6-alpha.
10417 - Don't log "I learned some more directory information" when we're
10418 reading cached directory information. Reserve it for when new
10419 directory information arrives in response to a fetch. Resolves
10421 - Prevent rounding error in path bias counts when scaling
10422 them down, and use the correct scale factor default. Also demote
10423 some path bias related log messages down a level and make others
10424 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
10425 - We no longer warn so much when generating manpages from their
10428 o Code simplifications and refactoring:
10429 - Enhance our internal sscanf replacement so that we can eliminate
10430 the last remaining uses of the system sscanf. (Though those uses
10431 of sscanf were safe, sscanf itself is generally error prone, so
10432 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
10434 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
10435 - Move last_reachable and testing_since from routerinfo_t to node_t.
10436 Implements ticket 5529.
10437 - Add replaycache_t structure, functions and unit tests, then refactor
10438 rend_service_introduce() to be more clear to read, improve, debug,
10439 and test. Resolves bug 6177.
10440 - Finally remove support for malloc_good_size and malloc_usable_size.
10441 We had hoped that these functions would let us eke a little more
10442 memory out of our malloc implementation. Unfortunately, the only
10443 implementations that provided these functions are also ones that
10444 are already efficient about not overallocation: they never got us
10445 more than 7 or so bytes per allocation. Removing them saves us a
10446 little code complexity and a nontrivial amount of build complexity.
10448 o New requirements:
10449 - Tor maintainers now require Automake version 1.9 or later to build
10450 Tor from the Git repository. (Automake is not required when building
10451 from a source distribution.)
10454 Changes in version 0.2.3.21-rc - 2012-09-05
10455 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
10456 series. It fixes a trio of potential security bugs, fixes a bug where
10457 we were leaving some of the fast relays out of the microdescriptor
10458 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
10459 and cleans up other smaller issues.
10461 o Major bugfixes (security):
10462 - Tear down the circuit if we get an unexpected SENDME cell. Clients
10463 could use this trick to make their circuits receive cells faster
10464 than our flow control would have allowed, or to gum up the network,
10465 or possibly to do targeted memory denial-of-service attacks on
10466 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
10467 from July 2002, before the release of Tor 0.0.0. We had committed
10468 this patch previously, but we had to revert it because of bug 6271.
10469 Now that 6271 is fixed, this patch appears to work.
10470 - Reject any attempt to extend to an internal address. Without
10471 this fix, a router could be used to probe addresses on an internal
10472 network to see whether they were accepting connections. Fixes bug
10473 6710; bugfix on 0.0.8pre1.
10474 - Do not crash when comparing an address with port value 0 to an
10475 address policy. This bug could have been used to cause a remote
10476 assertion failure by or against directory authorities, or to
10477 allow some applications to crash clients. Fixes bug 6690; bugfix
10481 - Remove the upper bound on microdescriptor length. We were hitting
10482 the limit for routers with complex exit policies or family
10483 declarations, causing clients to not use them. Fixes the first
10484 piece of bug 6404; fix on 0.2.2.6-alpha.
10485 - Detect "ORPort 0" as meaning, uniformly, that we're not running
10486 as a relay. Previously, some of our code would treat the presence
10487 of any ORPort line as meaning that we should act like a relay,
10488 even though our new listener code would correctly not open any
10489 ORPorts for ORPort 0. Similar bugs in other Port options are also
10490 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
10493 - Avoid a pair of double-free and use-after-mark bugs that can
10494 occur with certain timings in canceled and re-received DNS
10495 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
10496 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
10497 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
10498 - Allow one-hop directory fetching circuits the full "circuit build
10499 timeout" period, rather than just half of it, before failing them
10500 and marking the relay down. This fix should help reduce cases where
10501 clients declare relays (or worse, bridges) unreachable because
10502 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
10503 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
10505 - Authorities no longer include any router in their microdescriptor
10506 consensuses for which they couldn't generate or agree on a
10507 microdescriptor. Fixes the second piece of bug 6404; fix on
10509 - Detect and reject attempts to specify both "FooPort" and
10510 "FooPort 0" in the same configuration domain. (It's still okay
10511 to have a FooPort in your configuration file, and use "FooPort 0"
10512 on the command line to disable it.) Fixes the second half of bug
10513 6507; bugfix on 0.2.3.3-alpha.
10514 - Make wildcarded addresses (that is, ones beginning with "*.") work
10515 when provided via the controller's MapAddress command. Previously,
10516 they were accepted, but we never actually noticed that they were
10517 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
10518 - Avoid crashing on a malformed state file where EntryGuardPathBias
10519 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
10520 - Add a (probably redundant) memory clear between iterations of
10521 the router status voting loop, to prevent future coding errors
10522 where data might leak between iterations of the loop. Resolves
10525 o Minor bugfixes (log messages):
10526 - Downgrade "set buildtimeout to low value" messages to "info"
10527 severity; they were never an actual problem, there was never
10528 anything reasonable to do about them, and they tended to spam logs
10529 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
10530 - Downgrade path-bias warning messages to "info". We'll try to get
10531 them working better in 0.2.4. Add internal circuit construction
10532 state to protect against the noisy warn message "Unexpectedly high
10533 circuit_successes". Also add some additional rate-limited notice
10534 messages to help determine the root cause of the warn. Fixes bug
10535 6475. Bugfix against 0.2.3.17-beta.
10536 - Move log message when unable to find a microdesc in a routerstatus
10537 entry to parse time. Previously we'd spam this warning every time
10538 we tried to figure out which microdescriptors to download. Fixes
10539 the third piece of bug 6404; fix on 0.2.3.18-rc.
10542 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
10543 change when the authority is deciding whether to accept a newly
10544 uploaded descriptor. Implements ticket 6423.
10545 - Add missing documentation for consensus and microdesc files.
10546 Resolves ticket 6732.
10549 Changes in version 0.2.2.38 - 2012-08-12
10550 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
10551 attack that could in theory leak path information.
10554 - Avoid an uninitialized memory read when reading a vote or consensus
10555 document that has an unrecognized flavor name. This read could
10556 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
10557 - Try to leak less information about what relays a client is
10558 choosing to a side-channel attacker. Previously, a Tor client would
10559 stop iterating through the list of available relays as soon as it
10560 had chosen one, thus finishing a little earlier when it picked
10561 a router earlier in the list. If an attacker can recover this
10562 timing information (nontrivial but not proven to be impossible),
10563 they could learn some coarse-grained information about which relays
10564 a client was picking (middle nodes in particular are likelier to
10565 be affected than exits). The timing attack might be mitigated by
10566 other factors (see bug 6537 for some discussion), but it's best
10567 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
10570 Changes in version 0.2.3.20-rc - 2012-08-05
10571 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
10572 series. It fixes a pair of code security bugs and a potential anonymity
10573 issue, updates our RPM spec files, and cleans up other smaller issues.
10576 - Avoid read-from-freed-memory and double-free bugs that could occur
10577 when a DNS request fails while launching it. Fixes bug 6480;
10578 bugfix on 0.2.0.1-alpha.
10579 - Avoid an uninitialized memory read when reading a vote or consensus
10580 document that has an unrecognized flavor name. This read could
10581 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
10582 - Try to leak less information about what relays a client is
10583 choosing to a side-channel attacker. Previously, a Tor client would
10584 stop iterating through the list of available relays as soon as it
10585 had chosen one, thus finishing a little earlier when it picked
10586 a router earlier in the list. If an attacker can recover this
10587 timing information (nontrivial but not proven to be impossible),
10588 they could learn some coarse-grained information about which relays
10589 a client was picking (middle nodes in particular are likelier to
10590 be affected than exits). The timing attack might be mitigated by
10591 other factors (see bug 6537 for some discussion), but it's best
10592 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
10595 - Try to make the warning when giving an obsolete SOCKSListenAddress
10596 a little more useful.
10597 - Terminate active server managed proxies if Tor stops being a
10598 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
10599 - Provide a better error message about possible OSX Asciidoc failure
10600 reasons. Fixes bug 6436.
10601 - Warn when Tor is configured to use accounting in a way that can
10602 link a hidden service to some other hidden service or public
10603 address. Resolves ticket 6490.
10606 - Check return value of fputs() when writing authority certificate
10607 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
10608 - Ignore ServerTransportPlugin lines when Tor is not configured as
10609 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
10610 - When disabling guards for having too high a proportion of failed
10611 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
10615 - Update our default RPM spec files to work with mock and rpmbuild
10616 on RHEL/Fedora. They have an updated set of dependencies and
10617 conflicts, a fix for an ancient typo when creating the "_tor"
10618 user, and better instructions. Thanks to Ondrej Mikle for the
10619 patch series. Fixes bug 6043.
10622 - Make it possible to set the TestingTorNetwork configuration
10623 option using AlternateDirAuthority and AlternateBridgeAuthority
10624 as an alternative to setting DirServer. Addresses ticket 6377.
10627 - Clarify the documentation for the Alternate*Authority options.
10629 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
10631 o Code simplification and refactoring:
10632 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
10633 10 lines. Also, don't nest them. Doing so in the past has
10634 led to hard-to-debug code. The new style is to use the
10635 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
10638 Changes in version 0.2.3.19-rc - 2012-07-06
10639 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
10640 series. It fixes the compile on Windows, reverts to a GeoIP database
10641 that isn't as broken, and fixes a flow control bug that has been around
10642 since the beginning of Tor.
10645 - Fix a bug handling SENDME cells on nonexistent streams that could
10646 result in bizarre window values. Report and patch contributed
10647 pseudonymously. Fixes part of bug 6271. This bug was introduced
10648 before the first Tor release, in svn commit r152.
10649 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
10650 June 2012 database, Maxmind marked many Tor relays as country "A1",
10651 which will cause risky behavior for clients that set EntryNodes
10652 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
10653 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
10654 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
10657 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
10658 bugfix on 0.2.1.10-alpha.
10661 Changes in version 0.2.3.18-rc - 2012-06-28
10662 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
10663 series. It fixes a few smaller bugs, but generally appears stable.
10664 Please test it and let us know whether it is!
10667 - Allow wildcarded mapaddress targets to be specified on the
10668 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
10669 - Make our linker option detection code more robust against linkers
10670 such as on FreeBSD 8, where a bad combination of options completes
10671 successfully but makes an unrunnable binary. Fixes bug 6173;
10672 bugfix on 0.2.3.17-beta.
10674 o Minor bugfixes (on 0.2.2.x and earlier):
10675 - Avoid a false positive in the util/threads unit test by increasing
10676 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
10677 - Replace "Sending publish request" log messages with "Launching
10678 upload", so that they no longer confusingly imply that we're
10679 sending something to a directory we might not even be connected
10680 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
10681 - Make sure to set *socket_error in all error cases in
10682 connection_connect(), so it can't produce a warning about
10683 errno being zero from errno_to_orconn_end_reason(). Bugfix on
10684 0.2.1.1-alpha; resolves ticket 6028.
10685 - Downgrade "Got a certificate, but we already have it" log messages
10686 from warning to info, except when we're a dirauth. Fixes bug 5238;
10687 bugfix on 0.2.1.7-alpha.
10688 - When checking for requested signatures on the latest consensus
10689 before serving it to a client, make sure to check the right
10690 consensus flavor. Bugfix on 0.2.2.6-alpha.
10691 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
10692 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
10694 o Minor bugfixes (on 0.2.3.x):
10695 - Make format_helper_exit_status() avoid unnecessary space padding
10696 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
10698 - Downgrade a message about cleaning the microdescriptor cache to
10699 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
10700 - Log a BUG message at severity INFO if we have a networkstatus with
10701 a missing entry for some microdescriptor. Continues on a patch
10703 - Improve the log message when a managed proxy fails to launch. Fixes
10704 bug 5099; bugfix on 0.2.3.6-alpha.
10705 - Don't do DNS lookups when parsing corrupted managed proxy protocol
10706 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
10707 - When formatting wildcarded address mappings for the controller,
10708 be sure to include "*." as appropriate. Partially fixes bug 6244;
10709 bugfix on 0.2.3.9-alpha.
10710 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
10711 Bugfix on 0.2.3.13-alpha.
10712 - Stop logging messages about running with circuit timeout learning
10713 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
10714 - Disable a spurious warning about reading on a marked and flushing
10715 connection. We shouldn't be doing that, but apparently we
10716 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
10717 - Fix a bug that stopped AllowDotExit from working on addresses
10718 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
10721 o Code simplification, refactoring, unit tests:
10722 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
10723 Libevent's notion of cached time when possible.
10724 - Remove duplicate code for invoking getrlimit() from control.c.
10725 - Add a unit test for the environment_variable_names_equal function.
10728 - Document the --defaults-torrc option, and the new (in 0.2.3)
10729 semantics for overriding, extending, and clearing lists of
10730 options. Closes bug 4748.
10733 Changes in version 0.2.3.17-beta - 2012-06-15
10734 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
10735 gets our TLS handshake back on track for being able to blend in with
10736 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
10737 with Vidalia, and otherwise continues to get us closer to a release
10741 - Enable gcc and ld hardening by default. Resolves ticket 5210.
10742 - Update TLS cipher list to match Firefox 8 and later. Resolves
10744 - Implement the client side of proposal 198: remove support for
10745 clients falsely claiming to support standard ciphersuites that
10746 they can actually provide. As of modern OpenSSL versions, it's not
10747 necessary to fake any standard ciphersuite, and doing so prevents
10748 us from using better ciphersuites in the future, since servers
10749 can't know whether an advertised ciphersuite is really supported or
10750 not. Some hosts -- notably, ones with very old versions of OpenSSL
10751 or where OpenSSL has been built with ECC disabled -- will stand
10752 out because of this change; TBB users should not be affected.
10755 - Change the default value for DynamicDHGroups (introduced in
10756 0.2.3.9-alpha) to 0. This feature can make Tor relays less
10757 identifiable by their use of the mod_ssl DH group, but at
10758 the cost of some usability (#4721) and bridge tracing (#6087)
10759 regressions. Resolves ticket 5598.
10760 - Send a CRLF at the end of each STATUS_* control protocol event. This
10761 bug tickled a bug in Vidalia which would make it freeze. Fixes
10762 bug 6094; bugfix on 0.2.3.16-alpha.
10765 - Disable writing on marked-for-close connections when they are
10766 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
10767 bug 5263; bugfix on 0.0.2pre13, where we first added a special
10768 case for flushing marked connections.
10769 - Detect SSL handshake even when the initial attempt to write the
10770 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
10771 - Change the AllowDotExit rules so they should actually work.
10772 We now enforce AllowDotExit only immediately after receiving an
10773 address via SOCKS or DNSPort: other sources are free to provide
10774 .exit addresses after the resolution occurs. Fixes bug 3940;
10775 bugfix on 0.2.2.1-alpha.
10776 - Fix a (harmless) integer overflow in cell statistics reported by
10777 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
10778 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
10779 right places and never depends on the consensus parameters or
10780 computes adaptive timeouts when it is disabled. Fixes bug 5049;
10781 bugfix on 0.2.2.14-alpha.
10782 - When building Tor on Windows with -DUNICODE (not default), ensure
10783 that error messages, filenames, and DNS server names are always
10784 NUL-terminated when we convert them to a single-byte encoding.
10785 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
10786 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
10787 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
10788 - Fix an edge case where TestingTorNetwork is set but the authorities
10789 and relays all have an uptime of zero, where the private Tor network
10790 could briefly lack support for hidden services. Fixes bug 3886;
10791 bugfix on 0.2.2.18-alpha.
10792 - Correct the manpage's descriptions for the default values of
10793 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
10795 - Fix the documentation for the --hush and --quiet command line
10796 options, which changed their behavior back in 0.2.3.3-alpha.
10797 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
10801 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
10802 more information to it, so that we can track it down in case it
10803 returns again. Mitigates bug 5235.
10804 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
10805 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
10806 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
10807 - Warn the user when HTTPProxy, but no other proxy type, is
10808 configured. This can cause surprising behavior: it doesn't send
10809 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
10810 directory traffic only. Resolves ticket 4663.
10811 - Issue a notice if a guard completes less than 40% of your circuits.
10812 Threshold is configurable by torrc option PathBiasNoticeRate and
10813 consensus parameter pb_noticepct. There is additional, off-by-
10814 default code to disable guards which fail too many circuits.
10815 Addresses ticket 5458.
10816 - Update to the June 6 2012 Maxmind GeoLite Country database.
10818 o Code simplifications and refactoring:
10819 - Remove validate_pluggable_transports_config(): its warning
10820 message is now handled by connection_or_connect().
10823 Changes in version 0.2.2.37 - 2012-06-06
10824 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
10825 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
10829 - Work around a bug in OpenSSL that broke renegotiation with TLS
10830 1.1 and TLS 1.2. Without this workaround, all attempts to speak
10831 the v2 Tor connection protocol when both sides were using OpenSSL
10832 1.0.1 would fail. Resolves ticket 6033.
10833 - When waiting for a client to renegotiate, don't allow it to add
10834 any bytes to the input buffer. This fixes a potential DoS issue.
10835 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
10836 - Fix an edge case where if we fetch or publish a hidden service
10837 descriptor, we might build a 4-hop circuit and then use that circuit
10838 for exiting afterwards -- even if the new last hop doesn't obey our
10839 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
10842 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
10843 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
10846 - Tell GCC and Clang to check for any errors in format strings passed
10847 to the tor_v*(print|scan)f functions.
10850 Changes in version 0.2.3.16-alpha - 2012-06-05
10851 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
10852 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
10853 currently). It also fixes a variety of smaller bugs and other cleanups
10854 that get us closer to a release candidate.
10856 o Major bugfixes (general):
10857 - Work around a bug in OpenSSL that broke renegotiation with TLS
10858 1.1 and TLS 1.2. Without this workaround, all attempts to speak
10859 the v2 Tor connection protocol when both sides were using OpenSSL
10860 1.0.1 would fail. Resolves ticket 6033.
10861 - When waiting for a client to renegotiate, don't allow it to add
10862 any bytes to the input buffer. This fixes a potential DoS issue.
10863 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
10864 - Pass correct OR address to managed proxies (like obfsproxy),
10865 even when ORListenAddress is used. Fixes bug 4865; bugfix on
10867 - The advertised platform of a router now includes only its operating
10868 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
10869 service pack level (for Windows) or its CPU architecture (for Unix).
10870 We also no longer include the "git-XYZ" tag in the version. Resolves
10873 o Major bugfixes (clients):
10874 - If we are unable to find any exit that supports our predicted ports,
10875 stop calling them predicted, so that we don't loop and build
10876 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
10877 which introduced predicted ports.
10878 - Fix an edge case where if we fetch or publish a hidden service
10879 descriptor, we might build a 4-hop circuit and then use that circuit
10880 for exiting afterwards -- even if the new last hop doesn't obey our
10881 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
10882 - Check at each new consensus whether our entry guards were picked
10883 long enough ago that we should rotate them. Previously, we only
10884 did this check at startup, which could lead to us holding a guard
10885 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
10886 - When fetching a bridge descriptor from a bridge authority,
10887 always do so anonymously, whether we have been able to open
10888 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
10889 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
10890 but we'll need to wait for bug 6010 before it's actually usable.
10892 o Major bugfixes (directory authorities):
10893 - When computing weight parameters, behave more robustly in the
10894 presence of a bad bwweightscale value. Previously, the authorities
10895 would crash if they agreed on a sufficiently broken weight_scale
10896 value: now, they use a reasonable default and carry on. Partial
10897 fix for 5786; bugfix on 0.2.2.17-alpha.
10898 - Check more thoroughly to prevent a rogue authority from
10899 double-voting on any consensus directory parameter. Previously,
10900 authorities would crash in this case if the total number of
10901 votes for any parameter exceeded the number of active voters,
10902 but would let it pass otherwise. Partial fix for bug 5786; bugfix
10906 - Rate-limit log messages when asked to connect anonymously to
10907 a private address. When these hit, they tended to hit fast and
10908 often. Also, don't bother trying to connect to addresses that we
10909 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
10910 reply makes us think we have been lied to, even when the address the
10911 client tried to connect to was "localhost." Resolves ticket 2822.
10912 - Allow packagers to insert an extra string in server descriptor
10913 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
10914 Resolves the rest of ticket 2988.
10915 - Raise the threshold of server descriptors needed (75%) and exit
10916 server descriptors needed (50%) before we will declare ourselves
10917 bootstrapped. This will make clients start building circuits a
10918 little later, but makes the initially constructed circuits less
10919 skewed and less in conflict with further directory fetches. Fixes
10921 - Close any connection that sends unrecognized junk before the
10922 handshake. Solves an issue noted in bug 4369.
10923 - Improve log messages about managed transports. Resolves ticket 5070.
10924 - Tag a bridge's descriptor as "never to be sent unencrypted".
10925 This shouldn't matter, since bridges don't open non-anonymous
10926 connections to the bridge authority and don't allow unencrypted
10927 directory connections from clients, but we might as well make
10928 sure. Closes bug 5139.
10929 - Expose our view of whether we have gone dormant to the controller,
10930 via a new "GETINFO dormant" value. Torbutton and other controllers
10931 can use this to avoid doing periodic requests through Tor while
10932 it's dormant (bug 4718). Fixes bug 5954.
10933 - Tell GCC and Clang to check for any errors in format strings passed
10934 to the tor_v*(print|scan)f functions.
10935 - Update to the May 1 2012 Maxmind GeoLite Country database.
10937 o Minor bugfixes (already included in 0.2.2.36):
10938 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
10939 Fixes bug 5346; bugfix on 0.0.8pre3.
10940 - Correct parsing of certain date types in parse_http_time().
10941 Without this patch, If-Modified-Since would behave
10942 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
10943 Esteban Manchado Velázques.
10944 - Make our number-parsing functions always treat too-large values
10945 as an error, even when those values exceed the width of the
10946 underlying type. Previously, if the caller provided these
10947 functions with minima or maxima set to the extreme values of the
10948 underlying integer type, these functions would return those
10949 values on overflow rather than treating overflow as an error.
10950 Fixes part of bug 5786; bugfix on 0.0.9.
10951 - If we hit the error case where routerlist_insert() replaces an
10952 existing (old) server descriptor, make sure to remove that
10953 server descriptor from the old_routers list. Fix related to bug
10954 1776. Bugfix on 0.2.2.18-alpha.
10955 - Clarify the behavior of MaxCircuitDirtiness with hidden service
10956 circuits. Fixes issue 5259.
10958 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
10959 - Prevent a null-pointer dereference when receiving a data cell
10960 for a nonexistent stream when the circuit in question has an
10961 empty deliver window. We don't believe this is triggerable,
10962 since we don't currently allow deliver windows to become empty,
10963 but the logic is tricky enough that it's better to make the code
10964 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
10965 - Fix a memory leak when trying to launch a DNS request when the
10966 network is disabled or the nameservers are unconfigurable. Fixes
10967 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
10968 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
10969 - Don't hold a Windows file handle open for every file mapping;
10970 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
10972 - Avoid O(n^2) performance characteristics when parsing a large
10973 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
10974 - Format more doubles with %f, not %lf. Patch from grarpamp to make
10975 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
10977 - Make our replacement implementation of strtok_r() compatible with
10978 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
10979 bugfix on 0.2.2.1-alpha.
10980 - Fix a NULL-pointer dereference on a badly formed
10981 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
10982 bugfix on 0.2.2.9-alpha.
10983 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
10984 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
10985 - Defensively refactor rend_mid_rendezvous() so that protocol
10986 violations and length checks happen in the beginning. Fixes
10988 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
10989 that IPv6 stuff will compile on MSVC, and compilation issues
10990 will be easier to track down. Fixes bug 5861.
10992 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
10993 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
10994 resource exhaustion, so that clients can adjust their load to
10995 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
10996 started using END_STREAM_REASON_RESOURCELIMIT.
10997 - Don't check for whether the address we're using for outbound
10998 connections has changed until after the outbound connection has
10999 completed. On Windows, getsockname() doesn't succeed until the
11000 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
11001 - If the configuration tries to set MyFamily on a bridge, refuse to
11002 do so, and warn about the security implications. Fixes bug 4657;
11003 bugfix on 0.2.0.3-alpha.
11004 - If the client fails to set a reasonable set of ciphersuites
11005 during its v2 handshake renegotiation, allow the renegotiation to
11006 continue nevertheless (i.e. send all the required certificates).
11007 Fixes bug 4591; bugfix on 0.2.0.20-rc.
11008 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
11009 option is set to 0 (which Vidalia version 0.2.16 now does when
11010 a SAVECONF attempt fails), perform other actions that SIGHUP
11011 usually causes (like reopening the logs). Fixes bug 5095; bugfix
11013 - If we fail to write a microdescriptor to the disk cache, do not
11014 continue replacing the old microdescriptor file. Fixes bug 2954;
11015 bugfix on 0.2.2.6-alpha.
11016 - Exit nodes don't need to fetch certificates for authorities that
11017 they don't recognize; only directory authorities, bridges,
11018 and caches need to do that. Fixes part of bug 2297; bugfix on
11020 - Correctly handle checking the permissions on the parent
11021 directory of a control socket in the root directory. Bug found
11022 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
11024 - When told to add a bridge with the same digest as a preexisting
11025 bridge but a different addr:port, change the addr:port as
11026 requested. Previously we would not notice the change. Fixes half
11027 of bug 5603; fix on 0.2.2.26-beta.
11028 - End AUTHCHALLENGE error messages (in the control protocol) with
11029 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
11031 o Minor bugfixes (on 0.2.3.x):
11032 - Turn an assertion (that the number of handshakes received as a
11033 server is not < 1) into a warning. Fixes bug 4873; bugfix on
11035 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
11036 we had reversed them when the answer was cached.) Fixes bug
11037 5723; bugfix on 0.2.3.1-alpha.
11038 - Work correctly on Linux systems with accept4 support advertised in
11039 their headers, but without accept4 support in the kernel. Fix
11040 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
11041 - When told to add a bridge with the same addr:port as a preexisting
11042 bridge but a different transport, change the transport as
11043 requested. Previously we would not notice the change. Fixes half
11044 of bug 5603; fix on 0.2.3.2-alpha.
11045 - Avoid a "double-reply" warning when replying to a SOCKS request
11046 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
11047 bugfix on 0.2.3.4-alpha.
11048 - Fix a bug where a bridge authority crashes if it has seen no
11049 directory requests when it's time to write statistics to disk.
11050 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
11052 - Don't try to open non-control listeners when DisableNetwork is set.
11053 Previously, we'd open all listeners, then immediately close them.
11054 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
11055 - Don't abort the managed proxy protocol if the managed proxy
11056 sends us an unrecognized line; ignore it instead. Fixes bug
11057 5910; bugfix on 0.2.3.9-alpha.
11058 - Fix a compile warning in crypto.c when compiling with clang 3.1.
11059 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
11060 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
11061 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
11062 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
11063 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
11064 - Resolve numerous small warnings and build issues with MSVC. Resolves
11067 o Documentation fixes:
11068 - Improve the manual's documentation for the NT Service command-line
11069 options. Addresses ticket 3964.
11070 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
11071 - Document the changes to the ORPort and DirPort options, and the
11072 fact that {OR/Dir}ListenAddress is now unnecessary (and
11073 therefore deprecated). Resolves ticket 5597.
11076 - Remove the torrc.bridge file: we don't use it for anything, and
11077 it had become badly desynchronized from torrc.sample. Resolves
11081 Changes in version 0.2.2.36 - 2012-05-24
11082 Tor 0.2.2.36 updates the addresses for two of the eight directory
11083 authorities, fixes some potential anonymity and security issues,
11084 and fixes several crash bugs.
11086 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
11087 known flaws, and nobody should be using them. You should upgrade. If
11088 you're using a Linux or BSD and its packages are obsolete, stop using
11089 those packages and upgrade anyway.
11091 o Directory authority changes:
11092 - Change IP address for maatuska (v3 directory authority).
11093 - Change IP address for ides (v3 directory authority), and rename
11097 - When building or running with any version of OpenSSL earlier
11098 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
11099 versions have a bug (CVE-2011-4576) in which their block cipher
11100 padding includes uninitialized data, potentially leaking sensitive
11101 information to any peer with whom they make a SSLv3 connection. Tor
11102 does not use SSL v3 by default, but a hostile client or server
11103 could force an SSLv3 connection in order to gain information that
11104 they shouldn't have been able to get. The best solution here is to
11105 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
11106 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
11107 to make sure that the bug can't happen.
11108 - Never use a bridge or a controller-supplied node as an exit, even
11109 if its exit policy allows it. Found by wanoskarnet. Fixes bug
11110 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
11111 and 0.2.0.3-alpha (for bridge-purpose descriptors).
11112 - Only build circuits if we have a sufficient threshold of the total
11113 descriptors that are marked in the consensus with the "Exit"
11114 flag. This mitigates an attack proposed by wanoskarnet, in which
11115 all of a client's bridges collude to restrict the exit nodes that
11116 the client knows about. Fixes bug 5343.
11117 - Provide controllers with a safer way to implement the cookie
11118 authentication mechanism. With the old method, if another locally
11119 running program could convince a controller that it was the Tor
11120 process, then that program could trick the controller into telling
11121 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
11122 authentication method uses a challenge-response approach to prevent
11123 this attack. Fixes bug 5185; implements proposal 193.
11126 - Avoid logging uninitialized data when unable to decode a hidden
11127 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
11128 - Avoid a client-side assertion failure when receiving an INTRODUCE2
11129 cell on a general purpose circuit. Fixes bug 5644; bugfix on
11131 - Fix builds when the path to sed, openssl, or sha1sum contains
11132 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
11134 - Correct our replacements for the timeradd() and timersub() functions
11135 on platforms that lack them (for example, Windows). The timersub()
11136 function is used when expiring circuits, while timeradd() is
11137 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
11138 bugfix on 0.2.2.24-alpha.
11139 - Fix the SOCKET_OK test that we use to tell when socket
11140 creation fails so that it works on Win64. Fixes part of bug 4533;
11141 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
11144 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
11145 Fixes bug 5346; bugfix on 0.0.8pre3.
11146 - Make our number-parsing functions always treat too-large values
11147 as an error, even when those values exceed the width of the
11148 underlying type. Previously, if the caller provided these
11149 functions with minima or maxima set to the extreme values of the
11150 underlying integer type, these functions would return those
11151 values on overflow rather than treating overflow as an error.
11152 Fixes part of bug 5786; bugfix on 0.0.9.
11153 - Older Linux kernels erroneously respond to strange nmap behavior
11154 by having accept() return successfully with a zero-length
11155 socket. When this happens, just close the connection. Previously,
11156 we would try harder to learn the remote address: but there was
11157 no such remote address to learn, and our method for trying to
11158 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
11159 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
11160 - Correct parsing of certain date types in parse_http_time().
11161 Without this patch, If-Modified-Since would behave
11162 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
11163 Esteban Manchado Velázques.
11164 - Change the BridgePassword feature (part of the "bridge community"
11165 design, which is not yet implemented) to use a time-independent
11166 comparison. The old behavior might have allowed an adversary
11167 to use timing to guess the BridgePassword value. Fixes bug 5543;
11168 bugfix on 0.2.0.14-alpha.
11169 - Detect and reject certain misformed escape sequences in
11170 configuration values. Previously, these values would cause us
11171 to crash if received in a torrc file or over an authenticated
11172 control port. Bug found by Esteban Manchado Velázquez, and
11173 independently by Robert Connolly from Matta Consulting who further
11174 noted that it allows a post-authentication heap overflow. Patch
11175 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
11176 bugfix on 0.2.0.16-alpha.
11177 - Fix a compile warning when using the --enable-openbsd-malloc
11178 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
11179 - During configure, detect when we're building with clang version
11180 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
11181 CFLAGS. clang doesn't support them yet.
11182 - When sending an HTTP/1.1 proxy request, include a Host header.
11183 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
11184 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
11185 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
11186 - If we hit the error case where routerlist_insert() replaces an
11187 existing (old) server descriptor, make sure to remove that
11188 server descriptor from the old_routers list. Fix related to bug
11189 1776. Bugfix on 0.2.2.18-alpha.
11191 o Minor bugfixes (documentation and log messages):
11192 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
11193 Fixes bug 4856; bugfix on Tor 0.0.6.
11194 - Update "ClientOnly" man page entry to explain that there isn't
11195 really any point to messing with it. Resolves ticket 5005.
11196 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
11197 directory authority option (introduced in Tor 0.2.2.34).
11198 - Downgrade the "We're missing a certificate" message from notice
11199 to info: people kept mistaking it for a real problem, whereas it
11200 is seldom the problem even when we are failing to bootstrap. Fixes
11201 bug 5067; bugfix on 0.2.0.10-alpha.
11202 - Correctly spell "connect" in a log message on failure to create a
11203 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
11204 - Clarify the behavior of MaxCircuitDirtiness with hidden service
11205 circuits. Fixes issue 5259.
11208 - Directory authorities now reject versions of Tor older than
11209 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
11210 inclusive. These versions accounted for only a small fraction of
11211 the Tor network, and have numerous known security issues. Resolves
11213 - Update to the May 1 2012 Maxmind GeoLite Country database.
11216 - When sending or relaying a RELAY_EARLY cell, we used to convert
11217 it to a RELAY cell if the connection was using the v1 link
11218 protocol. This was a workaround for older versions of Tor, which
11219 didn't handle RELAY_EARLY cells properly. Now that all supported
11220 versions can handle RELAY_EARLY cells, and now that we're enforcing
11221 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
11222 remove this workaround. Addresses bug 4786.
11225 Changes in version 0.2.3.15-alpha - 2012-04-30
11226 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
11227 the development branch build on Windows again.
11229 o Minor bugfixes (on 0.2.2.x and earlier):
11230 - Make sure that there are no unhandled pending TLS errors before
11231 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
11232 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
11233 Bugfix on 0.1.0.5-rc; fixes bug 4528.
11234 - Fix an assert that directory authorities could trigger on sighup
11235 during some configuration state transitions. We now don't treat
11236 it as a fatal error when the new descriptor we just generated in
11237 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
11238 - After we pick a directory mirror, we would refuse to use it if
11239 it's in our ExcludeExitNodes list, resulting in mysterious failures
11240 to bootstrap for people who just wanted to avoid exiting from
11241 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
11242 - When building with --enable-static-tor on OpenBSD, do not
11243 erroneously attempt to link -lrt. Fixes bug 5103.
11245 o Minor bugfixes (on 0.2.3.x):
11246 - When Tor is built with kernel headers from a recent (last few
11247 years) Linux kernel, do not fail to run on older (pre-2.6.28
11248 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
11249 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
11250 and 0.2.3.12-alpha.
11251 - Fix compilation with miniupnpc version 1.6; patch from
11252 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
11253 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
11254 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
11255 - Fix compilation on platforms without unistd.h, or where environ
11256 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
11259 - Directory authorities are now a little more lenient at accepting
11260 older router descriptors, or newer router descriptors that don't
11261 make big changes. This should help ameliorate past and future
11262 issues where routers think they have uploaded valid descriptors,
11263 but the authorities don't think so. Fix for ticket 2479.
11264 - Make the code that clients use to detect an address change be
11265 IPv6-aware, so that it won't fill clients' logs with error
11266 messages when trying to get the IPv4 address of an IPv6
11267 connection. Implements ticket 5537.
11269 o Removed features:
11270 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
11271 authorities needed to use it for a while to keep the network working
11272 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
11273 that was six months ago. As of now, it should no longer be needed
11277 Changes in version 0.2.3.14-alpha - 2012-04-23
11278 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
11279 candidate. It also dramatically speeds up AES: fast relays should
11280 consider switching to the newer OpenSSL library.
11282 o Directory authority changes:
11283 - Change IP address for ides (v3 directory authority), and rename
11287 - Avoid logging uninitialized data when unable to decode a hidden
11288 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
11289 - Avoid a client-side assertion failure when receiving an INTRODUCE2
11290 cell on a general purpose circuit. Fixes bug 5644; bugfix on
11292 - If authorities are unable to get a v2 consensus document from other
11293 directory authorities, they no longer fall back to fetching
11294 them from regular directory caches. Fixes bug 5635; bugfix on
11295 0.2.2.26-beta, where routers stopped downloading v2 consensus
11296 documents entirely.
11297 - When we start a Tor client with a normal consensus already cached,
11298 be willing to download a microdescriptor consensus. Fixes bug 4011;
11299 fix on 0.2.3.1-alpha.
11301 o Major features (performance):
11302 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
11303 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
11304 vectorized AES implementations as appropriate. These can be much,
11305 much faster than other AES implementations.
11307 o Minor bugfixes (0.2.2.x and earlier):
11308 - Don't launch more than 10 service-side introduction-point circuits
11309 for a hidden service in five minutes. Previously, we would consider
11310 launching more introduction-point circuits if at least one second
11311 had passed without any introduction-point circuits failing. Fixes
11312 bug 4607; bugfix on 0.0.7pre1.
11313 - Change the BridgePassword feature (part of the "bridge community"
11314 design, which is not yet implemented) to use a time-independent
11315 comparison. The old behavior might have allowed an adversary
11316 to use timing to guess the BridgePassword value. Fixes bug 5543;
11317 bugfix on 0.2.0.14-alpha.
11318 - Enforce correct return behavior of tor_vsscanf() when the '%%'
11319 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
11320 - When sending an HTTP/1.1 proxy request, include a Host header.
11321 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
11322 - Don't log that we have "decided to publish new relay descriptor"
11323 unless we are actually publishing a descriptor. Fixes bug 3942;
11324 bugfix on 0.2.2.28-beta.
11326 o Minor bugfixes (0.2.3.x):
11327 - Fix a bug where a bridge authority crashes (on a failed assert)
11328 if it has seen no directory requests when it's time to write
11329 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
11330 - Fix bug stomping on ORPort option NoListen and ignoring option
11331 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
11332 - In the testsuite, provide a large enough buffer in the tor_sscanf
11333 unit test. Otherwise we'd overrun that buffer and crash during
11334 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
11336 - Make sure we create the keys directory if it doesn't exist and we're
11337 about to store the dynamic Diffie-Hellman parameters. Fixes bug
11338 5572; bugfix on 0.2.3.13-alpha.
11339 - Fix a small memory leak when trying to decode incorrect base16
11340 authenticator during SAFECOOKIE authentication. Found by
11341 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
11344 - Add more information to a log statement that might help track down
11345 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
11346 non-IP address" messages (or any Bug messages, for that matter!),
11347 please let us know about it.
11348 - Relays now understand an IPv6 address when they get one from a
11349 directory server. Resolves ticket 4875.
11350 - Resolve IPv6 addresses in bridge and entry statistics to country
11351 code "??" which means we at least count them. Resolves ticket 5053;
11352 improves on 0.2.3.9-alpha.
11353 - Update to the April 3 2012 Maxmind GeoLite Country database.
11354 - Begin a doc/state-contents.txt file to explain the contents of
11355 the Tor state file. Fixes bug 2987.
11357 o Default torrc changes:
11358 - Stop listing "socksport 9050" in torrc.sample. We open a socks
11359 port on 9050 by default anyway, so this should not change anything
11361 - Stop mentioning the deprecated *ListenAddress options in
11362 torrc.sample. Fixes bug 5438.
11363 - Document unit of bandwidth related options in sample torrc.
11366 o Removed features:
11367 - The "torify" script no longer supports the "tsocks" socksifier
11368 tool, since tsocks doesn't support DNS and UDP right for Tor.
11369 Everyone should be using torsocks instead. Fixes bugs 3530 and
11370 5180. Based on a patch by "ugh".
11372 o Code refactoring:
11373 - Change the symmetric cipher interface so that creating and
11374 initializing a stream cipher are no longer separate functions.
11375 - Remove all internal support for unpadded RSA. We never used it, and
11376 it would be a bad idea to start.
11379 Changes in version 0.2.3.13-alpha - 2012-03-26
11380 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
11381 in managed pluggable transports, as well as providing other cleanups
11382 that get us closer to a release candidate.
11384 o Directory authority changes:
11385 - Change IP address for maatuska (v3 directory authority).
11388 - Provide controllers with a safer way to implement the cookie
11389 authentication mechanism. With the old method, if another locally
11390 running program could convince a controller that it was the Tor
11391 process, then that program could trick the controller into telling
11392 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
11393 authentication method uses a challenge-response approach to prevent
11394 this attack. Fixes bug 5185, implements proposal 193.
11395 - Never use a bridge or a controller-supplied node as an exit, even
11396 if its exit policy allows it. Found by wanoskarnet. Fixes bug
11397 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
11398 and 0.2.0.3-alpha (for bridge-purpose descriptors).
11399 - Only build circuits if we have a sufficient threshold of the total
11400 descriptors that are marked in the consensus with the "Exit"
11401 flag. This mitigates an attack proposed by wanoskarnet, in which
11402 all of a client's bridges collude to restrict the exit nodes that
11403 the client knows about. Fixes bug 5343.
11405 o Major bugfixes (on Tor 0.2.3.x):
11406 - Avoid an assert when managed proxies like obfsproxy are configured,
11407 and we receive HUP signals or setconf attempts too rapidly. This
11408 situation happens most commonly when Vidalia tries to attach to
11409 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
11410 bugfix on 0.2.3.6-alpha.
11411 - Fix a relay-side pluggable transports bug where managed proxies were
11412 unreachable from the Internet, because Tor asked them to bind on
11413 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
11414 - Stop discarding command-line arguments when TestingTorNetwork
11415 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
11416 0.2.3.9-alpha, where task 4552 added support for two layers of
11418 - Resume allowing the unit tests to run in gdb. This was accidentally
11419 made impossible when the DisableDebuggerAttachment option was
11420 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
11421 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
11422 0.2.3.11-alpha. Reported by Anthony G. Basile.
11424 o Minor bugfixes (on 0.2.2.x and earlier):
11425 - Ensure we don't cannibalize circuits that are longer than three hops
11426 already, so we don't end up making circuits with 5 or more
11427 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
11428 0.1.0.1-rc which introduced cannibalization.
11429 - Detect and reject certain misformed escape sequences in
11430 configuration values. Previously, these values would cause us
11431 to crash if received in a torrc file or over an authenticated
11432 control port. Bug found by Esteban Manchado Velázquez, and
11433 independently by Robert Connolly from Matta Consulting who further
11434 noted that it allows a post-authentication heap overflow. Patch
11435 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
11436 bugfix on 0.2.0.16-alpha.
11437 - Fix a compile warning when using the --enable-openbsd-malloc
11438 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
11439 - Directory caches no longer refuse to clean out descriptors because
11440 of missing v2 networkstatus documents, unless they're configured
11441 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
11442 0.2.2.26-beta. Patch by Daniel Bryg.
11443 - Update to the latest version of the tinytest unit testing framework.
11444 This includes a couple of bugfixes that can be relevant for
11445 running forked unit tests on Windows, and removes all reserved
11448 o Minor bugfixes (on 0.2.3.x):
11449 - On a failed pipe() call, don't leak file descriptors. Fixes bug
11450 4296; bugfix on 0.2.3.1-alpha.
11451 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
11452 until after we have received a CERTS cell. Fixes bug 4361; bugfix
11453 on 0.2.3.6-alpha. Patch by "frosty".
11454 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
11455 option, so that the IP stack doesn't decide to use it for IPv4
11456 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
11457 - Ensure that variables set in Tor's environment cannot override
11458 environment variables that Tor passes to a managed
11459 pluggable-transport proxy. Previously, Tor would pass every
11460 variable in its environment to managed proxies along with the new
11461 ones, in such a way that on many operating systems, the inherited
11462 environment variables would override those which Tor tried to
11463 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
11464 bugfix on 0.2.3.9-alpha for Windows.
11467 - A wide variety of new unit tests by Esteban Manchado Velázquez.
11468 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
11469 - Update to the March 6 2012 Maxmind GeoLite Country database.
11472 Changes in version 0.2.3.12-alpha - 2012-02-13
11473 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
11474 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
11475 when Tor is configured to use a pluggable transport like obfsproxy.
11478 - Fix builds when the path to sed, openssl, or sha1sum contains
11479 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
11481 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
11482 connections. This change should allow busy exit relays to stop
11483 running out of available sockets as quickly. Fixes bug 4950;
11484 bugfix on 0.2.2.26-beta.
11485 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
11486 would ask the bridge for microdescriptors, which are only supported
11487 in 0.2.3.x, and then fail to bootstrap when it didn't get the
11488 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
11489 - Properly set up obfsproxy's environment when in managed mode. The
11490 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
11491 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
11492 5076 and 5082; bugfix on 0.2.3.6-alpha.
11495 - Use the dead_strip option when building Tor on OS X. This reduces
11496 binary size by almost 19% when linking openssl and libevent
11497 statically, which we do for Tor Browser Bundle.
11498 - Fix broken URLs in the sample torrc file, and tell readers about
11499 the OutboundBindAddress, ExitPolicyRejectPrivate, and
11500 PublishServerDescriptor options. Addresses bug 4652.
11501 - Update to the February 7 2012 Maxmind GeoLite Country database.
11504 - Downgrade the "We're missing a certificate" message from notice
11505 to info: people kept mistaking it for a real problem, whereas it
11506 is seldom the problem even when we are failing to bootstrap. Fixes
11507 bug 5067; bugfix on 0.2.0.10-alpha.
11508 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
11509 managed pluggable transport server proxy's environment.
11510 Previously, we would put it there, even though Tor doesn't
11511 implement an 'extended server port' yet, and even though Tor
11512 almost certainly isn't listening at that address. For now, we set
11513 it to an empty string to avoid crashing older obfsproxies. Bugfix
11515 - Log the heartbeat message every HeartbeatPeriod seconds, not every
11516 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
11517 0.2.3.1-alpha. Bug reported by Scott Bennett.
11518 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
11519 bugfix on 0.2.3.11-alpha.
11520 - Update "ClientOnly" man page entry to explain that there isn't
11521 really any point to messing with it. Resolves ticket 5005.
11522 - Use the correct CVE number for CVE-2011-4576 in our comments and
11523 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
11526 o Code simplifications and refactoring:
11527 - Use the _WIN32 macro throughout our code to detect Windows.
11528 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
11532 Changes in version 0.2.3.11-alpha - 2012-01-22
11533 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
11534 the last step of the plan to limit maximum circuit length, includes
11535 a wide variety of hidden service performance and correctness fixes,
11536 works around an OpenSSL security flaw if your distro is too stubborn
11537 to upgrade, and fixes a bunch of smaller issues.
11540 - Now that Tor 0.2.0.x is completely deprecated, enable the final
11541 part of "Proposal 110: Avoiding infinite length circuits" by
11542 refusing all circuit-extend requests that do not use a relay_early
11543 cell. This change helps Tor resist a class of denial-of-service
11544 attacks by limiting the maximum circuit length.
11545 - Adjust the number of introduction points that a hidden service
11546 will try to maintain based on how long its introduction points
11547 remain in use and how many introductions they handle. Fixes
11549 - Try to use system facilities for enumerating local interface
11550 addresses, before falling back to our old approach (which was
11551 binding a UDP socket, and calling getsockname() on it). That
11552 approach was scaring OS X users whose draconian firewall
11553 software warned about binding to UDP sockets, regardless of
11554 whether packets were sent. Now we try to use getifaddrs(),
11555 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
11556 system supports. Resolves ticket 1827.
11558 o Major security workaround:
11559 - When building or running with any version of OpenSSL earlier
11560 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
11561 versions have a bug (CVE-2011-4576) in which their block cipher
11562 padding includes uninitialized data, potentially leaking sensitive
11563 information to any peer with whom they make a SSLv3 connection. Tor
11564 does not use SSL v3 by default, but a hostile client or server
11565 could force an SSLv3 connection in order to gain information that
11566 they shouldn't have been able to get. The best solution here is to
11567 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
11568 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
11569 to make sure that the bug can't happen.
11572 - Fix the SOCKET_OK test that we use to tell when socket
11573 creation fails so that it works on Win64. Fixes part of bug 4533;
11574 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
11575 - Correct our replacements for the timeradd() and timersub() functions
11576 on platforms that lack them (for example, Windows). The timersub()
11577 function is used when expiring circuits, while timeradd() is
11578 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
11579 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
11580 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
11581 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
11582 bug at runtime, not compile time, because some distributions hack
11583 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
11584 on 0.2.3.9-alpha. Found by Pascal.
11586 o Minor features (controller):
11587 - Use absolute path names when reporting the torrc filename in the
11588 control protocol, so a controller can more easily find the torrc
11589 file. Resolves bug 1101.
11590 - Extend the control protocol to report flags that control a circuit's
11591 path selection in CIRC events and in replies to 'GETINFO
11592 circuit-status'. Implements part of ticket 2411.
11593 - Extend the control protocol to report the hidden service address
11594 and current state of a hidden-service-related circuit in CIRC
11595 events and in replies to 'GETINFO circuit-status'. Implements part
11597 - When reporting the path to the cookie file to the controller,
11598 give an absolute path. Resolves ticket 4881.
11599 - Allow controllers to request an event notification whenever a
11600 circuit is cannibalized or its purpose is changed. Implements
11601 part of ticket 3457.
11602 - Include the creation time of a circuit in CIRC and CIRC2
11603 control-port events and the list produced by the 'GETINFO
11604 circuit-status' control-port command.
11606 o Minor features (directory authorities):
11607 - Directory authorities now reject versions of Tor older than
11608 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
11609 inclusive. These versions accounted for only a small fraction of
11610 the Tor network, and have numerous known security issues. Resolves
11612 - Authority operators can now vote for all relays in a given
11613 set of countries to be BadDir/BadExit/Invalid/Rejected.
11614 - Provide two consensus parameters (FastFlagMinThreshold and
11615 FastFlagMaxThreshold) to control the range of allowable bandwidths
11616 for the Fast directory flag. These allow authorities to run
11617 experiments on appropriate requirements for being a "Fast" node.
11618 The AuthDirFastGuarantee config value still applies. Implements
11620 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
11621 directory authority option (introduced in Tor 0.2.2.34).
11623 o Minor features (other):
11624 - Don't disable the DirPort when we cannot exceed our AccountingMax
11625 limit during this interval because the effective bandwidthrate is
11626 low enough. This is useful in a situation where AccountMax is only
11627 used as an additional safeguard or to provide statistics.
11628 - Prepend an informative header to generated dynamic_dh_params files.
11629 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
11630 EntryNodes will have no effect. Resolves issue 2571.
11631 - Log more useful messages when we fail to disable debugger
11633 - Log which authority we're missing votes from when we go to fetch
11634 them from the other auths.
11635 - Log (at debug level) whenever a circuit's purpose is changed.
11636 - Add missing documentation for the MaxClientCircuitsPending,
11637 UseMicrodescriptors, UserspaceIOCPBuffers, and
11638 _UseFilteringSSLBufferevents options, all introduced during
11639 the 0.2.3.x series.
11640 - Update to the January 3 2012 Maxmind GeoLite Country database.
11642 o Minor bugfixes (hidden services):
11643 - Don't close hidden service client circuits which have almost
11644 finished connecting to their destination when they reach
11645 the normal circuit-build timeout. Previously, we would close
11646 introduction circuits which are waiting for an acknowledgement
11647 from the introduction point, and rendezvous circuits which have
11648 been specified in an INTRODUCE1 cell sent to a hidden service,
11649 after the normal CBT. Now, we mark them as 'timed out', and launch
11650 another rendezvous attempt in parallel. This behavior change can
11651 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
11652 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
11653 - Don't close hidden-service-side rendezvous circuits when they
11654 reach the normal circuit-build timeout. This behavior change can
11655 be disabled using the new
11656 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
11657 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
11658 - Make sure we never mark the wrong rendezvous circuit as having
11659 had its introduction cell acknowleged by the introduction-point
11660 relay. Previously, when we received an INTRODUCE_ACK cell on a
11661 client-side hidden-service introduction circuit, we might have
11662 marked a rendezvous circuit other than the one we specified in
11663 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
11664 a warning message and interfered with the hidden service
11665 connection-establishment process. Fixes bug 4759; bugfix on
11666 0.2.3.3-alpha, when we added the stream-isolation feature which
11667 might cause Tor to open multiple rendezvous circuits for the same
11669 - Don't trigger an assertion failure when we mark a new client-side
11670 hidden-service introduction circuit for close during the process
11671 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
11674 o Minor bugfixes (log messages):
11675 - Correctly spell "connect" in a log message on failure to create a
11676 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
11678 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
11679 Fixes bug 4856; bugfix on Tor 0.0.6.
11680 - Fix the log message describing how we work around discovering
11681 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
11682 4837; bugfix on 0.2.2.9-alpha.
11683 - When logging about a disallowed .exit name, do not also call it
11684 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
11686 o Minor bugfixes (build fixes):
11687 - During configure, detect when we're building with clang version
11688 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
11689 CFLAGS. clang doesn't support them yet.
11690 - During configure, search for library containing cos function as
11691 libm lives in libcore on some platforms (BeOS/Haiku). Linking
11692 against libm was hard-coded before. Fixes the first part of bug
11693 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
11695 - Detect attempts to build Tor on (as yet hypothetical) versions
11696 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
11697 fix for bug 4533. Bugfix on 0.2.2.28-beta.
11698 - Preprocessor directives should not be put inside the arguments
11699 of a macro. This would break compilation with GCC releases prior
11700 to version 3.3. We would never recommend such an old GCC version,
11701 but it is apparently required for binary compatibility on some
11702 platforms (namely, certain builds of Haiku). Fixes the other part
11703 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
11706 o Minor bugfixes (other):
11707 - Older Linux kernels erroneously respond to strange nmap behavior
11708 by having accept() return successfully with a zero-length
11709 socket. When this happens, just close the connection. Previously,
11710 we would try harder to learn the remote address: but there was
11711 no such remote address to learn, and our method for trying to
11712 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
11713 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
11714 - Fix null-pointer access that could occur if TLS allocation failed.
11715 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
11716 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
11717 accidentally been reverted.
11718 - Fix our implementation of crypto_random_hostname() so it can't
11719 overflow on ridiculously large inputs. (No Tor version has ever
11720 provided this kind of bad inputs, but let's be correct in depth.)
11721 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
11722 - Find more places in the code that should have been testing for
11723 invalid sockets using the SOCKET_OK macro. Required for a fix
11724 for bug 4533. Bugfix on 0.2.2.28-beta.
11725 - Fix an assertion failure when, while running with bufferevents, a
11726 connection finishes connecting after it is marked for close, but
11727 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
11728 - test_util_spawn_background_ok() hardcoded the expected value
11729 for ENOENT to 2. This isn't portable as error numbers are
11730 platform specific, and particularly the hurd has ENOENT at
11731 0x40000002. Construct expected string at runtime, using the correct
11732 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
11733 - Reject attempts to disable DisableDebuggerAttachment while Tor is
11734 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
11735 - Use an appropriate-width type for sockets in tor-fw-helper on
11736 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
11739 - When sending or relaying a RELAY_EARLY cell, we used to convert
11740 it to a RELAY cell if the connection was using the v1 link
11741 protocol. This was a workaround for older versions of Tor, which
11742 didn't handle RELAY_EARLY cells properly. Now that all supported
11743 versions can handle RELAY_EARLY cells, and now that we're enforcing
11744 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
11745 remove this workaround. Addresses bug 4786.
11747 o Code simplifications and refactoring:
11748 - Use OpenSSL's built-in SSL_state_string_long() instead of our
11749 own homebrewed ssl_state_to_string() replacement. Patch from
11750 Emile Snyder. Fixes bug 4653.
11751 - Use macros to indicate OpenSSL versions, so we don't need to worry
11752 about accidental hexadecimal bit shifts.
11753 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
11755 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
11756 - Use the smartlist_add_asprintf() alias more consistently.
11757 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
11758 invalid value, rather than just -1.
11759 - Rename a handful of old identifiers, mostly related to crypto
11760 structures and crypto functions. By convention, our "create an
11761 object" functions are called "type_new()", our "free an object"
11762 functions are called "type_free()", and our types indicate that
11763 they are types only with a final "_t". But a handful of older
11764 types and functions broke these rules, with function names like
11765 "type_create" or "subsystem_op_type", or with type names like
11769 Changes in version 0.2.3.10-alpha - 2011-12-16
11770 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
11771 Tor's buffers code. Absolutely everybody should upgrade.
11773 The bug relied on an incorrect calculation when making data continuous
11774 in one of our IO buffers, if the first chunk of the buffer was
11775 misaligned by just the wrong amount. The miscalculation would allow an
11776 attacker to overflow a piece of heap-allocated memory. To mount this
11777 attack, the attacker would need to either open a SOCKS connection to
11778 Tor's SocksPort (usually restricted to localhost), or target a Tor
11779 instance configured to make its connections through a SOCKS proxy
11780 (which Tor does not do by default).
11782 Good security practice requires that all heap-overflow bugs should be
11783 presumed to be exploitable until proven otherwise, so we are treating
11784 this as a potential code execution attack. Please upgrade immediately!
11785 This bug does not affect bufferevents-based builds of Tor. Special
11786 thanks to "Vektor" for reporting this issue to us!
11788 This release also contains a few minor bugfixes for issues discovered
11792 - Fix a heap overflow bug that could occur when trying to pull
11793 data into the first chunk of a buffer, when that chunk had
11794 already had some data drained from it. Fixes CVE-2011-2778;
11795 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
11798 - If we can't attach streams to a rendezvous circuit when we
11799 finish connecting to a hidden service, clear the rendezvous
11800 circuit's stream-isolation state and try to attach streams
11801 again. Previously, we cleared rendezvous circuits' isolation
11802 state either too early (if they were freshly built) or not at all
11803 (if they had been built earlier and were cannibalized). Bugfix on
11804 0.2.3.3-alpha; fixes bug 4655.
11805 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
11806 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
11807 - Fix an assertion failure when a relay with accounting enabled
11808 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
11811 - Update to the December 6 2011 Maxmind GeoLite Country database.
11814 Changes in version 0.2.2.35 - 2011-12-16
11815 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
11816 buffers code. Absolutely everybody should upgrade.
11818 The bug relied on an incorrect calculation when making data continuous
11819 in one of our IO buffers, if the first chunk of the buffer was
11820 misaligned by just the wrong amount. The miscalculation would allow an
11821 attacker to overflow a piece of heap-allocated memory. To mount this
11822 attack, the attacker would need to either open a SOCKS connection to
11823 Tor's SocksPort (usually restricted to localhost), or target a Tor
11824 instance configured to make its connections through a SOCKS proxy
11825 (which Tor does not do by default).
11827 Good security practice requires that all heap-overflow bugs should be
11828 presumed to be exploitable until proven otherwise, so we are treating
11829 this as a potential code execution attack. Please upgrade immediately!
11830 This bug does not affect bufferevents-based builds of Tor. Special
11831 thanks to "Vektor" for reporting this issue to us!
11833 Tor 0.2.2.35 also fixes several bugs in previous versions, including
11834 crash bugs for unusual configurations, and a long-term bug that
11835 would prevent Tor from starting on Windows machines with draconian
11838 With this release, we remind everyone that 0.2.0.x has reached its
11839 formal end-of-life. Those Tor versions have many known flaws, and
11840 nobody should be using them. You should upgrade -- ideally to the
11841 0.2.2.x series. If you're using a Linux or BSD and its packages are
11842 obsolete, stop using those packages and upgrade anyway.
11844 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
11845 longer receive support after some time in early 2012.
11848 - Fix a heap overflow bug that could occur when trying to pull
11849 data into the first chunk of a buffer, when that chunk had
11850 already had some data drained from it. Fixes CVE-2011-2778;
11851 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
11852 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
11853 that it doesn't attempt to allocate a socketpair. This could cause
11854 some problems on Windows systems with overzealous firewalls. Fix for
11855 bug 4457; workaround for Libevent versions 2.0.1-alpha through
11857 - If we mark an OR connection for close based on a cell we process,
11858 don't process any further cells on it. We already avoid further
11859 reads on marked-for-close connections, but now we also discard the
11860 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
11861 which was the first version where we might mark a connection for
11862 close based on processing a cell on it.
11863 - Correctly sanity-check that we don't underflow on a memory
11864 allocation (and then assert) for hidden service introduction
11865 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
11866 bugfix on 0.2.1.5-alpha.
11867 - Fix a memory leak when we check whether a hidden service
11868 descriptor has any usable introduction points left. Fixes bug
11869 4424. Bugfix on 0.2.2.25-alpha.
11870 - Don't crash when we're running as a relay and don't have a GeoIP
11871 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
11872 we've had in the 0.2.3.x branch already.
11873 - When running as a client, do not print a misleading (and plain
11874 wrong) log message that we're collecting "directory request"
11875 statistics: clients don't collect statistics. Also don't create a
11876 useless (because empty) stats file in the stats/ directory. Fixes
11877 bug 4353; bugfix on 0.2.2.34.
11880 - Detect failure to initialize Libevent. This fix provides better
11881 detection for future instances of bug 4457.
11882 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
11883 function. This was eating up hideously large amounts of time on some
11884 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
11885 - Resolve an integer overflow bug in smartlist_ensure_capacity().
11886 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
11888 - Don't warn about unused log_mutex in log.c when building with
11889 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
11890 0.1.0.6-rc which introduced --disable-threads.
11891 - When configuring, starting, or stopping an NT service, stop
11892 immediately after the service configuration attempt has succeeded
11893 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
11894 - When sending a NETINFO cell, include the original address
11895 received for the other side, not its canonical address. Found
11896 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
11897 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
11898 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
11899 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
11900 occurred when a client tried to fetch a descriptor for a bridge
11901 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
11902 - Backport fixes for a pair of compilation warnings on Windows.
11903 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
11904 - If we had ever tried to call tor_addr_to_str on an address of
11905 unknown type, we would have done a strdup on an uninitialized
11906 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
11907 Reported by "troll_un".
11908 - Correctly detect and handle transient lookup failures from
11909 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
11910 Reported by "troll_un".
11911 - Fix null-pointer access that could occur if TLS allocation failed.
11912 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
11913 - Use tor_socket_t type for listener argument to accept(). Fixes bug
11914 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
11917 - Add two new config options for directory authorities:
11918 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
11919 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
11920 that is always sufficient to satisfy the bandwidth requirement for
11921 the Guard flag. Now it will be easier for researchers to simulate
11922 Tor networks with different values. Resolves ticket 4484.
11923 - When Tor ignores a hidden service specified in its configuration,
11924 include the hidden service's directory in the warning message.
11925 Previously, we would only tell the user that some hidden service
11926 was ignored. Bugfix on 0.0.6; fixes bug 4426.
11927 - Update to the December 6 2011 Maxmind GeoLite Country database.
11929 o Packaging changes:
11930 - Make it easier to automate expert package builds on Windows,
11931 by removing an absolute path from makensis.exe command.
11934 Changes in version 0.2.1.32 - 2011-12-16
11935 Tor 0.2.1.32 backports important security and privacy fixes for
11936 oldstable. This release is intended only for package maintainers and
11937 others who cannot use the 0.2.2 stable series. All others should be
11938 using Tor 0.2.2.x or newer.
11940 The Tor 0.2.1.x series will reach formal end-of-life some time in
11941 early 2012; we will stop releasing patches for it then.
11943 o Major bugfixes (also included in 0.2.2.x):
11944 - Correctly sanity-check that we don't underflow on a memory
11945 allocation (and then assert) for hidden service introduction
11946 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
11947 bugfix on 0.2.1.5-alpha.
11948 - Fix a heap overflow bug that could occur when trying to pull
11949 data into the first chunk of a buffer, when that chunk had
11950 already had some data drained from it. Fixes CVE-2011-2778;
11951 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
11954 - Update to the December 6 2011 Maxmind GeoLite Country database.
11957 Changes in version 0.2.3.9-alpha - 2011-12-08
11958 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
11959 a "DisableNetwork" security feature that bundles can use to avoid
11960 touching the network until bridges are configured, moves forward on
11961 the pluggable transport design, fixes a flaw in the hidden service
11962 design that unnecessarily prevented clients with wrong clocks from
11963 reaching hidden services, and fixes a wide variety of other issues.
11966 - Clients can now connect to private bridges over IPv6. Bridges
11967 still need at least one IPv4 address in order to connect to
11968 other relays. Note that we don't yet handle the case where the
11969 user has two bridge lines for the same bridge (one IPv4, one
11970 IPv6). Implements parts of proposal 186.
11971 - New "DisableNetwork" config option to prevent Tor from launching any
11972 connections or accepting any connections except on a control port.
11973 Bundles and controllers can set this option before letting Tor talk
11974 to the rest of the network, for example to prevent any connections
11975 to a non-bridge address. Packages like Orbot can also use this
11976 option to instruct Tor to save power when the network is off.
11977 - Clients and bridges can now be configured to use a separate
11978 "transport" proxy. This approach makes the censorship arms race
11979 easier by allowing bridges to use protocol obfuscation plugins. It
11980 implements the "managed proxy" part of proposal 180 (ticket 3472).
11981 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
11982 implementation. It makes AES_CTR about 7% faster than our old one
11983 (which was about 10% faster than the one OpenSSL used to provide).
11984 Resolves ticket 4526.
11985 - Add a "tor2web mode" for clients that want to connect to hidden
11986 services non-anonymously (and possibly more quickly). As a safety
11987 measure to try to keep users from turning this on without knowing
11988 what they are doing, tor2web mode must be explicitly enabled at
11989 compile time, and a copy of Tor compiled to run in tor2web mode
11990 cannot be used as a normal Tor client. Implements feature 2553.
11991 - Add experimental support for running on Windows with IOCP and no
11992 kernel-space socket buffers. This feature is controlled by a new
11993 "UserspaceIOCPBuffers" config option (off by default), which has
11994 no effect unless Tor has been built with support for bufferevents,
11995 is running on Windows, and has enabled IOCP. This may, in the long
11996 run, help solve or mitigate bug 98.
11997 - Use a more secure consensus parameter voting algorithm. Now at
11998 least three directory authorities or a majority of them must
11999 vote on a given parameter before it will be included in the
12000 consensus. Implements proposal 178.
12003 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
12004 They used to check that the timestamp was within 30 minutes
12005 of their system clock, so they could cap the size of their
12006 replay-detection cache, but that approach unnecessarily refused
12007 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
12008 the v3 intro-point protocol (the first one which sent a timestamp
12009 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
12010 - Only use the EVP interface when AES acceleration is enabled,
12011 to avoid a 5-7% performance regression. Resolves issue 4525;
12012 bugfix on 0.2.3.8-alpha.
12014 o Privacy/anonymity features (bridge detection):
12015 - Make bridge SSL certificates a bit more stealthy by using random
12016 serial numbers, in the same fashion as OpenSSL when generating
12017 self-signed certificates. Implements ticket 4584.
12018 - Introduce a new config option "DynamicDHGroups", enabled by
12019 default, which provides each bridge with a unique prime DH modulus
12020 to be used during SSL handshakes. This option attempts to help
12021 against censors who might use the Apache DH modulus as a static
12022 identifier for bridges. Addresses ticket 4548.
12024 o Minor features (new/different config options):
12025 - New configuration option "DisableDebuggerAttachment" (on by default)
12026 to prevent basic debugging attachment attempts by other processes.
12027 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
12028 - Allow MapAddress directives to specify matches against super-domains,
12029 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
12030 Implements issue 933.
12031 - Slightly change behavior of "list" options (that is, config
12032 options that can appear more than once) when they appear both in
12033 torrc and on the command line. Previously, the command-line options
12034 would be appended to the ones from torrc. Now, the command-line
12035 options override the torrc options entirely. This new behavior
12036 allows the user to override list options (like exit policies and
12037 ports to listen on) from the command line, rather than simply
12038 appending to the list.
12039 - You can get the old (appending) command-line behavior for "list"
12040 options by prefixing the option name with a "+".
12041 - You can remove all the values for a "list" option from the command
12042 line without adding any new ones by prefixing the option name
12044 - Add experimental support for a "defaults" torrc file to be parsed
12045 before the regular torrc. Torrc options override the defaults file's
12046 options in the same way that the command line overrides the torrc.
12047 The SAVECONF controller command saves only those options which
12048 differ between the current configuration and the defaults file. HUP
12049 reloads both files. (Note: This is an experimental feature; its
12050 behavior will probably be refined in future 0.2.3.x-alpha versions
12051 to better meet packagers' needs.) Implements task 4552.
12054 - Try to make the introductory warning message that Tor prints on
12055 startup more useful for actually finding help and information.
12056 Resolves ticket 2474.
12057 - Running "make version" now displays the version of Tor that
12058 we're about to build. Idea from katmagic; resolves issue 4400.
12059 - Expire old or over-used hidden service introduction points.
12060 Required by fix for bug 3460.
12061 - Move the replay-detection cache for the RSA-encrypted parts of
12062 INTRODUCE2 cells to the introduction point data structures.
12063 Previously, we would use one replay-detection cache per hidden
12064 service. Required by fix for bug 3460.
12065 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
12066 public key replay-detection cache from 60 minutes to 5 minutes. This
12067 replay-detection cache is now used only to detect multiple
12068 INTRODUCE2 cells specifying the same rendezvous point, so we can
12069 avoid launching multiple simultaneous attempts to connect to it.
12071 o Minor bugfixes (on Tor 0.2.2.x and earlier):
12072 - Resolve an integer overflow bug in smartlist_ensure_capacity().
12073 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
12075 - Fix a minor formatting issue in one of tor-gencert's error messages.
12077 - Prevent a false positive from the check-spaces script, by disabling
12078 the "whitespace between function name and (" check for functions
12080 - Fix a log message suggesting that people contact a non-existent
12081 email address. Fixes bug 3448.
12082 - Fix null-pointer access that could occur if TLS allocation failed.
12083 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
12084 - Report a real bootstrap problem to the controller on router
12085 identity mismatch. Previously we just said "foo", which probably
12086 made a lot of sense at the time. Fixes bug 4169; bugfix on
12088 - If we had ever tried to call tor_addr_to_str() on an address of
12089 unknown type, we would have done a strdup() on an uninitialized
12090 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
12091 Reported by "troll_un".
12092 - Correctly detect and handle transient lookup failures from
12093 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
12094 Reported by "troll_un".
12095 - Use tor_socket_t type for listener argument to accept(). Fixes bug
12096 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
12097 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
12098 bug 4532; found by "troll_un".
12100 o Minor bugfixes (on Tor 0.2.3.x):
12101 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
12103 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
12104 circuit for use as a hidden service client's rendezvous point.
12105 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
12106 with help from wanoskarnet.
12107 - Restore behavior of overriding SocksPort, ORPort, and similar
12108 options from the command line. Bugfix on 0.2.3.3-alpha.
12111 - Properly handle the case where the build-tree is not the same
12112 as the source tree when generating src/common/common_sha1.i,
12113 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
12114 bugfix on 0.2.0.1-alpha.
12116 o Code simplifications, cleanups, and refactorings:
12117 - Remove the pure attribute from all functions that used it
12118 previously. In many cases we assigned it incorrectly, because the
12119 functions might assert or call impure functions, and we don't have
12120 evidence that keeping the pure attribute is worthwhile. Implements
12121 changes suggested in ticket 4421.
12122 - Remove some dead code spotted by coverity. Fixes cid 432.
12123 Bugfix on 0.2.3.1-alpha, closes bug 4637.
12126 Changes in version 0.2.3.8-alpha - 2011-11-22
12127 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
12128 socketpair-related bug that has been bothering Windows users. It adds
12129 support to serve microdescriptors to controllers, so Vidalia's network
12130 map can resume listing relays (once Vidalia implements its side),
12131 and adds better support for hardware AES acceleration. Finally, it
12132 starts the process of adjusting the bandwidth cutoff for getting the
12133 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
12134 that tiny relays harm performance more than they help network capacity.
12137 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
12138 that it doesn't attempt to allocate a socketpair. This could cause
12139 some problems on Windows systems with overzealous firewalls. Fix for
12140 bug 4457; workaround for Libevent versions 2.0.1-alpha through
12142 - Correctly sanity-check that we don't underflow on a memory
12143 allocation (and then assert) for hidden service introduction
12144 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12145 bugfix on 0.2.1.5-alpha.
12146 - Remove the artificially low cutoff of 20KB to guarantee the Fast
12147 flag. In the past few years the average relay speed has picked
12148 up, and while the "top 7/8 of the network get the Fast flag" and
12149 "all relays with 20KB or more of capacity get the Fast flag" rules
12150 used to have the same result, now the top 7/8 of the network has
12151 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
12152 - Fix a rare assertion failure when checking whether a v0 hidden
12153 service descriptor has any usable introduction points left, and
12154 we don't have enough information to build a circuit to the first
12155 intro point named in the descriptor. The HS client code in
12156 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
12157 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
12158 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
12159 - Make bridge authorities not crash when they are asked for their own
12160 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
12161 - When running as a client, do not print a misleading (and plain
12162 wrong) log message that we're collecting "directory request"
12163 statistics: clients don't collect statistics. Also don't create a
12164 useless (because empty) stats file in the stats/ directory. Fixes
12165 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
12168 - Allow Tor controllers like Vidalia to obtain the microdescriptor
12169 for a relay by identity digest or nickname. Previously,
12170 microdescriptors were only available by their own digests, so a
12171 controller would have to ask for and parse the whole microdescriptor
12172 consensus in order to look up a single relay's microdesc. Fixes
12173 bug 3832; bugfix on 0.2.3.1-alpha.
12174 - Use OpenSSL's EVP interface for AES encryption, so that all AES
12175 operations can use hardware acceleration (if present). Resolves
12178 o Minor bugfixes (on 0.2.2.x and earlier):
12179 - Detect failure to initialize Libevent. This fix provides better
12180 detection for future instances of bug 4457.
12181 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
12182 function. This was eating up hideously large amounts of time on some
12183 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
12184 - Don't warn about unused log_mutex in log.c when building with
12185 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
12186 0.1.0.6-rc which introduced --disable-threads.
12187 - Allow manual 'authenticate' commands to the controller interface
12188 from netcat (nc) as well as telnet. We were rejecting them because
12189 they didn't come with the expected whitespace at the end of the
12190 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
12191 - Fix some (not actually triggerable) buffer size checks in usage of
12192 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
12194 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
12195 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
12196 - When configuring, starting, or stopping an NT service, stop
12197 immediately after the service configuration attempt has succeeded
12198 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
12199 - When sending a NETINFO cell, include the original address
12200 received for the other side, not its canonical address. Found
12201 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
12202 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
12203 can pick them up when the tests aren't disabled. Bugfix on
12204 0.2.2.4-alpha which introduced tinytest.
12205 - Fix a memory leak when we check whether a hidden service
12206 descriptor has any usable introduction points left. Fixes bug
12207 4424. Bugfix on 0.2.2.25-alpha.
12208 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
12209 occurred when a client tried to fetch a descriptor for a bridge
12210 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
12212 o Minor bugfixes (on 0.2.3.x):
12213 - Make util unit tests build correctly with MSVC. Bugfix on
12214 0.2.3.3-alpha. Patch by Gisle Vanem.
12215 - Successfully detect AUTH_CHALLENGE cells with no recognized
12216 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
12217 Found by frosty_un.
12218 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
12219 it should still send a NETINFO cell to allow the connection to
12220 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
12222 - Log less loudly when we get an invalid authentication certificate
12223 from a source other than a directory authority: it's not unusual
12224 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
12226 - Tolerate servers with more clock skew in their authentication
12227 certificates than previously. Fixes bug 4371; bugfix on
12229 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
12230 on 0.2.3.4-alpha and 0.2.3.6-alpha.
12233 - Add two new config options for directory authorities:
12234 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
12235 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
12236 that is always sufficient to satisfy the bandwidth requirement for
12237 the Guard flag. Now it will be easier for researchers to simulate
12238 Tor networks with different values. Resolves ticket 4484.
12239 - When Tor ignores a hidden service specified in its configuration,
12240 include the hidden service's directory in the warning message.
12241 Previously, we would only tell the user that some hidden service
12242 was ignored. Bugfix on 0.0.6; fixes bug 4426.
12243 - When we fail to initialize Libevent, retry with IOCP disabled so we
12244 don't need to turn on multi-threading support in Libevent, which in
12245 turn requires a working socketpair(). This is a workaround for bug
12246 4457, which affects Libevent versions from 2.0.1-alpha through
12248 - Detect when we try to build on a platform that doesn't define
12249 AF_UNSPEC to 0. We don't work there, so refuse to compile.
12250 - Update to the November 1 2011 Maxmind GeoLite Country database.
12252 o Packaging changes:
12253 - Make it easier to automate expert package builds on Windows,
12254 by removing an absolute path from makensis.exe command.
12256 o Code simplifications and refactoring:
12257 - Remove some redundant #include directives throughout the code.
12258 Patch from Andrea Gelmini.
12259 - Unconditionally use OpenSSL's AES implementation instead of our
12260 old built-in one. OpenSSL's AES has been better for a while, and
12261 relatively few servers should still be on any version of OpenSSL
12262 that doesn't have good optimized assembly AES.
12263 - Use the name "CERTS" consistently to refer to the new cell type;
12264 we were calling it CERT in some places and CERTS in others.
12267 - Numerous new unit tests for functions in util.c and address.c by
12269 - The long-disabled benchmark tests are now split into their own
12270 ./src/test/bench binary.
12271 - The benchmark tests can now use more accurate timers than
12272 gettimeofday() when such timers are available.
12275 Changes in version 0.2.3.7-alpha - 2011-10-30
12276 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
12277 the new v3 handshake. It also resolves yet another bridge address
12281 - If we mark an OR connection for close based on a cell we process,
12282 don't process any further cells on it. We already avoid further
12283 reads on marked-for-close connections, but now we also discard the
12284 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
12285 which was the first version where we might mark a connection for
12286 close based on processing a cell on it.
12287 - Fix a double-free bug that would occur when we received an invalid
12288 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
12289 bugfix on 0.2.3.6-alpha.
12290 - Bridges no longer include their address in NETINFO cells on outgoing
12291 OR connections, to allow them to blend in better with clients.
12292 Removes another avenue for enumerating bridges. Reported by
12293 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
12294 cells were introduced.
12297 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
12298 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
12301 Changes in version 0.2.3.6-alpha - 2011-10-26
12302 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
12303 anonymity vulnerability where an attacker can deanonymize Tor
12304 users. Everybody should upgrade.
12306 This release also features support for a new v3 connection handshake
12307 protocol, and fixes to make hidden service connections more robust.
12310 - Implement a new handshake protocol (v3) for authenticating Tors to
12311 each other over TLS. It should be more resistant to fingerprinting
12312 than previous protocols, and should require less TLS hacking for
12313 future Tor implementations. Implements proposal 176.
12314 - Allow variable-length padding cells to disguise the length of
12315 Tor's TLS records. Implements part of proposal 184.
12317 o Privacy/anonymity fixes (clients):
12318 - Clients and bridges no longer send TLS certificate chains on
12319 outgoing OR connections. Previously, each client or bridge would
12320 use the same cert chain for all outgoing OR connections until
12321 its IP address changes, which allowed any relay that the client
12322 or bridge contacted to determine which entry guards it is using.
12323 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12324 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12325 no longer considers that connection as suitable for satisfying a
12326 circuit EXTEND request. Now relays can protect clients from the
12327 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12328 - Directory authorities no longer assign the Guard flag to relays
12329 that haven't upgraded to the above "refuse EXTEND requests
12330 to client connections" fix. Now directory authorities can
12331 protect clients from the CVE-2011-2768 issue even if neither
12332 the clients nor the relays have upgraded yet. There's a new
12333 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
12334 to let us transition smoothly, else tomorrow there would be no
12337 o Major bugfixes (hidden services):
12338 - Improve hidden service robustness: when an attempt to connect to
12339 a hidden service ends, be willing to refetch its hidden service
12340 descriptors from each of the HSDir relays responsible for them
12341 immediately. Previously, we would not consider refetching the
12342 service's descriptors from each HSDir for 15 minutes after the last
12343 fetch, which was inconvenient if the hidden service was not running
12344 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
12345 - When one of a hidden service's introduction points appears to be
12346 unreachable, stop trying it. Previously, we would keep trying
12347 to build circuits to the introduction point until we lost the
12348 descriptor, usually because the user gave up and restarted Tor.
12349 Partly fixes bug 3825.
12350 - Don't launch a useless circuit after failing to use one of a
12351 hidden service's introduction points. Previously, we would
12352 launch a new introduction circuit, but not set the hidden service
12353 which that circuit was intended to connect to, so it would never
12354 actually be used. A different piece of code would then create a
12355 new introduction circuit correctly. Bug reported by katmagic and
12356 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
12358 o Major bugfixes (other):
12359 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12360 that they initiated. Relays could distinguish incoming bridge
12361 connections from client connections, creating another avenue for
12362 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12363 Found by "frosty_un".
12364 - Don't update the AccountingSoftLimitHitAt state file entry whenever
12365 tor gets started. This prevents a wrong average bandwidth
12366 estimate, which would cause relays to always start a new accounting
12367 interval at the earliest possible moment. Fixes bug 2003; bugfix
12368 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
12369 immensely in tracking this bug down.
12370 - Fix a crash bug when changing node restrictions while a DNS lookup
12371 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
12374 o Minor bugfixes (on 0.2.2.x and earlier):
12375 - When a hidden service turns an extra service-side introduction
12376 circuit into a general-purpose circuit, free the rend_data and
12377 intro_key fields first, so we won't leak memory if the circuit
12378 is cannibalized for use as another service-side introduction
12379 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
12380 - Rephrase the log message emitted if the TestSocks check is
12381 successful. Patch from Fabian Keil; fixes bug 4094.
12382 - Bridges now skip DNS self-tests, to act a little more stealthily.
12383 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
12384 bridges. Patch by "warms0x".
12385 - Remove a confusing dollar sign from the example fingerprint in the
12386 man page, and also make the example fingerprint a valid one. Fixes
12387 bug 4309; bugfix on 0.2.1.3-alpha.
12388 - Fix internal bug-checking logic that was supposed to catch
12389 failures in digest generation so that it will fail more robustly
12390 if we ask for a nonexistent algorithm. Found by Coverity Scan.
12391 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
12392 - Report any failure in init_keys() calls launched because our
12393 IP address has changed. Spotted by Coverity Scan. Bugfix on
12394 0.1.1.4-alpha; fixes CID 484.
12396 o Minor bugfixes (on 0.2.3.x):
12397 - Fix a bug in configure.in that kept it from building a configure
12398 script with autoconf versions earlier than 2.61. Fixes bug 2430;
12399 bugfix on 0.2.3.1-alpha.
12400 - Don't warn users that they are exposing a client port to the
12401 Internet if they have specified an RFC1918 address. Previously,
12402 we would warn if the user had specified any non-loopback
12403 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
12404 - Fix memory leaks in the failing cases of the new SocksPort and
12405 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
12406 fixes coverity CIDs 485, 486, and 487.
12409 - When a hidden service's introduction point times out, consider
12410 trying it again during the next attempt to connect to the
12411 HS. Previously, we would not try it again unless a newly fetched
12412 descriptor contained it. Required by fixes for bugs 1297 and 3825.
12413 - The next version of Windows will be called Windows 8, and it has
12414 a major version of 6, minor version of 2. Correctly identify that
12415 version instead of calling it "Very recent version". Resolves
12416 ticket 4153; reported by funkstar.
12417 - The Bridge Authority now writes statistics on how many bridge
12418 descriptors it gave out in total, and how many unique descriptors
12419 it gave out. It also lists how often the most and least commonly
12420 fetched descriptors were given out, as well as the median and
12421 25th/75th percentile. Implements tickets 4200 and 4294.
12422 - Update to the October 4 2011 Maxmind GeoLite Country database.
12424 o Code simplifications and refactoring:
12425 - Remove some old code to remember statistics about which descriptors
12426 we've served as a directory mirror. The feature wasn't used and
12427 is outdated now that microdescriptors are around.
12428 - Rename Tor functions that turn strings into addresses, so that
12429 "parse" indicates that no hostname resolution occurs, and
12430 "lookup" indicates that hostname resolution may occur. This
12431 should help prevent mistakes in the future. Fixes bug 3512.
12434 Changes in version 0.2.2.34 - 2011-10-26
12435 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
12436 can deanonymize Tor users. Everybody should upgrade.
12438 The attack relies on four components: 1) Clients reuse their TLS cert
12439 when talking to different relays, so relays can recognize a user by
12440 the identity key in her cert. 2) An attacker who knows the client's
12441 identity key can probe each guard relay to see if that identity key
12442 is connected to that guard relay right now. 3) A variety of active
12443 attacks in the literature (starting from "Low-Cost Traffic Analysis
12444 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
12445 discover the guard relays that a Tor user visiting the website is using.
12446 4) Clients typically pick three guards at random, so the set of guards
12447 for a given user could well be a unique fingerprint for her. This
12448 release fixes components #1 and #2, which is enough to block the attack;
12449 the other two remain as open research problems. Special thanks to
12450 "frosty_un" for reporting the issue to us!
12452 Clients should upgrade so they are no longer recognizable by the TLS
12453 certs they present. Relays should upgrade so they no longer allow a
12454 remote attacker to probe them to test whether unpatched clients are
12455 currently connected to them.
12457 This release also fixes several vulnerabilities that allow an attacker
12458 to enumerate bridge relays. Some bridge enumeration attacks still
12459 remain; see for example proposal 188.
12461 o Privacy/anonymity fixes (clients):
12462 - Clients and bridges no longer send TLS certificate chains on
12463 outgoing OR connections. Previously, each client or bridge would
12464 use the same cert chain for all outgoing OR connections until
12465 its IP address changes, which allowed any relay that the client
12466 or bridge contacted to determine which entry guards it is using.
12467 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12468 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12469 no longer considers that connection as suitable for satisfying a
12470 circuit EXTEND request. Now relays can protect clients from the
12471 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12472 - Directory authorities no longer assign the Guard flag to relays
12473 that haven't upgraded to the above "refuse EXTEND requests
12474 to client connections" fix. Now directory authorities can
12475 protect clients from the CVE-2011-2768 issue even if neither
12476 the clients nor the relays have upgraded yet. There's a new
12477 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
12478 to let us transition smoothly, else tomorrow there would be no
12481 o Privacy/anonymity fixes (bridge enumeration):
12482 - Bridge relays now do their directory fetches inside Tor TLS
12483 connections, like all the other clients do, rather than connecting
12484 directly to the DirPort like public relays do. Removes another
12485 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
12486 - Bridges relays now build circuits for themselves in a more similar
12487 way to how clients build them. Removes another avenue for
12488 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
12489 when bridges were introduced.
12490 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12491 that they initiated. Relays could distinguish incoming bridge
12492 connections from client connections, creating another avenue for
12493 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12494 Found by "frosty_un".
12497 - Fix a crash bug when changing node restrictions while a DNS lookup
12498 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
12500 - Don't launch a useless circuit after failing to use one of a
12501 hidden service's introduction points. Previously, we would
12502 launch a new introduction circuit, but not set the hidden service
12503 which that circuit was intended to connect to, so it would never
12504 actually be used. A different piece of code would then create a
12505 new introduction circuit correctly. Bug reported by katmagic and
12506 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
12509 - Change an integer overflow check in the OpenBSD_Malloc code so
12510 that GCC is less likely to eliminate it as impossible. Patch
12511 from Mansour Moufid. Fixes bug 4059.
12512 - When a hidden service turns an extra service-side introduction
12513 circuit into a general-purpose circuit, free the rend_data and
12514 intro_key fields first, so we won't leak memory if the circuit
12515 is cannibalized for use as another service-side introduction
12516 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
12517 - Bridges now skip DNS self-tests, to act a little more stealthily.
12518 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
12519 bridges. Patch by "warms0x".
12520 - Fix internal bug-checking logic that was supposed to catch
12521 failures in digest generation so that it will fail more robustly
12522 if we ask for a nonexistent algorithm. Found by Coverity Scan.
12523 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
12524 - Report any failure in init_keys() calls launched because our
12525 IP address has changed. Spotted by Coverity Scan. Bugfix on
12526 0.1.1.4-alpha; fixes CID 484.
12528 o Minor bugfixes (log messages and documentation):
12529 - Remove a confusing dollar sign from the example fingerprint in the
12530 man page, and also make the example fingerprint a valid one. Fixes
12531 bug 4309; bugfix on 0.2.1.3-alpha.
12532 - The next version of Windows will be called Windows 8, and it has
12533 a major version of 6, minor version of 2. Correctly identify that
12534 version instead of calling it "Very recent version". Resolves
12535 ticket 4153; reported by funkstar.
12536 - Downgrade log messages about circuit timeout calibration from
12537 "notice" to "info": they don't require or suggest any human
12538 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
12539 bugfix on 0.2.2.14-alpha.
12542 - Turn on directory request statistics by default and include them in
12543 extra-info descriptors. Don't break if we have no GeoIP database.
12544 Backported from 0.2.3.1-alpha; implements ticket 3951.
12545 - Update to the October 4 2011 Maxmind GeoLite Country database.
12548 Changes in version 0.2.1.31 - 2011-10-26
12549 Tor 0.2.1.31 backports important security and privacy fixes for
12550 oldstable. This release is intended only for package maintainers and
12551 others who cannot use the 0.2.2 stable series. All others should be
12552 using Tor 0.2.2.x or newer.
12554 o Security fixes (also included in 0.2.2.x):
12555 - Replace all potentially sensitive memory comparison operations
12556 with versions whose runtime does not depend on the data being
12557 compared. This will help resist a class of attacks where an
12558 adversary can use variations in timing information to learn
12559 sensitive data. Fix for one case of bug 3122. (Safe memcmp
12560 implementation by Robert Ransom based partially on code by DJB.)
12561 - Fix an assert in parsing router descriptors containing IPv6
12562 addresses. This one took down the directory authorities when
12563 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
12565 o Privacy/anonymity fixes (also included in 0.2.2.x):
12566 - Clients and bridges no longer send TLS certificate chains on
12567 outgoing OR connections. Previously, each client or bridge would
12568 use the same cert chain for all outgoing OR connections until
12569 its IP address changes, which allowed any relay that the client
12570 or bridge contacted to determine which entry guards it is using.
12571 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12572 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12573 no longer considers that connection as suitable for satisfying a
12574 circuit EXTEND request. Now relays can protect clients from the
12575 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12576 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12577 that they initiated. Relays could distinguish incoming bridge
12578 connections from client connections, creating another avenue for
12579 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12580 Found by "frosty_un".
12581 - When receiving a hidden service descriptor, check that it is for
12582 the hidden service we wanted. Previously, Tor would store any
12583 hidden service descriptors that a directory gave it, whether it
12584 wanted them or not. This wouldn't have let an attacker impersonate
12585 a hidden service, but it did let directories pre-seed a client
12586 with descriptors that it didn't want. Bugfix on 0.0.6.
12587 - Avoid linkability based on cached hidden service descriptors: forget
12588 all hidden service descriptors cached as a client when processing a
12589 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
12590 - Make the bridge directory authority refuse to answer directory
12591 requests for "all" descriptors. It used to include bridge
12592 descriptors in its answer, which was a major information leak.
12593 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
12594 - Don't attach new streams to old rendezvous circuits after SIGNAL
12595 NEWNYM. Previously, we would keep using an existing rendezvous
12596 circuit if it remained open (i.e. if it were kept open by a
12597 long-lived stream, or if a new stream were attached to it before
12598 Tor could notice that it was old and no longer in use). Bugfix on
12599 0.1.1.15-rc; fixes bug 3375.
12601 o Minor bugfixes (also included in 0.2.2.x):
12602 - When we restart our relay, we might get a successful connection
12603 from the outside before we've started our reachability tests,
12604 triggering a warning: "ORPort found reachable, but I have no
12605 routerinfo yet. Failing to inform controller of success." This
12606 bug was harmless unless Tor is running under a controller
12607 like Vidalia, in which case the controller would never get a
12608 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
12610 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
12611 enabled. Fixes bug 1526.
12612 - Remove undocumented option "-F" from tor-resolve: it hasn't done
12613 anything since 0.2.1.16-rc.
12614 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
12615 None of the cases where we did this before were wrong, but by making
12616 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
12617 - Fix a rare crash bug that could occur when a client was configured
12618 with a large number of bridges. Fixes bug 2629; bugfix on
12619 0.2.1.2-alpha. Bugfix by trac user "shitlei".
12620 - Correct the warning displayed when a rendezvous descriptor exceeds
12621 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
12623 - Fix an uncommon assertion failure when running with DNSPort under
12624 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
12625 - When warning about missing zlib development packages during compile,
12626 give the correct package names. Bugfix on 0.2.0.1-alpha.
12627 - Require that introduction point keys and onion keys have public
12628 exponent 65537. Bugfix on 0.2.0.10-alpha.
12629 - Do not crash when our configuration file becomes unreadable, for
12630 example due to a permissions change, between when we start up
12631 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
12633 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
12635 - Always NUL-terminate the sun_path field of a sockaddr_un before
12636 passing it to the kernel. (Not a security issue: kernels are
12637 smart enough to reject bad sockaddr_uns.) Found by Coverity;
12638 CID #428. Bugfix on Tor 0.2.0.3-alpha.
12639 - Don't stack-allocate the list of supplementary GIDs when we're
12640 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
12641 could take up to 256K, which is way too much stack. Found by
12642 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
12644 o Minor bugfixes (only in 0.2.1.x):
12645 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
12646 rely on them. Bugfix on 0.2.1.30.
12647 - Use git revisions instead of svn revisions when generating our
12648 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
12650 o Minor features (also included in 0.2.2.x):
12651 - Adjust the expiration time on our SSL session certificates to
12652 better match SSL certs seen in the wild. Resolves ticket 4014.
12653 - Allow nameservers with IPv6 address. Resolves bug 2574.
12654 - Update to the October 4 2011 Maxmind GeoLite Country database.
12657 Changes in version 0.2.3.5-alpha - 2011-09-28
12658 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
12659 bridge relays; fixes an assertion error that many users started hitting
12660 today; and adds the ability to refill token buckets more often than
12661 once per second, allowing significant performance improvements.
12664 - Bridge relays now do their directory fetches inside Tor TLS
12665 connections, like all the other clients do, rather than connecting
12666 directly to the DirPort like public relays do. Removes another
12667 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
12668 - Bridges relays now build circuits for themselves in a more similar
12669 way to how clients build them. Removes another avenue for
12670 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
12671 when bridges were introduced.
12674 - Fix an "Assertion md->held_by_node == 1 failed" error that could
12675 occur when the same microdescriptor was referenced by two node_t
12676 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
12678 o Major features (networking):
12679 - Add a new TokenBucketRefillInterval option to refill token buckets
12680 more frequently than once per second. This should improve network
12681 performance, alleviate queueing problems, and make traffic less
12682 bursty. Implements proposal 183; closes ticket 3630. Design by
12683 Florian Tschorsch and Björn Scheuermann; implementation by
12687 - Change an integer overflow check in the OpenBSD_Malloc code so
12688 that GCC is less likely to eliminate it as impossible. Patch
12689 from Mansour Moufid. Fixes bug 4059.
12691 o Minor bugfixes (usability):
12692 - Downgrade log messages about circuit timeout calibration from
12693 "notice" to "info": they don't require or suggest any human
12694 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
12695 bugfix on 0.2.2.14-alpha.
12697 o Minor features (diagnostics):
12698 - When the system call to create a listener socket fails, log the
12699 error message explaining why. This may help diagnose bug 4027.
12702 Changes in version 0.2.3.4-alpha - 2011-09-13
12703 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
12704 tweak to Tor's TLS handshake that makes relays and bridges that run
12705 this new version reachable from Iran again. It also fixes a few new
12706 bugs in 0.2.3.x, and teaches relays to recognize when they're not
12707 listed in the network consensus and republish.
12709 o Major bugfixes (also part of 0.2.2.33):
12710 - Avoid an assertion failure when reloading a configuration with
12711 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
12712 3923; bugfix on 0.2.2.25-alpha.
12714 o Minor features (security, also part of 0.2.2.33):
12715 - Check for replays of the public-key encrypted portion of an
12716 INTRODUCE1 cell, in addition to the current check for replays of
12717 the g^x value. This prevents a possible class of active attacks
12718 by an attacker who controls both an introduction point and a
12719 rendezvous point, and who uses the malleability of AES-CTR to
12720 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
12721 that these attacks are infeasible (requiring the attacker to send
12722 on the order of zettabytes of altered cells in a short interval),
12723 but we'd rather block them off in case there are any classes of
12724 this attack that we missed. Reported by Willem Pinckaers.
12726 o Minor features (also part of 0.2.2.33):
12727 - Adjust the expiration time on our SSL session certificates to
12728 better match SSL certs seen in the wild. Resolves ticket 4014.
12729 - Change the default required uptime for a relay to be accepted as
12730 a HSDir (hidden service directory) from 24 hours to 25 hours.
12731 Improves on 0.2.0.10-alpha; resolves ticket 2649.
12732 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
12733 authorities to abstain from voting on assignment of the HSDir
12734 consensus flag. Related to bug 2649.
12735 - Update to the September 6 2011 Maxmind GeoLite Country database.
12737 o Minor bugfixes (also part of 0.2.2.33):
12738 - Demote the 'replay detected' log message emitted when a hidden
12739 service receives the same Diffie-Hellman public key in two different
12740 INTRODUCE2 cells to info level. A normal Tor client can cause that
12741 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
12742 fixes part of bug 2442.
12743 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
12744 level. There is nothing that a hidden service's operator can do
12745 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
12747 - Clarify a log message specifying the characters permitted in
12748 HiddenServiceAuthorizeClient client names. Previously, the log
12749 message said that "[A-Za-z0-9+-_]" were permitted; that could have
12750 given the impression that every ASCII character between "+" and "_"
12751 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
12753 o Build fixes (also part of 0.2.2.33):
12754 - Clean up some code issues that prevented Tor from building on older
12755 BSDs. Fixes bug 3894; reported by "grarpamp".
12756 - Search for a platform-specific version of "ar" when cross-compiling.
12757 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
12760 - Fix a bug where the SocksPort option (for example) would get
12761 ignored and replaced by the default if a SocksListenAddress
12762 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
12766 - Relays now try regenerating and uploading their descriptor more
12767 frequently if they are not listed in the consensus, or if the
12768 version of their descriptor listed in the consensus is too
12769 old. This fix should prevent situations where a server declines
12770 to re-publish itself because it has done so too recently, even
12771 though the authorities decided not to list its recent-enough
12772 descriptor. Fix for bug 3327.
12775 - Relays now include a reason for regenerating their descriptors
12776 in an HTTP header when uploading to the authorities. This will
12777 make it easier to debug descriptor-upload issues in the future.
12778 - When starting as root and then changing our UID via the User
12779 control option, and we have a ControlSocket configured, make sure
12780 that the ControlSocket is owned by the same account that Tor will
12781 run under. Implements ticket 3421; fix by Jérémy Bobbio.
12784 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
12785 utility function used in the control-port code). This shouldn't
12786 ever happen unless Tor is completely out of memory, but if it did
12787 happen and Tor somehow recovered from it, Tor could have sent a log
12788 message to a control port in the middle of a reply to a controller
12789 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
12790 - Make 'FetchUselessDescriptors' cause all descriptor types and
12791 all consensus types (including microdescriptors) to get fetched.
12792 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
12794 o Code refactoring:
12795 - Make a new "entry connection" struct as an internal subtype of "edge
12796 connection", to simplify the code and make exit connections smaller.
12799 Changes in version 0.2.2.33 - 2011-09-13
12800 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
12801 TLS handshake that makes relays and bridges that run this new version
12802 reachable from Iran again.
12805 - Avoid an assertion failure when reloading a configuration with
12806 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
12807 3923; bugfix on 0.2.2.25-alpha.
12809 o Minor features (security):
12810 - Check for replays of the public-key encrypted portion of an
12811 INTRODUCE1 cell, in addition to the current check for replays of
12812 the g^x value. This prevents a possible class of active attacks
12813 by an attacker who controls both an introduction point and a
12814 rendezvous point, and who uses the malleability of AES-CTR to
12815 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
12816 that these attacks are infeasible (requiring the attacker to send
12817 on the order of zettabytes of altered cells in a short interval),
12818 but we'd rather block them off in case there are any classes of
12819 this attack that we missed. Reported by Willem Pinckaers.
12822 - Adjust the expiration time on our SSL session certificates to
12823 better match SSL certs seen in the wild. Resolves ticket 4014.
12824 - Change the default required uptime for a relay to be accepted as
12825 a HSDir (hidden service directory) from 24 hours to 25 hours.
12826 Improves on 0.2.0.10-alpha; resolves ticket 2649.
12827 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
12828 authorities to abstain from voting on assignment of the HSDir
12829 consensus flag. Related to bug 2649.
12830 - Update to the September 6 2011 Maxmind GeoLite Country database.
12832 o Minor bugfixes (documentation and log messages):
12833 - Correct the man page to explain that HashedControlPassword and
12834 CookieAuthentication can both be set, in which case either method
12835 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
12836 when we decided to allow these config options to both be set. Issue
12837 raised by bug 3898.
12838 - Demote the 'replay detected' log message emitted when a hidden
12839 service receives the same Diffie-Hellman public key in two different
12840 INTRODUCE2 cells to info level. A normal Tor client can cause that
12841 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
12842 fixes part of bug 2442.
12843 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
12844 level. There is nothing that a hidden service's operator can do
12845 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
12847 - Clarify a log message specifying the characters permitted in
12848 HiddenServiceAuthorizeClient client names. Previously, the log
12849 message said that "[A-Za-z0-9+-_]" were permitted; that could have
12850 given the impression that every ASCII character between "+" and "_"
12851 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
12854 - Provide a substitute implementation of lround() for MSVC, which
12855 apparently lacks it. Patch from Gisle Vanem.
12856 - Clean up some code issues that prevented Tor from building on older
12857 BSDs. Fixes bug 3894; reported by "grarpamp".
12858 - Search for a platform-specific version of "ar" when cross-compiling.
12859 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
12862 Changes in version 0.2.3.3-alpha - 2011-09-01
12863 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
12864 security, and provides client-side support for the microdescriptor
12865 and optimistic data features introduced earlier in the 0.2.3.x
12866 series. It also includes numerous critical bugfixes in the (optional)
12867 bufferevent-based networking backend.
12869 o Major features (stream isolation):
12870 - You can now configure Tor so that streams from different
12871 applications are isolated on different circuits, to prevent an
12872 attacker who sees your streams as they leave an exit node from
12873 linking your sessions to one another. To do this, choose some way
12874 to distinguish the applications: have them connect to different
12875 SocksPorts, or have one of them use SOCKS4 while the other uses
12876 SOCKS5, or have them pass different authentication strings to the
12877 SOCKS proxy. Then, use the new SocksPort syntax to configure the
12878 degree of isolation you need. This implements Proposal 171.
12879 - There's a new syntax for specifying multiple client ports (such as
12880 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
12881 multiple *Port entries with full addr:port syntax on each.
12882 The old *ListenAddress format is still supported, but you can't
12883 mix it with the new *Port syntax.
12885 o Major features (other):
12886 - Enable microdescriptor fetching by default for clients. This allows
12887 clients to download a much smaller amount of directory information.
12888 To disable it (and go back to the old-style consensus and
12889 descriptors), set "UseMicrodescriptors 0" in your torrc file.
12890 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
12891 "PortForwarding" config option), now supports Windows.
12892 - When using an exit relay running 0.2.3.x, clients can now
12893 "optimistically" send data before the exit relay reports that
12894 the stream has opened. This saves a round trip when starting
12895 connections where the client speaks first (such as web browsing).
12896 This behavior is controlled by a consensus parameter (currently
12897 disabled). To turn it on or off manually, use the "OptimisticData"
12898 torrc option. Implements proposal 181; code by Ian Goldberg.
12900 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
12901 - When using IOCP on Windows, we need to enable Libevent windows
12903 - The IOCP backend now works even when the user has not specified
12904 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
12905 Fixes part of bug 3752.
12906 - Correctly record the bytes we've read and written when using
12907 bufferevents, so that we can include them in our bandwidth history
12908 and advertised bandwidth. Fixes bug 3803.
12909 - Apply rate-limiting only at the bottom of a chain of filtering
12910 bufferevents. This prevents us from filling up internal read
12911 buffers and violating rate-limits when filtering bufferevents
12912 are enabled. Fixes part of bug 3804.
12913 - Add high-watermarks to the output buffers for filtered
12914 bufferevents. This prevents us from filling up internal write
12915 buffers and wasting CPU cycles when filtering bufferevents are
12916 enabled. Fixes part of bug 3804.
12917 - Correctly notice when data has been written from a bufferevent
12918 without flushing it completely. Fixes bug 3805.
12919 - Fix a bug where server-side tunneled bufferevent-based directory
12920 streams would get closed prematurely. Fixes bug 3814.
12921 - Fix a use-after-free error with per-connection rate-limiting
12922 buckets. Fixes bug 3888.
12924 o Major bugfixes (also part of 0.2.2.31-rc):
12925 - If we're configured to write our ControlPorts to disk, only write
12926 them after switching UID and creating the data directory. This way,
12927 we don't fail when starting up with a nonexistent DataDirectory
12928 and a ControlPortWriteToFile setting based on that directory. Fixes
12929 bug 3747; bugfix on Tor 0.2.2.26-beta.
12932 - Added a new CONF_CHANGED event so that controllers can be notified
12933 of any configuration changes made by other controllers, or by the
12934 user. Implements ticket 1692.
12935 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
12936 leak when using bufferevents, and lets Libevent worry about how to
12937 best copy data out of a buffer.
12938 - Replace files in stats/ rather than appending to them. Now that we
12939 include statistics in extra-info descriptors, it makes no sense to
12940 keep old statistics forever. Implements ticket 2930.
12942 o Minor features (build compatibility):
12943 - Limited, experimental support for building with nmake and MSVC.
12944 - Provide a substitute implementation of lround() for MSVC, which
12945 apparently lacks it. Patch from Gisle Vanem.
12947 o Minor features (also part of 0.2.2.31-rc):
12948 - Update to the August 2 2011 Maxmind GeoLite Country database.
12950 o Minor bugfixes (on 0.2.3.x-alpha):
12951 - Fix a spurious warning when parsing SOCKS requests with
12952 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
12953 - Get rid of a harmless warning that could happen on relays running
12954 with bufferevents. The warning was caused by someone doing an http
12955 request to a relay's orport. Also don't warn for a few related
12956 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
12958 o Minor bugfixes (on 2.2.x and earlier):
12959 - Correct the man page to explain that HashedControlPassword and
12960 CookieAuthentication can both be set, in which case either method
12961 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
12962 when we decided to allow these config options to both be set. Issue
12963 raised by bug 3898.
12964 - The "--quiet" and "--hush" options now apply not only to Tor's
12965 behavior before logs are configured, but also to Tor's behavior in
12966 the absense of configured logs. Fixes bug 3550; bugfix on
12969 o Minor bugfixes (also part of 0.2.2.31-rc):
12970 - Write several files in text mode, on OSes that distinguish text
12971 mode from binary mode (namely, Windows). These files are:
12972 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
12973 that collect those statistics; 'client_keys' and 'hostname' for
12974 hidden services that use authentication; and (in the tor-gencert
12975 utility) newly generated identity and signing keys. Previously,
12976 we wouldn't specify text mode or binary mode, leading to an
12977 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
12978 the DirRecordUsageByCountry option which would have triggered
12979 the assertion failure was added), although this assertion failure
12980 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
12981 - Selectively disable deprecation warnings on OS X because Lion
12982 started deprecating the shipped copy of openssl. Fixes bug 3643.
12983 - Remove an extra pair of quotation marks around the error
12984 message in control-port STATUS_GENERAL BUG events. Bugfix on
12985 0.1.2.6-alpha; fixes bug 3732.
12986 - When unable to format an address as a string, report its value
12987 as "???" rather than reusing the last formatted address. Bugfix
12990 o Code simplifications and refactoring:
12991 - Rewrite the listener-selection logic so that parsing which ports
12992 we want to listen on is now separate from binding to the ports
12996 - Building Tor with bufferevent support now requires Libevent
12997 2.0.13-stable or later. Previous versions of Libevent had bugs in
12998 SSL-related bufferevents and related issues that would make Tor
12999 work badly with bufferevents. Requiring 2.0.13-stable also allows
13000 Tor with bufferevents to take advantage of Libevent APIs
13001 introduced after 2.0.8-rc.
13004 Changes in version 0.2.2.32 - 2011-08-27
13005 The Tor 0.2.2 release series is dedicated to the memory of Andreas
13006 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
13007 a founder of the PETS community, a leader in our field, a mentor,
13008 and a friend. He left us with these words: "I had the possibility
13009 to contribute to this world that is not as it should be. I hope I
13010 could help in some areas to make the world a better place, and that
13011 I could also encourage other people to be engaged in improving the
13012 world. Please, stay engaged. This world needs you, your love, your
13013 initiative -- now I cannot be part of that anymore."
13015 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
13016 ready. More than two years in the making, this release features improved
13017 client performance and hidden service reliability, better compatibility
13018 for Android, correct behavior for bridges that listen on more than
13019 one address, more extensible and flexible directory object handling,
13020 better reporting of network statistics, improved code security, and
13021 many many other features and bugfixes.
13024 Changes in version 0.2.2.31-rc - 2011-08-17
13025 Tor 0.2.2.31-rc is the second and hopefully final release candidate
13026 for the Tor 0.2.2.x series.
13029 - Remove an extra pair of quotation marks around the error
13030 message in control-port STATUS_GENERAL BUG events. Bugfix on
13031 0.1.2.6-alpha; fixes bug 3732.
13032 - If we're configured to write our ControlPorts to disk, only write
13033 them after switching UID and creating the data directory. This way,
13034 we don't fail when starting up with a nonexistent DataDirectory
13035 and a ControlPortWriteToFile setting based on that directory. Fixes
13036 bug 3747; bugfix on Tor 0.2.2.26-beta.
13039 - Update to the August 2 2011 Maxmind GeoLite Country database.
13042 - Allow GETINFO fingerprint to return a fingerprint even when
13043 we have not yet built a router descriptor. Fixes bug 3577;
13044 bugfix on 0.2.0.1-alpha.
13045 - Write several files in text mode, on OSes that distinguish text
13046 mode from binary mode (namely, Windows). These files are:
13047 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
13048 that collect those statistics; 'client_keys' and 'hostname' for
13049 hidden services that use authentication; and (in the tor-gencert
13050 utility) newly generated identity and signing keys. Previously,
13051 we wouldn't specify text mode or binary mode, leading to an
13052 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
13053 the DirRecordUsageByCountry option which would have triggered
13054 the assertion failure was added), although this assertion failure
13055 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
13056 - Selectively disable deprecation warnings on OS X because Lion
13057 started deprecating the shipped copy of openssl. Fixes bug 3643.
13058 - When unable to format an address as a string, report its value
13059 as "???" rather than reusing the last formatted address. Bugfix
13063 Changes in version 0.2.3.2-alpha - 2011-07-18
13064 Tor 0.2.3.2-alpha introduces two new experimental features:
13065 microdescriptors and pluggable transports. It also continues cleaning
13066 up a variety of recently introduced features.
13069 - Clients can now use microdescriptors instead of regular descriptors
13070 to build circuits. Microdescriptors are authority-generated
13071 summaries of regular descriptors' contents, designed to change
13072 very rarely (see proposal 158 for details). This feature is
13073 designed to save bandwidth, especially for clients on slow internet
13074 connections. It's off by default for now, since nearly no caches
13075 support it, but it will be on-by-default for clients in a future
13076 version. You can use the UseMicrodescriptors option to turn it on.
13077 - Tor clients using bridges can now be configured to use a separate
13078 'transport' proxy for each bridge. This approach helps to resist
13079 censorship by allowing bridges to use protocol obfuscation
13080 plugins. It implements part of proposal 180. Implements ticket 2841.
13081 - While we're trying to bootstrap, record how many TLS connections
13082 fail in each state, and report which states saw the most failures
13083 in response to any bootstrap failures. This feature may speed up
13084 diagnosis of censorship events. Implements ticket 3116.
13086 o Major bugfixes (on 0.2.3.1-alpha):
13087 - When configuring a large set of nodes in EntryNodes (as with
13088 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
13089 random subset to be guards, and choose them in random
13090 order. Fixes bug 2798.
13091 - Tor could crash when remembering a consensus in a non-used consensus
13092 flavor without having a current consensus set. Fixes bug 3361.
13093 - Comparing an unknown address to a microdescriptor's shortened exit
13094 policy would always give a "rejected" result. Fixes bug 3599.
13095 - Using microdescriptors as a client no longer prevents Tor from
13096 uploading and downloading hidden service descriptors. Fixes
13100 - Allow nameservers with IPv6 address. Resolves bug 2574.
13101 - Accept attempts to include a password authenticator in the
13102 handshake, as supported by SOCKS5. This handles SOCKS clients that
13103 don't know how to omit a password when authenticating. Resolves
13105 - When configuring a large set of nodes in EntryNodes, and there are
13106 enough of them listed as Guard so that we don't need to consider
13107 the non-guard entries, prefer the ones listed with the Guard flag.
13108 - Check for and recover from inconsistency in the microdescriptor
13109 cache. This will make it harder for us to accidentally free a
13110 microdescriptor without removing it from the appropriate data
13111 structures. Fixes issue 3135; issue noted by "wanoskarnet".
13112 - Log SSL state transitions at log level DEBUG, log domain
13113 HANDSHAKE. This can be useful for debugging censorship events.
13114 Implements ticket 3264.
13115 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
13116 implements ticket 3439.
13118 o Minor bugfixes (on 0.2.3.1-alpha):
13119 - Do not free all general-purpose regular descriptors just
13120 because microdescriptor use is enabled. Fixes bug 3113.
13121 - Correctly link libevent_openssl when --enable-static-libevent
13122 is passed to configure. Fixes bug 3118.
13123 - Bridges should not complain during their heartbeat log messages that
13124 they are unlisted in the consensus: that's more or less the point
13125 of being a bridge. Fixes bug 3183.
13126 - Report a SIGNAL event to controllers when acting on a delayed
13127 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
13128 event to the controller if we acted on a SIGNAL NEWNYM command
13129 immediately, and otherwise not report a SIGNAL event for the
13130 command at all. Fixes bug 3349.
13131 - Fix a crash when handling the SIGNAL controller command or
13132 reporting ERR-level status events with bufferevents enabled. Found
13133 by Robert Ransom. Fixes bug 3367.
13134 - Always ship the tor-fw-helper manpage in our release tarballs.
13135 Fixes bug 3389. Reported by Stephen Walker.
13136 - Fix a class of double-mark-for-close bugs when bufferevents
13137 are enabled. Fixes bug 3403.
13138 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
13139 - Add SIGNAL to the list returned by the 'GETINFO events/names'
13140 control-port command. Fixes part of bug 3465.
13141 - Prevent using negative indices during unit test runs when read_all()
13142 fails. Spotted by coverity.
13143 - Fix a rare memory leak when checking the nodelist without it being
13144 present. Found by coverity.
13145 - Only try to download a microdescriptor-flavored consensus from
13146 a directory cache that provides them.
13148 o Minor bugfixes (on 0.2.2.x and earlier):
13149 - Assert that hidden-service-related operations are not performed
13150 using single-hop circuits. Previously, Tor would assert that
13151 client-side streams are not attached to single-hop circuits,
13152 but not that other sensitive operations on the client and service
13153 side are not performed using single-hop circuits. Fixes bug 3332;
13155 - Don't publish a new relay descriptor when we reload our onion key,
13156 unless the onion key has actually changed. Fixes bug 3263 and
13157 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
13158 - Allow GETINFO fingerprint to return a fingerprint even when
13159 we have not yet built a router descriptor. Fixes bug 3577;
13160 bugfix on 0.2.0.1-alpha.
13161 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
13162 on 0.2.2.4-alpha; fixes bug 3427.
13164 o Code simplification and refactoring:
13165 - Use tor_sscanf() in place of scanf() in more places through the
13166 code. This makes us a little more locale-independent, and
13167 should help shut up code-analysis tools that can't tell
13168 a safe sscanf string from a dangerous one.
13169 - Use tt_assert(), not tor_assert(), for checking for test failures.
13170 This makes the unit tests more able to go on in the event that
13172 - Split connection_about_to_close() into separate functions for each
13176 - On Windows, we now define the _WIN32_WINNT macros only if they
13177 are not already defined. This lets the person building Tor decide,
13178 if they want, to require a later version of Windows.
13181 Changes in version 0.2.2.30-rc - 2011-07-07
13182 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
13183 series. It fixes a few smaller bugs, but generally appears stable.
13184 Please test it and let us know whether it is!
13187 - Send a SUCCEEDED stream event to the controller when a reverse
13188 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
13189 discovered by katmagic.
13190 - Always NUL-terminate the sun_path field of a sockaddr_un before
13191 passing it to the kernel. (Not a security issue: kernels are
13192 smart enough to reject bad sockaddr_uns.) Found by Coverity;
13193 CID #428. Bugfix on Tor 0.2.0.3-alpha.
13194 - Don't stack-allocate the list of supplementary GIDs when we're
13195 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
13196 could take up to 256K, which is way too much stack. Found by
13197 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
13198 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
13199 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
13200 fixes part of bug 3465.
13201 - Fix a memory leak when receiving a descriptor for a hidden
13202 service we didn't ask for. Found by Coverity; CID #30. Bugfix
13206 - Update to the July 1 2011 Maxmind GeoLite Country database.
13209 Changes in version 0.2.2.29-beta - 2011-06-20
13210 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
13211 have bridge lines in their torrc but don't want to use them; gets
13212 us closer to having the control socket feature working on Debian;
13213 and fixes a variety of smaller bugs.
13216 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
13217 When we changed the default behavior to "use bridges if any
13218 are listed in the torrc", we surprised users who had bridges
13219 in their torrc files but who didn't actually want to use them.
13220 Partial resolution for bug 3354.
13223 - Don't attach new streams to old rendezvous circuits after SIGNAL
13224 NEWNYM. Previously, we would keep using an existing rendezvous
13225 circuit if it remained open (i.e. if it were kept open by a
13226 long-lived stream, or if a new stream were attached to it before
13227 Tor could notice that it was old and no longer in use). Bugfix on
13228 0.1.1.15-rc; fixes bug 3375.
13231 - Fix a bug when using ControlSocketsGroupWritable with User. The
13232 directory's group would be checked against the current group, not
13233 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
13234 bugfix on 0.2.2.26-beta.
13235 - Make connection_printf_to_buf()'s behavior sane. Its callers
13236 expect it to emit a CRLF iff the format string ends with CRLF;
13237 it actually emitted a CRLF iff (a) the format string ended with
13238 CRLF or (b) the resulting string was over 1023 characters long or
13239 (c) the format string did not end with CRLF *and* the resulting
13240 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
13241 fixes part of bug 3407.
13242 - Make send_control_event_impl()'s behavior sane. Its callers
13243 expect it to always emit a CRLF at the end of the string; it
13244 might have emitted extra control characters as well. Bugfix on
13245 0.1.1.9-alpha; fixes another part of bug 3407.
13246 - Make crypto_rand_int() check the value of its input correctly.
13247 Previously, it accepted values up to UINT_MAX, but could return a
13248 negative number if given a value above INT_MAX+1. Found by George
13249 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
13250 - Avoid a segfault when reading a malformed circuit build state
13251 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
13253 - When asked about a DNS record type we don't support via a
13254 client DNSPort, reply with NOTIMPL rather than an empty
13255 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
13256 - Fix a rare memory leak during stats writing. Found by coverity.
13259 - Update to the June 1 2011 Maxmind GeoLite Country database.
13261 o Code simplifications and refactoring:
13262 - Remove some dead code as indicated by coverity.
13263 - Remove a few dead assignments during router parsing. Found by
13265 - Add some forgotten return value checks during unit tests. Found
13267 - Don't use 1-bit wide signed bit fields. Found by coverity.
13270 Changes in version 0.2.2.28-beta - 2011-06-04
13271 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
13272 fixed a big bug in whether relays stay in the consensus consistently,
13273 we moved closer to handling bridges and hidden services correctly,
13274 and we started the process of better handling the dreaded "my Vidalia
13275 died, and now my Tor demands a password when I try to reconnect to it"
13279 - Don't decide to make a new descriptor when receiving a HUP signal.
13280 This bug has caused a lot of 0.2.2.x relays to disappear from the
13281 consensus periodically. Fixes the most common case of triggering
13282 bug 1810; bugfix on 0.2.2.7-alpha.
13283 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
13284 - Don't try to build descriptors if "ORPort auto" is set and we
13285 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
13287 - Resolve a crash that occurred when setting BridgeRelay to 1 with
13288 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
13289 - Apply circuit timeouts to opened hidden-service-related circuits
13290 based on the correct start time. Previously, we would apply the
13291 circuit build timeout based on time since the circuit's creation;
13292 it was supposed to be applied based on time since the circuit
13293 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
13294 - Use the same circuit timeout for client-side introduction
13295 circuits as for other four-hop circuits, rather than the timeout
13296 for single-hop directory-fetch circuits; the shorter timeout may
13297 have been appropriate with the static circuit build timeout in
13298 0.2.1.x and earlier, but caused many hidden service access attempts
13299 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
13300 on 0.2.2.2-alpha; fixes another part of bug 1297.
13301 - In ticket 2511 we fixed a case where you could use an unconfigured
13302 bridge if you had configured it as a bridge the last time you ran
13303 Tor. Now fix another edge case: if you had configured it as a bridge
13304 but then switched to a different bridge via the controller, you
13305 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
13309 - Add an __OwningControllerProcess configuration option and a
13310 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
13311 that when it exits, Tor will shut down. Implements feature 3049.
13312 - If "UseBridges 1" is set and no bridges are configured, Tor will
13313 now refuse to build any circuits until some bridges are set.
13314 If "UseBridges auto" is set, Tor will use bridges if they are
13315 configured and we are not running as a server, but otherwise will
13316 make circuits as usual. The new default is "auto". Patch by anonym,
13317 so the Tails LiveCD can stop automatically revealing you as a Tor
13321 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
13322 - Remove a trailing asterisk from "exit-policy/default" in the
13323 output of the control port command "GETINFO info/names". Bugfix
13325 - Use a wide type to hold sockets when built for 64-bit Windows builds.
13327 - Warn when the user configures two HiddenServiceDir lines that point
13328 to the same directory. Bugfix on 0.0.6 (the version introducing
13329 HiddenServiceDir); fixes bug 3289.
13330 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
13331 part of bug 2748; bugfix on 0.2.0.10-alpha.
13332 - Log malformed requests for rendezvous descriptors as protocol
13333 warnings, not warnings. Also, use a more informative log message
13334 in case someone sees it at log level warning without prior
13335 info-level messages. Fixes the other part of bug 2748; bugfix
13337 - Clear the table recording the time of the last request for each
13338 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
13339 Previously, we would clear our HS descriptor cache on SIGNAL
13340 NEWNYM, but if we had previously retrieved a descriptor (or tried
13341 to) from every directory responsible for it, we would refuse to
13342 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
13344 - Fix a log message that said "bits" while displaying a value in
13345 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
13347 - When checking for 1024-bit keys, check for 1024 bits, not 128
13348 bytes. This allows Tor to correctly discard keys of length 1017
13349 through 1023. Bugfix on 0.0.9pre5.
13352 - Relays now log the reason for publishing a new relay descriptor,
13353 so we have a better chance of hunting down instances of bug 1810.
13354 Resolves ticket 3252.
13355 - Revise most log messages that refer to nodes by nickname to
13356 instead use the "$key=nickname at address" format. This should be
13357 more useful, especially since nicknames are less and less likely
13358 to be unique. Resolves ticket 3045.
13359 - Log (at info level) when purging pieces of hidden-service-client
13360 state because of SIGNAL NEWNYM.
13363 - Remove undocumented option "-F" from tor-resolve: it hasn't done
13364 anything since 0.2.1.16-rc.
13367 Changes in version 0.2.2.27-beta - 2011-05-18
13368 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
13369 release, and also adds a few more general bugfixes.
13372 - Fix a crash bug when changing bridges in a running Tor process.
13373 Fixes bug 3213; bugfix on 0.2.2.26-beta.
13374 - When the controller configures a new bridge, don't wait 10 to 60
13375 seconds before trying to fetch its descriptor. Bugfix on
13376 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
13379 - Require that onion keys have exponent 65537 in microdescriptors too.
13380 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
13381 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
13382 Changed the limit to 512 characters by removing base64 newlines.
13383 Fixes bug 2752. Fix by Michael Yakubovich.
13384 - When a client starts or stops using bridges, never use a circuit
13385 that was built before the configuration change. This behavior could
13386 put at risk a user who uses bridges to ensure that her traffic
13387 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
13391 Changes in version 0.2.2.26-beta - 2011-05-17
13392 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
13393 also introduces a new "socksport auto" approach that should make it
13394 easier to run multiple Tors on the same system, and does a lot of
13395 cleanup to get us closer to a release candidate.
13397 o Security/privacy fixes:
13398 - Replace all potentially sensitive memory comparison operations
13399 with versions whose runtime does not depend on the data being
13400 compared. This will help resist a class of attacks where an
13401 adversary can use variations in timing information to learn
13402 sensitive data. Fix for one case of bug 3122. (Safe memcmp
13403 implementation by Robert Ransom based partially on code by DJB.)
13404 - When receiving a hidden service descriptor, check that it is for
13405 the hidden service we wanted. Previously, Tor would store any
13406 hidden service descriptors that a directory gave it, whether it
13407 wanted them or not. This wouldn't have let an attacker impersonate
13408 a hidden service, but it did let directories pre-seed a client
13409 with descriptors that it didn't want. Bugfix on 0.0.6.
13410 - On SIGHUP, do not clear out all TrackHostExits mappings, client
13411 DNS cache entries, and virtual address mappings: that's what
13412 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
13415 - The options SocksPort, ControlPort, and so on now all accept a
13416 value "auto" that opens a socket on an OS-selected port. A
13417 new ControlPortWriteToFile option tells Tor to write its
13418 actual control port or ports to a chosen file. If the option
13419 ControlPortFileGroupReadable is set, the file is created as
13420 group-readable. Now users can run two Tor clients on the same
13421 system without needing to manually mess with parameters. Resolves
13422 part of ticket 3076.
13423 - Set SO_REUSEADDR on all sockets, not just listeners. This should
13424 help busy exit nodes avoid running out of useable ports just
13425 because all the ports have been used in the near past. Resolves
13429 - New "GETINFO net/listeners/(type)" controller command to return
13430 a list of addresses and ports that are bound for listeners for a
13431 given connection type. This is useful when the user has configured
13432 "SocksPort auto" and the controller needs to know which port got
13433 chosen. Resolves another part of ticket 3076.
13434 - Add a new ControlSocketsGroupWritable configuration option: when
13435 it is turned on, ControlSockets are group-writeable by the default
13436 group of the current user. Patch by Jérémy Bobbio; implements
13438 - Tor now refuses to create a ControlSocket in a directory that is
13439 world-readable (or group-readable if ControlSocketsGroupWritable
13440 is 0). This is necessary because some operating systems do not
13441 enforce permissions on an AF_UNIX sockets. Permissions on the
13442 directory holding the socket, however, seems to work everywhere.
13443 - Rate-limit a warning about failures to download v2 networkstatus
13444 documents. Resolves part of bug 1352.
13445 - Backport code from 0.2.3.x that allows directory authorities to
13446 clean their microdescriptor caches. Needed to resolve bug 2230.
13447 - When an HTTPS proxy reports "403 Forbidden", we now explain
13448 what it means rather than calling it an unexpected status code.
13449 Closes bug 2503. Patch from Michael Yakubovich.
13450 - Update to the May 1 2011 Maxmind GeoLite Country database.
13453 - Authorities now clean their microdesc cache periodically and when
13454 reading from disk initially, not only when adding new descriptors.
13455 This prevents a bug where we could lose microdescriptors. Bugfix
13456 on 0.2.2.6-alpha. Fixes bug 2230.
13457 - Do not crash when our configuration file becomes unreadable, for
13458 example due to a permissions change, between when we start up
13459 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
13461 - Avoid a bug that would keep us from replacing a microdescriptor
13462 cache on Windows. (We would try to replace the file while still
13463 holding it open. That's fine on Unix, but Windows doesn't let us
13464 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
13465 - Add missing explanations for the authority-related torrc options
13466 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
13467 man page. Resolves issue 2379.
13468 - As an authority, do not upload our own vote or signature set to
13469 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
13470 it would get flagged as a duplicate. Resolves bug 3026.
13471 - Accept hidden service descriptors if we think we might be a hidden
13472 service directory, regardless of what our consensus says. This
13473 helps robustness, since clients and hidden services can sometimes
13474 have a more up-to-date view of the network consensus than we do,
13475 and if they think that the directory authorities list us a HSDir,
13476 we might actually be one. Related to bug 2732; bugfix on
13478 - When a controller changes TrackHostExits, remove mappings for
13479 hosts that should no longer have their exits tracked. Bugfix on
13481 - When a controller changes VirtualAddrNetwork, remove any mappings
13482 for hosts that were automapped to the old network. Bugfix on
13484 - When a controller changes one of the AutomapHosts* options, remove
13485 any mappings for hosts that should no longer be automapped. Bugfix
13487 - Do not reset the bridge descriptor download status every time we
13488 re-parse our configuration or get a configuration change. Fixes
13489 bug 3019; bugfix on 0.2.0.3-alpha.
13491 o Minor bugfixes (code cleanup):
13492 - When loading the microdesc journal, remember its current size.
13493 In 0.2.2, this helps prevent the microdesc journal from growing
13494 without limit on authorities (who are the only ones to use it in
13495 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
13496 Fix posted by "cypherpunks."
13497 - The microdesc journal is supposed to get rebuilt only if it is
13498 at least _half_ the length of the store, not _twice_ the length
13499 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
13500 - Fix a potential null-pointer dereference while computing a
13501 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
13503 - Avoid a possible null-pointer dereference when rebuilding the mdesc
13504 cache without actually having any descriptors to cache. Bugfix on
13505 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
13506 - If we fail to compute the identity digest of a v3 legacy keypair,
13507 warn, and don't use a buffer-full of junk instead. Bugfix on
13508 0.2.1.1-alpha; fixes bug 3106.
13509 - Resolve an untriggerable issue in smartlist_string_num_isin(),
13510 where if the function had ever in the future been used to check
13511 for the presence of a too-large number, it would have given an
13512 incorrect result. (Fortunately, we only used it for 16-bit
13513 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
13514 - Require that introduction point keys and onion handshake keys
13515 have a public exponent of 65537. Starts to fix bug 3207; bugfix
13518 o Removed features:
13519 - Caches no longer download and serve v2 networkstatus documents
13520 unless FetchV2Networkstatus flag is set: these documents haven't
13521 haven't been used by clients or relays since 0.2.0.x. Resolves
13525 Changes in version 0.2.3.1-alpha - 2011-05-05
13526 Tor 0.2.3.1-alpha adds some new experimental features, including support
13527 for an improved network IO backend, IOCP networking on Windows,
13528 microdescriptor caching, "fast-start" support for streams, and automatic
13529 home router configuration. There are also numerous internal improvements
13530 to try to make the code easier for developers to work with.
13532 This is the first alpha release in a new series, so expect there to be
13533 bugs. Users who would rather test out a more stable branch should
13534 stay with 0.2.2.x for now.
13537 - Tor can now optionally build with the "bufferevents" buffered IO
13538 backend provided by Libevent 2. To use this feature, make sure you
13539 have the latest possible version of Libevent, and pass the
13540 --enable-bufferevents flag to configure when building Tor from
13541 source. This feature will make our networking code more flexible,
13542 let us stack layers on each other, and let us use more efficient
13543 zero-copy transports where available.
13544 - As an experimental feature, Tor can use IOCP for networking on Windows.
13545 Once this code is tuned and optimized, it promises much better
13546 performance than the select-based backend we've used in the past. To
13547 try this feature, you must build Tor with Libevent 2, configure Tor
13548 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
13549 your torrc. There are known bugs here: only try this if you can help
13550 debug it as it breaks.
13551 - The EntryNodes option can now include country codes like {de} or IP
13552 addresses or network masks. Previously we had disallowed these options
13553 because we didn't have an efficient way to keep the list up to
13554 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
13555 - Exit nodes now accept and queue data on not-yet-connected streams.
13556 Previously, the client wasn't allowed to send data until the stream was
13557 connected, which slowed down all connections. This change will enable
13558 clients to perform a "fast-start" on streams and send data without
13559 having to wait for a confirmation that the stream has opened. (Patch
13560 from Ian Goldberg; implements the server side of Proposal 174.)
13561 - Tor now has initial support for automatic port mapping on the many
13562 home routers that support NAT-PMP or UPnP. (Not yet supported on
13563 Windows). To build the support code, you'll need to have libnatpnp
13564 library and/or the libminiupnpc library, and you'll need to enable the
13565 feature specifically by passing "--enable-upnp" and/or
13566 "--enable-natpnp" to configure. To turn it on, use the new
13567 PortForwarding option.
13568 - Caches now download, cache, and serve multiple "flavors" of the
13569 consensus, including a flavor that describes microdescriptors.
13570 - Caches now download, cache, and serve microdescriptors -- small
13571 summaries of router descriptors that are authenticated by all of the
13572 directory authorities. Once enough caches are running this code,
13573 clients will be able to save significant amounts of directory bandwidth
13574 by downloading microdescriptors instead of router descriptors.
13577 - Make logging resolution configurable with a new LogTimeGranularity
13578 option, and change the default from 1 millisecond to 1 second.
13579 Implements enhancement 1668.
13580 - We log which torrc file we're using on startup. Implements ticket
13582 - Ordinarily, Tor does not count traffic from private addresses (like
13583 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
13584 There is now a new option, CountPrivateBandwidth, to disable this
13585 behavior. Patch from Daniel Cagara.
13586 - New --enable-static-tor configure option for building Tor as
13587 statically as possible. Idea, general hackery and thoughts from
13588 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
13590 - If you set the NumCPUs option to 0, Tor will now try to detect how
13591 many CPUs you have. This is the new default behavior.
13592 - Turn on directory request statistics by default and include them in
13593 extra-info descriptors. Don't break if we have no GeoIP database.
13594 - Relays that set "ConnDirectionStatistics 1" write statistics on the
13595 bidirectional use of connections to disk every 24 hours.
13596 - Add a GeoIP file digest to the extra-info descriptor. Implements
13598 - The NodeFamily option -- which let you declare that you want to
13599 consider nodes to be part of a family whether they list themselves
13600 that way or not -- now allows IP address ranges and country codes.
13601 - Add a new 'Heartbeat' log message type to periodically log a message
13602 describing Tor's status at level Notice. This feature is meant for
13603 operators who log at notice, and want to make sure that their Tor
13604 server is still working. Implementation by George Kadianakis.
13606 o Minor bugfixes (on 0.2.2.25-alpha):
13607 - When loading the microdesc journal, remember its current size.
13608 In 0.2.2, this helps prevent the microdesc journal from growing
13609 without limit on authorities (who are the only ones to use it in
13610 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
13611 Fix posted by "cypherpunks."
13612 - The microdesc journal is supposed to get rebuilt only if it is
13613 at least _half_ the length of the store, not _twice_ the length
13614 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
13615 - If as an authority we fail to compute the identity digest of a v3
13616 legacy keypair, warn, and don't use a buffer-full of junk instead.
13617 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
13618 - Authorities now clean their microdesc cache periodically and when
13619 reading from disk initially, not only when adding new descriptors.
13620 This prevents a bug where we could lose microdescriptors. Bugfix
13623 o Minor features (controller):
13624 - Add a new SIGNAL event to the controller interface so that
13625 controllers can be notified when Tor handles a signal. Resolves
13626 issue 1955. Patch by John Brooks.
13627 - Add a new GETINFO option to get total bytes read and written. Patch
13628 from pipe, revised by atagar. Resolves ticket 2345.
13629 - Implement some GETINFO controller fields to provide information about
13630 the Tor process's pid, euid, username, and resource limits.
13633 - Our build system requires automake 1.6 or later to create the
13634 Makefile.in files. Previously, you could have used 1.4.
13635 This only affects developers and people building Tor from git;
13636 people who build Tor from the source distribution without changing
13637 the Makefile.am files should be fine.
13638 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
13639 so on. This is more robust against some of the failure modes
13640 associated with running the autotools pieces on their own.
13642 o Minor packaging issues:
13643 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
13644 already created. Patch from Andreas Stieger. Fixes bug 2573.
13646 o Code simplifications and refactoring:
13647 - A major revision to our internal node-selecting and listing logic.
13648 Tor already had at least two major ways to look at the question of
13649 "which Tor servers do we know about": a list of router descriptors,
13650 and a list of entries in the current consensus. With
13651 microdescriptors, we're adding a third. Having so many systems
13652 without an abstraction layer over them was hurting the codebase.
13653 Now, we have a new "node_t" abstraction that presents a consistent
13654 interface to a client's view of a Tor node, and holds (nearly) all
13655 of the mutable state formerly in routerinfo_t and routerstatus_t.
13656 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
13657 no longer link against Libevent: they never used it, but
13658 our library structure used to force them to link it.
13660 o Removed features:
13661 - Remove some old code to work around even older versions of Tor that
13662 used forked processes to handle DNS requests. Such versions of Tor
13663 are no longer in use as servers.
13665 o Documentation fixes:
13666 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
13667 - Add missing documentation for the authority-related torrc options
13668 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
13672 Changes in version 0.2.2.25-alpha - 2011-04-29
13673 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
13674 robust, routers no longer overreport their bandwidth, Win7 should crash
13675 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
13676 now prevents hidden service-related activity from being linkable. It
13677 provides more information to Vidalia so you can see if your bridge is
13678 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
13679 StrictNodes configuration options to make them more reliable, more
13680 understandable, and more regularly applied. If you use those options,
13681 please see the revised documentation for them in the manual page.
13684 - Relays were publishing grossly inflated bandwidth values because
13685 they were writing their state files wrong--now they write the
13686 correct value. Also, resume reading bandwidth history from the
13687 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
13688 - Improve hidden service robustness: When we find that we have
13689 extended a hidden service's introduction circuit to a relay not
13690 listed as an introduction point in the HS descriptor we currently
13691 have, retry with an introduction point from the current
13692 descriptor. Previously we would just give up. Fixes bugs 1024 and
13693 1930; bugfix on 0.2.0.10-alpha.
13694 - Clients now stop trying to use an exit node associated with a given
13695 destination by TrackHostExits if they fail to reach that exit node.
13696 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
13697 - Fix crash bug on platforms where gmtime and localtime can return
13698 NULL. Windows 7 users were running into this one. Fixes part of bug
13699 2077. Bugfix on all versions of Tor. Found by boboper.
13701 o Security and stability fixes:
13702 - Don't double-free a parsable, but invalid, microdescriptor, even if
13703 it is followed in the blob we're parsing by an unparsable
13704 microdescriptor. Fixes an issue reported in a comment on bug 2954.
13705 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
13706 - If the Nickname configuration option isn't given, Tor would pick a
13707 nickname based on the local hostname as the nickname for a relay.
13708 Because nicknames are not very important in today's Tor and the
13709 "Unnamed" nickname has been implemented, this is now problematic
13710 behavior: It leaks information about the hostname without being
13711 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
13712 introduced the Unnamed nickname. Reported by tagnaq.
13713 - Fix an uncommon assertion failure when running with DNSPort under
13714 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
13715 - Avoid linkability based on cached hidden service descriptors: forget
13716 all hidden service descriptors cached as a client when processing a
13717 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
13720 - Export GeoIP information on bridge usage to controllers even if we
13721 have not yet been running for 24 hours. Now Vidalia bridge operators
13722 can get more accurate and immediate feedback about their
13723 contributions to the network.
13725 o Major features and bugfixes (node selection):
13726 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
13727 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
13728 options. Previously, we had been ambiguous in describing what
13729 counted as an "exit" node, and what operations exactly "StrictNodes
13730 0" would permit. This created confusion when people saw nodes built
13731 through unexpected circuits, and made it hard to tell real bugs from
13732 surprises. Now the intended behavior is:
13733 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
13734 a node that delivers user traffic outside the Tor network.
13735 . "Entry", in the context of EntryNodes, means a node used as the
13736 first hop of a multihop circuit. It doesn't include direct
13737 connections to directory servers.
13738 . "ExcludeNodes" applies to all nodes.
13739 . "StrictNodes" changes the behavior of ExcludeNodes only. When
13740 StrictNodes is set, Tor should avoid all nodes listed in
13741 ExcludeNodes, even when it will make user requests fail. When
13742 StrictNodes is *not* set, then Tor should follow ExcludeNodes
13743 whenever it can, except when it must use an excluded node to
13744 perform self-tests, connect to a hidden service, provide a
13745 hidden service, fulfill a .exit request, upload directory
13746 information, or fetch directory information.
13747 Collectively, the changes to implement the behavior fix bug 1090.
13748 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
13749 a node is listed in both, it's treated as excluded.
13750 - ExcludeNodes now applies to directory nodes -- as a preference if
13751 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
13752 Don't exclude all the directory authorities and set StrictNodes to 1
13753 unless you really want your Tor to break.
13754 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
13755 - ExcludeExitNodes now overrides .exit requests.
13756 - We don't use bridges listed in ExcludeNodes.
13757 - When StrictNodes is 1:
13758 . We now apply ExcludeNodes to hidden service introduction points
13759 and to rendezvous points selected by hidden service users. This
13760 can make your hidden service less reliable: use it with caution!
13761 . If we have used ExcludeNodes on ourself, do not try relay
13762 reachability self-tests.
13763 . If we have excluded all the directory authorities, we will not
13764 even try to upload our descriptor if we're a relay.
13765 . Do not honor .exit requests to an excluded node.
13766 - Remove a misfeature that caused us to ignore the Fast/Stable flags
13767 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
13768 - When the set of permitted nodes changes, we now remove any mappings
13769 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
13771 - We never cannibalize a circuit that had excluded nodes on it, even
13772 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
13773 - Revert a change where we would be laxer about attaching streams to
13774 circuits than when building the circuits. This was meant to prevent
13775 a set of bugs where streams were never attachable, but our improved
13776 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
13777 - Keep track of how many times we launch a new circuit to handle a
13778 given stream. Too many launches could indicate an inconsistency
13779 between our "launch a circuit to handle this stream" logic and our
13780 "attach this stream to one of the available circuits" logic.
13781 - Improve log messages related to excluded nodes.
13784 - Fix a spurious warning when moving from a short month to a long
13785 month on relays with month-based BandwidthAccounting. Bugfix on
13786 0.2.2.17-alpha; fixes bug 3020.
13787 - When a client finds that an origin circuit has run out of 16-bit
13788 stream IDs, we now mark it as unusable for new streams. Previously,
13789 we would try to close the entire circuit. Bugfix on 0.0.6.
13790 - Add a forgotten cast that caused a compile warning on OS X 10.6.
13791 Bugfix on 0.2.2.24-alpha.
13792 - Be more careful about reporting the correct error from a failed
13793 connect() system call. Under some circumstances, it was possible to
13794 look at an incorrect value for errno when sending the end reason.
13795 Bugfix on 0.1.0.1-rc.
13796 - Correctly handle an "impossible" overflow cases in connection byte
13797 counting, where we write or read more than 4GB on an edge connection
13798 in a single second. Bugfix on 0.1.2.8-beta.
13799 - Correct the warning displayed when a rendezvous descriptor exceeds
13800 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
13802 - Clients and hidden services now use HSDir-flagged relays for hidden
13803 service descriptor downloads and uploads even if the relays have no
13804 DirPort set and the client has disabled TunnelDirConns. This will
13805 eventually allow us to give the HSDir flag to relays with no
13806 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
13807 - Downgrade "no current certificates known for authority" message from
13808 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
13809 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
13810 2917. Bugfix on 0.1.1.1-alpha.
13811 - Only limit the lengths of single HS descriptors, even when multiple
13812 HS descriptors are published to an HSDir relay in a single POST
13813 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
13814 - Write the current time into the LastWritten line in our state file,
13815 rather than the time from the previous write attempt. Also, stop
13816 trying to use a time of -1 in our log statements. Fixes bug 3039;
13817 bugfix on 0.2.2.14-alpha.
13818 - Be more consistent in our treatment of file system paths. "~" should
13819 get expanded to the user's home directory in the Log config option.
13820 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
13821 feature for the -f and --DataDirectory options.
13824 - Make sure every relay writes a state file at least every 12 hours.
13825 Previously, a relay could go for weeks without writing its state
13826 file, and on a crash could lose its bandwidth history, capacity
13827 estimates, client country statistics, and so on. Addresses bug 3012.
13828 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
13829 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
13830 clients are already deprecated because of security bugs.
13831 - Don't allow v0 hidden service authorities to act as clients.
13832 Required by fix for bug 3000.
13833 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
13834 by fix for bug 3000.
13835 - Ensure that no empty [dirreq-](read|write)-history lines are added
13836 to an extrainfo document. Implements ticket 2497.
13838 o Code simplification and refactoring:
13839 - Remove workaround code to handle directory responses from servers
13840 that had bug 539 (they would send HTTP status 503 responses _and_
13841 send a body too). Since only server versions before
13842 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
13843 keep the workaround in place.
13844 - Remove the old 'fuzzy time' logic. It was supposed to be used for
13845 handling calculations where we have a known amount of clock skew and
13846 an allowed amount of unknown skew. But we only used it in three
13847 places, and we never adjusted the known/unknown skew values. This is
13848 still something we might want to do someday, but if we do, we'll
13849 want to do it differently.
13850 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
13851 None of the cases where we did this before were wrong, but by making
13852 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
13853 - Use GetTempDir to find the proper temporary directory location on
13854 Windows when generating temporary files for the unit tests. Patch by
13858 Changes in version 0.2.2.24-alpha - 2011-04-08
13859 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
13860 prevented Tor clients from effectively using "multihomed" bridges,
13861 that is, bridges that listen on multiple ports or IP addresses so users
13862 can continue to use some of their addresses even if others get blocked.
13865 - Fix a bug where bridge users who configure the non-canonical
13866 address of a bridge automatically switch to its canonical
13867 address. If a bridge listens at more than one address, it should be
13868 able to advertise those addresses independently and any non-blocked
13869 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
13871 - If you configured Tor to use bridge A, and then quit and
13872 configured Tor to use bridge B instead, it would happily continue
13873 to use bridge A if it's still reachable. While this behavior is
13874 a feature if your goal is connectivity, in some scenarios it's a
13875 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
13876 - Directory authorities now use data collected from their own
13877 uptime observations when choosing whether to assign the HSDir flag
13878 to relays, instead of trusting the uptime value the relay reports in
13879 its descriptor. This change helps prevent an attack where a small
13880 set of nodes with frequently-changing identity keys can blackhole
13881 a hidden service. (Only authorities need upgrade; others will be
13882 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
13885 - When we restart our relay, we might get a successful connection
13886 from the outside before we've started our reachability tests,
13887 triggering a warning: "ORPort found reachable, but I have no
13888 routerinfo yet. Failing to inform controller of success." This
13889 bug was harmless unless Tor is running under a controller
13890 like Vidalia, in which case the controller would never get a
13891 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
13893 - Make directory authorities more accurate at recording when
13894 relays that have failed several reachability tests became
13895 unreachable, so we can provide more accuracy at assigning Stable,
13896 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
13897 - Fix an issue that prevented static linking of libevent on
13898 some platforms (notably Linux). Fixes bug 2698; bugfix on
13899 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
13900 the --with-static-libevent configure option).
13901 - We now ask the other side of a stream (the client or the exit)
13902 for more data on that stream when the amount of queued data on
13903 that stream dips low enough. Previously, we wouldn't ask the
13904 other side for more data until either it sent us more data (which
13905 it wasn't supposed to do if it had exhausted its window!) or we
13906 had completely flushed all our queued data. This flow control fix
13907 should improve throughput. Fixes bug 2756; bugfix on the earliest
13908 released versions of Tor (svn commit r152).
13909 - Avoid a double-mark-for-free warning when failing to attach a
13910 transparent proxy connection. (We thought we had fixed this in
13911 0.2.2.23-alpha, but it turns out our fix was checking the wrong
13912 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
13913 bug) and 0.2.2.23-alpha (the incorrect fix).
13914 - When warning about missing zlib development packages during compile,
13915 give the correct package names. Bugfix on 0.2.0.1-alpha.
13918 - Directory authorities now log the source of a rejected POSTed v3
13919 networkstatus vote.
13920 - Make compilation with clang possible when using
13921 --enable-gcc-warnings by removing two warning options that clang
13922 hasn't implemented yet and by fixing a few warnings. Implements
13924 - When expiring circuits, use microsecond timers rather than
13925 one-second timers. This can avoid an unpleasant situation where a
13926 circuit is launched near the end of one second and expired right
13927 near the beginning of the next, and prevent fluctuations in circuit
13929 - Use computed circuit-build timeouts to decide when to launch
13930 parallel introduction circuits for hidden services. (Previously,
13931 we would retry after 15 seconds.)
13932 - Update to the April 1 2011 Maxmind GeoLite Country database.
13935 - Create the /var/run/tor directory on startup on OpenSUSE if it is
13936 not already created. Patch from Andreas Stieger. Fixes bug 2573.
13938 o Documentation changes:
13939 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
13940 - Resolve all doxygen warnings except those for missing documentation.
13942 - Add doxygen documentation for more functions, fields, and types.
13945 Changes in version 0.2.2.23-alpha - 2011-03-08
13946 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
13947 they restart they don't lose their bandwidth capacity estimate. This
13948 release also fixes a diverse set of user-facing bugs, ranging from
13949 relays overrunning their rate limiting to clients falsely warning about
13950 clock skew to bridge descriptor leaks by our bridge directory authority.
13953 - Stop sending a CLOCK_SKEW controller status event whenever
13954 we fetch directory information from a relay that has a wrong clock.
13955 Instead, only inform the controller when it's a trusted authority
13956 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
13957 the rest of bug 1074.
13958 - Fix an assert in parsing router descriptors containing IPv6
13959 addresses. This one took down the directory authorities when
13960 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
13961 - Make the bridge directory authority refuse to answer directory
13962 requests for "all" descriptors. It used to include bridge
13963 descriptors in its answer, which was a major information leak.
13964 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
13965 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
13966 Tor would ignore their RelayBandwidthBurst setting,
13967 potentially using more bandwidth than expected. Bugfix on
13968 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
13969 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
13970 hidserv" in her torrc. The 'hidserv' argument never controlled
13971 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
13974 - Relays now save observed peak bandwidth throughput rates to their
13975 state file (along with total usage, which was already saved)
13976 so that they can determine their correct estimated bandwidth on
13977 restart. Resolves bug 1863, where Tor relays would reset their
13978 estimated bandwidth to 0 after restarting.
13979 - Directory authorities now take changes in router IP address and
13980 ORPort into account when determining router stability. Previously,
13981 if a router changed its IP or ORPort, the authorities would not
13982 treat it as having any downtime for the purposes of stability
13983 calculation, whereas clients would experience downtime since the
13984 change could take a while to propagate to them. Resolves issue 1035.
13985 - Enable Address Space Layout Randomization (ASLR) and Data Execution
13986 Prevention (DEP) by default on Windows to make it harder for
13987 attackers to exploit vulnerabilities. Patch from John Brooks.
13989 o Minor bugfixes (on 0.2.1.x and earlier):
13990 - Fix a rare crash bug that could occur when a client was configured
13991 with a large number of bridges. Fixes bug 2629; bugfix on
13992 0.2.1.2-alpha. Bugfix by trac user "shitlei".
13993 - Avoid a double mark-for-free warning when failing to attach a
13994 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
13996 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
13997 found by "cypherpunks". This bug was introduced before the first
13998 Tor release, in svn commit r110.
13999 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
14000 don't mention them in the manpage. Fixes bug 2450; issue
14001 spotted by keb and G-Lo.
14002 - Fix a bug in bandwidth history state parsing that could have been
14003 triggered if a future version of Tor ever changed the timing
14004 granularity at which bandwidth history is measured. Bugfix on
14005 Tor 0.1.1.11-alpha.
14006 - When a relay decides that its DNS is too broken for it to serve
14007 as an exit server, it advertised itself as a non-exit, but
14008 continued to act as an exit. This could create accidental
14009 partitioning opportunities for users. Instead, if a relay is
14010 going to advertise reject *:* as its exit policy, it should
14011 really act with exit policy "reject *:*". Fixes bug 2366.
14012 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
14013 - In the special case where you configure a public exit relay as your
14014 bridge, Tor would be willing to use that exit relay as the last
14015 hop in your circuit as well. Now we fail that circuit instead.
14016 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
14017 - Fix a bug with our locking implementation on Windows that couldn't
14018 correctly detect when a file was already locked. Fixes bug 2504,
14019 bugfix on 0.2.1.6-alpha.
14020 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
14021 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
14023 - Set target port in get_interface_address6() correctly. Bugfix
14024 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
14025 - Directory authorities are now more robust to hops back in time
14026 when calculating router stability. Previously, if a run of uptime
14027 or downtime appeared to be negative, the calculation could give
14028 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
14030 - Fix an assert that got triggered when using the TestingTorNetwork
14031 configuration option and then issuing a GETINFO config-text control
14032 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
14034 o Minor bugfixes (on 0.2.2.x):
14035 - Clients should not weight BadExit nodes as Exits in their node
14036 selection. Similarly, directory authorities should not count BadExit
14037 bandwidth as Exit bandwidth when computing bandwidth-weights.
14038 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
14039 - Correctly clear our dir_read/dir_write history when there is an
14040 error parsing any bw history value from the state file. Bugfix on
14041 Tor 0.2.2.15-alpha.
14042 - Resolve a bug in verifying signatures of directory objects
14043 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
14044 Fixes bug 2409. Found by "piebeer".
14045 - Bridge authorities no longer crash on SIGHUP when they try to
14046 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
14050 - Log less aggressively about circuit timeout changes, and improve
14051 some other circuit timeout messages. Resolves bug 2004.
14052 - Log a little more clearly about the times at which we're no longer
14053 accepting new connections. Resolves bug 2181.
14054 - Reject attempts at the client side to open connections to private
14055 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
14056 a randomly chosen exit node. Attempts to do so are always
14057 ill-defined, generally prevented by exit policies, and usually
14058 in error. This will also help to detect loops in transparent
14059 proxy configurations. You can disable this feature by setting
14060 "ClientRejectInternalAddresses 0" in your torrc.
14061 - Always treat failure to allocate an RSA key as an unrecoverable
14063 - Update to the March 1 2011 Maxmind GeoLite Country database.
14065 o Minor features (log subsystem):
14066 - Add documentation for configuring logging at different severities in
14067 different log domains. We've had this feature since 0.2.1.1-alpha,
14068 but for some reason it never made it into the manpage. Fixes
14070 - Make it simpler to specify "All log domains except for A and B".
14071 Previously you needed to say "[*,~A,~B]". Now you can just say
14073 - Add a "LogMessageDomains 1" option to include the domains of log
14074 messages along with the messages. Without this, there's no way
14075 to use log domains without reading the source or doing a lot
14078 o Packaging changes:
14079 - Stop shipping the Tor specs files and development proposal documents
14080 in the tarball. They are now in a separate git repository at
14081 git://git.torproject.org/torspec.git
14084 Changes in version 0.2.1.30 - 2011-02-23
14085 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
14086 change is a slight tweak to Tor's TLS handshake that makes relays
14087 and bridges that run this new version reachable from Iran again.
14088 We don't expect this tweak will win the arms race long-term, but it
14089 buys us time until we roll out a better solution.
14092 - Stop sending a CLOCK_SKEW controller status event whenever
14093 we fetch directory information from a relay that has a wrong clock.
14094 Instead, only inform the controller when it's a trusted authority
14095 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
14096 the rest of bug 1074.
14097 - Fix a bounds-checking error that could allow an attacker to
14098 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
14099 Found by "piebeer".
14100 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
14101 Tor would ignore their RelayBandwidthBurst setting,
14102 potentially using more bandwidth than expected. Bugfix on
14103 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
14104 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
14105 hidserv" in her torrc. The 'hidserv' argument never controlled
14106 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
14109 - Adjust our TLS Diffie-Hellman parameters to match those used by
14111 - Update to the February 1 2011 Maxmind GeoLite Country database.
14114 - Check for and reject overly long directory certificates and
14115 directory tokens before they have a chance to hit any assertions.
14116 Bugfix on 0.2.1.28. Found by "doorss".
14117 - Bring the logic that gathers routerinfos and assesses the
14118 acceptability of circuits into line. This prevents a Tor OP from
14119 getting locked in a cycle of choosing its local OR as an exit for a
14120 path (due to a .exit request) and then rejecting the circuit because
14121 its OR is not listed yet. It also prevents Tor clients from using an
14122 OR running in the same instance as an exit (due to a .exit request)
14123 if the OR does not meet the same requirements expected of an OR
14124 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
14126 o Packaging changes:
14127 - Stop shipping the Tor specs files and development proposal documents
14128 in the tarball. They are now in a separate git repository at
14129 git://git.torproject.org/torspec.git
14130 - Do not include Git version tags as though they are SVN tags when
14131 generating a tarball from inside a repository that has switched
14132 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
14135 Changes in version 0.2.2.22-alpha - 2011-01-25
14136 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
14137 main other change is a slight tweak to Tor's TLS handshake that makes
14138 relays and bridges that run this new version reachable from Iran again.
14139 We don't expect this tweak will win the arms race long-term, but it
14140 will buy us a bit more time until we roll out a better solution.
14143 - Fix a bounds-checking error that could allow an attacker to
14144 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
14145 Found by "piebeer".
14146 - Don't assert when changing from bridge to relay or vice versa
14147 via the controller. The assert happened because we didn't properly
14148 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
14149 bug 2433. Reported by bastik.
14152 - Adjust our TLS Diffie-Hellman parameters to match those used by
14154 - Provide a log message stating which geoip file we're parsing
14155 instead of just stating that we're parsing the geoip file.
14156 Implements ticket 2432.
14159 - Check for and reject overly long directory certificates and
14160 directory tokens before they have a chance to hit any assertions.
14161 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
14164 Changes in version 0.2.2.21-alpha - 2011-01-15
14165 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
14166 continues our recent code security audit work. The main fix resolves
14167 a remote heap overflow vulnerability that can allow remote code
14168 execution (CVE-2011-0427). Other fixes address a variety of assert
14169 and crash bugs, most of which we think are hard to exploit remotely.
14171 o Major bugfixes (security), also included in 0.2.1.29:
14172 - Fix a heap overflow bug where an adversary could cause heap
14173 corruption. This bug probably allows remote code execution
14174 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
14176 - Prevent a denial-of-service attack by disallowing any
14177 zlib-compressed data whose compression factor is implausibly
14178 high. Fixes part of bug 2324; reported by "doorss".
14179 - Zero out a few more keys in memory before freeing them. Fixes
14180 bug 2384 and part of bug 2385. These key instances found by
14181 "cypherpunks", based on Andrew Case's report about being able
14182 to find sensitive data in Tor's memory space if you have enough
14183 permissions. Bugfix on 0.0.2pre9.
14185 o Major bugfixes (crashes), also included in 0.2.1.29:
14186 - Prevent calls to Libevent from inside Libevent log handlers.
14187 This had potential to cause a nasty set of crashes, especially
14188 if running Libevent with debug logging enabled, and running
14189 Tor with a controller watching for low-severity log messages.
14190 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
14191 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
14192 underflow errors there too. Fixes the other part of bug 2324.
14193 - Fix a bug where we would assert if we ever had a
14194 cached-descriptors.new file (or another file read directly into
14195 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
14196 on 0.2.1.25. Found by doorss.
14197 - Fix some potential asserts and parsing issues with grossly
14198 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
14201 o Minor bugfixes (other), also included in 0.2.1.29:
14202 - Fix a bug with handling misformed replies to reverse DNS lookup
14203 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
14204 bug reported by doorss.
14205 - Fix compilation on mingw when a pthreads compatibility library
14206 has been installed. (We don't want to use it, so we shouldn't
14207 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
14208 - Fix a bug where we would declare that we had run out of virtual
14209 addresses when the address space was only half-exhausted. Bugfix
14211 - Correctly handle the case where AutomapHostsOnResolve is set but
14212 no virtual addresses are available. Fixes bug 2328; bugfix on
14213 0.1.2.1-alpha. Bug found by doorss.
14214 - Correctly handle wrapping around when we run out of virtual
14215 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
14217 o Minor features, also included in 0.2.1.29:
14218 - Update to the January 1 2011 Maxmind GeoLite Country database.
14219 - Introduce output size checks on all of our decryption functions.
14221 o Build changes, also included in 0.2.1.29:
14222 - Tor does not build packages correctly with Automake 1.6 and earlier;
14223 added a check to Makefile.am to make sure that we're building with
14224 Automake 1.7 or later.
14225 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
14226 because we built it with a too-old version of automake. Thus that
14227 release broke ./configure --enable-openbsd-malloc, which is popular
14228 among really fast exit relays on Linux.
14230 o Major bugfixes, new in 0.2.2.21-alpha:
14231 - Prevent crash/heap corruption when the cbtnummodes consensus
14232 parameter is set to 0 or large values. Fixes bug 2317; bugfix
14235 o Major features, new in 0.2.2.21-alpha:
14236 - Introduce minimum/maximum values that clients will believe
14237 from the consensus. Now we'll have a better chance to avoid crashes
14238 or worse when a consensus param has a weird value.
14240 o Minor features, new in 0.2.2.21-alpha:
14241 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
14242 used on bridges, and it makes bridge scanning somewhat easier.
14243 - If writing the state file to disk fails, wait up to an hour before
14244 retrying again, rather than trying again each second. Fixes bug
14245 2346; bugfix on Tor 0.1.1.3-alpha.
14246 - Make Libevent log messages get delivered to controllers later,
14247 and not from inside the Libevent log handler. This prevents unsafe
14248 reentrant Libevent calls while still letting the log messages
14250 - Detect platforms that brokenly use a signed size_t, and refuse to
14251 build there. Found and analyzed by doorss and rransom.
14252 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
14255 o Minor bugfixes, new in 0.2.2.21-alpha:
14256 - Handle SOCKS messages longer than 128 bytes long correctly, rather
14257 than waiting forever for them to finish. Fixes bug 2330; bugfix
14258 on 0.2.0.16-alpha. Found by doorss.
14259 - Add assertions to check for overflow in arguments to
14260 base32_encode() and base32_decode(); fix a signed-unsigned
14261 comparison there too. These bugs are not actually reachable in Tor,
14262 but it's good to prevent future errors too. Found by doorss.
14263 - Correctly detect failures to create DNS requests when using Libevent
14264 versions before v2. (Before Libevent 2, we used our own evdns
14265 implementation. Its return values for Libevent's evdns_resolve_*()
14266 functions are not consistent with those from Libevent.) Fixes bug
14267 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
14269 o Documentation, new in 0.2.2.21-alpha:
14270 - Document the default socks host and port (127.0.0.1:9050) for
14274 Changes in version 0.2.1.29 - 2011-01-15
14275 Tor 0.2.1.29 continues our recent code security audit work. The main
14276 fix resolves a remote heap overflow vulnerability that can allow remote
14277 code execution. Other fixes address a variety of assert and crash bugs,
14278 most of which we think are hard to exploit remotely.
14280 o Major bugfixes (security):
14281 - Fix a heap overflow bug where an adversary could cause heap
14282 corruption. This bug probably allows remote code execution
14283 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
14285 - Prevent a denial-of-service attack by disallowing any
14286 zlib-compressed data whose compression factor is implausibly
14287 high. Fixes part of bug 2324; reported by "doorss".
14288 - Zero out a few more keys in memory before freeing them. Fixes
14289 bug 2384 and part of bug 2385. These key instances found by
14290 "cypherpunks", based on Andrew Case's report about being able
14291 to find sensitive data in Tor's memory space if you have enough
14292 permissions. Bugfix on 0.0.2pre9.
14294 o Major bugfixes (crashes):
14295 - Prevent calls to Libevent from inside Libevent log handlers.
14296 This had potential to cause a nasty set of crashes, especially
14297 if running Libevent with debug logging enabled, and running
14298 Tor with a controller watching for low-severity log messages.
14299 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
14300 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
14301 underflow errors there too. Fixes the other part of bug 2324.
14302 - Fix a bug where we would assert if we ever had a
14303 cached-descriptors.new file (or another file read directly into
14304 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
14305 on 0.2.1.25. Found by doorss.
14306 - Fix some potential asserts and parsing issues with grossly
14307 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
14310 o Minor bugfixes (other):
14311 - Fix a bug with handling misformed replies to reverse DNS lookup
14312 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
14313 bug reported by doorss.
14314 - Fix compilation on mingw when a pthreads compatibility library
14315 has been installed. (We don't want to use it, so we shouldn't
14316 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
14317 - Fix a bug where we would declare that we had run out of virtual
14318 addresses when the address space was only half-exhausted. Bugfix
14320 - Correctly handle the case where AutomapHostsOnResolve is set but
14321 no virtual addresses are available. Fixes bug 2328; bugfix on
14322 0.1.2.1-alpha. Bug found by doorss.
14323 - Correctly handle wrapping around to when we run out of virtual
14324 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
14325 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
14326 because we built it with a too-old version of automake. Thus that
14327 release broke ./configure --enable-openbsd-malloc, which is popular
14328 among really fast exit relays on Linux.
14331 - Update to the January 1 2011 Maxmind GeoLite Country database.
14332 - Introduce output size checks on all of our decryption functions.
14335 - Tor does not build packages correctly with Automake 1.6 and earlier;
14336 added a check to Makefile.am to make sure that we're building with
14337 Automake 1.7 or later.
14340 Changes in version 0.2.2.20-alpha - 2010-12-17
14341 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
14342 exploitable bugs. We also fix a variety of other significant bugs,
14343 change the IP address for one of our directory authorities, and update
14344 the minimum version that Tor relays must run to join the network.
14347 - Fix a remotely exploitable bug that could be used to crash instances
14348 of Tor remotely by overflowing on the heap. Remote-code execution
14349 hasn't been confirmed, but can't be ruled out. Everyone should
14350 upgrade. Bugfix on the 0.1.1 series and later.
14351 - Fix a bug that could break accounting on 64-bit systems with large
14352 time_t values, making them hibernate for impossibly long intervals.
14353 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
14354 - Fix a logic error in directory_fetches_from_authorities() that
14355 would cause all _non_-exits refusing single-hop-like circuits
14356 to fetch from authorities, when we wanted to have _exits_ fetch
14357 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
14359 - Fix a stream fairness bug that would cause newer streams on a given
14360 circuit to get preference when reading bytes from the origin or
14361 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
14362 introduced before the first Tor release, in svn revision r152.
14364 o Directory authority changes:
14365 - Change IP address and ports for gabelmoo (v3 directory authority).
14368 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
14369 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
14370 - Fix an off-by-one error in calculating some controller command
14371 argument lengths. Fortunately, this mistake is harmless since
14372 the controller code does redundant NUL termination too. Found by
14373 boboper. Bugfix on 0.1.1.1-alpha.
14374 - Do not dereference NULL if a bridge fails to build its
14375 extra-info descriptor. Found by an anonymous commenter on
14376 Trac. Bugfix on 0.2.2.19-alpha.
14379 - Update to the December 1 2010 Maxmind GeoLite Country database.
14380 - Directory authorities now reject relays running any versions of
14381 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
14382 known bugs that keep RELAY_EARLY cells from working on rendezvous
14383 circuits. Followup to fix for bug 2081.
14384 - Directory authorities now reject relays running any version of Tor
14385 older than 0.2.0.26-rc. That version is the earliest that fetches
14386 current directory information correctly. Fixes bug 2156.
14387 - Report only the top 10 ports in exit-port stats in order not to
14388 exceed the maximum extra-info descriptor length of 50 KB. Implements
14392 Changes in version 0.2.1.28 - 2010-12-17
14393 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
14394 exploitable bugs. We also took this opportunity to change the IP address
14395 for one of our directory authorities, and to update the geoip database
14399 - Fix a remotely exploitable bug that could be used to crash instances
14400 of Tor remotely by overflowing on the heap. Remote-code execution
14401 hasn't been confirmed, but can't be ruled out. Everyone should
14402 upgrade. Bugfix on the 0.1.1 series and later.
14404 o Directory authority changes:
14405 - Change IP address and ports for gabelmoo (v3 directory authority).
14408 - Update to the December 1 2010 Maxmind GeoLite Country database.
14411 Changes in version 0.2.1.27 - 2010-11-23
14412 Yet another OpenSSL security patch broke its compatibility with Tor:
14413 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
14414 also took this opportunity to fix several crash bugs, integrate a new
14415 directory authority, and update the bundled GeoIP database.
14418 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
14419 No longer set the tlsext_host_name extension on server SSL objects;
14420 but continue to set it on client SSL objects. Our goal in setting
14421 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
14422 bugfix on 0.2.1.1-alpha.
14423 - Do not log messages to the controller while shrinking buffer
14424 freelists. Doing so would sometimes make the controller connection
14425 try to allocate a buffer chunk, which would mess up the internals
14426 of the freelist and cause an assertion failure. Fixes bug 1125;
14427 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
14428 - Learn our external IP address when we're a relay or bridge, even if
14429 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
14430 where we introduced bridge relays that don't need to publish to
14431 be useful. Fixes bug 2050.
14432 - Do even more to reject (and not just ignore) annotations on
14433 router descriptors received anywhere but from the cache. Previously
14434 we would ignore such annotations at first, but cache them to disk
14435 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
14436 - When you're using bridges and your network goes away and your
14437 bridges get marked as down, recover when you attempt a new socks
14438 connection (if the network is back), rather than waiting up to an
14439 hour to try fetching new descriptors for your bridges. Bugfix on
14440 0.2.0.3-alpha; fixes bug 1981.
14443 - Move to the November 2010 Maxmind GeoLite country db (rather
14444 than the June 2009 ip-to-country GeoIP db) for our statistics that
14445 count how many users relays are seeing from each country. Now we'll
14446 have more accurate data, especially for many African countries.
14448 o New directory authorities:
14449 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
14453 - Fix an assertion failure that could occur in directory caches or
14454 bridge users when using a very short voting interval on a testing
14455 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
14457 - Enforce multiplicity rules when parsing annotations. Bugfix on
14458 0.2.0.8-alpha. Found by piebeer.
14459 - Allow handshaking OR connections to take a full KeepalivePeriod
14460 seconds to handshake. Previously, we would close them after
14461 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
14462 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
14464 - When building with --enable-gcc-warnings on OpenBSD, disable
14465 warnings in system headers. This makes --enable-gcc-warnings
14466 pass on OpenBSD 4.8.
14469 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
14470 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
14471 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
14472 Servers can start sending this code when enough clients recognize
14473 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
14474 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
14475 Patch from mingw-san.
14478 - Remove the old debian/ directory from the main Tor distribution.
14479 The official Tor-for-debian git repository lives at the URL
14480 https://git.torproject.org/debian/tor.git
14481 - Stop shipping the old doc/website/ directory in the tarball. We
14482 changed the website format in late 2010, and what we shipped in
14483 0.2.1.26 really wasn't that useful anyway.
14486 Changes in version 0.2.2.19-alpha - 2010-11-22
14487 Yet another OpenSSL security patch broke its compatibility with Tor:
14488 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
14491 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
14492 No longer set the tlsext_host_name extension on server SSL objects;
14493 but continue to set it on client SSL objects. Our goal in setting
14494 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
14495 bugfix on 0.2.1.1-alpha.
14498 - Try harder not to exceed the maximum length of 50 KB when writing
14499 statistics to extra-info descriptors. This bug was triggered by very
14500 fast relays reporting exit-port, entry, and dirreq statistics.
14501 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
14502 - Publish a router descriptor even if generating an extra-info
14503 descriptor fails. Previously we would not publish a router
14504 descriptor without an extra-info descriptor; this can cause fast
14505 exit relays collecting exit-port statistics to drop from the
14506 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
14509 Changes in version 0.2.2.18-alpha - 2010-11-16
14510 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
14511 us lately, makes unpublished bridge relays able to detect their IP
14512 address, and fixes a wide variety of other bugs to get us much closer
14513 to a stable release.
14516 - Do even more to reject (and not just ignore) annotations on
14517 router descriptors received anywhere but from the cache. Previously
14518 we would ignore such annotations at first, but cache them to disk
14519 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
14520 - Do not log messages to the controller while shrinking buffer
14521 freelists. Doing so would sometimes make the controller connection
14522 try to allocate a buffer chunk, which would mess up the internals
14523 of the freelist and cause an assertion failure. Fixes bug 1125;
14524 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
14525 - Learn our external IP address when we're a relay or bridge, even if
14526 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
14527 where we introduced bridge relays that don't need to publish to
14528 be useful. Fixes bug 2050.
14529 - Maintain separate TLS contexts and certificates for incoming and
14530 outgoing connections in bridge relays. Previously we would use the
14531 same TLS contexts and certs for incoming and outgoing connections.
14532 Bugfix on 0.2.0.3-alpha; addresses bug 988.
14533 - Maintain separate identity keys for incoming and outgoing TLS
14534 contexts in bridge relays. Previously we would use the same
14535 identity keys for incoming and outgoing TLS contexts. Bugfix on
14536 0.2.0.3-alpha; addresses the other half of bug 988.
14537 - Avoid an assertion failure when we as an authority receive a
14538 duplicate upload of a router descriptor that we already have,
14539 but which we previously considered an obsolete descriptor.
14540 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
14541 - Avoid a crash bug triggered by looking at a dangling pointer while
14542 setting the network status consensus. Found by Robert Ransom.
14543 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
14544 - Fix a logic error where servers that _didn't_ act as exits would
14545 try to keep their server lists more aggressively up to date than
14546 exits, when it was supposed to be the other way around. Bugfix
14549 o Minor bugfixes (on Tor 0.2.1.x and earlier):
14550 - When we're trying to guess whether we know our IP address as
14551 a relay, we would log various ways that we failed to guess
14552 our address, but never log that we ended up guessing it
14553 successfully. Now add a log line to help confused and anxious
14554 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
14555 - Bring the logic that gathers routerinfos and assesses the
14556 acceptability of circuits into line. This prevents a Tor OP from
14557 getting locked in a cycle of choosing its local OR as an exit for a
14558 path (due to a .exit request) and then rejecting the circuit because
14559 its OR is not listed yet. It also prevents Tor clients from using an
14560 OR running in the same instance as an exit (due to a .exit request)
14561 if the OR does not meet the same requirements expected of an OR
14562 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
14563 - Correctly describe errors that occur when generating a TLS object.
14564 Previously we would attribute them to a failure while generating a
14565 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
14567 - Enforce multiplicity rules when parsing annotations. Bugfix on
14568 0.2.0.8-alpha. Found by piebeer.
14569 - Fix warnings that newer versions of autoconf produced during
14570 ./autogen.sh. These warnings appear to be harmless in our case,
14571 but they were extremely verbose. Fixes bug 2020.
14573 o Minor bugfixes (on Tor 0.2.2.x):
14574 - Enable protection of small arrays whenever we build with gcc
14575 hardening features, not only when also building with warnings
14576 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
14579 - Make hidden services work better in private Tor networks by not
14580 requiring any uptime to join the hidden service descriptor
14581 DHT. Implements ticket 2088.
14582 - Rate-limit the "your application is giving Tor only an IP address"
14583 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
14584 - When AllowSingleHopExits is set, print a warning to explain to the
14585 relay operator why most clients are avoiding her relay.
14586 - Update to the November 1 2010 Maxmind GeoLite Country database.
14588 o Code simplifications and refactoring:
14589 - When we fixed bug 1038 we had to put in a restriction not to send
14590 RELAY_EARLY cells on rend circuits. This was necessary as long
14591 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
14592 active. Now remove this obsolete check. Resolves bug 2081.
14593 - Some options used different conventions for uppercasing of acronyms
14594 when comparing manpage and source. Fix those in favor of the
14595 manpage, as it makes sense to capitalize acronyms.
14596 - Remove the torrc.complete file. It hasn't been kept up to date
14597 and users will have better luck checking out the manpage.
14598 - Remove the obsolete "NoPublish" option; it has been flagged
14599 as obsolete and has produced a warning since 0.1.1.18-rc.
14600 - Remove everything related to building the expert bundle for OS X.
14601 It has confused many users, doesn't work right on OS X 10.6,
14602 and is hard to get rid of once installed. Resolves bug 1274.
14605 Changes in version 0.2.2.17-alpha - 2010-09-30
14606 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
14607 to use one-hop circuits (which can put the exit relays at higher risk,
14608 plus unbalance the network); fixes a big bug in bandwidth accounting
14609 for relays that want to limit their monthly bandwidth use; fixes a
14610 big pile of bugs in how clients tolerate temporary network failure;
14611 and makes our adaptive circuit build timeout feature (which improves
14612 client performance if your network is fast while not breaking things
14613 if your network is slow) better handle bad networks.
14616 - Exit relays now try harder to block exit attempts from unknown
14617 relays, to make it harder for people to use them as one-hop proxies
14618 a la tortunnel. Controlled by the refuseunknownexits consensus
14619 parameter (currently enabled), or you can override it on your
14620 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
14622 o Major bugfixes (0.2.1.x and earlier):
14623 - Fix a bug in bandwidth accounting that could make us use twice
14624 the intended bandwidth when our interval start changes due to
14625 daylight saving time. Now we tolerate skew in stored vs computed
14626 interval starts: if the start of the period changes by no more than
14627 50% of the period's duration, we remember bytes that we transferred
14628 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
14629 - Always search the Windows system directory for system DLLs, and
14630 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
14631 - When you're using bridges and your network goes away and your
14632 bridges get marked as down, recover when you attempt a new socks
14633 connection (if the network is back), rather than waiting up to an
14634 hour to try fetching new descriptors for your bridges. Bugfix on
14635 0.2.0.3-alpha; fixes bug 1981.
14637 o Major bugfixes (on 0.2.2.x):
14638 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
14640 - Fix a segfault that could happen when operating a bridge relay with
14641 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
14642 - The consensus bandwidth-weights (used by clients to choose fast
14643 relays) entered an unexpected edge case in September where
14644 Exits were much scarcer than Guards, resulting in bad weight
14645 recommendations. Now we compute them using new constraints that
14646 should succeed in all cases. Also alter directory authorities to
14647 not include the bandwidth-weights line if they fail to produce
14648 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
14649 - When weighting bridges during path selection, we used to trust
14650 the bandwidths they provided in their descriptor, only capping them
14651 at 10MB/s. This turned out to be problematic for two reasons:
14652 Bridges could claim to handle a lot more traffic then they
14653 actually would, thus making more clients pick them and have a
14654 pretty effective DoS attack. The other issue is that new bridges
14655 that might not have a good estimate for their bw capacity yet
14656 would not get used at all unless no other bridges are available
14657 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
14659 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
14660 - Ignore cannibalized circuits when recording circuit build times.
14661 This should provide for a minor performance improvement for hidden
14662 service users using 0.2.2.14-alpha, and should remove two spurious
14663 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
14664 - Simplify the logic that causes us to decide if the network is
14665 unavailable for purposes of recording circuit build times. If we
14666 receive no cells whatsoever for the entire duration of a circuit's
14667 full measured lifetime, the network is probably down. Also ignore
14668 one-hop directory fetching circuit timeouts when calculating our
14669 circuit build times. These changes should hopefully reduce the
14670 cases where we see ridiculous circuit build timeouts for people
14671 with spotty wireless connections. Fixes part of bug 1772; bugfix
14673 - Prevent the circuit build timeout from becoming larger than
14674 the maximum build time we have ever seen. Also, prevent the time
14675 period for measurement circuits from becoming larger than twice that
14676 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
14679 - When we run out of directory information such that we can't build
14680 circuits, but then get enough that we can build circuits, log when
14681 we actually construct a circuit, so the user has a better chance of
14682 knowing what's going on. Fixes bug 1362.
14683 - Be more generous with how much bandwidth we'd use up (with
14684 accounting enabled) before entering "soft hibernation". Previously,
14685 we'd refuse new connections and circuits once we'd used up 95% of
14686 our allotment. Now, we use up 95% of our allotment, AND make sure
14687 that we have no more than 500MB (or 3 hours of expected traffic,
14688 whichever is lower) remaining before we enter soft hibernation.
14689 - If we've configured EntryNodes and our network goes away and/or all
14690 our entrynodes get marked down, optimistically retry them all when
14691 a new socks application request appears. Fixes bug 1882.
14692 - Add some more defensive programming for architectures that can't
14693 handle unaligned integer accesses. We don't know of any actual bugs
14694 right now, but that's the best time to fix them. Fixes bug 1943.
14695 - Support line continuations in the torrc config file. If a line
14696 ends with a single backslash character, the newline is ignored, and
14697 the configuration value is treated as continuing on the next line.
14700 o Minor bugfixes (on 0.2.1.x and earlier):
14701 - For bandwidth accounting, calculate our expected bandwidth rate
14702 based on the time during which we were active and not in
14703 soft-hibernation during the last interval. Previously, we were
14704 also considering the time spent in soft-hibernation. If this
14705 was a long time, we would wind up underestimating our bandwidth
14706 by a lot, and skewing our wakeup time towards the start of the
14707 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
14709 o Minor bugfixes (on 0.2.2.x):
14710 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
14711 which were disabled by the circuit build timeout changes in
14712 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
14713 - Make sure we don't warn about missing bandwidth weights when
14714 choosing bridges or other relays not in the consensus. Bugfix on
14715 0.2.2.10-alpha; fixes bug 1805.
14716 - In our logs, do not double-report signatures from unrecognized
14717 authorities both as "from unknown authority" and "not
14718 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
14721 Changes in version 0.2.2.16-alpha - 2010-09-17
14722 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
14723 evident at exit relays), and also continues to resolve all the little
14724 bugs that have been filling up trac lately.
14726 o Major bugfixes (stream-level fairness):
14727 - When receiving a circuit-level SENDME for a blocked circuit, try
14728 to package cells fairly from all the streams that had previously
14729 been blocked on that circuit. Previously, we had started with the
14730 oldest stream, and allowed each stream to potentially exhaust
14731 the circuit's package window. This gave older streams on any
14732 given circuit priority over newer ones. Fixes bug 1937. Detected
14733 originally by Camilo Viecco. This bug was introduced before the
14734 first Tor release, in svn commit r152: it is the new winner of
14735 the longest-lived bug prize.
14736 - When the exit relay got a circuit-level sendme cell, it started
14737 reading on the exit streams, even if had 500 cells queued in the
14738 circuit queue already, so the circuit queue just grew and grew in
14739 some cases. We fix this by not re-enabling reading on receipt of a
14740 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
14741 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
14743 - Newly created streams were allowed to read cells onto circuits,
14744 even if the circuit's cell queue was blocked and waiting to drain.
14745 This created potential unfairness, as older streams would be
14746 blocked, but newer streams would gladly fill the queue completely.
14747 We add code to detect this situation and prevent any stream from
14748 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
14752 - Update to the September 1 2010 Maxmind GeoLite Country database.
14753 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
14754 not. This would lead to a cookie that is still not group readable.
14755 Closes bug 1843. Suggested by katmagic.
14756 - When logging a rate-limited warning, we now mention how many messages
14757 got suppressed since the last warning.
14758 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
14759 do individual connection-level rate limiting of clients. The torrc
14760 config options with the same names trump the consensus params, if
14761 both are present. Replaces the old "bwconnrate" and "bwconnburst"
14762 consensus params which were broken from 0.2.2.7-alpha through
14763 0.2.2.14-alpha. Closes bug 1947.
14764 - When a router changes IP address or port, authorities now launch
14765 a new reachability test for it. Implements ticket 1899.
14766 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
14767 2 no signature, 4 required" messages about consensus signatures
14768 easier to read, and make sure they get logged at the same severity
14769 as the messages explaining which keys are which. Fixes bug 1290.
14770 - Don't warn when we have a consensus that we can't verify because
14771 of missing certificates, unless those certificates are ones
14772 that we have been trying and failing to download. Fixes bug 1145.
14773 - If you configure your bridge with a known identity fingerprint,
14774 and the bridge authority is unreachable (as it is in at least
14775 one country now), fall back to directly requesting the descriptor
14776 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
14778 - When building with --enable-gcc-warnings on OpenBSD, disable
14779 warnings in system headers. This makes --enable-gcc-warnings
14780 pass on OpenBSD 4.8.
14782 o Minor bugfixes (on 0.2.1.x and earlier):
14783 - Authorities will now attempt to download consensuses if their
14784 own efforts to make a live consensus have failed. This change
14785 means authorities that restart will fetch a valid consensus, and
14786 it means authorities that didn't agree with the current consensus
14787 will still fetch and serve it if it has enough signatures. Bugfix
14788 on 0.2.0.9-alpha; fixes bug 1300.
14789 - Ensure DNS requests launched by "RESOLVE" commands from the
14790 controller respect the __LeaveStreamsUnattached setconf options. The
14791 same goes for requests launched via DNSPort or transparent
14792 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
14793 - Allow handshaking OR connections to take a full KeepalivePeriod
14794 seconds to handshake. Previously, we would close them after
14795 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
14796 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
14798 - Rate-limit "Failed to hand off onionskin" warnings.
14799 - Never relay a cell for a circuit we have already destroyed.
14800 Between marking a circuit as closeable and finally closing it,
14801 it may have been possible for a few queued cells to get relayed,
14802 even though they would have been immediately dropped by the next
14803 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
14804 - Never queue a cell for a circuit that's already been marked
14806 - Never vote for a server as "Running" if we have a descriptor for
14807 it claiming to be hibernating, and that descriptor was published
14808 more recently than our last contact with the server. Bugfix on
14809 0.2.0.3-alpha; fixes bug 911.
14810 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
14813 o Minor bugfixes (on 0.2.2.x):
14814 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
14815 down if a directory fetch fails and you've configured either
14816 bridges or EntryNodes. The intent was to mark the relay as down
14817 _unless_ you're using bridges or EntryNodes, since if you are
14818 then you could quickly run out of entry points.
14819 - Fix the Windows directory-listing code. A bug introduced in
14820 0.2.2.14-alpha could make Windows directory servers forget to load
14821 some of their cached v2 networkstatus files.
14822 - Really allow clients to use relays as bridges. Fixes bug 1776;
14823 bugfix on 0.2.2.15-alpha.
14824 - Demote a warn to info that happens when the CellStatistics option
14825 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
14826 Reported by Moritz Bartl.
14827 - On Windows, build correctly either with or without Unicode support.
14828 This is necessary so that Tor can support fringe platforms like
14829 Windows 98 (which has no Unicode), or Windows CE (which has no
14830 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
14833 - Add a unit test for cross-platform directory-listing code.
14836 Changes in version 0.2.2.15-alpha - 2010-08-18
14837 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
14838 fixes a variety of other bugs that were preventing performance
14839 experiments from moving forward, fixes several bothersome memory leaks,
14840 and generally closes a lot of smaller bugs that have been filling up
14844 - Stop assigning the HSDir flag to relays that disable their
14845 DirPort (and thus will refuse to answer directory requests). This
14846 fix should dramatically improve the reachability of hidden services:
14847 hidden services and hidden service clients pick six HSDir relays
14848 to store and retrieve the hidden service descriptor, and currently
14849 about half of the HSDir relays will refuse to work. Bugfix on
14850 0.2.0.10-alpha; fixes part of bug 1693.
14851 - The PerConnBWRate and Burst config options, along with the
14852 bwconnrate and bwconnburst consensus params, initialized each conn's
14853 token bucket values only when the connection is established. Now we
14854 update them if the config options change, and update them every time
14855 we get a new consensus. Otherwise we can encounter an ugly edge
14856 case where we initialize an OR conn to client-level bandwidth,
14857 but then later the relay joins the consensus and we leave it
14858 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
14859 - Fix a regression that caused Tor to rebind its ports if it receives
14860 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
14863 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
14864 should give us approximately 40-50% more Guard-flagged nodes,
14865 improving the anonymity the Tor network can provide and also
14866 decreasing the dropoff in throughput that relays experience when
14867 they first get the Guard flag.
14868 - Allow enabling or disabling the *Statistics config options while
14872 - Update to the August 1 2010 Maxmind GeoLite Country database.
14873 - Have the controller interface give a more useful message than
14874 "Internal Error" in response to failed GETINFO requests.
14875 - Warn when the same option is provided more than once in a torrc
14876 file, on the command line, or in a single SETCONF statement, and
14877 the option is one that only accepts a single line. Closes bug 1384.
14878 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
14879 Patch from mingw-san.
14880 - Add support for the country code "{??}" in torrc options like
14881 ExcludeNodes, to indicate all routers of unknown country. Closes
14883 - Relays report the number of bytes spent on answering directory
14884 requests in extra-info descriptors similar to {read,write}-history.
14885 Implements enhancement 1790.
14887 o Minor bugfixes (on 0.2.1.x and earlier):
14888 - Complain if PublishServerDescriptor is given multiple arguments that
14889 include 0 or 1. This configuration will be rejected in the future.
14890 Bugfix on 0.2.0.1-alpha; closes bug 1107.
14891 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
14892 Bugfix on 0.2.0.13-alpha; closes bug 928.
14893 - Change "Application request when we're believed to be offline."
14894 notice to "Application request when we haven't used client
14895 functionality lately.", to clarify that it's not an error. Bugfix
14896 on 0.0.9.3; fixes bug 1222.
14897 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
14898 would return "551 Internal error" rather than "552 Unrecognized key
14899 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
14900 - Users can't configure a regular relay to be their bridge. It didn't
14901 work because when Tor fetched the bridge descriptor, it found
14902 that it already had it, and didn't realize that the purpose of the
14903 descriptor had changed. Now we replace routers with a purpose other
14904 than bridge with bridge descriptors when fetching them. Bugfix on
14905 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
14906 refetch the descriptor with router purpose 'general', disabling
14908 - Fix a rare bug in rend_fn unit tests: we would fail a test when
14909 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
14910 on 0.2.0.10-alpha; fixes bug 1808.
14911 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
14912 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
14913 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
14914 Servers can start sending this code when enough clients recognize
14915 it. Also update the spec to reflect this new reason. Bugfix on
14916 0.1.0.1-rc; fixes part of bug 1793.
14917 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
14918 when we switch from being a public relay to a bridge. Otherwise
14919 there will still be clients that see the relay in their consensus,
14920 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
14922 - Instead of giving an assertion failure on an internal mismatch
14923 on estimated freelist size, just log a BUG warning and try later.
14924 Mitigates but does not fix bug 1125.
14925 - Fix an assertion failure that could occur in caches or bridge users
14926 when using a very short voting interval on a testing network.
14927 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
14929 o Minor bugfixes (on 0.2.2.x):
14930 - Alter directory authorities to always consider Exit-flagged nodes
14931 as potential Guard nodes in their votes. The actual decision to
14932 use Exits as Guards is done in the consensus bandwidth weights.
14933 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
14934 - When the controller is reporting the purpose of circuits that
14935 didn't finish building before the circuit build timeout, it was
14936 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
14937 - Our libevent version parsing code couldn't handle versions like
14938 1.4.14b-stable and incorrectly warned the user about using an
14939 old and broken version of libevent. Treat 1.4.14b-stable like
14940 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
14942 - Don't use substitution references like $(VAR:MOD) when
14943 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
14944 '$(:x)' to 'x' rather than the empty string. This bites us in
14945 doc/ when configured with --disable-asciidoc. Bugfix on
14946 0.2.2.9-alpha; fixes bug 1773.
14947 - Remove a spurious hidden service server-side log notice about
14948 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
14950 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
14952 - Correctly report written bytes on linked connections. Found while
14953 implementing 1790. Bugfix on 0.2.2.4-alpha.
14954 - Fix three memory leaks: one in circuit_build_times_parse_state(),
14955 one in dirvote_add_signatures_to_pending_consensus(), and one every
14956 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
14957 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
14959 o Code simplifications and refactoring:
14960 - Take a first step towards making or.h smaller by splitting out
14961 function definitions for all source files in src/or/. Leave
14962 structures and defines in or.h for now.
14963 - Remove a bunch of unused function declarations as well as a block of
14964 #if 0'd code from the unit tests. Closes bug 1824.
14965 - New unit tests for exit-port history statistics; refactored exit
14966 statistics code to be more easily tested.
14967 - Remove the old debian/ directory from the main Tor distribution.
14968 The official Tor-for-debian git repository lives at the URL
14969 https://git.torproject.org/debian/tor.git
14972 Changes in version 0.2.2.14-alpha - 2010-07-12
14973 Tor 0.2.2.14-alpha greatly improves client-side handling of
14974 circuit build timeouts, which are used to estimate speed and improve
14975 performance. We also move to a much better GeoIP database, port Tor to
14976 Windows CE, introduce new compile flags that improve code security,
14977 add an eighth v3 directory authority, and address a lot of more
14981 - Tor directory authorities no longer crash when started with a
14982 cached-microdesc-consensus file in their data directory. Bugfix
14983 on 0.2.2.6-alpha; fixes bug 1532.
14984 - Treat an unset $HOME like an empty $HOME rather than triggering an
14985 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
14986 - Ignore negative and large circuit build timeout values that can
14987 happen during a suspend or hibernate. These values caused various
14988 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
14989 - Alter calculation of Pareto distribution parameter 'Xm' for
14990 Circuit Build Timeout learning to use the weighted average of the
14991 top N=3 modes (because we have three entry guards). Considering
14992 multiple modes should improve the timeout calculation in some cases,
14993 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
14995 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
14996 right censored distribution model. This approach improves over the
14997 synthetic timeout generation approach that was producing insanely
14998 high timeout values. Now we calculate build timeouts using truncated
14999 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
15000 - Do not close circuits that are under construction when they reach
15001 the circuit build timeout. Instead, leave them building (but do not
15002 use them) for up until the time corresponding to the 95th percentile
15003 on the Pareto CDF or 60 seconds, whichever is greater. This is done
15004 to provide better data for the new Pareto model. This percentile
15005 can be controlled by the consensus.
15008 - Move to the June 2010 Maxmind GeoLite country db (rather than the
15009 June 2009 ip-to-country GeoIP db) for our statistics that count
15010 how many users relays are seeing from each country. Now we have
15011 more accurate data for many African countries.
15012 - Port Tor to build and run correctly on Windows CE systems, using
15013 the wcecompat library. Contributed by Valerio Lupi.
15014 - New "--enable-gcc-hardening" ./configure flag (off by default)
15015 to turn on gcc compile time hardening options. It ensures
15016 that signed ints have defined behavior (-fwrapv), enables
15017 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
15018 with canaries (-fstack-protector-all), turns on ASLR protection if
15019 supported by the kernel (-fPIE, -pie), and adds additional security
15020 related warnings. Verified to work on Mac OS X and Debian Lenny.
15021 - New "--enable-linker-hardening" ./configure flag (off by default)
15022 to turn on ELF specific hardening features (relro, now). This does
15023 not work with Mac OS X or any other non-ELF binary format.
15025 o New directory authorities:
15026 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
15030 - New config option "WarnUnsafeSocks 0" disables the warning that
15031 occurs whenever Tor receives a socks handshake using a version of
15032 the socks protocol that can only provide an IP address (rather
15033 than a hostname). Setups that do DNS locally over Tor are fine,
15034 and we shouldn't spam the logs in that case.
15035 - Convert the HACKING file to asciidoc, and add a few new sections
15036 to it, explaining how we use Git, how we make changelogs, and
15037 what should go in a patch.
15038 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
15039 event, to give information on the current rate of circuit timeouts
15040 over our stored history.
15041 - Add ability to disable circuit build time learning via consensus
15042 parameter and via a LearnCircuitBuildTimeout config option. Also
15043 automatically disable circuit build time calculation if we are
15044 either a AuthoritativeDirectory, or if we fail to write our state
15045 file. Fixes bug 1296.
15046 - More gracefully handle corrupt state files, removing asserts
15047 in favor of saving a backup and resetting state.
15048 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
15052 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
15054 - When a2x fails, mention that the user could disable manpages instead
15055 of trying to fix their asciidoc installation.
15056 - Where available, use Libevent 2.0's periodic timers so that our
15057 once-per-second cleanup code gets called even more closely to
15058 once per second than it would otherwise. Fixes bug 943.
15059 - If you run a bridge that listens on multiple IP addresses, and
15060 some user configures a bridge address that uses a different IP
15061 address than your bridge writes in its router descriptor, and the
15062 user doesn't specify an identity key, their Tor would discard the
15063 descriptor because "it isn't one of our configured bridges", and
15064 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
15065 Bugfix on 0.2.0.3-alpha.
15066 - If OpenSSL fails to make a duplicate of a private or public key, log
15067 an error message and try to exit cleanly. May help with debugging
15068 if bug 1209 ever remanifests.
15069 - Save a couple bytes in memory allocation every time we escape
15070 certain characters in a string. Patch from Florian Zumbiehl.
15071 - Make it explicit that we don't cannibalize one-hop circuits. This
15072 happens in the wild, but doesn't turn out to be a problem because
15073 we fortunately don't use those circuits. Many thanks to outofwords
15074 for the initial analysis and to swissknife who confirmed that
15075 two-hop circuits are actually created.
15076 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
15077 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
15078 - Eliminate a case where a circuit build time warning was displayed
15079 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
15082 Changes in version 0.2.1.26 - 2010-05-02
15083 Tor 0.2.1.26 addresses the recent connection and memory overload
15084 problems we've been seeing on relays, especially relays with their
15085 DirPort open. If your relay has been crashing, or you turned it off
15086 because it used too many resources, give this release a try.
15088 This release also fixes yet another instance of broken OpenSSL libraries
15089 that was causing some relays to drop out of the consensus.
15092 - Teach relays to defend themselves from connection overload. Relays
15093 now close idle circuits early if it looks like they were intended
15094 for directory fetches. Relays are also more aggressive about closing
15095 TLS connections that have no circuits on them. Such circuits are
15096 unlikely to be re-used, and tens of thousands of them were piling
15097 up at the fast relays, causing the relays to run out of sockets
15098 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
15099 their directory fetches over TLS).
15100 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
15101 that claim to be earlier than 0.9.8m, but which have in reality
15102 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
15103 behavior. Possible fix for some cases of bug 1346.
15104 - Directory mirrors were fetching relay descriptors only from v2
15105 directory authorities, rather than v3 authorities like they should.
15106 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
15107 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
15110 - Finally get rid of the deprecated and now harmful notion of "clique
15111 mode", where directory authorities maintain TLS connections to
15115 - In the util/threads test, no longer free the test_mutex before all
15116 worker threads have finished. Bugfix on 0.2.1.6-alpha.
15117 - The master thread could starve the worker threads quite badly on
15118 certain systems, causing them to run only partially in the allowed
15119 window. This resulted in test failures. Now the master thread sleeps
15120 occasionally for a few microseconds while the two worker-threads
15121 compete for the mutex. Bugfix on 0.2.0.1-alpha.
15124 Changes in version 0.2.2.13-alpha - 2010-04-24
15125 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
15126 problems we've been seeing on relays, especially relays with their
15127 DirPort open. If your relay has been crashing, or you turned it off
15128 because it used too many resources, give this release a try.
15131 - Teach relays to defend themselves from connection overload. Relays
15132 now close idle circuits early if it looks like they were intended
15133 for directory fetches. Relays are also more aggressive about closing
15134 TLS connections that have no circuits on them. Such circuits are
15135 unlikely to be re-used, and tens of thousands of them were piling
15136 up at the fast relays, causing the relays to run out of sockets
15137 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
15138 their directory fetches over TLS).
15141 - Finally get rid of the deprecated and now harmful notion of "clique
15142 mode", where directory authorities maintain TLS connections to
15144 - Directory authorities now do an immediate reachability check as soon
15145 as they hear about a new relay. This change should slightly reduce
15146 the time between setting up a relay and getting listed as running
15147 in the consensus. It should also improve the time between setting
15148 up a bridge and seeing use by bridge users.
15149 - Directory authorities no longer launch a TLS connection to every
15150 relay as they startup. Now that we have 2k+ descriptors cached,
15151 the resulting network hiccup is becoming a burden. Besides,
15152 authorities already avoid voting about Running for the first half
15153 hour of their uptime.
15156 Changes in version 0.2.2.12-alpha - 2010-04-20
15157 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
15158 handle and vote on descriptors. It was causing relays to drop out of
15162 - Many relays have been falling out of the consensus lately because
15163 not enough authorities know about their descriptor for them to get
15164 a majority of votes. When we deprecated the v2 directory protocol,
15165 we got rid of the only way that v3 authorities can hear from each
15166 other about other descriptors. Now authorities examine every v3
15167 vote for new descriptors, and fetch them from that authority. Bugfix
15169 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
15170 and a warning in or.h related to bandwidth_weight_rule_t that
15171 prevented clean compile on OS X. Fixes bug 1363; bugfix on
15173 - Fix a segfault on relays when DirReqStatistics is enabled
15174 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
15178 - Demote a confusing TLS warning that relay operators might get when
15179 someone tries to talk to their OrPort. It is neither the operator's
15180 fault nor can they do anything about it. Fixes bug 1364; bugfix
15184 Changes in version 0.2.2.11-alpha - 2010-04-15
15185 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
15186 libraries that was causing some relays to drop out of the consensus.
15189 - Directory mirrors were fetching relay descriptors only from v2
15190 directory authorities, rather than v3 authorities like they should.
15191 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
15192 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
15193 - Fix a parsing error that made every possible value of
15194 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
15195 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
15196 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
15197 about the option without breaking older ones.
15198 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
15199 that claim to be earlier than 0.9.8m, but which have in reality
15200 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
15201 behavior. Possible fix for some cases of bug 1346.
15204 - Experiment with a more aggressive approach to preventing clients
15205 from making one-hop exit streams. Exit relays who want to try it
15206 out can set "RefuseUnknownExits 1" in their torrc, and then look
15207 for "Attempt by %s to open a stream" log messages. Let us know
15209 - Add support for statically linking zlib by specifying
15210 --enable-static-zlib, to go with our support for statically linking
15211 openssl and libevent. Resolves bug 1358.
15214 - Fix a segfault that happens whenever a Tor client that is using
15215 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
15217 - When we cleaned up the contrib/tor-exit-notice.html file, we left
15218 out the first line. Fixes bug 1295.
15219 - When building the manpage from a tarball, we required asciidoc, but
15220 the asciidoc -> roff/html conversion was already done for the
15221 tarball. Make 'make' complain only when we need asciidoc (either
15222 because we're compiling directly from git, or because we altered
15223 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
15224 - When none of the directory authorities vote on any params, Tor
15225 segfaulted when trying to make the consensus from the votes. We
15226 didn't trigger the bug in practice, because authorities do include
15227 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
15230 - In the util/threads test, no longer free the test_mutex before all
15231 worker threads have finished. Bugfix on 0.2.1.6-alpha.
15232 - The master thread could starve the worker threads quite badly on
15233 certain systems, causing them to run only partially in the allowed
15234 window. This resulted in test failures. Now the master thread sleeps
15235 occasionally for a few microseconds while the two worker-threads
15236 compete for the mutex. Bugfix on 0.2.0.1-alpha.
15239 Changes in version 0.2.2.10-alpha - 2010-03-07
15240 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
15241 could prevent relays from guessing their IP address correctly. It also
15242 starts the groundwork for another client-side performance boost, since
15243 currently we're not making efficient use of relays that have both the
15244 Guard flag and the Exit flag.
15247 - Fix a regression from our patch for bug 1244 that caused relays
15248 to guess their IP address incorrectly if they didn't set Address
15249 in their torrc and/or their address fails to resolve. Bugfix on
15250 0.2.2.9-alpha; fixes bug 1269.
15252 o Major features (performance):
15253 - Directory authorities now compute consensus weightings that instruct
15254 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
15255 and no flag. Clients that use these weightings will distribute
15256 network load more evenly across these different relay types. The
15257 weightings are in the consensus so we can change them globally in
15258 the future. Extra thanks to "outofwords" for finding some nasty
15259 security bugs in the first implementation of this feature.
15261 o Minor features (performance):
15262 - Always perform router selections using weighted relay bandwidth,
15263 even if we don't need a high capacity circuit at the time. Non-fast
15264 circuits now only differ from fast ones in that they can use relays
15265 not marked with the Fast flag. This "feature" could turn out to
15266 be a horrible bug; we should investigate more before it goes into
15270 - Allow disabling building of the manpages. Skipping the manpage
15271 speeds up the build considerably.
15273 o Minor bugfixes (on 0.2.2.x):
15274 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
15275 Bugfix on 0.2.2.9-alpha.
15276 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
15277 config option. Bugfix on 0.2.2.7-alpha.
15278 - Ship the asciidoc-helper file in the tarball, so that people can
15279 build from source if they want to, and touching the .1.txt files
15280 doesn't break the build. Bugfix on 0.2.2.9-alpha.
15282 o Minor bugfixes (on 0.2.1.x or earlier):
15283 - Fix a dereference-then-NULL-check sequence when publishing
15284 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
15286 - Fix another dereference-then-NULL-check sequence. Bugfix on
15287 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
15288 - Make sure we treat potentially not NUL-terminated strings correctly.
15289 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
15291 o Code simplifications and refactoring:
15292 - Fix some urls in the exit notice file and make it XHTML1.1 strict
15293 compliant. Based on a patch from Christian Kujau.
15294 - Don't use sed in asciidoc-helper anymore.
15295 - Make the build process fail if asciidoc cannot be found and
15296 building with asciidoc isn't disabled.
15299 Changes in version 0.2.2.9-alpha - 2010-02-22
15300 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
15301 location of a directory authority, and cleans up a bunch of small bugs.
15303 o Directory authority changes:
15304 - Change IP address for dannenberg (v3 directory authority), and
15305 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
15306 service directory authority) from the list.
15309 - Make Tor work again on the latest OS X: when deciding whether to
15310 use strange flags to turn TLS renegotiation on, detect the OpenSSL
15311 version at run-time, not compile time. We need to do this because
15312 Apple doesn't update its dev-tools headers when it updates its
15313 libraries in a security patch.
15314 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
15315 that could happen on 32-bit platforms with 64-bit time_t. Also fix
15316 a memory leak when requesting a hidden service descriptor we've
15317 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
15319 - Authorities could be tricked into giving out the Exit flag to relays
15320 that didn't allow exiting to any ports. This bug could screw
15321 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
15322 1238. Bug discovered by Martin Kowalczyk.
15323 - When freeing a session key, zero it out completely. We only zeroed
15324 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
15325 patched by ekir. Fixes bug 1254.
15328 - Fix static compilation by listing the openssl libraries in the right
15329 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
15330 - Resume handling .exit hostnames in a special way: originally we
15331 stripped the .exit part and used the requested exit relay. In
15332 0.2.2.1-alpha we stopped treating them in any special way, meaning
15333 if you use a .exit address then Tor will pass it on to the exit
15334 relay. Now we reject the .exit stream outright, since that behavior
15335 might be more expected by the user. Found and diagnosed by Scott
15336 Bennett and Downie on or-talk.
15337 - Don't spam the controller with events when we have no file
15338 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
15339 for log messages was already solved from bug 748.)
15340 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
15342 - Make the DNSPort option work with libevent 2.x. Don't alter the
15343 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
15344 - Emit a GUARD DROPPED controller event for a case we missed.
15345 - Make more fields in the controller protocol case-insensitive, since
15346 control-spec.txt said they were.
15347 - Refactor resolve_my_address() to not use gethostbyname() anymore.
15348 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
15349 - Fix a spec conformance issue: the network-status-version token
15350 must be the first token in a v3 consensus or vote. Discovered by
15351 parakeep. Bugfix on 0.2.0.3-alpha.
15353 o Code simplifications and refactoring:
15354 - Generate our manpage and HTML documentation using Asciidoc. This
15355 change should make it easier to maintain the documentation, and
15356 produce nicer HTML.
15357 - Remove the --enable-iphone option. According to reports from Marco
15358 Bonetti, Tor builds fine without any special tweaking on recent
15359 iPhone SDK versions.
15360 - Removed some unnecessary files from the source distribution. The
15361 AUTHORS file has now been merged into the people page on the
15362 website. The roadmaps and design doc can now be found in the
15363 projects directory in svn.
15364 - Enabled various circuit build timeout constants to be controlled
15365 by consensus parameters. Also set better defaults for these
15366 parameters based on experimentation on broadband and simulated
15367 high latency links.
15370 - The 'EXTENDCIRCUIT' control port command can now be used with
15371 a circ id of 0 and no path. This feature will cause Tor to build
15372 a new 'fast' general purpose circuit using its own path selection
15374 - Added a BUILDTIMEOUT_SET controller event to describe changes
15375 to the circuit build timeout.
15376 - Future-proof the controller protocol a bit by ignoring keyword
15377 arguments we do not recognize.
15378 - Expand homedirs passed to tor-checkkey. This should silence a
15379 coverity complaint about passing a user-supplied string into
15380 open() without checking it.
15383 Changes in version 0.2.1.25 - 2010-03-16
15384 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
15385 prevent relays from guessing their IP address correctly. It also fixes
15386 several minor potential security bugs.
15389 - Fix a regression from our patch for bug 1244 that caused relays
15390 to guess their IP address incorrectly if they didn't set Address
15391 in their torrc and/or their address fails to resolve. Bugfix on
15392 0.2.1.23; fixes bug 1269.
15393 - When freeing a session key, zero it out completely. We only zeroed
15394 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
15395 patched by ekir. Fixes bug 1254.
15398 - Fix a dereference-then-NULL-check sequence when publishing
15399 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
15401 - Fix another dereference-then-NULL-check sequence. Bugfix on
15402 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
15403 - Make sure we treat potentially not NUL-terminated strings correctly.
15404 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
15408 Changes in version 0.2.1.24 - 2010-02-21
15409 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
15413 - Work correctly out-of-the-box with even more vendor-patched versions
15414 of OpenSSL. In particular, make it so Debian and OS X don't need
15415 customized patches to run/build.
15418 Changes in version 0.2.1.23 - 2010-02-13
15419 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
15420 again on the latest OS X, and updates the location of a directory
15423 o Major bugfixes (performance):
15424 - We were selecting our guards uniformly at random, and then weighting
15425 which of our guards we'd use uniformly at random. This imbalance
15426 meant that Tor clients were severely limited on throughput (and
15427 probably latency too) by the first hop in their circuit. Now we
15428 select guards weighted by currently advertised bandwidth. We also
15429 automatically discard guards picked using the old algorithm. Fixes
15430 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
15433 - Make Tor work again on the latest OS X: when deciding whether to
15434 use strange flags to turn TLS renegotiation on, detect the OpenSSL
15435 version at run-time, not compile time. We need to do this because
15436 Apple doesn't update its dev-tools headers when it updates its
15437 libraries in a security patch.
15438 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
15439 that could happen on 32-bit platforms with 64-bit time_t. Also fix
15440 a memory leak when requesting a hidden service descriptor we've
15441 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
15444 o Directory authority changes:
15445 - Change IP address for dannenberg (v3 directory authority), and
15446 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
15447 service directory authority) from the list.
15450 - Refactor resolve_my_address() to not use gethostbyname() anymore.
15451 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
15454 - Avoid a mad rush at the beginning of each month when each client
15455 rotates half of its guards. Instead we spread the rotation out
15456 throughout the month, but we still avoid leaving a precise timestamp
15457 in the state file about when we first picked the guard. Improves
15458 over the behavior introduced in 0.1.2.17.
15461 Changes in version 0.2.2.8-alpha - 2010-01-26
15462 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
15463 causing bridge relays to disappear. If you're running a bridge,
15467 - Fix a memory corruption bug on bridges that occured during the
15468 inclusion of stats data in extra-info descriptors. Also fix the
15469 interface for geoip_get_bridge_stats* to prevent similar bugs in
15470 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
15471 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
15474 - Ignore OutboundBindAddress when connecting to localhost.
15475 Connections to localhost need to come _from_ localhost, or else
15476 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
15480 Changes in version 0.2.2.7-alpha - 2010-01-19
15481 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
15482 as laying the groundwork for further relay-side performance fixes. It
15483 also starts cleaning up client behavior with respect to the EntryNodes,
15484 ExitNodes, and StrictNodes config options.
15486 This release also rotates two directory authority keys, due to a
15487 security breach of some of the Torproject servers.
15489 o Directory authority changes:
15490 - Rotate keys (both v3 identity and relay identity) for moria1
15493 o Major features (performance):
15494 - We were selecting our guards uniformly at random, and then weighting
15495 which of our guards we'd use uniformly at random. This imbalance
15496 meant that Tor clients were severely limited on throughput (and
15497 probably latency too) by the first hop in their circuit. Now we
15498 select guards weighted by currently advertised bandwidth. We also
15499 automatically discard guards picked using the old algorithm. Fixes
15500 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
15501 - When choosing which cells to relay first, relays can now favor
15502 circuits that have been quiet recently, to provide lower latency
15503 for low-volume circuits. By default, relays enable or disable this
15504 feature based on a setting in the consensus. You can override
15505 this default by using the new "CircuitPriorityHalflife" config
15506 option. Design and code by Ian Goldberg, Can Tang, and Chris
15508 - Add separate per-conn write limiting to go with the per-conn read
15509 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
15510 but never per-conn write limits.
15511 - New consensus params "bwconnrate" and "bwconnburst" to let us
15512 rate-limit client connections as they enter the network. It's
15513 controlled in the consensus so we can turn it on and off for
15514 experiments. It's starting out off. Based on proposal 163.
15516 o Major features (relay selection options):
15517 - Switch to a StrictNodes config option, rather than the previous
15518 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
15519 "StrictExcludeNodes" option.
15520 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
15521 change during a config reload, mark and discard all our origin
15522 circuits. This fix should address edge cases where we change the
15523 config options and but then choose a circuit that we created before
15525 - If EntryNodes or ExitNodes are set, be more willing to use an
15526 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
15528 - Make EntryNodes config option much more aggressive even when
15529 StrictNodes is not set. Before it would prepend your requested
15530 entrynodes to your list of guard nodes, but feel free to use others
15531 after that. Now it chooses only from your EntryNodes if any of
15532 those are available, and only falls back to others if a) they're
15533 all down and b) StrictNodes is not set.
15534 - Now we refresh your entry guards from EntryNodes at each consensus
15535 fetch -- rather than just at startup and then they slowly rot as
15536 the network changes.
15539 - Stop bridge directory authorities from answering dbg-stability.txt
15540 directory queries, which would let people fetch a list of all
15541 bridge identities they track. Bugfix on 0.2.1.6-alpha.
15544 - Log a notice when we get a new control connection. Now it's easier
15545 for security-conscious users to recognize when a local application
15546 is knocking on their controller door. Suggested by bug 1196.
15547 - New config option "CircuitStreamTimeout" to override our internal
15548 timeout schedule for how many seconds until we detach a stream from
15549 a circuit and try a new circuit. If your network is particularly
15550 slow, you might want to set this to a number like 60.
15551 - New controller command "getinfo config-text". It returns the
15552 contents that Tor would write if you send it a SAVECONF command,
15553 so the controller can write the file to disk itself.
15554 - New options for SafeLogging to allow scrubbing only log messages
15555 generated while acting as a relay.
15556 - Ship the bridges spec file in the tarball too.
15557 - Avoid a mad rush at the beginning of each month when each client
15558 rotates half of its guards. Instead we spread the rotation out
15559 throughout the month, but we still avoid leaving a precise timestamp
15560 in the state file about when we first picked the guard. Improves
15561 over the behavior introduced in 0.1.2.17.
15563 o Minor bugfixes (compiling):
15564 - Fix compilation on OS X 10.3, which has a stub mlockall() but
15565 hides it. Bugfix on 0.2.2.6-alpha.
15566 - Fix compilation on Solaris by removing support for the
15567 DisableAllSwap config option. Solaris doesn't have an rlimit for
15568 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
15571 o Minor bugfixes (crashes):
15572 - Do not segfault when writing buffer stats when we haven't observed
15573 a single circuit to report about. Found by Fabian Lanze. Bugfix on
15575 - If we're in the pathological case where there's no exit bandwidth
15576 but there is non-exit bandwidth, or no guard bandwidth but there
15577 is non-guard bandwidth, don't crash during path selection. Bugfix
15579 - Fix an impossible-to-actually-trigger buffer overflow in relay
15580 descriptor generation. Bugfix on 0.1.0.15.
15582 o Minor bugfixes (privacy):
15583 - Fix an instance where a Tor directory mirror might accidentally
15584 log the IP address of a misbehaving Tor client. Bugfix on
15586 - Don't list Windows capabilities in relay descriptors. We never made
15587 use of them, and maybe it's a bad idea to publish them. Bugfix
15590 o Minor bugfixes (other):
15591 - Resolve an edge case in path weighting that could make us misweight
15592 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
15593 - Fix statistics on client numbers by country as seen by bridges that
15594 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
15595 intervals instead of variable 12-to-48-hour intervals.
15596 - After we free an internal connection structure, overwrite it
15597 with a different memory value than we use for overwriting a freed
15598 internal circuit structure. Should help with debugging. Suggested
15600 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
15603 o Removed features:
15604 - Remove the HSAuthorityRecordStats option that version 0 hidden
15605 service authorities could have used to track statistics of overall
15606 hidden service usage.
15609 Changes in version 0.2.1.22 - 2010-01-19
15610 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
15611 authorities -- it would tell you its whole history of bridge descriptors
15612 if you make the right directory request. This stable update also
15613 rotates two of the seven v3 directory authority keys and locations.
15615 o Directory authority changes:
15616 - Rotate keys (both v3 identity and relay identity) for moria1
15620 - Stop bridge directory authorities from answering dbg-stability.txt
15621 directory queries, which would let people fetch a list of all
15622 bridge identities they track. Bugfix on 0.2.1.6-alpha.
15625 Changes in version 0.2.1.21 - 2009-12-21
15626 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
15627 library. If you use Tor on Linux / Unix and you're getting SSL
15628 renegotiation errors, upgrading should help. We also recommend an
15629 upgrade if you're an exit relay.
15632 - Work around a security feature in OpenSSL 0.9.8l that prevents our
15633 handshake from working unless we explicitly tell OpenSSL that we
15634 are using SSL renegotiation safely. We are, of course, but OpenSSL
15635 0.9.8l won't work unless we say we are.
15636 - Avoid crashing if the client is trying to upload many bytes and the
15637 circuit gets torn down at the same time, or if the flip side
15638 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
15641 - Do not refuse to learn about authority certs and v2 networkstatus
15642 documents that are older than the latest consensus. This bug might
15643 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
15644 Spotted and fixed by xmux.
15645 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
15646 trigger platform-specific option misparsing case found by Coverity
15648 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
15649 trigger assert. Fixes bug 1173.
15652 Changes in version 0.2.2.6-alpha - 2009-11-19
15653 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
15654 support for the new lower-footprint "microdescriptor" directory design,
15655 future-proofing our consensus format against new hash functions or
15656 other changes, and an Android port. It also makes Tor compatible with
15657 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
15660 - Directory authorities can now create, vote on, and serve multiple
15661 parallel formats of directory data as part of their voting process.
15662 Partially implements Proposal 162: "Publish the consensus in
15664 - Directory authorities can now agree on and publish small summaries
15665 of router information that clients can use in place of regular
15666 server descriptors. This transition will eventually allow clients
15667 to use far less bandwidth for downloading information about the
15668 network. Begins the implementation of Proposal 158: "Clients
15669 download consensus + microdescriptors".
15670 - The directory voting system is now extensible to use multiple hash
15671 algorithms for signatures and resource selection. Newer formats
15672 are signed with SHA256, with a possibility for moving to a better
15673 hash algorithm in the future.
15674 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
15675 current and future memory pages via mlockall(). On supported
15676 platforms (modern Linux and probably BSD but not Windows or OS X),
15677 this should effectively disable any and all attempts to page out
15678 memory. This option requires that you start your Tor as root --
15679 if you use DisableAllSwap, please consider using the User option
15680 to properly reduce the privileges of your Tor.
15681 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
15682 to help Tor build correctly for Android phones.
15685 - Work around a security feature in OpenSSL 0.9.8l that prevents our
15686 handshake from working unless we explicitly tell OpenSSL that we
15687 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
15688 won't work unless we say we are.
15691 - Fix a crash bug when trying to initialize the evdns module in
15692 Libevent 2. Bugfix on 0.2.1.16-rc.
15693 - Stop logging at severity 'warn' when some other Tor client tries
15694 to establish a circuit with us using weak DH keys. It's a protocol
15695 violation, but that doesn't mean ordinary users need to hear about
15696 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
15697 - Do not refuse to learn about authority certs and v2 networkstatus
15698 documents that are older than the latest consensus. This bug might
15699 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
15700 Spotted and fixed by xmux.
15701 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
15702 - If all authorities restart at once right before a consensus vote,
15703 nobody will vote about "Running", and clients will get a consensus
15704 with no usable relays. Instead, authorities refuse to build a
15705 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
15706 - If your relay can't keep up with the number of incoming create
15707 cells, it would log one warning per failure into your logs. Limit
15708 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
15709 - Bridges now use "reject *:*" as their default exit policy. Bugfix
15710 on 0.2.0.3-alpha; fixes bug 1113.
15711 - Fix a memory leak on directory authorities during voting that was
15712 introduced in 0.2.2.1-alpha. Found via valgrind.
15715 Changes in version 0.2.1.20 - 2009-10-15
15716 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
15717 services at once, prepares for more performance improvements, and
15718 fixes a bunch of smaller bugs.
15720 The Windows and OS X bundles also include a more recent Vidalia,
15721 and switch from Privoxy to Polipo.
15723 The OS X installers are now drag and drop. It's best to un-install
15724 Tor/Vidalia and then install this new bundle, rather than upgrade. If
15725 you want to upgrade, you'll need to update the paths for Tor and Polipo
15726 in the Vidalia Settings window.
15729 - Send circuit or stream sendme cells when our window has decreased
15730 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
15731 by Karsten when testing the "reduce circuit window" performance
15732 patch. Bugfix on the 54th commit on Tor -- from July 2002,
15733 before the release of Tor 0.0.0. This is the new winner of the
15735 - Fix a remotely triggerable memory leak when a consensus document
15736 contains more than one signature from the same voter. Bugfix on
15738 - Avoid segfault in rare cases when finishing an introduction circuit
15739 as a client and finding out that we don't have an introduction key
15740 for it. Fixes bug 1073. Reported by Aaron Swartz.
15743 - Tor now reads the "circwindow" parameter out of the consensus,
15744 and uses that value for its circuit package window rather than the
15745 default of 1000 cells. Begins the implementation of proposal 168.
15747 o New directory authorities:
15748 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
15750 - Move moria1 and tonga to alternate IP addresses.
15753 - Fix a signed/unsigned compile warning in 0.2.1.19.
15754 - Fix possible segmentation fault on directory authorities. Bugfix on
15756 - Fix an extremely rare infinite recursion bug that could occur if
15757 we tried to log a message after shutting down the log subsystem.
15758 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
15759 - Fix an obscure bug where hidden services on 64-bit big-endian
15760 systems might mis-read the timestamp in v3 introduce cells, and
15761 refuse to connect back to the client. Discovered by "rotor".
15762 Bugfix on 0.2.1.6-alpha.
15763 - We were triggering a CLOCK_SKEW controller status event whenever
15764 we connect via the v2 connection protocol to any relay that has
15765 a wrong clock. Instead, we should only inform the controller when
15766 it's a trusted authority that claims our clock is wrong. Bugfix
15767 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
15768 - We were telling the controller about CHECKING_REACHABILITY and
15769 REACHABILITY_FAILED status events whenever we launch a testing
15770 circuit or notice that one has failed. Instead, only tell the
15771 controller when we want to inform the user of overall success or
15772 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
15774 - Don't warn when we're using a circuit that ends with a node
15775 excluded in ExcludeExitNodes, but the circuit is not used to access
15776 the outside world. This should help fix bug 1090. Bugfix on
15778 - Work around a small memory leak in some versions of OpenSSL that
15779 stopped the memory used by the hostname TLS extension from being
15783 - Add a "getinfo status/accepted-server-descriptor" controller
15784 command, which is the recommended way for controllers to learn
15785 whether our server descriptor has been successfully received by at
15786 least on directory authority. Un-recommend good-server-descriptor
15787 getinfo and status events until we have a better design for them.
15790 Changes in version 0.2.2.5-alpha - 2009-10-11
15791 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
15794 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
15796 o Directory authorities:
15797 - Temporarily (just for this release) move dizum to an alternate
15801 Changes in version 0.2.2.4-alpha - 2009-10-10
15802 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
15803 introduces a new unit test framework, shifts directry authority
15804 addresses around to reduce the impact from recent blocking events,
15805 and fixes a few smaller bugs.
15808 - Fix several more asserts in the circuit_build_times code, for
15809 example one that causes Tor to fail to start once we have
15810 accumulated 5000 build times in the state file. Bugfixes on
15811 0.2.2.2-alpha; fixes bug 1108.
15813 o New directory authorities:
15814 - Move moria1 and Tonga to alternate IP addresses.
15817 - Log SSL state transitions at debug level during handshake, and
15818 include SSL states in error messages. This may help debug future
15819 SSL handshake issues.
15820 - Add a new "Handshake" log domain for activities that happen
15821 during the TLS handshake.
15822 - Revert to the "June 3 2009" ip-to-country file. The September one
15823 seems to have removed most US IP addresses.
15824 - Directory authorities now reject Tor relays with versions less than
15825 0.1.2.14. This step cuts out four relays from the current network,
15826 none of which are very big.
15829 - Fix a couple of smaller issues with gathering statistics. Bugfixes
15831 - Fix two memory leaks in the error case of
15832 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
15833 - Don't count one-hop circuits when we're estimating how long it
15834 takes circuits to build on average. Otherwise we'll set our circuit
15835 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
15836 - Directory authorities no longer change their opinion of, or vote on,
15837 whether a router is Running, unless they have themselves been
15838 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
15841 o Code simplifications and refactoring:
15842 - Revise our unit tests to use the "tinytest" framework, so we
15843 can run tests in their own processes, have smarter setup/teardown
15844 code, and so on. The unit test code has moved to its own
15845 subdirectory, and has been split into multiple modules.
15848 Changes in version 0.2.2.3-alpha - 2009-09-23
15849 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
15852 - Fix an overzealous assert in our new circuit build timeout code.
15853 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
15856 - If the networkstatus consensus tells us that we should use a
15857 negative circuit package window, ignore it. Otherwise we'll
15858 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
15861 Changes in version 0.2.2.2-alpha - 2009-09-21
15862 Tor 0.2.2.2-alpha introduces our latest performance improvement for
15863 clients: Tor tracks the average time it takes to build a circuit, and
15864 avoids using circuits that take too long to build. For fast connections,
15865 this feature can cut your expected latency in half. For slow or flaky
15866 connections, it could ruin your Tor experience. Let us know if it does!
15869 - Tor now tracks how long it takes to build client-side circuits
15870 over time, and adapts its timeout to local network performance.
15871 Since a circuit that takes a long time to build will also provide
15872 bad performance, we get significant latency improvements by
15873 discarding the slowest 20% of circuits. Specifically, Tor creates
15874 circuits more aggressively than usual until it has enough data
15875 points for a good timeout estimate. Implements proposal 151.
15876 We are especially looking for reports (good and bad) from users with
15877 both EDGE and broadband connections that can move from broadband
15878 to EDGE and find out if the build-time data in the .tor/state gets
15879 reset without loss of Tor usability. You should also see a notice
15880 log message telling you that Tor has reset its timeout.
15881 - Directory authorities can now vote on arbitary integer values as
15882 part of the consensus process. This is designed to help set
15883 network-wide parameters. Implements proposal 167.
15884 - Tor now reads the "circwindow" parameter out of the consensus,
15885 and uses that value for its circuit package window rather than the
15886 default of 1000 cells. Begins the implementation of proposal 168.
15889 - Fix a remotely triggerable memory leak when a consensus document
15890 contains more than one signature from the same voter. Bugfix on
15894 - Fix an extremely rare infinite recursion bug that could occur if
15895 we tried to log a message after shutting down the log subsystem.
15896 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
15897 - Fix parsing for memory or time units given without a space between
15898 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
15899 - A networkstatus vote must contain exactly one signature. Spec
15900 conformance issue. Bugfix on 0.2.0.3-alpha.
15901 - Fix an obscure bug where hidden services on 64-bit big-endian
15902 systems might mis-read the timestamp in v3 introduce cells, and
15903 refuse to connect back to the client. Discovered by "rotor".
15904 Bugfix on 0.2.1.6-alpha.
15905 - We were triggering a CLOCK_SKEW controller status event whenever
15906 we connect via the v2 connection protocol to any relay that has
15907 a wrong clock. Instead, we should only inform the controller when
15908 it's a trusted authority that claims our clock is wrong. Bugfix
15909 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
15910 - We were telling the controller about CHECKING_REACHABILITY and
15911 REACHABILITY_FAILED status events whenever we launch a testing
15912 circuit or notice that one has failed. Instead, only tell the
15913 controller when we want to inform the user of overall success or
15914 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
15916 - Don't warn when we're using a circuit that ends with a node
15917 excluded in ExcludeExitNodes, but the circuit is not used to access
15918 the outside world. This should help fix bug 1090, but more problems
15919 remain. Bugfix on 0.2.1.6-alpha.
15920 - Work around a small memory leak in some versions of OpenSSL that
15921 stopped the memory used by the hostname TLS extension from being
15923 - Make our 'torify' script more portable; if we have only one of
15924 'torsocks' or 'tsocks' installed, don't complain to the user;
15925 and explain our warning about tsocks better.
15928 - Add a "getinfo status/accepted-server-descriptor" controller
15929 command, which is the recommended way for controllers to learn
15930 whether our server descriptor has been successfully received by at
15931 least on directory authority. Un-recommend good-server-descriptor
15932 getinfo and status events until we have a better design for them.
15933 - Update to the "September 4 2009" ip-to-country file.
15936 Changes in version 0.2.2.1-alpha - 2009-08-26
15937 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
15938 Tor clients to bootstrap on networks where only port 80 is reachable,
15939 makes it more straightforward to support hardware crypto accelerators,
15940 and starts the groundwork for gathering stats safely at relays.
15943 - Start the process of disabling ".exit" address notation, since it
15944 can be used for a variety of esoteric application-level attacks
15945 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
15948 o New directory authorities:
15949 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
15953 - New AccelName and AccelDir options add support for dynamic OpenSSL
15954 hardware crypto acceleration engines.
15955 - Tor now supports tunneling all of its outgoing connections over
15956 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
15957 configuration options. Code by Christopher Davis.
15960 - Send circuit or stream sendme cells when our window has decreased
15961 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
15962 by Karsten when testing the "reduce circuit window" performance
15963 patch. Bugfix on the 54th commit on Tor -- from July 2002,
15964 before the release of Tor 0.0.0. This is the new winner of the
15967 o New options for gathering stats safely:
15968 - Directory mirrors that set "DirReqStatistics 1" write statistics
15969 about directory requests to disk every 24 hours. As compared to the
15970 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
15971 1) stats are written to disk exactly every 24 hours; 2) estimated
15972 shares of v2 and v3 requests are determined as mean values, not at
15973 the end of a measurement period; 3) unresolved requests are listed
15974 with country code '??'; 4) directories also measure download times.
15975 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
15976 number of exit streams and transferred bytes per port to disk every
15978 - Relays that set "CellStatistics 1" write statistics on how long
15979 cells spend in their circuit queues to disk every 24 hours.
15980 - Entry nodes that set "EntryStatistics 1" write statistics on the
15981 rough number and origins of connecting clients to disk every 24
15983 - Relays that write any of the above statistics to disk and set
15984 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
15985 their extra-info documents.
15988 - New --digests command-line switch to output the digests of the
15989 source files Tor was built with.
15990 - The "torify" script now uses torsocks where available.
15991 - The memarea code now uses a sentinel value at the end of each area
15992 to make sure nothing writes beyond the end of an area. This might
15993 help debug some conceivable causes of bug 930.
15994 - Time and memory units in the configuration file can now be set to
15995 fractional units. For example, "2.5 GB" is now a valid value for
15997 - Certain Tor clients (such as those behind check.torproject.org) may
15998 want to fetch the consensus in an extra early manner. To enable this
15999 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
16000 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
16001 as only certain clients who must have this information sooner should
16003 - Instead of adding the svn revision to the Tor version string, report
16004 the git commit (when we're building from a git checkout).
16007 - If any of the v3 certs we download are unparseable, we should
16008 actually notice the failure so we don't retry indefinitely. Bugfix
16009 on 0.2.0.x; reported by "rotator".
16010 - If the cached cert file is unparseable, warn but don't exit.
16011 - Fix possible segmentation fault on directory authorities. Bugfix on
16013 - When Tor fails to parse a descriptor of any kind, dump it to disk.
16014 Might help diagnosing bug 1051.
16016 o Deprecated and removed features:
16017 - The controller no longer accepts the old obsolete "addr-mappings/"
16018 or "unregistered-servers-" GETINFO values.
16019 - Hidden services no longer publish version 0 descriptors, and clients
16020 do not request or use version 0 descriptors. However, the old hidden
16021 service authorities still accept and serve version 0 descriptors
16022 when contacted by older hidden services/clients.
16023 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
16024 always on; using them is necessary for correct forward-compatible
16026 - Remove support for .noconnect style addresses. Nobody was using
16027 them, and they provided another avenue for detecting Tor users
16028 via application-level web tricks.
16030 o Packaging changes:
16031 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
16032 installer bundles. See
16033 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
16034 for details of what's new in Vidalia 0.2.3.
16035 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
16036 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
16037 configuration file, rather than the old Privoxy.
16038 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
16039 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
16040 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
16041 better compatibility with OS X 10.6, aka Snow Leopard.
16042 - OS X Vidalia Bundle: The multi-package installer is now replaced
16043 by a simple drag and drop to the /Applications folder. This change
16044 occurred with the upgrade to Vidalia 0.2.3.
16047 Changes in version 0.2.1.19 - 2009-07-28
16048 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
16049 services on Tor 0.2.1.3-alpha through 0.2.1.18.
16052 - Make accessing hidden services on 0.2.1.x work right again.
16053 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
16054 part of patch provided by "optimist".
16057 - When a relay/bridge is writing out its identity key fingerprint to
16058 the "fingerprint" file and to its logs, write it without spaces. Now
16059 it will look like the fingerprints in our bridges documentation,
16060 and confuse fewer users.
16063 - Relays no longer publish a new server descriptor if they change
16064 their MaxAdvertisedBandwidth config option but it doesn't end up
16065 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
16066 fixes bug 1026. Patch from Sebastian.
16067 - Avoid leaking memory every time we get a create cell but we have
16068 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
16069 fixes bug 1034. Reported by BarkerJr.
16072 Changes in version 0.2.1.18 - 2009-07-24
16073 Tor 0.2.1.18 lays the foundations for performance improvements,
16074 adds status events to help users diagnose bootstrap problems, adds
16075 optional authentication/authorization for hidden services, fixes a
16076 variety of potential anonymity problems, and includes a huge pile of
16077 other features and bug fixes.
16080 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
16083 Changes in version 0.2.1.17-rc - 2009-07-07
16084 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
16085 candidate for the 0.2.1.x series. It lays the groundwork for further
16086 client performance improvements, and also fixes a big bug with directory
16087 authorities that were causing them to assign Guard and Stable flags
16090 The Windows bundles also finally include the geoip database that we
16091 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
16092 should actually install Torbutton rather than giving you a cryptic
16093 failure message (oops).
16096 - Clients now use the bandwidth values in the consensus, rather than
16097 the bandwidth values in each relay descriptor. This approach opens
16098 the door to more accurate bandwidth estimates once the directory
16099 authorities start doing active measurements. Implements more of
16103 - When Tor clients restart after 1-5 days, they discard all their
16104 cached descriptors as too old, but they still use the cached
16105 consensus document. This approach is good for robustness, but
16106 bad for performance: since they don't know any bandwidths, they
16107 end up choosing at random rather than weighting their choice by
16108 speed. Fixed by the above feature of putting bandwidths in the
16109 consensus. Bugfix on 0.2.0.x.
16110 - Directory authorities were neglecting to mark relays down in their
16111 internal histories if the relays fall off the routerlist without
16112 ever being found unreachable. So there were relays in the histories
16113 that haven't been seen for eight months, and are listed as being
16114 up for eight months. This wreaked havoc on the "median wfu"
16115 and "median mtbf" calculations, in turn making Guard and Stable
16116 flags very wrong, hurting network performance. Fixes bugs 696 and
16117 969. Bugfix on 0.2.0.6-alpha.
16120 - Serve the DirPortFrontPage page even when we have been approaching
16121 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
16122 - The control port would close the connection before flushing long
16123 replies, such as the network consensus, if a QUIT command was issued
16124 before the reply had completed. Now, the control port flushes all
16125 pending replies before closing the connection. Also fixed a spurious
16126 warning when a QUIT command is issued after a malformed or rejected
16127 AUTHENTICATE command, but before the connection was closed. Patch
16128 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
16129 - When we can't find an intro key for a v2 hidden service descriptor,
16130 fall back to the v0 hidden service descriptor and log a bug message.
16131 Workaround for bug 1024.
16132 - Fix a log message that did not respect the SafeLogging option.
16136 - If we're a relay and we change our IP address, be more verbose
16137 about the reason that made us change. Should help track down
16138 further bugs for relays on dynamic IP addresses.
16141 Changes in version 0.2.0.35 - 2009-06-24
16143 - Avoid crashing in the presence of certain malformed descriptors.
16144 Found by lark, and by automated fuzzing.
16145 - Fix an edge case where a malicious exit relay could convince a
16146 controller that the client's DNS question resolves to an internal IP
16147 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
16150 - Finally fix the bug where dynamic-IP relays disappear when their
16151 IP address changes: directory mirrors were mistakenly telling
16152 them their old address if they asked via begin_dir, so they
16153 never got an accurate answer about their new address, so they
16154 just vanished after a day. For belt-and-suspenders, relays that
16155 don't set Address in their config now avoid using begin_dir for
16156 all direct connections. Should fix bugs 827, 883, and 900.
16157 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
16158 that would occur on some exit nodes when DNS failures and timeouts
16159 occurred in certain patterns. Fix for bug 957.
16162 - When starting with a cache over a few days old, do not leak
16163 memory for the obsolete router descriptors in it. Bugfix on
16164 0.2.0.33; fixes bug 672.
16165 - Hidden service clients didn't use a cached service descriptor that
16166 was older than 15 minutes, but wouldn't fetch a new one either,
16167 because there was already one in the cache. Now, fetch a v2
16168 descriptor unless the same descriptor was added to the cache within
16169 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
16172 Changes in version 0.2.1.16-rc - 2009-06-20
16173 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
16174 a bunch of minor bugs.
16177 - Fix an edge case where a malicious exit relay could convince a
16178 controller that the client's DNS question resolves to an internal IP
16179 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
16181 o Major performance improvements (on 0.2.0.x):
16182 - Disable and refactor some debugging checks that forced a linear scan
16183 over the whole server-side DNS cache. These accounted for over 50%
16184 of CPU time on a relatively busy exit node's gprof profile. Found
16186 - Disable some debugging checks that appeared in exit node profile
16190 - Update to the "June 3 2009" ip-to-country file.
16191 - Do not have tor-resolve automatically refuse all .onion addresses;
16192 if AutomapHostsOnResolve is set in your torrc, this will work fine.
16194 o Minor bugfixes (on 0.2.0.x):
16195 - Log correct error messages for DNS-related network errors on
16197 - Fix a race condition that could cause crashes or memory corruption
16198 when running as a server with a controller listening for log
16200 - Avoid crashing when we have a policy specified in a DirPolicy or
16201 SocksPolicy or ReachableAddresses option with ports set on it,
16202 and we re-load the policy. May fix bug 996.
16203 - Hidden service clients didn't use a cached service descriptor that
16204 was older than 15 minutes, but wouldn't fetch a new one either,
16205 because there was already one in the cache. Now, fetch a v2
16206 descriptor unless the same descriptor was added to the cache within
16207 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
16209 o Minor bugfixes (on 0.2.1.x):
16210 - Don't warn users about low port and hibernation mix when they
16211 provide a *ListenAddress directive to fix that. Bugfix on
16213 - When switching back and forth between bridge mode, do not start
16214 gathering GeoIP data until two hours have passed.
16215 - Do not complain that the user has requested an excluded node as
16216 an exit when the node is not really an exit. This could happen
16217 because the circuit was for testing, or an introduction point.
16221 Changes in version 0.2.1.15-rc - 2009-05-25
16222 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
16223 series. It fixes a major bug on fast exit relays, as well as a variety
16224 of more minor bugs.
16226 o Major bugfixes (on 0.2.0.x):
16227 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
16228 that would occur on some exit nodes when DNS failures and timeouts
16229 occurred in certain patterns. Fix for bug 957.
16231 o Minor bugfixes (on 0.2.0.x):
16232 - Actually return -1 in the error case for read_bandwidth_usage().
16233 Harmless bug, since we currently don't care about the return value
16234 anywhere. Bugfix on 0.2.0.9-alpha.
16235 - Provide a more useful log message if bug 977 (related to buffer
16236 freelists) ever reappears, and do not crash right away.
16237 - Fix an assertion failure on 64-bit platforms when we allocated
16238 memory right up to the end of a memarea, then realigned the memory
16239 one step beyond the end. Fixes a possible cause of bug 930.
16240 - Protect the count of open sockets with a mutex, so we can't
16241 corrupt it when two threads are closing or opening sockets at once.
16242 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
16243 - Don't allow a bridge to publish its router descriptor to a
16244 non-bridge directory authority. Fixes part of bug 932.
16245 - When we change to or from being a bridge, reset our counts of
16246 client usage by country. Fixes bug 932.
16247 - Fix a bug that made stream bandwidth get misreported to the
16249 - Stop using malloc_usable_size() to use more area than we had
16250 actually allocated: it was safe, but made valgrind really unhappy.
16251 - Fix a memory leak when v3 directory authorities load their keys
16252 and cert from disk. Bugfix on 0.2.0.1-alpha.
16254 o Minor bugfixes (on 0.2.1.x):
16255 - Fix use of freed memory when deciding to mark a non-addable
16256 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
16259 Changes in version 0.2.1.14-rc - 2009-04-12
16260 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
16261 series. It begins fixing some major performance problems, and also
16262 finally addresses the bug that was causing relays on dynamic IP
16263 addresses to fall out of the directory.
16266 - Clients replace entry guards that were chosen more than a few months
16267 ago. This change should significantly improve client performance,
16268 especially once more people upgrade, since relays that have been
16269 a guard for a long time are currently overloaded.
16271 o Major bugfixes (on 0.2.0):
16272 - Finally fix the bug where dynamic-IP relays disappear when their
16273 IP address changes: directory mirrors were mistakenly telling
16274 them their old address if they asked via begin_dir, so they
16275 never got an accurate answer about their new address, so they
16276 just vanished after a day. For belt-and-suspenders, relays that
16277 don't set Address in their config now avoid using begin_dir for
16278 all direct connections. Should fix bugs 827, 883, and 900.
16279 - Relays were falling out of the networkstatus consensus for
16280 part of a day if they changed their local config but the
16281 authorities discarded their new descriptor as "not sufficiently
16282 different". Now directory authorities accept a descriptor as changed
16283 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
16284 patch by Sebastian.
16285 - Avoid crashing in the presence of certain malformed descriptors.
16286 Found by lark, and by automated fuzzing.
16289 - When generating circuit events with verbose nicknames for
16290 controllers, try harder to look up nicknames for routers on a
16291 circuit. (Previously, we would look in the router descriptors we had
16292 for nicknames, but not in the consensus.) Partial fix for bug 941.
16293 - If the bridge config line doesn't specify a port, assume 443.
16294 This makes bridge lines a bit smaller and easier for users to
16296 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
16297 bytes (aka 20KB/s), to match our documentation. Also update
16298 directory authorities so they always assign the Fast flag to relays
16299 with 20KB/s of capacity. Now people running relays won't suddenly
16300 find themselves not seeing any use, if the network gets faster
16302 - Update to the "April 3 2009" ip-to-country file.
16305 - Avoid trying to print raw memory to the logs when we decide to
16306 give up on downloading a given relay descriptor. Bugfix on
16308 - In tor-resolve, when the Tor client to use is specified by
16309 <hostname>:<port>, actually use the specified port rather than
16310 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
16311 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
16312 - When starting with a cache over a few days old, do not leak
16313 memory for the obsolete router descriptors in it. Bugfix on
16315 - Avoid double-free on list of successfully uploaded hidden
16316 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
16317 - Change memarea_strndup() implementation to work even when
16318 duplicating a string at the end of a page. This bug was
16319 harmless for now, but could have meant crashes later. Fix by
16320 lark. Bugfix on 0.2.1.1-alpha.
16321 - Limit uploaded directory documents to be 16M rather than 500K.
16322 The directory authorities were refusing v3 consensus votes from
16323 other authorities, since the votes are now 504K. Fixes bug 959;
16324 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
16325 - Directory authorities should never send a 503 "busy" response to
16326 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
16330 Changes in version 0.2.1.13-alpha - 2009-03-09
16331 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
16332 cleanups. We're finally getting close to a release candidate.
16335 - Correctly update the list of which countries we exclude as
16336 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
16337 lark. Bugfix on 0.2.1.6-alpha.
16339 o Minor bugfixes (on 0.2.0.x and earlier):
16340 - Automatically detect MacOSX versions earlier than 10.4.0, and
16341 disable kqueue from inside Tor when running with these versions.
16342 We previously did this from the startup script, but that was no
16343 help to people who didn't use the startup script. Resolves bug 863.
16344 - When we had picked an exit node for a connection, but marked it as
16345 "optional", and it turned out we had no onion key for the exit,
16346 stop wanting that exit and try again. This situation may not
16347 be possible now, but will probably become feasible with proposal
16348 158. Spotted by rovv. Fixes another case of bug 752.
16349 - Clients no longer cache certificates for authorities they do not
16350 recognize. Bugfix on 0.2.0.9-alpha.
16351 - When we can't transmit a DNS request due to a network error, retry
16352 it after a while, and eventually transmit a failing response to
16353 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
16354 - If the controller claimed responsibility for a stream, but that
16355 stream never finished making its connection, it would live
16356 forever in circuit_wait state. Now we close it after SocksTimeout
16357 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
16358 - Drop begin cells to a hidden service if they come from the middle
16359 of a circuit. Patch from lark.
16360 - When we erroneously receive two EXTEND cells for the same circuit
16361 ID on the same connection, drop the second. Patch from lark.
16362 - Fix a crash that occurs on exit nodes when a nameserver request
16363 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
16364 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
16366 - Do not assume that a stack-allocated character array will be
16367 64-bit aligned on platforms that demand that uint64_t access is
16368 aligned. Possible fix for bug 604.
16369 - Parse dates and IPv4 addresses in a locale- and libc-independent
16370 manner, to avoid platform-dependent behavior on malformed input.
16371 - Build correctly when configured to build outside the main source
16372 path. Patch from Michael Gold.
16373 - We were already rejecting relay begin cells with destination port
16374 of 0. Now also reject extend cells with destination port or address
16375 of 0. Suggested by lark.
16377 o Minor bugfixes (on 0.2.1.x):
16378 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
16379 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
16380 - If we're an exit node, scrub the IP address to which we are exiting
16381 in the logs. Bugfix on 0.2.1.8-alpha.
16384 - On Linux, use the prctl call to re-enable core dumps when the user
16386 - New controller event NEWCONSENSUS that lists the networkstatus
16387 lines for every recommended relay. Now controllers like Torflow
16388 can keep up-to-date on which relays they should be using.
16389 - Update to the "February 26 2009" ip-to-country file.
16392 Changes in version 0.2.0.34 - 2009-02-08
16393 Tor 0.2.0.34 features several more security-related fixes. You should
16394 upgrade, especially if you run an exit relay (remote crash) or a
16395 directory authority (remote infinite loop), or you're on an older
16396 (pre-XP) or not-recently-patched Windows (remote exploit).
16398 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
16399 have many known flaws, and nobody should be using them. You should
16400 upgrade. If you're using a Linux or BSD and its packages are obsolete,
16401 stop using those packages and upgrade anyway.
16404 - Fix an infinite-loop bug on handling corrupt votes under certain
16405 circumstances. Bugfix on 0.2.0.8-alpha.
16406 - Fix a temporary DoS vulnerability that could be performed by
16407 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
16408 - Avoid a potential crash on exit nodes when processing malformed
16409 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
16410 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
16411 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
16414 - Fix compilation on systems where time_t is a 64-bit integer.
16415 Patch from Matthias Drochner.
16416 - Don't consider expiring already-closed client connections. Fixes
16417 bug 893. Bugfix on 0.0.2pre20.
16420 Changes in version 0.2.1.12-alpha - 2009-02-08
16421 Tor 0.2.1.12-alpha features several more security-related fixes. You
16422 should upgrade, especially if you run an exit relay (remote crash) or
16423 a directory authority (remote infinite loop), or you're on an older
16424 (pre-XP) or not-recently-patched Windows (remote exploit). It also
16425 includes a big pile of minor bugfixes and cleanups.
16428 - Fix an infinite-loop bug on handling corrupt votes under certain
16429 circumstances. Bugfix on 0.2.0.8-alpha.
16430 - Fix a temporary DoS vulnerability that could be performed by
16431 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
16432 - Avoid a potential crash on exit nodes when processing malformed
16433 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
16436 - Let controllers actually ask for the "clients_seen" event for
16437 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
16438 reported by Matt Edman.
16439 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
16441 - Fix a bug in address parsing that was preventing bridges or hidden
16442 service targets from being at IPv6 addresses.
16443 - Solve a bug that kept hardware crypto acceleration from getting
16444 enabled when accounting was turned on. Fixes bug 907. Bugfix on
16446 - Remove a bash-ism from configure.in to build properly on non-Linux
16447 platforms. Bugfix on 0.2.1.1-alpha.
16448 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
16449 headers. Bugfix on 0.2.0.10-alpha.
16450 - Don't consider expiring already-closed client connections. Fixes
16451 bug 893. Bugfix on 0.0.2pre20.
16452 - Fix another interesting corner-case of bug 891 spotted by rovv:
16453 Previously, if two hosts had different amounts of clock drift, and
16454 one of them created a new connection with just the wrong timing,
16455 the other might decide to deprecate the new connection erroneously.
16456 Bugfix on 0.1.1.13-alpha.
16457 - Resolve a very rare crash bug that could occur when the user forced
16458 a nameserver reconfiguration during the middle of a nameserver
16459 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
16460 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
16461 Bugfix on 0.2.1.7-alpha.
16462 - If we're using bridges and our network goes away, be more willing
16463 to forgive our bridges and try again when we get an application
16464 request. Bugfix on 0.2.0.x.
16467 - Support platforms where time_t is 64 bits long. (Congratulations,
16468 NetBSD!) Patch from Matthias Drochner.
16469 - Add a 'getinfo status/clients-seen' controller command, in case
16470 controllers want to hear clients_seen events but connect late.
16473 - Disable GCC's strict alias optimization by default, to avoid the
16474 likelihood of its introducing subtle bugs whenever our code violates
16475 the letter of C99's alias rules.
16478 Changes in version 0.2.0.33 - 2009-01-21
16479 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
16480 useful to users. It also finally fixes a bug where a relay or client
16481 that's been off for many days would take a long time to bootstrap.
16483 This update also fixes an important security-related bug reported by
16484 Ilja van Sprundel. You should upgrade. (We'll send out more details
16485 about the bug once people have had some time to upgrade.)
16488 - Fix a heap-corruption bug that may be remotely triggerable on
16489 some platforms. Reported by Ilja van Sprundel.
16492 - When a stream at an exit relay is in state "resolving" or
16493 "connecting" and it receives an "end" relay cell, the exit relay
16494 would silently ignore the end cell and not close the stream. If
16495 the client never closes the circuit, then the exit relay never
16496 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
16497 reported by "wood".
16498 - When sending CREATED cells back for a given circuit, use a 64-bit
16499 connection ID to find the right connection, rather than an addr:port
16500 combination. Now that we can have multiple OR connections between
16501 the same ORs, it is no longer possible to use addr:port to uniquely
16502 identify a connection.
16503 - Bridge relays that had DirPort set to 0 would stop fetching
16504 descriptors shortly after startup, and then briefly resume
16505 after a new bandwidth test and/or after publishing a new bridge
16506 descriptor. Bridge users that try to bootstrap from them would
16507 get a recent networkstatus but would get descriptors from up to
16508 18 hours earlier, meaning most of the descriptors were obsolete
16509 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
16510 - Prevent bridge relays from serving their 'extrainfo' document
16511 to anybody who asks, now that extrainfo docs include potentially
16512 sensitive aggregated client geoip summaries. Bugfix on
16514 - If the cached networkstatus consensus is more than five days old,
16515 discard it rather than trying to use it. In theory it could be
16516 useful because it lists alternate directory mirrors, but in practice
16517 it just means we spend many minutes trying directory mirrors that
16518 are long gone from the network. Also discard router descriptors as
16519 we load them if they are more than five days old, since the onion
16520 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
16523 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
16524 could make gcc generate non-functional binary search code. Bugfix
16526 - Build correctly on platforms without socklen_t.
16527 - Compile without warnings on solaris.
16528 - Avoid potential crash on internal error during signature collection.
16529 Fixes bug 864. Patch from rovv.
16530 - Correct handling of possible malformed authority signing key
16531 certificates with internal signature types. Fixes bug 880.
16532 Bugfix on 0.2.0.3-alpha.
16533 - Fix a hard-to-trigger resource leak when logging credential status.
16535 - When we can't initialize DNS because the network is down, do not
16536 automatically stop Tor from starting. Instead, we retry failed
16537 dns_init() every 10 minutes, and change the exit policy to reject
16538 *:* until one succeeds. Fixes bug 691.
16539 - Use 64 bits instead of 32 bits for connection identifiers used with
16540 the controller protocol, to greatly reduce risk of identifier reuse.
16541 - When we're choosing an exit node for a circuit, and we have
16542 no pending streams, choose a good general exit rather than one that
16543 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
16544 - Fix another case of assuming, when a specific exit is requested,
16545 that we know more than the user about what hosts it allows.
16546 Fixes one case of bug 752. Patch from rovv.
16547 - Clip the MaxCircuitDirtiness config option to a minimum of 10
16548 seconds. Warn the user if lower values are given in the
16549 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
16550 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
16551 user if lower values are given in the configuration. Bugfix on
16552 0.1.1.17-rc. Patch by Sebastian.
16553 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
16554 the cache because we already had a v0 descriptor with the same ID.
16555 Bugfix on 0.2.0.18-alpha.
16556 - Fix a race condition when freeing keys shared between main thread
16557 and CPU workers that could result in a memory leak. Bugfix on
16558 0.1.0.1-rc. Fixes bug 889.
16559 - Send a valid END cell back when a client tries to connect to a
16560 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
16561 840. Patch from rovv.
16562 - Check which hops rendezvous stream cells are associated with to
16563 prevent possible guess-the-streamid injection attacks from
16564 intermediate hops. Fixes another case of bug 446. Based on patch
16566 - If a broken client asks a non-exit router to connect somewhere,
16567 do not even do the DNS lookup before rejecting the connection.
16568 Fixes another case of bug 619. Patch from rovv.
16569 - When a relay gets a create cell it can't decrypt (e.g. because it's
16570 using the wrong onion key), we were dropping it and letting the
16571 client time out. Now actually answer with a destroy cell. Fixes
16572 bug 904. Bugfix on 0.0.2pre8.
16574 o Minor bugfixes (hidden services):
16575 - Do not throw away existing introduction points on SIGHUP. Bugfix on
16576 0.0.6pre1. Patch by Karsten. Fixes bug 874.
16579 - Report the case where all signatures in a detached set are rejected
16580 differently than the case where there is an error handling the
16582 - When we realize that another process has modified our cached
16583 descriptors, print out a more useful error message rather than
16584 triggering an assertion. Fixes bug 885. Patch from Karsten.
16585 - Implement the 0x20 hack to better resist DNS poisoning: set the
16586 case on outgoing DNS requests randomly, and reject responses that do
16587 not match the case correctly. This logic can be disabled with the
16588 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
16589 of servers that do not reliably preserve case in replies. See
16590 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
16592 - Check DNS replies for more matching fields to better resist DNS
16594 - Never use OpenSSL compression: it wastes RAM and CPU trying to
16595 compress cells, which are basically all encrypted, compressed, or
16599 Changes in version 0.2.1.11-alpha - 2009-01-20
16600 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
16601 week it will take a long time to bootstrap again" bug. It also fixes
16602 an important security-related bug reported by Ilja van Sprundel. You
16603 should upgrade. (We'll send out more details about the bug once people
16604 have had some time to upgrade.)
16607 - Fix a heap-corruption bug that may be remotely triggerable on
16608 some platforms. Reported by Ilja van Sprundel.
16611 - Discard router descriptors as we load them if they are more than
16612 five days old. Otherwise if Tor is off for a long time and then
16613 starts with cached descriptors, it will try to use the onion
16614 keys in those obsolete descriptors when building circuits. Bugfix
16615 on 0.2.0.x. Fixes bug 887.
16618 - Try to make sure that the version of Libevent we're running with
16619 is binary-compatible with the one we built with. May address bug
16621 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
16622 for bug 905. Bugfix on 0.2.1.7-alpha.
16623 - Add a new --enable-local-appdata configuration switch to change
16624 the default location of the datadir on win32 from APPDATA to
16625 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
16626 entirely. Patch from coderman.
16629 - Make outbound DNS packets respect the OutboundBindAddress setting.
16630 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
16631 - When our circuit fails at the first hop (e.g. we get a destroy
16632 cell back), avoid using that OR connection anymore, and also
16633 tell all the one-hop directory requests waiting for it that they
16634 should fail. Bugfix on 0.2.1.3-alpha.
16635 - In the torify(1) manpage, mention that tsocks will leak your
16639 Changes in version 0.2.1.10-alpha - 2009-01-06
16640 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
16641 would make the bridge relay not so useful if it had DirPort set to 0,
16642 and one that could let an attacker learn a little bit of information
16643 about the bridge's users), and a bug that would cause your Tor relay
16644 to ignore a circuit create request it can't decrypt (rather than reply
16645 with an error). It also fixes a wide variety of other bugs.
16648 - If the cached networkstatus consensus is more than five days old,
16649 discard it rather than trying to use it. In theory it could
16650 be useful because it lists alternate directory mirrors, but in
16651 practice it just means we spend many minutes trying directory
16652 mirrors that are long gone from the network. Helps bug 887 a bit;
16654 - Bridge relays that had DirPort set to 0 would stop fetching
16655 descriptors shortly after startup, and then briefly resume
16656 after a new bandwidth test and/or after publishing a new bridge
16657 descriptor. Bridge users that try to bootstrap from them would
16658 get a recent networkstatus but would get descriptors from up to
16659 18 hours earlier, meaning most of the descriptors were obsolete
16660 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
16661 - Prevent bridge relays from serving their 'extrainfo' document
16662 to anybody who asks, now that extrainfo docs include potentially
16663 sensitive aggregated client geoip summaries. Bugfix on
16667 - New controller event "clients_seen" to report a geoip-based summary
16668 of which countries we've seen clients from recently. Now controllers
16669 like Vidalia can show bridge operators that they're actually making
16671 - Build correctly against versions of OpenSSL 0.9.8 or later built
16672 without support for deprecated functions.
16673 - Update to the "December 19 2008" ip-to-country file.
16675 o Minor bugfixes (on 0.2.0.x):
16676 - Authorities now vote for the Stable flag for any router whose
16677 weighted MTBF is at least 5 days, regardless of the mean MTBF.
16678 - Do not remove routers as too old if we do not have any consensus
16679 document. Bugfix on 0.2.0.7-alpha.
16680 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
16681 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
16682 - When an exit relay resolves a stream address to a local IP address,
16683 do not just keep retrying that same exit relay over and
16684 over. Instead, just close the stream. Addresses bug 872. Bugfix
16685 on 0.2.0.32. Patch from rovv.
16686 - If a hidden service sends us an END cell, do not consider
16687 retrying the connection; just close it. Patch from rovv.
16688 - When we made bridge authorities stop serving bridge descriptors over
16689 unencrypted links, we also broke DirPort reachability testing for
16690 bridges. So bridges with a non-zero DirPort were printing spurious
16691 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
16692 - When a relay gets a create cell it can't decrypt (e.g. because it's
16693 using the wrong onion key), we were dropping it and letting the
16694 client time out. Now actually answer with a destroy cell. Fixes
16695 bug 904. Bugfix on 0.0.2pre8.
16696 - Squeeze 2-5% out of client performance (according to oprofile) by
16697 improving the implementation of some policy-manipulation functions.
16699 o Minor bugfixes (on 0.2.1.x):
16700 - Make get_interface_address() function work properly again; stop
16701 guessing the wrong parts of our address as our address.
16702 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
16703 send on that circuit. Otherwise we might violate the proposal-110
16704 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
16706 - When we're sending non-EXTEND cells to the first hop in a circuit,
16707 for example to use an encrypted directory connection, we don't need
16708 to use RELAY_EARLY cells: the first hop knows what kind of cell
16709 it is, and nobody else can even see the cell type. Conserving
16710 RELAY_EARLY cells makes it easier to cannibalize circuits like
16712 - Stop logging nameserver addresses in reverse order.
16713 - If we are retrying a directory download slowly over and over, do
16714 not automatically give up after the 254th failure. Bugfix on
16716 - Resume reporting accurate "stream end" reasons to the local control
16717 port. They were lost in the changes for Proposal 148. Bugfix on
16720 o Deprecated and removed features:
16721 - The old "tor --version --version" command, which would print out
16722 the subversion "Id" of most of the source files, is now removed. It
16723 turned out to be less useful than we'd expected, and harder to
16726 o Code simplifications and refactoring:
16727 - Change our header file guard macros to be less likely to conflict
16728 with system headers. Adam Langley noticed that we were conflicting
16729 with log.h on Android.
16730 - Tool-assisted documentation cleanup. Nearly every function or
16731 static variable in Tor should have its own documentation now.
16734 Changes in version 0.2.1.9-alpha - 2008-12-25
16735 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
16737 o New directory authorities:
16738 - gabelmoo (the authority run by Karsten Loesing) now has a new
16742 - Never use a connection with a mismatched address to extend a
16743 circuit, unless that connection is canonical. A canonical
16744 connection is one whose address is authenticated by the router's
16745 identity key, either in a NETINFO cell or in a router descriptor.
16746 - Avoid a possible memory corruption bug when receiving hidden service
16747 descriptors. Bugfix on 0.2.1.6-alpha.
16750 - Fix a logic error that would automatically reject all but the first
16751 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
16752 part of bug 813/868. Bug spotted by coderman.
16753 - When a stream at an exit relay is in state "resolving" or
16754 "connecting" and it receives an "end" relay cell, the exit relay
16755 would silently ignore the end cell and not close the stream. If
16756 the client never closes the circuit, then the exit relay never
16757 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
16758 reported by "wood".
16759 - When we can't initialize DNS because the network is down, do not
16760 automatically stop Tor from starting. Instead, retry failed
16761 dns_init() every 10 minutes, and change the exit policy to reject
16762 *:* until one succeeds. Fixes bug 691.
16765 - Give a better error message when an overzealous init script says
16766 "sudo -u username tor --user username". Makes Bug 882 easier for
16768 - When a directory authority gives us a new guess for our IP address,
16769 log which authority we used. Hopefully this will help us debug
16770 the recent complaints about bad IP address guesses.
16771 - Detect svn revision properly when we're using git-svn.
16772 - Try not to open more than one descriptor-downloading connection
16773 to an authority at once. This should reduce load on directory
16774 authorities. Fixes bug 366.
16775 - Add cross-certification to newly generated certificates, so that
16776 a signing key is enough information to look up a certificate.
16777 Partial implementation of proposal 157.
16778 - Start serving certificates by <identity digest, signing key digest>
16779 pairs. Partial implementation of proposal 157.
16780 - Clients now never report any stream end reason except 'MISC'.
16781 Implements proposal 148.
16782 - On platforms with a maximum syslog string length, truncate syslog
16783 messages to that length ourselves, rather than relying on the
16784 system to do it for us.
16785 - Optimize out calls to time(NULL) that occur for every IO operation,
16786 or for every cell. On systems where time() is a slow syscall,
16787 this fix will be slightly helpful.
16788 - Exit servers can now answer resolve requests for ip6.arpa addresses.
16789 - When we download a descriptor that we then immediately (as
16790 a directory authority) reject, do not retry downloading it right
16791 away. Should save some bandwidth on authorities. Fix for bug
16792 888. Patch by Sebastian Hahn.
16793 - When a download gets us zero good descriptors, do not notify
16794 Tor that new directory information has arrived.
16795 - Avoid some nasty corner cases in the logic for marking connections
16796 as too old or obsolete or noncanonical for circuits. Partial
16799 o Minor features (controller):
16800 - New CONSENSUS_ARRIVED event to note when a new consensus has
16801 been fetched and validated.
16802 - When we realize that another process has modified our cached
16803 descriptors file, print out a more useful error message rather
16804 than triggering an assertion. Fixes bug 885. Patch from Karsten.
16805 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
16806 controllers to prevent SIGHUP from reloading the
16807 configuration. Fixes bug 856.
16810 - Resume using the correct "REASON=" stream when telling the
16811 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
16812 - When a canonical connection appears later in our internal list
16813 than a noncanonical one for a given OR ID, always use the
16814 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
16816 - Clip the MaxCircuitDirtiness config option to a minimum of 10
16817 seconds. Warn the user if lower values are given in the
16818 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
16819 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
16820 user if lower values are given in the configuration. Bugfix on
16821 0.1.1.17-rc. Patch by Sebastian.
16822 - Fix a race condition when freeing keys shared between main thread
16823 and CPU workers that could result in a memory leak. Bugfix on
16824 0.1.0.1-rc. Fixes bug 889.
16826 o Minor bugfixes (hidden services):
16827 - Do not throw away existing introduction points on SIGHUP (bugfix on
16828 0.0.6pre1); also, do not stall hidden services because we're
16829 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
16830 by John Brooks. Patch by Karsten. Fixes bug 874.
16831 - Fix a memory leak when we decline to add a v2 rendezvous
16832 descriptor to the cache because we already had a v0 descriptor
16833 with the same ID. Bugfix on 0.2.0.18-alpha.
16835 o Deprecated and removed features:
16836 - RedirectExits has been removed. It was deprecated since
16838 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
16839 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
16840 - Cell pools are now always enabled; --disable-cell-pools is ignored.
16842 o Code simplifications and refactoring:
16843 - Rename the confusing or_is_obsolete field to the more appropriate
16844 is_bad_for_new_circs, and move it to or_connection_t where it
16846 - Move edge-only flags from connection_t to edge_connection_t: not
16847 only is this better coding, but on machines of plausible alignment,
16848 it should save 4-8 bytes per connection_t. "Every little bit helps."
16849 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
16850 for consistency; keep old option working for backward compatibility.
16851 - Simplify the code for finding connections to use for a circuit.
16854 Changes in version 0.2.1.8-alpha - 2008-12-08
16855 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
16856 builds better on unusual platforms like Solaris and old OS X, and
16857 fixes a variety of other issues.
16860 - New DirPortFrontPage option that takes an html file and publishes
16861 it as "/" on the DirPort. Now relay operators can provide a
16862 disclaimer without needing to set up a separate webserver. There's
16863 a sample disclaimer in contrib/tor-exit-notice.html.
16866 - When the client is choosing entry guards, now it selects at most
16867 one guard from a given relay family. Otherwise we could end up with
16868 all of our entry points into the network run by the same operator.
16869 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
16872 - Fix a DOS opportunity during the voting signature collection process
16873 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
16874 - Fix a possible segfault when establishing an exit connection. Bugfix
16878 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
16880 - Made Tor a little less aggressive about deleting expired
16881 certificates. Partial fix for bug 854.
16882 - Stop doing unaligned memory access that generated bus errors on
16883 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
16884 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
16885 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
16886 - Make USR2 log-level switch take effect immediately. Bugfix on
16888 - If one win32 nameserver fails to get added, continue adding the
16889 rest, and don't automatically fail.
16890 - Use fcntl() for locking when flock() is not available. Should fix
16891 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
16892 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
16893 could make gcc generate non-functional binary search code. Bugfix
16895 - Build correctly on platforms without socklen_t.
16896 - Avoid potential crash on internal error during signature collection.
16897 Fixes bug 864. Patch from rovv.
16898 - Do not use C's stdio library for writing to log files. This will
16899 improve logging performance by a minute amount, and will stop
16900 leaking fds when our disk is full. Fixes bug 861.
16901 - Stop erroneous use of O_APPEND in cases where we did not in fact
16902 want to re-seek to the end of a file before every last write().
16903 - Correct handling of possible malformed authority signing key
16904 certificates with internal signature types. Fixes bug 880. Bugfix
16906 - Fix a hard-to-trigger resource leak when logging credential status.
16910 - Directory mirrors no longer fetch the v1 directory or
16911 running-routers files. They are obsolete, and nobody asks for them
16912 anymore. This is the first step to making v1 authorities obsolete.
16914 o Minor features (controller):
16915 - Return circuit purposes in response to GETINFO circuit-status. Fixes
16919 Changes in version 0.2.0.32 - 2008-11-20
16920 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
16921 packages (and maybe other packages) noticed by Theo de Raadt, fixes
16922 a smaller security flaw that might allow an attacker to access local
16923 services, further improves hidden service performance, and fixes a
16924 variety of other issues.
16927 - The "User" and "Group" config options did not clear the
16928 supplementary group entries for the Tor process. The "User" option
16929 is now more robust, and we now set the groups to the specified
16930 user's primary group. The "Group" option is now ignored. For more
16931 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
16932 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
16933 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
16934 - The "ClientDNSRejectInternalAddresses" config option wasn't being
16935 consistently obeyed: if an exit relay refuses a stream because its
16936 exit policy doesn't allow it, we would remember what IP address
16937 the relay said the destination address resolves to, even if it's
16938 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
16941 - Fix a DOS opportunity during the voting signature collection process
16942 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
16944 o Major bugfixes (hidden services):
16945 - When fetching v0 and v2 rendezvous service descriptors in parallel,
16946 we were failing the whole hidden service request when the v0
16947 descriptor fetch fails, even if the v2 fetch is still pending and
16948 might succeed. Similarly, if the last v2 fetch fails, we were
16949 failing the whole hidden service request even if a v0 fetch is
16950 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
16951 - When extending a circuit to a hidden service directory to upload a
16952 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
16953 requests failed, because the router descriptor has not been
16954 downloaded yet. In these cases, do not attempt to upload the
16955 rendezvous descriptor, but wait until the router descriptor is
16956 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
16957 descriptor from a hidden service directory for which the router
16958 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
16962 - Fix several infrequent memory leaks spotted by Coverity.
16963 - When testing for libevent functions, set the LDFLAGS variable
16964 correctly. Found by Riastradh.
16965 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
16966 bootstrapping with tunneled directory connections. Bugfix on
16967 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
16968 - When asked to connect to A.B.exit:80, if we don't know the IP for A
16969 and we know that server B rejects most-but-not all connections to
16970 port 80, we would previously reject the connection. Now, we assume
16971 the user knows what they were asking for. Fixes bug 752. Bugfix
16972 on 0.0.9rc5. Diagnosed by BarkerJr.
16973 - If we overrun our per-second write limits a little, count this as
16974 having used up our write allocation for the second, and choke
16975 outgoing directory writes. Previously, we had only counted this when
16976 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
16977 Bugfix on 0.2.0.x (??).
16978 - Remove the old v2 directory authority 'lefkada' from the default
16979 list. It has been gone for many months.
16980 - Stop doing unaligned memory access that generated bus errors on
16981 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
16982 - Make USR2 log-level switch take effect immediately. Bugfix on
16985 o Minor bugfixes (controller):
16986 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
16987 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
16990 Changes in version 0.2.1.7-alpha - 2008-11-08
16991 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
16992 packages (and maybe other packages) noticed by Theo de Raadt, fixes
16993 a smaller security flaw that might allow an attacker to access local
16994 services, adds better defense against DNS poisoning attacks on exit
16995 relays, further improves hidden service performance, and fixes a
16996 variety of other issues.
16999 - The "ClientDNSRejectInternalAddresses" config option wasn't being
17000 consistently obeyed: if an exit relay refuses a stream because its
17001 exit policy doesn't allow it, we would remember what IP address
17002 the relay said the destination address resolves to, even if it's
17003 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
17004 - The "User" and "Group" config options did not clear the
17005 supplementary group entries for the Tor process. The "User" option
17006 is now more robust, and we now set the groups to the specified
17007 user's primary group. The "Group" option is now ignored. For more
17008 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
17009 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
17010 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
17011 - Do not use or believe expired v3 authority certificates. Patch
17012 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
17015 - Now NodeFamily and MyFamily config options allow spaces in
17016 identity fingerprints, so it's easier to paste them in.
17017 Suggested by Lucky Green.
17018 - Implement the 0x20 hack to better resist DNS poisoning: set the
17019 case on outgoing DNS requests randomly, and reject responses that do
17020 not match the case correctly. This logic can be disabled with the
17021 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
17022 of servers that do not reliably preserve case in replies. See
17023 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
17025 - Preserve case in replies to DNSPort requests in order to support
17026 the 0x20 hack for resisting DNS poisoning attacks.
17028 o Hidden service performance improvements:
17029 - When the client launches an introduction circuit, retry with a
17030 new circuit after 30 seconds rather than 60 seconds.
17031 - Launch a second client-side introduction circuit in parallel
17032 after a delay of 15 seconds (based on work by Christian Wilms).
17033 - Hidden services start out building five intro circuits rather
17034 than three, and when the first three finish they publish a service
17035 descriptor using those. Now we publish our service descriptor much
17036 faster after restart.
17039 - Minor fix in the warning messages when you're having problems
17040 bootstrapping; also, be more forgiving of bootstrap problems when
17041 we're still making incremental progress on a given bootstrap phase.
17042 - When we're choosing an exit node for a circuit, and we have
17043 no pending streams, choose a good general exit rather than one that
17044 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
17045 - Send a valid END cell back when a client tries to connect to a
17046 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
17047 840. Patch from rovv.
17048 - If a broken client asks a non-exit router to connect somewhere,
17049 do not even do the DNS lookup before rejecting the connection.
17050 Fixes another case of bug 619. Patch from rovv.
17051 - Fix another case of assuming, when a specific exit is requested,
17052 that we know more than the user about what hosts it allows.
17053 Fixes another case of bug 752. Patch from rovv.
17054 - Check which hops rendezvous stream cells are associated with to
17055 prevent possible guess-the-streamid injection attacks from
17056 intermediate hops. Fixes another case of bug 446. Based on patch
17058 - Avoid using a negative right-shift when comparing 32-bit
17059 addresses. Possible fix for bug 845 and bug 811.
17060 - Make the assert_circuit_ok() function work correctly on circuits that
17061 have already been marked for close.
17062 - Fix read-off-the-end-of-string error in unit tests when decoding
17063 introduction points.
17064 - Fix uninitialized size field for memory area allocation: may improve
17065 memory performance during directory parsing.
17066 - Treat duplicate certificate fetches as failures, so that we do
17067 not try to re-fetch an expired certificate over and over and over.
17068 - Do not say we're fetching a certificate when we'll in fact skip it
17069 because of a pending download.
17072 Changes in version 0.2.1.6-alpha - 2008-09-30
17073 Tor 0.2.1.6-alpha further improves performance and robustness of
17074 hidden services, starts work on supporting per-country relay selection,
17075 and fixes a variety of smaller issues.
17078 - Implement proposal 121: make it possible to build hidden services
17079 that only certain clients are allowed to connect to. This is
17080 enforced at several points, so that unauthorized clients are unable
17081 to send INTRODUCE cells to the service, or even (depending on the
17082 type of authentication) to learn introduction points. This feature
17083 raises the bar for certain kinds of active attacks against hidden
17084 services. Code by Karsten Loesing.
17085 - Relays now store and serve v2 hidden service descriptors by default,
17086 i.e., the new default value for HidServDirectoryV2 is 1. This is
17087 the last step in proposal 114, which aims to make hidden service
17088 lookups more reliable.
17089 - Start work to allow node restrictions to include country codes. The
17090 syntax to exclude nodes in a country with country code XX is
17091 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
17092 refinement to decide what config options should take priority if
17093 you ask to both use a particular node and exclude it.
17094 - Allow ExitNodes list to include IP ranges and country codes, just
17095 like the Exclude*Nodes lists. Patch from Robert Hogan.
17098 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
17099 Tor to fail to start if you had it configured to use a bridge
17100 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
17101 - When extending a circuit to a hidden service directory to upload a
17102 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
17103 requests failed, because the router descriptor had not been
17104 downloaded yet. In these cases, we now wait until the router
17105 descriptor is downloaded, and then retry. Likewise, clients
17106 now skip over a hidden service directory if they don't yet have
17107 its router descriptor, rather than futilely requesting it and
17108 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
17110 - When fetching v0 and v2 rendezvous service descriptors in parallel,
17111 we were failing the whole hidden service request when the v0
17112 descriptor fetch fails, even if the v2 fetch is still pending and
17113 might succeed. Similarly, if the last v2 fetch fails, we were
17114 failing the whole hidden service request even if a v0 fetch is
17115 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
17116 - DNS replies need to have names matching their requests, but
17117 these names should be in the questions section, not necessarily
17118 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
17121 - Update to the "September 1 2008" ip-to-country file.
17122 - Allow ports 465 and 587 in the default exit policy again. We had
17123 rejected them in 0.1.0.15, because back in 2005 they were commonly
17124 misconfigured and ended up as spam targets. We hear they are better
17125 locked down these days.
17126 - Use a lockfile to make sure that two Tor processes are not
17127 simultaneously running with the same datadir.
17128 - Serve the latest v3 networkstatus consensus via the control
17129 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
17130 - Better logging about stability/reliability calculations on directory
17132 - Drop the requirement to have an open dir port for storing and
17133 serving v2 hidden service descriptors.
17134 - Directory authorities now serve a /tor/dbg-stability.txt URL to
17135 help debug WFU and MTBF calculations.
17136 - Implement most of Proposal 152: allow specialized servers to permit
17137 single-hop circuits, and clients to use those servers to build
17138 single-hop circuits when using a specialized controller. Patch
17139 from Josh Albrecht. Resolves feature request 768.
17140 - Add a -p option to tor-resolve for specifying the SOCKS port: some
17141 people find host:port too confusing.
17142 - Make TrackHostExit mappings expire a while after their last use, not
17143 after their creation. Patch from Robert Hogan.
17144 - Provide circuit purposes along with circuit events to the controller.
17147 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
17149 - Fixed some memory leaks -- some quite frequent, some almost
17150 impossible to trigger -- based on results from Coverity.
17151 - When testing for libevent functions, set the LDFLAGS variable
17152 correctly. Found by Riastradh.
17153 - Fix an assertion bug in parsing policy-related options; possible fix
17155 - Catch and report a few more bootstrapping failure cases when Tor
17156 fails to establish a TCP connection. Cleanup on 0.2.1.x.
17157 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
17158 bootstrapping with tunneled directory connections. Bugfix on
17159 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
17160 - When asked to connect to A.B.exit:80, if we don't know the IP for A
17161 and we know that server B rejects most-but-not all connections to
17162 port 80, we would previously reject the connection. Now, we assume
17163 the user knows what they were asking for. Fixes bug 752. Bugfix
17164 on 0.0.9rc5. Diagnosed by BarkerJr.
17165 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
17166 service directories if they have no advertised dir port. Bugfix
17168 - If we overrun our per-second write limits a little, count this as
17169 having used up our write allocation for the second, and choke
17170 outgoing directory writes. Previously, we had only counted this when
17171 we had met our limits precisely. Fixes bug 824. Patch by rovv.
17172 Bugfix on 0.2.0.x (??).
17173 - Avoid a "0 divided by 0" calculation when calculating router uptime
17174 at directory authorities. Bugfix on 0.2.0.8-alpha.
17175 - Make DNS resolved controller events into "CLOSED", not
17176 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
17178 - Fix a bug where an unreachable relay would establish enough
17179 reachability testing circuits to do a bandwidth test -- if
17180 we already have a connection to the middle hop of the testing
17181 circuit, then it could establish the last hop by using the existing
17182 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
17183 circuits no longer use entry guards in 0.2.1.3-alpha.
17184 - If we have correct permissions on $datadir, we complain to stdout
17185 and fail to start. But dangerous permissions on
17186 $datadir/cached-status/ would cause us to open a log and complain
17187 there. Now complain to stdout and fail to start in both cases. Fixes
17188 bug 820, reported by seeess.
17189 - Remove the old v2 directory authority 'lefkada' from the default
17190 list. It has been gone for many months.
17192 o Code simplifications and refactoring:
17193 - Revise the connection_new functions so that a more typesafe variant
17194 exists. This will work better with Coverity, and let us find any
17195 actual mistakes we're making here.
17196 - Refactor unit testing logic so that dmalloc can be used sensibly
17197 with unit tests to check for memory leaks.
17198 - Move all hidden-service related fields from connection and circuit
17199 structure to substructures: this way they won't eat so much memory.
17202 Changes in version 0.2.0.31 - 2008-09-03
17203 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
17204 a big bug we're seeing where in rare cases traffic from one Tor stream
17205 gets mixed into another stream, and fixes a variety of smaller issues.
17208 - Make sure that two circuits can never exist on the same connection
17209 with the same circuit ID, even if one is marked for close. This
17210 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
17211 - Relays now reject risky extend cells: if the extend cell includes
17212 a digest of all zeroes, or asks to extend back to the relay that
17213 sent the extend cell, tear down the circuit. Ideas suggested
17215 - If not enough of our entry guards are available so we add a new
17216 one, we might use the new one even if it overlapped with the
17217 current circuit's exit relay (or its family). Anonymity bugfix
17218 pointed out by rovv.
17221 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
17222 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
17223 - Correctly detect the presence of the linux/netfilter_ipv4.h header
17224 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
17225 - Pick size of default geoip filename string correctly on windows.
17226 Fixes bug 806. Bugfix on 0.2.0.30.
17227 - Make the autoconf script accept the obsolete --with-ssl-dir
17228 option as an alias for the actually-working --with-openssl-dir
17229 option. Fix the help documentation to recommend --with-openssl-dir.
17230 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
17231 - When using the TransPort option on OpenBSD, and using the User
17232 option to change UID and drop privileges, make sure to open
17233 /dev/pf before dropping privileges. Fixes bug 782. Patch from
17234 Christopher Davis. Bugfix on 0.1.2.1-alpha.
17235 - Try to attach connections immediately upon receiving a RENDEZVOUS2
17236 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
17237 on the client side when connecting to a hidden service. Bugfix
17238 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
17239 - When closing an application-side connection because its circuit is
17240 getting torn down, generate the stream event correctly. Bugfix on
17241 0.1.2.x. Anonymous patch.
17244 Changes in version 0.2.1.5-alpha - 2008-08-31
17245 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
17246 in a lot of the infrastructure for adding authorization to hidden
17247 services, lays the groundwork for having clients read their load
17248 balancing information out of the networkstatus consensus rather than
17249 the individual router descriptors, addresses two potential anonymity
17250 issues, and fixes a variety of smaller issues.
17253 - Convert many internal address representations to optionally hold
17255 - Generate and accept IPv6 addresses in many protocol elements.
17256 - Make resolver code handle nameservers located at ipv6 addresses.
17257 - Begin implementation of proposal 121 ("Client authorization for
17258 hidden services"): configure hidden services with client
17259 authorization, publish descriptors for them, and configure
17260 authorization data for hidden services at clients. The next
17261 step is to actually access hidden services that perform client
17263 - More progress toward proposal 141: Network status consensus
17264 documents and votes now contain bandwidth information for each
17265 router and a summary of that router's exit policy. Eventually this
17266 will be used by clients so that they do not have to download every
17267 known descriptor before building circuits.
17269 o Major bugfixes (on 0.2.0.x and before):
17270 - When sending CREATED cells back for a given circuit, use a 64-bit
17271 connection ID to find the right connection, rather than an addr:port
17272 combination. Now that we can have multiple OR connections between
17273 the same ORs, it is no longer possible to use addr:port to uniquely
17274 identify a connection.
17275 - Relays now reject risky extend cells: if the extend cell includes
17276 a digest of all zeroes, or asks to extend back to the relay that
17277 sent the extend cell, tear down the circuit. Ideas suggested
17279 - If not enough of our entry guards are available so we add a new
17280 one, we might use the new one even if it overlapped with the
17281 current circuit's exit relay (or its family). Anonymity bugfix
17282 pointed out by rovv.
17285 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
17286 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
17287 - When using the TransPort option on OpenBSD, and using the User
17288 option to change UID and drop privileges, make sure to open /dev/pf
17289 before dropping privileges. Fixes bug 782. Patch from Christopher
17290 Davis. Bugfix on 0.1.2.1-alpha.
17291 - Correctly detect the presence of the linux/netfilter_ipv4.h header
17292 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
17293 - Add a missing safe_str() call for a debug log message.
17294 - Use 64 bits instead of 32 bits for connection identifiers used with
17295 the controller protocol, to greatly reduce risk of identifier reuse.
17296 - Make the autoconf script accept the obsolete --with-ssl-dir
17297 option as an alias for the actually-working --with-openssl-dir
17298 option. Fix the help documentation to recommend --with-openssl-dir.
17299 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
17302 - Rate-limit too-many-sockets messages: when they happen, they happen
17303 a lot. Resolves bug 748.
17304 - Resist DNS poisoning a little better by making sure that names in
17305 answer sections match.
17306 - Print the SOCKS5 error message string as well as the error code
17307 when a tor-resolve request fails. Patch from Jacob.
17310 Changes in version 0.2.1.4-alpha - 2008-08-04
17311 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
17314 - The address part of exit policies was not correctly written
17315 to router descriptors. This generated router descriptors that failed
17316 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
17318 - Tor triggered a false assert when extending a circuit to a relay
17319 but we already have a connection open to that relay. Noticed by
17320 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
17323 - Fix a hidden service logging bug: in some edge cases, the router
17324 descriptor of a previously picked introduction point becomes
17325 obsolete and we need to give up on it rather than continually
17326 complaining that it has become obsolete. Observed by xiando. Bugfix
17329 o Removed features:
17330 - Take out the TestVia config option, since it was a workaround for
17331 a bug that was fixed in Tor 0.1.1.21.
17334 Changes in version 0.2.1.3-alpha - 2008-08-03
17335 Tor 0.2.1.3-alpha implements most of the pieces to prevent
17336 infinite-length circuit attacks (see proposal 110); fixes a bug that
17337 might cause exit relays to corrupt streams they send back; allows
17338 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
17339 ExcludeExitNodes config options; and fixes a big pile of bugs.
17341 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
17342 - Send a bootstrap problem "warn" event on the first problem if the
17343 reason is NO_ROUTE (that is, our network is down).
17346 - Implement most of proposal 110: The first K cells to be sent
17347 along a circuit are marked as special "early" cells; only K "early"
17348 cells will be allowed. Once this code is universal, we can block
17349 certain kinds of DOS attack by requiring that EXTEND commands must
17350 be sent using an "early" cell.
17353 - Try to attach connections immediately upon receiving a RENDEZVOUS2
17354 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
17355 on the client side when connecting to a hidden service. Bugfix
17356 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
17357 - Ensure that two circuits can never exist on the same connection
17358 with the same circuit ID, even if one is marked for close. This
17359 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
17362 - When relays do their initial bandwidth measurement, don't limit
17363 to just our entry guards for the test circuits. Otherwise we tend
17364 to have multiple test circuits going through a single entry guard,
17365 which makes our bandwidth test less accurate. Fixes part of bug 654;
17366 patch contributed by Josh Albrecht.
17367 - Add an ExcludeExitNodes option so users can list a set of nodes
17368 that should be be excluded from the exit node position, but
17369 allowed elsewhere. Implements proposal 151.
17370 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
17371 ExcludeNodes and ExcludeExitNodes lists.
17372 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
17373 be more efficient. Formerly it was quadratic in the number of
17374 servers; now it should be linear. Fixes bug 509.
17375 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
17376 and n_conn_id_digest fields into a separate structure that's
17377 only needed when the circuit has not yet attached to an n_conn.
17380 - Change the contrib/tor.logrotate script so it makes the new
17381 logs as "_tor:_tor" rather than the default, which is generally
17382 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
17383 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
17384 warnings (occasionally), but it can also cause the compiler to
17385 eliminate error-checking code. Suggested by Peter Gutmann.
17386 - When a hidden service is giving up on an introduction point candidate
17387 that was not included in the last published rendezvous descriptor,
17388 don't reschedule publication of the next descriptor. Fixes bug 763.
17390 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
17391 HiddenServiceExcludeNodes as obsolete: they never worked properly,
17392 and nobody claims to be using them. Fixes bug 754. Bugfix on
17393 0.1.0.1-rc. Patch from Christian Wilms.
17394 - Fix a small alignment and memory-wasting bug on buffer chunks.
17397 o Minor bugfixes (controller):
17398 - When closing an application-side connection because its circuit
17399 is getting torn down, generate the stream event correctly.
17400 Bugfix on 0.1.2.x. Anonymous patch.
17402 o Removed features:
17403 - Remove all backward-compatibility code to support relays running
17404 versions of Tor so old that they no longer work at all on the
17408 Changes in version 0.2.0.30 - 2008-07-15
17410 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
17411 warnings (occasionally), but it can also cause the compiler to
17412 eliminate error-checking code. Suggested by Peter Gutmann.
17415 Changes in version 0.2.0.29-rc - 2008-07-08
17416 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
17417 hidden-service performance bugs, and fixes a bunch of smaller bugs.
17420 - If you have more than one bridge but don't know their keys,
17421 you would only launch a request for the descriptor of the first one
17422 on your list. (Tor considered launching requests for the others, but
17423 found that it already had a connection on the way for $0000...0000
17424 so it didn't open another.) Bugfix on 0.2.0.x.
17425 - If you have more than one bridge but don't know their keys, and the
17426 connection to one of the bridges failed, you would cancel all
17427 pending bridge connections. (After all, they all have the same
17428 digest.) Bugfix on 0.2.0.x.
17429 - When a hidden service was trying to establish an introduction point,
17430 and Tor had built circuits preemptively for such purposes, we
17431 were ignoring all the preemptive circuits and launching a new one
17432 instead. Bugfix on 0.2.0.14-alpha.
17433 - When a hidden service was trying to establish an introduction point,
17434 and Tor *did* manage to reuse one of the preemptively built
17435 circuits, it didn't correctly remember which one it used,
17436 so it asked for another one soon after, until there were no
17437 more preemptive circuits, at which point it launched one from
17438 scratch. Bugfix on 0.0.9.x.
17439 - Make directory servers include the X-Your-Address-Is: http header in
17440 their responses even for begin_dir conns. Now clients who only
17441 ever use begin_dir connections still have a way to learn their IP
17442 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
17445 - Fix a macro/CPP interaction that was confusing some compilers:
17446 some GCCs don't like #if/#endif pairs inside macro arguments.
17448 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
17449 Fixes bug 704; fix from Steven Murdoch.
17450 - When opening /dev/null in finish_daemonize(), do not pass the
17451 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
17452 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
17453 - Correctly detect transparent proxy support on Linux hosts that
17454 require in.h to be included before netfilter_ipv4.h. Patch
17456 - Disallow session resumption attempts during the renegotiation
17457 stage of the v2 handshake protocol. Clients should never be trying
17458 session resumption at this point, but apparently some did, in
17459 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
17460 found by Geoff Goodell.
17463 Changes in version 0.2.1.2-alpha - 2008-06-20
17464 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
17465 make it easier to set up your own private Tor network; fixes several
17466 big bugs with using more than one bridge relay; fixes a big bug with
17467 offering hidden services quickly after Tor starts; and uses a better
17468 API for reporting potential bootstrapping problems to the controller.
17471 - New TestingTorNetwork config option to allow adjustment of
17472 previously constant values that, while reasonable, could slow
17473 bootstrapping. Implements proposal 135. Patch from Karsten.
17476 - If you have more than one bridge but don't know their digests,
17477 you would only learn a request for the descriptor of the first one
17478 on your list. (Tor considered launching requests for the others, but
17479 found that it already had a connection on the way for $0000...0000
17480 so it didn't open another.) Bugfix on 0.2.0.x.
17481 - If you have more than one bridge but don't know their digests,
17482 and the connection to one of the bridges failed, you would cancel
17483 all pending bridge connections. (After all, they all have the
17484 same digest.) Bugfix on 0.2.0.x.
17485 - When establishing a hidden service, introduction points that
17486 originate from cannibalized circuits are completely ignored and not
17487 included in rendezvous service descriptors. This might be another
17488 reason for delay in making a hidden service available. Bugfix
17489 from long ago (0.0.9.x?)
17492 - Allow OpenSSL to use dynamic locks if it wants.
17493 - When building a consensus, do not include routers that are down.
17494 This will cut down 30% to 40% on consensus size. Implements
17496 - In directory authorities' approved-routers files, allow
17497 fingerprints with or without space.
17498 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
17499 controller can query our current bootstrap state in case it attaches
17500 partway through and wants to catch up.
17501 - Send an initial "Starting" bootstrap status event, so we have a
17502 state to start out in.
17505 - Asking for a conditional consensus at .../consensus/<fingerprints>
17506 would crash a dirserver if it did not already have a
17507 consensus. Bugfix on 0.2.1.1-alpha.
17508 - Clean up some macro/CPP interactions: some GCC versions don't like
17509 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
17512 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
17513 - Directory authorities shouldn't complain about bootstrapping
17514 problems just because they do a lot of reachability testing and
17515 some of the connection attempts fail.
17516 - Start sending "count" and "recommendation" key/value pairs in
17517 bootstrap problem status events, so the controller can hear about
17518 problems even before Tor decides they're worth reporting for sure.
17519 - If you're using bridges, generate "bootstrap problem" warnings
17520 as soon as you run out of working bridges, rather than waiting
17521 for ten failures -- which will never happen if you have less than
17523 - If we close our OR connection because there's been a circuit
17524 pending on it for too long, we were telling our bootstrap status
17525 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
17528 Changes in version 0.2.1.1-alpha - 2008-06-13
17529 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
17530 were making the Tor process bloat especially on Linux; makes our TLS
17531 handshake blend in better; sends "bootstrap phase" status events to
17532 the controller, so it can keep the user informed of progress (and
17533 problems) fetching directory information and establishing circuits;
17534 and adds a variety of smaller features.
17537 - More work on making our TLS handshake blend in: modify the list
17538 of ciphers advertised by OpenSSL in client mode to even more
17539 closely resemble a common web browser. We cheat a little so that
17540 we can advertise ciphers that the locally installed OpenSSL doesn't
17542 - Start sending "bootstrap phase" status events to the controller,
17543 so it can keep the user informed of progress fetching directory
17544 information and establishing circuits. Also inform the controller
17545 if we think we're stuck at a particular bootstrap phase. Implements
17547 - Resume using OpenSSL's RAND_poll() for better (and more portable)
17548 cross-platform entropy collection again. We used to use it, then
17549 stopped using it because of a bug that could crash systems that
17550 called RAND_poll when they had a lot of fds open. It looks like the
17551 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
17552 at startup, and to call RAND_poll() when we reseed later only if
17553 we have a non-buggy OpenSSL version.
17556 - When we choose to abandon a new entry guard because we think our
17557 older ones might be better, close any circuits pending on that
17558 new entry guard connection. This fix should make us recover much
17559 faster when our network is down and then comes back. Bugfix on
17560 0.1.2.8-beta; found by lodger.
17562 o Memory fixes and improvements:
17563 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
17564 to avoid unused RAM in buffer chunks and memory pools.
17565 - Speed up parsing and cut down on memory fragmentation by using
17566 stack-style allocations for parsing directory objects. Previously,
17567 this accounted for over 40% of allocations from within Tor's code
17568 on a typical directory cache.
17569 - Use a Bloom filter rather than a digest-based set to track which
17570 descriptors we need to keep around when we're cleaning out old
17571 router descriptors. This speeds up the computation significantly,
17572 and may reduce fragmentation.
17573 - Reduce the default smartlist size from 32 to 16; it turns out that
17574 most smartlists hold around 8-12 elements tops.
17575 - Make dumpstats() log the fullness and size of openssl-internal
17577 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
17578 patch to their OpenSSL, turn it on to save memory on servers. This
17579 patch will (with any luck) get included in a mainline distribution
17581 - Never use OpenSSL compression: it wastes RAM and CPU trying to
17582 compress cells, which are basically all encrypted, compressed,
17586 - Stop reloading the router list from disk for no reason when we
17587 run out of reachable directory mirrors. Once upon a time reloading
17588 it would set the 'is_running' flag back to 1 for them. It hasn't
17589 done that for a long time.
17590 - In very rare situations new hidden service descriptors were
17591 published earlier than 30 seconds after the last change to the
17592 service. (We currently think that a hidden service descriptor
17593 that's been stable for 30 seconds is worth publishing.)
17596 - Allow separate log levels to be configured for different logging
17597 domains. For example, this allows one to log all notices, warnings,
17598 or errors, plus all memory management messages of level debug or
17599 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
17600 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
17601 and stop using a warning that had become unfixably verbose under
17603 - New --hush command-line option similar to --quiet. While --quiet
17604 disables all logging to the console on startup, --hush limits the
17605 output to messages of warning and error severity.
17606 - Servers support a new URL scheme for consensus downloads that
17607 allows the client to specify which authorities are trusted.
17608 The server then only sends the consensus if the client will trust
17609 it. Otherwise a 404 error is sent back. Clients use this
17610 new scheme when the server supports it (meaning it's running
17611 0.2.1.1-alpha or later). Implements proposal 134.
17612 - New configure/torrc options (--enable-geoip-stats,
17613 DirRecordUsageByCountry) to record how many IPs we've served
17614 directory info to in each country code, how many status documents
17615 total we've sent to each country code, and what share of the total
17616 directory requests we should expect to see.
17617 - Use the TLS1 hostname extension to more closely resemble browser
17619 - Lots of new unit tests.
17620 - Add a macro to implement the common pattern of iterating through
17621 two parallel lists in lockstep.
17624 Changes in version 0.2.0.28-rc - 2008-06-13
17625 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
17626 performance bug, and fixes a bunch of smaller bugs.
17629 - Fix a bug where, when we were choosing the 'end stream reason' to
17630 put in our relay end cell that we send to the exit relay, Tor
17631 clients on Windows were sometimes sending the wrong 'reason'. The
17632 anonymity problem is that exit relays may be able to guess whether
17633 the client is running Windows, thus helping partition the anonymity
17634 set. Down the road we should stop sending reasons to exit relays,
17635 or otherwise prevent future versions of this bug.
17638 - While setting up a hidden service, some valid introduction circuits
17639 were overlooked and abandoned. This might be the reason for
17640 the long delay in making a hidden service available. Bugfix on
17644 - Update to the "June 9 2008" ip-to-country file.
17645 - Run 'make test' as part of 'make dist', so we stop releasing so
17646 many development snapshots that fail their unit tests.
17649 - When we're checking if we have enough dir info for each relay
17650 to begin establishing circuits, make sure that we actually have
17651 the descriptor listed in the consensus, not just any descriptor.
17653 - Bridge relays no longer print "xx=0" in their extrainfo document
17654 for every single country code in the geoip db. Bugfix on
17656 - Only warn when we fail to load the geoip file if we were planning to
17657 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
17658 - If we change our MaxAdvertisedBandwidth and then reload torrc,
17659 Tor won't realize it should publish a new relay descriptor. Fixes
17660 bug 688, reported by mfr. Bugfix on 0.1.2.x.
17661 - When we haven't had any application requests lately, don't bother
17662 logging that we have expired a bunch of descriptors. Bugfix
17664 - Make relay cells written on a connection count as non-padding when
17665 tracking how long a connection has been in use. Bugfix on
17666 0.2.0.1-alpha. Spotted by lodger.
17667 - Fix unit tests in 0.2.0.27-rc.
17668 - Fix compile on Windows.
17671 Changes in version 0.2.0.27-rc - 2008-06-03
17672 Tor 0.2.0.27-rc adds a few features we left out of the earlier
17673 release candidates. In particular, we now include an IP-to-country
17674 GeoIP database, so controllers can easily look up what country a
17675 given relay is in, and so bridge relays can give us some sanitized
17676 summaries about which countries are making use of bridges. (See proposal
17677 126-geoip-fetching.txt for details.)
17680 - Include an IP-to-country GeoIP file in the tarball, so bridge
17681 relays can report sanitized summaries of the usage they're seeing.
17684 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
17685 Robert Hogan. Fixes the first part of bug 681.
17686 - Make bridge authorities never serve extrainfo docs.
17687 - Add support to detect Libevent versions in the 1.4.x series
17689 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
17690 - Include a new contrib/tor-exit-notice.html file that exit relay
17691 operators can put on their website to help reduce abuse queries.
17694 - When tunneling an encrypted directory connection, and its first
17695 circuit fails, do not leave it unattached and ask the controller
17696 to deal. Fixes the second part of bug 681.
17697 - Make bridge authorities correctly expire old extrainfo documents
17701 Changes in version 0.2.0.26-rc - 2008-05-13
17702 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
17703 in Debian's OpenSSL packages. All users running any 0.2.0.x version
17704 should upgrade, whether they're running Debian or not.
17706 o Major security fixes:
17707 - Use new V3 directory authority keys on the tor26, gabelmoo, and
17708 moria1 V3 directory authorities. The old keys were generated with
17709 a vulnerable version of Debian's OpenSSL package, and must be
17710 considered compromised. Other authorities' keys were not generated
17711 with an affected version of OpenSSL.
17714 - List authority signatures as "unrecognized" based on DirServer
17715 lines, not on cert cache. Bugfix on 0.2.0.x.
17718 - Add a new V3AuthUseLegacyKey option to make it easier for
17719 authorities to change their identity keys if they have to.
17722 Changes in version 0.2.0.25-rc - 2008-04-23
17723 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
17726 - Remember to initialize threading before initializing logging.
17727 Otherwise, many BSD-family implementations will crash hard on
17728 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
17731 - Authorities correctly free policies on bad servers on
17732 exit. Fixes bug 672. Bugfix on 0.2.0.x.
17735 Changes in version 0.2.0.24-rc - 2008-04-22
17736 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
17737 v3 directory authority, makes relays with dynamic IP addresses and no
17738 DirPort notice more quickly when their IP address changes, fixes a few
17739 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
17741 o New directory authorities:
17742 - Take lefkada out of the list of v3 directory authorities, since
17743 it has been down for months.
17744 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
17748 - Detect address changes more quickly on non-directory mirror
17749 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
17751 o Minor features (security):
17752 - Reject requests for reverse-dns lookup of names that are in
17753 a private address space. Patch from lodger.
17754 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
17757 o Minor bugfixes (crashes):
17758 - Avoid a rare assert that can trigger when Tor doesn't have much
17759 directory information yet and it tries to fetch a v2 hidden
17760 service descriptor. Fixes bug 651, reported by nwf.
17761 - Initialize log mutex before initializing dmalloc. Otherwise,
17762 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
17763 - Use recursive pthread mutexes in order to avoid deadlock when
17764 logging debug-level messages to a controller. Bug spotted by nwf,
17765 bugfix on 0.2.0.16-alpha.
17767 o Minor bugfixes (resource management):
17768 - Keep address policies from leaking memory: start their refcount
17769 at 1, not 2. Bugfix on 0.2.0.16-alpha.
17770 - Free authority certificates on exit, so they don't look like memory
17771 leaks. Bugfix on 0.2.0.19-alpha.
17772 - Free static hashtables for policy maps and for TLS connections on
17773 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
17774 - Avoid allocating extra space when computing consensuses on 64-bit
17775 platforms. Bug spotted by aakova.
17777 o Minor bugfixes (misc):
17778 - Do not read the configuration file when we've only been told to
17779 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
17780 based on patch from Sebastian Hahn.
17781 - Exit relays that are used as a client can now reach themselves
17782 using the .exit notation, rather than just launching an infinite
17783 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
17784 - When attempting to open a logfile fails, tell us why.
17785 - Fix a dumb bug that was preventing us from knowing that we should
17786 preemptively build circuits to handle expected directory requests.
17787 Fixes bug 660. Bugfix on 0.1.2.x.
17788 - Warn less verbosely about clock skew from netinfo cells from
17789 untrusted sources. Fixes bug 663.
17790 - Make controller stream events for DNS requests more consistent,
17791 by adding "new stream" events for DNS requests, and removing
17792 spurious "stream closed" events" for cached reverse resolves.
17793 Patch from mwenge. Fixes bug 646.
17794 - Correctly notify one-hop connections when a circuit build has
17795 failed. Possible fix for bug 669. Found by lodger.
17798 Changes in version 0.2.0.23-rc - 2008-03-24
17799 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
17800 makes bootstrapping faster if the first directory mirror you contact
17801 is down. The bundles also include the new Vidalia 0.1.2 release.
17804 - When a tunneled directory request is made to a directory server
17805 that's down, notice after 30 seconds rather than 120 seconds. Also,
17806 fail any begindir streams that are pending on it, so they can
17807 retry elsewhere. This was causing multi-minute delays on bootstrap.
17810 Changes in version 0.2.0.22-rc - 2008-03-18
17811 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
17812 enables encrypted directory connections by default for non-relays, fixes
17813 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
17814 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
17817 - Enable encrypted directory connections by default for non-relays,
17818 so censor tools that block Tor directory connections based on their
17819 plaintext patterns will no longer work. This means Tor works in
17820 certain censored countries by default again.
17823 - Make sure servers always request certificates from clients during
17824 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
17825 - Do not enter a CPU-eating loop when a connection is closed in
17826 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
17827 diagnosed by lodger; bugfix on 0.2.0.20-rc.
17828 - Fix assertion failure that could occur when a blocked circuit
17829 became unblocked, and it had pending client DNS requests. Bugfix
17830 on 0.2.0.1-alpha. Fixes bug 632.
17832 o Minor bugfixes (on 0.1.2.x):
17833 - Generate "STATUS_SERVER" events rather than misspelled
17834 "STATUS_SEVER" events. Caught by mwenge.
17835 - When counting the number of bytes written on a TLS connection,
17836 look at the BIO actually used for writing to the network, not
17837 at the BIO used (sometimes) to buffer data for the network.
17838 Looking at different BIOs could result in write counts on the
17839 order of ULONG_MAX. Fixes bug 614.
17840 - On Windows, correctly detect errors when listing the contents of
17841 a directory. Fix from lodger.
17843 o Minor bugfixes (on 0.2.0.x):
17844 - Downgrade "sslv3 alert handshake failure" message to INFO.
17845 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
17846 left BandwidthRate and BandwidthBurst at the default, we would be
17847 silently limited by those defaults. Now raise them to match the
17848 RelayBandwidth* values.
17849 - Fix the SVK version detection logic to work correctly on a branch.
17850 - Make --enable-openbsd-malloc work correctly on Linux with alpha
17851 CPUs. Fixes bug 625.
17852 - Logging functions now check that the passed severity is sane.
17853 - Use proper log levels in the testsuite call of
17854 get_interface_address6().
17855 - When using a nonstandard malloc, do not use the platform values for
17856 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
17857 - Make the openbsd malloc code use 8k pages on alpha CPUs and
17859 - Detect mismatched page sizes when using --enable-openbsd-malloc.
17860 - Avoid double-marked-for-close warning when certain kinds of invalid
17861 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
17862 for bug 617. Bugfix on 0.2.0.1-alpha.
17863 - Make sure that the "NULL-means-reject *:*" convention is followed by
17864 all the policy manipulation functions, avoiding some possible crash
17865 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
17866 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
17867 actually works, and doesn't warn about every single reverse lookup.
17868 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
17871 - Only log guard node status when guard node status has changed.
17872 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
17873 make "INFO" 75% less verbose.
17876 Changes in version 0.2.0.21-rc - 2008-03-02
17877 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
17878 makes Tor work well with Vidalia again, fixes a rare assert bug,
17879 and fixes a pair of more minor bugs. The bundles also include Vidalia
17880 0.1.0 and Torbutton 1.1.16.
17883 - The control port should declare that it requires password auth
17884 when HashedControlSessionPassword is set too. Patch from Matt Edman;
17885 bugfix on 0.2.0.20-rc. Fixes bug 615.
17886 - Downgrade assert in connection_buckets_decrement() to a log message.
17887 This may help us solve bug 614, and in any case will make its
17888 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
17889 - We were sometimes miscounting the number of bytes read from the
17890 network, causing our rate limiting to not be followed exactly.
17891 Bugfix on 0.2.0.16-alpha. Reported by lodger.
17894 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
17895 OpenSSL versions should have been working fine. Diagnosis and patch
17896 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
17897 Bugfix on 0.2.0.20-rc.
17900 Changes in version 0.2.0.20-rc - 2008-02-24
17901 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
17902 makes more progress towards normalizing Tor's TLS handshake, makes
17903 hidden services work better again, helps relays bootstrap if they don't
17904 know their IP address, adds optional support for linking in openbsd's
17905 allocator or tcmalloc, allows really fast relays to scale past 15000
17906 sockets, and fixes a bunch of minor bugs reported by Veracode.
17909 - Enable the revised TLS handshake based on the one designed by
17910 Steven Murdoch in proposal 124, as revised in proposal 130. It
17911 includes version negotiation for OR connections as described in
17912 proposal 105. The new handshake is meant to be harder for censors
17913 to fingerprint, and it adds the ability to detect certain kinds of
17914 man-in-the-middle traffic analysis attacks. The version negotiation
17915 feature will allow us to improve Tor's link protocol more safely
17917 - Choose which bridge to use proportional to its advertised bandwidth,
17918 rather than uniformly at random. This should speed up Tor for
17919 bridge users. Also do this for people who set StrictEntryNodes.
17920 - When a TrackHostExits-chosen exit fails too many times in a row,
17921 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
17924 - Resolved problems with (re-)fetching hidden service descriptors.
17925 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
17926 and 0.2.0.19-alpha.
17927 - If we only ever used Tor for hidden service lookups or posts, we
17928 would stop building circuits and start refusing connections after
17929 24 hours, since we falsely believed that Tor was dormant. Reported
17930 by nwf; bugfix on 0.1.2.x.
17931 - Servers that don't know their own IP address should go to the
17932 authorities for their first directory fetch, even if their DirPort
17933 is off or if they don't know they're reachable yet. This will help
17934 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
17935 - When counting the number of open sockets, count not only the number
17936 of sockets we have received from the socket() call, but also
17937 the number we've gotten from accept() and socketpair(). This bug
17938 made us fail to count all sockets that we were using for incoming
17939 connections. Bugfix on 0.2.0.x.
17940 - Fix code used to find strings within buffers, when those strings
17941 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
17942 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
17943 - Add a new __HashedControlSessionPassword option for controllers
17944 to use for one-off session password hashes that shouldn't get
17945 saved to disk by SAVECONF --- Vidalia users were accumulating a
17946 pile of HashedControlPassword lines in their torrc files, one for
17947 each time they had restarted Tor and then clicked Save. Make Tor
17948 automatically convert "HashedControlPassword" to this new option but
17949 only when it's given on the command line. Partial fix for bug 586.
17951 o Minor features (performance):
17952 - Tune parameters for cell pool allocation to minimize amount of
17954 - Add OpenBSD malloc code from phk as an optional malloc
17955 replacement on Linux: some glibc libraries do very poorly
17956 with Tor's memory allocation patterns. Pass
17957 --enable-openbsd-malloc to get the replacement malloc code.
17958 - Add a --with-tcmalloc option to the configure script to link
17959 against tcmalloc (if present). Does not yet search for
17960 non-system include paths.
17961 - Stop imposing an arbitrary maximum on the number of file descriptors
17962 used for busy servers. Bug reported by Olaf Selke; patch from
17965 o Minor features (other):
17966 - When SafeLogging is disabled, log addresses along with all TLS
17968 - When building with --enable-gcc-warnings, check for whether Apple's
17969 warning "-Wshorten-64-to-32" is available.
17970 - Add a --passphrase-fd argument to the tor-gencert command for
17973 o Minor bugfixes (memory leaks and code problems):
17974 - We were leaking a file descriptor if Tor started with a zero-length
17975 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
17976 - Detect size overflow in zlib code. Reported by Justin Ferguson and
17978 - We were comparing the raw BridgePassword entry with a base64'ed
17979 version of it, when handling a "/tor/networkstatus-bridges"
17980 directory request. Now compare correctly. Noticed by Veracode.
17981 - Recover from bad tracked-since value in MTBF-history file.
17982 Should fix bug 537.
17983 - Alter the code that tries to recover from unhandled write
17984 errors, to not try to flush onto a socket that's given us
17985 unhandled errors. Bugfix on 0.1.2.x.
17986 - Make Unix controlsockets work correctly on OpenBSD. Patch from
17987 tup. Bugfix on 0.2.0.3-alpha.
17989 o Minor bugfixes (other):
17990 - If we have an extra-info document for our server, always make
17991 it available on the control port, even if we haven't gotten
17992 a copy of it from an authority yet. Patch from mwenge.
17993 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
17994 - Directory mirrors no longer include a guess at the client's IP
17995 address if the connection appears to be coming from the same /24
17996 network; it was producing too many wrong guesses.
17997 - Make the new hidden service code respect the SafeLogging setting.
17998 Bugfix on 0.2.0.x. Patch from Karsten.
17999 - When starting as an authority, do not overwrite all certificates
18000 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
18001 - If we're trying to flush the last bytes on a connection (for
18002 example, when answering a directory request), reset the
18003 time-to-give-up timeout every time we manage to write something
18004 on the socket. Bugfix on 0.1.2.x.
18005 - Change the behavior of "getinfo status/good-server-descriptor"
18006 so it doesn't return failure when any authority disappears.
18007 - Even though the man page said that "TrackHostExits ." should
18008 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
18009 - Report TLS "zero return" case as a "clean close" and "IO error"
18010 as a "close". Stop calling closes "unexpected closes": existing
18011 Tors don't use SSL_close(), so having a connection close without
18012 the TLS shutdown handshake is hardly unexpected.
18013 - Send NAMESERVER_STATUS messages for a single failed nameserver
18016 o Code simplifications and refactoring:
18017 - Remove the tor_strpartition function: its logic was confused,
18018 and it was only used for one thing that could be implemented far
18022 Changes in version 0.2.0.19-alpha - 2008-02-09
18023 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
18024 handshake, makes path selection for relays more secure and IP address
18025 guessing more robust, and generally fixes a lot of bugs in preparation
18026 for calling the 0.2.0 branch stable.
18029 - Do not include recognizeable strings in the commonname part of
18030 Tor's x509 certificates.
18033 - If we're a relay, avoid picking ourselves as an introduction point,
18034 a rendezvous point, or as the final hop for internal circuits. Bug
18035 reported by taranis and lodger. Bugfix on 0.1.2.x.
18036 - Patch from "Andrew S. Lists" to catch when we contact a directory
18037 mirror at IP address X and he says we look like we're coming from
18038 IP address X. Bugfix on 0.1.2.x.
18040 o Minor features (security):
18041 - Be more paranoid about overwriting sensitive memory on free(),
18042 as a defensive programming tactic to ensure forward secrecy.
18044 o Minor features (directory authority):
18045 - Actually validate the options passed to AuthDirReject,
18046 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
18047 - Reject router descriptors with out-of-range bandwidthcapacity or
18048 bandwidthburst values.
18050 o Minor features (controller):
18051 - Reject controller commands over 1MB in length. This keeps rogue
18052 processes from running us out of memory.
18054 o Minor features (misc):
18055 - Give more descriptive well-formedness errors for out-of-range
18056 hidden service descriptor/protocol versions.
18057 - Make memory debugging information describe more about history
18058 of cell allocation, so we can help reduce our memory use.
18060 o Deprecated features (controller):
18061 - The status/version/num-versioning and status/version/num-concurring
18062 GETINFO options are no longer useful in the v3 directory protocol:
18063 treat them as deprecated, and warn when they're used.
18066 - When our consensus networkstatus has been expired for a while, stop
18067 being willing to build circuits using it. Fixes bug 401. Bugfix
18069 - Directory caches now fetch certificates from all authorities
18070 listed in a networkstatus consensus, even when they do not
18071 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
18072 - When connecting to a bridge without specifying its key, insert
18073 the connection into the identity-to-connection map as soon as
18074 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
18075 - Detect versions of OS X where malloc_good_size() is present in the
18076 library but never actually declared. Resolves bug 587. Bugfix
18078 - Stop incorrectly truncating zlib responses to directory authority
18079 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
18080 - Stop recommending that every server operator send mail to tor-ops.
18081 Resolves bug 597. Bugfix on 0.1.2.x.
18082 - Don't trigger an assert if we start a directory authority with a
18083 private IP address (like 127.0.0.1).
18084 - Avoid possible failures when generating a directory with routers
18085 with over-long versions strings, or too many flags set. Bugfix
18087 - If an attempt to launch a DNS resolve request over the control
18088 port fails because we have overrun the limit on the number of
18089 connections, tell the controller that the request has failed.
18090 - Avoid using too little bandwidth when our clock skips a few
18091 seconds. Bugfix on 0.1.2.x.
18092 - Fix shell error when warning about missing packages in configure
18093 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
18094 - Do not become confused when receiving a spurious VERSIONS-like
18095 cell from a confused v1 client. Bugfix on 0.2.0.x.
18096 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
18097 introduction points for a hidden service have failed. Patch from
18098 Karsten Loesing. Bugfix on 0.2.0.x.
18100 o Code simplifications and refactoring:
18101 - Remove some needless generality from cpuworker code, for improved
18103 - Stop overloading the circuit_t.onionskin field for both "onionskin
18104 from a CREATE cell that we are waiting for a cpuworker to be
18105 assigned" and "onionskin from an EXTEND cell that we are going to
18106 send to an OR as soon as we are connected". Might help with bug 600.
18107 - Add an in-place version of aes_crypt() so that we can avoid doing a
18108 needless memcpy() call on each cell payload.
18111 Changes in version 0.2.0.18-alpha - 2008-01-25
18112 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
18113 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
18114 that can warn or reject connections to ports generally associated with
18115 vulnerable-plaintext protocols.
18117 o New directory authorities:
18118 - Set up dannenberg (run by CCC) as the sixth v3 directory
18122 - Fix a major memory leak when attempting to use the v2 TLS
18123 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
18124 - We accidentally enabled the under-development v2 TLS handshake
18125 code, which was causing log entries like "TLS error while
18126 renegotiating handshake". Disable it again. Resolves bug 590.
18127 - We were computing the wrong Content-Length: header for directory
18128 responses that need to be compressed on the fly, causing clients
18129 asking for those items to always fail. Bugfix on 0.2.0.x; partially
18133 - Avoid going directly to the directory authorities even if you're a
18134 relay, if you haven't found yourself reachable yet or if you've
18135 decided not to advertise your dirport yet. Addresses bug 556.
18136 - If we've gone 12 hours since our last bandwidth check, and we
18137 estimate we have less than 50KB bandwidth capacity but we could
18138 handle more, do another bandwidth test.
18139 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
18140 Tor can warn and/or refuse connections to ports commonly used with
18141 vulnerable-plaintext protocols. Currently we warn on ports 23,
18142 109, 110, and 143, but we don't reject any.
18145 - When we setconf ClientOnly to 1, close any current OR and Dir
18146 listeners. Reported by mwenge.
18147 - When we get a consensus that's been signed by more people than
18148 we expect, don't log about it; it's not a big deal. Reported
18152 - Don't answer "/tor/networkstatus-bridges" directory requests if
18153 the request isn't encrypted.
18154 - Make "ClientOnly 1" config option disable directory ports too.
18155 - Patches from Karsten Loesing to make v2 hidden services more
18156 robust: work even when there aren't enough HSDir relays available;
18157 retry when a v2 rend desc fetch fails; but don't retry if we
18158 already have a usable v0 rend desc.
18161 Changes in version 0.2.0.17-alpha - 2008-01-17
18162 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
18165 - Make the tor-gencert man page get included correctly in the tarball.
18168 Changes in version 0.2.0.16-alpha - 2008-01-17
18169 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
18170 Loesing, and generally cleans up a lot of features and minor bugs.
18172 o New directory authorities:
18173 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
18176 o Major performance improvements:
18177 - Switch our old ring buffer implementation for one more like that
18178 used by free Unix kernels. The wasted space in a buffer with 1mb
18179 of data will now be more like 8k than 1mb. The new implementation
18180 also avoids realloc();realloc(); patterns that can contribute to
18181 memory fragmentation.
18184 - Configuration files now accept C-style strings as values. This
18185 helps encode characters not allowed in the current configuration
18186 file format, such as newline or #. Addresses bug 557.
18187 - Although we fixed bug 539 (where servers would send HTTP status 503
18188 responses _and_ send a body too), there are still servers out
18189 there that haven't upgraded. Therefore, make clients parse such
18190 bodies when they receive them.
18191 - When we're not serving v2 directory information, there is no reason
18192 to actually keep any around. Remove the obsolete files and directory
18193 on startup if they are very old and we aren't going to serve them.
18195 o Minor performance improvements:
18196 - Reference-count and share copies of address policy entries; only 5%
18197 of them were actually distinct.
18198 - Never walk through the list of logs if we know that no log is
18199 interested in a given message.
18202 - When an authority has not signed a consensus, do not try to
18203 download a nonexistent "certificate with key 00000000". Bugfix
18204 on 0.2.0.x. Fixes bug 569.
18205 - Fix a rare assert error when we're closing one of our threads:
18206 use a mutex to protect the list of logs, so we never write to the
18207 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
18208 bug 575, which is kind of the revenge of bug 222.
18209 - Patch from Karsten Loesing to complain less at both the client
18210 and the relay when a relay used to have the HSDir flag but doesn't
18211 anymore, and we try to upload a hidden service descriptor.
18212 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
18214 - Do not try to download missing certificates until we have tried
18215 to check our fallback consensus. Fixes bug 583.
18216 - Make bridges round reported GeoIP stats info up to the nearest
18217 estimate, not down. Now we can distinguish between "0 people from
18218 this country" and "1 person from this country".
18219 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
18220 - Avoid possible segfault if key generation fails in
18221 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
18222 - Avoid segfault in the case where a badly behaved v2 versioning
18223 directory sends a signed networkstatus with missing client-versions.
18225 - Avoid segfaults on certain complex invocations of
18226 router_get_by_hexdigest(). Bugfix on 0.1.2.
18227 - Correct bad index on array access in parse_http_time(). Bugfix
18229 - Fix possible bug in vote generation when server versions are present
18230 but client versions are not.
18231 - Fix rare bug on REDIRECTSTREAM control command when called with no
18232 port set: it could erroneously report an error when none had
18234 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
18235 compressing large objects and find ourselves with more than 4k
18236 left over. Bugfix on 0.2.0.
18237 - Fix a small memory leak when setting up a hidden service.
18238 - Fix a few memory leaks that could in theory happen under bizarre
18240 - Fix an assert if we post a general-purpose descriptor via the
18241 control port but that descriptor isn't mentioned in our current
18242 network consensus. Bug reported by Jon McLachlan; bugfix on
18245 o Minor features (controller):
18246 - Get NS events working again. Patch from tup.
18247 - The GETCONF command now escapes and quotes configuration values
18248 that don't otherwise fit into the torrc file.
18249 - The SETCONF command now handles quoted values correctly.
18251 o Minor features (directory authorities):
18252 - New configuration options to override default maximum number of
18253 servers allowed on a single IP address. This is important for
18254 running a test network on a single host.
18255 - Actually implement the -s option to tor-gencert.
18256 - Add a manual page for tor-gencert.
18258 o Minor features (bridges):
18259 - Bridge authorities no longer serve bridge descriptors over
18260 unencrypted connections.
18262 o Minor features (other):
18263 - Add hidden services and DNSPorts to the list of things that make
18264 Tor accept that it has running ports. Change starting Tor with no
18265 ports from a fatal error to a warning; we might change it back if
18266 this turns out to confuse anybody. Fixes bug 579.
18269 Changes in version 0.1.2.19 - 2008-01-17
18270 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
18271 exit policy a little bit more conservative so it's safer to run an
18272 exit relay on a home system, and fixes a variety of smaller issues.
18275 - Exit policies now reject connections that are addressed to a
18276 relay's public (external) IP address too, unless
18277 ExitPolicyRejectPrivate is turned off. We do this because too
18278 many relays are running nearby to services that trust them based
18279 on network address.
18282 - When the clock jumps forward a lot, do not allow the bandwidth
18283 buckets to become negative. Fixes bug 544.
18284 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
18285 on every successful resolve. Reported by Mike Perry.
18286 - Purge old entries from the "rephist" database and the hidden
18287 service descriptor database even when DirPort is zero.
18288 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
18289 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
18290 crashing or mis-answering these requests.
18291 - When we decide to send a 503 response to a request for servers, do
18292 not then also send the server descriptors: this defeats the whole
18293 purpose. Fixes bug 539.
18296 - Changing the ExitPolicyRejectPrivate setting should cause us to
18297 rebuild our server descriptor.
18298 - Fix handling of hex nicknames when answering controller requests for
18299 networkstatus by name, or when deciding whether to warn about
18300 unknown routers in a config option. (Patch from mwenge.)
18301 - Fix a couple of hard-to-trigger autoconf problems that could result
18302 in really weird results on platforms whose sys/types.h files define
18303 nonstandard integer types.
18304 - Don't try to create the datadir when running --verify-config or
18305 --hash-password. Resolves bug 540.
18306 - If we were having problems getting a particular descriptor from the
18307 directory caches, and then we learned about a new descriptor for
18308 that router, we weren't resetting our failure count. Reported
18310 - Although we fixed bug 539 (where servers would send HTTP status 503
18311 responses _and_ send a body too), there are still servers out there
18312 that haven't upgraded. Therefore, make clients parse such bodies
18313 when they receive them.
18314 - Run correctly on systems where rlim_t is larger than unsigned long.
18315 This includes some 64-bit systems.
18316 - Run correctly on platforms (like some versions of OS X 10.5) where
18317 the real limit for number of open files is OPEN_FILES, not rlim_max
18318 from getrlimit(RLIMIT_NOFILES).
18319 - Avoid a spurious free on base64 failure.
18320 - Avoid segfaults on certain complex invocations of
18321 router_get_by_hexdigest().
18322 - Fix rare bug on REDIRECTSTREAM control command when called with no
18323 port set: it could erroneously report an error when none had
18327 Changes in version 0.2.0.15-alpha - 2007-12-25
18328 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
18329 features added in 0.2.0.13-alpha.
18332 - Fix several remotely triggerable asserts based on DirPort requests
18333 for a v2 or v3 networkstatus object before we were prepared. This
18334 was particularly bad for 0.2.0.13 and later bridge relays, who
18335 would never have a v2 networkstatus and would thus always crash
18336 when used. Bugfixes on 0.2.0.x.
18337 - Estimate the v3 networkstatus size more accurately, rather than
18338 estimating it at zero bytes and giving it artificially high priority
18339 compared to other directory requests. Bugfix on 0.2.0.x.
18342 - Fix configure.in logic for cross-compilation.
18343 - When we load a bridge descriptor from the cache, and it was
18344 previously unreachable, mark it as retriable so we won't just
18345 ignore it. Also, try fetching a new copy immediately. Bugfixes
18347 - The bridge GeoIP stats were counting other relays, for example
18348 self-reachability and authority-reachability tests.
18351 - Support compilation to target iPhone; patch from cjacker huang.
18352 To build for iPhone, pass the --enable-iphone option to configure.
18355 Changes in version 0.2.0.14-alpha - 2007-12-23
18357 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
18358 without a datadirectory from a previous Tor install. Reported
18360 - Fix a crash when we fetch a descriptor that turns out to be
18361 unexpected (it used to be in our networkstatus when we started
18362 fetching it, but it isn't in our current networkstatus), and we
18363 aren't using bridges. Bugfix on 0.2.0.x.
18364 - Fix a crash when accessing hidden services: it would work the first
18365 time you use a given introduction point for your service, but
18366 on subsequent requests we'd be using garbage memory. Fixed by
18367 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
18368 - Fix a crash when we load a bridge descriptor from disk but we don't
18369 currently have a Bridge line for it in our torrc. Bugfix on
18373 - If bridge authorities set BridgePassword, they will serve a
18374 snapshot of known bridge routerstatuses from their DirPort to
18375 anybody who knows that password. Unset by default.
18378 - Make the unit tests build again.
18379 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
18380 - Make PublishServerDescriptor default to 1, so the default doesn't
18381 have to change as we invent new directory protocol versions.
18382 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
18383 be included unless sys/time.h is already included. Fixes
18384 bug 553. Bugfix on 0.2.0.x.
18385 - If we receive a general-purpose descriptor and then receive an
18386 identical bridge-purpose descriptor soon after, don't discard
18387 the next one as a duplicate.
18390 - If BridgeRelay is set to 1, then the default for
18391 PublishServerDescriptor is now "bridge" rather than "v2,v3".
18392 - If the user sets RelayBandwidthRate but doesn't set
18393 RelayBandwidthBurst, then make them equal rather than erroring out.
18396 Changes in version 0.2.0.13-alpha - 2007-12-21
18397 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
18398 Goodell, fixes many more bugs, and adds a lot of infrastructure for
18401 o New directory authorities:
18402 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
18406 - Only update guard status (usable / not usable) once we have
18407 enough directory information. This was causing us to always pick
18408 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
18409 causing us to discard all our guards on startup if we hadn't been
18410 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
18411 - Purge old entries from the "rephist" database and the hidden
18412 service descriptor databases even when DirPort is zero. Bugfix
18414 - We were ignoring our RelayBandwidthRate for the first 30 seconds
18415 after opening a circuit -- even a relayed circuit. Bugfix on
18417 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
18418 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
18419 crashing or mis-answering these types of requests.
18420 - Relays were publishing their server descriptor to v1 and v2
18421 directory authorities, but they didn't try publishing to v3-only
18422 authorities. Fix this; and also stop publishing to v1 authorities.
18424 - When we were reading router descriptors from cache, we were ignoring
18425 the annotations -- so for example we were reading in bridge-purpose
18426 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
18427 - When we decided to send a 503 response to a request for servers, we
18428 were then also sending the server descriptors: this defeats the
18429 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
18432 - Bridge relays now behave like clients with respect to time
18433 intervals for downloading new consensus documents -- otherwise they
18434 stand out. Bridge users now wait until the end of the interval,
18435 so their bridge relay will be sure to have a new consensus document.
18436 - Three new config options (AlternateDirAuthority,
18437 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
18438 user selectively replace the default directory authorities by type,
18439 rather than the all-or-nothing replacement that DirServer offers.
18440 - Tor can now be configured to read a GeoIP file from disk in one
18441 of two formats. This can be used by controllers to map IP addresses
18442 to countries. Eventually, it may support exit-by-country.
18443 - When possible, bridge relays remember which countries users
18444 are coming from, and report aggregate information in their
18445 extra-info documents, so that the bridge authorities can learn
18446 where Tor is blocked.
18447 - Bridge directory authorities now do reachability testing on the
18448 bridges they know. They provide router status summaries to the
18449 controller via "getinfo ns/purpose/bridge", and also dump summaries
18450 to a file periodically.
18451 - Stop fetching directory info so aggressively if your DirPort is
18452 on but your ORPort is off; stop fetching v2 dir info entirely.
18453 You can override these choices with the new FetchDirInfoEarly
18457 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
18458 consensus documents when there are too many relays at a single
18459 IP address. Now clear it in v2 network status documents too, and
18460 also clear it in routerinfo_t when the relay is no longer listed
18461 in the relevant networkstatus document.
18462 - Don't crash if we get an unexpected value for the
18463 PublishServerDescriptor config option. Reported by Matt Edman;
18464 bugfix on 0.2.0.9-alpha.
18465 - Our new v2 hidden service descriptor format allows descriptors
18466 that have no introduction points. But Tor crashed when we tried
18467 to build a descriptor with no intro points (and it would have
18468 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
18469 by Karsten Loesing.
18470 - Fix building with dmalloc 5.5.2 with glibc.
18471 - Reject uploaded descriptors and extrainfo documents if they're
18472 huge. Otherwise we'll cache them all over the network and it'll
18473 clog everything up. Reported by Aljosha Judmayer.
18474 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
18475 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
18476 - When the DANGEROUS_VERSION controller status event told us we're
18477 running an obsolete version, it used the string "OLD" to describe
18478 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
18479 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
18480 - If we can't expand our list of entry guards (e.g. because we're
18481 using bridges or we have StrictEntryNodes set), don't mark relays
18482 down when they fail a directory request. Otherwise we're too quick
18483 to mark all our entry points down. Bugfix on 0.1.2.x.
18484 - Fix handling of hex nicknames when answering controller requests for
18485 networkstatus by name, or when deciding whether to warn about unknown
18486 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
18487 - Fix a couple of hard-to-trigger autoconf problems that could result
18488 in really weird results on platforms whose sys/types.h files define
18489 nonstandard integer types. Bugfix on 0.1.2.x.
18490 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
18491 - Don't crash on name lookup when we have no current consensus. Fixes
18492 bug 538; bugfix on 0.2.0.x.
18493 - Only Tors that want to mirror the v2 directory info should
18494 create the "cached-status" directory in their datadir. (All Tors
18495 used to create it.) Bugfix on 0.2.0.9-alpha.
18496 - Directory authorities should only automatically download Extra Info
18497 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
18500 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
18501 consumers. (We already do this on HUP.)
18502 - Authorities and caches fetch the v2 networkstatus documents
18503 less often, now that v3 is encouraged.
18504 - Add a new config option BridgeRelay that specifies you want to
18505 be a bridge relay. Right now the only difference is that it makes
18506 you answer begin_dir requests, and it makes you cache dir info,
18507 even if your DirPort isn't on.
18508 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
18509 ask about source, timestamp of arrival, purpose, etc. We need
18510 something like this to help Vidalia not do GeoIP lookups on bridge
18512 - Allow multiple HashedControlPassword config lines, to support
18513 multiple controller passwords.
18514 - Authorities now decide whether they're authoritative for a given
18515 router based on the router's purpose.
18516 - New config options AuthDirBadDir and AuthDirListBadDirs for
18517 authorities to mark certain relays as "bad directories" in the
18518 networkstatus documents. Also supports the "!baddir" directive in
18519 the approved-routers file.
18522 Changes in version 0.2.0.12-alpha - 2007-11-16
18523 This twelfth development snapshot fixes some more build problems as
18524 well as a few minor bugs.
18527 - Make it build on OpenBSD again. Patch from tup.
18528 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
18529 package-building for Red Hat, OS X, etc.
18531 o Minor bugfixes (on 0.1.2.x):
18532 - Changing the ExitPolicyRejectPrivate setting should cause us to
18533 rebuild our server descriptor.
18535 o Minor bugfixes (on 0.2.0.x):
18536 - When we're lacking a consensus, don't try to perform rendezvous
18537 operations. Reported by Karsten Loesing.
18538 - Fix a small memory leak whenever we decide against using a
18539 newly picked entry guard. Reported by Mike Perry.
18540 - When authorities detected more than two relays running on the same
18541 IP address, they were clearing all the status flags but forgetting
18542 to clear the "hsdir" flag. So clients were being told that a
18543 given relay was the right choice for a v2 hsdir lookup, yet they
18544 never had its descriptor because it was marked as 'not running'
18546 - If we're trying to fetch a bridge descriptor and there's no way
18547 the bridge authority could help us (for example, we don't know
18548 a digest, or there is no bridge authority), don't be so eager to
18549 fall back to asking the bridge authority.
18550 - If we're using bridges or have strictentrynodes set, and our
18551 chosen exit is in the same family as all our bridges/entry guards,
18552 then be flexible about families.
18555 - When we negotiate a v2 link-layer connection (not yet implemented),
18556 accept RELAY_EARLY cells and turn them into RELAY cells if we've
18557 negotiated a v1 connection for their next step. Initial code for
18561 Changes in version 0.2.0.11-alpha - 2007-11-12
18562 This eleventh development snapshot fixes some build problems with
18563 the previous snapshot. It also includes a more secure-by-default exit
18564 policy for relays, fixes an enormous memory leak for exit relays, and
18565 fixes another bug where servers were falling out of the directory list.
18568 - Exit policies now reject connections that are addressed to a
18569 relay's public (external) IP address too, unless
18570 ExitPolicyRejectPrivate is turned off. We do this because too
18571 many relays are running nearby to services that trust them based
18572 on network address. Bugfix on 0.1.2.x.
18575 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
18576 on every successful resolve. Reported by Mike Perry; bugfix
18578 - On authorities, never downgrade to old router descriptors simply
18579 because they're listed in the consensus. This created a catch-22
18580 where we wouldn't list a new descriptor because there was an
18581 old one in the consensus, and we couldn't get the new one in the
18582 consensus because we wouldn't list it. Possible fix for bug 548.
18583 Also, this might cause bug 543 to appear on authorities; if so,
18584 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
18586 o Packaging fixes on 0.2.0.10-alpha:
18587 - We were including instructions about what to do with the
18588 src/config/fallback-consensus file, but we weren't actually
18589 including it in the tarball. Disable all of that for now.
18592 - Allow people to say PreferTunnelledDirConns rather than
18593 PreferTunneledDirConns, for those alternate-spellers out there.
18596 - Don't reevaluate all the information from our consensus document
18597 just because we've downloaded a v2 networkstatus that we intend
18598 to cache. Fixes bug 545; bugfix on 0.2.0.x.
18601 Changes in version 0.2.0.10-alpha - 2007-11-10
18602 This tenth development snapshot adds a third v3 directory authority
18603 run by Mike Perry, adds most of Karsten Loesing's new hidden service
18604 descriptor format, fixes a bad crash bug and new bridge bugs introduced
18605 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
18606 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
18607 addresses many more minor issues.
18609 o New directory authorities:
18610 - Set up ides (run by Mike Perry) as the third v3 directory authority.
18613 - Allow tunnelled directory connections to ask for an encrypted
18614 "begin_dir" connection or an anonymized "uses a full Tor circuit"
18615 connection independently. Now we can make anonymized begin_dir
18616 connections for (e.g.) more secure hidden service posting and
18618 - More progress on proposal 114: code from Karsten Loesing to
18619 implement new hidden service descriptor format.
18620 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
18621 accommodate the growing number of servers that use the default
18622 and are reaching it.
18623 - Directory authorities use a new formula for selecting which nodes
18624 to advertise as Guards: they must be in the top 7/8 in terms of
18625 how long we have known about them, and above the median of those
18626 nodes in terms of weighted fractional uptime.
18627 - Make "not enough dir info yet" warnings describe *why* Tor feels
18628 it doesn't have enough directory info yet.
18631 - Stop servers from crashing if they set a Family option (or
18632 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
18634 - Make bridge users work again -- the move to v3 directories in
18635 0.2.0.9-alpha had introduced a number of bugs that made bridges
18636 no longer work for clients.
18637 - When the clock jumps forward a lot, do not allow the bandwidth
18638 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
18640 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
18641 - When the consensus lists a router descriptor that we previously were
18642 mirroring, but that we considered non-canonical, reload the
18643 descriptor as canonical. This fixes bug 543 where Tor servers
18644 would start complaining after a few days that they don't have
18645 enough directory information to build a circuit.
18646 - Consider replacing the current consensus when certificates arrive
18647 that make the pending consensus valid. Previously, we were only
18648 considering replacement when the new certs _didn't_ help.
18649 - Fix an assert error on startup if we didn't already have the
18650 consensus and certs cached in our datadirectory: we were caching
18651 the consensus in consensus_waiting_for_certs but then free'ing it
18653 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
18654 Request) if we need more v3 certs but we've already got pending
18655 requests for all of them.
18656 - Correctly back off from failing certificate downloads. Fixes
18658 - Authorities don't vote on the Running flag if they have been running
18659 for less than 30 minutes themselves. Fixes bug 547, where a newly
18660 started authority would vote that everyone was down.
18662 o New requirements:
18663 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
18664 it, it had no AES, and it hasn't seen any security patches since
18668 - Clients now hold circuitless TLS connections open for 1.5 times
18669 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
18670 rebuild a new circuit over them within that timeframe. Previously,
18671 they held them open only for KeepalivePeriod (5 minutes).
18672 - Use "If-Modified-Since" to avoid retrieving consensus
18673 networkstatuses that we already have.
18674 - When we have no consensus, check FallbackNetworkstatusFile (defaults
18675 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
18676 we start knowing some directory caches.
18677 - When we receive a consensus from the future, warn about skew.
18678 - Improve skew reporting: try to give the user a better log message
18679 about how skewed they are, and how much this matters.
18680 - When we have a certificate for an authority, believe that
18681 certificate's claims about the authority's IP address.
18682 - New --quiet command-line option to suppress the default console log.
18683 Good in combination with --hash-password.
18684 - Authorities send back an X-Descriptor-Not-New header in response to
18685 an accepted-but-discarded descriptor upload. Partially implements
18687 - Make the log message for "tls error. breaking." more useful.
18688 - Better log messages about certificate downloads, to attempt to
18689 track down the second incarnation of bug 546.
18691 o Minor features (bridges):
18692 - If bridge users set UpdateBridgesFromAuthority, but the digest
18693 they ask for is a 404 from the bridge authority, they now fall
18694 back to trying the bridge directly.
18695 - Bridges now use begin_dir to publish their server descriptor to
18696 the bridge authority, even when they haven't set TunnelDirConns.
18698 o Minor features (controller):
18699 - When reporting clock skew, and we know that the clock is _at least
18700 as skewed_ as some value, but we don't know the actual value,
18701 report the value as a "minimum skew."
18704 - Update linux-tor-prio.sh script to allow QoS based on the uid of
18705 the Tor process. Patch from Marco Bonetti with tweaks from Mike
18709 - Refuse to start if both ORPort and UseBridges are set. Bugfix
18710 on 0.2.0.x, suggested by Matt Edman.
18711 - Don't stop fetching descriptors when FetchUselessDescriptors is
18712 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
18713 reported by tup and ioerror.
18714 - Better log message on vote from unknown authority.
18715 - Don't log "Launching 0 request for 0 router" message.
18717 o Minor bugfixes (memory leaks):
18718 - Stop leaking memory every time we parse a v3 certificate. Bugfix
18720 - Stop leaking memory every time we load a v3 certificate. Bugfix
18721 on 0.2.0.1-alpha. Fixes bug 536.
18722 - Stop leaking a cached networkstatus on exit. Bugfix on
18724 - Stop leaking voter information every time we free a consensus.
18725 Bugfix on 0.2.0.3-alpha.
18726 - Stop leaking signed data every time we check a voter signature.
18727 Bugfix on 0.2.0.3-alpha.
18728 - Stop leaking a signature every time we fail to parse a consensus or
18729 a vote. Bugfix on 0.2.0.3-alpha.
18730 - Stop leaking v2_download_status_map on shutdown. Bugfix on
18732 - Stop leaking conn->nickname every time we make a connection to a
18733 Tor relay without knowing its expected identity digest (e.g. when
18734 using bridges). Bugfix on 0.2.0.3-alpha.
18736 - Minor bugfixes (portability):
18737 - Run correctly on platforms where rlim_t is larger than unsigned
18738 long, and/or where the real limit for number of open files is
18739 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
18740 particular, these may be needed for OS X 10.5.
18743 Changes in version 0.1.2.18 - 2007-10-28
18744 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
18745 hidden service introduction that were causing huge delays, and a big
18746 bug that was causing some servers to disappear from the network status
18747 lists for a few hours each day.
18749 o Major bugfixes (crashes):
18750 - If a connection is shut down abruptly because of something that
18751 happened inside connection_flushed_some(), do not call
18752 connection_finished_flushing(). Should fix bug 451:
18753 "connection_stop_writing: Assertion conn->write_event failed"
18754 Bugfix on 0.1.2.7-alpha.
18755 - Fix possible segfaults in functions called from
18756 rend_process_relay_cell().
18758 o Major bugfixes (hidden services):
18759 - Hidden services were choosing introduction points uniquely by
18760 hexdigest, but when constructing the hidden service descriptor
18761 they merely wrote the (potentially ambiguous) nickname.
18762 - Clients now use the v2 intro format for hidden service
18763 connections: they specify their chosen rendezvous point by identity
18764 digest rather than by (potentially ambiguous) nickname. These
18765 changes could speed up hidden service connections dramatically.
18767 o Major bugfixes (other):
18768 - Stop publishing a new server descriptor just because we get a
18769 HUP signal. This led (in a roundabout way) to some servers getting
18770 dropped from the networkstatus lists for a few hours each day.
18771 - When looking for a circuit to cannibalize, consider family as well
18772 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
18773 circuit cannibalization).
18774 - When a router wasn't listed in a new networkstatus, we were leaving
18775 the flags for that router alone -- meaning it remained Named,
18776 Running, etc -- even though absence from the networkstatus means
18777 that it shouldn't be considered to exist at all anymore. Now we
18778 clear all the flags for routers that fall out of the networkstatus
18779 consensus. Fixes bug 529.
18782 - Don't try to access (or alter) the state file when running
18783 --list-fingerprint or --verify-config or --hash-password. Resolves
18785 - When generating information telling us how to extend to a given
18786 router, do not try to include the nickname if it is
18787 absent. Resolves bug 467.
18788 - Fix a user-triggerable segfault in expand_filename(). (There isn't
18789 a way to trigger this remotely.)
18790 - When sending a status event to the controller telling it that an
18791 OR address is reachable, set the port correctly. (Previously we
18792 were reporting the dir port.)
18793 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
18794 command. Bugfix on 0.1.2.17.
18795 - When loading bandwidth history, do not believe any information in
18796 the future. Fixes bug 434.
18797 - When loading entry guard information, do not believe any information
18799 - When we have our clock set far in the future and generate an
18800 onion key, then re-set our clock to be correct, we should not stop
18801 the onion key from getting rotated.
18802 - On some platforms, accept() can return a broken address. Detect
18803 this more quietly, and deal accordingly. Fixes bug 483.
18804 - It's not actually an error to find a non-pending entry in the DNS
18805 cache when canceling a pending resolve. Don't log unless stuff
18806 is fishy. Resolves bug 463.
18807 - Don't reset trusted dir server list when we set a configuration
18808 option. Patch from Robert Hogan.
18809 - Don't try to create the datadir when running --verify-config or
18810 --hash-password. Resolves bug 540.
18813 Changes in version 0.2.0.9-alpha - 2007-10-24
18814 This ninth development snapshot switches clients to the new v3 directory
18815 system; allows servers to be listed in the network status even when they
18816 have the same nickname as a registered server; and fixes many other
18817 bugs including a big one that was causing some servers to disappear
18818 from the network status lists for a few hours each day.
18820 o Major features (directory system):
18821 - Clients now download v3 consensus networkstatus documents instead
18822 of v2 networkstatus documents. Clients and caches now base their
18823 opinions about routers on these consensus documents. Clients only
18824 download router descriptors listed in the consensus.
18825 - Authorities now list servers who have the same nickname as
18826 a different named server, but list them with a new flag,
18827 "Unnamed". Now we can list servers that happen to pick the same
18828 nickname as a server that registered two years ago and then
18829 disappeared. Partially implements proposal 122.
18830 - If the consensus lists a router as "Unnamed", the name is assigned
18831 to a different router: do not identify the router by that name.
18832 Partially implements proposal 122.
18833 - Authorities can now come to a consensus on which method to use to
18834 compute the consensus. This gives us forward compatibility.
18837 - Stop publishing a new server descriptor just because we HUP or
18838 when we find our DirPort to be reachable but won't actually publish
18839 it. New descriptors without any real changes are dropped by the
18840 authorities, and can screw up our "publish every 18 hours" schedule.
18842 - When a router wasn't listed in a new networkstatus, we were leaving
18843 the flags for that router alone -- meaning it remained Named,
18844 Running, etc -- even though absence from the networkstatus means
18845 that it shouldn't be considered to exist at all anymore. Now we
18846 clear all the flags for routers that fall out of the networkstatus
18847 consensus. Fixes bug 529; bugfix on 0.1.2.x.
18848 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
18849 extrainfo documents and then discard them immediately for not
18850 matching the latest router. Bugfix on 0.2.0.1-alpha.
18852 o Minor features (v3 directory protocol):
18853 - Allow tor-gencert to generate a new certificate without replacing
18855 - Allow certificates to include an address.
18856 - When we change our directory-cache settings, reschedule all voting
18857 and download operations.
18858 - Reattempt certificate downloads immediately on failure, as long as
18859 we haven't failed a threshold number of times yet.
18860 - Delay retrying consensus downloads while we're downloading
18861 certificates to verify the one we just got. Also, count getting a
18862 consensus that we already have (or one that isn't valid) as a failure,
18863 and count failing to get the certificates after 20 minutes as a
18865 - Build circuits and download descriptors even if our consensus is a
18866 little expired. (This feature will go away once authorities are
18869 o Minor features (router descriptor cache):
18870 - If we find a cached-routers file that's been sitting around for more
18871 than 28 days unmodified, then most likely it's a leftover from
18872 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
18874 - When we (as a cache) download a descriptor because it was listed
18875 in a consensus, remember when the consensus was supposed to expire,
18876 and don't expire the descriptor until then.
18878 o Minor features (performance):
18879 - Call routerlist_remove_old_routers() much less often. This should
18880 speed startup, especially on directory caches.
18881 - Don't try to launch new descriptor downloads quite so often when we
18882 already have enough directory information to build circuits.
18883 - Base64 decoding was actually showing up on our profile when parsing
18884 the initial descriptor file; switch to an in-process all-at-once
18885 implementation that's about 3.5x times faster than calling out to
18888 o Minor features (compilation):
18889 - Detect non-ASCII platforms (if any still exist) and refuse to
18890 build there: some of our code assumes that 'A' is 65 and so on.
18892 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
18893 - Make the "next period" votes into "current period" votes immediately
18894 after publishing the consensus; avoid a heisenbug that made them
18895 stick around indefinitely.
18896 - When we discard a vote as a duplicate, do not report this as
18898 - Treat missing v3 keys or certificates as an error when running as a
18899 v3 directory authority.
18900 - When we're configured to be a v3 authority, but we're only listed
18901 as a non-v3 authority in our DirServer line for ourself, correct
18903 - If an authority doesn't have a qualified hostname, just put
18904 its address in the vote. This fixes the problem where we referred to
18905 "moria on moria:9031."
18906 - Distinguish between detached signatures for the wrong period, and
18907 detached signatures for a divergent vote.
18908 - Fix a small memory leak when computing a consensus.
18909 - When there's no concensus, we were forming a vote every 30
18910 minutes, but writing the "valid-after" line in our vote based
18911 on our configured V3AuthVotingInterval: so unless the intervals
18912 matched up, we immediately rejected our own vote because it didn't
18913 start at the voting interval that caused us to construct a vote.
18915 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
18916 - Delete unverified-consensus when the real consensus is set.
18917 - Consider retrying a consensus networkstatus fetch immediately
18918 after one fails: don't wait 60 seconds to notice.
18919 - When fetching a consensus as a cache, wait until a newer consensus
18920 should exist before trying to replace the current one.
18921 - Use a more forgiving schedule for retrying failed consensus
18922 downloads than for other types.
18924 o Minor bugfixes (other directory issues):
18925 - Correct the implementation of "download votes by digest." Bugfix on
18927 - Authorities no longer send back "400 you're unreachable please fix
18928 it" errors to Tor servers that aren't online all the time. We're
18929 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
18931 o Minor bugfixes (controller):
18932 - Don't reset trusted dir server list when we set a configuration
18933 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
18934 - Respond to INT and TERM SIGNAL commands before we execute the
18935 signal, in case the signal shuts us down. We had a patch in
18936 0.1.2.1-alpha that tried to do this by queueing the response on
18937 the connection's buffer before shutting down, but that really
18938 isn't the same thing at all. Bug located by Matt Edman.
18940 o Minor bugfixes (misc):
18941 - Correctly check for bad options to the "PublishServerDescriptor"
18942 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
18943 - Stop leaking memory on failing case of base32_decode, and make
18944 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
18945 - Don't try to download extrainfo documents when we're trying to
18946 fetch enough directory info to build a circuit: having enough
18947 info should get priority. Bugfix on 0.2.0.x.
18948 - Don't complain that "your server has not managed to confirm that its
18949 ports are reachable" if we haven't been able to build any circuits
18950 yet. Bug found by spending four hours without a v3 consensus. Bugfix
18952 - Detect the reason for failing to mmap a descriptor file we just
18953 wrote, and give a more useful log message. Fixes bug 533. Bugfix
18956 o Code simplifications and refactoring:
18957 - Remove support for the old bw_accounting file: we've been storing
18958 bandwidth accounting information in the state file since
18959 0.1.2.5-alpha. This may result in bandwidth accounting errors
18960 if you try to upgrade from 0.1.1.x or earlier, or if you try to
18961 downgrade to 0.1.1.x or earlier.
18962 - New convenience code to locate a file within the DataDirectory.
18963 - Move non-authority functionality out of dirvote.c.
18964 - Refactor the arguments for router_pick_{directory_|trusteddir}server
18965 so that they all take the same named flags.
18968 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
18969 Unix users an easy way to script their Tor process (e.g. by
18970 adjusting bandwidth based on the time of the day).
18973 Changes in version 0.2.0.8-alpha - 2007-10-12
18974 This eighth development snapshot fixes a crash bug that's been bothering
18975 us since February 2007, lets bridge authorities store a list of bridge
18976 descriptors they've seen, gets v3 directory voting closer to working,
18977 starts caching v3 directory consensus documents on directory mirrors,
18978 and fixes a variety of smaller issues including some minor memory leaks.
18980 o Major features (router descriptor cache):
18981 - Store routers in a file called cached-descriptors instead of in
18982 cached-routers. Initialize cached-descriptors from cached-routers
18983 if the old format is around. The new format allows us to store
18984 annotations along with descriptors.
18985 - Use annotations to record the time we received each descriptor, its
18986 source, and its purpose.
18987 - Disable the SETROUTERPURPOSE controller command: it is now
18989 - Controllers should now specify cache=no or cache=yes when using
18990 the +POSTDESCRIPTOR command.
18991 - Bridge authorities now write bridge descriptors to disk, meaning
18992 we can export them to other programs and begin distributing them
18995 o Major features (directory authorities):
18996 - When a v3 authority is missing votes or signatures, it now tries
18998 - Directory authorities track weighted fractional uptime as well as
18999 weighted mean-time-between failures. WFU is suitable for deciding
19000 whether a node is "usually up", while MTBF is suitable for deciding
19001 whether a node is "likely to stay up." We need both, because
19002 "usually up" is a good requirement for guards, while "likely to
19003 stay up" is a good requirement for long-lived connections.
19005 o Major features (v3 directory system):
19006 - Caches now download v3 network status documents as needed,
19007 and download the descriptors listed in them.
19008 - All hosts now attempt to download and keep fresh v3 authority
19009 certificates, and re-attempt after failures.
19010 - More internal-consistency checks for vote parsing.
19012 o Major bugfixes (crashes):
19013 - If a connection is shut down abruptly because of something that
19014 happened inside connection_flushed_some(), do not call
19015 connection_finished_flushing(). Should fix bug 451. Bugfix on
19018 o Major bugfixes (performance):
19019 - Fix really bad O(n^2) performance when parsing a long list of
19020 routers: Instead of searching the entire list for an "extra-info "
19021 string which usually wasn't there, once for every routerinfo
19022 we read, just scan lines forward until we find one we like.
19024 - When we add data to a write buffer in response to the data on that
19025 write buffer getting low because of a flush, do not consider the
19026 newly added data as a candidate for immediate flushing, but rather
19027 make it wait until the next round of writing. Otherwise, we flush
19028 and refill recursively, and a single greedy TLS connection can
19029 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
19031 o Minor features (v3 authority system):
19032 - Add more ways for tools to download the votes that lead to the
19034 - Send a 503 when low on bandwidth and a vote, consensus, or
19035 certificate is requested.
19036 - If-modified-since is now implemented properly for all kinds of
19037 certificate requests.
19039 o Minor bugfixes (network statuses):
19040 - Tweak the implementation of proposal 109 slightly: allow at most
19041 two Tor servers on the same IP address, except if it's the location
19042 of a directory authority, in which case allow five. Bugfix on
19045 o Minor bugfixes (controller):
19046 - When sending a status event to the controller telling it that an
19047 OR address is reachable, set the port correctly. (Previously we
19048 were reporting the dir port.) Bugfix on 0.1.2.x.
19050 o Minor bugfixes (v3 directory system):
19051 - Fix logic to look up a cert by its signing key digest. Bugfix on
19053 - Only change the reply to a vote to "OK" if it's not already
19054 set. This gets rid of annoying "400 OK" log messages, which may
19055 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
19056 - When we get a valid consensus, recompute the voting schedule.
19057 - Base the valid-after time of a vote on the consensus voting
19058 schedule, not on our preferred schedule.
19059 - Make the return values and messages from signature uploads and
19060 downloads more sensible.
19061 - Fix a memory leak when serving votes and consensus documents, and
19062 another when serving certificates.
19064 o Minor bugfixes (performance):
19065 - Use a slightly simpler string hashing algorithm (copying Python's
19066 instead of Java's) and optimize our digest hashing algorithm to take
19067 advantage of 64-bit platforms and to remove some possibly-costly
19069 - Fix a minor memory leak whenever we parse guards from our state
19070 file. Bugfix on 0.2.0.7-alpha.
19071 - Fix a minor memory leak whenever we write out a file. Bugfix on
19073 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
19074 command. Bugfix on 0.2.0.5-alpha.
19076 o Minor bugfixes (portability):
19077 - On some platforms, accept() can return a broken address. Detect
19078 this more quietly, and deal accordingly. Fixes bug 483.
19079 - Stop calling tor_strlower() on uninitialized memory in some cases.
19080 Bugfix in 0.2.0.7-alpha.
19082 o Minor bugfixes (usability):
19083 - Treat some 403 responses from directory servers as INFO rather than
19084 WARN-severity events.
19085 - It's not actually an error to find a non-pending entry in the DNS
19086 cache when canceling a pending resolve. Don't log unless stuff is
19087 fishy. Resolves bug 463.
19089 o Minor bugfixes (anonymity):
19090 - Never report that we've used more bandwidth than we're willing to
19091 relay: it leaks how much non-relay traffic we're using. Resolves
19093 - When looking for a circuit to cannibalize, consider family as well
19094 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
19095 circuit cannibalization).
19097 o Code simplifications and refactoring:
19098 - Make a bunch of functions static. Remove some dead code.
19099 - Pull out about a third of the really big routerlist.c; put it in a
19100 new module, networkstatus.c.
19101 - Merge the extra fields in local_routerstatus_t back into
19102 routerstatus_t: we used to need one routerstatus_t for each
19103 authority's opinion, plus a local_routerstatus_t for the locally
19104 computed consensus opinion. To save space, we put the locally
19105 modified fields into local_routerstatus_t, and only the common
19106 stuff into routerstatus_t. But once v3 directories are in use,
19107 clients and caches will no longer need to hold authority opinions;
19108 thus, the rationale for keeping the types separate is now gone.
19109 - Make the code used to reschedule and reattempt downloads more
19111 - Turn all 'Are we a directory server/mirror?' logic into a call to
19113 - Remove the code to generate the oldest (v1) directory format.
19114 The code has been disabled since 0.2.0.5-alpha.
19117 Changes in version 0.2.0.7-alpha - 2007-09-21
19118 This seventh development snapshot makes bridges work again, makes bridge
19119 authorities work for the first time, fixes two huge performance flaws
19120 in hidden services, and fixes a variety of minor issues.
19122 o New directory authorities:
19123 - Set up moria1 and tor26 as the first v3 directory authorities. See
19124 doc/spec/dir-spec.txt for details on the new directory design.
19126 o Major bugfixes (crashes):
19127 - Fix possible segfaults in functions called from
19128 rend_process_relay_cell(). Bugfix on 0.1.2.x.
19130 o Major bugfixes (bridges):
19131 - Fix a bug that made servers send a "404 Not found" in response to
19132 attempts to fetch their server descriptor. This caused Tor servers
19133 to take many minutes to establish reachability for their DirPort,
19134 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
19135 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
19136 users configure that and specify a bridge with an identity
19137 fingerprint, now they will lookup the bridge descriptor at the
19138 default bridge authority via a one-hop tunnel, but once circuits
19139 are established they will switch to a three-hop tunnel for later
19140 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
19142 o Major bugfixes (hidden services):
19143 - Hidden services were choosing introduction points uniquely by
19144 hexdigest, but when constructing the hidden service descriptor
19145 they merely wrote the (potentially ambiguous) nickname.
19146 - Clients now use the v2 intro format for hidden service
19147 connections: they specify their chosen rendezvous point by identity
19148 digest rather than by (potentially ambiguous) nickname. Both
19149 are bugfixes on 0.1.2.x, and they could speed up hidden service
19150 connections dramatically. Thanks to Karsten Loesing.
19152 o Minor features (security):
19153 - As a client, do not believe any server that tells us that an
19154 address maps to an internal address space.
19155 - Make it possible to enable HashedControlPassword and
19156 CookieAuthentication at the same time.
19158 o Minor features (guard nodes):
19159 - Tag every guard node in our state file with the version that
19160 we believe added it, or with our own version if we add it. This way,
19161 if a user temporarily runs an old version of Tor and then switches
19162 back to a new one, she doesn't automatically lose her guards.
19164 o Minor features (speed):
19165 - When implementing AES counter mode, update only the portions of the
19166 counter buffer that need to change, and don't keep separate
19167 network-order and host-order counters when they are the same (i.e.,
19168 on big-endian hosts.)
19170 o Minor features (controller):
19171 - Accept LF instead of CRLF on controller, since some software has a
19172 hard time generating real Internet newlines.
19173 - Add GETINFO values for the server status events
19174 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
19177 o Removed features:
19178 - Routers no longer include bandwidth-history lines in their
19179 descriptors; this information is already available in extra-info
19180 documents, and including it in router descriptors took up 60%
19181 (!) of compressed router descriptor downloads. Completes
19182 implementation of proposal 104.
19183 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
19184 and TorControl.py, as they use the old v0 controller protocol,
19185 and are obsoleted by TorFlow anyway.
19186 - Drop support for v1 rendezvous descriptors, since we never used
19187 them anyway, and the code has probably rotted by now. Based on
19188 patch from Karsten Loesing.
19189 - On OSX, stop warning the user that kqueue support in libevent is
19190 "experimental", since it seems to have worked fine for ages.
19193 - When generating information telling us how to extend to a given
19194 router, do not try to include the nickname if it is absent. Fixes
19195 bug 467. Bugfix on 0.2.0.3-alpha.
19196 - Fix a user-triggerable (but not remotely-triggerable) segfault
19197 in expand_filename(). Bugfix on 0.1.2.x.
19198 - Fix a memory leak when freeing incomplete requests from DNSPort.
19199 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
19200 - Don't try to access (or alter) the state file when running
19201 --list-fingerprint or --verify-config or --hash-password. (Resolves
19202 bug 499.) Bugfix on 0.1.2.x.
19203 - Servers used to decline to publish their DirPort if their
19204 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
19205 were below a threshold. Now they only look at BandwidthRate and
19206 RelayBandwidthRate. Bugfix on 0.1.2.x.
19207 - Remove an optimization in the AES counter-mode code that assumed
19208 that the counter never exceeded 2^68. When the counter can be set
19209 arbitrarily as an IV (as it is by Karsten's new hidden services
19210 code), this assumption no longer holds. Bugfix on 0.1.2.x.
19211 - Resume listing "AUTHORITY" flag for authorities in network status.
19212 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
19214 o Code simplifications and refactoring:
19215 - Revamp file-writing logic so we don't need to have the entire
19216 contents of a file in memory at once before we write to disk. Tor,
19218 - Turn "descriptor store" into a full-fledged type.
19219 - Move all NT services code into a separate source file.
19220 - Unify all code that computes medians, percentile elements, etc.
19221 - Get rid of a needless malloc when parsing address policies.
19224 Changes in version 0.1.2.17 - 2007-08-30
19225 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
19226 X bundles. Vidalia 0.0.14 makes authentication required for the
19227 ControlPort in the default configuration, which addresses important
19228 security risks. Everybody who uses Vidalia (or another controller)
19231 In addition, this Tor update fixes major load balancing problems with
19232 path selection, which should speed things up a lot once many people
19235 o Major bugfixes (security):
19236 - We removed support for the old (v0) control protocol. It has been
19237 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
19238 become more of a headache than it's worth.
19240 o Major bugfixes (load balancing):
19241 - When choosing nodes for non-guard positions, weight guards
19242 proportionally less, since they already have enough load. Patch
19244 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
19245 will allow fast Tor servers to get more attention.
19246 - When we're upgrading from an old Tor version, forget our current
19247 guards and pick new ones according to the new weightings. These
19248 three load balancing patches could raise effective network capacity
19249 by a factor of four. Thanks to Mike Perry for measurements.
19251 o Major bugfixes (stream expiration):
19252 - Expire not-yet-successful application streams in all cases if
19253 they've been around longer than SocksTimeout. Right now there are
19254 some cases where the stream will live forever, demanding a new
19255 circuit every 15 seconds. Fixes bug 454; reported by lodger.
19257 o Minor features (controller):
19258 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
19259 is valid before any authentication has been received. It tells
19260 a controller what kind of authentication is expected, and what
19261 protocol is spoken. Implements proposal 119.
19263 o Minor bugfixes (performance):
19264 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
19265 greatly speeding up loading cached-routers from disk on startup.
19266 - Disable sentinel-based debugging for buffer code: we squashed all
19267 the bugs that this was supposed to detect a long time ago, and now
19268 its only effect is to change our buffer sizes from nice powers of
19269 two (which platform mallocs tend to like) to values slightly over
19270 powers of two (which make some platform mallocs sad).
19272 o Minor bugfixes (misc):
19273 - If exit bandwidth ever exceeds one third of total bandwidth, then
19274 use the correct formula to weight exit nodes when choosing paths.
19275 Based on patch from Mike Perry.
19276 - Choose perfectly fairly among routers when choosing by bandwidth and
19277 weighting by fraction of bandwidth provided by exits. Previously, we
19278 would choose with only approximate fairness, and correct ourselves
19279 if we ran off the end of the list.
19280 - If we require CookieAuthentication but we fail to write the
19281 cookie file, we would warn but not exit, and end up in a state
19282 where no controller could authenticate. Now we exit.
19283 - If we require CookieAuthentication, stop generating a new cookie
19284 every time we change any piece of our config.
19285 - Refuse to start with certain directory authority keys, and
19286 encourage people using them to stop.
19287 - Terminate multi-line control events properly. Original patch
19289 - Fix a minor memory leak when we fail to find enough suitable
19290 servers to choose a circuit.
19291 - Stop leaking part of the descriptor when we run into a particularly
19292 unparseable piece of it.
19295 Changes in version 0.2.0.6-alpha - 2007-08-26
19296 This sixth development snapshot features a new Vidalia version in the
19297 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
19298 the ControlPort in the default configuration, which addresses important
19301 In addition, this snapshot fixes major load balancing problems
19302 with path selection, which should speed things up a lot once many
19303 people have upgraded. The directory authorities also use a new
19304 mean-time-between-failure approach to tracking which servers are stable,
19305 rather than just looking at the most recent uptime.
19307 o New directory authorities:
19308 - Set up Tonga as the default bridge directory authority.
19311 - Directory authorities now track servers by weighted
19312 mean-times-between-failures. When we have 4 or more days of data,
19313 use measured MTBF rather than declared uptime to decide whether
19314 to call a router Stable. Implements proposal 108.
19316 o Major bugfixes (load balancing):
19317 - When choosing nodes for non-guard positions, weight guards
19318 proportionally less, since they already have enough load. Patch
19320 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
19321 will allow fast Tor servers to get more attention.
19322 - When we're upgrading from an old Tor version, forget our current
19323 guards and pick new ones according to the new weightings. These
19324 three load balancing patches could raise effective network capacity
19325 by a factor of four. Thanks to Mike Perry for measurements.
19327 o Major bugfixes (descriptor parsing):
19328 - Handle unexpected whitespace better in malformed descriptors. Bug
19329 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
19332 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
19333 GETINFO for Torstat to use until it can switch to using extrainfos.
19334 - Optionally (if built with -DEXPORTMALLINFO) export the output
19335 of mallinfo via http, as tor/mallinfo.txt. Only accessible
19339 - Do not intermix bridge routers with controller-added
19340 routers. (Bugfix on 0.2.0.x)
19341 - Do not fail with an assert when accept() returns an unexpected
19342 address family. Addresses but does not wholly fix bug 483. (Bugfix
19344 - Let directory authorities startup even when they can't generate
19345 a descriptor immediately, e.g. because they don't know their
19347 - Stop putting the authentication cookie in a file called "0"
19348 in your working directory if you don't specify anything for the
19349 new CookieAuthFile option. Reported by Matt Edman.
19350 - Make it possible to read the PROTOCOLINFO response in a way that
19351 conforms to our control-spec. Reported by Matt Edman.
19352 - Fix a minor memory leak when we fail to find enough suitable
19353 servers to choose a circuit. Bugfix on 0.1.2.x.
19354 - Stop leaking part of the descriptor when we run into a particularly
19355 unparseable piece of it. Bugfix on 0.1.2.x.
19356 - Unmap the extrainfo cache file on exit.
19359 Changes in version 0.2.0.5-alpha - 2007-08-19
19360 This fifth development snapshot fixes compilation on Windows again;
19361 fixes an obnoxious client-side bug that slowed things down and put
19362 extra load on the network; gets us closer to using the v3 directory
19363 voting scheme; makes it easier for Tor controllers to use cookie-based
19364 authentication; and fixes a variety of other bugs.
19366 o Removed features:
19367 - Version 1 directories are no longer generated in full. Instead,
19368 authorities generate and serve "stub" v1 directories that list
19369 no servers. This will stop Tor versions 0.1.0.x and earlier from
19370 working, but (for security reasons) nobody should be running those
19373 o Major bugfixes (compilation, 0.2.0.x):
19374 - Try to fix Win32 compilation again: improve checking for IPv6 types.
19375 - Try to fix MSVC compilation: build correctly on platforms that do
19376 not define s6_addr16 or s6_addr32.
19377 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
19380 o Major bugfixes (stream expiration):
19381 - Expire not-yet-successful application streams in all cases if
19382 they've been around longer than SocksTimeout. Right now there are
19383 some cases where the stream will live forever, demanding a new
19384 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
19385 reported by lodger.
19387 o Minor features (directory servers):
19388 - When somebody requests a list of statuses or servers, and we have
19389 none of those, return a 404 rather than an empty 200.
19391 o Minor features (directory voting):
19392 - Store v3 consensus status consensuses on disk, and reload them
19395 o Minor features (security):
19396 - Warn about unsafe ControlPort configurations.
19397 - Refuse to start with certain directory authority keys, and
19398 encourage people using them to stop.
19400 o Minor features (controller):
19401 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
19402 is valid before any authentication has been received. It tells
19403 a controller what kind of authentication is expected, and what
19404 protocol is spoken. Implements proposal 119.
19405 - New config option CookieAuthFile to choose a new location for the
19406 cookie authentication file, and config option
19407 CookieAuthFileGroupReadable to make it group-readable.
19409 o Minor features (unit testing):
19410 - Add command-line arguments to unit-test executable so that we can
19411 invoke any chosen test from the command line rather than having
19412 to run the whole test suite at once; and so that we can turn on
19413 logging for the unit tests.
19415 o Minor bugfixes (on 0.1.2.x):
19416 - If we require CookieAuthentication but we fail to write the
19417 cookie file, we would warn but not exit, and end up in a state
19418 where no controller could authenticate. Now we exit.
19419 - If we require CookieAuthentication, stop generating a new cookie
19420 every time we change any piece of our config.
19421 - When loading bandwidth history, do not believe any information in
19422 the future. Fixes bug 434.
19423 - When loading entry guard information, do not believe any information
19425 - When we have our clock set far in the future and generate an
19426 onion key, then re-set our clock to be correct, we should not stop
19427 the onion key from getting rotated.
19428 - Clean up torrc sample config file.
19429 - Do not automatically run configure from autogen.sh. This
19430 non-standard behavior tended to annoy people who have built other
19433 o Minor bugfixes (on 0.2.0.x):
19434 - Fix a bug with AutomapHostsOnResolve that would always cause
19435 the second request to fail. Bug reported by Kate. Bugfix on
19437 - Fix a bug in ADDRMAP controller replies that would sometimes
19438 try to print a NULL. Patch from tup.
19439 - Read v3 directory authority keys from the right location.
19440 - Numerous bugfixes to directory voting code.
19443 Changes in version 0.1.2.16 - 2007-08-01
19444 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
19445 remote attacker in certain situations to rewrite the user's torrc
19446 configuration file. This can completely compromise anonymity of users
19447 in most configurations, including those running the Vidalia bundles,
19448 TorK, etc. Or worse.
19450 o Major security fixes:
19451 - Close immediately after missing authentication on control port;
19452 do not allow multiple authentication attempts.
19455 Changes in version 0.2.0.4-alpha - 2007-08-01
19456 This fourth development snapshot fixes a critical security vulnerability
19457 for most users, specifically those running Vidalia, TorK, etc. Everybody
19458 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
19460 o Major security fixes:
19461 - Close immediately after missing authentication on control port;
19462 do not allow multiple authentication attempts.
19464 o Major bugfixes (compilation):
19465 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
19468 o Minor features (performance):
19469 - Be even more aggressive about releasing RAM from small
19470 empty buffers. Thanks to our free-list code, this shouldn't be too
19471 performance-intensive.
19472 - Disable sentinel-based debugging for buffer code: we squashed all
19473 the bugs that this was supposed to detect a long time ago, and
19474 now its only effect is to change our buffer sizes from nice
19475 powers of two (which platform mallocs tend to like) to values
19476 slightly over powers of two (which make some platform mallocs sad).
19477 - Log malloc statistics from mallinfo() on platforms where it
19481 Changes in version 0.2.0.3-alpha - 2007-07-29
19482 This third development snapshot introduces new experimental
19483 blocking-resistance features and a preliminary version of the v3
19484 directory voting design, and includes many other smaller features
19488 - The first pieces of our "bridge" design for blocking-resistance
19489 are implemented. People can run bridge directory authorities;
19490 people can run bridges; and people can configure their Tor clients
19491 with a set of bridges to use as the first hop into the Tor network.
19492 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
19494 - Create listener connections before we setuid to the configured
19495 User and Group. Now non-Windows users can choose port values
19496 under 1024, start Tor as root, and have Tor bind those ports
19497 before it changes to another UID. (Windows users could already
19499 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
19500 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
19501 on "vserver" accounts. (Patch from coderman.)
19502 - Be even more aggressive about separating local traffic from relayed
19503 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
19505 o Major features (experimental):
19506 - First cut of code for "v3 dir voting": directory authorities will
19507 vote on a common network status document rather than each publishing
19508 their own opinion. This code needs more testing and more corner-case
19509 handling before it's ready for use.
19512 - Directory authorities now call routers Fast if their bandwidth is
19513 at least 100KB/s, and consider their bandwidth adequate to be a
19514 Guard if it is at least 250KB/s, no matter the medians. This fix
19515 complements proposal 107. [Bugfix on 0.1.2.x]
19516 - Directory authorities now never mark more than 3 servers per IP as
19517 Valid and Running. (Implements proposal 109, by Kevin Bauer and
19519 - Minor change to organizationName and commonName generation
19520 procedures in TLS certificates during Tor handshakes, to invalidate
19521 some earlier censorware approaches. This is not a long-term
19522 solution, but applying it will give us a bit of time to look into
19523 the epidemiology of countermeasures as they spread.
19525 o Major bugfixes (directory):
19526 - Rewrite directory tokenization code to never run off the end of
19527 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
19529 o Minor features (controller):
19530 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
19531 match requests to applications. (Patch from Robert Hogan.)
19532 - Report address and port correctly on connections to DNSPort. (Patch
19533 from Robert Hogan.)
19534 - Add a RESOLVE command to launch hostname lookups. (Original patch
19535 from Robert Hogan.)
19536 - Add GETINFO status/enough-dir-info to let controllers tell whether
19537 Tor has downloaded sufficient directory information. (Patch
19539 - You can now use the ControlSocket option to tell Tor to listen for
19540 controller connections on Unix domain sockets on systems that
19541 support them. (Patch from Peter Palfrader.)
19542 - STREAM NEW events are generated for DNSPort requests and for
19543 tunneled directory connections. (Patch from Robert Hogan.)
19544 - New "GETINFO address-mappings/*" command to get address mappings
19545 with expiry information. "addr-mappings/*" is now deprecated.
19548 o Minor features (misc):
19549 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
19551 - The tor-gencert tool for v3 directory authorities now creates all
19552 files as readable to the file creator only, and write-protects
19553 the authority identity key.
19554 - When dumping memory usage, list bytes used in buffer memory
19556 - When running with dmalloc, dump more stats on hup and on exit.
19557 - Directory authorities now fail quickly and (relatively) harmlessly
19558 if they generate a network status document that is somehow
19561 o Traffic load balancing improvements:
19562 - If exit bandwidth ever exceeds one third of total bandwidth, then
19563 use the correct formula to weight exit nodes when choosing paths.
19564 (Based on patch from Mike Perry.)
19565 - Choose perfectly fairly among routers when choosing by bandwidth and
19566 weighting by fraction of bandwidth provided by exits. Previously, we
19567 would choose with only approximate fairness, and correct ourselves
19568 if we ran off the end of the list. [Bugfix on 0.1.2.x]
19570 o Performance improvements:
19571 - Be more aggressive with freeing buffer RAM or putting it on the
19573 - Use Critical Sections rather than Mutexes for synchronizing threads
19574 on win32; Mutexes are heavier-weight, and designed for synchronizing
19577 o Deprecated and removed features:
19578 - RedirectExits is now deprecated.
19579 - Stop allowing address masks that do not correspond to bit prefixes.
19580 We have warned about these for a really long time; now it's time
19581 to reject them. (Patch from croup.)
19583 o Minor bugfixes (directory):
19584 - Fix another crash bug related to extra-info caching. (Bug found by
19585 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
19586 - Directories no longer return a "304 not modified" when they don't
19587 have the networkstatus the client asked for. Also fix a memory
19588 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
19589 - We had accidentally labelled 0.1.2.x directory servers as not
19590 suitable for begin_dir requests, and had labelled no directory
19591 servers as suitable for uploading extra-info documents. [Bugfix
19594 o Minor bugfixes (dns):
19595 - Fix a crash when DNSPort is set more than once. (Patch from Robert
19596 Hogan.) [Bugfix on 0.2.0.2-alpha]
19597 - Add DNSPort connections to the global connection list, so that we
19598 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
19600 - Fix a dangling reference that could lead to a crash when DNSPort is
19601 changed or closed (Patch from Robert Hogan.) [Bugfix on
19604 o Minor bugfixes (controller):
19605 - Provide DNS expiry times in GMT, not in local time. For backward
19606 compatibility, ADDRMAP events only provide GMT expiry in an extended
19607 field. "GETINFO address-mappings" always does the right thing.
19608 - Use CRLF line endings properly in NS events.
19609 - Terminate multi-line control events properly. (Original patch
19610 from tup.) [Bugfix on 0.1.2.x-alpha]
19611 - Do not include spaces in SOURCE_ADDR fields in STREAM
19612 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
19615 Changes in version 0.1.2.15 - 2007-07-17
19616 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
19617 problems, fixes compilation on BSD, and fixes a variety of other
19618 bugs. Everybody should upgrade.
19620 o Major bugfixes (compilation):
19621 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
19623 o Major bugfixes (crashes):
19624 - Try even harder not to dereference the first character after
19625 an mmap(). Reported by lodger.
19626 - Fix a crash bug in directory authorities when we re-number the
19627 routerlist while inserting a new router.
19628 - When the cached-routers file is an even multiple of the page size,
19629 don't run off the end and crash. (Fixes bug 455; based on idea
19631 - Fix eventdns.c behavior on Solaris: It is critical to include
19632 orconfig.h _before_ sys/types.h, so that we can get the expected
19633 definition of _FILE_OFFSET_BITS.
19635 o Major bugfixes (security):
19636 - Fix a possible buffer overrun when using BSD natd support. Bug
19638 - When sending destroy cells from a circuit's origin, don't include
19639 the reason for tearing down the circuit. The spec says we didn't,
19640 and now we actually don't. Reported by lodger.
19641 - Keep streamids from different exits on a circuit separate. This
19642 bug may have allowed other routers on a given circuit to inject
19643 cells into streams. Reported by lodger; fixes bug 446.
19644 - If there's a never-before-connected-to guard node in our list,
19645 never choose any guards past it. This way we don't expand our
19646 guard list unless we need to.
19648 o Minor bugfixes (guard nodes):
19649 - Weight guard selection by bandwidth, so that low-bandwidth nodes
19650 don't get overused as guards.
19652 o Minor bugfixes (directory):
19653 - Correctly count the number of authorities that recommend each
19654 version. Previously, we were under-counting by 1.
19655 - Fix a potential crash bug when we load many server descriptors at
19656 once and some of them make others of them obsolete. Fixes bug 458.
19658 o Minor bugfixes (hidden services):
19659 - Stop tearing down the whole circuit when the user asks for a
19660 connection to a port that the hidden service didn't configure.
19663 o Minor bugfixes (misc):
19664 - On Windows, we were preventing other processes from reading
19665 cached-routers while Tor was running. Reported by janbar.
19666 - Fix a possible (but very unlikely) bug in picking routers by
19667 bandwidth. Add a log message to confirm that it is in fact
19668 unlikely. Patch from lodger.
19669 - Backport a couple of memory leak fixes.
19670 - Backport miscellaneous cosmetic bugfixes.
19673 Changes in version 0.2.0.2-alpha - 2007-06-02
19674 o Major bugfixes on 0.2.0.1-alpha:
19675 - Fix an assertion failure related to servers without extra-info digests.
19676 Resolves bugs 441 and 442.
19678 o Minor features (directory):
19679 - Support "If-Modified-Since" when answering HTTP requests for
19680 directories, running-routers documents, and network-status documents.
19681 (There's no need to support it for router descriptors, since those
19682 are downloaded by descriptor digest.)
19684 o Minor build issues:
19685 - Clear up some MIPSPro compiler warnings.
19686 - When building from a tarball on a machine that happens to have SVK
19687 installed, report the micro-revision as whatever version existed
19688 in the tarball, not as "x".
19691 Changes in version 0.2.0.1-alpha - 2007-06-01
19692 This early development snapshot provides new features for people running
19693 Tor as both a client and a server (check out the new RelayBandwidth
19694 config options); lets Tor run as a DNS proxy; and generally moves us
19695 forward on a lot of fronts.
19697 o Major features, server usability:
19698 - New config options RelayBandwidthRate and RelayBandwidthBurst:
19699 a separate set of token buckets for relayed traffic. Right now
19700 relayed traffic is defined as answers to directory requests, and
19701 OR connections that don't have any local circuits on them.
19703 o Major features, client usability:
19704 - A client-side DNS proxy feature to replace the need for
19705 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
19706 for DNS requests on port 9999, use the Tor network to resolve them
19707 anonymously, and send the reply back like a regular DNS server.
19708 The code still only implements a subset of DNS.
19709 - Make PreferTunneledDirConns and TunnelDirConns work even when
19710 we have no cached directory info. This means Tor clients can now
19711 do all of their connections protected by TLS.
19713 o Major features, performance and efficiency:
19714 - Directory authorities accept and serve "extra info" documents for
19715 routers. These documents contain fields from router descriptors
19716 that aren't usually needed, and that use a lot of excess
19717 bandwidth. Once these fields are removed from router descriptors,
19718 the bandwidth savings should be about 60%. [Partially implements
19720 - Servers upload extra-info documents to any authority that accepts
19721 them. Authorities (and caches that have been configured to download
19722 extra-info documents) download them as needed. [Partially implements
19724 - Change the way that Tor buffers data that it is waiting to write.
19725 Instead of queueing data cells in an enormous ring buffer for each
19726 client->OR or OR->OR connection, we now queue cells on a separate
19727 queue for each circuit. This lets us use less slack memory, and
19728 will eventually let us be smarter about prioritizing different kinds
19730 - Use memory pools to allocate cells with better speed and memory
19731 efficiency, especially on platforms where malloc() is inefficient.
19732 - Stop reading on edge connections when their corresponding circuit
19733 buffers are full; start again as the circuits empty out.
19735 o Major features, other:
19736 - Add an HSAuthorityRecordStats option that hidden service authorities
19737 can use to track statistics of overall hidden service usage without
19738 logging information that would be very useful to an attacker.
19739 - Start work implementing multi-level keys for directory authorities:
19740 Add a standalone tool to generate key certificates. (Proposal 103.)
19743 - Directory authorities now call routers Stable if they have an
19744 uptime of at least 30 days, even if that's not the median uptime
19745 in the network. Implements proposal 107, suggested by Kevin Bauer
19748 o Minor fixes (resource management):
19749 - Count the number of open sockets separately from the number
19750 of active connection_t objects. This will let us avoid underusing
19751 our allocated connection limit.
19752 - We no longer use socket pairs to link an edge connection to an
19753 anonymous directory connection or a DirPort test connection.
19754 Instead, we track the link internally and transfer the data
19755 in-process. This saves two sockets per "linked" connection (at the
19756 client and at the server), and avoids the nasty Windows socketpair()
19758 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
19759 for every single inactive connection_t. Free items from the
19760 4k/16k-buffer free lists when they haven't been used for a while.
19762 o Minor features (build):
19763 - Make autoconf search for libevent, openssl, and zlib consistently.
19764 - Update deprecated macros in configure.in.
19765 - When warning about missing headers, tell the user to let us
19766 know if the compile succeeds anyway, so we can downgrade the
19768 - Include the current subversion revision as part of the version
19769 string: either fetch it directly if we're in an SVN checkout, do
19770 some magic to guess it if we're in an SVK checkout, or use
19771 the last-detected version if we're building from a .tar.gz.
19772 Use this version consistently in log messages.
19774 o Minor features (logging):
19775 - Always prepend "Bug: " to any log message about a bug.
19776 - Put a platform string (e.g. "Linux i686") in the startup log
19777 message, so when people paste just their logs, we know if it's
19778 OpenBSD or Windows or what.
19779 - When logging memory usage, break down memory used in buffers by
19782 o Minor features (directory system):
19783 - New config option V2AuthoritativeDirectory that all directory
19784 authorities should set. This will let future authorities choose
19785 not to serve V2 directory information.
19786 - Directory authorities allow multiple router descriptors and/or extra
19787 info documents to be uploaded in a single go. This will make
19788 implementing proposal 104 simpler.
19790 o Minor features (controller):
19791 - Add a new config option __DisablePredictedCircuits designed for
19792 use by the controller, when we don't want Tor to build any circuits
19794 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
19795 so we can exit from the middle of the circuit.
19796 - Implement "getinfo status/circuit-established".
19797 - Implement "getinfo status/version/..." so a controller can tell
19798 whether the current version is recommended, and whether any versions
19799 are good, and how many authorities agree. (Patch from shibz.)
19801 o Minor features (hidden services):
19802 - Allow multiple HiddenServicePort directives with the same virtual
19803 port; when they occur, the user is sent round-robin to one
19804 of the target ports chosen at random. Partially fixes bug 393 by
19805 adding limited ad-hoc round-robining.
19807 o Minor features (other):
19809 - Add a new AutomapHostsOnResolve option: when it is enabled, any
19810 resolve request for hosts matching a given pattern causes Tor to
19811 generate an internal virtual address mapping for that host. This
19812 allows DNSPort to work sensibly with hidden service users. By
19813 default, .exit and .onion addresses are remapped; the list of
19814 patterns can be reconfigured with AutomapHostsSuffixes.
19815 - Add an "-F" option to tor-resolve to force a resolve for a .onion
19816 address. Thanks to the AutomapHostsOnResolve option, this is no
19817 longer a completely silly thing to do.
19818 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
19819 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
19820 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
19821 minus 1 byte: the actual maximum declared bandwidth.
19823 o Removed features:
19824 - Removed support for the old binary "version 0" controller protocol.
19825 This has been deprecated since 0.1.1, and warnings have been issued
19826 since 0.1.2. When we encounter a v0 control message, we now send
19827 back an error and close the connection.
19828 - Remove the old "dns worker" server DNS code: it hasn't been default
19829 since 0.1.2.2-alpha, and all the servers seem to be using the new
19832 o Minor bugfixes (portability):
19833 - Even though Windows is equally happy with / and \ as path separators,
19834 try to use \ consistently on Windows and / consistently on Unix: it
19835 makes the log messages nicer.
19836 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
19837 - Read resolv.conf files correctly on platforms where read() returns
19838 partial results on small file reads.
19840 o Minor bugfixes (directory):
19841 - Correctly enforce that elements of directory objects do not appear
19842 more often than they are allowed to appear.
19843 - When we are reporting the DirServer line we just parsed, we were
19844 logging the second stanza of the key fingerprint, not the first.
19846 o Minor bugfixes (logging):
19847 - When we hit an EOF on a log (probably because we're shutting down),
19848 don't try to remove the log from the list: just mark it as
19849 unusable. (Bulletproofs against bug 222.)
19851 o Minor bugfixes (other):
19852 - In the exitlist script, only consider the most recently published
19853 server descriptor for each server. Also, when the user requests
19854 a list of servers that _reject_ connections to a given address,
19855 explicitly exclude the IPs that also have servers that accept
19856 connections to that address. (Resolves bug 405.)
19857 - Stop allowing hibernating servers to be "stable" or "fast".
19858 - On Windows, we were preventing other processes from reading
19859 cached-routers while Tor was running. (Reported by janbar)
19860 - Make the NodeFamilies config option work. (Reported by
19861 lodger -- it has never actually worked, even though we added it
19863 - Check return values from pthread_mutex functions.
19864 - Don't save non-general-purpose router descriptors to the disk cache,
19865 because we have no way of remembering what their purpose was when
19867 - Add even more asserts to hunt down bug 417.
19868 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
19869 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
19870 Add a log message to confirm that it is in fact unlikely.
19872 o Minor bugfixes (controller):
19873 - Make 'getinfo fingerprint' return a 551 error if we're not a
19874 server, so we match what the control spec claims we do. Reported
19876 - Fix a typo in an error message when extendcircuit fails that
19877 caused us to not follow the \r\n-based delimiter protocol. Reported
19880 o Code simplifications and refactoring:
19881 - Stop passing around circuit_t and crypt_path_t pointers that are
19882 implicit in other procedure arguments.
19883 - Drop the old code to choke directory connections when the
19884 corresponding OR connections got full: thanks to the cell queue
19885 feature, OR conns don't get full any more.
19886 - Make dns_resolve() handle attaching connections to circuits
19887 properly, so the caller doesn't have to.
19888 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
19889 - Keep the connection array as a dynamic smartlist_t, rather than as
19890 a fixed-sized array. This is important, as the number of connections
19891 is becoming increasingly decoupled from the number of sockets.
19894 Changes in version 0.1.2.14 - 2007-05-25
19895 Tor 0.1.2.14 changes the addresses of two directory authorities (this
19896 change especially affects those who serve or use hidden services),
19897 and fixes several other crash- and security-related bugs.
19899 o Directory authority changes:
19900 - Two directory authorities (moria1 and moria2) just moved to new
19901 IP addresses. This change will particularly affect those who serve
19902 or use hidden services.
19904 o Major bugfixes (crashes):
19905 - If a directory server runs out of space in the connection table
19906 as it's processing a begin_dir request, it will free the exit stream
19907 but leave it attached to the circuit, leading to unpredictable
19908 behavior. (Reported by seeess, fixes bug 425.)
19909 - Fix a bug in dirserv_remove_invalid() that would cause authorities
19910 to corrupt memory under some really unlikely scenarios.
19911 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
19912 - Avoid segfaults when reading from mmaped descriptor file. (Reported
19915 o Major bugfixes (security):
19916 - When choosing an entry guard for a circuit, avoid using guards
19917 that are in the same family as the chosen exit -- not just guards
19918 that are exactly the chosen exit. (Reported by lodger.)
19920 o Major bugfixes (resource management):
19921 - If a directory authority is down, skip it when deciding where to get
19922 networkstatus objects or descriptors. Otherwise we keep asking
19923 every 10 seconds forever. Fixes bug 384.
19924 - Count it as a failure if we fetch a valid network-status but we
19925 don't want to keep it. Otherwise we'll keep fetching it and keep
19926 not wanting to keep it. Fixes part of bug 422.
19927 - If all of our dirservers have given us bad or no networkstatuses
19928 lately, then stop hammering them once per minute even when we
19929 think they're failed. Fixes another part of bug 422.
19932 - Actually set the purpose correctly for descriptors inserted with
19933 purpose=controller.
19934 - When we have k non-v2 authorities in our DirServer config,
19935 we ignored the last k authorities in the list when updating our
19937 - Correctly back-off from requesting router descriptors that we are
19938 having a hard time downloading.
19939 - Read resolv.conf files correctly on platforms where read() returns
19940 partial results on small file reads.
19941 - Don't rebuild the entire router store every time we get 32K of
19942 routers: rebuild it when the journal gets very large, or when
19943 the gaps in the store get very large.
19946 - When routers publish SVN revisions in their router descriptors,
19947 authorities now include those versions correctly in networkstatus
19949 - Warn when using a version of libevent before 1.3b to run a server on
19950 OSX or BSD: these versions interact badly with userspace threads.
19953 Changes in version 0.1.2.13 - 2007-04-24
19954 This release features some major anonymity fixes, such as safer path
19955 selection; better client performance; faster bootstrapping, better
19956 address detection, and better DNS support for servers; write limiting as
19957 well as read limiting to make servers easier to run; and a huge pile of
19958 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
19960 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
19961 of the Freenode IRC network, remembering his patience and vision for
19962 free speech on the Internet.
19965 - Fix a memory leak when we ask for "all" networkstatuses and we
19966 get one we don't recognize.
19967 - Add more asserts to hunt down bug 417.
19968 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
19971 Changes in version 0.1.2.12-rc - 2007-03-16
19973 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
19974 directory information requested inside Tor connections (i.e. via
19975 begin_dir cells). It only triggered when the same connection was
19976 serving other data at the same time. Reported by seeess.
19979 - When creating a circuit via the controller, send a 'launched'
19980 event when we're done, so we follow the spec better.
19983 Changes in version 0.1.2.11-rc - 2007-03-15
19984 o Minor bugfixes (controller), reported by daejees:
19985 - Correct the control spec to match how the code actually responds
19986 to 'getinfo addr-mappings/*'.
19987 - The control spec described a GUARDS event, but the code
19988 implemented a GUARD event. Standardize on GUARD, but let people
19989 ask for GUARDS too.
19992 Changes in version 0.1.2.10-rc - 2007-03-07
19993 o Major bugfixes (Windows):
19994 - Do not load the NT services library functions (which may not exist)
19995 just to detect if we're a service trying to shut down. Now we run
19996 on Win98 and friends again.
19998 o Minor bugfixes (other):
19999 - Clarify a couple of log messages.
20000 - Fix a misleading socks5 error number.
20003 Changes in version 0.1.2.9-rc - 2007-03-02
20004 o Major bugfixes (Windows):
20005 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
20006 of the usual GCC "%llu". This prevents a bug when saving 64-bit
20007 int configuration values: the high-order 32 bits would get
20008 truncated. In particular, we were being bitten by the default
20009 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
20010 and maybe also bug 397.)
20012 o Minor bugfixes (performance):
20013 - Use OpenSSL's AES implementation on platforms where it's faster.
20014 This could save us as much as 10% CPU usage.
20016 o Minor bugfixes (server):
20017 - Do not rotate onion key immediately after setting it for the first
20020 o Minor bugfixes (directory authorities):
20021 - Stop calling servers that have been hibernating for a long time
20022 "stable". Also, stop letting hibernating or obsolete servers affect
20023 uptime and bandwidth cutoffs.
20024 - Stop listing hibernating servers in the v1 directory.
20026 o Minor bugfixes (hidden services):
20027 - Upload hidden service descriptors slightly less often, to reduce
20028 load on authorities.
20030 o Minor bugfixes (other):
20031 - Fix an assert that could trigger if a controller quickly set then
20032 cleared EntryNodes. Bug found by Udo van den Heuvel.
20033 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
20035 - Fix a potential race condition in the rpm installer. Found by
20037 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
20038 of 2 as indicating that the server is completely bad; it sometimes
20039 means that the server is just bad for the request in question. (may fix
20040 the last of bug 326.)
20041 - Disable encrypted directory connections when we don't have a server
20042 descriptor for the destination. We'll get this working again in
20046 Changes in version 0.1.2.8-beta - 2007-02-26
20047 o Major bugfixes (crashes):
20048 - Stop crashing when the controller asks us to resetconf more than
20049 one config option at once. (Vidalia 0.0.11 does this.)
20050 - Fix a crash that happened on Win98 when we're given command-line
20051 arguments: don't try to load NT service functions from advapi32.dll
20052 except when we need them. (Bug introduced in 0.1.2.7-alpha;
20054 - Fix a longstanding obscure crash bug that could occur when
20055 we run out of DNS worker processes. (Resolves bug 390.)
20057 o Major bugfixes (hidden services):
20058 - Correctly detect whether hidden service descriptor downloads are
20059 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
20061 o Major bugfixes (accounting):
20062 - When we start during an accounting interval before it's time to wake
20063 up, remember to wake up at the correct time. (May fix bug 342.)
20065 o Minor bugfixes (controller):
20066 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
20067 clear the corresponding on_circuit variable, and remember later
20068 that we don't need to send a redundant CLOSED event. Resolves part
20070 - Report events where a resolve succeeded or where we got a socks
20071 protocol error correctly, rather than calling both of them
20073 - Change reported stream target addresses to IP consistently when
20074 we finally get the IP from an exit node.
20075 - Send log messages to the controller even if they happen to be very
20078 o Minor bugfixes (other):
20079 - Display correct results when reporting which versions are
20080 recommended, and how recommended they are. (Resolves bug 383.)
20081 - Improve our estimates for directory bandwidth to be less random:
20082 guess that an unrecognized directory will have the average bandwidth
20083 from all known directories, not that it will have the average
20084 bandwidth from those directories earlier than it on the list.
20085 - If we start a server with ClientOnly 1, then set ClientOnly to 0
20086 and hup, stop triggering an assert based on an empty onion_key.
20087 - On platforms with no working mmap() equivalent, don't warn the
20088 user when cached-routers doesn't exist.
20089 - Warn the user when mmap() [or its equivalent] fails for some reason
20090 other than file-not-found.
20091 - Don't warn the user when cached-routers.new doesn't exist: that's
20092 perfectly fine when starting up for the first time.
20093 - When EntryNodes are configured, rebuild the guard list to contain,
20094 in order: the EntryNodes that were guards before; the rest of the
20095 EntryNodes; the nodes that were guards before.
20096 - Mask out all signals in sub-threads; only the libevent signal
20097 handler should be processing them. This should prevent some crashes
20098 on some machines using pthreads. (Patch from coderman.)
20099 - Fix switched arguments on memset in the implementation of
20100 tor_munmap() for systems with no mmap() call.
20101 - When Tor receives a router descriptor that it asked for, but
20102 no longer wants (because it has received fresh networkstatuses
20103 in the meantime), do not warn the user. Cache the descriptor if
20104 we're a cache; drop it if we aren't.
20105 - Make earlier entry guards _really_ get retried when the network
20107 - On a malformed DNS reply, always give an error to the corresponding
20109 - Build with recent libevents on platforms that do not define the
20110 nonstandard types "u_int8_t" and friends.
20112 o Minor features (controller):
20113 - Warn the user when an application uses the obsolete binary v0
20114 control protocol. We're planning to remove support for it during
20115 the next development series, so it's good to give people some
20117 - Add STREAM_BW events to report per-entry-stream bandwidth
20118 use. (Patch from Robert Hogan.)
20119 - Rate-limit SIGNEWNYM signals in response to controllers that
20120 impolitely generate them for every single stream. (Patch from
20121 mwenge; closes bug 394.)
20122 - Make REMAP stream events have a SOURCE (cache or exit), and
20123 make them generated in every case where we get a successful
20124 connected or resolved cell.
20126 o Minor bugfixes (performance):
20127 - Call router_have_min_dir_info half as often. (This is showing up in
20128 some profiles, but not others.)
20129 - When using GCC, make log_debug never get called at all, and its
20130 arguments never get evaluated, when no debug logs are configured.
20131 (This is showing up in some profiles, but not others.)
20134 - Remove some never-implemented options. Mark PathlenCoinWeight as
20136 - Implement proposal 106: Stop requiring clients to have well-formed
20137 certificates; stop checking nicknames in certificates. (Clients
20138 have certificates so that they can look like Tor servers, but in
20139 the future we might want to allow them to look like regular TLS
20140 clients instead. Nicknames in certificates serve no purpose other
20141 than making our protocol easier to recognize on the wire.)
20142 - Revise messages on handshake failure again to be even more clear about
20143 which are incoming connections and which are outgoing.
20144 - Discard any v1 directory info that's over 1 month old (for
20145 directories) or over 1 week old (for running-routers lists).
20146 - Do not warn when individual nodes in the configuration's EntryNodes,
20147 ExitNodes, etc are down: warn only when all possible nodes
20148 are down. (Fixes bug 348.)
20149 - Always remove expired routers and networkstatus docs before checking
20150 whether we have enough information to build circuits. (Fixes
20152 - Put a lower-bound on MaxAdvertisedBandwidth.
20155 Changes in version 0.1.2.7-alpha - 2007-02-06
20156 o Major bugfixes (rate limiting):
20157 - Servers decline directory requests much more aggressively when
20158 they're low on bandwidth. Otherwise they end up queueing more and
20159 more directory responses, which can't be good for latency.
20160 - But never refuse directory requests from local addresses.
20161 - Fix a memory leak when sending a 503 response for a networkstatus
20163 - Be willing to read or write on local connections (e.g. controller
20164 connections) even when the global rate limiting buckets are empty.
20165 - If our system clock jumps back in time, don't publish a negative
20166 uptime in the descriptor. Also, don't let the global rate limiting
20167 buckets go absurdly negative.
20168 - Flush local controller connection buffers periodically as we're
20169 writing to them, so we avoid queueing 4+ megabytes of data before
20172 o Major bugfixes (NT services):
20173 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
20174 command-line flag so that admins can override the default by saying
20175 "tor --service install --user "SomeUser"". This will not affect
20176 existing installed services. Also, warn the user that the service
20177 will look for its configuration file in the service user's
20178 %appdata% directory. (We can't do the 'hardwire the user's appdata
20179 directory' trick any more, since we may not have read access to that
20182 o Major bugfixes (other):
20183 - Previously, we would cache up to 16 old networkstatus documents
20184 indefinitely, if they came from nontrusted authorities. Now we
20185 discard them if they are more than 10 days old.
20186 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
20188 - Detect and reject malformed DNS responses containing circular
20190 - If exits are rare enough that we're not marking exits as guards,
20191 ignore exit bandwidth when we're deciding the required bandwidth
20193 - When we're handling a directory connection tunneled over Tor,
20194 don't fill up internal memory buffers with all the data we want
20195 to tunnel; instead, only add it if the OR connection that will
20196 eventually receive it has some room for it. (This can lead to
20197 slowdowns in tunneled dir connections; a better solution will have
20198 to wait for 0.2.0.)
20200 o Minor bugfixes (dns):
20201 - Add some defensive programming to eventdns.c in an attempt to catch
20202 possible memory-stomping bugs.
20203 - Detect and reject DNS replies containing IPv4 or IPv6 records with
20204 an incorrect number of bytes. (Previously, we would ignore the
20206 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
20207 in the correct order, and doesn't crash.
20208 - Free memory held in recently-completed DNS lookup attempts on exit.
20209 This was not a memory leak, but may have been hiding memory leaks.
20210 - Handle TTL values correctly on reverse DNS lookups.
20211 - Treat failure to parse resolv.conf as an error.
20213 o Minor bugfixes (other):
20214 - Fix crash with "tor --list-fingerprint" (reported by seeess).
20215 - When computing clock skew from directory HTTP headers, consider what
20216 time it was when we finished asking for the directory, not what
20218 - Expire socks connections if they spend too long waiting for the
20219 handshake to finish. Previously we would let them sit around for
20220 days, if the connecting application didn't close them either.
20221 - And if the socks handshake hasn't started, don't send a
20222 "DNS resolve socks failed" handshake reply; just close it.
20223 - Stop using C functions that OpenBSD's linker doesn't like.
20224 - Don't launch requests for descriptors unless we have networkstatuses
20225 from at least half of the authorities. This delays the first
20226 download slightly under pathological circumstances, but can prevent
20227 us from downloading a bunch of descriptors we don't need.
20228 - Do not log IPs with TLS failures for incoming TLS
20229 connections. (Fixes bug 382.)
20230 - If the user asks to use invalid exit nodes, be willing to use
20232 - Stop using the reserved ac_cv namespace in our configure script.
20233 - Call stat() slightly less often; use fstat() when possible.
20234 - Refactor the way we handle pending circuits when an OR connection
20235 completes or fails, in an attempt to fix a rare crash bug.
20236 - Only rewrite a conn's address based on X-Forwarded-For: headers
20237 if it's a parseable public IP address; and stop adding extra quotes
20238 to the resulting address.
20241 - Weight directory requests by advertised bandwidth. Now we can
20242 let servers enable write limiting but still allow most clients to
20243 succeed at their directory requests. (We still ignore weights when
20244 choosing a directory authority; I hope this is a feature.)
20247 - Create a new file ReleaseNotes which was the old ChangeLog. The
20248 new ChangeLog file now includes the summaries for all development
20250 - Check for addresses with invalid characters at the exit as well
20251 as at the client, and warn less verbosely when they fail. You can
20252 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
20253 - Adapt a patch from goodell to let the contrib/exitlist script
20254 take arguments rather than require direct editing.
20255 - Inform the server operator when we decide not to advertise a
20256 DirPort due to AccountingMax enabled or a low BandwidthRate. It
20257 was confusing Zax, so now we're hopefully more helpful.
20258 - Bring us one step closer to being able to establish an encrypted
20259 directory tunnel without knowing a descriptor first. Still not
20260 ready yet. As part of the change, now assume we can use a
20261 create_fast cell if we don't know anything about a router.
20262 - Allow exit nodes to use nameservers running on ports other than 53.
20263 - Servers now cache reverse DNS replies.
20264 - Add an --ignore-missing-torrc command-line option so that we can
20265 get the "use sensible defaults if the configuration file doesn't
20266 exist" behavior even when specifying a torrc location on the command
20269 o Minor features (controller):
20270 - Track reasons for OR connection failure; make these reasons
20271 available via the controller interface. (Patch from Mike Perry.)
20272 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
20273 can learn when clients are sending malformed hostnames to Tor.
20274 - Clean up documentation for controller status events.
20275 - Add a REMAP status to stream events to note that a stream's
20276 address has changed because of a cached address or a MapAddress
20280 Changes in version 0.1.2.6-alpha - 2007-01-09
20282 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
20283 connection handles more than 4 gigs in either direction, we crash.
20284 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
20285 advertised exit node, somebody might try to exit from us when
20286 we're bootstrapping and before we've built our descriptor yet.
20287 Refuse the connection rather than crashing.
20290 - Warn if we (as a server) find that we've resolved an address that we
20291 weren't planning to resolve.
20292 - Warn that using select() on any libevent version before 1.1 will be
20293 unnecessarily slow (even for select()).
20294 - Flush ERR-level controller status events just like we currently
20295 flush ERR-level log events, so that a Tor shutdown doesn't prevent
20296 the controller from learning about current events.
20298 o Minor features (more controller status events):
20299 - Implement EXTERNAL_ADDRESS server status event so controllers can
20300 learn when our address changes.
20301 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
20302 can learn when directories reject our descriptor.
20303 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
20304 can learn when a client application is speaking a non-socks protocol
20306 - Implement DANGEROUS_SOCKS client status event so controllers
20307 can learn when a client application is leaking DNS addresses.
20308 - Implement BUG general status event so controllers can learn when
20309 Tor is unhappy about its internal invariants.
20310 - Implement CLOCK_SKEW general status event so controllers can learn
20311 when Tor thinks the system clock is set incorrectly.
20312 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
20313 server status events so controllers can learn when their descriptors
20314 are accepted by a directory.
20315 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
20316 server status events so controllers can learn about Tor's progress in
20317 deciding whether it's reachable from the outside.
20318 - Implement BAD_LIBEVENT general status event so controllers can learn
20319 when we have a version/method combination in libevent that needs to
20321 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
20322 and DNS_USELESS server status events so controllers can learn
20323 about changes to DNS server status.
20325 o Minor features (directory):
20326 - Authorities no longer recommend exits as guards if this would shift
20327 too much load to the exit nodes.
20330 Changes in version 0.1.2.5-alpha - 2007-01-06
20332 - Enable write limiting as well as read limiting. Now we sacrifice
20333 capacity if we're pushing out lots of directory traffic, rather
20334 than overrunning the user's intended bandwidth limits.
20335 - Include TLS overhead when counting bandwidth usage; previously, we
20336 would count only the bytes sent over TLS, but not the bytes used
20338 - Support running the Tor service with a torrc not in the same
20339 directory as tor.exe and default to using the torrc located in
20340 the %appdata%\Tor\ of the user who installed the service. Patch
20342 - Servers now check for the case when common DNS requests are going to
20343 wildcarded addresses (i.e. all getting the same answer), and change
20344 their exit policy to reject *:* if it's happening.
20345 - Implement BEGIN_DIR cells, so we can connect to the directory
20346 server via TLS to do encrypted directory requests rather than
20347 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
20348 config options if you like.
20350 o Minor features (config and docs):
20351 - Start using the state file to store bandwidth accounting data:
20352 the bw_accounting file is now obsolete. We'll keep generating it
20353 for a while for people who are still using 0.1.2.4-alpha.
20354 - Try to batch changes to the state file so that we do as few
20355 disk writes as possible while still storing important things in
20357 - The state file and the bw_accounting file get saved less often when
20358 the AvoidDiskWrites config option is set.
20359 - Make PIDFile work on Windows (untested).
20360 - Add internal descriptions for a bunch of configuration options:
20361 accessible via controller interface and in comments in saved
20363 - Reject *:563 (NNTPS) in the default exit policy. We already reject
20364 NNTP by default, so this seems like a sensible addition.
20365 - Clients now reject hostnames with invalid characters. This should
20366 avoid some inadvertent info leaks. Add an option
20367 AllowNonRFC953Hostnames to disable this behavior, in case somebody
20368 is running a private network with hosts called @, !, and #.
20369 - Add a maintainer script to tell us which options are missing
20370 documentation: "make check-docs".
20371 - Add a new address-spec.txt document to describe our special-case
20372 addresses: .exit, .onion, and .noconnnect.
20374 o Minor features (DNS):
20375 - Ongoing work on eventdns infrastructure: now it has dns server
20376 and ipv6 support. One day Tor will make use of it.
20377 - Add client-side caching for reverse DNS lookups.
20378 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
20379 - When we change nameservers or IP addresses, reset and re-launch
20380 our tests for DNS hijacking.
20382 o Minor features (directory):
20383 - Authorities now specify server versions in networkstatus. This adds
20384 about 2% to the size of compressed networkstatus docs, and allows
20385 clients to tell which servers support BEGIN_DIR and which don't.
20386 The implementation is forward-compatible with a proposed future
20387 protocol version scheme not tied to Tor versions.
20388 - DirServer configuration lines now have an orport= option so
20389 clients can open encrypted tunnels to the authorities without
20390 having downloaded their descriptors yet. Enabled for moria1,
20391 moria2, tor26, and lefkada now in the default configuration.
20392 - Directory servers are more willing to send a 503 "busy" if they
20393 are near their write limit, especially for v1 directory requests.
20394 Now they can use their limited bandwidth for actual Tor traffic.
20395 - Clients track responses with status 503 from dirservers. After a
20396 dirserver has given us a 503, we try not to use it until an hour has
20397 gone by, or until we have no dirservers that haven't given us a 503.
20398 - When we get a 503 from a directory, and we're not a server, we don't
20399 count the failure against the total number of failures allowed
20400 for the thing we're trying to download.
20401 - Report X-Your-Address-Is correctly from tunneled directory
20402 connections; don't report X-Your-Address-Is when it's an internal
20403 address; and never believe reported remote addresses when they're
20405 - Protect against an unlikely DoS attack on directory servers.
20406 - Add a BadDirectory flag to network status docs so that authorities
20407 can (eventually) tell clients about caches they believe to be
20410 o Minor features (controller):
20411 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
20412 - Reimplement GETINFO so that info/names stays in sync with the
20414 - Implement "GETINFO fingerprint".
20415 - Implement "SETEVENTS GUARD" so controllers can get updates on
20416 entry guard status as it changes.
20418 o Minor features (clean up obsolete pieces):
20419 - Remove some options that have been deprecated since at least
20420 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
20421 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
20422 to set log options.
20423 - We no longer look for identity and onion keys in "identity.key" and
20424 "onion.key" -- these were replaced by secret_id_key and
20425 secret_onion_key in 0.0.8pre1.
20426 - We no longer require unrecognized directory entries to be
20429 o Major bugfixes (security):
20430 - Stop sending the HttpProxyAuthenticator string to directory
20431 servers when directory connections are tunnelled through Tor.
20432 - Clients no longer store bandwidth history in the state file.
20433 - Do not log introduction points for hidden services if SafeLogging
20435 - When generating bandwidth history, round down to the nearest
20436 1k. When storing accounting data, round up to the nearest 1k.
20437 - When we're running as a server, remember when we last rotated onion
20438 keys, so that we will rotate keys once they're a week old even if
20439 we never stay up for a week ourselves.
20441 o Major bugfixes (other):
20442 - Fix a longstanding bug in eventdns that prevented the count of
20443 timed-out resolves from ever being reset. This bug caused us to
20444 give up on a nameserver the third time it timed out, and try it
20445 10 seconds later... and to give up on it every time it timed out
20447 - Take out the '5 second' timeout from the connection retry
20448 schedule. Now the first connect attempt will wait a full 10
20449 seconds before switching to a new circuit. Perhaps this will help
20450 a lot. Based on observations from Mike Perry.
20451 - Fix a bug on the Windows implementation of tor_mmap_file() that
20452 would prevent the cached-routers file from ever loading. Reported
20456 - Fix an assert failure when a directory authority sets
20457 AuthDirRejectUnlisted and then receives a descriptor from an
20458 unlisted router. Reported by seeess.
20459 - Avoid a double-free when parsing malformed DirServer lines.
20460 - Fix a bug when a BSD-style PF socket is first used. Patch from
20462 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
20463 to resolve an address at a given exit node even when they ask for
20465 - Servers no longer ever list themselves in their "family" line,
20466 even if configured to do so. This makes it easier to configure
20467 family lists conveniently.
20468 - When running as a server, don't fall back to 127.0.0.1 when no
20469 nameservers are configured in /etc/resolv.conf; instead, make the
20470 user fix resolv.conf or specify nameservers explicitly. (Resolves
20472 - Stop accepting certain malformed ports in configured exit policies.
20473 - Don't re-write the fingerprint file every restart, unless it has
20475 - Stop warning when a single nameserver fails: only warn when _all_ of
20476 our nameservers have failed. Also, when we only have one nameserver,
20477 raise the threshold for deciding that the nameserver is dead.
20478 - Directory authorities now only decide that routers are reachable
20479 if their identity keys are as expected.
20480 - When the user uses bad syntax in the Log config line, stop
20481 suggesting other bad syntax as a replacement.
20482 - Correctly detect ipv6 DNS capability on OpenBSD.
20484 o Minor bugfixes (controller):
20485 - Report the circuit number correctly in STREAM CLOSED events. Bug
20486 reported by Mike Perry.
20487 - Do not report bizarre values for results of accounting GETINFOs
20488 when the last second's write or read exceeds the allotted bandwidth.
20489 - Report "unrecognized key" rather than an empty string when the
20490 controller tries to fetch a networkstatus that doesn't exist.
20493 Changes in version 0.1.1.26 - 2006-12-14
20494 o Security bugfixes:
20495 - Stop sending the HttpProxyAuthenticator string to directory
20496 servers when directory connections are tunnelled through Tor.
20497 - Clients no longer store bandwidth history in the state file.
20498 - Do not log introduction points for hidden services if SafeLogging
20502 - Fix an assert failure when a directory authority sets
20503 AuthDirRejectUnlisted and then receives a descriptor from an
20504 unlisted router (reported by seeess).
20507 Changes in version 0.1.2.4-alpha - 2006-12-03
20509 - Add support for using natd; this allows FreeBSDs earlier than
20510 5.1.2 to have ipfw send connections through Tor without using
20511 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
20514 - Make all connections to addresses of the form ".noconnect"
20515 immediately get closed. This lets application/controller combos
20516 successfully test whether they're talking to the same Tor by
20517 watching for STREAM events.
20518 - Make cross.sh cross-compilation script work even when autogen.sh
20519 hasn't been run. (Patch from Michael Mohr.)
20520 - Statistics dumped by -USR2 now include a breakdown of public key
20521 operations, for profiling.
20524 - Fix a major leak when directory authorities parse their
20525 approved-routers list, a minor memory leak when we fail to pick
20526 an exit node, and a few rare leaks on errors.
20527 - Handle TransPort connections even when the server sends data before
20528 the client sends data. Previously, the connection would just hang
20529 until the client sent data. (Patch from tup based on patch from
20531 - Avoid assert failure when our cached-routers file is empty on
20535 - Don't log spurious warnings when we see a circuit close reason we
20536 don't recognize; it's probably just from a newer version of Tor.
20537 - Have directory authorities allow larger amounts of drift in uptime
20538 without replacing the server descriptor: previously, a server that
20539 restarted every 30 minutes could have 48 "interesting" descriptors
20541 - Start linking to the Tor specification and Tor reference manual
20542 correctly in the Windows installer.
20543 - Add Vidalia to the OS X uninstaller script, so when we uninstall
20544 Tor/Privoxy we also uninstall Vidalia.
20545 - Resume building on Irix64, and fix a lot of warnings from its
20546 MIPSpro C compiler.
20547 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
20548 when we're running as a client.
20551 Changes in version 0.1.1.25 - 2006-11-04
20553 - When a client asks us to resolve (rather than connect to)
20554 an address, and we have a cached answer, give them the cached
20555 answer. Previously, we would give them no answer at all.
20556 - We were building exactly the wrong circuits when we predict
20557 hidden service requirements, meaning Tor would have to build all
20558 its circuits on demand.
20559 - If none of our live entry guards have a high uptime, but we
20560 require a guard with a high uptime, try adding a new guard before
20561 we give up on the requirement. This patch should make long-lived
20562 connections more stable on average.
20563 - When testing reachability of our DirPort, don't launch new
20564 tests when there's already one in progress -- unreachable
20565 servers were stacking up dozens of testing streams.
20567 o Security bugfixes:
20568 - When the user sends a NEWNYM signal, clear the client-side DNS
20569 cache too. Otherwise we continue to act on previous information.
20572 - Avoid a memory corruption bug when creating a hash table for
20574 - Avoid possibility of controller-triggered crash when misusing
20575 certain commands from a v0 controller on platforms that do not
20576 handle printf("%s",NULL) gracefully.
20577 - Avoid infinite loop on unexpected controller input.
20578 - Don't log spurious warnings when we see a circuit close reason we
20579 don't recognize; it's probably just from a newer version of Tor.
20580 - Add Vidalia to the OS X uninstaller script, so when we uninstall
20581 Tor/Privoxy we also uninstall Vidalia.
20584 Changes in version 0.1.2.3-alpha - 2006-10-29
20586 - Prepare for servers to publish descriptors less often: never
20587 discard a descriptor simply for being too old until either it is
20588 recommended by no authorities, or until we get a better one for
20589 the same router. Make caches consider retaining old recommended
20590 routers for even longer.
20591 - If most authorities set a BadExit flag for a server, clients
20592 don't think of it as a general-purpose exit. Clients only consider
20593 authorities that advertise themselves as listing bad exits.
20594 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
20595 headers for content, so that we can work better in the presence of
20596 caching HTTP proxies.
20597 - Allow authorities to list nodes as bad exits by fingerprint or by
20600 o Minor features, controller:
20601 - Add a REASON field to CIRC events; for backward compatibility, this
20602 field is sent only to controllers that have enabled the extended
20603 event format. Also, add additional reason codes to explain why
20604 a given circuit has been destroyed or truncated. (Patches from
20606 - Add a REMOTE_REASON field to extended CIRC events to tell the
20607 controller about why a remote OR told us to close a circuit.
20608 - Stream events also now have REASON and REMOTE_REASON fields,
20609 working much like those for circuit events.
20610 - There's now a GETINFO ns/... field so that controllers can ask Tor
20611 about the current status of a router.
20612 - A new event type "NS" to inform a controller when our opinion of
20613 a router's status has changed.
20614 - Add a GETINFO events/names and GETINFO features/names so controllers
20615 can tell which events and features are supported.
20616 - A new CLEARDNSCACHE signal to allow controllers to clear the
20617 client-side DNS cache without expiring circuits.
20619 o Security bugfixes:
20620 - When the user sends a NEWNYM signal, clear the client-side DNS
20621 cache too. Otherwise we continue to act on previous information.
20624 - Avoid sending junk to controllers or segfaulting when a controller
20625 uses EVENT_NEW_DESC with verbose nicknames.
20626 - Stop triggering asserts if the controller tries to extend hidden
20627 service circuits (reported by mwenge).
20628 - Avoid infinite loop on unexpected controller input.
20629 - When the controller does a "GETINFO network-status", tell it
20630 about even those routers whose descriptors are very old, and use
20631 long nicknames where appropriate.
20632 - Change NT service functions to be loaded on demand. This lets us
20633 build with MinGW without breaking Tor for Windows 98 users.
20634 - Do DirPort reachability tests less often, since a single test
20635 chews through many circuits before giving up.
20636 - In the hidden service example in torrc.sample, stop recommending
20637 esoteric and discouraged hidden service options.
20638 - When stopping an NT service, wait up to 10 sec for it to actually
20639 stop. Patch from Matt Edman; resolves bug 295.
20640 - Fix handling of verbose nicknames with ORCONN controller events:
20641 make them show up exactly when requested, rather than exactly when
20643 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
20644 printing a duplicate "$" in the keys we send (reported by mwenge).
20645 - Correctly set maximum connection limit on Cygwin. (This time
20647 - Try to detect Windows correctly when cross-compiling.
20648 - Detect the size of the routers file correctly even if it is
20649 corrupted (on systems without mmap) or not page-aligned (on systems
20650 with mmap). This bug was harmless.
20651 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
20652 to open a stream fails; now we do in more cases. This should
20653 make clients able to find a good exit faster in some cases, since
20654 unhandleable requests will now get an error rather than timing out.
20655 - Resolve two memory leaks when rebuilding the on-disk router cache
20656 (reported by fookoowa).
20657 - Clean up minor code warnings suggested by the MIPSpro C compiler,
20658 and reported by some Centos users.
20659 - Controller signals now work on non-Unix platforms that don't define
20660 SIGUSR1 and SIGUSR2 the way we expect.
20661 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
20662 values before failing, and always enables eventdns.
20663 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
20664 Try to fix this in configure.in by checking for most functions
20665 before we check for libevent.
20668 Changes in version 0.1.2.2-alpha - 2006-10-07
20670 - Make our async eventdns library on-by-default for Tor servers,
20671 and plan to deprecate the separate dnsworker threads.
20672 - Add server-side support for "reverse" DNS lookups (using PTR
20673 records so clients can determine the canonical hostname for a given
20674 IPv4 address). Only supported by servers using eventdns; servers
20675 now announce in their descriptors whether they support eventdns.
20676 - Specify and implement client-side SOCKS5 interface for reverse DNS
20677 lookups (see doc/socks-extensions.txt).
20678 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
20679 connect to directory servers through Tor. Previously, clients needed
20680 to find Tor exits to make private connections to directory servers.
20681 - Avoid choosing Exit nodes for entry or middle hops when the
20682 total bandwidth available from non-Exit nodes is much higher than
20683 the total bandwidth available from Exit nodes.
20684 - Workaround for name servers (like Earthlink's) that hijack failing
20685 DNS requests and replace the no-such-server answer with a "helpful"
20686 redirect to an advertising-driven search portal. Also work around
20687 DNS hijackers who "helpfully" decline to hijack known-invalid
20688 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
20689 lets you turn it off.
20690 - Send out a burst of long-range padding cells once we've established
20691 that we're reachable. Spread them over 4 circuits, so hopefully
20692 a few will be fast. This exercises our bandwidth and bootstraps
20693 us into the directory more quickly.
20695 o New/improved config options:
20696 - Add new config option "ResolvConf" to let the server operator
20697 choose an alternate resolve.conf file when using eventdns.
20698 - Add an "EnforceDistinctSubnets" option to control our "exclude
20699 servers on the same /16" behavior. It's still on by default; this
20700 is mostly for people who want to operate private test networks with
20701 all the machines on the same subnet.
20702 - If one of our entry guards is on the ExcludeNodes list, or the
20703 directory authorities don't think it's a good guard, treat it as
20704 if it were unlisted: stop using it as a guard, and throw it off
20705 the guards list if it stays that way for a long time.
20706 - Allow directory authorities to be marked separately as authorities
20707 for the v1 directory protocol, the v2 directory protocol, and
20708 as hidden service directories, to make it easier to retire old
20709 authorities. V1 authorities should set "HSAuthoritativeDir 1"
20710 to continue being hidden service authorities too.
20711 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
20713 o Minor features, controller:
20714 - Fix CIRC controller events so that controllers can learn the
20715 identity digests of non-Named servers used in circuit paths.
20716 - Let controllers ask for more useful identifiers for servers. Instead
20717 of learning identity digests for un-Named servers and nicknames
20718 for Named servers, the new identifiers include digest, nickname,
20719 and indication of Named status. Off by default; see control-spec.txt
20720 for more information.
20721 - Add a "getinfo address" controller command so it can display Tor's
20722 best guess to the user.
20723 - New controller event to alert the controller when our server
20724 descriptor has changed.
20725 - Give more meaningful errors on controller authentication failure.
20727 o Minor features, other:
20728 - When asked to resolve a hostname, don't use non-exit servers unless
20729 requested to do so. This allows servers with broken DNS to be
20730 useful to the network.
20731 - Divide eventdns log messages into warn and info messages.
20732 - Reserve the nickname "Unnamed" for routers that can't pick
20733 a hostname: any router can call itself Unnamed; directory
20734 authorities will never allocate Unnamed to any particular router;
20735 clients won't believe that any router is the canonical Unnamed.
20736 - Only include function names in log messages for info/debug messages.
20737 For notice/warn/err, the content of the message should be clear on
20738 its own, and printing the function name only confuses users.
20739 - Avoid some false positives during reachability testing: don't try
20740 to test via a server that's on the same /24 as us.
20741 - If we fail to build a circuit to an intended enclave, and it's
20742 not mandatory that we use that enclave, stop wanting it.
20743 - When eventdns is enabled, allow multithreaded builds on NetBSD and
20744 OpenBSD. (We had previously disabled threads on these platforms
20745 because they didn't have working thread-safe resolver functions.)
20747 o Major bugfixes, anonymity/security:
20748 - If a client asked for a server by name, and there's a named server
20749 in our network-status but we don't have its descriptor yet, we
20750 could return an unnamed server instead.
20751 - Fix NetBSD bug that could allow someone to force uninitialized RAM
20752 to be sent to a server's DNS resolver. This only affects NetBSD
20753 and other platforms that do not bounds-check tolower().
20754 - Reject (most) attempts to use Tor circuits with length one. (If
20755 many people start using Tor as a one-hop proxy, exit nodes become
20756 a more attractive target for compromise.)
20757 - Just because your DirPort is open doesn't mean people should be
20758 able to remotely teach you about hidden service descriptors. Now
20759 only accept rendezvous posts if you've got HSAuthoritativeDir set.
20761 o Major bugfixes, other:
20762 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
20763 - When a client asks the server to resolve (not connect to)
20764 an address, and it has a cached answer, give them the cached answer.
20765 Previously, the server would give them no answer at all.
20766 - Allow really slow clients to not hang up five minutes into their
20767 directory downloads (suggested by Adam J. Richter).
20768 - We were building exactly the wrong circuits when we anticipated
20769 hidden service requirements, meaning Tor would have to build all
20770 its circuits on demand.
20771 - Avoid crashing when we mmap a router cache file of size 0.
20772 - When testing reachability of our DirPort, don't launch new
20773 tests when there's already one in progress -- unreachable
20774 servers were stacking up dozens of testing streams.
20776 o Minor bugfixes, correctness:
20777 - If we're a directory mirror and we ask for "all" network status
20778 documents, we would discard status documents from authorities
20779 we don't recognize.
20780 - Avoid a memory corruption bug when creating a hash table for
20782 - Avoid controller-triggered crash when misusing certain commands
20783 from a v0 controller on platforms that do not handle
20784 printf("%s",NULL) gracefully.
20785 - Don't crash when a controller sends a third argument to an
20786 "extendcircuit" request.
20787 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
20788 response; fix error code when "getinfo dir/status/" fails.
20789 - Avoid crash when telling controller stream-status and a stream
20791 - Patch from Adam Langley to fix assert() in eventdns.c.
20792 - Fix a debug log message in eventdns to say "X resolved to Y"
20793 instead of "X resolved to X".
20794 - Make eventdns give strings for DNS errors, not just error numbers.
20795 - Track unreachable entry guards correctly: don't conflate
20796 'unreachable by us right now' with 'listed as down by the directory
20797 authorities'. With the old code, if a guard was unreachable by
20798 us but listed as running, it would clog our guard list forever.
20799 - Behave correctly in case we ever have a network with more than
20800 2GB/s total advertised capacity.
20801 - Make TrackExitHosts case-insensitive, and fix the behavior of
20802 ".suffix" TrackExitHosts items to avoid matching in the middle of
20804 - Finally fix the openssl warnings from newer gccs that believe that
20805 ignoring a return value is okay, but casting a return value and
20806 then ignoring it is a sign of madness.
20807 - Prevent the contrib/exitlist script from printing the same
20808 result more than once.
20809 - Patch from Steve Hildrey: Generate network status correctly on
20810 non-versioning dirservers.
20811 - Don't listen to the X-Your-Address-Is hint if you did the lookup
20812 via Tor; otherwise you'll think you're the exit node's IP address.
20814 o Minor bugfixes, performance:
20815 - Two small performance improvements on parsing descriptors.
20816 - Major performance improvement on inserting descriptors: change
20817 algorithm from O(n^2) to O(n).
20818 - Make the common memory allocation path faster on machines where
20819 malloc(0) returns a pointer.
20820 - Start remembering X-Your-Address-Is directory hints even if you're
20821 a client, so you can become a server more smoothly.
20822 - Avoid duplicate entries on MyFamily line in server descriptor.
20824 o Packaging, features:
20825 - Remove architecture from OS X builds. The official builds are
20826 now universal binaries.
20827 - The Debian package now uses --verify-config when (re)starting,
20828 to distinguish configuration errors from other errors.
20829 - Update RPMs to require libevent 1.1b.
20831 o Packaging, bugfixes:
20832 - Patches so Tor builds with MinGW on Windows.
20833 - Patches so Tor might run on Cygwin again.
20834 - Resume building on non-gcc compilers and ancient gcc. Resume
20835 building with the -O0 compile flag. Resume building cleanly on
20837 - Run correctly on OS X platforms with case-sensitive filesystems.
20838 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
20839 - Add autoconf checks so Tor can build on Solaris x86 again.
20842 - Documented (and renamed) ServerDNSSearchDomains and
20843 ServerDNSResolvConfFile options.
20844 - Be clearer that the *ListenAddress directives can be repeated
20848 Changes in version 0.1.1.24 - 2006-09-29
20850 - Allow really slow clients to not hang up five minutes into their
20851 directory downloads (suggested by Adam J. Richter).
20852 - Fix major performance regression from 0.1.0.x: instead of checking
20853 whether we have enough directory information every time we want to
20854 do something, only check when the directory information has changed.
20855 This should improve client CPU usage by 25-50%.
20856 - Don't crash if, after a server has been running for a while,
20857 it can't resolve its hostname.
20860 - Allow Tor to start when RunAsDaemon is set but no logs are set.
20861 - Don't crash when the controller receives a third argument to an
20862 "extendcircuit" request.
20863 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
20864 response; fix error code when "getinfo dir/status/" fails.
20865 - Fix configure.in to not produce broken configure files with
20866 more recent versions of autoconf. Thanks to Clint for his auto*
20868 - Fix security bug on NetBSD that could allow someone to force
20869 uninitialized RAM to be sent to a server's DNS resolver. This
20870 only affects NetBSD and other platforms that do not bounds-check
20872 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
20873 methods: these are known to be buggy.
20874 - If we're a directory mirror and we ask for "all" network status
20875 documents, we would discard status documents from authorities
20876 we don't recognize.
20879 Changes in version 0.1.2.1-alpha - 2006-08-27
20881 - Add "eventdns" async dns library from Adam Langley, tweaked to
20882 build on OSX and Windows. Only enabled if you pass the
20883 --enable-eventdns argument to configure.
20884 - Allow servers with no hostname or IP address to learn their
20885 IP address by asking the directory authorities. This code only
20886 kicks in when you would normally have exited with a "no address"
20887 error. Nothing's authenticated, so use with care.
20888 - Rather than waiting a fixed amount of time between retrying
20889 application connections, we wait only 5 seconds for the first,
20890 10 seconds for the second, and 15 seconds for each retry after
20891 that. Hopefully this will improve the expected user experience.
20892 - Patch from Tup to add support for transparent AP connections:
20893 this basically bundles the functionality of trans-proxy-tor
20894 into the Tor mainline. Now hosts with compliant pf/netfilter
20895 implementations can redirect TCP connections straight to Tor
20896 without diverting through SOCKS. Needs docs.
20897 - Busy directory servers save lots of memory by spooling server
20898 descriptors, v1 directories, and v2 networkstatus docs to buffers
20899 as needed rather than en masse. Also mmap the cached-routers
20900 files, so we don't need to keep the whole thing in memory too.
20901 - Automatically avoid picking more than one node from the same
20902 /16 network when constructing a circuit.
20903 - Revise and clean up the torrc.sample that we ship with; add
20904 a section for BandwidthRate and BandwidthBurst.
20907 - Split circuit_t into origin_circuit_t and or_circuit_t, and
20908 split connection_t into edge, or, dir, control, and base structs.
20909 These will save quite a bit of memory on busy servers, and they'll
20910 also help us track down bugs in the code and bugs in the spec.
20911 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
20912 or later. Log when we are doing this, so we can diagnose it when
20913 it fails. (Also, recommend libevent 1.1b for kqueue and
20914 win32 methods; deprecate libevent 1.0b harder; make libevent
20915 recommendation system saner.)
20916 - Start being able to build universal binaries on OS X (thanks
20918 - Export the default exit policy via the control port, so controllers
20919 don't need to guess what it is / will be later.
20920 - Add a man page entry for ProtocolWarnings.
20921 - Add TestVia config option to the man page.
20922 - Remove even more protocol-related warnings from Tor server logs,
20923 such as bad TLS handshakes and malformed begin cells.
20924 - Stop fetching descriptors if you're not a dir mirror and you
20925 haven't tried to establish any circuits lately. [This currently
20926 causes some dangerous behavior, because when you start up again
20927 you'll use your ancient server descriptors.]
20928 - New DirPort behavior: if you have your dirport set, you download
20929 descriptors aggressively like a directory mirror, whether or not
20930 your ORPort is set.
20931 - Get rid of the router_retry_connections notion. Now routers
20932 no longer try to rebuild long-term connections to directory
20933 authorities, and directory authorities no longer try to rebuild
20934 long-term connections to all servers. We still don't hang up
20935 connections in these two cases though -- we need to look at it
20936 more carefully to avoid flapping, and we likely need to wait til
20937 0.1.1.x is obsolete.
20938 - Drop compatibility with obsolete Tors that permit create cells
20939 to have the wrong circ_id_type.
20940 - Re-enable per-connection rate limiting. Get rid of the "OP
20941 bandwidth" concept. Lay groundwork for "bandwidth classes" --
20942 separate global buckets that apply depending on what sort of conn
20944 - Start publishing one minute or so after we find our ORPort
20945 to be reachable. This will help reduce the number of descriptors
20946 we have for ourselves floating around, since it's quite likely
20947 other things (e.g. DirPort) will change during that minute too.
20948 - Fork the v1 directory protocol into its own spec document,
20949 and mark dir-spec.txt as the currently correct (v2) spec.
20952 - When we find our DirPort to be reachable, publish a new descriptor
20953 so we'll tell the world (reported by pnx).
20954 - Publish a new descriptor after we hup/reload. This is important
20955 if our config has changed such that we'll want to start advertising
20956 our DirPort now, etc.
20957 - Allow Tor to start when RunAsDaemon is set but no logs are set.
20958 - When we have a state file we cannot parse, tell the user and
20959 move it aside. Now we avoid situations where the user starts
20960 Tor in 1904, Tor writes a state file with that timestamp in it,
20961 the user fixes her clock, and Tor refuses to start.
20962 - Fix configure.in to not produce broken configure files with
20963 more recent versions of autoconf. Thanks to Clint for his auto*
20965 - "tor --verify-config" now exits with -1(255) or 0 depending on
20966 whether the config options are bad or good.
20967 - Resolve bug 321 when using dnsworkers: append a period to every
20968 address we resolve at the exit node, so that we do not accidentally
20969 pick up local addresses, and so that failing searches are retried
20970 in the resolver search domains. (This is already solved for
20971 eventdns.) (This breaks Blossom servers for now.)
20972 - If we are using an exit enclave and we can't connect, e.g. because
20973 its webserver is misconfigured to not listen on localhost, then
20974 back off and try connecting from somewhere else before we fail.
20977 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
20978 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
20979 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
20980 when the IP address is mapped through MapAddress to a hostname.
20981 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
20982 useless IPv6 DNS resolves.
20983 - Patch suggested by Karsten Loesing: respond to SIGNAL command
20984 before we execute the signal, in case the signal shuts us down.
20985 - Clean up AllowInvalidNodes man page entry.
20986 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
20987 - Add more asserts to track down an assert error on a windows Tor
20988 server with connection_add being called with socket == -1.
20989 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
20990 - Fix misleading log messages: an entry guard that is "unlisted",
20991 as well as not known to be "down" (because we've never heard
20992 of it), is not therefore "up".
20993 - Remove code to special-case "-cvs" ending, since it has not
20994 actually mattered since 0.0.9.
20995 - Make our socks5 handling more robust to broken socks clients:
20996 throw out everything waiting on the buffer in between socks
20997 handshake phases, since they can't possibly (so the theory
20998 goes) have predicted what we plan to respond to them.
21001 Changes in version 0.1.1.23 - 2006-07-30
21003 - Fast Tor servers, especially exit nodes, were triggering asserts
21004 due to a bug in handling the list of pending DNS resolves. Some
21005 bugs still remain here; we're hunting them.
21006 - Entry guards could crash clients by sending unexpected input.
21007 - More fixes on reachability testing: if you find yourself reachable,
21008 then don't ever make any client requests (so you stop predicting
21009 circuits), then hup or have your clock jump, then later your IP
21010 changes, you won't think circuits are working, so you won't try to
21011 test reachability, so you won't publish.
21014 - Avoid a crash if the controller does a resetconf firewallports
21015 and then a setconf fascistfirewall=1.
21016 - Avoid an integer underflow when the dir authority decides whether
21017 a router is stable: we might wrongly label it stable, and compute
21018 a slightly wrong median stability, when a descriptor is published
21020 - Fix a place where we might trigger an assert if we can't build our
21021 own server descriptor yet.
21024 Changes in version 0.1.1.22 - 2006-07-05
21026 - Fix a big bug that was causing servers to not find themselves
21027 reachable if they changed IP addresses. Since only 0.1.1.22+
21028 servers can do reachability testing correctly, now we automatically
21029 make sure to test via one of these.
21030 - Fix to allow clients and mirrors to learn directory info from
21031 descriptor downloads that get cut off partway through.
21032 - Directory authorities had a bug in deciding if a newly published
21033 descriptor was novel enough to make everybody want a copy -- a few
21034 servers seem to be publishing new descriptors many times a minute.
21036 - Fix a rare bug that was causing some servers to complain about
21037 "closing wedged cpuworkers" and skip some circuit create requests.
21038 - Make the Exit flag in directory status documents actually work.
21041 Changes in version 0.1.1.21 - 2006-06-10
21042 o Crash and assert fixes from 0.1.1.20:
21043 - Fix a rare crash on Tor servers that have enabled hibernation.
21044 - Fix a seg fault on startup for Tor networks that use only one
21045 directory authority.
21046 - Fix an assert from a race condition that occurs on Tor servers
21047 while exiting, where various threads are trying to log that they're
21048 exiting, and delete the logs, at the same time.
21049 - Make our unit tests pass again on certain obscure platforms.
21052 - Add support for building SUSE RPM packages.
21053 - Speed up initial bootstrapping for clients: if we are making our
21054 first ever connection to any entry guard, then don't mark it down
21056 - When only one Tor server in the network is labelled as a guard,
21057 and we've already picked him, we would cycle endlessly picking him
21058 again, being unhappy about it, etc. Now we specifically exclude
21059 current guards when picking a new guard.
21060 - Servers send create cells more reliably after the TLS connection
21061 is established: we were sometimes forgetting to send half of them
21062 when we had more than one pending.
21063 - If we get a create cell that asks us to extend somewhere, but the
21064 Tor server there doesn't match the expected digest, we now send
21065 a destroy cell back, rather than silently doing nothing.
21066 - Make options->RedirectExit work again.
21067 - Make cookie authentication for the controller work again.
21068 - Stop being picky about unusual characters in the arguments to
21069 mapaddress. It's none of our business.
21070 - Add a new config option "TestVia" that lets you specify preferred
21071 middle hops to use for test circuits. Perhaps this will let me
21072 debug the reachability problems better.
21074 o Log / documentation fixes:
21075 - If we're a server and some peer has a broken TLS certificate, don't
21076 log about it unless ProtocolWarnings is set, i.e., we want to hear
21077 about protocol violations by others.
21078 - Fix spelling of VirtualAddrNetwork in man page.
21079 - Add a better explanation at the top of the autogenerated torrc file
21080 about what happened to our old torrc.
21083 Changes in version 0.1.1.20 - 2006-05-23
21085 - Downgrade a log severity where servers complain that they're
21087 - Avoid a compile warning on FreeBSD.
21088 - Remove string size limit on NEWDESC messages; solve bug 291.
21089 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
21090 more thoroughly when we're running on windows.
21093 Changes in version 0.1.1.19-rc - 2006-05-03
21095 - Regenerate our local descriptor if it's dirty and we try to use
21096 it locally (e.g. if it changes during reachability detection).
21097 - If we setconf our ORPort to 0, we continued to listen on the
21098 old ORPort and receive connections.
21099 - Avoid a second warning about machine/limits.h on Debian
21101 - Be willing to add our own routerinfo into the routerlist.
21102 Now authorities will include themselves in their directories
21103 and network-statuses.
21104 - Stop trying to upload rendezvous descriptors to every
21105 directory authority: only try the v1 authorities.
21106 - Servers no longer complain when they think they're not
21107 registered with the directory authorities. There were too many
21109 - Backport dist-rpm changes so rpms can be built without errors.
21112 - Implement an option, VirtualAddrMask, to set which addresses
21113 get handed out in response to mapaddress requests. This works
21114 around a bug in tsocks where 127.0.0.0/8 is never socksified.
21117 Changes in version 0.1.1.18-rc - 2006-04-10
21119 - Work harder to download live network-statuses from all the
21120 directory authorities we know about. Improve the threshold
21121 decision logic so we're more robust to edge cases.
21122 - When fetching rendezvous descriptors, we were willing to ask
21123 v2 authorities too, which would always return 404.
21126 - Stop listing down or invalid nodes in the v1 directory. This will
21127 reduce its bulk by about 1/3, and reduce load on directory
21129 - When deciding whether a router is Fast or Guard-worthy, consider
21130 his advertised BandwidthRate and not just the BandwidthCapacity.
21131 - No longer ship INSTALL and README files -- they are useless now.
21132 - Force rpmbuild to behave and honor target_cpu.
21133 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
21134 - Start to include translated versions of the tor-doc-*.html
21135 files, along with the screenshots. Still needs more work.
21136 - Start sending back 512 and 451 errors if mapaddress fails,
21137 rather than not sending anything back at all.
21138 - When we fail to bind or listen on an incoming or outgoing
21139 socket, we should close it before failing. otherwise we just
21140 leak it. (thanks to weasel for finding.)
21141 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
21142 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
21143 - Make NoPublish (even though deprecated) work again.
21144 - Fix a minor security flaw where a versioning auth dirserver
21145 could list a recommended version many times in a row to make
21146 clients more convinced that it's recommended.
21147 - Fix crash bug if there are two unregistered servers running
21148 with the same nickname, one of them is down, and you ask for
21149 them by nickname in your EntryNodes or ExitNodes. Also, try
21150 to pick the one that's running rather than an arbitrary one.
21151 - Fix an infinite loop we could hit if we go offline for too long.
21152 - Complain when we hit WSAENOBUFS on recv() or write() too.
21153 Perhaps this will help us hunt the bug.
21154 - If you're not a versioning dirserver, don't put the string
21155 "client-versions \nserver-versions \n" in your network-status.
21156 - Lower the minimum required number of file descriptors to 1000,
21157 so we can have some overhead for Valgrind on Linux, where the
21158 default ulimit -n is 1024.
21161 - Add tor.dizum.com as the fifth authoritative directory server.
21162 - Add a new config option FetchUselessDescriptors, off by default,
21163 for when you plan to run "exitlist" on your client and you want
21164 to know about even the non-running descriptors.
21167 Changes in version 0.1.1.17-rc - 2006-03-28
21169 - Clients and servers since 0.1.1.10-alpha have been expiring
21170 connections whenever they are idle for 5 minutes and they *do*
21171 have circuits on them. Oops. With this new version, clients will
21172 discard their previous entry guard choices and avoid choosing
21173 entry guards running these flawed versions.
21174 - Fix memory leak when uncompressing concatenated zlib streams. This
21175 was causing substantial leaks over time on Tor servers.
21176 - The v1 directory was including servers as much as 48 hours old,
21177 because that's how the new routerlist->routers works. Now only
21178 include them if they're 20 hours old or less.
21181 - Resume building on irix64, netbsd 2.0, etc.
21182 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
21184 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
21185 and it is confusing some users.
21186 - Mirrors stop caching the v1 directory so often.
21187 - Make the max number of old descriptors that a cache will hold
21188 rise with the number of directory authorities, so we can scale.
21189 - Change our win32 uname() hack to be more forgiving about what
21190 win32 versions it thinks it's found.
21193 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
21195 - When the controller's *setconf commands fail, collect an error
21196 message in a string and hand it back to the controller.
21197 - Make the v2 dir's "Fast" flag based on relative capacity, just
21198 like "Stable" is based on median uptime. Name everything in the
21199 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
21200 - Log server fingerprint on startup, so new server operators don't
21201 have to go hunting around their filesystem for it.
21202 - Return a robots.txt on our dirport to discourage google indexing.
21203 - Let the controller ask for GETINFO dir/status/foo so it can ask
21204 directly rather than connecting to the dir port. Only works when
21205 dirport is set for now.
21207 o New config options rather than constants in the code:
21208 - SocksTimeout: How long do we let a socks connection wait
21209 unattached before we fail it?
21210 - CircuitBuildTimeout: Cull non-open circuits that were born
21211 at least this many seconds ago.
21212 - CircuitIdleTimeout: Cull open clean circuits that were born
21213 at least this many seconds ago.
21216 Changes in version 0.1.1.16-rc - 2006-03-18
21217 o Bugfixes on 0.1.1.15-rc:
21218 - Fix assert when the controller asks to attachstream a connect-wait
21219 or resolve-wait stream.
21220 - Now do address rewriting when the controller asks us to attach
21221 to a particular circuit too. This will let Blossom specify
21222 "moria2.exit" without having to learn what moria2's IP address is.
21223 - Make the "tor --verify-config" command-line work again, so people
21224 can automatically check if their torrc will parse.
21225 - Authoritative dirservers no longer require an open connection from
21226 a server to consider him "reachable". We need this change because
21227 when we add new auth dirservers, old servers won't know not to
21229 - Let Tor build on Sun CC again.
21230 - Fix an off-by-one buffer size in dirserv.c that magically never
21231 hit our three authorities but broke sjmurdoch's own tor network.
21232 - If we as a directory mirror don't know of any v1 directory
21233 authorities, then don't try to cache any v1 directories.
21234 - Stop warning about unknown servers in our family when they are
21235 given as hex digests.
21236 - Stop complaining as quickly to the server operator that he
21237 hasn't registered his nickname/key binding.
21238 - Various cleanups so we can add new V2 Auth Dirservers.
21239 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
21240 reflect the updated flags in our v2 dir protocol.
21241 - Resume allowing non-printable characters for exit streams (both
21242 for connecting and for resolving). Now we tolerate applications
21243 that don't follow the RFCs. But continue to block malformed names
21246 o Bugfixes on 0.1.0.x:
21247 - Fix assert bug in close_logs(): when we close and delete logs,
21248 remove them all from the global "logfiles" list.
21249 - Fix minor integer overflow in calculating when we expect to use up
21250 our bandwidth allocation before hibernating.
21251 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
21252 there are multiple SSLs installed with different versions.
21253 - When we try to be a server and Address is not explicitly set and
21254 our hostname resolves to a private IP address, try to use an
21255 interface address if it has a public address. Now Windows machines
21256 that think of themselves as localhost can work by default.
21259 - Let the controller ask for GETINFO dir/server/foo so it can ask
21260 directly rather than connecting to the dir port.
21261 - Let the controller tell us about certain router descriptors
21262 that it doesn't want Tor to use in circuits. Implement
21263 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
21264 - New config option SafeSocks to reject all application connections
21265 using unsafe socks protocols. Defaults to off.
21268 Changes in version 0.1.1.15-rc - 2006-03-11
21269 o Bugfixes and cleanups:
21270 - When we're printing strings from the network, don't try to print
21271 non-printable characters. This protects us against shell escape
21272 sequence exploits, and also against attacks to fool humans into
21273 misreading their logs.
21274 - Fix a bug where Tor would fail to establish any connections if you
21275 left it off for 24 hours and then started it: we were happy with
21276 the obsolete network statuses, but they all referred to router
21277 descriptors that were too old to fetch, so we ended up with no
21278 valid router descriptors.
21279 - Fix a seg fault in the controller's "getinfo orconn-status"
21280 command while listing status on incoming handshaking connections.
21281 Introduce a status name "NEW" for these connections.
21282 - If we get a linelist or linelist_s config option from the torrc
21283 (e.g. ExitPolicy) and it has no value, warn and skip rather than
21284 silently resetting it to its default.
21285 - Don't abandon entry guards until they've been down or gone for
21287 - Cleaner and quieter log messages.
21290 - New controller signal NEWNYM that makes new application requests
21291 use clean circuits.
21292 - Add a new circuit purpose 'controller' to let the controller ask
21293 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
21294 controller command to let you specify the purpose if you're
21295 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
21296 command to let you change a circuit's purpose after it's been
21298 - Accept "private:*" in routerdesc exit policies; not generated yet
21299 because older Tors do not understand it.
21300 - Add BSD-style contributed startup script "rc.subr" from Peter
21304 Changes in version 0.1.1.14-alpha - 2006-02-20
21305 o Bugfixes on 0.1.1.x:
21306 - Don't die if we ask for a stdout or stderr log (even implicitly)
21307 and we're set to RunAsDaemon -- just warn.
21308 - We still had a few bugs in the OR connection rotation code that
21309 caused directory servers to slowly aggregate connections to other
21310 fast Tor servers. This time for sure!
21311 - Make log entries on Win32 include the name of the function again.
21312 - We were treating a pair of exit policies if they were equal even
21313 if one said accept and the other said reject -- causing us to
21314 not always publish a new descriptor since we thought nothing
21316 - Retry pending server downloads as well as pending networkstatus
21317 downloads when we unexpectedly get a socks request.
21318 - We were ignoring the IS_FAST flag in the directory status,
21319 meaning we were willing to pick trivial-bandwidth nodes for "fast"
21321 - If the controller's SAVECONF command fails (e.g. due to file
21322 permissions), let the controller know that it failed.
21325 - If we're trying to be a Tor server and running Windows 95/98/ME
21326 as a server, explain that we'll likely crash.
21327 - When we're a server, a client asks for an old-style directory,
21328 and our write bucket is empty, don't give it to him. This way
21329 small servers can continue to serve the directory *sometimes*,
21330 without getting overloaded.
21331 - Compress exit policies even more -- look for duplicate lines
21333 - Clients now honor the "guard" flag in the router status when
21334 picking entry guards, rather than looking at is_fast or is_stable.
21335 - Retain unrecognized lines in $DATADIR/state file, so that we can
21336 be forward-compatible.
21337 - Generate 18.0.0.0/8 address policy format in descs when we can;
21338 warn when the mask is not reducible to a bit-prefix.
21339 - Let the user set ControlListenAddress in the torrc. This can be
21340 dangerous, but there are some cases (like a secured LAN) where it
21342 - Split ReachableAddresses into ReachableDirAddresses and
21343 ReachableORAddresses, so we can restrict Dir conns to port 80
21344 and OR conns to port 443.
21345 - Now we can target arch and OS in rpm builds (contributed by
21346 Phobos). Also make the resulting dist-rpm filename match the
21348 - New config options to help controllers: FetchServerDescriptors
21349 and FetchHidServDescriptors for whether to fetch server
21350 info and hidserv info or let the controller do it, and
21351 PublishServerDescriptor and PublishHidServDescriptors.
21352 - Also let the controller set the __AllDirActionsPrivate config
21353 option if you want all directory fetches/publishes to happen via
21354 Tor (it assumes your controller bootstraps your circuits).
21357 Changes in version 0.1.0.17 - 2006-02-17
21358 o Crash bugfixes on 0.1.0.x:
21359 - When servers with a non-zero DirPort came out of hibernation,
21360 sometimes they would trigger an assert.
21362 o Other important bugfixes:
21363 - On platforms that don't have getrlimit (like Windows), we were
21364 artificially constraining ourselves to a max of 1024
21365 connections. Now just assume that we can handle as many as 15000
21366 connections. Hopefully this won't cause other problems.
21368 o Backported features:
21369 - When we're a server, a client asks for an old-style directory,
21370 and our write bucket is empty, don't give it to him. This way
21371 small servers can continue to serve the directory *sometimes*,
21372 without getting overloaded.
21373 - Whenever you get a 503 in response to a directory fetch, try
21374 once more. This will become important once servers start sending
21375 503's whenever they feel busy.
21376 - Fetch a new directory every 120 minutes, not every 40 minutes.
21377 Now that we have hundreds of thousands of users running the old
21378 directory algorithm, it's starting to hurt a lot.
21379 - Bump up the period for forcing a hidden service descriptor upload
21380 from 20 minutes to 1 hour.
21383 Changes in version 0.1.1.13-alpha - 2006-02-09
21384 o Crashes in 0.1.1.x:
21385 - When you tried to setconf ORPort via the controller, Tor would
21386 crash. So people using TorCP to become a server were sad.
21387 - Solve (I hope) the stack-smashing bug that we were seeing on fast
21388 servers. The problem appears to be something do with OpenSSL's
21389 random number generation, or how we call it, or something. Let me
21390 know if the crashes continue.
21391 - Turn crypto hardware acceleration off by default, until we find
21392 somebody smart who can test it for us. (It appears to produce
21393 seg faults in at least some cases.)
21394 - Fix a rare assert error when we've tried all intro points for
21395 a hidden service and we try fetching the service descriptor again:
21396 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
21399 - Fix a major load balance bug: we were round-robining in 16 KB
21400 chunks, and servers with bandwidthrate of 20 KB, while downloading
21401 a 600 KB directory, would starve their other connections. Now we
21402 try to be a bit more fair.
21403 - Dir authorities and mirrors were never expiring the newest
21404 descriptor for each server, causing memory and directory bloat.
21405 - Fix memory-bloating and connection-bloating bug on servers: We
21406 were never closing any connection that had ever had a circuit on
21407 it, because we were checking conn->n_circuits == 0, yet we had a
21408 bug that let it go negative.
21409 - Make Tor work using squid as your http proxy again -- squid
21410 returns an error if you ask for a URL that's too long, and it uses
21411 a really generic error message. Plus, many people are behind a
21412 transparent squid so they don't even realize it.
21413 - On platforms that don't have getrlimit (like Windows), we were
21414 artificially constraining ourselves to a max of 1024
21415 connections. Now just assume that we can handle as many as 15000
21416 connections. Hopefully this won't cause other problems.
21417 - Add a new config option ExitPolicyRejectPrivate which defaults to
21418 1. This means all exit policies will begin with rejecting private
21419 addresses, unless the server operator explicitly turns it off.
21422 - Clients no longer download descriptors for non-running
21424 - Before we add new directory authorities, we should make it
21425 clear that only v1 authorities should receive/publish hidden
21426 service descriptors.
21429 - As soon as we've fetched some more directory info, immediately
21430 try to download more server descriptors. This way we don't have
21431 a 10 second pause during initial bootstrapping.
21432 - Remove even more loud log messages that the server operator can't
21434 - When we're running an obsolete or un-recommended version, make
21435 the log message more clear about what the problem is and what
21436 versions *are* still recommended.
21437 - Provide a more useful warn message when our onion queue gets full:
21438 the CPU is too slow or the exit policy is too liberal.
21439 - Don't warn when we receive a 503 from a dirserver/cache -- this
21440 will pave the way for them being able to refuse if they're busy.
21441 - When we fail to bind a listener, try to provide a more useful
21442 log message: e.g., "Is Tor already running?"
21443 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
21444 Goldberg can prove things about our handshake protocol more
21446 - MaxConn has been obsolete for a while now. Document the ConnLimit
21447 config option, which is a *minimum* number of file descriptors
21448 that must be available else Tor refuses to start.
21449 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
21450 if you log to syslog and want something other than LOG_DAEMON.
21451 - Make dirservers generate a separate "guard" flag to mean,
21452 "would make a good entry guard". Make clients parse it and vote
21453 on it. Not used by clients yet.
21454 - Implement --with-libevent-dir option to ./configure. Also, improve
21455 search techniques to find libevent, and use those for openssl too.
21456 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
21457 - Only start testing reachability once we've established a
21458 circuit. This will make startup on dirservers less noisy.
21459 - Don't try to upload hidden service descriptors until we have
21460 established a circuit.
21461 - Fix the controller's "attachstream 0" command to treat conn like
21462 it just connected, doing address remapping, handling .exit and
21463 .onion idioms, and so on. Now we're more uniform in making sure
21464 that the controller hears about new and closing connections.
21467 Changes in version 0.1.1.12-alpha - 2006-01-11
21468 o Bugfixes on 0.1.1.x:
21469 - The fix to close duplicate server connections was closing all
21470 Tor client connections if they didn't establish a circuit
21471 quickly enough. Oops.
21472 - Fix minor memory issue (double-free) that happened on exit.
21474 o Bugfixes on 0.1.0.x:
21475 - Tor didn't warn when it failed to open a log file.
21478 Changes in version 0.1.1.11-alpha - 2006-01-10
21479 o Crashes in 0.1.1.x:
21480 - Include all the assert/crash fixes from 0.1.0.16.
21481 - If you start Tor and then quit very quickly, there were some
21482 races that tried to free things that weren't allocated yet.
21483 - Fix a rare memory stomp if you're running hidden services.
21484 - Fix segfault when specifying DirServer in config without nickname.
21485 - Fix a seg fault when you finish connecting to a server but at
21486 that moment you dump his server descriptor.
21487 - Extendcircuit and Attachstream controller commands would
21488 assert/crash if you don't give them enough arguments.
21489 - Fix an assert error when we're out of space in the connection_list
21490 and we try to post a hidden service descriptor (reported by weasel).
21491 - If you specify a relative torrc path and you set RunAsDaemon in
21492 your torrc, then it chdir()'s to the new directory. If you HUP,
21493 it tries to load the new torrc location, fails, and exits.
21494 The fix: no longer allow a relative path to torrc using -f.
21497 - Implement "entry guards": automatically choose a handful of entry
21498 nodes and stick with them for all circuits. Only pick new guards
21499 when the ones you have are unsuitable, and if the old guards
21500 become suitable again, switch back. This will increase security
21501 dramatically against certain end-point attacks. The EntryNodes
21502 config option now provides some hints about which entry guards you
21503 want to use most; and StrictEntryNodes means to only use those.
21504 - New directory logic: download by descriptor digest, not by
21505 fingerprint. Caches try to download all listed digests from
21506 authorities; clients try to download "best" digests from caches.
21507 This avoids partitioning and isolating attacks better.
21508 - Make the "stable" router flag in network-status be the median of
21509 the uptimes of running valid servers, and make clients pay
21510 attention to the network-status flags. Thus the cutoff adapts
21511 to the stability of the network as a whole, making IRC, IM, etc
21512 connections more reliable.
21515 - Tor servers with dynamic IP addresses were needing to wait 18
21516 hours before they could start doing reachability testing using
21517 the new IP address and ports. This is because they were using
21518 the internal descriptor to learn what to test, yet they were only
21519 rebuilding the descriptor once they decided they were reachable.
21520 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
21521 to download certain server descriptors, throw them away, and then
21522 fetch them again after 30 minutes. Now mirrors throw away these
21523 server descriptors so clients can't get them.
21524 - We were leaving duplicate connections to other ORs open for a week,
21525 rather than closing them once we detect a duplicate. This only
21526 really affected authdirservers, but it affected them a lot.
21527 - Spread the authdirservers' reachability testing over the entire
21528 testing interval, so we don't try to do 500 TLS's at once every
21532 - If the network is down, and we try to connect to a conn because
21533 we have a circuit in mind, and we timeout (30 seconds) because the
21534 network never answers, we were expiring the circuit, but we weren't
21535 obsoleting the connection or telling the entry_guards functions.
21536 - Some Tor servers process billions of cells per day. These statistics
21537 need to be uint64_t's.
21538 - Check for integer overflows in more places, when adding elements
21539 to smartlists. This could possibly prevent a buffer overflow
21540 on malicious huge inputs. I don't see any, but I haven't looked
21542 - ReachableAddresses kept growing new "reject *:*" lines on every
21544 - When you "setconf log" via the controller, it should remove all
21545 logs. We were automatically adding back in a "log notice stdout".
21546 - Newly bootstrapped Tor networks couldn't establish hidden service
21547 circuits until they had nodes with high uptime. Be more tolerant.
21548 - We were marking servers down when they could not answer every piece
21549 of the directory request we sent them. This was far too harsh.
21550 - Fix the torify (tsocks) config file to not use Tor for localhost
21552 - Directory authorities now go to the proper authority when asking for
21553 a networkstatus, even when they want a compressed one.
21554 - Fix a harmless bug that was causing Tor servers to log
21555 "Got an end because of misc error, but we're not an AP. Closing."
21556 - Authorities were treating their own descriptor changes as cosmetic,
21557 meaning the descriptor available in the network-status and the
21558 descriptor that clients downloaded were different.
21559 - The OS X installer was adding a symlink for tor_resolve but
21560 the binary was called tor-resolve (reported by Thomas Hardly).
21561 - Workaround a problem with some http proxies where they refuse GET
21562 requests that specify "Content-Length: 0" (reported by Adrian).
21563 - Fix wrong log message when you add a "HiddenServiceNodes" config
21564 line without any HiddenServiceDir line (reported by Chris Thomas).
21567 - Write the TorVersion into the state file so we have a prayer of
21568 keeping forward and backward compatibility.
21569 - Revive the FascistFirewall config option rather than eliminating it:
21570 now it's a synonym for ReachableAddresses *:80,*:443.
21571 - Clients choose directory servers from the network status lists,
21572 not from their internal list of router descriptors. Now they can
21573 go to caches directly rather than needing to go to authorities
21575 - Directory authorities ignore router descriptors that have only
21576 cosmetic differences: do this for 0.1.0.x servers now too.
21577 - Add a new flag to network-status indicating whether the server
21578 can answer v2 directory requests too.
21579 - Authdirs now stop whining so loudly about bad descriptors that
21580 they fetch from other dirservers. So when there's a log complaint,
21581 it's for sure from a freshly uploaded descriptor.
21582 - Reduce memory requirements in our structs by changing the order
21584 - There used to be two ways to specify your listening ports in a
21585 server descriptor: on the "router" line and with a separate "ports"
21586 line. Remove support for the "ports" line.
21587 - New config option "AuthDirRejectUnlisted" for auth dirservers as
21588 a panic button: if we get flooded with unusable servers we can
21589 revert to only listing servers in the approved-routers file.
21590 - Auth dir servers can now mark a fingerprint as "!reject" or
21591 "!invalid" in the approved-routers file (as its nickname), to
21592 refuse descriptors outright or include them but marked as invalid.
21593 - Servers store bandwidth history across restarts/crashes.
21594 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
21595 get a better idea of why their circuits failed. Not used yet.
21596 - Directory mirrors now cache up to 16 unrecognized network-status
21597 docs. Now we can add new authdirservers and they'll be cached too.
21598 - When picking a random directory, prefer non-authorities if any
21600 - New controller option "getinfo desc/all-recent" to fetch the
21601 latest server descriptor for every router that Tor knows about.
21604 Changes in version 0.1.0.16 - 2006-01-02
21605 o Crash bugfixes on 0.1.0.x:
21606 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
21607 corrupting the heap, losing FDs, or crashing when we need to resize
21608 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
21609 - It turns out sparc64 platforms crash on unaligned memory access
21610 too -- so detect and avoid this.
21611 - Handle truncated compressed data correctly (by detecting it and
21613 - Fix possible-but-unlikely free(NULL) in control.c.
21614 - When we were closing connections, there was a rare case that
21615 stomped on memory, triggering seg faults and asserts.
21616 - Avoid potential infinite recursion when building a descriptor. (We
21617 don't know that it ever happened, but better to fix it anyway.)
21618 - We were neglecting to unlink marked circuits from soon-to-close OR
21619 connections, which caused some rare scribbling on freed memory.
21620 - Fix a memory stomping race bug when closing the joining point of two
21621 rendezvous circuits.
21622 - Fix an assert in time parsing found by Steven Murdoch.
21624 o Other bugfixes on 0.1.0.x:
21625 - When we're doing reachability testing, provide more useful log
21626 messages so the operator knows what to expect.
21627 - Do not check whether DirPort is reachable when we are suppressing
21628 advertising it because of hibernation.
21629 - When building with -static or on Solaris, we sometimes needed -ldl.
21630 - When we're deciding whether a stream has enough circuits around
21631 that can handle it, count the freshly dirty ones and not the ones
21632 that are so dirty they won't be able to handle it.
21633 - When we're expiring old circuits, we had a logic error that caused
21634 us to close new rendezvous circuits rather than old ones.
21635 - Give a more helpful log message when you try to change ORPort via
21636 the controller: you should upgrade Tor if you want that to work.
21637 - We were failing to parse Tor versions that start with "Tor ".
21638 - Tolerate faulty streams better: when a stream fails for reason
21639 exitpolicy, stop assuming that the router is lying about his exit
21640 policy. When a stream fails for reason misc, allow it to retry just
21641 as if it was resolvefailed. When a stream has failed three times,
21642 reset its failure count so we can try again and get all three tries.
21645 Changes in version 0.1.1.10-alpha - 2005-12-11
21646 o Correctness bugfixes on 0.1.0.x:
21647 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
21648 corrupting the heap, losing FDs, or crashing when we need to resize
21649 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
21650 - Stop doing the complex voodoo overkill checking for insecure
21651 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
21652 - When we were closing connections, there was a rare case that
21653 stomped on memory, triggering seg faults and asserts.
21654 - We were neglecting to unlink marked circuits from soon-to-close OR
21655 connections, which caused some rare scribbling on freed memory.
21656 - When we're deciding whether a stream has enough circuits around
21657 that can handle it, count the freshly dirty ones and not the ones
21658 that are so dirty they won't be able to handle it.
21659 - Recover better from TCP connections to Tor servers that are
21660 broken but don't tell you (it happens!); and rotate TLS
21661 connections once a week.
21662 - When we're expiring old circuits, we had a logic error that caused
21663 us to close new rendezvous circuits rather than old ones.
21664 - Fix a scary-looking but apparently harmless bug where circuits
21665 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
21666 servers, and never switch to state CIRCUIT_STATE_OPEN.
21667 - When building with -static or on Solaris, we sometimes needed to
21669 - Give a useful message when people run Tor as the wrong user,
21670 rather than telling them to start chowning random directories.
21671 - We were failing to inform the controller about new .onion streams.
21673 o Security bugfixes on 0.1.0.x:
21674 - Refuse server descriptors if the fingerprint line doesn't match
21675 the included identity key. Tor doesn't care, but other apps (and
21676 humans) might actually be trusting the fingerprint line.
21677 - We used to kill the circuit when we receive a relay command we
21678 don't recognize. Now we just drop it.
21679 - Start obeying our firewall options more rigorously:
21680 . If we can't get to a dirserver directly, try going via Tor.
21681 . Don't ever try to connect (as a client) to a place our
21682 firewall options forbid.
21683 . If we specify a proxy and also firewall options, obey the
21684 firewall options even when we're using the proxy: some proxies
21685 can only proxy to certain destinations.
21686 - Fix a bug found by Lasse Overlier: when we were making internal
21687 circuits (intended to be cannibalized later for rendezvous and
21688 introduction circuits), we were picking them so that they had
21689 useful exit nodes. There was no need for this, and it actually
21690 aids some statistical attacks.
21691 - Start treating internal circuits and exit circuits separately.
21692 It's important to keep them separate because internal circuits
21693 have their last hops picked like middle hops, rather than like
21694 exit hops. So exiting on them will break the user's expectations.
21696 o Bugfixes on 0.1.1.x:
21697 - Take out the mis-feature where we tried to detect IP address
21698 flapping for people with DynDNS, and chose not to upload a new
21699 server descriptor sometimes.
21700 - Try to be compatible with OpenSSL 0.9.6 again.
21701 - Log fix: when the controller is logging about .onion addresses,
21702 sometimes it didn't include the ".onion" part of the address.
21703 - Don't try to modify options->DirServers internally -- if the
21704 user didn't specify any, just add the default ones directly to
21705 the trusted dirserver list. This fixes a bug where people running
21706 controllers would use SETCONF on some totally unrelated config
21707 option, and Tor would start yelling at them about changing their
21709 - Let the controller's redirectstream command specify a port, in
21710 case the controller wants to change that too.
21711 - When we requested a pile of server descriptors, we sometimes
21712 accidentally launched a duplicate request for the first one.
21713 - Bugfix for trackhostexits: write down the fingerprint of the
21714 chosen exit, not its nickname, because the chosen exit might not
21716 - When parsing foo.exit, if foo is unknown, and we are leaving
21717 circuits unattached, set the chosen_exit field and leave the
21718 address empty. This matters because controllers got confused
21720 - Directory authorities no longer try to download server
21721 descriptors that they know they will reject.
21723 o Features and updates:
21724 - Replace balanced trees with hash tables: this should make stuff
21725 significantly faster.
21726 - Resume using the AES counter-mode implementation that we ship,
21727 rather than OpenSSL's. Ours is significantly faster.
21728 - Many other CPU and memory improvements.
21729 - Add a new config option FastFirstHopPK (on by default) so clients
21730 do a trivial crypto handshake for their first hop, since TLS has
21731 already taken care of confidentiality and authentication.
21732 - Add a new config option TestSocks so people can see if their
21733 applications are using socks4, socks4a, socks5-with-ip, or
21734 socks5-with-hostname. This way they don't have to keep mucking
21735 with tcpdump and wondering if something got cached somewhere.
21736 - Warn when listening on a public address for socks. I suspect a
21737 lot of people are setting themselves up as open socks proxies,
21738 and they have no idea that jerks on the Internet are using them,
21739 since they simply proxy the traffic into the Tor network.
21740 - Add "private:*" as an alias in configuration for policies. Now
21741 you can simplify your exit policy rather than needing to list
21742 every single internal or nonroutable network space.
21743 - Add a new controller event type that allows controllers to get
21744 all server descriptors that were uploaded to a router in its role
21745 as authoritative dirserver.
21746 - Start shipping socks-extensions.txt, tor-doc-unix.html,
21747 tor-doc-server.html, and stylesheet.css in the tarball.
21748 - Stop shipping tor-doc.html in the tarball.
21751 Changes in version 0.1.1.9-alpha - 2005-11-15
21752 o Usability improvements:
21753 - Start calling it FooListenAddress rather than FooBindAddress,
21754 since few of our users know what it means to bind an address
21756 - Reduce clutter in server logs. We're going to try to make
21757 them actually usable now. New config option ProtocolWarnings that
21758 lets you hear about how _other Tors_ are breaking the protocol. Off
21760 - Divide log messages into logging domains. Once we put some sort
21761 of interface on this, it will let people looking at more verbose
21762 log levels specify the topics they want to hear more about.
21763 - Make directory servers return better http 404 error messages
21764 instead of a generic "Servers unavailable".
21765 - Check for even more Windows version flags when writing the platform
21766 string in server descriptors, and note any we don't recognize.
21767 - Clean up more of the OpenSSL memory when exiting, so we can detect
21768 memory leaks better.
21769 - Make directory authorities be non-versioning, non-naming by
21770 default. Now we can add new directory servers without requiring
21771 their operators to pay close attention.
21772 - When logging via syslog, include the pid whenever we provide
21773 a log entry. Suggested by Todd Fries.
21775 o Performance improvements:
21776 - Directory servers now silently throw away new descriptors that
21777 haven't changed much if the timestamps are similar. We do this to
21778 tolerate older Tor servers that upload a new descriptor every 15
21779 minutes. (It seemed like a good idea at the time.)
21780 - Inline bottleneck smartlist functions; use fast versions by default.
21781 - Add a "Map from digest to void*" abstraction digestmap_t so we
21782 can do less hex encoding/decoding. Use it in router_get_by_digest()
21783 to resolve a performance bottleneck.
21784 - Allow tor_gzip_uncompress to extract as much as possible from
21785 truncated compressed data. Try to extract as many
21786 descriptors as possible from truncated http responses (when
21787 DIR_PURPOSE_FETCH_ROUTERDESC).
21788 - Make circ->onionskin a pointer, not a static array. moria2 was using
21789 125000 circuit_t's after it had been up for a few weeks, which
21790 translates to 20+ megs of wasted space.
21791 - The private half of our EDH handshake keys are now chosen out
21792 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
21794 o Security improvements:
21795 - Start making directory caches retain old routerinfos, so soon
21796 clients can start asking by digest of descriptor rather than by
21797 fingerprint of server.
21798 - Add half our entropy from RAND_poll in OpenSSL. This knows how
21799 to use egd (if present), openbsd weirdness (if present), vms/os2
21800 weirdness (if we ever port there), and more in the future.
21802 o Bugfixes on 0.1.0.x:
21803 - Do round-robin writes of at most 16 kB per write. This might be
21804 more fair on loaded Tor servers, and it might resolve our Windows
21805 crash bug. It might also slow things down.
21806 - Our TLS handshakes were generating a single public/private
21807 keypair for the TLS context, rather than making a new one for
21808 each new connections. Oops. (But we were still rotating them
21809 periodically, so it's not so bad.)
21810 - When we were cannibalizing a circuit with a particular exit
21811 node in mind, we weren't checking to see if that exit node was
21812 already present earlier in the circuit. Oops.
21813 - When a Tor server's IP changes (e.g. from a dyndns address),
21814 upload a new descriptor so clients will learn too.
21815 - Really busy servers were keeping enough circuits open on stable
21816 connections that they were wrapping around the circuit_id
21817 space. (It's only two bytes.) This exposed a bug where we would
21818 feel free to reuse a circuit_id even if it still exists but has
21819 been marked for close. Try to fix this bug. Some bug remains.
21820 - If we would close a stream early (e.g. it asks for a .exit that
21821 we know would refuse it) but the LeaveStreamsUnattached config
21822 option is set by the controller, then don't close it.
21824 o Bugfixes on 0.1.1.8-alpha:
21825 - Fix a big pile of memory leaks, some of them serious.
21826 - Do not try to download a routerdesc if we would immediately reject
21828 - Resume inserting a newline between all router descriptors when
21829 generating (old style) signed directories, since our spec says
21831 - When providing content-type application/octet-stream for
21832 server descriptors using .z, we were leaving out the
21833 content-encoding header. Oops. (Everything tolerated this just
21834 fine, but that doesn't mean we need to be part of the problem.)
21835 - Fix a potential seg fault in getconf and getinfo using version 1
21836 of the controller protocol.
21837 - Avoid crash: do not check whether DirPort is reachable when we
21838 are suppressing it because of hibernation.
21839 - Make --hash-password not crash on exit.
21842 Changes in version 0.1.1.8-alpha - 2005-10-07
21843 o New features (major):
21844 - Clients don't download or use the directory anymore. Now they
21845 download and use network-statuses from the trusted dirservers,
21846 and fetch individual server descriptors as needed from mirrors.
21847 See dir-spec.txt for all the gory details.
21848 - Be more conservative about whether to advertise our DirPort.
21849 The main change is to not advertise if we're running at capacity
21850 and either a) we could hibernate or b) our capacity is low and
21851 we're using a default DirPort.
21852 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
21854 o New features (minor):
21855 - Try to be smart about when to retry network-status and
21856 server-descriptor fetches. Still needs some tuning.
21857 - Stop parsing, storing, or using running-routers output (but
21858 mirrors still cache and serve it).
21859 - Consider a threshold of versioning dirservers (dirservers who have
21860 an opinion about which Tor versions are still recommended) before
21861 deciding whether to warn the user that he's obsolete.
21862 - Dirservers can now reject/invalidate by key and IP, with the
21863 config options "AuthDirInvalid" and "AuthDirReject". This is
21864 useful since currently we automatically list servers as running
21865 and usable even if we know they're jerks.
21866 - Provide dire warnings to any users who set DirServer; move it out
21867 of torrc.sample and into torrc.complete.
21868 - Add MyFamily to torrc.sample in the server section.
21869 - Add nicknames to the DirServer line, so we can refer to them
21870 without requiring all our users to memorize their IP addresses.
21871 - When we get an EOF or a timeout on a directory connection, note
21872 how many bytes of serverdesc we are dropping. This will help
21873 us determine whether it is smart to parse incomplete serverdesc
21875 - Add a new function to "change pseudonyms" -- that is, to stop
21876 using any currently-dirty circuits for new streams, so we don't
21877 link new actions to old actions. Currently it's only called on
21878 HUP (or SIGNAL RELOAD).
21879 - On sighup, if UseHelperNodes changed to 1, use new circuits.
21880 - Start using RAND_bytes rather than RAND_pseudo_bytes from
21881 OpenSSL. Also, reseed our entropy every hour, not just at
21882 startup. And entropy in 512-bit chunks, not 160-bit chunks.
21884 o Fixes on 0.1.1.7-alpha:
21885 - Nobody ever implemented EVENT_ADDRMAP for control protocol
21886 version 0, so don't let version 0 controllers ask for it.
21887 - If you requested something with too many newlines via the
21888 v1 controller protocol, you could crash tor.
21889 - Fix a number of memory leaks, including some pretty serious ones.
21890 - Re-enable DirPort testing again, so Tor servers will be willing
21891 to advertise their DirPort if it's reachable.
21892 - On TLS handshake, only check the other router's nickname against
21893 its expected nickname if is_named is set.
21895 o Fixes forward-ported from 0.1.0.15:
21896 - Don't crash when we don't have any spare file descriptors and we
21897 try to spawn a dns or cpu worker.
21898 - Make the numbers in read-history and write-history into uint64s,
21899 so they don't overflow and publish negatives in the descriptor.
21901 o Fixes on 0.1.0.x:
21902 - For the OS X package's modified privoxy config file, comment
21903 out the "logfile" line so we don't log everything passed
21905 - We were whining about using socks4 or socks5-with-local-lookup
21906 even when it's an IP in the "virtual" range we designed exactly
21908 - We were leaking some memory every time the client changes IPs.
21909 - Never call free() on tor_malloc()d memory. This will help us
21910 use dmalloc to detect memory leaks.
21911 - Check for named servers when looking them up by nickname;
21912 warn when we'recalling a non-named server by its nickname;
21913 don't warn twice about the same name.
21914 - Try to list MyFamily elements by key, not by nickname, and warn
21915 if we've not heard of the server.
21916 - Make windows platform detection (uname equivalent) smarter.
21917 - It turns out sparc64 doesn't like unaligned access either.
21920 Changes in version 0.1.0.15 - 2005-09-23
21921 o Bugfixes on 0.1.0.x:
21922 - Reject ports 465 and 587 (spam targets) in default exit policy.
21923 - Don't crash when we don't have any spare file descriptors and we
21924 try to spawn a dns or cpu worker.
21925 - Get rid of IgnoreVersion undocumented config option, and make us
21926 only warn, never exit, when we're running an obsolete version.
21927 - Don't try to print a null string when your server finds itself to
21928 be unreachable and the Address config option is empty.
21929 - Make the numbers in read-history and write-history into uint64s,
21930 so they don't overflow and publish negatives in the descriptor.
21931 - Fix a minor memory leak in smartlist_string_remove().
21932 - We were only allowing ourselves to upload a server descriptor at
21933 most every 20 minutes, even if it changed earlier than that.
21934 - Clean up log entries that pointed to old URLs.
21937 Changes in version 0.1.1.7-alpha - 2005-09-14
21938 o Fixes on 0.1.1.6-alpha:
21939 - Exit servers were crashing when people asked them to make a
21940 connection to an address not in their exit policy.
21941 - Looking up a non-existent stream for a v1 control connection would
21943 - Fix a seg fault if we ask a dirserver for a descriptor by
21944 fingerprint but he doesn't know about him.
21945 - SETCONF was appending items to linelists, not clearing them.
21946 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
21947 out and refuse the setconf if it would fail.
21948 - Downgrade the dirserver log messages when whining about
21952 - Add Peter Palfrader's check-tor script to tor/contrib/
21953 It lets you easily check whether a given server (referenced by
21954 nickname) is reachable by you.
21955 - Numerous changes to move towards client-side v2 directories. Not
21958 o Fixes on 0.1.0.x:
21959 - If the user gave tor an odd number of command-line arguments,
21960 we were silently ignoring the last one. Now we complain and fail.
21961 [This wins the oldest-bug prize -- this bug has been present since
21962 November 2002, as released in Tor 0.0.0.]
21963 - Do not use unaligned memory access on alpha, mips, or mipsel.
21964 It *works*, but is very slow, so we treat them as if it doesn't.
21965 - Retry directory requests if we fail to get an answer we like
21966 from a given dirserver (we were retrying before, but only if
21967 we fail to connect).
21968 - When writing the RecommendedVersions line, sort them first.
21969 - When the client asked for a rendezvous port that the hidden
21970 service didn't want to provide, we were sending an IP address
21971 back along with the end cell. Fortunately, it was zero. But stop
21973 - Correct "your server is reachable" log entries to indicate that
21974 it was self-testing that told us so.
21977 Changes in version 0.1.1.6-alpha - 2005-09-09
21978 o Fixes on 0.1.1.5-alpha:
21979 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
21980 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
21981 - Fix bug with tor_memmem finding a match at the end of the string.
21982 - Make unit tests run without segfaulting.
21983 - Resolve some solaris x86 compile warnings.
21984 - Handle duplicate lines in approved-routers files without warning.
21985 - Fix bug where as soon as a server refused any requests due to his
21986 exit policy (e.g. when we ask for localhost and he tells us that's
21987 127.0.0.1 and he won't do it), we decided he wasn't obeying his
21988 exit policy using him for any exits.
21989 - Only do openssl hardware accelerator stuff if openssl version is
21992 o New controller features/fixes:
21993 - Add a "RESETCONF" command so you can set config options like
21994 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
21995 a config option in the torrc with no value, then it clears it
21996 entirely (rather than setting it to its default).
21997 - Add a "GETINFO config-file" to tell us where torrc is.
21998 - Avoid sending blank lines when GETINFO replies should be empty.
21999 - Add a QUIT command for the controller (for using it manually).
22000 - Fix a bug in SAVECONF that was adding default dirservers and
22001 other redundant entries to the torrc file.
22003 o Start on the new directory design:
22004 - Generate, publish, cache, serve new network-status format.
22005 - Publish individual descriptors (by fingerprint, by "all", and by
22007 - Publish client and server recommended versions separately.
22008 - Allow tor_gzip_uncompress() to handle multiple concatenated
22009 compressed strings. Serve compressed groups of router
22010 descriptors. The compression logic here could be more
22012 - Distinguish v1 authorities (all currently trusted directories)
22013 from v2 authorities (all trusted directories).
22014 - Change DirServers config line to note which dirs are v1 authorities.
22015 - Add configuration option "V1AuthoritativeDirectory 1" which
22016 moria1, moria2, and tor26 should set.
22017 - Remove option when getting directory cache to see whether they
22018 support running-routers; they all do now. Replace it with one
22019 to see whether caches support v2 stuff.
22022 - Dirservers now do their own external reachability testing of each
22023 Tor server, and only list them as running if they've been found to
22024 be reachable. We also send back warnings to the server's logs if
22025 it uploads a descriptor that we already believe is unreachable.
22026 - Implement exit enclaves: if we know an IP address for the
22027 destination, and there's a running Tor server at that address
22028 which allows exit to the destination, then extend the circuit to
22029 that exit first. This provides end-to-end encryption and end-to-end
22030 authentication. Also, if the user wants a .exit address or enclave,
22031 use 4 hops rather than 3, and cannibalize a general circ for it
22033 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
22034 controller. Also, rotate dns and cpu workers if the controller
22035 changes options that will affect them; and initialize the dns
22036 worker cache tree whether or not we start out as a server.
22037 - Only upload a new server descriptor when options change, 18
22038 hours have passed, uptime is reset, or bandwidth changes a lot.
22039 - Check [X-]Forwarded-For headers in HTTP requests when generating
22040 log messages. This lets people run dirservers (and caches) behind
22041 Apache but still know which IP addresses are causing warnings.
22043 o Config option changes:
22044 - Replace (Fascist)Firewall* config options with a new
22045 ReachableAddresses option that understands address policies.
22046 For example, "ReachableAddresses *:80,*:443"
22047 - Get rid of IgnoreVersion undocumented config option, and make us
22048 only warn, never exit, when we're running an obsolete version.
22049 - Make MonthlyAccountingStart config option truly obsolete now.
22051 o Fixes on 0.1.0.x:
22052 - Reject ports 465 and 587 in the default exit policy, since
22053 people have started using them for spam too.
22054 - It turns out we couldn't bootstrap a network since we added
22055 reachability detection in 0.1.0.1-rc. Good thing the Tor network
22056 has never gone down. Add an AssumeReachable config option to let
22057 servers and dirservers bootstrap. When we're trying to build a
22058 high-uptime or high-bandwidth circuit but there aren't enough
22059 suitable servers, try being less picky rather than simply failing.
22060 - Our logic to decide if the OR we connected to was the right guy
22061 was brittle and maybe open to a mitm for unverified routers.
22062 - We weren't cannibalizing circuits correctly for
22063 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
22064 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
22065 build those from scratch. This should make hidden services faster.
22066 - Predict required circuits better, with an eye toward making hidden
22067 services faster on the service end.
22068 - Retry streams if the exit node sends back a 'misc' failure. This
22069 should result in fewer random failures. Also, after failing
22070 from resolve failed or misc, reset the num failures, so we give
22071 it a fair shake next time we try.
22072 - Clean up the rendezvous warn log msgs, and downgrade some to info.
22073 - Reduce severity on logs about dns worker spawning and culling.
22074 - When we're shutting down and we do something like try to post a
22075 server descriptor or rendezvous descriptor, don't complain that
22076 we seem to be unreachable. Of course we are, we're shutting down.
22077 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
22078 We don't use them yet, but maybe one day our DNS resolver will be
22079 able to discover them.
22080 - Make ContactInfo mandatory for authoritative directory servers.
22081 - Require server descriptors to list IPv4 addresses -- hostnames
22082 are no longer allowed. This also fixes some potential security
22083 problems with people providing hostnames as their address and then
22084 preferentially resolving them to partition users.
22085 - Change log line for unreachability to explicitly suggest /etc/hosts
22086 as the culprit. Also make it clearer what IP address and ports we're
22087 testing for reachability.
22088 - Put quotes around user-supplied strings when logging so users are
22089 more likely to realize if they add bad characters (like quotes)
22091 - Let auth dir servers start without specifying an Address config
22093 - Make unit tests (and other invocations that aren't the real Tor)
22094 run without launching listeners, creating subdirectories, and so on.
22097 Changes in version 0.1.1.5-alpha - 2005-08-08
22098 o Bugfixes included in 0.1.0.14.
22100 o Bugfixes on 0.1.0.x:
22101 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
22102 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
22103 it would silently using ignore the 6668.
22106 Changes in version 0.1.0.14 - 2005-08-08
22107 o Bugfixes on 0.1.0.x:
22108 - Fix the other half of the bug with crypto handshakes
22110 - Fix an assert trigger if you send a 'signal term' via the
22111 controller when it's listening for 'event info' messages.
22114 Changes in version 0.1.1.4-alpha - 2005-08-04
22115 o Bugfixes included in 0.1.0.13.
22118 - Improve tor_gettimeofday() granularity on windows.
22119 - Make clients regenerate their keys when their IP address changes.
22120 - Implement some more GETINFO goodness: expose helper nodes, config
22121 options, getinfo keys.
22124 Changes in version 0.1.0.13 - 2005-08-04
22125 o Bugfixes on 0.1.0.x:
22126 - Fix a critical bug in the security of our crypto handshakes.
22127 - Fix a size_t underflow in smartlist_join_strings2() that made
22128 it do bad things when you hand it an empty smartlist.
22129 - Fix Windows installer to ship Tor license (thanks to Aphex for
22130 pointing out this oversight) and put a link to the doc directory
22132 - Explicitly set no-unaligned-access for sparc: it turns out the
22133 new gcc's let you compile broken code, but that doesn't make it
22137 Changes in version 0.1.1.3-alpha - 2005-07-23
22138 o Bugfixes on 0.1.1.2-alpha:
22139 - Fix a bug in handling the controller's "post descriptor"
22141 - Fix several bugs in handling the controller's "extend circuit"
22143 - Fix a bug in handling the controller's "stream status" event.
22144 - Fix an assert failure if we have a controller listening for
22145 circuit events and we go offline.
22146 - Re-allow hidden service descriptors to publish 0 intro points.
22147 - Fix a crash when generating your hidden service descriptor if
22148 you don't have enough intro points already.
22150 o New features on 0.1.1.2-alpha:
22151 - New controller function "getinfo accounting", to ask how
22152 many bytes we've used in this time period.
22153 - Experimental support for helper nodes: a lot of the risk from
22154 a small static adversary comes because users pick new random
22155 nodes every time they rebuild a circuit. Now users will try to
22156 stick to the same small set of entry nodes if they can. Not
22157 enabled by default yet.
22159 o Bugfixes on 0.1.0.12:
22160 - If you're an auth dir server, always publish your dirport,
22161 even if you haven't yet found yourself to be reachable.
22162 - Fix a size_t underflow in smartlist_join_strings2() that made
22163 it do bad things when you hand it an empty smartlist.
22166 Changes in version 0.1.0.12 - 2005-07-18
22167 o New directory servers:
22168 - tor26 has changed IP address.
22170 o Bugfixes on 0.1.0.x:
22171 - Fix a possible double-free in tor_gzip_uncompress().
22172 - When --disable-threads is set, do not search for or link against
22173 pthreads libraries.
22174 - Don't trigger an assert if an authoritative directory server
22175 claims its dirport is 0.
22176 - Fix bug with removing Tor as an NT service: some people were
22177 getting "The service did not return an error." Thanks to Matt
22181 Changes in version 0.1.1.2-alpha - 2005-07-15
22182 o New directory servers:
22183 - tor26 has changed IP address.
22185 o Bugfixes on 0.1.0.x, crashes/leaks:
22186 - Port the servers-not-obeying-their-exit-policies fix from
22188 - Fix an fd leak in start_daemon().
22189 - On Windows, you can't always reopen a port right after you've
22190 closed it. So change retry_listeners() to only close and re-open
22191 ports that have changed.
22192 - Fix a possible double-free in tor_gzip_uncompress().
22194 o Bugfixes on 0.1.0.x, usability:
22195 - When tor_socketpair() fails in Windows, give a reasonable
22196 Windows-style errno back.
22197 - Let people type "tor --install" as well as "tor -install" when
22199 want to make it an NT service.
22200 - NT service patch from Matt Edman to improve error messages.
22201 - When the controller asks for a config option with an abbreviated
22202 name, give the full name in our response.
22203 - Correct the man page entry on TrackHostExitsExpire.
22204 - Looks like we were never delivering deflated (i.e. compressed)
22205 running-routers lists, even when asked. Oops.
22206 - When --disable-threads is set, do not search for or link against
22207 pthreads libraries.
22209 o Bugfixes on 0.1.1.x:
22210 - Fix a seg fault with autodetecting which controller version is
22214 - New hidden service descriptor format: put a version in it, and
22215 let people specify introduction/rendezvous points that aren't
22216 in "the directory" (which is subjective anyway).
22217 - Allow the DEBUG controller event to work again. Mark certain log
22218 entries as "don't tell this to controllers", so we avoid cycles.
22221 Changes in version 0.1.0.11 - 2005-06-30
22222 o Bugfixes on 0.1.0.x:
22223 - Fix major security bug: servers were disregarding their
22224 exit policies if clients behaved unexpectedly.
22225 - Make OS X init script check for missing argument, so we don't
22226 confuse users who invoke it incorrectly.
22227 - Fix a seg fault in "tor --hash-password foo".
22228 - The MAPADDRESS control command was broken.
22231 Changes in version 0.1.1.1-alpha - 2005-06-29
22233 - Make OS X init script check for missing argument, so we don't
22234 confuse users who invoke it incorrectly.
22235 - Fix a seg fault in "tor --hash-password foo".
22236 - Fix a possible way to DoS dirservers.
22237 - When we complain that your exit policy implicitly allows local or
22238 private address spaces, name them explicitly so operators can
22240 - Make the log message less scary when all the dirservers are
22241 temporarily unreachable.
22242 - We were printing the number of idle dns workers incorrectly when
22246 - Revised controller protocol (version 1) that uses ascii rather
22247 than binary. Add supporting libraries in python and java so you
22248 can use the controller from your applications without caring how
22249 our protocol works.
22250 - Spiffy new support for crypto hardware accelerators. Can somebody
22254 Changes in version 0.0.9.10 - 2005-06-16
22255 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
22256 - Refuse relay cells that claim to have a length larger than the
22257 maximum allowed. This prevents a potential attack that could read
22258 arbitrary memory (e.g. keys) from an exit server's process
22262 Changes in version 0.1.0.10 - 2005-06-14
22263 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
22264 libevent before 1.1a.
22267 Changes in version 0.1.0.9-rc - 2005-06-09
22269 - Reset buf->highwater every time buf_shrink() is called, not just on
22270 a successful shrink. This was causing significant memory bloat.
22271 - Fix buffer overflow when checking hashed passwords.
22272 - Security fix: if seeding the RNG on Win32 fails, quit.
22273 - Allow seeding the RNG on Win32 even when you're not running as
22275 - Disable threading on Solaris too. Something is wonky with it,
22276 cpuworkers, and reentrant libs.
22277 - Reenable the part of the code that tries to flush as soon as an
22278 OR outbuf has a full TLS record available. Perhaps this will make
22279 OR outbufs not grow as huge except in rare cases, thus saving lots
22280 of CPU time plus memory.
22281 - Reject malformed .onion addresses rather then passing them on as
22282 normal web requests.
22283 - Adapt patch from Adam Langley: fix possible memory leak in
22284 tor_lookup_hostname().
22285 - Initialize libevent later in the startup process, so the logs are
22286 already established by the time we start logging libevent warns.
22287 - Use correct errno on win32 if libevent fails.
22288 - Check and warn about known-bad/slow libevent versions.
22289 - Pay more attention to the ClientOnly config option.
22290 - Have torctl.in/tor.sh.in check for location of su binary (needed
22292 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
22293 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
22294 HttpProxyAuthenticator
22295 - Stop warning about sigpipes in the logs. We're going to
22296 pretend that getting these occassionally is normal and fine.
22297 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
22299 installer screens; and don't put stuff into StartupItems unless
22300 the user asks you to.
22301 - Require servers that use the default dirservers to have public IP
22302 addresses. We have too many servers that are configured with private
22303 IPs and their admins never notice the log entries complaining that
22304 their descriptors are being rejected.
22305 - Add OSX uninstall instructions. An actual uninstall script will
22309 Changes in version 0.1.0.8-rc - 2005-05-23
22311 - It turns out that kqueue on OS X 10.3.9 was causing kernel
22312 panics. Disable kqueue on all OS X Tors.
22313 - Fix RPM: remove duplicate line accidentally added to the rpm
22315 - Disable threads on openbsd too, since its gethostaddr is not
22317 - Tolerate libevent 0.8 since it still works, even though it's
22319 - Enable building on Red Hat 9.0 again.
22320 - Allow the middle hop of the testing circuit to be running any
22321 version, now that most of them have the bugfix to let them connect
22322 to unknown servers. This will allow reachability testing to work
22323 even when 0.0.9.7-0.0.9.9 become obsolete.
22324 - Handle relay cells with rh.length too large. This prevents
22325 a potential attack that could read arbitrary memory (maybe even
22326 keys) from the exit server's process.
22327 - We screwed up the dirport reachability testing when we don't yet
22328 have a cached version of the directory. Hopefully now fixed.
22329 - Clean up router_load_single_router() (used by the controller),
22330 so it doesn't seg fault on error.
22331 - Fix a minor memory leak when somebody establishes an introduction
22332 point at your Tor server.
22333 - If a socks connection ends because read fails, don't warn that
22334 you're not sending a socks reply back.
22337 - Add HttpProxyAuthenticator config option too, that works like
22338 the HttpsProxyAuthenticator config option.
22339 - Encode hashed controller passwords in hex instead of base64,
22340 to make it easier to write controllers.
22343 Changes in version 0.1.0.7-rc - 2005-05-17
22345 - Fix a bug in the OS X package installer that prevented it from
22346 installing on Tiger.
22347 - Fix a script bug in the OS X package installer that made it
22348 complain during installation.
22349 - Find libevent even if it's hiding in /usr/local/ and your
22350 CFLAGS and LDFLAGS don't tell you to look there.
22351 - Be able to link with libevent as a shared library (the default
22352 after 1.0d), even if it's hiding in /usr/local/lib and even
22353 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
22354 assuming you're running gcc. Otherwise fail and give a useful
22356 - Fix a bug in the RPM packager: set home directory for _tor to
22357 something more reasonable when first installing.
22358 - Free a minor amount of memory that is still reachable on exit.
22361 Changes in version 0.1.0.6-rc - 2005-05-14
22363 - Implement --disable-threads configure option. Disable threads on
22364 netbsd by default, because it appears to have no reentrant resolver
22366 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
22367 release (1.1) detects and disables kqueue if it's broken.
22368 - Append default exit policy before checking for implicit internal
22369 addresses. Now we don't log a bunch of complaints on startup
22370 when using the default exit policy.
22371 - Some people were putting "Address " in their torrc, and they had
22372 a buggy resolver that resolved " " to 0.0.0.0. Oops.
22373 - If DataDir is ~/.tor, and that expands to /.tor, then default to
22374 LOCALSTATEDIR/tor instead.
22375 - Fix fragmented-message bug in TorControl.py.
22376 - Resolve a minor bug which would prevent unreachable dirports
22377 from getting suppressed in the published descriptor.
22378 - When the controller gave us a new descriptor, we weren't resolving
22379 it immediately, so Tor would think its address was 0.0.0.0 until
22380 we fetched a new directory.
22381 - Fix an uppercase/lowercase case error in suppressing a bogus
22382 libevent warning on some Linuxes.
22385 - Begin scrubbing sensitive strings from logs by default. Turn off
22386 the config option SafeLogging if you need to do debugging.
22387 - Switch to a new buffer management algorithm, which tries to avoid
22388 reallocing and copying quite as much. In first tests it looks like
22389 it uses *more* memory on average, but less cpu.
22390 - First cut at support for "create-fast" cells. Clients can use
22391 these when extending to their first hop, since the TLS already
22392 provides forward secrecy and authentication. Not enabled on
22394 - When dirservers refuse a router descriptor, we now log its
22395 contactinfo, platform, and the poster's IP address.
22396 - Call tor_free_all instead of connections_free_all after forking, to
22397 save memory on systems that need to fork.
22398 - Whine at you if you're a server and you don't set your contactinfo.
22399 - Implement --verify-config command-line option to check if your torrc
22400 is valid without actually launching Tor.
22401 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
22402 rather than just rejecting it.
22405 Changes in version 0.1.0.5-rc - 2005-04-27
22407 - Stop trying to print a null pointer if an OR conn fails because
22408 we didn't like its cert.
22410 - Switch our internal buffers implementation to use a ring buffer,
22411 to hopefully improve performance for fast servers a lot.
22412 - Add HttpsProxyAuthenticator support (basic auth only), based
22413 on patch from Adam Langley.
22414 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
22415 the fast servers that have been joining lately.
22416 - Give hidden service accesses extra time on the first attempt,
22417 since 60 seconds is often only barely enough. This might improve
22419 - Improve performance for dirservers: stop re-parsing the whole
22420 directory every time you regenerate it.
22421 - Add more debugging info to help us find the weird dns freebsd
22422 pthreads bug; cleaner debug messages to help track future issues.
22425 Changes in version 0.0.9.9 - 2005-04-23
22426 o Bugfixes on 0.0.9.x:
22427 - If unofficial Tor clients connect and send weird TLS certs, our
22428 Tor server triggers an assert. This release contains a minimal
22429 backport from the broader fix that we put into 0.1.0.4-rc.
22432 Changes in version 0.1.0.4-rc - 2005-04-23
22434 - If unofficial Tor clients connect and send weird TLS certs, our
22435 Tor server triggers an assert. Stop asserting, and start handling
22436 TLS errors better in other situations too.
22437 - When the controller asks us to tell it about all the debug-level
22438 logs, it turns out we were generating debug-level logs while
22439 telling it about them, which turns into a bad loop. Now keep
22440 track of whether you're sending a debug log to the controller,
22441 and don't log when you are.
22442 - Fix the "postdescriptor" feature of the controller interface: on
22443 non-complete success, only say "done" once.
22445 - Clients are now willing to load balance over up to 2mB, not 1mB,
22446 of advertised bandwidth capacity.
22447 - Add a NoPublish config option, so you can be a server (e.g. for
22448 testing running Tor servers in other Tor networks) without
22449 publishing your descriptor to the primary dirservers.
22452 Changes in version 0.1.0.3-rc - 2005-04-08
22453 o Improvements on 0.1.0.2-rc:
22454 - Client now retries when streams end early for 'hibernating' or
22455 'resource limit' reasons, rather than failing them.
22456 - More automated handling for dirserver operators:
22457 - Automatically approve nodes running 0.1.0.2-rc or later,
22458 now that the the reachability detection stuff is working.
22459 - Now we allow two unverified servers with the same nickname
22460 but different keys. But if a nickname is verified, only that
22461 nickname+key are allowed.
22462 - If you're an authdirserver connecting to an address:port,
22463 and it's not the OR you were expecting, forget about that
22464 descriptor. If he *was* the one you were expecting, then forget
22465 about all other descriptors for that address:port.
22466 - Allow servers to publish descriptors from 12 hours in the future.
22467 Corollary: only whine about clock skew from the dirserver if
22468 he's a trusted dirserver (since now even verified servers could
22469 have quite wrong clocks).
22470 - Adjust maximum skew and age for rendezvous descriptors: let skew
22471 be 48 hours rather than 90 minutes.
22472 - Efficiency improvements:
22473 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
22474 it much faster to look up a circuit for each relay cell.
22475 - Remove most calls to assert_all_pending_dns_resolves_ok(),
22476 since they're eating our cpu on exit nodes.
22477 - Stop wasting time doing a case insensitive comparison for every
22478 dns name every time we do any lookup. Canonicalize the names to
22479 lowercase and be done with it.
22480 - Start sending 'truncated' cells back rather than destroy cells,
22481 if the circuit closes in front of you. This means we won't have
22482 to abandon partially built circuits.
22483 - Only warn once per nickname from add_nickname_list_to_smartlist
22484 per failure, so an entrynode or exitnode choice that's down won't
22486 - Put a note in the torrc about abuse potential with the default
22488 - Revise control spec and implementation to allow all log messages to
22489 be sent to controller with their severities intact (suggested by
22490 Matt Edman). Update TorControl to handle new log event types.
22491 - Provide better explanation messages when controller's POSTDESCRIPTOR
22493 - Stop putting nodename in the Platform string in server descriptors.
22494 It doesn't actually help, and it is confusing/upsetting some people.
22496 o Bugfixes on 0.1.0.2-rc:
22497 - We were printing the host mask wrong in exit policies in server
22498 descriptors. This isn't a critical bug though, since we were still
22499 obeying the exit policy internally.
22500 - Fix Tor when compiled with libevent but without pthreads: move
22501 connection_unregister() from _connection_free() to
22503 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
22504 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
22505 when we look through the connection array, we'll find any of the
22506 cpu/dnsworkers. This is no good.
22508 o Bugfixes on 0.0.9.8:
22509 - Fix possible bug on threading platforms (e.g. win32) which was
22510 leaking a file descriptor whenever a cpuworker or dnsworker died.
22511 - When using preferred entry or exit nodes, ignore whether the
22512 circuit wants uptime or capacity. They asked for the nodes, they
22514 - chdir() to your datadirectory at the *end* of the daemonize process,
22515 not the beginning. This was a problem because the first time you
22516 run tor, if your datadir isn't there, and you have runasdaemon set
22517 to 1, it will try to chdir to it before it tries to create it. Oops.
22518 - Handle changed router status correctly when dirserver reloads
22519 fingerprint file. We used to be dropping all unverified descriptors
22520 right then. The bug was hidden because we would immediately
22521 fetch a directory from another dirserver, which would include the
22522 descriptors we just dropped.
22523 - When we're connecting to an OR and he's got a different nickname/key
22524 than we were expecting, only complain loudly if we're an OP or a
22525 dirserver. Complaining loudly to the OR admins just confuses them.
22526 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
22527 artificially capped at 500kB.
22530 Changes in version 0.0.9.8 - 2005-04-07
22531 o Bugfixes on 0.0.9.x:
22532 - We have a bug that I haven't found yet. Sometimes, very rarely,
22533 cpuworkers get stuck in the 'busy' state, even though the cpuworker
22534 thinks of itself as idle. This meant that no new circuits ever got
22535 established. Here's a workaround to kill any cpuworker that's been
22536 busy for more than 100 seconds.
22539 Changes in version 0.1.0.2-rc - 2005-04-01
22540 o Bugfixes on 0.1.0.1-rc:
22541 - Fixes on reachability detection:
22542 - Don't check for reachability while hibernating.
22543 - If ORPort is reachable but DirPort isn't, still publish the
22544 descriptor, but zero out DirPort until it's found reachable.
22545 - When building testing circs for ORPort testing, use only
22546 high-bandwidth nodes, so fewer circuits fail.
22547 - Complain about unreachable ORPort separately from unreachable
22548 DirPort, so the user knows what's going on.
22549 - Make sure we only conclude ORPort reachability if we didn't
22550 initiate the conn. Otherwise we could falsely conclude that
22551 we're reachable just because we connected to the guy earlier
22552 and he used that same pipe to extend to us.
22553 - Authdirservers shouldn't do ORPort reachability detection,
22554 since they're in clique mode, so it will be rare to find a
22555 server not already connected to them.
22556 - When building testing circuits, always pick middle hops running
22557 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
22558 bug. (This is a kludge; it will go away when 0.0.9.x becomes
22560 - When we decide we're reachable, actually publish our descriptor
22562 - Fix bug in redirectstream in the controller.
22563 - Fix the state descriptor strings so logs don't claim edge streams
22564 are in a different state than they actually are.
22565 - Use recent libevent features when possible (this only really affects
22566 win32 and osx right now, because the new libevent with these
22567 features hasn't been released yet). Add code to suppress spurious
22569 - Prevent possible segfault in connection_close_unattached_ap().
22570 - Fix newlines on torrc in win32.
22571 - Improve error msgs when tor-resolve fails.
22573 o Improvements on 0.0.9.x:
22574 - New experimental script tor/contrib/ExerciseServer.py (needs more
22575 work) that uses the controller interface to build circuits and
22576 fetch pages over them. This will help us bootstrap servers that
22577 have lots of capacity but haven't noticed it yet.
22578 - New experimental script tor/contrib/PathDemo.py (needs more work)
22579 that uses the controller interface to let you choose whole paths
22581 "<hostname>.<path,separated by dots>.<length of path>.path"
22582 - When we've connected to an OR and handshaked but didn't like
22583 the result, we were closing the conn without sending destroy
22584 cells back for pending circuits. Now send those destroys.
22587 Changes in version 0.0.9.7 - 2005-04-01
22588 o Bugfixes on 0.0.9.x:
22589 - Fix another race crash bug (thanks to Glenn Fink for reporting).
22590 - Compare identity to identity, not to nickname, when extending to
22591 a router not already in the directory. This was preventing us from
22592 extending to unknown routers. Oops.
22593 - Make sure to create OS X Tor user in <500 range, so we aren't
22594 creating actual system users.
22595 - Note where connection-that-hasn't-sent-end was marked, and fix
22596 a few really loud instances of this harmless bug (it's fixed more
22600 Changes in version 0.1.0.1-rc - 2005-03-28
22602 - Add reachability testing. Your Tor server will automatically try
22603 to see if its ORPort and DirPort are reachable from the outside,
22604 and it won't upload its descriptor until it decides they are.
22605 - Handle unavailable hidden services better. Handle slow or busy
22606 hidden services better.
22607 - Add support for CONNECTing through https proxies, with "HttpsProxy"
22609 - New exit policy: accept most low-numbered ports, rather than
22610 rejecting most low-numbered ports.
22611 - More Tor controller support (still experimental). See
22612 http://tor.eff.org/doc/control-spec.txt for all the new features,
22613 including signals to emulate unix signals from any platform;
22614 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
22615 closestream; closecircuit; etc.
22616 - Make nt services work and start on startup on win32 (based on
22617 patch by Matt Edman).
22618 - Add a new AddressMap config directive to rewrite incoming socks
22619 addresses. This lets you, for example, declare an implicit
22620 required exit node for certain sites.
22621 - Add a new TrackHostExits config directive to trigger addressmaps
22622 for certain incoming socks addresses -- for sites that break when
22623 your exit keeps changing (based on patch by Mike Perry).
22624 - Redo the client-side dns cache so it's just an addressmap too.
22625 - Notice when our IP changes, and reset stats/uptime/reachability.
22626 - When an application is using socks5, give him the whole variety of
22627 potential socks5 responses (connect refused, host unreachable, etc),
22628 rather than just "success" or "failure".
22629 - A more sane version numbering system. See
22630 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
22631 - New contributed script "exitlist": a simple python script to
22632 parse directories and find Tor nodes that exit to listed
22634 - New contributed script "privoxy-tor-toggle" to toggle whether
22635 Privoxy uses Tor. Seems to be configured for Debian by default.
22636 - Report HTTP reasons to client when getting a response from directory
22637 servers -- so you can actually know what went wrong.
22638 - New config option MaxAdvertisedBandwidth which lets you advertise
22639 a low bandwidthrate (to not attract as many circuits) while still
22640 allowing a higher bandwidthrate in reality.
22642 o Robustness/stability fixes:
22643 - Make Tor use Niels Provos's libevent instead of its current
22644 poll-but-sometimes-select mess. This will let us use faster async
22645 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
22647 - pthread support now too. This was forced because when we forked,
22648 we ended up wasting a lot of duplicate ram over time. Also switch
22649 to foo_r versions of some library calls to allow reentry and
22651 - Better handling for heterogeneous / unreliable nodes:
22652 - Annotate circuits w/ whether they aim to contain high uptime nodes
22653 and/or high capacity nodes. When building circuits, choose
22655 - This means that every single node in an intro rend circuit,
22656 not just the last one, will have a minimum uptime.
22657 - New config option LongLivedPorts to indicate application streams
22658 that will want high uptime circuits.
22659 - Servers reset uptime when a dir fetch entirely fails. This
22660 hopefully reflects stability of the server's network connectivity.
22661 - If somebody starts his tor server in Jan 2004 and then fixes his
22662 clock, don't make his published uptime be a year.
22663 - Reset published uptime when you wake up from hibernation.
22664 - Introduce a notion of 'internal' circs, which are chosen without
22665 regard to the exit policy of the last hop. Intro and rendezvous
22666 circs must be internal circs, to avoid leaking information. Resolve
22667 and connect streams can use internal circs if they want.
22668 - New circuit pooling algorithm: make sure to have enough circs around
22669 to satisfy any predicted ports, and also make sure to have 2 internal
22670 circs around if we've required internal circs lately (and with high
22671 uptime if we've seen that lately too).
22672 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
22673 which describes how often we retry making new circuits if current
22674 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
22675 how long we're willing to make use of an already-dirty circuit.
22676 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
22677 circ as necessary, if there are any completed ones lying around
22678 when we try to launch one.
22679 - Make hidden services try to establish a rendezvous for 30 seconds,
22680 rather than for n (where n=3) attempts to build a circuit.
22681 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
22682 "ShutdownWaitLength".
22683 - Try to be more zealous about calling connection_edge_end when
22684 things go bad with edge conns in connection.c.
22685 - Revise tor-spec to add more/better stream end reasons.
22686 - Revise all calls to connection_edge_end to avoid sending "misc",
22687 and to take errno into account where possible.
22690 - Fix a race condition that can trigger an assert, when we have a
22691 pending create cell and an OR connection fails right then.
22692 - Fix several double-mark-for-close bugs, e.g. where we were finding
22693 a conn for a cell even if that conn is already marked for close.
22694 - Make sequence of log messages when starting on win32 with no config
22695 file more reasonable.
22696 - When choosing an exit node for a new non-internal circ, don't take
22697 into account whether it'll be useful for any pending x.onion
22698 addresses -- it won't.
22699 - Turn addr_policy_compare from a tristate to a quadstate; this should
22700 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
22701 for google.com" problem.
22702 - Make "platform" string in descriptor more accurate for Win32 servers,
22703 so it's not just "unknown platform".
22704 - Fix an edge case in parsing config options (thanks weasel).
22705 If they say "--" on the commandline, it's not an option.
22706 - Reject odd-looking addresses at the client (e.g. addresses that
22707 contain a colon), rather than having the server drop them because
22709 - tor-resolve requests were ignoring .exit if there was a working circuit
22710 they could use instead.
22711 - REUSEADDR on normal platforms means you can rebind to the port
22712 right after somebody else has let it go. But REUSEADDR on win32
22713 means to let you bind to the port _even when somebody else
22714 already has it bound_! So, don't do that on Win32.
22715 - Change version parsing logic: a version is "obsolete" if it is not
22716 recommended and (1) there is a newer recommended version in the
22717 same series, or (2) there are no recommended versions in the same
22718 series, but there are some recommended versions in a newer series.
22719 A version is "new" if it is newer than any recommended version in
22721 - Stop most cases of hanging up on a socks connection without sending
22725 - Require BandwidthRate to be at least 20kB/s for servers.
22726 - When a dirserver causes you to give a warn, mention which dirserver
22728 - New config option DirAllowPrivateAddresses for authdirservers.
22729 Now by default they refuse router descriptors that have non-IP or
22730 private-IP addresses.
22731 - Stop publishing socksport in the directory, since it's not
22732 actually meant to be public. For compatibility, publish a 0 there
22734 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
22735 smart" value, that is low for servers and high for clients.
22736 - If our clock jumps forward by 100 seconds or more, assume something
22737 has gone wrong with our network and abandon all not-yet-used circs.
22738 - Warn when exit policy implicitly allows local addresses.
22739 - If we get an incredibly skewed timestamp from a dirserver mirror
22740 that isn't a verified OR, don't warn -- it's probably him that's
22742 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
22743 cookies to disk and doesn't log each web request to disk. (Thanks
22744 to Brett Carrington for pointing this out.)
22745 - When a client asks us for a dir mirror and we don't have one,
22746 launch an attempt to get a fresh one.
22747 - If we're hibernating and we get a SIGINT, exit immediately.
22748 - Add --with-dmalloc ./configure option, to track memory leaks.
22749 - And try to free all memory on closing, so we can detect what
22751 - Cache local dns resolves correctly even when they're .exit
22753 - Give a better warning when some other server advertises an
22754 ORPort that is actually an apache running ssl.
22755 - Add "opt hibernating 1" to server descriptor to make it clearer
22756 whether the server is hibernating.
22759 Changes in version 0.0.9.6 - 2005-03-24
22760 o Bugfixes on 0.0.9.x (crashes and asserts):
22761 - Add new end stream reasons to maintainance branch. Fix bug where
22762 reason (8) could trigger an assert. Prevent bug from recurring.
22763 - Apparently win32 stat wants paths to not end with a slash.
22764 - Fix assert triggers in assert_cpath_layer_ok(), where we were
22765 blowing away the circuit that conn->cpath_layer points to, then
22766 checking to see if the circ is well-formed. Backport check to make
22767 sure we dont use the cpath on a closed connection.
22768 - Prevent circuit_resume_edge_reading_helper() from trying to package
22769 inbufs for marked-for-close streams.
22770 - Don't crash on hup if your options->address has become unresolvable.
22771 - Some systems (like OS X) sometimes accept() a connection and tell
22772 you the remote host is 0.0.0.0:0. If this happens, due to some
22773 other mis-features, we get confused; so refuse the conn for now.
22775 o Bugfixes on 0.0.9.x (other):
22776 - Fix harmless but scary "Unrecognized content encoding" warn message.
22777 - Add new stream error reason: TORPROTOCOL reason means "you are not
22778 speaking a version of Tor I understand; say bye-bye to your stream."
22779 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
22780 into the future, now that we are more tolerant of skew. This
22781 resolves a bug where a Tor server would refuse to cache a directory
22782 because all the directories it gets are too far in the future;
22783 yet the Tor server never logs any complaints about clock skew.
22784 - Mac packaging magic: make man pages useable, and do not overwrite
22785 existing torrc files.
22786 - Make OS X log happily to /var/log/tor/tor.log
22789 Changes in version 0.0.9.5 - 2005-02-22
22790 o Bugfixes on 0.0.9.x:
22791 - Fix an assert race at exit nodes when resolve requests fail.
22792 - Stop picking unverified dir mirrors--it only leads to misery.
22793 - Patch from Matt Edman to make NT services work better. Service
22794 support is still not compiled into the executable by default.
22795 - Patch from Dmitri Bely so the Tor service runs better under
22796 the win32 SYSTEM account.
22797 - Make tor-resolve actually work (?) on Win32.
22798 - Fix a sign bug when getrlimit claims to have 4+ billion
22799 file descriptors available.
22800 - Stop refusing to start when bandwidthburst == bandwidthrate.
22801 - When create cells have been on the onion queue more than five
22802 seconds, just send back a destroy and take them off the list.
22805 Changes in version 0.0.9.4 - 2005-02-03
22806 o Bugfixes on 0.0.9:
22807 - Fix an assert bug that took down most of our servers: when
22808 a server claims to have 1 GB of bandwidthburst, don't
22810 - Don't crash as badly if we have spawned the max allowed number
22811 of dnsworkers, or we're out of file descriptors.
22812 - Block more file-sharing ports in the default exit policy.
22813 - MaxConn is now automatically set to the hard limit of max
22814 file descriptors we're allowed (ulimit -n), minus a few for
22816 - Give a clearer message when servers need to raise their
22817 ulimit -n when they start running out of file descriptors.
22818 - SGI Compatibility patches from Jan Schaumann.
22819 - Tolerate a corrupt cached directory better.
22820 - When a dirserver hasn't approved your server, list which one.
22821 - Go into soft hibernation after 95% of the bandwidth is used,
22822 not 99%. This is especially important for daily hibernators who
22823 have a small accounting max. Hopefully it will result in fewer
22824 cut connections when the hard hibernation starts.
22825 - Load-balance better when using servers that claim more than
22826 800kB/s of capacity.
22827 - Make NT services work (experimental, only used if compiled in).
22830 Changes in version 0.0.9.3 - 2005-01-21
22831 o Bugfixes on 0.0.9:
22832 - Backport the cpu use fixes from main branch, so busy servers won't
22833 need as much processor time.
22834 - Work better when we go offline and then come back, or when we
22835 run Tor at boot before the network is up. We do this by
22836 optimistically trying to fetch a new directory whenever an
22837 application request comes in and we think we're offline -- the
22838 human is hopefully a good measure of when the network is back.
22839 - Backport some minimal hidserv bugfixes: keep rend circuits open as
22840 long as you keep using them; actually publish hidserv descriptors
22841 shortly after they change, rather than waiting 20-40 minutes.
22842 - Enable Mac startup script by default.
22843 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
22844 - When you update AllowUnverifiedNodes or FirewallPorts via the
22845 controller's setconf feature, we were always appending, never
22847 - When you update HiddenServiceDir via setconf, it was screwing up
22848 the order of reading the lines, making it fail.
22849 - Do not rewrite a cached directory back to the cache; otherwise we
22850 will think it is recent and not fetch a newer one on startup.
22851 - Workaround for webservers that lie about Content-Encoding: Tor
22852 now tries to autodetect compressed directories and compression
22853 itself. This lets us Proxypass dir fetches through apache.
22856 Changes in version 0.0.9.2 - 2005-01-04
22857 o Bugfixes on 0.0.9 (crashes and asserts):
22858 - Fix an assert on startup when the disk is full and you're logging
22860 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
22861 style address, then we'd crash.
22862 - Fix an assert trigger when the running-routers string we get from
22863 a dirserver is broken.
22864 - Make worker threads start and run on win32. Now win32 servers
22866 - Bandaid (not actually fix, but now it doesn't crash) an assert
22867 where the dns worker dies mysteriously and the main Tor process
22868 doesn't remember anything about the address it was resolving.
22870 o Bugfixes on 0.0.9 (Win32):
22871 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
22872 name out of the warning/assert messages.
22873 - Fix a superficial "unhandled error on read" bug on win32.
22874 - The win32 installer no longer requires a click-through for our
22875 license, since our Free Software license grants rights but does not
22877 - Win32: When connecting to a dirserver fails, try another one
22878 immediately. (This was already working for non-win32 Tors.)
22879 - Stop trying to parse $HOME on win32 when hunting for default
22881 - Make tor-resolve.c work on win32 by calling network_init().
22883 o Bugfixes on 0.0.9 (other):
22884 - Make 0.0.9.x build on Solaris again.
22885 - Due to a fencepost error, we were blowing away the \n when reporting
22886 confvalue items in the controller. So asking for multiple config
22887 values at once couldn't work.
22888 - When listing circuits that are pending on an opening OR connection,
22889 if we're an OR we were listing circuits that *end* at us as
22890 being pending on every listener, dns/cpu worker, etc. Stop that.
22891 - Dirservers were failing to create 'running-routers' or 'directory'
22892 strings if we had more than some threshold of routers. Fix them so
22893 they can handle any number of routers.
22894 - Fix a superficial "Duplicate mark for close" bug.
22895 - Stop checking for clock skew for OR connections, even for servers.
22896 - Fix a fencepost error that was chopping off the last letter of any
22897 nickname that is the maximum allowed nickname length.
22898 - Update URLs in log messages so they point to the new website.
22899 - Fix a potential problem in mangling server private keys while
22900 writing to disk (not triggered yet, as far as we know).
22901 - Include the licenses for other free software we include in Tor,
22902 now that we're shipping binary distributions more regularly.
22905 Changes in version 0.0.9.1 - 2004-12-15
22906 o Bugfixes on 0.0.9:
22907 - Make hibernation actually work.
22908 - Make HashedControlPassword config option work.
22909 - When we're reporting event circuit status to a controller,
22910 don't use the stream status code.
22913 Changes in version 0.0.9 - 2004-12-12
22915 - Clean up manpage and torrc.sample file.
22916 - Clean up severities and text of log warnings.
22918 - Make servers trigger an assert when they enter hibernation.
22921 Changes in version 0.0.9rc7 - 2004-12-08
22922 o Bugfixes on 0.0.9rc:
22923 - Fix a stack-trashing crash when an exit node begins hibernating.
22924 - Avoid looking at unallocated memory while considering which
22925 ports we need to build circuits to cover.
22926 - Stop a sigpipe: when an 'end' cell races with eof from the app,
22927 we shouldn't hold-open-until-flush if the eof arrived first.
22928 - Fix a bug with init_cookie_authentication() in the controller.
22929 - When recommending new-format log lines, if the upper bound is
22930 LOG_ERR, leave it implicit.
22932 o Bugfixes on 0.0.8.1:
22933 - Fix a whole slew of memory leaks.
22934 - Fix isspace() and friends so they still make Solaris happy
22935 but also so they don't trigger asserts on win32.
22936 - Fix parse_iso_time on platforms without strptime (eg win32).
22937 - win32: tolerate extra "readable" events better.
22938 - win32: when being multithreaded, leave parent fdarray open.
22939 - Make unit tests work on win32.
22942 Changes in version 0.0.9rc6 - 2004-12-06
22943 o Bugfixes on 0.0.9pre:
22944 - Clean up some more integer underflow opportunities (not exploitable
22946 - While hibernating, hup should not regrow our listeners.
22947 - Send an end to the streams we close when we hibernate, rather
22948 than just chopping them off.
22949 - React to eof immediately on non-open edge connections.
22951 o Bugfixes on 0.0.8.1:
22952 - Calculate timeout for waiting for a connected cell from the time
22953 we sent the begin cell, not from the time the stream started. If
22954 it took a long time to establish the circuit, we would time out
22955 right after sending the begin cell.
22956 - Fix router_compare_addr_to_addr_policy: it was not treating a port
22957 of * as always matching, so we were picking reject *:* nodes as
22958 exit nodes too. Oops.
22961 - New circuit building strategy: keep a list of ports that we've
22962 used in the past 6 hours, and always try to have 2 circuits open
22963 or on the way that will handle each such port. Seed us with port
22964 80 so web users won't complain that Tor is "slow to start up".
22965 - Make kill -USR1 dump more useful stats about circuits.
22966 - When warning about retrying or giving up, print the address, so
22967 the user knows which one it's talking about.
22968 - If you haven't used a clean circuit in an hour, throw it away,
22969 just to be on the safe side. (This means after 6 hours a totally
22970 unused Tor client will have no circuits open.)
22973 Changes in version 0.0.9rc5 - 2004-12-01
22974 o Bugfixes on 0.0.8.1:
22975 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
22976 - Let resolve conns retry/expire also, rather than sticking around
22978 - If we are using select, make sure we stay within FD_SETSIZE.
22980 o Bugfixes on 0.0.9pre:
22981 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
22982 but doesn't seem to be currently; thanks to Ilja van Sprundel for
22984 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
22985 instead. Impose minima and maxima for all *Period options; impose
22986 even tighter maxima for fetching if we are a caching dirserver.
22987 Clip rather than rejecting.
22988 - Fetch cached running-routers from servers that serve it (that is,
22989 authdirservers and servers running 0.0.9rc5-cvs or later.)
22992 - Accept *:706 (silc) in default exit policy.
22993 - Implement new versioning format for post 0.1.
22994 - Support "foo.nickname.exit" addresses, to let Alice request the
22995 address "foo" as viewed by exit node "nickname". Based on a patch
22997 - Make tor --version --version dump the cvs Id of every file.
23000 Changes in version 0.0.9rc4 - 2004-11-28
23001 o Bugfixes on 0.0.8.1:
23002 - Make windows sockets actually non-blocking (oops), and handle
23003 win32 socket errors better.
23005 o Bugfixes on 0.0.9rc1:
23006 - Actually catch the -USR2 signal.
23009 Changes in version 0.0.9rc3 - 2004-11-25
23010 o Bugfixes on 0.0.8.1:
23011 - Flush the log file descriptor after we print "Tor opening log file",
23012 so we don't see those messages days later.
23014 o Bugfixes on 0.0.9rc1:
23015 - Make tor-resolve work again.
23016 - Avoid infinite loop in tor-resolve if tor hangs up on it.
23017 - Fix an assert trigger for clients/servers handling resolves.
23020 Changes in version 0.0.9rc2 - 2004-11-24
23021 o Bugfixes on 0.0.9rc1:
23022 - I broke socks5 support while fixing the eof bug.
23023 - Allow unitless bandwidths and intervals; they default to bytes
23025 - New servers don't start out hibernating; they are active until
23026 they run out of bytes, so they have a better estimate of how
23027 long it takes, and so their operators can know they're working.
23030 Changes in version 0.0.9rc1 - 2004-11-23
23031 o Bugfixes on 0.0.8.1:
23032 - Finally fix a bug that's been plaguing us for a year:
23033 With high load, circuit package window was reaching 0. Whenever
23034 we got a circuit-level sendme, we were reading a lot on each
23035 socket, but only writing out a bit. So we would eventually reach
23036 eof. This would be noticed and acted on even when there were still
23037 bytes sitting in the inbuf.
23038 - When poll() is interrupted, we shouldn't believe the revents values.
23040 o Bugfixes on 0.0.9pre6:
23041 - Fix hibernate bug that caused pre6 to be broken.
23042 - Don't keep rephist info for routers that haven't had activity for
23043 24 hours. (This matters now that clients have keys, since we track
23045 - Never call close_temp_logs while validating log options.
23046 - Fix backslash-escaping on tor.sh.in and torctl.in.
23049 - Implement weekly/monthly/daily accounting: now you specify your
23050 hibernation properties by
23051 AccountingMax N bytes|KB|MB|GB|TB
23052 AccountingStart day|week|month [day] HH:MM
23053 Defaults to "month 1 0:00".
23054 - Let bandwidth and interval config options be specified as 5 bytes,
23055 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
23056 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
23057 get back to normal.)
23058 - If your requested entry or exit node has advertised bandwidth 0,
23060 - Be more greedy about filling up relay cells -- we try reading again
23061 once we've processed the stuff we read, in case enough has arrived
23062 to fill the last cell completely.
23063 - Apply NT service patch from Osamu Fujino. Still needs more work.
23066 Changes in version 0.0.9pre6 - 2004-11-15
23067 o Bugfixes on 0.0.8.1:
23068 - Fix assert failure on malformed socks4a requests.
23069 - Use identity comparison, not nickname comparison, to choose which
23070 half of circuit-ID-space each side gets to use. This is needed
23071 because sometimes we think of a router as a nickname, and sometimes
23072 as a hex ID, and we can't predict what the other side will do.
23073 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
23074 write() call will fail and we handle it there.
23075 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
23076 and smartlist_len, which are two major profiling offenders.
23078 o Bugfixes on 0.0.9pre5:
23079 - Fix a bug in read_all that was corrupting config files on windows.
23080 - When we're raising the max number of open file descriptors to
23081 'unlimited', don't log that we just raised it to '-1'.
23082 - Include event code with events, as required by control-spec.txt.
23083 - Don't give a fingerprint when clients do --list-fingerprint:
23084 it's misleading, because it will never be the same again.
23085 - Stop using strlcpy in tor_strndup, since it was slowing us
23087 - Remove warn on startup about missing cached-directory file.
23088 - Make kill -USR1 work again.
23089 - Hibernate if we start tor during the "wait for wakeup-time" phase
23090 of an accounting interval. Log our hibernation plans better.
23091 - Authoritative dirservers now also cache their directory, so they
23092 have it on start-up.
23095 - Fetch running-routers; cache running-routers; compress
23096 running-routers; serve compressed running-routers.z
23097 - Add NSI installer script contributed by J Doe.
23098 - Commit VC6 and VC7 workspace/project files.
23099 - Commit a tor.spec for making RPM files, with help from jbash.
23100 - Add contrib/torctl.in contributed by Glenn Fink.
23101 - Implement the control-spec's SAVECONF command, to write your
23102 configuration to torrc.
23103 - Get cookie authentication for the controller closer to working.
23104 - Include control-spec.txt in the tarball.
23105 - When set_conf changes our server descriptor, upload a new copy.
23106 But don't upload it too often if there are frequent changes.
23107 - Document authentication config in man page, and document signals
23109 - Clean up confusing parts of man page and torrc.sample.
23110 - Make expand_filename handle ~ and ~username.
23111 - Use autoconf to enable largefile support where necessary. Use
23112 ftello where available, since ftell can fail at 2GB.
23113 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
23114 log more informatively.
23115 - Give a slightly more useful output for "tor -h".
23116 - Refuse application socks connections to port 0.
23117 - Check clock skew for verified servers, but allow unverified
23118 servers and clients to have any clock skew.
23119 - Break DirFetchPostPeriod into:
23120 - DirFetchPeriod for fetching full directory,
23121 - StatusFetchPeriod for fetching running-routers,
23122 - DirPostPeriod for posting server descriptor,
23123 - RendPostPeriod for posting hidden service descriptors.
23124 - Make sure the hidden service descriptors are at a random offset
23125 from each other, to hinder linkability.
23128 Changes in version 0.0.9pre5 - 2004-11-09
23129 o Bugfixes on 0.0.9pre4:
23130 - Fix a seg fault in unit tests (doesn't affect main program).
23131 - Fix an assert bug where a hidden service provider would fail if
23132 the first hop of his rendezvous circuit was down.
23133 - Hidden service operators now correctly handle version 1 style
23134 INTRODUCE1 cells (nobody generates them still, so not a critical
23136 - If do_hup fails, actually notice.
23137 - Handle more errnos from accept() without closing the listener.
23138 Some OpenBSD machines were closing their listeners because
23139 they ran out of file descriptors.
23140 - Send resolve cells to exit routers that are running a new
23141 enough version of the resolve code to work right.
23142 - Better handling of winsock includes on non-MSV win32 compilers.
23143 - Some people had wrapped their tor client/server in a script
23144 that would restart it whenever it died. This did not play well
23145 with our "shut down if your version is obsolete" code. Now people
23146 don't fetch a new directory if their local cached version is
23148 - Make our autogen.sh work on ksh as well as bash.
23151 - Hibernation: New config option "AccountingMaxKB" lets you
23152 set how many KBytes per month you want to allow your server to
23153 consume. Rather than spreading those bytes out evenly over the
23154 month, we instead hibernate for some of the month and pop up
23155 at a deterministic time, work until the bytes are consumed, then
23156 hibernate again. Config option "MonthlyAccountingStart" lets you
23157 specify which day of the month your billing cycle starts on.
23158 - Control interface: a separate program can now talk to your
23159 client/server over a socket, and get/set config options, receive
23160 notifications of circuits and streams starting/finishing/dying,
23161 bandwidth used, etc. The next step is to get some GUIs working.
23162 Let us know if you want to help out. See doc/control-spec.txt .
23163 - Ship a contrib/tor-control.py as an example script to interact
23164 with the control port.
23165 - "tor --hash-password zzyxz" will output a salted password for
23166 use in authenticating to the control interface.
23167 - New log format in config:
23168 "Log minsev[-maxsev] stdout|stderr|syslog" or
23169 "Log minsev[-maxsev] file /var/foo"
23172 - DirPolicy config option, to let people reject incoming addresses
23173 from their dirserver.
23174 - "tor --list-fingerprint" will list your identity key fingerprint
23176 - Add "pass" target for RedirectExit, to make it easier to break
23177 out of a sequence of RedirectExit rules.
23178 - Clients now generate a TLS cert too, in preparation for having
23179 them act more like real nodes.
23180 - Ship src/win32/ in the tarball, so people can use it to build.
23181 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
23183 - New "router-status" line in directory, to better bind each verified
23184 nickname to its identity key.
23185 - Deprecate unofficial config option abbreviations, and abbreviations
23186 not on the command line.
23187 - Add a pure-C tor-resolve implementation.
23188 - Use getrlimit and friends to ensure we can reach MaxConn (currently
23189 1024) file descriptors.
23191 o Code security improvements, inspired by Ilja:
23192 - Replace sprintf with snprintf. (I think they were all safe, but
23194 - Replace strcpy/strncpy with strlcpy in more places.
23195 - Avoid strcat; use snprintf or strlcat instead.
23196 - snprintf wrapper with consistent (though not C99) overflow behavior.
23199 Changes in version 0.0.9pre4 - 2004-10-17
23200 o Bugfixes on 0.0.9pre3:
23201 - If the server doesn't specify an exit policy, use the real default
23202 exit policy, not reject *:*.
23203 - Ignore fascistfirewall when uploading/downloading hidden service
23204 descriptors, since we go through Tor for those; and when using
23205 an HttpProxy, since we assume it can reach them all.
23206 - When looking for an authoritative dirserver, use only the ones
23207 configured at boot. Don't bother looking in the directory.
23208 - The rest of the fix for get_default_conf_file() on older win32.
23209 - Make 'Routerfile' config option obsolete.
23212 - New 'MyFamily nick1,...' config option for a server to
23213 specify other servers that shouldn't be used in the same circuit
23214 with it. Only believed if nick1 also specifies us.
23215 - New 'NodeFamily nick1,nick2,...' config option for a client to
23216 specify nodes that it doesn't want to use in the same circuit.
23217 - New 'Redirectexit pattern address:port' config option for a
23218 server to redirect exit connections, e.g. to a local squid.
23221 Changes in version 0.0.9pre3 - 2004-10-13
23222 o Bugfixes on 0.0.8.1:
23223 - Better torrc example lines for dirbindaddress and orbindaddress.
23224 - Improved bounds checking on parsed ints (e.g. config options and
23225 the ones we find in directories.)
23226 - Better handling of size_t vs int, so we're more robust on 64
23228 - Fix the rest of the bug where a newly started OR would appear
23229 as unverified even after we've added his fingerprint and hupped
23231 - Fix a bug from 0.0.7: when read() failed on a stream, we would
23232 close it without sending back an end. So 'connection refused'
23233 would simply be ignored and the user would get no response.
23235 o Bugfixes on 0.0.9pre2:
23236 - Serving the cached-on-disk directory to people is bad. We now
23237 provide no directory until we've fetched a fresh one.
23238 - Workaround for bug on windows where cached-directories get crlf
23240 - Make get_default_conf_file() work on older windows too.
23241 - If we write a *:* exit policy line in the descriptor, don't write
23242 any more exit policy lines.
23245 - Use only 0.0.9pre1 and later servers for resolve cells.
23246 - Make the dirservers file obsolete.
23247 - Include a dir-signing-key token in directories to tell the
23248 parsing entity which key is being used to sign.
23249 - Remove the built-in bulky default dirservers string.
23250 - New config option "Dirserver %s:%d [fingerprint]", which can be
23251 repeated as many times as needed. If no dirservers specified,
23252 default to moria1,moria2,tor26.
23253 - Make moria2 advertise a dirport of 80, so people behind firewalls
23254 will be able to get a directory.
23255 - Http proxy support
23256 - Dirservers translate requests for http://%s:%d/x to /x
23257 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
23258 be routed through this host.
23259 - Clients ask for /tor/x rather than /x for new enough dirservers.
23260 This way we can one day coexist peacefully with apache.
23261 - Clients specify a "Host: %s%d" http header, to be compatible
23262 with more proxies, and so running squid on an exit node can work.
23265 Changes in version 0.0.8.1 - 2004-10-13
23267 - Fix a seg fault that can be triggered remotely for Tor
23268 clients/servers with an open dirport.
23269 - Fix a rare assert trigger, where routerinfos for entries in
23270 our cpath would expire while we're building the path.
23271 - Fix a bug in OutboundBindAddress so it (hopefully) works.
23272 - Fix a rare seg fault for people running hidden services on
23273 intermittent connections.
23274 - Fix a bug in parsing opt keywords with objects.
23275 - Fix a stale pointer assert bug when a stream detaches and
23277 - Fix a string format vulnerability (probably not exploitable)
23278 in reporting stats locally.
23279 - Fix an assert trigger: sometimes launching circuits can fail
23280 immediately, e.g. because too many circuits have failed recently.
23281 - Fix a compile warning on 64 bit platforms.
23284 Changes in version 0.0.9pre2 - 2004-10-03
23286 - Make fetching a cached directory work for 64-bit platforms too.
23287 - Make zlib.h a required header, not an optional header.
23290 Changes in version 0.0.9pre1 - 2004-10-01
23292 - Stop using separate defaults for no-config-file and
23293 empty-config-file. Now you have to explicitly turn off SocksPort,
23294 if you don't want it open.
23295 - Fix a bug in OutboundBindAddress so it (hopefully) works.
23296 - Improve man page to mention more of the 0.0.8 features.
23297 - Fix a rare seg fault for people running hidden services on
23298 intermittent connections.
23299 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
23301 - Fix more dns related bugs: send back resolve_failed and end cells
23302 more reliably when the resolve fails, rather than closing the
23303 circuit and then trying to send the cell. Also attach dummy resolve
23304 connections to a circuit *before* calling dns_resolve(), to fix
23305 a bug where cached answers would never be sent in RESOLVED cells.
23306 - When we run out of disk space, or other log writing error, don't
23307 crash. Just stop logging to that log and continue.
23308 - We were starting to daemonize before we opened our logs, so if
23309 there were any problems opening logs, we would complain to stderr,
23310 which wouldn't work, and then mysteriously exit.
23311 - Fix a rare bug where sometimes a verified OR would connect to us
23312 before he'd uploaded his descriptor, which would cause us to
23313 assign conn->nickname as though he's unverified. Now we look through
23314 the fingerprint list to see if he's there.
23315 - Fix a rare assert trigger, where routerinfos for entries in
23316 our cpath would expire while we're building the path.
23319 - Clients can ask dirservers for /dir.z to get a compressed version
23320 of the directory. Only works for servers running 0.0.9, of course.
23321 - Make clients cache directories and use them to seed their router
23322 lists at startup. This means clients have a datadir again.
23323 - Configuration infrastructure support for warning on obsolete
23325 - Respond to content-encoding headers by trying to uncompress as
23327 - Reply with a deflated directory when a client asks for "dir.z".
23328 We could use allow-encodings instead, but allow-encodings isn't
23329 specified in HTTP 1.0.
23330 - Raise the max dns workers from 50 to 100.
23331 - Discourage people from setting their dirfetchpostperiod more often
23332 than once per minute.
23333 - Protect dirservers from overzealous descriptor uploading -- wait
23334 10 seconds after directory gets dirty, before regenerating.
23337 Changes in version 0.0.8 - 2004-08-25
23338 o Port it to SunOS 5.9 / Athena
23341 Changes in version 0.0.8rc2 - 2004-08-20
23342 o Make it compile on cygwin again.
23343 o When picking unverified routers, skip those with low uptime and/or
23344 low bandwidth, depending on what properties you care about.
23347 Changes in version 0.0.8rc1 - 2004-08-18
23348 o Changes from 0.0.7.3:
23350 - Fix assert triggers: if the other side returns an address 0.0.0.0,
23351 don't put it into the client dns cache.
23352 - If a begin failed due to exit policy, but we believe the IP address
23353 should have been allowed, switch that router to exitpolicy reject *:*
23354 until we get our next directory.
23356 - Clients choose nodes proportional to advertised bandwidth.
23357 - Avoid using nodes with low uptime as introduction points.
23358 - Handle servers with dynamic IP addresses: don't replace
23359 options->Address with the resolved one at startup, and
23360 detect our address right before we make a routerinfo each time.
23361 - 'FascistFirewall' option to pick dirservers and ORs on specific
23362 ports; plus 'FirewallPorts' config option to tell FascistFirewall
23363 which ports are open. (Defaults to 80,443)
23364 - Be more aggressive about trying to make circuits when the network
23365 has changed (e.g. when you unsuspend your laptop).
23366 - Check for time skew on http headers; report date in response to
23368 - If the entrynode config line has only one node, don't pick it as
23370 - Add strict{entry|exit}nodes config options. If set to 1, then
23371 we refuse to build circuits that don't include the specified entry
23373 - OutboundBindAddress config option, to bind to a specific
23374 IP address for outgoing connect()s.
23375 - End truncated log entries (e.g. directories) with "[truncated]".
23377 o Patches to 0.0.8preX:
23379 - Patches to compile and run on win32 again (maybe)?
23380 - Fix crash when looking for ~/.torrc with no $HOME set.
23381 - Fix a race bug in the unit tests.
23382 - Handle verified/unverified name collisions better when new
23383 routerinfo's arrive in a directory.
23384 - Sometimes routers were getting entered into the stats before
23385 we'd assigned their identity_digest. Oops.
23386 - Only pick and establish intro points after we've gotten a
23389 - AllowUnverifiedNodes config option to let circuits choose no-name
23390 routers in entry,middle,exit,introduction,rendezvous positions.
23391 Allow middle and rendezvous positions by default.
23392 - Add a man page for tor-resolve.
23395 Changes in version 0.0.7.3 - 2004-08-12
23396 o Stop dnsworkers from triggering an assert failure when you
23397 ask them to resolve the host "".
23400 Changes in version 0.0.8pre3 - 2004-08-09
23401 o Changes from 0.0.7.2:
23402 - Allow multiple ORs with same nickname in routerlist -- now when
23403 people give us one identity key for a nickname, then later
23404 another, we don't constantly complain until the first expires.
23405 - Remember used bandwidth (both in and out), and publish 15-minute
23406 snapshots for the past day into our descriptor.
23407 - You can now fetch $DIRURL/running-routers to get just the
23408 running-routers line, not the whole descriptor list. (But
23409 clients don't use this yet.)
23410 - When people mistakenly use Tor as an http proxy, point them
23411 at the tor-doc.html rather than the INSTALL.
23412 - Remove our mostly unused -- and broken -- hex_encode()
23413 function. Use base16_encode() instead. (Thanks to Timo Lindfors
23414 for pointing out this bug.)
23415 - Rotate onion keys every 12 hours, not every 2 hours, so we have
23416 fewer problems with people using the wrong key.
23417 - Change the default exit policy to reject the default edonkey,
23418 kazaa, gnutella ports.
23419 - Add replace_file() to util.[ch] to handle win32's rename().
23421 o Changes from 0.0.8preX:
23422 - Fix two bugs in saving onion keys to disk when rotating, so
23423 hopefully we'll get fewer people using old onion keys.
23424 - Fix an assert error that was making SocksPolicy not work.
23425 - Be willing to expire routers that have an open dirport -- it's
23426 just the authoritative dirservers we want to not forget.
23427 - Reject tor-resolve requests for .onion addresses early, so we
23428 don't build a whole rendezvous circuit and then fail.
23429 - When you're warning a server that he's unverified, don't cry
23430 wolf unpredictably.
23431 - Fix a race condition: don't try to extend onto a connection
23432 that's still handshaking.
23433 - For servers in clique mode, require the conn to be open before
23434 you'll choose it for your path.
23435 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
23436 end relay cell, etc.
23437 - Measure bandwidth capacity over the last 24 hours, not just 12
23438 - Bugfix: authoritative dirservers were making and signing a new
23439 directory for each client, rather than reusing the cached one.
23442 Changes in version 0.0.8pre2 - 2004-08-04
23443 o Changes from 0.0.7.2:
23445 - Check directory signature _before_ you decide whether you're
23446 you're running an obsolete version and should exit.
23447 - Check directory signature _before_ you parse the running-routers
23448 list to decide who's running or verified.
23449 - Bugfixes and features:
23450 - Check return value of fclose while writing to disk, so we don't
23451 end up with broken files when servers run out of disk space.
23452 - Log a warning if the user uses an unsafe socks variant, so people
23453 are more likely to learn about privoxy or socat.
23454 - Dirservers now include RFC1123-style dates in the HTTP headers,
23455 which one day we will use to better detect clock skew.
23457 o Changes from 0.0.8pre1:
23458 - Make it compile without warnings again on win32.
23459 - Log a warning if you're running an unverified server, to let you
23460 know you might want to get it verified.
23461 - Only pick a default nickname if you plan to be a server.
23464 Changes in version 0.0.8pre1 - 2004-07-23
23466 - Made our unit tests compile again on OpenBSD 3.5, and tor
23467 itself compile again on OpenBSD on a sparc64.
23468 - We were neglecting milliseconds when logging on win32, so
23469 everything appeared to happen at the beginning of each second.
23471 o Protocol changes:
23472 - 'Extend' relay cell payloads now include the digest of the
23473 intended next hop's identity key. Now we can verify that we're
23474 extending to the right router, and also extend to routers we
23475 hadn't heard of before.
23478 - Tor nodes can now act as relays (with an advertised ORPort)
23479 without being manually verified by the dirserver operators.
23480 - Uploaded descriptors of unverified routers are now accepted
23481 by the dirservers, and included in the directory.
23482 - Verified routers are listed by nickname in the running-routers
23483 list; unverified routers are listed as "$<fingerprint>".
23484 - We now use hash-of-identity-key in most places rather than
23485 nickname or addr:port, for improved security/flexibility.
23486 - To avoid Sybil attacks, paths still use only verified servers.
23487 But now we have a chance to play around with hybrid approaches.
23488 - Nodes track bandwidth usage to estimate capacity (not used yet).
23489 - ClientOnly option for nodes that never want to become servers.
23490 - Directory caching.
23491 - "AuthoritativeDir 1" option for the official dirservers.
23492 - Now other nodes (clients and servers) will cache the latest
23493 directory they've pulled down.
23494 - They can enable their DirPort to serve it to others.
23495 - Clients will pull down a directory from any node with an open
23496 DirPort, and check the signature/timestamp correctly.
23497 - Authoritative dirservers now fetch directories from other
23498 authdirservers, to stay better synced.
23499 - Running-routers list tells who's down also, along with noting
23500 if they're verified (listed by nickname) or unverified (listed
23502 - Allow dirservers to serve running-router list separately.
23503 This isn't used yet.
23504 - ORs connect-on-demand to other ORs
23505 - If you get an extend cell to an OR you're not connected to,
23506 connect, handshake, and forward the create cell.
23507 - The authoritative dirservers stay connected to everybody,
23508 and everybody stays connected to 0.0.7 servers, but otherwise
23509 clients/servers expire unused connections after 5 minutes.
23510 - When servers get a sigint, they delay 30 seconds (refusing new
23511 connections) then exit. A second sigint causes immediate exit.
23512 - File and name management:
23513 - Look for .torrc if no CONFDIR "torrc" is found.
23514 - If no datadir is defined, then choose, make, and secure ~/.tor
23516 - If torrc not found, exitpolicy reject *:*.
23517 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
23518 - If no nickname is defined, derive default from hostname.
23519 - Rename secret key files, e.g. identity.key -> secret_id_key,
23520 to discourage people from mailing their identity key to tor-ops.
23521 - Refuse to build a circuit before the directory has arrived --
23522 it won't work anyway, since you won't know the right onion keys
23524 - Try other dirservers immediately if the one you try is down. This
23525 should tolerate down dirservers better now.
23526 - Parse tor version numbers so we can do an is-newer-than check
23527 rather than an is-in-the-list check.
23528 - New socks command 'resolve', to let us shim gethostbyname()
23530 - A 'tor_resolve' script to access the socks resolve functionality.
23531 - A new socks-extensions.txt doc file to describe our
23532 interpretation and extensions to the socks protocols.
23533 - Add a ContactInfo option, which gets published in descriptor.
23534 - Publish OR uptime in descriptor (and thus in directory) too.
23535 - Write tor version at the top of each log file
23536 - New docs in the tarball:
23538 - Document that you should proxy your SSL traffic too.
23541 Changes in version 0.0.7.2 - 2004-07-07
23542 o A better fix for the 0.0.0.0 problem, that will hopefully
23543 eliminate the remaining related assertion failures.
23546 Changes in version 0.0.7.1 - 2004-07-04
23547 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
23548 since internally we use 0.0.0.0 to signify "not yet resolved".
23551 Changes in version 0.0.7 - 2004-06-07
23552 o Updated the man page to reflect the new features.
23555 Changes in version 0.0.7rc2 - 2004-06-06
23556 o Changes from 0.0.7rc1:
23557 - Make it build on Win32 again.
23558 o Changes from 0.0.6.2:
23559 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
23563 Changes in version 0.0.7rc1 - 2004-06-02
23565 - On sighup, we were adding another log without removing the first
23566 one. So log messages would get duplicated n times for n sighups.
23567 - Several cases of using a connection after we'd freed it. The
23568 problem was that connections that are pending resolve are in both
23569 the pending_resolve tree, and also the circuit's resolving_streams
23570 list. When you want to remove one, you must remove it from both.
23571 - Fix a double-mark-for-close where an end cell arrived for a
23572 resolving stream, and then the resolve failed.
23573 - Check directory signatures based on name of signer, not on whom
23574 we got the directory from. This will let us cache directories more
23577 - Crank up some of our constants to handle more users.
23580 Changes in version 0.0.7pre1 - 2004-06-02
23581 o Fixes for crashes and other obnoxious bugs:
23582 - Fix an epipe bug: sometimes when directory connections failed
23583 to connect, we would give them a chance to flush before closing
23585 - When we detached from a circuit because of resolvefailed, we
23586 would immediately try the same circuit twice more, and then
23587 give up on the resolve thinking we'd tried three different
23589 - Limit the number of intro circuits we'll attempt to build for a
23590 hidden service per 15-minute period.
23591 - Check recommended-software string *early*, before actually parsing
23592 the directory. Thus we can detect an obsolete version and exit,
23593 even if the new directory format doesn't parse.
23594 o Fixes for security bugs:
23595 - Remember which nodes are dirservers when you startup, and if a
23596 random OR enables his dirport, don't automatically assume he's
23597 a trusted dirserver.
23599 - Directory connections were asking the wrong poll socket to
23600 start writing, and not asking themselves to start writing.
23601 - When we detached from a circuit because we sent a begin but
23602 didn't get a connected, we would use it again the first time;
23603 but after that we would correctly switch to a different one.
23604 - Stop warning when the first onion decrypt attempt fails; they
23605 will sometimes legitimately fail now that we rotate keys.
23606 - Override unaligned-access-ok check when $host_cpu is ia64 or
23607 arm. Apparently they allow it but the kernel whines.
23608 - Dirservers try to reconnect periodically too, in case connections
23610 - Fix some memory leaks in directory servers.
23611 - Allow backslash in Win32 filenames.
23612 - Made Tor build complain-free on FreeBSD, hopefully without
23613 breaking other BSD builds. We'll see.
23615 - Doxygen markup on all functions and global variables.
23616 - Make directory functions update routerlist, not replace it. So
23617 now directory disagreements are not so critical a problem.
23618 - Remove the upper limit on number of descriptors in a dirserver's
23619 directory (not that we were anywhere close).
23620 - Allow multiple logfiles at different severity ranges.
23621 - Allow *BindAddress to specify ":port" rather than setting *Port
23622 separately. Allow multiple instances of each BindAddress config
23623 option, so you can bind to multiple interfaces if you want.
23624 - Allow multiple exit policy lines, which are processed in order.
23625 Now we don't need that huge line with all the commas in it.
23626 - Enable accept/reject policies on SOCKS connections, so you can bind
23627 to 0.0.0.0 but still control who can use your OP.
23630 Changes in version 0.0.6.2 - 2004-05-16
23631 o Our integrity-checking digest was checking only the most recent cell,
23632 not the previous cells like we'd thought.
23633 Thanks to Stefan Mark for finding the flaw!
23636 Changes in version 0.0.6.1 - 2004-05-06
23637 o Fix two bugs in our AES counter-mode implementation (this affected
23638 onion-level stream encryption, but not TLS-level). It turns
23639 out we were doing something much more akin to a 16-character
23640 polyalphabetic cipher. Oops.
23641 Thanks to Stefan Mark for finding the flaw!
23642 o Retire moria3 as a directory server, and add tor26 as a directory
23646 Changes in version 0.0.6 - 2004-05-02
23647 [version bump only]
23650 Changes in version 0.0.6rc4 - 2004-05-01
23651 o Update the built-in dirservers list to use the new directory format
23652 o Fix a rare seg fault: if a node offering a hidden service attempts
23653 to build a circuit to Alice's rendezvous point and fails before it
23654 reaches the last hop, it retries with a different circuit, but
23656 o Handle windows socket errors correctly.
23659 Changes in version 0.0.6rc3 - 2004-04-28
23660 o Don't expire non-general excess circuits (if we had enough
23661 circuits open, we were expiring rendezvous circuits -- even
23662 when they had a stream attached. oops.)
23663 o Fetch randomness from /dev/urandom better (not via fopen/fread)
23664 o Better debugging for tls errors
23665 o Some versions of openssl have an SSL_pending function that erroneously
23666 returns bytes when there is a non-application record pending.
23667 o Set Content-Type on the directory and hidserv descriptor.
23668 o Remove IVs from cipher code, since AES-ctr has none.
23669 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
23670 o We were using an array of length zero in a few places.
23671 o win32's gethostbyname can't resolve an IP to an IP.
23672 o win32's close can't close a socket.
23675 Changes in version 0.0.6rc2 - 2004-04-26
23676 o Fix a bug where we were closing tls connections intermittently.
23677 It turns out openssl keeps its errors around -- so if an error
23678 happens, and you don't ask about it, and then another openssl
23679 operation happens and succeeds, and you ask if there was an error,
23680 it tells you about the first error. Fun fun.
23681 o Fix a bug that's been lurking since 27 may 03 (!)
23682 When passing back a destroy cell, we would use the wrong circ id.
23683 'Mostly harmless', but still worth fixing.
23684 o Since we don't support truncateds much, don't bother sending them;
23685 just close the circ.
23686 o check for <machine/limits.h> so we build on NetBSD again (I hope).
23687 o don't crash if a conn that sent a begin has suddenly lost its circuit
23688 (this was quite rare).
23691 Changes in version 0.0.6rc1 - 2004-04-25
23692 o We now rotate link (tls context) keys and onion keys.
23693 o CREATE cells now include oaep padding, so you can tell
23694 if you decrypted them correctly.
23695 o Add bandwidthburst to server descriptor.
23696 o Directories now say which dirserver signed them.
23697 o Use a tor_assert macro that logs failed assertions too.
23700 Changes in version 0.0.6pre5 - 2004-04-18
23701 o changes from 0.0.6pre4:
23702 - make tor build on broken freebsd 5.2 installs
23703 - fix a failed assert when you try an intro point, get a nack, and try
23704 a second one and it works.
23705 - when alice uses a port that the hidden service doesn't accept,
23706 it now sends back an end cell (denied by exit policy). otherwise
23707 alice would just have to wait to time out.
23708 - fix another rare bug: when we had tried all the intro
23709 points for a hidden service, we fetched the descriptor
23710 again, but we left our introcirc thinking it had already
23711 sent an intro, so it kept waiting for a response...
23712 - bugfix: when you sleep your hidden-service laptop, as soon
23713 as it wakes up it tries to upload a service descriptor, but
23714 socketpair fails for some reason (localhost not up yet?).
23715 now we simply give up on that upload, and we'll try again later.
23716 i'd still like to find the bug though.
23717 - if an intro circ waiting for an ack dies before getting one, then
23719 - we were reusing stale service descriptors and refetching usable
23723 Changes in version 0.0.6pre4 - 2004-04-14
23724 o changes from 0.0.6pre3:
23725 - when bob fails to connect to the rendezvous point, and his
23726 circ didn't fail because of the rendezvous point itself, then
23727 he retries a couple of times
23728 - we expire introduction and rendezvous circs more thoroughly
23729 (sometimes they were hanging around forever)
23730 - we expire unattached rendezvous streams that have been around
23731 too long (they were sticking around forever).
23732 - fix a measly fencepost error that was crashing everybody with
23736 Changes in version 0.0.6pre3 - 2004-04-14
23737 o changes from 0.0.6pre2:
23738 - make hup work again
23739 - fix some memory leaks for dirservers
23740 - allow more skew in rendezvous descriptor timestamps, to help
23741 handle people like blanu who don't know what time it is
23742 - normal circs are 3 hops, but some rend/intro circs are 4, if
23743 the initiator doesn't get to choose the last hop
23744 - send acks for introductions, so alice can know whether to try
23746 - bob publishes intro points more correctly
23747 o changes from 0.0.5:
23748 - fix an assert trigger that's been plaguing us since the days
23749 of 0.0.2prexx (thanks weasel!)
23750 - retry stream correctly when we fail to connect because of
23751 exit-policy-reject (should try another) or can't-resolve-address
23752 (also should try another, because dns on random internet servers
23754 - when we hup a dirserver and we've *removed* a server from the
23755 approved-routers list, now we remove that server from the
23756 in-memory directories too
23759 Changes in version 0.0.6pre2 - 2004-04-08
23760 o We fixed our base32 implementation. Now it works on all architectures.
23763 Changes in version 0.0.6pre1 - 2004-04-08
23765 - Hidden services and rendezvous points are implemented. Go to
23766 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
23767 hidden services. (This only works via a socks4a proxy such as
23768 Privoxy, and currently it's quite slow.)
23771 Changes in version 0.0.5 - 2004-03-30
23772 [version bump only]
23775 Changes in version 0.0.5rc3 - 2004-03-29
23776 o Install torrc as torrc.sample -- we no longer clobber your
23778 o Re-enable recommendedversion checking (we broke it in rc2, oops)
23779 o Add in a 'notice' log level for things the operator should hear
23780 but that aren't warnings
23783 Changes in version 0.0.5rc2 - 2004-03-29
23784 o Hold socks connection open until reply is flushed (if possible)
23785 o Make exit nodes resolve IPs to IPs immediately, rather than asking
23786 the dns farm to do it.
23787 o Fix c99 aliasing warnings in rephist.c
23788 o Don't include server descriptors that are older than 24 hours in the
23790 o Give socks 'reject' replies their whole 15s to attempt to flush,
23791 rather than seeing the 60s timeout and assuming the flush had failed.
23792 o Clean automake droppings from the cvs repository
23795 Changes in version 0.0.5rc1 - 2004-03-28
23796 o Fix mangled-state bug in directory fetching (was causing sigpipes).
23797 o Only build circuits after we've fetched the directory: clients were
23798 using only the directory servers before they'd fetched a directory.
23799 This also means longer startup time; so it goes.
23800 o Fix an assert trigger where an OP would fail to handshake, and we'd
23801 expect it to have a nickname.
23802 o Work around a tsocks bug: do a socks reject when AP connection dies
23803 early, else tsocks goes into an infinite loop.
23806 Changes in version 0.0.4 - 2004-03-26
23807 o When connecting to a dirserver or OR and the network is down,
23811 Changes in version 0.0.3 - 2004-03-26
23812 o Warn and fail if server chose a nickname with illegal characters
23813 o Port to Solaris and Sparc:
23814 - include missing header fcntl.h
23815 - have autoconf find -lsocket -lnsl automatically
23816 - deal with hardware word alignment
23817 - make uname() work (solaris has a different return convention)
23818 - switch from using signal() to sigaction()
23819 o Preliminary work on reputation system:
23820 - Keep statistics on success/fail of connect attempts; they're published
23821 by kill -USR1 currently.
23822 - Add a RunTesting option to try to learn link state by creating test
23823 circuits, even when SocksPort is off.
23824 - Remove unused open circuits when there are too many.
23827 Changes in version 0.0.2 - 2004-03-19
23828 - Include strlcpy and strlcat for safer string ops
23829 - define INADDR_NONE so we compile (but still not run) on solaris
23832 Changes in version 0.0.2pre27 - 2004-03-14
23834 - Allow internal tor networks (we were rejecting internal IPs,
23835 now we allow them if they're set explicitly).
23836 - And fix a few endian issues.
23839 Changes in version 0.0.2pre26 - 2004-03-14
23841 - If a stream times out after 15s without a connected cell, don't
23842 try that circuit again: try a new one.
23843 - Retry streams at most 4 times. Then give up.
23844 - When a dirserver gets a descriptor from an unknown router, it
23845 logs its fingerprint (so the dirserver operator can choose to
23846 accept it even without mail from the server operator).
23847 - Inform unapproved servers when we reject their descriptors.
23848 - Make tor build on Windows again. It works as a client, who knows
23850 - Clearer instructions in the torrc for how to set up a server.
23851 - Be more efficient about reading fd's when our global token bucket
23852 (used for rate limiting) becomes empty.
23854 - Stop asserting that computers always go forward in time. It's
23856 - When we sent a cell (e.g. destroy) and then marked an OR connection
23857 expired, we might close it before finishing a flush if the other
23858 side isn't reading right then.
23859 - Don't allow dirservers to start if they haven't defined
23860 RecommendedVersions
23861 - We were caching transient dns failures. Oops.
23862 - Prevent servers from publishing an internal IP as their address.
23863 - Address a strcat vulnerability in circuit.c
23866 Changes in version 0.0.2pre25 - 2004-03-04
23868 - Put the OR's IP in its router descriptor, not its fqdn. That way
23869 we'll stop being stalled by gethostbyname for nodes with flaky dns,
23872 - If the user typed in an address that didn't resolve, the server
23876 Changes in version 0.0.2pre24 - 2004-03-03
23878 - Fix an assertion failure in dns.c, where we were trying to dequeue
23879 a pending dns resolve even if it wasn't pending
23880 - Fix a spurious socks5 warning about still trying to write after the
23881 connection is finished.
23882 - Hold certain marked_for_close connections open until they're finished
23883 flushing, rather than losing bytes by closing them too early.
23884 - Correctly report the reason for ending a stream
23885 - Remove some duplicate calls to connection_mark_for_close
23886 - Put switch_id and start_daemon earlier in the boot sequence, so it
23887 will actually try to chdir() to options.DataDirectory
23888 - Make 'make test' exit(1) if a test fails; fix some unit tests
23889 - Make tor fail when you use a config option it doesn't know about,
23890 rather than warn and continue.
23891 - Make --version work
23892 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
23895 Changes in version 0.0.2pre23 - 2004-02-29
23897 - Print a statement when the first circ is finished, so the user
23898 knows it's working.
23899 - If a relay cell is unrecognized at the end of the circuit,
23900 send back a destroy. (So attacks to mutate cells are more
23902 - New config option 'excludenodes' to avoid certain nodes for circuits.
23903 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
23904 so you can collect coredumps there.
23906 - Fix a bug in tls flushing where sometimes data got wedged and
23907 didn't flush until more data got sent. Hopefully this bug was
23908 a big factor in the random delays we were seeing.
23909 - Make 'connected' cells include the resolved IP, so the client
23910 dns cache actually gets populated.
23911 - Disallow changing from ORPort=0 to ORPort>0 on hup.
23912 - When we time-out on a stream and detach from the circuit, send an
23913 end cell down it first.
23914 - Only warn about an unknown router (in exitnodes, entrynodes,
23915 excludenodes) after we've fetched a directory.
23918 Changes in version 0.0.2pre22 - 2004-02-26
23920 - Servers publish less revealing uname information in descriptors.
23921 - More memory tracking and assertions, to crash more usefully when
23923 - If the default torrc isn't there, just use some default defaults.
23924 Plus provide an internal dirservers file if they don't have one.
23925 - When the user tries to use Tor as an http proxy, give them an http
23926 501 failure explaining that we're a socks proxy.
23927 - Dump a new router.desc on hup, to help confused people who change
23928 their exit policies and then wonder why router.desc doesn't reflect
23930 - Clean up the generic tor.sh init script that we ship with.
23932 - If the exit stream is pending on the resolve, and a destroy arrives,
23933 then the stream wasn't getting removed from the pending list. I
23934 think this was the one causing recent server crashes.
23935 - Use a more robust poll on OSX 10.3, since their poll is flaky.
23936 - When it couldn't resolve any dirservers, it was useless from then on.
23937 Now it reloads the RouterFile (or default dirservers) if it has no
23939 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
23940 many users don't even *have* a /usr/local/sbin/.
23943 Changes in version 0.0.2pre21 - 2004-02-18
23945 - There's a ChangeLog file that actually reflects the changelog.
23946 - There's a 'torify' wrapper script, with an accompanying
23947 tor-tsocks.conf, that simplifies the process of using tsocks for
23948 tor. It even has a man page.
23949 - The tor binary gets installed to sbin rather than bin now.
23950 - Retry streams where the connected cell hasn't arrived in 15 seconds
23951 - Clean up exit policy handling -- get the default out of the torrc,
23952 so we can update it without forcing each server operator to fix
23954 - Allow imaps and pop3s in default exit policy
23956 - Prevent picking middleman nodes as the last node in the circuit
23959 Changes in version 0.0.2pre20 - 2004-01-30
23961 - We now have a deb package, and it's in debian unstable. Go to
23962 it, apt-getters. :)
23963 - I've split the TotalBandwidth option into BandwidthRate (how many
23964 bytes per second you want to allow, long-term) and
23965 BandwidthBurst (how many bytes you will allow at once before the cap
23966 kicks in). This better token bucket approach lets you, say, set
23967 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
23968 performance while not exceeding your monthly bandwidth quota.
23969 - Push out a tls record's worth of data once you've got it, rather
23970 than waiting until you've read everything waiting to be read. This
23971 may improve performance by pipelining better. We'll see.
23972 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
23973 from failed circuits (if they haven't been connected yet) and attach
23975 - Expire old streams that haven't managed to connect. Some day we'll
23976 have them reattach to new circuits instead.
23979 - Fix several memory leaks that were causing servers to become bloated
23981 - Fix a few very rare assert triggers. A few more remain.
23982 - Setuid to User _before_ complaining about running as root.
23985 Changes in version 0.0.2pre19 - 2004-01-07
23987 - Fix deadlock condition in dns farm. We were telling a child to die by
23988 closing the parent's file descriptor to him. But newer children were
23989 inheriting the open file descriptor from the parent, and since they
23990 weren't closing it, the socket never closed, so the child never read
23991 eof, so he never knew to exit. Similarly, dns workers were holding
23992 open other sockets, leading to all sorts of chaos.
23993 - New cleaner daemon() code for forking and backgrounding.
23994 - If you log to a file, it now prints an entry at the top of the
23995 logfile so you know it's working.
23996 - The onionskin challenge length was 30 bytes longer than necessary.
23997 - Started to patch up the spec so it's not quite so out of date.
24000 Changes in version 0.0.2pre18 - 2004-01-02
24002 - Fix endian issues with the 'integrity' field in the relay header.
24003 - Fix a potential bug where connections in state
24004 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
24007 Changes in version 0.0.2pre17 - 2003-12-30
24009 - Made --debuglogfile (or any second log file, actually) work.
24010 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
24011 adversary could force us into an infinite loop.
24014 - Each onionskin handshake now includes a hash of the computed key,
24015 to prove the server's identity and help perfect forward secrecy.
24016 - Changed cell size from 256 to 512 bytes (working toward compatibility
24018 - Changed cell length to 2 bytes, and moved it to the relay header.
24019 - Implemented end-to-end integrity checking for the payloads of
24021 - Separated streamid from 'recognized' (otherwise circuits will get
24022 messed up when we try to have streams exit from the middle). We
24023 use the integrity-checking to confirm that a cell is addressed to
24025 - Randomize the initial circid and streamid values, so an adversary who
24026 breaks into a node can't learn how many circuits or streams have
24030 Changes in version 0.0.2pre16 - 2003-12-14
24032 - Fixed a bug that made HUP trigger an assert
24033 - Fixed a bug where a circuit that immediately failed wasn't being
24034 counted as a failed circuit in counting retries.
24037 - Now we close the circuit when we get a truncated cell: otherwise we're
24038 open to an anonymity attack where a bad node in the path truncates
24039 the circuit and then we open streams at him.
24040 - Add port ranges to exit policies
24041 - Add a conservative default exit policy
24042 - Warn if you're running tor as root
24043 - on HUP, retry OR connections and close/rebind listeners
24044 - options.EntryNodes: try these nodes first when picking the first node
24045 - options.ExitNodes: if your best choices happen to include any of
24046 your preferred exit nodes, you choose among just those preferred
24048 - options.ExcludedNodes: nodes that are never picked in path building
24051 Changes in version 0.0.2pre15 - 2003-12-03
24052 o Robustness and bugfixes:
24053 - Sometimes clients would cache incorrect DNS resolves, which would
24054 really screw things up.
24055 - An OP that goes offline would slowly leak all its sockets and stop
24057 - A wide variety of bugfixes in exit node selection, exit policy
24058 handling, and processing pending streams when a new circuit is
24060 - Pick nodes for a path only from those the directory says are up
24061 - Choose randomly from all running dirservers, not always the first one
24062 - Increase allowed http header size for directory fetch.
24063 - Stop writing to stderr (if we're daemonized it will be closed).
24064 - Enable -g always, so cores will be more useful to me.
24065 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
24068 - Wrote a man page. It lists commonly used options.
24071 - Change default loglevel to warn.
24072 - Make PidFile default to null rather than littering in your CWD.
24073 - OnionRouter config option is now obsolete. Instead it just checks
24075 - Moved to a single unified torrc file for both clients and servers.
24078 Changes in version 0.0.2pre14 - 2003-11-29
24079 o Robustness and bugfixes:
24080 - Force the admin to make the DataDirectory himself
24081 - to get ownership/permissions right
24082 - so clients no longer make a DataDirectory and then never use it
24083 - fix bug where a client who was offline for 45 minutes would never
24084 pull down a directory again
24085 - fix (or at least hide really well) the dns assert bug that was
24086 causing server crashes
24087 - warnings and improved robustness wrt clockskew for certs
24088 - use the native daemon(3) to daemonize, when available
24089 - exit if bind() fails
24090 - exit if neither socksport nor orport is defined
24091 - include our own tor_timegm (Win32 doesn't have its own)
24092 - bugfix for win32 with lots of connections
24093 - fix minor bias in PRNG
24094 - make dirserver more robust to corrupt cached directory
24097 - Wrote the design document (woo)
24099 o Circuit building and exit policies:
24100 - Circuits no longer try to use nodes that the directory has told them
24102 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
24103 bitcounts (18.0.0.0/8).
24104 - Make AP connections standby for a circuit if no suitable circuit
24105 exists, rather than failing
24106 - Circuits choose exit node based on addr/port, exit policies, and
24107 which AP connections are standing by
24108 - Bump min pathlen from 2 to 3
24109 - Relay end cells have a payload to describe why the stream ended.
24110 - If the stream failed because of exit policy, try again with a new
24112 - Clients have a dns cache to remember resolved addresses.
24113 - Notice more quickly when we have no working circuits
24116 - APPort is now called SocksPort
24117 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
24119 - RecommendedVersions is now a config variable rather than
24120 hardcoded (for dirservers)
24121 - Reloads config on HUP
24122 - Usage info on -h or --help
24123 - If you set User and Group config vars, it'll setu/gid to them.
24126 Changes in version 0.0.2pre13 - 2003-10-19
24127 o General stability:
24128 - SSL_write no longer fails when it returns WANTWRITE and the number
24129 of bytes in the buf has changed by the next SSL_write call.
24130 - Fix segfault fetching directory when network is down
24131 - Fix a variety of minor memory leaks
24132 - Dirservers reload the fingerprints file on HUP, so I don't have
24133 to take down the network when I approve a new router
24134 - Default server config file has explicit Address line to specify fqdn
24137 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
24138 - Make listener connections not ever alloc bufs
24140 o Autoconf improvements:
24141 - don't clobber an external CFLAGS in ./configure
24142 - Make install now works
24143 - create var/lib/tor on make install
24144 - autocreate a tor.sh initscript to help distribs
24145 - autocreate the torrc and sample-server-torrc with correct paths
24147 o Log files and Daemonizing now work:
24148 - If --DebugLogFile is specified, log to it at -l debug
24149 - If --LogFile is specified, use it instead of commandline
24150 - If --RunAsDaemon is set, tor forks and backgrounds on startup