1 Changes in version 0.3.2.6-alpha - 2017-12-01
2 This version of Tor is the latest in the 0.3.2 alpha series. It
3 includes fixes for several important security issues. All Tor users
4 should upgrade to this release, or to one of the other releases coming
7 o Major bugfixes (security):
8 - Fix a denial of service bug where an attacker could use a
9 malformed directory object to cause a Tor instance to pause while
10 OpenSSL would try to read a passphrase from the terminal. (Tor
11 instances run without a terminal, which is the case for most Tor
12 packages, are not impacted.) Fixes bug 24246; bugfix on every
13 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
14 Found by OSS-Fuzz as testcase 6360145429790720.
15 - Fix a denial of service issue where an attacker could crash a
16 directory authority using a malformed router descriptor. Fixes bug
17 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
19 - When checking for replays in the INTRODUCE1 cell data for a
20 (legacy) onion service, correctly detect replays in the RSA-
21 encrypted part of the cell. We were previously checking for
22 replays on the entire cell, but those can be circumvented due to
23 the malleability of Tor's legacy hybrid encryption. This fix helps
24 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
25 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
28 o Major bugfixes (security, onion service v2):
29 - Fix a use-after-free error that could crash v2 Tor onion services
30 when they failed to open circuits while expiring introduction
31 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
32 also tracked as TROVE-2017-013 and CVE-2017-8823.
34 o Major bugfixes (security, relay):
35 - When running as a relay, make sure that we never build a path
36 through ourselves, even in the case where we have somehow lost the
37 version of our descriptor appearing in the consensus. Fixes part
38 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
39 as TROVE-2017-012 and CVE-2017-8822.
40 - When running as a relay, make sure that we never choose ourselves
41 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
42 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
44 o Minor feature (relay statistics):
45 - Change relay bandwidth reporting stats interval from 4 hours to 24
46 hours in order to reduce the efficiency of guard discovery
47 attacks. Fixes ticket 23856.
49 o Minor features (directory authority):
50 - Add an IPv6 address for the "bastet" directory authority. Closes
53 o Minor bugfixes (client):
54 - By default, do not enable storage of client-side DNS values. These
55 values were unused by default previously, but they should not have
56 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
59 Changes in version 0.3.1.9 - 2017-12-01:
60 Tor 0.3.1.9 backports important security and stability fixes from the
61 0.3.2 development series. All Tor users should upgrade to this
62 release, or to another of the releases coming out today.
64 o Major bugfixes (security, backport from 0.3.2.6-alpha):
65 - Fix a denial of service bug where an attacker could use a
66 malformed directory object to cause a Tor instance to pause while
67 OpenSSL would try to read a passphrase from the terminal. (Tor
68 instances run without a terminal, which is the case for most Tor
69 packages, are not impacted.) Fixes bug 24246; bugfix on every
70 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
71 Found by OSS-Fuzz as testcase 6360145429790720.
72 - Fix a denial of service issue where an attacker could crash a
73 directory authority using a malformed router descriptor. Fixes bug
74 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
76 - When checking for replays in the INTRODUCE1 cell data for a
77 (legacy) onion service, correctly detect replays in the RSA-
78 encrypted part of the cell. We were previously checking for
79 replays on the entire cell, but those can be circumvented due to
80 the malleability of Tor's legacy hybrid encryption. This fix helps
81 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
82 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
85 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
86 - Fix a use-after-free error that could crash v2 Tor onion services
87 when they failed to open circuits while expiring introduction
88 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
89 also tracked as TROVE-2017-013 and CVE-2017-8823.
91 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
92 - When running as a relay, make sure that we never build a path
93 through ourselves, even in the case where we have somehow lost the
94 version of our descriptor appearing in the consensus. Fixes part
95 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
96 as TROVE-2017-012 and CVE-2017-8822.
97 - When running as a relay, make sure that we never choose ourselves
98 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
99 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
101 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
102 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
103 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
104 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
105 identifying and finding a workaround to this bug and to Moritz,
106 Arthur Edelstein, and Roger for helping to track it down and
109 o Minor features (bridge):
110 - Bridges now include notice in their descriptors that they are
111 bridges, and notice of their distribution status, based on their
112 publication settings. Implements ticket 18329. For more fine-
113 grained control of how a bridge is distributed, upgrade to 0.3.2.x
116 o Minor features (directory authority, backport from 0.3.2.6-alpha):
117 - Add an IPv6 address for the "bastet" directory authority. Closes
120 o Minor features (geoip):
121 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
124 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
125 - Avoid unnecessary calls to directory_fetches_from_authorities() on
126 relays, to prevent spurious address resolutions and descriptor
127 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
128 bugfix on in 0.2.8.1-alpha.
130 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
131 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
132 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
134 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
135 - When a circuit is marked for close, do not attempt to package any
136 cells for channels on that circuit. Previously, we would detect
137 this condition lower in the call stack, when we noticed that the
138 circuit had no attached channel, and log an annoying message.
139 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
141 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
142 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
143 so it matches dir-spec.txt. Fixes bug 24262; bugfix
146 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
147 - Avoid a crash when transitioning from client mode to bridge mode.
148 Previously, we would launch the worker threads whenever our
149 "public server" mode changed, but not when our "server" mode
150 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
153 Changes in version 0.3.0.13 - 2017-12-01
154 Tor 0.3.0.13 backports important security and stability bugfixes from
155 later Tor releases. All Tor users should upgrade to this release, or
156 to another of the releases coming out today.
158 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
159 2018. If you need a release with long-term support, please stick with
160 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
162 o Major bugfixes (security, backport from 0.3.2.6-alpha):
163 - Fix a denial of service bug where an attacker could use a
164 malformed directory object to cause a Tor instance to pause while
165 OpenSSL would try to read a passphrase from the terminal. (Tor
166 instances run without a terminal, which is the case for most Tor
167 packages, are not impacted.) Fixes bug 24246; bugfix on every
168 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
169 Found by OSS-Fuzz as testcase 6360145429790720.
170 - Fix a denial of service issue where an attacker could crash a
171 directory authority using a malformed router descriptor. Fixes bug
172 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
174 - When checking for replays in the INTRODUCE1 cell data for a
175 (legacy) onion service, correctly detect replays in the RSA-
176 encrypted part of the cell. We were previously checking for
177 replays on the entire cell, but those can be circumvented due to
178 the malleability of Tor's legacy hybrid encryption. This fix helps
179 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
180 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
183 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
184 - Fix a use-after-free error that could crash v2 Tor onion services
185 when they failed to open circuits while expiring introduction
186 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
187 also tracked as TROVE-2017-013 and CVE-2017-8823.
189 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
190 - When running as a relay, make sure that we never build a path
191 through ourselves, even in the case where we have somehow lost the
192 version of our descriptor appearing in the consensus. Fixes part
193 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
194 as TROVE-2017-012 and CVE-2017-8822.
195 - When running as a relay, make sure that we never choose ourselves
196 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
197 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
199 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
200 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
201 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
202 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
203 identifying and finding a workaround to this bug and to Moritz,
204 Arthur Edelstein, and Roger for helping to track it down and
207 o Minor features (security, windows, backport from 0.3.1.1-alpha):
208 - Enable a couple of pieces of Windows hardening: one
209 (HeapEnableTerminationOnCorruption) that has been on-by-default
210 since Windows 8, and unavailable before Windows 7; and one
211 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
212 affect us, but shouldn't do any harm. Closes ticket 21953.
214 o Minor features (bridge, backport from 0.3.1.9):
215 - Bridges now include notice in their descriptors that they are
216 bridges, and notice of their distribution status, based on their
217 publication settings. Implements ticket 18329. For more fine-
218 grained control of how a bridge is distributed, upgrade to 0.3.2.x
221 o Minor features (directory authority, backport from 0.3.2.6-alpha):
222 - Add an IPv6 address for the "bastet" directory authority. Closes
225 o Minor features (geoip):
226 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
229 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
230 - Avoid unnecessary calls to directory_fetches_from_authorities() on
231 relays, to prevent spurious address resolutions and descriptor
232 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
233 bugfix on in 0.2.8.1-alpha.
235 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
236 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
237 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
239 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
240 - When a circuit is marked for close, do not attempt to package any
241 cells for channels on that circuit. Previously, we would detect
242 this condition lower in the call stack, when we noticed that the
243 circuit had no attached channel, and log an annoying message.
244 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
246 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
247 - Avoid a crash when transitioning from client mode to bridge mode.
248 Previously, we would launch the worker threads whenever our
249 "public server" mode changed, but not when our "server" mode
250 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
252 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
253 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
254 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
257 Changes in version 0.2.9.14 - 2017-12-01
258 Tor 0.3.0.13 backports important security and stability bugfixes from
259 later Tor releases. All Tor users should upgrade to this release, or
260 to another of the releases coming out today.
262 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
263 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
264 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
265 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
266 identifying and finding a workaround to this bug and to Moritz,
267 Arthur Edelstein, and Roger for helping to track it down and
270 o Major bugfixes (security, backport from 0.3.2.6-alpha):
271 - Fix a denial of service bug where an attacker could use a
272 malformed directory object to cause a Tor instance to pause while
273 OpenSSL would try to read a passphrase from the terminal. (Tor
274 instances run without a terminal, which is the case for most Tor
275 packages, are not impacted.) Fixes bug 24246; bugfix on every
276 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
277 Found by OSS-Fuzz as testcase 6360145429790720.
278 - Fix a denial of service issue where an attacker could crash a
279 directory authority using a malformed router descriptor. Fixes bug
280 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
282 - When checking for replays in the INTRODUCE1 cell data for a
283 (legacy) onion service, correctly detect replays in the RSA-
284 encrypted part of the cell. We were previously checking for
285 replays on the entire cell, but those can be circumvented due to
286 the malleability of Tor's legacy hybrid encryption. This fix helps
287 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
288 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
291 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
292 - Fix a use-after-free error that could crash v2 Tor onion services
293 when they failed to open circuits while expiring introduction
294 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
295 also tracked as TROVE-2017-013 and CVE-2017-8823.
297 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
298 - When running as a relay, make sure that we never build a path
299 through ourselves, even in the case where we have somehow lost the
300 version of our descriptor appearing in the consensus. Fixes part
301 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
302 as TROVE-2017-012 and CVE-2017-8822.
304 o Minor features (bridge, backport from 0.3.1.9):
305 - Bridges now include notice in their descriptors that they are
306 bridges, and notice of their distribution status, based on their
307 publication settings. Implements ticket 18329. For more fine-
308 grained control of how a bridge is distributed, upgrade to 0.3.2.x
311 o Minor features (directory authority, backport from 0.3.2.6-alpha):
312 - Add an IPv6 address for the "bastet" directory authority. Closes
315 o Minor features (geoip):
316 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
319 o Minor features (security, windows, backport from 0.3.1.1-alpha):
320 - Enable a couple of pieces of Windows hardening: one
321 (HeapEnableTerminationOnCorruption) that has been on-by-default
322 since Windows 8, and unavailable before Windows 7; and one
323 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
324 affect us, but shouldn't do any harm. Closes ticket 21953.
326 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
327 - Avoid unnecessary calls to directory_fetches_from_authorities() on
328 relays, to prevent spurious address resolutions and descriptor
329 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
330 bugfix on in 0.2.8.1-alpha.
332 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
333 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
334 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
336 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
337 - When a circuit is marked for close, do not attempt to package any
338 cells for channels on that circuit. Previously, we would detect
339 this condition lower in the call stack, when we noticed that the
340 circuit had no attached channel, and log an annoying message.
341 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
343 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
344 - Avoid a crash when transitioning from client mode to bridge mode.
345 Previously, we would launch the worker threads whenever our
346 "public server" mode changed, but not when our "server" mode
347 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
349 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
350 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
351 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
354 Changes in version 0.2.8.17 - 2017-12-01
355 Tor 0.2.8.17 backports important security and stability bugfixes from
356 later Tor releases. All Tor users should upgrade to this release, or
357 to another of the releases coming out today.
359 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
360 2018. If you need a release with long-term support, please upgrade with
361 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
363 o Major bugfixes (security, backport from 0.3.2.6-alpha):
364 - Fix a denial of service bug where an attacker could use a
365 malformed directory object to cause a Tor instance to pause while
366 OpenSSL would try to read a passphrase from the terminal. (Tor
367 instances run without a terminal, which is the case for most Tor
368 packages, are not impacted.) Fixes bug 24246; bugfix on every
369 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
370 Found by OSS-Fuzz as testcase 6360145429790720.
371 - When checking for replays in the INTRODUCE1 cell data for a
372 (legacy) onion service, correctly detect replays in the RSA-
373 encrypted part of the cell. We were previously checking for
374 replays on the entire cell, but those can be circumvented due to
375 the malleability of Tor's legacy hybrid encryption. This fix helps
376 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
377 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
380 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
381 - Fix a use-after-free error that could crash v2 Tor onion services
382 when they failed to open circuits while expiring introduction
383 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
384 also tracked as TROVE-2017-013 and CVE-2017-8823.
386 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
387 - When running as a relay, make sure that we never build a path through
388 ourselves, even in the case where we have somehow lost the version of
389 our descriptor appearing in the consensus. Fixes part of bug 21534;
390 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
393 o Minor features (bridge, backport from 0.3.1.9):
394 - Bridges now include notice in their descriptors that they are
395 bridges, and notice of their distribution status, based on their
396 publication settings. Implements ticket 18329. For more fine-
397 grained control of how a bridge is distributed, upgrade to 0.3.2.x
400 o Minor features (directory authority, backport from 0.3.2.6-alpha):
401 - Add an IPv6 address for the "bastet" directory authority. Closes
404 o Minor features (geoip):
405 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
408 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
409 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
410 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
413 Changes in version 0.2.5.16 - 2017-12-01
414 Tor 0.2.5.13 backports important security and stability bugfixes from
415 later Tor releases. All Tor users should upgrade to this release, or
416 to another of the releases coming out today.
418 Note: the Tor 0.2.5 series will no longer be supported after 1 May
419 2018. If you need a release with long-term support, please upgrade to
420 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
422 o Major bugfixes (security, backport from 0.3.2.6-alpha):
423 - Fix a denial of service bug where an attacker could use a
424 malformed directory object to cause a Tor instance to pause while
425 OpenSSL would try to read a passphrase from the terminal. (Tor
426 instances run without a terminal, which is the case for most Tor
427 packages, are not impacted.) Fixes bug 24246; bugfix on every
428 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
429 Found by OSS-Fuzz as testcase 6360145429790720.
430 - When checking for replays in the INTRODUCE1 cell data for a
431 (legacy) onion service, correctly detect replays in the RSA-
432 encrypted part of the cell. We were previously checking for
433 replays on the entire cell, but those can be circumvented due to
434 the malleability of Tor's legacy hybrid encryption. This fix helps
435 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
436 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
439 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
440 - When running as a relay, make sure that we never build a path
441 through ourselves, even in the case where we have somehow lost the
442 version of our descriptor appearing in the consensus. Fixes part
443 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
444 as TROVE-2017-012 and CVE-2017-8822.
446 o Minor features (bridge, backport from 0.3.1.9):
447 - Bridges now include notice in their descriptors that they are
448 bridges, and notice of their distribution status, based on their
449 publication settings. Implements ticket 18329. For more fine-
450 grained control of how a bridge is distributed, upgrade to 0.3.2.x
453 o Minor features (geoip):
454 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
458 Changes in version 0.3.2.5-alpha - 2017-11-22
459 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
460 fixes several stability and reliability bugs, including a fix for
461 intermittent bootstrapping failures that some people have been seeing
462 since the 0.3.0.x series.
464 Please test this alpha out -- many of these fixes will soon be
465 backported to stable Tor versions if no additional bugs are found
468 o Major bugfixes (bootstrapping):
469 - Fetch descriptors aggressively whenever we lack enough to build
470 circuits, regardless of how many descriptors we are missing.
471 Previously, we would delay launching the fetch when we had fewer
472 than 15 missing descriptors, even if some of those descriptors
473 were blocking circuits from building. Fixes bug 23985; bugfix on
474 0.1.1.11-alpha. The effects of this bug became worse in
475 0.3.0.3-alpha, when we began treating missing descriptors from our
476 primary guards as a reason to delay circuits.
477 - Don't try fetching microdescriptors from relays that have failed
478 to deliver them in the past. Fixes bug 23817; bugfix
481 o Minor features (directory authority):
482 - Make the "Exit" flag assignment only depend on whether the exit
483 policy allows connections to ports 80 and 443. Previously relays
484 would get the Exit flag if they allowed connections to one of
485 these ports and also port 6667. Resolves ticket 23637.
487 o Minor features (geoip):
488 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
491 o Minor features (linux seccomp2 sandbox):
492 - Update the sandbox rules so that they should now work correctly
493 with Glibc 2.26. Closes ticket 24315.
495 o Minor features (logging):
496 - Downgrade a pair of log messages that could occur when an exit's
497 resolver gave us an unusual (but not forbidden) response. Closes
499 - Improve the message we log when re-enabling circuit build timeouts
500 after having received a consensus. Closes ticket 20963.
502 o Minor bugfixes (compilation):
503 - Fix a memory leak warning in one of the libevent-related
504 configuration tests that could occur when manually specifying
505 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
506 Found and patched by Alex Xu.
507 - When detecting OpenSSL on Windows from our configure script, make
508 sure to try linking with the ws2_32 library. Fixes bug 23783;
509 bugfix on 0.3.2.2-alpha.
511 o Minor bugfixes (control port, linux seccomp2 sandbox):
512 - Avoid a crash when attempting to use the seccomp2 sandbox together
513 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
516 o Minor bugfixes (control port, onion services):
517 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
518 HS_DESC event when a service is not able to upload a descriptor.
519 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
521 o Minor bugfixes (directory cache):
522 - Recover better from empty or corrupt files in the consensus cache
523 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
524 - When a consensus diff calculation is only partially successful,
525 only record the successful parts as having succeeded. Partial
526 success can happen if (for example) one compression method fails
527 but the others succeed. Previously we misrecorded all the
528 calculations as having succeeded, which would later cause a
529 nonfatal assertion failure. Fixes bug 24086; bugfix
532 o Minor bugfixes (logging):
533 - Only log once if we notice that KIST support is gone. Fixes bug
534 24158; bugfix on 0.3.2.1-alpha.
535 - Suppress a log notice when relay descriptors arrive. We already
536 have a bootstrap progress for this so no need to log notice
537 everytime tor receives relay descriptors. Microdescriptors behave
538 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
540 o Minor bugfixes (network layer):
541 - When closing a connection via close_connection_immediately(), we
542 mark it as "not blocked on bandwidth", to prevent later calls from
543 trying to unblock it, and give it permission to read. This fixes a
544 backtrace warning that can happen on relays under various
545 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
547 o Minor bugfixes (onion services):
548 - The introduction circuit was being timed out too quickly while
549 waiting for the rendezvous circuit to complete. Keep the intro
550 circuit around longer instead of timing out and reopening new ones
551 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
552 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
553 so it matches dir-spec.txt. Fixes bug 24262; bugfix
555 - Silence a warning about failed v3 onion descriptor uploads that
556 can happen naturally under certain edge cases. Fixes part of bug
557 23662; bugfix on 0.3.2.1-alpha.
559 o Minor bugfixes (tests):
560 - Fix a memory leak in one of the bridge-distribution test cases.
561 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
562 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
563 to correctly handle cases where a caller gives it an RSA key of
564 under 160 bits. (This is not actually a bug in Tor itself, but
565 rather in our fuzzing code.) Fixes bug 24247; bugfix on
566 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
569 - Add notes in man page regarding OS support for the various
570 scheduler types. Attempt to use less jargon in the scheduler
571 section. Closes ticket 24254.
574 Changes in version 0.3.2.4-alpha - 2017-11-08
575 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
576 It fixes several stability and reliability bugs, especially including
577 a major reliability issue that has been plaguing fast exit relays in
580 o Major bugfixes (exit relays, DNS):
581 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
582 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
583 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
584 identifying and finding a workaround to this bug and to Moritz,
585 Arthur Edelstein, and Roger for helping to track it down and
588 o Major bugfixes (scheduler, channel):
589 - Stop processing scheduled channels if they closed while flushing
590 cells. This can happen if the write on the connection fails
591 leading to the channel being closed while in the scheduler loop.
592 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
594 o Minor features (logging, scheduler):
595 - Introduce a SCHED_BUG() function to log extra information about
596 the scheduler state if we ever catch a bug in the scheduler.
599 o Minor features (removed deprecations):
600 - The ClientDNSRejectInternalAddresses flag can once again be set in
601 non-testing Tor networks, so long as they do not use the default
602 directory authorities. This change also removes the deprecation of
603 this flag from 0.2.9.2-alpha. Closes ticket 21031.
605 o Minor features (testing):
606 - Our fuzzing tests now test the encrypted portions of v3 onion
607 service descriptors. Implements more of 21509.
609 o Minor bugfixes (directory client):
610 - On failure to download directory information, delay retry attempts
611 by a random amount based on the "decorrelated jitter" algorithm.
612 Our previous delay algorithm tended to produce extra-long delays
613 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
615 o Minor bugfixes (IPv6, v3 single onion services):
616 - Remove buggy code for IPv6-only v3 single onion services, and
617 reject attempts to configure them. This release supports IPv4,
618 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
619 stack v3 single onion services. Fixes bug 23820; bugfix
622 o Minor bugfixes (logging, relay):
623 - Give only a protocol warning when the ed25519 key is not
624 consistent between the descriptor and microdescriptor of a relay.
625 This can happen, for instance, if the relay has been flagged
626 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
628 o Minor bugfixes (manpage, onion service):
629 - Document that the HiddenServiceNumIntroductionPoints option is
630 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
631 bugfix on 0.3.2.1-alpha.
633 o Minor bugfixes (memory leaks):
634 - Fix a minor memory leak at exit in the KIST scheduler. This bug
635 should have no user-visible impact. Fixes bug 23774; bugfix
637 - Fix a memory leak when decrypting a badly formatted v3 onion
638 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
639 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
641 o Minor bugfixes (onion services):
642 - Cache some needed onion service client information instead of
643 constantly computing it over and over again. Fixes bug 23623;
644 bugfix on 0.3.2.1-alpha.
645 - Properly retry HSv3 descriptor fetches when missing required
646 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
648 o Minor bugfixes (path selection):
649 - When selecting relays by bandwidth, avoid a rounding error that
650 could sometimes cause load to be imbalanced incorrectly.
651 Previously, we would always round upwards; now, we round towards
652 the nearest integer. This had the biggest effect when a relay's
653 weight adjustments should have given it weight 0, but it got
654 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
655 - When calculating the fraction of nodes that have descriptors, and
656 all nodes in the network have zero bandwidths, count the number of
657 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
658 - Actually log the total bandwidth in compute_weighted_bandwidths().
659 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
661 o Minor bugfixes (relay, crash):
662 - Avoid a crash when transitioning from client mode to bridge mode.
663 Previously, we would launch the worker threads whenever our
664 "public server" mode changed, but not when our "server" mode
665 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
667 o Minor bugfixes (testing):
668 - Fix a spurious fuzzing-only use of an uninitialized value. Found
669 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
670 - Test that IPv6-only clients can use microdescriptors when running
671 "make test-network-all". Requires chutney master 61c28b9 or later.
675 Changes in version 0.3.2.3-alpha - 2017-10-27
676 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
677 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
678 directory authority, Bastet.
680 o Directory authority changes:
681 - Add "Bastet" as a ninth directory authority to the default list.
683 - The directory authority "Longclaw" has changed its IP address.
686 o Minor features (bridge):
687 - Bridge relays can now set the BridgeDistribution config option to
688 add a "bridge-distribution-request" line to their bridge
689 descriptor, which tells BridgeDB how they'd like their bridge
690 address to be given out. (Note that as of Oct 2017, BridgeDB does
691 not yet implement this feature.) As a side benefit, this feature
692 provides a way to distinguish bridge descriptors from non-bridge
693 descriptors. Implements tickets 18329.
695 o Minor features (client, entry guards):
696 - Improve log messages when missing descriptors for primary guards.
697 Resolves ticket 23670.
699 o Minor features (geoip):
700 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
703 o Minor bugfixes (bridge):
704 - Overwrite the bridge address earlier in the process of retrieving
705 its descriptor, to make sure we reach it on the configured
706 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
708 o Minor bugfixes (documentation):
709 - Document better how to read gcov, and what our gcov postprocessing
710 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
712 o Minor bugfixes (entry guards):
713 - Tor now updates its guard state when it reads a consensus
714 regardless of whether it's missing descriptors. That makes tor use
715 its primary guards to fetch descriptors in some edge cases where
716 it would previously have used fallback directories. Fixes bug
717 23862; bugfix on 0.3.0.1-alpha.
719 o Minor bugfixes (hidden service client):
720 - When handling multiple SOCKS request for the same .onion address,
721 only fetch the service descriptor once.
722 - When a descriptor fetch fails with a non-recoverable error, close
723 all pending SOCKS requests for that .onion. Fixes bug 23653;
724 bugfix on 0.3.2.1-alpha.
726 o Minor bugfixes (hidden service):
727 - Always regenerate missing hidden service public key files. Prior
728 to this, if the public key was deleted from disk, it wouldn't get
729 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
731 - Make sure that we have a usable ed25519 key when the intro point
732 relay supports ed25519 link authentication. Fixes bug 24002;
733 bugfix on 0.3.2.1-alpha.
735 o Minor bugfixes (hidden service, v2):
736 - When reloading configured hidden services, copy all information
737 from the old service object. Previously, some data was omitted,
738 causing delays in descriptor upload, and other bugs. Fixes bug
739 23790; bugfix on 0.2.1.9-alpha.
741 o Minor bugfixes (memory safety, defensive programming):
742 - Clear the target address when node_get_prim_orport() returns
743 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
745 o Minor bugfixes (relay):
746 - Avoid a BUG warning when receiving a dubious CREATE cell while an
747 option transition is in progress. Fixes bug 23952; bugfix
750 o Minor bugfixes (testing):
751 - Adjust the GitLab CI configuration to more closely match that of
752 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
753 - Prevent scripts/test/coverage from attempting to move gcov output
754 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
755 - When running unit tests as root, skip a test that would fail
756 because it expects a permissions error. This affects some
757 continuous integration setups. Fixes bug 23758; bugfix
759 - Stop unconditionally mirroring the tor repository in GitLab CI.
760 This prevented developers from enabling GitLab CI on master. Fixes
761 bug 23755; bugfix on 0.3.2.2-alpha.
762 - Fix the hidden service v3 descriptor decoding fuzzing to use the
763 latest decoding API correctly. Fixes bug 21509; bugfix
766 o Minor bugfixes (warnings):
767 - When we get an HTTP request on a SOCKS port, tell the user about
768 the new HTTPTunnelPort option. Previously, we would give a "Tor is
769 not an HTTP Proxy" message, which stopped being true when
770 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
774 Changes in version 0.2.5.15 - 2017-10-25
775 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
776 series. It also adds a new directory authority, Bastet.
778 Note: the Tor 0.2.5 series will no longer be supported after 1 May
779 2018. If you need a release with long-term support, please upgrade to
780 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
782 o Directory authority changes:
783 - Add "Bastet" as a ninth directory authority to the default list.
785 - The directory authority "Longclaw" has changed its IP address.
788 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
789 - Avoid an assertion failure bug affecting our implementation of
790 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
791 handling of "0xx" differs from what we had expected. Fixes bug
792 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
794 o Minor features (geoip):
795 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
798 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
799 - Fix a memset() off the end of an array when packing cells. This
800 bug should be harmless in practice, since the corrupted bytes are
801 still in the same structure, and are always padding bytes,
802 ignored, or immediately overwritten, depending on compiler
803 behavior. Nevertheless, because the memset()'s purpose is to make
804 sure that any other cell-handling bugs can't expose bytes to the
805 network, we need to fix it. Fixes bug 22737; bugfix on
806 0.2.4.11-alpha. Fixes CID 1401591.
808 o Build features (backport from 0.3.1.5-alpha):
809 - Tor's repository now includes a Travis Continuous Integration (CI)
810 configuration file (.travis.yml). This is meant to help new
811 developers and contributors who fork Tor to a Github repository be
812 better able to test their changes, and understand what we expect
813 to pass. To use this new build feature, you must fork Tor to your
814 Github account, then go into the "Integrations" menu in the
815 repository settings for your fork and enable Travis, then push
816 your changes. Closes ticket 22636.
819 Changes in version 0.2.8.16 - 2017-10-25
820 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
821 series, including a bugfix for a crash issue that had affected relays
822 under memory pressure. It also adds a new directory authority, Bastet.
824 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
825 2018. If you need a release with long-term support, please stick with
826 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
828 o Directory authority changes:
829 - Add "Bastet" as a ninth directory authority to the default list.
831 - The directory authority "Longclaw" has changed its IP address.
834 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
835 - Fix a timing-based assertion failure that could occur when the
836 circuit out-of-memory handler freed a connection's output buffer.
837 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
839 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
840 - Remove longclaw's IPv6 address, as it will soon change. Authority
841 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
842 3/8 directory authorities with IPv6 addresses, but there are also
843 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
845 o Minor features (geoip):
846 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
850 Changes in version 0.2.9.13 - 2017-10-25
851 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
852 series, including a bugfix for a crash issue that had affected relays
853 under memory pressure. It also adds a new directory authority, Bastet.
855 o Directory authority changes:
856 - Add "Bastet" as a ninth directory authority to the default list.
858 - The directory authority "Longclaw" has changed its IP address.
861 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
862 - Fix a timing-based assertion failure that could occur when the
863 circuit out-of-memory handler freed a connection's output buffer.
864 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
866 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
867 - Remove longclaw's IPv6 address, as it will soon change. Authority
868 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
869 3/8 directory authorities with IPv6 addresses, but there are also
870 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
872 o Minor features (geoip):
873 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
876 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
877 - When a directory authority rejects a descriptor or extrainfo with
878 a given digest, mark that digest as undownloadable, so that we do
879 not attempt to download it again over and over. We previously
880 tried to avoid downloading such descriptors by other means, but we
881 didn't notice if we accidentally downloaded one anyway. This
882 behavior became problematic in 0.2.7.2-alpha, when authorities
883 began pinning Ed25519 keys. Fixes bug 22349; bugfix
886 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
887 - Clear the address when node_get_prim_orport() returns early.
888 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
890 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
891 - When running as a Windows service, set the ID of the main thread
892 correctly. Failure to do so made us fail to send log messages to
893 the controller in 0.2.1.16-rc, slowed down controller event
894 delivery in 0.2.7.3-rc and later, and crash with an assertion
895 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
896 Patch and diagnosis from "Vort".
899 Changes in version 0.3.0.12 - 2017-10-25
900 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
901 series, including a bugfix for a crash issue that had affected relays
902 under memory pressure. It also adds a new directory authority, Bastet.
904 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
905 2018. If you need a release with long-term support, please stick with
906 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
908 o Directory authority changes:
909 - Add "Bastet" as a ninth directory authority to the default list.
911 - The directory authority "Longclaw" has changed its IP address.
914 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
915 - Fix a timing-based assertion failure that could occur when the
916 circuit out-of-memory handler freed a connection's output buffer.
917 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
919 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
920 - Remove longclaw's IPv6 address, as it will soon change. Authority
921 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
922 3/8 directory authorities with IPv6 addresses, but there are also
923 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
925 o Minor features (geoip):
926 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
929 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
930 - When a directory authority rejects a descriptor or extrainfo with
931 a given digest, mark that digest as undownloadable, so that we do
932 not attempt to download it again over and over. We previously
933 tried to avoid downloading such descriptors by other means, but we
934 didn't notice if we accidentally downloaded one anyway. This
935 behavior became problematic in 0.2.7.2-alpha, when authorities
936 began pinning Ed25519 keys. Fixes bug 22349; bugfix
939 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
940 - Avoid a possible double close of a circuit by the intro point on
941 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
942 bugfix on 0.3.0.1-alpha.
944 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
945 - Clear the address when node_get_prim_orport() returns early.
946 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
948 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
949 - When running as a Windows service, set the ID of the main thread
950 correctly. Failure to do so made us fail to send log messages to
951 the controller in 0.2.1.16-rc, slowed down controller event
952 delivery in 0.2.7.3-rc and later, and crash with an assertion
953 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
954 Patch and diagnosis from "Vort".
957 Changes in version 0.3.1.8 - 2017-10-25
958 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
959 It includes several bugfixes, including a bugfix for a crash issue
960 that had affected relays under memory pressure. It also adds
961 a new directory authority, Bastet.
963 o Directory authority changes:
964 - Add "Bastet" as a ninth directory authority to the default list.
966 - The directory authority "Longclaw" has changed its IP address.
969 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
970 - Fix a timing-based assertion failure that could occur when the
971 circuit out-of-memory handler freed a connection's output buffer.
972 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
974 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
975 - Remove longclaw's IPv6 address, as it will soon change. Authority
976 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
977 3/8 directory authorities with IPv6 addresses, but there are also
978 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
980 o Minor features (geoip):
981 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
984 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
985 - Fix a compilation warning when building with zstd support on
986 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
987 and fixed by Andreas Stieger.
989 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
990 - Handle a pathological case when decompressing Zstandard data when
991 the output buffer size is zero. Fixes bug 23551; bugfix
994 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
995 - Remove the length limit on HTTP status lines that authorities can
996 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
998 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
999 - Avoid a possible double close of a circuit by the intro point on
1000 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1001 bugfix on 0.3.0.1-alpha.
1003 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1004 - Clear the address when node_get_prim_orport() returns early.
1005 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1007 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
1008 - Fix additional channelpadding unit test failures by using mocked
1009 time instead of actual time for all tests. Fixes bug 23608; bugfix
1013 Changes in version 0.3.2.2-alpha - 2017-09-29
1014 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
1015 release fixes several minor bugs in the new scheduler and next-
1016 generation onion services; both features were newly added in the 0.3.2
1017 series. Other fixes in this alpha include several fixes for non-fatal
1018 tracebacks which would appear in logs.
1020 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
1021 alpha does not contain any substantial new features. Minor features
1022 include better testing and logging.
1024 The following comprises the complete list of changes included
1025 in tor-0.3.2.2-alpha:
1027 o Major bugfixes (relay, crash, assertion failure):
1028 - Fix a timing-based assertion failure that could occur when the
1029 circuit out-of-memory handler freed a connection's output buffer.
1030 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1032 o Major bugfixes (scheduler):
1033 - If a channel is put into the scheduler's pending list, then it
1034 starts closing, and then if the scheduler runs before it finishes
1035 closing, the scheduler will get stuck trying to flush its cells
1036 while the lower layers refuse to cooperate. Fix that race
1037 condition by giving the scheduler an escape method. Fixes bug
1038 23676; bugfix on 0.3.2.1-alpha.
1040 o Minor features (build, compilation):
1041 - The "check-changes" feature is now part of the "make check" tests;
1042 we'll use it to try to prevent misformed changes files from
1043 accumulating. Closes ticket 23564.
1044 - Tor builds should now fail if there are any mismatches between the
1045 C type representing a configuration variable and the C type the
1046 data-driven parser uses to store a value there. Previously, we
1047 needed to check these by hand, which sometimes led to mistakes.
1048 Closes ticket 23643.
1050 o Minor features (directory authorities):
1051 - Remove longclaw's IPv6 address, as it will soon change. Authority
1052 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1053 3/8 directory authorities with IPv6 addresses, but there are also
1054 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1056 o Minor features (hidden service, circuit, logging):
1057 - Improve logging of many callsite in the circuit subsystem to print
1058 the circuit identifier(s).
1059 - Log when we cleanup an intro point from a service so we know when
1060 and for what reason it happened. Closes ticket 23604.
1062 o Minor features (logging):
1063 - Log more circuit information whenever we are about to try to
1064 package a relay cell on a circuit with a nonexistent n_chan.
1065 Attempt to diagnose ticket 8185.
1066 - Improve info-level log identification of particular circuits, to
1067 help with debugging. Closes ticket 23645.
1069 o Minor features (relay):
1070 - When choosing which circuits can be expired as unused, consider
1071 circuits from clients even if those clients used regular CREATE
1072 cells to make them; and do not consider circuits from relays even
1073 if they were made with CREATE_FAST. Part of ticket 22805.
1075 o Minor features (robustness):
1076 - Change several fatal assertions when flushing buffers into non-
1077 fatal assertions, to prevent any recurrence of 23690.
1079 o Minor features (spec conformance, bridge, diagnostic):
1080 - When handling the USERADDR command on an ExtOrPort, warn when the
1081 transports provides a USERADDR with no port. In a future version,
1082 USERADDR commands of this format may be rejected. Detects problems
1083 related to ticket 23080.
1085 o Minor features (testing):
1086 - Add a unit test to make sure that our own generated platform
1087 string will be accepted by directory authorities. Closes
1090 o Minor bugfixes (bootstrapping):
1091 - When warning about state file clock skew, report the correct
1092 direction for the detected skew. Fixes bug 23606; bugfix
1094 - Avoid an assertion failure when logging a state file clock skew
1095 very early in bootstrapping. Fixes bug 23607; bugfix
1098 o Minor bugfixes (build, compilation):
1099 - Fix a compilation warning when building with zstd support on
1100 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1101 and fixed by Andreas Stieger.
1102 - When searching for OpenSSL, don't accept any OpenSSL library that
1103 lacks TLSv1_1_method(): Tor doesn't build with those versions.
1104 Additionally, look in /usr/local/opt/openssl, if it's present.
1105 These changes together repair the default build on OSX systems
1106 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
1108 o Minor bugfixes (compression):
1109 - Handle a pathological case when decompressing Zstandard data when
1110 the output buffer size is zero. Fixes bug 23551; bugfix
1113 o Minor bugfixes (documentation):
1114 - Fix manpage to not refer to the obsolete (and misspelled)
1115 UseEntryGuardsAsDirectoryGuards parameter in the description of
1116 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
1118 o Minor bugfixes (hidden service v3):
1119 - Don't log an assertion failure when we can't find the right
1120 information to extend to an introduction point. In rare cases,
1121 this could happen, causing a warning, even though tor would
1122 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
1123 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
1124 much bigger so the rendezvous point can't distinguish which hidden
1125 service protocol is being used. Fixes bug 23420; bugfix
1128 o Minor bugfixes (hidden service, relay):
1129 - Avoid a possible double close of a circuit by the intro point on
1130 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1131 bugfix on 0.3.0.1-alpha.
1133 o Minor bugfixes (logging, relay shutdown, annoyance):
1134 - When a circuit is marked for close, do not attempt to package any
1135 cells for channels on that circuit. Previously, we would detect
1136 this condition lower in the call stack, when we noticed that the
1137 circuit had no attached channel, and log an annoying message.
1138 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1140 o Minor bugfixes (scheduler):
1141 - When switching schedulers due to a consensus change, we didn't
1142 give the new scheduler a chance to react to the consensus. Fix
1143 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
1144 - Make the KISTSchedRunInterval option a non negative value. With
1145 this, the way to disable KIST through the consensus is to set it
1146 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
1147 - Only notice log the selected scheduler when we switch scheduler
1148 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
1149 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
1150 by a different tv_usec data type. Fixes bug 23575; bugfix
1152 - Make a hard exit if tor is unable to pick a scheduler which can
1153 happen if the user specifies a scheduler type that is not
1154 supported and not other types in Schedulers. Fixes bug 23581;
1155 bugfix on 0.3.2.1-alpha.
1156 - Properly initialize the scheduler last run time counter so it is
1157 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
1159 o Minor bugfixes (testing):
1160 - Capture and detect several "Result does not fit" warnings in unit
1161 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
1163 - Fix additional channelpadding unit test failures by using mocked
1164 time instead of actual time for all tests. Fixes bug 23608; bugfix
1166 - The removal of some old scheduler options caused some tests to
1167 fail on BSD systems. Assume current behavior is correct and make
1168 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
1170 o Code simplification and refactoring:
1171 - Remove various ways of testing circuits and connections for
1172 "clientness"; instead, favor channel_is_client(). Part of
1175 o Deprecated features:
1176 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
1177 now deprecated; they do not apply to relays, and they have had no
1178 effect on clients since 0.2.8.x. Closes ticket 19704.
1181 - HiddenServiceVersion man page entry wasn't mentioning the now
1182 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
1183 - Clarify that the Address option is entirely about setting an
1184 advertised IPv4 address. Closes ticket 18891.
1185 - Clarify the manpage's use of the term "address" to clarify what
1186 kind of address is intended. Closes ticket 21405.
1187 - Document that onion service subdomains are allowed, and ignored.
1188 Closes ticket 18736.
1191 Changes in version 0.3.2.1-alpha - 2017-09-18
1192 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
1193 includes support for our next-generation ("v3") onion service
1194 protocol, and adds a new circuit scheduler for more responsive
1195 forwarding decisions from relays. There are also numerous other small
1196 features and bugfixes here.
1198 Below are the changes since Tor 0.3.1.7.
1200 o Major feature (scheduler, channel):
1201 - Tor now uses new schedulers to decide which circuits should
1202 deliver cells first, in order to improve congestion at relays. The
1203 first type is called "KIST" ("Kernel Informed Socket Transport"),
1204 and is only available on Linux-like systems: it uses feedback from
1205 the kernel to prevent the kernel's TCP buffers from growing too
1206 full. The second new scheduler type is called "KISTLite": it
1207 behaves the same as KIST, but runs on systems without kernel
1208 support for inspecting TCP implementation details. The old
1209 scheduler is still available, under the name "Vanilla". To change
1210 the default scheduler preference order, use the new "Schedulers"
1211 option. (The default preference order is "KIST,KISTLite,Vanilla".)
1213 Matt Traudt implemented KIST, based on research by Rob Jansen,
1214 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
1215 more information, see the design paper at
1216 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
1217 followup implementation paper at https://arxiv.org/abs/1709.01044.
1218 Closes ticket 12541.
1220 o Major features (next-generation onion services):
1221 - Tor now supports the next-generation onion services protocol for
1222 clients and services! As part of this release, the core of
1223 proposal 224 has been implemented and is available for
1224 experimentation and testing by our users. This newer version of
1225 onion services ("v3") features many improvements over the legacy
1228 a) Better crypto (replaced SHA1/DH/RSA1024
1229 with SHA3/ed25519/curve25519)
1231 b) Improved directory protocol, leaking much less information to
1234 c) Improved directory protocol, with smaller surface for
1237 d) Better onion address security against impersonation.
1239 e) More extensible introduction/rendezvous protocol.
1241 f) A cleaner and more modular codebase.
1243 You can identify a next-generation onion address by its length:
1244 they are 56 characters long, as in
1245 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
1247 In the future, we will release more options and features for v3
1248 onion services, but we first need a testing period, so that the
1249 current codebase matures and becomes more robust. Planned features
1250 include: offline keys, advanced client authorization, improved
1251 guard algorithms, and statistics. For full details, see
1254 Legacy ("v2") onion services will still work for the foreseeable
1255 future, and will remain the default until this new codebase gets
1256 tested and hardened. Service operators who want to experiment with
1257 the new system can use the 'HiddenServiceVersion 3' torrc
1258 directive along with the regular onion service configuration
1259 options. We will publish a blog post about this new feature
1262 o Major bugfixes (usability, control port):
1263 - Report trusted clock skew indications as bootstrap errors, so
1264 controllers can more easily alert users when their clocks are
1265 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
1267 o Minor features (bug detection):
1268 - Log a warning message with a stack trace for any attempt to call
1269 get_options() during option validation. This pattern has caused
1270 subtle bugs in the past. Closes ticket 22281.
1272 o Minor features (client):
1273 - You can now use Tor as a tunneled HTTP proxy: use the new
1274 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
1275 requests. Closes ticket 22407.
1276 - Add an extra check to make sure that we always use the newer guard
1277 selection code for picking our guards. Closes ticket 22779.
1278 - When downloading (micro)descriptors, don't split the list into
1279 multiple requests unless we want at least 32 descriptors.
1280 Previously, we split at 4, not 32, which led to significant
1281 overhead in HTTP request size and degradation in compression
1282 performance. Closes ticket 23220.
1284 o Minor features (command line):
1285 - Add a new commandline option, --key-expiration, which prints when
1286 the current signing key is going to expire. Implements ticket
1287 17639; patch by Isis Lovecruft.
1289 o Minor features (control port):
1290 - If an application tries to use the control port as an HTTP proxy,
1291 respond with a meaningful "This is the Tor control port" message,
1292 and log the event. Closes ticket 1667. Patch from Ravi
1294 - Provide better error message for GETINFO desc/(id|name) when not
1295 fetching router descriptors. Closes ticket 5847. Patch by
1297 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
1298 whether Tor will try to download router descriptors and
1299 microdescriptors respectively. Closes ticket 22684.
1300 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
1301 so controllers can tell whether the geoip databases are loaded.
1302 Closes ticket 23237.
1303 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
1304 events. Closes ticket 19254. Patch by "DonnchaC".
1306 o Minor features (development support):
1307 - Developers can now generate a call-graph for Tor using the
1308 "calltool" python program, which post-processes object dumps. It
1309 should work okay on many Linux and OSX platforms, and might work
1310 elsewhere too. To run it, install calltool from
1311 https://gitweb.torproject.org/user/nickm/calltool.git and run
1312 "make callgraph". Closes ticket 19307.
1314 o Minor features (ed25519):
1315 - Add validation function to checks for torsion components in
1316 ed25519 public keys, used by prop224 client-side code. Closes
1317 ticket 22006. Math help by Ian Goldberg.
1319 o Minor features (exit relay, DNS):
1320 - Improve the clarity and safety of the log message from evdns when
1321 receiving an apparently spoofed DNS reply. Closes ticket 3056.
1323 o Minor features (integration, hardening):
1324 - Add a new NoExec option to prevent Tor from running other
1325 programs. When this option is set to 1, Tor will never try to run
1326 another program, regardless of the settings of
1327 PortForwardingHelper, ClientTransportPlugin, or
1328 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
1329 without restarting Tor. Closes ticket 22976.
1331 o Minor features (logging):
1332 - Improve the warning message for specifying a relay by nickname.
1333 The previous message implied that nickname registration was still
1334 part of the Tor network design, which it isn't. Closes
1336 - If the sandbox filter fails to load, suggest to the user that
1337 their kernel might not support seccomp2. Closes ticket 23090.
1339 o Minor features (portability):
1340 - Check at configure time whether uint8_t is the same type as
1341 unsigned char. Lots of existing code already makes this
1342 assumption, and there could be strict aliasing issues if the
1343 assumption is violated. Closes ticket 22410.
1345 o Minor features (relay, configuration):
1346 - Reject attempts to use relative file paths when RunAsDaemon is
1347 set. Previously, Tor would accept these, but the directory-
1348 changing step of RunAsDaemon would give strange and/or confusing
1349 results. Closes ticket 22731.
1351 o Minor features (startup, safety):
1352 - When configured to write a PID file, Tor now exits if it is unable
1353 to do so. Previously, it would warn and continue. Closes
1356 o Minor features (static analysis):
1357 - The BUG() macro has been changed slightly so that Coverity no
1358 longer complains about dead code if the bug is impossible. Closes
1361 o Minor features (testing):
1362 - The default chutney network tests now include tests for the v3
1363 hidden service design. Make sure you have the latest version of
1364 chutney if you want to run these. Closes ticket 22437.
1365 - Add a unit test to verify that we can parse a hardcoded v2 hidden
1366 service descriptor. Closes ticket 15554.
1368 o Minor bugfixes (certificate handling):
1369 - Fix a time handling bug in Tor certificates set to expire after
1370 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
1371 Coverity as CID 1415728.
1373 o Minor bugfixes (client, usability):
1374 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
1375 SOCKS4a requests that contain IP address strings, even when
1376 SafeSocks in enabled, as this prevents user from connecting to
1377 known IP addresses without relying on DNS for resolving. SafeSocks
1378 still rejects SOCKS connections that connect to IP addresses when
1379 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
1380 bugfix on Tor 0.2.6.2-alpha.
1382 o Minor bugfixes (code correctness):
1383 - Call htons() in extend_cell_format() for encoding a 16-bit value.
1384 Previously we used ntohs(), which happens to behave the same on
1385 all the platforms we support, but which isn't really correct.
1386 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
1387 - For defense-in-depth, make the controller's write_escaped_data()
1388 function robust to extremely long inputs. Fixes bug 19281; bugfix
1389 on 0.1.1.1-alpha. Reported by Guido Vranken.
1391 o Minor bugfixes (compilation):
1392 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
1393 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1395 o Minor bugfixes (consensus expiry):
1396 - Check for adequate directory information correctly. Previously, Tor
1397 would reconsider whether it had sufficient directory information
1398 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
1400 o Minor bugfixes (directory protocol):
1401 - Directory servers now include a "Date:" http header for response
1402 codes other than 200. Clients starting with a skewed clock and a
1403 recent consensus were getting "304 Not modified" responses from
1404 directory authorities, so without the Date header, the client
1405 would never hear about a wrong clock. Fixes bug 23499; bugfix
1407 - Make clients wait for 6 seconds before trying to download a
1408 consensus from an authority. Fixes bug 17750; bugfix
1411 o Minor bugfixes (DoS-resistance):
1412 - If future code asks if there are any running bridges, without
1413 checking if bridges are enabled, log a BUG warning rather than
1414 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
1416 o Minor bugfixes (format strictness):
1417 - Restrict several data formats to decimal. Previously, the
1418 BuildTimeHistogram entries in the state file, the "bw=" entries in
1419 the bandwidth authority file, and the process IDs passed to the
1420 __OwningControllerProcess option could all be specified in hex or
1421 octal as well as in decimal. This was not an intentional feature.
1422 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
1425 o Minor bugfixes (heartbeat):
1426 - If we fail to write a heartbeat message, schedule a retry for the
1427 minimum heartbeat interval number of seconds in the future. Fixes
1428 bug 19476; bugfix on 0.2.3.1-alpha.
1430 o Minor bugfixes (linux seccomp2 sandbox, logging):
1431 - Fix some messages on unexpected errors from the seccomp2 library.
1432 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
1434 o Minor bugfixes (logging):
1435 - Remove duplicate log messages regarding opening non-local
1436 SocksPorts upon parsing config and opening listeners at startup.
1437 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
1438 - Use a more comprehensible log message when telling the user
1439 they've excluded every running exit node. Fixes bug 7890; bugfix
1441 - When logging the number of descriptors we intend to download per
1442 directory request, do not log a number higher than then the number
1443 of descriptors we're fetching in total. Fixes bug 19648; bugfix
1445 - When warning about a directory owned by the wrong user, log the
1446 actual name of the user owning the directory. Previously, we'd log
1447 the name of the process owner twice. Fixes bug 23487; bugfix
1449 - The tor specification says hop counts are 1-based, so fix two log
1450 messages that mistakenly logged 0-based hop counts. Fixes bug
1451 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
1452 Credit to Xiaofan Li for reporting this issue.
1454 o Minor bugfixes (portability):
1455 - Stop using the PATH_MAX variable, which is not defined on GNU
1456 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
1458 o Minor bugfixes (relay):
1459 - When uploading our descriptor for the first time after startup,
1460 report the reason for uploading as "Tor just started" rather than
1461 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
1462 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1463 relays, to prevent spurious address resolutions and descriptor
1464 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1465 bugfix on in 0.2.8.1-alpha.
1467 o Minor bugfixes (tests):
1468 - Fix a broken unit test for the OutboundAddress option: the parsing
1469 function was never returning an error on failure. Fixes bug 23366;
1470 bugfix on 0.3.0.3-alpha.
1471 - Fix a signed-integer overflow in the unit tests for
1472 dir/download_status_random_backoff, which was untriggered until we
1473 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
1475 o Minor bugfixes (usability, control port):
1476 - Stop making an unnecessary routerlist check in NETINFO clock skew
1477 detection; this was preventing clients from reporting NETINFO clock
1478 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
1480 o Code simplification and refactoring:
1481 - Extract the code for handling newly-open channels into a separate
1482 function from the general code to handle channel state
1483 transitions. This change simplifies our callgraph, reducing the
1484 size of the largest strongly connected component by roughly a
1485 factor of two. Closes ticket 22608.
1486 - Remove dead code for largely unused statistics on the number of
1487 times we've attempted various public key operations. Fixes bug
1488 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
1489 - Remove several now-obsolete functions for asking about old
1490 variants directory authority status. Closes ticket 22311; patch
1492 - Remove some of the code that once supported "Named" and "Unnamed"
1493 routers. Authorities no longer vote for these flags. Closes
1495 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
1496 and old hidden services, to indicate that they aren't suitable for
1497 new protocols or formats. Closes ticket 23026.
1498 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
1499 22521. Patch from Neel Chauhan.
1500 - Split the enormous circuit_send_next_onion_skin() function into
1501 multiple subfunctions. Closes ticket 22804.
1502 - Split the portions of the buffer.c module that handle particular
1503 protocols into separate modules. Part of ticket 23149.
1504 - Use our test macros more consistently, to produce more useful
1505 error messages when our unit tests fail. Add coccinelle patches to
1506 allow us to re-check for test macro uses. Closes ticket 22497.
1508 o Deprecated features:
1509 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
1510 only applies to direct unencrypted HTTP connections to your
1511 directory server, which your Tor probably isn't using. Closes
1515 - Clarify in the manual that "Sandbox 1" is only supported on Linux
1516 kernels. Closes ticket 22677.
1517 - Document all values of PublishServerDescriptor in the manpage.
1518 Closes ticket 15645.
1519 - Improve the documentation for the directory port part of the
1520 DirAuthority line. Closes ticket 20152.
1521 - Restore documentation for the authorities' "approved-routers"
1522 file. Closes ticket 21148.
1525 - The AllowDotExit option has been removed as unsafe. It has been
1526 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
1527 - The ClientDNSRejectInternalAddresses flag can no longer be set on
1528 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
1529 Closes ticket 21031.
1530 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
1531 nobody was using it any longer. Closes ticket 22377.
1534 Changes in version 0.2.8.15 - 2017-09-18
1535 Tor 0.2.8.15 backports a collection of bugfixes from later
1538 Most significantly, it includes a fix for TROVE-2017-008, a
1539 security bug that affects hidden services running with the
1540 SafeLogging option disabled. For more information, see
1541 https://trac.torproject.org/projects/tor/ticket/23490
1543 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
1544 2018. We suggest that you upgrade to the latest stable release if
1545 possible. If you can't, we recommend that you upgrade at least to
1546 0.2.9, which will be supported until 2020.
1548 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1549 - Avoid an assertion failure bug affecting our implementation of
1550 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1551 handling of "0xx" differs from what we had expected. Fixes bug
1552 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1555 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1558 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1559 - Backport a fix for an "unused variable" warning that appeared
1560 in some versions of mingw. Fixes bug 22838; bugfix on
1563 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1564 - Fix a memset() off the end of an array when packing cells. This
1565 bug should be harmless in practice, since the corrupted bytes are
1566 still in the same structure, and are always padding bytes,
1567 ignored, or immediately overwritten, depending on compiler
1568 behavior. Nevertheless, because the memset()'s purpose is to make
1569 sure that any other cell-handling bugs can't expose bytes to the
1570 network, we need to fix it. Fixes bug 22737; bugfix on
1571 0.2.4.11-alpha. Fixes CID 1401591.
1573 o Build features (backport from 0.3.1.5-alpha):
1574 - Tor's repository now includes a Travis Continuous Integration (CI)
1575 configuration file (.travis.yml). This is meant to help new
1576 developers and contributors who fork Tor to a Github repository be
1577 better able to test their changes, and understand what we expect
1578 to pass. To use this new build feature, you must fork Tor to your
1579 Github account, then go into the "Integrations" menu in the
1580 repository settings for your fork and enable Travis, then push
1581 your changes. Closes ticket 22636.
1584 Changes in version 0.2.9.12 - 2017-09-18
1585 Tor 0.2.9.12 backports a collection of bugfixes from later
1588 Most significantly, it includes a fix for TROVE-2017-008, a
1589 security bug that affects hidden services running with the
1590 SafeLogging option disabled. For more information, see
1591 https://trac.torproject.org/projects/tor/ticket/23490
1593 o Major features (security, backport from 0.3.0.2-alpha):
1594 - Change the algorithm used to decide DNS TTLs on client and server
1595 side, to better resist DNS-based correlation attacks like the
1596 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
1597 Feamster. Now relays only return one of two possible DNS TTL
1598 values, and clients are willing to believe DNS TTL values up to 3
1599 hours long. Closes ticket 19769.
1601 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
1602 - Fix a rare crash when sending a begin cell on a circuit whose
1603 linked directory connection had already been closed. Fixes bug
1604 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
1606 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
1607 - Fix a bug that prevented exit nodes from caching DNS records for
1608 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
1610 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
1611 - Fix a typo that had prevented TPROXY-based transparent proxying
1612 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
1613 Patch from "d4fq0fQAgoJ".
1615 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1616 - Avoid an assertion failure bug affecting our implementation of
1617 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1618 handling of "0xx" differs from what we had expected. Fixes bug
1619 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1621 o Minor features (code style, backport from 0.3.1.3-alpha):
1622 - Add "Falls through" comments to our codebase, in order to silence
1623 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1624 Stieger. Closes ticket 22446.
1626 o Minor features (geoip):
1627 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1630 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
1631 - Roll over monthly accounting at the configured hour and minute,
1632 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1633 Found by Andrey Karpov with PVS-Studio.
1635 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
1636 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
1637 bugfix on 0.2.8.1-alpha.
1638 - Fix warnings when building with libscrypt and openssl scrypt support
1639 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
1640 - When building with certain versions the mingw C header files, avoid
1641 float-conversion warnings when calling the C functions isfinite(),
1642 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
1644 o Minor bugfixes (compilation, backport from 0.3.1.7):
1645 - Avoid compiler warnings in the unit tests for running tor_sscanf()
1646 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1648 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1649 - Backport a fix for an "unused variable" warning that appeared
1650 in some versions of mingw. Fixes bug 22838; bugfix on
1653 o Minor bugfixes (controller, backport from 0.3.1.7):
1654 - Do not crash when receiving a HSPOST command with an empty body.
1655 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1656 - Do not crash when receiving a POSTDESCRIPTOR command with an
1657 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1659 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
1660 - Avoid Coverity build warnings related to our BUG() macro. By
1661 default, Coverity treats BUG() as the Linux kernel does: an
1662 instant abort(). We need to override that so our BUG() macro
1663 doesn't prevent Coverity from analyzing functions that use it.
1664 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
1666 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1667 - Fix a memset() off the end of an array when packing cells. This
1668 bug should be harmless in practice, since the corrupted bytes are
1669 still in the same structure, and are always padding bytes,
1670 ignored, or immediately overwritten, depending on compiler
1671 behavior. Nevertheless, because the memset()'s purpose is to make
1672 sure that any other cell-handling bugs can't expose bytes to the
1673 network, we need to fix it. Fixes bug 22737; bugfix on
1674 0.2.4.11-alpha. Fixes CID 1401591.
1676 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1677 - When setting the maximum number of connections allowed by the OS,
1678 always allow some extra file descriptors for other files. Fixes
1679 bug 22797; bugfix on 0.2.0.10-alpha.
1681 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
1682 - Avoid a sandbox failure when trying to re-bind to a socket and
1683 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
1685 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
1686 - Permit the fchmod system call, to avoid crashing on startup when
1687 starting with the seccomp2 sandbox and an unexpected set of
1688 permissions on the data directory or its contents. Fixes bug
1689 22516; bugfix on 0.2.5.4-alpha.
1691 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
1692 - Avoid a double-marked-circuit warning that could happen when we
1693 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
1696 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
1697 - Reject version numbers with non-numeric prefixes (such as +, -, or
1698 whitespace). Disallowing whitespace prevents differential version
1699 parsing between POSIX-based and Windows platforms. Fixes bug 21507
1700 and part of 21508; bugfix on 0.0.8pre1.
1702 o Build features (backport from 0.3.1.5-alpha):
1703 - Tor's repository now includes a Travis Continuous Integration (CI)
1704 configuration file (.travis.yml). This is meant to help new
1705 developers and contributors who fork Tor to a Github repository be
1706 better able to test their changes, and understand what we expect
1707 to pass. To use this new build feature, you must fork Tor to your
1708 Github account, then go into the "Integrations" menu in the
1709 repository settings for your fork and enable Travis, then push
1710 your changes. Closes ticket 22636.
1713 Changes in version 0.3.0.11 - 2017-09-18
1714 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
1717 Most significantly, it includes a fix for TROVE-2017-008, a
1718 security bug that affects hidden services running with the
1719 SafeLogging option disabled. For more information, see
1720 https://trac.torproject.org/projects/tor/ticket/23490
1722 o Minor features (code style, backport from 0.3.1.7):
1723 - Add "Falls through" comments to our codebase, in order to silence
1724 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1725 Stieger. Closes ticket 22446.
1728 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1731 o Minor bugfixes (compilation, backport from 0.3.1.7):
1732 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1733 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1735 o Minor bugfixes (controller, backport from 0.3.1.7):
1736 - Do not crash when receiving a HSPOST command with an empty body.
1737 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1738 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1739 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1741 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1742 - When setting the maximum number of connections allowed by the OS,
1743 always allow some extra file descriptors for other files. Fixes
1744 bug 22797; bugfix on 0.2.0.10-alpha.
1746 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
1747 - Remove a forgotten debugging message when an introduction point
1748 successfully establishes a hidden service prop224 circuit with
1750 - Change three other log_warn() for an introduction point to
1751 protocol warnings, because they can be failure from the network
1752 and are not relevant to the operator. Fixes bug 23078; bugfix on
1753 0.3.0.1-alpha and 0.3.0.2-alpha.
1756 Changes in version 0.3.1.7 - 2017-09-18
1757 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
1759 With the 0.3.1 series, Tor now serves and downloads directory
1760 information in more compact formats, to save on bandwidth overhead. It
1761 also contains a new padding system to resist netflow-based traffic
1762 analysis, and experimental support for building parts of Tor in Rust
1763 (though no parts of Tor are in Rust yet). There are also numerous
1764 small features, bugfixes on earlier release series, and groundwork for
1765 the hidden services revamp of 0.3.2.
1767 This release also includes a fix for TROVE-2017-008, a security bug
1768 that affects hidden services running with the SafeLogging option
1769 disabled. For more information, see
1770 https://trac.torproject.org/projects/tor/ticket/23490
1772 Per our stable release policy, we plan to support each stable release
1773 series for at least the next nine months, or for three months after
1774 the first stable release of the next series: whichever is longer. If
1775 you need a release with long-term support, we recommend that you stay
1776 with the 0.2.9 series.
1778 Below is a list of the changes since 0.3.1.6-rc. For a list of all
1779 changes since 0.3.0, see the ReleaseNotes file.
1781 o Major bugfixes (security, hidden services, loggging):
1782 - Fix a bug where we could log uninitialized stack when a certain
1783 hidden service error occurred while SafeLogging was disabled.
1784 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
1785 TROVE-2017-008 and CVE-2017-0380.
1787 o Minor features (defensive programming):
1788 - Create a pair of consensus parameters, nf_pad_tor2web and
1789 nf_pad_single_onion, to disable netflow padding in the consensus
1790 for non-anonymous connections in case the overhead is high. Closes
1793 o Minor features (diagnostic):
1794 - Add a stack trace to the bug warnings that can be logged when
1795 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
1796 attempt for bug 23105.
1798 o Minor features (geoip):
1799 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1802 o Minor bugfixes (compilation):
1803 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1804 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1806 o Minor bugfixes (controller):
1807 - Do not crash when receiving a HSPOST command with an empty body.
1808 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1809 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1810 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1812 o Minor bugfixes (relay):
1813 - Inform the geoip and rephist modules about all requests, even on
1814 relays that are only fetching microdescriptors. Fixes a bug
1815 related to 21585; bugfix on 0.3.0.1-alpha.
1817 o Minor bugfixes (unit tests):
1818 - Fix a channelpadding unit test failure on slow systems by using
1819 mocked time instead of actual time. Fixes bug 23077; bugfix
1823 Changes in version 0.3.1.6-rc - 2017-09-05
1824 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
1825 release series, including a bug that produced weird behavior on
1826 Windows directory caches.
1828 This is the first release candidate in the Tor 0.3.1 series. If we
1829 find no new bugs or regressions here, the first stable 0.3.1 release
1830 will be nearly identical to it.
1832 o Major bugfixes (windows, directory cache):
1833 - On Windows, do not try to delete cached consensus documents and
1834 diffs before they are unmapped from memory--Windows won't allow
1835 that. Instead, allow the consensus cache directory to grow larger,
1836 to hold files that might need to stay around longer. Fixes bug
1837 22752; bugfix on 0.3.1.1-alpha.
1839 o Minor features (directory authority):
1840 - Improve the message that authorities report to relays that present
1841 RSA/Ed25519 keypairs that conflict with previously pinned keys.
1842 Closes ticket 22348.
1844 o Minor features (geoip):
1845 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
1848 o Minor features (testing):
1849 - Add more tests for compression backend initialization. Closes
1852 o Minor bugfixes (directory cache):
1853 - Fix a memory leak when recovering space in the consensus cache.
1854 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
1856 o Minor bugfixes (hidden service):
1857 - Increase the number of circuits that a service is allowed to
1858 open over a specific period of time. The value was lower than it
1859 should be (8 vs 12) in the normal case of 3 introduction points.
1860 Fixes bug 22159; bugfix on 0.3.0.5-rc.
1861 - Fix a BUG warning during HSv3 descriptor decoding that could be
1862 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
1863 on 0.3.0.1-alpha. Bug found by "haxxpop".
1864 - Rate-limit the log messages if we exceed the maximum number of
1865 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
1867 o Minor bugfixes (logging, relay):
1868 - Remove a forgotten debugging message when an introduction point
1869 successfully establishes a hidden service prop224 circuit with
1871 - Change three other log_warn() for an introduction point to
1872 protocol warnings, because they can be failure from the network
1873 and are not relevant to the operator. Fixes bug 23078; bugfix on
1874 0.3.0.1-alpha and 0.3.0.2-alpha.
1876 o Minor bugfixes (relay):
1877 - When a relay is not running as a directory cache, it will no
1878 longer generate compressed consensuses and consensus diff
1879 information. Previously, this was a waste of disk and CPU. Fixes
1880 bug 23275; bugfix on 0.3.1.1-alpha.
1882 o Minor bugfixes (robustness, error handling):
1883 - Improve our handling of the cases where OpenSSL encounters a
1884 memory error while encoding keys and certificates. We haven't
1885 observed these errors in the wild, but if they do happen, we now
1886 detect and respond better. Fixes bug 19418; bugfix on all versions
1887 of Tor. Reported by Guido Vranken.
1889 o Minor bugfixes (stability):
1890 - Avoid crashing on a double-free when unable to load or process an
1891 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
1892 with the clang static analyzer.
1894 o Minor bugfixes (testing):
1895 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1896 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1897 - Port the hs_ntor handshake test to work correctly with recent
1898 versions of the pysha3 module. Fixes bug 23071; bugfix
1901 o Minor bugfixes (Windows service):
1902 - When running as a Windows service, set the ID of the main thread
1903 correctly. Failure to do so made us fail to send log messages to
1904 the controller in 0.2.1.16-rc, slowed down controller event
1905 delivery in 0.2.7.3-rc and later, and crash with an assertion
1906 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1907 Patch and diagnosis from "Vort".
1910 Changes in version 0.3.0.10 - 2017-08-02
1911 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
1912 from the current Tor alpha series. OpenBSD users and TPROXY users
1913 should upgrade; others are probably okay sticking with 0.3.0.9.
1915 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
1916 - Tor's repository now includes a Travis Continuous Integration (CI)
1917 configuration file (.travis.yml). This is meant to help new
1918 developers and contributors who fork Tor to a Github repository be
1919 better able to test their changes, and understand what we expect
1920 to pass. To use this new build feature, you must fork Tor to your
1921 Github account, then go into the "Integrations" menu in the
1922 repository settings for your fork and enable Travis, then push
1923 your changes. Closes ticket 22636.
1925 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
1926 - Fix a typo that had prevented TPROXY-based transparent proxying
1927 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
1928 Patch from "d4fq0fQAgoJ".
1930 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1931 - Avoid an assertion failure bug affecting our implementation of
1932 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1933 handling of "0xbar" differs from what we had expected. Fixes bug
1934 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1936 o Minor features (backport from 0.3.1.5-alpha):
1937 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
1940 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
1941 - Roll over monthly accounting at the configured hour and minute,
1942 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1943 Found by Andrey Karpov with PVS-Studio.
1945 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
1946 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
1947 bugfix on 0.2.8.1-alpha.
1948 - Fix warnings when building with libscrypt and openssl scrypt
1949 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
1950 - When building with certain versions of the mingw C header files,
1951 avoid float-conversion warnings when calling the C functions
1952 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
1955 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1956 - Backport a fix for an "unused variable" warning that appeared
1957 in some versions of mingw. Fixes bug 22838; bugfix on
1960 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
1961 - Avoid Coverity build warnings related to our BUG() macro. By
1962 default, Coverity treats BUG() as the Linux kernel does: an
1963 instant abort(). We need to override that so our BUG() macro
1964 doesn't prevent Coverity from analyzing functions that use it.
1965 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
1967 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
1968 - When rejecting a router descriptor for running an obsolete version
1969 of Tor without ntor support, warn about the obsolete tor version,
1970 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
1972 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
1973 - Avoid a sandbox failure when trying to re-bind to a socket and
1974 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
1976 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
1977 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
1978 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
1981 Changes in version 0.3.1.5-alpha - 2017-08-01
1982 Tor 0.3.1.5-alpha improves the performance of consensus diff
1983 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
1984 several other bugs. If no serious bugs are found in this version, the
1985 next version will be a release candidate.
1987 This release also marks the end of support for the Tor 0.2.4.x,
1988 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
1989 further bug or security fixes. Anyone still running or distributing
1990 one of those versions should upgrade.
1992 o Major features (build system, continuous integration):
1993 - Tor's repository now includes a Travis Continuous Integration (CI)
1994 configuration file (.travis.yml). This is meant to help new
1995 developers and contributors who fork Tor to a Github repository be
1996 better able to test their changes, and understand what we expect
1997 to pass. To use this new build feature, you must fork Tor to your
1998 Github account, then go into the "Integrations" menu in the
1999 repository settings for your fork and enable Travis, then push
2000 your changes. Closes ticket 22636.
2002 o Major bugfixes (openbsd, denial-of-service):
2003 - Avoid an assertion failure bug affecting our implementation of
2004 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2005 handling of "0xbar" differs from what we had expected. Fixes bug
2006 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2008 o Major bugfixes (relay, performance):
2009 - Perform circuit handshake operations at a higher priority than we
2010 use for consensus diff creation and compression. This should
2011 prevent circuits from starving when a relay or bridge receives a
2012 new consensus, especially on lower-powered machines. Fixes bug
2013 22883; bugfix on 0.3.1.1-alpha.
2015 o Minor features (bridge authority):
2016 - Add "fingerprint" lines to the networkstatus-bridges file produced
2017 by bridge authorities. Closes ticket 22207.
2019 o Minor features (directory cache, consensus diff):
2020 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
2021 operators with low-resource environments to adjust the number of
2022 consensuses they'll store and generate diffs from. Most cache
2023 operators should leave it unchanged. Helps to work around
2026 o Minor features (geoip):
2027 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
2030 o Minor features (relay, performance):
2031 - Always start relays with at least two worker threads, to prevent
2032 priority inversion on slow tasks. Part of the fix for bug 22883.
2033 - Allow background work to be queued with different priorities, so
2034 that a big pile of slow low-priority jobs will not starve out
2035 higher priority jobs. This lays the groundwork for a fix for
2038 o Minor bugfixes (build system, rust):
2039 - Fix a problem where Rust toolchains were not being found when
2040 building without --enable-cargo-online-mode, due to setting the
2041 $HOME environment variable instead of $CARGO_HOME. Fixes bug
2042 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
2044 o Minor bugfixes (compatibility, zstd):
2045 - Write zstd epilogues correctly when the epilogue requires
2046 reallocation of the output buffer, even with zstd 1.3.0.
2047 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
2048 22927; bugfix on 0.3.1.1-alpha.
2050 o Minor bugfixes (compilation warnings):
2051 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
2052 22915; bugfix on 0.2.8.1-alpha.
2053 - Fix warnings when building with libscrypt and openssl scrypt
2054 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2055 - Compile correctly when both openssl 1.1.0 and libscrypt are
2056 detected. Previously this would cause an error. Fixes bug 22892;
2057 bugfix on 0.3.1.1-alpha.
2058 - When building with certain versions of the mingw C header files,
2059 avoid float-conversion warnings when calling the C functions
2060 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2063 o Minor bugfixes (coverity build support):
2064 - Avoid Coverity build warnings related to our BUG() macro. By
2065 default, Coverity treats BUG() as the Linux kernel does: an
2066 instant abort(). We need to override that so our BUG() macro
2067 doesn't prevent Coverity from analyzing functions that use it.
2068 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2070 o Minor bugfixes (directory authority):
2071 - When a directory authority rejects a descriptor or extrainfo with
2072 a given digest, mark that digest as undownloadable, so that we do
2073 not attempt to download it again over and over. We previously
2074 tried to avoid downloading such descriptors by other means, but we
2075 didn't notice if we accidentally downloaded one anyway. This
2076 behavior became problematic in 0.2.7.2-alpha, when authorities
2077 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2080 o Minor bugfixes (error reporting, windows):
2081 - When formatting Windows error messages, use the English format to
2082 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
2085 o Minor bugfixes (file limits, osx):
2086 - When setting the maximum number of connections allowed by the OS,
2087 always allow some extra file descriptors for other files. Fixes
2088 bug 22797; bugfix on 0.2.0.10-alpha.
2090 o Minor bugfixes (linux seccomp2 sandbox):
2091 - Avoid a sandbox failure when trying to re-bind to a socket and
2092 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2094 o Minor bugfixes (memory leaks):
2095 - Fix a small memory leak when validating a configuration that uses
2096 two or more AF_UNIX sockets for the same port type. Fixes bug
2097 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
2099 o Minor bugfixes (unit tests):
2100 - test_consdiff_base64cmp would fail on OS X because while OS X
2101 follows the standard of (less than zero/zero/greater than zero),
2102 it doesn't follow the convention of (-1/0/+1). Make the test
2103 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
2104 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2105 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2108 Changes in version 0.3.1.4-alpha - 2017-06-29
2109 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
2110 to use a guard that was in the same network family as a chosen exit
2111 relay. This is a security regression; all clients running earlier
2112 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
2115 This release also fixes several other bugs introduced in 0.3.0.x
2116 and 0.3.1.x, including others that can affect bandwidth usage
2120 - To build with zstd and lzma support, Tor now requires the
2121 pkg-config tool at build time. (This requirement was new in
2122 0.3.1.1-alpha, but was not noted at the time. Noting it here to
2123 close ticket 22623.)
2125 o Major bugfixes (path selection, security):
2126 - When choosing which guard to use for a circuit, avoid the exit's
2127 family along with the exit itself. Previously, the new guard
2128 selection logic avoided the exit, but did not consider its family.
2129 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2130 006 and CVE-2017-0377.
2132 o Major bugfixes (compression, zstd):
2133 - Correctly detect a full buffer when decompressing a large zstd-
2134 compressed input. Previously, we would sometimes treat a full
2135 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
2137 o Major bugfixes (directory protocol):
2138 - Ensure that we send "304 Not modified" as HTTP status code when a
2139 client is attempting to fetch a consensus or consensus diff, and
2140 the best one we can send them is one they already have. Fixes bug
2141 22702; bugfix on 0.3.1.1-alpha.
2143 o Major bugfixes (entry guards):
2144 - When starting with an old consensus, do not add new entry guards
2145 unless the consensus is "reasonably live" (under 1 day old). Fixes
2146 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2148 o Minor features (bug mitigation, diagnostics, logging):
2149 - Avoid an assertion failure, and log a better error message, when
2150 unable to remove a file from the consensus cache on Windows.
2151 Attempts to mitigate and diagnose bug 22752.
2153 o Minor features (geoip):
2154 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
2157 o Minor bugfixes (compression):
2158 - When compressing or decompressing a buffer, check for a failure to
2159 create a compression object. Fixes bug 22626; bugfix
2161 - When decompressing a buffer, check for extra data after the end of
2162 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
2163 - When decompressing an object received over an anonymous directory
2164 connection, if we have already decompressed it using an acceptable
2165 compression method, do not reject it for looking like an
2166 unacceptable compression method. Fixes part of bug 22670; bugfix
2168 - When serving directory votes compressed with zlib, do not claim to
2169 have compressed them with zstd. Fixes bug 22669; bugfix
2171 - When spooling compressed data to an output buffer, don't try to
2172 spool more data when there is no more data to spool and we are not
2173 trying to flush the input. Previously, we would sometimes launch
2174 compression requests with nothing to do, which interferes with our
2175 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
2177 o Minor bugfixes (defensive programming):
2178 - Detect and break out of infinite loops in our compression code. We
2179 don't think that any such loops exist now, but it's best to be
2180 safe. Closes ticket 22672.
2181 - Fix a memset() off the end of an array when packing cells. This
2182 bug should be harmless in practice, since the corrupted bytes are
2183 still in the same structure, and are always padding bytes,
2184 ignored, or immediately overwritten, depending on compiler
2185 behavior. Nevertheless, because the memset()'s purpose is to make
2186 sure that any other cell-handling bugs can't expose bytes to the
2187 network, we need to fix it. Fixes bug 22737; bugfix on
2188 0.2.4.11-alpha. Fixes CID 1401591.
2190 o Minor bugfixes (linux seccomp2 sandbox):
2191 - Permit the fchmod system call, to avoid crashing on startup when
2192 starting with the seccomp2 sandbox and an unexpected set of
2193 permissions on the data directory or its contents. Fixes bug
2194 22516; bugfix on 0.2.5.4-alpha.
2195 - Fix a crash in the LZMA module, when the sandbox was enabled, and
2196 liblzma would allocate more than 16 MB of memory. We solve this by
2197 bumping the mprotect() limit in the sandbox module from 16 MB to
2198 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
2200 o Minor bugfixes (logging):
2201 - When decompressing, do not warn if we fail to decompress using a
2202 compression method that we merely guessed. Fixes part of bug
2203 22670; bugfix on 0.1.1.14-alpha.
2204 - When decompressing, treat mismatch between content-encoding and
2205 actual compression type as a protocol warning. Fixes part of bug
2206 22670; bugfix on 0.1.1.9-alpha.
2207 - Downgrade "assigned_to_cpuworker failed" message to info-level
2208 severity. In every case that can reach it, either a better warning
2209 has already been logged, or no warning is warranted. Fixes bug
2210 22356; bugfix on 0.2.6.3-alpha.
2211 - Demote a warn that was caused by libevent delays to info if
2212 netflow padding is less than 4.5 seconds late, or to notice
2213 if it is more (4.5 seconds is the amount of time that a netflow
2214 record might be emitted after, if we chose the maximum timeout).
2215 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
2217 o Minor bugfixes (process behavior):
2218 - When exiting because of an error, always exit with a nonzero exit
2219 status. Previously, we would fail to report an error in our exit
2220 status in cases related to __OwningControllerProcess failure,
2221 lockfile contention, and Ed25519 key initialization. Fixes bug
2222 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
2223 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
2227 - Add a manpage description for the key-pinning-journal file. Closes
2229 - Correctly note that bandwidth accounting values are stored in the
2230 state file, and the bw_accounting file is now obsolete. Closes
2232 - Document more of the files in the Tor data directory, including
2233 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
2234 approved-routers, sr-random, and diff-cache. Found while fixing
2238 Changes in version 0.3.0.9 - 2017-06-29
2239 Tor 0.3.0.9 fixes a path selection bug that would allow a client
2240 to use a guard that was in the same network family as a chosen exit
2241 relay. This is a security regression; all clients running earlier
2242 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
2245 This release also backports several other bugfixes from the 0.3.1.x
2248 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
2249 - When choosing which guard to use for a circuit, avoid the exit's
2250 family along with the exit itself. Previously, the new guard
2251 selection logic avoided the exit, but did not consider its family.
2252 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2253 006 and CVE-2017-0377.
2255 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
2256 - Don't block bootstrapping when a primary bridge is offline and we
2257 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2258 21969; bugfix on 0.3.0.3-alpha.
2260 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
2261 - When starting with an old consensus, do not add new entry guards
2262 unless the consensus is "reasonably live" (under 1 day old). Fixes
2263 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2265 o Minor features (geoip):
2266 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
2269 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
2270 - Reject version numbers with non-numeric prefixes (such as +, -, or
2271 whitespace). Disallowing whitespace prevents differential version
2272 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2273 and part of 21508; bugfix on 0.0.8pre1.
2275 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
2276 - Permit the fchmod system call, to avoid crashing on startup when
2277 starting with the seccomp2 sandbox and an unexpected set of
2278 permissions on the data directory or its contents. Fixes bug
2279 22516; bugfix on 0.2.5.4-alpha.
2281 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
2282 - Fix a memset() off the end of an array when packing cells. This
2283 bug should be harmless in practice, since the corrupted bytes are
2284 still in the same structure, and are always padding bytes,
2285 ignored, or immediately overwritten, depending on compiler
2286 behavior. Nevertheless, because the memset()'s purpose is to make
2287 sure that any other cell-handling bugs can't expose bytes to the
2288 network, we need to fix it. Fixes bug 22737; bugfix on
2289 0.2.4.11-alpha. Fixes CID 1401591.
2292 Changes in version 0.3.1.3-alpha - 2017-06-08
2293 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
2294 remotely crash a hidden service with an assertion failure. Anyone
2295 running a hidden service should upgrade to this version, or to some
2296 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
2298 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
2299 that sometimes made relays unreliable, as well as several other
2300 bugfixes described below.
2302 o Major bugfixes (hidden service, relay, security):
2303 - Fix a remotely triggerable assertion failure when a hidden service
2304 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2305 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2306 - Fix a remotely triggerable assertion failure caused by receiving a
2307 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2308 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2311 o Major bugfixes (relay, link handshake):
2312 - When performing the v3 link handshake on a TLS connection, report
2313 that we have the x509 certificate that we actually used on that
2314 connection, even if we have changed certificates since that
2315 connection was first opened. Previously, we would claim to have
2316 used our most recent x509 link certificate, which would sometimes
2317 make the link handshake fail. Fixes one case of bug 22460; bugfix
2320 o Major bugfixes (relays, key management):
2321 - Regenerate link and authentication certificates whenever the key
2322 that signs them changes; also, regenerate link certificates
2323 whenever the signed key changes. Previously, these processes were
2324 only weakly coupled, and we relays could (for minutes to hours)
2325 wind up with an inconsistent set of keys and certificates, which
2326 other relays would not accept. Fixes two cases of bug 22460;
2327 bugfix on 0.3.0.1-alpha.
2328 - When sending an Ed25519 signing->link certificate in a CERTS cell,
2329 send the certificate that matches the x509 certificate that we
2330 used on the TLS connection. Previously, there was a race condition
2331 if the TLS context rotated after we began the TLS handshake but
2332 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
2335 o Major bugfixes (torrc, crash):
2336 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
2337 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
2339 o Minor features (code style):
2340 - Add "Falls through" comments to our codebase, in order to silence
2341 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2342 Stieger. Closes ticket 22446.
2344 o Minor features (diagnostic):
2345 - Add logging messages to try to diagnose a rare bug that seems to
2346 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
2347 think this is happening because of incorrect system clocks, but
2348 we'd like to know for certain. Diagnostic for bug 22466.
2350 o Minor bugfixes (correctness):
2351 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2352 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2354 o Minor bugfixes (directory protocol):
2355 - Check for libzstd >= 1.1, because older versions lack the
2356 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
2358 o Minor bugfixes (link handshake):
2359 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2360 months, and regenerate it when it is within one month of expiring.
2361 Previously, we had generated this certificate at startup with a
2362 ten-year lifetime, but that could lead to weird behavior when Tor
2363 was started with a grossly inaccurate clock. Mitigates bug 22466;
2364 mitigation on 0.3.0.1-alpha.
2366 o Minor bugfixes (storage directories):
2367 - Always check for underflows in the cached storage directory usage.
2368 If the usage does underflow, re-calculate it. Also, avoid a
2369 separate underflow when the usage is not known. Fixes bug 22424;
2370 bugfix on 0.3.1.1-alpha.
2372 o Minor bugfixes (unit tests):
2373 - The unit tests now pass on systems where localhost is misconfigured
2374 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
2378 - Clarify the manpage for the (deprecated) torify script. Closes
2381 Changes in version 0.3.0.8 - 2017-06-08
2382 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
2383 remotely crash a hidden service with an assertion failure. Anyone
2384 running a hidden service should upgrade to this version, or to some
2385 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
2387 Tor 0.3.0.8 also includes fixes for several key management bugs
2388 that sometimes made relays unreliable, as well as several other
2389 bugfixes described below.
2391 o Major bugfixes (hidden service, relay, security, backport
2392 from 0.3.1.3-alpha):
2393 - Fix a remotely triggerable assertion failure when a hidden service
2394 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2395 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2396 - Fix a remotely triggerable assertion failure caused by receiving a
2397 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2398 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2401 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2402 - When performing the v3 link handshake on a TLS connection, report
2403 that we have the x509 certificate that we actually used on that
2404 connection, even if we have changed certificates since that
2405 connection was first opened. Previously, we would claim to have
2406 used our most recent x509 link certificate, which would sometimes
2407 make the link handshake fail. Fixes one case of bug 22460; bugfix
2410 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
2411 - Regenerate link and authentication certificates whenever the key
2412 that signs them changes; also, regenerate link certificates
2413 whenever the signed key changes. Previously, these processes were
2414 only weakly coupled, and we relays could (for minutes to hours)
2415 wind up with an inconsistent set of keys and certificates, which
2416 other relays would not accept. Fixes two cases of bug 22460;
2417 bugfix on 0.3.0.1-alpha.
2418 - When sending an Ed25519 signing->link certificate in a CERTS cell,
2419 send the certificate that matches the x509 certificate that we
2420 used on the TLS connection. Previously, there was a race condition
2421 if the TLS context rotated after we began the TLS handshake but
2422 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
2425 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
2426 - Stop rejecting v3 hidden service descriptors because their size
2427 did not match an old padding rule. Fixes bug 22447; bugfix on
2430 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2431 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2432 December 2016 (of which ~126 were still functional) with a list of
2433 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2434 2017. Resolves ticket 21564.
2436 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
2437 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
2438 bug 22252; bugfix on 0.2.9.3-alpha.
2440 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
2441 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2442 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2444 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
2445 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2446 months, and regenerate it when it is within one month of expiring.
2447 Previously, we had generated this certificate at startup with a
2448 ten-year lifetime, but that could lead to weird behavior when Tor
2449 was started with a grossly inaccurate clock. Mitigates bug 22466;
2450 mitigation on 0.3.0.1-alpha.
2452 o Minor bugfixes (memory leak, directory authority, backport from
2454 - When directory authorities reject a router descriptor due to
2455 keypinning, free the router descriptor rather than leaking the
2456 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2459 Changes in version 0.2.9.11 - 2017-06-08
2460 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
2461 remotely crash a hidden service with an assertion failure. Anyone
2462 running a hidden service should upgrade to this version, or to some
2463 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2464 are not affected by TROVE-2017-004.)
2466 Tor 0.2.9.11 also backports fixes for several key management bugs
2467 that sometimes made relays unreliable, as well as several other
2468 bugfixes described below.
2470 o Major bugfixes (hidden service, relay, security, backport
2471 from 0.3.1.3-alpha):
2472 - Fix a remotely triggerable assertion failure caused by receiving a
2473 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2474 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2477 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2478 - When performing the v3 link handshake on a TLS connection, report
2479 that we have the x509 certificate that we actually used on that
2480 connection, even if we have changed certificates since that
2481 connection was first opened. Previously, we would claim to have
2482 used our most recent x509 link certificate, which would sometimes
2483 make the link handshake fail. Fixes one case of bug 22460; bugfix
2486 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2487 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2488 December 2016 (of which ~126 were still functional) with a list of
2489 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2490 2017. Resolves ticket 21564.
2492 o Minor features (future-proofing, backport from 0.3.0.7):
2493 - Tor no longer refuses to download microdescriptors or descriptors if
2494 they are listed as "published in the future". This change will
2495 eventually allow us to stop listing meaningful "published" dates
2496 in microdescriptor consensuses, and thereby allow us to reduce the
2497 resources required to download consensus diffs by over 50%.
2498 Implements part of ticket 21642; implements part of proposal 275.
2500 o Minor features (directory authorities, backport from 0.3.0.4-rc)
2501 - Directory authorities now reject relays running versions
2502 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
2503 suffer from bug 20499 and don't keep their consensus cache
2504 up-to-date. Resolves ticket 20509.
2506 o Minor features (geoip):
2507 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2510 o Minor bugfixes (control port, backport from 0.3.0.6):
2511 - The GETINFO extra-info/digest/<digest> command was broken because
2512 of a wrong base16 decode return value check, introduced when
2513 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
2515 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
2516 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2517 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2519 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
2520 - The getpid() system call is now permitted under the Linux seccomp2
2521 sandbox, to avoid crashing with versions of OpenSSL (and other
2522 libraries) that attempt to learn the process's PID by using the
2523 syscall rather than the VDSO code. Fixes bug 21943; bugfix
2526 o Minor bugfixes (memory leak, directory authority, backport
2527 from 0.3.1.2-alpha):
2528 - When directory authorities reject a router descriptor due to
2529 keypinning, free the router descriptor rather than leaking the
2530 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2532 Changes in version 0.2.8.14 - 2017-06-08
2533 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2534 remotely crash a hidden service with an assertion failure. Anyone
2535 running a hidden service should upgrade to this version, or to some
2536 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2537 are not affected by TROVE-2017-004.)
2539 o Major bugfixes (hidden service, relay, security):
2540 - Fix a remotely triggerable assertion failure caused by receiving a
2541 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2542 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2545 o Minor features (geoip):
2546 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2549 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2550 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2551 December 2016 (of which ~126 were still functional) with a list of
2552 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2553 2017. Resolves ticket 21564.
2555 o Minor bugfixes (correctness):
2556 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2557 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2559 Changes in version 0.2.7.8 - 2017-06-08
2560 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2561 remotely crash a hidden service with an assertion failure. Anyone
2562 running a hidden service should upgrade to this version, or to some
2563 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2564 are not affected by TROVE-2017-004.)
2566 o Major bugfixes (hidden service, relay, security):
2567 - Fix a remotely triggerable assertion failure caused by receiving a
2568 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2569 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2572 o Minor features (geoip):
2573 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2576 o Minor bugfixes (correctness):
2577 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2578 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2581 Changes in version 0.2.6.12 - 2017-06-08
2582 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
2583 remotely crash a hidden service with an assertion failure. Anyone
2584 running a hidden service should upgrade to this version, or to some
2585 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2586 are not affected by TROVE-2017-004.)
2588 o Major bugfixes (hidden service, relay, security):
2589 - Fix a remotely triggerable assertion failure caused by receiving a
2590 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2591 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2594 o Minor features (geoip):
2595 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2598 o Minor bugfixes (correctness):
2599 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2600 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2602 Changes in version 0.2.5.14 - 2017-06-08
2603 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
2604 remotely crash a hidden service with an assertion failure. Anyone
2605 running a hidden service should upgrade to this version, or to some
2606 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2607 are not affected by TROVE-2017-004.)
2609 o Major bugfixes (hidden service, relay, security):
2610 - Fix a remotely triggerable assertion failure caused by receiving a
2611 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2612 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2615 o Minor features (geoip):
2616 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2619 o Minor bugfixes (correctness):
2620 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2621 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2623 Changes in version 0.2.4.29 - 2017-06-08
2624 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
2625 remotely crash a hidden service with an assertion failure. Anyone
2626 running a hidden service should upgrade to this version, or to some
2627 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2628 are not affected by TROVE-2017-004.)
2630 o Major bugfixes (hidden service, relay, security):
2631 - Fix a remotely triggerable assertion failure caused by receiving a
2632 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2633 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2636 o Minor features (geoip):
2637 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2640 o Minor bugfixes (correctness):
2641 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2642 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2645 Changes in version 0.3.1.2-alpha - 2017-05-26
2646 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
2647 fixes a few bugs found while testing 0.3.1.1-alpha, including a
2648 memory corruption bug that affected relay stability.
2650 o Major bugfixes (crash, relay):
2651 - Fix a memory-corruption bug in relays that set MyFamily.
2652 Previously, they would double-free MyFamily elements when making
2653 the next descriptor or when changing their configuration. Fixes
2654 bug 22368; bugfix on 0.3.1.1-alpha.
2656 o Minor bugfixes (logging):
2657 - Log a better message when a directory authority replies to an
2658 upload with an unexpected status code. Fixes bug 11121; bugfix
2661 o Minor bugfixes (memory leak, directory authority):
2662 - When directory authorities reject a router descriptor due to
2663 keypinning, free the router descriptor rather than leaking the
2664 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2667 Changes in version 0.3.1.1-alpha - 2017-05-22
2668 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
2669 reduces the bandwidth usage for Tor's directory protocol, adds some
2670 basic padding to resist netflow-based traffic analysis and to serve as
2671 the basis of other padding in the future, and adds rust support to the
2674 It also contains numerous other small features and improvements to
2675 security, correctness, and performance.
2677 Below are the changes since 0.3.0.7.
2679 o Major features (directory protocol):
2680 - Tor relays and authorities can now serve clients an abbreviated
2681 version of the consensus document, containing only the changes
2682 since an older consensus document that the client holds. Clients
2683 now request these documents when available. When both client and
2684 server use this new protocol, they will use far less bandwidth (up
2685 to 94% less) to keep the client's consensus up-to-date. Implements
2686 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
2687 - Tor can now compress directory traffic with lzma or with zstd
2688 compression algorithms, which can deliver better bandwidth
2689 performance. Because lzma is computationally expensive, it's only
2690 used for documents that can be compressed once and served many
2691 times. Support for these algorithms requires that tor is built
2692 with the libzstd and/or liblzma libraries available. Implements
2693 proposal 278; closes ticket 21662.
2694 - Relays now perform the more expensive compression operations, and
2695 consensus diff generation, in worker threads. This separation
2696 avoids delaying the main thread when a new consensus arrives.
2698 o Major features (experimental):
2699 - Tor can now build modules written in Rust. To turn this on, pass
2700 the "--enable-rust" flag to the configure script. It's not time to
2701 get excited yet: currently, there is no actual Rust functionality
2702 beyond some simple glue code, and a notice at startup to tell you
2703 that Rust is running. Still, we hope that programmers and
2704 packagers will try building Tor with Rust support, so that we can
2705 find issues and solve portability problems. Closes ticket 22106.
2707 o Major features (traffic analysis resistance):
2708 - Connections between clients and relays now send a padding cell in
2709 each direction every 1.5 to 9.5 seconds (tunable via consensus
2710 parameters). This padding will not resist specialized
2711 eavesdroppers, but it should be enough to make many ISPs' routine
2712 network flow logging less useful in traffic analysis against
2715 Padding is negotiated using Tor's link protocol, so both relays
2716 and clients must upgrade for this to take effect. Clients may
2717 still send padding despite the relay's version by setting
2718 ConnectionPadding 1 in torrc, and may disable padding by setting
2719 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
2720 users with the torrc option ReducedConnectionPadding. Implements
2721 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
2722 - Relays will publish 24 hour totals of padding and non-padding cell
2723 counts to their extra-info descriptors, unless PaddingStatistics 0
2724 is set in torrc. These 24 hour totals are also rounded to
2727 o Major bugfixes (connection usage):
2728 - We use NETINFO cells to try to determine if both relays involved
2729 in a connection will agree on the canonical status of that
2730 connection. We prefer the connections where this is the case for
2731 extend cells, and try to close connections where relays disagree
2732 on their canonical status early. Also, we now prefer the oldest
2733 valid connection for extend cells. These two changes should reduce
2734 the number of long-term connections that are kept open between
2735 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
2736 - Relays now log hourly statistics (look for
2737 "channel_check_for_duplicates" lines) on the total number of
2738 connections to other relays. If the number of connections per
2739 relay is unexpectedly large, this log message is at notice level.
2740 Otherwise it is at info.
2742 o Major bugfixes (entry guards):
2743 - Don't block bootstrapping when a primary bridge is offline and we
2744 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2745 21969; bugfix on 0.3.0.3-alpha.
2747 o Major bugfixes (linux TPROXY support):
2748 - Fix a typo that had prevented TPROXY-based transparent proxying
2749 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2750 Patch from "d4fq0fQAgoJ".
2752 o Minor features (security, windows):
2753 - Enable a couple of pieces of Windows hardening: one
2754 (HeapEnableTerminationOnCorruption) that has been on-by-default
2755 since Windows 8, and unavailable before Windows 7; and one
2756 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2757 affect us, but shouldn't do any harm. Closes ticket 21953.
2759 o Minor features (config options):
2760 - Allow "%include" directives in torrc configuration files. These
2761 directives import the settings from other files, or from all the
2762 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
2763 - Make SAVECONF return an error when overwriting a torrc that has
2764 includes. Using SAVECONF with the FORCE option will allow it to
2765 overwrite torrc even if includes are used. Related to ticket 1922.
2766 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
2767 will work without the FORCE option. Related to ticket 1922.
2769 o Minor features (controller):
2770 - Warn the first time that a controller requests data in the long-
2771 deprecated 'GETINFO network-status' format. Closes ticket 21703.
2773 o Minor features (defaults):
2774 - The default value for UseCreateFast is now 0: clients which
2775 haven't yet received a consensus document will now use a proper
2776 ntor handshake to talk to their directory servers whenever they
2777 can. Closes ticket 21407.
2778 - Onion key rotation and expiry intervals are now defined as a
2779 network consensus parameter, per proposal 274. The default
2780 lifetime of an onion key is increased from 7 to 28 days. Old onion
2781 keys will expire after 7 days by default. This change will make
2782 consensus diffs much smaller, and save significant bandwidth.
2783 Closes ticket 21641.
2785 o Minor features (fallback directory list):
2786 - Update the fallback directory mirror whitelist and blacklist based
2787 on operator emails. Closes task 21121.
2788 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2789 December 2016 (of which ~126 were still functional) with a list of
2790 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2791 2017. Resolves ticket 21564.
2793 o Minor features (hidden services, logging):
2794 - Log a message when a hidden service descriptor has fewer
2795 introduction points than specified in
2796 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
2797 - Log a message when a hidden service reaches its introduction point
2798 circuit limit, and when that limit is reset. Follow up to ticket
2799 21594; closes ticket 21622.
2800 - Warn user if multiple entries in EntryNodes and at least one
2801 HiddenService are used together. Pinning EntryNodes along with a
2802 hidden service can be possibly harmful; for instance see ticket
2803 14917 or 21155. Closes ticket 21155.
2805 o Minor features (linux seccomp2 sandbox):
2806 - We now have a document storage backend compatible with the Linux
2807 seccomp2 sandbox. This backend is used for consensus documents and
2808 diffs between them; in the long term, we'd like to use it for
2809 unparseable directory material too. Closes ticket 21645
2810 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
2811 from 1MB to 16MB. This was necessary with the glibc allocator in
2812 order to allow worker threads to allocate more memory -- which in
2813 turn is necessary because of our new use of worker threads for
2814 compression. Closes ticket 22096.
2816 o Minor features (logging):
2817 - Log files are no longer created world-readable by default.
2818 (Previously, most distributors would store the logs in a non-
2819 world-readable location to prevent inappropriate access. This
2820 change is an extra precaution.) Closes ticket 21729; patch
2823 o Minor features (performance):
2824 - Our Keccak (SHA-3) implementation now accesses memory more
2825 efficiently, especially on little-endian systems. Closes
2827 - Add an O(1) implementation of channel_find_by_global_id(), to
2828 speed some controller functions.
2830 o Minor features (relay, configuration):
2831 - The MyFamily option may now be repeated as many times as desired,
2832 for relays that want to configure large families. Closes ticket
2833 4998; patch by Daniel Pinto.
2835 o Minor features (safety):
2836 - Add an explicit check to extrainfo_parse_entry_from_string() for
2837 NULL inputs. We don't believe this can actually happen, but it may
2838 help silence a warning from the Clang analyzer. Closes
2841 o Minor features (testing):
2842 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
2843 When Tor is compiled with this option, we disable a number of
2844 redundant memory-safety failsafes that are intended to stop bugs
2845 from becoming security issues. This makes it easier to hunt for
2846 bugs that would be security issues without the failsafes turned
2847 on. Closes ticket 21439.
2848 - Add a general event-tracing instrumentation support to Tor. This
2849 subsystem will enable developers and researchers to add fine-
2850 grained instrumentation to their Tor instances, for use when
2851 examining Tor network performance issues. There are no trace
2852 events yet, and event-tracing is off by default unless enabled at
2853 compile time. Implements ticket 13802.
2854 - Improve our version parsing tests: add tests for typical version
2855 components, add tests for invalid versions, including numeric
2856 range and non-numeric prefixes. Unit tests 21278, 21450, and
2857 21507. Partially implements 21470.
2859 o Minor bugfixes (bandwidth accounting):
2860 - Roll over monthly accounting at the configured hour and minute,
2861 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2862 Found by Andrey Karpov with PVS-Studio.
2864 o Minor bugfixes (code correctness):
2865 - Accurately identify client connections by their lack of peer
2866 authentication. This means that we bail out earlier if asked to
2867 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
2870 o Minor bugfixes (configuration):
2871 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
2872 bug 22252; bugfix on 0.2.9.3-alpha.
2874 o Minor bugfixes (connection lifespan):
2875 - Allow more control over how long TLS connections are kept open:
2876 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
2877 single option called CircuitsAvailableTimeout. Also, allow the
2878 consensus to control the default values for both this preference
2879 and the lifespan of relay-to-relay connections. Fixes bug 17592;
2880 bugfix on 0.2.5.5-alpha.
2881 - Increase the initial circuit build timeout testing frequency, to
2882 help ensure that ReducedConnectionPadding clients finish learning
2883 a timeout before their orconn would expire. The initial testing
2884 rate was set back in the days of TAP and before the Tor Browser
2885 updater, when we had to be much more careful about new clients
2886 making lots of circuits. With this change, a circuit build timeout
2887 is learned in about 15-20 minutes, instead of 100-120 minutes.
2889 o Minor bugfixes (controller):
2890 - GETINFO onions/current and onions/detached no longer respond with
2891 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
2892 - Trigger HS descriptor events on the control port when the client
2893 fails to pick a hidden service directory for a hidden service.
2894 This can happen if all the hidden service directories are in
2895 ExcludeNodes, or they have all been queried within the last 15
2896 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
2898 o Minor bugfixes (directory authority):
2899 - When rejecting a router descriptor for running an obsolete version
2900 of Tor without ntor support, warn about the obsolete tor version,
2901 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2902 - Prevent the shared randomness subsystem from asserting when
2903 initialized by a bridge authority with an incomplete configuration
2904 file. Fixes bug 21586; bugfix on 0.2.9.8.
2906 o Minor bugfixes (exit-side DNS):
2907 - Fix an untriggerable assertion that checked the output of a
2908 libevent DNS error, so that the assertion actually behaves as
2909 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
2910 Karpov using PVS-Studio.
2912 o Minor bugfixes (fallback directories):
2913 - Make the usage example in updateFallbackDirs.py actually work, and
2914 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
2915 - Decrease the guard flag average required to be a fallback. This
2916 allows us to keep relays that have their guard flag removed when
2917 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2918 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
2919 bugfix on 0.2.8.1-alpha.
2920 - Make sure fallback directory mirrors have the same address, port,
2921 and relay identity key for at least 30 days before they are
2922 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2924 o Minor bugfixes (hidden services):
2925 - Stop printing a cryptic warning when a hidden service gets a
2926 request to connect to a virtual port that it hasn't configured.
2927 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
2928 - Simplify hidden service descriptor creation by using an existing
2929 flag to check if an introduction point is established. Fixes bug
2930 21599; bugfix on 0.2.7.2-alpha.
2932 o Minor bugfixes (memory leak):
2933 - Fix a small memory leak at exit from the backtrace handler code.
2934 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
2936 o Minor bugfixes (protocol, logging):
2937 - Downgrade a log statement about unexpected relay cells from "bug"
2938 to "protocol warning", because there is at least one use case
2939 where it can be triggered by a buggy tor implementation. Fixes bug
2940 21293; bugfix on 0.1.1.14-alpha.
2942 o Minor bugfixes (testing):
2943 - Use unbuffered I/O for utility functions around the
2944 process_handle_t type. This fixes unit test failures reported on
2945 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
2946 - Make display of captured unit test log messages consistent. Fixes
2947 bug 21510; bugfix on 0.2.9.3-alpha.
2948 - Make test-network.sh always call chutney's test-network.sh.
2949 Previously, this only worked on systems which had bash installed,
2950 due to some bash-specific code in the script. Fixes bug 19699;
2951 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
2953 o Minor bugfixes (voting consistency):
2954 - Reject version numbers with non-numeric prefixes (such as +, -, or
2955 whitespace). Disallowing whitespace prevents differential version
2956 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2957 and part of 21508; bugfix on 0.0.8pre1.
2959 o Minor bugfixes (windows, relay):
2960 - Resolve "Failure from drain_fd: No error" warnings on Windows
2961 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
2963 o Code simplification and refactoring:
2964 - Break up the 630-line function connection_dir_client_reached_eof()
2965 into a dozen smaller functions. This change should help
2966 maintainability and readability of the client directory code.
2967 - Isolate our use of the openssl headers so that they are only
2968 included from our crypto wrapper modules, and from tests that
2969 examine those modules' internals. Closes ticket 21841.
2970 - Simplify our API to launch directory requests, making it more
2971 extensible and less error-prone. Now it's easier to add extra
2972 headers to directory requests. Closes ticket 21646.
2973 - Our base64 decoding functions no longer overestimate the output
2974 space that they need when parsing unpadded inputs. Closes
2976 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
2977 Resolves ticket 22213.
2978 - The logic that directory caches use to spool request to clients,
2979 serving them one part at a time so as not to allocate too much
2980 memory, has been refactored for consistency. Previously there was
2981 a separate spooling implementation per type of spoolable data. Now
2982 there is one common spooling implementation, with extensible data
2983 types. Closes ticket 21651.
2984 - Tor's compression module now supports multiple backends. Part of
2985 the implementation for proposal 278; closes ticket 21663.
2988 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
2989 Closes ticket 21873.
2990 - Correct documentation about the default DataDirectory value.
2991 Closes ticket 21151.
2992 - Document the default behavior of NumEntryGuards and
2993 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
2995 - Document key=value pluggable transport arguments for Bridge lines
2996 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
2997 - Note that bandwidth-limiting options don't affect TCP headers or
2998 DNS. Closes ticket 17170.
3000 o Removed features (configuration options, all in ticket 22060):
3001 - These configuration options are now marked Obsolete, and no longer
3002 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
3003 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
3004 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
3005 in 0.2.9.2-alpha and have now been removed. The previous default
3006 behavior is now always chosen; the previous (less secure) non-
3007 default behavior is now unavailable.
3008 - CloseHSClientCircuitsImmediatelyOnTimeout and
3009 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
3010 0.2.9.2-alpha and now have been removed. HS circuits never close
3011 on circuit build timeout; they have a longer timeout period.
3012 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
3013 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
3014 (and others) to configure listen-only and advertise-only addresses.
3016 o Removed features (tools):
3017 - We've removed the tor-checkkey tool from src/tools. Long ago, we
3018 used it to help people detect RSA keys that were generated by
3019 versions of Debian affected by CVE-2008-0166. But those keys have
3020 been out of circulation for ages, and this tool is no longer
3021 required. Closes ticket 21842.
3024 Changes in version 0.3.0.7 - 2017-05-15
3025 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
3026 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
3027 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
3028 clients are not affected.
3030 o Major bugfixes (hidden service directory, security):
3031 - Fix an assertion failure in the hidden service directory code, which
3032 could be used by an attacker to remotely cause a Tor relay process to
3033 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
3034 should upgrade. This security issue is tracked as TROVE-2017-002.
3035 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
3038 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3041 o Minor features (future-proofing):
3042 - Tor no longer refuses to download microdescriptors or descriptors
3043 if they are listed as "published in the future". This change will
3044 eventually allow us to stop listing meaningful "published" dates
3045 in microdescriptor consensuses, and thereby allow us to reduce the
3046 resources required to download consensus diffs by over 50%.
3047 Implements part of ticket 21642; implements part of proposal 275.
3049 o Minor bugfixes (Linux seccomp2 sandbox):
3050 - The getpid() system call is now permitted under the Linux seccomp2
3051 sandbox, to avoid crashing with versions of OpenSSL (and other
3052 libraries) that attempt to learn the process's PID by using the
3053 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3057 Changes in version 0.3.0.6 - 2017-04-26
3058 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
3060 With the 0.3.0 series, clients and relays now use Ed25519 keys to
3061 authenticate their link connections to relays, rather than the old
3062 RSA1024 keys that they used before. (Circuit crypto has been
3063 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
3064 the guard selection and replacement algorithm to behave more robustly
3065 in the presence of unreliable networks, and to resist guard-
3068 This series also includes numerous other small features and bugfixes,
3069 along with more groundwork for the upcoming hidden-services revamp.
3071 Per our stable release policy, we plan to support the Tor 0.3.0
3072 release series for at least the next nine months, or for three months
3073 after the first stable release of the 0.3.1 series: whichever is
3074 longer. If you need a release with long-term support, we recommend
3075 that you stay with the 0.2.9 series.
3077 Below are the changes since 0.3.0.5-rc. For a list of all changes
3078 since 0.2.9, see the ReleaseNotes file.
3080 o Minor features (geoip):
3081 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
3084 o Minor bugfixes (control port):
3085 - The GETINFO extra-info/digest/<digest> command was broken because
3086 of a wrong base16 decode return value check, introduced when
3087 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3089 o Minor bugfixes (crash prevention):
3090 - Fix a (currently untriggerable, but potentially dangerous) crash
3091 bug when base32-encoding inputs whose sizes are not a multiple of
3092 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
3095 Changes in version 0.3.0.5-rc - 2017-04-05
3096 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
3097 0.3.0 release series.
3099 This is the second release candidate in the Tor 0.3.0 series, and has
3100 much fewer changes than the first. If we find no new bugs or
3101 regressions here, the first stable 0.3.0 release will be nearly
3104 o Major bugfixes (crash, directory connections):
3105 - Fix a rare crash when sending a begin cell on a circuit whose
3106 linked directory connection had already been closed. Fixes bug
3107 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3109 o Major bugfixes (guard selection):
3110 - Fix a guard selection bug where Tor would refuse to bootstrap in
3111 some cases if the user swapped a bridge for another bridge in
3112 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
3113 Reported by "torvlnt33r".
3115 o Minor features (geoip):
3116 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
3119 o Minor bugfix (compilation):
3120 - Fix a warning when compiling hs_service.c. Previously, it had no
3121 exported symbols when compiled for libor.a, resulting in a
3122 compilation warning from clang. Fixes bug 21825; bugfix
3125 o Minor bugfixes (hidden services):
3126 - Make hidden services check for failed intro point connections,
3127 even when they have exceeded their intro point creation limit.
3128 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
3129 - Make hidden services with 8 to 10 introduction points check for
3130 failed circuits immediately after startup. Previously, they would
3131 wait for 5 minutes before performing their first checks. Fixes bug
3132 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
3134 o Minor bugfixes (memory leaks):
3135 - Fix a memory leak when using GETCONF on a port option. Fixes bug
3136 21682; bugfix on 0.3.0.3-alpha.
3138 o Minor bugfixes (relay):
3139 - Avoid a double-marked-circuit warning that could happen when we
3140 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3143 o Minor bugfixes (tests):
3144 - Run the entry_guard_parse_from_state_full() test with the time set
3145 to a specific date. (The guard state that this test was parsing
3146 contained guards that had expired since the test was first
3147 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
3150 - Update the description of the directory server options in the
3151 manual page, to clarify that a relay no longer needs to set
3152 DirPort in order to be a directory cache. Closes ticket 21720.
3156 Changes in version 0.2.8.13 - 2017-03-03
3157 Tor 0.2.8.13 backports a security fix from later Tor
3158 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
3159 this release, if for some reason they cannot upgrade to a later
3160 release series, and if they build Tor with the --enable-expensive-hardening
3163 Note that support for Tor 0.2.8.x is ending next year: we will not issue
3164 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
3165 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3167 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3168 - Fix an integer underflow bug when comparing malformed Tor
3169 versions. This bug could crash Tor when built with
3170 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3171 0.2.9.8, which were built with -ftrapv by default. In other cases
3172 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3173 on 0.0.8pre1. Found by OSS-Fuzz.
3175 o Minor features (geoip):
3176 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3180 Changes in version 0.2.7.7 - 2017-03-03
3181 Tor 0.2.7.7 backports a number of security fixes from later Tor
3182 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
3183 this release, if for some reason they cannot upgrade to a later
3186 Note that support for Tor 0.2.7.x is ending this year: we will not issue
3187 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
3188 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3190 o Directory authority changes (backport from 0.2.8.5-rc):
3191 - Urras is no longer a directory authority. Closes ticket 19271.
3193 o Directory authority changes (backport from 0.2.9.2-alpha):
3194 - The "Tonga" bridge authority has been retired; the new bridge
3195 authority is "Bifroest". Closes tickets 19728 and 19690.
3197 o Directory authority key updates (backport from 0.2.8.1-alpha):
3198 - Update the V3 identity key for the dannenberg directory authority:
3199 it was changed on 18 November 2015. Closes task 17906. Patch
3202 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3203 - Fix a bug in parsing that could cause clients to read a single
3204 byte past the end of an allocated region. This bug could be used
3205 to cause hardened clients (built with --enable-expensive-hardening)
3206 to crash if they tried to visit a hostile hidden service. Non-
3207 hardened clients are only affected depending on the details of
3208 their platform's memory allocator. Fixes bug 21018; bugfix on
3209 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3210 2016-12-002 and as CVE-2016-1254.
3212 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3213 - Stop a crash that could occur when a client running with DNSPort
3214 received a query with multiple address types, and the first
3215 address type was not supported. Found and fixed by Scott Dial.
3216 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3217 - Prevent a class of security bugs caused by treating the contents
3218 of a buffer chunk as if they were a NUL-terminated string. At
3219 least one such bug seems to be present in all currently used
3220 versions of Tor, and would allow an attacker to remotely crash
3221 most Tor instances, especially those compiled with extra compiler
3222 hardening. With this defense in place, such bugs can't crash Tor,
3223 though we should still fix them as they occur. Closes ticket
3224 20384 (TROVE-2016-10-001).
3226 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3227 - Avoid a difficult-to-trigger heap corruption attack when extending
3228 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3229 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3230 Reported by Guido Vranken.
3232 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3233 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3234 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3236 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3237 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3238 pointer to the previous (uninitialized) key value. The impact here
3239 should be limited to a difficult-to-trigger crash, if OpenSSL is
3240 running an engine that makes key generation failures possible, or
3241 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3242 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3245 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3246 - Fix an integer underflow bug when comparing malformed Tor
3247 versions. This bug could crash Tor when built with
3248 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3249 0.2.9.8, which were built with -ftrapv by default. In other cases
3250 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3251 on 0.0.8pre1. Found by OSS-Fuzz.
3253 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3254 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3255 zero size. Check size argument to memwipe() for underflow. Fixes
3256 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3259 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3260 - Make Tor survive errors involving connections without a
3261 corresponding event object. Previously we'd fail with an
3262 assertion; now we produce a log message. Related to bug 16248.
3264 o Minor features (geoip):
3265 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3269 Changes in version 0.2.6.11 - 2017-03-03
3270 Tor 0.2.6.11 backports a number of security fixes from later Tor
3271 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
3272 this release, if for some reason they cannot upgrade to a later
3275 Note that support for Tor 0.2.6.x is ending this year: we will not issue
3276 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
3277 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3279 o Directory authority changes (backport from 0.2.8.5-rc):
3280 - Urras is no longer a directory authority. Closes ticket 19271.
3282 o Directory authority changes (backport from 0.2.9.2-alpha):
3283 - The "Tonga" bridge authority has been retired; the new bridge
3284 authority is "Bifroest". Closes tickets 19728 and 19690.
3286 o Directory authority key updates (backport from 0.2.8.1-alpha):
3287 - Update the V3 identity key for the dannenberg directory authority:
3288 it was changed on 18 November 2015. Closes task 17906. Patch
3291 o Major features (security fixes, backport from 0.2.9.4-alpha):
3292 - Prevent a class of security bugs caused by treating the contents
3293 of a buffer chunk as if they were a NUL-terminated string. At
3294 least one such bug seems to be present in all currently used
3295 versions of Tor, and would allow an attacker to remotely crash
3296 most Tor instances, especially those compiled with extra compiler
3297 hardening. With this defense in place, such bugs can't crash Tor,
3298 though we should still fix them as they occur. Closes ticket
3299 20384 (TROVE-2016-10-001).
3301 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3302 - Fix a bug in parsing that could cause clients to read a single
3303 byte past the end of an allocated region. This bug could be used
3304 to cause hardened clients (built with --enable-expensive-hardening)
3305 to crash if they tried to visit a hostile hidden service. Non-
3306 hardened clients are only affected depending on the details of
3307 their platform's memory allocator. Fixes bug 21018; bugfix on
3308 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3309 2016-12-002 and as CVE-2016-1254.
3311 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3312 - Stop a crash that could occur when a client running with DNSPort
3313 received a query with multiple address types, and the first
3314 address type was not supported. Found and fixed by Scott Dial.
3315 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3317 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3318 - Fix an error that could cause us to read 4 bytes before the
3319 beginning of an openssl string. This bug could be used to cause
3320 Tor to crash on systems with unusual malloc implementations, or
3321 systems with unusual hardening installed. Fixes bug 17404; bugfix
3324 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3325 - Avoid a difficult-to-trigger heap corruption attack when extending
3326 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3327 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3328 Reported by Guido Vranken.
3330 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3331 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3332 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3334 o Major bugfixes (guard selection, backport from 0.2.7.6):
3335 - Actually look at the Guard flag when selecting a new directory
3336 guard. When we implemented the directory guard design, we
3337 accidentally started treating all relays as if they have the Guard
3338 flag during guard selection, leading to weaker anonymity and worse
3339 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3342 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3343 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3344 pointer to the previous (uninitialized) key value. The impact here
3345 should be limited to a difficult-to-trigger crash, if OpenSSL is
3346 running an engine that makes key generation failures possible, or
3347 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3348 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3351 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3352 - Fix an integer underflow bug when comparing malformed Tor
3353 versions. This bug could crash Tor when built with
3354 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3355 0.2.9.8, which were built with -ftrapv by default. In other cases
3356 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3357 on 0.0.8pre1. Found by OSS-Fuzz.
3359 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3360 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3361 zero size. Check size argument to memwipe() for underflow. Fixes
3362 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3365 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3366 - Make Tor survive errors involving connections without a
3367 corresponding event object. Previously we'd fail with an
3368 assertion; now we produce a log message. Related to bug 16248.
3370 o Minor features (geoip):
3371 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3374 o Minor bugfixes (compilation, backport from 0.2.7.6):
3375 - Fix a compilation warning with Clang 3.6: Do not check the
3376 presence of an address which can never be NULL. Fixes bug 17781.
3379 Changes in version 0.2.5.13 - 2017-03-03
3380 Tor 0.2.5.13 backports a number of security fixes from later Tor
3381 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
3382 this release, if for some reason they cannot upgrade to a later
3385 Note that support for Tor 0.2.5.x is ending next year: we will not issue
3386 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
3387 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3389 o Directory authority changes (backport from 0.2.8.5-rc):
3390 - Urras is no longer a directory authority. Closes ticket 19271.
3392 o Directory authority changes (backport from 0.2.9.2-alpha):
3393 - The "Tonga" bridge authority has been retired; the new bridge
3394 authority is "Bifroest". Closes tickets 19728 and 19690.
3396 o Directory authority key updates (backport from 0.2.8.1-alpha):
3397 - Update the V3 identity key for the dannenberg directory authority:
3398 it was changed on 18 November 2015. Closes task 17906. Patch
3401 o Major features (security fixes, backport from 0.2.9.4-alpha):
3402 - Prevent a class of security bugs caused by treating the contents
3403 of a buffer chunk as if they were a NUL-terminated string. At
3404 least one such bug seems to be present in all currently used
3405 versions of Tor, and would allow an attacker to remotely crash
3406 most Tor instances, especially those compiled with extra compiler
3407 hardening. With this defense in place, such bugs can't crash Tor,
3408 though we should still fix them as they occur. Closes ticket
3409 20384 (TROVE-2016-10-001).
3411 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3412 - Fix a bug in parsing that could cause clients to read a single
3413 byte past the end of an allocated region. This bug could be used
3414 to cause hardened clients (built with --enable-expensive-hardening)
3415 to crash if they tried to visit a hostile hidden service. Non-
3416 hardened clients are only affected depending on the details of
3417 their platform's memory allocator. Fixes bug 21018; bugfix on
3418 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3419 2016-12-002 and as CVE-2016-1254.
3421 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3422 - Stop a crash that could occur when a client running with DNSPort
3423 received a query with multiple address types, and the first
3424 address type was not supported. Found and fixed by Scott Dial.
3425 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3427 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3428 - Fix an error that could cause us to read 4 bytes before the
3429 beginning of an openssl string. This bug could be used to cause
3430 Tor to crash on systems with unusual malloc implementations, or
3431 systems with unusual hardening installed. Fixes bug 17404; bugfix
3434 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3435 - Avoid a difficult-to-trigger heap corruption attack when extending
3436 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3437 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3438 Reported by Guido Vranken.
3440 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3441 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3442 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3444 o Major bugfixes (guard selection, backport from 0.2.7.6):
3445 - Actually look at the Guard flag when selecting a new directory
3446 guard. When we implemented the directory guard design, we
3447 accidentally started treating all relays as if they have the Guard
3448 flag during guard selection, leading to weaker anonymity and worse
3449 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3452 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3453 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3454 pointer to the previous (uninitialized) key value. The impact here
3455 should be limited to a difficult-to-trigger crash, if OpenSSL is
3456 running an engine that makes key generation failures possible, or
3457 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3458 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3461 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3462 - Fix an integer underflow bug when comparing malformed Tor
3463 versions. This bug could crash Tor when built with
3464 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3465 0.2.9.8, which were built with -ftrapv by default. In other cases
3466 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3467 on 0.0.8pre1. Found by OSS-Fuzz.
3469 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3470 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3471 zero size. Check size argument to memwipe() for underflow. Fixes
3472 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3475 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3476 - Make Tor survive errors involving connections without a
3477 corresponding event object. Previously we'd fail with an
3478 assertion; now we produce a log message. Related to bug 16248.
3480 o Minor features (geoip):
3481 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3484 o Minor bugfixes (compilation, backport from 0.2.7.6):
3485 - Fix a compilation warning with Clang 3.6: Do not check the
3486 presence of an address which can never be NULL. Fixes bug 17781.
3488 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
3489 - Check for failures from crypto_early_init, and refuse to continue.
3490 A previous typo meant that we could keep going with an
3491 uninitialized crypto library, and would have OpenSSL initialize
3492 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
3493 when implementing ticket 4900. Patch by "teor".
3495 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3496 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3497 a client authorized hidden service. Fixes bug 15823; bugfix
3501 Changes in version 0.2.4.28 - 2017-03-03
3502 Tor 0.2.4.28 backports a number of security fixes from later Tor
3503 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
3504 this release, if for some reason they cannot upgrade to a later
3507 Note that support for Tor 0.2.4.x is ending soon: we will not issue
3508 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
3509 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
3511 o Directory authority changes (backport from 0.2.8.5-rc):
3512 - Urras is no longer a directory authority. Closes ticket 19271.
3514 o Directory authority changes (backport from 0.2.9.2-alpha):
3515 - The "Tonga" bridge authority has been retired; the new bridge
3516 authority is "Bifroest". Closes tickets 19728 and 19690.
3518 o Directory authority key updates (backport from 0.2.8.1-alpha):
3519 - Update the V3 identity key for the dannenberg directory authority:
3520 it was changed on 18 November 2015. Closes task 17906. Patch
3523 o Major features (security fixes, backport from 0.2.9.4-alpha):
3524 - Prevent a class of security bugs caused by treating the contents
3525 of a buffer chunk as if they were a NUL-terminated string. At
3526 least one such bug seems to be present in all currently used
3527 versions of Tor, and would allow an attacker to remotely crash
3528 most Tor instances, especially those compiled with extra compiler
3529 hardening. With this defense in place, such bugs can't crash Tor,
3530 though we should still fix them as they occur. Closes ticket
3531 20384 (TROVE-2016-10-001).
3533 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3534 - Fix a bug in parsing that could cause clients to read a single
3535 byte past the end of an allocated region. This bug could be used
3536 to cause hardened clients (built with --enable-expensive-hardening)
3537 to crash if they tried to visit a hostile hidden service. Non-
3538 hardened clients are only affected depending on the details of
3539 their platform's memory allocator. Fixes bug 21018; bugfix on
3540 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3541 2016-12-002 and as CVE-2016-1254.
3543 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3544 - Fix an error that could cause us to read 4 bytes before the
3545 beginning of an openssl string. This bug could be used to cause
3546 Tor to crash on systems with unusual malloc implementations, or
3547 systems with unusual hardening installed. Fixes bug 17404; bugfix
3550 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3551 - Avoid a difficult-to-trigger heap corruption attack when extending
3552 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3553 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3554 Reported by Guido Vranken.
3556 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3557 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3558 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3560 o Major bugfixes (guard selection, backport from 0.2.7.6):
3561 - Actually look at the Guard flag when selecting a new directory
3562 guard. When we implemented the directory guard design, we
3563 accidentally started treating all relays as if they have the Guard
3564 flag during guard selection, leading to weaker anonymity and worse
3565 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3568 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3569 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3570 pointer to the previous (uninitialized) key value. The impact here
3571 should be limited to a difficult-to-trigger crash, if OpenSSL is
3572 running an engine that makes key generation failures possible, or
3573 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3574 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3577 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3578 - Fix an integer underflow bug when comparing malformed Tor
3579 versions. This bug could crash Tor when built with
3580 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3581 0.2.9.8, which were built with -ftrapv by default. In other cases
3582 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3583 on 0.0.8pre1. Found by OSS-Fuzz.
3585 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3586 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3587 zero size. Check size argument to memwipe() for underflow. Fixes
3588 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3591 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3592 - Make Tor survive errors involving connections without a
3593 corresponding event object. Previously we'd fail with an
3594 assertion; now we produce a log message. Related to bug 16248.
3596 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
3597 - Make it harder for attackers to overload hidden services with
3598 introductions, by blocking multiple introduction requests on the
3599 same circuit. Resolves ticket 15515.
3601 o Minor features (geoip):
3602 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3605 o Minor bugfixes (compilation, backport from 0.2.7.6):
3606 - Fix a compilation warning with Clang 3.6: Do not check the
3607 presence of an address which can never be NULL. Fixes bug 17781.
3609 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3610 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3611 a client authorized hidden service. Fixes bug 15823; bugfix
3615 Changes in version 0.3.0.4-rc - 2017-03-01
3616 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
3617 0.3.0 release series, and introduces a few reliability features to
3618 keep them from coming back.
3620 This is the first release candidate in the Tor 0.3.0 series. If we
3621 find no new bugs or regressions here, the first stable 0.3.0 release
3622 will be nearly identical to it.
3624 o Major bugfixes (bridges):
3625 - When the same bridge is configured multiple times with the same
3626 identity, but at different address:port combinations, treat those
3627 bridge instances as separate guards. This fix restores the ability
3628 of clients to configure the same bridge with multiple pluggable
3629 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
3631 o Major bugfixes (hidden service directory v3):
3632 - Stop crashing on a failed v3 hidden service descriptor lookup
3633 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
3635 o Major bugfixes (parsing):
3636 - When parsing a malformed content-length field from an HTTP
3637 message, do not read off the end of the buffer. This bug was a
3638 potential remote denial-of-service attack against Tor clients and
3639 relays. A workaround was released in October 2016, to prevent this
3640 bug from crashing Tor. This is a fix for the underlying issue,
3641 which should no longer matter (if you applied the earlier patch).
3642 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
3643 using AFL (http://lcamtuf.coredump.cx/afl/).
3644 - Fix an integer underflow bug when comparing malformed Tor
3645 versions. This bug could crash Tor when built with
3646 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3647 0.2.9.8, which were built with -ftrapv by default. In other cases
3648 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3649 on 0.0.8pre1. Found by OSS-Fuzz.
3651 o Minor feature (protocol versioning):
3652 - Add new protocol version for proposal 224. HSIntro now advertises
3653 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
3655 o Minor features (directory authorities):
3656 - Directory authorities now reject descriptors that claim to be
3657 malformed versions of Tor. Helps prevent exploitation of
3659 - Reject version numbers with components that exceed INT32_MAX.
3660 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3661 Fixes bug 21450; bugfix on 0.0.8pre1.
3662 - Directory authorities now reject relays running versions
3663 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
3664 suffer from bug 20499 and don't keep their consensus cache
3665 up-to-date. Resolves ticket 20509.
3667 o Minor features (geoip):
3668 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3671 o Minor features (reliability, crash):
3672 - Try better to detect problems in buffers where they might grow (or
3673 think they have grown) over 2 GB in size. Diagnostic for
3676 o Minor features (testing):
3677 - During 'make test-network-all', if tor logs any warnings, ask
3678 chutney to output them. Requires a recent version of chutney with
3679 the 21572 patch. Implements 21570.
3681 o Minor bugfixes (certificate expiration time):
3682 - Avoid using link certificates that don't become valid till some
3683 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
3685 o Minor bugfixes (code correctness):
3686 - Repair a couple of (unreachable or harmless) cases of the risky
3687 comparison-by-subtraction pattern that caused bug 21278.
3688 - Remove a redundant check for the UseEntryGuards option from the
3689 options_transition_affects_guards() function. Fixes bug 21492;
3690 bugfix on 0.3.0.1-alpha.
3692 o Minor bugfixes (directory mirrors):
3693 - Allow relays to use directory mirrors without a DirPort: these
3694 relays need to be contacted over their ORPorts using a begindir
3695 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
3696 - Clarify the message logged when a remote relay is unexpectedly
3697 missing an ORPort or DirPort: users were confusing this with a
3698 local port. Fixes another case of bug 20711; bugfix
3701 o Minor bugfixes (guards):
3702 - Don't warn about a missing guard state on timeout-measurement
3703 circuits: they aren't supposed to be using guards. Fixes an
3704 instance of bug 21007; bugfix on 0.3.0.1-alpha.
3705 - Silence a BUG() warning when attempting to use a guard whose
3706 descriptor we don't know, and make this scenario less likely to
3707 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
3709 o Minor bugfixes (hidden service):
3710 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
3711 cells. Previously, we were using sizeof() on a pointer, instead of
3712 the real destination buffer. Fortunately, that value was only used
3713 to double-check that there was enough room--which was already
3714 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
3716 o Minor bugfixes (testing):
3717 - Fix Raspbian build issues related to missing socket errno in
3718 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
3720 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
3721 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
3722 - Use bash in src/test/test-network.sh. This ensures we reliably
3723 call chutney's newer tools/test-network.sh when available. Fixes
3724 bug 21562; bugfix on 0.2.9.1-alpha.
3727 - Small fixes to the fuzzing documentation. Closes ticket 21472.
3730 Changes in version 0.2.9.10 - 2017-03-01
3731 Tor 0.2.9.10 backports a security fix from later Tor release. It also
3732 includes fixes for some major issues affecting directory authorities,
3733 LibreSSL compatibility, and IPv6 correctness.
3735 The Tor 0.2.9.x release series is now marked as a long-term-support
3736 series. We intend to backport security fixes to 0.2.9.x until at
3737 least January of 2020.
3739 o Major bugfixes (directory authority, 0.3.0.3-alpha):
3740 - During voting, when marking a relay as a probable sybil, do not
3741 clear its BadExit flag: sybils can still be bad in other ways
3742 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3745 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
3746 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3747 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3748 exit policy rejects that port on more than an IPv6 /16 of
3749 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3750 which rejected a relay's own IPv6 address by default. Fixes bug
3751 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3753 o Major bugfixes (parsing, also in 0.3.0.4-rc):
3754 - Fix an integer underflow bug when comparing malformed Tor
3755 versions. This bug could crash Tor when built with
3756 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3757 0.2.9.8, which were built with -ftrapv by default. In other cases
3758 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3759 on 0.0.8pre1. Found by OSS-Fuzz.
3761 o Minor features (directory authorities, also in 0.3.0.4-rc):
3762 - Directory authorities now reject descriptors that claim to be
3763 malformed versions of Tor. Helps prevent exploitation of
3765 - Reject version numbers with components that exceed INT32_MAX.
3766 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3767 Fixes bug 21450; bugfix on 0.0.8pre1.
3769 o Minor features (geoip):
3770 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3773 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
3774 - Autoconf now checks to determine if OpenSSL structures are opaque,
3775 instead of explicitly checking for OpenSSL version numbers. Part
3777 - Support building with recent LibreSSL code that uses opaque
3778 structures. Closes ticket 21359.
3780 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
3781 - Repair a couple of (unreachable or harmless) cases of the risky
3782 comparison-by-subtraction pattern that caused bug 21278.
3784 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
3785 - The tor-resolve command line tool now rejects hostnames over 255
3786 characters in length. Previously, it would silently truncate them,
3787 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3788 Patch by "junglefowl".
3791 Changes in version 0.3.0.3-alpha - 2017-02-03
3792 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
3793 0.3.0.x development series, including some that could cause
3794 authorities to behave badly. There is also a fix for a longstanding
3795 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
3796 includes some smaller features and bugfixes.
3798 The Tor 0.3.0.x release series is now in patch-freeze: no additional
3799 features will be considered for inclusion in 0.3.0.x. We suspect that
3800 some bugs will probably remain, however, and we encourage people to
3803 o Major bugfixes (directory authority):
3804 - During voting, when marking a relay as a probable sybil, do not
3805 clear its BadExit flag: sybils can still be bad in other ways
3806 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3808 - When deciding whether we have just found a router to be reachable,
3809 do not penalize it for not having performed an Ed25519 link
3810 handshake if it does not claim to support an Ed25519 handshake.
3811 Previously, we would treat such relays as non-running. Fixes bug
3812 21107; bugfix on 0.3.0.1-alpha.
3814 o Major bugfixes (entry guards):
3815 - Stop trying to build circuits through entry guards for which we
3816 have no descriptor. Also, stop crashing in the case that we *do*
3817 accidentally try to build a circuit in such a state. Fixes bug
3818 21242; bugfix on 0.3.0.1-alpha.
3820 o Major bugfixes (IPv6 Exits):
3821 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3822 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3823 exit policy rejects that port on more than an IPv6 /16 of
3824 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3825 which rejected a relay's own IPv6 address by default. Fixes bug
3826 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3828 o Minor feature (client):
3829 - Enable IPv6 traffic on the SocksPort by default. To disable this,
3830 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
3832 o Minor feature (fallback scripts):
3833 - Add a check_existing mode to updateFallbackDirs.py, which checks
3834 if fallbacks in the hard-coded list are working. Closes ticket
3835 20174. Patch by haxxpop.
3837 o Minor features (ciphersuite selection):
3838 - Clients now advertise a list of ciphersuites closer to the ones
3839 preferred by Firefox. Closes part of ticket 15426.
3840 - Allow relays to accept a wider range of ciphersuites, including
3841 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
3843 o Minor features (controller, configuration):
3844 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
3845 and so on, now comes with a __*Port variant that will not be saved
3846 to the torrc file by the controller's SAVECONF command. This
3847 change allows TorBrowser to set up a single-use domain socket for
3848 each time it launches Tor. Closes ticket 20956.
3849 - The GETCONF command can now query options that may only be
3850 meaningful in context-sensitive lists. This allows the controller
3851 to query the mixed SocksPort/__SocksPort style options introduced
3852 in feature 20956. Implements ticket 21300.
3854 o Minor features (portability, compilation):
3855 - Autoconf now checks to determine if OpenSSL structures are opaque,
3856 instead of explicitly checking for OpenSSL version numbers. Part
3858 - Support building with recent LibreSSL code that uses opaque
3859 structures. Closes ticket 21359.
3861 o Minor features (relay):
3862 - We now allow separation of exit and relay traffic to different
3863 source IP addresses, using the OutboundBindAddressExit and
3864 OutboundBindAddressOR options respectively. Closes ticket 17975.
3865 Written by Michael Sonntag.
3867 o Minor bugfix (logging):
3868 - Don't recommend the use of Tor2web in non-anonymous mode.
3869 Recommending Tor2web is a bad idea because the client loses all
3870 anonymity. Tor2web should only be used in specific cases by users
3871 who *know* and understand the issues. Fixes bug 21294; bugfix
3874 o Minor bugfixes (client):
3875 - Always recover from failures in extend_info_from_node(), in an
3876 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
3877 bugfix on 0.2.3.1-alpha.
3879 o Minor bugfixes (client, entry guards):
3880 - Fix a bug warning (with backtrace) when we fail a channel that
3881 circuits to fallback directories on it. Fixes bug 21128; bugfix
3883 - Fix a spurious bug warning (with backtrace) when removing an
3884 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
3885 - Fix a bug of the new guard algorithm where tor could stall for up
3886 to 10 minutes before retrying a guard after a long period of no
3887 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
3888 - Do not try to build circuits until we have descriptors for our
3889 primary entry guards. Related to fix for bug 21242.
3891 o Minor bugfixes (configure, autoconf):
3892 - Rename the configure option --enable-expensive-hardening to
3893 --enable-fragile-hardening. Expensive hardening makes the tor
3894 daemon abort when some kinds of issues are detected. Thus, it
3895 makes tor more at risk of remote crashes but safer against RCE or
3896 heartbleed bug category. We now try to explain this issue in a
3897 message from the configure script. Fixes bug 21290; bugfix
3900 o Minor bugfixes (controller):
3901 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
3902 20824; bugfix on 0.3.0.1-alpha.
3904 o Minor bugfixes (hidden service):
3905 - Clean up the code for expiring intro points with no associated
3906 circuits. It was causing, rarely, a service with some expiring
3907 introduction points to not open enough additional introduction
3908 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
3909 - Stop setting the torrc option HiddenServiceStatistics to "0" just
3910 because we're not a bridge or relay. Instead, we preserve whatever
3911 value the user set (or didn't set). Fixes bug 21150; bugfix
3913 - Resolve two possible underflows which could lead to creating and
3914 closing a lot of introduction point circuits in a non-stop loop.
3915 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
3917 o Minor bugfixes (portability):
3918 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
3919 It is supported by OpenBSD itself, and also by most OpenBSD
3920 variants (such as Bitrig). Fixes bug 20980; bugfix
3922 - When mapping a file of length greater than SIZE_MAX, do not
3923 silently truncate its contents. This issue could occur on 32 bit
3924 systems with large file support and files which are larger than 4
3925 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
3927 o Minor bugfixes (tor-resolve):
3928 - The tor-resolve command line tool now rejects hostnames over 255
3929 characters in length. Previously, it would silently truncate them,
3930 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3931 Patch by "junglefowl".
3933 o Minor bugfixes (Windows services):
3934 - Be sure to initialize the monotonic time subsystem before using
3935 it, even when running as an NT service. Fixes bug 21356; bugfix
3939 Changes in version 0.3.0.2-alpha - 2017-01-23
3940 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
3941 cause relays and clients to crash, even if they were not built with
3942 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
3943 versions, and also affects 0.3.0.1-alpha: all relays running an affected
3944 version should upgrade.
3946 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
3947 time-to-live values, makes directory authorities enforce the 1-to-1
3948 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
3949 client-side onion service reachability bug, does better at selecting
3950 the set of fallback directories, and more.
3952 o Major bugfixes (security, also in 0.2.9.9):
3953 - Downgrade the "-ftrapv" option from "always on" to "only on when
3954 --enable-expensive-hardening is provided." This hardening option, like
3955 others, can turn survivable bugs into crashes--and having it on by
3956 default made a (relatively harmless) integer overflow bug into a
3957 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
3960 o Major features (security):
3961 - Change the algorithm used to decide DNS TTLs on client and server
3962 side, to better resist DNS-based correlation attacks like the
3963 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
3964 Feamster. Now relays only return one of two possible DNS TTL
3965 values, and clients are willing to believe DNS TTL values up to 3
3966 hours long. Closes ticket 19769.
3968 o Major features (directory authority, security):
3969 - The default for AuthDirPinKeys is now 1: directory authorities
3970 will reject relays where the RSA identity key matches a previously
3971 seen value, but the Ed25519 key has changed. Closes ticket 18319.
3973 o Major bugfixes (client, guard, crash):
3974 - In circuit_get_global_origin_list(), return the actual list of
3975 origin circuits. The previous version of this code returned the
3976 list of all the circuits, and could have caused strange bugs,
3977 including possible crashes. Fixes bug 21118; bugfix
3980 o Major bugfixes (client, onion service, also in 0.2.9.9):
3981 - Fix a client-side onion service reachability bug, where multiple
3982 socks requests to an onion service (or a single slow request)
3983 could cause us to mistakenly mark some of the service's
3984 introduction points as failed, and we cache that failure so
3985 eventually we run out and can't reach the service. Also resolves a
3986 mysterious "Remote server sent bogus reason code 65021" log
3987 warning. The bug was introduced in ticket 17218, where we tried to
3988 remember the circuit end reason as a uint16_t, which mangled
3989 negative values. Partially fixes bug 21056 and fixes bug 20307;
3990 bugfix on 0.2.8.1-alpha.
3992 o Major bugfixes (DNS):
3993 - Fix a bug that prevented exit nodes from caching DNS records for
3994 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
3996 o Minor features (controller):
3997 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
3998 shared-random values to the controller. Closes ticket 19925.
4000 o Minor features (entry guards):
4001 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
4002 break regression tests.
4003 - Require UseEntryGuards when UseBridges is set, in order to make
4004 sure bridges aren't bypassed. Resolves ticket 20502.
4006 o Minor features (fallback directories):
4007 - Select 200 fallback directories for each release. Closes
4009 - Allow 3 fallback relays per operator, which is safe now that we
4010 are choosing 200 fallback relays. Closes ticket 20912.
4011 - Exclude relays affected by bug 20499 from the fallback list.
4012 Exclude relays from the fallback list if they are running versions
4013 known to be affected by bug 20499, or if in our tests they deliver
4014 a stale consensus (i.e. one that expired more than 24 hours ago).
4015 Closes ticket 20539.
4016 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
4018 - Require fallback directories to have the same address and port for
4019 7 days (now that we have enough relays with this stability).
4020 Relays whose OnionOO stability timer is reset on restart by bug
4021 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
4022 this issue. Closes ticket 20880; maintains short-term fix
4024 - Require fallbacks to have flags for 90% of the time (weighted
4025 decaying average), rather than 95%. This allows at least 73% of
4026 clients to bootstrap in the first 5 seconds without contacting an
4027 authority. Part of ticket 18828.
4028 - Annotate updateFallbackDirs.py with the bandwidth and consensus
4029 weight for each candidate fallback. Closes ticket 20878.
4030 - Make it easier to change the output sort order of fallbacks.
4031 Closes ticket 20822.
4032 - Display the relay fingerprint when downloading consensuses from
4033 fallbacks. Closes ticket 20908.
4035 o Minor features (geoip, also in 0.2.9.9):
4036 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4039 o Minor features (next-gen onion service directories):
4040 - Remove the "EnableOnionServicesV3" consensus parameter that we
4041 introduced in 0.3.0.1-alpha: relays are now always willing to act
4042 as v3 onion service directories. Resolves ticket 19899.
4044 o Minor features (linting):
4045 - Enhance the changes file linter to warn on Tor versions that are
4046 prefixed with "tor-". Closes ticket 21096.
4048 o Minor features (logging):
4049 - In several places, describe unset ed25519 keys as "<unset>",
4050 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
4052 o Minor bugfix (control protocol):
4053 - The reply to a "GETINFO config/names" request via the control
4054 protocol now spells the type "Dependent" correctly. This is a
4055 breaking change in the control protocol. (The field seems to be
4056 ignored by the most common known controllers.) Fixes bug 18146;
4057 bugfix on 0.1.1.4-alpha.
4059 o Minor bugfixes (bug resilience):
4060 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
4061 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
4062 Hans Jerry Illikainen.
4064 o Minor bugfixes (build):
4065 - Replace obsolete Autoconf macros with their modern equivalent and
4066 prevent similar issues in the future. Fixes bug 20990; bugfix
4069 o Minor bugfixes (client, guards):
4070 - Fix bug where Tor would think that there are circuits waiting for
4071 better guards even though those circuits have been freed. Fixes
4072 bug 21142; bugfix on 0.3.0.1-alpha.
4074 o Minor bugfixes (config):
4075 - Don't assert on startup when trying to get the options list and
4076 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
4077 options so of course they aren't ready yet. Fixes bug 21062;
4078 bugfix on 0.2.9.3-alpha.
4080 o Minor bugfixes (controller):
4081 - Make the GETINFO interface for inquiring about entry guards
4082 support the new guards backend. Fixes bug 20823; bugfix
4085 o Minor bugfixes (dead code):
4086 - Remove a redundant check for PidFile changes at runtime in
4087 options_transition_allowed(): this check is already performed
4088 regardless of whether the sandbox is active. Fixes bug 21123;
4089 bugfix on 0.2.5.4-alpha.
4091 o Minor bugfixes (documentation):
4092 - Update the tor manual page to document every option that can not
4093 be changed while tor is running. Fixes bug 21122.
4095 o Minor bugfixes (fallback directories):
4096 - Stop failing when a relay has no uptime data in
4097 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
4098 - Avoid checking fallback candidates' DirPorts if they are down in
4099 OnionOO. When a relay operator has multiple relays, this
4100 prioritizes relays that are up over relays that are down. Fixes
4101 bug 20926; bugfix on 0.2.8.3-alpha.
4102 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
4103 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
4105 o Minor bugfixes (guards, bootstrapping):
4106 - When connecting to a directory guard during bootstrap, do not mark
4107 the guard as successful until we receive a good-looking directory
4108 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
4110 o Minor bugfixes (onion services):
4111 - Fix the config reload pruning of old vs new services so it
4112 actually works when both ephemeral and non-ephemeral services are
4113 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
4114 - Allow the number of introduction points to be as low as 0, rather
4115 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
4117 o Minor bugfixes (IPv6):
4118 - Make IPv6-using clients try harder to find an IPv6 directory
4119 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
4120 - When IPv6 addresses have not been downloaded yet (microdesc
4121 consensus documents don't list relay IPv6 addresses), use hard-
4122 coded addresses for authorities, fallbacks, and configured
4123 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
4124 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
4126 o Minor bugfixes (memory leaks):
4127 - Fix a memory leak when configuring hidden services. Fixes bug
4128 20987; bugfix on 0.3.0.1-alpha.
4130 o Minor bugfixes (portability, also in 0.2.9.9):
4131 - Avoid crashing when Tor is built using headers that contain
4132 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4133 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4135 - Fix Libevent detection on platforms without Libevent 1 headers
4136 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4138 o Minor bugfixes (relay):
4139 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
4140 initializing the keys would reset the DataDirectory to 0700
4141 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
4142 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
4144 o Minor bugfixes (testing):
4145 - Remove undefined behavior from the backtrace generator by removing
4146 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
4148 o Minor bugfixes (unit tests):
4149 - Allow the unit tests to pass even when DNS lookups of bogus
4150 addresses do not fail as expected. Fixes bug 20862 and 20863;
4151 bugfix on unit tests introduced in 0.2.8.1-alpha
4152 through 0.2.9.4-alpha.
4154 o Code simplification and refactoring:
4155 - Refactor code to manipulate global_origin_circuit_list into
4156 separate functions. Closes ticket 20921.
4158 o Documentation (formatting):
4159 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
4160 blocks were incorrectly appearing. Closes ticket 20885.
4162 o Documentation (man page):
4163 - Clarify many options in tor.1 and add some min/max values for
4164 HiddenService options. Closes ticket 21058.
4167 Changes in version 0.2.9.9 - 2017-01-23
4168 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
4169 cause relays and clients to crash, even if they were not built with
4170 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
4171 versions, and also affects 0.3.0.1-alpha: all relays running an affected
4172 version should upgrade.
4174 This release also resolves a client-side onion service reachability
4175 bug, and resolves a pair of small portability issues.
4177 o Major bugfixes (security):
4178 - Downgrade the "-ftrapv" option from "always on" to "only on when
4179 --enable-expensive-hardening is provided." This hardening option,
4180 like others, can turn survivable bugs into crashes -- and having
4181 it on by default made a (relatively harmless) integer overflow bug
4182 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
4183 bugfix on 0.2.9.1-alpha.
4185 o Major bugfixes (client, onion service):
4186 - Fix a client-side onion service reachability bug, where multiple
4187 socks requests to an onion service (or a single slow request)
4188 could cause us to mistakenly mark some of the service's
4189 introduction points as failed, and we cache that failure so
4190 eventually we run out and can't reach the service. Also resolves a
4191 mysterious "Remote server sent bogus reason code 65021" log
4192 warning. The bug was introduced in ticket 17218, where we tried to
4193 remember the circuit end reason as a uint16_t, which mangled
4194 negative values. Partially fixes bug 21056 and fixes bug 20307;
4195 bugfix on 0.2.8.1-alpha.
4197 o Minor features (geoip):
4198 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4201 o Minor bugfixes (portability):
4202 - Avoid crashing when Tor is built using headers that contain
4203 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4204 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4206 - Fix Libevent detection on platforms without Libevent 1 headers
4207 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4210 Changes in version 0.3.0.1-alpha - 2016-12-19
4211 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
4212 series. It strengthens Tor's link and circuit handshakes by
4213 identifying relays by their Ed25519 keys, improves the algorithm that
4214 clients use to choose and maintain their list of guards, and includes
4215 additional backend support for the next-generation hidden service
4216 design. It also contains numerous other small features and
4217 improvements to security, correctness, and performance.
4219 Below are the changes since 0.2.9.8.
4221 o Major features (guard selection algorithm):
4222 - Tor's guard selection algorithm has been redesigned from the
4223 ground up, to better support unreliable networks and restrictive
4224 sets of entry nodes, and to better resist guard-capture attacks by
4225 hostile local networks. Implements proposal 271; closes
4228 o Major features (next-generation hidden services):
4229 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
4230 prop224 aka "Next Generation Hidden Services". Service and clients
4231 don't use this functionality yet. Closes ticket 19043. Based on
4232 initial code by Alec Heifetz.
4233 - Relays now support the HSDir version 3 protocol, so that they can
4234 can store and serve v3 descriptors. This is part of the next-
4235 generation onion service work detailed in proposal 224. Closes
4238 o Major features (protocol, ed25519 identity keys):
4239 - Relays now use Ed25519 to prove their Ed25519 identities and to
4240 one another, and to clients. This algorithm is faster and more
4241 secure than the RSA-based handshake we've been doing until now.
4242 Implements the second big part of proposal 220; Closes
4244 - Clients now support including Ed25519 identity keys in the EXTEND2
4245 cells they generate. By default, this is controlled by a consensus
4246 parameter, currently disabled. You can turn this feature on for
4247 testing by setting ExtendByEd25519ID in your configuration. This
4248 might make your traffic appear different than the traffic
4249 generated by other users, however. Implements part of ticket
4250 15056; part of proposal 220.
4251 - Relays now understand requests to extend to other relays by their
4252 Ed25519 identity keys. When an Ed25519 identity key is included in
4253 an EXTEND2 cell, the relay will only extend the circuit if the
4254 other relay can prove ownership of that identity. Implements part
4255 of ticket 15056; part of proposal 220.
4257 o Major bugfixes (scheduler):
4258 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
4259 caused the channel scheduler to behave more or less randomly,
4260 rather than preferring channels with higher-priority circuits.
4261 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
4263 o Minor features (controller):
4264 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
4265 rather than "unrecognized." Closes ticket 20389; patch from
4268 o Minor features (diagnostic, directory client):
4269 - Warn when we find an unexpected inconsistency in directory
4270 download status objects. Prevents some negative consequences of
4273 o Minor features (directory authority):
4274 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
4275 default) to control whether authorities should try to probe relays
4276 by their Ed25519 link keys. This option will go away in a few
4277 releases--unless we encounter major trouble in our ed25519 link
4278 protocol rollout, in which case it will serve as a safety option.
4280 o Minor features (directory cache):
4281 - Relays and bridges will now refuse to serve the consensus they
4282 have if they know it is too old for a client to use. Closes
4285 o Minor features (ed25519 link handshake):
4286 - Advertise support for the ed25519 link handshake using the
4287 subprotocol-versions mechanism, so that clients can tell which
4288 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
4290 o Minor features (fingerprinting resistance, authentication):
4291 - Extend the length of RSA keys used for TLS link authentication to
4292 2048 bits. (These weren't used for forward secrecy; for forward
4293 secrecy, we used P256.) Closes ticket 13752.
4295 o Minor features (infrastructure):
4296 - Implement smartlist_add_strdup() function. Replaces the use of
4297 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
4299 o Minor bugfixes (client):
4300 - When clients that use bridges start up with a cached consensus on
4301 disk, they were ignoring it and downloading a new one. Now they
4302 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
4304 o Minor bugfixes (configuration):
4305 - Accept non-space whitespace characters after the severity level in
4306 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
4307 - Support "TByte" and "TBytes" units in options given in bytes.
4308 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
4309 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
4311 o Minor bugfixes (consensus weight):
4312 - Add new consensus method that initializes bw weights to 1 instead
4313 of 0. This prevents a zero weight from making it all the way to
4314 the end (happens in small testing networks) and causing an error.
4315 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
4317 o Minor bugfixes (descriptors):
4318 - Correctly recognise downloaded full descriptors as valid, even
4319 when using microdescriptors as circuits. This affects clients with
4320 FetchUselessDescriptors set, and may affect directory authorities.
4321 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
4323 o Minor bugfixes (directory system):
4324 - Download all consensus flavors, descriptors, and authority
4325 certificates when FetchUselessDescriptors is set, regardless of
4326 whether tor is a directory cache or not. Fixes bug 20667; bugfix
4327 on all recent tor versions.
4328 - Bridges and relays now use microdescriptors (like clients do)
4329 rather than old-style router descriptors. Now bridges will blend
4330 in with clients in terms of the circuits they build. Fixes bug
4331 6769; bugfix on 0.2.3.2-alpha.
4333 o Minor bugfixes (ed25519 certificates):
4334 - Correctly interpret ed25519 certificates that would expire some
4335 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
4337 o Minor bugfixes (hidden services):
4338 - Stop ignoring misconfigured hidden services. Instead, refuse to
4339 start tor until the misconfigurations have been corrected. Fixes
4340 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
4343 o Minor bugfixes (memory leak at exit):
4344 - Fix a small harmless memory leak at exit of the previously unused
4345 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
4348 o Minor bugfixes (util):
4349 - When finishing writing a file to disk, if we were about to replace
4350 the file with the temporary file created before and we fail to
4351 replace it, remove the temporary file so it doesn't stay on disk.
4352 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
4354 o Minor bugfixes (Windows):
4355 - Check for getpagesize before using it to mmap files. This fixes
4356 compilation in some MinGW environments. Fixes bug 20530; bugfix on
4357 0.1.2.1-alpha. Reported by "ice".
4359 o Code simplification and refactoring:
4360 - Abolish all global guard context in entrynodes.c; replace with new
4361 guard_selection_t structure as preparation for proposal 271.
4362 Closes ticket 19858.
4363 - Introduce rend_service_is_ephemeral() that tells if given onion
4364 service is ephemeral. Replace unclear NULL-checkings for service
4365 directory with this function. Closes ticket 20526.
4366 - Extract magic numbers in circuituse.c into defined variables.
4367 - Refactor circuit_is_available_for_use to remove unnecessary check.
4368 - Refactor circuit_predict_and_launch_new for readability and
4369 testability. Closes ticket 18873.
4370 - Refactor large if statement in purpose_needs_anonymity to use
4371 switch statement instead. Closes part of ticket 20077.
4372 - Refactor the hashing API to return negative values for errors, as
4373 is done as throughout the codebase. Closes ticket 20717.
4374 - Remove data structures that were used to index or_connection
4375 objects by their RSA identity digests. These structures are fully
4376 redundant with the similar structures used in the
4377 channel abstraction.
4378 - Remove duplicate code in the channel_write_*cell() functions.
4379 Closes ticket 13827; patch from Pingl.
4380 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
4381 use only purpose_needs_anonymity. Closes part of ticket 20077.
4382 - The code to generate and parse EXTEND and EXTEND2 cells has been
4383 replaced with code automatically generated by the
4387 - Include the "TBits" unit in Tor's man page. Fixes part of bug
4388 20622; bugfix on tor-0.2.5.1-alpha.
4389 - Change '1' to 'weight_scale' in consensus bw weights calculation
4390 comments, as that is reality. Closes ticket 20273. Patch
4392 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
4393 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
4394 on tor-0.2.5.6-alpha.
4395 - Stop the man page from incorrectly stating that HiddenServiceDir
4396 must already exist. Fixes 20486.
4397 - Clarify that when ClientRejectInternalAddresses is enabled (which
4398 is the default), multicast DNS hostnames for machines on the local
4399 network (of the form *.local) are also rejected. Closes
4403 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
4404 limit for relays running on a single IP applies to authority IP
4405 addresses as well as to non-authority IP addresses. Closes
4407 - The UseDirectoryGuards torrc option no longer exists: all users
4408 that use entry guards will also use directory guards. Related to
4409 proposal 271; implements part of ticket 20831.
4412 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
4413 from "overcaffeinated".
4414 - Perform the coding style checks when running the tests and fail
4415 when coding style violations are found. Closes ticket 5500.
4416 - Add tests for networkstatus_compute_bw_weights_v10.
4417 - Add unit tests circuit_predict_and_launch_new.
4418 - Extract dummy_origin_circuit_new so it can be used by other
4422 Changes in version 0.2.8.12 - 2016-12-19
4423 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
4424 below) where Tor clients could crash when attempting to visit a
4425 hostile hidden service. Clients are recommended to upgrade as packages
4426 become available for their systems.
4428 It also includes an updated list of fallback directories, backported
4431 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
4432 backported to 0.2.8 in the future.
4434 o Major bugfixes (parsing, security, backported from 0.2.9.8):
4435 - Fix a bug in parsing that could cause clients to read a single
4436 byte past the end of an allocated region. This bug could be used
4437 to cause hardened clients (built with --enable-expensive-hardening)
4438 to crash if they tried to visit a hostile hidden service. Non-
4439 hardened clients are only affected depending on the details of
4440 their platform's memory allocator. Fixes bug 21018; bugfix on
4441 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4442 2016-12-002 and as CVE-2016-1254.
4444 o Minor features (fallback directory list, backported from 0.2.9.8):
4445 - Replace the 81 remaining fallbacks of the 100 originally
4446 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4447 fallbacks (123 new, 54 existing, 27 removed) generated in December
4448 2016. Resolves ticket 20170.
4450 o Minor features (geoip, backported from 0.2.9.7-rc):
4451 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
4455 Changes in version 0.2.9.8 - 2016-12-19
4456 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
4458 The Tor 0.2.9 series makes mandatory a number of security features
4459 that were formerly optional. It includes support for a new shared-
4460 randomness protocol that will form the basis for next generation
4461 hidden services, includes a single-hop hidden service mode for
4462 optimizing .onion services that don't actually want to be hidden,
4463 tries harder not to overload the directory authorities with excessive
4464 downloads, and supports a better protocol versioning scheme for
4465 improved compatibility with other implementations of the Tor protocol.
4467 And of course, there are numerous other bugfixes and improvements.
4469 This release also includes a fix for a medium-severity issue (bug
4470 21018 below) where Tor clients could crash when attempting to visit a
4471 hostile hidden service. Clients are recommended to upgrade as packages
4472 become available for their systems.
4474 Below are the changes since 0.2.9.7-rc. For a list of all changes
4475 since 0.2.8, see the ReleaseNotes file.
4477 o Major bugfixes (parsing, security):
4478 - Fix a bug in parsing that could cause clients to read a single
4479 byte past the end of an allocated region. This bug could be used
4480 to cause hardened clients (built with --enable-expensive-hardening)
4481 to crash if they tried to visit a hostile hidden service. Non-
4482 hardened clients are only affected depending on the details of
4483 their platform's memory allocator. Fixes bug 21018; bugfix on
4484 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4485 2016-12-002 and as CVE-2016-1254.
4487 o Minor features (fallback directory list):
4488 - Replace the 81 remaining fallbacks of the 100 originally
4489 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4490 fallbacks (123 new, 54 existing, 27 removed) generated in December
4491 2016. Resolves ticket 20170.
4494 Changes in version 0.2.9.7-rc - 2016-12-12
4495 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
4496 including a few that had prevented tests from passing on
4499 o Minor features (geoip):
4500 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
4503 o Minor bugfix (build):
4504 - The current Git revision when building from a local repository is
4505 now detected correctly when using git worktrees. Fixes bug 20492;
4506 bugfix on 0.2.3.9-alpha.
4508 o Minor bugfixes (directory authority):
4509 - When computing old Tor protocol line version in protover, we were
4510 looking at 0.2.7.5 twice instead of a specific case for
4511 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
4513 o Minor bugfixes (download scheduling):
4514 - Resolve a "bug" warning when considering a download schedule whose
4515 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
4517 o Minor bugfixes (logging):
4518 - Downgrade a harmless log message about the
4519 pending_entry_connections list from "warn" to "info". Mitigates
4522 o Minor bugfixes (memory leak):
4523 - Fix a small memory leak when receiving AF_UNIX connections on a
4524 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
4525 - When moving a signed descriptor object from a source to an
4526 existing destination, free the allocated memory inside that
4527 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
4529 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
4530 - Fix a memory leak and use-after-free error when removing entries
4531 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
4532 0.2.5.5-alpha. Patch from "cypherpunks".
4534 o Minor bugfixes (portability):
4535 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
4536 Fixes bug 20935; bugfix on 0.2.9.6-rc.
4538 o Minor bugfixes (unit tests):
4539 - Stop expecting NetBSD unit tests to report success for ipfw. Part
4540 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
4541 - Fix tolerances in unit tests for monotonic time comparisons
4542 between nanoseconds and microseconds. Previously, we accepted a 10
4543 us difference only, which is not realistic on every platform's
4544 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
4545 - Remove a double-free in the single onion service unit test. Stop
4546 ignoring a return value. Make future changes less error-prone.
4547 Fixes bug 20864; bugfix on 0.2.9.6-rc.
4550 Changes in version 0.2.8.11 - 2016-12-08
4551 Tor 0.2.8.11 backports fixes for additional portability issues that
4552 could prevent Tor from building correctly on OSX Sierra, or with
4553 OpenSSL 1.1. Affected users should upgrade; others can safely stay
4556 o Minor bugfixes (portability):
4557 - Avoid compilation errors when building on OSX Sierra. Sierra began
4558 to support the getentropy() and clock_gettime() APIs, but created
4559 a few problems in doing so. Tor 0.2.9 has a more thorough set of
4560 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
4561 monotonic time interfaces. Fixes bug 20865. Bugfix
4564 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4565 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
4566 architectures. Closes ticket 20588.
4569 Changes in version 0.2.8.10 - 2016-12-02
4570 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
4571 unusable after they left standby mode. It also backports fixes for
4572 a few portability issues and a small but problematic memory leak.
4574 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
4575 - When Tor leaves standby because of a new application request, open
4576 circuits as needed to serve that request. Previously, we would
4577 potentially wait a very long time. Fixes part of bug 19969; bugfix
4580 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
4581 - Clients now respond to new application stream requests immediately
4582 when they arrive, rather than waiting up to one second before
4583 starting to handle them. Fixes part of bug 19969; bugfix
4586 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
4587 - Work around a bug in the OSX 10.12 SDK that would prevent us from
4588 successfully targeting earlier versions of OSX. Resolves
4591 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4592 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
4593 20551; bugfix on 0.2.1.1-alpha.
4595 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
4596 - Work around a memory leak in OpenSSL 1.1 when encoding public
4597 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
4599 o Minor features (geoip):
4600 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
4603 Changes in version 0.2.9.6-rc - 2016-12-02
4604 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
4605 version. We hope that it will be ready to become stable soon, and we
4606 encourage everyone to test this release. If no showstopper bugs are
4607 found here, the next 0.2.9 release will be stable.
4609 o Major bugfixes (relay, resolver, logging):
4610 - For relays that don't know their own address, avoid attempting a
4611 local hostname resolve for each descriptor we download. This
4612 will cut down on the number of "Success: chose address 'x.x.x.x'"
4613 log lines, and also avoid confusing clock jumps if the resolver
4614 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
4616 o Minor bugfixes (client, fascistfirewall):
4617 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
4618 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
4620 o Minor bugfixes (hidden services):
4621 - Stop ignoring the anonymity status of saved keys for hidden
4622 services and single onion services when first starting tor.
4623 Instead, refuse to start tor if any hidden service key has been
4624 used in a different hidden service anonymity mode. Fixes bug
4625 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
4627 o Minor bugfixes (portability):
4628 - Work around a bug in the OSX 10.12 SDK that would prevent us from
4629 successfully targeting earlier versions of OSX. Resolves
4631 - Run correctly when built on Windows build environments that
4632 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
4634 o Minor bugfixes (single onion services, Tor2web):
4635 - Stop complaining about long-term one-hop circuits deliberately
4636 created by single onion services and Tor2web. These log messages
4637 are intended to diagnose issue 8387, which relates to circuits
4638 hanging around forever for no reason. Fixes bug 20613; bugfix on
4639 0.2.9.1-alpha. Reported by "pastly".
4641 o Minor bugfixes (unit tests):
4642 - Stop spurious failures in the local interface address discovery
4643 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
4647 - Correct the minimum bandwidth value in torrc.sample, and queue a
4648 corresponding change for torrc.minimal. Closes ticket 20085.
4651 Changes in version 0.2.9.5-alpha - 2016-11-08
4652 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
4653 version. We believe one or two probably remain, and we encourage
4654 everyone to test this release.
4656 o Major bugfixes (client performance):
4657 - Clients now respond to new application stream requests immediately
4658 when they arrive, rather than waiting up to one second before
4659 starting to handle them. Fixes part of bug 19969; bugfix
4662 o Major bugfixes (client reliability):
4663 - When Tor leaves standby because of a new application request, open
4664 circuits as needed to serve that request. Previously, we would
4665 potentially wait a very long time. Fixes part of bug 19969; bugfix
4668 o Major bugfixes (download scheduling):
4669 - When using an exponential backoff schedule, do not give up on
4670 downloading just because we have failed a bunch of times. Since
4671 each delay is longer than the last, retrying indefinitely won't
4672 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
4673 - If a consensus expires while we are waiting for certificates to
4674 download, stop waiting for certificates.
4675 - If we stop waiting for certificates less than a minute after we
4676 started downloading them, do not consider the certificate download
4677 failure a separate failure. Fixes bug 20533; bugfix
4679 - Remove the maximum delay on exponential-backoff scheduling. Since
4680 we now allow an infinite number of failures (see ticket 20536), we
4681 must now allow the time to grow longer on each failure. Fixes part
4682 of bug 20534; bugfix on 0.2.9.1-alpha.
4683 - Make our initial download delays closer to those from 0.2.8. Fixes
4684 another part of bug 20534; bugfix on 0.2.9.1-alpha.
4685 - When determining when to download a directory object, handle times
4686 after 2038 if the operating system supports them. (Someday this
4687 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
4688 - When using exponential backoff in test networks, use a lower
4689 exponent, so the delays do not vary as much. This helps test
4690 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
4692 o Minor features (geoip):
4693 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
4696 o Minor bugfixes (client directory scheduling):
4697 - Treat "relay too busy to answer request" as a failed request and a
4698 reason to back off on our retry frequency. This is safe now that
4699 exponential backoffs retry indefinitely, and avoids a bug where we
4700 would reset our download schedule erroneously. Fixes bug 20593;
4701 bugfix on 0.2.9.1-alpha.
4703 o Minor bugfixes (client, logging):
4704 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
4705 assume all nodes support EXTEND2. Use ntor whenever a key is
4706 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
4707 - On DNSPort, stop logging a BUG warning on a failed hostname
4708 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
4710 o Minor bugfixes (hidden services):
4711 - When configuring hidden services, check every hidden service
4712 directory's permissions. Previously, we only checked the last
4713 hidden service. Fixes bug 20529; bugfix the work to fix 13942
4716 o Minor bugfixes (portability):
4717 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
4718 architectures. Closes ticket 20588.
4719 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
4720 removed the ECDH ciphers which caused the tests to fail on
4721 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
4722 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
4723 20551; bugfix on 0.2.1.1-alpha.
4725 o Minor bugfixes (relay bootstrap):
4726 - Ensure relays don't make multiple connections during bootstrap.
4727 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
4729 o Minor bugfixes (relay):
4730 - Work around a memory leak in OpenSSL 1.1 when encoding public
4731 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
4732 - Avoid a small memory leak when informing worker threads about
4733 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
4734 - Do not try to parallelize workers more than 16x without the user
4735 explicitly configuring us to do so, even if we do detect more than
4736 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4738 o Minor bugfixes (single onion services):
4739 - Start correctly when creating a single onion service in a
4740 directory that did not previously exist. Fixes bug 20484; bugfix
4743 o Minor bugfixes (testing):
4744 - Avoid a unit test failure on systems with over 16 detectable CPU
4745 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4748 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
4749 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
4750 - Module-level documentation for several more modules. Closes
4751 tickets 19287 and 19290.
4754 Changes in version 0.2.8.9 - 2016-10-17
4755 Tor 0.2.8.9 backports a fix for a security hole in previous versions
4756 of Tor that would allow a remote attacker to crash a Tor client,
4757 hidden service, relay, or authority. All Tor users should upgrade to
4758 this version, or to 0.2.9.4-alpha. Patches will be released for older
4761 o Major features (security fixes, also in 0.2.9.4-alpha):
4762 - Prevent a class of security bugs caused by treating the contents
4763 of a buffer chunk as if they were a NUL-terminated string. At
4764 least one such bug seems to be present in all currently used
4765 versions of Tor, and would allow an attacker to remotely crash
4766 most Tor instances, especially those compiled with extra compiler
4767 hardening. With this defense in place, such bugs can't crash Tor,
4768 though we should still fix them as they occur. Closes ticket
4769 20384 (TROVE-2016-10-001).
4771 o Minor features (geoip):
4772 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
4776 Changes in version 0.2.9.4-alpha - 2016-10-17
4777 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
4778 that would allow a remote attacker to crash a Tor client, hidden
4779 service, relay, or authority. All Tor users should upgrade to this
4780 version, or to 0.2.8.9. Patches will be released for older versions
4783 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
4784 previous versions of Tor, including the implementation of a feature to
4785 future- proof the Tor ecosystem against protocol changes, some bug
4786 fixes necessary for Tor Browser to use unix domain sockets correctly,
4787 and several portability improvements. We anticipate that this will be
4788 the last alpha in the Tor 0.2.9 series, and that the next release will
4789 be a release candidate.
4791 o Major features (security fixes):
4792 - Prevent a class of security bugs caused by treating the contents
4793 of a buffer chunk as if they were a NUL-terminated string. At
4794 least one such bug seems to be present in all currently used
4795 versions of Tor, and would allow an attacker to remotely crash
4796 most Tor instances, especially those compiled with extra compiler
4797 hardening. With this defense in place, such bugs can't crash Tor,
4798 though we should still fix them as they occur. Closes ticket
4799 20384 (TROVE-2016-10-001).
4801 o Major features (subprotocol versions):
4802 - Tor directory authorities now vote on a set of recommended
4803 subprotocol versions, and on a set of required subprotocol
4804 versions. Clients and relays that lack support for a _required_
4805 subprotocol version will not start; those that lack support for a
4806 _recommended_ subprotocol version will warn the user to upgrade.
4807 Closes ticket 19958; implements part of proposal 264.
4808 - Tor now uses "subprotocol versions" to indicate compatibility.
4809 Previously, versions of Tor looked at the declared Tor version of
4810 a relay to tell whether they could use a given feature. Now, they
4811 should be able to rely on its declared subprotocol versions. This
4812 change allows compatible implementations of the Tor protocol(s) to
4813 exist without pretending to be 100% bug-compatible with particular
4814 releases of Tor itself. Closes ticket 19958; implements part of
4817 o Minor feature (fallback directories):
4818 - Remove broken fallbacks from the hard-coded fallback directory
4819 list. Closes ticket 20190; patch by teor.
4821 o Minor features (client, directory):
4822 - Since authorities now omit all routers that lack the Running and
4823 Valid flags, we assume that any relay listed in the consensus must
4824 have those flags. Closes ticket 20001; implements part of
4827 o Minor features (compilation, portability):
4828 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
4831 o Minor features (development tools, etags):
4832 - Teach the "make tags" Makefile target how to correctly find
4833 "MOCK_IMPL" function definitions. Patch from nherring; closes
4836 o Minor features (geoip):
4837 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
4840 o Minor features (unix domain sockets):
4841 - When configuring a unix domain socket for a SocksPort,
4842 ControlPort, or Hidden service, you can now wrap the address in
4843 quotes, using C-style escapes inside the quotes. This allows unix
4844 domain socket paths to contain spaces.
4846 o Minor features (virtual addresses):
4847 - Increase the maximum number of bits for the IPv6 virtual network
4848 prefix from 16 to 104. In this way, the condition for address
4849 allocation is less restrictive. Closes ticket 20151; feature
4852 o Minor bugfixes (address discovery):
4853 - Stop reordering IP addresses returned by the OS. This makes it
4854 more likely that Tor will guess the same relay IP address every
4855 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
4856 Reported by René Mayrhofer, patch by "cypherpunks".
4858 o Minor bugfixes (client, unix domain sockets):
4859 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
4860 the client address is meaningless. Fixes bug 20261; bugfix
4863 o Minor bugfixes (compilation, OpenBSD):
4864 - Detect Libevent2 functions correctly on systems that provide
4865 libevent2, but where libevent1 is linked with -levent. Fixes bug
4866 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
4868 o Minor bugfixes (configuration):
4869 - When parsing quoted configuration values from the torrc file,
4870 handle windows line endings correctly. Fixes bug 19167; bugfix on
4871 0.2.0.16-alpha. Patch from "Pingl".
4873 o Minor bugfixes (getpass):
4874 - Defensively fix a non-triggerable heap corruption at do_getpass()
4875 to protect ourselves from mistakes in the future. Fixes bug
4876 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
4879 o Minor bugfixes (hidden service):
4880 - Allow hidden services to run on IPv6 addresses even when the
4881 IPv6Exit option is not set. Fixes bug 18357; bugfix
4885 - Add module-level internal documentation for 36 C files that
4886 previously didn't have a high-level overview. Closes ticket #20385.
4888 o Required libraries:
4889 - When building with OpenSSL, Tor now requires version 1.0.1 or
4890 later. OpenSSL 1.0.0 and earlier are no longer supported by the
4891 OpenSSL team, and should not be used. Closes ticket 20303.
4894 Changes in version 0.2.9.3-alpha - 2016-09-23
4895 Tor 0.2.9.3-alpha adds improved support for entities that want to make
4896 high-performance services available through the Tor .onion mechanism
4897 without themselves receiving anonymity as they host those services. It
4898 also tries harder to ensure that all steps on a circuit are using the
4899 strongest crypto possible, strengthens some TLS properties, and
4900 resolves several bugs -- including a pair of crash bugs from the 0.2.8
4901 series. Anybody running an earlier version of 0.2.9.x should upgrade.
4903 o Major bugfixes (crash, also in 0.2.8.8):
4904 - Fix a complicated crash bug that could affect Tor clients
4905 configured to use bridges when replacing a networkstatus consensus
4906 in which one of their bridges was mentioned. OpenBSD users saw
4907 more crashes here, but all platforms were potentially affected.
4908 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
4910 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
4911 - Fix a timing-dependent assertion failure that could occur when we
4912 tried to flush from a circuit after having freed its cells because
4913 of an out-of-memory condition. Fixes bug 20203; bugfix on
4914 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
4917 o Major features (circuit building, security):
4918 - Authorities, relays and clients now require ntor keys in all
4919 descriptors, for all hops (except for rare hidden service protocol
4920 cases), for all circuits, and for all other roles. Part of
4922 - Tor authorities, relays, and clients only use ntor, except for
4923 rare cases in the hidden service protocol. Part of ticket 19163.
4925 o Major features (single-hop "hidden" services):
4926 - Add experimental HiddenServiceSingleHopMode and
4927 HiddenServiceNonAnonymousMode options. When both are set to 1,
4928 every hidden service on a Tor instance becomes a non-anonymous
4929 Single Onion Service. Single Onions make one-hop (direct)
4930 connections to their introduction and renzedvous points. One-hop
4931 circuits make Single Onion servers easily locatable, but clients
4932 remain location-anonymous. This is compatible with the existing
4933 hidden service implementation, and works on the current tor
4934 network without any changes to older relays or clients. Implements
4935 proposal 260, completes ticket 17178. Patch by teor and asn.
4937 o Major features (resource management):
4938 - Tor can now notice it is about to run out of sockets, and
4939 preemptively close connections of lower priority. (This feature is
4940 off by default for now, since the current prioritizing method is
4941 yet not mature enough. You can enable it by setting
4942 "DisableOOSCheck 0", but watch out: it might close some sockets
4943 you would rather have it keep.) Closes ticket 18640.
4945 o Major bugfixes (circuit building):
4946 - Hidden service client-to-intro-point and service-to-rendezvous-
4947 point circuits use the TAP key supplied by the protocol, to avoid
4948 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
4950 o Major bugfixes (compilation, OpenBSD):
4951 - Fix a Libevent-detection bug in our autoconf script that would
4952 prevent Tor from linking successfully on OpenBSD. Patch from
4953 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
4955 o Major bugfixes (hidden services):
4956 - Clients now require hidden services to include the TAP keys for
4957 their intro points in the hidden service descriptor. This prevents
4958 an inadvertent upgrade to ntor, which a malicious hidden service
4959 could use to distinguish clients by consensus version. Fixes bug
4960 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
4962 o Minor features (security, TLS):
4963 - Servers no longer support clients that without AES ciphersuites.
4964 (3DES is no longer considered an acceptable cipher.) We believe
4965 that no such Tor clients currently exist, since Tor has required
4966 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
4968 o Minor feature (fallback directories):
4969 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
4970 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
4971 2016. Closes ticket 20190; patch by teor.
4973 o Minor features (geoip, also in 0.2.8.8):
4974 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
4977 o Minor feature (port flags):
4978 - Add new flags to the *Port options to finer control over which
4979 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
4980 and the synthetic flag OnionTrafficOnly, which is equivalent to
4981 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
4982 18693; patch by "teor".
4984 o Minor features (directory authority):
4985 - After voting, if the authorities decide that a relay is not
4986 "Valid", they no longer include it in the consensus at all. Closes
4987 ticket 20002; implements part of proposal 272.
4989 o Minor features (testing):
4990 - Disable memory protections on OpenBSD when performing our unit
4991 tests for memwipe(). The test deliberately invokes undefined
4992 behavior, and the OpenBSD protections interfere with this. Patch
4993 from "rubiate". Closes ticket 20066.
4995 o Minor features (testing, ipv6):
4996 - Add the single-onion and single-onion-ipv6 chutney targets to
4997 "make test-network-all". This requires a recent chutney version
4998 with the single onion network flavours (git c72a652 or later).
4999 Closes ticket 20072; patch by teor.
5000 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
5001 tests. Remove bridges+hs, as it's somewhat redundant. This
5002 requires a recent chutney version that supports IPv6 clients,
5003 relays, and authorities. Closes ticket 20069; patch by teor.
5005 o Minor features (Tor2web):
5006 - Make Tor2web clients respect ReachableAddresses. This feature was
5007 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
5008 0.2.8.7. Implements feature 20034. Patch by teor.
5010 o Minor features (unit tests):
5011 - We've done significant work to make the unit tests run faster.
5012 - Our link-handshake unit tests now check that when invalid
5013 handshakes fail, they fail with the error messages we expected.
5014 - Our unit testing code that captures log messages no longer
5015 prevents them from being written out if the user asked for them
5016 (by passing --debug or --info or or --notice --warn to the "test"
5017 binary). This change prevents us from missing unexpected log
5018 messages simply because we were looking for others. Related to
5020 - The unit tests now log all warning messages with the "BUG" flag.
5021 Previously, they only logged errors by default. This change will
5022 help us make our testing code more correct, and make sure that we
5023 only hit this code when we mean to. In the meantime, however,
5024 there will be more warnings in the unit test logs than before.
5025 This is preparatory work for ticket 19999.
5026 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
5027 assertion as a test failure.
5029 o Minor bug fixes (circuits):
5030 - Use the CircuitBuildTimeout option whenever
5031 LearnCircuitBuildTimeout is disabled. Previously, we would respect
5032 the option when a user disabled it, but not when it was disabled
5033 because some other option was set. Fixes bug 20073; bugfix on
5034 0.2.4.12-alpha. Patch by teor.
5036 o Minor bugfixes (allocation):
5037 - Change how we allocate memory for large chunks on buffers, to
5038 avoid a (currently impossible) integer overflow, and to waste less
5039 space when allocating unusually large chunks. Fixes bug 20081;
5040 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
5041 - Always include orconfig.h before including any other C headers.
5042 Sometimes, it includes macros that affect the behavior of the
5043 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
5044 first version to use AC_USE_SYSTEM_EXTENSIONS).
5045 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
5046 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
5047 Patch from Gisle Vanem.
5048 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
5049 They apparently require a set of annotations that we aren't
5050 currently using, and they create false positives in our pthreads
5051 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
5053 o Minor bugfixes (directory authority):
5054 - Die with a more useful error when the operator forgets to place
5055 the authority_signing_key file into the keys directory. This
5056 avoids an uninformative assert & traceback about having an invalid
5057 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
5058 - When allowing private addresses, mark Exits that only exit to
5059 private locations as such. Fixes bug 20064; bugfix
5062 o Minor bugfixes (documentation):
5063 - Document the default PathsNeededToBuildCircuits value that's used
5064 by clients when the directory authorities don't set
5065 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
5066 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
5067 - Fix manual for the User option: it takes a username, not a UID.
5068 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
5071 o Minor bugfixes (hidden services):
5072 - Stop logging intro point details to the client log on certain
5073 error conditions. Fixed as part of bug 20012; bugfix on
5074 0.2.4.8-alpha. Patch by teor.
5076 o Minor bugfixes (IPv6, testing):
5077 - Check for IPv6 correctly on Linux when running test networks.
5078 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
5080 o Minor bugfixes (Linux seccomp2 sandbox):
5081 - Add permission to run the sched_yield() and sigaltstack() system
5082 calls, in order to support versions of Tor compiled with asan or
5083 ubsan code that use these calls. Now "sandbox 1" and
5084 "--enable-expensive-hardening" should be compatible on more
5085 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
5087 o Minor bugfixes (logging):
5088 - When logging a message from the BUG() macro, be explicit about
5089 what we were asserting. Previously we were confusing what we were
5090 asserting with what the bug was. Fixes bug 20093; bugfix
5092 - When we are unable to remove the bw_accounting file, do not warn
5093 if the reason we couldn't remove it was that it didn't exist.
5094 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
5096 o Minor bugfixes (option parsing):
5097 - Count unix sockets when counting client listeners (SOCKS, Trans,
5098 NATD, and DNS). This has no user-visible behaviour changes: these
5099 options are set once, and never read. Required for correct
5100 behaviour in ticket 17178. Fixes bug 19677; bugfix on
5101 0.2.6.3-alpha. Patch by teor.
5103 o Minor bugfixes (options):
5104 - Check the consistency of UseEntryGuards and EntryNodes more
5105 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
5107 - Stop changing the configured value of UseEntryGuards on
5108 authorities and Tor2web clients. Fixes bug 20074; bugfix on
5109 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
5112 o Minor bugfixes (Tor2web):
5113 - Prevent Tor2web clients running hidden services, these services
5114 are not anonymous due to the one-hop client paths. Fixes bug
5115 19678. Patch by teor.
5117 o Minor bugfixes (unit tests):
5118 - Fix a shared-random unit test that was failing on big endian
5119 architectures due to internal representation of a integer copied
5120 to a buffer. The test is changed to take a full 32 bytes of data
5121 and use the output of a python script that make the COMMIT and
5122 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
5124 - The tor_tls_server_info_callback unit test no longer crashes when
5125 debug-level logging is turned on. Fixes bug 20041; bugfix
5129 Changes in version 0.2.8.8 - 2016-09-23
5130 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
5131 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
5132 who select public relays as their bridges.
5134 o Major bugfixes (crash):
5135 - Fix a complicated crash bug that could affect Tor clients
5136 configured to use bridges when replacing a networkstatus consensus
5137 in which one of their bridges was mentioned. OpenBSD users saw
5138 more crashes here, but all platforms were potentially affected.
5139 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
5141 o Major bugfixes (relay, OOM handler):
5142 - Fix a timing-dependent assertion failure that could occur when we
5143 tried to flush from a circuit after having freed its cells because
5144 of an out-of-memory condition. Fixes bug 20203; bugfix on
5145 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
5148 o Minor feature (fallback directories):
5149 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
5150 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
5151 2016. Closes ticket 20190; patch by teor.
5153 o Minor features (geoip):
5154 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
5158 Changes in version 0.2.9.2-alpha - 2016-08-24
5159 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
5160 several new features and bugfixes. It also includes an important
5161 authority update and an important bugfix from 0.2.8.7. Everyone who
5162 sets the ReachableAddresses option, and all bridges, are strongly
5163 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
5165 o Directory authority changes (also in 0.2.8.7):
5166 - The "Tonga" bridge authority has been retired; the new bridge
5167 authority is "Bifroest". Closes tickets 19728 and 19690.
5169 o Major bugfixes (client, security, also in 0.2.8.7):
5170 - Only use the ReachableAddresses option to restrict the first hop
5171 in a path. In earlier versions of 0.2.8.x, it would apply to
5172 every hop in the path, with a possible degradation in anonymity
5173 for anyone using an uncommon ReachableAddress setting. Fixes bug
5174 19973; bugfix on 0.2.8.2-alpha.
5176 o Major features (user interface):
5177 - Tor now supports the ability to declare options deprecated, so
5178 that we can recommend that people stop using them. Previously,
5179 this was done in an ad-hoc way. Closes ticket 19820.
5181 o Major bugfixes (directory downloads):
5182 - Avoid resetting download status for consensuses hourly, since we
5183 already have another, smarter retry mechanism. Fixes bug 8625;
5184 bugfix on 0.2.0.9-alpha.
5186 o Minor features (config):
5187 - Warn users when descriptor and port addresses are inconsistent.
5188 Mitigates bug 13953; patch by teor.
5190 o Minor features (geoip):
5191 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
5194 o Minor features (user interface):
5195 - There is a new --list-deprecated-options command-line option to
5196 list all of the deprecated options. Implemented as part of
5199 o Minor bugfixes (code style):
5200 - Fix an integer signedness conversion issue in the case conversion
5201 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
5203 o Minor bugfixes (compilation):
5204 - Build correctly on versions of libevent2 without support for
5205 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
5207 - Fix a compilation warning on GCC versions before 4.6. Our
5208 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
5209 when it is also required as an argument to the compiler pragma.
5210 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
5212 o Minor bugfixes (compilation, also in 0.2.8.7):
5213 - Remove an inappropriate "inline" in tortls.c that was causing
5214 warnings on older versions of GCC. Fixes bug 19903; bugfix
5217 o Minor bugfixes (fallback directories, also in 0.2.8.7):
5218 - Avoid logging a NULL string pointer when loading fallback
5219 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
5220 and 0.2.8.1-alpha. Report and patch by "rubiate".
5222 o Minor bugfixes (logging):
5223 - Log a more accurate message when we fail to dump a microdescriptor.
5224 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
5226 o Minor bugfixes (memory leak):
5227 - Fix a series of slow memory leaks related to parsing torrc files
5228 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
5230 o Deprecated features:
5231 - A number of DNS-cache-related sub-options for client ports are now
5232 deprecated for security reasons, and may be removed in a future
5233 version of Tor. (We believe that client-side DNS cacheing is a bad
5234 idea for anonymity, and you should not turn it on.) The options
5235 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
5236 UseIPv4Cache, and UseIPv6Cache.
5237 - A number of options are deprecated for security reasons, and may
5238 be removed in a future version of Tor. The options are:
5239 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
5240 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
5241 CloseHSClientCircuitsImmediatelyOnTimeout,
5242 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
5243 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
5244 UseNTorHandshake, and WarnUnsafeSocks.
5245 - The *ListenAddress options are now deprecated as unnecessary: the
5246 corresponding *Port options should be used instead. These options
5247 may someday be removed. The affected options are:
5248 ControlListenAddress, DNSListenAddress, DirListenAddress,
5249 NATDListenAddress, ORListenAddress, SocksListenAddress,
5250 and TransListenAddress.
5253 - Correct the IPv6 syntax in our documentation for the
5254 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
5257 - We no longer include the (dead, deprecated) bufferevent code in
5258 Tor. Closes ticket 19450. Based on a patch from U+039b.
5261 Changes in version 0.2.8.7 - 2016-08-24
5262 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
5263 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
5264 who sets the ReachableAddresses option, and all bridges, are strongly
5265 encouraged to upgrade.
5267 o Directory authority changes:
5268 - The "Tonga" bridge authority has been retired; the new bridge
5269 authority is "Bifroest". Closes tickets 19728 and 19690.
5271 o Major bugfixes (client, security):
5272 - Only use the ReachableAddresses option to restrict the first hop
5273 in a path. In earlier versions of 0.2.8.x, it would apply to
5274 every hop in the path, with a possible degradation in anonymity
5275 for anyone using an uncommon ReachableAddress setting. Fixes bug
5276 19973; bugfix on 0.2.8.2-alpha.
5278 o Minor features (geoip):
5279 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
5282 o Minor bugfixes (compilation):
5283 - Remove an inappropriate "inline" in tortls.c that was causing
5284 warnings on older versions of GCC. Fixes bug 19903; bugfix
5287 o Minor bugfixes (fallback directories):
5288 - Avoid logging a NULL string pointer when loading fallback
5289 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
5290 and 0.2.8.1-alpha. Report and patch by "rubiate".
5293 Changes in version 0.2.9.1-alpha - 2016-08-08
5294 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
5295 series. It improves our support for hardened builds and compiler
5296 warnings, deploys some critical infrastructure for improvements to
5297 hidden services, includes a new timing backend that we hope to use for
5298 better support for traffic padding, makes it easier for programmers to
5299 log unexpected events, and contains other small improvements to
5300 security, correctness, and performance.
5302 Below are the changes since 0.2.8.6.
5304 o New system requirements:
5305 - Tor now requires Libevent version 2.0.10-stable or later. Older
5306 versions of Libevent have less efficient backends for several
5307 platforms, and lack the DNS code that we use for our server-side
5308 DNS support. This implements ticket 19554.
5309 - Tor now requires zlib version 1.2 or later, for security,
5310 efficiency, and (eventually) gzip support. (Back when we started,
5311 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
5312 released in 2003. We recommend the latest version.)
5314 o Major features (build, hardening):
5315 - Tor now builds with -ftrapv by default on compilers that support
5316 it. This option detects signed integer overflow (which C forbids),
5317 and turns it into a hard-failure. We do not apply this option to
5318 code that needs to run in constant time to avoid side-channels;
5319 instead, we use -fwrapv in that code. Closes ticket 17983.
5320 - When --enable-expensive-hardening is selected, stop applying the
5321 clang/gcc sanitizers to code that needs to run in constant time.
5322 Although we are aware of no introduced side-channels, we are not
5323 able to prove that there are none. Related to ticket 17983.
5325 o Major features (compilation):
5326 - Our big list of extra GCC warnings is now enabled by default when
5327 building with GCC (or with anything like Clang that claims to be
5328 GCC-compatible). To make all warnings into fatal compilation
5329 errors, pass --enable-fatal-warnings to configure. Closes
5331 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
5332 turn on C and POSIX extensions. (Previously, we attempted to do
5333 this on an ad hoc basis.) Closes ticket 19139.
5335 o Major features (directory authorities, hidden services):
5336 - Directory authorities can now perform the shared randomness
5337 protocol specified by proposal 250. Using this protocol, directory
5338 authorities generate a global fresh random value every day. In the
5339 future, this value will be used by hidden services to select
5340 HSDirs. This release implements the directory authority feature;
5341 the hidden service side will be implemented in the future as part
5342 of proposal 224. Resolves ticket 16943; implements proposal 250.
5344 o Major features (downloading, random exponential backoff):
5345 - When we fail to download an object from a directory service, wait
5346 for an (exponentially increasing) randomized amount of time before
5347 retrying, rather than a fixed interval as we did before. This
5348 prevents a group of Tor instances from becoming too synchronized,
5349 or a single Tor instance from becoming too predictable, in its
5350 download schedule. Closes ticket 15942.
5352 o Major bugfixes (exit policies):
5353 - Avoid disclosing exit outbound bind addresses, configured port
5354 bind addresses, and local interface addresses in relay descriptors
5355 by default under ExitPolicyRejectPrivate. Instead, only reject
5356 these (otherwise unlisted) addresses if
5357 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
5358 0.2.7.2-alpha. Patch by teor.
5360 o Major bugfixes (hidden service client):
5361 - Allow Tor clients with appropriate controllers to work with
5362 FetchHidServDescriptors set to 0. Previously, this option also
5363 disabled descriptor cache lookup, thus breaking hidden services
5364 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
5366 o Minor features (build, hardening):
5367 - Detect and work around a libclang_rt problem that would prevent
5368 clang from finding __mulodi4() on some 32-bit platforms, and thus
5369 keep -ftrapv from linking on those systems. Closes ticket 19079.
5370 - When building on a system without runtime support for the runtime
5371 hardening options, try to log a useful warning at configuration
5372 time, rather than an incomprehensible warning at link time. If
5373 expensive hardening was requested, this warning becomes an error.
5374 Closes ticket 18895.
5376 o Minor features (code safety):
5377 - In our integer-parsing functions, ensure that maxiumum value we
5378 give is no smaller than the minimum value. Closes ticket 19063;
5381 o Minor features (controller):
5382 - Implement new GETINFO queries for all downloads that use
5383 download_status_t to schedule retries. This allows controllers to
5384 examine the schedule for pending downloads. Closes ticket 19323.
5385 - Allow controllers to configure basic client authorization on
5386 hidden services when they create them with the ADD_ONION control
5387 command. Implements ticket 15588. Patch by "special".
5388 - Fire a STATUS_SERVER controller event whenever the hibernation
5389 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
5391 o Minor features (directory authority):
5392 - Directory authorities now only give the Guard flag to a relay if
5393 they are also giving it the Stable flag. This change allows us to
5394 simplify path selection for clients. It should have minimal effect
5395 in practice, since >99% of Guards already have the Stable flag.
5396 Implements ticket 18624.
5397 - Directory authorities now write their v3-status-votes file out to
5398 disk earlier in the consensus process, so we have a record of the
5399 votes even if we abort the consensus process. Resolves
5402 o Minor features (hidden service):
5403 - Stop being so strict about the payload length of "rendezvous1"
5404 cells. We used to be locked in to the "TAP" handshake length, and
5405 now we can handle better handshakes like "ntor". Resolves
5408 o Minor features (infrastructure, time):
5409 - Tor now uses the operating system's monotonic timers (where
5410 available) for internal fine-grained timing. Previously we would
5411 look at the system clock, and then attempt to compensate for the
5412 clock running backwards. Closes ticket 18908.
5413 - Tor now includes an improved timer backend, so that we can
5414 efficiently support tens or hundreds of thousands of concurrent
5415 timers, as will be needed for some of our planned anti-traffic-
5416 analysis work. This code is based on William Ahern's "timeout.c"
5417 project, which implements a "tickless hierarchical timing wheel".
5418 Closes ticket 18365.
5420 o Minor features (logging):
5421 - Provide a more useful warning message when configured with an
5422 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
5423 - When dumping unparseable router descriptors, optionally store them
5424 in separate files, named by digest, up to a configurable size
5425 limit. You can change the size limit by setting the
5426 MaxUnparseableDescSizeToLog option, and disable this feature by
5427 setting that option to 0. Closes ticket 18322.
5428 - Add a set of macros to check nonfatal assertions, for internal
5429 use. Migrating more of our checks to these should help us avoid
5430 needless crash bugs. Closes ticket 18613.
5432 o Minor features (performance):
5433 - Changer the "optimistic data" extension from "off by default" to
5434 "on by default". The default was ordinarily overridden by a
5435 consensus option, but when clients were bootstrapping for the
5436 first time, they would not have a consensus to get the option
5437 from. Changing this default When fetching a consensus for the
5438 first time, use optimistic data. This saves a round-trip during
5439 startup. Closes ticket 18815.
5441 o Minor features (relay, usability):
5442 - When the directory authorities refuse a bad relay's descriptor,
5443 encourage the relay operator to contact us. Many relay operators
5444 won't notice this line in their logs, but it's a win if even a few
5445 learn why we don't like what their relay was doing. Resolves
5448 o Minor features (testing):
5449 - Let backtrace tests work correctly under AddressSanitizer. Fixes
5450 part of bug 18934; bugfix on 0.2.5.2-alpha.
5451 - Move the test-network.sh script to chutney, and modify tor's test-
5452 network.sh to call the (newer) chutney version when available.
5453 Resolves ticket 19116. Patch by teor.
5454 - Use the lcov convention for marking lines as unreachable, so that
5455 we don't count them when we're generating test coverage data.
5456 Update our coverage tools to understand this convention. Closes
5459 o Minor bugfixes (bootstrap):
5460 - Remember the directory we fetched the consensus or previous
5461 certificates from, and use it to fetch future authority
5462 certificates. This change improves bootstrapping performance.
5463 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
5465 o Minor bugfixes (build):
5466 - The test-stem and test-network makefile targets now depend only on
5467 the tor binary that they are testing. Previously, they depended on
5468 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
5469 patch from "cypherpunks".
5471 o Minor bugfixes (circuits):
5472 - Make sure extend_info_from_router() is only called on servers.
5473 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
5475 o Minor bugfixes (compilation):
5476 - When building with Clang, use a full set of GCC warnings.
5477 (Previously, we included only a subset, because of the way we
5478 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
5480 o Minor bugfixes (directory authority):
5481 - Authorities now sort the "package" lines in their votes, for ease
5482 of debugging. (They are already sorted in consensus documents.)
5483 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
5484 - When parsing a detached signature, make sure we use the length of
5485 the digest algorithm instead of an hardcoded DIGEST256_LEN in
5486 order to avoid comparing bytes out-of-bounds with a smaller digest
5487 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
5489 o Minor bugfixes (documentation):
5490 - Document the --passphrase-fd option in the tor manpage. Fixes bug
5491 19504; bugfix on 0.2.7.3-rc.
5492 - Fix the description of the --passphrase-fd option in the
5493 tor-gencert manpage. The option is used to pass the number of a
5494 file descriptor to read the passphrase from, not to read the file
5495 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
5497 o Minor bugfixes (ephemeral hidden service):
5498 - When deleting an ephemeral hidden service, close its intro points
5499 even if they are not completely open. Fixes bug 18604; bugfix
5502 o Minor bugfixes (guard selection):
5503 - Use a single entry guard even if the NumEntryGuards consensus
5504 parameter is not provided. Fixes bug 17688; bugfix
5506 - Don't mark guards as unreachable if connection_connect() fails.
5507 That function fails for local reasons, so it shouldn't reveal
5508 anything about the status of the guard. Fixes bug 14334; bugfix
5511 o Minor bugfixes (hidden service client):
5512 - Increase the minimum number of internal circuits we preemptively
5513 build from 2 to 3, so a circuit is available when a client
5514 connects to another onion service. Fixes bug 13239; bugfix
5517 o Minor bugfixes (logging):
5518 - When logging a directory ownership mismatch, log the owning
5519 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
5521 o Minor bugfixes (memory leaks):
5522 - Fix a small, uncommon memory leak that could occur when reading a
5523 truncated ed25519 key file. Fixes bug 18956; bugfix
5526 o Minor bugfixes (testing):
5527 - Allow clients to retry HSDirs much faster in test networks. Fixes
5528 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
5529 - Disable ASAN's detection of segmentation faults while running
5530 test_bt.sh, so that we can make sure that our own backtrace
5531 generation code works. Fixes another aspect of bug 18934; bugfix
5532 on 0.2.5.2-alpha. Patch from "cypherpunks".
5533 - Fix the test-network-all target on out-of-tree builds by using the
5534 correct path to the test driver script. Fixes bug 19421; bugfix
5537 o Minor bugfixes (time):
5538 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
5539 bugfix on all released tor versions.
5540 - When computing the difference between two times in milliseconds,
5541 we now round to the nearest millisecond correctly. Previously, we
5542 could sometimes round in the wrong direction. Fixes bug 19428;
5543 bugfix on 0.2.2.2-alpha.
5545 o Minor bugfixes (user interface):
5546 - Display a more accurate number of suppressed messages in the log
5547 rate-limiter. Previously, there was a potential integer overflow
5548 in the counter. Now, if the number of messages hits a maximum, the
5549 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
5551 - Fix a typo in the passphrase prompt for the ed25519 identity key.
5552 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
5554 o Code simplification and refactoring:
5555 - Remove redundant declarations of the MIN macro. Closes
5557 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
5558 Closes ticket 18462; patch from "icanhasaccount".
5559 - Split the 600-line directory_handle_command_get function into
5560 separate functions for different URL types. Closes ticket 16698.
5563 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
5564 ticket 19153. Patch from "U+039b".
5567 - Remove support for "GET /tor/bytes.txt" DirPort request, and
5568 "GETINFO dir-usage" controller request, which were only available
5569 via a compile-time option in Tor anyway. Feature was added in
5570 0.2.2.1-alpha. Resolves ticket 19035.
5571 - There is no longer a compile-time option to disable support for
5572 TransPort. (If you don't want TransPort; just don't use it.) Patch
5573 from "U+039b". Closes ticket 19449.
5576 - Run more workqueue tests as part of "make check". These had
5577 previously been implemented, but you needed to know special
5578 command-line options to enable them.
5579 - We now have unit tests for our code to reject zlib "compression
5580 bombs". (Fortunately, the code works fine.)
5583 Changes in version 0.2.8.6 - 2016-08-02
5585 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
5587 The Tor 0.2.8 series improves client bootstrapping performance,
5588 completes the authority-side implementation of improved identity
5589 keys for relays, and includes numerous bugfixes and performance
5590 improvements throughout the program. This release continues to
5591 improve the coverage of Tor's test suite. For a full list of
5592 changes since Tor 0.2.7, see the ReleaseNotes file.
5594 Changes since 0.2.8.5-rc:
5596 o Minor features (geoip):
5597 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
5600 o Minor bugfixes (compilation):
5601 - Fix a compilation warning in the unit tests on systems where char
5602 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
5604 o Minor bugfixes (fallback directories):
5605 - Remove 1 fallback that was on the hardcoded list, then opted-out,
5606 leaving 89 of the 100 fallbacks originally introduced in Tor
5607 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
5609 o Minor bugfixes (Linux seccomp2 sandbox):
5610 - Allow more syscalls when running with "Sandbox 1" enabled:
5611 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
5612 some systems, these are required for Tor to start. Fixes bug
5613 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
5614 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
5615 so that get_interface_address6_via_udp_socket_hack() can work.
5616 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
5619 Changes in version 0.2.8.5-rc - 2016-07-07
5620 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
5621 series. If we find no new bugs or regressions here, the first stable
5622 0.2.8 release will be identical to it. It has a few small bugfixes
5623 against previous versions.
5625 o Directory authority changes:
5626 - Urras is no longer a directory authority. Closes ticket 19271.
5628 o Major bugfixes (heartbeat):
5629 - Fix a regression that would crash Tor when the periodic
5630 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
5631 0.2.8.1-alpha. Reported by "kubaku".
5633 o Minor features (build):
5634 - Tor now again builds with the recent OpenSSL 1.1 development
5635 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
5636 - When building manual pages, set the timezone to "UTC", so that the
5637 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
5638 Patch from intrigeri.
5640 o Minor bugfixes (fallback directory selection):
5641 - Avoid errors during fallback selection if there are no eligible
5642 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
5645 o Minor bugfixes (IPv6, microdescriptors):
5646 - Don't check node addresses when we only have a routerstatus. This
5647 allows IPv6-only clients to bootstrap by fetching microdescriptors
5648 from fallback directory mirrors. (The microdescriptor consensus
5649 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
5652 o Minor bugfixes (logging):
5653 - Reduce pointlessly verbose log messages when directory servers
5654 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
5655 0.2.8.1-alpha. Patch by teor.
5656 - When a fallback directory changes its fingerprint from the hard-
5657 coded fingerprint, log a less severe, more explanatory log
5658 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
5660 o Minor bugfixes (Linux seccomp2 sandboxing):
5661 - Allow statistics to be written to disk when "Sandbox 1" is
5662 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
5663 0.2.6.1-alpha respectively.
5665 o Minor bugfixes (user interface):
5666 - Remove a warning message "Service [scrubbed] not found after
5667 descriptor upload". This message appears when one uses HSPOST
5668 control command to upload a service descriptor. Since there is
5669 only a descriptor and no service, showing this message is
5670 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
5672 o Fallback directory list:
5673 - Add a comment to the generated fallback directory list that
5674 explains how to comment out unsuitable fallbacks in a way that's
5675 compatible with the stem fallback parser.
5676 - Update fallback whitelist and blacklist based on relay operator
5677 emails. Blacklist unsuitable (non-working, over-volatile)
5678 fallbacks. Resolves ticket 19071. Patch by teor.
5679 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
5680 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
5681 ticket 19071; patch by teor.
5684 Changes in version 0.2.8.4-rc - 2016-06-15
5685 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
5686 If we find no new bugs or regressions here, the first stable 0.2.8
5687 release will be identical to it. It has a few small bugfixes against
5690 o Major bugfixes (user interface):
5691 - Correctly give a warning in the cases where a relay is specified
5692 by nickname, and one such relay is found, but it is not officially
5693 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
5695 o Minor features (build):
5696 - Tor now builds once again with the recent OpenSSL 1.1 development
5697 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
5699 o Minor features (geoip):
5700 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
5703 o Minor bugfixes (compilation):
5704 - Cause the unit tests to compile correctly on mingw64 versions that
5705 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
5707 o Minor bugfixes (downloading):
5708 - Predict more correctly whether we'll be downloading over HTTP when
5709 we determine the maximum length of a URL. This should avoid a
5710 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
5714 Changes in version 0.2.8.3-alpha - 2016-05-26
5715 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
5716 the course of the 0.2.8 development cycle. It improves the behavior of
5717 directory clients, fixes several crash bugs, fixes a gap in compiler
5718 hardening, and allows the full integration test suite to run on
5721 o Major bugfixes (security, client, DNS proxy):
5722 - Stop a crash that could occur when a client running with DNSPort
5723 received a query with multiple address types, and the first
5724 address type was not supported. Found and fixed by Scott Dial.
5725 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5727 o Major bugfixes (security, compilation):
5728 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
5729 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
5730 cause a compiler warning, thereby making other checks fail, and
5731 needlessly disabling compiler-hardening support. Fixes one case of
5732 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
5734 o Major bugfixes (security, directory authorities):
5735 - Fix a crash and out-of-bounds write during authority voting, when
5736 the list of relays includes duplicate ed25519 identity keys. Fixes
5737 bug 19032; bugfix on 0.2.8.2-alpha.
5739 o Major bugfixes (client, bootstrapping):
5740 - Check if bootstrap consensus downloads are still needed when the
5741 linked connection attaches. This prevents tor making unnecessary
5742 begindir-style connections, which are the only directory
5743 connections tor clients make since the fix for 18483 was merged.
5744 - Fix some edge cases where consensus download connections may not
5745 have been closed, even though they were not needed. Related to fix
5747 - Make relays retry consensus downloads the correct number of times,
5748 rather than the more aggressive client retry count. Fixes part of
5750 - Stop downloading consensuses when we have a consensus, even if we
5751 don't have all the certificates for it yet. Fixes bug 18809;
5752 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
5754 o Major bugfixes (directory mirrors):
5755 - Decide whether to advertise begindir support in the the same way
5756 we decide whether to advertise our DirPort. Allowing these
5757 decisions to become out-of-sync led to surprising behavior like
5758 advertising begindir support when hibernation made us not
5759 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
5762 o Major bugfixes (IPv6 bridges, client):
5763 - Actually use IPv6 addresses when selecting directory addresses for
5764 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
5767 o Major bugfixes (key management):
5768 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5769 pointer to the previous (uninitialized) key value. The impact here
5770 should be limited to a difficult-to-trigger crash, if OpenSSL is
5771 running an engine that makes key generation failures possible, or
5772 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5773 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5776 o Major bugfixes (testing):
5777 - Fix a bug that would block 'make test-network-all' on systems where
5778 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
5779 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
5780 bugfix on 0.2.8.1-alpha.
5782 o Minor features (clients):
5783 - Make clients, onion services, and bridge relays always use an
5784 encrypted begindir connection for directory requests. Resolves
5785 ticket 18483. Patch by "teor".
5787 o Minor features (fallback directory mirrors):
5788 - Give each fallback the same weight for client selection; restrict
5789 fallbacks to one per operator; report fallback directory detail
5790 changes when rebuilding list; add new fallback directory mirrors
5791 to the whitelist; and many other minor simplifications and fixes.
5792 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
5793 0.2.8.1-alpha; patch by "teor".
5794 - Replace the 21 fallbacks generated in January 2016 and included in
5795 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
5796 2016. Closes task 17158; patch by "teor".
5798 o Minor features (geoip):
5799 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
5802 o Minor bugfixes (assert, portability):
5803 - Fix an assertion failure in memarea.c on systems where "long" is
5804 shorter than the size of a pointer. Fixes bug 18716; bugfix
5807 o Minor bugfixes (bootstrap):
5808 - Consistently use the consensus download schedule for authority
5809 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
5811 o Minor bugfixes (build):
5812 - Remove a pair of redundant AM_CONDITIONAL declarations from
5813 configure.ac. Fixes one final case of bug 17744; bugfix
5815 - Resolve warnings when building on systems that are concerned with
5816 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
5818 - When libscrypt.h is found, but no libscrypt library can be linked,
5819 treat libscrypt as absent. Fixes bug 19161; bugfix
5822 o Minor bugfixes (client):
5823 - Turn all TestingClientBootstrap* into non-testing torrc options.
5824 This changes simply renames them by removing "Testing" in front of
5825 them and they do not require TestingTorNetwork to be enabled
5826 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
5827 - Make directory node selection more reliable, mainly for IPv6-only
5828 clients and clients with few reachable addresses. Fixes bug 18929;
5829 bugfix on 0.2.8.1-alpha. Patch by "teor".
5831 o Minor bugfixes (controller, microdescriptors):
5832 - Make GETINFO dir/status-vote/current/consensus conform to the
5833 control specification by returning "551 Could not open cached
5834 consensus..." when not caching consensuses. Fixes bug 18920;
5835 bugfix on 0.2.2.6-alpha.
5837 o Minor bugfixes (crypto, portability):
5838 - The SHA3 and SHAKE routines now produce the correct output on Big
5839 Endian systems. No code calls either algorithm yet, so this is
5840 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
5841 - Tor now builds again with the recent OpenSSL 1.1 development
5842 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
5845 o Minor bugfixes (directories):
5846 - When fetching extrainfo documents, compare their SHA256 digests
5847 and Ed25519 signing key certificates with the routerinfo that led
5848 us to fetch them, rather than with the most recent routerinfo.
5849 Otherwise we generate many spurious warnings about mismatches.
5850 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
5852 o Minor bugfixes (logging):
5853 - When we can't generate a signing key because OfflineMasterKey is
5854 set, do not imply that we should have been able to load it. Fixes
5855 bug 18133; bugfix on 0.2.7.2-alpha.
5856 - Stop periodic_event_dispatch() from blasting twelve lines per
5857 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
5858 - When rejecting a misformed INTRODUCE2 cell, only log at
5859 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
5861 o Minor bugfixes (pluggable transports):
5862 - Avoid reporting a spurious error when we decide that we don't need
5863 to terminate a pluggable transport because it has already exited.
5864 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
5866 o Minor bugfixes (pointer arithmetic):
5867 - Fix a bug in memarea_alloc() that could have resulted in remote
5868 heap write access, if Tor had ever passed an unchecked size to
5869 memarea_alloc(). Fortunately, all the sizes we pass to
5870 memarea_alloc() are pre-checked to be less than 128 kilobytes.
5871 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
5874 o Minor bugfixes (relays):
5875 - Consider more config options when relays decide whether to
5876 regenerate their descriptor. Fixes more of bug 12538; bugfix
5878 - Resolve some edge cases where we might launch an ORPort
5879 reachability check even when DisableNetwork is set. Noticed while
5880 fixing bug 18616; bugfix on 0.2.3.9-alpha.
5882 o Minor bugfixes (statistics):
5883 - We now include consensus downloads via IPv6 in our directory-
5884 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
5886 o Minor bugfixes (testing):
5887 - Allow directories in small networks to bootstrap by skipping
5888 DirPort checks when the consensus has no exits. Fixes bug 19003;
5889 bugfix on 0.2.8.1-alpha. Patch by teor.
5890 - Fix a small memory leak that would occur when the
5891 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
5892 bugfix on 0.2.5.2-alpha.
5894 o Minor bugfixes (time handling):
5895 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
5896 field. Otherwise, our unit tests crash on Windows. Fixes bug
5897 18977; bugfix on 0.2.2.25-alpha.
5900 - Document the contents of the 'datadir/keys' subdirectory in the
5901 manual page. Closes ticket 17621.
5902 - Stop recommending use of nicknames to identify relays in our
5903 MapAddress documentation. Closes ticket 18312.
5906 Changes in version 0.2.8.2-alpha - 2016-03-28
5907 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
5908 bugs in earlier versions of Tor, including some that prevented
5909 authorities using Tor 0.2.7.x from running correctly. IPv6 and
5910 directory support should also be much improved.
5912 o New system requirements:
5913 - Tor no longer supports versions of OpenSSL with a broken
5914 implementation of counter mode. (This bug was present in OpenSSL
5915 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
5916 longer runs with, these versions.
5917 - Tor no longer attempts to support platforms where the "time_t"
5918 type is unsigned. (To the best of our knowledge, only OpenVMS does
5919 this, and Tor has never actually built on OpenVMS.) Closes
5921 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
5922 later (released in 2008 and 2009 respectively). If you are
5923 building Tor from the git repository instead of from the source
5924 distribution, and your tools are older than this, you will need to
5925 upgrade. Closes ticket 17732.
5927 o Major bugfixes (security, pointers):
5928 - Avoid a difficult-to-trigger heap corruption attack when extending
5929 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5930 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5931 Reported by Guido Vranken.
5933 o Major bugfixes (bridges, pluggable transports):
5934 - Modify the check for OR connections to private addresses. Allow
5935 bridges on private addresses, including pluggable transports that
5936 ignore the (potentially private) address in the bridge line. Fixes
5937 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
5939 o Major bugfixes (compilation):
5940 - Repair hardened builds under the clang compiler. Previously, our
5941 use of _FORTIFY_SOURCE would conflict with clang's address
5942 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
5944 o Major bugfixes (crash on shutdown):
5945 - Correctly handle detaching circuits from muxes when shutting down.
5946 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
5947 - Fix an assert-on-exit bug related to counting memory usage in
5948 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
5950 o Major bugfixes (crash on startup):
5951 - Fix a segfault during startup: If a Unix domain socket was
5952 configured as listener (such as a ControlSocket or a SocksPort
5953 "unix:" socket), and tor was started as root but not configured to
5954 switch to another user, tor would segfault while trying to string
5955 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
5958 o Major bugfixes (dns proxy mode, crash):
5959 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5960 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5962 o Major bugfixes (relays, bridge clients):
5963 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
5964 bridge clients use the address configured in the bridge line.
5965 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
5968 o Major bugfixes (voting):
5969 - Actually enable support for authorities to match routers by their
5970 Ed25519 identities. Previously, the code had been written, but
5971 some debugging code that had accidentally been left in the
5972 codebase made it stay turned off. Fixes bug 17702; bugfix
5974 - When collating votes by Ed25519 identities, authorities now
5975 include a "NoEdConsensus" flag if the ed25519 value (or lack
5976 thereof) for a server does not reflect the majority consensus.
5977 Related to bug 17668; bugfix on 0.2.7.2-alpha.
5978 - When generating a vote with keypinning disabled, never include two
5979 entries for the same ed25519 identity. This bug was causing
5980 authorities to generate votes that they could not parse when a
5981 router violated key pinning by changing its RSA identity but
5982 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
5983 18318. Bugfix on 0.2.7.2-alpha.
5985 o Minor features (security, win32):
5986 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
5987 attack. Fixes bug 18123; bugfix on all tor versions. Patch
5990 o Minor features (bug-resistance):
5991 - Make Tor survive errors involving connections without a
5992 corresponding event object. Previously we'd fail with an
5993 assertion; now we produce a log message. Related to bug 16248.
5995 o Minor features (build):
5996 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
5997 as having possible IPFW support. Closes ticket 18448. Patch from
6000 o Minor features (code hardening):
6001 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
6002 level code, to harden against accidental failures to NUL-
6003 terminate. Part of ticket 17852. Patch from jsturgix. Found
6006 o Minor features (crypto):
6007 - Validate the hard-coded Diffie-Hellman parameters and ensure that
6008 p is a safe prime, and g is a suitable generator. Closes
6011 o Minor features (geoip):
6012 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
6015 o Minor features (hidden service directory):
6016 - Streamline relay-side hsdir handling: when relays consider whether
6017 to accept an uploaded hidden service descriptor, they no longer
6018 check whether they are one of the relays in the network that is
6019 "supposed" to handle that descriptor. Implements ticket 18332.
6021 o Minor features (IPv6):
6022 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
6023 to 1, tor prefers IPv6 directory addresses.
6024 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
6025 avoids using IPv4 for client OR and directory connections.
6026 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
6027 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
6028 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
6030 o Minor features (linux seccomp2 sandbox):
6031 - Reject attempts to change our Address with "Sandbox 1" enabled.
6032 Changing Address with Sandbox turned on would never actually work,
6033 but previously it would fail in strange and confusing ways. Found
6036 o Minor features (robustness):
6037 - Exit immediately with an error message if the code attempts to use
6038 Libevent without having initialized it. This should resolve some
6039 frequently-made mistakes in our unit tests. Closes ticket 18241.
6041 o Minor features (unix domain sockets):
6042 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
6043 Unix domain sockets without checking the permissions on the parent
6044 directory. (Tor checks permissions by default because some
6045 operating systems only check permissions on the parent directory.
6046 However, some operating systems do look at permissions on the
6047 socket, and tor's default check is unneeded.) Closes ticket 18458.
6050 o Minor bugfixes (exit policies, security):
6051 - Refresh an exit relay's exit policy when interface addresses
6052 change. Previously, tor only refreshed the exit policy when the
6053 configured external address changed. Fixes bug 18208; bugfix on
6054 0.2.7.3-rc. Patch by teor.
6056 o Minor bugfixes (security, hidden services):
6057 - Prevent hidden services connecting to client-supplied rendezvous
6058 addresses that are reserved as internal or multicast. Fixes bug
6059 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
6061 o Minor bugfixes (build):
6062 - Do not link the unit tests against both the testing and non-
6063 testing versions of the static libraries. Fixes bug 18490; bugfix
6065 - Avoid spurious failures from configure files related to calling
6066 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
6067 0.2.0.1-alpha. Patch from "cypherpunks".
6068 - Silence spurious clang-scan warnings in the ed25519_donna code by
6069 explicitly initializing some objects. Fixes bug 18384; bugfix on
6070 0.2.7.2-alpha. Patch by teor.
6072 o Minor bugfixes (client, bootstrap):
6073 - Count receipt of new microdescriptors as progress towards
6074 bootstrapping. Previously, with EntryNodes set, Tor might not
6075 successfully repopulate the guard set on bootstrapping. Fixes bug
6076 16825; bugfix on 0.2.3.1-alpha.
6078 o Minor bugfixes (code correctness):
6079 - Update to the latest version of Trunnel, which tries harder to
6080 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
6081 by clang address sanitizer. Fixes bug 18373; bugfix
6084 o Minor bugfixes (configuration):
6085 - Fix a tiny memory leak when parsing a port configuration ending in
6086 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
6088 o Minor bugfixes (containers):
6089 - If we somehow attempt to construct a heap with more than
6090 1073741822 elements, avoid an integer overflow when maintaining
6091 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
6093 o Minor bugfixes (correctness):
6094 - Fix a bad memory handling bug that would occur if we had queued a
6095 cell on a channel's incoming queue. Fortunately, we can't actually
6096 queue a cell like that as our code is constructed today, but it's
6097 best to avoid this kind of error, even if there isn't any code
6098 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
6100 o Minor bugfixes (directory):
6101 - When generating a URL for a directory server on an IPv6 address,
6102 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
6103 on 0.2.3.9-alpha. Patch from Malek.
6105 o Minor bugfixes (fallback directory mirrors):
6106 - When requesting extrainfo descriptors from a trusted directory
6107 server, check whether it is an authority or a fallback directory
6108 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
6109 0.2.4.7-alpha. Reported by atagar, patch by teor.
6111 o Minor bugfixes (hidden service, client):
6112 - Handle the case where the user makes several fast consecutive
6113 requests to the same .onion address. Previously, the first six
6114 requests would each trigger a descriptor fetch, each picking a
6115 directory (there are 6 overall) and the seventh one would fail
6116 because no directories were left, thereby triggering a close on
6117 all current directory connections asking for the hidden service.
6118 The solution here is to not close the connections if we have
6119 pending directory fetches. Fixes bug 15937; bugfix
6122 o Minor bugfixes (hidden service, control port):
6123 - Add the onion address to the HS_DESC event for the UPLOADED action
6124 both on success or failure. It was previously hardcoded with
6125 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
6127 o Minor bugfixes (hidden service, directory):
6128 - Bridges now refuse "rendezvous2" (hidden service descriptor)
6129 publish attempts. Suggested by ticket 18332.
6131 o Minor bugfixes (linux seccomp2 sandbox):
6132 - Allow the setrlimit syscall, and the prlimit and prlimit64
6133 syscalls, which some libc implementations use under the hood.
6134 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
6135 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
6136 enabled and no DNS resolvers configured. This should help TAILS
6137 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
6138 - Fix the sandbox's interoperability with unix domain sockets under
6139 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
6141 o Minor bugfixes (logging):
6142 - When logging information about an unparsable networkstatus vote or
6143 consensus, do not say "vote" when we mean consensus. Fixes bug
6144 18368; bugfix on 0.2.0.8-alpha.
6145 - Scrub service name in "unrecognized service ID" log messages.
6146 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
6147 - Downgrade logs and backtraces about IP versions to info-level.
6148 Only log backtraces once each time tor runs. Assists in diagnosing
6149 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
6150 Christian, patch by teor.
6152 o Minor bugfixes (memory safety):
6153 - Avoid freeing an uninitialized pointer when opening a socket fails
6154 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
6155 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
6157 - Correctly duplicate addresses in get_interface_address6_list().
6158 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
6159 patch by "cypherpunks".
6160 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
6162 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
6163 18672; bugfix on 0.2.5.1-alpha.
6165 o Minor bugfixes (private directory):
6166 - Prevent a race condition when creating private directories. Fixes
6167 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
6168 Patch from jsturgix. Found with Flawfinder.
6170 o Minor bugfixes (test networks, IPv6):
6171 - Allow internal IPv6 addresses in descriptors in test networks.
6172 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
6175 o Minor bugfixes (testing):
6176 - We no longer disable assertions in the unit tests when coverage is
6177 enabled. Instead, we require you to say --disable-asserts-in-tests
6178 to the configure script if you need assertions disabled in the
6179 unit tests (for example, if you want to perform branch coverage).
6180 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
6182 o Minor bugfixes (time parsing):
6183 - Avoid overflow in tor_timegm when parsing dates in and after 2038
6184 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
6185 0.0.2pre14. Patch by teor.
6187 o Minor bugfixes (tor-gencert):
6188 - Correctly handle the case where an authority operator enters a
6189 passphrase but sends an EOF before sending a newline. Fixes bug
6190 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
6192 o Code simplification and refactoring:
6193 - Quote all the string interpolations in configure.ac -- even those
6194 which we are pretty sure can't contain spaces. Closes ticket
6195 17744. Patch from zerosion.
6196 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
6197 inplace, so there's no need to have a separate implementation for
6198 the non-inplace code. Closes ticket 18258. Patch from Malek.
6199 - Simplify return types for some crypto functions that can't
6200 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
6203 - Change build messages to refer to "Fedora" instead of "Fedora
6204 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
6205 Patches from "icanhasaccount" and "cypherpunks".
6208 - We no longer maintain an internal freelist in memarea.c.
6209 Allocators should be good enough to make this code unnecessary,
6210 and it's doubtful that it ever had any performance benefit.
6213 - Fix several warnings from clang's address sanitizer produced in
6215 - Treat backtrace test failures as expected on FreeBSD until we
6216 solve bug 17808. Closes ticket 18204.
6219 Changes in version 0.2.8.1-alpha - 2016-02-04
6220 Tor 0.2.8.1-alpha is the first alpha release in its series. It
6221 includes numerous small features and bugfixes against previous Tor
6222 versions, and numerous small infrastructure improvements. The most
6223 notable features are a set of improvements to the directory subsystem.
6225 o Major features (security, Linux):
6226 - When Tor starts as root on Linux and is told to switch user ID, it
6227 can now retain the capability to bind to low ports. By default,
6228 Tor will do this only when it's switching user ID and some low
6229 ports have been configured. You can change this behavior with the
6230 new option KeepBindCapabilities. Closes ticket 8195.
6232 o Major features (directory system):
6233 - When bootstrapping multiple consensus downloads at a time, use the
6234 first one that starts downloading, and close the rest. This
6235 reduces failures when authorities or fallback directories are slow
6236 or down. Together with the code for feature 15775, this feature
6237 should reduces failures due to fallback churn. Implements ticket
6238 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
6239 "mikeperry" and "teor".
6240 - Include a trial list of 21 default fallback directories, generated
6241 in January 2016, based on an opt-in survey of suitable relays.
6242 Doing this should make clients bootstrap more quickly and reliably,
6243 and reduce the load on the directory authorities. Closes ticket
6244 15775. Patch by "teor".
6245 Candidates identified using an OnionOO script by "weasel", "teor",
6246 "gsathya", and "karsten".
6247 - Previously only relays that explicitly opened a directory port
6248 (DirPort) accepted directory requests from clients. Now all
6249 relays, with and without a DirPort, accept and serve tunneled
6250 directory requests that they receive through their ORPort. You can
6251 disable this behavior using the new DirCache option. Closes
6254 o Major key updates:
6255 - Update the V3 identity key for the dannenberg directory authority:
6256 it was changed on 18 November 2015. Closes task 17906. Patch
6259 o Minor features (security, clock):
6260 - Warn when the system clock appears to move back in time (when the
6261 state file was last written in the future). Tor doesn't know that
6262 consensuses have expired if the clock is in the past. Patch by
6263 "teor". Implements ticket 17188.
6265 o Minor features (security, exit policies):
6266 - ExitPolicyRejectPrivate now rejects more private addresses by
6267 default. Specifically, it now rejects the relay's outbound bind
6268 addresses (if configured), and the relay's configured port
6269 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
6270 0.2.0.11-alpha. Patch by "teor".
6272 o Minor features (security, memory erasure):
6273 - Set the unused entries in a smartlist to NULL. This helped catch
6274 a (harmless) bug, and shouldn't affect performance too much.
6275 Implements ticket 17026.
6276 - Use SecureMemoryWipe() function to securely clean memory on
6277 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
6278 Implements feature 17986.
6279 - Use explicit_bzero or memset_s when present. Previously, we'd use
6280 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
6281 from <logan@hackers.mu> and <selven@hackers.mu>.
6282 - Make memwipe() do nothing when passed a NULL pointer or buffer of
6283 zero size. Check size argument to memwipe() for underflow. Fixes
6284 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
6287 o Minor features (security, RNG):
6288 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
6289 positively are not allowed to fail. Previously we depended on
6290 internal details of OpenSSL's behavior. Closes ticket 17686.
6291 - Never use the system entropy output directly for anything besides
6292 seeding the PRNG. When we want to generate important keys, instead
6293 of using system entropy directly, we now hash it with the PRNG
6294 stream. This may help resist certain attacks based on broken OS
6295 entropy implementations. Closes part of ticket 17694.
6296 - Use modern system calls (like getentropy() or getrandom()) to
6297 generate strong entropy on platforms that have them. Closes
6300 o Minor features (accounting):
6301 - Added two modes to the AccountingRule option: One for limiting
6302 only the number of bytes sent ("AccountingRule out"), and one for
6303 limiting only the number of bytes received ("AccountingRule in").
6304 Closes ticket 15989; patch from "unixninja92".
6306 o Minor features (build):
6307 - Since our build process now uses "make distcheck", we no longer
6308 force "make dist" to depend on "make check". Closes ticket 17893;
6309 patch from "cypherpunks."
6310 - Tor now builds successfully with the recent OpenSSL 1.1
6311 development branch, and with the latest LibreSSL. Closes tickets
6312 17549, 17921, and 17984.
6314 o Minor features (controller):
6315 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
6316 tickets 16774 and 17817. Patch by George Tankersley.
6317 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
6318 service descriptor from a service's local hidden service
6319 descriptor cache. Closes ticket 14846.
6320 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
6321 controllers can examine the the reject rules added by
6322 ExitPolicyRejectPrivate. This makes it easier for stem to display
6325 o Minor features (crypto):
6326 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
6328 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
6329 - When allocating a digest state object, allocate no more space than
6330 we actually need. Previously, we would allocate as much space as
6331 the state for the largest algorithm would need. This change saves
6332 up to 672 bytes per circuit. Closes ticket 17796.
6333 - Improve performance when hashing non-multiple of 8 sized buffers,
6334 based on Andrew Moon's public domain SipHash-2-4 implementation.
6335 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
6337 o Minor features (directory downloads):
6338 - Wait for busy authorities and fallback directories to become non-
6339 busy when bootstrapping. (A similar change was made in 6c443e987d
6340 for directory caches chosen from the consensus.) Closes ticket
6341 17864; patch by "teor".
6342 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
6343 directory mirrors. The default is 1; set it to 0 to disable
6344 fallbacks. Implements ticket 17576. Patch by "teor".
6346 o Minor features (geoip):
6347 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
6350 o Minor features (IPv6):
6351 - Add an argument 'ipv6=address:orport' to the DirAuthority and
6352 FallbackDir torrc options, to specify an IPv6 address for an
6353 authority or fallback directory. Add hard-coded ipv6 addresses for
6354 directory authorities that have them. Closes ticket 17327; patch
6355 from Nick Mathewson and "teor".
6356 - Add address policy assume_action support for IPv6 addresses.
6357 - Limit IPv6 mask bits to 128.
6358 - Warn when comparing against an AF_UNSPEC address in a policy, it's
6359 almost always a bug. Closes ticket 17863; patch by "teor".
6360 - Allow users to configure directory authorities and fallback
6361 directory servers with IPv6 addresses and ORPorts. Resolves
6363 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
6364 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
6365 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
6366 17638; bugfix on 0.0.2pre8. Patch by "teor".
6368 o Minor features (logging):
6369 - When logging to syslog, allow a tag to be added to the syslog
6370 identity (the string prepended to every log message). The tag can
6371 be configured with SyslogIdentityTag and defaults to none. Setting
6372 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
6375 o Minor features (portability):
6376 - Use timingsafe_memcmp() where available. Closes ticket 17944;
6377 patch from <logan@hackers.mu>.
6379 o Minor features (relay, address discovery):
6380 - Add a family argument to get_interface_addresses_raw() and
6381 subfunctions to make network interface address interogation more
6382 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
6383 types of interfaces from the operating system. Resolves
6385 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
6386 fails to enumerate interface addresses using the platform-specific
6387 API, have it rely on the UDP socket fallback technique to try and
6388 find out what IP addresses (both IPv4 and IPv6) our machine has.
6389 Resolves ticket 17951.
6391 o Minor features (replay cache):
6392 - The replay cache now uses SHA256 instead of SHA1. Implements
6393 feature 8961. Patch by "teor", issue reported by "rransom".
6395 o Minor features (unix file permissions):
6396 - Defer creation of Unix sockets until after setuid. This avoids
6397 needing CAP_CHOWN and CAP_FOWNER when using systemd's
6398 CapabilityBoundingSet, or chown and fowner when using SELinux.
6399 Implements part of ticket 17562. Patch from Jamie Nguyen.
6400 - If any directory created by Tor is marked as group readable, the
6401 filesystem group is allowed to be either the default GID or the
6402 root user. Allowing root to read the DataDirectory prevents the
6403 need for CAP_READ_SEARCH when using systemd's
6404 CapabilityBoundingSet, or dac_read_search when using SELinux.
6405 Implements part of ticket 17562. Patch from Jamie Nguyen.
6406 - Introduce a new DataDirectoryGroupReadable option. If it is set to
6407 1, the DataDirectory will be made readable by the default GID.
6408 Implements part of ticket 17562. Patch from Jamie Nguyen.
6410 o Minor bugfixes (accounting):
6411 - The max bandwidth when using 'AccountRule sum' is now correctly
6412 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
6415 o Minor bugfixes (code correctness):
6416 - When closing an entry connection, generate a warning if we should
6417 have sent an end cell for it but we haven't. Fixes bug 17876;
6418 bugfix on 0.2.3.2-alpha.
6419 - Assert that allocated memory held by the reputation code is freed
6420 according to its internal counters. Fixes bug 17753; bugfix
6422 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
6425 o Minor bugfixes (compilation):
6426 - Mark all object files that include micro-revision.i as depending
6427 on it, so as to make parallel builds more reliable. Fixes bug
6428 17826; bugfix on 0.2.5.1-alpha.
6429 - Don't try to use the pthread_condattr_setclock() function unless
6430 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
6431 17819; bugfix on 0.2.6.3-alpha.
6432 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
6434 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
6435 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
6436 - Fix search for libevent libraries on OpenBSD (and other systems
6437 that install libevent 1 and libevent 2 in parallel). Fixes bug
6438 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
6439 - Isolate environment variables meant for tests from the rest of the
6440 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
6441 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
6443 - Remove config.log only from make distclean, not from make clean.
6444 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
6446 o Minor bugfixes (crypto):
6447 - Check the return value of HMAC() and assert on failure. Fixes bug
6448 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
6450 o Minor bugfixes (fallback directories):
6451 - Mark fallbacks as "too busy" when they return a 503 response,
6452 rather than just marking authorities. Fixes bug 17572; bugfix on
6453 0.2.4.7-alpha. Patch by "teor".
6455 o Minor bugfixes (IPv6):
6456 - Update the limits in max_dl_per_request for IPv6 address length.
6457 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
6459 o Minor bugfixes (linux seccomp2 sandbox):
6460 - Fix a crash when using offline master ed25519 keys with the Linux
6461 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
6463 o Minor bugfixes (logging):
6464 - In log messages that include a function name, use __FUNCTION__
6465 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
6466 with clang __PRETTY_FUNCTION__ has extra information we don't
6467 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
6469 - Remove needless quotes from a log message about unparseable
6470 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
6472 o Minor bugfixes (portability):
6473 - Remove an #endif from configure.ac so that we correctly detect the
6474 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
6477 o Minor bugfixes (relays):
6478 - Check that both the ORPort and DirPort (if present) are reachable
6479 before publishing a relay descriptor. Otherwise, relays publish a
6480 descriptor with DirPort 0 when the DirPort reachability test takes
6481 longer than the ORPort reachability test. Fixes bug 18050; bugfix
6482 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
6484 o Minor bugfixes (relays, hidden services):
6485 - Refuse connection requests to private OR addresses unless
6486 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
6487 then refuse to send any cells to a private address. Fixes bugs
6488 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
6490 o Minor bugfixes (safe logging):
6491 - When logging a malformed hostname received through socks4, scrub
6492 it if SafeLogging says we should. Fixes bug 17419; bugfix
6495 o Minor bugfixes (statistics code):
6496 - Consistently check for overflow in round_*_to_next_multiple_of
6497 functions, and add unit tests with additional and maximal values.
6498 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
6499 - Handle edge cases in the laplace functions: avoid division by
6500 zero, avoid taking the log of zero, and silence clang type
6501 conversion warnings using round and trunc. Add unit tests for edge
6502 cases with maximal values. Fixes part of bug 13192; bugfix
6505 o Minor bugfixes (testing):
6506 - The test for log_heartbeat was incorrectly failing in timezones
6507 with non-integer offsets. Instead of comparing the end of the time
6508 string against a constant, compare it to the output of
6509 format_local_iso_time when given the correct input. Fixes bug
6510 18039; bugfix on 0.2.5.4-alpha.
6511 - Make unit tests pass on IPv6-only systems, and systems without
6512 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
6513 bugfix on 0.2.7.3-rc. Patch by "teor".
6514 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
6516 - Check the full results of SHA256 and SHA512 digests in the unit
6517 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
6519 o Code simplification and refactoring:
6520 - Move logging of redundant policy entries in
6521 policies_parse_exit_policy_internal into its own function. Closes
6522 ticket 17608; patch from "juce".
6523 - Extract the more complicated parts of circuit_mark_for_close()
6524 into a new function that we run periodically before circuits are
6525 freed. This change removes more than half of the functions
6526 currently in the "blob". Closes ticket 17218.
6527 - Clean up a little duplicated code in
6528 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
6530 - Decouple the list of streams waiting to be attached to circuits
6531 from the overall connection list. This change makes it possible to
6532 attach streams quickly while simplifying Tor's callgraph and
6533 avoiding O(N) scans of the entire connection list. Closes
6535 - When a direct directory request fails immediately on launch,
6536 instead of relaunching that request from inside the code that
6537 launches it, instead mark the connection for teardown. This change
6538 simplifies Tor's callback and prevents the directory-request
6539 launching code from invoking itself recursively. Closes
6541 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
6542 use them. Closes ticket 17926.
6545 - Add a description of the correct use of the '--keygen' command-
6546 line option. Closes ticket 17583; based on text by 's7r'.
6547 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
6548 - Explain actual minima for BandwidthRate. Closes ticket 16382.
6549 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
6550 - Mention torspec URL in the manpage and point the reader to it
6551 whenever we mention a document that belongs in torspce. Fixes
6555 - Remove client-side support for connecting to Tor relays running
6556 versions of Tor before 0.2.3.6-alpha. These relays didn't support
6557 the v3 TLS handshake protocol, and are no longer allowed on the
6558 Tor network. Implements the client side of ticket 11150. Based on
6559 patches by Tom van der Woerdt.
6562 - Add unit tests to check for common RNG failure modes, such as
6563 returning all zeroes, identical values, or incrementing values
6564 (OpenSSL's rand_predictable feature). Patch by "teor".
6565 - Log more information when the backtrace tests fail. Closes ticket
6566 17892. Patch from "cypherpunks."
6567 - Always test both ed25519 backends, so that we can be sure that our
6568 batch-open replacement code works. Part of ticket 16794.
6569 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
6570 portion of ticket 16831.
6571 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
6572 util_format.c, directory.c, and options_validate.c. Closes tickets
6573 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
6575 - Unit tests for directory_handle_command_get. Closes ticket 17004.
6576 Patch from Reinaldo de Souza Jr.
6579 Changes in version 0.2.7.6 - 2015-12-10
6580 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
6581 well as a minor bug in hidden service reliability.
6583 o Major bugfixes (guard selection):
6584 - Actually look at the Guard flag when selecting a new directory
6585 guard. When we implemented the directory guard design, we
6586 accidentally started treating all relays as if they have the Guard
6587 flag during guard selection, leading to weaker anonymity and worse
6588 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
6591 o Minor features (geoip):
6592 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
6595 o Minor bugfixes (compilation):
6596 - When checking for net/pfvar.h, include netinet/in.h if possible.
6597 This fixes transparent proxy detection on OpenBSD. Fixes bug
6598 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
6599 - Fix a compilation warning with Clang 3.6: Do not check the
6600 presence of an address which can never be NULL. Fixes bug 17781.
6602 o Minor bugfixes (correctness):
6603 - When displaying an IPv6 exit policy, include the mask bits
6604 correctly even when the number is greater than 31. Fixes bug
6605 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
6606 - The wrong list was used when looking up expired intro points in a
6607 rend service object, causing what we think could be reachability
6608 issues for hidden services, and triggering a BUG log. Fixes bug
6609 16702; bugfix on 0.2.7.2-alpha.
6610 - Fix undefined behavior in the tor_cert_checksig function. Fixes
6611 bug 17722; bugfix on 0.2.7.2-alpha.
6614 Changes in version 0.2.7.5 - 2015-11-20
6615 The Tor 0.2.7 release series is dedicated to the memory of Tor user
6616 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
6617 tirelessly to advocate human rights regardless of national borders,
6618 and oppose the encroachments of mass surveillance. He opposed national
6619 exceptionalism, he brought clarity to legal and policy debates, he
6620 understood and predicted the impact of mass surveillance on the world,
6621 and he laid the groundwork for resisting it. While serving on the Tor
6622 Project's board of directors, he brought us his uncompromising focus
6623 on technical excellence in the service of humankind. Caspar was an
6624 inimitable force for good and a wonderful friend. He was kind,
6625 humorous, generous, gallant, and believed we should protect one
6626 another without exception. We honor him here for his ideals, his
6627 efforts, and his accomplishments. Please honor his memory with works
6628 that would make him proud.
6630 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
6632 The 0.2.7 series adds a more secure identity key type for relays,
6633 improves cryptography performance, resolves several longstanding
6634 hidden-service performance issues, improves controller support for
6635 hidden services, and includes small bugfixes and performance
6636 improvements throughout the program. This release series also includes
6637 more tests than before, and significant simplifications to which parts
6638 of Tor invoke which others.
6640 (This release contains no code changes since 0.2.7.4-rc.)
6643 Changes in version 0.2.7.4-rc - 2015-10-21
6644 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
6645 fixes some important memory leaks, and a scary-looking (but mostly
6646 harmless in practice) invalid-read bug. It also has a few small
6647 bugfixes, notably fixes for compilation and portability on different
6648 platforms. If no further significant bounds are found, the next
6649 release will the the official stable release.
6651 o Major bugfixes (security, correctness):
6652 - Fix an error that could cause us to read 4 bytes before the
6653 beginning of an openssl string. This bug could be used to cause
6654 Tor to crash on systems with unusual malloc implementations, or
6655 systems with unusual hardening installed. Fixes bug 17404; bugfix
6658 o Major bugfixes (correctness):
6659 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
6660 bug 17401; bugfix on 0.2.7.3-rc.
6662 o Major bugfixes (memory leaks):
6663 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
6664 17398; bugfix on 0.2.6.1-alpha.
6665 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
6666 17402; bugfix on 0.2.7.3-rc.
6667 - Fix a memory leak when reading an expired signing key from disk.
6668 Fixes bug 17403; bugfix on 0.2.7.2-rc.
6670 o Minor features (geoIP):
6671 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
6674 o Minor bugfixes (compilation):
6675 - Repair compilation with the most recent (unreleased, alpha)
6676 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
6677 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
6678 17251; bugfix on 0.2.7.2-alpha.
6679 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
6680 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
6682 o Minor bugfixes (portability):
6683 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
6684 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
6687 o Minor bugfixes (sandbox):
6688 - Add the "hidserv-stats" filename to our sandbox filter for the
6689 HiddenServiceStatistics option to work properly. Fixes bug 17354;
6690 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
6692 o Minor bugfixes (testing):
6693 - Add unit tests for get_interface_address* failure cases. Fixes bug
6694 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
6695 - Fix breakage when running 'make check' with BSD make. Fixes bug
6696 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
6697 - Make the get_ifaddrs_* unit tests more tolerant of different
6698 network configurations. (Don't assume every test box has an IPv4
6699 address, and don't assume every test box has a non-localhost
6700 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
6701 - Skip backtrace tests when backtrace support is not compiled in.
6702 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
6706 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
6707 - Note that HiddenServicePorts can take a unix domain socket. Closes
6711 Changes in version 0.2.7.3-rc - 2015-09-25
6712 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
6713 contains numerous usability fixes for Ed25519 keys, safeguards against
6714 several misconfiguration problems, significant simplifications to
6715 Tor's callgraph, and numerous bugfixes and small features.
6717 This is the most tested release of Tor to date. The unit tests cover
6718 39.40% of the code, and the integration tests (accessible with "make
6719 test-full-online", requiring stem and chutney and a network
6720 connection) raise the coverage to 64.49%.
6722 o Major features (security, hidden services):
6723 - Hidden services, if using the EntryNodes option, are required to
6724 use more than one EntryNode, in order to avoid a guard discovery
6725 attack. (This would only affect people who had configured hidden
6726 services and manually specified the EntryNodes option with a
6727 single entry-node. The impact was that it would be easy to
6728 remotely identify the guard node used by such a hidden service.
6729 See ticket for more information.) Fixes ticket 14917.
6731 o Major features (Ed25519 keys, keypinning):
6732 - The key-pinning option on directory authorities is now advisory-
6733 only by default. In a future version, or when the AuthDirPinKeys
6734 option is set, pins are enforced again. Disabling key-pinning
6735 seemed like a good idea so that we can survive the fallout of any
6736 usability problems associated with Ed25519 keys. Closes
6739 o Major features (Ed25519 performance):
6740 - Improve the speed of Ed25519 operations and Curve25519 keypair
6741 generation when built targeting 32 bit x86 platforms with SSE2
6742 available. Implements ticket 16535.
6743 - Improve the runtime speed of Ed25519 signature verification by
6744 using Ed25519-donna's batch verification support. Implements
6747 o Major features (performance testing):
6748 - The test-network.sh script now supports performance testing.
6749 Requires corresponding chutney performance testing changes. Patch
6750 by "teor". Closes ticket 14175.
6752 o Major features (relay, Ed25519):
6753 - Significant usability improvements for Ed25519 key management. Log
6754 messages are better, and the code can recover from far more
6755 failure conditions. Thanks to "s7r" for reporting and diagnosing
6757 - Add a new OfflineMasterKey option to tell Tor never to try loading
6758 or generating a secret Ed25519 identity key. You can use this in
6759 combination with tor --keygen to manage offline and/or encrypted
6760 Ed25519 keys. Implements ticket 16944.
6761 - Add a --newpass option to allow changing or removing the
6762 passphrase of an encrypted key with tor --keygen. Implements part
6764 - On receiving a HUP signal, check to see whether the Ed25519
6765 signing key has changed, and reload it if so. Closes ticket 16790.
6767 o Major bugfixes (relay, Ed25519):
6768 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
6769 0.2.7.2-alpha. Reported by "s7r".
6770 - Improve handling of expired signing keys with offline master keys.
6771 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
6773 o Minor features (client-side privacy):
6774 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
6775 lifespan when IsolateSOCKSAuth and streams with SOCKS
6776 authentication are attached to the circuit. This allows
6777 applications like TorBrowser to manage circuit lifetime on their
6778 own. Implements feature 15482.
6779 - When logging malformed hostnames from SOCKS5 requests, respect
6780 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
6782 o Minor features (compilation):
6783 - Give a warning as early as possible when trying to build with an
6784 unsupported OpenSSL version. Closes ticket 16901.
6785 - Fail during configure if we're trying to build against an OpenSSL
6786 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
6787 which started requiring ECC.
6789 o Minor features (geoip):
6790 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
6793 o Minor features (hidden services):
6794 - Relays need to have the Fast flag to get the HSDir flag. As this
6795 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
6796 drop. This change should make some attacks against the hidden
6797 service directory system harder. Fixes ticket 15963.
6798 - Turn on hidden service statistics collection by setting the torrc
6799 option HiddenServiceStatistics to "1" by default. (This keeps
6800 track only of the fraction of traffic used by hidden services, and
6801 the total number of hidden services in existence.) Closes
6803 - Client now uses an introduction point failure cache to know when
6804 to fetch or keep a descriptor in their cache. Previously, failures
6805 were recorded implicitly, but not explicitly remembered. Closes
6808 o Minor features (testing, authorities, documentation):
6809 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
6810 explicitly manage consensus flags in testing networks. Patch by
6811 "robgjansen", modified by "teor". Implements part of ticket 14882.
6813 o Minor bugfixes (security, exit policies):
6814 - ExitPolicyRejectPrivate now also rejects the relay's published
6815 IPv6 address (if any), and any publicly routable IPv4 or IPv6
6816 addresses on any local interfaces. ticket 17027. Patch by "teor".
6817 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
6819 o Minor bug fixes (torrc exit policies):
6820 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
6821 produce IPv6 wildcard addresses. Previously they would produce
6822 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
6823 of bug 16069; bugfix on 0.2.4.7-alpha.
6824 - When parsing torrc ExitPolicies, we now warn for a number of cases
6825 where the user's intent is likely to differ from Tor's actual
6826 behavior. These include: using an IPv4 address with an accept6 or
6827 reject6 line; using "private" on an accept6 or reject6 line; and
6828 including any ExitPolicy lines after accept *:* or reject *:*.
6829 Related to ticket 16069.
6830 - When parsing torrc ExitPolicies, we now issue an info-level
6831 message when expanding an "accept/reject *" line to include both
6832 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
6833 - In each instance above, usage advice is provided to avoid the
6834 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
6835 16069; bugfix on 0.2.4.7-alpha.
6837 o Minor bugfixes (authority):
6838 - Don't assign "HSDir" to a router if it isn't Valid and Running.
6839 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
6840 - Downgrade log messages about Ed25519 key issues if they are in old
6841 cached router descriptors. Fixes part of bug 16286; bugfix
6843 - When we find an Ed25519 key issue in a cached descriptor, stop
6844 saying the descriptor was just "uploaded". Fixes another part of
6845 bug 16286; bugfix on 0.2.7.2-alpha.
6847 o Minor bugfixes (control port):
6848 - Repair a warning and a spurious result when getting the maximum
6849 number of file descriptors from the controller. Fixes bug 16697;
6850 bugfix on 0.2.7.2-alpha.
6852 o Minor bugfixes (correctness):
6853 - When calling channel_free_list(), avoid calling smartlist_remove()
6854 while inside a FOREACH loop. This partially reverts commit
6855 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
6856 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
6858 o Minor bugfixes (documentation):
6859 - Advise users on how to configure separate IPv4 and IPv6 exit
6860 policies in the manpage and sample torrcs. Related to ticket 16069.
6861 - Fix the usage message of tor-resolve(1) so that it no longer lists
6862 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
6863 - Fix an error in the manual page and comments for
6864 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
6865 required "ORPort connectivity". While this is true, it is in no
6866 way unique to the HSDir flag. Of all the flags, only HSDirs need a
6867 DirPort configured in order for the authorities to assign that
6868 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
6871 o Minor bugfixes (Ed25519):
6872 - Fix a memory leak when reading router descriptors with expired
6873 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
6875 o Minor bugfixes (linux seccomp2 sandbox):
6876 - Allow bridge authorities to run correctly under the seccomp2
6877 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
6878 - Allow routers with ed25519 keys to run correctly under the
6879 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
6881 o Minor bugfixes (open file limit):
6882 - Fix set_max_file_descriptors() to set by default the max open file
6883 limit to the current limit when setrlimit() fails. Fixes bug
6884 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
6886 o Minor bugfixes (portability):
6887 - Try harder to normalize the exit status of the Tor process to the
6888 standard-provided range. Fixes bug 16975; bugfix on every version
6890 - Check correctly for Windows socket errors in the workqueue
6891 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
6892 - Fix the behavior of crypto_rand_time_range() when told to consider
6893 times before 1970. (These times were possible when running in a
6894 simulated network environment where time()'s output starts at
6895 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
6896 - Restore correct operation of TLS client-cipher detection on
6897 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
6899 o Minor bugfixes (relay):
6900 - Ensure that worker threads actually exit when a fatal error or
6901 shutdown is indicated. This fix doesn't currently affect the
6902 behavior of Tor, because Tor workers never indicates fatal error
6903 or shutdown except in the unit tests. Fixes bug 16868; bugfix
6905 - Unblock threads before releasing the work queue mutex to ensure
6906 predictable scheduling behavior. Fixes bug 16644; bugfix
6909 o Code simplification and refactoring:
6910 - Change the function that's called when we need to retry all
6911 downloads so that it only reschedules the downloads to happen
6912 immediately, rather than launching them all at once itself. This
6913 further simplifies Tor's callgraph.
6914 - Move some format-parsing functions out of crypto.c and
6915 crypto_curve25519.c into crypto_format.c and/or util_format.c.
6916 - Move the client-only parts of init_keys() into a separate
6917 function. Closes ticket 16763.
6918 - Simplify the microdesc_free() implementation so that it no longer
6919 appears (to code analysis tools) to potentially invoke a huge
6920 suite of other microdesc functions.
6921 - Simply the control graph further by deferring the inner body of
6922 directory_all_unreachable() into a callback. Closes ticket 16762.
6923 - Treat the loss of an owning controller as equivalent to a SIGTERM
6924 signal. This removes a tiny amount of duplicated code, and
6925 simplifies our callgraph. Closes ticket 16788.
6926 - When generating an event to send to the controller, we no longer
6927 put the event over the network immediately. Instead, we queue
6928 these events, and use a Libevent callback to deliver them. This
6929 change simplifies Tor's callgraph by reducing the number of
6930 functions from which all other Tor functions are reachable. Closes
6932 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
6933 that try to scan or compile every file on Unix won't decide that
6935 - Remove the unused "nulterminate" argument from buf_pullup().
6938 - Recommend a 40 GB example AccountingMax in torrc.sample rather
6939 than a 4 GB max. Closes ticket 16742.
6940 - Include the TUNING document in our source tarball. It is referred
6941 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
6945 - The internal pure-C tor-fw-helper tool is now removed from the Tor
6946 distribution, in favor of the pure-Go clone available from
6947 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
6948 used by the C tor-fw-helper are not, in our opinion, very
6949 confidence- inspiring in their secure-programming techniques.
6950 Closes ticket 13338.
6951 - Remove the code that would try to aggressively flush controller
6952 connections while writing to them. This code was introduced in
6953 0.1.2.7-alpha, in order to keep output buffers from exceeding
6954 their limits. But there is no longer a maximum output buffer size,
6955 and flushing data in this way caused some undesirable recursions
6956 in our call graph. Closes ticket 16480.
6959 - Make "bridges+hs" the default test network. This tests almost all
6960 tor functionality during make test-network, while allowing tests
6961 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
6962 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
6963 (chutney). Patches by "teor".
6964 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
6965 by-side in the same parent directory. Closes ticket 16903. Patch
6967 - Use environment variables rather than autoconf substitutions to
6968 send variables from the build system to the test scripts. This
6969 change should be easier to maintain, and cause 'make distcheck' to
6970 work better than before. Fixes bug 17148.
6971 - Add a new set of callgraph analysis scripts that use clang to
6972 produce a list of which Tor functions are reachable from which
6973 other Tor functions. We're planning to use these to help simplify
6974 our code structure by identifying illogical dependencies.
6975 - Add new 'test-full' and 'test-full-online' targets to run all
6976 tests, including integration tests with stem and chutney.
6977 - Make the test-workqueue test work on Windows by initializing the
6978 network before we begin.
6979 - New make target (make test-network-all) to run multiple applicable
6980 chutney test cases. Patch from Teor; closes 16953.
6981 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
6982 functions in dns.c. Implements a portion of ticket 16831.
6983 - When building Tor with testing coverage enabled, run Chutney tests
6984 (if any) using the 'tor-cov' coverage binary.
6985 - When running test-network or test-stem, check for the absence of
6986 stem/chutney before doing any build operations.
6989 Changes in version 0.2.7.2-alpha - 2015-07-27
6990 This, the second alpha in the Tor 0.2.7 series, has a number of new
6991 features, including a way to manually pick the number of introduction
6992 points for hidden services, and the much stronger Ed25519 signing key
6993 algorithm for regular Tor relays (including support for encrypted
6994 offline identity keys in the new algorithm).
6996 Support for Ed25519 on relays is currently limited to signing router
6997 descriptors; later alphas in this series will extend Ed25519 key
6998 support to more parts of the Tor protocol.
7000 o Major features (Ed25519 identity keys, Proposal 220):
7001 - All relays now maintain a stronger identity key, using the Ed25519
7002 elliptic curve signature format. This master key is designed so
7003 that it can be kept offline. Relays also generate an online
7004 signing key, and a set of other Ed25519 keys and certificates.
7005 These are all automatically regenerated and rotated as needed.
7006 Implements part of ticket 12498.
7007 - Directory authorities now vote on Ed25519 identity keys along with
7008 RSA1024 keys. Implements part of ticket 12498.
7009 - Directory authorities track which Ed25519 identity keys have been
7010 used with which RSA1024 identity keys, and do not allow them to
7011 vary freely. Implements part of ticket 12498.
7012 - Microdescriptors now include Ed25519 identity keys. Implements
7013 part of ticket 12498.
7014 - Add support for offline encrypted Ed25519 master keys. To use this
7015 feature on your tor relay, run "tor --keygen" to make a new master
7016 key (or to make a new signing key if you already have a master
7017 key). Closes ticket 13642.
7019 o Major features (Hidden services):
7020 - Add the torrc option HiddenServiceNumIntroductionPoints, to
7021 specify a fixed number of introduction points. Its maximum value
7022 is 10 and default is 3. Using this option can increase a hidden
7023 service's reliability under load, at the cost of making it more
7024 visible that the hidden service is facing extra load. Closes
7026 - Remove the adaptive algorithm for choosing the number of
7027 introduction points, which used to change the number of
7028 introduction points (poorly) depending on the number of
7029 connections the HS sees. Closes ticket 4862.
7031 o Major features (onion key cross-certification):
7032 - Relay descriptors now include signatures of their own identity
7033 keys, made using the TAP and ntor onion keys. These signatures
7034 allow relays to prove ownership of their own onion keys. Because
7035 of this change, microdescriptors will no longer need to include
7036 RSA identity keys. Implements proposal 228; closes ticket 12499.
7038 o Major features (performance):
7039 - Improve the runtime speed of Ed25519 operations by using the
7040 public-domain Ed25519-donna by Andrew M. ("floodyberry").
7041 Implements ticket 16467.
7042 - Improve the runtime speed of the ntor handshake by using an
7043 optimized curve25519 basepoint scalarmult implementation from the
7044 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
7045 ideas by Adam Langley. Implements ticket 9663.
7047 o Major bugfixes (client-side privacy, also in 0.2.6.9):
7048 - Properly separate out each SOCKSPort when applying stream
7049 isolation. The error occurred because each port's session group
7050 was being overwritten by a default value when the listener
7051 connection was initialized. Fixes bug 16247; bugfix on
7052 0.2.6.3-alpha. Patch by "jojelino".
7054 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
7055 - Stop refusing to store updated hidden service descriptors on a
7056 client. This reverts commit 9407040c59218 (which indeed fixed bug
7057 14219, but introduced a major hidden service reachability
7058 regression detailed in bug 16381). This is a temporary fix since
7059 we can live with the minor issue in bug 14219 (it just results in
7060 some load on the network) but the regression of 16381 is too much
7061 of a setback. First-round fix for bug 16381; bugfix
7064 o Major bugfixes (hidden services):
7065 - When cannibalizing a circuit for an introduction point, always
7066 extend to the chosen exit node (creating a 4 hop circuit).
7067 Previously Tor would use the current circuit exit node, which
7068 changed the original choice of introduction point, and could cause
7069 the hidden service to skip excluded introduction points or
7070 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
7073 o Major bugfixes (open file limit):
7074 - The open file limit wasn't checked before calling
7075 tor_accept_socket_nonblocking(), which would make Tor exceed the
7076 limit. Now, before opening a new socket, Tor validates the open
7077 file limit just before, and if the max has been reached, return an
7078 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
7080 o Major bugfixes (stability, also in 0.2.6.10):
7081 - Stop crashing with an assertion failure when parsing certain kinds
7082 of malformed or truncated microdescriptors. Fixes bug 16400;
7083 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7084 by "cypherpunks_backup".
7085 - Stop random client-side assertion failures that could occur when
7086 connecting to a busy hidden service, or connecting to a hidden
7087 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7090 o Minor features (directory authorities, security, also in 0.2.6.9):
7091 - The HSDir flag given by authorities now requires the Stable flag.
7092 For the current network, this results in going from 2887 to 2806
7093 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7094 attack by raising the effort for a relay to become Stable to
7095 require at the very least 7 days, while maintaining the 96 hours
7096 uptime requirement for HSDir. Implements ticket 8243.
7098 o Minor features (client):
7099 - Relax the validation of hostnames in SOCKS5 requests, allowing the
7100 character '_' to appear, in order to cope with domains observed in
7101 the wild that are serving non-RFC compliant records. Resolves
7103 - Relax the validation done to hostnames in SOCKS5 requests, and
7104 allow a single trailing '.' to cope with clients that pass FQDNs
7105 using that syntax to explicitly indicate that the domain name is
7106 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
7107 - Add GroupWritable and WorldWritable options to unix-socket based
7108 SocksPort and ControlPort options. These options apply to a single
7109 socket, and override {Control,Socks}SocketsGroupWritable. Closes
7112 o Minor features (control protocol):
7113 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
7114 the control protocol. Resolves ticket 15358.
7116 o Minor features (directory authorities):
7117 - Directory authorities no longer vote against the "Fast", "Stable",
7118 and "HSDir" flags just because they were going to vote against
7119 "Running": if the consensus turns out to be that the router was
7120 running, then the authority's vote should count. Patch from Peter
7121 Retzlaff; closes issue 8712.
7123 o Minor features (geoip, also in 0.2.6.10):
7124 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
7125 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
7127 o Minor features (hidden services):
7128 - Add the new options "HiddenServiceMaxStreams" and
7129 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
7130 limit the maximum number of simultaneous streams per circuit, and
7131 optionally tear down the circuit when the limit is exceeded. Part
7134 o Minor features (portability):
7135 - Use C99 variadic macros when the compiler is not GCC. This avoids
7136 failing compilations on MSVC, and fixes a log-file-based race
7137 condition in our old workarounds. Original patch from Gisle Vanem.
7139 o Minor bugfixes (compilation, also in 0.2.6.9):
7140 - Build with --enable-systemd correctly when libsystemd is
7141 installed, but systemd is not. Fixes bug 16164; bugfix on
7142 0.2.6.3-alpha. Patch from Peter Palfrader.
7144 o Minor bugfixes (controller):
7145 - Add the descriptor ID in each HS_DESC control event. It was
7146 missing, but specified in control-spec.txt. Fixes bug 15881;
7147 bugfix on 0.2.5.2-alpha.
7149 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
7150 - Check for failures from crypto_early_init, and refuse to continue.
7151 A previous typo meant that we could keep going with an
7152 uninitialized crypto library, and would have OpenSSL initialize
7153 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7154 when implementing ticket 4900. Patch by "teor".
7156 o Minor bugfixes (hidden services):
7157 - Fix a crash when reloading configuration while at least one
7158 configured and one ephemeral hidden service exists. Fixes bug
7159 16060; bugfix on 0.2.7.1-alpha.
7160 - Avoid crashing with a double-free bug when we create an ephemeral
7161 hidden service but adding it fails for some reason. Fixes bug
7162 16228; bugfix on 0.2.7.1-alpha.
7164 o Minor bugfixes (Linux seccomp2 sandbox):
7165 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
7166 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
7168 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
7169 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7170 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7171 on 0.2.6.3-alpha. Patch from "teor".
7173 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
7174 - Fix sandboxing to work when running as a relay, by allowing the
7175 renaming of secret_id_key, and allowing the eventfd2 and futex
7176 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
7178 - Allow systemd connections to work with the Linux seccomp2 sandbox
7179 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7182 o Minor bugfixes (relay):
7183 - Fix a rarely-encountered memory leak when failing to initialize
7184 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
7187 o Minor bugfixes (systemd):
7188 - Fix an accidental formatting error that broke the systemd
7189 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
7190 - Tor's systemd unit file no longer contains extraneous spaces.
7191 These spaces would sometimes confuse tools like deb-systemd-
7192 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
7194 o Minor bugfixes (tests):
7195 - Use the configured Python executable when running test-stem-full.
7196 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
7198 o Minor bugfixes (tests, also in 0.2.6.9):
7199 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7200 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7202 o Minor bugfixes (threads, comments):
7203 - Always initialize return value in compute_desc_id in rendcommon.c
7204 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
7205 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
7206 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
7207 - Remove undefined directive-in-macro in test_util_writepid clang
7208 3.7 complains that using a preprocessor directive inside a macro
7209 invocation in test_util_writepid in test_util.c is undefined.
7210 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
7212 o Code simplification and refactoring:
7213 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
7214 to ensure they remain consistent and visible everywhere.
7215 - Remove some vestigial workarounds for the MSVC6 compiler. We
7216 haven't supported that in ages.
7217 - The link authentication code has been refactored for better
7218 testability and reliability. It now uses code generated with the
7219 "trunnel" binary encoding generator, to reduce the risk of bugs
7220 due to programmer error. Done as part of ticket 12498.
7223 - Include a specific and (hopefully) accurate documentation of the
7224 torrc file's meta-format in doc/torrc_format.txt. This is mainly
7225 of interest to people writing programs to parse or generate torrc
7226 files. This document is not a commitment to long-term
7227 compatibility; some aspects of the current format are a bit
7228 ridiculous. Closes ticket 2325.
7231 - Tor no longer supports copies of OpenSSL that are missing support
7232 for Elliptic Curve Cryptography. (We began using ECC when
7233 available in 0.2.4.8-alpha, for more safe and efficient key
7234 negotiation.) In particular, support for at least one of P256 or
7235 P224 is now required, with manual configuration needed if only
7236 P224 is available. Resolves ticket 16140.
7237 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
7238 on an operating system that has not upgraded to OpenSSL 1.0 or
7239 later, and you compile Tor from source, you will need to install a
7240 more recent OpenSSL to link Tor against.) These versions of
7241 OpenSSL are still supported by the OpenSSL, but the numerous
7242 cryptographic improvements in later OpenSSL releases makes them a
7243 clear choice. Resolves ticket 16034.
7244 - Remove the HidServDirectoryV2 option. Now all relays offer to
7245 store hidden service descriptors. Related to 16543.
7246 - Remove the VoteOnHidServDirectoriesV2 option, since all
7247 authorities have long set it to 1. Closes ticket 16543.
7250 - Document use of coverity, clang static analyzer, and clang dynamic
7251 undefined behavior and address sanitizers in doc/HACKING. Include
7252 detailed usage instructions in the blacklist. Patch by "teor".
7253 Closes ticket 15817.
7254 - The link authentication protocol code now has extensive tests.
7255 - The relay descriptor signature testing code now has
7257 - The test_workqueue program now runs faster, and is enabled by
7258 default as a part of "make check".
7259 - Now that OpenSSL has its own scrypt implementation, add an unit
7260 test that checks for interoperability between libscrypt_scrypt()
7261 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
7262 and rely on EVP_PBE_scrypt() whenever possible. Resolves
7266 Changes in version 0.2.6.10 - 2015-07-12
7267 Tor version 0.2.6.10 fixes some significant stability and hidden
7268 service client bugs, bulletproofs the cryptography init process, and
7269 fixes a bug when using the sandbox code with some older versions of
7270 Linux. Everyone running an older version, especially an older version
7271 of 0.2.6, should upgrade.
7273 o Major bugfixes (hidden service clients, stability):
7274 - Stop refusing to store updated hidden service descriptors on a
7275 client. This reverts commit 9407040c59218 (which indeed fixed bug
7276 14219, but introduced a major hidden service reachability
7277 regression detailed in bug 16381). This is a temporary fix since
7278 we can live with the minor issue in bug 14219 (it just results in
7279 some load on the network) but the regression of 16381 is too much
7280 of a setback. First-round fix for bug 16381; bugfix
7283 o Major bugfixes (stability):
7284 - Stop crashing with an assertion failure when parsing certain kinds
7285 of malformed or truncated microdescriptors. Fixes bug 16400;
7286 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7287 by "cypherpunks_backup".
7288 - Stop random client-side assertion failures that could occur when
7289 connecting to a busy hidden service, or connecting to a hidden
7290 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7293 o Minor features (geoip):
7294 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
7295 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
7297 o Minor bugfixes (crypto error-handling):
7298 - Check for failures from crypto_early_init, and refuse to continue.
7299 A previous typo meant that we could keep going with an
7300 uninitialized crypto library, and would have OpenSSL initialize
7301 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7302 when implementing ticket 4900. Patch by "teor".
7304 o Minor bugfixes (Linux seccomp2 sandbox):
7305 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7306 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7307 on 0.2.6.3-alpha. Patch from "teor".
7310 Changes in version 0.2.6.9 - 2015-06-11
7311 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
7312 requirements for receiving an HSDir flag, and addresses some other small
7313 bugs in the systemd and sandbox code. Clients using circuit isolation
7314 should upgrade; all directory authorities should upgrade.
7316 o Major bugfixes (client-side privacy):
7317 - Properly separate out each SOCKSPort when applying stream
7318 isolation. The error occurred because each port's session group was
7319 being overwritten by a default value when the listener connection
7320 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
7323 o Minor feature (directory authorities, security):
7324 - The HSDir flag given by authorities now requires the Stable flag.
7325 For the current network, this results in going from 2887 to 2806
7326 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7327 attack by raising the effort for a relay to become Stable which
7328 takes at the very least 7 days to do so and by keeping the 96
7329 hours uptime requirement for HSDir. Implements ticket 8243.
7331 o Minor bugfixes (compilation):
7332 - Build with --enable-systemd correctly when libsystemd is
7333 installed, but systemd is not. Fixes bug 16164; bugfix on
7334 0.2.6.3-alpha. Patch from Peter Palfrader.
7336 o Minor bugfixes (Linux seccomp2 sandbox):
7337 - Fix sandboxing to work when running as a relaymby renaming of
7338 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
7339 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
7340 - Allow systemd connections to work with the Linux seccomp2 sandbox
7341 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7344 o Minor bugfixes (tests):
7345 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7346 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7349 Changes in version 0.2.6.8 - 2015-05-21
7350 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
7351 fixes an authority-side bug in assigning the HSDir flag. All directory
7352 authorities should upgrade.
7354 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
7355 - Revert commit that made directory authorities assign the HSDir
7356 flag to relays without a DirPort; this was bad because such relays
7357 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7360 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7361 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7362 a client authorized hidden service. Fixes bug 15823; bugfix
7365 o Minor features (geoip):
7366 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
7367 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
7371 Changes in version 0.2.7.1-alpha - 2015-05-12
7372 Tor 0.2.7.1-alpha is the first alpha release in its series. It
7373 includes numerous small features and bugfixes against previous Tor
7374 versions, and numerous small infrastructure improvements. The most
7375 notable features are several new ways for controllers to interact with
7376 the hidden services subsystem.
7378 o New system requirements:
7379 - Tor no longer includes workarounds to support Libevent versions
7380 before 1.3e. Libevent 2.0 or later is recommended. Closes
7383 o Major features (controller):
7384 - Add the ADD_ONION and DEL_ONION commands that allow the creation
7385 and management of hidden services via the controller. Closes
7387 - New "GETINFO onions/current" and "GETINFO onions/detached"
7388 commands to get information about hidden services created via the
7389 controller. Part of ticket 6411.
7390 - New HSFETCH command to launch a request for a hidden service
7391 descriptor. Closes ticket 14847.
7392 - New HSPOST command to upload a hidden service descriptor. Closes
7393 ticket 3523. Patch by "DonnchaC".
7395 o Major bugfixes (hidden services):
7396 - Revert commit that made directory authorities assign the HSDir
7397 flag to relays without a DirPort; this was bad because such relays
7398 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7401 o Minor features (clock-jump tolerance):
7402 - Recover better when our clock jumps back many hours, like might
7403 happen for Tails or Whonix users who start with a very wrong
7404 hardware clock, use Tor to discover a more accurate time, and then
7405 fix their clock. Resolves part of ticket 8766.
7407 o Minor features (command-line interface):
7408 - Make --hash-password imply --hush to prevent unnecessary noise.
7409 Closes ticket 15542. Patch from "cypherpunks".
7410 - Print a warning whenever we find a relative file path being used
7411 as torrc option. Resolves issue 14018.
7413 o Minor features (controller):
7414 - Add DirAuthority lines for default directory authorities to the
7415 output of the "GETINFO config/defaults" command if not already
7416 present. Implements ticket 14840.
7417 - Controllers can now use "GETINFO hs/client/desc/id/..." to
7418 retrieve items from the client's hidden service descriptor cache.
7419 Closes ticket 14845.
7420 - Implement a new controller command "GETINFO status/fresh-relay-
7421 descs" to fetch a descriptor/extrainfo pair that was generated on
7422 demand just for the controller's use. Implements ticket 14784.
7424 o Minor features (DoS-resistance):
7425 - Make it harder for attackers to overload hidden services with
7426 introductions, by blocking multiple introduction requests on the
7427 same circuit. Resolves ticket 15515.
7429 o Minor features (geoip):
7430 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
7431 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
7434 o Minor features (HS popularity countermeasure):
7435 - To avoid leaking HS popularity, don't cycle the introduction point
7436 when we've handled a fixed number of INTRODUCE2 cells but instead
7437 cycle it when a random number of introductions is reached, thus
7438 making it more difficult for an attacker to find out the amount of
7439 clients that have used the introduction point for a specific HS.
7440 Closes ticket 15745.
7442 o Minor features (logging):
7443 - Include the Tor version in all LD_BUG log messages, since people
7444 tend to cut and paste those into the bugtracker. Implements
7447 o Minor features (pluggable transports):
7448 - When launching managed pluggable transports on Linux systems,
7449 attempt to have the kernel deliver a SIGTERM on tor exit if the
7450 pluggable transport process is still running. Resolves
7452 - When launching managed pluggable transports, setup a valid open
7453 stdin in the child process that can be used to detect if tor has
7454 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
7455 can be used by implementations to detect this new behavior.
7456 Resolves ticket 15435.
7458 o Minor features (testing):
7459 - Add a test to verify that the compiler does not eliminate our
7460 memwipe() implementation. Closes ticket 15377.
7461 - Add make rule `check-changes` to verify the format of changes
7462 files. Closes ticket 15180.
7463 - Add unit tests for control_event_is_interesting(). Add a compile-
7464 time check that the number of events doesn't exceed the capacity
7465 of control_event_t.event_mask. Closes ticket 15431, checks for
7466 bugs similar to 13085. Patch by "teor".
7467 - Command-line argument tests moved to Stem. Resolves ticket 14806.
7468 - Integrate the ntor, backtrace, and zero-length keys tests into the
7469 automake test suite. Closes ticket 15344.
7470 - Remove assertions during builds to determine Tor's test coverage.
7471 We don't want to trigger these even in assertions, so including
7472 them artificially makes our branch coverage look worse than it is.
7473 This patch provides the new test-stem-full and coverage-html-full
7474 configure options. Implements ticket 15400.
7476 o Minor bugfixes (build):
7477 - Improve out-of-tree builds by making non-standard rules work and
7478 clean up additional files and directories. Fixes bug 15053; bugfix
7481 o Minor bugfixes (command-line interface):
7482 - When "--quiet" is provided along with "--validate-config", do not
7483 write anything to stdout on success. Fixes bug 14994; bugfix
7485 - When complaining about bad arguments to "--dump-config", use
7488 o Minor bugfixes (configuration, unit tests):
7489 - Only add the default fallback directories when the DirAuthorities,
7490 AlternateDirAuthority, and FallbackDir directory config options
7491 are set to their defaults. The default fallback directory list is
7492 currently empty, this fix will only change tor's behavior when it
7493 has default fallback directories. Includes unit tests for
7494 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
7495 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
7497 o Minor bugfixes (correctness):
7498 - For correctness, avoid modifying a constant string in
7499 handle_control_postdescriptor. Fixes bug 15546; bugfix
7501 - Remove side-effects from tor_assert() calls. This was harmless,
7502 because we never disable assertions, but it is bad style and
7503 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
7506 o Minor bugfixes (hidden service):
7507 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7508 a client authorized hidden service. Fixes bug 15823; bugfix
7510 - Remove an extraneous newline character from the end of hidden
7511 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
7513 o Minor bugfixes (interface):
7514 - Print usage information for --dump-config when it is used without
7515 an argument. Also, fix the error message to use different wording
7516 and add newline at the end. Fixes bug 15541; bugfix
7519 o Minor bugfixes (logs):
7520 - When building Tor under Clang, do not include an extra set of
7521 parentheses in log messages that include function names. Fixes bug
7522 15269; bugfix on every released version of Tor when compiled with
7523 recent enough Clang.
7525 o Minor bugfixes (network):
7526 - When attempting to use fallback technique for network interface
7527 lookup, disregard loopback and multicast addresses since they are
7528 unsuitable for public communications.
7530 o Minor bugfixes (statistics):
7531 - Disregard the ConnDirectionStatistics torrc options when Tor is
7532 not a relay since in that mode of operation no sensible data is
7533 being collected and because Tor might run into measurement hiccups
7534 when running as a client for some time, then becoming a relay.
7535 Fixes bug 15604; bugfix on 0.2.2.35.
7537 o Minor bugfixes (test networks):
7538 - When self-testing reachability, use ExtendAllowPrivateAddresses to
7539 determine if local/private addresses imply reachability. The
7540 previous fix used TestingTorNetwork, which implies
7541 ExtendAllowPrivateAddresses, but this excluded rare configurations
7542 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
7543 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
7544 issue discovered by CJ Ess.
7546 o Minor bugfixes (testing):
7547 - Check for matching value in server response in ntor_ref.py. Fixes
7548 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
7550 - Set the severity correctly when testing
7551 get_interface_addresses_ifaddrs() and
7552 get_interface_addresses_win32(), so that the tests fail gracefully
7553 instead of triggering an assertion. Fixes bug 15759; bugfix on
7554 0.2.6.3-alpha. Reported by Nicolas Derive.
7556 o Code simplification and refactoring:
7557 - Move the hacky fallback code out of get_interface_address6() into
7558 separate function and get it covered with unit-tests. Resolves
7560 - Refactor hidden service client-side cache lookup to intelligently
7561 report its various failure cases, and disentangle failure cases
7562 involving a lack of introduction points. Closes ticket 14391.
7563 - Use our own Base64 encoder instead of OpenSSL's, to allow more
7564 control over the output. Part of ticket 15652.
7567 - Improve the descriptions of statistics-related torrc options in
7568 the manpage to describe rationale and possible uses cases. Fixes
7570 - Improve the layout and formatting of ./configure --help messages.
7571 Closes ticket 15024. Patch from "cypherpunks".
7572 - Standardize on the term "server descriptor" in the manual page.
7573 Previously, we had used "router descriptor", "server descriptor",
7574 and "relay descriptor" interchangeably. Part of ticket 14987.
7577 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
7578 and always use the internal Base64 decoder. The internal decoder
7579 has been part of tor since 0.2.0.10-alpha, and no one should
7580 be using the OpenSSL one. Part of ticket 15652.
7581 - Remove the 'tor_strclear()' function; use memwipe() instead.
7582 Closes ticket 14922.
7585 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
7586 fingerprinting we now recommend pluggable transports; for forward-
7587 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
7588 - Remove the undocumented "--digests" command-line option. It
7589 complicated our build process, caused subtle build issues on
7590 multiple platforms, and is now redundant since we started
7591 including git version identifiers. Closes ticket 14742.
7592 - Tor no longer contains checks for ancient directory cache versions
7593 that didn't know about microdescriptors.
7594 - Tor no longer contains workarounds for stat files generated by
7595 super-old versions of Tor that didn't choose guards sensibly.
7598 Changes in version 0.2.4.27 - 2015-04-06
7599 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
7600 could be used by an attacker to crash hidden services, or crash clients
7601 visiting hidden services. Hidden services should upgrade as soon as
7602 possible; clients should upgrade whenever packages become available.
7604 This release also backports a simple improvement to make hidden
7605 services a bit less vulnerable to denial-of-service attacks.
7607 o Major bugfixes (security, hidden service):
7608 - Fix an issue that would allow a malicious client to trigger an
7609 assertion failure and halt a hidden service. Fixes bug 15600;
7610 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7611 - Fix a bug that could cause a client to crash with an assertion
7612 failure when parsing a malformed hidden service descriptor. Fixes
7613 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7615 o Minor features (DoS-resistance, hidden service):
7616 - Introduction points no longer allow multiple INTRODUCE1 cells to
7617 arrive on the same circuit. This should make it more expensive for
7618 attackers to overwhelm hidden services with introductions.
7619 Resolves ticket 15515.
7622 Changes in version 0.2.5.12 - 2015-04-06
7623 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
7624 could be used by an attacker to crash hidden services, or crash clients
7625 visiting hidden services. Hidden services should upgrade as soon as
7626 possible; clients should upgrade whenever packages become available.
7628 This release also backports a simple improvement to make hidden
7629 services a bit less vulnerable to denial-of-service attacks.
7631 o Major bugfixes (security, hidden service):
7632 - Fix an issue that would allow a malicious client to trigger an
7633 assertion failure and halt a hidden service. Fixes bug 15600;
7634 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7635 - Fix a bug that could cause a client to crash with an assertion
7636 failure when parsing a malformed hidden service descriptor. Fixes
7637 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7639 o Minor features (DoS-resistance, hidden service):
7640 - Introduction points no longer allow multiple INTRODUCE1 cells to
7641 arrive on the same circuit. This should make it more expensive for
7642 attackers to overwhelm hidden services with introductions.
7643 Resolves ticket 15515.
7646 Changes in version 0.2.6.7 - 2015-04-06
7647 Tor 0.2.6.7 fixes two security issues that could be used by an
7648 attacker to crash hidden services, or crash clients visiting hidden
7649 services. Hidden services should upgrade as soon as possible; clients
7650 should upgrade whenever packages become available.
7652 This release also contains two simple improvements to make hidden
7653 services a bit less vulnerable to denial-of-service attacks.
7655 o Major bugfixes (security, hidden service):
7656 - Fix an issue that would allow a malicious client to trigger an
7657 assertion failure and halt a hidden service. Fixes bug 15600;
7658 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7659 - Fix a bug that could cause a client to crash with an assertion
7660 failure when parsing a malformed hidden service descriptor. Fixes
7661 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7663 o Minor features (DoS-resistance, hidden service):
7664 - Introduction points no longer allow multiple INTRODUCE1 cells to
7665 arrive on the same circuit. This should make it more expensive for
7666 attackers to overwhelm hidden services with introductions.
7667 Resolves ticket 15515.
7668 - Decrease the amount of reattempts that a hidden service performs
7669 when its rendezvous circuits fail. This reduces the computational
7670 cost for running a hidden service under heavy load. Resolves
7674 Changes in version 0.2.6.6 - 2015-03-24
7675 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
7677 It adds numerous safety, security, correctness, and performance
7678 improvements. Client programs can be configured to use more kinds of
7679 sockets, AutomapHosts works better, the multithreading backend is
7680 improved, cell transmission is refactored, test coverage is much
7681 higher, more denial-of-service attacks are handled, guard selection is
7682 improved to handle long-term guards better, pluggable transports
7683 should work a bit better, and some annoying hidden service performance
7684 bugs should be addressed.
7686 o Minor bugfixes (portability):
7687 - Use the correct datatype in the SipHash-2-4 function to prevent
7688 compilers from assuming any sort of alignment. Fixes bug 15436;
7689 bugfix on 0.2.5.3-alpha.
7691 Changes in version 0.2.6.5-rc - 2015-03-18
7692 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
7693 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
7695 o Major bugfixes (client):
7696 - Avoid crashing when making certain configuration option changes on
7697 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
7700 o Major bugfixes (pluggable transports):
7701 - Initialize the extended OR Port authentication cookie before
7702 launching pluggable transports. This prevents a race condition
7703 that occured when server-side pluggable transports would cache the
7704 authentication cookie before it has been (re)generated. Fixes bug
7705 15240; bugfix on 0.2.5.1-alpha.
7707 o Major bugfixes (portability):
7708 - Do not crash on startup when running on Solaris. Fixes a bug
7709 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
7712 o Minor features (heartbeat):
7713 - On relays, report how many connections we negotiated using each
7714 version of the Tor link protocols. This information will let us
7715 know if removing support for very old versions of the Tor
7716 protocols is harming the network. Closes ticket 15212.
7718 o Code simplification and refactoring:
7719 - Refactor main loop to extract the 'loop' part. This makes it
7720 easier to run Tor under Shadow. Closes ticket 15176.
7723 Changes in version 0.2.5.11 - 2015-03-17
7724 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
7726 It backports several bugfixes from the 0.2.6 branch, including a
7727 couple of medium-level security fixes for relays and exit nodes.
7728 It also updates the list of directory authorities.
7730 o Directory authority changes:
7731 - Remove turtles as a directory authority.
7732 - Add longclaw as a new (v3) directory authority. This implements
7733 ticket 13296. This keeps the directory authority count at 9.
7734 - The directory authority Faravahar has a new IP address. This
7735 closes ticket 14487.
7737 o Major bugfixes (crash, OSX, security):
7738 - Fix a remote denial-of-service opportunity caused by a bug in
7739 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7742 o Major bugfixes (relay, stability, possible security):
7743 - Fix a bug that could lead to a relay crashing with an assertion
7744 failure if a buffer of exactly the wrong layout was passed to
7745 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7746 0.2.0.10-alpha. Patch from 'cypherpunks'.
7747 - Do not assert if the 'data' pointer on a buffer is advanced to the
7748 very end of the buffer; log a BUG message instead. Only assert if
7749 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7751 o Major bugfixes (exit node stability):
7752 - Fix an assertion failure that could occur under high DNS load.
7753 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7754 diagnosed and fixed by "cypherpunks".
7756 o Major bugfixes (Linux seccomp2 sandbox):
7757 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7758 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7759 0.2.5.1-alpha. Patch from "sanic".
7761 o Minor features (controller):
7762 - New "GETINFO bw-event-cache" to get information about recent
7763 bandwidth events. Closes ticket 14128. Useful for controllers to
7764 get recent bandwidth history after the fix for ticket 13988.
7766 o Minor features (geoip):
7767 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7768 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7771 o Minor bugfixes (client, automapping):
7772 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
7773 no value follows the option. Fixes bug 14142; bugfix on
7774 0.2.4.7-alpha. Patch by "teor".
7775 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
7776 14195; bugfix on 0.1.0.1-rc.
7778 o Minor bugfixes (compilation):
7779 - Build without warnings with the stock OpenSSL srtp.h header, which
7780 has a duplicate declaration of SSL_get_selected_srtp_profile().
7781 Fixes bug 14220; this is OpenSSL's bug, not ours.
7783 o Minor bugfixes (directory authority):
7784 - Allow directory authorities to fetch more data from one another if
7785 they find themselves missing lots of votes. Previously, they had
7786 been bumping against the 10 MB queued data limit. Fixes bug 14261;
7787 bugfix on 0.1.2.5-alpha.
7788 - Enlarge the buffer to read bwauth generated files to avoid an
7789 issue when parsing the file in dirserv_read_measured_bandwidths().
7790 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
7792 o Minor bugfixes (statistics):
7793 - Increase period over which bandwidth observations are aggregated
7794 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7796 o Minor bugfixes (preventative security, C safety):
7797 - When reading a hexadecimal, base-32, or base-64 encoded value from
7798 a string, always overwrite the whole output buffer. This prevents
7799 some bugs where we would look at (but fortunately, not reveal)
7800 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7804 Changes in version 0.2.4.26 - 2015-03-17
7805 Tor 0.2.4.26 includes an updated list of directory authorities. It
7806 also backports a couple of stability and security bugfixes from 0.2.5
7809 o Directory authority changes:
7810 - Remove turtles as a directory authority.
7811 - Add longclaw as a new (v3) directory authority. This implements
7812 ticket 13296. This keeps the directory authority count at 9.
7813 - The directory authority Faravahar has a new IP address. This
7814 closes ticket 14487.
7816 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
7817 - Fix an assertion failure that could occur under high DNS load.
7818 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7819 diagnosed and fixed by "cypherpunks".
7821 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
7822 - Fix a bug that could lead to a relay crashing with an assertion
7823 failure if a buffer of exactly the wrong layout was passed to
7824 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7825 0.2.0.10-alpha. Patch from 'cypherpunks'.
7826 - Do not assert if the 'data' pointer on a buffer is advanced to the
7827 very end of the buffer; log a BUG message instead. Only assert if
7828 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7830 o Minor features (geoip):
7831 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7832 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7835 Changes in version 0.2.6.4-rc - 2015-03-09
7836 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
7837 attacker might be able to use in order to crash certain Tor
7838 directories. It also resolves some minor issues left over from, or
7839 introduced in, Tor 0.2.6.3-alpha or earlier.
7841 o Major bugfixes (crash, OSX, security):
7842 - Fix a remote denial-of-service opportunity caused by a bug in
7843 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7846 o Major bugfixes (relay, stability, possible security):
7847 - Fix a bug that could lead to a relay crashing with an assertion
7848 failure if a buffer of exactly the wrong layout is passed to
7849 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7850 0.2.0.10-alpha. Patch from "cypherpunks".
7851 - Do not assert if the 'data' pointer on a buffer is advanced to the
7852 very end of the buffer; log a BUG message instead. Only assert if
7853 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7855 o Major bugfixes (FreeBSD IPFW transparent proxy):
7856 - Fix address detection with FreeBSD transparent proxies, when
7857 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
7860 o Major bugfixes (Linux seccomp2 sandbox):
7861 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
7862 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
7864 - Allow AF_UNIX hidden services to be used with the seccomp2
7865 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
7866 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7867 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7868 0.2.5.1-alpha. Patch from "sanic".
7870 o Minor features (controller):
7871 - Messages about problems in the bootstrap process now include
7872 information about the server we were trying to connect to when we
7873 noticed the problem. Closes ticket 15006.
7875 o Minor features (geoip):
7876 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7877 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7880 o Minor features (logs):
7881 - Quiet some log messages in the heartbeat and at startup. Closes
7884 o Minor bugfixes (certificate handling):
7885 - If an authority operator accidentally makes a signing certificate
7886 with a future publication time, do not discard its real signing
7887 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
7888 - Remove any old authority certificates that have been superseded
7889 for at least two days. Previously, we would keep superseded
7890 certificates until they expired, if they were published close in
7891 time to the certificate that superseded them. Fixes bug 11454;
7892 bugfix on 0.2.1.8-alpha.
7894 o Minor bugfixes (compilation):
7895 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
7897 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
7900 o Minor bugfixes (testing):
7901 - Fix endianness issues in unit test for resolve_my_address() to
7902 have it pass on big endian systems. Fixes bug 14980; bugfix on
7904 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
7905 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
7906 - When running the new 'make test-stem' target, use the configured
7907 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
7909 - When running the zero-length-keys tests, do not use the default
7910 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
7913 o Directory authority IP change:
7914 - The directory authority Faravahar has a new IP address. This
7915 closes ticket 14487.
7918 - Remove some lingering dead code that once supported mempools.
7919 Mempools were disabled by default in 0.2.5, and removed entirely
7920 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
7924 Changes in version 0.2.6.3-alpha - 2015-02-19
7925 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
7926 the 0.2.6.x series. It introduces support for more kinds of sockets,
7927 makes it harder to accidentally run an exit, improves our
7928 multithreading backend, incorporates several fixes for the
7929 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
7931 If no major regressions or security holes are found in this version,
7932 the next version will be a release candidate.
7934 o Deprecated versions:
7935 - Tor relays older than 0.2.4.18-rc are no longer allowed to
7936 advertise themselves on the network. Closes ticket 13555.
7938 o Major features (security, unix domain sockets):
7939 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
7940 applications can reach Tor without having to create AF_INET or
7941 AF_INET6 sockets, meaning they can completely disable their
7942 ability to make non-Tor network connections. To create a socket of
7943 this type, use "SocksPort unix:/path/to/socket". Implements
7945 - Support mapping hidden service virtual ports to AF_UNIX sockets.
7946 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
7947 Implements ticket 11485.
7949 o Major features (changed defaults):
7950 - Prevent relay operators from unintentionally running exits: When a
7951 relay is configured as an exit node, we now warn the user unless
7952 the "ExitRelay" option is set to 1. We warn even more loudly if
7953 the relay is configured with the default exit policy, since this
7954 can indicate accidental misconfiguration. Setting "ExitRelay 0"
7955 stops Tor from running as an exit relay. Closes ticket 10067.
7957 o Major features (directory system):
7958 - When downloading server- or microdescriptors from a directory
7959 server, we no longer launch multiple simultaneous requests to the
7960 same server. This reduces load on the directory servers,
7961 especially when directory guards are in use. Closes ticket 9969.
7962 - When downloading server- or microdescriptors over a tunneled
7963 connection, do not limit the length of our requests to what the
7964 Squid proxy is willing to handle. Part of ticket 9969.
7965 - Authorities can now vote on the correct digests and latest
7966 versions for different software packages. This allows packages
7967 that include Tor to use the Tor authority system as a way to get
7968 notified of updates and their correct digests. Implements proposal
7969 227. Closes ticket 10395.
7971 o Major features (guards):
7972 - Introduce the Guardfraction feature to improves load balancing on
7973 guard nodes. Specifically, it aims to reduce the traffic gap that
7974 guard nodes experience when they first get the Guard flag. This is
7975 a required step if we want to increase the guard lifetime to 9
7976 months or greater. Closes ticket 9321.
7978 o Major features (performance):
7979 - Make the CPU worker implementation more efficient by avoiding the
7980 kernel and lengthening pipelines. The original implementation used
7981 sockets to transfer data from the main thread to the workers, and
7982 didn't allow any thread to be assigned more than a single piece of
7983 work at once. The new implementation avoids communications
7984 overhead by making requests in shared memory, avoiding kernel IO
7985 where possible, and keeping more requests in flight at once.
7986 Implements ticket 9682.
7988 o Major features (relay):
7989 - Raise the minimum acceptable configured bandwidth rate for bridges
7990 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
7991 20 KiB/sec.) Closes ticket 13822.
7993 o Major bugfixes (exit node stability):
7994 - Fix an assertion failure that could occur under high DNS load.
7995 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7996 diagnosed and fixed by "cypherpunks".
7998 o Major bugfixes (mixed relay-client operation):
7999 - When running as a relay and client at the same time (not
8000 recommended), if we decide not to use a new guard because we want
8001 to retry older guards, only close the locally-originating circuits
8002 passing through that guard. Previously we would close all the
8003 circuits through that guard. Fixes bug 9819; bugfix on
8004 0.2.1.1-alpha. Reported by "skruffy".
8006 o Minor features (build):
8007 - New --disable-system-torrc compile-time option to prevent Tor from
8008 looking for the system-wide torrc or torrc-defaults files.
8009 Resolves ticket 13037.
8011 o Minor features (controller):
8012 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
8013 events so controllers can observe circuit isolation inputs. Closes
8015 - ControlPort now supports the unix:/path/to/socket syntax as an
8016 alternative to the ControlSocket option, for consistency with
8017 SocksPort and HiddenServicePort. Closes ticket 14451.
8018 - New "GETINFO bw-event-cache" to get information about recent
8019 bandwidth events. Closes ticket 14128. Useful for controllers to
8020 get recent bandwidth history after the fix for ticket 13988.
8022 o Minor features (Denial of service resistance):
8023 - Count the total number of bytes used storing hidden service
8024 descriptors against the value of MaxMemInQueues. If we're low on
8025 memory, and more than 20% of our memory is used holding hidden
8026 service descriptors, free them until no more than 10% of our
8027 memory holds hidden service descriptors. Free the least recently
8028 fetched descriptors first. Resolves ticket 13806.
8029 - When we have recently been under memory pressure (over 3/4 of
8030 MaxMemInQueues is allocated), then allocate smaller zlib objects
8031 for small requests. Closes ticket 11791.
8033 o Minor features (geoip):
8034 - Update geoip and geoip6 files to the January 7 2015 Maxmind
8035 GeoLite2 Country database.
8037 o Minor features (guard nodes):
8038 - Reduce the time delay before saving guard status to disk from 10
8039 minutes to 30 seconds (or from one hour to 10 minutes if
8040 AvoidDiskWrites is set). Closes ticket 12485.
8042 o Minor features (hidden service):
8043 - Make Sybil attacks against hidden services harder by changing the
8044 minimum time required to get the HSDir flag from 25 hours up to 96
8045 hours. Addresses ticket 14149.
8046 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
8047 services to disable the anti-scanning feature introduced in
8048 0.2.6.2-alpha. With this option not set, a connection to an
8049 unlisted port closes the circuit. With this option set, only a
8050 RELAY_DONE cell is sent. Closes ticket 14084.
8052 o Minor features (interface):
8053 - Implement "-f -" command-line option to read torrc configuration
8054 from standard input, if you don't want to store the torrc file in
8055 the file system. Implements feature 13865.
8057 o Minor features (logging):
8058 - Add a count of unique clients to the bridge heartbeat message.
8059 Resolves ticket 6852.
8060 - Suppress "router info incompatible with extra info" message when
8061 reading extrainfo documents from cache. (This message got loud
8062 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
8064 - Elevate hidden service authorized-client message from DEBUG to
8065 INFO. Closes ticket 14015.
8067 o Minor features (stability):
8068 - Add assertions in our hash-table iteration code to check for
8069 corrupted values that could cause infinite loops. Closes
8072 o Minor features (systemd):
8073 - Various improvements and modernizations in systemd hardening
8074 support. Closes ticket 13805. Patch from Craig Andrews.
8076 o Minor features (testing networks):
8077 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
8078 and the default on a testing network to 2 minutes. Drop the
8079 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
8080 keep the default on a testing network at 30 seconds. This reduces
8081 HS bootstrap time to around 25 seconds. Also, change the default
8082 time in test-network.sh to match. Closes ticket 13401. Patch
8084 - Create TestingDirAuthVoteHSDir to correspond to
8085 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
8086 HSDir flag for the listed relays regardless of uptime or ORPort
8087 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
8088 Partial implementation for ticket 14067. Patch by "teor".
8090 o Minor features (tor2web mode):
8091 - Introduce the config option Tor2webRendezvousPoints, which allows
8092 clients in Tor2webMode to select a specific Rendezvous Point to be
8093 used in HS circuits. This might allow better performance for
8094 Tor2Web nodes. Implements ticket 12844.
8096 o Minor bugfixes (client DNS):
8097 - Report the correct cached DNS expiration times on SOCKS port or in
8098 DNS replies. Previously, we would report everything as "never
8099 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
8100 - Avoid a small memory leak when we find a cached answer for a
8101 reverse DNS lookup in a client-side DNS cache. (Remember, client-
8102 side DNS caching is off by default, and is not recommended.) Fixes
8103 bug 14259; bugfix on 0.2.0.1-alpha.
8105 o Minor bugfixes (client, automapping):
8106 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8107 no value follows the option. Fixes bug 14142; bugfix on
8108 0.2.4.7-alpha. Patch by "teor".
8109 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8110 14195; bugfix on 0.1.0.1-rc.
8111 - Prevent changes to other options from removing the wildcard value
8112 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
8114 - Allow MapAddress and AutomapHostsOnResolve to work together when
8115 an address is mapped into another address type (like .onion) that
8116 must be automapped at resolve time. Fixes bug 7555; bugfix
8119 o Minor bugfixes (client, bridges):
8120 - When we are using bridges and we had a network connectivity
8121 problem, only retry connecting to our currently configured
8122 bridges, not all bridges we know about and remember using. Fixes
8123 bug 14216; bugfix on 0.2.2.17-alpha.
8125 o Minor bugfixes (client, IPv6):
8126 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
8127 flag is not set; and not because the NoIPv4Traffic flag was set.
8128 Previously we'd looked at the NoIPv4Traffic flag for both types of
8129 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
8131 o Minor bugfixes (compilation):
8132 - The address of an array in the middle of a structure will always
8133 be non-NULL. clang recognises this and complains. Disable the
8134 tautologous and redundant check to silence this warning. Fixes bug
8135 14001; bugfix on 0.2.1.2-alpha.
8136 - Avoid warnings when building with systemd 209 or later. Fixes bug
8137 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
8138 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
8139 Addresses ticket 14188.
8140 - Build without warnings with the stock OpenSSL srtp.h header, which
8141 has a duplicate declaration of SSL_get_selected_srtp_profile().
8142 Fixes bug 14220; this is OpenSSL's bug, not ours.
8143 - Do not compile any code related to Tor2Web mode when Tor2Web mode
8144 is not enabled at compile time. Previously, this code was included
8145 in a disabled state. See discussion on ticket 12844.
8146 - Remove the --disable-threads configure option again. It was
8147 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
8148 14819; bugfix on 0.2.6.2-alpha.
8150 o Minor bugfixes (controller):
8151 - Report "down" in response to the "GETINFO entry-guards" command
8152 when relays are down with an unreachable_since value. Previously,
8153 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
8154 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
8155 14116; bugfix on 0.2.2.9-alpha.
8156 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
8157 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
8159 o Minor bugfixes (directory authority):
8160 - Allow directory authorities to fetch more data from one another if
8161 they find themselves missing lots of votes. Previously, they had
8162 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8163 bugfix on 0.1.2.5-alpha.
8164 - Do not attempt to download extrainfo documents which we will be
8165 unable to validate with a matching server descriptor. Fixes bug
8166 13762; bugfix on 0.2.0.1-alpha.
8167 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
8168 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
8169 - Enlarge the buffer to read bwauth generated files to avoid an
8170 issue when parsing the file in dirserv_read_measured_bandwidths().
8171 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8173 o Minor bugfixes (file handling):
8174 - Stop failing when key files are zero-length. Instead, generate new
8175 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
8176 on all versions of Tor. Patch by "teor".
8177 - Stop generating a fresh .old RSA onion key file when the .old file
8178 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
8179 - Avoid overwriting .old key files with empty key files.
8180 - Skip loading zero-length extrainfo store, router store, stats,
8181 state, and key files.
8182 - Avoid crashing when trying to reload a torrc specified as a
8183 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
8186 o Minor bugfixes (hidden services):
8187 - Close the introduction circuit when we have no more usable intro
8188 points, instead of waiting for it to time out. This also ensures
8189 that no follow-up HS descriptor fetch is triggered when the
8190 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
8191 - When fetching a hidden service descriptor for a down service that
8192 was recently up, do not keep refetching until we try the same
8193 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
8194 - Successfully launch Tor with a nonexistent hidden service
8195 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
8196 14106; bugfix on 0.2.6.2-alpha.
8198 o Minor bugfixes (logging):
8199 - Avoid crashing when there are more log domains than entries in
8200 domain_list. Bugfix on 0.2.3.1-alpha.
8201 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
8203 - Don't log messages to stdout twice when starting up. Fixes bug
8204 13993; bugfix on 0.2.6.1-alpha.
8206 o Minor bugfixes (parsing):
8207 - Stop accepting milliseconds (or other junk) at the end of
8208 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
8209 - Support two-number and three-number version numbers correctly, in
8210 case we change the Tor versioning system in the future. Fixes bug
8211 13661; bugfix on 0.0.8pre1.
8213 o Minor bugfixes (path counting):
8214 - When deciding whether the consensus lists any exit nodes, count
8215 the number listed in the consensus, not the number we have
8216 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
8217 - When deciding whether we have any exit nodes, only examine
8218 ExitNodes when the ExitNodes option is actually set. Fixes part of
8219 bug 14918; bugfix on 0.2.6.2-alpha.
8220 - Get rid of redundant and possibly scary warnings that we are
8221 missing directory information while we bootstrap. Fixes part of
8222 bug 14918; bugfix on 0.2.6.2-alpha.
8224 o Minor bugfixes (portability):
8225 - Fix the ioctl()-based network interface lookup code so that it
8226 will work on systems that have variable-length struct ifreq, for
8228 - Fix scheduler compilation on targets where char is unsigned. Fixes
8229 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
8231 o Minor bugfixes (sandbox):
8232 - Allow glibc fatal errors to be sent to stderr before Tor exits.
8233 Previously, glibc would try to write them to /dev/tty, and the
8234 sandbox would trap the call and make Tor exit prematurely. Fixes
8235 bug 14759; bugfix on 0.2.5.1-alpha.
8237 o Minor bugfixes (shutdown):
8238 - When shutting down, always call event_del() on lingering read or
8239 write events before freeing them. Otherwise, we risk double-frees
8240 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
8243 o Minor bugfixes (small memory leaks):
8244 - Avoid leaking memory when using IPv6 virtual address mappings.
8245 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
8248 o Minor bugfixes (statistics):
8249 - Increase period over which bandwidth observations are aggregated
8250 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
8252 o Minor bugfixes (systemd support):
8253 - Fix detection and operation of systemd watchdog. Fixes part of bug
8254 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
8255 - Run correctly under systemd with the RunAsDaemon option set. Fixes
8256 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
8257 - Inform the systemd supervisor about more changes in the Tor
8258 process status. Implements part of ticket 14141. Patch from
8260 - Cause the "--disable-systemd" option to actually disable systemd
8261 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
8264 o Minor bugfixes (TLS):
8265 - Check more thoroughly throughout the TLS code for possible
8266 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
8268 o Minor bugfixes (transparent proxy):
8269 - Use getsockname, not getsockopt, to retrieve the address for a
8270 TPROXY-redirected connection. Fixes bug 13796; bugfix
8273 o Code simplification and refactoring:
8274 - Move fields related to isolating and configuring client ports into
8275 a shared structure. Previously, they were duplicated across
8276 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
8277 to copy them correctly had been the cause of at least one bug in
8278 the past. Closes ticket 8546.
8279 - Refactor the get_interface_addresses_raw() doom-function into
8280 multiple smaller and simpler subfunctions. Cover the resulting
8281 subfunctions with unit-tests. Fixes a significant portion of
8283 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
8284 only for version <= 0.2.2.24 which is now deprecated. Closes
8286 - Remove a test for a long-defunct broken version-one
8290 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
8291 for writing the OpenBSD-specific tips. Resolves ticket 13702.
8292 - Make the tor-resolve documentation match its help string and its
8293 options. Resolves part of ticket 14325.
8294 - Log a more useful error message from tor-resolve when failing to
8295 look up a hidden service address. Resolves part of ticket 14325.
8297 o Downgraded warnings:
8298 - Don't warn when we've attempted to contact a relay using the wrong
8299 ntor onion key. Closes ticket 9635.
8302 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
8303 longer silently accepted as an alias for "ExitNodes".
8304 - The --enable-mempool and --enable-buf-freelists options, which
8305 were originally created to work around bad malloc implementations,
8306 no longer exist. They were off-by-default in 0.2.5. Closes
8310 - Make the checkdir/perms test complete successfully even if the
8311 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
8312 - Test that tor does not fail when key files are zero-length. Check
8313 that tor generates new keys, and overwrites the empty key files.
8314 - Test that tor generates new keys when keys are missing
8315 (existing behavior).
8316 - Test that tor does not overwrite key files that already contain
8317 data (existing behavior). Tests bug 13111. Patch by "teor".
8318 - New "make test-stem" target to run stem integration tests.
8319 Requires that the "STEM_SOURCE_DIR" environment variable be set.
8320 Closes ticket 14107.
8321 - Make the test_cmdline_args.py script work correctly on Windows.
8322 Patch from Gisle Vanem.
8323 - Move the slower unit tests into a new "./src/test/test-slow"
8324 binary that can be run independently of the other tests. Closes
8326 - Avoid undefined behavior when sampling huge values from the
8327 Laplace distribution. This made unittests fail on Raspberry Pi.
8328 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
8331 Changes in version 0.2.6.2-alpha - 2014-12-31
8332 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
8333 It introduces a major new backend for deciding when to send cells on
8334 channels, which should lead down the road to big performance
8335 increases. It contains security and statistics features for better
8336 work on hidden services, and numerous bugfixes.
8338 This release contains many new unit tests, along with major
8339 performance improvements for running testing networks using Chutney.
8340 Thanks to a series of patches contributed by "teor", testing networks
8341 should now bootstrap in seconds, rather than minutes.
8343 o Major features (relay, infrastructure):
8344 - Complete revision of the code that relays use to decide which cell
8345 to send next. Formerly, we selected the best circuit to write on
8346 each channel, but we didn't select among channels in any
8347 sophisticated way. Now, we choose the best circuits globally from
8348 among those whose channels are ready to deliver traffic.
8350 This patch implements a new inter-cmux comparison API, a global
8351 high/low watermark mechanism and a global scheduler loop for
8352 transmission prioritization across all channels as well as among
8353 circuits on one channel. This schedule is currently tuned to
8354 (tolerantly) avoid making changes in network performance, but it
8355 should form the basis for major circuit performance increases in
8356 the future. Code by Andrea; tuning by Rob Jansen; implements
8359 o Major features (hidden services):
8360 - Make HS port scanning more difficult by immediately closing the
8361 circuit when a user attempts to connect to a nonexistent port.
8362 Closes ticket 13667.
8363 - Add a HiddenServiceStatistics option that allows Tor relays to
8364 gather and publish statistics about the overall size and volume of
8365 hidden service usage. Specifically, when this option is turned on,
8366 an HSDir will publish an approximate number of hidden services
8367 that have published descriptors to it the past 24 hours. Also, if
8368 a relay has acted as a hidden service rendezvous point, it will
8369 publish the approximate amount of rendezvous cells it has relayed
8370 the past 24 hours. The statistics themselves are obfuscated so
8371 that the exact values cannot be derived. For more details see
8372 proposal 238, "Better hidden service stats from Tor relays". This
8373 feature is currently disabled by default. Implements feature 13192.
8375 o Major bugfixes (client, automap):
8376 - Repair automapping with IPv6 addresses. This automapping should
8377 have worked previously, but one piece of debugging code that we
8378 inserted to detect a regression actually caused the regression to
8379 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
8380 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
8383 o Major bugfixes (hidden services):
8384 - When closing an introduction circuit that was opened in parallel
8385 with others, don't mark the introduction point as unreachable.
8386 Previously, the first successful connection to an introduction
8387 point would make the other introduction points get marked as
8388 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
8390 o Directory authority changes:
8391 - Remove turtles as a directory authority.
8392 - Add longclaw as a new (v3) directory authority. This implements
8393 ticket 13296. This keeps the directory authority count at 9.
8395 o Major removed features:
8396 - Tor clients no longer support connecting to hidden services
8397 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
8398 option has been removed. (There shouldn't be any hidden services
8399 running these versions on the network.) Closes ticket 7803.
8401 o Minor features (client):
8402 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
8403 is enabled, reject requests with IP addresses as hostnames.
8404 Resolves ticket 13315.
8406 o Minor features (controller):
8407 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
8408 write an unscheduled heartbeat message to the log. Implements
8411 o Minor features (geoip):
8412 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
8415 o Minor features (hidden services):
8416 - When re-enabling the network, don't try to build introduction
8417 circuits until we have successfully built a circuit. This makes
8418 hidden services come up faster when the network is re-enabled.
8419 Patch from "akwizgran". Closes ticket 13447.
8420 - When we fail to retrieve a hidden service descriptor, send the
8421 controller an "HS_DESC FAILED" controller event. Implements
8423 - New HiddenServiceDirGroupReadable option to cause hidden service
8424 directories and hostname files to be created group-readable. Patch
8425 from "anon", David Stainton, and "meejah". Closes ticket 11291.
8427 o Minor features (systemd):
8428 - Where supported, when running with systemd, report successful
8429 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
8430 - When running with systemd, support systemd watchdog messages. Part
8431 of ticket 11016. Patch by Michael Scherer.
8433 o Minor features (transparent proxy):
8434 - Update the transparent proxy option checks to allow for both ipfw
8435 and pf on OS X. Closes ticket 14002.
8436 - Use the correct option when using IPv6 with transparent proxy
8437 support on Linux. Resolves 13808. Patch by Francisco Blas
8440 o Minor bugfixes (preventative security, C safety):
8441 - When reading a hexadecimal, base-32, or base-64 encoded value from
8442 a string, always overwrite the whole output buffer. This prevents
8443 some bugs where we would look at (but fortunately, not reveal)
8444 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
8446 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
8447 just the part that's used. This makes it harder for data leak bugs
8448 to occur in the event of other programming failures. Resolves
8451 o Minor bugfixes (client, microdescriptors):
8452 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
8453 computing which microdescriptors to download. This keeps us from
8454 erroneous download behavior if two microdescriptor digests ever
8455 have the same first 160 bits. Fixes part of bug 13399; bugfix
8457 - Reset a router's status if its microdescriptor digest changes,
8458 even if the first 160 bits remain the same. Fixes part of bug
8459 13399; bugfix on 0.2.3.1-alpha.
8461 o Minor bugfixes (compilation):
8462 - Silence clang warnings under --enable-expensive-hardening,
8463 including implicit truncation of 64 bit values to 32 bit, const
8464 char assignment to self, tautological compare, and additional
8465 parentheses around equality tests. Fixes bug 13577; bugfix
8467 - Fix a clang warning about checking whether an address in the
8468 middle of a structure is NULL. Fixes bug 14001; bugfix
8471 o Minor bugfixes (hidden services):
8472 - Correctly send a controller event when we find that a rendezvous
8473 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
8474 - Pre-check directory permissions for new hidden-services to avoid
8475 at least one case of "Bug: Acting on config options left us in a
8476 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
8477 - When adding a new hidden service (for example, via SETCONF), Tor
8478 no longer congratulates the user for running a relay. Fixes bug
8479 13941; bugfix on 0.2.6.1-alpha.
8480 - When fetching hidden service descriptors, we now check not only
8481 for whether we got the hidden service we had in mind, but also
8482 whether we got the particular descriptors we wanted. This prevents
8483 a class of inefficient but annoying DoS attacks by hidden service
8484 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
8487 o Minor bugfixes (Linux seccomp2 sandbox):
8488 - Make transparent proxy support work along with the seccomp2
8489 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
8490 by Francisco Blas Izquierdo Riera.
8491 - Fix a memory leak in tor-resolve when running with the sandbox
8492 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
8494 o Minor bugfixes (logging):
8495 - Downgrade warnings about RSA signature failures to info log level.
8496 Emit a warning when an extra info document is found incompatible
8497 with a corresponding router descriptor. Fixes bug 9812; bugfix
8499 - Make connection_ap_handshake_attach_circuit() log the circuit ID
8500 correctly. Fixes bug 13701; bugfix on 0.0.6.
8502 o Minor bugfixes (misc):
8503 - Stop allowing invalid address patterns like "*/24" that contain
8504 both a wildcard address and a bit prefix length. This affects all
8505 our address-range parsing code. Fixes bug 7484; bugfix
8508 o Minor bugfixes (testing networks, fast startup):
8509 - Allow Tor to build circuits using a consensus with no exits. If
8510 the consensus has no exits (typical of a bootstrapping test
8511 network), allow Tor to build circuits once enough descriptors have
8512 been downloaded. This assists in bootstrapping a testing Tor
8513 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
8515 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
8516 header to directory servers. This allows us to obtain consensuses
8517 promptly when the consensus interval is very short. This assists
8518 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
8519 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
8520 - Stop assuming that private addresses are local when checking
8521 reachability in a TestingTorNetwork. Instead, when testing, assume
8522 all OR connections are remote. (This is necessary due to many test
8523 scenarios running all relays on localhost.) This assists in
8524 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
8525 0.1.0.1-rc. Patch by "teor".
8526 - Avoid building exit circuits from a consensus with no exits. Now
8527 thanks to our fix for 13718, we accept a no-exit network as not
8528 wholly lost, but we need to remember not to try to build exit
8529 circuits on it. Closes ticket 13814; patch by "teor".
8530 - Stop requiring exits to have non-zero bandwithcapacity in a
8531 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
8532 ignore exit bandwidthcapacity. This assists in bootstrapping a
8533 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
8534 on 0.2.0.3-alpha. Patch by "teor".
8535 - Add "internal" to some bootstrap statuses when no exits are
8536 available. If the consensus does not contain Exits, Tor will only
8537 build internal circuits. In this case, relevant statuses will
8538 contain the word "internal" as indicated in the Tor control-
8539 spec.txt. When bootstrap completes, Tor will be ready to build
8540 internal circuits. If a future consensus contains Exits, exit
8541 circuits may become available. Fixes part of bug 13718; bugfix on
8542 0.2.4.10-alpha. Patch by "teor".
8543 - Decrease minimum consensus interval to 10 seconds when
8544 TestingTorNetwork is set, or 5 seconds for the first consensus.
8545 Fix assumptions throughout the code that assume larger intervals.
8546 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
8548 - Avoid excluding guards from path building in minimal test
8549 networks, when we're in a test network and excluding guards would
8550 exclude all relays. This typically occurs in incredibly small tor
8551 networks, and those using "TestingAuthVoteGuard *". Fixes part of
8552 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
8554 o Code simplification and refactoring:
8555 - Stop using can_complete_circuits as a global variable; access it
8556 with a function instead.
8557 - Avoid using operators directly as macro arguments: this lets us
8558 apply coccinelle transformations to our codebase more directly.
8559 Closes ticket 13172.
8560 - Combine the functions used to parse ClientTransportPlugin and
8561 ServerTransportPlugin into a single function. Closes ticket 6456.
8562 - Add inline functions and convenience macros for inspecting channel
8563 state. Refactor the code to use convenience macros instead of
8564 checking channel state directly. Fixes issue 7356.
8565 - Document all members of was_router_added_t and rename
8566 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
8567 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
8568 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
8569 constant instead of hardcoded value. Fixes issue 13840.
8570 - Refactor our generic strmap and digestmap types into a single
8571 implementation, so that we can add a new digest256map
8575 - Document the bridge-authority-only 'networkstatus-bridges' file.
8576 Closes ticket 13713; patch from "tom".
8577 - Fix typo in PredictedPortsRelevanceTime option description in
8578 manpage. Resolves issue 13707.
8579 - Stop suggesting that users specify relays by nickname: it isn't a
8580 good idea. Also, properly cross-reference how to specify relays in
8581 all parts of manual documenting options that take a list of
8582 relays. Closes ticket 13381.
8583 - Clarify the HiddenServiceDir option description in manpage to make
8584 it clear that relative paths are taken with respect to the current
8585 working directory. Also clarify that this behavior is not
8586 guaranteed to remain indefinitely. Fixes issue 13913.
8589 - New tests for many parts of channel, relay, and circuitmux
8590 functionality. Code by Andrea; part of 9262.
8591 - New tests for parse_transport_line(). Part of ticket 6456.
8592 - In the unit tests, use chgrp() to change the group of the unit
8593 test temporary directory to the current user, so that the sticky
8594 bit doesn't interfere with tests that check directory groups.
8596 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
8600 Changes in version 0.2.6.1-alpha - 2014-10-30
8601 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
8602 includes numerous code cleanups and new tests, and fixes a large
8603 number of annoying bugs. Out-of-memory conditions are handled better
8604 than in 0.2.5, pluggable transports have improved proxy support, and
8605 clients now use optimistic data for contacting hidden services. Also,
8606 we are now more robust to changes in what we consider a parseable
8607 directory object, so that tightening restrictions does not have a risk
8608 of introducing infinite download loops.
8610 This is the first alpha release in a new series, so expect there to be
8611 bugs. Users who would rather test out a more stable branch should stay
8612 with 0.2.5.x for now.
8614 o New compiler and system requirements:
8615 - Tor 0.2.6.x requires that your compiler support more of the C99
8616 language standard than before. The 'configure' script now detects
8617 whether your compiler supports C99 mid-block declarations and
8618 designated initializers. If it does not, Tor will not compile.
8620 We may revisit this requirement if it turns out that a significant
8621 number of people need to build Tor with compilers that don't
8622 bother implementing a 15-year-old standard. Closes ticket 13233.
8623 - Tor no longer supports systems without threading support. When we
8624 began working on Tor, there were several systems that didn't have
8625 threads, or where the thread support wasn't able to run the
8626 threads of a single process on multiple CPUs. That no longer
8627 holds: every system where Tor needs to run well now has threading
8628 support. Resolves ticket 12439.
8630 o Removed platform support:
8631 - We no longer include special code to build on Windows CE; as far
8632 as we know, nobody has used Tor on Windows CE in a very long time.
8633 Closes ticket 11446.
8635 o Major features (bridges):
8636 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
8637 transports if they are configured via the "TOR_PT_PROXY"
8638 environment variable. Implements proposal 232. Resolves
8641 o Major features (client performance, hidden services):
8642 - Allow clients to use optimistic data when connecting to a hidden
8643 service, which should remove a round-trip from hidden service
8644 initialization. See proposal 181 for details. Implements
8647 o Major features (directory system):
8648 - Upon receiving an unparseable directory object, if its digest
8649 matches what we expected, then don't try to download it again.
8650 Previously, when we got a descriptor we didn't like, we would keep
8651 trying to download it over and over. Closes ticket 11243.
8653 o Major features (sample torrc):
8654 - Add a new, infrequently-changed "torrc.minimal". This file is
8655 similar to torrc.sample, but it will change as infrequently as
8656 possible, for the benefit of users whose systems prompt them for
8657 intervention whenever a default configuration file is changed.
8658 Making this change allows us to update torrc.sample to be a more
8659 generally useful "sample torrc".
8661 o Major bugfixes (directory authorities):
8662 - Do not assign the HSDir flag to relays if they are not Valid, or
8663 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
8665 o Major bugfixes (directory bandwidth performance):
8666 - Don't flush the zlib buffer aggressively when compressing
8667 directory information for clients. This should save about 7% of
8668 the bandwidth currently used for compressed descriptors and
8669 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
8671 o Minor features (security, memory wiping):
8672 - Ensure we securely wipe keys from memory after
8673 crypto_digest_get_digest and init_curve25519_keypair_from_file
8674 have finished using them. Resolves ticket 13477.
8676 o Minor features (security, out-of-memory handling):
8677 - When handling an out-of-memory condition, allocate less memory for
8678 temporary data structures. Fixes issue 10115.
8679 - When handling an out-of-memory condition, consider more types of
8680 buffers, including those on directory connections, and zlib
8681 buffers. Resolves ticket 11792.
8684 - When identity keypair is generated for first time, log a
8685 congratulatory message that links to the new relay lifecycle
8686 document. Implements feature 10427.
8688 o Minor features (client):
8689 - Clients are now willing to send optimistic data (before they
8690 receive a 'connected' cell) to relays of any version. (Relays
8691 without support for optimistic data are no longer supported on the
8692 Tor network.) Resolves ticket 13153.
8694 o Minor features (directory authorities):
8695 - Don't list relays with a bandwidth estimate of 0 in the consensus.
8696 Implements a feature proposed during discussion of bug 13000.
8697 - In tor-gencert, report an error if the user provides the same
8698 argument more than once.
8699 - If a directory authority can't find a best consensus method in the
8700 votes that it holds, it now falls back to its favorite consensus
8701 method. Previously, it fell back to method 1. Neither of these is
8702 likely to get enough signatures, but "fall back to favorite"
8703 doesn't require us to maintain support an obsolete consensus
8704 method. Implements part of proposal 215.
8706 o Minor features (logging):
8707 - On Unix-like systems, you can now use named pipes as the target of
8708 the Log option, and other options that try to append to files.
8709 Closes ticket 12061. Patch from "carlo von lynX".
8710 - When opening a log file at startup, send it every log message that
8711 we generated between startup and opening it. Previously, log
8712 messages that were generated before opening the log file were only
8713 logged to stdout. Closes ticket 6938.
8714 - Add a TruncateLogFile option to overwrite logs instead of
8715 appending to them. Closes ticket 5583.
8717 o Minor features (portability, Solaris):
8718 - Threads are no longer disabled by default on Solaris; we believe
8719 that the versions of Solaris with broken threading support are all
8720 obsolete by now. Resolves ticket 9495.
8722 o Minor features (relay):
8723 - Re-check our address after we detect a changed IP address from
8724 getsockname(). This ensures that the controller command "GETINFO
8725 address" will report the correct value. Resolves ticket 11582.
8727 - A new AccountingRule option lets Relays set whether they'd like
8728 AccountingMax to be applied separately to inbound and outbound
8729 traffic, or applied to the sum of inbound and outbound traffic.
8730 Resolves ticket 961. Patch by "chobe".
8732 o Minor features (testing networks):
8733 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
8734 the "Exit" flag regardless of their uptime, bandwidth, or exit
8735 policy. TestingTorNetwork must be set for this option to have any
8736 effect. Previously, authorities would take up to 35 minutes to
8737 give nodes the Exit flag in a test network. Partially implements
8740 o Minor features (validation):
8741 - Check all date/time values passed to tor_timegm and
8742 parse_rfc1123_time for validity, taking leap years into account.
8743 Improves HTTP header validation. Implemented with bug 13476.
8744 - In correct_tm(), limit the range of values returned by system
8745 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
8746 This means we don't have to deal with negative or too large dates,
8747 even if a clock is wrong. Otherwise we might fail to read a file
8748 written by us which includes such a date. Fixes bug 13476.
8750 o Minor bugfixes (bridge clients):
8751 - When configured to use a bridge without an identity digest (not
8752 recommended), avoid launching an extra channel to it when
8753 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
8755 o Minor bugfixes (bridges):
8756 - When DisableNetwork is set, do not launch pluggable transport
8757 plugins, and if any are running, terminate them. Fixes bug 13213;
8758 bugfix on 0.2.3.6-alpha.
8760 o Minor bugfixes (C correctness):
8761 - Fix several instances of possible integer overflow/underflow/NaN.
8762 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
8764 - In circuit_build_times_calculate_timeout() in circuitstats.c,
8765 avoid dividing by zero in the pareto calculations. This traps
8766 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
8768 - Fix an integer overflow in format_time_interval(). Fixes bug
8769 13393; bugfix on 0.2.0.10-alpha.
8770 - Set the correct day of year value when the system's localtime(_r)
8771 or gmtime(_r) functions fail to set struct tm. Not externally
8772 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
8773 - Avoid unlikely signed integer overflow in tor_timegm on systems
8774 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
8776 o Minor bugfixes (client):
8777 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
8778 BadExit flag are not considered worthy candidates. Fixes bug
8779 13066; bugfix on 0.1.2.3-alpha.
8780 - Use the consensus schedule for downloading consensuses, and not
8781 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
8782 - Handle unsupported or malformed SOCKS5 requests properly by
8783 responding with the appropriate error message before closing the
8784 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
8786 o Minor bugfixes (client, torrc):
8787 - Stop modifying the value of our DirReqStatistics torrc option just
8788 because we're not a bridge or relay. This bug was causing Tor
8789 Browser users to write "DirReqStatistics 0" in their torrc files
8790 as if they had chosen to change the config. Fixes bug 4244; bugfix
8792 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
8793 that our options have changed every time we SIGHUP. Fixes bug
8794 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
8796 o Minor bugfixes (controller):
8797 - Return an error when the second or later arguments of the
8798 "setevents" controller command are invalid events. Previously we
8799 would return success while silently skipping invalid events. Fixes
8800 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
8802 o Minor bugfixes (directory system):
8803 - Always believe that v3 directory authorities serve extra-info
8804 documents, whether they advertise "caches-extra-info" or not.
8805 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8806 - When running as a v3 directory authority, advertise that you serve
8807 extra-info documents so that clients who want them can find them
8808 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8809 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
8810 Previously, directories offering BRIDGE_DIRINFO and some other
8811 flag (i.e. microdescriptors or extrainfo) would be ignored when
8812 looking for bridges. Partially fixes bug 13163; bugfix
8815 o Minor bugfixes (networking):
8816 - Check for orconns and use connection_or_close_for_error() rather
8817 than connection_mark_for_close() directly in the getsockopt()
8818 failure case of connection_handle_write_impl(). Fixes bug 11302;
8819 bugfix on 0.2.4.4-alpha.
8821 o Minor bugfixes (relay):
8822 - When generating our family list, remove spaces from around the
8823 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
8824 - If our previous bandwidth estimate was 0 bytes, allow publishing a
8825 new relay descriptor immediately. Fixes bug 13000; bugfix
8828 o Minor bugfixes (testing networks):
8829 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
8830 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
8831 - Stop using the default authorities in networks which provide both
8832 AlternateDirAuthority and AlternateBridgeAuthority. Partially
8833 fixes bug 13163; bugfix on 0.2.0.13-alpha.
8835 o Minor bugfixes (testing):
8836 - Stop spawn test failures due to a race condition between the
8837 SIGCHLD handler updating the process status, and the test reading
8838 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
8840 o Minor bugfixes (testing, Windows):
8841 - Avoid passing an extra backslash when creating a temporary
8842 directory for running the unit tests on Windows. Fixes bug 12392;
8843 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
8845 o Minor bugfixes (windows):
8846 - Remove code to special-case handling of NTE_BAD_KEYSET when
8847 acquiring windows CryptoAPI context. This error can't actually
8848 occur for the parameters we're providing. Fixes bug 10816; bugfix
8851 o Minor bugfixes (zlib):
8852 - Avoid truncating a zlib stream when trying to finalize it with an
8853 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
8856 - Allow our configure script to build correctly with autoconf 2.62
8857 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
8858 - Improve the error message from ./configure to make it clear that
8859 when asciidoc has not been found, the user will have to either add
8860 --disable-asciidoc argument or install asciidoc. Resolves
8863 o Code simplification and refactoring:
8864 - Change the entry_is_live() function to take named bitfield
8865 elements instead of an unnamed list of booleans. Closes
8867 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
8868 Resolves ticket 12205.
8869 - Use calloc and reallocarray functions instead of multiply-
8870 then-malloc. This makes it less likely for us to fall victim to an
8871 integer overflow attack when allocating. Resolves ticket 12855.
8872 - Use the standard macro name SIZE_MAX, instead of our
8874 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
8875 functions which take them as arguments. Replace 0 with NO_DIRINFO
8876 in a function call for clarity. Seeks to prevent future issues
8878 - Avoid 4 null pointer errors under clang static analysis by using
8879 tor_assert() to prove that the pointers aren't null. Fixes
8881 - Rework the API of policies_parse_exit_policy() to use a bitmask to
8882 represent parsing options, instead of a confusing mess of
8883 booleans. Resolves ticket 8197.
8884 - Introduce a helper function to parse ExitPolicy in
8885 or_options_t structure.
8888 - Add a doc/TUNING document with tips for handling large numbers of
8889 TCP connections when running busy Tor relay. Update the warning
8890 message to point to this file when running out of sockets
8891 operating system is allowing to use simultaneously. Resolves
8895 - We no longer remind the user about configuration options that have
8896 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
8897 - Remove our old, non-weighted bandwidth-based node selection code.
8898 Previously, we used it as a fallback when we couldn't perform
8899 weighted bandwidth-based node selection. But that would only
8900 happen in the cases where we had no consensus, or when we had a
8901 consensus generated by buggy or ancient directory authorities. In
8902 either case, it's better to use the more modern, better maintained
8903 algorithm, with reasonable defaults for the weights. Closes
8905 - Remove the --disable-curve25519 configure option. Relays and
8906 clients now are required to support curve25519 and the
8908 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
8909 used to be deprecated synonyms for "StrictNodes", are now marked
8910 obsolete. Resolves ticket 12226.
8911 - Clients don't understand the BadDirectory flag in the consensus
8912 anymore, and ignore it.
8915 - Refactor the function that chooses guard nodes so that it can more
8916 easily be tested; write some tests for it.
8917 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
8918 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
8919 - Create unit tests for format_time_interval(). With bug 13393.
8920 - Add unit tests for tor_timegm signed overflow, tor_timegm and
8921 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
8922 tests (visible) fixes in bug 13476.
8923 - Add a "coverage-html" make target to generate HTML-visualized
8924 coverage results when building with --enable-coverage. (Requires
8925 lcov.) Patch from Kevin Murray.
8926 - Enable the backtrace handler (where supported) when running the
8928 - Revise all unit tests that used the legacy test_* macros to
8929 instead use the recommended tt_* macros. This patch was generated
8930 with coccinelle, to avoid manual errors. Closes ticket 13119.
8932 o Distribution (systemd):
8933 - systemd unit file: only allow tor to write to /var/lib/tor and
8934 /var/log/tor. The rest of the filesystem is accessible for reading
8935 only. Patch by intrigeri; resolves ticket 12751.
8936 - systemd unit file: ensure that the process and all its children
8937 can never gain new privileges. Patch by intrigeri; resolves
8939 - systemd unit file: set up /var/run/tor as writable for the Tor
8940 service. Patch by intrigeri; resolves ticket 13196.
8942 o Removed features (directory authorities):
8943 - Remove code that prevented authorities from listing Tor relays
8944 affected by CVE-2011-2769 as guards. These relays are already
8945 rejected altogether due to the minimum version requirement of
8946 0.2.3.16-alpha. Closes ticket 13152.
8947 - The "AuthDirRejectUnlisted" option no longer has any effect, as
8948 the fingerprints file (approved-routers) has been deprecated.
8949 - Directory authorities do not support being Naming dirauths anymore.
8950 The "NamingAuthoritativeDir" config option is now obsolete.
8951 - Directory authorities do not support giving out the BadDirectory
8953 - Directory authorities no longer advertise or support consensus
8954 methods 1 through 12 inclusive. These consensus methods were
8955 obsolete and/or insecure: maintaining the ability to support them
8956 served no good purpose. Implements part of proposal 215; closes
8959 o Testing (test-network.sh):
8960 - Stop using "echo -n", as some shells' built-in echo doesn't
8961 support "-n". Instead, use "/bin/echo -n". Partially fixes
8963 - Stop an apparent test-network hang when used with make -j2. Fixes
8965 - Add a --delay option to test-network.sh, which configures the
8966 delay before the chutney network tests for data transmission.
8967 Partially implements ticket 13161.
8970 Changes in version 0.2.5.10 - 2014-10-24
8971 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
8973 It adds several new security features, including improved
8974 denial-of-service resistance for relays, new compiler hardening
8975 options, and a system-call sandbox for hardened installations on Linux
8976 (requires seccomp2). The controller protocol has several new features,
8977 resolving IPv6 addresses should work better than before, and relays
8978 should be a little more CPU-efficient. We've added support for more
8979 OpenBSD and FreeBSD transparent proxy types. We've improved the build
8980 system and testing infrastructure to allow unit testing of more parts
8981 of the Tor codebase. Finally, we've addressed several nagging pluggable
8982 transport usability issues, and included numerous other small bugfixes
8983 and features mentioned below.
8985 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
8986 have accumulated many known flaws; everyone should upgrade.
8988 o Deprecated versions:
8989 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
8990 attention for some while.
8993 Changes in version 0.2.5.9-rc - 2014-10-20
8994 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
8995 series. It disables SSL3 in response to the recent "POODLE" attack
8996 (even though POODLE does not affect Tor). It also works around a crash
8997 bug caused by some operating systems' response to the "POODLE" attack
8998 (which does affect Tor). It also contains a few miscellaneous fixes.
9000 o Major security fixes:
9001 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9002 today support TLS 1.0 or later, so we can safely turn off support
9003 for this old (and insecure) protocol. Fixes bug 13426.
9005 o Major bugfixes (openssl bug workaround):
9006 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9007 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9008 13471. This is a workaround for an OpenSSL bug.
9011 - Disable the sandbox name resolver cache when running tor-resolve:
9012 tor-resolve doesn't use the sandbox code, and turning it on was
9013 breaking attempts to do tor-resolve on a non-default server on
9014 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
9016 o Compilation fixes:
9017 - Build and run correctly on systems like OpenBSD-current that have
9018 patched OpenSSL to remove get_cipher_by_char and/or its
9019 implementations. Fixes issue 13325.
9021 o Downgraded warnings:
9022 - Downgrade the severity of the 'unexpected sendme cell from client'
9023 from 'warn' to 'protocol warning'. Closes ticket 8093.
9026 Changes in version 0.2.4.25 - 2014-10-20
9027 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
9028 (even though POODLE does not affect Tor). It also works around a crash
9029 bug caused by some operating systems' response to the "POODLE" attack
9030 (which does affect Tor).
9032 o Major security fixes (also in 0.2.5.9-rc):
9033 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9034 today support TLS 1.0 or later, so we can safely turn off support
9035 for this old (and insecure) protocol. Fixes bug 13426.
9037 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
9038 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9039 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9040 13471. This is a workaround for an OpenSSL bug.
9043 Changes in version 0.2.5.8-rc - 2014-09-22
9044 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
9045 series. It fixes a bug that affects consistency and speed when
9046 connecting to hidden services, and it updates the location of one of
9047 the directory authorities.
9050 - Clients now send the correct address for their chosen rendezvous
9051 point when trying to access a hidden service. They used to send
9052 the wrong address, which would still work some of the time because
9053 they also sent the identity digest of the rendezvous point, and if
9054 the hidden service happened to try connecting to the rendezvous
9055 point from a relay that already had a connection open to it,
9056 the relay would reuse that connection. Now connections to hidden
9057 services should be more robust and faster. Also, this bug meant
9058 that clients were leaking to the hidden service whether they were
9059 on a little-endian (common) or big-endian (rare) system, which for
9060 some users might have reduced their anonymity. Fixes bug 13151;
9061 bugfix on 0.2.1.5-alpha.
9063 o Directory authority changes:
9064 - Change IP address for gabelmoo (v3 directory authority).
9067 Changes in version 0.2.4.24 - 2014-09-22
9068 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
9069 connecting to hidden services, and it updates the location of one of
9070 the directory authorities.
9073 - Clients now send the correct address for their chosen rendezvous
9074 point when trying to access a hidden service. They used to send
9075 the wrong address, which would still work some of the time because
9076 they also sent the identity digest of the rendezvous point, and if
9077 the hidden service happened to try connecting to the rendezvous
9078 point from a relay that already had a connection open to it,
9079 the relay would reuse that connection. Now connections to hidden
9080 services should be more robust and faster. Also, this bug meant
9081 that clients were leaking to the hidden service whether they were
9082 on a little-endian (common) or big-endian (rare) system, which for
9083 some users might have reduced their anonymity. Fixes bug 13151;
9084 bugfix on 0.2.1.5-alpha.
9086 o Directory authority changes:
9087 - Change IP address for gabelmoo (v3 directory authority).
9089 o Minor features (geoip):
9090 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9094 Changes in version 0.2.5.7-rc - 2014-09-11
9095 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
9096 release series, and some long-standing bugs related to ORPort reachability
9097 testing and failure to send CREATE cells. It is the first release
9098 candidate for the Tor 0.2.5.x series.
9100 o Major bugfixes (client, startup):
9101 - Start making circuits as soon as DisabledNetwork is turned off.
9102 When Tor started with DisabledNetwork set, it would correctly
9103 conclude that it shouldn't build circuits, but it would mistakenly
9104 cache this conclusion, and continue believing it even when
9105 DisableNetwork is set to 0. Fixes the bug introduced by the fix
9106 for bug 11200; bugfix on 0.2.5.4-alpha.
9107 - Resume expanding abbreviations for command-line options. The fix
9108 for bug 4647 accidentally removed our hack from bug 586 that
9109 rewrote HashedControlPassword to __HashedControlSessionPassword
9110 when it appears on the commandline (which allowed the user to set
9111 her own HashedControlPassword in the torrc file while the
9112 controller generates a fresh session password for each run). Fixes
9113 bug 12948; bugfix on 0.2.5.1-alpha.
9114 - Warn about attempts to run hidden services and relays in the same
9115 process: that's probably not a good idea. Closes ticket 12908.
9117 o Major bugfixes (relay):
9118 - Avoid queuing or sending destroy cells for circuit ID zero when we
9119 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
9120 Found and fixed by "cypherpunks".
9121 - Fix ORPort reachability detection on relays running behind a
9122 proxy, by correctly updating the "local" mark on the controlling
9123 channel when changing the address of an or_connection_t after the
9124 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
9126 o Minor features (bridge):
9127 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
9128 cookie file for the ExtORPort g+r by default.
9130 o Minor features (geoip):
9131 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9134 o Minor bugfixes (logging):
9135 - Reduce the log severity of the "Pluggable transport proxy does not
9136 provide any needed transports and will not be launched." message,
9137 since Tor Browser includes several ClientTransportPlugin lines in
9138 its torrc-defaults file, leading every Tor Browser user who looks
9139 at her logs to see these notices and wonder if they're dangerous.
9140 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
9141 - Downgrade "Unexpected onionskin length after decryption" warning
9142 to a protocol-warn, since there's nothing relay operators can do
9143 about a client that sends them a malformed create cell. Resolves
9144 bug 12996; bugfix on 0.0.6rc1.
9145 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
9146 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
9147 - When logging information about an EXTEND2 or EXTENDED2 cell, log
9148 their names correctly. Fixes part of bug 12700; bugfix
9150 - When logging information about a relay cell whose command we don't
9151 recognize, log its command as an integer. Fixes part of bug 12700;
9152 bugfix on 0.2.1.10-alpha.
9153 - Escape all strings from the directory connection before logging
9154 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
9156 o Minor bugfixes (controller):
9157 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
9158 bug 12864; bugfix on 0.2.5.1-alpha.
9159 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
9160 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
9163 o Minor bugfixes (compilation):
9164 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
9165 bugfix on 0.2.5.5-alpha.
9166 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
9167 0.2.5.1-alpha. Patch from "NewEraCracker".
9168 - In routerlist_assert_ok(), don't take the address of a
9169 routerinfo's cache_info member unless that routerinfo is non-NULL.
9170 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
9171 - Fix a large number of false positive warnings from the clang
9172 analyzer static analysis tool. This should make real warnings
9173 easier for clang analyzer to find. Patch from "teor". Closes
9176 o Distribution (systemd):
9177 - Verify configuration file via ExecStartPre in the systemd unit
9178 file. Patch from intrigeri; resolves ticket 12730.
9179 - Explicitly disable RunAsDaemon in the systemd unit file. Our
9180 current systemd unit uses "Type = simple", so systemd does not
9181 expect tor to fork. If the user has "RunAsDaemon 1" in their
9182 torrc, then things won't work as expected. This is e.g. the case
9183 on Debian (and derivatives), since there we pass "--defaults-torrc
9184 /usr/share/tor/tor-service-defaults-torrc" (that contains
9185 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
9189 - Adjust the URLs in the README to refer to the new locations of
9190 several documents on the website. Fixes bug 12830. Patch from
9192 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
9196 Changes in version 0.2.5.6-alpha - 2014-07-28
9197 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
9198 risk from guard rotation, and fixes a variety of other issues to get
9199 us closer to a release candidate.
9201 o Major features (also in 0.2.4.23):
9202 - Make the number of entry guards configurable via a new
9203 NumEntryGuards consensus parameter, and the number of directory
9204 guards configurable via a new NumDirectoryGuards consensus
9205 parameter. Implements ticket 12688.
9207 o Major bugfixes (also in 0.2.4.23):
9208 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
9209 implementation that caused incorrect results on 32-bit
9210 implementations when certain malformed inputs were used along with
9211 a small class of private ntor keys. This bug does not currently
9212 appear to allow an attacker to learn private keys or impersonate a
9213 Tor server, but it could provide a means to distinguish 32-bit Tor
9214 implementations from 64-bit Tor implementations. Fixes bug 12694;
9215 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
9219 - Perform circuit cleanup operations even when circuit
9220 construction operations are disabled (because the network is
9221 disabled, or because there isn't enough directory information).
9222 Previously, when we were not building predictive circuits, we
9223 were not closing expired circuits either. Fixes bug 8387; bugfix on
9224 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
9225 became more strict about when we have "enough directory information
9229 - Authorities now assign the Guard flag to the fastest 25% of the
9230 network (it used to be the fastest 50%). Also raise the consensus
9231 weight that guarantees the Guard flag from 250 to 2000. For the
9232 current network, this results in about 1100 guards, down from 2500.
9233 This step paves the way for moving the number of entry guards
9234 down to 1 (proposal 236) while still providing reasonable expected
9235 performance for most users. Implements ticket 12690.
9236 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
9238 - Slightly enhance the diagnostic message for bug 12184.
9240 o Minor bugfixes (also in 0.2.4.23):
9241 - Warn and drop the circuit if we receive an inbound 'relay early'
9242 cell. Those used to be normal to receive on hidden service circuits
9243 due to bug 1038, but the buggy Tor versions are long gone from
9244 the network so we can afford to resume watching for them. Resolves
9245 the rest of bug 1038; bugfix on 0.2.1.19.
9246 - Correct a confusing error message when trying to extend a circuit
9247 via the control protocol but we don't know a descriptor or
9248 microdescriptor for one of the specified relays. Fixes bug 12718;
9249 bugfix on 0.2.3.1-alpha.
9252 - Fix compilation when building with bufferevents enabled. (This
9253 configuration is still not expected to work, however.)
9254 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
9255 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
9257 - Compile correctly with builds and forks of OpenSSL (such as
9258 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
9259 0.2.1.1-alpha. Patch from "dhill".
9262 Changes in version 0.2.4.23 - 2014-07-28
9263 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
9264 guard rotation, and also backports several important fixes from the
9265 Tor 0.2.5 alpha release series.
9268 - Clients now look at the "usecreatefast" consensus parameter to
9269 decide whether to use CREATE_FAST or CREATE cells for the first hop
9270 of their circuit. This approach can improve security on connections
9271 where Tor's circuit handshake is stronger than the available TLS
9272 connection security levels, but the tradeoff is more computational
9273 load on guard relays. Implements proposal 221. Resolves ticket 9386.
9274 - Make the number of entry guards configurable via a new
9275 NumEntryGuards consensus parameter, and the number of directory
9276 guards configurable via a new NumDirectoryGuards consensus
9277 parameter. Implements ticket 12688.
9280 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
9281 implementation that caused incorrect results on 32-bit
9282 implementations when certain malformed inputs were used along with
9283 a small class of private ntor keys. This bug does not currently
9284 appear to allow an attacker to learn private keys or impersonate a
9285 Tor server, but it could provide a means to distinguish 32-bit Tor
9286 implementations from 64-bit Tor implementations. Fixes bug 12694;
9287 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
9291 - Warn and drop the circuit if we receive an inbound 'relay early'
9292 cell. Those used to be normal to receive on hidden service circuits
9293 due to bug 1038, but the buggy Tor versions are long gone from
9294 the network so we can afford to resume watching for them. Resolves
9295 the rest of bug 1038; bugfix on 0.2.1.19.
9296 - Correct a confusing error message when trying to extend a circuit
9297 via the control protocol but we don't know a descriptor or
9298 microdescriptor for one of the specified relays. Fixes bug 12718;
9299 bugfix on 0.2.3.1-alpha.
9300 - Avoid an illegal read from stack when initializing the TLS
9301 module using a version of OpenSSL without all of the ciphers
9302 used by the v2 link handshake. Fixes bug 12227; bugfix on
9303 0.2.4.8-alpha. Found by "starlight".
9306 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
9310 Changes in version 0.2.5.5-alpha - 2014-06-18
9311 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
9312 0.2.5.x release series, including a couple of DoS issues, some
9313 performance regressions, a large number of bugs affecting the Linux
9314 seccomp2 sandbox code, and various other bugfixes. It also adds
9315 diagnostic bugfixes for a few tricky issues that we're trying to
9318 o Major features (security, traffic analysis resistance):
9319 - Several major improvements to the algorithm used to decide when to
9320 close TLS connections. Previous versions of Tor closed connections
9321 at a fixed interval after the last time a non-padding cell was
9322 sent over the connection, regardless of the target of the
9323 connection. Now, we randomize the intervals by adding up to 50% of
9324 their base value, we measure the length of time since connection
9325 last had at least one circuit, and we allow connections to known
9326 ORs to remain open a little longer (15 minutes instead of 3
9327 minutes minimum). These changes should improve Tor's resistance
9328 against some kinds of traffic analysis, and lower some overhead
9329 from needlessly closed connections. Fixes ticket 6799.
9330 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
9332 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
9333 - Fix a memory leak that could occur if a microdescriptor parse
9334 fails during the tokenizing step. This bug could enable a memory
9335 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9338 o Major bugfixes (security, directory authorities):
9339 - Directory authorities now include a digest of each relay's
9340 identity key as a part of its microdescriptor.
9342 This is a workaround for bug 11743 (reported by "cypherpunks"),
9343 where Tor clients do not support receiving multiple
9344 microdescriptors with the same SHA256 digest in the same
9345 consensus. When clients receive a consensus like this, they only
9346 use one of the relays. Without this fix, a hostile relay could
9347 selectively disable some client use of target relays by
9348 constructing a router descriptor with a different identity and the
9349 same microdescriptor parameters and getting the authorities to
9350 list it in a microdescriptor consensus. This fix prevents an
9351 attacker from causing a microdescriptor collision, because the
9352 router's identity is not forgeable.
9354 o Major bugfixes (relay):
9355 - Use a direct dirport connection when uploading non-anonymous
9356 descriptors to the directory authorities. Previously, relays would
9357 incorrectly use tunnel connections under a fairly wide variety of
9358 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
9359 - When a circuit accidentally has the same circuit ID for its
9360 forward and reverse direction, correctly detect the direction of
9361 cells using that circuit. Previously, this bug made roughly one
9362 circuit in a million non-functional. Fixes bug 12195; this is a
9363 bugfix on every version of Tor.
9365 o Major bugfixes (client, pluggable transports):
9366 - When managing pluggable transports, use OS notification facilities
9367 to learn if they have crashed, and don't attempt to kill any
9368 process that has already exited. Fixes bug 8746; bugfix
9371 o Minor features (diagnostic):
9372 - When logging a warning because of bug 7164, additionally check the
9373 hash table for consistency (as proposed on ticket 11737). This may
9374 help diagnose bug 7164.
9375 - When we log a heartbeat, log how many one-hop circuits we have
9376 that are at least 30 minutes old, and log status information about
9377 a few of them. This is an attempt to track down bug 8387.
9378 - When encountering an unexpected CR while writing text to a file on
9379 Windows, log the name of the file. Should help diagnosing
9381 - Give more specific warnings when a client notices that an onion
9382 handshake has failed. Fixes ticket 9635.
9383 - Add significant new logging code to attempt to diagnose bug 12184,
9384 where relays seem to run out of available circuit IDs.
9385 - Improve the diagnostic log message for bug 8387 even further to
9386 try to improve our odds of figuring out why one-hop directory
9387 circuits sometimes do not get closed.
9389 o Minor features (security, memory management):
9390 - Memory allocation tricks (mempools and buffer freelists) are now
9391 disabled by default. You can turn them back on with
9392 --enable-mempools and --enable-buf-freelists respectively. We're
9393 disabling these features because malloc performance is good enough
9394 on most platforms, and a similar feature in OpenSSL exacerbated
9395 exploitation of the Heartbleed attack. Resolves ticket 11476.
9397 o Minor features (security):
9398 - Apply the secure SipHash-2-4 function to the hash table mapping
9399 circuit IDs and channels to circuits. We missed this one when we
9400 were converting all the other hash functions to use SipHash back
9401 in 0.2.5.3-alpha. Resolves ticket 11750.
9403 o Minor features (build):
9404 - The configure script has a --disable-seccomp option to turn off
9405 support for libseccomp on systems that have it, in case it (or
9406 Tor's use of it) is broken. Resolves ticket 11628.
9408 o Minor features (other):
9409 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
9412 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
9413 - When running a hidden service, do not allow TunneledDirConns 0;
9414 this will keep the hidden service from running, and also
9415 make it publish its descriptors directly over HTTP. Fixes bug 10849;
9416 bugfix on 0.2.1.1-alpha.
9418 o Minor bugfixes (performance):
9419 - Avoid a bug where every successful connection made us recompute
9420 the flag telling us whether we have sufficient information to
9421 build circuits. Previously, we would forget our cached value
9422 whenever we successfully opened a channel (or marked a router as
9423 running or not running for any other reason), regardless of
9424 whether we had previously believed the router to be running. This
9425 forced us to run an expensive update operation far too often.
9426 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
9427 - Avoid using tor_memeq() for checking relay cell integrity. This
9428 removes a possible performance bottleneck. Fixes part of bug
9429 12169; bugfix on 0.2.1.31.
9431 o Minor bugfixes (compilation):
9432 - Fix compilation of test_status.c when building with MVSC. Bugfix
9433 on 0.2.5.4-alpha. Patch from Gisle Vanem.
9434 - Resolve GCC complaints on OpenBSD about discarding constness in
9435 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
9436 on 0.1.1.23. Patch from Dana Koch.
9437 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
9438 treatment of long and time_t as comparable types. Fixes part of
9439 bug 11633. Patch from Dana Koch.
9440 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
9441 11623; bugfix on 0.2.5.3-alpha.
9442 - When deciding whether to build the 64-bit curve25519
9443 implementation, detect platforms where we can compile 128-bit
9444 arithmetic but cannot link it. Fixes bug 11729; bugfix on
9445 0.2.4.8-alpha. Patch from "conradev".
9446 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
9447 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
9448 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
9451 o Minor bugfixes (Directory server):
9452 - When sending a compressed set of descriptors or microdescriptors,
9453 make sure to finalize the zlib stream. Previously, we would write
9454 all the compressed data, but if the last descriptor we wanted to
9455 send was missing or too old, we would not mark the stream as
9456 finished. This caused problems for decompression tools. Fixes bug
9457 11648; bugfix on 0.1.1.23.
9459 o Minor bugfixes (Linux seccomp sandbox):
9460 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
9461 11622; bugfix on 0.2.5.1-alpha.
9462 - Avoid crashing when re-opening listener ports with the seccomp
9463 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
9464 - Avoid crashing with the seccomp sandbox enabled along with
9465 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
9466 - When we receive a SIGHUP with the sandbox enabled, correctly
9467 support rotating our log files. Fixes bug 12032; bugfix
9469 - Avoid crash when running with sandboxing enabled and
9470 DirReqStatistics not disabled. Fixes bug 12035; bugfix
9472 - Fix a "BUG" warning when trying to write bridge-stats files with
9473 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
9475 - Prevent the sandbox from crashing on startup when run with the
9476 --enable-expensive-hardening configuration option. Fixes bug
9477 11477; bugfix on 0.2.5.4-alpha.
9478 - When running with DirPortFrontPage and sandboxing both enabled,
9479 reload the DirPortFrontPage correctly when restarting. Fixes bug
9480 12028; bugfix on 0.2.5.1-alpha.
9481 - Don't try to enable the sandbox when using the Tor binary to check
9482 its configuration, hash a passphrase, or so on. Doing so was
9483 crashing on startup for some users. Fixes bug 11609; bugfix
9485 - Avoid warnings when running with sandboxing and node statistics
9486 enabled at the same time. Fixes part of 12064; bugfix on
9487 0.2.5.1-alpha. Patch from Michael Wolf.
9488 - Avoid warnings when running with sandboxing enabled at the same
9489 time as cookie authentication, hidden services, or directory
9490 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
9491 - Do not allow options that require calls to exec to be enabled
9492 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
9493 bug 12043; bugfix on 0.2.5.1-alpha.
9494 - Handle failures in getpwnam()/getpwuid() when running with the
9495 User option set and the Linux syscall sandbox enabled. Fixes bug
9496 11946; bugfix on 0.2.5.1-alpha.
9497 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
9498 to avoid calling getaddrinfo() after installing the sandbox
9499 filters. Previously, it preloaded a cache with the IPv4 address
9500 for our hostname, and nothing else. Now, it loads the cache with
9501 every address that it used to initialize the Tor process. Fixes
9502 bug 11970; bugfix on 0.2.5.1-alpha.
9504 o Minor bugfixes (pluggable transports):
9505 - Enable the ExtORPortCookieAuthFile option, to allow changing the
9506 default location of the authentication token for the extended OR
9507 Port as used by sever-side pluggable transports. We had
9508 implemented this option before, but the code to make it settable
9509 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
9510 - Avoid another 60-second delay when starting Tor in a pluggable-
9511 transport-using configuration when we already have cached
9512 descriptors for our bridges. Fixes bug 11965; bugfix
9515 o Minor bugfixes (client):
9516 - Avoid "Tried to open a socket with DisableNetwork set" warnings
9517 when starting a client with bridges configured and DisableNetwork
9518 set. (Tor launcher starts Tor with DisableNetwork set the first
9519 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
9521 o Minor bugfixes (testing):
9522 - The Python parts of the test scripts now work on Python 3 as well
9523 as Python 2, so systems where '/usr/bin/python' is Python 3 will
9524 no longer have the tests break. Fixes bug 11608; bugfix
9526 - When looking for versions of python that we could run the tests
9527 with, check for "python2.7" and "python3.3"; previously we were
9528 only looking for "python", "python2", and "python3". Patch from
9529 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
9530 - Fix all valgrind warnings produced by the unit tests. There were
9531 over a thousand memory leak warnings previously, mostly produced
9532 by forgetting to free things in the unit test code. Fixes bug
9533 11618, bugfixes on many versions of Tor.
9535 o Minor bugfixes (tor-fw-helper):
9536 - Give a correct log message when tor-fw-helper fails to launch.
9537 (Previously, we would say something like "tor-fw-helper sent us a
9538 string we could not parse".) Fixes bug 9781; bugfix
9541 o Minor bugfixes (relay, threading):
9542 - Check return code on spawn_func() in cpuworker code, so that we
9543 don't think we've spawned a nonworking cpuworker and write junk to
9544 it forever. Fix related to bug 4345; bugfix on all released Tor
9545 versions. Found by "skruffy".
9546 - Use a pthread_attr to make sure that spawn_func() cannot return an
9547 error while at the same time launching a thread. Fix related to
9548 bug 4345; bugfix on all released Tor versions. Reported
9551 o Minor bugfixes (relay, oom prevention):
9552 - Correctly detect the total available system memory. We tried to do
9553 this in 0.2.5.4-alpha, but the code was set up to always return an
9554 error value, even on success. Fixes bug 11805; bugfix
9557 o Minor bugfixes (relay, other):
9558 - We now drop CREATE cells for already-existent circuit IDs and for
9559 zero-valued circuit IDs, regardless of other factors that might
9560 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
9562 - Avoid an illegal read from stack when initializing the TLS module
9563 using a version of OpenSSL without all of the ciphers used by the
9564 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
9566 - When rejecting DATA cells for stream_id zero, still count them
9567 against the circuit's deliver window so that we don't fail to send
9568 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
9570 o Minor bugfixes (logging):
9571 - Fix a misformatted log message about delayed directory fetches.
9572 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
9573 - Squelch a spurious LD_BUG message "No origin circuit for
9574 successful SOCKS stream" in certain hidden service failure cases;
9578 - Include a tor.service file in contrib/dist for use with systemd.
9579 Some distributions will be able to use this file unmodified;
9580 others will need to tweak it, or write their own. Patch from Jamie
9581 Nguyen; resolves ticket 8368.
9584 - Clean up several option names in the manpage to match their real
9585 names, add the missing documentation for a couple of testing and
9586 directory authority options, remove the documentation for a
9587 V2-directory fetching option that no longer exists. Resolves
9589 - Correct the documenation so that it lists the correct directory
9590 for the stats files. (They are in a subdirectory called "stats",
9592 - In the manpage, move more authority-only options into the
9593 directory authority section so that operators of regular directory
9594 caches don't get confused.
9597 - The contrib directory has been sorted and tidied. Before, it was
9598 an unsorted dumping ground for useful and not-so-useful things.
9599 Now, it is divided based on functionality, and the items which
9600 seemed to be nonfunctional or useless have been removed. Resolves
9601 ticket 8966; based on patches from "rl1987".
9604 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
9605 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
9606 - The TunnelDirConns and PreferTunnelledDirConns options no longer
9607 exist; tunneled directory connections have been available since
9608 0.1.2.5-alpha, and turning them off is not a good idea. This is a
9609 brute-force fix for 10849, where "TunnelDirConns 0" would break
9613 Changes in version 0.2.4.22 - 2014-05-16
9614 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
9615 alpha release series. These include blocking all authority signing
9616 keys that may have been affected by the OpenSSL "heartbleed" bug,
9617 choosing a far more secure set of TLS ciphersuites by default, closing
9618 a couple of memory leaks that could be used to run a target relay out
9619 of RAM, and several others.
9621 o Major features (security, backport from 0.2.5.4-alpha):
9622 - Block authority signing keys that were used on authorities
9623 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9624 don't have any evidence that these keys _were_ compromised; we're
9625 doing this to be prudent.) Resolves ticket 11464.
9627 o Major bugfixes (security, OOM):
9628 - Fix a memory leak that could occur if a microdescriptor parse
9629 fails during the tokenizing step. This bug could enable a memory
9630 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9633 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
9634 - The relay ciphersuite list is now generated automatically based on
9635 uniform criteria, and includes all OpenSSL ciphersuites with
9636 acceptable strength and forward secrecy. Previously, we had left
9637 some perfectly fine ciphersuites unsupported due to omission or
9638 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9639 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9640 - Relays now trust themselves to have a better view than clients of
9641 which TLS ciphersuites are better than others. (Thanks to bug
9642 11513, the relay list is now well-considered, whereas the client
9643 list has been chosen mainly for anti-fingerprinting purposes.)
9644 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9645 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9646 AES128. Resolves ticket 11528.
9647 - Clients now try to advertise the same list of ciphersuites as
9648 Firefox 28. This change enables selection of (fast) GCM
9649 ciphersuites, disables some strange old ciphers, and stops
9650 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9651 Resolves ticket 11438.
9653 o Minor bugfixes (configuration, security):
9654 - When running a hidden service, do not allow TunneledDirConns 0:
9655 trying to set that option together with a hidden service would
9656 otherwise prevent the hidden service from running, and also make
9657 it publish its descriptors directly over HTTP. Fixes bug 10849;
9658 bugfix on 0.2.1.1-alpha.
9660 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
9661 - Avoid sending a garbage value to the controller when a circuit is
9662 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9664 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
9665 - Stop leaking memory when we successfully resolve a PTR record.
9666 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9668 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
9669 - Avoid 60-second delays in the bootstrapping process when Tor is
9670 launching for a second time while using bridges. Fixes bug 9229;
9671 bugfix on 0.2.0.3-alpha.
9673 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
9674 - Give the correct URL in the warning message when trying to run a
9675 relay on an ancient version of Windows. Fixes bug 9393.
9677 o Minor bugfixes (compilation):
9678 - Fix a compilation error when compiling with --disable-curve25519.
9679 Fixes bug 9700; bugfix on 0.2.4.17-rc.
9682 - Downgrade the warning severity for the the "md was still
9683 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
9684 for trying to diagnose this bug, and the current warning in
9685 earlier versions of tor achieves nothing useful. Addresses warning
9688 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
9689 - When we run out of usable circuit IDs on a channel, log only one
9690 warning for the whole channel, and describe how many circuits
9691 there were on the channel. Fixes part of ticket 11553.
9693 o Minor features (security, backport from 0.2.5.4-alpha):
9694 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
9695 leave the default at 8GBytes), to better support Raspberry Pi
9696 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
9698 o Documentation (backport from 0.2.5.4-alpha):
9699 - Correctly document that we search for a system torrc file before
9700 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
9704 Changes in version 0.2.5.4-alpha - 2014-04-25
9705 Tor 0.2.5.4-alpha includes several security and performance
9706 improvements for clients and relays, including blacklisting authority
9707 signing keys that were used while susceptible to the OpenSSL
9708 "heartbleed" bug, fixing two expensive functions on busy relays,
9709 improved TLS ciphersuite preference lists, support for run-time
9710 hardening on compilers that support AddressSanitizer, and more work on
9711 the Linux sandbox code.
9713 There are also several usability fixes for clients (especially clients
9714 that use bridges), two new TransPort protocols supported (one on
9715 OpenBSD, one on FreeBSD), and various other bugfixes.
9717 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
9718 have accumulated many known flaws; everyone should upgrade.
9720 o Major features (security):
9721 - If you don't specify MaxMemInQueues yourself, Tor now tries to
9722 pick a good value based on your total system memory. Previously,
9723 the default was always 8 GB. You can still override the default by
9724 setting MaxMemInQueues yourself. Resolves ticket 11396.
9725 - Block authority signing keys that were used on authorities
9726 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9727 don't have any evidence that these keys _were_ compromised; we're
9728 doing this to be prudent.) Resolves ticket 11464.
9730 o Major features (relay performance):
9731 - Speed up server-side lookups of rendezvous and introduction point
9732 circuits by using hashtables instead of linear searches. These
9733 functions previously accounted between 3 and 7% of CPU usage on
9734 some busy relays. Resolves ticket 9841.
9735 - Avoid wasting CPU when extending a circuit over a channel that is
9736 nearly out of circuit IDs. Previously, we would do a linear scan
9737 over possible circuit IDs before finding one or deciding that we
9738 had exhausted our possibilities. Now, we try at most 64 random
9739 circuit IDs before deciding that we probably won't succeed. Fixes
9740 a possible root cause of ticket 11553.
9742 o Major features (seccomp2 sandbox, Linux only):
9743 - The seccomp2 sandbox can now run a test network for multiple hours
9744 without crashing. The sandbox is still experimental, and more bugs
9745 will probably turn up. To try it, enable "Sandbox 1" on a Linux
9746 host. Resolves ticket 11351.
9747 - Strengthen sandbox code: the sandbox can now test the arguments
9748 for rename(), and blocks _sysctl() entirely. Resolves another part
9750 - When the sandbox blocks a system call, it now tries to log a stack
9751 trace before exiting. Resolves ticket 11465.
9753 o Major bugfixes (TLS cipher selection):
9754 - The relay ciphersuite list is now generated automatically based on
9755 uniform criteria, and includes all OpenSSL ciphersuites with
9756 acceptable strength and forward secrecy. Previously, we had left
9757 some perfectly fine ciphersuites unsupported due to omission or
9758 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9759 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9760 - Relays now trust themselves to have a better view than clients of
9761 which TLS ciphersuites are better than others. (Thanks to bug
9762 11513, the relay list is now well-considered, whereas the client
9763 list has been chosen mainly for anti-fingerprinting purposes.)
9764 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9765 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9766 AES128. Resolves ticket 11528.
9767 - Clients now try to advertise the same list of ciphersuites as
9768 Firefox 28. This change enables selection of (fast) GCM
9769 ciphersuites, disables some strange old ciphers, and stops
9770 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9771 Resolves ticket 11438.
9773 o Major bugfixes (bridge client):
9774 - Avoid 60-second delays in the bootstrapping process when Tor is
9775 launching for a second time while using bridges. Fixes bug 9229;
9776 bugfix on 0.2.0.3-alpha.
9778 o Minor features (transparent proxy, *BSD):
9779 - Support FreeBSD's ipfw firewall interface for TransPort ports on
9780 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
9781 10267; patch from "yurivict".
9782 - Support OpenBSD's divert-to rules with the pf firewall for
9783 transparent proxy ports. To enable it, set "TransProxyType
9784 pf-divert". This allows Tor to run a TransPort transparent proxy
9785 port on OpenBSD 4.4 or later without root privileges. See the
9786 pf.conf(5) manual page for information on configuring pf to use
9787 divert-to rules. Closes ticket 10896; patch from Dana Koch.
9789 o Minor features (security):
9790 - New --enable-expensive-hardening option to enable security
9791 hardening options that consume nontrivial amounts of CPU and
9792 memory. Right now, this includes AddressSanitizer and UbSan, which
9793 are supported in newer versions of GCC and Clang. Closes ticket
9796 o Minor features (log verbosity):
9797 - Demote the message that we give when a flushing connection times
9798 out for too long from NOTICE to INFO. It was usually meaningless.
9799 Resolves ticket 5286.
9800 - Don't log so many notice-level bootstrapping messages at startup
9801 about downloading descriptors. Previously, we'd log a notice
9802 whenever we learned about more routers. Now, we only log a notice
9803 at every 5% of progress. Fixes bug 9963.
9804 - Warn less verbosely when receiving a malformed
9805 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
9806 - When we run out of usable circuit IDs on a channel, log only one
9807 warning for the whole channel, and describe how many circuits
9808 there were on the channel. Fixes part of ticket 11553.
9810 o Minor features (relay):
9811 - If a circuit timed out for at least 3 minutes, check if we have a
9812 new external IP address, and publish a new descriptor with the new
9813 IP address if it changed. Resolves ticket 2454.
9815 o Minor features (controller):
9816 - Make the entire exit policy available from the control port via
9817 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
9819 - Because of the fix for ticket 11396, the real limit for memory
9820 usage may no longer match the configured MaxMemInQueues value. The
9821 real limit is now exposed via GETINFO limits/max-mem-in-queues.
9823 o Minor features (bridge client):
9824 - Report a more useful failure message when we can't connect to a
9825 bridge because we don't have the right pluggable transport
9826 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
9828 o Minor features (diagnostic):
9829 - Add more log messages to diagnose bug 7164, which causes
9830 intermittent "microdesc_free() called but md was still referenced"
9831 warnings. We now include more information, to figure out why we
9832 might be cleaning a microdescriptor for being too old if it's
9833 still referenced by a live node_t object.
9835 o Minor bugfixes (client, DNSPort):
9836 - When using DNSPort, try to respond to AAAA requests with AAAA
9837 answers. Previously, we hadn't looked at the request type when
9838 deciding which answer type to prefer. Fixes bug 10468; bugfix on
9840 - When receiving a DNS query for an unsupported record type, reply
9841 with no answer rather than with a NOTIMPL error. This behavior
9842 isn't correct either, but it will break fewer client programs, we
9843 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
9846 o Minor bugfixes (exit relay):
9847 - Stop leaking memory when we successfully resolve a PTR record.
9848 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9850 o Minor bugfixes (bridge client):
9851 - Stop accepting bridge lines containing hostnames. Doing so would
9852 cause clients to perform DNS requests on the hostnames, which was
9853 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
9854 - Avoid a 60-second delay in the bootstrapping process when a Tor
9855 client with pluggable transports re-reads its configuration at
9856 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
9858 o Minor bugfixes (client, logging during bootstrap):
9859 - Warn only once if we start logging in an unsafe way. Previously,
9860 we complain as many times as we had problems. Fixes bug 9870;
9861 bugfix on 0.2.5.1-alpha.
9862 - Only report the first fatal bootstrap error on a given OR
9863 connection. This stops us from telling the controller bogus error
9864 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
9865 - Be more helpful when trying to run sandboxed on Linux without
9866 libseccomp. Instead of saying "Sandbox is not implemented on this
9867 platform", we now explain that we need to be built with
9868 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
9869 - Avoid generating spurious warnings when starting with
9870 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
9873 o Minor bugfixes (closing OR connections):
9874 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
9875 check if it's an or_connection_t and correctly call
9876 connection_or_close_for_error() rather than
9877 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
9879 - When closing all connections on setting DisableNetwork to 1, use
9880 connection_or_close_normally() rather than closing OR connections
9881 out from under the channel layer. Fixes bug 11306; bugfix on
9884 o Minor bugfixes (controller):
9885 - Avoid sending a garbage value to the controller when a circuit is
9886 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9888 o Minor bugfixes (tor-fw-helper):
9889 - Allow tor-fw-helper to build again by adding src/ext to its
9890 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
9892 o Minor bugfixes (bridges):
9893 - Avoid potential crashes or bad behavior when launching a
9894 server-side managed proxy with ORPort or ExtORPort temporarily
9895 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
9897 o Minor bugfixes (platform-specific):
9898 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
9899 bug 11426; bugfix on 0.2.5.3-alpha.
9900 - When dumping a malformed directory object to disk, save it in
9901 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
9903 - Don't report failures from make_socket_reuseable() on incoming
9904 sockets on OSX: this can happen when incoming connections close
9905 early. Fixes bug 10081.
9907 o Minor bugfixes (trivial memory leaks):
9908 - Fix a small memory leak when signing a directory object. Fixes bug
9909 11275; bugfix on 0.2.4.13-alpha.
9910 - Free placeholder entries in our circuit table at exit; fixes a
9911 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
9912 - Don't re-initialize a second set of OpenSSL mutexes when starting
9913 up. Previously, we'd make one set of mutexes, and then immediately
9914 replace them with another. Fixes bug 11726; bugfix on
9916 - Resolve some memory leaks found by coverity in the unit tests, on
9917 exit in tor-gencert, and on a failure to compute digests for our
9918 own keys when generating a v3 networkstatus vote. These leaks
9919 should never have affected anyone in practice.
9921 o Minor bugfixes (hidden service):
9922 - Only retry attempts to connect to a chosen rendezvous point 8
9923 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
9925 o Minor bugfixes (misc code correctness):
9926 - Fix various instances of undefined behavior in channeltls.c,
9927 tor_memmem(), and eventdns.c that would cause us to construct
9928 pointers to memory outside an allocated object. (These invalid
9929 pointers were not accessed, but C does not even allow them to
9930 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
9931 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
9932 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
9933 fix some miscellaneous errors in our tests and codebase. Fixes bug
9934 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
9935 - Always check return values for unlink, munmap, UnmapViewOfFile;
9936 check strftime return values more often. In some cases all we can
9937 do is report a warning, but this may help prevent deeper bugs from
9938 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
9940 - Fix numerous warnings from the clang "scan-build" static analyzer.
9941 Some of these are programming style issues; some of them are false
9942 positives that indicated awkward code; some are undefined behavior
9943 cases related to constructing (but not using) invalid pointers;
9944 some are assumptions about API behavior; some are (harmlessly)
9945 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
9946 correct; and one or two are genuine bugs that weren't reachable
9947 from the rest of the program. Fixes bug 8793; bugfixes on many,
9951 - Build the torify.1 manpage again. Previously, we were only trying
9952 to build it when also building tor-fw-helper. That's why we didn't
9953 notice that we'd broken the ability to build it. Fixes bug 11321;
9954 bugfix on 0.2.5.1-alpha.
9955 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
9956 11061; bugfix on 0.2.4.7-alpha.
9957 - Correctly document that we search for a system torrc file before
9958 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
9960 - Resolve warnings from Doxygen.
9962 o Code simplifications and refactoring:
9963 - Remove is_internal_IP() function. Resolves ticket 4645.
9964 - Remove unused function circuit_dump_by_chan from circuitlist.c.
9965 Closes issue 9107; patch from "marek".
9966 - Change our use of the ENUM_BF macro to avoid declarations that
9969 o Deprecated versions:
9970 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
9971 attention for some while. Directory authorities no longer accept
9972 descriptors from relays running any version of Tor prior to Tor
9973 0.2.3.16-alpha. Resolves ticket 11149.
9976 - New macros in test.h to simplify writing mock-functions for unit
9977 tests. Part of ticket 11507. Patch from Dana Koch.
9978 - Complete tests for the status.c module. Resolves ticket 11507.
9979 Patch from Dana Koch.
9982 - Remove all code for the long unused v1 directory protocol.
9983 Resolves ticket 11070.
9986 Changes in version 0.2.5.3-alpha - 2014-03-22
9987 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
9988 two new anti-DoS features for Tor relays, resolves a bug that kept
9989 SOCKS5 support for IPv6 from working, fixes several annoying usability
9990 issues for bridge users, and removes more old code for unused
9993 The Tor 0.2.5.x release series is now in patch-freeze: no feature
9994 patches not already written will be considered for inclusion in 0.2.5.x.
9996 o Major features (relay security, DoS-resistance):
9997 - When deciding whether we have run out of memory and we need to
9998 close circuits, also consider memory allocated in buffers for
9999 streams attached to each circuit.
10001 This change, which extends an anti-DoS feature introduced in
10002 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
10003 better resist more memory-based DoS attacks than before. Since the
10004 MaxMemInCellQueues option now applies to all queues, it is renamed
10005 to MaxMemInQueues. This feature fixes bug 10169.
10006 - Avoid hash-flooding denial-of-service attacks by using the secure
10007 SipHash-2-4 hash function for our hashtables. Without this
10008 feature, an attacker could degrade performance of a targeted
10009 client or server by flooding their data structures with a large
10010 number of entries to be stored at the same hash table position,
10011 thereby slowing down the Tor instance. With this feature, hash
10012 table positions are derived from a randomized cryptographic key,
10013 and an attacker cannot predict which entries will collide. Closes
10015 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
10016 the default at 8GBytes), to better support Raspberry Pi users. Fixes
10017 bug 9686; bugfix on 0.2.4.14-alpha.
10019 o Minor features (bridges, pluggable transports):
10020 - Bridges now write the SHA1 digest of their identity key
10021 fingerprint (that is, a hash of a hash of their public key) to
10022 notice-level logs, and to a new hashed-fingerprint file. This
10023 information will help bridge operators look up their bridge in
10024 Globe and similar tools. Resolves ticket 10884.
10025 - Improve the message that Tor displays when running as a bridge
10026 using pluggable transports without an Extended ORPort listener.
10027 Also, log the message in the log file too. Resolves ticket 11043.
10029 o Minor features (other):
10030 - Add a new option, PredictedPortsRelevanceTime, to control how long
10031 after having received a request to connect to a given port Tor
10032 will try to keep circuits ready in anticipation of future requests
10033 for that port. Patch from "unixninja92"; implements ticket 9176.
10034 - Generate a warning if any ports are listed in the SocksPolicy,
10035 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
10036 AuthDirBadExit options. (These options only support address
10037 ranges.) Fixes part of ticket 11108.
10038 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
10041 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
10042 - Build without warnings under clang 3.4. (We have some macros that
10043 define static functions only some of which will get used later in
10044 the module. Starting with clang 3.4, these give a warning unless the
10045 unused attribute is set on them.) Resolves ticket 10904.
10046 - Fix build warnings about missing "a2x" comment when building the
10047 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
10048 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
10050 o Minor bugfixes (client):
10051 - Improve the log message when we can't connect to a hidden service
10052 because all of the hidden service directory nodes hosting its
10053 descriptor are excluded. Improves on our fix for bug 10722, which
10054 was a bugfix on 0.2.0.10-alpha.
10055 - Raise a control port warning when we fail to connect to all of
10056 our bridges. Previously, we didn't inform the controller, and
10057 the bootstrap process would stall. Fixes bug 11069; bugfix on
10059 - Exit immediately when a process-owning controller exits.
10060 Previously, tor relays would wait for a little while after their
10061 controller exited, as if they had gotten an INT signal -- but this
10062 was problematic, since there was no feedback for the user. To do a
10063 clean shutdown, controllers should send an INT signal and give Tor
10064 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
10065 - Stop attempting to connect to bridges before our pluggable
10066 transports are configured (harmless but resulted in some erroneous
10067 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
10068 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
10069 generating incorrect SOCKS5 responses, and confusing client
10070 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
10072 o Minor bugfixes (relays and bridges):
10073 - Avoid crashing on a malformed resolv.conf file when running a
10074 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
10075 - Non-exit relays no longer launch mock DNS requests to check for
10076 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
10077 non-exit relays stopped servicing DNS requests. Fixes bug 965;
10078 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
10079 - Bridges now report complete directory request statistics. Related
10080 to bug 5824; bugfix on 0.2.2.1-alpha.
10081 - Bridges now never collect statistics that were designed for
10082 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
10083 - Stop giving annoying warning messages when we decide not to launch
10084 a pluggable transport proxy that we don't need (because there are
10085 no bridges configured to use it). Resolves ticket 5018; bugfix
10087 - Give the correct URL in the warning message when trying to run a
10088 relay on an ancient version of Windows. Fixes bug 9393.
10090 o Minor bugfixes (backtrace support):
10091 - Support automatic backtraces on more platforms by using the
10092 "-fasynchronous-unwind-tables" compiler option. This option is
10093 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
10094 is on by default and table generation is not. This doesn't yet
10095 add Windows support; only Linux, OSX, and some BSDs are affected.
10096 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
10097 - Avoid strange behavior if two threads hit failed assertions at the
10098 same time and both try to log backtraces at once. (Previously, if
10099 this had happened, both threads would have stored their intermediate
10100 results in the same buffer, and generated junk outputs.) Reported by
10101 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
10102 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
10103 0.2.5.2-alpha; patch from Nick Hopper.
10105 o Minor bugfixes (unit tests):
10106 - Fix a small bug in the unit tests that might have made the tests
10107 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
10108 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
10111 - Remove all remaining code related to version-0 hidden service
10112 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
10113 the rest of bug 10841.
10116 - Document in the manpage that "KBytes" may also be written as
10117 "kilobytes" or "KB", that "Kbits" may also be written as
10118 "kilobits", and so forth. Closes ticket 9222.
10119 - Document that the ClientOnly config option overrides ORPort.
10120 Our old explanation made ClientOnly sound as though it did
10121 nothing at all. Resolves bug 9059.
10122 - Explain that SocksPolicy, DirPolicy, and similar options don't
10123 take port arguments. Fixes the other part of ticket 11108.
10124 - Fix a comment about the rend_server_descriptor_t.protocols field
10125 to more accurately describe its range. Also, make that field
10126 unsigned, to more accurately reflect its usage. Fixes bug 9099;
10127 bugfix on 0.2.1.5-alpha.
10128 - Fix the manpage's description of HiddenServiceAuthorizeClient:
10129 the maximum client name length is 16, not 19. Fixes bug 11118;
10130 bugfix on 0.2.1.6-alpha.
10132 o Code simplifications and refactoring:
10133 - Get rid of router->address, since in all cases it was just the
10134 string representation of router->addr. Resolves ticket 5528.
10136 o Test infrastructure:
10137 - Update to the latest version of tinytest.
10138 - Improve the tinytest implementation of string operation tests so
10139 that comparisons with NULL strings no longer crash the tests; they
10140 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
10143 Changes in version 0.2.4.21 - 2014-02-28
10144 Tor 0.2.4.21 further improves security against potential adversaries who
10145 find breaking 1024-bit crypto doable, and backports several stability
10146 and robustness patches from the 0.2.5 branch.
10148 o Major features (client security):
10149 - When we choose a path for a 3-hop circuit, make sure it contains
10150 at least one relay that supports the NTor circuit extension
10151 handshake. Otherwise, there is a chance that we're building
10152 a circuit that's worth attacking by an adversary who finds
10153 breaking 1024-bit crypto doable, and that chance changes the game
10154 theory. Implements ticket 9777.
10157 - Do not treat streams that fail with reason
10158 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
10159 since it could also indicate an ENETUNREACH connection error. Fixes
10160 part of bug 10777; bugfix on 0.2.4.8-alpha.
10162 o Code simplification and refactoring:
10163 - Remove data structures which were introduced to implement the
10164 CellStatistics option: they are now redundant with the new timestamp
10165 field in the regular packed_cell_t data structure, which we did
10166 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
10169 - Always clear OpenSSL bignums before freeing them -- even bignums
10170 that don't contain secrets. Resolves ticket 10793. Patch by
10172 - Build without warnings under clang 3.4. (We have some macros that
10173 define static functions only some of which will get used later in
10174 the module. Starting with clang 3.4, these give a warning unless the
10175 unused attribute is set on them.) Resolves ticket 10904.
10176 - Update geoip and geoip6 files to the February 7 2014 Maxmind
10177 GeoLite2 Country database.
10180 - Set the listen() backlog limit to the largest actually supported
10181 on the system, not to the value in a header file. Fixes bug 9716;
10182 bugfix on every released Tor.
10183 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
10184 exit node as a NOROUTE error, not an INTERNAL error, since they
10185 can apparently happen when trying to connect to the wrong sort
10186 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
10187 - Fix build warnings about missing "a2x" comment when building the
10188 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
10189 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
10190 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
10191 not entirely remove it from the connection lists. Fixes bug 9602;
10192 bugfix on 0.2.4.4-alpha.
10193 - Fix a segmentation fault in our benchmark code when running with
10194 Fedora's OpenSSL package, or any other OpenSSL that provides
10195 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
10196 - Turn "circuit handshake stats since last time" log messages into a
10197 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
10199 o Documentation fixes:
10200 - Document that all but one DirPort entry must have the NoAdvertise
10201 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
10204 Changes in version 0.2.5.2-alpha - 2014-02-13
10205 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
10206 like the "poor random number generation" fix and the "building too many
10207 circuits" fix. It also further improves security against potential
10208 adversaries who find breaking 1024-bit crypto doable, and launches
10209 pluggable transports on demand (which gets us closer to integrating
10210 pluggable transport support by default -- not to be confused with Tor
10211 bundles enabling pluggable transports and bridges by default).
10213 o Major features (client security):
10214 - When we choose a path for a 3-hop circuit, make sure it contains
10215 at least one relay that supports the NTor circuit extension
10216 handshake. Otherwise, there is a chance that we're building
10217 a circuit that's worth attacking by an adversary who finds
10218 breaking 1024-bit crypto doable, and that chance changes the game
10219 theory. Implements ticket 9777.
10220 - Clients now look at the "usecreatefast" consensus parameter to
10221 decide whether to use CREATE_FAST or CREATE cells for the first hop
10222 of their circuit. This approach can improve security on connections
10223 where Tor's circuit handshake is stronger than the available TLS
10224 connection security levels, but the tradeoff is more computational
10225 load on guard relays. Implements proposal 221. Resolves ticket 9386.
10227 o Major features (bridges):
10228 - Don't launch pluggable transport proxies if we don't have any
10229 bridges configured that would use them. Now we can list many
10230 pluggable transports, and Tor will dynamically start one when it
10231 hears a bridge address that needs it. Resolves ticket 5018.
10232 - The bridge directory authority now assigns status flags (Stable,
10233 Guard, etc) to bridges based on thresholds calculated over all
10234 Running bridges. Now bridgedb can finally make use of its features
10235 to e.g. include at least one Stable bridge in its answers. Fixes
10238 o Major features (other):
10239 - Extend ORCONN controller event to include an "ID" parameter,
10240 and add four new controller event types CONN_BW, CIRC_BW,
10241 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
10242 The new events are emitted in private Tor networks only, with the
10243 goal of being able to better track performance and load during
10244 full-network simulations. Implements proposal 218 and ticket 7359.
10245 - On some platforms (currently: recent OSX versions, glibc-based
10246 platforms that support the ELF format, and a few other
10247 Unix-like operating systems), Tor can now dump stack traces
10248 when a crash occurs or an assertion fails. By default, traces
10249 are dumped to stderr (if possible) and to any logs that are
10250 reporting errors. Implements ticket 9299.
10253 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
10254 not entirely remove it from the connection lists. Fixes bug 9602;
10255 bugfix on 0.2.4.4-alpha.
10256 - Do not treat streams that fail with reason
10257 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
10258 since it could also indicate an ENETUNREACH connection error. Fixes
10259 part of bug 10777; bugfix on 0.2.4.8-alpha.
10261 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
10262 - Do not allow OpenSSL engines to replace the PRNG, even when
10263 HardwareAccel is set. The only default builtin PRNG engine uses
10264 the Intel RDRAND instruction to replace the entire PRNG, and
10265 ignores all attempts to seed it with more entropy. That's
10266 cryptographically stupid: the right response to a new alleged
10267 entropy source is never to discard all previously used entropy
10268 sources. Fixes bug 10402; works around behavior introduced in
10269 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
10271 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
10272 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
10273 - Avoid launching spurious extra circuits when a stream is pending.
10274 This fixes a bug where any circuit that _wasn't_ unusable for new
10275 streams would be treated as if it were, causing extra circuits to
10276 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
10278 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10279 - No longer stop reading or writing on cpuworker connections when
10280 our rate limiting buckets go empty. Now we should handle circuit
10281 handshake requests more promptly. Resolves bug 9731.
10282 - Stop trying to bootstrap all our directory information from
10283 only our first guard. Discovered while fixing bug 9946; bugfix
10286 o Minor features (bridges, pluggable transports):
10287 - Add threshold cutoffs to the networkstatus document created by
10288 the Bridge Authority. Fixes bug 1117.
10289 - On Windows, spawn background processes using the CREATE_NO_WINDOW
10290 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
10291 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
10292 Vidalia set this option for us.) Implements ticket 10297.
10294 o Minor features (security):
10295 - Always clear OpenSSL bignums before freeing them -- even bignums
10296 that don't contain secrets. Resolves ticket 10793. Patch by
10297 Florent Daignière.
10299 o Minor features (config options and command line):
10300 - Add an --allow-missing-torrc commandline option that tells Tor to
10301 run even if the configuration file specified by -f is not available.
10302 Implements ticket 10060.
10303 - Add support for the TPROXY transparent proxying facility on Linux.
10304 See documentation for the new TransProxyType option for more
10305 details. Implementation by "thomo". Closes ticket 10582.
10307 o Minor features (controller):
10308 - Add a new "HS_DESC" controller event that reports activities
10309 related to hidden service descriptors. Resolves ticket 8510.
10310 - New "DROPGUARDS" controller command to forget all current entry
10311 guards. Not recommended for ordinary use, since replacing guards
10312 too frequently makes several attacks easier. Resolves ticket 9934;
10315 o Minor features (build):
10316 - Assume that a user using ./configure --host wants to cross-compile,
10317 and give an error if we cannot find a properly named
10318 tool-chain. Add a --disable-tool-name-check option to proceed
10319 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
10320 - If we run ./configure and the compiler recognizes -fstack-protector
10321 but the linker rejects it, warn the user about a potentially missing
10322 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
10324 o Minor features (testing):
10325 - If Python is installed, "make check" now runs extra tests beyond
10326 the unit test scripts.
10327 - When bootstrapping a test network, sometimes very few relays get
10328 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
10329 specify a set of relays which should be voted Guard regardless of
10330 their uptime or bandwidth. Addresses ticket 9206.
10332 o Minor features (log messages):
10333 - When ServerTransportPlugin is set on a bridge, Tor can write more
10334 useful statistics about bridge use in its extrainfo descriptors,
10335 but only if the Extended ORPort ("ExtORPort") is set too. Add a
10336 log message to inform the user in this case. Resolves ticket 9651.
10337 - When receiving a new controller connection, log the origin address.
10338 Resolves ticket 9698; patch from "sigpipe".
10339 - When logging OpenSSL engine status at startup, log the status of
10340 more engines. Fixes ticket 10043; patch from Joshua Datko.
10341 - Turn "circuit handshake stats since last time" log messages into a
10342 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
10344 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10345 - Improve the circuit queue out-of-memory handler. Previously, when
10346 we ran low on memory, we'd close whichever circuits had the most
10347 queued cells. Now, we close those that have the *oldest* queued
10348 cells, on the theory that those are most responsible for us
10349 running low on memory. Based on analysis from a forthcoming paper
10350 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
10351 - Generate bootstrapping status update events correctly when fetching
10352 microdescriptors. Fixes bug 9927.
10353 - Update to the October 2 2013 Maxmind GeoLite Country database.
10355 o Minor bugfixes (clients):
10356 - When closing a channel that has already been open, do not close
10357 pending circuits that were waiting to connect to the same relay.
10358 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
10361 o Minor bugfixes (relays):
10362 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
10363 exit node as a NOROUTE error, not an INTERNAL error, since they
10364 can apparently happen when trying to connect to the wrong sort
10365 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
10367 o Minor bugfixes (bridges):
10368 - Fix a bug where the first connection works to a bridge that uses a
10369 pluggable transport with client-side parameters, but we don't send
10370 the client-side parameters on subsequent connections. (We don't
10371 use any pluggable transports with client-side parameters yet,
10372 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
10373 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
10375 o Minor bugfixes (node selection):
10376 - If ExcludeNodes is set, consider non-excluded hidden service
10377 directory servers before excluded ones. Do not consider excluded
10378 hidden service directory servers at all if StrictNodes is
10379 set. (Previously, we would sometimes decide to connect to those
10380 servers, and then realize before we initiated a connection that
10381 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
10382 Reported by "mr-4".
10383 - If we set the ExitNodes option but it doesn't include any nodes
10384 that have the Exit flag, we would choose not to bootstrap. Now we
10385 bootstrap so long as ExitNodes includes nodes which can exit to
10386 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
10388 o Minor bugfixes (controller and command-line):
10389 - If changing a config option via "setconf" fails in a recoverable
10390 way, we used to nonetheless write our new control ports to the
10391 file described by the "ControlPortWriteToFile" option. Now we only
10392 write out that file if we successfully switch to the new config
10393 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
10394 - When a command-line option such as --version or --help that
10395 ordinarily implies --hush appears on the command line along with
10396 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
10397 only if it appeared later on the command line. Fixes bug 9578;
10398 bugfix on 0.2.5.1-alpha.
10400 o Minor bugfixes (code correctness):
10401 - Previously we used two temporary files when writing descriptors to
10402 disk; now we only use one. Fixes bug 1376.
10403 - Remove an erroneous (but impossible and thus harmless) pointer
10404 comparison that would have allowed compilers to skip a bounds
10405 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
10406 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
10407 - Fix an always-true assertion in pluggable transports code so it
10408 actually checks what it was trying to check. Fixes bug 10046;
10409 bugfix on 0.2.3.9-alpha. Found by "dcb".
10411 o Minor bugfixes (protocol correctness):
10412 - When receiving a VERSIONS cell with an odd number of bytes, close
10413 the connection immediately since the cell is malformed. Fixes bug
10414 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
10417 o Minor bugfixes (build):
10418 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
10419 turned off (that is, without support for v2 link handshakes). Fixes
10420 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
10421 - Fix compilation warnings and startup issues when running with
10422 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
10424 - Fix compilation on Solaris 9, which didn't like us having an
10425 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
10427 o Minor bugfixes (testing):
10428 - Fix a segmentation fault in our benchmark code when running with
10429 Fedora's OpenSSL package, or any other OpenSSL that provides
10430 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
10432 o Minor bugfixes (log messages):
10433 - Fix a bug where clients using bridges would report themselves
10434 as 50% bootstrapped even without a live consensus document.
10435 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
10436 - Suppress a warning where, if there's only one directory authority
10437 in the network, we would complain that votes and signatures cannot
10438 be uploaded to other directory authorities. Fixes bug 10842;
10439 bugfix on 0.2.2.26-beta.
10440 - Report bootstrapping progress correctly when we're downloading
10441 microdescriptors. We had updated our "do we have enough microdescs
10442 to begin building circuits?" logic most recently in 0.2.4.10-alpha
10443 (see bug 5956), but we left the bootstrap status event logic at
10444 "how far through getting 1/4 of them are we?" Fixes bug 9958;
10445 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
10447 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
10448 - Avoid a crash bug when starting with a corrupted microdescriptor
10449 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
10450 - If we fail to dump a previously cached microdescriptor to disk, avoid
10451 freeing duplicate data later on. Fixes bug 10423; bugfix on
10452 0.2.4.13-alpha. Spotted by "bobnomnom".
10454 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10455 - Correctly log long IPv6 exit policies, instead of truncating them
10456 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
10457 - Our default TLS ecdhe groups were backwards: we meant to be using
10458 P224 for relays (for performance win) and P256 for bridges (since
10459 it is more common in the wild). Instead we had it backwards. After
10460 reconsideration, we decided that the default should be P256 on all
10461 hosts, since its security is probably better, and since P224 is
10462 reportedly used quite little in the wild. Found by "skruffy" on
10463 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
10464 - Free directory authority certificate download statuses on exit
10465 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
10467 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10468 - If the guard we choose first doesn't answer, we would try the
10469 second guard, but once we connected to the second guard we would
10470 abandon it and retry the first one, slowing down bootstrapping.
10471 The fix is to treat all our initially chosen guards as acceptable
10472 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10473 - Fix an assertion failure that would occur when disabling the
10474 ORPort setting on a running Tor process while accounting was
10475 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10476 - When examining the list of network interfaces to find our address,
10477 do not consider non-running or disabled network interfaces. Fixes
10478 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10479 - Avoid an off-by-one error when checking buffer boundaries when
10480 formatting the exit status of a pluggable transport helper.
10481 This is probably not an exploitable bug, but better safe than
10482 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10485 o Removed code and features:
10486 - Clients now reject any directory authority certificates lacking
10487 a dir-key-crosscert element. These have been included since
10488 0.2.1.9-alpha, so there's no real reason for them to be optional
10489 any longer. Completes proposal 157. Resolves ticket 10162.
10490 - Remove all code that existed to support the v2 directory system,
10491 since there are no longer any v2 directory authorities. Resolves
10493 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
10494 options, which were used for designating authorities as "Hidden
10495 service authorities". There has been no use of hidden service
10496 authorities since 0.2.2.1-alpha, when we stopped uploading or
10497 downloading v0 hidden service descriptors. Fixes bug 10881; also
10498 part of a fix for bug 10841.
10500 o Code simplification and refactoring:
10501 - Remove some old fallback code designed to keep Tor clients working
10502 in a network with only two working relays. Elsewhere in the code we
10503 have long since stopped supporting such networks, so there wasn't
10504 much point in keeping it around. Addresses ticket 9926.
10505 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
10506 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
10507 - Remove data structures which were introduced to implement the
10508 CellStatistics option: they are now redundant with the addition
10509 of a timestamp to the regular packed_cell_t data structure, which
10510 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
10513 o Documentation (man page) fixes:
10514 - Update manpage to describe some of the files you can expect to
10515 find in Tor's DataDirectory. Addresses ticket 9839.
10516 - Document that all but one DirPort entry must have the NoAdvertise
10517 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
10519 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10520 - Clarify the usage and risks of setting the ContactInfo torrc line
10521 for your relay or bridge. Resolves ticket 9854.
10522 - Add anchors to the manpage so we can link to the html version of
10523 the documentation for specific options. Resolves ticket 9866.
10524 - Replace remaining references to DirServer in man page and
10525 log entries. Resolves ticket 10124.
10528 - Make the "tor-gencert" tool used by directory authority operators
10529 create 2048-bit signing keys by default (rather than 1024-bit, since
10530 1024-bit is uncomfortably small these days). Addresses ticket 10324.
10533 Changes in version 0.2.4.20 - 2013-12-22
10534 Tor 0.2.4.20 fixes potentially poor random number generation for users
10535 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
10536 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
10537 and 4) have no state file in their DataDirectory (as would happen on
10538 first start). Users who generated relay or hidden service identity
10539 keys in such a situation should discard them and generate new ones.
10541 This release also fixes a logic error that caused Tor clients to build
10542 many more preemptive circuits than they actually need.
10545 - Do not allow OpenSSL engines to replace the PRNG, even when
10546 HardwareAccel is set. The only default builtin PRNG engine uses
10547 the Intel RDRAND instruction to replace the entire PRNG, and
10548 ignores all attempts to seed it with more entropy. That's
10549 cryptographically stupid: the right response to a new alleged
10550 entropy source is never to discard all previously used entropy
10551 sources. Fixes bug 10402; works around behavior introduced in
10552 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
10554 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
10555 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
10556 - Avoid launching spurious extra circuits when a stream is pending.
10557 This fixes a bug where any circuit that _wasn't_ unusable for new
10558 streams would be treated as if it were, causing extra circuits to
10559 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
10562 - Avoid a crash bug when starting with a corrupted microdescriptor
10563 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
10564 - If we fail to dump a previously cached microdescriptor to disk, avoid
10565 freeing duplicate data later on. Fixes bug 10423; bugfix on
10566 0.2.4.13-alpha. Spotted by "bobnomnom".
10569 Changes in version 0.2.4.19 - 2013-12-11
10570 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
10571 (1986-2013). Aaron worked on diverse projects including helping to guide
10572 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
10573 transparency to the U.S government's PACER documents, and contributing
10574 design and development for Tor and Tor2Web. Aaron was one of the latest
10575 martyrs in our collective fight for civil liberties and human rights,
10576 and his death is all the more painful because he was one of us.
10578 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
10579 a new circuit handshake and link encryption that use ECC to provide
10580 better security and efficiency; makes relays better manage circuit
10581 creation requests; uses "directory guards" to reduce client enumeration
10582 risks; makes bridges collect and report statistics about the pluggable
10583 transports they support; cleans up and improves our geoip database;
10584 gets much closer to IPv6 support for clients, bridges, and relays; makes
10585 directory authorities use measured bandwidths rather than advertised
10586 ones when computing flags and thresholds; disables client-side DNS
10587 caching to reduce tracking risks; and fixes a big bug in bridge
10588 reachability testing. This release introduces two new design
10589 abstractions in the code: a new "channel" abstraction between circuits
10590 and or_connections to allow for implementing alternate relay-to-relay
10591 transports, and a new "circuitmux" abstraction storing the queue of
10592 circuits for a channel. The release also includes many stability,
10593 security, and privacy fixes.
10596 Changes in version 0.2.4.18-rc - 2013-11-16
10597 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
10598 series. It takes a variety of fixes from the 0.2.5.x branch to improve
10599 stability, performance, and better handling of edge cases.
10602 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10603 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10604 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10605 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10606 them to solve bug 6033.)
10609 - No longer stop reading or writing on cpuworker connections when
10610 our rate limiting buckets go empty. Now we should handle circuit
10611 handshake requests more promptly. Resolves bug 9731.
10612 - If we are unable to save a microdescriptor to the journal, do not
10613 drop it from memory and then reattempt downloading it. Fixes bug
10614 9645; bugfix on 0.2.2.6-alpha.
10615 - Stop trying to bootstrap all our directory information from
10616 only our first guard. Discovered while fixing bug 9946; bugfix
10618 - The new channel code sometimes lost track of in-progress circuits,
10619 causing long-running clients to stop building new circuits. The
10620 fix is to always call circuit_n_chan_done(chan, 0) from
10621 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
10623 o Minor bugfixes (on 0.2.4.x):
10624 - Correctly log long IPv6 exit policies, instead of truncating them
10625 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
10626 - Our default TLS ecdhe groups were backwards: we meant to be using
10627 P224 for relays (for performance win) and P256 for bridges (since
10628 it is more common in the wild). Instead we had it backwards. After
10629 reconsideration, we decided that the default should be P256 on all
10630 hosts, since its security is probably better, and since P224 is
10631 reportedly used quite little in the wild. Found by "skruffy" on
10632 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
10633 - Free directory authority certificate download statuses on exit
10634 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
10636 o Minor bugfixes (on 0.2.3.x and earlier):
10637 - If the guard we choose first doesn't answer, we would try the
10638 second guard, but once we connected to the second guard we would
10639 abandon it and retry the first one, slowing down bootstrapping.
10640 The fix is to treat all our initially chosen guards as acceptable
10641 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10642 - Fix an assertion failure that would occur when disabling the
10643 ORPort setting on a running Tor process while accounting was
10644 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10645 - When examining the list of network interfaces to find our address,
10646 do not consider non-running or disabled network interfaces. Fixes
10647 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10648 - Avoid an off-by-one error when checking buffer boundaries when
10649 formatting the exit status of a pluggable transport helper.
10650 This is probably not an exploitable bug, but better safe than
10651 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10654 o Minor features (protecting client timestamps):
10655 - Clients no longer send timestamps in their NETINFO cells. These were
10656 not used for anything, and they provided one small way for clients
10657 to be distinguished from each other as they moved from network to
10658 network or behind NAT. Implements part of proposal 222.
10659 - Clients now round timestamps in INTRODUCE cells down to the nearest
10660 10 minutes. If a new Support022HiddenServices option is set to 0, or
10661 if it's set to "auto" and the feature is disabled in the consensus,
10662 the timestamp is sent as 0 instead. Implements part of proposal 222.
10663 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10664 a big deal from a security point of view, but it achieves no actual
10665 good purpose, and isn't needed. Implements part of proposal 222.
10666 - Reduce down accuracy of timestamps in hidden service descriptors.
10667 Implements part of proposal 222.
10669 o Minor features (other):
10670 - Improve the circuit queue out-of-memory handler. Previously, when
10671 we ran low on memory, we'd close whichever circuits had the most
10672 queued cells. Now, we close those that have the *oldest* queued
10673 cells, on the theory that those are most responsible for us
10674 running low on memory. Based on analysis from a forthcoming paper
10675 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
10676 - Generate bootstrapping status update events correctly when fetching
10677 microdescriptors. Fixes bug 9927.
10678 - Update to the October 2 2013 Maxmind GeoLite Country database.
10680 o Documentation fixes:
10681 - Clarify the usage and risks of setting the ContactInfo torrc line
10682 for your relay or bridge. Resolves ticket 9854.
10683 - Add anchors to the manpage so we can link to the html version of
10684 the documentation for specific options. Resolves ticket 9866.
10685 - Replace remaining references to DirServer in man page and
10686 log entries. Resolves ticket 10124.
10689 Changes in version 0.2.5.1-alpha - 2013-10-02
10690 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
10691 on Linux, allows bridges that offer pluggable transports to report usage
10692 statistics, fixes many issues to make testing easier, and provides
10693 a pile of minor features and bugfixes that have been waiting for a
10694 release of the new branch.
10696 This is the first alpha release in a new series, so expect there to
10697 be bugs. Users who would rather test out a more stable branch should
10698 stay with 0.2.4.x for now.
10700 o Major features (security):
10701 - Use the seccomp2 syscall filtering facility on Linux to limit
10702 which system calls Tor can invoke. This is an experimental,
10703 Linux-only feature to provide defense-in-depth against unknown
10704 attacks. To try turning it on, set "Sandbox 1" in your torrc
10705 file. Please be ready to report bugs. We hope to add support
10706 for better sandboxing in the future, including more fine-grained
10707 filters, better division of responsibility, and support for more
10708 platforms. This work has been done by Cristian-Matei Toader for
10709 Google Summer of Code.
10710 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10711 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10712 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10713 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10714 them to solve bug 6033.)
10716 o Major features (other):
10717 - Add support for passing arguments to managed pluggable transport
10718 proxies. Implements ticket 3594.
10719 - Bridges now track GeoIP information and the number of their users
10720 even when pluggable transports are in use, and report usage
10721 statistics in their extra-info descriptors. Resolves tickets 4773
10723 - Make testing Tor networks bootstrap better: lower directory fetch
10724 retry schedules and maximum interval without directory requests,
10725 and raise maximum download tries. Implements ticket 6752.
10726 - Add make target 'test-network' to run tests on a Chutney network.
10727 Implements ticket 8530.
10728 - The ntor handshake is now on-by-default, no matter what the
10729 directory authorities recommend. Implements ticket 8561.
10732 - Instead of writing destroy cells directly to outgoing connection
10733 buffers, queue them and intersperse them with other outgoing cells.
10734 This can prevent a set of resource starvation conditions where too
10735 many pending destroy cells prevent data cells from actually getting
10736 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
10737 bugfix on 0.2.0.1-alpha.
10738 - If we are unable to save a microdescriptor to the journal, do not
10739 drop it from memory and then reattempt downloading it. Fixes bug
10740 9645; bugfix on 0.2.2.6-alpha.
10741 - The new channel code sometimes lost track of in-progress circuits,
10742 causing long-running clients to stop building new circuits. The
10743 fix is to always call circuit_n_chan_done(chan, 0) from
10744 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
10747 - Tor now builds each source file in two modes: a mode that avoids
10748 exposing identifiers needlessly, and another mode that exposes
10749 more identifiers for testing. This lets the compiler do better at
10750 optimizing the production code, while enabling us to take more
10751 radical measures to let the unit tests test things.
10752 - The production builds no longer include functions used only in
10753 the unit tests; all functions exposed from a module only for
10754 unit-testing are now static in production builds.
10755 - Add an --enable-coverage configuration option to make the unit
10756 tests (and a new src/or/tor-cov target) to build with gcov test
10760 - We now have rudimentary function mocking support that our unit
10761 tests can use to test functions in isolation. Function mocking
10762 lets the tests temporarily replace a function's dependencies with
10763 stub functions, so that the tests can check the function without
10764 invoking the other functions it calls.
10765 - Add more unit tests for the <circid,channel>->circuit map, and
10766 the destroy-cell-tracking code to fix bug 7912.
10767 - Unit tests for failing cases of the TAP onion handshake.
10768 - More unit tests for address-manipulation functions.
10770 o Minor features (protecting client timestamps):
10771 - Clients no longer send timestamps in their NETINFO cells. These were
10772 not used for anything, and they provided one small way for clients
10773 to be distinguished from each other as they moved from network to
10774 network or behind NAT. Implements part of proposal 222.
10775 - Clients now round timestamps in INTRODUCE cells down to the nearest
10776 10 minutes. If a new Support022HiddenServices option is set to 0, or
10777 if it's set to "auto" and the feature is disabled in the consensus,
10778 the timestamp is sent as 0 instead. Implements part of proposal 222.
10779 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10780 a big deal from a security point of view, but it achieves no actual
10781 good purpose, and isn't needed. Implements part of proposal 222.
10782 - Reduce down accuracy of timestamps in hidden service descriptors.
10783 Implements part of proposal 222.
10785 o Minor features (config options):
10786 - Config (torrc) lines now handle fingerprints which are missing
10787 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
10788 - Support a --dump-config option to print some or all of the
10789 configured options. Mainly useful for debugging the command-line
10790 option parsing code. Helps resolve ticket 4647.
10791 - Raise awareness of safer logging: notify user of potentially
10792 unsafe config options, like logging more verbosely than severity
10793 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
10794 - Add a new configuration option TestingV3AuthVotingStartOffset
10795 that bootstraps a network faster by changing the timing for
10796 consensus votes. Addresses ticket 8532.
10797 - Add a new torrc option "ServerTransportOptions" that allows
10798 bridge operators to pass configuration parameters to their
10799 pluggable transports. Resolves ticket 8929.
10800 - The config (torrc) file now accepts bandwidth and space limits in
10801 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
10802 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
10805 o Minor features (build):
10806 - Add support for `--library-versions` flag. Implements ticket 6384.
10807 - Return the "unexpected sendme" warnings to a warn severity, but make
10808 them rate limited, to help diagnose ticket 8093.
10809 - Detect a missing asciidoc, and warn the user about it, during
10810 configure rather than at build time. Fixes issue 6506. Patch from
10813 o Minor features (other):
10814 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
10815 sockets in a single system call. Implements ticket 5129.
10816 - Log current accounting state (bytes sent and received + remaining
10817 time for the current accounting period) in the relay's heartbeat
10818 message. Implements ticket 5526; patch from Peter Retzlaff.
10819 - Implement the TRANSPORT_LAUNCHED control port event that
10820 notifies controllers about new launched pluggable
10821 transports. Resolves ticket 5609.
10822 - If we're using the pure-C 32-bit curve25519_donna implementation
10823 of curve25519, build it with the -fomit-frame-pointer option to
10824 make it go faster on register-starved hosts. This improves our
10825 handshake performance by about 6% on i386 hosts without nacl.
10826 Closes ticket 8109.
10827 - Update to the September 4 2013 Maxmind GeoLite Country database.
10830 - Set the listen() backlog limit to the largest actually supported
10831 on the system, not to the value in a header file. Fixes bug 9716;
10832 bugfix on every released Tor.
10833 - No longer accept malformed http headers when parsing urls from
10834 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
10835 bugfix on 0.0.6pre1.
10836 - In munge_extrainfo_into_routerinfo(), check the return value of
10837 memchr(). This would have been a serious issue if we ever passed
10838 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
10840 - On the chance that somebody manages to build Tor on a
10841 platform where time_t is unsigned, correct the way that
10842 microdesc_add_to_cache() handles negative time arguments.
10843 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
10844 - Reject relative control socket paths and emit a warning. Previously,
10845 single-component control socket paths would be rejected, but Tor
10846 would not log why it could not validate the config. Fixes bug 9258;
10847 bugfix on 0.2.3.16-alpha.
10849 o Minor bugfixes (command line):
10850 - Use a single command-line parser for parsing torrc options on the
10851 command line and for finding special command-line options to avoid
10852 inconsistent behavior for torrc option arguments that have the same
10853 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
10855 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
10856 9573; bugfix on 0.0.9pre5.
10858 o Minor fixes (build, auxiliary programs):
10859 - Stop preprocessing the "torify" script with autoconf, since
10860 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
10862 - The tor-fw-helper program now follows the standard convention and
10863 exits with status code "0" on success. Fixes bug 9030; bugfix on
10864 0.2.3.1-alpha. Patch by Arlo Breault.
10865 - Corrected ./configure advice for what openssl dev package you should
10866 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
10868 o Minor code improvements:
10869 - Remove constants and tests for PKCS1 padding; it's insecure and
10870 shouldn't be used for anything new. Fixes bug 8792; patch
10872 - Remove instances of strcpy() from the unit tests. They weren't
10873 hurting anything, since they were only in the unit tests, but it's
10874 embarassing to have strcpy() in the code at all, and some analysis
10875 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
10876 0.2.3.8-alpha. Patch from Arlo Breault.
10878 o Removed features:
10879 - Remove migration code from when we renamed the "cached-routers"
10880 file to "cached-descriptors" back in 0.2.0.8-alpha. This
10881 incidentally resolves ticket 6502 by cleaning up the related code
10882 a bit. Patch from Akshay Hebbar.
10884 o Code simplification and refactoring:
10885 - Extract the common duplicated code for creating a subdirectory
10886 of the data directory and writing to a file in it. Fixes ticket
10887 4282; patch from Peter Retzlaff.
10888 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
10889 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
10890 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
10891 - Add a set of accessor functions for the circuit timeout data
10892 structure. Fixes ticket 6153; patch from "piet".
10893 - Clean up exit paths from connection_listener_new(). Closes ticket
10894 8789. Patch from Arlo Breault.
10895 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
10896 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
10897 - Use a doubly-linked list to implement the global circuit list.
10898 Resolves ticket 9108. Patch from Marek Majkowski.
10899 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
10902 Changes in version 0.2.4.17-rc - 2013-09-05
10903 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
10904 series. It adds an emergency step to help us tolerate the massive
10905 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
10906 circuit-level handshakes now effectively jump the queue compared to
10907 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
10908 big bug hindering bridge reachability tests.
10911 - Relays now process the new "NTor" circuit-level handshake requests
10912 with higher priority than the old "TAP" circuit-level handshake
10913 requests. We still process some TAP requests to not totally starve
10914 0.2.3 clients when NTor becomes popular. A new consensus parameter
10915 "NumNTorsPerTAP" lets us tune the balance later if we need to.
10916 Implements ticket 9574.
10919 - If the circuit build timeout logic is disabled (via the consensus,
10920 or because we are an authority), then don't build testing circuits.
10921 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
10922 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
10923 previously they did not, which prevented them from receiving
10924 successful connections from relays for self-test or bandwidth
10925 testing. Also, when a relay is extending a circuit to a bridge,
10926 it needs to send a NETINFO cell, even when the bridge hasn't sent
10927 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
10928 - If the time to download the next old-style networkstatus is in
10929 the future, do not decline to consider whether to download the
10930 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
10934 - Avoid double-closing the listener socket in our socketpair()
10935 replacement (used on Windows) in the case where the addresses on
10936 our opened sockets don't match what we expected. Fixes bug 9400;
10937 bugfix on 0.0.2pre7. Found by Coverity.
10939 o Minor fixes (config options):
10940 - Avoid overflows when the user sets MaxCircuitDirtiness to a
10941 ridiculously high value, by imposing a (ridiculously high) 30-day
10942 maximum on MaxCircuitDirtiness.
10943 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
10944 message is logged at notice, not at info.
10945 - Warn and fail if a server is configured not to advertise any
10946 ORPorts at all. (We need *something* to put in our descriptor,
10947 or we just won't work.)
10950 - Track how many "TAP" and "NTor" circuit handshake requests we get,
10951 and how many we complete, and log it every hour to help relay
10952 operators follow trends in network load. Addresses ticket 9658.
10953 - Update to the August 7 2013 Maxmind GeoLite Country database.
10956 Changes in version 0.2.4.16-rc - 2013-08-10
10957 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
10958 series. It fixes several crash bugs in the 0.2.4 branch.
10961 - Fix a bug in the voting algorithm that could yield incorrect results
10962 when a non-naming authority declared too many flags. Fixes bug 9200;
10963 bugfix on 0.2.0.3-alpha.
10964 - Fix an uninitialized read that could in some cases lead to a remote
10965 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
10966 Anybody running a hidden service on the experimental 0.2.4.x
10967 branch should upgrade. (This is, so far as we know, unrelated to
10969 - Avoid an assertion failure when processing DNS replies without the
10970 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
10971 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
10972 0.2.4.15-rc. Found by stem integration tests.
10975 - Fix an invalid memory read that occured when a pluggable
10976 transport proxy failed its configuration protocol.
10977 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
10978 - When evaluating whether to use a connection that we haven't
10979 decided is canonical using a recent link protocol version,
10980 decide that it's canonical only if it used address _does_
10981 match the desired address. Fixes bug 9309; bugfix on
10982 0.2.4.4-alpha. Reported by skruffy.
10983 - Make the default behavior of NumDirectoryGuards be to track
10984 NumEntryGuards. Now a user who changes only NumEntryGuards will get
10985 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
10986 - Fix a spurious compilation warning with some older versions of
10987 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
10990 - Update to the July 3 2013 Maxmind GeoLite Country database.
10993 Changes in version 0.2.4.15-rc - 2013-07-01
10994 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
10995 series. It fixes a few smaller bugs, but generally appears stable.
10996 Please test it and let us know whether it is!
10999 - When receiving a new configuration file via the control port's
11000 LOADCONF command, do not treat the defaults file as absent.
11001 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
11004 - Issue a warning when running with the bufferevents backend enabled.
11005 It's still not stable, and people should know that they're likely
11006 to hit unexpected problems. Closes ticket 9147.
11009 Changes in version 0.2.4.14-alpha - 2013-06-18
11010 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
11011 present in 0.2.4.13-alpha.
11014 - When we have too much memory queued in circuits (according to a new
11015 MaxMemInCellQueues option), close the circuits consuming the most
11016 memory. This prevents us from running out of memory as a relay if
11017 circuits fill up faster than they can be drained. Fixes bug 9063;
11018 bugfix on the 54th commit of Tor. This bug is a further fix beyond
11019 bug 6252, whose fix was merged into 0.2.3.21-rc.
11021 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
11022 where we tried to solve this issue simply by imposing an upper limit
11023 on the number of queued cells for a single circuit. That approach
11024 proved to be problematic, since there are ways to provoke clients to
11025 send a number of cells in excess of any such reasonable limit. Fixes
11026 bug 9072; bugfix on 0.2.4.13-alpha.
11028 - Limit hidden service descriptors to at most ten introduction
11029 points, to slow one kind of guard enumeration. Fixes bug 9002;
11030 bugfix on 0.1.1.11-alpha.
11033 Changes in version 0.2.4.13-alpha - 2013-06-14
11034 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
11035 vulnerabilities, makes socks5 username/password circuit isolation
11036 actually actually work (this time for sure!), and cleans up a bunch
11037 of other issues in preparation for a release candidate.
11039 o Major bugfixes (robustness):
11040 - Close any circuit that has too many cells queued on it. Fixes
11041 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
11042 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
11043 - Prevent the get_freelists() function from running off the end of
11044 the list of freelists if it somehow gets an unrecognized
11045 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
11047 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
11048 when an exit connection with optimistic data succeeds immediately
11049 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
11051 - Fix a directory authority crash bug when building a consensus
11052 using an older consensus as its basis. Fixes bug 8833. Bugfix
11056 - Avoid a memory leak where we would leak a consensus body when we
11057 find that a consensus which we couldn't previously verify due to
11058 missing certificates is now verifiable. Fixes bug 8719; bugfix
11060 - We used to always request authority certificates by identity digest,
11061 meaning we'd get the newest one even when we wanted one with a
11062 different signing key. Then we would complain about being given
11063 a certificate we already had, and never get the one we really
11064 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
11065 resource to request the one we want. Fixes bug 5595; bugfix on
11067 - Follow the socks5 protocol when offering username/password
11068 authentication. The fix for bug 8117 exposed this bug, and it
11069 turns out real-world applications like Pidgin do care. Bugfix on
11070 0.2.3.2-alpha; fixes bug 8879.
11071 - Prevent failures on Windows Vista and later when rebuilding the
11072 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
11073 bugfix on 0.2.4.12-alpha.
11076 - Fix an impossible buffer overrun in the AES unit tests. Fixes
11077 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
11078 - If for some reason we fail to write a microdescriptor while
11079 rebuilding the cache, do not let the annotations from that
11080 microdescriptor linger in the cache file, and do not let the
11081 microdescriptor stay recorded as present in its old location.
11082 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
11083 - Fix a memory leak that would occur whenever a configuration
11084 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
11085 - Paste the description for PathBias parameters from the man
11086 page into or.h, so the code documents them too. Fixes bug 7982;
11087 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
11088 - Relays now treat a changed IPv6 ORPort as sufficient reason to
11089 publish an updated descriptor. Fixes bug 6026; bugfix on
11091 - When launching a resolve request on behalf of an AF_UNIX control
11092 socket, omit the address field of the new entry connection, used in
11093 subsequent controller events, rather than letting tor_dup_addr()
11094 set it to "<unknown address type>". Fixes bug 8639; bugfix on
11097 o Minor bugfixes (log messages):
11098 - Fix a scaling issue in the path bias accounting code that
11099 resulted in "Bug:" log messages from either
11100 pathbias_scale_close_rates() or pathbias_count_build_success().
11101 This represents a bugfix on a previous bugfix: the original fix
11102 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
11104 - Give a less useless error message when the user asks for an IPv4
11105 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
11109 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
11110 to tolerate bug 8093 for now.
11111 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
11112 in directory authority votes to describe whether they have enough
11113 measured bandwidths to ignore advertised (relay descriptor)
11114 bandwidth claims. Resolves ticket 8711.
11115 - Update to the June 5 2013 Maxmind GeoLite Country database.
11117 o Removed documentation:
11118 - Remove some of the older contents of doc/ as obsolete; move others
11119 to torspec.git. Fixes bug 8965.
11121 o Code simplification and refactoring:
11122 - Avoid using character buffers when constructing most directory
11123 objects: this approach was unwieldy and error-prone. Instead,
11124 build smartlists of strings, and concatenate them when done.
11127 Changes in version 0.2.4.12-alpha - 2013-04-18
11128 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
11129 process for lengthening the guard rotation period, makes directory
11130 authority opinions in the consensus a bit less gameable, makes socks5
11131 username/password circuit isolation actually work, and fixes a wide
11132 variety of other issues.
11135 - Raise the default time that a client keeps an entry guard from
11136 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
11137 2012 paper. (We would make it even longer, but we need better client
11138 load balancing first.) Also, make the guard lifetime controllable
11139 via a new GuardLifetime torrc option and a GuardLifetime consensus
11140 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
11141 - Directory authorities now prefer using measured bandwidths to
11142 advertised ones when computing flags and thresholds. Resolves
11144 - Directory authorities that have more than a threshold number
11145 of relays with measured bandwidths now treat relays with unmeasured
11146 bandwidths as having bandwidth 0. Resolves ticket 8435.
11148 o Major bugfixes (assert / resource use):
11149 - Avoid a bug where our response to TLS renegotiation under certain
11150 network conditions could lead to a busy-loop, with 100% CPU
11151 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
11152 - Avoid an assertion when we discover that we'd like to write a cell
11153 onto a closing connection: just discard the cell. Fixes another
11154 case of bug 7350; bugfix on 0.2.4.4-alpha.
11156 o Major bugfixes (client-side privacy):
11157 - When we mark a circuit as unusable for new circuits, have it
11158 continue to be unusable for new circuits even if MaxCircuitDirtiness
11159 is increased too much at the wrong time, or the system clock jumps
11160 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
11161 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
11162 which have resolved to internal addresses") is set, apply that
11163 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
11164 - When an exit relay rejects a stream with reason "exit policy", but
11165 we only know an exit policy summary (e.g. from the microdesc
11166 consensus) for it, do not mark the relay as useless for all exiting.
11167 Instead, mark just the circuit as unsuitable for that particular
11168 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
11169 - Allow applications to get proper stream isolation with
11170 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
11171 username/password authentication also offer "no authentication". Tor
11172 had previously preferred "no authentication", so the applications
11173 never actually sent Tor their auth details. Now Tor selects
11174 username/password authentication if it's offered. You can disable
11175 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
11176 bug 8117; bugfix on 0.2.3.3-alpha.
11178 o Major bugfixes (other):
11179 - When unable to find any working directory nodes to use as a
11180 directory guard, give up rather than adding the same non-working
11181 nodes to the directory guard list over and over. Fixes bug 8231;
11182 bugfix on 0.2.4.8-alpha.
11185 - Reject as invalid most directory objects containing a NUL.
11186 Belt-and-suspender fix for bug 8037.
11187 - In our testsuite, create temporary directories with a bit more
11188 entropy in their name to make name collisions less likely. Fixes
11190 - Add CACHED keyword to ADDRMAP events in the control protocol
11191 to indicate whether a DNS result will be cached or not. Resolves
11193 - Update to the April 3 2013 Maxmind GeoLite Country database.
11195 o Minor features (build):
11196 - Detect and reject attempts to build Tor with threading support
11197 when OpenSSL has been compiled without threading support.
11199 - Clarify that when autoconf is checking for nacl, it is checking
11200 specifically for nacl with a fast curve25519 implementation.
11202 - Warn if building on a platform with an unsigned time_t: there
11203 are too many places where Tor currently assumes that time_t can
11204 hold negative values. We'd like to fix them all, but probably
11207 o Minor bugfixes (build):
11208 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
11209 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
11210 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
11211 - Add the old src/or/micro-revision.i filename to CLEANFILES.
11212 On the off chance that somebody has one, it will go away as soon
11213 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
11214 - Build Tor correctly on 32-bit platforms where the compiler can build
11215 but not run code using the "uint128_t" construction. Fixes bug 8587;
11216 bugfix on 0.2.4.8-alpha.
11217 - Fix compilation warning with some versions of clang that would
11218 prefer the -Wswitch-enum compiler flag to warn about switch
11219 statements with missing enum values, even if those switch
11220 statements have a "default:" statement. Fixes bug 8598; bugfix
11223 o Minor bugfixes (protocol):
11224 - Fix the handling of a TRUNCATE cell when it arrives while the
11225 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
11226 - Fix a misframing issue when reading the version numbers in a
11227 VERSIONS cell. Previously we would recognize [00 01 00 02] as
11228 'version 1, version 2, and version 0x100', when it should have
11229 only included versions 1 and 2. Fixes bug 8059; bugfix on
11230 0.2.0.10-alpha. Reported pseudonymously.
11231 - Make the format and order of STREAM events for DNS lookups
11232 consistent among the various ways to launch DNS lookups. Fixes
11233 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
11234 - Correct our check for which versions of Tor support the EXTEND2
11235 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
11236 later, when support was really added in version 0.2.4.8-alpha.
11237 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
11239 o Minor bugfixes (other):
11240 - Correctly store microdescriptors and extrainfo descriptors with
11241 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
11242 Bug reported by "cypherpunks".
11243 - Increase the width of the field used to remember a connection's
11244 link protocol version to two bytes. Harmless for now, since the
11245 only currently recognized versions are one byte long. Reported
11246 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
11247 - If the state file's path bias counts are invalid (presumably from a
11248 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
11249 additional checks and log messages to the scaling of Path Bias
11250 counts, in case there still are remaining issues with scaling.
11251 Should help resolve bug 8235.
11252 - Eliminate several instances where we use "Nickname=ID" to refer to
11253 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
11254 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
11255 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
11257 o Minor bugfixes (syscalls):
11258 - Always check the return values of functions fcntl() and
11259 setsockopt(). We don't believe these are ever actually failing in
11260 practice, but better safe than sorry. Also, checking these return
11261 values should please analysis tools like Coverity. Patch from
11262 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
11263 - Use direct writes rather than stdio when building microdescriptor
11264 caches, in an attempt to mitigate bug 8031, or at least make it
11267 o Minor bugfixes (config):
11268 - When rejecting a configuration because we were unable to parse a
11269 quoted string, log an actual error message. Fixes bug 7950; bugfix
11271 - Behave correctly when the user disables LearnCircuitBuildTimeout
11272 but doesn't tell us what they would like the timeout to be. Fixes
11273 bug 6304; bugfix on 0.2.2.14-alpha.
11274 - When autodetecting the number of CPUs, use the number of available
11275 CPUs in preference to the number of configured CPUs. Inform the
11276 user if this reduces the number of available CPUs. Fixes bug 8002;
11277 bugfix on 0.2.3.1-alpha.
11278 - Make it an error when you set EntryNodes but disable UseGuardNodes,
11279 since it will (surprisingly to some users) ignore EntryNodes. Fixes
11280 bug 8180; bugfix on 0.2.3.11-alpha.
11281 - Allow TestingTorNetworks to override the 4096-byte minimum for
11282 the Fast threshold. Otherwise they can't bootstrap until they've
11283 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
11284 - Fix some logic errors when the user manually overrides the
11285 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
11288 o Minor bugfixes (log messages to help diagnose bugs):
11289 - If we fail to free a microdescriptor because of bug 7164, log
11290 the filename and line number from which we tried to free it.
11291 - Add another diagnostic to the heartbeat message: track and log
11292 overhead that TLS is adding to the data we write. If this is
11293 high, we are sending too little data to SSL_write at a time.
11294 Diagnostic for bug 7707.
11295 - Add more detail to a log message about relaxed timeouts, to help
11297 - Warn more aggressively when flushing microdescriptors to a
11298 microdescriptor cache fails, in an attempt to mitigate bug 8031,
11299 or at least make it more diagnosable.
11300 - Improve debugging output to help track down bug 8185 ("Bug:
11301 outgoing relay cell has n_chan==NULL. Dropping.")
11302 - Log the purpose of a path-bias testing circuit correctly.
11303 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
11305 o Minor bugfixes (0.2.4.x log messages that were too noisy):
11306 - Don't attempt to relax the timeout of already opened 1-hop circuits.
11307 They might never timeout. This should eliminate some/all cases of
11308 the relaxed timeout log message.
11309 - Use circuit creation time for network liveness evaluation. This
11310 should eliminate warning log messages about liveness caused
11311 by changes in timeout evaluation. Fixes bug 6572; bugfix on
11313 - Reduce a path bias length check from notice to info. The message
11314 is triggered when creating controller circuits. Fixes bug 8196;
11315 bugfix on 0.2.4.8-alpha.
11316 - Fix a path state issue that triggered a notice during relay startup.
11317 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
11318 - Reduce occurrences of warns about circuit purpose in
11319 connection_ap_expire_building(). Fixes bug 8477; bugfix on
11322 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
11323 - If we encounter a write failure on a SOCKS connection before we
11324 finish our SOCKS handshake, don't warn that we closed the
11325 connection before we could send a SOCKS reply. Fixes bug 8427;
11326 bugfix on 0.1.0.1-rc.
11327 - Correctly recognize that [::1] is a loopback address. Fixes
11328 bug 8377; bugfix on 0.2.1.3-alpha.
11329 - Fix a directory authority warn caused when we have a large amount
11330 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
11331 - Don't log inappropriate heartbeat messages when hibernating: a
11332 hibernating node is _expected_ to drop out of the consensus,
11333 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
11334 bugfix on 0.2.3.1-alpha.
11335 - Don't complain about bootstrapping problems while hibernating.
11336 These complaints reflect a general code problem, but not one
11337 with any problematic effects (no connections are actually
11338 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
11340 o Documentation fixes:
11341 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
11342 names match. Fixes bug 7768.
11343 - Make the torify manpage no longer refer to tsocks; torify hasn't
11344 supported tsocks since 0.2.3.14-alpha.
11345 - Make the tor manpage no longer reference tsocks.
11346 - Fix the GeoIPExcludeUnknown documentation to refer to
11347 ExcludeExitNodes rather than the currently nonexistent
11348 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
11351 - The tor-tsocks.conf is no longer distributed or installed. We
11352 recommend that tsocks users use torsocks instead. Resolves
11356 Changes in version 0.2.4.11-alpha - 2013-03-11
11357 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
11358 more robust, makes hidden service authentication work again, and
11359 resolves a DPI fingerprint for Tor's SSL transport.
11361 o Major features (directory authorities):
11362 - Directory authorities now support a new consensus method (17)
11363 where they cap the published bandwidth of servers for which
11364 insufficient bandwidth measurements exist. Fixes part of bug 2286.
11365 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
11366 serve any v2 directory information. Now we can test disabling the
11367 old deprecated v2 directory format, and see whether doing so has
11368 any effect on network load. Begins to fix bug 6783.
11369 - Directory authorities now include inside each vote a statement of
11370 the performance thresholds they used when assigning flags.
11371 Implements ticket 8151.
11373 o Major bugfixes (directory authorities):
11374 - Stop marking every relay as having been down for one hour every
11375 time we restart a directory authority. These artificial downtimes
11376 were messing with our Stable and Guard flag calculations. Fixes
11377 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
11379 o Major bugfixes (hidden services):
11380 - Allow hidden service authentication to succeed again. When we
11381 refactored the hidden service introduction code back
11382 in 0.2.4.1-alpha, we didn't update the code that checks
11383 whether authentication information is present, causing all
11384 authentication checks to return "false". Fix for bug 8207; bugfix
11385 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
11387 o Minor features (relays, bridges):
11388 - Make bridge relays check once a minute for whether their IP
11389 address has changed, rather than only every 15 minutes. Resolves
11390 bugs 1913 and 1992.
11391 - Refactor resolve_my_address() so it returns the method by which we
11392 decided our public IP address (explicitly configured, resolved from
11393 explicit hostname, guessed from interfaces, learned by gethostname).
11394 Now we can provide more helpful log messages when a relay guesses
11395 its IP address incorrectly (e.g. due to unexpected lines in
11396 /etc/hosts). Resolves ticket 2267.
11397 - Teach bridge-using clients to avoid 0.2.2 bridges when making
11398 microdescriptor-related dir requests, and only fall back to normal
11399 descriptors if none of their bridges can handle microdescriptors
11400 (as opposed to the fix in ticket 4013, which caused them to fall
11401 back to normal descriptors if *any* of their bridges preferred
11402 them). Resolves ticket 4994.
11403 - Randomize the lifetime of our SSL link certificate, so censors can't
11404 use the static value for filtering Tor flows. Resolves ticket 8443;
11405 related to ticket 4014 which was included in 0.2.2.33.
11406 - Support a new version of the link protocol that allows 4-byte circuit
11407 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
11408 a possible resource exhaustion issue. Closes ticket 7351; implements
11411 o Minor features (portability):
11412 - Tweak the curve25519-donna*.c implementations to tolerate systems
11413 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
11414 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
11415 the signs of types during autoconf. This is better than our old
11416 approach, which didn't work when cross-compiling.
11417 - Detect the sign of enum values, rather than assuming that MSC is the
11418 only compiler where enum types are all signed. Fixes bug 7727;
11419 bugfix on 0.2.4.10-alpha.
11421 o Minor features (other):
11422 - Say "KBytes" rather than "KB" in the man page (for various values
11423 of K), to further reduce confusion about whether Tor counts in
11424 units of memory or fractions of units of memory. Resolves ticket 7054.
11425 - Clear the high bit on curve25519 public keys before passing them to
11426 our backend, in case we ever wind up using a backend that doesn't do
11427 so itself. If we used such a backend, and *didn't* clear the high bit,
11428 we could wind up in a situation where users with such backends would
11429 be distinguishable from users without. Fixes bug 8121; bugfix on
11431 - Update to the March 6 2013 Maxmind GeoLite Country database.
11433 o Minor bugfixes (clients):
11434 - When we receive a RELAY_END cell with the reason DONE, or with no
11435 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
11436 status as "connection refused". Previously we reported these cases
11437 as success but then immediately closed the connection. Fixes bug
11438 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
11439 - Downgrade an assertion in connection_ap_expire_beginning to an
11440 LD_BUG message. The fix for bug 8024 should prevent this message
11441 from displaying, but just in case, a warn that we can diagnose
11442 is better than more assert crashes. Fixes bug 8065; bugfix on
11444 - Lower path use bias thresholds to .80 for notice and .60 for warn.
11445 Also make the rate limiting flags for the path use bias log messages
11446 independent from the original path bias flags. Fixes bug 8161;
11447 bugfix on 0.2.4.10-alpha.
11449 o Minor bugfixes (relays):
11450 - Stop trying to resolve our hostname so often (e.g. every time we
11451 think about doing a directory fetch). Now we reuse the cached
11452 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
11453 and 2410 (bugfix on 0.1.2.2-alpha).
11454 - Stop sending a stray "(null)" in some cases for the server status
11455 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
11457 - When choosing which stream on a formerly stalled circuit to wake
11458 first, make better use of the platform's weak RNG. Previously,
11459 we had been using the % ("modulo") operator to try to generate a
11460 1/N chance of picking each stream, but this behaves badly with
11461 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
11463 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
11464 Irix's random() only return 15 bits; Solaris's random() returns more
11465 bits but its RAND_MAX says it only returns 15, and so on. Motivated
11466 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
11468 o Minor bugfixes (directory authorities):
11469 - Directory authorities now use less space when formatting identical
11470 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
11473 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
11474 - Avoid leaking memory if we fail to compute a consensus signature
11475 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
11476 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
11478 - Fix a memory leak during safe-cookie controller authentication.
11479 Bugfix on 0.2.3.13-alpha.
11480 - Avoid memory leak of IPv6 policy content if we fail to format it into
11481 a router descriptor. Bugfix on 0.2.4.7-alpha.
11483 o Minor bugfixes (other code correctness issues):
11484 - Avoid a crash if we fail to generate an extrainfo descriptor.
11485 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
11486 this is CID 718634.
11487 - When detecting the largest possible file descriptor (in order to
11488 close all file descriptors when launching a new program), actually
11489 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
11490 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
11492 - Fix a copy-and-paste error when adding a missing A1 to a routerset
11493 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
11494 Bugfix on 0.2.4.10-alpha.
11495 - Fix an impossible-to-trigger integer overflow when estimating how
11496 long our onionskin queue would take. (This overflow would require us
11497 to accept 4 million onionskins before processing 100 of them.) Fixes
11498 bug 8210; bugfix on 0.2.4.10-alpha.
11500 o Code simplification and refactoring:
11501 - Add a wrapper function for the common "log a message with a
11505 Changes in version 0.2.4.10-alpha - 2013-02-04
11506 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
11507 certain attacks that flood the network with relays; changes the queue
11508 for circuit create requests from a sized-based limit to a time-based
11509 limit; resumes building with MSVC on Windows; and fixes a wide variety
11512 o Major bugfixes (directory authority):
11513 - When computing directory thresholds, ignore any rejected-as-sybil
11514 nodes during the computation so that they can't influence Fast,
11515 Guard, etc. (We should have done this for proposal 109.) Fixes
11517 - When marking a node as a likely sybil, reset its uptime metrics
11518 to zero, so that it cannot time towards getting marked as Guard,
11519 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
11523 - When a TLS write is partially successful but incomplete, remember
11524 that the flushed part has been flushed, and notice that bytes were
11525 actually written. Reported and fixed pseudonymously. Fixes bug
11526 7708; bugfix on Tor 0.1.0.5-rc.
11527 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
11528 ID: these could be used to create unexpected streams and circuits
11529 which would count as "present" to some parts of Tor but "absent"
11530 to others, leading to zombie circuits and streams or to a bandwidth
11531 denial-of-service. Fixes bug 7889; bugfix on every released version
11532 of Tor. Reported by "oftc_must_be_destroyed".
11533 - Rename all macros in our local copy of queue.h to begin with "TOR_".
11534 This change seems the only good way to permanently prevent conflicts
11535 with queue.h on various operating systems. Fixes bug 8107; bugfix
11538 o Major features (relay):
11539 - Instead of limiting the number of queued onionskins (aka circuit
11540 create requests) to a fixed, hard-to-configure number, we limit
11541 the size of the queue based on how many we expect to be able to
11542 process in a given amount of time. We estimate the time it will
11543 take to process an onionskin based on average processing time
11544 of previous onionskins. Closes ticket 7291. You'll never have to
11545 configure MaxOnionsPending again.
11547 o Major features (portability):
11548 - Resume building correctly with MSVC and Makefile.nmake. This patch
11549 resolves numerous bugs and fixes reported by ultramage, including
11550 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
11551 - Make the ntor and curve25519 code build correctly with MSVC.
11552 Fix on 0.2.4.8-alpha.
11555 - When directory authorities are computing thresholds for flags,
11556 never let the threshold for the Fast flag fall below 4096
11557 bytes. Also, do not consider nodes with extremely low bandwidths
11558 when deciding thresholds for various directory flags. This change
11559 should raise our threshold for Fast relays, possibly in turn
11560 improving overall network performance; see ticket 1854. Resolves
11562 - The Tor client now ignores sub-domain components of a .onion
11563 address. This change makes HTTP "virtual" hosting
11564 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
11565 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
11566 hosted on the same hidden service. Implements proposal 204.
11567 - We compute the overhead from passing onionskins back and forth to
11568 cpuworkers, and report it when dumping statistics in response to
11569 SIGUSR1. Supports ticket 7291.
11571 o Minor features (path selection):
11572 - When deciding whether we have enough descriptors to build circuits,
11573 instead of looking at raw relay counts, look at which fraction
11574 of (bandwidth-weighted) paths we're able to build. This approach
11575 keeps clients from building circuits if their paths are likely to
11576 stand out statistically. The default fraction of paths needed is
11577 taken from the consensus directory; you can override it with the
11578 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
11579 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
11580 and we have GeoIP information, also exclude all nodes with unknown
11581 countries "??" and "A1". This behavior is controlled by the
11582 new GeoIPExcludeUnknown option: you can make such nodes always
11583 excluded with "GeoIPExcludeUnknown 1", and disable the feature
11584 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
11585 gets you the default behavior. Implements feature 7706.
11586 - Path Use Bias: Perform separate accounting for successful circuit
11587 use. Keep separate statistics on stream attempt rates versus stream
11588 success rates for each guard. Provide configurable thresholds to
11589 determine when to emit log messages or disable use of guards that
11590 fail too many stream attempts. Resolves ticket 7802.
11592 o Minor features (log messages):
11593 - When learning a fingerprint for a bridge, log its corresponding
11594 transport type. Implements ticket 7896.
11595 - Improve the log message when "Bug/attack: unexpected sendme cell
11596 from client" occurs, to help us track bug 8093.
11599 - Remove a couple of extraneous semicolons that were upsetting the
11600 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
11601 bugfix on 0.2.2.1-alpha.
11602 - Remove a source of rounding error during path bias count scaling;
11603 don't count cannibalized circuits as used for path bias until we
11604 actually try to use them; and fix a circuit_package_relay_cell()
11605 warning message about n_chan==NULL. Fixes bug 7802.
11606 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
11607 actually link against nacl when we're configured to use it. Fixes
11608 bug 7972; bugfix on 0.2.4.8-alpha.
11609 - Compile correctly with the --disable-curve25519 option. Fixes
11610 bug 8153; bugfix on 0.2.4.8-alpha.
11612 o Build improvements:
11613 - Do not report status verbosely from autogen.sh unless the -v flag
11614 is specified. Fixes issue 4664. Patch from Onizuka.
11615 - Replace all calls to snprintf() outside of src/ext with
11616 tor_snprintf(). Also remove the #define to replace snprintf with
11617 _snprintf on Windows; they have different semantics, and all of
11618 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
11619 - Try to detect if we are ever building on a platform where
11620 memset(...,0,...) does not set the value of a double to 0.0. Such
11621 platforms are permitted by the C standard, though in practice
11622 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
11623 currently support them, but it's better to detect them and fail
11624 than to perform erroneously.
11626 o Removed features:
11627 - Stop exporting estimates of v2 and v3 directory traffic shares
11628 in extrainfo documents. They were unneeded and sometimes inaccurate.
11629 Also stop exporting any v2 directory request statistics. Resolves
11631 - Drop support for detecting and warning about versions of Libevent
11632 before 1.3e. Nothing reasonable ships with them any longer;
11633 warning the user about them shouldn't be needed. Resolves ticket
11636 o Code simplifications and refactoring:
11637 - Rename "isin" functions to "contains", for grammar. Resolves
11639 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
11640 with the natural logarithm function from the system libm. Resolves
11644 Changes in version 0.2.4.9-alpha - 2013-01-15
11645 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
11646 work more robustly.
11649 - Fix backward compatibility logic when receiving an embedded ntor
11650 handshake tunneled in a CREATE cell. This clears up the "Bug:
11651 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
11655 Changes in version 0.2.4.8-alpha - 2013-01-14
11656 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
11657 risks, adds a new stronger and faster circuit handshake, and offers
11658 stronger and faster link encryption when both sides support it.
11661 - Preliminary support for directory guards (proposal 207): when
11662 possible, clients now use their entry guards for non-anonymous
11663 directory requests. This can help prevent client enumeration. Note
11664 that this behavior only works when we have a usable consensus
11665 directory, and when options about what to download are more or less
11666 standard. In the future we should re-bootstrap from our guards,
11667 rather than re-bootstrapping from the preconfigured list of
11668 directory sources that ships with Tor. Resolves ticket 6526.
11669 - Tor relays and clients now support a better CREATE/EXTEND cell
11670 format, allowing the sender to specify multiple address, identity,
11671 and handshake types. Implements Robert Ransom's proposal 200;
11672 closes ticket 7199.
11674 o Major features (new circuit handshake):
11675 - Tor now supports a new circuit extension handshake designed by Ian
11676 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
11677 circuit extension handshake, later called "TAP", was a bit slow
11678 (especially on the relay side), had a fragile security proof, and
11679 used weaker keys than we'd now prefer. The new circuit handshake
11680 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
11681 function, making it significantly more secure than the older
11682 handshake, and significantly faster. Tor can use one of two built-in
11683 pure-C curve25519-donna implementations by Adam Langley, or it
11684 can link against the "nacl" library for a tuned version if present.
11686 The built-in version is very fast for 64-bit systems when building
11687 with GCC. The built-in 32-bit version is still faster than the
11688 old TAP protocol, but using libnacl is better on most such hosts.
11690 Clients don't currently use this protocol by default, since
11691 comparatively few clients support it so far. To try it, set
11692 UseNTorHandshake to 1.
11694 Implements proposal 216; closes ticket 7202.
11696 o Major features (better link encryption):
11697 - Relays can now enable the ECDHE TLS ciphersuites when available
11698 and appropriate. These ciphersuites let us negotiate forward-secure
11699 TLS secret keys more safely and more efficiently than with our
11700 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
11701 public relays prefer the (faster) P224 group, and bridges prefer
11702 the (more common) P256 group; you can override this with the
11705 Enabling these ciphers was a little tricky, since for a long time,
11706 clients had been claiming to support them without actually doing
11707 so, in order to foil fingerprinting. But with the client-side
11708 implementation of proposal 198 in 0.2.3.17-beta, clients can now
11709 match the ciphers from recent Firefox versions *and* list the
11710 ciphers they actually mean, so relays can believe such clients
11711 when they advertise ECDHE support in their TLS ClientHello messages.
11713 This feature requires clients running 0.2.3.17-beta or later,
11714 and requires both sides to be running OpenSSL 1.0.0 or later
11715 with ECC support. OpenSSL 1.0.1, with the compile-time option
11716 "enable-ec_nistp_64_gcc_128", is highly recommended.
11718 Implements the relay side of proposal 198; closes ticket 7200.
11721 - Avoid crashing when, as a relay without IPv6-exit support, a
11722 client insists on getting an IPv6 address or nothing. Fixes bug
11723 7814; bugfix on 0.2.4.7-alpha.
11726 - Improve circuit build timeout handling for hidden services.
11727 In particular: adjust build timeouts more accurately depending
11728 upon the number of hop-RTTs that a particular circuit type
11729 undergoes. Additionally, launch intro circuits in parallel
11730 if they timeout, and take the first one to reply as valid.
11731 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
11732 separate error codes; or at least, don't break for that reason.
11733 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
11734 - Update to the January 2 2013 Maxmind GeoLite Country database.
11736 o Minor features (testing):
11737 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
11738 (P-256) Diffie-Hellman handshakes to src/or/bench.
11739 - Add benchmark functions to test onion handshake performance.
11741 o Minor features (path bias detection):
11742 - Alter the Path Bias log messages to be more descriptive in terms
11743 of reporting timeouts and other statistics.
11744 - Create three levels of Path Bias log messages, as opposed to just
11745 two. These are configurable via consensus as well as via the torrc
11746 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
11747 The default values are 0.70, 0.50, and 0.30 respectively.
11748 - Separate the log message levels from the decision to drop guards,
11749 which also is available via torrc option PathBiasDropGuards.
11750 PathBiasDropGuards still defaults to 0 (off).
11751 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
11752 in combination with PathBiasExtremeRate.
11753 - Increase the default values for PathBiasScaleThreshold and
11754 PathBiasCircThreshold from (200, 20) to (300, 150).
11755 - Add in circuit usage accounting to path bias. If we try to use a
11756 built circuit but fail for any reason, it counts as path bias.
11757 Certain classes of circuits where the adversary gets to pick your
11758 destination node are exempt from this accounting. Usage accounting
11759 can be specifically disabled via consensus parameter or torrc.
11760 - Convert all internal path bias state to double-precision floating
11761 point, to avoid roundoff error and other issues.
11762 - Only record path bias information for circuits that have completed
11763 *two* hops. Assuming end-to-end tagging is the attack vector, this
11764 makes us more resilient to ambient circuit failure without any
11765 detection capability loss.
11767 o Minor bugfixes (log messages):
11768 - Rate-limit the "No circuits are opened. Relaxed timeout for a
11769 circuit with channel state open..." message to once per hour to
11770 keep it from filling the notice logs. Mitigates bug 7799 but does
11771 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
11772 - Avoid spurious warnings when configuring multiple client ports of
11773 which only some are nonlocal. Previously, we had claimed that some
11774 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
11777 o Code simplifications and refactoring:
11778 - Get rid of a couple of harmless clang warnings, where we compared
11779 enums to ints. These warnings are newly introduced in clang 3.2.
11780 - Split the onion.c file into separate modules for the onion queue
11781 and the different handshakes it supports.
11782 - Remove the marshalling/unmarshalling code for sending requests to
11783 cpuworkers over a socket, and instead just send structs. The
11784 recipient will always be the same Tor binary as the sender, so
11785 any encoding is overkill.
11788 Changes in version 0.2.4.7-alpha - 2012-12-24
11789 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
11790 directory mirrors for more robust bootstrapping; fixes more issues where
11791 clients with changing network conditions refuse to make any circuits;
11792 adds initial support for exiting to IPv6 addresses; resumes being able
11793 to update our GeoIP database, and includes the geoip6 file this time;
11794 turns off the client-side DNS cache by default due to privacy risks;
11795 and fixes a variety of other issues.
11797 o Major features (client resilience):
11798 - Add a new "FallbackDir" torrc option to use when we can't use
11799 a directory mirror from the consensus (either because we lack a
11800 consensus, or because they're all down). Currently, all authorities
11801 are fallbacks by default, and there are no other default fallbacks,
11802 but that will change. This option will allow us to give clients a
11803 longer list of servers to try to get a consensus from when first
11804 connecting to the Tor network, and thereby reduce load on the
11805 directory authorities. Implements proposal 206, "Preconfigured
11806 directory sources for bootstrapping". We also removed the old
11807 "FallbackNetworkstatus" option, since we never got it working well
11808 enough to use it. Closes bug 572.
11809 - If we have no circuits open, use a relaxed timeout (the
11810 95-percentile cutoff) until a circuit succeeds. This heuristic
11811 should allow Tor to succeed at building circuits even when the
11812 network connection drastically changes. Should help with bug 3443.
11814 o Major features (IPv6):
11815 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
11816 connectivity, then set the IPv6Exit flag to 1. Also make sure your
11817 exit policy reads as you would like: the address * applies to all
11818 address families, whereas *4 is IPv4 address only, and *6 is IPv6
11819 addresses only. On the client side, you'll need to wait until the
11820 authorities have upgraded, wait for enough exits to support IPv6,
11821 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
11822 ticket 5547, implements proposal 117 as revised in proposal 208.
11824 We DO NOT recommend that clients with actual anonymity needs start
11825 using IPv6 over Tor yet, since not enough exits support it yet.
11827 o Major features (geoip database):
11828 - Maxmind began labelling Tor relays as being in country "A1",
11829 which breaks by-country node selection inside Tor. Now we use a
11830 script to replace "A1" ("Anonymous Proxy") entries in our geoip
11831 file with real country codes. This script fixes about 90% of "A1"
11832 entries automatically and uses manual country code assignments to
11833 fix the remaining 10%. See src/config/README.geoip for details.
11834 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
11835 Country database, as modified above.
11837 o Major bugfixes (client-side DNS):
11838 - Turn off the client-side DNS cache by default. Updating and using
11839 the DNS cache is now configurable on a per-client-port
11840 level. SOCKSPort, DNSPort, etc lines may now contain
11841 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
11842 cache these types of DNS answers when we receive them from an
11843 exit node in response to an application request on this port, and
11844 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
11845 cached DNS answers of these types, we shouldn't use them. It's
11846 potentially risky to use cached DNS answers at the client, since
11847 doing so can indicate to one exit what answers we've gotten
11848 for DNS lookups in the past. With IPv6, this becomes especially
11849 problematic. Using cached DNS answers for requests on the same
11850 circuit would present less linkability risk, since all traffic
11851 on a circuit is already linkable, but it would also provide
11852 little performance benefit: the exit node caches DNS replies
11853 too. Implements a simplified version of Proposal 205. Implements
11856 o Major bugfixes (other):
11857 - Alter circuit build timeout measurement to start at the point
11858 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
11859 initialization). This should make our timeout measurements more
11860 uniform. Previously, we were sometimes including ORconn setup time
11861 in our circuit build time measurements. Should resolve bug 3443.
11862 - Fix an assertion that could trigger in hibernate_go_dormant() when
11863 closing an or_connection_t: call channel_mark_for_close() rather
11864 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
11866 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
11867 7655; bugfix on 0.2.4.6-alpha.
11870 - Add a new torrc option "ServerTransportListenAddr" to let bridge
11871 operators select the address where their pluggable transports will
11872 listen for connections. Resolves ticket 7013.
11873 - Allow an optional $ before the node identity digest in the
11874 controller command GETINFO ns/id/<identity>, for consistency with
11875 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
11876 - Log packaged cell fullness as part of the heartbeat message.
11877 Diagnosis to try to determine the extent of bug 7743.
11879 o Minor features (IPv6):
11880 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
11881 prefer to hand out virtual IPv6 addresses, since there are more of
11882 them and we can't run out. To override this behavior and make IPv4
11883 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
11884 or DNSPort you're using for resolving. Implements ticket 7571.
11885 - AutomapHostsOnResolve responses are now randomized, to avoid
11886 annoying situations where Tor is restarted and applications
11887 connect to the wrong addresses.
11888 - Never try more than 1000 times to pick a new virtual address when
11889 AutomapHostsOnResolve is set. That's good enough so long as we
11890 aren't close to handing out our entire virtual address space;
11891 if you're getting there, it's best to switch to IPv6 virtual
11895 - The ADDRMAP command can no longer generate an ill-formed error
11896 code on a failed MAPADDRESS. It now says "internal" rather than
11897 an English sentence fragment with spaces in the middle. Bugfix on
11898 Tor 0.2.0.19-alpha.
11899 - Fix log messages and comments to avoid saying "GMT" when we mean
11900 "UTC". Fixes bug 6113.
11901 - Compile on win64 using mingw64. Fixes bug 7260; patches from
11903 - Fix a crash when debugging unit tests on Windows: deallocate a
11904 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
11905 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
11908 - The DirServer option is now DirAuthority, for consistency with
11909 current naming patterns. You can still use the old DirServer form.
11911 o Code simplification and refactoring:
11912 - Move the client-side address-map/virtual-address/DNS-cache code
11913 out of connection_edge.c into a new addressmap.c module.
11914 - Remove unused code for parsing v1 directories and "running routers"
11915 documents. Fixes bug 6887.
11918 Changes in version 0.2.3.25 - 2012-11-19
11919 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
11920 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
11921 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
11922 programmer, and friend. Unstinting in his dedication to the cause of
11923 freedom, he inspired and helped many of us as we began our work on
11924 anonymity, and inspires us still. Please honor his memory by writing
11925 software to protect people's freedoms, and by helping others to do so.
11927 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
11928 significantly reduced directory overhead (via microdescriptors),
11929 enormous crypto performance improvements for fast relays on new
11930 enough hardware, a new v3 TLS handshake protocol that can better
11931 resist fingerprinting, support for protocol obfuscation plugins (aka
11932 pluggable transports), better scalability for hidden services, IPv6
11933 support for bridges, performance improvements like allowing clients
11934 to skip the first round-trip on the circuit ("optimistic data") and
11935 refilling token buckets more often, a new "stream isolation" design
11936 to isolate different applications on different circuits, and many
11937 stability, security, and privacy fixes.
11940 - Tor tries to wipe potentially sensitive data after using it, so
11941 that if some subsequent security failure exposes Tor's memory,
11942 the damage will be limited. But we had a bug where the compiler
11943 was eliminating these wipe operations when it decided that the
11944 memory was no longer visible to a (correctly running) program,
11945 hence defeating our attempt at defense in depth. We fix that
11946 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
11947 is unlikely to optimize away. Future versions of Tor may use
11948 a less ridiculously heavy approach for this. Fixes bug 7352.
11949 Reported in an article by Andrey Karpov.
11952 - Fix a harmless bug when opting against publishing a relay descriptor
11953 because DisableNetwork is set. Fixes bug 7464; bugfix on
11957 Changes in version 0.2.4.6-alpha - 2012-11-13
11958 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
11959 makes our defense-in-depth memory wiping more reliable, and begins to
11960 count IPv6 addresses in bridge statistics,
11963 - Fix an assertion failure that could occur when closing a connection
11964 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
11966 - Tor tries to wipe potentially sensitive data after using it, so
11967 that if some subsequent security failure exposes Tor's memory,
11968 the damage will be limited. But we had a bug where the compiler
11969 was eliminating these wipe operations when it decided that the
11970 memory was no longer visible to a (correctly running) program,
11971 hence defeating our attempt at defense in depth. We fix that
11972 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
11973 is unlikely to optimize away. Future versions of Tor may use
11974 a less ridiculously heavy approach for this. Fixes bug 7352.
11975 Reported in an article by Andrey Karpov.
11978 - Add GeoIP database for IPv6 addresses. The new config option
11980 - Bridge statistics now count bridge clients connecting over IPv6:
11981 bridge statistics files now list "bridge-ip-versions" and
11982 extra-info documents list "geoip6-db-digest". The control protocol
11983 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
11984 implementation by "shkoo", addressing ticket 5055.
11987 - Warn when we are binding low ports when hibernation is enabled;
11988 previously we had warned when we were _advertising_ low ports with
11989 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
11990 - Fix a harmless bug when opting against publishing a relay descriptor
11991 because DisableNetwork is set. Fixes bug 7464; bugfix on
11993 - Add warning message when a managed proxy dies during configuration.
11994 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
11995 - Fix a linking error when building tor-fw-helper without miniupnp.
11996 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
11997 - Check for closing an or_connection_t without going through correct
11998 channel functions; emit a warning and then call
11999 connection_or_close_for_error() so we don't assert as in bugs 7212
12001 - Compile correctly on compilers without C99 designated initializer
12002 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
12003 - Avoid a possible assert that can occur when channel_send_destroy() is
12004 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
12005 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
12006 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
12007 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
12008 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
12010 o Code simplification and refactoring:
12011 - Start using OpenBSD's implementation of queue.h, so that we don't
12012 need to hand-roll our own pointer and list structures whenever we
12013 need them. (We can't rely on a sys/queue.h, since some operating
12014 systems don't have them, and the ones that do have them don't all
12015 present the same extensions.)
12018 Changes in version 0.2.4.5-alpha - 2012-10-25
12019 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
12020 two important security vulnerabilities that could lead to remotely
12021 triggerable relay crashes, fix a major bug that was preventing clients
12022 from choosing suitable exit nodes, and refactor some of our code.
12024 o Major bugfixes (security, also in 0.2.3.24-rc):
12025 - Fix a group of remotely triggerable assertion failures related to
12026 incorrect link protocol negotiation. Found, diagnosed, and fixed
12027 by "some guy from France". Fix for CVE-2012-2250; bugfix on
12029 - Fix a denial of service attack by which any directory authority
12030 could crash all the others, or by which a single v2 directory
12031 authority could crash everybody downloading v2 directory
12032 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
12034 o Major bugfixes (also in 0.2.3.24-rc):
12035 - When parsing exit policy summaries from microdescriptors, we had
12036 previously been ignoring the last character in each one, so that
12037 "accept 80,443,8080" would be treated by clients as indicating
12038 a node that allows access to ports 80, 443, and 808. That would
12039 lead to clients attempting connections that could never work,
12040 and ignoring exit nodes that would support their connections. Now
12041 clients parse these exit policy summaries correctly. Fixes bug 7192;
12042 bugfix on 0.2.3.1-alpha.
12044 o Minor bugfixes (also in 0.2.3.24-rc):
12045 - Clients now consider the ClientRejectInternalAddresses config option
12046 when using a microdescriptor consensus stanza to decide whether
12047 an exit relay would allow exiting to an internal address. Fixes
12048 bug 7190; bugfix on 0.2.3.1-alpha.
12051 - Only disable TLS session ticket support when running as a TLS
12052 server. Now clients will blend better with regular Firefox
12053 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
12055 o Code simplification and refactoring:
12056 - Start using OpenBSD's implementation of queue.h (originally by
12058 - Move the entry node code from circuitbuild.c to its own file.
12059 - Move the circuit build timeout tracking code from circuitbuild.c
12063 Changes in version 0.2.3.24-rc - 2012-10-25
12064 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
12065 could lead to remotely triggerable relay crashes, and fixes
12066 a major bug that was preventing clients from choosing suitable exit
12069 o Major bugfixes (security):
12070 - Fix a group of remotely triggerable assertion failures related to
12071 incorrect link protocol negotiation. Found, diagnosed, and fixed
12072 by "some guy from France". Fix for CVE-2012-2250; bugfix on
12074 - Fix a denial of service attack by which any directory authority
12075 could crash all the others, or by which a single v2 directory
12076 authority could crash everybody downloading v2 directory
12077 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
12080 - When parsing exit policy summaries from microdescriptors, we had
12081 previously been ignoring the last character in each one, so that
12082 "accept 80,443,8080" would be treated by clients as indicating
12083 a node that allows access to ports 80, 443, and 808. That would
12084 lead to clients attempting connections that could never work,
12085 and ignoring exit nodes that would support their connections. Now
12086 clients parse these exit policy summaries correctly. Fixes bug 7192;
12087 bugfix on 0.2.3.1-alpha.
12090 - Clients now consider the ClientRejectInternalAddresses config option
12091 when using a microdescriptor consensus stanza to decide whether
12092 an exit relay would allow exiting to an internal address. Fixes
12093 bug 7190; bugfix on 0.2.3.1-alpha.
12096 Changes in version 0.2.4.4-alpha - 2012-10-20
12097 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
12098 vulnerability introduced by a change in OpenSSL, fixes a remotely
12099 triggerable assert, and adds new channel_t and circuitmux_t abstractions
12100 that will make it easier to test new connection transport and cell
12101 scheduling algorithms.
12103 o New directory authorities (also in 0.2.3.23-rc):
12104 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
12105 authority. Closes ticket 5749.
12107 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
12108 - Disable TLS session tickets. OpenSSL's implementation was giving
12109 our TLS session keys the lifetime of our TLS context objects, when
12110 perfect forward secrecy would want us to discard anything that
12111 could decrypt a link connection as soon as the link connection
12112 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
12113 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
12114 - Discard extraneous renegotiation attempts once the V3 link
12115 protocol has been initiated. Failure to do so left us open to
12116 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
12117 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
12119 o Internal abstraction features:
12120 - Introduce new channel_t abstraction between circuits and
12121 or_connection_t to allow for implementing alternate OR-to-OR
12122 transports. A channel_t is an abstract object which can either be a
12123 cell-bearing channel, which is responsible for authenticating and
12124 handshaking with the remote OR and transmitting cells to and from
12125 it, or a listening channel, which spawns new cell-bearing channels
12126 at the request of remote ORs. Implements part of ticket 6465.
12127 - Also new is the channel_tls_t subclass of channel_t, adapting it
12128 to the existing or_connection_t code. The V2/V3 protocol handshaking
12129 code which formerly resided in command.c has been moved below the
12130 channel_t abstraction layer and may be found in channeltls.c now.
12131 Implements the rest of ticket 6465.
12132 - Introduce new circuitmux_t storing the queue of circuits for
12133 a channel; this encapsulates and abstracts the queue logic and
12134 circuit selection policy, and allows the latter to be overridden
12135 easily by switching out a policy object. The existing EWMA behavior
12136 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
12138 o Required libraries:
12139 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
12140 strongly recommended.
12143 - Warn users who run hidden services on a Tor client with
12144 UseEntryGuards disabled that their hidden services will be
12145 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
12146 attack which motivated Tor to support entry guards in the first
12147 place). Resolves ticket 6889.
12148 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
12149 dhill. Resolves ticket 6982.
12150 - Option OutboundBindAddress can be specified multiple times and
12151 accepts IPv6 addresses. Resolves ticket 6876.
12153 o Minor bugfixes (also in 0.2.3.23-rc):
12154 - Don't serve or accept v2 hidden service descriptors over a
12155 relay's DirPort. It's never correct to do so, and disabling it
12156 might make it more annoying to exploit any bugs that turn up in the
12157 descriptor-parsing code. Fixes bug 7149.
12158 - Fix two cases in src/or/transports.c where we were calling
12159 fmt_addr() twice in a parameter list. Bug found by David
12160 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
12161 - Fix memory leaks whenever we logged any message about the "path
12162 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
12163 - When relays refuse a "create" cell because their queue of pending
12164 create cells is too big (typically because their cpu can't keep up
12165 with the arrival rate), send back reason "resource limit" rather
12166 than reason "internal", so network measurement scripts can get a
12167 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
12170 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
12171 - Free some more still-in-use memory at exit, to make hunting for
12172 memory leaks easier. Resolves bug 7029.
12173 - When a Tor client gets a "truncated" relay cell, the first byte of
12174 its payload specifies why the circuit was truncated. We were
12175 ignoring this 'reason' byte when tearing down the circuit, resulting
12176 in the controller not being told why the circuit closed. Now we
12177 pass the reason from the truncated cell to the controller. Bugfix
12178 on 0.1.2.3-alpha; fixes bug 7039.
12179 - Downgrade "Failed to hand off onionskin" messages to "debug"
12180 severity, since they're typically redundant with the "Your computer
12181 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
12182 - Make clients running with IPv6 bridges connect over IPv6 again,
12183 even without setting new config options ClientUseIPv6 and
12184 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
12185 - Use square brackets around IPv6 addresses in numerous places
12186 that needed them, including log messages, HTTPS CONNECT proxy
12187 requests, TransportProxy statefile entries, and pluggable transport
12188 extra-info lines. Fixes bug 7011; patch by David Fifield.
12190 o Code refactoring and cleanup:
12191 - Source files taken from other packages now reside in src/ext;
12192 previously they were scattered around the rest of Tor.
12193 - Avoid use of reserved identifiers in our C code. The C standard
12194 doesn't like us declaring anything that starts with an
12195 underscore, so let's knock it off before we get in trouble. Fix
12196 for bug 1031; bugfix on the first Tor commit.
12199 Changes in version 0.2.3.23-rc - 2012-10-20
12200 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
12201 vulnerability introduced by a change in OpenSSL, and fixes a variety
12202 of smaller bugs in preparation for the release.
12204 o New directory authorities:
12205 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
12206 authority. Closes ticket 5749.
12208 o Major bugfixes (security/privacy):
12209 - Disable TLS session tickets. OpenSSL's implementation was giving
12210 our TLS session keys the lifetime of our TLS context objects, when
12211 perfect forward secrecy would want us to discard anything that
12212 could decrypt a link connection as soon as the link connection
12213 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
12214 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
12215 - Discard extraneous renegotiation attempts once the V3 link
12216 protocol has been initiated. Failure to do so left us open to
12217 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
12218 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
12221 - Fix a possible crash bug when checking for deactivated circuits
12222 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
12223 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
12225 o Minor bugfixes (on 0.2.3.x):
12226 - Fix two cases in src/or/transports.c where we were calling
12227 fmt_addr() twice in a parameter list. Bug found by David
12228 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
12229 - Convert an assert in the pathbias code to a log message. The assert
12230 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
12231 bugfix on 0.2.3.17-beta.
12232 - Fix memory leaks whenever we logged any message about the "path
12233 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
12235 o Minor bugfixes (on 0.2.2.x and earlier):
12236 - Don't serve or accept v2 hidden service descriptors over a relay's
12237 DirPort. It's never correct to do so, and disabling it might
12238 make it more annoying to exploit any bugs that turn up in the
12239 descriptor-parsing code. Fixes bug 7149.
12240 - When relays refuse a "create" cell because their queue of pending
12241 create cells is too big (typically because their cpu can't keep up
12242 with the arrival rate), send back reason "resource limit" rather
12243 than reason "internal", so network measurement scripts can get a
12244 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
12245 - Correct file sizes when reading binary files on Cygwin, to avoid
12246 a bug where Tor would fail to read its state file. Fixes bug 6844;
12247 bugfix on 0.1.2.7-alpha.
12248 - Avoid undefined behavior when parsing the list of supported
12249 rendezvous/introduction protocols in a hidden service descriptor.
12250 Previously, Tor would have confused (as-yet-unused) protocol version
12251 numbers greater than 32 with lower ones on many platforms. Fixes
12252 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
12254 o Documentation fixes:
12255 - Clarify that hidden services are TCP only. Fixes bug 6024.
12258 Changes in version 0.2.4.3-alpha - 2012-09-22
12259 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
12260 assertion, resumes letting relays test reachability of their DirPort,
12261 and cleans up a bunch of smaller bugs.
12264 - Fix an assertion failure in tor_timegm() that could be triggered
12265 by a badly formatted directory object. Bug found by fuzzing with
12266 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12269 - Fix a possible crash bug when checking for deactivated circuits
12270 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
12271 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
12272 - Allow routers to detect that their own DirPorts are running. When
12273 we removed support for versions_supports_begindir, we also
12274 accidentally removed the mechanism we used to self-test our
12275 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
12276 bugfix on 0.2.4.2-alpha.
12278 o Security features:
12279 - Switch to a completely time-invariant approach for picking nodes
12280 weighted by bandwidth. Our old approach would run through the
12281 part of the loop after it had made its choice slightly slower
12282 than it ran through the part of the loop before it had made its
12283 choice. Addresses ticket 6538.
12284 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
12285 by tor2web clients allows hidden services to identify tor2web
12286 clients through their repeated selection of the same rendezvous
12287 and introduction point circuit endpoints (their guards). Resolves
12291 - Enable Tor to read configuration, state, and key information from
12292 a FIFO. Previously Tor would only read from files with a positive
12293 stat.st_size. Code from meejah; fixes bug 6044.
12296 - Correct file sizes when reading binary files on Cygwin, to avoid
12297 a bug where Tor would fail to read its state file. Fixes bug 6844;
12298 bugfix on 0.1.2.7-alpha.
12299 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
12300 bugfix on 0.2.0.3-alpha.
12301 - When complaining about a client port on a public address, log
12302 which address we're complaining about. Fixes bug 4020; bugfix on
12303 0.2.3.3-alpha. Patch by Tom Fitzhenry.
12304 - Convert an assert in the pathbias code to a log message. The assert
12305 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
12306 bugfix on 0.2.3.17-beta.
12307 - Our new buildsystem was overzealous about rebuilding manpages: it
12308 would rebuild them all whenever any one of them changed. Now our
12309 dependency checking should be correct. Fixes bug 6843; bugfix on
12311 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
12312 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
12313 - Correct log printout about which address family is preferred
12314 when connecting to a bridge with both an IPv4 and IPv6 OR port.
12315 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
12317 o Minor bugfixes (code cleanliness):
12318 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
12319 with large values. This situation was untriggered, but nevertheless
12320 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
12321 - Reject consensus votes with more than 64 known-flags. We aren't even
12322 close to that limit yet, and our code doesn't handle it correctly.
12323 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
12324 - Avoid undefined behavior when parsing the list of supported
12325 rendezvous/introduction protocols in a hidden service descriptor.
12326 Previously, Tor would have confused (as-yet-unused) protocol version
12327 numbers greater than 32 with lower ones on many platforms. Fixes
12328 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
12329 - Fix handling of rendezvous client authorization types over 8.
12330 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
12331 - Fix building with older versions of GCC (2.95, for one) that don't
12332 like preprocessor directives inside macro arguments. Found by
12333 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
12334 - Switch weighted node selection rule from using a list of doubles
12335 to using a list of int64_t. This change should make the process
12336 slightly easier to debug and maintain. Needed to finish ticket 6538.
12338 o Code simplification and refactoring:
12339 - Move the generic "config" code into a new file, and have "config.c"
12340 hold only torrc- and state-related code. Resolves ticket 6823.
12341 - Move the core of our "choose a weighted element at random" logic
12342 into its own function, and give it unit tests. Now the logic is
12343 testable, and a little less fragile too.
12344 - Removed the testing_since field of node_t, which hasn't been used
12345 for anything since 0.2.0.9-alpha.
12347 o Documentation fixes:
12348 - Clarify that hidden services are TCP only. Fixes bug 6024.
12349 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
12353 Changes in version 0.2.3.22-rc - 2012-09-11
12354 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
12358 - Fix an assertion failure in tor_timegm() that could be triggered
12359 by a badly formatted directory object. Bug found by fuzzing with
12360 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12363 - Avoid segfault when starting up having run with an extremely old
12364 version of Tor and parsing its state file. Fixes bug 6801; bugfix
12368 Changes in version 0.2.2.39 - 2012-09-11
12369 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
12373 - Fix an assertion failure in tor_timegm() that could be triggered
12374 by a badly formatted directory object. Bug found by fuzzing with
12375 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12376 - Do not crash when comparing an address with port value 0 to an
12377 address policy. This bug could have been used to cause a remote
12378 assertion failure by or against directory authorities, or to
12379 allow some applications to crash clients. Fixes bug 6690; bugfix
12383 Changes in version 0.2.4.2-alpha - 2012-09-10
12384 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
12385 raises the default rate limiting even more, and makes the bootstrapping
12386 log messages less noisy.
12389 - Automatically forward the TCP ports of pluggable transport
12390 proxies using tor-fw-helper if PortForwarding is enabled. Implements
12394 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
12395 to 1GB/1GB. The previous defaults were intended to be "basically
12396 infinite", but it turns out they're now limiting our 100mbit+
12397 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
12398 last time we raised it).
12401 - Detect when we're running with a version of OpenSSL other than the
12402 one we compiled with. This has occasionally given people hard-to-
12404 - Log fewer lines at level "notice" about our OpenSSL and Libevent
12405 versions and capabilities when everything is going right. Resolves
12406 part of ticket 6736.
12407 - Directory authorities no long accept descriptors for any version of
12408 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
12409 These versions are insecure, unsupported, or both. Implements
12413 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
12414 to start with a triple-underscore so the controller won't touch it.
12415 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
12416 - Avoid segfault when starting up having run with an extremely old
12417 version of Tor and parsing its state file. Fixes bug 6801; bugfix
12419 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
12420 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
12421 - Don't follow the NULL pointer if microdescriptor generation fails.
12422 (This does not appear to be triggerable, but it's best to be safe.)
12423 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
12424 - Fix mis-declared dependencies on src/common/crypto.c and
12425 src/or/tor_main.c that could break out-of-tree builds under some
12426 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
12427 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
12428 6778; bugfix on 0.2.4.1-alpha.
12429 - Fix a harmless (in this case) build warning for implicitly
12430 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
12432 o Removed features:
12433 - Now that all versions before 0.2.2.x are disallowed, we no longer
12434 need to work around their missing features. Thus we can remove a
12435 bunch of compatibility code.
12437 o Code refactoring:
12438 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
12439 TCP ports to forward. In the past it only accepted two ports:
12440 the ORPort and the DirPort.
12443 Changes in version 0.2.4.1-alpha - 2012-09-05
12444 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
12445 bridgedb; lets relays use IPv6 addresses and directory authorities
12446 advertise them; and switches to a cleaner build interface.
12448 This is the first alpha release in a new series, so expect there to
12449 be bugs. Users who would rather test out a more stable branch should
12450 stay with 0.2.3.x for now.
12452 o Major features (bridges):
12453 - Bridges now report the pluggable transports they support to the
12454 bridge authority, so it can pass the supported transports on to
12455 bridgedb and/or eventually do reachability testing. Implements
12458 o Major features (IPv6):
12459 - Bridge authorities now accept IPv6 bridge addresses and include
12460 them in network status documents. Implements ticket 5534.
12461 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
12462 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
12463 to happen. Implements ticket 5535.
12464 - All kind of relays, not just bridges, can now advertise an IPv6
12465 OR port. Implements ticket 6362.
12466 - Directory authorities vote on IPv6 OR ports using the new consensus
12467 method 14. Implements ticket 6363.
12469 o Major features (build):
12470 - Switch to a nonrecursive Makefile structure. Now instead of each
12471 Makefile.am invoking other Makefile.am's, there is a master
12472 Makefile.am that includes the others. This change makes our build
12473 process slightly more maintainable, and improves parallelism for
12474 building with make -j. Original patch by Stewart Smith; various
12475 fixes by Jim Meyering.
12476 - Where available, we now use automake's "silent" make rules by
12477 default, so that warnings are easier to spot. You can get the old
12478 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
12480 o Minor features (code security and spec conformance):
12481 - Clear keys and key-derived material left on the stack in
12482 rendservice.c and rendclient.c. Check return value of
12483 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
12484 These fixes should make us more forward-secure against cold-boot
12485 attacks and the like. Fixes bug 2385.
12486 - Reject EXTEND cells sent to nonexistent streams. According to the
12487 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
12488 we were only checking for stream IDs that were currently in use.
12489 Found while hunting for more instances of bug 6271. Bugfix on
12490 0.0.2pre8, which introduced incremental circuit construction.
12492 o Minor features (streamlining);
12493 - No longer include the "opt" prefix when generating routerinfos
12494 or v2 directories: it has been needless since Tor 0.1.2. Closes
12496 - Remove some now-needless code that tried to aggressively flush
12497 OR connections as data was added to them. Since 0.2.0.1-alpha, our
12498 cell queue logic has saved us from the failure mode that this code
12499 was supposed to prevent. Removing this code will limit the number
12500 of baroque control flow paths through Tor's network logic. Reported
12501 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
12503 o Minor features (controller):
12504 - Add a "GETINFO signal/names" control port command. Implements
12506 - Provide default values for all options via "GETINFO config/defaults".
12507 Implements ticket 4971.
12509 o Minor features (IPv6):
12510 - New config option "AuthDirHasIPv6Connectivity 1" that directory
12511 authorities should set if they have IPv6 connectivity and want to
12512 do reachability tests for IPv6 relays. Implements feature 5974.
12513 - A relay with an IPv6 OR port now sends that address in NETINFO
12514 cells (in addition to its other address). Implements ticket 6364.
12516 o Minor features (log messages):
12517 - Omit the first heartbeat log message, because it never has anything
12518 useful to say, and it clutters up the bootstrapping messages.
12519 Resolves ticket 6758.
12520 - Don't log about reloading the microdescriptor cache at startup. Our
12521 bootstrap warnings are supposed to tell the user when there's a
12522 problem, and our bootstrap notices say when there isn't. Resolves
12523 ticket 6759; bugfix on 0.2.2.6-alpha.
12524 - Don't log "I learned some more directory information" when we're
12525 reading cached directory information. Reserve it for when new
12526 directory information arrives in response to a fetch. Resolves
12528 - Prevent rounding error in path bias counts when scaling
12529 them down, and use the correct scale factor default. Also demote
12530 some path bias related log messages down a level and make others
12531 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
12532 - We no longer warn so much when generating manpages from their
12535 o Code simplifications and refactoring:
12536 - Enhance our internal sscanf replacement so that we can eliminate
12537 the last remaining uses of the system sscanf. (Though those uses
12538 of sscanf were safe, sscanf itself is generally error prone, so
12539 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
12541 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
12542 - Move last_reachable and testing_since from routerinfo_t to node_t.
12543 Implements ticket 5529.
12544 - Add replaycache_t structure, functions and unit tests, then refactor
12545 rend_service_introduce() to be more clear to read, improve, debug,
12546 and test. Resolves bug 6177.
12547 - Finally remove support for malloc_good_size and malloc_usable_size.
12548 We had hoped that these functions would let us eke a little more
12549 memory out of our malloc implementation. Unfortunately, the only
12550 implementations that provided these functions are also ones that
12551 are already efficient about not overallocation: they never got us
12552 more than 7 or so bytes per allocation. Removing them saves us a
12553 little code complexity and a nontrivial amount of build complexity.
12555 o New requirements:
12556 - Tor maintainers now require Automake version 1.9 or later to build
12557 Tor from the Git repository. (Automake is not required when building
12558 from a source distribution.)
12561 Changes in version 0.2.3.21-rc - 2012-09-05
12562 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
12563 series. It fixes a trio of potential security bugs, fixes a bug where
12564 we were leaving some of the fast relays out of the microdescriptor
12565 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
12566 and cleans up other smaller issues.
12568 o Major bugfixes (security):
12569 - Tear down the circuit if we get an unexpected SENDME cell. Clients
12570 could use this trick to make their circuits receive cells faster
12571 than our flow control would have allowed, or to gum up the network,
12572 or possibly to do targeted memory denial-of-service attacks on
12573 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
12574 from July 2002, before the release of Tor 0.0.0. We had committed
12575 this patch previously, but we had to revert it because of bug 6271.
12576 Now that 6271 is fixed, this patch appears to work.
12577 - Reject any attempt to extend to an internal address. Without
12578 this fix, a router could be used to probe addresses on an internal
12579 network to see whether they were accepting connections. Fixes bug
12580 6710; bugfix on 0.0.8pre1.
12581 - Do not crash when comparing an address with port value 0 to an
12582 address policy. This bug could have been used to cause a remote
12583 assertion failure by or against directory authorities, or to
12584 allow some applications to crash clients. Fixes bug 6690; bugfix
12588 - Remove the upper bound on microdescriptor length. We were hitting
12589 the limit for routers with complex exit policies or family
12590 declarations, causing clients to not use them. Fixes the first
12591 piece of bug 6404; fix on 0.2.2.6-alpha.
12592 - Detect "ORPort 0" as meaning, uniformly, that we're not running
12593 as a relay. Previously, some of our code would treat the presence
12594 of any ORPort line as meaning that we should act like a relay,
12595 even though our new listener code would correctly not open any
12596 ORPorts for ORPort 0. Similar bugs in other Port options are also
12597 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
12600 - Avoid a pair of double-free and use-after-mark bugs that can
12601 occur with certain timings in canceled and re-received DNS
12602 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
12603 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
12604 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
12605 - Allow one-hop directory fetching circuits the full "circuit build
12606 timeout" period, rather than just half of it, before failing them
12607 and marking the relay down. This fix should help reduce cases where
12608 clients declare relays (or worse, bridges) unreachable because
12609 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
12610 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
12612 - Authorities no longer include any router in their microdescriptor
12613 consensuses for which they couldn't generate or agree on a
12614 microdescriptor. Fixes the second piece of bug 6404; fix on
12616 - Detect and reject attempts to specify both "FooPort" and
12617 "FooPort 0" in the same configuration domain. (It's still okay
12618 to have a FooPort in your configuration file, and use "FooPort 0"
12619 on the command line to disable it.) Fixes the second half of bug
12620 6507; bugfix on 0.2.3.3-alpha.
12621 - Make wildcarded addresses (that is, ones beginning with "*.") work
12622 when provided via the controller's MapAddress command. Previously,
12623 they were accepted, but we never actually noticed that they were
12624 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
12625 - Avoid crashing on a malformed state file where EntryGuardPathBias
12626 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
12627 - Add a (probably redundant) memory clear between iterations of
12628 the router status voting loop, to prevent future coding errors
12629 where data might leak between iterations of the loop. Resolves
12632 o Minor bugfixes (log messages):
12633 - Downgrade "set buildtimeout to low value" messages to "info"
12634 severity; they were never an actual problem, there was never
12635 anything reasonable to do about them, and they tended to spam logs
12636 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
12637 - Downgrade path-bias warning messages to "info". We'll try to get
12638 them working better in 0.2.4. Add internal circuit construction
12639 state to protect against the noisy warn message "Unexpectedly high
12640 circuit_successes". Also add some additional rate-limited notice
12641 messages to help determine the root cause of the warn. Fixes bug
12642 6475. Bugfix against 0.2.3.17-beta.
12643 - Move log message when unable to find a microdesc in a routerstatus
12644 entry to parse time. Previously we'd spam this warning every time
12645 we tried to figure out which microdescriptors to download. Fixes
12646 the third piece of bug 6404; fix on 0.2.3.18-rc.
12649 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
12650 change when the authority is deciding whether to accept a newly
12651 uploaded descriptor. Implements ticket 6423.
12652 - Add missing documentation for consensus and microdesc files.
12653 Resolves ticket 6732.
12656 Changes in version 0.2.2.38 - 2012-08-12
12657 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
12658 attack that could in theory leak path information.
12661 - Avoid an uninitialized memory read when reading a vote or consensus
12662 document that has an unrecognized flavor name. This read could
12663 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12664 - Try to leak less information about what relays a client is
12665 choosing to a side-channel attacker. Previously, a Tor client would
12666 stop iterating through the list of available relays as soon as it
12667 had chosen one, thus finishing a little earlier when it picked
12668 a router earlier in the list. If an attacker can recover this
12669 timing information (nontrivial but not proven to be impossible),
12670 they could learn some coarse-grained information about which relays
12671 a client was picking (middle nodes in particular are likelier to
12672 be affected than exits). The timing attack might be mitigated by
12673 other factors (see bug 6537 for some discussion), but it's best
12674 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12677 Changes in version 0.2.3.20-rc - 2012-08-05
12678 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
12679 series. It fixes a pair of code security bugs and a potential anonymity
12680 issue, updates our RPM spec files, and cleans up other smaller issues.
12683 - Avoid read-from-freed-memory and double-free bugs that could occur
12684 when a DNS request fails while launching it. Fixes bug 6480;
12685 bugfix on 0.2.0.1-alpha.
12686 - Avoid an uninitialized memory read when reading a vote or consensus
12687 document that has an unrecognized flavor name. This read could
12688 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12689 - Try to leak less information about what relays a client is
12690 choosing to a side-channel attacker. Previously, a Tor client would
12691 stop iterating through the list of available relays as soon as it
12692 had chosen one, thus finishing a little earlier when it picked
12693 a router earlier in the list. If an attacker can recover this
12694 timing information (nontrivial but not proven to be impossible),
12695 they could learn some coarse-grained information about which relays
12696 a client was picking (middle nodes in particular are likelier to
12697 be affected than exits). The timing attack might be mitigated by
12698 other factors (see bug 6537 for some discussion), but it's best
12699 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12702 - Try to make the warning when giving an obsolete SOCKSListenAddress
12703 a little more useful.
12704 - Terminate active server managed proxies if Tor stops being a
12705 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
12706 - Provide a better error message about possible OSX Asciidoc failure
12707 reasons. Fixes bug 6436.
12708 - Warn when Tor is configured to use accounting in a way that can
12709 link a hidden service to some other hidden service or public
12710 address. Resolves ticket 6490.
12713 - Check return value of fputs() when writing authority certificate
12714 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
12715 - Ignore ServerTransportPlugin lines when Tor is not configured as
12716 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
12717 - When disabling guards for having too high a proportion of failed
12718 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
12722 - Update our default RPM spec files to work with mock and rpmbuild
12723 on RHEL/Fedora. They have an updated set of dependencies and
12724 conflicts, a fix for an ancient typo when creating the "_tor"
12725 user, and better instructions. Thanks to Ondrej Mikle for the
12726 patch series. Fixes bug 6043.
12729 - Make it possible to set the TestingTorNetwork configuration
12730 option using AlternateDirAuthority and AlternateBridgeAuthority
12731 as an alternative to setting DirServer. Addresses ticket 6377.
12734 - Clarify the documentation for the Alternate*Authority options.
12736 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
12738 o Code simplification and refactoring:
12739 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
12740 10 lines. Also, don't nest them. Doing so in the past has
12741 led to hard-to-debug code. The new style is to use the
12742 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
12745 Changes in version 0.2.3.19-rc - 2012-07-06
12746 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
12747 series. It fixes the compile on Windows, reverts to a GeoIP database
12748 that isn't as broken, and fixes a flow control bug that has been around
12749 since the beginning of Tor.
12752 - Fix a bug handling SENDME cells on nonexistent streams that could
12753 result in bizarre window values. Report and patch contributed
12754 pseudonymously. Fixes part of bug 6271. This bug was introduced
12755 before the first Tor release, in svn commit r152.
12756 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
12757 June 2012 database, Maxmind marked many Tor relays as country "A1",
12758 which will cause risky behavior for clients that set EntryNodes
12759 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
12760 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
12761 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
12764 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
12765 bugfix on 0.2.1.10-alpha.
12768 Changes in version 0.2.3.18-rc - 2012-06-28
12769 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
12770 series. It fixes a few smaller bugs, but generally appears stable.
12771 Please test it and let us know whether it is!
12774 - Allow wildcarded mapaddress targets to be specified on the
12775 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
12776 - Make our linker option detection code more robust against linkers
12777 such as on FreeBSD 8, where a bad combination of options completes
12778 successfully but makes an unrunnable binary. Fixes bug 6173;
12779 bugfix on 0.2.3.17-beta.
12781 o Minor bugfixes (on 0.2.2.x and earlier):
12782 - Avoid a false positive in the util/threads unit test by increasing
12783 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
12784 - Replace "Sending publish request" log messages with "Launching
12785 upload", so that they no longer confusingly imply that we're
12786 sending something to a directory we might not even be connected
12787 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
12788 - Make sure to set *socket_error in all error cases in
12789 connection_connect(), so it can't produce a warning about
12790 errno being zero from errno_to_orconn_end_reason(). Bugfix on
12791 0.2.1.1-alpha; resolves ticket 6028.
12792 - Downgrade "Got a certificate, but we already have it" log messages
12793 from warning to info, except when we're a dirauth. Fixes bug 5238;
12794 bugfix on 0.2.1.7-alpha.
12795 - When checking for requested signatures on the latest consensus
12796 before serving it to a client, make sure to check the right
12797 consensus flavor. Bugfix on 0.2.2.6-alpha.
12798 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
12799 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
12801 o Minor bugfixes (on 0.2.3.x):
12802 - Make format_helper_exit_status() avoid unnecessary space padding
12803 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
12805 - Downgrade a message about cleaning the microdescriptor cache to
12806 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
12807 - Log a BUG message at severity INFO if we have a networkstatus with
12808 a missing entry for some microdescriptor. Continues on a patch
12810 - Improve the log message when a managed proxy fails to launch. Fixes
12811 bug 5099; bugfix on 0.2.3.6-alpha.
12812 - Don't do DNS lookups when parsing corrupted managed proxy protocol
12813 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
12814 - When formatting wildcarded address mappings for the controller,
12815 be sure to include "*." as appropriate. Partially fixes bug 6244;
12816 bugfix on 0.2.3.9-alpha.
12817 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
12818 Bugfix on 0.2.3.13-alpha.
12819 - Stop logging messages about running with circuit timeout learning
12820 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
12821 - Disable a spurious warning about reading on a marked and flushing
12822 connection. We shouldn't be doing that, but apparently we
12823 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
12824 - Fix a bug that stopped AllowDotExit from working on addresses
12825 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
12828 o Code simplification, refactoring, unit tests:
12829 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
12830 Libevent's notion of cached time when possible.
12831 - Remove duplicate code for invoking getrlimit() from control.c.
12832 - Add a unit test for the environment_variable_names_equal function.
12835 - Document the --defaults-torrc option, and the new (in 0.2.3)
12836 semantics for overriding, extending, and clearing lists of
12837 options. Closes bug 4748.
12840 Changes in version 0.2.3.17-beta - 2012-06-15
12841 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
12842 gets our TLS handshake back on track for being able to blend in with
12843 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
12844 with Vidalia, and otherwise continues to get us closer to a release
12848 - Enable gcc and ld hardening by default. Resolves ticket 5210.
12849 - Update TLS cipher list to match Firefox 8 and later. Resolves
12851 - Implement the client side of proposal 198: remove support for
12852 clients falsely claiming to support standard ciphersuites that
12853 they can actually provide. As of modern OpenSSL versions, it's not
12854 necessary to fake any standard ciphersuite, and doing so prevents
12855 us from using better ciphersuites in the future, since servers
12856 can't know whether an advertised ciphersuite is really supported or
12857 not. Some hosts -- notably, ones with very old versions of OpenSSL
12858 or where OpenSSL has been built with ECC disabled -- will stand
12859 out because of this change; TBB users should not be affected.
12862 - Change the default value for DynamicDHGroups (introduced in
12863 0.2.3.9-alpha) to 0. This feature can make Tor relays less
12864 identifiable by their use of the mod_ssl DH group, but at
12865 the cost of some usability (#4721) and bridge tracing (#6087)
12866 regressions. Resolves ticket 5598.
12867 - Send a CRLF at the end of each STATUS_* control protocol event. This
12868 bug tickled a bug in Vidalia which would make it freeze. Fixes
12869 bug 6094; bugfix on 0.2.3.16-alpha.
12872 - Disable writing on marked-for-close connections when they are
12873 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
12874 bug 5263; bugfix on 0.0.2pre13, where we first added a special
12875 case for flushing marked connections.
12876 - Detect SSL handshake even when the initial attempt to write the
12877 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
12878 - Change the AllowDotExit rules so they should actually work.
12879 We now enforce AllowDotExit only immediately after receiving an
12880 address via SOCKS or DNSPort: other sources are free to provide
12881 .exit addresses after the resolution occurs. Fixes bug 3940;
12882 bugfix on 0.2.2.1-alpha.
12883 - Fix a (harmless) integer overflow in cell statistics reported by
12884 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
12885 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
12886 right places and never depends on the consensus parameters or
12887 computes adaptive timeouts when it is disabled. Fixes bug 5049;
12888 bugfix on 0.2.2.14-alpha.
12889 - When building Tor on Windows with -DUNICODE (not default), ensure
12890 that error messages, filenames, and DNS server names are always
12891 NUL-terminated when we convert them to a single-byte encoding.
12892 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
12893 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
12894 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
12895 - Fix an edge case where TestingTorNetwork is set but the authorities
12896 and relays all have an uptime of zero, where the private Tor network
12897 could briefly lack support for hidden services. Fixes bug 3886;
12898 bugfix on 0.2.2.18-alpha.
12899 - Correct the manpage's descriptions for the default values of
12900 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
12902 - Fix the documentation for the --hush and --quiet command line
12903 options, which changed their behavior back in 0.2.3.3-alpha.
12904 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
12908 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
12909 more information to it, so that we can track it down in case it
12910 returns again. Mitigates bug 5235.
12911 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
12912 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
12913 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
12914 - Warn the user when HTTPProxy, but no other proxy type, is
12915 configured. This can cause surprising behavior: it doesn't send
12916 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
12917 directory traffic only. Resolves ticket 4663.
12918 - Issue a notice if a guard completes less than 40% of your circuits.
12919 Threshold is configurable by torrc option PathBiasNoticeRate and
12920 consensus parameter pb_noticepct. There is additional, off-by-
12921 default code to disable guards which fail too many circuits.
12922 Addresses ticket 5458.
12923 - Update to the June 6 2012 Maxmind GeoLite Country database.
12925 o Code simplifications and refactoring:
12926 - Remove validate_pluggable_transports_config(): its warning
12927 message is now handled by connection_or_connect().
12930 Changes in version 0.2.2.37 - 2012-06-06
12931 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
12932 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
12936 - Work around a bug in OpenSSL that broke renegotiation with TLS
12937 1.1 and TLS 1.2. Without this workaround, all attempts to speak
12938 the v2 Tor connection protocol when both sides were using OpenSSL
12939 1.0.1 would fail. Resolves ticket 6033.
12940 - When waiting for a client to renegotiate, don't allow it to add
12941 any bytes to the input buffer. This fixes a potential DoS issue.
12942 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
12943 - Fix an edge case where if we fetch or publish a hidden service
12944 descriptor, we might build a 4-hop circuit and then use that circuit
12945 for exiting afterwards -- even if the new last hop doesn't obey our
12946 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
12949 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
12950 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
12953 - Tell GCC and Clang to check for any errors in format strings passed
12954 to the tor_v*(print|scan)f functions.
12957 Changes in version 0.2.3.16-alpha - 2012-06-05
12958 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
12959 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
12960 currently). It also fixes a variety of smaller bugs and other cleanups
12961 that get us closer to a release candidate.
12963 o Major bugfixes (general):
12964 - Work around a bug in OpenSSL that broke renegotiation with TLS
12965 1.1 and TLS 1.2. Without this workaround, all attempts to speak
12966 the v2 Tor connection protocol when both sides were using OpenSSL
12967 1.0.1 would fail. Resolves ticket 6033.
12968 - When waiting for a client to renegotiate, don't allow it to add
12969 any bytes to the input buffer. This fixes a potential DoS issue.
12970 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
12971 - Pass correct OR address to managed proxies (like obfsproxy),
12972 even when ORListenAddress is used. Fixes bug 4865; bugfix on
12974 - The advertised platform of a router now includes only its operating
12975 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
12976 service pack level (for Windows) or its CPU architecture (for Unix).
12977 We also no longer include the "git-XYZ" tag in the version. Resolves
12980 o Major bugfixes (clients):
12981 - If we are unable to find any exit that supports our predicted ports,
12982 stop calling them predicted, so that we don't loop and build
12983 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
12984 which introduced predicted ports.
12985 - Fix an edge case where if we fetch or publish a hidden service
12986 descriptor, we might build a 4-hop circuit and then use that circuit
12987 for exiting afterwards -- even if the new last hop doesn't obey our
12988 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
12989 - Check at each new consensus whether our entry guards were picked
12990 long enough ago that we should rotate them. Previously, we only
12991 did this check at startup, which could lead to us holding a guard
12992 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
12993 - When fetching a bridge descriptor from a bridge authority,
12994 always do so anonymously, whether we have been able to open
12995 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
12996 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
12997 but we'll need to wait for bug 6010 before it's actually usable.
12999 o Major bugfixes (directory authorities):
13000 - When computing weight parameters, behave more robustly in the
13001 presence of a bad bwweightscale value. Previously, the authorities
13002 would crash if they agreed on a sufficiently broken weight_scale
13003 value: now, they use a reasonable default and carry on. Partial
13004 fix for 5786; bugfix on 0.2.2.17-alpha.
13005 - Check more thoroughly to prevent a rogue authority from
13006 double-voting on any consensus directory parameter. Previously,
13007 authorities would crash in this case if the total number of
13008 votes for any parameter exceeded the number of active voters,
13009 but would let it pass otherwise. Partial fix for bug 5786; bugfix
13013 - Rate-limit log messages when asked to connect anonymously to
13014 a private address. When these hit, they tended to hit fast and
13015 often. Also, don't bother trying to connect to addresses that we
13016 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
13017 reply makes us think we have been lied to, even when the address the
13018 client tried to connect to was "localhost." Resolves ticket 2822.
13019 - Allow packagers to insert an extra string in server descriptor
13020 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
13021 Resolves the rest of ticket 2988.
13022 - Raise the threshold of server descriptors needed (75%) and exit
13023 server descriptors needed (50%) before we will declare ourselves
13024 bootstrapped. This will make clients start building circuits a
13025 little later, but makes the initially constructed circuits less
13026 skewed and less in conflict with further directory fetches. Fixes
13028 - Close any connection that sends unrecognized junk before the
13029 handshake. Solves an issue noted in bug 4369.
13030 - Improve log messages about managed transports. Resolves ticket 5070.
13031 - Tag a bridge's descriptor as "never to be sent unencrypted".
13032 This shouldn't matter, since bridges don't open non-anonymous
13033 connections to the bridge authority and don't allow unencrypted
13034 directory connections from clients, but we might as well make
13035 sure. Closes bug 5139.
13036 - Expose our view of whether we have gone dormant to the controller,
13037 via a new "GETINFO dormant" value. Torbutton and other controllers
13038 can use this to avoid doing periodic requests through Tor while
13039 it's dormant (bug 4718). Fixes bug 5954.
13040 - Tell GCC and Clang to check for any errors in format strings passed
13041 to the tor_v*(print|scan)f functions.
13042 - Update to the May 1 2012 Maxmind GeoLite Country database.
13044 o Minor bugfixes (already included in 0.2.2.36):
13045 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
13046 Fixes bug 5346; bugfix on 0.0.8pre3.
13047 - Correct parsing of certain date types in parse_http_time().
13048 Without this patch, If-Modified-Since would behave
13049 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
13050 Esteban Manchado Velázques.
13051 - Make our number-parsing functions always treat too-large values
13052 as an error, even when those values exceed the width of the
13053 underlying type. Previously, if the caller provided these
13054 functions with minima or maxima set to the extreme values of the
13055 underlying integer type, these functions would return those
13056 values on overflow rather than treating overflow as an error.
13057 Fixes part of bug 5786; bugfix on 0.0.9.
13058 - If we hit the error case where routerlist_insert() replaces an
13059 existing (old) server descriptor, make sure to remove that
13060 server descriptor from the old_routers list. Fix related to bug
13061 1776. Bugfix on 0.2.2.18-alpha.
13062 - Clarify the behavior of MaxCircuitDirtiness with hidden service
13063 circuits. Fixes issue 5259.
13065 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
13066 - Prevent a null-pointer dereference when receiving a data cell
13067 for a nonexistent stream when the circuit in question has an
13068 empty deliver window. We don't believe this is triggerable,
13069 since we don't currently allow deliver windows to become empty,
13070 but the logic is tricky enough that it's better to make the code
13071 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
13072 - Fix a memory leak when trying to launch a DNS request when the
13073 network is disabled or the nameservers are unconfigurable. Fixes
13074 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
13075 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
13076 - Don't hold a Windows file handle open for every file mapping;
13077 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
13079 - Avoid O(n^2) performance characteristics when parsing a large
13080 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
13081 - Format more doubles with %f, not %lf. Patch from grarpamp to make
13082 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
13084 - Make our replacement implementation of strtok_r() compatible with
13085 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
13086 bugfix on 0.2.2.1-alpha.
13087 - Fix a NULL-pointer dereference on a badly formed
13088 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
13089 bugfix on 0.2.2.9-alpha.
13090 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
13091 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
13092 - Defensively refactor rend_mid_rendezvous() so that protocol
13093 violations and length checks happen in the beginning. Fixes
13095 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
13096 that IPv6 stuff will compile on MSVC, and compilation issues
13097 will be easier to track down. Fixes bug 5861.
13099 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
13100 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
13101 resource exhaustion, so that clients can adjust their load to
13102 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
13103 started using END_STREAM_REASON_RESOURCELIMIT.
13104 - Don't check for whether the address we're using for outbound
13105 connections has changed until after the outbound connection has
13106 completed. On Windows, getsockname() doesn't succeed until the
13107 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
13108 - If the configuration tries to set MyFamily on a bridge, refuse to
13109 do so, and warn about the security implications. Fixes bug 4657;
13110 bugfix on 0.2.0.3-alpha.
13111 - If the client fails to set a reasonable set of ciphersuites
13112 during its v2 handshake renegotiation, allow the renegotiation to
13113 continue nevertheless (i.e. send all the required certificates).
13114 Fixes bug 4591; bugfix on 0.2.0.20-rc.
13115 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
13116 option is set to 0 (which Vidalia version 0.2.16 now does when
13117 a SAVECONF attempt fails), perform other actions that SIGHUP
13118 usually causes (like reopening the logs). Fixes bug 5095; bugfix
13120 - If we fail to write a microdescriptor to the disk cache, do not
13121 continue replacing the old microdescriptor file. Fixes bug 2954;
13122 bugfix on 0.2.2.6-alpha.
13123 - Exit nodes don't need to fetch certificates for authorities that
13124 they don't recognize; only directory authorities, bridges,
13125 and caches need to do that. Fixes part of bug 2297; bugfix on
13127 - Correctly handle checking the permissions on the parent
13128 directory of a control socket in the root directory. Bug found
13129 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
13131 - When told to add a bridge with the same digest as a preexisting
13132 bridge but a different addr:port, change the addr:port as
13133 requested. Previously we would not notice the change. Fixes half
13134 of bug 5603; fix on 0.2.2.26-beta.
13135 - End AUTHCHALLENGE error messages (in the control protocol) with
13136 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
13138 o Minor bugfixes (on 0.2.3.x):
13139 - Turn an assertion (that the number of handshakes received as a
13140 server is not < 1) into a warning. Fixes bug 4873; bugfix on
13142 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
13143 we had reversed them when the answer was cached.) Fixes bug
13144 5723; bugfix on 0.2.3.1-alpha.
13145 - Work correctly on Linux systems with accept4 support advertised in
13146 their headers, but without accept4 support in the kernel. Fix
13147 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
13148 - When told to add a bridge with the same addr:port as a preexisting
13149 bridge but a different transport, change the transport as
13150 requested. Previously we would not notice the change. Fixes half
13151 of bug 5603; fix on 0.2.3.2-alpha.
13152 - Avoid a "double-reply" warning when replying to a SOCKS request
13153 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
13154 bugfix on 0.2.3.4-alpha.
13155 - Fix a bug where a bridge authority crashes if it has seen no
13156 directory requests when it's time to write statistics to disk.
13157 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
13159 - Don't try to open non-control listeners when DisableNetwork is set.
13160 Previously, we'd open all listeners, then immediately close them.
13161 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
13162 - Don't abort the managed proxy protocol if the managed proxy
13163 sends us an unrecognized line; ignore it instead. Fixes bug
13164 5910; bugfix on 0.2.3.9-alpha.
13165 - Fix a compile warning in crypto.c when compiling with clang 3.1.
13166 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
13167 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
13168 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
13169 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
13170 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
13171 - Resolve numerous small warnings and build issues with MSVC. Resolves
13174 o Documentation fixes:
13175 - Improve the manual's documentation for the NT Service command-line
13176 options. Addresses ticket 3964.
13177 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
13178 - Document the changes to the ORPort and DirPort options, and the
13179 fact that {OR/Dir}ListenAddress is now unnecessary (and
13180 therefore deprecated). Resolves ticket 5597.
13183 - Remove the torrc.bridge file: we don't use it for anything, and
13184 it had become badly desynchronized from torrc.sample. Resolves
13188 Changes in version 0.2.2.36 - 2012-05-24
13189 Tor 0.2.2.36 updates the addresses for two of the eight directory
13190 authorities, fixes some potential anonymity and security issues,
13191 and fixes several crash bugs.
13193 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
13194 known flaws, and nobody should be using them. You should upgrade. If
13195 you're using a Linux or BSD and its packages are obsolete, stop using
13196 those packages and upgrade anyway.
13198 o Directory authority changes:
13199 - Change IP address for maatuska (v3 directory authority).
13200 - Change IP address for ides (v3 directory authority), and rename
13204 - When building or running with any version of OpenSSL earlier
13205 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
13206 versions have a bug (CVE-2011-4576) in which their block cipher
13207 padding includes uninitialized data, potentially leaking sensitive
13208 information to any peer with whom they make a SSLv3 connection. Tor
13209 does not use SSL v3 by default, but a hostile client or server
13210 could force an SSLv3 connection in order to gain information that
13211 they shouldn't have been able to get. The best solution here is to
13212 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
13213 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
13214 to make sure that the bug can't happen.
13215 - Never use a bridge or a controller-supplied node as an exit, even
13216 if its exit policy allows it. Found by wanoskarnet. Fixes bug
13217 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
13218 and 0.2.0.3-alpha (for bridge-purpose descriptors).
13219 - Only build circuits if we have a sufficient threshold of the total
13220 descriptors that are marked in the consensus with the "Exit"
13221 flag. This mitigates an attack proposed by wanoskarnet, in which
13222 all of a client's bridges collude to restrict the exit nodes that
13223 the client knows about. Fixes bug 5343.
13224 - Provide controllers with a safer way to implement the cookie
13225 authentication mechanism. With the old method, if another locally
13226 running program could convince a controller that it was the Tor
13227 process, then that program could trick the controller into telling
13228 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
13229 authentication method uses a challenge-response approach to prevent
13230 this attack. Fixes bug 5185; implements proposal 193.
13233 - Avoid logging uninitialized data when unable to decode a hidden
13234 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
13235 - Avoid a client-side assertion failure when receiving an INTRODUCE2
13236 cell on a general purpose circuit. Fixes bug 5644; bugfix on
13238 - Fix builds when the path to sed, openssl, or sha1sum contains
13239 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
13241 - Correct our replacements for the timeradd() and timersub() functions
13242 on platforms that lack them (for example, Windows). The timersub()
13243 function is used when expiring circuits, while timeradd() is
13244 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
13245 bugfix on 0.2.2.24-alpha.
13246 - Fix the SOCKET_OK test that we use to tell when socket
13247 creation fails so that it works on Win64. Fixes part of bug 4533;
13248 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
13251 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
13252 Fixes bug 5346; bugfix on 0.0.8pre3.
13253 - Make our number-parsing functions always treat too-large values
13254 as an error, even when those values exceed the width of the
13255 underlying type. Previously, if the caller provided these
13256 functions with minima or maxima set to the extreme values of the
13257 underlying integer type, these functions would return those
13258 values on overflow rather than treating overflow as an error.
13259 Fixes part of bug 5786; bugfix on 0.0.9.
13260 - Older Linux kernels erroneously respond to strange nmap behavior
13261 by having accept() return successfully with a zero-length
13262 socket. When this happens, just close the connection. Previously,
13263 we would try harder to learn the remote address: but there was
13264 no such remote address to learn, and our method for trying to
13265 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
13266 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
13267 - Correct parsing of certain date types in parse_http_time().
13268 Without this patch, If-Modified-Since would behave
13269 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
13270 Esteban Manchado Velázques.
13271 - Change the BridgePassword feature (part of the "bridge community"
13272 design, which is not yet implemented) to use a time-independent
13273 comparison. The old behavior might have allowed an adversary
13274 to use timing to guess the BridgePassword value. Fixes bug 5543;
13275 bugfix on 0.2.0.14-alpha.
13276 - Detect and reject certain misformed escape sequences in
13277 configuration values. Previously, these values would cause us
13278 to crash if received in a torrc file or over an authenticated
13279 control port. Bug found by Esteban Manchado Velázquez, and
13280 independently by Robert Connolly from Matta Consulting who further
13281 noted that it allows a post-authentication heap overflow. Patch
13282 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
13283 bugfix on 0.2.0.16-alpha.
13284 - Fix a compile warning when using the --enable-openbsd-malloc
13285 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
13286 - During configure, detect when we're building with clang version
13287 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
13288 CFLAGS. clang doesn't support them yet.
13289 - When sending an HTTP/1.1 proxy request, include a Host header.
13290 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
13291 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
13292 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
13293 - If we hit the error case where routerlist_insert() replaces an
13294 existing (old) server descriptor, make sure to remove that
13295 server descriptor from the old_routers list. Fix related to bug
13296 1776. Bugfix on 0.2.2.18-alpha.
13298 o Minor bugfixes (documentation and log messages):
13299 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
13300 Fixes bug 4856; bugfix on Tor 0.0.6.
13301 - Update "ClientOnly" man page entry to explain that there isn't
13302 really any point to messing with it. Resolves ticket 5005.
13303 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
13304 directory authority option (introduced in Tor 0.2.2.34).
13305 - Downgrade the "We're missing a certificate" message from notice
13306 to info: people kept mistaking it for a real problem, whereas it
13307 is seldom the problem even when we are failing to bootstrap. Fixes
13308 bug 5067; bugfix on 0.2.0.10-alpha.
13309 - Correctly spell "connect" in a log message on failure to create a
13310 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
13311 - Clarify the behavior of MaxCircuitDirtiness with hidden service
13312 circuits. Fixes issue 5259.
13315 - Directory authorities now reject versions of Tor older than
13316 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
13317 inclusive. These versions accounted for only a small fraction of
13318 the Tor network, and have numerous known security issues. Resolves
13320 - Update to the May 1 2012 Maxmind GeoLite Country database.
13323 - When sending or relaying a RELAY_EARLY cell, we used to convert
13324 it to a RELAY cell if the connection was using the v1 link
13325 protocol. This was a workaround for older versions of Tor, which
13326 didn't handle RELAY_EARLY cells properly. Now that all supported
13327 versions can handle RELAY_EARLY cells, and now that we're enforcing
13328 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
13329 remove this workaround. Addresses bug 4786.
13332 Changes in version 0.2.3.15-alpha - 2012-04-30
13333 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
13334 the development branch build on Windows again.
13336 o Minor bugfixes (on 0.2.2.x and earlier):
13337 - Make sure that there are no unhandled pending TLS errors before
13338 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
13339 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
13340 Bugfix on 0.1.0.5-rc; fixes bug 4528.
13341 - Fix an assert that directory authorities could trigger on sighup
13342 during some configuration state transitions. We now don't treat
13343 it as a fatal error when the new descriptor we just generated in
13344 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
13345 - After we pick a directory mirror, we would refuse to use it if
13346 it's in our ExcludeExitNodes list, resulting in mysterious failures
13347 to bootstrap for people who just wanted to avoid exiting from
13348 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
13349 - When building with --enable-static-tor on OpenBSD, do not
13350 erroneously attempt to link -lrt. Fixes bug 5103.
13352 o Minor bugfixes (on 0.2.3.x):
13353 - When Tor is built with kernel headers from a recent (last few
13354 years) Linux kernel, do not fail to run on older (pre-2.6.28
13355 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
13356 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
13357 and 0.2.3.12-alpha.
13358 - Fix compilation with miniupnpc version 1.6; patch from
13359 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
13360 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
13361 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
13362 - Fix compilation on platforms without unistd.h, or where environ
13363 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
13366 - Directory authorities are now a little more lenient at accepting
13367 older router descriptors, or newer router descriptors that don't
13368 make big changes. This should help ameliorate past and future
13369 issues where routers think they have uploaded valid descriptors,
13370 but the authorities don't think so. Fix for ticket 2479.
13371 - Make the code that clients use to detect an address change be
13372 IPv6-aware, so that it won't fill clients' logs with error
13373 messages when trying to get the IPv4 address of an IPv6
13374 connection. Implements ticket 5537.
13376 o Removed features:
13377 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
13378 authorities needed to use it for a while to keep the network working
13379 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
13380 that was six months ago. As of now, it should no longer be needed
13384 Changes in version 0.2.3.14-alpha - 2012-04-23
13385 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
13386 candidate. It also dramatically speeds up AES: fast relays should
13387 consider switching to the newer OpenSSL library.
13389 o Directory authority changes:
13390 - Change IP address for ides (v3 directory authority), and rename
13394 - Avoid logging uninitialized data when unable to decode a hidden
13395 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
13396 - Avoid a client-side assertion failure when receiving an INTRODUCE2
13397 cell on a general purpose circuit. Fixes bug 5644; bugfix on
13399 - If authorities are unable to get a v2 consensus document from other
13400 directory authorities, they no longer fall back to fetching
13401 them from regular directory caches. Fixes bug 5635; bugfix on
13402 0.2.2.26-beta, where routers stopped downloading v2 consensus
13403 documents entirely.
13404 - When we start a Tor client with a normal consensus already cached,
13405 be willing to download a microdescriptor consensus. Fixes bug 4011;
13406 fix on 0.2.3.1-alpha.
13408 o Major features (performance):
13409 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
13410 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
13411 vectorized AES implementations as appropriate. These can be much,
13412 much faster than other AES implementations.
13414 o Minor bugfixes (0.2.2.x and earlier):
13415 - Don't launch more than 10 service-side introduction-point circuits
13416 for a hidden service in five minutes. Previously, we would consider
13417 launching more introduction-point circuits if at least one second
13418 had passed without any introduction-point circuits failing. Fixes
13419 bug 4607; bugfix on 0.0.7pre1.
13420 - Change the BridgePassword feature (part of the "bridge community"
13421 design, which is not yet implemented) to use a time-independent
13422 comparison. The old behavior might have allowed an adversary
13423 to use timing to guess the BridgePassword value. Fixes bug 5543;
13424 bugfix on 0.2.0.14-alpha.
13425 - Enforce correct return behavior of tor_vsscanf() when the '%%'
13426 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
13427 - When sending an HTTP/1.1 proxy request, include a Host header.
13428 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
13429 - Don't log that we have "decided to publish new relay descriptor"
13430 unless we are actually publishing a descriptor. Fixes bug 3942;
13431 bugfix on 0.2.2.28-beta.
13433 o Minor bugfixes (0.2.3.x):
13434 - Fix a bug where a bridge authority crashes (on a failed assert)
13435 if it has seen no directory requests when it's time to write
13436 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
13437 - Fix bug stomping on ORPort option NoListen and ignoring option
13438 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
13439 - In the testsuite, provide a large enough buffer in the tor_sscanf
13440 unit test. Otherwise we'd overrun that buffer and crash during
13441 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
13443 - Make sure we create the keys directory if it doesn't exist and we're
13444 about to store the dynamic Diffie-Hellman parameters. Fixes bug
13445 5572; bugfix on 0.2.3.13-alpha.
13446 - Fix a small memory leak when trying to decode incorrect base16
13447 authenticator during SAFECOOKIE authentication. Found by
13448 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
13451 - Add more information to a log statement that might help track down
13452 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
13453 non-IP address" messages (or any Bug messages, for that matter!),
13454 please let us know about it.
13455 - Relays now understand an IPv6 address when they get one from a
13456 directory server. Resolves ticket 4875.
13457 - Resolve IPv6 addresses in bridge and entry statistics to country
13458 code "??" which means we at least count them. Resolves ticket 5053;
13459 improves on 0.2.3.9-alpha.
13460 - Update to the April 3 2012 Maxmind GeoLite Country database.
13461 - Begin a doc/state-contents.txt file to explain the contents of
13462 the Tor state file. Fixes bug 2987.
13464 o Default torrc changes:
13465 - Stop listing "socksport 9050" in torrc.sample. We open a socks
13466 port on 9050 by default anyway, so this should not change anything
13468 - Stop mentioning the deprecated *ListenAddress options in
13469 torrc.sample. Fixes bug 5438.
13470 - Document unit of bandwidth related options in sample torrc.
13473 o Removed features:
13474 - The "torify" script no longer supports the "tsocks" socksifier
13475 tool, since tsocks doesn't support DNS and UDP right for Tor.
13476 Everyone should be using torsocks instead. Fixes bugs 3530 and
13477 5180. Based on a patch by "ugh".
13479 o Code refactoring:
13480 - Change the symmetric cipher interface so that creating and
13481 initializing a stream cipher are no longer separate functions.
13482 - Remove all internal support for unpadded RSA. We never used it, and
13483 it would be a bad idea to start.
13486 Changes in version 0.2.3.13-alpha - 2012-03-26
13487 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
13488 in managed pluggable transports, as well as providing other cleanups
13489 that get us closer to a release candidate.
13491 o Directory authority changes:
13492 - Change IP address for maatuska (v3 directory authority).
13495 - Provide controllers with a safer way to implement the cookie
13496 authentication mechanism. With the old method, if another locally
13497 running program could convince a controller that it was the Tor
13498 process, then that program could trick the controller into telling
13499 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
13500 authentication method uses a challenge-response approach to prevent
13501 this attack. Fixes bug 5185, implements proposal 193.
13502 - Never use a bridge or a controller-supplied node as an exit, even
13503 if its exit policy allows it. Found by wanoskarnet. Fixes bug
13504 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
13505 and 0.2.0.3-alpha (for bridge-purpose descriptors).
13506 - Only build circuits if we have a sufficient threshold of the total
13507 descriptors that are marked in the consensus with the "Exit"
13508 flag. This mitigates an attack proposed by wanoskarnet, in which
13509 all of a client's bridges collude to restrict the exit nodes that
13510 the client knows about. Fixes bug 5343.
13512 o Major bugfixes (on Tor 0.2.3.x):
13513 - Avoid an assert when managed proxies like obfsproxy are configured,
13514 and we receive HUP signals or setconf attempts too rapidly. This
13515 situation happens most commonly when Vidalia tries to attach to
13516 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
13517 bugfix on 0.2.3.6-alpha.
13518 - Fix a relay-side pluggable transports bug where managed proxies were
13519 unreachable from the Internet, because Tor asked them to bind on
13520 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
13521 - Stop discarding command-line arguments when TestingTorNetwork
13522 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
13523 0.2.3.9-alpha, where task 4552 added support for two layers of
13525 - Resume allowing the unit tests to run in gdb. This was accidentally
13526 made impossible when the DisableDebuggerAttachment option was
13527 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
13528 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
13529 0.2.3.11-alpha. Reported by Anthony G. Basile.
13531 o Minor bugfixes (on 0.2.2.x and earlier):
13532 - Ensure we don't cannibalize circuits that are longer than three hops
13533 already, so we don't end up making circuits with 5 or more
13534 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
13535 0.1.0.1-rc which introduced cannibalization.
13536 - Detect and reject certain misformed escape sequences in
13537 configuration values. Previously, these values would cause us
13538 to crash if received in a torrc file or over an authenticated
13539 control port. Bug found by Esteban Manchado Velázquez, and
13540 independently by Robert Connolly from Matta Consulting who further
13541 noted that it allows a post-authentication heap overflow. Patch
13542 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
13543 bugfix on 0.2.0.16-alpha.
13544 - Fix a compile warning when using the --enable-openbsd-malloc
13545 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
13546 - Directory caches no longer refuse to clean out descriptors because
13547 of missing v2 networkstatus documents, unless they're configured
13548 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
13549 0.2.2.26-beta. Patch by Daniel Bryg.
13550 - Update to the latest version of the tinytest unit testing framework.
13551 This includes a couple of bugfixes that can be relevant for
13552 running forked unit tests on Windows, and removes all reserved
13555 o Minor bugfixes (on 0.2.3.x):
13556 - On a failed pipe() call, don't leak file descriptors. Fixes bug
13557 4296; bugfix on 0.2.3.1-alpha.
13558 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
13559 until after we have received a CERTS cell. Fixes bug 4361; bugfix
13560 on 0.2.3.6-alpha. Patch by "frosty".
13561 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
13562 option, so that the IP stack doesn't decide to use it for IPv4
13563 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
13564 - Ensure that variables set in Tor's environment cannot override
13565 environment variables that Tor passes to a managed
13566 pluggable-transport proxy. Previously, Tor would pass every
13567 variable in its environment to managed proxies along with the new
13568 ones, in such a way that on many operating systems, the inherited
13569 environment variables would override those which Tor tried to
13570 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
13571 bugfix on 0.2.3.9-alpha for Windows.
13574 - A wide variety of new unit tests by Esteban Manchado Velázquez.
13575 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
13576 - Update to the March 6 2012 Maxmind GeoLite Country database.
13579 Changes in version 0.2.3.12-alpha - 2012-02-13
13580 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
13581 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
13582 when Tor is configured to use a pluggable transport like obfsproxy.
13585 - Fix builds when the path to sed, openssl, or sha1sum contains
13586 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
13588 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
13589 connections. This change should allow busy exit relays to stop
13590 running out of available sockets as quickly. Fixes bug 4950;
13591 bugfix on 0.2.2.26-beta.
13592 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
13593 would ask the bridge for microdescriptors, which are only supported
13594 in 0.2.3.x, and then fail to bootstrap when it didn't get the
13595 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
13596 - Properly set up obfsproxy's environment when in managed mode. The
13597 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
13598 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
13599 5076 and 5082; bugfix on 0.2.3.6-alpha.
13602 - Use the dead_strip option when building Tor on OS X. This reduces
13603 binary size by almost 19% when linking openssl and libevent
13604 statically, which we do for Tor Browser Bundle.
13605 - Fix broken URLs in the sample torrc file, and tell readers about
13606 the OutboundBindAddress, ExitPolicyRejectPrivate, and
13607 PublishServerDescriptor options. Addresses bug 4652.
13608 - Update to the February 7 2012 Maxmind GeoLite Country database.
13611 - Downgrade the "We're missing a certificate" message from notice
13612 to info: people kept mistaking it for a real problem, whereas it
13613 is seldom the problem even when we are failing to bootstrap. Fixes
13614 bug 5067; bugfix on 0.2.0.10-alpha.
13615 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
13616 managed pluggable transport server proxy's environment.
13617 Previously, we would put it there, even though Tor doesn't
13618 implement an 'extended server port' yet, and even though Tor
13619 almost certainly isn't listening at that address. For now, we set
13620 it to an empty string to avoid crashing older obfsproxies. Bugfix
13622 - Log the heartbeat message every HeartbeatPeriod seconds, not every
13623 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
13624 0.2.3.1-alpha. Bug reported by Scott Bennett.
13625 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
13626 bugfix on 0.2.3.11-alpha.
13627 - Update "ClientOnly" man page entry to explain that there isn't
13628 really any point to messing with it. Resolves ticket 5005.
13629 - Use the correct CVE number for CVE-2011-4576 in our comments and
13630 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
13633 o Code simplifications and refactoring:
13634 - Use the _WIN32 macro throughout our code to detect Windows.
13635 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
13639 Changes in version 0.2.3.11-alpha - 2012-01-22
13640 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
13641 the last step of the plan to limit maximum circuit length, includes
13642 a wide variety of hidden service performance and correctness fixes,
13643 works around an OpenSSL security flaw if your distro is too stubborn
13644 to upgrade, and fixes a bunch of smaller issues.
13647 - Now that Tor 0.2.0.x is completely deprecated, enable the final
13648 part of "Proposal 110: Avoiding infinite length circuits" by
13649 refusing all circuit-extend requests that do not use a relay_early
13650 cell. This change helps Tor resist a class of denial-of-service
13651 attacks by limiting the maximum circuit length.
13652 - Adjust the number of introduction points that a hidden service
13653 will try to maintain based on how long its introduction points
13654 remain in use and how many introductions they handle. Fixes
13656 - Try to use system facilities for enumerating local interface
13657 addresses, before falling back to our old approach (which was
13658 binding a UDP socket, and calling getsockname() on it). That
13659 approach was scaring OS X users whose draconian firewall
13660 software warned about binding to UDP sockets, regardless of
13661 whether packets were sent. Now we try to use getifaddrs(),
13662 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
13663 system supports. Resolves ticket 1827.
13665 o Major security workaround:
13666 - When building or running with any version of OpenSSL earlier
13667 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
13668 versions have a bug (CVE-2011-4576) in which their block cipher
13669 padding includes uninitialized data, potentially leaking sensitive
13670 information to any peer with whom they make a SSLv3 connection. Tor
13671 does not use SSL v3 by default, but a hostile client or server
13672 could force an SSLv3 connection in order to gain information that
13673 they shouldn't have been able to get. The best solution here is to
13674 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
13675 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
13676 to make sure that the bug can't happen.
13679 - Fix the SOCKET_OK test that we use to tell when socket
13680 creation fails so that it works on Win64. Fixes part of bug 4533;
13681 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
13682 - Correct our replacements for the timeradd() and timersub() functions
13683 on platforms that lack them (for example, Windows). The timersub()
13684 function is used when expiring circuits, while timeradd() is
13685 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
13686 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
13687 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
13688 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
13689 bug at runtime, not compile time, because some distributions hack
13690 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
13691 on 0.2.3.9-alpha. Found by Pascal.
13693 o Minor features (controller):
13694 - Use absolute path names when reporting the torrc filename in the
13695 control protocol, so a controller can more easily find the torrc
13696 file. Resolves bug 1101.
13697 - Extend the control protocol to report flags that control a circuit's
13698 path selection in CIRC events and in replies to 'GETINFO
13699 circuit-status'. Implements part of ticket 2411.
13700 - Extend the control protocol to report the hidden service address
13701 and current state of a hidden-service-related circuit in CIRC
13702 events and in replies to 'GETINFO circuit-status'. Implements part
13704 - When reporting the path to the cookie file to the controller,
13705 give an absolute path. Resolves ticket 4881.
13706 - Allow controllers to request an event notification whenever a
13707 circuit is cannibalized or its purpose is changed. Implements
13708 part of ticket 3457.
13709 - Include the creation time of a circuit in CIRC and CIRC2
13710 control-port events and the list produced by the 'GETINFO
13711 circuit-status' control-port command.
13713 o Minor features (directory authorities):
13714 - Directory authorities now reject versions of Tor older than
13715 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
13716 inclusive. These versions accounted for only a small fraction of
13717 the Tor network, and have numerous known security issues. Resolves
13719 - Authority operators can now vote for all relays in a given
13720 set of countries to be BadDir/BadExit/Invalid/Rejected.
13721 - Provide two consensus parameters (FastFlagMinThreshold and
13722 FastFlagMaxThreshold) to control the range of allowable bandwidths
13723 for the Fast directory flag. These allow authorities to run
13724 experiments on appropriate requirements for being a "Fast" node.
13725 The AuthDirFastGuarantee config value still applies. Implements
13727 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
13728 directory authority option (introduced in Tor 0.2.2.34).
13730 o Minor features (other):
13731 - Don't disable the DirPort when we cannot exceed our AccountingMax
13732 limit during this interval because the effective bandwidthrate is
13733 low enough. This is useful in a situation where AccountMax is only
13734 used as an additional safeguard or to provide statistics.
13735 - Prepend an informative header to generated dynamic_dh_params files.
13736 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
13737 EntryNodes will have no effect. Resolves issue 2571.
13738 - Log more useful messages when we fail to disable debugger
13740 - Log which authority we're missing votes from when we go to fetch
13741 them from the other auths.
13742 - Log (at debug level) whenever a circuit's purpose is changed.
13743 - Add missing documentation for the MaxClientCircuitsPending,
13744 UseMicrodescriptors, UserspaceIOCPBuffers, and
13745 _UseFilteringSSLBufferevents options, all introduced during
13746 the 0.2.3.x series.
13747 - Update to the January 3 2012 Maxmind GeoLite Country database.
13749 o Minor bugfixes (hidden services):
13750 - Don't close hidden service client circuits which have almost
13751 finished connecting to their destination when they reach
13752 the normal circuit-build timeout. Previously, we would close
13753 introduction circuits which are waiting for an acknowledgement
13754 from the introduction point, and rendezvous circuits which have
13755 been specified in an INTRODUCE1 cell sent to a hidden service,
13756 after the normal CBT. Now, we mark them as 'timed out', and launch
13757 another rendezvous attempt in parallel. This behavior change can
13758 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
13759 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
13760 - Don't close hidden-service-side rendezvous circuits when they
13761 reach the normal circuit-build timeout. This behavior change can
13762 be disabled using the new
13763 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
13764 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
13765 - Make sure we never mark the wrong rendezvous circuit as having
13766 had its introduction cell acknowleged by the introduction-point
13767 relay. Previously, when we received an INTRODUCE_ACK cell on a
13768 client-side hidden-service introduction circuit, we might have
13769 marked a rendezvous circuit other than the one we specified in
13770 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
13771 a warning message and interfered with the hidden service
13772 connection-establishment process. Fixes bug 4759; bugfix on
13773 0.2.3.3-alpha, when we added the stream-isolation feature which
13774 might cause Tor to open multiple rendezvous circuits for the same
13776 - Don't trigger an assertion failure when we mark a new client-side
13777 hidden-service introduction circuit for close during the process
13778 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
13781 o Minor bugfixes (log messages):
13782 - Correctly spell "connect" in a log message on failure to create a
13783 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
13785 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
13786 Fixes bug 4856; bugfix on Tor 0.0.6.
13787 - Fix the log message describing how we work around discovering
13788 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
13789 4837; bugfix on 0.2.2.9-alpha.
13790 - When logging about a disallowed .exit name, do not also call it
13791 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
13793 o Minor bugfixes (build fixes):
13794 - During configure, detect when we're building with clang version
13795 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
13796 CFLAGS. clang doesn't support them yet.
13797 - During configure, search for library containing cos function as
13798 libm lives in libcore on some platforms (BeOS/Haiku). Linking
13799 against libm was hard-coded before. Fixes the first part of bug
13800 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
13802 - Detect attempts to build Tor on (as yet hypothetical) versions
13803 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
13804 fix for bug 4533. Bugfix on 0.2.2.28-beta.
13805 - Preprocessor directives should not be put inside the arguments
13806 of a macro. This would break compilation with GCC releases prior
13807 to version 3.3. We would never recommend such an old GCC version,
13808 but it is apparently required for binary compatibility on some
13809 platforms (namely, certain builds of Haiku). Fixes the other part
13810 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
13813 o Minor bugfixes (other):
13814 - Older Linux kernels erroneously respond to strange nmap behavior
13815 by having accept() return successfully with a zero-length
13816 socket. When this happens, just close the connection. Previously,
13817 we would try harder to learn the remote address: but there was
13818 no such remote address to learn, and our method for trying to
13819 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
13820 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
13821 - Fix null-pointer access that could occur if TLS allocation failed.
13822 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
13823 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
13824 accidentally been reverted.
13825 - Fix our implementation of crypto_random_hostname() so it can't
13826 overflow on ridiculously large inputs. (No Tor version has ever
13827 provided this kind of bad inputs, but let's be correct in depth.)
13828 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
13829 - Find more places in the code that should have been testing for
13830 invalid sockets using the SOCKET_OK macro. Required for a fix
13831 for bug 4533. Bugfix on 0.2.2.28-beta.
13832 - Fix an assertion failure when, while running with bufferevents, a
13833 connection finishes connecting after it is marked for close, but
13834 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
13835 - test_util_spawn_background_ok() hardcoded the expected value
13836 for ENOENT to 2. This isn't portable as error numbers are
13837 platform specific, and particularly the hurd has ENOENT at
13838 0x40000002. Construct expected string at runtime, using the correct
13839 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
13840 - Reject attempts to disable DisableDebuggerAttachment while Tor is
13841 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
13842 - Use an appropriate-width type for sockets in tor-fw-helper on
13843 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
13846 - When sending or relaying a RELAY_EARLY cell, we used to convert
13847 it to a RELAY cell if the connection was using the v1 link
13848 protocol. This was a workaround for older versions of Tor, which
13849 didn't handle RELAY_EARLY cells properly. Now that all supported
13850 versions can handle RELAY_EARLY cells, and now that we're enforcing
13851 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
13852 remove this workaround. Addresses bug 4786.
13854 o Code simplifications and refactoring:
13855 - Use OpenSSL's built-in SSL_state_string_long() instead of our
13856 own homebrewed ssl_state_to_string() replacement. Patch from
13857 Emile Snyder. Fixes bug 4653.
13858 - Use macros to indicate OpenSSL versions, so we don't need to worry
13859 about accidental hexadecimal bit shifts.
13860 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
13862 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
13863 - Use the smartlist_add_asprintf() alias more consistently.
13864 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
13865 invalid value, rather than just -1.
13866 - Rename a handful of old identifiers, mostly related to crypto
13867 structures and crypto functions. By convention, our "create an
13868 object" functions are called "type_new()", our "free an object"
13869 functions are called "type_free()", and our types indicate that
13870 they are types only with a final "_t". But a handful of older
13871 types and functions broke these rules, with function names like
13872 "type_create" or "subsystem_op_type", or with type names like
13876 Changes in version 0.2.3.10-alpha - 2011-12-16
13877 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
13878 Tor's buffers code. Absolutely everybody should upgrade.
13880 The bug relied on an incorrect calculation when making data continuous
13881 in one of our IO buffers, if the first chunk of the buffer was
13882 misaligned by just the wrong amount. The miscalculation would allow an
13883 attacker to overflow a piece of heap-allocated memory. To mount this
13884 attack, the attacker would need to either open a SOCKS connection to
13885 Tor's SocksPort (usually restricted to localhost), or target a Tor
13886 instance configured to make its connections through a SOCKS proxy
13887 (which Tor does not do by default).
13889 Good security practice requires that all heap-overflow bugs should be
13890 presumed to be exploitable until proven otherwise, so we are treating
13891 this as a potential code execution attack. Please upgrade immediately!
13892 This bug does not affect bufferevents-based builds of Tor. Special
13893 thanks to "Vektor" for reporting this issue to us!
13895 This release also contains a few minor bugfixes for issues discovered
13899 - Fix a heap overflow bug that could occur when trying to pull
13900 data into the first chunk of a buffer, when that chunk had
13901 already had some data drained from it. Fixes CVE-2011-2778;
13902 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
13905 - If we can't attach streams to a rendezvous circuit when we
13906 finish connecting to a hidden service, clear the rendezvous
13907 circuit's stream-isolation state and try to attach streams
13908 again. Previously, we cleared rendezvous circuits' isolation
13909 state either too early (if they were freshly built) or not at all
13910 (if they had been built earlier and were cannibalized). Bugfix on
13911 0.2.3.3-alpha; fixes bug 4655.
13912 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
13913 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
13914 - Fix an assertion failure when a relay with accounting enabled
13915 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
13918 - Update to the December 6 2011 Maxmind GeoLite Country database.
13921 Changes in version 0.2.2.35 - 2011-12-16
13922 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
13923 buffers code. Absolutely everybody should upgrade.
13925 The bug relied on an incorrect calculation when making data continuous
13926 in one of our IO buffers, if the first chunk of the buffer was
13927 misaligned by just the wrong amount. The miscalculation would allow an
13928 attacker to overflow a piece of heap-allocated memory. To mount this
13929 attack, the attacker would need to either open a SOCKS connection to
13930 Tor's SocksPort (usually restricted to localhost), or target a Tor
13931 instance configured to make its connections through a SOCKS proxy
13932 (which Tor does not do by default).
13934 Good security practice requires that all heap-overflow bugs should be
13935 presumed to be exploitable until proven otherwise, so we are treating
13936 this as a potential code execution attack. Please upgrade immediately!
13937 This bug does not affect bufferevents-based builds of Tor. Special
13938 thanks to "Vektor" for reporting this issue to us!
13940 Tor 0.2.2.35 also fixes several bugs in previous versions, including
13941 crash bugs for unusual configurations, and a long-term bug that
13942 would prevent Tor from starting on Windows machines with draconian
13945 With this release, we remind everyone that 0.2.0.x has reached its
13946 formal end-of-life. Those Tor versions have many known flaws, and
13947 nobody should be using them. You should upgrade -- ideally to the
13948 0.2.2.x series. If you're using a Linux or BSD and its packages are
13949 obsolete, stop using those packages and upgrade anyway.
13951 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
13952 longer receive support after some time in early 2012.
13955 - Fix a heap overflow bug that could occur when trying to pull
13956 data into the first chunk of a buffer, when that chunk had
13957 already had some data drained from it. Fixes CVE-2011-2778;
13958 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
13959 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
13960 that it doesn't attempt to allocate a socketpair. This could cause
13961 some problems on Windows systems with overzealous firewalls. Fix for
13962 bug 4457; workaround for Libevent versions 2.0.1-alpha through
13964 - If we mark an OR connection for close based on a cell we process,
13965 don't process any further cells on it. We already avoid further
13966 reads on marked-for-close connections, but now we also discard the
13967 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
13968 which was the first version where we might mark a connection for
13969 close based on processing a cell on it.
13970 - Correctly sanity-check that we don't underflow on a memory
13971 allocation (and then assert) for hidden service introduction
13972 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
13973 bugfix on 0.2.1.5-alpha.
13974 - Fix a memory leak when we check whether a hidden service
13975 descriptor has any usable introduction points left. Fixes bug
13976 4424. Bugfix on 0.2.2.25-alpha.
13977 - Don't crash when we're running as a relay and don't have a GeoIP
13978 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
13979 we've had in the 0.2.3.x branch already.
13980 - When running as a client, do not print a misleading (and plain
13981 wrong) log message that we're collecting "directory request"
13982 statistics: clients don't collect statistics. Also don't create a
13983 useless (because empty) stats file in the stats/ directory. Fixes
13984 bug 4353; bugfix on 0.2.2.34.
13987 - Detect failure to initialize Libevent. This fix provides better
13988 detection for future instances of bug 4457.
13989 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
13990 function. This was eating up hideously large amounts of time on some
13991 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
13992 - Resolve an integer overflow bug in smartlist_ensure_capacity().
13993 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
13995 - Don't warn about unused log_mutex in log.c when building with
13996 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
13997 0.1.0.6-rc which introduced --disable-threads.
13998 - When configuring, starting, or stopping an NT service, stop
13999 immediately after the service configuration attempt has succeeded
14000 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
14001 - When sending a NETINFO cell, include the original address
14002 received for the other side, not its canonical address. Found
14003 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
14004 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
14005 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
14006 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
14007 occurred when a client tried to fetch a descriptor for a bridge
14008 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
14009 - Backport fixes for a pair of compilation warnings on Windows.
14010 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
14011 - If we had ever tried to call tor_addr_to_str on an address of
14012 unknown type, we would have done a strdup on an uninitialized
14013 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
14014 Reported by "troll_un".
14015 - Correctly detect and handle transient lookup failures from
14016 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
14017 Reported by "troll_un".
14018 - Fix null-pointer access that could occur if TLS allocation failed.
14019 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
14020 - Use tor_socket_t type for listener argument to accept(). Fixes bug
14021 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
14024 - Add two new config options for directory authorities:
14025 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
14026 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
14027 that is always sufficient to satisfy the bandwidth requirement for
14028 the Guard flag. Now it will be easier for researchers to simulate
14029 Tor networks with different values. Resolves ticket 4484.
14030 - When Tor ignores a hidden service specified in its configuration,
14031 include the hidden service's directory in the warning message.
14032 Previously, we would only tell the user that some hidden service
14033 was ignored. Bugfix on 0.0.6; fixes bug 4426.
14034 - Update to the December 6 2011 Maxmind GeoLite Country database.
14036 o Packaging changes:
14037 - Make it easier to automate expert package builds on Windows,
14038 by removing an absolute path from makensis.exe command.
14041 Changes in version 0.2.1.32 - 2011-12-16
14042 Tor 0.2.1.32 backports important security and privacy fixes for
14043 oldstable. This release is intended only for package maintainers and
14044 others who cannot use the 0.2.2 stable series. All others should be
14045 using Tor 0.2.2.x or newer.
14047 The Tor 0.2.1.x series will reach formal end-of-life some time in
14048 early 2012; we will stop releasing patches for it then.
14050 o Major bugfixes (also included in 0.2.2.x):
14051 - Correctly sanity-check that we don't underflow on a memory
14052 allocation (and then assert) for hidden service introduction
14053 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14054 bugfix on 0.2.1.5-alpha.
14055 - Fix a heap overflow bug that could occur when trying to pull
14056 data into the first chunk of a buffer, when that chunk had
14057 already had some data drained from it. Fixes CVE-2011-2778;
14058 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
14061 - Update to the December 6 2011 Maxmind GeoLite Country database.
14064 Changes in version 0.2.3.9-alpha - 2011-12-08
14065 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
14066 a "DisableNetwork" security feature that bundles can use to avoid
14067 touching the network until bridges are configured, moves forward on
14068 the pluggable transport design, fixes a flaw in the hidden service
14069 design that unnecessarily prevented clients with wrong clocks from
14070 reaching hidden services, and fixes a wide variety of other issues.
14073 - Clients can now connect to private bridges over IPv6. Bridges
14074 still need at least one IPv4 address in order to connect to
14075 other relays. Note that we don't yet handle the case where the
14076 user has two bridge lines for the same bridge (one IPv4, one
14077 IPv6). Implements parts of proposal 186.
14078 - New "DisableNetwork" config option to prevent Tor from launching any
14079 connections or accepting any connections except on a control port.
14080 Bundles and controllers can set this option before letting Tor talk
14081 to the rest of the network, for example to prevent any connections
14082 to a non-bridge address. Packages like Orbot can also use this
14083 option to instruct Tor to save power when the network is off.
14084 - Clients and bridges can now be configured to use a separate
14085 "transport" proxy. This approach makes the censorship arms race
14086 easier by allowing bridges to use protocol obfuscation plugins. It
14087 implements the "managed proxy" part of proposal 180 (ticket 3472).
14088 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
14089 implementation. It makes AES_CTR about 7% faster than our old one
14090 (which was about 10% faster than the one OpenSSL used to provide).
14091 Resolves ticket 4526.
14092 - Add a "tor2web mode" for clients that want to connect to hidden
14093 services non-anonymously (and possibly more quickly). As a safety
14094 measure to try to keep users from turning this on without knowing
14095 what they are doing, tor2web mode must be explicitly enabled at
14096 compile time, and a copy of Tor compiled to run in tor2web mode
14097 cannot be used as a normal Tor client. Implements feature 2553.
14098 - Add experimental support for running on Windows with IOCP and no
14099 kernel-space socket buffers. This feature is controlled by a new
14100 "UserspaceIOCPBuffers" config option (off by default), which has
14101 no effect unless Tor has been built with support for bufferevents,
14102 is running on Windows, and has enabled IOCP. This may, in the long
14103 run, help solve or mitigate bug 98.
14104 - Use a more secure consensus parameter voting algorithm. Now at
14105 least three directory authorities or a majority of them must
14106 vote on a given parameter before it will be included in the
14107 consensus. Implements proposal 178.
14110 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
14111 They used to check that the timestamp was within 30 minutes
14112 of their system clock, so they could cap the size of their
14113 replay-detection cache, but that approach unnecessarily refused
14114 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
14115 the v3 intro-point protocol (the first one which sent a timestamp
14116 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
14117 - Only use the EVP interface when AES acceleration is enabled,
14118 to avoid a 5-7% performance regression. Resolves issue 4525;
14119 bugfix on 0.2.3.8-alpha.
14121 o Privacy/anonymity features (bridge detection):
14122 - Make bridge SSL certificates a bit more stealthy by using random
14123 serial numbers, in the same fashion as OpenSSL when generating
14124 self-signed certificates. Implements ticket 4584.
14125 - Introduce a new config option "DynamicDHGroups", enabled by
14126 default, which provides each bridge with a unique prime DH modulus
14127 to be used during SSL handshakes. This option attempts to help
14128 against censors who might use the Apache DH modulus as a static
14129 identifier for bridges. Addresses ticket 4548.
14131 o Minor features (new/different config options):
14132 - New configuration option "DisableDebuggerAttachment" (on by default)
14133 to prevent basic debugging attachment attempts by other processes.
14134 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
14135 - Allow MapAddress directives to specify matches against super-domains,
14136 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
14137 Implements issue 933.
14138 - Slightly change behavior of "list" options (that is, config
14139 options that can appear more than once) when they appear both in
14140 torrc and on the command line. Previously, the command-line options
14141 would be appended to the ones from torrc. Now, the command-line
14142 options override the torrc options entirely. This new behavior
14143 allows the user to override list options (like exit policies and
14144 ports to listen on) from the command line, rather than simply
14145 appending to the list.
14146 - You can get the old (appending) command-line behavior for "list"
14147 options by prefixing the option name with a "+".
14148 - You can remove all the values for a "list" option from the command
14149 line without adding any new ones by prefixing the option name
14151 - Add experimental support for a "defaults" torrc file to be parsed
14152 before the regular torrc. Torrc options override the defaults file's
14153 options in the same way that the command line overrides the torrc.
14154 The SAVECONF controller command saves only those options which
14155 differ between the current configuration and the defaults file. HUP
14156 reloads both files. (Note: This is an experimental feature; its
14157 behavior will probably be refined in future 0.2.3.x-alpha versions
14158 to better meet packagers' needs.) Implements task 4552.
14161 - Try to make the introductory warning message that Tor prints on
14162 startup more useful for actually finding help and information.
14163 Resolves ticket 2474.
14164 - Running "make version" now displays the version of Tor that
14165 we're about to build. Idea from katmagic; resolves issue 4400.
14166 - Expire old or over-used hidden service introduction points.
14167 Required by fix for bug 3460.
14168 - Move the replay-detection cache for the RSA-encrypted parts of
14169 INTRODUCE2 cells to the introduction point data structures.
14170 Previously, we would use one replay-detection cache per hidden
14171 service. Required by fix for bug 3460.
14172 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
14173 public key replay-detection cache from 60 minutes to 5 minutes. This
14174 replay-detection cache is now used only to detect multiple
14175 INTRODUCE2 cells specifying the same rendezvous point, so we can
14176 avoid launching multiple simultaneous attempts to connect to it.
14178 o Minor bugfixes (on Tor 0.2.2.x and earlier):
14179 - Resolve an integer overflow bug in smartlist_ensure_capacity().
14180 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
14182 - Fix a minor formatting issue in one of tor-gencert's error messages.
14184 - Prevent a false positive from the check-spaces script, by disabling
14185 the "whitespace between function name and (" check for functions
14187 - Fix a log message suggesting that people contact a non-existent
14188 email address. Fixes bug 3448.
14189 - Fix null-pointer access that could occur if TLS allocation failed.
14190 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
14191 - Report a real bootstrap problem to the controller on router
14192 identity mismatch. Previously we just said "foo", which probably
14193 made a lot of sense at the time. Fixes bug 4169; bugfix on
14195 - If we had ever tried to call tor_addr_to_str() on an address of
14196 unknown type, we would have done a strdup() on an uninitialized
14197 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
14198 Reported by "troll_un".
14199 - Correctly detect and handle transient lookup failures from
14200 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
14201 Reported by "troll_un".
14202 - Use tor_socket_t type for listener argument to accept(). Fixes bug
14203 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
14204 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
14205 bug 4532; found by "troll_un".
14207 o Minor bugfixes (on Tor 0.2.3.x):
14208 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
14210 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
14211 circuit for use as a hidden service client's rendezvous point.
14212 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
14213 with help from wanoskarnet.
14214 - Restore behavior of overriding SocksPort, ORPort, and similar
14215 options from the command line. Bugfix on 0.2.3.3-alpha.
14218 - Properly handle the case where the build-tree is not the same
14219 as the source tree when generating src/common/common_sha1.i,
14220 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
14221 bugfix on 0.2.0.1-alpha.
14223 o Code simplifications, cleanups, and refactorings:
14224 - Remove the pure attribute from all functions that used it
14225 previously. In many cases we assigned it incorrectly, because the
14226 functions might assert or call impure functions, and we don't have
14227 evidence that keeping the pure attribute is worthwhile. Implements
14228 changes suggested in ticket 4421.
14229 - Remove some dead code spotted by coverity. Fixes cid 432.
14230 Bugfix on 0.2.3.1-alpha, closes bug 4637.
14233 Changes in version 0.2.3.8-alpha - 2011-11-22
14234 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
14235 socketpair-related bug that has been bothering Windows users. It adds
14236 support to serve microdescriptors to controllers, so Vidalia's network
14237 map can resume listing relays (once Vidalia implements its side),
14238 and adds better support for hardware AES acceleration. Finally, it
14239 starts the process of adjusting the bandwidth cutoff for getting the
14240 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
14241 that tiny relays harm performance more than they help network capacity.
14244 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
14245 that it doesn't attempt to allocate a socketpair. This could cause
14246 some problems on Windows systems with overzealous firewalls. Fix for
14247 bug 4457; workaround for Libevent versions 2.0.1-alpha through
14249 - Correctly sanity-check that we don't underflow on a memory
14250 allocation (and then assert) for hidden service introduction
14251 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14252 bugfix on 0.2.1.5-alpha.
14253 - Remove the artificially low cutoff of 20KB to guarantee the Fast
14254 flag. In the past few years the average relay speed has picked
14255 up, and while the "top 7/8 of the network get the Fast flag" and
14256 "all relays with 20KB or more of capacity get the Fast flag" rules
14257 used to have the same result, now the top 7/8 of the network has
14258 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
14259 - Fix a rare assertion failure when checking whether a v0 hidden
14260 service descriptor has any usable introduction points left, and
14261 we don't have enough information to build a circuit to the first
14262 intro point named in the descriptor. The HS client code in
14263 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
14264 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
14265 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
14266 - Make bridge authorities not crash when they are asked for their own
14267 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
14268 - When running as a client, do not print a misleading (and plain
14269 wrong) log message that we're collecting "directory request"
14270 statistics: clients don't collect statistics. Also don't create a
14271 useless (because empty) stats file in the stats/ directory. Fixes
14272 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
14275 - Allow Tor controllers like Vidalia to obtain the microdescriptor
14276 for a relay by identity digest or nickname. Previously,
14277 microdescriptors were only available by their own digests, so a
14278 controller would have to ask for and parse the whole microdescriptor
14279 consensus in order to look up a single relay's microdesc. Fixes
14280 bug 3832; bugfix on 0.2.3.1-alpha.
14281 - Use OpenSSL's EVP interface for AES encryption, so that all AES
14282 operations can use hardware acceleration (if present). Resolves
14285 o Minor bugfixes (on 0.2.2.x and earlier):
14286 - Detect failure to initialize Libevent. This fix provides better
14287 detection for future instances of bug 4457.
14288 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
14289 function. This was eating up hideously large amounts of time on some
14290 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
14291 - Don't warn about unused log_mutex in log.c when building with
14292 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
14293 0.1.0.6-rc which introduced --disable-threads.
14294 - Allow manual 'authenticate' commands to the controller interface
14295 from netcat (nc) as well as telnet. We were rejecting them because
14296 they didn't come with the expected whitespace at the end of the
14297 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
14298 - Fix some (not actually triggerable) buffer size checks in usage of
14299 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
14301 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
14302 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
14303 - When configuring, starting, or stopping an NT service, stop
14304 immediately after the service configuration attempt has succeeded
14305 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
14306 - When sending a NETINFO cell, include the original address
14307 received for the other side, not its canonical address. Found
14308 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
14309 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
14310 can pick them up when the tests aren't disabled. Bugfix on
14311 0.2.2.4-alpha which introduced tinytest.
14312 - Fix a memory leak when we check whether a hidden service
14313 descriptor has any usable introduction points left. Fixes bug
14314 4424. Bugfix on 0.2.2.25-alpha.
14315 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
14316 occurred when a client tried to fetch a descriptor for a bridge
14317 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
14319 o Minor bugfixes (on 0.2.3.x):
14320 - Make util unit tests build correctly with MSVC. Bugfix on
14321 0.2.3.3-alpha. Patch by Gisle Vanem.
14322 - Successfully detect AUTH_CHALLENGE cells with no recognized
14323 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
14324 Found by frosty_un.
14325 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
14326 it should still send a NETINFO cell to allow the connection to
14327 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
14329 - Log less loudly when we get an invalid authentication certificate
14330 from a source other than a directory authority: it's not unusual
14331 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
14333 - Tolerate servers with more clock skew in their authentication
14334 certificates than previously. Fixes bug 4371; bugfix on
14336 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
14337 on 0.2.3.4-alpha and 0.2.3.6-alpha.
14340 - Add two new config options for directory authorities:
14341 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
14342 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
14343 that is always sufficient to satisfy the bandwidth requirement for
14344 the Guard flag. Now it will be easier for researchers to simulate
14345 Tor networks with different values. Resolves ticket 4484.
14346 - When Tor ignores a hidden service specified in its configuration,
14347 include the hidden service's directory in the warning message.
14348 Previously, we would only tell the user that some hidden service
14349 was ignored. Bugfix on 0.0.6; fixes bug 4426.
14350 - When we fail to initialize Libevent, retry with IOCP disabled so we
14351 don't need to turn on multi-threading support in Libevent, which in
14352 turn requires a working socketpair(). This is a workaround for bug
14353 4457, which affects Libevent versions from 2.0.1-alpha through
14355 - Detect when we try to build on a platform that doesn't define
14356 AF_UNSPEC to 0. We don't work there, so refuse to compile.
14357 - Update to the November 1 2011 Maxmind GeoLite Country database.
14359 o Packaging changes:
14360 - Make it easier to automate expert package builds on Windows,
14361 by removing an absolute path from makensis.exe command.
14363 o Code simplifications and refactoring:
14364 - Remove some redundant #include directives throughout the code.
14365 Patch from Andrea Gelmini.
14366 - Unconditionally use OpenSSL's AES implementation instead of our
14367 old built-in one. OpenSSL's AES has been better for a while, and
14368 relatively few servers should still be on any version of OpenSSL
14369 that doesn't have good optimized assembly AES.
14370 - Use the name "CERTS" consistently to refer to the new cell type;
14371 we were calling it CERT in some places and CERTS in others.
14374 - Numerous new unit tests for functions in util.c and address.c by
14376 - The long-disabled benchmark tests are now split into their own
14377 ./src/test/bench binary.
14378 - The benchmark tests can now use more accurate timers than
14379 gettimeofday() when such timers are available.
14382 Changes in version 0.2.3.7-alpha - 2011-10-30
14383 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
14384 the new v3 handshake. It also resolves yet another bridge address
14388 - If we mark an OR connection for close based on a cell we process,
14389 don't process any further cells on it. We already avoid further
14390 reads on marked-for-close connections, but now we also discard the
14391 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
14392 which was the first version where we might mark a connection for
14393 close based on processing a cell on it.
14394 - Fix a double-free bug that would occur when we received an invalid
14395 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
14396 bugfix on 0.2.3.6-alpha.
14397 - Bridges no longer include their address in NETINFO cells on outgoing
14398 OR connections, to allow them to blend in better with clients.
14399 Removes another avenue for enumerating bridges. Reported by
14400 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
14401 cells were introduced.
14404 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
14405 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
14408 Changes in version 0.2.3.6-alpha - 2011-10-26
14409 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
14410 anonymity vulnerability where an attacker can deanonymize Tor
14411 users. Everybody should upgrade.
14413 This release also features support for a new v3 connection handshake
14414 protocol, and fixes to make hidden service connections more robust.
14417 - Implement a new handshake protocol (v3) for authenticating Tors to
14418 each other over TLS. It should be more resistant to fingerprinting
14419 than previous protocols, and should require less TLS hacking for
14420 future Tor implementations. Implements proposal 176.
14421 - Allow variable-length padding cells to disguise the length of
14422 Tor's TLS records. Implements part of proposal 184.
14424 o Privacy/anonymity fixes (clients):
14425 - Clients and bridges no longer send TLS certificate chains on
14426 outgoing OR connections. Previously, each client or bridge would
14427 use the same cert chain for all outgoing OR connections until
14428 its IP address changes, which allowed any relay that the client
14429 or bridge contacted to determine which entry guards it is using.
14430 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14431 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14432 no longer considers that connection as suitable for satisfying a
14433 circuit EXTEND request. Now relays can protect clients from the
14434 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14435 - Directory authorities no longer assign the Guard flag to relays
14436 that haven't upgraded to the above "refuse EXTEND requests
14437 to client connections" fix. Now directory authorities can
14438 protect clients from the CVE-2011-2768 issue even if neither
14439 the clients nor the relays have upgraded yet. There's a new
14440 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
14441 to let us transition smoothly, else tomorrow there would be no
14444 o Major bugfixes (hidden services):
14445 - Improve hidden service robustness: when an attempt to connect to
14446 a hidden service ends, be willing to refetch its hidden service
14447 descriptors from each of the HSDir relays responsible for them
14448 immediately. Previously, we would not consider refetching the
14449 service's descriptors from each HSDir for 15 minutes after the last
14450 fetch, which was inconvenient if the hidden service was not running
14451 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
14452 - When one of a hidden service's introduction points appears to be
14453 unreachable, stop trying it. Previously, we would keep trying
14454 to build circuits to the introduction point until we lost the
14455 descriptor, usually because the user gave up and restarted Tor.
14456 Partly fixes bug 3825.
14457 - Don't launch a useless circuit after failing to use one of a
14458 hidden service's introduction points. Previously, we would
14459 launch a new introduction circuit, but not set the hidden service
14460 which that circuit was intended to connect to, so it would never
14461 actually be used. A different piece of code would then create a
14462 new introduction circuit correctly. Bug reported by katmagic and
14463 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
14465 o Major bugfixes (other):
14466 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14467 that they initiated. Relays could distinguish incoming bridge
14468 connections from client connections, creating another avenue for
14469 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14470 Found by "frosty_un".
14471 - Don't update the AccountingSoftLimitHitAt state file entry whenever
14472 tor gets started. This prevents a wrong average bandwidth
14473 estimate, which would cause relays to always start a new accounting
14474 interval at the earliest possible moment. Fixes bug 2003; bugfix
14475 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
14476 immensely in tracking this bug down.
14477 - Fix a crash bug when changing node restrictions while a DNS lookup
14478 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
14481 o Minor bugfixes (on 0.2.2.x and earlier):
14482 - When a hidden service turns an extra service-side introduction
14483 circuit into a general-purpose circuit, free the rend_data and
14484 intro_key fields first, so we won't leak memory if the circuit
14485 is cannibalized for use as another service-side introduction
14486 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
14487 - Rephrase the log message emitted if the TestSocks check is
14488 successful. Patch from Fabian Keil; fixes bug 4094.
14489 - Bridges now skip DNS self-tests, to act a little more stealthily.
14490 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
14491 bridges. Patch by "warms0x".
14492 - Remove a confusing dollar sign from the example fingerprint in the
14493 man page, and also make the example fingerprint a valid one. Fixes
14494 bug 4309; bugfix on 0.2.1.3-alpha.
14495 - Fix internal bug-checking logic that was supposed to catch
14496 failures in digest generation so that it will fail more robustly
14497 if we ask for a nonexistent algorithm. Found by Coverity Scan.
14498 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
14499 - Report any failure in init_keys() calls launched because our
14500 IP address has changed. Spotted by Coverity Scan. Bugfix on
14501 0.1.1.4-alpha; fixes CID 484.
14503 o Minor bugfixes (on 0.2.3.x):
14504 - Fix a bug in configure.in that kept it from building a configure
14505 script with autoconf versions earlier than 2.61. Fixes bug 2430;
14506 bugfix on 0.2.3.1-alpha.
14507 - Don't warn users that they are exposing a client port to the
14508 Internet if they have specified an RFC1918 address. Previously,
14509 we would warn if the user had specified any non-loopback
14510 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
14511 - Fix memory leaks in the failing cases of the new SocksPort and
14512 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
14513 fixes coverity CIDs 485, 486, and 487.
14516 - When a hidden service's introduction point times out, consider
14517 trying it again during the next attempt to connect to the
14518 HS. Previously, we would not try it again unless a newly fetched
14519 descriptor contained it. Required by fixes for bugs 1297 and 3825.
14520 - The next version of Windows will be called Windows 8, and it has
14521 a major version of 6, minor version of 2. Correctly identify that
14522 version instead of calling it "Very recent version". Resolves
14523 ticket 4153; reported by funkstar.
14524 - The Bridge Authority now writes statistics on how many bridge
14525 descriptors it gave out in total, and how many unique descriptors
14526 it gave out. It also lists how often the most and least commonly
14527 fetched descriptors were given out, as well as the median and
14528 25th/75th percentile. Implements tickets 4200 and 4294.
14529 - Update to the October 4 2011 Maxmind GeoLite Country database.
14531 o Code simplifications and refactoring:
14532 - Remove some old code to remember statistics about which descriptors
14533 we've served as a directory mirror. The feature wasn't used and
14534 is outdated now that microdescriptors are around.
14535 - Rename Tor functions that turn strings into addresses, so that
14536 "parse" indicates that no hostname resolution occurs, and
14537 "lookup" indicates that hostname resolution may occur. This
14538 should help prevent mistakes in the future. Fixes bug 3512.
14541 Changes in version 0.2.2.34 - 2011-10-26
14542 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
14543 can deanonymize Tor users. Everybody should upgrade.
14545 The attack relies on four components: 1) Clients reuse their TLS cert
14546 when talking to different relays, so relays can recognize a user by
14547 the identity key in her cert. 2) An attacker who knows the client's
14548 identity key can probe each guard relay to see if that identity key
14549 is connected to that guard relay right now. 3) A variety of active
14550 attacks in the literature (starting from "Low-Cost Traffic Analysis
14551 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
14552 discover the guard relays that a Tor user visiting the website is using.
14553 4) Clients typically pick three guards at random, so the set of guards
14554 for a given user could well be a unique fingerprint for her. This
14555 release fixes components #1 and #2, which is enough to block the attack;
14556 the other two remain as open research problems. Special thanks to
14557 "frosty_un" for reporting the issue to us!
14559 Clients should upgrade so they are no longer recognizable by the TLS
14560 certs they present. Relays should upgrade so they no longer allow a
14561 remote attacker to probe them to test whether unpatched clients are
14562 currently connected to them.
14564 This release also fixes several vulnerabilities that allow an attacker
14565 to enumerate bridge relays. Some bridge enumeration attacks still
14566 remain; see for example proposal 188.
14568 o Privacy/anonymity fixes (clients):
14569 - Clients and bridges no longer send TLS certificate chains on
14570 outgoing OR connections. Previously, each client or bridge would
14571 use the same cert chain for all outgoing OR connections until
14572 its IP address changes, which allowed any relay that the client
14573 or bridge contacted to determine which entry guards it is using.
14574 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14575 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14576 no longer considers that connection as suitable for satisfying a
14577 circuit EXTEND request. Now relays can protect clients from the
14578 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14579 - Directory authorities no longer assign the Guard flag to relays
14580 that haven't upgraded to the above "refuse EXTEND requests
14581 to client connections" fix. Now directory authorities can
14582 protect clients from the CVE-2011-2768 issue even if neither
14583 the clients nor the relays have upgraded yet. There's a new
14584 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
14585 to let us transition smoothly, else tomorrow there would be no
14588 o Privacy/anonymity fixes (bridge enumeration):
14589 - Bridge relays now do their directory fetches inside Tor TLS
14590 connections, like all the other clients do, rather than connecting
14591 directly to the DirPort like public relays do. Removes another
14592 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
14593 - Bridges relays now build circuits for themselves in a more similar
14594 way to how clients build them. Removes another avenue for
14595 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
14596 when bridges were introduced.
14597 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14598 that they initiated. Relays could distinguish incoming bridge
14599 connections from client connections, creating another avenue for
14600 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14601 Found by "frosty_un".
14604 - Fix a crash bug when changing node restrictions while a DNS lookup
14605 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
14607 - Don't launch a useless circuit after failing to use one of a
14608 hidden service's introduction points. Previously, we would
14609 launch a new introduction circuit, but not set the hidden service
14610 which that circuit was intended to connect to, so it would never
14611 actually be used. A different piece of code would then create a
14612 new introduction circuit correctly. Bug reported by katmagic and
14613 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
14616 - Change an integer overflow check in the OpenBSD_Malloc code so
14617 that GCC is less likely to eliminate it as impossible. Patch
14618 from Mansour Moufid. Fixes bug 4059.
14619 - When a hidden service turns an extra service-side introduction
14620 circuit into a general-purpose circuit, free the rend_data and
14621 intro_key fields first, so we won't leak memory if the circuit
14622 is cannibalized for use as another service-side introduction
14623 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
14624 - Bridges now skip DNS self-tests, to act a little more stealthily.
14625 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
14626 bridges. Patch by "warms0x".
14627 - Fix internal bug-checking logic that was supposed to catch
14628 failures in digest generation so that it will fail more robustly
14629 if we ask for a nonexistent algorithm. Found by Coverity Scan.
14630 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
14631 - Report any failure in init_keys() calls launched because our
14632 IP address has changed. Spotted by Coverity Scan. Bugfix on
14633 0.1.1.4-alpha; fixes CID 484.
14635 o Minor bugfixes (log messages and documentation):
14636 - Remove a confusing dollar sign from the example fingerprint in the
14637 man page, and also make the example fingerprint a valid one. Fixes
14638 bug 4309; bugfix on 0.2.1.3-alpha.
14639 - The next version of Windows will be called Windows 8, and it has
14640 a major version of 6, minor version of 2. Correctly identify that
14641 version instead of calling it "Very recent version". Resolves
14642 ticket 4153; reported by funkstar.
14643 - Downgrade log messages about circuit timeout calibration from
14644 "notice" to "info": they don't require or suggest any human
14645 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
14646 bugfix on 0.2.2.14-alpha.
14649 - Turn on directory request statistics by default and include them in
14650 extra-info descriptors. Don't break if we have no GeoIP database.
14651 Backported from 0.2.3.1-alpha; implements ticket 3951.
14652 - Update to the October 4 2011 Maxmind GeoLite Country database.
14655 Changes in version 0.2.1.31 - 2011-10-26
14656 Tor 0.2.1.31 backports important security and privacy fixes for
14657 oldstable. This release is intended only for package maintainers and
14658 others who cannot use the 0.2.2 stable series. All others should be
14659 using Tor 0.2.2.x or newer.
14661 o Security fixes (also included in 0.2.2.x):
14662 - Replace all potentially sensitive memory comparison operations
14663 with versions whose runtime does not depend on the data being
14664 compared. This will help resist a class of attacks where an
14665 adversary can use variations in timing information to learn
14666 sensitive data. Fix for one case of bug 3122. (Safe memcmp
14667 implementation by Robert Ransom based partially on code by DJB.)
14668 - Fix an assert in parsing router descriptors containing IPv6
14669 addresses. This one took down the directory authorities when
14670 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
14672 o Privacy/anonymity fixes (also included in 0.2.2.x):
14673 - Clients and bridges no longer send TLS certificate chains on
14674 outgoing OR connections. Previously, each client or bridge would
14675 use the same cert chain for all outgoing OR connections until
14676 its IP address changes, which allowed any relay that the client
14677 or bridge contacted to determine which entry guards it is using.
14678 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14679 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14680 no longer considers that connection as suitable for satisfying a
14681 circuit EXTEND request. Now relays can protect clients from the
14682 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14683 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14684 that they initiated. Relays could distinguish incoming bridge
14685 connections from client connections, creating another avenue for
14686 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14687 Found by "frosty_un".
14688 - When receiving a hidden service descriptor, check that it is for
14689 the hidden service we wanted. Previously, Tor would store any
14690 hidden service descriptors that a directory gave it, whether it
14691 wanted them or not. This wouldn't have let an attacker impersonate
14692 a hidden service, but it did let directories pre-seed a client
14693 with descriptors that it didn't want. Bugfix on 0.0.6.
14694 - Avoid linkability based on cached hidden service descriptors: forget
14695 all hidden service descriptors cached as a client when processing a
14696 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
14697 - Make the bridge directory authority refuse to answer directory
14698 requests for "all" descriptors. It used to include bridge
14699 descriptors in its answer, which was a major information leak.
14700 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
14701 - Don't attach new streams to old rendezvous circuits after SIGNAL
14702 NEWNYM. Previously, we would keep using an existing rendezvous
14703 circuit if it remained open (i.e. if it were kept open by a
14704 long-lived stream, or if a new stream were attached to it before
14705 Tor could notice that it was old and no longer in use). Bugfix on
14706 0.1.1.15-rc; fixes bug 3375.
14708 o Minor bugfixes (also included in 0.2.2.x):
14709 - When we restart our relay, we might get a successful connection
14710 from the outside before we've started our reachability tests,
14711 triggering a warning: "ORPort found reachable, but I have no
14712 routerinfo yet. Failing to inform controller of success." This
14713 bug was harmless unless Tor is running under a controller
14714 like Vidalia, in which case the controller would never get a
14715 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
14717 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
14718 enabled. Fixes bug 1526.
14719 - Remove undocumented option "-F" from tor-resolve: it hasn't done
14720 anything since 0.2.1.16-rc.
14721 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
14722 None of the cases where we did this before were wrong, but by making
14723 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
14724 - Fix a rare crash bug that could occur when a client was configured
14725 with a large number of bridges. Fixes bug 2629; bugfix on
14726 0.2.1.2-alpha. Bugfix by trac user "shitlei".
14727 - Correct the warning displayed when a rendezvous descriptor exceeds
14728 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
14730 - Fix an uncommon assertion failure when running with DNSPort under
14731 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
14732 - When warning about missing zlib development packages during compile,
14733 give the correct package names. Bugfix on 0.2.0.1-alpha.
14734 - Require that introduction point keys and onion keys have public
14735 exponent 65537. Bugfix on 0.2.0.10-alpha.
14736 - Do not crash when our configuration file becomes unreadable, for
14737 example due to a permissions change, between when we start up
14738 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
14740 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
14742 - Always NUL-terminate the sun_path field of a sockaddr_un before
14743 passing it to the kernel. (Not a security issue: kernels are
14744 smart enough to reject bad sockaddr_uns.) Found by Coverity;
14745 CID #428. Bugfix on Tor 0.2.0.3-alpha.
14746 - Don't stack-allocate the list of supplementary GIDs when we're
14747 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
14748 could take up to 256K, which is way too much stack. Found by
14749 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
14751 o Minor bugfixes (only in 0.2.1.x):
14752 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
14753 rely on them. Bugfix on 0.2.1.30.
14754 - Use git revisions instead of svn revisions when generating our
14755 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
14757 o Minor features (also included in 0.2.2.x):
14758 - Adjust the expiration time on our SSL session certificates to
14759 better match SSL certs seen in the wild. Resolves ticket 4014.
14760 - Allow nameservers with IPv6 address. Resolves bug 2574.
14761 - Update to the October 4 2011 Maxmind GeoLite Country database.
14764 Changes in version 0.2.3.5-alpha - 2011-09-28
14765 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
14766 bridge relays; fixes an assertion error that many users started hitting
14767 today; and adds the ability to refill token buckets more often than
14768 once per second, allowing significant performance improvements.
14771 - Bridge relays now do their directory fetches inside Tor TLS
14772 connections, like all the other clients do, rather than connecting
14773 directly to the DirPort like public relays do. Removes another
14774 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
14775 - Bridges relays now build circuits for themselves in a more similar
14776 way to how clients build them. Removes another avenue for
14777 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
14778 when bridges were introduced.
14781 - Fix an "Assertion md->held_by_node == 1 failed" error that could
14782 occur when the same microdescriptor was referenced by two node_t
14783 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
14785 o Major features (networking):
14786 - Add a new TokenBucketRefillInterval option to refill token buckets
14787 more frequently than once per second. This should improve network
14788 performance, alleviate queueing problems, and make traffic less
14789 bursty. Implements proposal 183; closes ticket 3630. Design by
14790 Florian Tschorsch and Björn Scheuermann; implementation by
14794 - Change an integer overflow check in the OpenBSD_Malloc code so
14795 that GCC is less likely to eliminate it as impossible. Patch
14796 from Mansour Moufid. Fixes bug 4059.
14798 o Minor bugfixes (usability):
14799 - Downgrade log messages about circuit timeout calibration from
14800 "notice" to "info": they don't require or suggest any human
14801 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
14802 bugfix on 0.2.2.14-alpha.
14804 o Minor features (diagnostics):
14805 - When the system call to create a listener socket fails, log the
14806 error message explaining why. This may help diagnose bug 4027.
14809 Changes in version 0.2.3.4-alpha - 2011-09-13
14810 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
14811 tweak to Tor's TLS handshake that makes relays and bridges that run
14812 this new version reachable from Iran again. It also fixes a few new
14813 bugs in 0.2.3.x, and teaches relays to recognize when they're not
14814 listed in the network consensus and republish.
14816 o Major bugfixes (also part of 0.2.2.33):
14817 - Avoid an assertion failure when reloading a configuration with
14818 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
14819 3923; bugfix on 0.2.2.25-alpha.
14821 o Minor features (security, also part of 0.2.2.33):
14822 - Check for replays of the public-key encrypted portion of an
14823 INTRODUCE1 cell, in addition to the current check for replays of
14824 the g^x value. This prevents a possible class of active attacks
14825 by an attacker who controls both an introduction point and a
14826 rendezvous point, and who uses the malleability of AES-CTR to
14827 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
14828 that these attacks are infeasible (requiring the attacker to send
14829 on the order of zettabytes of altered cells in a short interval),
14830 but we'd rather block them off in case there are any classes of
14831 this attack that we missed. Reported by Willem Pinckaers.
14833 o Minor features (also part of 0.2.2.33):
14834 - Adjust the expiration time on our SSL session certificates to
14835 better match SSL certs seen in the wild. Resolves ticket 4014.
14836 - Change the default required uptime for a relay to be accepted as
14837 a HSDir (hidden service directory) from 24 hours to 25 hours.
14838 Improves on 0.2.0.10-alpha; resolves ticket 2649.
14839 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
14840 authorities to abstain from voting on assignment of the HSDir
14841 consensus flag. Related to bug 2649.
14842 - Update to the September 6 2011 Maxmind GeoLite Country database.
14844 o Minor bugfixes (also part of 0.2.2.33):
14845 - Demote the 'replay detected' log message emitted when a hidden
14846 service receives the same Diffie-Hellman public key in two different
14847 INTRODUCE2 cells to info level. A normal Tor client can cause that
14848 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
14849 fixes part of bug 2442.
14850 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
14851 level. There is nothing that a hidden service's operator can do
14852 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
14854 - Clarify a log message specifying the characters permitted in
14855 HiddenServiceAuthorizeClient client names. Previously, the log
14856 message said that "[A-Za-z0-9+-_]" were permitted; that could have
14857 given the impression that every ASCII character between "+" and "_"
14858 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
14860 o Build fixes (also part of 0.2.2.33):
14861 - Clean up some code issues that prevented Tor from building on older
14862 BSDs. Fixes bug 3894; reported by "grarpamp".
14863 - Search for a platform-specific version of "ar" when cross-compiling.
14864 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
14867 - Fix a bug where the SocksPort option (for example) would get
14868 ignored and replaced by the default if a SocksListenAddress
14869 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
14873 - Relays now try regenerating and uploading their descriptor more
14874 frequently if they are not listed in the consensus, or if the
14875 version of their descriptor listed in the consensus is too
14876 old. This fix should prevent situations where a server declines
14877 to re-publish itself because it has done so too recently, even
14878 though the authorities decided not to list its recent-enough
14879 descriptor. Fix for bug 3327.
14882 - Relays now include a reason for regenerating their descriptors
14883 in an HTTP header when uploading to the authorities. This will
14884 make it easier to debug descriptor-upload issues in the future.
14885 - When starting as root and then changing our UID via the User
14886 control option, and we have a ControlSocket configured, make sure
14887 that the ControlSocket is owned by the same account that Tor will
14888 run under. Implements ticket 3421; fix by Jérémy Bobbio.
14891 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
14892 utility function used in the control-port code). This shouldn't
14893 ever happen unless Tor is completely out of memory, but if it did
14894 happen and Tor somehow recovered from it, Tor could have sent a log
14895 message to a control port in the middle of a reply to a controller
14896 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
14897 - Make 'FetchUselessDescriptors' cause all descriptor types and
14898 all consensus types (including microdescriptors) to get fetched.
14899 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
14901 o Code refactoring:
14902 - Make a new "entry connection" struct as an internal subtype of "edge
14903 connection", to simplify the code and make exit connections smaller.
14906 Changes in version 0.2.2.33 - 2011-09-13
14907 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
14908 TLS handshake that makes relays and bridges that run this new version
14909 reachable from Iran again.
14912 - Avoid an assertion failure when reloading a configuration with
14913 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
14914 3923; bugfix on 0.2.2.25-alpha.
14916 o Minor features (security):
14917 - Check for replays of the public-key encrypted portion of an
14918 INTRODUCE1 cell, in addition to the current check for replays of
14919 the g^x value. This prevents a possible class of active attacks
14920 by an attacker who controls both an introduction point and a
14921 rendezvous point, and who uses the malleability of AES-CTR to
14922 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
14923 that these attacks are infeasible (requiring the attacker to send
14924 on the order of zettabytes of altered cells in a short interval),
14925 but we'd rather block them off in case there are any classes of
14926 this attack that we missed. Reported by Willem Pinckaers.
14929 - Adjust the expiration time on our SSL session certificates to
14930 better match SSL certs seen in the wild. Resolves ticket 4014.
14931 - Change the default required uptime for a relay to be accepted as
14932 a HSDir (hidden service directory) from 24 hours to 25 hours.
14933 Improves on 0.2.0.10-alpha; resolves ticket 2649.
14934 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
14935 authorities to abstain from voting on assignment of the HSDir
14936 consensus flag. Related to bug 2649.
14937 - Update to the September 6 2011 Maxmind GeoLite Country database.
14939 o Minor bugfixes (documentation and log messages):
14940 - Correct the man page to explain that HashedControlPassword and
14941 CookieAuthentication can both be set, in which case either method
14942 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
14943 when we decided to allow these config options to both be set. Issue
14944 raised by bug 3898.
14945 - Demote the 'replay detected' log message emitted when a hidden
14946 service receives the same Diffie-Hellman public key in two different
14947 INTRODUCE2 cells to info level. A normal Tor client can cause that
14948 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
14949 fixes part of bug 2442.
14950 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
14951 level. There is nothing that a hidden service's operator can do
14952 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
14954 - Clarify a log message specifying the characters permitted in
14955 HiddenServiceAuthorizeClient client names. Previously, the log
14956 message said that "[A-Za-z0-9+-_]" were permitted; that could have
14957 given the impression that every ASCII character between "+" and "_"
14958 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
14961 - Provide a substitute implementation of lround() for MSVC, which
14962 apparently lacks it. Patch from Gisle Vanem.
14963 - Clean up some code issues that prevented Tor from building on older
14964 BSDs. Fixes bug 3894; reported by "grarpamp".
14965 - Search for a platform-specific version of "ar" when cross-compiling.
14966 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
14969 Changes in version 0.2.3.3-alpha - 2011-09-01
14970 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
14971 security, and provides client-side support for the microdescriptor
14972 and optimistic data features introduced earlier in the 0.2.3.x
14973 series. It also includes numerous critical bugfixes in the (optional)
14974 bufferevent-based networking backend.
14976 o Major features (stream isolation):
14977 - You can now configure Tor so that streams from different
14978 applications are isolated on different circuits, to prevent an
14979 attacker who sees your streams as they leave an exit node from
14980 linking your sessions to one another. To do this, choose some way
14981 to distinguish the applications: have them connect to different
14982 SocksPorts, or have one of them use SOCKS4 while the other uses
14983 SOCKS5, or have them pass different authentication strings to the
14984 SOCKS proxy. Then, use the new SocksPort syntax to configure the
14985 degree of isolation you need. This implements Proposal 171.
14986 - There's a new syntax for specifying multiple client ports (such as
14987 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
14988 multiple *Port entries with full addr:port syntax on each.
14989 The old *ListenAddress format is still supported, but you can't
14990 mix it with the new *Port syntax.
14992 o Major features (other):
14993 - Enable microdescriptor fetching by default for clients. This allows
14994 clients to download a much smaller amount of directory information.
14995 To disable it (and go back to the old-style consensus and
14996 descriptors), set "UseMicrodescriptors 0" in your torrc file.
14997 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
14998 "PortForwarding" config option), now supports Windows.
14999 - When using an exit relay running 0.2.3.x, clients can now
15000 "optimistically" send data before the exit relay reports that
15001 the stream has opened. This saves a round trip when starting
15002 connections where the client speaks first (such as web browsing).
15003 This behavior is controlled by a consensus parameter (currently
15004 disabled). To turn it on or off manually, use the "OptimisticData"
15005 torrc option. Implements proposal 181; code by Ian Goldberg.
15007 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
15008 - When using IOCP on Windows, we need to enable Libevent windows
15010 - The IOCP backend now works even when the user has not specified
15011 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
15012 Fixes part of bug 3752.
15013 - Correctly record the bytes we've read and written when using
15014 bufferevents, so that we can include them in our bandwidth history
15015 and advertised bandwidth. Fixes bug 3803.
15016 - Apply rate-limiting only at the bottom of a chain of filtering
15017 bufferevents. This prevents us from filling up internal read
15018 buffers and violating rate-limits when filtering bufferevents
15019 are enabled. Fixes part of bug 3804.
15020 - Add high-watermarks to the output buffers for filtered
15021 bufferevents. This prevents us from filling up internal write
15022 buffers and wasting CPU cycles when filtering bufferevents are
15023 enabled. Fixes part of bug 3804.
15024 - Correctly notice when data has been written from a bufferevent
15025 without flushing it completely. Fixes bug 3805.
15026 - Fix a bug where server-side tunneled bufferevent-based directory
15027 streams would get closed prematurely. Fixes bug 3814.
15028 - Fix a use-after-free error with per-connection rate-limiting
15029 buckets. Fixes bug 3888.
15031 o Major bugfixes (also part of 0.2.2.31-rc):
15032 - If we're configured to write our ControlPorts to disk, only write
15033 them after switching UID and creating the data directory. This way,
15034 we don't fail when starting up with a nonexistent DataDirectory
15035 and a ControlPortWriteToFile setting based on that directory. Fixes
15036 bug 3747; bugfix on Tor 0.2.2.26-beta.
15039 - Added a new CONF_CHANGED event so that controllers can be notified
15040 of any configuration changes made by other controllers, or by the
15041 user. Implements ticket 1692.
15042 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
15043 leak when using bufferevents, and lets Libevent worry about how to
15044 best copy data out of a buffer.
15045 - Replace files in stats/ rather than appending to them. Now that we
15046 include statistics in extra-info descriptors, it makes no sense to
15047 keep old statistics forever. Implements ticket 2930.
15049 o Minor features (build compatibility):
15050 - Limited, experimental support for building with nmake and MSVC.
15051 - Provide a substitute implementation of lround() for MSVC, which
15052 apparently lacks it. Patch from Gisle Vanem.
15054 o Minor features (also part of 0.2.2.31-rc):
15055 - Update to the August 2 2011 Maxmind GeoLite Country database.
15057 o Minor bugfixes (on 0.2.3.x-alpha):
15058 - Fix a spurious warning when parsing SOCKS requests with
15059 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
15060 - Get rid of a harmless warning that could happen on relays running
15061 with bufferevents. The warning was caused by someone doing an http
15062 request to a relay's orport. Also don't warn for a few related
15063 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
15065 o Minor bugfixes (on 2.2.x and earlier):
15066 - Correct the man page to explain that HashedControlPassword and
15067 CookieAuthentication can both be set, in which case either method
15068 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
15069 when we decided to allow these config options to both be set. Issue
15070 raised by bug 3898.
15071 - The "--quiet" and "--hush" options now apply not only to Tor's
15072 behavior before logs are configured, but also to Tor's behavior in
15073 the absense of configured logs. Fixes bug 3550; bugfix on
15076 o Minor bugfixes (also part of 0.2.2.31-rc):
15077 - Write several files in text mode, on OSes that distinguish text
15078 mode from binary mode (namely, Windows). These files are:
15079 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
15080 that collect those statistics; 'client_keys' and 'hostname' for
15081 hidden services that use authentication; and (in the tor-gencert
15082 utility) newly generated identity and signing keys. Previously,
15083 we wouldn't specify text mode or binary mode, leading to an
15084 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
15085 the DirRecordUsageByCountry option which would have triggered
15086 the assertion failure was added), although this assertion failure
15087 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
15088 - Selectively disable deprecation warnings on OS X because Lion
15089 started deprecating the shipped copy of openssl. Fixes bug 3643.
15090 - Remove an extra pair of quotation marks around the error
15091 message in control-port STATUS_GENERAL BUG events. Bugfix on
15092 0.1.2.6-alpha; fixes bug 3732.
15093 - When unable to format an address as a string, report its value
15094 as "???" rather than reusing the last formatted address. Bugfix
15097 o Code simplifications and refactoring:
15098 - Rewrite the listener-selection logic so that parsing which ports
15099 we want to listen on is now separate from binding to the ports
15103 - Building Tor with bufferevent support now requires Libevent
15104 2.0.13-stable or later. Previous versions of Libevent had bugs in
15105 SSL-related bufferevents and related issues that would make Tor
15106 work badly with bufferevents. Requiring 2.0.13-stable also allows
15107 Tor with bufferevents to take advantage of Libevent APIs
15108 introduced after 2.0.8-rc.
15111 Changes in version 0.2.2.32 - 2011-08-27
15112 The Tor 0.2.2 release series is dedicated to the memory of Andreas
15113 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
15114 a founder of the PETS community, a leader in our field, a mentor,
15115 and a friend. He left us with these words: "I had the possibility
15116 to contribute to this world that is not as it should be. I hope I
15117 could help in some areas to make the world a better place, and that
15118 I could also encourage other people to be engaged in improving the
15119 world. Please, stay engaged. This world needs you, your love, your
15120 initiative -- now I cannot be part of that anymore."
15122 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
15123 ready. More than two years in the making, this release features improved
15124 client performance and hidden service reliability, better compatibility
15125 for Android, correct behavior for bridges that listen on more than
15126 one address, more extensible and flexible directory object handling,
15127 better reporting of network statistics, improved code security, and
15128 many many other features and bugfixes.
15131 Changes in version 0.2.2.31-rc - 2011-08-17
15132 Tor 0.2.2.31-rc is the second and hopefully final release candidate
15133 for the Tor 0.2.2.x series.
15136 - Remove an extra pair of quotation marks around the error
15137 message in control-port STATUS_GENERAL BUG events. Bugfix on
15138 0.1.2.6-alpha; fixes bug 3732.
15139 - If we're configured to write our ControlPorts to disk, only write
15140 them after switching UID and creating the data directory. This way,
15141 we don't fail when starting up with a nonexistent DataDirectory
15142 and a ControlPortWriteToFile setting based on that directory. Fixes
15143 bug 3747; bugfix on Tor 0.2.2.26-beta.
15146 - Update to the August 2 2011 Maxmind GeoLite Country database.
15149 - Allow GETINFO fingerprint to return a fingerprint even when
15150 we have not yet built a router descriptor. Fixes bug 3577;
15151 bugfix on 0.2.0.1-alpha.
15152 - Write several files in text mode, on OSes that distinguish text
15153 mode from binary mode (namely, Windows). These files are:
15154 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
15155 that collect those statistics; 'client_keys' and 'hostname' for
15156 hidden services that use authentication; and (in the tor-gencert
15157 utility) newly generated identity and signing keys. Previously,
15158 we wouldn't specify text mode or binary mode, leading to an
15159 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
15160 the DirRecordUsageByCountry option which would have triggered
15161 the assertion failure was added), although this assertion failure
15162 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
15163 - Selectively disable deprecation warnings on OS X because Lion
15164 started deprecating the shipped copy of openssl. Fixes bug 3643.
15165 - When unable to format an address as a string, report its value
15166 as "???" rather than reusing the last formatted address. Bugfix
15170 Changes in version 0.2.3.2-alpha - 2011-07-18
15171 Tor 0.2.3.2-alpha introduces two new experimental features:
15172 microdescriptors and pluggable transports. It also continues cleaning
15173 up a variety of recently introduced features.
15176 - Clients can now use microdescriptors instead of regular descriptors
15177 to build circuits. Microdescriptors are authority-generated
15178 summaries of regular descriptors' contents, designed to change
15179 very rarely (see proposal 158 for details). This feature is
15180 designed to save bandwidth, especially for clients on slow internet
15181 connections. It's off by default for now, since nearly no caches
15182 support it, but it will be on-by-default for clients in a future
15183 version. You can use the UseMicrodescriptors option to turn it on.
15184 - Tor clients using bridges can now be configured to use a separate
15185 'transport' proxy for each bridge. This approach helps to resist
15186 censorship by allowing bridges to use protocol obfuscation
15187 plugins. It implements part of proposal 180. Implements ticket 2841.
15188 - While we're trying to bootstrap, record how many TLS connections
15189 fail in each state, and report which states saw the most failures
15190 in response to any bootstrap failures. This feature may speed up
15191 diagnosis of censorship events. Implements ticket 3116.
15193 o Major bugfixes (on 0.2.3.1-alpha):
15194 - When configuring a large set of nodes in EntryNodes (as with
15195 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
15196 random subset to be guards, and choose them in random
15197 order. Fixes bug 2798.
15198 - Tor could crash when remembering a consensus in a non-used consensus
15199 flavor without having a current consensus set. Fixes bug 3361.
15200 - Comparing an unknown address to a microdescriptor's shortened exit
15201 policy would always give a "rejected" result. Fixes bug 3599.
15202 - Using microdescriptors as a client no longer prevents Tor from
15203 uploading and downloading hidden service descriptors. Fixes
15207 - Allow nameservers with IPv6 address. Resolves bug 2574.
15208 - Accept attempts to include a password authenticator in the
15209 handshake, as supported by SOCKS5. This handles SOCKS clients that
15210 don't know how to omit a password when authenticating. Resolves
15212 - When configuring a large set of nodes in EntryNodes, and there are
15213 enough of them listed as Guard so that we don't need to consider
15214 the non-guard entries, prefer the ones listed with the Guard flag.
15215 - Check for and recover from inconsistency in the microdescriptor
15216 cache. This will make it harder for us to accidentally free a
15217 microdescriptor without removing it from the appropriate data
15218 structures. Fixes issue 3135; issue noted by "wanoskarnet".
15219 - Log SSL state transitions at log level DEBUG, log domain
15220 HANDSHAKE. This can be useful for debugging censorship events.
15221 Implements ticket 3264.
15222 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
15223 implements ticket 3439.
15225 o Minor bugfixes (on 0.2.3.1-alpha):
15226 - Do not free all general-purpose regular descriptors just
15227 because microdescriptor use is enabled. Fixes bug 3113.
15228 - Correctly link libevent_openssl when --enable-static-libevent
15229 is passed to configure. Fixes bug 3118.
15230 - Bridges should not complain during their heartbeat log messages that
15231 they are unlisted in the consensus: that's more or less the point
15232 of being a bridge. Fixes bug 3183.
15233 - Report a SIGNAL event to controllers when acting on a delayed
15234 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
15235 event to the controller if we acted on a SIGNAL NEWNYM command
15236 immediately, and otherwise not report a SIGNAL event for the
15237 command at all. Fixes bug 3349.
15238 - Fix a crash when handling the SIGNAL controller command or
15239 reporting ERR-level status events with bufferevents enabled. Found
15240 by Robert Ransom. Fixes bug 3367.
15241 - Always ship the tor-fw-helper manpage in our release tarballs.
15242 Fixes bug 3389. Reported by Stephen Walker.
15243 - Fix a class of double-mark-for-close bugs when bufferevents
15244 are enabled. Fixes bug 3403.
15245 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
15246 - Add SIGNAL to the list returned by the 'GETINFO events/names'
15247 control-port command. Fixes part of bug 3465.
15248 - Prevent using negative indices during unit test runs when read_all()
15249 fails. Spotted by coverity.
15250 - Fix a rare memory leak when checking the nodelist without it being
15251 present. Found by coverity.
15252 - Only try to download a microdescriptor-flavored consensus from
15253 a directory cache that provides them.
15255 o Minor bugfixes (on 0.2.2.x and earlier):
15256 - Assert that hidden-service-related operations are not performed
15257 using single-hop circuits. Previously, Tor would assert that
15258 client-side streams are not attached to single-hop circuits,
15259 but not that other sensitive operations on the client and service
15260 side are not performed using single-hop circuits. Fixes bug 3332;
15262 - Don't publish a new relay descriptor when we reload our onion key,
15263 unless the onion key has actually changed. Fixes bug 3263 and
15264 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
15265 - Allow GETINFO fingerprint to return a fingerprint even when
15266 we have not yet built a router descriptor. Fixes bug 3577;
15267 bugfix on 0.2.0.1-alpha.
15268 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
15269 on 0.2.2.4-alpha; fixes bug 3427.
15271 o Code simplification and refactoring:
15272 - Use tor_sscanf() in place of scanf() in more places through the
15273 code. This makes us a little more locale-independent, and
15274 should help shut up code-analysis tools that can't tell
15275 a safe sscanf string from a dangerous one.
15276 - Use tt_assert(), not tor_assert(), for checking for test failures.
15277 This makes the unit tests more able to go on in the event that
15279 - Split connection_about_to_close() into separate functions for each
15283 - On Windows, we now define the _WIN32_WINNT macros only if they
15284 are not already defined. This lets the person building Tor decide,
15285 if they want, to require a later version of Windows.
15288 Changes in version 0.2.2.30-rc - 2011-07-07
15289 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
15290 series. It fixes a few smaller bugs, but generally appears stable.
15291 Please test it and let us know whether it is!
15294 - Send a SUCCEEDED stream event to the controller when a reverse
15295 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
15296 discovered by katmagic.
15297 - Always NUL-terminate the sun_path field of a sockaddr_un before
15298 passing it to the kernel. (Not a security issue: kernels are
15299 smart enough to reject bad sockaddr_uns.) Found by Coverity;
15300 CID #428. Bugfix on Tor 0.2.0.3-alpha.
15301 - Don't stack-allocate the list of supplementary GIDs when we're
15302 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
15303 could take up to 256K, which is way too much stack. Found by
15304 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
15305 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
15306 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
15307 fixes part of bug 3465.
15308 - Fix a memory leak when receiving a descriptor for a hidden
15309 service we didn't ask for. Found by Coverity; CID #30. Bugfix
15313 - Update to the July 1 2011 Maxmind GeoLite Country database.
15316 Changes in version 0.2.2.29-beta - 2011-06-20
15317 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
15318 have bridge lines in their torrc but don't want to use them; gets
15319 us closer to having the control socket feature working on Debian;
15320 and fixes a variety of smaller bugs.
15323 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
15324 When we changed the default behavior to "use bridges if any
15325 are listed in the torrc", we surprised users who had bridges
15326 in their torrc files but who didn't actually want to use them.
15327 Partial resolution for bug 3354.
15330 - Don't attach new streams to old rendezvous circuits after SIGNAL
15331 NEWNYM. Previously, we would keep using an existing rendezvous
15332 circuit if it remained open (i.e. if it were kept open by a
15333 long-lived stream, or if a new stream were attached to it before
15334 Tor could notice that it was old and no longer in use). Bugfix on
15335 0.1.1.15-rc; fixes bug 3375.
15338 - Fix a bug when using ControlSocketsGroupWritable with User. The
15339 directory's group would be checked against the current group, not
15340 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
15341 bugfix on 0.2.2.26-beta.
15342 - Make connection_printf_to_buf()'s behavior sane. Its callers
15343 expect it to emit a CRLF iff the format string ends with CRLF;
15344 it actually emitted a CRLF iff (a) the format string ended with
15345 CRLF or (b) the resulting string was over 1023 characters long or
15346 (c) the format string did not end with CRLF *and* the resulting
15347 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
15348 fixes part of bug 3407.
15349 - Make send_control_event_impl()'s behavior sane. Its callers
15350 expect it to always emit a CRLF at the end of the string; it
15351 might have emitted extra control characters as well. Bugfix on
15352 0.1.1.9-alpha; fixes another part of bug 3407.
15353 - Make crypto_rand_int() check the value of its input correctly.
15354 Previously, it accepted values up to UINT_MAX, but could return a
15355 negative number if given a value above INT_MAX+1. Found by George
15356 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
15357 - Avoid a segfault when reading a malformed circuit build state
15358 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
15360 - When asked about a DNS record type we don't support via a
15361 client DNSPort, reply with NOTIMPL rather than an empty
15362 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
15363 - Fix a rare memory leak during stats writing. Found by coverity.
15366 - Update to the June 1 2011 Maxmind GeoLite Country database.
15368 o Code simplifications and refactoring:
15369 - Remove some dead code as indicated by coverity.
15370 - Remove a few dead assignments during router parsing. Found by
15372 - Add some forgotten return value checks during unit tests. Found
15374 - Don't use 1-bit wide signed bit fields. Found by coverity.
15377 Changes in version 0.2.2.28-beta - 2011-06-04
15378 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
15379 fixed a big bug in whether relays stay in the consensus consistently,
15380 we moved closer to handling bridges and hidden services correctly,
15381 and we started the process of better handling the dreaded "my Vidalia
15382 died, and now my Tor demands a password when I try to reconnect to it"
15386 - Don't decide to make a new descriptor when receiving a HUP signal.
15387 This bug has caused a lot of 0.2.2.x relays to disappear from the
15388 consensus periodically. Fixes the most common case of triggering
15389 bug 1810; bugfix on 0.2.2.7-alpha.
15390 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
15391 - Don't try to build descriptors if "ORPort auto" is set and we
15392 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
15394 - Resolve a crash that occurred when setting BridgeRelay to 1 with
15395 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
15396 - Apply circuit timeouts to opened hidden-service-related circuits
15397 based on the correct start time. Previously, we would apply the
15398 circuit build timeout based on time since the circuit's creation;
15399 it was supposed to be applied based on time since the circuit
15400 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
15401 - Use the same circuit timeout for client-side introduction
15402 circuits as for other four-hop circuits, rather than the timeout
15403 for single-hop directory-fetch circuits; the shorter timeout may
15404 have been appropriate with the static circuit build timeout in
15405 0.2.1.x and earlier, but caused many hidden service access attempts
15406 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
15407 on 0.2.2.2-alpha; fixes another part of bug 1297.
15408 - In ticket 2511 we fixed a case where you could use an unconfigured
15409 bridge if you had configured it as a bridge the last time you ran
15410 Tor. Now fix another edge case: if you had configured it as a bridge
15411 but then switched to a different bridge via the controller, you
15412 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
15416 - Add an __OwningControllerProcess configuration option and a
15417 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
15418 that when it exits, Tor will shut down. Implements feature 3049.
15419 - If "UseBridges 1" is set and no bridges are configured, Tor will
15420 now refuse to build any circuits until some bridges are set.
15421 If "UseBridges auto" is set, Tor will use bridges if they are
15422 configured and we are not running as a server, but otherwise will
15423 make circuits as usual. The new default is "auto". Patch by anonym,
15424 so the Tails LiveCD can stop automatically revealing you as a Tor
15428 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
15429 - Remove a trailing asterisk from "exit-policy/default" in the
15430 output of the control port command "GETINFO info/names". Bugfix
15432 - Use a wide type to hold sockets when built for 64-bit Windows builds.
15434 - Warn when the user configures two HiddenServiceDir lines that point
15435 to the same directory. Bugfix on 0.0.6 (the version introducing
15436 HiddenServiceDir); fixes bug 3289.
15437 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
15438 part of bug 2748; bugfix on 0.2.0.10-alpha.
15439 - Log malformed requests for rendezvous descriptors as protocol
15440 warnings, not warnings. Also, use a more informative log message
15441 in case someone sees it at log level warning without prior
15442 info-level messages. Fixes the other part of bug 2748; bugfix
15444 - Clear the table recording the time of the last request for each
15445 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
15446 Previously, we would clear our HS descriptor cache on SIGNAL
15447 NEWNYM, but if we had previously retrieved a descriptor (or tried
15448 to) from every directory responsible for it, we would refuse to
15449 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
15451 - Fix a log message that said "bits" while displaying a value in
15452 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
15454 - When checking for 1024-bit keys, check for 1024 bits, not 128
15455 bytes. This allows Tor to correctly discard keys of length 1017
15456 through 1023. Bugfix on 0.0.9pre5.
15459 - Relays now log the reason for publishing a new relay descriptor,
15460 so we have a better chance of hunting down instances of bug 1810.
15461 Resolves ticket 3252.
15462 - Revise most log messages that refer to nodes by nickname to
15463 instead use the "$key=nickname at address" format. This should be
15464 more useful, especially since nicknames are less and less likely
15465 to be unique. Resolves ticket 3045.
15466 - Log (at info level) when purging pieces of hidden-service-client
15467 state because of SIGNAL NEWNYM.
15470 - Remove undocumented option "-F" from tor-resolve: it hasn't done
15471 anything since 0.2.1.16-rc.
15474 Changes in version 0.2.2.27-beta - 2011-05-18
15475 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
15476 release, and also adds a few more general bugfixes.
15479 - Fix a crash bug when changing bridges in a running Tor process.
15480 Fixes bug 3213; bugfix on 0.2.2.26-beta.
15481 - When the controller configures a new bridge, don't wait 10 to 60
15482 seconds before trying to fetch its descriptor. Bugfix on
15483 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
15486 - Require that onion keys have exponent 65537 in microdescriptors too.
15487 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
15488 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
15489 Changed the limit to 512 characters by removing base64 newlines.
15490 Fixes bug 2752. Fix by Michael Yakubovich.
15491 - When a client starts or stops using bridges, never use a circuit
15492 that was built before the configuration change. This behavior could
15493 put at risk a user who uses bridges to ensure that her traffic
15494 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
15498 Changes in version 0.2.2.26-beta - 2011-05-17
15499 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
15500 also introduces a new "socksport auto" approach that should make it
15501 easier to run multiple Tors on the same system, and does a lot of
15502 cleanup to get us closer to a release candidate.
15504 o Security/privacy fixes:
15505 - Replace all potentially sensitive memory comparison operations
15506 with versions whose runtime does not depend on the data being
15507 compared. This will help resist a class of attacks where an
15508 adversary can use variations in timing information to learn
15509 sensitive data. Fix for one case of bug 3122. (Safe memcmp
15510 implementation by Robert Ransom based partially on code by DJB.)
15511 - When receiving a hidden service descriptor, check that it is for
15512 the hidden service we wanted. Previously, Tor would store any
15513 hidden service descriptors that a directory gave it, whether it
15514 wanted them or not. This wouldn't have let an attacker impersonate
15515 a hidden service, but it did let directories pre-seed a client
15516 with descriptors that it didn't want. Bugfix on 0.0.6.
15517 - On SIGHUP, do not clear out all TrackHostExits mappings, client
15518 DNS cache entries, and virtual address mappings: that's what
15519 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
15522 - The options SocksPort, ControlPort, and so on now all accept a
15523 value "auto" that opens a socket on an OS-selected port. A
15524 new ControlPortWriteToFile option tells Tor to write its
15525 actual control port or ports to a chosen file. If the option
15526 ControlPortFileGroupReadable is set, the file is created as
15527 group-readable. Now users can run two Tor clients on the same
15528 system without needing to manually mess with parameters. Resolves
15529 part of ticket 3076.
15530 - Set SO_REUSEADDR on all sockets, not just listeners. This should
15531 help busy exit nodes avoid running out of useable ports just
15532 because all the ports have been used in the near past. Resolves
15536 - New "GETINFO net/listeners/(type)" controller command to return
15537 a list of addresses and ports that are bound for listeners for a
15538 given connection type. This is useful when the user has configured
15539 "SocksPort auto" and the controller needs to know which port got
15540 chosen. Resolves another part of ticket 3076.
15541 - Add a new ControlSocketsGroupWritable configuration option: when
15542 it is turned on, ControlSockets are group-writeable by the default
15543 group of the current user. Patch by Jérémy Bobbio; implements
15545 - Tor now refuses to create a ControlSocket in a directory that is
15546 world-readable (or group-readable if ControlSocketsGroupWritable
15547 is 0). This is necessary because some operating systems do not
15548 enforce permissions on an AF_UNIX sockets. Permissions on the
15549 directory holding the socket, however, seems to work everywhere.
15550 - Rate-limit a warning about failures to download v2 networkstatus
15551 documents. Resolves part of bug 1352.
15552 - Backport code from 0.2.3.x that allows directory authorities to
15553 clean their microdescriptor caches. Needed to resolve bug 2230.
15554 - When an HTTPS proxy reports "403 Forbidden", we now explain
15555 what it means rather than calling it an unexpected status code.
15556 Closes bug 2503. Patch from Michael Yakubovich.
15557 - Update to the May 1 2011 Maxmind GeoLite Country database.
15560 - Authorities now clean their microdesc cache periodically and when
15561 reading from disk initially, not only when adding new descriptors.
15562 This prevents a bug where we could lose microdescriptors. Bugfix
15563 on 0.2.2.6-alpha. Fixes bug 2230.
15564 - Do not crash when our configuration file becomes unreadable, for
15565 example due to a permissions change, between when we start up
15566 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
15568 - Avoid a bug that would keep us from replacing a microdescriptor
15569 cache on Windows. (We would try to replace the file while still
15570 holding it open. That's fine on Unix, but Windows doesn't let us
15571 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
15572 - Add missing explanations for the authority-related torrc options
15573 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
15574 man page. Resolves issue 2379.
15575 - As an authority, do not upload our own vote or signature set to
15576 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
15577 it would get flagged as a duplicate. Resolves bug 3026.
15578 - Accept hidden service descriptors if we think we might be a hidden
15579 service directory, regardless of what our consensus says. This
15580 helps robustness, since clients and hidden services can sometimes
15581 have a more up-to-date view of the network consensus than we do,
15582 and if they think that the directory authorities list us a HSDir,
15583 we might actually be one. Related to bug 2732; bugfix on
15585 - When a controller changes TrackHostExits, remove mappings for
15586 hosts that should no longer have their exits tracked. Bugfix on
15588 - When a controller changes VirtualAddrNetwork, remove any mappings
15589 for hosts that were automapped to the old network. Bugfix on
15591 - When a controller changes one of the AutomapHosts* options, remove
15592 any mappings for hosts that should no longer be automapped. Bugfix
15594 - Do not reset the bridge descriptor download status every time we
15595 re-parse our configuration or get a configuration change. Fixes
15596 bug 3019; bugfix on 0.2.0.3-alpha.
15598 o Minor bugfixes (code cleanup):
15599 - When loading the microdesc journal, remember its current size.
15600 In 0.2.2, this helps prevent the microdesc journal from growing
15601 without limit on authorities (who are the only ones to use it in
15602 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
15603 Fix posted by "cypherpunks."
15604 - The microdesc journal is supposed to get rebuilt only if it is
15605 at least _half_ the length of the store, not _twice_ the length
15606 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
15607 - Fix a potential null-pointer dereference while computing a
15608 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
15610 - Avoid a possible null-pointer dereference when rebuilding the mdesc
15611 cache without actually having any descriptors to cache. Bugfix on
15612 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
15613 - If we fail to compute the identity digest of a v3 legacy keypair,
15614 warn, and don't use a buffer-full of junk instead. Bugfix on
15615 0.2.1.1-alpha; fixes bug 3106.
15616 - Resolve an untriggerable issue in smartlist_string_num_isin(),
15617 where if the function had ever in the future been used to check
15618 for the presence of a too-large number, it would have given an
15619 incorrect result. (Fortunately, we only used it for 16-bit
15620 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
15621 - Require that introduction point keys and onion handshake keys
15622 have a public exponent of 65537. Starts to fix bug 3207; bugfix
15625 o Removed features:
15626 - Caches no longer download and serve v2 networkstatus documents
15627 unless FetchV2Networkstatus flag is set: these documents haven't
15628 haven't been used by clients or relays since 0.2.0.x. Resolves
15632 Changes in version 0.2.3.1-alpha - 2011-05-05
15633 Tor 0.2.3.1-alpha adds some new experimental features, including support
15634 for an improved network IO backend, IOCP networking on Windows,
15635 microdescriptor caching, "fast-start" support for streams, and automatic
15636 home router configuration. There are also numerous internal improvements
15637 to try to make the code easier for developers to work with.
15639 This is the first alpha release in a new series, so expect there to be
15640 bugs. Users who would rather test out a more stable branch should
15641 stay with 0.2.2.x for now.
15644 - Tor can now optionally build with the "bufferevents" buffered IO
15645 backend provided by Libevent 2. To use this feature, make sure you
15646 have the latest possible version of Libevent, and pass the
15647 --enable-bufferevents flag to configure when building Tor from
15648 source. This feature will make our networking code more flexible,
15649 let us stack layers on each other, and let us use more efficient
15650 zero-copy transports where available.
15651 - As an experimental feature, Tor can use IOCP for networking on Windows.
15652 Once this code is tuned and optimized, it promises much better
15653 performance than the select-based backend we've used in the past. To
15654 try this feature, you must build Tor with Libevent 2, configure Tor
15655 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
15656 your torrc. There are known bugs here: only try this if you can help
15657 debug it as it breaks.
15658 - The EntryNodes option can now include country codes like {de} or IP
15659 addresses or network masks. Previously we had disallowed these options
15660 because we didn't have an efficient way to keep the list up to
15661 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
15662 - Exit nodes now accept and queue data on not-yet-connected streams.
15663 Previously, the client wasn't allowed to send data until the stream was
15664 connected, which slowed down all connections. This change will enable
15665 clients to perform a "fast-start" on streams and send data without
15666 having to wait for a confirmation that the stream has opened. (Patch
15667 from Ian Goldberg; implements the server side of Proposal 174.)
15668 - Tor now has initial support for automatic port mapping on the many
15669 home routers that support NAT-PMP or UPnP. (Not yet supported on
15670 Windows). To build the support code, you'll need to have libnatpnp
15671 library and/or the libminiupnpc library, and you'll need to enable the
15672 feature specifically by passing "--enable-upnp" and/or
15673 "--enable-natpnp" to configure. To turn it on, use the new
15674 PortForwarding option.
15675 - Caches now download, cache, and serve multiple "flavors" of the
15676 consensus, including a flavor that describes microdescriptors.
15677 - Caches now download, cache, and serve microdescriptors -- small
15678 summaries of router descriptors that are authenticated by all of the
15679 directory authorities. Once enough caches are running this code,
15680 clients will be able to save significant amounts of directory bandwidth
15681 by downloading microdescriptors instead of router descriptors.
15684 - Make logging resolution configurable with a new LogTimeGranularity
15685 option, and change the default from 1 millisecond to 1 second.
15686 Implements enhancement 1668.
15687 - We log which torrc file we're using on startup. Implements ticket
15689 - Ordinarily, Tor does not count traffic from private addresses (like
15690 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
15691 There is now a new option, CountPrivateBandwidth, to disable this
15692 behavior. Patch from Daniel Cagara.
15693 - New --enable-static-tor configure option for building Tor as
15694 statically as possible. Idea, general hackery and thoughts from
15695 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
15697 - If you set the NumCPUs option to 0, Tor will now try to detect how
15698 many CPUs you have. This is the new default behavior.
15699 - Turn on directory request statistics by default and include them in
15700 extra-info descriptors. Don't break if we have no GeoIP database.
15701 - Relays that set "ConnDirectionStatistics 1" write statistics on the
15702 bidirectional use of connections to disk every 24 hours.
15703 - Add a GeoIP file digest to the extra-info descriptor. Implements
15705 - The NodeFamily option -- which let you declare that you want to
15706 consider nodes to be part of a family whether they list themselves
15707 that way or not -- now allows IP address ranges and country codes.
15708 - Add a new 'Heartbeat' log message type to periodically log a message
15709 describing Tor's status at level Notice. This feature is meant for
15710 operators who log at notice, and want to make sure that their Tor
15711 server is still working. Implementation by George Kadianakis.
15713 o Minor bugfixes (on 0.2.2.25-alpha):
15714 - When loading the microdesc journal, remember its current size.
15715 In 0.2.2, this helps prevent the microdesc journal from growing
15716 without limit on authorities (who are the only ones to use it in
15717 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
15718 Fix posted by "cypherpunks."
15719 - The microdesc journal is supposed to get rebuilt only if it is
15720 at least _half_ the length of the store, not _twice_ the length
15721 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
15722 - If as an authority we fail to compute the identity digest of a v3
15723 legacy keypair, warn, and don't use a buffer-full of junk instead.
15724 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
15725 - Authorities now clean their microdesc cache periodically and when
15726 reading from disk initially, not only when adding new descriptors.
15727 This prevents a bug where we could lose microdescriptors. Bugfix
15730 o Minor features (controller):
15731 - Add a new SIGNAL event to the controller interface so that
15732 controllers can be notified when Tor handles a signal. Resolves
15733 issue 1955. Patch by John Brooks.
15734 - Add a new GETINFO option to get total bytes read and written. Patch
15735 from pipe, revised by atagar. Resolves ticket 2345.
15736 - Implement some GETINFO controller fields to provide information about
15737 the Tor process's pid, euid, username, and resource limits.
15740 - Our build system requires automake 1.6 or later to create the
15741 Makefile.in files. Previously, you could have used 1.4.
15742 This only affects developers and people building Tor from git;
15743 people who build Tor from the source distribution without changing
15744 the Makefile.am files should be fine.
15745 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
15746 so on. This is more robust against some of the failure modes
15747 associated with running the autotools pieces on their own.
15749 o Minor packaging issues:
15750 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
15751 already created. Patch from Andreas Stieger. Fixes bug 2573.
15753 o Code simplifications and refactoring:
15754 - A major revision to our internal node-selecting and listing logic.
15755 Tor already had at least two major ways to look at the question of
15756 "which Tor servers do we know about": a list of router descriptors,
15757 and a list of entries in the current consensus. With
15758 microdescriptors, we're adding a third. Having so many systems
15759 without an abstraction layer over them was hurting the codebase.
15760 Now, we have a new "node_t" abstraction that presents a consistent
15761 interface to a client's view of a Tor node, and holds (nearly) all
15762 of the mutable state formerly in routerinfo_t and routerstatus_t.
15763 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
15764 no longer link against Libevent: they never used it, but
15765 our library structure used to force them to link it.
15767 o Removed features:
15768 - Remove some old code to work around even older versions of Tor that
15769 used forked processes to handle DNS requests. Such versions of Tor
15770 are no longer in use as servers.
15772 o Documentation fixes:
15773 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
15774 - Add missing documentation for the authority-related torrc options
15775 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
15779 Changes in version 0.2.2.25-alpha - 2011-04-29
15780 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
15781 robust, routers no longer overreport their bandwidth, Win7 should crash
15782 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
15783 now prevents hidden service-related activity from being linkable. It
15784 provides more information to Vidalia so you can see if your bridge is
15785 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
15786 StrictNodes configuration options to make them more reliable, more
15787 understandable, and more regularly applied. If you use those options,
15788 please see the revised documentation for them in the manual page.
15791 - Relays were publishing grossly inflated bandwidth values because
15792 they were writing their state files wrong--now they write the
15793 correct value. Also, resume reading bandwidth history from the
15794 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
15795 - Improve hidden service robustness: When we find that we have
15796 extended a hidden service's introduction circuit to a relay not
15797 listed as an introduction point in the HS descriptor we currently
15798 have, retry with an introduction point from the current
15799 descriptor. Previously we would just give up. Fixes bugs 1024 and
15800 1930; bugfix on 0.2.0.10-alpha.
15801 - Clients now stop trying to use an exit node associated with a given
15802 destination by TrackHostExits if they fail to reach that exit node.
15803 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
15804 - Fix crash bug on platforms where gmtime and localtime can return
15805 NULL. Windows 7 users were running into this one. Fixes part of bug
15806 2077. Bugfix on all versions of Tor. Found by boboper.
15808 o Security and stability fixes:
15809 - Don't double-free a parsable, but invalid, microdescriptor, even if
15810 it is followed in the blob we're parsing by an unparsable
15811 microdescriptor. Fixes an issue reported in a comment on bug 2954.
15812 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
15813 - If the Nickname configuration option isn't given, Tor would pick a
15814 nickname based on the local hostname as the nickname for a relay.
15815 Because nicknames are not very important in today's Tor and the
15816 "Unnamed" nickname has been implemented, this is now problematic
15817 behavior: It leaks information about the hostname without being
15818 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
15819 introduced the Unnamed nickname. Reported by tagnaq.
15820 - Fix an uncommon assertion failure when running with DNSPort under
15821 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
15822 - Avoid linkability based on cached hidden service descriptors: forget
15823 all hidden service descriptors cached as a client when processing a
15824 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
15827 - Export GeoIP information on bridge usage to controllers even if we
15828 have not yet been running for 24 hours. Now Vidalia bridge operators
15829 can get more accurate and immediate feedback about their
15830 contributions to the network.
15832 o Major features and bugfixes (node selection):
15833 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
15834 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
15835 options. Previously, we had been ambiguous in describing what
15836 counted as an "exit" node, and what operations exactly "StrictNodes
15837 0" would permit. This created confusion when people saw nodes built
15838 through unexpected circuits, and made it hard to tell real bugs from
15839 surprises. Now the intended behavior is:
15840 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
15841 a node that delivers user traffic outside the Tor network.
15842 . "Entry", in the context of EntryNodes, means a node used as the
15843 first hop of a multihop circuit. It doesn't include direct
15844 connections to directory servers.
15845 . "ExcludeNodes" applies to all nodes.
15846 . "StrictNodes" changes the behavior of ExcludeNodes only. When
15847 StrictNodes is set, Tor should avoid all nodes listed in
15848 ExcludeNodes, even when it will make user requests fail. When
15849 StrictNodes is *not* set, then Tor should follow ExcludeNodes
15850 whenever it can, except when it must use an excluded node to
15851 perform self-tests, connect to a hidden service, provide a
15852 hidden service, fulfill a .exit request, upload directory
15853 information, or fetch directory information.
15854 Collectively, the changes to implement the behavior fix bug 1090.
15855 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
15856 a node is listed in both, it's treated as excluded.
15857 - ExcludeNodes now applies to directory nodes -- as a preference if
15858 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
15859 Don't exclude all the directory authorities and set StrictNodes to 1
15860 unless you really want your Tor to break.
15861 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
15862 - ExcludeExitNodes now overrides .exit requests.
15863 - We don't use bridges listed in ExcludeNodes.
15864 - When StrictNodes is 1:
15865 . We now apply ExcludeNodes to hidden service introduction points
15866 and to rendezvous points selected by hidden service users. This
15867 can make your hidden service less reliable: use it with caution!
15868 . If we have used ExcludeNodes on ourself, do not try relay
15869 reachability self-tests.
15870 . If we have excluded all the directory authorities, we will not
15871 even try to upload our descriptor if we're a relay.
15872 . Do not honor .exit requests to an excluded node.
15873 - Remove a misfeature that caused us to ignore the Fast/Stable flags
15874 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
15875 - When the set of permitted nodes changes, we now remove any mappings
15876 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
15878 - We never cannibalize a circuit that had excluded nodes on it, even
15879 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
15880 - Revert a change where we would be laxer about attaching streams to
15881 circuits than when building the circuits. This was meant to prevent
15882 a set of bugs where streams were never attachable, but our improved
15883 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
15884 - Keep track of how many times we launch a new circuit to handle a
15885 given stream. Too many launches could indicate an inconsistency
15886 between our "launch a circuit to handle this stream" logic and our
15887 "attach this stream to one of the available circuits" logic.
15888 - Improve log messages related to excluded nodes.
15891 - Fix a spurious warning when moving from a short month to a long
15892 month on relays with month-based BandwidthAccounting. Bugfix on
15893 0.2.2.17-alpha; fixes bug 3020.
15894 - When a client finds that an origin circuit has run out of 16-bit
15895 stream IDs, we now mark it as unusable for new streams. Previously,
15896 we would try to close the entire circuit. Bugfix on 0.0.6.
15897 - Add a forgotten cast that caused a compile warning on OS X 10.6.
15898 Bugfix on 0.2.2.24-alpha.
15899 - Be more careful about reporting the correct error from a failed
15900 connect() system call. Under some circumstances, it was possible to
15901 look at an incorrect value for errno when sending the end reason.
15902 Bugfix on 0.1.0.1-rc.
15903 - Correctly handle an "impossible" overflow cases in connection byte
15904 counting, where we write or read more than 4GB on an edge connection
15905 in a single second. Bugfix on 0.1.2.8-beta.
15906 - Correct the warning displayed when a rendezvous descriptor exceeds
15907 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
15909 - Clients and hidden services now use HSDir-flagged relays for hidden
15910 service descriptor downloads and uploads even if the relays have no
15911 DirPort set and the client has disabled TunnelDirConns. This will
15912 eventually allow us to give the HSDir flag to relays with no
15913 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
15914 - Downgrade "no current certificates known for authority" message from
15915 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
15916 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
15917 2917. Bugfix on 0.1.1.1-alpha.
15918 - Only limit the lengths of single HS descriptors, even when multiple
15919 HS descriptors are published to an HSDir relay in a single POST
15920 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
15921 - Write the current time into the LastWritten line in our state file,
15922 rather than the time from the previous write attempt. Also, stop
15923 trying to use a time of -1 in our log statements. Fixes bug 3039;
15924 bugfix on 0.2.2.14-alpha.
15925 - Be more consistent in our treatment of file system paths. "~" should
15926 get expanded to the user's home directory in the Log config option.
15927 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
15928 feature for the -f and --DataDirectory options.
15931 - Make sure every relay writes a state file at least every 12 hours.
15932 Previously, a relay could go for weeks without writing its state
15933 file, and on a crash could lose its bandwidth history, capacity
15934 estimates, client country statistics, and so on. Addresses bug 3012.
15935 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
15936 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
15937 clients are already deprecated because of security bugs.
15938 - Don't allow v0 hidden service authorities to act as clients.
15939 Required by fix for bug 3000.
15940 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
15941 by fix for bug 3000.
15942 - Ensure that no empty [dirreq-](read|write)-history lines are added
15943 to an extrainfo document. Implements ticket 2497.
15945 o Code simplification and refactoring:
15946 - Remove workaround code to handle directory responses from servers
15947 that had bug 539 (they would send HTTP status 503 responses _and_
15948 send a body too). Since only server versions before
15949 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
15950 keep the workaround in place.
15951 - Remove the old 'fuzzy time' logic. It was supposed to be used for
15952 handling calculations where we have a known amount of clock skew and
15953 an allowed amount of unknown skew. But we only used it in three
15954 places, and we never adjusted the known/unknown skew values. This is
15955 still something we might want to do someday, but if we do, we'll
15956 want to do it differently.
15957 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
15958 None of the cases where we did this before were wrong, but by making
15959 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
15960 - Use GetTempDir to find the proper temporary directory location on
15961 Windows when generating temporary files for the unit tests. Patch by
15965 Changes in version 0.2.2.24-alpha - 2011-04-08
15966 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
15967 prevented Tor clients from effectively using "multihomed" bridges,
15968 that is, bridges that listen on multiple ports or IP addresses so users
15969 can continue to use some of their addresses even if others get blocked.
15972 - Fix a bug where bridge users who configure the non-canonical
15973 address of a bridge automatically switch to its canonical
15974 address. If a bridge listens at more than one address, it should be
15975 able to advertise those addresses independently and any non-blocked
15976 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
15978 - If you configured Tor to use bridge A, and then quit and
15979 configured Tor to use bridge B instead, it would happily continue
15980 to use bridge A if it's still reachable. While this behavior is
15981 a feature if your goal is connectivity, in some scenarios it's a
15982 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
15983 - Directory authorities now use data collected from their own
15984 uptime observations when choosing whether to assign the HSDir flag
15985 to relays, instead of trusting the uptime value the relay reports in
15986 its descriptor. This change helps prevent an attack where a small
15987 set of nodes with frequently-changing identity keys can blackhole
15988 a hidden service. (Only authorities need upgrade; others will be
15989 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
15992 - When we restart our relay, we might get a successful connection
15993 from the outside before we've started our reachability tests,
15994 triggering a warning: "ORPort found reachable, but I have no
15995 routerinfo yet. Failing to inform controller of success." This
15996 bug was harmless unless Tor is running under a controller
15997 like Vidalia, in which case the controller would never get a
15998 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
16000 - Make directory authorities more accurate at recording when
16001 relays that have failed several reachability tests became
16002 unreachable, so we can provide more accuracy at assigning Stable,
16003 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
16004 - Fix an issue that prevented static linking of libevent on
16005 some platforms (notably Linux). Fixes bug 2698; bugfix on
16006 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
16007 the --with-static-libevent configure option).
16008 - We now ask the other side of a stream (the client or the exit)
16009 for more data on that stream when the amount of queued data on
16010 that stream dips low enough. Previously, we wouldn't ask the
16011 other side for more data until either it sent us more data (which
16012 it wasn't supposed to do if it had exhausted its window!) or we
16013 had completely flushed all our queued data. This flow control fix
16014 should improve throughput. Fixes bug 2756; bugfix on the earliest
16015 released versions of Tor (svn commit r152).
16016 - Avoid a double-mark-for-free warning when failing to attach a
16017 transparent proxy connection. (We thought we had fixed this in
16018 0.2.2.23-alpha, but it turns out our fix was checking the wrong
16019 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
16020 bug) and 0.2.2.23-alpha (the incorrect fix).
16021 - When warning about missing zlib development packages during compile,
16022 give the correct package names. Bugfix on 0.2.0.1-alpha.
16025 - Directory authorities now log the source of a rejected POSTed v3
16026 networkstatus vote.
16027 - Make compilation with clang possible when using
16028 --enable-gcc-warnings by removing two warning options that clang
16029 hasn't implemented yet and by fixing a few warnings. Implements
16031 - When expiring circuits, use microsecond timers rather than
16032 one-second timers. This can avoid an unpleasant situation where a
16033 circuit is launched near the end of one second and expired right
16034 near the beginning of the next, and prevent fluctuations in circuit
16036 - Use computed circuit-build timeouts to decide when to launch
16037 parallel introduction circuits for hidden services. (Previously,
16038 we would retry after 15 seconds.)
16039 - Update to the April 1 2011 Maxmind GeoLite Country database.
16042 - Create the /var/run/tor directory on startup on OpenSUSE if it is
16043 not already created. Patch from Andreas Stieger. Fixes bug 2573.
16045 o Documentation changes:
16046 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
16047 - Resolve all doxygen warnings except those for missing documentation.
16049 - Add doxygen documentation for more functions, fields, and types.
16052 Changes in version 0.2.2.23-alpha - 2011-03-08
16053 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
16054 they restart they don't lose their bandwidth capacity estimate. This
16055 release also fixes a diverse set of user-facing bugs, ranging from
16056 relays overrunning their rate limiting to clients falsely warning about
16057 clock skew to bridge descriptor leaks by our bridge directory authority.
16060 - Stop sending a CLOCK_SKEW controller status event whenever
16061 we fetch directory information from a relay that has a wrong clock.
16062 Instead, only inform the controller when it's a trusted authority
16063 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
16064 the rest of bug 1074.
16065 - Fix an assert in parsing router descriptors containing IPv6
16066 addresses. This one took down the directory authorities when
16067 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
16068 - Make the bridge directory authority refuse to answer directory
16069 requests for "all" descriptors. It used to include bridge
16070 descriptors in its answer, which was a major information leak.
16071 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
16072 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
16073 Tor would ignore their RelayBandwidthBurst setting,
16074 potentially using more bandwidth than expected. Bugfix on
16075 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
16076 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
16077 hidserv" in her torrc. The 'hidserv' argument never controlled
16078 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
16081 - Relays now save observed peak bandwidth throughput rates to their
16082 state file (along with total usage, which was already saved)
16083 so that they can determine their correct estimated bandwidth on
16084 restart. Resolves bug 1863, where Tor relays would reset their
16085 estimated bandwidth to 0 after restarting.
16086 - Directory authorities now take changes in router IP address and
16087 ORPort into account when determining router stability. Previously,
16088 if a router changed its IP or ORPort, the authorities would not
16089 treat it as having any downtime for the purposes of stability
16090 calculation, whereas clients would experience downtime since the
16091 change could take a while to propagate to them. Resolves issue 1035.
16092 - Enable Address Space Layout Randomization (ASLR) and Data Execution
16093 Prevention (DEP) by default on Windows to make it harder for
16094 attackers to exploit vulnerabilities. Patch from John Brooks.
16096 o Minor bugfixes (on 0.2.1.x and earlier):
16097 - Fix a rare crash bug that could occur when a client was configured
16098 with a large number of bridges. Fixes bug 2629; bugfix on
16099 0.2.1.2-alpha. Bugfix by trac user "shitlei".
16100 - Avoid a double mark-for-free warning when failing to attach a
16101 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
16103 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
16104 found by "cypherpunks". This bug was introduced before the first
16105 Tor release, in svn commit r110.
16106 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
16107 don't mention them in the manpage. Fixes bug 2450; issue
16108 spotted by keb and G-Lo.
16109 - Fix a bug in bandwidth history state parsing that could have been
16110 triggered if a future version of Tor ever changed the timing
16111 granularity at which bandwidth history is measured. Bugfix on
16112 Tor 0.1.1.11-alpha.
16113 - When a relay decides that its DNS is too broken for it to serve
16114 as an exit server, it advertised itself as a non-exit, but
16115 continued to act as an exit. This could create accidental
16116 partitioning opportunities for users. Instead, if a relay is
16117 going to advertise reject *:* as its exit policy, it should
16118 really act with exit policy "reject *:*". Fixes bug 2366.
16119 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
16120 - In the special case where you configure a public exit relay as your
16121 bridge, Tor would be willing to use that exit relay as the last
16122 hop in your circuit as well. Now we fail that circuit instead.
16123 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
16124 - Fix a bug with our locking implementation on Windows that couldn't
16125 correctly detect when a file was already locked. Fixes bug 2504,
16126 bugfix on 0.2.1.6-alpha.
16127 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
16128 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
16130 - Set target port in get_interface_address6() correctly. Bugfix
16131 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
16132 - Directory authorities are now more robust to hops back in time
16133 when calculating router stability. Previously, if a run of uptime
16134 or downtime appeared to be negative, the calculation could give
16135 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
16137 - Fix an assert that got triggered when using the TestingTorNetwork
16138 configuration option and then issuing a GETINFO config-text control
16139 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
16141 o Minor bugfixes (on 0.2.2.x):
16142 - Clients should not weight BadExit nodes as Exits in their node
16143 selection. Similarly, directory authorities should not count BadExit
16144 bandwidth as Exit bandwidth when computing bandwidth-weights.
16145 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
16146 - Correctly clear our dir_read/dir_write history when there is an
16147 error parsing any bw history value from the state file. Bugfix on
16148 Tor 0.2.2.15-alpha.
16149 - Resolve a bug in verifying signatures of directory objects
16150 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
16151 Fixes bug 2409. Found by "piebeer".
16152 - Bridge authorities no longer crash on SIGHUP when they try to
16153 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
16157 - Log less aggressively about circuit timeout changes, and improve
16158 some other circuit timeout messages. Resolves bug 2004.
16159 - Log a little more clearly about the times at which we're no longer
16160 accepting new connections. Resolves bug 2181.
16161 - Reject attempts at the client side to open connections to private
16162 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
16163 a randomly chosen exit node. Attempts to do so are always
16164 ill-defined, generally prevented by exit policies, and usually
16165 in error. This will also help to detect loops in transparent
16166 proxy configurations. You can disable this feature by setting
16167 "ClientRejectInternalAddresses 0" in your torrc.
16168 - Always treat failure to allocate an RSA key as an unrecoverable
16170 - Update to the March 1 2011 Maxmind GeoLite Country database.
16172 o Minor features (log subsystem):
16173 - Add documentation for configuring logging at different severities in
16174 different log domains. We've had this feature since 0.2.1.1-alpha,
16175 but for some reason it never made it into the manpage. Fixes
16177 - Make it simpler to specify "All log domains except for A and B".
16178 Previously you needed to say "[*,~A,~B]". Now you can just say
16180 - Add a "LogMessageDomains 1" option to include the domains of log
16181 messages along with the messages. Without this, there's no way
16182 to use log domains without reading the source or doing a lot
16185 o Packaging changes:
16186 - Stop shipping the Tor specs files and development proposal documents
16187 in the tarball. They are now in a separate git repository at
16188 git://git.torproject.org/torspec.git
16191 Changes in version 0.2.1.30 - 2011-02-23
16192 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
16193 change is a slight tweak to Tor's TLS handshake that makes relays
16194 and bridges that run this new version reachable from Iran again.
16195 We don't expect this tweak will win the arms race long-term, but it
16196 buys us time until we roll out a better solution.
16199 - Stop sending a CLOCK_SKEW controller status event whenever
16200 we fetch directory information from a relay that has a wrong clock.
16201 Instead, only inform the controller when it's a trusted authority
16202 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
16203 the rest of bug 1074.
16204 - Fix a bounds-checking error that could allow an attacker to
16205 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
16206 Found by "piebeer".
16207 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
16208 Tor would ignore their RelayBandwidthBurst setting,
16209 potentially using more bandwidth than expected. Bugfix on
16210 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
16211 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
16212 hidserv" in her torrc. The 'hidserv' argument never controlled
16213 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
16216 - Adjust our TLS Diffie-Hellman parameters to match those used by
16218 - Update to the February 1 2011 Maxmind GeoLite Country database.
16221 - Check for and reject overly long directory certificates and
16222 directory tokens before they have a chance to hit any assertions.
16223 Bugfix on 0.2.1.28. Found by "doorss".
16224 - Bring the logic that gathers routerinfos and assesses the
16225 acceptability of circuits into line. This prevents a Tor OP from
16226 getting locked in a cycle of choosing its local OR as an exit for a
16227 path (due to a .exit request) and then rejecting the circuit because
16228 its OR is not listed yet. It also prevents Tor clients from using an
16229 OR running in the same instance as an exit (due to a .exit request)
16230 if the OR does not meet the same requirements expected of an OR
16231 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
16233 o Packaging changes:
16234 - Stop shipping the Tor specs files and development proposal documents
16235 in the tarball. They are now in a separate git repository at
16236 git://git.torproject.org/torspec.git
16237 - Do not include Git version tags as though they are SVN tags when
16238 generating a tarball from inside a repository that has switched
16239 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
16242 Changes in version 0.2.2.22-alpha - 2011-01-25
16243 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
16244 main other change is a slight tweak to Tor's TLS handshake that makes
16245 relays and bridges that run this new version reachable from Iran again.
16246 We don't expect this tweak will win the arms race long-term, but it
16247 will buy us a bit more time until we roll out a better solution.
16250 - Fix a bounds-checking error that could allow an attacker to
16251 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
16252 Found by "piebeer".
16253 - Don't assert when changing from bridge to relay or vice versa
16254 via the controller. The assert happened because we didn't properly
16255 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
16256 bug 2433. Reported by bastik.
16259 - Adjust our TLS Diffie-Hellman parameters to match those used by
16261 - Provide a log message stating which geoip file we're parsing
16262 instead of just stating that we're parsing the geoip file.
16263 Implements ticket 2432.
16266 - Check for and reject overly long directory certificates and
16267 directory tokens before they have a chance to hit any assertions.
16268 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
16271 Changes in version 0.2.2.21-alpha - 2011-01-15
16272 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
16273 continues our recent code security audit work. The main fix resolves
16274 a remote heap overflow vulnerability that can allow remote code
16275 execution (CVE-2011-0427). Other fixes address a variety of assert
16276 and crash bugs, most of which we think are hard to exploit remotely.
16278 o Major bugfixes (security), also included in 0.2.1.29:
16279 - Fix a heap overflow bug where an adversary could cause heap
16280 corruption. This bug probably allows remote code execution
16281 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
16283 - Prevent a denial-of-service attack by disallowing any
16284 zlib-compressed data whose compression factor is implausibly
16285 high. Fixes part of bug 2324; reported by "doorss".
16286 - Zero out a few more keys in memory before freeing them. Fixes
16287 bug 2384 and part of bug 2385. These key instances found by
16288 "cypherpunks", based on Andrew Case's report about being able
16289 to find sensitive data in Tor's memory space if you have enough
16290 permissions. Bugfix on 0.0.2pre9.
16292 o Major bugfixes (crashes), also included in 0.2.1.29:
16293 - Prevent calls to Libevent from inside Libevent log handlers.
16294 This had potential to cause a nasty set of crashes, especially
16295 if running Libevent with debug logging enabled, and running
16296 Tor with a controller watching for low-severity log messages.
16297 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
16298 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
16299 underflow errors there too. Fixes the other part of bug 2324.
16300 - Fix a bug where we would assert if we ever had a
16301 cached-descriptors.new file (or another file read directly into
16302 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
16303 on 0.2.1.25. Found by doorss.
16304 - Fix some potential asserts and parsing issues with grossly
16305 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
16308 o Minor bugfixes (other), also included in 0.2.1.29:
16309 - Fix a bug with handling misformed replies to reverse DNS lookup
16310 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
16311 bug reported by doorss.
16312 - Fix compilation on mingw when a pthreads compatibility library
16313 has been installed. (We don't want to use it, so we shouldn't
16314 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
16315 - Fix a bug where we would declare that we had run out of virtual
16316 addresses when the address space was only half-exhausted. Bugfix
16318 - Correctly handle the case where AutomapHostsOnResolve is set but
16319 no virtual addresses are available. Fixes bug 2328; bugfix on
16320 0.1.2.1-alpha. Bug found by doorss.
16321 - Correctly handle wrapping around when we run out of virtual
16322 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
16324 o Minor features, also included in 0.2.1.29:
16325 - Update to the January 1 2011 Maxmind GeoLite Country database.
16326 - Introduce output size checks on all of our decryption functions.
16328 o Build changes, also included in 0.2.1.29:
16329 - Tor does not build packages correctly with Automake 1.6 and earlier;
16330 added a check to Makefile.am to make sure that we're building with
16331 Automake 1.7 or later.
16332 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
16333 because we built it with a too-old version of automake. Thus that
16334 release broke ./configure --enable-openbsd-malloc, which is popular
16335 among really fast exit relays on Linux.
16337 o Major bugfixes, new in 0.2.2.21-alpha:
16338 - Prevent crash/heap corruption when the cbtnummodes consensus
16339 parameter is set to 0 or large values. Fixes bug 2317; bugfix
16342 o Major features, new in 0.2.2.21-alpha:
16343 - Introduce minimum/maximum values that clients will believe
16344 from the consensus. Now we'll have a better chance to avoid crashes
16345 or worse when a consensus param has a weird value.
16347 o Minor features, new in 0.2.2.21-alpha:
16348 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
16349 used on bridges, and it makes bridge scanning somewhat easier.
16350 - If writing the state file to disk fails, wait up to an hour before
16351 retrying again, rather than trying again each second. Fixes bug
16352 2346; bugfix on Tor 0.1.1.3-alpha.
16353 - Make Libevent log messages get delivered to controllers later,
16354 and not from inside the Libevent log handler. This prevents unsafe
16355 reentrant Libevent calls while still letting the log messages
16357 - Detect platforms that brokenly use a signed size_t, and refuse to
16358 build there. Found and analyzed by doorss and rransom.
16359 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
16362 o Minor bugfixes, new in 0.2.2.21-alpha:
16363 - Handle SOCKS messages longer than 128 bytes long correctly, rather
16364 than waiting forever for them to finish. Fixes bug 2330; bugfix
16365 on 0.2.0.16-alpha. Found by doorss.
16366 - Add assertions to check for overflow in arguments to
16367 base32_encode() and base32_decode(); fix a signed-unsigned
16368 comparison there too. These bugs are not actually reachable in Tor,
16369 but it's good to prevent future errors too. Found by doorss.
16370 - Correctly detect failures to create DNS requests when using Libevent
16371 versions before v2. (Before Libevent 2, we used our own evdns
16372 implementation. Its return values for Libevent's evdns_resolve_*()
16373 functions are not consistent with those from Libevent.) Fixes bug
16374 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
16376 o Documentation, new in 0.2.2.21-alpha:
16377 - Document the default socks host and port (127.0.0.1:9050) for
16381 Changes in version 0.2.1.29 - 2011-01-15
16382 Tor 0.2.1.29 continues our recent code security audit work. The main
16383 fix resolves a remote heap overflow vulnerability that can allow remote
16384 code execution. Other fixes address a variety of assert and crash bugs,
16385 most of which we think are hard to exploit remotely.
16387 o Major bugfixes (security):
16388 - Fix a heap overflow bug where an adversary could cause heap
16389 corruption. This bug probably allows remote code execution
16390 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
16392 - Prevent a denial-of-service attack by disallowing any
16393 zlib-compressed data whose compression factor is implausibly
16394 high. Fixes part of bug 2324; reported by "doorss".
16395 - Zero out a few more keys in memory before freeing them. Fixes
16396 bug 2384 and part of bug 2385. These key instances found by
16397 "cypherpunks", based on Andrew Case's report about being able
16398 to find sensitive data in Tor's memory space if you have enough
16399 permissions. Bugfix on 0.0.2pre9.
16401 o Major bugfixes (crashes):
16402 - Prevent calls to Libevent from inside Libevent log handlers.
16403 This had potential to cause a nasty set of crashes, especially
16404 if running Libevent with debug logging enabled, and running
16405 Tor with a controller watching for low-severity log messages.
16406 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
16407 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
16408 underflow errors there too. Fixes the other part of bug 2324.
16409 - Fix a bug where we would assert if we ever had a
16410 cached-descriptors.new file (or another file read directly into
16411 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
16412 on 0.2.1.25. Found by doorss.
16413 - Fix some potential asserts and parsing issues with grossly
16414 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
16417 o Minor bugfixes (other):
16418 - Fix a bug with handling misformed replies to reverse DNS lookup
16419 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
16420 bug reported by doorss.
16421 - Fix compilation on mingw when a pthreads compatibility library
16422 has been installed. (We don't want to use it, so we shouldn't
16423 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
16424 - Fix a bug where we would declare that we had run out of virtual
16425 addresses when the address space was only half-exhausted. Bugfix
16427 - Correctly handle the case where AutomapHostsOnResolve is set but
16428 no virtual addresses are available. Fixes bug 2328; bugfix on
16429 0.1.2.1-alpha. Bug found by doorss.
16430 - Correctly handle wrapping around to when we run out of virtual
16431 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
16432 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
16433 because we built it with a too-old version of automake. Thus that
16434 release broke ./configure --enable-openbsd-malloc, which is popular
16435 among really fast exit relays on Linux.
16438 - Update to the January 1 2011 Maxmind GeoLite Country database.
16439 - Introduce output size checks on all of our decryption functions.
16442 - Tor does not build packages correctly with Automake 1.6 and earlier;
16443 added a check to Makefile.am to make sure that we're building with
16444 Automake 1.7 or later.
16447 Changes in version 0.2.2.20-alpha - 2010-12-17
16448 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
16449 exploitable bugs. We also fix a variety of other significant bugs,
16450 change the IP address for one of our directory authorities, and update
16451 the minimum version that Tor relays must run to join the network.
16454 - Fix a remotely exploitable bug that could be used to crash instances
16455 of Tor remotely by overflowing on the heap. Remote-code execution
16456 hasn't been confirmed, but can't be ruled out. Everyone should
16457 upgrade. Bugfix on the 0.1.1 series and later.
16458 - Fix a bug that could break accounting on 64-bit systems with large
16459 time_t values, making them hibernate for impossibly long intervals.
16460 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
16461 - Fix a logic error in directory_fetches_from_authorities() that
16462 would cause all _non_-exits refusing single-hop-like circuits
16463 to fetch from authorities, when we wanted to have _exits_ fetch
16464 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
16466 - Fix a stream fairness bug that would cause newer streams on a given
16467 circuit to get preference when reading bytes from the origin or
16468 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
16469 introduced before the first Tor release, in svn revision r152.
16471 o Directory authority changes:
16472 - Change IP address and ports for gabelmoo (v3 directory authority).
16475 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
16476 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
16477 - Fix an off-by-one error in calculating some controller command
16478 argument lengths. Fortunately, this mistake is harmless since
16479 the controller code does redundant NUL termination too. Found by
16480 boboper. Bugfix on 0.1.1.1-alpha.
16481 - Do not dereference NULL if a bridge fails to build its
16482 extra-info descriptor. Found by an anonymous commenter on
16483 Trac. Bugfix on 0.2.2.19-alpha.
16486 - Update to the December 1 2010 Maxmind GeoLite Country database.
16487 - Directory authorities now reject relays running any versions of
16488 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
16489 known bugs that keep RELAY_EARLY cells from working on rendezvous
16490 circuits. Followup to fix for bug 2081.
16491 - Directory authorities now reject relays running any version of Tor
16492 older than 0.2.0.26-rc. That version is the earliest that fetches
16493 current directory information correctly. Fixes bug 2156.
16494 - Report only the top 10 ports in exit-port stats in order not to
16495 exceed the maximum extra-info descriptor length of 50 KB. Implements
16499 Changes in version 0.2.1.28 - 2010-12-17
16500 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
16501 exploitable bugs. We also took this opportunity to change the IP address
16502 for one of our directory authorities, and to update the geoip database
16506 - Fix a remotely exploitable bug that could be used to crash instances
16507 of Tor remotely by overflowing on the heap. Remote-code execution
16508 hasn't been confirmed, but can't be ruled out. Everyone should
16509 upgrade. Bugfix on the 0.1.1 series and later.
16511 o Directory authority changes:
16512 - Change IP address and ports for gabelmoo (v3 directory authority).
16515 - Update to the December 1 2010 Maxmind GeoLite Country database.
16518 Changes in version 0.2.1.27 - 2010-11-23
16519 Yet another OpenSSL security patch broke its compatibility with Tor:
16520 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
16521 also took this opportunity to fix several crash bugs, integrate a new
16522 directory authority, and update the bundled GeoIP database.
16525 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
16526 No longer set the tlsext_host_name extension on server SSL objects;
16527 but continue to set it on client SSL objects. Our goal in setting
16528 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
16529 bugfix on 0.2.1.1-alpha.
16530 - Do not log messages to the controller while shrinking buffer
16531 freelists. Doing so would sometimes make the controller connection
16532 try to allocate a buffer chunk, which would mess up the internals
16533 of the freelist and cause an assertion failure. Fixes bug 1125;
16534 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
16535 - Learn our external IP address when we're a relay or bridge, even if
16536 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
16537 where we introduced bridge relays that don't need to publish to
16538 be useful. Fixes bug 2050.
16539 - Do even more to reject (and not just ignore) annotations on
16540 router descriptors received anywhere but from the cache. Previously
16541 we would ignore such annotations at first, but cache them to disk
16542 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
16543 - When you're using bridges and your network goes away and your
16544 bridges get marked as down, recover when you attempt a new socks
16545 connection (if the network is back), rather than waiting up to an
16546 hour to try fetching new descriptors for your bridges. Bugfix on
16547 0.2.0.3-alpha; fixes bug 1981.
16550 - Move to the November 2010 Maxmind GeoLite country db (rather
16551 than the June 2009 ip-to-country GeoIP db) for our statistics that
16552 count how many users relays are seeing from each country. Now we'll
16553 have more accurate data, especially for many African countries.
16555 o New directory authorities:
16556 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
16560 - Fix an assertion failure that could occur in directory caches or
16561 bridge users when using a very short voting interval on a testing
16562 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
16564 - Enforce multiplicity rules when parsing annotations. Bugfix on
16565 0.2.0.8-alpha. Found by piebeer.
16566 - Allow handshaking OR connections to take a full KeepalivePeriod
16567 seconds to handshake. Previously, we would close them after
16568 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
16569 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
16571 - When building with --enable-gcc-warnings on OpenBSD, disable
16572 warnings in system headers. This makes --enable-gcc-warnings
16573 pass on OpenBSD 4.8.
16576 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
16577 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
16578 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
16579 Servers can start sending this code when enough clients recognize
16580 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
16581 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
16582 Patch from mingw-san.
16585 - Remove the old debian/ directory from the main Tor distribution.
16586 The official Tor-for-debian git repository lives at the URL
16587 https://git.torproject.org/debian/tor.git
16588 - Stop shipping the old doc/website/ directory in the tarball. We
16589 changed the website format in late 2010, and what we shipped in
16590 0.2.1.26 really wasn't that useful anyway.
16593 Changes in version 0.2.2.19-alpha - 2010-11-22
16594 Yet another OpenSSL security patch broke its compatibility with Tor:
16595 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
16598 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
16599 No longer set the tlsext_host_name extension on server SSL objects;
16600 but continue to set it on client SSL objects. Our goal in setting
16601 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
16602 bugfix on 0.2.1.1-alpha.
16605 - Try harder not to exceed the maximum length of 50 KB when writing
16606 statistics to extra-info descriptors. This bug was triggered by very
16607 fast relays reporting exit-port, entry, and dirreq statistics.
16608 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
16609 - Publish a router descriptor even if generating an extra-info
16610 descriptor fails. Previously we would not publish a router
16611 descriptor without an extra-info descriptor; this can cause fast
16612 exit relays collecting exit-port statistics to drop from the
16613 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
16616 Changes in version 0.2.2.18-alpha - 2010-11-16
16617 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
16618 us lately, makes unpublished bridge relays able to detect their IP
16619 address, and fixes a wide variety of other bugs to get us much closer
16620 to a stable release.
16623 - Do even more to reject (and not just ignore) annotations on
16624 router descriptors received anywhere but from the cache. Previously
16625 we would ignore such annotations at first, but cache them to disk
16626 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
16627 - Do not log messages to the controller while shrinking buffer
16628 freelists. Doing so would sometimes make the controller connection
16629 try to allocate a buffer chunk, which would mess up the internals
16630 of the freelist and cause an assertion failure. Fixes bug 1125;
16631 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
16632 - Learn our external IP address when we're a relay or bridge, even if
16633 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
16634 where we introduced bridge relays that don't need to publish to
16635 be useful. Fixes bug 2050.
16636 - Maintain separate TLS contexts and certificates for incoming and
16637 outgoing connections in bridge relays. Previously we would use the
16638 same TLS contexts and certs for incoming and outgoing connections.
16639 Bugfix on 0.2.0.3-alpha; addresses bug 988.
16640 - Maintain separate identity keys for incoming and outgoing TLS
16641 contexts in bridge relays. Previously we would use the same
16642 identity keys for incoming and outgoing TLS contexts. Bugfix on
16643 0.2.0.3-alpha; addresses the other half of bug 988.
16644 - Avoid an assertion failure when we as an authority receive a
16645 duplicate upload of a router descriptor that we already have,
16646 but which we previously considered an obsolete descriptor.
16647 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
16648 - Avoid a crash bug triggered by looking at a dangling pointer while
16649 setting the network status consensus. Found by Robert Ransom.
16650 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
16651 - Fix a logic error where servers that _didn't_ act as exits would
16652 try to keep their server lists more aggressively up to date than
16653 exits, when it was supposed to be the other way around. Bugfix
16656 o Minor bugfixes (on Tor 0.2.1.x and earlier):
16657 - When we're trying to guess whether we know our IP address as
16658 a relay, we would log various ways that we failed to guess
16659 our address, but never log that we ended up guessing it
16660 successfully. Now add a log line to help confused and anxious
16661 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
16662 - Bring the logic that gathers routerinfos and assesses the
16663 acceptability of circuits into line. This prevents a Tor OP from
16664 getting locked in a cycle of choosing its local OR as an exit for a
16665 path (due to a .exit request) and then rejecting the circuit because
16666 its OR is not listed yet. It also prevents Tor clients from using an
16667 OR running in the same instance as an exit (due to a .exit request)
16668 if the OR does not meet the same requirements expected of an OR
16669 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
16670 - Correctly describe errors that occur when generating a TLS object.
16671 Previously we would attribute them to a failure while generating a
16672 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
16674 - Enforce multiplicity rules when parsing annotations. Bugfix on
16675 0.2.0.8-alpha. Found by piebeer.
16676 - Fix warnings that newer versions of autoconf produced during
16677 ./autogen.sh. These warnings appear to be harmless in our case,
16678 but they were extremely verbose. Fixes bug 2020.
16680 o Minor bugfixes (on Tor 0.2.2.x):
16681 - Enable protection of small arrays whenever we build with gcc
16682 hardening features, not only when also building with warnings
16683 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
16686 - Make hidden services work better in private Tor networks by not
16687 requiring any uptime to join the hidden service descriptor
16688 DHT. Implements ticket 2088.
16689 - Rate-limit the "your application is giving Tor only an IP address"
16690 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
16691 - When AllowSingleHopExits is set, print a warning to explain to the
16692 relay operator why most clients are avoiding her relay.
16693 - Update to the November 1 2010 Maxmind GeoLite Country database.
16695 o Code simplifications and refactoring:
16696 - When we fixed bug 1038 we had to put in a restriction not to send
16697 RELAY_EARLY cells on rend circuits. This was necessary as long
16698 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
16699 active. Now remove this obsolete check. Resolves bug 2081.
16700 - Some options used different conventions for uppercasing of acronyms
16701 when comparing manpage and source. Fix those in favor of the
16702 manpage, as it makes sense to capitalize acronyms.
16703 - Remove the torrc.complete file. It hasn't been kept up to date
16704 and users will have better luck checking out the manpage.
16705 - Remove the obsolete "NoPublish" option; it has been flagged
16706 as obsolete and has produced a warning since 0.1.1.18-rc.
16707 - Remove everything related to building the expert bundle for OS X.
16708 It has confused many users, doesn't work right on OS X 10.6,
16709 and is hard to get rid of once installed. Resolves bug 1274.
16712 Changes in version 0.2.2.17-alpha - 2010-09-30
16713 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
16714 to use one-hop circuits (which can put the exit relays at higher risk,
16715 plus unbalance the network); fixes a big bug in bandwidth accounting
16716 for relays that want to limit their monthly bandwidth use; fixes a
16717 big pile of bugs in how clients tolerate temporary network failure;
16718 and makes our adaptive circuit build timeout feature (which improves
16719 client performance if your network is fast while not breaking things
16720 if your network is slow) better handle bad networks.
16723 - Exit relays now try harder to block exit attempts from unknown
16724 relays, to make it harder for people to use them as one-hop proxies
16725 a la tortunnel. Controlled by the refuseunknownexits consensus
16726 parameter (currently enabled), or you can override it on your
16727 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
16729 o Major bugfixes (0.2.1.x and earlier):
16730 - Fix a bug in bandwidth accounting that could make us use twice
16731 the intended bandwidth when our interval start changes due to
16732 daylight saving time. Now we tolerate skew in stored vs computed
16733 interval starts: if the start of the period changes by no more than
16734 50% of the period's duration, we remember bytes that we transferred
16735 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
16736 - Always search the Windows system directory for system DLLs, and
16737 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
16738 - When you're using bridges and your network goes away and your
16739 bridges get marked as down, recover when you attempt a new socks
16740 connection (if the network is back), rather than waiting up to an
16741 hour to try fetching new descriptors for your bridges. Bugfix on
16742 0.2.0.3-alpha; fixes bug 1981.
16744 o Major bugfixes (on 0.2.2.x):
16745 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
16747 - Fix a segfault that could happen when operating a bridge relay with
16748 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
16749 - The consensus bandwidth-weights (used by clients to choose fast
16750 relays) entered an unexpected edge case in September where
16751 Exits were much scarcer than Guards, resulting in bad weight
16752 recommendations. Now we compute them using new constraints that
16753 should succeed in all cases. Also alter directory authorities to
16754 not include the bandwidth-weights line if they fail to produce
16755 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
16756 - When weighting bridges during path selection, we used to trust
16757 the bandwidths they provided in their descriptor, only capping them
16758 at 10MB/s. This turned out to be problematic for two reasons:
16759 Bridges could claim to handle a lot more traffic then they
16760 actually would, thus making more clients pick them and have a
16761 pretty effective DoS attack. The other issue is that new bridges
16762 that might not have a good estimate for their bw capacity yet
16763 would not get used at all unless no other bridges are available
16764 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
16766 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
16767 - Ignore cannibalized circuits when recording circuit build times.
16768 This should provide for a minor performance improvement for hidden
16769 service users using 0.2.2.14-alpha, and should remove two spurious
16770 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
16771 - Simplify the logic that causes us to decide if the network is
16772 unavailable for purposes of recording circuit build times. If we
16773 receive no cells whatsoever for the entire duration of a circuit's
16774 full measured lifetime, the network is probably down. Also ignore
16775 one-hop directory fetching circuit timeouts when calculating our
16776 circuit build times. These changes should hopefully reduce the
16777 cases where we see ridiculous circuit build timeouts for people
16778 with spotty wireless connections. Fixes part of bug 1772; bugfix
16780 - Prevent the circuit build timeout from becoming larger than
16781 the maximum build time we have ever seen. Also, prevent the time
16782 period for measurement circuits from becoming larger than twice that
16783 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
16786 - When we run out of directory information such that we can't build
16787 circuits, but then get enough that we can build circuits, log when
16788 we actually construct a circuit, so the user has a better chance of
16789 knowing what's going on. Fixes bug 1362.
16790 - Be more generous with how much bandwidth we'd use up (with
16791 accounting enabled) before entering "soft hibernation". Previously,
16792 we'd refuse new connections and circuits once we'd used up 95% of
16793 our allotment. Now, we use up 95% of our allotment, AND make sure
16794 that we have no more than 500MB (or 3 hours of expected traffic,
16795 whichever is lower) remaining before we enter soft hibernation.
16796 - If we've configured EntryNodes and our network goes away and/or all
16797 our entrynodes get marked down, optimistically retry them all when
16798 a new socks application request appears. Fixes bug 1882.
16799 - Add some more defensive programming for architectures that can't
16800 handle unaligned integer accesses. We don't know of any actual bugs
16801 right now, but that's the best time to fix them. Fixes bug 1943.
16802 - Support line continuations in the torrc config file. If a line
16803 ends with a single backslash character, the newline is ignored, and
16804 the configuration value is treated as continuing on the next line.
16807 o Minor bugfixes (on 0.2.1.x and earlier):
16808 - For bandwidth accounting, calculate our expected bandwidth rate
16809 based on the time during which we were active and not in
16810 soft-hibernation during the last interval. Previously, we were
16811 also considering the time spent in soft-hibernation. If this
16812 was a long time, we would wind up underestimating our bandwidth
16813 by a lot, and skewing our wakeup time towards the start of the
16814 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
16816 o Minor bugfixes (on 0.2.2.x):
16817 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
16818 which were disabled by the circuit build timeout changes in
16819 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
16820 - Make sure we don't warn about missing bandwidth weights when
16821 choosing bridges or other relays not in the consensus. Bugfix on
16822 0.2.2.10-alpha; fixes bug 1805.
16823 - In our logs, do not double-report signatures from unrecognized
16824 authorities both as "from unknown authority" and "not
16825 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
16828 Changes in version 0.2.2.16-alpha - 2010-09-17
16829 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
16830 evident at exit relays), and also continues to resolve all the little
16831 bugs that have been filling up trac lately.
16833 o Major bugfixes (stream-level fairness):
16834 - When receiving a circuit-level SENDME for a blocked circuit, try
16835 to package cells fairly from all the streams that had previously
16836 been blocked on that circuit. Previously, we had started with the
16837 oldest stream, and allowed each stream to potentially exhaust
16838 the circuit's package window. This gave older streams on any
16839 given circuit priority over newer ones. Fixes bug 1937. Detected
16840 originally by Camilo Viecco. This bug was introduced before the
16841 first Tor release, in svn commit r152: it is the new winner of
16842 the longest-lived bug prize.
16843 - When the exit relay got a circuit-level sendme cell, it started
16844 reading on the exit streams, even if had 500 cells queued in the
16845 circuit queue already, so the circuit queue just grew and grew in
16846 some cases. We fix this by not re-enabling reading on receipt of a
16847 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
16848 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
16850 - Newly created streams were allowed to read cells onto circuits,
16851 even if the circuit's cell queue was blocked and waiting to drain.
16852 This created potential unfairness, as older streams would be
16853 blocked, but newer streams would gladly fill the queue completely.
16854 We add code to detect this situation and prevent any stream from
16855 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
16859 - Update to the September 1 2010 Maxmind GeoLite Country database.
16860 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
16861 not. This would lead to a cookie that is still not group readable.
16862 Closes bug 1843. Suggested by katmagic.
16863 - When logging a rate-limited warning, we now mention how many messages
16864 got suppressed since the last warning.
16865 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
16866 do individual connection-level rate limiting of clients. The torrc
16867 config options with the same names trump the consensus params, if
16868 both are present. Replaces the old "bwconnrate" and "bwconnburst"
16869 consensus params which were broken from 0.2.2.7-alpha through
16870 0.2.2.14-alpha. Closes bug 1947.
16871 - When a router changes IP address or port, authorities now launch
16872 a new reachability test for it. Implements ticket 1899.
16873 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
16874 2 no signature, 4 required" messages about consensus signatures
16875 easier to read, and make sure they get logged at the same severity
16876 as the messages explaining which keys are which. Fixes bug 1290.
16877 - Don't warn when we have a consensus that we can't verify because
16878 of missing certificates, unless those certificates are ones
16879 that we have been trying and failing to download. Fixes bug 1145.
16880 - If you configure your bridge with a known identity fingerprint,
16881 and the bridge authority is unreachable (as it is in at least
16882 one country now), fall back to directly requesting the descriptor
16883 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
16885 - When building with --enable-gcc-warnings on OpenBSD, disable
16886 warnings in system headers. This makes --enable-gcc-warnings
16887 pass on OpenBSD 4.8.
16889 o Minor bugfixes (on 0.2.1.x and earlier):
16890 - Authorities will now attempt to download consensuses if their
16891 own efforts to make a live consensus have failed. This change
16892 means authorities that restart will fetch a valid consensus, and
16893 it means authorities that didn't agree with the current consensus
16894 will still fetch and serve it if it has enough signatures. Bugfix
16895 on 0.2.0.9-alpha; fixes bug 1300.
16896 - Ensure DNS requests launched by "RESOLVE" commands from the
16897 controller respect the __LeaveStreamsUnattached setconf options. The
16898 same goes for requests launched via DNSPort or transparent
16899 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
16900 - Allow handshaking OR connections to take a full KeepalivePeriod
16901 seconds to handshake. Previously, we would close them after
16902 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
16903 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
16905 - Rate-limit "Failed to hand off onionskin" warnings.
16906 - Never relay a cell for a circuit we have already destroyed.
16907 Between marking a circuit as closeable and finally closing it,
16908 it may have been possible for a few queued cells to get relayed,
16909 even though they would have been immediately dropped by the next
16910 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
16911 - Never queue a cell for a circuit that's already been marked
16913 - Never vote for a server as "Running" if we have a descriptor for
16914 it claiming to be hibernating, and that descriptor was published
16915 more recently than our last contact with the server. Bugfix on
16916 0.2.0.3-alpha; fixes bug 911.
16917 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
16920 o Minor bugfixes (on 0.2.2.x):
16921 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
16922 down if a directory fetch fails and you've configured either
16923 bridges or EntryNodes. The intent was to mark the relay as down
16924 _unless_ you're using bridges or EntryNodes, since if you are
16925 then you could quickly run out of entry points.
16926 - Fix the Windows directory-listing code. A bug introduced in
16927 0.2.2.14-alpha could make Windows directory servers forget to load
16928 some of their cached v2 networkstatus files.
16929 - Really allow clients to use relays as bridges. Fixes bug 1776;
16930 bugfix on 0.2.2.15-alpha.
16931 - Demote a warn to info that happens when the CellStatistics option
16932 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
16933 Reported by Moritz Bartl.
16934 - On Windows, build correctly either with or without Unicode support.
16935 This is necessary so that Tor can support fringe platforms like
16936 Windows 98 (which has no Unicode), or Windows CE (which has no
16937 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
16940 - Add a unit test for cross-platform directory-listing code.
16943 Changes in version 0.2.2.15-alpha - 2010-08-18
16944 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
16945 fixes a variety of other bugs that were preventing performance
16946 experiments from moving forward, fixes several bothersome memory leaks,
16947 and generally closes a lot of smaller bugs that have been filling up
16951 - Stop assigning the HSDir flag to relays that disable their
16952 DirPort (and thus will refuse to answer directory requests). This
16953 fix should dramatically improve the reachability of hidden services:
16954 hidden services and hidden service clients pick six HSDir relays
16955 to store and retrieve the hidden service descriptor, and currently
16956 about half of the HSDir relays will refuse to work. Bugfix on
16957 0.2.0.10-alpha; fixes part of bug 1693.
16958 - The PerConnBWRate and Burst config options, along with the
16959 bwconnrate and bwconnburst consensus params, initialized each conn's
16960 token bucket values only when the connection is established. Now we
16961 update them if the config options change, and update them every time
16962 we get a new consensus. Otherwise we can encounter an ugly edge
16963 case where we initialize an OR conn to client-level bandwidth,
16964 but then later the relay joins the consensus and we leave it
16965 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
16966 - Fix a regression that caused Tor to rebind its ports if it receives
16967 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
16970 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
16971 should give us approximately 40-50% more Guard-flagged nodes,
16972 improving the anonymity the Tor network can provide and also
16973 decreasing the dropoff in throughput that relays experience when
16974 they first get the Guard flag.
16975 - Allow enabling or disabling the *Statistics config options while
16979 - Update to the August 1 2010 Maxmind GeoLite Country database.
16980 - Have the controller interface give a more useful message than
16981 "Internal Error" in response to failed GETINFO requests.
16982 - Warn when the same option is provided more than once in a torrc
16983 file, on the command line, or in a single SETCONF statement, and
16984 the option is one that only accepts a single line. Closes bug 1384.
16985 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
16986 Patch from mingw-san.
16987 - Add support for the country code "{??}" in torrc options like
16988 ExcludeNodes, to indicate all routers of unknown country. Closes
16990 - Relays report the number of bytes spent on answering directory
16991 requests in extra-info descriptors similar to {read,write}-history.
16992 Implements enhancement 1790.
16994 o Minor bugfixes (on 0.2.1.x and earlier):
16995 - Complain if PublishServerDescriptor is given multiple arguments that
16996 include 0 or 1. This configuration will be rejected in the future.
16997 Bugfix on 0.2.0.1-alpha; closes bug 1107.
16998 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
16999 Bugfix on 0.2.0.13-alpha; closes bug 928.
17000 - Change "Application request when we're believed to be offline."
17001 notice to "Application request when we haven't used client
17002 functionality lately.", to clarify that it's not an error. Bugfix
17003 on 0.0.9.3; fixes bug 1222.
17004 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
17005 would return "551 Internal error" rather than "552 Unrecognized key
17006 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
17007 - Users can't configure a regular relay to be their bridge. It didn't
17008 work because when Tor fetched the bridge descriptor, it found
17009 that it already had it, and didn't realize that the purpose of the
17010 descriptor had changed. Now we replace routers with a purpose other
17011 than bridge with bridge descriptors when fetching them. Bugfix on
17012 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
17013 refetch the descriptor with router purpose 'general', disabling
17015 - Fix a rare bug in rend_fn unit tests: we would fail a test when
17016 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
17017 on 0.2.0.10-alpha; fixes bug 1808.
17018 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
17019 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
17020 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
17021 Servers can start sending this code when enough clients recognize
17022 it. Also update the spec to reflect this new reason. Bugfix on
17023 0.1.0.1-rc; fixes part of bug 1793.
17024 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
17025 when we switch from being a public relay to a bridge. Otherwise
17026 there will still be clients that see the relay in their consensus,
17027 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
17029 - Instead of giving an assertion failure on an internal mismatch
17030 on estimated freelist size, just log a BUG warning and try later.
17031 Mitigates but does not fix bug 1125.
17032 - Fix an assertion failure that could occur in caches or bridge users
17033 when using a very short voting interval on a testing network.
17034 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
17036 o Minor bugfixes (on 0.2.2.x):
17037 - Alter directory authorities to always consider Exit-flagged nodes
17038 as potential Guard nodes in their votes. The actual decision to
17039 use Exits as Guards is done in the consensus bandwidth weights.
17040 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
17041 - When the controller is reporting the purpose of circuits that
17042 didn't finish building before the circuit build timeout, it was
17043 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
17044 - Our libevent version parsing code couldn't handle versions like
17045 1.4.14b-stable and incorrectly warned the user about using an
17046 old and broken version of libevent. Treat 1.4.14b-stable like
17047 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
17049 - Don't use substitution references like $(VAR:MOD) when
17050 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
17051 '$(:x)' to 'x' rather than the empty string. This bites us in
17052 doc/ when configured with --disable-asciidoc. Bugfix on
17053 0.2.2.9-alpha; fixes bug 1773.
17054 - Remove a spurious hidden service server-side log notice about
17055 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
17057 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
17059 - Correctly report written bytes on linked connections. Found while
17060 implementing 1790. Bugfix on 0.2.2.4-alpha.
17061 - Fix three memory leaks: one in circuit_build_times_parse_state(),
17062 one in dirvote_add_signatures_to_pending_consensus(), and one every
17063 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
17064 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
17066 o Code simplifications and refactoring:
17067 - Take a first step towards making or.h smaller by splitting out
17068 function definitions for all source files in src/or/. Leave
17069 structures and defines in or.h for now.
17070 - Remove a bunch of unused function declarations as well as a block of
17071 #if 0'd code from the unit tests. Closes bug 1824.
17072 - New unit tests for exit-port history statistics; refactored exit
17073 statistics code to be more easily tested.
17074 - Remove the old debian/ directory from the main Tor distribution.
17075 The official Tor-for-debian git repository lives at the URL
17076 https://git.torproject.org/debian/tor.git
17079 Changes in version 0.2.2.14-alpha - 2010-07-12
17080 Tor 0.2.2.14-alpha greatly improves client-side handling of
17081 circuit build timeouts, which are used to estimate speed and improve
17082 performance. We also move to a much better GeoIP database, port Tor to
17083 Windows CE, introduce new compile flags that improve code security,
17084 add an eighth v3 directory authority, and address a lot of more
17088 - Tor directory authorities no longer crash when started with a
17089 cached-microdesc-consensus file in their data directory. Bugfix
17090 on 0.2.2.6-alpha; fixes bug 1532.
17091 - Treat an unset $HOME like an empty $HOME rather than triggering an
17092 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
17093 - Ignore negative and large circuit build timeout values that can
17094 happen during a suspend or hibernate. These values caused various
17095 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
17096 - Alter calculation of Pareto distribution parameter 'Xm' for
17097 Circuit Build Timeout learning to use the weighted average of the
17098 top N=3 modes (because we have three entry guards). Considering
17099 multiple modes should improve the timeout calculation in some cases,
17100 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
17102 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
17103 right censored distribution model. This approach improves over the
17104 synthetic timeout generation approach that was producing insanely
17105 high timeout values. Now we calculate build timeouts using truncated
17106 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
17107 - Do not close circuits that are under construction when they reach
17108 the circuit build timeout. Instead, leave them building (but do not
17109 use them) for up until the time corresponding to the 95th percentile
17110 on the Pareto CDF or 60 seconds, whichever is greater. This is done
17111 to provide better data for the new Pareto model. This percentile
17112 can be controlled by the consensus.
17115 - Move to the June 2010 Maxmind GeoLite country db (rather than the
17116 June 2009 ip-to-country GeoIP db) for our statistics that count
17117 how many users relays are seeing from each country. Now we have
17118 more accurate data for many African countries.
17119 - Port Tor to build and run correctly on Windows CE systems, using
17120 the wcecompat library. Contributed by Valerio Lupi.
17121 - New "--enable-gcc-hardening" ./configure flag (off by default)
17122 to turn on gcc compile time hardening options. It ensures
17123 that signed ints have defined behavior (-fwrapv), enables
17124 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
17125 with canaries (-fstack-protector-all), turns on ASLR protection if
17126 supported by the kernel (-fPIE, -pie), and adds additional security
17127 related warnings. Verified to work on Mac OS X and Debian Lenny.
17128 - New "--enable-linker-hardening" ./configure flag (off by default)
17129 to turn on ELF specific hardening features (relro, now). This does
17130 not work with Mac OS X or any other non-ELF binary format.
17132 o New directory authorities:
17133 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
17137 - New config option "WarnUnsafeSocks 0" disables the warning that
17138 occurs whenever Tor receives a socks handshake using a version of
17139 the socks protocol that can only provide an IP address (rather
17140 than a hostname). Setups that do DNS locally over Tor are fine,
17141 and we shouldn't spam the logs in that case.
17142 - Convert the HACKING file to asciidoc, and add a few new sections
17143 to it, explaining how we use Git, how we make changelogs, and
17144 what should go in a patch.
17145 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
17146 event, to give information on the current rate of circuit timeouts
17147 over our stored history.
17148 - Add ability to disable circuit build time learning via consensus
17149 parameter and via a LearnCircuitBuildTimeout config option. Also
17150 automatically disable circuit build time calculation if we are
17151 either a AuthoritativeDirectory, or if we fail to write our state
17152 file. Fixes bug 1296.
17153 - More gracefully handle corrupt state files, removing asserts
17154 in favor of saving a backup and resetting state.
17155 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
17159 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
17161 - When a2x fails, mention that the user could disable manpages instead
17162 of trying to fix their asciidoc installation.
17163 - Where available, use Libevent 2.0's periodic timers so that our
17164 once-per-second cleanup code gets called even more closely to
17165 once per second than it would otherwise. Fixes bug 943.
17166 - If you run a bridge that listens on multiple IP addresses, and
17167 some user configures a bridge address that uses a different IP
17168 address than your bridge writes in its router descriptor, and the
17169 user doesn't specify an identity key, their Tor would discard the
17170 descriptor because "it isn't one of our configured bridges", and
17171 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
17172 Bugfix on 0.2.0.3-alpha.
17173 - If OpenSSL fails to make a duplicate of a private or public key, log
17174 an error message and try to exit cleanly. May help with debugging
17175 if bug 1209 ever remanifests.
17176 - Save a couple bytes in memory allocation every time we escape
17177 certain characters in a string. Patch from Florian Zumbiehl.
17178 - Make it explicit that we don't cannibalize one-hop circuits. This
17179 happens in the wild, but doesn't turn out to be a problem because
17180 we fortunately don't use those circuits. Many thanks to outofwords
17181 for the initial analysis and to swissknife who confirmed that
17182 two-hop circuits are actually created.
17183 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
17184 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
17185 - Eliminate a case where a circuit build time warning was displayed
17186 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
17189 Changes in version 0.2.1.26 - 2010-05-02
17190 Tor 0.2.1.26 addresses the recent connection and memory overload
17191 problems we've been seeing on relays, especially relays with their
17192 DirPort open. If your relay has been crashing, or you turned it off
17193 because it used too many resources, give this release a try.
17195 This release also fixes yet another instance of broken OpenSSL libraries
17196 that was causing some relays to drop out of the consensus.
17199 - Teach relays to defend themselves from connection overload. Relays
17200 now close idle circuits early if it looks like they were intended
17201 for directory fetches. Relays are also more aggressive about closing
17202 TLS connections that have no circuits on them. Such circuits are
17203 unlikely to be re-used, and tens of thousands of them were piling
17204 up at the fast relays, causing the relays to run out of sockets
17205 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
17206 their directory fetches over TLS).
17207 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
17208 that claim to be earlier than 0.9.8m, but which have in reality
17209 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
17210 behavior. Possible fix for some cases of bug 1346.
17211 - Directory mirrors were fetching relay descriptors only from v2
17212 directory authorities, rather than v3 authorities like they should.
17213 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
17214 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
17217 - Finally get rid of the deprecated and now harmful notion of "clique
17218 mode", where directory authorities maintain TLS connections to
17222 - In the util/threads test, no longer free the test_mutex before all
17223 worker threads have finished. Bugfix on 0.2.1.6-alpha.
17224 - The master thread could starve the worker threads quite badly on
17225 certain systems, causing them to run only partially in the allowed
17226 window. This resulted in test failures. Now the master thread sleeps
17227 occasionally for a few microseconds while the two worker-threads
17228 compete for the mutex. Bugfix on 0.2.0.1-alpha.
17231 Changes in version 0.2.2.13-alpha - 2010-04-24
17232 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
17233 problems we've been seeing on relays, especially relays with their
17234 DirPort open. If your relay has been crashing, or you turned it off
17235 because it used too many resources, give this release a try.
17238 - Teach relays to defend themselves from connection overload. Relays
17239 now close idle circuits early if it looks like they were intended
17240 for directory fetches. Relays are also more aggressive about closing
17241 TLS connections that have no circuits on them. Such circuits are
17242 unlikely to be re-used, and tens of thousands of them were piling
17243 up at the fast relays, causing the relays to run out of sockets
17244 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
17245 their directory fetches over TLS).
17248 - Finally get rid of the deprecated and now harmful notion of "clique
17249 mode", where directory authorities maintain TLS connections to
17251 - Directory authorities now do an immediate reachability check as soon
17252 as they hear about a new relay. This change should slightly reduce
17253 the time between setting up a relay and getting listed as running
17254 in the consensus. It should also improve the time between setting
17255 up a bridge and seeing use by bridge users.
17256 - Directory authorities no longer launch a TLS connection to every
17257 relay as they startup. Now that we have 2k+ descriptors cached,
17258 the resulting network hiccup is becoming a burden. Besides,
17259 authorities already avoid voting about Running for the first half
17260 hour of their uptime.
17263 Changes in version 0.2.2.12-alpha - 2010-04-20
17264 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
17265 handle and vote on descriptors. It was causing relays to drop out of
17269 - Many relays have been falling out of the consensus lately because
17270 not enough authorities know about their descriptor for them to get
17271 a majority of votes. When we deprecated the v2 directory protocol,
17272 we got rid of the only way that v3 authorities can hear from each
17273 other about other descriptors. Now authorities examine every v3
17274 vote for new descriptors, and fetch them from that authority. Bugfix
17276 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
17277 and a warning in or.h related to bandwidth_weight_rule_t that
17278 prevented clean compile on OS X. Fixes bug 1363; bugfix on
17280 - Fix a segfault on relays when DirReqStatistics is enabled
17281 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
17285 - Demote a confusing TLS warning that relay operators might get when
17286 someone tries to talk to their OrPort. It is neither the operator's
17287 fault nor can they do anything about it. Fixes bug 1364; bugfix
17291 Changes in version 0.2.2.11-alpha - 2010-04-15
17292 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
17293 libraries that was causing some relays to drop out of the consensus.
17296 - Directory mirrors were fetching relay descriptors only from v2
17297 directory authorities, rather than v3 authorities like they should.
17298 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
17299 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
17300 - Fix a parsing error that made every possible value of
17301 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
17302 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
17303 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
17304 about the option without breaking older ones.
17305 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
17306 that claim to be earlier than 0.9.8m, but which have in reality
17307 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
17308 behavior. Possible fix for some cases of bug 1346.
17311 - Experiment with a more aggressive approach to preventing clients
17312 from making one-hop exit streams. Exit relays who want to try it
17313 out can set "RefuseUnknownExits 1" in their torrc, and then look
17314 for "Attempt by %s to open a stream" log messages. Let us know
17316 - Add support for statically linking zlib by specifying
17317 --enable-static-zlib, to go with our support for statically linking
17318 openssl and libevent. Resolves bug 1358.
17321 - Fix a segfault that happens whenever a Tor client that is using
17322 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
17324 - When we cleaned up the contrib/tor-exit-notice.html file, we left
17325 out the first line. Fixes bug 1295.
17326 - When building the manpage from a tarball, we required asciidoc, but
17327 the asciidoc -> roff/html conversion was already done for the
17328 tarball. Make 'make' complain only when we need asciidoc (either
17329 because we're compiling directly from git, or because we altered
17330 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
17331 - When none of the directory authorities vote on any params, Tor
17332 segfaulted when trying to make the consensus from the votes. We
17333 didn't trigger the bug in practice, because authorities do include
17334 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
17337 - In the util/threads test, no longer free the test_mutex before all
17338 worker threads have finished. Bugfix on 0.2.1.6-alpha.
17339 - The master thread could starve the worker threads quite badly on
17340 certain systems, causing them to run only partially in the allowed
17341 window. This resulted in test failures. Now the master thread sleeps
17342 occasionally for a few microseconds while the two worker-threads
17343 compete for the mutex. Bugfix on 0.2.0.1-alpha.
17346 Changes in version 0.2.2.10-alpha - 2010-03-07
17347 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
17348 could prevent relays from guessing their IP address correctly. It also
17349 starts the groundwork for another client-side performance boost, since
17350 currently we're not making efficient use of relays that have both the
17351 Guard flag and the Exit flag.
17354 - Fix a regression from our patch for bug 1244 that caused relays
17355 to guess their IP address incorrectly if they didn't set Address
17356 in their torrc and/or their address fails to resolve. Bugfix on
17357 0.2.2.9-alpha; fixes bug 1269.
17359 o Major features (performance):
17360 - Directory authorities now compute consensus weightings that instruct
17361 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
17362 and no flag. Clients that use these weightings will distribute
17363 network load more evenly across these different relay types. The
17364 weightings are in the consensus so we can change them globally in
17365 the future. Extra thanks to "outofwords" for finding some nasty
17366 security bugs in the first implementation of this feature.
17368 o Minor features (performance):
17369 - Always perform router selections using weighted relay bandwidth,
17370 even if we don't need a high capacity circuit at the time. Non-fast
17371 circuits now only differ from fast ones in that they can use relays
17372 not marked with the Fast flag. This "feature" could turn out to
17373 be a horrible bug; we should investigate more before it goes into
17377 - Allow disabling building of the manpages. Skipping the manpage
17378 speeds up the build considerably.
17380 o Minor bugfixes (on 0.2.2.x):
17381 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
17382 Bugfix on 0.2.2.9-alpha.
17383 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
17384 config option. Bugfix on 0.2.2.7-alpha.
17385 - Ship the asciidoc-helper file in the tarball, so that people can
17386 build from source if they want to, and touching the .1.txt files
17387 doesn't break the build. Bugfix on 0.2.2.9-alpha.
17389 o Minor bugfixes (on 0.2.1.x or earlier):
17390 - Fix a dereference-then-NULL-check sequence when publishing
17391 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
17393 - Fix another dereference-then-NULL-check sequence. Bugfix on
17394 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
17395 - Make sure we treat potentially not NUL-terminated strings correctly.
17396 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
17398 o Code simplifications and refactoring:
17399 - Fix some urls in the exit notice file and make it XHTML1.1 strict
17400 compliant. Based on a patch from Christian Kujau.
17401 - Don't use sed in asciidoc-helper anymore.
17402 - Make the build process fail if asciidoc cannot be found and
17403 building with asciidoc isn't disabled.
17406 Changes in version 0.2.2.9-alpha - 2010-02-22
17407 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
17408 location of a directory authority, and cleans up a bunch of small bugs.
17410 o Directory authority changes:
17411 - Change IP address for dannenberg (v3 directory authority), and
17412 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
17413 service directory authority) from the list.
17416 - Make Tor work again on the latest OS X: when deciding whether to
17417 use strange flags to turn TLS renegotiation on, detect the OpenSSL
17418 version at run-time, not compile time. We need to do this because
17419 Apple doesn't update its dev-tools headers when it updates its
17420 libraries in a security patch.
17421 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
17422 that could happen on 32-bit platforms with 64-bit time_t. Also fix
17423 a memory leak when requesting a hidden service descriptor we've
17424 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
17426 - Authorities could be tricked into giving out the Exit flag to relays
17427 that didn't allow exiting to any ports. This bug could screw
17428 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
17429 1238. Bug discovered by Martin Kowalczyk.
17430 - When freeing a session key, zero it out completely. We only zeroed
17431 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
17432 patched by ekir. Fixes bug 1254.
17435 - Fix static compilation by listing the openssl libraries in the right
17436 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
17437 - Resume handling .exit hostnames in a special way: originally we
17438 stripped the .exit part and used the requested exit relay. In
17439 0.2.2.1-alpha we stopped treating them in any special way, meaning
17440 if you use a .exit address then Tor will pass it on to the exit
17441 relay. Now we reject the .exit stream outright, since that behavior
17442 might be more expected by the user. Found and diagnosed by Scott
17443 Bennett and Downie on or-talk.
17444 - Don't spam the controller with events when we have no file
17445 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
17446 for log messages was already solved from bug 748.)
17447 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
17449 - Make the DNSPort option work with libevent 2.x. Don't alter the
17450 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
17451 - Emit a GUARD DROPPED controller event for a case we missed.
17452 - Make more fields in the controller protocol case-insensitive, since
17453 control-spec.txt said they were.
17454 - Refactor resolve_my_address() to not use gethostbyname() anymore.
17455 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
17456 - Fix a spec conformance issue: the network-status-version token
17457 must be the first token in a v3 consensus or vote. Discovered by
17458 parakeep. Bugfix on 0.2.0.3-alpha.
17460 o Code simplifications and refactoring:
17461 - Generate our manpage and HTML documentation using Asciidoc. This
17462 change should make it easier to maintain the documentation, and
17463 produce nicer HTML.
17464 - Remove the --enable-iphone option. According to reports from Marco
17465 Bonetti, Tor builds fine without any special tweaking on recent
17466 iPhone SDK versions.
17467 - Removed some unnecessary files from the source distribution. The
17468 AUTHORS file has now been merged into the people page on the
17469 website. The roadmaps and design doc can now be found in the
17470 projects directory in svn.
17471 - Enabled various circuit build timeout constants to be controlled
17472 by consensus parameters. Also set better defaults for these
17473 parameters based on experimentation on broadband and simulated
17474 high latency links.
17477 - The 'EXTENDCIRCUIT' control port command can now be used with
17478 a circ id of 0 and no path. This feature will cause Tor to build
17479 a new 'fast' general purpose circuit using its own path selection
17481 - Added a BUILDTIMEOUT_SET controller event to describe changes
17482 to the circuit build timeout.
17483 - Future-proof the controller protocol a bit by ignoring keyword
17484 arguments we do not recognize.
17485 - Expand homedirs passed to tor-checkkey. This should silence a
17486 coverity complaint about passing a user-supplied string into
17487 open() without checking it.
17490 Changes in version 0.2.1.25 - 2010-03-16
17491 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
17492 prevent relays from guessing their IP address correctly. It also fixes
17493 several minor potential security bugs.
17496 - Fix a regression from our patch for bug 1244 that caused relays
17497 to guess their IP address incorrectly if they didn't set Address
17498 in their torrc and/or their address fails to resolve. Bugfix on
17499 0.2.1.23; fixes bug 1269.
17500 - When freeing a session key, zero it out completely. We only zeroed
17501 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
17502 patched by ekir. Fixes bug 1254.
17505 - Fix a dereference-then-NULL-check sequence when publishing
17506 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
17508 - Fix another dereference-then-NULL-check sequence. Bugfix on
17509 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
17510 - Make sure we treat potentially not NUL-terminated strings correctly.
17511 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
17515 Changes in version 0.2.1.24 - 2010-02-21
17516 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
17520 - Work correctly out-of-the-box with even more vendor-patched versions
17521 of OpenSSL. In particular, make it so Debian and OS X don't need
17522 customized patches to run/build.
17525 Changes in version 0.2.1.23 - 2010-02-13
17526 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
17527 again on the latest OS X, and updates the location of a directory
17530 o Major bugfixes (performance):
17531 - We were selecting our guards uniformly at random, and then weighting
17532 which of our guards we'd use uniformly at random. This imbalance
17533 meant that Tor clients were severely limited on throughput (and
17534 probably latency too) by the first hop in their circuit. Now we
17535 select guards weighted by currently advertised bandwidth. We also
17536 automatically discard guards picked using the old algorithm. Fixes
17537 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17540 - Make Tor work again on the latest OS X: when deciding whether to
17541 use strange flags to turn TLS renegotiation on, detect the OpenSSL
17542 version at run-time, not compile time. We need to do this because
17543 Apple doesn't update its dev-tools headers when it updates its
17544 libraries in a security patch.
17545 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
17546 that could happen on 32-bit platforms with 64-bit time_t. Also fix
17547 a memory leak when requesting a hidden service descriptor we've
17548 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
17551 o Directory authority changes:
17552 - Change IP address for dannenberg (v3 directory authority), and
17553 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
17554 service directory authority) from the list.
17557 - Refactor resolve_my_address() to not use gethostbyname() anymore.
17558 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
17561 - Avoid a mad rush at the beginning of each month when each client
17562 rotates half of its guards. Instead we spread the rotation out
17563 throughout the month, but we still avoid leaving a precise timestamp
17564 in the state file about when we first picked the guard. Improves
17565 over the behavior introduced in 0.1.2.17.
17568 Changes in version 0.2.2.8-alpha - 2010-01-26
17569 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
17570 causing bridge relays to disappear. If you're running a bridge,
17574 - Fix a memory corruption bug on bridges that occured during the
17575 inclusion of stats data in extra-info descriptors. Also fix the
17576 interface for geoip_get_bridge_stats* to prevent similar bugs in
17577 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
17578 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
17581 - Ignore OutboundBindAddress when connecting to localhost.
17582 Connections to localhost need to come _from_ localhost, or else
17583 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
17587 Changes in version 0.2.2.7-alpha - 2010-01-19
17588 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
17589 as laying the groundwork for further relay-side performance fixes. It
17590 also starts cleaning up client behavior with respect to the EntryNodes,
17591 ExitNodes, and StrictNodes config options.
17593 This release also rotates two directory authority keys, due to a
17594 security breach of some of the Torproject servers.
17596 o Directory authority changes:
17597 - Rotate keys (both v3 identity and relay identity) for moria1
17600 o Major features (performance):
17601 - We were selecting our guards uniformly at random, and then weighting
17602 which of our guards we'd use uniformly at random. This imbalance
17603 meant that Tor clients were severely limited on throughput (and
17604 probably latency too) by the first hop in their circuit. Now we
17605 select guards weighted by currently advertised bandwidth. We also
17606 automatically discard guards picked using the old algorithm. Fixes
17607 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17608 - When choosing which cells to relay first, relays can now favor
17609 circuits that have been quiet recently, to provide lower latency
17610 for low-volume circuits. By default, relays enable or disable this
17611 feature based on a setting in the consensus. You can override
17612 this default by using the new "CircuitPriorityHalflife" config
17613 option. Design and code by Ian Goldberg, Can Tang, and Chris
17615 - Add separate per-conn write limiting to go with the per-conn read
17616 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
17617 but never per-conn write limits.
17618 - New consensus params "bwconnrate" and "bwconnburst" to let us
17619 rate-limit client connections as they enter the network. It's
17620 controlled in the consensus so we can turn it on and off for
17621 experiments. It's starting out off. Based on proposal 163.
17623 o Major features (relay selection options):
17624 - Switch to a StrictNodes config option, rather than the previous
17625 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
17626 "StrictExcludeNodes" option.
17627 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
17628 change during a config reload, mark and discard all our origin
17629 circuits. This fix should address edge cases where we change the
17630 config options and but then choose a circuit that we created before
17632 - If EntryNodes or ExitNodes are set, be more willing to use an
17633 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
17635 - Make EntryNodes config option much more aggressive even when
17636 StrictNodes is not set. Before it would prepend your requested
17637 entrynodes to your list of guard nodes, but feel free to use others
17638 after that. Now it chooses only from your EntryNodes if any of
17639 those are available, and only falls back to others if a) they're
17640 all down and b) StrictNodes is not set.
17641 - Now we refresh your entry guards from EntryNodes at each consensus
17642 fetch -- rather than just at startup and then they slowly rot as
17643 the network changes.
17646 - Stop bridge directory authorities from answering dbg-stability.txt
17647 directory queries, which would let people fetch a list of all
17648 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17651 - Log a notice when we get a new control connection. Now it's easier
17652 for security-conscious users to recognize when a local application
17653 is knocking on their controller door. Suggested by bug 1196.
17654 - New config option "CircuitStreamTimeout" to override our internal
17655 timeout schedule for how many seconds until we detach a stream from
17656 a circuit and try a new circuit. If your network is particularly
17657 slow, you might want to set this to a number like 60.
17658 - New controller command "getinfo config-text". It returns the
17659 contents that Tor would write if you send it a SAVECONF command,
17660 so the controller can write the file to disk itself.
17661 - New options for SafeLogging to allow scrubbing only log messages
17662 generated while acting as a relay.
17663 - Ship the bridges spec file in the tarball too.
17664 - Avoid a mad rush at the beginning of each month when each client
17665 rotates half of its guards. Instead we spread the rotation out
17666 throughout the month, but we still avoid leaving a precise timestamp
17667 in the state file about when we first picked the guard. Improves
17668 over the behavior introduced in 0.1.2.17.
17670 o Minor bugfixes (compiling):
17671 - Fix compilation on OS X 10.3, which has a stub mlockall() but
17672 hides it. Bugfix on 0.2.2.6-alpha.
17673 - Fix compilation on Solaris by removing support for the
17674 DisableAllSwap config option. Solaris doesn't have an rlimit for
17675 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
17678 o Minor bugfixes (crashes):
17679 - Do not segfault when writing buffer stats when we haven't observed
17680 a single circuit to report about. Found by Fabian Lanze. Bugfix on
17682 - If we're in the pathological case where there's no exit bandwidth
17683 but there is non-exit bandwidth, or no guard bandwidth but there
17684 is non-guard bandwidth, don't crash during path selection. Bugfix
17686 - Fix an impossible-to-actually-trigger buffer overflow in relay
17687 descriptor generation. Bugfix on 0.1.0.15.
17689 o Minor bugfixes (privacy):
17690 - Fix an instance where a Tor directory mirror might accidentally
17691 log the IP address of a misbehaving Tor client. Bugfix on
17693 - Don't list Windows capabilities in relay descriptors. We never made
17694 use of them, and maybe it's a bad idea to publish them. Bugfix
17697 o Minor bugfixes (other):
17698 - Resolve an edge case in path weighting that could make us misweight
17699 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
17700 - Fix statistics on client numbers by country as seen by bridges that
17701 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
17702 intervals instead of variable 12-to-48-hour intervals.
17703 - After we free an internal connection structure, overwrite it
17704 with a different memory value than we use for overwriting a freed
17705 internal circuit structure. Should help with debugging. Suggested
17707 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
17710 o Removed features:
17711 - Remove the HSAuthorityRecordStats option that version 0 hidden
17712 service authorities could have used to track statistics of overall
17713 hidden service usage.
17716 Changes in version 0.2.1.22 - 2010-01-19
17717 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
17718 authorities -- it would tell you its whole history of bridge descriptors
17719 if you make the right directory request. This stable update also
17720 rotates two of the seven v3 directory authority keys and locations.
17722 o Directory authority changes:
17723 - Rotate keys (both v3 identity and relay identity) for moria1
17727 - Stop bridge directory authorities from answering dbg-stability.txt
17728 directory queries, which would let people fetch a list of all
17729 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17732 Changes in version 0.2.1.21 - 2009-12-21
17733 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
17734 library. If you use Tor on Linux / Unix and you're getting SSL
17735 renegotiation errors, upgrading should help. We also recommend an
17736 upgrade if you're an exit relay.
17739 - Work around a security feature in OpenSSL 0.9.8l that prevents our
17740 handshake from working unless we explicitly tell OpenSSL that we
17741 are using SSL renegotiation safely. We are, of course, but OpenSSL
17742 0.9.8l won't work unless we say we are.
17743 - Avoid crashing if the client is trying to upload many bytes and the
17744 circuit gets torn down at the same time, or if the flip side
17745 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
17748 - Do not refuse to learn about authority certs and v2 networkstatus
17749 documents that are older than the latest consensus. This bug might
17750 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
17751 Spotted and fixed by xmux.
17752 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
17753 trigger platform-specific option misparsing case found by Coverity
17755 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
17756 trigger assert. Fixes bug 1173.
17759 Changes in version 0.2.2.6-alpha - 2009-11-19
17760 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
17761 support for the new lower-footprint "microdescriptor" directory design,
17762 future-proofing our consensus format against new hash functions or
17763 other changes, and an Android port. It also makes Tor compatible with
17764 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
17767 - Directory authorities can now create, vote on, and serve multiple
17768 parallel formats of directory data as part of their voting process.
17769 Partially implements Proposal 162: "Publish the consensus in
17771 - Directory authorities can now agree on and publish small summaries
17772 of router information that clients can use in place of regular
17773 server descriptors. This transition will eventually allow clients
17774 to use far less bandwidth for downloading information about the
17775 network. Begins the implementation of Proposal 158: "Clients
17776 download consensus + microdescriptors".
17777 - The directory voting system is now extensible to use multiple hash
17778 algorithms for signatures and resource selection. Newer formats
17779 are signed with SHA256, with a possibility for moving to a better
17780 hash algorithm in the future.
17781 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
17782 current and future memory pages via mlockall(). On supported
17783 platforms (modern Linux and probably BSD but not Windows or OS X),
17784 this should effectively disable any and all attempts to page out
17785 memory. This option requires that you start your Tor as root --
17786 if you use DisableAllSwap, please consider using the User option
17787 to properly reduce the privileges of your Tor.
17788 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
17789 to help Tor build correctly for Android phones.
17792 - Work around a security feature in OpenSSL 0.9.8l that prevents our
17793 handshake from working unless we explicitly tell OpenSSL that we
17794 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
17795 won't work unless we say we are.
17798 - Fix a crash bug when trying to initialize the evdns module in
17799 Libevent 2. Bugfix on 0.2.1.16-rc.
17800 - Stop logging at severity 'warn' when some other Tor client tries
17801 to establish a circuit with us using weak DH keys. It's a protocol
17802 violation, but that doesn't mean ordinary users need to hear about
17803 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
17804 - Do not refuse to learn about authority certs and v2 networkstatus
17805 documents that are older than the latest consensus. This bug might
17806 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
17807 Spotted and fixed by xmux.
17808 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
17809 - If all authorities restart at once right before a consensus vote,
17810 nobody will vote about "Running", and clients will get a consensus
17811 with no usable relays. Instead, authorities refuse to build a
17812 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
17813 - If your relay can't keep up with the number of incoming create
17814 cells, it would log one warning per failure into your logs. Limit
17815 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
17816 - Bridges now use "reject *:*" as their default exit policy. Bugfix
17817 on 0.2.0.3-alpha; fixes bug 1113.
17818 - Fix a memory leak on directory authorities during voting that was
17819 introduced in 0.2.2.1-alpha. Found via valgrind.
17822 Changes in version 0.2.1.20 - 2009-10-15
17823 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
17824 services at once, prepares for more performance improvements, and
17825 fixes a bunch of smaller bugs.
17827 The Windows and OS X bundles also include a more recent Vidalia,
17828 and switch from Privoxy to Polipo.
17830 The OS X installers are now drag and drop. It's best to un-install
17831 Tor/Vidalia and then install this new bundle, rather than upgrade. If
17832 you want to upgrade, you'll need to update the paths for Tor and Polipo
17833 in the Vidalia Settings window.
17836 - Send circuit or stream sendme cells when our window has decreased
17837 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
17838 by Karsten when testing the "reduce circuit window" performance
17839 patch. Bugfix on the 54th commit on Tor -- from July 2002,
17840 before the release of Tor 0.0.0. This is the new winner of the
17842 - Fix a remotely triggerable memory leak when a consensus document
17843 contains more than one signature from the same voter. Bugfix on
17845 - Avoid segfault in rare cases when finishing an introduction circuit
17846 as a client and finding out that we don't have an introduction key
17847 for it. Fixes bug 1073. Reported by Aaron Swartz.
17850 - Tor now reads the "circwindow" parameter out of the consensus,
17851 and uses that value for its circuit package window rather than the
17852 default of 1000 cells. Begins the implementation of proposal 168.
17854 o New directory authorities:
17855 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
17857 - Move moria1 and tonga to alternate IP addresses.
17860 - Fix a signed/unsigned compile warning in 0.2.1.19.
17861 - Fix possible segmentation fault on directory authorities. Bugfix on
17863 - Fix an extremely rare infinite recursion bug that could occur if
17864 we tried to log a message after shutting down the log subsystem.
17865 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
17866 - Fix an obscure bug where hidden services on 64-bit big-endian
17867 systems might mis-read the timestamp in v3 introduce cells, and
17868 refuse to connect back to the client. Discovered by "rotor".
17869 Bugfix on 0.2.1.6-alpha.
17870 - We were triggering a CLOCK_SKEW controller status event whenever
17871 we connect via the v2 connection protocol to any relay that has
17872 a wrong clock. Instead, we should only inform the controller when
17873 it's a trusted authority that claims our clock is wrong. Bugfix
17874 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
17875 - We were telling the controller about CHECKING_REACHABILITY and
17876 REACHABILITY_FAILED status events whenever we launch a testing
17877 circuit or notice that one has failed. Instead, only tell the
17878 controller when we want to inform the user of overall success or
17879 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
17881 - Don't warn when we're using a circuit that ends with a node
17882 excluded in ExcludeExitNodes, but the circuit is not used to access
17883 the outside world. This should help fix bug 1090. Bugfix on
17885 - Work around a small memory leak in some versions of OpenSSL that
17886 stopped the memory used by the hostname TLS extension from being
17890 - Add a "getinfo status/accepted-server-descriptor" controller
17891 command, which is the recommended way for controllers to learn
17892 whether our server descriptor has been successfully received by at
17893 least on directory authority. Un-recommend good-server-descriptor
17894 getinfo and status events until we have a better design for them.
17897 Changes in version 0.2.2.5-alpha - 2009-10-11
17898 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
17901 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
17903 o Directory authorities:
17904 - Temporarily (just for this release) move dizum to an alternate
17908 Changes in version 0.2.2.4-alpha - 2009-10-10
17909 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
17910 introduces a new unit test framework, shifts directry authority
17911 addresses around to reduce the impact from recent blocking events,
17912 and fixes a few smaller bugs.
17915 - Fix several more asserts in the circuit_build_times code, for
17916 example one that causes Tor to fail to start once we have
17917 accumulated 5000 build times in the state file. Bugfixes on
17918 0.2.2.2-alpha; fixes bug 1108.
17920 o New directory authorities:
17921 - Move moria1 and Tonga to alternate IP addresses.
17924 - Log SSL state transitions at debug level during handshake, and
17925 include SSL states in error messages. This may help debug future
17926 SSL handshake issues.
17927 - Add a new "Handshake" log domain for activities that happen
17928 during the TLS handshake.
17929 - Revert to the "June 3 2009" ip-to-country file. The September one
17930 seems to have removed most US IP addresses.
17931 - Directory authorities now reject Tor relays with versions less than
17932 0.1.2.14. This step cuts out four relays from the current network,
17933 none of which are very big.
17936 - Fix a couple of smaller issues with gathering statistics. Bugfixes
17938 - Fix two memory leaks in the error case of
17939 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
17940 - Don't count one-hop circuits when we're estimating how long it
17941 takes circuits to build on average. Otherwise we'll set our circuit
17942 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
17943 - Directory authorities no longer change their opinion of, or vote on,
17944 whether a router is Running, unless they have themselves been
17945 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
17948 o Code simplifications and refactoring:
17949 - Revise our unit tests to use the "tinytest" framework, so we
17950 can run tests in their own processes, have smarter setup/teardown
17951 code, and so on. The unit test code has moved to its own
17952 subdirectory, and has been split into multiple modules.
17955 Changes in version 0.2.2.3-alpha - 2009-09-23
17956 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
17959 - Fix an overzealous assert in our new circuit build timeout code.
17960 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
17963 - If the networkstatus consensus tells us that we should use a
17964 negative circuit package window, ignore it. Otherwise we'll
17965 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
17968 Changes in version 0.2.2.2-alpha - 2009-09-21
17969 Tor 0.2.2.2-alpha introduces our latest performance improvement for
17970 clients: Tor tracks the average time it takes to build a circuit, and
17971 avoids using circuits that take too long to build. For fast connections,
17972 this feature can cut your expected latency in half. For slow or flaky
17973 connections, it could ruin your Tor experience. Let us know if it does!
17976 - Tor now tracks how long it takes to build client-side circuits
17977 over time, and adapts its timeout to local network performance.
17978 Since a circuit that takes a long time to build will also provide
17979 bad performance, we get significant latency improvements by
17980 discarding the slowest 20% of circuits. Specifically, Tor creates
17981 circuits more aggressively than usual until it has enough data
17982 points for a good timeout estimate. Implements proposal 151.
17983 We are especially looking for reports (good and bad) from users with
17984 both EDGE and broadband connections that can move from broadband
17985 to EDGE and find out if the build-time data in the .tor/state gets
17986 reset without loss of Tor usability. You should also see a notice
17987 log message telling you that Tor has reset its timeout.
17988 - Directory authorities can now vote on arbitary integer values as
17989 part of the consensus process. This is designed to help set
17990 network-wide parameters. Implements proposal 167.
17991 - Tor now reads the "circwindow" parameter out of the consensus,
17992 and uses that value for its circuit package window rather than the
17993 default of 1000 cells. Begins the implementation of proposal 168.
17996 - Fix a remotely triggerable memory leak when a consensus document
17997 contains more than one signature from the same voter. Bugfix on
18001 - Fix an extremely rare infinite recursion bug that could occur if
18002 we tried to log a message after shutting down the log subsystem.
18003 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
18004 - Fix parsing for memory or time units given without a space between
18005 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
18006 - A networkstatus vote must contain exactly one signature. Spec
18007 conformance issue. Bugfix on 0.2.0.3-alpha.
18008 - Fix an obscure bug where hidden services on 64-bit big-endian
18009 systems might mis-read the timestamp in v3 introduce cells, and
18010 refuse to connect back to the client. Discovered by "rotor".
18011 Bugfix on 0.2.1.6-alpha.
18012 - We were triggering a CLOCK_SKEW controller status event whenever
18013 we connect via the v2 connection protocol to any relay that has
18014 a wrong clock. Instead, we should only inform the controller when
18015 it's a trusted authority that claims our clock is wrong. Bugfix
18016 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
18017 - We were telling the controller about CHECKING_REACHABILITY and
18018 REACHABILITY_FAILED status events whenever we launch a testing
18019 circuit or notice that one has failed. Instead, only tell the
18020 controller when we want to inform the user of overall success or
18021 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
18023 - Don't warn when we're using a circuit that ends with a node
18024 excluded in ExcludeExitNodes, but the circuit is not used to access
18025 the outside world. This should help fix bug 1090, but more problems
18026 remain. Bugfix on 0.2.1.6-alpha.
18027 - Work around a small memory leak in some versions of OpenSSL that
18028 stopped the memory used by the hostname TLS extension from being
18030 - Make our 'torify' script more portable; if we have only one of
18031 'torsocks' or 'tsocks' installed, don't complain to the user;
18032 and explain our warning about tsocks better.
18035 - Add a "getinfo status/accepted-server-descriptor" controller
18036 command, which is the recommended way for controllers to learn
18037 whether our server descriptor has been successfully received by at
18038 least on directory authority. Un-recommend good-server-descriptor
18039 getinfo and status events until we have a better design for them.
18040 - Update to the "September 4 2009" ip-to-country file.
18043 Changes in version 0.2.2.1-alpha - 2009-08-26
18044 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
18045 Tor clients to bootstrap on networks where only port 80 is reachable,
18046 makes it more straightforward to support hardware crypto accelerators,
18047 and starts the groundwork for gathering stats safely at relays.
18050 - Start the process of disabling ".exit" address notation, since it
18051 can be used for a variety of esoteric application-level attacks
18052 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
18055 o New directory authorities:
18056 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
18060 - New AccelName and AccelDir options add support for dynamic OpenSSL
18061 hardware crypto acceleration engines.
18062 - Tor now supports tunneling all of its outgoing connections over
18063 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
18064 configuration options. Code by Christopher Davis.
18067 - Send circuit or stream sendme cells when our window has decreased
18068 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
18069 by Karsten when testing the "reduce circuit window" performance
18070 patch. Bugfix on the 54th commit on Tor -- from July 2002,
18071 before the release of Tor 0.0.0. This is the new winner of the
18074 o New options for gathering stats safely:
18075 - Directory mirrors that set "DirReqStatistics 1" write statistics
18076 about directory requests to disk every 24 hours. As compared to the
18077 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
18078 1) stats are written to disk exactly every 24 hours; 2) estimated
18079 shares of v2 and v3 requests are determined as mean values, not at
18080 the end of a measurement period; 3) unresolved requests are listed
18081 with country code '??'; 4) directories also measure download times.
18082 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
18083 number of exit streams and transferred bytes per port to disk every
18085 - Relays that set "CellStatistics 1" write statistics on how long
18086 cells spend in their circuit queues to disk every 24 hours.
18087 - Entry nodes that set "EntryStatistics 1" write statistics on the
18088 rough number and origins of connecting clients to disk every 24
18090 - Relays that write any of the above statistics to disk and set
18091 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
18092 their extra-info documents.
18095 - New --digests command-line switch to output the digests of the
18096 source files Tor was built with.
18097 - The "torify" script now uses torsocks where available.
18098 - The memarea code now uses a sentinel value at the end of each area
18099 to make sure nothing writes beyond the end of an area. This might
18100 help debug some conceivable causes of bug 930.
18101 - Time and memory units in the configuration file can now be set to
18102 fractional units. For example, "2.5 GB" is now a valid value for
18104 - Certain Tor clients (such as those behind check.torproject.org) may
18105 want to fetch the consensus in an extra early manner. To enable this
18106 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
18107 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
18108 as only certain clients who must have this information sooner should
18110 - Instead of adding the svn revision to the Tor version string, report
18111 the git commit (when we're building from a git checkout).
18114 - If any of the v3 certs we download are unparseable, we should
18115 actually notice the failure so we don't retry indefinitely. Bugfix
18116 on 0.2.0.x; reported by "rotator".
18117 - If the cached cert file is unparseable, warn but don't exit.
18118 - Fix possible segmentation fault on directory authorities. Bugfix on
18120 - When Tor fails to parse a descriptor of any kind, dump it to disk.
18121 Might help diagnosing bug 1051.
18123 o Deprecated and removed features:
18124 - The controller no longer accepts the old obsolete "addr-mappings/"
18125 or "unregistered-servers-" GETINFO values.
18126 - Hidden services no longer publish version 0 descriptors, and clients
18127 do not request or use version 0 descriptors. However, the old hidden
18128 service authorities still accept and serve version 0 descriptors
18129 when contacted by older hidden services/clients.
18130 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
18131 always on; using them is necessary for correct forward-compatible
18133 - Remove support for .noconnect style addresses. Nobody was using
18134 them, and they provided another avenue for detecting Tor users
18135 via application-level web tricks.
18137 o Packaging changes:
18138 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
18139 installer bundles. See
18140 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
18141 for details of what's new in Vidalia 0.2.3.
18142 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
18143 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
18144 configuration file, rather than the old Privoxy.
18145 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
18146 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
18147 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
18148 better compatibility with OS X 10.6, aka Snow Leopard.
18149 - OS X Vidalia Bundle: The multi-package installer is now replaced
18150 by a simple drag and drop to the /Applications folder. This change
18151 occurred with the upgrade to Vidalia 0.2.3.
18154 Changes in version 0.2.1.19 - 2009-07-28
18155 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
18156 services on Tor 0.2.1.3-alpha through 0.2.1.18.
18159 - Make accessing hidden services on 0.2.1.x work right again.
18160 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
18161 part of patch provided by "optimist".
18164 - When a relay/bridge is writing out its identity key fingerprint to
18165 the "fingerprint" file and to its logs, write it without spaces. Now
18166 it will look like the fingerprints in our bridges documentation,
18167 and confuse fewer users.
18170 - Relays no longer publish a new server descriptor if they change
18171 their MaxAdvertisedBandwidth config option but it doesn't end up
18172 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
18173 fixes bug 1026. Patch from Sebastian.
18174 - Avoid leaking memory every time we get a create cell but we have
18175 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
18176 fixes bug 1034. Reported by BarkerJr.
18179 Changes in version 0.2.1.18 - 2009-07-24
18180 Tor 0.2.1.18 lays the foundations for performance improvements,
18181 adds status events to help users diagnose bootstrap problems, adds
18182 optional authentication/authorization for hidden services, fixes a
18183 variety of potential anonymity problems, and includes a huge pile of
18184 other features and bug fixes.
18187 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
18190 Changes in version 0.2.1.17-rc - 2009-07-07
18191 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
18192 candidate for the 0.2.1.x series. It lays the groundwork for further
18193 client performance improvements, and also fixes a big bug with directory
18194 authorities that were causing them to assign Guard and Stable flags
18197 The Windows bundles also finally include the geoip database that we
18198 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
18199 should actually install Torbutton rather than giving you a cryptic
18200 failure message (oops).
18203 - Clients now use the bandwidth values in the consensus, rather than
18204 the bandwidth values in each relay descriptor. This approach opens
18205 the door to more accurate bandwidth estimates once the directory
18206 authorities start doing active measurements. Implements more of
18210 - When Tor clients restart after 1-5 days, they discard all their
18211 cached descriptors as too old, but they still use the cached
18212 consensus document. This approach is good for robustness, but
18213 bad for performance: since they don't know any bandwidths, they
18214 end up choosing at random rather than weighting their choice by
18215 speed. Fixed by the above feature of putting bandwidths in the
18216 consensus. Bugfix on 0.2.0.x.
18217 - Directory authorities were neglecting to mark relays down in their
18218 internal histories if the relays fall off the routerlist without
18219 ever being found unreachable. So there were relays in the histories
18220 that haven't been seen for eight months, and are listed as being
18221 up for eight months. This wreaked havoc on the "median wfu"
18222 and "median mtbf" calculations, in turn making Guard and Stable
18223 flags very wrong, hurting network performance. Fixes bugs 696 and
18224 969. Bugfix on 0.2.0.6-alpha.
18227 - Serve the DirPortFrontPage page even when we have been approaching
18228 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
18229 - The control port would close the connection before flushing long
18230 replies, such as the network consensus, if a QUIT command was issued
18231 before the reply had completed. Now, the control port flushes all
18232 pending replies before closing the connection. Also fixed a spurious
18233 warning when a QUIT command is issued after a malformed or rejected
18234 AUTHENTICATE command, but before the connection was closed. Patch
18235 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
18236 - When we can't find an intro key for a v2 hidden service descriptor,
18237 fall back to the v0 hidden service descriptor and log a bug message.
18238 Workaround for bug 1024.
18239 - Fix a log message that did not respect the SafeLogging option.
18243 - If we're a relay and we change our IP address, be more verbose
18244 about the reason that made us change. Should help track down
18245 further bugs for relays on dynamic IP addresses.
18248 Changes in version 0.2.0.35 - 2009-06-24
18250 - Avoid crashing in the presence of certain malformed descriptors.
18251 Found by lark, and by automated fuzzing.
18252 - Fix an edge case where a malicious exit relay could convince a
18253 controller that the client's DNS question resolves to an internal IP
18254 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
18257 - Finally fix the bug where dynamic-IP relays disappear when their
18258 IP address changes: directory mirrors were mistakenly telling
18259 them their old address if they asked via begin_dir, so they
18260 never got an accurate answer about their new address, so they
18261 just vanished after a day. For belt-and-suspenders, relays that
18262 don't set Address in their config now avoid using begin_dir for
18263 all direct connections. Should fix bugs 827, 883, and 900.
18264 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
18265 that would occur on some exit nodes when DNS failures and timeouts
18266 occurred in certain patterns. Fix for bug 957.
18269 - When starting with a cache over a few days old, do not leak
18270 memory for the obsolete router descriptors in it. Bugfix on
18271 0.2.0.33; fixes bug 672.
18272 - Hidden service clients didn't use a cached service descriptor that
18273 was older than 15 minutes, but wouldn't fetch a new one either,
18274 because there was already one in the cache. Now, fetch a v2
18275 descriptor unless the same descriptor was added to the cache within
18276 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
18279 Changes in version 0.2.1.16-rc - 2009-06-20
18280 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
18281 a bunch of minor bugs.
18284 - Fix an edge case where a malicious exit relay could convince a
18285 controller that the client's DNS question resolves to an internal IP
18286 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
18288 o Major performance improvements (on 0.2.0.x):
18289 - Disable and refactor some debugging checks that forced a linear scan
18290 over the whole server-side DNS cache. These accounted for over 50%
18291 of CPU time on a relatively busy exit node's gprof profile. Found
18293 - Disable some debugging checks that appeared in exit node profile
18297 - Update to the "June 3 2009" ip-to-country file.
18298 - Do not have tor-resolve automatically refuse all .onion addresses;
18299 if AutomapHostsOnResolve is set in your torrc, this will work fine.
18301 o Minor bugfixes (on 0.2.0.x):
18302 - Log correct error messages for DNS-related network errors on
18304 - Fix a race condition that could cause crashes or memory corruption
18305 when running as a server with a controller listening for log
18307 - Avoid crashing when we have a policy specified in a DirPolicy or
18308 SocksPolicy or ReachableAddresses option with ports set on it,
18309 and we re-load the policy. May fix bug 996.
18310 - Hidden service clients didn't use a cached service descriptor that
18311 was older than 15 minutes, but wouldn't fetch a new one either,
18312 because there was already one in the cache. Now, fetch a v2
18313 descriptor unless the same descriptor was added to the cache within
18314 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
18316 o Minor bugfixes (on 0.2.1.x):
18317 - Don't warn users about low port and hibernation mix when they
18318 provide a *ListenAddress directive to fix that. Bugfix on
18320 - When switching back and forth between bridge mode, do not start
18321 gathering GeoIP data until two hours have passed.
18322 - Do not complain that the user has requested an excluded node as
18323 an exit when the node is not really an exit. This could happen
18324 because the circuit was for testing, or an introduction point.
18328 Changes in version 0.2.1.15-rc - 2009-05-25
18329 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
18330 series. It fixes a major bug on fast exit relays, as well as a variety
18331 of more minor bugs.
18333 o Major bugfixes (on 0.2.0.x):
18334 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
18335 that would occur on some exit nodes when DNS failures and timeouts
18336 occurred in certain patterns. Fix for bug 957.
18338 o Minor bugfixes (on 0.2.0.x):
18339 - Actually return -1 in the error case for read_bandwidth_usage().
18340 Harmless bug, since we currently don't care about the return value
18341 anywhere. Bugfix on 0.2.0.9-alpha.
18342 - Provide a more useful log message if bug 977 (related to buffer
18343 freelists) ever reappears, and do not crash right away.
18344 - Fix an assertion failure on 64-bit platforms when we allocated
18345 memory right up to the end of a memarea, then realigned the memory
18346 one step beyond the end. Fixes a possible cause of bug 930.
18347 - Protect the count of open sockets with a mutex, so we can't
18348 corrupt it when two threads are closing or opening sockets at once.
18349 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
18350 - Don't allow a bridge to publish its router descriptor to a
18351 non-bridge directory authority. Fixes part of bug 932.
18352 - When we change to or from being a bridge, reset our counts of
18353 client usage by country. Fixes bug 932.
18354 - Fix a bug that made stream bandwidth get misreported to the
18356 - Stop using malloc_usable_size() to use more area than we had
18357 actually allocated: it was safe, but made valgrind really unhappy.
18358 - Fix a memory leak when v3 directory authorities load their keys
18359 and cert from disk. Bugfix on 0.2.0.1-alpha.
18361 o Minor bugfixes (on 0.2.1.x):
18362 - Fix use of freed memory when deciding to mark a non-addable
18363 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
18366 Changes in version 0.2.1.14-rc - 2009-04-12
18367 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
18368 series. It begins fixing some major performance problems, and also
18369 finally addresses the bug that was causing relays on dynamic IP
18370 addresses to fall out of the directory.
18373 - Clients replace entry guards that were chosen more than a few months
18374 ago. This change should significantly improve client performance,
18375 especially once more people upgrade, since relays that have been
18376 a guard for a long time are currently overloaded.
18378 o Major bugfixes (on 0.2.0):
18379 - Finally fix the bug where dynamic-IP relays disappear when their
18380 IP address changes: directory mirrors were mistakenly telling
18381 them their old address if they asked via begin_dir, so they
18382 never got an accurate answer about their new address, so they
18383 just vanished after a day. For belt-and-suspenders, relays that
18384 don't set Address in their config now avoid using begin_dir for
18385 all direct connections. Should fix bugs 827, 883, and 900.
18386 - Relays were falling out of the networkstatus consensus for
18387 part of a day if they changed their local config but the
18388 authorities discarded their new descriptor as "not sufficiently
18389 different". Now directory authorities accept a descriptor as changed
18390 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
18391 patch by Sebastian.
18392 - Avoid crashing in the presence of certain malformed descriptors.
18393 Found by lark, and by automated fuzzing.
18396 - When generating circuit events with verbose nicknames for
18397 controllers, try harder to look up nicknames for routers on a
18398 circuit. (Previously, we would look in the router descriptors we had
18399 for nicknames, but not in the consensus.) Partial fix for bug 941.
18400 - If the bridge config line doesn't specify a port, assume 443.
18401 This makes bridge lines a bit smaller and easier for users to
18403 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
18404 bytes (aka 20KB/s), to match our documentation. Also update
18405 directory authorities so they always assign the Fast flag to relays
18406 with 20KB/s of capacity. Now people running relays won't suddenly
18407 find themselves not seeing any use, if the network gets faster
18409 - Update to the "April 3 2009" ip-to-country file.
18412 - Avoid trying to print raw memory to the logs when we decide to
18413 give up on downloading a given relay descriptor. Bugfix on
18415 - In tor-resolve, when the Tor client to use is specified by
18416 <hostname>:<port>, actually use the specified port rather than
18417 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
18418 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
18419 - When starting with a cache over a few days old, do not leak
18420 memory for the obsolete router descriptors in it. Bugfix on
18422 - Avoid double-free on list of successfully uploaded hidden
18423 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
18424 - Change memarea_strndup() implementation to work even when
18425 duplicating a string at the end of a page. This bug was
18426 harmless for now, but could have meant crashes later. Fix by
18427 lark. Bugfix on 0.2.1.1-alpha.
18428 - Limit uploaded directory documents to be 16M rather than 500K.
18429 The directory authorities were refusing v3 consensus votes from
18430 other authorities, since the votes are now 504K. Fixes bug 959;
18431 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
18432 - Directory authorities should never send a 503 "busy" response to
18433 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
18437 Changes in version 0.2.1.13-alpha - 2009-03-09
18438 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
18439 cleanups. We're finally getting close to a release candidate.
18442 - Correctly update the list of which countries we exclude as
18443 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
18444 lark. Bugfix on 0.2.1.6-alpha.
18446 o Minor bugfixes (on 0.2.0.x and earlier):
18447 - Automatically detect MacOSX versions earlier than 10.4.0, and
18448 disable kqueue from inside Tor when running with these versions.
18449 We previously did this from the startup script, but that was no
18450 help to people who didn't use the startup script. Resolves bug 863.
18451 - When we had picked an exit node for a connection, but marked it as
18452 "optional", and it turned out we had no onion key for the exit,
18453 stop wanting that exit and try again. This situation may not
18454 be possible now, but will probably become feasible with proposal
18455 158. Spotted by rovv. Fixes another case of bug 752.
18456 - Clients no longer cache certificates for authorities they do not
18457 recognize. Bugfix on 0.2.0.9-alpha.
18458 - When we can't transmit a DNS request due to a network error, retry
18459 it after a while, and eventually transmit a failing response to
18460 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
18461 - If the controller claimed responsibility for a stream, but that
18462 stream never finished making its connection, it would live
18463 forever in circuit_wait state. Now we close it after SocksTimeout
18464 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
18465 - Drop begin cells to a hidden service if they come from the middle
18466 of a circuit. Patch from lark.
18467 - When we erroneously receive two EXTEND cells for the same circuit
18468 ID on the same connection, drop the second. Patch from lark.
18469 - Fix a crash that occurs on exit nodes when a nameserver request
18470 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
18471 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
18473 - Do not assume that a stack-allocated character array will be
18474 64-bit aligned on platforms that demand that uint64_t access is
18475 aligned. Possible fix for bug 604.
18476 - Parse dates and IPv4 addresses in a locale- and libc-independent
18477 manner, to avoid platform-dependent behavior on malformed input.
18478 - Build correctly when configured to build outside the main source
18479 path. Patch from Michael Gold.
18480 - We were already rejecting relay begin cells with destination port
18481 of 0. Now also reject extend cells with destination port or address
18482 of 0. Suggested by lark.
18484 o Minor bugfixes (on 0.2.1.x):
18485 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
18486 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
18487 - If we're an exit node, scrub the IP address to which we are exiting
18488 in the logs. Bugfix on 0.2.1.8-alpha.
18491 - On Linux, use the prctl call to re-enable core dumps when the user
18493 - New controller event NEWCONSENSUS that lists the networkstatus
18494 lines for every recommended relay. Now controllers like Torflow
18495 can keep up-to-date on which relays they should be using.
18496 - Update to the "February 26 2009" ip-to-country file.
18499 Changes in version 0.2.0.34 - 2009-02-08
18500 Tor 0.2.0.34 features several more security-related fixes. You should
18501 upgrade, especially if you run an exit relay (remote crash) or a
18502 directory authority (remote infinite loop), or you're on an older
18503 (pre-XP) or not-recently-patched Windows (remote exploit).
18505 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
18506 have many known flaws, and nobody should be using them. You should
18507 upgrade. If you're using a Linux or BSD and its packages are obsolete,
18508 stop using those packages and upgrade anyway.
18511 - Fix an infinite-loop bug on handling corrupt votes under certain
18512 circumstances. Bugfix on 0.2.0.8-alpha.
18513 - Fix a temporary DoS vulnerability that could be performed by
18514 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
18515 - Avoid a potential crash on exit nodes when processing malformed
18516 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
18517 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
18518 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
18521 - Fix compilation on systems where time_t is a 64-bit integer.
18522 Patch from Matthias Drochner.
18523 - Don't consider expiring already-closed client connections. Fixes
18524 bug 893. Bugfix on 0.0.2pre20.
18527 Changes in version 0.2.1.12-alpha - 2009-02-08
18528 Tor 0.2.1.12-alpha features several more security-related fixes. You
18529 should upgrade, especially if you run an exit relay (remote crash) or
18530 a directory authority (remote infinite loop), or you're on an older
18531 (pre-XP) or not-recently-patched Windows (remote exploit). It also
18532 includes a big pile of minor bugfixes and cleanups.
18535 - Fix an infinite-loop bug on handling corrupt votes under certain
18536 circumstances. Bugfix on 0.2.0.8-alpha.
18537 - Fix a temporary DoS vulnerability that could be performed by
18538 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
18539 - Avoid a potential crash on exit nodes when processing malformed
18540 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
18543 - Let controllers actually ask for the "clients_seen" event for
18544 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
18545 reported by Matt Edman.
18546 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
18548 - Fix a bug in address parsing that was preventing bridges or hidden
18549 service targets from being at IPv6 addresses.
18550 - Solve a bug that kept hardware crypto acceleration from getting
18551 enabled when accounting was turned on. Fixes bug 907. Bugfix on
18553 - Remove a bash-ism from configure.in to build properly on non-Linux
18554 platforms. Bugfix on 0.2.1.1-alpha.
18555 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
18556 headers. Bugfix on 0.2.0.10-alpha.
18557 - Don't consider expiring already-closed client connections. Fixes
18558 bug 893. Bugfix on 0.0.2pre20.
18559 - Fix another interesting corner-case of bug 891 spotted by rovv:
18560 Previously, if two hosts had different amounts of clock drift, and
18561 one of them created a new connection with just the wrong timing,
18562 the other might decide to deprecate the new connection erroneously.
18563 Bugfix on 0.1.1.13-alpha.
18564 - Resolve a very rare crash bug that could occur when the user forced
18565 a nameserver reconfiguration during the middle of a nameserver
18566 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
18567 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
18568 Bugfix on 0.2.1.7-alpha.
18569 - If we're using bridges and our network goes away, be more willing
18570 to forgive our bridges and try again when we get an application
18571 request. Bugfix on 0.2.0.x.
18574 - Support platforms where time_t is 64 bits long. (Congratulations,
18575 NetBSD!) Patch from Matthias Drochner.
18576 - Add a 'getinfo status/clients-seen' controller command, in case
18577 controllers want to hear clients_seen events but connect late.
18580 - Disable GCC's strict alias optimization by default, to avoid the
18581 likelihood of its introducing subtle bugs whenever our code violates
18582 the letter of C99's alias rules.
18585 Changes in version 0.2.0.33 - 2009-01-21
18586 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
18587 useful to users. It also finally fixes a bug where a relay or client
18588 that's been off for many days would take a long time to bootstrap.
18590 This update also fixes an important security-related bug reported by
18591 Ilja van Sprundel. You should upgrade. (We'll send out more details
18592 about the bug once people have had some time to upgrade.)
18595 - Fix a heap-corruption bug that may be remotely triggerable on
18596 some platforms. Reported by Ilja van Sprundel.
18599 - When a stream at an exit relay is in state "resolving" or
18600 "connecting" and it receives an "end" relay cell, the exit relay
18601 would silently ignore the end cell and not close the stream. If
18602 the client never closes the circuit, then the exit relay never
18603 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
18604 reported by "wood".
18605 - When sending CREATED cells back for a given circuit, use a 64-bit
18606 connection ID to find the right connection, rather than an addr:port
18607 combination. Now that we can have multiple OR connections between
18608 the same ORs, it is no longer possible to use addr:port to uniquely
18609 identify a connection.
18610 - Bridge relays that had DirPort set to 0 would stop fetching
18611 descriptors shortly after startup, and then briefly resume
18612 after a new bandwidth test and/or after publishing a new bridge
18613 descriptor. Bridge users that try to bootstrap from them would
18614 get a recent networkstatus but would get descriptors from up to
18615 18 hours earlier, meaning most of the descriptors were obsolete
18616 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
18617 - Prevent bridge relays from serving their 'extrainfo' document
18618 to anybody who asks, now that extrainfo docs include potentially
18619 sensitive aggregated client geoip summaries. Bugfix on
18621 - If the cached networkstatus consensus is more than five days old,
18622 discard it rather than trying to use it. In theory it could be
18623 useful because it lists alternate directory mirrors, but in practice
18624 it just means we spend many minutes trying directory mirrors that
18625 are long gone from the network. Also discard router descriptors as
18626 we load them if they are more than five days old, since the onion
18627 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
18630 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
18631 could make gcc generate non-functional binary search code. Bugfix
18633 - Build correctly on platforms without socklen_t.
18634 - Compile without warnings on solaris.
18635 - Avoid potential crash on internal error during signature collection.
18636 Fixes bug 864. Patch from rovv.
18637 - Correct handling of possible malformed authority signing key
18638 certificates with internal signature types. Fixes bug 880.
18639 Bugfix on 0.2.0.3-alpha.
18640 - Fix a hard-to-trigger resource leak when logging credential status.
18642 - When we can't initialize DNS because the network is down, do not
18643 automatically stop Tor from starting. Instead, we retry failed
18644 dns_init() every 10 minutes, and change the exit policy to reject
18645 *:* until one succeeds. Fixes bug 691.
18646 - Use 64 bits instead of 32 bits for connection identifiers used with
18647 the controller protocol, to greatly reduce risk of identifier reuse.
18648 - When we're choosing an exit node for a circuit, and we have
18649 no pending streams, choose a good general exit rather than one that
18650 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
18651 - Fix another case of assuming, when a specific exit is requested,
18652 that we know more than the user about what hosts it allows.
18653 Fixes one case of bug 752. Patch from rovv.
18654 - Clip the MaxCircuitDirtiness config option to a minimum of 10
18655 seconds. Warn the user if lower values are given in the
18656 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
18657 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
18658 user if lower values are given in the configuration. Bugfix on
18659 0.1.1.17-rc. Patch by Sebastian.
18660 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
18661 the cache because we already had a v0 descriptor with the same ID.
18662 Bugfix on 0.2.0.18-alpha.
18663 - Fix a race condition when freeing keys shared between main thread
18664 and CPU workers that could result in a memory leak. Bugfix on
18665 0.1.0.1-rc. Fixes bug 889.
18666 - Send a valid END cell back when a client tries to connect to a
18667 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
18668 840. Patch from rovv.
18669 - Check which hops rendezvous stream cells are associated with to
18670 prevent possible guess-the-streamid injection attacks from
18671 intermediate hops. Fixes another case of bug 446. Based on patch
18673 - If a broken client asks a non-exit router to connect somewhere,
18674 do not even do the DNS lookup before rejecting the connection.
18675 Fixes another case of bug 619. Patch from rovv.
18676 - When a relay gets a create cell it can't decrypt (e.g. because it's
18677 using the wrong onion key), we were dropping it and letting the
18678 client time out. Now actually answer with a destroy cell. Fixes
18679 bug 904. Bugfix on 0.0.2pre8.
18681 o Minor bugfixes (hidden services):
18682 - Do not throw away existing introduction points on SIGHUP. Bugfix on
18683 0.0.6pre1. Patch by Karsten. Fixes bug 874.
18686 - Report the case where all signatures in a detached set are rejected
18687 differently than the case where there is an error handling the
18689 - When we realize that another process has modified our cached
18690 descriptors, print out a more useful error message rather than
18691 triggering an assertion. Fixes bug 885. Patch from Karsten.
18692 - Implement the 0x20 hack to better resist DNS poisoning: set the
18693 case on outgoing DNS requests randomly, and reject responses that do
18694 not match the case correctly. This logic can be disabled with the
18695 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
18696 of servers that do not reliably preserve case in replies. See
18697 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
18699 - Check DNS replies for more matching fields to better resist DNS
18701 - Never use OpenSSL compression: it wastes RAM and CPU trying to
18702 compress cells, which are basically all encrypted, compressed, or
18706 Changes in version 0.2.1.11-alpha - 2009-01-20
18707 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
18708 week it will take a long time to bootstrap again" bug. It also fixes
18709 an important security-related bug reported by Ilja van Sprundel. You
18710 should upgrade. (We'll send out more details about the bug once people
18711 have had some time to upgrade.)
18714 - Fix a heap-corruption bug that may be remotely triggerable on
18715 some platforms. Reported by Ilja van Sprundel.
18718 - Discard router descriptors as we load them if they are more than
18719 five days old. Otherwise if Tor is off for a long time and then
18720 starts with cached descriptors, it will try to use the onion
18721 keys in those obsolete descriptors when building circuits. Bugfix
18722 on 0.2.0.x. Fixes bug 887.
18725 - Try to make sure that the version of Libevent we're running with
18726 is binary-compatible with the one we built with. May address bug
18728 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
18729 for bug 905. Bugfix on 0.2.1.7-alpha.
18730 - Add a new --enable-local-appdata configuration switch to change
18731 the default location of the datadir on win32 from APPDATA to
18732 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
18733 entirely. Patch from coderman.
18736 - Make outbound DNS packets respect the OutboundBindAddress setting.
18737 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
18738 - When our circuit fails at the first hop (e.g. we get a destroy
18739 cell back), avoid using that OR connection anymore, and also
18740 tell all the one-hop directory requests waiting for it that they
18741 should fail. Bugfix on 0.2.1.3-alpha.
18742 - In the torify(1) manpage, mention that tsocks will leak your
18746 Changes in version 0.2.1.10-alpha - 2009-01-06
18747 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
18748 would make the bridge relay not so useful if it had DirPort set to 0,
18749 and one that could let an attacker learn a little bit of information
18750 about the bridge's users), and a bug that would cause your Tor relay
18751 to ignore a circuit create request it can't decrypt (rather than reply
18752 with an error). It also fixes a wide variety of other bugs.
18755 - If the cached networkstatus consensus is more than five days old,
18756 discard it rather than trying to use it. In theory it could
18757 be useful because it lists alternate directory mirrors, but in
18758 practice it just means we spend many minutes trying directory
18759 mirrors that are long gone from the network. Helps bug 887 a bit;
18761 - Bridge relays that had DirPort set to 0 would stop fetching
18762 descriptors shortly after startup, and then briefly resume
18763 after a new bandwidth test and/or after publishing a new bridge
18764 descriptor. Bridge users that try to bootstrap from them would
18765 get a recent networkstatus but would get descriptors from up to
18766 18 hours earlier, meaning most of the descriptors were obsolete
18767 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
18768 - Prevent bridge relays from serving their 'extrainfo' document
18769 to anybody who asks, now that extrainfo docs include potentially
18770 sensitive aggregated client geoip summaries. Bugfix on
18774 - New controller event "clients_seen" to report a geoip-based summary
18775 of which countries we've seen clients from recently. Now controllers
18776 like Vidalia can show bridge operators that they're actually making
18778 - Build correctly against versions of OpenSSL 0.9.8 or later built
18779 without support for deprecated functions.
18780 - Update to the "December 19 2008" ip-to-country file.
18782 o Minor bugfixes (on 0.2.0.x):
18783 - Authorities now vote for the Stable flag for any router whose
18784 weighted MTBF is at least 5 days, regardless of the mean MTBF.
18785 - Do not remove routers as too old if we do not have any consensus
18786 document. Bugfix on 0.2.0.7-alpha.
18787 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
18788 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
18789 - When an exit relay resolves a stream address to a local IP address,
18790 do not just keep retrying that same exit relay over and
18791 over. Instead, just close the stream. Addresses bug 872. Bugfix
18792 on 0.2.0.32. Patch from rovv.
18793 - If a hidden service sends us an END cell, do not consider
18794 retrying the connection; just close it. Patch from rovv.
18795 - When we made bridge authorities stop serving bridge descriptors over
18796 unencrypted links, we also broke DirPort reachability testing for
18797 bridges. So bridges with a non-zero DirPort were printing spurious
18798 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
18799 - When a relay gets a create cell it can't decrypt (e.g. because it's
18800 using the wrong onion key), we were dropping it and letting the
18801 client time out. Now actually answer with a destroy cell. Fixes
18802 bug 904. Bugfix on 0.0.2pre8.
18803 - Squeeze 2-5% out of client performance (according to oprofile) by
18804 improving the implementation of some policy-manipulation functions.
18806 o Minor bugfixes (on 0.2.1.x):
18807 - Make get_interface_address() function work properly again; stop
18808 guessing the wrong parts of our address as our address.
18809 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
18810 send on that circuit. Otherwise we might violate the proposal-110
18811 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
18813 - When we're sending non-EXTEND cells to the first hop in a circuit,
18814 for example to use an encrypted directory connection, we don't need
18815 to use RELAY_EARLY cells: the first hop knows what kind of cell
18816 it is, and nobody else can even see the cell type. Conserving
18817 RELAY_EARLY cells makes it easier to cannibalize circuits like
18819 - Stop logging nameserver addresses in reverse order.
18820 - If we are retrying a directory download slowly over and over, do
18821 not automatically give up after the 254th failure. Bugfix on
18823 - Resume reporting accurate "stream end" reasons to the local control
18824 port. They were lost in the changes for Proposal 148. Bugfix on
18827 o Deprecated and removed features:
18828 - The old "tor --version --version" command, which would print out
18829 the subversion "Id" of most of the source files, is now removed. It
18830 turned out to be less useful than we'd expected, and harder to
18833 o Code simplifications and refactoring:
18834 - Change our header file guard macros to be less likely to conflict
18835 with system headers. Adam Langley noticed that we were conflicting
18836 with log.h on Android.
18837 - Tool-assisted documentation cleanup. Nearly every function or
18838 static variable in Tor should have its own documentation now.
18841 Changes in version 0.2.1.9-alpha - 2008-12-25
18842 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
18844 o New directory authorities:
18845 - gabelmoo (the authority run by Karsten Loesing) now has a new
18849 - Never use a connection with a mismatched address to extend a
18850 circuit, unless that connection is canonical. A canonical
18851 connection is one whose address is authenticated by the router's
18852 identity key, either in a NETINFO cell or in a router descriptor.
18853 - Avoid a possible memory corruption bug when receiving hidden service
18854 descriptors. Bugfix on 0.2.1.6-alpha.
18857 - Fix a logic error that would automatically reject all but the first
18858 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
18859 part of bug 813/868. Bug spotted by coderman.
18860 - When a stream at an exit relay is in state "resolving" or
18861 "connecting" and it receives an "end" relay cell, the exit relay
18862 would silently ignore the end cell and not close the stream. If
18863 the client never closes the circuit, then the exit relay never
18864 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
18865 reported by "wood".
18866 - When we can't initialize DNS because the network is down, do not
18867 automatically stop Tor from starting. Instead, retry failed
18868 dns_init() every 10 minutes, and change the exit policy to reject
18869 *:* until one succeeds. Fixes bug 691.
18872 - Give a better error message when an overzealous init script says
18873 "sudo -u username tor --user username". Makes Bug 882 easier for
18875 - When a directory authority gives us a new guess for our IP address,
18876 log which authority we used. Hopefully this will help us debug
18877 the recent complaints about bad IP address guesses.
18878 - Detect svn revision properly when we're using git-svn.
18879 - Try not to open more than one descriptor-downloading connection
18880 to an authority at once. This should reduce load on directory
18881 authorities. Fixes bug 366.
18882 - Add cross-certification to newly generated certificates, so that
18883 a signing key is enough information to look up a certificate.
18884 Partial implementation of proposal 157.
18885 - Start serving certificates by <identity digest, signing key digest>
18886 pairs. Partial implementation of proposal 157.
18887 - Clients now never report any stream end reason except 'MISC'.
18888 Implements proposal 148.
18889 - On platforms with a maximum syslog string length, truncate syslog
18890 messages to that length ourselves, rather than relying on the
18891 system to do it for us.
18892 - Optimize out calls to time(NULL) that occur for every IO operation,
18893 or for every cell. On systems where time() is a slow syscall,
18894 this fix will be slightly helpful.
18895 - Exit servers can now answer resolve requests for ip6.arpa addresses.
18896 - When we download a descriptor that we then immediately (as
18897 a directory authority) reject, do not retry downloading it right
18898 away. Should save some bandwidth on authorities. Fix for bug
18899 888. Patch by Sebastian Hahn.
18900 - When a download gets us zero good descriptors, do not notify
18901 Tor that new directory information has arrived.
18902 - Avoid some nasty corner cases in the logic for marking connections
18903 as too old or obsolete or noncanonical for circuits. Partial
18906 o Minor features (controller):
18907 - New CONSENSUS_ARRIVED event to note when a new consensus has
18908 been fetched and validated.
18909 - When we realize that another process has modified our cached
18910 descriptors file, print out a more useful error message rather
18911 than triggering an assertion. Fixes bug 885. Patch from Karsten.
18912 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
18913 controllers to prevent SIGHUP from reloading the
18914 configuration. Fixes bug 856.
18917 - Resume using the correct "REASON=" stream when telling the
18918 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
18919 - When a canonical connection appears later in our internal list
18920 than a noncanonical one for a given OR ID, always use the
18921 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
18923 - Clip the MaxCircuitDirtiness config option to a minimum of 10
18924 seconds. Warn the user if lower values are given in the
18925 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
18926 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
18927 user if lower values are given in the configuration. Bugfix on
18928 0.1.1.17-rc. Patch by Sebastian.
18929 - Fix a race condition when freeing keys shared between main thread
18930 and CPU workers that could result in a memory leak. Bugfix on
18931 0.1.0.1-rc. Fixes bug 889.
18933 o Minor bugfixes (hidden services):
18934 - Do not throw away existing introduction points on SIGHUP (bugfix on
18935 0.0.6pre1); also, do not stall hidden services because we're
18936 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
18937 by John Brooks. Patch by Karsten. Fixes bug 874.
18938 - Fix a memory leak when we decline to add a v2 rendezvous
18939 descriptor to the cache because we already had a v0 descriptor
18940 with the same ID. Bugfix on 0.2.0.18-alpha.
18942 o Deprecated and removed features:
18943 - RedirectExits has been removed. It was deprecated since
18945 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
18946 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
18947 - Cell pools are now always enabled; --disable-cell-pools is ignored.
18949 o Code simplifications and refactoring:
18950 - Rename the confusing or_is_obsolete field to the more appropriate
18951 is_bad_for_new_circs, and move it to or_connection_t where it
18953 - Move edge-only flags from connection_t to edge_connection_t: not
18954 only is this better coding, but on machines of plausible alignment,
18955 it should save 4-8 bytes per connection_t. "Every little bit helps."
18956 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
18957 for consistency; keep old option working for backward compatibility.
18958 - Simplify the code for finding connections to use for a circuit.
18961 Changes in version 0.2.1.8-alpha - 2008-12-08
18962 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
18963 builds better on unusual platforms like Solaris and old OS X, and
18964 fixes a variety of other issues.
18967 - New DirPortFrontPage option that takes an html file and publishes
18968 it as "/" on the DirPort. Now relay operators can provide a
18969 disclaimer without needing to set up a separate webserver. There's
18970 a sample disclaimer in contrib/tor-exit-notice.html.
18973 - When the client is choosing entry guards, now it selects at most
18974 one guard from a given relay family. Otherwise we could end up with
18975 all of our entry points into the network run by the same operator.
18976 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
18979 - Fix a DOS opportunity during the voting signature collection process
18980 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
18981 - Fix a possible segfault when establishing an exit connection. Bugfix
18985 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
18987 - Made Tor a little less aggressive about deleting expired
18988 certificates. Partial fix for bug 854.
18989 - Stop doing unaligned memory access that generated bus errors on
18990 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
18991 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
18992 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
18993 - Make USR2 log-level switch take effect immediately. Bugfix on
18995 - If one win32 nameserver fails to get added, continue adding the
18996 rest, and don't automatically fail.
18997 - Use fcntl() for locking when flock() is not available. Should fix
18998 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
18999 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
19000 could make gcc generate non-functional binary search code. Bugfix
19002 - Build correctly on platforms without socklen_t.
19003 - Avoid potential crash on internal error during signature collection.
19004 Fixes bug 864. Patch from rovv.
19005 - Do not use C's stdio library for writing to log files. This will
19006 improve logging performance by a minute amount, and will stop
19007 leaking fds when our disk is full. Fixes bug 861.
19008 - Stop erroneous use of O_APPEND in cases where we did not in fact
19009 want to re-seek to the end of a file before every last write().
19010 - Correct handling of possible malformed authority signing key
19011 certificates with internal signature types. Fixes bug 880. Bugfix
19013 - Fix a hard-to-trigger resource leak when logging credential status.
19017 - Directory mirrors no longer fetch the v1 directory or
19018 running-routers files. They are obsolete, and nobody asks for them
19019 anymore. This is the first step to making v1 authorities obsolete.
19021 o Minor features (controller):
19022 - Return circuit purposes in response to GETINFO circuit-status. Fixes
19026 Changes in version 0.2.0.32 - 2008-11-20
19027 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
19028 packages (and maybe other packages) noticed by Theo de Raadt, fixes
19029 a smaller security flaw that might allow an attacker to access local
19030 services, further improves hidden service performance, and fixes a
19031 variety of other issues.
19034 - The "User" and "Group" config options did not clear the
19035 supplementary group entries for the Tor process. The "User" option
19036 is now more robust, and we now set the groups to the specified
19037 user's primary group. The "Group" option is now ignored. For more
19038 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
19039 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
19040 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
19041 - The "ClientDNSRejectInternalAddresses" config option wasn't being
19042 consistently obeyed: if an exit relay refuses a stream because its
19043 exit policy doesn't allow it, we would remember what IP address
19044 the relay said the destination address resolves to, even if it's
19045 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
19048 - Fix a DOS opportunity during the voting signature collection process
19049 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
19051 o Major bugfixes (hidden services):
19052 - When fetching v0 and v2 rendezvous service descriptors in parallel,
19053 we were failing the whole hidden service request when the v0
19054 descriptor fetch fails, even if the v2 fetch is still pending and
19055 might succeed. Similarly, if the last v2 fetch fails, we were
19056 failing the whole hidden service request even if a v0 fetch is
19057 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
19058 - When extending a circuit to a hidden service directory to upload a
19059 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
19060 requests failed, because the router descriptor has not been
19061 downloaded yet. In these cases, do not attempt to upload the
19062 rendezvous descriptor, but wait until the router descriptor is
19063 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
19064 descriptor from a hidden service directory for which the router
19065 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
19069 - Fix several infrequent memory leaks spotted by Coverity.
19070 - When testing for libevent functions, set the LDFLAGS variable
19071 correctly. Found by Riastradh.
19072 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
19073 bootstrapping with tunneled directory connections. Bugfix on
19074 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
19075 - When asked to connect to A.B.exit:80, if we don't know the IP for A
19076 and we know that server B rejects most-but-not all connections to
19077 port 80, we would previously reject the connection. Now, we assume
19078 the user knows what they were asking for. Fixes bug 752. Bugfix
19079 on 0.0.9rc5. Diagnosed by BarkerJr.
19080 - If we overrun our per-second write limits a little, count this as
19081 having used up our write allocation for the second, and choke
19082 outgoing directory writes. Previously, we had only counted this when
19083 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
19084 Bugfix on 0.2.0.x (??).
19085 - Remove the old v2 directory authority 'lefkada' from the default
19086 list. It has been gone for many months.
19087 - Stop doing unaligned memory access that generated bus errors on
19088 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
19089 - Make USR2 log-level switch take effect immediately. Bugfix on
19092 o Minor bugfixes (controller):
19093 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
19094 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
19097 Changes in version 0.2.1.7-alpha - 2008-11-08
19098 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
19099 packages (and maybe other packages) noticed by Theo de Raadt, fixes
19100 a smaller security flaw that might allow an attacker to access local
19101 services, adds better defense against DNS poisoning attacks on exit
19102 relays, further improves hidden service performance, and fixes a
19103 variety of other issues.
19106 - The "ClientDNSRejectInternalAddresses" config option wasn't being
19107 consistently obeyed: if an exit relay refuses a stream because its
19108 exit policy doesn't allow it, we would remember what IP address
19109 the relay said the destination address resolves to, even if it's
19110 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
19111 - The "User" and "Group" config options did not clear the
19112 supplementary group entries for the Tor process. The "User" option
19113 is now more robust, and we now set the groups to the specified
19114 user's primary group. The "Group" option is now ignored. For more
19115 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
19116 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
19117 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
19118 - Do not use or believe expired v3 authority certificates. Patch
19119 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
19122 - Now NodeFamily and MyFamily config options allow spaces in
19123 identity fingerprints, so it's easier to paste them in.
19124 Suggested by Lucky Green.
19125 - Implement the 0x20 hack to better resist DNS poisoning: set the
19126 case on outgoing DNS requests randomly, and reject responses that do
19127 not match the case correctly. This logic can be disabled with the
19128 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
19129 of servers that do not reliably preserve case in replies. See
19130 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
19132 - Preserve case in replies to DNSPort requests in order to support
19133 the 0x20 hack for resisting DNS poisoning attacks.
19135 o Hidden service performance improvements:
19136 - When the client launches an introduction circuit, retry with a
19137 new circuit after 30 seconds rather than 60 seconds.
19138 - Launch a second client-side introduction circuit in parallel
19139 after a delay of 15 seconds (based on work by Christian Wilms).
19140 - Hidden services start out building five intro circuits rather
19141 than three, and when the first three finish they publish a service
19142 descriptor using those. Now we publish our service descriptor much
19143 faster after restart.
19146 - Minor fix in the warning messages when you're having problems
19147 bootstrapping; also, be more forgiving of bootstrap problems when
19148 we're still making incremental progress on a given bootstrap phase.
19149 - When we're choosing an exit node for a circuit, and we have
19150 no pending streams, choose a good general exit rather than one that
19151 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
19152 - Send a valid END cell back when a client tries to connect to a
19153 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
19154 840. Patch from rovv.
19155 - If a broken client asks a non-exit router to connect somewhere,
19156 do not even do the DNS lookup before rejecting the connection.
19157 Fixes another case of bug 619. Patch from rovv.
19158 - Fix another case of assuming, when a specific exit is requested,
19159 that we know more than the user about what hosts it allows.
19160 Fixes another case of bug 752. Patch from rovv.
19161 - Check which hops rendezvous stream cells are associated with to
19162 prevent possible guess-the-streamid injection attacks from
19163 intermediate hops. Fixes another case of bug 446. Based on patch
19165 - Avoid using a negative right-shift when comparing 32-bit
19166 addresses. Possible fix for bug 845 and bug 811.
19167 - Make the assert_circuit_ok() function work correctly on circuits that
19168 have already been marked for close.
19169 - Fix read-off-the-end-of-string error in unit tests when decoding
19170 introduction points.
19171 - Fix uninitialized size field for memory area allocation: may improve
19172 memory performance during directory parsing.
19173 - Treat duplicate certificate fetches as failures, so that we do
19174 not try to re-fetch an expired certificate over and over and over.
19175 - Do not say we're fetching a certificate when we'll in fact skip it
19176 because of a pending download.
19179 Changes in version 0.2.1.6-alpha - 2008-09-30
19180 Tor 0.2.1.6-alpha further improves performance and robustness of
19181 hidden services, starts work on supporting per-country relay selection,
19182 and fixes a variety of smaller issues.
19185 - Implement proposal 121: make it possible to build hidden services
19186 that only certain clients are allowed to connect to. This is
19187 enforced at several points, so that unauthorized clients are unable
19188 to send INTRODUCE cells to the service, or even (depending on the
19189 type of authentication) to learn introduction points. This feature
19190 raises the bar for certain kinds of active attacks against hidden
19191 services. Code by Karsten Loesing.
19192 - Relays now store and serve v2 hidden service descriptors by default,
19193 i.e., the new default value for HidServDirectoryV2 is 1. This is
19194 the last step in proposal 114, which aims to make hidden service
19195 lookups more reliable.
19196 - Start work to allow node restrictions to include country codes. The
19197 syntax to exclude nodes in a country with country code XX is
19198 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
19199 refinement to decide what config options should take priority if
19200 you ask to both use a particular node and exclude it.
19201 - Allow ExitNodes list to include IP ranges and country codes, just
19202 like the Exclude*Nodes lists. Patch from Robert Hogan.
19205 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
19206 Tor to fail to start if you had it configured to use a bridge
19207 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
19208 - When extending a circuit to a hidden service directory to upload a
19209 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
19210 requests failed, because the router descriptor had not been
19211 downloaded yet. In these cases, we now wait until the router
19212 descriptor is downloaded, and then retry. Likewise, clients
19213 now skip over a hidden service directory if they don't yet have
19214 its router descriptor, rather than futilely requesting it and
19215 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
19217 - When fetching v0 and v2 rendezvous service descriptors in parallel,
19218 we were failing the whole hidden service request when the v0
19219 descriptor fetch fails, even if the v2 fetch is still pending and
19220 might succeed. Similarly, if the last v2 fetch fails, we were
19221 failing the whole hidden service request even if a v0 fetch is
19222 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
19223 - DNS replies need to have names matching their requests, but
19224 these names should be in the questions section, not necessarily
19225 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
19228 - Update to the "September 1 2008" ip-to-country file.
19229 - Allow ports 465 and 587 in the default exit policy again. We had
19230 rejected them in 0.1.0.15, because back in 2005 they were commonly
19231 misconfigured and ended up as spam targets. We hear they are better
19232 locked down these days.
19233 - Use a lockfile to make sure that two Tor processes are not
19234 simultaneously running with the same datadir.
19235 - Serve the latest v3 networkstatus consensus via the control
19236 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
19237 - Better logging about stability/reliability calculations on directory
19239 - Drop the requirement to have an open dir port for storing and
19240 serving v2 hidden service descriptors.
19241 - Directory authorities now serve a /tor/dbg-stability.txt URL to
19242 help debug WFU and MTBF calculations.
19243 - Implement most of Proposal 152: allow specialized servers to permit
19244 single-hop circuits, and clients to use those servers to build
19245 single-hop circuits when using a specialized controller. Patch
19246 from Josh Albrecht. Resolves feature request 768.
19247 - Add a -p option to tor-resolve for specifying the SOCKS port: some
19248 people find host:port too confusing.
19249 - Make TrackHostExit mappings expire a while after their last use, not
19250 after their creation. Patch from Robert Hogan.
19251 - Provide circuit purposes along with circuit events to the controller.
19254 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
19256 - Fixed some memory leaks -- some quite frequent, some almost
19257 impossible to trigger -- based on results from Coverity.
19258 - When testing for libevent functions, set the LDFLAGS variable
19259 correctly. Found by Riastradh.
19260 - Fix an assertion bug in parsing policy-related options; possible fix
19262 - Catch and report a few more bootstrapping failure cases when Tor
19263 fails to establish a TCP connection. Cleanup on 0.2.1.x.
19264 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
19265 bootstrapping with tunneled directory connections. Bugfix on
19266 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
19267 - When asked to connect to A.B.exit:80, if we don't know the IP for A
19268 and we know that server B rejects most-but-not all connections to
19269 port 80, we would previously reject the connection. Now, we assume
19270 the user knows what they were asking for. Fixes bug 752. Bugfix
19271 on 0.0.9rc5. Diagnosed by BarkerJr.
19272 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
19273 service directories if they have no advertised dir port. Bugfix
19275 - If we overrun our per-second write limits a little, count this as
19276 having used up our write allocation for the second, and choke
19277 outgoing directory writes. Previously, we had only counted this when
19278 we had met our limits precisely. Fixes bug 824. Patch by rovv.
19279 Bugfix on 0.2.0.x (??).
19280 - Avoid a "0 divided by 0" calculation when calculating router uptime
19281 at directory authorities. Bugfix on 0.2.0.8-alpha.
19282 - Make DNS resolved controller events into "CLOSED", not
19283 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
19285 - Fix a bug where an unreachable relay would establish enough
19286 reachability testing circuits to do a bandwidth test -- if
19287 we already have a connection to the middle hop of the testing
19288 circuit, then it could establish the last hop by using the existing
19289 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
19290 circuits no longer use entry guards in 0.2.1.3-alpha.
19291 - If we have correct permissions on $datadir, we complain to stdout
19292 and fail to start. But dangerous permissions on
19293 $datadir/cached-status/ would cause us to open a log and complain
19294 there. Now complain to stdout and fail to start in both cases. Fixes
19295 bug 820, reported by seeess.
19296 - Remove the old v2 directory authority 'lefkada' from the default
19297 list. It has been gone for many months.
19299 o Code simplifications and refactoring:
19300 - Revise the connection_new functions so that a more typesafe variant
19301 exists. This will work better with Coverity, and let us find any
19302 actual mistakes we're making here.
19303 - Refactor unit testing logic so that dmalloc can be used sensibly
19304 with unit tests to check for memory leaks.
19305 - Move all hidden-service related fields from connection and circuit
19306 structure to substructures: this way they won't eat so much memory.
19309 Changes in version 0.2.0.31 - 2008-09-03
19310 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
19311 a big bug we're seeing where in rare cases traffic from one Tor stream
19312 gets mixed into another stream, and fixes a variety of smaller issues.
19315 - Make sure that two circuits can never exist on the same connection
19316 with the same circuit ID, even if one is marked for close. This
19317 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
19318 - Relays now reject risky extend cells: if the extend cell includes
19319 a digest of all zeroes, or asks to extend back to the relay that
19320 sent the extend cell, tear down the circuit. Ideas suggested
19322 - If not enough of our entry guards are available so we add a new
19323 one, we might use the new one even if it overlapped with the
19324 current circuit's exit relay (or its family). Anonymity bugfix
19325 pointed out by rovv.
19328 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
19329 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
19330 - Correctly detect the presence of the linux/netfilter_ipv4.h header
19331 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
19332 - Pick size of default geoip filename string correctly on windows.
19333 Fixes bug 806. Bugfix on 0.2.0.30.
19334 - Make the autoconf script accept the obsolete --with-ssl-dir
19335 option as an alias for the actually-working --with-openssl-dir
19336 option. Fix the help documentation to recommend --with-openssl-dir.
19337 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
19338 - When using the TransPort option on OpenBSD, and using the User
19339 option to change UID and drop privileges, make sure to open
19340 /dev/pf before dropping privileges. Fixes bug 782. Patch from
19341 Christopher Davis. Bugfix on 0.1.2.1-alpha.
19342 - Try to attach connections immediately upon receiving a RENDEZVOUS2
19343 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
19344 on the client side when connecting to a hidden service. Bugfix
19345 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
19346 - When closing an application-side connection because its circuit is
19347 getting torn down, generate the stream event correctly. Bugfix on
19348 0.1.2.x. Anonymous patch.
19351 Changes in version 0.2.1.5-alpha - 2008-08-31
19352 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
19353 in a lot of the infrastructure for adding authorization to hidden
19354 services, lays the groundwork for having clients read their load
19355 balancing information out of the networkstatus consensus rather than
19356 the individual router descriptors, addresses two potential anonymity
19357 issues, and fixes a variety of smaller issues.
19360 - Convert many internal address representations to optionally hold
19362 - Generate and accept IPv6 addresses in many protocol elements.
19363 - Make resolver code handle nameservers located at ipv6 addresses.
19364 - Begin implementation of proposal 121 ("Client authorization for
19365 hidden services"): configure hidden services with client
19366 authorization, publish descriptors for them, and configure
19367 authorization data for hidden services at clients. The next
19368 step is to actually access hidden services that perform client
19370 - More progress toward proposal 141: Network status consensus
19371 documents and votes now contain bandwidth information for each
19372 router and a summary of that router's exit policy. Eventually this
19373 will be used by clients so that they do not have to download every
19374 known descriptor before building circuits.
19376 o Major bugfixes (on 0.2.0.x and before):
19377 - When sending CREATED cells back for a given circuit, use a 64-bit
19378 connection ID to find the right connection, rather than an addr:port
19379 combination. Now that we can have multiple OR connections between
19380 the same ORs, it is no longer possible to use addr:port to uniquely
19381 identify a connection.
19382 - Relays now reject risky extend cells: if the extend cell includes
19383 a digest of all zeroes, or asks to extend back to the relay that
19384 sent the extend cell, tear down the circuit. Ideas suggested
19386 - If not enough of our entry guards are available so we add a new
19387 one, we might use the new one even if it overlapped with the
19388 current circuit's exit relay (or its family). Anonymity bugfix
19389 pointed out by rovv.
19392 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
19393 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
19394 - When using the TransPort option on OpenBSD, and using the User
19395 option to change UID and drop privileges, make sure to open /dev/pf
19396 before dropping privileges. Fixes bug 782. Patch from Christopher
19397 Davis. Bugfix on 0.1.2.1-alpha.
19398 - Correctly detect the presence of the linux/netfilter_ipv4.h header
19399 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
19400 - Add a missing safe_str() call for a debug log message.
19401 - Use 64 bits instead of 32 bits for connection identifiers used with
19402 the controller protocol, to greatly reduce risk of identifier reuse.
19403 - Make the autoconf script accept the obsolete --with-ssl-dir
19404 option as an alias for the actually-working --with-openssl-dir
19405 option. Fix the help documentation to recommend --with-openssl-dir.
19406 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
19409 - Rate-limit too-many-sockets messages: when they happen, they happen
19410 a lot. Resolves bug 748.
19411 - Resist DNS poisoning a little better by making sure that names in
19412 answer sections match.
19413 - Print the SOCKS5 error message string as well as the error code
19414 when a tor-resolve request fails. Patch from Jacob.
19417 Changes in version 0.2.1.4-alpha - 2008-08-04
19418 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
19421 - The address part of exit policies was not correctly written
19422 to router descriptors. This generated router descriptors that failed
19423 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
19425 - Tor triggered a false assert when extending a circuit to a relay
19426 but we already have a connection open to that relay. Noticed by
19427 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
19430 - Fix a hidden service logging bug: in some edge cases, the router
19431 descriptor of a previously picked introduction point becomes
19432 obsolete and we need to give up on it rather than continually
19433 complaining that it has become obsolete. Observed by xiando. Bugfix
19436 o Removed features:
19437 - Take out the TestVia config option, since it was a workaround for
19438 a bug that was fixed in Tor 0.1.1.21.
19441 Changes in version 0.2.1.3-alpha - 2008-08-03
19442 Tor 0.2.1.3-alpha implements most of the pieces to prevent
19443 infinite-length circuit attacks (see proposal 110); fixes a bug that
19444 might cause exit relays to corrupt streams they send back; allows
19445 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
19446 ExcludeExitNodes config options; and fixes a big pile of bugs.
19448 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
19449 - Send a bootstrap problem "warn" event on the first problem if the
19450 reason is NO_ROUTE (that is, our network is down).
19453 - Implement most of proposal 110: The first K cells to be sent
19454 along a circuit are marked as special "early" cells; only K "early"
19455 cells will be allowed. Once this code is universal, we can block
19456 certain kinds of DOS attack by requiring that EXTEND commands must
19457 be sent using an "early" cell.
19460 - Try to attach connections immediately upon receiving a RENDEZVOUS2
19461 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
19462 on the client side when connecting to a hidden service. Bugfix
19463 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
19464 - Ensure that two circuits can never exist on the same connection
19465 with the same circuit ID, even if one is marked for close. This
19466 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
19469 - When relays do their initial bandwidth measurement, don't limit
19470 to just our entry guards for the test circuits. Otherwise we tend
19471 to have multiple test circuits going through a single entry guard,
19472 which makes our bandwidth test less accurate. Fixes part of bug 654;
19473 patch contributed by Josh Albrecht.
19474 - Add an ExcludeExitNodes option so users can list a set of nodes
19475 that should be be excluded from the exit node position, but
19476 allowed elsewhere. Implements proposal 151.
19477 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
19478 ExcludeNodes and ExcludeExitNodes lists.
19479 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
19480 be more efficient. Formerly it was quadratic in the number of
19481 servers; now it should be linear. Fixes bug 509.
19482 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
19483 and n_conn_id_digest fields into a separate structure that's
19484 only needed when the circuit has not yet attached to an n_conn.
19487 - Change the contrib/tor.logrotate script so it makes the new
19488 logs as "_tor:_tor" rather than the default, which is generally
19489 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
19490 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
19491 warnings (occasionally), but it can also cause the compiler to
19492 eliminate error-checking code. Suggested by Peter Gutmann.
19493 - When a hidden service is giving up on an introduction point candidate
19494 that was not included in the last published rendezvous descriptor,
19495 don't reschedule publication of the next descriptor. Fixes bug 763.
19497 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
19498 HiddenServiceExcludeNodes as obsolete: they never worked properly,
19499 and nobody claims to be using them. Fixes bug 754. Bugfix on
19500 0.1.0.1-rc. Patch from Christian Wilms.
19501 - Fix a small alignment and memory-wasting bug on buffer chunks.
19504 o Minor bugfixes (controller):
19505 - When closing an application-side connection because its circuit
19506 is getting torn down, generate the stream event correctly.
19507 Bugfix on 0.1.2.x. Anonymous patch.
19509 o Removed features:
19510 - Remove all backward-compatibility code to support relays running
19511 versions of Tor so old that they no longer work at all on the
19515 Changes in version 0.2.0.30 - 2008-07-15
19517 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
19518 warnings (occasionally), but it can also cause the compiler to
19519 eliminate error-checking code. Suggested by Peter Gutmann.
19522 Changes in version 0.2.0.29-rc - 2008-07-08
19523 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
19524 hidden-service performance bugs, and fixes a bunch of smaller bugs.
19527 - If you have more than one bridge but don't know their keys,
19528 you would only launch a request for the descriptor of the first one
19529 on your list. (Tor considered launching requests for the others, but
19530 found that it already had a connection on the way for $0000...0000
19531 so it didn't open another.) Bugfix on 0.2.0.x.
19532 - If you have more than one bridge but don't know their keys, and the
19533 connection to one of the bridges failed, you would cancel all
19534 pending bridge connections. (After all, they all have the same
19535 digest.) Bugfix on 0.2.0.x.
19536 - When a hidden service was trying to establish an introduction point,
19537 and Tor had built circuits preemptively for such purposes, we
19538 were ignoring all the preemptive circuits and launching a new one
19539 instead. Bugfix on 0.2.0.14-alpha.
19540 - When a hidden service was trying to establish an introduction point,
19541 and Tor *did* manage to reuse one of the preemptively built
19542 circuits, it didn't correctly remember which one it used,
19543 so it asked for another one soon after, until there were no
19544 more preemptive circuits, at which point it launched one from
19545 scratch. Bugfix on 0.0.9.x.
19546 - Make directory servers include the X-Your-Address-Is: http header in
19547 their responses even for begin_dir conns. Now clients who only
19548 ever use begin_dir connections still have a way to learn their IP
19549 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
19552 - Fix a macro/CPP interaction that was confusing some compilers:
19553 some GCCs don't like #if/#endif pairs inside macro arguments.
19555 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
19556 Fixes bug 704; fix from Steven Murdoch.
19557 - When opening /dev/null in finish_daemonize(), do not pass the
19558 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
19559 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
19560 - Correctly detect transparent proxy support on Linux hosts that
19561 require in.h to be included before netfilter_ipv4.h. Patch
19563 - Disallow session resumption attempts during the renegotiation
19564 stage of the v2 handshake protocol. Clients should never be trying
19565 session resumption at this point, but apparently some did, in
19566 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
19567 found by Geoff Goodell.
19570 Changes in version 0.2.1.2-alpha - 2008-06-20
19571 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
19572 make it easier to set up your own private Tor network; fixes several
19573 big bugs with using more than one bridge relay; fixes a big bug with
19574 offering hidden services quickly after Tor starts; and uses a better
19575 API for reporting potential bootstrapping problems to the controller.
19578 - New TestingTorNetwork config option to allow adjustment of
19579 previously constant values that, while reasonable, could slow
19580 bootstrapping. Implements proposal 135. Patch from Karsten.
19583 - If you have more than one bridge but don't know their digests,
19584 you would only learn a request for the descriptor of the first one
19585 on your list. (Tor considered launching requests for the others, but
19586 found that it already had a connection on the way for $0000...0000
19587 so it didn't open another.) Bugfix on 0.2.0.x.
19588 - If you have more than one bridge but don't know their digests,
19589 and the connection to one of the bridges failed, you would cancel
19590 all pending bridge connections. (After all, they all have the
19591 same digest.) Bugfix on 0.2.0.x.
19592 - When establishing a hidden service, introduction points that
19593 originate from cannibalized circuits are completely ignored and not
19594 included in rendezvous service descriptors. This might be another
19595 reason for delay in making a hidden service available. Bugfix
19596 from long ago (0.0.9.x?)
19599 - Allow OpenSSL to use dynamic locks if it wants.
19600 - When building a consensus, do not include routers that are down.
19601 This will cut down 30% to 40% on consensus size. Implements
19603 - In directory authorities' approved-routers files, allow
19604 fingerprints with or without space.
19605 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
19606 controller can query our current bootstrap state in case it attaches
19607 partway through and wants to catch up.
19608 - Send an initial "Starting" bootstrap status event, so we have a
19609 state to start out in.
19612 - Asking for a conditional consensus at .../consensus/<fingerprints>
19613 would crash a dirserver if it did not already have a
19614 consensus. Bugfix on 0.2.1.1-alpha.
19615 - Clean up some macro/CPP interactions: some GCC versions don't like
19616 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
19619 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
19620 - Directory authorities shouldn't complain about bootstrapping
19621 problems just because they do a lot of reachability testing and
19622 some of the connection attempts fail.
19623 - Start sending "count" and "recommendation" key/value pairs in
19624 bootstrap problem status events, so the controller can hear about
19625 problems even before Tor decides they're worth reporting for sure.
19626 - If you're using bridges, generate "bootstrap problem" warnings
19627 as soon as you run out of working bridges, rather than waiting
19628 for ten failures -- which will never happen if you have less than
19630 - If we close our OR connection because there's been a circuit
19631 pending on it for too long, we were telling our bootstrap status
19632 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
19635 Changes in version 0.2.1.1-alpha - 2008-06-13
19636 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
19637 were making the Tor process bloat especially on Linux; makes our TLS
19638 handshake blend in better; sends "bootstrap phase" status events to
19639 the controller, so it can keep the user informed of progress (and
19640 problems) fetching directory information and establishing circuits;
19641 and adds a variety of smaller features.
19644 - More work on making our TLS handshake blend in: modify the list
19645 of ciphers advertised by OpenSSL in client mode to even more
19646 closely resemble a common web browser. We cheat a little so that
19647 we can advertise ciphers that the locally installed OpenSSL doesn't
19649 - Start sending "bootstrap phase" status events to the controller,
19650 so it can keep the user informed of progress fetching directory
19651 information and establishing circuits. Also inform the controller
19652 if we think we're stuck at a particular bootstrap phase. Implements
19654 - Resume using OpenSSL's RAND_poll() for better (and more portable)
19655 cross-platform entropy collection again. We used to use it, then
19656 stopped using it because of a bug that could crash systems that
19657 called RAND_poll when they had a lot of fds open. It looks like the
19658 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
19659 at startup, and to call RAND_poll() when we reseed later only if
19660 we have a non-buggy OpenSSL version.
19663 - When we choose to abandon a new entry guard because we think our
19664 older ones might be better, close any circuits pending on that
19665 new entry guard connection. This fix should make us recover much
19666 faster when our network is down and then comes back. Bugfix on
19667 0.1.2.8-beta; found by lodger.
19669 o Memory fixes and improvements:
19670 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
19671 to avoid unused RAM in buffer chunks and memory pools.
19672 - Speed up parsing and cut down on memory fragmentation by using
19673 stack-style allocations for parsing directory objects. Previously,
19674 this accounted for over 40% of allocations from within Tor's code
19675 on a typical directory cache.
19676 - Use a Bloom filter rather than a digest-based set to track which
19677 descriptors we need to keep around when we're cleaning out old
19678 router descriptors. This speeds up the computation significantly,
19679 and may reduce fragmentation.
19680 - Reduce the default smartlist size from 32 to 16; it turns out that
19681 most smartlists hold around 8-12 elements tops.
19682 - Make dumpstats() log the fullness and size of openssl-internal
19684 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
19685 patch to their OpenSSL, turn it on to save memory on servers. This
19686 patch will (with any luck) get included in a mainline distribution
19688 - Never use OpenSSL compression: it wastes RAM and CPU trying to
19689 compress cells, which are basically all encrypted, compressed,
19693 - Stop reloading the router list from disk for no reason when we
19694 run out of reachable directory mirrors. Once upon a time reloading
19695 it would set the 'is_running' flag back to 1 for them. It hasn't
19696 done that for a long time.
19697 - In very rare situations new hidden service descriptors were
19698 published earlier than 30 seconds after the last change to the
19699 service. (We currently think that a hidden service descriptor
19700 that's been stable for 30 seconds is worth publishing.)
19703 - Allow separate log levels to be configured for different logging
19704 domains. For example, this allows one to log all notices, warnings,
19705 or errors, plus all memory management messages of level debug or
19706 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
19707 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
19708 and stop using a warning that had become unfixably verbose under
19710 - New --hush command-line option similar to --quiet. While --quiet
19711 disables all logging to the console on startup, --hush limits the
19712 output to messages of warning and error severity.
19713 - Servers support a new URL scheme for consensus downloads that
19714 allows the client to specify which authorities are trusted.
19715 The server then only sends the consensus if the client will trust
19716 it. Otherwise a 404 error is sent back. Clients use this
19717 new scheme when the server supports it (meaning it's running
19718 0.2.1.1-alpha or later). Implements proposal 134.
19719 - New configure/torrc options (--enable-geoip-stats,
19720 DirRecordUsageByCountry) to record how many IPs we've served
19721 directory info to in each country code, how many status documents
19722 total we've sent to each country code, and what share of the total
19723 directory requests we should expect to see.
19724 - Use the TLS1 hostname extension to more closely resemble browser
19726 - Lots of new unit tests.
19727 - Add a macro to implement the common pattern of iterating through
19728 two parallel lists in lockstep.
19731 Changes in version 0.2.0.28-rc - 2008-06-13
19732 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
19733 performance bug, and fixes a bunch of smaller bugs.
19736 - Fix a bug where, when we were choosing the 'end stream reason' to
19737 put in our relay end cell that we send to the exit relay, Tor
19738 clients on Windows were sometimes sending the wrong 'reason'. The
19739 anonymity problem is that exit relays may be able to guess whether
19740 the client is running Windows, thus helping partition the anonymity
19741 set. Down the road we should stop sending reasons to exit relays,
19742 or otherwise prevent future versions of this bug.
19745 - While setting up a hidden service, some valid introduction circuits
19746 were overlooked and abandoned. This might be the reason for
19747 the long delay in making a hidden service available. Bugfix on
19751 - Update to the "June 9 2008" ip-to-country file.
19752 - Run 'make test' as part of 'make dist', so we stop releasing so
19753 many development snapshots that fail their unit tests.
19756 - When we're checking if we have enough dir info for each relay
19757 to begin establishing circuits, make sure that we actually have
19758 the descriptor listed in the consensus, not just any descriptor.
19760 - Bridge relays no longer print "xx=0" in their extrainfo document
19761 for every single country code in the geoip db. Bugfix on
19763 - Only warn when we fail to load the geoip file if we were planning to
19764 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
19765 - If we change our MaxAdvertisedBandwidth and then reload torrc,
19766 Tor won't realize it should publish a new relay descriptor. Fixes
19767 bug 688, reported by mfr. Bugfix on 0.1.2.x.
19768 - When we haven't had any application requests lately, don't bother
19769 logging that we have expired a bunch of descriptors. Bugfix
19771 - Make relay cells written on a connection count as non-padding when
19772 tracking how long a connection has been in use. Bugfix on
19773 0.2.0.1-alpha. Spotted by lodger.
19774 - Fix unit tests in 0.2.0.27-rc.
19775 - Fix compile on Windows.
19778 Changes in version 0.2.0.27-rc - 2008-06-03
19779 Tor 0.2.0.27-rc adds a few features we left out of the earlier
19780 release candidates. In particular, we now include an IP-to-country
19781 GeoIP database, so controllers can easily look up what country a
19782 given relay is in, and so bridge relays can give us some sanitized
19783 summaries about which countries are making use of bridges. (See proposal
19784 126-geoip-fetching.txt for details.)
19787 - Include an IP-to-country GeoIP file in the tarball, so bridge
19788 relays can report sanitized summaries of the usage they're seeing.
19791 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
19792 Robert Hogan. Fixes the first part of bug 681.
19793 - Make bridge authorities never serve extrainfo docs.
19794 - Add support to detect Libevent versions in the 1.4.x series
19796 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
19797 - Include a new contrib/tor-exit-notice.html file that exit relay
19798 operators can put on their website to help reduce abuse queries.
19801 - When tunneling an encrypted directory connection, and its first
19802 circuit fails, do not leave it unattached and ask the controller
19803 to deal. Fixes the second part of bug 681.
19804 - Make bridge authorities correctly expire old extrainfo documents
19808 Changes in version 0.2.0.26-rc - 2008-05-13
19809 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
19810 in Debian's OpenSSL packages. All users running any 0.2.0.x version
19811 should upgrade, whether they're running Debian or not.
19813 o Major security fixes:
19814 - Use new V3 directory authority keys on the tor26, gabelmoo, and
19815 moria1 V3 directory authorities. The old keys were generated with
19816 a vulnerable version of Debian's OpenSSL package, and must be
19817 considered compromised. Other authorities' keys were not generated
19818 with an affected version of OpenSSL.
19821 - List authority signatures as "unrecognized" based on DirServer
19822 lines, not on cert cache. Bugfix on 0.2.0.x.
19825 - Add a new V3AuthUseLegacyKey option to make it easier for
19826 authorities to change their identity keys if they have to.
19829 Changes in version 0.2.0.25-rc - 2008-04-23
19830 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
19833 - Remember to initialize threading before initializing logging.
19834 Otherwise, many BSD-family implementations will crash hard on
19835 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
19838 - Authorities correctly free policies on bad servers on
19839 exit. Fixes bug 672. Bugfix on 0.2.0.x.
19842 Changes in version 0.2.0.24-rc - 2008-04-22
19843 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
19844 v3 directory authority, makes relays with dynamic IP addresses and no
19845 DirPort notice more quickly when their IP address changes, fixes a few
19846 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
19848 o New directory authorities:
19849 - Take lefkada out of the list of v3 directory authorities, since
19850 it has been down for months.
19851 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
19855 - Detect address changes more quickly on non-directory mirror
19856 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
19858 o Minor features (security):
19859 - Reject requests for reverse-dns lookup of names that are in
19860 a private address space. Patch from lodger.
19861 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
19864 o Minor bugfixes (crashes):
19865 - Avoid a rare assert that can trigger when Tor doesn't have much
19866 directory information yet and it tries to fetch a v2 hidden
19867 service descriptor. Fixes bug 651, reported by nwf.
19868 - Initialize log mutex before initializing dmalloc. Otherwise,
19869 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
19870 - Use recursive pthread mutexes in order to avoid deadlock when
19871 logging debug-level messages to a controller. Bug spotted by nwf,
19872 bugfix on 0.2.0.16-alpha.
19874 o Minor bugfixes (resource management):
19875 - Keep address policies from leaking memory: start their refcount
19876 at 1, not 2. Bugfix on 0.2.0.16-alpha.
19877 - Free authority certificates on exit, so they don't look like memory
19878 leaks. Bugfix on 0.2.0.19-alpha.
19879 - Free static hashtables for policy maps and for TLS connections on
19880 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
19881 - Avoid allocating extra space when computing consensuses on 64-bit
19882 platforms. Bug spotted by aakova.
19884 o Minor bugfixes (misc):
19885 - Do not read the configuration file when we've only been told to
19886 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
19887 based on patch from Sebastian Hahn.
19888 - Exit relays that are used as a client can now reach themselves
19889 using the .exit notation, rather than just launching an infinite
19890 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
19891 - When attempting to open a logfile fails, tell us why.
19892 - Fix a dumb bug that was preventing us from knowing that we should
19893 preemptively build circuits to handle expected directory requests.
19894 Fixes bug 660. Bugfix on 0.1.2.x.
19895 - Warn less verbosely about clock skew from netinfo cells from
19896 untrusted sources. Fixes bug 663.
19897 - Make controller stream events for DNS requests more consistent,
19898 by adding "new stream" events for DNS requests, and removing
19899 spurious "stream closed" events" for cached reverse resolves.
19900 Patch from mwenge. Fixes bug 646.
19901 - Correctly notify one-hop connections when a circuit build has
19902 failed. Possible fix for bug 669. Found by lodger.
19905 Changes in version 0.2.0.23-rc - 2008-03-24
19906 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
19907 makes bootstrapping faster if the first directory mirror you contact
19908 is down. The bundles also include the new Vidalia 0.1.2 release.
19911 - When a tunneled directory request is made to a directory server
19912 that's down, notice after 30 seconds rather than 120 seconds. Also,
19913 fail any begindir streams that are pending on it, so they can
19914 retry elsewhere. This was causing multi-minute delays on bootstrap.
19917 Changes in version 0.2.0.22-rc - 2008-03-18
19918 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
19919 enables encrypted directory connections by default for non-relays, fixes
19920 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
19921 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
19924 - Enable encrypted directory connections by default for non-relays,
19925 so censor tools that block Tor directory connections based on their
19926 plaintext patterns will no longer work. This means Tor works in
19927 certain censored countries by default again.
19930 - Make sure servers always request certificates from clients during
19931 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
19932 - Do not enter a CPU-eating loop when a connection is closed in
19933 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
19934 diagnosed by lodger; bugfix on 0.2.0.20-rc.
19935 - Fix assertion failure that could occur when a blocked circuit
19936 became unblocked, and it had pending client DNS requests. Bugfix
19937 on 0.2.0.1-alpha. Fixes bug 632.
19939 o Minor bugfixes (on 0.1.2.x):
19940 - Generate "STATUS_SERVER" events rather than misspelled
19941 "STATUS_SEVER" events. Caught by mwenge.
19942 - When counting the number of bytes written on a TLS connection,
19943 look at the BIO actually used for writing to the network, not
19944 at the BIO used (sometimes) to buffer data for the network.
19945 Looking at different BIOs could result in write counts on the
19946 order of ULONG_MAX. Fixes bug 614.
19947 - On Windows, correctly detect errors when listing the contents of
19948 a directory. Fix from lodger.
19950 o Minor bugfixes (on 0.2.0.x):
19951 - Downgrade "sslv3 alert handshake failure" message to INFO.
19952 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
19953 left BandwidthRate and BandwidthBurst at the default, we would be
19954 silently limited by those defaults. Now raise them to match the
19955 RelayBandwidth* values.
19956 - Fix the SVK version detection logic to work correctly on a branch.
19957 - Make --enable-openbsd-malloc work correctly on Linux with alpha
19958 CPUs. Fixes bug 625.
19959 - Logging functions now check that the passed severity is sane.
19960 - Use proper log levels in the testsuite call of
19961 get_interface_address6().
19962 - When using a nonstandard malloc, do not use the platform values for
19963 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
19964 - Make the openbsd malloc code use 8k pages on alpha CPUs and
19966 - Detect mismatched page sizes when using --enable-openbsd-malloc.
19967 - Avoid double-marked-for-close warning when certain kinds of invalid
19968 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
19969 for bug 617. Bugfix on 0.2.0.1-alpha.
19970 - Make sure that the "NULL-means-reject *:*" convention is followed by
19971 all the policy manipulation functions, avoiding some possible crash
19972 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
19973 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
19974 actually works, and doesn't warn about every single reverse lookup.
19975 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
19978 - Only log guard node status when guard node status has changed.
19979 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
19980 make "INFO" 75% less verbose.
19983 Changes in version 0.2.0.21-rc - 2008-03-02
19984 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
19985 makes Tor work well with Vidalia again, fixes a rare assert bug,
19986 and fixes a pair of more minor bugs. The bundles also include Vidalia
19987 0.1.0 and Torbutton 1.1.16.
19990 - The control port should declare that it requires password auth
19991 when HashedControlSessionPassword is set too. Patch from Matt Edman;
19992 bugfix on 0.2.0.20-rc. Fixes bug 615.
19993 - Downgrade assert in connection_buckets_decrement() to a log message.
19994 This may help us solve bug 614, and in any case will make its
19995 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
19996 - We were sometimes miscounting the number of bytes read from the
19997 network, causing our rate limiting to not be followed exactly.
19998 Bugfix on 0.2.0.16-alpha. Reported by lodger.
20001 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
20002 OpenSSL versions should have been working fine. Diagnosis and patch
20003 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
20004 Bugfix on 0.2.0.20-rc.
20007 Changes in version 0.2.0.20-rc - 2008-02-24
20008 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
20009 makes more progress towards normalizing Tor's TLS handshake, makes
20010 hidden services work better again, helps relays bootstrap if they don't
20011 know their IP address, adds optional support for linking in openbsd's
20012 allocator or tcmalloc, allows really fast relays to scale past 15000
20013 sockets, and fixes a bunch of minor bugs reported by Veracode.
20016 - Enable the revised TLS handshake based on the one designed by
20017 Steven Murdoch in proposal 124, as revised in proposal 130. It
20018 includes version negotiation for OR connections as described in
20019 proposal 105. The new handshake is meant to be harder for censors
20020 to fingerprint, and it adds the ability to detect certain kinds of
20021 man-in-the-middle traffic analysis attacks. The version negotiation
20022 feature will allow us to improve Tor's link protocol more safely
20024 - Choose which bridge to use proportional to its advertised bandwidth,
20025 rather than uniformly at random. This should speed up Tor for
20026 bridge users. Also do this for people who set StrictEntryNodes.
20027 - When a TrackHostExits-chosen exit fails too many times in a row,
20028 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
20031 - Resolved problems with (re-)fetching hidden service descriptors.
20032 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
20033 and 0.2.0.19-alpha.
20034 - If we only ever used Tor for hidden service lookups or posts, we
20035 would stop building circuits and start refusing connections after
20036 24 hours, since we falsely believed that Tor was dormant. Reported
20037 by nwf; bugfix on 0.1.2.x.
20038 - Servers that don't know their own IP address should go to the
20039 authorities for their first directory fetch, even if their DirPort
20040 is off or if they don't know they're reachable yet. This will help
20041 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
20042 - When counting the number of open sockets, count not only the number
20043 of sockets we have received from the socket() call, but also
20044 the number we've gotten from accept() and socketpair(). This bug
20045 made us fail to count all sockets that we were using for incoming
20046 connections. Bugfix on 0.2.0.x.
20047 - Fix code used to find strings within buffers, when those strings
20048 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
20049 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
20050 - Add a new __HashedControlSessionPassword option for controllers
20051 to use for one-off session password hashes that shouldn't get
20052 saved to disk by SAVECONF --- Vidalia users were accumulating a
20053 pile of HashedControlPassword lines in their torrc files, one for
20054 each time they had restarted Tor and then clicked Save. Make Tor
20055 automatically convert "HashedControlPassword" to this new option but
20056 only when it's given on the command line. Partial fix for bug 586.
20058 o Minor features (performance):
20059 - Tune parameters for cell pool allocation to minimize amount of
20061 - Add OpenBSD malloc code from phk as an optional malloc
20062 replacement on Linux: some glibc libraries do very poorly
20063 with Tor's memory allocation patterns. Pass
20064 --enable-openbsd-malloc to get the replacement malloc code.
20065 - Add a --with-tcmalloc option to the configure script to link
20066 against tcmalloc (if present). Does not yet search for
20067 non-system include paths.
20068 - Stop imposing an arbitrary maximum on the number of file descriptors
20069 used for busy servers. Bug reported by Olaf Selke; patch from
20072 o Minor features (other):
20073 - When SafeLogging is disabled, log addresses along with all TLS
20075 - When building with --enable-gcc-warnings, check for whether Apple's
20076 warning "-Wshorten-64-to-32" is available.
20077 - Add a --passphrase-fd argument to the tor-gencert command for
20080 o Minor bugfixes (memory leaks and code problems):
20081 - We were leaking a file descriptor if Tor started with a zero-length
20082 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
20083 - Detect size overflow in zlib code. Reported by Justin Ferguson and
20085 - We were comparing the raw BridgePassword entry with a base64'ed
20086 version of it, when handling a "/tor/networkstatus-bridges"
20087 directory request. Now compare correctly. Noticed by Veracode.
20088 - Recover from bad tracked-since value in MTBF-history file.
20089 Should fix bug 537.
20090 - Alter the code that tries to recover from unhandled write
20091 errors, to not try to flush onto a socket that's given us
20092 unhandled errors. Bugfix on 0.1.2.x.
20093 - Make Unix controlsockets work correctly on OpenBSD. Patch from
20094 tup. Bugfix on 0.2.0.3-alpha.
20096 o Minor bugfixes (other):
20097 - If we have an extra-info document for our server, always make
20098 it available on the control port, even if we haven't gotten
20099 a copy of it from an authority yet. Patch from mwenge.
20100 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
20101 - Directory mirrors no longer include a guess at the client's IP
20102 address if the connection appears to be coming from the same /24
20103 network; it was producing too many wrong guesses.
20104 - Make the new hidden service code respect the SafeLogging setting.
20105 Bugfix on 0.2.0.x. Patch from Karsten.
20106 - When starting as an authority, do not overwrite all certificates
20107 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
20108 - If we're trying to flush the last bytes on a connection (for
20109 example, when answering a directory request), reset the
20110 time-to-give-up timeout every time we manage to write something
20111 on the socket. Bugfix on 0.1.2.x.
20112 - Change the behavior of "getinfo status/good-server-descriptor"
20113 so it doesn't return failure when any authority disappears.
20114 - Even though the man page said that "TrackHostExits ." should
20115 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
20116 - Report TLS "zero return" case as a "clean close" and "IO error"
20117 as a "close". Stop calling closes "unexpected closes": existing
20118 Tors don't use SSL_close(), so having a connection close without
20119 the TLS shutdown handshake is hardly unexpected.
20120 - Send NAMESERVER_STATUS messages for a single failed nameserver
20123 o Code simplifications and refactoring:
20124 - Remove the tor_strpartition function: its logic was confused,
20125 and it was only used for one thing that could be implemented far
20129 Changes in version 0.2.0.19-alpha - 2008-02-09
20130 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
20131 handshake, makes path selection for relays more secure and IP address
20132 guessing more robust, and generally fixes a lot of bugs in preparation
20133 for calling the 0.2.0 branch stable.
20136 - Do not include recognizeable strings in the commonname part of
20137 Tor's x509 certificates.
20140 - If we're a relay, avoid picking ourselves as an introduction point,
20141 a rendezvous point, or as the final hop for internal circuits. Bug
20142 reported by taranis and lodger. Bugfix on 0.1.2.x.
20143 - Patch from "Andrew S. Lists" to catch when we contact a directory
20144 mirror at IP address X and he says we look like we're coming from
20145 IP address X. Bugfix on 0.1.2.x.
20147 o Minor features (security):
20148 - Be more paranoid about overwriting sensitive memory on free(),
20149 as a defensive programming tactic to ensure forward secrecy.
20151 o Minor features (directory authority):
20152 - Actually validate the options passed to AuthDirReject,
20153 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
20154 - Reject router descriptors with out-of-range bandwidthcapacity or
20155 bandwidthburst values.
20157 o Minor features (controller):
20158 - Reject controller commands over 1MB in length. This keeps rogue
20159 processes from running us out of memory.
20161 o Minor features (misc):
20162 - Give more descriptive well-formedness errors for out-of-range
20163 hidden service descriptor/protocol versions.
20164 - Make memory debugging information describe more about history
20165 of cell allocation, so we can help reduce our memory use.
20167 o Deprecated features (controller):
20168 - The status/version/num-versioning and status/version/num-concurring
20169 GETINFO options are no longer useful in the v3 directory protocol:
20170 treat them as deprecated, and warn when they're used.
20173 - When our consensus networkstatus has been expired for a while, stop
20174 being willing to build circuits using it. Fixes bug 401. Bugfix
20176 - Directory caches now fetch certificates from all authorities
20177 listed in a networkstatus consensus, even when they do not
20178 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
20179 - When connecting to a bridge without specifying its key, insert
20180 the connection into the identity-to-connection map as soon as
20181 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
20182 - Detect versions of OS X where malloc_good_size() is present in the
20183 library but never actually declared. Resolves bug 587. Bugfix
20185 - Stop incorrectly truncating zlib responses to directory authority
20186 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
20187 - Stop recommending that every server operator send mail to tor-ops.
20188 Resolves bug 597. Bugfix on 0.1.2.x.
20189 - Don't trigger an assert if we start a directory authority with a
20190 private IP address (like 127.0.0.1).
20191 - Avoid possible failures when generating a directory with routers
20192 with over-long versions strings, or too many flags set. Bugfix
20194 - If an attempt to launch a DNS resolve request over the control
20195 port fails because we have overrun the limit on the number of
20196 connections, tell the controller that the request has failed.
20197 - Avoid using too little bandwidth when our clock skips a few
20198 seconds. Bugfix on 0.1.2.x.
20199 - Fix shell error when warning about missing packages in configure
20200 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
20201 - Do not become confused when receiving a spurious VERSIONS-like
20202 cell from a confused v1 client. Bugfix on 0.2.0.x.
20203 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
20204 introduction points for a hidden service have failed. Patch from
20205 Karsten Loesing. Bugfix on 0.2.0.x.
20207 o Code simplifications and refactoring:
20208 - Remove some needless generality from cpuworker code, for improved
20210 - Stop overloading the circuit_t.onionskin field for both "onionskin
20211 from a CREATE cell that we are waiting for a cpuworker to be
20212 assigned" and "onionskin from an EXTEND cell that we are going to
20213 send to an OR as soon as we are connected". Might help with bug 600.
20214 - Add an in-place version of aes_crypt() so that we can avoid doing a
20215 needless memcpy() call on each cell payload.
20218 Changes in version 0.2.0.18-alpha - 2008-01-25
20219 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
20220 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
20221 that can warn or reject connections to ports generally associated with
20222 vulnerable-plaintext protocols.
20224 o New directory authorities:
20225 - Set up dannenberg (run by CCC) as the sixth v3 directory
20229 - Fix a major memory leak when attempting to use the v2 TLS
20230 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
20231 - We accidentally enabled the under-development v2 TLS handshake
20232 code, which was causing log entries like "TLS error while
20233 renegotiating handshake". Disable it again. Resolves bug 590.
20234 - We were computing the wrong Content-Length: header for directory
20235 responses that need to be compressed on the fly, causing clients
20236 asking for those items to always fail. Bugfix on 0.2.0.x; partially
20240 - Avoid going directly to the directory authorities even if you're a
20241 relay, if you haven't found yourself reachable yet or if you've
20242 decided not to advertise your dirport yet. Addresses bug 556.
20243 - If we've gone 12 hours since our last bandwidth check, and we
20244 estimate we have less than 50KB bandwidth capacity but we could
20245 handle more, do another bandwidth test.
20246 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
20247 Tor can warn and/or refuse connections to ports commonly used with
20248 vulnerable-plaintext protocols. Currently we warn on ports 23,
20249 109, 110, and 143, but we don't reject any.
20252 - When we setconf ClientOnly to 1, close any current OR and Dir
20253 listeners. Reported by mwenge.
20254 - When we get a consensus that's been signed by more people than
20255 we expect, don't log about it; it's not a big deal. Reported
20259 - Don't answer "/tor/networkstatus-bridges" directory requests if
20260 the request isn't encrypted.
20261 - Make "ClientOnly 1" config option disable directory ports too.
20262 - Patches from Karsten Loesing to make v2 hidden services more
20263 robust: work even when there aren't enough HSDir relays available;
20264 retry when a v2 rend desc fetch fails; but don't retry if we
20265 already have a usable v0 rend desc.
20268 Changes in version 0.2.0.17-alpha - 2008-01-17
20269 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
20272 - Make the tor-gencert man page get included correctly in the tarball.
20275 Changes in version 0.2.0.16-alpha - 2008-01-17
20276 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
20277 Loesing, and generally cleans up a lot of features and minor bugs.
20279 o New directory authorities:
20280 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
20283 o Major performance improvements:
20284 - Switch our old ring buffer implementation for one more like that
20285 used by free Unix kernels. The wasted space in a buffer with 1mb
20286 of data will now be more like 8k than 1mb. The new implementation
20287 also avoids realloc();realloc(); patterns that can contribute to
20288 memory fragmentation.
20291 - Configuration files now accept C-style strings as values. This
20292 helps encode characters not allowed in the current configuration
20293 file format, such as newline or #. Addresses bug 557.
20294 - Although we fixed bug 539 (where servers would send HTTP status 503
20295 responses _and_ send a body too), there are still servers out
20296 there that haven't upgraded. Therefore, make clients parse such
20297 bodies when they receive them.
20298 - When we're not serving v2 directory information, there is no reason
20299 to actually keep any around. Remove the obsolete files and directory
20300 on startup if they are very old and we aren't going to serve them.
20302 o Minor performance improvements:
20303 - Reference-count and share copies of address policy entries; only 5%
20304 of them were actually distinct.
20305 - Never walk through the list of logs if we know that no log is
20306 interested in a given message.
20309 - When an authority has not signed a consensus, do not try to
20310 download a nonexistent "certificate with key 00000000". Bugfix
20311 on 0.2.0.x. Fixes bug 569.
20312 - Fix a rare assert error when we're closing one of our threads:
20313 use a mutex to protect the list of logs, so we never write to the
20314 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
20315 bug 575, which is kind of the revenge of bug 222.
20316 - Patch from Karsten Loesing to complain less at both the client
20317 and the relay when a relay used to have the HSDir flag but doesn't
20318 anymore, and we try to upload a hidden service descriptor.
20319 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
20321 - Do not try to download missing certificates until we have tried
20322 to check our fallback consensus. Fixes bug 583.
20323 - Make bridges round reported GeoIP stats info up to the nearest
20324 estimate, not down. Now we can distinguish between "0 people from
20325 this country" and "1 person from this country".
20326 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
20327 - Avoid possible segfault if key generation fails in
20328 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
20329 - Avoid segfault in the case where a badly behaved v2 versioning
20330 directory sends a signed networkstatus with missing client-versions.
20332 - Avoid segfaults on certain complex invocations of
20333 router_get_by_hexdigest(). Bugfix on 0.1.2.
20334 - Correct bad index on array access in parse_http_time(). Bugfix
20336 - Fix possible bug in vote generation when server versions are present
20337 but client versions are not.
20338 - Fix rare bug on REDIRECTSTREAM control command when called with no
20339 port set: it could erroneously report an error when none had
20341 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
20342 compressing large objects and find ourselves with more than 4k
20343 left over. Bugfix on 0.2.0.
20344 - Fix a small memory leak when setting up a hidden service.
20345 - Fix a few memory leaks that could in theory happen under bizarre
20347 - Fix an assert if we post a general-purpose descriptor via the
20348 control port but that descriptor isn't mentioned in our current
20349 network consensus. Bug reported by Jon McLachlan; bugfix on
20352 o Minor features (controller):
20353 - Get NS events working again. Patch from tup.
20354 - The GETCONF command now escapes and quotes configuration values
20355 that don't otherwise fit into the torrc file.
20356 - The SETCONF command now handles quoted values correctly.
20358 o Minor features (directory authorities):
20359 - New configuration options to override default maximum number of
20360 servers allowed on a single IP address. This is important for
20361 running a test network on a single host.
20362 - Actually implement the -s option to tor-gencert.
20363 - Add a manual page for tor-gencert.
20365 o Minor features (bridges):
20366 - Bridge authorities no longer serve bridge descriptors over
20367 unencrypted connections.
20369 o Minor features (other):
20370 - Add hidden services and DNSPorts to the list of things that make
20371 Tor accept that it has running ports. Change starting Tor with no
20372 ports from a fatal error to a warning; we might change it back if
20373 this turns out to confuse anybody. Fixes bug 579.
20376 Changes in version 0.1.2.19 - 2008-01-17
20377 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
20378 exit policy a little bit more conservative so it's safer to run an
20379 exit relay on a home system, and fixes a variety of smaller issues.
20382 - Exit policies now reject connections that are addressed to a
20383 relay's public (external) IP address too, unless
20384 ExitPolicyRejectPrivate is turned off. We do this because too
20385 many relays are running nearby to services that trust them based
20386 on network address.
20389 - When the clock jumps forward a lot, do not allow the bandwidth
20390 buckets to become negative. Fixes bug 544.
20391 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
20392 on every successful resolve. Reported by Mike Perry.
20393 - Purge old entries from the "rephist" database and the hidden
20394 service descriptor database even when DirPort is zero.
20395 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
20396 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
20397 crashing or mis-answering these requests.
20398 - When we decide to send a 503 response to a request for servers, do
20399 not then also send the server descriptors: this defeats the whole
20400 purpose. Fixes bug 539.
20403 - Changing the ExitPolicyRejectPrivate setting should cause us to
20404 rebuild our server descriptor.
20405 - Fix handling of hex nicknames when answering controller requests for
20406 networkstatus by name, or when deciding whether to warn about
20407 unknown routers in a config option. (Patch from mwenge.)
20408 - Fix a couple of hard-to-trigger autoconf problems that could result
20409 in really weird results on platforms whose sys/types.h files define
20410 nonstandard integer types.
20411 - Don't try to create the datadir when running --verify-config or
20412 --hash-password. Resolves bug 540.
20413 - If we were having problems getting a particular descriptor from the
20414 directory caches, and then we learned about a new descriptor for
20415 that router, we weren't resetting our failure count. Reported
20417 - Although we fixed bug 539 (where servers would send HTTP status 503
20418 responses _and_ send a body too), there are still servers out there
20419 that haven't upgraded. Therefore, make clients parse such bodies
20420 when they receive them.
20421 - Run correctly on systems where rlim_t is larger than unsigned long.
20422 This includes some 64-bit systems.
20423 - Run correctly on platforms (like some versions of OS X 10.5) where
20424 the real limit for number of open files is OPEN_FILES, not rlim_max
20425 from getrlimit(RLIMIT_NOFILES).
20426 - Avoid a spurious free on base64 failure.
20427 - Avoid segfaults on certain complex invocations of
20428 router_get_by_hexdigest().
20429 - Fix rare bug on REDIRECTSTREAM control command when called with no
20430 port set: it could erroneously report an error when none had
20434 Changes in version 0.2.0.15-alpha - 2007-12-25
20435 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
20436 features added in 0.2.0.13-alpha.
20439 - Fix several remotely triggerable asserts based on DirPort requests
20440 for a v2 or v3 networkstatus object before we were prepared. This
20441 was particularly bad for 0.2.0.13 and later bridge relays, who
20442 would never have a v2 networkstatus and would thus always crash
20443 when used. Bugfixes on 0.2.0.x.
20444 - Estimate the v3 networkstatus size more accurately, rather than
20445 estimating it at zero bytes and giving it artificially high priority
20446 compared to other directory requests. Bugfix on 0.2.0.x.
20449 - Fix configure.in logic for cross-compilation.
20450 - When we load a bridge descriptor from the cache, and it was
20451 previously unreachable, mark it as retriable so we won't just
20452 ignore it. Also, try fetching a new copy immediately. Bugfixes
20454 - The bridge GeoIP stats were counting other relays, for example
20455 self-reachability and authority-reachability tests.
20458 - Support compilation to target iPhone; patch from cjacker huang.
20459 To build for iPhone, pass the --enable-iphone option to configure.
20462 Changes in version 0.2.0.14-alpha - 2007-12-23
20464 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
20465 without a datadirectory from a previous Tor install. Reported
20467 - Fix a crash when we fetch a descriptor that turns out to be
20468 unexpected (it used to be in our networkstatus when we started
20469 fetching it, but it isn't in our current networkstatus), and we
20470 aren't using bridges. Bugfix on 0.2.0.x.
20471 - Fix a crash when accessing hidden services: it would work the first
20472 time you use a given introduction point for your service, but
20473 on subsequent requests we'd be using garbage memory. Fixed by
20474 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
20475 - Fix a crash when we load a bridge descriptor from disk but we don't
20476 currently have a Bridge line for it in our torrc. Bugfix on
20480 - If bridge authorities set BridgePassword, they will serve a
20481 snapshot of known bridge routerstatuses from their DirPort to
20482 anybody who knows that password. Unset by default.
20485 - Make the unit tests build again.
20486 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
20487 - Make PublishServerDescriptor default to 1, so the default doesn't
20488 have to change as we invent new directory protocol versions.
20489 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
20490 be included unless sys/time.h is already included. Fixes
20491 bug 553. Bugfix on 0.2.0.x.
20492 - If we receive a general-purpose descriptor and then receive an
20493 identical bridge-purpose descriptor soon after, don't discard
20494 the next one as a duplicate.
20497 - If BridgeRelay is set to 1, then the default for
20498 PublishServerDescriptor is now "bridge" rather than "v2,v3".
20499 - If the user sets RelayBandwidthRate but doesn't set
20500 RelayBandwidthBurst, then make them equal rather than erroring out.
20503 Changes in version 0.2.0.13-alpha - 2007-12-21
20504 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
20505 Goodell, fixes many more bugs, and adds a lot of infrastructure for
20508 o New directory authorities:
20509 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
20513 - Only update guard status (usable / not usable) once we have
20514 enough directory information. This was causing us to always pick
20515 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
20516 causing us to discard all our guards on startup if we hadn't been
20517 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
20518 - Purge old entries from the "rephist" database and the hidden
20519 service descriptor databases even when DirPort is zero. Bugfix
20521 - We were ignoring our RelayBandwidthRate for the first 30 seconds
20522 after opening a circuit -- even a relayed circuit. Bugfix on
20524 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
20525 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
20526 crashing or mis-answering these types of requests.
20527 - Relays were publishing their server descriptor to v1 and v2
20528 directory authorities, but they didn't try publishing to v3-only
20529 authorities. Fix this; and also stop publishing to v1 authorities.
20531 - When we were reading router descriptors from cache, we were ignoring
20532 the annotations -- so for example we were reading in bridge-purpose
20533 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
20534 - When we decided to send a 503 response to a request for servers, we
20535 were then also sending the server descriptors: this defeats the
20536 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
20539 - Bridge relays now behave like clients with respect to time
20540 intervals for downloading new consensus documents -- otherwise they
20541 stand out. Bridge users now wait until the end of the interval,
20542 so their bridge relay will be sure to have a new consensus document.
20543 - Three new config options (AlternateDirAuthority,
20544 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
20545 user selectively replace the default directory authorities by type,
20546 rather than the all-or-nothing replacement that DirServer offers.
20547 - Tor can now be configured to read a GeoIP file from disk in one
20548 of two formats. This can be used by controllers to map IP addresses
20549 to countries. Eventually, it may support exit-by-country.
20550 - When possible, bridge relays remember which countries users
20551 are coming from, and report aggregate information in their
20552 extra-info documents, so that the bridge authorities can learn
20553 where Tor is blocked.
20554 - Bridge directory authorities now do reachability testing on the
20555 bridges they know. They provide router status summaries to the
20556 controller via "getinfo ns/purpose/bridge", and also dump summaries
20557 to a file periodically.
20558 - Stop fetching directory info so aggressively if your DirPort is
20559 on but your ORPort is off; stop fetching v2 dir info entirely.
20560 You can override these choices with the new FetchDirInfoEarly
20564 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
20565 consensus documents when there are too many relays at a single
20566 IP address. Now clear it in v2 network status documents too, and
20567 also clear it in routerinfo_t when the relay is no longer listed
20568 in the relevant networkstatus document.
20569 - Don't crash if we get an unexpected value for the
20570 PublishServerDescriptor config option. Reported by Matt Edman;
20571 bugfix on 0.2.0.9-alpha.
20572 - Our new v2 hidden service descriptor format allows descriptors
20573 that have no introduction points. But Tor crashed when we tried
20574 to build a descriptor with no intro points (and it would have
20575 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
20576 by Karsten Loesing.
20577 - Fix building with dmalloc 5.5.2 with glibc.
20578 - Reject uploaded descriptors and extrainfo documents if they're
20579 huge. Otherwise we'll cache them all over the network and it'll
20580 clog everything up. Reported by Aljosha Judmayer.
20581 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
20582 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
20583 - When the DANGEROUS_VERSION controller status event told us we're
20584 running an obsolete version, it used the string "OLD" to describe
20585 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
20586 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
20587 - If we can't expand our list of entry guards (e.g. because we're
20588 using bridges or we have StrictEntryNodes set), don't mark relays
20589 down when they fail a directory request. Otherwise we're too quick
20590 to mark all our entry points down. Bugfix on 0.1.2.x.
20591 - Fix handling of hex nicknames when answering controller requests for
20592 networkstatus by name, or when deciding whether to warn about unknown
20593 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
20594 - Fix a couple of hard-to-trigger autoconf problems that could result
20595 in really weird results on platforms whose sys/types.h files define
20596 nonstandard integer types. Bugfix on 0.1.2.x.
20597 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
20598 - Don't crash on name lookup when we have no current consensus. Fixes
20599 bug 538; bugfix on 0.2.0.x.
20600 - Only Tors that want to mirror the v2 directory info should
20601 create the "cached-status" directory in their datadir. (All Tors
20602 used to create it.) Bugfix on 0.2.0.9-alpha.
20603 - Directory authorities should only automatically download Extra Info
20604 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
20607 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
20608 consumers. (We already do this on HUP.)
20609 - Authorities and caches fetch the v2 networkstatus documents
20610 less often, now that v3 is encouraged.
20611 - Add a new config option BridgeRelay that specifies you want to
20612 be a bridge relay. Right now the only difference is that it makes
20613 you answer begin_dir requests, and it makes you cache dir info,
20614 even if your DirPort isn't on.
20615 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
20616 ask about source, timestamp of arrival, purpose, etc. We need
20617 something like this to help Vidalia not do GeoIP lookups on bridge
20619 - Allow multiple HashedControlPassword config lines, to support
20620 multiple controller passwords.
20621 - Authorities now decide whether they're authoritative for a given
20622 router based on the router's purpose.
20623 - New config options AuthDirBadDir and AuthDirListBadDirs for
20624 authorities to mark certain relays as "bad directories" in the
20625 networkstatus documents. Also supports the "!baddir" directive in
20626 the approved-routers file.
20629 Changes in version 0.2.0.12-alpha - 2007-11-16
20630 This twelfth development snapshot fixes some more build problems as
20631 well as a few minor bugs.
20634 - Make it build on OpenBSD again. Patch from tup.
20635 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
20636 package-building for Red Hat, OS X, etc.
20638 o Minor bugfixes (on 0.1.2.x):
20639 - Changing the ExitPolicyRejectPrivate setting should cause us to
20640 rebuild our server descriptor.
20642 o Minor bugfixes (on 0.2.0.x):
20643 - When we're lacking a consensus, don't try to perform rendezvous
20644 operations. Reported by Karsten Loesing.
20645 - Fix a small memory leak whenever we decide against using a
20646 newly picked entry guard. Reported by Mike Perry.
20647 - When authorities detected more than two relays running on the same
20648 IP address, they were clearing all the status flags but forgetting
20649 to clear the "hsdir" flag. So clients were being told that a
20650 given relay was the right choice for a v2 hsdir lookup, yet they
20651 never had its descriptor because it was marked as 'not running'
20653 - If we're trying to fetch a bridge descriptor and there's no way
20654 the bridge authority could help us (for example, we don't know
20655 a digest, or there is no bridge authority), don't be so eager to
20656 fall back to asking the bridge authority.
20657 - If we're using bridges or have strictentrynodes set, and our
20658 chosen exit is in the same family as all our bridges/entry guards,
20659 then be flexible about families.
20662 - When we negotiate a v2 link-layer connection (not yet implemented),
20663 accept RELAY_EARLY cells and turn them into RELAY cells if we've
20664 negotiated a v1 connection for their next step. Initial code for
20668 Changes in version 0.2.0.11-alpha - 2007-11-12
20669 This eleventh development snapshot fixes some build problems with
20670 the previous snapshot. It also includes a more secure-by-default exit
20671 policy for relays, fixes an enormous memory leak for exit relays, and
20672 fixes another bug where servers were falling out of the directory list.
20675 - Exit policies now reject connections that are addressed to a
20676 relay's public (external) IP address too, unless
20677 ExitPolicyRejectPrivate is turned off. We do this because too
20678 many relays are running nearby to services that trust them based
20679 on network address. Bugfix on 0.1.2.x.
20682 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
20683 on every successful resolve. Reported by Mike Perry; bugfix
20685 - On authorities, never downgrade to old router descriptors simply
20686 because they're listed in the consensus. This created a catch-22
20687 where we wouldn't list a new descriptor because there was an
20688 old one in the consensus, and we couldn't get the new one in the
20689 consensus because we wouldn't list it. Possible fix for bug 548.
20690 Also, this might cause bug 543 to appear on authorities; if so,
20691 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
20693 o Packaging fixes on 0.2.0.10-alpha:
20694 - We were including instructions about what to do with the
20695 src/config/fallback-consensus file, but we weren't actually
20696 including it in the tarball. Disable all of that for now.
20699 - Allow people to say PreferTunnelledDirConns rather than
20700 PreferTunneledDirConns, for those alternate-spellers out there.
20703 - Don't reevaluate all the information from our consensus document
20704 just because we've downloaded a v2 networkstatus that we intend
20705 to cache. Fixes bug 545; bugfix on 0.2.0.x.
20708 Changes in version 0.2.0.10-alpha - 2007-11-10
20709 This tenth development snapshot adds a third v3 directory authority
20710 run by Mike Perry, adds most of Karsten Loesing's new hidden service
20711 descriptor format, fixes a bad crash bug and new bridge bugs introduced
20712 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
20713 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
20714 addresses many more minor issues.
20716 o New directory authorities:
20717 - Set up ides (run by Mike Perry) as the third v3 directory authority.
20720 - Allow tunnelled directory connections to ask for an encrypted
20721 "begin_dir" connection or an anonymized "uses a full Tor circuit"
20722 connection independently. Now we can make anonymized begin_dir
20723 connections for (e.g.) more secure hidden service posting and
20725 - More progress on proposal 114: code from Karsten Loesing to
20726 implement new hidden service descriptor format.
20727 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
20728 accommodate the growing number of servers that use the default
20729 and are reaching it.
20730 - Directory authorities use a new formula for selecting which nodes
20731 to advertise as Guards: they must be in the top 7/8 in terms of
20732 how long we have known about them, and above the median of those
20733 nodes in terms of weighted fractional uptime.
20734 - Make "not enough dir info yet" warnings describe *why* Tor feels
20735 it doesn't have enough directory info yet.
20738 - Stop servers from crashing if they set a Family option (or
20739 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
20741 - Make bridge users work again -- the move to v3 directories in
20742 0.2.0.9-alpha had introduced a number of bugs that made bridges
20743 no longer work for clients.
20744 - When the clock jumps forward a lot, do not allow the bandwidth
20745 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
20747 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
20748 - When the consensus lists a router descriptor that we previously were
20749 mirroring, but that we considered non-canonical, reload the
20750 descriptor as canonical. This fixes bug 543 where Tor servers
20751 would start complaining after a few days that they don't have
20752 enough directory information to build a circuit.
20753 - Consider replacing the current consensus when certificates arrive
20754 that make the pending consensus valid. Previously, we were only
20755 considering replacement when the new certs _didn't_ help.
20756 - Fix an assert error on startup if we didn't already have the
20757 consensus and certs cached in our datadirectory: we were caching
20758 the consensus in consensus_waiting_for_certs but then free'ing it
20760 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
20761 Request) if we need more v3 certs but we've already got pending
20762 requests for all of them.
20763 - Correctly back off from failing certificate downloads. Fixes
20765 - Authorities don't vote on the Running flag if they have been running
20766 for less than 30 minutes themselves. Fixes bug 547, where a newly
20767 started authority would vote that everyone was down.
20769 o New requirements:
20770 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
20771 it, it had no AES, and it hasn't seen any security patches since
20775 - Clients now hold circuitless TLS connections open for 1.5 times
20776 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
20777 rebuild a new circuit over them within that timeframe. Previously,
20778 they held them open only for KeepalivePeriod (5 minutes).
20779 - Use "If-Modified-Since" to avoid retrieving consensus
20780 networkstatuses that we already have.
20781 - When we have no consensus, check FallbackNetworkstatusFile (defaults
20782 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
20783 we start knowing some directory caches.
20784 - When we receive a consensus from the future, warn about skew.
20785 - Improve skew reporting: try to give the user a better log message
20786 about how skewed they are, and how much this matters.
20787 - When we have a certificate for an authority, believe that
20788 certificate's claims about the authority's IP address.
20789 - New --quiet command-line option to suppress the default console log.
20790 Good in combination with --hash-password.
20791 - Authorities send back an X-Descriptor-Not-New header in response to
20792 an accepted-but-discarded descriptor upload. Partially implements
20794 - Make the log message for "tls error. breaking." more useful.
20795 - Better log messages about certificate downloads, to attempt to
20796 track down the second incarnation of bug 546.
20798 o Minor features (bridges):
20799 - If bridge users set UpdateBridgesFromAuthority, but the digest
20800 they ask for is a 404 from the bridge authority, they now fall
20801 back to trying the bridge directly.
20802 - Bridges now use begin_dir to publish their server descriptor to
20803 the bridge authority, even when they haven't set TunnelDirConns.
20805 o Minor features (controller):
20806 - When reporting clock skew, and we know that the clock is _at least
20807 as skewed_ as some value, but we don't know the actual value,
20808 report the value as a "minimum skew."
20811 - Update linux-tor-prio.sh script to allow QoS based on the uid of
20812 the Tor process. Patch from Marco Bonetti with tweaks from Mike
20816 - Refuse to start if both ORPort and UseBridges are set. Bugfix
20817 on 0.2.0.x, suggested by Matt Edman.
20818 - Don't stop fetching descriptors when FetchUselessDescriptors is
20819 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
20820 reported by tup and ioerror.
20821 - Better log message on vote from unknown authority.
20822 - Don't log "Launching 0 request for 0 router" message.
20824 o Minor bugfixes (memory leaks):
20825 - Stop leaking memory every time we parse a v3 certificate. Bugfix
20827 - Stop leaking memory every time we load a v3 certificate. Bugfix
20828 on 0.2.0.1-alpha. Fixes bug 536.
20829 - Stop leaking a cached networkstatus on exit. Bugfix on
20831 - Stop leaking voter information every time we free a consensus.
20832 Bugfix on 0.2.0.3-alpha.
20833 - Stop leaking signed data every time we check a voter signature.
20834 Bugfix on 0.2.0.3-alpha.
20835 - Stop leaking a signature every time we fail to parse a consensus or
20836 a vote. Bugfix on 0.2.0.3-alpha.
20837 - Stop leaking v2_download_status_map on shutdown. Bugfix on
20839 - Stop leaking conn->nickname every time we make a connection to a
20840 Tor relay without knowing its expected identity digest (e.g. when
20841 using bridges). Bugfix on 0.2.0.3-alpha.
20843 - Minor bugfixes (portability):
20844 - Run correctly on platforms where rlim_t is larger than unsigned
20845 long, and/or where the real limit for number of open files is
20846 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
20847 particular, these may be needed for OS X 10.5.
20850 Changes in version 0.1.2.18 - 2007-10-28
20851 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
20852 hidden service introduction that were causing huge delays, and a big
20853 bug that was causing some servers to disappear from the network status
20854 lists for a few hours each day.
20856 o Major bugfixes (crashes):
20857 - If a connection is shut down abruptly because of something that
20858 happened inside connection_flushed_some(), do not call
20859 connection_finished_flushing(). Should fix bug 451:
20860 "connection_stop_writing: Assertion conn->write_event failed"
20861 Bugfix on 0.1.2.7-alpha.
20862 - Fix possible segfaults in functions called from
20863 rend_process_relay_cell().
20865 o Major bugfixes (hidden services):
20866 - Hidden services were choosing introduction points uniquely by
20867 hexdigest, but when constructing the hidden service descriptor
20868 they merely wrote the (potentially ambiguous) nickname.
20869 - Clients now use the v2 intro format for hidden service
20870 connections: they specify their chosen rendezvous point by identity
20871 digest rather than by (potentially ambiguous) nickname. These
20872 changes could speed up hidden service connections dramatically.
20874 o Major bugfixes (other):
20875 - Stop publishing a new server descriptor just because we get a
20876 HUP signal. This led (in a roundabout way) to some servers getting
20877 dropped from the networkstatus lists for a few hours each day.
20878 - When looking for a circuit to cannibalize, consider family as well
20879 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
20880 circuit cannibalization).
20881 - When a router wasn't listed in a new networkstatus, we were leaving
20882 the flags for that router alone -- meaning it remained Named,
20883 Running, etc -- even though absence from the networkstatus means
20884 that it shouldn't be considered to exist at all anymore. Now we
20885 clear all the flags for routers that fall out of the networkstatus
20886 consensus. Fixes bug 529.
20889 - Don't try to access (or alter) the state file when running
20890 --list-fingerprint or --verify-config or --hash-password. Resolves
20892 - When generating information telling us how to extend to a given
20893 router, do not try to include the nickname if it is
20894 absent. Resolves bug 467.
20895 - Fix a user-triggerable segfault in expand_filename(). (There isn't
20896 a way to trigger this remotely.)
20897 - When sending a status event to the controller telling it that an
20898 OR address is reachable, set the port correctly. (Previously we
20899 were reporting the dir port.)
20900 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
20901 command. Bugfix on 0.1.2.17.
20902 - When loading bandwidth history, do not believe any information in
20903 the future. Fixes bug 434.
20904 - When loading entry guard information, do not believe any information
20906 - When we have our clock set far in the future and generate an
20907 onion key, then re-set our clock to be correct, we should not stop
20908 the onion key from getting rotated.
20909 - On some platforms, accept() can return a broken address. Detect
20910 this more quietly, and deal accordingly. Fixes bug 483.
20911 - It's not actually an error to find a non-pending entry in the DNS
20912 cache when canceling a pending resolve. Don't log unless stuff
20913 is fishy. Resolves bug 463.
20914 - Don't reset trusted dir server list when we set a configuration
20915 option. Patch from Robert Hogan.
20916 - Don't try to create the datadir when running --verify-config or
20917 --hash-password. Resolves bug 540.
20920 Changes in version 0.2.0.9-alpha - 2007-10-24
20921 This ninth development snapshot switches clients to the new v3 directory
20922 system; allows servers to be listed in the network status even when they
20923 have the same nickname as a registered server; and fixes many other
20924 bugs including a big one that was causing some servers to disappear
20925 from the network status lists for a few hours each day.
20927 o Major features (directory system):
20928 - Clients now download v3 consensus networkstatus documents instead
20929 of v2 networkstatus documents. Clients and caches now base their
20930 opinions about routers on these consensus documents. Clients only
20931 download router descriptors listed in the consensus.
20932 - Authorities now list servers who have the same nickname as
20933 a different named server, but list them with a new flag,
20934 "Unnamed". Now we can list servers that happen to pick the same
20935 nickname as a server that registered two years ago and then
20936 disappeared. Partially implements proposal 122.
20937 - If the consensus lists a router as "Unnamed", the name is assigned
20938 to a different router: do not identify the router by that name.
20939 Partially implements proposal 122.
20940 - Authorities can now come to a consensus on which method to use to
20941 compute the consensus. This gives us forward compatibility.
20944 - Stop publishing a new server descriptor just because we HUP or
20945 when we find our DirPort to be reachable but won't actually publish
20946 it. New descriptors without any real changes are dropped by the
20947 authorities, and can screw up our "publish every 18 hours" schedule.
20949 - When a router wasn't listed in a new networkstatus, we were leaving
20950 the flags for that router alone -- meaning it remained Named,
20951 Running, etc -- even though absence from the networkstatus means
20952 that it shouldn't be considered to exist at all anymore. Now we
20953 clear all the flags for routers that fall out of the networkstatus
20954 consensus. Fixes bug 529; bugfix on 0.1.2.x.
20955 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
20956 extrainfo documents and then discard them immediately for not
20957 matching the latest router. Bugfix on 0.2.0.1-alpha.
20959 o Minor features (v3 directory protocol):
20960 - Allow tor-gencert to generate a new certificate without replacing
20962 - Allow certificates to include an address.
20963 - When we change our directory-cache settings, reschedule all voting
20964 and download operations.
20965 - Reattempt certificate downloads immediately on failure, as long as
20966 we haven't failed a threshold number of times yet.
20967 - Delay retrying consensus downloads while we're downloading
20968 certificates to verify the one we just got. Also, count getting a
20969 consensus that we already have (or one that isn't valid) as a failure,
20970 and count failing to get the certificates after 20 minutes as a
20972 - Build circuits and download descriptors even if our consensus is a
20973 little expired. (This feature will go away once authorities are
20976 o Minor features (router descriptor cache):
20977 - If we find a cached-routers file that's been sitting around for more
20978 than 28 days unmodified, then most likely it's a leftover from
20979 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
20981 - When we (as a cache) download a descriptor because it was listed
20982 in a consensus, remember when the consensus was supposed to expire,
20983 and don't expire the descriptor until then.
20985 o Minor features (performance):
20986 - Call routerlist_remove_old_routers() much less often. This should
20987 speed startup, especially on directory caches.
20988 - Don't try to launch new descriptor downloads quite so often when we
20989 already have enough directory information to build circuits.
20990 - Base64 decoding was actually showing up on our profile when parsing
20991 the initial descriptor file; switch to an in-process all-at-once
20992 implementation that's about 3.5x times faster than calling out to
20995 o Minor features (compilation):
20996 - Detect non-ASCII platforms (if any still exist) and refuse to
20997 build there: some of our code assumes that 'A' is 65 and so on.
20999 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
21000 - Make the "next period" votes into "current period" votes immediately
21001 after publishing the consensus; avoid a heisenbug that made them
21002 stick around indefinitely.
21003 - When we discard a vote as a duplicate, do not report this as
21005 - Treat missing v3 keys or certificates as an error when running as a
21006 v3 directory authority.
21007 - When we're configured to be a v3 authority, but we're only listed
21008 as a non-v3 authority in our DirServer line for ourself, correct
21010 - If an authority doesn't have a qualified hostname, just put
21011 its address in the vote. This fixes the problem where we referred to
21012 "moria on moria:9031."
21013 - Distinguish between detached signatures for the wrong period, and
21014 detached signatures for a divergent vote.
21015 - Fix a small memory leak when computing a consensus.
21016 - When there's no concensus, we were forming a vote every 30
21017 minutes, but writing the "valid-after" line in our vote based
21018 on our configured V3AuthVotingInterval: so unless the intervals
21019 matched up, we immediately rejected our own vote because it didn't
21020 start at the voting interval that caused us to construct a vote.
21022 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
21023 - Delete unverified-consensus when the real consensus is set.
21024 - Consider retrying a consensus networkstatus fetch immediately
21025 after one fails: don't wait 60 seconds to notice.
21026 - When fetching a consensus as a cache, wait until a newer consensus
21027 should exist before trying to replace the current one.
21028 - Use a more forgiving schedule for retrying failed consensus
21029 downloads than for other types.
21031 o Minor bugfixes (other directory issues):
21032 - Correct the implementation of "download votes by digest." Bugfix on
21034 - Authorities no longer send back "400 you're unreachable please fix
21035 it" errors to Tor servers that aren't online all the time. We're
21036 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
21038 o Minor bugfixes (controller):
21039 - Don't reset trusted dir server list when we set a configuration
21040 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
21041 - Respond to INT and TERM SIGNAL commands before we execute the
21042 signal, in case the signal shuts us down. We had a patch in
21043 0.1.2.1-alpha that tried to do this by queueing the response on
21044 the connection's buffer before shutting down, but that really
21045 isn't the same thing at all. Bug located by Matt Edman.
21047 o Minor bugfixes (misc):
21048 - Correctly check for bad options to the "PublishServerDescriptor"
21049 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
21050 - Stop leaking memory on failing case of base32_decode, and make
21051 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
21052 - Don't try to download extrainfo documents when we're trying to
21053 fetch enough directory info to build a circuit: having enough
21054 info should get priority. Bugfix on 0.2.0.x.
21055 - Don't complain that "your server has not managed to confirm that its
21056 ports are reachable" if we haven't been able to build any circuits
21057 yet. Bug found by spending four hours without a v3 consensus. Bugfix
21059 - Detect the reason for failing to mmap a descriptor file we just
21060 wrote, and give a more useful log message. Fixes bug 533. Bugfix
21063 o Code simplifications and refactoring:
21064 - Remove support for the old bw_accounting file: we've been storing
21065 bandwidth accounting information in the state file since
21066 0.1.2.5-alpha. This may result in bandwidth accounting errors
21067 if you try to upgrade from 0.1.1.x or earlier, or if you try to
21068 downgrade to 0.1.1.x or earlier.
21069 - New convenience code to locate a file within the DataDirectory.
21070 - Move non-authority functionality out of dirvote.c.
21071 - Refactor the arguments for router_pick_{directory_|trusteddir}server
21072 so that they all take the same named flags.
21075 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
21076 Unix users an easy way to script their Tor process (e.g. by
21077 adjusting bandwidth based on the time of the day).
21080 Changes in version 0.2.0.8-alpha - 2007-10-12
21081 This eighth development snapshot fixes a crash bug that's been bothering
21082 us since February 2007, lets bridge authorities store a list of bridge
21083 descriptors they've seen, gets v3 directory voting closer to working,
21084 starts caching v3 directory consensus documents on directory mirrors,
21085 and fixes a variety of smaller issues including some minor memory leaks.
21087 o Major features (router descriptor cache):
21088 - Store routers in a file called cached-descriptors instead of in
21089 cached-routers. Initialize cached-descriptors from cached-routers
21090 if the old format is around. The new format allows us to store
21091 annotations along with descriptors.
21092 - Use annotations to record the time we received each descriptor, its
21093 source, and its purpose.
21094 - Disable the SETROUTERPURPOSE controller command: it is now
21096 - Controllers should now specify cache=no or cache=yes when using
21097 the +POSTDESCRIPTOR command.
21098 - Bridge authorities now write bridge descriptors to disk, meaning
21099 we can export them to other programs and begin distributing them
21102 o Major features (directory authorities):
21103 - When a v3 authority is missing votes or signatures, it now tries
21105 - Directory authorities track weighted fractional uptime as well as
21106 weighted mean-time-between failures. WFU is suitable for deciding
21107 whether a node is "usually up", while MTBF is suitable for deciding
21108 whether a node is "likely to stay up." We need both, because
21109 "usually up" is a good requirement for guards, while "likely to
21110 stay up" is a good requirement for long-lived connections.
21112 o Major features (v3 directory system):
21113 - Caches now download v3 network status documents as needed,
21114 and download the descriptors listed in them.
21115 - All hosts now attempt to download and keep fresh v3 authority
21116 certificates, and re-attempt after failures.
21117 - More internal-consistency checks for vote parsing.
21119 o Major bugfixes (crashes):
21120 - If a connection is shut down abruptly because of something that
21121 happened inside connection_flushed_some(), do not call
21122 connection_finished_flushing(). Should fix bug 451. Bugfix on
21125 o Major bugfixes (performance):
21126 - Fix really bad O(n^2) performance when parsing a long list of
21127 routers: Instead of searching the entire list for an "extra-info "
21128 string which usually wasn't there, once for every routerinfo
21129 we read, just scan lines forward until we find one we like.
21131 - When we add data to a write buffer in response to the data on that
21132 write buffer getting low because of a flush, do not consider the
21133 newly added data as a candidate for immediate flushing, but rather
21134 make it wait until the next round of writing. Otherwise, we flush
21135 and refill recursively, and a single greedy TLS connection can
21136 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
21138 o Minor features (v3 authority system):
21139 - Add more ways for tools to download the votes that lead to the
21141 - Send a 503 when low on bandwidth and a vote, consensus, or
21142 certificate is requested.
21143 - If-modified-since is now implemented properly for all kinds of
21144 certificate requests.
21146 o Minor bugfixes (network statuses):
21147 - Tweak the implementation of proposal 109 slightly: allow at most
21148 two Tor servers on the same IP address, except if it's the location
21149 of a directory authority, in which case allow five. Bugfix on
21152 o Minor bugfixes (controller):
21153 - When sending a status event to the controller telling it that an
21154 OR address is reachable, set the port correctly. (Previously we
21155 were reporting the dir port.) Bugfix on 0.1.2.x.
21157 o Minor bugfixes (v3 directory system):
21158 - Fix logic to look up a cert by its signing key digest. Bugfix on
21160 - Only change the reply to a vote to "OK" if it's not already
21161 set. This gets rid of annoying "400 OK" log messages, which may
21162 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
21163 - When we get a valid consensus, recompute the voting schedule.
21164 - Base the valid-after time of a vote on the consensus voting
21165 schedule, not on our preferred schedule.
21166 - Make the return values and messages from signature uploads and
21167 downloads more sensible.
21168 - Fix a memory leak when serving votes and consensus documents, and
21169 another when serving certificates.
21171 o Minor bugfixes (performance):
21172 - Use a slightly simpler string hashing algorithm (copying Python's
21173 instead of Java's) and optimize our digest hashing algorithm to take
21174 advantage of 64-bit platforms and to remove some possibly-costly
21176 - Fix a minor memory leak whenever we parse guards from our state
21177 file. Bugfix on 0.2.0.7-alpha.
21178 - Fix a minor memory leak whenever we write out a file. Bugfix on
21180 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
21181 command. Bugfix on 0.2.0.5-alpha.
21183 o Minor bugfixes (portability):
21184 - On some platforms, accept() can return a broken address. Detect
21185 this more quietly, and deal accordingly. Fixes bug 483.
21186 - Stop calling tor_strlower() on uninitialized memory in some cases.
21187 Bugfix in 0.2.0.7-alpha.
21189 o Minor bugfixes (usability):
21190 - Treat some 403 responses from directory servers as INFO rather than
21191 WARN-severity events.
21192 - It's not actually an error to find a non-pending entry in the DNS
21193 cache when canceling a pending resolve. Don't log unless stuff is
21194 fishy. Resolves bug 463.
21196 o Minor bugfixes (anonymity):
21197 - Never report that we've used more bandwidth than we're willing to
21198 relay: it leaks how much non-relay traffic we're using. Resolves
21200 - When looking for a circuit to cannibalize, consider family as well
21201 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
21202 circuit cannibalization).
21204 o Code simplifications and refactoring:
21205 - Make a bunch of functions static. Remove some dead code.
21206 - Pull out about a third of the really big routerlist.c; put it in a
21207 new module, networkstatus.c.
21208 - Merge the extra fields in local_routerstatus_t back into
21209 routerstatus_t: we used to need one routerstatus_t for each
21210 authority's opinion, plus a local_routerstatus_t for the locally
21211 computed consensus opinion. To save space, we put the locally
21212 modified fields into local_routerstatus_t, and only the common
21213 stuff into routerstatus_t. But once v3 directories are in use,
21214 clients and caches will no longer need to hold authority opinions;
21215 thus, the rationale for keeping the types separate is now gone.
21216 - Make the code used to reschedule and reattempt downloads more
21218 - Turn all 'Are we a directory server/mirror?' logic into a call to
21220 - Remove the code to generate the oldest (v1) directory format.
21221 The code has been disabled since 0.2.0.5-alpha.
21224 Changes in version 0.2.0.7-alpha - 2007-09-21
21225 This seventh development snapshot makes bridges work again, makes bridge
21226 authorities work for the first time, fixes two huge performance flaws
21227 in hidden services, and fixes a variety of minor issues.
21229 o New directory authorities:
21230 - Set up moria1 and tor26 as the first v3 directory authorities. See
21231 doc/spec/dir-spec.txt for details on the new directory design.
21233 o Major bugfixes (crashes):
21234 - Fix possible segfaults in functions called from
21235 rend_process_relay_cell(). Bugfix on 0.1.2.x.
21237 o Major bugfixes (bridges):
21238 - Fix a bug that made servers send a "404 Not found" in response to
21239 attempts to fetch their server descriptor. This caused Tor servers
21240 to take many minutes to establish reachability for their DirPort,
21241 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
21242 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
21243 users configure that and specify a bridge with an identity
21244 fingerprint, now they will lookup the bridge descriptor at the
21245 default bridge authority via a one-hop tunnel, but once circuits
21246 are established they will switch to a three-hop tunnel for later
21247 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
21249 o Major bugfixes (hidden services):
21250 - Hidden services were choosing introduction points uniquely by
21251 hexdigest, but when constructing the hidden service descriptor
21252 they merely wrote the (potentially ambiguous) nickname.
21253 - Clients now use the v2 intro format for hidden service
21254 connections: they specify their chosen rendezvous point by identity
21255 digest rather than by (potentially ambiguous) nickname. Both
21256 are bugfixes on 0.1.2.x, and they could speed up hidden service
21257 connections dramatically. Thanks to Karsten Loesing.
21259 o Minor features (security):
21260 - As a client, do not believe any server that tells us that an
21261 address maps to an internal address space.
21262 - Make it possible to enable HashedControlPassword and
21263 CookieAuthentication at the same time.
21265 o Minor features (guard nodes):
21266 - Tag every guard node in our state file with the version that
21267 we believe added it, or with our own version if we add it. This way,
21268 if a user temporarily runs an old version of Tor and then switches
21269 back to a new one, she doesn't automatically lose her guards.
21271 o Minor features (speed):
21272 - When implementing AES counter mode, update only the portions of the
21273 counter buffer that need to change, and don't keep separate
21274 network-order and host-order counters when they are the same (i.e.,
21275 on big-endian hosts.)
21277 o Minor features (controller):
21278 - Accept LF instead of CRLF on controller, since some software has a
21279 hard time generating real Internet newlines.
21280 - Add GETINFO values for the server status events
21281 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
21284 o Removed features:
21285 - Routers no longer include bandwidth-history lines in their
21286 descriptors; this information is already available in extra-info
21287 documents, and including it in router descriptors took up 60%
21288 (!) of compressed router descriptor downloads. Completes
21289 implementation of proposal 104.
21290 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
21291 and TorControl.py, as they use the old v0 controller protocol,
21292 and are obsoleted by TorFlow anyway.
21293 - Drop support for v1 rendezvous descriptors, since we never used
21294 them anyway, and the code has probably rotted by now. Based on
21295 patch from Karsten Loesing.
21296 - On OSX, stop warning the user that kqueue support in libevent is
21297 "experimental", since it seems to have worked fine for ages.
21300 - When generating information telling us how to extend to a given
21301 router, do not try to include the nickname if it is absent. Fixes
21302 bug 467. Bugfix on 0.2.0.3-alpha.
21303 - Fix a user-triggerable (but not remotely-triggerable) segfault
21304 in expand_filename(). Bugfix on 0.1.2.x.
21305 - Fix a memory leak when freeing incomplete requests from DNSPort.
21306 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
21307 - Don't try to access (or alter) the state file when running
21308 --list-fingerprint or --verify-config or --hash-password. (Resolves
21309 bug 499.) Bugfix on 0.1.2.x.
21310 - Servers used to decline to publish their DirPort if their
21311 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
21312 were below a threshold. Now they only look at BandwidthRate and
21313 RelayBandwidthRate. Bugfix on 0.1.2.x.
21314 - Remove an optimization in the AES counter-mode code that assumed
21315 that the counter never exceeded 2^68. When the counter can be set
21316 arbitrarily as an IV (as it is by Karsten's new hidden services
21317 code), this assumption no longer holds. Bugfix on 0.1.2.x.
21318 - Resume listing "AUTHORITY" flag for authorities in network status.
21319 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
21321 o Code simplifications and refactoring:
21322 - Revamp file-writing logic so we don't need to have the entire
21323 contents of a file in memory at once before we write to disk. Tor,
21325 - Turn "descriptor store" into a full-fledged type.
21326 - Move all NT services code into a separate source file.
21327 - Unify all code that computes medians, percentile elements, etc.
21328 - Get rid of a needless malloc when parsing address policies.
21331 Changes in version 0.1.2.17 - 2007-08-30
21332 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
21333 X bundles. Vidalia 0.0.14 makes authentication required for the
21334 ControlPort in the default configuration, which addresses important
21335 security risks. Everybody who uses Vidalia (or another controller)
21338 In addition, this Tor update fixes major load balancing problems with
21339 path selection, which should speed things up a lot once many people
21342 o Major bugfixes (security):
21343 - We removed support for the old (v0) control protocol. It has been
21344 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
21345 become more of a headache than it's worth.
21347 o Major bugfixes (load balancing):
21348 - When choosing nodes for non-guard positions, weight guards
21349 proportionally less, since they already have enough load. Patch
21351 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
21352 will allow fast Tor servers to get more attention.
21353 - When we're upgrading from an old Tor version, forget our current
21354 guards and pick new ones according to the new weightings. These
21355 three load balancing patches could raise effective network capacity
21356 by a factor of four. Thanks to Mike Perry for measurements.
21358 o Major bugfixes (stream expiration):
21359 - Expire not-yet-successful application streams in all cases if
21360 they've been around longer than SocksTimeout. Right now there are
21361 some cases where the stream will live forever, demanding a new
21362 circuit every 15 seconds. Fixes bug 454; reported by lodger.
21364 o Minor features (controller):
21365 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
21366 is valid before any authentication has been received. It tells
21367 a controller what kind of authentication is expected, and what
21368 protocol is spoken. Implements proposal 119.
21370 o Minor bugfixes (performance):
21371 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
21372 greatly speeding up loading cached-routers from disk on startup.
21373 - Disable sentinel-based debugging for buffer code: we squashed all
21374 the bugs that this was supposed to detect a long time ago, and now
21375 its only effect is to change our buffer sizes from nice powers of
21376 two (which platform mallocs tend to like) to values slightly over
21377 powers of two (which make some platform mallocs sad).
21379 o Minor bugfixes (misc):
21380 - If exit bandwidth ever exceeds one third of total bandwidth, then
21381 use the correct formula to weight exit nodes when choosing paths.
21382 Based on patch from Mike Perry.
21383 - Choose perfectly fairly among routers when choosing by bandwidth and
21384 weighting by fraction of bandwidth provided by exits. Previously, we
21385 would choose with only approximate fairness, and correct ourselves
21386 if we ran off the end of the list.
21387 - If we require CookieAuthentication but we fail to write the
21388 cookie file, we would warn but not exit, and end up in a state
21389 where no controller could authenticate. Now we exit.
21390 - If we require CookieAuthentication, stop generating a new cookie
21391 every time we change any piece of our config.
21392 - Refuse to start with certain directory authority keys, and
21393 encourage people using them to stop.
21394 - Terminate multi-line control events properly. Original patch
21396 - Fix a minor memory leak when we fail to find enough suitable
21397 servers to choose a circuit.
21398 - Stop leaking part of the descriptor when we run into a particularly
21399 unparseable piece of it.
21402 Changes in version 0.2.0.6-alpha - 2007-08-26
21403 This sixth development snapshot features a new Vidalia version in the
21404 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
21405 the ControlPort in the default configuration, which addresses important
21408 In addition, this snapshot fixes major load balancing problems
21409 with path selection, which should speed things up a lot once many
21410 people have upgraded. The directory authorities also use a new
21411 mean-time-between-failure approach to tracking which servers are stable,
21412 rather than just looking at the most recent uptime.
21414 o New directory authorities:
21415 - Set up Tonga as the default bridge directory authority.
21418 - Directory authorities now track servers by weighted
21419 mean-times-between-failures. When we have 4 or more days of data,
21420 use measured MTBF rather than declared uptime to decide whether
21421 to call a router Stable. Implements proposal 108.
21423 o Major bugfixes (load balancing):
21424 - When choosing nodes for non-guard positions, weight guards
21425 proportionally less, since they already have enough load. Patch
21427 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
21428 will allow fast Tor servers to get more attention.
21429 - When we're upgrading from an old Tor version, forget our current
21430 guards and pick new ones according to the new weightings. These
21431 three load balancing patches could raise effective network capacity
21432 by a factor of four. Thanks to Mike Perry for measurements.
21434 o Major bugfixes (descriptor parsing):
21435 - Handle unexpected whitespace better in malformed descriptors. Bug
21436 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
21439 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
21440 GETINFO for Torstat to use until it can switch to using extrainfos.
21441 - Optionally (if built with -DEXPORTMALLINFO) export the output
21442 of mallinfo via http, as tor/mallinfo.txt. Only accessible
21446 - Do not intermix bridge routers with controller-added
21447 routers. (Bugfix on 0.2.0.x)
21448 - Do not fail with an assert when accept() returns an unexpected
21449 address family. Addresses but does not wholly fix bug 483. (Bugfix
21451 - Let directory authorities startup even when they can't generate
21452 a descriptor immediately, e.g. because they don't know their
21454 - Stop putting the authentication cookie in a file called "0"
21455 in your working directory if you don't specify anything for the
21456 new CookieAuthFile option. Reported by Matt Edman.
21457 - Make it possible to read the PROTOCOLINFO response in a way that
21458 conforms to our control-spec. Reported by Matt Edman.
21459 - Fix a minor memory leak when we fail to find enough suitable
21460 servers to choose a circuit. Bugfix on 0.1.2.x.
21461 - Stop leaking part of the descriptor when we run into a particularly
21462 unparseable piece of it. Bugfix on 0.1.2.x.
21463 - Unmap the extrainfo cache file on exit.
21466 Changes in version 0.2.0.5-alpha - 2007-08-19
21467 This fifth development snapshot fixes compilation on Windows again;
21468 fixes an obnoxious client-side bug that slowed things down and put
21469 extra load on the network; gets us closer to using the v3 directory
21470 voting scheme; makes it easier for Tor controllers to use cookie-based
21471 authentication; and fixes a variety of other bugs.
21473 o Removed features:
21474 - Version 1 directories are no longer generated in full. Instead,
21475 authorities generate and serve "stub" v1 directories that list
21476 no servers. This will stop Tor versions 0.1.0.x and earlier from
21477 working, but (for security reasons) nobody should be running those
21480 o Major bugfixes (compilation, 0.2.0.x):
21481 - Try to fix Win32 compilation again: improve checking for IPv6 types.
21482 - Try to fix MSVC compilation: build correctly on platforms that do
21483 not define s6_addr16 or s6_addr32.
21484 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
21487 o Major bugfixes (stream expiration):
21488 - Expire not-yet-successful application streams in all cases if
21489 they've been around longer than SocksTimeout. Right now there are
21490 some cases where the stream will live forever, demanding a new
21491 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
21492 reported by lodger.
21494 o Minor features (directory servers):
21495 - When somebody requests a list of statuses or servers, and we have
21496 none of those, return a 404 rather than an empty 200.
21498 o Minor features (directory voting):
21499 - Store v3 consensus status consensuses on disk, and reload them
21502 o Minor features (security):
21503 - Warn about unsafe ControlPort configurations.
21504 - Refuse to start with certain directory authority keys, and
21505 encourage people using them to stop.
21507 o Minor features (controller):
21508 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
21509 is valid before any authentication has been received. It tells
21510 a controller what kind of authentication is expected, and what
21511 protocol is spoken. Implements proposal 119.
21512 - New config option CookieAuthFile to choose a new location for the
21513 cookie authentication file, and config option
21514 CookieAuthFileGroupReadable to make it group-readable.
21516 o Minor features (unit testing):
21517 - Add command-line arguments to unit-test executable so that we can
21518 invoke any chosen test from the command line rather than having
21519 to run the whole test suite at once; and so that we can turn on
21520 logging for the unit tests.
21522 o Minor bugfixes (on 0.1.2.x):
21523 - If we require CookieAuthentication but we fail to write the
21524 cookie file, we would warn but not exit, and end up in a state
21525 where no controller could authenticate. Now we exit.
21526 - If we require CookieAuthentication, stop generating a new cookie
21527 every time we change any piece of our config.
21528 - When loading bandwidth history, do not believe any information in
21529 the future. Fixes bug 434.
21530 - When loading entry guard information, do not believe any information
21532 - When we have our clock set far in the future and generate an
21533 onion key, then re-set our clock to be correct, we should not stop
21534 the onion key from getting rotated.
21535 - Clean up torrc sample config file.
21536 - Do not automatically run configure from autogen.sh. This
21537 non-standard behavior tended to annoy people who have built other
21540 o Minor bugfixes (on 0.2.0.x):
21541 - Fix a bug with AutomapHostsOnResolve that would always cause
21542 the second request to fail. Bug reported by Kate. Bugfix on
21544 - Fix a bug in ADDRMAP controller replies that would sometimes
21545 try to print a NULL. Patch from tup.
21546 - Read v3 directory authority keys from the right location.
21547 - Numerous bugfixes to directory voting code.
21550 Changes in version 0.1.2.16 - 2007-08-01
21551 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
21552 remote attacker in certain situations to rewrite the user's torrc
21553 configuration file. This can completely compromise anonymity of users
21554 in most configurations, including those running the Vidalia bundles,
21555 TorK, etc. Or worse.
21557 o Major security fixes:
21558 - Close immediately after missing authentication on control port;
21559 do not allow multiple authentication attempts.
21562 Changes in version 0.2.0.4-alpha - 2007-08-01
21563 This fourth development snapshot fixes a critical security vulnerability
21564 for most users, specifically those running Vidalia, TorK, etc. Everybody
21565 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
21567 o Major security fixes:
21568 - Close immediately after missing authentication on control port;
21569 do not allow multiple authentication attempts.
21571 o Major bugfixes (compilation):
21572 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
21575 o Minor features (performance):
21576 - Be even more aggressive about releasing RAM from small
21577 empty buffers. Thanks to our free-list code, this shouldn't be too
21578 performance-intensive.
21579 - Disable sentinel-based debugging for buffer code: we squashed all
21580 the bugs that this was supposed to detect a long time ago, and
21581 now its only effect is to change our buffer sizes from nice
21582 powers of two (which platform mallocs tend to like) to values
21583 slightly over powers of two (which make some platform mallocs sad).
21584 - Log malloc statistics from mallinfo() on platforms where it
21588 Changes in version 0.2.0.3-alpha - 2007-07-29
21589 This third development snapshot introduces new experimental
21590 blocking-resistance features and a preliminary version of the v3
21591 directory voting design, and includes many other smaller features
21595 - The first pieces of our "bridge" design for blocking-resistance
21596 are implemented. People can run bridge directory authorities;
21597 people can run bridges; and people can configure their Tor clients
21598 with a set of bridges to use as the first hop into the Tor network.
21599 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
21601 - Create listener connections before we setuid to the configured
21602 User and Group. Now non-Windows users can choose port values
21603 under 1024, start Tor as root, and have Tor bind those ports
21604 before it changes to another UID. (Windows users could already
21606 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
21607 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
21608 on "vserver" accounts. (Patch from coderman.)
21609 - Be even more aggressive about separating local traffic from relayed
21610 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
21612 o Major features (experimental):
21613 - First cut of code for "v3 dir voting": directory authorities will
21614 vote on a common network status document rather than each publishing
21615 their own opinion. This code needs more testing and more corner-case
21616 handling before it's ready for use.
21619 - Directory authorities now call routers Fast if their bandwidth is
21620 at least 100KB/s, and consider their bandwidth adequate to be a
21621 Guard if it is at least 250KB/s, no matter the medians. This fix
21622 complements proposal 107. [Bugfix on 0.1.2.x]
21623 - Directory authorities now never mark more than 3 servers per IP as
21624 Valid and Running. (Implements proposal 109, by Kevin Bauer and
21626 - Minor change to organizationName and commonName generation
21627 procedures in TLS certificates during Tor handshakes, to invalidate
21628 some earlier censorware approaches. This is not a long-term
21629 solution, but applying it will give us a bit of time to look into
21630 the epidemiology of countermeasures as they spread.
21632 o Major bugfixes (directory):
21633 - Rewrite directory tokenization code to never run off the end of
21634 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
21636 o Minor features (controller):
21637 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
21638 match requests to applications. (Patch from Robert Hogan.)
21639 - Report address and port correctly on connections to DNSPort. (Patch
21640 from Robert Hogan.)
21641 - Add a RESOLVE command to launch hostname lookups. (Original patch
21642 from Robert Hogan.)
21643 - Add GETINFO status/enough-dir-info to let controllers tell whether
21644 Tor has downloaded sufficient directory information. (Patch
21646 - You can now use the ControlSocket option to tell Tor to listen for
21647 controller connections on Unix domain sockets on systems that
21648 support them. (Patch from Peter Palfrader.)
21649 - STREAM NEW events are generated for DNSPort requests and for
21650 tunneled directory connections. (Patch from Robert Hogan.)
21651 - New "GETINFO address-mappings/*" command to get address mappings
21652 with expiry information. "addr-mappings/*" is now deprecated.
21655 o Minor features (misc):
21656 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
21658 - The tor-gencert tool for v3 directory authorities now creates all
21659 files as readable to the file creator only, and write-protects
21660 the authority identity key.
21661 - When dumping memory usage, list bytes used in buffer memory
21663 - When running with dmalloc, dump more stats on hup and on exit.
21664 - Directory authorities now fail quickly and (relatively) harmlessly
21665 if they generate a network status document that is somehow
21668 o Traffic load balancing improvements:
21669 - If exit bandwidth ever exceeds one third of total bandwidth, then
21670 use the correct formula to weight exit nodes when choosing paths.
21671 (Based on patch from Mike Perry.)
21672 - Choose perfectly fairly among routers when choosing by bandwidth and
21673 weighting by fraction of bandwidth provided by exits. Previously, we
21674 would choose with only approximate fairness, and correct ourselves
21675 if we ran off the end of the list. [Bugfix on 0.1.2.x]
21677 o Performance improvements:
21678 - Be more aggressive with freeing buffer RAM or putting it on the
21680 - Use Critical Sections rather than Mutexes for synchronizing threads
21681 on win32; Mutexes are heavier-weight, and designed for synchronizing
21684 o Deprecated and removed features:
21685 - RedirectExits is now deprecated.
21686 - Stop allowing address masks that do not correspond to bit prefixes.
21687 We have warned about these for a really long time; now it's time
21688 to reject them. (Patch from croup.)
21690 o Minor bugfixes (directory):
21691 - Fix another crash bug related to extra-info caching. (Bug found by
21692 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
21693 - Directories no longer return a "304 not modified" when they don't
21694 have the networkstatus the client asked for. Also fix a memory
21695 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
21696 - We had accidentally labelled 0.1.2.x directory servers as not
21697 suitable for begin_dir requests, and had labelled no directory
21698 servers as suitable for uploading extra-info documents. [Bugfix
21701 o Minor bugfixes (dns):
21702 - Fix a crash when DNSPort is set more than once. (Patch from Robert
21703 Hogan.) [Bugfix on 0.2.0.2-alpha]
21704 - Add DNSPort connections to the global connection list, so that we
21705 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
21707 - Fix a dangling reference that could lead to a crash when DNSPort is
21708 changed or closed (Patch from Robert Hogan.) [Bugfix on
21711 o Minor bugfixes (controller):
21712 - Provide DNS expiry times in GMT, not in local time. For backward
21713 compatibility, ADDRMAP events only provide GMT expiry in an extended
21714 field. "GETINFO address-mappings" always does the right thing.
21715 - Use CRLF line endings properly in NS events.
21716 - Terminate multi-line control events properly. (Original patch
21717 from tup.) [Bugfix on 0.1.2.x-alpha]
21718 - Do not include spaces in SOURCE_ADDR fields in STREAM
21719 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
21722 Changes in version 0.1.2.15 - 2007-07-17
21723 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
21724 problems, fixes compilation on BSD, and fixes a variety of other
21725 bugs. Everybody should upgrade.
21727 o Major bugfixes (compilation):
21728 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
21730 o Major bugfixes (crashes):
21731 - Try even harder not to dereference the first character after
21732 an mmap(). Reported by lodger.
21733 - Fix a crash bug in directory authorities when we re-number the
21734 routerlist while inserting a new router.
21735 - When the cached-routers file is an even multiple of the page size,
21736 don't run off the end and crash. (Fixes bug 455; based on idea
21738 - Fix eventdns.c behavior on Solaris: It is critical to include
21739 orconfig.h _before_ sys/types.h, so that we can get the expected
21740 definition of _FILE_OFFSET_BITS.
21742 o Major bugfixes (security):
21743 - Fix a possible buffer overrun when using BSD natd support. Bug
21745 - When sending destroy cells from a circuit's origin, don't include
21746 the reason for tearing down the circuit. The spec says we didn't,
21747 and now we actually don't. Reported by lodger.
21748 - Keep streamids from different exits on a circuit separate. This
21749 bug may have allowed other routers on a given circuit to inject
21750 cells into streams. Reported by lodger; fixes bug 446.
21751 - If there's a never-before-connected-to guard node in our list,
21752 never choose any guards past it. This way we don't expand our
21753 guard list unless we need to.
21755 o Minor bugfixes (guard nodes):
21756 - Weight guard selection by bandwidth, so that low-bandwidth nodes
21757 don't get overused as guards.
21759 o Minor bugfixes (directory):
21760 - Correctly count the number of authorities that recommend each
21761 version. Previously, we were under-counting by 1.
21762 - Fix a potential crash bug when we load many server descriptors at
21763 once and some of them make others of them obsolete. Fixes bug 458.
21765 o Minor bugfixes (hidden services):
21766 - Stop tearing down the whole circuit when the user asks for a
21767 connection to a port that the hidden service didn't configure.
21770 o Minor bugfixes (misc):
21771 - On Windows, we were preventing other processes from reading
21772 cached-routers while Tor was running. Reported by janbar.
21773 - Fix a possible (but very unlikely) bug in picking routers by
21774 bandwidth. Add a log message to confirm that it is in fact
21775 unlikely. Patch from lodger.
21776 - Backport a couple of memory leak fixes.
21777 - Backport miscellaneous cosmetic bugfixes.
21780 Changes in version 0.2.0.2-alpha - 2007-06-02
21781 o Major bugfixes on 0.2.0.1-alpha:
21782 - Fix an assertion failure related to servers without extra-info digests.
21783 Resolves bugs 441 and 442.
21785 o Minor features (directory):
21786 - Support "If-Modified-Since" when answering HTTP requests for
21787 directories, running-routers documents, and network-status documents.
21788 (There's no need to support it for router descriptors, since those
21789 are downloaded by descriptor digest.)
21791 o Minor build issues:
21792 - Clear up some MIPSPro compiler warnings.
21793 - When building from a tarball on a machine that happens to have SVK
21794 installed, report the micro-revision as whatever version existed
21795 in the tarball, not as "x".
21798 Changes in version 0.2.0.1-alpha - 2007-06-01
21799 This early development snapshot provides new features for people running
21800 Tor as both a client and a server (check out the new RelayBandwidth
21801 config options); lets Tor run as a DNS proxy; and generally moves us
21802 forward on a lot of fronts.
21804 o Major features, server usability:
21805 - New config options RelayBandwidthRate and RelayBandwidthBurst:
21806 a separate set of token buckets for relayed traffic. Right now
21807 relayed traffic is defined as answers to directory requests, and
21808 OR connections that don't have any local circuits on them.
21810 o Major features, client usability:
21811 - A client-side DNS proxy feature to replace the need for
21812 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
21813 for DNS requests on port 9999, use the Tor network to resolve them
21814 anonymously, and send the reply back like a regular DNS server.
21815 The code still only implements a subset of DNS.
21816 - Make PreferTunneledDirConns and TunnelDirConns work even when
21817 we have no cached directory info. This means Tor clients can now
21818 do all of their connections protected by TLS.
21820 o Major features, performance and efficiency:
21821 - Directory authorities accept and serve "extra info" documents for
21822 routers. These documents contain fields from router descriptors
21823 that aren't usually needed, and that use a lot of excess
21824 bandwidth. Once these fields are removed from router descriptors,
21825 the bandwidth savings should be about 60%. [Partially implements
21827 - Servers upload extra-info documents to any authority that accepts
21828 them. Authorities (and caches that have been configured to download
21829 extra-info documents) download them as needed. [Partially implements
21831 - Change the way that Tor buffers data that it is waiting to write.
21832 Instead of queueing data cells in an enormous ring buffer for each
21833 client->OR or OR->OR connection, we now queue cells on a separate
21834 queue for each circuit. This lets us use less slack memory, and
21835 will eventually let us be smarter about prioritizing different kinds
21837 - Use memory pools to allocate cells with better speed and memory
21838 efficiency, especially on platforms where malloc() is inefficient.
21839 - Stop reading on edge connections when their corresponding circuit
21840 buffers are full; start again as the circuits empty out.
21842 o Major features, other:
21843 - Add an HSAuthorityRecordStats option that hidden service authorities
21844 can use to track statistics of overall hidden service usage without
21845 logging information that would be very useful to an attacker.
21846 - Start work implementing multi-level keys for directory authorities:
21847 Add a standalone tool to generate key certificates. (Proposal 103.)
21850 - Directory authorities now call routers Stable if they have an
21851 uptime of at least 30 days, even if that's not the median uptime
21852 in the network. Implements proposal 107, suggested by Kevin Bauer
21855 o Minor fixes (resource management):
21856 - Count the number of open sockets separately from the number
21857 of active connection_t objects. This will let us avoid underusing
21858 our allocated connection limit.
21859 - We no longer use socket pairs to link an edge connection to an
21860 anonymous directory connection or a DirPort test connection.
21861 Instead, we track the link internally and transfer the data
21862 in-process. This saves two sockets per "linked" connection (at the
21863 client and at the server), and avoids the nasty Windows socketpair()
21865 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
21866 for every single inactive connection_t. Free items from the
21867 4k/16k-buffer free lists when they haven't been used for a while.
21869 o Minor features (build):
21870 - Make autoconf search for libevent, openssl, and zlib consistently.
21871 - Update deprecated macros in configure.in.
21872 - When warning about missing headers, tell the user to let us
21873 know if the compile succeeds anyway, so we can downgrade the
21875 - Include the current subversion revision as part of the version
21876 string: either fetch it directly if we're in an SVN checkout, do
21877 some magic to guess it if we're in an SVK checkout, or use
21878 the last-detected version if we're building from a .tar.gz.
21879 Use this version consistently in log messages.
21881 o Minor features (logging):
21882 - Always prepend "Bug: " to any log message about a bug.
21883 - Put a platform string (e.g. "Linux i686") in the startup log
21884 message, so when people paste just their logs, we know if it's
21885 OpenBSD or Windows or what.
21886 - When logging memory usage, break down memory used in buffers by
21889 o Minor features (directory system):
21890 - New config option V2AuthoritativeDirectory that all directory
21891 authorities should set. This will let future authorities choose
21892 not to serve V2 directory information.
21893 - Directory authorities allow multiple router descriptors and/or extra
21894 info documents to be uploaded in a single go. This will make
21895 implementing proposal 104 simpler.
21897 o Minor features (controller):
21898 - Add a new config option __DisablePredictedCircuits designed for
21899 use by the controller, when we don't want Tor to build any circuits
21901 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
21902 so we can exit from the middle of the circuit.
21903 - Implement "getinfo status/circuit-established".
21904 - Implement "getinfo status/version/..." so a controller can tell
21905 whether the current version is recommended, and whether any versions
21906 are good, and how many authorities agree. (Patch from shibz.)
21908 o Minor features (hidden services):
21909 - Allow multiple HiddenServicePort directives with the same virtual
21910 port; when they occur, the user is sent round-robin to one
21911 of the target ports chosen at random. Partially fixes bug 393 by
21912 adding limited ad-hoc round-robining.
21914 o Minor features (other):
21916 - Add a new AutomapHostsOnResolve option: when it is enabled, any
21917 resolve request for hosts matching a given pattern causes Tor to
21918 generate an internal virtual address mapping for that host. This
21919 allows DNSPort to work sensibly with hidden service users. By
21920 default, .exit and .onion addresses are remapped; the list of
21921 patterns can be reconfigured with AutomapHostsSuffixes.
21922 - Add an "-F" option to tor-resolve to force a resolve for a .onion
21923 address. Thanks to the AutomapHostsOnResolve option, this is no
21924 longer a completely silly thing to do.
21925 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
21926 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
21927 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
21928 minus 1 byte: the actual maximum declared bandwidth.
21930 o Removed features:
21931 - Removed support for the old binary "version 0" controller protocol.
21932 This has been deprecated since 0.1.1, and warnings have been issued
21933 since 0.1.2. When we encounter a v0 control message, we now send
21934 back an error and close the connection.
21935 - Remove the old "dns worker" server DNS code: it hasn't been default
21936 since 0.1.2.2-alpha, and all the servers seem to be using the new
21939 o Minor bugfixes (portability):
21940 - Even though Windows is equally happy with / and \ as path separators,
21941 try to use \ consistently on Windows and / consistently on Unix: it
21942 makes the log messages nicer.
21943 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
21944 - Read resolv.conf files correctly on platforms where read() returns
21945 partial results on small file reads.
21947 o Minor bugfixes (directory):
21948 - Correctly enforce that elements of directory objects do not appear
21949 more often than they are allowed to appear.
21950 - When we are reporting the DirServer line we just parsed, we were
21951 logging the second stanza of the key fingerprint, not the first.
21953 o Minor bugfixes (logging):
21954 - When we hit an EOF on a log (probably because we're shutting down),
21955 don't try to remove the log from the list: just mark it as
21956 unusable. (Bulletproofs against bug 222.)
21958 o Minor bugfixes (other):
21959 - In the exitlist script, only consider the most recently published
21960 server descriptor for each server. Also, when the user requests
21961 a list of servers that _reject_ connections to a given address,
21962 explicitly exclude the IPs that also have servers that accept
21963 connections to that address. (Resolves bug 405.)
21964 - Stop allowing hibernating servers to be "stable" or "fast".
21965 - On Windows, we were preventing other processes from reading
21966 cached-routers while Tor was running. (Reported by janbar)
21967 - Make the NodeFamilies config option work. (Reported by
21968 lodger -- it has never actually worked, even though we added it
21970 - Check return values from pthread_mutex functions.
21971 - Don't save non-general-purpose router descriptors to the disk cache,
21972 because we have no way of remembering what their purpose was when
21974 - Add even more asserts to hunt down bug 417.
21975 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
21976 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
21977 Add a log message to confirm that it is in fact unlikely.
21979 o Minor bugfixes (controller):
21980 - Make 'getinfo fingerprint' return a 551 error if we're not a
21981 server, so we match what the control spec claims we do. Reported
21983 - Fix a typo in an error message when extendcircuit fails that
21984 caused us to not follow the \r\n-based delimiter protocol. Reported
21987 o Code simplifications and refactoring:
21988 - Stop passing around circuit_t and crypt_path_t pointers that are
21989 implicit in other procedure arguments.
21990 - Drop the old code to choke directory connections when the
21991 corresponding OR connections got full: thanks to the cell queue
21992 feature, OR conns don't get full any more.
21993 - Make dns_resolve() handle attaching connections to circuits
21994 properly, so the caller doesn't have to.
21995 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
21996 - Keep the connection array as a dynamic smartlist_t, rather than as
21997 a fixed-sized array. This is important, as the number of connections
21998 is becoming increasingly decoupled from the number of sockets.
22001 Changes in version 0.1.2.14 - 2007-05-25
22002 Tor 0.1.2.14 changes the addresses of two directory authorities (this
22003 change especially affects those who serve or use hidden services),
22004 and fixes several other crash- and security-related bugs.
22006 o Directory authority changes:
22007 - Two directory authorities (moria1 and moria2) just moved to new
22008 IP addresses. This change will particularly affect those who serve
22009 or use hidden services.
22011 o Major bugfixes (crashes):
22012 - If a directory server runs out of space in the connection table
22013 as it's processing a begin_dir request, it will free the exit stream
22014 but leave it attached to the circuit, leading to unpredictable
22015 behavior. (Reported by seeess, fixes bug 425.)
22016 - Fix a bug in dirserv_remove_invalid() that would cause authorities
22017 to corrupt memory under some really unlikely scenarios.
22018 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
22019 - Avoid segfaults when reading from mmaped descriptor file. (Reported
22022 o Major bugfixes (security):
22023 - When choosing an entry guard for a circuit, avoid using guards
22024 that are in the same family as the chosen exit -- not just guards
22025 that are exactly the chosen exit. (Reported by lodger.)
22027 o Major bugfixes (resource management):
22028 - If a directory authority is down, skip it when deciding where to get
22029 networkstatus objects or descriptors. Otherwise we keep asking
22030 every 10 seconds forever. Fixes bug 384.
22031 - Count it as a failure if we fetch a valid network-status but we
22032 don't want to keep it. Otherwise we'll keep fetching it and keep
22033 not wanting to keep it. Fixes part of bug 422.
22034 - If all of our dirservers have given us bad or no networkstatuses
22035 lately, then stop hammering them once per minute even when we
22036 think they're failed. Fixes another part of bug 422.
22039 - Actually set the purpose correctly for descriptors inserted with
22040 purpose=controller.
22041 - When we have k non-v2 authorities in our DirServer config,
22042 we ignored the last k authorities in the list when updating our
22044 - Correctly back-off from requesting router descriptors that we are
22045 having a hard time downloading.
22046 - Read resolv.conf files correctly on platforms where read() returns
22047 partial results on small file reads.
22048 - Don't rebuild the entire router store every time we get 32K of
22049 routers: rebuild it when the journal gets very large, or when
22050 the gaps in the store get very large.
22053 - When routers publish SVN revisions in their router descriptors,
22054 authorities now include those versions correctly in networkstatus
22056 - Warn when using a version of libevent before 1.3b to run a server on
22057 OSX or BSD: these versions interact badly with userspace threads.
22060 Changes in version 0.1.2.13 - 2007-04-24
22061 This release features some major anonymity fixes, such as safer path
22062 selection; better client performance; faster bootstrapping, better
22063 address detection, and better DNS support for servers; write limiting as
22064 well as read limiting to make servers easier to run; and a huge pile of
22065 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
22067 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
22068 of the Freenode IRC network, remembering his patience and vision for
22069 free speech on the Internet.
22072 - Fix a memory leak when we ask for "all" networkstatuses and we
22073 get one we don't recognize.
22074 - Add more asserts to hunt down bug 417.
22075 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
22078 Changes in version 0.1.2.12-rc - 2007-03-16
22080 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
22081 directory information requested inside Tor connections (i.e. via
22082 begin_dir cells). It only triggered when the same connection was
22083 serving other data at the same time. Reported by seeess.
22086 - When creating a circuit via the controller, send a 'launched'
22087 event when we're done, so we follow the spec better.
22090 Changes in version 0.1.2.11-rc - 2007-03-15
22091 o Minor bugfixes (controller), reported by daejees:
22092 - Correct the control spec to match how the code actually responds
22093 to 'getinfo addr-mappings/*'.
22094 - The control spec described a GUARDS event, but the code
22095 implemented a GUARD event. Standardize on GUARD, but let people
22096 ask for GUARDS too.
22099 Changes in version 0.1.2.10-rc - 2007-03-07
22100 o Major bugfixes (Windows):
22101 - Do not load the NT services library functions (which may not exist)
22102 just to detect if we're a service trying to shut down. Now we run
22103 on Win98 and friends again.
22105 o Minor bugfixes (other):
22106 - Clarify a couple of log messages.
22107 - Fix a misleading socks5 error number.
22110 Changes in version 0.1.2.9-rc - 2007-03-02
22111 o Major bugfixes (Windows):
22112 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
22113 of the usual GCC "%llu". This prevents a bug when saving 64-bit
22114 int configuration values: the high-order 32 bits would get
22115 truncated. In particular, we were being bitten by the default
22116 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
22117 and maybe also bug 397.)
22119 o Minor bugfixes (performance):
22120 - Use OpenSSL's AES implementation on platforms where it's faster.
22121 This could save us as much as 10% CPU usage.
22123 o Minor bugfixes (server):
22124 - Do not rotate onion key immediately after setting it for the first
22127 o Minor bugfixes (directory authorities):
22128 - Stop calling servers that have been hibernating for a long time
22129 "stable". Also, stop letting hibernating or obsolete servers affect
22130 uptime and bandwidth cutoffs.
22131 - Stop listing hibernating servers in the v1 directory.
22133 o Minor bugfixes (hidden services):
22134 - Upload hidden service descriptors slightly less often, to reduce
22135 load on authorities.
22137 o Minor bugfixes (other):
22138 - Fix an assert that could trigger if a controller quickly set then
22139 cleared EntryNodes. Bug found by Udo van den Heuvel.
22140 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
22142 - Fix a potential race condition in the rpm installer. Found by
22144 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
22145 of 2 as indicating that the server is completely bad; it sometimes
22146 means that the server is just bad for the request in question. (may fix
22147 the last of bug 326.)
22148 - Disable encrypted directory connections when we don't have a server
22149 descriptor for the destination. We'll get this working again in
22153 Changes in version 0.1.2.8-beta - 2007-02-26
22154 o Major bugfixes (crashes):
22155 - Stop crashing when the controller asks us to resetconf more than
22156 one config option at once. (Vidalia 0.0.11 does this.)
22157 - Fix a crash that happened on Win98 when we're given command-line
22158 arguments: don't try to load NT service functions from advapi32.dll
22159 except when we need them. (Bug introduced in 0.1.2.7-alpha;
22161 - Fix a longstanding obscure crash bug that could occur when
22162 we run out of DNS worker processes. (Resolves bug 390.)
22164 o Major bugfixes (hidden services):
22165 - Correctly detect whether hidden service descriptor downloads are
22166 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
22168 o Major bugfixes (accounting):
22169 - When we start during an accounting interval before it's time to wake
22170 up, remember to wake up at the correct time. (May fix bug 342.)
22172 o Minor bugfixes (controller):
22173 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
22174 clear the corresponding on_circuit variable, and remember later
22175 that we don't need to send a redundant CLOSED event. Resolves part
22177 - Report events where a resolve succeeded or where we got a socks
22178 protocol error correctly, rather than calling both of them
22180 - Change reported stream target addresses to IP consistently when
22181 we finally get the IP from an exit node.
22182 - Send log messages to the controller even if they happen to be very
22185 o Minor bugfixes (other):
22186 - Display correct results when reporting which versions are
22187 recommended, and how recommended they are. (Resolves bug 383.)
22188 - Improve our estimates for directory bandwidth to be less random:
22189 guess that an unrecognized directory will have the average bandwidth
22190 from all known directories, not that it will have the average
22191 bandwidth from those directories earlier than it on the list.
22192 - If we start a server with ClientOnly 1, then set ClientOnly to 0
22193 and hup, stop triggering an assert based on an empty onion_key.
22194 - On platforms with no working mmap() equivalent, don't warn the
22195 user when cached-routers doesn't exist.
22196 - Warn the user when mmap() [or its equivalent] fails for some reason
22197 other than file-not-found.
22198 - Don't warn the user when cached-routers.new doesn't exist: that's
22199 perfectly fine when starting up for the first time.
22200 - When EntryNodes are configured, rebuild the guard list to contain,
22201 in order: the EntryNodes that were guards before; the rest of the
22202 EntryNodes; the nodes that were guards before.
22203 - Mask out all signals in sub-threads; only the libevent signal
22204 handler should be processing them. This should prevent some crashes
22205 on some machines using pthreads. (Patch from coderman.)
22206 - Fix switched arguments on memset in the implementation of
22207 tor_munmap() for systems with no mmap() call.
22208 - When Tor receives a router descriptor that it asked for, but
22209 no longer wants (because it has received fresh networkstatuses
22210 in the meantime), do not warn the user. Cache the descriptor if
22211 we're a cache; drop it if we aren't.
22212 - Make earlier entry guards _really_ get retried when the network
22214 - On a malformed DNS reply, always give an error to the corresponding
22216 - Build with recent libevents on platforms that do not define the
22217 nonstandard types "u_int8_t" and friends.
22219 o Minor features (controller):
22220 - Warn the user when an application uses the obsolete binary v0
22221 control protocol. We're planning to remove support for it during
22222 the next development series, so it's good to give people some
22224 - Add STREAM_BW events to report per-entry-stream bandwidth
22225 use. (Patch from Robert Hogan.)
22226 - Rate-limit SIGNEWNYM signals in response to controllers that
22227 impolitely generate them for every single stream. (Patch from
22228 mwenge; closes bug 394.)
22229 - Make REMAP stream events have a SOURCE (cache or exit), and
22230 make them generated in every case where we get a successful
22231 connected or resolved cell.
22233 o Minor bugfixes (performance):
22234 - Call router_have_min_dir_info half as often. (This is showing up in
22235 some profiles, but not others.)
22236 - When using GCC, make log_debug never get called at all, and its
22237 arguments never get evaluated, when no debug logs are configured.
22238 (This is showing up in some profiles, but not others.)
22241 - Remove some never-implemented options. Mark PathlenCoinWeight as
22243 - Implement proposal 106: Stop requiring clients to have well-formed
22244 certificates; stop checking nicknames in certificates. (Clients
22245 have certificates so that they can look like Tor servers, but in
22246 the future we might want to allow them to look like regular TLS
22247 clients instead. Nicknames in certificates serve no purpose other
22248 than making our protocol easier to recognize on the wire.)
22249 - Revise messages on handshake failure again to be even more clear about
22250 which are incoming connections and which are outgoing.
22251 - Discard any v1 directory info that's over 1 month old (for
22252 directories) or over 1 week old (for running-routers lists).
22253 - Do not warn when individual nodes in the configuration's EntryNodes,
22254 ExitNodes, etc are down: warn only when all possible nodes
22255 are down. (Fixes bug 348.)
22256 - Always remove expired routers and networkstatus docs before checking
22257 whether we have enough information to build circuits. (Fixes
22259 - Put a lower-bound on MaxAdvertisedBandwidth.
22262 Changes in version 0.1.2.7-alpha - 2007-02-06
22263 o Major bugfixes (rate limiting):
22264 - Servers decline directory requests much more aggressively when
22265 they're low on bandwidth. Otherwise they end up queueing more and
22266 more directory responses, which can't be good for latency.
22267 - But never refuse directory requests from local addresses.
22268 - Fix a memory leak when sending a 503 response for a networkstatus
22270 - Be willing to read or write on local connections (e.g. controller
22271 connections) even when the global rate limiting buckets are empty.
22272 - If our system clock jumps back in time, don't publish a negative
22273 uptime in the descriptor. Also, don't let the global rate limiting
22274 buckets go absurdly negative.
22275 - Flush local controller connection buffers periodically as we're
22276 writing to them, so we avoid queueing 4+ megabytes of data before
22279 o Major bugfixes (NT services):
22280 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
22281 command-line flag so that admins can override the default by saying
22282 "tor --service install --user "SomeUser"". This will not affect
22283 existing installed services. Also, warn the user that the service
22284 will look for its configuration file in the service user's
22285 %appdata% directory. (We can't do the 'hardwire the user's appdata
22286 directory' trick any more, since we may not have read access to that
22289 o Major bugfixes (other):
22290 - Previously, we would cache up to 16 old networkstatus documents
22291 indefinitely, if they came from nontrusted authorities. Now we
22292 discard them if they are more than 10 days old.
22293 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
22295 - Detect and reject malformed DNS responses containing circular
22297 - If exits are rare enough that we're not marking exits as guards,
22298 ignore exit bandwidth when we're deciding the required bandwidth
22300 - When we're handling a directory connection tunneled over Tor,
22301 don't fill up internal memory buffers with all the data we want
22302 to tunnel; instead, only add it if the OR connection that will
22303 eventually receive it has some room for it. (This can lead to
22304 slowdowns in tunneled dir connections; a better solution will have
22305 to wait for 0.2.0.)
22307 o Minor bugfixes (dns):
22308 - Add some defensive programming to eventdns.c in an attempt to catch
22309 possible memory-stomping bugs.
22310 - Detect and reject DNS replies containing IPv4 or IPv6 records with
22311 an incorrect number of bytes. (Previously, we would ignore the
22313 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
22314 in the correct order, and doesn't crash.
22315 - Free memory held in recently-completed DNS lookup attempts on exit.
22316 This was not a memory leak, but may have been hiding memory leaks.
22317 - Handle TTL values correctly on reverse DNS lookups.
22318 - Treat failure to parse resolv.conf as an error.
22320 o Minor bugfixes (other):
22321 - Fix crash with "tor --list-fingerprint" (reported by seeess).
22322 - When computing clock skew from directory HTTP headers, consider what
22323 time it was when we finished asking for the directory, not what
22325 - Expire socks connections if they spend too long waiting for the
22326 handshake to finish. Previously we would let them sit around for
22327 days, if the connecting application didn't close them either.
22328 - And if the socks handshake hasn't started, don't send a
22329 "DNS resolve socks failed" handshake reply; just close it.
22330 - Stop using C functions that OpenBSD's linker doesn't like.
22331 - Don't launch requests for descriptors unless we have networkstatuses
22332 from at least half of the authorities. This delays the first
22333 download slightly under pathological circumstances, but can prevent
22334 us from downloading a bunch of descriptors we don't need.
22335 - Do not log IPs with TLS failures for incoming TLS
22336 connections. (Fixes bug 382.)
22337 - If the user asks to use invalid exit nodes, be willing to use
22339 - Stop using the reserved ac_cv namespace in our configure script.
22340 - Call stat() slightly less often; use fstat() when possible.
22341 - Refactor the way we handle pending circuits when an OR connection
22342 completes or fails, in an attempt to fix a rare crash bug.
22343 - Only rewrite a conn's address based on X-Forwarded-For: headers
22344 if it's a parseable public IP address; and stop adding extra quotes
22345 to the resulting address.
22348 - Weight directory requests by advertised bandwidth. Now we can
22349 let servers enable write limiting but still allow most clients to
22350 succeed at their directory requests. (We still ignore weights when
22351 choosing a directory authority; I hope this is a feature.)
22354 - Create a new file ReleaseNotes which was the old ChangeLog. The
22355 new ChangeLog file now includes the summaries for all development
22357 - Check for addresses with invalid characters at the exit as well
22358 as at the client, and warn less verbosely when they fail. You can
22359 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
22360 - Adapt a patch from goodell to let the contrib/exitlist script
22361 take arguments rather than require direct editing.
22362 - Inform the server operator when we decide not to advertise a
22363 DirPort due to AccountingMax enabled or a low BandwidthRate. It
22364 was confusing Zax, so now we're hopefully more helpful.
22365 - Bring us one step closer to being able to establish an encrypted
22366 directory tunnel without knowing a descriptor first. Still not
22367 ready yet. As part of the change, now assume we can use a
22368 create_fast cell if we don't know anything about a router.
22369 - Allow exit nodes to use nameservers running on ports other than 53.
22370 - Servers now cache reverse DNS replies.
22371 - Add an --ignore-missing-torrc command-line option so that we can
22372 get the "use sensible defaults if the configuration file doesn't
22373 exist" behavior even when specifying a torrc location on the command
22376 o Minor features (controller):
22377 - Track reasons for OR connection failure; make these reasons
22378 available via the controller interface. (Patch from Mike Perry.)
22379 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
22380 can learn when clients are sending malformed hostnames to Tor.
22381 - Clean up documentation for controller status events.
22382 - Add a REMAP status to stream events to note that a stream's
22383 address has changed because of a cached address or a MapAddress
22387 Changes in version 0.1.2.6-alpha - 2007-01-09
22389 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
22390 connection handles more than 4 gigs in either direction, we crash.
22391 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
22392 advertised exit node, somebody might try to exit from us when
22393 we're bootstrapping and before we've built our descriptor yet.
22394 Refuse the connection rather than crashing.
22397 - Warn if we (as a server) find that we've resolved an address that we
22398 weren't planning to resolve.
22399 - Warn that using select() on any libevent version before 1.1 will be
22400 unnecessarily slow (even for select()).
22401 - Flush ERR-level controller status events just like we currently
22402 flush ERR-level log events, so that a Tor shutdown doesn't prevent
22403 the controller from learning about current events.
22405 o Minor features (more controller status events):
22406 - Implement EXTERNAL_ADDRESS server status event so controllers can
22407 learn when our address changes.
22408 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
22409 can learn when directories reject our descriptor.
22410 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
22411 can learn when a client application is speaking a non-socks protocol
22413 - Implement DANGEROUS_SOCKS client status event so controllers
22414 can learn when a client application is leaking DNS addresses.
22415 - Implement BUG general status event so controllers can learn when
22416 Tor is unhappy about its internal invariants.
22417 - Implement CLOCK_SKEW general status event so controllers can learn
22418 when Tor thinks the system clock is set incorrectly.
22419 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
22420 server status events so controllers can learn when their descriptors
22421 are accepted by a directory.
22422 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
22423 server status events so controllers can learn about Tor's progress in
22424 deciding whether it's reachable from the outside.
22425 - Implement BAD_LIBEVENT general status event so controllers can learn
22426 when we have a version/method combination in libevent that needs to
22428 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
22429 and DNS_USELESS server status events so controllers can learn
22430 about changes to DNS server status.
22432 o Minor features (directory):
22433 - Authorities no longer recommend exits as guards if this would shift
22434 too much load to the exit nodes.
22437 Changes in version 0.1.2.5-alpha - 2007-01-06
22439 - Enable write limiting as well as read limiting. Now we sacrifice
22440 capacity if we're pushing out lots of directory traffic, rather
22441 than overrunning the user's intended bandwidth limits.
22442 - Include TLS overhead when counting bandwidth usage; previously, we
22443 would count only the bytes sent over TLS, but not the bytes used
22445 - Support running the Tor service with a torrc not in the same
22446 directory as tor.exe and default to using the torrc located in
22447 the %appdata%\Tor\ of the user who installed the service. Patch
22449 - Servers now check for the case when common DNS requests are going to
22450 wildcarded addresses (i.e. all getting the same answer), and change
22451 their exit policy to reject *:* if it's happening.
22452 - Implement BEGIN_DIR cells, so we can connect to the directory
22453 server via TLS to do encrypted directory requests rather than
22454 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
22455 config options if you like.
22457 o Minor features (config and docs):
22458 - Start using the state file to store bandwidth accounting data:
22459 the bw_accounting file is now obsolete. We'll keep generating it
22460 for a while for people who are still using 0.1.2.4-alpha.
22461 - Try to batch changes to the state file so that we do as few
22462 disk writes as possible while still storing important things in
22464 - The state file and the bw_accounting file get saved less often when
22465 the AvoidDiskWrites config option is set.
22466 - Make PIDFile work on Windows (untested).
22467 - Add internal descriptions for a bunch of configuration options:
22468 accessible via controller interface and in comments in saved
22470 - Reject *:563 (NNTPS) in the default exit policy. We already reject
22471 NNTP by default, so this seems like a sensible addition.
22472 - Clients now reject hostnames with invalid characters. This should
22473 avoid some inadvertent info leaks. Add an option
22474 AllowNonRFC953Hostnames to disable this behavior, in case somebody
22475 is running a private network with hosts called @, !, and #.
22476 - Add a maintainer script to tell us which options are missing
22477 documentation: "make check-docs".
22478 - Add a new address-spec.txt document to describe our special-case
22479 addresses: .exit, .onion, and .noconnnect.
22481 o Minor features (DNS):
22482 - Ongoing work on eventdns infrastructure: now it has dns server
22483 and ipv6 support. One day Tor will make use of it.
22484 - Add client-side caching for reverse DNS lookups.
22485 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
22486 - When we change nameservers or IP addresses, reset and re-launch
22487 our tests for DNS hijacking.
22489 o Minor features (directory):
22490 - Authorities now specify server versions in networkstatus. This adds
22491 about 2% to the size of compressed networkstatus docs, and allows
22492 clients to tell which servers support BEGIN_DIR and which don't.
22493 The implementation is forward-compatible with a proposed future
22494 protocol version scheme not tied to Tor versions.
22495 - DirServer configuration lines now have an orport= option so
22496 clients can open encrypted tunnels to the authorities without
22497 having downloaded their descriptors yet. Enabled for moria1,
22498 moria2, tor26, and lefkada now in the default configuration.
22499 - Directory servers are more willing to send a 503 "busy" if they
22500 are near their write limit, especially for v1 directory requests.
22501 Now they can use their limited bandwidth for actual Tor traffic.
22502 - Clients track responses with status 503 from dirservers. After a
22503 dirserver has given us a 503, we try not to use it until an hour has
22504 gone by, or until we have no dirservers that haven't given us a 503.
22505 - When we get a 503 from a directory, and we're not a server, we don't
22506 count the failure against the total number of failures allowed
22507 for the thing we're trying to download.
22508 - Report X-Your-Address-Is correctly from tunneled directory
22509 connections; don't report X-Your-Address-Is when it's an internal
22510 address; and never believe reported remote addresses when they're
22512 - Protect against an unlikely DoS attack on directory servers.
22513 - Add a BadDirectory flag to network status docs so that authorities
22514 can (eventually) tell clients about caches they believe to be
22517 o Minor features (controller):
22518 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
22519 - Reimplement GETINFO so that info/names stays in sync with the
22521 - Implement "GETINFO fingerprint".
22522 - Implement "SETEVENTS GUARD" so controllers can get updates on
22523 entry guard status as it changes.
22525 o Minor features (clean up obsolete pieces):
22526 - Remove some options that have been deprecated since at least
22527 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
22528 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
22529 to set log options.
22530 - We no longer look for identity and onion keys in "identity.key" and
22531 "onion.key" -- these were replaced by secret_id_key and
22532 secret_onion_key in 0.0.8pre1.
22533 - We no longer require unrecognized directory entries to be
22536 o Major bugfixes (security):
22537 - Stop sending the HttpProxyAuthenticator string to directory
22538 servers when directory connections are tunnelled through Tor.
22539 - Clients no longer store bandwidth history in the state file.
22540 - Do not log introduction points for hidden services if SafeLogging
22542 - When generating bandwidth history, round down to the nearest
22543 1k. When storing accounting data, round up to the nearest 1k.
22544 - When we're running as a server, remember when we last rotated onion
22545 keys, so that we will rotate keys once they're a week old even if
22546 we never stay up for a week ourselves.
22548 o Major bugfixes (other):
22549 - Fix a longstanding bug in eventdns that prevented the count of
22550 timed-out resolves from ever being reset. This bug caused us to
22551 give up on a nameserver the third time it timed out, and try it
22552 10 seconds later... and to give up on it every time it timed out
22554 - Take out the '5 second' timeout from the connection retry
22555 schedule. Now the first connect attempt will wait a full 10
22556 seconds before switching to a new circuit. Perhaps this will help
22557 a lot. Based on observations from Mike Perry.
22558 - Fix a bug on the Windows implementation of tor_mmap_file() that
22559 would prevent the cached-routers file from ever loading. Reported
22563 - Fix an assert failure when a directory authority sets
22564 AuthDirRejectUnlisted and then receives a descriptor from an
22565 unlisted router. Reported by seeess.
22566 - Avoid a double-free when parsing malformed DirServer lines.
22567 - Fix a bug when a BSD-style PF socket is first used. Patch from
22569 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
22570 to resolve an address at a given exit node even when they ask for
22572 - Servers no longer ever list themselves in their "family" line,
22573 even if configured to do so. This makes it easier to configure
22574 family lists conveniently.
22575 - When running as a server, don't fall back to 127.0.0.1 when no
22576 nameservers are configured in /etc/resolv.conf; instead, make the
22577 user fix resolv.conf or specify nameservers explicitly. (Resolves
22579 - Stop accepting certain malformed ports in configured exit policies.
22580 - Don't re-write the fingerprint file every restart, unless it has
22582 - Stop warning when a single nameserver fails: only warn when _all_ of
22583 our nameservers have failed. Also, when we only have one nameserver,
22584 raise the threshold for deciding that the nameserver is dead.
22585 - Directory authorities now only decide that routers are reachable
22586 if their identity keys are as expected.
22587 - When the user uses bad syntax in the Log config line, stop
22588 suggesting other bad syntax as a replacement.
22589 - Correctly detect ipv6 DNS capability on OpenBSD.
22591 o Minor bugfixes (controller):
22592 - Report the circuit number correctly in STREAM CLOSED events. Bug
22593 reported by Mike Perry.
22594 - Do not report bizarre values for results of accounting GETINFOs
22595 when the last second's write or read exceeds the allotted bandwidth.
22596 - Report "unrecognized key" rather than an empty string when the
22597 controller tries to fetch a networkstatus that doesn't exist.
22600 Changes in version 0.1.1.26 - 2006-12-14
22601 o Security bugfixes:
22602 - Stop sending the HttpProxyAuthenticator string to directory
22603 servers when directory connections are tunnelled through Tor.
22604 - Clients no longer store bandwidth history in the state file.
22605 - Do not log introduction points for hidden services if SafeLogging
22609 - Fix an assert failure when a directory authority sets
22610 AuthDirRejectUnlisted and then receives a descriptor from an
22611 unlisted router (reported by seeess).
22614 Changes in version 0.1.2.4-alpha - 2006-12-03
22616 - Add support for using natd; this allows FreeBSDs earlier than
22617 5.1.2 to have ipfw send connections through Tor without using
22618 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
22621 - Make all connections to addresses of the form ".noconnect"
22622 immediately get closed. This lets application/controller combos
22623 successfully test whether they're talking to the same Tor by
22624 watching for STREAM events.
22625 - Make cross.sh cross-compilation script work even when autogen.sh
22626 hasn't been run. (Patch from Michael Mohr.)
22627 - Statistics dumped by -USR2 now include a breakdown of public key
22628 operations, for profiling.
22631 - Fix a major leak when directory authorities parse their
22632 approved-routers list, a minor memory leak when we fail to pick
22633 an exit node, and a few rare leaks on errors.
22634 - Handle TransPort connections even when the server sends data before
22635 the client sends data. Previously, the connection would just hang
22636 until the client sent data. (Patch from tup based on patch from
22638 - Avoid assert failure when our cached-routers file is empty on
22642 - Don't log spurious warnings when we see a circuit close reason we
22643 don't recognize; it's probably just from a newer version of Tor.
22644 - Have directory authorities allow larger amounts of drift in uptime
22645 without replacing the server descriptor: previously, a server that
22646 restarted every 30 minutes could have 48 "interesting" descriptors
22648 - Start linking to the Tor specification and Tor reference manual
22649 correctly in the Windows installer.
22650 - Add Vidalia to the OS X uninstaller script, so when we uninstall
22651 Tor/Privoxy we also uninstall Vidalia.
22652 - Resume building on Irix64, and fix a lot of warnings from its
22653 MIPSpro C compiler.
22654 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
22655 when we're running as a client.
22658 Changes in version 0.1.1.25 - 2006-11-04
22660 - When a client asks us to resolve (rather than connect to)
22661 an address, and we have a cached answer, give them the cached
22662 answer. Previously, we would give them no answer at all.
22663 - We were building exactly the wrong circuits when we predict
22664 hidden service requirements, meaning Tor would have to build all
22665 its circuits on demand.
22666 - If none of our live entry guards have a high uptime, but we
22667 require a guard with a high uptime, try adding a new guard before
22668 we give up on the requirement. This patch should make long-lived
22669 connections more stable on average.
22670 - When testing reachability of our DirPort, don't launch new
22671 tests when there's already one in progress -- unreachable
22672 servers were stacking up dozens of testing streams.
22674 o Security bugfixes:
22675 - When the user sends a NEWNYM signal, clear the client-side DNS
22676 cache too. Otherwise we continue to act on previous information.
22679 - Avoid a memory corruption bug when creating a hash table for
22681 - Avoid possibility of controller-triggered crash when misusing
22682 certain commands from a v0 controller on platforms that do not
22683 handle printf("%s",NULL) gracefully.
22684 - Avoid infinite loop on unexpected controller input.
22685 - Don't log spurious warnings when we see a circuit close reason we
22686 don't recognize; it's probably just from a newer version of Tor.
22687 - Add Vidalia to the OS X uninstaller script, so when we uninstall
22688 Tor/Privoxy we also uninstall Vidalia.
22691 Changes in version 0.1.2.3-alpha - 2006-10-29
22693 - Prepare for servers to publish descriptors less often: never
22694 discard a descriptor simply for being too old until either it is
22695 recommended by no authorities, or until we get a better one for
22696 the same router. Make caches consider retaining old recommended
22697 routers for even longer.
22698 - If most authorities set a BadExit flag for a server, clients
22699 don't think of it as a general-purpose exit. Clients only consider
22700 authorities that advertise themselves as listing bad exits.
22701 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
22702 headers for content, so that we can work better in the presence of
22703 caching HTTP proxies.
22704 - Allow authorities to list nodes as bad exits by fingerprint or by
22707 o Minor features, controller:
22708 - Add a REASON field to CIRC events; for backward compatibility, this
22709 field is sent only to controllers that have enabled the extended
22710 event format. Also, add additional reason codes to explain why
22711 a given circuit has been destroyed or truncated. (Patches from
22713 - Add a REMOTE_REASON field to extended CIRC events to tell the
22714 controller about why a remote OR told us to close a circuit.
22715 - Stream events also now have REASON and REMOTE_REASON fields,
22716 working much like those for circuit events.
22717 - There's now a GETINFO ns/... field so that controllers can ask Tor
22718 about the current status of a router.
22719 - A new event type "NS" to inform a controller when our opinion of
22720 a router's status has changed.
22721 - Add a GETINFO events/names and GETINFO features/names so controllers
22722 can tell which events and features are supported.
22723 - A new CLEARDNSCACHE signal to allow controllers to clear the
22724 client-side DNS cache without expiring circuits.
22726 o Security bugfixes:
22727 - When the user sends a NEWNYM signal, clear the client-side DNS
22728 cache too. Otherwise we continue to act on previous information.
22731 - Avoid sending junk to controllers or segfaulting when a controller
22732 uses EVENT_NEW_DESC with verbose nicknames.
22733 - Stop triggering asserts if the controller tries to extend hidden
22734 service circuits (reported by mwenge).
22735 - Avoid infinite loop on unexpected controller input.
22736 - When the controller does a "GETINFO network-status", tell it
22737 about even those routers whose descriptors are very old, and use
22738 long nicknames where appropriate.
22739 - Change NT service functions to be loaded on demand. This lets us
22740 build with MinGW without breaking Tor for Windows 98 users.
22741 - Do DirPort reachability tests less often, since a single test
22742 chews through many circuits before giving up.
22743 - In the hidden service example in torrc.sample, stop recommending
22744 esoteric and discouraged hidden service options.
22745 - When stopping an NT service, wait up to 10 sec for it to actually
22746 stop. Patch from Matt Edman; resolves bug 295.
22747 - Fix handling of verbose nicknames with ORCONN controller events:
22748 make them show up exactly when requested, rather than exactly when
22750 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
22751 printing a duplicate "$" in the keys we send (reported by mwenge).
22752 - Correctly set maximum connection limit on Cygwin. (This time
22754 - Try to detect Windows correctly when cross-compiling.
22755 - Detect the size of the routers file correctly even if it is
22756 corrupted (on systems without mmap) or not page-aligned (on systems
22757 with mmap). This bug was harmless.
22758 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
22759 to open a stream fails; now we do in more cases. This should
22760 make clients able to find a good exit faster in some cases, since
22761 unhandleable requests will now get an error rather than timing out.
22762 - Resolve two memory leaks when rebuilding the on-disk router cache
22763 (reported by fookoowa).
22764 - Clean up minor code warnings suggested by the MIPSpro C compiler,
22765 and reported by some Centos users.
22766 - Controller signals now work on non-Unix platforms that don't define
22767 SIGUSR1 and SIGUSR2 the way we expect.
22768 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
22769 values before failing, and always enables eventdns.
22770 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
22771 Try to fix this in configure.in by checking for most functions
22772 before we check for libevent.
22775 Changes in version 0.1.2.2-alpha - 2006-10-07
22777 - Make our async eventdns library on-by-default for Tor servers,
22778 and plan to deprecate the separate dnsworker threads.
22779 - Add server-side support for "reverse" DNS lookups (using PTR
22780 records so clients can determine the canonical hostname for a given
22781 IPv4 address). Only supported by servers using eventdns; servers
22782 now announce in their descriptors whether they support eventdns.
22783 - Specify and implement client-side SOCKS5 interface for reverse DNS
22784 lookups (see doc/socks-extensions.txt).
22785 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
22786 connect to directory servers through Tor. Previously, clients needed
22787 to find Tor exits to make private connections to directory servers.
22788 - Avoid choosing Exit nodes for entry or middle hops when the
22789 total bandwidth available from non-Exit nodes is much higher than
22790 the total bandwidth available from Exit nodes.
22791 - Workaround for name servers (like Earthlink's) that hijack failing
22792 DNS requests and replace the no-such-server answer with a "helpful"
22793 redirect to an advertising-driven search portal. Also work around
22794 DNS hijackers who "helpfully" decline to hijack known-invalid
22795 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
22796 lets you turn it off.
22797 - Send out a burst of long-range padding cells once we've established
22798 that we're reachable. Spread them over 4 circuits, so hopefully
22799 a few will be fast. This exercises our bandwidth and bootstraps
22800 us into the directory more quickly.
22802 o New/improved config options:
22803 - Add new config option "ResolvConf" to let the server operator
22804 choose an alternate resolve.conf file when using eventdns.
22805 - Add an "EnforceDistinctSubnets" option to control our "exclude
22806 servers on the same /16" behavior. It's still on by default; this
22807 is mostly for people who want to operate private test networks with
22808 all the machines on the same subnet.
22809 - If one of our entry guards is on the ExcludeNodes list, or the
22810 directory authorities don't think it's a good guard, treat it as
22811 if it were unlisted: stop using it as a guard, and throw it off
22812 the guards list if it stays that way for a long time.
22813 - Allow directory authorities to be marked separately as authorities
22814 for the v1 directory protocol, the v2 directory protocol, and
22815 as hidden service directories, to make it easier to retire old
22816 authorities. V1 authorities should set "HSAuthoritativeDir 1"
22817 to continue being hidden service authorities too.
22818 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
22820 o Minor features, controller:
22821 - Fix CIRC controller events so that controllers can learn the
22822 identity digests of non-Named servers used in circuit paths.
22823 - Let controllers ask for more useful identifiers for servers. Instead
22824 of learning identity digests for un-Named servers and nicknames
22825 for Named servers, the new identifiers include digest, nickname,
22826 and indication of Named status. Off by default; see control-spec.txt
22827 for more information.
22828 - Add a "getinfo address" controller command so it can display Tor's
22829 best guess to the user.
22830 - New controller event to alert the controller when our server
22831 descriptor has changed.
22832 - Give more meaningful errors on controller authentication failure.
22834 o Minor features, other:
22835 - When asked to resolve a hostname, don't use non-exit servers unless
22836 requested to do so. This allows servers with broken DNS to be
22837 useful to the network.
22838 - Divide eventdns log messages into warn and info messages.
22839 - Reserve the nickname "Unnamed" for routers that can't pick
22840 a hostname: any router can call itself Unnamed; directory
22841 authorities will never allocate Unnamed to any particular router;
22842 clients won't believe that any router is the canonical Unnamed.
22843 - Only include function names in log messages for info/debug messages.
22844 For notice/warn/err, the content of the message should be clear on
22845 its own, and printing the function name only confuses users.
22846 - Avoid some false positives during reachability testing: don't try
22847 to test via a server that's on the same /24 as us.
22848 - If we fail to build a circuit to an intended enclave, and it's
22849 not mandatory that we use that enclave, stop wanting it.
22850 - When eventdns is enabled, allow multithreaded builds on NetBSD and
22851 OpenBSD. (We had previously disabled threads on these platforms
22852 because they didn't have working thread-safe resolver functions.)
22854 o Major bugfixes, anonymity/security:
22855 - If a client asked for a server by name, and there's a named server
22856 in our network-status but we don't have its descriptor yet, we
22857 could return an unnamed server instead.
22858 - Fix NetBSD bug that could allow someone to force uninitialized RAM
22859 to be sent to a server's DNS resolver. This only affects NetBSD
22860 and other platforms that do not bounds-check tolower().
22861 - Reject (most) attempts to use Tor circuits with length one. (If
22862 many people start using Tor as a one-hop proxy, exit nodes become
22863 a more attractive target for compromise.)
22864 - Just because your DirPort is open doesn't mean people should be
22865 able to remotely teach you about hidden service descriptors. Now
22866 only accept rendezvous posts if you've got HSAuthoritativeDir set.
22868 o Major bugfixes, other:
22869 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
22870 - When a client asks the server to resolve (not connect to)
22871 an address, and it has a cached answer, give them the cached answer.
22872 Previously, the server would give them no answer at all.
22873 - Allow really slow clients to not hang up five minutes into their
22874 directory downloads (suggested by Adam J. Richter).
22875 - We were building exactly the wrong circuits when we anticipated
22876 hidden service requirements, meaning Tor would have to build all
22877 its circuits on demand.
22878 - Avoid crashing when we mmap a router cache file of size 0.
22879 - When testing reachability of our DirPort, don't launch new
22880 tests when there's already one in progress -- unreachable
22881 servers were stacking up dozens of testing streams.
22883 o Minor bugfixes, correctness:
22884 - If we're a directory mirror and we ask for "all" network status
22885 documents, we would discard status documents from authorities
22886 we don't recognize.
22887 - Avoid a memory corruption bug when creating a hash table for
22889 - Avoid controller-triggered crash when misusing certain commands
22890 from a v0 controller on platforms that do not handle
22891 printf("%s",NULL) gracefully.
22892 - Don't crash when a controller sends a third argument to an
22893 "extendcircuit" request.
22894 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
22895 response; fix error code when "getinfo dir/status/" fails.
22896 - Avoid crash when telling controller stream-status and a stream
22898 - Patch from Adam Langley to fix assert() in eventdns.c.
22899 - Fix a debug log message in eventdns to say "X resolved to Y"
22900 instead of "X resolved to X".
22901 - Make eventdns give strings for DNS errors, not just error numbers.
22902 - Track unreachable entry guards correctly: don't conflate
22903 'unreachable by us right now' with 'listed as down by the directory
22904 authorities'. With the old code, if a guard was unreachable by
22905 us but listed as running, it would clog our guard list forever.
22906 - Behave correctly in case we ever have a network with more than
22907 2GB/s total advertised capacity.
22908 - Make TrackExitHosts case-insensitive, and fix the behavior of
22909 ".suffix" TrackExitHosts items to avoid matching in the middle of
22911 - Finally fix the openssl warnings from newer gccs that believe that
22912 ignoring a return value is okay, but casting a return value and
22913 then ignoring it is a sign of madness.
22914 - Prevent the contrib/exitlist script from printing the same
22915 result more than once.
22916 - Patch from Steve Hildrey: Generate network status correctly on
22917 non-versioning dirservers.
22918 - Don't listen to the X-Your-Address-Is hint if you did the lookup
22919 via Tor; otherwise you'll think you're the exit node's IP address.
22921 o Minor bugfixes, performance:
22922 - Two small performance improvements on parsing descriptors.
22923 - Major performance improvement on inserting descriptors: change
22924 algorithm from O(n^2) to O(n).
22925 - Make the common memory allocation path faster on machines where
22926 malloc(0) returns a pointer.
22927 - Start remembering X-Your-Address-Is directory hints even if you're
22928 a client, so you can become a server more smoothly.
22929 - Avoid duplicate entries on MyFamily line in server descriptor.
22931 o Packaging, features:
22932 - Remove architecture from OS X builds. The official builds are
22933 now universal binaries.
22934 - The Debian package now uses --verify-config when (re)starting,
22935 to distinguish configuration errors from other errors.
22936 - Update RPMs to require libevent 1.1b.
22938 o Packaging, bugfixes:
22939 - Patches so Tor builds with MinGW on Windows.
22940 - Patches so Tor might run on Cygwin again.
22941 - Resume building on non-gcc compilers and ancient gcc. Resume
22942 building with the -O0 compile flag. Resume building cleanly on
22944 - Run correctly on OS X platforms with case-sensitive filesystems.
22945 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
22946 - Add autoconf checks so Tor can build on Solaris x86 again.
22949 - Documented (and renamed) ServerDNSSearchDomains and
22950 ServerDNSResolvConfFile options.
22951 - Be clearer that the *ListenAddress directives can be repeated
22955 Changes in version 0.1.1.24 - 2006-09-29
22957 - Allow really slow clients to not hang up five minutes into their
22958 directory downloads (suggested by Adam J. Richter).
22959 - Fix major performance regression from 0.1.0.x: instead of checking
22960 whether we have enough directory information every time we want to
22961 do something, only check when the directory information has changed.
22962 This should improve client CPU usage by 25-50%.
22963 - Don't crash if, after a server has been running for a while,
22964 it can't resolve its hostname.
22967 - Allow Tor to start when RunAsDaemon is set but no logs are set.
22968 - Don't crash when the controller receives a third argument to an
22969 "extendcircuit" request.
22970 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
22971 response; fix error code when "getinfo dir/status/" fails.
22972 - Fix configure.in to not produce broken configure files with
22973 more recent versions of autoconf. Thanks to Clint for his auto*
22975 - Fix security bug on NetBSD that could allow someone to force
22976 uninitialized RAM to be sent to a server's DNS resolver. This
22977 only affects NetBSD and other platforms that do not bounds-check
22979 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
22980 methods: these are known to be buggy.
22981 - If we're a directory mirror and we ask for "all" network status
22982 documents, we would discard status documents from authorities
22983 we don't recognize.
22986 Changes in version 0.1.2.1-alpha - 2006-08-27
22988 - Add "eventdns" async dns library from Adam Langley, tweaked to
22989 build on OSX and Windows. Only enabled if you pass the
22990 --enable-eventdns argument to configure.
22991 - Allow servers with no hostname or IP address to learn their
22992 IP address by asking the directory authorities. This code only
22993 kicks in when you would normally have exited with a "no address"
22994 error. Nothing's authenticated, so use with care.
22995 - Rather than waiting a fixed amount of time between retrying
22996 application connections, we wait only 5 seconds for the first,
22997 10 seconds for the second, and 15 seconds for each retry after
22998 that. Hopefully this will improve the expected user experience.
22999 - Patch from Tup to add support for transparent AP connections:
23000 this basically bundles the functionality of trans-proxy-tor
23001 into the Tor mainline. Now hosts with compliant pf/netfilter
23002 implementations can redirect TCP connections straight to Tor
23003 without diverting through SOCKS. Needs docs.
23004 - Busy directory servers save lots of memory by spooling server
23005 descriptors, v1 directories, and v2 networkstatus docs to buffers
23006 as needed rather than en masse. Also mmap the cached-routers
23007 files, so we don't need to keep the whole thing in memory too.
23008 - Automatically avoid picking more than one node from the same
23009 /16 network when constructing a circuit.
23010 - Revise and clean up the torrc.sample that we ship with; add
23011 a section for BandwidthRate and BandwidthBurst.
23014 - Split circuit_t into origin_circuit_t and or_circuit_t, and
23015 split connection_t into edge, or, dir, control, and base structs.
23016 These will save quite a bit of memory on busy servers, and they'll
23017 also help us track down bugs in the code and bugs in the spec.
23018 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
23019 or later. Log when we are doing this, so we can diagnose it when
23020 it fails. (Also, recommend libevent 1.1b for kqueue and
23021 win32 methods; deprecate libevent 1.0b harder; make libevent
23022 recommendation system saner.)
23023 - Start being able to build universal binaries on OS X (thanks
23025 - Export the default exit policy via the control port, so controllers
23026 don't need to guess what it is / will be later.
23027 - Add a man page entry for ProtocolWarnings.
23028 - Add TestVia config option to the man page.
23029 - Remove even more protocol-related warnings from Tor server logs,
23030 such as bad TLS handshakes and malformed begin cells.
23031 - Stop fetching descriptors if you're not a dir mirror and you
23032 haven't tried to establish any circuits lately. [This currently
23033 causes some dangerous behavior, because when you start up again
23034 you'll use your ancient server descriptors.]
23035 - New DirPort behavior: if you have your dirport set, you download
23036 descriptors aggressively like a directory mirror, whether or not
23037 your ORPort is set.
23038 - Get rid of the router_retry_connections notion. Now routers
23039 no longer try to rebuild long-term connections to directory
23040 authorities, and directory authorities no longer try to rebuild
23041 long-term connections to all servers. We still don't hang up
23042 connections in these two cases though -- we need to look at it
23043 more carefully to avoid flapping, and we likely need to wait til
23044 0.1.1.x is obsolete.
23045 - Drop compatibility with obsolete Tors that permit create cells
23046 to have the wrong circ_id_type.
23047 - Re-enable per-connection rate limiting. Get rid of the "OP
23048 bandwidth" concept. Lay groundwork for "bandwidth classes" --
23049 separate global buckets that apply depending on what sort of conn
23051 - Start publishing one minute or so after we find our ORPort
23052 to be reachable. This will help reduce the number of descriptors
23053 we have for ourselves floating around, since it's quite likely
23054 other things (e.g. DirPort) will change during that minute too.
23055 - Fork the v1 directory protocol into its own spec document,
23056 and mark dir-spec.txt as the currently correct (v2) spec.
23059 - When we find our DirPort to be reachable, publish a new descriptor
23060 so we'll tell the world (reported by pnx).
23061 - Publish a new descriptor after we hup/reload. This is important
23062 if our config has changed such that we'll want to start advertising
23063 our DirPort now, etc.
23064 - Allow Tor to start when RunAsDaemon is set but no logs are set.
23065 - When we have a state file we cannot parse, tell the user and
23066 move it aside. Now we avoid situations where the user starts
23067 Tor in 1904, Tor writes a state file with that timestamp in it,
23068 the user fixes her clock, and Tor refuses to start.
23069 - Fix configure.in to not produce broken configure files with
23070 more recent versions of autoconf. Thanks to Clint for his auto*
23072 - "tor --verify-config" now exits with -1(255) or 0 depending on
23073 whether the config options are bad or good.
23074 - Resolve bug 321 when using dnsworkers: append a period to every
23075 address we resolve at the exit node, so that we do not accidentally
23076 pick up local addresses, and so that failing searches are retried
23077 in the resolver search domains. (This is already solved for
23078 eventdns.) (This breaks Blossom servers for now.)
23079 - If we are using an exit enclave and we can't connect, e.g. because
23080 its webserver is misconfigured to not listen on localhost, then
23081 back off and try connecting from somewhere else before we fail.
23084 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
23085 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
23086 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
23087 when the IP address is mapped through MapAddress to a hostname.
23088 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
23089 useless IPv6 DNS resolves.
23090 - Patch suggested by Karsten Loesing: respond to SIGNAL command
23091 before we execute the signal, in case the signal shuts us down.
23092 - Clean up AllowInvalidNodes man page entry.
23093 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
23094 - Add more asserts to track down an assert error on a windows Tor
23095 server with connection_add being called with socket == -1.
23096 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
23097 - Fix misleading log messages: an entry guard that is "unlisted",
23098 as well as not known to be "down" (because we've never heard
23099 of it), is not therefore "up".
23100 - Remove code to special-case "-cvs" ending, since it has not
23101 actually mattered since 0.0.9.
23102 - Make our socks5 handling more robust to broken socks clients:
23103 throw out everything waiting on the buffer in between socks
23104 handshake phases, since they can't possibly (so the theory
23105 goes) have predicted what we plan to respond to them.
23108 Changes in version 0.1.1.23 - 2006-07-30
23110 - Fast Tor servers, especially exit nodes, were triggering asserts
23111 due to a bug in handling the list of pending DNS resolves. Some
23112 bugs still remain here; we're hunting them.
23113 - Entry guards could crash clients by sending unexpected input.
23114 - More fixes on reachability testing: if you find yourself reachable,
23115 then don't ever make any client requests (so you stop predicting
23116 circuits), then hup or have your clock jump, then later your IP
23117 changes, you won't think circuits are working, so you won't try to
23118 test reachability, so you won't publish.
23121 - Avoid a crash if the controller does a resetconf firewallports
23122 and then a setconf fascistfirewall=1.
23123 - Avoid an integer underflow when the dir authority decides whether
23124 a router is stable: we might wrongly label it stable, and compute
23125 a slightly wrong median stability, when a descriptor is published
23127 - Fix a place where we might trigger an assert if we can't build our
23128 own server descriptor yet.
23131 Changes in version 0.1.1.22 - 2006-07-05
23133 - Fix a big bug that was causing servers to not find themselves
23134 reachable if they changed IP addresses. Since only 0.1.1.22+
23135 servers can do reachability testing correctly, now we automatically
23136 make sure to test via one of these.
23137 - Fix to allow clients and mirrors to learn directory info from
23138 descriptor downloads that get cut off partway through.
23139 - Directory authorities had a bug in deciding if a newly published
23140 descriptor was novel enough to make everybody want a copy -- a few
23141 servers seem to be publishing new descriptors many times a minute.
23143 - Fix a rare bug that was causing some servers to complain about
23144 "closing wedged cpuworkers" and skip some circuit create requests.
23145 - Make the Exit flag in directory status documents actually work.
23148 Changes in version 0.1.1.21 - 2006-06-10
23149 o Crash and assert fixes from 0.1.1.20:
23150 - Fix a rare crash on Tor servers that have enabled hibernation.
23151 - Fix a seg fault on startup for Tor networks that use only one
23152 directory authority.
23153 - Fix an assert from a race condition that occurs on Tor servers
23154 while exiting, where various threads are trying to log that they're
23155 exiting, and delete the logs, at the same time.
23156 - Make our unit tests pass again on certain obscure platforms.
23159 - Add support for building SUSE RPM packages.
23160 - Speed up initial bootstrapping for clients: if we are making our
23161 first ever connection to any entry guard, then don't mark it down
23163 - When only one Tor server in the network is labelled as a guard,
23164 and we've already picked him, we would cycle endlessly picking him
23165 again, being unhappy about it, etc. Now we specifically exclude
23166 current guards when picking a new guard.
23167 - Servers send create cells more reliably after the TLS connection
23168 is established: we were sometimes forgetting to send half of them
23169 when we had more than one pending.
23170 - If we get a create cell that asks us to extend somewhere, but the
23171 Tor server there doesn't match the expected digest, we now send
23172 a destroy cell back, rather than silently doing nothing.
23173 - Make options->RedirectExit work again.
23174 - Make cookie authentication for the controller work again.
23175 - Stop being picky about unusual characters in the arguments to
23176 mapaddress. It's none of our business.
23177 - Add a new config option "TestVia" that lets you specify preferred
23178 middle hops to use for test circuits. Perhaps this will let me
23179 debug the reachability problems better.
23181 o Log / documentation fixes:
23182 - If we're a server and some peer has a broken TLS certificate, don't
23183 log about it unless ProtocolWarnings is set, i.e., we want to hear
23184 about protocol violations by others.
23185 - Fix spelling of VirtualAddrNetwork in man page.
23186 - Add a better explanation at the top of the autogenerated torrc file
23187 about what happened to our old torrc.
23190 Changes in version 0.1.1.20 - 2006-05-23
23192 - Downgrade a log severity where servers complain that they're
23194 - Avoid a compile warning on FreeBSD.
23195 - Remove string size limit on NEWDESC messages; solve bug 291.
23196 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
23197 more thoroughly when we're running on windows.
23200 Changes in version 0.1.1.19-rc - 2006-05-03
23202 - Regenerate our local descriptor if it's dirty and we try to use
23203 it locally (e.g. if it changes during reachability detection).
23204 - If we setconf our ORPort to 0, we continued to listen on the
23205 old ORPort and receive connections.
23206 - Avoid a second warning about machine/limits.h on Debian
23208 - Be willing to add our own routerinfo into the routerlist.
23209 Now authorities will include themselves in their directories
23210 and network-statuses.
23211 - Stop trying to upload rendezvous descriptors to every
23212 directory authority: only try the v1 authorities.
23213 - Servers no longer complain when they think they're not
23214 registered with the directory authorities. There were too many
23216 - Backport dist-rpm changes so rpms can be built without errors.
23219 - Implement an option, VirtualAddrMask, to set which addresses
23220 get handed out in response to mapaddress requests. This works
23221 around a bug in tsocks where 127.0.0.0/8 is never socksified.
23224 Changes in version 0.1.1.18-rc - 2006-04-10
23226 - Work harder to download live network-statuses from all the
23227 directory authorities we know about. Improve the threshold
23228 decision logic so we're more robust to edge cases.
23229 - When fetching rendezvous descriptors, we were willing to ask
23230 v2 authorities too, which would always return 404.
23233 - Stop listing down or invalid nodes in the v1 directory. This will
23234 reduce its bulk by about 1/3, and reduce load on directory
23236 - When deciding whether a router is Fast or Guard-worthy, consider
23237 his advertised BandwidthRate and not just the BandwidthCapacity.
23238 - No longer ship INSTALL and README files -- they are useless now.
23239 - Force rpmbuild to behave and honor target_cpu.
23240 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
23241 - Start to include translated versions of the tor-doc-*.html
23242 files, along with the screenshots. Still needs more work.
23243 - Start sending back 512 and 451 errors if mapaddress fails,
23244 rather than not sending anything back at all.
23245 - When we fail to bind or listen on an incoming or outgoing
23246 socket, we should close it before failing. otherwise we just
23247 leak it. (thanks to weasel for finding.)
23248 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
23249 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
23250 - Make NoPublish (even though deprecated) work again.
23251 - Fix a minor security flaw where a versioning auth dirserver
23252 could list a recommended version many times in a row to make
23253 clients more convinced that it's recommended.
23254 - Fix crash bug if there are two unregistered servers running
23255 with the same nickname, one of them is down, and you ask for
23256 them by nickname in your EntryNodes or ExitNodes. Also, try
23257 to pick the one that's running rather than an arbitrary one.
23258 - Fix an infinite loop we could hit if we go offline for too long.
23259 - Complain when we hit WSAENOBUFS on recv() or write() too.
23260 Perhaps this will help us hunt the bug.
23261 - If you're not a versioning dirserver, don't put the string
23262 "client-versions \nserver-versions \n" in your network-status.
23263 - Lower the minimum required number of file descriptors to 1000,
23264 so we can have some overhead for Valgrind on Linux, where the
23265 default ulimit -n is 1024.
23268 - Add tor.dizum.com as the fifth authoritative directory server.
23269 - Add a new config option FetchUselessDescriptors, off by default,
23270 for when you plan to run "exitlist" on your client and you want
23271 to know about even the non-running descriptors.
23274 Changes in version 0.1.1.17-rc - 2006-03-28
23276 - Clients and servers since 0.1.1.10-alpha have been expiring
23277 connections whenever they are idle for 5 minutes and they *do*
23278 have circuits on them. Oops. With this new version, clients will
23279 discard their previous entry guard choices and avoid choosing
23280 entry guards running these flawed versions.
23281 - Fix memory leak when uncompressing concatenated zlib streams. This
23282 was causing substantial leaks over time on Tor servers.
23283 - The v1 directory was including servers as much as 48 hours old,
23284 because that's how the new routerlist->routers works. Now only
23285 include them if they're 20 hours old or less.
23288 - Resume building on irix64, netbsd 2.0, etc.
23289 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
23291 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
23292 and it is confusing some users.
23293 - Mirrors stop caching the v1 directory so often.
23294 - Make the max number of old descriptors that a cache will hold
23295 rise with the number of directory authorities, so we can scale.
23296 - Change our win32 uname() hack to be more forgiving about what
23297 win32 versions it thinks it's found.
23300 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
23302 - When the controller's *setconf commands fail, collect an error
23303 message in a string and hand it back to the controller.
23304 - Make the v2 dir's "Fast" flag based on relative capacity, just
23305 like "Stable" is based on median uptime. Name everything in the
23306 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
23307 - Log server fingerprint on startup, so new server operators don't
23308 have to go hunting around their filesystem for it.
23309 - Return a robots.txt on our dirport to discourage google indexing.
23310 - Let the controller ask for GETINFO dir/status/foo so it can ask
23311 directly rather than connecting to the dir port. Only works when
23312 dirport is set for now.
23314 o New config options rather than constants in the code:
23315 - SocksTimeout: How long do we let a socks connection wait
23316 unattached before we fail it?
23317 - CircuitBuildTimeout: Cull non-open circuits that were born
23318 at least this many seconds ago.
23319 - CircuitIdleTimeout: Cull open clean circuits that were born
23320 at least this many seconds ago.
23323 Changes in version 0.1.1.16-rc - 2006-03-18
23324 o Bugfixes on 0.1.1.15-rc:
23325 - Fix assert when the controller asks to attachstream a connect-wait
23326 or resolve-wait stream.
23327 - Now do address rewriting when the controller asks us to attach
23328 to a particular circuit too. This will let Blossom specify
23329 "moria2.exit" without having to learn what moria2's IP address is.
23330 - Make the "tor --verify-config" command-line work again, so people
23331 can automatically check if their torrc will parse.
23332 - Authoritative dirservers no longer require an open connection from
23333 a server to consider him "reachable". We need this change because
23334 when we add new auth dirservers, old servers won't know not to
23336 - Let Tor build on Sun CC again.
23337 - Fix an off-by-one buffer size in dirserv.c that magically never
23338 hit our three authorities but broke sjmurdoch's own tor network.
23339 - If we as a directory mirror don't know of any v1 directory
23340 authorities, then don't try to cache any v1 directories.
23341 - Stop warning about unknown servers in our family when they are
23342 given as hex digests.
23343 - Stop complaining as quickly to the server operator that he
23344 hasn't registered his nickname/key binding.
23345 - Various cleanups so we can add new V2 Auth Dirservers.
23346 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
23347 reflect the updated flags in our v2 dir protocol.
23348 - Resume allowing non-printable characters for exit streams (both
23349 for connecting and for resolving). Now we tolerate applications
23350 that don't follow the RFCs. But continue to block malformed names
23353 o Bugfixes on 0.1.0.x:
23354 - Fix assert bug in close_logs(): when we close and delete logs,
23355 remove them all from the global "logfiles" list.
23356 - Fix minor integer overflow in calculating when we expect to use up
23357 our bandwidth allocation before hibernating.
23358 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
23359 there are multiple SSLs installed with different versions.
23360 - When we try to be a server and Address is not explicitly set and
23361 our hostname resolves to a private IP address, try to use an
23362 interface address if it has a public address. Now Windows machines
23363 that think of themselves as localhost can work by default.
23366 - Let the controller ask for GETINFO dir/server/foo so it can ask
23367 directly rather than connecting to the dir port.
23368 - Let the controller tell us about certain router descriptors
23369 that it doesn't want Tor to use in circuits. Implement
23370 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
23371 - New config option SafeSocks to reject all application connections
23372 using unsafe socks protocols. Defaults to off.
23375 Changes in version 0.1.1.15-rc - 2006-03-11
23376 o Bugfixes and cleanups:
23377 - When we're printing strings from the network, don't try to print
23378 non-printable characters. This protects us against shell escape
23379 sequence exploits, and also against attacks to fool humans into
23380 misreading their logs.
23381 - Fix a bug where Tor would fail to establish any connections if you
23382 left it off for 24 hours and then started it: we were happy with
23383 the obsolete network statuses, but they all referred to router
23384 descriptors that were too old to fetch, so we ended up with no
23385 valid router descriptors.
23386 - Fix a seg fault in the controller's "getinfo orconn-status"
23387 command while listing status on incoming handshaking connections.
23388 Introduce a status name "NEW" for these connections.
23389 - If we get a linelist or linelist_s config option from the torrc
23390 (e.g. ExitPolicy) and it has no value, warn and skip rather than
23391 silently resetting it to its default.
23392 - Don't abandon entry guards until they've been down or gone for
23394 - Cleaner and quieter log messages.
23397 - New controller signal NEWNYM that makes new application requests
23398 use clean circuits.
23399 - Add a new circuit purpose 'controller' to let the controller ask
23400 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
23401 controller command to let you specify the purpose if you're
23402 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
23403 command to let you change a circuit's purpose after it's been
23405 - Accept "private:*" in routerdesc exit policies; not generated yet
23406 because older Tors do not understand it.
23407 - Add BSD-style contributed startup script "rc.subr" from Peter
23411 Changes in version 0.1.1.14-alpha - 2006-02-20
23412 o Bugfixes on 0.1.1.x:
23413 - Don't die if we ask for a stdout or stderr log (even implicitly)
23414 and we're set to RunAsDaemon -- just warn.
23415 - We still had a few bugs in the OR connection rotation code that
23416 caused directory servers to slowly aggregate connections to other
23417 fast Tor servers. This time for sure!
23418 - Make log entries on Win32 include the name of the function again.
23419 - We were treating a pair of exit policies if they were equal even
23420 if one said accept and the other said reject -- causing us to
23421 not always publish a new descriptor since we thought nothing
23423 - Retry pending server downloads as well as pending networkstatus
23424 downloads when we unexpectedly get a socks request.
23425 - We were ignoring the IS_FAST flag in the directory status,
23426 meaning we were willing to pick trivial-bandwidth nodes for "fast"
23428 - If the controller's SAVECONF command fails (e.g. due to file
23429 permissions), let the controller know that it failed.
23432 - If we're trying to be a Tor server and running Windows 95/98/ME
23433 as a server, explain that we'll likely crash.
23434 - When we're a server, a client asks for an old-style directory,
23435 and our write bucket is empty, don't give it to him. This way
23436 small servers can continue to serve the directory *sometimes*,
23437 without getting overloaded.
23438 - Compress exit policies even more -- look for duplicate lines
23440 - Clients now honor the "guard" flag in the router status when
23441 picking entry guards, rather than looking at is_fast or is_stable.
23442 - Retain unrecognized lines in $DATADIR/state file, so that we can
23443 be forward-compatible.
23444 - Generate 18.0.0.0/8 address policy format in descs when we can;
23445 warn when the mask is not reducible to a bit-prefix.
23446 - Let the user set ControlListenAddress in the torrc. This can be
23447 dangerous, but there are some cases (like a secured LAN) where it
23449 - Split ReachableAddresses into ReachableDirAddresses and
23450 ReachableORAddresses, so we can restrict Dir conns to port 80
23451 and OR conns to port 443.
23452 - Now we can target arch and OS in rpm builds (contributed by
23453 Phobos). Also make the resulting dist-rpm filename match the
23455 - New config options to help controllers: FetchServerDescriptors
23456 and FetchHidServDescriptors for whether to fetch server
23457 info and hidserv info or let the controller do it, and
23458 PublishServerDescriptor and PublishHidServDescriptors.
23459 - Also let the controller set the __AllDirActionsPrivate config
23460 option if you want all directory fetches/publishes to happen via
23461 Tor (it assumes your controller bootstraps your circuits).
23464 Changes in version 0.1.0.17 - 2006-02-17
23465 o Crash bugfixes on 0.1.0.x:
23466 - When servers with a non-zero DirPort came out of hibernation,
23467 sometimes they would trigger an assert.
23469 o Other important bugfixes:
23470 - On platforms that don't have getrlimit (like Windows), we were
23471 artificially constraining ourselves to a max of 1024
23472 connections. Now just assume that we can handle as many as 15000
23473 connections. Hopefully this won't cause other problems.
23475 o Backported features:
23476 - When we're a server, a client asks for an old-style directory,
23477 and our write bucket is empty, don't give it to him. This way
23478 small servers can continue to serve the directory *sometimes*,
23479 without getting overloaded.
23480 - Whenever you get a 503 in response to a directory fetch, try
23481 once more. This will become important once servers start sending
23482 503's whenever they feel busy.
23483 - Fetch a new directory every 120 minutes, not every 40 minutes.
23484 Now that we have hundreds of thousands of users running the old
23485 directory algorithm, it's starting to hurt a lot.
23486 - Bump up the period for forcing a hidden service descriptor upload
23487 from 20 minutes to 1 hour.
23490 Changes in version 0.1.1.13-alpha - 2006-02-09
23491 o Crashes in 0.1.1.x:
23492 - When you tried to setconf ORPort via the controller, Tor would
23493 crash. So people using TorCP to become a server were sad.
23494 - Solve (I hope) the stack-smashing bug that we were seeing on fast
23495 servers. The problem appears to be something do with OpenSSL's
23496 random number generation, or how we call it, or something. Let me
23497 know if the crashes continue.
23498 - Turn crypto hardware acceleration off by default, until we find
23499 somebody smart who can test it for us. (It appears to produce
23500 seg faults in at least some cases.)
23501 - Fix a rare assert error when we've tried all intro points for
23502 a hidden service and we try fetching the service descriptor again:
23503 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
23506 - Fix a major load balance bug: we were round-robining in 16 KB
23507 chunks, and servers with bandwidthrate of 20 KB, while downloading
23508 a 600 KB directory, would starve their other connections. Now we
23509 try to be a bit more fair.
23510 - Dir authorities and mirrors were never expiring the newest
23511 descriptor for each server, causing memory and directory bloat.
23512 - Fix memory-bloating and connection-bloating bug on servers: We
23513 were never closing any connection that had ever had a circuit on
23514 it, because we were checking conn->n_circuits == 0, yet we had a
23515 bug that let it go negative.
23516 - Make Tor work using squid as your http proxy again -- squid
23517 returns an error if you ask for a URL that's too long, and it uses
23518 a really generic error message. Plus, many people are behind a
23519 transparent squid so they don't even realize it.
23520 - On platforms that don't have getrlimit (like Windows), we were
23521 artificially constraining ourselves to a max of 1024
23522 connections. Now just assume that we can handle as many as 15000
23523 connections. Hopefully this won't cause other problems.
23524 - Add a new config option ExitPolicyRejectPrivate which defaults to
23525 1. This means all exit policies will begin with rejecting private
23526 addresses, unless the server operator explicitly turns it off.
23529 - Clients no longer download descriptors for non-running
23531 - Before we add new directory authorities, we should make it
23532 clear that only v1 authorities should receive/publish hidden
23533 service descriptors.
23536 - As soon as we've fetched some more directory info, immediately
23537 try to download more server descriptors. This way we don't have
23538 a 10 second pause during initial bootstrapping.
23539 - Remove even more loud log messages that the server operator can't
23541 - When we're running an obsolete or un-recommended version, make
23542 the log message more clear about what the problem is and what
23543 versions *are* still recommended.
23544 - Provide a more useful warn message when our onion queue gets full:
23545 the CPU is too slow or the exit policy is too liberal.
23546 - Don't warn when we receive a 503 from a dirserver/cache -- this
23547 will pave the way for them being able to refuse if they're busy.
23548 - When we fail to bind a listener, try to provide a more useful
23549 log message: e.g., "Is Tor already running?"
23550 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
23551 Goldberg can prove things about our handshake protocol more
23553 - MaxConn has been obsolete for a while now. Document the ConnLimit
23554 config option, which is a *minimum* number of file descriptors
23555 that must be available else Tor refuses to start.
23556 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
23557 if you log to syslog and want something other than LOG_DAEMON.
23558 - Make dirservers generate a separate "guard" flag to mean,
23559 "would make a good entry guard". Make clients parse it and vote
23560 on it. Not used by clients yet.
23561 - Implement --with-libevent-dir option to ./configure. Also, improve
23562 search techniques to find libevent, and use those for openssl too.
23563 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
23564 - Only start testing reachability once we've established a
23565 circuit. This will make startup on dirservers less noisy.
23566 - Don't try to upload hidden service descriptors until we have
23567 established a circuit.
23568 - Fix the controller's "attachstream 0" command to treat conn like
23569 it just connected, doing address remapping, handling .exit and
23570 .onion idioms, and so on. Now we're more uniform in making sure
23571 that the controller hears about new and closing connections.
23574 Changes in version 0.1.1.12-alpha - 2006-01-11
23575 o Bugfixes on 0.1.1.x:
23576 - The fix to close duplicate server connections was closing all
23577 Tor client connections if they didn't establish a circuit
23578 quickly enough. Oops.
23579 - Fix minor memory issue (double-free) that happened on exit.
23581 o Bugfixes on 0.1.0.x:
23582 - Tor didn't warn when it failed to open a log file.
23585 Changes in version 0.1.1.11-alpha - 2006-01-10
23586 o Crashes in 0.1.1.x:
23587 - Include all the assert/crash fixes from 0.1.0.16.
23588 - If you start Tor and then quit very quickly, there were some
23589 races that tried to free things that weren't allocated yet.
23590 - Fix a rare memory stomp if you're running hidden services.
23591 - Fix segfault when specifying DirServer in config without nickname.
23592 - Fix a seg fault when you finish connecting to a server but at
23593 that moment you dump his server descriptor.
23594 - Extendcircuit and Attachstream controller commands would
23595 assert/crash if you don't give them enough arguments.
23596 - Fix an assert error when we're out of space in the connection_list
23597 and we try to post a hidden service descriptor (reported by weasel).
23598 - If you specify a relative torrc path and you set RunAsDaemon in
23599 your torrc, then it chdir()'s to the new directory. If you HUP,
23600 it tries to load the new torrc location, fails, and exits.
23601 The fix: no longer allow a relative path to torrc using -f.
23604 - Implement "entry guards": automatically choose a handful of entry
23605 nodes and stick with them for all circuits. Only pick new guards
23606 when the ones you have are unsuitable, and if the old guards
23607 become suitable again, switch back. This will increase security
23608 dramatically against certain end-point attacks. The EntryNodes
23609 config option now provides some hints about which entry guards you
23610 want to use most; and StrictEntryNodes means to only use those.
23611 - New directory logic: download by descriptor digest, not by
23612 fingerprint. Caches try to download all listed digests from
23613 authorities; clients try to download "best" digests from caches.
23614 This avoids partitioning and isolating attacks better.
23615 - Make the "stable" router flag in network-status be the median of
23616 the uptimes of running valid servers, and make clients pay
23617 attention to the network-status flags. Thus the cutoff adapts
23618 to the stability of the network as a whole, making IRC, IM, etc
23619 connections more reliable.
23622 - Tor servers with dynamic IP addresses were needing to wait 18
23623 hours before they could start doing reachability testing using
23624 the new IP address and ports. This is because they were using
23625 the internal descriptor to learn what to test, yet they were only
23626 rebuilding the descriptor once they decided they were reachable.
23627 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
23628 to download certain server descriptors, throw them away, and then
23629 fetch them again after 30 minutes. Now mirrors throw away these
23630 server descriptors so clients can't get them.
23631 - We were leaving duplicate connections to other ORs open for a week,
23632 rather than closing them once we detect a duplicate. This only
23633 really affected authdirservers, but it affected them a lot.
23634 - Spread the authdirservers' reachability testing over the entire
23635 testing interval, so we don't try to do 500 TLS's at once every
23639 - If the network is down, and we try to connect to a conn because
23640 we have a circuit in mind, and we timeout (30 seconds) because the
23641 network never answers, we were expiring the circuit, but we weren't
23642 obsoleting the connection or telling the entry_guards functions.
23643 - Some Tor servers process billions of cells per day. These statistics
23644 need to be uint64_t's.
23645 - Check for integer overflows in more places, when adding elements
23646 to smartlists. This could possibly prevent a buffer overflow
23647 on malicious huge inputs. I don't see any, but I haven't looked
23649 - ReachableAddresses kept growing new "reject *:*" lines on every
23651 - When you "setconf log" via the controller, it should remove all
23652 logs. We were automatically adding back in a "log notice stdout".
23653 - Newly bootstrapped Tor networks couldn't establish hidden service
23654 circuits until they had nodes with high uptime. Be more tolerant.
23655 - We were marking servers down when they could not answer every piece
23656 of the directory request we sent them. This was far too harsh.
23657 - Fix the torify (tsocks) config file to not use Tor for localhost
23659 - Directory authorities now go to the proper authority when asking for
23660 a networkstatus, even when they want a compressed one.
23661 - Fix a harmless bug that was causing Tor servers to log
23662 "Got an end because of misc error, but we're not an AP. Closing."
23663 - Authorities were treating their own descriptor changes as cosmetic,
23664 meaning the descriptor available in the network-status and the
23665 descriptor that clients downloaded were different.
23666 - The OS X installer was adding a symlink for tor_resolve but
23667 the binary was called tor-resolve (reported by Thomas Hardly).
23668 - Workaround a problem with some http proxies where they refuse GET
23669 requests that specify "Content-Length: 0" (reported by Adrian).
23670 - Fix wrong log message when you add a "HiddenServiceNodes" config
23671 line without any HiddenServiceDir line (reported by Chris Thomas).
23674 - Write the TorVersion into the state file so we have a prayer of
23675 keeping forward and backward compatibility.
23676 - Revive the FascistFirewall config option rather than eliminating it:
23677 now it's a synonym for ReachableAddresses *:80,*:443.
23678 - Clients choose directory servers from the network status lists,
23679 not from their internal list of router descriptors. Now they can
23680 go to caches directly rather than needing to go to authorities
23682 - Directory authorities ignore router descriptors that have only
23683 cosmetic differences: do this for 0.1.0.x servers now too.
23684 - Add a new flag to network-status indicating whether the server
23685 can answer v2 directory requests too.
23686 - Authdirs now stop whining so loudly about bad descriptors that
23687 they fetch from other dirservers. So when there's a log complaint,
23688 it's for sure from a freshly uploaded descriptor.
23689 - Reduce memory requirements in our structs by changing the order
23691 - There used to be two ways to specify your listening ports in a
23692 server descriptor: on the "router" line and with a separate "ports"
23693 line. Remove support for the "ports" line.
23694 - New config option "AuthDirRejectUnlisted" for auth dirservers as
23695 a panic button: if we get flooded with unusable servers we can
23696 revert to only listing servers in the approved-routers file.
23697 - Auth dir servers can now mark a fingerprint as "!reject" or
23698 "!invalid" in the approved-routers file (as its nickname), to
23699 refuse descriptors outright or include them but marked as invalid.
23700 - Servers store bandwidth history across restarts/crashes.
23701 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
23702 get a better idea of why their circuits failed. Not used yet.
23703 - Directory mirrors now cache up to 16 unrecognized network-status
23704 docs. Now we can add new authdirservers and they'll be cached too.
23705 - When picking a random directory, prefer non-authorities if any
23707 - New controller option "getinfo desc/all-recent" to fetch the
23708 latest server descriptor for every router that Tor knows about.
23711 Changes in version 0.1.0.16 - 2006-01-02
23712 o Crash bugfixes on 0.1.0.x:
23713 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
23714 corrupting the heap, losing FDs, or crashing when we need to resize
23715 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
23716 - It turns out sparc64 platforms crash on unaligned memory access
23717 too -- so detect and avoid this.
23718 - Handle truncated compressed data correctly (by detecting it and
23720 - Fix possible-but-unlikely free(NULL) in control.c.
23721 - When we were closing connections, there was a rare case that
23722 stomped on memory, triggering seg faults and asserts.
23723 - Avoid potential infinite recursion when building a descriptor. (We
23724 don't know that it ever happened, but better to fix it anyway.)
23725 - We were neglecting to unlink marked circuits from soon-to-close OR
23726 connections, which caused some rare scribbling on freed memory.
23727 - Fix a memory stomping race bug when closing the joining point of two
23728 rendezvous circuits.
23729 - Fix an assert in time parsing found by Steven Murdoch.
23731 o Other bugfixes on 0.1.0.x:
23732 - When we're doing reachability testing, provide more useful log
23733 messages so the operator knows what to expect.
23734 - Do not check whether DirPort is reachable when we are suppressing
23735 advertising it because of hibernation.
23736 - When building with -static or on Solaris, we sometimes needed -ldl.
23737 - When we're deciding whether a stream has enough circuits around
23738 that can handle it, count the freshly dirty ones and not the ones
23739 that are so dirty they won't be able to handle it.
23740 - When we're expiring old circuits, we had a logic error that caused
23741 us to close new rendezvous circuits rather than old ones.
23742 - Give a more helpful log message when you try to change ORPort via
23743 the controller: you should upgrade Tor if you want that to work.
23744 - We were failing to parse Tor versions that start with "Tor ".
23745 - Tolerate faulty streams better: when a stream fails for reason
23746 exitpolicy, stop assuming that the router is lying about his exit
23747 policy. When a stream fails for reason misc, allow it to retry just
23748 as if it was resolvefailed. When a stream has failed three times,
23749 reset its failure count so we can try again and get all three tries.
23752 Changes in version 0.1.1.10-alpha - 2005-12-11
23753 o Correctness bugfixes on 0.1.0.x:
23754 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
23755 corrupting the heap, losing FDs, or crashing when we need to resize
23756 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
23757 - Stop doing the complex voodoo overkill checking for insecure
23758 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
23759 - When we were closing connections, there was a rare case that
23760 stomped on memory, triggering seg faults and asserts.
23761 - We were neglecting to unlink marked circuits from soon-to-close OR
23762 connections, which caused some rare scribbling on freed memory.
23763 - When we're deciding whether a stream has enough circuits around
23764 that can handle it, count the freshly dirty ones and not the ones
23765 that are so dirty they won't be able to handle it.
23766 - Recover better from TCP connections to Tor servers that are
23767 broken but don't tell you (it happens!); and rotate TLS
23768 connections once a week.
23769 - When we're expiring old circuits, we had a logic error that caused
23770 us to close new rendezvous circuits rather than old ones.
23771 - Fix a scary-looking but apparently harmless bug where circuits
23772 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
23773 servers, and never switch to state CIRCUIT_STATE_OPEN.
23774 - When building with -static or on Solaris, we sometimes needed to
23776 - Give a useful message when people run Tor as the wrong user,
23777 rather than telling them to start chowning random directories.
23778 - We were failing to inform the controller about new .onion streams.
23780 o Security bugfixes on 0.1.0.x:
23781 - Refuse server descriptors if the fingerprint line doesn't match
23782 the included identity key. Tor doesn't care, but other apps (and
23783 humans) might actually be trusting the fingerprint line.
23784 - We used to kill the circuit when we receive a relay command we
23785 don't recognize. Now we just drop it.
23786 - Start obeying our firewall options more rigorously:
23787 . If we can't get to a dirserver directly, try going via Tor.
23788 . Don't ever try to connect (as a client) to a place our
23789 firewall options forbid.
23790 . If we specify a proxy and also firewall options, obey the
23791 firewall options even when we're using the proxy: some proxies
23792 can only proxy to certain destinations.
23793 - Fix a bug found by Lasse Overlier: when we were making internal
23794 circuits (intended to be cannibalized later for rendezvous and
23795 introduction circuits), we were picking them so that they had
23796 useful exit nodes. There was no need for this, and it actually
23797 aids some statistical attacks.
23798 - Start treating internal circuits and exit circuits separately.
23799 It's important to keep them separate because internal circuits
23800 have their last hops picked like middle hops, rather than like
23801 exit hops. So exiting on them will break the user's expectations.
23803 o Bugfixes on 0.1.1.x:
23804 - Take out the mis-feature where we tried to detect IP address
23805 flapping for people with DynDNS, and chose not to upload a new
23806 server descriptor sometimes.
23807 - Try to be compatible with OpenSSL 0.9.6 again.
23808 - Log fix: when the controller is logging about .onion addresses,
23809 sometimes it didn't include the ".onion" part of the address.
23810 - Don't try to modify options->DirServers internally -- if the
23811 user didn't specify any, just add the default ones directly to
23812 the trusted dirserver list. This fixes a bug where people running
23813 controllers would use SETCONF on some totally unrelated config
23814 option, and Tor would start yelling at them about changing their
23816 - Let the controller's redirectstream command specify a port, in
23817 case the controller wants to change that too.
23818 - When we requested a pile of server descriptors, we sometimes
23819 accidentally launched a duplicate request for the first one.
23820 - Bugfix for trackhostexits: write down the fingerprint of the
23821 chosen exit, not its nickname, because the chosen exit might not
23823 - When parsing foo.exit, if foo is unknown, and we are leaving
23824 circuits unattached, set the chosen_exit field and leave the
23825 address empty. This matters because controllers got confused
23827 - Directory authorities no longer try to download server
23828 descriptors that they know they will reject.
23830 o Features and updates:
23831 - Replace balanced trees with hash tables: this should make stuff
23832 significantly faster.
23833 - Resume using the AES counter-mode implementation that we ship,
23834 rather than OpenSSL's. Ours is significantly faster.
23835 - Many other CPU and memory improvements.
23836 - Add a new config option FastFirstHopPK (on by default) so clients
23837 do a trivial crypto handshake for their first hop, since TLS has
23838 already taken care of confidentiality and authentication.
23839 - Add a new config option TestSocks so people can see if their
23840 applications are using socks4, socks4a, socks5-with-ip, or
23841 socks5-with-hostname. This way they don't have to keep mucking
23842 with tcpdump and wondering if something got cached somewhere.
23843 - Warn when listening on a public address for socks. I suspect a
23844 lot of people are setting themselves up as open socks proxies,
23845 and they have no idea that jerks on the Internet are using them,
23846 since they simply proxy the traffic into the Tor network.
23847 - Add "private:*" as an alias in configuration for policies. Now
23848 you can simplify your exit policy rather than needing to list
23849 every single internal or nonroutable network space.
23850 - Add a new controller event type that allows controllers to get
23851 all server descriptors that were uploaded to a router in its role
23852 as authoritative dirserver.
23853 - Start shipping socks-extensions.txt, tor-doc-unix.html,
23854 tor-doc-server.html, and stylesheet.css in the tarball.
23855 - Stop shipping tor-doc.html in the tarball.
23858 Changes in version 0.1.1.9-alpha - 2005-11-15
23859 o Usability improvements:
23860 - Start calling it FooListenAddress rather than FooBindAddress,
23861 since few of our users know what it means to bind an address
23863 - Reduce clutter in server logs. We're going to try to make
23864 them actually usable now. New config option ProtocolWarnings that
23865 lets you hear about how _other Tors_ are breaking the protocol. Off
23867 - Divide log messages into logging domains. Once we put some sort
23868 of interface on this, it will let people looking at more verbose
23869 log levels specify the topics they want to hear more about.
23870 - Make directory servers return better http 404 error messages
23871 instead of a generic "Servers unavailable".
23872 - Check for even more Windows version flags when writing the platform
23873 string in server descriptors, and note any we don't recognize.
23874 - Clean up more of the OpenSSL memory when exiting, so we can detect
23875 memory leaks better.
23876 - Make directory authorities be non-versioning, non-naming by
23877 default. Now we can add new directory servers without requiring
23878 their operators to pay close attention.
23879 - When logging via syslog, include the pid whenever we provide
23880 a log entry. Suggested by Todd Fries.
23882 o Performance improvements:
23883 - Directory servers now silently throw away new descriptors that
23884 haven't changed much if the timestamps are similar. We do this to
23885 tolerate older Tor servers that upload a new descriptor every 15
23886 minutes. (It seemed like a good idea at the time.)
23887 - Inline bottleneck smartlist functions; use fast versions by default.
23888 - Add a "Map from digest to void*" abstraction digestmap_t so we
23889 can do less hex encoding/decoding. Use it in router_get_by_digest()
23890 to resolve a performance bottleneck.
23891 - Allow tor_gzip_uncompress to extract as much as possible from
23892 truncated compressed data. Try to extract as many
23893 descriptors as possible from truncated http responses (when
23894 DIR_PURPOSE_FETCH_ROUTERDESC).
23895 - Make circ->onionskin a pointer, not a static array. moria2 was using
23896 125000 circuit_t's after it had been up for a few weeks, which
23897 translates to 20+ megs of wasted space.
23898 - The private half of our EDH handshake keys are now chosen out
23899 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
23901 o Security improvements:
23902 - Start making directory caches retain old routerinfos, so soon
23903 clients can start asking by digest of descriptor rather than by
23904 fingerprint of server.
23905 - Add half our entropy from RAND_poll in OpenSSL. This knows how
23906 to use egd (if present), openbsd weirdness (if present), vms/os2
23907 weirdness (if we ever port there), and more in the future.
23909 o Bugfixes on 0.1.0.x:
23910 - Do round-robin writes of at most 16 kB per write. This might be
23911 more fair on loaded Tor servers, and it might resolve our Windows
23912 crash bug. It might also slow things down.
23913 - Our TLS handshakes were generating a single public/private
23914 keypair for the TLS context, rather than making a new one for
23915 each new connections. Oops. (But we were still rotating them
23916 periodically, so it's not so bad.)
23917 - When we were cannibalizing a circuit with a particular exit
23918 node in mind, we weren't checking to see if that exit node was
23919 already present earlier in the circuit. Oops.
23920 - When a Tor server's IP changes (e.g. from a dyndns address),
23921 upload a new descriptor so clients will learn too.
23922 - Really busy servers were keeping enough circuits open on stable
23923 connections that they were wrapping around the circuit_id
23924 space. (It's only two bytes.) This exposed a bug where we would
23925 feel free to reuse a circuit_id even if it still exists but has
23926 been marked for close. Try to fix this bug. Some bug remains.
23927 - If we would close a stream early (e.g. it asks for a .exit that
23928 we know would refuse it) but the LeaveStreamsUnattached config
23929 option is set by the controller, then don't close it.
23931 o Bugfixes on 0.1.1.8-alpha:
23932 - Fix a big pile of memory leaks, some of them serious.
23933 - Do not try to download a routerdesc if we would immediately reject
23935 - Resume inserting a newline between all router descriptors when
23936 generating (old style) signed directories, since our spec says
23938 - When providing content-type application/octet-stream for
23939 server descriptors using .z, we were leaving out the
23940 content-encoding header. Oops. (Everything tolerated this just
23941 fine, but that doesn't mean we need to be part of the problem.)
23942 - Fix a potential seg fault in getconf and getinfo using version 1
23943 of the controller protocol.
23944 - Avoid crash: do not check whether DirPort is reachable when we
23945 are suppressing it because of hibernation.
23946 - Make --hash-password not crash on exit.
23949 Changes in version 0.1.1.8-alpha - 2005-10-07
23950 o New features (major):
23951 - Clients don't download or use the directory anymore. Now they
23952 download and use network-statuses from the trusted dirservers,
23953 and fetch individual server descriptors as needed from mirrors.
23954 See dir-spec.txt for all the gory details.
23955 - Be more conservative about whether to advertise our DirPort.
23956 The main change is to not advertise if we're running at capacity
23957 and either a) we could hibernate or b) our capacity is low and
23958 we're using a default DirPort.
23959 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
23961 o New features (minor):
23962 - Try to be smart about when to retry network-status and
23963 server-descriptor fetches. Still needs some tuning.
23964 - Stop parsing, storing, or using running-routers output (but
23965 mirrors still cache and serve it).
23966 - Consider a threshold of versioning dirservers (dirservers who have
23967 an opinion about which Tor versions are still recommended) before
23968 deciding whether to warn the user that he's obsolete.
23969 - Dirservers can now reject/invalidate by key and IP, with the
23970 config options "AuthDirInvalid" and "AuthDirReject". This is
23971 useful since currently we automatically list servers as running
23972 and usable even if we know they're jerks.
23973 - Provide dire warnings to any users who set DirServer; move it out
23974 of torrc.sample and into torrc.complete.
23975 - Add MyFamily to torrc.sample in the server section.
23976 - Add nicknames to the DirServer line, so we can refer to them
23977 without requiring all our users to memorize their IP addresses.
23978 - When we get an EOF or a timeout on a directory connection, note
23979 how many bytes of serverdesc we are dropping. This will help
23980 us determine whether it is smart to parse incomplete serverdesc
23982 - Add a new function to "change pseudonyms" -- that is, to stop
23983 using any currently-dirty circuits for new streams, so we don't
23984 link new actions to old actions. Currently it's only called on
23985 HUP (or SIGNAL RELOAD).
23986 - On sighup, if UseHelperNodes changed to 1, use new circuits.
23987 - Start using RAND_bytes rather than RAND_pseudo_bytes from
23988 OpenSSL. Also, reseed our entropy every hour, not just at
23989 startup. And entropy in 512-bit chunks, not 160-bit chunks.
23991 o Fixes on 0.1.1.7-alpha:
23992 - Nobody ever implemented EVENT_ADDRMAP for control protocol
23993 version 0, so don't let version 0 controllers ask for it.
23994 - If you requested something with too many newlines via the
23995 v1 controller protocol, you could crash tor.
23996 - Fix a number of memory leaks, including some pretty serious ones.
23997 - Re-enable DirPort testing again, so Tor servers will be willing
23998 to advertise their DirPort if it's reachable.
23999 - On TLS handshake, only check the other router's nickname against
24000 its expected nickname if is_named is set.
24002 o Fixes forward-ported from 0.1.0.15:
24003 - Don't crash when we don't have any spare file descriptors and we
24004 try to spawn a dns or cpu worker.
24005 - Make the numbers in read-history and write-history into uint64s,
24006 so they don't overflow and publish negatives in the descriptor.
24008 o Fixes on 0.1.0.x:
24009 - For the OS X package's modified privoxy config file, comment
24010 out the "logfile" line so we don't log everything passed
24012 - We were whining about using socks4 or socks5-with-local-lookup
24013 even when it's an IP in the "virtual" range we designed exactly
24015 - We were leaking some memory every time the client changes IPs.
24016 - Never call free() on tor_malloc()d memory. This will help us
24017 use dmalloc to detect memory leaks.
24018 - Check for named servers when looking them up by nickname;
24019 warn when we'recalling a non-named server by its nickname;
24020 don't warn twice about the same name.
24021 - Try to list MyFamily elements by key, not by nickname, and warn
24022 if we've not heard of the server.
24023 - Make windows platform detection (uname equivalent) smarter.
24024 - It turns out sparc64 doesn't like unaligned access either.
24027 Changes in version 0.1.0.15 - 2005-09-23
24028 o Bugfixes on 0.1.0.x:
24029 - Reject ports 465 and 587 (spam targets) in default exit policy.
24030 - Don't crash when we don't have any spare file descriptors and we
24031 try to spawn a dns or cpu worker.
24032 - Get rid of IgnoreVersion undocumented config option, and make us
24033 only warn, never exit, when we're running an obsolete version.
24034 - Don't try to print a null string when your server finds itself to
24035 be unreachable and the Address config option is empty.
24036 - Make the numbers in read-history and write-history into uint64s,
24037 so they don't overflow and publish negatives in the descriptor.
24038 - Fix a minor memory leak in smartlist_string_remove().
24039 - We were only allowing ourselves to upload a server descriptor at
24040 most every 20 minutes, even if it changed earlier than that.
24041 - Clean up log entries that pointed to old URLs.
24044 Changes in version 0.1.1.7-alpha - 2005-09-14
24045 o Fixes on 0.1.1.6-alpha:
24046 - Exit servers were crashing when people asked them to make a
24047 connection to an address not in their exit policy.
24048 - Looking up a non-existent stream for a v1 control connection would
24050 - Fix a seg fault if we ask a dirserver for a descriptor by
24051 fingerprint but he doesn't know about him.
24052 - SETCONF was appending items to linelists, not clearing them.
24053 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
24054 out and refuse the setconf if it would fail.
24055 - Downgrade the dirserver log messages when whining about
24059 - Add Peter Palfrader's check-tor script to tor/contrib/
24060 It lets you easily check whether a given server (referenced by
24061 nickname) is reachable by you.
24062 - Numerous changes to move towards client-side v2 directories. Not
24065 o Fixes on 0.1.0.x:
24066 - If the user gave tor an odd number of command-line arguments,
24067 we were silently ignoring the last one. Now we complain and fail.
24068 [This wins the oldest-bug prize -- this bug has been present since
24069 November 2002, as released in Tor 0.0.0.]
24070 - Do not use unaligned memory access on alpha, mips, or mipsel.
24071 It *works*, but is very slow, so we treat them as if it doesn't.
24072 - Retry directory requests if we fail to get an answer we like
24073 from a given dirserver (we were retrying before, but only if
24074 we fail to connect).
24075 - When writing the RecommendedVersions line, sort them first.
24076 - When the client asked for a rendezvous port that the hidden
24077 service didn't want to provide, we were sending an IP address
24078 back along with the end cell. Fortunately, it was zero. But stop
24080 - Correct "your server is reachable" log entries to indicate that
24081 it was self-testing that told us so.
24084 Changes in version 0.1.1.6-alpha - 2005-09-09
24085 o Fixes on 0.1.1.5-alpha:
24086 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
24087 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
24088 - Fix bug with tor_memmem finding a match at the end of the string.
24089 - Make unit tests run without segfaulting.
24090 - Resolve some solaris x86 compile warnings.
24091 - Handle duplicate lines in approved-routers files without warning.
24092 - Fix bug where as soon as a server refused any requests due to his
24093 exit policy (e.g. when we ask for localhost and he tells us that's
24094 127.0.0.1 and he won't do it), we decided he wasn't obeying his
24095 exit policy using him for any exits.
24096 - Only do openssl hardware accelerator stuff if openssl version is
24099 o New controller features/fixes:
24100 - Add a "RESETCONF" command so you can set config options like
24101 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
24102 a config option in the torrc with no value, then it clears it
24103 entirely (rather than setting it to its default).
24104 - Add a "GETINFO config-file" to tell us where torrc is.
24105 - Avoid sending blank lines when GETINFO replies should be empty.
24106 - Add a QUIT command for the controller (for using it manually).
24107 - Fix a bug in SAVECONF that was adding default dirservers and
24108 other redundant entries to the torrc file.
24110 o Start on the new directory design:
24111 - Generate, publish, cache, serve new network-status format.
24112 - Publish individual descriptors (by fingerprint, by "all", and by
24114 - Publish client and server recommended versions separately.
24115 - Allow tor_gzip_uncompress() to handle multiple concatenated
24116 compressed strings. Serve compressed groups of router
24117 descriptors. The compression logic here could be more
24119 - Distinguish v1 authorities (all currently trusted directories)
24120 from v2 authorities (all trusted directories).
24121 - Change DirServers config line to note which dirs are v1 authorities.
24122 - Add configuration option "V1AuthoritativeDirectory 1" which
24123 moria1, moria2, and tor26 should set.
24124 - Remove option when getting directory cache to see whether they
24125 support running-routers; they all do now. Replace it with one
24126 to see whether caches support v2 stuff.
24129 - Dirservers now do their own external reachability testing of each
24130 Tor server, and only list them as running if they've been found to
24131 be reachable. We also send back warnings to the server's logs if
24132 it uploads a descriptor that we already believe is unreachable.
24133 - Implement exit enclaves: if we know an IP address for the
24134 destination, and there's a running Tor server at that address
24135 which allows exit to the destination, then extend the circuit to
24136 that exit first. This provides end-to-end encryption and end-to-end
24137 authentication. Also, if the user wants a .exit address or enclave,
24138 use 4 hops rather than 3, and cannibalize a general circ for it
24140 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
24141 controller. Also, rotate dns and cpu workers if the controller
24142 changes options that will affect them; and initialize the dns
24143 worker cache tree whether or not we start out as a server.
24144 - Only upload a new server descriptor when options change, 18
24145 hours have passed, uptime is reset, or bandwidth changes a lot.
24146 - Check [X-]Forwarded-For headers in HTTP requests when generating
24147 log messages. This lets people run dirservers (and caches) behind
24148 Apache but still know which IP addresses are causing warnings.
24150 o Config option changes:
24151 - Replace (Fascist)Firewall* config options with a new
24152 ReachableAddresses option that understands address policies.
24153 For example, "ReachableAddresses *:80,*:443"
24154 - Get rid of IgnoreVersion undocumented config option, and make us
24155 only warn, never exit, when we're running an obsolete version.
24156 - Make MonthlyAccountingStart config option truly obsolete now.
24158 o Fixes on 0.1.0.x:
24159 - Reject ports 465 and 587 in the default exit policy, since
24160 people have started using them for spam too.
24161 - It turns out we couldn't bootstrap a network since we added
24162 reachability detection in 0.1.0.1-rc. Good thing the Tor network
24163 has never gone down. Add an AssumeReachable config option to let
24164 servers and dirservers bootstrap. When we're trying to build a
24165 high-uptime or high-bandwidth circuit but there aren't enough
24166 suitable servers, try being less picky rather than simply failing.
24167 - Our logic to decide if the OR we connected to was the right guy
24168 was brittle and maybe open to a mitm for unverified routers.
24169 - We weren't cannibalizing circuits correctly for
24170 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
24171 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
24172 build those from scratch. This should make hidden services faster.
24173 - Predict required circuits better, with an eye toward making hidden
24174 services faster on the service end.
24175 - Retry streams if the exit node sends back a 'misc' failure. This
24176 should result in fewer random failures. Also, after failing
24177 from resolve failed or misc, reset the num failures, so we give
24178 it a fair shake next time we try.
24179 - Clean up the rendezvous warn log msgs, and downgrade some to info.
24180 - Reduce severity on logs about dns worker spawning and culling.
24181 - When we're shutting down and we do something like try to post a
24182 server descriptor or rendezvous descriptor, don't complain that
24183 we seem to be unreachable. Of course we are, we're shutting down.
24184 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
24185 We don't use them yet, but maybe one day our DNS resolver will be
24186 able to discover them.
24187 - Make ContactInfo mandatory for authoritative directory servers.
24188 - Require server descriptors to list IPv4 addresses -- hostnames
24189 are no longer allowed. This also fixes some potential security
24190 problems with people providing hostnames as their address and then
24191 preferentially resolving them to partition users.
24192 - Change log line for unreachability to explicitly suggest /etc/hosts
24193 as the culprit. Also make it clearer what IP address and ports we're
24194 testing for reachability.
24195 - Put quotes around user-supplied strings when logging so users are
24196 more likely to realize if they add bad characters (like quotes)
24198 - Let auth dir servers start without specifying an Address config
24200 - Make unit tests (and other invocations that aren't the real Tor)
24201 run without launching listeners, creating subdirectories, and so on.
24204 Changes in version 0.1.1.5-alpha - 2005-08-08
24205 o Bugfixes included in 0.1.0.14.
24207 o Bugfixes on 0.1.0.x:
24208 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
24209 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
24210 it would silently using ignore the 6668.
24213 Changes in version 0.1.0.14 - 2005-08-08
24214 o Bugfixes on 0.1.0.x:
24215 - Fix the other half of the bug with crypto handshakes
24217 - Fix an assert trigger if you send a 'signal term' via the
24218 controller when it's listening for 'event info' messages.
24221 Changes in version 0.1.1.4-alpha - 2005-08-04
24222 o Bugfixes included in 0.1.0.13.
24225 - Improve tor_gettimeofday() granularity on windows.
24226 - Make clients regenerate their keys when their IP address changes.
24227 - Implement some more GETINFO goodness: expose helper nodes, config
24228 options, getinfo keys.
24231 Changes in version 0.1.0.13 - 2005-08-04
24232 o Bugfixes on 0.1.0.x:
24233 - Fix a critical bug in the security of our crypto handshakes.
24234 - Fix a size_t underflow in smartlist_join_strings2() that made
24235 it do bad things when you hand it an empty smartlist.
24236 - Fix Windows installer to ship Tor license (thanks to Aphex for
24237 pointing out this oversight) and put a link to the doc directory
24239 - Explicitly set no-unaligned-access for sparc: it turns out the
24240 new gcc's let you compile broken code, but that doesn't make it
24244 Changes in version 0.1.1.3-alpha - 2005-07-23
24245 o Bugfixes on 0.1.1.2-alpha:
24246 - Fix a bug in handling the controller's "post descriptor"
24248 - Fix several bugs in handling the controller's "extend circuit"
24250 - Fix a bug in handling the controller's "stream status" event.
24251 - Fix an assert failure if we have a controller listening for
24252 circuit events and we go offline.
24253 - Re-allow hidden service descriptors to publish 0 intro points.
24254 - Fix a crash when generating your hidden service descriptor if
24255 you don't have enough intro points already.
24257 o New features on 0.1.1.2-alpha:
24258 - New controller function "getinfo accounting", to ask how
24259 many bytes we've used in this time period.
24260 - Experimental support for helper nodes: a lot of the risk from
24261 a small static adversary comes because users pick new random
24262 nodes every time they rebuild a circuit. Now users will try to
24263 stick to the same small set of entry nodes if they can. Not
24264 enabled by default yet.
24266 o Bugfixes on 0.1.0.12:
24267 - If you're an auth dir server, always publish your dirport,
24268 even if you haven't yet found yourself to be reachable.
24269 - Fix a size_t underflow in smartlist_join_strings2() that made
24270 it do bad things when you hand it an empty smartlist.
24273 Changes in version 0.1.0.12 - 2005-07-18
24274 o New directory servers:
24275 - tor26 has changed IP address.
24277 o Bugfixes on 0.1.0.x:
24278 - Fix a possible double-free in tor_gzip_uncompress().
24279 - When --disable-threads is set, do not search for or link against
24280 pthreads libraries.
24281 - Don't trigger an assert if an authoritative directory server
24282 claims its dirport is 0.
24283 - Fix bug with removing Tor as an NT service: some people were
24284 getting "The service did not return an error." Thanks to Matt
24288 Changes in version 0.1.1.2-alpha - 2005-07-15
24289 o New directory servers:
24290 - tor26 has changed IP address.
24292 o Bugfixes on 0.1.0.x, crashes/leaks:
24293 - Port the servers-not-obeying-their-exit-policies fix from
24295 - Fix an fd leak in start_daemon().
24296 - On Windows, you can't always reopen a port right after you've
24297 closed it. So change retry_listeners() to only close and re-open
24298 ports that have changed.
24299 - Fix a possible double-free in tor_gzip_uncompress().
24301 o Bugfixes on 0.1.0.x, usability:
24302 - When tor_socketpair() fails in Windows, give a reasonable
24303 Windows-style errno back.
24304 - Let people type "tor --install" as well as "tor -install" when
24306 want to make it an NT service.
24307 - NT service patch from Matt Edman to improve error messages.
24308 - When the controller asks for a config option with an abbreviated
24309 name, give the full name in our response.
24310 - Correct the man page entry on TrackHostExitsExpire.
24311 - Looks like we were never delivering deflated (i.e. compressed)
24312 running-routers lists, even when asked. Oops.
24313 - When --disable-threads is set, do not search for or link against
24314 pthreads libraries.
24316 o Bugfixes on 0.1.1.x:
24317 - Fix a seg fault with autodetecting which controller version is
24321 - New hidden service descriptor format: put a version in it, and
24322 let people specify introduction/rendezvous points that aren't
24323 in "the directory" (which is subjective anyway).
24324 - Allow the DEBUG controller event to work again. Mark certain log
24325 entries as "don't tell this to controllers", so we avoid cycles.
24328 Changes in version 0.1.0.11 - 2005-06-30
24329 o Bugfixes on 0.1.0.x:
24330 - Fix major security bug: servers were disregarding their
24331 exit policies if clients behaved unexpectedly.
24332 - Make OS X init script check for missing argument, so we don't
24333 confuse users who invoke it incorrectly.
24334 - Fix a seg fault in "tor --hash-password foo".
24335 - The MAPADDRESS control command was broken.
24338 Changes in version 0.1.1.1-alpha - 2005-06-29
24340 - Make OS X init script check for missing argument, so we don't
24341 confuse users who invoke it incorrectly.
24342 - Fix a seg fault in "tor --hash-password foo".
24343 - Fix a possible way to DoS dirservers.
24344 - When we complain that your exit policy implicitly allows local or
24345 private address spaces, name them explicitly so operators can
24347 - Make the log message less scary when all the dirservers are
24348 temporarily unreachable.
24349 - We were printing the number of idle dns workers incorrectly when
24353 - Revised controller protocol (version 1) that uses ascii rather
24354 than binary. Add supporting libraries in python and java so you
24355 can use the controller from your applications without caring how
24356 our protocol works.
24357 - Spiffy new support for crypto hardware accelerators. Can somebody
24361 Changes in version 0.0.9.10 - 2005-06-16
24362 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
24363 - Refuse relay cells that claim to have a length larger than the
24364 maximum allowed. This prevents a potential attack that could read
24365 arbitrary memory (e.g. keys) from an exit server's process
24369 Changes in version 0.1.0.10 - 2005-06-14
24370 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
24371 libevent before 1.1a.
24374 Changes in version 0.1.0.9-rc - 2005-06-09
24376 - Reset buf->highwater every time buf_shrink() is called, not just on
24377 a successful shrink. This was causing significant memory bloat.
24378 - Fix buffer overflow when checking hashed passwords.
24379 - Security fix: if seeding the RNG on Win32 fails, quit.
24380 - Allow seeding the RNG on Win32 even when you're not running as
24382 - Disable threading on Solaris too. Something is wonky with it,
24383 cpuworkers, and reentrant libs.
24384 - Reenable the part of the code that tries to flush as soon as an
24385 OR outbuf has a full TLS record available. Perhaps this will make
24386 OR outbufs not grow as huge except in rare cases, thus saving lots
24387 of CPU time plus memory.
24388 - Reject malformed .onion addresses rather then passing them on as
24389 normal web requests.
24390 - Adapt patch from Adam Langley: fix possible memory leak in
24391 tor_lookup_hostname().
24392 - Initialize libevent later in the startup process, so the logs are
24393 already established by the time we start logging libevent warns.
24394 - Use correct errno on win32 if libevent fails.
24395 - Check and warn about known-bad/slow libevent versions.
24396 - Pay more attention to the ClientOnly config option.
24397 - Have torctl.in/tor.sh.in check for location of su binary (needed
24399 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
24400 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
24401 HttpProxyAuthenticator
24402 - Stop warning about sigpipes in the logs. We're going to
24403 pretend that getting these occassionally is normal and fine.
24404 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
24406 installer screens; and don't put stuff into StartupItems unless
24407 the user asks you to.
24408 - Require servers that use the default dirservers to have public IP
24409 addresses. We have too many servers that are configured with private
24410 IPs and their admins never notice the log entries complaining that
24411 their descriptors are being rejected.
24412 - Add OSX uninstall instructions. An actual uninstall script will
24416 Changes in version 0.1.0.8-rc - 2005-05-23
24418 - It turns out that kqueue on OS X 10.3.9 was causing kernel
24419 panics. Disable kqueue on all OS X Tors.
24420 - Fix RPM: remove duplicate line accidentally added to the rpm
24422 - Disable threads on openbsd too, since its gethostaddr is not
24424 - Tolerate libevent 0.8 since it still works, even though it's
24426 - Enable building on Red Hat 9.0 again.
24427 - Allow the middle hop of the testing circuit to be running any
24428 version, now that most of them have the bugfix to let them connect
24429 to unknown servers. This will allow reachability testing to work
24430 even when 0.0.9.7-0.0.9.9 become obsolete.
24431 - Handle relay cells with rh.length too large. This prevents
24432 a potential attack that could read arbitrary memory (maybe even
24433 keys) from the exit server's process.
24434 - We screwed up the dirport reachability testing when we don't yet
24435 have a cached version of the directory. Hopefully now fixed.
24436 - Clean up router_load_single_router() (used by the controller),
24437 so it doesn't seg fault on error.
24438 - Fix a minor memory leak when somebody establishes an introduction
24439 point at your Tor server.
24440 - If a socks connection ends because read fails, don't warn that
24441 you're not sending a socks reply back.
24444 - Add HttpProxyAuthenticator config option too, that works like
24445 the HttpsProxyAuthenticator config option.
24446 - Encode hashed controller passwords in hex instead of base64,
24447 to make it easier to write controllers.
24450 Changes in version 0.1.0.7-rc - 2005-05-17
24452 - Fix a bug in the OS X package installer that prevented it from
24453 installing on Tiger.
24454 - Fix a script bug in the OS X package installer that made it
24455 complain during installation.
24456 - Find libevent even if it's hiding in /usr/local/ and your
24457 CFLAGS and LDFLAGS don't tell you to look there.
24458 - Be able to link with libevent as a shared library (the default
24459 after 1.0d), even if it's hiding in /usr/local/lib and even
24460 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
24461 assuming you're running gcc. Otherwise fail and give a useful
24463 - Fix a bug in the RPM packager: set home directory for _tor to
24464 something more reasonable when first installing.
24465 - Free a minor amount of memory that is still reachable on exit.
24468 Changes in version 0.1.0.6-rc - 2005-05-14
24470 - Implement --disable-threads configure option. Disable threads on
24471 netbsd by default, because it appears to have no reentrant resolver
24473 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
24474 release (1.1) detects and disables kqueue if it's broken.
24475 - Append default exit policy before checking for implicit internal
24476 addresses. Now we don't log a bunch of complaints on startup
24477 when using the default exit policy.
24478 - Some people were putting "Address " in their torrc, and they had
24479 a buggy resolver that resolved " " to 0.0.0.0. Oops.
24480 - If DataDir is ~/.tor, and that expands to /.tor, then default to
24481 LOCALSTATEDIR/tor instead.
24482 - Fix fragmented-message bug in TorControl.py.
24483 - Resolve a minor bug which would prevent unreachable dirports
24484 from getting suppressed in the published descriptor.
24485 - When the controller gave us a new descriptor, we weren't resolving
24486 it immediately, so Tor would think its address was 0.0.0.0 until
24487 we fetched a new directory.
24488 - Fix an uppercase/lowercase case error in suppressing a bogus
24489 libevent warning on some Linuxes.
24492 - Begin scrubbing sensitive strings from logs by default. Turn off
24493 the config option SafeLogging if you need to do debugging.
24494 - Switch to a new buffer management algorithm, which tries to avoid
24495 reallocing and copying quite as much. In first tests it looks like
24496 it uses *more* memory on average, but less cpu.
24497 - First cut at support for "create-fast" cells. Clients can use
24498 these when extending to their first hop, since the TLS already
24499 provides forward secrecy and authentication. Not enabled on
24501 - When dirservers refuse a router descriptor, we now log its
24502 contactinfo, platform, and the poster's IP address.
24503 - Call tor_free_all instead of connections_free_all after forking, to
24504 save memory on systems that need to fork.
24505 - Whine at you if you're a server and you don't set your contactinfo.
24506 - Implement --verify-config command-line option to check if your torrc
24507 is valid without actually launching Tor.
24508 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
24509 rather than just rejecting it.
24512 Changes in version 0.1.0.5-rc - 2005-04-27
24514 - Stop trying to print a null pointer if an OR conn fails because
24515 we didn't like its cert.
24517 - Switch our internal buffers implementation to use a ring buffer,
24518 to hopefully improve performance for fast servers a lot.
24519 - Add HttpsProxyAuthenticator support (basic auth only), based
24520 on patch from Adam Langley.
24521 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
24522 the fast servers that have been joining lately.
24523 - Give hidden service accesses extra time on the first attempt,
24524 since 60 seconds is often only barely enough. This might improve
24526 - Improve performance for dirservers: stop re-parsing the whole
24527 directory every time you regenerate it.
24528 - Add more debugging info to help us find the weird dns freebsd
24529 pthreads bug; cleaner debug messages to help track future issues.
24532 Changes in version 0.0.9.9 - 2005-04-23
24533 o Bugfixes on 0.0.9.x:
24534 - If unofficial Tor clients connect and send weird TLS certs, our
24535 Tor server triggers an assert. This release contains a minimal
24536 backport from the broader fix that we put into 0.1.0.4-rc.
24539 Changes in version 0.1.0.4-rc - 2005-04-23
24541 - If unofficial Tor clients connect and send weird TLS certs, our
24542 Tor server triggers an assert. Stop asserting, and start handling
24543 TLS errors better in other situations too.
24544 - When the controller asks us to tell it about all the debug-level
24545 logs, it turns out we were generating debug-level logs while
24546 telling it about them, which turns into a bad loop. Now keep
24547 track of whether you're sending a debug log to the controller,
24548 and don't log when you are.
24549 - Fix the "postdescriptor" feature of the controller interface: on
24550 non-complete success, only say "done" once.
24552 - Clients are now willing to load balance over up to 2mB, not 1mB,
24553 of advertised bandwidth capacity.
24554 - Add a NoPublish config option, so you can be a server (e.g. for
24555 testing running Tor servers in other Tor networks) without
24556 publishing your descriptor to the primary dirservers.
24559 Changes in version 0.1.0.3-rc - 2005-04-08
24560 o Improvements on 0.1.0.2-rc:
24561 - Client now retries when streams end early for 'hibernating' or
24562 'resource limit' reasons, rather than failing them.
24563 - More automated handling for dirserver operators:
24564 - Automatically approve nodes running 0.1.0.2-rc or later,
24565 now that the the reachability detection stuff is working.
24566 - Now we allow two unverified servers with the same nickname
24567 but different keys. But if a nickname is verified, only that
24568 nickname+key are allowed.
24569 - If you're an authdirserver connecting to an address:port,
24570 and it's not the OR you were expecting, forget about that
24571 descriptor. If he *was* the one you were expecting, then forget
24572 about all other descriptors for that address:port.
24573 - Allow servers to publish descriptors from 12 hours in the future.
24574 Corollary: only whine about clock skew from the dirserver if
24575 he's a trusted dirserver (since now even verified servers could
24576 have quite wrong clocks).
24577 - Adjust maximum skew and age for rendezvous descriptors: let skew
24578 be 48 hours rather than 90 minutes.
24579 - Efficiency improvements:
24580 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
24581 it much faster to look up a circuit for each relay cell.
24582 - Remove most calls to assert_all_pending_dns_resolves_ok(),
24583 since they're eating our cpu on exit nodes.
24584 - Stop wasting time doing a case insensitive comparison for every
24585 dns name every time we do any lookup. Canonicalize the names to
24586 lowercase and be done with it.
24587 - Start sending 'truncated' cells back rather than destroy cells,
24588 if the circuit closes in front of you. This means we won't have
24589 to abandon partially built circuits.
24590 - Only warn once per nickname from add_nickname_list_to_smartlist
24591 per failure, so an entrynode or exitnode choice that's down won't
24593 - Put a note in the torrc about abuse potential with the default
24595 - Revise control spec and implementation to allow all log messages to
24596 be sent to controller with their severities intact (suggested by
24597 Matt Edman). Update TorControl to handle new log event types.
24598 - Provide better explanation messages when controller's POSTDESCRIPTOR
24600 - Stop putting nodename in the Platform string in server descriptors.
24601 It doesn't actually help, and it is confusing/upsetting some people.
24603 o Bugfixes on 0.1.0.2-rc:
24604 - We were printing the host mask wrong in exit policies in server
24605 descriptors. This isn't a critical bug though, since we were still
24606 obeying the exit policy internally.
24607 - Fix Tor when compiled with libevent but without pthreads: move
24608 connection_unregister() from _connection_free() to
24610 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
24611 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
24612 when we look through the connection array, we'll find any of the
24613 cpu/dnsworkers. This is no good.
24615 o Bugfixes on 0.0.9.8:
24616 - Fix possible bug on threading platforms (e.g. win32) which was
24617 leaking a file descriptor whenever a cpuworker or dnsworker died.
24618 - When using preferred entry or exit nodes, ignore whether the
24619 circuit wants uptime or capacity. They asked for the nodes, they
24621 - chdir() to your datadirectory at the *end* of the daemonize process,
24622 not the beginning. This was a problem because the first time you
24623 run tor, if your datadir isn't there, and you have runasdaemon set
24624 to 1, it will try to chdir to it before it tries to create it. Oops.
24625 - Handle changed router status correctly when dirserver reloads
24626 fingerprint file. We used to be dropping all unverified descriptors
24627 right then. The bug was hidden because we would immediately
24628 fetch a directory from another dirserver, which would include the
24629 descriptors we just dropped.
24630 - When we're connecting to an OR and he's got a different nickname/key
24631 than we were expecting, only complain loudly if we're an OP or a
24632 dirserver. Complaining loudly to the OR admins just confuses them.
24633 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
24634 artificially capped at 500kB.
24637 Changes in version 0.0.9.8 - 2005-04-07
24638 o Bugfixes on 0.0.9.x:
24639 - We have a bug that I haven't found yet. Sometimes, very rarely,
24640 cpuworkers get stuck in the 'busy' state, even though the cpuworker
24641 thinks of itself as idle. This meant that no new circuits ever got
24642 established. Here's a workaround to kill any cpuworker that's been
24643 busy for more than 100 seconds.
24646 Changes in version 0.1.0.2-rc - 2005-04-01
24647 o Bugfixes on 0.1.0.1-rc:
24648 - Fixes on reachability detection:
24649 - Don't check for reachability while hibernating.
24650 - If ORPort is reachable but DirPort isn't, still publish the
24651 descriptor, but zero out DirPort until it's found reachable.
24652 - When building testing circs for ORPort testing, use only
24653 high-bandwidth nodes, so fewer circuits fail.
24654 - Complain about unreachable ORPort separately from unreachable
24655 DirPort, so the user knows what's going on.
24656 - Make sure we only conclude ORPort reachability if we didn't
24657 initiate the conn. Otherwise we could falsely conclude that
24658 we're reachable just because we connected to the guy earlier
24659 and he used that same pipe to extend to us.
24660 - Authdirservers shouldn't do ORPort reachability detection,
24661 since they're in clique mode, so it will be rare to find a
24662 server not already connected to them.
24663 - When building testing circuits, always pick middle hops running
24664 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
24665 bug. (This is a kludge; it will go away when 0.0.9.x becomes
24667 - When we decide we're reachable, actually publish our descriptor
24669 - Fix bug in redirectstream in the controller.
24670 - Fix the state descriptor strings so logs don't claim edge streams
24671 are in a different state than they actually are.
24672 - Use recent libevent features when possible (this only really affects
24673 win32 and osx right now, because the new libevent with these
24674 features hasn't been released yet). Add code to suppress spurious
24676 - Prevent possible segfault in connection_close_unattached_ap().
24677 - Fix newlines on torrc in win32.
24678 - Improve error msgs when tor-resolve fails.
24680 o Improvements on 0.0.9.x:
24681 - New experimental script tor/contrib/ExerciseServer.py (needs more
24682 work) that uses the controller interface to build circuits and
24683 fetch pages over them. This will help us bootstrap servers that
24684 have lots of capacity but haven't noticed it yet.
24685 - New experimental script tor/contrib/PathDemo.py (needs more work)
24686 that uses the controller interface to let you choose whole paths
24688 "<hostname>.<path,separated by dots>.<length of path>.path"
24689 - When we've connected to an OR and handshaked but didn't like
24690 the result, we were closing the conn without sending destroy
24691 cells back for pending circuits. Now send those destroys.
24694 Changes in version 0.0.9.7 - 2005-04-01
24695 o Bugfixes on 0.0.9.x:
24696 - Fix another race crash bug (thanks to Glenn Fink for reporting).
24697 - Compare identity to identity, not to nickname, when extending to
24698 a router not already in the directory. This was preventing us from
24699 extending to unknown routers. Oops.
24700 - Make sure to create OS X Tor user in <500 range, so we aren't
24701 creating actual system users.
24702 - Note where connection-that-hasn't-sent-end was marked, and fix
24703 a few really loud instances of this harmless bug (it's fixed more
24707 Changes in version 0.1.0.1-rc - 2005-03-28
24709 - Add reachability testing. Your Tor server will automatically try
24710 to see if its ORPort and DirPort are reachable from the outside,
24711 and it won't upload its descriptor until it decides they are.
24712 - Handle unavailable hidden services better. Handle slow or busy
24713 hidden services better.
24714 - Add support for CONNECTing through https proxies, with "HttpsProxy"
24716 - New exit policy: accept most low-numbered ports, rather than
24717 rejecting most low-numbered ports.
24718 - More Tor controller support (still experimental). See
24719 http://tor.eff.org/doc/control-spec.txt for all the new features,
24720 including signals to emulate unix signals from any platform;
24721 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
24722 closestream; closecircuit; etc.
24723 - Make nt services work and start on startup on win32 (based on
24724 patch by Matt Edman).
24725 - Add a new AddressMap config directive to rewrite incoming socks
24726 addresses. This lets you, for example, declare an implicit
24727 required exit node for certain sites.
24728 - Add a new TrackHostExits config directive to trigger addressmaps
24729 for certain incoming socks addresses -- for sites that break when
24730 your exit keeps changing (based on patch by Mike Perry).
24731 - Redo the client-side dns cache so it's just an addressmap too.
24732 - Notice when our IP changes, and reset stats/uptime/reachability.
24733 - When an application is using socks5, give him the whole variety of
24734 potential socks5 responses (connect refused, host unreachable, etc),
24735 rather than just "success" or "failure".
24736 - A more sane version numbering system. See
24737 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
24738 - New contributed script "exitlist": a simple python script to
24739 parse directories and find Tor nodes that exit to listed
24741 - New contributed script "privoxy-tor-toggle" to toggle whether
24742 Privoxy uses Tor. Seems to be configured for Debian by default.
24743 - Report HTTP reasons to client when getting a response from directory
24744 servers -- so you can actually know what went wrong.
24745 - New config option MaxAdvertisedBandwidth which lets you advertise
24746 a low bandwidthrate (to not attract as many circuits) while still
24747 allowing a higher bandwidthrate in reality.
24749 o Robustness/stability fixes:
24750 - Make Tor use Niels Provos's libevent instead of its current
24751 poll-but-sometimes-select mess. This will let us use faster async
24752 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
24754 - pthread support now too. This was forced because when we forked,
24755 we ended up wasting a lot of duplicate ram over time. Also switch
24756 to foo_r versions of some library calls to allow reentry and
24758 - Better handling for heterogeneous / unreliable nodes:
24759 - Annotate circuits w/ whether they aim to contain high uptime nodes
24760 and/or high capacity nodes. When building circuits, choose
24762 - This means that every single node in an intro rend circuit,
24763 not just the last one, will have a minimum uptime.
24764 - New config option LongLivedPorts to indicate application streams
24765 that will want high uptime circuits.
24766 - Servers reset uptime when a dir fetch entirely fails. This
24767 hopefully reflects stability of the server's network connectivity.
24768 - If somebody starts his tor server in Jan 2004 and then fixes his
24769 clock, don't make his published uptime be a year.
24770 - Reset published uptime when you wake up from hibernation.
24771 - Introduce a notion of 'internal' circs, which are chosen without
24772 regard to the exit policy of the last hop. Intro and rendezvous
24773 circs must be internal circs, to avoid leaking information. Resolve
24774 and connect streams can use internal circs if they want.
24775 - New circuit pooling algorithm: make sure to have enough circs around
24776 to satisfy any predicted ports, and also make sure to have 2 internal
24777 circs around if we've required internal circs lately (and with high
24778 uptime if we've seen that lately too).
24779 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
24780 which describes how often we retry making new circuits if current
24781 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
24782 how long we're willing to make use of an already-dirty circuit.
24783 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
24784 circ as necessary, if there are any completed ones lying around
24785 when we try to launch one.
24786 - Make hidden services try to establish a rendezvous for 30 seconds,
24787 rather than for n (where n=3) attempts to build a circuit.
24788 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
24789 "ShutdownWaitLength".
24790 - Try to be more zealous about calling connection_edge_end when
24791 things go bad with edge conns in connection.c.
24792 - Revise tor-spec to add more/better stream end reasons.
24793 - Revise all calls to connection_edge_end to avoid sending "misc",
24794 and to take errno into account where possible.
24797 - Fix a race condition that can trigger an assert, when we have a
24798 pending create cell and an OR connection fails right then.
24799 - Fix several double-mark-for-close bugs, e.g. where we were finding
24800 a conn for a cell even if that conn is already marked for close.
24801 - Make sequence of log messages when starting on win32 with no config
24802 file more reasonable.
24803 - When choosing an exit node for a new non-internal circ, don't take
24804 into account whether it'll be useful for any pending x.onion
24805 addresses -- it won't.
24806 - Turn addr_policy_compare from a tristate to a quadstate; this should
24807 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
24808 for google.com" problem.
24809 - Make "platform" string in descriptor more accurate for Win32 servers,
24810 so it's not just "unknown platform".
24811 - Fix an edge case in parsing config options (thanks weasel).
24812 If they say "--" on the commandline, it's not an option.
24813 - Reject odd-looking addresses at the client (e.g. addresses that
24814 contain a colon), rather than having the server drop them because
24816 - tor-resolve requests were ignoring .exit if there was a working circuit
24817 they could use instead.
24818 - REUSEADDR on normal platforms means you can rebind to the port
24819 right after somebody else has let it go. But REUSEADDR on win32
24820 means to let you bind to the port _even when somebody else
24821 already has it bound_! So, don't do that on Win32.
24822 - Change version parsing logic: a version is "obsolete" if it is not
24823 recommended and (1) there is a newer recommended version in the
24824 same series, or (2) there are no recommended versions in the same
24825 series, but there are some recommended versions in a newer series.
24826 A version is "new" if it is newer than any recommended version in
24828 - Stop most cases of hanging up on a socks connection without sending
24832 - Require BandwidthRate to be at least 20kB/s for servers.
24833 - When a dirserver causes you to give a warn, mention which dirserver
24835 - New config option DirAllowPrivateAddresses for authdirservers.
24836 Now by default they refuse router descriptors that have non-IP or
24837 private-IP addresses.
24838 - Stop publishing socksport in the directory, since it's not
24839 actually meant to be public. For compatibility, publish a 0 there
24841 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
24842 smart" value, that is low for servers and high for clients.
24843 - If our clock jumps forward by 100 seconds or more, assume something
24844 has gone wrong with our network and abandon all not-yet-used circs.
24845 - Warn when exit policy implicitly allows local addresses.
24846 - If we get an incredibly skewed timestamp from a dirserver mirror
24847 that isn't a verified OR, don't warn -- it's probably him that's
24849 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
24850 cookies to disk and doesn't log each web request to disk. (Thanks
24851 to Brett Carrington for pointing this out.)
24852 - When a client asks us for a dir mirror and we don't have one,
24853 launch an attempt to get a fresh one.
24854 - If we're hibernating and we get a SIGINT, exit immediately.
24855 - Add --with-dmalloc ./configure option, to track memory leaks.
24856 - And try to free all memory on closing, so we can detect what
24858 - Cache local dns resolves correctly even when they're .exit
24860 - Give a better warning when some other server advertises an
24861 ORPort that is actually an apache running ssl.
24862 - Add "opt hibernating 1" to server descriptor to make it clearer
24863 whether the server is hibernating.
24866 Changes in version 0.0.9.6 - 2005-03-24
24867 o Bugfixes on 0.0.9.x (crashes and asserts):
24868 - Add new end stream reasons to maintainance branch. Fix bug where
24869 reason (8) could trigger an assert. Prevent bug from recurring.
24870 - Apparently win32 stat wants paths to not end with a slash.
24871 - Fix assert triggers in assert_cpath_layer_ok(), where we were
24872 blowing away the circuit that conn->cpath_layer points to, then
24873 checking to see if the circ is well-formed. Backport check to make
24874 sure we dont use the cpath on a closed connection.
24875 - Prevent circuit_resume_edge_reading_helper() from trying to package
24876 inbufs for marked-for-close streams.
24877 - Don't crash on hup if your options->address has become unresolvable.
24878 - Some systems (like OS X) sometimes accept() a connection and tell
24879 you the remote host is 0.0.0.0:0. If this happens, due to some
24880 other mis-features, we get confused; so refuse the conn for now.
24882 o Bugfixes on 0.0.9.x (other):
24883 - Fix harmless but scary "Unrecognized content encoding" warn message.
24884 - Add new stream error reason: TORPROTOCOL reason means "you are not
24885 speaking a version of Tor I understand; say bye-bye to your stream."
24886 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
24887 into the future, now that we are more tolerant of skew. This
24888 resolves a bug where a Tor server would refuse to cache a directory
24889 because all the directories it gets are too far in the future;
24890 yet the Tor server never logs any complaints about clock skew.
24891 - Mac packaging magic: make man pages useable, and do not overwrite
24892 existing torrc files.
24893 - Make OS X log happily to /var/log/tor/tor.log
24896 Changes in version 0.0.9.5 - 2005-02-22
24897 o Bugfixes on 0.0.9.x:
24898 - Fix an assert race at exit nodes when resolve requests fail.
24899 - Stop picking unverified dir mirrors--it only leads to misery.
24900 - Patch from Matt Edman to make NT services work better. Service
24901 support is still not compiled into the executable by default.
24902 - Patch from Dmitri Bely so the Tor service runs better under
24903 the win32 SYSTEM account.
24904 - Make tor-resolve actually work (?) on Win32.
24905 - Fix a sign bug when getrlimit claims to have 4+ billion
24906 file descriptors available.
24907 - Stop refusing to start when bandwidthburst == bandwidthrate.
24908 - When create cells have been on the onion queue more than five
24909 seconds, just send back a destroy and take them off the list.
24912 Changes in version 0.0.9.4 - 2005-02-03
24913 o Bugfixes on 0.0.9:
24914 - Fix an assert bug that took down most of our servers: when
24915 a server claims to have 1 GB of bandwidthburst, don't
24917 - Don't crash as badly if we have spawned the max allowed number
24918 of dnsworkers, or we're out of file descriptors.
24919 - Block more file-sharing ports in the default exit policy.
24920 - MaxConn is now automatically set to the hard limit of max
24921 file descriptors we're allowed (ulimit -n), minus a few for
24923 - Give a clearer message when servers need to raise their
24924 ulimit -n when they start running out of file descriptors.
24925 - SGI Compatibility patches from Jan Schaumann.
24926 - Tolerate a corrupt cached directory better.
24927 - When a dirserver hasn't approved your server, list which one.
24928 - Go into soft hibernation after 95% of the bandwidth is used,
24929 not 99%. This is especially important for daily hibernators who
24930 have a small accounting max. Hopefully it will result in fewer
24931 cut connections when the hard hibernation starts.
24932 - Load-balance better when using servers that claim more than
24933 800kB/s of capacity.
24934 - Make NT services work (experimental, only used if compiled in).
24937 Changes in version 0.0.9.3 - 2005-01-21
24938 o Bugfixes on 0.0.9:
24939 - Backport the cpu use fixes from main branch, so busy servers won't
24940 need as much processor time.
24941 - Work better when we go offline and then come back, or when we
24942 run Tor at boot before the network is up. We do this by
24943 optimistically trying to fetch a new directory whenever an
24944 application request comes in and we think we're offline -- the
24945 human is hopefully a good measure of when the network is back.
24946 - Backport some minimal hidserv bugfixes: keep rend circuits open as
24947 long as you keep using them; actually publish hidserv descriptors
24948 shortly after they change, rather than waiting 20-40 minutes.
24949 - Enable Mac startup script by default.
24950 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
24951 - When you update AllowUnverifiedNodes or FirewallPorts via the
24952 controller's setconf feature, we were always appending, never
24954 - When you update HiddenServiceDir via setconf, it was screwing up
24955 the order of reading the lines, making it fail.
24956 - Do not rewrite a cached directory back to the cache; otherwise we
24957 will think it is recent and not fetch a newer one on startup.
24958 - Workaround for webservers that lie about Content-Encoding: Tor
24959 now tries to autodetect compressed directories and compression
24960 itself. This lets us Proxypass dir fetches through apache.
24963 Changes in version 0.0.9.2 - 2005-01-04
24964 o Bugfixes on 0.0.9 (crashes and asserts):
24965 - Fix an assert on startup when the disk is full and you're logging
24967 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
24968 style address, then we'd crash.
24969 - Fix an assert trigger when the running-routers string we get from
24970 a dirserver is broken.
24971 - Make worker threads start and run on win32. Now win32 servers
24973 - Bandaid (not actually fix, but now it doesn't crash) an assert
24974 where the dns worker dies mysteriously and the main Tor process
24975 doesn't remember anything about the address it was resolving.
24977 o Bugfixes on 0.0.9 (Win32):
24978 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
24979 name out of the warning/assert messages.
24980 - Fix a superficial "unhandled error on read" bug on win32.
24981 - The win32 installer no longer requires a click-through for our
24982 license, since our Free Software license grants rights but does not
24984 - Win32: When connecting to a dirserver fails, try another one
24985 immediately. (This was already working for non-win32 Tors.)
24986 - Stop trying to parse $HOME on win32 when hunting for default
24988 - Make tor-resolve.c work on win32 by calling network_init().
24990 o Bugfixes on 0.0.9 (other):
24991 - Make 0.0.9.x build on Solaris again.
24992 - Due to a fencepost error, we were blowing away the \n when reporting
24993 confvalue items in the controller. So asking for multiple config
24994 values at once couldn't work.
24995 - When listing circuits that are pending on an opening OR connection,
24996 if we're an OR we were listing circuits that *end* at us as
24997 being pending on every listener, dns/cpu worker, etc. Stop that.
24998 - Dirservers were failing to create 'running-routers' or 'directory'
24999 strings if we had more than some threshold of routers. Fix them so
25000 they can handle any number of routers.
25001 - Fix a superficial "Duplicate mark for close" bug.
25002 - Stop checking for clock skew for OR connections, even for servers.
25003 - Fix a fencepost error that was chopping off the last letter of any
25004 nickname that is the maximum allowed nickname length.
25005 - Update URLs in log messages so they point to the new website.
25006 - Fix a potential problem in mangling server private keys while
25007 writing to disk (not triggered yet, as far as we know).
25008 - Include the licenses for other free software we include in Tor,
25009 now that we're shipping binary distributions more regularly.
25012 Changes in version 0.0.9.1 - 2004-12-15
25013 o Bugfixes on 0.0.9:
25014 - Make hibernation actually work.
25015 - Make HashedControlPassword config option work.
25016 - When we're reporting event circuit status to a controller,
25017 don't use the stream status code.
25020 Changes in version 0.0.9 - 2004-12-12
25022 - Clean up manpage and torrc.sample file.
25023 - Clean up severities and text of log warnings.
25025 - Make servers trigger an assert when they enter hibernation.
25028 Changes in version 0.0.9rc7 - 2004-12-08
25029 o Bugfixes on 0.0.9rc:
25030 - Fix a stack-trashing crash when an exit node begins hibernating.
25031 - Avoid looking at unallocated memory while considering which
25032 ports we need to build circuits to cover.
25033 - Stop a sigpipe: when an 'end' cell races with eof from the app,
25034 we shouldn't hold-open-until-flush if the eof arrived first.
25035 - Fix a bug with init_cookie_authentication() in the controller.
25036 - When recommending new-format log lines, if the upper bound is
25037 LOG_ERR, leave it implicit.
25039 o Bugfixes on 0.0.8.1:
25040 - Fix a whole slew of memory leaks.
25041 - Fix isspace() and friends so they still make Solaris happy
25042 but also so they don't trigger asserts on win32.
25043 - Fix parse_iso_time on platforms without strptime (eg win32).
25044 - win32: tolerate extra "readable" events better.
25045 - win32: when being multithreaded, leave parent fdarray open.
25046 - Make unit tests work on win32.
25049 Changes in version 0.0.9rc6 - 2004-12-06
25050 o Bugfixes on 0.0.9pre:
25051 - Clean up some more integer underflow opportunities (not exploitable
25053 - While hibernating, hup should not regrow our listeners.
25054 - Send an end to the streams we close when we hibernate, rather
25055 than just chopping them off.
25056 - React to eof immediately on non-open edge connections.
25058 o Bugfixes on 0.0.8.1:
25059 - Calculate timeout for waiting for a connected cell from the time
25060 we sent the begin cell, not from the time the stream started. If
25061 it took a long time to establish the circuit, we would time out
25062 right after sending the begin cell.
25063 - Fix router_compare_addr_to_addr_policy: it was not treating a port
25064 of * as always matching, so we were picking reject *:* nodes as
25065 exit nodes too. Oops.
25068 - New circuit building strategy: keep a list of ports that we've
25069 used in the past 6 hours, and always try to have 2 circuits open
25070 or on the way that will handle each such port. Seed us with port
25071 80 so web users won't complain that Tor is "slow to start up".
25072 - Make kill -USR1 dump more useful stats about circuits.
25073 - When warning about retrying or giving up, print the address, so
25074 the user knows which one it's talking about.
25075 - If you haven't used a clean circuit in an hour, throw it away,
25076 just to be on the safe side. (This means after 6 hours a totally
25077 unused Tor client will have no circuits open.)
25080 Changes in version 0.0.9rc5 - 2004-12-01
25081 o Bugfixes on 0.0.8.1:
25082 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
25083 - Let resolve conns retry/expire also, rather than sticking around
25085 - If we are using select, make sure we stay within FD_SETSIZE.
25087 o Bugfixes on 0.0.9pre:
25088 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
25089 but doesn't seem to be currently; thanks to Ilja van Sprundel for
25091 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
25092 instead. Impose minima and maxima for all *Period options; impose
25093 even tighter maxima for fetching if we are a caching dirserver.
25094 Clip rather than rejecting.
25095 - Fetch cached running-routers from servers that serve it (that is,
25096 authdirservers and servers running 0.0.9rc5-cvs or later.)
25099 - Accept *:706 (silc) in default exit policy.
25100 - Implement new versioning format for post 0.1.
25101 - Support "foo.nickname.exit" addresses, to let Alice request the
25102 address "foo" as viewed by exit node "nickname". Based on a patch
25104 - Make tor --version --version dump the cvs Id of every file.
25107 Changes in version 0.0.9rc4 - 2004-11-28
25108 o Bugfixes on 0.0.8.1:
25109 - Make windows sockets actually non-blocking (oops), and handle
25110 win32 socket errors better.
25112 o Bugfixes on 0.0.9rc1:
25113 - Actually catch the -USR2 signal.
25116 Changes in version 0.0.9rc3 - 2004-11-25
25117 o Bugfixes on 0.0.8.1:
25118 - Flush the log file descriptor after we print "Tor opening log file",
25119 so we don't see those messages days later.
25121 o Bugfixes on 0.0.9rc1:
25122 - Make tor-resolve work again.
25123 - Avoid infinite loop in tor-resolve if tor hangs up on it.
25124 - Fix an assert trigger for clients/servers handling resolves.
25127 Changes in version 0.0.9rc2 - 2004-11-24
25128 o Bugfixes on 0.0.9rc1:
25129 - I broke socks5 support while fixing the eof bug.
25130 - Allow unitless bandwidths and intervals; they default to bytes
25132 - New servers don't start out hibernating; they are active until
25133 they run out of bytes, so they have a better estimate of how
25134 long it takes, and so their operators can know they're working.
25137 Changes in version 0.0.9rc1 - 2004-11-23
25138 o Bugfixes on 0.0.8.1:
25139 - Finally fix a bug that's been plaguing us for a year:
25140 With high load, circuit package window was reaching 0. Whenever
25141 we got a circuit-level sendme, we were reading a lot on each
25142 socket, but only writing out a bit. So we would eventually reach
25143 eof. This would be noticed and acted on even when there were still
25144 bytes sitting in the inbuf.
25145 - When poll() is interrupted, we shouldn't believe the revents values.
25147 o Bugfixes on 0.0.9pre6:
25148 - Fix hibernate bug that caused pre6 to be broken.
25149 - Don't keep rephist info for routers that haven't had activity for
25150 24 hours. (This matters now that clients have keys, since we track
25152 - Never call close_temp_logs while validating log options.
25153 - Fix backslash-escaping on tor.sh.in and torctl.in.
25156 - Implement weekly/monthly/daily accounting: now you specify your
25157 hibernation properties by
25158 AccountingMax N bytes|KB|MB|GB|TB
25159 AccountingStart day|week|month [day] HH:MM
25160 Defaults to "month 1 0:00".
25161 - Let bandwidth and interval config options be specified as 5 bytes,
25162 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
25163 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
25164 get back to normal.)
25165 - If your requested entry or exit node has advertised bandwidth 0,
25167 - Be more greedy about filling up relay cells -- we try reading again
25168 once we've processed the stuff we read, in case enough has arrived
25169 to fill the last cell completely.
25170 - Apply NT service patch from Osamu Fujino. Still needs more work.
25173 Changes in version 0.0.9pre6 - 2004-11-15
25174 o Bugfixes on 0.0.8.1:
25175 - Fix assert failure on malformed socks4a requests.
25176 - Use identity comparison, not nickname comparison, to choose which
25177 half of circuit-ID-space each side gets to use. This is needed
25178 because sometimes we think of a router as a nickname, and sometimes
25179 as a hex ID, and we can't predict what the other side will do.
25180 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
25181 write() call will fail and we handle it there.
25182 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
25183 and smartlist_len, which are two major profiling offenders.
25185 o Bugfixes on 0.0.9pre5:
25186 - Fix a bug in read_all that was corrupting config files on windows.
25187 - When we're raising the max number of open file descriptors to
25188 'unlimited', don't log that we just raised it to '-1'.
25189 - Include event code with events, as required by control-spec.txt.
25190 - Don't give a fingerprint when clients do --list-fingerprint:
25191 it's misleading, because it will never be the same again.
25192 - Stop using strlcpy in tor_strndup, since it was slowing us
25194 - Remove warn on startup about missing cached-directory file.
25195 - Make kill -USR1 work again.
25196 - Hibernate if we start tor during the "wait for wakeup-time" phase
25197 of an accounting interval. Log our hibernation plans better.
25198 - Authoritative dirservers now also cache their directory, so they
25199 have it on start-up.
25202 - Fetch running-routers; cache running-routers; compress
25203 running-routers; serve compressed running-routers.z
25204 - Add NSI installer script contributed by J Doe.
25205 - Commit VC6 and VC7 workspace/project files.
25206 - Commit a tor.spec for making RPM files, with help from jbash.
25207 - Add contrib/torctl.in contributed by Glenn Fink.
25208 - Implement the control-spec's SAVECONF command, to write your
25209 configuration to torrc.
25210 - Get cookie authentication for the controller closer to working.
25211 - Include control-spec.txt in the tarball.
25212 - When set_conf changes our server descriptor, upload a new copy.
25213 But don't upload it too often if there are frequent changes.
25214 - Document authentication config in man page, and document signals
25216 - Clean up confusing parts of man page and torrc.sample.
25217 - Make expand_filename handle ~ and ~username.
25218 - Use autoconf to enable largefile support where necessary. Use
25219 ftello where available, since ftell can fail at 2GB.
25220 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
25221 log more informatively.
25222 - Give a slightly more useful output for "tor -h".
25223 - Refuse application socks connections to port 0.
25224 - Check clock skew for verified servers, but allow unverified
25225 servers and clients to have any clock skew.
25226 - Break DirFetchPostPeriod into:
25227 - DirFetchPeriod for fetching full directory,
25228 - StatusFetchPeriod for fetching running-routers,
25229 - DirPostPeriod for posting server descriptor,
25230 - RendPostPeriod for posting hidden service descriptors.
25231 - Make sure the hidden service descriptors are at a random offset
25232 from each other, to hinder linkability.
25235 Changes in version 0.0.9pre5 - 2004-11-09
25236 o Bugfixes on 0.0.9pre4:
25237 - Fix a seg fault in unit tests (doesn't affect main program).
25238 - Fix an assert bug where a hidden service provider would fail if
25239 the first hop of his rendezvous circuit was down.
25240 - Hidden service operators now correctly handle version 1 style
25241 INTRODUCE1 cells (nobody generates them still, so not a critical
25243 - If do_hup fails, actually notice.
25244 - Handle more errnos from accept() without closing the listener.
25245 Some OpenBSD machines were closing their listeners because
25246 they ran out of file descriptors.
25247 - Send resolve cells to exit routers that are running a new
25248 enough version of the resolve code to work right.
25249 - Better handling of winsock includes on non-MSV win32 compilers.
25250 - Some people had wrapped their tor client/server in a script
25251 that would restart it whenever it died. This did not play well
25252 with our "shut down if your version is obsolete" code. Now people
25253 don't fetch a new directory if their local cached version is
25255 - Make our autogen.sh work on ksh as well as bash.
25258 - Hibernation: New config option "AccountingMaxKB" lets you
25259 set how many KBytes per month you want to allow your server to
25260 consume. Rather than spreading those bytes out evenly over the
25261 month, we instead hibernate for some of the month and pop up
25262 at a deterministic time, work until the bytes are consumed, then
25263 hibernate again. Config option "MonthlyAccountingStart" lets you
25264 specify which day of the month your billing cycle starts on.
25265 - Control interface: a separate program can now talk to your
25266 client/server over a socket, and get/set config options, receive
25267 notifications of circuits and streams starting/finishing/dying,
25268 bandwidth used, etc. The next step is to get some GUIs working.
25269 Let us know if you want to help out. See doc/control-spec.txt .
25270 - Ship a contrib/tor-control.py as an example script to interact
25271 with the control port.
25272 - "tor --hash-password zzyxz" will output a salted password for
25273 use in authenticating to the control interface.
25274 - New log format in config:
25275 "Log minsev[-maxsev] stdout|stderr|syslog" or
25276 "Log minsev[-maxsev] file /var/foo"
25279 - DirPolicy config option, to let people reject incoming addresses
25280 from their dirserver.
25281 - "tor --list-fingerprint" will list your identity key fingerprint
25283 - Add "pass" target for RedirectExit, to make it easier to break
25284 out of a sequence of RedirectExit rules.
25285 - Clients now generate a TLS cert too, in preparation for having
25286 them act more like real nodes.
25287 - Ship src/win32/ in the tarball, so people can use it to build.
25288 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
25290 - New "router-status" line in directory, to better bind each verified
25291 nickname to its identity key.
25292 - Deprecate unofficial config option abbreviations, and abbreviations
25293 not on the command line.
25294 - Add a pure-C tor-resolve implementation.
25295 - Use getrlimit and friends to ensure we can reach MaxConn (currently
25296 1024) file descriptors.
25298 o Code security improvements, inspired by Ilja:
25299 - Replace sprintf with snprintf. (I think they were all safe, but
25301 - Replace strcpy/strncpy with strlcpy in more places.
25302 - Avoid strcat; use snprintf or strlcat instead.
25303 - snprintf wrapper with consistent (though not C99) overflow behavior.
25306 Changes in version 0.0.9pre4 - 2004-10-17
25307 o Bugfixes on 0.0.9pre3:
25308 - If the server doesn't specify an exit policy, use the real default
25309 exit policy, not reject *:*.
25310 - Ignore fascistfirewall when uploading/downloading hidden service
25311 descriptors, since we go through Tor for those; and when using
25312 an HttpProxy, since we assume it can reach them all.
25313 - When looking for an authoritative dirserver, use only the ones
25314 configured at boot. Don't bother looking in the directory.
25315 - The rest of the fix for get_default_conf_file() on older win32.
25316 - Make 'Routerfile' config option obsolete.
25319 - New 'MyFamily nick1,...' config option for a server to
25320 specify other servers that shouldn't be used in the same circuit
25321 with it. Only believed if nick1 also specifies us.
25322 - New 'NodeFamily nick1,nick2,...' config option for a client to
25323 specify nodes that it doesn't want to use in the same circuit.
25324 - New 'Redirectexit pattern address:port' config option for a
25325 server to redirect exit connections, e.g. to a local squid.
25328 Changes in version 0.0.9pre3 - 2004-10-13
25329 o Bugfixes on 0.0.8.1:
25330 - Better torrc example lines for dirbindaddress and orbindaddress.
25331 - Improved bounds checking on parsed ints (e.g. config options and
25332 the ones we find in directories.)
25333 - Better handling of size_t vs int, so we're more robust on 64
25335 - Fix the rest of the bug where a newly started OR would appear
25336 as unverified even after we've added his fingerprint and hupped
25338 - Fix a bug from 0.0.7: when read() failed on a stream, we would
25339 close it without sending back an end. So 'connection refused'
25340 would simply be ignored and the user would get no response.
25342 o Bugfixes on 0.0.9pre2:
25343 - Serving the cached-on-disk directory to people is bad. We now
25344 provide no directory until we've fetched a fresh one.
25345 - Workaround for bug on windows where cached-directories get crlf
25347 - Make get_default_conf_file() work on older windows too.
25348 - If we write a *:* exit policy line in the descriptor, don't write
25349 any more exit policy lines.
25352 - Use only 0.0.9pre1 and later servers for resolve cells.
25353 - Make the dirservers file obsolete.
25354 - Include a dir-signing-key token in directories to tell the
25355 parsing entity which key is being used to sign.
25356 - Remove the built-in bulky default dirservers string.
25357 - New config option "Dirserver %s:%d [fingerprint]", which can be
25358 repeated as many times as needed. If no dirservers specified,
25359 default to moria1,moria2,tor26.
25360 - Make moria2 advertise a dirport of 80, so people behind firewalls
25361 will be able to get a directory.
25362 - Http proxy support
25363 - Dirservers translate requests for http://%s:%d/x to /x
25364 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
25365 be routed through this host.
25366 - Clients ask for /tor/x rather than /x for new enough dirservers.
25367 This way we can one day coexist peacefully with apache.
25368 - Clients specify a "Host: %s%d" http header, to be compatible
25369 with more proxies, and so running squid on an exit node can work.
25372 Changes in version 0.0.8.1 - 2004-10-13
25374 - Fix a seg fault that can be triggered remotely for Tor
25375 clients/servers with an open dirport.
25376 - Fix a rare assert trigger, where routerinfos for entries in
25377 our cpath would expire while we're building the path.
25378 - Fix a bug in OutboundBindAddress so it (hopefully) works.
25379 - Fix a rare seg fault for people running hidden services on
25380 intermittent connections.
25381 - Fix a bug in parsing opt keywords with objects.
25382 - Fix a stale pointer assert bug when a stream detaches and
25384 - Fix a string format vulnerability (probably not exploitable)
25385 in reporting stats locally.
25386 - Fix an assert trigger: sometimes launching circuits can fail
25387 immediately, e.g. because too many circuits have failed recently.
25388 - Fix a compile warning on 64 bit platforms.
25391 Changes in version 0.0.9pre2 - 2004-10-03
25393 - Make fetching a cached directory work for 64-bit platforms too.
25394 - Make zlib.h a required header, not an optional header.
25397 Changes in version 0.0.9pre1 - 2004-10-01
25399 - Stop using separate defaults for no-config-file and
25400 empty-config-file. Now you have to explicitly turn off SocksPort,
25401 if you don't want it open.
25402 - Fix a bug in OutboundBindAddress so it (hopefully) works.
25403 - Improve man page to mention more of the 0.0.8 features.
25404 - Fix a rare seg fault for people running hidden services on
25405 intermittent connections.
25406 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
25408 - Fix more dns related bugs: send back resolve_failed and end cells
25409 more reliably when the resolve fails, rather than closing the
25410 circuit and then trying to send the cell. Also attach dummy resolve
25411 connections to a circuit *before* calling dns_resolve(), to fix
25412 a bug where cached answers would never be sent in RESOLVED cells.
25413 - When we run out of disk space, or other log writing error, don't
25414 crash. Just stop logging to that log and continue.
25415 - We were starting to daemonize before we opened our logs, so if
25416 there were any problems opening logs, we would complain to stderr,
25417 which wouldn't work, and then mysteriously exit.
25418 - Fix a rare bug where sometimes a verified OR would connect to us
25419 before he'd uploaded his descriptor, which would cause us to
25420 assign conn->nickname as though he's unverified. Now we look through
25421 the fingerprint list to see if he's there.
25422 - Fix a rare assert trigger, where routerinfos for entries in
25423 our cpath would expire while we're building the path.
25426 - Clients can ask dirservers for /dir.z to get a compressed version
25427 of the directory. Only works for servers running 0.0.9, of course.
25428 - Make clients cache directories and use them to seed their router
25429 lists at startup. This means clients have a datadir again.
25430 - Configuration infrastructure support for warning on obsolete
25432 - Respond to content-encoding headers by trying to uncompress as
25434 - Reply with a deflated directory when a client asks for "dir.z".
25435 We could use allow-encodings instead, but allow-encodings isn't
25436 specified in HTTP 1.0.
25437 - Raise the max dns workers from 50 to 100.
25438 - Discourage people from setting their dirfetchpostperiod more often
25439 than once per minute.
25440 - Protect dirservers from overzealous descriptor uploading -- wait
25441 10 seconds after directory gets dirty, before regenerating.
25444 Changes in version 0.0.8 - 2004-08-25
25445 o Port it to SunOS 5.9 / Athena
25448 Changes in version 0.0.8rc2 - 2004-08-20
25449 o Make it compile on cygwin again.
25450 o When picking unverified routers, skip those with low uptime and/or
25451 low bandwidth, depending on what properties you care about.
25454 Changes in version 0.0.8rc1 - 2004-08-18
25455 o Changes from 0.0.7.3:
25457 - Fix assert triggers: if the other side returns an address 0.0.0.0,
25458 don't put it into the client dns cache.
25459 - If a begin failed due to exit policy, but we believe the IP address
25460 should have been allowed, switch that router to exitpolicy reject *:*
25461 until we get our next directory.
25463 - Clients choose nodes proportional to advertised bandwidth.
25464 - Avoid using nodes with low uptime as introduction points.
25465 - Handle servers with dynamic IP addresses: don't replace
25466 options->Address with the resolved one at startup, and
25467 detect our address right before we make a routerinfo each time.
25468 - 'FascistFirewall' option to pick dirservers and ORs on specific
25469 ports; plus 'FirewallPorts' config option to tell FascistFirewall
25470 which ports are open. (Defaults to 80,443)
25471 - Be more aggressive about trying to make circuits when the network
25472 has changed (e.g. when you unsuspend your laptop).
25473 - Check for time skew on http headers; report date in response to
25475 - If the entrynode config line has only one node, don't pick it as
25477 - Add strict{entry|exit}nodes config options. If set to 1, then
25478 we refuse to build circuits that don't include the specified entry
25480 - OutboundBindAddress config option, to bind to a specific
25481 IP address for outgoing connect()s.
25482 - End truncated log entries (e.g. directories) with "[truncated]".
25484 o Patches to 0.0.8preX:
25486 - Patches to compile and run on win32 again (maybe)?
25487 - Fix crash when looking for ~/.torrc with no $HOME set.
25488 - Fix a race bug in the unit tests.
25489 - Handle verified/unverified name collisions better when new
25490 routerinfo's arrive in a directory.
25491 - Sometimes routers were getting entered into the stats before
25492 we'd assigned their identity_digest. Oops.
25493 - Only pick and establish intro points after we've gotten a
25496 - AllowUnverifiedNodes config option to let circuits choose no-name
25497 routers in entry,middle,exit,introduction,rendezvous positions.
25498 Allow middle and rendezvous positions by default.
25499 - Add a man page for tor-resolve.
25502 Changes in version 0.0.7.3 - 2004-08-12
25503 o Stop dnsworkers from triggering an assert failure when you
25504 ask them to resolve the host "".
25507 Changes in version 0.0.8pre3 - 2004-08-09
25508 o Changes from 0.0.7.2:
25509 - Allow multiple ORs with same nickname in routerlist -- now when
25510 people give us one identity key for a nickname, then later
25511 another, we don't constantly complain until the first expires.
25512 - Remember used bandwidth (both in and out), and publish 15-minute
25513 snapshots for the past day into our descriptor.
25514 - You can now fetch $DIRURL/running-routers to get just the
25515 running-routers line, not the whole descriptor list. (But
25516 clients don't use this yet.)
25517 - When people mistakenly use Tor as an http proxy, point them
25518 at the tor-doc.html rather than the INSTALL.
25519 - Remove our mostly unused -- and broken -- hex_encode()
25520 function. Use base16_encode() instead. (Thanks to Timo Lindfors
25521 for pointing out this bug.)
25522 - Rotate onion keys every 12 hours, not every 2 hours, so we have
25523 fewer problems with people using the wrong key.
25524 - Change the default exit policy to reject the default edonkey,
25525 kazaa, gnutella ports.
25526 - Add replace_file() to util.[ch] to handle win32's rename().
25528 o Changes from 0.0.8preX:
25529 - Fix two bugs in saving onion keys to disk when rotating, so
25530 hopefully we'll get fewer people using old onion keys.
25531 - Fix an assert error that was making SocksPolicy not work.
25532 - Be willing to expire routers that have an open dirport -- it's
25533 just the authoritative dirservers we want to not forget.
25534 - Reject tor-resolve requests for .onion addresses early, so we
25535 don't build a whole rendezvous circuit and then fail.
25536 - When you're warning a server that he's unverified, don't cry
25537 wolf unpredictably.
25538 - Fix a race condition: don't try to extend onto a connection
25539 that's still handshaking.
25540 - For servers in clique mode, require the conn to be open before
25541 you'll choose it for your path.
25542 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
25543 end relay cell, etc.
25544 - Measure bandwidth capacity over the last 24 hours, not just 12
25545 - Bugfix: authoritative dirservers were making and signing a new
25546 directory for each client, rather than reusing the cached one.
25549 Changes in version 0.0.8pre2 - 2004-08-04
25550 o Changes from 0.0.7.2:
25552 - Check directory signature _before_ you decide whether you're
25553 you're running an obsolete version and should exit.
25554 - Check directory signature _before_ you parse the running-routers
25555 list to decide who's running or verified.
25556 - Bugfixes and features:
25557 - Check return value of fclose while writing to disk, so we don't
25558 end up with broken files when servers run out of disk space.
25559 - Log a warning if the user uses an unsafe socks variant, so people
25560 are more likely to learn about privoxy or socat.
25561 - Dirservers now include RFC1123-style dates in the HTTP headers,
25562 which one day we will use to better detect clock skew.
25564 o Changes from 0.0.8pre1:
25565 - Make it compile without warnings again on win32.
25566 - Log a warning if you're running an unverified server, to let you
25567 know you might want to get it verified.
25568 - Only pick a default nickname if you plan to be a server.
25571 Changes in version 0.0.8pre1 - 2004-07-23
25573 - Made our unit tests compile again on OpenBSD 3.5, and tor
25574 itself compile again on OpenBSD on a sparc64.
25575 - We were neglecting milliseconds when logging on win32, so
25576 everything appeared to happen at the beginning of each second.
25578 o Protocol changes:
25579 - 'Extend' relay cell payloads now include the digest of the
25580 intended next hop's identity key. Now we can verify that we're
25581 extending to the right router, and also extend to routers we
25582 hadn't heard of before.
25585 - Tor nodes can now act as relays (with an advertised ORPort)
25586 without being manually verified by the dirserver operators.
25587 - Uploaded descriptors of unverified routers are now accepted
25588 by the dirservers, and included in the directory.
25589 - Verified routers are listed by nickname in the running-routers
25590 list; unverified routers are listed as "$<fingerprint>".
25591 - We now use hash-of-identity-key in most places rather than
25592 nickname or addr:port, for improved security/flexibility.
25593 - To avoid Sybil attacks, paths still use only verified servers.
25594 But now we have a chance to play around with hybrid approaches.
25595 - Nodes track bandwidth usage to estimate capacity (not used yet).
25596 - ClientOnly option for nodes that never want to become servers.
25597 - Directory caching.
25598 - "AuthoritativeDir 1" option for the official dirservers.
25599 - Now other nodes (clients and servers) will cache the latest
25600 directory they've pulled down.
25601 - They can enable their DirPort to serve it to others.
25602 - Clients will pull down a directory from any node with an open
25603 DirPort, and check the signature/timestamp correctly.
25604 - Authoritative dirservers now fetch directories from other
25605 authdirservers, to stay better synced.
25606 - Running-routers list tells who's down also, along with noting
25607 if they're verified (listed by nickname) or unverified (listed
25609 - Allow dirservers to serve running-router list separately.
25610 This isn't used yet.
25611 - ORs connect-on-demand to other ORs
25612 - If you get an extend cell to an OR you're not connected to,
25613 connect, handshake, and forward the create cell.
25614 - The authoritative dirservers stay connected to everybody,
25615 and everybody stays connected to 0.0.7 servers, but otherwise
25616 clients/servers expire unused connections after 5 minutes.
25617 - When servers get a sigint, they delay 30 seconds (refusing new
25618 connections) then exit. A second sigint causes immediate exit.
25619 - File and name management:
25620 - Look for .torrc if no CONFDIR "torrc" is found.
25621 - If no datadir is defined, then choose, make, and secure ~/.tor
25623 - If torrc not found, exitpolicy reject *:*.
25624 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
25625 - If no nickname is defined, derive default from hostname.
25626 - Rename secret key files, e.g. identity.key -> secret_id_key,
25627 to discourage people from mailing their identity key to tor-ops.
25628 - Refuse to build a circuit before the directory has arrived --
25629 it won't work anyway, since you won't know the right onion keys
25631 - Try other dirservers immediately if the one you try is down. This
25632 should tolerate down dirservers better now.
25633 - Parse tor version numbers so we can do an is-newer-than check
25634 rather than an is-in-the-list check.
25635 - New socks command 'resolve', to let us shim gethostbyname()
25637 - A 'tor_resolve' script to access the socks resolve functionality.
25638 - A new socks-extensions.txt doc file to describe our
25639 interpretation and extensions to the socks protocols.
25640 - Add a ContactInfo option, which gets published in descriptor.
25641 - Publish OR uptime in descriptor (and thus in directory) too.
25642 - Write tor version at the top of each log file
25643 - New docs in the tarball:
25645 - Document that you should proxy your SSL traffic too.
25648 Changes in version 0.0.7.2 - 2004-07-07
25649 o A better fix for the 0.0.0.0 problem, that will hopefully
25650 eliminate the remaining related assertion failures.
25653 Changes in version 0.0.7.1 - 2004-07-04
25654 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
25655 since internally we use 0.0.0.0 to signify "not yet resolved".
25658 Changes in version 0.0.7 - 2004-06-07
25659 o Updated the man page to reflect the new features.
25662 Changes in version 0.0.7rc2 - 2004-06-06
25663 o Changes from 0.0.7rc1:
25664 - Make it build on Win32 again.
25665 o Changes from 0.0.6.2:
25666 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
25670 Changes in version 0.0.7rc1 - 2004-06-02
25672 - On sighup, we were adding another log without removing the first
25673 one. So log messages would get duplicated n times for n sighups.
25674 - Several cases of using a connection after we'd freed it. The
25675 problem was that connections that are pending resolve are in both
25676 the pending_resolve tree, and also the circuit's resolving_streams
25677 list. When you want to remove one, you must remove it from both.
25678 - Fix a double-mark-for-close where an end cell arrived for a
25679 resolving stream, and then the resolve failed.
25680 - Check directory signatures based on name of signer, not on whom
25681 we got the directory from. This will let us cache directories more
25684 - Crank up some of our constants to handle more users.
25687 Changes in version 0.0.7pre1 - 2004-06-02
25688 o Fixes for crashes and other obnoxious bugs:
25689 - Fix an epipe bug: sometimes when directory connections failed
25690 to connect, we would give them a chance to flush before closing
25692 - When we detached from a circuit because of resolvefailed, we
25693 would immediately try the same circuit twice more, and then
25694 give up on the resolve thinking we'd tried three different
25696 - Limit the number of intro circuits we'll attempt to build for a
25697 hidden service per 15-minute period.
25698 - Check recommended-software string *early*, before actually parsing
25699 the directory. Thus we can detect an obsolete version and exit,
25700 even if the new directory format doesn't parse.
25701 o Fixes for security bugs:
25702 - Remember which nodes are dirservers when you startup, and if a
25703 random OR enables his dirport, don't automatically assume he's
25704 a trusted dirserver.
25706 - Directory connections were asking the wrong poll socket to
25707 start writing, and not asking themselves to start writing.
25708 - When we detached from a circuit because we sent a begin but
25709 didn't get a connected, we would use it again the first time;
25710 but after that we would correctly switch to a different one.
25711 - Stop warning when the first onion decrypt attempt fails; they
25712 will sometimes legitimately fail now that we rotate keys.
25713 - Override unaligned-access-ok check when $host_cpu is ia64 or
25714 arm. Apparently they allow it but the kernel whines.
25715 - Dirservers try to reconnect periodically too, in case connections
25717 - Fix some memory leaks in directory servers.
25718 - Allow backslash in Win32 filenames.
25719 - Made Tor build complain-free on FreeBSD, hopefully without
25720 breaking other BSD builds. We'll see.
25722 - Doxygen markup on all functions and global variables.
25723 - Make directory functions update routerlist, not replace it. So
25724 now directory disagreements are not so critical a problem.
25725 - Remove the upper limit on number of descriptors in a dirserver's
25726 directory (not that we were anywhere close).
25727 - Allow multiple logfiles at different severity ranges.
25728 - Allow *BindAddress to specify ":port" rather than setting *Port
25729 separately. Allow multiple instances of each BindAddress config
25730 option, so you can bind to multiple interfaces if you want.
25731 - Allow multiple exit policy lines, which are processed in order.
25732 Now we don't need that huge line with all the commas in it.
25733 - Enable accept/reject policies on SOCKS connections, so you can bind
25734 to 0.0.0.0 but still control who can use your OP.
25737 Changes in version 0.0.6.2 - 2004-05-16
25738 o Our integrity-checking digest was checking only the most recent cell,
25739 not the previous cells like we'd thought.
25740 Thanks to Stefan Mark for finding the flaw!
25743 Changes in version 0.0.6.1 - 2004-05-06
25744 o Fix two bugs in our AES counter-mode implementation (this affected
25745 onion-level stream encryption, but not TLS-level). It turns
25746 out we were doing something much more akin to a 16-character
25747 polyalphabetic cipher. Oops.
25748 Thanks to Stefan Mark for finding the flaw!
25749 o Retire moria3 as a directory server, and add tor26 as a directory
25753 Changes in version 0.0.6 - 2004-05-02
25754 [version bump only]
25757 Changes in version 0.0.6rc4 - 2004-05-01
25758 o Update the built-in dirservers list to use the new directory format
25759 o Fix a rare seg fault: if a node offering a hidden service attempts
25760 to build a circuit to Alice's rendezvous point and fails before it
25761 reaches the last hop, it retries with a different circuit, but
25763 o Handle windows socket errors correctly.
25766 Changes in version 0.0.6rc3 - 2004-04-28
25767 o Don't expire non-general excess circuits (if we had enough
25768 circuits open, we were expiring rendezvous circuits -- even
25769 when they had a stream attached. oops.)
25770 o Fetch randomness from /dev/urandom better (not via fopen/fread)
25771 o Better debugging for tls errors
25772 o Some versions of openssl have an SSL_pending function that erroneously
25773 returns bytes when there is a non-application record pending.
25774 o Set Content-Type on the directory and hidserv descriptor.
25775 o Remove IVs from cipher code, since AES-ctr has none.
25776 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
25777 o We were using an array of length zero in a few places.
25778 o win32's gethostbyname can't resolve an IP to an IP.
25779 o win32's close can't close a socket.
25782 Changes in version 0.0.6rc2 - 2004-04-26
25783 o Fix a bug where we were closing tls connections intermittently.
25784 It turns out openssl keeps its errors around -- so if an error
25785 happens, and you don't ask about it, and then another openssl
25786 operation happens and succeeds, and you ask if there was an error,
25787 it tells you about the first error. Fun fun.
25788 o Fix a bug that's been lurking since 27 may 03 (!)
25789 When passing back a destroy cell, we would use the wrong circ id.
25790 'Mostly harmless', but still worth fixing.
25791 o Since we don't support truncateds much, don't bother sending them;
25792 just close the circ.
25793 o check for <machine/limits.h> so we build on NetBSD again (I hope).
25794 o don't crash if a conn that sent a begin has suddenly lost its circuit
25795 (this was quite rare).
25798 Changes in version 0.0.6rc1 - 2004-04-25
25799 o We now rotate link (tls context) keys and onion keys.
25800 o CREATE cells now include oaep padding, so you can tell
25801 if you decrypted them correctly.
25802 o Add bandwidthburst to server descriptor.
25803 o Directories now say which dirserver signed them.
25804 o Use a tor_assert macro that logs failed assertions too.
25807 Changes in version 0.0.6pre5 - 2004-04-18
25808 o changes from 0.0.6pre4:
25809 - make tor build on broken freebsd 5.2 installs
25810 - fix a failed assert when you try an intro point, get a nack, and try
25811 a second one and it works.
25812 - when alice uses a port that the hidden service doesn't accept,
25813 it now sends back an end cell (denied by exit policy). otherwise
25814 alice would just have to wait to time out.
25815 - fix another rare bug: when we had tried all the intro
25816 points for a hidden service, we fetched the descriptor
25817 again, but we left our introcirc thinking it had already
25818 sent an intro, so it kept waiting for a response...
25819 - bugfix: when you sleep your hidden-service laptop, as soon
25820 as it wakes up it tries to upload a service descriptor, but
25821 socketpair fails for some reason (localhost not up yet?).
25822 now we simply give up on that upload, and we'll try again later.
25823 i'd still like to find the bug though.
25824 - if an intro circ waiting for an ack dies before getting one, then
25826 - we were reusing stale service descriptors and refetching usable
25830 Changes in version 0.0.6pre4 - 2004-04-14
25831 o changes from 0.0.6pre3:
25832 - when bob fails to connect to the rendezvous point, and his
25833 circ didn't fail because of the rendezvous point itself, then
25834 he retries a couple of times
25835 - we expire introduction and rendezvous circs more thoroughly
25836 (sometimes they were hanging around forever)
25837 - we expire unattached rendezvous streams that have been around
25838 too long (they were sticking around forever).
25839 - fix a measly fencepost error that was crashing everybody with
25843 Changes in version 0.0.6pre3 - 2004-04-14
25844 o changes from 0.0.6pre2:
25845 - make hup work again
25846 - fix some memory leaks for dirservers
25847 - allow more skew in rendezvous descriptor timestamps, to help
25848 handle people like blanu who don't know what time it is
25849 - normal circs are 3 hops, but some rend/intro circs are 4, if
25850 the initiator doesn't get to choose the last hop
25851 - send acks for introductions, so alice can know whether to try
25853 - bob publishes intro points more correctly
25854 o changes from 0.0.5:
25855 - fix an assert trigger that's been plaguing us since the days
25856 of 0.0.2prexx (thanks weasel!)
25857 - retry stream correctly when we fail to connect because of
25858 exit-policy-reject (should try another) or can't-resolve-address
25859 (also should try another, because dns on random internet servers
25861 - when we hup a dirserver and we've *removed* a server from the
25862 approved-routers list, now we remove that server from the
25863 in-memory directories too
25866 Changes in version 0.0.6pre2 - 2004-04-08
25867 o We fixed our base32 implementation. Now it works on all architectures.
25870 Changes in version 0.0.6pre1 - 2004-04-08
25872 - Hidden services and rendezvous points are implemented. Go to
25873 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
25874 hidden services. (This only works via a socks4a proxy such as
25875 Privoxy, and currently it's quite slow.)
25878 Changes in version 0.0.5 - 2004-03-30
25879 [version bump only]
25882 Changes in version 0.0.5rc3 - 2004-03-29
25883 o Install torrc as torrc.sample -- we no longer clobber your
25885 o Re-enable recommendedversion checking (we broke it in rc2, oops)
25886 o Add in a 'notice' log level for things the operator should hear
25887 but that aren't warnings
25890 Changes in version 0.0.5rc2 - 2004-03-29
25891 o Hold socks connection open until reply is flushed (if possible)
25892 o Make exit nodes resolve IPs to IPs immediately, rather than asking
25893 the dns farm to do it.
25894 o Fix c99 aliasing warnings in rephist.c
25895 o Don't include server descriptors that are older than 24 hours in the
25897 o Give socks 'reject' replies their whole 15s to attempt to flush,
25898 rather than seeing the 60s timeout and assuming the flush had failed.
25899 o Clean automake droppings from the cvs repository
25902 Changes in version 0.0.5rc1 - 2004-03-28
25903 o Fix mangled-state bug in directory fetching (was causing sigpipes).
25904 o Only build circuits after we've fetched the directory: clients were
25905 using only the directory servers before they'd fetched a directory.
25906 This also means longer startup time; so it goes.
25907 o Fix an assert trigger where an OP would fail to handshake, and we'd
25908 expect it to have a nickname.
25909 o Work around a tsocks bug: do a socks reject when AP connection dies
25910 early, else tsocks goes into an infinite loop.
25913 Changes in version 0.0.4 - 2004-03-26
25914 o When connecting to a dirserver or OR and the network is down,
25918 Changes in version 0.0.3 - 2004-03-26
25919 o Warn and fail if server chose a nickname with illegal characters
25920 o Port to Solaris and Sparc:
25921 - include missing header fcntl.h
25922 - have autoconf find -lsocket -lnsl automatically
25923 - deal with hardware word alignment
25924 - make uname() work (solaris has a different return convention)
25925 - switch from using signal() to sigaction()
25926 o Preliminary work on reputation system:
25927 - Keep statistics on success/fail of connect attempts; they're published
25928 by kill -USR1 currently.
25929 - Add a RunTesting option to try to learn link state by creating test
25930 circuits, even when SocksPort is off.
25931 - Remove unused open circuits when there are too many.
25934 Changes in version 0.0.2 - 2004-03-19
25935 - Include strlcpy and strlcat for safer string ops
25936 - define INADDR_NONE so we compile (but still not run) on solaris
25939 Changes in version 0.0.2pre27 - 2004-03-14
25941 - Allow internal tor networks (we were rejecting internal IPs,
25942 now we allow them if they're set explicitly).
25943 - And fix a few endian issues.
25946 Changes in version 0.0.2pre26 - 2004-03-14
25948 - If a stream times out after 15s without a connected cell, don't
25949 try that circuit again: try a new one.
25950 - Retry streams at most 4 times. Then give up.
25951 - When a dirserver gets a descriptor from an unknown router, it
25952 logs its fingerprint (so the dirserver operator can choose to
25953 accept it even without mail from the server operator).
25954 - Inform unapproved servers when we reject their descriptors.
25955 - Make tor build on Windows again. It works as a client, who knows
25957 - Clearer instructions in the torrc for how to set up a server.
25958 - Be more efficient about reading fd's when our global token bucket
25959 (used for rate limiting) becomes empty.
25961 - Stop asserting that computers always go forward in time. It's
25963 - When we sent a cell (e.g. destroy) and then marked an OR connection
25964 expired, we might close it before finishing a flush if the other
25965 side isn't reading right then.
25966 - Don't allow dirservers to start if they haven't defined
25967 RecommendedVersions
25968 - We were caching transient dns failures. Oops.
25969 - Prevent servers from publishing an internal IP as their address.
25970 - Address a strcat vulnerability in circuit.c
25973 Changes in version 0.0.2pre25 - 2004-03-04
25975 - Put the OR's IP in its router descriptor, not its fqdn. That way
25976 we'll stop being stalled by gethostbyname for nodes with flaky dns,
25979 - If the user typed in an address that didn't resolve, the server
25983 Changes in version 0.0.2pre24 - 2004-03-03
25985 - Fix an assertion failure in dns.c, where we were trying to dequeue
25986 a pending dns resolve even if it wasn't pending
25987 - Fix a spurious socks5 warning about still trying to write after the
25988 connection is finished.
25989 - Hold certain marked_for_close connections open until they're finished
25990 flushing, rather than losing bytes by closing them too early.
25991 - Correctly report the reason for ending a stream
25992 - Remove some duplicate calls to connection_mark_for_close
25993 - Put switch_id and start_daemon earlier in the boot sequence, so it
25994 will actually try to chdir() to options.DataDirectory
25995 - Make 'make test' exit(1) if a test fails; fix some unit tests
25996 - Make tor fail when you use a config option it doesn't know about,
25997 rather than warn and continue.
25998 - Make --version work
25999 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
26002 Changes in version 0.0.2pre23 - 2004-02-29
26004 - Print a statement when the first circ is finished, so the user
26005 knows it's working.
26006 - If a relay cell is unrecognized at the end of the circuit,
26007 send back a destroy. (So attacks to mutate cells are more
26009 - New config option 'excludenodes' to avoid certain nodes for circuits.
26010 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
26011 so you can collect coredumps there.
26013 - Fix a bug in tls flushing where sometimes data got wedged and
26014 didn't flush until more data got sent. Hopefully this bug was
26015 a big factor in the random delays we were seeing.
26016 - Make 'connected' cells include the resolved IP, so the client
26017 dns cache actually gets populated.
26018 - Disallow changing from ORPort=0 to ORPort>0 on hup.
26019 - When we time-out on a stream and detach from the circuit, send an
26020 end cell down it first.
26021 - Only warn about an unknown router (in exitnodes, entrynodes,
26022 excludenodes) after we've fetched a directory.
26025 Changes in version 0.0.2pre22 - 2004-02-26
26027 - Servers publish less revealing uname information in descriptors.
26028 - More memory tracking and assertions, to crash more usefully when
26030 - If the default torrc isn't there, just use some default defaults.
26031 Plus provide an internal dirservers file if they don't have one.
26032 - When the user tries to use Tor as an http proxy, give them an http
26033 501 failure explaining that we're a socks proxy.
26034 - Dump a new router.desc on hup, to help confused people who change
26035 their exit policies and then wonder why router.desc doesn't reflect
26037 - Clean up the generic tor.sh init script that we ship with.
26039 - If the exit stream is pending on the resolve, and a destroy arrives,
26040 then the stream wasn't getting removed from the pending list. I
26041 think this was the one causing recent server crashes.
26042 - Use a more robust poll on OSX 10.3, since their poll is flaky.
26043 - When it couldn't resolve any dirservers, it was useless from then on.
26044 Now it reloads the RouterFile (or default dirservers) if it has no
26046 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
26047 many users don't even *have* a /usr/local/sbin/.
26050 Changes in version 0.0.2pre21 - 2004-02-18
26052 - There's a ChangeLog file that actually reflects the changelog.
26053 - There's a 'torify' wrapper script, with an accompanying
26054 tor-tsocks.conf, that simplifies the process of using tsocks for
26055 tor. It even has a man page.
26056 - The tor binary gets installed to sbin rather than bin now.
26057 - Retry streams where the connected cell hasn't arrived in 15 seconds
26058 - Clean up exit policy handling -- get the default out of the torrc,
26059 so we can update it without forcing each server operator to fix
26061 - Allow imaps and pop3s in default exit policy
26063 - Prevent picking middleman nodes as the last node in the circuit
26066 Changes in version 0.0.2pre20 - 2004-01-30
26068 - We now have a deb package, and it's in debian unstable. Go to
26069 it, apt-getters. :)
26070 - I've split the TotalBandwidth option into BandwidthRate (how many
26071 bytes per second you want to allow, long-term) and
26072 BandwidthBurst (how many bytes you will allow at once before the cap
26073 kicks in). This better token bucket approach lets you, say, set
26074 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
26075 performance while not exceeding your monthly bandwidth quota.
26076 - Push out a tls record's worth of data once you've got it, rather
26077 than waiting until you've read everything waiting to be read. This
26078 may improve performance by pipelining better. We'll see.
26079 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
26080 from failed circuits (if they haven't been connected yet) and attach
26082 - Expire old streams that haven't managed to connect. Some day we'll
26083 have them reattach to new circuits instead.
26086 - Fix several memory leaks that were causing servers to become bloated
26088 - Fix a few very rare assert triggers. A few more remain.
26089 - Setuid to User _before_ complaining about running as root.
26092 Changes in version 0.0.2pre19 - 2004-01-07
26094 - Fix deadlock condition in dns farm. We were telling a child to die by
26095 closing the parent's file descriptor to him. But newer children were
26096 inheriting the open file descriptor from the parent, and since they
26097 weren't closing it, the socket never closed, so the child never read
26098 eof, so he never knew to exit. Similarly, dns workers were holding
26099 open other sockets, leading to all sorts of chaos.
26100 - New cleaner daemon() code for forking and backgrounding.
26101 - If you log to a file, it now prints an entry at the top of the
26102 logfile so you know it's working.
26103 - The onionskin challenge length was 30 bytes longer than necessary.
26104 - Started to patch up the spec so it's not quite so out of date.
26107 Changes in version 0.0.2pre18 - 2004-01-02
26109 - Fix endian issues with the 'integrity' field in the relay header.
26110 - Fix a potential bug where connections in state
26111 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
26114 Changes in version 0.0.2pre17 - 2003-12-30
26116 - Made --debuglogfile (or any second log file, actually) work.
26117 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
26118 adversary could force us into an infinite loop.
26121 - Each onionskin handshake now includes a hash of the computed key,
26122 to prove the server's identity and help perfect forward secrecy.
26123 - Changed cell size from 256 to 512 bytes (working toward compatibility
26125 - Changed cell length to 2 bytes, and moved it to the relay header.
26126 - Implemented end-to-end integrity checking for the payloads of
26128 - Separated streamid from 'recognized' (otherwise circuits will get
26129 messed up when we try to have streams exit from the middle). We
26130 use the integrity-checking to confirm that a cell is addressed to
26132 - Randomize the initial circid and streamid values, so an adversary who
26133 breaks into a node can't learn how many circuits or streams have
26137 Changes in version 0.0.2pre16 - 2003-12-14
26139 - Fixed a bug that made HUP trigger an assert
26140 - Fixed a bug where a circuit that immediately failed wasn't being
26141 counted as a failed circuit in counting retries.
26144 - Now we close the circuit when we get a truncated cell: otherwise we're
26145 open to an anonymity attack where a bad node in the path truncates
26146 the circuit and then we open streams at him.
26147 - Add port ranges to exit policies
26148 - Add a conservative default exit policy
26149 - Warn if you're running tor as root
26150 - on HUP, retry OR connections and close/rebind listeners
26151 - options.EntryNodes: try these nodes first when picking the first node
26152 - options.ExitNodes: if your best choices happen to include any of
26153 your preferred exit nodes, you choose among just those preferred
26155 - options.ExcludedNodes: nodes that are never picked in path building
26158 Changes in version 0.0.2pre15 - 2003-12-03
26159 o Robustness and bugfixes:
26160 - Sometimes clients would cache incorrect DNS resolves, which would
26161 really screw things up.
26162 - An OP that goes offline would slowly leak all its sockets and stop
26164 - A wide variety of bugfixes in exit node selection, exit policy
26165 handling, and processing pending streams when a new circuit is
26167 - Pick nodes for a path only from those the directory says are up
26168 - Choose randomly from all running dirservers, not always the first one
26169 - Increase allowed http header size for directory fetch.
26170 - Stop writing to stderr (if we're daemonized it will be closed).
26171 - Enable -g always, so cores will be more useful to me.
26172 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
26175 - Wrote a man page. It lists commonly used options.
26178 - Change default loglevel to warn.
26179 - Make PidFile default to null rather than littering in your CWD.
26180 - OnionRouter config option is now obsolete. Instead it just checks
26182 - Moved to a single unified torrc file for both clients and servers.
26185 Changes in version 0.0.2pre14 - 2003-11-29
26186 o Robustness and bugfixes:
26187 - Force the admin to make the DataDirectory himself
26188 - to get ownership/permissions right
26189 - so clients no longer make a DataDirectory and then never use it
26190 - fix bug where a client who was offline for 45 minutes would never
26191 pull down a directory again
26192 - fix (or at least hide really well) the dns assert bug that was
26193 causing server crashes
26194 - warnings and improved robustness wrt clockskew for certs
26195 - use the native daemon(3) to daemonize, when available
26196 - exit if bind() fails
26197 - exit if neither socksport nor orport is defined
26198 - include our own tor_timegm (Win32 doesn't have its own)
26199 - bugfix for win32 with lots of connections
26200 - fix minor bias in PRNG
26201 - make dirserver more robust to corrupt cached directory
26204 - Wrote the design document (woo)
26206 o Circuit building and exit policies:
26207 - Circuits no longer try to use nodes that the directory has told them
26209 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
26210 bitcounts (18.0.0.0/8).
26211 - Make AP connections standby for a circuit if no suitable circuit
26212 exists, rather than failing
26213 - Circuits choose exit node based on addr/port, exit policies, and
26214 which AP connections are standing by
26215 - Bump min pathlen from 2 to 3
26216 - Relay end cells have a payload to describe why the stream ended.
26217 - If the stream failed because of exit policy, try again with a new
26219 - Clients have a dns cache to remember resolved addresses.
26220 - Notice more quickly when we have no working circuits
26223 - APPort is now called SocksPort
26224 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
26226 - RecommendedVersions is now a config variable rather than
26227 hardcoded (for dirservers)
26228 - Reloads config on HUP
26229 - Usage info on -h or --help
26230 - If you set User and Group config vars, it'll setu/gid to them.
26233 Changes in version 0.0.2pre13 - 2003-10-19
26234 o General stability:
26235 - SSL_write no longer fails when it returns WANTWRITE and the number
26236 of bytes in the buf has changed by the next SSL_write call.
26237 - Fix segfault fetching directory when network is down
26238 - Fix a variety of minor memory leaks
26239 - Dirservers reload the fingerprints file on HUP, so I don't have
26240 to take down the network when I approve a new router
26241 - Default server config file has explicit Address line to specify fqdn
26244 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
26245 - Make listener connections not ever alloc bufs
26247 o Autoconf improvements:
26248 - don't clobber an external CFLAGS in ./configure
26249 - Make install now works
26250 - create var/lib/tor on make install
26251 - autocreate a tor.sh initscript to help distribs
26252 - autocreate the torrc and sample-server-torrc with correct paths
26254 o Log files and Daemonizing now work:
26255 - If --DebugLogFile is specified, log to it at -l debug
26256 - If --LogFile is specified, use it instead of commandline
26257 - If --RunAsDaemon is set, tor forks and backgrounds on startup