1 This document summarizes new features and bugfixes in each stable release
2 of Tor. If you want to see more detailed descriptions of the changes in
3 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.8.13 - 2017-03-03
7 Tor 0.2.8.13 backports a security fix from later Tor
8 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
9 this release, if for some reason they cannot upgrade to a later
10 release series, and if they build Tor with the --enable-expensive-hardening
13 Note that support for Tor 0.2.8.x is ending next year: we will not issue
14 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
15 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
17 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
18 - Fix an integer underflow bug when comparing malformed Tor
19 versions. This bug could crash Tor when built with
20 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
21 0.2.9.8, which were built with -ftrapv by default. In other cases
22 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
23 on 0.0.8pre1. Found by OSS-Fuzz.
25 o Minor features (geoip):
26 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
30 Changes in version 0.2.7.7 - 2017-03-03
31 Tor 0.2.7.7 backports a number of security fixes from later Tor
32 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
33 this release, if for some reason they cannot upgrade to a later
36 Note that support for Tor 0.2.7.x is ending this year: we will not issue
37 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
38 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
40 o Directory authority changes (backport from 0.2.8.5-rc):
41 - Urras is no longer a directory authority. Closes ticket 19271.
43 o Directory authority changes (backport from 0.2.9.2-alpha):
44 - The "Tonga" bridge authority has been retired; the new bridge
45 authority is "Bifroest". Closes tickets 19728 and 19690.
47 o Directory authority key updates (backport from 0.2.8.1-alpha):
48 - Update the V3 identity key for the dannenberg directory authority:
49 it was changed on 18 November 2015. Closes task 17906. Patch
52 o Major bugfixes (parsing, security, backport from 0.2.9.8):
53 - Fix a bug in parsing that could cause clients to read a single
54 byte past the end of an allocated region. This bug could be used
55 to cause hardened clients (built with --enable-expensive-hardening)
56 to crash if they tried to visit a hostile hidden service. Non-
57 hardened clients are only affected depending on the details of
58 their platform's memory allocator. Fixes bug 21018; bugfix on
59 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
60 2016-12-002 and as CVE-2016-1254.
62 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
63 - Stop a crash that could occur when a client running with DNSPort
64 received a query with multiple address types, and the first
65 address type was not supported. Found and fixed by Scott Dial.
66 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
67 - Prevent a class of security bugs caused by treating the contents
68 of a buffer chunk as if they were a NUL-terminated string. At
69 least one such bug seems to be present in all currently used
70 versions of Tor, and would allow an attacker to remotely crash
71 most Tor instances, especially those compiled with extra compiler
72 hardening. With this defense in place, such bugs can't crash Tor,
73 though we should still fix them as they occur. Closes ticket
74 20384 (TROVE-2016-10-001).
76 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
77 - Avoid a difficult-to-trigger heap corruption attack when extending
78 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
79 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
80 Reported by Guido Vranken.
82 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
83 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
84 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
86 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
87 - If OpenSSL fails to generate an RSA key, do not retain a dangling
88 pointer to the previous (uninitialized) key value. The impact here
89 should be limited to a difficult-to-trigger crash, if OpenSSL is
90 running an engine that makes key generation failures possible, or
91 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
92 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
95 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
96 - Fix an integer underflow bug when comparing malformed Tor
97 versions. This bug could crash Tor when built with
98 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
99 0.2.9.8, which were built with -ftrapv by default. In other cases
100 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
101 on 0.0.8pre1. Found by OSS-Fuzz.
103 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
104 - Make memwipe() do nothing when passed a NULL pointer or buffer of
105 zero size. Check size argument to memwipe() for underflow. Fixes
106 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
109 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
110 - Make Tor survive errors involving connections without a
111 corresponding event object. Previously we'd fail with an
112 assertion; now we produce a log message. Related to bug 16248.
114 o Minor features (geoip):
115 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
119 Changes in version 0.2.6.11 - 2017-03-03
120 Tor 0.2.6.11 backports a number of security fixes from later Tor
121 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
122 this release, if for some reason they cannot upgrade to a later
125 Note that support for Tor 0.2.6.x is ending this year: we will not issue
126 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
127 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
129 o Directory authority changes (backport from 0.2.8.5-rc):
130 - Urras is no longer a directory authority. Closes ticket 19271.
132 o Directory authority changes (backport from 0.2.9.2-alpha):
133 - The "Tonga" bridge authority has been retired; the new bridge
134 authority is "Bifroest". Closes tickets 19728 and 19690.
136 o Directory authority key updates (backport from 0.2.8.1-alpha):
137 - Update the V3 identity key for the dannenberg directory authority:
138 it was changed on 18 November 2015. Closes task 17906. Patch
141 o Major features (security fixes, backport from 0.2.9.4-alpha):
142 - Prevent a class of security bugs caused by treating the contents
143 of a buffer chunk as if they were a NUL-terminated string. At
144 least one such bug seems to be present in all currently used
145 versions of Tor, and would allow an attacker to remotely crash
146 most Tor instances, especially those compiled with extra compiler
147 hardening. With this defense in place, such bugs can't crash Tor,
148 though we should still fix them as they occur. Closes ticket
149 20384 (TROVE-2016-10-001).
151 o Major bugfixes (parsing, security, backport from 0.2.9.8):
152 - Fix a bug in parsing that could cause clients to read a single
153 byte past the end of an allocated region. This bug could be used
154 to cause hardened clients (built with --enable-expensive-hardening)
155 to crash if they tried to visit a hostile hidden service. Non-
156 hardened clients are only affected depending on the details of
157 their platform's memory allocator. Fixes bug 21018; bugfix on
158 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
159 2016-12-002 and as CVE-2016-1254.
161 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
162 - Stop a crash that could occur when a client running with DNSPort
163 received a query with multiple address types, and the first
164 address type was not supported. Found and fixed by Scott Dial.
165 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
167 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
168 - Fix an error that could cause us to read 4 bytes before the
169 beginning of an openssl string. This bug could be used to cause
170 Tor to crash on systems with unusual malloc implementations, or
171 systems with unusual hardening installed. Fixes bug 17404; bugfix
174 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
175 - Avoid a difficult-to-trigger heap corruption attack when extending
176 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
177 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
178 Reported by Guido Vranken.
180 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
181 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
182 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
184 o Major bugfixes (guard selection, backport from 0.2.7.6):
185 - Actually look at the Guard flag when selecting a new directory
186 guard. When we implemented the directory guard design, we
187 accidentally started treating all relays as if they have the Guard
188 flag during guard selection, leading to weaker anonymity and worse
189 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
192 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
193 - If OpenSSL fails to generate an RSA key, do not retain a dangling
194 pointer to the previous (uninitialized) key value. The impact here
195 should be limited to a difficult-to-trigger crash, if OpenSSL is
196 running an engine that makes key generation failures possible, or
197 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
198 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
201 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
202 - Fix an integer underflow bug when comparing malformed Tor
203 versions. This bug could crash Tor when built with
204 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
205 0.2.9.8, which were built with -ftrapv by default. In other cases
206 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
207 on 0.0.8pre1. Found by OSS-Fuzz.
209 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
210 - Make memwipe() do nothing when passed a NULL pointer or buffer of
211 zero size. Check size argument to memwipe() for underflow. Fixes
212 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
215 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
216 - Make Tor survive errors involving connections without a
217 corresponding event object. Previously we'd fail with an
218 assertion; now we produce a log message. Related to bug 16248.
220 o Minor features (geoip):
221 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
224 o Minor bugfixes (compilation, backport from 0.2.7.6):
225 - Fix a compilation warning with Clang 3.6: Do not check the
226 presence of an address which can never be NULL. Fixes bug 17781.
229 Changes in version 0.2.5.13 - 2017-03-03
230 Tor 0.2.5.13 backports a number of security fixes from later Tor
231 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
232 this release, if for some reason they cannot upgrade to a later
235 Note that support for Tor 0.2.5.x is ending next year: we will not issue
236 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
237 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
239 o Directory authority changes (backport from 0.2.8.5-rc):
240 - Urras is no longer a directory authority. Closes ticket 19271.
242 o Directory authority changes (backport from 0.2.9.2-alpha):
243 - The "Tonga" bridge authority has been retired; the new bridge
244 authority is "Bifroest". Closes tickets 19728 and 19690.
246 o Directory authority key updates (backport from 0.2.8.1-alpha):
247 - Update the V3 identity key for the dannenberg directory authority:
248 it was changed on 18 November 2015. Closes task 17906. Patch
251 o Major features (security fixes, backport from 0.2.9.4-alpha):
252 - Prevent a class of security bugs caused by treating the contents
253 of a buffer chunk as if they were a NUL-terminated string. At
254 least one such bug seems to be present in all currently used
255 versions of Tor, and would allow an attacker to remotely crash
256 most Tor instances, especially those compiled with extra compiler
257 hardening. With this defense in place, such bugs can't crash Tor,
258 though we should still fix them as they occur. Closes ticket
259 20384 (TROVE-2016-10-001).
261 o Major bugfixes (parsing, security, backport from 0.2.9.8):
262 - Fix a bug in parsing that could cause clients to read a single
263 byte past the end of an allocated region. This bug could be used
264 to cause hardened clients (built with --enable-expensive-hardening)
265 to crash if they tried to visit a hostile hidden service. Non-
266 hardened clients are only affected depending on the details of
267 their platform's memory allocator. Fixes bug 21018; bugfix on
268 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
269 2016-12-002 and as CVE-2016-1254.
271 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
272 - Stop a crash that could occur when a client running with DNSPort
273 received a query with multiple address types, and the first
274 address type was not supported. Found and fixed by Scott Dial.
275 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
277 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
278 - Fix an error that could cause us to read 4 bytes before the
279 beginning of an openssl string. This bug could be used to cause
280 Tor to crash on systems with unusual malloc implementations, or
281 systems with unusual hardening installed. Fixes bug 17404; bugfix
284 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
285 - Avoid a difficult-to-trigger heap corruption attack when extending
286 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
287 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
288 Reported by Guido Vranken.
290 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
291 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
292 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
294 o Major bugfixes (guard selection, backport from 0.2.7.6):
295 - Actually look at the Guard flag when selecting a new directory
296 guard. When we implemented the directory guard design, we
297 accidentally started treating all relays as if they have the Guard
298 flag during guard selection, leading to weaker anonymity and worse
299 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
302 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
303 - If OpenSSL fails to generate an RSA key, do not retain a dangling
304 pointer to the previous (uninitialized) key value. The impact here
305 should be limited to a difficult-to-trigger crash, if OpenSSL is
306 running an engine that makes key generation failures possible, or
307 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
308 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
311 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
312 - Fix an integer underflow bug when comparing malformed Tor
313 versions. This bug could crash Tor when built with
314 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
315 0.2.9.8, which were built with -ftrapv by default. In other cases
316 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
317 on 0.0.8pre1. Found by OSS-Fuzz.
319 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
320 - Make memwipe() do nothing when passed a NULL pointer or buffer of
321 zero size. Check size argument to memwipe() for underflow. Fixes
322 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
325 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
326 - Make Tor survive errors involving connections without a
327 corresponding event object. Previously we'd fail with an
328 assertion; now we produce a log message. Related to bug 16248.
330 o Minor features (geoip):
331 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
334 o Minor bugfixes (compilation, backport from 0.2.7.6):
335 - Fix a compilation warning with Clang 3.6: Do not check the
336 presence of an address which can never be NULL. Fixes bug 17781.
338 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
339 - Check for failures from crypto_early_init, and refuse to continue.
340 A previous typo meant that we could keep going with an
341 uninitialized crypto library, and would have OpenSSL initialize
342 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
343 when implementing ticket 4900. Patch by "teor".
345 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
346 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
347 a client authorized hidden service. Fixes bug 15823; bugfix
351 Changes in version 0.2.4.28 - 2017-03-03
352 Tor 0.2.4.28 backports a number of security fixes from later Tor
353 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
354 this release, if for some reason they cannot upgrade to a later
357 Note that support for Tor 0.2.4.x is ending soon: we will not issue
358 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
359 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
361 o Directory authority changes (backport from 0.2.8.5-rc):
362 - Urras is no longer a directory authority. Closes ticket 19271.
364 o Directory authority changes (backport from 0.2.9.2-alpha):
365 - The "Tonga" bridge authority has been retired; the new bridge
366 authority is "Bifroest". Closes tickets 19728 and 19690.
368 o Directory authority key updates (backport from 0.2.8.1-alpha):
369 - Update the V3 identity key for the dannenberg directory authority:
370 it was changed on 18 November 2015. Closes task 17906. Patch
373 o Major features (security fixes, backport from 0.2.9.4-alpha):
374 - Prevent a class of security bugs caused by treating the contents
375 of a buffer chunk as if they were a NUL-terminated string. At
376 least one such bug seems to be present in all currently used
377 versions of Tor, and would allow an attacker to remotely crash
378 most Tor instances, especially those compiled with extra compiler
379 hardening. With this defense in place, such bugs can't crash Tor,
380 though we should still fix them as they occur. Closes ticket
381 20384 (TROVE-2016-10-001).
383 o Major bugfixes (parsing, security, backport from 0.2.9.8):
384 - Fix a bug in parsing that could cause clients to read a single
385 byte past the end of an allocated region. This bug could be used
386 to cause hardened clients (built with --enable-expensive-hardening)
387 to crash if they tried to visit a hostile hidden service. Non-
388 hardened clients are only affected depending on the details of
389 their platform's memory allocator. Fixes bug 21018; bugfix on
390 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
391 2016-12-002 and as CVE-2016-1254.
393 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
394 - Fix an error that could cause us to read 4 bytes before the
395 beginning of an openssl string. This bug could be used to cause
396 Tor to crash on systems with unusual malloc implementations, or
397 systems with unusual hardening installed. Fixes bug 17404; bugfix
400 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
401 - Avoid a difficult-to-trigger heap corruption attack when extending
402 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
403 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
404 Reported by Guido Vranken.
406 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
407 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
408 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
410 o Major bugfixes (guard selection, backport from 0.2.7.6):
411 - Actually look at the Guard flag when selecting a new directory
412 guard. When we implemented the directory guard design, we
413 accidentally started treating all relays as if they have the Guard
414 flag during guard selection, leading to weaker anonymity and worse
415 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
418 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
419 - If OpenSSL fails to generate an RSA key, do not retain a dangling
420 pointer to the previous (uninitialized) key value. The impact here
421 should be limited to a difficult-to-trigger crash, if OpenSSL is
422 running an engine that makes key generation failures possible, or
423 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
424 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
427 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
428 - Fix an integer underflow bug when comparing malformed Tor
429 versions. This bug could crash Tor when built with
430 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
431 0.2.9.8, which were built with -ftrapv by default. In other cases
432 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
433 on 0.0.8pre1. Found by OSS-Fuzz.
435 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
436 - Make memwipe() do nothing when passed a NULL pointer or buffer of
437 zero size. Check size argument to memwipe() for underflow. Fixes
438 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
441 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
442 - Make Tor survive errors involving connections without a
443 corresponding event object. Previously we'd fail with an
444 assertion; now we produce a log message. Related to bug 16248.
446 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
447 - Make it harder for attackers to overload hidden services with
448 introductions, by blocking multiple introduction requests on the
449 same circuit. Resolves ticket 15515.
451 o Minor features (geoip):
452 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
455 o Minor bugfixes (compilation, backport from 0.2.7.6):
456 - Fix a compilation warning with Clang 3.6: Do not check the
457 presence of an address which can never be NULL. Fixes bug 17781.
459 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
460 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
461 a client authorized hidden service. Fixes bug 15823; bugfix
465 Changes in version 0.2.9.10 - 2017-03-01
466 Tor 0.2.9.10 backports a security fix from later Tor release. It also
467 includes fixes for some major issues affecting directory authorities,
468 LibreSSL compatibility, and IPv6 correctness.
470 The Tor 0.2.9.x release series is now marked as a long-term-support
471 series. We intend to backport security fixes to 0.2.9.x until at
472 least January of 2020.
474 o Major bugfixes (directory authority, 0.3.0.3-alpha):
475 - During voting, when marking a relay as a probable sybil, do not
476 clear its BadExit flag: sybils can still be bad in other ways
477 too. (We still clear the other flags.) Fixes bug 21108; bugfix
480 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
481 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
482 any IPv6 addresses. Instead, only reject a port over IPv6 if the
483 exit policy rejects that port on more than an IPv6 /16 of
484 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
485 which rejected a relay's own IPv6 address by default. Fixes bug
486 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
488 o Major bugfixes (parsing, also in 0.3.0.4-rc):
489 - Fix an integer underflow bug when comparing malformed Tor
490 versions. This bug could crash Tor when built with
491 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
492 0.2.9.8, which were built with -ftrapv by default. In other cases
493 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
494 on 0.0.8pre1. Found by OSS-Fuzz.
496 o Minor features (directory authorities, also in 0.3.0.4-rc):
497 - Directory authorities now reject descriptors that claim to be
498 malformed versions of Tor. Helps prevent exploitation of
500 - Reject version numbers with components that exceed INT32_MAX.
501 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
502 Fixes bug 21450; bugfix on 0.0.8pre1.
504 o Minor features (geoip):
505 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
508 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
509 - Autoconf now checks to determine if OpenSSL structures are opaque,
510 instead of explicitly checking for OpenSSL version numbers. Part
512 - Support building with recent LibreSSL code that uses opaque
513 structures. Closes ticket 21359.
515 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
516 - Repair a couple of (unreachable or harmless) cases of the risky
517 comparison-by-subtraction pattern that caused bug 21278.
519 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
520 - The tor-resolve command line tool now rejects hostnames over 255
521 characters in length. Previously, it would silently truncate them,
522 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
523 Patch by "junglefowl".
526 Changes in version 0.2.9.9 - 2017-01-23
527 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
528 cause relays and clients to crash, even if they were not built with
529 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
530 versions, and also affects 0.3.0.1-alpha: all relays running an affected
531 version should upgrade.
533 This release also resolves a client-side onion service reachability
534 bug, and resolves a pair of small portability issues.
536 o Major bugfixes (security):
537 - Downgrade the "-ftrapv" option from "always on" to "only on when
538 --enable-expensive-hardening is provided." This hardening option,
539 like others, can turn survivable bugs into crashes -- and having
540 it on by default made a (relatively harmless) integer overflow bug
541 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
542 bugfix on 0.2.9.1-alpha.
544 o Major bugfixes (client, onion service):
545 - Fix a client-side onion service reachability bug, where multiple
546 socks requests to an onion service (or a single slow request)
547 could cause us to mistakenly mark some of the service's
548 introduction points as failed, and we cache that failure so
549 eventually we run out and can't reach the service. Also resolves a
550 mysterious "Remote server sent bogus reason code 65021" log
551 warning. The bug was introduced in ticket 17218, where we tried to
552 remember the circuit end reason as a uint16_t, which mangled
553 negative values. Partially fixes bug 21056 and fixes bug 20307;
554 bugfix on 0.2.8.1-alpha.
556 o Minor features (geoip):
557 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
560 o Minor bugfixes (portability):
561 - Avoid crashing when Tor is built using headers that contain
562 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
563 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
565 - Fix Libevent detection on platforms without Libevent 1 headers
566 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
569 Changes in version 0.2.8.12 - 2016-12-19
570 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
571 below) where Tor clients could crash when attempting to visit a
572 hostile hidden service. Clients are recommended to upgrade as packages
573 become available for their systems.
575 It also includes an updated list of fallback directories, backported
578 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
579 backported to 0.2.8 in the future.
581 o Major bugfixes (parsing, security, backported from 0.2.9.8):
582 - Fix a bug in parsing that could cause clients to read a single
583 byte past the end of an allocated region. This bug could be used
584 to cause hardened clients (built with --enable-expensive-hardening)
585 to crash if they tried to visit a hostile hidden service. Non-
586 hardened clients are only affected depending on the details of
587 their platform's memory allocator. Fixes bug 21018; bugfix on
588 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
589 2016-12-002 and as CVE-2016-1254.
591 o Minor features (fallback directory list, backported from 0.2.9.8):
592 - Replace the 81 remaining fallbacks of the 100 originally
593 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
594 fallbacks (123 new, 54 existing, 27 removed) generated in December
595 2016. Resolves ticket 20170.
597 o Minor features (geoip, backported from 0.2.9.7-rc):
598 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
602 Changes in version 0.2.9.8 - 2016-12-19
603 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
605 The Tor 0.2.9 series makes mandatory a number of security features
606 that were formerly optional. It includes support for a new shared-
607 randomness protocol that will form the basis for next generation
608 hidden services, includes a single-hop hidden service mode for
609 optimizing .onion services that don't actually want to be hidden,
610 tries harder not to overload the directory authorities with excessive
611 downloads, and supports a better protocol versioning scheme for
612 improved compatibility with other implementations of the Tor protocol.
614 And of course, there are numerous other bugfixes and improvements.
616 This release also includes a fix for a medium-severity issue (bug
617 21018 below) where Tor clients could crash when attempting to visit a
618 hostile hidden service. Clients are recommended to upgrade as packages
619 become available for their systems.
621 Below are listed the changes since Tor 0.2.8.11. For a list of
622 changes since 0.2.9.7-rc, see the ChangeLog file.
624 o New system requirements:
625 - When building with OpenSSL, Tor now requires version 1.0.1 or
626 later. OpenSSL 1.0.0 and earlier are no longer supported by the
627 OpenSSL team, and should not be used. Closes ticket 20303.
628 - Tor now requires Libevent version 2.0.10-stable or later. Older
629 versions of Libevent have less efficient backends for several
630 platforms, and lack the DNS code that we use for our server-side
631 DNS support. This implements ticket 19554.
632 - Tor now requires zlib version 1.2 or later, for security,
633 efficiency, and (eventually) gzip support. (Back when we started,
634 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
635 released in 2003. We recommend the latest version.)
637 o Deprecated features:
638 - A number of DNS-cache-related sub-options for client ports are now
639 deprecated for security reasons, and may be removed in a future
640 version of Tor. (We believe that client-side DNS caching is a bad
641 idea for anonymity, and you should not turn it on.) The options
642 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
643 UseIPv4Cache, and UseIPv6Cache.
644 - A number of options are deprecated for security reasons, and may
645 be removed in a future version of Tor. The options are:
646 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
647 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
648 CloseHSClientCircuitsImmediatelyOnTimeout,
649 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
650 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
651 UseNTorHandshake, and WarnUnsafeSocks.
652 - The *ListenAddress options are now deprecated as unnecessary: the
653 corresponding *Port options should be used instead. These options
654 may someday be removed. The affected options are:
655 ControlListenAddress, DNSListenAddress, DirListenAddress,
656 NATDListenAddress, ORListenAddress, SocksListenAddress,
657 and TransListenAddress.
659 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
660 - Fix a bug in parsing that could cause clients to read a single
661 byte past the end of an allocated region. This bug could be used
662 to cause hardened clients (built with --enable-expensive-hardening)
663 to crash if they tried to visit a hostile hidden service. Non-
664 hardened clients are only affected depending on the details of
665 their platform's memory allocator. Fixes bug 21018; bugfix on
666 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
667 2016-12-002 and as CVE-2016-1254.
669 o Major features (build, hardening):
670 - Tor now builds with -ftrapv by default on compilers that support
671 it. This option detects signed integer overflow (which C forbids),
672 and turns it into a hard-failure. We do not apply this option to
673 code that needs to run in constant time to avoid side-channels;
674 instead, we use -fwrapv in that code. Closes ticket 17983.
675 - When --enable-expensive-hardening is selected, stop applying the
676 clang/gcc sanitizers to code that needs to run in constant time.
677 Although we are aware of no introduced side-channels, we are not
678 able to prove that there are none. Related to ticket 17983.
680 o Major features (circuit building, security):
681 - Authorities, relays, and clients now require ntor keys in all
682 descriptors, for all hops (except for rare hidden service protocol
683 cases), for all circuits, and for all other roles. Part of
685 - Authorities, relays, and clients only use ntor, except for
686 rare cases in the hidden service protocol. Part of ticket 19163.
688 o Major features (compilation):
689 - Our big list of extra GCC warnings is now enabled by default when
690 building with GCC (or with anything like Clang that claims to be
691 GCC-compatible). To make all warnings into fatal compilation
692 errors, pass --enable-fatal-warnings to configure. Closes
694 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
695 turn on C and POSIX extensions. (Previously, we attempted to do
696 this on an ad hoc basis.) Closes ticket 19139.
698 o Major features (directory authorities, hidden services):
699 - Directory authorities can now perform the shared randomness
700 protocol specified by proposal 250. Using this protocol, directory
701 authorities generate a global fresh random value every day. In the
702 future, this value will be used by hidden services to select
703 HSDirs. This release implements the directory authority feature;
704 the hidden service side will be implemented in the future as part
705 of proposal 224. Resolves ticket 16943; implements proposal 250.
707 o Major features (downloading, random exponential backoff):
708 - When we fail to download an object from a directory service, wait
709 for an (exponentially increasing) randomized amount of time before
710 retrying, rather than a fixed interval as we did before. This
711 prevents a group of Tor instances from becoming too synchronized,
712 or a single Tor instance from becoming too predictable, in its
713 download schedule. Closes ticket 15942.
715 o Major features (resource management):
716 - Tor can now notice it is about to run out of sockets, and
717 preemptively close connections of lower priority. (This feature is
718 off by default for now, since the current prioritizing method is
719 yet not mature enough. You can enable it by setting
720 "DisableOOSCheck 0", but watch out: it might close some sockets
721 you would rather have it keep.) Closes ticket 18640.
723 o Major features (single-hop "hidden" services):
724 - Add experimental HiddenServiceSingleHopMode and
725 HiddenServiceNonAnonymousMode options. When both are set to 1,
726 every hidden service on that Tor instance becomes a non-anonymous
727 Single Onion Service. Single Onions make one-hop (direct)
728 connections to their introduction and rendezvous points. One-hop
729 circuits make Single Onion servers easily locatable, but clients
730 remain location-anonymous. This is compatible with the existing
731 hidden service implementation, and works on the current Tor
732 network without any changes to older relays or clients. Implements
733 proposal 260, completes ticket 17178. Patch by teor and asn.
735 o Major features (subprotocol versions):
736 - Tor directory authorities now vote on a set of recommended
737 "subprotocol versions", and on a set of required subprotocol
738 versions. Clients and relays that lack support for a _required_
739 subprotocol version will not start; those that lack support for a
740 _recommended_ subprotocol version will warn the user to upgrade.
741 This change allows compatible implementations of the Tor protocol(s)
742 to exist without pretending to be 100% bug-compatible with
743 particular releases of Tor itself. Closes ticket 19958; implements
744 part of proposal 264.
746 o Major bugfixes (circuit building):
747 - Hidden service client-to-intro-point and service-to-rendezvous-
748 point circuits use the TAP key supplied by the protocol, to avoid
749 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
751 o Major bugfixes (download scheduling):
752 - Avoid resetting download status for consensuses hourly, since we
753 already have another, smarter retry mechanism. Fixes bug 8625;
754 bugfix on 0.2.0.9-alpha.
755 - If a consensus expires while we are waiting for certificates to
756 download, stop waiting for certificates.
757 - If we stop waiting for certificates less than a minute after we
758 started downloading them, do not consider the certificate download
759 failure a separate failure. Fixes bug 20533; bugfix
761 - When using exponential backoff in test networks, use a lower
762 exponent, so the delays do not vary as much. This helps test
763 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
765 o Major bugfixes (exit policies):
766 - Avoid disclosing exit outbound bind addresses, configured port
767 bind addresses, and local interface addresses in relay descriptors
768 by default under ExitPolicyRejectPrivate. Instead, only reject
769 these (otherwise unlisted) addresses if
770 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
771 0.2.7.2-alpha. Patch by teor.
773 o Major bugfixes (hidden services):
774 - Allow Tor clients with appropriate controllers to work with
775 FetchHidServDescriptors set to 0. Previously, this option also
776 disabled descriptor cache lookup, thus breaking hidden services
777 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
778 - Clients now require hidden services to include the TAP keys for
779 their intro points in the hidden service descriptor. This prevents
780 an inadvertent upgrade to ntor, which a malicious hidden service
781 could use to distinguish clients by consensus version. Fixes bug
782 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
784 o Major bugfixes (relay, resolver, logging):
785 - For relays that don't know their own address, avoid attempting a
786 local hostname resolve for each descriptor we download. This
787 will cut down on the number of "Success: chose address 'x.x.x.x'"
788 log lines, and also avoid confusing clock jumps if the resolver
789 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
791 o Minor features (port flags):
792 - Add new flags to the *Port options to give finer control over which
793 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
794 and the synthetic flag OnionTrafficOnly, which is equivalent to
795 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
796 18693; patch by "teor".
798 o Minor features (build, hardening):
799 - Detect and work around a libclang_rt problem that would prevent
800 clang from finding __mulodi4() on some 32-bit platforms, and thus
801 keep -ftrapv from linking on those systems. Closes ticket 19079.
802 - When building on a system without runtime support for the runtime
803 hardening options, try to log a useful warning at configuration
804 time, rather than an incomprehensible warning at link time. If
805 expensive hardening was requested, this warning becomes an error.
808 o Minor features (client, directory):
809 - Since authorities now omit all routers that lack the Running and
810 Valid flags, we assume that any relay listed in the consensus must
811 have those flags. Closes ticket 20001; implements part of
814 o Minor features (code safety):
815 - In our integer-parsing functions, ensure that the maximum value we
816 allow is no smaller than the minimum value. Closes ticket 19063;
819 o Minor features (compilation, portability):
820 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
823 o Minor features (config):
824 - Warn users when descriptor and port addresses are inconsistent.
825 Mitigates bug 13953; patch by teor.
827 o Minor features (controller):
828 - Allow controllers to configure basic client authorization on
829 hidden services when they create them with the ADD_ONION controller
830 command. Implements ticket 15588. Patch by "special".
831 - Fire a STATUS_SERVER controller event whenever the hibernation
832 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
833 - Implement new GETINFO queries for all downloads that use
834 download_status_t to schedule retries. This allows controllers to
835 examine the schedule for pending downloads. Closes ticket 19323.
837 o Minor features (development tools, etags):
838 - Teach the "make tags" Makefile target how to correctly find
839 "MOCK_IMPL" function definitions. Patch from nherring; closes
842 o Minor features (directory authority):
843 - After voting, if the authorities decide that a relay is not
844 "Valid", they no longer include it in the consensus at all. Closes
845 ticket 20002; implements part of proposal 272.
846 - Directory authorities now only give the Guard flag to a relay if
847 they are also giving it the Stable flag. This change allows us to
848 simplify path selection for clients. It should have minimal effect
849 in practice, since >99% of Guards already have the Stable flag.
850 Implements ticket 18624.
851 - Directory authorities now write their v3-status-votes file out to
852 disk earlier in the consensus process, so we have a record of the
853 votes even if we abort the consensus process. Resolves
856 o Minor features (fallback directory list, new since 0.2.9.7-rc):
857 - Replace the 81 remaining fallbacks of the 100 originally
858 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
859 fallbacks (123 new, 54 existing, 27 removed) generated in December
860 2016. Resolves ticket 20170.
862 o Minor features (hidden service):
863 - Stop being so strict about the payload length of "rendezvous1"
864 cells. We used to be locked in to the "TAP" handshake length, and
865 now we can handle better handshakes like "ntor". Resolves
868 o Minor features (infrastructure, time):
869 - Tor now includes an improved timer backend, so that we can
870 efficiently support tens or hundreds of thousands of concurrent
871 timers, as will be needed for some of our planned anti-traffic-
872 analysis work. This code is based on William Ahern's "timeout.c"
873 project, which implements a "tickless hierarchical timing wheel".
875 - Tor now uses the operating system's monotonic timers (where
876 available) for internal fine-grained timing. Previously we would
877 look at the system clock, and then attempt to compensate for the
878 clock running backwards. Closes ticket 18908.
880 o Minor features (logging):
881 - Add a set of macros to check nonfatal assertions, for internal
882 use. Migrating more of our checks to these should help us avoid
883 needless crash bugs. Closes ticket 18613.
884 - Provide a more useful warning message when configured with an
885 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
886 - When dumping unparseable router descriptors, optionally store them
887 in separate files, named by digest, up to a configurable size
888 limit. You can change the size limit by setting the
889 MaxUnparseableDescSizeToLog option, and disable this feature by
890 setting that option to 0. Closes ticket 18322.
892 o Minor features (performance):
893 - Change the "optimistic data" extension from "off by default" to
894 "on by default". The default was ordinarily overridden by a
895 consensus option, but when clients were bootstrapping for the
896 first time, they would not have a consensus to get the option
897 from. Changing this default saves a round-trip during startup.
900 o Minor features (relay, usability):
901 - When the directory authorities refuse a bad relay's descriptor,
902 encourage the relay operator to contact us. Many relay operators
903 won't notice this line in their logs, but it's a win if even a few
904 learn why we don't like what their relay was doing. Resolves
907 o Minor features (security, TLS):
908 - Servers no longer support clients that lack AES ciphersuites.
909 (3DES is no longer considered an acceptable cipher.) We believe
910 that no such Tor clients currently exist, since Tor has required
911 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
913 o Minor features (testing):
914 - Disable memory protections on OpenBSD when performing our unit
915 tests for memwipe(). The test deliberately invokes undefined
916 behavior, and the OpenBSD protections interfere with this. Patch
917 from "rubiate". Closes ticket 20066.
918 - Move the test-network.sh script to chutney, and modify tor's test-
919 network.sh to call the (newer) chutney version when available.
920 Resolves ticket 19116. Patch by teor.
921 - Use the lcov convention for marking lines as unreachable, so that
922 we don't count them when we're generating test coverage data.
923 Update our coverage tools to understand this convention. Closes
925 - Our link-handshake unit tests now check that when invalid
926 handshakes fail, they fail with the error messages we expected.
927 - Our unit testing code that captures log messages no longer
928 prevents them from being written out if the user asked for them
929 (by passing --debug or --info or --notice or --warn to the "test"
930 binary). This change prevents us from missing unexpected log
931 messages simply because we were looking for others. Related to
933 - The unit tests now log all warning messages with the "BUG" flag.
934 Previously, they only logged errors by default. This change will
935 help us make our testing code more correct, and make sure that we
936 only hit this code when we mean to. In the meantime, however,
937 there will be more warnings in the unit test logs than before.
938 This is preparatory work for ticket 19999.
939 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
940 assertion as a test failure.
941 - We've done significant work to make the unit tests run faster.
943 o Minor features (testing, ipv6):
944 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
945 tests. Remove bridges+hs, as it's somewhat redundant. This
946 requires a recent chutney version that supports IPv6 clients,
947 relays, and authorities. Closes ticket 20069; patch by teor.
948 - Add the single-onion and single-onion-ipv6 chutney targets to
949 "make test-network-all". This requires a recent chutney version
950 with the single onion network flavors (git c72a652 or later).
951 Closes ticket 20072; patch by teor.
953 o Minor features (Tor2web):
954 - Make Tor2web clients respect ReachableAddresses. This feature was
955 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
956 0.2.8.7. Implements feature 20034. Patch by teor.
958 o Minor features (unix domain sockets):
959 - When configuring a unix domain socket for a SocksPort,
960 ControlPort, or Hidden service, you can now wrap the address in
961 quotes, using C-style escapes inside the quotes. This allows unix
962 domain socket paths to contain spaces. Resolves ticket 18753.
964 o Minor features (user interface):
965 - Tor now supports the ability to declare options deprecated, so
966 that we can recommend that people stop using them. Previously, this
967 was done in an ad-hoc way. There is a new --list-deprecated-options
968 command-line option to list all of the deprecated options. Closes
971 o Minor features (virtual addresses):
972 - Increase the maximum number of bits for the IPv6 virtual network
973 prefix from 16 to 104. In this way, the condition for address
974 allocation is less restrictive. Closes ticket 20151; feature
977 o Minor bug fixes (circuits):
978 - Use the CircuitBuildTimeout option whenever
979 LearnCircuitBuildTimeout is disabled. Previously, we would respect
980 the option when a user disabled it, but not when it was disabled
981 because some other option was set. Fixes bug 20073; bugfix on
982 0.2.4.12-alpha. Patch by teor.
984 o Minor bugfixes (build):
985 - The current Git revision when building from a local repository is
986 now detected correctly when using git worktrees. Fixes bug 20492;
987 bugfix on 0.2.3.9-alpha.
989 o Minor bugfixes (relay address discovery):
990 - Stop reordering IP addresses returned by the OS. This makes it
991 more likely that Tor will guess the same relay IP address every
992 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
993 Reported by René Mayrhofer, patch by "cypherpunks".
995 o Minor bugfixes (memory allocation):
996 - Change how we allocate memory for large chunks on buffers, to
997 avoid a (currently impossible) integer overflow, and to waste less
998 space when allocating unusually large chunks. Fixes bug 20081;
999 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
1001 o Minor bugfixes (bootstrap):
1002 - Remember the directory server we fetched the consensus or previous
1003 certificates from, and use it to fetch future authority
1004 certificates. This change improves bootstrapping performance.
1005 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
1007 o Minor bugfixes (circuits):
1008 - Make sure extend_info_from_router() is only called on servers.
1009 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
1011 o Minor bugfixes (client, fascistfirewall):
1012 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
1013 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
1015 o Minor bugfixes (client, unix domain sockets):
1016 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
1017 the client address is meaningless. Fixes bug 20261; bugfix
1020 o Minor bugfixes (code style):
1021 - Fix an integer signedness conversion issue in the case conversion
1022 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
1024 o Minor bugfixes (compilation):
1025 - Build correctly on versions of libevent2 without support for
1026 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
1028 - When building with Clang, use a full set of GCC warnings.
1029 (Previously, we included only a subset, because of the way we
1030 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
1031 - Detect Libevent2 functions correctly on systems that provide
1032 libevent2, but where libevent1 is linked with -levent. Fixes bug
1033 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
1034 - Run correctly when built on Windows build environments that
1035 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
1037 o Minor bugfixes (configuration):
1038 - When parsing quoted configuration values from the torrc file,
1039 handle Windows line endings correctly. Fixes bug 19167; bugfix on
1040 0.2.0.16-alpha. Patch from "Pingl".
1042 o Minor bugfixes (directory authority):
1043 - Authorities now sort the "package" lines in their votes, for ease
1044 of debugging. (They are already sorted in consensus documents.)
1045 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
1046 - Die with a more useful error when the operator forgets to place
1047 the authority_signing_key file into the keys directory. This
1048 avoids an uninformative assert & traceback about having an invalid
1049 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
1050 - When allowing private addresses, mark Exits that only exit to
1051 private locations as such. Fixes bug 20064; bugfix
1053 - When parsing a detached signature, make sure we use the length of
1054 the digest algorithm instead of a hardcoded DIGEST256_LEN in
1055 order to avoid comparing bytes out-of-bounds with a smaller digest
1056 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
1058 o Minor bugfixes (getpass):
1059 - Defensively fix a non-triggerable heap corruption at do_getpass()
1060 to protect ourselves from mistakes in the future. Fixes bug
1061 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
1064 o Minor bugfixes (guard selection):
1065 - Don't mark guards as unreachable if connection_connect() fails.
1066 That function fails for local reasons, so it shouldn't reveal
1067 anything about the status of the guard. Fixes bug 14334; bugfix
1069 - Use a single entry guard even if the NumEntryGuards consensus
1070 parameter is not provided. Fixes bug 17688; bugfix
1073 o Minor bugfixes (hidden services):
1074 - Increase the minimum number of internal circuits we preemptively
1075 build from 2 to 3, so a circuit is available when a client
1076 connects to another onion service. Fixes bug 13239; bugfix
1078 - Allow hidden services to run on IPv6 addresses even when the
1079 IPv6Exit option is not set. Fixes bug 18357; bugfix
1081 - Stop logging intro point details to the client log on certain
1082 error conditions. Fixed as part of bug 20012; bugfix on
1083 0.2.4.8-alpha. Patch by teor.
1084 - When deleting an ephemeral hidden service, close its intro points
1085 even if they are not completely open. Fixes bug 18604; bugfix
1087 - When configuring hidden services, check every hidden service
1088 directory's permissions. Previously, we only checked the last
1089 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
1091 o Minor bugfixes (IPv6, testing):
1092 - Check for IPv6 correctly on Linux when running test networks.
1093 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
1095 o Minor bugfixes (Linux seccomp2 sandbox):
1096 - Add permission to run the sched_yield() and sigaltstack() system
1097 calls, in order to support versions of Tor compiled with asan or
1098 ubsan code that use these calls. Now "sandbox 1" and
1099 "--enable-expensive-hardening" should be compatible on more
1100 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
1102 o Minor bugfixes (logging):
1103 - Downgrade a harmless log message about the
1104 pending_entry_connections list from "warn" to "info". Mitigates
1106 - Log a more accurate message when we fail to dump a microdescriptor.
1107 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
1108 - When logging a directory ownership mismatch, log the owning
1109 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
1110 - When we are unable to remove the bw_accounting file, do not warn
1111 if the reason we couldn't remove it was that it didn't exist.
1112 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
1114 o Minor bugfixes (memory leak):
1115 - Fix a series of slow memory leaks related to parsing torrc files
1116 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
1117 - Avoid a small memory leak when informing worker threads about
1118 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
1119 - Fix a small memory leak when receiving AF_UNIX connections on a
1120 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
1121 - When moving a signed descriptor object from a source to an
1122 existing destination, free the allocated memory inside that
1123 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
1124 - Fix a memory leak and use-after-free error when removing entries
1125 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
1126 0.2.5.5-alpha. Patch from "cypherpunks".
1127 - Fix a small, uncommon memory leak that could occur when reading a
1128 truncated ed25519 key file. Fixes bug 18956; bugfix
1131 o Minor bugfixes (option parsing):
1132 - Count unix sockets when counting client listeners (SOCKS, Trans,
1133 NATD, and DNS). This has no user-visible behavior changes: these
1134 options are set once, and never read. Required for correct
1135 behavior in ticket 17178. Fixes bug 19677; bugfix on
1136 0.2.6.3-alpha. Patch by teor.
1138 o Minor bugfixes (options):
1139 - Check the consistency of UseEntryGuards and EntryNodes more
1140 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
1142 - Stop changing the configured value of UseEntryGuards on
1143 authorities and Tor2web clients. Fixes bug 20074; bugfix on
1144 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
1147 o Minor bugfixes (relay):
1148 - Ensure relays don't make multiple connections during bootstrap.
1149 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
1150 - Do not try to parallelize workers more than 16x without the user
1151 explicitly configuring us to do so, even if we do detect more than
1152 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
1154 o Minor bugfixes (testing):
1155 - The test-stem and test-network makefile targets now depend only on
1156 the tor binary that they are testing. Previously, they depended on
1157 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
1158 patch from "cypherpunks".
1159 - Allow clients to retry HSDirs much faster in test networks. Fixes
1160 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
1161 - Avoid a unit test failure on systems with over 16 detectable CPU
1162 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
1163 - Let backtrace tests work correctly under AddressSanitizer:
1164 disable ASAN's detection of segmentation faults while running
1165 test_bt.sh, so that we can make sure that our own backtrace
1166 generation code works. Fixes bug 18934; bugfix
1167 on 0.2.5.2-alpha. Patch from "cypherpunks".
1168 - Fix the test-network-all target on out-of-tree builds by using the
1169 correct path to the test driver script. Fixes bug 19421; bugfix
1171 - Stop spurious failures in the local interface address discovery
1172 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
1174 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
1175 removed the ECDH ciphers which caused the tests to fail on
1176 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
1177 - The tor_tls_server_info_callback unit test no longer crashes when
1178 debug-level logging is turned on. Fixes bug 20041; bugfix
1181 o Minor bugfixes (time):
1182 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
1183 bugfix on all released tor versions.
1184 - When computing the difference between two times in milliseconds,
1185 we now round to the nearest millisecond correctly. Previously, we
1186 could sometimes round in the wrong direction. Fixes bug 19428;
1187 bugfix on 0.2.2.2-alpha.
1189 o Minor bugfixes (Tor2web):
1190 - Prevent Tor2web clients from running hidden services: these services
1191 are not anonymous due to the one-hop client paths. Fixes bug
1192 19678. Patch by teor.
1194 o Minor bugfixes (user interface):
1195 - Display a more accurate number of suppressed messages in the log
1196 rate-limiter. Previously, there was a potential integer overflow
1197 in the counter. Now, if the number of messages hits a maximum, the
1198 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
1200 - Fix a typo in the passphrase prompt for the ed25519 identity key.
1201 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
1203 o Code simplification and refactoring:
1204 - Remove redundant declarations of the MIN macro. Closes
1206 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
1207 Closes ticket 18462; patch from "icanhasaccount".
1208 - Split the 600-line directory_handle_command_get function into
1209 separate functions for different URL types. Closes ticket 16698.
1212 - Add module-level internal documentation for 36 C files that
1213 previously didn't have a high-level overview. Closes ticket 20385.
1214 - Correct the IPv6 syntax in our documentation for the
1215 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
1216 - Correct the minimum bandwidth value in torrc.sample, and queue a
1217 corresponding change for torrc.minimal. Closes ticket 20085.
1218 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
1219 ticket 19153. Patch from "U+039b".
1220 - Module-level documentation for several more modules. Closes
1221 tickets 19287 and 19290.
1222 - Document the --passphrase-fd option in the tor manpage. Fixes bug
1223 19504; bugfix on 0.2.7.3-rc.
1224 - Document the default PathsNeededToBuildCircuits value that's used
1225 by clients when the directory authorities don't set
1226 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
1227 Patch by teor, reported by Jesse V.
1228 - Fix manual for the User option: it takes a username, not a UID.
1229 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
1231 - Fix the description of the --passphrase-fd option in the
1232 tor-gencert manpage. The option is used to pass the number of a
1233 file descriptor to read the passphrase from, not to read the file
1234 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
1237 - We no longer include the (dead, deprecated) bufferevent code in
1238 Tor. Closes ticket 19450. Based on a patch from "U+039b".
1241 - Remove support for "GET /tor/bytes.txt" DirPort request, and
1242 "GETINFO dir-usage" controller request, which were only available
1243 via a compile-time option in Tor anyway. Feature was added in
1244 0.2.2.1-alpha. Resolves ticket 19035.
1245 - There is no longer a compile-time option to disable support for
1246 TransPort. (If you don't want TransPort, just don't use it.) Patch
1247 from "U+039b". Closes ticket 19449.
1250 - Run more workqueue tests as part of "make check". These had
1251 previously been implemented, but you needed to know special
1252 command-line options to enable them.
1253 - We now have unit tests for our code to reject zlib "compression
1254 bombs". (Fortunately, the code works fine.)
1257 Changes in version 0.2.8.11 - 2016-12-08
1258 Tor 0.2.8.11 backports fixes for additional portability issues that
1259 could prevent Tor from building correctly on OSX Sierra, or with
1260 OpenSSL 1.1. Affected users should upgrade; others can safely stay
1263 o Minor bugfixes (portability):
1264 - Avoid compilation errors when building on OSX Sierra. Sierra began
1265 to support the getentropy() and clock_gettime() APIs, but created
1266 a few problems in doing so. Tor 0.2.9 has a more thorough set of
1267 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
1268 monotonic time interfaces. Fixes bug 20865. Bugfix
1271 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
1272 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
1273 architectures. Closes ticket 20588.
1276 Changes in version 0.2.8.10 - 2016-12-02
1277 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
1278 unusable after they left standby mode. It also backports fixes for
1279 a few portability issues and a small but problematic memory leak.
1281 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
1282 - When Tor leaves standby because of a new application request, open
1283 circuits as needed to serve that request. Previously, we would
1284 potentially wait a very long time. Fixes part of bug 19969; bugfix
1287 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
1288 - Clients now respond to new application stream requests immediately
1289 when they arrive, rather than waiting up to one second before
1290 starting to handle them. Fixes part of bug 19969; bugfix
1293 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
1294 - Work around a bug in the OSX 10.12 SDK that would prevent us from
1295 successfully targeting earlier versions of OSX. Resolves
1298 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
1299 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
1300 20551; bugfix on 0.2.1.1-alpha.
1302 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
1303 - Work around a memory leak in OpenSSL 1.1 when encoding public
1304 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
1306 o Minor features (geoip):
1307 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
1311 Changes in version 0.2.8.9 - 2016-10-17
1312 Tor 0.2.8.9 backports a fix for a security hole in previous versions
1313 of Tor that would allow a remote attacker to crash a Tor client,
1314 hidden service, relay, or authority. All Tor users should upgrade to
1315 this version, or to 0.2.9.4-alpha. Patches will be released for older
1318 o Major features (security fixes, also in 0.2.9.4-alpha):
1319 - Prevent a class of security bugs caused by treating the contents
1320 of a buffer chunk as if they were a NUL-terminated string. At
1321 least one such bug seems to be present in all currently used
1322 versions of Tor, and would allow an attacker to remotely crash
1323 most Tor instances, especially those compiled with extra compiler
1324 hardening. With this defense in place, such bugs can't crash Tor,
1325 though we should still fix them as they occur. Closes ticket
1326 20384 (TROVE-2016-10-001).
1328 o Minor features (geoip):
1329 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
1333 Changes in version 0.2.8.8 - 2016-09-23
1334 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
1335 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
1336 who select public relays as their bridges.
1338 o Major bugfixes (crash):
1339 - Fix a complicated crash bug that could affect Tor clients
1340 configured to use bridges when replacing a networkstatus consensus
1341 in which one of their bridges was mentioned. OpenBSD users saw
1342 more crashes here, but all platforms were potentially affected.
1343 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
1345 o Major bugfixes (relay, OOM handler):
1346 - Fix a timing-dependent assertion failure that could occur when we
1347 tried to flush from a circuit after having freed its cells because
1348 of an out-of-memory condition. Fixes bug 20203; bugfix on
1349 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
1352 o Minor feature (fallback directories):
1353 - Remove broken fallbacks from the hard-coded fallback directory
1354 list. Closes ticket 20190; patch by teor.
1356 o Minor features (geoip):
1357 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
1361 Changes in version 0.2.8.7 - 2016-08-24
1362 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
1363 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
1364 who sets the ReachableAddresses option, and all bridges, are strongly
1365 encouraged to upgrade.
1367 o Directory authority changes:
1368 - The "Tonga" bridge authority has been retired; the new bridge
1369 authority is "Bifroest". Closes tickets 19728 and 19690.
1371 o Major bugfixes (client, security):
1372 - Only use the ReachableAddresses option to restrict the first hop
1373 in a path. In earlier versions of 0.2.8.x, it would apply to
1374 every hop in the path, with a possible degradation in anonymity
1375 for anyone using an uncommon ReachableAddress setting. Fixes bug
1376 19973; bugfix on 0.2.8.2-alpha.
1378 o Minor features (geoip):
1379 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
1382 o Minor bugfixes (compilation):
1383 - Remove an inappropriate "inline" in tortls.c that was causing
1384 warnings on older versions of GCC. Fixes bug 19903; bugfix
1387 o Minor bugfixes (fallback directories):
1388 - Avoid logging a NULL string pointer when loading fallback
1389 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
1390 and 0.2.8.1-alpha. Report and patch by "rubiate".
1393 Changes in version 0.2.8.6 - 2016-08-02
1395 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
1397 The Tor 0.2.8 series improves client bootstrapping performance,
1398 completes the authority-side implementation of improved identity
1399 keys for relays, and includes numerous bugfixes and performance
1400 improvements throughout the program. This release continues to
1401 improve the coverage of Tor's test suite. For a full list of
1402 changes since Tor 0.2.7, see the ReleaseNotes file.
1404 Below is a list of the changes since Tor 0.2.7.
1406 o New system requirements:
1407 - Tor no longer attempts to support platforms where the "time_t"
1408 type is unsigned. (To the best of our knowledge, only OpenVMS does
1409 this, and Tor has never actually built on OpenVMS.) Closes
1411 - Tor no longer supports versions of OpenSSL with a broken
1412 implementation of counter mode. (This bug was present in OpenSSL
1413 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
1414 longer runs with, these versions.
1415 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
1416 later (released in 2008 and 2009 respectively). If you are
1417 building Tor from the git repository instead of from the source
1418 distribution, and your tools are older than this, you will need to
1419 upgrade. Closes ticket 17732.
1421 o Directory authority changes:
1422 - Update the V3 identity key for the dannenberg directory authority:
1423 it was changed on 18 November 2015. Closes task 17906. Patch
1425 - Urras is no longer a directory authority. Closes ticket 19271.
1427 o Major features (directory system):
1428 - Include a trial list of default fallback directories, based on an
1429 opt-in survey of suitable relays. Doing this should make clients
1430 bootstrap more quickly and reliably, and reduce the load on the
1431 directory authorities. Closes ticket 15775. Patch by teor.
1432 Candidates identified using an OnionOO script by weasel, teor,
1433 gsathya, and karsten.
1434 - Previously only relays that explicitly opened a directory port
1435 (DirPort) accepted directory requests from clients. Now all
1436 relays, with and without a DirPort, accept and serve tunneled
1437 directory requests that they receive through their ORPort. You can
1438 disable this behavior using the new DirCache option. Closes
1440 - When bootstrapping multiple consensus downloads at a time, use the
1441 first one that starts downloading, and close the rest. This
1442 reduces failures when authorities or fallback directories are slow
1443 or down. Together with the code for feature 15775, this feature
1444 should reduces failures due to fallback churn. Implements ticket
1445 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
1448 o Major features (security, Linux):
1449 - When Tor starts as root on Linux and is told to switch user ID, it
1450 can now retain the capability to bind to low ports. By default,
1451 Tor will do this only when it's switching user ID and some low
1452 ports have been configured. You can change this behavior with the
1453 new option KeepBindCapabilities. Closes ticket 8195.
1455 o Major bugfixes (client, bootstrapping):
1456 - Check if bootstrap consensus downloads are still needed when the
1457 linked connection attaches. This prevents tor making unnecessary
1458 begindir-style connections, which are the only directory
1459 connections tor clients make since the fix for 18483 was merged.
1460 - Fix some edge cases where consensus download connections may not
1461 have been closed, even though they were not needed. Related to fix
1463 - Make relays retry consensus downloads the correct number of times,
1464 rather than the more aggressive client retry count. Fixes part of
1467 o Major bugfixes (dns proxy mode, crash):
1468 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1469 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1471 o Major bugfixes (ed25519, voting):
1472 - Actually enable support for authorities to match routers by their
1473 Ed25519 identities. Previously, the code had been written, but
1474 some debugging code that had accidentally been left in the
1475 codebase made it stay turned off. Fixes bug 17702; bugfix
1477 - When collating votes by Ed25519 identities, authorities now
1478 include a "NoEdConsensus" flag if the ed25519 value (or lack
1479 thereof) for a server does not reflect the majority consensus.
1480 Related to bug 17668; bugfix on 0.2.7.2-alpha.
1481 - When generating a vote with keypinning disabled, never include two
1482 entries for the same ed25519 identity. This bug was causing
1483 authorities to generate votes that they could not parse when a
1484 router violated key pinning by changing its RSA identity but
1485 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
1486 18318. Bugfix on 0.2.7.2-alpha.
1488 o Major bugfixes (key management):
1489 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1490 pointer to the previous (uninitialized) key value. The impact here
1491 should be limited to a difficult-to-trigger crash, if OpenSSL is
1492 running an engine that makes key generation failures possible, or
1493 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1494 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1497 o Major bugfixes (security, client, DNS proxy):
1498 - Stop a crash that could occur when a client running with DNSPort
1499 received a query with multiple address types, and the first
1500 address type was not supported. Found and fixed by Scott Dial.
1501 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1503 o Major bugfixes (security, compilation):
1504 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
1505 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
1506 cause a compiler warning, thereby making other checks fail, and
1507 needlessly disabling compiler-hardening support. Fixes one case of
1508 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
1509 - Repair hardened builds under the clang compiler. Previously, our
1510 use of _FORTIFY_SOURCE would conflict with clang's address
1511 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
1513 o Major bugfixes (security, pointers):
1514 - Avoid a difficult-to-trigger heap corruption attack when extending
1515 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1516 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1517 Reported by Guido Vranken.
1519 o Major bugfixes (testing):
1520 - Fix a bug that would block 'make test-network-all' on systems where
1521 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
1523 o Major bugfixes (user interface):
1524 - Correctly give a warning in the cases where a relay is specified
1525 by nickname, and one such relay is found, but it is not officially
1526 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
1528 o Minor features (accounting):
1529 - Added two modes to the AccountingRule option: One for limiting
1530 only the number of bytes sent ("AccountingRule out"), and one for
1531 limiting only the number of bytes received ("AccountingRule in").
1532 Closes ticket 15989; patch from "unixninja92".
1534 o Minor features (bug-resistance):
1535 - Make Tor survive errors involving connections without a
1536 corresponding event object. Previously we'd fail with an
1537 assertion; now we produce a log message. Related to bug 16248.
1538 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
1539 level code, to harden against accidental failures to NUL-
1540 terminate. Part of ticket 17852. Patch from jsturgix. Found
1543 o Minor features (build):
1544 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
1545 as having possible IPFW support. Closes ticket 18448. Patch from
1547 - Since our build process now uses "make distcheck", we no longer
1548 force "make dist" to depend on "make check". Closes ticket 17893;
1549 patch from "cypherpunks".
1550 - Tor now builds once again with the recent OpenSSL 1.1 development
1551 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
1552 tracking OpenSSL 1.1 development as it has progressed, and fixing
1553 numerous compatibility issues as they arose. See tickets
1554 17549, 17921, 17984, 19499, and 18286.
1555 - When building manual pages, set the timezone to "UTC", so that the
1556 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
1557 Patch from intrigeri.
1559 o Minor features (clients):
1560 - Make clients, onion services, and bridge relays always use an
1561 encrypted begindir connection for directory requests. Resolves
1562 ticket 18483. Patch by teor.
1564 o Minor features (controller):
1565 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
1566 controllers can examine the the reject rules added by
1567 ExitPolicyRejectPrivate. This makes it easier for stem to display
1569 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
1570 tickets 16774 and 17817. Patch by George Tankersley.
1571 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
1572 service descriptor from a service's local hidden service
1573 descriptor cache. Closes ticket 14846.
1575 o Minor features (crypto):
1576 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
1577 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
1579 - Improve performance when hashing non-multiple of 8 sized buffers,
1580 based on Andrew Moon's public domain SipHash-2-4 implementation.
1581 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
1582 - Validate the hard-coded Diffie-Hellman parameters and ensure that
1583 p is a safe prime, and g is a suitable generator. Closes
1585 - When allocating a digest state object, allocate no more space than
1586 we actually need. Previously, we would allocate as much space as
1587 the state for the largest algorithm would need. This change saves
1588 up to 672 bytes per circuit. Closes ticket 17796.
1590 o Minor features (directory downloads):
1591 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
1592 directory mirrors. The default is 1; set it to 0 to disable
1593 fallbacks. Implements ticket 17576. Patch by teor.
1594 - Wait for busy authorities and fallback directories to become non-
1595 busy when bootstrapping. (A similar change was made in 6c443e987d
1596 for directory caches chosen from the consensus.) Closes ticket
1597 17864; patch by teor.
1599 o Minor features (geoip):
1600 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
1603 o Minor features (hidden service directory):
1604 - Streamline relay-side hsdir handling: when relays consider whether
1605 to accept an uploaded hidden service descriptor, they no longer
1606 check whether they are one of the relays in the network that is
1607 "supposed" to handle that descriptor. Implements ticket 18332.
1609 o Minor features (IPv6):
1610 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
1611 to 1, tor prefers IPv6 directory addresses.
1612 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
1613 avoids using IPv4 for client OR and directory connections.
1614 - Add address policy assume_action support for IPv6 addresses.
1615 - Add an argument 'ipv6=address:orport' to the DirAuthority and
1616 FallbackDir torrc options, to specify an IPv6 address for an
1617 authority or fallback directory. Add hard-coded ipv6 addresses for
1618 directory authorities that have them. Closes ticket 17327; patch
1619 from Nick Mathewson and teor.
1620 - Allow users to configure directory authorities and fallback
1621 directory servers with IPv6 addresses and ORPorts. Resolves
1623 - Limit IPv6 mask bits to 128.
1624 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
1625 17638; bugfix on 0.0.2pre8. Patch by teor.
1626 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
1627 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
1628 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
1629 - Warn when comparing against an AF_UNSPEC address in a policy, it's
1630 almost always a bug. Closes ticket 17863; patch by teor.
1631 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
1632 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
1634 o Minor features (Linux seccomp2 sandbox):
1635 - Reject attempts to change our Address with "Sandbox 1" enabled.
1636 Changing Address with Sandbox turned on would never actually work,
1637 but previously it would fail in strange and confusing ways. Found
1640 o Minor features (logging):
1641 - When logging to syslog, allow a tag to be added to the syslog
1642 identity (the string prepended to every log message). The tag can
1643 be configured with SyslogIdentityTag and defaults to none. Setting
1644 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
1647 o Minor features (portability):
1648 - Use timingsafe_memcmp() where available. Closes ticket 17944;
1649 patch from <logan@hackers.mu>.
1651 o Minor features (relay, address discovery):
1652 - Add a family argument to get_interface_addresses_raw() and
1653 subfunctions to make network interface address interogation more
1654 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
1655 types of interfaces from the operating system. Resolves
1657 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
1658 fails to enumerate interface addresses using the platform-specific
1659 API, have it rely on the UDP socket fallback technique to try and
1660 find out what IP addresses (both IPv4 and IPv6) our machine has.
1661 Resolves ticket 17951.
1663 o Minor features (replay cache):
1664 - The replay cache now uses SHA256 instead of SHA1. Implements
1665 feature 8961. Patch by teor, issue reported by rransom.
1667 o Minor features (robustness):
1668 - Exit immediately with an error message if the code attempts to use
1669 Libevent without having initialized it. This should resolve some
1670 frequently-made mistakes in our unit tests. Closes ticket 18241.
1672 o Minor features (security, clock):
1673 - Warn when the system clock appears to move back in time (when the
1674 state file was last written in the future). Tor doesn't know that
1675 consensuses have expired if the clock is in the past. Patch by
1676 teor. Implements ticket 17188.
1678 o Minor features (security, exit policies):
1679 - ExitPolicyRejectPrivate now rejects more private addresses by
1680 default. Specifically, it now rejects the relay's outbound bind
1681 addresses (if configured), and the relay's configured port
1682 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
1683 0.2.0.11-alpha. Patch by teor.
1685 o Minor features (security, memory erasure):
1686 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1687 zero size. Check size argument to memwipe() for underflow. Fixes
1688 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1690 - Set the unused entries in a smartlist to NULL. This helped catch
1691 a (harmless) bug, and shouldn't affect performance too much.
1692 Implements ticket 17026.
1693 - Use SecureMemoryWipe() function to securely clean memory on
1694 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
1695 Implements feature 17986.
1696 - Use explicit_bzero or memset_s when present. Previously, we'd use
1697 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
1698 from <logan@hackers.mu> and <selven@hackers.mu>.
1700 o Minor features (security, RNG):
1701 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
1702 positively are not allowed to fail. Previously we depended on
1703 internal details of OpenSSL's behavior. Closes ticket 17686.
1704 - Never use the system entropy output directly for anything besides
1705 seeding the PRNG. When we want to generate important keys, instead
1706 of using system entropy directly, we now hash it with the PRNG
1707 stream. This may help resist certain attacks based on broken OS
1708 entropy implementations. Closes part of ticket 17694.
1709 - Use modern system calls (like getentropy() or getrandom()) to
1710 generate strong entropy on platforms that have them. Closes
1713 o Minor features (security, win32):
1714 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
1715 attack. Fixes bug 18123; bugfix on all tor versions. Patch
1718 o Minor features (unix domain sockets):
1719 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
1720 Unix domain sockets without checking the permissions on the parent
1721 directory. (Tor checks permissions by default because some
1722 operating systems only check permissions on the parent directory.
1723 However, some operating systems do look at permissions on the
1724 socket, and tor's default check is unneeded.) Closes ticket 18458.
1727 o Minor features (unix file permissions):
1728 - Defer creation of Unix sockets until after setuid. This avoids
1729 needing CAP_CHOWN and CAP_FOWNER when using systemd's
1730 CapabilityBoundingSet, or chown and fowner when using SELinux.
1731 Implements part of ticket 17562. Patch from Jamie Nguyen.
1732 - If any directory created by Tor is marked as group readable, the
1733 filesystem group is allowed to be either the default GID or the
1734 root user. Allowing root to read the DataDirectory prevents the
1735 need for CAP_READ_SEARCH when using systemd's
1736 CapabilityBoundingSet, or dac_read_search when using SELinux.
1737 Implements part of ticket 17562. Patch from Jamie Nguyen.
1738 - Introduce a new DataDirectoryGroupReadable option. If it is set to
1739 1, the DataDirectory will be made readable by the default GID.
1740 Implements part of ticket 17562. Patch from Jamie Nguyen.
1742 o Minor bugfixes (accounting):
1743 - The max bandwidth when using 'AccountRule sum' is now correctly
1744 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
1747 o Minor bugfixes (assert, portability):
1748 - Fix an assertion failure in memarea.c on systems where "long" is
1749 shorter than the size of a pointer. Fixes bug 18716; bugfix
1752 o Minor bugfixes (bootstrap):
1753 - Consistently use the consensus download schedule for authority
1754 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
1756 o Minor bugfixes (build):
1757 - Avoid spurious failures from configure files related to calling
1758 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
1759 0.2.0.1-alpha. Patch from "cypherpunks".
1760 - Do not link the unit tests against both the testing and non-
1761 testing versions of the static libraries. Fixes bug 18490; bugfix
1763 - Resolve warnings when building on systems that are concerned with
1764 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
1766 - Silence spurious clang-scan warnings in the ed25519_donna code by
1767 explicitly initializing some objects. Fixes bug 18384; bugfix on
1768 0.2.7.2-alpha. Patch by teor.
1769 - When libscrypt.h is found, but no libscrypt library can be linked,
1770 treat libscrypt as absent. Fixes bug 19161; bugfix
1772 - Cause the unit tests to compile correctly on mingw64 versions that
1773 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
1774 - Don't try to use the pthread_condattr_setclock() function unless
1775 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
1776 17819; bugfix on 0.2.6.3-alpha.
1777 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
1779 - Fix search for libevent libraries on OpenBSD (and other systems
1780 that install libevent 1 and libevent 2 in parallel). Fixes bug
1781 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
1782 - Isolate environment variables meant for tests from the rest of the
1783 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
1784 - Mark all object files that include micro-revision.i as depending
1785 on it, so as to make parallel builds more reliable. Fixes bug
1786 17826; bugfix on 0.2.5.1-alpha.
1787 - Remove config.log only from make distclean, not from make clean.
1788 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
1789 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
1791 - Remove an #endif from configure.ac so that we correctly detect the
1792 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
1795 o Minor bugfixes (client, bootstrap):
1796 - Count receipt of new microdescriptors as progress towards
1797 bootstrapping. Previously, with EntryNodes set, Tor might not
1798 successfully repopulate the guard set on bootstrapping. Fixes bug
1799 16825; bugfix on 0.2.3.1-alpha.
1801 o Minor bugfixes (code correctness):
1802 - Fix a bad memory handling bug that would occur if we had queued a
1803 cell on a channel's incoming queue. Fortunately, we can't actually
1804 queue a cell like that as our code is constructed today, but it's
1805 best to avoid this kind of error, even if there isn't any code
1806 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
1807 - Assert that allocated memory held by the reputation code is freed
1808 according to its internal counters. Fixes bug 17753; bugfix
1810 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
1812 - Update to the latest version of Trunnel, which tries harder to
1813 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
1814 by clang address sanitizer. Fixes bug 18373; bugfix
1816 - When closing an entry connection, generate a warning if we should
1817 have sent an end cell for it but we haven't. Fixes bug 17876;
1818 bugfix on 0.2.3.2-alpha.
1820 o Minor bugfixes (configuration):
1821 - Fix a tiny memory leak when parsing a port configuration ending in
1822 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
1824 o Minor bugfixes (containers):
1825 - If we somehow attempt to construct a heap with more than
1826 1073741822 elements, avoid an integer overflow when maintaining
1827 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
1829 o Minor bugfixes (controller, microdescriptors):
1830 - Make GETINFO dir/status-vote/current/consensus conform to the
1831 control specification by returning "551 Could not open cached
1832 consensus..." when not caching consensuses. Fixes bug 18920;
1833 bugfix on 0.2.2.6-alpha.
1835 o Minor bugfixes (crypto):
1836 - Check the return value of HMAC() and assert on failure. Fixes bug
1837 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
1839 o Minor bugfixes (directories):
1840 - When fetching extrainfo documents, compare their SHA256 digests
1841 and Ed25519 signing key certificates with the routerinfo that led
1842 us to fetch them, rather than with the most recent routerinfo.
1843 Otherwise we generate many spurious warnings about mismatches.
1844 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
1845 - When generating a URL for a directory server on an IPv6 address,
1846 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
1847 on 0.2.3.9-alpha. Patch from Malek.
1849 o Minor bugfixes (downloading):
1850 - Predict more correctly whether we'll be downloading over HTTP when
1851 we determine the maximum length of a URL. This should avoid a
1852 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
1855 o Minor bugfixes (exit policies, security):
1856 - Refresh an exit relay's exit policy when interface addresses
1857 change. Previously, tor only refreshed the exit policy when the
1858 configured external address changed. Fixes bug 18208; bugfix on
1859 0.2.7.3-rc. Patch by teor.
1861 o Minor bugfixes (fallback directories):
1862 - Mark fallbacks as "too busy" when they return a 503 response,
1863 rather than just marking authorities. Fixes bug 17572; bugfix on
1864 0.2.4.7-alpha. Patch by teor.
1865 - When requesting extrainfo descriptors from a trusted directory
1866 server, check whether it is an authority or a fallback directory
1867 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
1868 0.2.4.7-alpha. Reported by atagar, patch by teor.
1870 o Minor bugfixes (hidden service, client):
1871 - Handle the case where the user makes several fast consecutive
1872 requests to the same .onion address. Previously, the first six
1873 requests would each trigger a descriptor fetch, each picking a
1874 directory (there are 6 overall) and the seventh one would fail
1875 because no directories were left, thereby triggering a close on
1876 all current directory connections asking for the hidden service.
1877 The solution here is to not close the connections if we have
1878 pending directory fetches. Fixes bug 15937; bugfix
1881 o Minor bugfixes (hidden service, control port):
1882 - Add the onion address to the HS_DESC event for the UPLOADED action
1883 both on success or failure. It was previously hardcoded with
1884 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
1886 o Minor bugfixes (hidden service, directory):
1887 - Bridges now refuse "rendezvous2" (hidden service descriptor)
1888 publish attempts. Suggested by ticket 18332.
1890 o Minor bugfixes (IPv6):
1891 - Update the limits in max_dl_per_request for IPv6 address length.
1892 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
1894 o Minor bugfixes (Linux seccomp2 sandbox):
1895 - Allow more syscalls when running with "Sandbox 1" enabled:
1896 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
1897 some systems, these are required for Tor to start. Fixes bug
1898 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
1899 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
1900 so that get_interface_address6_via_udp_socket_hack() can work.
1901 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
1902 - Allow the setrlimit syscall, and the prlimit and prlimit64
1903 syscalls, which some libc implementations use under the hood.
1904 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
1905 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
1906 enabled and no DNS resolvers configured. This should help TAILS
1907 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
1908 - Fix a crash when using offline master ed25519 keys with the Linux
1909 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
1910 - Allow statistics to be written to disk when "Sandbox 1" is
1911 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
1912 0.2.6.1-alpha respectively.
1914 o Minor bugfixes (logging):
1915 - In log messages that include a function name, use __FUNCTION__
1916 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
1917 with clang __PRETTY_FUNCTION__ has extra information we don't
1918 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
1920 - Remove needless quotes from a log message about unparseable
1921 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
1922 - Scrub service name in "unrecognized service ID" log messages.
1923 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
1924 - When logging information about an unparsable networkstatus vote or
1925 consensus, do not say "vote" when we mean consensus. Fixes bug
1926 18368; bugfix on 0.2.0.8-alpha.
1927 - When we can't generate a signing key because OfflineMasterKey is
1928 set, do not imply that we should have been able to load it. Fixes
1929 bug 18133; bugfix on 0.2.7.2-alpha.
1930 - When logging a malformed hostname received through socks4, scrub
1931 it if SafeLogging says we should. Fixes bug 17419; bugfix
1934 o Minor bugfixes (memory safety):
1935 - Avoid freeing an uninitialized pointer when opening a socket fails
1936 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
1937 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
1939 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
1940 18672; bugfix on 0.2.5.1-alpha.
1941 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
1944 o Minor bugfixes (pluggable transports):
1945 - Avoid reporting a spurious error when we decide that we don't need
1946 to terminate a pluggable transport because it has already exited.
1947 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
1949 o Minor bugfixes (pointer arithmetic):
1950 - Fix a bug in memarea_alloc() that could have resulted in remote
1951 heap write access, if Tor had ever passed an unchecked size to
1952 memarea_alloc(). Fortunately, all the sizes we pass to
1953 memarea_alloc() are pre-checked to be less than 128 kilobytes.
1954 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
1957 o Minor bugfixes (private directory):
1958 - Prevent a race condition when creating private directories. Fixes
1959 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
1960 Patch from jsturgix. Found with Flawfinder.
1962 o Minor bugfixes (relays):
1963 - Check that both the ORPort and DirPort (if present) are reachable
1964 before publishing a relay descriptor. Otherwise, relays publish a
1965 descriptor with DirPort 0 when the DirPort reachability test takes
1966 longer than the ORPort reachability test. Fixes bug 18050; bugfix
1967 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
1968 - Resolve some edge cases where we might launch an ORPort
1969 reachability check even when DisableNetwork is set. Noticed while
1970 fixing bug 18616; bugfix on 0.2.3.9-alpha.
1972 o Minor bugfixes (relays, hidden services):
1973 - Refuse connection requests to private OR addresses unless
1974 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
1975 then refuse to send any cells to a private address. Fixes bugs
1976 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
1978 o Minor bugfixes (security, hidden services):
1979 - Prevent hidden services connecting to client-supplied rendezvous
1980 addresses that are reserved as internal or multicast. Fixes bug
1981 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
1983 o Minor bugfixes (statistics):
1984 - Consistently check for overflow in round_*_to_next_multiple_of
1985 functions, and add unit tests with additional and maximal values.
1986 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
1987 - Handle edge cases in the laplace functions: avoid division by
1988 zero, avoid taking the log of zero, and silence clang type
1989 conversion warnings using round and trunc. Add unit tests for edge
1990 cases with maximal values. Fixes part of bug 13192; bugfix
1992 - We now include consensus downloads via IPv6 in our directory-
1993 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
1995 o Minor bugfixes (test networks, IPv6):
1996 - Allow internal IPv6 addresses in descriptors in test networks.
1997 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
2000 o Minor bugfixes (testing):
2001 - Check the full results of SHA256 and SHA512 digests in the unit
2002 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
2003 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
2005 - Fix a small memory leak that would occur when the
2006 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
2007 bugfix on 0.2.5.2-alpha.
2008 - Make unit tests pass on IPv6-only systems, and systems without
2009 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
2010 bugfix on 0.2.7.3-rc. Patch by teor.
2011 - The test for log_heartbeat was incorrectly failing in timezones
2012 with non-integer offsets. Instead of comparing the end of the time
2013 string against a constant, compare it to the output of
2014 format_local_iso_time when given the correct input. Fixes bug
2015 18039; bugfix on 0.2.5.4-alpha.
2016 - We no longer disable assertions in the unit tests when coverage is
2017 enabled. Instead, we require you to say --disable-asserts-in-tests
2018 to the configure script if you need assertions disabled in the
2019 unit tests (for example, if you want to perform branch coverage).
2020 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
2022 o Minor bugfixes (time handling):
2023 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
2024 field. Otherwise, our unit tests crash on Windows. Fixes bug
2025 18977; bugfix on 0.2.2.25-alpha.
2026 - Avoid overflow in tor_timegm when parsing dates in and after 2038
2027 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
2028 0.0.2pre14. Patch by teor.
2030 o Minor bugfixes (tor-gencert):
2031 - Correctly handle the case where an authority operator enters a
2032 passphrase but sends an EOF before sending a newline. Fixes bug
2033 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
2035 o Code simplification and refactoring:
2036 - Clean up a little duplicated code in
2037 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
2039 - Decouple the list of streams waiting to be attached to circuits
2040 from the overall connection list. This change makes it possible to
2041 attach streams quickly while simplifying Tor's callgraph and
2042 avoiding O(N) scans of the entire connection list. Closes
2044 - Extract the more complicated parts of circuit_mark_for_close()
2045 into a new function that we run periodically before circuits are
2046 freed. This change removes more than half of the functions
2047 currently in the "blob". Closes ticket 17218.
2048 - Move logging of redundant policy entries in
2049 policies_parse_exit_policy_internal into its own function. Closes
2050 ticket 17608; patch from "juce".
2051 - Quote all the string interpolations in configure.ac -- even those
2052 which we are pretty sure can't contain spaces. Closes ticket
2053 17744. Patch from zerosion.
2054 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
2055 use them. Closes ticket 17926.
2056 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
2057 inplace, so there's no need to have a separate implementation for
2058 the non-inplace code. Closes ticket 18258. Patch from Malek.
2059 - Simplify return types for some crypto functions that can't
2060 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
2061 - When a direct directory request fails immediately on launch,
2062 instead of relaunching that request from inside the code that
2063 launches it, instead mark the connection for teardown. This change
2064 simplifies Tor's callback and prevents the directory-request
2065 launching code from invoking itself recursively. Closes
2069 - Add a description of the correct use of the '--keygen' command-
2070 line option. Closes ticket 17583; based on text by 's7r'.
2071 - Change build messages to refer to "Fedora" instead of "Fedora
2072 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
2073 Patches from "icanhasaccount" and "cypherpunks".
2074 - Document the contents of the 'datadir/keys' subdirectory in the
2075 manual page. Closes ticket 17621.
2076 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
2077 - Explain actual minima for BandwidthRate. Closes ticket 16382.
2078 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
2079 - Mention torspec URL in the manpage and point the reader to it
2080 whenever we mention a document that belongs in torspce. Fixes
2082 - Stop recommending use of nicknames to identify relays in our
2083 MapAddress documentation. Closes ticket 18312.
2086 - Remove client-side support for connecting to Tor relays running
2087 versions of Tor before 0.2.3.6-alpha. These relays didn't support
2088 the v3 TLS handshake protocol, and are no longer allowed on the
2089 Tor network. Implements the client side of ticket 11150. Based on
2090 patches by Tom van der Woerdt.
2091 - We no longer maintain an internal freelist in memarea.c.
2092 Allocators should be good enough to make this code unnecessary,
2093 and it's doubtful that it ever had any performance benefit.
2096 - Add unit tests to check for common RNG failure modes, such as
2097 returning all zeroes, identical values, or incrementing values
2098 (OpenSSL's rand_predictable feature). Patch by teor.
2099 - Always test both ed25519 backends, so that we can be sure that our
2100 batch-open replacement code works. Part of ticket 16794.
2101 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
2102 portion of ticket 16831.
2103 - Fix several warnings from clang's address sanitizer produced in
2105 - Log more information when the backtrace tests fail. Closes ticket
2106 17892. Patch from "cypherpunks."
2107 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
2108 util_format.c, directory.c, and options_validate.c. Closes tickets
2109 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
2111 - Treat backtrace test failures as expected on FreeBSD until we
2112 solve bug 17808. Closes ticket 18204.
2113 - Unit tests for directory_handle_command_get. Closes ticket 17004.
2114 Patch from Reinaldo de Souza Jr.
2117 Changes in version 0.2.7.6 - 2015-12-10
2118 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
2119 well as a minor bug in hidden service reliability.
2121 o Major bugfixes (guard selection):
2122 - Actually look at the Guard flag when selecting a new directory
2123 guard. When we implemented the directory guard design, we
2124 accidentally started treating all relays as if they have the Guard
2125 flag during guard selection, leading to weaker anonymity and worse
2126 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
2129 o Minor features (geoip):
2130 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
2133 o Minor bugfixes (compilation):
2134 - When checking for net/pfvar.h, include netinet/in.h if possible.
2135 This fixes transparent proxy detection on OpenBSD. Fixes bug
2136 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
2137 - Fix a compilation warning with Clang 3.6: Do not check the
2138 presence of an address which can never be NULL. Fixes bug 17781.
2140 o Minor bugfixes (correctness):
2141 - When displaying an IPv6 exit policy, include the mask bits
2142 correctly even when the number is greater than 31. Fixes bug
2143 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
2144 - The wrong list was used when looking up expired intro points in a
2145 rend service object, causing what we think could be reachability
2146 issues for hidden services, and triggering a BUG log. Fixes bug
2147 16702; bugfix on 0.2.7.2-alpha.
2148 - Fix undefined behavior in the tor_cert_checksig function. Fixes
2149 bug 17722; bugfix on 0.2.7.2-alpha.
2152 Changes in version 0.2.7.5 - 2015-11-20
2153 The Tor 0.2.7 release series is dedicated to the memory of Tor user
2154 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
2155 tirelessly to advocate human rights regardless of national borders,
2156 and oppose the encroachments of mass surveillance. He opposed national
2157 exceptionalism, he brought clarity to legal and policy debates, he
2158 understood and predicted the impact of mass surveillance on the world,
2159 and he laid the groundwork for resisting it. While serving on the Tor
2160 Project's board of directors, he brought us his uncompromising focus
2161 on technical excellence in the service of humankind. Caspar was an
2162 inimitable force for good and a wonderful friend. He was kind,
2163 humorous, generous, gallant, and believed we should protect one
2164 another without exception. We honor him here for his ideals, his
2165 efforts, and his accomplishments. Please honor his memory with works
2166 that would make him proud.
2168 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
2170 The 0.2.7 series adds a more secure identity key type for relays,
2171 improves cryptography performance, resolves several longstanding
2172 hidden-service performance issues, improves controller support for
2173 hidden services, and includes small bugfixes and performance
2174 improvements throughout the program. This release series also includes
2175 more tests than before, and significant simplifications to which parts
2176 of Tor invoke which others. For a full list of changes, see below.
2178 o New system requirements:
2179 - Tor no longer includes workarounds to support Libevent versions
2180 before 1.3e. Libevent 2.0 or later is recommended. Closes
2182 - Tor no longer supports copies of OpenSSL that are missing support
2183 for Elliptic Curve Cryptography. (We began using ECC when
2184 available in 0.2.4.8-alpha, for more safe and efficient key
2185 negotiation.) In particular, support for at least one of P256 or
2186 P224 is now required, with manual configuration needed if only
2187 P224 is available. Resolves ticket 16140.
2188 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
2189 on an operating system that has not upgraded to OpenSSL 1.0 or
2190 later, and you compile Tor from source, you will need to install a
2191 more recent OpenSSL to link Tor against.) These versions of
2192 OpenSSL are still supported by the OpenSSL, but the numerous
2193 cryptographic improvements in later OpenSSL releases makes them a
2194 clear choice. Resolves ticket 16034.
2196 o Major features (controller):
2197 - Add the ADD_ONION and DEL_ONION commands that allow the creation
2198 and management of hidden services via the controller. Closes
2200 - New "GETINFO onions/current" and "GETINFO onions/detached"
2201 commands to get information about hidden services created via the
2202 controller. Part of ticket 6411.
2203 - New HSFETCH command to launch a request for a hidden service
2204 descriptor. Closes ticket 14847.
2205 - New HSPOST command to upload a hidden service descriptor. Closes
2206 ticket 3523. Patch by "DonnchaC".
2208 o Major features (Ed25519 identity keys, Proposal 220):
2209 - Add support for offline encrypted Ed25519 master keys. To use this
2210 feature on your tor relay, run "tor --keygen" to make a new master
2211 key (or to make a new signing key if you already have a master
2212 key). Closes ticket 13642.
2213 - All relays now maintain a stronger identity key, using the Ed25519
2214 elliptic curve signature format. This master key is designed so
2215 that it can be kept offline. Relays also generate an online
2216 signing key, and a set of other Ed25519 keys and certificates.
2217 These are all automatically regenerated and rotated as needed.
2218 Implements part of ticket 12498.
2219 - Directory authorities now vote on Ed25519 identity keys along with
2220 RSA1024 keys. Implements part of ticket 12498.
2221 - Directory authorities track which Ed25519 identity keys have been
2222 used with which RSA1024 identity keys, and do not allow them to
2223 vary freely. Implements part of ticket 12498.
2224 - Microdescriptors now include Ed25519 identity keys. Implements
2225 part of ticket 12498.
2226 - Add a --newpass option to allow changing or removing the
2227 passphrase of an encrypted key with tor --keygen. Implements part
2229 - Add a new OfflineMasterKey option to tell Tor never to try loading
2230 or generating a secret Ed25519 identity key. You can use this in
2231 combination with tor --keygen to manage offline and/or encrypted
2232 Ed25519 keys. Implements ticket 16944.
2233 - On receiving a HUP signal, check to see whether the Ed25519
2234 signing key has changed, and reload it if so. Closes ticket 16790.
2235 - Significant usability improvements for Ed25519 key management. Log
2236 messages are better, and the code can recover from far more
2237 failure conditions. Thanks to "s7r" for reporting and diagnosing
2240 o Major features (ECC performance):
2241 - Improve the runtime speed of Ed25519 signature verification by
2242 using Ed25519-donna's batch verification support. Implements
2244 - Improve the speed of Ed25519 operations and Curve25519 keypair
2245 generation when built targeting 32 bit x86 platforms with SSE2
2246 available. Implements ticket 16535.
2247 - Improve the runtime speed of Ed25519 operations by using the
2248 public-domain Ed25519-donna by Andrew M. ("floodyberry").
2249 Implements ticket 16467.
2250 - Improve the runtime speed of the ntor handshake by using an
2251 optimized curve25519 basepoint scalarmult implementation from the
2252 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
2253 ideas by Adam Langley. Implements ticket 9663.
2255 o Major features (Hidden services):
2256 - Hidden services, if using the EntryNodes option, are required to
2257 use more than one EntryNode, in order to avoid a guard discovery
2258 attack. (This would only affect people who had configured hidden
2259 services and manually specified the EntryNodes option with a
2260 single entry-node. The impact was that it would be easy to
2261 remotely identify the guard node used by such a hidden service.
2262 See ticket for more information.) Fixes ticket 14917.
2263 - Add the torrc option HiddenServiceNumIntroductionPoints, to
2264 specify a fixed number of introduction points. Its maximum value
2265 is 10 and default is 3. Using this option can increase a hidden
2266 service's reliability under load, at the cost of making it more
2267 visible that the hidden service is facing extra load. Closes
2269 - Remove the adaptive algorithm for choosing the number of
2270 introduction points, which used to change the number of
2271 introduction points (poorly) depending on the number of
2272 connections the HS sees. Closes ticket 4862.
2274 o Major features (onion key cross-certification):
2275 - Relay descriptors now include signatures of their own identity
2276 keys, made using the TAP and ntor onion keys. These signatures
2277 allow relays to prove ownership of their own onion keys. Because
2278 of this change, microdescriptors will no longer need to include
2279 RSA identity keys. Implements proposal 228; closes ticket 12499.
2281 o Major bugfixes (client-side privacy, also in 0.2.6.9):
2282 - Properly separate out each SOCKSPort when applying stream
2283 isolation. The error occurred because each port's session group
2284 was being overwritten by a default value when the listener
2285 connection was initialized. Fixes bug 16247; bugfix on
2286 0.2.6.3-alpha. Patch by "jojelino".
2288 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
2289 - Stop refusing to store updated hidden service descriptors on a
2290 client. This reverts commit 9407040c59218 (which indeed fixed bug
2291 14219, but introduced a major hidden service reachability
2292 regression detailed in bug 16381). This is a temporary fix since
2293 we can live with the minor issue in bug 14219 (it just results in
2294 some load on the network) but the regression of 16381 is too much
2295 of a setback. First-round fix for bug 16381; bugfix
2298 o Major bugfixes (hidden services):
2299 - Revert commit that made directory authorities assign the HSDir
2300 flag to relay without a DirPort; this was bad because such relays
2301 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
2303 - When cannibalizing a circuit for an introduction point, always
2304 extend to the chosen exit node (creating a 4 hop circuit).
2305 Previously Tor would use the current circuit exit node, which
2306 changed the original choice of introduction point, and could cause
2307 the hidden service to skip excluded introduction points or
2308 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
2311 o Major bugfixes (memory leaks):
2312 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
2313 17398; bugfix on 0.2.6.1-alpha.
2315 o Major bugfixes (open file limit):
2316 - The open file limit wasn't checked before calling
2317 tor_accept_socket_nonblocking(), which would make Tor exceed the
2318 limit. Now, before opening a new socket, Tor validates the open
2319 file limit just before, and if the max has been reached, return an
2320 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
2322 o Major bugfixes (security, correctness):
2323 - Fix an error that could cause us to read 4 bytes before the
2324 beginning of an openssl string. This bug could be used to cause
2325 Tor to crash on systems with unusual malloc implementations, or
2326 systems with unusual hardening installed. Fixes bug 17404; bugfix
2329 o Major bugfixes (stability, also in 0.2.6.10):
2330 - Stop crashing with an assertion failure when parsing certain kinds
2331 of malformed or truncated microdescriptors. Fixes bug 16400;
2332 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
2333 by "cypherpunks_backup".
2334 - Stop random client-side assertion failures that could occur when
2335 connecting to a busy hidden service, or connecting to a hidden
2336 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
2339 o Minor features (client, SOCKS):
2340 - Add GroupWritable and WorldWritable options to unix-socket based
2341 SocksPort and ControlPort options. These options apply to a single
2342 socket, and override {Control,Socks}SocketsGroupWritable. Closes
2344 - Relax the validation done to hostnames in SOCKS5 requests, and
2345 allow a single trailing '.' to cope with clients that pass FQDNs
2346 using that syntax to explicitly indicate that the domain name is
2347 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
2348 - Relax the validation of hostnames in SOCKS5 requests, allowing the
2349 character '_' to appear, in order to cope with domains observed in
2350 the wild that are serving non-RFC compliant records. Resolves
2353 o Minor features (client-side privacy):
2354 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
2355 lifespan when IsolateSOCKSAuth and streams with SOCKS
2356 authentication are attached to the circuit. This allows
2357 applications like TorBrowser to manage circuit lifetime on their
2358 own. Implements feature 15482.
2359 - When logging malformed hostnames from SOCKS5 requests, respect
2360 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
2362 o Minor features (clock-jump tolerance):
2363 - Recover better when our clock jumps back many hours, like might
2364 happen for Tails or Whonix users who start with a very wrong
2365 hardware clock, use Tor to discover a more accurate time, and then
2366 fix their clock. Resolves part of ticket 8766.
2368 o Minor features (command-line interface):
2369 - Make --hash-password imply --hush to prevent unnecessary noise.
2370 Closes ticket 15542. Patch from "cypherpunks".
2371 - Print a warning whenever we find a relative file path being used
2372 as torrc option. Resolves issue 14018.
2374 o Minor features (compilation):
2375 - Give a warning as early as possible when trying to build with an
2376 unsupported OpenSSL version. Closes ticket 16901.
2377 - Use C99 variadic macros when the compiler is not GCC. This avoids
2378 failing compilations on MSVC, and fixes a log-file-based race
2379 condition in our old workarounds. Original patch from Gisle Vanem.
2381 o Minor features (control protocol):
2382 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
2383 the control protocol. Resolves ticket 15358.
2385 o Minor features (controller):
2386 - Add DirAuthority lines for default directory authorities to the
2387 output of the "GETINFO config/defaults" command if not already
2388 present. Implements ticket 14840.
2389 - Controllers can now use "GETINFO hs/client/desc/id/..." to
2390 retrieve items from the client's hidden service descriptor cache.
2391 Closes ticket 14845.
2392 - Implement a new controller command "GETINFO status/fresh-relay-
2393 descs" to fetch a descriptor/extrainfo pair that was generated on
2394 demand just for the controller's use. Implements ticket 14784.
2396 o Minor features (directory authorities):
2397 - Directory authorities no longer vote against the "Fast", "Stable",
2398 and "HSDir" flags just because they were going to vote against
2399 "Running": if the consensus turns out to be that the router was
2400 running, then the authority's vote should count. Patch from Peter
2401 Retzlaff; closes issue 8712.
2403 o Minor features (directory authorities, security, also in 0.2.6.9):
2404 - The HSDir flag given by authorities now requires the Stable flag.
2405 For the current network, this results in going from 2887 to 2806
2406 HSDirs. Also, it makes it harder for an attacker to launch a sybil
2407 attack by raising the effort for a relay to become Stable to
2408 require at the very least 7 days, while maintaining the 96 hours
2409 uptime requirement for HSDir. Implements ticket 8243.
2411 o Minor features (DoS-resistance):
2412 - Make it harder for attackers to overload hidden services with
2413 introductions, by blocking multiple introduction requests on the
2414 same circuit. Resolves ticket 15515.
2416 o Minor features (geoip):
2417 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
2420 o Minor features (hidden services):
2421 - Add the new options "HiddenServiceMaxStreams" and
2422 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
2423 limit the maximum number of simultaneous streams per circuit, and
2424 optionally tear down the circuit when the limit is exceeded. Part
2426 - Client now uses an introduction point failure cache to know when
2427 to fetch or keep a descriptor in their cache. Previously, failures
2428 were recorded implicitly, but not explicitly remembered. Closes
2430 - Relays need to have the Fast flag to get the HSDir flag. As this
2431 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
2432 drop. This change should make some attacks against the hidden
2433 service directory system harder. Fixes ticket 15963.
2434 - Turn on hidden service statistics collection by setting the torrc
2435 option HiddenServiceStatistics to "1" by default. (This keeps
2436 track only of the fraction of traffic used by hidden services, and
2437 the total number of hidden services in existence.) Closes
2439 - To avoid leaking HS popularity, don't cycle the introduction point
2440 when we've handled a fixed number of INTRODUCE2 cells but instead
2441 cycle it when a random number of introductions is reached, thus
2442 making it more difficult for an attacker to find out the amount of
2443 clients that have used the introduction point for a specific HS.
2444 Closes ticket 15745.
2446 o Minor features (logging):
2447 - Include the Tor version in all LD_BUG log messages, since people
2448 tend to cut and paste those into the bugtracker. Implements
2451 o Minor features (pluggable transports):
2452 - When launching managed pluggable transports on Linux systems,
2453 attempt to have the kernel deliver a SIGTERM on tor exit if the
2454 pluggable transport process is still running. Resolves
2456 - When launching managed pluggable transports, setup a valid open
2457 stdin in the child process that can be used to detect if tor has
2458 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
2459 can be used by implementations to detect this new behavior.
2460 Resolves ticket 15435.
2462 o Minor bugfixes (torrc exit policies):
2463 - In each instance above, usage advice is provided to avoid the
2464 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
2465 16069; bugfix on 0.2.4.7-alpha.
2466 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
2467 produce IPv6 wildcard addresses. Previously they would produce
2468 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
2469 of bug 16069; bugfix on 0.2.4.7-alpha.
2470 - When parsing torrc ExitPolicies, we now issue an info-level
2471 message when expanding an "accept/reject *" line to include both
2472 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
2473 - When parsing torrc ExitPolicies, we now warn for a number of cases
2474 where the user's intent is likely to differ from Tor's actual
2475 behavior. These include: using an IPv4 address with an accept6 or
2476 reject6 line; using "private" on an accept6 or reject6 line; and
2477 including any ExitPolicy lines after accept *:* or reject *:*.
2478 Related to ticket 16069.
2480 o Minor bugfixes (command-line interface):
2481 - When "--quiet" is provided along with "--validate-config", do not
2482 write anything to stdout on success. Fixes bug 14994; bugfix
2484 - When complaining about bad arguments to "--dump-config", use
2486 - Print usage information for --dump-config when it is used without
2487 an argument. Also, fix the error message to use different wording
2488 and add newline at the end. Fixes bug 15541; bugfix
2491 o Minor bugfixes (compilation):
2492 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
2493 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
2494 - Repair compilation with the most recent (unreleased, alpha)
2495 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
2497 o Minor bugfixes (compilation, also in 0.2.6.9):
2498 - Build with --enable-systemd correctly when libsystemd is
2499 installed, but systemd is not. Fixes bug 16164; bugfix on
2500 0.2.6.3-alpha. Patch from Peter Palfrader.
2502 o Minor bugfixes (configuration, unit tests):
2503 - Only add the default fallback directories when the DirAuthorities,
2504 AlternateDirAuthority, and FallbackDir directory config options
2505 are set to their defaults. The default fallback directory list is
2506 currently empty, this fix will only change tor's behavior when it
2507 has default fallback directories. Includes unit tests for
2508 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
2509 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
2511 o Minor bugfixes (controller):
2512 - Add the descriptor ID in each HS_DESC control event. It was
2513 missing, but specified in control-spec.txt. Fixes bug 15881;
2514 bugfix on 0.2.5.2-alpha.
2516 o Minor bugfixes (correctness):
2517 - For correctness, avoid modifying a constant string in
2518 handle_control_postdescriptor. Fixes bug 15546; bugfix
2520 - Remove side-effects from tor_assert() calls. This was harmless,
2521 because we never disable assertions, but it is bad style and
2522 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
2524 - When calling channel_free_list(), avoid calling smartlist_remove()
2525 while inside a FOREACH loop. This partially reverts commit
2526 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
2527 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
2529 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
2530 - Check for failures from crypto_early_init, and refuse to continue.
2531 A previous typo meant that we could keep going with an
2532 uninitialized crypto library, and would have OpenSSL initialize
2533 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
2534 when implementing ticket 4900. Patch by "teor".
2536 o Minor bugfixes (hidden service):
2537 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2538 a client authorized hidden service. Fixes bug 15823; bugfix
2540 - Remove an extraneous newline character from the end of hidden
2541 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
2543 o Minor bugfixes (Linux seccomp2 sandbox):
2544 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
2545 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
2546 - Allow bridge authorities to run correctly under the seccomp2
2547 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
2548 - Add the "hidserv-stats" filename to our sandbox filter for the
2549 HiddenServiceStatistics option to work properly. Fixes bug 17354;
2550 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
2552 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
2553 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
2554 these when eventfd2() support is missing. Fixes bug 16363; bugfix
2555 on 0.2.6.3-alpha. Patch from "teor".
2557 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
2558 - Allow systemd connections to work with the Linux seccomp2 sandbox
2559 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
2561 - Fix sandboxing to work when running as a relay, by allowing the
2562 renaming of secret_id_key, and allowing the eventfd2 and futex
2563 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
2566 o Minor bugfixes (logging):
2567 - When building Tor under Clang, do not include an extra set of
2568 parentheses in log messages that include function names. Fixes bug
2569 15269; bugfix on every released version of Tor when compiled with
2570 recent enough Clang.
2572 o Minor bugfixes (network):
2573 - When attempting to use fallback technique for network interface
2574 lookup, disregard loopback and multicast addresses since they are
2575 unsuitable for public communications.
2577 o Minor bugfixes (open file limit):
2578 - Fix set_max_file_descriptors() to set by default the max open file
2579 limit to the current limit when setrlimit() fails. Fixes bug
2580 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
2582 o Minor bugfixes (portability):
2583 - Check correctly for Windows socket errors in the workqueue
2584 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
2585 - Try harder to normalize the exit status of the Tor process to the
2586 standard-provided range. Fixes bug 16975; bugfix on every version
2588 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
2589 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
2591 o Minor bugfixes (relay):
2592 - Ensure that worker threads actually exit when a fatal error or
2593 shutdown is indicated. This fix doesn't currently affect the
2594 behavior of Tor, because Tor workers never indicates fatal error
2595 or shutdown except in the unit tests. Fixes bug 16868; bugfix
2597 - Fix a rarely-encountered memory leak when failing to initialize
2598 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
2600 - Unblock threads before releasing the work queue mutex to ensure
2601 predictable scheduling behavior. Fixes bug 16644; bugfix
2604 o Minor bugfixes (security, exit policies):
2605 - ExitPolicyRejectPrivate now also rejects the relay's published
2606 IPv6 address (if any), and any publicly routable IPv4 or IPv6
2607 addresses on any local interfaces. ticket 17027. Patch by "teor".
2608 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
2610 o Minor bugfixes (statistics):
2611 - Disregard the ConnDirectionStatistics torrc options when Tor is
2612 not a relay since in that mode of operation no sensible data is
2613 being collected and because Tor might run into measurement hiccups
2614 when running as a client for some time, then becoming a relay.
2615 Fixes bug 15604; bugfix on 0.2.2.35.
2617 o Minor bugfixes (systemd):
2618 - Tor's systemd unit file no longer contains extraneous spaces.
2619 These spaces would sometimes confuse tools like deb-systemd-
2620 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
2622 o Minor bugfixes (test networks):
2623 - When self-testing reachability, use ExtendAllowPrivateAddresses to
2624 determine if local/private addresses imply reachability. The
2625 previous fix used TestingTorNetwork, which implies
2626 ExtendAllowPrivateAddresses, but this excluded rare configurations
2627 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
2628 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
2629 issue discovered by CJ Ess.
2631 o Minor bugfixes (tests, also in 0.2.6.9):
2632 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
2633 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
2635 o Code simplification and refactoring:
2636 - Change the function that's called when we need to retry all
2637 downloads so that it only reschedules the downloads to happen
2638 immediately, rather than launching them all at once itself. This
2639 further simplifies Tor's callgraph.
2640 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
2641 to ensure they remain consistent and visible everywhere.
2642 - Move some format-parsing functions out of crypto.c and
2643 crypto_curve25519.c into crypto_format.c and/or util_format.c.
2644 - Move the client-only parts of init_keys() into a separate
2645 function. Closes ticket 16763.
2646 - Move the hacky fallback code out of get_interface_address6() into
2647 separate function and get it covered with unit-tests. Resolves
2649 - Refactor hidden service client-side cache lookup to intelligently
2650 report its various failure cases, and disentangle failure cases
2651 involving a lack of introduction points. Closes ticket 14391.
2652 - Remove some vestigial workarounds for the MSVC6 compiler. We
2653 haven't supported that in ages.
2654 - Remove the unused "nulterminate" argument from buf_pullup().
2655 - Simplify the microdesc_free() implementation so that it no longer
2656 appears (to code analysis tools) to potentially invoke a huge
2657 suite of other microdesc functions.
2658 - Simply the control graph further by deferring the inner body of
2659 directory_all_unreachable() into a callback. Closes ticket 16762.
2660 - The link authentication code has been refactored for better
2661 testability and reliability. It now uses code generated with the
2662 "trunnel" binary encoding generator, to reduce the risk of bugs
2663 due to programmer error. Done as part of ticket 12498.
2664 - Treat the loss of an owning controller as equivalent to a SIGTERM
2665 signal. This removes a tiny amount of duplicated code, and
2666 simplifies our callgraph. Closes ticket 16788.
2667 - Use our own Base64 encoder instead of OpenSSL's, to allow more
2668 control over the output. Part of ticket 15652.
2669 - When generating an event to send to the controller, we no longer
2670 put the event over the network immediately. Instead, we queue
2671 these events, and use a Libevent callback to deliver them. This
2672 change simplifies Tor's callgraph by reducing the number of
2673 functions from which all other Tor functions are reachable. Closes
2675 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
2676 that try to scan or compile every file on Unix won't decide that
2680 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
2681 - Improve the descriptions of statistics-related torrc options in
2682 the manpage to describe rationale and possible uses cases. Fixes
2684 - Improve the layout and formatting of ./configure --help messages.
2685 Closes ticket 15024. Patch from "cypherpunks".
2686 - Include a specific and (hopefully) accurate documentation of the
2687 torrc file's meta-format in doc/torrc_format.txt. This is mainly
2688 of interest to people writing programs to parse or generate torrc
2689 files. This document is not a commitment to long-term
2690 compatibility; some aspects of the current format are a bit
2691 ridiculous. Closes ticket 2325.
2692 - Include the TUNING document in our source tarball. It is referred
2693 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
2695 - Note that HiddenServicePorts can take a unix domain socket. Closes
2697 - Recommend a 40 GB example AccountingMax in torrc.sample rather
2698 than a 4 GB max. Closes ticket 16742.
2699 - Standardize on the term "server descriptor" in the manual page.
2700 Previously, we had used "router descriptor", "server descriptor",
2701 and "relay descriptor" interchangeably. Part of ticket 14987.
2702 - Advise users on how to configure separate IPv4 and IPv6 exit
2703 policies in the manpage and sample torrcs. Related to ticket 16069.
2704 - Fix an error in the manual page and comments for
2705 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
2706 required "ORPort connectivity". While this is true, it is in no
2707 way unique to the HSDir flag. Of all the flags, only HSDirs need a
2708 DirPort configured in order for the authorities to assign that
2709 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
2711 - Fix the usage message of tor-resolve(1) so that it no longer lists
2712 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
2715 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
2716 and always use the internal Base64 decoder. The internal decoder
2717 has been part of tor since 0.2.0.10-alpha, and no one should
2718 be using the OpenSSL one. Part of ticket 15652.
2719 - Remove the 'tor_strclear()' function; use memwipe() instead.
2720 Closes ticket 14922.
2721 - Remove the code that would try to aggressively flush controller
2722 connections while writing to them. This code was introduced in
2723 0.1.2.7-alpha, in order to keep output buffers from exceeding
2724 their limits. But there is no longer a maximum output buffer size,
2725 and flushing data in this way caused some undesirable recursions
2726 in our call graph. Closes ticket 16480.
2727 - The internal pure-C tor-fw-helper tool is now removed from the Tor
2728 distribution, in favor of the pure-Go clone available from
2729 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
2730 used by the C tor-fw-helper are not, in our opinion, very
2731 confidence- inspiring in their secure-programming techniques.
2732 Closes ticket 13338.
2735 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
2736 fingerprinting we now recommend pluggable transports; for forward-
2737 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
2738 - Remove the HidServDirectoryV2 option. Now all relays offer to
2739 store hidden service descriptors. Related to 16543.
2740 - Remove the VoteOnHidServDirectoriesV2 option, since all
2741 authorities have long set it to 1. Closes ticket 16543.
2742 - Remove the undocumented "--digests" command-line option. It
2743 complicated our build process, caused subtle build issues on
2744 multiple platforms, and is now redundant since we started
2745 including git version identifiers. Closes ticket 14742.
2746 - Tor no longer contains checks for ancient directory cache versions
2747 that didn't know about microdescriptors.
2748 - Tor no longer contains workarounds for stat files generated by
2749 super-old versions of Tor that didn't choose guards sensibly.
2752 - The test-network.sh script now supports performance testing.
2753 Requires corresponding chutney performance testing changes. Patch
2754 by "teor". Closes ticket 14175.
2755 - Add a new set of callgraph analysis scripts that use clang to
2756 produce a list of which Tor functions are reachable from which
2757 other Tor functions. We're planning to use these to help simplify
2758 our code structure by identifying illogical dependencies.
2759 - Add new 'test-full' and 'test-full-online' targets to run all
2760 tests, including integration tests with stem and chutney.
2761 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
2762 by-side in the same parent directory. Closes ticket 16903. Patch
2764 - Document use of coverity, clang static analyzer, and clang dynamic
2765 undefined behavior and address sanitizers in doc/HACKING. Include
2766 detailed usage instructions in the blacklist. Patch by "teor".
2767 Closes ticket 15817.
2768 - Make "bridges+hs" the default test network. This tests almost all
2769 tor functionality during make test-network, while allowing tests
2770 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
2771 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
2772 (chutney). Patches by "teor".
2773 - Make the test-workqueue test work on Windows by initializing the
2774 network before we begin.
2775 - New make target (make test-network-all) to run multiple applicable
2776 chutney test cases. Patch from Teor; closes 16953.
2777 - Now that OpenSSL has its own scrypt implementation, add an unit
2778 test that checks for interoperability between libscrypt_scrypt()
2779 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
2780 and rely on EVP_PBE_scrypt() whenever possible. Resolves
2782 - The link authentication protocol code now has extensive tests.
2783 - The relay descriptor signature testing code now has
2785 - The test_workqueue program now runs faster, and is enabled by
2786 default as a part of "make check".
2787 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
2788 functions in dns.c. Implements a portion of ticket 16831.
2789 - Use environment variables rather than autoconf substitutions to
2790 send variables from the build system to the test scripts. This
2791 change should be easier to maintain, and cause 'make distcheck' to
2792 work better than before. Fixes bug 17148.
2793 - When building Tor with testing coverage enabled, run Chutney tests
2794 (if any) using the 'tor-cov' coverage binary.
2795 - When running test-network or test-stem, check for the absence of
2796 stem/chutney before doing any build operations.
2797 - Add a test to verify that the compiler does not eliminate our
2798 memwipe() implementation. Closes ticket 15377.
2799 - Add make rule `check-changes` to verify the format of changes
2800 files. Closes ticket 15180.
2801 - Add unit tests for control_event_is_interesting(). Add a compile-
2802 time check that the number of events doesn't exceed the capacity
2803 of control_event_t.event_mask. Closes ticket 15431, checks for
2804 bugs similar to 13085. Patch by "teor".
2805 - Command-line argument tests moved to Stem. Resolves ticket 14806.
2806 - Integrate the ntor, backtrace, and zero-length keys tests into the
2807 automake test suite. Closes ticket 15344.
2808 - Remove assertions during builds to determine Tor's test coverage.
2809 We don't want to trigger these even in assertions, so including
2810 them artificially makes our branch coverage look worse than it is.
2811 This patch provides the new test-stem-full and coverage-html-full
2812 configure options. Implements ticket 15400.
2813 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
2814 explicitly manage consensus flags in testing networks. Patch by
2815 "robgjansen", modified by "teor". Implements part of ticket 14882.
2816 - Check for matching value in server response in ntor_ref.py. Fixes
2817 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
2819 - Set the severity correctly when testing
2820 get_interface_addresses_ifaddrs() and
2821 get_interface_addresses_win32(), so that the tests fail gracefully
2822 instead of triggering an assertion. Fixes bug 15759; bugfix on
2823 0.2.6.3-alpha. Reported by Nicolas Derive.
2825 Changes in version 0.2.6.10 - 2015-07-12
2826 Tor version 0.2.6.10 fixes some significant stability and hidden
2827 service client bugs, bulletproofs the cryptography init process, and
2828 fixes a bug when using the sandbox code with some older versions of
2829 Linux. Everyone running an older version, especially an older version
2830 of 0.2.6, should upgrade.
2832 o Major bugfixes (hidden service clients, stability):
2833 - Stop refusing to store updated hidden service descriptors on a
2834 client. This reverts commit 9407040c59218 (which indeed fixed bug
2835 14219, but introduced a major hidden service reachability
2836 regression detailed in bug 16381). This is a temporary fix since
2837 we can live with the minor issue in bug 14219 (it just results in
2838 some load on the network) but the regression of 16381 is too much
2839 of a setback. First-round fix for bug 16381; bugfix
2842 o Major bugfixes (stability):
2843 - Stop crashing with an assertion failure when parsing certain kinds
2844 of malformed or truncated microdescriptors. Fixes bug 16400;
2845 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
2846 by "cypherpunks_backup".
2847 - Stop random client-side assertion failures that could occur when
2848 connecting to a busy hidden service, or connecting to a hidden
2849 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
2852 o Minor features (geoip):
2853 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
2854 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
2856 o Minor bugfixes (crypto error-handling):
2857 - Check for failures from crypto_early_init, and refuse to continue.
2858 A previous typo meant that we could keep going with an
2859 uninitialized crypto library, and would have OpenSSL initialize
2860 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
2861 when implementing ticket 4900. Patch by "teor".
2863 o Minor bugfixes (Linux seccomp2 sandbox):
2864 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
2865 these when eventfd2() support is missing. Fixes bug 16363; bugfix
2866 on 0.2.6.3-alpha. Patch from "teor".
2869 Changes in version 0.2.6.9 - 2015-06-11
2870 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
2871 requirements for receiving an HSDir flag, and addresses some other small
2872 bugs in the systemd and sandbox code. Clients using circuit isolation
2873 should upgrade; all directory authorities should upgrade.
2875 o Major bugfixes (client-side privacy):
2876 - Properly separate out each SOCKSPort when applying stream
2877 isolation. The error occurred because each port's session group was
2878 being overwritten by a default value when the listener connection
2879 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
2882 o Minor feature (directory authorities, security):
2883 - The HSDir flag given by authorities now requires the Stable flag.
2884 For the current network, this results in going from 2887 to 2806
2885 HSDirs. Also, it makes it harder for an attacker to launch a sybil
2886 attack by raising the effort for a relay to become Stable which
2887 takes at the very least 7 days to do so and by keeping the 96
2888 hours uptime requirement for HSDir. Implements ticket 8243.
2890 o Minor bugfixes (compilation):
2891 - Build with --enable-systemd correctly when libsystemd is
2892 installed, but systemd is not. Fixes bug 16164; bugfix on
2893 0.2.6.3-alpha. Patch from Peter Palfrader.
2895 o Minor bugfixes (Linux seccomp2 sandbox):
2896 - Fix sandboxing to work when running as a relaymby renaming of
2897 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
2898 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
2899 - Allow systemd connections to work with the Linux seccomp2 sandbox
2900 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
2903 o Minor bugfixes (tests):
2904 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
2905 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
2908 Changes in version 0.2.6.8 - 2015-05-21
2909 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
2910 fixes an authority-side bug in assigning the HSDir flag. All directory
2911 authorities should upgrade.
2913 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
2914 - Revert commit that made directory authorities assign the HSDir
2915 flag to relay without a DirPort; this was bad because such relays
2916 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
2919 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
2920 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2921 a client authorized hidden service. Fixes bug 15823; bugfix
2924 o Minor features (geoip):
2925 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
2926 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
2930 Changes in version 0.2.6.7 - 2015-04-06
2931 Tor 0.2.6.7 fixes two security issues that could be used by an
2932 attacker to crash hidden services, or crash clients visiting hidden
2933 services. Hidden services should upgrade as soon as possible; clients
2934 should upgrade whenever packages become available.
2936 This release also contains two simple improvements to make hidden
2937 services a bit less vulnerable to denial-of-service attacks.
2939 o Major bugfixes (security, hidden service):
2940 - Fix an issue that would allow a malicious client to trigger an
2941 assertion failure and halt a hidden service. Fixes bug 15600;
2942 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
2943 - Fix a bug that could cause a client to crash with an assertion
2944 failure when parsing a malformed hidden service descriptor. Fixes
2945 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
2947 o Minor features (DoS-resistance, hidden service):
2948 - Introduction points no longer allow multiple INTRODUCE1 cells to
2949 arrive on the same circuit. This should make it more expensive for
2950 attackers to overwhelm hidden services with introductions.
2951 Resolves ticket 15515.
2952 - Decrease the amount of reattempts that a hidden service performs
2953 when its rendezvous circuits fail. This reduces the computational
2954 cost for running a hidden service under heavy load. Resolves
2958 Changes in version 0.2.5.12 - 2015-04-06
2959 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
2960 could be used by an attacker to crash hidden services, or crash clients
2961 visiting hidden services. Hidden services should upgrade as soon as
2962 possible; clients should upgrade whenever packages become available.
2964 This release also backports a simple improvement to make hidden
2965 services a bit less vulnerable to denial-of-service attacks.
2967 o Major bugfixes (security, hidden service):
2968 - Fix an issue that would allow a malicious client to trigger an
2969 assertion failure and halt a hidden service. Fixes bug 15600;
2970 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
2971 - Fix a bug that could cause a client to crash with an assertion
2972 failure when parsing a malformed hidden service descriptor. Fixes
2973 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
2975 o Minor features (DoS-resistance, hidden service):
2976 - Introduction points no longer allow multiple INTRODUCE1 cells to
2977 arrive on the same circuit. This should make it more expensive for
2978 attackers to overwhelm hidden services with introductions.
2979 Resolves ticket 15515.
2982 Changes in version 0.2.4.27 - 2015-04-06
2983 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
2984 could be used by an attacker to crash hidden services, or crash clients
2985 visiting hidden services. Hidden services should upgrade as soon as
2986 possible; clients should upgrade whenever packages become available.
2988 This release also backports a simple improvement to make hidden
2989 services a bit less vulnerable to denial-of-service attacks.
2991 o Major bugfixes (security, hidden service):
2992 - Fix an issue that would allow a malicious client to trigger an
2993 assertion failure and halt a hidden service. Fixes bug 15600;
2994 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
2995 - Fix a bug that could cause a client to crash with an assertion
2996 failure when parsing a malformed hidden service descriptor. Fixes
2997 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
2999 o Minor features (DoS-resistance, hidden service):
3000 - Introduction points no longer allow multiple INTRODUCE1 cells to
3001 arrive on the same circuit. This should make it more expensive for
3002 attackers to overwhelm hidden services with introductions.
3003 Resolves ticket 15515.
3006 Changes in version 0.2.6.6 - 2015-03-24
3007 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
3009 It adds numerous safety, security, correctness, and performance
3010 improvements. Client programs can be configured to use more kinds of
3011 sockets, AutomapHosts works better, the multithreading backend is
3012 improved, cell transmission is refactored, test coverage is much
3013 higher, more denial-of-service attacks are handled, guard selection is
3014 improved to handle long-term guards better, pluggable transports
3015 should work a bit better, and some annoying hidden service performance
3016 bugs should be addressed.
3018 o New compiler and system requirements:
3019 - Tor 0.2.6.x requires that your compiler support more of the C99
3020 language standard than before. The 'configure' script now detects
3021 whether your compiler supports C99 mid-block declarations and
3022 designated initializers. If it does not, Tor will not compile.
3024 We may revisit this requirement if it turns out that a significant
3025 number of people need to build Tor with compilers that don't
3026 bother implementing a 15-year-old standard. Closes ticket 13233.
3027 - Tor no longer supports systems without threading support. When we
3028 began working on Tor, there were several systems that didn't have
3029 threads, or where the thread support wasn't able to run the
3030 threads of a single process on multiple CPUs. That no longer
3031 holds: every system where Tor needs to run well now has threading
3032 support. Resolves ticket 12439.
3034 o Deprecated versions and removed support:
3035 - Tor relays older than 0.2.4.18-rc are no longer allowed to
3036 advertise themselves on the network. Closes ticket 13555.
3037 - Tor clients no longer support connecting to hidden services
3038 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
3039 option has been removed. (There shouldn't be any hidden services
3040 running these versions on the network.) Closes ticket 7803.
3042 o Directory authority changes:
3043 - The directory authority Faravahar has a new IP address. This
3044 closes ticket 14487.
3045 - Remove turtles as a directory authority.
3046 - Add longclaw as a new (v3) directory authority. This implements
3047 ticket 13296. This keeps the directory authority count at 9.
3049 o Major features (bridges):
3050 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
3051 transports if they are configured via the "TOR_PT_PROXY"
3052 environment variable. Implements proposal 232. Resolves
3055 o Major features (changed defaults):
3056 - Prevent relay operators from unintentionally running exits: When a
3057 relay is configured as an exit node, we now warn the user unless
3058 the "ExitRelay" option is set to 1. We warn even more loudly if
3059 the relay is configured with the default exit policy, since this
3060 can indicate accidental misconfiguration. Setting "ExitRelay 0"
3061 stops Tor from running as an exit relay. Closes ticket 10067.
3063 o Major features (client performance, hidden services):
3064 - Allow clients to use optimistic data when connecting to a hidden
3065 service, which should remove a round-trip from hidden service
3066 initialization. See proposal 181 for details. Implements
3069 o Major features (directory system):
3070 - Upon receiving an unparseable directory object, if its digest
3071 matches what we expected, then don't try to download it again.
3072 Previously, when we got a descriptor we didn't like, we would keep
3073 trying to download it over and over. Closes ticket 11243.
3074 - When downloading server- or microdescriptors from a directory
3075 server, we no longer launch multiple simultaneous requests to the
3076 same server. This reduces load on the directory servers,
3077 especially when directory guards are in use. Closes ticket 9969.
3078 - When downloading server- or microdescriptors over a tunneled
3079 connection, do not limit the length of our requests to what the
3080 Squid proxy is willing to handle. Part of ticket 9969.
3081 - Authorities can now vote on the correct digests and latest
3082 versions for different software packages. This allows packages
3083 that include Tor to use the Tor authority system as a way to get
3084 notified of updates and their correct digests. Implements proposal
3085 227. Closes ticket 10395.
3087 o Major features (guards):
3088 - Introduce the Guardfraction feature to improves load balancing on
3089 guard nodes. Specifically, it aims to reduce the traffic gap that
3090 guard nodes experience when they first get the Guard flag. This is
3091 a required step if we want to increase the guard lifetime to 9
3092 months or greater. Closes ticket 9321.
3094 o Major features (hidden services):
3095 - Make HS port scanning more difficult by immediately closing the
3096 circuit when a user attempts to connect to a nonexistent port.
3097 Closes ticket 13667.
3098 - Add a HiddenServiceStatistics option that allows Tor relays to
3099 gather and publish statistics about the overall size and volume of
3100 hidden service usage. Specifically, when this option is turned on,
3101 an HSDir will publish an approximate number of hidden services
3102 that have published descriptors to it the past 24 hours. Also, if
3103 a relay has acted as a hidden service rendezvous point, it will
3104 publish the approximate amount of rendezvous cells it has relayed
3105 the past 24 hours. The statistics themselves are obfuscated so
3106 that the exact values cannot be derived. For more details see
3107 proposal 238, "Better hidden service stats from Tor relays". This
3108 feature is currently disabled by default. Implements feature 13192.
3110 o Major features (performance):
3111 - Make the CPU worker implementation more efficient by avoiding the
3112 kernel and lengthening pipelines. The original implementation used
3113 sockets to transfer data from the main thread to the workers, and
3114 didn't allow any thread to be assigned more than a single piece of
3115 work at once. The new implementation avoids communications
3116 overhead by making requests in shared memory, avoiding kernel IO
3117 where possible, and keeping more requests in flight at once.
3118 Implements ticket 9682.
3120 o Major features (relay):
3121 - Raise the minimum acceptable configured bandwidth rate for bridges
3122 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
3123 20 KiB/sec.) Closes ticket 13822.
3124 - Complete revision of the code that relays use to decide which cell
3125 to send next. Formerly, we selected the best circuit to write on
3126 each channel, but we didn't select among channels in any
3127 sophisticated way. Now, we choose the best circuits globally from
3128 among those whose channels are ready to deliver traffic.
3130 This patch implements a new inter-cmux comparison API, a global
3131 high/low watermark mechanism and a global scheduler loop for
3132 transmission prioritization across all channels as well as among
3133 circuits on one channel. This schedule is currently tuned to
3134 (tolerantly) avoid making changes in network performance, but it
3135 should form the basis for major circuit performance increases in
3136 the future. Code by Andrea; tuning by Rob Jansen; implements
3139 o Major features (sample torrc):
3140 - Add a new, infrequently-changed "torrc.minimal". This file is
3141 similar to torrc.sample, but it will change as infrequently as
3142 possible, for the benefit of users whose systems prompt them for
3143 intervention whenever a default configuration file is changed.
3144 Making this change allows us to update torrc.sample to be a more
3145 generally useful "sample torrc".
3147 o Major features (security, unix domain sockets):
3148 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
3149 applications can reach Tor without having to create AF_INET or
3150 AF_INET6 sockets, meaning they can completely disable their
3151 ability to make non-Tor network connections. To create a socket of
3152 this type, use "SocksPort unix:/path/to/socket". Implements
3154 - Support mapping hidden service virtual ports to AF_UNIX sockets.
3155 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
3156 Implements ticket 11485.
3158 o Major bugfixes (client, automap):
3159 - Repair automapping with IPv6 addresses. This automapping should
3160 have worked previously, but one piece of debugging code that we
3161 inserted to detect a regression actually caused the regression to
3162 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
3163 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
3166 o Major bugfixes (crash, OSX, security):
3167 - Fix a remote denial-of-service opportunity caused by a bug in
3168 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
3171 o Major bugfixes (directory authorities):
3172 - Do not assign the HSDir flag to relays if they are not Valid, or
3173 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
3175 o Major bugfixes (directory bandwidth performance):
3176 - Don't flush the zlib buffer aggressively when compressing
3177 directory information for clients. This should save about 7% of
3178 the bandwidth currently used for compressed descriptors and
3179 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
3181 o Major bugfixes (exit node stability):
3182 - Fix an assertion failure that could occur under high DNS load.
3183 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
3184 diagnosed and fixed by "cypherpunks".
3186 o Major bugfixes (FreeBSD IPFW transparent proxy):
3187 - Fix address detection with FreeBSD transparent proxies, when
3188 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
3191 o Major bugfixes (hidden services):
3192 - When closing an introduction circuit that was opened in parallel
3193 with others, don't mark the introduction point as unreachable.
3194 Previously, the first successful connection to an introduction
3195 point would make the other introduction points get marked as
3196 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
3198 o Major bugfixes (Linux seccomp2 sandbox):
3199 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
3200 crash during attempts to call wait4. Fixes bug 15088; bugfix on
3201 0.2.5.1-alpha. Patch from "sanic".
3203 o Major bugfixes (mixed relay-client operation):
3204 - When running as a relay and client at the same time (not
3205 recommended), if we decide not to use a new guard because we want
3206 to retry older guards, only close the locally-originating circuits
3207 passing through that guard. Previously we would close all the
3208 circuits through that guard. Fixes bug 9819; bugfix on
3209 0.2.1.1-alpha. Reported by "skruffy".
3211 o Major bugfixes (pluggable transports):
3212 - Initialize the extended OR Port authentication cookie before
3213 launching pluggable transports. This prevents a race condition
3214 that occured when server-side pluggable transports would cache the
3215 authentication cookie before it has been (re)generated. Fixes bug
3216 15240; bugfix on 0.2.5.1-alpha.
3218 o Major bugfixes (relay, stability, possible security):
3219 - Fix a bug that could lead to a relay crashing with an assertion
3220 failure if a buffer of exactly the wrong layout is passed to
3221 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
3222 0.2.0.10-alpha. Patch from "cypherpunks".
3223 - Do not assert if the 'data' pointer on a buffer is advanced to the
3224 very end of the buffer; log a BUG message instead. Only assert if
3225 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
3227 o Minor features (build):
3228 - New --disable-system-torrc compile-time option to prevent Tor from
3229 looking for the system-wide torrc or torrc-defaults files.
3230 Resolves ticket 13037.
3232 o Minor features (client):
3233 - Clients are now willing to send optimistic data (before they
3234 receive a 'connected' cell) to relays of any version. (Relays
3235 without support for optimistic data are no longer supported on the
3236 Tor network.) Resolves ticket 13153.
3238 o Minor features (client):
3239 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
3240 is enabled, reject requests with IP addresses as hostnames.
3241 Resolves ticket 13315.
3243 o Minor features (controller):
3244 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
3245 write an unscheduled heartbeat message to the log. Implements
3247 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
3248 events so controllers can observe circuit isolation inputs. Closes
3250 - ControlPort now supports the unix:/path/to/socket syntax as an
3251 alternative to the ControlSocket option, for consistency with
3252 SocksPort and HiddenServicePort. Closes ticket 14451.
3253 - New "GETINFO bw-event-cache" to get information about recent
3254 bandwidth events. Closes ticket 14128. Useful for controllers to
3255 get recent bandwidth history after the fix for ticket 13988.
3256 - Messages about problems in the bootstrap process now include
3257 information about the server we were trying to connect to when we
3258 noticed the problem. Closes ticket 15006.
3260 o Minor features (Denial of service resistance):
3261 - Count the total number of bytes used storing hidden service
3262 descriptors against the value of MaxMemInQueues. If we're low on
3263 memory, and more than 20% of our memory is used holding hidden
3264 service descriptors, free them until no more than 10% of our
3265 memory holds hidden service descriptors. Free the least recently
3266 fetched descriptors first. Resolves ticket 13806.
3267 - When we have recently been under memory pressure (over 3/4 of
3268 MaxMemInQueues is allocated), then allocate smaller zlib objects
3269 for small requests. Closes ticket 11791.
3271 o Minor features (directory authorities):
3272 - Don't list relays with a bandwidth estimate of 0 in the consensus.
3273 Implements a feature proposed during discussion of bug 13000.
3274 - In tor-gencert, report an error if the user provides the same
3275 argument more than once.
3276 - If a directory authority can't find a best consensus method in the
3277 votes that it holds, it now falls back to its favorite consensus
3278 method. Previously, it fell back to method 1. Neither of these is
3279 likely to get enough signatures, but "fall back to favorite"
3280 doesn't require us to maintain support an obsolete consensus
3281 method. Implements part of proposal 215.
3283 o Minor features (geoip):
3284 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
3285 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
3288 o Minor features (guard nodes):
3289 - Reduce the time delay before saving guard status to disk from 10
3290 minutes to 30 seconds (or from one hour to 10 minutes if
3291 AvoidDiskWrites is set). Closes ticket 12485.
3293 o Minor features (heartbeat):
3294 - On relays, report how many connections we negotiated using each
3295 version of the Tor link protocols. This information will let us
3296 know if removing support for very old versions of the Tor
3297 protocols is harming the network. Closes ticket 15212.
3299 o Minor features (hidden service):
3300 - Make Sybil attacks against hidden services harder by changing the
3301 minimum time required to get the HSDir flag from 25 hours up to 96
3302 hours. Addresses ticket 14149.
3303 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
3304 services to disable the anti-scanning feature introduced in
3305 0.2.6.2-alpha. With this option not set, a connection to an
3306 unlisted port closes the circuit. With this option set, only a
3307 RELAY_DONE cell is sent. Closes ticket 14084.
3308 - When re-enabling the network, don't try to build introduction
3309 circuits until we have successfully built a circuit. This makes
3310 hidden services come up faster when the network is re-enabled.
3311 Patch from "akwizgran". Closes ticket 13447.
3312 - When we fail to retrieve a hidden service descriptor, send the
3313 controller an "HS_DESC FAILED" controller event. Implements
3315 - New HiddenServiceDirGroupReadable option to cause hidden service
3316 directories and hostname files to be created group-readable. Patch
3317 from "anon", David Stainton, and "meejah". Closes ticket 11291.
3319 o Minor features (interface):
3320 - Implement "-f -" command-line option to read torrc configuration
3321 from standard input, if you don't want to store the torrc file in
3322 the file system. Implements feature 13865.
3324 o Minor features (logging):
3325 - Add a count of unique clients to the bridge heartbeat message.
3326 Resolves ticket 6852.
3327 - Suppress "router info incompatible with extra info" message when
3328 reading extrainfo documents from cache. (This message got loud
3329 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
3331 - Elevate hidden service authorized-client message from DEBUG to
3332 INFO. Closes ticket 14015.
3333 - On Unix-like systems, you can now use named pipes as the target of
3334 the Log option, and other options that try to append to files.
3335 Closes ticket 12061. Patch from "carlo von lynX".
3336 - When opening a log file at startup, send it every log message that
3337 we generated between startup and opening it. Previously, log
3338 messages that were generated before opening the log file were only
3339 logged to stdout. Closes ticket 6938.
3340 - Add a TruncateLogFile option to overwrite logs instead of
3341 appending to them. Closes ticket 5583.
3342 - Quiet some log messages in the heartbeat and at startup. Closes
3345 o Minor features (portability, Solaris):
3346 - Threads are no longer disabled by default on Solaris; we believe
3347 that the versions of Solaris with broken threading support are all
3348 obsolete by now. Resolves ticket 9495.
3350 o Minor features (relay):
3351 - Re-check our address after we detect a changed IP address from
3352 getsockname(). This ensures that the controller command "GETINFO
3353 address" will report the correct value. Resolves ticket 11582.
3355 - A new AccountingRule option lets Relays set whether they'd like
3356 AccountingMax to be applied separately to inbound and outbound
3357 traffic, or applied to the sum of inbound and outbound traffic.
3358 Resolves ticket 961. Patch by "chobe".
3359 - When identity keypair is generated for first time, log a
3360 congratulatory message that links to the new relay lifecycle
3361 document. Implements feature 10427.
3363 o Minor features (security, memory wiping):
3364 - Ensure we securely wipe keys from memory after
3365 crypto_digest_get_digest and init_curve25519_keypair_from_file
3366 have finished using them. Resolves ticket 13477.
3368 o Minor features (security, out-of-memory handling):
3369 - When handling an out-of-memory condition, allocate less memory for
3370 temporary data structures. Fixes issue 10115.
3371 - When handling an out-of-memory condition, consider more types of
3372 buffers, including those on directory connections, and zlib
3373 buffers. Resolves ticket 11792.
3375 o Minor features (stability):
3376 - Add assertions in our hash-table iteration code to check for
3377 corrupted values that could cause infinite loops. Closes
3380 o Minor features (systemd):
3381 - Various improvements and modernizations in systemd hardening
3382 support. Closes ticket 13805. Patch from Craig Andrews.
3383 - Where supported, when running with systemd, report successful
3384 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
3385 - When running with systemd, support systemd watchdog messages. Part
3386 of ticket 11016. Patch by Michael Scherer.
3388 o Minor features (testing networks):
3389 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
3390 the "Exit" flag regardless of their uptime, bandwidth, or exit
3391 policy. TestingTorNetwork must be set for this option to have any
3392 effect. Previously, authorities would take up to 35 minutes to
3393 give nodes the Exit flag in a test network. Partially implements
3395 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
3396 and the default on a testing network to 2 minutes. Drop the
3397 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
3398 keep the default on a testing network at 30 seconds. This reduces
3399 HS bootstrap time to around 25 seconds. Also, change the default
3400 time in test-network.sh to match. Closes ticket 13401. Patch
3402 - Create TestingDirAuthVoteHSDir to correspond to
3403 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
3404 HSDir flag for the listed relays regardless of uptime or ORPort
3405 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
3406 Partial implementation for ticket 14067. Patch by "teor".
3408 o Minor features (tor2web mode):
3409 - Introduce the config option Tor2webRendezvousPoints, which allows
3410 clients in Tor2webMode to select a specific Rendezvous Point to be
3411 used in HS circuits. This might allow better performance for
3412 Tor2Web nodes. Implements ticket 12844.
3414 o Minor features (transparent proxy):
3415 - Update the transparent proxy option checks to allow for both ipfw
3416 and pf on OS X. Closes ticket 14002.
3417 - Use the correct option when using IPv6 with transparent proxy
3418 support on Linux. Resolves 13808. Patch by Francisco Blas
3421 o Minor features (validation):
3422 - Check all date/time values passed to tor_timegm and
3423 parse_rfc1123_time for validity, taking leap years into account.
3424 Improves HTTP header validation. Implemented with bug 13476.
3425 - In correct_tm(), limit the range of values returned by system
3426 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
3427 This means we don't have to deal with negative or too large dates,
3428 even if a clock is wrong. Otherwise we might fail to read a file
3429 written by us which includes such a date. Fixes bug 13476.
3430 - Stop allowing invalid address patterns like "*/24" that contain
3431 both a wildcard address and a bit prefix length. This affects all
3432 our address-range parsing code. Fixes bug 7484; bugfix
3435 o Minor bugfixes (bridge clients):
3436 - When configured to use a bridge without an identity digest (not
3437 recommended), avoid launching an extra channel to it when
3438 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
3440 o Minor bugfixes (bridges):
3441 - When DisableNetwork is set, do not launch pluggable transport
3442 plugins, and if any are running, terminate them. Fixes bug 13213;
3443 bugfix on 0.2.3.6-alpha.
3445 o Minor bugfixes (C correctness):
3446 - Fix several instances of possible integer overflow/underflow/NaN.
3447 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
3449 - In circuit_build_times_calculate_timeout() in circuitstats.c,
3450 avoid dividing by zero in the pareto calculations. This traps
3451 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
3453 - Fix an integer overflow in format_time_interval(). Fixes bug
3454 13393; bugfix on 0.2.0.10-alpha.
3455 - Set the correct day of year value when the system's localtime(_r)
3456 or gmtime(_r) functions fail to set struct tm. Not externally
3457 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
3458 - Avoid unlikely signed integer overflow in tor_timegm on systems
3459 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
3461 o Minor bugfixes (certificate handling):
3462 - If an authority operator accidentally makes a signing certificate
3463 with a future publication time, do not discard its real signing
3464 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
3465 - Remove any old authority certificates that have been superseded
3466 for at least two days. Previously, we would keep superseded
3467 certificates until they expired, if they were published close in
3468 time to the certificate that superseded them. Fixes bug 11454;
3469 bugfix on 0.2.1.8-alpha.
3471 o Minor bugfixes (client):
3472 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
3473 BadExit flag are not considered worthy candidates. Fixes bug
3474 13066; bugfix on 0.1.2.3-alpha.
3475 - Use the consensus schedule for downloading consensuses, and not
3476 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
3477 - Handle unsupported or malformed SOCKS5 requests properly by
3478 responding with the appropriate error message before closing the
3479 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
3481 o Minor bugfixes (client, automapping):
3482 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
3483 no value follows the option. Fixes bug 14142; bugfix on
3484 0.2.4.7-alpha. Patch by "teor".
3485 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
3486 14195; bugfix on 0.1.0.1-rc.
3487 - Prevent changes to other options from removing the wildcard value
3488 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
3490 - Allow MapAddress and AutomapHostsOnResolve to work together when
3491 an address is mapped into another address type (like .onion) that
3492 must be automapped at resolve time. Fixes bug 7555; bugfix
3495 o Minor bugfixes (client, bridges):
3496 - When we are using bridges and we had a network connectivity
3497 problem, only retry connecting to our currently configured
3498 bridges, not all bridges we know about and remember using. Fixes
3499 bug 14216; bugfix on 0.2.2.17-alpha.
3501 o Minor bugfixes (client, DNS):
3502 - Report the correct cached DNS expiration times on SOCKS port or in
3503 DNS replies. Previously, we would report everything as "never
3504 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
3505 - Avoid a small memory leak when we find a cached answer for a
3506 reverse DNS lookup in a client-side DNS cache. (Remember, client-
3507 side DNS caching is off by default, and is not recommended.) Fixes
3508 bug 14259; bugfix on 0.2.0.1-alpha.
3510 o Minor bugfixes (client, IPv6):
3511 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
3512 flag is not set; and not because the NoIPv4Traffic flag was set.
3513 Previously we'd looked at the NoIPv4Traffic flag for both types of
3514 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
3516 o Minor bugfixes (client, microdescriptors):
3517 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
3518 computing which microdescriptors to download. This keeps us from
3519 erroneous download behavior if two microdescriptor digests ever
3520 have the same first 160 bits. Fixes part of bug 13399; bugfix
3522 - Reset a router's status if its microdescriptor digest changes,
3523 even if the first 160 bits remain the same. Fixes part of bug
3524 13399; bugfix on 0.2.3.1-alpha.
3526 o Minor bugfixes (client, torrc):
3527 - Stop modifying the value of our DirReqStatistics torrc option just
3528 because we're not a bridge or relay. This bug was causing Tor
3529 Browser users to write "DirReqStatistics 0" in their torrc files
3530 as if they had chosen to change the config. Fixes bug 4244; bugfix
3532 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
3533 that our options have changed every time we SIGHUP. Fixes bug
3534 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
3536 o Minor bugfixes (compilation):
3537 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
3539 - Silence clang warnings under --enable-expensive-hardening,
3540 including implicit truncation of 64 bit values to 32 bit, const
3541 char assignment to self, tautological compare, and additional
3542 parentheses around equality tests. Fixes bug 13577; bugfix
3544 - Fix a clang warning about checking whether an address in the
3545 middle of a structure is NULL. Fixes bug 14001; bugfix
3547 - The address of an array in the middle of a structure will always
3548 be non-NULL. clang recognises this and complains. Disable the
3549 tautologous and redundant check to silence this warning. Fixes bug
3550 14001; bugfix on 0.2.1.2-alpha.
3551 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
3552 Addresses ticket 14188.
3553 - Build without warnings with the stock OpenSSL srtp.h header, which
3554 has a duplicate declaration of SSL_get_selected_srtp_profile().
3555 Fixes bug 14220; this is OpenSSL's bug, not ours.
3556 - Do not compile any code related to Tor2Web mode when Tor2Web mode
3557 is not enabled at compile time. Previously, this code was included
3558 in a disabled state. See discussion on ticket 12844.
3559 - Allow our configure script to build correctly with autoconf 2.62
3560 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
3561 - Improve the error message from ./configure to make it clear that
3562 when asciidoc has not been found, the user will have to either add
3563 --disable-asciidoc argument or install asciidoc. Resolves
3566 o Minor bugfixes (controller):
3567 - Report "down" in response to the "GETINFO entry-guards" command
3568 when relays are down with an unreachable_since value. Previously,
3569 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
3570 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
3571 14116; bugfix on 0.2.2.9-alpha.
3573 o Minor bugfixes (controller):
3574 - Return an error when the second or later arguments of the
3575 "setevents" controller command are invalid events. Previously we
3576 would return success while silently skipping invalid events. Fixes
3577 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
3579 o Minor bugfixes (directory authority):
3580 - Allow directory authorities to fetch more data from one another if
3581 they find themselves missing lots of votes. Previously, they had
3582 been bumping against the 10 MB queued data limit. Fixes bug 14261;
3583 bugfix on 0.1.2.5-alpha.
3584 - Do not attempt to download extrainfo documents which we will be
3585 unable to validate with a matching server descriptor. Fixes bug
3586 13762; bugfix on 0.2.0.1-alpha.
3587 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
3588 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
3589 - Enlarge the buffer to read bwauth generated files to avoid an
3590 issue when parsing the file in dirserv_read_measured_bandwidths().
3591 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
3592 - When running as a v3 directory authority, advertise that you serve
3593 extra-info documents so that clients who want them can find them
3594 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3596 o Minor bugfixes (directory system):
3597 - Always believe that v3 directory authorities serve extra-info
3598 documents, whether they advertise "caches-extra-info" or not.
3599 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3600 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
3601 Previously, directories offering BRIDGE_DIRINFO and some other
3602 flag (i.e. microdescriptors or extrainfo) would be ignored when
3603 looking for bridges. Partially fixes bug 13163; bugfix
3606 o Minor bugfixes (file handling):
3607 - Stop failing when key files are zero-length. Instead, generate new
3608 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
3609 on all versions of Tor. Patch by "teor".
3610 - Stop generating a fresh .old RSA onion key file when the .old file
3611 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
3612 - Avoid overwriting .old key files with empty key files.
3613 - Skip loading zero-length extrainfo store, router store, stats,
3614 state, and key files.
3615 - Avoid crashing when trying to reload a torrc specified as a
3616 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
3619 o Minor bugfixes (hidden services):
3620 - Close the introduction circuit when we have no more usable intro
3621 points, instead of waiting for it to time out. This also ensures
3622 that no follow-up HS descriptor fetch is triggered when the
3623 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
3624 - When fetching a hidden service descriptor for a down service that
3625 was recently up, do not keep refetching until we try the same
3626 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
3627 - Correctly send a controller event when we find that a rendezvous
3628 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
3629 - Pre-check directory permissions for new hidden-services to avoid
3630 at least one case of "Bug: Acting on config options left us in a
3631 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
3632 - When fetching hidden service descriptors, we now check not only
3633 for whether we got the hidden service we had in mind, but also
3634 whether we got the particular descriptors we wanted. This prevents
3635 a class of inefficient but annoying DoS attacks by hidden service
3636 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
3639 o Minor bugfixes (Linux seccomp2 sandbox):
3640 - Make transparent proxy support work along with the seccomp2
3641 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
3642 by Francisco Blas Izquierdo Riera.
3643 - Fix a memory leak in tor-resolve when running with the sandbox
3644 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
3645 - Allow glibc fatal errors to be sent to stderr before Tor exits.
3646 Previously, glibc would try to write them to /dev/tty, and the
3647 sandbox would trap the call and make Tor exit prematurely. Fixes
3648 bug 14759; bugfix on 0.2.5.1-alpha.
3650 o Minor bugfixes (logging):
3651 - Avoid crashing when there are more log domains than entries in
3652 domain_list. Bugfix on 0.2.3.1-alpha.
3653 - Downgrade warnings about RSA signature failures to info log level.
3654 Emit a warning when an extra info document is found incompatible
3655 with a corresponding router descriptor. Fixes bug 9812; bugfix
3657 - Make connection_ap_handshake_attach_circuit() log the circuit ID
3658 correctly. Fixes bug 13701; bugfix on 0.0.6.
3660 o Minor bugfixes (networking):
3661 - Check for orconns and use connection_or_close_for_error() rather
3662 than connection_mark_for_close() directly in the getsockopt()
3663 failure case of connection_handle_write_impl(). Fixes bug 11302;
3664 bugfix on 0.2.4.4-alpha.
3666 o Minor bugfixes (parsing):
3667 - Stop accepting milliseconds (or other junk) at the end of
3668 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
3669 - Support two-number and three-number version numbers correctly, in
3670 case we change the Tor versioning system in the future. Fixes bug
3671 13661; bugfix on 0.0.8pre1.
3673 o Minor bugfixes (portability):
3674 - Fix the ioctl()-based network interface lookup code so that it
3675 will work on systems that have variable-length struct ifreq, for
3677 - Use the correct datatype in the SipHash-2-4 function to prevent
3678 compilers from assuming any sort of alignment. Fixes bug 15436;
3679 bugfix on 0.2.5.3-alpha.
3681 o Minor bugfixes (preventative security, C safety):
3682 - When reading a hexadecimal, base-32, or base-64 encoded value from
3683 a string, always overwrite the whole output buffer. This prevents
3684 some bugs where we would look at (but fortunately, not reveal)
3685 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
3687 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
3688 just the part that's used. This makes it harder for data leak bugs
3689 to occur in the event of other programming failures. Resolves
3692 o Minor bugfixes (relay):
3693 - When generating our family list, remove spaces from around the
3694 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
3695 - If our previous bandwidth estimate was 0 bytes, allow publishing a
3696 new relay descriptor immediately. Fixes bug 13000; bugfix
3699 o Minor bugfixes (shutdown):
3700 - When shutting down, always call event_del() on lingering read or
3701 write events before freeing them. Otherwise, we risk double-frees
3702 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
3705 o Minor bugfixes (small memory leaks):
3706 - Avoid leaking memory when using IPv6 virtual address mappings.
3707 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
3710 o Minor bugfixes (statistics):
3711 - Increase period over which bandwidth observations are aggregated
3712 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
3714 o Minor bugfixes (systemd support):
3715 - Run correctly under systemd with the RunAsDaemon option set. Fixes
3716 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
3717 - Inform the systemd supervisor about more changes in the Tor
3718 process status. Implements part of ticket 14141. Patch from
3721 o Minor bugfixes (testing networks):
3722 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
3723 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
3724 - Stop using the default authorities in networks which provide both
3725 AlternateDirAuthority and AlternateBridgeAuthority. Partially
3726 fixes bug 13163; bugfix on 0.2.0.13-alpha.
3728 o Minor bugfixes (testing networks, fast startup):
3729 - Allow Tor to build circuits using a consensus with no exits. If
3730 the consensus has no exits (typical of a bootstrapping test
3731 network), allow Tor to build circuits once enough descriptors have
3732 been downloaded. This assists in bootstrapping a testing Tor
3733 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
3735 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
3736 header to directory servers. This allows us to obtain consensuses
3737 promptly when the consensus interval is very short. This assists
3738 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
3739 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
3740 - Stop assuming that private addresses are local when checking
3741 reachability in a TestingTorNetwork. Instead, when testing, assume
3742 all OR connections are remote. (This is necessary due to many test
3743 scenarios running all relays on localhost.) This assists in
3744 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
3745 0.1.0.1-rc. Patch by "teor".
3746 - Avoid building exit circuits from a consensus with no exits. Now
3747 thanks to our fix for 13718, we accept a no-exit network as not
3748 wholly lost, but we need to remember not to try to build exit
3749 circuits on it. Closes ticket 13814; patch by "teor".
3750 - Stop requiring exits to have non-zero bandwithcapacity in a
3751 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
3752 ignore exit bandwidthcapacity. This assists in bootstrapping a
3753 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
3754 on 0.2.0.3-alpha. Patch by "teor".
3755 - Add "internal" to some bootstrap statuses when no exits are
3756 available. If the consensus does not contain Exits, Tor will only
3757 build internal circuits. In this case, relevant statuses will
3758 contain the word "internal" as indicated in the Tor control-
3759 spec.txt. When bootstrap completes, Tor will be ready to build
3760 internal circuits. If a future consensus contains Exits, exit
3761 circuits may become available. Fixes part of bug 13718; bugfix on
3762 0.2.4.10-alpha. Patch by "teor".
3763 - Decrease minimum consensus interval to 10 seconds when
3764 TestingTorNetwork is set, or 5 seconds for the first consensus.
3765 Fix assumptions throughout the code that assume larger intervals.
3766 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
3768 - Avoid excluding guards from path building in minimal test
3769 networks, when we're in a test network and excluding guards would
3770 exclude all relays. This typically occurs in incredibly small tor
3771 networks, and those using "TestingAuthVoteGuard *". Fixes part of
3772 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
3774 o Minor bugfixes (testing):
3775 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
3776 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
3777 - Stop spawn test failures due to a race condition between the
3778 SIGCHLD handler updating the process status, and the test reading
3779 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
3780 - Avoid passing an extra backslash when creating a temporary
3781 directory for running the unit tests on Windows. Fixes bug 12392;
3782 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
3784 o Minor bugfixes (TLS):
3785 - Check more thoroughly throughout the TLS code for possible
3786 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
3788 o Minor bugfixes (transparent proxy):
3789 - Use getsockname, not getsockopt, to retrieve the address for a
3790 TPROXY-redirected connection. Fixes bug 13796; bugfix
3793 o Minor bugfixes (windows):
3794 - Remove code to special-case handling of NTE_BAD_KEYSET when
3795 acquiring windows CryptoAPI context. This error can't actually
3796 occur for the parameters we're providing. Fixes bug 10816; bugfix
3799 o Minor bugfixes (zlib):
3800 - Avoid truncating a zlib stream when trying to finalize it with an
3801 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
3803 o Code simplification and refactoring:
3804 - Change the entry_is_live() function to take named bitfield
3805 elements instead of an unnamed list of booleans. Closes
3807 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
3808 Resolves ticket 12205.
3809 - Use calloc and reallocarray functions instead of multiply-
3810 then-malloc. This makes it less likely for us to fall victim to an
3811 integer overflow attack when allocating. Resolves ticket 12855.
3812 - Use the standard macro name SIZE_MAX, instead of our
3814 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
3815 functions which take them as arguments. Replace 0 with NO_DIRINFO
3816 in a function call for clarity. Seeks to prevent future issues
3818 - Avoid 4 null pointer errors under clang static analysis by using
3819 tor_assert() to prove that the pointers aren't null. Fixes
3821 - Rework the API of policies_parse_exit_policy() to use a bitmask to
3822 represent parsing options, instead of a confusing mess of
3823 booleans. Resolves ticket 8197.
3824 - Introduce a helper function to parse ExitPolicy in
3825 or_options_t structure.
3826 - Move fields related to isolating and configuring client ports into
3827 a shared structure. Previously, they were duplicated across
3828 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
3829 to copy them correctly had been the cause of at least one bug in
3830 the past. Closes ticket 8546.
3831 - Refactor the get_interface_addresses_raw() doom-function into
3832 multiple smaller and simpler subfunctions. Cover the resulting
3833 subfunctions with unit-tests. Fixes a significant portion of
3835 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
3836 only for version <= 0.2.2.24 which is now deprecated. Closes
3838 - Remove a test for a long-defunct broken version-one
3840 - Refactor main loop to extract the 'loop' part. This makes it
3841 easier to run Tor under Shadow. Closes ticket 15176.
3842 - Stop using can_complete_circuits as a global variable; access it
3843 with a function instead.
3844 - Avoid using operators directly as macro arguments: this lets us
3845 apply coccinelle transformations to our codebase more directly.
3846 Closes ticket 13172.
3847 - Combine the functions used to parse ClientTransportPlugin and
3848 ServerTransportPlugin into a single function. Closes ticket 6456.
3849 - Add inline functions and convenience macros for inspecting channel
3850 state. Refactor the code to use convenience macros instead of
3851 checking channel state directly. Fixes issue 7356.
3852 - Document all members of was_router_added_t and rename
3853 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
3854 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
3855 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
3856 constant instead of hardcoded value. Fixes issue 13840.
3857 - Refactor our generic strmap and digestmap types into a single
3858 implementation, so that we can add a new digest256map
3862 - Add a doc/TUNING document with tips for handling large numbers of
3863 TCP connections when running busy Tor relay. Update the warning
3864 message to point to this file when running out of sockets
3865 operating system is allowing to use simultaneously. Resolves
3867 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
3868 for writing the OpenBSD-specific tips. Resolves ticket 13702.
3869 - Make the tor-resolve documentation match its help string and its
3870 options. Resolves part of ticket 14325.
3871 - Log a more useful error message from tor-resolve when failing to
3872 look up a hidden service address. Resolves part of ticket 14325.
3873 - Document the bridge-authority-only 'networkstatus-bridges' file.
3874 Closes ticket 13713; patch from "tom".
3875 - Fix typo in PredictedPortsRelevanceTime option description in
3876 manpage. Resolves issue 13707.
3877 - Stop suggesting that users specify relays by nickname: it isn't a
3878 good idea. Also, properly cross-reference how to specify relays in
3879 all parts of manual documenting options that take a list of
3880 relays. Closes ticket 13381.
3881 - Clarify the HiddenServiceDir option description in manpage to make
3882 it clear that relative paths are taken with respect to the current
3883 working directory. Also clarify that this behavior is not
3884 guaranteed to remain indefinitely. Fixes issue 13913.
3886 o Distribution (systemd):
3887 - systemd unit file: only allow tor to write to /var/lib/tor and
3888 /var/log/tor. The rest of the filesystem is accessible for reading
3889 only. Patch by intrigeri; resolves ticket 12751.
3890 - systemd unit file: ensure that the process and all its children
3891 can never gain new privileges. Patch by intrigeri; resolves
3893 - systemd unit file: set up /var/run/tor as writable for the Tor
3894 service. Patch by intrigeri; resolves ticket 13196.
3896 o Downgraded warnings:
3897 - Don't warn when we've attempted to contact a relay using the wrong
3898 ntor onion key. Closes ticket 9635.
3901 - Remove some lingering dead code that once supported mempools.
3902 Mempools were disabled by default in 0.2.5, and removed entirely
3903 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
3906 o Removed features (directory authorities):
3907 - Remove code that prevented authorities from listing Tor relays
3908 affected by CVE-2011-2769 as guards. These relays are already
3909 rejected altogether due to the minimum version requirement of
3910 0.2.3.16-alpha. Closes ticket 13152.
3911 - The "AuthDirRejectUnlisted" option no longer has any effect, as
3912 the fingerprints file (approved-routers) has been deprecated.
3913 - Directory authorities do not support being Naming dirauths anymore.
3914 The "NamingAuthoritativeDir" config option is now obsolete.
3915 - Directory authorities do not support giving out the BadDirectory
3917 - Directory authorities no longer advertise or support consensus
3918 methods 1 through 12 inclusive. These consensus methods were
3919 obsolete and/or insecure: maintaining the ability to support them
3920 served no good purpose. Implements part of proposal 215; closes
3924 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
3925 longer silently accepted as an alias for "ExitNodes".
3926 - The --enable-mempool and --enable-buf-freelists options, which
3927 were originally created to work around bad malloc implementations,
3928 no longer exist. They were off-by-default in 0.2.5. Closes
3930 - We no longer remind the user about configuration options that have
3931 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
3932 - Remove our old, non-weighted bandwidth-based node selection code.
3933 Previously, we used it as a fallback when we couldn't perform
3934 weighted bandwidth-based node selection. But that would only
3935 happen in the cases where we had no consensus, or when we had a
3936 consensus generated by buggy or ancient directory authorities. In
3937 either case, it's better to use the more modern, better maintained
3938 algorithm, with reasonable defaults for the weights. Closes
3940 - Remove the --disable-curve25519 configure option. Relays and
3941 clients now are required to support curve25519 and the
3943 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
3944 used to be deprecated synonyms for "StrictNodes", are now marked
3945 obsolete. Resolves ticket 12226.
3946 - Clients don't understand the BadDirectory flag in the consensus
3947 anymore, and ignore it.
3949 o Removed platform support:
3950 - We no longer include special code to build on Windows CE; as far
3951 as we know, nobody has used Tor on Windows CE in a very long time.
3952 Closes ticket 11446.
3954 o Testing (test-network.sh):
3955 - Stop using "echo -n", as some shells' built-in echo doesn't
3956 support "-n". Instead, use "/bin/echo -n". Partially fixes
3958 - Stop an apparent test-network hang when used with make -j2. Fixes
3960 - Add a --delay option to test-network.sh, which configures the
3961 delay before the chutney network tests for data transmission.
3962 Partially implements ticket 13161.
3965 - Test that tor does not fail when key files are zero-length. Check
3966 that tor generates new keys, and overwrites the empty key files.
3967 - Test that tor generates new keys when keys are missing
3968 (existing behavior).
3969 - Test that tor does not overwrite key files that already contain
3970 data (existing behavior). Tests bug 13111. Patch by "teor".
3971 - New "make test-stem" target to run stem integration tests.
3972 Requires that the "STEM_SOURCE_DIR" environment variable be set.
3973 Closes ticket 14107.
3974 - Make the test_cmdline_args.py script work correctly on Windows.
3975 Patch from Gisle Vanem.
3976 - Move the slower unit tests into a new "./src/test/test-slow"
3977 binary that can be run independently of the other tests. Closes
3979 - New tests for many parts of channel, relay, and circuitmux
3980 functionality. Code by Andrea; part of 9262.
3981 - New tests for parse_transport_line(). Part of ticket 6456.
3982 - In the unit tests, use chgrp() to change the group of the unit
3983 test temporary directory to the current user, so that the sticky
3984 bit doesn't interfere with tests that check directory groups.
3986 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
3988 - Refactor the function that chooses guard nodes so that it can more
3989 easily be tested; write some tests for it.
3990 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
3991 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
3992 - Create unit tests for format_time_interval(). With bug 13393.
3993 - Add unit tests for tor_timegm signed overflow, tor_timegm and
3994 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
3995 tests (visible) fixes in bug 13476.
3996 - Add a "coverage-html" make target to generate HTML-visualized
3997 coverage results when building with --enable-coverage. (Requires
3998 lcov.) Patch from Kevin Murray.
3999 - Enable the backtrace handler (where supported) when running the
4001 - Revise all unit tests that used the legacy test_* macros to
4002 instead use the recommended tt_* macros. This patch was generated
4003 with coccinelle, to avoid manual errors. Closes ticket 13119.
4005 Changes in version 0.2.5.11 - 2015-03-17
4006 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
4008 It backports several bugfixes from the 0.2.6 branch, including a
4009 couple of medium-level security fixes for relays and exit nodes.
4010 It also updates the list of directory authorities.
4012 o Directory authority changes:
4013 - Remove turtles as a directory authority.
4014 - Add longclaw as a new (v3) directory authority. This implements
4015 ticket 13296. This keeps the directory authority count at 9.
4016 - The directory authority Faravahar has a new IP address. This
4017 closes ticket 14487.
4019 o Major bugfixes (crash, OSX, security):
4020 - Fix a remote denial-of-service opportunity caused by a bug in
4021 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
4024 o Major bugfixes (relay, stability, possible security):
4025 - Fix a bug that could lead to a relay crashing with an assertion
4026 failure if a buffer of exactly the wrong layout was passed to
4027 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
4028 0.2.0.10-alpha. Patch from 'cypherpunks'.
4029 - Do not assert if the 'data' pointer on a buffer is advanced to the
4030 very end of the buffer; log a BUG message instead. Only assert if
4031 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
4033 o Major bugfixes (exit node stability):
4034 - Fix an assertion failure that could occur under high DNS load.
4035 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
4036 diagnosed and fixed by "cypherpunks".
4038 o Major bugfixes (Linux seccomp2 sandbox):
4039 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
4040 crash during attempts to call wait4. Fixes bug 15088; bugfix on
4041 0.2.5.1-alpha. Patch from "sanic".
4043 o Minor features (controller):
4044 - New "GETINFO bw-event-cache" to get information about recent
4045 bandwidth events. Closes ticket 14128. Useful for controllers to
4046 get recent bandwidth history after the fix for ticket 13988.
4048 o Minor features (geoip):
4049 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
4050 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
4053 o Minor bugfixes (client, automapping):
4054 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
4055 no value follows the option. Fixes bug 14142; bugfix on
4056 0.2.4.7-alpha. Patch by "teor".
4057 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
4058 14195; bugfix on 0.1.0.1-rc.
4060 o Minor bugfixes (compilation):
4061 - Build without warnings with the stock OpenSSL srtp.h header, which
4062 has a duplicate declaration of SSL_get_selected_srtp_profile().
4063 Fixes bug 14220; this is OpenSSL's bug, not ours.
4065 o Minor bugfixes (directory authority):
4066 - Allow directory authorities to fetch more data from one another if
4067 they find themselves missing lots of votes. Previously, they had
4068 been bumping against the 10 MB queued data limit. Fixes bug 14261;
4069 bugfix on 0.1.2.5-alpha.
4070 - Enlarge the buffer to read bwauth generated files to avoid an
4071 issue when parsing the file in dirserv_read_measured_bandwidths().
4072 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
4074 o Minor bugfixes (statistics):
4075 - Increase period over which bandwidth observations are aggregated
4076 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
4078 o Minor bugfixes (preventative security, C safety):
4079 - When reading a hexadecimal, base-32, or base-64 encoded value from
4080 a string, always overwrite the whole output buffer. This prevents
4081 some bugs where we would look at (but fortunately, not reveal)
4082 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
4086 Changes in version 0.2.4.26 - 2015-03-17
4087 Tor 0.2.4.26 includes an updated list of directory authorities. It
4088 also backports a couple of stability and security bugfixes from 0.2.5
4091 o Directory authority changes:
4092 - Remove turtles as a directory authority.
4093 - Add longclaw as a new (v3) directory authority. This implements
4094 ticket 13296. This keeps the directory authority count at 9.
4095 - The directory authority Faravahar has a new IP address. This
4096 closes ticket 14487.
4098 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
4099 - Fix an assertion failure that could occur under high DNS load.
4100 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
4101 diagnosed and fixed by "cypherpunks".
4103 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
4104 - Fix a bug that could lead to a relay crashing with an assertion
4105 failure if a buffer of exactly the wrong layout was passed to
4106 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
4107 0.2.0.10-alpha. Patch from 'cypherpunks'.
4108 - Do not assert if the 'data' pointer on a buffer is advanced to the
4109 very end of the buffer; log a BUG message instead. Only assert if
4110 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
4112 o Minor features (geoip):
4113 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
4114 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
4117 Changes in version 0.2.5.10 - 2014-10-24
4118 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
4120 It adds several new security features, including improved
4121 denial-of-service resistance for relays, new compiler hardening
4122 options, and a system-call sandbox for hardened installations on Linux
4123 (requires seccomp2). The controller protocol has several new features,
4124 resolving IPv6 addresses should work better than before, and relays
4125 should be a little more CPU-efficient. We've added support for more
4126 OpenBSD and FreeBSD transparent proxy types. We've improved the build
4127 system and testing infrastructure to allow unit testing of more parts
4128 of the Tor codebase. Finally, we've addressed several nagging pluggable
4129 transport usability issues, and included numerous other small bugfixes
4130 and features mentioned below.
4132 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
4133 have accumulated many known flaws; everyone should upgrade.
4135 o Major features (security):
4136 - The ntor handshake is now on-by-default, no matter what the
4137 directory authorities recommend. Implements ticket 8561.
4138 - Make the "tor-gencert" tool used by directory authority operators
4139 create 2048-bit signing keys by default (rather than 1024-bit, since
4140 1024-bit is uncomfortably small these days). Addresses ticket 10324.
4141 - Warn about attempts to run hidden services and relays in the same
4142 process: that's probably not a good idea. Closes ticket 12908.
4143 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
4144 today support TLS 1.0 or later, so we can safely turn off support
4145 for this old (and insecure) protocol. Fixes bug 13426.
4147 o Major features (relay security, DoS-resistance):
4148 - When deciding whether we have run out of memory and we need to
4149 close circuits, also consider memory allocated in buffers for
4150 streams attached to each circuit.
4152 This change, which extends an anti-DoS feature introduced in
4153 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
4154 better resist more memory-based DoS attacks than before. Since the
4155 MaxMemInCellQueues option now applies to all queues, it is renamed
4156 to MaxMemInQueues. This feature fixes bug 10169.
4157 - Avoid hash-flooding denial-of-service attacks by using the secure
4158 SipHash-2-4 hash function for our hashtables. Without this
4159 feature, an attacker could degrade performance of a targeted
4160 client or server by flooding their data structures with a large
4161 number of entries to be stored at the same hash table position,
4162 thereby slowing down the Tor instance. With this feature, hash
4163 table positions are derived from a randomized cryptographic key,
4164 and an attacker cannot predict which entries will collide. Closes
4166 - If you don't specify MaxMemInQueues yourself, Tor now tries to
4167 pick a good value based on your total system memory. Previously,
4168 the default was always 8 GB. You can still override the default by
4169 setting MaxMemInQueues yourself. Resolves ticket 11396.
4171 o Major features (bridges and pluggable transports):
4172 - Add support for passing arguments to managed pluggable transport
4173 proxies. Implements ticket 3594.
4174 - Bridges now track GeoIP information and the number of their users
4175 even when pluggable transports are in use, and report usage
4176 statistics in their extra-info descriptors. Resolves tickets 4773
4178 - Don't launch pluggable transport proxies if we don't have any
4179 bridges configured that would use them. Now we can list many
4180 pluggable transports, and Tor will dynamically start one when it
4181 hears a bridge address that needs it. Resolves ticket 5018.
4182 - The bridge directory authority now assigns status flags (Stable,
4183 Guard, etc) to bridges based on thresholds calculated over all
4184 Running bridges. Now bridgedb can finally make use of its features
4185 to e.g. include at least one Stable bridge in its answers. Fixes
4188 o Major features (controller):
4189 - Extend ORCONN controller event to include an "ID" parameter,
4190 and add four new controller event types CONN_BW, CIRC_BW,
4191 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
4192 The new events are emitted in private Tor networks only, with the
4193 goal of being able to better track performance and load during
4194 full-network simulations. Implements proposal 218 and ticket 7359.
4196 o Major features (relay performance):
4197 - Speed up server-side lookups of rendezvous and introduction point
4198 circuits by using hashtables instead of linear searches. These
4199 functions previously accounted between 3 and 7% of CPU usage on
4200 some busy relays. Resolves ticket 9841.
4201 - Avoid wasting CPU when extending a circuit over a channel that is
4202 nearly out of circuit IDs. Previously, we would do a linear scan
4203 over possible circuit IDs before finding one or deciding that we
4204 had exhausted our possibilities. Now, we try at most 64 random
4205 circuit IDs before deciding that we probably won't succeed. Fixes
4206 a possible root cause of ticket 11553.
4208 o Major features (seccomp2 sandbox, Linux only):
4209 - Use the seccomp2 syscall filtering facility on Linux to limit
4210 which system calls Tor can invoke. This is an experimental,
4211 Linux-only feature to provide defense-in-depth against unknown
4212 attacks. To try turning it on, set "Sandbox 1" in your torrc
4213 file. Please be ready to report bugs. We hope to add support
4214 for better sandboxing in the future, including more fine-grained
4215 filters, better division of responsibility, and support for more
4216 platforms. This work has been done by Cristian-Matei Toader for
4217 Google Summer of Code. Resolves tickets 11351 and 11465.
4219 o Major features (testing networks):
4220 - Make testing Tor networks bootstrap better: lower directory fetch
4221 retry schedules and maximum interval without directory requests,
4222 and raise maximum download tries. Implements ticket 6752.
4223 - Add make target 'test-network' to run tests on a Chutney network.
4224 Implements ticket 8530.
4226 o Major features (other):
4227 - On some platforms (currently: recent OSX versions, glibc-based
4228 platforms that support the ELF format, and a few other
4229 Unix-like operating systems), Tor can now dump stack traces
4230 when a crash occurs or an assertion fails. By default, traces
4231 are dumped to stderr (if possible) and to any logs that are
4232 reporting errors. Implements ticket 9299.
4234 o Deprecated versions:
4235 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
4236 attention for some while.
4238 o Major bugfixes (security, directory authorities):
4239 - Directory authorities now include a digest of each relay's
4240 identity key as a part of its microdescriptor.
4242 This is a workaround for bug 11743 (reported by "cypherpunks"),
4243 where Tor clients do not support receiving multiple
4244 microdescriptors with the same SHA256 digest in the same
4245 consensus. When clients receive a consensus like this, they only
4246 use one of the relays. Without this fix, a hostile relay could
4247 selectively disable some client use of target relays by
4248 constructing a router descriptor with a different identity and the
4249 same microdescriptor parameters and getting the authorities to
4250 list it in a microdescriptor consensus. This fix prevents an
4251 attacker from causing a microdescriptor collision, because the
4252 router's identity is not forgeable.
4254 o Major bugfixes (openssl bug workaround):
4255 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
4256 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
4257 bug 13471. This is a workaround for an OpenSSL bug.
4259 o Major bugfixes (client):
4260 - Perform circuit cleanup operations even when circuit
4261 construction operations are disabled (because the network is
4262 disabled, or because there isn't enough directory information).
4263 Previously, when we were not building predictive circuits, we
4264 were not closing expired circuits either. Fixes bug 8387; bugfix on
4265 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
4266 became more strict about when we have "enough directory information
4269 o Major bugfixes (client, pluggable transports):
4270 - When managing pluggable transports, use OS notification facilities
4271 to learn if they have crashed, and don't attempt to kill any
4272 process that has already exited. Fixes bug 8746; bugfix
4275 o Major bugfixes (relay denial of service):
4276 - Instead of writing destroy cells directly to outgoing connection
4277 buffers, queue them and intersperse them with other outgoing cells.
4278 This can prevent a set of resource starvation conditions where too
4279 many pending destroy cells prevent data cells from actually getting
4280 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
4281 bugfix on 0.2.0.1-alpha.
4283 o Major bugfixes (relay):
4284 - Avoid queuing or sending destroy cells for circuit ID zero when we
4285 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
4286 Found and fixed by "cypherpunks".
4287 - Fix ORPort reachability detection on relays running behind a
4288 proxy, by correctly updating the "local" mark on the controlling
4289 channel when changing the address of an or_connection_t after the
4290 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
4291 - Use a direct dirport connection when uploading non-anonymous
4292 descriptors to the directory authorities. Previously, relays would
4293 incorrectly use tunnel connections under a fairly wide variety of
4294 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
4295 - When a circuit accidentally has the same circuit ID for its
4296 forward and reverse direction, correctly detect the direction of
4297 cells using that circuit. Previously, this bug made roughly one
4298 circuit in a million non-functional. Fixes bug 12195; this is a
4299 bugfix on every version of Tor.
4301 o Minor features (security):
4302 - New --enable-expensive-hardening option to enable security
4303 hardening options that consume nontrivial amounts of CPU and
4304 memory. Right now, this includes AddressSanitizer and UbSan, which
4305 are supported in newer versions of GCC and Clang. Closes ticket
4307 - Authorities now assign the Guard flag to the fastest 25% of the
4308 network (it used to be the fastest 50%). Also raise the consensus
4309 weight that guarantees the Guard flag from 250 to 2000. For the
4310 current network, this results in about 1100 guards, down from 2500.
4311 This step paves the way for moving the number of entry guards
4312 down to 1 (proposal 236) while still providing reasonable expected
4313 performance for most users. Implements ticket 12690.
4315 o Minor features (security, memory management):
4316 - Memory allocation tricks (mempools and buffer freelists) are now
4317 disabled by default. You can turn them back on with
4318 --enable-mempools and --enable-buf-freelists respectively. We're
4319 disabling these features because malloc performance is good enough
4320 on most platforms, and a similar feature in OpenSSL exacerbated
4321 exploitation of the Heartbleed attack. Resolves ticket 11476.
4323 o Minor features (bridge client):
4324 - Report a more useful failure message when we can't connect to a
4325 bridge because we don't have the right pluggable transport
4326 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
4328 o Minor features (bridge):
4329 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
4330 cookie file for the ExtORPort g+r by default.
4332 o Minor features (bridges, pluggable transports):
4333 - Bridges now write the SHA1 digest of their identity key
4334 fingerprint (that is, a hash of a hash of their public key) to
4335 notice-level logs, and to a new hashed-fingerprint file. This
4336 information will help bridge operators look up their bridge in
4337 Globe and similar tools. Resolves ticket 10884.
4338 - Improve the message that Tor displays when running as a bridge
4339 using pluggable transports without an Extended ORPort listener.
4340 Also, log the message in the log file too. Resolves ticket 11043.
4341 - Add threshold cutoffs to the networkstatus document created by
4342 the Bridge Authority. Fixes bug 1117.
4343 - On Windows, spawn background processes using the CREATE_NO_WINDOW
4344 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
4345 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
4346 Vidalia set this option for us.) Implements ticket 10297.
4348 o Minor features (build):
4349 - The configure script has a --disable-seccomp option to turn off
4350 support for libseccomp on systems that have it, in case it (or
4351 Tor's use of it) is broken. Resolves ticket 11628.
4352 - Assume that a user using ./configure --host wants to cross-compile,
4353 and give an error if we cannot find a properly named
4354 tool-chain. Add a --disable-tool-name-check option to proceed
4355 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
4356 - If we run ./configure and the compiler recognizes -fstack-protector
4357 but the linker rejects it, warn the user about a potentially missing
4358 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
4359 - Add support for `--library-versions` flag. Implements ticket 6384.
4360 - Return the "unexpected sendme" warnings to a warn severity, but make
4361 them rate limited, to help diagnose ticket 8093.
4362 - Detect a missing asciidoc, and warn the user about it, during
4363 configure rather than at build time. Fixes issue 6506. Patch from
4366 o Minor features (client):
4367 - Add a new option, PredictedPortsRelevanceTime, to control how long
4368 after having received a request to connect to a given port Tor
4369 will try to keep circuits ready in anticipation of future requests
4370 for that port. Patch from "unixninja92"; implements ticket 9176.
4372 o Minor features (config options and command line):
4373 - Add an --allow-missing-torrc commandline option that tells Tor to
4374 run even if the configuration file specified by -f is not available.
4375 Implements ticket 10060.
4376 - Add support for the TPROXY transparent proxying facility on Linux.
4377 See documentation for the new TransProxyType option for more
4378 details. Implementation by "thomo". Closes ticket 10582.
4380 o Minor features (config options):
4381 - Config (torrc) lines now handle fingerprints which are missing
4382 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
4383 - Support a --dump-config option to print some or all of the
4384 configured options. Mainly useful for debugging the command-line
4385 option parsing code. Helps resolve ticket 4647.
4386 - Raise awareness of safer logging: notify user of potentially
4387 unsafe config options, like logging more verbosely than severity
4388 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
4389 - Add a new configuration option TestingV3AuthVotingStartOffset
4390 that bootstraps a network faster by changing the timing for
4391 consensus votes. Addresses ticket 8532.
4392 - Add a new torrc option "ServerTransportOptions" that allows
4393 bridge operators to pass configuration parameters to their
4394 pluggable transports. Resolves ticket 8929.
4395 - The config (torrc) file now accepts bandwidth and space limits in
4396 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
4397 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
4400 o Minor features (controller):
4401 - Make the entire exit policy available from the control port via
4402 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
4404 - Because of the fix for ticket 11396, the real limit for memory
4405 usage may no longer match the configured MaxMemInQueues value. The
4406 real limit is now exposed via GETINFO limits/max-mem-in-queues.
4407 - Add a new "HS_DESC" controller event that reports activities
4408 related to hidden service descriptors. Resolves ticket 8510.
4409 - New "DROPGUARDS" controller command to forget all current entry
4410 guards. Not recommended for ordinary use, since replacing guards
4411 too frequently makes several attacks easier. Resolves ticket 9934;
4413 - Implement the TRANSPORT_LAUNCHED control port event that
4414 notifies controllers about new launched pluggable
4415 transports. Resolves ticket 5609.
4417 o Minor features (diagnostic):
4418 - When logging a warning because of bug 7164, additionally check the
4419 hash table for consistency (as proposed on ticket 11737). This may
4420 help diagnose bug 7164.
4421 - When we log a heartbeat, log how many one-hop circuits we have
4422 that are at least 30 minutes old, and log status information about
4423 a few of them. This is an attempt to track down bug 8387.
4424 - When encountering an unexpected CR while writing text to a file on
4425 Windows, log the name of the file. Should help diagnosing
4427 - Give more specific warnings when a client notices that an onion
4428 handshake has failed. Fixes ticket 9635.
4429 - Add significant new logging code to attempt to diagnose bug 12184,
4430 where relays seem to run out of available circuit IDs.
4431 - Improve the diagnostic log message for bug 8387 even further to
4432 try to improve our odds of figuring out why one-hop directory
4433 circuits sometimes do not get closed.
4434 - Add more log messages to diagnose bug 7164, which causes
4435 intermittent "microdesc_free() called but md was still referenced"
4436 warnings. We now include more information, to figure out why we
4437 might be cleaning a microdescriptor for being too old if it's
4438 still referenced by a live node_t object.
4439 - Log current accounting state (bytes sent and received + remaining
4440 time for the current accounting period) in the relay's heartbeat
4441 message. Implements ticket 5526; patch from Peter Retzlaff.
4443 o Minor features (geoip):
4444 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
4447 o Minor features (interface):
4448 - Generate a warning if any ports are listed in the SocksPolicy,
4449 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
4450 AuthDirBadExit options. (These options only support address
4451 ranges.) Fixes part of ticket 11108.
4453 o Minor features (kernel API usage):
4454 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
4455 sockets in a single system call. Implements ticket 5129.
4457 o Minor features (log messages):
4458 - When ServerTransportPlugin is set on a bridge, Tor can write more
4459 useful statistics about bridge use in its extrainfo descriptors,
4460 but only if the Extended ORPort ("ExtORPort") is set too. Add a
4461 log message to inform the user in this case. Resolves ticket 9651.
4462 - When receiving a new controller connection, log the origin address.
4463 Resolves ticket 9698; patch from "sigpipe".
4464 - When logging OpenSSL engine status at startup, log the status of
4465 more engines. Fixes ticket 10043; patch from Joshua Datko.
4467 o Minor features (log verbosity):
4468 - Demote the message that we give when a flushing connection times
4469 out for too long from NOTICE to INFO. It was usually meaningless.
4470 Resolves ticket 5286.
4471 - Don't log so many notice-level bootstrapping messages at startup
4472 about downloading descriptors. Previously, we'd log a notice
4473 whenever we learned about more routers. Now, we only log a notice
4474 at every 5% of progress. Fixes bug 9963.
4475 - Warn less verbosely when receiving a malformed
4476 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
4478 o Minor features (performance):
4479 - If we're using the pure-C 32-bit curve25519_donna implementation
4480 of curve25519, build it with the -fomit-frame-pointer option to
4481 make it go faster on register-starved hosts. This improves our
4482 handshake performance by about 6% on i386 hosts without nacl.
4485 o Minor features (relay):
4486 - If a circuit timed out for at least 3 minutes, check if we have a
4487 new external IP address, and publish a new descriptor with the new
4488 IP address if it changed. Resolves ticket 2454.
4490 o Minor features (testing):
4491 - If Python is installed, "make check" now runs extra tests beyond
4492 the unit test scripts.
4493 - When bootstrapping a test network, sometimes very few relays get
4494 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
4495 specify a set of relays which should be voted Guard regardless of
4496 their uptime or bandwidth. Addresses ticket 9206.
4498 o Minor features (transparent proxy, *BSD):
4499 - Support FreeBSD's ipfw firewall interface for TransPort ports on
4500 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
4501 10267; patch from "yurivict".
4502 - Support OpenBSD's divert-to rules with the pf firewall for
4503 transparent proxy ports. To enable it, set "TransProxyType
4504 pf-divert". This allows Tor to run a TransPort transparent proxy
4505 port on OpenBSD 4.4 or later without root privileges. See the
4506 pf.conf(5) manual page for information on configuring pf to use
4507 divert-to rules. Closes ticket 10896; patch from Dana Koch.
4509 o Minor bugfixes (bridge client):
4510 - Stop accepting bridge lines containing hostnames. Doing so would
4511 cause clients to perform DNS requests on the hostnames, which was
4512 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
4514 o Minor bugfixes (bridges):
4515 - Avoid potential crashes or bad behavior when launching a
4516 server-side managed proxy with ORPort or ExtORPort temporarily
4517 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
4518 - Fix a bug where the first connection works to a bridge that uses a
4519 pluggable transport with client-side parameters, but we don't send
4520 the client-side parameters on subsequent connections. (We don't
4521 use any pluggable transports with client-side parameters yet,
4522 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
4523 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
4525 o Minor bugfixes (build, auxiliary programs):
4526 - Stop preprocessing the "torify" script with autoconf, since
4527 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
4529 - The tor-fw-helper program now follows the standard convention and
4530 exits with status code "0" on success. Fixes bug 9030; bugfix on
4531 0.2.3.1-alpha. Patch by Arlo Breault.
4532 - Corrected ./configure advice for what openssl dev package you should
4533 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
4535 o Minor bugfixes (client):
4536 - Avoid "Tried to open a socket with DisableNetwork set" warnings
4537 when starting a client with bridges configured and DisableNetwork
4538 set. (Tor launcher starts Tor with DisableNetwork set the first
4539 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
4540 - Improve the log message when we can't connect to a hidden service
4541 because all of the hidden service directory nodes hosting its
4542 descriptor are excluded. Improves on our fix for bug 10722, which
4543 was a bugfix on 0.2.0.10-alpha.
4544 - Raise a control port warning when we fail to connect to all of
4545 our bridges. Previously, we didn't inform the controller, and
4546 the bootstrap process would stall. Fixes bug 11069; bugfix on
4548 - Exit immediately when a process-owning controller exits.
4549 Previously, tor relays would wait for a little while after their
4550 controller exited, as if they had gotten an INT signal -- but this
4551 was problematic, since there was no feedback for the user. To do a
4552 clean shutdown, controllers should send an INT signal and give Tor
4553 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
4554 - Stop attempting to connect to bridges before our pluggable
4555 transports are configured (harmless but resulted in some erroneous
4556 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
4557 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
4558 generating incorrect SOCKS5 responses, and confusing client
4559 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
4561 o Minor bugfixes (client, DNSPort):
4562 - When using DNSPort, try to respond to AAAA requests with AAAA
4563 answers. Previously, we hadn't looked at the request type when
4564 deciding which answer type to prefer. Fixes bug 10468; bugfix on
4566 - When receiving a DNS query for an unsupported record type, reply
4567 with no answer rather than with a NOTIMPL error. This behavior
4568 isn't correct either, but it will break fewer client programs, we
4569 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
4572 o Minor bugfixes (client, logging during bootstrap):
4573 - Only report the first fatal bootstrap error on a given OR
4574 connection. This stops us from telling the controller bogus error
4575 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
4576 - Avoid generating spurious warnings when starting with
4577 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
4580 o Minor bugfixes (closing OR connections):
4581 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
4582 check if it's an or_connection_t and correctly call
4583 connection_or_close_for_error() rather than
4584 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
4586 - When closing all connections on setting DisableNetwork to 1, use
4587 connection_or_close_normally() rather than closing OR connections
4588 out from under the channel layer. Fixes bug 11306; bugfix on
4591 o Minor bugfixes (code correctness):
4592 - Previously we used two temporary files when writing descriptors to
4593 disk; now we only use one. Fixes bug 1376.
4594 - Remove an erroneous (but impossible and thus harmless) pointer
4595 comparison that would have allowed compilers to skip a bounds
4596 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
4597 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
4598 - Fix an always-true assertion in pluggable transports code so it
4599 actually checks what it was trying to check. Fixes bug 10046;
4600 bugfix on 0.2.3.9-alpha. Found by "dcb".
4602 o Minor bugfixes (command line):
4603 - Use a single command-line parser for parsing torrc options on the
4604 command line and for finding special command-line options to avoid
4605 inconsistent behavior for torrc option arguments that have the same
4606 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
4608 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
4609 9573; bugfix on 0.0.9pre5.
4611 o Minor bugfixes (compilation):
4612 - Compile correctly with builds and forks of OpenSSL (such as
4613 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
4614 0.2.1.1-alpha. Patch from "dhill".
4615 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
4616 turned off (that is, without support for v2 link handshakes). Fixes
4617 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
4618 - In routerlist_assert_ok(), don't take the address of a
4619 routerinfo's cache_info member unless that routerinfo is non-NULL.
4620 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
4621 - Fix a large number of false positive warnings from the clang
4622 analyzer static analysis tool. This should make real warnings
4623 easier for clang analyzer to find. Patch from "teor". Closes
4625 - Resolve GCC complaints on OpenBSD about discarding constness in
4626 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
4627 on 0.1.1.23. Patch from Dana Koch.
4628 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
4629 treatment of long and time_t as comparable types. Fixes part of
4630 bug 11633. Patch from Dana Koch.
4631 - When deciding whether to build the 64-bit curve25519
4632 implementation, detect platforms where we can compile 128-bit
4633 arithmetic but cannot link it. Fixes bug 11729; bugfix on
4634 0.2.4.8-alpha. Patch from "conradev".
4635 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
4636 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
4637 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
4639 - Build and run correctly on systems like OpenBSD-current that have
4640 patched OpenSSL to remove get_cipher_by_char and/or its
4641 implementations. Fixes issue 13325.
4643 o Minor bugfixes (controller and command-line):
4644 - If changing a config option via "setconf" fails in a recoverable
4645 way, we used to nonetheless write our new control ports to the
4646 file described by the "ControlPortWriteToFile" option. Now we only
4647 write out that file if we successfully switch to the new config
4648 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
4650 o Minor bugfixes (directory server):
4651 - No longer accept malformed http headers when parsing urls from
4652 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
4653 bugfix on 0.0.6pre1.
4654 - When sending a compressed set of descriptors or microdescriptors,
4655 make sure to finalize the zlib stream. Previously, we would write
4656 all the compressed data, but if the last descriptor we wanted to
4657 send was missing or too old, we would not mark the stream as
4658 finished. This caused problems for decompression tools. Fixes bug
4659 11648; bugfix on 0.1.1.23.
4661 o Minor bugfixes (hidden service):
4662 - Only retry attempts to connect to a chosen rendezvous point 8
4663 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
4665 o Minor bugfixes (interface):
4666 - Reject relative control socket paths and emit a warning. Previously,
4667 single-component control socket paths would be rejected, but Tor
4668 would not log why it could not validate the config. Fixes bug 9258;
4669 bugfix on 0.2.3.16-alpha.
4671 o Minor bugfixes (log messages):
4672 - Fix a bug where clients using bridges would report themselves
4673 as 50% bootstrapped even without a live consensus document.
4674 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
4675 - Suppress a warning where, if there's only one directory authority
4676 in the network, we would complain that votes and signatures cannot
4677 be uploaded to other directory authorities. Fixes bug 10842;
4678 bugfix on 0.2.2.26-beta.
4679 - Report bootstrapping progress correctly when we're downloading
4680 microdescriptors. We had updated our "do we have enough microdescs
4681 to begin building circuits?" logic most recently in 0.2.4.10-alpha
4682 (see bug 5956), but we left the bootstrap status event logic at
4683 "how far through getting 1/4 of them are we?" Fixes bug 9958;
4684 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
4686 o Minor bugfixes (logging):
4687 - Downgrade "Unexpected onionskin length after decryption" warning
4688 to a protocol-warn, since there's nothing relay operators can do
4689 about a client that sends them a malformed create cell. Resolves
4690 bug 12996; bugfix on 0.0.6rc1.
4691 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
4692 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
4693 - When logging information about an EXTEND2 or EXTENDED2 cell, log
4694 their names correctly. Fixes part of bug 12700; bugfix
4696 - When logging information about a relay cell whose command we don't
4697 recognize, log its command as an integer. Fixes part of bug 12700;
4698 bugfix on 0.2.1.10-alpha.
4699 - Escape all strings from the directory connection before logging
4700 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
4701 - Squelch a spurious LD_BUG message "No origin circuit for
4702 successful SOCKS stream" in certain hidden service failure cases;
4704 - Downgrade the severity of the 'unexpected sendme cell from client'
4705 from 'warn' to 'protocol warning'. Closes ticket 8093.
4707 o Minor bugfixes (misc code correctness):
4708 - In munge_extrainfo_into_routerinfo(), check the return value of
4709 memchr(). This would have been a serious issue if we ever passed
4710 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
4712 - On the chance that somebody manages to build Tor on a
4713 platform where time_t is unsigned, correct the way that
4714 microdesc_add_to_cache() handles negative time arguments.
4715 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
4716 - Fix various instances of undefined behavior in channeltls.c,
4717 tor_memmem(), and eventdns.c that would cause us to construct
4718 pointers to memory outside an allocated object. (These invalid
4719 pointers were not accessed, but C does not even allow them to
4720 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
4721 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
4722 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
4723 fix some miscellaneous errors in our tests and codebase. Fixes bug
4724 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
4725 - Always check return values for unlink, munmap, UnmapViewOfFile;
4726 check strftime return values more often. In some cases all we can
4727 do is report a warning, but this may help prevent deeper bugs from
4728 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
4730 - Fix numerous warnings from the clang "scan-build" static analyzer.
4731 Some of these are programming style issues; some of them are false
4732 positives that indicated awkward code; some are undefined behavior
4733 cases related to constructing (but not using) invalid pointers;
4734 some are assumptions about API behavior; some are (harmlessly)
4735 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
4736 correct; and one or two are genuine bugs that weren't reachable
4737 from the rest of the program. Fixes bug 8793; bugfixes on many,
4740 o Minor bugfixes (node selection):
4741 - If ExcludeNodes is set, consider non-excluded hidden service
4742 directory servers before excluded ones. Do not consider excluded
4743 hidden service directory servers at all if StrictNodes is
4744 set. (Previously, we would sometimes decide to connect to those
4745 servers, and then realize before we initiated a connection that
4746 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
4748 - If we set the ExitNodes option but it doesn't include any nodes
4749 that have the Exit flag, we would choose not to bootstrap. Now we
4750 bootstrap so long as ExitNodes includes nodes which can exit to
4751 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
4753 o Minor bugfixes (performance):
4754 - Avoid a bug where every successful connection made us recompute
4755 the flag telling us whether we have sufficient information to
4756 build circuits. Previously, we would forget our cached value
4757 whenever we successfully opened a channel (or marked a router as
4758 running or not running for any other reason), regardless of
4759 whether we had previously believed the router to be running. This
4760 forced us to run an expensive update operation far too often.
4761 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
4762 - Avoid using tor_memeq() for checking relay cell integrity. This
4763 removes a possible performance bottleneck. Fixes part of bug
4764 12169; bugfix on 0.2.1.31.
4766 o Minor bugfixes (platform-specific):
4767 - When dumping a malformed directory object to disk, save it in
4768 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
4770 - Don't report failures from make_socket_reuseable() on incoming
4771 sockets on OSX: this can happen when incoming connections close
4772 early. Fixes bug 10081.
4774 o Minor bugfixes (pluggable transports):
4775 - Avoid another 60-second delay when starting Tor in a pluggable-
4776 transport-using configuration when we already have cached
4777 descriptors for our bridges. Fixes bug 11965; bugfix
4780 o Minor bugfixes (protocol correctness):
4781 - When receiving a VERSIONS cell with an odd number of bytes, close
4782 the connection immediately since the cell is malformed. Fixes bug
4783 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
4786 o Minor bugfixes (relay, other):
4787 - We now drop CREATE cells for already-existent circuit IDs and for
4788 zero-valued circuit IDs, regardless of other factors that might
4789 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
4791 - When rejecting DATA cells for stream_id zero, still count them
4792 against the circuit's deliver window so that we don't fail to send
4793 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
4795 o Minor bugfixes (relay, threading):
4796 - Check return code on spawn_func() in cpuworker code, so that we
4797 don't think we've spawned a nonworking cpuworker and write junk to
4798 it forever. Fix related to bug 4345; bugfix on all released Tor
4799 versions. Found by "skruffy".
4800 - Use a pthread_attr to make sure that spawn_func() cannot return an
4801 error while at the same time launching a thread. Fix related to
4802 bug 4345; bugfix on all released Tor versions. Reported
4805 o Minor bugfixes (relays and bridges):
4806 - Avoid crashing on a malformed resolv.conf file when running a
4807 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
4808 - Non-exit relays no longer launch mock DNS requests to check for
4809 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
4810 non-exit relays stopped servicing DNS requests. Fixes bug 965;
4811 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
4812 - Bridges now report complete directory request statistics. Related
4813 to bug 5824; bugfix on 0.2.2.1-alpha.
4814 - Bridges now never collect statistics that were designed for
4815 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
4817 o Minor bugfixes (testing):
4818 - Fix all valgrind warnings produced by the unit tests. There were
4819 over a thousand memory leak warnings previously, mostly produced
4820 by forgetting to free things in the unit test code. Fixes bug
4821 11618, bugfixes on many versions of Tor.
4823 o Minor bugfixes (tor-fw-helper):
4824 - Give a correct log message when tor-fw-helper fails to launch.
4825 (Previously, we would say something like "tor-fw-helper sent us a
4826 string we could not parse".) Fixes bug 9781; bugfix
4829 o Minor bugfixes (trivial memory leaks):
4830 - Fix a small memory leak when signing a directory object. Fixes bug
4831 11275; bugfix on 0.2.4.13-alpha.
4832 - Resolve some memory leaks found by coverity in the unit tests, on
4833 exit in tor-gencert, and on a failure to compute digests for our
4834 own keys when generating a v3 networkstatus vote. These leaks
4835 should never have affected anyone in practice.
4837 o Code simplification and refactoring:
4838 - Remove some old fallback code designed to keep Tor clients working
4839 in a network with only two working relays. Elsewhere in the code we
4840 have long since stopped supporting such networks, so there wasn't
4841 much point in keeping it around. Addresses ticket 9926.
4842 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
4843 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
4844 - Extract the common duplicated code for creating a subdirectory
4845 of the data directory and writing to a file in it. Fixes ticket
4846 4282; patch from Peter Retzlaff.
4847 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
4848 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
4849 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
4850 - Add a set of accessor functions for the circuit timeout data
4851 structure. Fixes ticket 6153; patch from "piet".
4852 - Clean up exit paths from connection_listener_new(). Closes ticket
4853 8789. Patch from Arlo Breault.
4854 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
4855 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
4856 - Use a doubly-linked list to implement the global circuit list.
4857 Resolves ticket 9108. Patch from Marek Majkowski.
4858 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
4859 - Remove constants and tests for PKCS1 padding; it's insecure and
4860 shouldn't be used for anything new. Fixes bug 8792; patch
4862 - Remove instances of strcpy() from the unit tests. They weren't
4863 hurting anything, since they were only in the unit tests, but it's
4864 embarassing to have strcpy() in the code at all, and some analysis
4865 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
4866 0.2.3.8-alpha. Patch from Arlo Breault.
4867 - Remove is_internal_IP() function. Resolves ticket 4645.
4868 - Remove unused function circuit_dump_by_chan from circuitlist.c.
4869 Closes issue 9107; patch from "marek".
4870 - Change our use of the ENUM_BF macro to avoid declarations that
4872 - Get rid of router->address, since in all cases it was just the
4873 string representation of router->addr. Resolves ticket 5528.
4876 - Adjust the URLs in the README to refer to the new locations of
4877 several documents on the website. Fixes bug 12830. Patch from
4879 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
4881 - Update manpage to describe some of the files you can expect to
4882 find in Tor's DataDirectory. Addresses ticket 9839.
4883 - Clean up several option names in the manpage to match their real
4884 names, add the missing documentation for a couple of testing and
4885 directory authority options, remove the documentation for a
4886 V2-directory fetching option that no longer exists. Resolves
4888 - Correct the documenation so that it lists the correct directory
4889 for the stats files. (They are in a subdirectory called "stats",
4891 - In the manpage, move more authority-only options into the
4892 directory authority section so that operators of regular directory
4893 caches don't get confused.
4894 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
4895 11061; bugfix on 0.2.4.7-alpha.
4896 - Resolve warnings from Doxygen.
4897 - Document in the manpage that "KBytes" may also be written as
4898 "kilobytes" or "KB", that "Kbits" may also be written as
4899 "kilobits", and so forth. Closes ticket 9222.
4900 - Document that the ClientOnly config option overrides ORPort.
4901 Our old explanation made ClientOnly sound as though it did
4902 nothing at all. Resolves bug 9059.
4903 - Explain that SocksPolicy, DirPolicy, and similar options don't
4904 take port arguments. Fixes the other part of ticket 11108.
4905 - Fix a comment about the rend_server_descriptor_t.protocols field
4906 to more accurately describe its range. Also, make that field
4907 unsigned, to more accurately reflect its usage. Fixes bug 9099;
4908 bugfix on 0.2.1.5-alpha.
4909 - Fix the manpage's description of HiddenServiceAuthorizeClient:
4910 the maximum client name length is 16, not 19. Fixes bug 11118;
4911 bugfix on 0.2.1.6-alpha.
4914 - The contrib directory has been sorted and tidied. Before, it was
4915 an unsorted dumping ground for useful and not-so-useful things.
4916 Now, it is divided based on functionality, and the items which
4917 seemed to be nonfunctional or useless have been removed. Resolves
4918 ticket 8966; based on patches from "rl1987".
4920 o Removed code and features:
4921 - Clients now reject any directory authority certificates lacking
4922 a dir-key-crosscert element. These have been included since
4923 0.2.1.9-alpha, so there's no real reason for them to be optional
4924 any longer. Completes proposal 157. Resolves ticket 10162.
4925 - Remove all code that existed to support the v2 directory system,
4926 since there are no longer any v2 directory authorities. Resolves
4928 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
4929 options, which were used for designating authorities as "Hidden
4930 service authorities". There has been no use of hidden service
4931 authorities since 0.2.2.1-alpha, when we stopped uploading or
4932 downloading v0 hidden service descriptors. Fixes bug 10881; also
4933 part of a fix for bug 10841.
4934 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
4935 and MTBF calculations, but that nobody was using. Fixes bug 11742.
4936 - The TunnelDirConns and PreferTunnelledDirConns options no longer
4937 exist; tunneled directory connections have been available since
4938 0.1.2.5-alpha, and turning them off is not a good idea. This is a
4939 brute-force fix for 10849, where "TunnelDirConns 0" would break
4941 - Remove all code for the long unused v1 directory protocol.
4942 Resolves ticket 11070.
4943 - Remove all remaining code related to version-0 hidden service
4944 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
4945 the rest of bug 10841.
4946 - Remove migration code from when we renamed the "cached-routers"
4947 file to "cached-descriptors" back in 0.2.0.8-alpha. This
4948 incidentally resolves ticket 6502 by cleaning up the related code
4949 a bit. Patch from Akshay Hebbar.
4951 o Test infrastructure:
4952 - Tor now builds each source file in two modes: a mode that avoids
4953 exposing identifiers needlessly, and another mode that exposes
4954 more identifiers for testing. This lets the compiler do better at
4955 optimizing the production code, while enabling us to take more
4956 radical measures to let the unit tests test things.
4957 - The production builds no longer include functions used only in
4958 the unit tests; all functions exposed from a module only for
4959 unit-testing are now static in production builds.
4960 - Add an --enable-coverage configuration option to make the unit
4961 tests (and a new src/or/tor-cov target) to build with gcov test
4963 - Update to the latest version of tinytest.
4964 - Improve the tinytest implementation of string operation tests so
4965 that comparisons with NULL strings no longer crash the tests; they
4966 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
4967 - New macros in test.h to simplify writing mock-functions for unit
4968 tests. Part of ticket 11507. Patch from Dana Koch.
4969 - We now have rudimentary function mocking support that our unit
4970 tests can use to test functions in isolation. Function mocking
4971 lets the tests temporarily replace a function's dependencies with
4972 stub functions, so that the tests can check the function without
4973 invoking the other functions it calls.
4976 - Complete tests for the status.c module. Resolves ticket 11507.
4977 Patch from Dana Koch.
4978 - Add more unit tests for the <circid,channel>->circuit map, and
4979 the destroy-cell-tracking code to fix bug 7912.
4980 - Unit tests for failing cases of the TAP onion handshake.
4981 - More unit tests for address-manipulation functions.
4983 o Distribution (systemd):
4984 - Include a tor.service file in contrib/dist for use with systemd.
4985 Some distributions will be able to use this file unmodified;
4986 others will need to tweak it, or write their own. Patch from Jamie
4987 Nguyen; resolves ticket 8368.
4988 - Verify configuration file via ExecStartPre in the systemd unit
4989 file. Patch from intrigeri; resolves ticket 12730.
4990 - Explicitly disable RunAsDaemon in the systemd unit file. Our
4991 current systemd unit uses "Type = simple", so systemd does not
4992 expect tor to fork. If the user has "RunAsDaemon 1" in their
4993 torrc, then things won't work as expected. This is e.g. the case
4994 on Debian (and derivatives), since there we pass "--defaults-torrc
4995 /usr/share/tor/tor-service-defaults-torrc" (that contains
4996 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
5000 Changes in version 0.2.4.25 - 2014-10-20
5001 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
5002 (even though POODLE does not affect Tor). It also works around a crash
5003 bug caused by some operating systems' response to the "POODLE" attack
5004 (which does affect Tor).
5006 o Major security fixes (also in 0.2.5.9-rc):
5007 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
5008 today support TLS 1.0 or later, so we can safely turn off support
5009 for this old (and insecure) protocol. Fixes bug 13426.
5011 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
5012 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
5013 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
5014 13471. This is a workaround for an OpenSSL bug.
5017 Changes in version 0.2.4.24 - 2014-09-22
5018 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
5019 connecting to hidden services, and it updates the location of one of
5020 the directory authorities.
5023 - Clients now send the correct address for their chosen rendezvous
5024 point when trying to access a hidden service. They used to send
5025 the wrong address, which would still work some of the time because
5026 they also sent the identity digest of the rendezvous point, and if
5027 the hidden service happened to try connecting to the rendezvous
5028 point from a relay that already had a connection open to it,
5029 the relay would reuse that connection. Now connections to hidden
5030 services should be more robust and faster. Also, this bug meant
5031 that clients were leaking to the hidden service whether they were
5032 on a little-endian (common) or big-endian (rare) system, which for
5033 some users might have reduced their anonymity. Fixes bug 13151;
5034 bugfix on 0.2.1.5-alpha.
5036 o Directory authority changes:
5037 - Change IP address for gabelmoo (v3 directory authority).
5039 o Minor features (geoip):
5040 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
5044 Changes in version 0.2.4.23 - 2014-07-28
5045 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
5046 guard rotation, and also backports several important fixes from the
5047 Tor 0.2.5 alpha release series.
5050 - Clients now look at the "usecreatefast" consensus parameter to
5051 decide whether to use CREATE_FAST or CREATE cells for the first hop
5052 of their circuit. This approach can improve security on connections
5053 where Tor's circuit handshake is stronger than the available TLS
5054 connection security levels, but the tradeoff is more computational
5055 load on guard relays. Implements proposal 221. Resolves ticket 9386.
5056 - Make the number of entry guards configurable via a new
5057 NumEntryGuards consensus parameter, and the number of directory
5058 guards configurable via a new NumDirectoryGuards consensus
5059 parameter. Implements ticket 12688.
5062 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
5063 implementation that caused incorrect results on 32-bit
5064 implementations when certain malformed inputs were used along with
5065 a small class of private ntor keys. This bug does not currently
5066 appear to allow an attacker to learn private keys or impersonate a
5067 Tor server, but it could provide a means to distinguish 32-bit Tor
5068 implementations from 64-bit Tor implementations. Fixes bug 12694;
5069 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
5073 - Warn and drop the circuit if we receive an inbound 'relay early'
5074 cell. Those used to be normal to receive on hidden service circuits
5075 due to bug 1038, but the buggy Tor versions are long gone from
5076 the network so we can afford to resume watching for them. Resolves
5077 the rest of bug 1038; bugfix on 0.2.1.19.
5078 - Correct a confusing error message when trying to extend a circuit
5079 via the control protocol but we don't know a descriptor or
5080 microdescriptor for one of the specified relays. Fixes bug 12718;
5081 bugfix on 0.2.3.1-alpha.
5082 - Avoid an illegal read from stack when initializing the TLS
5083 module using a version of OpenSSL without all of the ciphers
5084 used by the v2 link handshake. Fixes bug 12227; bugfix on
5085 0.2.4.8-alpha. Found by "starlight".
5088 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
5092 Changes in version 0.2.4.22 - 2014-05-16
5093 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
5094 alpha release series. These include blocking all authority signing
5095 keys that may have been affected by the OpenSSL "heartbleed" bug,
5096 choosing a far more secure set of TLS ciphersuites by default, closing
5097 a couple of memory leaks that could be used to run a target relay out
5098 of RAM, and several others.
5100 o Major features (security, backport from 0.2.5.4-alpha):
5101 - Block authority signing keys that were used on authorities
5102 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
5103 don't have any evidence that these keys _were_ compromised; we're
5104 doing this to be prudent.) Resolves ticket 11464.
5106 o Major bugfixes (security, OOM):
5107 - Fix a memory leak that could occur if a microdescriptor parse
5108 fails during the tokenizing step. This bug could enable a memory
5109 exhaustion attack by directory servers. Fixes bug 11649; bugfix
5112 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
5113 - The relay ciphersuite list is now generated automatically based on
5114 uniform criteria, and includes all OpenSSL ciphersuites with
5115 acceptable strength and forward secrecy. Previously, we had left
5116 some perfectly fine ciphersuites unsupported due to omission or
5117 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
5118 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
5119 - Relays now trust themselves to have a better view than clients of
5120 which TLS ciphersuites are better than others. (Thanks to bug
5121 11513, the relay list is now well-considered, whereas the client
5122 list has been chosen mainly for anti-fingerprinting purposes.)
5123 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
5124 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
5125 AES128. Resolves ticket 11528.
5126 - Clients now try to advertise the same list of ciphersuites as
5127 Firefox 28. This change enables selection of (fast) GCM
5128 ciphersuites, disables some strange old ciphers, and stops
5129 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
5130 Resolves ticket 11438.
5132 o Minor bugfixes (configuration, security):
5133 - When running a hidden service, do not allow TunneledDirConns 0:
5134 trying to set that option together with a hidden service would
5135 otherwise prevent the hidden service from running, and also make
5136 it publish its descriptors directly over HTTP. Fixes bug 10849;
5137 bugfix on 0.2.1.1-alpha.
5139 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
5140 - Avoid sending a garbage value to the controller when a circuit is
5141 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
5143 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
5144 - Stop leaking memory when we successfully resolve a PTR record.
5145 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
5147 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
5148 - Avoid 60-second delays in the bootstrapping process when Tor is
5149 launching for a second time while using bridges. Fixes bug 9229;
5150 bugfix on 0.2.0.3-alpha.
5152 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
5153 - Give the correct URL in the warning message when trying to run a
5154 relay on an ancient version of Windows. Fixes bug 9393.
5156 o Minor bugfixes (compilation):
5157 - Fix a compilation error when compiling with --disable-curve25519.
5158 Fixes bug 9700; bugfix on 0.2.4.17-rc.
5161 - Downgrade the warning severity for the the "md was still
5162 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
5163 for trying to diagnose this bug, and the current warning in
5164 earlier versions of tor achieves nothing useful. Addresses warning
5167 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
5168 - When we run out of usable circuit IDs on a channel, log only one
5169 warning for the whole channel, and describe how many circuits
5170 there were on the channel. Fixes part of ticket 11553.
5172 o Minor features (security, backport from 0.2.5.4-alpha):
5173 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
5174 leave the default at 8GBytes), to better support Raspberry Pi
5175 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
5177 o Documentation (backport from 0.2.5.4-alpha):
5178 - Correctly document that we search for a system torrc file before
5179 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
5183 Changes in version 0.2.4.21 - 2014-02-28
5184 Tor 0.2.4.21 further improves security against potential adversaries who
5185 find breaking 1024-bit crypto doable, and backports several stability
5186 and robustness patches from the 0.2.5 branch.
5188 o Major features (client security):
5189 - When we choose a path for a 3-hop circuit, make sure it contains
5190 at least one relay that supports the NTor circuit extension
5191 handshake. Otherwise, there is a chance that we're building
5192 a circuit that's worth attacking by an adversary who finds
5193 breaking 1024-bit crypto doable, and that chance changes the game
5194 theory. Implements ticket 9777.
5197 - Do not treat streams that fail with reason
5198 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
5199 since it could also indicate an ENETUNREACH connection error. Fixes
5200 part of bug 10777; bugfix on 0.2.4.8-alpha.
5202 o Code simplification and refactoring:
5203 - Remove data structures which were introduced to implement the
5204 CellStatistics option: they are now redundant with the new timestamp
5205 field in the regular packed_cell_t data structure, which we did
5206 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
5209 - Always clear OpenSSL bignums before freeing them -- even bignums
5210 that don't contain secrets. Resolves ticket 10793. Patch by
5212 - Build without warnings under clang 3.4. (We have some macros that
5213 define static functions only some of which will get used later in
5214 the module. Starting with clang 3.4, these give a warning unless the
5215 unused attribute is set on them.) Resolves ticket 10904.
5216 - Update geoip and geoip6 files to the February 7 2014 Maxmind
5217 GeoLite2 Country database.
5220 - Set the listen() backlog limit to the largest actually supported
5221 on the system, not to the value in a header file. Fixes bug 9716;
5222 bugfix on every released Tor.
5223 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
5224 exit node as a NOROUTE error, not an INTERNAL error, since they
5225 can apparently happen when trying to connect to the wrong sort
5226 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
5227 - Fix build warnings about missing "a2x" comment when building the
5228 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
5229 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
5230 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
5231 not entirely remove it from the connection lists. Fixes bug 9602;
5232 bugfix on 0.2.4.4-alpha.
5233 - Fix a segmentation fault in our benchmark code when running with
5234 Fedora's OpenSSL package, or any other OpenSSL that provides
5235 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
5236 - Turn "circuit handshake stats since last time" log messages into a
5237 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
5239 o Documentation fixes:
5240 - Document that all but one DirPort entry must have the NoAdvertise
5241 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
5244 Changes in version 0.2.4.20 - 2013-12-22
5245 Tor 0.2.4.20 fixes potentially poor random number generation for users
5246 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
5247 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
5248 and 4) have no state file in their DataDirectory (as would happen on
5249 first start). Users who generated relay or hidden service identity
5250 keys in such a situation should discard them and generate new ones.
5252 This release also fixes a logic error that caused Tor clients to build
5253 many more preemptive circuits than they actually need.
5256 - Do not allow OpenSSL engines to replace the PRNG, even when
5257 HardwareAccel is set. The only default builtin PRNG engine uses
5258 the Intel RDRAND instruction to replace the entire PRNG, and
5259 ignores all attempts to seed it with more entropy. That's
5260 cryptographically stupid: the right response to a new alleged
5261 entropy source is never to discard all previously used entropy
5262 sources. Fixes bug 10402; works around behavior introduced in
5263 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
5265 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
5266 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
5267 - Avoid launching spurious extra circuits when a stream is pending.
5268 This fixes a bug where any circuit that _wasn't_ unusable for new
5269 streams would be treated as if it were, causing extra circuits to
5270 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
5273 - Avoid a crash bug when starting with a corrupted microdescriptor
5274 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
5275 - If we fail to dump a previously cached microdescriptor to disk, avoid
5276 freeing duplicate data later on. Fixes bug 10423; bugfix on
5277 0.2.4.13-alpha. Spotted by "bobnomnom".
5280 Changes in version 0.2.4.19 - 2013-12-11
5281 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
5282 (1986-2013). Aaron worked on diverse projects including helping to guide
5283 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
5284 transparency to the U.S government's PACER documents, and contributing
5285 design and development for Tor and Tor2Web. Aaron was one of the latest
5286 martyrs in our collective fight for civil liberties and human rights,
5287 and his death is all the more painful because he was one of us.
5289 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
5290 a new circuit handshake and link encryption that use ECC to provide
5291 better security and efficiency; makes relays better manage circuit
5292 creation requests; uses "directory guards" to reduce client enumeration
5293 risks; makes bridges collect and report statistics about the pluggable
5294 transports they support; cleans up and improves our geoip database;
5295 gets much closer to IPv6 support for clients, bridges, and relays; makes
5296 directory authorities use measured bandwidths rather than advertised
5297 ones when computing flags and thresholds; disables client-side DNS
5298 caching to reduce tracking risks; and fixes a big bug in bridge
5299 reachability testing. This release introduces two new design
5300 abstractions in the code: a new "channel" abstraction between circuits
5301 and or_connections to allow for implementing alternate relay-to-relay
5302 transports, and a new "circuitmux" abstraction storing the queue of
5303 circuits for a channel. The release also includes many stability,
5304 security, and privacy fixes.
5306 o Major features (new circuit handshake):
5307 - Tor now supports a new circuit extension handshake designed by Ian
5308 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
5309 circuit extension handshake, later called "TAP", was a bit slow
5310 (especially on the relay side), had a fragile security proof, and
5311 used weaker keys than we'd now prefer. The new circuit handshake
5312 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
5313 function, making it significantly more secure than the older
5314 handshake, and significantly faster. Tor can use one of two built-in
5315 pure-C curve25519-donna implementations by Adam Langley, or it
5316 can link against the "nacl" library for a tuned version if present.
5318 The built-in version is very fast for 64-bit systems when building
5319 with GCC. The built-in 32-bit version is still faster than the
5320 old TAP protocol, but using libnacl is better on most such hosts.
5322 Implements proposal 216; closes ticket 7202.
5324 o Major features (better link encryption):
5325 - Relays can now enable the ECDHE TLS ciphersuites when available
5326 and appropriate. These ciphersuites let us negotiate forward-secure
5327 TLS secret keys more safely and more efficiently than with our
5328 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
5329 public relays prefer the (faster) P224 group, and bridges prefer
5330 the (more common) P256 group; you can override this with the
5333 This feature requires clients running 0.2.3.17-beta or later,
5334 and requires both sides to be running OpenSSL 1.0.0 or later
5335 with ECC support. OpenSSL 1.0.1, with the compile-time option
5336 "enable-ec_nistp_64_gcc_128", is highly recommended.
5338 Implements the relay side of proposal 198; closes ticket 7200.
5340 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
5341 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
5342 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
5343 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
5344 them to solve bug 6033.)
5346 o Major features (relay performance):
5347 - Instead of limiting the number of queued onionskins (aka circuit
5348 create requests) to a fixed, hard-to-configure number, we limit
5349 the size of the queue based on how many we expect to be able to
5350 process in a given amount of time. We estimate the time it will
5351 take to process an onionskin based on average processing time
5352 of previous onionskins. Closes ticket 7291. You'll never have to
5353 configure MaxOnionsPending again.
5354 - Relays process the new "NTor" circuit-level handshake requests
5355 with higher priority than the old "TAP" circuit-level handshake
5356 requests. We still process some TAP requests to not totally starve
5357 0.2.3 clients when NTor becomes popular. A new consensus parameter
5358 "NumNTorsPerTAP" lets us tune the balance later if we need to.
5359 Implements ticket 9574.
5361 o Major features (client bootstrapping resilience):
5362 - Add a new "FallbackDir" torrc option to use when we can't use
5363 a directory mirror from the consensus (either because we lack a
5364 consensus, or because they're all down). Currently, all authorities
5365 are fallbacks by default, and there are no other default fallbacks,
5366 but that will change. This option will allow us to give clients a
5367 longer list of servers to try to get a consensus from when first
5368 connecting to the Tor network, and thereby reduce load on the
5369 directory authorities. Implements proposal 206, "Preconfigured
5370 directory sources for bootstrapping". We also removed the old
5371 "FallbackNetworkstatus" option, since we never got it working well
5372 enough to use it. Closes bug 572.
5373 - If we have no circuits open, use a relaxed timeout (the
5374 95th-percentile cutoff) until a circuit succeeds. This heuristic
5375 should allow Tor to succeed at building circuits even when the
5376 network connection drastically changes. Should help with bug 3443.
5378 o Major features (use of guards):
5379 - Support directory guards (proposal 207): when possible, clients now
5380 use their entry guards for non-anonymous directory requests. This
5381 can help prevent client enumeration. Note that this behavior only
5382 works when we have a usable consensus directory, and when options
5383 about what to download are more or less standard. In the future we
5384 should re-bootstrap from our guards, rather than re-bootstrapping
5385 from the preconfigured list of directory sources that ships with
5386 Tor. Resolves ticket 6526.
5387 - Raise the default time that a client keeps an entry guard from
5388 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
5389 2012 paper. (We would make it even longer, but we need better client
5390 load balancing first.) Also, make the guard lifetime controllable
5391 via a new GuardLifetime torrc option and a GuardLifetime consensus
5392 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
5394 o Major features (bridges with pluggable transports):
5395 - Bridges now report the pluggable transports they support to the
5396 bridge authority, so it can pass the supported transports on to
5397 bridgedb and/or eventually do reachability testing. Implements
5399 - Automatically forward the TCP ports of pluggable transport
5400 proxies using tor-fw-helper if PortForwarding is enabled. Implements
5403 o Major features (geoip database):
5404 - Maxmind began labelling Tor relays as being in country "A1",
5405 which breaks by-country node selection inside Tor. Now we use a
5406 script to replace "A1" ("Anonymous Proxy") entries in our geoip
5407 file with real country codes. This script fixes about 90% of "A1"
5408 entries automatically and uses manual country code assignments to
5409 fix the remaining 10%. See src/config/README.geoip for details.
5411 - Add GeoIP database for IPv6 addresses. The new config option
5413 - Update to the October 2 2013 Maxmind GeoLite Country database.
5415 o Major features (IPv6):
5416 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
5417 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
5418 to happen. Implements ticket 5535.
5419 - All kind of relays, not just bridges, can now advertise an IPv6
5420 OR port. Implements ticket 6362.
5421 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
5422 connectivity, then set the IPv6Exit flag to 1. Also make sure your
5423 exit policy reads as you would like: the address * applies to all
5424 address families, whereas *4 is IPv4 address only, and *6 is IPv6
5425 addresses only. On the client side, you'll need to wait for enough
5426 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
5427 and use Socks5. Closes ticket 5547, implements proposal 117 as
5428 revised in proposal 208.
5429 - Bridge authorities now accept IPv6 bridge addresses and include
5430 them in network status documents. Implements ticket 5534.
5431 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
5433 o Major features (directory authorities):
5434 - Directory authorities now prefer using measured bandwidths to
5435 advertised ones when computing flags and thresholds. Resolves
5437 - Directory authorities that vote measured bandwidths about more
5438 than a threshold number of relays now treat relays with
5439 unmeasured bandwidths as having bandwidth 0 when computing their
5440 flags. Resolves ticket 8435.
5441 - Directory authorities now support a new consensus method (17)
5442 where they cap the published bandwidth of relays for which
5443 insufficient bandwidth measurements exist. Fixes part of bug 2286.
5444 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
5445 serve any v2 directory information. Now we can test disabling the
5446 old deprecated v2 directory format, and see whether doing so has
5447 any effect on network load. Begins to fix bug 6783.
5449 o Major features (build and portability):
5450 - Switch to a nonrecursive Makefile structure. Now instead of each
5451 Makefile.am invoking other Makefile.am's, there is a master
5452 Makefile.am that includes the others. This change makes our build
5453 process slightly more maintainable, and improves parallelism for
5454 building with make -j. Original patch by Stewart Smith; various
5455 fixes by Jim Meyering.
5456 - Where available, we now use automake's "silent" make rules by
5457 default, so that warnings are easier to spot. You can get the old
5458 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
5459 - Resume building correctly with MSVC and Makefile.nmake. This patch
5460 resolves numerous bugs and fixes reported by ultramage, including
5461 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
5463 o Security features:
5464 - Switch to a completely time-invariant approach for picking nodes
5465 weighted by bandwidth. Our old approach would run through the
5466 part of the loop after it had made its choice slightly slower
5467 than it ran through the part of the loop before it had made its
5468 choice. Addresses ticket 6538.
5469 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
5470 by tor2web clients allows hidden services to identify tor2web
5471 clients through their repeated selection of the same rendezvous
5472 and introduction point circuit endpoints (their guards). Resolves
5475 o Major bugfixes (relay denial of service):
5476 - When we have too much memory queued in circuits (according to a new
5477 MaxMemInCellQueues option), close the circuits that have the oldest
5478 queued cells, on the theory that those are most responsible for
5479 us running low on memory. This prevents us from running out of
5480 memory as a relay if circuits fill up faster than they can be
5481 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
5482 Tor. This bug is a further fix beyond bug 6252, whose fix was
5483 merged into 0.2.3.21-rc.
5484 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
5485 ID: these could be used to create unexpected streams and circuits
5486 which would count as "present" to some parts of Tor but "absent"
5487 to others, leading to zombie circuits and streams or to a bandwidth
5488 denial-of-service. Fixes bug 7889; bugfix on every released version
5489 of Tor. Reported by "oftc_must_be_destroyed".
5490 - Avoid a bug where our response to TLS renegotiation under certain
5491 network conditions could lead to a busy-loop, with 100% CPU
5492 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
5494 o Major bugfixes (asserts, crashes, leaks):
5495 - Prevent the get_freelists() function from running off the end of
5496 the list of freelists if it somehow gets an unrecognized
5497 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
5499 - Avoid a memory leak where we would leak a consensus body when we
5500 find that a consensus which we couldn't previously verify due to
5501 missing certificates is now verifiable. Fixes bug 8719; bugfix
5503 - If we are unable to save a microdescriptor to the journal, do not
5504 drop it from memory and then reattempt downloading it. Fixes bug
5505 9645; bugfix on 0.2.2.6-alpha.
5506 - Fix an assertion failure that would occur when disabling the
5507 ORPort setting on a running Tor process while accounting was
5508 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
5509 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
5510 when an exit connection with optimistic data succeeds immediately
5511 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
5513 - Fix a memory leak that would occur whenever a configuration
5514 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
5516 o Major bugfixes (relay rate limiting):
5517 - When a TLS write is partially successful but incomplete, remember
5518 that the flushed part has been flushed, and notice that bytes were
5519 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
5520 bugfix on Tor 0.1.0.5-rc.
5521 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
5522 to 1GB/1GB. The previous defaults were intended to be "basically
5523 infinite", but it turns out they're now limiting our 100mbit+
5524 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
5525 last time we raised it).
5526 - No longer stop reading or writing on cpuworker connections when
5527 our rate limiting buckets go empty. Now we should handle circuit
5528 handshake requests more promptly. Resolves bug 9731.
5530 o Major bugfixes (client-side privacy):
5531 - When we mark a circuit as unusable for new circuits, have it
5532 continue to be unusable for new circuits even if MaxCircuitDirtiness
5533 is increased too much at the wrong time, or the system clock jumps
5534 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
5535 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
5536 which have resolved to internal addresses") is set, apply that
5537 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
5538 - When an exit relay rejects a stream with reason "exit policy", but
5539 we only know an exit policy summary (e.g. from the microdesc
5540 consensus) for it, do not mark the relay as useless for all exiting.
5541 Instead, mark just the circuit as unsuitable for that particular
5542 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
5544 o Major bugfixes (stream isolation):
5545 - Allow applications to get proper stream isolation with
5546 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
5547 username/password authentication also offer "no authentication". Tor
5548 had previously preferred "no authentication", so the applications
5549 never actually sent Tor their auth details. Now Tor selects
5550 username/password authentication if it's offered. You can disable
5551 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
5552 bug 8117; bugfix on 0.2.3.3-alpha.
5553 - Follow the socks5 protocol when offering username/password
5554 authentication. The fix for bug 8117 exposed this bug, and it
5555 turns out real-world applications like Pidgin do care. Bugfix on
5556 0.2.3.2-alpha; fixes bug 8879.
5558 o Major bugfixes (client circuit building):
5559 - Alter circuit build timeout measurement to start at the point
5560 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
5561 initialization). This should make our timeout measurements more
5562 uniform. Previously, we were sometimes including ORconn setup time
5563 in our circuit build time measurements. Should resolve bug 3443.
5564 - If the circuit build timeout logic is disabled (via the consensus,
5565 or because we are an authority), then don't build testing circuits.
5566 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
5568 o Major bugfixes (client-side DNS):
5569 - Turn off the client-side DNS cache by default. Updating and using
5570 the DNS cache is now configurable on a per-client-port
5571 level. SOCKSPort, DNSPort, etc lines may now contain
5572 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
5573 cache these types of DNS answers when we receive them from an
5574 exit node in response to an application request on this port, and
5575 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
5576 cached DNS answers of these types, we shouldn't use them. It's
5577 potentially risky to use cached DNS answers at the client, since
5578 doing so can indicate to one exit what answers we've gotten
5579 for DNS lookups in the past. With IPv6, this becomes especially
5580 problematic. Using cached DNS answers for requests on the same
5581 circuit would present less linkability risk, since all traffic
5582 on a circuit is already linkable, but it would also provide
5583 little performance benefit: the exit node caches DNS replies
5584 too. Implements a simplified version of Proposal 205. Implements
5587 o Major bugfixes (hidden service privacy):
5588 - Limit hidden service descriptors to at most ten introduction
5589 points, to slow one kind of guard enumeration. Fixes bug 9002;
5590 bugfix on 0.1.1.11-alpha.
5592 o Major bugfixes (directory fetching):
5593 - If the time to download the next old-style networkstatus is in
5594 the future, do not decline to consider whether to download the
5595 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
5597 - We used to always request authority certificates by identity digest,
5598 meaning we'd get the newest one even when we wanted one with a
5599 different signing key. Then we would complain about being given
5600 a certificate we already had, and never get the one we really
5601 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
5602 resource to request the one we want. Fixes bug 5595; bugfix on
5605 o Major bugfixes (bridge reachability):
5606 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
5607 previously they did not, which prevented them from receiving
5608 successful connections from relays for self-test or bandwidth
5609 testing. Also, when a relay is extending a circuit to a bridge,
5610 it needs to send a NETINFO cell, even when the bridge hasn't sent
5611 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
5613 o Major bugfixes (control interface):
5614 - When receiving a new configuration file via the control port's
5615 LOADCONF command, do not treat the defaults file as absent.
5616 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
5618 o Major bugfixes (directory authorities):
5619 - Stop marking every relay as having been down for one hour every
5620 time we restart a directory authority. These artificial downtimes
5621 were messing with our Stable and Guard flag calculations. Fixes
5622 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
5623 - When computing directory thresholds, ignore any rejected-as-sybil
5624 nodes during the computation so that they can't influence Fast,
5625 Guard, etc. (We should have done this for proposal 109.) Fixes
5627 - When marking a node as a likely sybil, reset its uptime metrics
5628 to zero, so that it cannot time towards getting marked as Guard,
5629 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
5631 - Fix a bug in the voting algorithm that could yield incorrect results
5632 when a non-naming authority declared too many flags. Fixes bug 9200;
5633 bugfix on 0.2.0.3-alpha.
5635 o Internal abstraction features:
5636 - Introduce new channel_t abstraction between circuits and
5637 or_connection_t to allow for implementing alternate OR-to-OR
5638 transports. A channel_t is an abstract object which can either be a
5639 cell-bearing channel, which is responsible for authenticating and
5640 handshaking with the remote OR and transmitting cells to and from
5641 it, or a listening channel, which spawns new cell-bearing channels
5642 at the request of remote ORs. Implements part of ticket 6465.
5643 - Make a channel_tls_t subclass of channel_t, adapting it to the
5644 existing or_connection_t code. The V2/V3 protocol handshaking
5645 code which formerly resided in command.c has been moved below the
5646 channel_t abstraction layer and may be found in channeltls.c now.
5647 Implements the rest of ticket 6465.
5648 - Introduce new circuitmux_t storing the queue of circuits for
5649 a channel; this encapsulates and abstracts the queue logic and
5650 circuit selection policy, and allows the latter to be overridden
5651 easily by switching out a policy object. The existing EWMA behavior
5652 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
5654 o New build requirements:
5655 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
5656 strongly recommended.
5657 - Tor maintainers now require Automake version 1.9 or later to build
5658 Tor from the Git repository. (Automake is not required when building
5659 from a source distribution.)
5661 o Minor features (protocol):
5662 - No longer include the "opt" prefix when generating routerinfos
5663 or v2 directories: it has been needless since Tor 0.1.2. Closes
5665 - Reject EXTEND cells sent to nonexistent streams. According to the
5666 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
5667 we were only checking for stream IDs that were currently in use.
5668 Found while hunting for more instances of bug 6271. Bugfix on
5669 0.0.2pre8, which introduced incremental circuit construction.
5670 - Tor relays and clients now support a better CREATE/EXTEND cell
5671 format, allowing the sender to specify multiple address, identity,
5672 and handshake types. Implements Robert Ransom's proposal 200;
5674 - Reject as invalid most directory objects containing a NUL.
5675 Belt-and-suspender fix for bug 8037.
5677 o Minor features (security):
5678 - Clear keys and key-derived material left on the stack in
5679 rendservice.c and rendclient.c. Check return value of
5680 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
5681 These fixes should make us more forward-secure against cold-boot
5682 attacks and the like. Fixes bug 2385.
5683 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
5684 Irix's random() only return 15 bits; Solaris's random() returns more
5685 bits but its RAND_MAX says it only returns 15, and so on. Motivated
5686 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
5688 o Minor features (control protocol):
5689 - Add a "GETINFO signal/names" control port command. Implements
5691 - Provide default values for all options via "GETINFO config/defaults".
5692 Implements ticket 4971.
5693 - Allow an optional $ before the node identity digest in the
5694 controller command GETINFO ns/id/<identity>, for consistency with
5695 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
5696 - Add CACHED keyword to ADDRMAP events in the control protocol
5697 to indicate whether a DNS result will be cached or not. Resolves
5699 - Generate bootstrapping status update events correctly when fetching
5700 microdescriptors. Fixes bug 9927.
5702 o Minor features (path selection):
5703 - When deciding whether we have enough descriptors to build circuits,
5704 instead of looking at raw relay counts, look at which fraction
5705 of (bandwidth-weighted) paths we're able to build. This approach
5706 keeps clients from building circuits if their paths are likely to
5707 stand out statistically. The default fraction of paths needed is
5708 taken from the consensus directory; you can override it with the
5709 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
5710 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
5711 and we have GeoIP information, also exclude all nodes with unknown
5712 countries "??" and "A1". This behavior is controlled by the
5713 new GeoIPExcludeUnknown option: you can make such nodes always
5714 excluded with "GeoIPExcludeUnknown 1", and disable the feature
5715 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
5716 gets you the default behavior. Implements feature 7706.
5718 o Minor features (hidden services):
5719 - Improve circuit build timeout handling for hidden services.
5720 In particular: adjust build timeouts more accurately depending
5721 upon the number of hop-RTTs that a particular circuit type
5722 undergoes. Additionally, launch intro circuits in parallel
5723 if they timeout, and take the first one to reply as valid.
5724 - The Tor client now ignores sub-domain components of a .onion
5725 address. This change makes HTTP "virtual" hosting
5726 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
5727 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
5728 hosted on the same hidden service. Implements proposal 204.
5729 - Enable Tor to read configuration, state, and key information from
5730 a FIFO. Previously Tor would only read from files with a positive
5731 stat.st_size. Code from meejah; fixes bug 6044.
5733 o Minor features (clients):
5734 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
5735 microdescriptor-related dir requests, and only fall back to normal
5736 descriptors if none of their bridges can handle microdescriptors
5737 (as opposed to the fix in ticket 4013, which caused them to fall
5738 back to normal descriptors if *any* of their bridges preferred
5739 them). Resolves ticket 4994.
5740 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
5741 TCP ports to forward. In the past it only accepted two ports:
5742 the ORPort and the DirPort.
5744 o Minor features (protecting client timestamps):
5745 - Clients no longer send timestamps in their NETINFO cells. These were
5746 not used for anything, and they provided one small way for clients
5747 to be distinguished from each other as they moved from network to
5748 network or behind NAT. Implements part of proposal 222.
5749 - Clients now round timestamps in INTRODUCE cells down to the nearest
5750 10 minutes. If a new Support022HiddenServices option is set to 0, or
5751 if it's set to "auto" and the feature is disabled in the consensus,
5752 the timestamp is sent as 0 instead. Implements part of proposal 222.
5753 - Stop sending timestamps in AUTHENTICATE cells. This is not such
5754 a big deal from a security point of view, but it achieves no actual
5755 good purpose, and isn't needed. Implements part of proposal 222.
5756 - Reduce down accuracy of timestamps in hidden service descriptors.
5757 Implements part of proposal 222.
5759 o Minor features (bridges):
5760 - Make bridge relays check once a minute for whether their IP
5761 address has changed, rather than only every 15 minutes. Resolves
5763 - Bridge statistics now count bridge clients connecting over IPv6:
5764 bridge statistics files now list "bridge-ip-versions" and
5765 extra-info documents list "geoip6-db-digest". The control protocol
5766 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
5767 implementation by "shkoo", addressing ticket 5055.
5768 - Add a new torrc option "ServerTransportListenAddr" to let bridge
5769 operators select the address where their pluggable transports will
5770 listen for connections. Resolves ticket 7013.
5771 - Randomize the lifetime of our SSL link certificate, so censors can't
5772 use the static value for filtering Tor flows. Resolves ticket 8443;
5773 related to ticket 4014 which was included in 0.2.2.33.
5775 o Minor features (relays):
5776 - Option OutboundBindAddress can be specified multiple times and
5777 accepts IPv6 addresses. Resolves ticket 6876.
5779 o Minor features (IPv6, client side):
5780 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
5781 prefer to hand out virtual IPv6 addresses, since there are more of
5782 them and we can't run out. To override this behavior and make IPv4
5783 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
5784 or DNSPort you're using for resolving. Implements ticket 7571.
5785 - AutomapHostsOnResolve responses are now randomized, to avoid
5786 annoying situations where Tor is restarted and applications
5787 connect to the wrong addresses.
5788 - Never try more than 1000 times to pick a new virtual address when
5789 AutomapHostsOnResolve is set. That's good enough so long as we
5790 aren't close to handing out our entire virtual address space;
5791 if you're getting there, it's best to switch to IPv6 virtual
5794 o Minor features (IPv6, relay/authority side):
5795 - New config option "AuthDirHasIPv6Connectivity 1" that directory
5796 authorities should set if they have IPv6 connectivity and want to
5797 do reachability tests for IPv6 relays. Implements feature 5974.
5798 - A relay with an IPv6 OR port now sends that address in NETINFO
5799 cells (in addition to its other address). Implements ticket 6364.
5801 o Minor features (directory authorities):
5802 - Directory authorities no long accept descriptors for any version of
5803 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
5804 These versions are insecure, unsupported, or both. Implements
5806 - When directory authorities are computing thresholds for flags,
5807 never let the threshold for the Fast flag fall below 4096
5808 bytes. Also, do not consider nodes with extremely low bandwidths
5809 when deciding thresholds for various directory flags. This change
5810 should raise our threshold for Fast relays, possibly in turn
5811 improving overall network performance; see ticket 1854. Resolves
5813 - Directory authorities now include inside each vote a statement of
5814 the performance thresholds they used when assigning flags.
5815 Implements ticket 8151.
5816 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
5817 in directory authority votes to describe whether they have enough
5818 measured bandwidths to ignore advertised (relay descriptor)
5819 bandwidth claims. Resolves ticket 8711.
5821 o Minor features (path bias detection):
5822 - Path Use Bias: Perform separate accounting for successful circuit
5823 use. Keep separate statistics on stream attempt rates versus stream
5824 success rates for each guard. Provide configurable thresholds to
5825 determine when to emit log messages or disable use of guards that
5826 fail too many stream attempts. Resolves ticket 7802.
5827 - Create three levels of Path Bias log messages, as opposed to just
5828 two. These are configurable via consensus as well as via the torrc
5829 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
5830 The default values are 0.70, 0.50, and 0.30 respectively.
5831 - Separate the log message levels from the decision to drop guards,
5832 which also is available via torrc option PathBiasDropGuards.
5833 PathBiasDropGuards still defaults to 0 (off).
5834 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
5835 in combination with PathBiasExtremeRate.
5836 - Increase the default values for PathBiasScaleThreshold and
5837 PathBiasCircThreshold from (200, 20) to (300, 150).
5838 - Add in circuit usage accounting to path bias. If we try to use a
5839 built circuit but fail for any reason, it counts as path bias.
5840 Certain classes of circuits where the adversary gets to pick your
5841 destination node are exempt from this accounting. Usage accounting
5842 can be specifically disabled via consensus parameter or torrc.
5843 - Convert all internal path bias state to double-precision floating
5844 point, to avoid roundoff error and other issues.
5845 - Only record path bias information for circuits that have completed
5846 *two* hops. Assuming end-to-end tagging is the attack vector, this
5847 makes us more resilient to ambient circuit failure without any
5848 detection capability loss.
5850 o Minor features (build):
5851 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
5852 dhill. Resolves ticket 6982.
5853 - Compile on win64 using mingw64. Fixes bug 7260; patches from
5855 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
5856 separate error codes; or at least, don't break for that reason.
5857 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
5859 o Build improvements (autotools):
5860 - Warn if building on a platform with an unsigned time_t: there
5861 are too many places where Tor currently assumes that time_t can
5862 hold negative values. We'd like to fix them all, but probably
5864 - Do not report status verbosely from autogen.sh unless the -v flag
5865 is specified. Fixes issue 4664. Patch from Onizuka.
5866 - Detect and reject attempts to build Tor with threading support
5867 when OpenSSL has been compiled without threading support.
5869 - Try to detect if we are ever building on a platform where
5870 memset(...,0,...) does not set the value of a double to 0.0. Such
5871 platforms are permitted by the C standard, though in practice
5872 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
5873 currently support them, but it's better to detect them and fail
5874 than to perform erroneously.
5875 - We no longer warn so much when generating manpages from their
5877 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
5878 the signs of types during autoconf. This is better than our old
5879 approach, which didn't work when cross-compiling.
5881 o Minor features (log messages, warnings):
5882 - Detect when we're running with a version of OpenSSL other than the
5883 one we compiled with. This conflict has occasionally given people
5884 hard-to-track-down errors.
5885 - Warn users who run hidden services on a Tor client with
5886 UseEntryGuards disabled that their hidden services will be
5887 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
5888 attack which motivated Tor to support entry guards in the first
5889 place). Resolves ticket 6889.
5890 - Warn when we are binding low ports when hibernation is enabled;
5891 previously we had warned when we were _advertising_ low ports with
5892 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
5893 - Issue a warning when running with the bufferevents backend enabled.
5894 It's still not stable, and people should know that they're likely
5895 to hit unexpected problems. Closes ticket 9147.
5897 o Minor features (log messages, notices):
5898 - Refactor resolve_my_address() so it returns the method by which we
5899 decided our public IP address (explicitly configured, resolved from
5900 explicit hostname, guessed from interfaces, learned by gethostname).
5901 Now we can provide more helpful log messages when a relay guesses
5902 its IP address incorrectly (e.g. due to unexpected lines in
5903 /etc/hosts). Resolves ticket 2267.
5904 - Track how many "TAP" and "NTor" circuit handshake requests we get,
5905 and how many we complete, and log it every hour to help relay
5906 operators follow trends in network load. Addresses ticket 9658.
5908 o Minor features (log messages, diagnostics):
5909 - If we fail to free a microdescriptor because of bug 7164, log
5910 the filename and line number from which we tried to free it.
5911 - We compute the overhead from passing onionskins back and forth to
5912 cpuworkers, and report it when dumping statistics in response to
5913 SIGUSR1. Supports ticket 7291.
5914 - Add another diagnostic to the heartbeat message: track and log
5915 overhead that TLS is adding to the data we write. If this is
5916 high, we are sending too little data to SSL_write at a time.
5917 Diagnostic for bug 7707.
5918 - Log packaged cell fullness as part of the heartbeat message.
5919 Diagnosis to try to determine the extent of bug 7743.
5920 - Add more detail to a log message about relaxed timeouts, to help
5922 - When learning a fingerprint for a bridge, log its corresponding
5923 transport type. Implements ticket 7896.
5924 - Warn more aggressively when flushing microdescriptors to a
5925 microdescriptor cache fails, in an attempt to mitigate bug 8031,
5926 or at least make it more diagnosable.
5927 - Improve the log message when "Bug/attack: unexpected sendme cell
5928 from client" occurs, to help us track bug 8093.
5929 - Improve debugging output to help track down bug 8185 ("Bug:
5930 outgoing relay cell has n_chan==NULL. Dropping.")
5932 o Minor features (log messages, quieter bootstrapping):
5933 - Log fewer lines at level "notice" about our OpenSSL and Libevent
5934 versions and capabilities when everything is going right. Resolves
5935 part of ticket 6736.
5936 - Omit the first heartbeat log message, because it never has anything
5937 useful to say, and it clutters up the bootstrapping messages.
5938 Resolves ticket 6758.
5939 - Don't log about reloading the microdescriptor cache at startup. Our
5940 bootstrap warnings are supposed to tell the user when there's a
5941 problem, and our bootstrap notices say when there isn't. Resolves
5942 ticket 6759; bugfix on 0.2.2.6-alpha.
5943 - Don't log "I learned some more directory information" when we're
5944 reading cached directory information. Reserve it for when new
5945 directory information arrives in response to a fetch. Resolves
5947 - Don't complain about bootstrapping problems while hibernating.
5948 These complaints reflect a general code problem, but not one
5949 with any problematic effects (no connections are actually
5950 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
5952 o Minor features (testing):
5953 - In our testsuite, create temporary directories with a bit more
5954 entropy in their name to make name collisions less likely. Fixes
5956 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
5957 (P-256) Diffie-Hellman handshakes to src/or/bench.
5958 - Add benchmark functions to test onion handshake performance.
5961 - The DirServer option is now DirAuthority, for consistency with
5962 current naming patterns. You can still use the old DirServer form.
5964 o Minor bugfixes (protocol):
5965 - Fix the handling of a TRUNCATE cell when it arrives while the
5966 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
5967 - When a Tor client gets a "truncated" relay cell, the first byte of
5968 its payload specifies why the circuit was truncated. We were
5969 ignoring this 'reason' byte when tearing down the circuit, resulting
5970 in the controller not being told why the circuit closed. Now we
5971 pass the reason from the truncated cell to the controller. Bugfix
5972 on 0.1.2.3-alpha; fixes bug 7039.
5973 - Fix a misframing issue when reading the version numbers in a
5974 VERSIONS cell. Previously we would recognize [00 01 00 02] as
5975 'version 1, version 2, and version 0x100', when it should have
5976 only included versions 1 and 2. Fixes bug 8059; bugfix on
5977 0.2.0.10-alpha. Reported pseudonymously.
5978 - Make the format and order of STREAM events for DNS lookups
5979 consistent among the various ways to launch DNS lookups. Fixes
5980 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
5982 o Minor bugfixes (syscalls and disk interaction):
5983 - Always check the return values of functions fcntl() and
5984 setsockopt(). We don't believe these are ever actually failing in
5985 practice, but better safe than sorry. Also, checking these return
5986 values should please analysis tools like Coverity. Patch from
5987 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
5988 - Avoid double-closing the listener socket in our socketpair()
5989 replacement (used on Windows) in the case where the addresses on
5990 our opened sockets don't match what we expected. Fixes bug 9400;
5991 bugfix on 0.0.2pre7. Found by Coverity.
5992 - Correctly store microdescriptors and extrainfo descriptors that
5993 include an internal NUL byte. Fixes bug 8037; bugfix on
5994 0.2.0.1-alpha. Bug reported by "cypherpunks".
5995 - If for some reason we fail to write a microdescriptor while
5996 rebuilding the cache, do not let the annotations from that
5997 microdescriptor linger in the cache file, and do not let the
5998 microdescriptor stay recorded as present in its old location.
5999 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
6000 - Use direct writes rather than stdio when building microdescriptor
6001 caches, in an attempt to mitigate bug 8031, or at least make it
6004 o Minor fixes (config options):
6005 - Warn and fail if a server is configured not to advertise any
6006 ORPorts at all. (We need *something* to put in our descriptor,
6007 or we just won't work.)
6008 - Behave correctly when the user disables LearnCircuitBuildTimeout
6009 but doesn't tell us what they would like the timeout to be. Fixes
6010 bug 6304; bugfix on 0.2.2.14-alpha.
6011 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
6012 to start with a triple-underscore so the controller won't touch it.
6013 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
6014 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
6015 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
6016 - When autodetecting the number of CPUs, use the number of available
6017 CPUs in preference to the number of configured CPUs. Inform the
6018 user if this reduces the number of available CPUs. Fixes bug 8002;
6019 bugfix on 0.2.3.1-alpha.
6020 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
6021 - Make it an error when you set EntryNodes but disable UseGuardNodes,
6022 since it will (surprisingly to some users) ignore EntryNodes. Fixes
6023 bug 8180; bugfix on 0.2.3.11-alpha.
6024 - Avoid overflows when the user sets MaxCircuitDirtiness to a
6025 ridiculously high value, by imposing a (ridiculously high) 30-day
6026 maximum on MaxCircuitDirtiness.
6028 o Minor bugfixes (control protocol):
6029 - Stop sending a stray "(null)" in some cases for the server status
6030 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
6032 - The ADDRMAP command can no longer generate an ill-formed error
6033 code on a failed MAPADDRESS. It now says "internal" rather than
6034 an English sentence fragment with spaces in the middle. Bugfix on
6037 o Minor bugfixes (clients / edges):
6038 - When we receive a RELAY_END cell with the reason DONE, or with no
6039 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
6040 status as "connection refused". Previously we reported these cases
6041 as success but then immediately closed the connection. Fixes bug
6042 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
6043 - If the guard we choose first doesn't answer, we would try the
6044 second guard, but once we connected to the second guard we would
6045 abandon it and retry the first one, slowing down bootstrapping.
6046 The fix is to treat all our initially chosen guards as acceptable
6047 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
6048 - When choosing which stream on a formerly stalled circuit to wake
6049 first, make better use of the platform's weak RNG. Previously,
6050 we had been using the % ("modulo") operator to try to generate a
6051 1/N chance of picking each stream, but this behaves badly with
6052 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
6055 o Minor bugfixes (path bias detection):
6056 - If the state file's path bias counts are invalid (presumably from a
6057 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
6058 additional checks and log messages to the scaling of Path Bias
6059 counts, in case there still are remaining issues with scaling.
6060 Should help resolve bug 8235.
6061 - Prevent rounding error in path bias counts when scaling
6062 them down, and use the correct scale factor default. Also demote
6063 some path bias related log messages down a level and make others
6064 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
6065 - Remove a source of rounding error during path bias count scaling;
6066 don't count cannibalized circuits as used for path bias until we
6067 actually try to use them; and fix a circuit_package_relay_cell()
6068 warning message about n_chan==NULL. Fixes bug 7802.
6069 - Paste the description for PathBias parameters from the man
6070 page into or.h, so the code documents them too. Fixes bug 7982;
6071 bugfix on 0.2.3.17-beta.
6073 o Minor bugfixes (relays):
6074 - Stop trying to resolve our hostname so often (e.g. every time we
6075 think about doing a directory fetch). Now we reuse the cached
6076 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
6077 and 2410 (bugfix on 0.1.2.2-alpha).
6078 - When examining the list of network interfaces to find our address,
6079 do not consider non-running or disabled network interfaces. Fixes
6080 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
6082 o Minor bugfixes (blocking resistance):
6083 - Only disable TLS session ticket support when running as a TLS
6084 server. Now clients will blend better with regular Firefox
6085 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
6087 o Minor bugfixes (IPv6):
6088 - Use square brackets around IPv6 addresses in numerous places
6089 that needed them, including log messages, HTTPS CONNECT proxy
6090 requests, TransportProxy statefile entries, and pluggable transport
6091 extra-info lines. Fixes bug 7011; patch by David Fifield.
6093 o Minor bugfixes (directory authorities):
6094 - Reject consensus votes with more than 64 known-flags. We aren't even
6095 close to that limit yet, and our code doesn't handle it correctly.
6096 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
6097 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
6098 bugfix on 0.2.0.3-alpha.
6100 o Minor bugfixes (memory leaks):
6101 - Avoid leaking memory if we fail to compute a consensus signature
6102 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
6103 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
6104 on 0.2.1.1-alpha; fixes bug 7816.
6105 - Fix a memory leak during safe-cookie controller authentication.
6106 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
6107 - Free some more still-in-use memory at exit, to make hunting for
6108 memory leaks easier. Resolves bug 7029.
6110 o Minor bugfixes (code correctness):
6111 - Increase the width of the field used to remember a connection's
6112 link protocol version to two bytes. Harmless for now, since the
6113 only currently recognized versions are one byte long. Reported
6114 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
6115 - Fix a crash when debugging unit tests on Windows: deallocate a
6116 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
6117 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
6118 - When detecting the largest possible file descriptor (in order to
6119 close all file descriptors when launching a new program), actually
6120 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
6121 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
6123 - Avoid a crash if we fail to generate an extrainfo descriptor.
6124 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
6126 - Avoid an off-by-one error when checking buffer boundaries when
6127 formatting the exit status of a pluggable transport helper.
6128 This is probably not an exploitable bug, but better safe than
6129 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
6131 - Get rid of a couple of harmless clang warnings, where we compared
6132 enums to ints. These warnings are newly introduced in clang 3.2.
6134 o Minor bugfixes (code cleanliness):
6135 - Avoid use of reserved identifiers in our C code. The C standard
6136 doesn't like us declaring anything that starts with an
6137 underscore, so let's knock it off before we get in trouble. Fix
6138 for bug 1031; bugfix on the first Tor commit.
6139 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
6140 with large values. This situation was untriggered, but nevertheless
6141 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
6142 - Fix an impossible buffer overrun in the AES unit tests. Fixes
6143 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
6144 - Fix handling of rendezvous client authorization types over 8.
6145 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
6146 - Remove a couple of extraneous semicolons that were upsetting the
6147 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
6148 bugfix on 0.2.2.1-alpha.
6149 - When complaining about a client port on a public address, log
6150 which address we're complaining about. Fixes bug 4020; bugfix on
6151 0.2.3.3-alpha. Patch by Tom Fitzhenry.
6153 o Minor bugfixes (log messages, warnings):
6154 - If we encounter a write failure on a SOCKS connection before we
6155 finish our SOCKS handshake, don't warn that we closed the
6156 connection before we could send a SOCKS reply. Fixes bug 8427;
6157 bugfix on 0.1.0.1-rc.
6158 - Fix a directory authority warn caused when we have a large amount
6159 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
6160 - Downgrade "Failed to hand off onionskin" messages to "debug"
6161 severity, since they're typically redundant with the "Your computer
6162 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
6163 - Avoid spurious warnings when configuring multiple client ports of
6164 which only some are nonlocal. Previously, we had claimed that some
6165 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
6168 o Minor bugfixes (log messages, other):
6169 - Fix log messages and comments to avoid saying "GMT" when we mean
6170 "UTC". Fixes bug 6113.
6171 - When rejecting a configuration because we were unable to parse a
6172 quoted string, log an actual error message. Fixes bug 7950; bugfix
6174 - Correctly recognize that [::1] is a loopback address. Fixes
6175 bug 8377; bugfix on 0.2.1.3-alpha.
6176 - Don't log inappropriate heartbeat messages when hibernating: a
6177 hibernating node is _expected_ to drop out of the consensus,
6178 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
6179 bugfix on 0.2.3.1-alpha.
6180 - Eliminate several instances where we use "Nickname=ID" to refer to
6181 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
6182 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
6185 o Minor bugfixes (build):
6186 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
6187 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
6188 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
6190 o Documentation fixes:
6191 - Make the torify manpage no longer refer to tsocks; torify hasn't
6192 supported tsocks since 0.2.3.14-alpha.
6193 - Make the tor manpage no longer reference tsocks.
6194 - Fix the GeoIPExcludeUnknown documentation to refer to
6195 ExcludeExitNodes rather than the currently nonexistent
6196 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
6197 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
6199 - Say "KBytes" rather than "KB" in the man page (for various values
6200 of K), to further reduce confusion about whether Tor counts in
6201 units of memory or fractions of units of memory. Resolves ticket 7054.
6202 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
6203 names match. Fixes bug 7768.
6204 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
6205 message is logged at notice, not at info.
6206 - Clarify the usage and risks of setting the ContactInfo torrc line
6207 for your relay or bridge. Resolves ticket 9854.
6208 - Add anchors to the manpage so we can link to the html version of
6209 the documentation for specific options. Resolves ticket 9866.
6210 - Replace remaining references to DirServer in man page and
6211 log entries. Resolves ticket 10124.
6214 - Stop exporting estimates of v2 and v3 directory traffic shares
6215 in extrainfo documents. They were unneeded and sometimes inaccurate.
6216 Also stop exporting any v2 directory request statistics. Resolves
6218 - Drop support for detecting and warning about versions of Libevent
6219 before 1.3e. Nothing reasonable ships with them any longer; warning
6220 the user about them shouldn't be needed. Resolves ticket 6826.
6221 - Now that all versions before 0.2.2.x are disallowed, we no longer
6222 need to work around their missing features. Remove a bunch of
6226 - The tor-tsocks.conf is no longer distributed or installed. We
6227 recommend that tsocks users use torsocks instead. Resolves
6229 - Remove some of the older contents of doc/ as obsolete; move others
6230 to torspec.git. Fixes bug 8965.
6232 o Code simplification:
6233 - Avoid using character buffers when constructing most directory
6234 objects: this approach was unwieldy and error-prone. Instead,
6235 build smartlists of strings, and concatenate them when done.
6236 - Rename "isin" functions to "contains", for grammar. Resolves
6238 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
6239 with the natural logarithm function from the system libm. Resolves
6241 - Start using OpenBSD's implementation of queue.h, so that we don't
6242 need to hand-roll our own pointer and list structures whenever we
6243 need them. (We can't rely on a sys/queue.h, since some operating
6244 systems don't have them, and the ones that do have them don't all
6245 present the same extensions.)
6246 - Start using OpenBSD's implementation of queue.h (originally by
6248 - Enhance our internal sscanf replacement so that we can eliminate
6249 the last remaining uses of the system sscanf. (Though those uses
6250 of sscanf were safe, sscanf itself is generally error prone, so
6251 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
6253 - Replace all calls to snprintf() outside of src/ext with
6254 tor_snprintf(). Also remove the #define to replace snprintf with
6255 _snprintf on Windows; they have different semantics, and all of
6256 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
6259 - Add a wrapper function for the common "log a message with a
6261 - Split the onion.c file into separate modules for the onion queue
6262 and the different handshakes it supports.
6263 - Move the client-side address-map/virtual-address/DNS-cache code
6264 out of connection_edge.c into a new addressmap.c module.
6265 - Move the entry node code from circuitbuild.c to its own file.
6266 - Move the circuit build timeout tracking code from circuitbuild.c
6268 - Source files taken from other packages now reside in src/ext;
6269 previously they were scattered around the rest of Tor.
6270 - Move the generic "config" code into a new file, and have "config.c"
6271 hold only torrc- and state-related code. Resolves ticket 6823.
6272 - Move the core of our "choose a weighted element at random" logic
6273 into its own function, and give it unit tests. Now the logic is
6274 testable, and a little less fragile too.
6275 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
6276 - Move last_reachable and testing_since from routerinfo_t to node_t.
6277 Implements ticket 5529.
6278 - Add replaycache_t structure, functions and unit tests, then refactor
6279 rend_service_introduce() to be more clear to read, improve, debug,
6280 and test. Resolves bug 6177.
6283 - Remove some now-needless code that tried to aggressively flush
6284 OR connections as data was added to them. Since 0.2.0.1-alpha, our
6285 cell queue logic has saved us from the failure mode that this code
6286 was supposed to prevent. Removing this code will limit the number
6287 of baroque control flow paths through Tor's network logic. Reported
6288 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
6289 - Remove unused code for parsing v1 directories and "running routers"
6290 documents. Fixes bug 6887.
6291 - Remove the marshalling/unmarshalling code for sending requests to
6292 cpuworkers over a socket, and instead just send structs. The
6293 recipient will always be the same Tor binary as the sender, so
6294 any encoding is overkill.
6295 - Remove the testing_since field of node_t, which hasn't been used
6296 for anything since 0.2.0.9-alpha.
6297 - Finally remove support for malloc_good_size and malloc_usable_size.
6298 We had hoped that these functions would let us eke a little more
6299 memory out of our malloc implementation. Unfortunately, the only
6300 implementations that provided these functions are also ones that
6301 are already efficient about not overallocation: they never got us
6302 more than 7 or so bytes per allocation. Removing them saves us a
6303 little code complexity and a nontrivial amount of build complexity.
6306 Changes in version 0.2.3.25 - 2012-11-19
6307 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
6308 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
6309 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
6310 programmer, and friend. Unstinting in his dedication to the cause of
6311 freedom, he inspired and helped many of us as we began our work on
6312 anonymity, and inspires us still. Please honor his memory by writing
6313 software to protect people's freedoms, and by helping others to do so.
6315 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
6316 significantly reduced directory overhead (via microdescriptors),
6317 enormous crypto performance improvements for fast relays on new
6318 enough hardware, a new v3 TLS handshake protocol that can better
6319 resist fingerprinting, support for protocol obfuscation plugins (aka
6320 pluggable transports), better scalability for hidden services, IPv6
6321 support for bridges, performance improvements like allowing clients
6322 to skip the first round-trip on the circuit ("optimistic data") and
6323 refilling token buckets more often, a new "stream isolation" design
6324 to isolate different applications on different circuits, and many
6325 stability, security, and privacy fixes.
6327 Major features (v3 directory protocol):
6328 - Clients now use microdescriptors instead of regular descriptors
6329 to build circuits. Microdescriptors are authority-generated
6330 summaries of regular descriptors' contents, designed to change very
6331 rarely (see proposal 158 for details). This feature is designed
6332 to save bandwidth, especially for clients on slow internet
6333 connections. Use "UseMicrodescriptors 0" to disable it.
6334 - Caches now download, cache, and serve microdescriptors, as well
6335 as multiple "flavors" of the consensus, including a flavor that
6336 describes microdescriptors.
6338 o Major features (build hardening):
6339 - Enable gcc and ld hardening by default. Resolves ticket 5210.
6341 o Major features (relay scaling):
6342 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
6343 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
6344 vectorized AES implementations as appropriate. These can be much,
6345 much faster than other AES implementations.
6346 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
6347 implementation. It makes AES_CTR about 7% faster than our old one
6348 (which was about 10% faster than the one OpenSSL used to provide).
6349 Resolves ticket 4526.
6350 - Use OpenSSL's EVP interface for AES encryption, so that all AES
6351 operations can use hardware acceleration (if present). Resolves
6353 - Unconditionally use OpenSSL's AES implementation instead of our
6354 old built-in one. OpenSSL's AES has been better for a while, and
6355 relatively few servers should still be on any version of OpenSSL
6356 that doesn't have good optimized assembly AES.
6358 o Major features (blocking resistance):
6359 - Update TLS cipher list to match Firefox 8 and later. Resolves
6361 - Remove support for clients falsely claiming to support standard
6362 ciphersuites that they can actually provide. As of modern OpenSSL
6363 versions, it's not necessary to fake any standard ciphersuite,
6364 and doing so prevents us from using better ciphersuites in the
6365 future, since servers can't know whether an advertised ciphersuite
6366 is really supported or not. Some hosts -- notably, ones with very
6367 old versions of OpenSSL or where OpenSSL has been built with ECC
6368 disabled -- will stand out because of this change; TBB users should
6369 not be affected. Implements the client side of proposal 198.
6370 - Implement a new handshake protocol (v3) for authenticating Tors to
6371 each other over TLS. It should be more resistant to fingerprinting
6372 than previous protocols, and should require less TLS hacking for
6373 future Tor implementations. Implements proposal 176.
6374 - Allow variable-length padding cells, to disguise the length of
6375 Tor's TLS records. Implements part of proposal 184.
6376 - While we're trying to bootstrap, record how many TLS connections
6377 fail in each state, and report which states saw the most failures
6378 in response to any bootstrap failures. This feature may speed up
6379 diagnosis of censorship events. Implements ticket 3116.
6381 o Major features (pluggable transports):
6382 - Clients and bridges can now be configured to use a separate
6383 "transport" proxy. This approach makes the censorship arms race
6384 easier by allowing bridges to use protocol obfuscation plugins.
6385 Implements proposal 180 (tickets 2841 and 3472).
6387 o Major features (DoS resistance):
6388 - Now that Tor 0.2.0.x is completely deprecated, enable the final
6389 part of "Proposal 110: Avoiding infinite length circuits" by
6390 refusing all circuit-extend requests that do not use a relay_early
6391 cell. This change helps Tor resist a class of denial-of-service
6392 attacks by limiting the maximum circuit length.
6393 - Tear down the circuit if we get an unexpected SENDME cell. Clients
6394 could use this trick to make their circuits receive cells faster
6395 than our flow control would have allowed, or to gum up the network,
6396 or possibly to do targeted memory denial-of-service attacks on
6397 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
6398 from July 2002, before the release of Tor 0.0.0.
6400 o Major features (hidden services):
6401 - Adjust the number of introduction points that a hidden service
6402 will try to maintain based on how long its introduction points
6403 remain in use and how many introductions they handle. Fixes
6405 - Add a "tor2web mode" for clients that want to connect to hidden
6406 services non-anonymously (and possibly more quickly). As a safety
6407 measure to try to keep users from turning this on without knowing
6408 what they are doing, tor2web mode must be explicitly enabled at
6409 compile time, and a copy of Tor compiled to run in tor2web mode
6410 cannot be used as a normal Tor client. Implements feature 2553.
6412 o Major features (IPv6):
6413 - Clients can now connect to private bridges over IPv6. Bridges
6414 still need at least one IPv4 address in order to connect to
6415 other relays. Note that we don't yet handle the case where the
6416 user has two bridge lines for the same bridge (one IPv4, one
6417 IPv6). Implements parts of proposal 186.
6419 o Major features (directory authorities):
6420 - Use a more secure consensus parameter voting algorithm. Now at
6421 least three directory authorities or a majority of them must
6422 vote on a given parameter before it will be included in the
6423 consensus. Implements proposal 178.
6424 - Remove the artificially low cutoff of 20KB to guarantee the Fast
6425 flag. In the past few years the average relay speed has picked
6426 up, and while the "top 7/8 of the network get the Fast flag" and
6427 "all relays with 20KB or more of capacity get the Fast flag" rules
6428 used to have the same result, now the top 7/8 of the network has
6429 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
6431 o Major features (performance):
6432 - Exit nodes now accept and queue data on not-yet-connected streams.
6433 Previously, the client wasn't allowed to send data until the
6434 stream was connected, which slowed down all connections. This
6435 change will enable clients to perform a "fast-start" on streams
6436 and send data without having to wait for a confirmation that the
6437 stream has opened. Patch from Ian Goldberg; implements the server
6438 side of Proposal 174.
6439 - When using an exit relay running 0.2.3.x, clients can now
6440 "optimistically" send data before the exit relay reports that
6441 the stream has opened. This saves a round trip when starting
6442 connections where the client speaks first (such as web browsing).
6443 This behavior is controlled by a consensus parameter (currently
6444 disabled). To turn it on or off manually, use the "OptimisticData"
6445 torrc option. Implements proposal 181; code by Ian Goldberg.
6446 - Add a new TokenBucketRefillInterval option to refill token buckets
6447 more frequently than once per second. This should improve network
6448 performance, alleviate queueing problems, and make traffic less
6449 bursty. Implements proposal 183; closes ticket 3630. Design by
6450 Florian Tschorsch and Björn Scheuermann; implementation by
6452 - Raise the threshold of server descriptors needed (75%) and exit
6453 server descriptors needed (50%) before we will declare ourselves
6454 bootstrapped. This will make clients start building circuits a
6455 little later, but makes the initially constructed circuits less
6456 skewed and less in conflict with further directory fetches. Fixes
6459 o Major features (relays):
6460 - Relays now try regenerating and uploading their descriptor more
6461 frequently if they are not listed in the consensus, or if the
6462 version of their descriptor listed in the consensus is too
6463 old. This fix should prevent situations where a server declines
6464 to re-publish itself because it has done so too recently, even
6465 though the authorities decided not to list its recent-enough
6466 descriptor. Fix for bug 3327.
6468 o Major features (stream isolation):
6469 - You can now configure Tor so that streams from different
6470 applications are isolated on different circuits, to prevent an
6471 attacker who sees your streams as they leave an exit node from
6472 linking your sessions to one another. To do this, choose some way
6473 to distinguish the applications: have them connect to different
6474 SocksPorts, or have one of them use SOCKS4 while the other uses
6475 SOCKS5, or have them pass different authentication strings to the
6476 SOCKS proxy. Then, use the new SocksPort syntax to configure the
6477 degree of isolation you need. This implements Proposal 171.
6478 - There's a new syntax for specifying multiple client ports (such as
6479 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
6480 multiple *Port entries with full addr:port syntax on each.
6481 The old *ListenAddress format is still supported, but you can't
6482 mix it with the new *Port syntax.
6484 o Major features (bufferevents):
6485 - Tor can now optionally build with the "bufferevents" buffered IO
6486 backend provided by Libevent 2. To use this feature, make sure you
6487 have the latest possible version of Libevent, and pass the
6488 --enable-bufferevents flag to configure when building Tor from
6489 source. This feature will make our networking code more flexible,
6490 let us stack layers on each other, and let us use more efficient
6491 zero-copy transports where available.
6492 - Add experimental support for running on Windows with IOCP and no
6493 kernel-space socket buffers. This feature is controlled by a new
6494 "UserspaceIOCPBuffers" config option (off by default), which has
6495 no effect unless Tor has been built with bufferevents enabled,
6496 you're running on Windows, and you've set "DisableIOCP 0". In the
6497 long run, this may help solve or mitigate bug 98.
6499 o Major features (path selection):
6500 - The EntryNodes option can now include country codes like {de} or IP
6501 addresses or network masks. Previously we had disallowed these
6502 options because we didn't have an efficient way to keep the list up
6503 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
6506 o Major features (port forwarding):
6507 - Add support for automatic port mapping on the many home routers
6508 that support NAT-PMP or UPnP. To build the support code, you'll
6509 need to have the libnatpnp library and/or the libminiupnpc library,
6510 and you'll need to enable the feature specifically by passing
6511 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
6512 it on, use the new PortForwarding option.
6514 o Major features (logging):
6515 - Add a new 'Heartbeat' log message type to periodically log a message
6516 describing Tor's status at level Notice. This feature is meant for
6517 operators who log at notice, and want to make sure that their Tor
6518 server is still working. Implementation by George Kadianakis.
6519 - Make logging resolution configurable with a new LogTimeGranularity
6520 option, and change the default from 1 millisecond to 1 second.
6521 Implements enhancement 1668.
6523 o Major features (other):
6524 - New "DisableNetwork" config option to prevent Tor from launching any
6525 connections or accepting any connections except on a control port.
6526 Bundles and controllers can set this option before letting Tor talk
6527 to the rest of the network, for example to prevent any connections
6528 to a non-bridge address. Packages like Orbot can also use this
6529 option to instruct Tor to save power when the network is off.
6530 - Try to use system facilities for enumerating local interface
6531 addresses, before falling back to our old approach (which was
6532 binding a UDP socket, and calling getsockname() on it). That
6533 approach was scaring OS X users whose draconian firewall
6534 software warned about binding to UDP sockets regardless of
6535 whether packets were sent. Now we try to use getifaddrs(),
6536 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
6537 system supports. Resolves ticket 1827.
6538 - Add experimental support for a "defaults" torrc file to be parsed
6539 before the regular torrc. Torrc options override the defaults file's
6540 options in the same way that the command line overrides the torrc.
6541 The SAVECONF controller command saves only those options which
6542 differ between the current configuration and the defaults file. HUP
6543 reloads both files. Implements task 4552.
6545 o New directory authorities:
6546 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6547 authority. Closes ticket 5749.
6549 o Security/privacy fixes:
6550 - Avoid read-from-freed-memory and double-free bugs that could occur
6551 when a DNS request fails while launching it. Fixes bug 6480;
6552 bugfix on 0.2.0.1-alpha.
6553 - Reject any attempt to extend to an internal address. Without
6554 this fix, a router could be used to probe addresses on an internal
6555 network to see whether they were accepting connections. Fixes bug
6556 6710; bugfix on 0.0.8pre1.
6557 - Close any connection that sends unrecognized junk before the TLS
6558 handshake. Solves an issue noted in bug 4369.
6559 - The advertised platform of a relay now includes only its operating
6560 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
6561 its service pack level (for Windows) or its CPU architecture
6562 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
6563 can insert an extra string in the platform line by setting the
6564 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
6565 - Disable TLS session tickets. OpenSSL's implementation was giving
6566 our TLS session keys the lifetime of our TLS context objects, when
6567 perfect forward secrecy would want us to discard anything that
6568 could decrypt a link connection as soon as the link connection
6569 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6570 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6571 - Tor tries to wipe potentially sensitive data after using it, so
6572 that if some subsequent security failure exposes Tor's memory,
6573 the damage will be limited. But we had a bug where the compiler
6574 was eliminating these wipe operations when it decided that the
6575 memory was no longer visible to a (correctly running) program,
6576 hence defeating our attempt at defense in depth. We fix that
6577 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6578 is unlikely to optimize away. Future versions of Tor may use
6579 a less ridiculously heavy approach for this. Fixes bug 7352.
6580 Reported in an article by Andrey Karpov.
6582 o Major bugfixes (crashes and asserts):
6583 - Avoid a pair of double-free and use-after-mark bugs that can
6584 occur with certain timings in canceled and re-received DNS
6585 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
6586 - Fix a denial of service attack by which any directory authority
6587 could crash all the others, or by which a single v2 directory
6588 authority could crash everybody downloading v2 directory
6589 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6590 - Fix an assert that directory authorities could trigger on sighup
6591 during some configuration state transitions. We now don't treat
6592 it as a fatal error when the new descriptor we just generated in
6593 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
6594 - Avoid segfault when starting up having run with an extremely old
6595 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6598 o Major bugfixes (clients):
6599 - If we are unable to find any exit that supports our predicted ports,
6600 stop calling them predicted, so that we don't loop and build
6601 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
6602 which introduced predicted ports.
6603 - Check at each new consensus whether our entry guards were picked
6604 long enough ago that we should rotate them. Previously, we only
6605 did this check at startup, which could lead to us holding a guard
6606 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
6607 - When fetching a bridge descriptor from a bridge authority,
6608 always do so anonymously, whether we have been able to open
6609 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
6610 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
6611 but we'll need to wait for bug 6010 before it's actually usable.
6613 o Major bugfixes (directory voting):
6614 - Check more thoroughly to prevent a rogue authority from
6615 double-voting on any consensus directory parameter. Previously,
6616 authorities would crash in this case if the total number of
6617 votes for any parameter exceeded the number of active voters,
6618 but would let it pass otherwise. Partially fixes bug 5786; bugfix
6620 - When computing weight parameters, behave more robustly in the
6621 presence of a bad bwweightscale value. Previously, the authorities
6622 would crash if they agreed on a sufficiently broken weight_scale
6623 value; now, they use a reasonable default and carry on. Fixes the
6624 rest of bug 5786; bugfix on 0.2.2.17-alpha.
6625 - If authorities are unable to get a v2 consensus document from other
6626 directory authorities, they no longer fall back to fetching
6627 them from regular directory caches. Fixes bug 5635; bugfix on
6628 0.2.2.26-beta, where routers stopped downloading v2 consensus
6631 o Major bugfixes (relays):
6632 - Fix a bug handling SENDME cells on nonexistent streams that could
6633 result in bizarre window values. Report and patch contributed
6634 pseudonymously. Fixes part of bug 6271. This bug was introduced
6635 before the first Tor release, in svn commit r152.
6636 - Don't update the AccountingSoftLimitHitAt state file entry whenever
6637 tor gets started. This prevents a wrong average bandwidth
6638 estimate, which would cause relays to always start a new accounting
6639 interval at the earliest possible moment. Fixes bug 2003; bugfix
6640 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
6641 immensely in tracking this bug down.
6642 - Fix a possible crash bug when checking for deactivated circuits
6643 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6644 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6645 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
6646 connections. This change should allow busy exit relays to stop
6647 running out of available sockets as quickly. Fixes bug 4950;
6648 bugfix on 0.2.2.26-beta.
6650 o Major bugfixes (blocking resistance):
6651 - Bridges no longer include their address in NETINFO cells on outgoing
6652 OR connections, to allow them to blend in better with clients.
6653 Removes another avenue for enumerating bridges. Reported by
6654 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
6655 cells were introduced.
6656 - Warn the user when HTTPProxy, but no other proxy type, is
6657 configured. This can cause surprising behavior: it doesn't send
6658 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
6659 directory traffic only. Resolves ticket 4663.
6661 o Major bugfixes (hidden services):
6662 - Improve hidden service robustness: when an attempt to connect to
6663 a hidden service ends, be willing to refetch its hidden service
6664 descriptors from each of the HSDir relays responsible for them
6665 immediately. Previously, we would not consider refetching the
6666 service's descriptors from each HSDir for 15 minutes after the last
6667 fetch, which was inconvenient if the hidden service was not running
6668 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
6669 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
6670 They used to check that the timestamp was within 30 minutes
6671 of their system clock, so they could cap the size of their
6672 replay-detection cache, but that approach unnecessarily refused
6673 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
6674 the v3 intro-point protocol (the first one which sent a timestamp
6675 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
6676 - When one of a hidden service's introduction points appears to be
6677 unreachable, stop trying it. Previously, we would keep trying
6678 to build circuits to the introduction point until we lost the
6679 descriptor, usually because the user gave up and restarted Tor.
6680 Fixes part of bug 3825.
6682 o Changes to default torrc file:
6683 - Stop listing "socksport 9050" in torrc.sample. We open a socks
6684 port on 9050 by default anyway, so this should not change anything
6686 - Stop mentioning the deprecated *ListenAddress options in
6687 torrc.sample. Fixes bug 5438.
6688 - Document unit of bandwidth-related options in sample torrc.
6690 - Fix broken URLs in the sample torrc file, and tell readers about
6691 the OutboundBindAddress, ExitPolicyRejectPrivate, and
6692 PublishServerDescriptor options. Addresses bug 4652.
6694 o Minor features (directory authorities):
6695 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
6696 change when the authority is deciding whether to accept a newly
6697 uploaded descriptor. Implements ticket 6423.
6698 - Directory authorities are now a little more lenient at accepting
6699 older router descriptors, or newer router descriptors that don't
6700 make big changes. This should help ameliorate past and future
6701 issues where routers think they have uploaded valid descriptors,
6702 but the authorities don't think so. Fix for ticket 2479.
6703 - Authority operators can now vote for all relays in a given
6704 set of countries to be BadDir/BadExit/Invalid/Rejected.
6705 - Provide two consensus parameters (FastFlagMinThreshold and
6706 FastFlagMaxThreshold) to control the range of allowable bandwidths
6707 for the Fast directory flag. These allow authorities to run
6708 experiments on appropriate requirements for being a "Fast" node.
6709 The AuthDirFastGuarantee config value still applies. Implements
6712 o Minor features (bridges / bridge authorities):
6713 - Make bridge SSL certificates a bit more stealthy by using random
6714 serial numbers, in the same fashion as OpenSSL when generating
6715 self-signed certificates. Implements ticket 4584.
6716 - Tag a bridge's descriptor as "never to be sent unencrypted".
6717 This shouldn't matter, since bridges don't open non-anonymous
6718 connections to the bridge authority and don't allow unencrypted
6719 directory connections from clients, but we might as well make
6720 sure. Closes bug 5139.
6721 - The Bridge Authority now writes statistics on how many bridge
6722 descriptors it gave out in total, and how many unique descriptors
6723 it gave out. It also lists how often the most and least commonly
6724 fetched descriptors were given out, as well as the median and
6725 25th/75th percentile. Implements tickets 4200 and 4294.
6727 o Minor features (IPv6):
6728 - Make the code that clients use to detect an address change be
6729 IPv6-aware, so that it won't fill clients' logs with error
6730 messages when trying to get the IPv4 address of an IPv6
6731 connection. Implements ticket 5537.
6732 - Relays now understand an IPv6 address when they get one from a
6733 directory server. Resolves ticket 4875.
6735 o Minor features (hidden services):
6736 - Expire old or over-used hidden service introduction points.
6737 Required by fix for bug 3460.
6738 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
6739 public key replay-detection cache from 60 minutes to 5 minutes. This
6740 replay-detection cache is now used only to detect multiple
6741 INTRODUCE2 cells specifying the same rendezvous point, so we can
6742 avoid launching multiple simultaneous attempts to connect to it.
6743 - When a hidden service's introduction point times out, consider
6744 trying it again during the next attempt to connect to the
6745 HS. Previously, we would not try it again unless a newly fetched
6746 descriptor contained it. Required by fixes for bugs 1297 and 3825.
6748 o Minor features (relays):
6749 - Relays now include a reason for regenerating their descriptors
6750 in an HTTP header when uploading to the authorities. This will
6751 make it easier to debug descriptor-upload issues in the future.
6752 - Turn on directory request statistics by default and include them in
6753 extra-info descriptors. Don't break if we have no GeoIP database.
6754 - Replace files in stats/ rather than appending to them. Now that we
6755 include statistics in extra-info descriptors, it makes no sense to
6756 keep old statistics forever. Implements ticket 2930.
6757 - Relays that set "ConnDirectionStatistics 1" write statistics on the
6758 bidirectional use of connections to disk every 24 hours.
6759 - Add a GeoIP file digest to the extra-info descriptor. Implements
6762 o Minor features (new config options):
6763 - New config option "DynamicDHGroups" (disabled by default) provides
6764 each bridge with a unique prime DH modulus to be used during
6765 SSL handshakes. This option attempts to help against censors
6766 who might use the Apache DH modulus as a static identifier for
6767 bridges. Addresses ticket 4548.
6768 - New config option "DisableDebuggerAttachment" (on by default)
6769 to prevent basic debugging attachment attempts by other processes.
6770 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
6771 - Ordinarily, Tor does not count traffic from private addresses (like
6772 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
6773 There is now a new option, CountPrivateBandwidth, to disable this
6774 behavior. Patch from Daniel Cagara.
6776 o Minor features (different behavior for old config options):
6777 - Allow MapAddress directives to specify matches against super-domains,
6778 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
6779 Implements issue 933.
6780 - Don't disable the DirPort when we cannot exceed our AccountingMax
6781 limit during this interval because the effective bandwidthrate is
6782 low enough. This is useful in a situation where AccountMax is only
6783 used as an additional safeguard or to provide statistics.
6784 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
6785 implements ticket 3439.
6786 - When configuring a large set of nodes in EntryNodes, and there are
6787 enough of them listed as Guard so that we don't need to consider
6788 the non-guard entries, prefer the ones listed with the Guard flag.
6789 - If you set the NumCPUs option to 0, Tor will now try to detect how
6790 many CPUs you have. This is the new default behavior.
6791 - The NodeFamily option -- which let you declare that you want to
6792 consider nodes to be part of a family whether they list themselves
6793 that way or not -- now allows IP address ranges and country codes.
6795 o Minor features (new command-line config behavior):
6796 - Slightly change behavior of "list" options (that is, config
6797 options that can appear more than once) when they appear both in
6798 torrc and on the command line. Previously, the command-line options
6799 would be appended to the ones from torrc. Now, the command-line
6800 options override the torrc options entirely. This new behavior
6801 allows the user to override list options (like exit policies and
6802 ports to listen on) from the command line, rather than simply
6803 appending to the list.
6804 - You can get the old (appending) command-line behavior for "list"
6805 options by prefixing the option name with a "+".
6806 - You can remove all the values for a "list" option from the command
6807 line without adding any new ones by prefixing the option name
6810 o Minor features (controller, new events):
6811 - Extend the control protocol to report flags that control a circuit's
6812 path selection in CIRC events and in replies to 'GETINFO
6813 circuit-status'. Implements part of ticket 2411.
6814 - Extend the control protocol to report the hidden service address
6815 and current state of a hidden-service-related circuit in CIRC
6816 events and in replies to 'GETINFO circuit-status'. Implements part
6818 - Include the creation time of a circuit in CIRC and CIRC2
6819 control-port events and the list produced by the 'GETINFO
6820 circuit-status' control-port command.
6821 - Add a new CONF_CHANGED event so that controllers can be notified
6822 of any configuration changes made by other controllers, or by the
6823 user. Implements ticket 1692.
6824 - Add a new SIGNAL event to the controller interface so that
6825 controllers can be notified when Tor handles a signal. Resolves
6826 issue 1955. Patch by John Brooks.
6828 o Minor features (controller, new getinfo options):
6829 - Expose our view of whether we have gone dormant to the controller,
6830 via a new "GETINFO dormant" value. Torbutton and other controllers
6831 can use this to avoid doing periodic requests through Tor while
6832 it's dormant (bug 4718). Resolves ticket 5954.
6833 - Add a new GETINFO option to get total bytes read and written. Patch
6834 from pipe, revised by atagar. Resolves ticket 2345.
6835 - Implement new GETINFO controller fields to provide information about
6836 the Tor process's pid, euid, username, and resource limits.
6838 o Minor features (controller, other):
6839 - Allow controllers to request an event notification whenever a
6840 circuit is cannibalized or its purpose is changed. Implements
6841 part of ticket 3457.
6842 - Use absolute path names when reporting the torrc filename in the
6843 control protocol, so a controller can more easily find the torrc
6844 file. Resolves bug 1101.
6845 - When reporting the path to the cookie file to the controller,
6846 give an absolute path. Resolves ticket 4881.
6848 o Minor features (log messages):
6849 - Add more information to a log statement that might help track down
6850 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
6851 non-IP address" messages (or any Bug messages, for that matter!),
6852 please let us know about it.
6853 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
6854 EntryNodes will have no effect. Resolves issue 2571.
6855 - Try to make the introductory warning message that Tor prints on
6856 startup more useful for actually finding help and information.
6857 Resolves ticket 2474.
6858 - When the system call to create a listener socket fails, log the
6859 error message explaining why. This may help diagnose bug 4027.
6861 o Minor features (other):
6862 - When we fail to initialize Libevent, retry with IOCP disabled so we
6863 don't need to turn on multi-threading support in Libevent, which in
6864 turn requires a working socketpair(). This is a workaround for bug
6865 4457, which affects Libevent versions from 2.0.1-alpha through
6867 - When starting as root and then changing our UID via the User
6868 control option, and we have a ControlSocket configured, make sure
6869 that the ControlSocket is owned by the same account that Tor will
6870 run under. Implements ticket 3421; fix by Jérémy Bobbio.
6871 - Accept attempts to include a password authenticator in the
6872 handshake, as supported by SOCKS5. This handles SOCKS clients that
6873 don't know how to omit a password when authenticating. Resolves
6875 - Check for and recover from inconsistency in the microdescriptor
6876 cache. This will make it harder for us to accidentally free a
6877 microdescriptor without removing it from the appropriate data
6878 structures. Fixes issue 3135; issue noted by "wanoskarnet".
6879 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
6881 o Minor bugfixes (code security):
6882 - Prevent a null-pointer dereference when receiving a data cell
6883 for a nonexistent stream when the circuit in question has an
6884 empty deliver window. We don't believe this is triggerable,
6885 since we don't currently allow deliver windows to become empty,
6886 but the logic is tricky enough that it's better to make the code
6887 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
6888 - Fix a (harmless) integer overflow in cell statistics reported by
6889 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
6890 - Fix our implementation of crypto_random_hostname() so it can't
6891 overflow on ridiculously large inputs. (No Tor version has ever
6892 provided this kind of bad inputs, but let's be correct in depth.)
6893 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
6894 - Add a (probably redundant) memory clear between iterations of
6895 the router status voting loop, to prevent future coding errors
6896 where data might leak between iterations of the loop. Resolves
6899 o Minor bugfixes (wrapper functions):
6900 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
6901 utility function used in the control-port code). This shouldn't
6902 ever happen unless Tor is completely out of memory, but if it did
6903 happen and Tor somehow recovered from it, Tor could have sent a log
6904 message to a control port in the middle of a reply to a controller
6905 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
6906 - Fix some (not actually triggerable) buffer size checks in usage of
6907 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
6909 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
6910 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
6911 - Enforce correct return behavior of tor_vsscanf() when the '%%'
6912 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
6913 - Make our replacement implementation of strtok_r() compatible with
6914 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
6915 bugfix on 0.2.2.1-alpha.
6916 - Find more places in the code that should have been testing for
6917 invalid sockets using the SOCKET_OK macro. Required for a fix
6918 for bug 4533. Bugfix on 0.2.2.28-beta.
6920 o Minor bugfixes (code correctness):
6921 - Check return value of fputs() when writing authority certificate
6922 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
6923 - When building Tor on Windows with -DUNICODE (not default), ensure
6924 that error messages, filenames, and DNS server names are always
6925 NUL-terminated when we convert them to a single-byte encoding.
6926 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
6927 - Fix a memory leak when trying to launch a DNS request when the
6928 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
6930 - Correct file sizes when reading binary files on Cygwin, to avoid
6931 a bug where Tor would fail to read its state file. Fixes bug 6844;
6932 bugfix on 0.1.2.7-alpha.
6933 - Make sure to set *socket_error in all error cases in
6934 connection_connect(), so it can't produce a warning about
6935 errno being zero from errno_to_orconn_end_reason(). Bugfix on
6936 0.2.1.1-alpha; resolves ticket 6028.
6937 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
6938 bug 4532; found by "troll_un".
6940 o Minor bugfixes (clients):
6941 - Allow one-hop directory-fetching circuits the full "circuit build
6942 timeout" period, rather than just half of it, before failing them
6943 and marking the relay down. This fix should help reduce cases where
6944 clients declare relays (or worse, bridges) unreachable because
6945 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
6946 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
6948 - Ensure we don't cannibalize circuits that are longer than three hops
6949 already, so we don't end up making circuits with 5 or more
6950 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
6951 0.1.0.1-rc which introduced cannibalization.
6953 o Minor bugfixes (relays):
6954 - Don't publish a new relay descriptor when we reload our onion key,
6955 unless the onion key has actually changed. Fixes bug 3263 and
6956 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
6957 - When relays refuse a "create" cell because their queue of pending
6958 create cells is too big (typically because their cpu can't keep up
6959 with the arrival rate), send back reason "resource limit" rather
6960 than reason "internal", so network measurement scripts can get a
6961 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
6962 - Exit nodes don't need to fetch certificates for authorities that
6963 they don't recognize; only directory authorities, bridges,
6964 and caches need to do that. Fixes part of bug 2297; bugfix on
6967 o Minor bugfixes (directory authority / mirrors):
6968 - Avoid O(n^2) performance characteristics when parsing a large
6969 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
6970 - Authorities no longer include any router in their microdescriptor
6971 consensuses for which they couldn't generate or agree on a
6972 microdescriptor. Fixes the second piece of bug 6404; fix on
6974 - When checking for requested signatures on the latest consensus
6975 before serving it to a client, make sure to check the right
6976 consensus flavor. Bugfix on 0.2.2.6-alpha.
6977 - Fix an edge case where TestingTorNetwork is set but the authorities
6978 and relays all have an uptime of zero, so the private Tor network
6979 could briefly lack support for hidden services. Fixes bug 3886;
6980 bugfix on 0.2.2.18-alpha.
6981 - Directory caches no longer refuse to clean out descriptors because
6982 of missing v2 networkstatus documents, unless they're configured
6983 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
6984 0.2.2.26-beta. Patch by Daniel Bryg.
6985 - Don't serve or accept v2 hidden service descriptors over a relay's
6986 DirPort. It's never correct to do so, and disabling it might
6987 make it more annoying to exploit any bugs that turn up in the
6988 descriptor-parsing code. Fixes bug 7149.
6990 o Minor bugfixes (hidden services, client-side):
6991 - Assert that hidden-service-related operations are not performed
6992 using single-hop circuits. Previously, Tor would assert that
6993 client-side streams are not attached to single-hop circuits,
6994 but not that other sensitive operations on the client and service
6995 side are not performed using single-hop circuits. Fixes bug 3332;
6997 - Avoid undefined behavior when parsing the list of supported
6998 rendezvous/introduction protocols in a hidden service descriptor.
6999 Previously, Tor would have confused (as-yet-unused) protocol version
7000 numbers greater than 32 with lower ones on many platforms. Fixes
7001 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
7002 - Don't close hidden service client circuits which have almost
7003 finished connecting to their destination when they reach
7004 the normal circuit-build timeout. Previously, we would close
7005 introduction circuits which are waiting for an acknowledgement
7006 from the introduction point, and rendezvous circuits which have
7007 been specified in an INTRODUCE1 cell sent to a hidden service,
7008 after the normal CBT. Now, we mark them as 'timed out', and launch
7009 another rendezvous attempt in parallel. This behavior change can
7010 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
7011 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
7013 o Minor bugfixes (hidden services, service-side):
7014 - Don't close hidden-service-side rendezvous circuits when they
7015 reach the normal circuit-build timeout. This behavior change can
7016 be disabled using the new
7017 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
7018 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
7019 - Don't launch more than 10 service-side introduction-point circuits
7020 for a hidden service in five minutes. Previously, we would consider
7021 launching more introduction-point circuits if at least one second
7022 had passed without any introduction-point circuits failing. Fixes
7023 bug 4607; bugfix on 0.0.7pre1.
7025 o Minor bugfixes (config option behavior):
7026 - If the user tries to set MyFamily on a bridge, refuse to
7027 do so, and warn about the security implications. Fixes bug 4657;
7028 bugfix on 0.2.0.3-alpha.
7029 - The "--quiet" and "--hush" options now apply not only to Tor's
7030 behavior before logs are configured, but also to Tor's behavior in
7031 the absense of configured logs. Fixes bug 3550; bugfix on
7033 - Change the AllowDotExit rules so they should actually work.
7034 We now enforce AllowDotExit only immediately after receiving an
7035 address via SOCKS or DNSPort: other sources are free to provide
7036 .exit addresses after the resolution occurs. Fixes bug 3940;
7037 bugfix on 0.2.2.1-alpha.
7038 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
7039 don't depend on the consensus parameters or compute adaptive
7040 timeouts when it is disabled. Fixes bug 5049; bugfix on
7042 - After we pick a directory mirror, we would refuse to use it if
7043 it's in our ExcludeExitNodes list, resulting in mysterious failures
7044 to bootstrap for people who just wanted to avoid exiting from
7045 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
7046 - When told to add a bridge with the same digest as a preexisting
7047 bridge but a different addr:port, change the addr:port as
7048 requested. Previously we would not notice the change. Fixes half
7049 of bug 5603; fix on 0.2.2.26-beta.
7051 o Minor bugfixes (controller):
7052 - Allow manual 'authenticate' commands to the controller interface
7053 from netcat (nc) as well as telnet. We were rejecting them because
7054 they didn't come with the expected whitespace at the end of the
7055 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
7056 - Report a real bootstrap problem to the controller on router
7057 identity mismatch. Previously we just said "foo", which probably
7058 made a lot of sense at the time. Fixes bug 4169; bugfix on
7060 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
7061 option is set to 0 (which Vidalia version 0.2.16 now does when
7062 a SAVECONF attempt fails), perform other actions that SIGHUP
7063 usually causes (like reopening the logs). Fixes bug 5095; bugfix
7065 - Correctly handle checking the permissions on the parent
7066 directory of a control socket in the root directory. Bug found
7067 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
7069 - End AUTHCHALLENGE error messages (in the control protocol) with
7070 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
7072 o Minor bugfixes (network reading/writing):
7073 - Disable writing on marked-for-close connections when they are
7074 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
7075 bug 5263; bugfix on 0.0.2pre13, where we first added a special
7076 case for flushing marked connections.
7077 - Make sure that there are no unhandled pending TLS errors before
7078 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
7079 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
7080 Bugfix on 0.1.0.5-rc; fixes bug 4528.
7081 - Detect SSL handshake even when the initial attempt to write the
7082 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
7083 - If the client fails to set a reasonable set of ciphersuites
7084 during its v2 handshake renegotiation, allow the renegotiation to
7085 continue nevertheless (i.e. send all the required certificates).
7086 Fixes bug 4591; bugfix on 0.2.0.20-rc.
7088 o Minor bugfixes (other):
7089 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
7090 resource exhaustion, so that clients can adjust their load to
7091 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
7092 started using END_STREAM_REASON_RESOURCELIMIT.
7093 - Don't check for whether the address we're using for outbound
7094 connections has changed until after the outbound connection has
7095 completed. On Windows, getsockname() doesn't succeed until the
7096 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
7097 - Don't hold a Windows file handle open for every file mapping;
7098 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
7100 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
7101 bugfix on 0.2.1.10-alpha.
7102 - If we fail to write a microdescriptor to the disk cache, do not
7103 continue replacing the old microdescriptor file. Fixes bug 2954;
7104 bugfix on 0.2.2.6-alpha.
7106 o Minor bugfixes (log messages, path selection):
7107 - Downgrade "set buildtimeout to low value" messages to "info"
7108 severity; they were never an actual problem, there was never
7109 anything reasonable to do about them, and they tended to spam logs
7110 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
7111 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
7112 more information to it, so that we can track it down in case it
7113 returns again. Mitigates bug 5235.
7114 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
7115 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
7116 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
7117 - Issue a log message if a guard completes less than 40% of your
7118 circuits. Threshold is configurable by torrc option
7119 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
7120 additional, off-by-default code to disable guards which fail too
7121 many circuits. Addresses ticket 5458.
7123 o Minor bugfixes (log messages, client):
7124 - Downgrade "Got a certificate, but we already have it" log messages
7125 from warning to info, except when we're a dirauth. Fixes bug 5238;
7126 bugfix on 0.2.1.7-alpha.
7127 - Fix the log message describing how we work around discovering
7128 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
7129 4837; bugfix on 0.2.2.9-alpha.
7130 - When logging about a disallowed .exit name, do not also call it
7131 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
7132 - Fix a log message suggesting that people contact a non-existent
7133 email address. Fixes bug 3448.
7134 - Rephrase the log message emitted if the TestSocks check is
7135 successful. Patch from Fabian Keil; fixes bug 4094.
7136 - Log (at debug level) whenever a circuit's purpose is changed.
7137 - Log SSL state transitions at log level DEBUG, log domain
7138 HANDSHAKE. This can be useful for debugging censorship events.
7139 Implements ticket 3264.
7140 - We now log which torrc file we're using on startup. Implements
7142 - Rate-limit log messages when asked to connect anonymously to
7143 a private address. When these hit, they tended to hit fast and
7144 often. Also, don't bother trying to connect to addresses that we
7145 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
7146 reply makes us think we have been lied to, even when the address the
7147 client tried to connect to was "localhost." Resolves ticket 2822.
7149 o Minor bugfixes (log messages, non-client):
7150 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
7151 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
7152 - Don't log that we have "decided to publish new relay descriptor"
7153 unless we are actually publishing a descriptor. Fixes bug 3942;
7154 bugfix on 0.2.2.28-beta.
7155 - Log which authority we're missing votes from when we go to fetch
7156 them from the other auths.
7157 - Replace "Sending publish request" log messages with "Launching
7158 upload", so that they no longer confusingly imply that we're
7159 sending something to a directory we might not even be connected
7160 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
7161 - Warn when Tor is configured to use accounting in a way that can
7162 link a hidden service to some other hidden service or public
7163 address. Resolves ticket 6490.
7164 - Fix a minor formatting issue in one of tor-gencert's error messages.
7168 - Update to the latest version of the tinytest unit testing framework.
7169 This includes a couple of bugfixes that can be relevant for
7170 running forked unit tests on Windows, and removes all reserved
7172 - Avoid a false positive in the util/threads unit test by increasing
7173 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
7174 - Make it possible to set the TestingTorNetwork configuration
7175 option using AlternateDirAuthority and AlternateBridgeAuthority
7176 as an alternative to setting DirServer. Addresses ticket 6377.
7177 - Add a unit test for the environment_variable_names_equal() function.
7178 - A wide variety of new unit tests by Esteban Manchado Velázquez.
7179 - Numerous new unit tests for functions in util.c and address.c by
7181 - The long-disabled benchmark tests are now split into their own
7182 ./src/test/bench binary.
7183 - The benchmark tests can now use more accurate timers than
7184 gettimeofday() when such timers are available.
7185 - Use tt_assert(), not tor_assert(), for checking for test failures.
7186 This makes the unit tests more able to go on in the event that
7189 o Build improvements:
7190 - Use the dead_strip option when building Tor on OS X. This reduces
7191 binary size by almost 19% when linking openssl and libevent
7192 statically, which we do for Tor Browser Bundle.
7193 - Provide a better error message about possible OSX Asciidoc failure
7194 reasons. Fixes bug 6436.
7195 - Detect attempts to build Tor on (as yet hypothetical) versions
7196 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
7197 fix for bug 4533. Bugfix on 0.2.2.28-beta.
7198 - On Windows, we now define the _WIN32_WINNT macros only if they
7199 are not already defined. This lets the person building Tor decide,
7200 if they want, to require a later version of Windows.
7201 - Our autogen.sh script now uses autoreconf to launch autoconf,
7202 automake, and so on. This is more robust against some of the failure
7203 modes associated with running the autotools pieces on their own.
7204 - Running "make version" now displays the version of Tor that
7205 we're about to build. Idea from katmagic; resolves issue 4400.
7206 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
7207 on 0.2.2.4-alpha; fixes bug 3427.
7208 - New --enable-static-tor configure option for building Tor as
7209 statically as possible. Idea, general hackery and thoughts from
7210 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
7212 - Limited, experimental support for building with nmake and MSVC.
7214 o Build requirements:
7215 - Building Tor with bufferevent support now requires Libevent
7216 2.0.13-stable or later. Previous versions of Libevent had bugs in
7217 SSL-related bufferevents and related issues that would make Tor
7218 work badly with bufferevents. Requiring 2.0.13-stable also allows
7219 Tor with bufferevents to take advantage of Libevent APIs
7220 introduced after 2.0.8-rc.
7221 - Our build system requires automake 1.6 or later to create the
7222 Makefile.in files. Previously, you could have used 1.4.
7223 This only affects developers and people building Tor from git;
7224 people who build Tor from the source distribution without changing
7225 the Makefile.am files should be fine.
7226 - Detect when we try to build on a platform that doesn't define
7227 AF_UNSPEC to 0. We don't work there, so refuse to compile.
7229 o Build fixes (compile/link):
7230 - Format more doubles with %f, not %lf. Patch from grarpamp to make
7231 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
7233 - When building with --enable-static-tor on OpenBSD, do not
7234 erroneously attempt to link -lrt. Fixes bug 5103.
7235 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
7236 that IPv6 stuff will compile on MSVC, and compilation issues
7237 will be easier to track down. Fixes bug 5861.
7238 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
7239 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
7240 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
7241 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
7243 o Build fixes (other):
7244 - Use the _WIN32 macro throughout our code to detect Windows.
7245 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
7247 - Properly handle the case where the build-tree is not the same
7248 as the source tree when generating src/common/common_sha1.i,
7249 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
7250 bugfix on 0.2.0.1-alpha.
7251 - During configure, search for library containing cos function as
7252 libm lives in libcore on some platforms (BeOS/Haiku). Linking
7253 against libm was hard-coded before. Fixes the first part of bug
7254 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
7256 - Prevent a false positive from the check-spaces script, by disabling
7257 the "whitespace between function name and (" check for functions
7260 o Packaging (RPM) changes:
7261 - Update our default RPM spec files to work with mock and rpmbuild
7262 on RHEL/Fedora. They have an updated set of dependencies and
7263 conflicts, a fix for an ancient typo when creating the "_tor"
7264 user, and better instructions. Thanks to Ondrej Mikle for the
7265 patch series. Fixes bug 6043.
7266 - On OpenSUSE, create the /var/run/tor directory on startup if it
7267 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
7269 o Code refactoring (safety):
7270 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
7271 10 lines. Also, don't nest them. Doing so in the past has
7272 led to hard-to-debug code. The new style is to use the
7273 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
7274 - Use macros to indicate OpenSSL versions, so we don't need to worry
7275 about accidental hexadecimal bit shifts.
7276 - Use tor_sscanf() in place of scanf() in more places through the
7277 code. This makes us a little more locale-independent, and
7278 should help shut up code-analysis tools that can't tell
7279 a safe sscanf string from a dangerous one.
7280 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
7281 - Use the smartlist_add_asprintf() alias more consistently.
7283 o Code refactoring (consolidate):
7284 - A major revision to our internal node-selecting and listing logic.
7285 Tor already had at least two major ways to look at the question of
7286 "which Tor servers do we know about": a list of router descriptors,
7287 and a list of entries in the current consensus. With
7288 microdescriptors, we're adding a third. Having so many systems
7289 without an abstraction layer over them was hurting the codebase.
7290 Now, we have a new "node_t" abstraction that presents a consistent
7291 interface to a client's view of a Tor node, and holds (nearly) all
7292 of the mutable state formerly in routerinfo_t and routerstatus_t.
7293 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
7294 Libevent's notion of cached time when possible.
7295 - Remove duplicate code for invoking getrlimit() from control.c.
7296 - Use OpenSSL's built-in SSL_state_string_long() instead of our
7297 own homebrewed ssl_state_to_string() replacement. Patch from
7298 Emile Snyder. Fixes bug 4653.
7299 - Change the symmetric cipher interface so that creating and
7300 initializing a stream cipher are no longer separate functions.
7302 o Code refactoring (separate):
7303 - Make a new "entry connection" struct as an internal subtype of "edge
7304 connection", to simplify the code and make exit connections smaller.
7305 - Split connection_about_to_close() into separate functions for each
7307 - Rewrite the listener-selection logic so that parsing which ports
7308 we want to listen on is now separate from binding to the ports
7311 o Code refactoring (name changes):
7312 - Rename a handful of old identifiers, mostly related to crypto
7313 structures and crypto functions. By convention, our "create an
7314 object" functions are called "type_new()", our "free an object"
7315 functions are called "type_free()", and our types indicate that
7316 they are types only with a final "_t". But a handful of older
7317 types and functions broke these rules, with function names like
7318 "type_create" or "subsystem_op_type", or with type names like
7320 - Rename Tor functions that turn strings into addresses, so that
7321 "parse" indicates that no hostname resolution occurs, and
7322 "lookup" indicates that hostname resolution may occur. This
7323 should help prevent mistakes in the future. Fixes bug 3512.
7324 - Use the name "CERTS" consistently to refer to the new cell type;
7325 we were calling it CERT in some places and CERTS in others.
7326 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
7327 invalid value, rather than just -1.
7328 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
7329 can pick them up when the tests aren't disabled. Bugfix on
7330 0.2.2.4-alpha which introduced tinytest.
7332 o Code refactoring (other):
7333 - Defensively refactor rend_mid_rendezvous() so that protocol
7334 violations and length checks happen in the beginning. Fixes
7336 - Remove the pure attribute from all functions that used it
7337 previously. In many cases we assigned it incorrectly, because the
7338 functions might assert or call impure functions, and we don't have
7339 evidence that keeping the pure attribute is worthwhile. Implements
7340 changes suggested in ticket 4421.
7341 - Move the replay-detection cache for the RSA-encrypted parts of
7342 INTRODUCE2 cells to the introduction point data structures.
7343 Previously, we would use one replay-detection cache per hidden
7344 service. Required by fix for bug 3460.
7345 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
7346 no longer link against Libevent: they never used it, but
7347 our library structure used to force them to link it.
7349 o Removed features and files:
7350 - Remove all internal support for unpadded RSA. We never used it, and
7351 it would be a bad idea to start.
7352 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
7354 - Remove some redundant #include directives throughout the code.
7355 Patch from Andrea Gelmini.
7356 - Remove some old code to remember statistics about which descriptors
7357 we've served as a directory mirror. The feature wasn't used and
7358 is outdated now that microdescriptors are around.
7359 - Remove some old code to work around even older versions of Tor that
7360 used forked processes to handle DNS requests. Such versions of Tor
7361 are no longer in use as relays.
7362 - The "torify" script no longer supports the "tsocks" socksifier
7363 tool, since tsocks doesn't support DNS and UDP right for Tor.
7364 Everyone should be using torsocks instead. Fixes bugs 3530 and
7365 5180. Based on a patch by "ugh".
7366 - Remove the torrc.bridge file: we don't use it for anything, and
7367 it had become badly desynchronized from torrc.sample. Resolves
7371 - Begin a doc/state-contents.txt file to explain the contents of
7372 the Tor state file. Fixes bug 2987.
7373 - Clarify the documentation for the Alternate*Authority options.
7375 - Document the --defaults-torrc option, and the new semantics for
7376 overriding, extending, and clearing lists of options. Closes
7378 - Add missing man page documentation for consensus and microdesc
7379 files. Resolves ticket 6732.
7380 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
7382 o Documentation fixes:
7383 - Improve the manual's documentation for the NT Service command-line
7384 options. Addresses ticket 3964.
7385 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
7386 - Document the changes to the ORPort and DirPort options, and the
7387 fact that {OR/Dir}ListenAddress is now unnecessary (and
7388 therefore deprecated). Resolves ticket 5597.
7389 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
7390 - Clarify that hidden services are TCP only. Fixes bug 6024.
7393 Changes in version 0.2.2.39 - 2012-09-11
7394 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
7398 - Fix an assertion failure in tor_timegm() that could be triggered
7399 by a badly formatted directory object. Bug found by fuzzing with
7400 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
7401 - Do not crash when comparing an address with port value 0 to an
7402 address policy. This bug could have been used to cause a remote
7403 assertion failure by or against directory authorities, or to
7404 allow some applications to crash clients. Fixes bug 6690; bugfix
7408 Changes in version 0.2.2.38 - 2012-08-12
7409 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
7410 attack that could in theory leak path information.
7413 - Avoid an uninitialized memory read when reading a vote or consensus
7414 document that has an unrecognized flavor name. This read could
7415 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
7416 - Try to leak less information about what relays a client is
7417 choosing to a side-channel attacker. Previously, a Tor client would
7418 stop iterating through the list of available relays as soon as it
7419 had chosen one, thus finishing a little earlier when it picked
7420 a router earlier in the list. If an attacker can recover this
7421 timing information (nontrivial but not proven to be impossible),
7422 they could learn some coarse-grained information about which relays
7423 a client was picking (middle nodes in particular are likelier to
7424 be affected than exits). The timing attack might be mitigated by
7425 other factors (see bug 6537 for some discussion), but it's best
7426 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
7429 Changes in version 0.2.2.37 - 2012-06-06
7430 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
7431 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7435 - Work around a bug in OpenSSL that broke renegotiation with TLS
7436 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7437 the v2 Tor connection protocol when both sides were using OpenSSL
7438 1.0.1 would fail. Resolves ticket 6033.
7439 - When waiting for a client to renegotiate, don't allow it to add
7440 any bytes to the input buffer. This fixes a potential DoS issue.
7441 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7442 - Fix an edge case where if we fetch or publish a hidden service
7443 descriptor, we might build a 4-hop circuit and then use that circuit
7444 for exiting afterwards -- even if the new last hop doesn't obey our
7445 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7448 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7449 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7452 - Tell GCC and Clang to check for any errors in format strings passed
7453 to the tor_v*(print|scan)f functions.
7456 Changes in version 0.2.2.36 - 2012-05-24
7457 Tor 0.2.2.36 updates the addresses for two of the eight directory
7458 authorities, fixes some potential anonymity and security issues,
7459 and fixes several crash bugs.
7461 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
7462 known flaws, and nobody should be using them. You should upgrade. If
7463 you're using a Linux or BSD and its packages are obsolete, stop using
7464 those packages and upgrade anyway.
7466 o Directory authority changes:
7467 - Change IP address for maatuska (v3 directory authority).
7468 - Change IP address for ides (v3 directory authority), and rename
7472 - When building or running with any version of OpenSSL earlier
7473 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7474 versions have a bug (CVE-2011-4576) in which their block cipher
7475 padding includes uninitialized data, potentially leaking sensitive
7476 information to any peer with whom they make a SSLv3 connection. Tor
7477 does not use SSL v3 by default, but a hostile client or server
7478 could force an SSLv3 connection in order to gain information that
7479 they shouldn't have been able to get. The best solution here is to
7480 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7481 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7482 to make sure that the bug can't happen.
7483 - Never use a bridge or a controller-supplied node as an exit, even
7484 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7485 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7486 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7487 - Only build circuits if we have a sufficient threshold of the total
7488 descriptors that are marked in the consensus with the "Exit"
7489 flag. This mitigates an attack proposed by wanoskarnet, in which
7490 all of a client's bridges collude to restrict the exit nodes that
7491 the client knows about. Fixes bug 5343.
7492 - Provide controllers with a safer way to implement the cookie
7493 authentication mechanism. With the old method, if another locally
7494 running program could convince a controller that it was the Tor
7495 process, then that program could trick the controller into telling
7496 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7497 authentication method uses a challenge-response approach to prevent
7498 this attack. Fixes bug 5185; implements proposal 193.
7501 - Avoid logging uninitialized data when unable to decode a hidden
7502 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7503 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7504 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7506 - Fix builds when the path to sed, openssl, or sha1sum contains
7507 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7509 - Correct our replacements for the timeradd() and timersub() functions
7510 on platforms that lack them (for example, Windows). The timersub()
7511 function is used when expiring circuits, while timeradd() is
7512 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7513 bugfix on 0.2.2.24-alpha.
7514 - Fix the SOCKET_OK test that we use to tell when socket
7515 creation fails so that it works on Win64. Fixes part of bug 4533;
7516 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7519 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7520 Fixes bug 5346; bugfix on 0.0.8pre3.
7521 - Make our number-parsing functions always treat too-large values
7522 as an error, even when those values exceed the width of the
7523 underlying type. Previously, if the caller provided these
7524 functions with minima or maxima set to the extreme values of the
7525 underlying integer type, these functions would return those
7526 values on overflow rather than treating overflow as an error.
7527 Fixes part of bug 5786; bugfix on 0.0.9.
7528 - Older Linux kernels erroneously respond to strange nmap behavior
7529 by having accept() return successfully with a zero-length
7530 socket. When this happens, just close the connection. Previously,
7531 we would try harder to learn the remote address: but there was
7532 no such remote address to learn, and our method for trying to
7533 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7534 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7535 - Correct parsing of certain date types in parse_http_time().
7536 Without this patch, If-Modified-Since would behave
7537 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7538 Esteban Manchado Velázques.
7539 - Change the BridgePassword feature (part of the "bridge community"
7540 design, which is not yet implemented) to use a time-independent
7541 comparison. The old behavior might have allowed an adversary
7542 to use timing to guess the BridgePassword value. Fixes bug 5543;
7543 bugfix on 0.2.0.14-alpha.
7544 - Detect and reject certain misformed escape sequences in
7545 configuration values. Previously, these values would cause us
7546 to crash if received in a torrc file or over an authenticated
7547 control port. Bug found by Esteban Manchado Velázquez, and
7548 independently by Robert Connolly from Matta Consulting who further
7549 noted that it allows a post-authentication heap overflow. Patch
7550 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7551 bugfix on 0.2.0.16-alpha.
7552 - Fix a compile warning when using the --enable-openbsd-malloc
7553 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7554 - During configure, detect when we're building with clang version
7555 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7556 CFLAGS. clang doesn't support them yet.
7557 - When sending an HTTP/1.1 proxy request, include a Host header.
7558 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7559 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
7560 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
7561 - If we hit the error case where routerlist_insert() replaces an
7562 existing (old) server descriptor, make sure to remove that
7563 server descriptor from the old_routers list. Fix related to bug
7564 1776. Bugfix on 0.2.2.18-alpha.
7566 o Minor bugfixes (documentation and log messages):
7567 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7568 Fixes bug 4856; bugfix on Tor 0.0.6.
7569 - Update "ClientOnly" man page entry to explain that there isn't
7570 really any point to messing with it. Resolves ticket 5005.
7571 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7572 directory authority option (introduced in Tor 0.2.2.34).
7573 - Downgrade the "We're missing a certificate" message from notice
7574 to info: people kept mistaking it for a real problem, whereas it
7575 is seldom the problem even when we are failing to bootstrap. Fixes
7576 bug 5067; bugfix on 0.2.0.10-alpha.
7577 - Correctly spell "connect" in a log message on failure to create a
7578 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
7579 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7580 circuits. Fixes issue 5259.
7583 - Directory authorities now reject versions of Tor older than
7584 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7585 inclusive. These versions accounted for only a small fraction of
7586 the Tor network, and have numerous known security issues. Resolves
7588 - Update to the May 1 2012 Maxmind GeoLite Country database.
7591 - When sending or relaying a RELAY_EARLY cell, we used to convert
7592 it to a RELAY cell if the connection was using the v1 link
7593 protocol. This was a workaround for older versions of Tor, which
7594 didn't handle RELAY_EARLY cells properly. Now that all supported
7595 versions can handle RELAY_EARLY cells, and now that we're enforcing
7596 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7597 remove this workaround. Addresses bug 4786.
7600 Changes in version 0.2.2.35 - 2011-12-16
7601 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
7602 buffers code. Absolutely everybody should upgrade.
7604 The bug relied on an incorrect calculation when making data continuous
7605 in one of our IO buffers, if the first chunk of the buffer was
7606 misaligned by just the wrong amount. The miscalculation would allow an
7607 attacker to overflow a piece of heap-allocated memory. To mount this
7608 attack, the attacker would need to either open a SOCKS connection to
7609 Tor's SocksPort (usually restricted to localhost), or target a Tor
7610 instance configured to make its connections through a SOCKS proxy
7611 (which Tor does not do by default).
7613 Good security practice requires that all heap-overflow bugs should be
7614 presumed to be exploitable until proven otherwise, so we are treating
7615 this as a potential code execution attack. Please upgrade immediately!
7616 This bug does not affect bufferevents-based builds of Tor. Special
7617 thanks to "Vektor" for reporting this issue to us!
7619 Tor 0.2.2.35 also fixes several bugs in previous versions, including
7620 crash bugs for unusual configurations, and a long-term bug that
7621 would prevent Tor from starting on Windows machines with draconian
7624 With this release, we remind everyone that 0.2.0.x has reached its
7625 formal end-of-life. Those Tor versions have many known flaws, and
7626 nobody should be using them. You should upgrade -- ideally to the
7627 0.2.2.x series. If you're using a Linux or BSD and its packages are
7628 obsolete, stop using those packages and upgrade anyway.
7630 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
7631 longer receive support after some time in early 2012.
7634 - Fix a heap overflow bug that could occur when trying to pull
7635 data into the first chunk of a buffer, when that chunk had
7636 already had some data drained from it. Fixes CVE-2011-2778;
7637 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7638 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7639 that it doesn't attempt to allocate a socketpair. This could cause
7640 some problems on Windows systems with overzealous firewalls. Fix for
7641 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7643 - If we mark an OR connection for close based on a cell we process,
7644 don't process any further cells on it. We already avoid further
7645 reads on marked-for-close connections, but now we also discard the
7646 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7647 which was the first version where we might mark a connection for
7648 close based on processing a cell on it.
7649 - Correctly sanity-check that we don't underflow on a memory
7650 allocation (and then assert) for hidden service introduction
7651 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7652 bugfix on 0.2.1.5-alpha.
7653 - Fix a memory leak when we check whether a hidden service
7654 descriptor has any usable introduction points left. Fixes bug
7655 4424. Bugfix on 0.2.2.25-alpha.
7656 - Don't crash when we're running as a relay and don't have a GeoIP
7657 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
7658 we've had in the 0.2.3.x branch already.
7659 - When running as a client, do not print a misleading (and plain
7660 wrong) log message that we're collecting "directory request"
7661 statistics: clients don't collect statistics. Also don't create a
7662 useless (because empty) stats file in the stats/ directory. Fixes
7663 bug 4353; bugfix on 0.2.2.34.
7666 - Detect failure to initialize Libevent. This fix provides better
7667 detection for future instances of bug 4457.
7668 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7669 function. This was eating up hideously large amounts of time on some
7670 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7671 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7672 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7674 - Don't warn about unused log_mutex in log.c when building with
7675 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7676 0.1.0.6-rc which introduced --disable-threads.
7677 - When configuring, starting, or stopping an NT service, stop
7678 immediately after the service configuration attempt has succeeded
7679 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7680 - When sending a NETINFO cell, include the original address
7681 received for the other side, not its canonical address. Found
7682 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7683 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
7684 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7685 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7686 occurred when a client tried to fetch a descriptor for a bridge
7687 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7688 - Backport fixes for a pair of compilation warnings on Windows.
7689 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
7690 - If we had ever tried to call tor_addr_to_str on an address of
7691 unknown type, we would have done a strdup on an uninitialized
7692 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7693 Reported by "troll_un".
7694 - Correctly detect and handle transient lookup failures from
7695 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7696 Reported by "troll_un".
7697 - Fix null-pointer access that could occur if TLS allocation failed.
7698 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7699 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7700 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7703 - Add two new config options for directory authorities:
7704 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7705 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7706 that is always sufficient to satisfy the bandwidth requirement for
7707 the Guard flag. Now it will be easier for researchers to simulate
7708 Tor networks with different values. Resolves ticket 4484.
7709 - When Tor ignores a hidden service specified in its configuration,
7710 include the hidden service's directory in the warning message.
7711 Previously, we would only tell the user that some hidden service
7712 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7713 - Update to the December 6 2011 Maxmind GeoLite Country database.
7715 o Packaging changes:
7716 - Make it easier to automate expert package builds on Windows,
7717 by removing an absolute path from makensis.exe command.
7720 Changes in version 0.2.1.32 - 2011-12-16
7721 Tor 0.2.1.32 backports important security and privacy fixes for
7722 oldstable. This release is intended only for package maintainers and
7723 others who cannot use the 0.2.2 stable series. All others should be
7724 using Tor 0.2.2.x or newer.
7726 The Tor 0.2.1.x series will reach formal end-of-life some time in
7727 early 2012; we will stop releasing patches for it then.
7729 o Major bugfixes (also included in 0.2.2.x):
7730 - Correctly sanity-check that we don't underflow on a memory
7731 allocation (and then assert) for hidden service introduction
7732 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7733 bugfix on 0.2.1.5-alpha.
7734 - Fix a heap overflow bug that could occur when trying to pull
7735 data into the first chunk of a buffer, when that chunk had
7736 already had some data drained from it. Fixes CVE-2011-2778;
7737 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7740 - Update to the December 6 2011 Maxmind GeoLite Country database.
7743 Changes in version 0.2.2.34 - 2011-10-26
7744 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
7745 can deanonymize Tor users. Everybody should upgrade.
7747 The attack relies on four components: 1) Clients reuse their TLS cert
7748 when talking to different relays, so relays can recognize a user by
7749 the identity key in her cert. 2) An attacker who knows the client's
7750 identity key can probe each guard relay to see if that identity key
7751 is connected to that guard relay right now. 3) A variety of active
7752 attacks in the literature (starting from "Low-Cost Traffic Analysis
7753 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
7754 discover the guard relays that a Tor user visiting the website is using.
7755 4) Clients typically pick three guards at random, so the set of guards
7756 for a given user could well be a unique fingerprint for her. This
7757 release fixes components #1 and #2, which is enough to block the attack;
7758 the other two remain as open research problems. Special thanks to
7759 "frosty_un" for reporting the issue to us!
7761 Clients should upgrade so they are no longer recognizable by the TLS
7762 certs they present. Relays should upgrade so they no longer allow a
7763 remote attacker to probe them to test whether unpatched clients are
7764 currently connected to them.
7766 This release also fixes several vulnerabilities that allow an attacker
7767 to enumerate bridge relays. Some bridge enumeration attacks still
7768 remain; see for example proposal 188.
7770 o Privacy/anonymity fixes (clients):
7771 - Clients and bridges no longer send TLS certificate chains on
7772 outgoing OR connections. Previously, each client or bridge would
7773 use the same cert chain for all outgoing OR connections until
7774 its IP address changes, which allowed any relay that the client
7775 or bridge contacted to determine which entry guards it is using.
7776 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7777 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7778 no longer considers that connection as suitable for satisfying a
7779 circuit EXTEND request. Now relays can protect clients from the
7780 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7781 - Directory authorities no longer assign the Guard flag to relays
7782 that haven't upgraded to the above "refuse EXTEND requests
7783 to client connections" fix. Now directory authorities can
7784 protect clients from the CVE-2011-2768 issue even if neither
7785 the clients nor the relays have upgraded yet. There's a new
7786 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7787 to let us transition smoothly, else tomorrow there would be no
7790 o Privacy/anonymity fixes (bridge enumeration):
7791 - Bridge relays now do their directory fetches inside Tor TLS
7792 connections, like all the other clients do, rather than connecting
7793 directly to the DirPort like public relays do. Removes another
7794 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7795 - Bridges relays now build circuits for themselves in a more similar
7796 way to how clients build them. Removes another avenue for
7797 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7798 when bridges were introduced.
7799 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7800 that they initiated. Relays could distinguish incoming bridge
7801 connections from client connections, creating another avenue for
7802 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7803 Found by "frosty_un".
7806 - Fix a crash bug when changing node restrictions while a DNS lookup
7807 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7809 - Don't launch a useless circuit after failing to use one of a
7810 hidden service's introduction points. Previously, we would
7811 launch a new introduction circuit, but not set the hidden service
7812 which that circuit was intended to connect to, so it would never
7813 actually be used. A different piece of code would then create a
7814 new introduction circuit correctly. Bug reported by katmagic and
7815 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7818 - Change an integer overflow check in the OpenBSD_Malloc code so
7819 that GCC is less likely to eliminate it as impossible. Patch
7820 from Mansour Moufid. Fixes bug 4059.
7821 - When a hidden service turns an extra service-side introduction
7822 circuit into a general-purpose circuit, free the rend_data and
7823 intro_key fields first, so we won't leak memory if the circuit
7824 is cannibalized for use as another service-side introduction
7825 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7826 - Bridges now skip DNS self-tests, to act a little more stealthily.
7827 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7828 bridges. Patch by "warms0x".
7829 - Fix internal bug-checking logic that was supposed to catch
7830 failures in digest generation so that it will fail more robustly
7831 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7832 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7833 - Report any failure in init_keys() calls launched because our
7834 IP address has changed. Spotted by Coverity Scan. Bugfix on
7835 0.1.1.4-alpha; fixes CID 484.
7837 o Minor bugfixes (log messages and documentation):
7838 - Remove a confusing dollar sign from the example fingerprint in the
7839 man page, and also make the example fingerprint a valid one. Fixes
7840 bug 4309; bugfix on 0.2.1.3-alpha.
7841 - The next version of Windows will be called Windows 8, and it has
7842 a major version of 6, minor version of 2. Correctly identify that
7843 version instead of calling it "Very recent version". Resolves
7844 ticket 4153; reported by funkstar.
7845 - Downgrade log messages about circuit timeout calibration from
7846 "notice" to "info": they don't require or suggest any human
7847 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7848 bugfix on 0.2.2.14-alpha.
7851 - Turn on directory request statistics by default and include them in
7852 extra-info descriptors. Don't break if we have no GeoIP database.
7853 Backported from 0.2.3.1-alpha; implements ticket 3951.
7854 - Update to the October 4 2011 Maxmind GeoLite Country database.
7857 Changes in version 0.2.1.31 - 2011-10-26
7858 Tor 0.2.1.31 backports important security and privacy fixes for
7859 oldstable. This release is intended only for package maintainers and
7860 others who cannot use the 0.2.2 stable series. All others should be
7861 using Tor 0.2.2.x or newer.
7863 o Security fixes (also included in 0.2.2.x):
7864 - Replace all potentially sensitive memory comparison operations
7865 with versions whose runtime does not depend on the data being
7866 compared. This will help resist a class of attacks where an
7867 adversary can use variations in timing information to learn
7868 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7869 implementation by Robert Ransom based partially on code by DJB.)
7870 - Fix an assert in parsing router descriptors containing IPv6
7871 addresses. This one took down the directory authorities when
7872 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7874 o Privacy/anonymity fixes (also included in 0.2.2.x):
7875 - Clients and bridges no longer send TLS certificate chains on
7876 outgoing OR connections. Previously, each client or bridge would
7877 use the same cert chain for all outgoing OR connections until
7878 its IP address changes, which allowed any relay that the client
7879 or bridge contacted to determine which entry guards it is using.
7880 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7881 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7882 no longer considers that connection as suitable for satisfying a
7883 circuit EXTEND request. Now relays can protect clients from the
7884 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7885 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7886 that they initiated. Relays could distinguish incoming bridge
7887 connections from client connections, creating another avenue for
7888 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7889 Found by "frosty_un".
7890 - When receiving a hidden service descriptor, check that it is for
7891 the hidden service we wanted. Previously, Tor would store any
7892 hidden service descriptors that a directory gave it, whether it
7893 wanted them or not. This wouldn't have let an attacker impersonate
7894 a hidden service, but it did let directories pre-seed a client
7895 with descriptors that it didn't want. Bugfix on 0.0.6.
7896 - Avoid linkability based on cached hidden service descriptors: forget
7897 all hidden service descriptors cached as a client when processing a
7898 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7899 - Make the bridge directory authority refuse to answer directory
7900 requests for "all" descriptors. It used to include bridge
7901 descriptors in its answer, which was a major information leak.
7902 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7903 - Don't attach new streams to old rendezvous circuits after SIGNAL
7904 NEWNYM. Previously, we would keep using an existing rendezvous
7905 circuit if it remained open (i.e. if it were kept open by a
7906 long-lived stream, or if a new stream were attached to it before
7907 Tor could notice that it was old and no longer in use). Bugfix on
7908 0.1.1.15-rc; fixes bug 3375.
7910 o Minor bugfixes (also included in 0.2.2.x):
7911 - When we restart our relay, we might get a successful connection
7912 from the outside before we've started our reachability tests,
7913 triggering a warning: "ORPort found reachable, but I have no
7914 routerinfo yet. Failing to inform controller of success." This
7915 bug was harmless unless Tor is running under a controller
7916 like Vidalia, in which case the controller would never get a
7917 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
7919 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7920 enabled. Fixes bug 1526.
7921 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7922 anything since 0.2.1.16-rc.
7923 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7924 None of the cases where we did this before were wrong, but by making
7925 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7926 - Fix a rare crash bug that could occur when a client was configured
7927 with a large number of bridges. Fixes bug 2629; bugfix on
7928 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7929 - Correct the warning displayed when a rendezvous descriptor exceeds
7930 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7932 - Fix an uncommon assertion failure when running with DNSPort under
7933 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7934 - When warning about missing zlib development packages during compile,
7935 give the correct package names. Bugfix on 0.2.0.1-alpha.
7936 - Require that introduction point keys and onion keys have public
7937 exponent 65537. Bugfix on 0.2.0.10-alpha.
7938 - Do not crash when our configuration file becomes unreadable, for
7939 example due to a permissions change, between when we start up
7940 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7942 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7944 - Always NUL-terminate the sun_path field of a sockaddr_un before
7945 passing it to the kernel. (Not a security issue: kernels are
7946 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7947 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7948 - Don't stack-allocate the list of supplementary GIDs when we're
7949 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7950 could take up to 256K, which is way too much stack. Found by
7951 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7953 o Minor bugfixes (only in 0.2.1.x):
7954 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
7955 rely on them. Bugfix on 0.2.1.30.
7956 - Use git revisions instead of svn revisions when generating our
7957 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7959 o Minor features (also included in 0.2.2.x):
7960 - Adjust the expiration time on our SSL session certificates to
7961 better match SSL certs seen in the wild. Resolves ticket 4014.
7962 - Allow nameservers with IPv6 address. Resolves bug 2574.
7963 - Update to the October 4 2011 Maxmind GeoLite Country database.
7966 Changes in version 0.2.2.33 - 2011-09-13
7967 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
7968 TLS handshake that makes relays and bridges that run this new version
7969 reachable from Iran again.
7972 - Avoid an assertion failure when reloading a configuration with
7973 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7974 3923; bugfix on 0.2.2.25-alpha.
7976 o Minor features (security):
7977 - Check for replays of the public-key encrypted portion of an
7978 INTRODUCE1 cell, in addition to the current check for replays of
7979 the g^x value. This prevents a possible class of active attacks
7980 by an attacker who controls both an introduction point and a
7981 rendezvous point, and who uses the malleability of AES-CTR to
7982 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7983 that these attacks are infeasible (requiring the attacker to send
7984 on the order of zettabytes of altered cells in a short interval),
7985 but we'd rather block them off in case there are any classes of
7986 this attack that we missed. Reported by Willem Pinckaers.
7989 - Adjust the expiration time on our SSL session certificates to
7990 better match SSL certs seen in the wild. Resolves ticket 4014.
7991 - Change the default required uptime for a relay to be accepted as
7992 a HSDir (hidden service directory) from 24 hours to 25 hours.
7993 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7994 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7995 authorities to abstain from voting on assignment of the HSDir
7996 consensus flag. Related to bug 2649.
7997 - Update to the September 6 2011 Maxmind GeoLite Country database.
7999 o Minor bugfixes (documentation and log messages):
8000 - Correct the man page to explain that HashedControlPassword and
8001 CookieAuthentication can both be set, in which case either method
8002 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8003 when we decided to allow these config options to both be set. Issue
8005 - Demote the 'replay detected' log message emitted when a hidden
8006 service receives the same Diffie-Hellman public key in two different
8007 INTRODUCE2 cells to info level. A normal Tor client can cause that
8008 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8009 fixes part of bug 2442.
8010 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8011 level. There is nothing that a hidden service's operator can do
8012 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8014 - Clarify a log message specifying the characters permitted in
8015 HiddenServiceAuthorizeClient client names. Previously, the log
8016 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8017 given the impression that every ASCII character between "+" and "_"
8018 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8021 - Provide a substitute implementation of lround() for MSVC, which
8022 apparently lacks it. Patch from Gisle Vanem.
8023 - Clean up some code issues that prevented Tor from building on older
8024 BSDs. Fixes bug 3894; reported by "grarpamp".
8025 - Search for a platform-specific version of "ar" when cross-compiling.
8026 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8029 Changes in version 0.2.2.32 - 2011-08-27
8030 The Tor 0.2.2 release series is dedicated to the memory of Andreas
8031 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
8032 a founder of the PETS community, a leader in our field, a mentor,
8033 and a friend. He left us with these words: "I had the possibility
8034 to contribute to this world that is not as it should be. I hope I
8035 could help in some areas to make the world a better place, and that
8036 I could also encourage other people to be engaged in improving the
8037 world. Please, stay engaged. This world needs you, your love, your
8038 initiative -- now I cannot be part of that anymore."
8040 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
8041 ready. More than two years in the making, this release features improved
8042 client performance and hidden service reliability, better compatibility
8043 for Android, correct behavior for bridges that listen on more than
8044 one address, more extensible and flexible directory object handling,
8045 better reporting of network statistics, improved code security, and
8046 many many other features and bugfixes.
8048 o Major features (client performance):
8049 - When choosing which cells to relay first, relays now favor circuits
8050 that have been quiet recently, to provide lower latency for
8051 low-volume circuits. By default, relays enable or disable this
8052 feature based on a setting in the consensus. They can override
8053 this default by using the new "CircuitPriorityHalflife" config
8054 option. Design and code by Ian Goldberg, Can Tang, and Chris
8056 - Directory authorities now compute consensus weightings that instruct
8057 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
8058 and no flag. Clients use these weightings to distribute network load
8059 more evenly across these different relay types. The weightings are
8060 in the consensus so we can change them globally in the future. Extra
8061 thanks to "outofwords" for finding some nasty security bugs in
8062 the first implementation of this feature.
8064 o Major features (client performance, circuit build timeout):
8065 - Tor now tracks how long it takes to build client-side circuits
8066 over time, and adapts its timeout to local network performance.
8067 Since a circuit that takes a long time to build will also provide
8068 bad performance, we get significant latency improvements by
8069 discarding the slowest 20% of circuits. Specifically, Tor creates
8070 circuits more aggressively than usual until it has enough data
8071 points for a good timeout estimate. Implements proposal 151.
8072 - Circuit build timeout constants can be controlled by consensus
8073 parameters. We set good defaults for these parameters based on
8074 experimentation on broadband and simulated high-latency links.
8075 - Circuit build time learning can be disabled via consensus parameter
8076 or by the client via a LearnCircuitBuildTimeout config option. We
8077 also automatically disable circuit build time calculation if either
8078 AuthoritativeDirectory is set, or if we fail to write our state
8079 file. Implements ticket 1296.
8081 o Major features (relays use their capacity better):
8082 - Set SO_REUSEADDR socket option on all sockets, not just
8083 listeners. This should help busy exit nodes avoid running out of
8084 useable ports just because all the ports have been used in the
8085 near past. Resolves issue 2850.
8086 - Relays now save observed peak bandwidth throughput rates to their
8087 state file (along with total usage, which was already saved),
8088 so that they can determine their correct estimated bandwidth on
8089 restart. Resolves bug 1863, where Tor relays would reset their
8090 estimated bandwidth to 0 after restarting.
8091 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
8092 should give us approximately 40-50% more Guard-flagged nodes,
8093 improving the anonymity the Tor network can provide and also
8094 decreasing the dropoff in throughput that relays experience when
8095 they first get the Guard flag.
8096 - Directory authorities now take changes in router IP address and
8097 ORPort into account when determining router stability. Previously,
8098 if a router changed its IP or ORPort, the authorities would not
8099 treat it as having any downtime for the purposes of stability
8100 calculation, whereas clients would experience downtime since the
8101 change would take a while to propagate to them. Resolves issue 1035.
8102 - New AccelName and AccelDir options add support for dynamic OpenSSL
8103 hardware crypto acceleration engines.
8105 o Major features (relays control their load better):
8106 - Exit relays now try harder to block exit attempts from unknown
8107 relays, to make it harder for people to use them as one-hop proxies
8108 a la tortunnel. Controlled by the refuseunknownexits consensus
8109 parameter (currently enabled), or you can override it on your
8110 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
8111 based on a variant of proposal 163.
8112 - Add separate per-conn write limiting to go with the per-conn read
8113 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
8114 but never per-conn write limits.
8115 - New consensus params "bwconnrate" and "bwconnburst" to let us
8116 rate-limit client connections as they enter the network. It's
8117 controlled in the consensus so we can turn it on and off for
8118 experiments. It's starting out off. Based on proposal 163.
8120 o Major features (controllers):
8121 - Export GeoIP information on bridge usage to controllers even if we
8122 have not yet been running for 24 hours. Now Vidalia bridge operators
8123 can get more accurate and immediate feedback about their
8124 contributions to the network.
8125 - Add an __OwningControllerProcess configuration option and a
8126 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
8127 that when it exits, Tor will shut down. Implements feature 3049.
8129 o Major features (directory authorities):
8130 - Directory authorities now create, vote on, and serve multiple
8131 parallel formats of directory data as part of their voting process.
8132 Partially implements Proposal 162: "Publish the consensus in
8134 - Directory authorities now agree on and publish small summaries
8135 of router information that clients can use in place of regular
8136 server descriptors. This transition will allow Tor 0.2.3 clients
8137 to use far less bandwidth for downloading information about the
8138 network. Begins the implementation of Proposal 158: "Clients
8139 download consensus + microdescriptors".
8140 - The directory voting system is now extensible to use multiple hash
8141 algorithms for signatures and resource selection. Newer formats
8142 are signed with SHA256, with a possibility for moving to a better
8143 hash algorithm in the future.
8144 - Directory authorities can now vote on arbitary integer values as
8145 part of the consensus process. This is designed to help set
8146 network-wide parameters. Implements proposal 167.
8148 o Major features and bugfixes (node selection):
8149 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
8150 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
8151 options. Previously, we had been ambiguous in describing what
8152 counted as an "exit" node, and what operations exactly "StrictNodes
8153 0" would permit. This created confusion when people saw nodes built
8154 through unexpected circuits, and made it hard to tell real bugs from
8155 surprises. Now the intended behavior is:
8156 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
8157 a node that delivers user traffic outside the Tor network.
8158 . "Entry", in the context of EntryNodes, means a node used as the
8159 first hop of a multihop circuit. It doesn't include direct
8160 connections to directory servers.
8161 . "ExcludeNodes" applies to all nodes.
8162 . "StrictNodes" changes the behavior of ExcludeNodes only. When
8163 StrictNodes is set, Tor should avoid all nodes listed in
8164 ExcludeNodes, even when it will make user requests fail. When
8165 StrictNodes is *not* set, then Tor should follow ExcludeNodes
8166 whenever it can, except when it must use an excluded node to
8167 perform self-tests, connect to a hidden service, provide a
8168 hidden service, fulfill a .exit request, upload directory
8169 information, or fetch directory information.
8170 Collectively, the changes to implement the behavior fix bug 1090.
8171 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
8172 change during a config reload, mark and discard all our origin
8173 circuits. This fix should address edge cases where we change the
8174 config options and but then choose a circuit that we created before
8176 - Make EntryNodes config option much more aggressive even when
8177 StrictNodes is not set. Before it would prepend your requested
8178 entrynodes to your list of guard nodes, but feel free to use others
8179 after that. Now it chooses only from your EntryNodes if any of
8180 those are available, and only falls back to others if a) they're
8181 all down and b) StrictNodes is not set.
8182 - Now we refresh your entry guards from EntryNodes at each consensus
8183 fetch -- rather than just at startup and then they slowly rot as
8184 the network changes.
8185 - Add support for the country code "{??}" in torrc options like
8186 ExcludeNodes, to indicate all routers of unknown country. Closes
8188 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
8189 a node is listed in both, it's treated as excluded.
8190 - ExcludeNodes now applies to directory nodes -- as a preference if
8191 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
8192 Don't exclude all the directory authorities and set StrictNodes to 1
8193 unless you really want your Tor to break.
8194 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
8195 - ExcludeExitNodes now overrides .exit requests.
8196 - We don't use bridges listed in ExcludeNodes.
8197 - When StrictNodes is 1:
8198 . We now apply ExcludeNodes to hidden service introduction points
8199 and to rendezvous points selected by hidden service users. This
8200 can make your hidden service less reliable: use it with caution!
8201 . If we have used ExcludeNodes on ourself, do not try relay
8202 reachability self-tests.
8203 . If we have excluded all the directory authorities, we will not
8204 even try to upload our descriptor if we're a relay.
8205 . Do not honor .exit requests to an excluded node.
8206 - When the set of permitted nodes changes, we now remove any mappings
8207 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
8209 - We never cannibalize a circuit that had excluded nodes on it, even
8210 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
8211 - Improve log messages related to excluded nodes.
8213 o Major features (misc):
8214 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
8215 to help Tor build correctly for Android phones.
8216 - The options SocksPort, ControlPort, and so on now all accept a
8217 value "auto" that opens a socket on an OS-selected port. A
8218 new ControlPortWriteToFile option tells Tor to write its
8219 actual control port or ports to a chosen file. If the option
8220 ControlPortFileGroupReadable is set, the file is created as
8221 group-readable. Now users can run two Tor clients on the same
8222 system without needing to manually mess with parameters. Resolves
8223 part of ticket 3076.
8224 - Tor now supports tunneling all of its outgoing connections over
8225 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
8226 configuration options. Code by Christopher Davis.
8228 o Code security improvements:
8229 - Replace all potentially sensitive memory comparison operations
8230 with versions whose runtime does not depend on the data being
8231 compared. This will help resist a class of attacks where an
8232 adversary can use variations in timing information to learn
8233 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8234 implementation by Robert Ransom based partially on code by DJB.)
8235 - Enable Address Space Layout Randomization (ASLR) and Data Execution
8236 Prevention (DEP) by default on Windows to make it harder for
8237 attackers to exploit vulnerabilities. Patch from John Brooks.
8238 - New "--enable-gcc-hardening" ./configure flag (off by default)
8239 to turn on gcc compile time hardening options. It ensures
8240 that signed ints have defined behavior (-fwrapv), enables
8241 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
8242 with canaries (-fstack-protector-all), turns on ASLR protection if
8243 supported by the kernel (-fPIE, -pie), and adds additional security
8244 related warnings. Verified to work on Mac OS X and Debian Lenny.
8245 - New "--enable-linker-hardening" ./configure flag (off by default)
8246 to turn on ELF specific hardening features (relro, now). This does
8247 not work with Mac OS X or any other non-ELF binary format.
8248 - Always search the Windows system directory for system DLLs, and
8249 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
8250 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
8251 current and future memory pages via mlockall(). On supported
8252 platforms (modern Linux and probably BSD but not Windows or OS X),
8253 this should effectively disable any and all attempts to page out
8254 memory. This option requires that you start your Tor as root --
8255 if you use DisableAllSwap, please consider using the User option
8256 to properly reduce the privileges of your Tor.
8258 o Major bugfixes (crashes):
8259 - Fix crash bug on platforms where gmtime and localtime can return
8260 NULL. Windows 7 users were running into this one. Fixes part of bug
8261 2077. Bugfix on all versions of Tor. Found by boboper.
8262 - Introduce minimum/maximum values that clients will believe
8263 from the consensus. Now we'll have a better chance to avoid crashes
8264 or worse when a consensus param has a weird value.
8265 - Fix a rare crash bug that could occur when a client was configured
8266 with a large number of bridges. Fixes bug 2629; bugfix on
8267 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8268 - Do not crash when our configuration file becomes unreadable, for
8269 example due to a permissions change, between when we start up
8270 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8272 - If we're in the pathological case where there's no exit bandwidth
8273 but there is non-exit bandwidth, or no guard bandwidth but there
8274 is non-guard bandwidth, don't crash during path selection. Bugfix
8276 - Fix a crash bug when trying to initialize the evdns module in
8277 Libevent 2. Bugfix on 0.2.1.16-rc.
8279 o Major bugfixes (stability):
8280 - Fix an assert in parsing router descriptors containing IPv6
8281 addresses. This one took down the directory authorities when
8282 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8283 - Fix an uncommon assertion failure when running with DNSPort under
8284 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8285 - Treat an unset $HOME like an empty $HOME rather than triggering an
8286 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
8287 - More gracefully handle corrupt state files, removing asserts
8288 in favor of saving a backup and resetting state.
8289 - Instead of giving an assertion failure on an internal mismatch
8290 on estimated freelist size, just log a BUG warning and try later.
8291 Mitigates but does not fix bug 1125.
8292 - Fix an assert that got triggered when using the TestingTorNetwork
8293 configuration option and then issuing a GETINFO config-text control
8294 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
8295 - If the cached cert file is unparseable, warn but don't exit.
8297 o Privacy fixes (relays/bridges):
8298 - Don't list Windows capabilities in relay descriptors. We never made
8299 use of them, and maybe it's a bad idea to publish them. Bugfix
8301 - If the Nickname configuration option isn't given, Tor would pick a
8302 nickname based on the local hostname as the nickname for a relay.
8303 Because nicknames are not very important in today's Tor and the
8304 "Unnamed" nickname has been implemented, this is now problematic
8305 behavior: It leaks information about the hostname without being
8306 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
8307 introduced the Unnamed nickname. Reported by tagnaq.
8308 - Maintain separate TLS contexts and certificates for incoming and
8309 outgoing connections in bridge relays. Previously we would use the
8310 same TLS contexts and certs for incoming and outgoing connections.
8311 Bugfix on 0.2.0.3-alpha; addresses bug 988.
8312 - Maintain separate identity keys for incoming and outgoing TLS
8313 contexts in bridge relays. Previously we would use the same
8314 identity keys for incoming and outgoing TLS contexts. Bugfix on
8315 0.2.0.3-alpha; addresses the other half of bug 988.
8316 - Make the bridge directory authority refuse to answer directory
8317 requests for "all descriptors". It used to include bridge
8318 descriptors in its answer, which was a major information leak.
8319 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8321 o Privacy fixes (clients):
8322 - When receiving a hidden service descriptor, check that it is for
8323 the hidden service we wanted. Previously, Tor would store any
8324 hidden service descriptors that a directory gave it, whether it
8325 wanted them or not. This wouldn't have let an attacker impersonate
8326 a hidden service, but it did let directories pre-seed a client
8327 with descriptors that it didn't want. Bugfix on 0.0.6.
8328 - Start the process of disabling ".exit" address notation, since it
8329 can be used for a variety of esoteric application-level attacks
8330 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
8332 - Reject attempts at the client side to open connections to private
8333 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
8334 a randomly chosen exit node. Attempts to do so are always
8335 ill-defined, generally prevented by exit policies, and usually
8336 in error. This will also help to detect loops in transparent
8337 proxy configurations. You can disable this feature by setting
8338 "ClientRejectInternalAddresses 0" in your torrc.
8339 - Log a notice when we get a new control connection. Now it's easier
8340 for security-conscious users to recognize when a local application
8341 is knocking on their controller door. Suggested by bug 1196.
8343 o Privacy fixes (newnym):
8344 - Avoid linkability based on cached hidden service descriptors: forget
8345 all hidden service descriptors cached as a client when processing a
8346 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8347 - On SIGHUP, do not clear out all TrackHostExits mappings, client
8348 DNS cache entries, and virtual address mappings: that's what
8349 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
8350 - Don't attach new streams to old rendezvous circuits after SIGNAL
8351 NEWNYM. Previously, we would keep using an existing rendezvous
8352 circuit if it remained open (i.e. if it were kept open by a
8353 long-lived stream, or if a new stream were attached to it before
8354 Tor could notice that it was old and no longer in use). Bugfix on
8355 0.1.1.15-rc; fixes bug 3375.
8357 o Major bugfixes (relay bandwidth accounting):
8358 - Fix a bug that could break accounting on 64-bit systems with large
8359 time_t values, making them hibernate for impossibly long intervals.
8360 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
8361 - Fix a bug in bandwidth accounting that could make us use twice
8362 the intended bandwidth when our interval start changes due to
8363 daylight saving time. Now we tolerate skew in stored vs computed
8364 interval starts: if the start of the period changes by no more than
8365 50% of the period's duration, we remember bytes that we transferred
8366 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
8368 o Major bugfixes (bridges):
8369 - Bridges now use "reject *:*" as their default exit policy. Bugfix
8370 on 0.2.0.3-alpha. Fixes bug 1113.
8371 - If you configure your bridge with a known identity fingerprint,
8372 and the bridge authority is unreachable (as it is in at least
8373 one country now), fall back to directly requesting the descriptor
8374 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
8376 - Fix a bug where bridge users who configure the non-canonical
8377 address of a bridge automatically switch to its canonical
8378 address. If a bridge listens at more than one address, it
8379 should be able to advertise those addresses independently and
8380 any non-blocked addresses should continue to work. Bugfix on Tor
8381 0.2.0.3-alpha. Fixes bug 2510.
8382 - If you configure Tor to use bridge A, and then quit and
8383 configure Tor to use bridge B instead (or if you change Tor
8384 to use bridge B via the controller), it would happily continue
8385 to use bridge A if it's still reachable. While this behavior is
8386 a feature if your goal is connectivity, in some scenarios it's a
8387 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
8388 - When the controller configures a new bridge, don't wait 10 to 60
8389 seconds before trying to fetch its descriptor. Bugfix on
8390 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
8392 o Major bugfixes (directory authorities):
8393 - Many relays have been falling out of the consensus lately because
8394 not enough authorities know about their descriptor for them to get
8395 a majority of votes. When we deprecated the v2 directory protocol,
8396 we got rid of the only way that v3 authorities can hear from each
8397 other about other descriptors. Now authorities examine every v3
8398 vote for new descriptors, and fetch them from that authority. Bugfix
8400 - Authorities could be tricked into giving out the Exit flag to relays
8401 that didn't allow exiting to any ports. This bug could screw
8402 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
8403 1238. Bug discovered by Martin Kowalczyk.
8404 - If all authorities restart at once right before a consensus vote,
8405 nobody will vote about "Running", and clients will get a consensus
8406 with no usable relays. Instead, authorities refuse to build a
8407 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
8409 o Major bugfixes (stream-level fairness):
8410 - When receiving a circuit-level SENDME for a blocked circuit, try
8411 to package cells fairly from all the streams that had previously
8412 been blocked on that circuit. Previously, we had started with the
8413 oldest stream, and allowed each stream to potentially exhaust
8414 the circuit's package window. This gave older streams on any
8415 given circuit priority over newer ones. Fixes bug 1937. Detected
8416 originally by Camilo Viecco. This bug was introduced before the
8417 first Tor release, in svn commit r152: it is the new winner of
8418 the longest-lived bug prize.
8419 - Fix a stream fairness bug that would cause newer streams on a given
8420 circuit to get preference when reading bytes from the origin or
8421 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
8422 introduced before the first Tor release, in svn revision r152.
8423 - When the exit relay got a circuit-level sendme cell, it started
8424 reading on the exit streams, even if had 500 cells queued in the
8425 circuit queue already, so the circuit queue just grew and grew in
8426 some cases. We fix this by not re-enabling reading on receipt of a
8427 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
8428 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
8430 - Newly created streams were allowed to read cells onto circuits,
8431 even if the circuit's cell queue was blocked and waiting to drain.
8432 This created potential unfairness, as older streams would be
8433 blocked, but newer streams would gladly fill the queue completely.
8434 We add code to detect this situation and prevent any stream from
8435 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
8438 o Major bugfixes (hidden services):
8439 - Apply circuit timeouts to opened hidden-service-related circuits
8440 based on the correct start time. Previously, we would apply the
8441 circuit build timeout based on time since the circuit's creation;
8442 it was supposed to be applied based on time since the circuit
8443 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
8444 - Improve hidden service robustness: When we find that we have
8445 extended a hidden service's introduction circuit to a relay not
8446 listed as an introduction point in the HS descriptor we currently
8447 have, retry with an introduction point from the current
8448 descriptor. Previously we would just give up. Fixes bugs 1024 and
8449 1930; bugfix on 0.2.0.10-alpha.
8450 - Directory authorities now use data collected from their own
8451 uptime observations when choosing whether to assign the HSDir flag
8452 to relays, instead of trusting the uptime value the relay reports in
8453 its descriptor. This change helps prevent an attack where a small
8454 set of nodes with frequently-changing identity keys can blackhole
8455 a hidden service. (Only authorities need upgrade; others will be
8456 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
8457 - Stop assigning the HSDir flag to relays that disable their
8458 DirPort (and thus will refuse to answer directory requests). This
8459 fix should dramatically improve the reachability of hidden services:
8460 hidden services and hidden service clients pick six HSDir relays
8461 to store and retrieve the hidden service descriptor, and currently
8462 about half of the HSDir relays will refuse to work. Bugfix on
8463 0.2.0.10-alpha; fixes part of bug 1693.
8465 o Major bugfixes (misc):
8466 - Clients now stop trying to use an exit node associated with a given
8467 destination by TrackHostExits if they fail to reach that exit node.
8468 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
8469 - Fix a regression that caused Tor to rebind its ports if it receives
8470 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
8471 - Remove an extra pair of quotation marks around the error
8472 message in control-port STATUS_GENERAL BUG events. Bugfix on
8473 0.1.2.6-alpha; fixes bug 3732.
8475 o Minor features (relays):
8476 - Ensure that no empty [dirreq-](read|write)-history lines are added
8477 to an extrainfo document. Implements ticket 2497.
8478 - When bandwidth accounting is enabled, be more generous with how
8479 much bandwidth we'll use up before entering "soft hibernation".
8480 Previously, we'd refuse new connections and circuits once we'd
8481 used up 95% of our allotment. Now, we use up 95% of our allotment,
8482 AND make sure that we have no more than 500MB (or 3 hours of
8483 expected traffic, whichever is lower) remaining before we enter
8485 - Relays now log the reason for publishing a new relay descriptor,
8486 so we have a better chance of hunting down instances of bug 1810.
8487 Resolves ticket 3252.
8488 - Log a little more clearly about the times at which we're no longer
8489 accepting new connections (e.g. due to hibernating). Resolves
8491 - When AllowSingleHopExits is set, print a warning to explain to the
8492 relay operator why most clients are avoiding her relay.
8493 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
8494 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
8495 clients are already deprecated because of security bugs.
8497 o Minor features (network statistics):
8498 - Directory mirrors that set "DirReqStatistics 1" write statistics
8499 about directory requests to disk every 24 hours. As compared to the
8500 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
8501 improvements: 1) stats are written to disk exactly every 24 hours;
8502 2) estimated shares of v2 and v3 requests are determined as mean
8503 values, not at the end of a measurement period; 3) unresolved
8504 requests are listed with country code '??'; 4) directories also
8505 measure download times.
8506 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
8507 number of exit streams and transferred bytes per port to disk every
8509 - Relays that set "CellStatistics 1" write statistics on how long
8510 cells spend in their circuit queues to disk every 24 hours.
8511 - Entry nodes that set "EntryStatistics 1" write statistics on the
8512 rough number and origins of connecting clients to disk every 24
8514 - Relays that write any of the above statistics to disk and set
8515 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
8516 their extra-info documents. Implements proposal 166.
8518 o Minor features (GeoIP and statistics):
8519 - Provide a log message stating which geoip file we're parsing
8520 instead of just stating that we're parsing the geoip file.
8521 Implements ticket 2432.
8522 - Make sure every relay writes a state file at least every 12 hours.
8523 Previously, a relay could go for weeks without writing its state
8524 file, and on a crash could lose its bandwidth history, capacity
8525 estimates, client country statistics, and so on. Addresses bug 3012.
8526 - Relays report the number of bytes spent on answering directory
8527 requests in extra-info descriptors similar to {read,write}-history.
8528 Implements enhancement 1790.
8529 - Report only the top 10 ports in exit-port stats in order not to
8530 exceed the maximum extra-info descriptor length of 50 KB. Implements
8532 - If writing the state file to disk fails, wait up to an hour before
8533 retrying again, rather than trying again each second. Fixes bug
8534 2346; bugfix on Tor 0.1.1.3-alpha.
8535 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
8536 when we switch from being a public relay to a bridge. Otherwise
8537 there will still be clients that see the relay in their consensus,
8538 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
8540 - Update to the August 2 2011 Maxmind GeoLite Country database.
8542 o Minor features (clients):
8543 - When expiring circuits, use microsecond timers rather than
8544 one-second timers. This can avoid an unpleasant situation where a
8545 circuit is launched near the end of one second and expired right
8546 near the beginning of the next, and prevent fluctuations in circuit
8548 - If we've configured EntryNodes and our network goes away and/or all
8549 our entrynodes get marked down, optimistically retry them all when
8550 a new socks application request appears. Fixes bug 1882.
8551 - Always perform router selections using weighted relay bandwidth,
8552 even if we don't need a high capacity circuit at the time. Non-fast
8553 circuits now only differ from fast ones in that they can use relays
8554 not marked with the Fast flag. This "feature" could turn out to
8555 be a horrible bug; we should investigate more before it goes into
8557 - When we run out of directory information such that we can't build
8558 circuits, but then get enough that we can build circuits, log when
8559 we actually construct a circuit, so the user has a better chance of
8560 knowing what's going on. Fixes bug 1362.
8561 - Log SSL state transitions at debug level during handshake, and
8562 include SSL states in error messages. This may help debug future
8563 SSL handshake issues.
8565 o Minor features (directory authorities):
8566 - When a router changes IP address or port, authorities now launch
8567 a new reachability test for it. Implements ticket 1899.
8568 - Directory authorities now reject relays running any versions of
8569 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
8570 known bugs that keep RELAY_EARLY cells from working on rendezvous
8571 circuits. Followup to fix for bug 2081.
8572 - Directory authorities now reject relays running any version of Tor
8573 older than 0.2.0.26-rc. That version is the earliest that fetches
8574 current directory information correctly. Fixes bug 2156.
8575 - Directory authorities now do an immediate reachability check as soon
8576 as they hear about a new relay. This change should slightly reduce
8577 the time between setting up a relay and getting listed as running
8578 in the consensus. It should also improve the time between setting
8579 up a bridge and seeing use by bridge users.
8580 - Directory authorities no longer launch a TLS connection to every
8581 relay as they startup. Now that we have 2k+ descriptors cached,
8582 the resulting network hiccup is becoming a burden. Besides,
8583 authorities already avoid voting about Running for the first half
8584 hour of their uptime.
8585 - Directory authorities now log the source of a rejected POSTed v3
8586 networkstatus vote, so we can track failures better.
8587 - Backport code from 0.2.3.x that allows directory authorities to
8588 clean their microdescriptor caches. Needed to resolve bug 2230.
8590 o Minor features (hidden services):
8591 - Use computed circuit-build timeouts to decide when to launch
8592 parallel introduction circuits for hidden services. (Previously,
8593 we would retry after 15 seconds.)
8594 - Don't allow v0 hidden service authorities to act as clients.
8595 Required by fix for bug 3000.
8596 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
8597 by fix for bug 3000.
8598 - Make hidden services work better in private Tor networks by not
8599 requiring any uptime to join the hidden service descriptor
8600 DHT. Implements ticket 2088.
8601 - Log (at info level) when purging pieces of hidden-service-client
8602 state because of SIGNAL NEWNYM.
8604 o Minor features (controller interface):
8605 - New "GETINFO net/listeners/(type)" controller command to return
8606 a list of addresses and ports that are bound for listeners for a
8607 given connection type. This is useful when the user has configured
8608 "SocksPort auto" and the controller needs to know which port got
8609 chosen. Resolves another part of ticket 3076.
8610 - Have the controller interface give a more useful message than
8611 "Internal Error" in response to failed GETINFO requests.
8612 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
8613 event, to give information on the current rate of circuit timeouts
8614 over our stored history.
8615 - The 'EXTENDCIRCUIT' control port command can now be used with
8616 a circ id of 0 and no path. This feature will cause Tor to build
8617 a new 'fast' general purpose circuit using its own path selection
8619 - Added a BUILDTIMEOUT_SET controller event to describe changes
8620 to the circuit build timeout.
8621 - New controller command "getinfo config-text". It returns the
8622 contents that Tor would write if you send it a SAVECONF command,
8623 so the controller can write the file to disk itself.
8625 o Minor features (controller protocol):
8626 - Add a new ControlSocketsGroupWritable configuration option: when
8627 it is turned on, ControlSockets are group-writeable by the default
8628 group of the current user. Patch by Jérémy Bobbio; implements
8630 - Tor now refuses to create a ControlSocket in a directory that is
8631 world-readable (or group-readable if ControlSocketsGroupWritable
8632 is 0). This is necessary because some operating systems do not
8633 enforce permissions on an AF_UNIX sockets. Permissions on the
8634 directory holding the socket, however, seems to work everywhere.
8635 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
8636 not. This would lead to a cookie that is still not group readable.
8637 Closes bug 1843. Suggested by katmagic.
8638 - Future-proof the controller protocol a bit by ignoring keyword
8639 arguments we do not recognize.
8641 o Minor features (more useful logging):
8642 - Revise most log messages that refer to nodes by nickname to
8643 instead use the "$key=nickname at address" format. This should be
8644 more useful, especially since nicknames are less and less likely
8645 to be unique. Resolves ticket 3045.
8646 - When an HTTPS proxy reports "403 Forbidden", we now explain
8647 what it means rather than calling it an unexpected status code.
8648 Closes bug 2503. Patch from Michael Yakubovich.
8649 - Rate-limit a warning about failures to download v2 networkstatus
8650 documents. Resolves part of bug 1352.
8651 - Rate-limit the "your application is giving Tor only an IP address"
8652 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
8653 - Rate-limit "Failed to hand off onionskin" warnings.
8654 - When logging a rate-limited warning, we now mention how many messages
8655 got suppressed since the last warning.
8656 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
8657 2 no signature, 4 required" messages about consensus signatures
8658 easier to read, and make sure they get logged at the same severity
8659 as the messages explaining which keys are which. Fixes bug 1290.
8660 - Don't warn when we have a consensus that we can't verify because
8661 of missing certificates, unless those certificates are ones
8662 that we have been trying and failing to download. Fixes bug 1145.
8664 o Minor features (log domains):
8665 - Add documentation for configuring logging at different severities in
8666 different log domains. We've had this feature since 0.2.1.1-alpha,
8667 but for some reason it never made it into the manpage. Fixes
8669 - Make it simpler to specify "All log domains except for A and B".
8670 Previously you needed to say "[*,~A,~B]". Now you can just say
8672 - Add a "LogMessageDomains 1" option to include the domains of log
8673 messages along with the messages. Without this, there's no way
8674 to use log domains without reading the source or doing a lot
8676 - Add a new "Handshake" log domain for activities that happen
8677 during the TLS handshake.
8679 o Minor features (build process):
8680 - Make compilation with clang possible when using
8681 "--enable-gcc-warnings" by removing two warning options that clang
8682 hasn't implemented yet and by fixing a few warnings. Resolves
8684 - Detect platforms that brokenly use a signed size_t, and refuse to
8685 build there. Found and analyzed by doorss and rransom.
8686 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
8688 - Add support for statically linking zlib by specifying
8689 "--enable-static-zlib", to go with our support for statically
8690 linking openssl and libevent. Resolves bug 1358.
8691 - Instead of adding the svn revision to the Tor version string, report
8692 the git commit (when we're building from a git checkout).
8693 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
8695 - New --digests command-line switch to output the digests of the
8696 source files Tor was built with.
8697 - Generate our manpage and HTML documentation using Asciidoc. This
8698 change should make it easier to maintain the documentation, and
8699 produce nicer HTML. The build process fails if asciidoc cannot
8700 be found and building with asciidoc isn't disabled (via the
8701 "--disable-asciidoc" argument to ./configure. Skipping the manpage
8702 speeds up the build considerably.
8704 o Minor features (options / torrc):
8705 - Warn when the same option is provided more than once in a torrc
8706 file, on the command line, or in a single SETCONF statement, and
8707 the option is one that only accepts a single line. Closes bug 1384.
8708 - Warn when the user configures two HiddenServiceDir lines that point
8709 to the same directory. Bugfix on 0.0.6 (the version introducing
8710 HiddenServiceDir); fixes bug 3289.
8711 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
8712 do individual connection-level rate limiting of clients. The torrc
8713 config options with the same names trump the consensus params, if
8714 both are present. Replaces the old "bwconnrate" and "bwconnburst"
8715 consensus params which were broken from 0.2.2.7-alpha through
8716 0.2.2.14-alpha. Closes bug 1947.
8717 - New config option "WarnUnsafeSocks 0" disables the warning that
8718 occurs whenever Tor receives a socks handshake using a version of
8719 the socks protocol that can only provide an IP address (rather
8720 than a hostname). Setups that do DNS locally over Tor are fine,
8721 and we shouldn't spam the logs in that case.
8722 - New config option "CircuitStreamTimeout" to override our internal
8723 timeout schedule for how many seconds until we detach a stream from
8724 a circuit and try a new circuit. If your network is particularly
8725 slow, you might want to set this to a number like 60.
8726 - New options for SafeLogging to allow scrubbing only log messages
8727 generated while acting as a relay. Specify "SafeLogging relay" if
8728 you want to ensure that only messages known to originate from
8729 client use of the Tor process will be logged unsafely.
8730 - Time and memory units in the configuration file can now be set to
8731 fractional units. For example, "2.5 GB" is now a valid value for
8733 - Support line continuations in the torrc config file. If a line
8734 ends with a single backslash character, the newline is ignored, and
8735 the configuration value is treated as continuing on the next line.
8738 o Minor features (unit tests):
8739 - Revise our unit tests to use the "tinytest" framework, so we
8740 can run tests in their own processes, have smarter setup/teardown
8741 code, and so on. The unit test code has moved to its own
8742 subdirectory, and has been split into multiple modules.
8743 - Add a unit test for cross-platform directory-listing code.
8744 - Add some forgotten return value checks during unit tests. Found
8746 - Use GetTempDir to find the proper temporary directory location on
8747 Windows when generating temporary files for the unit tests. Patch
8750 o Minor features (misc):
8751 - The "torify" script now uses torsocks where available.
8752 - Make Libevent log messages get delivered to controllers later,
8753 and not from inside the Libevent log handler. This prevents unsafe
8754 reentrant Libevent calls while still letting the log messages
8756 - Certain Tor clients (such as those behind check.torproject.org) may
8757 want to fetch the consensus in an extra early manner. To enable this
8758 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
8759 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
8760 as only certain clients who must have this information sooner should
8762 - Expand homedirs passed to tor-checkkey. This should silence a
8763 coverity complaint about passing a user-supplied string into
8764 open() without checking it.
8765 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
8766 used on bridges, and it makes bridge scanning somewhat easier.
8767 - Create the /var/run/tor directory on startup on OpenSUSE if it is
8768 not already created. Patch from Andreas Stieger. Fixes bug 2573.
8770 o Minor bugfixes (relays):
8771 - When a relay decides that its DNS is too broken for it to serve
8772 as an exit server, it advertised itself as a non-exit, but
8773 continued to act as an exit. This could create accidental
8774 partitioning opportunities for users. Instead, if a relay is
8775 going to advertise reject *:* as its exit policy, it should
8776 really act with exit policy "reject *:*". Fixes bug 2366.
8777 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
8778 - Publish a router descriptor even if generating an extra-info
8779 descriptor fails. Previously we would not publish a router
8780 descriptor without an extra-info descriptor; this can cause fast
8781 exit relays collecting exit-port statistics to drop from the
8782 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
8783 - When we're trying to guess whether we know our IP address as
8784 a relay, we would log various ways that we failed to guess
8785 our address, but never log that we ended up guessing it
8786 successfully. Now add a log line to help confused and anxious
8787 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
8788 - For bandwidth accounting, calculate our expected bandwidth rate
8789 based on the time during which we were active and not in
8790 soft-hibernation during the last interval. Previously, we were
8791 also considering the time spent in soft-hibernation. If this
8792 was a long time, we would wind up underestimating our bandwidth
8793 by a lot, and skewing our wakeup time towards the start of the
8794 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
8795 - Demote a confusing TLS warning that relay operators might get when
8796 someone tries to talk to their ORPort. It is not the operator's
8797 fault, nor can they do anything about it. Fixes bug 1364; bugfix
8799 - Change "Application request when we're believed to be offline."
8800 notice to "Application request when we haven't used client
8801 functionality lately.", to clarify that it's not an error. Bugfix
8802 on 0.0.9.3; fixes bug 1222.
8804 o Minor bugfixes (bridges):
8805 - When a client starts or stops using bridges, never use a circuit
8806 that was built before the configuration change. This behavior could
8807 put at risk a user who uses bridges to ensure that her traffic
8808 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
8810 - Do not reset the bridge descriptor download status every time we
8811 re-parse our configuration or get a configuration change. Fixes
8812 bug 3019; bugfix on 0.2.0.3-alpha.
8813 - Users couldn't configure a regular relay to be their bridge. It
8814 didn't work because when Tor fetched the bridge descriptor, it found
8815 that it already had it, and didn't realize that the purpose of the
8816 descriptor had changed. Now we replace routers with a purpose other
8817 than bridge with bridge descriptors when fetching them. Bugfix on
8818 0.1.1.9-alpha. Fixes bug 1776.
8819 - In the special case where you configure a public exit relay as your
8820 bridge, Tor would be willing to use that exit relay as the last
8821 hop in your circuit as well. Now we fail that circuit instead.
8822 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
8824 o Minor bugfixes (clients):
8825 - We now ask the other side of a stream (the client or the exit)
8826 for more data on that stream when the amount of queued data on
8827 that stream dips low enough. Previously, we wouldn't ask the
8828 other side for more data until either it sent us more data (which
8829 it wasn't supposed to do if it had exhausted its window!) or we
8830 had completely flushed all our queued data. This flow control fix
8831 should improve throughput. Fixes bug 2756; bugfix on the earliest
8832 released versions of Tor (svn commit r152).
8833 - When a client finds that an origin circuit has run out of 16-bit
8834 stream IDs, we now mark it as unusable for new streams. Previously,
8835 we would try to close the entire circuit. Bugfix on 0.0.6.
8836 - Make it explicit that we don't cannibalize one-hop circuits. This
8837 happens in the wild, but doesn't turn out to be a problem because
8838 we fortunately don't use those circuits. Many thanks to outofwords
8839 for the initial analysis and to swissknife who confirmed that
8840 two-hop circuits are actually created.
8841 - Resolve an edge case in path weighting that could make us misweight
8842 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
8843 - Make the DNSPort option work with libevent 2.x. Don't alter the
8844 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
8846 o Minor bugfixes (directory authorities):
8847 - Make directory authorities more accurate at recording when
8848 relays that have failed several reachability tests became
8849 unreachable, so we can provide more accuracy at assigning Stable,
8850 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
8851 - Directory authorities are now more robust to hops back in time
8852 when calculating router stability. Previously, if a run of uptime
8853 or downtime appeared to be negative, the calculation could give
8854 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
8856 - Directory authorities will now attempt to download consensuses
8857 if their own efforts to make a live consensus have failed. This
8858 change means authorities that restart will fetch a valid
8859 consensus, and it means authorities that didn't agree with the
8860 current consensus will still fetch and serve it if it has enough
8861 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
8862 - Never vote for a server as "Running" if we have a descriptor for
8863 it claiming to be hibernating, and that descriptor was published
8864 more recently than our last contact with the server. Bugfix on
8865 0.2.0.3-alpha; fixes bug 911.
8866 - Directory authorities no longer change their opinion of, or vote on,
8867 whether a router is Running, unless they have themselves been
8868 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
8871 o Minor bugfixes (hidden services):
8872 - Log malformed requests for rendezvous descriptors as protocol
8873 warnings, not warnings. Also, use a more informative log message
8874 in case someone sees it at log level warning without prior
8875 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
8876 - Accept hidden service descriptors if we think we might be a hidden
8877 service directory, regardless of what our consensus says. This
8878 helps robustness, since clients and hidden services can sometimes
8879 have a more up-to-date view of the network consensus than we do,
8880 and if they think that the directory authorities list us a HSDir,
8881 we might actually be one. Related to bug 2732; bugfix on
8883 - Correct the warning displayed when a rendezvous descriptor exceeds
8884 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8886 - Clients and hidden services now use HSDir-flagged relays for hidden
8887 service descriptor downloads and uploads even if the relays have no
8888 DirPort set and the client has disabled TunnelDirConns. This will
8889 eventually allow us to give the HSDir flag to relays with no
8890 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
8891 - Only limit the lengths of single HS descriptors, even when multiple
8892 HS descriptors are published to an HSDir relay in a single POST
8893 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
8895 o Minor bugfixes (controllers):
8896 - Allow GETINFO fingerprint to return a fingerprint even when
8897 we have not yet built a router descriptor. Fixes bug 3577;
8898 bugfix on 0.2.0.1-alpha.
8899 - Send a SUCCEEDED stream event to the controller when a reverse
8900 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
8901 discovered by katmagic.
8902 - Remove a trailing asterisk from "exit-policy/default" in the
8903 output of the control port command "GETINFO info/names". Bugfix
8905 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
8906 2917. Bugfix on 0.1.1.1-alpha.
8907 - When we restart our relay, we might get a successful connection
8908 from the outside before we've started our reachability tests,
8909 triggering a warning: "ORPort found reachable, but I have no
8910 routerinfo yet. Failing to inform controller of success." This
8911 bug was harmless unless Tor is running under a controller
8912 like Vidalia, in which case the controller would never get a
8913 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8915 - When a controller changes TrackHostExits, remove mappings for
8916 hosts that should no longer have their exits tracked. Bugfix on
8918 - When a controller changes VirtualAddrNetwork, remove any mappings
8919 for hosts that were automapped to the old network. Bugfix on
8921 - When a controller changes one of the AutomapHosts* options, remove
8922 any mappings for hosts that should no longer be automapped. Bugfix
8924 - Fix an off-by-one error in calculating some controller command
8925 argument lengths. Fortunately, this mistake is harmless since
8926 the controller code does redundant NUL termination too. Found by
8927 boboper. Bugfix on 0.1.1.1-alpha.
8928 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
8929 would return "551 Internal error" rather than "552 Unrecognized key
8930 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
8931 - Don't spam the controller with events when we have no file
8932 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
8933 for log messages was already solved from bug 748.)
8934 - Emit a GUARD DROPPED controller event for a case we missed.
8935 - Ensure DNS requests launched by "RESOLVE" commands from the
8936 controller respect the __LeaveStreamsUnattached setconf options. The
8937 same goes for requests launched via DNSPort or transparent
8938 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
8940 o Minor bugfixes (config options):
8941 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
8942 Change the limit to 512 characters by removing base64 newlines.
8943 Fixes bug 2752. Fix by Michael Yakubovich.
8944 - Complain if PublishServerDescriptor is given multiple arguments that
8945 include 0 or 1. This configuration will be rejected in the future.
8946 Bugfix on 0.2.0.1-alpha; closes bug 1107.
8947 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
8948 Bugfix on 0.2.0.13-alpha; closes bug 928.
8950 o Minor bugfixes (log subsystem fixes):
8951 - When unable to format an address as a string, report its value
8952 as "???" rather than reusing the last formatted address. Bugfix
8954 - Be more consistent in our treatment of file system paths. "~" should
8955 get expanded to the user's home directory in the Log config option.
8956 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
8957 feature for the -f and --DataDirectory options.
8959 o Minor bugfixes (memory management):
8960 - Don't stack-allocate the list of supplementary GIDs when we're
8961 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8962 could take up to 256K, which is way too much stack. Found by
8963 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8964 - Save a couple bytes in memory allocation every time we escape
8965 certain characters in a string. Patch from Florian Zumbiehl.
8967 o Minor bugfixes (protocol correctness):
8968 - When checking for 1024-bit keys, check for 1024 bits, not 128
8969 bytes. This allows Tor to correctly discard keys of length 1017
8970 through 1023. Bugfix on 0.0.9pre5.
8971 - Require that introduction point keys and onion handshake keys
8972 have a public exponent of 65537. Starts to fix bug 3207; bugfix
8974 - Handle SOCKS messages longer than 128 bytes long correctly, rather
8975 than waiting forever for them to finish. Fixes bug 2330; bugfix
8976 on 0.2.0.16-alpha. Found by doorss.
8977 - Never relay a cell for a circuit we have already destroyed.
8978 Between marking a circuit as closeable and finally closing it,
8979 it may have been possible for a few queued cells to get relayed,
8980 even though they would have been immediately dropped by the next
8981 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
8982 - Never queue a cell for a circuit that's already been marked
8984 - Fix a spec conformance issue: the network-status-version token
8985 must be the first token in a v3 consensus or vote. Discovered by
8986 "parakeep". Bugfix on 0.2.0.3-alpha.
8987 - A networkstatus vote must contain exactly one signature. Spec
8988 conformance issue. Bugfix on 0.2.0.3-alpha.
8989 - When asked about a DNS record type we don't support via a
8990 client DNSPort, reply with NOTIMPL rather than an empty
8991 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
8992 - Make more fields in the controller protocol case-insensitive, since
8993 control-spec.txt said they were.
8995 o Minor bugfixes (log messages):
8996 - Fix a log message that said "bits" while displaying a value in
8997 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
8999 - Downgrade "no current certificates known for authority" message from
9000 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
9001 - Correctly describe errors that occur when generating a TLS object.
9002 Previously we would attribute them to a failure while generating a
9003 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
9005 - Fix an instance where a Tor directory mirror might accidentally
9006 log the IP address of a misbehaving Tor client. Bugfix on
9008 - Stop logging at severity 'warn' when some other Tor client tries
9009 to establish a circuit with us using weak DH keys. It's a protocol
9010 violation, but that doesn't mean ordinary users need to hear about
9011 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
9012 - If your relay can't keep up with the number of incoming create
9013 cells, it would log one warning per failure into your logs. Limit
9014 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
9016 o Minor bugfixes (build fixes):
9017 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9018 - When warning about missing zlib development packages during compile,
9019 give the correct package names. Bugfix on 0.2.0.1-alpha.
9020 - Fix warnings that newer versions of autoconf produce during
9021 ./autogen.sh. These warnings appear to be harmless in our case,
9022 but they were extremely verbose. Fixes bug 2020.
9023 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
9026 o Minor bugfixes (portability):
9027 - Write several files in text mode, on OSes that distinguish text
9028 mode from binary mode (namely, Windows). These files are:
9029 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9030 that collect those statistics; 'client_keys' and 'hostname' for
9031 hidden services that use authentication; and (in the tor-gencert
9032 utility) newly generated identity and signing keys. Previously,
9033 we wouldn't specify text mode or binary mode, leading to an
9034 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9035 the DirRecordUsageByCountry option which would have triggered
9036 the assertion failure was added), although this assertion failure
9037 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9038 - Selectively disable deprecation warnings on OS X because Lion
9039 started deprecating the shipped copy of openssl. Fixes bug 3643.
9040 - Use a wide type to hold sockets when built for 64-bit Windows.
9042 - Fix an issue that prevented static linking of libevent on
9043 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
9044 where we introduced the "--with-static-libevent" configure option.
9045 - Fix a bug with our locking implementation on Windows that couldn't
9046 correctly detect when a file was already locked. Fixes bug 2504,
9047 bugfix on 0.2.1.6-alpha.
9048 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9050 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
9051 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
9054 o Minor bugfixes (code correctness):
9055 - Always NUL-terminate the sun_path field of a sockaddr_un before
9056 passing it to the kernel. (Not a security issue: kernels are
9057 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9058 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9059 - Make connection_printf_to_buf()'s behavior sane. Its callers
9060 expect it to emit a CRLF iff the format string ends with CRLF;
9061 it actually emitted a CRLF iff (a) the format string ended with
9062 CRLF or (b) the resulting string was over 1023 characters long or
9063 (c) the format string did not end with CRLF *and* the resulting
9064 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
9065 fixes part of bug 3407.
9066 - Make send_control_event_impl()'s behavior sane. Its callers
9067 expect it to always emit a CRLF at the end of the string; it
9068 might have emitted extra control characters as well. Bugfix on
9069 0.1.1.9-alpha; fixes another part of bug 3407.
9070 - Make crypto_rand_int() check the value of its input correctly.
9071 Previously, it accepted values up to UINT_MAX, but could return a
9072 negative number if given a value above INT_MAX+1. Found by George
9073 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
9074 - Fix a potential null-pointer dereference while computing a
9075 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
9077 - If we fail to compute the identity digest of a v3 legacy keypair,
9078 warn, and don't use a buffer-full of junk instead. Bugfix on
9079 0.2.1.1-alpha; fixes bug 3106.
9080 - Resolve an untriggerable issue in smartlist_string_num_isin(),
9081 where if the function had ever in the future been used to check
9082 for the presence of a too-large number, it would have given an
9083 incorrect result. (Fortunately, we only used it for 16-bit
9084 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
9085 - Be more careful about reporting the correct error from a failed
9086 connect() system call. Under some circumstances, it was possible to
9087 look at an incorrect value for errno when sending the end reason.
9088 Bugfix on 0.1.0.1-rc.
9089 - Correctly handle an "impossible" overflow cases in connection byte
9090 counting, where we write or read more than 4GB on an edge connection
9091 in a single second. Bugfix on 0.1.2.8-beta.
9092 - Avoid a double mark-for-free warning when failing to attach a
9093 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
9095 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
9096 found by "cypherpunks". This bug was introduced before the first
9097 Tor release, in svn commit r110.
9098 - Fix a bug in bandwidth history state parsing that could have been
9099 triggered if a future version of Tor ever changed the timing
9100 granularity at which bandwidth history is measured. Bugfix on
9102 - Add assertions to check for overflow in arguments to
9103 base32_encode() and base32_decode(); fix a signed-unsigned
9104 comparison there too. These bugs are not actually reachable in Tor,
9105 but it's good to prevent future errors too. Found by doorss.
9106 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
9108 - Set target port in get_interface_address6() correctly. Bugfix
9109 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
9110 - Fix an impossible-to-actually-trigger buffer overflow in relay
9111 descriptor generation. Bugfix on 0.1.0.15.
9112 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
9114 o Minor bugfixes (code improvements):
9115 - After we free an internal connection structure, overwrite it
9116 with a different memory value than we use for overwriting a freed
9117 internal circuit structure. Should help with debugging. Suggested
9119 - If OpenSSL fails to make a duplicate of a private or public key, log
9120 an error message and try to exit cleanly. May help with debugging
9121 if bug 1209 ever remanifests.
9122 - Some options used different conventions for uppercasing of acronyms
9123 when comparing manpage and source. Fix those in favor of the
9124 manpage, as it makes sense to capitalize acronyms.
9125 - Take a first step towards making or.h smaller by splitting out
9126 function definitions for all source files in src/or/. Leave
9127 structures and defines in or.h for now.
9128 - Remove a few dead assignments during router parsing. Found by
9130 - Don't use 1-bit wide signed bit fields. Found by coverity.
9131 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9132 None of the cases where we did this before were wrong, but by making
9133 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9134 - The memarea code now uses a sentinel value at the end of each area
9135 to make sure nothing writes beyond the end of an area. This might
9136 help debug some conceivable causes of bug 930.
9137 - Always treat failure to allocate an RSA key as an unrecoverable
9139 - Add some more defensive programming for architectures that can't
9140 handle unaligned integer accesses. We don't know of any actual bugs
9141 right now, but that's the best time to fix them. Fixes bug 1943.
9143 o Minor bugfixes (misc):
9144 - Fix a rare bug in rend_fn unit tests: we would fail a test when
9145 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
9146 on 0.2.0.10-alpha; fixes bug 1808.
9147 - Where available, use Libevent 2.0's periodic timers so that our
9148 once-per-second cleanup code gets called even more closely to
9149 once per second than it would otherwise. Fixes bug 943.
9150 - Ignore OutboundBindAddress when connecting to localhost.
9151 Connections to localhost need to come _from_ localhost, or else
9152 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
9154 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
9156 - If any of the v3 certs we download are unparseable, we should
9157 actually notice the failure so we don't retry indefinitely. Bugfix
9158 on 0.2.0.x; reported by "rotator".
9159 - When Tor fails to parse a descriptor of any kind, dump it to disk.
9160 Might help diagnosing bug 1051.
9161 - Make our 'torify' script more portable; if we have only one of
9162 'torsocks' or 'tsocks' installed, don't complain to the user;
9163 and explain our warning about tsocks better.
9164 - Fix some urls in the exit notice file and make it XHTML1.1 strict
9165 compliant. Based on a patch from Christian Kujau.
9167 o Documentation changes:
9168 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
9169 - Resolve all doxygen warnings except those for missing documentation.
9171 - Add doxygen documentation for more functions, fields, and types.
9172 - Convert the HACKING file to asciidoc, and add a few new sections
9173 to it, explaining how we use Git, how we make changelogs, and
9174 what should go in a patch.
9175 - Document the default socks host and port (127.0.0.1:9050) for
9177 - Removed some unnecessary files from the source distribution. The
9178 AUTHORS file has now been merged into the people page on the
9179 website. The roadmaps and design doc can now be found in the
9180 projects directory in svn.
9182 o Deprecated and removed features (config):
9183 - Remove the torrc.complete file. It hasn't been kept up to date
9184 and users will have better luck checking out the manpage.
9185 - Remove the HSAuthorityRecordStats option that version 0 hidden
9186 service authorities could use to track statistics of overall v0
9187 hidden service usage.
9188 - Remove the obsolete "NoPublish" option; it has been flagged
9189 as obsolete and has produced a warning since 0.1.1.18-rc.
9190 - Caches no longer download and serve v2 networkstatus documents
9191 unless FetchV2Networkstatus flag is set: these documents haven't
9192 haven't been used by clients or relays since 0.2.0.x. Resolves
9195 o Deprecated and removed features (controller):
9196 - The controller no longer accepts the old obsolete "addr-mappings/"
9197 or "unregistered-servers-" GETINFO values.
9198 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
9199 always on; using them is necessary for correct forward-compatible
9202 o Deprecated and removed features (misc):
9203 - Hidden services no longer publish version 0 descriptors, and clients
9204 do not request or use version 0 descriptors. However, the old hidden
9205 service authorities still accept and serve version 0 descriptors
9206 when contacted by older hidden services/clients.
9207 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9208 anything since 0.2.1.16-rc.
9209 - Remove everything related to building the expert bundle for OS X.
9210 It has confused many users, doesn't work right on OS X 10.6,
9211 and is hard to get rid of once installed. Resolves bug 1274.
9212 - Remove support for .noconnect style addresses. Nobody was using
9213 them, and they provided another avenue for detecting Tor users
9214 via application-level web tricks.
9215 - When we fixed bug 1038 we had to put in a restriction not to send
9216 RELAY_EARLY cells on rend circuits. This was necessary as long
9217 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
9218 active. Now remove this obsolete check. Resolves bug 2081.
9219 - Remove workaround code to handle directory responses from servers
9220 that had bug 539 (they would send HTTP status 503 responses _and_
9221 send a body too). Since only server versions before
9222 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
9223 keep the workaround in place.
9224 - Remove the old 'fuzzy time' logic. It was supposed to be used for
9225 handling calculations where we have a known amount of clock skew and
9226 an allowed amount of unknown skew. But we only used it in three
9227 places, and we never adjusted the known/unknown skew values. This is
9228 still something we might want to do someday, but if we do, we'll
9229 want to do it differently.
9230 - Remove the "--enable-iphone" option to ./configure. According to
9231 reports from Marco Bonetti, Tor builds fine without any special
9232 tweaking on recent iPhone SDK versions.
9235 Changes in version 0.2.1.30 - 2011-02-23
9236 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
9237 change is a slight tweak to Tor's TLS handshake that makes relays
9238 and bridges that run this new version reachable from Iran again.
9239 We don't expect this tweak will win the arms race long-term, but it
9240 buys us time until we roll out a better solution.
9243 - Stop sending a CLOCK_SKEW controller status event whenever
9244 we fetch directory information from a relay that has a wrong clock.
9245 Instead, only inform the controller when it's a trusted authority
9246 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9247 the rest of bug 1074.
9248 - Fix a bounds-checking error that could allow an attacker to
9249 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9251 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9252 Tor would ignore their RelayBandwidthBurst setting,
9253 potentially using more bandwidth than expected. Bugfix on
9254 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9255 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9256 hidserv" in her torrc. The 'hidserv' argument never controlled
9257 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9260 - Adjust our TLS Diffie-Hellman parameters to match those used by
9262 - Update to the February 1 2011 Maxmind GeoLite Country database.
9265 - Check for and reject overly long directory certificates and
9266 directory tokens before they have a chance to hit any assertions.
9267 Bugfix on 0.2.1.28. Found by "doorss".
9268 - Bring the logic that gathers routerinfos and assesses the
9269 acceptability of circuits into line. This prevents a Tor OP from
9270 getting locked in a cycle of choosing its local OR as an exit for a
9271 path (due to a .exit request) and then rejecting the circuit because
9272 its OR is not listed yet. It also prevents Tor clients from using an
9273 OR running in the same instance as an exit (due to a .exit request)
9274 if the OR does not meet the same requirements expected of an OR
9275 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9277 o Packaging changes:
9278 - Stop shipping the Tor specs files and development proposal documents
9279 in the tarball. They are now in a separate git repository at
9280 git://git.torproject.org/torspec.git
9281 - Do not include Git version tags as though they are SVN tags when
9282 generating a tarball from inside a repository that has switched
9283 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9286 Changes in version 0.2.1.29 - 2011-01-15
9287 Tor 0.2.1.29 continues our recent code security audit work. The main
9288 fix resolves a remote heap overflow vulnerability that can allow remote
9289 code execution. Other fixes address a variety of assert and crash bugs,
9290 most of which we think are hard to exploit remotely.
9292 o Major bugfixes (security):
9293 - Fix a heap overflow bug where an adversary could cause heap
9294 corruption. This bug probably allows remote code execution
9295 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9297 - Prevent a denial-of-service attack by disallowing any
9298 zlib-compressed data whose compression factor is implausibly
9299 high. Fixes part of bug 2324; reported by "doorss".
9300 - Zero out a few more keys in memory before freeing them. Fixes
9301 bug 2384 and part of bug 2385. These key instances found by
9302 "cypherpunks", based on Andrew Case's report about being able
9303 to find sensitive data in Tor's memory space if you have enough
9304 permissions. Bugfix on 0.0.2pre9.
9306 o Major bugfixes (crashes):
9307 - Prevent calls to Libevent from inside Libevent log handlers.
9308 This had potential to cause a nasty set of crashes, especially
9309 if running Libevent with debug logging enabled, and running
9310 Tor with a controller watching for low-severity log messages.
9311 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9312 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9313 underflow errors there too. Fixes the other part of bug 2324.
9314 - Fix a bug where we would assert if we ever had a
9315 cached-descriptors.new file (or another file read directly into
9316 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9317 on 0.2.1.25. Found by doorss.
9318 - Fix some potential asserts and parsing issues with grossly
9319 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9322 o Minor bugfixes (other):
9323 - Fix a bug with handling misformed replies to reverse DNS lookup
9324 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9325 bug reported by doorss.
9326 - Fix compilation on mingw when a pthreads compatibility library
9327 has been installed. (We don't want to use it, so we shouldn't
9328 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9329 - Fix a bug where we would declare that we had run out of virtual
9330 addresses when the address space was only half-exhausted. Bugfix
9332 - Correctly handle the case where AutomapHostsOnResolve is set but
9333 no virtual addresses are available. Fixes bug 2328; bugfix on
9334 0.1.2.1-alpha. Bug found by doorss.
9335 - Correctly handle wrapping around when we run out of virtual
9336 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
9339 - Update to the January 1 2011 Maxmind GeoLite Country database.
9340 - Introduce output size checks on all of our decryption functions.
9343 - Tor does not build packages correctly with Automake 1.6 and earlier;
9344 added a check to Makefile.am to make sure that we're building with
9345 Automake 1.7 or later.
9346 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9347 because we built it with a too-old version of automake. Thus that
9348 release broke ./configure --enable-openbsd-malloc, which is popular
9349 among really fast exit relays on Linux.
9352 Changes in version 0.2.1.28 - 2010-12-17
9353 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
9354 exploitable bugs. We also took this opportunity to change the IP address
9355 for one of our directory authorities, and to update the geoip database
9359 - Fix a remotely exploitable bug that could be used to crash instances
9360 of Tor remotely by overflowing on the heap. Remote-code execution
9361 hasn't been confirmed, but can't be ruled out. Everyone should
9362 upgrade. Bugfix on the 0.1.1 series and later.
9364 o Directory authority changes:
9365 - Change IP address and ports for gabelmoo (v3 directory authority).
9368 - Update to the December 1 2010 Maxmind GeoLite Country database.
9371 Changes in version 0.2.1.27 - 2010-11-23
9372 Yet another OpenSSL security patch broke its compatibility with Tor:
9373 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
9374 also took this opportunity to fix several crash bugs, integrate a new
9375 directory authority, and update the bundled GeoIP database.
9378 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9379 No longer set the tlsext_host_name extension on server SSL objects;
9380 but continue to set it on client SSL objects. Our goal in setting
9381 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9382 bugfix on 0.2.1.1-alpha.
9383 - Do not log messages to the controller while shrinking buffer
9384 freelists. Doing so would sometimes make the controller connection
9385 try to allocate a buffer chunk, which would mess up the internals
9386 of the freelist and cause an assertion failure. Fixes bug 1125;
9387 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9388 - Learn our external IP address when we're a relay or bridge, even if
9389 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9390 where we introduced bridge relays that don't need to publish to
9391 be useful. Fixes bug 2050.
9392 - Do even more to reject (and not just ignore) annotations on
9393 router descriptors received anywhere but from the cache. Previously
9394 we would ignore such annotations at first, but cache them to disk
9395 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9396 - When you're using bridges and your network goes away and your
9397 bridges get marked as down, recover when you attempt a new socks
9398 connection (if the network is back), rather than waiting up to an
9399 hour to try fetching new descriptors for your bridges. Bugfix on
9400 0.2.0.3-alpha; fixes bug 1981.
9403 - Move to the November 2010 Maxmind GeoLite country db (rather
9404 than the June 2009 ip-to-country GeoIP db) for our statistics that
9405 count how many users relays are seeing from each country. Now we'll
9406 have more accurate data, especially for many African countries.
9408 o New directory authorities:
9409 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9413 - Fix an assertion failure that could occur in directory caches or
9414 bridge users when using a very short voting interval on a testing
9415 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
9417 - Enforce multiplicity rules when parsing annotations. Bugfix on
9418 0.2.0.8-alpha. Found by piebeer.
9419 - Allow handshaking OR connections to take a full KeepalivePeriod
9420 seconds to handshake. Previously, we would close them after
9421 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9422 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9424 - When building with --enable-gcc-warnings on OpenBSD, disable
9425 warnings in system headers. This makes --enable-gcc-warnings
9426 pass on OpenBSD 4.8.
9429 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9430 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9431 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9432 Servers can start sending this code when enough clients recognize
9433 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
9434 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9435 Patch from mingw-san.
9438 - Remove the old debian/ directory from the main Tor distribution.
9439 The official Tor-for-debian git repository lives at the URL
9440 https://git.torproject.org/debian/tor.git
9441 - Stop shipping the old doc/website/ directory in the tarball. We
9442 changed the website format in late 2010, and what we shipped in
9443 0.2.1.26 really wasn't that useful anyway.
9446 Changes in version 0.2.1.26 - 2010-05-02
9447 Tor 0.2.1.26 addresses the recent connection and memory overload
9448 problems we've been seeing on relays, especially relays with their
9449 DirPort open. If your relay has been crashing, or you turned it off
9450 because it used too many resources, give this release a try.
9452 This release also fixes yet another instance of broken OpenSSL libraries
9453 that was causing some relays to drop out of the consensus.
9456 - Teach relays to defend themselves from connection overload. Relays
9457 now close idle circuits early if it looks like they were intended
9458 for directory fetches. Relays are also more aggressive about closing
9459 TLS connections that have no circuits on them. Such circuits are
9460 unlikely to be re-used, and tens of thousands of them were piling
9461 up at the fast relays, causing the relays to run out of sockets
9462 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9463 their directory fetches over TLS).
9464 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9465 that claim to be earlier than 0.9.8m, but which have in reality
9466 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9467 behavior. Possible fix for some cases of bug 1346.
9468 - Directory mirrors were fetching relay descriptors only from v2
9469 directory authorities, rather than v3 authorities like they should.
9470 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9471 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9474 - Finally get rid of the deprecated and now harmful notion of "clique
9475 mode", where directory authorities maintain TLS connections to
9479 - In the util/threads test, no longer free the test_mutex before all
9480 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9481 - The master thread could starve the worker threads quite badly on
9482 certain systems, causing them to run only partially in the allowed
9483 window. This resulted in test failures. Now the master thread sleeps
9484 occasionally for a few microseconds while the two worker-threads
9485 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9488 Changes in version 0.2.1.25 - 2010-03-16
9489 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
9490 prevent relays from guessing their IP address correctly. It also fixes
9491 several minor potential security bugs.
9494 - Fix a regression from our patch for bug 1244 that caused relays
9495 to guess their IP address incorrectly if they didn't set Address
9496 in their torrc and/or their address fails to resolve. Bugfix on
9497 0.2.1.23; fixes bug 1269.
9498 - When freeing a session key, zero it out completely. We only zeroed
9499 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9500 patched by ekir. Fixes bug 1254.
9503 - Fix a dereference-then-NULL-check sequence when publishing
9504 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9506 - Fix another dereference-then-NULL-check sequence. Bugfix on
9507 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9508 - Make sure we treat potentially not NUL-terminated strings correctly.
9509 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9512 Changes in version 0.2.1.24 - 2010-02-21
9513 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
9517 - Work correctly out-of-the-box with even more vendor-patched versions
9518 of OpenSSL. In particular, make it so Debian and OS X don't need
9519 customized patches to run/build.
9522 Changes in version 0.2.1.23 - 2010-02-13
9523 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
9524 again on the latest OS X, and updates the location of a directory
9527 o Major bugfixes (performance):
9528 - We were selecting our guards uniformly at random, and then weighting
9529 which of our guards we'd use uniformly at random. This imbalance
9530 meant that Tor clients were severely limited on throughput (and
9531 probably latency too) by the first hop in their circuit. Now we
9532 select guards weighted by currently advertised bandwidth. We also
9533 automatically discard guards picked using the old algorithm. Fixes
9534 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9537 - Make Tor work again on the latest OS X: when deciding whether to
9538 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9539 version at run-time, not compile time. We need to do this because
9540 Apple doesn't update its dev-tools headers when it updates its
9541 libraries in a security patch.
9542 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9543 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9544 a memory leak when requesting a hidden service descriptor we've
9545 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9549 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9550 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9553 - Avoid a mad rush at the beginning of each month when each client
9554 rotates half of its guards. Instead we spread the rotation out
9555 throughout the month, but we still avoid leaving a precise timestamp
9556 in the state file about when we first picked the guard. Improves
9557 over the behavior introduced in 0.1.2.17.
9560 Changes in version 0.2.1.22 - 2010-01-19
9561 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
9562 authorities -- it would tell you its whole history of bridge descriptors
9563 if you make the right directory request. This stable update also
9564 rotates two of the seven v3 directory authority keys and locations.
9566 o Directory authority changes:
9567 - Rotate keys (both v3 identity and relay identity) for moria1
9571 - Stop bridge directory authorities from answering dbg-stability.txt
9572 directory queries, which would let people fetch a list of all
9573 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9576 Changes in version 0.2.1.21 - 2009-12-21
9577 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
9578 library. If you use Tor on Linux / Unix and you're getting SSL
9579 renegotiation errors, upgrading should help. We also recommend an
9580 upgrade if you're an exit relay.
9583 - Work around a security feature in OpenSSL 0.9.8l that prevents our
9584 handshake from working unless we explicitly tell OpenSSL that we
9585 are using SSL renegotiation safely. We are, of course, but OpenSSL
9586 0.9.8l won't work unless we say we are.
9587 - Avoid crashing if the client is trying to upload many bytes and the
9588 circuit gets torn down at the same time, or if the flip side
9589 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
9592 - Do not refuse to learn about authority certs and v2 networkstatus
9593 documents that are older than the latest consensus. This bug might
9594 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
9595 Spotted and fixed by xmux.
9596 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
9597 trigger platform-specific option misparsing case found by Coverity
9599 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
9600 trigger assert. Fixes bug 1173.
9603 Changes in version 0.2.1.20 - 2009-10-15
9604 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
9605 services at once, prepares for more performance improvements, and
9606 fixes a bunch of smaller bugs.
9608 The Windows and OS X bundles also include a more recent Vidalia,
9609 and switch from Privoxy to Polipo.
9611 The OS X installers are now drag and drop. It's best to un-install
9612 Tor/Vidalia and then install this new bundle, rather than upgrade. If
9613 you want to upgrade, you'll need to update the paths for Tor and Polipo
9614 in the Vidalia Settings window.
9617 - Send circuit or stream sendme cells when our window has decreased
9618 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
9619 by Karsten when testing the "reduce circuit window" performance
9620 patch. Bugfix on the 54th commit on Tor -- from July 2002,
9621 before the release of Tor 0.0.0. This is the new winner of the
9623 - Fix a remotely triggerable memory leak when a consensus document
9624 contains more than one signature from the same voter. Bugfix on
9626 - Avoid segfault in rare cases when finishing an introduction circuit
9627 as a client and finding out that we don't have an introduction key
9628 for it. Fixes bug 1073. Reported by Aaron Swartz.
9631 - Tor now reads the "circwindow" parameter out of the consensus,
9632 and uses that value for its circuit package window rather than the
9633 default of 1000 cells. Begins the implementation of proposal 168.
9635 o New directory authorities:
9636 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
9638 - Move moria1 and tonga to alternate IP addresses.
9641 - Fix a signed/unsigned compile warning in 0.2.1.19.
9642 - Fix possible segmentation fault on directory authorities. Bugfix on
9644 - Fix an extremely rare infinite recursion bug that could occur if
9645 we tried to log a message after shutting down the log subsystem.
9646 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
9647 - Fix an obscure bug where hidden services on 64-bit big-endian
9648 systems might mis-read the timestamp in v3 introduce cells, and
9649 refuse to connect back to the client. Discovered by "rotor".
9650 Bugfix on 0.2.1.6-alpha.
9651 - We were triggering a CLOCK_SKEW controller status event whenever
9652 we connect via the v2 connection protocol to any relay that has
9653 a wrong clock. Instead, we should only inform the controller when
9654 it's a trusted authority that claims our clock is wrong. Bugfix
9655 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
9656 - We were telling the controller about CHECKING_REACHABILITY and
9657 REACHABILITY_FAILED status events whenever we launch a testing
9658 circuit or notice that one has failed. Instead, only tell the
9659 controller when we want to inform the user of overall success or
9660 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
9662 - Don't warn when we're using a circuit that ends with a node
9663 excluded in ExcludeExitNodes, but the circuit is not used to access
9664 the outside world. This should help fix bug 1090. Bugfix on
9666 - Work around a small memory leak in some versions of OpenSSL that
9667 stopped the memory used by the hostname TLS extension from being
9671 - Add a "getinfo status/accepted-server-descriptor" controller
9672 command, which is the recommended way for controllers to learn
9673 whether our server descriptor has been successfully received by at
9674 least on directory authority. Un-recommend good-server-descriptor
9675 getinfo and status events until we have a better design for them.
9678 Changes in version 0.2.1.19 - 2009-07-28
9679 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
9683 - Make accessing hidden services on 0.2.1.x work right again.
9684 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
9685 part of patch provided by "optimist".
9688 - When a relay/bridge is writing out its identity key fingerprint to
9689 the "fingerprint" file and to its logs, write it without spaces. Now
9690 it will look like the fingerprints in our bridges documentation,
9691 and confuse fewer users.
9694 - Relays no longer publish a new server descriptor if they change
9695 their MaxAdvertisedBandwidth config option but it doesn't end up
9696 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
9697 fixes bug 1026. Patch from Sebastian.
9698 - Avoid leaking memory every time we get a create cell but we have
9699 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
9700 fixes bug 1034. Reported by BarkerJr.
9703 Changes in version 0.2.1.18 - 2009-07-24
9704 Tor 0.2.1.18 lays the foundations for performance improvements,
9705 adds status events to help users diagnose bootstrap problems, adds
9706 optional authentication/authorization for hidden services, fixes a
9707 variety of potential anonymity problems, and includes a huge pile of
9708 other features and bug fixes.
9710 o Major features (clients):
9711 - Start sending "bootstrap phase" status events to the controller,
9712 so it can keep the user informed of progress fetching directory
9713 information and establishing circuits. Also inform the controller
9714 if we think we're stuck at a particular bootstrap phase. Implements
9716 - Clients replace entry guards that were chosen more than a few months
9717 ago. This change should significantly improve client performance,
9718 especially once more people upgrade, since relays that have been
9719 a guard for a long time are currently overloaded.
9720 - Network status consensus documents and votes now contain bandwidth
9721 information for each relay. Clients use the bandwidth values
9722 in the consensus, rather than the bandwidth values in each
9723 relay descriptor. This approach opens the door to more accurate
9724 bandwidth estimates once the directory authorities start doing
9725 active measurements. Implements part of proposal 141.
9727 o Major features (relays):
9728 - Disable and refactor some debugging checks that forced a linear scan
9729 over the whole server-side DNS cache. These accounted for over 50%
9730 of CPU time on a relatively busy exit node's gprof profile. Also,
9731 disable some debugging checks that appeared in exit node profile
9732 data. Found by Jacob.
9733 - New DirPortFrontPage option that takes an html file and publishes
9734 it as "/" on the DirPort. Now relay operators can provide a
9735 disclaimer without needing to set up a separate webserver. There's
9736 a sample disclaimer in contrib/tor-exit-notice.html.
9738 o Major features (hidden services):
9739 - Make it possible to build hidden services that only certain clients
9740 are allowed to connect to. This is enforced at several points,
9741 so that unauthorized clients are unable to send INTRODUCE cells
9742 to the service, or even (depending on the type of authentication)
9743 to learn introduction points. This feature raises the bar for
9744 certain kinds of active attacks against hidden services. Design
9745 and code by Karsten Loesing. Implements proposal 121.
9746 - Relays now store and serve v2 hidden service descriptors by default,
9747 i.e., the new default value for HidServDirectoryV2 is 1. This is
9748 the last step in proposal 114, which aims to make hidden service
9749 lookups more reliable.
9751 o Major features (path selection):
9752 - ExitNodes and Exclude*Nodes config options now allow you to restrict
9753 by country code ("{US}") or IP address or address pattern
9754 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
9755 refinement to decide what config options should take priority if
9756 you ask to both use a particular node and exclude it.
9758 o Major features (misc):
9759 - When building a consensus, do not include routers that are down.
9760 This cuts down 30% to 40% on consensus size. Implements proposal
9762 - New TestingTorNetwork config option to allow adjustment of
9763 previously constant values that could slow bootstrapping. Implements
9764 proposal 135. Patch from Karsten.
9765 - Convert many internal address representations to optionally hold
9766 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
9767 elements. Make resolver code handle nameservers located at IPv6
9769 - More work on making our TLS handshake blend in: modify the list
9770 of ciphers advertised by OpenSSL in client mode to even more
9771 closely resemble a common web browser. We cheat a little so that
9772 we can advertise ciphers that the locally installed OpenSSL doesn't
9774 - Use the TLS1 hostname extension to more closely resemble browser
9777 o Security fixes (anonymity/entropy):
9778 - Never use a connection with a mismatched address to extend a
9779 circuit, unless that connection is canonical. A canonical
9780 connection is one whose address is authenticated by the router's
9781 identity key, either in a NETINFO cell or in a router descriptor.
9782 - Implement most of proposal 110: The first K cells to be sent
9783 along a circuit are marked as special "early" cells; only K "early"
9784 cells will be allowed. Once this code is universal, we can block
9785 certain kinds of denial-of-service attack by requiring that EXTEND
9786 commands must be sent using an "early" cell.
9787 - Resume using OpenSSL's RAND_poll() for better (and more portable)
9788 cross-platform entropy collection again. We used to use it, then
9789 stopped using it because of a bug that could crash systems that
9790 called RAND_poll when they had a lot of fds open. It looks like the
9791 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
9792 at startup, and to call RAND_poll() when we reseed later only if
9793 we have a non-buggy OpenSSL version.
9794 - When the client is choosing entry guards, now it selects at most
9795 one guard from a given relay family. Otherwise we could end up with
9796 all of our entry points into the network run by the same operator.
9797 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
9798 - Do not use or believe expired v3 authority certificates. Patch
9799 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
9800 - Drop begin cells to a hidden service if they come from the middle
9801 of a circuit. Patch from lark.
9802 - When we erroneously receive two EXTEND cells for the same circuit
9803 ID on the same connection, drop the second. Patch from lark.
9804 - Authorities now vote for the Stable flag for any router whose
9805 weighted MTBF is at least 5 days, regardless of the mean MTBF.
9806 - Clients now never report any stream end reason except 'MISC'.
9807 Implements proposal 148.
9809 o Major bugfixes (crashes):
9810 - Parse dates and IPv4 addresses in a locale- and libc-independent
9811 manner, to avoid platform-dependent behavior on malformed input.
9812 - Fix a crash that occurs on exit nodes when a nameserver request
9813 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
9814 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
9816 - Do not assume that a stack-allocated character array will be
9817 64-bit aligned on platforms that demand that uint64_t access is
9818 aligned. Possible fix for bug 604.
9819 - Resolve a very rare crash bug that could occur when the user forced
9820 a nameserver reconfiguration during the middle of a nameserver
9821 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
9822 - Avoid a "0 divided by 0" calculation when calculating router uptime
9823 at directory authorities. Bugfix on 0.2.0.8-alpha.
9824 - Fix an assertion bug in parsing policy-related options; possible fix
9826 - Rate-limit too-many-sockets messages: when they happen, they happen
9827 a lot and end up filling up the disk. Resolves bug 748.
9828 - Fix a race condition that could cause crashes or memory corruption
9829 when running as a server with a controller listening for log
9831 - Avoid crashing when we have a policy specified in a DirPolicy or
9832 SocksPolicy or ReachableAddresses option with ports set on it,
9833 and we re-load the policy. May fix bug 996.
9834 - Fix an assertion failure on 64-bit platforms when we allocated
9835 memory right up to the end of a memarea, then realigned the memory
9836 one step beyond the end. Fixes a possible cause of bug 930.
9837 - Protect the count of open sockets with a mutex, so we can't
9838 corrupt it when two threads are closing or opening sockets at once.
9839 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
9841 o Major bugfixes (clients):
9842 - Discard router descriptors as we load them if they are more than
9843 five days old. Otherwise if Tor is off for a long time and then
9844 starts with cached descriptors, it will try to use the onion keys
9845 in those obsolete descriptors when building circuits. Fixes bug 887.
9846 - When we choose to abandon a new entry guard because we think our
9847 older ones might be better, close any circuits pending on that
9848 new entry guard connection. This fix should make us recover much
9849 faster when our network is down and then comes back. Bugfix on
9850 0.1.2.8-beta; found by lodger.
9851 - When Tor clients restart after 1-5 days, they discard all their
9852 cached descriptors as too old, but they still use the cached
9853 consensus document. This approach is good for robustness, but
9854 bad for performance: since they don't know any bandwidths, they
9855 end up choosing at random rather than weighting their choice by
9856 speed. Fixed by the above feature of putting bandwidths in the
9859 o Major bugfixes (relays):
9860 - Relays were falling out of the networkstatus consensus for
9861 part of a day if they changed their local config but the
9862 authorities discarded their new descriptor as "not sufficiently
9863 different". Now directory authorities accept a descriptor as changed
9864 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
9866 - Ensure that two circuits can never exist on the same connection
9867 with the same circuit ID, even if one is marked for close. This
9868 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
9869 - Directory authorities were neglecting to mark relays down in their
9870 internal histories if the relays fall off the routerlist without
9871 ever being found unreachable. So there were relays in the histories
9872 that haven't been seen for eight months, and are listed as being
9873 up for eight months. This wreaked havoc on the "median wfu" and
9874 "median mtbf" calculations, in turn making Guard and Stable flags
9875 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
9878 o Major bugfixes (hidden services):
9879 - When establishing a hidden service, introduction points that
9880 originate from cannibalized circuits were completely ignored
9881 and not included in rendezvous service descriptors. This might
9882 have been another reason for delay in making a hidden service
9883 available. Bugfix from long ago (0.0.9.x?)
9885 o Major bugfixes (memory and resource management):
9886 - Fixed some memory leaks -- some quite frequent, some almost
9887 impossible to trigger -- based on results from Coverity.
9888 - Speed up parsing and cut down on memory fragmentation by using
9889 stack-style allocations for parsing directory objects. Previously,
9890 this accounted for over 40% of allocations from within Tor's code
9891 on a typical directory cache.
9892 - Use a Bloom filter rather than a digest-based set to track which
9893 descriptors we need to keep around when we're cleaning out old
9894 router descriptors. This speeds up the computation significantly,
9895 and may reduce fragmentation.
9897 o New/changed config options:
9898 - Now NodeFamily and MyFamily config options allow spaces in
9899 identity fingerprints, so it's easier to paste them in.
9900 Suggested by Lucky Green.
9901 - Allow ports 465 and 587 in the default exit policy again. We had
9902 rejected them in 0.1.0.15, because back in 2005 they were commonly
9903 misconfigured and ended up as spam targets. We hear they are better
9904 locked down these days.
9905 - Make TrackHostExit mappings expire a while after their last use, not
9906 after their creation. Patch from Robert Hogan.
9907 - Add an ExcludeExitNodes option so users can list a set of nodes
9908 that should be be excluded from the exit node position, but
9909 allowed elsewhere. Implements proposal 151.
9910 - New --hush command-line option similar to --quiet. While --quiet
9911 disables all logging to the console on startup, --hush limits the
9912 output to messages of warning and error severity.
9913 - New configure/torrc options (--enable-geoip-stats,
9914 DirRecordUsageByCountry) to record how many IPs we've served
9915 directory info to in each country code, how many status documents
9916 total we've sent to each country code, and what share of the total
9917 directory requests we should expect to see.
9918 - Make outbound DNS packets respect the OutboundBindAddress setting.
9919 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
9920 - Allow separate log levels to be configured for different logging
9921 domains. For example, this allows one to log all notices, warnings,
9922 or errors, plus all memory management messages of level debug or
9923 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
9924 - Update to the "June 3 2009" ip-to-country file.
9926 o Minor features (relays):
9927 - Raise the minimum rate limiting to be a relay from 20000 bytes
9928 to 20480 bytes (aka 20KB/s), to match our documentation. Also
9929 update directory authorities so they always assign the Fast flag
9930 to relays with 20KB/s of capacity. Now people running relays won't
9931 suddenly find themselves not seeing any use, if the network gets
9933 - If we're a relay and we change our IP address, be more verbose
9934 about the reason that made us change. Should help track down
9935 further bugs for relays on dynamic IP addresses.
9936 - Exit servers can now answer resolve requests for ip6.arpa addresses.
9937 - Implement most of Proposal 152: allow specialized servers to permit
9938 single-hop circuits, and clients to use those servers to build
9939 single-hop circuits when using a specialized controller. Patch
9940 from Josh Albrecht. Resolves feature request 768.
9941 - When relays do their initial bandwidth measurement, don't limit
9942 to just our entry guards for the test circuits. Otherwise we tend
9943 to have multiple test circuits going through a single entry guard,
9944 which makes our bandwidth test less accurate. Fixes part of bug 654;
9945 patch contributed by Josh Albrecht.
9947 o Minor features (directory authorities):
9948 - Try not to open more than one descriptor-downloading connection
9949 to an authority at once. This should reduce load on directory
9950 authorities. Fixes bug 366.
9951 - Add cross-certification to newly generated certificates, so that
9952 a signing key is enough information to look up a certificate. Start
9953 serving certificates by <identity digest, signing key digest>
9954 pairs. Implements proposal 157.
9955 - When a directory authority downloads a descriptor that it then
9956 immediately rejects, do not retry downloading it right away. Should
9957 save some bandwidth on authorities. Fix for bug 888. Patch by
9959 - Directory authorities now serve a /tor/dbg-stability.txt URL to
9960 help debug WFU and MTBF calculations.
9961 - In directory authorities' approved-routers files, allow
9962 fingerprints with or without space.
9964 o Minor features (directory mirrors):
9965 - When a download gets us zero good descriptors, do not notify
9966 Tor that new directory information has arrived.
9967 - Servers support a new URL scheme for consensus downloads that
9968 allows the client to specify which authorities are trusted.
9969 The server then only sends the consensus if the client will trust
9970 it. Otherwise a 404 error is sent back. Clients use this
9971 new scheme when the server supports it (meaning it's running
9972 0.2.1.1-alpha or later). Implements proposal 134.
9974 o Minor features (bridges):
9975 - If the bridge config line doesn't specify a port, assume 443.
9976 This makes bridge lines a bit smaller and easier for users to
9978 - If we're using bridges and our network goes away, be more willing
9979 to forgive our bridges and try again when we get an application
9982 o Minor features (hidden services):
9983 - When the client launches an introduction circuit, retry with a
9984 new circuit after 30 seconds rather than 60 seconds.
9985 - Launch a second client-side introduction circuit in parallel
9986 after a delay of 15 seconds (based on work by Christian Wilms).
9987 - Hidden services start out building five intro circuits rather
9988 than three, and when the first three finish they publish a service
9989 descriptor using those. Now we publish our service descriptor much
9990 faster after restart.
9991 - Drop the requirement to have an open dir port for storing and
9992 serving v2 hidden service descriptors.
9994 o Minor features (build and packaging):
9995 - On Linux, use the prctl call to re-enable core dumps when the User
9997 - Try to make sure that the version of Libevent we're running with
9998 is binary-compatible with the one we built with. May address bug
10000 - Add a new --enable-local-appdata configuration switch to change
10001 the default location of the datadir on win32 from APPDATA to
10002 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
10003 entirely. Patch from coderman.
10004 - Build correctly against versions of OpenSSL 0.9.8 or later that
10005 are built without support for deprecated functions.
10006 - On platforms with a maximum syslog string length, truncate syslog
10007 messages to that length ourselves, rather than relying on the
10008 system to do it for us.
10009 - Automatically detect MacOSX versions earlier than 10.4.0, and
10010 disable kqueue from inside Tor when running with these versions.
10011 We previously did this from the startup script, but that was no
10012 help to people who didn't use the startup script. Resolves bug 863.
10013 - Build correctly when configured to build outside the main source
10014 path. Patch from Michael Gold.
10015 - Disable GCC's strict alias optimization by default, to avoid the
10016 likelihood of its introducing subtle bugs whenever our code violates
10017 the letter of C99's alias rules.
10018 - Change the contrib/tor.logrotate script so it makes the new
10019 logs as "_tor:_tor" rather than the default, which is generally
10020 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
10021 - Change our header file guard macros to be less likely to conflict
10022 with system headers. Adam Langley noticed that we were conflicting
10023 with log.h on Android.
10024 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
10025 and stop using a warning that had become unfixably verbose under
10027 - Use a lockfile to make sure that two Tor processes are not
10028 simultaneously running with the same datadir.
10029 - Allow OpenSSL to use dynamic locks if it wants.
10030 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
10032 o Minor features (controllers):
10033 - When generating circuit events with verbose nicknames for
10034 controllers, try harder to look up nicknames for routers on a
10035 circuit. (Previously, we would look in the router descriptors we had
10036 for nicknames, but not in the consensus.) Partial fix for bug 941.
10037 - New controller event NEWCONSENSUS that lists the networkstatus
10038 lines for every recommended relay. Now controllers like Torflow
10039 can keep up-to-date on which relays they should be using.
10040 - New controller event "clients_seen" to report a geoip-based summary
10041 of which countries we've seen clients from recently. Now controllers
10042 like Vidalia can show bridge operators that they're actually making
10044 - Add a 'getinfo status/clients-seen' controller command, in case
10045 controllers want to hear clients_seen events but connect late.
10046 - New CONSENSUS_ARRIVED event to note when a new consensus has
10047 been fetched and validated.
10048 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
10049 controllers to prevent SIGHUP from reloading the configuration.
10051 - Return circuit purposes in response to GETINFO circuit-status.
10053 - Serve the latest v3 networkstatus consensus via the control
10054 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
10055 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
10056 controller can query our current bootstrap state in case it attaches
10057 partway through and wants to catch up.
10058 - Provide circuit purposes along with circuit events to the controller.
10060 o Minor features (tools):
10061 - Do not have tor-resolve automatically refuse all .onion addresses;
10062 if AutomapHostsOnResolve is set in your torrc, this will work fine.
10063 - Add a -p option to tor-resolve for specifying the SOCKS port: some
10064 people find host:port too confusing.
10065 - Print the SOCKS5 error message string as well as the error code
10066 when a tor-resolve request fails. Patch from Jacob.
10068 o Minor bugfixes (memory and resource management):
10069 - Clients no longer cache certificates for authorities they do not
10070 recognize. Bugfix on 0.2.0.9-alpha.
10071 - Do not use C's stdio library for writing to log files. This will
10072 improve logging performance by a minute amount, and will stop
10073 leaking fds when our disk is full. Fixes bug 861.
10074 - Stop erroneous use of O_APPEND in cases where we did not in fact
10075 want to re-seek to the end of a file before every last write().
10076 - Fix a small alignment and memory-wasting bug on buffer chunks.
10078 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
10079 to avoid unused RAM in buffer chunks and memory pools.
10080 - Reduce the default smartlist size from 32 to 16; it turns out that
10081 most smartlists hold around 8-12 elements tops.
10082 - Make dumpstats() log the fullness and size of openssl-internal
10084 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
10085 patch to their OpenSSL, turn it on to save memory on servers. This
10086 patch will (with any luck) get included in a mainline distribution
10088 - Fix a memory leak when v3 directory authorities load their keys
10089 and cert from disk. Bugfix on 0.2.0.1-alpha.
10090 - Stop using malloc_usable_size() to use more area than we had
10091 actually allocated: it was safe, but made valgrind really unhappy.
10092 - Make the assert_circuit_ok() function work correctly on circuits that
10093 have already been marked for close.
10094 - Fix uninitialized size field for memory area allocation: may improve
10095 memory performance during directory parsing.
10097 o Minor bugfixes (clients):
10098 - Stop reloading the router list from disk for no reason when we
10099 run out of reachable directory mirrors. Once upon a time reloading
10100 it would set the 'is_running' flag back to 1 for them. It hasn't
10101 done that for a long time.
10102 - When we had picked an exit node for a connection, but marked it as
10103 "optional", and it turned out we had no onion key for the exit,
10104 stop wanting that exit and try again. This situation may not
10105 be possible now, but will probably become feasible with proposal
10106 158. Spotted by rovv. Fixes another case of bug 752.
10107 - Fix a bug in address parsing that was preventing bridges or hidden
10108 service targets from being at IPv6 addresses.
10109 - Do not remove routers as too old if we do not have any consensus
10110 document. Bugfix on 0.2.0.7-alpha.
10111 - When an exit relay resolves a stream address to a local IP address,
10112 do not just keep retrying that same exit relay over and
10113 over. Instead, just close the stream. Addresses bug 872. Bugfix
10114 on 0.2.0.32. Patch from rovv.
10115 - Made Tor a little less aggressive about deleting expired
10116 certificates. Partial fix for bug 854.
10117 - Treat duplicate certificate fetches as failures, so that we do
10118 not try to re-fetch an expired certificate over and over and over.
10119 - Do not say we're fetching a certificate when we'll in fact skip it
10120 because of a pending download.
10121 - If we have correct permissions on $datadir, we complain to stdout
10122 and fail to start. But dangerous permissions on
10123 $datadir/cached-status/ would cause us to open a log and complain
10124 there. Now complain to stdout and fail to start in both cases. Fixes
10125 bug 820, reported by seeess.
10127 o Minor bugfixes (bridges):
10128 - When we made bridge authorities stop serving bridge descriptors over
10129 unencrypted links, we also broke DirPort reachability testing for
10130 bridges. So bridges with a non-zero DirPort were printing spurious
10131 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
10132 - Don't allow a bridge to publish its router descriptor to a
10133 non-bridge directory authority. Fixes part of bug 932.
10134 - When we change to or from being a bridge, reset our counts of
10135 client usage by country. Fixes bug 932.
10137 o Minor bugfixes (relays):
10138 - Log correct error messages for DNS-related network errors on
10140 - Actually return -1 in the error case for read_bandwidth_usage().
10141 Harmless bug, since we currently don't care about the return value
10142 anywhere. Bugfix on 0.2.0.9-alpha.
10143 - Provide a more useful log message if bug 977 (related to buffer
10144 freelists) ever reappears, and do not crash right away.
10145 - We were already rejecting relay begin cells with destination port
10146 of 0. Now also reject extend cells with destination port or address
10147 of 0. Suggested by lark.
10148 - When we can't transmit a DNS request due to a network error, retry
10149 it after a while, and eventually transmit a failing response to
10150 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
10151 - Solve a bug that kept hardware crypto acceleration from getting
10152 enabled when accounting was turned on. Fixes bug 907. Bugfix on
10154 - When a canonical connection appears later in our internal list
10155 than a noncanonical one for a given OR ID, always use the
10156 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
10158 - Avoid some nasty corner cases in the logic for marking connections
10159 as too old or obsolete or noncanonical for circuits. Partial
10161 - Fix another interesting corner-case of bug 891 spotted by rovv:
10162 Previously, if two hosts had different amounts of clock drift, and
10163 one of them created a new connection with just the wrong timing,
10164 the other might decide to deprecate the new connection erroneously.
10165 Bugfix on 0.1.1.13-alpha.
10166 - If one win32 nameserver fails to get added, continue adding the
10167 rest, and don't automatically fail.
10168 - Fix a bug where an unreachable relay would establish enough
10169 reachability testing circuits to do a bandwidth test -- if
10170 we already have a connection to the middle hop of the testing
10171 circuit, then it could establish the last hop by using the existing
10172 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
10173 circuits no longer use entry guards in 0.2.1.3-alpha.
10175 o Minor bugfixes (directory authorities):
10176 - Limit uploaded directory documents to be 16M rather than 500K.
10177 The directory authorities were refusing v3 consensus votes from
10178 other authorities, since the votes are now 504K. Fixes bug 959;
10179 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
10180 - Directory authorities should never send a 503 "busy" response to
10181 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
10183 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
10184 headers. Bugfix on 0.2.0.10-alpha.
10186 o Minor bugfixes (hidden services):
10187 - When we can't find an intro key for a v2 hidden service descriptor,
10188 fall back to the v0 hidden service descriptor and log a bug message.
10189 Workaround for bug 1024.
10190 - In very rare situations new hidden service descriptors were
10191 published earlier than 30 seconds after the last change to the
10192 service. (We currently think that a hidden service descriptor
10193 that's been stable for 30 seconds is worth publishing.)
10194 - If a hidden service sends us an END cell, do not consider
10195 retrying the connection; just close it. Patch from rovv.
10196 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
10197 service directories if they have no advertised dir port. Bugfix
10200 o Minor bugfixes (tools):
10201 - In the torify(1) manpage, mention that tsocks will leak your
10204 o Minor bugfixes (controllers):
10205 - If the controller claimed responsibility for a stream, but that
10206 stream never finished making its connection, it would live
10207 forever in circuit_wait state. Now we close it after SocksTimeout
10208 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
10209 - Make DNS resolved controller events into "CLOSED", not
10210 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
10212 - The control port would close the connection before flushing long
10213 replies, such as the network consensus, if a QUIT command was issued
10214 before the reply had completed. Now, the control port flushes all
10215 pending replies before closing the connection. Also fix a spurious
10216 warning when a QUIT command is issued after a malformed or rejected
10217 AUTHENTICATE command, but before the connection was closed. Patch
10218 by Marcus Griep. Fixes bugs 1015 and 1016.
10219 - Fix a bug that made stream bandwidth get misreported to the
10222 o Deprecated and removed features:
10223 - The old "tor --version --version" command, which would print out
10224 the subversion "Id" of most of the source files, is now removed. It
10225 turned out to be less useful than we'd expected, and harder to
10227 - RedirectExits has been removed. It was deprecated since
10229 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
10230 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
10231 - Cell pools are now always enabled; --disable-cell-pools is ignored.
10232 - Directory mirrors no longer fetch the v1 directory or
10233 running-routers files. They are obsolete, and nobody asks for them
10234 anymore. This is the first step to making v1 authorities obsolete.
10235 - Take out the TestVia config option, since it was a workaround for
10236 a bug that was fixed in Tor 0.1.1.21.
10237 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
10238 HiddenServiceExcludeNodes as obsolete: they never worked properly,
10239 and nobody seems to be using them. Fixes bug 754. Bugfix on
10240 0.1.0.1-rc. Patch from Christian Wilms.
10241 - Remove all backward-compatibility code for relays running
10242 versions of Tor so old that they no longer work at all on the
10245 o Code simplifications and refactoring:
10246 - Tool-assisted documentation cleanup. Nearly every function or
10247 static variable in Tor should have its own documentation now.
10248 - Rename the confusing or_is_obsolete field to the more appropriate
10249 is_bad_for_new_circs, and move it to or_connection_t where it
10251 - Move edge-only flags from connection_t to edge_connection_t: not
10252 only is this better coding, but on machines of plausible alignment,
10253 it should save 4-8 bytes per connection_t. "Every little bit helps."
10254 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
10255 for consistency; keep old option working for backward compatibility.
10256 - Simplify the code for finding connections to use for a circuit.
10257 - Revise the connection_new functions so that a more typesafe variant
10258 exists. This will work better with Coverity, and let us find any
10259 actual mistakes we're making here.
10260 - Refactor unit testing logic so that dmalloc can be used sensibly
10261 with unit tests to check for memory leaks.
10262 - Move all hidden-service related fields from connection and circuit
10263 structure to substructures: this way they won't eat so much memory.
10264 - Squeeze 2-5% out of client performance (according to oprofile) by
10265 improving the implementation of some policy-manipulation functions.
10266 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
10267 be more efficient. Formerly it was quadratic in the number of
10268 servers; now it should be linear. Fixes bug 509.
10269 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
10270 and n_conn_id_digest fields into a separate structure that's
10271 only needed when the circuit has not yet attached to an n_conn.
10272 - Optimize out calls to time(NULL) that occur for every IO operation,
10273 or for every cell. On systems like Windows where time() is a
10274 slow syscall, this fix will be slightly helpful.
10277 Changes in version 0.2.0.35 - 2009-06-24
10279 - Avoid crashing in the presence of certain malformed descriptors.
10280 Found by lark, and by automated fuzzing.
10281 - Fix an edge case where a malicious exit relay could convince a
10282 controller that the client's DNS question resolves to an internal IP
10283 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10286 - Finally fix the bug where dynamic-IP relays disappear when their
10287 IP address changes: directory mirrors were mistakenly telling
10288 them their old address if they asked via begin_dir, so they
10289 never got an accurate answer about their new address, so they
10290 just vanished after a day. For belt-and-suspenders, relays that
10291 don't set Address in their config now avoid using begin_dir for
10292 all direct connections. Should fix bugs 827, 883, and 900.
10293 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10294 that would occur on some exit nodes when DNS failures and timeouts
10295 occurred in certain patterns. Fix for bug 957.
10298 - When starting with a cache over a few days old, do not leak
10299 memory for the obsolete router descriptors in it. Bugfix on
10300 0.2.0.33; fixes bug 672.
10301 - Hidden service clients didn't use a cached service descriptor that
10302 was older than 15 minutes, but wouldn't fetch a new one either,
10303 because there was already one in the cache. Now, fetch a v2
10304 descriptor unless the same descriptor was added to the cache within
10305 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10308 Changes in version 0.2.0.34 - 2009-02-08
10309 Tor 0.2.0.34 features several more security-related fixes. You should
10310 upgrade, especially if you run an exit relay (remote crash) or a
10311 directory authority (remote infinite loop), or you're on an older
10312 (pre-XP) or not-recently-patched Windows (remote exploit).
10314 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
10315 have many known flaws, and nobody should be using them. You should
10316 upgrade. If you're using a Linux or BSD and its packages are obsolete,
10317 stop using those packages and upgrade anyway.
10320 - Fix an infinite-loop bug on handling corrupt votes under certain
10321 circumstances. Bugfix on 0.2.0.8-alpha.
10322 - Fix a temporary DoS vulnerability that could be performed by
10323 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10324 - Avoid a potential crash on exit nodes when processing malformed
10325 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
10326 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10327 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10330 - Fix compilation on systems where time_t is a 64-bit integer.
10331 Patch from Matthias Drochner.
10332 - Don't consider expiring already-closed client connections. Fixes
10333 bug 893. Bugfix on 0.0.2pre20.
10336 Changes in version 0.2.0.33 - 2009-01-21
10337 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
10338 useful to users. It also finally fixes a bug where a relay or client
10339 that's been off for many days would take a long time to bootstrap.
10341 This update also fixes an important security-related bug reported by
10342 Ilja van Sprundel. You should upgrade. (We'll send out more details
10343 about the bug once people have had some time to upgrade.)
10346 - Fix a heap-corruption bug that may be remotely triggerable on
10347 some platforms. Reported by Ilja van Sprundel.
10350 - When a stream at an exit relay is in state "resolving" or
10351 "connecting" and it receives an "end" relay cell, the exit relay
10352 would silently ignore the end cell and not close the stream. If
10353 the client never closes the circuit, then the exit relay never
10354 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
10355 reported by "wood".
10356 - When sending CREATED cells back for a given circuit, use a 64-bit
10357 connection ID to find the right connection, rather than an addr:port
10358 combination. Now that we can have multiple OR connections between
10359 the same ORs, it is no longer possible to use addr:port to uniquely
10360 identify a connection.
10361 - Bridge relays that had DirPort set to 0 would stop fetching
10362 descriptors shortly after startup, and then briefly resume
10363 after a new bandwidth test and/or after publishing a new bridge
10364 descriptor. Bridge users that try to bootstrap from them would
10365 get a recent networkstatus but would get descriptors from up to
10366 18 hours earlier, meaning most of the descriptors were obsolete
10367 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
10368 - Prevent bridge relays from serving their 'extrainfo' document
10369 to anybody who asks, now that extrainfo docs include potentially
10370 sensitive aggregated client geoip summaries. Bugfix on
10372 - If the cached networkstatus consensus is more than five days old,
10373 discard it rather than trying to use it. In theory it could be
10374 useful because it lists alternate directory mirrors, but in practice
10375 it just means we spend many minutes trying directory mirrors that
10376 are long gone from the network. Also discard router descriptors as
10377 we load them if they are more than five days old, since the onion
10378 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
10381 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
10382 could make gcc generate non-functional binary search code. Bugfix
10384 - Build correctly on platforms without socklen_t.
10385 - Compile without warnings on solaris.
10386 - Avoid potential crash on internal error during signature collection.
10387 Fixes bug 864. Patch from rovv.
10388 - Correct handling of possible malformed authority signing key
10389 certificates with internal signature types. Fixes bug 880.
10390 Bugfix on 0.2.0.3-alpha.
10391 - Fix a hard-to-trigger resource leak when logging credential status.
10393 - When we can't initialize DNS because the network is down, do not
10394 automatically stop Tor from starting. Instead, we retry failed
10395 dns_init() every 10 minutes, and change the exit policy to reject
10396 *:* until one succeeds. Fixes bug 691.
10397 - Use 64 bits instead of 32 bits for connection identifiers used with
10398 the controller protocol, to greatly reduce risk of identifier reuse.
10399 - When we're choosing an exit node for a circuit, and we have
10400 no pending streams, choose a good general exit rather than one that
10401 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
10402 - Fix another case of assuming, when a specific exit is requested,
10403 that we know more than the user about what hosts it allows.
10404 Fixes one case of bug 752. Patch from rovv.
10405 - Clip the MaxCircuitDirtiness config option to a minimum of 10
10406 seconds. Warn the user if lower values are given in the
10407 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
10408 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
10409 user if lower values are given in the configuration. Bugfix on
10410 0.1.1.17-rc. Patch by Sebastian.
10411 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
10412 the cache because we already had a v0 descriptor with the same ID.
10413 Bugfix on 0.2.0.18-alpha.
10414 - Fix a race condition when freeing keys shared between main thread
10415 and CPU workers that could result in a memory leak. Bugfix on
10416 0.1.0.1-rc. Fixes bug 889.
10417 - Send a valid END cell back when a client tries to connect to a
10418 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
10419 840. Patch from rovv.
10420 - Check which hops rendezvous stream cells are associated with to
10421 prevent possible guess-the-streamid injection attacks from
10422 intermediate hops. Fixes another case of bug 446. Based on patch
10424 - If a broken client asks a non-exit router to connect somewhere,
10425 do not even do the DNS lookup before rejecting the connection.
10426 Fixes another case of bug 619. Patch from rovv.
10427 - When a relay gets a create cell it can't decrypt (e.g. because it's
10428 using the wrong onion key), we were dropping it and letting the
10429 client time out. Now actually answer with a destroy cell. Fixes
10430 bug 904. Bugfix on 0.0.2pre8.
10432 o Minor bugfixes (hidden services):
10433 - Do not throw away existing introduction points on SIGHUP. Bugfix on
10434 0.0.6pre1. Patch by Karsten. Fixes bug 874.
10437 - Report the case where all signatures in a detached set are rejected
10438 differently than the case where there is an error handling the
10440 - When we realize that another process has modified our cached
10441 descriptors, print out a more useful error message rather than
10442 triggering an assertion. Fixes bug 885. Patch from Karsten.
10443 - Implement the 0x20 hack to better resist DNS poisoning: set the
10444 case on outgoing DNS requests randomly, and reject responses that do
10445 not match the case correctly. This logic can be disabled with the
10446 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
10447 of servers that do not reliably preserve case in replies. See
10448 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
10450 - Check DNS replies for more matching fields to better resist DNS
10452 - Never use OpenSSL compression: it wastes RAM and CPU trying to
10453 compress cells, which are basically all encrypted, compressed, or
10457 Changes in version 0.2.0.32 - 2008-11-20
10458 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
10459 packages (and maybe other packages) noticed by Theo de Raadt, fixes
10460 a smaller security flaw that might allow an attacker to access local
10461 services, further improves hidden service performance, and fixes a
10462 variety of other issues.
10465 - The "User" and "Group" config options did not clear the
10466 supplementary group entries for the Tor process. The "User" option
10467 is now more robust, and we now set the groups to the specified
10468 user's primary group. The "Group" option is now ignored. For more
10469 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
10470 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
10471 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
10472 - The "ClientDNSRejectInternalAddresses" config option wasn't being
10473 consistently obeyed: if an exit relay refuses a stream because its
10474 exit policy doesn't allow it, we would remember what IP address
10475 the relay said the destination address resolves to, even if it's
10476 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
10479 - Fix a DOS opportunity during the voting signature collection process
10480 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
10482 o Major bugfixes (hidden services):
10483 - When fetching v0 and v2 rendezvous service descriptors in parallel,
10484 we were failing the whole hidden service request when the v0
10485 descriptor fetch fails, even if the v2 fetch is still pending and
10486 might succeed. Similarly, if the last v2 fetch fails, we were
10487 failing the whole hidden service request even if a v0 fetch is
10488 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
10489 - When extending a circuit to a hidden service directory to upload a
10490 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
10491 requests failed, because the router descriptor has not been
10492 downloaded yet. In these cases, do not attempt to upload the
10493 rendezvous descriptor, but wait until the router descriptor is
10494 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
10495 descriptor from a hidden service directory for which the router
10496 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
10500 - Fix several infrequent memory leaks spotted by Coverity.
10501 - When testing for libevent functions, set the LDFLAGS variable
10502 correctly. Found by Riastradh.
10503 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
10504 bootstrapping with tunneled directory connections. Bugfix on
10505 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
10506 - When asked to connect to A.B.exit:80, if we don't know the IP for A
10507 and we know that server B rejects most-but-not all connections to
10508 port 80, we would previously reject the connection. Now, we assume
10509 the user knows what they were asking for. Fixes bug 752. Bugfix
10510 on 0.0.9rc5. Diagnosed by BarkerJr.
10511 - If we overrun our per-second write limits a little, count this as
10512 having used up our write allocation for the second, and choke
10513 outgoing directory writes. Previously, we had only counted this when
10514 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
10515 Bugfix on 0.2.0.x (??).
10516 - Remove the old v2 directory authority 'lefkada' from the default
10517 list. It has been gone for many months.
10518 - Stop doing unaligned memory access that generated bus errors on
10519 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
10520 - Make USR2 log-level switch take effect immediately. Bugfix on
10523 o Minor bugfixes (controller):
10524 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
10525 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
10528 Changes in version 0.2.0.31 - 2008-09-03
10529 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
10530 a big bug we're seeing where in rare cases traffic from one Tor stream
10531 gets mixed into another stream, and fixes a variety of smaller issues.
10534 - Make sure that two circuits can never exist on the same connection
10535 with the same circuit ID, even if one is marked for close. This
10536 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
10537 - Relays now reject risky extend cells: if the extend cell includes
10538 a digest of all zeroes, or asks to extend back to the relay that
10539 sent the extend cell, tear down the circuit. Ideas suggested
10541 - If not enough of our entry guards are available so we add a new
10542 one, we might use the new one even if it overlapped with the
10543 current circuit's exit relay (or its family). Anonymity bugfix
10544 pointed out by rovv.
10547 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10548 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
10549 - Correctly detect the presence of the linux/netfilter_ipv4.h header
10550 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
10551 - Pick size of default geoip filename string correctly on windows.
10552 Fixes bug 806. Bugfix on 0.2.0.30.
10553 - Make the autoconf script accept the obsolete --with-ssl-dir
10554 option as an alias for the actually-working --with-openssl-dir
10555 option. Fix the help documentation to recommend --with-openssl-dir.
10556 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
10557 - When using the TransPort option on OpenBSD, and using the User
10558 option to change UID and drop privileges, make sure to open
10559 /dev/pf before dropping privileges. Fixes bug 782. Patch from
10560 Christopher Davis. Bugfix on 0.1.2.1-alpha.
10561 - Try to attach connections immediately upon receiving a RENDEZVOUS2
10562 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
10563 on the client side when connecting to a hidden service. Bugfix
10564 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
10565 - When closing an application-side connection because its circuit is
10566 getting torn down, generate the stream event correctly. Bugfix on
10567 0.1.2.x. Anonymous patch.
10570 Changes in version 0.2.0.30 - 2008-07-15
10571 This new stable release switches to a more efficient directory
10572 distribution design, adds features to make connections to the Tor
10573 network harder to block, allows Tor to act as a DNS proxy, adds separate
10574 rate limiting for relayed traffic to make it easier for clients to
10575 become relays, fixes a variety of potential anonymity problems, and
10576 includes the usual huge pile of other features and bug fixes.
10578 o New v3 directory design:
10579 - Tor now uses a new way to learn about and distribute information
10580 about the network: the directory authorities vote on a common
10581 network status document rather than each publishing their own
10582 opinion. Now clients and caches download only one networkstatus
10583 document to bootstrap, rather than downloading one for each
10584 authority. Clients only download router descriptors listed in
10585 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
10587 - Set up moria1, tor26, and dizum as v3 directory authorities
10588 in addition to being v2 authorities. Also add three new ones:
10589 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
10590 dannenberg (run by CCC).
10591 - Switch to multi-level keys for directory authorities: now their
10592 long-term identity key can be kept offline, and they periodically
10593 generate a new signing key. Clients fetch the "key certificates"
10594 to keep up to date on the right keys. Add a standalone tool
10595 "tor-gencert" to generate key certificates. Implements proposal 103.
10596 - Add a new V3AuthUseLegacyKey config option to make it easier for
10597 v3 authorities to change their identity keys if another bug like
10598 Debian's OpenSSL RNG flaw appears.
10599 - Authorities and caches fetch the v2 networkstatus documents
10600 less often, now that v3 is recommended.
10602 o Make Tor connections stand out less on the wire:
10603 - Use an improved TLS handshake designed by Steven Murdoch in proposal
10604 124, as revised in proposal 130. The new handshake is meant to
10605 be harder for censors to fingerprint, and it adds the ability
10606 to detect certain kinds of man-in-the-middle traffic analysis
10607 attacks. The new handshake format includes version negotiation for
10608 OR connections as described in proposal 105, which will allow us
10609 to improve Tor's link protocol more safely in the future.
10610 - Enable encrypted directory connections by default for non-relays,
10611 so censor tools that block Tor directory connections based on their
10612 plaintext patterns will no longer work. This means Tor works in
10613 certain censored countries by default again.
10614 - Stop including recognizeable strings in the commonname part of
10615 Tor's x509 certificates.
10617 o Implement bridge relays:
10618 - Bridge relays (or "bridges" for short) are Tor relays that aren't
10619 listed in the main Tor directory. Since there is no complete public
10620 list of them, even an ISP that is filtering connections to all the
10621 known Tor relays probably won't be able to block all the bridges.
10622 See doc/design-paper/blocking.pdf and proposal 125 for details.
10623 - New config option BridgeRelay that specifies you want to be a
10624 bridge relay rather than a normal relay. When BridgeRelay is set
10625 to 1, then a) you cache dir info even if your DirPort ins't on,
10626 and b) the default for PublishServerDescriptor is now "bridge"
10627 rather than "v2,v3".
10628 - New config option "UseBridges 1" for clients that want to use bridge
10629 relays instead of ordinary entry guards. Clients then specify
10630 bridge relays by adding "Bridge" lines to their config file. Users
10631 can learn about a bridge relay either manually through word of
10632 mouth, or by one of our rate-limited mechanisms for giving out
10633 bridge addresses without letting an attacker easily enumerate them
10634 all. See https://www.torproject.org/bridges for details.
10635 - Bridge relays behave like clients with respect to time intervals
10636 for downloading new v3 consensus documents -- otherwise they
10637 stand out. Bridge users now wait until the end of the interval,
10638 so their bridge relay will be sure to have a new consensus document.
10640 o Implement bridge directory authorities:
10641 - Bridge authorities are like normal directory authorities, except
10642 they don't serve a list of known bridges. Therefore users that know
10643 a bridge's fingerprint can fetch a relay descriptor for that bridge,
10644 including fetching updates e.g. if the bridge changes IP address,
10645 yet an attacker can't just fetch a list of all the bridges.
10646 - Set up Tonga as the default bridge directory authority.
10647 - Bridge authorities refuse to serve bridge descriptors or other
10648 bridge information over unencrypted connections (that is, when
10649 responding to direct DirPort requests rather than begin_dir cells.)
10650 - Bridge directory authorities do reachability testing on the
10651 bridges they know. They provide router status summaries to the
10652 controller via "getinfo ns/purpose/bridge", and also dump summaries
10653 to a file periodically, so we can keep internal stats about which
10654 bridges are functioning.
10655 - If bridge users set the UpdateBridgesFromAuthority config option,
10656 but the digest they ask for is a 404 on the bridge authority,
10657 they fall back to contacting the bridge directly.
10658 - Bridges always use begin_dir to publish their server descriptor to
10659 the bridge authority using an anonymous encrypted tunnel.
10660 - Early work on a "bridge community" design: if bridge authorities set
10661 the BridgePassword config option, they will serve a snapshot of
10662 known bridge routerstatuses from their DirPort to anybody who
10663 knows that password. Unset by default.
10664 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
10665 report sanitized aggregated summaries in their extra-info documents
10666 privately to the bridge authority, listing which countries are
10667 able to reach them. We hope this mechanism will let us learn when
10668 certain countries start trying to block bridges.
10669 - Bridge authorities write bridge descriptors to disk, so they can
10670 reload them after a reboot. They can also export the descriptors
10671 to other programs, so we can distribute them to blocked users via
10672 the BridgeDB interface, e.g. via https://bridges.torproject.org/
10673 and bridges@torproject.org.
10675 o Tor can be a DNS proxy:
10676 - The new client-side DNS proxy feature replaces the need for
10677 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
10678 for DNS requests on port 9999, use the Tor network to resolve them
10679 anonymously, and send the reply back like a regular DNS server.
10680 The code still only implements a subset of DNS.
10681 - Add a new AutomapHostsOnResolve option: when it is enabled, any
10682 resolve request for hosts matching a given pattern causes Tor to
10683 generate an internal virtual address mapping for that host. This
10684 allows DNSPort to work sensibly with hidden service users. By
10685 default, .exit and .onion addresses are remapped; the list of
10686 patterns can be reconfigured with AutomapHostsSuffixes.
10687 - Add an "-F" option to tor-resolve to force a resolve for a .onion
10688 address. Thanks to the AutomapHostsOnResolve option, this is no
10689 longer a completely silly thing to do.
10691 o Major features (relay usability):
10692 - New config options RelayBandwidthRate and RelayBandwidthBurst:
10693 a separate set of token buckets for relayed traffic. Right now
10694 relayed traffic is defined as answers to directory requests, and
10695 OR connections that don't have any local circuits on them. See
10696 proposal 111 for details.
10697 - Create listener connections before we setuid to the configured
10698 User and Group. Now non-Windows users can choose port values
10699 under 1024, start Tor as root, and have Tor bind those ports
10700 before it changes to another UID. (Windows users could already
10702 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10703 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10704 on "vserver" accounts. Patch from coderman.
10706 o Major features (directory authorities):
10707 - Directory authorities track weighted fractional uptime and weighted
10708 mean-time-between failures for relays. WFU is suitable for deciding
10709 whether a node is "usually up", while MTBF is suitable for deciding
10710 whether a node is "likely to stay up." We need both, because
10711 "usually up" is a good requirement for guards, while "likely to
10712 stay up" is a good requirement for long-lived connections.
10713 - Directory authorities use a new formula for selecting which relays
10714 to advertise as Guards: they must be in the top 7/8 in terms of
10715 how long we have known about them, and above the median of those
10716 nodes in terms of weighted fractional uptime.
10717 - Directory authorities use a new formula for selecting which relays
10718 to advertise as Stable: when we have 4 or more days of data, use
10719 median measured MTBF rather than median declared uptime. Implements
10721 - Directory authorities accept and serve "extra info" documents for
10722 routers. Routers now publish their bandwidth-history lines in the
10723 extra-info docs rather than the main descriptor. This step saves
10724 60% (!) on compressed router descriptor downloads. Servers upload
10725 extra-info docs to any authority that accepts them; directory
10726 authorities now allow multiple router descriptors and/or extra
10727 info documents to be uploaded in a single go. Authorities, and
10728 caches that have been configured to download extra-info documents,
10729 download them as needed. Implements proposal 104.
10730 - Authorities now list relays who have the same nickname as
10731 a different named relay, but list them with a new flag:
10732 "Unnamed". Now we can make use of relays that happen to pick the
10733 same nickname as a server that registered two years ago and then
10734 disappeared. Implements proposal 122.
10735 - Store routers in a file called cached-descriptors instead of in
10736 cached-routers. Initialize cached-descriptors from cached-routers
10737 if the old format is around. The new format allows us to store
10738 annotations along with descriptors, to record the time we received
10739 each descriptor, its source, and its purpose: currently one of
10740 general, controller, or bridge.
10742 o Major features (other):
10743 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
10744 Tor can warn and/or refuse connections to ports commonly used with
10745 vulnerable-plaintext protocols. Currently we warn on ports 23,
10746 109, 110, and 143, but we don't reject any. Based on proposal 129
10747 by Kevin Bauer and Damon McCoy.
10748 - Integrate Karsten Loesing's Google Summer of Code project to publish
10749 hidden service descriptors on a set of redundant relays that are a
10750 function of the hidden service address. Now we don't have to rely
10751 on three central hidden service authorities for publishing and
10752 fetching every hidden service descriptor. Implements proposal 114.
10753 - Allow tunnelled directory connections to ask for an encrypted
10754 "begin_dir" connection or an anonymized "uses a full Tor circuit"
10755 connection independently. Now we can make anonymized begin_dir
10756 connections for (e.g.) more secure hidden service posting and
10759 o Major bugfixes (crashes and assert failures):
10760 - Stop imposing an arbitrary maximum on the number of file descriptors
10761 used for busy servers. Bug reported by Olaf Selke; patch from
10763 - Avoid possible failures when generating a directory with routers
10764 with over-long versions strings, or too many flags set.
10765 - Fix a rare assert error when we're closing one of our threads:
10766 use a mutex to protect the list of logs, so we never write to the
10767 list as it's being freed. Fixes the very rare bug 575, which is
10768 kind of the revenge of bug 222.
10769 - Avoid segfault in the case where a badly behaved v2 versioning
10770 directory sends a signed networkstatus with missing client-versions.
10771 - When we hit an EOF on a log (probably because we're shutting down),
10772 don't try to remove the log from the list: just mark it as
10773 unusable. (Bulletproofs against bug 222.)
10775 o Major bugfixes (code security fixes):
10776 - Detect size overflow in zlib code. Reported by Justin Ferguson and
10778 - Rewrite directory tokenization code to never run off the end of
10779 a string. Fixes bug 455. Patch from croup.
10780 - Be more paranoid about overwriting sensitive memory on free(),
10781 as a defensive programming tactic to ensure forward secrecy.
10783 o Major bugfixes (anonymity fixes):
10784 - Reject requests for reverse-dns lookup of names that are in
10785 a private address space. Patch from lodger.
10786 - Never report that we've used more bandwidth than we're willing to
10787 relay: it leaks how much non-relay traffic we're using. Resolves
10789 - As a client, do not believe any server that tells us that an
10790 address maps to an internal address space.
10791 - Warn about unsafe ControlPort configurations.
10792 - Directory authorities now call routers Fast if their bandwidth is
10793 at least 100KB/s, and consider their bandwidth adequate to be a
10794 Guard if it is at least 250KB/s, no matter the medians. This fix
10795 complements proposal 107.
10796 - Directory authorities now never mark more than 2 servers per IP as
10797 Valid and Running (or 5 on addresses shared by authorities).
10798 Implements proposal 109, by Kevin Bauer and Damon McCoy.
10799 - If we're a relay, avoid picking ourselves as an introduction point,
10800 a rendezvous point, or as the final hop for internal circuits. Bug
10801 reported by taranis and lodger.
10802 - Exit relays that are used as a client can now reach themselves
10803 using the .exit notation, rather than just launching an infinite
10804 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
10805 - Fix a bug where, when we were choosing the 'end stream reason' to
10806 put in our relay end cell that we send to the exit relay, Tor
10807 clients on Windows were sometimes sending the wrong 'reason'. The
10808 anonymity problem is that exit relays may be able to guess whether
10809 the client is running Windows, thus helping partition the anonymity
10810 set. Down the road we should stop sending reasons to exit relays,
10811 or otherwise prevent future versions of this bug.
10812 - Only update guard status (usable / not usable) once we have
10813 enough directory information. This was causing us to discard all our
10814 guards on startup if we hadn't been running for a few weeks. Fixes
10816 - When our directory information has been expired for a while, stop
10817 being willing to build circuits using it. Fixes bug 401.
10819 o Major bugfixes (peace of mind for relay operators)
10820 - Non-exit relays no longer answer "resolve" relay cells, so they
10821 can't be induced to do arbitrary DNS requests. (Tor clients already
10822 avoid using non-exit relays for resolve cells, but now servers
10823 enforce this too.) Fixes bug 619. Patch from lodger.
10824 - When we setconf ClientOnly to 1, close any current OR and Dir
10825 listeners. Reported by mwenge.
10827 o Major bugfixes (other):
10828 - If we only ever used Tor for hidden service lookups or posts, we
10829 would stop building circuits and start refusing connections after
10830 24 hours, since we falsely believed that Tor was dormant. Reported
10832 - Add a new __HashedControlSessionPassword option for controllers
10833 to use for one-off session password hashes that shouldn't get
10834 saved to disk by SAVECONF --- Vidalia users were accumulating a
10835 pile of HashedControlPassword lines in their torrc files, one for
10836 each time they had restarted Tor and then clicked Save. Make Tor
10837 automatically convert "HashedControlPassword" to this new option but
10838 only when it's given on the command line. Partial fix for bug 586.
10839 - Patch from "Andrew S. Lists" to catch when we contact a directory
10840 mirror at IP address X and he says we look like we're coming from
10841 IP address X. Otherwise this would screw up our address detection.
10842 - Reject uploaded descriptors and extrainfo documents if they're
10843 huge. Otherwise we'll cache them all over the network and it'll
10844 clog everything up. Suggested by Aljosha Judmayer.
10845 - When a hidden service was trying to establish an introduction point,
10846 and Tor *did* manage to reuse one of the preemptively built
10847 circuits, it didn't correctly remember which one it used,
10848 so it asked for another one soon after, until there were no
10849 more preemptive circuits, at which point it launched one from
10850 scratch. Bugfix on 0.0.9.x.
10852 o Rate limiting and load balancing improvements:
10853 - When we add data to a write buffer in response to the data on that
10854 write buffer getting low because of a flush, do not consider the
10855 newly added data as a candidate for immediate flushing, but rather
10856 make it wait until the next round of writing. Otherwise, we flush
10857 and refill recursively, and a single greedy TLS connection can
10858 eat all of our bandwidth.
10859 - When counting the number of bytes written on a TLS connection,
10860 look at the BIO actually used for writing to the network, not
10861 at the BIO used (sometimes) to buffer data for the network.
10862 Looking at different BIOs could result in write counts on the
10863 order of ULONG_MAX. Fixes bug 614.
10864 - If we change our MaxAdvertisedBandwidth and then reload torrc,
10865 Tor won't realize it should publish a new relay descriptor. Fixes
10866 bug 688, reported by mfr.
10867 - Avoid using too little bandwidth when our clock skips a few seconds.
10868 - Choose which bridge to use proportional to its advertised bandwidth,
10869 rather than uniformly at random. This should speed up Tor for
10870 bridge users. Also do this for people who set StrictEntryNodes.
10872 o Bootstrapping faster and building circuits more intelligently:
10873 - Fix bug 660 that was preventing us from knowing that we should
10874 preemptively build circuits to handle expected directory requests.
10875 - When we're checking if we have enough dir info for each relay
10876 to begin establishing circuits, make sure that we actually have
10877 the descriptor listed in the consensus, not just any descriptor.
10878 - Correctly notify one-hop connections when a circuit build has
10879 failed. Possible fix for bug 669. Found by lodger.
10880 - Clients now hold circuitless TLS connections open for 1.5 times
10881 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
10882 rebuild a new circuit over them within that timeframe. Previously,
10883 they held them open only for KeepalivePeriod (5 minutes).
10885 o Performance improvements (memory):
10886 - Add OpenBSD malloc code from "phk" as an optional malloc
10887 replacement on Linux: some glibc libraries do very poorly with
10888 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
10889 ./configure to get the replacement malloc code.
10890 - Switch our old ring buffer implementation for one more like that
10891 used by free Unix kernels. The wasted space in a buffer with 1mb
10892 of data will now be more like 8k than 1mb. The new implementation
10893 also avoids realloc();realloc(); patterns that can contribute to
10894 memory fragmentation.
10895 - Change the way that Tor buffers data that it is waiting to write.
10896 Instead of queueing data cells in an enormous ring buffer for each
10897 client->OR or OR->OR connection, we now queue cells on a separate
10898 queue for each circuit. This lets us use less slack memory, and
10899 will eventually let us be smarter about prioritizing different kinds
10901 - Reference-count and share copies of address policy entries; only 5%
10902 of them were actually distinct.
10903 - Tune parameters for cell pool allocation to minimize amount of
10905 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
10906 for every single inactive connection_t. Free items from the
10907 4k/16k-buffer free lists when they haven't been used for a while.
10908 - Make memory debugging information describe more about history
10909 of cell allocation, so we can help reduce our memory use.
10910 - Be even more aggressive about releasing RAM from small
10911 empty buffers. Thanks to our free-list code, this shouldn't be too
10912 performance-intensive.
10913 - Log malloc statistics from mallinfo() on platforms where it exists.
10914 - Use memory pools to allocate cells with better speed and memory
10915 efficiency, especially on platforms where malloc() is inefficient.
10916 - Add a --with-tcmalloc option to the configure script to link
10917 against tcmalloc (if present). Does not yet search for non-system
10920 o Performance improvements (socket management):
10921 - Count the number of open sockets separately from the number of
10922 active connection_t objects. This will let us avoid underusing
10923 our allocated connection limit.
10924 - We no longer use socket pairs to link an edge connection to an
10925 anonymous directory connection or a DirPort test connection.
10926 Instead, we track the link internally and transfer the data
10927 in-process. This saves two sockets per "linked" connection (at the
10928 client and at the server), and avoids the nasty Windows socketpair()
10930 - We were leaking a file descriptor if Tor started with a zero-length
10931 cached-descriptors file. Patch by "freddy77".
10933 o Performance improvements (CPU use):
10934 - Never walk through the list of logs if we know that no log target
10935 is interested in a given message.
10936 - Call routerlist_remove_old_routers() much less often. This should
10937 speed startup, especially on directory caches.
10938 - Base64 decoding was actually showing up on our profile when parsing
10939 the initial descriptor file; switch to an in-process all-at-once
10940 implementation that's about 3.5x times faster than calling out to
10942 - Use a slightly simpler string hashing algorithm (copying Python's
10943 instead of Java's) and optimize our digest hashing algorithm to take
10944 advantage of 64-bit platforms and to remove some possibly-costly
10946 - When implementing AES counter mode, update only the portions of the
10947 counter buffer that need to change, and don't keep separate
10948 network-order and host-order counters on big-endian hosts (where
10949 they are the same).
10950 - Add an in-place version of aes_crypt() so that we can avoid doing a
10951 needless memcpy() call on each cell payload.
10952 - Use Critical Sections rather than Mutexes for synchronizing threads
10953 on win32; Mutexes are heavier-weight, and designed for synchronizing
10956 o Performance improvements (bandwidth use):
10957 - Don't try to launch new descriptor downloads quite so often when we
10958 already have enough directory information to build circuits.
10959 - Version 1 directories are no longer generated in full. Instead,
10960 authorities generate and serve "stub" v1 directories that list
10961 no servers. This will stop Tor versions 0.1.0.x and earlier from
10962 working, but (for security reasons) nobody should be running those
10964 - Avoid going directly to the directory authorities even if you're a
10965 relay, if you haven't found yourself reachable yet or if you've
10966 decided not to advertise your dirport yet. Addresses bug 556.
10967 - If we've gone 12 hours since our last bandwidth check, and we
10968 estimate we have less than 50KB bandwidth capacity but we could
10969 handle more, do another bandwidth test.
10970 - Support "If-Modified-Since" when answering HTTP requests for
10971 directories, running-routers documents, and v2 and v3 networkstatus
10972 documents. (There's no need to support it for router descriptors,
10973 since those are downloaded by descriptor digest.)
10974 - Stop fetching directory info so aggressively if your DirPort is
10975 on but your ORPort is off; stop fetching v2 dir info entirely.
10976 You can override these choices with the new FetchDirInfoEarly
10979 o Changed config option behavior (features):
10980 - Configuration files now accept C-style strings as values. This
10981 helps encode characters not allowed in the current configuration
10982 file format, such as newline or #. Addresses bug 557.
10983 - Add hidden services and DNSPorts to the list of things that make
10984 Tor accept that it has running ports. Change starting Tor with no
10985 ports from a fatal error to a warning; we might change it back if
10986 this turns out to confuse anybody. Fixes bug 579.
10987 - Make PublishServerDescriptor default to 1, so the default doesn't
10988 have to change as we invent new directory protocol versions.
10989 - Allow people to say PreferTunnelledDirConns rather than
10990 PreferTunneledDirConns, for those alternate-spellers out there.
10991 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
10992 accommodate the growing number of servers that use the default
10993 and are reaching it.
10994 - Make it possible to enable HashedControlPassword and
10995 CookieAuthentication at the same time.
10996 - When a TrackHostExits-chosen exit fails too many times in a row,
10997 stop using it. Fixes bug 437.
10999 o Changed config option behavior (bugfixes):
11000 - Do not read the configuration file when we've only been told to
11001 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
11002 based on patch from Sebastian Hahn.
11003 - Actually validate the options passed to AuthDirReject,
11004 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
11005 - Make "ClientOnly 1" config option disable directory ports too.
11006 - Don't stop fetching descriptors when FetchUselessDescriptors is
11007 set, even if we stop asking for circuits. Bug reported by tup
11009 - Servers used to decline to publish their DirPort if their
11010 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
11011 they look only at BandwidthRate and RelayBandwidthRate.
11012 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11013 minus 1 byte: the actual maximum declared bandwidth.
11014 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
11015 - Make the NodeFamilies config option work. (Reported by
11016 lodger -- it has never actually worked, even though we added it
11018 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11019 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11021 o New config options:
11022 - New configuration options AuthDirMaxServersPerAddr and
11023 AuthDirMaxServersperAuthAddr to override default maximum number
11024 of servers allowed on a single IP address. This is important for
11025 running a test network on a single host.
11026 - Three new config options (AlternateDirAuthority,
11027 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
11028 user selectively replace the default directory authorities by type,
11029 rather than the all-or-nothing replacement that DirServer offers.
11030 - New config options AuthDirBadDir and AuthDirListBadDirs for
11031 authorities to mark certain relays as "bad directories" in the
11032 networkstatus documents. Also supports the "!baddir" directive in
11033 the approved-routers file.
11034 - New config option V2AuthoritativeDirectory that all v2 directory
11035 authorities must set. This lets v3 authorities choose not to serve
11036 v2 directory information.
11038 o Minor features (other):
11039 - When we're not serving v2 directory information, there is no reason
11040 to actually keep any around. Remove the obsolete files and directory
11041 on startup if they are very old and we aren't going to serve them.
11042 - When we negotiate a v2 link-layer connection (not yet implemented),
11043 accept RELAY_EARLY cells and turn them into RELAY cells if we've
11044 negotiated a v1 connection for their next step. Initial steps for
11046 - When we have no consensus, check FallbackNetworkstatusFile (defaults
11047 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
11048 we can start out knowing some directory caches. We don't ship with
11049 a fallback consensus by default though, because it was making
11050 bootstrapping take too long while we tried many down relays.
11051 - Authorities send back an X-Descriptor-Not-New header in response to
11052 an accepted-but-discarded descriptor upload. Partially implements
11054 - If we find a cached-routers file that's been sitting around for more
11055 than 28 days unmodified, then most likely it's a leftover from
11056 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
11058 - When we (as a cache) download a descriptor because it was listed
11059 in a consensus, remember when the consensus was supposed to expire,
11060 and don't expire the descriptor until then.
11061 - Optionally (if built with -DEXPORTMALLINFO) export the output
11062 of mallinfo via http, as tor/mallinfo.txt. Only accessible
11064 - Tag every guard node in our state file with the version that
11065 we believe added it, or with our own version if we add it. This way,
11066 if a user temporarily runs an old version of Tor and then switches
11067 back to a new one, she doesn't automatically lose her guards.
11068 - When somebody requests a list of statuses or servers, and we have
11069 none of those, return a 404 rather than an empty 200.
11070 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
11072 - Add an HSAuthorityRecordStats option that hidden service authorities
11073 can use to track statistics of overall hidden service usage without
11074 logging information that would be as useful to an attacker.
11075 - Allow multiple HiddenServicePort directives with the same virtual
11076 port; when they occur, the user is sent round-robin to one
11077 of the target ports chosen at random. Partially fixes bug 393 by
11078 adding limited ad-hoc round-robining.
11079 - Revamp file-writing logic so we don't need to have the entire
11080 contents of a file in memory at once before we write to disk. Tor,
11083 o Minor bugfixes (other):
11084 - Alter the code that tries to recover from unhandled write
11085 errors, to not try to flush onto a socket that's given us
11087 - Directory mirrors no longer include a guess at the client's IP
11088 address if the connection appears to be coming from the same /24
11089 network; it was producing too many wrong guesses.
11090 - If we're trying to flush the last bytes on a connection (for
11091 example, when answering a directory request), reset the
11092 time-to-give-up timeout every time we manage to write something
11094 - Reject router descriptors with out-of-range bandwidthcapacity or
11095 bandwidthburst values.
11096 - If we can't expand our list of entry guards (e.g. because we're
11097 using bridges or we have StrictEntryNodes set), don't mark relays
11098 down when they fail a directory request. Otherwise we're too quick
11099 to mark all our entry points down.
11100 - Authorities no longer send back "400 you're unreachable please fix
11101 it" errors to Tor servers that aren't online all the time. We're
11102 supposed to tolerate these servers now.
11103 - Let directory authorities startup even when they can't generate
11104 a descriptor immediately, e.g. because they don't know their
11106 - Correctly enforce that elements of directory objects do not appear
11107 more often than they are allowed to appear.
11108 - Stop allowing hibernating servers to be "stable" or "fast".
11109 - On Windows, we were preventing other processes from reading
11110 cached-routers while Tor was running. (Reported by janbar)
11111 - Check return values from pthread_mutex functions.
11112 - When opening /dev/null in finish_daemonize(), do not pass the
11113 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
11114 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
11116 o Controller features:
11117 - The GETCONF command now escapes and quotes configuration values
11118 that don't otherwise fit into the torrc file.
11119 - The SETCONF command now handles quoted values correctly.
11120 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
11121 ask about source, timestamp of arrival, purpose, etc. We need
11122 something like this to help Vidalia not do GeoIP lookups on bridge
11124 - Allow multiple HashedControlPassword config lines, to support
11125 multiple controller passwords.
11126 - Accept LF instead of CRLF on controller, since some software has a
11127 hard time generating real Internet newlines.
11128 - Add GETINFO values for the server status events
11129 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
11131 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
11132 GETINFO for Torstat to use until it can switch to using extrainfos.
11133 - New config option CookieAuthFile to choose a new location for the
11134 cookie authentication file, and config option
11135 CookieAuthFileGroupReadable to make it group-readable.
11136 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
11137 match requests to applications. Patch from Robert Hogan.
11138 - Add a RESOLVE command to launch hostname lookups. Original patch
11140 - Add GETINFO status/enough-dir-info to let controllers tell whether
11141 Tor has downloaded sufficient directory information. Patch from Tup.
11142 - You can now use the ControlSocket option to tell Tor to listen for
11143 controller connections on Unix domain sockets on systems that
11144 support them. Patch from Peter Palfrader.
11145 - New "GETINFO address-mappings/*" command to get address mappings
11146 with expiry information. "addr-mappings/*" is now deprecated.
11148 - Add a new config option __DisablePredictedCircuits designed for
11149 use by the controller, when we don't want Tor to build any circuits
11151 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11152 so we can exit from the middle of the circuit.
11153 - Implement "getinfo status/circuit-established".
11154 - Implement "getinfo status/version/..." so a controller can tell
11155 whether the current version is recommended, and whether any versions
11156 are good, and how many authorities agree. Patch from "shibz".
11157 - Controllers should now specify cache=no or cache=yes when using
11158 the +POSTDESCRIPTOR command.
11159 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
11160 Robert Hogan. Fixes the first part of bug 681.
11161 - When reporting clock skew, and we know that the clock is _at least
11162 as skewed_ as some value, but we don't know the actual value,
11163 report the value as a "minimum skew."
11165 o Controller bugfixes:
11166 - Generate "STATUS_SERVER" events rather than misspelled
11167 "STATUS_SEVER" events. Caught by mwenge.
11168 - Reject controller commands over 1MB in length, so rogue
11169 processes can't run us out of memory.
11170 - Change the behavior of "getinfo status/good-server-descriptor"
11171 so it doesn't return failure when any authority disappears.
11172 - Send NAMESERVER_STATUS messages for a single failed nameserver
11174 - When the DANGEROUS_VERSION controller status event told us we're
11175 running an obsolete version, it used the string "OLD" to describe
11176 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
11177 "OBSOLETE" in both cases.
11178 - Respond to INT and TERM SIGNAL commands before we execute the
11179 signal, in case the signal shuts us down. We had a patch in
11180 0.1.2.1-alpha that tried to do this by queueing the response on
11181 the connection's buffer before shutting down, but that really
11182 isn't the same thing at all. Bug located by Matt Edman.
11183 - Provide DNS expiry times in GMT, not in local time. For backward
11184 compatibility, ADDRMAP events only provide GMT expiry in an extended
11185 field. "GETINFO address-mappings" always does the right thing.
11186 - Use CRLF line endings properly in NS events.
11187 - Make 'getinfo fingerprint' return a 551 error if we're not a
11188 server, so we match what the control spec claims we do. Reported
11190 - Fix a typo in an error message when extendcircuit fails that
11191 caused us to not follow the \r\n-based delimiter protocol. Reported
11193 - When tunneling an encrypted directory connection, and its first
11194 circuit fails, do not leave it unattached and ask the controller
11195 to deal. Fixes the second part of bug 681.
11196 - Treat some 403 responses from directory servers as INFO rather than
11197 WARN-severity events.
11199 o Portability / building / compiling:
11200 - When building with --enable-gcc-warnings, check for whether Apple's
11201 warning "-Wshorten-64-to-32" is available.
11202 - Support compilation to target iPhone; patch from cjacker huang.
11203 To build for iPhone, pass the --enable-iphone option to configure.
11204 - Port Tor to build and run correctly on Windows CE systems, using
11205 the wcecompat library. Contributed by Valerio Lupi.
11206 - Detect non-ASCII platforms (if any still exist) and refuse to
11207 build there: some of our code assumes that 'A' is 65 and so on.
11208 - Clear up some MIPSPro compiler warnings.
11209 - Make autoconf search for libevent, openssl, and zlib consistently.
11210 - Update deprecated macros in configure.in.
11211 - When warning about missing headers, tell the user to let us
11212 know if the compile succeeds anyway, so we can downgrade the
11214 - Include the current subversion revision as part of the version
11215 string: either fetch it directly if we're in an SVN checkout, do
11216 some magic to guess it if we're in an SVK checkout, or use
11217 the last-detected version if we're building from a .tar.gz.
11218 Use this version consistently in log messages.
11219 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11220 - Read resolv.conf files correctly on platforms where read() returns
11221 partial results on small file reads.
11222 - Build without verbose warnings even on gcc 4.2 and 4.3.
11223 - On Windows, correctly detect errors when listing the contents of
11224 a directory. Fix from lodger.
11225 - Run 'make test' as part of 'make dist', so we stop releasing so
11226 many development snapshots that fail their unit tests.
11227 - Add support to detect Libevent versions in the 1.4.x series
11229 - Add command-line arguments to unit-test executable so that we can
11230 invoke any chosen test from the command line rather than having
11231 to run the whole test suite at once; and so that we can turn on
11232 logging for the unit tests.
11233 - Do not automatically run configure from autogen.sh. This
11234 non-standard behavior tended to annoy people who have built other
11236 - Fix a macro/CPP interaction that was confusing some compilers:
11237 some GCCs don't like #if/#endif pairs inside macro arguments.
11239 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
11240 Fixes bug 704; fix from Steven Murdoch.
11241 - Correctly detect transparent proxy support on Linux hosts that
11242 require in.h to be included before netfilter_ipv4.h. Patch
11245 o Logging improvements:
11246 - When we haven't had any application requests lately, don't bother
11247 logging that we have expired a bunch of descriptors.
11248 - When attempting to open a logfile fails, tell us why.
11249 - Only log guard node status when guard node status has changed.
11250 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
11251 make "INFO" 75% less verbose.
11252 - When SafeLogging is disabled, log addresses along with all TLS
11254 - Report TLS "zero return" case as a "clean close" and "IO error"
11255 as a "close". Stop calling closes "unexpected closes": existing
11256 Tors don't use SSL_close(), so having a connection close without
11257 the TLS shutdown handshake is hardly unexpected.
11258 - When we receive a consensus from the future, warn about skew.
11259 - Make "not enough dir info yet" warnings describe *why* Tor feels
11260 it doesn't have enough directory info yet.
11261 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
11262 consumers. (We already do this on HUP.)
11263 - Give more descriptive well-formedness errors for out-of-range
11264 hidden service descriptor/protocol versions.
11265 - Stop recommending that every server operator send mail to tor-ops.
11266 Resolves bug 597. Bugfix on 0.1.2.x.
11267 - Improve skew reporting: try to give the user a better log message
11268 about how skewed they are, and how much this matters.
11269 - New --quiet command-line option to suppress the default console log.
11270 Good in combination with --hash-password.
11271 - Don't complain that "your server has not managed to confirm that its
11272 ports are reachable" if we haven't been able to build any circuits
11274 - Detect the reason for failing to mmap a descriptor file we just
11275 wrote, and give a more useful log message. Fixes bug 533.
11276 - Always prepend "Bug: " to any log message about a bug.
11277 - When dumping memory usage, list bytes used in buffer memory
11279 - When running with dmalloc, dump more stats on hup and on exit.
11280 - Put a platform string (e.g. "Linux i686") in the startup log
11281 message, so when people paste just their logs, we know if it's
11282 OpenBSD or Windows or what.
11283 - When logging memory usage, break down memory used in buffers by
11285 - When we are reporting the DirServer line we just parsed, we were
11286 logging the second stanza of the key fingerprint, not the first.
11287 - Even though Windows is equally happy with / and \ as path separators,
11288 try to use \ consistently on Windows and / consistently on Unix: it
11289 makes the log messages nicer.
11290 - On OSX, stop warning the user that kqueue support in libevent is
11291 "experimental", since it seems to have worked fine for ages.
11293 o Contributed scripts and tools:
11294 - Update linux-tor-prio.sh script to allow QoS based on the uid of
11295 the Tor process. Patch from Marco Bonetti with tweaks from Mike
11297 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
11298 Unix users an easy way to script their Tor process (e.g. by
11299 adjusting bandwidth based on the time of the day).
11300 - In the exitlist script, only consider the most recently published
11301 server descriptor for each server. Also, when the user requests
11302 a list of servers that _reject_ connections to a given address,
11303 explicitly exclude the IPs that also have servers that accept
11304 connections to that address. Resolves bug 405.
11305 - Include a new contrib/tor-exit-notice.html file that exit relay
11306 operators can put on their website to help reduce abuse queries.
11308 o Newly deprecated features:
11309 - The status/version/num-versioning and status/version/num-concurring
11310 GETINFO controller options are no longer useful in the v3 directory
11311 protocol: treat them as deprecated, and warn when they're used.
11312 - The RedirectExits config option is now deprecated.
11314 o Removed features:
11315 - Drop the old code to choke directory connections when the
11316 corresponding OR connections got full: thanks to the cell queue
11317 feature, OR conns don't get full any more.
11318 - Remove the old "dns worker" server DNS code: it hasn't been default
11319 since 0.1.2.2-alpha, and all the servers are using the new
11321 - Remove the code to generate the oldest (v1) directory format.
11322 - Remove support for the old bw_accounting file: we've been storing
11323 bandwidth accounting information in the state file since
11324 0.1.2.5-alpha. This may result in bandwidth accounting errors
11325 if you try to upgrade from 0.1.1.x or earlier, or if you try to
11326 downgrade to 0.1.1.x or earlier.
11327 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
11328 it, it had no AES, and it hasn't seen any security patches since
11330 - Stop overloading the circuit_t.onionskin field for both "onionskin
11331 from a CREATE cell that we are waiting for a cpuworker to be
11332 assigned" and "onionskin from an EXTEND cell that we are going to
11333 send to an OR as soon as we are connected". Might help with bug 600.
11334 - Remove the tor_strpartition() function: its logic was confused,
11335 and it was only used for one thing that could be implemented far
11337 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
11338 and TorControl.py, as they use the old v0 controller protocol,
11339 and are obsoleted by TorFlow anyway.
11340 - Drop support for v1 rendezvous descriptors, since we never used
11341 them anyway, and the code has probably rotted by now. Based on
11342 patch from Karsten Loesing.
11343 - Stop allowing address masks that do not correspond to bit prefixes.
11344 We have warned about these for a really long time; now it's time
11345 to reject them. (Patch from croup.)
11346 - Remove an optimization in the AES counter-mode code that assumed
11347 that the counter never exceeded 2^68. When the counter can be set
11348 arbitrarily as an IV (as it is by Karsten's new hidden services
11349 code), this assumption no longer holds.
11350 - Disable the SETROUTERPURPOSE controller command: it is now
11354 Changes in version 0.1.2.19 - 2008-01-17
11355 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
11356 exit policy a little bit more conservative so it's safer to run an
11357 exit relay on a home system, and fixes a variety of smaller issues.
11360 - Exit policies now reject connections that are addressed to a
11361 relay's public (external) IP address too, unless
11362 ExitPolicyRejectPrivate is turned off. We do this because too
11363 many relays are running nearby to services that trust them based
11364 on network address.
11367 - When the clock jumps forward a lot, do not allow the bandwidth
11368 buckets to become negative. Fixes bug 544.
11369 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
11370 on every successful resolve. Reported by Mike Perry.
11371 - Purge old entries from the "rephist" database and the hidden
11372 service descriptor database even when DirPort is zero.
11373 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
11374 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
11375 crashing or mis-answering these requests.
11376 - When we decide to send a 503 response to a request for servers, do
11377 not then also send the server descriptors: this defeats the whole
11378 purpose. Fixes bug 539.
11381 - Changing the ExitPolicyRejectPrivate setting should cause us to
11382 rebuild our server descriptor.
11383 - Fix handling of hex nicknames when answering controller requests for
11384 networkstatus by name, or when deciding whether to warn about
11385 unknown routers in a config option. (Patch from mwenge.)
11386 - Fix a couple of hard-to-trigger autoconf problems that could result
11387 in really weird results on platforms whose sys/types.h files define
11388 nonstandard integer types.
11389 - Don't try to create the datadir when running --verify-config or
11390 --hash-password. Resolves bug 540.
11391 - If we were having problems getting a particular descriptor from the
11392 directory caches, and then we learned about a new descriptor for
11393 that router, we weren't resetting our failure count. Reported
11395 - Although we fixed bug 539 (where servers would send HTTP status 503
11396 responses _and_ send a body too), there are still servers out there
11397 that haven't upgraded. Therefore, make clients parse such bodies
11398 when they receive them.
11399 - Run correctly on systems where rlim_t is larger than unsigned long.
11400 This includes some 64-bit systems.
11401 - Run correctly on platforms (like some versions of OS X 10.5) where
11402 the real limit for number of open files is OPEN_FILES, not rlim_max
11403 from getrlimit(RLIMIT_NOFILES).
11404 - Avoid a spurious free on base64 failure.
11405 - Avoid segfaults on certain complex invocations of
11406 router_get_by_hexdigest().
11407 - Fix rare bug on REDIRECTSTREAM control command when called with no
11408 port set: it could erroneously report an error when none had
11412 Changes in version 0.1.2.18 - 2007-10-28
11413 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
11414 hidden service introduction that were causing huge delays, and a big
11415 bug that was causing some servers to disappear from the network status
11416 lists for a few hours each day.
11418 o Major bugfixes (crashes):
11419 - If a connection is shut down abruptly because of something that
11420 happened inside connection_flushed_some(), do not call
11421 connection_finished_flushing(). Should fix bug 451:
11422 "connection_stop_writing: Assertion conn->write_event failed"
11423 Bugfix on 0.1.2.7-alpha.
11424 - Fix possible segfaults in functions called from
11425 rend_process_relay_cell().
11427 o Major bugfixes (hidden services):
11428 - Hidden services were choosing introduction points uniquely by
11429 hexdigest, but when constructing the hidden service descriptor
11430 they merely wrote the (potentially ambiguous) nickname.
11431 - Clients now use the v2 intro format for hidden service
11432 connections: they specify their chosen rendezvous point by identity
11433 digest rather than by (potentially ambiguous) nickname. These
11434 changes could speed up hidden service connections dramatically.
11436 o Major bugfixes (other):
11437 - Stop publishing a new server descriptor just because we get a
11438 HUP signal. This led (in a roundabout way) to some servers getting
11439 dropped from the networkstatus lists for a few hours each day.
11440 - When looking for a circuit to cannibalize, consider family as well
11441 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11442 circuit cannibalization).
11443 - When a router wasn't listed in a new networkstatus, we were leaving
11444 the flags for that router alone -- meaning it remained Named,
11445 Running, etc -- even though absence from the networkstatus means
11446 that it shouldn't be considered to exist at all anymore. Now we
11447 clear all the flags for routers that fall out of the networkstatus
11448 consensus. Fixes bug 529.
11451 - Don't try to access (or alter) the state file when running
11452 --list-fingerprint or --verify-config or --hash-password. Resolves
11454 - When generating information telling us how to extend to a given
11455 router, do not try to include the nickname if it is
11456 absent. Resolves bug 467.
11457 - Fix a user-triggerable segfault in expand_filename(). (There isn't
11458 a way to trigger this remotely.)
11459 - When sending a status event to the controller telling it that an
11460 OR address is reachable, set the port correctly. (Previously we
11461 were reporting the dir port.)
11462 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11463 command. Bugfix on 0.1.2.17.
11464 - When loading bandwidth history, do not believe any information in
11465 the future. Fixes bug 434.
11466 - When loading entry guard information, do not believe any information
11468 - When we have our clock set far in the future and generate an
11469 onion key, then re-set our clock to be correct, we should not stop
11470 the onion key from getting rotated.
11471 - On some platforms, accept() can return a broken address. Detect
11472 this more quietly, and deal accordingly. Fixes bug 483.
11473 - It's not actually an error to find a non-pending entry in the DNS
11474 cache when canceling a pending resolve. Don't log unless stuff
11475 is fishy. Resolves bug 463.
11476 - Don't reset trusted dir server list when we set a configuration
11477 option. Patch from Robert Hogan.
11480 Changes in version 0.1.2.17 - 2007-08-30
11481 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
11482 X bundles. Vidalia 0.0.14 makes authentication required for the
11483 ControlPort in the default configuration, which addresses important
11484 security risks. Everybody who uses Vidalia (or another controller)
11487 In addition, this Tor update fixes major load balancing problems with
11488 path selection, which should speed things up a lot once many people
11491 o Major bugfixes (security):
11492 - We removed support for the old (v0) control protocol. It has been
11493 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
11494 become more of a headache than it's worth.
11496 o Major bugfixes (load balancing):
11497 - When choosing nodes for non-guard positions, weight guards
11498 proportionally less, since they already have enough load. Patch
11500 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11501 will allow fast Tor servers to get more attention.
11502 - When we're upgrading from an old Tor version, forget our current
11503 guards and pick new ones according to the new weightings. These
11504 three load balancing patches could raise effective network capacity
11505 by a factor of four. Thanks to Mike Perry for measurements.
11507 o Major bugfixes (stream expiration):
11508 - Expire not-yet-successful application streams in all cases if
11509 they've been around longer than SocksTimeout. Right now there are
11510 some cases where the stream will live forever, demanding a new
11511 circuit every 15 seconds. Fixes bug 454; reported by lodger.
11513 o Minor features (controller):
11514 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11515 is valid before any authentication has been received. It tells
11516 a controller what kind of authentication is expected, and what
11517 protocol is spoken. Implements proposal 119.
11519 o Minor bugfixes (performance):
11520 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
11521 greatly speeding up loading cached-routers from disk on startup.
11522 - Disable sentinel-based debugging for buffer code: we squashed all
11523 the bugs that this was supposed to detect a long time ago, and now
11524 its only effect is to change our buffer sizes from nice powers of
11525 two (which platform mallocs tend to like) to values slightly over
11526 powers of two (which make some platform mallocs sad).
11528 o Minor bugfixes (misc):
11529 - If exit bandwidth ever exceeds one third of total bandwidth, then
11530 use the correct formula to weight exit nodes when choosing paths.
11531 Based on patch from Mike Perry.
11532 - Choose perfectly fairly among routers when choosing by bandwidth and
11533 weighting by fraction of bandwidth provided by exits. Previously, we
11534 would choose with only approximate fairness, and correct ourselves
11535 if we ran off the end of the list.
11536 - If we require CookieAuthentication but we fail to write the
11537 cookie file, we would warn but not exit, and end up in a state
11538 where no controller could authenticate. Now we exit.
11539 - If we require CookieAuthentication, stop generating a new cookie
11540 every time we change any piece of our config.
11541 - Refuse to start with certain directory authority keys, and
11542 encourage people using them to stop.
11543 - Terminate multi-line control events properly. Original patch
11545 - Fix a minor memory leak when we fail to find enough suitable
11546 servers to choose a circuit.
11547 - Stop leaking part of the descriptor when we run into a particularly
11548 unparseable piece of it.
11551 Changes in version 0.1.2.16 - 2007-08-01
11552 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
11553 remote attacker in certain situations to rewrite the user's torrc
11554 configuration file. This can completely compromise anonymity of users
11555 in most configurations, including those running the Vidalia bundles,
11556 TorK, etc. Or worse.
11558 o Major security fixes:
11559 - Close immediately after missing authentication on control port;
11560 do not allow multiple authentication attempts.
11563 Changes in version 0.1.2.15 - 2007-07-17
11564 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
11565 problems, fixes compilation on BSD, and fixes a variety of other
11566 bugs. Everybody should upgrade.
11568 o Major bugfixes (compilation):
11569 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
11571 o Major bugfixes (crashes):
11572 - Try even harder not to dereference the first character after
11573 an mmap(). Reported by lodger.
11574 - Fix a crash bug in directory authorities when we re-number the
11575 routerlist while inserting a new router.
11576 - When the cached-routers file is an even multiple of the page size,
11577 don't run off the end and crash. (Fixes bug 455; based on idea
11579 - Fix eventdns.c behavior on Solaris: It is critical to include
11580 orconfig.h _before_ sys/types.h, so that we can get the expected
11581 definition of _FILE_OFFSET_BITS.
11583 o Major bugfixes (security):
11584 - Fix a possible buffer overrun when using BSD natd support. Bug
11586 - When sending destroy cells from a circuit's origin, don't include
11587 the reason for tearing down the circuit. The spec says we didn't,
11588 and now we actually don't. Reported by lodger.
11589 - Keep streamids from different exits on a circuit separate. This
11590 bug may have allowed other routers on a given circuit to inject
11591 cells into streams. Reported by lodger; fixes bug 446.
11592 - If there's a never-before-connected-to guard node in our list,
11593 never choose any guards past it. This way we don't expand our
11594 guard list unless we need to.
11596 o Minor bugfixes (guard nodes):
11597 - Weight guard selection by bandwidth, so that low-bandwidth nodes
11598 don't get overused as guards.
11600 o Minor bugfixes (directory):
11601 - Correctly count the number of authorities that recommend each
11602 version. Previously, we were under-counting by 1.
11603 - Fix a potential crash bug when we load many server descriptors at
11604 once and some of them make others of them obsolete. Fixes bug 458.
11606 o Minor bugfixes (hidden services):
11607 - Stop tearing down the whole circuit when the user asks for a
11608 connection to a port that the hidden service didn't configure.
11611 o Minor bugfixes (misc):
11612 - On Windows, we were preventing other processes from reading
11613 cached-routers while Tor was running. Reported by janbar.
11614 - Fix a possible (but very unlikely) bug in picking routers by
11615 bandwidth. Add a log message to confirm that it is in fact
11616 unlikely. Patch from lodger.
11617 - Backport a couple of memory leak fixes.
11618 - Backport miscellaneous cosmetic bugfixes.
11621 Changes in version 0.1.2.14 - 2007-05-25
11622 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11623 change especially affects those who serve or use hidden services),
11624 and fixes several other crash- and security-related bugs.
11626 o Directory authority changes:
11627 - Two directory authorities (moria1 and moria2) just moved to new
11628 IP addresses. This change will particularly affect those who serve
11629 or use hidden services.
11631 o Major bugfixes (crashes):
11632 - If a directory server runs out of space in the connection table
11633 as it's processing a begin_dir request, it will free the exit stream
11634 but leave it attached to the circuit, leading to unpredictable
11635 behavior. (Reported by seeess, fixes bug 425.)
11636 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11637 to corrupt memory under some really unlikely scenarios.
11638 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11639 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11642 o Major bugfixes (security):
11643 - When choosing an entry guard for a circuit, avoid using guards
11644 that are in the same family as the chosen exit -- not just guards
11645 that are exactly the chosen exit. (Reported by lodger.)
11647 o Major bugfixes (resource management):
11648 - If a directory authority is down, skip it when deciding where to get
11649 networkstatus objects or descriptors. Otherwise we keep asking
11650 every 10 seconds forever. Fixes bug 384.
11651 - Count it as a failure if we fetch a valid network-status but we
11652 don't want to keep it. Otherwise we'll keep fetching it and keep
11653 not wanting to keep it. Fixes part of bug 422.
11654 - If all of our dirservers have given us bad or no networkstatuses
11655 lately, then stop hammering them once per minute even when we
11656 think they're failed. Fixes another part of bug 422.
11659 - Actually set the purpose correctly for descriptors inserted with
11660 purpose=controller.
11661 - When we have k non-v2 authorities in our DirServer config,
11662 we ignored the last k authorities in the list when updating our
11664 - Correctly back-off from requesting router descriptors that we are
11665 having a hard time downloading.
11666 - Read resolv.conf files correctly on platforms where read() returns
11667 partial results on small file reads.
11668 - Don't rebuild the entire router store every time we get 32K of
11669 routers: rebuild it when the journal gets very large, or when
11670 the gaps in the store get very large.
11673 - When routers publish SVN revisions in their router descriptors,
11674 authorities now include those versions correctly in networkstatus
11676 - Warn when using a version of libevent before 1.3b to run a server on
11677 OSX or BSD: these versions interact badly with userspace threads.
11680 Changes in version 0.1.2.13 - 2007-04-24
11681 This release features some major anonymity fixes, such as safer path
11682 selection; better client performance; faster bootstrapping, better
11683 address detection, and better DNS support for servers; write limiting as
11684 well as read limiting to make servers easier to run; and a huge pile of
11685 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11687 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11688 of the Freenode IRC network, remembering his patience and vision for
11689 free speech on the Internet.
11691 o Major features, client performance:
11692 - Weight directory requests by advertised bandwidth. Now we can
11693 let servers enable write limiting but still allow most clients to
11694 succeed at their directory requests. (We still ignore weights when
11695 choosing a directory authority; I hope this is a feature.)
11696 - Stop overloading exit nodes -- avoid choosing them for entry or
11697 middle hops when the total bandwidth available from non-exit nodes
11698 is much higher than the total bandwidth available from exit nodes.
11699 - Rather than waiting a fixed amount of time between retrying
11700 application connections, we wait only 10 seconds for the first,
11701 10 seconds for the second, and 15 seconds for each retry after
11702 that. Hopefully this will improve the expected user experience.
11703 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
11704 to open a stream fails; now we do in more cases. This should
11705 make clients able to find a good exit faster in some cases, since
11706 unhandleable requests will now get an error rather than timing out.
11708 o Major features, client functionality:
11709 - Implement BEGIN_DIR cells, so we can connect to a directory
11710 server via TLS to do encrypted directory requests rather than
11711 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11712 config options if you like. For now, this feature only works if
11713 you already have a descriptor for the destination dirserver.
11714 - Add support for transparent application connections: this basically
11715 bundles the functionality of trans-proxy-tor into the Tor
11716 mainline. Now hosts with compliant pf/netfilter implementations
11717 can redirect TCP connections straight to Tor without diverting
11718 through SOCKS. (Based on patch from tup.)
11719 - Add support for using natd; this allows FreeBSDs earlier than
11720 5.1.2 to have ipfw send connections through Tor without using
11721 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11723 o Major features, servers:
11724 - Setting up a dyndns name for your server is now optional: servers
11725 with no hostname or IP address will learn their IP address by
11726 asking the directory authorities. This code only kicks in when you
11727 would normally have exited with a "no address" error. Nothing's
11728 authenticated, so use with care.
11729 - Directory servers now spool server descriptors, v1 directories,
11730 and v2 networkstatus objects to buffers as needed rather than en
11731 masse. They also mmap the cached-routers files. These steps save
11733 - Stop requiring clients to have well-formed certificates, and stop
11734 checking nicknames in certificates. (Clients have certificates so
11735 that they can look like Tor servers, but in the future we might want
11736 to allow them to look like regular TLS clients instead. Nicknames
11737 in certificates serve no purpose other than making our protocol
11738 easier to recognize on the wire.) Implements proposal 106.
11740 o Improvements on DNS support:
11741 - Add "eventdns" asynchronous dns library originally based on code
11742 from Adam Langley. Now we can discard the old rickety dnsworker
11743 concept, and support a wider variety of DNS functions. Allows
11744 multithreaded builds on NetBSD and OpenBSD again.
11745 - Add server-side support for "reverse" DNS lookups (using PTR
11746 records so clients can determine the canonical hostname for a given
11747 IPv4 address). Only supported by servers using eventdns; servers
11748 now announce in their descriptors if they don't support eventdns.
11749 - Workaround for name servers (like Earthlink's) that hijack failing
11750 DNS requests and replace the no-such-server answer with a "helpful"
11751 redirect to an advertising-driven search portal. Also work around
11752 DNS hijackers who "helpfully" decline to hijack known-invalid
11753 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
11754 lets you turn it off.
11755 - Servers now check for the case when common DNS requests are going to
11756 wildcarded addresses (i.e. all getting the same answer), and change
11757 their exit policy to reject *:* if it's happening.
11758 - When asked to resolve a hostname, don't use non-exit servers unless
11759 requested to do so. This allows servers with broken DNS to be
11760 useful to the network.
11761 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
11762 useless IPv6 DNS resolves.
11763 - Specify and implement client-side SOCKS5 interface for reverse DNS
11764 lookups (see doc/socks-extensions.txt). Also cache them.
11765 - When we change nameservers or IP addresses, reset and re-launch
11766 our tests for DNS hijacking.
11768 o Improvements on reachability testing:
11769 - Servers send out a burst of long-range padding cells once they've
11770 established that they're reachable. Spread them over 4 circuits,
11771 so hopefully a few will be fast. This exercises bandwidth and
11772 bootstraps them into the directory more quickly.
11773 - When we find our DirPort to be reachable, publish a new descriptor
11774 so we'll tell the world (reported by pnx).
11775 - Directory authorities now only decide that routers are reachable
11776 if their identity keys are as expected.
11777 - Do DirPort reachability tests less often, since a single test
11778 chews through many circuits before giving up.
11779 - Avoid some false positives during reachability testing: don't try
11780 to test via a server that's on the same /24 network as us.
11781 - Start publishing one minute or so after we find our ORPort
11782 to be reachable. This will help reduce the number of descriptors
11783 we have for ourselves floating around, since it's quite likely
11784 other things (e.g. DirPort) will change during that minute too.
11785 - Routers no longer try to rebuild long-term connections to directory
11786 authorities, and directory authorities no longer try to rebuild
11787 long-term connections to all servers. We still don't hang up
11788 connections in these two cases though -- we need to look at it
11789 more carefully to avoid flapping, and we likely need to wait til
11790 0.1.1.x is obsolete.
11792 o Improvements on rate limiting:
11793 - Enable write limiting as well as read limiting. Now we sacrifice
11794 capacity if we're pushing out lots of directory traffic, rather
11795 than overrunning the user's intended bandwidth limits.
11796 - Include TLS overhead when counting bandwidth usage; previously, we
11797 would count only the bytes sent over TLS, but not the bytes used
11799 - Servers decline directory requests much more aggressively when
11800 they're low on bandwidth. Otherwise they end up queueing more and
11801 more directory responses, which can't be good for latency.
11802 - But never refuse directory requests from local addresses.
11803 - Be willing to read or write on local connections (e.g. controller
11804 connections) even when the global rate limiting buckets are empty.
11805 - Flush local controller connection buffers periodically as we're
11806 writing to them, so we avoid queueing 4+ megabytes of data before
11808 - Revise and clean up the torrc.sample that we ship with; add
11809 a section for BandwidthRate and BandwidthBurst.
11811 o Major features, NT services:
11812 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11813 command-line flag so that admins can override the default by saying
11814 "tor --service install --user "SomeUser"". This will not affect
11815 existing installed services. Also, warn the user that the service
11816 will look for its configuration file in the service user's
11817 %appdata% directory. (We can't do the "hardwire the user's appdata
11818 directory" trick any more, since we may not have read access to that
11820 - Support running the Tor service with a torrc not in the same
11821 directory as tor.exe and default to using the torrc located in
11822 the %appdata%\Tor\ of the user who installed the service. Patch
11824 - Add an --ignore-missing-torrc command-line option so that we can
11825 get the "use sensible defaults if the configuration file doesn't
11826 exist" behavior even when specifying a torrc location on the
11828 - When stopping an NT service, wait up to 10 sec for it to actually
11829 stop. (Patch from Matt Edman; resolves bug 295.)
11831 o Directory authority improvements:
11832 - Stop letting hibernating or obsolete servers affect uptime and
11834 - Stop listing hibernating servers in the v1 directory.
11835 - Authorities no longer recommend exits as guards if this would shift
11836 too much load to the exit nodes.
11837 - Authorities now specify server versions in networkstatus. This adds
11838 about 2% to the size of compressed networkstatus docs, and allows
11839 clients to tell which servers support BEGIN_DIR and which don't.
11840 The implementation is forward-compatible with a proposed future
11841 protocol version scheme not tied to Tor versions.
11842 - DirServer configuration lines now have an orport= option so
11843 clients can open encrypted tunnels to the authorities without
11844 having downloaded their descriptors yet. Enabled for moria1,
11845 moria2, tor26, and lefkada now in the default configuration.
11846 - Add a BadDirectory flag to network status docs so that authorities
11847 can (eventually) tell clients about caches they believe to be
11848 broken. Not used yet.
11849 - Allow authorities to list nodes as bad exits in their
11850 approved-routers file by fingerprint or by address. If most
11851 authorities set a BadExit flag for a server, clients don't think
11852 of it as a general-purpose exit. Clients only consider authorities
11853 that advertise themselves as listing bad exits.
11854 - Patch from Steve Hildrey: Generate network status correctly on
11855 non-versioning dirservers.
11856 - Have directory authorities allow larger amounts of drift in uptime
11857 without replacing the server descriptor: previously, a server that
11858 restarted every 30 minutes could have 48 "interesting" descriptors
11860 - Reserve the nickname "Unnamed" for routers that can't pick
11861 a hostname: any router can call itself Unnamed; directory
11862 authorities will never allocate Unnamed to any particular router;
11863 clients won't believe that any router is the canonical Unnamed.
11865 o Directory mirrors and clients:
11866 - Discard any v1 directory info that's over 1 month old (for
11867 directories) or over 1 week old (for running-routers lists).
11868 - Clients track responses with status 503 from dirservers. After a
11869 dirserver has given us a 503, we try not to use it until an hour has
11870 gone by, or until we have no dirservers that haven't given us a 503.
11871 - When we get a 503 from a directory, and we're not a server, we no
11872 longer count the failure against the total number of failures
11873 allowed for the object we're trying to download.
11874 - Prepare for servers to publish descriptors less often: never
11875 discard a descriptor simply for being too old until either it is
11876 recommended by no authorities, or until we get a better one for
11877 the same router. Make caches consider retaining old recommended
11878 routers for even longer.
11879 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
11880 headers for content, so that we can work better in the presence of
11881 caching HTTP proxies.
11882 - Stop fetching descriptors if you're not a dir mirror and you
11883 haven't tried to establish any circuits lately. (This currently
11884 causes some dangerous behavior, because when you start up again
11885 you'll use your ancient server descriptors.)
11887 o Major fixes, crashes:
11888 - Stop crashing when the controller asks us to resetconf more than
11889 one config option at once. (Vidalia 0.0.11 does this.)
11890 - Fix a longstanding obscure crash bug that could occur when we run
11891 out of DNS worker processes, if we're not using eventdns. (Resolves
11893 - Fix an assert that could trigger if a controller quickly set then
11894 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
11895 - Avoid crash when telling controller about stream-status and a
11896 stream is detached.
11897 - Avoid sending junk to controllers or segfaulting when a controller
11898 uses EVENT_NEW_DESC with verbose nicknames.
11899 - Stop triggering asserts if the controller tries to extend hidden
11900 service circuits (reported by mwenge).
11901 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11902 and hup, stop triggering an assert based on an empty onion_key.
11903 - Mask out all signals in sub-threads; only the libevent signal
11904 handler should be processing them. This should prevent some crashes
11905 on some machines using pthreads. (Patch from coderman.)
11906 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11908 o Major fixes, anonymity/security:
11909 - Automatically avoid picking more than one node from the same
11910 /16 network when constructing a circuit. Add an
11911 "EnforceDistinctSubnets" option to let people disable it if they
11912 want to operate private test networks on a single subnet.
11913 - When generating bandwidth history, round down to the nearest
11914 1k. When storing accounting data, round up to the nearest 1k.
11915 - When we're running as a server, remember when we last rotated onion
11916 keys, so that we will rotate keys once they're a week old even if
11917 we never stay up for a week ourselves.
11918 - If a client asked for a server by name, and there's a named server
11919 in our network-status but we don't have its descriptor yet, we
11920 could return an unnamed server instead.
11921 - Reject (most) attempts to use Tor circuits with length one. (If
11922 many people start using Tor as a one-hop proxy, exit nodes become
11923 a more attractive target for compromise.)
11924 - Just because your DirPort is open doesn't mean people should be
11925 able to remotely teach you about hidden service descriptors. Now
11926 only accept rendezvous posts if you've got HSAuthoritativeDir set.
11927 - Fix a potential race condition in the rpm installer. Found by
11929 - Do not log IPs with TLS failures for incoming TLS
11930 connections. (Fixes bug 382.)
11932 o Major fixes, other:
11933 - If our system clock jumps back in time, don't publish a negative
11934 uptime in the descriptor.
11935 - When we start during an accounting interval before it's time to wake
11936 up, remember to wake up at the correct time. (May fix bug 342.)
11937 - Previously, we would cache up to 16 old networkstatus documents
11938 indefinitely, if they came from nontrusted authorities. Now we
11939 discard them if they are more than 10 days old.
11940 - When we have a state file we cannot parse, tell the user and
11941 move it aside. Now we avoid situations where the user starts
11942 Tor in 1904, Tor writes a state file with that timestamp in it,
11943 the user fixes her clock, and Tor refuses to start.
11944 - Publish a new descriptor after we hup/reload. This is important
11945 if our config has changed such that we'll want to start advertising
11946 our DirPort now, etc.
11947 - If we are using an exit enclave and we can't connect, e.g. because
11948 its webserver is misconfigured to not listen on localhost, then
11949 back off and try connecting from somewhere else before we fail.
11951 o New config options or behaviors:
11952 - When EntryNodes are configured, rebuild the guard list to contain,
11953 in order: the EntryNodes that were guards before; the rest of the
11954 EntryNodes; the nodes that were guards before.
11955 - Do not warn when individual nodes in the configuration's EntryNodes,
11956 ExitNodes, etc are down: warn only when all possible nodes
11957 are down. (Fixes bug 348.)
11958 - Put a lower-bound on MaxAdvertisedBandwidth.
11959 - Start using the state file to store bandwidth accounting data:
11960 the bw_accounting file is now obsolete. We'll keep generating it
11961 for a while for people who are still using 0.1.2.4-alpha.
11962 - Try to batch changes to the state file so that we do as few
11963 disk writes as possible while still storing important things in
11965 - The state file and the bw_accounting file get saved less often when
11966 the AvoidDiskWrites config option is set.
11967 - Make PIDFile work on Windows.
11968 - Add internal descriptions for a bunch of configuration options:
11969 accessible via controller interface and in comments in saved
11971 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11972 NNTP by default, so this seems like a sensible addition.
11973 - Clients now reject hostnames with invalid characters. This should
11974 avoid some inadvertent info leaks. Add an option
11975 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11976 is running a private network with hosts called @, !, and #.
11977 - Check for addresses with invalid characters at the exit as well,
11978 and warn less verbosely when they fail. You can override this by
11979 setting ServerDNSAllowNonRFC953Addresses to 1.
11980 - Remove some options that have been deprecated since at least
11981 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11982 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11983 to set log options. Mark PathlenCoinWeight as obsolete.
11984 - Stop accepting certain malformed ports in configured exit policies.
11985 - When the user uses bad syntax in the Log config line, stop
11986 suggesting other bad syntax as a replacement.
11987 - Add new config option "ResolvConf" to let the server operator
11988 choose an alternate resolve.conf file when using eventdns.
11989 - If one of our entry guards is on the ExcludeNodes list, or the
11990 directory authorities don't think it's a good guard, treat it as
11991 if it were unlisted: stop using it as a guard, and throw it off
11992 the guards list if it stays that way for a long time.
11993 - Allow directory authorities to be marked separately as authorities
11994 for the v1 directory protocol, the v2 directory protocol, and
11995 as hidden service directories, to make it easier to retire old
11996 authorities. V1 authorities should set "HSAuthoritativeDir 1"
11997 to continue being hidden service authorities too.
11998 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
11999 - Make TrackExitHosts case-insensitive, and fix the behavior of
12000 ".suffix" TrackExitHosts items to avoid matching in the middle of
12002 - New DirPort behavior: if you have your dirport set, you download
12003 descriptors aggressively like a directory mirror, whether or not
12004 your ORPort is set.
12007 - Create a new file ReleaseNotes which was the old ChangeLog. The
12008 new ChangeLog file now includes the notes for all development
12010 - Add a new address-spec.txt document to describe our special-case
12011 addresses: .exit, .onion, and .noconnnect.
12012 - Fork the v1 directory protocol into its own spec document,
12013 and mark dir-spec.txt as the currently correct (v2) spec.
12015 o Packaging, porting, and contrib
12016 - "tor --verify-config" now exits with -1(255) or 0 depending on
12017 whether the config options are bad or good.
12018 - The Debian package now uses --verify-config when (re)starting,
12019 to distinguish configuration errors from other errors.
12020 - Adapt a patch from goodell to let the contrib/exitlist script
12021 take arguments rather than require direct editing.
12022 - Prevent the contrib/exitlist script from printing the same
12023 result more than once.
12024 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
12025 - In the hidden service example in torrc.sample, stop recommending
12026 esoteric and discouraged hidden service options.
12027 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
12028 values before failing, and always enables eventdns.
12029 - Try to detect Windows correctly when cross-compiling.
12030 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
12031 Try to fix this in configure.in by checking for most functions
12032 before we check for libevent.
12033 - Update RPMs to require libevent 1.2.
12034 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12035 or later. Log when we are doing this, so we can diagnose it when
12036 it fails. (Also, recommend libevent 1.1b for kqueue and
12037 win32 methods; deprecate libevent 1.0b harder; make libevent
12038 recommendation system saner.)
12039 - Build with recent (1.3+) libevents on platforms that do not
12040 define the nonstandard types "u_int8_t" and friends.
12041 - Remove architecture from OS X builds. The official builds are
12042 now universal binaries.
12043 - Run correctly on OS X platforms with case-sensitive filesystems.
12044 - Correctly set maximum connection limit on Cygwin. (This time
12046 - Start compiling on MinGW on Windows (patches from Mike Chiussi
12048 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12049 - Finally fix the openssl warnings from newer gccs that believe that
12050 ignoring a return value is okay, but casting a return value and
12051 then ignoring it is a sign of madness.
12052 - On architectures where sizeof(int)>4, still clamp declarable
12053 bandwidth to INT32_MAX.
12055 o Minor features, controller:
12056 - Warn the user when an application uses the obsolete binary v0
12057 control protocol. We're planning to remove support for it during
12058 the next development series, so it's good to give people some
12060 - Add STREAM_BW events to report per-entry-stream bandwidth
12061 use. (Patch from Robert Hogan.)
12062 - Rate-limit SIGNEWNYM signals in response to controllers that
12063 impolitely generate them for every single stream. (Patch from
12064 mwenge; closes bug 394.)
12065 - Add a REMAP status to stream events to note that a stream's
12066 address has changed because of a cached address or a MapAddress
12068 - Make REMAP stream events have a SOURCE (cache or exit), and
12069 make them generated in every case where we get a successful
12070 connected or resolved cell.
12071 - Track reasons for OR connection failure; make these reasons
12072 available via the controller interface. (Patch from Mike Perry.)
12073 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
12074 can learn when clients are sending malformed hostnames to Tor.
12075 - Specify and implement some of the controller status events.
12076 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
12077 - Reimplement GETINFO so that info/names stays in sync with the
12079 - Implement "GETINFO fingerprint".
12080 - Implement "SETEVENTS GUARD" so controllers can get updates on
12081 entry guard status as it changes.
12082 - Make all connections to addresses of the form ".noconnect"
12083 immediately get closed. This lets application/controller combos
12084 successfully test whether they're talking to the same Tor by
12085 watching for STREAM events.
12086 - Add a REASON field to CIRC events; for backward compatibility, this
12087 field is sent only to controllers that have enabled the extended
12088 event format. Also, add additional reason codes to explain why
12089 a given circuit has been destroyed or truncated. (Patches from
12091 - Add a REMOTE_REASON field to extended CIRC events to tell the
12092 controller why a remote OR told us to close a circuit.
12093 - Stream events also now have REASON and REMOTE_REASON fields,
12094 working much like those for circuit events.
12095 - There's now a GETINFO ns/... field so that controllers can ask Tor
12096 about the current status of a router.
12097 - A new event type "NS" to inform a controller when our opinion of
12098 a router's status has changed.
12099 - Add a GETINFO events/names and GETINFO features/names so controllers
12100 can tell which events and features are supported.
12101 - A new CLEARDNSCACHE signal to allow controllers to clear the
12102 client-side DNS cache without expiring circuits.
12103 - Fix CIRC controller events so that controllers can learn the
12104 identity digests of non-Named servers used in circuit paths.
12105 - Let controllers ask for more useful identifiers for servers. Instead
12106 of learning identity digests for un-Named servers and nicknames
12107 for Named servers, the new identifiers include digest, nickname,
12108 and indication of Named status. Off by default; see control-spec.txt
12109 for more information.
12110 - Add a "getinfo address" controller command so it can display Tor's
12111 best guess to the user.
12112 - New controller event to alert the controller when our server
12113 descriptor has changed.
12114 - Give more meaningful errors on controller authentication failure.
12115 - Export the default exit policy via the control port, so controllers
12116 don't need to guess what it is / will be later.
12118 o Minor bugfixes, controller:
12119 - When creating a circuit via the controller, send a 'launched'
12120 event when we're done, so we follow the spec better.
12121 - Correct the control spec to match how the code actually responds
12122 to 'getinfo addr-mappings/*'. Reported by daejees.
12123 - The control spec described a GUARDS event, but the code
12124 implemented a GUARD event. Standardize on GUARD, but let people
12125 ask for GUARDS too. Reported by daejees.
12126 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
12127 clear the corresponding on_circuit variable, and remember later
12128 that we don't need to send a redundant CLOSED event. (Resolves part
12130 - Report events where a resolve succeeded or where we got a socks
12131 protocol error correctly, rather than calling both of them
12133 - Change reported stream target addresses to IP consistently when
12134 we finally get the IP from an exit node.
12135 - Send log messages to the controller even if they happen to be very
12137 - Flush ERR-level controller status events just like we currently
12138 flush ERR-level log events, so that a Tor shutdown doesn't prevent
12139 the controller from learning about current events.
12140 - Report the circuit number correctly in STREAM CLOSED events. Bug
12141 reported by Mike Perry.
12142 - Do not report bizarre values for results of accounting GETINFOs
12143 when the last second's write or read exceeds the allotted bandwidth.
12144 - Report "unrecognized key" rather than an empty string when the
12145 controller tries to fetch a networkstatus that doesn't exist.
12146 - When the controller does a "GETINFO network-status", tell it
12147 about even those routers whose descriptors are very old, and use
12148 long nicknames where appropriate.
12149 - Fix handling of verbose nicknames with ORCONN controller events:
12150 make them show up exactly when requested, rather than exactly when
12152 - Controller signals now work on non-Unix platforms that don't define
12153 SIGUSR1 and SIGUSR2 the way we expect.
12154 - Respond to SIGNAL command before we execute the signal, in case
12155 the signal shuts us down. Suggested by Karsten Loesing.
12156 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12158 o Minor features, code performance:
12159 - Major performance improvement on inserting descriptors: change
12160 algorithm from O(n^2) to O(n).
12161 - Do not rotate onion key immediately after setting it for the first
12163 - Call router_have_min_dir_info half as often. (This is showing up in
12164 some profiles, but not others.)
12165 - When using GCC, make log_debug never get called at all, and its
12166 arguments never get evaluated, when no debug logs are configured.
12167 (This is showing up in some profiles, but not others.)
12168 - Statistics dumped by -USR2 now include a breakdown of public key
12169 operations, for profiling.
12170 - Make the common memory allocation path faster on machines where
12171 malloc(0) returns a pointer.
12172 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12173 split connection_t into edge, or, dir, control, and base structs.
12174 These will save quite a bit of memory on busy servers, and they'll
12175 also help us track down bugs in the code and bugs in the spec.
12176 - Use OpenSSL's AES implementation on platforms where it's faster.
12177 This could save us as much as 10% CPU usage.
12179 o Minor features, descriptors and descriptor handling:
12180 - Avoid duplicate entries on MyFamily line in server descriptor.
12181 - When Tor receives a router descriptor that it asked for, but
12182 no longer wants (because it has received fresh networkstatuses
12183 in the meantime), do not warn the user. Cache the descriptor if
12184 we're a cache; drop it if we aren't.
12185 - Servers no longer ever list themselves in their "family" line,
12186 even if configured to do so. This makes it easier to configure
12187 family lists conveniently.
12189 o Minor fixes, confusing/misleading log messages:
12190 - Display correct results when reporting which versions are
12191 recommended, and how recommended they are. (Resolves bug 383.)
12192 - Inform the server operator when we decide not to advertise a
12193 DirPort due to AccountingMax enabled or a low BandwidthRate.
12194 - Only include function names in log messages for info/debug messages.
12195 For notice/warn/err, the content of the message should be clear on
12196 its own, and printing the function name only confuses users.
12197 - Remove even more protocol-related warnings from Tor server logs,
12198 such as bad TLS handshakes and malformed begin cells.
12199 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12200 when the IP address is mapped through MapAddress to a hostname.
12201 - Fix misleading log messages: an entry guard that is "unlisted",
12202 as well as not known to be "down" (because we've never heard
12203 of it), is not therefore "up".
12205 o Minor fixes, old/obsolete behavior:
12206 - Start assuming we can use a create_fast cell if we don't know
12207 what version a router is running.
12208 - We no longer look for identity and onion keys in "identity.key" and
12209 "onion.key" -- these were replaced by secret_id_key and
12210 secret_onion_key in 0.0.8pre1.
12211 - We no longer require unrecognized directory entries to be
12213 - Drop compatibility with obsolete Tors that permit create cells
12214 to have the wrong circ_id_type.
12215 - Remove code to special-case "-cvs" ending, since it has not
12216 actually mattered since 0.0.9.
12217 - Don't re-write the fingerprint file every restart, unless it has
12220 o Minor fixes, misc client-side behavior:
12221 - Always remove expired routers and networkstatus docs before checking
12222 whether we have enough information to build circuits. (Fixes
12224 - When computing clock skew from directory HTTP headers, consider what
12225 time it was when we finished asking for the directory, not what
12227 - Make our socks5 handling more robust to broken socks clients:
12228 throw out everything waiting on the buffer in between socks
12229 handshake phases, since they can't possibly (so the theory
12230 goes) have predicted what we plan to respond to them.
12231 - Expire socks connections if they spend too long waiting for the
12232 handshake to finish. Previously we would let them sit around for
12233 days, if the connecting application didn't close them either.
12234 - And if the socks handshake hasn't started, don't send a
12235 "DNS resolve socks failed" handshake reply; just close it.
12236 - If the user asks to use invalid exit nodes, be willing to use
12238 - Track unreachable entry guards correctly: don't conflate
12239 'unreachable by us right now' with 'listed as down by the directory
12240 authorities'. With the old code, if a guard was unreachable by us
12241 but listed as running, it would clog our guard list forever.
12242 - Behave correctly in case we ever have a network with more than
12243 2GB/s total advertised capacity.
12244 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12245 - Fix a memory leak when we ask for "all" networkstatuses and we
12246 get one we don't recognize.
12249 Changes in version 0.1.1.26 - 2006-12-14
12250 o Security bugfixes:
12251 - Stop sending the HttpProxyAuthenticator string to directory
12252 servers when directory connections are tunnelled through Tor.
12253 - Clients no longer store bandwidth history in the state file.
12254 - Do not log introduction points for hidden services if SafeLogging
12258 - Fix an assert failure when a directory authority sets
12259 AuthDirRejectUnlisted and then receives a descriptor from an
12260 unlisted router (reported by seeess).
12263 Changes in version 0.1.1.25 - 2006-11-04
12265 - When a client asks us to resolve (rather than connect to)
12266 an address, and we have a cached answer, give them the cached
12267 answer. Previously, we would give them no answer at all.
12268 - We were building exactly the wrong circuits when we predict
12269 hidden service requirements, meaning Tor would have to build all
12270 its circuits on demand.
12271 - If none of our live entry guards have a high uptime, but we
12272 require a guard with a high uptime, try adding a new guard before
12273 we give up on the requirement. This patch should make long-lived
12274 connections more stable on average.
12275 - When testing reachability of our DirPort, don't launch new
12276 tests when there's already one in progress -- unreachable
12277 servers were stacking up dozens of testing streams.
12279 o Security bugfixes:
12280 - When the user sends a NEWNYM signal, clear the client-side DNS
12281 cache too. Otherwise we continue to act on previous information.
12284 - Avoid a memory corruption bug when creating a hash table for
12286 - Avoid possibility of controller-triggered crash when misusing
12287 certain commands from a v0 controller on platforms that do not
12288 handle printf("%s",NULL) gracefully.
12289 - Avoid infinite loop on unexpected controller input.
12290 - Don't log spurious warnings when we see a circuit close reason we
12291 don't recognize; it's probably just from a newer version of Tor.
12292 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12293 Tor/Privoxy we also uninstall Vidalia.
12296 Changes in version 0.1.1.24 - 2006-09-29
12298 - Allow really slow clients to not hang up five minutes into their
12299 directory downloads (suggested by Adam J. Richter).
12300 - Fix major performance regression from 0.1.0.x: instead of checking
12301 whether we have enough directory information every time we want to
12302 do something, only check when the directory information has changed.
12303 This should improve client CPU usage by 25-50%.
12304 - Don't crash if, after a server has been running for a while,
12305 it can't resolve its hostname.
12306 - When a client asks us to resolve (not connect to) an address,
12307 and we have a cached answer, give them the cached answer.
12308 Previously, we would give them no answer at all.
12311 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12312 - Don't crash when the controller receives a third argument to an
12313 "extendcircuit" request.
12314 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12315 response; fix error code when "getinfo dir/status/" fails.
12316 - Fix configure.in to not produce broken configure files with
12317 more recent versions of autoconf. Thanks to Clint for his auto*
12319 - Fix security bug on NetBSD that could allow someone to force
12320 uninitialized RAM to be sent to a server's DNS resolver. This
12321 only affects NetBSD and other platforms that do not bounds-check
12323 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12324 methods: these are known to be buggy.
12325 - If we're a directory mirror and we ask for "all" network status
12326 documents, we would discard status documents from authorities
12327 we don't recognize.
12330 Changes in version 0.1.1.23 - 2006-07-30
12332 - Fast Tor servers, especially exit nodes, were triggering asserts
12333 due to a bug in handling the list of pending DNS resolves. Some
12334 bugs still remain here; we're hunting them.
12335 - Entry guards could crash clients by sending unexpected input.
12336 - More fixes on reachability testing: if you find yourself reachable,
12337 then don't ever make any client requests (so you stop predicting
12338 circuits), then hup or have your clock jump, then later your IP
12339 changes, you won't think circuits are working, so you won't try to
12340 test reachability, so you won't publish.
12343 - Avoid a crash if the controller does a resetconf firewallports
12344 and then a setconf fascistfirewall=1.
12345 - Avoid an integer underflow when the dir authority decides whether
12346 a router is stable: we might wrongly label it stable, and compute
12347 a slightly wrong median stability, when a descriptor is published
12349 - Fix a place where we might trigger an assert if we can't build our
12350 own server descriptor yet.
12353 Changes in version 0.1.1.22 - 2006-07-05
12355 - Fix a big bug that was causing servers to not find themselves
12356 reachable if they changed IP addresses. Since only 0.1.1.22+
12357 servers can do reachability testing correctly, now we automatically
12358 make sure to test via one of these.
12359 - Fix to allow clients and mirrors to learn directory info from
12360 descriptor downloads that get cut off partway through.
12361 - Directory authorities had a bug in deciding if a newly published
12362 descriptor was novel enough to make everybody want a copy -- a few
12363 servers seem to be publishing new descriptors many times a minute.
12365 - Fix a rare bug that was causing some servers to complain about
12366 "closing wedged cpuworkers" and skip some circuit create requests.
12367 - Make the Exit flag in directory status documents actually work.
12370 Changes in version 0.1.1.21 - 2006-06-10
12371 o Crash and assert fixes from 0.1.1.20:
12372 - Fix a rare crash on Tor servers that have enabled hibernation.
12373 - Fix a seg fault on startup for Tor networks that use only one
12374 directory authority.
12375 - Fix an assert from a race condition that occurs on Tor servers
12376 while exiting, where various threads are trying to log that they're
12377 exiting, and delete the logs, at the same time.
12378 - Make our unit tests pass again on certain obscure platforms.
12381 - Add support for building SUSE RPM packages.
12382 - Speed up initial bootstrapping for clients: if we are making our
12383 first ever connection to any entry guard, then don't mark it down
12385 - When only one Tor server in the network is labelled as a guard,
12386 and we've already picked him, we would cycle endlessly picking him
12387 again, being unhappy about it, etc. Now we specifically exclude
12388 current guards when picking a new guard.
12389 - Servers send create cells more reliably after the TLS connection
12390 is established: we were sometimes forgetting to send half of them
12391 when we had more than one pending.
12392 - If we get a create cell that asks us to extend somewhere, but the
12393 Tor server there doesn't match the expected digest, we now send
12394 a destroy cell back, rather than silently doing nothing.
12395 - Make options->RedirectExit work again.
12396 - Make cookie authentication for the controller work again.
12397 - Stop being picky about unusual characters in the arguments to
12398 mapaddress. It's none of our business.
12399 - Add a new config option "TestVia" that lets you specify preferred
12400 middle hops to use for test circuits. Perhaps this will let me
12401 debug the reachability problems better.
12403 o Log / documentation fixes:
12404 - If we're a server and some peer has a broken TLS certificate, don't
12405 log about it unless ProtocolWarnings is set, i.e., we want to hear
12406 about protocol violations by others.
12407 - Fix spelling of VirtualAddrNetwork in man page.
12408 - Add a better explanation at the top of the autogenerated torrc file
12409 about what happened to our old torrc.
12412 Changes in version 0.1.1.20 - 2006-05-23
12413 o Crash and assert fixes from 0.1.0.17:
12414 - Fix assert bug in close_logs() on exit: when we close and delete
12415 logs, remove them all from the global "logfiles" list.
12416 - Fix an assert error when we're out of space in the connection_list
12417 and we try to post a hidden service descriptor (reported by Peter
12419 - Fix a rare assert error when we've tried all intro points for
12420 a hidden service and we try fetching the service descriptor again:
12421 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
12422 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
12423 out and refuse the setconf if it would fail.
12424 - If you specify a relative torrc path and you set RunAsDaemon in
12425 your torrc, then it chdir()'s to the new directory. If you then
12426 HUP, it tries to load the new torrc location, fails, and exits.
12427 The fix: no longer allow a relative path to torrc when using -f.
12428 - Check for integer overflows in more places, when adding elements
12429 to smartlists. This could possibly prevent a buffer overflow
12430 on malicious huge inputs.
12432 o Security fixes, major:
12433 - When we're printing strings from the network, don't try to print
12434 non-printable characters. Now we're safer against shell escape
12435 sequence exploits, and also against attacks to fool users into
12436 misreading their logs.
12437 - Implement entry guards: automatically choose a handful of entry
12438 nodes and stick with them for all circuits. Only pick new guards
12439 when the ones you have are unsuitable, and if the old guards
12440 become suitable again, switch back. This will increase security
12441 dramatically against certain end-point attacks. The EntryNodes
12442 config option now provides some hints about which entry guards you
12443 want to use most; and StrictEntryNodes means to only use those.
12444 Fixes CVE-2006-0414.
12445 - Implement exit enclaves: if we know an IP address for the
12446 destination, and there's a running Tor server at that address
12447 which allows exit to the destination, then extend the circuit to
12448 that exit first. This provides end-to-end encryption and end-to-end
12449 authentication. Also, if the user wants a .exit address or enclave,
12450 use 4 hops rather than 3, and cannibalize a general circ for it
12452 - Obey our firewall options more faithfully:
12453 . If we can't get to a dirserver directly, try going via Tor.
12454 . Don't ever try to connect (as a client) to a place our
12455 firewall options forbid.
12456 . If we specify a proxy and also firewall options, obey the
12457 firewall options even when we're using the proxy: some proxies
12458 can only proxy to certain destinations.
12459 - Make clients regenerate their keys when their IP address changes.
12460 - For the OS X package's modified privoxy config file, comment
12461 out the "logfile" line so we don't log everything passed
12463 - Our TLS handshakes were generating a single public/private
12464 keypair for the TLS context, rather than making a new one for
12465 each new connection. Oops. (But we were still rotating them
12466 periodically, so it's not so bad.)
12467 - When we were cannibalizing a circuit with a particular exit
12468 node in mind, we weren't checking to see if that exit node was
12469 already present earlier in the circuit. Now we are.
12470 - Require server descriptors to list IPv4 addresses -- hostnames
12471 are no longer allowed. This also fixes potential vulnerabilities
12472 to servers providing hostnames as their address and then
12473 preferentially resolving them so they can partition users.
12474 - Our logic to decide if the OR we connected to was the right guy
12475 was brittle and maybe open to a mitm for invalid routers.
12477 o Security fixes, minor:
12478 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
12479 Ian Goldberg can prove things about our handshake protocol more
12481 - Make directory authorities generate a separate "guard" flag to
12482 mean "would make a good entry guard". Clients now honor the
12483 is_guard flag rather than looking at is_fast or is_stable.
12484 - Try to list MyFamily elements by key, not by nickname, and warn
12485 if we've not heard of a server.
12486 - Start using RAND_bytes rather than RAND_pseudo_bytes from
12487 OpenSSL. Also, reseed our entropy every hour, not just at
12488 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
12489 - Refuse server descriptors where the fingerprint line doesn't match
12490 the included identity key. Tor doesn't care, but other apps (and
12491 humans) might actually be trusting the fingerprint line.
12492 - We used to kill the circuit when we receive a relay command we
12493 don't recognize. Now we just drop that cell.
12494 - Fix a bug found by Lasse Overlier: when we were making internal
12495 circuits (intended to be cannibalized later for rendezvous and
12496 introduction circuits), we were picking them so that they had
12497 useful exit nodes. There was no need for this, and it actually
12498 aids some statistical attacks.
12499 - Start treating internal circuits and exit circuits separately.
12500 It's important to keep them separate because internal circuits
12501 have their last hops picked like middle hops, rather than like
12502 exit hops. So exiting on them will break the user's expectations.
12503 - Fix a possible way to DoS dirservers.
12504 - When the client asked for a rendezvous port that the hidden
12505 service didn't want to provide, we were sending an IP address
12506 back along with the end cell. Fortunately, it was zero. But stop
12509 o Packaging improvements:
12510 - Implement --with-libevent-dir option to ./configure. Improve
12511 search techniques to find libevent, and use those for openssl too.
12512 - Fix a couple of bugs in OpenSSL detection. Deal better when
12513 there are multiple SSLs installed with different versions.
12514 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12515 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
12517 - Make unit tests (and other invocations that aren't the real Tor)
12518 run without launching listeners, creating subdirectories, and so on.
12519 - The OS X installer was adding a symlink for tor_resolve but
12520 the binary was called tor-resolve (reported by Thomas Hardly).
12521 - Now we can target arch and OS in rpm builds (contributed by
12522 Phobos). Also make the resulting dist-rpm filename match the
12524 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12525 if you log to syslog and want something other than LOG_DAEMON.
12526 - Fix the torify (tsocks) config file to not use Tor for localhost
12528 - Start shipping socks-extensions.txt, tor-doc-unix.html,
12529 tor-doc-server.html, and stylesheet.css in the tarball.
12530 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
12531 They are useless now.
12532 - Add Peter Palfrader's contributed check-tor script. It lets you
12533 easily check whether a given server (referenced by nickname)
12534 is reachable by you.
12535 - Add BSD-style contributed startup script "rc.subr" from Peter
12538 o Directory improvements -- new directory protocol:
12539 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
12540 - Authorities and caches publish individual descriptors (by
12541 digest, by fingerprint, by "all", and by "tell me yours").
12542 - Clients don't download or use the old directory anymore. Now they
12543 download network-statuses from the directory authorities, and
12544 fetch individual server descriptors as needed from mirrors.
12545 - Clients don't download descriptors of non-running servers.
12546 - Download descriptors by digest, not by fingerprint. Caches try to
12547 download all listed digests from authorities; clients try to
12548 download "best" digests from caches. This avoids partitioning
12549 and isolating attacks better.
12550 - Only upload a new server descriptor when options change, 18
12551 hours have passed, uptime is reset, or bandwidth changes a lot.
12552 - Directory authorities silently throw away new descriptors that
12553 haven't changed much if the timestamps are similar. We do this to
12554 tolerate older Tor servers that upload a new descriptor every 15
12555 minutes. (It seemed like a good idea at the time.)
12556 - Clients choose directory servers from the network status lists,
12557 not from their internal list of router descriptors. Now they can
12558 go to caches directly rather than needing to go to authorities
12559 to bootstrap the first set of descriptors.
12560 - When picking a random directory, prefer non-authorities if any
12562 - Add a new flag to network-status indicating whether the server
12563 can answer v2 directory requests too.
12564 - Directory mirrors now cache up to 16 unrecognized network-status
12565 docs, so new directory authorities will be cached too.
12566 - Stop parsing, storing, or using running-routers output (but
12567 mirrors still cache and serve it).
12568 - Clients consider a threshold of "versioning" directory authorities
12569 before deciding whether to warn the user that he's obsolete.
12570 - Authorities publish separate sorted lists of recommended versions
12571 for clients and for servers.
12572 - Change DirServers config line to note which dirs are v1 authorities.
12573 - Put nicknames on the DirServer line, so we can refer to them
12574 without requiring all our users to memorize their IP addresses.
12575 - Remove option when getting directory cache to see whether they
12576 support running-routers; they all do now. Replace it with one
12577 to see whether caches support v2 stuff.
12578 - Stop listing down or invalid nodes in the v1 directory. This
12579 reduces its bulk by about 1/3, and reduces load on mirrors.
12580 - Mirrors no longer cache the v1 directory as often.
12581 - If we as a directory mirror don't know of any v1 directory
12582 authorities, then don't try to cache any v1 directories.
12584 o Other directory improvements:
12585 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
12586 fifth authoritative directory servers.
12587 - Directory authorities no longer require an open connection from
12588 a server to consider him "reachable". We need this change because
12589 when we add new directory authorities, old servers won't know not
12590 to hang up on them.
12591 - Dir authorities now do their own external reachability testing
12592 of each server, and only list as running the ones they found to
12593 be reachable. We also send back warnings to the server's logs if
12594 it uploads a descriptor that we already believe is unreachable.
12595 - Spread the directory authorities' reachability testing over the
12596 entire testing interval, so we don't try to do 500 TLS's at once
12598 - Make the "stable" router flag in network-status be the median of
12599 the uptimes of running valid servers, and make clients pay
12600 attention to the network-status flags. Thus the cutoff adapts
12601 to the stability of the network as a whole, making IRC, IM, etc
12602 connections more reliable.
12603 - Make the v2 dir's "Fast" flag based on relative capacity, just
12604 like "Stable" is based on median uptime. Name everything in the
12605 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12606 - Retry directory requests if we fail to get an answer we like
12607 from a given dirserver (we were retrying before, but only if
12608 we fail to connect).
12609 - Return a robots.txt on our dirport to discourage google indexing.
12611 o Controller protocol improvements:
12612 - Revised controller protocol (version 1) that uses ascii rather
12613 than binary: tor/doc/control-spec.txt. Add supporting libraries
12614 in python and java and c# so you can use the controller from your
12615 applications without caring how our protocol works.
12616 - Allow the DEBUG controller event to work again. Mark certain log
12617 entries as "don't tell this to controllers", so we avoid cycles.
12618 - New controller function "getinfo accounting", to ask how
12619 many bytes we've used in this time period.
12620 - Add a "resetconf" command so you can set config options like
12621 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
12622 a config option in the torrc with no value, then it clears it
12623 entirely (rather than setting it to its default).
12624 - Add a "getinfo config-file" to tell us where torrc is. Also
12625 expose guard nodes, config options/names.
12626 - Add a "quit" command (when when using the controller manually).
12627 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
12628 stop using any currently-dirty circuits for new streams, so we
12629 don't link new actions to old actions. This also occurs on HUP
12630 or "signal reload".
12631 - If we would close a stream early (e.g. it asks for a .exit that
12632 we know would refuse it) but the LeaveStreamsUnattached config
12633 option is set by the controller, then don't close it.
12634 - Add a new controller event type "authdir_newdescs" that allows
12635 controllers to get all server descriptors that were uploaded to
12636 a router in its role as directory authority.
12637 - New controller option "getinfo desc/all-recent" to fetch the
12638 latest server descriptor for every router that Tor knows about.
12639 - Fix the controller's "attachstream 0" command to treat conn like
12640 it just connected, doing address remapping, handling .exit and
12641 .onion idioms, and so on. Now we're more uniform in making sure
12642 that the controller hears about new and closing connections.
12643 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
12644 the controller. Also, rotate dns and cpu workers if the controller
12645 changes options that will affect them; and initialize the dns
12646 worker cache tree whether or not we start out as a server.
12647 - Add a new circuit purpose 'controller' to let the controller ask
12648 for a circuit that Tor won't try to use. Extend the "extendcircuit"
12649 controller command to let you specify the purpose if you're starting
12650 a new circuit. Add a new "setcircuitpurpose" controller command to
12651 let you change a circuit's purpose after it's been created.
12652 - Let the controller ask for "getinfo dir/server/foo" so it can ask
12653 directly rather than connecting to the dir port. "getinfo
12654 dir/status/foo" also works, but currently only if your DirPort
12656 - Let the controller tell us about certain router descriptors
12657 that it doesn't want Tor to use in circuits. Implement
12658 "setrouterpurpose" and modify "+postdescriptor" to do this.
12659 - If the controller's *setconf commands fail, collect an error
12660 message in a string and hand it back to the controller -- don't
12661 just tell them to go read their logs.
12663 o Scalability, resource management, and performance:
12664 - Fix a major load balance bug: we were round-robin reading in 16 KB
12665 chunks, and servers with bandwidthrate of 20 KB, while downloading
12666 a 600 KB directory, would starve their other connections. Now we
12667 try to be a bit more fair.
12668 - Be more conservative about whether to advertise our DirPort.
12669 The main change is to not advertise if we're running at capacity
12670 and either a) we could hibernate ever or b) our capacity is low
12671 and we're using a default DirPort.
12672 - We weren't cannibalizing circuits correctly for
12673 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
12674 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
12675 build those from scratch. This should make hidden services faster.
12676 - Predict required circuits better, with an eye toward making hidden
12677 services faster on the service end.
12678 - Compress exit policies even more: look for duplicate lines and
12680 - Generate 18.0.0.0/8 address policy format in descs when we can;
12681 warn when the mask is not reducible to a bit-prefix.
12682 - There used to be two ways to specify your listening ports in a
12683 server descriptor: on the "router" line and with a separate "ports"
12684 line. Remove support for the "ports" line.
12685 - Reduce memory requirements in our structs by changing the order
12686 of fields. Replace balanced trees with hash tables. Inline
12687 bottleneck smartlist functions. Add a "Map from digest to void*"
12688 abstraction so we can do less hex encoding/decoding, and use it
12689 in router_get_by_digest(). Many other CPU and memory improvements.
12690 - Allow tor_gzip_uncompress to extract as much as possible from
12691 truncated compressed data. Try to extract as many
12692 descriptors as possible from truncated http responses (when
12693 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
12694 - Make circ->onionskin a pointer, not a static array. moria2 was using
12695 125000 circuit_t's after it had been up for a few weeks, which
12696 translates to 20+ megs of wasted space.
12697 - The private half of our EDH handshake keys are now chosen out
12698 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
12699 - Stop doing the complex voodoo overkill checking for insecure
12700 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
12701 - Do round-robin writes for TLS of at most 16 kB per write. This
12702 might be more fair on loaded Tor servers.
12703 - Do not use unaligned memory access on alpha, mips, or mipsel.
12704 It *works*, but is very slow, so we treat them as if it doesn't.
12706 o Other bugfixes and improvements:
12707 - Start storing useful information to $DATADIR/state, so we can
12708 remember things across invocations of Tor. Retain unrecognized
12709 lines so we can be forward-compatible, and write a TorVersion line
12710 so we can be backward-compatible.
12711 - If ORPort is set, Address is not explicitly set, and our hostname
12712 resolves to a private IP address, try to use an interface address
12713 if it has a public address. Now Windows machines that think of
12714 themselves as localhost can guess their address.
12715 - Regenerate our local descriptor if it's dirty and we try to use
12716 it locally (e.g. if it changes during reachability detection).
12717 This was causing some Tor servers to keep publishing the same
12718 initial descriptor forever.
12719 - Tor servers with dynamic IP addresses were needing to wait 18
12720 hours before they could start doing reachability testing using
12721 the new IP address and ports. This is because they were using
12722 the internal descriptor to learn what to test, yet they were only
12723 rebuilding the descriptor once they decided they were reachable.
12724 - It turns out we couldn't bootstrap a network since we added
12725 reachability detection in 0.1.0.1-rc. Good thing the Tor network
12726 has never gone down. Add an AssumeReachable config option to let
12727 servers and authorities bootstrap. When we're trying to build a
12728 high-uptime or high-bandwidth circuit but there aren't enough
12729 suitable servers, try being less picky rather than simply failing.
12730 - Newly bootstrapped Tor networks couldn't establish hidden service
12731 circuits until they had nodes with high uptime. Be more tolerant.
12732 - Really busy servers were keeping enough circuits open on stable
12733 connections that they were wrapping around the circuit_id
12734 space. (It's only two bytes.) This exposed a bug where we would
12735 feel free to reuse a circuit_id even if it still exists but has
12736 been marked for close. Try to fix this bug. Some bug remains.
12737 - When we fail to bind or listen on an incoming or outgoing
12738 socket, we now close it before refusing, rather than just
12739 leaking it. (Thanks to Peter Palfrader for finding.)
12740 - Fix a file descriptor leak in start_daemon().
12741 - On Windows, you can't always reopen a port right after you've
12742 closed it. So change retry_listeners() to only close and re-open
12743 ports that have changed.
12744 - Workaround a problem with some http proxies that refuse GET
12745 requests that specify "Content-Length: 0". Reported by Adrian.
12746 - Recover better from TCP connections to Tor servers that are
12747 broken but don't tell you (it happens!); and rotate TLS
12748 connections once a week.
12749 - Fix a scary-looking but apparently harmless bug where circuits
12750 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
12751 servers, and never switch to state CIRCUIT_STATE_OPEN.
12752 - Check for even more Windows version flags when writing the platform
12753 string in server descriptors, and note any we don't recognize.
12754 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
12755 get a better idea of why their circuits failed. Not used yet.
12756 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
12757 We don't use them yet, but maybe one day our DNS resolver will be
12758 able to discover them.
12759 - Let people type "tor --install" as well as "tor -install" when they
12760 want to make it an NT service.
12761 - Looks like we were never delivering deflated (i.e. compressed)
12762 running-routers lists, even when asked. Oops.
12763 - We were leaking some memory every time the client changed IPs.
12764 - Clean up more of the OpenSSL memory when exiting, so we can detect
12765 memory leaks better.
12766 - Never call free() on tor_malloc()d memory. This will help us
12767 use dmalloc to detect memory leaks.
12768 - Some Tor servers process billions of cells per day. These
12769 statistics are now uint64_t's.
12770 - Check [X-]Forwarded-For headers in HTTP requests when generating
12771 log messages. This lets people run dirservers (and caches) behind
12772 Apache but still know which IP addresses are causing warnings.
12773 - Fix minor integer overflow in calculating when we expect to use up
12774 our bandwidth allocation before hibernating.
12775 - Lower the minimum required number of file descriptors to 1000,
12776 so we can have some overhead for Valgrind on Linux, where the
12777 default ulimit -n is 1024.
12778 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12779 and its existence is confusing some users.
12781 o Config option fixes:
12782 - Add a new config option ExitPolicyRejectPrivate which defaults
12783 to on. Now all exit policies will begin with rejecting private
12784 addresses, unless the server operator explicitly turns it off.
12785 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
12786 - Add new ReachableORAddresses and ReachableDirAddresses options
12787 that understand address policies. FascistFirewall is now a synonym
12788 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
12789 - Start calling it FooListenAddress rather than FooBindAddress,
12790 since few of our users know what it means to bind an address
12792 - If the user gave Tor an odd number of command-line arguments,
12793 we were silently ignoring the last one. Now we complain and fail.
12794 This wins the oldest-bug prize -- this bug has been present since
12795 November 2002, as released in Tor 0.0.0.
12796 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
12797 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
12798 it would silently ignore the 6668.
12799 - If we get a linelist or linelist_s config option from the torrc,
12800 e.g. ExitPolicy, and it has no value, warn and skip rather than
12801 silently resetting it to its default.
12802 - Setconf was appending items to linelists, not clearing them.
12803 - Add MyFamily to torrc.sample in the server section, so operators
12804 will be more likely to learn that it exists.
12805 - Make ContactInfo mandatory for authoritative directory servers.
12806 - MaxConn has been obsolete for a while now. Document the ConnLimit
12807 config option, which is a *minimum* number of file descriptors
12808 that must be available else Tor refuses to start.
12809 - Get rid of IgnoreVersion undocumented config option, and make us
12810 only warn, never exit, when we're running an obsolete version.
12811 - Make MonthlyAccountingStart config option truly obsolete now.
12812 - Correct the man page entry on TrackHostExitsExpire.
12813 - Let directory authorities start even if they don't specify an
12814 Address config option.
12815 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12816 reflect the updated flags in our v2 dir protocol.
12818 o Config option features:
12819 - Add a new config option FastFirstHopPK (on by default) so clients
12820 do a trivial crypto handshake for their first hop, since TLS has
12821 already taken care of confidentiality and authentication.
12822 - Let the user set ControlListenAddress in the torrc. This can be
12823 dangerous, but there are some cases (like a secured LAN) where it
12825 - New config options to help controllers: FetchServerDescriptors
12826 and FetchHidServDescriptors for whether to fetch server
12827 info and hidserv info or let the controller do it, and
12828 PublishServerDescriptor and PublishHidServDescriptors.
12829 - Also let the controller set the __AllDirActionsPrivate config
12830 option if you want all directory fetches/publishes to happen via
12831 Tor (it assumes your controller bootstraps your circuits).
12832 - Add "HardwareAccel" config option: support for crypto hardware
12833 accelerators via OpenSSL. Off by default, until we find somebody
12834 smart who can test it for us. (It appears to produce seg faults
12835 in at least some cases.)
12836 - New config option "AuthDirRejectUnlisted" for directory authorities
12837 as a panic button: if we get flooded with unusable servers we can
12838 revert to only listing servers in the approved-routers file.
12839 - Directory authorities can now reject/invalidate by key and IP,
12840 with the config options "AuthDirInvalid" and "AuthDirReject", or
12841 by marking a fingerprint as "!reject" or "!invalid" (as its
12842 nickname) in the approved-routers file. This is useful since
12843 currently we automatically list servers as running and usable
12844 even if we know they're jerks.
12845 - Add a new config option TestSocks so people can see whether their
12846 applications are using socks4, socks4a, socks5-with-ip, or
12847 socks5-with-fqdn. This way they don't have to keep mucking
12848 with tcpdump and wondering if something got cached somewhere.
12849 - Add "private:*" as an alias in configuration for policies. Now
12850 you can simplify your exit policy rather than needing to list
12851 every single internal or nonroutable network space.
12852 - Accept "private:*" in routerdesc exit policies; not generated yet
12853 because older Tors do not understand it.
12854 - Add configuration option "V1AuthoritativeDirectory 1" which
12855 moria1, moria2, and tor26 have set.
12856 - Implement an option, VirtualAddrMask, to set which addresses
12857 get handed out in response to mapaddress requests. This works
12858 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12859 - Add a new config option FetchUselessDescriptors, off by default,
12860 for when you plan to run "exitlist" on your client and you want
12861 to know about even the non-running descriptors.
12862 - SocksTimeout: How long do we let a socks connection wait
12863 unattached before we fail it?
12864 - CircuitBuildTimeout: Cull non-open circuits that were born
12865 at least this many seconds ago.
12866 - CircuitIdleTimeout: Cull open clean circuits that were born
12867 at least this many seconds ago.
12868 - New config option SafeSocks to reject all application connections
12869 using unsafe socks protocols. Defaults to off.
12871 o Improved and clearer log messages:
12872 - Reduce clutter in server logs. We're going to try to make
12873 them actually usable now. New config option ProtocolWarnings that
12874 lets you hear about how _other Tors_ are breaking the protocol. Off
12876 - Divide log messages into logging domains. Once we put some sort
12877 of interface on this, it will let people looking at more verbose
12878 log levels specify the topics they want to hear more about.
12879 - Log server fingerprint on startup, so new server operators don't
12880 have to go hunting around their filesystem for it.
12881 - Provide dire warnings to any users who set DirServer manually;
12882 move it out of torrc.sample and into torrc.complete.
12883 - Make the log message less scary when all the dirservers are
12884 temporarily unreachable.
12885 - When tor_socketpair() fails in Windows, give a reasonable
12886 Windows-style errno back.
12887 - Improve tor_gettimeofday() granularity on windows.
12888 - We were printing the number of idle dns workers incorrectly when
12890 - Handle duplicate lines in approved-routers files without warning.
12891 - We were whining about using socks4 or socks5-with-local-lookup
12892 even when it's an IP address in the "virtual" range we designed
12893 exactly for this case.
12894 - Check for named servers when looking them up by nickname;
12895 warn when we're calling a non-named server by its nickname;
12896 don't warn twice about the same name.
12897 - Downgrade the dirserver log messages when whining about
12899 - Correct "your server is reachable" log entries to indicate that
12900 it was self-testing that told us so.
12901 - If we're trying to be a Tor server and running Windows 95/98/ME
12902 as a server, explain that we'll likely crash.
12903 - Provide a more useful warn message when our onion queue gets full:
12904 the CPU is too slow or the exit policy is too liberal.
12905 - Don't warn when we receive a 503 from a dirserver/cache -- this
12906 will pave the way for them being able to refuse if they're busy.
12907 - When we fail to bind a listener, try to provide a more useful
12908 log message: e.g., "Is Tor already running?"
12909 - Only start testing reachability once we've established a
12910 circuit. This will make startup on dir authorities less noisy.
12911 - Don't try to upload hidden service descriptors until we have
12912 established a circuit.
12913 - Tor didn't warn when it failed to open a log file.
12914 - Warn when listening on a public address for socks. We suspect a
12915 lot of people are setting themselves up as open socks proxies,
12916 and they have no idea that jerks on the Internet are using them,
12917 since they simply proxy the traffic into the Tor network.
12918 - Give a useful message when people run Tor as the wrong user,
12919 rather than telling them to start chowning random directories.
12920 - Fix a harmless bug that was causing Tor servers to log
12921 "Got an end because of misc error, but we're not an AP. Closing."
12922 - Fix wrong log message when you add a "HiddenServiceNodes" config
12923 line without any HiddenServiceDir line (reported by Chris Thomas).
12924 - Directory authorities now stop whining so loudly about bad
12925 descriptors that they fetch from other dirservers. So when there's
12926 a log complaint, it's for sure from a freshly uploaded descriptor.
12927 - When logging via syslog, include the pid whenever we provide
12928 a log entry. Suggested by Todd Fries.
12929 - When we're shutting down and we do something like try to post a
12930 server descriptor or rendezvous descriptor, don't complain that
12931 we seem to be unreachable. Of course we are, we're shutting down.
12932 - Change log line for unreachability to explicitly suggest /etc/hosts
12933 as the culprit. Also make it clearer what IP address and ports we're
12934 testing for reachability.
12935 - Put quotes around user-supplied strings when logging so users are
12936 more likely to realize if they add bad characters (like quotes)
12938 - NT service patch from Matt Edman to improve error messages on Win32.
12941 Changes in version 0.1.0.17 - 2006-02-17
12942 o Crash bugfixes on 0.1.0.x:
12943 - When servers with a non-zero DirPort came out of hibernation,
12944 sometimes they would trigger an assert.
12946 o Other important bugfixes:
12947 - On platforms that don't have getrlimit (like Windows), we were
12948 artificially constraining ourselves to a max of 1024
12949 connections. Now just assume that we can handle as many as 15000
12950 connections. Hopefully this won't cause other problems.
12952 o Backported features:
12953 - When we're a server, a client asks for an old-style directory,
12954 and our write bucket is empty, don't give it to him. This way
12955 small servers can continue to serve the directory *sometimes*,
12956 without getting overloaded.
12957 - Whenever you get a 503 in response to a directory fetch, try
12958 once more. This will become important once servers start sending
12959 503's whenever they feel busy.
12960 - Fetch a new directory every 120 minutes, not every 40 minutes.
12961 Now that we have hundreds of thousands of users running the old
12962 directory algorithm, it's starting to hurt a lot.
12963 - Bump up the period for forcing a hidden service descriptor upload
12964 from 20 minutes to 1 hour.
12967 Changes in version 0.1.0.16 - 2006-01-02
12968 o Crash bugfixes on 0.1.0.x:
12969 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12970 corrupting the heap, losing FDs, or crashing when we need to resize
12971 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12972 - It turns out sparc64 platforms crash on unaligned memory access
12973 too -- so detect and avoid this.
12974 - Handle truncated compressed data correctly (by detecting it and
12976 - Fix possible-but-unlikely free(NULL) in control.c.
12977 - When we were closing connections, there was a rare case that
12978 stomped on memory, triggering seg faults and asserts.
12979 - Avoid potential infinite recursion when building a descriptor. (We
12980 don't know that it ever happened, but better to fix it anyway.)
12981 - We were neglecting to unlink marked circuits from soon-to-close OR
12982 connections, which caused some rare scribbling on freed memory.
12983 - Fix a memory stomping race bug when closing the joining point of two
12984 rendezvous circuits.
12985 - Fix an assert in time parsing found by Steven Murdoch.
12987 o Other bugfixes on 0.1.0.x:
12988 - When we're doing reachability testing, provide more useful log
12989 messages so the operator knows what to expect.
12990 - Do not check whether DirPort is reachable when we are suppressing
12991 advertising it because of hibernation.
12992 - When building with -static or on Solaris, we sometimes needed -ldl.
12993 - One of the dirservers (tor26) changed its IP address.
12994 - When we're deciding whether a stream has enough circuits around
12995 that can handle it, count the freshly dirty ones and not the ones
12996 that are so dirty they won't be able to handle it.
12997 - When we're expiring old circuits, we had a logic error that caused
12998 us to close new rendezvous circuits rather than old ones.
12999 - Give a more helpful log message when you try to change ORPort via
13000 the controller: you should upgrade Tor if you want that to work.
13001 - We were failing to parse Tor versions that start with "Tor ".
13002 - Tolerate faulty streams better: when a stream fails for reason
13003 exitpolicy, stop assuming that the router is lying about his exit
13004 policy. When a stream fails for reason misc, allow it to retry just
13005 as if it was resolvefailed. When a stream has failed three times,
13006 reset its failure count so we can try again and get all three tries.
13009 Changes in version 0.1.0.15 - 2005-09-23
13010 o Bugfixes on 0.1.0.x:
13011 - Reject ports 465 and 587 (spam targets) in default exit policy.
13012 - Don't crash when we don't have any spare file descriptors and we
13013 try to spawn a dns or cpu worker.
13014 - Get rid of IgnoreVersion undocumented config option, and make us
13015 only warn, never exit, when we're running an obsolete version.
13016 - Don't try to print a null string when your server finds itself to
13017 be unreachable and the Address config option is empty.
13018 - Make the numbers in read-history and write-history into uint64s,
13019 so they don't overflow and publish negatives in the descriptor.
13020 - Fix a minor memory leak in smartlist_string_remove().
13021 - We were only allowing ourselves to upload a server descriptor at
13022 most every 20 minutes, even if it changed earlier than that.
13023 - Clean up log entries that pointed to old URLs.
13026 Changes in version 0.1.0.14 - 2005-08-08
13027 o Bugfixes on 0.1.0.x:
13028 - Fix the other half of the bug with crypto handshakes
13030 - Fix an assert trigger if you send a 'signal term' via the
13031 controller when it's listening for 'event info' messages.
13034 Changes in version 0.1.0.13 - 2005-08-04
13035 o Bugfixes on 0.1.0.x:
13036 - Fix a critical bug in the security of our crypto handshakes.
13037 - Fix a size_t underflow in smartlist_join_strings2() that made
13038 it do bad things when you hand it an empty smartlist.
13039 - Fix Windows installer to ship Tor license (thanks to Aphex for
13040 pointing out this oversight) and put a link to the doc directory
13042 - Explicitly set no-unaligned-access for sparc: it turns out the
13043 new gcc's let you compile broken code, but that doesn't make it
13047 Changes in version 0.1.0.12 - 2005-07-18
13048 o New directory servers:
13049 - tor26 has changed IP address.
13051 o Bugfixes on 0.1.0.x:
13052 - Fix a possible double-free in tor_gzip_uncompress().
13053 - When --disable-threads is set, do not search for or link against
13054 pthreads libraries.
13055 - Don't trigger an assert if an authoritative directory server
13056 claims its dirport is 0.
13057 - Fix bug with removing Tor as an NT service: some people were
13058 getting "The service did not return an error." Thanks to Matt
13062 Changes in version 0.1.0.11 - 2005-06-30
13063 o Bugfixes on 0.1.0.x:
13064 - Fix major security bug: servers were disregarding their
13065 exit policies if clients behaved unexpectedly.
13066 - Make OS X init script check for missing argument, so we don't
13067 confuse users who invoke it incorrectly.
13068 - Fix a seg fault in "tor --hash-password foo".
13069 - The MAPADDRESS control command was broken.
13072 Changes in version 0.1.0.10 - 2005-06-14
13074 - Make NT services work and start on startup on Win32 (based on
13075 patch by Matt Edman). See the FAQ entry for details.
13076 - Make 'platform' string in descriptor more accurate for Win32
13077 servers, so it's not just "unknown platform".
13078 - REUSEADDR on normal platforms means you can rebind to the port
13079 right after somebody else has let it go. But REUSEADDR on Win32
13080 means you can bind to the port _even when somebody else already
13081 has it bound_! So, don't do that on Win32.
13082 - Clean up the log messages when starting on Win32 with no config
13084 - Allow seeding the RNG on Win32 even when you're not running as
13085 Administrator. If seeding the RNG on Win32 fails, quit.
13087 o Assert / crash bugs:
13088 - Refuse relay cells that claim to have a length larger than the
13089 maximum allowed. This prevents a potential attack that could read
13090 arbitrary memory (e.g. keys) from an exit server's process
13092 - If unofficial Tor clients connect and send weird TLS certs, our
13093 Tor server triggers an assert. Stop asserting, and start handling
13094 TLS errors better in other situations too.
13095 - Fix a race condition that can trigger an assert when we have a
13096 pending create cell and an OR connection attempt fails.
13099 - Use pthreads for worker processes rather than forking. This was
13100 forced because when we forked, we ended up wasting a lot of
13101 duplicate ram over time.
13102 - Also switch to foo_r versions of some library calls to allow
13103 reentry and threadsafeness.
13104 - Implement --disable-threads configure option. Disable threads on
13105 netbsd and openbsd by default, because they have no reentrant
13106 resolver functions (!), and on solaris since it has other
13108 - Fix possible bug on threading platforms (e.g. win32) which was
13109 leaking a file descriptor whenever a cpuworker or dnsworker died.
13110 - Fix a minor memory leak when somebody establishes an introduction
13111 point at your Tor server.
13112 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
13114 - Add ./configure --with-dmalloc option, to track memory leaks.
13115 - And try to free all memory on closing, so we can detect what
13118 o Protocol correctness:
13119 - When we've connected to an OR and handshaked but didn't like
13120 the result, we were closing the conn without sending destroy
13121 cells back for pending circuits. Now send those destroys.
13122 - Start sending 'truncated' cells back rather than destroy cells
13123 if the circuit closes in front of you. This means we won't have
13124 to abandon partially built circuits.
13125 - Handle changed router status correctly when dirserver reloads
13126 fingerprint file. We used to be dropping all unverified descriptors
13127 right then. The bug was hidden because we would immediately
13128 fetch a directory from another dirserver, which would include the
13129 descriptors we just dropped.
13130 - Revise tor-spec to add more/better stream end reasons.
13131 - Revise all calls to connection_edge_end to avoid sending 'misc',
13132 and to take errno into account where possible.
13133 - Client now retries when streams end early for 'hibernating' or
13134 'resource limit' reasons, rather than failing them.
13135 - Try to be more zealous about calling connection_edge_end when
13136 things go bad with edge conns in connection.c.
13138 o Robustness improvements:
13139 - Better handling for heterogeneous / unreliable nodes:
13140 - Annotate circuits with whether they aim to contain high uptime
13141 nodes and/or high capacity nodes. When building circuits, choose
13143 - This means that every single node in an intro rend circuit,
13144 not just the last one, will have a minimum uptime.
13145 - New config option LongLivedPorts to indicate application streams
13146 that will want high uptime circuits.
13147 - Servers reset uptime when a dir fetch entirely fails. This
13148 hopefully reflects stability of the server's network connectivity.
13149 - If somebody starts his tor server in Jan 2004 and then fixes his
13150 clock, don't make his published uptime be a year.
13151 - Reset published uptime when we wake up from hibernation.
13152 - Introduce a notion of 'internal' circs, which are chosen without
13153 regard to the exit policy of the last hop. Intro and rendezvous
13154 circs must be internal circs, to avoid leaking information. Resolve
13155 and connect streams can use internal circs if they want.
13156 - New circuit pooling algorithm: keep track of what destination ports
13157 we've used recently (start out assuming we'll want to use 80), and
13158 make sure to have enough circs around to satisfy these ports. Also
13159 make sure to have 2 internal circs around if we've required internal
13160 circs lately (and with high uptime if we've seen that lately too).
13161 - Turn addr_policy_compare from a tristate to a quadstate; this should
13162 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
13163 for google.com" problem.
13164 - When a client asks us for a dir mirror and we don't have one,
13165 launch an attempt to get a fresh one.
13166 - First cut at support for "create-fast" cells. Clients can use
13167 these when extending to their first hop, since the TLS already
13168 provides forward secrecy and authentication. Not enabled on
13171 o Reachability testing.
13172 - Your Tor server will automatically try to see if its ORPort and
13173 DirPort are reachable from the outside, and it won't upload its
13174 descriptor until it decides at least ORPort is reachable (when
13175 DirPort is not yet found reachable, publish it as zero).
13176 - When building testing circs for ORPort testing, use only
13177 high-bandwidth nodes, so fewer circuits fail.
13178 - Notice when our IP changes, and reset stats/uptime/reachability.
13179 - Authdirservers don't do ORPort reachability detection, since
13180 they're in clique mode, so it will be rare to find a server not
13181 already connected to them.
13182 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
13186 - Now we allow two unverified servers with the same nickname
13187 but different keys. But if a nickname is verified, only that
13188 nickname+key are allowed.
13189 - If you're an authdirserver connecting to an address:port,
13190 and it's not the OR you were expecting, forget about that
13191 descriptor. If he *was* the one you were expecting, then forget
13192 about all other descriptors for that address:port.
13193 - Allow servers to publish descriptors from 12 hours in the future.
13194 Corollary: only whine about clock skew from the dirserver if
13195 he's a trusted dirserver (since now even verified servers could
13196 have quite wrong clocks).
13197 - Require servers that use the default dirservers to have public IP
13198 addresses. We have too many servers that are configured with private
13199 IPs and their admins never notice the log entries complaining that
13200 their descriptors are being rejected.
13202 o Efficiency improvements:
13203 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
13204 and /dev/poll), and hopefully work better on Windows too.
13205 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
13206 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
13207 - Find libevent even if it's hiding in /usr/local/ and your
13208 CFLAGS and LDFLAGS don't tell you to look there.
13209 - Be able to link with libevent as a shared library (the default
13210 after 1.0d), even if it's hiding in /usr/local/lib and even
13211 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13212 assuming you're running gcc. Otherwise fail and give a useful
13214 - Switch to a new buffer management algorithm, which tries to avoid
13215 reallocing and copying quite as much. In first tests it looks like
13216 it uses *more* memory on average, but less cpu.
13217 - Switch our internal buffers implementation to use a ring buffer,
13218 to hopefully improve performance for fast servers a lot.
13219 - Reenable the part of the code that tries to flush as soon as an
13220 OR outbuf has a full TLS record available. Perhaps this will make
13221 OR outbufs not grow as huge except in rare cases, thus saving lots
13222 of CPU time plus memory.
13223 - Improve performance for dirservers: stop re-parsing the whole
13224 directory every time you regenerate it.
13225 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13226 it much faster to look up a circuit for each relay cell.
13227 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13228 since they're eating our cpu on exit nodes.
13229 - Stop wasting time doing a case insensitive comparison for every
13230 dns name every time we do any lookup. Canonicalize the names to
13231 lowercase when you first see them.
13234 - Handle unavailable hidden services better. Handle slow or busy
13235 hidden services better.
13236 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
13237 circ as necessary, if there are any completed ones lying around
13238 when we try to launch one.
13239 - Make hidden services try to establish a rendezvous for 30 seconds
13240 after fetching the descriptor, rather than for n (where n=3)
13241 attempts to build a circuit.
13242 - Adjust maximum skew and age for rendezvous descriptors: let skew
13243 be 48 hours rather than 90 minutes.
13244 - Reject malformed .onion addresses rather then passing them on as
13245 normal web requests.
13248 - More Tor controller support. See
13249 http://tor.eff.org/doc/control-spec.txt for all the new features,
13250 including signals to emulate unix signals from any platform;
13251 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
13252 closestream; closecircuit; etc.
13253 - Encode hashed controller passwords in hex instead of base64,
13254 to make it easier to write controllers.
13255 - Revise control spec and implementation to allow all log messages to
13256 be sent to controller with their severities intact (suggested by
13257 Matt Edman). Disable debug-level logs while delivering a debug-level
13258 log to the controller, to prevent loop. Update TorControl to handle
13259 new log event types.
13261 o New config options/defaults:
13262 - Begin scrubbing sensitive strings from logs by default. Turn off
13263 the config option SafeLogging if you need to do debugging.
13264 - New exit policy: accept most low-numbered ports, rather than
13265 rejecting most low-numbered ports.
13266 - Put a note in the torrc about abuse potential with the default
13268 - Add support for CONNECTing through https proxies, with "HttpsProxy"
13270 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
13271 based on patch from Adam Langley (basic auth only).
13272 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13273 the fast servers that have been joining lately. (Clients are now
13274 willing to load balance over up to 2 MB of advertised bandwidth
13276 - New config option MaxAdvertisedBandwidth which lets you advertise
13277 a low bandwidthrate (to not attract as many circuits) while still
13278 allowing a higher bandwidthrate in reality.
13279 - Require BandwidthRate to be at least 20kB/s for servers.
13280 - Add a NoPublish config option, so you can be a server (e.g. for
13281 testing running Tor servers in other Tor networks) without
13282 publishing your descriptor to the primary dirservers.
13283 - Add a new AddressMap config directive to rewrite incoming socks
13284 addresses. This lets you, for example, declare an implicit
13285 required exit node for certain sites.
13286 - Add a new TrackHostExits config directive to trigger addressmaps
13287 for certain incoming socks addresses -- for sites that break when
13288 your exit keeps changing (based on patch from Mike Perry).
13289 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
13290 which describes how often we retry making new circuits if current
13291 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
13292 how long we're willing to make use of an already-dirty circuit.
13293 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
13294 a config option "ShutdownWaitLength" (when using kill -INT on
13296 - Fix an edge case in parsing config options: if they say "--"
13297 on the commandline, it's not a config option (thanks weasel).
13298 - New config option DirAllowPrivateAddresses for authdirservers.
13299 Now by default they refuse router descriptors that have non-IP or
13300 private-IP addresses.
13301 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
13302 smart" default value: low for servers and high for clients.
13303 - Some people were putting "Address " in their torrc, and they had
13304 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13305 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13306 LOCALSTATEDIR/tor instead.
13307 - Implement --verify-config command-line option to check if your torrc
13308 is valid without actually launching Tor.
13310 o Logging improvements:
13311 - When dirservers refuse a server descriptor, we now log its
13312 contactinfo, platform, and the poster's IP address.
13313 - Only warn once per nickname from add_nickname_list_to_smartlist()
13314 per failure, so an entrynode or exitnode choice that's down won't
13316 - When we're connecting to an OR and he's got a different nickname/key
13317 than we were expecting, only complain loudly if we're an OP or a
13318 dirserver. Complaining loudly to the OR admins just confuses them.
13319 - Whine at you if you're a server and you don't set your contactinfo.
13320 - Warn when exit policy implicitly allows local addresses.
13321 - Give a better warning when some other server advertises an
13322 ORPort that is actually an apache running ssl.
13323 - If we get an incredibly skewed timestamp from a dirserver mirror
13324 that isn't a verified OR, don't warn -- it's probably him that's
13326 - When a dirserver causes you to give a warn, mention which dirserver
13328 - Initialize libevent later in the startup process, so the logs are
13329 already established by the time we start logging libevent warns.
13330 - Use correct errno on win32 if libevent fails.
13331 - Check and warn about known-bad/slow libevent versions.
13332 - Stop warning about sigpipes in the logs. We're going to
13333 pretend that getting these occassionally is normal and fine.
13335 o New contrib scripts:
13336 - New experimental script tor/contrib/exitlist: a simple python
13337 script to parse directories and find Tor nodes that exit to listed
13339 - New experimental script tor/contrib/ExerciseServer.py (needs more
13340 work) that uses the controller interface to build circuits and
13341 fetch pages over them. This will help us bootstrap servers that
13342 have lots of capacity but haven't noticed it yet.
13343 - New experimental script tor/contrib/PathDemo.py (needs more work)
13344 that uses the controller interface to let you choose whole paths
13346 "<hostname>.<path,separated by dots>.<length of path>.path"
13347 - New contributed script "privoxy-tor-toggle" to toggle whether
13348 Privoxy uses Tor. Seems to be configured for Debian by default.
13349 - Have torctl.in/tor.sh.in check for location of su binary (needed
13353 - chdir() to your datadirectory at the *end* of the daemonize process,
13354 not the beginning. This was a problem because the first time you
13355 run tor, if your datadir isn't there, and you have runasdaemon set
13356 to 1, it will try to chdir to it before it tries to create it. Oops.
13357 - Fix several double-mark-for-close bugs, e.g. where we were finding
13358 a conn for a cell even if that conn is already marked for close.
13359 - Stop most cases of hanging up on a socks connection without sending
13361 - Fix a bug in the RPM package: set home directory for _tor to
13362 something more reasonable when first installing.
13363 - Stop putting nodename in the Platform string in server descriptors.
13364 It doesn't actually help, and it is confusing/upsetting some people.
13365 - When using preferred entry or exit nodes, ignore whether the
13366 circuit wants uptime or capacity. They asked for the nodes, they
13368 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13369 artificially capped at 500kB.
13370 - Cache local dns resolves correctly even when they're .exit
13372 - If we're hibernating and we get a SIGINT, exit immediately.
13373 - tor-resolve requests were ignoring .exit if there was a working circuit
13374 they could use instead.
13375 - Pay more attention to the ClientOnly config option.
13376 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
13377 installer screens; and don't put stuff into StartupItems unless
13378 the user asks you to.
13381 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
13382 rather than just rejecting it.
13383 - If our clock jumps forward by 100 seconds or more, assume something
13384 has gone wrong with our network and abandon all not-yet-used circs.
13385 - When an application is using socks5, give him the whole variety of
13386 potential socks5 responses (connect refused, host unreachable, etc),
13387 rather than just "success" or "failure".
13388 - A more sane version numbering system. See
13389 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
13390 - Change version parsing logic: a version is "obsolete" if it is not
13391 recommended and (1) there is a newer recommended version in the
13392 same series, or (2) there are no recommended versions in the same
13393 series, but there are some recommended versions in a newer series.
13394 A version is "new" if it is newer than any recommended version in
13396 - Report HTTP reasons to client when getting a response from directory
13397 servers -- so you can actually know what went wrong.
13398 - Reject odd-looking addresses at the client (e.g. addresses that
13399 contain a colon), rather than having the server drop them because
13401 - Stop publishing socksport in the directory, since it's not
13402 actually meant to be public. For compatibility, publish a 0 there
13404 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
13405 cookies to disk and doesn't log each web request to disk. (Thanks
13406 to Brett Carrington for pointing this out.)
13407 - Add OSX uninstall instructions. An actual uninstall script will
13409 - Add "opt hibernating 1" to server descriptor to make it clearer
13410 whether the server is hibernating.
13413 Changes in version 0.0.9.10 - 2005-06-16
13414 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13415 - Refuse relay cells that claim to have a length larger than the
13416 maximum allowed. This prevents a potential attack that could read
13417 arbitrary memory (e.g. keys) from an exit server's process
13421 Changes in version 0.0.9.9 - 2005-04-23
13422 o Bugfixes on 0.0.9.x:
13423 - If unofficial Tor clients connect and send weird TLS certs, our
13424 Tor server triggers an assert. This release contains a minimal
13425 backport from the broader fix that we put into 0.1.0.4-rc.
13428 Changes in version 0.0.9.8 - 2005-04-07
13429 o Bugfixes on 0.0.9.x:
13430 - We have a bug that I haven't found yet. Sometimes, very rarely,
13431 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13432 thinks of itself as idle. This meant that no new circuits ever got
13433 established. Here's a workaround to kill any cpuworker that's been
13434 busy for more than 100 seconds.
13437 Changes in version 0.0.9.7 - 2005-04-01
13438 o Bugfixes on 0.0.9.x:
13439 - Fix another race crash bug (thanks to Glenn Fink for reporting).
13440 - Compare identity to identity, not to nickname, when extending to
13441 a router not already in the directory. This was preventing us from
13442 extending to unknown routers. Oops.
13443 - Make sure to create OS X Tor user in <500 range, so we aren't
13444 creating actual system users.
13445 - Note where connection-that-hasn't-sent-end was marked, and fix
13446 a few really loud instances of this harmless bug (it's fixed more
13450 Changes in version 0.0.9.6 - 2005-03-24
13451 o Bugfixes on 0.0.9.x (crashes and asserts):
13452 - Add new end stream reasons to maintainance branch. Fix bug where
13453 reason (8) could trigger an assert. Prevent bug from recurring.
13454 - Apparently win32 stat wants paths to not end with a slash.
13455 - Fix assert triggers in assert_cpath_layer_ok(), where we were
13456 blowing away the circuit that conn->cpath_layer points to, then
13457 checking to see if the circ is well-formed. Backport check to make
13458 sure we dont use the cpath on a closed connection.
13459 - Prevent circuit_resume_edge_reading_helper() from trying to package
13460 inbufs for marked-for-close streams.
13461 - Don't crash on hup if your options->address has become unresolvable.
13462 - Some systems (like OS X) sometimes accept() a connection and tell
13463 you the remote host is 0.0.0.0:0. If this happens, due to some
13464 other mis-features, we get confused; so refuse the conn for now.
13466 o Bugfixes on 0.0.9.x (other):
13467 - Fix harmless but scary "Unrecognized content encoding" warn message.
13468 - Add new stream error reason: TORPROTOCOL reason means "you are not
13469 speaking a version of Tor I understand; say bye-bye to your stream."
13470 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
13471 into the future, now that we are more tolerant of skew. This
13472 resolves a bug where a Tor server would refuse to cache a directory
13473 because all the directories it gets are too far in the future;
13474 yet the Tor server never logs any complaints about clock skew.
13475 - Mac packaging magic: make man pages useable, and do not overwrite
13476 existing torrc files.
13477 - Make OS X log happily to /var/log/tor/tor.log
13480 Changes in version 0.0.9.5 - 2005-02-22
13481 o Bugfixes on 0.0.9.x:
13482 - Fix an assert race at exit nodes when resolve requests fail.
13483 - Stop picking unverified dir mirrors--it only leads to misery.
13484 - Patch from Matt Edman to make NT services work better. Service
13485 support is still not compiled into the executable by default.
13486 - Patch from Dmitri Bely so the Tor service runs better under
13487 the win32 SYSTEM account.
13488 - Make tor-resolve actually work (?) on Win32.
13489 - Fix a sign bug when getrlimit claims to have 4+ billion
13490 file descriptors available.
13491 - Stop refusing to start when bandwidthburst == bandwidthrate.
13492 - When create cells have been on the onion queue more than five
13493 seconds, just send back a destroy and take them off the list.
13496 Changes in version 0.0.9.4 - 2005-02-03
13497 o Bugfixes on 0.0.9:
13498 - Fix an assert bug that took down most of our servers: when
13499 a server claims to have 1 GB of bandwidthburst, don't
13501 - Don't crash as badly if we have spawned the max allowed number
13502 of dnsworkers, or we're out of file descriptors.
13503 - Block more file-sharing ports in the default exit policy.
13504 - MaxConn is now automatically set to the hard limit of max
13505 file descriptors we're allowed (ulimit -n), minus a few for
13507 - Give a clearer message when servers need to raise their
13508 ulimit -n when they start running out of file descriptors.
13509 - SGI Compatibility patches from Jan Schaumann.
13510 - Tolerate a corrupt cached directory better.
13511 - When a dirserver hasn't approved your server, list which one.
13512 - Go into soft hibernation after 95% of the bandwidth is used,
13513 not 99%. This is especially important for daily hibernators who
13514 have a small accounting max. Hopefully it will result in fewer
13515 cut connections when the hard hibernation starts.
13516 - Load-balance better when using servers that claim more than
13517 800kB/s of capacity.
13518 - Make NT services work (experimental, only used if compiled in).
13521 Changes in version 0.0.9.3 - 2005-01-21
13522 o Bugfixes on 0.0.9:
13523 - Backport the cpu use fixes from main branch, so busy servers won't
13524 need as much processor time.
13525 - Work better when we go offline and then come back, or when we
13526 run Tor at boot before the network is up. We do this by
13527 optimistically trying to fetch a new directory whenever an
13528 application request comes in and we think we're offline -- the
13529 human is hopefully a good measure of when the network is back.
13530 - Backport some minimal hidserv bugfixes: keep rend circuits open as
13531 long as you keep using them; actually publish hidserv descriptors
13532 shortly after they change, rather than waiting 20-40 minutes.
13533 - Enable Mac startup script by default.
13534 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
13535 - When you update AllowUnverifiedNodes or FirewallPorts via the
13536 controller's setconf feature, we were always appending, never
13538 - When you update HiddenServiceDir via setconf, it was screwing up
13539 the order of reading the lines, making it fail.
13540 - Do not rewrite a cached directory back to the cache; otherwise we
13541 will think it is recent and not fetch a newer one on startup.
13542 - Workaround for webservers that lie about Content-Encoding: Tor
13543 now tries to autodetect compressed directories and compression
13544 itself. This lets us Proxypass dir fetches through apache.
13547 Changes in version 0.0.9.2 - 2005-01-04
13548 o Bugfixes on 0.0.9 (crashes and asserts):
13549 - Fix an assert on startup when the disk is full and you're logging
13551 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
13552 style address, then we'd crash.
13553 - Fix an assert trigger when the running-routers string we get from
13554 a dirserver is broken.
13555 - Make worker threads start and run on win32. Now win32 servers
13557 - Bandaid (not actually fix, but now it doesn't crash) an assert
13558 where the dns worker dies mysteriously and the main Tor process
13559 doesn't remember anything about the address it was resolving.
13561 o Bugfixes on 0.0.9 (Win32):
13562 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
13563 name out of the warning/assert messages.
13564 - Fix a superficial "unhandled error on read" bug on win32.
13565 - The win32 installer no longer requires a click-through for our
13566 license, since our Free Software license grants rights but does not
13568 - Win32: When connecting to a dirserver fails, try another one
13569 immediately. (This was already working for non-win32 Tors.)
13570 - Stop trying to parse $HOME on win32 when hunting for default
13572 - Make tor-resolve.c work on win32 by calling network_init().
13574 o Bugfixes on 0.0.9 (other):
13575 - Make 0.0.9.x build on Solaris again.
13576 - Due to a fencepost error, we were blowing away the \n when reporting
13577 confvalue items in the controller. So asking for multiple config
13578 values at once couldn't work.
13579 - When listing circuits that are pending on an opening OR connection,
13580 if we're an OR we were listing circuits that *end* at us as
13581 being pending on every listener, dns/cpu worker, etc. Stop that.
13582 - Dirservers were failing to create 'running-routers' or 'directory'
13583 strings if we had more than some threshold of routers. Fix them so
13584 they can handle any number of routers.
13585 - Fix a superficial "Duplicate mark for close" bug.
13586 - Stop checking for clock skew for OR connections, even for servers.
13587 - Fix a fencepost error that was chopping off the last letter of any
13588 nickname that is the maximum allowed nickname length.
13589 - Update URLs in log messages so they point to the new website.
13590 - Fix a potential problem in mangling server private keys while
13591 writing to disk (not triggered yet, as far as we know).
13592 - Include the licenses for other free software we include in Tor,
13593 now that we're shipping binary distributions more regularly.
13596 Changes in version 0.0.9.1 - 2004-12-15
13597 o Bugfixes on 0.0.9:
13598 - Make hibernation actually work.
13599 - Make HashedControlPassword config option work.
13600 - When we're reporting event circuit status to a controller,
13601 don't use the stream status code.
13604 Changes in version 0.0.9 - 2004-12-12
13605 o Bugfixes on 0.0.8.1 (Crashes and asserts):
13606 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
13607 write() call will fail and we handle it there.
13608 - When we run out of disk space, or other log writing error, don't
13609 crash. Just stop logging to that log and continue.
13610 - Fix isspace() and friends so they still make Solaris happy
13611 but also so they don't trigger asserts on win32.
13612 - Fix assert failure on malformed socks4a requests.
13613 - Fix an assert bug where a hidden service provider would fail if
13614 the first hop of his rendezvous circuit was down.
13615 - Better handling of size_t vs int, so we're more robust on 64
13618 o Bugfixes on 0.0.8.1 (Win32):
13619 - Make windows sockets actually non-blocking (oops), and handle
13620 win32 socket errors better.
13621 - Fix parse_iso_time on platforms without strptime (eg win32).
13622 - win32: when being multithreaded, leave parent fdarray open.
13623 - Better handling of winsock includes on non-MSV win32 compilers.
13624 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
13626 - Make unit tests work on win32.
13628 o Bugfixes on 0.0.8.1 (Path selection and streams):
13629 - Calculate timeout for waiting for a connected cell from the time
13630 we sent the begin cell, not from the time the stream started. If
13631 it took a long time to establish the circuit, we would time out
13632 right after sending the begin cell.
13633 - Fix router_compare_addr_to_addr_policy: it was not treating a port
13634 of * as always matching, so we were picking reject *:* nodes as
13635 exit nodes too. Oops.
13636 - When read() failed on a stream, we would close it without sending
13637 back an end. So 'connection refused' would simply be ignored and
13638 the user would get no response.
13639 - Stop a sigpipe: when an 'end' cell races with eof from the app,
13640 we shouldn't hold-open-until-flush if the eof arrived first.
13641 - Let resolve conns retry/expire also, rather than sticking around
13643 - Fix more dns related bugs: send back resolve_failed and end cells
13644 more reliably when the resolve fails, rather than closing the
13645 circuit and then trying to send the cell. Also attach dummy resolve
13646 connections to a circuit *before* calling dns_resolve(), to fix
13647 a bug where cached answers would never be sent in RESOLVED cells.
13649 o Bugfixes on 0.0.8.1 (Circuits):
13650 - Finally fix a bug that's been plaguing us for a year:
13651 With high load, circuit package window was reaching 0. Whenever
13652 we got a circuit-level sendme, we were reading a lot on each
13653 socket, but only writing out a bit. So we would eventually reach
13654 eof. This would be noticed and acted on even when there were still
13655 bytes sitting in the inbuf.
13656 - Use identity comparison, not nickname comparison, to choose which
13657 half of circuit-ID-space each side gets to use. This is needed
13658 because sometimes we think of a router as a nickname, and sometimes
13659 as a hex ID, and we can't predict what the other side will do.
13661 o Bugfixes on 0.0.8.1 (Other):
13662 - Fix a whole slew of memory leaks.
13663 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
13664 - If we are using select, make sure we stay within FD_SETSIZE.
13665 - When poll() is interrupted, we shouldn't believe the revents values.
13666 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
13667 and smartlist_len, which are two major profiling offenders.
13668 - If do_hup fails, actually notice.
13669 - Flush the log file descriptor after we print "Tor opening log file",
13670 so we don't see those messages days later.
13671 - Hidden service operators now correctly handle version 1 style
13672 INTRODUCE1 cells (nobody generates them still, so not a critical
13674 - Handle more errnos from accept() without closing the listener.
13675 Some OpenBSD machines were closing their listeners because
13676 they ran out of file descriptors.
13677 - Some people had wrapped their tor client/server in a script
13678 that would restart it whenever it died. This did not play well
13679 with our "shut down if your version is obsolete" code. Now people
13680 don't fetch a new directory if their local cached version is
13682 - Make our autogen.sh work on ksh as well as bash.
13683 - Better torrc example lines for dirbindaddress and orbindaddress.
13684 - Improved bounds checking on parsed ints (e.g. config options and
13685 the ones we find in directories.)
13686 - Stop using separate defaults for no-config-file and
13687 empty-config-file. Now you have to explicitly turn off SocksPort,
13688 if you don't want it open.
13689 - We were starting to daemonize before we opened our logs, so if
13690 there were any problems opening logs, we would complain to stderr,
13691 which wouldn't work, and then mysteriously exit.
13692 - If a verified OR connects to us before he's uploaded his descriptor,
13693 or we verify him and hup but he still has the original TLS
13694 connection, then conn->nickname is still set like he's unverified.
13696 o Code security improvements, inspired by Ilja:
13697 - tor_snprintf wrapper over snprintf with consistent (though not C99)
13699 - Replace sprintf with tor_snprintf. (I think they were all safe, but
13701 - Replace strcpy/strncpy with strlcpy in more places.
13702 - Avoid strcat; use tor_snprintf or strlcat instead.
13704 o Features (circuits and streams):
13705 - New circuit building strategy: keep a list of ports that we've
13706 used in the past 6 hours, and always try to have 2 circuits open
13707 or on the way that will handle each such port. Seed us with port
13708 80 so web users won't complain that Tor is "slow to start up".
13709 - Make kill -USR1 dump more useful stats about circuits.
13710 - When warning about retrying or giving up, print the address, so
13711 the user knows which one it's talking about.
13712 - If you haven't used a clean circuit in an hour, throw it away,
13713 just to be on the safe side. (This means after 6 hours a totally
13714 unused Tor client will have no circuits open.)
13715 - Support "foo.nickname.exit" addresses, to let Alice request the
13716 address "foo" as viewed by exit node "nickname". Based on a patch
13717 from Geoff Goodell.
13718 - If your requested entry or exit node has advertised bandwidth 0,
13720 - Be more greedy about filling up relay cells -- we try reading again
13721 once we've processed the stuff we read, in case enough has arrived
13722 to fill the last cell completely.
13723 - Refuse application socks connections to port 0.
13724 - Use only 0.0.9pre1 and later servers for resolve cells.
13726 o Features (bandwidth):
13727 - Hibernation: New config option "AccountingMax" lets you
13728 set how many bytes per month (in each direction) you want to
13729 allow your server to consume. Rather than spreading those
13730 bytes out evenly over the month, we instead hibernate for some
13731 of the month and pop up at a deterministic time, work until
13732 the bytes are consumed, then hibernate again. Config option
13733 "MonthlyAccountingStart" lets you specify which day of the month
13734 your billing cycle starts on.
13735 - Implement weekly/monthly/daily accounting: now you specify your
13736 hibernation properties by
13737 AccountingMax N bytes|KB|MB|GB|TB
13738 AccountingStart day|week|month [day] HH:MM
13739 Defaults to "month 1 0:00".
13740 - Let bandwidth and interval config options be specified as 5 bytes,
13741 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
13743 o Features (directories):
13744 - New "router-status" line in directory, to better bind each verified
13745 nickname to its identity key.
13746 - Clients can ask dirservers for /dir.z to get a compressed version
13747 of the directory. Only works for servers running 0.0.9, of course.
13748 - Make clients cache directories and use them to seed their router
13749 lists at startup. This means clients have a datadir again.
13750 - Respond to content-encoding headers by trying to uncompress as
13752 - Clients and servers now fetch running-routers; cache
13753 running-routers; compress running-routers; serve compressed
13755 - Make moria2 advertise a dirport of 80, so people behind firewalls
13756 will be able to get a directory.
13757 - Http proxy support
13758 - Dirservers translate requests for http://%s:%d/x to /x
13759 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
13760 be routed through this host.
13761 - Clients ask for /tor/x rather than /x for new enough dirservers.
13762 This way we can one day coexist peacefully with apache.
13763 - Clients specify a "Host: %s%d" http header, to be compatible
13764 with more proxies, and so running squid on an exit node can work.
13765 - Protect dirservers from overzealous descriptor uploading -- wait
13766 10 seconds after directory gets dirty, before regenerating.
13768 o Features (packages and install):
13769 - Add NSI installer contributed by J Doe.
13770 - Apply NT service patch from Osamu Fujino. Still needs more work.
13771 - Commit VC6 and VC7 workspace/project files.
13772 - Commit a tor.spec for making RPM files, with help from jbash.
13773 - Add contrib/torctl.in contributed by Glenn Fink.
13774 - Make expand_filename handle ~ and ~username.
13775 - Use autoconf to enable largefile support where necessary. Use
13776 ftello where available, since ftell can fail at 2GB.
13777 - Ship src/win32/ in the tarball, so people can use it to build.
13778 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
13781 o Features (ui controller):
13782 - Control interface: a separate program can now talk to your
13783 client/server over a socket, and get/set config options, receive
13784 notifications of circuits and streams starting/finishing/dying,
13785 bandwidth used, etc. The next step is to get some GUIs working.
13786 Let us know if you want to help out. See doc/control-spec.txt .
13787 - Ship a contrib/tor-control.py as an example script to interact
13788 with the control port.
13789 - "tor --hash-password zzyxz" will output a salted password for
13790 use in authenticating to the control interface.
13791 - Implement the control-spec's SAVECONF command, to write your
13792 configuration to torrc.
13793 - Get cookie authentication for the controller closer to working.
13794 - When set_conf changes our server descriptor, upload a new copy.
13795 But don't upload it too often if there are frequent changes.
13797 o Features (config and command-line):
13798 - Deprecate unofficial config option abbreviations, and abbreviations
13799 not on the command line.
13800 - Configuration infrastructure support for warning on obsolete
13802 - Give a slightly more useful output for "tor -h".
13803 - Break DirFetchPostPeriod into:
13804 - DirFetchPeriod for fetching full directory,
13805 - StatusFetchPeriod for fetching running-routers,
13806 - DirPostPeriod for posting server descriptor,
13807 - RendPostPeriod for posting hidden service descriptors.
13808 - New log format in config:
13809 "Log minsev[-maxsev] stdout|stderr|syslog" or
13810 "Log minsev[-maxsev] file /var/foo"
13811 - DirPolicy config option, to let people reject incoming addresses
13812 from their dirserver.
13813 - "tor --list-fingerprint" will list your identity key fingerprint
13815 - Make tor --version --version dump the cvs Id of every file.
13816 - New 'MyFamily nick1,...' config option for a server to
13817 specify other servers that shouldn't be used in the same circuit
13818 with it. Only believed if nick1 also specifies us.
13819 - New 'NodeFamily nick1,nick2,...' config option for a client to
13820 specify nodes that it doesn't want to use in the same circuit.
13821 - New 'Redirectexit pattern address:port' config option for a
13822 server to redirect exit connections, e.g. to a local squid.
13823 - Add "pass" target for RedirectExit, to make it easier to break
13824 out of a sequence of RedirectExit rules.
13825 - Make the dirservers file obsolete.
13826 - Include a dir-signing-key token in directories to tell the
13827 parsing entity which key is being used to sign.
13828 - Remove the built-in bulky default dirservers string.
13829 - New config option "Dirserver %s:%d [fingerprint]", which can be
13830 repeated as many times as needed. If no dirservers specified,
13831 default to moria1,moria2,tor26.
13832 - Make 'Routerfile' config option obsolete.
13833 - Discourage people from setting their dirfetchpostperiod more often
13834 than once per minute.
13836 o Features (other):
13837 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
13838 get back to normal.)
13839 - Accept *:706 (silc) in default exit policy.
13840 - Implement new versioning format for post 0.1.
13841 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
13842 log more informatively.
13843 - Check clock skew for verified servers, but allow unverified
13844 servers and clients to have any clock skew.
13845 - Make sure the hidden service descriptors are at a random offset
13846 from each other, to hinder linkability.
13847 - Clients now generate a TLS cert too, in preparation for having
13848 them act more like real nodes.
13849 - Add a pure-C tor-resolve implementation.
13850 - Use getrlimit and friends to ensure we can reach MaxConn (currently
13851 1024) file descriptors.
13852 - Raise the max dns workers from 50 to 100.
13855 Changes in version 0.0.8.1 - 2004-10-13
13857 - Fix a seg fault that can be triggered remotely for Tor
13858 clients/servers with an open dirport.
13859 - Fix a rare assert trigger, where routerinfos for entries in
13860 our cpath would expire while we're building the path.
13861 - Fix a bug in OutboundBindAddress so it (hopefully) works.
13862 - Fix a rare seg fault for people running hidden services on
13863 intermittent connections.
13864 - Fix a bug in parsing opt keywords with objects.
13865 - Fix a stale pointer assert bug when a stream detaches and
13867 - Fix a string format vulnerability (probably not exploitable)
13868 in reporting stats locally.
13869 - Fix an assert trigger: sometimes launching circuits can fail
13870 immediately, e.g. because too many circuits have failed recently.
13871 - Fix a compile warning on 64 bit platforms.
13874 Changes in version 0.0.8 - 2004-08-25
13876 - Made our unit tests compile again on OpenBSD 3.5, and tor
13877 itself compile again on OpenBSD on a sparc64.
13878 - We were neglecting milliseconds when logging on win32, so
13879 everything appeared to happen at the beginning of each second.
13880 - Check directory signature _before_ you decide whether you're
13881 you're running an obsolete version and should exit.
13882 - Check directory signature _before_ you parse the running-routers
13883 list to decide who's running.
13884 - Check return value of fclose while writing to disk, so we don't
13885 end up with broken files when servers run out of disk space.
13886 - Port it to SunOS 5.9 / Athena
13887 - Fix two bugs in saving onion keys to disk when rotating, so
13888 hopefully we'll get fewer people using old onion keys.
13889 - Remove our mostly unused -- and broken -- hex_encode()
13890 function. Use base16_encode() instead. (Thanks to Timo Lindfors
13891 for pointing out this bug.)
13892 - Only pick and establish intro points after we've gotten a
13894 - Fix assert triggers: if the other side returns an address 0.0.0.0,
13895 don't put it into the client dns cache.
13896 - If a begin failed due to exit policy, but we believe the IP
13897 address should have been allowed, switch that router to exitpolicy
13898 reject *:* until we get our next directory.
13900 o Protocol changes:
13901 - 'Extend' relay cell payloads now include the digest of the
13902 intended next hop's identity key. Now we can verify that we're
13903 extending to the right router, and also extend to routers we
13904 hadn't heard of before.
13907 - Tor nodes can now act as relays (with an advertised ORPort)
13908 without being manually verified by the dirserver operators.
13909 - Uploaded descriptors of unverified routers are now accepted
13910 by the dirservers, and included in the directory.
13911 - Verified routers are listed by nickname in the running-routers
13912 list; unverified routers are listed as "$<fingerprint>".
13913 - We now use hash-of-identity-key in most places rather than
13914 nickname or addr:port, for improved security/flexibility.
13915 - AllowUnverifiedNodes config option to let circuits choose no-name
13916 routers in entry,middle,exit,introduction,rendezvous positions.
13917 Allow middle and rendezvous positions by default.
13918 - When picking unverified routers, skip those with low uptime and/or
13919 low bandwidth, depending on what properties you care about.
13920 - ClientOnly option for nodes that never want to become servers.
13921 - Directory caching.
13922 - "AuthoritativeDir 1" option for the official dirservers.
13923 - Now other nodes (clients and servers) will cache the latest
13924 directory they've pulled down.
13925 - They can enable their DirPort to serve it to others.
13926 - Clients will pull down a directory from any node with an open
13927 DirPort, and check the signature/timestamp correctly.
13928 - Authoritative dirservers now fetch directories from other
13929 authdirservers, to stay better synced.
13930 - Running-routers list tells who's down also, along with noting
13931 if they're verified (listed by nickname) or unverified (listed
13933 - Allow dirservers to serve running-router list separately.
13934 This isn't used yet.
13935 - You can now fetch $DIRURL/running-routers to get just the
13936 running-routers line, not the whole descriptor list. (But
13937 clients don't use this yet.)
13938 - Clients choose nodes proportional to advertised bandwidth.
13939 - Clients avoid using nodes with low uptime as introduction points.
13940 - Handle servers with dynamic IP addresses: don't just replace
13941 options->Address with the resolved one at startup, and
13942 detect our address right before we make a routerinfo each time.
13943 - 'FascistFirewall' option to pick dirservers and ORs on specific
13944 ports; plus 'FirewallPorts' config option to tell FascistFirewall
13945 which ports are open. (Defaults to 80,443)
13946 - Try other dirservers immediately if the one you try is down. This
13947 should tolerate down dirservers better now.
13948 - ORs connect-on-demand to other ORs
13949 - If you get an extend cell to an OR you're not connected to,
13950 connect, handshake, and forward the create cell.
13951 - The authoritative dirservers stay connected to everybody,
13952 and everybody stays connected to 0.0.7 servers, but otherwise
13953 clients/servers expire unused connections after 5 minutes.
13954 - When servers get a sigint, they delay 30 seconds (refusing new
13955 connections) then exit. A second sigint causes immediate exit.
13956 - File and name management:
13957 - Look for .torrc if no CONFDIR "torrc" is found.
13958 - If no datadir is defined, then choose, make, and secure ~/.tor
13960 - If torrc not found, exitpolicy reject *:*.
13961 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
13962 - If no nickname is defined, derive default from hostname.
13963 - Rename secret key files, e.g. identity.key -> secret_id_key,
13964 to discourage people from mailing their identity key to tor-ops.
13965 - Refuse to build a circuit before the directory has arrived --
13966 it won't work anyway, since you won't know the right onion keys
13968 - Parse tor version numbers so we can do an is-newer-than check
13969 rather than an is-in-the-list check.
13970 - New socks command 'resolve', to let us shim gethostbyname()
13972 - A 'tor_resolve' script to access the socks resolve functionality.
13973 - A new socks-extensions.txt doc file to describe our
13974 interpretation and extensions to the socks protocols.
13975 - Add a ContactInfo option, which gets published in descriptor.
13976 - Write tor version at the top of each log file
13977 - New docs in the tarball:
13979 - Document that you should proxy your SSL traffic too.
13980 - Log a warning if the user uses an unsafe socks variant, so people
13981 are more likely to learn about privoxy or socat.
13982 - Log a warning if you're running an unverified server, to let you
13983 know you might want to get it verified.
13984 - Change the default exit policy to reject the default edonkey,
13985 kazaa, gnutella ports.
13986 - Add replace_file() to util.[ch] to handle win32's rename().
13987 - Publish OR uptime in descriptor (and thus in directory) too.
13988 - Remember used bandwidth (both in and out), and publish 15-minute
13989 snapshots for the past day into our descriptor.
13990 - Be more aggressive about trying to make circuits when the network
13991 has changed (e.g. when you unsuspend your laptop).
13992 - Check for time skew on http headers; report date in response to
13994 - If the entrynode config line has only one node, don't pick it as
13996 - Add strict{entry|exit}nodes config options. If set to 1, then
13997 we refuse to build circuits that don't include the specified entry
13999 - OutboundBindAddress config option, to bind to a specific
14000 IP address for outgoing connect()s.
14001 - End truncated log entries (e.g. directories) with "[truncated]".
14004 Changes in version 0.0.7.3 - 2004-08-12
14005 o Stop dnsworkers from triggering an assert failure when you
14006 ask them to resolve the host "".
14009 Changes in version 0.0.7.2 - 2004-07-07
14010 o A better fix for the 0.0.0.0 problem, that will hopefully
14011 eliminate the remaining related assertion failures.
14014 Changes in version 0.0.7.1 - 2004-07-04
14015 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14016 since internally we use 0.0.0.0 to signify "not yet resolved".
14019 Changes in version 0.0.7 - 2004-06-07
14020 o Fixes for crashes and other obnoxious bugs:
14021 - Fix an epipe bug: sometimes when directory connections failed
14022 to connect, we would give them a chance to flush before closing
14024 - When we detached from a circuit because of resolvefailed, we
14025 would immediately try the same circuit twice more, and then
14026 give up on the resolve thinking we'd tried three different
14028 - Limit the number of intro circuits we'll attempt to build for a
14029 hidden service per 15-minute period.
14030 - Check recommended-software string *early*, before actually parsing
14031 the directory. Thus we can detect an obsolete version and exit,
14032 even if the new directory format doesn't parse.
14033 o Fixes for security bugs:
14034 - Remember which nodes are dirservers when you startup, and if a
14035 random OR enables his dirport, don't automatically assume he's
14036 a trusted dirserver.
14038 - Directory connections were asking the wrong poll socket to
14039 start writing, and not asking themselves to start writing.
14040 - When we detached from a circuit because we sent a begin but
14041 didn't get a connected, we would use it again the first time;
14042 but after that we would correctly switch to a different one.
14043 - Stop warning when the first onion decrypt attempt fails; they
14044 will sometimes legitimately fail now that we rotate keys.
14045 - Override unaligned-access-ok check when $host_cpu is ia64 or
14046 arm. Apparently they allow it but the kernel whines.
14047 - Dirservers try to reconnect periodically too, in case connections
14049 - Fix some memory leaks in directory servers.
14050 - Allow backslash in Win32 filenames.
14051 - Made Tor build complain-free on FreeBSD, hopefully without
14052 breaking other BSD builds. We'll see.
14053 - Check directory signatures based on name of signer, not on whom
14054 we got the directory from. This will let us cache directories more
14056 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14059 - Doxygen markup on all functions and global variables.
14060 - Make directory functions update routerlist, not replace it. So
14061 now directory disagreements are not so critical a problem.
14062 - Remove the upper limit on number of descriptors in a dirserver's
14063 directory (not that we were anywhere close).
14064 - Allow multiple logfiles at different severity ranges.
14065 - Allow *BindAddress to specify ":port" rather than setting *Port
14066 separately. Allow multiple instances of each BindAddress config
14067 option, so you can bind to multiple interfaces if you want.
14068 - Allow multiple exit policy lines, which are processed in order.
14069 Now we don't need that huge line with all the commas in it.
14070 - Enable accept/reject policies on SOCKS connections, so you can bind
14071 to 0.0.0.0 but still control who can use your OP.
14072 - Updated the man page to reflect these features.
14075 Changes in version 0.0.6.2 - 2004-05-16
14076 o Our integrity-checking digest was checking only the most recent cell,
14077 not the previous cells like we'd thought.
14078 Thanks to Stefan Mark for finding the flaw!
14081 Changes in version 0.0.6.1 - 2004-05-06
14082 o Fix two bugs in our AES counter-mode implementation (this affected
14083 onion-level stream encryption, but not TLS-level). It turns
14084 out we were doing something much more akin to a 16-character
14085 polyalphabetic cipher. Oops.
14086 Thanks to Stefan Mark for finding the flaw!
14087 o Retire moria3 as a directory server, and add tor26 as a directory
14091 Changes in version 0.0.6 - 2004-05-02
14093 - Hidden services and rendezvous points are implemented. Go to
14094 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
14095 hidden services. (This only works via a socks4a proxy such as
14096 Privoxy, and currently it's quite slow.)
14097 - We now rotate link (tls context) keys and onion keys.
14098 - CREATE cells now include oaep padding, so you can tell
14099 if you decrypted them correctly.
14100 - Retry stream correctly when we fail to connect because of
14101 exit-policy-reject (should try another) or can't-resolve-address.
14102 - When we hup a dirserver and we've *removed* a server from the
14103 approved-routers list, now we remove that server from the
14104 in-memory directories too.
14105 - Add bandwidthburst to server descriptor.
14106 - Directories now say which dirserver signed them.
14107 - Use a tor_assert macro that logs failed assertions too.
14108 - Since we don't support truncateds much, don't bother sending them;
14109 just close the circ.
14110 - Fetch randomness from /dev/urandom better (not via fopen/fread)
14111 - Better debugging for tls errors
14112 - Set Content-Type on the directory and hidserv descriptor.
14113 - Remove IVs from cipher code, since AES-ctr has none.
14115 - Fix an assert trigger for exit nodes that's been plaguing us since
14116 the days of 0.0.2prexx (thanks weasel!)
14117 - Fix a bug where we were closing tls connections intermittently.
14118 It turns out openssl keeps its errors around -- so if an error
14119 happens, and you don't ask about it, and then another openssl
14120 operation happens and succeeds, and you ask if there was an error,
14121 it tells you about the first error.
14122 - Fix a bug that's been lurking since 27 may 03 (!)
14123 When passing back a destroy cell, we would use the wrong circ id.
14124 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
14125 - Some versions of openssl have an SSL_pending function that erroneously
14126 returns bytes when there is a non-application record pending.
14127 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
14128 o We were using an array of length zero in a few places.
14129 o Win32's gethostbyname can't resolve an IP to an IP.
14130 o Win32's close can't close a socket.
14131 o Handle windows socket errors correctly.
14133 - check for <sys/limits.h> so we build on FreeBSD again, and
14134 <machine/limits.h> for NetBSD.
14137 Changes in version 0.0.5 - 2004-03-30
14138 o Install torrc as torrc.sample -- we no longer clobber your
14140 o Fix mangled-state bug in directory fetching (was causing sigpipes).
14141 o Only build circuits after we've fetched the directory: clients were
14142 using only the directory servers before they'd fetched a directory.
14143 This also means longer startup time; so it goes.
14144 o Fix an assert trigger where an OP would fail to handshake, and we'd
14145 expect it to have a nickname.
14146 o Work around a tsocks bug: do a socks reject when AP connection dies
14147 early, else tsocks goes into an infinite loop.
14148 o Hold socks connection open until reply is flushed (if possible)
14149 o Make exit nodes resolve IPs to IPs immediately, rather than asking
14150 the dns farm to do it.
14151 o Fix c99 aliasing warnings in rephist.c
14152 o Don't include server descriptors that are older than 24 hours in the
14154 o Give socks 'reject' replies their whole 15s to attempt to flush,
14155 rather than seeing the 60s timeout and assuming the flush had failed.
14156 o Clean automake droppings from the cvs repository
14157 o Add in a 'notice' log level for things the operator should hear
14158 but that aren't warnings
14161 Changes in version 0.0.4 - 2004-03-26
14162 o When connecting to a dirserver or OR and the network is down,
14166 Changes in version 0.0.3 - 2004-03-26
14167 o Warn and fail if server chose a nickname with illegal characters
14168 o Port to Solaris and Sparc:
14169 - include missing header fcntl.h
14170 - have autoconf find -lsocket -lnsl automatically
14171 - deal with hardware word alignment
14172 - make uname() work (solaris has a different return convention)
14173 - switch from using signal() to sigaction()
14174 o Preliminary work on reputation system:
14175 - Keep statistics on success/fail of connect attempts; they're published
14176 by kill -USR1 currently.
14177 - Add a RunTesting option to try to learn link state by creating test
14178 circuits, even when SocksPort is off.
14179 - Remove unused open circuits when there are too many.
14182 Changes in version 0.0.2 - 2004-03-19
14183 - Include strlcpy and strlcat for safer string ops
14184 - define INADDR_NONE so we compile (but still not run) on solaris
14187 Changes in version 0.0.2pre27 - 2004-03-14
14189 - Allow internal tor networks (we were rejecting internal IPs,
14190 now we allow them if they're set explicitly).
14191 - And fix a few endian issues.
14194 Changes in version 0.0.2pre26 - 2004-03-14
14196 - If a stream times out after 15s without a connected cell, don't
14197 try that circuit again: try a new one.
14198 - Retry streams at most 4 times. Then give up.
14199 - When a dirserver gets a descriptor from an unknown router, it
14200 logs its fingerprint (so the dirserver operator can choose to
14201 accept it even without mail from the server operator).
14202 - Inform unapproved servers when we reject their descriptors.
14203 - Make tor build on Windows again. It works as a client, who knows
14205 - Clearer instructions in the torrc for how to set up a server.
14206 - Be more efficient about reading fd's when our global token bucket
14207 (used for rate limiting) becomes empty.
14209 - Stop asserting that computers always go forward in time. It's
14211 - When we sent a cell (e.g. destroy) and then marked an OR connection
14212 expired, we might close it before finishing a flush if the other
14213 side isn't reading right then.
14214 - Don't allow dirservers to start if they haven't defined
14215 RecommendedVersions
14216 - We were caching transient dns failures. Oops.
14217 - Prevent servers from publishing an internal IP as their address.
14218 - Address a strcat vulnerability in circuit.c
14221 Changes in version 0.0.2pre25 - 2004-03-04
14223 - Put the OR's IP in its router descriptor, not its fqdn. That way
14224 we'll stop being stalled by gethostbyname for nodes with flaky dns,
14227 - If the user typed in an address that didn't resolve, the server
14231 Changes in version 0.0.2pre24 - 2004-03-03
14233 - Fix an assertion failure in dns.c, where we were trying to dequeue
14234 a pending dns resolve even if it wasn't pending
14235 - Fix a spurious socks5 warning about still trying to write after the
14236 connection is finished.
14237 - Hold certain marked_for_close connections open until they're finished
14238 flushing, rather than losing bytes by closing them too early.
14239 - Correctly report the reason for ending a stream
14240 - Remove some duplicate calls to connection_mark_for_close
14241 - Put switch_id and start_daemon earlier in the boot sequence, so it
14242 will actually try to chdir() to options.DataDirectory
14243 - Make 'make test' exit(1) if a test fails; fix some unit tests
14244 - Make tor fail when you use a config option it doesn't know about,
14245 rather than warn and continue.
14246 - Make --version work
14247 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
14250 Changes in version 0.0.2pre23 - 2004-02-29
14252 - Print a statement when the first circ is finished, so the user
14253 knows it's working.
14254 - If a relay cell is unrecognized at the end of the circuit,
14255 send back a destroy. (So attacks to mutate cells are more
14257 - New config option 'excludenodes' to avoid certain nodes for circuits.
14258 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
14259 so you can collect coredumps there.
14261 - Fix a bug in tls flushing where sometimes data got wedged and
14262 didn't flush until more data got sent. Hopefully this bug was
14263 a big factor in the random delays we were seeing.
14264 - Make 'connected' cells include the resolved IP, so the client
14265 dns cache actually gets populated.
14266 - Disallow changing from ORPort=0 to ORPort>0 on hup.
14267 - When we time-out on a stream and detach from the circuit, send an
14268 end cell down it first.
14269 - Only warn about an unknown router (in exitnodes, entrynodes,
14270 excludenodes) after we've fetched a directory.
14273 Changes in version 0.0.2pre22 - 2004-02-26
14275 - Servers publish less revealing uname information in descriptors.
14276 - More memory tracking and assertions, to crash more usefully when
14278 - If the default torrc isn't there, just use some default defaults.
14279 Plus provide an internal dirservers file if they don't have one.
14280 - When the user tries to use Tor as an http proxy, give them an http
14281 501 failure explaining that we're a socks proxy.
14282 - Dump a new router.desc on hup, to help confused people who change
14283 their exit policies and then wonder why router.desc doesn't reflect
14285 - Clean up the generic tor.sh init script that we ship with.
14287 - If the exit stream is pending on the resolve, and a destroy arrives,
14288 then the stream wasn't getting removed from the pending list. I
14289 think this was the one causing recent server crashes.
14290 - Use a more robust poll on OSX 10.3, since their poll is flaky.
14291 - When it couldn't resolve any dirservers, it was useless from then on.
14292 Now it reloads the RouterFile (or default dirservers) if it has no
14294 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
14295 many users don't even *have* a /usr/local/sbin/.
14298 Changes in version 0.0.2pre21 - 2004-02-18
14300 - There's a ChangeLog file that actually reflects the changelog.
14301 - There's a 'torify' wrapper script, with an accompanying
14302 tor-tsocks.conf, that simplifies the process of using tsocks for
14303 tor. It even has a man page.
14304 - The tor binary gets installed to sbin rather than bin now.
14305 - Retry streams where the connected cell hasn't arrived in 15 seconds
14306 - Clean up exit policy handling -- get the default out of the torrc,
14307 so we can update it without forcing each server operator to fix
14309 - Allow imaps and pop3s in default exit policy
14311 - Prevent picking middleman nodes as the last node in the circuit
14314 Changes in version 0.0.2pre20 - 2004-01-30
14316 - We now have a deb package, and it's in debian unstable. Go to
14317 it, apt-getters. :)
14318 - I've split the TotalBandwidth option into BandwidthRate (how many
14319 bytes per second you want to allow, long-term) and
14320 BandwidthBurst (how many bytes you will allow at once before the cap
14321 kicks in). This better token bucket approach lets you, say, set
14322 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
14323 performance while not exceeding your monthly bandwidth quota.
14324 - Push out a tls record's worth of data once you've got it, rather
14325 than waiting until you've read everything waiting to be read. This
14326 may improve performance by pipelining better. We'll see.
14327 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
14328 from failed circuits (if they haven't been connected yet) and attach
14330 - Expire old streams that haven't managed to connect. Some day we'll
14331 have them reattach to new circuits instead.
14334 - Fix several memory leaks that were causing servers to become bloated
14336 - Fix a few very rare assert triggers. A few more remain.
14337 - Setuid to User _before_ complaining about running as root.
14340 Changes in version 0.0.2pre19 - 2004-01-07
14342 - Fix deadlock condition in dns farm. We were telling a child to die by
14343 closing the parent's file descriptor to him. But newer children were
14344 inheriting the open file descriptor from the parent, and since they
14345 weren't closing it, the socket never closed, so the child never read
14346 eof, so he never knew to exit. Similarly, dns workers were holding
14347 open other sockets, leading to all sorts of chaos.
14348 - New cleaner daemon() code for forking and backgrounding.
14349 - If you log to a file, it now prints an entry at the top of the
14350 logfile so you know it's working.
14351 - The onionskin challenge length was 30 bytes longer than necessary.
14352 - Started to patch up the spec so it's not quite so out of date.
14355 Changes in version 0.0.2pre18 - 2004-01-02
14357 - Fix endian issues with the 'integrity' field in the relay header.
14358 - Fix a potential bug where connections in state
14359 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
14362 Changes in version 0.0.2pre17 - 2003-12-30
14364 - Made --debuglogfile (or any second log file, actually) work.
14365 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
14366 adversary could force us into an infinite loop.
14369 - Each onionskin handshake now includes a hash of the computed key,
14370 to prove the server's identity and help perfect forward secrecy.
14371 - Changed cell size from 256 to 512 bytes (working toward compatibility
14373 - Changed cell length to 2 bytes, and moved it to the relay header.
14374 - Implemented end-to-end integrity checking for the payloads of
14376 - Separated streamid from 'recognized' (otherwise circuits will get
14377 messed up when we try to have streams exit from the middle). We
14378 use the integrity-checking to confirm that a cell is addressed to
14380 - Randomize the initial circid and streamid values, so an adversary who
14381 breaks into a node can't learn how many circuits or streams have
14385 Changes in version 0.0.2pre16 - 2003-12-14
14387 - Fixed a bug that made HUP trigger an assert
14388 - Fixed a bug where a circuit that immediately failed wasn't being
14389 counted as a failed circuit in counting retries.
14392 - Now we close the circuit when we get a truncated cell: otherwise we're
14393 open to an anonymity attack where a bad node in the path truncates
14394 the circuit and then we open streams at him.
14395 - Add port ranges to exit policies
14396 - Add a conservative default exit policy
14397 - Warn if you're running tor as root
14398 - on HUP, retry OR connections and close/rebind listeners
14399 - options.EntryNodes: try these nodes first when picking the first node
14400 - options.ExitNodes: if your best choices happen to include any of
14401 your preferred exit nodes, you choose among just those preferred
14403 - options.ExcludedNodes: nodes that are never picked in path building
14406 Changes in version 0.0.2pre15 - 2003-12-03
14407 o Robustness and bugfixes:
14408 - Sometimes clients would cache incorrect DNS resolves, which would
14409 really screw things up.
14410 - An OP that goes offline would slowly leak all its sockets and stop
14412 - A wide variety of bugfixes in exit node selection, exit policy
14413 handling, and processing pending streams when a new circuit is
14415 - Pick nodes for a path only from those the directory says are up
14416 - Choose randomly from all running dirservers, not always the first one
14417 - Increase allowed http header size for directory fetch.
14418 - Stop writing to stderr (if we're daemonized it will be closed).
14419 - Enable -g always, so cores will be more useful to me.
14420 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
14423 - Wrote a man page. It lists commonly used options.
14426 - Change default loglevel to warn.
14427 - Make PidFile default to null rather than littering in your CWD.
14428 - OnionRouter config option is now obsolete. Instead it just checks
14430 - Moved to a single unified torrc file for both clients and servers.
14433 Changes in version 0.0.2pre14 - 2003-11-29
14434 o Robustness and bugfixes:
14435 - Force the admin to make the DataDirectory himself
14436 - to get ownership/permissions right
14437 - so clients no longer make a DataDirectory and then never use it
14438 - fix bug where a client who was offline for 45 minutes would never
14439 pull down a directory again
14440 - fix (or at least hide really well) the dns assert bug that was
14441 causing server crashes
14442 - warnings and improved robustness wrt clockskew for certs
14443 - use the native daemon(3) to daemonize, when available
14444 - exit if bind() fails
14445 - exit if neither socksport nor orport is defined
14446 - include our own tor_timegm (Win32 doesn't have its own)
14447 - bugfix for win32 with lots of connections
14448 - fix minor bias in PRNG
14449 - make dirserver more robust to corrupt cached directory
14452 - Wrote the design document (woo)
14454 o Circuit building and exit policies:
14455 - Circuits no longer try to use nodes that the directory has told them
14457 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
14458 bitcounts (18.0.0.0/8).
14459 - Make AP connections standby for a circuit if no suitable circuit
14460 exists, rather than failing
14461 - Circuits choose exit node based on addr/port, exit policies, and
14462 which AP connections are standing by
14463 - Bump min pathlen from 2 to 3
14464 - Relay end cells have a payload to describe why the stream ended.
14465 - If the stream failed because of exit policy, try again with a new
14467 - Clients have a dns cache to remember resolved addresses.
14468 - Notice more quickly when we have no working circuits
14471 - APPort is now called SocksPort
14472 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
14474 - RecommendedVersions is now a config variable rather than
14475 hardcoded (for dirservers)
14476 - Reloads config on HUP
14477 - Usage info on -h or --help
14478 - If you set User and Group config vars, it'll setu/gid to them.
14480 Changes in version 0.0.2pre13 - 2003-10-19
14481 o General stability:
14482 - SSL_write no longer fails when it returns WANTWRITE and the number
14483 of bytes in the buf has changed by the next SSL_write call.
14484 - Fix segfault fetching directory when network is down
14485 - Fix a variety of minor memory leaks
14486 - Dirservers reload the fingerprints file on HUP, so I don't have
14487 to take down the network when I approve a new router
14488 - Default server config file has explicit Address line to specify fqdn
14491 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
14492 - Make listener connections not ever alloc bufs
14494 o Autoconf improvements:
14495 - don't clobber an external CFLAGS in ./configure
14496 - Make install now works
14497 - create var/lib/tor on make install
14498 - autocreate a tor.sh initscript to help distribs
14499 - autocreate the torrc and sample-server-torrc with correct paths
14501 o Log files and Daemonizing now work:
14502 - If --DebugLogFile is specified, log to it at -l debug
14503 - If --LogFile is specified, use it instead of commandline
14504 - If --RunAsDaemon is set, tor forks and backgrounds on startup