1 Changes in version 0.3.2.7-rc - 2017-12-14
2 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
3 including some that could affect reliability or correctness.
5 This is the first release candidate in the 0.3.2 series. If we find no
6 new bugs or regression here, then the first stable 0.3.2. release will
7 be nearly identical to this.
9 o Major bugfixes (circuit prediction):
10 - Fix circuit prediction logic so that a client doesn't treat a port
11 as being "handled" by a circuit if that circuit already has
12 isolation settings on it. This change should make Tor clients more
13 responsive by improving their chances of having a pre-created
14 circuit ready for use when a request arrives. Fixes bug 18859;
15 bugfix on 0.2.3.3-alpha.
17 o Minor features (logging):
18 - Provide better warnings when the getrandom() syscall fails. Closes
21 o Minor features (portability):
22 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
23 (It doesn't yet work with the sandbox enabled.) Closes
26 o Minor bugfixes (bridge clients, bootstrap):
27 - Retry directory downloads when we get our first bridge descriptor
28 during bootstrap or while reconnecting to the network. Keep
29 retrying every time we get a bridge descriptor, until we have a
30 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
31 - Stop delaying bridge descriptor fetches when we have cached bridge
32 descriptors. Instead, only delay bridge descriptor fetches when we
33 have at least one reachable bridge. Fixes part of bug 24367;
34 bugfix on 0.2.0.3-alpha.
35 - Stop delaying directory fetches when we have cached bridge
36 descriptors. Instead, only delay bridge descriptor fetches when
37 all our bridges are definitely unreachable. Fixes part of bug
38 24367; bugfix on 0.2.0.3-alpha.
40 o Minor bugfixes (compilation):
41 - Fix a signed/unsigned comparison warning introduced by our fix to
42 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
44 o Minor bugfixes (correctness):
45 - Fix several places in our codebase where a C compiler would be
46 likely to eliminate a check, based on assuming that undefined
47 behavior had not happened elsewhere in the code. These cases are
48 usually a sign of redundant checking or dubious arithmetic. Found
49 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
50 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
53 o Minor bugfixes (onion service v3):
54 - Fix a race where an onion service would launch a new intro circuit
55 after closing an old one, but fail to register it before freeing
56 the previously closed circuit. This bug was making the service
57 unable to find the established intro circuit and thus not upload
58 its descriptor, thus making a service unavailable for up to 24
59 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
61 o Minor bugfixes (scheduler, KIST):
62 - Properly set the scheduler state of an unopened channel in the
63 KIST scheduler main loop. This prevents a harmless but annoying
64 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
65 - Avoid a possible integer overflow when computing the available
66 space on the TCP buffer of a channel. This had no security
67 implications; but could make KIST allow too many cells on a
68 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
69 - Downgrade to "info" a harmless warning about the monotonic time
70 moving backwards: This can happen on platform not supporting
71 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
74 Changes in version 0.3.2.6-alpha - 2017-12-01
75 This version of Tor is the latest in the 0.3.2 alpha series. It
76 includes fixes for several important security issues. All Tor users
77 should upgrade to this release, or to one of the other releases coming
80 o Major bugfixes (security):
81 - Fix a denial of service bug where an attacker could use a
82 malformed directory object to cause a Tor instance to pause while
83 OpenSSL would try to read a passphrase from the terminal. (Tor
84 instances run without a terminal, which is the case for most Tor
85 packages, are not impacted.) Fixes bug 24246; bugfix on every
86 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
87 Found by OSS-Fuzz as testcase 6360145429790720.
88 - Fix a denial of service issue where an attacker could crash a
89 directory authority using a malformed router descriptor. Fixes bug
90 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
92 - When checking for replays in the INTRODUCE1 cell data for a
93 (legacy) onion service, correctly detect replays in the RSA-
94 encrypted part of the cell. We were previously checking for
95 replays on the entire cell, but those can be circumvented due to
96 the malleability of Tor's legacy hybrid encryption. This fix helps
97 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
98 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
101 o Major bugfixes (security, onion service v2):
102 - Fix a use-after-free error that could crash v2 Tor onion services
103 when they failed to open circuits while expiring introduction
104 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
105 also tracked as TROVE-2017-013 and CVE-2017-8823.
107 o Major bugfixes (security, relay):
108 - When running as a relay, make sure that we never build a path
109 through ourselves, even in the case where we have somehow lost the
110 version of our descriptor appearing in the consensus. Fixes part
111 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
112 as TROVE-2017-012 and CVE-2017-8822.
113 - When running as a relay, make sure that we never choose ourselves
114 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
115 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
117 o Minor feature (relay statistics):
118 - Change relay bandwidth reporting stats interval from 4 hours to 24
119 hours in order to reduce the efficiency of guard discovery
120 attacks. Fixes ticket 23856.
122 o Minor features (directory authority):
123 - Add an IPv6 address for the "bastet" directory authority. Closes
126 o Minor bugfixes (client):
127 - By default, do not enable storage of client-side DNS values. These
128 values were unused by default previously, but they should not have
129 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
132 Changes in version 0.3.1.9 - 2017-12-01:
133 Tor 0.3.1.9 backports important security and stability fixes from the
134 0.3.2 development series. All Tor users should upgrade to this
135 release, or to another of the releases coming out today.
137 o Major bugfixes (security, backport from 0.3.2.6-alpha):
138 - Fix a denial of service bug where an attacker could use a
139 malformed directory object to cause a Tor instance to pause while
140 OpenSSL would try to read a passphrase from the terminal. (Tor
141 instances run without a terminal, which is the case for most Tor
142 packages, are not impacted.) Fixes bug 24246; bugfix on every
143 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
144 Found by OSS-Fuzz as testcase 6360145429790720.
145 - Fix a denial of service issue where an attacker could crash a
146 directory authority using a malformed router descriptor. Fixes bug
147 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
149 - When checking for replays in the INTRODUCE1 cell data for a
150 (legacy) onion service, correctly detect replays in the RSA-
151 encrypted part of the cell. We were previously checking for
152 replays on the entire cell, but those can be circumvented due to
153 the malleability of Tor's legacy hybrid encryption. This fix helps
154 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
155 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
158 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
159 - Fix a use-after-free error that could crash v2 Tor onion services
160 when they failed to open circuits while expiring introduction
161 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
162 also tracked as TROVE-2017-013 and CVE-2017-8823.
164 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
165 - When running as a relay, make sure that we never build a path
166 through ourselves, even in the case where we have somehow lost the
167 version of our descriptor appearing in the consensus. Fixes part
168 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
169 as TROVE-2017-012 and CVE-2017-8822.
170 - When running as a relay, make sure that we never choose ourselves
171 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
172 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
174 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
175 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
176 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
177 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
178 identifying and finding a workaround to this bug and to Moritz,
179 Arthur Edelstein, and Roger for helping to track it down and
182 o Minor features (bridge):
183 - Bridges now include notice in their descriptors that they are
184 bridges, and notice of their distribution status, based on their
185 publication settings. Implements ticket 18329. For more fine-
186 grained control of how a bridge is distributed, upgrade to 0.3.2.x
189 o Minor features (directory authority, backport from 0.3.2.6-alpha):
190 - Add an IPv6 address for the "bastet" directory authority. Closes
193 o Minor features (geoip):
194 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
197 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
198 - Avoid unnecessary calls to directory_fetches_from_authorities() on
199 relays, to prevent spurious address resolutions and descriptor
200 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
201 bugfix on in 0.2.8.1-alpha.
203 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
204 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
205 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
207 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
208 - When a circuit is marked for close, do not attempt to package any
209 cells for channels on that circuit. Previously, we would detect
210 this condition lower in the call stack, when we noticed that the
211 circuit had no attached channel, and log an annoying message.
212 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
214 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
215 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
216 so it matches dir-spec.txt. Fixes bug 24262; bugfix
219 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
220 - Avoid a crash when transitioning from client mode to bridge mode.
221 Previously, we would launch the worker threads whenever our
222 "public server" mode changed, but not when our "server" mode
223 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
226 Changes in version 0.3.0.13 - 2017-12-01
227 Tor 0.3.0.13 backports important security and stability bugfixes from
228 later Tor releases. All Tor users should upgrade to this release, or
229 to another of the releases coming out today.
231 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
232 2018. If you need a release with long-term support, please stick with
233 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
235 o Major bugfixes (security, backport from 0.3.2.6-alpha):
236 - Fix a denial of service bug where an attacker could use a
237 malformed directory object to cause a Tor instance to pause while
238 OpenSSL would try to read a passphrase from the terminal. (Tor
239 instances run without a terminal, which is the case for most Tor
240 packages, are not impacted.) Fixes bug 24246; bugfix on every
241 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
242 Found by OSS-Fuzz as testcase 6360145429790720.
243 - Fix a denial of service issue where an attacker could crash a
244 directory authority using a malformed router descriptor. Fixes bug
245 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
247 - When checking for replays in the INTRODUCE1 cell data for a
248 (legacy) onion service, correctly detect replays in the RSA-
249 encrypted part of the cell. We were previously checking for
250 replays on the entire cell, but those can be circumvented due to
251 the malleability of Tor's legacy hybrid encryption. This fix helps
252 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
253 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
256 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
257 - Fix a use-after-free error that could crash v2 Tor onion services
258 when they failed to open circuits while expiring introduction
259 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
260 also tracked as TROVE-2017-013 and CVE-2017-8823.
262 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
263 - When running as a relay, make sure that we never build a path
264 through ourselves, even in the case where we have somehow lost the
265 version of our descriptor appearing in the consensus. Fixes part
266 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
267 as TROVE-2017-012 and CVE-2017-8822.
268 - When running as a relay, make sure that we never choose ourselves
269 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
270 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
272 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
273 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
274 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
275 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
276 identifying and finding a workaround to this bug and to Moritz,
277 Arthur Edelstein, and Roger for helping to track it down and
280 o Minor features (security, windows, backport from 0.3.1.1-alpha):
281 - Enable a couple of pieces of Windows hardening: one
282 (HeapEnableTerminationOnCorruption) that has been on-by-default
283 since Windows 8, and unavailable before Windows 7; and one
284 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
285 affect us, but shouldn't do any harm. Closes ticket 21953.
287 o Minor features (bridge, backport from 0.3.1.9):
288 - Bridges now include notice in their descriptors that they are
289 bridges, and notice of their distribution status, based on their
290 publication settings. Implements ticket 18329. For more fine-
291 grained control of how a bridge is distributed, upgrade to 0.3.2.x
294 o Minor features (directory authority, backport from 0.3.2.6-alpha):
295 - Add an IPv6 address for the "bastet" directory authority. Closes
298 o Minor features (geoip):
299 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
302 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
303 - Avoid unnecessary calls to directory_fetches_from_authorities() on
304 relays, to prevent spurious address resolutions and descriptor
305 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
306 bugfix on in 0.2.8.1-alpha.
308 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
309 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
310 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
312 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
313 - When a circuit is marked for close, do not attempt to package any
314 cells for channels on that circuit. Previously, we would detect
315 this condition lower in the call stack, when we noticed that the
316 circuit had no attached channel, and log an annoying message.
317 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
319 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
320 - Avoid a crash when transitioning from client mode to bridge mode.
321 Previously, we would launch the worker threads whenever our
322 "public server" mode changed, but not when our "server" mode
323 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
325 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
326 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
327 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
330 Changes in version 0.2.9.14 - 2017-12-01
331 Tor 0.3.0.13 backports important security and stability bugfixes from
332 later Tor releases. All Tor users should upgrade to this release, or
333 to another of the releases coming out today.
335 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
336 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
337 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
338 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
339 identifying and finding a workaround to this bug and to Moritz,
340 Arthur Edelstein, and Roger for helping to track it down and
343 o Major bugfixes (security, backport from 0.3.2.6-alpha):
344 - Fix a denial of service bug where an attacker could use a
345 malformed directory object to cause a Tor instance to pause while
346 OpenSSL would try to read a passphrase from the terminal. (Tor
347 instances run without a terminal, which is the case for most Tor
348 packages, are not impacted.) Fixes bug 24246; bugfix on every
349 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
350 Found by OSS-Fuzz as testcase 6360145429790720.
351 - Fix a denial of service issue where an attacker could crash a
352 directory authority using a malformed router descriptor. Fixes bug
353 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
355 - When checking for replays in the INTRODUCE1 cell data for a
356 (legacy) onion service, correctly detect replays in the RSA-
357 encrypted part of the cell. We were previously checking for
358 replays on the entire cell, but those can be circumvented due to
359 the malleability of Tor's legacy hybrid encryption. This fix helps
360 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
361 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
364 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
365 - Fix a use-after-free error that could crash v2 Tor onion services
366 when they failed to open circuits while expiring introduction
367 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
368 also tracked as TROVE-2017-013 and CVE-2017-8823.
370 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
371 - When running as a relay, make sure that we never build a path
372 through ourselves, even in the case where we have somehow lost the
373 version of our descriptor appearing in the consensus. Fixes part
374 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
375 as TROVE-2017-012 and CVE-2017-8822.
377 o Minor features (bridge, backport from 0.3.1.9):
378 - Bridges now include notice in their descriptors that they are
379 bridges, and notice of their distribution status, based on their
380 publication settings. Implements ticket 18329. For more fine-
381 grained control of how a bridge is distributed, upgrade to 0.3.2.x
384 o Minor features (directory authority, backport from 0.3.2.6-alpha):
385 - Add an IPv6 address for the "bastet" directory authority. Closes
388 o Minor features (geoip):
389 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
392 o Minor features (security, windows, backport from 0.3.1.1-alpha):
393 - Enable a couple of pieces of Windows hardening: one
394 (HeapEnableTerminationOnCorruption) that has been on-by-default
395 since Windows 8, and unavailable before Windows 7; and one
396 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
397 affect us, but shouldn't do any harm. Closes ticket 21953.
399 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
400 - Avoid unnecessary calls to directory_fetches_from_authorities() on
401 relays, to prevent spurious address resolutions and descriptor
402 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
403 bugfix on in 0.2.8.1-alpha.
405 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
406 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
407 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
409 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
410 - When a circuit is marked for close, do not attempt to package any
411 cells for channels on that circuit. Previously, we would detect
412 this condition lower in the call stack, when we noticed that the
413 circuit had no attached channel, and log an annoying message.
414 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
416 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
417 - Avoid a crash when transitioning from client mode to bridge mode.
418 Previously, we would launch the worker threads whenever our
419 "public server" mode changed, but not when our "server" mode
420 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
422 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
423 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
424 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
427 Changes in version 0.2.8.17 - 2017-12-01
428 Tor 0.2.8.17 backports important security and stability bugfixes from
429 later Tor releases. All Tor users should upgrade to this release, or
430 to another of the releases coming out today.
432 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
433 2018. If you need a release with long-term support, please upgrade with
434 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
436 o Major bugfixes (security, backport from 0.3.2.6-alpha):
437 - Fix a denial of service bug where an attacker could use a
438 malformed directory object to cause a Tor instance to pause while
439 OpenSSL would try to read a passphrase from the terminal. (Tor
440 instances run without a terminal, which is the case for most Tor
441 packages, are not impacted.) Fixes bug 24246; bugfix on every
442 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
443 Found by OSS-Fuzz as testcase 6360145429790720.
444 - When checking for replays in the INTRODUCE1 cell data for a
445 (legacy) onion service, correctly detect replays in the RSA-
446 encrypted part of the cell. We were previously checking for
447 replays on the entire cell, but those can be circumvented due to
448 the malleability of Tor's legacy hybrid encryption. This fix helps
449 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
450 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
453 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
454 - Fix a use-after-free error that could crash v2 Tor onion services
455 when they failed to open circuits while expiring introduction
456 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
457 also tracked as TROVE-2017-013 and CVE-2017-8823.
459 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
460 - When running as a relay, make sure that we never build a path through
461 ourselves, even in the case where we have somehow lost the version of
462 our descriptor appearing in the consensus. Fixes part of bug 21534;
463 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
466 o Minor features (bridge, backport from 0.3.1.9):
467 - Bridges now include notice in their descriptors that they are
468 bridges, and notice of their distribution status, based on their
469 publication settings. Implements ticket 18329. For more fine-
470 grained control of how a bridge is distributed, upgrade to 0.3.2.x
473 o Minor features (directory authority, backport from 0.3.2.6-alpha):
474 - Add an IPv6 address for the "bastet" directory authority. Closes
477 o Minor features (geoip):
478 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
481 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
482 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
483 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
486 Changes in version 0.2.5.16 - 2017-12-01
487 Tor 0.2.5.13 backports important security and stability bugfixes from
488 later Tor releases. All Tor users should upgrade to this release, or
489 to another of the releases coming out today.
491 Note: the Tor 0.2.5 series will no longer be supported after 1 May
492 2018. If you need a release with long-term support, please upgrade to
493 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
495 o Major bugfixes (security, backport from 0.3.2.6-alpha):
496 - Fix a denial of service bug where an attacker could use a
497 malformed directory object to cause a Tor instance to pause while
498 OpenSSL would try to read a passphrase from the terminal. (Tor
499 instances run without a terminal, which is the case for most Tor
500 packages, are not impacted.) Fixes bug 24246; bugfix on every
501 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
502 Found by OSS-Fuzz as testcase 6360145429790720.
503 - When checking for replays in the INTRODUCE1 cell data for a
504 (legacy) onion service, correctly detect replays in the RSA-
505 encrypted part of the cell. We were previously checking for
506 replays on the entire cell, but those can be circumvented due to
507 the malleability of Tor's legacy hybrid encryption. This fix helps
508 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
509 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
512 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
513 - When running as a relay, make sure that we never build a path
514 through ourselves, even in the case where we have somehow lost the
515 version of our descriptor appearing in the consensus. Fixes part
516 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
517 as TROVE-2017-012 and CVE-2017-8822.
519 o Minor features (bridge, backport from 0.3.1.9):
520 - Bridges now include notice in their descriptors that they are
521 bridges, and notice of their distribution status, based on their
522 publication settings. Implements ticket 18329. For more fine-
523 grained control of how a bridge is distributed, upgrade to 0.3.2.x
526 o Minor features (geoip):
527 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
531 Changes in version 0.3.2.5-alpha - 2017-11-22
532 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
533 fixes several stability and reliability bugs, including a fix for
534 intermittent bootstrapping failures that some people have been seeing
535 since the 0.3.0.x series.
537 Please test this alpha out -- many of these fixes will soon be
538 backported to stable Tor versions if no additional bugs are found
541 o Major bugfixes (bootstrapping):
542 - Fetch descriptors aggressively whenever we lack enough to build
543 circuits, regardless of how many descriptors we are missing.
544 Previously, we would delay launching the fetch when we had fewer
545 than 15 missing descriptors, even if some of those descriptors
546 were blocking circuits from building. Fixes bug 23985; bugfix on
547 0.1.1.11-alpha. The effects of this bug became worse in
548 0.3.0.3-alpha, when we began treating missing descriptors from our
549 primary guards as a reason to delay circuits.
550 - Don't try fetching microdescriptors from relays that have failed
551 to deliver them in the past. Fixes bug 23817; bugfix
554 o Minor features (directory authority):
555 - Make the "Exit" flag assignment only depend on whether the exit
556 policy allows connections to ports 80 and 443. Previously relays
557 would get the Exit flag if they allowed connections to one of
558 these ports and also port 6667. Resolves ticket 23637.
560 o Minor features (geoip):
561 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
564 o Minor features (linux seccomp2 sandbox):
565 - Update the sandbox rules so that they should now work correctly
566 with Glibc 2.26. Closes ticket 24315.
568 o Minor features (logging):
569 - Downgrade a pair of log messages that could occur when an exit's
570 resolver gave us an unusual (but not forbidden) response. Closes
572 - Improve the message we log when re-enabling circuit build timeouts
573 after having received a consensus. Closes ticket 20963.
575 o Minor bugfixes (compilation):
576 - Fix a memory leak warning in one of the libevent-related
577 configuration tests that could occur when manually specifying
578 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
579 Found and patched by Alex Xu.
580 - When detecting OpenSSL on Windows from our configure script, make
581 sure to try linking with the ws2_32 library. Fixes bug 23783;
582 bugfix on 0.3.2.2-alpha.
584 o Minor bugfixes (control port, linux seccomp2 sandbox):
585 - Avoid a crash when attempting to use the seccomp2 sandbox together
586 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
589 o Minor bugfixes (control port, onion services):
590 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
591 HS_DESC event when a service is not able to upload a descriptor.
592 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
594 o Minor bugfixes (directory cache):
595 - Recover better from empty or corrupt files in the consensus cache
596 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
597 - When a consensus diff calculation is only partially successful,
598 only record the successful parts as having succeeded. Partial
599 success can happen if (for example) one compression method fails
600 but the others succeed. Previously we misrecorded all the
601 calculations as having succeeded, which would later cause a
602 nonfatal assertion failure. Fixes bug 24086; bugfix
605 o Minor bugfixes (logging):
606 - Only log once if we notice that KIST support is gone. Fixes bug
607 24158; bugfix on 0.3.2.1-alpha.
608 - Suppress a log notice when relay descriptors arrive. We already
609 have a bootstrap progress for this so no need to log notice
610 everytime tor receives relay descriptors. Microdescriptors behave
611 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
613 o Minor bugfixes (network layer):
614 - When closing a connection via close_connection_immediately(), we
615 mark it as "not blocked on bandwidth", to prevent later calls from
616 trying to unblock it, and give it permission to read. This fixes a
617 backtrace warning that can happen on relays under various
618 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
620 o Minor bugfixes (onion services):
621 - The introduction circuit was being timed out too quickly while
622 waiting for the rendezvous circuit to complete. Keep the intro
623 circuit around longer instead of timing out and reopening new ones
624 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
625 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
626 so it matches dir-spec.txt. Fixes bug 24262; bugfix
628 - Silence a warning about failed v3 onion descriptor uploads that
629 can happen naturally under certain edge cases. Fixes part of bug
630 23662; bugfix on 0.3.2.1-alpha.
632 o Minor bugfixes (tests):
633 - Fix a memory leak in one of the bridge-distribution test cases.
634 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
635 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
636 to correctly handle cases where a caller gives it an RSA key of
637 under 160 bits. (This is not actually a bug in Tor itself, but
638 rather in our fuzzing code.) Fixes bug 24247; bugfix on
639 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
642 - Add notes in man page regarding OS support for the various
643 scheduler types. Attempt to use less jargon in the scheduler
644 section. Closes ticket 24254.
647 Changes in version 0.3.2.4-alpha - 2017-11-08
648 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
649 It fixes several stability and reliability bugs, especially including
650 a major reliability issue that has been plaguing fast exit relays in
653 o Major bugfixes (exit relays, DNS):
654 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
655 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
656 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
657 identifying and finding a workaround to this bug and to Moritz,
658 Arthur Edelstein, and Roger for helping to track it down and
661 o Major bugfixes (scheduler, channel):
662 - Stop processing scheduled channels if they closed while flushing
663 cells. This can happen if the write on the connection fails
664 leading to the channel being closed while in the scheduler loop.
665 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
667 o Minor features (logging, scheduler):
668 - Introduce a SCHED_BUG() function to log extra information about
669 the scheduler state if we ever catch a bug in the scheduler.
672 o Minor features (removed deprecations):
673 - The ClientDNSRejectInternalAddresses flag can once again be set in
674 non-testing Tor networks, so long as they do not use the default
675 directory authorities. This change also removes the deprecation of
676 this flag from 0.2.9.2-alpha. Closes ticket 21031.
678 o Minor features (testing):
679 - Our fuzzing tests now test the encrypted portions of v3 onion
680 service descriptors. Implements more of 21509.
682 o Minor bugfixes (directory client):
683 - On failure to download directory information, delay retry attempts
684 by a random amount based on the "decorrelated jitter" algorithm.
685 Our previous delay algorithm tended to produce extra-long delays
686 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
688 o Minor bugfixes (IPv6, v3 single onion services):
689 - Remove buggy code for IPv6-only v3 single onion services, and
690 reject attempts to configure them. This release supports IPv4,
691 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
692 stack v3 single onion services. Fixes bug 23820; bugfix
695 o Minor bugfixes (logging, relay):
696 - Give only a protocol warning when the ed25519 key is not
697 consistent between the descriptor and microdescriptor of a relay.
698 This can happen, for instance, if the relay has been flagged
699 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
701 o Minor bugfixes (manpage, onion service):
702 - Document that the HiddenServiceNumIntroductionPoints option is
703 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
704 bugfix on 0.3.2.1-alpha.
706 o Minor bugfixes (memory leaks):
707 - Fix a minor memory leak at exit in the KIST scheduler. This bug
708 should have no user-visible impact. Fixes bug 23774; bugfix
710 - Fix a memory leak when decrypting a badly formatted v3 onion
711 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
712 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
714 o Minor bugfixes (onion services):
715 - Cache some needed onion service client information instead of
716 constantly computing it over and over again. Fixes bug 23623;
717 bugfix on 0.3.2.1-alpha.
718 - Properly retry HSv3 descriptor fetches when missing required
719 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
721 o Minor bugfixes (path selection):
722 - When selecting relays by bandwidth, avoid a rounding error that
723 could sometimes cause load to be imbalanced incorrectly.
724 Previously, we would always round upwards; now, we round towards
725 the nearest integer. This had the biggest effect when a relay's
726 weight adjustments should have given it weight 0, but it got
727 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
728 - When calculating the fraction of nodes that have descriptors, and
729 all nodes in the network have zero bandwidths, count the number of
730 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
731 - Actually log the total bandwidth in compute_weighted_bandwidths().
732 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
734 o Minor bugfixes (relay, crash):
735 - Avoid a crash when transitioning from client mode to bridge mode.
736 Previously, we would launch the worker threads whenever our
737 "public server" mode changed, but not when our "server" mode
738 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
740 o Minor bugfixes (testing):
741 - Fix a spurious fuzzing-only use of an uninitialized value. Found
742 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
743 - Test that IPv6-only clients can use microdescriptors when running
744 "make test-network-all". Requires chutney master 61c28b9 or later.
748 Changes in version 0.3.2.3-alpha - 2017-10-27
749 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
750 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
751 directory authority, Bastet.
753 o Directory authority changes:
754 - Add "Bastet" as a ninth directory authority to the default list.
756 - The directory authority "Longclaw" has changed its IP address.
759 o Minor features (bridge):
760 - Bridge relays can now set the BridgeDistribution config option to
761 add a "bridge-distribution-request" line to their bridge
762 descriptor, which tells BridgeDB how they'd like their bridge
763 address to be given out. (Note that as of Oct 2017, BridgeDB does
764 not yet implement this feature.) As a side benefit, this feature
765 provides a way to distinguish bridge descriptors from non-bridge
766 descriptors. Implements tickets 18329.
768 o Minor features (client, entry guards):
769 - Improve log messages when missing descriptors for primary guards.
770 Resolves ticket 23670.
772 o Minor features (geoip):
773 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
776 o Minor bugfixes (bridge):
777 - Overwrite the bridge address earlier in the process of retrieving
778 its descriptor, to make sure we reach it on the configured
779 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
781 o Minor bugfixes (documentation):
782 - Document better how to read gcov, and what our gcov postprocessing
783 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
785 o Minor bugfixes (entry guards):
786 - Tor now updates its guard state when it reads a consensus
787 regardless of whether it's missing descriptors. That makes tor use
788 its primary guards to fetch descriptors in some edge cases where
789 it would previously have used fallback directories. Fixes bug
790 23862; bugfix on 0.3.0.1-alpha.
792 o Minor bugfixes (hidden service client):
793 - When handling multiple SOCKS request for the same .onion address,
794 only fetch the service descriptor once.
795 - When a descriptor fetch fails with a non-recoverable error, close
796 all pending SOCKS requests for that .onion. Fixes bug 23653;
797 bugfix on 0.3.2.1-alpha.
799 o Minor bugfixes (hidden service):
800 - Always regenerate missing hidden service public key files. Prior
801 to this, if the public key was deleted from disk, it wouldn't get
802 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
804 - Make sure that we have a usable ed25519 key when the intro point
805 relay supports ed25519 link authentication. Fixes bug 24002;
806 bugfix on 0.3.2.1-alpha.
808 o Minor bugfixes (hidden service, v2):
809 - When reloading configured hidden services, copy all information
810 from the old service object. Previously, some data was omitted,
811 causing delays in descriptor upload, and other bugs. Fixes bug
812 23790; bugfix on 0.2.1.9-alpha.
814 o Minor bugfixes (memory safety, defensive programming):
815 - Clear the target address when node_get_prim_orport() returns
816 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
818 o Minor bugfixes (relay):
819 - Avoid a BUG warning when receiving a dubious CREATE cell while an
820 option transition is in progress. Fixes bug 23952; bugfix
823 o Minor bugfixes (testing):
824 - Adjust the GitLab CI configuration to more closely match that of
825 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
826 - Prevent scripts/test/coverage from attempting to move gcov output
827 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
828 - When running unit tests as root, skip a test that would fail
829 because it expects a permissions error. This affects some
830 continuous integration setups. Fixes bug 23758; bugfix
832 - Stop unconditionally mirroring the tor repository in GitLab CI.
833 This prevented developers from enabling GitLab CI on master. Fixes
834 bug 23755; bugfix on 0.3.2.2-alpha.
835 - Fix the hidden service v3 descriptor decoding fuzzing to use the
836 latest decoding API correctly. Fixes bug 21509; bugfix
839 o Minor bugfixes (warnings):
840 - When we get an HTTP request on a SOCKS port, tell the user about
841 the new HTTPTunnelPort option. Previously, we would give a "Tor is
842 not an HTTP Proxy" message, which stopped being true when
843 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
847 Changes in version 0.2.5.15 - 2017-10-25
848 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
849 series. It also adds a new directory authority, Bastet.
851 Note: the Tor 0.2.5 series will no longer be supported after 1 May
852 2018. If you need a release with long-term support, please upgrade to
853 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
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 (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
862 - Avoid an assertion failure bug affecting our implementation of
863 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
864 handling of "0xx" differs from what we had expected. Fixes bug
865 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
867 o Minor features (geoip):
868 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
871 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
872 - Fix a memset() off the end of an array when packing cells. This
873 bug should be harmless in practice, since the corrupted bytes are
874 still in the same structure, and are always padding bytes,
875 ignored, or immediately overwritten, depending on compiler
876 behavior. Nevertheless, because the memset()'s purpose is to make
877 sure that any other cell-handling bugs can't expose bytes to the
878 network, we need to fix it. Fixes bug 22737; bugfix on
879 0.2.4.11-alpha. Fixes CID 1401591.
881 o Build features (backport from 0.3.1.5-alpha):
882 - Tor's repository now includes a Travis Continuous Integration (CI)
883 configuration file (.travis.yml). This is meant to help new
884 developers and contributors who fork Tor to a Github repository be
885 better able to test their changes, and understand what we expect
886 to pass. To use this new build feature, you must fork Tor to your
887 Github account, then go into the "Integrations" menu in the
888 repository settings for your fork and enable Travis, then push
889 your changes. Closes ticket 22636.
892 Changes in version 0.2.8.16 - 2017-10-25
893 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
894 series, including a bugfix for a crash issue that had affected relays
895 under memory pressure. It also adds a new directory authority, Bastet.
897 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
898 2018. If you need a release with long-term support, please stick with
899 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
901 o Directory authority changes:
902 - Add "Bastet" as a ninth directory authority to the default list.
904 - The directory authority "Longclaw" has changed its IP address.
907 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
908 - Fix a timing-based assertion failure that could occur when the
909 circuit out-of-memory handler freed a connection's output buffer.
910 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
912 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
913 - Remove longclaw's IPv6 address, as it will soon change. Authority
914 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
915 3/8 directory authorities with IPv6 addresses, but there are also
916 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
918 o Minor features (geoip):
919 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
923 Changes in version 0.2.9.13 - 2017-10-25
924 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
925 series, including a bugfix for a crash issue that had affected relays
926 under memory pressure. It also adds a new directory authority, Bastet.
928 o Directory authority changes:
929 - Add "Bastet" as a ninth directory authority to the default list.
931 - The directory authority "Longclaw" has changed its IP address.
934 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
935 - Fix a timing-based assertion failure that could occur when the
936 circuit out-of-memory handler freed a connection's output buffer.
937 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
939 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
940 - Remove longclaw's IPv6 address, as it will soon change. Authority
941 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
942 3/8 directory authorities with IPv6 addresses, but there are also
943 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
945 o Minor features (geoip):
946 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
949 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
950 - When a directory authority rejects a descriptor or extrainfo with
951 a given digest, mark that digest as undownloadable, so that we do
952 not attempt to download it again over and over. We previously
953 tried to avoid downloading such descriptors by other means, but we
954 didn't notice if we accidentally downloaded one anyway. This
955 behavior became problematic in 0.2.7.2-alpha, when authorities
956 began pinning Ed25519 keys. Fixes bug 22349; bugfix
959 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
960 - Clear the address when node_get_prim_orport() returns early.
961 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
963 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
964 - When running as a Windows service, set the ID of the main thread
965 correctly. Failure to do so made us fail to send log messages to
966 the controller in 0.2.1.16-rc, slowed down controller event
967 delivery in 0.2.7.3-rc and later, and crash with an assertion
968 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
969 Patch and diagnosis from "Vort".
972 Changes in version 0.3.0.12 - 2017-10-25
973 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
974 series, including a bugfix for a crash issue that had affected relays
975 under memory pressure. It also adds a new directory authority, Bastet.
977 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
978 2018. If you need a release with long-term support, please stick with
979 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
981 o Directory authority changes:
982 - Add "Bastet" as a ninth directory authority to the default list.
984 - The directory authority "Longclaw" has changed its IP address.
987 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
988 - Fix a timing-based assertion failure that could occur when the
989 circuit out-of-memory handler freed a connection's output buffer.
990 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
992 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
993 - Remove longclaw's IPv6 address, as it will soon change. Authority
994 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
995 3/8 directory authorities with IPv6 addresses, but there are also
996 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
998 o Minor features (geoip):
999 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1002 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
1003 - When a directory authority rejects a descriptor or extrainfo with
1004 a given digest, mark that digest as undownloadable, so that we do
1005 not attempt to download it again over and over. We previously
1006 tried to avoid downloading such descriptors by other means, but we
1007 didn't notice if we accidentally downloaded one anyway. This
1008 behavior became problematic in 0.2.7.2-alpha, when authorities
1009 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1012 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1013 - Avoid a possible double close of a circuit by the intro point on
1014 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1015 bugfix on 0.3.0.1-alpha.
1017 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1018 - Clear the address when node_get_prim_orport() returns early.
1019 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1021 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
1022 - When running as a Windows service, set the ID of the main thread
1023 correctly. Failure to do so made us fail to send log messages to
1024 the controller in 0.2.1.16-rc, slowed down controller event
1025 delivery in 0.2.7.3-rc and later, and crash with an assertion
1026 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1027 Patch and diagnosis from "Vort".
1030 Changes in version 0.3.1.8 - 2017-10-25
1031 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
1032 It includes several bugfixes, including a bugfix for a crash issue
1033 that had affected relays under memory pressure. It also adds
1034 a new directory authority, Bastet.
1036 o Directory authority changes:
1037 - Add "Bastet" as a ninth directory authority to the default list.
1038 Closes ticket 23910.
1039 - The directory authority "Longclaw" has changed its IP address.
1040 Closes ticket 23592.
1042 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1043 - Fix a timing-based assertion failure that could occur when the
1044 circuit out-of-memory handler freed a connection's output buffer.
1045 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1047 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1048 - Remove longclaw's IPv6 address, as it will soon change. Authority
1049 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1050 3/8 directory authorities with IPv6 addresses, but there are also
1051 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1053 o Minor features (geoip):
1054 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1057 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
1058 - Fix a compilation warning when building with zstd support on
1059 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1060 and fixed by Andreas Stieger.
1062 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
1063 - Handle a pathological case when decompressing Zstandard data when
1064 the output buffer size is zero. Fixes bug 23551; bugfix
1067 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
1068 - Remove the length limit on HTTP status lines that authorities can
1069 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
1071 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1072 - Avoid a possible double close of a circuit by the intro point on
1073 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1074 bugfix on 0.3.0.1-alpha.
1076 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1077 - Clear the address when node_get_prim_orport() returns early.
1078 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1080 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
1081 - Fix additional channelpadding unit test failures by using mocked
1082 time instead of actual time for all tests. Fixes bug 23608; bugfix
1086 Changes in version 0.3.2.2-alpha - 2017-09-29
1087 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
1088 release fixes several minor bugs in the new scheduler and next-
1089 generation onion services; both features were newly added in the 0.3.2
1090 series. Other fixes in this alpha include several fixes for non-fatal
1091 tracebacks which would appear in logs.
1093 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
1094 alpha does not contain any substantial new features. Minor features
1095 include better testing and logging.
1097 The following comprises the complete list of changes included
1098 in tor-0.3.2.2-alpha:
1100 o Major bugfixes (relay, crash, assertion failure):
1101 - Fix a timing-based assertion failure that could occur when the
1102 circuit out-of-memory handler freed a connection's output buffer.
1103 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1105 o Major bugfixes (scheduler):
1106 - If a channel is put into the scheduler's pending list, then it
1107 starts closing, and then if the scheduler runs before it finishes
1108 closing, the scheduler will get stuck trying to flush its cells
1109 while the lower layers refuse to cooperate. Fix that race
1110 condition by giving the scheduler an escape method. Fixes bug
1111 23676; bugfix on 0.3.2.1-alpha.
1113 o Minor features (build, compilation):
1114 - The "check-changes" feature is now part of the "make check" tests;
1115 we'll use it to try to prevent misformed changes files from
1116 accumulating. Closes ticket 23564.
1117 - Tor builds should now fail if there are any mismatches between the
1118 C type representing a configuration variable and the C type the
1119 data-driven parser uses to store a value there. Previously, we
1120 needed to check these by hand, which sometimes led to mistakes.
1121 Closes ticket 23643.
1123 o Minor features (directory authorities):
1124 - Remove longclaw's IPv6 address, as it will soon change. Authority
1125 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1126 3/8 directory authorities with IPv6 addresses, but there are also
1127 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1129 o Minor features (hidden service, circuit, logging):
1130 - Improve logging of many callsite in the circuit subsystem to print
1131 the circuit identifier(s).
1132 - Log when we cleanup an intro point from a service so we know when
1133 and for what reason it happened. Closes ticket 23604.
1135 o Minor features (logging):
1136 - Log more circuit information whenever we are about to try to
1137 package a relay cell on a circuit with a nonexistent n_chan.
1138 Attempt to diagnose ticket 8185.
1139 - Improve info-level log identification of particular circuits, to
1140 help with debugging. Closes ticket 23645.
1142 o Minor features (relay):
1143 - When choosing which circuits can be expired as unused, consider
1144 circuits from clients even if those clients used regular CREATE
1145 cells to make them; and do not consider circuits from relays even
1146 if they were made with CREATE_FAST. Part of ticket 22805.
1148 o Minor features (robustness):
1149 - Change several fatal assertions when flushing buffers into non-
1150 fatal assertions, to prevent any recurrence of 23690.
1152 o Minor features (spec conformance, bridge, diagnostic):
1153 - When handling the USERADDR command on an ExtOrPort, warn when the
1154 transports provides a USERADDR with no port. In a future version,
1155 USERADDR commands of this format may be rejected. Detects problems
1156 related to ticket 23080.
1158 o Minor features (testing):
1159 - Add a unit test to make sure that our own generated platform
1160 string will be accepted by directory authorities. Closes
1163 o Minor bugfixes (bootstrapping):
1164 - When warning about state file clock skew, report the correct
1165 direction for the detected skew. Fixes bug 23606; bugfix
1167 - Avoid an assertion failure when logging a state file clock skew
1168 very early in bootstrapping. Fixes bug 23607; bugfix
1171 o Minor bugfixes (build, compilation):
1172 - Fix a compilation warning when building with zstd support on
1173 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1174 and fixed by Andreas Stieger.
1175 - When searching for OpenSSL, don't accept any OpenSSL library that
1176 lacks TLSv1_1_method(): Tor doesn't build with those versions.
1177 Additionally, look in /usr/local/opt/openssl, if it's present.
1178 These changes together repair the default build on OSX systems
1179 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
1181 o Minor bugfixes (compression):
1182 - Handle a pathological case when decompressing Zstandard data when
1183 the output buffer size is zero. Fixes bug 23551; bugfix
1186 o Minor bugfixes (documentation):
1187 - Fix manpage to not refer to the obsolete (and misspelled)
1188 UseEntryGuardsAsDirectoryGuards parameter in the description of
1189 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
1191 o Minor bugfixes (hidden service v3):
1192 - Don't log an assertion failure when we can't find the right
1193 information to extend to an introduction point. In rare cases,
1194 this could happen, causing a warning, even though tor would
1195 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
1196 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
1197 much bigger so the rendezvous point can't distinguish which hidden
1198 service protocol is being used. Fixes bug 23420; bugfix
1201 o Minor bugfixes (hidden service, relay):
1202 - Avoid a possible double close of a circuit by the intro point on
1203 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1204 bugfix on 0.3.0.1-alpha.
1206 o Minor bugfixes (logging, relay shutdown, annoyance):
1207 - When a circuit is marked for close, do not attempt to package any
1208 cells for channels on that circuit. Previously, we would detect
1209 this condition lower in the call stack, when we noticed that the
1210 circuit had no attached channel, and log an annoying message.
1211 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1213 o Minor bugfixes (scheduler):
1214 - When switching schedulers due to a consensus change, we didn't
1215 give the new scheduler a chance to react to the consensus. Fix
1216 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
1217 - Make the KISTSchedRunInterval option a non negative value. With
1218 this, the way to disable KIST through the consensus is to set it
1219 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
1220 - Only notice log the selected scheduler when we switch scheduler
1221 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
1222 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
1223 by a different tv_usec data type. Fixes bug 23575; bugfix
1225 - Make a hard exit if tor is unable to pick a scheduler which can
1226 happen if the user specifies a scheduler type that is not
1227 supported and not other types in Schedulers. Fixes bug 23581;
1228 bugfix on 0.3.2.1-alpha.
1229 - Properly initialize the scheduler last run time counter so it is
1230 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
1232 o Minor bugfixes (testing):
1233 - Capture and detect several "Result does not fit" warnings in unit
1234 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
1236 - Fix additional channelpadding unit test failures by using mocked
1237 time instead of actual time for all tests. Fixes bug 23608; bugfix
1239 - The removal of some old scheduler options caused some tests to
1240 fail on BSD systems. Assume current behavior is correct and make
1241 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
1243 o Code simplification and refactoring:
1244 - Remove various ways of testing circuits and connections for
1245 "clientness"; instead, favor channel_is_client(). Part of
1248 o Deprecated features:
1249 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
1250 now deprecated; they do not apply to relays, and they have had no
1251 effect on clients since 0.2.8.x. Closes ticket 19704.
1254 - HiddenServiceVersion man page entry wasn't mentioning the now
1255 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
1256 - Clarify that the Address option is entirely about setting an
1257 advertised IPv4 address. Closes ticket 18891.
1258 - Clarify the manpage's use of the term "address" to clarify what
1259 kind of address is intended. Closes ticket 21405.
1260 - Document that onion service subdomains are allowed, and ignored.
1261 Closes ticket 18736.
1264 Changes in version 0.3.2.1-alpha - 2017-09-18
1265 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
1266 includes support for our next-generation ("v3") onion service
1267 protocol, and adds a new circuit scheduler for more responsive
1268 forwarding decisions from relays. There are also numerous other small
1269 features and bugfixes here.
1271 Below are the changes since Tor 0.3.1.7.
1273 o Major feature (scheduler, channel):
1274 - Tor now uses new schedulers to decide which circuits should
1275 deliver cells first, in order to improve congestion at relays. The
1276 first type is called "KIST" ("Kernel Informed Socket Transport"),
1277 and is only available on Linux-like systems: it uses feedback from
1278 the kernel to prevent the kernel's TCP buffers from growing too
1279 full. The second new scheduler type is called "KISTLite": it
1280 behaves the same as KIST, but runs on systems without kernel
1281 support for inspecting TCP implementation details. The old
1282 scheduler is still available, under the name "Vanilla". To change
1283 the default scheduler preference order, use the new "Schedulers"
1284 option. (The default preference order is "KIST,KISTLite,Vanilla".)
1286 Matt Traudt implemented KIST, based on research by Rob Jansen,
1287 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
1288 more information, see the design paper at
1289 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
1290 followup implementation paper at https://arxiv.org/abs/1709.01044.
1291 Closes ticket 12541.
1293 o Major features (next-generation onion services):
1294 - Tor now supports the next-generation onion services protocol for
1295 clients and services! As part of this release, the core of
1296 proposal 224 has been implemented and is available for
1297 experimentation and testing by our users. This newer version of
1298 onion services ("v3") features many improvements over the legacy
1301 a) Better crypto (replaced SHA1/DH/RSA1024
1302 with SHA3/ed25519/curve25519)
1304 b) Improved directory protocol, leaking much less information to
1307 c) Improved directory protocol, with smaller surface for
1310 d) Better onion address security against impersonation.
1312 e) More extensible introduction/rendezvous protocol.
1314 f) A cleaner and more modular codebase.
1316 You can identify a next-generation onion address by its length:
1317 they are 56 characters long, as in
1318 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
1320 In the future, we will release more options and features for v3
1321 onion services, but we first need a testing period, so that the
1322 current codebase matures and becomes more robust. Planned features
1323 include: offline keys, advanced client authorization, improved
1324 guard algorithms, and statistics. For full details, see
1327 Legacy ("v2") onion services will still work for the foreseeable
1328 future, and will remain the default until this new codebase gets
1329 tested and hardened. Service operators who want to experiment with
1330 the new system can use the 'HiddenServiceVersion 3' torrc
1331 directive along with the regular onion service configuration
1332 options. We will publish a blog post about this new feature
1335 o Major bugfixes (usability, control port):
1336 - Report trusted clock skew indications as bootstrap errors, so
1337 controllers can more easily alert users when their clocks are
1338 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
1340 o Minor features (bug detection):
1341 - Log a warning message with a stack trace for any attempt to call
1342 get_options() during option validation. This pattern has caused
1343 subtle bugs in the past. Closes ticket 22281.
1345 o Minor features (client):
1346 - You can now use Tor as a tunneled HTTP proxy: use the new
1347 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
1348 requests. Closes ticket 22407.
1349 - Add an extra check to make sure that we always use the newer guard
1350 selection code for picking our guards. Closes ticket 22779.
1351 - When downloading (micro)descriptors, don't split the list into
1352 multiple requests unless we want at least 32 descriptors.
1353 Previously, we split at 4, not 32, which led to significant
1354 overhead in HTTP request size and degradation in compression
1355 performance. Closes ticket 23220.
1357 o Minor features (command line):
1358 - Add a new commandline option, --key-expiration, which prints when
1359 the current signing key is going to expire. Implements ticket
1360 17639; patch by Isis Lovecruft.
1362 o Minor features (control port):
1363 - If an application tries to use the control port as an HTTP proxy,
1364 respond with a meaningful "This is the Tor control port" message,
1365 and log the event. Closes ticket 1667. Patch from Ravi
1367 - Provide better error message for GETINFO desc/(id|name) when not
1368 fetching router descriptors. Closes ticket 5847. Patch by
1370 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
1371 whether Tor will try to download router descriptors and
1372 microdescriptors respectively. Closes ticket 22684.
1373 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
1374 so controllers can tell whether the geoip databases are loaded.
1375 Closes ticket 23237.
1376 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
1377 events. Closes ticket 19254. Patch by "DonnchaC".
1379 o Minor features (development support):
1380 - Developers can now generate a call-graph for Tor using the
1381 "calltool" python program, which post-processes object dumps. It
1382 should work okay on many Linux and OSX platforms, and might work
1383 elsewhere too. To run it, install calltool from
1384 https://gitweb.torproject.org/user/nickm/calltool.git and run
1385 "make callgraph". Closes ticket 19307.
1387 o Minor features (ed25519):
1388 - Add validation function to checks for torsion components in
1389 ed25519 public keys, used by prop224 client-side code. Closes
1390 ticket 22006. Math help by Ian Goldberg.
1392 o Minor features (exit relay, DNS):
1393 - Improve the clarity and safety of the log message from evdns when
1394 receiving an apparently spoofed DNS reply. Closes ticket 3056.
1396 o Minor features (integration, hardening):
1397 - Add a new NoExec option to prevent Tor from running other
1398 programs. When this option is set to 1, Tor will never try to run
1399 another program, regardless of the settings of
1400 PortForwardingHelper, ClientTransportPlugin, or
1401 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
1402 without restarting Tor. Closes ticket 22976.
1404 o Minor features (logging):
1405 - Improve the warning message for specifying a relay by nickname.
1406 The previous message implied that nickname registration was still
1407 part of the Tor network design, which it isn't. Closes
1409 - If the sandbox filter fails to load, suggest to the user that
1410 their kernel might not support seccomp2. Closes ticket 23090.
1412 o Minor features (portability):
1413 - Check at configure time whether uint8_t is the same type as
1414 unsigned char. Lots of existing code already makes this
1415 assumption, and there could be strict aliasing issues if the
1416 assumption is violated. Closes ticket 22410.
1418 o Minor features (relay, configuration):
1419 - Reject attempts to use relative file paths when RunAsDaemon is
1420 set. Previously, Tor would accept these, but the directory-
1421 changing step of RunAsDaemon would give strange and/or confusing
1422 results. Closes ticket 22731.
1424 o Minor features (startup, safety):
1425 - When configured to write a PID file, Tor now exits if it is unable
1426 to do so. Previously, it would warn and continue. Closes
1429 o Minor features (static analysis):
1430 - The BUG() macro has been changed slightly so that Coverity no
1431 longer complains about dead code if the bug is impossible. Closes
1434 o Minor features (testing):
1435 - The default chutney network tests now include tests for the v3
1436 hidden service design. Make sure you have the latest version of
1437 chutney if you want to run these. Closes ticket 22437.
1438 - Add a unit test to verify that we can parse a hardcoded v2 hidden
1439 service descriptor. Closes ticket 15554.
1441 o Minor bugfixes (certificate handling):
1442 - Fix a time handling bug in Tor certificates set to expire after
1443 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
1444 Coverity as CID 1415728.
1446 o Minor bugfixes (client, usability):
1447 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
1448 SOCKS4a requests that contain IP address strings, even when
1449 SafeSocks in enabled, as this prevents user from connecting to
1450 known IP addresses without relying on DNS for resolving. SafeSocks
1451 still rejects SOCKS connections that connect to IP addresses when
1452 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
1453 bugfix on Tor 0.2.6.2-alpha.
1455 o Minor bugfixes (code correctness):
1456 - Call htons() in extend_cell_format() for encoding a 16-bit value.
1457 Previously we used ntohs(), which happens to behave the same on
1458 all the platforms we support, but which isn't really correct.
1459 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
1460 - For defense-in-depth, make the controller's write_escaped_data()
1461 function robust to extremely long inputs. Fixes bug 19281; bugfix
1462 on 0.1.1.1-alpha. Reported by Guido Vranken.
1464 o Minor bugfixes (compilation):
1465 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
1466 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1468 o Minor bugfixes (consensus expiry):
1469 - Check for adequate directory information correctly. Previously, Tor
1470 would reconsider whether it had sufficient directory information
1471 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
1473 o Minor bugfixes (directory protocol):
1474 - Directory servers now include a "Date:" http header for response
1475 codes other than 200. Clients starting with a skewed clock and a
1476 recent consensus were getting "304 Not modified" responses from
1477 directory authorities, so without the Date header, the client
1478 would never hear about a wrong clock. Fixes bug 23499; bugfix
1480 - Make clients wait for 6 seconds before trying to download a
1481 consensus from an authority. Fixes bug 17750; bugfix
1484 o Minor bugfixes (DoS-resistance):
1485 - If future code asks if there are any running bridges, without
1486 checking if bridges are enabled, log a BUG warning rather than
1487 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
1489 o Minor bugfixes (format strictness):
1490 - Restrict several data formats to decimal. Previously, the
1491 BuildTimeHistogram entries in the state file, the "bw=" entries in
1492 the bandwidth authority file, and the process IDs passed to the
1493 __OwningControllerProcess option could all be specified in hex or
1494 octal as well as in decimal. This was not an intentional feature.
1495 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
1498 o Minor bugfixes (heartbeat):
1499 - If we fail to write a heartbeat message, schedule a retry for the
1500 minimum heartbeat interval number of seconds in the future. Fixes
1501 bug 19476; bugfix on 0.2.3.1-alpha.
1503 o Minor bugfixes (linux seccomp2 sandbox, logging):
1504 - Fix some messages on unexpected errors from the seccomp2 library.
1505 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
1507 o Minor bugfixes (logging):
1508 - Remove duplicate log messages regarding opening non-local
1509 SocksPorts upon parsing config and opening listeners at startup.
1510 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
1511 - Use a more comprehensible log message when telling the user
1512 they've excluded every running exit node. Fixes bug 7890; bugfix
1514 - When logging the number of descriptors we intend to download per
1515 directory request, do not log a number higher than then the number
1516 of descriptors we're fetching in total. Fixes bug 19648; bugfix
1518 - When warning about a directory owned by the wrong user, log the
1519 actual name of the user owning the directory. Previously, we'd log
1520 the name of the process owner twice. Fixes bug 23487; bugfix
1522 - The tor specification says hop counts are 1-based, so fix two log
1523 messages that mistakenly logged 0-based hop counts. Fixes bug
1524 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
1525 Credit to Xiaofan Li for reporting this issue.
1527 o Minor bugfixes (portability):
1528 - Stop using the PATH_MAX variable, which is not defined on GNU
1529 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
1531 o Minor bugfixes (relay):
1532 - When uploading our descriptor for the first time after startup,
1533 report the reason for uploading as "Tor just started" rather than
1534 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
1535 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1536 relays, to prevent spurious address resolutions and descriptor
1537 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1538 bugfix on in 0.2.8.1-alpha.
1540 o Minor bugfixes (tests):
1541 - Fix a broken unit test for the OutboundAddress option: the parsing
1542 function was never returning an error on failure. Fixes bug 23366;
1543 bugfix on 0.3.0.3-alpha.
1544 - Fix a signed-integer overflow in the unit tests for
1545 dir/download_status_random_backoff, which was untriggered until we
1546 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
1548 o Minor bugfixes (usability, control port):
1549 - Stop making an unnecessary routerlist check in NETINFO clock skew
1550 detection; this was preventing clients from reporting NETINFO clock
1551 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
1553 o Code simplification and refactoring:
1554 - Extract the code for handling newly-open channels into a separate
1555 function from the general code to handle channel state
1556 transitions. This change simplifies our callgraph, reducing the
1557 size of the largest strongly connected component by roughly a
1558 factor of two. Closes ticket 22608.
1559 - Remove dead code for largely unused statistics on the number of
1560 times we've attempted various public key operations. Fixes bug
1561 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
1562 - Remove several now-obsolete functions for asking about old
1563 variants directory authority status. Closes ticket 22311; patch
1565 - Remove some of the code that once supported "Named" and "Unnamed"
1566 routers. Authorities no longer vote for these flags. Closes
1568 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
1569 and old hidden services, to indicate that they aren't suitable for
1570 new protocols or formats. Closes ticket 23026.
1571 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
1572 22521. Patch from Neel Chauhan.
1573 - Split the enormous circuit_send_next_onion_skin() function into
1574 multiple subfunctions. Closes ticket 22804.
1575 - Split the portions of the buffer.c module that handle particular
1576 protocols into separate modules. Part of ticket 23149.
1577 - Use our test macros more consistently, to produce more useful
1578 error messages when our unit tests fail. Add coccinelle patches to
1579 allow us to re-check for test macro uses. Closes ticket 22497.
1581 o Deprecated features:
1582 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
1583 only applies to direct unencrypted HTTP connections to your
1584 directory server, which your Tor probably isn't using. Closes
1588 - Clarify in the manual that "Sandbox 1" is only supported on Linux
1589 kernels. Closes ticket 22677.
1590 - Document all values of PublishServerDescriptor in the manpage.
1591 Closes ticket 15645.
1592 - Improve the documentation for the directory port part of the
1593 DirAuthority line. Closes ticket 20152.
1594 - Restore documentation for the authorities' "approved-routers"
1595 file. Closes ticket 21148.
1598 - The AllowDotExit option has been removed as unsafe. It has been
1599 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
1600 - The ClientDNSRejectInternalAddresses flag can no longer be set on
1601 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
1602 Closes ticket 21031.
1603 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
1604 nobody was using it any longer. Closes ticket 22377.
1607 Changes in version 0.2.8.15 - 2017-09-18
1608 Tor 0.2.8.15 backports a collection of bugfixes from later
1611 Most significantly, it includes a fix for TROVE-2017-008, a
1612 security bug that affects hidden services running with the
1613 SafeLogging option disabled. For more information, see
1614 https://trac.torproject.org/projects/tor/ticket/23490
1616 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
1617 2018. We suggest that you upgrade to the latest stable release if
1618 possible. If you can't, we recommend that you upgrade at least to
1619 0.2.9, which will be supported until 2020.
1621 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1622 - Avoid an assertion failure bug affecting our implementation of
1623 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1624 handling of "0xx" differs from what we had expected. Fixes bug
1625 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1628 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1631 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1632 - Backport a fix for an "unused variable" warning that appeared
1633 in some versions of mingw. Fixes bug 22838; bugfix on
1636 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1637 - Fix a memset() off the end of an array when packing cells. This
1638 bug should be harmless in practice, since the corrupted bytes are
1639 still in the same structure, and are always padding bytes,
1640 ignored, or immediately overwritten, depending on compiler
1641 behavior. Nevertheless, because the memset()'s purpose is to make
1642 sure that any other cell-handling bugs can't expose bytes to the
1643 network, we need to fix it. Fixes bug 22737; bugfix on
1644 0.2.4.11-alpha. Fixes CID 1401591.
1646 o Build features (backport from 0.3.1.5-alpha):
1647 - Tor's repository now includes a Travis Continuous Integration (CI)
1648 configuration file (.travis.yml). This is meant to help new
1649 developers and contributors who fork Tor to a Github repository be
1650 better able to test their changes, and understand what we expect
1651 to pass. To use this new build feature, you must fork Tor to your
1652 Github account, then go into the "Integrations" menu in the
1653 repository settings for your fork and enable Travis, then push
1654 your changes. Closes ticket 22636.
1657 Changes in version 0.2.9.12 - 2017-09-18
1658 Tor 0.2.9.12 backports a collection of bugfixes from later
1661 Most significantly, it includes a fix for TROVE-2017-008, a
1662 security bug that affects hidden services running with the
1663 SafeLogging option disabled. For more information, see
1664 https://trac.torproject.org/projects/tor/ticket/23490
1666 o Major features (security, backport from 0.3.0.2-alpha):
1667 - Change the algorithm used to decide DNS TTLs on client and server
1668 side, to better resist DNS-based correlation attacks like the
1669 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
1670 Feamster. Now relays only return one of two possible DNS TTL
1671 values, and clients are willing to believe DNS TTL values up to 3
1672 hours long. Closes ticket 19769.
1674 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
1675 - Fix a rare crash when sending a begin cell on a circuit whose
1676 linked directory connection had already been closed. Fixes bug
1677 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
1679 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
1680 - Fix a bug that prevented exit nodes from caching DNS records for
1681 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
1683 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
1684 - Fix a typo that had prevented TPROXY-based transparent proxying
1685 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
1686 Patch from "d4fq0fQAgoJ".
1688 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1689 - Avoid an assertion failure bug affecting our implementation of
1690 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1691 handling of "0xx" differs from what we had expected. Fixes bug
1692 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1694 o Minor features (code style, backport from 0.3.1.3-alpha):
1695 - Add "Falls through" comments to our codebase, in order to silence
1696 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1697 Stieger. Closes ticket 22446.
1699 o Minor features (geoip):
1700 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1703 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
1704 - Roll over monthly accounting at the configured hour and minute,
1705 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1706 Found by Andrey Karpov with PVS-Studio.
1708 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
1709 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
1710 bugfix on 0.2.8.1-alpha.
1711 - Fix warnings when building with libscrypt and openssl scrypt support
1712 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
1713 - When building with certain versions the mingw C header files, avoid
1714 float-conversion warnings when calling the C functions isfinite(),
1715 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
1717 o Minor bugfixes (compilation, backport from 0.3.1.7):
1718 - Avoid compiler warnings in the unit tests for running tor_sscanf()
1719 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1721 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1722 - Backport a fix for an "unused variable" warning that appeared
1723 in some versions of mingw. Fixes bug 22838; bugfix on
1726 o Minor bugfixes (controller, backport from 0.3.1.7):
1727 - Do not crash when receiving a HSPOST command with an empty body.
1728 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1729 - Do not crash when receiving a POSTDESCRIPTOR command with an
1730 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1732 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
1733 - Avoid Coverity build warnings related to our BUG() macro. By
1734 default, Coverity treats BUG() as the Linux kernel does: an
1735 instant abort(). We need to override that so our BUG() macro
1736 doesn't prevent Coverity from analyzing functions that use it.
1737 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
1739 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1740 - Fix a memset() off the end of an array when packing cells. This
1741 bug should be harmless in practice, since the corrupted bytes are
1742 still in the same structure, and are always padding bytes,
1743 ignored, or immediately overwritten, depending on compiler
1744 behavior. Nevertheless, because the memset()'s purpose is to make
1745 sure that any other cell-handling bugs can't expose bytes to the
1746 network, we need to fix it. Fixes bug 22737; bugfix on
1747 0.2.4.11-alpha. Fixes CID 1401591.
1749 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1750 - When setting the maximum number of connections allowed by the OS,
1751 always allow some extra file descriptors for other files. Fixes
1752 bug 22797; bugfix on 0.2.0.10-alpha.
1754 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
1755 - Avoid a sandbox failure when trying to re-bind to a socket and
1756 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
1758 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
1759 - Permit the fchmod system call, to avoid crashing on startup when
1760 starting with the seccomp2 sandbox and an unexpected set of
1761 permissions on the data directory or its contents. Fixes bug
1762 22516; bugfix on 0.2.5.4-alpha.
1764 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
1765 - Avoid a double-marked-circuit warning that could happen when we
1766 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
1769 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
1770 - Reject version numbers with non-numeric prefixes (such as +, -, or
1771 whitespace). Disallowing whitespace prevents differential version
1772 parsing between POSIX-based and Windows platforms. Fixes bug 21507
1773 and part of 21508; bugfix on 0.0.8pre1.
1775 o Build features (backport from 0.3.1.5-alpha):
1776 - Tor's repository now includes a Travis Continuous Integration (CI)
1777 configuration file (.travis.yml). This is meant to help new
1778 developers and contributors who fork Tor to a Github repository be
1779 better able to test their changes, and understand what we expect
1780 to pass. To use this new build feature, you must fork Tor to your
1781 Github account, then go into the "Integrations" menu in the
1782 repository settings for your fork and enable Travis, then push
1783 your changes. Closes ticket 22636.
1786 Changes in version 0.3.0.11 - 2017-09-18
1787 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
1790 Most significantly, it includes a fix for TROVE-2017-008, a
1791 security bug that affects hidden services running with the
1792 SafeLogging option disabled. For more information, see
1793 https://trac.torproject.org/projects/tor/ticket/23490
1795 o Minor features (code style, backport from 0.3.1.7):
1796 - Add "Falls through" comments to our codebase, in order to silence
1797 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1798 Stieger. Closes ticket 22446.
1801 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1804 o Minor bugfixes (compilation, backport from 0.3.1.7):
1805 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1806 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1808 o Minor bugfixes (controller, backport from 0.3.1.7):
1809 - Do not crash when receiving a HSPOST command with an empty body.
1810 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1811 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1812 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1814 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1815 - When setting the maximum number of connections allowed by the OS,
1816 always allow some extra file descriptors for other files. Fixes
1817 bug 22797; bugfix on 0.2.0.10-alpha.
1819 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
1820 - Remove a forgotten debugging message when an introduction point
1821 successfully establishes a hidden service prop224 circuit with
1823 - Change three other log_warn() for an introduction point to
1824 protocol warnings, because they can be failure from the network
1825 and are not relevant to the operator. Fixes bug 23078; bugfix on
1826 0.3.0.1-alpha and 0.3.0.2-alpha.
1829 Changes in version 0.3.1.7 - 2017-09-18
1830 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
1832 With the 0.3.1 series, Tor now serves and downloads directory
1833 information in more compact formats, to save on bandwidth overhead. It
1834 also contains a new padding system to resist netflow-based traffic
1835 analysis, and experimental support for building parts of Tor in Rust
1836 (though no parts of Tor are in Rust yet). There are also numerous
1837 small features, bugfixes on earlier release series, and groundwork for
1838 the hidden services revamp of 0.3.2.
1840 This release also includes a fix for TROVE-2017-008, a security bug
1841 that affects hidden services running with the SafeLogging option
1842 disabled. For more information, see
1843 https://trac.torproject.org/projects/tor/ticket/23490
1845 Per our stable release policy, we plan to support each stable release
1846 series for at least the next nine months, or for three months after
1847 the first stable release of the next series: whichever is longer. If
1848 you need a release with long-term support, we recommend that you stay
1849 with the 0.2.9 series.
1851 Below is a list of the changes since 0.3.1.6-rc. For a list of all
1852 changes since 0.3.0, see the ReleaseNotes file.
1854 o Major bugfixes (security, hidden services, loggging):
1855 - Fix a bug where we could log uninitialized stack when a certain
1856 hidden service error occurred while SafeLogging was disabled.
1857 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
1858 TROVE-2017-008 and CVE-2017-0380.
1860 o Minor features (defensive programming):
1861 - Create a pair of consensus parameters, nf_pad_tor2web and
1862 nf_pad_single_onion, to disable netflow padding in the consensus
1863 for non-anonymous connections in case the overhead is high. Closes
1866 o Minor features (diagnostic):
1867 - Add a stack trace to the bug warnings that can be logged when
1868 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
1869 attempt for bug 23105.
1871 o Minor features (geoip):
1872 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1875 o Minor bugfixes (compilation):
1876 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1877 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1879 o Minor bugfixes (controller):
1880 - Do not crash when receiving a HSPOST command with an empty body.
1881 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1882 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1883 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1885 o Minor bugfixes (relay):
1886 - Inform the geoip and rephist modules about all requests, even on
1887 relays that are only fetching microdescriptors. Fixes a bug
1888 related to 21585; bugfix on 0.3.0.1-alpha.
1890 o Minor bugfixes (unit tests):
1891 - Fix a channelpadding unit test failure on slow systems by using
1892 mocked time instead of actual time. Fixes bug 23077; bugfix
1896 Changes in version 0.3.1.6-rc - 2017-09-05
1897 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
1898 release series, including a bug that produced weird behavior on
1899 Windows directory caches.
1901 This is the first release candidate in the Tor 0.3.1 series. If we
1902 find no new bugs or regressions here, the first stable 0.3.1 release
1903 will be nearly identical to it.
1905 o Major bugfixes (windows, directory cache):
1906 - On Windows, do not try to delete cached consensus documents and
1907 diffs before they are unmapped from memory--Windows won't allow
1908 that. Instead, allow the consensus cache directory to grow larger,
1909 to hold files that might need to stay around longer. Fixes bug
1910 22752; bugfix on 0.3.1.1-alpha.
1912 o Minor features (directory authority):
1913 - Improve the message that authorities report to relays that present
1914 RSA/Ed25519 keypairs that conflict with previously pinned keys.
1915 Closes ticket 22348.
1917 o Minor features (geoip):
1918 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
1921 o Minor features (testing):
1922 - Add more tests for compression backend initialization. Closes
1925 o Minor bugfixes (directory cache):
1926 - Fix a memory leak when recovering space in the consensus cache.
1927 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
1929 o Minor bugfixes (hidden service):
1930 - Increase the number of circuits that a service is allowed to
1931 open over a specific period of time. The value was lower than it
1932 should be (8 vs 12) in the normal case of 3 introduction points.
1933 Fixes bug 22159; bugfix on 0.3.0.5-rc.
1934 - Fix a BUG warning during HSv3 descriptor decoding that could be
1935 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
1936 on 0.3.0.1-alpha. Bug found by "haxxpop".
1937 - Rate-limit the log messages if we exceed the maximum number of
1938 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
1940 o Minor bugfixes (logging, relay):
1941 - Remove a forgotten debugging message when an introduction point
1942 successfully establishes a hidden service prop224 circuit with
1944 - Change three other log_warn() for an introduction point to
1945 protocol warnings, because they can be failure from the network
1946 and are not relevant to the operator. Fixes bug 23078; bugfix on
1947 0.3.0.1-alpha and 0.3.0.2-alpha.
1949 o Minor bugfixes (relay):
1950 - When a relay is not running as a directory cache, it will no
1951 longer generate compressed consensuses and consensus diff
1952 information. Previously, this was a waste of disk and CPU. Fixes
1953 bug 23275; bugfix on 0.3.1.1-alpha.
1955 o Minor bugfixes (robustness, error handling):
1956 - Improve our handling of the cases where OpenSSL encounters a
1957 memory error while encoding keys and certificates. We haven't
1958 observed these errors in the wild, but if they do happen, we now
1959 detect and respond better. Fixes bug 19418; bugfix on all versions
1960 of Tor. Reported by Guido Vranken.
1962 o Minor bugfixes (stability):
1963 - Avoid crashing on a double-free when unable to load or process an
1964 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
1965 with the clang static analyzer.
1967 o Minor bugfixes (testing):
1968 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1969 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1970 - Port the hs_ntor handshake test to work correctly with recent
1971 versions of the pysha3 module. Fixes bug 23071; bugfix
1974 o Minor bugfixes (Windows service):
1975 - When running as a Windows service, set the ID of the main thread
1976 correctly. Failure to do so made us fail to send log messages to
1977 the controller in 0.2.1.16-rc, slowed down controller event
1978 delivery in 0.2.7.3-rc and later, and crash with an assertion
1979 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1980 Patch and diagnosis from "Vort".
1983 Changes in version 0.3.0.10 - 2017-08-02
1984 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
1985 from the current Tor alpha series. OpenBSD users and TPROXY users
1986 should upgrade; others are probably okay sticking with 0.3.0.9.
1988 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
1989 - Tor's repository now includes a Travis Continuous Integration (CI)
1990 configuration file (.travis.yml). This is meant to help new
1991 developers and contributors who fork Tor to a Github repository be
1992 better able to test their changes, and understand what we expect
1993 to pass. To use this new build feature, you must fork Tor to your
1994 Github account, then go into the "Integrations" menu in the
1995 repository settings for your fork and enable Travis, then push
1996 your changes. Closes ticket 22636.
1998 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
1999 - Fix a typo that had prevented TPROXY-based transparent proxying
2000 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2001 Patch from "d4fq0fQAgoJ".
2003 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2004 - Avoid an assertion failure bug affecting our implementation of
2005 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2006 handling of "0xbar" differs from what we had expected. Fixes bug
2007 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2009 o Minor features (backport from 0.3.1.5-alpha):
2010 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
2013 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
2014 - Roll over monthly accounting at the configured hour and minute,
2015 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2016 Found by Andrey Karpov with PVS-Studio.
2018 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
2019 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
2020 bugfix on 0.2.8.1-alpha.
2021 - Fix warnings when building with libscrypt and openssl scrypt
2022 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2023 - When building with certain versions of the mingw C header files,
2024 avoid float-conversion warnings when calling the C functions
2025 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2028 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2029 - Backport a fix for an "unused variable" warning that appeared
2030 in some versions of mingw. Fixes bug 22838; bugfix on
2033 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
2034 - Avoid Coverity build warnings related to our BUG() macro. By
2035 default, Coverity treats BUG() as the Linux kernel does: an
2036 instant abort(). We need to override that so our BUG() macro
2037 doesn't prevent Coverity from analyzing functions that use it.
2038 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2040 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
2041 - When rejecting a router descriptor for running an obsolete version
2042 of Tor without ntor support, warn about the obsolete tor version,
2043 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2045 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
2046 - Avoid a sandbox failure when trying to re-bind to a socket and
2047 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2049 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
2050 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2051 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2054 Changes in version 0.3.1.5-alpha - 2017-08-01
2055 Tor 0.3.1.5-alpha improves the performance of consensus diff
2056 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
2057 several other bugs. If no serious bugs are found in this version, the
2058 next version will be a release candidate.
2060 This release also marks the end of support for the Tor 0.2.4.x,
2061 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
2062 further bug or security fixes. Anyone still running or distributing
2063 one of those versions should upgrade.
2065 o Major features (build system, continuous integration):
2066 - Tor's repository now includes a Travis Continuous Integration (CI)
2067 configuration file (.travis.yml). This is meant to help new
2068 developers and contributors who fork Tor to a Github repository be
2069 better able to test their changes, and understand what we expect
2070 to pass. To use this new build feature, you must fork Tor to your
2071 Github account, then go into the "Integrations" menu in the
2072 repository settings for your fork and enable Travis, then push
2073 your changes. Closes ticket 22636.
2075 o Major bugfixes (openbsd, denial-of-service):
2076 - Avoid an assertion failure bug affecting our implementation of
2077 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2078 handling of "0xbar" differs from what we had expected. Fixes bug
2079 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2081 o Major bugfixes (relay, performance):
2082 - Perform circuit handshake operations at a higher priority than we
2083 use for consensus diff creation and compression. This should
2084 prevent circuits from starving when a relay or bridge receives a
2085 new consensus, especially on lower-powered machines. Fixes bug
2086 22883; bugfix on 0.3.1.1-alpha.
2088 o Minor features (bridge authority):
2089 - Add "fingerprint" lines to the networkstatus-bridges file produced
2090 by bridge authorities. Closes ticket 22207.
2092 o Minor features (directory cache, consensus diff):
2093 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
2094 operators with low-resource environments to adjust the number of
2095 consensuses they'll store and generate diffs from. Most cache
2096 operators should leave it unchanged. Helps to work around
2099 o Minor features (geoip):
2100 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
2103 o Minor features (relay, performance):
2104 - Always start relays with at least two worker threads, to prevent
2105 priority inversion on slow tasks. Part of the fix for bug 22883.
2106 - Allow background work to be queued with different priorities, so
2107 that a big pile of slow low-priority jobs will not starve out
2108 higher priority jobs. This lays the groundwork for a fix for
2111 o Minor bugfixes (build system, rust):
2112 - Fix a problem where Rust toolchains were not being found when
2113 building without --enable-cargo-online-mode, due to setting the
2114 $HOME environment variable instead of $CARGO_HOME. Fixes bug
2115 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
2117 o Minor bugfixes (compatibility, zstd):
2118 - Write zstd epilogues correctly when the epilogue requires
2119 reallocation of the output buffer, even with zstd 1.3.0.
2120 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
2121 22927; bugfix on 0.3.1.1-alpha.
2123 o Minor bugfixes (compilation warnings):
2124 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
2125 22915; bugfix on 0.2.8.1-alpha.
2126 - Fix warnings when building with libscrypt and openssl scrypt
2127 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2128 - Compile correctly when both openssl 1.1.0 and libscrypt are
2129 detected. Previously this would cause an error. Fixes bug 22892;
2130 bugfix on 0.3.1.1-alpha.
2131 - When building with certain versions of the mingw C header files,
2132 avoid float-conversion warnings when calling the C functions
2133 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2136 o Minor bugfixes (coverity build support):
2137 - Avoid Coverity build warnings related to our BUG() macro. By
2138 default, Coverity treats BUG() as the Linux kernel does: an
2139 instant abort(). We need to override that so our BUG() macro
2140 doesn't prevent Coverity from analyzing functions that use it.
2141 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2143 o Minor bugfixes (directory authority):
2144 - When a directory authority rejects a descriptor or extrainfo with
2145 a given digest, mark that digest as undownloadable, so that we do
2146 not attempt to download it again over and over. We previously
2147 tried to avoid downloading such descriptors by other means, but we
2148 didn't notice if we accidentally downloaded one anyway. This
2149 behavior became problematic in 0.2.7.2-alpha, when authorities
2150 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2153 o Minor bugfixes (error reporting, windows):
2154 - When formatting Windows error messages, use the English format to
2155 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
2158 o Minor bugfixes (file limits, osx):
2159 - When setting the maximum number of connections allowed by the OS,
2160 always allow some extra file descriptors for other files. Fixes
2161 bug 22797; bugfix on 0.2.0.10-alpha.
2163 o Minor bugfixes (linux seccomp2 sandbox):
2164 - Avoid a sandbox failure when trying to re-bind to a socket and
2165 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2167 o Minor bugfixes (memory leaks):
2168 - Fix a small memory leak when validating a configuration that uses
2169 two or more AF_UNIX sockets for the same port type. Fixes bug
2170 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
2172 o Minor bugfixes (unit tests):
2173 - test_consdiff_base64cmp would fail on OS X because while OS X
2174 follows the standard of (less than zero/zero/greater than zero),
2175 it doesn't follow the convention of (-1/0/+1). Make the test
2176 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
2177 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2178 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2181 Changes in version 0.3.1.4-alpha - 2017-06-29
2182 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
2183 to use a guard that was in the same network family as a chosen exit
2184 relay. This is a security regression; all clients running earlier
2185 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
2188 This release also fixes several other bugs introduced in 0.3.0.x
2189 and 0.3.1.x, including others that can affect bandwidth usage
2193 - To build with zstd and lzma support, Tor now requires the
2194 pkg-config tool at build time. (This requirement was new in
2195 0.3.1.1-alpha, but was not noted at the time. Noting it here to
2196 close ticket 22623.)
2198 o Major bugfixes (path selection, security):
2199 - When choosing which guard to use for a circuit, avoid the exit's
2200 family along with the exit itself. Previously, the new guard
2201 selection logic avoided the exit, but did not consider its family.
2202 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2203 006 and CVE-2017-0377.
2205 o Major bugfixes (compression, zstd):
2206 - Correctly detect a full buffer when decompressing a large zstd-
2207 compressed input. Previously, we would sometimes treat a full
2208 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
2210 o Major bugfixes (directory protocol):
2211 - Ensure that we send "304 Not modified" as HTTP status code when a
2212 client is attempting to fetch a consensus or consensus diff, and
2213 the best one we can send them is one they already have. Fixes bug
2214 22702; bugfix on 0.3.1.1-alpha.
2216 o Major bugfixes (entry guards):
2217 - When starting with an old consensus, do not add new entry guards
2218 unless the consensus is "reasonably live" (under 1 day old). Fixes
2219 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2221 o Minor features (bug mitigation, diagnostics, logging):
2222 - Avoid an assertion failure, and log a better error message, when
2223 unable to remove a file from the consensus cache on Windows.
2224 Attempts to mitigate and diagnose bug 22752.
2226 o Minor features (geoip):
2227 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
2230 o Minor bugfixes (compression):
2231 - When compressing or decompressing a buffer, check for a failure to
2232 create a compression object. Fixes bug 22626; bugfix
2234 - When decompressing a buffer, check for extra data after the end of
2235 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
2236 - When decompressing an object received over an anonymous directory
2237 connection, if we have already decompressed it using an acceptable
2238 compression method, do not reject it for looking like an
2239 unacceptable compression method. Fixes part of bug 22670; bugfix
2241 - When serving directory votes compressed with zlib, do not claim to
2242 have compressed them with zstd. Fixes bug 22669; bugfix
2244 - When spooling compressed data to an output buffer, don't try to
2245 spool more data when there is no more data to spool and we are not
2246 trying to flush the input. Previously, we would sometimes launch
2247 compression requests with nothing to do, which interferes with our
2248 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
2250 o Minor bugfixes (defensive programming):
2251 - Detect and break out of infinite loops in our compression code. We
2252 don't think that any such loops exist now, but it's best to be
2253 safe. Closes ticket 22672.
2254 - Fix a memset() off the end of an array when packing cells. This
2255 bug should be harmless in practice, since the corrupted bytes are
2256 still in the same structure, and are always padding bytes,
2257 ignored, or immediately overwritten, depending on compiler
2258 behavior. Nevertheless, because the memset()'s purpose is to make
2259 sure that any other cell-handling bugs can't expose bytes to the
2260 network, we need to fix it. Fixes bug 22737; bugfix on
2261 0.2.4.11-alpha. Fixes CID 1401591.
2263 o Minor bugfixes (linux seccomp2 sandbox):
2264 - Permit the fchmod system call, to avoid crashing on startup when
2265 starting with the seccomp2 sandbox and an unexpected set of
2266 permissions on the data directory or its contents. Fixes bug
2267 22516; bugfix on 0.2.5.4-alpha.
2268 - Fix a crash in the LZMA module, when the sandbox was enabled, and
2269 liblzma would allocate more than 16 MB of memory. We solve this by
2270 bumping the mprotect() limit in the sandbox module from 16 MB to
2271 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
2273 o Minor bugfixes (logging):
2274 - When decompressing, do not warn if we fail to decompress using a
2275 compression method that we merely guessed. Fixes part of bug
2276 22670; bugfix on 0.1.1.14-alpha.
2277 - When decompressing, treat mismatch between content-encoding and
2278 actual compression type as a protocol warning. Fixes part of bug
2279 22670; bugfix on 0.1.1.9-alpha.
2280 - Downgrade "assigned_to_cpuworker failed" message to info-level
2281 severity. In every case that can reach it, either a better warning
2282 has already been logged, or no warning is warranted. Fixes bug
2283 22356; bugfix on 0.2.6.3-alpha.
2284 - Demote a warn that was caused by libevent delays to info if
2285 netflow padding is less than 4.5 seconds late, or to notice
2286 if it is more (4.5 seconds is the amount of time that a netflow
2287 record might be emitted after, if we chose the maximum timeout).
2288 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
2290 o Minor bugfixes (process behavior):
2291 - When exiting because of an error, always exit with a nonzero exit
2292 status. Previously, we would fail to report an error in our exit
2293 status in cases related to __OwningControllerProcess failure,
2294 lockfile contention, and Ed25519 key initialization. Fixes bug
2295 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
2296 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
2300 - Add a manpage description for the key-pinning-journal file. Closes
2302 - Correctly note that bandwidth accounting values are stored in the
2303 state file, and the bw_accounting file is now obsolete. Closes
2305 - Document more of the files in the Tor data directory, including
2306 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
2307 approved-routers, sr-random, and diff-cache. Found while fixing
2311 Changes in version 0.3.0.9 - 2017-06-29
2312 Tor 0.3.0.9 fixes a path selection bug that would allow a client
2313 to use a guard that was in the same network family as a chosen exit
2314 relay. This is a security regression; all clients running earlier
2315 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
2318 This release also backports several other bugfixes from the 0.3.1.x
2321 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
2322 - When choosing which guard to use for a circuit, avoid the exit's
2323 family along with the exit itself. Previously, the new guard
2324 selection logic avoided the exit, but did not consider its family.
2325 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2326 006 and CVE-2017-0377.
2328 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
2329 - Don't block bootstrapping when a primary bridge is offline and we
2330 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2331 21969; bugfix on 0.3.0.3-alpha.
2333 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
2334 - When starting with an old consensus, do not add new entry guards
2335 unless the consensus is "reasonably live" (under 1 day old). Fixes
2336 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2338 o Minor features (geoip):
2339 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
2342 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
2343 - Reject version numbers with non-numeric prefixes (such as +, -, or
2344 whitespace). Disallowing whitespace prevents differential version
2345 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2346 and part of 21508; bugfix on 0.0.8pre1.
2348 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
2349 - Permit the fchmod system call, to avoid crashing on startup when
2350 starting with the seccomp2 sandbox and an unexpected set of
2351 permissions on the data directory or its contents. Fixes bug
2352 22516; bugfix on 0.2.5.4-alpha.
2354 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
2355 - Fix a memset() off the end of an array when packing cells. This
2356 bug should be harmless in practice, since the corrupted bytes are
2357 still in the same structure, and are always padding bytes,
2358 ignored, or immediately overwritten, depending on compiler
2359 behavior. Nevertheless, because the memset()'s purpose is to make
2360 sure that any other cell-handling bugs can't expose bytes to the
2361 network, we need to fix it. Fixes bug 22737; bugfix on
2362 0.2.4.11-alpha. Fixes CID 1401591.
2365 Changes in version 0.3.1.3-alpha - 2017-06-08
2366 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
2367 remotely crash a hidden service with an assertion failure. Anyone
2368 running a hidden service should upgrade to this version, or to some
2369 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
2371 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
2372 that sometimes made relays unreliable, as well as several other
2373 bugfixes described below.
2375 o Major bugfixes (hidden service, relay, security):
2376 - Fix a remotely triggerable assertion failure when a hidden service
2377 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2378 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2379 - Fix a remotely triggerable assertion failure caused by receiving a
2380 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2381 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2384 o Major bugfixes (relay, link handshake):
2385 - When performing the v3 link handshake on a TLS connection, report
2386 that we have the x509 certificate that we actually used on that
2387 connection, even if we have changed certificates since that
2388 connection was first opened. Previously, we would claim to have
2389 used our most recent x509 link certificate, which would sometimes
2390 make the link handshake fail. Fixes one case of bug 22460; bugfix
2393 o Major bugfixes (relays, key management):
2394 - Regenerate link and authentication certificates whenever the key
2395 that signs them changes; also, regenerate link certificates
2396 whenever the signed key changes. Previously, these processes were
2397 only weakly coupled, and we relays could (for minutes to hours)
2398 wind up with an inconsistent set of keys and certificates, which
2399 other relays would not accept. Fixes two cases of bug 22460;
2400 bugfix on 0.3.0.1-alpha.
2401 - When sending an Ed25519 signing->link certificate in a CERTS cell,
2402 send the certificate that matches the x509 certificate that we
2403 used on the TLS connection. Previously, there was a race condition
2404 if the TLS context rotated after we began the TLS handshake but
2405 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
2408 o Major bugfixes (torrc, crash):
2409 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
2410 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
2412 o Minor features (code style):
2413 - Add "Falls through" comments to our codebase, in order to silence
2414 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2415 Stieger. Closes ticket 22446.
2417 o Minor features (diagnostic):
2418 - Add logging messages to try to diagnose a rare bug that seems to
2419 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
2420 think this is happening because of incorrect system clocks, but
2421 we'd like to know for certain. Diagnostic for bug 22466.
2423 o Minor bugfixes (correctness):
2424 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2425 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2427 o Minor bugfixes (directory protocol):
2428 - Check for libzstd >= 1.1, because older versions lack the
2429 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
2431 o Minor bugfixes (link handshake):
2432 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2433 months, and regenerate it when it is within one month of expiring.
2434 Previously, we had generated this certificate at startup with a
2435 ten-year lifetime, but that could lead to weird behavior when Tor
2436 was started with a grossly inaccurate clock. Mitigates bug 22466;
2437 mitigation on 0.3.0.1-alpha.
2439 o Minor bugfixes (storage directories):
2440 - Always check for underflows in the cached storage directory usage.
2441 If the usage does underflow, re-calculate it. Also, avoid a
2442 separate underflow when the usage is not known. Fixes bug 22424;
2443 bugfix on 0.3.1.1-alpha.
2445 o Minor bugfixes (unit tests):
2446 - The unit tests now pass on systems where localhost is misconfigured
2447 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
2451 - Clarify the manpage for the (deprecated) torify script. Closes
2454 Changes in version 0.3.0.8 - 2017-06-08
2455 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
2456 remotely crash a hidden service with an assertion failure. Anyone
2457 running a hidden service should upgrade to this version, or to some
2458 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
2460 Tor 0.3.0.8 also includes fixes for several key management bugs
2461 that sometimes made relays unreliable, as well as several other
2462 bugfixes described below.
2464 o Major bugfixes (hidden service, relay, security, backport
2465 from 0.3.1.3-alpha):
2466 - Fix a remotely triggerable assertion failure when a hidden service
2467 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2468 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2469 - Fix a remotely triggerable assertion failure caused by receiving a
2470 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2471 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2474 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2475 - When performing the v3 link handshake on a TLS connection, report
2476 that we have the x509 certificate that we actually used on that
2477 connection, even if we have changed certificates since that
2478 connection was first opened. Previously, we would claim to have
2479 used our most recent x509 link certificate, which would sometimes
2480 make the link handshake fail. Fixes one case of bug 22460; bugfix
2483 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
2484 - Regenerate link and authentication certificates whenever the key
2485 that signs them changes; also, regenerate link certificates
2486 whenever the signed key changes. Previously, these processes were
2487 only weakly coupled, and we relays could (for minutes to hours)
2488 wind up with an inconsistent set of keys and certificates, which
2489 other relays would not accept. Fixes two cases of bug 22460;
2490 bugfix on 0.3.0.1-alpha.
2491 - When sending an Ed25519 signing->link certificate in a CERTS cell,
2492 send the certificate that matches the x509 certificate that we
2493 used on the TLS connection. Previously, there was a race condition
2494 if the TLS context rotated after we began the TLS handshake but
2495 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
2498 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
2499 - Stop rejecting v3 hidden service descriptors because their size
2500 did not match an old padding rule. Fixes bug 22447; bugfix on
2503 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2504 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2505 December 2016 (of which ~126 were still functional) with a list of
2506 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2507 2017. Resolves ticket 21564.
2509 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
2510 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
2511 bug 22252; bugfix on 0.2.9.3-alpha.
2513 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
2514 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2515 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2517 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
2518 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2519 months, and regenerate it when it is within one month of expiring.
2520 Previously, we had generated this certificate at startup with a
2521 ten-year lifetime, but that could lead to weird behavior when Tor
2522 was started with a grossly inaccurate clock. Mitigates bug 22466;
2523 mitigation on 0.3.0.1-alpha.
2525 o Minor bugfixes (memory leak, directory authority, backport from
2527 - When directory authorities reject a router descriptor due to
2528 keypinning, free the router descriptor rather than leaking the
2529 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2532 Changes in version 0.2.9.11 - 2017-06-08
2533 Tor 0.2.9.11 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 Tor 0.2.9.11 also backports fixes for several key management bugs
2540 that sometimes made relays unreliable, as well as several other
2541 bugfixes described below.
2543 o Major bugfixes (hidden service, relay, security, backport
2544 from 0.3.1.3-alpha):
2545 - Fix a remotely triggerable assertion failure caused by receiving a
2546 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2547 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2550 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2551 - When performing the v3 link handshake on a TLS connection, report
2552 that we have the x509 certificate that we actually used on that
2553 connection, even if we have changed certificates since that
2554 connection was first opened. Previously, we would claim to have
2555 used our most recent x509 link certificate, which would sometimes
2556 make the link handshake fail. Fixes one case of bug 22460; bugfix
2559 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2560 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2561 December 2016 (of which ~126 were still functional) with a list of
2562 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2563 2017. Resolves ticket 21564.
2565 o Minor features (future-proofing, backport from 0.3.0.7):
2566 - Tor no longer refuses to download microdescriptors or descriptors if
2567 they are listed as "published in the future". This change will
2568 eventually allow us to stop listing meaningful "published" dates
2569 in microdescriptor consensuses, and thereby allow us to reduce the
2570 resources required to download consensus diffs by over 50%.
2571 Implements part of ticket 21642; implements part of proposal 275.
2573 o Minor features (directory authorities, backport from 0.3.0.4-rc)
2574 - Directory authorities now reject relays running versions
2575 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
2576 suffer from bug 20499 and don't keep their consensus cache
2577 up-to-date. Resolves ticket 20509.
2579 o Minor features (geoip):
2580 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2583 o Minor bugfixes (control port, backport from 0.3.0.6):
2584 - The GETINFO extra-info/digest/<digest> command was broken because
2585 of a wrong base16 decode return value check, introduced when
2586 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
2588 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
2589 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2590 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2592 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
2593 - The getpid() system call is now permitted under the Linux seccomp2
2594 sandbox, to avoid crashing with versions of OpenSSL (and other
2595 libraries) that attempt to learn the process's PID by using the
2596 syscall rather than the VDSO code. Fixes bug 21943; bugfix
2599 o Minor bugfixes (memory leak, directory authority, backport
2600 from 0.3.1.2-alpha):
2601 - When directory authorities reject a router descriptor due to
2602 keypinning, free the router descriptor rather than leaking the
2603 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2605 Changes in version 0.2.8.14 - 2017-06-08
2606 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2607 remotely crash a hidden service with an assertion failure. Anyone
2608 running a hidden service should upgrade to this version, or to some
2609 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2610 are not affected by TROVE-2017-004.)
2612 o Major bugfixes (hidden service, relay, security):
2613 - Fix a remotely triggerable assertion failure caused by receiving a
2614 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2615 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2618 o Minor features (geoip):
2619 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2622 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2623 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2624 December 2016 (of which ~126 were still functional) with a list of
2625 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2626 2017. Resolves ticket 21564.
2628 o Minor bugfixes (correctness):
2629 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2630 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2632 Changes in version 0.2.7.8 - 2017-06-08
2633 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2634 remotely crash a hidden service with an assertion failure. Anyone
2635 running a hidden service should upgrade to this version, or to some
2636 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2637 are not affected by TROVE-2017-004.)
2639 o Major bugfixes (hidden service, relay, security):
2640 - Fix a remotely triggerable assertion failure caused by receiving a
2641 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2642 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2645 o Minor features (geoip):
2646 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2649 o Minor bugfixes (correctness):
2650 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2651 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2654 Changes in version 0.2.6.12 - 2017-06-08
2655 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
2656 remotely crash a hidden service with an assertion failure. Anyone
2657 running a hidden service should upgrade to this version, or to some
2658 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2659 are not affected by TROVE-2017-004.)
2661 o Major bugfixes (hidden service, relay, security):
2662 - Fix a remotely triggerable assertion failure caused by receiving a
2663 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2664 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2667 o Minor features (geoip):
2668 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2671 o Minor bugfixes (correctness):
2672 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2673 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2675 Changes in version 0.2.5.14 - 2017-06-08
2676 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
2677 remotely crash a hidden service with an assertion failure. Anyone
2678 running a hidden service should upgrade to this version, or to some
2679 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2680 are not affected by TROVE-2017-004.)
2682 o Major bugfixes (hidden service, relay, security):
2683 - Fix a remotely triggerable assertion failure caused by receiving a
2684 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2685 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2688 o Minor features (geoip):
2689 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2692 o Minor bugfixes (correctness):
2693 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2694 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2696 Changes in version 0.2.4.29 - 2017-06-08
2697 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
2698 remotely crash a hidden service with an assertion failure. Anyone
2699 running a hidden service should upgrade to this version, or to some
2700 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2701 are not affected by TROVE-2017-004.)
2703 o Major bugfixes (hidden service, relay, security):
2704 - Fix a remotely triggerable assertion failure caused by receiving a
2705 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2706 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2709 o Minor features (geoip):
2710 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2713 o Minor bugfixes (correctness):
2714 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2715 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2718 Changes in version 0.3.1.2-alpha - 2017-05-26
2719 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
2720 fixes a few bugs found while testing 0.3.1.1-alpha, including a
2721 memory corruption bug that affected relay stability.
2723 o Major bugfixes (crash, relay):
2724 - Fix a memory-corruption bug in relays that set MyFamily.
2725 Previously, they would double-free MyFamily elements when making
2726 the next descriptor or when changing their configuration. Fixes
2727 bug 22368; bugfix on 0.3.1.1-alpha.
2729 o Minor bugfixes (logging):
2730 - Log a better message when a directory authority replies to an
2731 upload with an unexpected status code. Fixes bug 11121; bugfix
2734 o Minor bugfixes (memory leak, directory authority):
2735 - When directory authorities reject a router descriptor due to
2736 keypinning, free the router descriptor rather than leaking the
2737 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2740 Changes in version 0.3.1.1-alpha - 2017-05-22
2741 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
2742 reduces the bandwidth usage for Tor's directory protocol, adds some
2743 basic padding to resist netflow-based traffic analysis and to serve as
2744 the basis of other padding in the future, and adds rust support to the
2747 It also contains numerous other small features and improvements to
2748 security, correctness, and performance.
2750 Below are the changes since 0.3.0.7.
2752 o Major features (directory protocol):
2753 - Tor relays and authorities can now serve clients an abbreviated
2754 version of the consensus document, containing only the changes
2755 since an older consensus document that the client holds. Clients
2756 now request these documents when available. When both client and
2757 server use this new protocol, they will use far less bandwidth (up
2758 to 94% less) to keep the client's consensus up-to-date. Implements
2759 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
2760 - Tor can now compress directory traffic with lzma or with zstd
2761 compression algorithms, which can deliver better bandwidth
2762 performance. Because lzma is computationally expensive, it's only
2763 used for documents that can be compressed once and served many
2764 times. Support for these algorithms requires that tor is built
2765 with the libzstd and/or liblzma libraries available. Implements
2766 proposal 278; closes ticket 21662.
2767 - Relays now perform the more expensive compression operations, and
2768 consensus diff generation, in worker threads. This separation
2769 avoids delaying the main thread when a new consensus arrives.
2771 o Major features (experimental):
2772 - Tor can now build modules written in Rust. To turn this on, pass
2773 the "--enable-rust" flag to the configure script. It's not time to
2774 get excited yet: currently, there is no actual Rust functionality
2775 beyond some simple glue code, and a notice at startup to tell you
2776 that Rust is running. Still, we hope that programmers and
2777 packagers will try building Tor with Rust support, so that we can
2778 find issues and solve portability problems. Closes ticket 22106.
2780 o Major features (traffic analysis resistance):
2781 - Connections between clients and relays now send a padding cell in
2782 each direction every 1.5 to 9.5 seconds (tunable via consensus
2783 parameters). This padding will not resist specialized
2784 eavesdroppers, but it should be enough to make many ISPs' routine
2785 network flow logging less useful in traffic analysis against
2788 Padding is negotiated using Tor's link protocol, so both relays
2789 and clients must upgrade for this to take effect. Clients may
2790 still send padding despite the relay's version by setting
2791 ConnectionPadding 1 in torrc, and may disable padding by setting
2792 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
2793 users with the torrc option ReducedConnectionPadding. Implements
2794 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
2795 - Relays will publish 24 hour totals of padding and non-padding cell
2796 counts to their extra-info descriptors, unless PaddingStatistics 0
2797 is set in torrc. These 24 hour totals are also rounded to
2800 o Major bugfixes (connection usage):
2801 - We use NETINFO cells to try to determine if both relays involved
2802 in a connection will agree on the canonical status of that
2803 connection. We prefer the connections where this is the case for
2804 extend cells, and try to close connections where relays disagree
2805 on their canonical status early. Also, we now prefer the oldest
2806 valid connection for extend cells. These two changes should reduce
2807 the number of long-term connections that are kept open between
2808 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
2809 - Relays now log hourly statistics (look for
2810 "channel_check_for_duplicates" lines) on the total number of
2811 connections to other relays. If the number of connections per
2812 relay is unexpectedly large, this log message is at notice level.
2813 Otherwise it is at info.
2815 o Major bugfixes (entry guards):
2816 - Don't block bootstrapping when a primary bridge is offline and we
2817 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2818 21969; bugfix on 0.3.0.3-alpha.
2820 o Major bugfixes (linux TPROXY support):
2821 - Fix a typo that had prevented TPROXY-based transparent proxying
2822 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2823 Patch from "d4fq0fQAgoJ".
2825 o Minor features (security, windows):
2826 - Enable a couple of pieces of Windows hardening: one
2827 (HeapEnableTerminationOnCorruption) that has been on-by-default
2828 since Windows 8, and unavailable before Windows 7; and one
2829 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2830 affect us, but shouldn't do any harm. Closes ticket 21953.
2832 o Minor features (config options):
2833 - Allow "%include" directives in torrc configuration files. These
2834 directives import the settings from other files, or from all the
2835 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
2836 - Make SAVECONF return an error when overwriting a torrc that has
2837 includes. Using SAVECONF with the FORCE option will allow it to
2838 overwrite torrc even if includes are used. Related to ticket 1922.
2839 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
2840 will work without the FORCE option. Related to ticket 1922.
2842 o Minor features (controller):
2843 - Warn the first time that a controller requests data in the long-
2844 deprecated 'GETINFO network-status' format. Closes ticket 21703.
2846 o Minor features (defaults):
2847 - The default value for UseCreateFast is now 0: clients which
2848 haven't yet received a consensus document will now use a proper
2849 ntor handshake to talk to their directory servers whenever they
2850 can. Closes ticket 21407.
2851 - Onion key rotation and expiry intervals are now defined as a
2852 network consensus parameter, per proposal 274. The default
2853 lifetime of an onion key is increased from 7 to 28 days. Old onion
2854 keys will expire after 7 days by default. This change will make
2855 consensus diffs much smaller, and save significant bandwidth.
2856 Closes ticket 21641.
2858 o Minor features (fallback directory list):
2859 - Update the fallback directory mirror whitelist and blacklist based
2860 on operator emails. Closes task 21121.
2861 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2862 December 2016 (of which ~126 were still functional) with a list of
2863 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2864 2017. Resolves ticket 21564.
2866 o Minor features (hidden services, logging):
2867 - Log a message when a hidden service descriptor has fewer
2868 introduction points than specified in
2869 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
2870 - Log a message when a hidden service reaches its introduction point
2871 circuit limit, and when that limit is reset. Follow up to ticket
2872 21594; closes ticket 21622.
2873 - Warn user if multiple entries in EntryNodes and at least one
2874 HiddenService are used together. Pinning EntryNodes along with a
2875 hidden service can be possibly harmful; for instance see ticket
2876 14917 or 21155. Closes ticket 21155.
2878 o Minor features (linux seccomp2 sandbox):
2879 - We now have a document storage backend compatible with the Linux
2880 seccomp2 sandbox. This backend is used for consensus documents and
2881 diffs between them; in the long term, we'd like to use it for
2882 unparseable directory material too. Closes ticket 21645
2883 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
2884 from 1MB to 16MB. This was necessary with the glibc allocator in
2885 order to allow worker threads to allocate more memory -- which in
2886 turn is necessary because of our new use of worker threads for
2887 compression. Closes ticket 22096.
2889 o Minor features (logging):
2890 - Log files are no longer created world-readable by default.
2891 (Previously, most distributors would store the logs in a non-
2892 world-readable location to prevent inappropriate access. This
2893 change is an extra precaution.) Closes ticket 21729; patch
2896 o Minor features (performance):
2897 - Our Keccak (SHA-3) implementation now accesses memory more
2898 efficiently, especially on little-endian systems. Closes
2900 - Add an O(1) implementation of channel_find_by_global_id(), to
2901 speed some controller functions.
2903 o Minor features (relay, configuration):
2904 - The MyFamily option may now be repeated as many times as desired,
2905 for relays that want to configure large families. Closes ticket
2906 4998; patch by Daniel Pinto.
2908 o Minor features (safety):
2909 - Add an explicit check to extrainfo_parse_entry_from_string() for
2910 NULL inputs. We don't believe this can actually happen, but it may
2911 help silence a warning from the Clang analyzer. Closes
2914 o Minor features (testing):
2915 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
2916 When Tor is compiled with this option, we disable a number of
2917 redundant memory-safety failsafes that are intended to stop bugs
2918 from becoming security issues. This makes it easier to hunt for
2919 bugs that would be security issues without the failsafes turned
2920 on. Closes ticket 21439.
2921 - Add a general event-tracing instrumentation support to Tor. This
2922 subsystem will enable developers and researchers to add fine-
2923 grained instrumentation to their Tor instances, for use when
2924 examining Tor network performance issues. There are no trace
2925 events yet, and event-tracing is off by default unless enabled at
2926 compile time. Implements ticket 13802.
2927 - Improve our version parsing tests: add tests for typical version
2928 components, add tests for invalid versions, including numeric
2929 range and non-numeric prefixes. Unit tests 21278, 21450, and
2930 21507. Partially implements 21470.
2932 o Minor bugfixes (bandwidth accounting):
2933 - Roll over monthly accounting at the configured hour and minute,
2934 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2935 Found by Andrey Karpov with PVS-Studio.
2937 o Minor bugfixes (code correctness):
2938 - Accurately identify client connections by their lack of peer
2939 authentication. This means that we bail out earlier if asked to
2940 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
2943 o Minor bugfixes (configuration):
2944 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
2945 bug 22252; bugfix on 0.2.9.3-alpha.
2947 o Minor bugfixes (connection lifespan):
2948 - Allow more control over how long TLS connections are kept open:
2949 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
2950 single option called CircuitsAvailableTimeout. Also, allow the
2951 consensus to control the default values for both this preference
2952 and the lifespan of relay-to-relay connections. Fixes bug 17592;
2953 bugfix on 0.2.5.5-alpha.
2954 - Increase the initial circuit build timeout testing frequency, to
2955 help ensure that ReducedConnectionPadding clients finish learning
2956 a timeout before their orconn would expire. The initial testing
2957 rate was set back in the days of TAP and before the Tor Browser
2958 updater, when we had to be much more careful about new clients
2959 making lots of circuits. With this change, a circuit build timeout
2960 is learned in about 15-20 minutes, instead of 100-120 minutes.
2962 o Minor bugfixes (controller):
2963 - GETINFO onions/current and onions/detached no longer respond with
2964 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
2965 - Trigger HS descriptor events on the control port when the client
2966 fails to pick a hidden service directory for a hidden service.
2967 This can happen if all the hidden service directories are in
2968 ExcludeNodes, or they have all been queried within the last 15
2969 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
2971 o Minor bugfixes (directory authority):
2972 - When rejecting a router descriptor for running an obsolete version
2973 of Tor without ntor support, warn about the obsolete tor version,
2974 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2975 - Prevent the shared randomness subsystem from asserting when
2976 initialized by a bridge authority with an incomplete configuration
2977 file. Fixes bug 21586; bugfix on 0.2.9.8.
2979 o Minor bugfixes (exit-side DNS):
2980 - Fix an untriggerable assertion that checked the output of a
2981 libevent DNS error, so that the assertion actually behaves as
2982 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
2983 Karpov using PVS-Studio.
2985 o Minor bugfixes (fallback directories):
2986 - Make the usage example in updateFallbackDirs.py actually work, and
2987 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
2988 - Decrease the guard flag average required to be a fallback. This
2989 allows us to keep relays that have their guard flag removed when
2990 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2991 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
2992 bugfix on 0.2.8.1-alpha.
2993 - Make sure fallback directory mirrors have the same address, port,
2994 and relay identity key for at least 30 days before they are
2995 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2997 o Minor bugfixes (hidden services):
2998 - Stop printing a cryptic warning when a hidden service gets a
2999 request to connect to a virtual port that it hasn't configured.
3000 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
3001 - Simplify hidden service descriptor creation by using an existing
3002 flag to check if an introduction point is established. Fixes bug
3003 21599; bugfix on 0.2.7.2-alpha.
3005 o Minor bugfixes (memory leak):
3006 - Fix a small memory leak at exit from the backtrace handler code.
3007 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
3009 o Minor bugfixes (protocol, logging):
3010 - Downgrade a log statement about unexpected relay cells from "bug"
3011 to "protocol warning", because there is at least one use case
3012 where it can be triggered by a buggy tor implementation. Fixes bug
3013 21293; bugfix on 0.1.1.14-alpha.
3015 o Minor bugfixes (testing):
3016 - Use unbuffered I/O for utility functions around the
3017 process_handle_t type. This fixes unit test failures reported on
3018 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
3019 - Make display of captured unit test log messages consistent. Fixes
3020 bug 21510; bugfix on 0.2.9.3-alpha.
3021 - Make test-network.sh always call chutney's test-network.sh.
3022 Previously, this only worked on systems which had bash installed,
3023 due to some bash-specific code in the script. Fixes bug 19699;
3024 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
3026 o Minor bugfixes (voting consistency):
3027 - Reject version numbers with non-numeric prefixes (such as +, -, or
3028 whitespace). Disallowing whitespace prevents differential version
3029 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3030 and part of 21508; bugfix on 0.0.8pre1.
3032 o Minor bugfixes (windows, relay):
3033 - Resolve "Failure from drain_fd: No error" warnings on Windows
3034 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
3036 o Code simplification and refactoring:
3037 - Break up the 630-line function connection_dir_client_reached_eof()
3038 into a dozen smaller functions. This change should help
3039 maintainability and readability of the client directory code.
3040 - Isolate our use of the openssl headers so that they are only
3041 included from our crypto wrapper modules, and from tests that
3042 examine those modules' internals. Closes ticket 21841.
3043 - Simplify our API to launch directory requests, making it more
3044 extensible and less error-prone. Now it's easier to add extra
3045 headers to directory requests. Closes ticket 21646.
3046 - Our base64 decoding functions no longer overestimate the output
3047 space that they need when parsing unpadded inputs. Closes
3049 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
3050 Resolves ticket 22213.
3051 - The logic that directory caches use to spool request to clients,
3052 serving them one part at a time so as not to allocate too much
3053 memory, has been refactored for consistency. Previously there was
3054 a separate spooling implementation per type of spoolable data. Now
3055 there is one common spooling implementation, with extensible data
3056 types. Closes ticket 21651.
3057 - Tor's compression module now supports multiple backends. Part of
3058 the implementation for proposal 278; closes ticket 21663.
3061 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
3062 Closes ticket 21873.
3063 - Correct documentation about the default DataDirectory value.
3064 Closes ticket 21151.
3065 - Document the default behavior of NumEntryGuards and
3066 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
3068 - Document key=value pluggable transport arguments for Bridge lines
3069 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
3070 - Note that bandwidth-limiting options don't affect TCP headers or
3071 DNS. Closes ticket 17170.
3073 o Removed features (configuration options, all in ticket 22060):
3074 - These configuration options are now marked Obsolete, and no longer
3075 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
3076 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
3077 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
3078 in 0.2.9.2-alpha and have now been removed. The previous default
3079 behavior is now always chosen; the previous (less secure) non-
3080 default behavior is now unavailable.
3081 - CloseHSClientCircuitsImmediatelyOnTimeout and
3082 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
3083 0.2.9.2-alpha and now have been removed. HS circuits never close
3084 on circuit build timeout; they have a longer timeout period.
3085 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
3086 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
3087 (and others) to configure listen-only and advertise-only addresses.
3089 o Removed features (tools):
3090 - We've removed the tor-checkkey tool from src/tools. Long ago, we
3091 used it to help people detect RSA keys that were generated by
3092 versions of Debian affected by CVE-2008-0166. But those keys have
3093 been out of circulation for ages, and this tool is no longer
3094 required. Closes ticket 21842.
3097 Changes in version 0.3.0.7 - 2017-05-15
3098 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
3099 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
3100 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
3101 clients are not affected.
3103 o Major bugfixes (hidden service directory, security):
3104 - Fix an assertion failure in the hidden service directory code, which
3105 could be used by an attacker to remotely cause a Tor relay process to
3106 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
3107 should upgrade. This security issue is tracked as TROVE-2017-002.
3108 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
3111 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3114 o Minor features (future-proofing):
3115 - Tor no longer refuses to download microdescriptors or descriptors
3116 if they are listed as "published in the future". This change will
3117 eventually allow us to stop listing meaningful "published" dates
3118 in microdescriptor consensuses, and thereby allow us to reduce the
3119 resources required to download consensus diffs by over 50%.
3120 Implements part of ticket 21642; implements part of proposal 275.
3122 o Minor bugfixes (Linux seccomp2 sandbox):
3123 - The getpid() system call is now permitted under the Linux seccomp2
3124 sandbox, to avoid crashing with versions of OpenSSL (and other
3125 libraries) that attempt to learn the process's PID by using the
3126 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3130 Changes in version 0.3.0.6 - 2017-04-26
3131 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
3133 With the 0.3.0 series, clients and relays now use Ed25519 keys to
3134 authenticate their link connections to relays, rather than the old
3135 RSA1024 keys that they used before. (Circuit crypto has been
3136 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
3137 the guard selection and replacement algorithm to behave more robustly
3138 in the presence of unreliable networks, and to resist guard-
3141 This series also includes numerous other small features and bugfixes,
3142 along with more groundwork for the upcoming hidden-services revamp.
3144 Per our stable release policy, we plan to support the Tor 0.3.0
3145 release series for at least the next nine months, or for three months
3146 after the first stable release of the 0.3.1 series: whichever is
3147 longer. If you need a release with long-term support, we recommend
3148 that you stay with the 0.2.9 series.
3150 Below are the changes since 0.3.0.5-rc. For a list of all changes
3151 since 0.2.9, see the ReleaseNotes file.
3153 o Minor features (geoip):
3154 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
3157 o Minor bugfixes (control port):
3158 - The GETINFO extra-info/digest/<digest> command was broken because
3159 of a wrong base16 decode return value check, introduced when
3160 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3162 o Minor bugfixes (crash prevention):
3163 - Fix a (currently untriggerable, but potentially dangerous) crash
3164 bug when base32-encoding inputs whose sizes are not a multiple of
3165 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
3168 Changes in version 0.3.0.5-rc - 2017-04-05
3169 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
3170 0.3.0 release series.
3172 This is the second release candidate in the Tor 0.3.0 series, and has
3173 much fewer changes than the first. If we find no new bugs or
3174 regressions here, the first stable 0.3.0 release will be nearly
3177 o Major bugfixes (crash, directory connections):
3178 - Fix a rare crash when sending a begin cell on a circuit whose
3179 linked directory connection had already been closed. Fixes bug
3180 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3182 o Major bugfixes (guard selection):
3183 - Fix a guard selection bug where Tor would refuse to bootstrap in
3184 some cases if the user swapped a bridge for another bridge in
3185 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
3186 Reported by "torvlnt33r".
3188 o Minor features (geoip):
3189 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
3192 o Minor bugfix (compilation):
3193 - Fix a warning when compiling hs_service.c. Previously, it had no
3194 exported symbols when compiled for libor.a, resulting in a
3195 compilation warning from clang. Fixes bug 21825; bugfix
3198 o Minor bugfixes (hidden services):
3199 - Make hidden services check for failed intro point connections,
3200 even when they have exceeded their intro point creation limit.
3201 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
3202 - Make hidden services with 8 to 10 introduction points check for
3203 failed circuits immediately after startup. Previously, they would
3204 wait for 5 minutes before performing their first checks. Fixes bug
3205 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
3207 o Minor bugfixes (memory leaks):
3208 - Fix a memory leak when using GETCONF on a port option. Fixes bug
3209 21682; bugfix on 0.3.0.3-alpha.
3211 o Minor bugfixes (relay):
3212 - Avoid a double-marked-circuit warning that could happen when we
3213 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3216 o Minor bugfixes (tests):
3217 - Run the entry_guard_parse_from_state_full() test with the time set
3218 to a specific date. (The guard state that this test was parsing
3219 contained guards that had expired since the test was first
3220 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
3223 - Update the description of the directory server options in the
3224 manual page, to clarify that a relay no longer needs to set
3225 DirPort in order to be a directory cache. Closes ticket 21720.
3229 Changes in version 0.2.8.13 - 2017-03-03
3230 Tor 0.2.8.13 backports a security fix from later Tor
3231 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
3232 this release, if for some reason they cannot upgrade to a later
3233 release series, and if they build Tor with the --enable-expensive-hardening
3236 Note that support for Tor 0.2.8.x is ending next year: we will not issue
3237 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
3238 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3240 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3241 - Fix an integer underflow bug when comparing malformed Tor
3242 versions. This bug could crash Tor when built with
3243 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3244 0.2.9.8, which were built with -ftrapv by default. In other cases
3245 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3246 on 0.0.8pre1. Found by OSS-Fuzz.
3248 o Minor features (geoip):
3249 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3253 Changes in version 0.2.7.7 - 2017-03-03
3254 Tor 0.2.7.7 backports a number of security fixes from later Tor
3255 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
3256 this release, if for some reason they cannot upgrade to a later
3259 Note that support for Tor 0.2.7.x is ending this year: we will not issue
3260 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
3261 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3263 o Directory authority changes (backport from 0.2.8.5-rc):
3264 - Urras is no longer a directory authority. Closes ticket 19271.
3266 o Directory authority changes (backport from 0.2.9.2-alpha):
3267 - The "Tonga" bridge authority has been retired; the new bridge
3268 authority is "Bifroest". Closes tickets 19728 and 19690.
3270 o Directory authority key updates (backport from 0.2.8.1-alpha):
3271 - Update the V3 identity key for the dannenberg directory authority:
3272 it was changed on 18 November 2015. Closes task 17906. Patch
3275 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3276 - Fix a bug in parsing that could cause clients to read a single
3277 byte past the end of an allocated region. This bug could be used
3278 to cause hardened clients (built with --enable-expensive-hardening)
3279 to crash if they tried to visit a hostile hidden service. Non-
3280 hardened clients are only affected depending on the details of
3281 their platform's memory allocator. Fixes bug 21018; bugfix on
3282 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3283 2016-12-002 and as CVE-2016-1254.
3285 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3286 - Stop a crash that could occur when a client running with DNSPort
3287 received a query with multiple address types, and the first
3288 address type was not supported. Found and fixed by Scott Dial.
3289 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3290 - Prevent a class of security bugs caused by treating the contents
3291 of a buffer chunk as if they were a NUL-terminated string. At
3292 least one such bug seems to be present in all currently used
3293 versions of Tor, and would allow an attacker to remotely crash
3294 most Tor instances, especially those compiled with extra compiler
3295 hardening. With this defense in place, such bugs can't crash Tor,
3296 though we should still fix them as they occur. Closes ticket
3297 20384 (TROVE-2016-10-001).
3299 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3300 - Avoid a difficult-to-trigger heap corruption attack when extending
3301 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3302 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3303 Reported by Guido Vranken.
3305 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3306 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3307 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3309 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3310 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3311 pointer to the previous (uninitialized) key value. The impact here
3312 should be limited to a difficult-to-trigger crash, if OpenSSL is
3313 running an engine that makes key generation failures possible, or
3314 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3315 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3318 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3319 - Fix an integer underflow bug when comparing malformed Tor
3320 versions. This bug could crash Tor when built with
3321 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3322 0.2.9.8, which were built with -ftrapv by default. In other cases
3323 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3324 on 0.0.8pre1. Found by OSS-Fuzz.
3326 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3327 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3328 zero size. Check size argument to memwipe() for underflow. Fixes
3329 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3332 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3333 - Make Tor survive errors involving connections without a
3334 corresponding event object. Previously we'd fail with an
3335 assertion; now we produce a log message. Related to bug 16248.
3337 o Minor features (geoip):
3338 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3342 Changes in version 0.2.6.11 - 2017-03-03
3343 Tor 0.2.6.11 backports a number of security fixes from later Tor
3344 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
3345 this release, if for some reason they cannot upgrade to a later
3348 Note that support for Tor 0.2.6.x is ending this year: we will not issue
3349 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
3350 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3352 o Directory authority changes (backport from 0.2.8.5-rc):
3353 - Urras is no longer a directory authority. Closes ticket 19271.
3355 o Directory authority changes (backport from 0.2.9.2-alpha):
3356 - The "Tonga" bridge authority has been retired; the new bridge
3357 authority is "Bifroest". Closes tickets 19728 and 19690.
3359 o Directory authority key updates (backport from 0.2.8.1-alpha):
3360 - Update the V3 identity key for the dannenberg directory authority:
3361 it was changed on 18 November 2015. Closes task 17906. Patch
3364 o Major features (security fixes, backport from 0.2.9.4-alpha):
3365 - Prevent a class of security bugs caused by treating the contents
3366 of a buffer chunk as if they were a NUL-terminated string. At
3367 least one such bug seems to be present in all currently used
3368 versions of Tor, and would allow an attacker to remotely crash
3369 most Tor instances, especially those compiled with extra compiler
3370 hardening. With this defense in place, such bugs can't crash Tor,
3371 though we should still fix them as they occur. Closes ticket
3372 20384 (TROVE-2016-10-001).
3374 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3375 - Fix a bug in parsing that could cause clients to read a single
3376 byte past the end of an allocated region. This bug could be used
3377 to cause hardened clients (built with --enable-expensive-hardening)
3378 to crash if they tried to visit a hostile hidden service. Non-
3379 hardened clients are only affected depending on the details of
3380 their platform's memory allocator. Fixes bug 21018; bugfix on
3381 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3382 2016-12-002 and as CVE-2016-1254.
3384 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3385 - Stop a crash that could occur when a client running with DNSPort
3386 received a query with multiple address types, and the first
3387 address type was not supported. Found and fixed by Scott Dial.
3388 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3390 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3391 - Fix an error that could cause us to read 4 bytes before the
3392 beginning of an openssl string. This bug could be used to cause
3393 Tor to crash on systems with unusual malloc implementations, or
3394 systems with unusual hardening installed. Fixes bug 17404; bugfix
3397 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3398 - Avoid a difficult-to-trigger heap corruption attack when extending
3399 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3400 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3401 Reported by Guido Vranken.
3403 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3404 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3405 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3407 o Major bugfixes (guard selection, backport from 0.2.7.6):
3408 - Actually look at the Guard flag when selecting a new directory
3409 guard. When we implemented the directory guard design, we
3410 accidentally started treating all relays as if they have the Guard
3411 flag during guard selection, leading to weaker anonymity and worse
3412 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3415 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3416 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3417 pointer to the previous (uninitialized) key value. The impact here
3418 should be limited to a difficult-to-trigger crash, if OpenSSL is
3419 running an engine that makes key generation failures possible, or
3420 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3421 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3424 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3425 - Fix an integer underflow bug when comparing malformed Tor
3426 versions. This bug could crash Tor when built with
3427 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3428 0.2.9.8, which were built with -ftrapv by default. In other cases
3429 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3430 on 0.0.8pre1. Found by OSS-Fuzz.
3432 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3433 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3434 zero size. Check size argument to memwipe() for underflow. Fixes
3435 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3438 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3439 - Make Tor survive errors involving connections without a
3440 corresponding event object. Previously we'd fail with an
3441 assertion; now we produce a log message. Related to bug 16248.
3443 o Minor features (geoip):
3444 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3447 o Minor bugfixes (compilation, backport from 0.2.7.6):
3448 - Fix a compilation warning with Clang 3.6: Do not check the
3449 presence of an address which can never be NULL. Fixes bug 17781.
3452 Changes in version 0.2.5.13 - 2017-03-03
3453 Tor 0.2.5.13 backports a number of security fixes from later Tor
3454 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
3455 this release, if for some reason they cannot upgrade to a later
3458 Note that support for Tor 0.2.5.x is ending next year: we will not issue
3459 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
3460 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3462 o Directory authority changes (backport from 0.2.8.5-rc):
3463 - Urras is no longer a directory authority. Closes ticket 19271.
3465 o Directory authority changes (backport from 0.2.9.2-alpha):
3466 - The "Tonga" bridge authority has been retired; the new bridge
3467 authority is "Bifroest". Closes tickets 19728 and 19690.
3469 o Directory authority key updates (backport from 0.2.8.1-alpha):
3470 - Update the V3 identity key for the dannenberg directory authority:
3471 it was changed on 18 November 2015. Closes task 17906. Patch
3474 o Major features (security fixes, backport from 0.2.9.4-alpha):
3475 - Prevent a class of security bugs caused by treating the contents
3476 of a buffer chunk as if they were a NUL-terminated string. At
3477 least one such bug seems to be present in all currently used
3478 versions of Tor, and would allow an attacker to remotely crash
3479 most Tor instances, especially those compiled with extra compiler
3480 hardening. With this defense in place, such bugs can't crash Tor,
3481 though we should still fix them as they occur. Closes ticket
3482 20384 (TROVE-2016-10-001).
3484 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3485 - Fix a bug in parsing that could cause clients to read a single
3486 byte past the end of an allocated region. This bug could be used
3487 to cause hardened clients (built with --enable-expensive-hardening)
3488 to crash if they tried to visit a hostile hidden service. Non-
3489 hardened clients are only affected depending on the details of
3490 their platform's memory allocator. Fixes bug 21018; bugfix on
3491 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3492 2016-12-002 and as CVE-2016-1254.
3494 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3495 - Stop a crash that could occur when a client running with DNSPort
3496 received a query with multiple address types, and the first
3497 address type was not supported. Found and fixed by Scott Dial.
3498 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3500 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3501 - Fix an error that could cause us to read 4 bytes before the
3502 beginning of an openssl string. This bug could be used to cause
3503 Tor to crash on systems with unusual malloc implementations, or
3504 systems with unusual hardening installed. Fixes bug 17404; bugfix
3507 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3508 - Avoid a difficult-to-trigger heap corruption attack when extending
3509 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3510 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3511 Reported by Guido Vranken.
3513 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3514 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3515 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3517 o Major bugfixes (guard selection, backport from 0.2.7.6):
3518 - Actually look at the Guard flag when selecting a new directory
3519 guard. When we implemented the directory guard design, we
3520 accidentally started treating all relays as if they have the Guard
3521 flag during guard selection, leading to weaker anonymity and worse
3522 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3525 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3526 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3527 pointer to the previous (uninitialized) key value. The impact here
3528 should be limited to a difficult-to-trigger crash, if OpenSSL is
3529 running an engine that makes key generation failures possible, or
3530 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3531 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3534 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3535 - Fix an integer underflow bug when comparing malformed Tor
3536 versions. This bug could crash Tor when built with
3537 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3538 0.2.9.8, which were built with -ftrapv by default. In other cases
3539 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3540 on 0.0.8pre1. Found by OSS-Fuzz.
3542 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3543 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3544 zero size. Check size argument to memwipe() for underflow. Fixes
3545 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3548 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3549 - Make Tor survive errors involving connections without a
3550 corresponding event object. Previously we'd fail with an
3551 assertion; now we produce a log message. Related to bug 16248.
3553 o Minor features (geoip):
3554 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3557 o Minor bugfixes (compilation, backport from 0.2.7.6):
3558 - Fix a compilation warning with Clang 3.6: Do not check the
3559 presence of an address which can never be NULL. Fixes bug 17781.
3561 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
3562 - Check for failures from crypto_early_init, and refuse to continue.
3563 A previous typo meant that we could keep going with an
3564 uninitialized crypto library, and would have OpenSSL initialize
3565 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
3566 when implementing ticket 4900. Patch by "teor".
3568 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3569 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3570 a client authorized hidden service. Fixes bug 15823; bugfix
3574 Changes in version 0.2.4.28 - 2017-03-03
3575 Tor 0.2.4.28 backports a number of security fixes from later Tor
3576 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
3577 this release, if for some reason they cannot upgrade to a later
3580 Note that support for Tor 0.2.4.x is ending soon: we will not issue
3581 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
3582 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
3584 o Directory authority changes (backport from 0.2.8.5-rc):
3585 - Urras is no longer a directory authority. Closes ticket 19271.
3587 o Directory authority changes (backport from 0.2.9.2-alpha):
3588 - The "Tonga" bridge authority has been retired; the new bridge
3589 authority is "Bifroest". Closes tickets 19728 and 19690.
3591 o Directory authority key updates (backport from 0.2.8.1-alpha):
3592 - Update the V3 identity key for the dannenberg directory authority:
3593 it was changed on 18 November 2015. Closes task 17906. Patch
3596 o Major features (security fixes, backport from 0.2.9.4-alpha):
3597 - Prevent a class of security bugs caused by treating the contents
3598 of a buffer chunk as if they were a NUL-terminated string. At
3599 least one such bug seems to be present in all currently used
3600 versions of Tor, and would allow an attacker to remotely crash
3601 most Tor instances, especially those compiled with extra compiler
3602 hardening. With this defense in place, such bugs can't crash Tor,
3603 though we should still fix them as they occur. Closes ticket
3604 20384 (TROVE-2016-10-001).
3606 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3607 - Fix a bug in parsing that could cause clients to read a single
3608 byte past the end of an allocated region. This bug could be used
3609 to cause hardened clients (built with --enable-expensive-hardening)
3610 to crash if they tried to visit a hostile hidden service. Non-
3611 hardened clients are only affected depending on the details of
3612 their platform's memory allocator. Fixes bug 21018; bugfix on
3613 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3614 2016-12-002 and as CVE-2016-1254.
3616 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3617 - Fix an error that could cause us to read 4 bytes before the
3618 beginning of an openssl string. This bug could be used to cause
3619 Tor to crash on systems with unusual malloc implementations, or
3620 systems with unusual hardening installed. Fixes bug 17404; bugfix
3623 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3624 - Avoid a difficult-to-trigger heap corruption attack when extending
3625 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3626 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3627 Reported by Guido Vranken.
3629 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3630 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3631 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3633 o Major bugfixes (guard selection, backport from 0.2.7.6):
3634 - Actually look at the Guard flag when selecting a new directory
3635 guard. When we implemented the directory guard design, we
3636 accidentally started treating all relays as if they have the Guard
3637 flag during guard selection, leading to weaker anonymity and worse
3638 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3641 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3642 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3643 pointer to the previous (uninitialized) key value. The impact here
3644 should be limited to a difficult-to-trigger crash, if OpenSSL is
3645 running an engine that makes key generation failures possible, or
3646 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3647 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3650 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3651 - Fix an integer underflow bug when comparing malformed Tor
3652 versions. This bug could crash Tor when built with
3653 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3654 0.2.9.8, which were built with -ftrapv by default. In other cases
3655 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3656 on 0.0.8pre1. Found by OSS-Fuzz.
3658 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3659 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3660 zero size. Check size argument to memwipe() for underflow. Fixes
3661 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3664 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3665 - Make Tor survive errors involving connections without a
3666 corresponding event object. Previously we'd fail with an
3667 assertion; now we produce a log message. Related to bug 16248.
3669 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
3670 - Make it harder for attackers to overload hidden services with
3671 introductions, by blocking multiple introduction requests on the
3672 same circuit. Resolves ticket 15515.
3674 o Minor features (geoip):
3675 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3678 o Minor bugfixes (compilation, backport from 0.2.7.6):
3679 - Fix a compilation warning with Clang 3.6: Do not check the
3680 presence of an address which can never be NULL. Fixes bug 17781.
3682 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3683 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3684 a client authorized hidden service. Fixes bug 15823; bugfix
3688 Changes in version 0.3.0.4-rc - 2017-03-01
3689 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
3690 0.3.0 release series, and introduces a few reliability features to
3691 keep them from coming back.
3693 This is the first release candidate in the Tor 0.3.0 series. If we
3694 find no new bugs or regressions here, the first stable 0.3.0 release
3695 will be nearly identical to it.
3697 o Major bugfixes (bridges):
3698 - When the same bridge is configured multiple times with the same
3699 identity, but at different address:port combinations, treat those
3700 bridge instances as separate guards. This fix restores the ability
3701 of clients to configure the same bridge with multiple pluggable
3702 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
3704 o Major bugfixes (hidden service directory v3):
3705 - Stop crashing on a failed v3 hidden service descriptor lookup
3706 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
3708 o Major bugfixes (parsing):
3709 - When parsing a malformed content-length field from an HTTP
3710 message, do not read off the end of the buffer. This bug was a
3711 potential remote denial-of-service attack against Tor clients and
3712 relays. A workaround was released in October 2016, to prevent this
3713 bug from crashing Tor. This is a fix for the underlying issue,
3714 which should no longer matter (if you applied the earlier patch).
3715 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
3716 using AFL (http://lcamtuf.coredump.cx/afl/).
3717 - Fix an integer underflow bug when comparing malformed Tor
3718 versions. This bug could crash Tor when built with
3719 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3720 0.2.9.8, which were built with -ftrapv by default. In other cases
3721 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3722 on 0.0.8pre1. Found by OSS-Fuzz.
3724 o Minor feature (protocol versioning):
3725 - Add new protocol version for proposal 224. HSIntro now advertises
3726 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
3728 o Minor features (directory authorities):
3729 - Directory authorities now reject descriptors that claim to be
3730 malformed versions of Tor. Helps prevent exploitation of
3732 - Reject version numbers with components that exceed INT32_MAX.
3733 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3734 Fixes bug 21450; bugfix on 0.0.8pre1.
3735 - Directory authorities now reject relays running versions
3736 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
3737 suffer from bug 20499 and don't keep their consensus cache
3738 up-to-date. Resolves ticket 20509.
3740 o Minor features (geoip):
3741 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3744 o Minor features (reliability, crash):
3745 - Try better to detect problems in buffers where they might grow (or
3746 think they have grown) over 2 GB in size. Diagnostic for
3749 o Minor features (testing):
3750 - During 'make test-network-all', if tor logs any warnings, ask
3751 chutney to output them. Requires a recent version of chutney with
3752 the 21572 patch. Implements 21570.
3754 o Minor bugfixes (certificate expiration time):
3755 - Avoid using link certificates that don't become valid till some
3756 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
3758 o Minor bugfixes (code correctness):
3759 - Repair a couple of (unreachable or harmless) cases of the risky
3760 comparison-by-subtraction pattern that caused bug 21278.
3761 - Remove a redundant check for the UseEntryGuards option from the
3762 options_transition_affects_guards() function. Fixes bug 21492;
3763 bugfix on 0.3.0.1-alpha.
3765 o Minor bugfixes (directory mirrors):
3766 - Allow relays to use directory mirrors without a DirPort: these
3767 relays need to be contacted over their ORPorts using a begindir
3768 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
3769 - Clarify the message logged when a remote relay is unexpectedly
3770 missing an ORPort or DirPort: users were confusing this with a
3771 local port. Fixes another case of bug 20711; bugfix
3774 o Minor bugfixes (guards):
3775 - Don't warn about a missing guard state on timeout-measurement
3776 circuits: they aren't supposed to be using guards. Fixes an
3777 instance of bug 21007; bugfix on 0.3.0.1-alpha.
3778 - Silence a BUG() warning when attempting to use a guard whose
3779 descriptor we don't know, and make this scenario less likely to
3780 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
3782 o Minor bugfixes (hidden service):
3783 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
3784 cells. Previously, we were using sizeof() on a pointer, instead of
3785 the real destination buffer. Fortunately, that value was only used
3786 to double-check that there was enough room--which was already
3787 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
3789 o Minor bugfixes (testing):
3790 - Fix Raspbian build issues related to missing socket errno in
3791 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
3793 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
3794 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
3795 - Use bash in src/test/test-network.sh. This ensures we reliably
3796 call chutney's newer tools/test-network.sh when available. Fixes
3797 bug 21562; bugfix on 0.2.9.1-alpha.
3800 - Small fixes to the fuzzing documentation. Closes ticket 21472.
3803 Changes in version 0.2.9.10 - 2017-03-01
3804 Tor 0.2.9.10 backports a security fix from later Tor release. It also
3805 includes fixes for some major issues affecting directory authorities,
3806 LibreSSL compatibility, and IPv6 correctness.
3808 The Tor 0.2.9.x release series is now marked as a long-term-support
3809 series. We intend to backport security fixes to 0.2.9.x until at
3810 least January of 2020.
3812 o Major bugfixes (directory authority, 0.3.0.3-alpha):
3813 - During voting, when marking a relay as a probable sybil, do not
3814 clear its BadExit flag: sybils can still be bad in other ways
3815 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3818 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
3819 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3820 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3821 exit policy rejects that port on more than an IPv6 /16 of
3822 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3823 which rejected a relay's own IPv6 address by default. Fixes bug
3824 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3826 o Major bugfixes (parsing, also in 0.3.0.4-rc):
3827 - Fix an integer underflow bug when comparing malformed Tor
3828 versions. This bug could crash Tor when built with
3829 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3830 0.2.9.8, which were built with -ftrapv by default. In other cases
3831 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3832 on 0.0.8pre1. Found by OSS-Fuzz.
3834 o Minor features (directory authorities, also in 0.3.0.4-rc):
3835 - Directory authorities now reject descriptors that claim to be
3836 malformed versions of Tor. Helps prevent exploitation of
3838 - Reject version numbers with components that exceed INT32_MAX.
3839 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3840 Fixes bug 21450; bugfix on 0.0.8pre1.
3842 o Minor features (geoip):
3843 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3846 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
3847 - Autoconf now checks to determine if OpenSSL structures are opaque,
3848 instead of explicitly checking for OpenSSL version numbers. Part
3850 - Support building with recent LibreSSL code that uses opaque
3851 structures. Closes ticket 21359.
3853 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
3854 - Repair a couple of (unreachable or harmless) cases of the risky
3855 comparison-by-subtraction pattern that caused bug 21278.
3857 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
3858 - The tor-resolve command line tool now rejects hostnames over 255
3859 characters in length. Previously, it would silently truncate them,
3860 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3861 Patch by "junglefowl".
3864 Changes in version 0.3.0.3-alpha - 2017-02-03
3865 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
3866 0.3.0.x development series, including some that could cause
3867 authorities to behave badly. There is also a fix for a longstanding
3868 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
3869 includes some smaller features and bugfixes.
3871 The Tor 0.3.0.x release series is now in patch-freeze: no additional
3872 features will be considered for inclusion in 0.3.0.x. We suspect that
3873 some bugs will probably remain, however, and we encourage people to
3876 o Major bugfixes (directory authority):
3877 - During voting, when marking a relay as a probable sybil, do not
3878 clear its BadExit flag: sybils can still be bad in other ways
3879 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3881 - When deciding whether we have just found a router to be reachable,
3882 do not penalize it for not having performed an Ed25519 link
3883 handshake if it does not claim to support an Ed25519 handshake.
3884 Previously, we would treat such relays as non-running. Fixes bug
3885 21107; bugfix on 0.3.0.1-alpha.
3887 o Major bugfixes (entry guards):
3888 - Stop trying to build circuits through entry guards for which we
3889 have no descriptor. Also, stop crashing in the case that we *do*
3890 accidentally try to build a circuit in such a state. Fixes bug
3891 21242; bugfix on 0.3.0.1-alpha.
3893 o Major bugfixes (IPv6 Exits):
3894 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3895 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3896 exit policy rejects that port on more than an IPv6 /16 of
3897 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3898 which rejected a relay's own IPv6 address by default. Fixes bug
3899 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3901 o Minor feature (client):
3902 - Enable IPv6 traffic on the SocksPort by default. To disable this,
3903 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
3905 o Minor feature (fallback scripts):
3906 - Add a check_existing mode to updateFallbackDirs.py, which checks
3907 if fallbacks in the hard-coded list are working. Closes ticket
3908 20174. Patch by haxxpop.
3910 o Minor features (ciphersuite selection):
3911 - Clients now advertise a list of ciphersuites closer to the ones
3912 preferred by Firefox. Closes part of ticket 15426.
3913 - Allow relays to accept a wider range of ciphersuites, including
3914 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
3916 o Minor features (controller, configuration):
3917 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
3918 and so on, now comes with a __*Port variant that will not be saved
3919 to the torrc file by the controller's SAVECONF command. This
3920 change allows TorBrowser to set up a single-use domain socket for
3921 each time it launches Tor. Closes ticket 20956.
3922 - The GETCONF command can now query options that may only be
3923 meaningful in context-sensitive lists. This allows the controller
3924 to query the mixed SocksPort/__SocksPort style options introduced
3925 in feature 20956. Implements ticket 21300.
3927 o Minor features (portability, compilation):
3928 - Autoconf now checks to determine if OpenSSL structures are opaque,
3929 instead of explicitly checking for OpenSSL version numbers. Part
3931 - Support building with recent LibreSSL code that uses opaque
3932 structures. Closes ticket 21359.
3934 o Minor features (relay):
3935 - We now allow separation of exit and relay traffic to different
3936 source IP addresses, using the OutboundBindAddressExit and
3937 OutboundBindAddressOR options respectively. Closes ticket 17975.
3938 Written by Michael Sonntag.
3940 o Minor bugfix (logging):
3941 - Don't recommend the use of Tor2web in non-anonymous mode.
3942 Recommending Tor2web is a bad idea because the client loses all
3943 anonymity. Tor2web should only be used in specific cases by users
3944 who *know* and understand the issues. Fixes bug 21294; bugfix
3947 o Minor bugfixes (client):
3948 - Always recover from failures in extend_info_from_node(), in an
3949 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
3950 bugfix on 0.2.3.1-alpha.
3952 o Minor bugfixes (client, entry guards):
3953 - Fix a bug warning (with backtrace) when we fail a channel that
3954 circuits to fallback directories on it. Fixes bug 21128; bugfix
3956 - Fix a spurious bug warning (with backtrace) when removing an
3957 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
3958 - Fix a bug of the new guard algorithm where tor could stall for up
3959 to 10 minutes before retrying a guard after a long period of no
3960 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
3961 - Do not try to build circuits until we have descriptors for our
3962 primary entry guards. Related to fix for bug 21242.
3964 o Minor bugfixes (configure, autoconf):
3965 - Rename the configure option --enable-expensive-hardening to
3966 --enable-fragile-hardening. Expensive hardening makes the tor
3967 daemon abort when some kinds of issues are detected. Thus, it
3968 makes tor more at risk of remote crashes but safer against RCE or
3969 heartbleed bug category. We now try to explain this issue in a
3970 message from the configure script. Fixes bug 21290; bugfix
3973 o Minor bugfixes (controller):
3974 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
3975 20824; bugfix on 0.3.0.1-alpha.
3977 o Minor bugfixes (hidden service):
3978 - Clean up the code for expiring intro points with no associated
3979 circuits. It was causing, rarely, a service with some expiring
3980 introduction points to not open enough additional introduction
3981 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
3982 - Stop setting the torrc option HiddenServiceStatistics to "0" just
3983 because we're not a bridge or relay. Instead, we preserve whatever
3984 value the user set (or didn't set). Fixes bug 21150; bugfix
3986 - Resolve two possible underflows which could lead to creating and
3987 closing a lot of introduction point circuits in a non-stop loop.
3988 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
3990 o Minor bugfixes (portability):
3991 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
3992 It is supported by OpenBSD itself, and also by most OpenBSD
3993 variants (such as Bitrig). Fixes bug 20980; bugfix
3995 - When mapping a file of length greater than SIZE_MAX, do not
3996 silently truncate its contents. This issue could occur on 32 bit
3997 systems with large file support and files which are larger than 4
3998 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
4000 o Minor bugfixes (tor-resolve):
4001 - The tor-resolve command line tool now rejects hostnames over 255
4002 characters in length. Previously, it would silently truncate them,
4003 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
4004 Patch by "junglefowl".
4006 o Minor bugfixes (Windows services):
4007 - Be sure to initialize the monotonic time subsystem before using
4008 it, even when running as an NT service. Fixes bug 21356; bugfix
4012 Changes in version 0.3.0.2-alpha - 2017-01-23
4013 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
4014 cause relays and clients to crash, even if they were not built with
4015 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
4016 versions, and also affects 0.3.0.1-alpha: all relays running an affected
4017 version should upgrade.
4019 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
4020 time-to-live values, makes directory authorities enforce the 1-to-1
4021 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
4022 client-side onion service reachability bug, does better at selecting
4023 the set of fallback directories, and more.
4025 o Major bugfixes (security, also in 0.2.9.9):
4026 - Downgrade the "-ftrapv" option from "always on" to "only on when
4027 --enable-expensive-hardening is provided." This hardening option, like
4028 others, can turn survivable bugs into crashes--and having it on by
4029 default made a (relatively harmless) integer overflow bug into a
4030 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
4033 o Major features (security):
4034 - Change the algorithm used to decide DNS TTLs on client and server
4035 side, to better resist DNS-based correlation attacks like the
4036 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
4037 Feamster. Now relays only return one of two possible DNS TTL
4038 values, and clients are willing to believe DNS TTL values up to 3
4039 hours long. Closes ticket 19769.
4041 o Major features (directory authority, security):
4042 - The default for AuthDirPinKeys is now 1: directory authorities
4043 will reject relays where the RSA identity key matches a previously
4044 seen value, but the Ed25519 key has changed. Closes ticket 18319.
4046 o Major bugfixes (client, guard, crash):
4047 - In circuit_get_global_origin_list(), return the actual list of
4048 origin circuits. The previous version of this code returned the
4049 list of all the circuits, and could have caused strange bugs,
4050 including possible crashes. Fixes bug 21118; bugfix
4053 o Major bugfixes (client, onion service, also in 0.2.9.9):
4054 - Fix a client-side onion service reachability bug, where multiple
4055 socks requests to an onion service (or a single slow request)
4056 could cause us to mistakenly mark some of the service's
4057 introduction points as failed, and we cache that failure so
4058 eventually we run out and can't reach the service. Also resolves a
4059 mysterious "Remote server sent bogus reason code 65021" log
4060 warning. The bug was introduced in ticket 17218, where we tried to
4061 remember the circuit end reason as a uint16_t, which mangled
4062 negative values. Partially fixes bug 21056 and fixes bug 20307;
4063 bugfix on 0.2.8.1-alpha.
4065 o Major bugfixes (DNS):
4066 - Fix a bug that prevented exit nodes from caching DNS records for
4067 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
4069 o Minor features (controller):
4070 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
4071 shared-random values to the controller. Closes ticket 19925.
4073 o Minor features (entry guards):
4074 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
4075 break regression tests.
4076 - Require UseEntryGuards when UseBridges is set, in order to make
4077 sure bridges aren't bypassed. Resolves ticket 20502.
4079 o Minor features (fallback directories):
4080 - Select 200 fallback directories for each release. Closes
4082 - Allow 3 fallback relays per operator, which is safe now that we
4083 are choosing 200 fallback relays. Closes ticket 20912.
4084 - Exclude relays affected by bug 20499 from the fallback list.
4085 Exclude relays from the fallback list if they are running versions
4086 known to be affected by bug 20499, or if in our tests they deliver
4087 a stale consensus (i.e. one that expired more than 24 hours ago).
4088 Closes ticket 20539.
4089 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
4091 - Require fallback directories to have the same address and port for
4092 7 days (now that we have enough relays with this stability).
4093 Relays whose OnionOO stability timer is reset on restart by bug
4094 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
4095 this issue. Closes ticket 20880; maintains short-term fix
4097 - Require fallbacks to have flags for 90% of the time (weighted
4098 decaying average), rather than 95%. This allows at least 73% of
4099 clients to bootstrap in the first 5 seconds without contacting an
4100 authority. Part of ticket 18828.
4101 - Annotate updateFallbackDirs.py with the bandwidth and consensus
4102 weight for each candidate fallback. Closes ticket 20878.
4103 - Make it easier to change the output sort order of fallbacks.
4104 Closes ticket 20822.
4105 - Display the relay fingerprint when downloading consensuses from
4106 fallbacks. Closes ticket 20908.
4108 o Minor features (geoip, also in 0.2.9.9):
4109 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4112 o Minor features (next-gen onion service directories):
4113 - Remove the "EnableOnionServicesV3" consensus parameter that we
4114 introduced in 0.3.0.1-alpha: relays are now always willing to act
4115 as v3 onion service directories. Resolves ticket 19899.
4117 o Minor features (linting):
4118 - Enhance the changes file linter to warn on Tor versions that are
4119 prefixed with "tor-". Closes ticket 21096.
4121 o Minor features (logging):
4122 - In several places, describe unset ed25519 keys as "<unset>",
4123 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
4125 o Minor bugfix (control protocol):
4126 - The reply to a "GETINFO config/names" request via the control
4127 protocol now spells the type "Dependent" correctly. This is a
4128 breaking change in the control protocol. (The field seems to be
4129 ignored by the most common known controllers.) Fixes bug 18146;
4130 bugfix on 0.1.1.4-alpha.
4132 o Minor bugfixes (bug resilience):
4133 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
4134 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
4135 Hans Jerry Illikainen.
4137 o Minor bugfixes (build):
4138 - Replace obsolete Autoconf macros with their modern equivalent and
4139 prevent similar issues in the future. Fixes bug 20990; bugfix
4142 o Minor bugfixes (client, guards):
4143 - Fix bug where Tor would think that there are circuits waiting for
4144 better guards even though those circuits have been freed. Fixes
4145 bug 21142; bugfix on 0.3.0.1-alpha.
4147 o Minor bugfixes (config):
4148 - Don't assert on startup when trying to get the options list and
4149 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
4150 options so of course they aren't ready yet. Fixes bug 21062;
4151 bugfix on 0.2.9.3-alpha.
4153 o Minor bugfixes (controller):
4154 - Make the GETINFO interface for inquiring about entry guards
4155 support the new guards backend. Fixes bug 20823; bugfix
4158 o Minor bugfixes (dead code):
4159 - Remove a redundant check for PidFile changes at runtime in
4160 options_transition_allowed(): this check is already performed
4161 regardless of whether the sandbox is active. Fixes bug 21123;
4162 bugfix on 0.2.5.4-alpha.
4164 o Minor bugfixes (documentation):
4165 - Update the tor manual page to document every option that can not
4166 be changed while tor is running. Fixes bug 21122.
4168 o Minor bugfixes (fallback directories):
4169 - Stop failing when a relay has no uptime data in
4170 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
4171 - Avoid checking fallback candidates' DirPorts if they are down in
4172 OnionOO. When a relay operator has multiple relays, this
4173 prioritizes relays that are up over relays that are down. Fixes
4174 bug 20926; bugfix on 0.2.8.3-alpha.
4175 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
4176 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
4178 o Minor bugfixes (guards, bootstrapping):
4179 - When connecting to a directory guard during bootstrap, do not mark
4180 the guard as successful until we receive a good-looking directory
4181 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
4183 o Minor bugfixes (onion services):
4184 - Fix the config reload pruning of old vs new services so it
4185 actually works when both ephemeral and non-ephemeral services are
4186 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
4187 - Allow the number of introduction points to be as low as 0, rather
4188 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
4190 o Minor bugfixes (IPv6):
4191 - Make IPv6-using clients try harder to find an IPv6 directory
4192 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
4193 - When IPv6 addresses have not been downloaded yet (microdesc
4194 consensus documents don't list relay IPv6 addresses), use hard-
4195 coded addresses for authorities, fallbacks, and configured
4196 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
4197 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
4199 o Minor bugfixes (memory leaks):
4200 - Fix a memory leak when configuring hidden services. Fixes bug
4201 20987; bugfix on 0.3.0.1-alpha.
4203 o Minor bugfixes (portability, also in 0.2.9.9):
4204 - Avoid crashing when Tor is built using headers that contain
4205 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4206 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4208 - Fix Libevent detection on platforms without Libevent 1 headers
4209 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4211 o Minor bugfixes (relay):
4212 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
4213 initializing the keys would reset the DataDirectory to 0700
4214 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
4215 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
4217 o Minor bugfixes (testing):
4218 - Remove undefined behavior from the backtrace generator by removing
4219 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
4221 o Minor bugfixes (unit tests):
4222 - Allow the unit tests to pass even when DNS lookups of bogus
4223 addresses do not fail as expected. Fixes bug 20862 and 20863;
4224 bugfix on unit tests introduced in 0.2.8.1-alpha
4225 through 0.2.9.4-alpha.
4227 o Code simplification and refactoring:
4228 - Refactor code to manipulate global_origin_circuit_list into
4229 separate functions. Closes ticket 20921.
4231 o Documentation (formatting):
4232 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
4233 blocks were incorrectly appearing. Closes ticket 20885.
4235 o Documentation (man page):
4236 - Clarify many options in tor.1 and add some min/max values for
4237 HiddenService options. Closes ticket 21058.
4240 Changes in version 0.2.9.9 - 2017-01-23
4241 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
4242 cause relays and clients to crash, even if they were not built with
4243 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
4244 versions, and also affects 0.3.0.1-alpha: all relays running an affected
4245 version should upgrade.
4247 This release also resolves a client-side onion service reachability
4248 bug, and resolves a pair of small portability issues.
4250 o Major bugfixes (security):
4251 - Downgrade the "-ftrapv" option from "always on" to "only on when
4252 --enable-expensive-hardening is provided." This hardening option,
4253 like others, can turn survivable bugs into crashes -- and having
4254 it on by default made a (relatively harmless) integer overflow bug
4255 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
4256 bugfix on 0.2.9.1-alpha.
4258 o Major bugfixes (client, onion service):
4259 - Fix a client-side onion service reachability bug, where multiple
4260 socks requests to an onion service (or a single slow request)
4261 could cause us to mistakenly mark some of the service's
4262 introduction points as failed, and we cache that failure so
4263 eventually we run out and can't reach the service. Also resolves a
4264 mysterious "Remote server sent bogus reason code 65021" log
4265 warning. The bug was introduced in ticket 17218, where we tried to
4266 remember the circuit end reason as a uint16_t, which mangled
4267 negative values. Partially fixes bug 21056 and fixes bug 20307;
4268 bugfix on 0.2.8.1-alpha.
4270 o Minor features (geoip):
4271 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4274 o Minor bugfixes (portability):
4275 - Avoid crashing when Tor is built using headers that contain
4276 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4277 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4279 - Fix Libevent detection on platforms without Libevent 1 headers
4280 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4283 Changes in version 0.3.0.1-alpha - 2016-12-19
4284 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
4285 series. It strengthens Tor's link and circuit handshakes by
4286 identifying relays by their Ed25519 keys, improves the algorithm that
4287 clients use to choose and maintain their list of guards, and includes
4288 additional backend support for the next-generation hidden service
4289 design. It also contains numerous other small features and
4290 improvements to security, correctness, and performance.
4292 Below are the changes since 0.2.9.8.
4294 o Major features (guard selection algorithm):
4295 - Tor's guard selection algorithm has been redesigned from the
4296 ground up, to better support unreliable networks and restrictive
4297 sets of entry nodes, and to better resist guard-capture attacks by
4298 hostile local networks. Implements proposal 271; closes
4301 o Major features (next-generation hidden services):
4302 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
4303 prop224 aka "Next Generation Hidden Services". Service and clients
4304 don't use this functionality yet. Closes ticket 19043. Based on
4305 initial code by Alec Heifetz.
4306 - Relays now support the HSDir version 3 protocol, so that they can
4307 can store and serve v3 descriptors. This is part of the next-
4308 generation onion service work detailed in proposal 224. Closes
4311 o Major features (protocol, ed25519 identity keys):
4312 - Relays now use Ed25519 to prove their Ed25519 identities and to
4313 one another, and to clients. This algorithm is faster and more
4314 secure than the RSA-based handshake we've been doing until now.
4315 Implements the second big part of proposal 220; Closes
4317 - Clients now support including Ed25519 identity keys in the EXTEND2
4318 cells they generate. By default, this is controlled by a consensus
4319 parameter, currently disabled. You can turn this feature on for
4320 testing by setting ExtendByEd25519ID in your configuration. This
4321 might make your traffic appear different than the traffic
4322 generated by other users, however. Implements part of ticket
4323 15056; part of proposal 220.
4324 - Relays now understand requests to extend to other relays by their
4325 Ed25519 identity keys. When an Ed25519 identity key is included in
4326 an EXTEND2 cell, the relay will only extend the circuit if the
4327 other relay can prove ownership of that identity. Implements part
4328 of ticket 15056; part of proposal 220.
4330 o Major bugfixes (scheduler):
4331 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
4332 caused the channel scheduler to behave more or less randomly,
4333 rather than preferring channels with higher-priority circuits.
4334 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
4336 o Minor features (controller):
4337 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
4338 rather than "unrecognized." Closes ticket 20389; patch from
4341 o Minor features (diagnostic, directory client):
4342 - Warn when we find an unexpected inconsistency in directory
4343 download status objects. Prevents some negative consequences of
4346 o Minor features (directory authority):
4347 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
4348 default) to control whether authorities should try to probe relays
4349 by their Ed25519 link keys. This option will go away in a few
4350 releases--unless we encounter major trouble in our ed25519 link
4351 protocol rollout, in which case it will serve as a safety option.
4353 o Minor features (directory cache):
4354 - Relays and bridges will now refuse to serve the consensus they
4355 have if they know it is too old for a client to use. Closes
4358 o Minor features (ed25519 link handshake):
4359 - Advertise support for the ed25519 link handshake using the
4360 subprotocol-versions mechanism, so that clients can tell which
4361 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
4363 o Minor features (fingerprinting resistance, authentication):
4364 - Extend the length of RSA keys used for TLS link authentication to
4365 2048 bits. (These weren't used for forward secrecy; for forward
4366 secrecy, we used P256.) Closes ticket 13752.
4368 o Minor features (infrastructure):
4369 - Implement smartlist_add_strdup() function. Replaces the use of
4370 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
4372 o Minor bugfixes (client):
4373 - When clients that use bridges start up with a cached consensus on
4374 disk, they were ignoring it and downloading a new one. Now they
4375 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
4377 o Minor bugfixes (configuration):
4378 - Accept non-space whitespace characters after the severity level in
4379 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
4380 - Support "TByte" and "TBytes" units in options given in bytes.
4381 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
4382 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
4384 o Minor bugfixes (consensus weight):
4385 - Add new consensus method that initializes bw weights to 1 instead
4386 of 0. This prevents a zero weight from making it all the way to
4387 the end (happens in small testing networks) and causing an error.
4388 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
4390 o Minor bugfixes (descriptors):
4391 - Correctly recognise downloaded full descriptors as valid, even
4392 when using microdescriptors as circuits. This affects clients with
4393 FetchUselessDescriptors set, and may affect directory authorities.
4394 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
4396 o Minor bugfixes (directory system):
4397 - Download all consensus flavors, descriptors, and authority
4398 certificates when FetchUselessDescriptors is set, regardless of
4399 whether tor is a directory cache or not. Fixes bug 20667; bugfix
4400 on all recent tor versions.
4401 - Bridges and relays now use microdescriptors (like clients do)
4402 rather than old-style router descriptors. Now bridges will blend
4403 in with clients in terms of the circuits they build. Fixes bug
4404 6769; bugfix on 0.2.3.2-alpha.
4406 o Minor bugfixes (ed25519 certificates):
4407 - Correctly interpret ed25519 certificates that would expire some
4408 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
4410 o Minor bugfixes (hidden services):
4411 - Stop ignoring misconfigured hidden services. Instead, refuse to
4412 start tor until the misconfigurations have been corrected. Fixes
4413 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
4416 o Minor bugfixes (memory leak at exit):
4417 - Fix a small harmless memory leak at exit of the previously unused
4418 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
4421 o Minor bugfixes (util):
4422 - When finishing writing a file to disk, if we were about to replace
4423 the file with the temporary file created before and we fail to
4424 replace it, remove the temporary file so it doesn't stay on disk.
4425 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
4427 o Minor bugfixes (Windows):
4428 - Check for getpagesize before using it to mmap files. This fixes
4429 compilation in some MinGW environments. Fixes bug 20530; bugfix on
4430 0.1.2.1-alpha. Reported by "ice".
4432 o Code simplification and refactoring:
4433 - Abolish all global guard context in entrynodes.c; replace with new
4434 guard_selection_t structure as preparation for proposal 271.
4435 Closes ticket 19858.
4436 - Introduce rend_service_is_ephemeral() that tells if given onion
4437 service is ephemeral. Replace unclear NULL-checkings for service
4438 directory with this function. Closes ticket 20526.
4439 - Extract magic numbers in circuituse.c into defined variables.
4440 - Refactor circuit_is_available_for_use to remove unnecessary check.
4441 - Refactor circuit_predict_and_launch_new for readability and
4442 testability. Closes ticket 18873.
4443 - Refactor large if statement in purpose_needs_anonymity to use
4444 switch statement instead. Closes part of ticket 20077.
4445 - Refactor the hashing API to return negative values for errors, as
4446 is done as throughout the codebase. Closes ticket 20717.
4447 - Remove data structures that were used to index or_connection
4448 objects by their RSA identity digests. These structures are fully
4449 redundant with the similar structures used in the
4450 channel abstraction.
4451 - Remove duplicate code in the channel_write_*cell() functions.
4452 Closes ticket 13827; patch from Pingl.
4453 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
4454 use only purpose_needs_anonymity. Closes part of ticket 20077.
4455 - The code to generate and parse EXTEND and EXTEND2 cells has been
4456 replaced with code automatically generated by the
4460 - Include the "TBits" unit in Tor's man page. Fixes part of bug
4461 20622; bugfix on tor-0.2.5.1-alpha.
4462 - Change '1' to 'weight_scale' in consensus bw weights calculation
4463 comments, as that is reality. Closes ticket 20273. Patch
4465 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
4466 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
4467 on tor-0.2.5.6-alpha.
4468 - Stop the man page from incorrectly stating that HiddenServiceDir
4469 must already exist. Fixes 20486.
4470 - Clarify that when ClientRejectInternalAddresses is enabled (which
4471 is the default), multicast DNS hostnames for machines on the local
4472 network (of the form *.local) are also rejected. Closes
4476 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
4477 limit for relays running on a single IP applies to authority IP
4478 addresses as well as to non-authority IP addresses. Closes
4480 - The UseDirectoryGuards torrc option no longer exists: all users
4481 that use entry guards will also use directory guards. Related to
4482 proposal 271; implements part of ticket 20831.
4485 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
4486 from "overcaffeinated".
4487 - Perform the coding style checks when running the tests and fail
4488 when coding style violations are found. Closes ticket 5500.
4489 - Add tests for networkstatus_compute_bw_weights_v10.
4490 - Add unit tests circuit_predict_and_launch_new.
4491 - Extract dummy_origin_circuit_new so it can be used by other
4495 Changes in version 0.2.8.12 - 2016-12-19
4496 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
4497 below) where Tor clients could crash when attempting to visit a
4498 hostile hidden service. Clients are recommended to upgrade as packages
4499 become available for their systems.
4501 It also includes an updated list of fallback directories, backported
4504 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
4505 backported to 0.2.8 in the future.
4507 o Major bugfixes (parsing, security, backported from 0.2.9.8):
4508 - Fix a bug in parsing that could cause clients to read a single
4509 byte past the end of an allocated region. This bug could be used
4510 to cause hardened clients (built with --enable-expensive-hardening)
4511 to crash if they tried to visit a hostile hidden service. Non-
4512 hardened clients are only affected depending on the details of
4513 their platform's memory allocator. Fixes bug 21018; bugfix on
4514 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4515 2016-12-002 and as CVE-2016-1254.
4517 o Minor features (fallback directory list, backported from 0.2.9.8):
4518 - Replace the 81 remaining fallbacks of the 100 originally
4519 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4520 fallbacks (123 new, 54 existing, 27 removed) generated in December
4521 2016. Resolves ticket 20170.
4523 o Minor features (geoip, backported from 0.2.9.7-rc):
4524 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
4528 Changes in version 0.2.9.8 - 2016-12-19
4529 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
4531 The Tor 0.2.9 series makes mandatory a number of security features
4532 that were formerly optional. It includes support for a new shared-
4533 randomness protocol that will form the basis for next generation
4534 hidden services, includes a single-hop hidden service mode for
4535 optimizing .onion services that don't actually want to be hidden,
4536 tries harder not to overload the directory authorities with excessive
4537 downloads, and supports a better protocol versioning scheme for
4538 improved compatibility with other implementations of the Tor protocol.
4540 And of course, there are numerous other bugfixes and improvements.
4542 This release also includes a fix for a medium-severity issue (bug
4543 21018 below) where Tor clients could crash when attempting to visit a
4544 hostile hidden service. Clients are recommended to upgrade as packages
4545 become available for their systems.
4547 Below are the changes since 0.2.9.7-rc. For a list of all changes
4548 since 0.2.8, see the ReleaseNotes file.
4550 o Major bugfixes (parsing, security):
4551 - Fix a bug in parsing that could cause clients to read a single
4552 byte past the end of an allocated region. This bug could be used
4553 to cause hardened clients (built with --enable-expensive-hardening)
4554 to crash if they tried to visit a hostile hidden service. Non-
4555 hardened clients are only affected depending on the details of
4556 their platform's memory allocator. Fixes bug 21018; bugfix on
4557 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4558 2016-12-002 and as CVE-2016-1254.
4560 o Minor features (fallback directory list):
4561 - Replace the 81 remaining fallbacks of the 100 originally
4562 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4563 fallbacks (123 new, 54 existing, 27 removed) generated in December
4564 2016. Resolves ticket 20170.
4567 Changes in version 0.2.9.7-rc - 2016-12-12
4568 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
4569 including a few that had prevented tests from passing on
4572 o Minor features (geoip):
4573 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
4576 o Minor bugfix (build):
4577 - The current Git revision when building from a local repository is
4578 now detected correctly when using git worktrees. Fixes bug 20492;
4579 bugfix on 0.2.3.9-alpha.
4581 o Minor bugfixes (directory authority):
4582 - When computing old Tor protocol line version in protover, we were
4583 looking at 0.2.7.5 twice instead of a specific case for
4584 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
4586 o Minor bugfixes (download scheduling):
4587 - Resolve a "bug" warning when considering a download schedule whose
4588 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
4590 o Minor bugfixes (logging):
4591 - Downgrade a harmless log message about the
4592 pending_entry_connections list from "warn" to "info". Mitigates
4595 o Minor bugfixes (memory leak):
4596 - Fix a small memory leak when receiving AF_UNIX connections on a
4597 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
4598 - When moving a signed descriptor object from a source to an
4599 existing destination, free the allocated memory inside that
4600 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
4602 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
4603 - Fix a memory leak and use-after-free error when removing entries
4604 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
4605 0.2.5.5-alpha. Patch from "cypherpunks".
4607 o Minor bugfixes (portability):
4608 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
4609 Fixes bug 20935; bugfix on 0.2.9.6-rc.
4611 o Minor bugfixes (unit tests):
4612 - Stop expecting NetBSD unit tests to report success for ipfw. Part
4613 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
4614 - Fix tolerances in unit tests for monotonic time comparisons
4615 between nanoseconds and microseconds. Previously, we accepted a 10
4616 us difference only, which is not realistic on every platform's
4617 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
4618 - Remove a double-free in the single onion service unit test. Stop
4619 ignoring a return value. Make future changes less error-prone.
4620 Fixes bug 20864; bugfix on 0.2.9.6-rc.
4623 Changes in version 0.2.8.11 - 2016-12-08
4624 Tor 0.2.8.11 backports fixes for additional portability issues that
4625 could prevent Tor from building correctly on OSX Sierra, or with
4626 OpenSSL 1.1. Affected users should upgrade; others can safely stay
4629 o Minor bugfixes (portability):
4630 - Avoid compilation errors when building on OSX Sierra. Sierra began
4631 to support the getentropy() and clock_gettime() APIs, but created
4632 a few problems in doing so. Tor 0.2.9 has a more thorough set of
4633 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
4634 monotonic time interfaces. Fixes bug 20865. Bugfix
4637 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4638 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
4639 architectures. Closes ticket 20588.
4642 Changes in version 0.2.8.10 - 2016-12-02
4643 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
4644 unusable after they left standby mode. It also backports fixes for
4645 a few portability issues and a small but problematic memory leak.
4647 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
4648 - When Tor leaves standby because of a new application request, open
4649 circuits as needed to serve that request. Previously, we would
4650 potentially wait a very long time. Fixes part of bug 19969; bugfix
4653 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
4654 - Clients now respond to new application stream requests immediately
4655 when they arrive, rather than waiting up to one second before
4656 starting to handle them. Fixes part of bug 19969; bugfix
4659 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
4660 - Work around a bug in the OSX 10.12 SDK that would prevent us from
4661 successfully targeting earlier versions of OSX. Resolves
4664 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4665 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
4666 20551; bugfix on 0.2.1.1-alpha.
4668 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
4669 - Work around a memory leak in OpenSSL 1.1 when encoding public
4670 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
4672 o Minor features (geoip):
4673 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
4676 Changes in version 0.2.9.6-rc - 2016-12-02
4677 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
4678 version. We hope that it will be ready to become stable soon, and we
4679 encourage everyone to test this release. If no showstopper bugs are
4680 found here, the next 0.2.9 release will be stable.
4682 o Major bugfixes (relay, resolver, logging):
4683 - For relays that don't know their own address, avoid attempting a
4684 local hostname resolve for each descriptor we download. This
4685 will cut down on the number of "Success: chose address 'x.x.x.x'"
4686 log lines, and also avoid confusing clock jumps if the resolver
4687 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
4689 o Minor bugfixes (client, fascistfirewall):
4690 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
4691 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
4693 o Minor bugfixes (hidden services):
4694 - Stop ignoring the anonymity status of saved keys for hidden
4695 services and single onion services when first starting tor.
4696 Instead, refuse to start tor if any hidden service key has been
4697 used in a different hidden service anonymity mode. Fixes bug
4698 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
4700 o Minor bugfixes (portability):
4701 - Work around a bug in the OSX 10.12 SDK that would prevent us from
4702 successfully targeting earlier versions of OSX. Resolves
4704 - Run correctly when built on Windows build environments that
4705 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
4707 o Minor bugfixes (single onion services, Tor2web):
4708 - Stop complaining about long-term one-hop circuits deliberately
4709 created by single onion services and Tor2web. These log messages
4710 are intended to diagnose issue 8387, which relates to circuits
4711 hanging around forever for no reason. Fixes bug 20613; bugfix on
4712 0.2.9.1-alpha. Reported by "pastly".
4714 o Minor bugfixes (unit tests):
4715 - Stop spurious failures in the local interface address discovery
4716 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
4720 - Correct the minimum bandwidth value in torrc.sample, and queue a
4721 corresponding change for torrc.minimal. Closes ticket 20085.
4724 Changes in version 0.2.9.5-alpha - 2016-11-08
4725 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
4726 version. We believe one or two probably remain, and we encourage
4727 everyone to test this release.
4729 o Major bugfixes (client performance):
4730 - Clients now respond to new application stream requests immediately
4731 when they arrive, rather than waiting up to one second before
4732 starting to handle them. Fixes part of bug 19969; bugfix
4735 o Major bugfixes (client reliability):
4736 - When Tor leaves standby because of a new application request, open
4737 circuits as needed to serve that request. Previously, we would
4738 potentially wait a very long time. Fixes part of bug 19969; bugfix
4741 o Major bugfixes (download scheduling):
4742 - When using an exponential backoff schedule, do not give up on
4743 downloading just because we have failed a bunch of times. Since
4744 each delay is longer than the last, retrying indefinitely won't
4745 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
4746 - If a consensus expires while we are waiting for certificates to
4747 download, stop waiting for certificates.
4748 - If we stop waiting for certificates less than a minute after we
4749 started downloading them, do not consider the certificate download
4750 failure a separate failure. Fixes bug 20533; bugfix
4752 - Remove the maximum delay on exponential-backoff scheduling. Since
4753 we now allow an infinite number of failures (see ticket 20536), we
4754 must now allow the time to grow longer on each failure. Fixes part
4755 of bug 20534; bugfix on 0.2.9.1-alpha.
4756 - Make our initial download delays closer to those from 0.2.8. Fixes
4757 another part of bug 20534; bugfix on 0.2.9.1-alpha.
4758 - When determining when to download a directory object, handle times
4759 after 2038 if the operating system supports them. (Someday this
4760 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
4761 - When using exponential backoff in test networks, use a lower
4762 exponent, so the delays do not vary as much. This helps test
4763 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
4765 o Minor features (geoip):
4766 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
4769 o Minor bugfixes (client directory scheduling):
4770 - Treat "relay too busy to answer request" as a failed request and a
4771 reason to back off on our retry frequency. This is safe now that
4772 exponential backoffs retry indefinitely, and avoids a bug where we
4773 would reset our download schedule erroneously. Fixes bug 20593;
4774 bugfix on 0.2.9.1-alpha.
4776 o Minor bugfixes (client, logging):
4777 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
4778 assume all nodes support EXTEND2. Use ntor whenever a key is
4779 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
4780 - On DNSPort, stop logging a BUG warning on a failed hostname
4781 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
4783 o Minor bugfixes (hidden services):
4784 - When configuring hidden services, check every hidden service
4785 directory's permissions. Previously, we only checked the last
4786 hidden service. Fixes bug 20529; bugfix the work to fix 13942
4789 o Minor bugfixes (portability):
4790 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
4791 architectures. Closes ticket 20588.
4792 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
4793 removed the ECDH ciphers which caused the tests to fail on
4794 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
4795 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
4796 20551; bugfix on 0.2.1.1-alpha.
4798 o Minor bugfixes (relay bootstrap):
4799 - Ensure relays don't make multiple connections during bootstrap.
4800 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
4802 o Minor bugfixes (relay):
4803 - Work around a memory leak in OpenSSL 1.1 when encoding public
4804 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
4805 - Avoid a small memory leak when informing worker threads about
4806 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
4807 - Do not try to parallelize workers more than 16x without the user
4808 explicitly configuring us to do so, even if we do detect more than
4809 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4811 o Minor bugfixes (single onion services):
4812 - Start correctly when creating a single onion service in a
4813 directory that did not previously exist. Fixes bug 20484; bugfix
4816 o Minor bugfixes (testing):
4817 - Avoid a unit test failure on systems with over 16 detectable CPU
4818 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4821 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
4822 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
4823 - Module-level documentation for several more modules. Closes
4824 tickets 19287 and 19290.
4827 Changes in version 0.2.8.9 - 2016-10-17
4828 Tor 0.2.8.9 backports a fix for a security hole in previous versions
4829 of Tor that would allow a remote attacker to crash a Tor client,
4830 hidden service, relay, or authority. All Tor users should upgrade to
4831 this version, or to 0.2.9.4-alpha. Patches will be released for older
4834 o Major features (security fixes, also in 0.2.9.4-alpha):
4835 - Prevent a class of security bugs caused by treating the contents
4836 of a buffer chunk as if they were a NUL-terminated string. At
4837 least one such bug seems to be present in all currently used
4838 versions of Tor, and would allow an attacker to remotely crash
4839 most Tor instances, especially those compiled with extra compiler
4840 hardening. With this defense in place, such bugs can't crash Tor,
4841 though we should still fix them as they occur. Closes ticket
4842 20384 (TROVE-2016-10-001).
4844 o Minor features (geoip):
4845 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
4849 Changes in version 0.2.9.4-alpha - 2016-10-17
4850 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
4851 that would allow a remote attacker to crash a Tor client, hidden
4852 service, relay, or authority. All Tor users should upgrade to this
4853 version, or to 0.2.8.9. Patches will be released for older versions
4856 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
4857 previous versions of Tor, including the implementation of a feature to
4858 future- proof the Tor ecosystem against protocol changes, some bug
4859 fixes necessary for Tor Browser to use unix domain sockets correctly,
4860 and several portability improvements. We anticipate that this will be
4861 the last alpha in the Tor 0.2.9 series, and that the next release will
4862 be a release candidate.
4864 o Major features (security fixes):
4865 - Prevent a class of security bugs caused by treating the contents
4866 of a buffer chunk as if they were a NUL-terminated string. At
4867 least one such bug seems to be present in all currently used
4868 versions of Tor, and would allow an attacker to remotely crash
4869 most Tor instances, especially those compiled with extra compiler
4870 hardening. With this defense in place, such bugs can't crash Tor,
4871 though we should still fix them as they occur. Closes ticket
4872 20384 (TROVE-2016-10-001).
4874 o Major features (subprotocol versions):
4875 - Tor directory authorities now vote on a set of recommended
4876 subprotocol versions, and on a set of required subprotocol
4877 versions. Clients and relays that lack support for a _required_
4878 subprotocol version will not start; those that lack support for a
4879 _recommended_ subprotocol version will warn the user to upgrade.
4880 Closes ticket 19958; implements part of proposal 264.
4881 - Tor now uses "subprotocol versions" to indicate compatibility.
4882 Previously, versions of Tor looked at the declared Tor version of
4883 a relay to tell whether they could use a given feature. Now, they
4884 should be able to rely on its declared subprotocol versions. This
4885 change allows compatible implementations of the Tor protocol(s) to
4886 exist without pretending to be 100% bug-compatible with particular
4887 releases of Tor itself. Closes ticket 19958; implements part of
4890 o Minor feature (fallback directories):
4891 - Remove broken fallbacks from the hard-coded fallback directory
4892 list. Closes ticket 20190; patch by teor.
4894 o Minor features (client, directory):
4895 - Since authorities now omit all routers that lack the Running and
4896 Valid flags, we assume that any relay listed in the consensus must
4897 have those flags. Closes ticket 20001; implements part of
4900 o Minor features (compilation, portability):
4901 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
4904 o Minor features (development tools, etags):
4905 - Teach the "make tags" Makefile target how to correctly find
4906 "MOCK_IMPL" function definitions. Patch from nherring; closes
4909 o Minor features (geoip):
4910 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
4913 o Minor features (unix domain sockets):
4914 - When configuring a unix domain socket for a SocksPort,
4915 ControlPort, or Hidden service, you can now wrap the address in
4916 quotes, using C-style escapes inside the quotes. This allows unix
4917 domain socket paths to contain spaces.
4919 o Minor features (virtual addresses):
4920 - Increase the maximum number of bits for the IPv6 virtual network
4921 prefix from 16 to 104. In this way, the condition for address
4922 allocation is less restrictive. Closes ticket 20151; feature
4925 o Minor bugfixes (address discovery):
4926 - Stop reordering IP addresses returned by the OS. This makes it
4927 more likely that Tor will guess the same relay IP address every
4928 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
4929 Reported by René Mayrhofer, patch by "cypherpunks".
4931 o Minor bugfixes (client, unix domain sockets):
4932 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
4933 the client address is meaningless. Fixes bug 20261; bugfix
4936 o Minor bugfixes (compilation, OpenBSD):
4937 - Detect Libevent2 functions correctly on systems that provide
4938 libevent2, but where libevent1 is linked with -levent. Fixes bug
4939 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
4941 o Minor bugfixes (configuration):
4942 - When parsing quoted configuration values from the torrc file,
4943 handle windows line endings correctly. Fixes bug 19167; bugfix on
4944 0.2.0.16-alpha. Patch from "Pingl".
4946 o Minor bugfixes (getpass):
4947 - Defensively fix a non-triggerable heap corruption at do_getpass()
4948 to protect ourselves from mistakes in the future. Fixes bug
4949 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
4952 o Minor bugfixes (hidden service):
4953 - Allow hidden services to run on IPv6 addresses even when the
4954 IPv6Exit option is not set. Fixes bug 18357; bugfix
4958 - Add module-level internal documentation for 36 C files that
4959 previously didn't have a high-level overview. Closes ticket #20385.
4961 o Required libraries:
4962 - When building with OpenSSL, Tor now requires version 1.0.1 or
4963 later. OpenSSL 1.0.0 and earlier are no longer supported by the
4964 OpenSSL team, and should not be used. Closes ticket 20303.
4967 Changes in version 0.2.9.3-alpha - 2016-09-23
4968 Tor 0.2.9.3-alpha adds improved support for entities that want to make
4969 high-performance services available through the Tor .onion mechanism
4970 without themselves receiving anonymity as they host those services. It
4971 also tries harder to ensure that all steps on a circuit are using the
4972 strongest crypto possible, strengthens some TLS properties, and
4973 resolves several bugs -- including a pair of crash bugs from the 0.2.8
4974 series. Anybody running an earlier version of 0.2.9.x should upgrade.
4976 o Major bugfixes (crash, also in 0.2.8.8):
4977 - Fix a complicated crash bug that could affect Tor clients
4978 configured to use bridges when replacing a networkstatus consensus
4979 in which one of their bridges was mentioned. OpenBSD users saw
4980 more crashes here, but all platforms were potentially affected.
4981 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
4983 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
4984 - Fix a timing-dependent assertion failure that could occur when we
4985 tried to flush from a circuit after having freed its cells because
4986 of an out-of-memory condition. Fixes bug 20203; bugfix on
4987 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
4990 o Major features (circuit building, security):
4991 - Authorities, relays and clients now require ntor keys in all
4992 descriptors, for all hops (except for rare hidden service protocol
4993 cases), for all circuits, and for all other roles. Part of
4995 - Tor authorities, relays, and clients only use ntor, except for
4996 rare cases in the hidden service protocol. Part of ticket 19163.
4998 o Major features (single-hop "hidden" services):
4999 - Add experimental HiddenServiceSingleHopMode and
5000 HiddenServiceNonAnonymousMode options. When both are set to 1,
5001 every hidden service on a Tor instance becomes a non-anonymous
5002 Single Onion Service. Single Onions make one-hop (direct)
5003 connections to their introduction and renzedvous points. One-hop
5004 circuits make Single Onion servers easily locatable, but clients
5005 remain location-anonymous. This is compatible with the existing
5006 hidden service implementation, and works on the current tor
5007 network without any changes to older relays or clients. Implements
5008 proposal 260, completes ticket 17178. Patch by teor and asn.
5010 o Major features (resource management):
5011 - Tor can now notice it is about to run out of sockets, and
5012 preemptively close connections of lower priority. (This feature is
5013 off by default for now, since the current prioritizing method is
5014 yet not mature enough. You can enable it by setting
5015 "DisableOOSCheck 0", but watch out: it might close some sockets
5016 you would rather have it keep.) Closes ticket 18640.
5018 o Major bugfixes (circuit building):
5019 - Hidden service client-to-intro-point and service-to-rendezvous-
5020 point circuits use the TAP key supplied by the protocol, to avoid
5021 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
5023 o Major bugfixes (compilation, OpenBSD):
5024 - Fix a Libevent-detection bug in our autoconf script that would
5025 prevent Tor from linking successfully on OpenBSD. Patch from
5026 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
5028 o Major bugfixes (hidden services):
5029 - Clients now require hidden services to include the TAP keys for
5030 their intro points in the hidden service descriptor. This prevents
5031 an inadvertent upgrade to ntor, which a malicious hidden service
5032 could use to distinguish clients by consensus version. Fixes bug
5033 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
5035 o Minor features (security, TLS):
5036 - Servers no longer support clients that without AES ciphersuites.
5037 (3DES is no longer considered an acceptable cipher.) We believe
5038 that no such Tor clients currently exist, since Tor has required
5039 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
5041 o Minor feature (fallback directories):
5042 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
5043 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
5044 2016. Closes ticket 20190; patch by teor.
5046 o Minor features (geoip, also in 0.2.8.8):
5047 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
5050 o Minor feature (port flags):
5051 - Add new flags to the *Port options to finer control over which
5052 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
5053 and the synthetic flag OnionTrafficOnly, which is equivalent to
5054 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
5055 18693; patch by "teor".
5057 o Minor features (directory authority):
5058 - After voting, if the authorities decide that a relay is not
5059 "Valid", they no longer include it in the consensus at all. Closes
5060 ticket 20002; implements part of proposal 272.
5062 o Minor features (testing):
5063 - Disable memory protections on OpenBSD when performing our unit
5064 tests for memwipe(). The test deliberately invokes undefined
5065 behavior, and the OpenBSD protections interfere with this. Patch
5066 from "rubiate". Closes ticket 20066.
5068 o Minor features (testing, ipv6):
5069 - Add the single-onion and single-onion-ipv6 chutney targets to
5070 "make test-network-all". This requires a recent chutney version
5071 with the single onion network flavours (git c72a652 or later).
5072 Closes ticket 20072; patch by teor.
5073 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
5074 tests. Remove bridges+hs, as it's somewhat redundant. This
5075 requires a recent chutney version that supports IPv6 clients,
5076 relays, and authorities. Closes ticket 20069; patch by teor.
5078 o Minor features (Tor2web):
5079 - Make Tor2web clients respect ReachableAddresses. This feature was
5080 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
5081 0.2.8.7. Implements feature 20034. Patch by teor.
5083 o Minor features (unit tests):
5084 - We've done significant work to make the unit tests run faster.
5085 - Our link-handshake unit tests now check that when invalid
5086 handshakes fail, they fail with the error messages we expected.
5087 - Our unit testing code that captures log messages no longer
5088 prevents them from being written out if the user asked for them
5089 (by passing --debug or --info or or --notice --warn to the "test"
5090 binary). This change prevents us from missing unexpected log
5091 messages simply because we were looking for others. Related to
5093 - The unit tests now log all warning messages with the "BUG" flag.
5094 Previously, they only logged errors by default. This change will
5095 help us make our testing code more correct, and make sure that we
5096 only hit this code when we mean to. In the meantime, however,
5097 there will be more warnings in the unit test logs than before.
5098 This is preparatory work for ticket 19999.
5099 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
5100 assertion as a test failure.
5102 o Minor bug fixes (circuits):
5103 - Use the CircuitBuildTimeout option whenever
5104 LearnCircuitBuildTimeout is disabled. Previously, we would respect
5105 the option when a user disabled it, but not when it was disabled
5106 because some other option was set. Fixes bug 20073; bugfix on
5107 0.2.4.12-alpha. Patch by teor.
5109 o Minor bugfixes (allocation):
5110 - Change how we allocate memory for large chunks on buffers, to
5111 avoid a (currently impossible) integer overflow, and to waste less
5112 space when allocating unusually large chunks. Fixes bug 20081;
5113 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
5114 - Always include orconfig.h before including any other C headers.
5115 Sometimes, it includes macros that affect the behavior of the
5116 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
5117 first version to use AC_USE_SYSTEM_EXTENSIONS).
5118 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
5119 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
5120 Patch from Gisle Vanem.
5121 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
5122 They apparently require a set of annotations that we aren't
5123 currently using, and they create false positives in our pthreads
5124 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
5126 o Minor bugfixes (directory authority):
5127 - Die with a more useful error when the operator forgets to place
5128 the authority_signing_key file into the keys directory. This
5129 avoids an uninformative assert & traceback about having an invalid
5130 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
5131 - When allowing private addresses, mark Exits that only exit to
5132 private locations as such. Fixes bug 20064; bugfix
5135 o Minor bugfixes (documentation):
5136 - Document the default PathsNeededToBuildCircuits value that's used
5137 by clients when the directory authorities don't set
5138 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
5139 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
5140 - Fix manual for the User option: it takes a username, not a UID.
5141 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
5144 o Minor bugfixes (hidden services):
5145 - Stop logging intro point details to the client log on certain
5146 error conditions. Fixed as part of bug 20012; bugfix on
5147 0.2.4.8-alpha. Patch by teor.
5149 o Minor bugfixes (IPv6, testing):
5150 - Check for IPv6 correctly on Linux when running test networks.
5151 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
5153 o Minor bugfixes (Linux seccomp2 sandbox):
5154 - Add permission to run the sched_yield() and sigaltstack() system
5155 calls, in order to support versions of Tor compiled with asan or
5156 ubsan code that use these calls. Now "sandbox 1" and
5157 "--enable-expensive-hardening" should be compatible on more
5158 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
5160 o Minor bugfixes (logging):
5161 - When logging a message from the BUG() macro, be explicit about
5162 what we were asserting. Previously we were confusing what we were
5163 asserting with what the bug was. Fixes bug 20093; bugfix
5165 - When we are unable to remove the bw_accounting file, do not warn
5166 if the reason we couldn't remove it was that it didn't exist.
5167 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
5169 o Minor bugfixes (option parsing):
5170 - Count unix sockets when counting client listeners (SOCKS, Trans,
5171 NATD, and DNS). This has no user-visible behaviour changes: these
5172 options are set once, and never read. Required for correct
5173 behaviour in ticket 17178. Fixes bug 19677; bugfix on
5174 0.2.6.3-alpha. Patch by teor.
5176 o Minor bugfixes (options):
5177 - Check the consistency of UseEntryGuards and EntryNodes more
5178 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
5180 - Stop changing the configured value of UseEntryGuards on
5181 authorities and Tor2web clients. Fixes bug 20074; bugfix on
5182 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
5185 o Minor bugfixes (Tor2web):
5186 - Prevent Tor2web clients running hidden services, these services
5187 are not anonymous due to the one-hop client paths. Fixes bug
5188 19678. Patch by teor.
5190 o Minor bugfixes (unit tests):
5191 - Fix a shared-random unit test that was failing on big endian
5192 architectures due to internal representation of a integer copied
5193 to a buffer. The test is changed to take a full 32 bytes of data
5194 and use the output of a python script that make the COMMIT and
5195 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
5197 - The tor_tls_server_info_callback unit test no longer crashes when
5198 debug-level logging is turned on. Fixes bug 20041; bugfix
5202 Changes in version 0.2.8.8 - 2016-09-23
5203 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
5204 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
5205 who select public relays as their bridges.
5207 o Major bugfixes (crash):
5208 - Fix a complicated crash bug that could affect Tor clients
5209 configured to use bridges when replacing a networkstatus consensus
5210 in which one of their bridges was mentioned. OpenBSD users saw
5211 more crashes here, but all platforms were potentially affected.
5212 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
5214 o Major bugfixes (relay, OOM handler):
5215 - Fix a timing-dependent assertion failure that could occur when we
5216 tried to flush from a circuit after having freed its cells because
5217 of an out-of-memory condition. Fixes bug 20203; bugfix on
5218 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
5221 o Minor feature (fallback directories):
5222 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
5223 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
5224 2016. Closes ticket 20190; patch by teor.
5226 o Minor features (geoip):
5227 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
5231 Changes in version 0.2.9.2-alpha - 2016-08-24
5232 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
5233 several new features and bugfixes. It also includes an important
5234 authority update and an important bugfix from 0.2.8.7. Everyone who
5235 sets the ReachableAddresses option, and all bridges, are strongly
5236 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
5238 o Directory authority changes (also in 0.2.8.7):
5239 - The "Tonga" bridge authority has been retired; the new bridge
5240 authority is "Bifroest". Closes tickets 19728 and 19690.
5242 o Major bugfixes (client, security, also in 0.2.8.7):
5243 - Only use the ReachableAddresses option to restrict the first hop
5244 in a path. In earlier versions of 0.2.8.x, it would apply to
5245 every hop in the path, with a possible degradation in anonymity
5246 for anyone using an uncommon ReachableAddress setting. Fixes bug
5247 19973; bugfix on 0.2.8.2-alpha.
5249 o Major features (user interface):
5250 - Tor now supports the ability to declare options deprecated, so
5251 that we can recommend that people stop using them. Previously,
5252 this was done in an ad-hoc way. Closes ticket 19820.
5254 o Major bugfixes (directory downloads):
5255 - Avoid resetting download status for consensuses hourly, since we
5256 already have another, smarter retry mechanism. Fixes bug 8625;
5257 bugfix on 0.2.0.9-alpha.
5259 o Minor features (config):
5260 - Warn users when descriptor and port addresses are inconsistent.
5261 Mitigates bug 13953; patch by teor.
5263 o Minor features (geoip):
5264 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
5267 o Minor features (user interface):
5268 - There is a new --list-deprecated-options command-line option to
5269 list all of the deprecated options. Implemented as part of
5272 o Minor bugfixes (code style):
5273 - Fix an integer signedness conversion issue in the case conversion
5274 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
5276 o Minor bugfixes (compilation):
5277 - Build correctly on versions of libevent2 without support for
5278 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
5280 - Fix a compilation warning on GCC versions before 4.6. Our
5281 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
5282 when it is also required as an argument to the compiler pragma.
5283 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
5285 o Minor bugfixes (compilation, also in 0.2.8.7):
5286 - Remove an inappropriate "inline" in tortls.c that was causing
5287 warnings on older versions of GCC. Fixes bug 19903; bugfix
5290 o Minor bugfixes (fallback directories, also in 0.2.8.7):
5291 - Avoid logging a NULL string pointer when loading fallback
5292 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
5293 and 0.2.8.1-alpha. Report and patch by "rubiate".
5295 o Minor bugfixes (logging):
5296 - Log a more accurate message when we fail to dump a microdescriptor.
5297 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
5299 o Minor bugfixes (memory leak):
5300 - Fix a series of slow memory leaks related to parsing torrc files
5301 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
5303 o Deprecated features:
5304 - A number of DNS-cache-related sub-options for client ports are now
5305 deprecated for security reasons, and may be removed in a future
5306 version of Tor. (We believe that client-side DNS cacheing is a bad
5307 idea for anonymity, and you should not turn it on.) The options
5308 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
5309 UseIPv4Cache, and UseIPv6Cache.
5310 - A number of options are deprecated for security reasons, and may
5311 be removed in a future version of Tor. The options are:
5312 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
5313 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
5314 CloseHSClientCircuitsImmediatelyOnTimeout,
5315 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
5316 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
5317 UseNTorHandshake, and WarnUnsafeSocks.
5318 - The *ListenAddress options are now deprecated as unnecessary: the
5319 corresponding *Port options should be used instead. These options
5320 may someday be removed. The affected options are:
5321 ControlListenAddress, DNSListenAddress, DirListenAddress,
5322 NATDListenAddress, ORListenAddress, SocksListenAddress,
5323 and TransListenAddress.
5326 - Correct the IPv6 syntax in our documentation for the
5327 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
5330 - We no longer include the (dead, deprecated) bufferevent code in
5331 Tor. Closes ticket 19450. Based on a patch from U+039b.
5334 Changes in version 0.2.8.7 - 2016-08-24
5335 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
5336 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
5337 who sets the ReachableAddresses option, and all bridges, are strongly
5338 encouraged to upgrade.
5340 o Directory authority changes:
5341 - The "Tonga" bridge authority has been retired; the new bridge
5342 authority is "Bifroest". Closes tickets 19728 and 19690.
5344 o Major bugfixes (client, security):
5345 - Only use the ReachableAddresses option to restrict the first hop
5346 in a path. In earlier versions of 0.2.8.x, it would apply to
5347 every hop in the path, with a possible degradation in anonymity
5348 for anyone using an uncommon ReachableAddress setting. Fixes bug
5349 19973; bugfix on 0.2.8.2-alpha.
5351 o Minor features (geoip):
5352 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
5355 o Minor bugfixes (compilation):
5356 - Remove an inappropriate "inline" in tortls.c that was causing
5357 warnings on older versions of GCC. Fixes bug 19903; bugfix
5360 o Minor bugfixes (fallback directories):
5361 - Avoid logging a NULL string pointer when loading fallback
5362 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
5363 and 0.2.8.1-alpha. Report and patch by "rubiate".
5366 Changes in version 0.2.9.1-alpha - 2016-08-08
5367 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
5368 series. It improves our support for hardened builds and compiler
5369 warnings, deploys some critical infrastructure for improvements to
5370 hidden services, includes a new timing backend that we hope to use for
5371 better support for traffic padding, makes it easier for programmers to
5372 log unexpected events, and contains other small improvements to
5373 security, correctness, and performance.
5375 Below are the changes since 0.2.8.6.
5377 o New system requirements:
5378 - Tor now requires Libevent version 2.0.10-stable or later. Older
5379 versions of Libevent have less efficient backends for several
5380 platforms, and lack the DNS code that we use for our server-side
5381 DNS support. This implements ticket 19554.
5382 - Tor now requires zlib version 1.2 or later, for security,
5383 efficiency, and (eventually) gzip support. (Back when we started,
5384 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
5385 released in 2003. We recommend the latest version.)
5387 o Major features (build, hardening):
5388 - Tor now builds with -ftrapv by default on compilers that support
5389 it. This option detects signed integer overflow (which C forbids),
5390 and turns it into a hard-failure. We do not apply this option to
5391 code that needs to run in constant time to avoid side-channels;
5392 instead, we use -fwrapv in that code. Closes ticket 17983.
5393 - When --enable-expensive-hardening is selected, stop applying the
5394 clang/gcc sanitizers to code that needs to run in constant time.
5395 Although we are aware of no introduced side-channels, we are not
5396 able to prove that there are none. Related to ticket 17983.
5398 o Major features (compilation):
5399 - Our big list of extra GCC warnings is now enabled by default when
5400 building with GCC (or with anything like Clang that claims to be
5401 GCC-compatible). To make all warnings into fatal compilation
5402 errors, pass --enable-fatal-warnings to configure. Closes
5404 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
5405 turn on C and POSIX extensions. (Previously, we attempted to do
5406 this on an ad hoc basis.) Closes ticket 19139.
5408 o Major features (directory authorities, hidden services):
5409 - Directory authorities can now perform the shared randomness
5410 protocol specified by proposal 250. Using this protocol, directory
5411 authorities generate a global fresh random value every day. In the
5412 future, this value will be used by hidden services to select
5413 HSDirs. This release implements the directory authority feature;
5414 the hidden service side will be implemented in the future as part
5415 of proposal 224. Resolves ticket 16943; implements proposal 250.
5417 o Major features (downloading, random exponential backoff):
5418 - When we fail to download an object from a directory service, wait
5419 for an (exponentially increasing) randomized amount of time before
5420 retrying, rather than a fixed interval as we did before. This
5421 prevents a group of Tor instances from becoming too synchronized,
5422 or a single Tor instance from becoming too predictable, in its
5423 download schedule. Closes ticket 15942.
5425 o Major bugfixes (exit policies):
5426 - Avoid disclosing exit outbound bind addresses, configured port
5427 bind addresses, and local interface addresses in relay descriptors
5428 by default under ExitPolicyRejectPrivate. Instead, only reject
5429 these (otherwise unlisted) addresses if
5430 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
5431 0.2.7.2-alpha. Patch by teor.
5433 o Major bugfixes (hidden service client):
5434 - Allow Tor clients with appropriate controllers to work with
5435 FetchHidServDescriptors set to 0. Previously, this option also
5436 disabled descriptor cache lookup, thus breaking hidden services
5437 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
5439 o Minor features (build, hardening):
5440 - Detect and work around a libclang_rt problem that would prevent
5441 clang from finding __mulodi4() on some 32-bit platforms, and thus
5442 keep -ftrapv from linking on those systems. Closes ticket 19079.
5443 - When building on a system without runtime support for the runtime
5444 hardening options, try to log a useful warning at configuration
5445 time, rather than an incomprehensible warning at link time. If
5446 expensive hardening was requested, this warning becomes an error.
5447 Closes ticket 18895.
5449 o Minor features (code safety):
5450 - In our integer-parsing functions, ensure that maxiumum value we
5451 give is no smaller than the minimum value. Closes ticket 19063;
5454 o Minor features (controller):
5455 - Implement new GETINFO queries for all downloads that use
5456 download_status_t to schedule retries. This allows controllers to
5457 examine the schedule for pending downloads. Closes ticket 19323.
5458 - Allow controllers to configure basic client authorization on
5459 hidden services when they create them with the ADD_ONION control
5460 command. Implements ticket 15588. Patch by "special".
5461 - Fire a STATUS_SERVER controller event whenever the hibernation
5462 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
5464 o Minor features (directory authority):
5465 - Directory authorities now only give the Guard flag to a relay if
5466 they are also giving it the Stable flag. This change allows us to
5467 simplify path selection for clients. It should have minimal effect
5468 in practice, since >99% of Guards already have the Stable flag.
5469 Implements ticket 18624.
5470 - Directory authorities now write their v3-status-votes file out to
5471 disk earlier in the consensus process, so we have a record of the
5472 votes even if we abort the consensus process. Resolves
5475 o Minor features (hidden service):
5476 - Stop being so strict about the payload length of "rendezvous1"
5477 cells. We used to be locked in to the "TAP" handshake length, and
5478 now we can handle better handshakes like "ntor". Resolves
5481 o Minor features (infrastructure, time):
5482 - Tor now uses the operating system's monotonic timers (where
5483 available) for internal fine-grained timing. Previously we would
5484 look at the system clock, and then attempt to compensate for the
5485 clock running backwards. Closes ticket 18908.
5486 - Tor now includes an improved timer backend, so that we can
5487 efficiently support tens or hundreds of thousands of concurrent
5488 timers, as will be needed for some of our planned anti-traffic-
5489 analysis work. This code is based on William Ahern's "timeout.c"
5490 project, which implements a "tickless hierarchical timing wheel".
5491 Closes ticket 18365.
5493 o Minor features (logging):
5494 - Provide a more useful warning message when configured with an
5495 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
5496 - When dumping unparseable router descriptors, optionally store them
5497 in separate files, named by digest, up to a configurable size
5498 limit. You can change the size limit by setting the
5499 MaxUnparseableDescSizeToLog option, and disable this feature by
5500 setting that option to 0. Closes ticket 18322.
5501 - Add a set of macros to check nonfatal assertions, for internal
5502 use. Migrating more of our checks to these should help us avoid
5503 needless crash bugs. Closes ticket 18613.
5505 o Minor features (performance):
5506 - Changer the "optimistic data" extension from "off by default" to
5507 "on by default". The default was ordinarily overridden by a
5508 consensus option, but when clients were bootstrapping for the
5509 first time, they would not have a consensus to get the option
5510 from. Changing this default When fetching a consensus for the
5511 first time, use optimistic data. This saves a round-trip during
5512 startup. Closes ticket 18815.
5514 o Minor features (relay, usability):
5515 - When the directory authorities refuse a bad relay's descriptor,
5516 encourage the relay operator to contact us. Many relay operators
5517 won't notice this line in their logs, but it's a win if even a few
5518 learn why we don't like what their relay was doing. Resolves
5521 o Minor features (testing):
5522 - Let backtrace tests work correctly under AddressSanitizer. Fixes
5523 part of bug 18934; bugfix on 0.2.5.2-alpha.
5524 - Move the test-network.sh script to chutney, and modify tor's test-
5525 network.sh to call the (newer) chutney version when available.
5526 Resolves ticket 19116. Patch by teor.
5527 - Use the lcov convention for marking lines as unreachable, so that
5528 we don't count them when we're generating test coverage data.
5529 Update our coverage tools to understand this convention. Closes
5532 o Minor bugfixes (bootstrap):
5533 - Remember the directory we fetched the consensus or previous
5534 certificates from, and use it to fetch future authority
5535 certificates. This change improves bootstrapping performance.
5536 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
5538 o Minor bugfixes (build):
5539 - The test-stem and test-network makefile targets now depend only on
5540 the tor binary that they are testing. Previously, they depended on
5541 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
5542 patch from "cypherpunks".
5544 o Minor bugfixes (circuits):
5545 - Make sure extend_info_from_router() is only called on servers.
5546 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
5548 o Minor bugfixes (compilation):
5549 - When building with Clang, use a full set of GCC warnings.
5550 (Previously, we included only a subset, because of the way we
5551 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
5553 o Minor bugfixes (directory authority):
5554 - Authorities now sort the "package" lines in their votes, for ease
5555 of debugging. (They are already sorted in consensus documents.)
5556 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
5557 - When parsing a detached signature, make sure we use the length of
5558 the digest algorithm instead of an hardcoded DIGEST256_LEN in
5559 order to avoid comparing bytes out-of-bounds with a smaller digest
5560 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
5562 o Minor bugfixes (documentation):
5563 - Document the --passphrase-fd option in the tor manpage. Fixes bug
5564 19504; bugfix on 0.2.7.3-rc.
5565 - Fix the description of the --passphrase-fd option in the
5566 tor-gencert manpage. The option is used to pass the number of a
5567 file descriptor to read the passphrase from, not to read the file
5568 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
5570 o Minor bugfixes (ephemeral hidden service):
5571 - When deleting an ephemeral hidden service, close its intro points
5572 even if they are not completely open. Fixes bug 18604; bugfix
5575 o Minor bugfixes (guard selection):
5576 - Use a single entry guard even if the NumEntryGuards consensus
5577 parameter is not provided. Fixes bug 17688; bugfix
5579 - Don't mark guards as unreachable if connection_connect() fails.
5580 That function fails for local reasons, so it shouldn't reveal
5581 anything about the status of the guard. Fixes bug 14334; bugfix
5584 o Minor bugfixes (hidden service client):
5585 - Increase the minimum number of internal circuits we preemptively
5586 build from 2 to 3, so a circuit is available when a client
5587 connects to another onion service. Fixes bug 13239; bugfix
5590 o Minor bugfixes (logging):
5591 - When logging a directory ownership mismatch, log the owning
5592 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
5594 o Minor bugfixes (memory leaks):
5595 - Fix a small, uncommon memory leak that could occur when reading a
5596 truncated ed25519 key file. Fixes bug 18956; bugfix
5599 o Minor bugfixes (testing):
5600 - Allow clients to retry HSDirs much faster in test networks. Fixes
5601 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
5602 - Disable ASAN's detection of segmentation faults while running
5603 test_bt.sh, so that we can make sure that our own backtrace
5604 generation code works. Fixes another aspect of bug 18934; bugfix
5605 on 0.2.5.2-alpha. Patch from "cypherpunks".
5606 - Fix the test-network-all target on out-of-tree builds by using the
5607 correct path to the test driver script. Fixes bug 19421; bugfix
5610 o Minor bugfixes (time):
5611 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
5612 bugfix on all released tor versions.
5613 - When computing the difference between two times in milliseconds,
5614 we now round to the nearest millisecond correctly. Previously, we
5615 could sometimes round in the wrong direction. Fixes bug 19428;
5616 bugfix on 0.2.2.2-alpha.
5618 o Minor bugfixes (user interface):
5619 - Display a more accurate number of suppressed messages in the log
5620 rate-limiter. Previously, there was a potential integer overflow
5621 in the counter. Now, if the number of messages hits a maximum, the
5622 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
5624 - Fix a typo in the passphrase prompt for the ed25519 identity key.
5625 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
5627 o Code simplification and refactoring:
5628 - Remove redundant declarations of the MIN macro. Closes
5630 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
5631 Closes ticket 18462; patch from "icanhasaccount".
5632 - Split the 600-line directory_handle_command_get function into
5633 separate functions for different URL types. Closes ticket 16698.
5636 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
5637 ticket 19153. Patch from "U+039b".
5640 - Remove support for "GET /tor/bytes.txt" DirPort request, and
5641 "GETINFO dir-usage" controller request, which were only available
5642 via a compile-time option in Tor anyway. Feature was added in
5643 0.2.2.1-alpha. Resolves ticket 19035.
5644 - There is no longer a compile-time option to disable support for
5645 TransPort. (If you don't want TransPort; just don't use it.) Patch
5646 from "U+039b". Closes ticket 19449.
5649 - Run more workqueue tests as part of "make check". These had
5650 previously been implemented, but you needed to know special
5651 command-line options to enable them.
5652 - We now have unit tests for our code to reject zlib "compression
5653 bombs". (Fortunately, the code works fine.)
5656 Changes in version 0.2.8.6 - 2016-08-02
5658 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
5660 The Tor 0.2.8 series improves client bootstrapping performance,
5661 completes the authority-side implementation of improved identity
5662 keys for relays, and includes numerous bugfixes and performance
5663 improvements throughout the program. This release continues to
5664 improve the coverage of Tor's test suite. For a full list of
5665 changes since Tor 0.2.7, see the ReleaseNotes file.
5667 Changes since 0.2.8.5-rc:
5669 o Minor features (geoip):
5670 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
5673 o Minor bugfixes (compilation):
5674 - Fix a compilation warning in the unit tests on systems where char
5675 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
5677 o Minor bugfixes (fallback directories):
5678 - Remove 1 fallback that was on the hardcoded list, then opted-out,
5679 leaving 89 of the 100 fallbacks originally introduced in Tor
5680 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
5682 o Minor bugfixes (Linux seccomp2 sandbox):
5683 - Allow more syscalls when running with "Sandbox 1" enabled:
5684 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
5685 some systems, these are required for Tor to start. Fixes bug
5686 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
5687 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
5688 so that get_interface_address6_via_udp_socket_hack() can work.
5689 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
5692 Changes in version 0.2.8.5-rc - 2016-07-07
5693 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
5694 series. If we find no new bugs or regressions here, the first stable
5695 0.2.8 release will be identical to it. It has a few small bugfixes
5696 against previous versions.
5698 o Directory authority changes:
5699 - Urras is no longer a directory authority. Closes ticket 19271.
5701 o Major bugfixes (heartbeat):
5702 - Fix a regression that would crash Tor when the periodic
5703 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
5704 0.2.8.1-alpha. Reported by "kubaku".
5706 o Minor features (build):
5707 - Tor now again builds with the recent OpenSSL 1.1 development
5708 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
5709 - When building manual pages, set the timezone to "UTC", so that the
5710 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
5711 Patch from intrigeri.
5713 o Minor bugfixes (fallback directory selection):
5714 - Avoid errors during fallback selection if there are no eligible
5715 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
5718 o Minor bugfixes (IPv6, microdescriptors):
5719 - Don't check node addresses when we only have a routerstatus. This
5720 allows IPv6-only clients to bootstrap by fetching microdescriptors
5721 from fallback directory mirrors. (The microdescriptor consensus
5722 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
5725 o Minor bugfixes (logging):
5726 - Reduce pointlessly verbose log messages when directory servers
5727 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
5728 0.2.8.1-alpha. Patch by teor.
5729 - When a fallback directory changes its fingerprint from the hard-
5730 coded fingerprint, log a less severe, more explanatory log
5731 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
5733 o Minor bugfixes (Linux seccomp2 sandboxing):
5734 - Allow statistics to be written to disk when "Sandbox 1" is
5735 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
5736 0.2.6.1-alpha respectively.
5738 o Minor bugfixes (user interface):
5739 - Remove a warning message "Service [scrubbed] not found after
5740 descriptor upload". This message appears when one uses HSPOST
5741 control command to upload a service descriptor. Since there is
5742 only a descriptor and no service, showing this message is
5743 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
5745 o Fallback directory list:
5746 - Add a comment to the generated fallback directory list that
5747 explains how to comment out unsuitable fallbacks in a way that's
5748 compatible with the stem fallback parser.
5749 - Update fallback whitelist and blacklist based on relay operator
5750 emails. Blacklist unsuitable (non-working, over-volatile)
5751 fallbacks. Resolves ticket 19071. Patch by teor.
5752 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
5753 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
5754 ticket 19071; patch by teor.
5757 Changes in version 0.2.8.4-rc - 2016-06-15
5758 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
5759 If we find no new bugs or regressions here, the first stable 0.2.8
5760 release will be identical to it. It has a few small bugfixes against
5763 o Major bugfixes (user interface):
5764 - Correctly give a warning in the cases where a relay is specified
5765 by nickname, and one such relay is found, but it is not officially
5766 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
5768 o Minor features (build):
5769 - Tor now builds once again with the recent OpenSSL 1.1 development
5770 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
5772 o Minor features (geoip):
5773 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
5776 o Minor bugfixes (compilation):
5777 - Cause the unit tests to compile correctly on mingw64 versions that
5778 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
5780 o Minor bugfixes (downloading):
5781 - Predict more correctly whether we'll be downloading over HTTP when
5782 we determine the maximum length of a URL. This should avoid a
5783 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
5787 Changes in version 0.2.8.3-alpha - 2016-05-26
5788 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
5789 the course of the 0.2.8 development cycle. It improves the behavior of
5790 directory clients, fixes several crash bugs, fixes a gap in compiler
5791 hardening, and allows the full integration test suite to run on
5794 o Major bugfixes (security, client, DNS proxy):
5795 - Stop a crash that could occur when a client running with DNSPort
5796 received a query with multiple address types, and the first
5797 address type was not supported. Found and fixed by Scott Dial.
5798 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5800 o Major bugfixes (security, compilation):
5801 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
5802 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
5803 cause a compiler warning, thereby making other checks fail, and
5804 needlessly disabling compiler-hardening support. Fixes one case of
5805 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
5807 o Major bugfixes (security, directory authorities):
5808 - Fix a crash and out-of-bounds write during authority voting, when
5809 the list of relays includes duplicate ed25519 identity keys. Fixes
5810 bug 19032; bugfix on 0.2.8.2-alpha.
5812 o Major bugfixes (client, bootstrapping):
5813 - Check if bootstrap consensus downloads are still needed when the
5814 linked connection attaches. This prevents tor making unnecessary
5815 begindir-style connections, which are the only directory
5816 connections tor clients make since the fix for 18483 was merged.
5817 - Fix some edge cases where consensus download connections may not
5818 have been closed, even though they were not needed. Related to fix
5820 - Make relays retry consensus downloads the correct number of times,
5821 rather than the more aggressive client retry count. Fixes part of
5823 - Stop downloading consensuses when we have a consensus, even if we
5824 don't have all the certificates for it yet. Fixes bug 18809;
5825 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
5827 o Major bugfixes (directory mirrors):
5828 - Decide whether to advertise begindir support in the the same way
5829 we decide whether to advertise our DirPort. Allowing these
5830 decisions to become out-of-sync led to surprising behavior like
5831 advertising begindir support when hibernation made us not
5832 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
5835 o Major bugfixes (IPv6 bridges, client):
5836 - Actually use IPv6 addresses when selecting directory addresses for
5837 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
5840 o Major bugfixes (key management):
5841 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5842 pointer to the previous (uninitialized) key value. The impact here
5843 should be limited to a difficult-to-trigger crash, if OpenSSL is
5844 running an engine that makes key generation failures possible, or
5845 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5846 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5849 o Major bugfixes (testing):
5850 - Fix a bug that would block 'make test-network-all' on systems where
5851 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
5852 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
5853 bugfix on 0.2.8.1-alpha.
5855 o Minor features (clients):
5856 - Make clients, onion services, and bridge relays always use an
5857 encrypted begindir connection for directory requests. Resolves
5858 ticket 18483. Patch by "teor".
5860 o Minor features (fallback directory mirrors):
5861 - Give each fallback the same weight for client selection; restrict
5862 fallbacks to one per operator; report fallback directory detail
5863 changes when rebuilding list; add new fallback directory mirrors
5864 to the whitelist; and many other minor simplifications and fixes.
5865 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
5866 0.2.8.1-alpha; patch by "teor".
5867 - Replace the 21 fallbacks generated in January 2016 and included in
5868 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
5869 2016. Closes task 17158; patch by "teor".
5871 o Minor features (geoip):
5872 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
5875 o Minor bugfixes (assert, portability):
5876 - Fix an assertion failure in memarea.c on systems where "long" is
5877 shorter than the size of a pointer. Fixes bug 18716; bugfix
5880 o Minor bugfixes (bootstrap):
5881 - Consistently use the consensus download schedule for authority
5882 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
5884 o Minor bugfixes (build):
5885 - Remove a pair of redundant AM_CONDITIONAL declarations from
5886 configure.ac. Fixes one final case of bug 17744; bugfix
5888 - Resolve warnings when building on systems that are concerned with
5889 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
5891 - When libscrypt.h is found, but no libscrypt library can be linked,
5892 treat libscrypt as absent. Fixes bug 19161; bugfix
5895 o Minor bugfixes (client):
5896 - Turn all TestingClientBootstrap* into non-testing torrc options.
5897 This changes simply renames them by removing "Testing" in front of
5898 them and they do not require TestingTorNetwork to be enabled
5899 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
5900 - Make directory node selection more reliable, mainly for IPv6-only
5901 clients and clients with few reachable addresses. Fixes bug 18929;
5902 bugfix on 0.2.8.1-alpha. Patch by "teor".
5904 o Minor bugfixes (controller, microdescriptors):
5905 - Make GETINFO dir/status-vote/current/consensus conform to the
5906 control specification by returning "551 Could not open cached
5907 consensus..." when not caching consensuses. Fixes bug 18920;
5908 bugfix on 0.2.2.6-alpha.
5910 o Minor bugfixes (crypto, portability):
5911 - The SHA3 and SHAKE routines now produce the correct output on Big
5912 Endian systems. No code calls either algorithm yet, so this is
5913 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
5914 - Tor now builds again with the recent OpenSSL 1.1 development
5915 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
5918 o Minor bugfixes (directories):
5919 - When fetching extrainfo documents, compare their SHA256 digests
5920 and Ed25519 signing key certificates with the routerinfo that led
5921 us to fetch them, rather than with the most recent routerinfo.
5922 Otherwise we generate many spurious warnings about mismatches.
5923 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
5925 o Minor bugfixes (logging):
5926 - When we can't generate a signing key because OfflineMasterKey is
5927 set, do not imply that we should have been able to load it. Fixes
5928 bug 18133; bugfix on 0.2.7.2-alpha.
5929 - Stop periodic_event_dispatch() from blasting twelve lines per
5930 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
5931 - When rejecting a misformed INTRODUCE2 cell, only log at
5932 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
5934 o Minor bugfixes (pluggable transports):
5935 - Avoid reporting a spurious error when we decide that we don't need
5936 to terminate a pluggable transport because it has already exited.
5937 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
5939 o Minor bugfixes (pointer arithmetic):
5940 - Fix a bug in memarea_alloc() that could have resulted in remote
5941 heap write access, if Tor had ever passed an unchecked size to
5942 memarea_alloc(). Fortunately, all the sizes we pass to
5943 memarea_alloc() are pre-checked to be less than 128 kilobytes.
5944 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
5947 o Minor bugfixes (relays):
5948 - Consider more config options when relays decide whether to
5949 regenerate their descriptor. Fixes more of bug 12538; bugfix
5951 - Resolve some edge cases where we might launch an ORPort
5952 reachability check even when DisableNetwork is set. Noticed while
5953 fixing bug 18616; bugfix on 0.2.3.9-alpha.
5955 o Minor bugfixes (statistics):
5956 - We now include consensus downloads via IPv6 in our directory-
5957 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
5959 o Minor bugfixes (testing):
5960 - Allow directories in small networks to bootstrap by skipping
5961 DirPort checks when the consensus has no exits. Fixes bug 19003;
5962 bugfix on 0.2.8.1-alpha. Patch by teor.
5963 - Fix a small memory leak that would occur when the
5964 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
5965 bugfix on 0.2.5.2-alpha.
5967 o Minor bugfixes (time handling):
5968 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
5969 field. Otherwise, our unit tests crash on Windows. Fixes bug
5970 18977; bugfix on 0.2.2.25-alpha.
5973 - Document the contents of the 'datadir/keys' subdirectory in the
5974 manual page. Closes ticket 17621.
5975 - Stop recommending use of nicknames to identify relays in our
5976 MapAddress documentation. Closes ticket 18312.
5979 Changes in version 0.2.8.2-alpha - 2016-03-28
5980 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
5981 bugs in earlier versions of Tor, including some that prevented
5982 authorities using Tor 0.2.7.x from running correctly. IPv6 and
5983 directory support should also be much improved.
5985 o New system requirements:
5986 - Tor no longer supports versions of OpenSSL with a broken
5987 implementation of counter mode. (This bug was present in OpenSSL
5988 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
5989 longer runs with, these versions.
5990 - Tor no longer attempts to support platforms where the "time_t"
5991 type is unsigned. (To the best of our knowledge, only OpenVMS does
5992 this, and Tor has never actually built on OpenVMS.) Closes
5994 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
5995 later (released in 2008 and 2009 respectively). If you are
5996 building Tor from the git repository instead of from the source
5997 distribution, and your tools are older than this, you will need to
5998 upgrade. Closes ticket 17732.
6000 o Major bugfixes (security, pointers):
6001 - Avoid a difficult-to-trigger heap corruption attack when extending
6002 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
6003 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
6004 Reported by Guido Vranken.
6006 o Major bugfixes (bridges, pluggable transports):
6007 - Modify the check for OR connections to private addresses. Allow
6008 bridges on private addresses, including pluggable transports that
6009 ignore the (potentially private) address in the bridge line. Fixes
6010 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
6012 o Major bugfixes (compilation):
6013 - Repair hardened builds under the clang compiler. Previously, our
6014 use of _FORTIFY_SOURCE would conflict with clang's address
6015 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
6017 o Major bugfixes (crash on shutdown):
6018 - Correctly handle detaching circuits from muxes when shutting down.
6019 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
6020 - Fix an assert-on-exit bug related to counting memory usage in
6021 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
6023 o Major bugfixes (crash on startup):
6024 - Fix a segfault during startup: If a Unix domain socket was
6025 configured as listener (such as a ControlSocket or a SocksPort
6026 "unix:" socket), and tor was started as root but not configured to
6027 switch to another user, tor would segfault while trying to string
6028 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
6031 o Major bugfixes (dns proxy mode, crash):
6032 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
6033 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
6035 o Major bugfixes (relays, bridge clients):
6036 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
6037 bridge clients use the address configured in the bridge line.
6038 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
6041 o Major bugfixes (voting):
6042 - Actually enable support for authorities to match routers by their
6043 Ed25519 identities. Previously, the code had been written, but
6044 some debugging code that had accidentally been left in the
6045 codebase made it stay turned off. Fixes bug 17702; bugfix
6047 - When collating votes by Ed25519 identities, authorities now
6048 include a "NoEdConsensus" flag if the ed25519 value (or lack
6049 thereof) for a server does not reflect the majority consensus.
6050 Related to bug 17668; bugfix on 0.2.7.2-alpha.
6051 - When generating a vote with keypinning disabled, never include two
6052 entries for the same ed25519 identity. This bug was causing
6053 authorities to generate votes that they could not parse when a
6054 router violated key pinning by changing its RSA identity but
6055 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
6056 18318. Bugfix on 0.2.7.2-alpha.
6058 o Minor features (security, win32):
6059 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
6060 attack. Fixes bug 18123; bugfix on all tor versions. Patch
6063 o Minor features (bug-resistance):
6064 - Make Tor survive errors involving connections without a
6065 corresponding event object. Previously we'd fail with an
6066 assertion; now we produce a log message. Related to bug 16248.
6068 o Minor features (build):
6069 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
6070 as having possible IPFW support. Closes ticket 18448. Patch from
6073 o Minor features (code hardening):
6074 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
6075 level code, to harden against accidental failures to NUL-
6076 terminate. Part of ticket 17852. Patch from jsturgix. Found
6079 o Minor features (crypto):
6080 - Validate the hard-coded Diffie-Hellman parameters and ensure that
6081 p is a safe prime, and g is a suitable generator. Closes
6084 o Minor features (geoip):
6085 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
6088 o Minor features (hidden service directory):
6089 - Streamline relay-side hsdir handling: when relays consider whether
6090 to accept an uploaded hidden service descriptor, they no longer
6091 check whether they are one of the relays in the network that is
6092 "supposed" to handle that descriptor. Implements ticket 18332.
6094 o Minor features (IPv6):
6095 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
6096 to 1, tor prefers IPv6 directory addresses.
6097 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
6098 avoids using IPv4 for client OR and directory connections.
6099 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
6100 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
6101 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
6103 o Minor features (linux seccomp2 sandbox):
6104 - Reject attempts to change our Address with "Sandbox 1" enabled.
6105 Changing Address with Sandbox turned on would never actually work,
6106 but previously it would fail in strange and confusing ways. Found
6109 o Minor features (robustness):
6110 - Exit immediately with an error message if the code attempts to use
6111 Libevent without having initialized it. This should resolve some
6112 frequently-made mistakes in our unit tests. Closes ticket 18241.
6114 o Minor features (unix domain sockets):
6115 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
6116 Unix domain sockets without checking the permissions on the parent
6117 directory. (Tor checks permissions by default because some
6118 operating systems only check permissions on the parent directory.
6119 However, some operating systems do look at permissions on the
6120 socket, and tor's default check is unneeded.) Closes ticket 18458.
6123 o Minor bugfixes (exit policies, security):
6124 - Refresh an exit relay's exit policy when interface addresses
6125 change. Previously, tor only refreshed the exit policy when the
6126 configured external address changed. Fixes bug 18208; bugfix on
6127 0.2.7.3-rc. Patch by teor.
6129 o Minor bugfixes (security, hidden services):
6130 - Prevent hidden services connecting to client-supplied rendezvous
6131 addresses that are reserved as internal or multicast. Fixes bug
6132 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
6134 o Minor bugfixes (build):
6135 - Do not link the unit tests against both the testing and non-
6136 testing versions of the static libraries. Fixes bug 18490; bugfix
6138 - Avoid spurious failures from configure files related to calling
6139 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
6140 0.2.0.1-alpha. Patch from "cypherpunks".
6141 - Silence spurious clang-scan warnings in the ed25519_donna code by
6142 explicitly initializing some objects. Fixes bug 18384; bugfix on
6143 0.2.7.2-alpha. Patch by teor.
6145 o Minor bugfixes (client, bootstrap):
6146 - Count receipt of new microdescriptors as progress towards
6147 bootstrapping. Previously, with EntryNodes set, Tor might not
6148 successfully repopulate the guard set on bootstrapping. Fixes bug
6149 16825; bugfix on 0.2.3.1-alpha.
6151 o Minor bugfixes (code correctness):
6152 - Update to the latest version of Trunnel, which tries harder to
6153 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
6154 by clang address sanitizer. Fixes bug 18373; bugfix
6157 o Minor bugfixes (configuration):
6158 - Fix a tiny memory leak when parsing a port configuration ending in
6159 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
6161 o Minor bugfixes (containers):
6162 - If we somehow attempt to construct a heap with more than
6163 1073741822 elements, avoid an integer overflow when maintaining
6164 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
6166 o Minor bugfixes (correctness):
6167 - Fix a bad memory handling bug that would occur if we had queued a
6168 cell on a channel's incoming queue. Fortunately, we can't actually
6169 queue a cell like that as our code is constructed today, but it's
6170 best to avoid this kind of error, even if there isn't any code
6171 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
6173 o Minor bugfixes (directory):
6174 - When generating a URL for a directory server on an IPv6 address,
6175 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
6176 on 0.2.3.9-alpha. Patch from Malek.
6178 o Minor bugfixes (fallback directory mirrors):
6179 - When requesting extrainfo descriptors from a trusted directory
6180 server, check whether it is an authority or a fallback directory
6181 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
6182 0.2.4.7-alpha. Reported by atagar, patch by teor.
6184 o Minor bugfixes (hidden service, client):
6185 - Handle the case where the user makes several fast consecutive
6186 requests to the same .onion address. Previously, the first six
6187 requests would each trigger a descriptor fetch, each picking a
6188 directory (there are 6 overall) and the seventh one would fail
6189 because no directories were left, thereby triggering a close on
6190 all current directory connections asking for the hidden service.
6191 The solution here is to not close the connections if we have
6192 pending directory fetches. Fixes bug 15937; bugfix
6195 o Minor bugfixes (hidden service, control port):
6196 - Add the onion address to the HS_DESC event for the UPLOADED action
6197 both on success or failure. It was previously hardcoded with
6198 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
6200 o Minor bugfixes (hidden service, directory):
6201 - Bridges now refuse "rendezvous2" (hidden service descriptor)
6202 publish attempts. Suggested by ticket 18332.
6204 o Minor bugfixes (linux seccomp2 sandbox):
6205 - Allow the setrlimit syscall, and the prlimit and prlimit64
6206 syscalls, which some libc implementations use under the hood.
6207 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
6208 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
6209 enabled and no DNS resolvers configured. This should help TAILS
6210 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
6211 - Fix the sandbox's interoperability with unix domain sockets under
6212 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
6214 o Minor bugfixes (logging):
6215 - When logging information about an unparsable networkstatus vote or
6216 consensus, do not say "vote" when we mean consensus. Fixes bug
6217 18368; bugfix on 0.2.0.8-alpha.
6218 - Scrub service name in "unrecognized service ID" log messages.
6219 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
6220 - Downgrade logs and backtraces about IP versions to info-level.
6221 Only log backtraces once each time tor runs. Assists in diagnosing
6222 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
6223 Christian, patch by teor.
6225 o Minor bugfixes (memory safety):
6226 - Avoid freeing an uninitialized pointer when opening a socket fails
6227 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
6228 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
6230 - Correctly duplicate addresses in get_interface_address6_list().
6231 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
6232 patch by "cypherpunks".
6233 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
6235 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
6236 18672; bugfix on 0.2.5.1-alpha.
6238 o Minor bugfixes (private directory):
6239 - Prevent a race condition when creating private directories. Fixes
6240 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
6241 Patch from jsturgix. Found with Flawfinder.
6243 o Minor bugfixes (test networks, IPv6):
6244 - Allow internal IPv6 addresses in descriptors in test networks.
6245 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
6248 o Minor bugfixes (testing):
6249 - We no longer disable assertions in the unit tests when coverage is
6250 enabled. Instead, we require you to say --disable-asserts-in-tests
6251 to the configure script if you need assertions disabled in the
6252 unit tests (for example, if you want to perform branch coverage).
6253 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
6255 o Minor bugfixes (time parsing):
6256 - Avoid overflow in tor_timegm when parsing dates in and after 2038
6257 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
6258 0.0.2pre14. Patch by teor.
6260 o Minor bugfixes (tor-gencert):
6261 - Correctly handle the case where an authority operator enters a
6262 passphrase but sends an EOF before sending a newline. Fixes bug
6263 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
6265 o Code simplification and refactoring:
6266 - Quote all the string interpolations in configure.ac -- even those
6267 which we are pretty sure can't contain spaces. Closes ticket
6268 17744. Patch from zerosion.
6269 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
6270 inplace, so there's no need to have a separate implementation for
6271 the non-inplace code. Closes ticket 18258. Patch from Malek.
6272 - Simplify return types for some crypto functions that can't
6273 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
6276 - Change build messages to refer to "Fedora" instead of "Fedora
6277 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
6278 Patches from "icanhasaccount" and "cypherpunks".
6281 - We no longer maintain an internal freelist in memarea.c.
6282 Allocators should be good enough to make this code unnecessary,
6283 and it's doubtful that it ever had any performance benefit.
6286 - Fix several warnings from clang's address sanitizer produced in
6288 - Treat backtrace test failures as expected on FreeBSD until we
6289 solve bug 17808. Closes ticket 18204.
6292 Changes in version 0.2.8.1-alpha - 2016-02-04
6293 Tor 0.2.8.1-alpha is the first alpha release in its series. It
6294 includes numerous small features and bugfixes against previous Tor
6295 versions, and numerous small infrastructure improvements. The most
6296 notable features are a set of improvements to the directory subsystem.
6298 o Major features (security, Linux):
6299 - When Tor starts as root on Linux and is told to switch user ID, it
6300 can now retain the capability to bind to low ports. By default,
6301 Tor will do this only when it's switching user ID and some low
6302 ports have been configured. You can change this behavior with the
6303 new option KeepBindCapabilities. Closes ticket 8195.
6305 o Major features (directory system):
6306 - When bootstrapping multiple consensus downloads at a time, use the
6307 first one that starts downloading, and close the rest. This
6308 reduces failures when authorities or fallback directories are slow
6309 or down. Together with the code for feature 15775, this feature
6310 should reduces failures due to fallback churn. Implements ticket
6311 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
6312 "mikeperry" and "teor".
6313 - Include a trial list of 21 default fallback directories, generated
6314 in January 2016, based on an opt-in survey of suitable relays.
6315 Doing this should make clients bootstrap more quickly and reliably,
6316 and reduce the load on the directory authorities. Closes ticket
6317 15775. Patch by "teor".
6318 Candidates identified using an OnionOO script by "weasel", "teor",
6319 "gsathya", and "karsten".
6320 - Previously only relays that explicitly opened a directory port
6321 (DirPort) accepted directory requests from clients. Now all
6322 relays, with and without a DirPort, accept and serve tunneled
6323 directory requests that they receive through their ORPort. You can
6324 disable this behavior using the new DirCache option. Closes
6327 o Major key updates:
6328 - Update the V3 identity key for the dannenberg directory authority:
6329 it was changed on 18 November 2015. Closes task 17906. Patch
6332 o Minor features (security, clock):
6333 - Warn when the system clock appears to move back in time (when the
6334 state file was last written in the future). Tor doesn't know that
6335 consensuses have expired if the clock is in the past. Patch by
6336 "teor". Implements ticket 17188.
6338 o Minor features (security, exit policies):
6339 - ExitPolicyRejectPrivate now rejects more private addresses by
6340 default. Specifically, it now rejects the relay's outbound bind
6341 addresses (if configured), and the relay's configured port
6342 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
6343 0.2.0.11-alpha. Patch by "teor".
6345 o Minor features (security, memory erasure):
6346 - Set the unused entries in a smartlist to NULL. This helped catch
6347 a (harmless) bug, and shouldn't affect performance too much.
6348 Implements ticket 17026.
6349 - Use SecureMemoryWipe() function to securely clean memory on
6350 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
6351 Implements feature 17986.
6352 - Use explicit_bzero or memset_s when present. Previously, we'd use
6353 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
6354 from <logan@hackers.mu> and <selven@hackers.mu>.
6355 - Make memwipe() do nothing when passed a NULL pointer or buffer of
6356 zero size. Check size argument to memwipe() for underflow. Fixes
6357 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
6360 o Minor features (security, RNG):
6361 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
6362 positively are not allowed to fail. Previously we depended on
6363 internal details of OpenSSL's behavior. Closes ticket 17686.
6364 - Never use the system entropy output directly for anything besides
6365 seeding the PRNG. When we want to generate important keys, instead
6366 of using system entropy directly, we now hash it with the PRNG
6367 stream. This may help resist certain attacks based on broken OS
6368 entropy implementations. Closes part of ticket 17694.
6369 - Use modern system calls (like getentropy() or getrandom()) to
6370 generate strong entropy on platforms that have them. Closes
6373 o Minor features (accounting):
6374 - Added two modes to the AccountingRule option: One for limiting
6375 only the number of bytes sent ("AccountingRule out"), and one for
6376 limiting only the number of bytes received ("AccountingRule in").
6377 Closes ticket 15989; patch from "unixninja92".
6379 o Minor features (build):
6380 - Since our build process now uses "make distcheck", we no longer
6381 force "make dist" to depend on "make check". Closes ticket 17893;
6382 patch from "cypherpunks."
6383 - Tor now builds successfully with the recent OpenSSL 1.1
6384 development branch, and with the latest LibreSSL. Closes tickets
6385 17549, 17921, and 17984.
6387 o Minor features (controller):
6388 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
6389 tickets 16774 and 17817. Patch by George Tankersley.
6390 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
6391 service descriptor from a service's local hidden service
6392 descriptor cache. Closes ticket 14846.
6393 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
6394 controllers can examine the the reject rules added by
6395 ExitPolicyRejectPrivate. This makes it easier for stem to display
6398 o Minor features (crypto):
6399 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
6401 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
6402 - When allocating a digest state object, allocate no more space than
6403 we actually need. Previously, we would allocate as much space as
6404 the state for the largest algorithm would need. This change saves
6405 up to 672 bytes per circuit. Closes ticket 17796.
6406 - Improve performance when hashing non-multiple of 8 sized buffers,
6407 based on Andrew Moon's public domain SipHash-2-4 implementation.
6408 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
6410 o Minor features (directory downloads):
6411 - Wait for busy authorities and fallback directories to become non-
6412 busy when bootstrapping. (A similar change was made in 6c443e987d
6413 for directory caches chosen from the consensus.) Closes ticket
6414 17864; patch by "teor".
6415 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
6416 directory mirrors. The default is 1; set it to 0 to disable
6417 fallbacks. Implements ticket 17576. Patch by "teor".
6419 o Minor features (geoip):
6420 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
6423 o Minor features (IPv6):
6424 - Add an argument 'ipv6=address:orport' to the DirAuthority and
6425 FallbackDir torrc options, to specify an IPv6 address for an
6426 authority or fallback directory. Add hard-coded ipv6 addresses for
6427 directory authorities that have them. Closes ticket 17327; patch
6428 from Nick Mathewson and "teor".
6429 - Add address policy assume_action support for IPv6 addresses.
6430 - Limit IPv6 mask bits to 128.
6431 - Warn when comparing against an AF_UNSPEC address in a policy, it's
6432 almost always a bug. Closes ticket 17863; patch by "teor".
6433 - Allow users to configure directory authorities and fallback
6434 directory servers with IPv6 addresses and ORPorts. Resolves
6436 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
6437 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
6438 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
6439 17638; bugfix on 0.0.2pre8. Patch by "teor".
6441 o Minor features (logging):
6442 - When logging to syslog, allow a tag to be added to the syslog
6443 identity (the string prepended to every log message). The tag can
6444 be configured with SyslogIdentityTag and defaults to none. Setting
6445 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
6448 o Minor features (portability):
6449 - Use timingsafe_memcmp() where available. Closes ticket 17944;
6450 patch from <logan@hackers.mu>.
6452 o Minor features (relay, address discovery):
6453 - Add a family argument to get_interface_addresses_raw() and
6454 subfunctions to make network interface address interogation more
6455 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
6456 types of interfaces from the operating system. Resolves
6458 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
6459 fails to enumerate interface addresses using the platform-specific
6460 API, have it rely on the UDP socket fallback technique to try and
6461 find out what IP addresses (both IPv4 and IPv6) our machine has.
6462 Resolves ticket 17951.
6464 o Minor features (replay cache):
6465 - The replay cache now uses SHA256 instead of SHA1. Implements
6466 feature 8961. Patch by "teor", issue reported by "rransom".
6468 o Minor features (unix file permissions):
6469 - Defer creation of Unix sockets until after setuid. This avoids
6470 needing CAP_CHOWN and CAP_FOWNER when using systemd's
6471 CapabilityBoundingSet, or chown and fowner when using SELinux.
6472 Implements part of ticket 17562. Patch from Jamie Nguyen.
6473 - If any directory created by Tor is marked as group readable, the
6474 filesystem group is allowed to be either the default GID or the
6475 root user. Allowing root to read the DataDirectory prevents the
6476 need for CAP_READ_SEARCH when using systemd's
6477 CapabilityBoundingSet, or dac_read_search when using SELinux.
6478 Implements part of ticket 17562. Patch from Jamie Nguyen.
6479 - Introduce a new DataDirectoryGroupReadable option. If it is set to
6480 1, the DataDirectory will be made readable by the default GID.
6481 Implements part of ticket 17562. Patch from Jamie Nguyen.
6483 o Minor bugfixes (accounting):
6484 - The max bandwidth when using 'AccountRule sum' is now correctly
6485 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
6488 o Minor bugfixes (code correctness):
6489 - When closing an entry connection, generate a warning if we should
6490 have sent an end cell for it but we haven't. Fixes bug 17876;
6491 bugfix on 0.2.3.2-alpha.
6492 - Assert that allocated memory held by the reputation code is freed
6493 according to its internal counters. Fixes bug 17753; bugfix
6495 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
6498 o Minor bugfixes (compilation):
6499 - Mark all object files that include micro-revision.i as depending
6500 on it, so as to make parallel builds more reliable. Fixes bug
6501 17826; bugfix on 0.2.5.1-alpha.
6502 - Don't try to use the pthread_condattr_setclock() function unless
6503 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
6504 17819; bugfix on 0.2.6.3-alpha.
6505 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
6507 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
6508 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
6509 - Fix search for libevent libraries on OpenBSD (and other systems
6510 that install libevent 1 and libevent 2 in parallel). Fixes bug
6511 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
6512 - Isolate environment variables meant for tests from the rest of the
6513 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
6514 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
6516 - Remove config.log only from make distclean, not from make clean.
6517 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
6519 o Minor bugfixes (crypto):
6520 - Check the return value of HMAC() and assert on failure. Fixes bug
6521 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
6523 o Minor bugfixes (fallback directories):
6524 - Mark fallbacks as "too busy" when they return a 503 response,
6525 rather than just marking authorities. Fixes bug 17572; bugfix on
6526 0.2.4.7-alpha. Patch by "teor".
6528 o Minor bugfixes (IPv6):
6529 - Update the limits in max_dl_per_request for IPv6 address length.
6530 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
6532 o Minor bugfixes (linux seccomp2 sandbox):
6533 - Fix a crash when using offline master ed25519 keys with the Linux
6534 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
6536 o Minor bugfixes (logging):
6537 - In log messages that include a function name, use __FUNCTION__
6538 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
6539 with clang __PRETTY_FUNCTION__ has extra information we don't
6540 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
6542 - Remove needless quotes from a log message about unparseable
6543 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
6545 o Minor bugfixes (portability):
6546 - Remove an #endif from configure.ac so that we correctly detect the
6547 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
6550 o Minor bugfixes (relays):
6551 - Check that both the ORPort and DirPort (if present) are reachable
6552 before publishing a relay descriptor. Otherwise, relays publish a
6553 descriptor with DirPort 0 when the DirPort reachability test takes
6554 longer than the ORPort reachability test. Fixes bug 18050; bugfix
6555 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
6557 o Minor bugfixes (relays, hidden services):
6558 - Refuse connection requests to private OR addresses unless
6559 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
6560 then refuse to send any cells to a private address. Fixes bugs
6561 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
6563 o Minor bugfixes (safe logging):
6564 - When logging a malformed hostname received through socks4, scrub
6565 it if SafeLogging says we should. Fixes bug 17419; bugfix
6568 o Minor bugfixes (statistics code):
6569 - Consistently check for overflow in round_*_to_next_multiple_of
6570 functions, and add unit tests with additional and maximal values.
6571 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
6572 - Handle edge cases in the laplace functions: avoid division by
6573 zero, avoid taking the log of zero, and silence clang type
6574 conversion warnings using round and trunc. Add unit tests for edge
6575 cases with maximal values. Fixes part of bug 13192; bugfix
6578 o Minor bugfixes (testing):
6579 - The test for log_heartbeat was incorrectly failing in timezones
6580 with non-integer offsets. Instead of comparing the end of the time
6581 string against a constant, compare it to the output of
6582 format_local_iso_time when given the correct input. Fixes bug
6583 18039; bugfix on 0.2.5.4-alpha.
6584 - Make unit tests pass on IPv6-only systems, and systems without
6585 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
6586 bugfix on 0.2.7.3-rc. Patch by "teor".
6587 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
6589 - Check the full results of SHA256 and SHA512 digests in the unit
6590 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
6592 o Code simplification and refactoring:
6593 - Move logging of redundant policy entries in
6594 policies_parse_exit_policy_internal into its own function. Closes
6595 ticket 17608; patch from "juce".
6596 - Extract the more complicated parts of circuit_mark_for_close()
6597 into a new function that we run periodically before circuits are
6598 freed. This change removes more than half of the functions
6599 currently in the "blob". Closes ticket 17218.
6600 - Clean up a little duplicated code in
6601 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
6603 - Decouple the list of streams waiting to be attached to circuits
6604 from the overall connection list. This change makes it possible to
6605 attach streams quickly while simplifying Tor's callgraph and
6606 avoiding O(N) scans of the entire connection list. Closes
6608 - When a direct directory request fails immediately on launch,
6609 instead of relaunching that request from inside the code that
6610 launches it, instead mark the connection for teardown. This change
6611 simplifies Tor's callback and prevents the directory-request
6612 launching code from invoking itself recursively. Closes
6614 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
6615 use them. Closes ticket 17926.
6618 - Add a description of the correct use of the '--keygen' command-
6619 line option. Closes ticket 17583; based on text by 's7r'.
6620 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
6621 - Explain actual minima for BandwidthRate. Closes ticket 16382.
6622 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
6623 - Mention torspec URL in the manpage and point the reader to it
6624 whenever we mention a document that belongs in torspce. Fixes
6628 - Remove client-side support for connecting to Tor relays running
6629 versions of Tor before 0.2.3.6-alpha. These relays didn't support
6630 the v3 TLS handshake protocol, and are no longer allowed on the
6631 Tor network. Implements the client side of ticket 11150. Based on
6632 patches by Tom van der Woerdt.
6635 - Add unit tests to check for common RNG failure modes, such as
6636 returning all zeroes, identical values, or incrementing values
6637 (OpenSSL's rand_predictable feature). Patch by "teor".
6638 - Log more information when the backtrace tests fail. Closes ticket
6639 17892. Patch from "cypherpunks."
6640 - Always test both ed25519 backends, so that we can be sure that our
6641 batch-open replacement code works. Part of ticket 16794.
6642 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
6643 portion of ticket 16831.
6644 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
6645 util_format.c, directory.c, and options_validate.c. Closes tickets
6646 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
6648 - Unit tests for directory_handle_command_get. Closes ticket 17004.
6649 Patch from Reinaldo de Souza Jr.
6652 Changes in version 0.2.7.6 - 2015-12-10
6653 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
6654 well as a minor bug in hidden service reliability.
6656 o Major bugfixes (guard selection):
6657 - Actually look at the Guard flag when selecting a new directory
6658 guard. When we implemented the directory guard design, we
6659 accidentally started treating all relays as if they have the Guard
6660 flag during guard selection, leading to weaker anonymity and worse
6661 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
6664 o Minor features (geoip):
6665 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
6668 o Minor bugfixes (compilation):
6669 - When checking for net/pfvar.h, include netinet/in.h if possible.
6670 This fixes transparent proxy detection on OpenBSD. Fixes bug
6671 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
6672 - Fix a compilation warning with Clang 3.6: Do not check the
6673 presence of an address which can never be NULL. Fixes bug 17781.
6675 o Minor bugfixes (correctness):
6676 - When displaying an IPv6 exit policy, include the mask bits
6677 correctly even when the number is greater than 31. Fixes bug
6678 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
6679 - The wrong list was used when looking up expired intro points in a
6680 rend service object, causing what we think could be reachability
6681 issues for hidden services, and triggering a BUG log. Fixes bug
6682 16702; bugfix on 0.2.7.2-alpha.
6683 - Fix undefined behavior in the tor_cert_checksig function. Fixes
6684 bug 17722; bugfix on 0.2.7.2-alpha.
6687 Changes in version 0.2.7.5 - 2015-11-20
6688 The Tor 0.2.7 release series is dedicated to the memory of Tor user
6689 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
6690 tirelessly to advocate human rights regardless of national borders,
6691 and oppose the encroachments of mass surveillance. He opposed national
6692 exceptionalism, he brought clarity to legal and policy debates, he
6693 understood and predicted the impact of mass surveillance on the world,
6694 and he laid the groundwork for resisting it. While serving on the Tor
6695 Project's board of directors, he brought us his uncompromising focus
6696 on technical excellence in the service of humankind. Caspar was an
6697 inimitable force for good and a wonderful friend. He was kind,
6698 humorous, generous, gallant, and believed we should protect one
6699 another without exception. We honor him here for his ideals, his
6700 efforts, and his accomplishments. Please honor his memory with works
6701 that would make him proud.
6703 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
6705 The 0.2.7 series adds a more secure identity key type for relays,
6706 improves cryptography performance, resolves several longstanding
6707 hidden-service performance issues, improves controller support for
6708 hidden services, and includes small bugfixes and performance
6709 improvements throughout the program. This release series also includes
6710 more tests than before, and significant simplifications to which parts
6711 of Tor invoke which others.
6713 (This release contains no code changes since 0.2.7.4-rc.)
6716 Changes in version 0.2.7.4-rc - 2015-10-21
6717 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
6718 fixes some important memory leaks, and a scary-looking (but mostly
6719 harmless in practice) invalid-read bug. It also has a few small
6720 bugfixes, notably fixes for compilation and portability on different
6721 platforms. If no further significant bounds are found, the next
6722 release will the the official stable release.
6724 o Major bugfixes (security, correctness):
6725 - Fix an error that could cause us to read 4 bytes before the
6726 beginning of an openssl string. This bug could be used to cause
6727 Tor to crash on systems with unusual malloc implementations, or
6728 systems with unusual hardening installed. Fixes bug 17404; bugfix
6731 o Major bugfixes (correctness):
6732 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
6733 bug 17401; bugfix on 0.2.7.3-rc.
6735 o Major bugfixes (memory leaks):
6736 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
6737 17398; bugfix on 0.2.6.1-alpha.
6738 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
6739 17402; bugfix on 0.2.7.3-rc.
6740 - Fix a memory leak when reading an expired signing key from disk.
6741 Fixes bug 17403; bugfix on 0.2.7.2-rc.
6743 o Minor features (geoIP):
6744 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
6747 o Minor bugfixes (compilation):
6748 - Repair compilation with the most recent (unreleased, alpha)
6749 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
6750 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
6751 17251; bugfix on 0.2.7.2-alpha.
6752 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
6753 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
6755 o Minor bugfixes (portability):
6756 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
6757 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
6760 o Minor bugfixes (sandbox):
6761 - Add the "hidserv-stats" filename to our sandbox filter for the
6762 HiddenServiceStatistics option to work properly. Fixes bug 17354;
6763 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
6765 o Minor bugfixes (testing):
6766 - Add unit tests for get_interface_address* failure cases. Fixes bug
6767 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
6768 - Fix breakage when running 'make check' with BSD make. Fixes bug
6769 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
6770 - Make the get_ifaddrs_* unit tests more tolerant of different
6771 network configurations. (Don't assume every test box has an IPv4
6772 address, and don't assume every test box has a non-localhost
6773 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
6774 - Skip backtrace tests when backtrace support is not compiled in.
6775 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
6779 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
6780 - Note that HiddenServicePorts can take a unix domain socket. Closes
6784 Changes in version 0.2.7.3-rc - 2015-09-25
6785 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
6786 contains numerous usability fixes for Ed25519 keys, safeguards against
6787 several misconfiguration problems, significant simplifications to
6788 Tor's callgraph, and numerous bugfixes and small features.
6790 This is the most tested release of Tor to date. The unit tests cover
6791 39.40% of the code, and the integration tests (accessible with "make
6792 test-full-online", requiring stem and chutney and a network
6793 connection) raise the coverage to 64.49%.
6795 o Major features (security, hidden services):
6796 - Hidden services, if using the EntryNodes option, are required to
6797 use more than one EntryNode, in order to avoid a guard discovery
6798 attack. (This would only affect people who had configured hidden
6799 services and manually specified the EntryNodes option with a
6800 single entry-node. The impact was that it would be easy to
6801 remotely identify the guard node used by such a hidden service.
6802 See ticket for more information.) Fixes ticket 14917.
6804 o Major features (Ed25519 keys, keypinning):
6805 - The key-pinning option on directory authorities is now advisory-
6806 only by default. In a future version, or when the AuthDirPinKeys
6807 option is set, pins are enforced again. Disabling key-pinning
6808 seemed like a good idea so that we can survive the fallout of any
6809 usability problems associated with Ed25519 keys. Closes
6812 o Major features (Ed25519 performance):
6813 - Improve the speed of Ed25519 operations and Curve25519 keypair
6814 generation when built targeting 32 bit x86 platforms with SSE2
6815 available. Implements ticket 16535.
6816 - Improve the runtime speed of Ed25519 signature verification by
6817 using Ed25519-donna's batch verification support. Implements
6820 o Major features (performance testing):
6821 - The test-network.sh script now supports performance testing.
6822 Requires corresponding chutney performance testing changes. Patch
6823 by "teor". Closes ticket 14175.
6825 o Major features (relay, Ed25519):
6826 - Significant usability improvements for Ed25519 key management. Log
6827 messages are better, and the code can recover from far more
6828 failure conditions. Thanks to "s7r" for reporting and diagnosing
6830 - Add a new OfflineMasterKey option to tell Tor never to try loading
6831 or generating a secret Ed25519 identity key. You can use this in
6832 combination with tor --keygen to manage offline and/or encrypted
6833 Ed25519 keys. Implements ticket 16944.
6834 - Add a --newpass option to allow changing or removing the
6835 passphrase of an encrypted key with tor --keygen. Implements part
6837 - On receiving a HUP signal, check to see whether the Ed25519
6838 signing key has changed, and reload it if so. Closes ticket 16790.
6840 o Major bugfixes (relay, Ed25519):
6841 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
6842 0.2.7.2-alpha. Reported by "s7r".
6843 - Improve handling of expired signing keys with offline master keys.
6844 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
6846 o Minor features (client-side privacy):
6847 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
6848 lifespan when IsolateSOCKSAuth and streams with SOCKS
6849 authentication are attached to the circuit. This allows
6850 applications like TorBrowser to manage circuit lifetime on their
6851 own. Implements feature 15482.
6852 - When logging malformed hostnames from SOCKS5 requests, respect
6853 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
6855 o Minor features (compilation):
6856 - Give a warning as early as possible when trying to build with an
6857 unsupported OpenSSL version. Closes ticket 16901.
6858 - Fail during configure if we're trying to build against an OpenSSL
6859 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
6860 which started requiring ECC.
6862 o Minor features (geoip):
6863 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
6866 o Minor features (hidden services):
6867 - Relays need to have the Fast flag to get the HSDir flag. As this
6868 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
6869 drop. This change should make some attacks against the hidden
6870 service directory system harder. Fixes ticket 15963.
6871 - Turn on hidden service statistics collection by setting the torrc
6872 option HiddenServiceStatistics to "1" by default. (This keeps
6873 track only of the fraction of traffic used by hidden services, and
6874 the total number of hidden services in existence.) Closes
6876 - Client now uses an introduction point failure cache to know when
6877 to fetch or keep a descriptor in their cache. Previously, failures
6878 were recorded implicitly, but not explicitly remembered. Closes
6881 o Minor features (testing, authorities, documentation):
6882 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
6883 explicitly manage consensus flags in testing networks. Patch by
6884 "robgjansen", modified by "teor". Implements part of ticket 14882.
6886 o Minor bugfixes (security, exit policies):
6887 - ExitPolicyRejectPrivate now also rejects the relay's published
6888 IPv6 address (if any), and any publicly routable IPv4 or IPv6
6889 addresses on any local interfaces. ticket 17027. Patch by "teor".
6890 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
6892 o Minor bug fixes (torrc exit policies):
6893 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
6894 produce IPv6 wildcard addresses. Previously they would produce
6895 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
6896 of bug 16069; bugfix on 0.2.4.7-alpha.
6897 - When parsing torrc ExitPolicies, we now warn for a number of cases
6898 where the user's intent is likely to differ from Tor's actual
6899 behavior. These include: using an IPv4 address with an accept6 or
6900 reject6 line; using "private" on an accept6 or reject6 line; and
6901 including any ExitPolicy lines after accept *:* or reject *:*.
6902 Related to ticket 16069.
6903 - When parsing torrc ExitPolicies, we now issue an info-level
6904 message when expanding an "accept/reject *" line to include both
6905 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
6906 - In each instance above, usage advice is provided to avoid the
6907 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
6908 16069; bugfix on 0.2.4.7-alpha.
6910 o Minor bugfixes (authority):
6911 - Don't assign "HSDir" to a router if it isn't Valid and Running.
6912 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
6913 - Downgrade log messages about Ed25519 key issues if they are in old
6914 cached router descriptors. Fixes part of bug 16286; bugfix
6916 - When we find an Ed25519 key issue in a cached descriptor, stop
6917 saying the descriptor was just "uploaded". Fixes another part of
6918 bug 16286; bugfix on 0.2.7.2-alpha.
6920 o Minor bugfixes (control port):
6921 - Repair a warning and a spurious result when getting the maximum
6922 number of file descriptors from the controller. Fixes bug 16697;
6923 bugfix on 0.2.7.2-alpha.
6925 o Minor bugfixes (correctness):
6926 - When calling channel_free_list(), avoid calling smartlist_remove()
6927 while inside a FOREACH loop. This partially reverts commit
6928 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
6929 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
6931 o Minor bugfixes (documentation):
6932 - Advise users on how to configure separate IPv4 and IPv6 exit
6933 policies in the manpage and sample torrcs. Related to ticket 16069.
6934 - Fix the usage message of tor-resolve(1) so that it no longer lists
6935 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
6936 - Fix an error in the manual page and comments for
6937 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
6938 required "ORPort connectivity". While this is true, it is in no
6939 way unique to the HSDir flag. Of all the flags, only HSDirs need a
6940 DirPort configured in order for the authorities to assign that
6941 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
6944 o Minor bugfixes (Ed25519):
6945 - Fix a memory leak when reading router descriptors with expired
6946 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
6948 o Minor bugfixes (linux seccomp2 sandbox):
6949 - Allow bridge authorities to run correctly under the seccomp2
6950 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
6951 - Allow routers with ed25519 keys to run correctly under the
6952 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
6954 o Minor bugfixes (open file limit):
6955 - Fix set_max_file_descriptors() to set by default the max open file
6956 limit to the current limit when setrlimit() fails. Fixes bug
6957 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
6959 o Minor bugfixes (portability):
6960 - Try harder to normalize the exit status of the Tor process to the
6961 standard-provided range. Fixes bug 16975; bugfix on every version
6963 - Check correctly for Windows socket errors in the workqueue
6964 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
6965 - Fix the behavior of crypto_rand_time_range() when told to consider
6966 times before 1970. (These times were possible when running in a
6967 simulated network environment where time()'s output starts at
6968 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
6969 - Restore correct operation of TLS client-cipher detection on
6970 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
6972 o Minor bugfixes (relay):
6973 - Ensure that worker threads actually exit when a fatal error or
6974 shutdown is indicated. This fix doesn't currently affect the
6975 behavior of Tor, because Tor workers never indicates fatal error
6976 or shutdown except in the unit tests. Fixes bug 16868; bugfix
6978 - Unblock threads before releasing the work queue mutex to ensure
6979 predictable scheduling behavior. Fixes bug 16644; bugfix
6982 o Code simplification and refactoring:
6983 - Change the function that's called when we need to retry all
6984 downloads so that it only reschedules the downloads to happen
6985 immediately, rather than launching them all at once itself. This
6986 further simplifies Tor's callgraph.
6987 - Move some format-parsing functions out of crypto.c and
6988 crypto_curve25519.c into crypto_format.c and/or util_format.c.
6989 - Move the client-only parts of init_keys() into a separate
6990 function. Closes ticket 16763.
6991 - Simplify the microdesc_free() implementation so that it no longer
6992 appears (to code analysis tools) to potentially invoke a huge
6993 suite of other microdesc functions.
6994 - Simply the control graph further by deferring the inner body of
6995 directory_all_unreachable() into a callback. Closes ticket 16762.
6996 - Treat the loss of an owning controller as equivalent to a SIGTERM
6997 signal. This removes a tiny amount of duplicated code, and
6998 simplifies our callgraph. Closes ticket 16788.
6999 - When generating an event to send to the controller, we no longer
7000 put the event over the network immediately. Instead, we queue
7001 these events, and use a Libevent callback to deliver them. This
7002 change simplifies Tor's callgraph by reducing the number of
7003 functions from which all other Tor functions are reachable. Closes
7005 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
7006 that try to scan or compile every file on Unix won't decide that
7008 - Remove the unused "nulterminate" argument from buf_pullup().
7011 - Recommend a 40 GB example AccountingMax in torrc.sample rather
7012 than a 4 GB max. Closes ticket 16742.
7013 - Include the TUNING document in our source tarball. It is referred
7014 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
7018 - The internal pure-C tor-fw-helper tool is now removed from the Tor
7019 distribution, in favor of the pure-Go clone available from
7020 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
7021 used by the C tor-fw-helper are not, in our opinion, very
7022 confidence- inspiring in their secure-programming techniques.
7023 Closes ticket 13338.
7024 - Remove the code that would try to aggressively flush controller
7025 connections while writing to them. This code was introduced in
7026 0.1.2.7-alpha, in order to keep output buffers from exceeding
7027 their limits. But there is no longer a maximum output buffer size,
7028 and flushing data in this way caused some undesirable recursions
7029 in our call graph. Closes ticket 16480.
7032 - Make "bridges+hs" the default test network. This tests almost all
7033 tor functionality during make test-network, while allowing tests
7034 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
7035 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
7036 (chutney). Patches by "teor".
7037 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
7038 by-side in the same parent directory. Closes ticket 16903. Patch
7040 - Use environment variables rather than autoconf substitutions to
7041 send variables from the build system to the test scripts. This
7042 change should be easier to maintain, and cause 'make distcheck' to
7043 work better than before. Fixes bug 17148.
7044 - Add a new set of callgraph analysis scripts that use clang to
7045 produce a list of which Tor functions are reachable from which
7046 other Tor functions. We're planning to use these to help simplify
7047 our code structure by identifying illogical dependencies.
7048 - Add new 'test-full' and 'test-full-online' targets to run all
7049 tests, including integration tests with stem and chutney.
7050 - Make the test-workqueue test work on Windows by initializing the
7051 network before we begin.
7052 - New make target (make test-network-all) to run multiple applicable
7053 chutney test cases. Patch from Teor; closes 16953.
7054 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
7055 functions in dns.c. Implements a portion of ticket 16831.
7056 - When building Tor with testing coverage enabled, run Chutney tests
7057 (if any) using the 'tor-cov' coverage binary.
7058 - When running test-network or test-stem, check for the absence of
7059 stem/chutney before doing any build operations.
7062 Changes in version 0.2.7.2-alpha - 2015-07-27
7063 This, the second alpha in the Tor 0.2.7 series, has a number of new
7064 features, including a way to manually pick the number of introduction
7065 points for hidden services, and the much stronger Ed25519 signing key
7066 algorithm for regular Tor relays (including support for encrypted
7067 offline identity keys in the new algorithm).
7069 Support for Ed25519 on relays is currently limited to signing router
7070 descriptors; later alphas in this series will extend Ed25519 key
7071 support to more parts of the Tor protocol.
7073 o Major features (Ed25519 identity keys, Proposal 220):
7074 - All relays now maintain a stronger identity key, using the Ed25519
7075 elliptic curve signature format. This master key is designed so
7076 that it can be kept offline. Relays also generate an online
7077 signing key, and a set of other Ed25519 keys and certificates.
7078 These are all automatically regenerated and rotated as needed.
7079 Implements part of ticket 12498.
7080 - Directory authorities now vote on Ed25519 identity keys along with
7081 RSA1024 keys. Implements part of ticket 12498.
7082 - Directory authorities track which Ed25519 identity keys have been
7083 used with which RSA1024 identity keys, and do not allow them to
7084 vary freely. Implements part of ticket 12498.
7085 - Microdescriptors now include Ed25519 identity keys. Implements
7086 part of ticket 12498.
7087 - Add support for offline encrypted Ed25519 master keys. To use this
7088 feature on your tor relay, run "tor --keygen" to make a new master
7089 key (or to make a new signing key if you already have a master
7090 key). Closes ticket 13642.
7092 o Major features (Hidden services):
7093 - Add the torrc option HiddenServiceNumIntroductionPoints, to
7094 specify a fixed number of introduction points. Its maximum value
7095 is 10 and default is 3. Using this option can increase a hidden
7096 service's reliability under load, at the cost of making it more
7097 visible that the hidden service is facing extra load. Closes
7099 - Remove the adaptive algorithm for choosing the number of
7100 introduction points, which used to change the number of
7101 introduction points (poorly) depending on the number of
7102 connections the HS sees. Closes ticket 4862.
7104 o Major features (onion key cross-certification):
7105 - Relay descriptors now include signatures of their own identity
7106 keys, made using the TAP and ntor onion keys. These signatures
7107 allow relays to prove ownership of their own onion keys. Because
7108 of this change, microdescriptors will no longer need to include
7109 RSA identity keys. Implements proposal 228; closes ticket 12499.
7111 o Major features (performance):
7112 - Improve the runtime speed of Ed25519 operations by using the
7113 public-domain Ed25519-donna by Andrew M. ("floodyberry").
7114 Implements ticket 16467.
7115 - Improve the runtime speed of the ntor handshake by using an
7116 optimized curve25519 basepoint scalarmult implementation from the
7117 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
7118 ideas by Adam Langley. Implements ticket 9663.
7120 o Major bugfixes (client-side privacy, also in 0.2.6.9):
7121 - Properly separate out each SOCKSPort when applying stream
7122 isolation. The error occurred because each port's session group
7123 was being overwritten by a default value when the listener
7124 connection was initialized. Fixes bug 16247; bugfix on
7125 0.2.6.3-alpha. Patch by "jojelino".
7127 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
7128 - Stop refusing to store updated hidden service descriptors on a
7129 client. This reverts commit 9407040c59218 (which indeed fixed bug
7130 14219, but introduced a major hidden service reachability
7131 regression detailed in bug 16381). This is a temporary fix since
7132 we can live with the minor issue in bug 14219 (it just results in
7133 some load on the network) but the regression of 16381 is too much
7134 of a setback. First-round fix for bug 16381; bugfix
7137 o Major bugfixes (hidden services):
7138 - When cannibalizing a circuit for an introduction point, always
7139 extend to the chosen exit node (creating a 4 hop circuit).
7140 Previously Tor would use the current circuit exit node, which
7141 changed the original choice of introduction point, and could cause
7142 the hidden service to skip excluded introduction points or
7143 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
7146 o Major bugfixes (open file limit):
7147 - The open file limit wasn't checked before calling
7148 tor_accept_socket_nonblocking(), which would make Tor exceed the
7149 limit. Now, before opening a new socket, Tor validates the open
7150 file limit just before, and if the max has been reached, return an
7151 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
7153 o Major bugfixes (stability, also in 0.2.6.10):
7154 - Stop crashing with an assertion failure when parsing certain kinds
7155 of malformed or truncated microdescriptors. Fixes bug 16400;
7156 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7157 by "cypherpunks_backup".
7158 - Stop random client-side assertion failures that could occur when
7159 connecting to a busy hidden service, or connecting to a hidden
7160 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7163 o Minor features (directory authorities, security, also in 0.2.6.9):
7164 - The HSDir flag given by authorities now requires the Stable flag.
7165 For the current network, this results in going from 2887 to 2806
7166 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7167 attack by raising the effort for a relay to become Stable to
7168 require at the very least 7 days, while maintaining the 96 hours
7169 uptime requirement for HSDir. Implements ticket 8243.
7171 o Minor features (client):
7172 - Relax the validation of hostnames in SOCKS5 requests, allowing the
7173 character '_' to appear, in order to cope with domains observed in
7174 the wild that are serving non-RFC compliant records. Resolves
7176 - Relax the validation done to hostnames in SOCKS5 requests, and
7177 allow a single trailing '.' to cope with clients that pass FQDNs
7178 using that syntax to explicitly indicate that the domain name is
7179 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
7180 - Add GroupWritable and WorldWritable options to unix-socket based
7181 SocksPort and ControlPort options. These options apply to a single
7182 socket, and override {Control,Socks}SocketsGroupWritable. Closes
7185 o Minor features (control protocol):
7186 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
7187 the control protocol. Resolves ticket 15358.
7189 o Minor features (directory authorities):
7190 - Directory authorities no longer vote against the "Fast", "Stable",
7191 and "HSDir" flags just because they were going to vote against
7192 "Running": if the consensus turns out to be that the router was
7193 running, then the authority's vote should count. Patch from Peter
7194 Retzlaff; closes issue 8712.
7196 o Minor features (geoip, also in 0.2.6.10):
7197 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
7198 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
7200 o Minor features (hidden services):
7201 - Add the new options "HiddenServiceMaxStreams" and
7202 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
7203 limit the maximum number of simultaneous streams per circuit, and
7204 optionally tear down the circuit when the limit is exceeded. Part
7207 o Minor features (portability):
7208 - Use C99 variadic macros when the compiler is not GCC. This avoids
7209 failing compilations on MSVC, and fixes a log-file-based race
7210 condition in our old workarounds. Original patch from Gisle Vanem.
7212 o Minor bugfixes (compilation, also in 0.2.6.9):
7213 - Build with --enable-systemd correctly when libsystemd is
7214 installed, but systemd is not. Fixes bug 16164; bugfix on
7215 0.2.6.3-alpha. Patch from Peter Palfrader.
7217 o Minor bugfixes (controller):
7218 - Add the descriptor ID in each HS_DESC control event. It was
7219 missing, but specified in control-spec.txt. Fixes bug 15881;
7220 bugfix on 0.2.5.2-alpha.
7222 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
7223 - Check for failures from crypto_early_init, and refuse to continue.
7224 A previous typo meant that we could keep going with an
7225 uninitialized crypto library, and would have OpenSSL initialize
7226 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7227 when implementing ticket 4900. Patch by "teor".
7229 o Minor bugfixes (hidden services):
7230 - Fix a crash when reloading configuration while at least one
7231 configured and one ephemeral hidden service exists. Fixes bug
7232 16060; bugfix on 0.2.7.1-alpha.
7233 - Avoid crashing with a double-free bug when we create an ephemeral
7234 hidden service but adding it fails for some reason. Fixes bug
7235 16228; bugfix on 0.2.7.1-alpha.
7237 o Minor bugfixes (Linux seccomp2 sandbox):
7238 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
7239 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
7241 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
7242 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7243 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7244 on 0.2.6.3-alpha. Patch from "teor".
7246 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
7247 - Fix sandboxing to work when running as a relay, by allowing the
7248 renaming of secret_id_key, and allowing the eventfd2 and futex
7249 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
7251 - Allow systemd connections to work with the Linux seccomp2 sandbox
7252 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7255 o Minor bugfixes (relay):
7256 - Fix a rarely-encountered memory leak when failing to initialize
7257 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
7260 o Minor bugfixes (systemd):
7261 - Fix an accidental formatting error that broke the systemd
7262 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
7263 - Tor's systemd unit file no longer contains extraneous spaces.
7264 These spaces would sometimes confuse tools like deb-systemd-
7265 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
7267 o Minor bugfixes (tests):
7268 - Use the configured Python executable when running test-stem-full.
7269 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
7271 o Minor bugfixes (tests, also in 0.2.6.9):
7272 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7273 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7275 o Minor bugfixes (threads, comments):
7276 - Always initialize return value in compute_desc_id in rendcommon.c
7277 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
7278 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
7279 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
7280 - Remove undefined directive-in-macro in test_util_writepid clang
7281 3.7 complains that using a preprocessor directive inside a macro
7282 invocation in test_util_writepid in test_util.c is undefined.
7283 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
7285 o Code simplification and refactoring:
7286 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
7287 to ensure they remain consistent and visible everywhere.
7288 - Remove some vestigial workarounds for the MSVC6 compiler. We
7289 haven't supported that in ages.
7290 - The link authentication code has been refactored for better
7291 testability and reliability. It now uses code generated with the
7292 "trunnel" binary encoding generator, to reduce the risk of bugs
7293 due to programmer error. Done as part of ticket 12498.
7296 - Include a specific and (hopefully) accurate documentation of the
7297 torrc file's meta-format in doc/torrc_format.txt. This is mainly
7298 of interest to people writing programs to parse or generate torrc
7299 files. This document is not a commitment to long-term
7300 compatibility; some aspects of the current format are a bit
7301 ridiculous. Closes ticket 2325.
7304 - Tor no longer supports copies of OpenSSL that are missing support
7305 for Elliptic Curve Cryptography. (We began using ECC when
7306 available in 0.2.4.8-alpha, for more safe and efficient key
7307 negotiation.) In particular, support for at least one of P256 or
7308 P224 is now required, with manual configuration needed if only
7309 P224 is available. Resolves ticket 16140.
7310 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
7311 on an operating system that has not upgraded to OpenSSL 1.0 or
7312 later, and you compile Tor from source, you will need to install a
7313 more recent OpenSSL to link Tor against.) These versions of
7314 OpenSSL are still supported by the OpenSSL, but the numerous
7315 cryptographic improvements in later OpenSSL releases makes them a
7316 clear choice. Resolves ticket 16034.
7317 - Remove the HidServDirectoryV2 option. Now all relays offer to
7318 store hidden service descriptors. Related to 16543.
7319 - Remove the VoteOnHidServDirectoriesV2 option, since all
7320 authorities have long set it to 1. Closes ticket 16543.
7323 - Document use of coverity, clang static analyzer, and clang dynamic
7324 undefined behavior and address sanitizers in doc/HACKING. Include
7325 detailed usage instructions in the blacklist. Patch by "teor".
7326 Closes ticket 15817.
7327 - The link authentication protocol code now has extensive tests.
7328 - The relay descriptor signature testing code now has
7330 - The test_workqueue program now runs faster, and is enabled by
7331 default as a part of "make check".
7332 - Now that OpenSSL has its own scrypt implementation, add an unit
7333 test that checks for interoperability between libscrypt_scrypt()
7334 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
7335 and rely on EVP_PBE_scrypt() whenever possible. Resolves
7339 Changes in version 0.2.6.10 - 2015-07-12
7340 Tor version 0.2.6.10 fixes some significant stability and hidden
7341 service client bugs, bulletproofs the cryptography init process, and
7342 fixes a bug when using the sandbox code with some older versions of
7343 Linux. Everyone running an older version, especially an older version
7344 of 0.2.6, should upgrade.
7346 o Major bugfixes (hidden service clients, stability):
7347 - Stop refusing to store updated hidden service descriptors on a
7348 client. This reverts commit 9407040c59218 (which indeed fixed bug
7349 14219, but introduced a major hidden service reachability
7350 regression detailed in bug 16381). This is a temporary fix since
7351 we can live with the minor issue in bug 14219 (it just results in
7352 some load on the network) but the regression of 16381 is too much
7353 of a setback. First-round fix for bug 16381; bugfix
7356 o Major bugfixes (stability):
7357 - Stop crashing with an assertion failure when parsing certain kinds
7358 of malformed or truncated microdescriptors. Fixes bug 16400;
7359 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7360 by "cypherpunks_backup".
7361 - Stop random client-side assertion failures that could occur when
7362 connecting to a busy hidden service, or connecting to a hidden
7363 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7366 o Minor features (geoip):
7367 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
7368 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
7370 o Minor bugfixes (crypto error-handling):
7371 - Check for failures from crypto_early_init, and refuse to continue.
7372 A previous typo meant that we could keep going with an
7373 uninitialized crypto library, and would have OpenSSL initialize
7374 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7375 when implementing ticket 4900. Patch by "teor".
7377 o Minor bugfixes (Linux seccomp2 sandbox):
7378 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7379 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7380 on 0.2.6.3-alpha. Patch from "teor".
7383 Changes in version 0.2.6.9 - 2015-06-11
7384 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
7385 requirements for receiving an HSDir flag, and addresses some other small
7386 bugs in the systemd and sandbox code. Clients using circuit isolation
7387 should upgrade; all directory authorities should upgrade.
7389 o Major bugfixes (client-side privacy):
7390 - Properly separate out each SOCKSPort when applying stream
7391 isolation. The error occurred because each port's session group was
7392 being overwritten by a default value when the listener connection
7393 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
7396 o Minor feature (directory authorities, security):
7397 - The HSDir flag given by authorities now requires the Stable flag.
7398 For the current network, this results in going from 2887 to 2806
7399 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7400 attack by raising the effort for a relay to become Stable which
7401 takes at the very least 7 days to do so and by keeping the 96
7402 hours uptime requirement for HSDir. Implements ticket 8243.
7404 o Minor bugfixes (compilation):
7405 - Build with --enable-systemd correctly when libsystemd is
7406 installed, but systemd is not. Fixes bug 16164; bugfix on
7407 0.2.6.3-alpha. Patch from Peter Palfrader.
7409 o Minor bugfixes (Linux seccomp2 sandbox):
7410 - Fix sandboxing to work when running as a relaymby renaming of
7411 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
7412 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
7413 - Allow systemd connections to work with the Linux seccomp2 sandbox
7414 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7417 o Minor bugfixes (tests):
7418 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7419 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7422 Changes in version 0.2.6.8 - 2015-05-21
7423 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
7424 fixes an authority-side bug in assigning the HSDir flag. All directory
7425 authorities should upgrade.
7427 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
7428 - Revert commit that made directory authorities assign the HSDir
7429 flag to relays without a DirPort; this was bad because such relays
7430 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7433 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7434 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7435 a client authorized hidden service. Fixes bug 15823; bugfix
7438 o Minor features (geoip):
7439 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
7440 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
7444 Changes in version 0.2.7.1-alpha - 2015-05-12
7445 Tor 0.2.7.1-alpha is the first alpha release in its series. It
7446 includes numerous small features and bugfixes against previous Tor
7447 versions, and numerous small infrastructure improvements. The most
7448 notable features are several new ways for controllers to interact with
7449 the hidden services subsystem.
7451 o New system requirements:
7452 - Tor no longer includes workarounds to support Libevent versions
7453 before 1.3e. Libevent 2.0 or later is recommended. Closes
7456 o Major features (controller):
7457 - Add the ADD_ONION and DEL_ONION commands that allow the creation
7458 and management of hidden services via the controller. Closes
7460 - New "GETINFO onions/current" and "GETINFO onions/detached"
7461 commands to get information about hidden services created via the
7462 controller. Part of ticket 6411.
7463 - New HSFETCH command to launch a request for a hidden service
7464 descriptor. Closes ticket 14847.
7465 - New HSPOST command to upload a hidden service descriptor. Closes
7466 ticket 3523. Patch by "DonnchaC".
7468 o Major bugfixes (hidden services):
7469 - Revert commit that made directory authorities assign the HSDir
7470 flag to relays without a DirPort; this was bad because such relays
7471 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7474 o Minor features (clock-jump tolerance):
7475 - Recover better when our clock jumps back many hours, like might
7476 happen for Tails or Whonix users who start with a very wrong
7477 hardware clock, use Tor to discover a more accurate time, and then
7478 fix their clock. Resolves part of ticket 8766.
7480 o Minor features (command-line interface):
7481 - Make --hash-password imply --hush to prevent unnecessary noise.
7482 Closes ticket 15542. Patch from "cypherpunks".
7483 - Print a warning whenever we find a relative file path being used
7484 as torrc option. Resolves issue 14018.
7486 o Minor features (controller):
7487 - Add DirAuthority lines for default directory authorities to the
7488 output of the "GETINFO config/defaults" command if not already
7489 present. Implements ticket 14840.
7490 - Controllers can now use "GETINFO hs/client/desc/id/..." to
7491 retrieve items from the client's hidden service descriptor cache.
7492 Closes ticket 14845.
7493 - Implement a new controller command "GETINFO status/fresh-relay-
7494 descs" to fetch a descriptor/extrainfo pair that was generated on
7495 demand just for the controller's use. Implements ticket 14784.
7497 o Minor features (DoS-resistance):
7498 - Make it harder for attackers to overload hidden services with
7499 introductions, by blocking multiple introduction requests on the
7500 same circuit. Resolves ticket 15515.
7502 o Minor features (geoip):
7503 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
7504 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
7507 o Minor features (HS popularity countermeasure):
7508 - To avoid leaking HS popularity, don't cycle the introduction point
7509 when we've handled a fixed number of INTRODUCE2 cells but instead
7510 cycle it when a random number of introductions is reached, thus
7511 making it more difficult for an attacker to find out the amount of
7512 clients that have used the introduction point for a specific HS.
7513 Closes ticket 15745.
7515 o Minor features (logging):
7516 - Include the Tor version in all LD_BUG log messages, since people
7517 tend to cut and paste those into the bugtracker. Implements
7520 o Minor features (pluggable transports):
7521 - When launching managed pluggable transports on Linux systems,
7522 attempt to have the kernel deliver a SIGTERM on tor exit if the
7523 pluggable transport process is still running. Resolves
7525 - When launching managed pluggable transports, setup a valid open
7526 stdin in the child process that can be used to detect if tor has
7527 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
7528 can be used by implementations to detect this new behavior.
7529 Resolves ticket 15435.
7531 o Minor features (testing):
7532 - Add a test to verify that the compiler does not eliminate our
7533 memwipe() implementation. Closes ticket 15377.
7534 - Add make rule `check-changes` to verify the format of changes
7535 files. Closes ticket 15180.
7536 - Add unit tests for control_event_is_interesting(). Add a compile-
7537 time check that the number of events doesn't exceed the capacity
7538 of control_event_t.event_mask. Closes ticket 15431, checks for
7539 bugs similar to 13085. Patch by "teor".
7540 - Command-line argument tests moved to Stem. Resolves ticket 14806.
7541 - Integrate the ntor, backtrace, and zero-length keys tests into the
7542 automake test suite. Closes ticket 15344.
7543 - Remove assertions during builds to determine Tor's test coverage.
7544 We don't want to trigger these even in assertions, so including
7545 them artificially makes our branch coverage look worse than it is.
7546 This patch provides the new test-stem-full and coverage-html-full
7547 configure options. Implements ticket 15400.
7549 o Minor bugfixes (build):
7550 - Improve out-of-tree builds by making non-standard rules work and
7551 clean up additional files and directories. Fixes bug 15053; bugfix
7554 o Minor bugfixes (command-line interface):
7555 - When "--quiet" is provided along with "--validate-config", do not
7556 write anything to stdout on success. Fixes bug 14994; bugfix
7558 - When complaining about bad arguments to "--dump-config", use
7561 o Minor bugfixes (configuration, unit tests):
7562 - Only add the default fallback directories when the DirAuthorities,
7563 AlternateDirAuthority, and FallbackDir directory config options
7564 are set to their defaults. The default fallback directory list is
7565 currently empty, this fix will only change tor's behavior when it
7566 has default fallback directories. Includes unit tests for
7567 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
7568 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
7570 o Minor bugfixes (correctness):
7571 - For correctness, avoid modifying a constant string in
7572 handle_control_postdescriptor. Fixes bug 15546; bugfix
7574 - Remove side-effects from tor_assert() calls. This was harmless,
7575 because we never disable assertions, but it is bad style and
7576 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
7579 o Minor bugfixes (hidden service):
7580 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7581 a client authorized hidden service. Fixes bug 15823; bugfix
7583 - Remove an extraneous newline character from the end of hidden
7584 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
7586 o Minor bugfixes (interface):
7587 - Print usage information for --dump-config when it is used without
7588 an argument. Also, fix the error message to use different wording
7589 and add newline at the end. Fixes bug 15541; bugfix
7592 o Minor bugfixes (logs):
7593 - When building Tor under Clang, do not include an extra set of
7594 parentheses in log messages that include function names. Fixes bug
7595 15269; bugfix on every released version of Tor when compiled with
7596 recent enough Clang.
7598 o Minor bugfixes (network):
7599 - When attempting to use fallback technique for network interface
7600 lookup, disregard loopback and multicast addresses since they are
7601 unsuitable for public communications.
7603 o Minor bugfixes (statistics):
7604 - Disregard the ConnDirectionStatistics torrc options when Tor is
7605 not a relay since in that mode of operation no sensible data is
7606 being collected and because Tor might run into measurement hiccups
7607 when running as a client for some time, then becoming a relay.
7608 Fixes bug 15604; bugfix on 0.2.2.35.
7610 o Minor bugfixes (test networks):
7611 - When self-testing reachability, use ExtendAllowPrivateAddresses to
7612 determine if local/private addresses imply reachability. The
7613 previous fix used TestingTorNetwork, which implies
7614 ExtendAllowPrivateAddresses, but this excluded rare configurations
7615 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
7616 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
7617 issue discovered by CJ Ess.
7619 o Minor bugfixes (testing):
7620 - Check for matching value in server response in ntor_ref.py. Fixes
7621 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
7623 - Set the severity correctly when testing
7624 get_interface_addresses_ifaddrs() and
7625 get_interface_addresses_win32(), so that the tests fail gracefully
7626 instead of triggering an assertion. Fixes bug 15759; bugfix on
7627 0.2.6.3-alpha. Reported by Nicolas Derive.
7629 o Code simplification and refactoring:
7630 - Move the hacky fallback code out of get_interface_address6() into
7631 separate function and get it covered with unit-tests. Resolves
7633 - Refactor hidden service client-side cache lookup to intelligently
7634 report its various failure cases, and disentangle failure cases
7635 involving a lack of introduction points. Closes ticket 14391.
7636 - Use our own Base64 encoder instead of OpenSSL's, to allow more
7637 control over the output. Part of ticket 15652.
7640 - Improve the descriptions of statistics-related torrc options in
7641 the manpage to describe rationale and possible uses cases. Fixes
7643 - Improve the layout and formatting of ./configure --help messages.
7644 Closes ticket 15024. Patch from "cypherpunks".
7645 - Standardize on the term "server descriptor" in the manual page.
7646 Previously, we had used "router descriptor", "server descriptor",
7647 and "relay descriptor" interchangeably. Part of ticket 14987.
7650 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
7651 and always use the internal Base64 decoder. The internal decoder
7652 has been part of tor since 0.2.0.10-alpha, and no one should
7653 be using the OpenSSL one. Part of ticket 15652.
7654 - Remove the 'tor_strclear()' function; use memwipe() instead.
7655 Closes ticket 14922.
7658 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
7659 fingerprinting we now recommend pluggable transports; for forward-
7660 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
7661 - Remove the undocumented "--digests" command-line option. It
7662 complicated our build process, caused subtle build issues on
7663 multiple platforms, and is now redundant since we started
7664 including git version identifiers. Closes ticket 14742.
7665 - Tor no longer contains checks for ancient directory cache versions
7666 that didn't know about microdescriptors.
7667 - Tor no longer contains workarounds for stat files generated by
7668 super-old versions of Tor that didn't choose guards sensibly.
7671 Changes in version 0.2.4.27 - 2015-04-06
7672 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
7673 could be used by an attacker to crash hidden services, or crash clients
7674 visiting hidden services. Hidden services should upgrade as soon as
7675 possible; clients should upgrade whenever packages become available.
7677 This release also backports a simple improvement to make hidden
7678 services a bit less vulnerable to denial-of-service attacks.
7680 o Major bugfixes (security, hidden service):
7681 - Fix an issue that would allow a malicious client to trigger an
7682 assertion failure and halt a hidden service. Fixes bug 15600;
7683 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7684 - Fix a bug that could cause a client to crash with an assertion
7685 failure when parsing a malformed hidden service descriptor. Fixes
7686 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7688 o Minor features (DoS-resistance, hidden service):
7689 - Introduction points no longer allow multiple INTRODUCE1 cells to
7690 arrive on the same circuit. This should make it more expensive for
7691 attackers to overwhelm hidden services with introductions.
7692 Resolves ticket 15515.
7695 Changes in version 0.2.5.12 - 2015-04-06
7696 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
7697 could be used by an attacker to crash hidden services, or crash clients
7698 visiting hidden services. Hidden services should upgrade as soon as
7699 possible; clients should upgrade whenever packages become available.
7701 This release also backports a simple improvement to make hidden
7702 services a bit less vulnerable to denial-of-service attacks.
7704 o Major bugfixes (security, hidden service):
7705 - Fix an issue that would allow a malicious client to trigger an
7706 assertion failure and halt a hidden service. Fixes bug 15600;
7707 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7708 - Fix a bug that could cause a client to crash with an assertion
7709 failure when parsing a malformed hidden service descriptor. Fixes
7710 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7712 o Minor features (DoS-resistance, hidden service):
7713 - Introduction points no longer allow multiple INTRODUCE1 cells to
7714 arrive on the same circuit. This should make it more expensive for
7715 attackers to overwhelm hidden services with introductions.
7716 Resolves ticket 15515.
7719 Changes in version 0.2.6.7 - 2015-04-06
7720 Tor 0.2.6.7 fixes two security issues that could be used by an
7721 attacker to crash hidden services, or crash clients visiting hidden
7722 services. Hidden services should upgrade as soon as possible; clients
7723 should upgrade whenever packages become available.
7725 This release also contains two simple improvements to make hidden
7726 services a bit less vulnerable to denial-of-service attacks.
7728 o Major bugfixes (security, hidden service):
7729 - Fix an issue that would allow a malicious client to trigger an
7730 assertion failure and halt a hidden service. Fixes bug 15600;
7731 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7732 - Fix a bug that could cause a client to crash with an assertion
7733 failure when parsing a malformed hidden service descriptor. Fixes
7734 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7736 o Minor features (DoS-resistance, hidden service):
7737 - Introduction points no longer allow multiple INTRODUCE1 cells to
7738 arrive on the same circuit. This should make it more expensive for
7739 attackers to overwhelm hidden services with introductions.
7740 Resolves ticket 15515.
7741 - Decrease the amount of reattempts that a hidden service performs
7742 when its rendezvous circuits fail. This reduces the computational
7743 cost for running a hidden service under heavy load. Resolves
7747 Changes in version 0.2.6.6 - 2015-03-24
7748 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
7750 It adds numerous safety, security, correctness, and performance
7751 improvements. Client programs can be configured to use more kinds of
7752 sockets, AutomapHosts works better, the multithreading backend is
7753 improved, cell transmission is refactored, test coverage is much
7754 higher, more denial-of-service attacks are handled, guard selection is
7755 improved to handle long-term guards better, pluggable transports
7756 should work a bit better, and some annoying hidden service performance
7757 bugs should be addressed.
7759 o Minor bugfixes (portability):
7760 - Use the correct datatype in the SipHash-2-4 function to prevent
7761 compilers from assuming any sort of alignment. Fixes bug 15436;
7762 bugfix on 0.2.5.3-alpha.
7764 Changes in version 0.2.6.5-rc - 2015-03-18
7765 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
7766 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
7768 o Major bugfixes (client):
7769 - Avoid crashing when making certain configuration option changes on
7770 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
7773 o Major bugfixes (pluggable transports):
7774 - Initialize the extended OR Port authentication cookie before
7775 launching pluggable transports. This prevents a race condition
7776 that occured when server-side pluggable transports would cache the
7777 authentication cookie before it has been (re)generated. Fixes bug
7778 15240; bugfix on 0.2.5.1-alpha.
7780 o Major bugfixes (portability):
7781 - Do not crash on startup when running on Solaris. Fixes a bug
7782 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
7785 o Minor features (heartbeat):
7786 - On relays, report how many connections we negotiated using each
7787 version of the Tor link protocols. This information will let us
7788 know if removing support for very old versions of the Tor
7789 protocols is harming the network. Closes ticket 15212.
7791 o Code simplification and refactoring:
7792 - Refactor main loop to extract the 'loop' part. This makes it
7793 easier to run Tor under Shadow. Closes ticket 15176.
7796 Changes in version 0.2.5.11 - 2015-03-17
7797 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
7799 It backports several bugfixes from the 0.2.6 branch, including a
7800 couple of medium-level security fixes for relays and exit nodes.
7801 It also updates the list of directory authorities.
7803 o Directory authority changes:
7804 - Remove turtles as a directory authority.
7805 - Add longclaw as a new (v3) directory authority. This implements
7806 ticket 13296. This keeps the directory authority count at 9.
7807 - The directory authority Faravahar has a new IP address. This
7808 closes ticket 14487.
7810 o Major bugfixes (crash, OSX, security):
7811 - Fix a remote denial-of-service opportunity caused by a bug in
7812 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7815 o Major bugfixes (relay, stability, possible security):
7816 - Fix a bug that could lead to a relay crashing with an assertion
7817 failure if a buffer of exactly the wrong layout was passed to
7818 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7819 0.2.0.10-alpha. Patch from 'cypherpunks'.
7820 - Do not assert if the 'data' pointer on a buffer is advanced to the
7821 very end of the buffer; log a BUG message instead. Only assert if
7822 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7824 o Major bugfixes (exit node stability):
7825 - Fix an assertion failure that could occur under high DNS load.
7826 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7827 diagnosed and fixed by "cypherpunks".
7829 o Major bugfixes (Linux seccomp2 sandbox):
7830 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7831 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7832 0.2.5.1-alpha. Patch from "sanic".
7834 o Minor features (controller):
7835 - New "GETINFO bw-event-cache" to get information about recent
7836 bandwidth events. Closes ticket 14128. Useful for controllers to
7837 get recent bandwidth history after the fix for ticket 13988.
7839 o Minor features (geoip):
7840 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7841 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7844 o Minor bugfixes (client, automapping):
7845 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
7846 no value follows the option. Fixes bug 14142; bugfix on
7847 0.2.4.7-alpha. Patch by "teor".
7848 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
7849 14195; bugfix on 0.1.0.1-rc.
7851 o Minor bugfixes (compilation):
7852 - Build without warnings with the stock OpenSSL srtp.h header, which
7853 has a duplicate declaration of SSL_get_selected_srtp_profile().
7854 Fixes bug 14220; this is OpenSSL's bug, not ours.
7856 o Minor bugfixes (directory authority):
7857 - Allow directory authorities to fetch more data from one another if
7858 they find themselves missing lots of votes. Previously, they had
7859 been bumping against the 10 MB queued data limit. Fixes bug 14261;
7860 bugfix on 0.1.2.5-alpha.
7861 - Enlarge the buffer to read bwauth generated files to avoid an
7862 issue when parsing the file in dirserv_read_measured_bandwidths().
7863 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
7865 o Minor bugfixes (statistics):
7866 - Increase period over which bandwidth observations are aggregated
7867 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7869 o Minor bugfixes (preventative security, C safety):
7870 - When reading a hexadecimal, base-32, or base-64 encoded value from
7871 a string, always overwrite the whole output buffer. This prevents
7872 some bugs where we would look at (but fortunately, not reveal)
7873 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7877 Changes in version 0.2.4.26 - 2015-03-17
7878 Tor 0.2.4.26 includes an updated list of directory authorities. It
7879 also backports a couple of stability and security bugfixes from 0.2.5
7882 o Directory authority changes:
7883 - Remove turtles as a directory authority.
7884 - Add longclaw as a new (v3) directory authority. This implements
7885 ticket 13296. This keeps the directory authority count at 9.
7886 - The directory authority Faravahar has a new IP address. This
7887 closes ticket 14487.
7889 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
7890 - Fix an assertion failure that could occur under high DNS load.
7891 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7892 diagnosed and fixed by "cypherpunks".
7894 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
7895 - Fix a bug that could lead to a relay crashing with an assertion
7896 failure if a buffer of exactly the wrong layout was passed to
7897 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7898 0.2.0.10-alpha. Patch from 'cypherpunks'.
7899 - Do not assert if the 'data' pointer on a buffer is advanced to the
7900 very end of the buffer; log a BUG message instead. Only assert if
7901 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7903 o Minor features (geoip):
7904 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7905 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7908 Changes in version 0.2.6.4-rc - 2015-03-09
7909 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
7910 attacker might be able to use in order to crash certain Tor
7911 directories. It also resolves some minor issues left over from, or
7912 introduced in, Tor 0.2.6.3-alpha or earlier.
7914 o Major bugfixes (crash, OSX, security):
7915 - Fix a remote denial-of-service opportunity caused by a bug in
7916 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7919 o Major bugfixes (relay, stability, possible security):
7920 - Fix a bug that could lead to a relay crashing with an assertion
7921 failure if a buffer of exactly the wrong layout is passed to
7922 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7923 0.2.0.10-alpha. Patch from "cypherpunks".
7924 - Do not assert if the 'data' pointer on a buffer is advanced to the
7925 very end of the buffer; log a BUG message instead. Only assert if
7926 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7928 o Major bugfixes (FreeBSD IPFW transparent proxy):
7929 - Fix address detection with FreeBSD transparent proxies, when
7930 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
7933 o Major bugfixes (Linux seccomp2 sandbox):
7934 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
7935 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
7937 - Allow AF_UNIX hidden services to be used with the seccomp2
7938 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
7939 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7940 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7941 0.2.5.1-alpha. Patch from "sanic".
7943 o Minor features (controller):
7944 - Messages about problems in the bootstrap process now include
7945 information about the server we were trying to connect to when we
7946 noticed the problem. Closes ticket 15006.
7948 o Minor features (geoip):
7949 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7950 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7953 o Minor features (logs):
7954 - Quiet some log messages in the heartbeat and at startup. Closes
7957 o Minor bugfixes (certificate handling):
7958 - If an authority operator accidentally makes a signing certificate
7959 with a future publication time, do not discard its real signing
7960 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
7961 - Remove any old authority certificates that have been superseded
7962 for at least two days. Previously, we would keep superseded
7963 certificates until they expired, if they were published close in
7964 time to the certificate that superseded them. Fixes bug 11454;
7965 bugfix on 0.2.1.8-alpha.
7967 o Minor bugfixes (compilation):
7968 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
7970 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
7973 o Minor bugfixes (testing):
7974 - Fix endianness issues in unit test for resolve_my_address() to
7975 have it pass on big endian systems. Fixes bug 14980; bugfix on
7977 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
7978 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
7979 - When running the new 'make test-stem' target, use the configured
7980 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
7982 - When running the zero-length-keys tests, do not use the default
7983 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
7986 o Directory authority IP change:
7987 - The directory authority Faravahar has a new IP address. This
7988 closes ticket 14487.
7991 - Remove some lingering dead code that once supported mempools.
7992 Mempools were disabled by default in 0.2.5, and removed entirely
7993 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
7997 Changes in version 0.2.6.3-alpha - 2015-02-19
7998 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
7999 the 0.2.6.x series. It introduces support for more kinds of sockets,
8000 makes it harder to accidentally run an exit, improves our
8001 multithreading backend, incorporates several fixes for the
8002 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
8004 If no major regressions or security holes are found in this version,
8005 the next version will be a release candidate.
8007 o Deprecated versions:
8008 - Tor relays older than 0.2.4.18-rc are no longer allowed to
8009 advertise themselves on the network. Closes ticket 13555.
8011 o Major features (security, unix domain sockets):
8012 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
8013 applications can reach Tor without having to create AF_INET or
8014 AF_INET6 sockets, meaning they can completely disable their
8015 ability to make non-Tor network connections. To create a socket of
8016 this type, use "SocksPort unix:/path/to/socket". Implements
8018 - Support mapping hidden service virtual ports to AF_UNIX sockets.
8019 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
8020 Implements ticket 11485.
8022 o Major features (changed defaults):
8023 - Prevent relay operators from unintentionally running exits: When a
8024 relay is configured as an exit node, we now warn the user unless
8025 the "ExitRelay" option is set to 1. We warn even more loudly if
8026 the relay is configured with the default exit policy, since this
8027 can indicate accidental misconfiguration. Setting "ExitRelay 0"
8028 stops Tor from running as an exit relay. Closes ticket 10067.
8030 o Major features (directory system):
8031 - When downloading server- or microdescriptors from a directory
8032 server, we no longer launch multiple simultaneous requests to the
8033 same server. This reduces load on the directory servers,
8034 especially when directory guards are in use. Closes ticket 9969.
8035 - When downloading server- or microdescriptors over a tunneled
8036 connection, do not limit the length of our requests to what the
8037 Squid proxy is willing to handle. Part of ticket 9969.
8038 - Authorities can now vote on the correct digests and latest
8039 versions for different software packages. This allows packages
8040 that include Tor to use the Tor authority system as a way to get
8041 notified of updates and their correct digests. Implements proposal
8042 227. Closes ticket 10395.
8044 o Major features (guards):
8045 - Introduce the Guardfraction feature to improves load balancing on
8046 guard nodes. Specifically, it aims to reduce the traffic gap that
8047 guard nodes experience when they first get the Guard flag. This is
8048 a required step if we want to increase the guard lifetime to 9
8049 months or greater. Closes ticket 9321.
8051 o Major features (performance):
8052 - Make the CPU worker implementation more efficient by avoiding the
8053 kernel and lengthening pipelines. The original implementation used
8054 sockets to transfer data from the main thread to the workers, and
8055 didn't allow any thread to be assigned more than a single piece of
8056 work at once. The new implementation avoids communications
8057 overhead by making requests in shared memory, avoiding kernel IO
8058 where possible, and keeping more requests in flight at once.
8059 Implements ticket 9682.
8061 o Major features (relay):
8062 - Raise the minimum acceptable configured bandwidth rate for bridges
8063 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
8064 20 KiB/sec.) Closes ticket 13822.
8066 o Major bugfixes (exit node stability):
8067 - Fix an assertion failure that could occur under high DNS load.
8068 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8069 diagnosed and fixed by "cypherpunks".
8071 o Major bugfixes (mixed relay-client operation):
8072 - When running as a relay and client at the same time (not
8073 recommended), if we decide not to use a new guard because we want
8074 to retry older guards, only close the locally-originating circuits
8075 passing through that guard. Previously we would close all the
8076 circuits through that guard. Fixes bug 9819; bugfix on
8077 0.2.1.1-alpha. Reported by "skruffy".
8079 o Minor features (build):
8080 - New --disable-system-torrc compile-time option to prevent Tor from
8081 looking for the system-wide torrc or torrc-defaults files.
8082 Resolves ticket 13037.
8084 o Minor features (controller):
8085 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
8086 events so controllers can observe circuit isolation inputs. Closes
8088 - ControlPort now supports the unix:/path/to/socket syntax as an
8089 alternative to the ControlSocket option, for consistency with
8090 SocksPort and HiddenServicePort. Closes ticket 14451.
8091 - New "GETINFO bw-event-cache" to get information about recent
8092 bandwidth events. Closes ticket 14128. Useful for controllers to
8093 get recent bandwidth history after the fix for ticket 13988.
8095 o Minor features (Denial of service resistance):
8096 - Count the total number of bytes used storing hidden service
8097 descriptors against the value of MaxMemInQueues. If we're low on
8098 memory, and more than 20% of our memory is used holding hidden
8099 service descriptors, free them until no more than 10% of our
8100 memory holds hidden service descriptors. Free the least recently
8101 fetched descriptors first. Resolves ticket 13806.
8102 - When we have recently been under memory pressure (over 3/4 of
8103 MaxMemInQueues is allocated), then allocate smaller zlib objects
8104 for small requests. Closes ticket 11791.
8106 o Minor features (geoip):
8107 - Update geoip and geoip6 files to the January 7 2015 Maxmind
8108 GeoLite2 Country database.
8110 o Minor features (guard nodes):
8111 - Reduce the time delay before saving guard status to disk from 10
8112 minutes to 30 seconds (or from one hour to 10 minutes if
8113 AvoidDiskWrites is set). Closes ticket 12485.
8115 o Minor features (hidden service):
8116 - Make Sybil attacks against hidden services harder by changing the
8117 minimum time required to get the HSDir flag from 25 hours up to 96
8118 hours. Addresses ticket 14149.
8119 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
8120 services to disable the anti-scanning feature introduced in
8121 0.2.6.2-alpha. With this option not set, a connection to an
8122 unlisted port closes the circuit. With this option set, only a
8123 RELAY_DONE cell is sent. Closes ticket 14084.
8125 o Minor features (interface):
8126 - Implement "-f -" command-line option to read torrc configuration
8127 from standard input, if you don't want to store the torrc file in
8128 the file system. Implements feature 13865.
8130 o Minor features (logging):
8131 - Add a count of unique clients to the bridge heartbeat message.
8132 Resolves ticket 6852.
8133 - Suppress "router info incompatible with extra info" message when
8134 reading extrainfo documents from cache. (This message got loud
8135 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
8137 - Elevate hidden service authorized-client message from DEBUG to
8138 INFO. Closes ticket 14015.
8140 o Minor features (stability):
8141 - Add assertions in our hash-table iteration code to check for
8142 corrupted values that could cause infinite loops. Closes
8145 o Minor features (systemd):
8146 - Various improvements and modernizations in systemd hardening
8147 support. Closes ticket 13805. Patch from Craig Andrews.
8149 o Minor features (testing networks):
8150 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
8151 and the default on a testing network to 2 minutes. Drop the
8152 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
8153 keep the default on a testing network at 30 seconds. This reduces
8154 HS bootstrap time to around 25 seconds. Also, change the default
8155 time in test-network.sh to match. Closes ticket 13401. Patch
8157 - Create TestingDirAuthVoteHSDir to correspond to
8158 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
8159 HSDir flag for the listed relays regardless of uptime or ORPort
8160 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
8161 Partial implementation for ticket 14067. Patch by "teor".
8163 o Minor features (tor2web mode):
8164 - Introduce the config option Tor2webRendezvousPoints, which allows
8165 clients in Tor2webMode to select a specific Rendezvous Point to be
8166 used in HS circuits. This might allow better performance for
8167 Tor2Web nodes. Implements ticket 12844.
8169 o Minor bugfixes (client DNS):
8170 - Report the correct cached DNS expiration times on SOCKS port or in
8171 DNS replies. Previously, we would report everything as "never
8172 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
8173 - Avoid a small memory leak when we find a cached answer for a
8174 reverse DNS lookup in a client-side DNS cache. (Remember, client-
8175 side DNS caching is off by default, and is not recommended.) Fixes
8176 bug 14259; bugfix on 0.2.0.1-alpha.
8178 o Minor bugfixes (client, automapping):
8179 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8180 no value follows the option. Fixes bug 14142; bugfix on
8181 0.2.4.7-alpha. Patch by "teor".
8182 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8183 14195; bugfix on 0.1.0.1-rc.
8184 - Prevent changes to other options from removing the wildcard value
8185 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
8187 - Allow MapAddress and AutomapHostsOnResolve to work together when
8188 an address is mapped into another address type (like .onion) that
8189 must be automapped at resolve time. Fixes bug 7555; bugfix
8192 o Minor bugfixes (client, bridges):
8193 - When we are using bridges and we had a network connectivity
8194 problem, only retry connecting to our currently configured
8195 bridges, not all bridges we know about and remember using. Fixes
8196 bug 14216; bugfix on 0.2.2.17-alpha.
8198 o Minor bugfixes (client, IPv6):
8199 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
8200 flag is not set; and not because the NoIPv4Traffic flag was set.
8201 Previously we'd looked at the NoIPv4Traffic flag for both types of
8202 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
8204 o Minor bugfixes (compilation):
8205 - The address of an array in the middle of a structure will always
8206 be non-NULL. clang recognises this and complains. Disable the
8207 tautologous and redundant check to silence this warning. Fixes bug
8208 14001; bugfix on 0.2.1.2-alpha.
8209 - Avoid warnings when building with systemd 209 or later. Fixes bug
8210 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
8211 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
8212 Addresses ticket 14188.
8213 - Build without warnings with the stock OpenSSL srtp.h header, which
8214 has a duplicate declaration of SSL_get_selected_srtp_profile().
8215 Fixes bug 14220; this is OpenSSL's bug, not ours.
8216 - Do not compile any code related to Tor2Web mode when Tor2Web mode
8217 is not enabled at compile time. Previously, this code was included
8218 in a disabled state. See discussion on ticket 12844.
8219 - Remove the --disable-threads configure option again. It was
8220 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
8221 14819; bugfix on 0.2.6.2-alpha.
8223 o Minor bugfixes (controller):
8224 - Report "down" in response to the "GETINFO entry-guards" command
8225 when relays are down with an unreachable_since value. Previously,
8226 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
8227 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
8228 14116; bugfix on 0.2.2.9-alpha.
8229 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
8230 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
8232 o Minor bugfixes (directory authority):
8233 - Allow directory authorities to fetch more data from one another if
8234 they find themselves missing lots of votes. Previously, they had
8235 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8236 bugfix on 0.1.2.5-alpha.
8237 - Do not attempt to download extrainfo documents which we will be
8238 unable to validate with a matching server descriptor. Fixes bug
8239 13762; bugfix on 0.2.0.1-alpha.
8240 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
8241 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
8242 - Enlarge the buffer to read bwauth generated files to avoid an
8243 issue when parsing the file in dirserv_read_measured_bandwidths().
8244 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8246 o Minor bugfixes (file handling):
8247 - Stop failing when key files are zero-length. Instead, generate new
8248 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
8249 on all versions of Tor. Patch by "teor".
8250 - Stop generating a fresh .old RSA onion key file when the .old file
8251 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
8252 - Avoid overwriting .old key files with empty key files.
8253 - Skip loading zero-length extrainfo store, router store, stats,
8254 state, and key files.
8255 - Avoid crashing when trying to reload a torrc specified as a
8256 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
8259 o Minor bugfixes (hidden services):
8260 - Close the introduction circuit when we have no more usable intro
8261 points, instead of waiting for it to time out. This also ensures
8262 that no follow-up HS descriptor fetch is triggered when the
8263 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
8264 - When fetching a hidden service descriptor for a down service that
8265 was recently up, do not keep refetching until we try the same
8266 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
8267 - Successfully launch Tor with a nonexistent hidden service
8268 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
8269 14106; bugfix on 0.2.6.2-alpha.
8271 o Minor bugfixes (logging):
8272 - Avoid crashing when there are more log domains than entries in
8273 domain_list. Bugfix on 0.2.3.1-alpha.
8274 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
8276 - Don't log messages to stdout twice when starting up. Fixes bug
8277 13993; bugfix on 0.2.6.1-alpha.
8279 o Minor bugfixes (parsing):
8280 - Stop accepting milliseconds (or other junk) at the end of
8281 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
8282 - Support two-number and three-number version numbers correctly, in
8283 case we change the Tor versioning system in the future. Fixes bug
8284 13661; bugfix on 0.0.8pre1.
8286 o Minor bugfixes (path counting):
8287 - When deciding whether the consensus lists any exit nodes, count
8288 the number listed in the consensus, not the number we have
8289 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
8290 - When deciding whether we have any exit nodes, only examine
8291 ExitNodes when the ExitNodes option is actually set. Fixes part of
8292 bug 14918; bugfix on 0.2.6.2-alpha.
8293 - Get rid of redundant and possibly scary warnings that we are
8294 missing directory information while we bootstrap. Fixes part of
8295 bug 14918; bugfix on 0.2.6.2-alpha.
8297 o Minor bugfixes (portability):
8298 - Fix the ioctl()-based network interface lookup code so that it
8299 will work on systems that have variable-length struct ifreq, for
8301 - Fix scheduler compilation on targets where char is unsigned. Fixes
8302 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
8304 o Minor bugfixes (sandbox):
8305 - Allow glibc fatal errors to be sent to stderr before Tor exits.
8306 Previously, glibc would try to write them to /dev/tty, and the
8307 sandbox would trap the call and make Tor exit prematurely. Fixes
8308 bug 14759; bugfix on 0.2.5.1-alpha.
8310 o Minor bugfixes (shutdown):
8311 - When shutting down, always call event_del() on lingering read or
8312 write events before freeing them. Otherwise, we risk double-frees
8313 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
8316 o Minor bugfixes (small memory leaks):
8317 - Avoid leaking memory when using IPv6 virtual address mappings.
8318 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
8321 o Minor bugfixes (statistics):
8322 - Increase period over which bandwidth observations are aggregated
8323 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
8325 o Minor bugfixes (systemd support):
8326 - Fix detection and operation of systemd watchdog. Fixes part of bug
8327 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
8328 - Run correctly under systemd with the RunAsDaemon option set. Fixes
8329 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
8330 - Inform the systemd supervisor about more changes in the Tor
8331 process status. Implements part of ticket 14141. Patch from
8333 - Cause the "--disable-systemd" option to actually disable systemd
8334 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
8337 o Minor bugfixes (TLS):
8338 - Check more thoroughly throughout the TLS code for possible
8339 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
8341 o Minor bugfixes (transparent proxy):
8342 - Use getsockname, not getsockopt, to retrieve the address for a
8343 TPROXY-redirected connection. Fixes bug 13796; bugfix
8346 o Code simplification and refactoring:
8347 - Move fields related to isolating and configuring client ports into
8348 a shared structure. Previously, they were duplicated across
8349 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
8350 to copy them correctly had been the cause of at least one bug in
8351 the past. Closes ticket 8546.
8352 - Refactor the get_interface_addresses_raw() doom-function into
8353 multiple smaller and simpler subfunctions. Cover the resulting
8354 subfunctions with unit-tests. Fixes a significant portion of
8356 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
8357 only for version <= 0.2.2.24 which is now deprecated. Closes
8359 - Remove a test for a long-defunct broken version-one
8363 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
8364 for writing the OpenBSD-specific tips. Resolves ticket 13702.
8365 - Make the tor-resolve documentation match its help string and its
8366 options. Resolves part of ticket 14325.
8367 - Log a more useful error message from tor-resolve when failing to
8368 look up a hidden service address. Resolves part of ticket 14325.
8370 o Downgraded warnings:
8371 - Don't warn when we've attempted to contact a relay using the wrong
8372 ntor onion key. Closes ticket 9635.
8375 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
8376 longer silently accepted as an alias for "ExitNodes".
8377 - The --enable-mempool and --enable-buf-freelists options, which
8378 were originally created to work around bad malloc implementations,
8379 no longer exist. They were off-by-default in 0.2.5. Closes
8383 - Make the checkdir/perms test complete successfully even if the
8384 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
8385 - Test that tor does not fail when key files are zero-length. Check
8386 that tor generates new keys, and overwrites the empty key files.
8387 - Test that tor generates new keys when keys are missing
8388 (existing behavior).
8389 - Test that tor does not overwrite key files that already contain
8390 data (existing behavior). Tests bug 13111. Patch by "teor".
8391 - New "make test-stem" target to run stem integration tests.
8392 Requires that the "STEM_SOURCE_DIR" environment variable be set.
8393 Closes ticket 14107.
8394 - Make the test_cmdline_args.py script work correctly on Windows.
8395 Patch from Gisle Vanem.
8396 - Move the slower unit tests into a new "./src/test/test-slow"
8397 binary that can be run independently of the other tests. Closes
8399 - Avoid undefined behavior when sampling huge values from the
8400 Laplace distribution. This made unittests fail on Raspberry Pi.
8401 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
8404 Changes in version 0.2.6.2-alpha - 2014-12-31
8405 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
8406 It introduces a major new backend for deciding when to send cells on
8407 channels, which should lead down the road to big performance
8408 increases. It contains security and statistics features for better
8409 work on hidden services, and numerous bugfixes.
8411 This release contains many new unit tests, along with major
8412 performance improvements for running testing networks using Chutney.
8413 Thanks to a series of patches contributed by "teor", testing networks
8414 should now bootstrap in seconds, rather than minutes.
8416 o Major features (relay, infrastructure):
8417 - Complete revision of the code that relays use to decide which cell
8418 to send next. Formerly, we selected the best circuit to write on
8419 each channel, but we didn't select among channels in any
8420 sophisticated way. Now, we choose the best circuits globally from
8421 among those whose channels are ready to deliver traffic.
8423 This patch implements a new inter-cmux comparison API, a global
8424 high/low watermark mechanism and a global scheduler loop for
8425 transmission prioritization across all channels as well as among
8426 circuits on one channel. This schedule is currently tuned to
8427 (tolerantly) avoid making changes in network performance, but it
8428 should form the basis for major circuit performance increases in
8429 the future. Code by Andrea; tuning by Rob Jansen; implements
8432 o Major features (hidden services):
8433 - Make HS port scanning more difficult by immediately closing the
8434 circuit when a user attempts to connect to a nonexistent port.
8435 Closes ticket 13667.
8436 - Add a HiddenServiceStatistics option that allows Tor relays to
8437 gather and publish statistics about the overall size and volume of
8438 hidden service usage. Specifically, when this option is turned on,
8439 an HSDir will publish an approximate number of hidden services
8440 that have published descriptors to it the past 24 hours. Also, if
8441 a relay has acted as a hidden service rendezvous point, it will
8442 publish the approximate amount of rendezvous cells it has relayed
8443 the past 24 hours. The statistics themselves are obfuscated so
8444 that the exact values cannot be derived. For more details see
8445 proposal 238, "Better hidden service stats from Tor relays". This
8446 feature is currently disabled by default. Implements feature 13192.
8448 o Major bugfixes (client, automap):
8449 - Repair automapping with IPv6 addresses. This automapping should
8450 have worked previously, but one piece of debugging code that we
8451 inserted to detect a regression actually caused the regression to
8452 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
8453 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
8456 o Major bugfixes (hidden services):
8457 - When closing an introduction circuit that was opened in parallel
8458 with others, don't mark the introduction point as unreachable.
8459 Previously, the first successful connection to an introduction
8460 point would make the other introduction points get marked as
8461 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
8463 o Directory authority changes:
8464 - Remove turtles as a directory authority.
8465 - Add longclaw as a new (v3) directory authority. This implements
8466 ticket 13296. This keeps the directory authority count at 9.
8468 o Major removed features:
8469 - Tor clients no longer support connecting to hidden services
8470 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
8471 option has been removed. (There shouldn't be any hidden services
8472 running these versions on the network.) Closes ticket 7803.
8474 o Minor features (client):
8475 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
8476 is enabled, reject requests with IP addresses as hostnames.
8477 Resolves ticket 13315.
8479 o Minor features (controller):
8480 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
8481 write an unscheduled heartbeat message to the log. Implements
8484 o Minor features (geoip):
8485 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
8488 o Minor features (hidden services):
8489 - When re-enabling the network, don't try to build introduction
8490 circuits until we have successfully built a circuit. This makes
8491 hidden services come up faster when the network is re-enabled.
8492 Patch from "akwizgran". Closes ticket 13447.
8493 - When we fail to retrieve a hidden service descriptor, send the
8494 controller an "HS_DESC FAILED" controller event. Implements
8496 - New HiddenServiceDirGroupReadable option to cause hidden service
8497 directories and hostname files to be created group-readable. Patch
8498 from "anon", David Stainton, and "meejah". Closes ticket 11291.
8500 o Minor features (systemd):
8501 - Where supported, when running with systemd, report successful
8502 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
8503 - When running with systemd, support systemd watchdog messages. Part
8504 of ticket 11016. Patch by Michael Scherer.
8506 o Minor features (transparent proxy):
8507 - Update the transparent proxy option checks to allow for both ipfw
8508 and pf on OS X. Closes ticket 14002.
8509 - Use the correct option when using IPv6 with transparent proxy
8510 support on Linux. Resolves 13808. Patch by Francisco Blas
8513 o Minor bugfixes (preventative security, C safety):
8514 - When reading a hexadecimal, base-32, or base-64 encoded value from
8515 a string, always overwrite the whole output buffer. This prevents
8516 some bugs where we would look at (but fortunately, not reveal)
8517 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
8519 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
8520 just the part that's used. This makes it harder for data leak bugs
8521 to occur in the event of other programming failures. Resolves
8524 o Minor bugfixes (client, microdescriptors):
8525 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
8526 computing which microdescriptors to download. This keeps us from
8527 erroneous download behavior if two microdescriptor digests ever
8528 have the same first 160 bits. Fixes part of bug 13399; bugfix
8530 - Reset a router's status if its microdescriptor digest changes,
8531 even if the first 160 bits remain the same. Fixes part of bug
8532 13399; bugfix on 0.2.3.1-alpha.
8534 o Minor bugfixes (compilation):
8535 - Silence clang warnings under --enable-expensive-hardening,
8536 including implicit truncation of 64 bit values to 32 bit, const
8537 char assignment to self, tautological compare, and additional
8538 parentheses around equality tests. Fixes bug 13577; bugfix
8540 - Fix a clang warning about checking whether an address in the
8541 middle of a structure is NULL. Fixes bug 14001; bugfix
8544 o Minor bugfixes (hidden services):
8545 - Correctly send a controller event when we find that a rendezvous
8546 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
8547 - Pre-check directory permissions for new hidden-services to avoid
8548 at least one case of "Bug: Acting on config options left us in a
8549 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
8550 - When adding a new hidden service (for example, via SETCONF), Tor
8551 no longer congratulates the user for running a relay. Fixes bug
8552 13941; bugfix on 0.2.6.1-alpha.
8553 - When fetching hidden service descriptors, we now check not only
8554 for whether we got the hidden service we had in mind, but also
8555 whether we got the particular descriptors we wanted. This prevents
8556 a class of inefficient but annoying DoS attacks by hidden service
8557 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
8560 o Minor bugfixes (Linux seccomp2 sandbox):
8561 - Make transparent proxy support work along with the seccomp2
8562 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
8563 by Francisco Blas Izquierdo Riera.
8564 - Fix a memory leak in tor-resolve when running with the sandbox
8565 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
8567 o Minor bugfixes (logging):
8568 - Downgrade warnings about RSA signature failures to info log level.
8569 Emit a warning when an extra info document is found incompatible
8570 with a corresponding router descriptor. Fixes bug 9812; bugfix
8572 - Make connection_ap_handshake_attach_circuit() log the circuit ID
8573 correctly. Fixes bug 13701; bugfix on 0.0.6.
8575 o Minor bugfixes (misc):
8576 - Stop allowing invalid address patterns like "*/24" that contain
8577 both a wildcard address and a bit prefix length. This affects all
8578 our address-range parsing code. Fixes bug 7484; bugfix
8581 o Minor bugfixes (testing networks, fast startup):
8582 - Allow Tor to build circuits using a consensus with no exits. If
8583 the consensus has no exits (typical of a bootstrapping test
8584 network), allow Tor to build circuits once enough descriptors have
8585 been downloaded. This assists in bootstrapping a testing Tor
8586 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
8588 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
8589 header to directory servers. This allows us to obtain consensuses
8590 promptly when the consensus interval is very short. This assists
8591 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
8592 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
8593 - Stop assuming that private addresses are local when checking
8594 reachability in a TestingTorNetwork. Instead, when testing, assume
8595 all OR connections are remote. (This is necessary due to many test
8596 scenarios running all relays on localhost.) This assists in
8597 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
8598 0.1.0.1-rc. Patch by "teor".
8599 - Avoid building exit circuits from a consensus with no exits. Now
8600 thanks to our fix for 13718, we accept a no-exit network as not
8601 wholly lost, but we need to remember not to try to build exit
8602 circuits on it. Closes ticket 13814; patch by "teor".
8603 - Stop requiring exits to have non-zero bandwithcapacity in a
8604 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
8605 ignore exit bandwidthcapacity. This assists in bootstrapping a
8606 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
8607 on 0.2.0.3-alpha. Patch by "teor".
8608 - Add "internal" to some bootstrap statuses when no exits are
8609 available. If the consensus does not contain Exits, Tor will only
8610 build internal circuits. In this case, relevant statuses will
8611 contain the word "internal" as indicated in the Tor control-
8612 spec.txt. When bootstrap completes, Tor will be ready to build
8613 internal circuits. If a future consensus contains Exits, exit
8614 circuits may become available. Fixes part of bug 13718; bugfix on
8615 0.2.4.10-alpha. Patch by "teor".
8616 - Decrease minimum consensus interval to 10 seconds when
8617 TestingTorNetwork is set, or 5 seconds for the first consensus.
8618 Fix assumptions throughout the code that assume larger intervals.
8619 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
8621 - Avoid excluding guards from path building in minimal test
8622 networks, when we're in a test network and excluding guards would
8623 exclude all relays. This typically occurs in incredibly small tor
8624 networks, and those using "TestingAuthVoteGuard *". Fixes part of
8625 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
8627 o Code simplification and refactoring:
8628 - Stop using can_complete_circuits as a global variable; access it
8629 with a function instead.
8630 - Avoid using operators directly as macro arguments: this lets us
8631 apply coccinelle transformations to our codebase more directly.
8632 Closes ticket 13172.
8633 - Combine the functions used to parse ClientTransportPlugin and
8634 ServerTransportPlugin into a single function. Closes ticket 6456.
8635 - Add inline functions and convenience macros for inspecting channel
8636 state. Refactor the code to use convenience macros instead of
8637 checking channel state directly. Fixes issue 7356.
8638 - Document all members of was_router_added_t and rename
8639 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
8640 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
8641 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
8642 constant instead of hardcoded value. Fixes issue 13840.
8643 - Refactor our generic strmap and digestmap types into a single
8644 implementation, so that we can add a new digest256map
8648 - Document the bridge-authority-only 'networkstatus-bridges' file.
8649 Closes ticket 13713; patch from "tom".
8650 - Fix typo in PredictedPortsRelevanceTime option description in
8651 manpage. Resolves issue 13707.
8652 - Stop suggesting that users specify relays by nickname: it isn't a
8653 good idea. Also, properly cross-reference how to specify relays in
8654 all parts of manual documenting options that take a list of
8655 relays. Closes ticket 13381.
8656 - Clarify the HiddenServiceDir option description in manpage to make
8657 it clear that relative paths are taken with respect to the current
8658 working directory. Also clarify that this behavior is not
8659 guaranteed to remain indefinitely. Fixes issue 13913.
8662 - New tests for many parts of channel, relay, and circuitmux
8663 functionality. Code by Andrea; part of 9262.
8664 - New tests for parse_transport_line(). Part of ticket 6456.
8665 - In the unit tests, use chgrp() to change the group of the unit
8666 test temporary directory to the current user, so that the sticky
8667 bit doesn't interfere with tests that check directory groups.
8669 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
8673 Changes in version 0.2.6.1-alpha - 2014-10-30
8674 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
8675 includes numerous code cleanups and new tests, and fixes a large
8676 number of annoying bugs. Out-of-memory conditions are handled better
8677 than in 0.2.5, pluggable transports have improved proxy support, and
8678 clients now use optimistic data for contacting hidden services. Also,
8679 we are now more robust to changes in what we consider a parseable
8680 directory object, so that tightening restrictions does not have a risk
8681 of introducing infinite download loops.
8683 This is the first alpha release in a new series, so expect there to be
8684 bugs. Users who would rather test out a more stable branch should stay
8685 with 0.2.5.x for now.
8687 o New compiler and system requirements:
8688 - Tor 0.2.6.x requires that your compiler support more of the C99
8689 language standard than before. The 'configure' script now detects
8690 whether your compiler supports C99 mid-block declarations and
8691 designated initializers. If it does not, Tor will not compile.
8693 We may revisit this requirement if it turns out that a significant
8694 number of people need to build Tor with compilers that don't
8695 bother implementing a 15-year-old standard. Closes ticket 13233.
8696 - Tor no longer supports systems without threading support. When we
8697 began working on Tor, there were several systems that didn't have
8698 threads, or where the thread support wasn't able to run the
8699 threads of a single process on multiple CPUs. That no longer
8700 holds: every system where Tor needs to run well now has threading
8701 support. Resolves ticket 12439.
8703 o Removed platform support:
8704 - We no longer include special code to build on Windows CE; as far
8705 as we know, nobody has used Tor on Windows CE in a very long time.
8706 Closes ticket 11446.
8708 o Major features (bridges):
8709 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
8710 transports if they are configured via the "TOR_PT_PROXY"
8711 environment variable. Implements proposal 232. Resolves
8714 o Major features (client performance, hidden services):
8715 - Allow clients to use optimistic data when connecting to a hidden
8716 service, which should remove a round-trip from hidden service
8717 initialization. See proposal 181 for details. Implements
8720 o Major features (directory system):
8721 - Upon receiving an unparseable directory object, if its digest
8722 matches what we expected, then don't try to download it again.
8723 Previously, when we got a descriptor we didn't like, we would keep
8724 trying to download it over and over. Closes ticket 11243.
8726 o Major features (sample torrc):
8727 - Add a new, infrequently-changed "torrc.minimal". This file is
8728 similar to torrc.sample, but it will change as infrequently as
8729 possible, for the benefit of users whose systems prompt them for
8730 intervention whenever a default configuration file is changed.
8731 Making this change allows us to update torrc.sample to be a more
8732 generally useful "sample torrc".
8734 o Major bugfixes (directory authorities):
8735 - Do not assign the HSDir flag to relays if they are not Valid, or
8736 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
8738 o Major bugfixes (directory bandwidth performance):
8739 - Don't flush the zlib buffer aggressively when compressing
8740 directory information for clients. This should save about 7% of
8741 the bandwidth currently used for compressed descriptors and
8742 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
8744 o Minor features (security, memory wiping):
8745 - Ensure we securely wipe keys from memory after
8746 crypto_digest_get_digest and init_curve25519_keypair_from_file
8747 have finished using them. Resolves ticket 13477.
8749 o Minor features (security, out-of-memory handling):
8750 - When handling an out-of-memory condition, allocate less memory for
8751 temporary data structures. Fixes issue 10115.
8752 - When handling an out-of-memory condition, consider more types of
8753 buffers, including those on directory connections, and zlib
8754 buffers. Resolves ticket 11792.
8757 - When identity keypair is generated for first time, log a
8758 congratulatory message that links to the new relay lifecycle
8759 document. Implements feature 10427.
8761 o Minor features (client):
8762 - Clients are now willing to send optimistic data (before they
8763 receive a 'connected' cell) to relays of any version. (Relays
8764 without support for optimistic data are no longer supported on the
8765 Tor network.) Resolves ticket 13153.
8767 o Minor features (directory authorities):
8768 - Don't list relays with a bandwidth estimate of 0 in the consensus.
8769 Implements a feature proposed during discussion of bug 13000.
8770 - In tor-gencert, report an error if the user provides the same
8771 argument more than once.
8772 - If a directory authority can't find a best consensus method in the
8773 votes that it holds, it now falls back to its favorite consensus
8774 method. Previously, it fell back to method 1. Neither of these is
8775 likely to get enough signatures, but "fall back to favorite"
8776 doesn't require us to maintain support an obsolete consensus
8777 method. Implements part of proposal 215.
8779 o Minor features (logging):
8780 - On Unix-like systems, you can now use named pipes as the target of
8781 the Log option, and other options that try to append to files.
8782 Closes ticket 12061. Patch from "carlo von lynX".
8783 - When opening a log file at startup, send it every log message that
8784 we generated between startup and opening it. Previously, log
8785 messages that were generated before opening the log file were only
8786 logged to stdout. Closes ticket 6938.
8787 - Add a TruncateLogFile option to overwrite logs instead of
8788 appending to them. Closes ticket 5583.
8790 o Minor features (portability, Solaris):
8791 - Threads are no longer disabled by default on Solaris; we believe
8792 that the versions of Solaris with broken threading support are all
8793 obsolete by now. Resolves ticket 9495.
8795 o Minor features (relay):
8796 - Re-check our address after we detect a changed IP address from
8797 getsockname(). This ensures that the controller command "GETINFO
8798 address" will report the correct value. Resolves ticket 11582.
8800 - A new AccountingRule option lets Relays set whether they'd like
8801 AccountingMax to be applied separately to inbound and outbound
8802 traffic, or applied to the sum of inbound and outbound traffic.
8803 Resolves ticket 961. Patch by "chobe".
8805 o Minor features (testing networks):
8806 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
8807 the "Exit" flag regardless of their uptime, bandwidth, or exit
8808 policy. TestingTorNetwork must be set for this option to have any
8809 effect. Previously, authorities would take up to 35 minutes to
8810 give nodes the Exit flag in a test network. Partially implements
8813 o Minor features (validation):
8814 - Check all date/time values passed to tor_timegm and
8815 parse_rfc1123_time for validity, taking leap years into account.
8816 Improves HTTP header validation. Implemented with bug 13476.
8817 - In correct_tm(), limit the range of values returned by system
8818 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
8819 This means we don't have to deal with negative or too large dates,
8820 even if a clock is wrong. Otherwise we might fail to read a file
8821 written by us which includes such a date. Fixes bug 13476.
8823 o Minor bugfixes (bridge clients):
8824 - When configured to use a bridge without an identity digest (not
8825 recommended), avoid launching an extra channel to it when
8826 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
8828 o Minor bugfixes (bridges):
8829 - When DisableNetwork is set, do not launch pluggable transport
8830 plugins, and if any are running, terminate them. Fixes bug 13213;
8831 bugfix on 0.2.3.6-alpha.
8833 o Minor bugfixes (C correctness):
8834 - Fix several instances of possible integer overflow/underflow/NaN.
8835 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
8837 - In circuit_build_times_calculate_timeout() in circuitstats.c,
8838 avoid dividing by zero in the pareto calculations. This traps
8839 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
8841 - Fix an integer overflow in format_time_interval(). Fixes bug
8842 13393; bugfix on 0.2.0.10-alpha.
8843 - Set the correct day of year value when the system's localtime(_r)
8844 or gmtime(_r) functions fail to set struct tm. Not externally
8845 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
8846 - Avoid unlikely signed integer overflow in tor_timegm on systems
8847 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
8849 o Minor bugfixes (client):
8850 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
8851 BadExit flag are not considered worthy candidates. Fixes bug
8852 13066; bugfix on 0.1.2.3-alpha.
8853 - Use the consensus schedule for downloading consensuses, and not
8854 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
8855 - Handle unsupported or malformed SOCKS5 requests properly by
8856 responding with the appropriate error message before closing the
8857 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
8859 o Minor bugfixes (client, torrc):
8860 - Stop modifying the value of our DirReqStatistics torrc option just
8861 because we're not a bridge or relay. This bug was causing Tor
8862 Browser users to write "DirReqStatistics 0" in their torrc files
8863 as if they had chosen to change the config. Fixes bug 4244; bugfix
8865 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
8866 that our options have changed every time we SIGHUP. Fixes bug
8867 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
8869 o Minor bugfixes (controller):
8870 - Return an error when the second or later arguments of the
8871 "setevents" controller command are invalid events. Previously we
8872 would return success while silently skipping invalid events. Fixes
8873 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
8875 o Minor bugfixes (directory system):
8876 - Always believe that v3 directory authorities serve extra-info
8877 documents, whether they advertise "caches-extra-info" or not.
8878 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8879 - When running as a v3 directory authority, advertise that you serve
8880 extra-info documents so that clients who want them can find them
8881 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8882 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
8883 Previously, directories offering BRIDGE_DIRINFO and some other
8884 flag (i.e. microdescriptors or extrainfo) would be ignored when
8885 looking for bridges. Partially fixes bug 13163; bugfix
8888 o Minor bugfixes (networking):
8889 - Check for orconns and use connection_or_close_for_error() rather
8890 than connection_mark_for_close() directly in the getsockopt()
8891 failure case of connection_handle_write_impl(). Fixes bug 11302;
8892 bugfix on 0.2.4.4-alpha.
8894 o Minor bugfixes (relay):
8895 - When generating our family list, remove spaces from around the
8896 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
8897 - If our previous bandwidth estimate was 0 bytes, allow publishing a
8898 new relay descriptor immediately. Fixes bug 13000; bugfix
8901 o Minor bugfixes (testing networks):
8902 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
8903 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
8904 - Stop using the default authorities in networks which provide both
8905 AlternateDirAuthority and AlternateBridgeAuthority. Partially
8906 fixes bug 13163; bugfix on 0.2.0.13-alpha.
8908 o Minor bugfixes (testing):
8909 - Stop spawn test failures due to a race condition between the
8910 SIGCHLD handler updating the process status, and the test reading
8911 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
8913 o Minor bugfixes (testing, Windows):
8914 - Avoid passing an extra backslash when creating a temporary
8915 directory for running the unit tests on Windows. Fixes bug 12392;
8916 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
8918 o Minor bugfixes (windows):
8919 - Remove code to special-case handling of NTE_BAD_KEYSET when
8920 acquiring windows CryptoAPI context. This error can't actually
8921 occur for the parameters we're providing. Fixes bug 10816; bugfix
8924 o Minor bugfixes (zlib):
8925 - Avoid truncating a zlib stream when trying to finalize it with an
8926 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
8929 - Allow our configure script to build correctly with autoconf 2.62
8930 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
8931 - Improve the error message from ./configure to make it clear that
8932 when asciidoc has not been found, the user will have to either add
8933 --disable-asciidoc argument or install asciidoc. Resolves
8936 o Code simplification and refactoring:
8937 - Change the entry_is_live() function to take named bitfield
8938 elements instead of an unnamed list of booleans. Closes
8940 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
8941 Resolves ticket 12205.
8942 - Use calloc and reallocarray functions instead of multiply-
8943 then-malloc. This makes it less likely for us to fall victim to an
8944 integer overflow attack when allocating. Resolves ticket 12855.
8945 - Use the standard macro name SIZE_MAX, instead of our
8947 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
8948 functions which take them as arguments. Replace 0 with NO_DIRINFO
8949 in a function call for clarity. Seeks to prevent future issues
8951 - Avoid 4 null pointer errors under clang static analysis by using
8952 tor_assert() to prove that the pointers aren't null. Fixes
8954 - Rework the API of policies_parse_exit_policy() to use a bitmask to
8955 represent parsing options, instead of a confusing mess of
8956 booleans. Resolves ticket 8197.
8957 - Introduce a helper function to parse ExitPolicy in
8958 or_options_t structure.
8961 - Add a doc/TUNING document with tips for handling large numbers of
8962 TCP connections when running busy Tor relay. Update the warning
8963 message to point to this file when running out of sockets
8964 operating system is allowing to use simultaneously. Resolves
8968 - We no longer remind the user about configuration options that have
8969 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
8970 - Remove our old, non-weighted bandwidth-based node selection code.
8971 Previously, we used it as a fallback when we couldn't perform
8972 weighted bandwidth-based node selection. But that would only
8973 happen in the cases where we had no consensus, or when we had a
8974 consensus generated by buggy or ancient directory authorities. In
8975 either case, it's better to use the more modern, better maintained
8976 algorithm, with reasonable defaults for the weights. Closes
8978 - Remove the --disable-curve25519 configure option. Relays and
8979 clients now are required to support curve25519 and the
8981 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
8982 used to be deprecated synonyms for "StrictNodes", are now marked
8983 obsolete. Resolves ticket 12226.
8984 - Clients don't understand the BadDirectory flag in the consensus
8985 anymore, and ignore it.
8988 - Refactor the function that chooses guard nodes so that it can more
8989 easily be tested; write some tests for it.
8990 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
8991 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
8992 - Create unit tests for format_time_interval(). With bug 13393.
8993 - Add unit tests for tor_timegm signed overflow, tor_timegm and
8994 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
8995 tests (visible) fixes in bug 13476.
8996 - Add a "coverage-html" make target to generate HTML-visualized
8997 coverage results when building with --enable-coverage. (Requires
8998 lcov.) Patch from Kevin Murray.
8999 - Enable the backtrace handler (where supported) when running the
9001 - Revise all unit tests that used the legacy test_* macros to
9002 instead use the recommended tt_* macros. This patch was generated
9003 with coccinelle, to avoid manual errors. Closes ticket 13119.
9005 o Distribution (systemd):
9006 - systemd unit file: only allow tor to write to /var/lib/tor and
9007 /var/log/tor. The rest of the filesystem is accessible for reading
9008 only. Patch by intrigeri; resolves ticket 12751.
9009 - systemd unit file: ensure that the process and all its children
9010 can never gain new privileges. Patch by intrigeri; resolves
9012 - systemd unit file: set up /var/run/tor as writable for the Tor
9013 service. Patch by intrigeri; resolves ticket 13196.
9015 o Removed features (directory authorities):
9016 - Remove code that prevented authorities from listing Tor relays
9017 affected by CVE-2011-2769 as guards. These relays are already
9018 rejected altogether due to the minimum version requirement of
9019 0.2.3.16-alpha. Closes ticket 13152.
9020 - The "AuthDirRejectUnlisted" option no longer has any effect, as
9021 the fingerprints file (approved-routers) has been deprecated.
9022 - Directory authorities do not support being Naming dirauths anymore.
9023 The "NamingAuthoritativeDir" config option is now obsolete.
9024 - Directory authorities do not support giving out the BadDirectory
9026 - Directory authorities no longer advertise or support consensus
9027 methods 1 through 12 inclusive. These consensus methods were
9028 obsolete and/or insecure: maintaining the ability to support them
9029 served no good purpose. Implements part of proposal 215; closes
9032 o Testing (test-network.sh):
9033 - Stop using "echo -n", as some shells' built-in echo doesn't
9034 support "-n". Instead, use "/bin/echo -n". Partially fixes
9036 - Stop an apparent test-network hang when used with make -j2. Fixes
9038 - Add a --delay option to test-network.sh, which configures the
9039 delay before the chutney network tests for data transmission.
9040 Partially implements ticket 13161.
9043 Changes in version 0.2.5.10 - 2014-10-24
9044 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
9046 It adds several new security features, including improved
9047 denial-of-service resistance for relays, new compiler hardening
9048 options, and a system-call sandbox for hardened installations on Linux
9049 (requires seccomp2). The controller protocol has several new features,
9050 resolving IPv6 addresses should work better than before, and relays
9051 should be a little more CPU-efficient. We've added support for more
9052 OpenBSD and FreeBSD transparent proxy types. We've improved the build
9053 system and testing infrastructure to allow unit testing of more parts
9054 of the Tor codebase. Finally, we've addressed several nagging pluggable
9055 transport usability issues, and included numerous other small bugfixes
9056 and features mentioned below.
9058 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
9059 have accumulated many known flaws; everyone should upgrade.
9061 o Deprecated versions:
9062 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
9063 attention for some while.
9066 Changes in version 0.2.5.9-rc - 2014-10-20
9067 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
9068 series. It disables SSL3 in response to the recent "POODLE" attack
9069 (even though POODLE does not affect Tor). It also works around a crash
9070 bug caused by some operating systems' response to the "POODLE" attack
9071 (which does affect Tor). It also contains a few miscellaneous fixes.
9073 o Major security fixes:
9074 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9075 today support TLS 1.0 or later, so we can safely turn off support
9076 for this old (and insecure) protocol. Fixes bug 13426.
9078 o Major bugfixes (openssl bug workaround):
9079 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9080 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9081 13471. This is a workaround for an OpenSSL bug.
9084 - Disable the sandbox name resolver cache when running tor-resolve:
9085 tor-resolve doesn't use the sandbox code, and turning it on was
9086 breaking attempts to do tor-resolve on a non-default server on
9087 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
9089 o Compilation fixes:
9090 - Build and run correctly on systems like OpenBSD-current that have
9091 patched OpenSSL to remove get_cipher_by_char and/or its
9092 implementations. Fixes issue 13325.
9094 o Downgraded warnings:
9095 - Downgrade the severity of the 'unexpected sendme cell from client'
9096 from 'warn' to 'protocol warning'. Closes ticket 8093.
9099 Changes in version 0.2.4.25 - 2014-10-20
9100 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
9101 (even though POODLE does not affect Tor). It also works around a crash
9102 bug caused by some operating systems' response to the "POODLE" attack
9103 (which does affect Tor).
9105 o Major security fixes (also in 0.2.5.9-rc):
9106 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9107 today support TLS 1.0 or later, so we can safely turn off support
9108 for this old (and insecure) protocol. Fixes bug 13426.
9110 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
9111 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9112 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9113 13471. This is a workaround for an OpenSSL bug.
9116 Changes in version 0.2.5.8-rc - 2014-09-22
9117 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
9118 series. It fixes a bug that affects consistency and speed when
9119 connecting to hidden services, and it updates the location of one of
9120 the directory authorities.
9123 - Clients now send the correct address for their chosen rendezvous
9124 point when trying to access a hidden service. They used to send
9125 the wrong address, which would still work some of the time because
9126 they also sent the identity digest of the rendezvous point, and if
9127 the hidden service happened to try connecting to the rendezvous
9128 point from a relay that already had a connection open to it,
9129 the relay would reuse that connection. Now connections to hidden
9130 services should be more robust and faster. Also, this bug meant
9131 that clients were leaking to the hidden service whether they were
9132 on a little-endian (common) or big-endian (rare) system, which for
9133 some users might have reduced their anonymity. Fixes bug 13151;
9134 bugfix on 0.2.1.5-alpha.
9136 o Directory authority changes:
9137 - Change IP address for gabelmoo (v3 directory authority).
9140 Changes in version 0.2.4.24 - 2014-09-22
9141 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
9142 connecting to hidden services, and it updates the location of one of
9143 the directory authorities.
9146 - Clients now send the correct address for their chosen rendezvous
9147 point when trying to access a hidden service. They used to send
9148 the wrong address, which would still work some of the time because
9149 they also sent the identity digest of the rendezvous point, and if
9150 the hidden service happened to try connecting to the rendezvous
9151 point from a relay that already had a connection open to it,
9152 the relay would reuse that connection. Now connections to hidden
9153 services should be more robust and faster. Also, this bug meant
9154 that clients were leaking to the hidden service whether they were
9155 on a little-endian (common) or big-endian (rare) system, which for
9156 some users might have reduced their anonymity. Fixes bug 13151;
9157 bugfix on 0.2.1.5-alpha.
9159 o Directory authority changes:
9160 - Change IP address for gabelmoo (v3 directory authority).
9162 o Minor features (geoip):
9163 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9167 Changes in version 0.2.5.7-rc - 2014-09-11
9168 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
9169 release series, and some long-standing bugs related to ORPort reachability
9170 testing and failure to send CREATE cells. It is the first release
9171 candidate for the Tor 0.2.5.x series.
9173 o Major bugfixes (client, startup):
9174 - Start making circuits as soon as DisabledNetwork is turned off.
9175 When Tor started with DisabledNetwork set, it would correctly
9176 conclude that it shouldn't build circuits, but it would mistakenly
9177 cache this conclusion, and continue believing it even when
9178 DisableNetwork is set to 0. Fixes the bug introduced by the fix
9179 for bug 11200; bugfix on 0.2.5.4-alpha.
9180 - Resume expanding abbreviations for command-line options. The fix
9181 for bug 4647 accidentally removed our hack from bug 586 that
9182 rewrote HashedControlPassword to __HashedControlSessionPassword
9183 when it appears on the commandline (which allowed the user to set
9184 her own HashedControlPassword in the torrc file while the
9185 controller generates a fresh session password for each run). Fixes
9186 bug 12948; bugfix on 0.2.5.1-alpha.
9187 - Warn about attempts to run hidden services and relays in the same
9188 process: that's probably not a good idea. Closes ticket 12908.
9190 o Major bugfixes (relay):
9191 - Avoid queuing or sending destroy cells for circuit ID zero when we
9192 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
9193 Found and fixed by "cypherpunks".
9194 - Fix ORPort reachability detection on relays running behind a
9195 proxy, by correctly updating the "local" mark on the controlling
9196 channel when changing the address of an or_connection_t after the
9197 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
9199 o Minor features (bridge):
9200 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
9201 cookie file for the ExtORPort g+r by default.
9203 o Minor features (geoip):
9204 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9207 o Minor bugfixes (logging):
9208 - Reduce the log severity of the "Pluggable transport proxy does not
9209 provide any needed transports and will not be launched." message,
9210 since Tor Browser includes several ClientTransportPlugin lines in
9211 its torrc-defaults file, leading every Tor Browser user who looks
9212 at her logs to see these notices and wonder if they're dangerous.
9213 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
9214 - Downgrade "Unexpected onionskin length after decryption" warning
9215 to a protocol-warn, since there's nothing relay operators can do
9216 about a client that sends them a malformed create cell. Resolves
9217 bug 12996; bugfix on 0.0.6rc1.
9218 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
9219 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
9220 - When logging information about an EXTEND2 or EXTENDED2 cell, log
9221 their names correctly. Fixes part of bug 12700; bugfix
9223 - When logging information about a relay cell whose command we don't
9224 recognize, log its command as an integer. Fixes part of bug 12700;
9225 bugfix on 0.2.1.10-alpha.
9226 - Escape all strings from the directory connection before logging
9227 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
9229 o Minor bugfixes (controller):
9230 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
9231 bug 12864; bugfix on 0.2.5.1-alpha.
9232 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
9233 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
9236 o Minor bugfixes (compilation):
9237 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
9238 bugfix on 0.2.5.5-alpha.
9239 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
9240 0.2.5.1-alpha. Patch from "NewEraCracker".
9241 - In routerlist_assert_ok(), don't take the address of a
9242 routerinfo's cache_info member unless that routerinfo is non-NULL.
9243 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
9244 - Fix a large number of false positive warnings from the clang
9245 analyzer static analysis tool. This should make real warnings
9246 easier for clang analyzer to find. Patch from "teor". Closes
9249 o Distribution (systemd):
9250 - Verify configuration file via ExecStartPre in the systemd unit
9251 file. Patch from intrigeri; resolves ticket 12730.
9252 - Explicitly disable RunAsDaemon in the systemd unit file. Our
9253 current systemd unit uses "Type = simple", so systemd does not
9254 expect tor to fork. If the user has "RunAsDaemon 1" in their
9255 torrc, then things won't work as expected. This is e.g. the case
9256 on Debian (and derivatives), since there we pass "--defaults-torrc
9257 /usr/share/tor/tor-service-defaults-torrc" (that contains
9258 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
9262 - Adjust the URLs in the README to refer to the new locations of
9263 several documents on the website. Fixes bug 12830. Patch from
9265 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
9269 Changes in version 0.2.5.6-alpha - 2014-07-28
9270 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
9271 risk from guard rotation, and fixes a variety of other issues to get
9272 us closer to a release candidate.
9274 o Major features (also in 0.2.4.23):
9275 - Make the number of entry guards configurable via a new
9276 NumEntryGuards consensus parameter, and the number of directory
9277 guards configurable via a new NumDirectoryGuards consensus
9278 parameter. Implements ticket 12688.
9280 o Major bugfixes (also in 0.2.4.23):
9281 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
9282 implementation that caused incorrect results on 32-bit
9283 implementations when certain malformed inputs were used along with
9284 a small class of private ntor keys. This bug does not currently
9285 appear to allow an attacker to learn private keys or impersonate a
9286 Tor server, but it could provide a means to distinguish 32-bit Tor
9287 implementations from 64-bit Tor implementations. Fixes bug 12694;
9288 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
9292 - Perform circuit cleanup operations even when circuit
9293 construction operations are disabled (because the network is
9294 disabled, or because there isn't enough directory information).
9295 Previously, when we were not building predictive circuits, we
9296 were not closing expired circuits either. Fixes bug 8387; bugfix on
9297 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
9298 became more strict about when we have "enough directory information
9302 - Authorities now assign the Guard flag to the fastest 25% of the
9303 network (it used to be the fastest 50%). Also raise the consensus
9304 weight that guarantees the Guard flag from 250 to 2000. For the
9305 current network, this results in about 1100 guards, down from 2500.
9306 This step paves the way for moving the number of entry guards
9307 down to 1 (proposal 236) while still providing reasonable expected
9308 performance for most users. Implements ticket 12690.
9309 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
9311 - Slightly enhance the diagnostic message for bug 12184.
9313 o Minor bugfixes (also in 0.2.4.23):
9314 - Warn and drop the circuit if we receive an inbound 'relay early'
9315 cell. Those used to be normal to receive on hidden service circuits
9316 due to bug 1038, but the buggy Tor versions are long gone from
9317 the network so we can afford to resume watching for them. Resolves
9318 the rest of bug 1038; bugfix on 0.2.1.19.
9319 - Correct a confusing error message when trying to extend a circuit
9320 via the control protocol but we don't know a descriptor or
9321 microdescriptor for one of the specified relays. Fixes bug 12718;
9322 bugfix on 0.2.3.1-alpha.
9325 - Fix compilation when building with bufferevents enabled. (This
9326 configuration is still not expected to work, however.)
9327 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
9328 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
9330 - Compile correctly with builds and forks of OpenSSL (such as
9331 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
9332 0.2.1.1-alpha. Patch from "dhill".
9335 Changes in version 0.2.4.23 - 2014-07-28
9336 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
9337 guard rotation, and also backports several important fixes from the
9338 Tor 0.2.5 alpha release series.
9341 - Clients now look at the "usecreatefast" consensus parameter to
9342 decide whether to use CREATE_FAST or CREATE cells for the first hop
9343 of their circuit. This approach can improve security on connections
9344 where Tor's circuit handshake is stronger than the available TLS
9345 connection security levels, but the tradeoff is more computational
9346 load on guard relays. Implements proposal 221. Resolves ticket 9386.
9347 - Make the number of entry guards configurable via a new
9348 NumEntryGuards consensus parameter, and the number of directory
9349 guards configurable via a new NumDirectoryGuards consensus
9350 parameter. Implements ticket 12688.
9353 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
9354 implementation that caused incorrect results on 32-bit
9355 implementations when certain malformed inputs were used along with
9356 a small class of private ntor keys. This bug does not currently
9357 appear to allow an attacker to learn private keys or impersonate a
9358 Tor server, but it could provide a means to distinguish 32-bit Tor
9359 implementations from 64-bit Tor implementations. Fixes bug 12694;
9360 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
9364 - Warn and drop the circuit if we receive an inbound 'relay early'
9365 cell. Those used to be normal to receive on hidden service circuits
9366 due to bug 1038, but the buggy Tor versions are long gone from
9367 the network so we can afford to resume watching for them. Resolves
9368 the rest of bug 1038; bugfix on 0.2.1.19.
9369 - Correct a confusing error message when trying to extend a circuit
9370 via the control protocol but we don't know a descriptor or
9371 microdescriptor for one of the specified relays. Fixes bug 12718;
9372 bugfix on 0.2.3.1-alpha.
9373 - Avoid an illegal read from stack when initializing the TLS
9374 module using a version of OpenSSL without all of the ciphers
9375 used by the v2 link handshake. Fixes bug 12227; bugfix on
9376 0.2.4.8-alpha. Found by "starlight".
9379 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
9383 Changes in version 0.2.5.5-alpha - 2014-06-18
9384 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
9385 0.2.5.x release series, including a couple of DoS issues, some
9386 performance regressions, a large number of bugs affecting the Linux
9387 seccomp2 sandbox code, and various other bugfixes. It also adds
9388 diagnostic bugfixes for a few tricky issues that we're trying to
9391 o Major features (security, traffic analysis resistance):
9392 - Several major improvements to the algorithm used to decide when to
9393 close TLS connections. Previous versions of Tor closed connections
9394 at a fixed interval after the last time a non-padding cell was
9395 sent over the connection, regardless of the target of the
9396 connection. Now, we randomize the intervals by adding up to 50% of
9397 their base value, we measure the length of time since connection
9398 last had at least one circuit, and we allow connections to known
9399 ORs to remain open a little longer (15 minutes instead of 3
9400 minutes minimum). These changes should improve Tor's resistance
9401 against some kinds of traffic analysis, and lower some overhead
9402 from needlessly closed connections. Fixes ticket 6799.
9403 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
9405 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
9406 - Fix a memory leak that could occur if a microdescriptor parse
9407 fails during the tokenizing step. This bug could enable a memory
9408 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9411 o Major bugfixes (security, directory authorities):
9412 - Directory authorities now include a digest of each relay's
9413 identity key as a part of its microdescriptor.
9415 This is a workaround for bug 11743 (reported by "cypherpunks"),
9416 where Tor clients do not support receiving multiple
9417 microdescriptors with the same SHA256 digest in the same
9418 consensus. When clients receive a consensus like this, they only
9419 use one of the relays. Without this fix, a hostile relay could
9420 selectively disable some client use of target relays by
9421 constructing a router descriptor with a different identity and the
9422 same microdescriptor parameters and getting the authorities to
9423 list it in a microdescriptor consensus. This fix prevents an
9424 attacker from causing a microdescriptor collision, because the
9425 router's identity is not forgeable.
9427 o Major bugfixes (relay):
9428 - Use a direct dirport connection when uploading non-anonymous
9429 descriptors to the directory authorities. Previously, relays would
9430 incorrectly use tunnel connections under a fairly wide variety of
9431 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
9432 - When a circuit accidentally has the same circuit ID for its
9433 forward and reverse direction, correctly detect the direction of
9434 cells using that circuit. Previously, this bug made roughly one
9435 circuit in a million non-functional. Fixes bug 12195; this is a
9436 bugfix on every version of Tor.
9438 o Major bugfixes (client, pluggable transports):
9439 - When managing pluggable transports, use OS notification facilities
9440 to learn if they have crashed, and don't attempt to kill any
9441 process that has already exited. Fixes bug 8746; bugfix
9444 o Minor features (diagnostic):
9445 - When logging a warning because of bug 7164, additionally check the
9446 hash table for consistency (as proposed on ticket 11737). This may
9447 help diagnose bug 7164.
9448 - When we log a heartbeat, log how many one-hop circuits we have
9449 that are at least 30 minutes old, and log status information about
9450 a few of them. This is an attempt to track down bug 8387.
9451 - When encountering an unexpected CR while writing text to a file on
9452 Windows, log the name of the file. Should help diagnosing
9454 - Give more specific warnings when a client notices that an onion
9455 handshake has failed. Fixes ticket 9635.
9456 - Add significant new logging code to attempt to diagnose bug 12184,
9457 where relays seem to run out of available circuit IDs.
9458 - Improve the diagnostic log message for bug 8387 even further to
9459 try to improve our odds of figuring out why one-hop directory
9460 circuits sometimes do not get closed.
9462 o Minor features (security, memory management):
9463 - Memory allocation tricks (mempools and buffer freelists) are now
9464 disabled by default. You can turn them back on with
9465 --enable-mempools and --enable-buf-freelists respectively. We're
9466 disabling these features because malloc performance is good enough
9467 on most platforms, and a similar feature in OpenSSL exacerbated
9468 exploitation of the Heartbleed attack. Resolves ticket 11476.
9470 o Minor features (security):
9471 - Apply the secure SipHash-2-4 function to the hash table mapping
9472 circuit IDs and channels to circuits. We missed this one when we
9473 were converting all the other hash functions to use SipHash back
9474 in 0.2.5.3-alpha. Resolves ticket 11750.
9476 o Minor features (build):
9477 - The configure script has a --disable-seccomp option to turn off
9478 support for libseccomp on systems that have it, in case it (or
9479 Tor's use of it) is broken. Resolves ticket 11628.
9481 o Minor features (other):
9482 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
9485 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
9486 - When running a hidden service, do not allow TunneledDirConns 0;
9487 this will keep the hidden service from running, and also
9488 make it publish its descriptors directly over HTTP. Fixes bug 10849;
9489 bugfix on 0.2.1.1-alpha.
9491 o Minor bugfixes (performance):
9492 - Avoid a bug where every successful connection made us recompute
9493 the flag telling us whether we have sufficient information to
9494 build circuits. Previously, we would forget our cached value
9495 whenever we successfully opened a channel (or marked a router as
9496 running or not running for any other reason), regardless of
9497 whether we had previously believed the router to be running. This
9498 forced us to run an expensive update operation far too often.
9499 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
9500 - Avoid using tor_memeq() for checking relay cell integrity. This
9501 removes a possible performance bottleneck. Fixes part of bug
9502 12169; bugfix on 0.2.1.31.
9504 o Minor bugfixes (compilation):
9505 - Fix compilation of test_status.c when building with MVSC. Bugfix
9506 on 0.2.5.4-alpha. Patch from Gisle Vanem.
9507 - Resolve GCC complaints on OpenBSD about discarding constness in
9508 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
9509 on 0.1.1.23. Patch from Dana Koch.
9510 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
9511 treatment of long and time_t as comparable types. Fixes part of
9512 bug 11633. Patch from Dana Koch.
9513 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
9514 11623; bugfix on 0.2.5.3-alpha.
9515 - When deciding whether to build the 64-bit curve25519
9516 implementation, detect platforms where we can compile 128-bit
9517 arithmetic but cannot link it. Fixes bug 11729; bugfix on
9518 0.2.4.8-alpha. Patch from "conradev".
9519 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
9520 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
9521 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
9524 o Minor bugfixes (Directory server):
9525 - When sending a compressed set of descriptors or microdescriptors,
9526 make sure to finalize the zlib stream. Previously, we would write
9527 all the compressed data, but if the last descriptor we wanted to
9528 send was missing or too old, we would not mark the stream as
9529 finished. This caused problems for decompression tools. Fixes bug
9530 11648; bugfix on 0.1.1.23.
9532 o Minor bugfixes (Linux seccomp sandbox):
9533 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
9534 11622; bugfix on 0.2.5.1-alpha.
9535 - Avoid crashing when re-opening listener ports with the seccomp
9536 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
9537 - Avoid crashing with the seccomp sandbox enabled along with
9538 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
9539 - When we receive a SIGHUP with the sandbox enabled, correctly
9540 support rotating our log files. Fixes bug 12032; bugfix
9542 - Avoid crash when running with sandboxing enabled and
9543 DirReqStatistics not disabled. Fixes bug 12035; bugfix
9545 - Fix a "BUG" warning when trying to write bridge-stats files with
9546 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
9548 - Prevent the sandbox from crashing on startup when run with the
9549 --enable-expensive-hardening configuration option. Fixes bug
9550 11477; bugfix on 0.2.5.4-alpha.
9551 - When running with DirPortFrontPage and sandboxing both enabled,
9552 reload the DirPortFrontPage correctly when restarting. Fixes bug
9553 12028; bugfix on 0.2.5.1-alpha.
9554 - Don't try to enable the sandbox when using the Tor binary to check
9555 its configuration, hash a passphrase, or so on. Doing so was
9556 crashing on startup for some users. Fixes bug 11609; bugfix
9558 - Avoid warnings when running with sandboxing and node statistics
9559 enabled at the same time. Fixes part of 12064; bugfix on
9560 0.2.5.1-alpha. Patch from Michael Wolf.
9561 - Avoid warnings when running with sandboxing enabled at the same
9562 time as cookie authentication, hidden services, or directory
9563 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
9564 - Do not allow options that require calls to exec to be enabled
9565 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
9566 bug 12043; bugfix on 0.2.5.1-alpha.
9567 - Handle failures in getpwnam()/getpwuid() when running with the
9568 User option set and the Linux syscall sandbox enabled. Fixes bug
9569 11946; bugfix on 0.2.5.1-alpha.
9570 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
9571 to avoid calling getaddrinfo() after installing the sandbox
9572 filters. Previously, it preloaded a cache with the IPv4 address
9573 for our hostname, and nothing else. Now, it loads the cache with
9574 every address that it used to initialize the Tor process. Fixes
9575 bug 11970; bugfix on 0.2.5.1-alpha.
9577 o Minor bugfixes (pluggable transports):
9578 - Enable the ExtORPortCookieAuthFile option, to allow changing the
9579 default location of the authentication token for the extended OR
9580 Port as used by sever-side pluggable transports. We had
9581 implemented this option before, but the code to make it settable
9582 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
9583 - Avoid another 60-second delay when starting Tor in a pluggable-
9584 transport-using configuration when we already have cached
9585 descriptors for our bridges. Fixes bug 11965; bugfix
9588 o Minor bugfixes (client):
9589 - Avoid "Tried to open a socket with DisableNetwork set" warnings
9590 when starting a client with bridges configured and DisableNetwork
9591 set. (Tor launcher starts Tor with DisableNetwork set the first
9592 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
9594 o Minor bugfixes (testing):
9595 - The Python parts of the test scripts now work on Python 3 as well
9596 as Python 2, so systems where '/usr/bin/python' is Python 3 will
9597 no longer have the tests break. Fixes bug 11608; bugfix
9599 - When looking for versions of python that we could run the tests
9600 with, check for "python2.7" and "python3.3"; previously we were
9601 only looking for "python", "python2", and "python3". Patch from
9602 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
9603 - Fix all valgrind warnings produced by the unit tests. There were
9604 over a thousand memory leak warnings previously, mostly produced
9605 by forgetting to free things in the unit test code. Fixes bug
9606 11618, bugfixes on many versions of Tor.
9608 o Minor bugfixes (tor-fw-helper):
9609 - Give a correct log message when tor-fw-helper fails to launch.
9610 (Previously, we would say something like "tor-fw-helper sent us a
9611 string we could not parse".) Fixes bug 9781; bugfix
9614 o Minor bugfixes (relay, threading):
9615 - Check return code on spawn_func() in cpuworker code, so that we
9616 don't think we've spawned a nonworking cpuworker and write junk to
9617 it forever. Fix related to bug 4345; bugfix on all released Tor
9618 versions. Found by "skruffy".
9619 - Use a pthread_attr to make sure that spawn_func() cannot return an
9620 error while at the same time launching a thread. Fix related to
9621 bug 4345; bugfix on all released Tor versions. Reported
9624 o Minor bugfixes (relay, oom prevention):
9625 - Correctly detect the total available system memory. We tried to do
9626 this in 0.2.5.4-alpha, but the code was set up to always return an
9627 error value, even on success. Fixes bug 11805; bugfix
9630 o Minor bugfixes (relay, other):
9631 - We now drop CREATE cells for already-existent circuit IDs and for
9632 zero-valued circuit IDs, regardless of other factors that might
9633 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
9635 - Avoid an illegal read from stack when initializing the TLS module
9636 using a version of OpenSSL without all of the ciphers used by the
9637 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
9639 - When rejecting DATA cells for stream_id zero, still count them
9640 against the circuit's deliver window so that we don't fail to send
9641 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
9643 o Minor bugfixes (logging):
9644 - Fix a misformatted log message about delayed directory fetches.
9645 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
9646 - Squelch a spurious LD_BUG message "No origin circuit for
9647 successful SOCKS stream" in certain hidden service failure cases;
9651 - Include a tor.service file in contrib/dist for use with systemd.
9652 Some distributions will be able to use this file unmodified;
9653 others will need to tweak it, or write their own. Patch from Jamie
9654 Nguyen; resolves ticket 8368.
9657 - Clean up several option names in the manpage to match their real
9658 names, add the missing documentation for a couple of testing and
9659 directory authority options, remove the documentation for a
9660 V2-directory fetching option that no longer exists. Resolves
9662 - Correct the documenation so that it lists the correct directory
9663 for the stats files. (They are in a subdirectory called "stats",
9665 - In the manpage, move more authority-only options into the
9666 directory authority section so that operators of regular directory
9667 caches don't get confused.
9670 - The contrib directory has been sorted and tidied. Before, it was
9671 an unsorted dumping ground for useful and not-so-useful things.
9672 Now, it is divided based on functionality, and the items which
9673 seemed to be nonfunctional or useless have been removed. Resolves
9674 ticket 8966; based on patches from "rl1987".
9677 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
9678 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
9679 - The TunnelDirConns and PreferTunnelledDirConns options no longer
9680 exist; tunneled directory connections have been available since
9681 0.1.2.5-alpha, and turning them off is not a good idea. This is a
9682 brute-force fix for 10849, where "TunnelDirConns 0" would break
9686 Changes in version 0.2.4.22 - 2014-05-16
9687 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
9688 alpha release series. These include blocking all authority signing
9689 keys that may have been affected by the OpenSSL "heartbleed" bug,
9690 choosing a far more secure set of TLS ciphersuites by default, closing
9691 a couple of memory leaks that could be used to run a target relay out
9692 of RAM, and several others.
9694 o Major features (security, backport from 0.2.5.4-alpha):
9695 - Block authority signing keys that were used on authorities
9696 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9697 don't have any evidence that these keys _were_ compromised; we're
9698 doing this to be prudent.) Resolves ticket 11464.
9700 o Major bugfixes (security, OOM):
9701 - Fix a memory leak that could occur if a microdescriptor parse
9702 fails during the tokenizing step. This bug could enable a memory
9703 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9706 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
9707 - The relay ciphersuite list is now generated automatically based on
9708 uniform criteria, and includes all OpenSSL ciphersuites with
9709 acceptable strength and forward secrecy. Previously, we had left
9710 some perfectly fine ciphersuites unsupported due to omission or
9711 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9712 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9713 - Relays now trust themselves to have a better view than clients of
9714 which TLS ciphersuites are better than others. (Thanks to bug
9715 11513, the relay list is now well-considered, whereas the client
9716 list has been chosen mainly for anti-fingerprinting purposes.)
9717 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9718 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9719 AES128. Resolves ticket 11528.
9720 - Clients now try to advertise the same list of ciphersuites as
9721 Firefox 28. This change enables selection of (fast) GCM
9722 ciphersuites, disables some strange old ciphers, and stops
9723 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9724 Resolves ticket 11438.
9726 o Minor bugfixes (configuration, security):
9727 - When running a hidden service, do not allow TunneledDirConns 0:
9728 trying to set that option together with a hidden service would
9729 otherwise prevent the hidden service from running, and also make
9730 it publish its descriptors directly over HTTP. Fixes bug 10849;
9731 bugfix on 0.2.1.1-alpha.
9733 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
9734 - Avoid sending a garbage value to the controller when a circuit is
9735 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9737 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
9738 - Stop leaking memory when we successfully resolve a PTR record.
9739 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9741 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
9742 - Avoid 60-second delays in the bootstrapping process when Tor is
9743 launching for a second time while using bridges. Fixes bug 9229;
9744 bugfix on 0.2.0.3-alpha.
9746 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
9747 - Give the correct URL in the warning message when trying to run a
9748 relay on an ancient version of Windows. Fixes bug 9393.
9750 o Minor bugfixes (compilation):
9751 - Fix a compilation error when compiling with --disable-curve25519.
9752 Fixes bug 9700; bugfix on 0.2.4.17-rc.
9755 - Downgrade the warning severity for the the "md was still
9756 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
9757 for trying to diagnose this bug, and the current warning in
9758 earlier versions of tor achieves nothing useful. Addresses warning
9761 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
9762 - When we run out of usable circuit IDs on a channel, log only one
9763 warning for the whole channel, and describe how many circuits
9764 there were on the channel. Fixes part of ticket 11553.
9766 o Minor features (security, backport from 0.2.5.4-alpha):
9767 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
9768 leave the default at 8GBytes), to better support Raspberry Pi
9769 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
9771 o Documentation (backport from 0.2.5.4-alpha):
9772 - Correctly document that we search for a system torrc file before
9773 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
9777 Changes in version 0.2.5.4-alpha - 2014-04-25
9778 Tor 0.2.5.4-alpha includes several security and performance
9779 improvements for clients and relays, including blacklisting authority
9780 signing keys that were used while susceptible to the OpenSSL
9781 "heartbleed" bug, fixing two expensive functions on busy relays,
9782 improved TLS ciphersuite preference lists, support for run-time
9783 hardening on compilers that support AddressSanitizer, and more work on
9784 the Linux sandbox code.
9786 There are also several usability fixes for clients (especially clients
9787 that use bridges), two new TransPort protocols supported (one on
9788 OpenBSD, one on FreeBSD), and various other bugfixes.
9790 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
9791 have accumulated many known flaws; everyone should upgrade.
9793 o Major features (security):
9794 - If you don't specify MaxMemInQueues yourself, Tor now tries to
9795 pick a good value based on your total system memory. Previously,
9796 the default was always 8 GB. You can still override the default by
9797 setting MaxMemInQueues yourself. Resolves ticket 11396.
9798 - Block authority signing keys that were used on authorities
9799 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9800 don't have any evidence that these keys _were_ compromised; we're
9801 doing this to be prudent.) Resolves ticket 11464.
9803 o Major features (relay performance):
9804 - Speed up server-side lookups of rendezvous and introduction point
9805 circuits by using hashtables instead of linear searches. These
9806 functions previously accounted between 3 and 7% of CPU usage on
9807 some busy relays. Resolves ticket 9841.
9808 - Avoid wasting CPU when extending a circuit over a channel that is
9809 nearly out of circuit IDs. Previously, we would do a linear scan
9810 over possible circuit IDs before finding one or deciding that we
9811 had exhausted our possibilities. Now, we try at most 64 random
9812 circuit IDs before deciding that we probably won't succeed. Fixes
9813 a possible root cause of ticket 11553.
9815 o Major features (seccomp2 sandbox, Linux only):
9816 - The seccomp2 sandbox can now run a test network for multiple hours
9817 without crashing. The sandbox is still experimental, and more bugs
9818 will probably turn up. To try it, enable "Sandbox 1" on a Linux
9819 host. Resolves ticket 11351.
9820 - Strengthen sandbox code: the sandbox can now test the arguments
9821 for rename(), and blocks _sysctl() entirely. Resolves another part
9823 - When the sandbox blocks a system call, it now tries to log a stack
9824 trace before exiting. Resolves ticket 11465.
9826 o Major bugfixes (TLS cipher selection):
9827 - The relay ciphersuite list is now generated automatically based on
9828 uniform criteria, and includes all OpenSSL ciphersuites with
9829 acceptable strength and forward secrecy. Previously, we had left
9830 some perfectly fine ciphersuites unsupported due to omission or
9831 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9832 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9833 - Relays now trust themselves to have a better view than clients of
9834 which TLS ciphersuites are better than others. (Thanks to bug
9835 11513, the relay list is now well-considered, whereas the client
9836 list has been chosen mainly for anti-fingerprinting purposes.)
9837 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9838 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9839 AES128. Resolves ticket 11528.
9840 - Clients now try to advertise the same list of ciphersuites as
9841 Firefox 28. This change enables selection of (fast) GCM
9842 ciphersuites, disables some strange old ciphers, and stops
9843 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9844 Resolves ticket 11438.
9846 o Major bugfixes (bridge client):
9847 - Avoid 60-second delays in the bootstrapping process when Tor is
9848 launching for a second time while using bridges. Fixes bug 9229;
9849 bugfix on 0.2.0.3-alpha.
9851 o Minor features (transparent proxy, *BSD):
9852 - Support FreeBSD's ipfw firewall interface for TransPort ports on
9853 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
9854 10267; patch from "yurivict".
9855 - Support OpenBSD's divert-to rules with the pf firewall for
9856 transparent proxy ports. To enable it, set "TransProxyType
9857 pf-divert". This allows Tor to run a TransPort transparent proxy
9858 port on OpenBSD 4.4 or later without root privileges. See the
9859 pf.conf(5) manual page for information on configuring pf to use
9860 divert-to rules. Closes ticket 10896; patch from Dana Koch.
9862 o Minor features (security):
9863 - New --enable-expensive-hardening option to enable security
9864 hardening options that consume nontrivial amounts of CPU and
9865 memory. Right now, this includes AddressSanitizer and UbSan, which
9866 are supported in newer versions of GCC and Clang. Closes ticket
9869 o Minor features (log verbosity):
9870 - Demote the message that we give when a flushing connection times
9871 out for too long from NOTICE to INFO. It was usually meaningless.
9872 Resolves ticket 5286.
9873 - Don't log so many notice-level bootstrapping messages at startup
9874 about downloading descriptors. Previously, we'd log a notice
9875 whenever we learned about more routers. Now, we only log a notice
9876 at every 5% of progress. Fixes bug 9963.
9877 - Warn less verbosely when receiving a malformed
9878 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
9879 - When we run out of usable circuit IDs on a channel, log only one
9880 warning for the whole channel, and describe how many circuits
9881 there were on the channel. Fixes part of ticket 11553.
9883 o Minor features (relay):
9884 - If a circuit timed out for at least 3 minutes, check if we have a
9885 new external IP address, and publish a new descriptor with the new
9886 IP address if it changed. Resolves ticket 2454.
9888 o Minor features (controller):
9889 - Make the entire exit policy available from the control port via
9890 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
9892 - Because of the fix for ticket 11396, the real limit for memory
9893 usage may no longer match the configured MaxMemInQueues value. The
9894 real limit is now exposed via GETINFO limits/max-mem-in-queues.
9896 o Minor features (bridge client):
9897 - Report a more useful failure message when we can't connect to a
9898 bridge because we don't have the right pluggable transport
9899 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
9901 o Minor features (diagnostic):
9902 - Add more log messages to diagnose bug 7164, which causes
9903 intermittent "microdesc_free() called but md was still referenced"
9904 warnings. We now include more information, to figure out why we
9905 might be cleaning a microdescriptor for being too old if it's
9906 still referenced by a live node_t object.
9908 o Minor bugfixes (client, DNSPort):
9909 - When using DNSPort, try to respond to AAAA requests with AAAA
9910 answers. Previously, we hadn't looked at the request type when
9911 deciding which answer type to prefer. Fixes bug 10468; bugfix on
9913 - When receiving a DNS query for an unsupported record type, reply
9914 with no answer rather than with a NOTIMPL error. This behavior
9915 isn't correct either, but it will break fewer client programs, we
9916 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
9919 o Minor bugfixes (exit relay):
9920 - Stop leaking memory when we successfully resolve a PTR record.
9921 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9923 o Minor bugfixes (bridge client):
9924 - Stop accepting bridge lines containing hostnames. Doing so would
9925 cause clients to perform DNS requests on the hostnames, which was
9926 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
9927 - Avoid a 60-second delay in the bootstrapping process when a Tor
9928 client with pluggable transports re-reads its configuration at
9929 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
9931 o Minor bugfixes (client, logging during bootstrap):
9932 - Warn only once if we start logging in an unsafe way. Previously,
9933 we complain as many times as we had problems. Fixes bug 9870;
9934 bugfix on 0.2.5.1-alpha.
9935 - Only report the first fatal bootstrap error on a given OR
9936 connection. This stops us from telling the controller bogus error
9937 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
9938 - Be more helpful when trying to run sandboxed on Linux without
9939 libseccomp. Instead of saying "Sandbox is not implemented on this
9940 platform", we now explain that we need to be built with
9941 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
9942 - Avoid generating spurious warnings when starting with
9943 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
9946 o Minor bugfixes (closing OR connections):
9947 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
9948 check if it's an or_connection_t and correctly call
9949 connection_or_close_for_error() rather than
9950 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
9952 - When closing all connections on setting DisableNetwork to 1, use
9953 connection_or_close_normally() rather than closing OR connections
9954 out from under the channel layer. Fixes bug 11306; bugfix on
9957 o Minor bugfixes (controller):
9958 - Avoid sending a garbage value to the controller when a circuit is
9959 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9961 o Minor bugfixes (tor-fw-helper):
9962 - Allow tor-fw-helper to build again by adding src/ext to its
9963 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
9965 o Minor bugfixes (bridges):
9966 - Avoid potential crashes or bad behavior when launching a
9967 server-side managed proxy with ORPort or ExtORPort temporarily
9968 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
9970 o Minor bugfixes (platform-specific):
9971 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
9972 bug 11426; bugfix on 0.2.5.3-alpha.
9973 - When dumping a malformed directory object to disk, save it in
9974 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
9976 - Don't report failures from make_socket_reuseable() on incoming
9977 sockets on OSX: this can happen when incoming connections close
9978 early. Fixes bug 10081.
9980 o Minor bugfixes (trivial memory leaks):
9981 - Fix a small memory leak when signing a directory object. Fixes bug
9982 11275; bugfix on 0.2.4.13-alpha.
9983 - Free placeholder entries in our circuit table at exit; fixes a
9984 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
9985 - Don't re-initialize a second set of OpenSSL mutexes when starting
9986 up. Previously, we'd make one set of mutexes, and then immediately
9987 replace them with another. Fixes bug 11726; bugfix on
9989 - Resolve some memory leaks found by coverity in the unit tests, on
9990 exit in tor-gencert, and on a failure to compute digests for our
9991 own keys when generating a v3 networkstatus vote. These leaks
9992 should never have affected anyone in practice.
9994 o Minor bugfixes (hidden service):
9995 - Only retry attempts to connect to a chosen rendezvous point 8
9996 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
9998 o Minor bugfixes (misc code correctness):
9999 - Fix various instances of undefined behavior in channeltls.c,
10000 tor_memmem(), and eventdns.c that would cause us to construct
10001 pointers to memory outside an allocated object. (These invalid
10002 pointers were not accessed, but C does not even allow them to
10003 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
10004 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
10005 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
10006 fix some miscellaneous errors in our tests and codebase. Fixes bug
10007 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
10008 - Always check return values for unlink, munmap, UnmapViewOfFile;
10009 check strftime return values more often. In some cases all we can
10010 do is report a warning, but this may help prevent deeper bugs from
10011 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
10013 - Fix numerous warnings from the clang "scan-build" static analyzer.
10014 Some of these are programming style issues; some of them are false
10015 positives that indicated awkward code; some are undefined behavior
10016 cases related to constructing (but not using) invalid pointers;
10017 some are assumptions about API behavior; some are (harmlessly)
10018 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
10019 correct; and one or two are genuine bugs that weren't reachable
10020 from the rest of the program. Fixes bug 8793; bugfixes on many,
10024 - Build the torify.1 manpage again. Previously, we were only trying
10025 to build it when also building tor-fw-helper. That's why we didn't
10026 notice that we'd broken the ability to build it. Fixes bug 11321;
10027 bugfix on 0.2.5.1-alpha.
10028 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
10029 11061; bugfix on 0.2.4.7-alpha.
10030 - Correctly document that we search for a system torrc file before
10031 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
10033 - Resolve warnings from Doxygen.
10035 o Code simplifications and refactoring:
10036 - Remove is_internal_IP() function. Resolves ticket 4645.
10037 - Remove unused function circuit_dump_by_chan from circuitlist.c.
10038 Closes issue 9107; patch from "marek".
10039 - Change our use of the ENUM_BF macro to avoid declarations that
10042 o Deprecated versions:
10043 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
10044 attention for some while. Directory authorities no longer accept
10045 descriptors from relays running any version of Tor prior to Tor
10046 0.2.3.16-alpha. Resolves ticket 11149.
10049 - New macros in test.h to simplify writing mock-functions for unit
10050 tests. Part of ticket 11507. Patch from Dana Koch.
10051 - Complete tests for the status.c module. Resolves ticket 11507.
10052 Patch from Dana Koch.
10055 - Remove all code for the long unused v1 directory protocol.
10056 Resolves ticket 11070.
10059 Changes in version 0.2.5.3-alpha - 2014-03-22
10060 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
10061 two new anti-DoS features for Tor relays, resolves a bug that kept
10062 SOCKS5 support for IPv6 from working, fixes several annoying usability
10063 issues for bridge users, and removes more old code for unused
10066 The Tor 0.2.5.x release series is now in patch-freeze: no feature
10067 patches not already written will be considered for inclusion in 0.2.5.x.
10069 o Major features (relay security, DoS-resistance):
10070 - When deciding whether we have run out of memory and we need to
10071 close circuits, also consider memory allocated in buffers for
10072 streams attached to each circuit.
10074 This change, which extends an anti-DoS feature introduced in
10075 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
10076 better resist more memory-based DoS attacks than before. Since the
10077 MaxMemInCellQueues option now applies to all queues, it is renamed
10078 to MaxMemInQueues. This feature fixes bug 10169.
10079 - Avoid hash-flooding denial-of-service attacks by using the secure
10080 SipHash-2-4 hash function for our hashtables. Without this
10081 feature, an attacker could degrade performance of a targeted
10082 client or server by flooding their data structures with a large
10083 number of entries to be stored at the same hash table position,
10084 thereby slowing down the Tor instance. With this feature, hash
10085 table positions are derived from a randomized cryptographic key,
10086 and an attacker cannot predict which entries will collide. Closes
10088 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
10089 the default at 8GBytes), to better support Raspberry Pi users. Fixes
10090 bug 9686; bugfix on 0.2.4.14-alpha.
10092 o Minor features (bridges, pluggable transports):
10093 - Bridges now write the SHA1 digest of their identity key
10094 fingerprint (that is, a hash of a hash of their public key) to
10095 notice-level logs, and to a new hashed-fingerprint file. This
10096 information will help bridge operators look up their bridge in
10097 Globe and similar tools. Resolves ticket 10884.
10098 - Improve the message that Tor displays when running as a bridge
10099 using pluggable transports without an Extended ORPort listener.
10100 Also, log the message in the log file too. Resolves ticket 11043.
10102 o Minor features (other):
10103 - Add a new option, PredictedPortsRelevanceTime, to control how long
10104 after having received a request to connect to a given port Tor
10105 will try to keep circuits ready in anticipation of future requests
10106 for that port. Patch from "unixninja92"; implements ticket 9176.
10107 - Generate a warning if any ports are listed in the SocksPolicy,
10108 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
10109 AuthDirBadExit options. (These options only support address
10110 ranges.) Fixes part of ticket 11108.
10111 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
10114 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
10115 - Build without warnings under clang 3.4. (We have some macros that
10116 define static functions only some of which will get used later in
10117 the module. Starting with clang 3.4, these give a warning unless the
10118 unused attribute is set on them.) Resolves ticket 10904.
10119 - Fix build warnings about missing "a2x" comment when building the
10120 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
10121 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
10123 o Minor bugfixes (client):
10124 - Improve the log message when we can't connect to a hidden service
10125 because all of the hidden service directory nodes hosting its
10126 descriptor are excluded. Improves on our fix for bug 10722, which
10127 was a bugfix on 0.2.0.10-alpha.
10128 - Raise a control port warning when we fail to connect to all of
10129 our bridges. Previously, we didn't inform the controller, and
10130 the bootstrap process would stall. Fixes bug 11069; bugfix on
10132 - Exit immediately when a process-owning controller exits.
10133 Previously, tor relays would wait for a little while after their
10134 controller exited, as if they had gotten an INT signal -- but this
10135 was problematic, since there was no feedback for the user. To do a
10136 clean shutdown, controllers should send an INT signal and give Tor
10137 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
10138 - Stop attempting to connect to bridges before our pluggable
10139 transports are configured (harmless but resulted in some erroneous
10140 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
10141 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
10142 generating incorrect SOCKS5 responses, and confusing client
10143 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
10145 o Minor bugfixes (relays and bridges):
10146 - Avoid crashing on a malformed resolv.conf file when running a
10147 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
10148 - Non-exit relays no longer launch mock DNS requests to check for
10149 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
10150 non-exit relays stopped servicing DNS requests. Fixes bug 965;
10151 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
10152 - Bridges now report complete directory request statistics. Related
10153 to bug 5824; bugfix on 0.2.2.1-alpha.
10154 - Bridges now never collect statistics that were designed for
10155 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
10156 - Stop giving annoying warning messages when we decide not to launch
10157 a pluggable transport proxy that we don't need (because there are
10158 no bridges configured to use it). Resolves ticket 5018; bugfix
10160 - Give the correct URL in the warning message when trying to run a
10161 relay on an ancient version of Windows. Fixes bug 9393.
10163 o Minor bugfixes (backtrace support):
10164 - Support automatic backtraces on more platforms by using the
10165 "-fasynchronous-unwind-tables" compiler option. This option is
10166 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
10167 is on by default and table generation is not. This doesn't yet
10168 add Windows support; only Linux, OSX, and some BSDs are affected.
10169 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
10170 - Avoid strange behavior if two threads hit failed assertions at the
10171 same time and both try to log backtraces at once. (Previously, if
10172 this had happened, both threads would have stored their intermediate
10173 results in the same buffer, and generated junk outputs.) Reported by
10174 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
10175 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
10176 0.2.5.2-alpha; patch from Nick Hopper.
10178 o Minor bugfixes (unit tests):
10179 - Fix a small bug in the unit tests that might have made the tests
10180 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
10181 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
10184 - Remove all remaining code related to version-0 hidden service
10185 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
10186 the rest of bug 10841.
10189 - Document in the manpage that "KBytes" may also be written as
10190 "kilobytes" or "KB", that "Kbits" may also be written as
10191 "kilobits", and so forth. Closes ticket 9222.
10192 - Document that the ClientOnly config option overrides ORPort.
10193 Our old explanation made ClientOnly sound as though it did
10194 nothing at all. Resolves bug 9059.
10195 - Explain that SocksPolicy, DirPolicy, and similar options don't
10196 take port arguments. Fixes the other part of ticket 11108.
10197 - Fix a comment about the rend_server_descriptor_t.protocols field
10198 to more accurately describe its range. Also, make that field
10199 unsigned, to more accurately reflect its usage. Fixes bug 9099;
10200 bugfix on 0.2.1.5-alpha.
10201 - Fix the manpage's description of HiddenServiceAuthorizeClient:
10202 the maximum client name length is 16, not 19. Fixes bug 11118;
10203 bugfix on 0.2.1.6-alpha.
10205 o Code simplifications and refactoring:
10206 - Get rid of router->address, since in all cases it was just the
10207 string representation of router->addr. Resolves ticket 5528.
10209 o Test infrastructure:
10210 - Update to the latest version of tinytest.
10211 - Improve the tinytest implementation of string operation tests so
10212 that comparisons with NULL strings no longer crash the tests; they
10213 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
10216 Changes in version 0.2.4.21 - 2014-02-28
10217 Tor 0.2.4.21 further improves security against potential adversaries who
10218 find breaking 1024-bit crypto doable, and backports several stability
10219 and robustness patches from the 0.2.5 branch.
10221 o Major features (client security):
10222 - When we choose a path for a 3-hop circuit, make sure it contains
10223 at least one relay that supports the NTor circuit extension
10224 handshake. Otherwise, there is a chance that we're building
10225 a circuit that's worth attacking by an adversary who finds
10226 breaking 1024-bit crypto doable, and that chance changes the game
10227 theory. Implements ticket 9777.
10230 - Do not treat streams that fail with reason
10231 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
10232 since it could also indicate an ENETUNREACH connection error. Fixes
10233 part of bug 10777; bugfix on 0.2.4.8-alpha.
10235 o Code simplification and refactoring:
10236 - Remove data structures which were introduced to implement the
10237 CellStatistics option: they are now redundant with the new timestamp
10238 field in the regular packed_cell_t data structure, which we did
10239 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
10242 - Always clear OpenSSL bignums before freeing them -- even bignums
10243 that don't contain secrets. Resolves ticket 10793. Patch by
10245 - Build without warnings under clang 3.4. (We have some macros that
10246 define static functions only some of which will get used later in
10247 the module. Starting with clang 3.4, these give a warning unless the
10248 unused attribute is set on them.) Resolves ticket 10904.
10249 - Update geoip and geoip6 files to the February 7 2014 Maxmind
10250 GeoLite2 Country database.
10253 - Set the listen() backlog limit to the largest actually supported
10254 on the system, not to the value in a header file. Fixes bug 9716;
10255 bugfix on every released Tor.
10256 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
10257 exit node as a NOROUTE error, not an INTERNAL error, since they
10258 can apparently happen when trying to connect to the wrong sort
10259 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
10260 - Fix build warnings about missing "a2x" comment when building the
10261 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
10262 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
10263 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
10264 not entirely remove it from the connection lists. Fixes bug 9602;
10265 bugfix on 0.2.4.4-alpha.
10266 - Fix a segmentation fault in our benchmark code when running with
10267 Fedora's OpenSSL package, or any other OpenSSL that provides
10268 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
10269 - Turn "circuit handshake stats since last time" log messages into a
10270 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
10272 o Documentation fixes:
10273 - Document that all but one DirPort entry must have the NoAdvertise
10274 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
10277 Changes in version 0.2.5.2-alpha - 2014-02-13
10278 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
10279 like the "poor random number generation" fix and the "building too many
10280 circuits" fix. It also further improves security against potential
10281 adversaries who find breaking 1024-bit crypto doable, and launches
10282 pluggable transports on demand (which gets us closer to integrating
10283 pluggable transport support by default -- not to be confused with Tor
10284 bundles enabling pluggable transports and bridges by default).
10286 o Major features (client security):
10287 - When we choose a path for a 3-hop circuit, make sure it contains
10288 at least one relay that supports the NTor circuit extension
10289 handshake. Otherwise, there is a chance that we're building
10290 a circuit that's worth attacking by an adversary who finds
10291 breaking 1024-bit crypto doable, and that chance changes the game
10292 theory. Implements ticket 9777.
10293 - Clients now look at the "usecreatefast" consensus parameter to
10294 decide whether to use CREATE_FAST or CREATE cells for the first hop
10295 of their circuit. This approach can improve security on connections
10296 where Tor's circuit handshake is stronger than the available TLS
10297 connection security levels, but the tradeoff is more computational
10298 load on guard relays. Implements proposal 221. Resolves ticket 9386.
10300 o Major features (bridges):
10301 - Don't launch pluggable transport proxies if we don't have any
10302 bridges configured that would use them. Now we can list many
10303 pluggable transports, and Tor will dynamically start one when it
10304 hears a bridge address that needs it. Resolves ticket 5018.
10305 - The bridge directory authority now assigns status flags (Stable,
10306 Guard, etc) to bridges based on thresholds calculated over all
10307 Running bridges. Now bridgedb can finally make use of its features
10308 to e.g. include at least one Stable bridge in its answers. Fixes
10311 o Major features (other):
10312 - Extend ORCONN controller event to include an "ID" parameter,
10313 and add four new controller event types CONN_BW, CIRC_BW,
10314 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
10315 The new events are emitted in private Tor networks only, with the
10316 goal of being able to better track performance and load during
10317 full-network simulations. Implements proposal 218 and ticket 7359.
10318 - On some platforms (currently: recent OSX versions, glibc-based
10319 platforms that support the ELF format, and a few other
10320 Unix-like operating systems), Tor can now dump stack traces
10321 when a crash occurs or an assertion fails. By default, traces
10322 are dumped to stderr (if possible) and to any logs that are
10323 reporting errors. Implements ticket 9299.
10326 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
10327 not entirely remove it from the connection lists. Fixes bug 9602;
10328 bugfix on 0.2.4.4-alpha.
10329 - Do not treat streams that fail with reason
10330 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
10331 since it could also indicate an ENETUNREACH connection error. Fixes
10332 part of bug 10777; bugfix on 0.2.4.8-alpha.
10334 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
10335 - Do not allow OpenSSL engines to replace the PRNG, even when
10336 HardwareAccel is set. The only default builtin PRNG engine uses
10337 the Intel RDRAND instruction to replace the entire PRNG, and
10338 ignores all attempts to seed it with more entropy. That's
10339 cryptographically stupid: the right response to a new alleged
10340 entropy source is never to discard all previously used entropy
10341 sources. Fixes bug 10402; works around behavior introduced in
10342 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
10344 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
10345 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
10346 - Avoid launching spurious extra circuits when a stream is pending.
10347 This fixes a bug where any circuit that _wasn't_ unusable for new
10348 streams would be treated as if it were, causing extra circuits to
10349 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
10351 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10352 - No longer stop reading or writing on cpuworker connections when
10353 our rate limiting buckets go empty. Now we should handle circuit
10354 handshake requests more promptly. Resolves bug 9731.
10355 - Stop trying to bootstrap all our directory information from
10356 only our first guard. Discovered while fixing bug 9946; bugfix
10359 o Minor features (bridges, pluggable transports):
10360 - Add threshold cutoffs to the networkstatus document created by
10361 the Bridge Authority. Fixes bug 1117.
10362 - On Windows, spawn background processes using the CREATE_NO_WINDOW
10363 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
10364 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
10365 Vidalia set this option for us.) Implements ticket 10297.
10367 o Minor features (security):
10368 - Always clear OpenSSL bignums before freeing them -- even bignums
10369 that don't contain secrets. Resolves ticket 10793. Patch by
10370 Florent Daignière.
10372 o Minor features (config options and command line):
10373 - Add an --allow-missing-torrc commandline option that tells Tor to
10374 run even if the configuration file specified by -f is not available.
10375 Implements ticket 10060.
10376 - Add support for the TPROXY transparent proxying facility on Linux.
10377 See documentation for the new TransProxyType option for more
10378 details. Implementation by "thomo". Closes ticket 10582.
10380 o Minor features (controller):
10381 - Add a new "HS_DESC" controller event that reports activities
10382 related to hidden service descriptors. Resolves ticket 8510.
10383 - New "DROPGUARDS" controller command to forget all current entry
10384 guards. Not recommended for ordinary use, since replacing guards
10385 too frequently makes several attacks easier. Resolves ticket 9934;
10388 o Minor features (build):
10389 - Assume that a user using ./configure --host wants to cross-compile,
10390 and give an error if we cannot find a properly named
10391 tool-chain. Add a --disable-tool-name-check option to proceed
10392 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
10393 - If we run ./configure and the compiler recognizes -fstack-protector
10394 but the linker rejects it, warn the user about a potentially missing
10395 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
10397 o Minor features (testing):
10398 - If Python is installed, "make check" now runs extra tests beyond
10399 the unit test scripts.
10400 - When bootstrapping a test network, sometimes very few relays get
10401 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
10402 specify a set of relays which should be voted Guard regardless of
10403 their uptime or bandwidth. Addresses ticket 9206.
10405 o Minor features (log messages):
10406 - When ServerTransportPlugin is set on a bridge, Tor can write more
10407 useful statistics about bridge use in its extrainfo descriptors,
10408 but only if the Extended ORPort ("ExtORPort") is set too. Add a
10409 log message to inform the user in this case. Resolves ticket 9651.
10410 - When receiving a new controller connection, log the origin address.
10411 Resolves ticket 9698; patch from "sigpipe".
10412 - When logging OpenSSL engine status at startup, log the status of
10413 more engines. Fixes ticket 10043; patch from Joshua Datko.
10414 - Turn "circuit handshake stats since last time" log messages into a
10415 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
10417 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10418 - Improve the circuit queue out-of-memory handler. Previously, when
10419 we ran low on memory, we'd close whichever circuits had the most
10420 queued cells. Now, we close those that have the *oldest* queued
10421 cells, on the theory that those are most responsible for us
10422 running low on memory. Based on analysis from a forthcoming paper
10423 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
10424 - Generate bootstrapping status update events correctly when fetching
10425 microdescriptors. Fixes bug 9927.
10426 - Update to the October 2 2013 Maxmind GeoLite Country database.
10428 o Minor bugfixes (clients):
10429 - When closing a channel that has already been open, do not close
10430 pending circuits that were waiting to connect to the same relay.
10431 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
10434 o Minor bugfixes (relays):
10435 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
10436 exit node as a NOROUTE error, not an INTERNAL error, since they
10437 can apparently happen when trying to connect to the wrong sort
10438 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
10440 o Minor bugfixes (bridges):
10441 - Fix a bug where the first connection works to a bridge that uses a
10442 pluggable transport with client-side parameters, but we don't send
10443 the client-side parameters on subsequent connections. (We don't
10444 use any pluggable transports with client-side parameters yet,
10445 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
10446 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
10448 o Minor bugfixes (node selection):
10449 - If ExcludeNodes is set, consider non-excluded hidden service
10450 directory servers before excluded ones. Do not consider excluded
10451 hidden service directory servers at all if StrictNodes is
10452 set. (Previously, we would sometimes decide to connect to those
10453 servers, and then realize before we initiated a connection that
10454 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
10455 Reported by "mr-4".
10456 - If we set the ExitNodes option but it doesn't include any nodes
10457 that have the Exit flag, we would choose not to bootstrap. Now we
10458 bootstrap so long as ExitNodes includes nodes which can exit to
10459 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
10461 o Minor bugfixes (controller and command-line):
10462 - If changing a config option via "setconf" fails in a recoverable
10463 way, we used to nonetheless write our new control ports to the
10464 file described by the "ControlPortWriteToFile" option. Now we only
10465 write out that file if we successfully switch to the new config
10466 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
10467 - When a command-line option such as --version or --help that
10468 ordinarily implies --hush appears on the command line along with
10469 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
10470 only if it appeared later on the command line. Fixes bug 9578;
10471 bugfix on 0.2.5.1-alpha.
10473 o Minor bugfixes (code correctness):
10474 - Previously we used two temporary files when writing descriptors to
10475 disk; now we only use one. Fixes bug 1376.
10476 - Remove an erroneous (but impossible and thus harmless) pointer
10477 comparison that would have allowed compilers to skip a bounds
10478 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
10479 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
10480 - Fix an always-true assertion in pluggable transports code so it
10481 actually checks what it was trying to check. Fixes bug 10046;
10482 bugfix on 0.2.3.9-alpha. Found by "dcb".
10484 o Minor bugfixes (protocol correctness):
10485 - When receiving a VERSIONS cell with an odd number of bytes, close
10486 the connection immediately since the cell is malformed. Fixes bug
10487 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
10490 o Minor bugfixes (build):
10491 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
10492 turned off (that is, without support for v2 link handshakes). Fixes
10493 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
10494 - Fix compilation warnings and startup issues when running with
10495 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
10497 - Fix compilation on Solaris 9, which didn't like us having an
10498 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
10500 o Minor bugfixes (testing):
10501 - Fix a segmentation fault in our benchmark code when running with
10502 Fedora's OpenSSL package, or any other OpenSSL that provides
10503 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
10505 o Minor bugfixes (log messages):
10506 - Fix a bug where clients using bridges would report themselves
10507 as 50% bootstrapped even without a live consensus document.
10508 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
10509 - Suppress a warning where, if there's only one directory authority
10510 in the network, we would complain that votes and signatures cannot
10511 be uploaded to other directory authorities. Fixes bug 10842;
10512 bugfix on 0.2.2.26-beta.
10513 - Report bootstrapping progress correctly when we're downloading
10514 microdescriptors. We had updated our "do we have enough microdescs
10515 to begin building circuits?" logic most recently in 0.2.4.10-alpha
10516 (see bug 5956), but we left the bootstrap status event logic at
10517 "how far through getting 1/4 of them are we?" Fixes bug 9958;
10518 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
10520 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
10521 - Avoid a crash bug when starting with a corrupted microdescriptor
10522 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
10523 - If we fail to dump a previously cached microdescriptor to disk, avoid
10524 freeing duplicate data later on. Fixes bug 10423; bugfix on
10525 0.2.4.13-alpha. Spotted by "bobnomnom".
10527 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10528 - Correctly log long IPv6 exit policies, instead of truncating them
10529 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
10530 - Our default TLS ecdhe groups were backwards: we meant to be using
10531 P224 for relays (for performance win) and P256 for bridges (since
10532 it is more common in the wild). Instead we had it backwards. After
10533 reconsideration, we decided that the default should be P256 on all
10534 hosts, since its security is probably better, and since P224 is
10535 reportedly used quite little in the wild. Found by "skruffy" on
10536 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
10537 - Free directory authority certificate download statuses on exit
10538 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
10540 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10541 - If the guard we choose first doesn't answer, we would try the
10542 second guard, but once we connected to the second guard we would
10543 abandon it and retry the first one, slowing down bootstrapping.
10544 The fix is to treat all our initially chosen guards as acceptable
10545 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10546 - Fix an assertion failure that would occur when disabling the
10547 ORPort setting on a running Tor process while accounting was
10548 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10549 - When examining the list of network interfaces to find our address,
10550 do not consider non-running or disabled network interfaces. Fixes
10551 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10552 - Avoid an off-by-one error when checking buffer boundaries when
10553 formatting the exit status of a pluggable transport helper.
10554 This is probably not an exploitable bug, but better safe than
10555 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10558 o Removed code and features:
10559 - Clients now reject any directory authority certificates lacking
10560 a dir-key-crosscert element. These have been included since
10561 0.2.1.9-alpha, so there's no real reason for them to be optional
10562 any longer. Completes proposal 157. Resolves ticket 10162.
10563 - Remove all code that existed to support the v2 directory system,
10564 since there are no longer any v2 directory authorities. Resolves
10566 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
10567 options, which were used for designating authorities as "Hidden
10568 service authorities". There has been no use of hidden service
10569 authorities since 0.2.2.1-alpha, when we stopped uploading or
10570 downloading v0 hidden service descriptors. Fixes bug 10881; also
10571 part of a fix for bug 10841.
10573 o Code simplification and refactoring:
10574 - Remove some old fallback code designed to keep Tor clients working
10575 in a network with only two working relays. Elsewhere in the code we
10576 have long since stopped supporting such networks, so there wasn't
10577 much point in keeping it around. Addresses ticket 9926.
10578 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
10579 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
10580 - Remove data structures which were introduced to implement the
10581 CellStatistics option: they are now redundant with the addition
10582 of a timestamp to the regular packed_cell_t data structure, which
10583 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
10586 o Documentation (man page) fixes:
10587 - Update manpage to describe some of the files you can expect to
10588 find in Tor's DataDirectory. Addresses ticket 9839.
10589 - Document that all but one DirPort entry must have the NoAdvertise
10590 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
10592 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10593 - Clarify the usage and risks of setting the ContactInfo torrc line
10594 for your relay or bridge. Resolves ticket 9854.
10595 - Add anchors to the manpage so we can link to the html version of
10596 the documentation for specific options. Resolves ticket 9866.
10597 - Replace remaining references to DirServer in man page and
10598 log entries. Resolves ticket 10124.
10601 - Make the "tor-gencert" tool used by directory authority operators
10602 create 2048-bit signing keys by default (rather than 1024-bit, since
10603 1024-bit is uncomfortably small these days). Addresses ticket 10324.
10606 Changes in version 0.2.4.20 - 2013-12-22
10607 Tor 0.2.4.20 fixes potentially poor random number generation for users
10608 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
10609 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
10610 and 4) have no state file in their DataDirectory (as would happen on
10611 first start). Users who generated relay or hidden service identity
10612 keys in such a situation should discard them and generate new ones.
10614 This release also fixes a logic error that caused Tor clients to build
10615 many more preemptive circuits than they actually need.
10618 - Do not allow OpenSSL engines to replace the PRNG, even when
10619 HardwareAccel is set. The only default builtin PRNG engine uses
10620 the Intel RDRAND instruction to replace the entire PRNG, and
10621 ignores all attempts to seed it with more entropy. That's
10622 cryptographically stupid: the right response to a new alleged
10623 entropy source is never to discard all previously used entropy
10624 sources. Fixes bug 10402; works around behavior introduced in
10625 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
10627 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
10628 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
10629 - Avoid launching spurious extra circuits when a stream is pending.
10630 This fixes a bug where any circuit that _wasn't_ unusable for new
10631 streams would be treated as if it were, causing extra circuits to
10632 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
10635 - Avoid a crash bug when starting with a corrupted microdescriptor
10636 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
10637 - If we fail to dump a previously cached microdescriptor to disk, avoid
10638 freeing duplicate data later on. Fixes bug 10423; bugfix on
10639 0.2.4.13-alpha. Spotted by "bobnomnom".
10642 Changes in version 0.2.4.19 - 2013-12-11
10643 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
10644 (1986-2013). Aaron worked on diverse projects including helping to guide
10645 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
10646 transparency to the U.S government's PACER documents, and contributing
10647 design and development for Tor and Tor2Web. Aaron was one of the latest
10648 martyrs in our collective fight for civil liberties and human rights,
10649 and his death is all the more painful because he was one of us.
10651 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
10652 a new circuit handshake and link encryption that use ECC to provide
10653 better security and efficiency; makes relays better manage circuit
10654 creation requests; uses "directory guards" to reduce client enumeration
10655 risks; makes bridges collect and report statistics about the pluggable
10656 transports they support; cleans up and improves our geoip database;
10657 gets much closer to IPv6 support for clients, bridges, and relays; makes
10658 directory authorities use measured bandwidths rather than advertised
10659 ones when computing flags and thresholds; disables client-side DNS
10660 caching to reduce tracking risks; and fixes a big bug in bridge
10661 reachability testing. This release introduces two new design
10662 abstractions in the code: a new "channel" abstraction between circuits
10663 and or_connections to allow for implementing alternate relay-to-relay
10664 transports, and a new "circuitmux" abstraction storing the queue of
10665 circuits for a channel. The release also includes many stability,
10666 security, and privacy fixes.
10669 Changes in version 0.2.4.18-rc - 2013-11-16
10670 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
10671 series. It takes a variety of fixes from the 0.2.5.x branch to improve
10672 stability, performance, and better handling of edge cases.
10675 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10676 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10677 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10678 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10679 them to solve bug 6033.)
10682 - No longer stop reading or writing on cpuworker connections when
10683 our rate limiting buckets go empty. Now we should handle circuit
10684 handshake requests more promptly. Resolves bug 9731.
10685 - If we are unable to save a microdescriptor to the journal, do not
10686 drop it from memory and then reattempt downloading it. Fixes bug
10687 9645; bugfix on 0.2.2.6-alpha.
10688 - Stop trying to bootstrap all our directory information from
10689 only our first guard. Discovered while fixing bug 9946; bugfix
10691 - The new channel code sometimes lost track of in-progress circuits,
10692 causing long-running clients to stop building new circuits. The
10693 fix is to always call circuit_n_chan_done(chan, 0) from
10694 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
10696 o Minor bugfixes (on 0.2.4.x):
10697 - Correctly log long IPv6 exit policies, instead of truncating them
10698 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
10699 - Our default TLS ecdhe groups were backwards: we meant to be using
10700 P224 for relays (for performance win) and P256 for bridges (since
10701 it is more common in the wild). Instead we had it backwards. After
10702 reconsideration, we decided that the default should be P256 on all
10703 hosts, since its security is probably better, and since P224 is
10704 reportedly used quite little in the wild. Found by "skruffy" on
10705 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
10706 - Free directory authority certificate download statuses on exit
10707 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
10709 o Minor bugfixes (on 0.2.3.x and earlier):
10710 - If the guard we choose first doesn't answer, we would try the
10711 second guard, but once we connected to the second guard we would
10712 abandon it and retry the first one, slowing down bootstrapping.
10713 The fix is to treat all our initially chosen guards as acceptable
10714 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10715 - Fix an assertion failure that would occur when disabling the
10716 ORPort setting on a running Tor process while accounting was
10717 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10718 - When examining the list of network interfaces to find our address,
10719 do not consider non-running or disabled network interfaces. Fixes
10720 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10721 - Avoid an off-by-one error when checking buffer boundaries when
10722 formatting the exit status of a pluggable transport helper.
10723 This is probably not an exploitable bug, but better safe than
10724 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10727 o Minor features (protecting client timestamps):
10728 - Clients no longer send timestamps in their NETINFO cells. These were
10729 not used for anything, and they provided one small way for clients
10730 to be distinguished from each other as they moved from network to
10731 network or behind NAT. Implements part of proposal 222.
10732 - Clients now round timestamps in INTRODUCE cells down to the nearest
10733 10 minutes. If a new Support022HiddenServices option is set to 0, or
10734 if it's set to "auto" and the feature is disabled in the consensus,
10735 the timestamp is sent as 0 instead. Implements part of proposal 222.
10736 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10737 a big deal from a security point of view, but it achieves no actual
10738 good purpose, and isn't needed. Implements part of proposal 222.
10739 - Reduce down accuracy of timestamps in hidden service descriptors.
10740 Implements part of proposal 222.
10742 o Minor features (other):
10743 - Improve the circuit queue out-of-memory handler. Previously, when
10744 we ran low on memory, we'd close whichever circuits had the most
10745 queued cells. Now, we close those that have the *oldest* queued
10746 cells, on the theory that those are most responsible for us
10747 running low on memory. Based on analysis from a forthcoming paper
10748 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
10749 - Generate bootstrapping status update events correctly when fetching
10750 microdescriptors. Fixes bug 9927.
10751 - Update to the October 2 2013 Maxmind GeoLite Country database.
10753 o Documentation fixes:
10754 - Clarify the usage and risks of setting the ContactInfo torrc line
10755 for your relay or bridge. Resolves ticket 9854.
10756 - Add anchors to the manpage so we can link to the html version of
10757 the documentation for specific options. Resolves ticket 9866.
10758 - Replace remaining references to DirServer in man page and
10759 log entries. Resolves ticket 10124.
10762 Changes in version 0.2.5.1-alpha - 2013-10-02
10763 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
10764 on Linux, allows bridges that offer pluggable transports to report usage
10765 statistics, fixes many issues to make testing easier, and provides
10766 a pile of minor features and bugfixes that have been waiting for a
10767 release of the new branch.
10769 This is the first alpha release in a new series, so expect there to
10770 be bugs. Users who would rather test out a more stable branch should
10771 stay with 0.2.4.x for now.
10773 o Major features (security):
10774 - Use the seccomp2 syscall filtering facility on Linux to limit
10775 which system calls Tor can invoke. This is an experimental,
10776 Linux-only feature to provide defense-in-depth against unknown
10777 attacks. To try turning it on, set "Sandbox 1" in your torrc
10778 file. Please be ready to report bugs. We hope to add support
10779 for better sandboxing in the future, including more fine-grained
10780 filters, better division of responsibility, and support for more
10781 platforms. This work has been done by Cristian-Matei Toader for
10782 Google Summer of Code.
10783 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10784 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10785 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10786 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10787 them to solve bug 6033.)
10789 o Major features (other):
10790 - Add support for passing arguments to managed pluggable transport
10791 proxies. Implements ticket 3594.
10792 - Bridges now track GeoIP information and the number of their users
10793 even when pluggable transports are in use, and report usage
10794 statistics in their extra-info descriptors. Resolves tickets 4773
10796 - Make testing Tor networks bootstrap better: lower directory fetch
10797 retry schedules and maximum interval without directory requests,
10798 and raise maximum download tries. Implements ticket 6752.
10799 - Add make target 'test-network' to run tests on a Chutney network.
10800 Implements ticket 8530.
10801 - The ntor handshake is now on-by-default, no matter what the
10802 directory authorities recommend. Implements ticket 8561.
10805 - Instead of writing destroy cells directly to outgoing connection
10806 buffers, queue them and intersperse them with other outgoing cells.
10807 This can prevent a set of resource starvation conditions where too
10808 many pending destroy cells prevent data cells from actually getting
10809 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
10810 bugfix on 0.2.0.1-alpha.
10811 - If we are unable to save a microdescriptor to the journal, do not
10812 drop it from memory and then reattempt downloading it. Fixes bug
10813 9645; bugfix on 0.2.2.6-alpha.
10814 - The new channel code sometimes lost track of in-progress circuits,
10815 causing long-running clients to stop building new circuits. The
10816 fix is to always call circuit_n_chan_done(chan, 0) from
10817 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
10820 - Tor now builds each source file in two modes: a mode that avoids
10821 exposing identifiers needlessly, and another mode that exposes
10822 more identifiers for testing. This lets the compiler do better at
10823 optimizing the production code, while enabling us to take more
10824 radical measures to let the unit tests test things.
10825 - The production builds no longer include functions used only in
10826 the unit tests; all functions exposed from a module only for
10827 unit-testing are now static in production builds.
10828 - Add an --enable-coverage configuration option to make the unit
10829 tests (and a new src/or/tor-cov target) to build with gcov test
10833 - We now have rudimentary function mocking support that our unit
10834 tests can use to test functions in isolation. Function mocking
10835 lets the tests temporarily replace a function's dependencies with
10836 stub functions, so that the tests can check the function without
10837 invoking the other functions it calls.
10838 - Add more unit tests for the <circid,channel>->circuit map, and
10839 the destroy-cell-tracking code to fix bug 7912.
10840 - Unit tests for failing cases of the TAP onion handshake.
10841 - More unit tests for address-manipulation functions.
10843 o Minor features (protecting client timestamps):
10844 - Clients no longer send timestamps in their NETINFO cells. These were
10845 not used for anything, and they provided one small way for clients
10846 to be distinguished from each other as they moved from network to
10847 network or behind NAT. Implements part of proposal 222.
10848 - Clients now round timestamps in INTRODUCE cells down to the nearest
10849 10 minutes. If a new Support022HiddenServices option is set to 0, or
10850 if it's set to "auto" and the feature is disabled in the consensus,
10851 the timestamp is sent as 0 instead. Implements part of proposal 222.
10852 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10853 a big deal from a security point of view, but it achieves no actual
10854 good purpose, and isn't needed. Implements part of proposal 222.
10855 - Reduce down accuracy of timestamps in hidden service descriptors.
10856 Implements part of proposal 222.
10858 o Minor features (config options):
10859 - Config (torrc) lines now handle fingerprints which are missing
10860 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
10861 - Support a --dump-config option to print some or all of the
10862 configured options. Mainly useful for debugging the command-line
10863 option parsing code. Helps resolve ticket 4647.
10864 - Raise awareness of safer logging: notify user of potentially
10865 unsafe config options, like logging more verbosely than severity
10866 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
10867 - Add a new configuration option TestingV3AuthVotingStartOffset
10868 that bootstraps a network faster by changing the timing for
10869 consensus votes. Addresses ticket 8532.
10870 - Add a new torrc option "ServerTransportOptions" that allows
10871 bridge operators to pass configuration parameters to their
10872 pluggable transports. Resolves ticket 8929.
10873 - The config (torrc) file now accepts bandwidth and space limits in
10874 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
10875 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
10878 o Minor features (build):
10879 - Add support for `--library-versions` flag. Implements ticket 6384.
10880 - Return the "unexpected sendme" warnings to a warn severity, but make
10881 them rate limited, to help diagnose ticket 8093.
10882 - Detect a missing asciidoc, and warn the user about it, during
10883 configure rather than at build time. Fixes issue 6506. Patch from
10886 o Minor features (other):
10887 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
10888 sockets in a single system call. Implements ticket 5129.
10889 - Log current accounting state (bytes sent and received + remaining
10890 time for the current accounting period) in the relay's heartbeat
10891 message. Implements ticket 5526; patch from Peter Retzlaff.
10892 - Implement the TRANSPORT_LAUNCHED control port event that
10893 notifies controllers about new launched pluggable
10894 transports. Resolves ticket 5609.
10895 - If we're using the pure-C 32-bit curve25519_donna implementation
10896 of curve25519, build it with the -fomit-frame-pointer option to
10897 make it go faster on register-starved hosts. This improves our
10898 handshake performance by about 6% on i386 hosts without nacl.
10899 Closes ticket 8109.
10900 - Update to the September 4 2013 Maxmind GeoLite Country database.
10903 - Set the listen() backlog limit to the largest actually supported
10904 on the system, not to the value in a header file. Fixes bug 9716;
10905 bugfix on every released Tor.
10906 - No longer accept malformed http headers when parsing urls from
10907 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
10908 bugfix on 0.0.6pre1.
10909 - In munge_extrainfo_into_routerinfo(), check the return value of
10910 memchr(). This would have been a serious issue if we ever passed
10911 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
10913 - On the chance that somebody manages to build Tor on a
10914 platform where time_t is unsigned, correct the way that
10915 microdesc_add_to_cache() handles negative time arguments.
10916 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
10917 - Reject relative control socket paths and emit a warning. Previously,
10918 single-component control socket paths would be rejected, but Tor
10919 would not log why it could not validate the config. Fixes bug 9258;
10920 bugfix on 0.2.3.16-alpha.
10922 o Minor bugfixes (command line):
10923 - Use a single command-line parser for parsing torrc options on the
10924 command line and for finding special command-line options to avoid
10925 inconsistent behavior for torrc option arguments that have the same
10926 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
10928 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
10929 9573; bugfix on 0.0.9pre5.
10931 o Minor fixes (build, auxiliary programs):
10932 - Stop preprocessing the "torify" script with autoconf, since
10933 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
10935 - The tor-fw-helper program now follows the standard convention and
10936 exits with status code "0" on success. Fixes bug 9030; bugfix on
10937 0.2.3.1-alpha. Patch by Arlo Breault.
10938 - Corrected ./configure advice for what openssl dev package you should
10939 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
10941 o Minor code improvements:
10942 - Remove constants and tests for PKCS1 padding; it's insecure and
10943 shouldn't be used for anything new. Fixes bug 8792; patch
10945 - Remove instances of strcpy() from the unit tests. They weren't
10946 hurting anything, since they were only in the unit tests, but it's
10947 embarassing to have strcpy() in the code at all, and some analysis
10948 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
10949 0.2.3.8-alpha. Patch from Arlo Breault.
10951 o Removed features:
10952 - Remove migration code from when we renamed the "cached-routers"
10953 file to "cached-descriptors" back in 0.2.0.8-alpha. This
10954 incidentally resolves ticket 6502 by cleaning up the related code
10955 a bit. Patch from Akshay Hebbar.
10957 o Code simplification and refactoring:
10958 - Extract the common duplicated code for creating a subdirectory
10959 of the data directory and writing to a file in it. Fixes ticket
10960 4282; patch from Peter Retzlaff.
10961 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
10962 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
10963 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
10964 - Add a set of accessor functions for the circuit timeout data
10965 structure. Fixes ticket 6153; patch from "piet".
10966 - Clean up exit paths from connection_listener_new(). Closes ticket
10967 8789. Patch from Arlo Breault.
10968 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
10969 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
10970 - Use a doubly-linked list to implement the global circuit list.
10971 Resolves ticket 9108. Patch from Marek Majkowski.
10972 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
10975 Changes in version 0.2.4.17-rc - 2013-09-05
10976 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
10977 series. It adds an emergency step to help us tolerate the massive
10978 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
10979 circuit-level handshakes now effectively jump the queue compared to
10980 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
10981 big bug hindering bridge reachability tests.
10984 - Relays now process the new "NTor" circuit-level handshake requests
10985 with higher priority than the old "TAP" circuit-level handshake
10986 requests. We still process some TAP requests to not totally starve
10987 0.2.3 clients when NTor becomes popular. A new consensus parameter
10988 "NumNTorsPerTAP" lets us tune the balance later if we need to.
10989 Implements ticket 9574.
10992 - If the circuit build timeout logic is disabled (via the consensus,
10993 or because we are an authority), then don't build testing circuits.
10994 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
10995 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
10996 previously they did not, which prevented them from receiving
10997 successful connections from relays for self-test or bandwidth
10998 testing. Also, when a relay is extending a circuit to a bridge,
10999 it needs to send a NETINFO cell, even when the bridge hasn't sent
11000 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
11001 - If the time to download the next old-style networkstatus is in
11002 the future, do not decline to consider whether to download the
11003 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
11007 - Avoid double-closing the listener socket in our socketpair()
11008 replacement (used on Windows) in the case where the addresses on
11009 our opened sockets don't match what we expected. Fixes bug 9400;
11010 bugfix on 0.0.2pre7. Found by Coverity.
11012 o Minor fixes (config options):
11013 - Avoid overflows when the user sets MaxCircuitDirtiness to a
11014 ridiculously high value, by imposing a (ridiculously high) 30-day
11015 maximum on MaxCircuitDirtiness.
11016 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
11017 message is logged at notice, not at info.
11018 - Warn and fail if a server is configured not to advertise any
11019 ORPorts at all. (We need *something* to put in our descriptor,
11020 or we just won't work.)
11023 - Track how many "TAP" and "NTor" circuit handshake requests we get,
11024 and how many we complete, and log it every hour to help relay
11025 operators follow trends in network load. Addresses ticket 9658.
11026 - Update to the August 7 2013 Maxmind GeoLite Country database.
11029 Changes in version 0.2.4.16-rc - 2013-08-10
11030 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
11031 series. It fixes several crash bugs in the 0.2.4 branch.
11034 - Fix a bug in the voting algorithm that could yield incorrect results
11035 when a non-naming authority declared too many flags. Fixes bug 9200;
11036 bugfix on 0.2.0.3-alpha.
11037 - Fix an uninitialized read that could in some cases lead to a remote
11038 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
11039 Anybody running a hidden service on the experimental 0.2.4.x
11040 branch should upgrade. (This is, so far as we know, unrelated to
11042 - Avoid an assertion failure when processing DNS replies without the
11043 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
11044 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
11045 0.2.4.15-rc. Found by stem integration tests.
11048 - Fix an invalid memory read that occured when a pluggable
11049 transport proxy failed its configuration protocol.
11050 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
11051 - When evaluating whether to use a connection that we haven't
11052 decided is canonical using a recent link protocol version,
11053 decide that it's canonical only if it used address _does_
11054 match the desired address. Fixes bug 9309; bugfix on
11055 0.2.4.4-alpha. Reported by skruffy.
11056 - Make the default behavior of NumDirectoryGuards be to track
11057 NumEntryGuards. Now a user who changes only NumEntryGuards will get
11058 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
11059 - Fix a spurious compilation warning with some older versions of
11060 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
11063 - Update to the July 3 2013 Maxmind GeoLite Country database.
11066 Changes in version 0.2.4.15-rc - 2013-07-01
11067 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
11068 series. It fixes a few smaller bugs, but generally appears stable.
11069 Please test it and let us know whether it is!
11072 - When receiving a new configuration file via the control port's
11073 LOADCONF command, do not treat the defaults file as absent.
11074 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
11077 - Issue a warning when running with the bufferevents backend enabled.
11078 It's still not stable, and people should know that they're likely
11079 to hit unexpected problems. Closes ticket 9147.
11082 Changes in version 0.2.4.14-alpha - 2013-06-18
11083 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
11084 present in 0.2.4.13-alpha.
11087 - When we have too much memory queued in circuits (according to a new
11088 MaxMemInCellQueues option), close the circuits consuming the most
11089 memory. This prevents us from running out of memory as a relay if
11090 circuits fill up faster than they can be drained. Fixes bug 9063;
11091 bugfix on the 54th commit of Tor. This bug is a further fix beyond
11092 bug 6252, whose fix was merged into 0.2.3.21-rc.
11094 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
11095 where we tried to solve this issue simply by imposing an upper limit
11096 on the number of queued cells for a single circuit. That approach
11097 proved to be problematic, since there are ways to provoke clients to
11098 send a number of cells in excess of any such reasonable limit. Fixes
11099 bug 9072; bugfix on 0.2.4.13-alpha.
11101 - Limit hidden service descriptors to at most ten introduction
11102 points, to slow one kind of guard enumeration. Fixes bug 9002;
11103 bugfix on 0.1.1.11-alpha.
11106 Changes in version 0.2.4.13-alpha - 2013-06-14
11107 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
11108 vulnerabilities, makes socks5 username/password circuit isolation
11109 actually actually work (this time for sure!), and cleans up a bunch
11110 of other issues in preparation for a release candidate.
11112 o Major bugfixes (robustness):
11113 - Close any circuit that has too many cells queued on it. Fixes
11114 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
11115 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
11116 - Prevent the get_freelists() function from running off the end of
11117 the list of freelists if it somehow gets an unrecognized
11118 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
11120 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
11121 when an exit connection with optimistic data succeeds immediately
11122 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
11124 - Fix a directory authority crash bug when building a consensus
11125 using an older consensus as its basis. Fixes bug 8833. Bugfix
11129 - Avoid a memory leak where we would leak a consensus body when we
11130 find that a consensus which we couldn't previously verify due to
11131 missing certificates is now verifiable. Fixes bug 8719; bugfix
11133 - We used to always request authority certificates by identity digest,
11134 meaning we'd get the newest one even when we wanted one with a
11135 different signing key. Then we would complain about being given
11136 a certificate we already had, and never get the one we really
11137 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
11138 resource to request the one we want. Fixes bug 5595; bugfix on
11140 - Follow the socks5 protocol when offering username/password
11141 authentication. The fix for bug 8117 exposed this bug, and it
11142 turns out real-world applications like Pidgin do care. Bugfix on
11143 0.2.3.2-alpha; fixes bug 8879.
11144 - Prevent failures on Windows Vista and later when rebuilding the
11145 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
11146 bugfix on 0.2.4.12-alpha.
11149 - Fix an impossible buffer overrun in the AES unit tests. Fixes
11150 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
11151 - If for some reason we fail to write a microdescriptor while
11152 rebuilding the cache, do not let the annotations from that
11153 microdescriptor linger in the cache file, and do not let the
11154 microdescriptor stay recorded as present in its old location.
11155 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
11156 - Fix a memory leak that would occur whenever a configuration
11157 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
11158 - Paste the description for PathBias parameters from the man
11159 page into or.h, so the code documents them too. Fixes bug 7982;
11160 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
11161 - Relays now treat a changed IPv6 ORPort as sufficient reason to
11162 publish an updated descriptor. Fixes bug 6026; bugfix on
11164 - When launching a resolve request on behalf of an AF_UNIX control
11165 socket, omit the address field of the new entry connection, used in
11166 subsequent controller events, rather than letting tor_dup_addr()
11167 set it to "<unknown address type>". Fixes bug 8639; bugfix on
11170 o Minor bugfixes (log messages):
11171 - Fix a scaling issue in the path bias accounting code that
11172 resulted in "Bug:" log messages from either
11173 pathbias_scale_close_rates() or pathbias_count_build_success().
11174 This represents a bugfix on a previous bugfix: the original fix
11175 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
11177 - Give a less useless error message when the user asks for an IPv4
11178 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
11182 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
11183 to tolerate bug 8093 for now.
11184 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
11185 in directory authority votes to describe whether they have enough
11186 measured bandwidths to ignore advertised (relay descriptor)
11187 bandwidth claims. Resolves ticket 8711.
11188 - Update to the June 5 2013 Maxmind GeoLite Country database.
11190 o Removed documentation:
11191 - Remove some of the older contents of doc/ as obsolete; move others
11192 to torspec.git. Fixes bug 8965.
11194 o Code simplification and refactoring:
11195 - Avoid using character buffers when constructing most directory
11196 objects: this approach was unwieldy and error-prone. Instead,
11197 build smartlists of strings, and concatenate them when done.
11200 Changes in version 0.2.4.12-alpha - 2013-04-18
11201 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
11202 process for lengthening the guard rotation period, makes directory
11203 authority opinions in the consensus a bit less gameable, makes socks5
11204 username/password circuit isolation actually work, and fixes a wide
11205 variety of other issues.
11208 - Raise the default time that a client keeps an entry guard from
11209 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
11210 2012 paper. (We would make it even longer, but we need better client
11211 load balancing first.) Also, make the guard lifetime controllable
11212 via a new GuardLifetime torrc option and a GuardLifetime consensus
11213 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
11214 - Directory authorities now prefer using measured bandwidths to
11215 advertised ones when computing flags and thresholds. Resolves
11217 - Directory authorities that have more than a threshold number
11218 of relays with measured bandwidths now treat relays with unmeasured
11219 bandwidths as having bandwidth 0. Resolves ticket 8435.
11221 o Major bugfixes (assert / resource use):
11222 - Avoid a bug where our response to TLS renegotiation under certain
11223 network conditions could lead to a busy-loop, with 100% CPU
11224 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
11225 - Avoid an assertion when we discover that we'd like to write a cell
11226 onto a closing connection: just discard the cell. Fixes another
11227 case of bug 7350; bugfix on 0.2.4.4-alpha.
11229 o Major bugfixes (client-side privacy):
11230 - When we mark a circuit as unusable for new circuits, have it
11231 continue to be unusable for new circuits even if MaxCircuitDirtiness
11232 is increased too much at the wrong time, or the system clock jumps
11233 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
11234 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
11235 which have resolved to internal addresses") is set, apply that
11236 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
11237 - When an exit relay rejects a stream with reason "exit policy", but
11238 we only know an exit policy summary (e.g. from the microdesc
11239 consensus) for it, do not mark the relay as useless for all exiting.
11240 Instead, mark just the circuit as unsuitable for that particular
11241 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
11242 - Allow applications to get proper stream isolation with
11243 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
11244 username/password authentication also offer "no authentication". Tor
11245 had previously preferred "no authentication", so the applications
11246 never actually sent Tor their auth details. Now Tor selects
11247 username/password authentication if it's offered. You can disable
11248 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
11249 bug 8117; bugfix on 0.2.3.3-alpha.
11251 o Major bugfixes (other):
11252 - When unable to find any working directory nodes to use as a
11253 directory guard, give up rather than adding the same non-working
11254 nodes to the directory guard list over and over. Fixes bug 8231;
11255 bugfix on 0.2.4.8-alpha.
11258 - Reject as invalid most directory objects containing a NUL.
11259 Belt-and-suspender fix for bug 8037.
11260 - In our testsuite, create temporary directories with a bit more
11261 entropy in their name to make name collisions less likely. Fixes
11263 - Add CACHED keyword to ADDRMAP events in the control protocol
11264 to indicate whether a DNS result will be cached or not. Resolves
11266 - Update to the April 3 2013 Maxmind GeoLite Country database.
11268 o Minor features (build):
11269 - Detect and reject attempts to build Tor with threading support
11270 when OpenSSL has been compiled without threading support.
11272 - Clarify that when autoconf is checking for nacl, it is checking
11273 specifically for nacl with a fast curve25519 implementation.
11275 - Warn if building on a platform with an unsigned time_t: there
11276 are too many places where Tor currently assumes that time_t can
11277 hold negative values. We'd like to fix them all, but probably
11280 o Minor bugfixes (build):
11281 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
11282 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
11283 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
11284 - Add the old src/or/micro-revision.i filename to CLEANFILES.
11285 On the off chance that somebody has one, it will go away as soon
11286 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
11287 - Build Tor correctly on 32-bit platforms where the compiler can build
11288 but not run code using the "uint128_t" construction. Fixes bug 8587;
11289 bugfix on 0.2.4.8-alpha.
11290 - Fix compilation warning with some versions of clang that would
11291 prefer the -Wswitch-enum compiler flag to warn about switch
11292 statements with missing enum values, even if those switch
11293 statements have a "default:" statement. Fixes bug 8598; bugfix
11296 o Minor bugfixes (protocol):
11297 - Fix the handling of a TRUNCATE cell when it arrives while the
11298 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
11299 - Fix a misframing issue when reading the version numbers in a
11300 VERSIONS cell. Previously we would recognize [00 01 00 02] as
11301 'version 1, version 2, and version 0x100', when it should have
11302 only included versions 1 and 2. Fixes bug 8059; bugfix on
11303 0.2.0.10-alpha. Reported pseudonymously.
11304 - Make the format and order of STREAM events for DNS lookups
11305 consistent among the various ways to launch DNS lookups. Fixes
11306 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
11307 - Correct our check for which versions of Tor support the EXTEND2
11308 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
11309 later, when support was really added in version 0.2.4.8-alpha.
11310 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
11312 o Minor bugfixes (other):
11313 - Correctly store microdescriptors and extrainfo descriptors with
11314 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
11315 Bug reported by "cypherpunks".
11316 - Increase the width of the field used to remember a connection's
11317 link protocol version to two bytes. Harmless for now, since the
11318 only currently recognized versions are one byte long. Reported
11319 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
11320 - If the state file's path bias counts are invalid (presumably from a
11321 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
11322 additional checks and log messages to the scaling of Path Bias
11323 counts, in case there still are remaining issues with scaling.
11324 Should help resolve bug 8235.
11325 - Eliminate several instances where we use "Nickname=ID" to refer to
11326 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
11327 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
11328 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
11330 o Minor bugfixes (syscalls):
11331 - Always check the return values of functions fcntl() and
11332 setsockopt(). We don't believe these are ever actually failing in
11333 practice, but better safe than sorry. Also, checking these return
11334 values should please analysis tools like Coverity. Patch from
11335 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
11336 - Use direct writes rather than stdio when building microdescriptor
11337 caches, in an attempt to mitigate bug 8031, or at least make it
11340 o Minor bugfixes (config):
11341 - When rejecting a configuration because we were unable to parse a
11342 quoted string, log an actual error message. Fixes bug 7950; bugfix
11344 - Behave correctly when the user disables LearnCircuitBuildTimeout
11345 but doesn't tell us what they would like the timeout to be. Fixes
11346 bug 6304; bugfix on 0.2.2.14-alpha.
11347 - When autodetecting the number of CPUs, use the number of available
11348 CPUs in preference to the number of configured CPUs. Inform the
11349 user if this reduces the number of available CPUs. Fixes bug 8002;
11350 bugfix on 0.2.3.1-alpha.
11351 - Make it an error when you set EntryNodes but disable UseGuardNodes,
11352 since it will (surprisingly to some users) ignore EntryNodes. Fixes
11353 bug 8180; bugfix on 0.2.3.11-alpha.
11354 - Allow TestingTorNetworks to override the 4096-byte minimum for
11355 the Fast threshold. Otherwise they can't bootstrap until they've
11356 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
11357 - Fix some logic errors when the user manually overrides the
11358 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
11361 o Minor bugfixes (log messages to help diagnose bugs):
11362 - If we fail to free a microdescriptor because of bug 7164, log
11363 the filename and line number from which we tried to free it.
11364 - Add another diagnostic to the heartbeat message: track and log
11365 overhead that TLS is adding to the data we write. If this is
11366 high, we are sending too little data to SSL_write at a time.
11367 Diagnostic for bug 7707.
11368 - Add more detail to a log message about relaxed timeouts, to help
11370 - Warn more aggressively when flushing microdescriptors to a
11371 microdescriptor cache fails, in an attempt to mitigate bug 8031,
11372 or at least make it more diagnosable.
11373 - Improve debugging output to help track down bug 8185 ("Bug:
11374 outgoing relay cell has n_chan==NULL. Dropping.")
11375 - Log the purpose of a path-bias testing circuit correctly.
11376 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
11378 o Minor bugfixes (0.2.4.x log messages that were too noisy):
11379 - Don't attempt to relax the timeout of already opened 1-hop circuits.
11380 They might never timeout. This should eliminate some/all cases of
11381 the relaxed timeout log message.
11382 - Use circuit creation time for network liveness evaluation. This
11383 should eliminate warning log messages about liveness caused
11384 by changes in timeout evaluation. Fixes bug 6572; bugfix on
11386 - Reduce a path bias length check from notice to info. The message
11387 is triggered when creating controller circuits. Fixes bug 8196;
11388 bugfix on 0.2.4.8-alpha.
11389 - Fix a path state issue that triggered a notice during relay startup.
11390 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
11391 - Reduce occurrences of warns about circuit purpose in
11392 connection_ap_expire_building(). Fixes bug 8477; bugfix on
11395 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
11396 - If we encounter a write failure on a SOCKS connection before we
11397 finish our SOCKS handshake, don't warn that we closed the
11398 connection before we could send a SOCKS reply. Fixes bug 8427;
11399 bugfix on 0.1.0.1-rc.
11400 - Correctly recognize that [::1] is a loopback address. Fixes
11401 bug 8377; bugfix on 0.2.1.3-alpha.
11402 - Fix a directory authority warn caused when we have a large amount
11403 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
11404 - Don't log inappropriate heartbeat messages when hibernating: a
11405 hibernating node is _expected_ to drop out of the consensus,
11406 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
11407 bugfix on 0.2.3.1-alpha.
11408 - Don't complain about bootstrapping problems while hibernating.
11409 These complaints reflect a general code problem, but not one
11410 with any problematic effects (no connections are actually
11411 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
11413 o Documentation fixes:
11414 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
11415 names match. Fixes bug 7768.
11416 - Make the torify manpage no longer refer to tsocks; torify hasn't
11417 supported tsocks since 0.2.3.14-alpha.
11418 - Make the tor manpage no longer reference tsocks.
11419 - Fix the GeoIPExcludeUnknown documentation to refer to
11420 ExcludeExitNodes rather than the currently nonexistent
11421 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
11424 - The tor-tsocks.conf is no longer distributed or installed. We
11425 recommend that tsocks users use torsocks instead. Resolves
11429 Changes in version 0.2.4.11-alpha - 2013-03-11
11430 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
11431 more robust, makes hidden service authentication work again, and
11432 resolves a DPI fingerprint for Tor's SSL transport.
11434 o Major features (directory authorities):
11435 - Directory authorities now support a new consensus method (17)
11436 where they cap the published bandwidth of servers for which
11437 insufficient bandwidth measurements exist. Fixes part of bug 2286.
11438 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
11439 serve any v2 directory information. Now we can test disabling the
11440 old deprecated v2 directory format, and see whether doing so has
11441 any effect on network load. Begins to fix bug 6783.
11442 - Directory authorities now include inside each vote a statement of
11443 the performance thresholds they used when assigning flags.
11444 Implements ticket 8151.
11446 o Major bugfixes (directory authorities):
11447 - Stop marking every relay as having been down for one hour every
11448 time we restart a directory authority. These artificial downtimes
11449 were messing with our Stable and Guard flag calculations. Fixes
11450 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
11452 o Major bugfixes (hidden services):
11453 - Allow hidden service authentication to succeed again. When we
11454 refactored the hidden service introduction code back
11455 in 0.2.4.1-alpha, we didn't update the code that checks
11456 whether authentication information is present, causing all
11457 authentication checks to return "false". Fix for bug 8207; bugfix
11458 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
11460 o Minor features (relays, bridges):
11461 - Make bridge relays check once a minute for whether their IP
11462 address has changed, rather than only every 15 minutes. Resolves
11463 bugs 1913 and 1992.
11464 - Refactor resolve_my_address() so it returns the method by which we
11465 decided our public IP address (explicitly configured, resolved from
11466 explicit hostname, guessed from interfaces, learned by gethostname).
11467 Now we can provide more helpful log messages when a relay guesses
11468 its IP address incorrectly (e.g. due to unexpected lines in
11469 /etc/hosts). Resolves ticket 2267.
11470 - Teach bridge-using clients to avoid 0.2.2 bridges when making
11471 microdescriptor-related dir requests, and only fall back to normal
11472 descriptors if none of their bridges can handle microdescriptors
11473 (as opposed to the fix in ticket 4013, which caused them to fall
11474 back to normal descriptors if *any* of their bridges preferred
11475 them). Resolves ticket 4994.
11476 - Randomize the lifetime of our SSL link certificate, so censors can't
11477 use the static value for filtering Tor flows. Resolves ticket 8443;
11478 related to ticket 4014 which was included in 0.2.2.33.
11479 - Support a new version of the link protocol that allows 4-byte circuit
11480 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
11481 a possible resource exhaustion issue. Closes ticket 7351; implements
11484 o Minor features (portability):
11485 - Tweak the curve25519-donna*.c implementations to tolerate systems
11486 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
11487 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
11488 the signs of types during autoconf. This is better than our old
11489 approach, which didn't work when cross-compiling.
11490 - Detect the sign of enum values, rather than assuming that MSC is the
11491 only compiler where enum types are all signed. Fixes bug 7727;
11492 bugfix on 0.2.4.10-alpha.
11494 o Minor features (other):
11495 - Say "KBytes" rather than "KB" in the man page (for various values
11496 of K), to further reduce confusion about whether Tor counts in
11497 units of memory or fractions of units of memory. Resolves ticket 7054.
11498 - Clear the high bit on curve25519 public keys before passing them to
11499 our backend, in case we ever wind up using a backend that doesn't do
11500 so itself. If we used such a backend, and *didn't* clear the high bit,
11501 we could wind up in a situation where users with such backends would
11502 be distinguishable from users without. Fixes bug 8121; bugfix on
11504 - Update to the March 6 2013 Maxmind GeoLite Country database.
11506 o Minor bugfixes (clients):
11507 - When we receive a RELAY_END cell with the reason DONE, or with no
11508 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
11509 status as "connection refused". Previously we reported these cases
11510 as success but then immediately closed the connection. Fixes bug
11511 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
11512 - Downgrade an assertion in connection_ap_expire_beginning to an
11513 LD_BUG message. The fix for bug 8024 should prevent this message
11514 from displaying, but just in case, a warn that we can diagnose
11515 is better than more assert crashes. Fixes bug 8065; bugfix on
11517 - Lower path use bias thresholds to .80 for notice and .60 for warn.
11518 Also make the rate limiting flags for the path use bias log messages
11519 independent from the original path bias flags. Fixes bug 8161;
11520 bugfix on 0.2.4.10-alpha.
11522 o Minor bugfixes (relays):
11523 - Stop trying to resolve our hostname so often (e.g. every time we
11524 think about doing a directory fetch). Now we reuse the cached
11525 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
11526 and 2410 (bugfix on 0.1.2.2-alpha).
11527 - Stop sending a stray "(null)" in some cases for the server status
11528 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
11530 - When choosing which stream on a formerly stalled circuit to wake
11531 first, make better use of the platform's weak RNG. Previously,
11532 we had been using the % ("modulo") operator to try to generate a
11533 1/N chance of picking each stream, but this behaves badly with
11534 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
11536 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
11537 Irix's random() only return 15 bits; Solaris's random() returns more
11538 bits but its RAND_MAX says it only returns 15, and so on. Motivated
11539 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
11541 o Minor bugfixes (directory authorities):
11542 - Directory authorities now use less space when formatting identical
11543 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
11546 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
11547 - Avoid leaking memory if we fail to compute a consensus signature
11548 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
11549 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
11551 - Fix a memory leak during safe-cookie controller authentication.
11552 Bugfix on 0.2.3.13-alpha.
11553 - Avoid memory leak of IPv6 policy content if we fail to format it into
11554 a router descriptor. Bugfix on 0.2.4.7-alpha.
11556 o Minor bugfixes (other code correctness issues):
11557 - Avoid a crash if we fail to generate an extrainfo descriptor.
11558 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
11559 this is CID 718634.
11560 - When detecting the largest possible file descriptor (in order to
11561 close all file descriptors when launching a new program), actually
11562 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
11563 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
11565 - Fix a copy-and-paste error when adding a missing A1 to a routerset
11566 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
11567 Bugfix on 0.2.4.10-alpha.
11568 - Fix an impossible-to-trigger integer overflow when estimating how
11569 long our onionskin queue would take. (This overflow would require us
11570 to accept 4 million onionskins before processing 100 of them.) Fixes
11571 bug 8210; bugfix on 0.2.4.10-alpha.
11573 o Code simplification and refactoring:
11574 - Add a wrapper function for the common "log a message with a
11578 Changes in version 0.2.4.10-alpha - 2013-02-04
11579 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
11580 certain attacks that flood the network with relays; changes the queue
11581 for circuit create requests from a sized-based limit to a time-based
11582 limit; resumes building with MSVC on Windows; and fixes a wide variety
11585 o Major bugfixes (directory authority):
11586 - When computing directory thresholds, ignore any rejected-as-sybil
11587 nodes during the computation so that they can't influence Fast,
11588 Guard, etc. (We should have done this for proposal 109.) Fixes
11590 - When marking a node as a likely sybil, reset its uptime metrics
11591 to zero, so that it cannot time towards getting marked as Guard,
11592 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
11596 - When a TLS write is partially successful but incomplete, remember
11597 that the flushed part has been flushed, and notice that bytes were
11598 actually written. Reported and fixed pseudonymously. Fixes bug
11599 7708; bugfix on Tor 0.1.0.5-rc.
11600 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
11601 ID: these could be used to create unexpected streams and circuits
11602 which would count as "present" to some parts of Tor but "absent"
11603 to others, leading to zombie circuits and streams or to a bandwidth
11604 denial-of-service. Fixes bug 7889; bugfix on every released version
11605 of Tor. Reported by "oftc_must_be_destroyed".
11606 - Rename all macros in our local copy of queue.h to begin with "TOR_".
11607 This change seems the only good way to permanently prevent conflicts
11608 with queue.h on various operating systems. Fixes bug 8107; bugfix
11611 o Major features (relay):
11612 - Instead of limiting the number of queued onionskins (aka circuit
11613 create requests) to a fixed, hard-to-configure number, we limit
11614 the size of the queue based on how many we expect to be able to
11615 process in a given amount of time. We estimate the time it will
11616 take to process an onionskin based on average processing time
11617 of previous onionskins. Closes ticket 7291. You'll never have to
11618 configure MaxOnionsPending again.
11620 o Major features (portability):
11621 - Resume building correctly with MSVC and Makefile.nmake. This patch
11622 resolves numerous bugs and fixes reported by ultramage, including
11623 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
11624 - Make the ntor and curve25519 code build correctly with MSVC.
11625 Fix on 0.2.4.8-alpha.
11628 - When directory authorities are computing thresholds for flags,
11629 never let the threshold for the Fast flag fall below 4096
11630 bytes. Also, do not consider nodes with extremely low bandwidths
11631 when deciding thresholds for various directory flags. This change
11632 should raise our threshold for Fast relays, possibly in turn
11633 improving overall network performance; see ticket 1854. Resolves
11635 - The Tor client now ignores sub-domain components of a .onion
11636 address. This change makes HTTP "virtual" hosting
11637 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
11638 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
11639 hosted on the same hidden service. Implements proposal 204.
11640 - We compute the overhead from passing onionskins back and forth to
11641 cpuworkers, and report it when dumping statistics in response to
11642 SIGUSR1. Supports ticket 7291.
11644 o Minor features (path selection):
11645 - When deciding whether we have enough descriptors to build circuits,
11646 instead of looking at raw relay counts, look at which fraction
11647 of (bandwidth-weighted) paths we're able to build. This approach
11648 keeps clients from building circuits if their paths are likely to
11649 stand out statistically. The default fraction of paths needed is
11650 taken from the consensus directory; you can override it with the
11651 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
11652 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
11653 and we have GeoIP information, also exclude all nodes with unknown
11654 countries "??" and "A1". This behavior is controlled by the
11655 new GeoIPExcludeUnknown option: you can make such nodes always
11656 excluded with "GeoIPExcludeUnknown 1", and disable the feature
11657 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
11658 gets you the default behavior. Implements feature 7706.
11659 - Path Use Bias: Perform separate accounting for successful circuit
11660 use. Keep separate statistics on stream attempt rates versus stream
11661 success rates for each guard. Provide configurable thresholds to
11662 determine when to emit log messages or disable use of guards that
11663 fail too many stream attempts. Resolves ticket 7802.
11665 o Minor features (log messages):
11666 - When learning a fingerprint for a bridge, log its corresponding
11667 transport type. Implements ticket 7896.
11668 - Improve the log message when "Bug/attack: unexpected sendme cell
11669 from client" occurs, to help us track bug 8093.
11672 - Remove a couple of extraneous semicolons that were upsetting the
11673 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
11674 bugfix on 0.2.2.1-alpha.
11675 - Remove a source of rounding error during path bias count scaling;
11676 don't count cannibalized circuits as used for path bias until we
11677 actually try to use them; and fix a circuit_package_relay_cell()
11678 warning message about n_chan==NULL. Fixes bug 7802.
11679 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
11680 actually link against nacl when we're configured to use it. Fixes
11681 bug 7972; bugfix on 0.2.4.8-alpha.
11682 - Compile correctly with the --disable-curve25519 option. Fixes
11683 bug 8153; bugfix on 0.2.4.8-alpha.
11685 o Build improvements:
11686 - Do not report status verbosely from autogen.sh unless the -v flag
11687 is specified. Fixes issue 4664. Patch from Onizuka.
11688 - Replace all calls to snprintf() outside of src/ext with
11689 tor_snprintf(). Also remove the #define to replace snprintf with
11690 _snprintf on Windows; they have different semantics, and all of
11691 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
11692 - Try to detect if we are ever building on a platform where
11693 memset(...,0,...) does not set the value of a double to 0.0. Such
11694 platforms are permitted by the C standard, though in practice
11695 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
11696 currently support them, but it's better to detect them and fail
11697 than to perform erroneously.
11699 o Removed features:
11700 - Stop exporting estimates of v2 and v3 directory traffic shares
11701 in extrainfo documents. They were unneeded and sometimes inaccurate.
11702 Also stop exporting any v2 directory request statistics. Resolves
11704 - Drop support for detecting and warning about versions of Libevent
11705 before 1.3e. Nothing reasonable ships with them any longer;
11706 warning the user about them shouldn't be needed. Resolves ticket
11709 o Code simplifications and refactoring:
11710 - Rename "isin" functions to "contains", for grammar. Resolves
11712 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
11713 with the natural logarithm function from the system libm. Resolves
11717 Changes in version 0.2.4.9-alpha - 2013-01-15
11718 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
11719 work more robustly.
11722 - Fix backward compatibility logic when receiving an embedded ntor
11723 handshake tunneled in a CREATE cell. This clears up the "Bug:
11724 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
11728 Changes in version 0.2.4.8-alpha - 2013-01-14
11729 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
11730 risks, adds a new stronger and faster circuit handshake, and offers
11731 stronger and faster link encryption when both sides support it.
11734 - Preliminary support for directory guards (proposal 207): when
11735 possible, clients now use their entry guards for non-anonymous
11736 directory requests. This can help prevent client enumeration. Note
11737 that this behavior only works when we have a usable consensus
11738 directory, and when options about what to download are more or less
11739 standard. In the future we should re-bootstrap from our guards,
11740 rather than re-bootstrapping from the preconfigured list of
11741 directory sources that ships with Tor. Resolves ticket 6526.
11742 - Tor relays and clients now support a better CREATE/EXTEND cell
11743 format, allowing the sender to specify multiple address, identity,
11744 and handshake types. Implements Robert Ransom's proposal 200;
11745 closes ticket 7199.
11747 o Major features (new circuit handshake):
11748 - Tor now supports a new circuit extension handshake designed by Ian
11749 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
11750 circuit extension handshake, later called "TAP", was a bit slow
11751 (especially on the relay side), had a fragile security proof, and
11752 used weaker keys than we'd now prefer. The new circuit handshake
11753 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
11754 function, making it significantly more secure than the older
11755 handshake, and significantly faster. Tor can use one of two built-in
11756 pure-C curve25519-donna implementations by Adam Langley, or it
11757 can link against the "nacl" library for a tuned version if present.
11759 The built-in version is very fast for 64-bit systems when building
11760 with GCC. The built-in 32-bit version is still faster than the
11761 old TAP protocol, but using libnacl is better on most such hosts.
11763 Clients don't currently use this protocol by default, since
11764 comparatively few clients support it so far. To try it, set
11765 UseNTorHandshake to 1.
11767 Implements proposal 216; closes ticket 7202.
11769 o Major features (better link encryption):
11770 - Relays can now enable the ECDHE TLS ciphersuites when available
11771 and appropriate. These ciphersuites let us negotiate forward-secure
11772 TLS secret keys more safely and more efficiently than with our
11773 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
11774 public relays prefer the (faster) P224 group, and bridges prefer
11775 the (more common) P256 group; you can override this with the
11778 Enabling these ciphers was a little tricky, since for a long time,
11779 clients had been claiming to support them without actually doing
11780 so, in order to foil fingerprinting. But with the client-side
11781 implementation of proposal 198 in 0.2.3.17-beta, clients can now
11782 match the ciphers from recent Firefox versions *and* list the
11783 ciphers they actually mean, so relays can believe such clients
11784 when they advertise ECDHE support in their TLS ClientHello messages.
11786 This feature requires clients running 0.2.3.17-beta or later,
11787 and requires both sides to be running OpenSSL 1.0.0 or later
11788 with ECC support. OpenSSL 1.0.1, with the compile-time option
11789 "enable-ec_nistp_64_gcc_128", is highly recommended.
11791 Implements the relay side of proposal 198; closes ticket 7200.
11794 - Avoid crashing when, as a relay without IPv6-exit support, a
11795 client insists on getting an IPv6 address or nothing. Fixes bug
11796 7814; bugfix on 0.2.4.7-alpha.
11799 - Improve circuit build timeout handling for hidden services.
11800 In particular: adjust build timeouts more accurately depending
11801 upon the number of hop-RTTs that a particular circuit type
11802 undergoes. Additionally, launch intro circuits in parallel
11803 if they timeout, and take the first one to reply as valid.
11804 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
11805 separate error codes; or at least, don't break for that reason.
11806 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
11807 - Update to the January 2 2013 Maxmind GeoLite Country database.
11809 o Minor features (testing):
11810 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
11811 (P-256) Diffie-Hellman handshakes to src/or/bench.
11812 - Add benchmark functions to test onion handshake performance.
11814 o Minor features (path bias detection):
11815 - Alter the Path Bias log messages to be more descriptive in terms
11816 of reporting timeouts and other statistics.
11817 - Create three levels of Path Bias log messages, as opposed to just
11818 two. These are configurable via consensus as well as via the torrc
11819 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
11820 The default values are 0.70, 0.50, and 0.30 respectively.
11821 - Separate the log message levels from the decision to drop guards,
11822 which also is available via torrc option PathBiasDropGuards.
11823 PathBiasDropGuards still defaults to 0 (off).
11824 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
11825 in combination with PathBiasExtremeRate.
11826 - Increase the default values for PathBiasScaleThreshold and
11827 PathBiasCircThreshold from (200, 20) to (300, 150).
11828 - Add in circuit usage accounting to path bias. If we try to use a
11829 built circuit but fail for any reason, it counts as path bias.
11830 Certain classes of circuits where the adversary gets to pick your
11831 destination node are exempt from this accounting. Usage accounting
11832 can be specifically disabled via consensus parameter or torrc.
11833 - Convert all internal path bias state to double-precision floating
11834 point, to avoid roundoff error and other issues.
11835 - Only record path bias information for circuits that have completed
11836 *two* hops. Assuming end-to-end tagging is the attack vector, this
11837 makes us more resilient to ambient circuit failure without any
11838 detection capability loss.
11840 o Minor bugfixes (log messages):
11841 - Rate-limit the "No circuits are opened. Relaxed timeout for a
11842 circuit with channel state open..." message to once per hour to
11843 keep it from filling the notice logs. Mitigates bug 7799 but does
11844 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
11845 - Avoid spurious warnings when configuring multiple client ports of
11846 which only some are nonlocal. Previously, we had claimed that some
11847 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
11850 o Code simplifications and refactoring:
11851 - Get rid of a couple of harmless clang warnings, where we compared
11852 enums to ints. These warnings are newly introduced in clang 3.2.
11853 - Split the onion.c file into separate modules for the onion queue
11854 and the different handshakes it supports.
11855 - Remove the marshalling/unmarshalling code for sending requests to
11856 cpuworkers over a socket, and instead just send structs. The
11857 recipient will always be the same Tor binary as the sender, so
11858 any encoding is overkill.
11861 Changes in version 0.2.4.7-alpha - 2012-12-24
11862 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
11863 directory mirrors for more robust bootstrapping; fixes more issues where
11864 clients with changing network conditions refuse to make any circuits;
11865 adds initial support for exiting to IPv6 addresses; resumes being able
11866 to update our GeoIP database, and includes the geoip6 file this time;
11867 turns off the client-side DNS cache by default due to privacy risks;
11868 and fixes a variety of other issues.
11870 o Major features (client resilience):
11871 - Add a new "FallbackDir" torrc option to use when we can't use
11872 a directory mirror from the consensus (either because we lack a
11873 consensus, or because they're all down). Currently, all authorities
11874 are fallbacks by default, and there are no other default fallbacks,
11875 but that will change. This option will allow us to give clients a
11876 longer list of servers to try to get a consensus from when first
11877 connecting to the Tor network, and thereby reduce load on the
11878 directory authorities. Implements proposal 206, "Preconfigured
11879 directory sources for bootstrapping". We also removed the old
11880 "FallbackNetworkstatus" option, since we never got it working well
11881 enough to use it. Closes bug 572.
11882 - If we have no circuits open, use a relaxed timeout (the
11883 95-percentile cutoff) until a circuit succeeds. This heuristic
11884 should allow Tor to succeed at building circuits even when the
11885 network connection drastically changes. Should help with bug 3443.
11887 o Major features (IPv6):
11888 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
11889 connectivity, then set the IPv6Exit flag to 1. Also make sure your
11890 exit policy reads as you would like: the address * applies to all
11891 address families, whereas *4 is IPv4 address only, and *6 is IPv6
11892 addresses only. On the client side, you'll need to wait until the
11893 authorities have upgraded, wait for enough exits to support IPv6,
11894 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
11895 ticket 5547, implements proposal 117 as revised in proposal 208.
11897 We DO NOT recommend that clients with actual anonymity needs start
11898 using IPv6 over Tor yet, since not enough exits support it yet.
11900 o Major features (geoip database):
11901 - Maxmind began labelling Tor relays as being in country "A1",
11902 which breaks by-country node selection inside Tor. Now we use a
11903 script to replace "A1" ("Anonymous Proxy") entries in our geoip
11904 file with real country codes. This script fixes about 90% of "A1"
11905 entries automatically and uses manual country code assignments to
11906 fix the remaining 10%. See src/config/README.geoip for details.
11907 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
11908 Country database, as modified above.
11910 o Major bugfixes (client-side DNS):
11911 - Turn off the client-side DNS cache by default. Updating and using
11912 the DNS cache is now configurable on a per-client-port
11913 level. SOCKSPort, DNSPort, etc lines may now contain
11914 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
11915 cache these types of DNS answers when we receive them from an
11916 exit node in response to an application request on this port, and
11917 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
11918 cached DNS answers of these types, we shouldn't use them. It's
11919 potentially risky to use cached DNS answers at the client, since
11920 doing so can indicate to one exit what answers we've gotten
11921 for DNS lookups in the past. With IPv6, this becomes especially
11922 problematic. Using cached DNS answers for requests on the same
11923 circuit would present less linkability risk, since all traffic
11924 on a circuit is already linkable, but it would also provide
11925 little performance benefit: the exit node caches DNS replies
11926 too. Implements a simplified version of Proposal 205. Implements
11929 o Major bugfixes (other):
11930 - Alter circuit build timeout measurement to start at the point
11931 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
11932 initialization). This should make our timeout measurements more
11933 uniform. Previously, we were sometimes including ORconn setup time
11934 in our circuit build time measurements. Should resolve bug 3443.
11935 - Fix an assertion that could trigger in hibernate_go_dormant() when
11936 closing an or_connection_t: call channel_mark_for_close() rather
11937 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
11939 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
11940 7655; bugfix on 0.2.4.6-alpha.
11943 - Add a new torrc option "ServerTransportListenAddr" to let bridge
11944 operators select the address where their pluggable transports will
11945 listen for connections. Resolves ticket 7013.
11946 - Allow an optional $ before the node identity digest in the
11947 controller command GETINFO ns/id/<identity>, for consistency with
11948 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
11949 - Log packaged cell fullness as part of the heartbeat message.
11950 Diagnosis to try to determine the extent of bug 7743.
11952 o Minor features (IPv6):
11953 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
11954 prefer to hand out virtual IPv6 addresses, since there are more of
11955 them and we can't run out. To override this behavior and make IPv4
11956 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
11957 or DNSPort you're using for resolving. Implements ticket 7571.
11958 - AutomapHostsOnResolve responses are now randomized, to avoid
11959 annoying situations where Tor is restarted and applications
11960 connect to the wrong addresses.
11961 - Never try more than 1000 times to pick a new virtual address when
11962 AutomapHostsOnResolve is set. That's good enough so long as we
11963 aren't close to handing out our entire virtual address space;
11964 if you're getting there, it's best to switch to IPv6 virtual
11968 - The ADDRMAP command can no longer generate an ill-formed error
11969 code on a failed MAPADDRESS. It now says "internal" rather than
11970 an English sentence fragment with spaces in the middle. Bugfix on
11971 Tor 0.2.0.19-alpha.
11972 - Fix log messages and comments to avoid saying "GMT" when we mean
11973 "UTC". Fixes bug 6113.
11974 - Compile on win64 using mingw64. Fixes bug 7260; patches from
11976 - Fix a crash when debugging unit tests on Windows: deallocate a
11977 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
11978 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
11981 - The DirServer option is now DirAuthority, for consistency with
11982 current naming patterns. You can still use the old DirServer form.
11984 o Code simplification and refactoring:
11985 - Move the client-side address-map/virtual-address/DNS-cache code
11986 out of connection_edge.c into a new addressmap.c module.
11987 - Remove unused code for parsing v1 directories and "running routers"
11988 documents. Fixes bug 6887.
11991 Changes in version 0.2.3.25 - 2012-11-19
11992 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
11993 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
11994 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
11995 programmer, and friend. Unstinting in his dedication to the cause of
11996 freedom, he inspired and helped many of us as we began our work on
11997 anonymity, and inspires us still. Please honor his memory by writing
11998 software to protect people's freedoms, and by helping others to do so.
12000 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
12001 significantly reduced directory overhead (via microdescriptors),
12002 enormous crypto performance improvements for fast relays on new
12003 enough hardware, a new v3 TLS handshake protocol that can better
12004 resist fingerprinting, support for protocol obfuscation plugins (aka
12005 pluggable transports), better scalability for hidden services, IPv6
12006 support for bridges, performance improvements like allowing clients
12007 to skip the first round-trip on the circuit ("optimistic data") and
12008 refilling token buckets more often, a new "stream isolation" design
12009 to isolate different applications on different circuits, and many
12010 stability, security, and privacy fixes.
12013 - Tor tries to wipe potentially sensitive data after using it, so
12014 that if some subsequent security failure exposes Tor's memory,
12015 the damage will be limited. But we had a bug where the compiler
12016 was eliminating these wipe operations when it decided that the
12017 memory was no longer visible to a (correctly running) program,
12018 hence defeating our attempt at defense in depth. We fix that
12019 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
12020 is unlikely to optimize away. Future versions of Tor may use
12021 a less ridiculously heavy approach for this. Fixes bug 7352.
12022 Reported in an article by Andrey Karpov.
12025 - Fix a harmless bug when opting against publishing a relay descriptor
12026 because DisableNetwork is set. Fixes bug 7464; bugfix on
12030 Changes in version 0.2.4.6-alpha - 2012-11-13
12031 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
12032 makes our defense-in-depth memory wiping more reliable, and begins to
12033 count IPv6 addresses in bridge statistics,
12036 - Fix an assertion failure that could occur when closing a connection
12037 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
12039 - Tor tries to wipe potentially sensitive data after using it, so
12040 that if some subsequent security failure exposes Tor's memory,
12041 the damage will be limited. But we had a bug where the compiler
12042 was eliminating these wipe operations when it decided that the
12043 memory was no longer visible to a (correctly running) program,
12044 hence defeating our attempt at defense in depth. We fix that
12045 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
12046 is unlikely to optimize away. Future versions of Tor may use
12047 a less ridiculously heavy approach for this. Fixes bug 7352.
12048 Reported in an article by Andrey Karpov.
12051 - Add GeoIP database for IPv6 addresses. The new config option
12053 - Bridge statistics now count bridge clients connecting over IPv6:
12054 bridge statistics files now list "bridge-ip-versions" and
12055 extra-info documents list "geoip6-db-digest". The control protocol
12056 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
12057 implementation by "shkoo", addressing ticket 5055.
12060 - Warn when we are binding low ports when hibernation is enabled;
12061 previously we had warned when we were _advertising_ low ports with
12062 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
12063 - Fix a harmless bug when opting against publishing a relay descriptor
12064 because DisableNetwork is set. Fixes bug 7464; bugfix on
12066 - Add warning message when a managed proxy dies during configuration.
12067 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
12068 - Fix a linking error when building tor-fw-helper without miniupnp.
12069 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
12070 - Check for closing an or_connection_t without going through correct
12071 channel functions; emit a warning and then call
12072 connection_or_close_for_error() so we don't assert as in bugs 7212
12074 - Compile correctly on compilers without C99 designated initializer
12075 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
12076 - Avoid a possible assert that can occur when channel_send_destroy() is
12077 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
12078 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
12079 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
12080 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
12081 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
12083 o Code simplification and refactoring:
12084 - Start using OpenBSD's implementation of queue.h, so that we don't
12085 need to hand-roll our own pointer and list structures whenever we
12086 need them. (We can't rely on a sys/queue.h, since some operating
12087 systems don't have them, and the ones that do have them don't all
12088 present the same extensions.)
12091 Changes in version 0.2.4.5-alpha - 2012-10-25
12092 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
12093 two important security vulnerabilities that could lead to remotely
12094 triggerable relay crashes, fix a major bug that was preventing clients
12095 from choosing suitable exit nodes, and refactor some of our code.
12097 o Major bugfixes (security, also in 0.2.3.24-rc):
12098 - Fix a group of remotely triggerable assertion failures related to
12099 incorrect link protocol negotiation. Found, diagnosed, and fixed
12100 by "some guy from France". Fix for CVE-2012-2250; bugfix on
12102 - Fix a denial of service attack by which any directory authority
12103 could crash all the others, or by which a single v2 directory
12104 authority could crash everybody downloading v2 directory
12105 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
12107 o Major bugfixes (also in 0.2.3.24-rc):
12108 - When parsing exit policy summaries from microdescriptors, we had
12109 previously been ignoring the last character in each one, so that
12110 "accept 80,443,8080" would be treated by clients as indicating
12111 a node that allows access to ports 80, 443, and 808. That would
12112 lead to clients attempting connections that could never work,
12113 and ignoring exit nodes that would support their connections. Now
12114 clients parse these exit policy summaries correctly. Fixes bug 7192;
12115 bugfix on 0.2.3.1-alpha.
12117 o Minor bugfixes (also in 0.2.3.24-rc):
12118 - Clients now consider the ClientRejectInternalAddresses config option
12119 when using a microdescriptor consensus stanza to decide whether
12120 an exit relay would allow exiting to an internal address. Fixes
12121 bug 7190; bugfix on 0.2.3.1-alpha.
12124 - Only disable TLS session ticket support when running as a TLS
12125 server. Now clients will blend better with regular Firefox
12126 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
12128 o Code simplification and refactoring:
12129 - Start using OpenBSD's implementation of queue.h (originally by
12131 - Move the entry node code from circuitbuild.c to its own file.
12132 - Move the circuit build timeout tracking code from circuitbuild.c
12136 Changes in version 0.2.3.24-rc - 2012-10-25
12137 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
12138 could lead to remotely triggerable relay crashes, and fixes
12139 a major bug that was preventing clients from choosing suitable exit
12142 o Major bugfixes (security):
12143 - Fix a group of remotely triggerable assertion failures related to
12144 incorrect link protocol negotiation. Found, diagnosed, and fixed
12145 by "some guy from France". Fix for CVE-2012-2250; bugfix on
12147 - Fix a denial of service attack by which any directory authority
12148 could crash all the others, or by which a single v2 directory
12149 authority could crash everybody downloading v2 directory
12150 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
12153 - When parsing exit policy summaries from microdescriptors, we had
12154 previously been ignoring the last character in each one, so that
12155 "accept 80,443,8080" would be treated by clients as indicating
12156 a node that allows access to ports 80, 443, and 808. That would
12157 lead to clients attempting connections that could never work,
12158 and ignoring exit nodes that would support their connections. Now
12159 clients parse these exit policy summaries correctly. Fixes bug 7192;
12160 bugfix on 0.2.3.1-alpha.
12163 - Clients now consider the ClientRejectInternalAddresses config option
12164 when using a microdescriptor consensus stanza to decide whether
12165 an exit relay would allow exiting to an internal address. Fixes
12166 bug 7190; bugfix on 0.2.3.1-alpha.
12169 Changes in version 0.2.4.4-alpha - 2012-10-20
12170 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
12171 vulnerability introduced by a change in OpenSSL, fixes a remotely
12172 triggerable assert, and adds new channel_t and circuitmux_t abstractions
12173 that will make it easier to test new connection transport and cell
12174 scheduling algorithms.
12176 o New directory authorities (also in 0.2.3.23-rc):
12177 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
12178 authority. Closes ticket 5749.
12180 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
12181 - Disable TLS session tickets. OpenSSL's implementation was giving
12182 our TLS session keys the lifetime of our TLS context objects, when
12183 perfect forward secrecy would want us to discard anything that
12184 could decrypt a link connection as soon as the link connection
12185 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
12186 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
12187 - Discard extraneous renegotiation attempts once the V3 link
12188 protocol has been initiated. Failure to do so left us open to
12189 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
12190 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
12192 o Internal abstraction features:
12193 - Introduce new channel_t abstraction between circuits and
12194 or_connection_t to allow for implementing alternate OR-to-OR
12195 transports. A channel_t is an abstract object which can either be a
12196 cell-bearing channel, which is responsible for authenticating and
12197 handshaking with the remote OR and transmitting cells to and from
12198 it, or a listening channel, which spawns new cell-bearing channels
12199 at the request of remote ORs. Implements part of ticket 6465.
12200 - Also new is the channel_tls_t subclass of channel_t, adapting it
12201 to the existing or_connection_t code. The V2/V3 protocol handshaking
12202 code which formerly resided in command.c has been moved below the
12203 channel_t abstraction layer and may be found in channeltls.c now.
12204 Implements the rest of ticket 6465.
12205 - Introduce new circuitmux_t storing the queue of circuits for
12206 a channel; this encapsulates and abstracts the queue logic and
12207 circuit selection policy, and allows the latter to be overridden
12208 easily by switching out a policy object. The existing EWMA behavior
12209 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
12211 o Required libraries:
12212 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
12213 strongly recommended.
12216 - Warn users who run hidden services on a Tor client with
12217 UseEntryGuards disabled that their hidden services will be
12218 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
12219 attack which motivated Tor to support entry guards in the first
12220 place). Resolves ticket 6889.
12221 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
12222 dhill. Resolves ticket 6982.
12223 - Option OutboundBindAddress can be specified multiple times and
12224 accepts IPv6 addresses. Resolves ticket 6876.
12226 o Minor bugfixes (also in 0.2.3.23-rc):
12227 - Don't serve or accept v2 hidden service descriptors over a
12228 relay's DirPort. It's never correct to do so, and disabling it
12229 might make it more annoying to exploit any bugs that turn up in the
12230 descriptor-parsing code. Fixes bug 7149.
12231 - Fix two cases in src/or/transports.c where we were calling
12232 fmt_addr() twice in a parameter list. Bug found by David
12233 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
12234 - Fix memory leaks whenever we logged any message about the "path
12235 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
12236 - When relays refuse a "create" cell because their queue of pending
12237 create cells is too big (typically because their cpu can't keep up
12238 with the arrival rate), send back reason "resource limit" rather
12239 than reason "internal", so network measurement scripts can get a
12240 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
12243 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
12244 - Free some more still-in-use memory at exit, to make hunting for
12245 memory leaks easier. Resolves bug 7029.
12246 - When a Tor client gets a "truncated" relay cell, the first byte of
12247 its payload specifies why the circuit was truncated. We were
12248 ignoring this 'reason' byte when tearing down the circuit, resulting
12249 in the controller not being told why the circuit closed. Now we
12250 pass the reason from the truncated cell to the controller. Bugfix
12251 on 0.1.2.3-alpha; fixes bug 7039.
12252 - Downgrade "Failed to hand off onionskin" messages to "debug"
12253 severity, since they're typically redundant with the "Your computer
12254 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
12255 - Make clients running with IPv6 bridges connect over IPv6 again,
12256 even without setting new config options ClientUseIPv6 and
12257 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
12258 - Use square brackets around IPv6 addresses in numerous places
12259 that needed them, including log messages, HTTPS CONNECT proxy
12260 requests, TransportProxy statefile entries, and pluggable transport
12261 extra-info lines. Fixes bug 7011; patch by David Fifield.
12263 o Code refactoring and cleanup:
12264 - Source files taken from other packages now reside in src/ext;
12265 previously they were scattered around the rest of Tor.
12266 - Avoid use of reserved identifiers in our C code. The C standard
12267 doesn't like us declaring anything that starts with an
12268 underscore, so let's knock it off before we get in trouble. Fix
12269 for bug 1031; bugfix on the first Tor commit.
12272 Changes in version 0.2.3.23-rc - 2012-10-20
12273 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
12274 vulnerability introduced by a change in OpenSSL, and fixes a variety
12275 of smaller bugs in preparation for the release.
12277 o New directory authorities:
12278 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
12279 authority. Closes ticket 5749.
12281 o Major bugfixes (security/privacy):
12282 - Disable TLS session tickets. OpenSSL's implementation was giving
12283 our TLS session keys the lifetime of our TLS context objects, when
12284 perfect forward secrecy would want us to discard anything that
12285 could decrypt a link connection as soon as the link connection
12286 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
12287 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
12288 - Discard extraneous renegotiation attempts once the V3 link
12289 protocol has been initiated. Failure to do so left us open to
12290 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
12291 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
12294 - Fix a possible crash bug when checking for deactivated circuits
12295 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
12296 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
12298 o Minor bugfixes (on 0.2.3.x):
12299 - Fix two cases in src/or/transports.c where we were calling
12300 fmt_addr() twice in a parameter list. Bug found by David
12301 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
12302 - Convert an assert in the pathbias code to a log message. The assert
12303 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
12304 bugfix on 0.2.3.17-beta.
12305 - Fix memory leaks whenever we logged any message about the "path
12306 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
12308 o Minor bugfixes (on 0.2.2.x and earlier):
12309 - Don't serve or accept v2 hidden service descriptors over a relay's
12310 DirPort. It's never correct to do so, and disabling it might
12311 make it more annoying to exploit any bugs that turn up in the
12312 descriptor-parsing code. Fixes bug 7149.
12313 - When relays refuse a "create" cell because their queue of pending
12314 create cells is too big (typically because their cpu can't keep up
12315 with the arrival rate), send back reason "resource limit" rather
12316 than reason "internal", so network measurement scripts can get a
12317 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
12318 - Correct file sizes when reading binary files on Cygwin, to avoid
12319 a bug where Tor would fail to read its state file. Fixes bug 6844;
12320 bugfix on 0.1.2.7-alpha.
12321 - Avoid undefined behavior when parsing the list of supported
12322 rendezvous/introduction protocols in a hidden service descriptor.
12323 Previously, Tor would have confused (as-yet-unused) protocol version
12324 numbers greater than 32 with lower ones on many platforms. Fixes
12325 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
12327 o Documentation fixes:
12328 - Clarify that hidden services are TCP only. Fixes bug 6024.
12331 Changes in version 0.2.4.3-alpha - 2012-09-22
12332 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
12333 assertion, resumes letting relays test reachability of their DirPort,
12334 and cleans up a bunch of smaller bugs.
12337 - Fix an assertion failure in tor_timegm() that could be triggered
12338 by a badly formatted directory object. Bug found by fuzzing with
12339 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12342 - Fix a possible crash bug when checking for deactivated circuits
12343 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
12344 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
12345 - Allow routers to detect that their own DirPorts are running. When
12346 we removed support for versions_supports_begindir, we also
12347 accidentally removed the mechanism we used to self-test our
12348 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
12349 bugfix on 0.2.4.2-alpha.
12351 o Security features:
12352 - Switch to a completely time-invariant approach for picking nodes
12353 weighted by bandwidth. Our old approach would run through the
12354 part of the loop after it had made its choice slightly slower
12355 than it ran through the part of the loop before it had made its
12356 choice. Addresses ticket 6538.
12357 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
12358 by tor2web clients allows hidden services to identify tor2web
12359 clients through their repeated selection of the same rendezvous
12360 and introduction point circuit endpoints (their guards). Resolves
12364 - Enable Tor to read configuration, state, and key information from
12365 a FIFO. Previously Tor would only read from files with a positive
12366 stat.st_size. Code from meejah; fixes bug 6044.
12369 - Correct file sizes when reading binary files on Cygwin, to avoid
12370 a bug where Tor would fail to read its state file. Fixes bug 6844;
12371 bugfix on 0.1.2.7-alpha.
12372 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
12373 bugfix on 0.2.0.3-alpha.
12374 - When complaining about a client port on a public address, log
12375 which address we're complaining about. Fixes bug 4020; bugfix on
12376 0.2.3.3-alpha. Patch by Tom Fitzhenry.
12377 - Convert an assert in the pathbias code to a log message. The assert
12378 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
12379 bugfix on 0.2.3.17-beta.
12380 - Our new buildsystem was overzealous about rebuilding manpages: it
12381 would rebuild them all whenever any one of them changed. Now our
12382 dependency checking should be correct. Fixes bug 6843; bugfix on
12384 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
12385 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
12386 - Correct log printout about which address family is preferred
12387 when connecting to a bridge with both an IPv4 and IPv6 OR port.
12388 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
12390 o Minor bugfixes (code cleanliness):
12391 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
12392 with large values. This situation was untriggered, but nevertheless
12393 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
12394 - Reject consensus votes with more than 64 known-flags. We aren't even
12395 close to that limit yet, and our code doesn't handle it correctly.
12396 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
12397 - Avoid undefined behavior when parsing the list of supported
12398 rendezvous/introduction protocols in a hidden service descriptor.
12399 Previously, Tor would have confused (as-yet-unused) protocol version
12400 numbers greater than 32 with lower ones on many platforms. Fixes
12401 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
12402 - Fix handling of rendezvous client authorization types over 8.
12403 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
12404 - Fix building with older versions of GCC (2.95, for one) that don't
12405 like preprocessor directives inside macro arguments. Found by
12406 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
12407 - Switch weighted node selection rule from using a list of doubles
12408 to using a list of int64_t. This change should make the process
12409 slightly easier to debug and maintain. Needed to finish ticket 6538.
12411 o Code simplification and refactoring:
12412 - Move the generic "config" code into a new file, and have "config.c"
12413 hold only torrc- and state-related code. Resolves ticket 6823.
12414 - Move the core of our "choose a weighted element at random" logic
12415 into its own function, and give it unit tests. Now the logic is
12416 testable, and a little less fragile too.
12417 - Removed the testing_since field of node_t, which hasn't been used
12418 for anything since 0.2.0.9-alpha.
12420 o Documentation fixes:
12421 - Clarify that hidden services are TCP only. Fixes bug 6024.
12422 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
12426 Changes in version 0.2.3.22-rc - 2012-09-11
12427 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
12431 - Fix an assertion failure in tor_timegm() that could be triggered
12432 by a badly formatted directory object. Bug found by fuzzing with
12433 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12436 - Avoid segfault when starting up having run with an extremely old
12437 version of Tor and parsing its state file. Fixes bug 6801; bugfix
12441 Changes in version 0.2.2.39 - 2012-09-11
12442 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
12446 - Fix an assertion failure in tor_timegm() that could be triggered
12447 by a badly formatted directory object. Bug found by fuzzing with
12448 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12449 - Do not crash when comparing an address with port value 0 to an
12450 address policy. This bug could have been used to cause a remote
12451 assertion failure by or against directory authorities, or to
12452 allow some applications to crash clients. Fixes bug 6690; bugfix
12456 Changes in version 0.2.4.2-alpha - 2012-09-10
12457 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
12458 raises the default rate limiting even more, and makes the bootstrapping
12459 log messages less noisy.
12462 - Automatically forward the TCP ports of pluggable transport
12463 proxies using tor-fw-helper if PortForwarding is enabled. Implements
12467 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
12468 to 1GB/1GB. The previous defaults were intended to be "basically
12469 infinite", but it turns out they're now limiting our 100mbit+
12470 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
12471 last time we raised it).
12474 - Detect when we're running with a version of OpenSSL other than the
12475 one we compiled with. This has occasionally given people hard-to-
12477 - Log fewer lines at level "notice" about our OpenSSL and Libevent
12478 versions and capabilities when everything is going right. Resolves
12479 part of ticket 6736.
12480 - Directory authorities no long accept descriptors for any version of
12481 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
12482 These versions are insecure, unsupported, or both. Implements
12486 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
12487 to start with a triple-underscore so the controller won't touch it.
12488 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
12489 - Avoid segfault when starting up having run with an extremely old
12490 version of Tor and parsing its state file. Fixes bug 6801; bugfix
12492 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
12493 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
12494 - Don't follow the NULL pointer if microdescriptor generation fails.
12495 (This does not appear to be triggerable, but it's best to be safe.)
12496 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
12497 - Fix mis-declared dependencies on src/common/crypto.c and
12498 src/or/tor_main.c that could break out-of-tree builds under some
12499 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
12500 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
12501 6778; bugfix on 0.2.4.1-alpha.
12502 - Fix a harmless (in this case) build warning for implicitly
12503 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
12505 o Removed features:
12506 - Now that all versions before 0.2.2.x are disallowed, we no longer
12507 need to work around their missing features. Thus we can remove a
12508 bunch of compatibility code.
12510 o Code refactoring:
12511 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
12512 TCP ports to forward. In the past it only accepted two ports:
12513 the ORPort and the DirPort.
12516 Changes in version 0.2.4.1-alpha - 2012-09-05
12517 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
12518 bridgedb; lets relays use IPv6 addresses and directory authorities
12519 advertise them; and switches to a cleaner build interface.
12521 This is the first alpha release in a new series, so expect there to
12522 be bugs. Users who would rather test out a more stable branch should
12523 stay with 0.2.3.x for now.
12525 o Major features (bridges):
12526 - Bridges now report the pluggable transports they support to the
12527 bridge authority, so it can pass the supported transports on to
12528 bridgedb and/or eventually do reachability testing. Implements
12531 o Major features (IPv6):
12532 - Bridge authorities now accept IPv6 bridge addresses and include
12533 them in network status documents. Implements ticket 5534.
12534 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
12535 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
12536 to happen. Implements ticket 5535.
12537 - All kind of relays, not just bridges, can now advertise an IPv6
12538 OR port. Implements ticket 6362.
12539 - Directory authorities vote on IPv6 OR ports using the new consensus
12540 method 14. Implements ticket 6363.
12542 o Major features (build):
12543 - Switch to a nonrecursive Makefile structure. Now instead of each
12544 Makefile.am invoking other Makefile.am's, there is a master
12545 Makefile.am that includes the others. This change makes our build
12546 process slightly more maintainable, and improves parallelism for
12547 building with make -j. Original patch by Stewart Smith; various
12548 fixes by Jim Meyering.
12549 - Where available, we now use automake's "silent" make rules by
12550 default, so that warnings are easier to spot. You can get the old
12551 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
12553 o Minor features (code security and spec conformance):
12554 - Clear keys and key-derived material left on the stack in
12555 rendservice.c and rendclient.c. Check return value of
12556 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
12557 These fixes should make us more forward-secure against cold-boot
12558 attacks and the like. Fixes bug 2385.
12559 - Reject EXTEND cells sent to nonexistent streams. According to the
12560 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
12561 we were only checking for stream IDs that were currently in use.
12562 Found while hunting for more instances of bug 6271. Bugfix on
12563 0.0.2pre8, which introduced incremental circuit construction.
12565 o Minor features (streamlining);
12566 - No longer include the "opt" prefix when generating routerinfos
12567 or v2 directories: it has been needless since Tor 0.1.2. Closes
12569 - Remove some now-needless code that tried to aggressively flush
12570 OR connections as data was added to them. Since 0.2.0.1-alpha, our
12571 cell queue logic has saved us from the failure mode that this code
12572 was supposed to prevent. Removing this code will limit the number
12573 of baroque control flow paths through Tor's network logic. Reported
12574 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
12576 o Minor features (controller):
12577 - Add a "GETINFO signal/names" control port command. Implements
12579 - Provide default values for all options via "GETINFO config/defaults".
12580 Implements ticket 4971.
12582 o Minor features (IPv6):
12583 - New config option "AuthDirHasIPv6Connectivity 1" that directory
12584 authorities should set if they have IPv6 connectivity and want to
12585 do reachability tests for IPv6 relays. Implements feature 5974.
12586 - A relay with an IPv6 OR port now sends that address in NETINFO
12587 cells (in addition to its other address). Implements ticket 6364.
12589 o Minor features (log messages):
12590 - Omit the first heartbeat log message, because it never has anything
12591 useful to say, and it clutters up the bootstrapping messages.
12592 Resolves ticket 6758.
12593 - Don't log about reloading the microdescriptor cache at startup. Our
12594 bootstrap warnings are supposed to tell the user when there's a
12595 problem, and our bootstrap notices say when there isn't. Resolves
12596 ticket 6759; bugfix on 0.2.2.6-alpha.
12597 - Don't log "I learned some more directory information" when we're
12598 reading cached directory information. Reserve it for when new
12599 directory information arrives in response to a fetch. Resolves
12601 - Prevent rounding error in path bias counts when scaling
12602 them down, and use the correct scale factor default. Also demote
12603 some path bias related log messages down a level and make others
12604 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
12605 - We no longer warn so much when generating manpages from their
12608 o Code simplifications and refactoring:
12609 - Enhance our internal sscanf replacement so that we can eliminate
12610 the last remaining uses of the system sscanf. (Though those uses
12611 of sscanf were safe, sscanf itself is generally error prone, so
12612 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
12614 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
12615 - Move last_reachable and testing_since from routerinfo_t to node_t.
12616 Implements ticket 5529.
12617 - Add replaycache_t structure, functions and unit tests, then refactor
12618 rend_service_introduce() to be more clear to read, improve, debug,
12619 and test. Resolves bug 6177.
12620 - Finally remove support for malloc_good_size and malloc_usable_size.
12621 We had hoped that these functions would let us eke a little more
12622 memory out of our malloc implementation. Unfortunately, the only
12623 implementations that provided these functions are also ones that
12624 are already efficient about not overallocation: they never got us
12625 more than 7 or so bytes per allocation. Removing them saves us a
12626 little code complexity and a nontrivial amount of build complexity.
12628 o New requirements:
12629 - Tor maintainers now require Automake version 1.9 or later to build
12630 Tor from the Git repository. (Automake is not required when building
12631 from a source distribution.)
12634 Changes in version 0.2.3.21-rc - 2012-09-05
12635 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
12636 series. It fixes a trio of potential security bugs, fixes a bug where
12637 we were leaving some of the fast relays out of the microdescriptor
12638 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
12639 and cleans up other smaller issues.
12641 o Major bugfixes (security):
12642 - Tear down the circuit if we get an unexpected SENDME cell. Clients
12643 could use this trick to make their circuits receive cells faster
12644 than our flow control would have allowed, or to gum up the network,
12645 or possibly to do targeted memory denial-of-service attacks on
12646 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
12647 from July 2002, before the release of Tor 0.0.0. We had committed
12648 this patch previously, but we had to revert it because of bug 6271.
12649 Now that 6271 is fixed, this patch appears to work.
12650 - Reject any attempt to extend to an internal address. Without
12651 this fix, a router could be used to probe addresses on an internal
12652 network to see whether they were accepting connections. Fixes bug
12653 6710; bugfix on 0.0.8pre1.
12654 - Do not crash when comparing an address with port value 0 to an
12655 address policy. This bug could have been used to cause a remote
12656 assertion failure by or against directory authorities, or to
12657 allow some applications to crash clients. Fixes bug 6690; bugfix
12661 - Remove the upper bound on microdescriptor length. We were hitting
12662 the limit for routers with complex exit policies or family
12663 declarations, causing clients to not use them. Fixes the first
12664 piece of bug 6404; fix on 0.2.2.6-alpha.
12665 - Detect "ORPort 0" as meaning, uniformly, that we're not running
12666 as a relay. Previously, some of our code would treat the presence
12667 of any ORPort line as meaning that we should act like a relay,
12668 even though our new listener code would correctly not open any
12669 ORPorts for ORPort 0. Similar bugs in other Port options are also
12670 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
12673 - Avoid a pair of double-free and use-after-mark bugs that can
12674 occur with certain timings in canceled and re-received DNS
12675 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
12676 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
12677 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
12678 - Allow one-hop directory fetching circuits the full "circuit build
12679 timeout" period, rather than just half of it, before failing them
12680 and marking the relay down. This fix should help reduce cases where
12681 clients declare relays (or worse, bridges) unreachable because
12682 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
12683 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
12685 - Authorities no longer include any router in their microdescriptor
12686 consensuses for which they couldn't generate or agree on a
12687 microdescriptor. Fixes the second piece of bug 6404; fix on
12689 - Detect and reject attempts to specify both "FooPort" and
12690 "FooPort 0" in the same configuration domain. (It's still okay
12691 to have a FooPort in your configuration file, and use "FooPort 0"
12692 on the command line to disable it.) Fixes the second half of bug
12693 6507; bugfix on 0.2.3.3-alpha.
12694 - Make wildcarded addresses (that is, ones beginning with "*.") work
12695 when provided via the controller's MapAddress command. Previously,
12696 they were accepted, but we never actually noticed that they were
12697 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
12698 - Avoid crashing on a malformed state file where EntryGuardPathBias
12699 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
12700 - Add a (probably redundant) memory clear between iterations of
12701 the router status voting loop, to prevent future coding errors
12702 where data might leak between iterations of the loop. Resolves
12705 o Minor bugfixes (log messages):
12706 - Downgrade "set buildtimeout to low value" messages to "info"
12707 severity; they were never an actual problem, there was never
12708 anything reasonable to do about them, and they tended to spam logs
12709 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
12710 - Downgrade path-bias warning messages to "info". We'll try to get
12711 them working better in 0.2.4. Add internal circuit construction
12712 state to protect against the noisy warn message "Unexpectedly high
12713 circuit_successes". Also add some additional rate-limited notice
12714 messages to help determine the root cause of the warn. Fixes bug
12715 6475. Bugfix against 0.2.3.17-beta.
12716 - Move log message when unable to find a microdesc in a routerstatus
12717 entry to parse time. Previously we'd spam this warning every time
12718 we tried to figure out which microdescriptors to download. Fixes
12719 the third piece of bug 6404; fix on 0.2.3.18-rc.
12722 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
12723 change when the authority is deciding whether to accept a newly
12724 uploaded descriptor. Implements ticket 6423.
12725 - Add missing documentation for consensus and microdesc files.
12726 Resolves ticket 6732.
12729 Changes in version 0.2.2.38 - 2012-08-12
12730 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
12731 attack that could in theory leak path information.
12734 - Avoid an uninitialized memory read when reading a vote or consensus
12735 document that has an unrecognized flavor name. This read could
12736 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12737 - Try to leak less information about what relays a client is
12738 choosing to a side-channel attacker. Previously, a Tor client would
12739 stop iterating through the list of available relays as soon as it
12740 had chosen one, thus finishing a little earlier when it picked
12741 a router earlier in the list. If an attacker can recover this
12742 timing information (nontrivial but not proven to be impossible),
12743 they could learn some coarse-grained information about which relays
12744 a client was picking (middle nodes in particular are likelier to
12745 be affected than exits). The timing attack might be mitigated by
12746 other factors (see bug 6537 for some discussion), but it's best
12747 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12750 Changes in version 0.2.3.20-rc - 2012-08-05
12751 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
12752 series. It fixes a pair of code security bugs and a potential anonymity
12753 issue, updates our RPM spec files, and cleans up other smaller issues.
12756 - Avoid read-from-freed-memory and double-free bugs that could occur
12757 when a DNS request fails while launching it. Fixes bug 6480;
12758 bugfix on 0.2.0.1-alpha.
12759 - Avoid an uninitialized memory read when reading a vote or consensus
12760 document that has an unrecognized flavor name. This read could
12761 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12762 - Try to leak less information about what relays a client is
12763 choosing to a side-channel attacker. Previously, a Tor client would
12764 stop iterating through the list of available relays as soon as it
12765 had chosen one, thus finishing a little earlier when it picked
12766 a router earlier in the list. If an attacker can recover this
12767 timing information (nontrivial but not proven to be impossible),
12768 they could learn some coarse-grained information about which relays
12769 a client was picking (middle nodes in particular are likelier to
12770 be affected than exits). The timing attack might be mitigated by
12771 other factors (see bug 6537 for some discussion), but it's best
12772 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12775 - Try to make the warning when giving an obsolete SOCKSListenAddress
12776 a little more useful.
12777 - Terminate active server managed proxies if Tor stops being a
12778 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
12779 - Provide a better error message about possible OSX Asciidoc failure
12780 reasons. Fixes bug 6436.
12781 - Warn when Tor is configured to use accounting in a way that can
12782 link a hidden service to some other hidden service or public
12783 address. Resolves ticket 6490.
12786 - Check return value of fputs() when writing authority certificate
12787 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
12788 - Ignore ServerTransportPlugin lines when Tor is not configured as
12789 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
12790 - When disabling guards for having too high a proportion of failed
12791 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
12795 - Update our default RPM spec files to work with mock and rpmbuild
12796 on RHEL/Fedora. They have an updated set of dependencies and
12797 conflicts, a fix for an ancient typo when creating the "_tor"
12798 user, and better instructions. Thanks to Ondrej Mikle for the
12799 patch series. Fixes bug 6043.
12802 - Make it possible to set the TestingTorNetwork configuration
12803 option using AlternateDirAuthority and AlternateBridgeAuthority
12804 as an alternative to setting DirServer. Addresses ticket 6377.
12807 - Clarify the documentation for the Alternate*Authority options.
12809 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
12811 o Code simplification and refactoring:
12812 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
12813 10 lines. Also, don't nest them. Doing so in the past has
12814 led to hard-to-debug code. The new style is to use the
12815 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
12818 Changes in version 0.2.3.19-rc - 2012-07-06
12819 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
12820 series. It fixes the compile on Windows, reverts to a GeoIP database
12821 that isn't as broken, and fixes a flow control bug that has been around
12822 since the beginning of Tor.
12825 - Fix a bug handling SENDME cells on nonexistent streams that could
12826 result in bizarre window values. Report and patch contributed
12827 pseudonymously. Fixes part of bug 6271. This bug was introduced
12828 before the first Tor release, in svn commit r152.
12829 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
12830 June 2012 database, Maxmind marked many Tor relays as country "A1",
12831 which will cause risky behavior for clients that set EntryNodes
12832 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
12833 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
12834 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
12837 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
12838 bugfix on 0.2.1.10-alpha.
12841 Changes in version 0.2.3.18-rc - 2012-06-28
12842 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
12843 series. It fixes a few smaller bugs, but generally appears stable.
12844 Please test it and let us know whether it is!
12847 - Allow wildcarded mapaddress targets to be specified on the
12848 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
12849 - Make our linker option detection code more robust against linkers
12850 such as on FreeBSD 8, where a bad combination of options completes
12851 successfully but makes an unrunnable binary. Fixes bug 6173;
12852 bugfix on 0.2.3.17-beta.
12854 o Minor bugfixes (on 0.2.2.x and earlier):
12855 - Avoid a false positive in the util/threads unit test by increasing
12856 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
12857 - Replace "Sending publish request" log messages with "Launching
12858 upload", so that they no longer confusingly imply that we're
12859 sending something to a directory we might not even be connected
12860 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
12861 - Make sure to set *socket_error in all error cases in
12862 connection_connect(), so it can't produce a warning about
12863 errno being zero from errno_to_orconn_end_reason(). Bugfix on
12864 0.2.1.1-alpha; resolves ticket 6028.
12865 - Downgrade "Got a certificate, but we already have it" log messages
12866 from warning to info, except when we're a dirauth. Fixes bug 5238;
12867 bugfix on 0.2.1.7-alpha.
12868 - When checking for requested signatures on the latest consensus
12869 before serving it to a client, make sure to check the right
12870 consensus flavor. Bugfix on 0.2.2.6-alpha.
12871 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
12872 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
12874 o Minor bugfixes (on 0.2.3.x):
12875 - Make format_helper_exit_status() avoid unnecessary space padding
12876 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
12878 - Downgrade a message about cleaning the microdescriptor cache to
12879 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
12880 - Log a BUG message at severity INFO if we have a networkstatus with
12881 a missing entry for some microdescriptor. Continues on a patch
12883 - Improve the log message when a managed proxy fails to launch. Fixes
12884 bug 5099; bugfix on 0.2.3.6-alpha.
12885 - Don't do DNS lookups when parsing corrupted managed proxy protocol
12886 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
12887 - When formatting wildcarded address mappings for the controller,
12888 be sure to include "*." as appropriate. Partially fixes bug 6244;
12889 bugfix on 0.2.3.9-alpha.
12890 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
12891 Bugfix on 0.2.3.13-alpha.
12892 - Stop logging messages about running with circuit timeout learning
12893 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
12894 - Disable a spurious warning about reading on a marked and flushing
12895 connection. We shouldn't be doing that, but apparently we
12896 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
12897 - Fix a bug that stopped AllowDotExit from working on addresses
12898 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
12901 o Code simplification, refactoring, unit tests:
12902 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
12903 Libevent's notion of cached time when possible.
12904 - Remove duplicate code for invoking getrlimit() from control.c.
12905 - Add a unit test for the environment_variable_names_equal function.
12908 - Document the --defaults-torrc option, and the new (in 0.2.3)
12909 semantics for overriding, extending, and clearing lists of
12910 options. Closes bug 4748.
12913 Changes in version 0.2.3.17-beta - 2012-06-15
12914 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
12915 gets our TLS handshake back on track for being able to blend in with
12916 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
12917 with Vidalia, and otherwise continues to get us closer to a release
12921 - Enable gcc and ld hardening by default. Resolves ticket 5210.
12922 - Update TLS cipher list to match Firefox 8 and later. Resolves
12924 - Implement the client side of proposal 198: remove support for
12925 clients falsely claiming to support standard ciphersuites that
12926 they can actually provide. As of modern OpenSSL versions, it's not
12927 necessary to fake any standard ciphersuite, and doing so prevents
12928 us from using better ciphersuites in the future, since servers
12929 can't know whether an advertised ciphersuite is really supported or
12930 not. Some hosts -- notably, ones with very old versions of OpenSSL
12931 or where OpenSSL has been built with ECC disabled -- will stand
12932 out because of this change; TBB users should not be affected.
12935 - Change the default value for DynamicDHGroups (introduced in
12936 0.2.3.9-alpha) to 0. This feature can make Tor relays less
12937 identifiable by their use of the mod_ssl DH group, but at
12938 the cost of some usability (#4721) and bridge tracing (#6087)
12939 regressions. Resolves ticket 5598.
12940 - Send a CRLF at the end of each STATUS_* control protocol event. This
12941 bug tickled a bug in Vidalia which would make it freeze. Fixes
12942 bug 6094; bugfix on 0.2.3.16-alpha.
12945 - Disable writing on marked-for-close connections when they are
12946 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
12947 bug 5263; bugfix on 0.0.2pre13, where we first added a special
12948 case for flushing marked connections.
12949 - Detect SSL handshake even when the initial attempt to write the
12950 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
12951 - Change the AllowDotExit rules so they should actually work.
12952 We now enforce AllowDotExit only immediately after receiving an
12953 address via SOCKS or DNSPort: other sources are free to provide
12954 .exit addresses after the resolution occurs. Fixes bug 3940;
12955 bugfix on 0.2.2.1-alpha.
12956 - Fix a (harmless) integer overflow in cell statistics reported by
12957 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
12958 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
12959 right places and never depends on the consensus parameters or
12960 computes adaptive timeouts when it is disabled. Fixes bug 5049;
12961 bugfix on 0.2.2.14-alpha.
12962 - When building Tor on Windows with -DUNICODE (not default), ensure
12963 that error messages, filenames, and DNS server names are always
12964 NUL-terminated when we convert them to a single-byte encoding.
12965 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
12966 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
12967 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
12968 - Fix an edge case where TestingTorNetwork is set but the authorities
12969 and relays all have an uptime of zero, where the private Tor network
12970 could briefly lack support for hidden services. Fixes bug 3886;
12971 bugfix on 0.2.2.18-alpha.
12972 - Correct the manpage's descriptions for the default values of
12973 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
12975 - Fix the documentation for the --hush and --quiet command line
12976 options, which changed their behavior back in 0.2.3.3-alpha.
12977 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
12981 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
12982 more information to it, so that we can track it down in case it
12983 returns again. Mitigates bug 5235.
12984 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
12985 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
12986 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
12987 - Warn the user when HTTPProxy, but no other proxy type, is
12988 configured. This can cause surprising behavior: it doesn't send
12989 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
12990 directory traffic only. Resolves ticket 4663.
12991 - Issue a notice if a guard completes less than 40% of your circuits.
12992 Threshold is configurable by torrc option PathBiasNoticeRate and
12993 consensus parameter pb_noticepct. There is additional, off-by-
12994 default code to disable guards which fail too many circuits.
12995 Addresses ticket 5458.
12996 - Update to the June 6 2012 Maxmind GeoLite Country database.
12998 o Code simplifications and refactoring:
12999 - Remove validate_pluggable_transports_config(): its warning
13000 message is now handled by connection_or_connect().
13003 Changes in version 0.2.2.37 - 2012-06-06
13004 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
13005 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
13009 - Work around a bug in OpenSSL that broke renegotiation with TLS
13010 1.1 and TLS 1.2. Without this workaround, all attempts to speak
13011 the v2 Tor connection protocol when both sides were using OpenSSL
13012 1.0.1 would fail. Resolves ticket 6033.
13013 - When waiting for a client to renegotiate, don't allow it to add
13014 any bytes to the input buffer. This fixes a potential DoS issue.
13015 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
13016 - Fix an edge case where if we fetch or publish a hidden service
13017 descriptor, we might build a 4-hop circuit and then use that circuit
13018 for exiting afterwards -- even if the new last hop doesn't obey our
13019 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
13022 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
13023 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
13026 - Tell GCC and Clang to check for any errors in format strings passed
13027 to the tor_v*(print|scan)f functions.
13030 Changes in version 0.2.3.16-alpha - 2012-06-05
13031 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
13032 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
13033 currently). It also fixes a variety of smaller bugs and other cleanups
13034 that get us closer to a release candidate.
13036 o Major bugfixes (general):
13037 - Work around a bug in OpenSSL that broke renegotiation with TLS
13038 1.1 and TLS 1.2. Without this workaround, all attempts to speak
13039 the v2 Tor connection protocol when both sides were using OpenSSL
13040 1.0.1 would fail. Resolves ticket 6033.
13041 - When waiting for a client to renegotiate, don't allow it to add
13042 any bytes to the input buffer. This fixes a potential DoS issue.
13043 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
13044 - Pass correct OR address to managed proxies (like obfsproxy),
13045 even when ORListenAddress is used. Fixes bug 4865; bugfix on
13047 - The advertised platform of a router now includes only its operating
13048 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
13049 service pack level (for Windows) or its CPU architecture (for Unix).
13050 We also no longer include the "git-XYZ" tag in the version. Resolves
13053 o Major bugfixes (clients):
13054 - If we are unable to find any exit that supports our predicted ports,
13055 stop calling them predicted, so that we don't loop and build
13056 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
13057 which introduced predicted ports.
13058 - Fix an edge case where if we fetch or publish a hidden service
13059 descriptor, we might build a 4-hop circuit and then use that circuit
13060 for exiting afterwards -- even if the new last hop doesn't obey our
13061 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
13062 - Check at each new consensus whether our entry guards were picked
13063 long enough ago that we should rotate them. Previously, we only
13064 did this check at startup, which could lead to us holding a guard
13065 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
13066 - When fetching a bridge descriptor from a bridge authority,
13067 always do so anonymously, whether we have been able to open
13068 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
13069 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
13070 but we'll need to wait for bug 6010 before it's actually usable.
13072 o Major bugfixes (directory authorities):
13073 - When computing weight parameters, behave more robustly in the
13074 presence of a bad bwweightscale value. Previously, the authorities
13075 would crash if they agreed on a sufficiently broken weight_scale
13076 value: now, they use a reasonable default and carry on. Partial
13077 fix for 5786; bugfix on 0.2.2.17-alpha.
13078 - Check more thoroughly to prevent a rogue authority from
13079 double-voting on any consensus directory parameter. Previously,
13080 authorities would crash in this case if the total number of
13081 votes for any parameter exceeded the number of active voters,
13082 but would let it pass otherwise. Partial fix for bug 5786; bugfix
13086 - Rate-limit log messages when asked to connect anonymously to
13087 a private address. When these hit, they tended to hit fast and
13088 often. Also, don't bother trying to connect to addresses that we
13089 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
13090 reply makes us think we have been lied to, even when the address the
13091 client tried to connect to was "localhost." Resolves ticket 2822.
13092 - Allow packagers to insert an extra string in server descriptor
13093 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
13094 Resolves the rest of ticket 2988.
13095 - Raise the threshold of server descriptors needed (75%) and exit
13096 server descriptors needed (50%) before we will declare ourselves
13097 bootstrapped. This will make clients start building circuits a
13098 little later, but makes the initially constructed circuits less
13099 skewed and less in conflict with further directory fetches. Fixes
13101 - Close any connection that sends unrecognized junk before the
13102 handshake. Solves an issue noted in bug 4369.
13103 - Improve log messages about managed transports. Resolves ticket 5070.
13104 - Tag a bridge's descriptor as "never to be sent unencrypted".
13105 This shouldn't matter, since bridges don't open non-anonymous
13106 connections to the bridge authority and don't allow unencrypted
13107 directory connections from clients, but we might as well make
13108 sure. Closes bug 5139.
13109 - Expose our view of whether we have gone dormant to the controller,
13110 via a new "GETINFO dormant" value. Torbutton and other controllers
13111 can use this to avoid doing periodic requests through Tor while
13112 it's dormant (bug 4718). Fixes bug 5954.
13113 - Tell GCC and Clang to check for any errors in format strings passed
13114 to the tor_v*(print|scan)f functions.
13115 - Update to the May 1 2012 Maxmind GeoLite Country database.
13117 o Minor bugfixes (already included in 0.2.2.36):
13118 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
13119 Fixes bug 5346; bugfix on 0.0.8pre3.
13120 - Correct parsing of certain date types in parse_http_time().
13121 Without this patch, If-Modified-Since would behave
13122 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
13123 Esteban Manchado Velázques.
13124 - Make our number-parsing functions always treat too-large values
13125 as an error, even when those values exceed the width of the
13126 underlying type. Previously, if the caller provided these
13127 functions with minima or maxima set to the extreme values of the
13128 underlying integer type, these functions would return those
13129 values on overflow rather than treating overflow as an error.
13130 Fixes part of bug 5786; bugfix on 0.0.9.
13131 - If we hit the error case where routerlist_insert() replaces an
13132 existing (old) server descriptor, make sure to remove that
13133 server descriptor from the old_routers list. Fix related to bug
13134 1776. Bugfix on 0.2.2.18-alpha.
13135 - Clarify the behavior of MaxCircuitDirtiness with hidden service
13136 circuits. Fixes issue 5259.
13138 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
13139 - Prevent a null-pointer dereference when receiving a data cell
13140 for a nonexistent stream when the circuit in question has an
13141 empty deliver window. We don't believe this is triggerable,
13142 since we don't currently allow deliver windows to become empty,
13143 but the logic is tricky enough that it's better to make the code
13144 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
13145 - Fix a memory leak when trying to launch a DNS request when the
13146 network is disabled or the nameservers are unconfigurable. Fixes
13147 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
13148 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
13149 - Don't hold a Windows file handle open for every file mapping;
13150 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
13152 - Avoid O(n^2) performance characteristics when parsing a large
13153 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
13154 - Format more doubles with %f, not %lf. Patch from grarpamp to make
13155 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
13157 - Make our replacement implementation of strtok_r() compatible with
13158 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
13159 bugfix on 0.2.2.1-alpha.
13160 - Fix a NULL-pointer dereference on a badly formed
13161 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
13162 bugfix on 0.2.2.9-alpha.
13163 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
13164 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
13165 - Defensively refactor rend_mid_rendezvous() so that protocol
13166 violations and length checks happen in the beginning. Fixes
13168 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
13169 that IPv6 stuff will compile on MSVC, and compilation issues
13170 will be easier to track down. Fixes bug 5861.
13172 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
13173 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
13174 resource exhaustion, so that clients can adjust their load to
13175 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
13176 started using END_STREAM_REASON_RESOURCELIMIT.
13177 - Don't check for whether the address we're using for outbound
13178 connections has changed until after the outbound connection has
13179 completed. On Windows, getsockname() doesn't succeed until the
13180 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
13181 - If the configuration tries to set MyFamily on a bridge, refuse to
13182 do so, and warn about the security implications. Fixes bug 4657;
13183 bugfix on 0.2.0.3-alpha.
13184 - If the client fails to set a reasonable set of ciphersuites
13185 during its v2 handshake renegotiation, allow the renegotiation to
13186 continue nevertheless (i.e. send all the required certificates).
13187 Fixes bug 4591; bugfix on 0.2.0.20-rc.
13188 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
13189 option is set to 0 (which Vidalia version 0.2.16 now does when
13190 a SAVECONF attempt fails), perform other actions that SIGHUP
13191 usually causes (like reopening the logs). Fixes bug 5095; bugfix
13193 - If we fail to write a microdescriptor to the disk cache, do not
13194 continue replacing the old microdescriptor file. Fixes bug 2954;
13195 bugfix on 0.2.2.6-alpha.
13196 - Exit nodes don't need to fetch certificates for authorities that
13197 they don't recognize; only directory authorities, bridges,
13198 and caches need to do that. Fixes part of bug 2297; bugfix on
13200 - Correctly handle checking the permissions on the parent
13201 directory of a control socket in the root directory. Bug found
13202 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
13204 - When told to add a bridge with the same digest as a preexisting
13205 bridge but a different addr:port, change the addr:port as
13206 requested. Previously we would not notice the change. Fixes half
13207 of bug 5603; fix on 0.2.2.26-beta.
13208 - End AUTHCHALLENGE error messages (in the control protocol) with
13209 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
13211 o Minor bugfixes (on 0.2.3.x):
13212 - Turn an assertion (that the number of handshakes received as a
13213 server is not < 1) into a warning. Fixes bug 4873; bugfix on
13215 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
13216 we had reversed them when the answer was cached.) Fixes bug
13217 5723; bugfix on 0.2.3.1-alpha.
13218 - Work correctly on Linux systems with accept4 support advertised in
13219 their headers, but without accept4 support in the kernel. Fix
13220 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
13221 - When told to add a bridge with the same addr:port as a preexisting
13222 bridge but a different transport, change the transport as
13223 requested. Previously we would not notice the change. Fixes half
13224 of bug 5603; fix on 0.2.3.2-alpha.
13225 - Avoid a "double-reply" warning when replying to a SOCKS request
13226 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
13227 bugfix on 0.2.3.4-alpha.
13228 - Fix a bug where a bridge authority crashes if it has seen no
13229 directory requests when it's time to write statistics to disk.
13230 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
13232 - Don't try to open non-control listeners when DisableNetwork is set.
13233 Previously, we'd open all listeners, then immediately close them.
13234 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
13235 - Don't abort the managed proxy protocol if the managed proxy
13236 sends us an unrecognized line; ignore it instead. Fixes bug
13237 5910; bugfix on 0.2.3.9-alpha.
13238 - Fix a compile warning in crypto.c when compiling with clang 3.1.
13239 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
13240 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
13241 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
13242 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
13243 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
13244 - Resolve numerous small warnings and build issues with MSVC. Resolves
13247 o Documentation fixes:
13248 - Improve the manual's documentation for the NT Service command-line
13249 options. Addresses ticket 3964.
13250 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
13251 - Document the changes to the ORPort and DirPort options, and the
13252 fact that {OR/Dir}ListenAddress is now unnecessary (and
13253 therefore deprecated). Resolves ticket 5597.
13256 - Remove the torrc.bridge file: we don't use it for anything, and
13257 it had become badly desynchronized from torrc.sample. Resolves
13261 Changes in version 0.2.2.36 - 2012-05-24
13262 Tor 0.2.2.36 updates the addresses for two of the eight directory
13263 authorities, fixes some potential anonymity and security issues,
13264 and fixes several crash bugs.
13266 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
13267 known flaws, and nobody should be using them. You should upgrade. If
13268 you're using a Linux or BSD and its packages are obsolete, stop using
13269 those packages and upgrade anyway.
13271 o Directory authority changes:
13272 - Change IP address for maatuska (v3 directory authority).
13273 - Change IP address for ides (v3 directory authority), and rename
13277 - When building or running with any version of OpenSSL earlier
13278 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
13279 versions have a bug (CVE-2011-4576) in which their block cipher
13280 padding includes uninitialized data, potentially leaking sensitive
13281 information to any peer with whom they make a SSLv3 connection. Tor
13282 does not use SSL v3 by default, but a hostile client or server
13283 could force an SSLv3 connection in order to gain information that
13284 they shouldn't have been able to get. The best solution here is to
13285 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
13286 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
13287 to make sure that the bug can't happen.
13288 - Never use a bridge or a controller-supplied node as an exit, even
13289 if its exit policy allows it. Found by wanoskarnet. Fixes bug
13290 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
13291 and 0.2.0.3-alpha (for bridge-purpose descriptors).
13292 - Only build circuits if we have a sufficient threshold of the total
13293 descriptors that are marked in the consensus with the "Exit"
13294 flag. This mitigates an attack proposed by wanoskarnet, in which
13295 all of a client's bridges collude to restrict the exit nodes that
13296 the client knows about. Fixes bug 5343.
13297 - Provide controllers with a safer way to implement the cookie
13298 authentication mechanism. With the old method, if another locally
13299 running program could convince a controller that it was the Tor
13300 process, then that program could trick the controller into telling
13301 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
13302 authentication method uses a challenge-response approach to prevent
13303 this attack. Fixes bug 5185; implements proposal 193.
13306 - Avoid logging uninitialized data when unable to decode a hidden
13307 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
13308 - Avoid a client-side assertion failure when receiving an INTRODUCE2
13309 cell on a general purpose circuit. Fixes bug 5644; bugfix on
13311 - Fix builds when the path to sed, openssl, or sha1sum contains
13312 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
13314 - Correct our replacements for the timeradd() and timersub() functions
13315 on platforms that lack them (for example, Windows). The timersub()
13316 function is used when expiring circuits, while timeradd() is
13317 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
13318 bugfix on 0.2.2.24-alpha.
13319 - Fix the SOCKET_OK test that we use to tell when socket
13320 creation fails so that it works on Win64. Fixes part of bug 4533;
13321 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
13324 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
13325 Fixes bug 5346; bugfix on 0.0.8pre3.
13326 - Make our number-parsing functions always treat too-large values
13327 as an error, even when those values exceed the width of the
13328 underlying type. Previously, if the caller provided these
13329 functions with minima or maxima set to the extreme values of the
13330 underlying integer type, these functions would return those
13331 values on overflow rather than treating overflow as an error.
13332 Fixes part of bug 5786; bugfix on 0.0.9.
13333 - Older Linux kernels erroneously respond to strange nmap behavior
13334 by having accept() return successfully with a zero-length
13335 socket. When this happens, just close the connection. Previously,
13336 we would try harder to learn the remote address: but there was
13337 no such remote address to learn, and our method for trying to
13338 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
13339 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
13340 - Correct parsing of certain date types in parse_http_time().
13341 Without this patch, If-Modified-Since would behave
13342 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
13343 Esteban Manchado Velázques.
13344 - Change the BridgePassword feature (part of the "bridge community"
13345 design, which is not yet implemented) to use a time-independent
13346 comparison. The old behavior might have allowed an adversary
13347 to use timing to guess the BridgePassword value. Fixes bug 5543;
13348 bugfix on 0.2.0.14-alpha.
13349 - Detect and reject certain misformed escape sequences in
13350 configuration values. Previously, these values would cause us
13351 to crash if received in a torrc file or over an authenticated
13352 control port. Bug found by Esteban Manchado Velázquez, and
13353 independently by Robert Connolly from Matta Consulting who further
13354 noted that it allows a post-authentication heap overflow. Patch
13355 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
13356 bugfix on 0.2.0.16-alpha.
13357 - Fix a compile warning when using the --enable-openbsd-malloc
13358 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
13359 - During configure, detect when we're building with clang version
13360 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
13361 CFLAGS. clang doesn't support them yet.
13362 - When sending an HTTP/1.1 proxy request, include a Host header.
13363 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
13364 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
13365 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
13366 - If we hit the error case where routerlist_insert() replaces an
13367 existing (old) server descriptor, make sure to remove that
13368 server descriptor from the old_routers list. Fix related to bug
13369 1776. Bugfix on 0.2.2.18-alpha.
13371 o Minor bugfixes (documentation and log messages):
13372 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
13373 Fixes bug 4856; bugfix on Tor 0.0.6.
13374 - Update "ClientOnly" man page entry to explain that there isn't
13375 really any point to messing with it. Resolves ticket 5005.
13376 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
13377 directory authority option (introduced in Tor 0.2.2.34).
13378 - Downgrade the "We're missing a certificate" message from notice
13379 to info: people kept mistaking it for a real problem, whereas it
13380 is seldom the problem even when we are failing to bootstrap. Fixes
13381 bug 5067; bugfix on 0.2.0.10-alpha.
13382 - Correctly spell "connect" in a log message on failure to create a
13383 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
13384 - Clarify the behavior of MaxCircuitDirtiness with hidden service
13385 circuits. Fixes issue 5259.
13388 - Directory authorities now reject versions of Tor older than
13389 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
13390 inclusive. These versions accounted for only a small fraction of
13391 the Tor network, and have numerous known security issues. Resolves
13393 - Update to the May 1 2012 Maxmind GeoLite Country database.
13396 - When sending or relaying a RELAY_EARLY cell, we used to convert
13397 it to a RELAY cell if the connection was using the v1 link
13398 protocol. This was a workaround for older versions of Tor, which
13399 didn't handle RELAY_EARLY cells properly. Now that all supported
13400 versions can handle RELAY_EARLY cells, and now that we're enforcing
13401 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
13402 remove this workaround. Addresses bug 4786.
13405 Changes in version 0.2.3.15-alpha - 2012-04-30
13406 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
13407 the development branch build on Windows again.
13409 o Minor bugfixes (on 0.2.2.x and earlier):
13410 - Make sure that there are no unhandled pending TLS errors before
13411 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
13412 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
13413 Bugfix on 0.1.0.5-rc; fixes bug 4528.
13414 - Fix an assert that directory authorities could trigger on sighup
13415 during some configuration state transitions. We now don't treat
13416 it as a fatal error when the new descriptor we just generated in
13417 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
13418 - After we pick a directory mirror, we would refuse to use it if
13419 it's in our ExcludeExitNodes list, resulting in mysterious failures
13420 to bootstrap for people who just wanted to avoid exiting from
13421 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
13422 - When building with --enable-static-tor on OpenBSD, do not
13423 erroneously attempt to link -lrt. Fixes bug 5103.
13425 o Minor bugfixes (on 0.2.3.x):
13426 - When Tor is built with kernel headers from a recent (last few
13427 years) Linux kernel, do not fail to run on older (pre-2.6.28
13428 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
13429 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
13430 and 0.2.3.12-alpha.
13431 - Fix compilation with miniupnpc version 1.6; patch from
13432 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
13433 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
13434 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
13435 - Fix compilation on platforms without unistd.h, or where environ
13436 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
13439 - Directory authorities are now a little more lenient at accepting
13440 older router descriptors, or newer router descriptors that don't
13441 make big changes. This should help ameliorate past and future
13442 issues where routers think they have uploaded valid descriptors,
13443 but the authorities don't think so. Fix for ticket 2479.
13444 - Make the code that clients use to detect an address change be
13445 IPv6-aware, so that it won't fill clients' logs with error
13446 messages when trying to get the IPv4 address of an IPv6
13447 connection. Implements ticket 5537.
13449 o Removed features:
13450 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
13451 authorities needed to use it for a while to keep the network working
13452 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
13453 that was six months ago. As of now, it should no longer be needed
13457 Changes in version 0.2.3.14-alpha - 2012-04-23
13458 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
13459 candidate. It also dramatically speeds up AES: fast relays should
13460 consider switching to the newer OpenSSL library.
13462 o Directory authority changes:
13463 - Change IP address for ides (v3 directory authority), and rename
13467 - Avoid logging uninitialized data when unable to decode a hidden
13468 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
13469 - Avoid a client-side assertion failure when receiving an INTRODUCE2
13470 cell on a general purpose circuit. Fixes bug 5644; bugfix on
13472 - If authorities are unable to get a v2 consensus document from other
13473 directory authorities, they no longer fall back to fetching
13474 them from regular directory caches. Fixes bug 5635; bugfix on
13475 0.2.2.26-beta, where routers stopped downloading v2 consensus
13476 documents entirely.
13477 - When we start a Tor client with a normal consensus already cached,
13478 be willing to download a microdescriptor consensus. Fixes bug 4011;
13479 fix on 0.2.3.1-alpha.
13481 o Major features (performance):
13482 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
13483 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
13484 vectorized AES implementations as appropriate. These can be much,
13485 much faster than other AES implementations.
13487 o Minor bugfixes (0.2.2.x and earlier):
13488 - Don't launch more than 10 service-side introduction-point circuits
13489 for a hidden service in five minutes. Previously, we would consider
13490 launching more introduction-point circuits if at least one second
13491 had passed without any introduction-point circuits failing. Fixes
13492 bug 4607; bugfix on 0.0.7pre1.
13493 - Change the BridgePassword feature (part of the "bridge community"
13494 design, which is not yet implemented) to use a time-independent
13495 comparison. The old behavior might have allowed an adversary
13496 to use timing to guess the BridgePassword value. Fixes bug 5543;
13497 bugfix on 0.2.0.14-alpha.
13498 - Enforce correct return behavior of tor_vsscanf() when the '%%'
13499 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
13500 - When sending an HTTP/1.1 proxy request, include a Host header.
13501 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
13502 - Don't log that we have "decided to publish new relay descriptor"
13503 unless we are actually publishing a descriptor. Fixes bug 3942;
13504 bugfix on 0.2.2.28-beta.
13506 o Minor bugfixes (0.2.3.x):
13507 - Fix a bug where a bridge authority crashes (on a failed assert)
13508 if it has seen no directory requests when it's time to write
13509 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
13510 - Fix bug stomping on ORPort option NoListen and ignoring option
13511 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
13512 - In the testsuite, provide a large enough buffer in the tor_sscanf
13513 unit test. Otherwise we'd overrun that buffer and crash during
13514 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
13516 - Make sure we create the keys directory if it doesn't exist and we're
13517 about to store the dynamic Diffie-Hellman parameters. Fixes bug
13518 5572; bugfix on 0.2.3.13-alpha.
13519 - Fix a small memory leak when trying to decode incorrect base16
13520 authenticator during SAFECOOKIE authentication. Found by
13521 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
13524 - Add more information to a log statement that might help track down
13525 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
13526 non-IP address" messages (or any Bug messages, for that matter!),
13527 please let us know about it.
13528 - Relays now understand an IPv6 address when they get one from a
13529 directory server. Resolves ticket 4875.
13530 - Resolve IPv6 addresses in bridge and entry statistics to country
13531 code "??" which means we at least count them. Resolves ticket 5053;
13532 improves on 0.2.3.9-alpha.
13533 - Update to the April 3 2012 Maxmind GeoLite Country database.
13534 - Begin a doc/state-contents.txt file to explain the contents of
13535 the Tor state file. Fixes bug 2987.
13537 o Default torrc changes:
13538 - Stop listing "socksport 9050" in torrc.sample. We open a socks
13539 port on 9050 by default anyway, so this should not change anything
13541 - Stop mentioning the deprecated *ListenAddress options in
13542 torrc.sample. Fixes bug 5438.
13543 - Document unit of bandwidth related options in sample torrc.
13546 o Removed features:
13547 - The "torify" script no longer supports the "tsocks" socksifier
13548 tool, since tsocks doesn't support DNS and UDP right for Tor.
13549 Everyone should be using torsocks instead. Fixes bugs 3530 and
13550 5180. Based on a patch by "ugh".
13552 o Code refactoring:
13553 - Change the symmetric cipher interface so that creating and
13554 initializing a stream cipher are no longer separate functions.
13555 - Remove all internal support for unpadded RSA. We never used it, and
13556 it would be a bad idea to start.
13559 Changes in version 0.2.3.13-alpha - 2012-03-26
13560 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
13561 in managed pluggable transports, as well as providing other cleanups
13562 that get us closer to a release candidate.
13564 o Directory authority changes:
13565 - Change IP address for maatuska (v3 directory authority).
13568 - Provide controllers with a safer way to implement the cookie
13569 authentication mechanism. With the old method, if another locally
13570 running program could convince a controller that it was the Tor
13571 process, then that program could trick the controller into telling
13572 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
13573 authentication method uses a challenge-response approach to prevent
13574 this attack. Fixes bug 5185, implements proposal 193.
13575 - Never use a bridge or a controller-supplied node as an exit, even
13576 if its exit policy allows it. Found by wanoskarnet. Fixes bug
13577 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
13578 and 0.2.0.3-alpha (for bridge-purpose descriptors).
13579 - Only build circuits if we have a sufficient threshold of the total
13580 descriptors that are marked in the consensus with the "Exit"
13581 flag. This mitigates an attack proposed by wanoskarnet, in which
13582 all of a client's bridges collude to restrict the exit nodes that
13583 the client knows about. Fixes bug 5343.
13585 o Major bugfixes (on Tor 0.2.3.x):
13586 - Avoid an assert when managed proxies like obfsproxy are configured,
13587 and we receive HUP signals or setconf attempts too rapidly. This
13588 situation happens most commonly when Vidalia tries to attach to
13589 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
13590 bugfix on 0.2.3.6-alpha.
13591 - Fix a relay-side pluggable transports bug where managed proxies were
13592 unreachable from the Internet, because Tor asked them to bind on
13593 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
13594 - Stop discarding command-line arguments when TestingTorNetwork
13595 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
13596 0.2.3.9-alpha, where task 4552 added support for two layers of
13598 - Resume allowing the unit tests to run in gdb. This was accidentally
13599 made impossible when the DisableDebuggerAttachment option was
13600 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
13601 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
13602 0.2.3.11-alpha. Reported by Anthony G. Basile.
13604 o Minor bugfixes (on 0.2.2.x and earlier):
13605 - Ensure we don't cannibalize circuits that are longer than three hops
13606 already, so we don't end up making circuits with 5 or more
13607 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
13608 0.1.0.1-rc which introduced cannibalization.
13609 - Detect and reject certain misformed escape sequences in
13610 configuration values. Previously, these values would cause us
13611 to crash if received in a torrc file or over an authenticated
13612 control port. Bug found by Esteban Manchado Velázquez, and
13613 independently by Robert Connolly from Matta Consulting who further
13614 noted that it allows a post-authentication heap overflow. Patch
13615 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
13616 bugfix on 0.2.0.16-alpha.
13617 - Fix a compile warning when using the --enable-openbsd-malloc
13618 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
13619 - Directory caches no longer refuse to clean out descriptors because
13620 of missing v2 networkstatus documents, unless they're configured
13621 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
13622 0.2.2.26-beta. Patch by Daniel Bryg.
13623 - Update to the latest version of the tinytest unit testing framework.
13624 This includes a couple of bugfixes that can be relevant for
13625 running forked unit tests on Windows, and removes all reserved
13628 o Minor bugfixes (on 0.2.3.x):
13629 - On a failed pipe() call, don't leak file descriptors. Fixes bug
13630 4296; bugfix on 0.2.3.1-alpha.
13631 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
13632 until after we have received a CERTS cell. Fixes bug 4361; bugfix
13633 on 0.2.3.6-alpha. Patch by "frosty".
13634 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
13635 option, so that the IP stack doesn't decide to use it for IPv4
13636 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
13637 - Ensure that variables set in Tor's environment cannot override
13638 environment variables that Tor passes to a managed
13639 pluggable-transport proxy. Previously, Tor would pass every
13640 variable in its environment to managed proxies along with the new
13641 ones, in such a way that on many operating systems, the inherited
13642 environment variables would override those which Tor tried to
13643 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
13644 bugfix on 0.2.3.9-alpha for Windows.
13647 - A wide variety of new unit tests by Esteban Manchado Velázquez.
13648 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
13649 - Update to the March 6 2012 Maxmind GeoLite Country database.
13652 Changes in version 0.2.3.12-alpha - 2012-02-13
13653 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
13654 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
13655 when Tor is configured to use a pluggable transport like obfsproxy.
13658 - Fix builds when the path to sed, openssl, or sha1sum contains
13659 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
13661 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
13662 connections. This change should allow busy exit relays to stop
13663 running out of available sockets as quickly. Fixes bug 4950;
13664 bugfix on 0.2.2.26-beta.
13665 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
13666 would ask the bridge for microdescriptors, which are only supported
13667 in 0.2.3.x, and then fail to bootstrap when it didn't get the
13668 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
13669 - Properly set up obfsproxy's environment when in managed mode. The
13670 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
13671 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
13672 5076 and 5082; bugfix on 0.2.3.6-alpha.
13675 - Use the dead_strip option when building Tor on OS X. This reduces
13676 binary size by almost 19% when linking openssl and libevent
13677 statically, which we do for Tor Browser Bundle.
13678 - Fix broken URLs in the sample torrc file, and tell readers about
13679 the OutboundBindAddress, ExitPolicyRejectPrivate, and
13680 PublishServerDescriptor options. Addresses bug 4652.
13681 - Update to the February 7 2012 Maxmind GeoLite Country database.
13684 - Downgrade the "We're missing a certificate" message from notice
13685 to info: people kept mistaking it for a real problem, whereas it
13686 is seldom the problem even when we are failing to bootstrap. Fixes
13687 bug 5067; bugfix on 0.2.0.10-alpha.
13688 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
13689 managed pluggable transport server proxy's environment.
13690 Previously, we would put it there, even though Tor doesn't
13691 implement an 'extended server port' yet, and even though Tor
13692 almost certainly isn't listening at that address. For now, we set
13693 it to an empty string to avoid crashing older obfsproxies. Bugfix
13695 - Log the heartbeat message every HeartbeatPeriod seconds, not every
13696 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
13697 0.2.3.1-alpha. Bug reported by Scott Bennett.
13698 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
13699 bugfix on 0.2.3.11-alpha.
13700 - Update "ClientOnly" man page entry to explain that there isn't
13701 really any point to messing with it. Resolves ticket 5005.
13702 - Use the correct CVE number for CVE-2011-4576 in our comments and
13703 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
13706 o Code simplifications and refactoring:
13707 - Use the _WIN32 macro throughout our code to detect Windows.
13708 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
13712 Changes in version 0.2.3.11-alpha - 2012-01-22
13713 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
13714 the last step of the plan to limit maximum circuit length, includes
13715 a wide variety of hidden service performance and correctness fixes,
13716 works around an OpenSSL security flaw if your distro is too stubborn
13717 to upgrade, and fixes a bunch of smaller issues.
13720 - Now that Tor 0.2.0.x is completely deprecated, enable the final
13721 part of "Proposal 110: Avoiding infinite length circuits" by
13722 refusing all circuit-extend requests that do not use a relay_early
13723 cell. This change helps Tor resist a class of denial-of-service
13724 attacks by limiting the maximum circuit length.
13725 - Adjust the number of introduction points that a hidden service
13726 will try to maintain based on how long its introduction points
13727 remain in use and how many introductions they handle. Fixes
13729 - Try to use system facilities for enumerating local interface
13730 addresses, before falling back to our old approach (which was
13731 binding a UDP socket, and calling getsockname() on it). That
13732 approach was scaring OS X users whose draconian firewall
13733 software warned about binding to UDP sockets, regardless of
13734 whether packets were sent. Now we try to use getifaddrs(),
13735 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
13736 system supports. Resolves ticket 1827.
13738 o Major security workaround:
13739 - When building or running with any version of OpenSSL earlier
13740 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
13741 versions have a bug (CVE-2011-4576) in which their block cipher
13742 padding includes uninitialized data, potentially leaking sensitive
13743 information to any peer with whom they make a SSLv3 connection. Tor
13744 does not use SSL v3 by default, but a hostile client or server
13745 could force an SSLv3 connection in order to gain information that
13746 they shouldn't have been able to get. The best solution here is to
13747 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
13748 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
13749 to make sure that the bug can't happen.
13752 - Fix the SOCKET_OK test that we use to tell when socket
13753 creation fails so that it works on Win64. Fixes part of bug 4533;
13754 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
13755 - Correct our replacements for the timeradd() and timersub() functions
13756 on platforms that lack them (for example, Windows). The timersub()
13757 function is used when expiring circuits, while timeradd() is
13758 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
13759 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
13760 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
13761 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
13762 bug at runtime, not compile time, because some distributions hack
13763 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
13764 on 0.2.3.9-alpha. Found by Pascal.
13766 o Minor features (controller):
13767 - Use absolute path names when reporting the torrc filename in the
13768 control protocol, so a controller can more easily find the torrc
13769 file. Resolves bug 1101.
13770 - Extend the control protocol to report flags that control a circuit's
13771 path selection in CIRC events and in replies to 'GETINFO
13772 circuit-status'. Implements part of ticket 2411.
13773 - Extend the control protocol to report the hidden service address
13774 and current state of a hidden-service-related circuit in CIRC
13775 events and in replies to 'GETINFO circuit-status'. Implements part
13777 - When reporting the path to the cookie file to the controller,
13778 give an absolute path. Resolves ticket 4881.
13779 - Allow controllers to request an event notification whenever a
13780 circuit is cannibalized or its purpose is changed. Implements
13781 part of ticket 3457.
13782 - Include the creation time of a circuit in CIRC and CIRC2
13783 control-port events and the list produced by the 'GETINFO
13784 circuit-status' control-port command.
13786 o Minor features (directory authorities):
13787 - Directory authorities now reject versions of Tor older than
13788 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
13789 inclusive. These versions accounted for only a small fraction of
13790 the Tor network, and have numerous known security issues. Resolves
13792 - Authority operators can now vote for all relays in a given
13793 set of countries to be BadDir/BadExit/Invalid/Rejected.
13794 - Provide two consensus parameters (FastFlagMinThreshold and
13795 FastFlagMaxThreshold) to control the range of allowable bandwidths
13796 for the Fast directory flag. These allow authorities to run
13797 experiments on appropriate requirements for being a "Fast" node.
13798 The AuthDirFastGuarantee config value still applies. Implements
13800 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
13801 directory authority option (introduced in Tor 0.2.2.34).
13803 o Minor features (other):
13804 - Don't disable the DirPort when we cannot exceed our AccountingMax
13805 limit during this interval because the effective bandwidthrate is
13806 low enough. This is useful in a situation where AccountMax is only
13807 used as an additional safeguard or to provide statistics.
13808 - Prepend an informative header to generated dynamic_dh_params files.
13809 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
13810 EntryNodes will have no effect. Resolves issue 2571.
13811 - Log more useful messages when we fail to disable debugger
13813 - Log which authority we're missing votes from when we go to fetch
13814 them from the other auths.
13815 - Log (at debug level) whenever a circuit's purpose is changed.
13816 - Add missing documentation for the MaxClientCircuitsPending,
13817 UseMicrodescriptors, UserspaceIOCPBuffers, and
13818 _UseFilteringSSLBufferevents options, all introduced during
13819 the 0.2.3.x series.
13820 - Update to the January 3 2012 Maxmind GeoLite Country database.
13822 o Minor bugfixes (hidden services):
13823 - Don't close hidden service client circuits which have almost
13824 finished connecting to their destination when they reach
13825 the normal circuit-build timeout. Previously, we would close
13826 introduction circuits which are waiting for an acknowledgement
13827 from the introduction point, and rendezvous circuits which have
13828 been specified in an INTRODUCE1 cell sent to a hidden service,
13829 after the normal CBT. Now, we mark them as 'timed out', and launch
13830 another rendezvous attempt in parallel. This behavior change can
13831 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
13832 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
13833 - Don't close hidden-service-side rendezvous circuits when they
13834 reach the normal circuit-build timeout. This behavior change can
13835 be disabled using the new
13836 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
13837 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
13838 - Make sure we never mark the wrong rendezvous circuit as having
13839 had its introduction cell acknowleged by the introduction-point
13840 relay. Previously, when we received an INTRODUCE_ACK cell on a
13841 client-side hidden-service introduction circuit, we might have
13842 marked a rendezvous circuit other than the one we specified in
13843 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
13844 a warning message and interfered with the hidden service
13845 connection-establishment process. Fixes bug 4759; bugfix on
13846 0.2.3.3-alpha, when we added the stream-isolation feature which
13847 might cause Tor to open multiple rendezvous circuits for the same
13849 - Don't trigger an assertion failure when we mark a new client-side
13850 hidden-service introduction circuit for close during the process
13851 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
13854 o Minor bugfixes (log messages):
13855 - Correctly spell "connect" in a log message on failure to create a
13856 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
13858 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
13859 Fixes bug 4856; bugfix on Tor 0.0.6.
13860 - Fix the log message describing how we work around discovering
13861 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
13862 4837; bugfix on 0.2.2.9-alpha.
13863 - When logging about a disallowed .exit name, do not also call it
13864 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
13866 o Minor bugfixes (build fixes):
13867 - During configure, detect when we're building with clang version
13868 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
13869 CFLAGS. clang doesn't support them yet.
13870 - During configure, search for library containing cos function as
13871 libm lives in libcore on some platforms (BeOS/Haiku). Linking
13872 against libm was hard-coded before. Fixes the first part of bug
13873 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
13875 - Detect attempts to build Tor on (as yet hypothetical) versions
13876 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
13877 fix for bug 4533. Bugfix on 0.2.2.28-beta.
13878 - Preprocessor directives should not be put inside the arguments
13879 of a macro. This would break compilation with GCC releases prior
13880 to version 3.3. We would never recommend such an old GCC version,
13881 but it is apparently required for binary compatibility on some
13882 platforms (namely, certain builds of Haiku). Fixes the other part
13883 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
13886 o Minor bugfixes (other):
13887 - Older Linux kernels erroneously respond to strange nmap behavior
13888 by having accept() return successfully with a zero-length
13889 socket. When this happens, just close the connection. Previously,
13890 we would try harder to learn the remote address: but there was
13891 no such remote address to learn, and our method for trying to
13892 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
13893 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
13894 - Fix null-pointer access that could occur if TLS allocation failed.
13895 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
13896 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
13897 accidentally been reverted.
13898 - Fix our implementation of crypto_random_hostname() so it can't
13899 overflow on ridiculously large inputs. (No Tor version has ever
13900 provided this kind of bad inputs, but let's be correct in depth.)
13901 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
13902 - Find more places in the code that should have been testing for
13903 invalid sockets using the SOCKET_OK macro. Required for a fix
13904 for bug 4533. Bugfix on 0.2.2.28-beta.
13905 - Fix an assertion failure when, while running with bufferevents, a
13906 connection finishes connecting after it is marked for close, but
13907 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
13908 - test_util_spawn_background_ok() hardcoded the expected value
13909 for ENOENT to 2. This isn't portable as error numbers are
13910 platform specific, and particularly the hurd has ENOENT at
13911 0x40000002. Construct expected string at runtime, using the correct
13912 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
13913 - Reject attempts to disable DisableDebuggerAttachment while Tor is
13914 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
13915 - Use an appropriate-width type for sockets in tor-fw-helper on
13916 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
13919 - When sending or relaying a RELAY_EARLY cell, we used to convert
13920 it to a RELAY cell if the connection was using the v1 link
13921 protocol. This was a workaround for older versions of Tor, which
13922 didn't handle RELAY_EARLY cells properly. Now that all supported
13923 versions can handle RELAY_EARLY cells, and now that we're enforcing
13924 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
13925 remove this workaround. Addresses bug 4786.
13927 o Code simplifications and refactoring:
13928 - Use OpenSSL's built-in SSL_state_string_long() instead of our
13929 own homebrewed ssl_state_to_string() replacement. Patch from
13930 Emile Snyder. Fixes bug 4653.
13931 - Use macros to indicate OpenSSL versions, so we don't need to worry
13932 about accidental hexadecimal bit shifts.
13933 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
13935 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
13936 - Use the smartlist_add_asprintf() alias more consistently.
13937 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
13938 invalid value, rather than just -1.
13939 - Rename a handful of old identifiers, mostly related to crypto
13940 structures and crypto functions. By convention, our "create an
13941 object" functions are called "type_new()", our "free an object"
13942 functions are called "type_free()", and our types indicate that
13943 they are types only with a final "_t". But a handful of older
13944 types and functions broke these rules, with function names like
13945 "type_create" or "subsystem_op_type", or with type names like
13949 Changes in version 0.2.3.10-alpha - 2011-12-16
13950 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
13951 Tor's buffers code. Absolutely everybody should upgrade.
13953 The bug relied on an incorrect calculation when making data continuous
13954 in one of our IO buffers, if the first chunk of the buffer was
13955 misaligned by just the wrong amount. The miscalculation would allow an
13956 attacker to overflow a piece of heap-allocated memory. To mount this
13957 attack, the attacker would need to either open a SOCKS connection to
13958 Tor's SocksPort (usually restricted to localhost), or target a Tor
13959 instance configured to make its connections through a SOCKS proxy
13960 (which Tor does not do by default).
13962 Good security practice requires that all heap-overflow bugs should be
13963 presumed to be exploitable until proven otherwise, so we are treating
13964 this as a potential code execution attack. Please upgrade immediately!
13965 This bug does not affect bufferevents-based builds of Tor. Special
13966 thanks to "Vektor" for reporting this issue to us!
13968 This release also contains a few minor bugfixes for issues discovered
13972 - Fix a heap overflow bug that could occur when trying to pull
13973 data into the first chunk of a buffer, when that chunk had
13974 already had some data drained from it. Fixes CVE-2011-2778;
13975 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
13978 - If we can't attach streams to a rendezvous circuit when we
13979 finish connecting to a hidden service, clear the rendezvous
13980 circuit's stream-isolation state and try to attach streams
13981 again. Previously, we cleared rendezvous circuits' isolation
13982 state either too early (if they were freshly built) or not at all
13983 (if they had been built earlier and were cannibalized). Bugfix on
13984 0.2.3.3-alpha; fixes bug 4655.
13985 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
13986 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
13987 - Fix an assertion failure when a relay with accounting enabled
13988 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
13991 - Update to the December 6 2011 Maxmind GeoLite Country database.
13994 Changes in version 0.2.2.35 - 2011-12-16
13995 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
13996 buffers code. Absolutely everybody should upgrade.
13998 The bug relied on an incorrect calculation when making data continuous
13999 in one of our IO buffers, if the first chunk of the buffer was
14000 misaligned by just the wrong amount. The miscalculation would allow an
14001 attacker to overflow a piece of heap-allocated memory. To mount this
14002 attack, the attacker would need to either open a SOCKS connection to
14003 Tor's SocksPort (usually restricted to localhost), or target a Tor
14004 instance configured to make its connections through a SOCKS proxy
14005 (which Tor does not do by default).
14007 Good security practice requires that all heap-overflow bugs should be
14008 presumed to be exploitable until proven otherwise, so we are treating
14009 this as a potential code execution attack. Please upgrade immediately!
14010 This bug does not affect bufferevents-based builds of Tor. Special
14011 thanks to "Vektor" for reporting this issue to us!
14013 Tor 0.2.2.35 also fixes several bugs in previous versions, including
14014 crash bugs for unusual configurations, and a long-term bug that
14015 would prevent Tor from starting on Windows machines with draconian
14018 With this release, we remind everyone that 0.2.0.x has reached its
14019 formal end-of-life. Those Tor versions have many known flaws, and
14020 nobody should be using them. You should upgrade -- ideally to the
14021 0.2.2.x series. If you're using a Linux or BSD and its packages are
14022 obsolete, stop using those packages and upgrade anyway.
14024 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
14025 longer receive support after some time in early 2012.
14028 - Fix a heap overflow bug that could occur when trying to pull
14029 data into the first chunk of a buffer, when that chunk had
14030 already had some data drained from it. Fixes CVE-2011-2778;
14031 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
14032 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
14033 that it doesn't attempt to allocate a socketpair. This could cause
14034 some problems on Windows systems with overzealous firewalls. Fix for
14035 bug 4457; workaround for Libevent versions 2.0.1-alpha through
14037 - If we mark an OR connection for close based on a cell we process,
14038 don't process any further cells on it. We already avoid further
14039 reads on marked-for-close connections, but now we also discard the
14040 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
14041 which was the first version where we might mark a connection for
14042 close based on processing a cell on it.
14043 - Correctly sanity-check that we don't underflow on a memory
14044 allocation (and then assert) for hidden service introduction
14045 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14046 bugfix on 0.2.1.5-alpha.
14047 - Fix a memory leak when we check whether a hidden service
14048 descriptor has any usable introduction points left. Fixes bug
14049 4424. Bugfix on 0.2.2.25-alpha.
14050 - Don't crash when we're running as a relay and don't have a GeoIP
14051 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
14052 we've had in the 0.2.3.x branch already.
14053 - When running as a client, do not print a misleading (and plain
14054 wrong) log message that we're collecting "directory request"
14055 statistics: clients don't collect statistics. Also don't create a
14056 useless (because empty) stats file in the stats/ directory. Fixes
14057 bug 4353; bugfix on 0.2.2.34.
14060 - Detect failure to initialize Libevent. This fix provides better
14061 detection for future instances of bug 4457.
14062 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
14063 function. This was eating up hideously large amounts of time on some
14064 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
14065 - Resolve an integer overflow bug in smartlist_ensure_capacity().
14066 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
14068 - Don't warn about unused log_mutex in log.c when building with
14069 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
14070 0.1.0.6-rc which introduced --disable-threads.
14071 - When configuring, starting, or stopping an NT service, stop
14072 immediately after the service configuration attempt has succeeded
14073 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
14074 - When sending a NETINFO cell, include the original address
14075 received for the other side, not its canonical address. Found
14076 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
14077 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
14078 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
14079 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
14080 occurred when a client tried to fetch a descriptor for a bridge
14081 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
14082 - Backport fixes for a pair of compilation warnings on Windows.
14083 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
14084 - If we had ever tried to call tor_addr_to_str on an address of
14085 unknown type, we would have done a strdup on an uninitialized
14086 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
14087 Reported by "troll_un".
14088 - Correctly detect and handle transient lookup failures from
14089 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
14090 Reported by "troll_un".
14091 - Fix null-pointer access that could occur if TLS allocation failed.
14092 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
14093 - Use tor_socket_t type for listener argument to accept(). Fixes bug
14094 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
14097 - Add two new config options for directory authorities:
14098 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
14099 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
14100 that is always sufficient to satisfy the bandwidth requirement for
14101 the Guard flag. Now it will be easier for researchers to simulate
14102 Tor networks with different values. Resolves ticket 4484.
14103 - When Tor ignores a hidden service specified in its configuration,
14104 include the hidden service's directory in the warning message.
14105 Previously, we would only tell the user that some hidden service
14106 was ignored. Bugfix on 0.0.6; fixes bug 4426.
14107 - Update to the December 6 2011 Maxmind GeoLite Country database.
14109 o Packaging changes:
14110 - Make it easier to automate expert package builds on Windows,
14111 by removing an absolute path from makensis.exe command.
14114 Changes in version 0.2.1.32 - 2011-12-16
14115 Tor 0.2.1.32 backports important security and privacy fixes for
14116 oldstable. This release is intended only for package maintainers and
14117 others who cannot use the 0.2.2 stable series. All others should be
14118 using Tor 0.2.2.x or newer.
14120 The Tor 0.2.1.x series will reach formal end-of-life some time in
14121 early 2012; we will stop releasing patches for it then.
14123 o Major bugfixes (also included in 0.2.2.x):
14124 - Correctly sanity-check that we don't underflow on a memory
14125 allocation (and then assert) for hidden service introduction
14126 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14127 bugfix on 0.2.1.5-alpha.
14128 - Fix a heap overflow bug that could occur when trying to pull
14129 data into the first chunk of a buffer, when that chunk had
14130 already had some data drained from it. Fixes CVE-2011-2778;
14131 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
14134 - Update to the December 6 2011 Maxmind GeoLite Country database.
14137 Changes in version 0.2.3.9-alpha - 2011-12-08
14138 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
14139 a "DisableNetwork" security feature that bundles can use to avoid
14140 touching the network until bridges are configured, moves forward on
14141 the pluggable transport design, fixes a flaw in the hidden service
14142 design that unnecessarily prevented clients with wrong clocks from
14143 reaching hidden services, and fixes a wide variety of other issues.
14146 - Clients can now connect to private bridges over IPv6. Bridges
14147 still need at least one IPv4 address in order to connect to
14148 other relays. Note that we don't yet handle the case where the
14149 user has two bridge lines for the same bridge (one IPv4, one
14150 IPv6). Implements parts of proposal 186.
14151 - New "DisableNetwork" config option to prevent Tor from launching any
14152 connections or accepting any connections except on a control port.
14153 Bundles and controllers can set this option before letting Tor talk
14154 to the rest of the network, for example to prevent any connections
14155 to a non-bridge address. Packages like Orbot can also use this
14156 option to instruct Tor to save power when the network is off.
14157 - Clients and bridges can now be configured to use a separate
14158 "transport" proxy. This approach makes the censorship arms race
14159 easier by allowing bridges to use protocol obfuscation plugins. It
14160 implements the "managed proxy" part of proposal 180 (ticket 3472).
14161 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
14162 implementation. It makes AES_CTR about 7% faster than our old one
14163 (which was about 10% faster than the one OpenSSL used to provide).
14164 Resolves ticket 4526.
14165 - Add a "tor2web mode" for clients that want to connect to hidden
14166 services non-anonymously (and possibly more quickly). As a safety
14167 measure to try to keep users from turning this on without knowing
14168 what they are doing, tor2web mode must be explicitly enabled at
14169 compile time, and a copy of Tor compiled to run in tor2web mode
14170 cannot be used as a normal Tor client. Implements feature 2553.
14171 - Add experimental support for running on Windows with IOCP and no
14172 kernel-space socket buffers. This feature is controlled by a new
14173 "UserspaceIOCPBuffers" config option (off by default), which has
14174 no effect unless Tor has been built with support for bufferevents,
14175 is running on Windows, and has enabled IOCP. This may, in the long
14176 run, help solve or mitigate bug 98.
14177 - Use a more secure consensus parameter voting algorithm. Now at
14178 least three directory authorities or a majority of them must
14179 vote on a given parameter before it will be included in the
14180 consensus. Implements proposal 178.
14183 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
14184 They used to check that the timestamp was within 30 minutes
14185 of their system clock, so they could cap the size of their
14186 replay-detection cache, but that approach unnecessarily refused
14187 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
14188 the v3 intro-point protocol (the first one which sent a timestamp
14189 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
14190 - Only use the EVP interface when AES acceleration is enabled,
14191 to avoid a 5-7% performance regression. Resolves issue 4525;
14192 bugfix on 0.2.3.8-alpha.
14194 o Privacy/anonymity features (bridge detection):
14195 - Make bridge SSL certificates a bit more stealthy by using random
14196 serial numbers, in the same fashion as OpenSSL when generating
14197 self-signed certificates. Implements ticket 4584.
14198 - Introduce a new config option "DynamicDHGroups", enabled by
14199 default, which provides each bridge with a unique prime DH modulus
14200 to be used during SSL handshakes. This option attempts to help
14201 against censors who might use the Apache DH modulus as a static
14202 identifier for bridges. Addresses ticket 4548.
14204 o Minor features (new/different config options):
14205 - New configuration option "DisableDebuggerAttachment" (on by default)
14206 to prevent basic debugging attachment attempts by other processes.
14207 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
14208 - Allow MapAddress directives to specify matches against super-domains,
14209 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
14210 Implements issue 933.
14211 - Slightly change behavior of "list" options (that is, config
14212 options that can appear more than once) when they appear both in
14213 torrc and on the command line. Previously, the command-line options
14214 would be appended to the ones from torrc. Now, the command-line
14215 options override the torrc options entirely. This new behavior
14216 allows the user to override list options (like exit policies and
14217 ports to listen on) from the command line, rather than simply
14218 appending to the list.
14219 - You can get the old (appending) command-line behavior for "list"
14220 options by prefixing the option name with a "+".
14221 - You can remove all the values for a "list" option from the command
14222 line without adding any new ones by prefixing the option name
14224 - Add experimental support for a "defaults" torrc file to be parsed
14225 before the regular torrc. Torrc options override the defaults file's
14226 options in the same way that the command line overrides the torrc.
14227 The SAVECONF controller command saves only those options which
14228 differ between the current configuration and the defaults file. HUP
14229 reloads both files. (Note: This is an experimental feature; its
14230 behavior will probably be refined in future 0.2.3.x-alpha versions
14231 to better meet packagers' needs.) Implements task 4552.
14234 - Try to make the introductory warning message that Tor prints on
14235 startup more useful for actually finding help and information.
14236 Resolves ticket 2474.
14237 - Running "make version" now displays the version of Tor that
14238 we're about to build. Idea from katmagic; resolves issue 4400.
14239 - Expire old or over-used hidden service introduction points.
14240 Required by fix for bug 3460.
14241 - Move the replay-detection cache for the RSA-encrypted parts of
14242 INTRODUCE2 cells to the introduction point data structures.
14243 Previously, we would use one replay-detection cache per hidden
14244 service. Required by fix for bug 3460.
14245 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
14246 public key replay-detection cache from 60 minutes to 5 minutes. This
14247 replay-detection cache is now used only to detect multiple
14248 INTRODUCE2 cells specifying the same rendezvous point, so we can
14249 avoid launching multiple simultaneous attempts to connect to it.
14251 o Minor bugfixes (on Tor 0.2.2.x and earlier):
14252 - Resolve an integer overflow bug in smartlist_ensure_capacity().
14253 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
14255 - Fix a minor formatting issue in one of tor-gencert's error messages.
14257 - Prevent a false positive from the check-spaces script, by disabling
14258 the "whitespace between function name and (" check for functions
14260 - Fix a log message suggesting that people contact a non-existent
14261 email address. Fixes bug 3448.
14262 - Fix null-pointer access that could occur if TLS allocation failed.
14263 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
14264 - Report a real bootstrap problem to the controller on router
14265 identity mismatch. Previously we just said "foo", which probably
14266 made a lot of sense at the time. Fixes bug 4169; bugfix on
14268 - If we had ever tried to call tor_addr_to_str() on an address of
14269 unknown type, we would have done a strdup() on an uninitialized
14270 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
14271 Reported by "troll_un".
14272 - Correctly detect and handle transient lookup failures from
14273 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
14274 Reported by "troll_un".
14275 - Use tor_socket_t type for listener argument to accept(). Fixes bug
14276 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
14277 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
14278 bug 4532; found by "troll_un".
14280 o Minor bugfixes (on Tor 0.2.3.x):
14281 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
14283 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
14284 circuit for use as a hidden service client's rendezvous point.
14285 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
14286 with help from wanoskarnet.
14287 - Restore behavior of overriding SocksPort, ORPort, and similar
14288 options from the command line. Bugfix on 0.2.3.3-alpha.
14291 - Properly handle the case where the build-tree is not the same
14292 as the source tree when generating src/common/common_sha1.i,
14293 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
14294 bugfix on 0.2.0.1-alpha.
14296 o Code simplifications, cleanups, and refactorings:
14297 - Remove the pure attribute from all functions that used it
14298 previously. In many cases we assigned it incorrectly, because the
14299 functions might assert or call impure functions, and we don't have
14300 evidence that keeping the pure attribute is worthwhile. Implements
14301 changes suggested in ticket 4421.
14302 - Remove some dead code spotted by coverity. Fixes cid 432.
14303 Bugfix on 0.2.3.1-alpha, closes bug 4637.
14306 Changes in version 0.2.3.8-alpha - 2011-11-22
14307 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
14308 socketpair-related bug that has been bothering Windows users. It adds
14309 support to serve microdescriptors to controllers, so Vidalia's network
14310 map can resume listing relays (once Vidalia implements its side),
14311 and adds better support for hardware AES acceleration. Finally, it
14312 starts the process of adjusting the bandwidth cutoff for getting the
14313 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
14314 that tiny relays harm performance more than they help network capacity.
14317 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
14318 that it doesn't attempt to allocate a socketpair. This could cause
14319 some problems on Windows systems with overzealous firewalls. Fix for
14320 bug 4457; workaround for Libevent versions 2.0.1-alpha through
14322 - Correctly sanity-check that we don't underflow on a memory
14323 allocation (and then assert) for hidden service introduction
14324 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14325 bugfix on 0.2.1.5-alpha.
14326 - Remove the artificially low cutoff of 20KB to guarantee the Fast
14327 flag. In the past few years the average relay speed has picked
14328 up, and while the "top 7/8 of the network get the Fast flag" and
14329 "all relays with 20KB or more of capacity get the Fast flag" rules
14330 used to have the same result, now the top 7/8 of the network has
14331 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
14332 - Fix a rare assertion failure when checking whether a v0 hidden
14333 service descriptor has any usable introduction points left, and
14334 we don't have enough information to build a circuit to the first
14335 intro point named in the descriptor. The HS client code in
14336 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
14337 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
14338 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
14339 - Make bridge authorities not crash when they are asked for their own
14340 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
14341 - When running as a client, do not print a misleading (and plain
14342 wrong) log message that we're collecting "directory request"
14343 statistics: clients don't collect statistics. Also don't create a
14344 useless (because empty) stats file in the stats/ directory. Fixes
14345 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
14348 - Allow Tor controllers like Vidalia to obtain the microdescriptor
14349 for a relay by identity digest or nickname. Previously,
14350 microdescriptors were only available by their own digests, so a
14351 controller would have to ask for and parse the whole microdescriptor
14352 consensus in order to look up a single relay's microdesc. Fixes
14353 bug 3832; bugfix on 0.2.3.1-alpha.
14354 - Use OpenSSL's EVP interface for AES encryption, so that all AES
14355 operations can use hardware acceleration (if present). Resolves
14358 o Minor bugfixes (on 0.2.2.x and earlier):
14359 - Detect failure to initialize Libevent. This fix provides better
14360 detection for future instances of bug 4457.
14361 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
14362 function. This was eating up hideously large amounts of time on some
14363 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
14364 - Don't warn about unused log_mutex in log.c when building with
14365 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
14366 0.1.0.6-rc which introduced --disable-threads.
14367 - Allow manual 'authenticate' commands to the controller interface
14368 from netcat (nc) as well as telnet. We were rejecting them because
14369 they didn't come with the expected whitespace at the end of the
14370 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
14371 - Fix some (not actually triggerable) buffer size checks in usage of
14372 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
14374 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
14375 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
14376 - When configuring, starting, or stopping an NT service, stop
14377 immediately after the service configuration attempt has succeeded
14378 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
14379 - When sending a NETINFO cell, include the original address
14380 received for the other side, not its canonical address. Found
14381 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
14382 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
14383 can pick them up when the tests aren't disabled. Bugfix on
14384 0.2.2.4-alpha which introduced tinytest.
14385 - Fix a memory leak when we check whether a hidden service
14386 descriptor has any usable introduction points left. Fixes bug
14387 4424. Bugfix on 0.2.2.25-alpha.
14388 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
14389 occurred when a client tried to fetch a descriptor for a bridge
14390 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
14392 o Minor bugfixes (on 0.2.3.x):
14393 - Make util unit tests build correctly with MSVC. Bugfix on
14394 0.2.3.3-alpha. Patch by Gisle Vanem.
14395 - Successfully detect AUTH_CHALLENGE cells with no recognized
14396 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
14397 Found by frosty_un.
14398 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
14399 it should still send a NETINFO cell to allow the connection to
14400 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
14402 - Log less loudly when we get an invalid authentication certificate
14403 from a source other than a directory authority: it's not unusual
14404 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
14406 - Tolerate servers with more clock skew in their authentication
14407 certificates than previously. Fixes bug 4371; bugfix on
14409 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
14410 on 0.2.3.4-alpha and 0.2.3.6-alpha.
14413 - Add two new config options for directory authorities:
14414 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
14415 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
14416 that is always sufficient to satisfy the bandwidth requirement for
14417 the Guard flag. Now it will be easier for researchers to simulate
14418 Tor networks with different values. Resolves ticket 4484.
14419 - When Tor ignores a hidden service specified in its configuration,
14420 include the hidden service's directory in the warning message.
14421 Previously, we would only tell the user that some hidden service
14422 was ignored. Bugfix on 0.0.6; fixes bug 4426.
14423 - When we fail to initialize Libevent, retry with IOCP disabled so we
14424 don't need to turn on multi-threading support in Libevent, which in
14425 turn requires a working socketpair(). This is a workaround for bug
14426 4457, which affects Libevent versions from 2.0.1-alpha through
14428 - Detect when we try to build on a platform that doesn't define
14429 AF_UNSPEC to 0. We don't work there, so refuse to compile.
14430 - Update to the November 1 2011 Maxmind GeoLite Country database.
14432 o Packaging changes:
14433 - Make it easier to automate expert package builds on Windows,
14434 by removing an absolute path from makensis.exe command.
14436 o Code simplifications and refactoring:
14437 - Remove some redundant #include directives throughout the code.
14438 Patch from Andrea Gelmini.
14439 - Unconditionally use OpenSSL's AES implementation instead of our
14440 old built-in one. OpenSSL's AES has been better for a while, and
14441 relatively few servers should still be on any version of OpenSSL
14442 that doesn't have good optimized assembly AES.
14443 - Use the name "CERTS" consistently to refer to the new cell type;
14444 we were calling it CERT in some places and CERTS in others.
14447 - Numerous new unit tests for functions in util.c and address.c by
14449 - The long-disabled benchmark tests are now split into their own
14450 ./src/test/bench binary.
14451 - The benchmark tests can now use more accurate timers than
14452 gettimeofday() when such timers are available.
14455 Changes in version 0.2.3.7-alpha - 2011-10-30
14456 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
14457 the new v3 handshake. It also resolves yet another bridge address
14461 - If we mark an OR connection for close based on a cell we process,
14462 don't process any further cells on it. We already avoid further
14463 reads on marked-for-close connections, but now we also discard the
14464 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
14465 which was the first version where we might mark a connection for
14466 close based on processing a cell on it.
14467 - Fix a double-free bug that would occur when we received an invalid
14468 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
14469 bugfix on 0.2.3.6-alpha.
14470 - Bridges no longer include their address in NETINFO cells on outgoing
14471 OR connections, to allow them to blend in better with clients.
14472 Removes another avenue for enumerating bridges. Reported by
14473 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
14474 cells were introduced.
14477 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
14478 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
14481 Changes in version 0.2.3.6-alpha - 2011-10-26
14482 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
14483 anonymity vulnerability where an attacker can deanonymize Tor
14484 users. Everybody should upgrade.
14486 This release also features support for a new v3 connection handshake
14487 protocol, and fixes to make hidden service connections more robust.
14490 - Implement a new handshake protocol (v3) for authenticating Tors to
14491 each other over TLS. It should be more resistant to fingerprinting
14492 than previous protocols, and should require less TLS hacking for
14493 future Tor implementations. Implements proposal 176.
14494 - Allow variable-length padding cells to disguise the length of
14495 Tor's TLS records. Implements part of proposal 184.
14497 o Privacy/anonymity fixes (clients):
14498 - Clients and bridges no longer send TLS certificate chains on
14499 outgoing OR connections. Previously, each client or bridge would
14500 use the same cert chain for all outgoing OR connections until
14501 its IP address changes, which allowed any relay that the client
14502 or bridge contacted to determine which entry guards it is using.
14503 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14504 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14505 no longer considers that connection as suitable for satisfying a
14506 circuit EXTEND request. Now relays can protect clients from the
14507 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14508 - Directory authorities no longer assign the Guard flag to relays
14509 that haven't upgraded to the above "refuse EXTEND requests
14510 to client connections" fix. Now directory authorities can
14511 protect clients from the CVE-2011-2768 issue even if neither
14512 the clients nor the relays have upgraded yet. There's a new
14513 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
14514 to let us transition smoothly, else tomorrow there would be no
14517 o Major bugfixes (hidden services):
14518 - Improve hidden service robustness: when an attempt to connect to
14519 a hidden service ends, be willing to refetch its hidden service
14520 descriptors from each of the HSDir relays responsible for them
14521 immediately. Previously, we would not consider refetching the
14522 service's descriptors from each HSDir for 15 minutes after the last
14523 fetch, which was inconvenient if the hidden service was not running
14524 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
14525 - When one of a hidden service's introduction points appears to be
14526 unreachable, stop trying it. Previously, we would keep trying
14527 to build circuits to the introduction point until we lost the
14528 descriptor, usually because the user gave up and restarted Tor.
14529 Partly fixes bug 3825.
14530 - Don't launch a useless circuit after failing to use one of a
14531 hidden service's introduction points. Previously, we would
14532 launch a new introduction circuit, but not set the hidden service
14533 which that circuit was intended to connect to, so it would never
14534 actually be used. A different piece of code would then create a
14535 new introduction circuit correctly. Bug reported by katmagic and
14536 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
14538 o Major bugfixes (other):
14539 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14540 that they initiated. Relays could distinguish incoming bridge
14541 connections from client connections, creating another avenue for
14542 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14543 Found by "frosty_un".
14544 - Don't update the AccountingSoftLimitHitAt state file entry whenever
14545 tor gets started. This prevents a wrong average bandwidth
14546 estimate, which would cause relays to always start a new accounting
14547 interval at the earliest possible moment. Fixes bug 2003; bugfix
14548 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
14549 immensely in tracking this bug down.
14550 - Fix a crash bug when changing node restrictions while a DNS lookup
14551 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
14554 o Minor bugfixes (on 0.2.2.x and earlier):
14555 - When a hidden service turns an extra service-side introduction
14556 circuit into a general-purpose circuit, free the rend_data and
14557 intro_key fields first, so we won't leak memory if the circuit
14558 is cannibalized for use as another service-side introduction
14559 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
14560 - Rephrase the log message emitted if the TestSocks check is
14561 successful. Patch from Fabian Keil; fixes bug 4094.
14562 - Bridges now skip DNS self-tests, to act a little more stealthily.
14563 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
14564 bridges. Patch by "warms0x".
14565 - Remove a confusing dollar sign from the example fingerprint in the
14566 man page, and also make the example fingerprint a valid one. Fixes
14567 bug 4309; bugfix on 0.2.1.3-alpha.
14568 - Fix internal bug-checking logic that was supposed to catch
14569 failures in digest generation so that it will fail more robustly
14570 if we ask for a nonexistent algorithm. Found by Coverity Scan.
14571 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
14572 - Report any failure in init_keys() calls launched because our
14573 IP address has changed. Spotted by Coverity Scan. Bugfix on
14574 0.1.1.4-alpha; fixes CID 484.
14576 o Minor bugfixes (on 0.2.3.x):
14577 - Fix a bug in configure.in that kept it from building a configure
14578 script with autoconf versions earlier than 2.61. Fixes bug 2430;
14579 bugfix on 0.2.3.1-alpha.
14580 - Don't warn users that they are exposing a client port to the
14581 Internet if they have specified an RFC1918 address. Previously,
14582 we would warn if the user had specified any non-loopback
14583 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
14584 - Fix memory leaks in the failing cases of the new SocksPort and
14585 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
14586 fixes coverity CIDs 485, 486, and 487.
14589 - When a hidden service's introduction point times out, consider
14590 trying it again during the next attempt to connect to the
14591 HS. Previously, we would not try it again unless a newly fetched
14592 descriptor contained it. Required by fixes for bugs 1297 and 3825.
14593 - The next version of Windows will be called Windows 8, and it has
14594 a major version of 6, minor version of 2. Correctly identify that
14595 version instead of calling it "Very recent version". Resolves
14596 ticket 4153; reported by funkstar.
14597 - The Bridge Authority now writes statistics on how many bridge
14598 descriptors it gave out in total, and how many unique descriptors
14599 it gave out. It also lists how often the most and least commonly
14600 fetched descriptors were given out, as well as the median and
14601 25th/75th percentile. Implements tickets 4200 and 4294.
14602 - Update to the October 4 2011 Maxmind GeoLite Country database.
14604 o Code simplifications and refactoring:
14605 - Remove some old code to remember statistics about which descriptors
14606 we've served as a directory mirror. The feature wasn't used and
14607 is outdated now that microdescriptors are around.
14608 - Rename Tor functions that turn strings into addresses, so that
14609 "parse" indicates that no hostname resolution occurs, and
14610 "lookup" indicates that hostname resolution may occur. This
14611 should help prevent mistakes in the future. Fixes bug 3512.
14614 Changes in version 0.2.2.34 - 2011-10-26
14615 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
14616 can deanonymize Tor users. Everybody should upgrade.
14618 The attack relies on four components: 1) Clients reuse their TLS cert
14619 when talking to different relays, so relays can recognize a user by
14620 the identity key in her cert. 2) An attacker who knows the client's
14621 identity key can probe each guard relay to see if that identity key
14622 is connected to that guard relay right now. 3) A variety of active
14623 attacks in the literature (starting from "Low-Cost Traffic Analysis
14624 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
14625 discover the guard relays that a Tor user visiting the website is using.
14626 4) Clients typically pick three guards at random, so the set of guards
14627 for a given user could well be a unique fingerprint for her. This
14628 release fixes components #1 and #2, which is enough to block the attack;
14629 the other two remain as open research problems. Special thanks to
14630 "frosty_un" for reporting the issue to us!
14632 Clients should upgrade so they are no longer recognizable by the TLS
14633 certs they present. Relays should upgrade so they no longer allow a
14634 remote attacker to probe them to test whether unpatched clients are
14635 currently connected to them.
14637 This release also fixes several vulnerabilities that allow an attacker
14638 to enumerate bridge relays. Some bridge enumeration attacks still
14639 remain; see for example proposal 188.
14641 o Privacy/anonymity fixes (clients):
14642 - Clients and bridges no longer send TLS certificate chains on
14643 outgoing OR connections. Previously, each client or bridge would
14644 use the same cert chain for all outgoing OR connections until
14645 its IP address changes, which allowed any relay that the client
14646 or bridge contacted to determine which entry guards it is using.
14647 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14648 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14649 no longer considers that connection as suitable for satisfying a
14650 circuit EXTEND request. Now relays can protect clients from the
14651 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14652 - Directory authorities no longer assign the Guard flag to relays
14653 that haven't upgraded to the above "refuse EXTEND requests
14654 to client connections" fix. Now directory authorities can
14655 protect clients from the CVE-2011-2768 issue even if neither
14656 the clients nor the relays have upgraded yet. There's a new
14657 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
14658 to let us transition smoothly, else tomorrow there would be no
14661 o Privacy/anonymity fixes (bridge enumeration):
14662 - Bridge relays now do their directory fetches inside Tor TLS
14663 connections, like all the other clients do, rather than connecting
14664 directly to the DirPort like public relays do. Removes another
14665 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
14666 - Bridges relays now build circuits for themselves in a more similar
14667 way to how clients build them. Removes another avenue for
14668 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
14669 when bridges were introduced.
14670 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14671 that they initiated. Relays could distinguish incoming bridge
14672 connections from client connections, creating another avenue for
14673 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14674 Found by "frosty_un".
14677 - Fix a crash bug when changing node restrictions while a DNS lookup
14678 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
14680 - Don't launch a useless circuit after failing to use one of a
14681 hidden service's introduction points. Previously, we would
14682 launch a new introduction circuit, but not set the hidden service
14683 which that circuit was intended to connect to, so it would never
14684 actually be used. A different piece of code would then create a
14685 new introduction circuit correctly. Bug reported by katmagic and
14686 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
14689 - Change an integer overflow check in the OpenBSD_Malloc code so
14690 that GCC is less likely to eliminate it as impossible. Patch
14691 from Mansour Moufid. Fixes bug 4059.
14692 - When a hidden service turns an extra service-side introduction
14693 circuit into a general-purpose circuit, free the rend_data and
14694 intro_key fields first, so we won't leak memory if the circuit
14695 is cannibalized for use as another service-side introduction
14696 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
14697 - Bridges now skip DNS self-tests, to act a little more stealthily.
14698 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
14699 bridges. Patch by "warms0x".
14700 - Fix internal bug-checking logic that was supposed to catch
14701 failures in digest generation so that it will fail more robustly
14702 if we ask for a nonexistent algorithm. Found by Coverity Scan.
14703 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
14704 - Report any failure in init_keys() calls launched because our
14705 IP address has changed. Spotted by Coverity Scan. Bugfix on
14706 0.1.1.4-alpha; fixes CID 484.
14708 o Minor bugfixes (log messages and documentation):
14709 - Remove a confusing dollar sign from the example fingerprint in the
14710 man page, and also make the example fingerprint a valid one. Fixes
14711 bug 4309; bugfix on 0.2.1.3-alpha.
14712 - The next version of Windows will be called Windows 8, and it has
14713 a major version of 6, minor version of 2. Correctly identify that
14714 version instead of calling it "Very recent version". Resolves
14715 ticket 4153; reported by funkstar.
14716 - Downgrade log messages about circuit timeout calibration from
14717 "notice" to "info": they don't require or suggest any human
14718 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
14719 bugfix on 0.2.2.14-alpha.
14722 - Turn on directory request statistics by default and include them in
14723 extra-info descriptors. Don't break if we have no GeoIP database.
14724 Backported from 0.2.3.1-alpha; implements ticket 3951.
14725 - Update to the October 4 2011 Maxmind GeoLite Country database.
14728 Changes in version 0.2.1.31 - 2011-10-26
14729 Tor 0.2.1.31 backports important security and privacy fixes for
14730 oldstable. This release is intended only for package maintainers and
14731 others who cannot use the 0.2.2 stable series. All others should be
14732 using Tor 0.2.2.x or newer.
14734 o Security fixes (also included in 0.2.2.x):
14735 - Replace all potentially sensitive memory comparison operations
14736 with versions whose runtime does not depend on the data being
14737 compared. This will help resist a class of attacks where an
14738 adversary can use variations in timing information to learn
14739 sensitive data. Fix for one case of bug 3122. (Safe memcmp
14740 implementation by Robert Ransom based partially on code by DJB.)
14741 - Fix an assert in parsing router descriptors containing IPv6
14742 addresses. This one took down the directory authorities when
14743 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
14745 o Privacy/anonymity fixes (also included in 0.2.2.x):
14746 - Clients and bridges no longer send TLS certificate chains on
14747 outgoing OR connections. Previously, each client or bridge would
14748 use the same cert chain for all outgoing OR connections until
14749 its IP address changes, which allowed any relay that the client
14750 or bridge contacted to determine which entry guards it is using.
14751 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14752 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14753 no longer considers that connection as suitable for satisfying a
14754 circuit EXTEND request. Now relays can protect clients from the
14755 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14756 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14757 that they initiated. Relays could distinguish incoming bridge
14758 connections from client connections, creating another avenue for
14759 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14760 Found by "frosty_un".
14761 - When receiving a hidden service descriptor, check that it is for
14762 the hidden service we wanted. Previously, Tor would store any
14763 hidden service descriptors that a directory gave it, whether it
14764 wanted them or not. This wouldn't have let an attacker impersonate
14765 a hidden service, but it did let directories pre-seed a client
14766 with descriptors that it didn't want. Bugfix on 0.0.6.
14767 - Avoid linkability based on cached hidden service descriptors: forget
14768 all hidden service descriptors cached as a client when processing a
14769 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
14770 - Make the bridge directory authority refuse to answer directory
14771 requests for "all" descriptors. It used to include bridge
14772 descriptors in its answer, which was a major information leak.
14773 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
14774 - Don't attach new streams to old rendezvous circuits after SIGNAL
14775 NEWNYM. Previously, we would keep using an existing rendezvous
14776 circuit if it remained open (i.e. if it were kept open by a
14777 long-lived stream, or if a new stream were attached to it before
14778 Tor could notice that it was old and no longer in use). Bugfix on
14779 0.1.1.15-rc; fixes bug 3375.
14781 o Minor bugfixes (also included in 0.2.2.x):
14782 - When we restart our relay, we might get a successful connection
14783 from the outside before we've started our reachability tests,
14784 triggering a warning: "ORPort found reachable, but I have no
14785 routerinfo yet. Failing to inform controller of success." This
14786 bug was harmless unless Tor is running under a controller
14787 like Vidalia, in which case the controller would never get a
14788 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
14790 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
14791 enabled. Fixes bug 1526.
14792 - Remove undocumented option "-F" from tor-resolve: it hasn't done
14793 anything since 0.2.1.16-rc.
14794 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
14795 None of the cases where we did this before were wrong, but by making
14796 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
14797 - Fix a rare crash bug that could occur when a client was configured
14798 with a large number of bridges. Fixes bug 2629; bugfix on
14799 0.2.1.2-alpha. Bugfix by trac user "shitlei".
14800 - Correct the warning displayed when a rendezvous descriptor exceeds
14801 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
14803 - Fix an uncommon assertion failure when running with DNSPort under
14804 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
14805 - When warning about missing zlib development packages during compile,
14806 give the correct package names. Bugfix on 0.2.0.1-alpha.
14807 - Require that introduction point keys and onion keys have public
14808 exponent 65537. Bugfix on 0.2.0.10-alpha.
14809 - Do not crash when our configuration file becomes unreadable, for
14810 example due to a permissions change, between when we start up
14811 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
14813 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
14815 - Always NUL-terminate the sun_path field of a sockaddr_un before
14816 passing it to the kernel. (Not a security issue: kernels are
14817 smart enough to reject bad sockaddr_uns.) Found by Coverity;
14818 CID #428. Bugfix on Tor 0.2.0.3-alpha.
14819 - Don't stack-allocate the list of supplementary GIDs when we're
14820 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
14821 could take up to 256K, which is way too much stack. Found by
14822 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
14824 o Minor bugfixes (only in 0.2.1.x):
14825 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
14826 rely on them. Bugfix on 0.2.1.30.
14827 - Use git revisions instead of svn revisions when generating our
14828 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
14830 o Minor features (also included in 0.2.2.x):
14831 - Adjust the expiration time on our SSL session certificates to
14832 better match SSL certs seen in the wild. Resolves ticket 4014.
14833 - Allow nameservers with IPv6 address. Resolves bug 2574.
14834 - Update to the October 4 2011 Maxmind GeoLite Country database.
14837 Changes in version 0.2.3.5-alpha - 2011-09-28
14838 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
14839 bridge relays; fixes an assertion error that many users started hitting
14840 today; and adds the ability to refill token buckets more often than
14841 once per second, allowing significant performance improvements.
14844 - Bridge relays now do their directory fetches inside Tor TLS
14845 connections, like all the other clients do, rather than connecting
14846 directly to the DirPort like public relays do. Removes another
14847 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
14848 - Bridges relays now build circuits for themselves in a more similar
14849 way to how clients build them. Removes another avenue for
14850 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
14851 when bridges were introduced.
14854 - Fix an "Assertion md->held_by_node == 1 failed" error that could
14855 occur when the same microdescriptor was referenced by two node_t
14856 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
14858 o Major features (networking):
14859 - Add a new TokenBucketRefillInterval option to refill token buckets
14860 more frequently than once per second. This should improve network
14861 performance, alleviate queueing problems, and make traffic less
14862 bursty. Implements proposal 183; closes ticket 3630. Design by
14863 Florian Tschorsch and Björn Scheuermann; implementation by
14867 - Change an integer overflow check in the OpenBSD_Malloc code so
14868 that GCC is less likely to eliminate it as impossible. Patch
14869 from Mansour Moufid. Fixes bug 4059.
14871 o Minor bugfixes (usability):
14872 - Downgrade log messages about circuit timeout calibration from
14873 "notice" to "info": they don't require or suggest any human
14874 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
14875 bugfix on 0.2.2.14-alpha.
14877 o Minor features (diagnostics):
14878 - When the system call to create a listener socket fails, log the
14879 error message explaining why. This may help diagnose bug 4027.
14882 Changes in version 0.2.3.4-alpha - 2011-09-13
14883 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
14884 tweak to Tor's TLS handshake that makes relays and bridges that run
14885 this new version reachable from Iran again. It also fixes a few new
14886 bugs in 0.2.3.x, and teaches relays to recognize when they're not
14887 listed in the network consensus and republish.
14889 o Major bugfixes (also part of 0.2.2.33):
14890 - Avoid an assertion failure when reloading a configuration with
14891 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
14892 3923; bugfix on 0.2.2.25-alpha.
14894 o Minor features (security, also part of 0.2.2.33):
14895 - Check for replays of the public-key encrypted portion of an
14896 INTRODUCE1 cell, in addition to the current check for replays of
14897 the g^x value. This prevents a possible class of active attacks
14898 by an attacker who controls both an introduction point and a
14899 rendezvous point, and who uses the malleability of AES-CTR to
14900 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
14901 that these attacks are infeasible (requiring the attacker to send
14902 on the order of zettabytes of altered cells in a short interval),
14903 but we'd rather block them off in case there are any classes of
14904 this attack that we missed. Reported by Willem Pinckaers.
14906 o Minor features (also part of 0.2.2.33):
14907 - Adjust the expiration time on our SSL session certificates to
14908 better match SSL certs seen in the wild. Resolves ticket 4014.
14909 - Change the default required uptime for a relay to be accepted as
14910 a HSDir (hidden service directory) from 24 hours to 25 hours.
14911 Improves on 0.2.0.10-alpha; resolves ticket 2649.
14912 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
14913 authorities to abstain from voting on assignment of the HSDir
14914 consensus flag. Related to bug 2649.
14915 - Update to the September 6 2011 Maxmind GeoLite Country database.
14917 o Minor bugfixes (also part of 0.2.2.33):
14918 - Demote the 'replay detected' log message emitted when a hidden
14919 service receives the same Diffie-Hellman public key in two different
14920 INTRODUCE2 cells to info level. A normal Tor client can cause that
14921 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
14922 fixes part of bug 2442.
14923 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
14924 level. There is nothing that a hidden service's operator can do
14925 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
14927 - Clarify a log message specifying the characters permitted in
14928 HiddenServiceAuthorizeClient client names. Previously, the log
14929 message said that "[A-Za-z0-9+-_]" were permitted; that could have
14930 given the impression that every ASCII character between "+" and "_"
14931 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
14933 o Build fixes (also part of 0.2.2.33):
14934 - Clean up some code issues that prevented Tor from building on older
14935 BSDs. Fixes bug 3894; reported by "grarpamp".
14936 - Search for a platform-specific version of "ar" when cross-compiling.
14937 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
14940 - Fix a bug where the SocksPort option (for example) would get
14941 ignored and replaced by the default if a SocksListenAddress
14942 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
14946 - Relays now try regenerating and uploading their descriptor more
14947 frequently if they are not listed in the consensus, or if the
14948 version of their descriptor listed in the consensus is too
14949 old. This fix should prevent situations where a server declines
14950 to re-publish itself because it has done so too recently, even
14951 though the authorities decided not to list its recent-enough
14952 descriptor. Fix for bug 3327.
14955 - Relays now include a reason for regenerating their descriptors
14956 in an HTTP header when uploading to the authorities. This will
14957 make it easier to debug descriptor-upload issues in the future.
14958 - When starting as root and then changing our UID via the User
14959 control option, and we have a ControlSocket configured, make sure
14960 that the ControlSocket is owned by the same account that Tor will
14961 run under. Implements ticket 3421; fix by Jérémy Bobbio.
14964 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
14965 utility function used in the control-port code). This shouldn't
14966 ever happen unless Tor is completely out of memory, but if it did
14967 happen and Tor somehow recovered from it, Tor could have sent a log
14968 message to a control port in the middle of a reply to a controller
14969 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
14970 - Make 'FetchUselessDescriptors' cause all descriptor types and
14971 all consensus types (including microdescriptors) to get fetched.
14972 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
14974 o Code refactoring:
14975 - Make a new "entry connection" struct as an internal subtype of "edge
14976 connection", to simplify the code and make exit connections smaller.
14979 Changes in version 0.2.2.33 - 2011-09-13
14980 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
14981 TLS handshake that makes relays and bridges that run this new version
14982 reachable from Iran again.
14985 - Avoid an assertion failure when reloading a configuration with
14986 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
14987 3923; bugfix on 0.2.2.25-alpha.
14989 o Minor features (security):
14990 - Check for replays of the public-key encrypted portion of an
14991 INTRODUCE1 cell, in addition to the current check for replays of
14992 the g^x value. This prevents a possible class of active attacks
14993 by an attacker who controls both an introduction point and a
14994 rendezvous point, and who uses the malleability of AES-CTR to
14995 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
14996 that these attacks are infeasible (requiring the attacker to send
14997 on the order of zettabytes of altered cells in a short interval),
14998 but we'd rather block them off in case there are any classes of
14999 this attack that we missed. Reported by Willem Pinckaers.
15002 - Adjust the expiration time on our SSL session certificates to
15003 better match SSL certs seen in the wild. Resolves ticket 4014.
15004 - Change the default required uptime for a relay to be accepted as
15005 a HSDir (hidden service directory) from 24 hours to 25 hours.
15006 Improves on 0.2.0.10-alpha; resolves ticket 2649.
15007 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
15008 authorities to abstain from voting on assignment of the HSDir
15009 consensus flag. Related to bug 2649.
15010 - Update to the September 6 2011 Maxmind GeoLite Country database.
15012 o Minor bugfixes (documentation and log messages):
15013 - Correct the man page to explain that HashedControlPassword and
15014 CookieAuthentication can both be set, in which case either method
15015 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
15016 when we decided to allow these config options to both be set. Issue
15017 raised by bug 3898.
15018 - Demote the 'replay detected' log message emitted when a hidden
15019 service receives the same Diffie-Hellman public key in two different
15020 INTRODUCE2 cells to info level. A normal Tor client can cause that
15021 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
15022 fixes part of bug 2442.
15023 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
15024 level. There is nothing that a hidden service's operator can do
15025 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
15027 - Clarify a log message specifying the characters permitted in
15028 HiddenServiceAuthorizeClient client names. Previously, the log
15029 message said that "[A-Za-z0-9+-_]" were permitted; that could have
15030 given the impression that every ASCII character between "+" and "_"
15031 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
15034 - Provide a substitute implementation of lround() for MSVC, which
15035 apparently lacks it. Patch from Gisle Vanem.
15036 - Clean up some code issues that prevented Tor from building on older
15037 BSDs. Fixes bug 3894; reported by "grarpamp".
15038 - Search for a platform-specific version of "ar" when cross-compiling.
15039 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
15042 Changes in version 0.2.3.3-alpha - 2011-09-01
15043 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
15044 security, and provides client-side support for the microdescriptor
15045 and optimistic data features introduced earlier in the 0.2.3.x
15046 series. It also includes numerous critical bugfixes in the (optional)
15047 bufferevent-based networking backend.
15049 o Major features (stream isolation):
15050 - You can now configure Tor so that streams from different
15051 applications are isolated on different circuits, to prevent an
15052 attacker who sees your streams as they leave an exit node from
15053 linking your sessions to one another. To do this, choose some way
15054 to distinguish the applications: have them connect to different
15055 SocksPorts, or have one of them use SOCKS4 while the other uses
15056 SOCKS5, or have them pass different authentication strings to the
15057 SOCKS proxy. Then, use the new SocksPort syntax to configure the
15058 degree of isolation you need. This implements Proposal 171.
15059 - There's a new syntax for specifying multiple client ports (such as
15060 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
15061 multiple *Port entries with full addr:port syntax on each.
15062 The old *ListenAddress format is still supported, but you can't
15063 mix it with the new *Port syntax.
15065 o Major features (other):
15066 - Enable microdescriptor fetching by default for clients. This allows
15067 clients to download a much smaller amount of directory information.
15068 To disable it (and go back to the old-style consensus and
15069 descriptors), set "UseMicrodescriptors 0" in your torrc file.
15070 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
15071 "PortForwarding" config option), now supports Windows.
15072 - When using an exit relay running 0.2.3.x, clients can now
15073 "optimistically" send data before the exit relay reports that
15074 the stream has opened. This saves a round trip when starting
15075 connections where the client speaks first (such as web browsing).
15076 This behavior is controlled by a consensus parameter (currently
15077 disabled). To turn it on or off manually, use the "OptimisticData"
15078 torrc option. Implements proposal 181; code by Ian Goldberg.
15080 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
15081 - When using IOCP on Windows, we need to enable Libevent windows
15083 - The IOCP backend now works even when the user has not specified
15084 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
15085 Fixes part of bug 3752.
15086 - Correctly record the bytes we've read and written when using
15087 bufferevents, so that we can include them in our bandwidth history
15088 and advertised bandwidth. Fixes bug 3803.
15089 - Apply rate-limiting only at the bottom of a chain of filtering
15090 bufferevents. This prevents us from filling up internal read
15091 buffers and violating rate-limits when filtering bufferevents
15092 are enabled. Fixes part of bug 3804.
15093 - Add high-watermarks to the output buffers for filtered
15094 bufferevents. This prevents us from filling up internal write
15095 buffers and wasting CPU cycles when filtering bufferevents are
15096 enabled. Fixes part of bug 3804.
15097 - Correctly notice when data has been written from a bufferevent
15098 without flushing it completely. Fixes bug 3805.
15099 - Fix a bug where server-side tunneled bufferevent-based directory
15100 streams would get closed prematurely. Fixes bug 3814.
15101 - Fix a use-after-free error with per-connection rate-limiting
15102 buckets. Fixes bug 3888.
15104 o Major bugfixes (also part of 0.2.2.31-rc):
15105 - If we're configured to write our ControlPorts to disk, only write
15106 them after switching UID and creating the data directory. This way,
15107 we don't fail when starting up with a nonexistent DataDirectory
15108 and a ControlPortWriteToFile setting based on that directory. Fixes
15109 bug 3747; bugfix on Tor 0.2.2.26-beta.
15112 - Added a new CONF_CHANGED event so that controllers can be notified
15113 of any configuration changes made by other controllers, or by the
15114 user. Implements ticket 1692.
15115 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
15116 leak when using bufferevents, and lets Libevent worry about how to
15117 best copy data out of a buffer.
15118 - Replace files in stats/ rather than appending to them. Now that we
15119 include statistics in extra-info descriptors, it makes no sense to
15120 keep old statistics forever. Implements ticket 2930.
15122 o Minor features (build compatibility):
15123 - Limited, experimental support for building with nmake and MSVC.
15124 - Provide a substitute implementation of lround() for MSVC, which
15125 apparently lacks it. Patch from Gisle Vanem.
15127 o Minor features (also part of 0.2.2.31-rc):
15128 - Update to the August 2 2011 Maxmind GeoLite Country database.
15130 o Minor bugfixes (on 0.2.3.x-alpha):
15131 - Fix a spurious warning when parsing SOCKS requests with
15132 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
15133 - Get rid of a harmless warning that could happen on relays running
15134 with bufferevents. The warning was caused by someone doing an http
15135 request to a relay's orport. Also don't warn for a few related
15136 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
15138 o Minor bugfixes (on 2.2.x and earlier):
15139 - Correct the man page to explain that HashedControlPassword and
15140 CookieAuthentication can both be set, in which case either method
15141 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
15142 when we decided to allow these config options to both be set. Issue
15143 raised by bug 3898.
15144 - The "--quiet" and "--hush" options now apply not only to Tor's
15145 behavior before logs are configured, but also to Tor's behavior in
15146 the absense of configured logs. Fixes bug 3550; bugfix on
15149 o Minor bugfixes (also part of 0.2.2.31-rc):
15150 - Write several files in text mode, on OSes that distinguish text
15151 mode from binary mode (namely, Windows). These files are:
15152 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
15153 that collect those statistics; 'client_keys' and 'hostname' for
15154 hidden services that use authentication; and (in the tor-gencert
15155 utility) newly generated identity and signing keys. Previously,
15156 we wouldn't specify text mode or binary mode, leading to an
15157 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
15158 the DirRecordUsageByCountry option which would have triggered
15159 the assertion failure was added), although this assertion failure
15160 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
15161 - Selectively disable deprecation warnings on OS X because Lion
15162 started deprecating the shipped copy of openssl. Fixes bug 3643.
15163 - Remove an extra pair of quotation marks around the error
15164 message in control-port STATUS_GENERAL BUG events. Bugfix on
15165 0.1.2.6-alpha; fixes bug 3732.
15166 - When unable to format an address as a string, report its value
15167 as "???" rather than reusing the last formatted address. Bugfix
15170 o Code simplifications and refactoring:
15171 - Rewrite the listener-selection logic so that parsing which ports
15172 we want to listen on is now separate from binding to the ports
15176 - Building Tor with bufferevent support now requires Libevent
15177 2.0.13-stable or later. Previous versions of Libevent had bugs in
15178 SSL-related bufferevents and related issues that would make Tor
15179 work badly with bufferevents. Requiring 2.0.13-stable also allows
15180 Tor with bufferevents to take advantage of Libevent APIs
15181 introduced after 2.0.8-rc.
15184 Changes in version 0.2.2.32 - 2011-08-27
15185 The Tor 0.2.2 release series is dedicated to the memory of Andreas
15186 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
15187 a founder of the PETS community, a leader in our field, a mentor,
15188 and a friend. He left us with these words: "I had the possibility
15189 to contribute to this world that is not as it should be. I hope I
15190 could help in some areas to make the world a better place, and that
15191 I could also encourage other people to be engaged in improving the
15192 world. Please, stay engaged. This world needs you, your love, your
15193 initiative -- now I cannot be part of that anymore."
15195 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
15196 ready. More than two years in the making, this release features improved
15197 client performance and hidden service reliability, better compatibility
15198 for Android, correct behavior for bridges that listen on more than
15199 one address, more extensible and flexible directory object handling,
15200 better reporting of network statistics, improved code security, and
15201 many many other features and bugfixes.
15204 Changes in version 0.2.2.31-rc - 2011-08-17
15205 Tor 0.2.2.31-rc is the second and hopefully final release candidate
15206 for the Tor 0.2.2.x series.
15209 - Remove an extra pair of quotation marks around the error
15210 message in control-port STATUS_GENERAL BUG events. Bugfix on
15211 0.1.2.6-alpha; fixes bug 3732.
15212 - If we're configured to write our ControlPorts to disk, only write
15213 them after switching UID and creating the data directory. This way,
15214 we don't fail when starting up with a nonexistent DataDirectory
15215 and a ControlPortWriteToFile setting based on that directory. Fixes
15216 bug 3747; bugfix on Tor 0.2.2.26-beta.
15219 - Update to the August 2 2011 Maxmind GeoLite Country database.
15222 - Allow GETINFO fingerprint to return a fingerprint even when
15223 we have not yet built a router descriptor. Fixes bug 3577;
15224 bugfix on 0.2.0.1-alpha.
15225 - Write several files in text mode, on OSes that distinguish text
15226 mode from binary mode (namely, Windows). These files are:
15227 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
15228 that collect those statistics; 'client_keys' and 'hostname' for
15229 hidden services that use authentication; and (in the tor-gencert
15230 utility) newly generated identity and signing keys. Previously,
15231 we wouldn't specify text mode or binary mode, leading to an
15232 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
15233 the DirRecordUsageByCountry option which would have triggered
15234 the assertion failure was added), although this assertion failure
15235 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
15236 - Selectively disable deprecation warnings on OS X because Lion
15237 started deprecating the shipped copy of openssl. Fixes bug 3643.
15238 - When unable to format an address as a string, report its value
15239 as "???" rather than reusing the last formatted address. Bugfix
15243 Changes in version 0.2.3.2-alpha - 2011-07-18
15244 Tor 0.2.3.2-alpha introduces two new experimental features:
15245 microdescriptors and pluggable transports. It also continues cleaning
15246 up a variety of recently introduced features.
15249 - Clients can now use microdescriptors instead of regular descriptors
15250 to build circuits. Microdescriptors are authority-generated
15251 summaries of regular descriptors' contents, designed to change
15252 very rarely (see proposal 158 for details). This feature is
15253 designed to save bandwidth, especially for clients on slow internet
15254 connections. It's off by default for now, since nearly no caches
15255 support it, but it will be on-by-default for clients in a future
15256 version. You can use the UseMicrodescriptors option to turn it on.
15257 - Tor clients using bridges can now be configured to use a separate
15258 'transport' proxy for each bridge. This approach helps to resist
15259 censorship by allowing bridges to use protocol obfuscation
15260 plugins. It implements part of proposal 180. Implements ticket 2841.
15261 - While we're trying to bootstrap, record how many TLS connections
15262 fail in each state, and report which states saw the most failures
15263 in response to any bootstrap failures. This feature may speed up
15264 diagnosis of censorship events. Implements ticket 3116.
15266 o Major bugfixes (on 0.2.3.1-alpha):
15267 - When configuring a large set of nodes in EntryNodes (as with
15268 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
15269 random subset to be guards, and choose them in random
15270 order. Fixes bug 2798.
15271 - Tor could crash when remembering a consensus in a non-used consensus
15272 flavor without having a current consensus set. Fixes bug 3361.
15273 - Comparing an unknown address to a microdescriptor's shortened exit
15274 policy would always give a "rejected" result. Fixes bug 3599.
15275 - Using microdescriptors as a client no longer prevents Tor from
15276 uploading and downloading hidden service descriptors. Fixes
15280 - Allow nameservers with IPv6 address. Resolves bug 2574.
15281 - Accept attempts to include a password authenticator in the
15282 handshake, as supported by SOCKS5. This handles SOCKS clients that
15283 don't know how to omit a password when authenticating. Resolves
15285 - When configuring a large set of nodes in EntryNodes, and there are
15286 enough of them listed as Guard so that we don't need to consider
15287 the non-guard entries, prefer the ones listed with the Guard flag.
15288 - Check for and recover from inconsistency in the microdescriptor
15289 cache. This will make it harder for us to accidentally free a
15290 microdescriptor without removing it from the appropriate data
15291 structures. Fixes issue 3135; issue noted by "wanoskarnet".
15292 - Log SSL state transitions at log level DEBUG, log domain
15293 HANDSHAKE. This can be useful for debugging censorship events.
15294 Implements ticket 3264.
15295 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
15296 implements ticket 3439.
15298 o Minor bugfixes (on 0.2.3.1-alpha):
15299 - Do not free all general-purpose regular descriptors just
15300 because microdescriptor use is enabled. Fixes bug 3113.
15301 - Correctly link libevent_openssl when --enable-static-libevent
15302 is passed to configure. Fixes bug 3118.
15303 - Bridges should not complain during their heartbeat log messages that
15304 they are unlisted in the consensus: that's more or less the point
15305 of being a bridge. Fixes bug 3183.
15306 - Report a SIGNAL event to controllers when acting on a delayed
15307 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
15308 event to the controller if we acted on a SIGNAL NEWNYM command
15309 immediately, and otherwise not report a SIGNAL event for the
15310 command at all. Fixes bug 3349.
15311 - Fix a crash when handling the SIGNAL controller command or
15312 reporting ERR-level status events with bufferevents enabled. Found
15313 by Robert Ransom. Fixes bug 3367.
15314 - Always ship the tor-fw-helper manpage in our release tarballs.
15315 Fixes bug 3389. Reported by Stephen Walker.
15316 - Fix a class of double-mark-for-close bugs when bufferevents
15317 are enabled. Fixes bug 3403.
15318 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
15319 - Add SIGNAL to the list returned by the 'GETINFO events/names'
15320 control-port command. Fixes part of bug 3465.
15321 - Prevent using negative indices during unit test runs when read_all()
15322 fails. Spotted by coverity.
15323 - Fix a rare memory leak when checking the nodelist without it being
15324 present. Found by coverity.
15325 - Only try to download a microdescriptor-flavored consensus from
15326 a directory cache that provides them.
15328 o Minor bugfixes (on 0.2.2.x and earlier):
15329 - Assert that hidden-service-related operations are not performed
15330 using single-hop circuits. Previously, Tor would assert that
15331 client-side streams are not attached to single-hop circuits,
15332 but not that other sensitive operations on the client and service
15333 side are not performed using single-hop circuits. Fixes bug 3332;
15335 - Don't publish a new relay descriptor when we reload our onion key,
15336 unless the onion key has actually changed. Fixes bug 3263 and
15337 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
15338 - Allow GETINFO fingerprint to return a fingerprint even when
15339 we have not yet built a router descriptor. Fixes bug 3577;
15340 bugfix on 0.2.0.1-alpha.
15341 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
15342 on 0.2.2.4-alpha; fixes bug 3427.
15344 o Code simplification and refactoring:
15345 - Use tor_sscanf() in place of scanf() in more places through the
15346 code. This makes us a little more locale-independent, and
15347 should help shut up code-analysis tools that can't tell
15348 a safe sscanf string from a dangerous one.
15349 - Use tt_assert(), not tor_assert(), for checking for test failures.
15350 This makes the unit tests more able to go on in the event that
15352 - Split connection_about_to_close() into separate functions for each
15356 - On Windows, we now define the _WIN32_WINNT macros only if they
15357 are not already defined. This lets the person building Tor decide,
15358 if they want, to require a later version of Windows.
15361 Changes in version 0.2.2.30-rc - 2011-07-07
15362 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
15363 series. It fixes a few smaller bugs, but generally appears stable.
15364 Please test it and let us know whether it is!
15367 - Send a SUCCEEDED stream event to the controller when a reverse
15368 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
15369 discovered by katmagic.
15370 - Always NUL-terminate the sun_path field of a sockaddr_un before
15371 passing it to the kernel. (Not a security issue: kernels are
15372 smart enough to reject bad sockaddr_uns.) Found by Coverity;
15373 CID #428. Bugfix on Tor 0.2.0.3-alpha.
15374 - Don't stack-allocate the list of supplementary GIDs when we're
15375 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
15376 could take up to 256K, which is way too much stack. Found by
15377 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
15378 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
15379 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
15380 fixes part of bug 3465.
15381 - Fix a memory leak when receiving a descriptor for a hidden
15382 service we didn't ask for. Found by Coverity; CID #30. Bugfix
15386 - Update to the July 1 2011 Maxmind GeoLite Country database.
15389 Changes in version 0.2.2.29-beta - 2011-06-20
15390 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
15391 have bridge lines in their torrc but don't want to use them; gets
15392 us closer to having the control socket feature working on Debian;
15393 and fixes a variety of smaller bugs.
15396 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
15397 When we changed the default behavior to "use bridges if any
15398 are listed in the torrc", we surprised users who had bridges
15399 in their torrc files but who didn't actually want to use them.
15400 Partial resolution for bug 3354.
15403 - Don't attach new streams to old rendezvous circuits after SIGNAL
15404 NEWNYM. Previously, we would keep using an existing rendezvous
15405 circuit if it remained open (i.e. if it were kept open by a
15406 long-lived stream, or if a new stream were attached to it before
15407 Tor could notice that it was old and no longer in use). Bugfix on
15408 0.1.1.15-rc; fixes bug 3375.
15411 - Fix a bug when using ControlSocketsGroupWritable with User. The
15412 directory's group would be checked against the current group, not
15413 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
15414 bugfix on 0.2.2.26-beta.
15415 - Make connection_printf_to_buf()'s behavior sane. Its callers
15416 expect it to emit a CRLF iff the format string ends with CRLF;
15417 it actually emitted a CRLF iff (a) the format string ended with
15418 CRLF or (b) the resulting string was over 1023 characters long or
15419 (c) the format string did not end with CRLF *and* the resulting
15420 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
15421 fixes part of bug 3407.
15422 - Make send_control_event_impl()'s behavior sane. Its callers
15423 expect it to always emit a CRLF at the end of the string; it
15424 might have emitted extra control characters as well. Bugfix on
15425 0.1.1.9-alpha; fixes another part of bug 3407.
15426 - Make crypto_rand_int() check the value of its input correctly.
15427 Previously, it accepted values up to UINT_MAX, but could return a
15428 negative number if given a value above INT_MAX+1. Found by George
15429 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
15430 - Avoid a segfault when reading a malformed circuit build state
15431 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
15433 - When asked about a DNS record type we don't support via a
15434 client DNSPort, reply with NOTIMPL rather than an empty
15435 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
15436 - Fix a rare memory leak during stats writing. Found by coverity.
15439 - Update to the June 1 2011 Maxmind GeoLite Country database.
15441 o Code simplifications and refactoring:
15442 - Remove some dead code as indicated by coverity.
15443 - Remove a few dead assignments during router parsing. Found by
15445 - Add some forgotten return value checks during unit tests. Found
15447 - Don't use 1-bit wide signed bit fields. Found by coverity.
15450 Changes in version 0.2.2.28-beta - 2011-06-04
15451 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
15452 fixed a big bug in whether relays stay in the consensus consistently,
15453 we moved closer to handling bridges and hidden services correctly,
15454 and we started the process of better handling the dreaded "my Vidalia
15455 died, and now my Tor demands a password when I try to reconnect to it"
15459 - Don't decide to make a new descriptor when receiving a HUP signal.
15460 This bug has caused a lot of 0.2.2.x relays to disappear from the
15461 consensus periodically. Fixes the most common case of triggering
15462 bug 1810; bugfix on 0.2.2.7-alpha.
15463 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
15464 - Don't try to build descriptors if "ORPort auto" is set and we
15465 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
15467 - Resolve a crash that occurred when setting BridgeRelay to 1 with
15468 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
15469 - Apply circuit timeouts to opened hidden-service-related circuits
15470 based on the correct start time. Previously, we would apply the
15471 circuit build timeout based on time since the circuit's creation;
15472 it was supposed to be applied based on time since the circuit
15473 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
15474 - Use the same circuit timeout for client-side introduction
15475 circuits as for other four-hop circuits, rather than the timeout
15476 for single-hop directory-fetch circuits; the shorter timeout may
15477 have been appropriate with the static circuit build timeout in
15478 0.2.1.x and earlier, but caused many hidden service access attempts
15479 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
15480 on 0.2.2.2-alpha; fixes another part of bug 1297.
15481 - In ticket 2511 we fixed a case where you could use an unconfigured
15482 bridge if you had configured it as a bridge the last time you ran
15483 Tor. Now fix another edge case: if you had configured it as a bridge
15484 but then switched to a different bridge via the controller, you
15485 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
15489 - Add an __OwningControllerProcess configuration option and a
15490 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
15491 that when it exits, Tor will shut down. Implements feature 3049.
15492 - If "UseBridges 1" is set and no bridges are configured, Tor will
15493 now refuse to build any circuits until some bridges are set.
15494 If "UseBridges auto" is set, Tor will use bridges if they are
15495 configured and we are not running as a server, but otherwise will
15496 make circuits as usual. The new default is "auto". Patch by anonym,
15497 so the Tails LiveCD can stop automatically revealing you as a Tor
15501 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
15502 - Remove a trailing asterisk from "exit-policy/default" in the
15503 output of the control port command "GETINFO info/names". Bugfix
15505 - Use a wide type to hold sockets when built for 64-bit Windows builds.
15507 - Warn when the user configures two HiddenServiceDir lines that point
15508 to the same directory. Bugfix on 0.0.6 (the version introducing
15509 HiddenServiceDir); fixes bug 3289.
15510 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
15511 part of bug 2748; bugfix on 0.2.0.10-alpha.
15512 - Log malformed requests for rendezvous descriptors as protocol
15513 warnings, not warnings. Also, use a more informative log message
15514 in case someone sees it at log level warning without prior
15515 info-level messages. Fixes the other part of bug 2748; bugfix
15517 - Clear the table recording the time of the last request for each
15518 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
15519 Previously, we would clear our HS descriptor cache on SIGNAL
15520 NEWNYM, but if we had previously retrieved a descriptor (or tried
15521 to) from every directory responsible for it, we would refuse to
15522 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
15524 - Fix a log message that said "bits" while displaying a value in
15525 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
15527 - When checking for 1024-bit keys, check for 1024 bits, not 128
15528 bytes. This allows Tor to correctly discard keys of length 1017
15529 through 1023. Bugfix on 0.0.9pre5.
15532 - Relays now log the reason for publishing a new relay descriptor,
15533 so we have a better chance of hunting down instances of bug 1810.
15534 Resolves ticket 3252.
15535 - Revise most log messages that refer to nodes by nickname to
15536 instead use the "$key=nickname at address" format. This should be
15537 more useful, especially since nicknames are less and less likely
15538 to be unique. Resolves ticket 3045.
15539 - Log (at info level) when purging pieces of hidden-service-client
15540 state because of SIGNAL NEWNYM.
15543 - Remove undocumented option "-F" from tor-resolve: it hasn't done
15544 anything since 0.2.1.16-rc.
15547 Changes in version 0.2.2.27-beta - 2011-05-18
15548 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
15549 release, and also adds a few more general bugfixes.
15552 - Fix a crash bug when changing bridges in a running Tor process.
15553 Fixes bug 3213; bugfix on 0.2.2.26-beta.
15554 - When the controller configures a new bridge, don't wait 10 to 60
15555 seconds before trying to fetch its descriptor. Bugfix on
15556 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
15559 - Require that onion keys have exponent 65537 in microdescriptors too.
15560 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
15561 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
15562 Changed the limit to 512 characters by removing base64 newlines.
15563 Fixes bug 2752. Fix by Michael Yakubovich.
15564 - When a client starts or stops using bridges, never use a circuit
15565 that was built before the configuration change. This behavior could
15566 put at risk a user who uses bridges to ensure that her traffic
15567 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
15571 Changes in version 0.2.2.26-beta - 2011-05-17
15572 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
15573 also introduces a new "socksport auto" approach that should make it
15574 easier to run multiple Tors on the same system, and does a lot of
15575 cleanup to get us closer to a release candidate.
15577 o Security/privacy fixes:
15578 - Replace all potentially sensitive memory comparison operations
15579 with versions whose runtime does not depend on the data being
15580 compared. This will help resist a class of attacks where an
15581 adversary can use variations in timing information to learn
15582 sensitive data. Fix for one case of bug 3122. (Safe memcmp
15583 implementation by Robert Ransom based partially on code by DJB.)
15584 - When receiving a hidden service descriptor, check that it is for
15585 the hidden service we wanted. Previously, Tor would store any
15586 hidden service descriptors that a directory gave it, whether it
15587 wanted them or not. This wouldn't have let an attacker impersonate
15588 a hidden service, but it did let directories pre-seed a client
15589 with descriptors that it didn't want. Bugfix on 0.0.6.
15590 - On SIGHUP, do not clear out all TrackHostExits mappings, client
15591 DNS cache entries, and virtual address mappings: that's what
15592 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
15595 - The options SocksPort, ControlPort, and so on now all accept a
15596 value "auto" that opens a socket on an OS-selected port. A
15597 new ControlPortWriteToFile option tells Tor to write its
15598 actual control port or ports to a chosen file. If the option
15599 ControlPortFileGroupReadable is set, the file is created as
15600 group-readable. Now users can run two Tor clients on the same
15601 system without needing to manually mess with parameters. Resolves
15602 part of ticket 3076.
15603 - Set SO_REUSEADDR on all sockets, not just listeners. This should
15604 help busy exit nodes avoid running out of useable ports just
15605 because all the ports have been used in the near past. Resolves
15609 - New "GETINFO net/listeners/(type)" controller command to return
15610 a list of addresses and ports that are bound for listeners for a
15611 given connection type. This is useful when the user has configured
15612 "SocksPort auto" and the controller needs to know which port got
15613 chosen. Resolves another part of ticket 3076.
15614 - Add a new ControlSocketsGroupWritable configuration option: when
15615 it is turned on, ControlSockets are group-writeable by the default
15616 group of the current user. Patch by Jérémy Bobbio; implements
15618 - Tor now refuses to create a ControlSocket in a directory that is
15619 world-readable (or group-readable if ControlSocketsGroupWritable
15620 is 0). This is necessary because some operating systems do not
15621 enforce permissions on an AF_UNIX sockets. Permissions on the
15622 directory holding the socket, however, seems to work everywhere.
15623 - Rate-limit a warning about failures to download v2 networkstatus
15624 documents. Resolves part of bug 1352.
15625 - Backport code from 0.2.3.x that allows directory authorities to
15626 clean their microdescriptor caches. Needed to resolve bug 2230.
15627 - When an HTTPS proxy reports "403 Forbidden", we now explain
15628 what it means rather than calling it an unexpected status code.
15629 Closes bug 2503. Patch from Michael Yakubovich.
15630 - Update to the May 1 2011 Maxmind GeoLite Country database.
15633 - Authorities now clean their microdesc cache periodically and when
15634 reading from disk initially, not only when adding new descriptors.
15635 This prevents a bug where we could lose microdescriptors. Bugfix
15636 on 0.2.2.6-alpha. Fixes bug 2230.
15637 - Do not crash when our configuration file becomes unreadable, for
15638 example due to a permissions change, between when we start up
15639 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
15641 - Avoid a bug that would keep us from replacing a microdescriptor
15642 cache on Windows. (We would try to replace the file while still
15643 holding it open. That's fine on Unix, but Windows doesn't let us
15644 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
15645 - Add missing explanations for the authority-related torrc options
15646 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
15647 man page. Resolves issue 2379.
15648 - As an authority, do not upload our own vote or signature set to
15649 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
15650 it would get flagged as a duplicate. Resolves bug 3026.
15651 - Accept hidden service descriptors if we think we might be a hidden
15652 service directory, regardless of what our consensus says. This
15653 helps robustness, since clients and hidden services can sometimes
15654 have a more up-to-date view of the network consensus than we do,
15655 and if they think that the directory authorities list us a HSDir,
15656 we might actually be one. Related to bug 2732; bugfix on
15658 - When a controller changes TrackHostExits, remove mappings for
15659 hosts that should no longer have their exits tracked. Bugfix on
15661 - When a controller changes VirtualAddrNetwork, remove any mappings
15662 for hosts that were automapped to the old network. Bugfix on
15664 - When a controller changes one of the AutomapHosts* options, remove
15665 any mappings for hosts that should no longer be automapped. Bugfix
15667 - Do not reset the bridge descriptor download status every time we
15668 re-parse our configuration or get a configuration change. Fixes
15669 bug 3019; bugfix on 0.2.0.3-alpha.
15671 o Minor bugfixes (code cleanup):
15672 - When loading the microdesc journal, remember its current size.
15673 In 0.2.2, this helps prevent the microdesc journal from growing
15674 without limit on authorities (who are the only ones to use it in
15675 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
15676 Fix posted by "cypherpunks."
15677 - The microdesc journal is supposed to get rebuilt only if it is
15678 at least _half_ the length of the store, not _twice_ the length
15679 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
15680 - Fix a potential null-pointer dereference while computing a
15681 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
15683 - Avoid a possible null-pointer dereference when rebuilding the mdesc
15684 cache without actually having any descriptors to cache. Bugfix on
15685 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
15686 - If we fail to compute the identity digest of a v3 legacy keypair,
15687 warn, and don't use a buffer-full of junk instead. Bugfix on
15688 0.2.1.1-alpha; fixes bug 3106.
15689 - Resolve an untriggerable issue in smartlist_string_num_isin(),
15690 where if the function had ever in the future been used to check
15691 for the presence of a too-large number, it would have given an
15692 incorrect result. (Fortunately, we only used it for 16-bit
15693 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
15694 - Require that introduction point keys and onion handshake keys
15695 have a public exponent of 65537. Starts to fix bug 3207; bugfix
15698 o Removed features:
15699 - Caches no longer download and serve v2 networkstatus documents
15700 unless FetchV2Networkstatus flag is set: these documents haven't
15701 haven't been used by clients or relays since 0.2.0.x. Resolves
15705 Changes in version 0.2.3.1-alpha - 2011-05-05
15706 Tor 0.2.3.1-alpha adds some new experimental features, including support
15707 for an improved network IO backend, IOCP networking on Windows,
15708 microdescriptor caching, "fast-start" support for streams, and automatic
15709 home router configuration. There are also numerous internal improvements
15710 to try to make the code easier for developers to work with.
15712 This is the first alpha release in a new series, so expect there to be
15713 bugs. Users who would rather test out a more stable branch should
15714 stay with 0.2.2.x for now.
15717 - Tor can now optionally build with the "bufferevents" buffered IO
15718 backend provided by Libevent 2. To use this feature, make sure you
15719 have the latest possible version of Libevent, and pass the
15720 --enable-bufferevents flag to configure when building Tor from
15721 source. This feature will make our networking code more flexible,
15722 let us stack layers on each other, and let us use more efficient
15723 zero-copy transports where available.
15724 - As an experimental feature, Tor can use IOCP for networking on Windows.
15725 Once this code is tuned and optimized, it promises much better
15726 performance than the select-based backend we've used in the past. To
15727 try this feature, you must build Tor with Libevent 2, configure Tor
15728 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
15729 your torrc. There are known bugs here: only try this if you can help
15730 debug it as it breaks.
15731 - The EntryNodes option can now include country codes like {de} or IP
15732 addresses or network masks. Previously we had disallowed these options
15733 because we didn't have an efficient way to keep the list up to
15734 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
15735 - Exit nodes now accept and queue data on not-yet-connected streams.
15736 Previously, the client wasn't allowed to send data until the stream was
15737 connected, which slowed down all connections. This change will enable
15738 clients to perform a "fast-start" on streams and send data without
15739 having to wait for a confirmation that the stream has opened. (Patch
15740 from Ian Goldberg; implements the server side of Proposal 174.)
15741 - Tor now has initial support for automatic port mapping on the many
15742 home routers that support NAT-PMP or UPnP. (Not yet supported on
15743 Windows). To build the support code, you'll need to have libnatpnp
15744 library and/or the libminiupnpc library, and you'll need to enable the
15745 feature specifically by passing "--enable-upnp" and/or
15746 "--enable-natpnp" to configure. To turn it on, use the new
15747 PortForwarding option.
15748 - Caches now download, cache, and serve multiple "flavors" of the
15749 consensus, including a flavor that describes microdescriptors.
15750 - Caches now download, cache, and serve microdescriptors -- small
15751 summaries of router descriptors that are authenticated by all of the
15752 directory authorities. Once enough caches are running this code,
15753 clients will be able to save significant amounts of directory bandwidth
15754 by downloading microdescriptors instead of router descriptors.
15757 - Make logging resolution configurable with a new LogTimeGranularity
15758 option, and change the default from 1 millisecond to 1 second.
15759 Implements enhancement 1668.
15760 - We log which torrc file we're using on startup. Implements ticket
15762 - Ordinarily, Tor does not count traffic from private addresses (like
15763 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
15764 There is now a new option, CountPrivateBandwidth, to disable this
15765 behavior. Patch from Daniel Cagara.
15766 - New --enable-static-tor configure option for building Tor as
15767 statically as possible. Idea, general hackery and thoughts from
15768 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
15770 - If you set the NumCPUs option to 0, Tor will now try to detect how
15771 many CPUs you have. This is the new default behavior.
15772 - Turn on directory request statistics by default and include them in
15773 extra-info descriptors. Don't break if we have no GeoIP database.
15774 - Relays that set "ConnDirectionStatistics 1" write statistics on the
15775 bidirectional use of connections to disk every 24 hours.
15776 - Add a GeoIP file digest to the extra-info descriptor. Implements
15778 - The NodeFamily option -- which let you declare that you want to
15779 consider nodes to be part of a family whether they list themselves
15780 that way or not -- now allows IP address ranges and country codes.
15781 - Add a new 'Heartbeat' log message type to periodically log a message
15782 describing Tor's status at level Notice. This feature is meant for
15783 operators who log at notice, and want to make sure that their Tor
15784 server is still working. Implementation by George Kadianakis.
15786 o Minor bugfixes (on 0.2.2.25-alpha):
15787 - When loading the microdesc journal, remember its current size.
15788 In 0.2.2, this helps prevent the microdesc journal from growing
15789 without limit on authorities (who are the only ones to use it in
15790 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
15791 Fix posted by "cypherpunks."
15792 - The microdesc journal is supposed to get rebuilt only if it is
15793 at least _half_ the length of the store, not _twice_ the length
15794 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
15795 - If as an authority we fail to compute the identity digest of a v3
15796 legacy keypair, warn, and don't use a buffer-full of junk instead.
15797 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
15798 - Authorities now clean their microdesc cache periodically and when
15799 reading from disk initially, not only when adding new descriptors.
15800 This prevents a bug where we could lose microdescriptors. Bugfix
15803 o Minor features (controller):
15804 - Add a new SIGNAL event to the controller interface so that
15805 controllers can be notified when Tor handles a signal. Resolves
15806 issue 1955. Patch by John Brooks.
15807 - Add a new GETINFO option to get total bytes read and written. Patch
15808 from pipe, revised by atagar. Resolves ticket 2345.
15809 - Implement some GETINFO controller fields to provide information about
15810 the Tor process's pid, euid, username, and resource limits.
15813 - Our build system requires automake 1.6 or later to create the
15814 Makefile.in files. Previously, you could have used 1.4.
15815 This only affects developers and people building Tor from git;
15816 people who build Tor from the source distribution without changing
15817 the Makefile.am files should be fine.
15818 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
15819 so on. This is more robust against some of the failure modes
15820 associated with running the autotools pieces on their own.
15822 o Minor packaging issues:
15823 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
15824 already created. Patch from Andreas Stieger. Fixes bug 2573.
15826 o Code simplifications and refactoring:
15827 - A major revision to our internal node-selecting and listing logic.
15828 Tor already had at least two major ways to look at the question of
15829 "which Tor servers do we know about": a list of router descriptors,
15830 and a list of entries in the current consensus. With
15831 microdescriptors, we're adding a third. Having so many systems
15832 without an abstraction layer over them was hurting the codebase.
15833 Now, we have a new "node_t" abstraction that presents a consistent
15834 interface to a client's view of a Tor node, and holds (nearly) all
15835 of the mutable state formerly in routerinfo_t and routerstatus_t.
15836 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
15837 no longer link against Libevent: they never used it, but
15838 our library structure used to force them to link it.
15840 o Removed features:
15841 - Remove some old code to work around even older versions of Tor that
15842 used forked processes to handle DNS requests. Such versions of Tor
15843 are no longer in use as servers.
15845 o Documentation fixes:
15846 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
15847 - Add missing documentation for the authority-related torrc options
15848 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
15852 Changes in version 0.2.2.25-alpha - 2011-04-29
15853 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
15854 robust, routers no longer overreport their bandwidth, Win7 should crash
15855 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
15856 now prevents hidden service-related activity from being linkable. It
15857 provides more information to Vidalia so you can see if your bridge is
15858 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
15859 StrictNodes configuration options to make them more reliable, more
15860 understandable, and more regularly applied. If you use those options,
15861 please see the revised documentation for them in the manual page.
15864 - Relays were publishing grossly inflated bandwidth values because
15865 they were writing their state files wrong--now they write the
15866 correct value. Also, resume reading bandwidth history from the
15867 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
15868 - Improve hidden service robustness: When we find that we have
15869 extended a hidden service's introduction circuit to a relay not
15870 listed as an introduction point in the HS descriptor we currently
15871 have, retry with an introduction point from the current
15872 descriptor. Previously we would just give up. Fixes bugs 1024 and
15873 1930; bugfix on 0.2.0.10-alpha.
15874 - Clients now stop trying to use an exit node associated with a given
15875 destination by TrackHostExits if they fail to reach that exit node.
15876 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
15877 - Fix crash bug on platforms where gmtime and localtime can return
15878 NULL. Windows 7 users were running into this one. Fixes part of bug
15879 2077. Bugfix on all versions of Tor. Found by boboper.
15881 o Security and stability fixes:
15882 - Don't double-free a parsable, but invalid, microdescriptor, even if
15883 it is followed in the blob we're parsing by an unparsable
15884 microdescriptor. Fixes an issue reported in a comment on bug 2954.
15885 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
15886 - If the Nickname configuration option isn't given, Tor would pick a
15887 nickname based on the local hostname as the nickname for a relay.
15888 Because nicknames are not very important in today's Tor and the
15889 "Unnamed" nickname has been implemented, this is now problematic
15890 behavior: It leaks information about the hostname without being
15891 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
15892 introduced the Unnamed nickname. Reported by tagnaq.
15893 - Fix an uncommon assertion failure when running with DNSPort under
15894 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
15895 - Avoid linkability based on cached hidden service descriptors: forget
15896 all hidden service descriptors cached as a client when processing a
15897 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
15900 - Export GeoIP information on bridge usage to controllers even if we
15901 have not yet been running for 24 hours. Now Vidalia bridge operators
15902 can get more accurate and immediate feedback about their
15903 contributions to the network.
15905 o Major features and bugfixes (node selection):
15906 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
15907 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
15908 options. Previously, we had been ambiguous in describing what
15909 counted as an "exit" node, and what operations exactly "StrictNodes
15910 0" would permit. This created confusion when people saw nodes built
15911 through unexpected circuits, and made it hard to tell real bugs from
15912 surprises. Now the intended behavior is:
15913 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
15914 a node that delivers user traffic outside the Tor network.
15915 . "Entry", in the context of EntryNodes, means a node used as the
15916 first hop of a multihop circuit. It doesn't include direct
15917 connections to directory servers.
15918 . "ExcludeNodes" applies to all nodes.
15919 . "StrictNodes" changes the behavior of ExcludeNodes only. When
15920 StrictNodes is set, Tor should avoid all nodes listed in
15921 ExcludeNodes, even when it will make user requests fail. When
15922 StrictNodes is *not* set, then Tor should follow ExcludeNodes
15923 whenever it can, except when it must use an excluded node to
15924 perform self-tests, connect to a hidden service, provide a
15925 hidden service, fulfill a .exit request, upload directory
15926 information, or fetch directory information.
15927 Collectively, the changes to implement the behavior fix bug 1090.
15928 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
15929 a node is listed in both, it's treated as excluded.
15930 - ExcludeNodes now applies to directory nodes -- as a preference if
15931 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
15932 Don't exclude all the directory authorities and set StrictNodes to 1
15933 unless you really want your Tor to break.
15934 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
15935 - ExcludeExitNodes now overrides .exit requests.
15936 - We don't use bridges listed in ExcludeNodes.
15937 - When StrictNodes is 1:
15938 . We now apply ExcludeNodes to hidden service introduction points
15939 and to rendezvous points selected by hidden service users. This
15940 can make your hidden service less reliable: use it with caution!
15941 . If we have used ExcludeNodes on ourself, do not try relay
15942 reachability self-tests.
15943 . If we have excluded all the directory authorities, we will not
15944 even try to upload our descriptor if we're a relay.
15945 . Do not honor .exit requests to an excluded node.
15946 - Remove a misfeature that caused us to ignore the Fast/Stable flags
15947 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
15948 - When the set of permitted nodes changes, we now remove any mappings
15949 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
15951 - We never cannibalize a circuit that had excluded nodes on it, even
15952 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
15953 - Revert a change where we would be laxer about attaching streams to
15954 circuits than when building the circuits. This was meant to prevent
15955 a set of bugs where streams were never attachable, but our improved
15956 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
15957 - Keep track of how many times we launch a new circuit to handle a
15958 given stream. Too many launches could indicate an inconsistency
15959 between our "launch a circuit to handle this stream" logic and our
15960 "attach this stream to one of the available circuits" logic.
15961 - Improve log messages related to excluded nodes.
15964 - Fix a spurious warning when moving from a short month to a long
15965 month on relays with month-based BandwidthAccounting. Bugfix on
15966 0.2.2.17-alpha; fixes bug 3020.
15967 - When a client finds that an origin circuit has run out of 16-bit
15968 stream IDs, we now mark it as unusable for new streams. Previously,
15969 we would try to close the entire circuit. Bugfix on 0.0.6.
15970 - Add a forgotten cast that caused a compile warning on OS X 10.6.
15971 Bugfix on 0.2.2.24-alpha.
15972 - Be more careful about reporting the correct error from a failed
15973 connect() system call. Under some circumstances, it was possible to
15974 look at an incorrect value for errno when sending the end reason.
15975 Bugfix on 0.1.0.1-rc.
15976 - Correctly handle an "impossible" overflow cases in connection byte
15977 counting, where we write or read more than 4GB on an edge connection
15978 in a single second. Bugfix on 0.1.2.8-beta.
15979 - Correct the warning displayed when a rendezvous descriptor exceeds
15980 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
15982 - Clients and hidden services now use HSDir-flagged relays for hidden
15983 service descriptor downloads and uploads even if the relays have no
15984 DirPort set and the client has disabled TunnelDirConns. This will
15985 eventually allow us to give the HSDir flag to relays with no
15986 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
15987 - Downgrade "no current certificates known for authority" message from
15988 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
15989 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
15990 2917. Bugfix on 0.1.1.1-alpha.
15991 - Only limit the lengths of single HS descriptors, even when multiple
15992 HS descriptors are published to an HSDir relay in a single POST
15993 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
15994 - Write the current time into the LastWritten line in our state file,
15995 rather than the time from the previous write attempt. Also, stop
15996 trying to use a time of -1 in our log statements. Fixes bug 3039;
15997 bugfix on 0.2.2.14-alpha.
15998 - Be more consistent in our treatment of file system paths. "~" should
15999 get expanded to the user's home directory in the Log config option.
16000 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
16001 feature for the -f and --DataDirectory options.
16004 - Make sure every relay writes a state file at least every 12 hours.
16005 Previously, a relay could go for weeks without writing its state
16006 file, and on a crash could lose its bandwidth history, capacity
16007 estimates, client country statistics, and so on. Addresses bug 3012.
16008 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
16009 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
16010 clients are already deprecated because of security bugs.
16011 - Don't allow v0 hidden service authorities to act as clients.
16012 Required by fix for bug 3000.
16013 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
16014 by fix for bug 3000.
16015 - Ensure that no empty [dirreq-](read|write)-history lines are added
16016 to an extrainfo document. Implements ticket 2497.
16018 o Code simplification and refactoring:
16019 - Remove workaround code to handle directory responses from servers
16020 that had bug 539 (they would send HTTP status 503 responses _and_
16021 send a body too). Since only server versions before
16022 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
16023 keep the workaround in place.
16024 - Remove the old 'fuzzy time' logic. It was supposed to be used for
16025 handling calculations where we have a known amount of clock skew and
16026 an allowed amount of unknown skew. But we only used it in three
16027 places, and we never adjusted the known/unknown skew values. This is
16028 still something we might want to do someday, but if we do, we'll
16029 want to do it differently.
16030 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
16031 None of the cases where we did this before were wrong, but by making
16032 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
16033 - Use GetTempDir to find the proper temporary directory location on
16034 Windows when generating temporary files for the unit tests. Patch by
16038 Changes in version 0.2.2.24-alpha - 2011-04-08
16039 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
16040 prevented Tor clients from effectively using "multihomed" bridges,
16041 that is, bridges that listen on multiple ports or IP addresses so users
16042 can continue to use some of their addresses even if others get blocked.
16045 - Fix a bug where bridge users who configure the non-canonical
16046 address of a bridge automatically switch to its canonical
16047 address. If a bridge listens at more than one address, it should be
16048 able to advertise those addresses independently and any non-blocked
16049 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
16051 - If you configured Tor to use bridge A, and then quit and
16052 configured Tor to use bridge B instead, it would happily continue
16053 to use bridge A if it's still reachable. While this behavior is
16054 a feature if your goal is connectivity, in some scenarios it's a
16055 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
16056 - Directory authorities now use data collected from their own
16057 uptime observations when choosing whether to assign the HSDir flag
16058 to relays, instead of trusting the uptime value the relay reports in
16059 its descriptor. This change helps prevent an attack where a small
16060 set of nodes with frequently-changing identity keys can blackhole
16061 a hidden service. (Only authorities need upgrade; others will be
16062 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
16065 - When we restart our relay, we might get a successful connection
16066 from the outside before we've started our reachability tests,
16067 triggering a warning: "ORPort found reachable, but I have no
16068 routerinfo yet. Failing to inform controller of success." This
16069 bug was harmless unless Tor is running under a controller
16070 like Vidalia, in which case the controller would never get a
16071 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
16073 - Make directory authorities more accurate at recording when
16074 relays that have failed several reachability tests became
16075 unreachable, so we can provide more accuracy at assigning Stable,
16076 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
16077 - Fix an issue that prevented static linking of libevent on
16078 some platforms (notably Linux). Fixes bug 2698; bugfix on
16079 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
16080 the --with-static-libevent configure option).
16081 - We now ask the other side of a stream (the client or the exit)
16082 for more data on that stream when the amount of queued data on
16083 that stream dips low enough. Previously, we wouldn't ask the
16084 other side for more data until either it sent us more data (which
16085 it wasn't supposed to do if it had exhausted its window!) or we
16086 had completely flushed all our queued data. This flow control fix
16087 should improve throughput. Fixes bug 2756; bugfix on the earliest
16088 released versions of Tor (svn commit r152).
16089 - Avoid a double-mark-for-free warning when failing to attach a
16090 transparent proxy connection. (We thought we had fixed this in
16091 0.2.2.23-alpha, but it turns out our fix was checking the wrong
16092 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
16093 bug) and 0.2.2.23-alpha (the incorrect fix).
16094 - When warning about missing zlib development packages during compile,
16095 give the correct package names. Bugfix on 0.2.0.1-alpha.
16098 - Directory authorities now log the source of a rejected POSTed v3
16099 networkstatus vote.
16100 - Make compilation with clang possible when using
16101 --enable-gcc-warnings by removing two warning options that clang
16102 hasn't implemented yet and by fixing a few warnings. Implements
16104 - When expiring circuits, use microsecond timers rather than
16105 one-second timers. This can avoid an unpleasant situation where a
16106 circuit is launched near the end of one second and expired right
16107 near the beginning of the next, and prevent fluctuations in circuit
16109 - Use computed circuit-build timeouts to decide when to launch
16110 parallel introduction circuits for hidden services. (Previously,
16111 we would retry after 15 seconds.)
16112 - Update to the April 1 2011 Maxmind GeoLite Country database.
16115 - Create the /var/run/tor directory on startup on OpenSUSE if it is
16116 not already created. Patch from Andreas Stieger. Fixes bug 2573.
16118 o Documentation changes:
16119 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
16120 - Resolve all doxygen warnings except those for missing documentation.
16122 - Add doxygen documentation for more functions, fields, and types.
16125 Changes in version 0.2.2.23-alpha - 2011-03-08
16126 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
16127 they restart they don't lose their bandwidth capacity estimate. This
16128 release also fixes a diverse set of user-facing bugs, ranging from
16129 relays overrunning their rate limiting to clients falsely warning about
16130 clock skew to bridge descriptor leaks by our bridge directory authority.
16133 - Stop sending a CLOCK_SKEW controller status event whenever
16134 we fetch directory information from a relay that has a wrong clock.
16135 Instead, only inform the controller when it's a trusted authority
16136 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
16137 the rest of bug 1074.
16138 - Fix an assert in parsing router descriptors containing IPv6
16139 addresses. This one took down the directory authorities when
16140 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
16141 - Make the bridge directory authority refuse to answer directory
16142 requests for "all" descriptors. It used to include bridge
16143 descriptors in its answer, which was a major information leak.
16144 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
16145 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
16146 Tor would ignore their RelayBandwidthBurst setting,
16147 potentially using more bandwidth than expected. Bugfix on
16148 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
16149 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
16150 hidserv" in her torrc. The 'hidserv' argument never controlled
16151 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
16154 - Relays now save observed peak bandwidth throughput rates to their
16155 state file (along with total usage, which was already saved)
16156 so that they can determine their correct estimated bandwidth on
16157 restart. Resolves bug 1863, where Tor relays would reset their
16158 estimated bandwidth to 0 after restarting.
16159 - Directory authorities now take changes in router IP address and
16160 ORPort into account when determining router stability. Previously,
16161 if a router changed its IP or ORPort, the authorities would not
16162 treat it as having any downtime for the purposes of stability
16163 calculation, whereas clients would experience downtime since the
16164 change could take a while to propagate to them. Resolves issue 1035.
16165 - Enable Address Space Layout Randomization (ASLR) and Data Execution
16166 Prevention (DEP) by default on Windows to make it harder for
16167 attackers to exploit vulnerabilities. Patch from John Brooks.
16169 o Minor bugfixes (on 0.2.1.x and earlier):
16170 - Fix a rare crash bug that could occur when a client was configured
16171 with a large number of bridges. Fixes bug 2629; bugfix on
16172 0.2.1.2-alpha. Bugfix by trac user "shitlei".
16173 - Avoid a double mark-for-free warning when failing to attach a
16174 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
16176 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
16177 found by "cypherpunks". This bug was introduced before the first
16178 Tor release, in svn commit r110.
16179 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
16180 don't mention them in the manpage. Fixes bug 2450; issue
16181 spotted by keb and G-Lo.
16182 - Fix a bug in bandwidth history state parsing that could have been
16183 triggered if a future version of Tor ever changed the timing
16184 granularity at which bandwidth history is measured. Bugfix on
16185 Tor 0.1.1.11-alpha.
16186 - When a relay decides that its DNS is too broken for it to serve
16187 as an exit server, it advertised itself as a non-exit, but
16188 continued to act as an exit. This could create accidental
16189 partitioning opportunities for users. Instead, if a relay is
16190 going to advertise reject *:* as its exit policy, it should
16191 really act with exit policy "reject *:*". Fixes bug 2366.
16192 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
16193 - In the special case where you configure a public exit relay as your
16194 bridge, Tor would be willing to use that exit relay as the last
16195 hop in your circuit as well. Now we fail that circuit instead.
16196 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
16197 - Fix a bug with our locking implementation on Windows that couldn't
16198 correctly detect when a file was already locked. Fixes bug 2504,
16199 bugfix on 0.2.1.6-alpha.
16200 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
16201 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
16203 - Set target port in get_interface_address6() correctly. Bugfix
16204 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
16205 - Directory authorities are now more robust to hops back in time
16206 when calculating router stability. Previously, if a run of uptime
16207 or downtime appeared to be negative, the calculation could give
16208 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
16210 - Fix an assert that got triggered when using the TestingTorNetwork
16211 configuration option and then issuing a GETINFO config-text control
16212 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
16214 o Minor bugfixes (on 0.2.2.x):
16215 - Clients should not weight BadExit nodes as Exits in their node
16216 selection. Similarly, directory authorities should not count BadExit
16217 bandwidth as Exit bandwidth when computing bandwidth-weights.
16218 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
16219 - Correctly clear our dir_read/dir_write history when there is an
16220 error parsing any bw history value from the state file. Bugfix on
16221 Tor 0.2.2.15-alpha.
16222 - Resolve a bug in verifying signatures of directory objects
16223 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
16224 Fixes bug 2409. Found by "piebeer".
16225 - Bridge authorities no longer crash on SIGHUP when they try to
16226 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
16230 - Log less aggressively about circuit timeout changes, and improve
16231 some other circuit timeout messages. Resolves bug 2004.
16232 - Log a little more clearly about the times at which we're no longer
16233 accepting new connections. Resolves bug 2181.
16234 - Reject attempts at the client side to open connections to private
16235 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
16236 a randomly chosen exit node. Attempts to do so are always
16237 ill-defined, generally prevented by exit policies, and usually
16238 in error. This will also help to detect loops in transparent
16239 proxy configurations. You can disable this feature by setting
16240 "ClientRejectInternalAddresses 0" in your torrc.
16241 - Always treat failure to allocate an RSA key as an unrecoverable
16243 - Update to the March 1 2011 Maxmind GeoLite Country database.
16245 o Minor features (log subsystem):
16246 - Add documentation for configuring logging at different severities in
16247 different log domains. We've had this feature since 0.2.1.1-alpha,
16248 but for some reason it never made it into the manpage. Fixes
16250 - Make it simpler to specify "All log domains except for A and B".
16251 Previously you needed to say "[*,~A,~B]". Now you can just say
16253 - Add a "LogMessageDomains 1" option to include the domains of log
16254 messages along with the messages. Without this, there's no way
16255 to use log domains without reading the source or doing a lot
16258 o Packaging changes:
16259 - Stop shipping the Tor specs files and development proposal documents
16260 in the tarball. They are now in a separate git repository at
16261 git://git.torproject.org/torspec.git
16264 Changes in version 0.2.1.30 - 2011-02-23
16265 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
16266 change is a slight tweak to Tor's TLS handshake that makes relays
16267 and bridges that run this new version reachable from Iran again.
16268 We don't expect this tweak will win the arms race long-term, but it
16269 buys us time until we roll out a better solution.
16272 - Stop sending a CLOCK_SKEW controller status event whenever
16273 we fetch directory information from a relay that has a wrong clock.
16274 Instead, only inform the controller when it's a trusted authority
16275 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
16276 the rest of bug 1074.
16277 - Fix a bounds-checking error that could allow an attacker to
16278 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
16279 Found by "piebeer".
16280 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
16281 Tor would ignore their RelayBandwidthBurst setting,
16282 potentially using more bandwidth than expected. Bugfix on
16283 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
16284 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
16285 hidserv" in her torrc. The 'hidserv' argument never controlled
16286 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
16289 - Adjust our TLS Diffie-Hellman parameters to match those used by
16291 - Update to the February 1 2011 Maxmind GeoLite Country database.
16294 - Check for and reject overly long directory certificates and
16295 directory tokens before they have a chance to hit any assertions.
16296 Bugfix on 0.2.1.28. Found by "doorss".
16297 - Bring the logic that gathers routerinfos and assesses the
16298 acceptability of circuits into line. This prevents a Tor OP from
16299 getting locked in a cycle of choosing its local OR as an exit for a
16300 path (due to a .exit request) and then rejecting the circuit because
16301 its OR is not listed yet. It also prevents Tor clients from using an
16302 OR running in the same instance as an exit (due to a .exit request)
16303 if the OR does not meet the same requirements expected of an OR
16304 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
16306 o Packaging changes:
16307 - Stop shipping the Tor specs files and development proposal documents
16308 in the tarball. They are now in a separate git repository at
16309 git://git.torproject.org/torspec.git
16310 - Do not include Git version tags as though they are SVN tags when
16311 generating a tarball from inside a repository that has switched
16312 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
16315 Changes in version 0.2.2.22-alpha - 2011-01-25
16316 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
16317 main other change is a slight tweak to Tor's TLS handshake that makes
16318 relays and bridges that run this new version reachable from Iran again.
16319 We don't expect this tweak will win the arms race long-term, but it
16320 will buy us a bit more time until we roll out a better solution.
16323 - Fix a bounds-checking error that could allow an attacker to
16324 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
16325 Found by "piebeer".
16326 - Don't assert when changing from bridge to relay or vice versa
16327 via the controller. The assert happened because we didn't properly
16328 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
16329 bug 2433. Reported by bastik.
16332 - Adjust our TLS Diffie-Hellman parameters to match those used by
16334 - Provide a log message stating which geoip file we're parsing
16335 instead of just stating that we're parsing the geoip file.
16336 Implements ticket 2432.
16339 - Check for and reject overly long directory certificates and
16340 directory tokens before they have a chance to hit any assertions.
16341 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
16344 Changes in version 0.2.2.21-alpha - 2011-01-15
16345 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
16346 continues our recent code security audit work. The main fix resolves
16347 a remote heap overflow vulnerability that can allow remote code
16348 execution (CVE-2011-0427). Other fixes address a variety of assert
16349 and crash bugs, most of which we think are hard to exploit remotely.
16351 o Major bugfixes (security), also included in 0.2.1.29:
16352 - Fix a heap overflow bug where an adversary could cause heap
16353 corruption. This bug probably allows remote code execution
16354 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
16356 - Prevent a denial-of-service attack by disallowing any
16357 zlib-compressed data whose compression factor is implausibly
16358 high. Fixes part of bug 2324; reported by "doorss".
16359 - Zero out a few more keys in memory before freeing them. Fixes
16360 bug 2384 and part of bug 2385. These key instances found by
16361 "cypherpunks", based on Andrew Case's report about being able
16362 to find sensitive data in Tor's memory space if you have enough
16363 permissions. Bugfix on 0.0.2pre9.
16365 o Major bugfixes (crashes), also included in 0.2.1.29:
16366 - Prevent calls to Libevent from inside Libevent log handlers.
16367 This had potential to cause a nasty set of crashes, especially
16368 if running Libevent with debug logging enabled, and running
16369 Tor with a controller watching for low-severity log messages.
16370 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
16371 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
16372 underflow errors there too. Fixes the other part of bug 2324.
16373 - Fix a bug where we would assert if we ever had a
16374 cached-descriptors.new file (or another file read directly into
16375 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
16376 on 0.2.1.25. Found by doorss.
16377 - Fix some potential asserts and parsing issues with grossly
16378 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
16381 o Minor bugfixes (other), also included in 0.2.1.29:
16382 - Fix a bug with handling misformed replies to reverse DNS lookup
16383 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
16384 bug reported by doorss.
16385 - Fix compilation on mingw when a pthreads compatibility library
16386 has been installed. (We don't want to use it, so we shouldn't
16387 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
16388 - Fix a bug where we would declare that we had run out of virtual
16389 addresses when the address space was only half-exhausted. Bugfix
16391 - Correctly handle the case where AutomapHostsOnResolve is set but
16392 no virtual addresses are available. Fixes bug 2328; bugfix on
16393 0.1.2.1-alpha. Bug found by doorss.
16394 - Correctly handle wrapping around when we run out of virtual
16395 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
16397 o Minor features, also included in 0.2.1.29:
16398 - Update to the January 1 2011 Maxmind GeoLite Country database.
16399 - Introduce output size checks on all of our decryption functions.
16401 o Build changes, also included in 0.2.1.29:
16402 - Tor does not build packages correctly with Automake 1.6 and earlier;
16403 added a check to Makefile.am to make sure that we're building with
16404 Automake 1.7 or later.
16405 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
16406 because we built it with a too-old version of automake. Thus that
16407 release broke ./configure --enable-openbsd-malloc, which is popular
16408 among really fast exit relays on Linux.
16410 o Major bugfixes, new in 0.2.2.21-alpha:
16411 - Prevent crash/heap corruption when the cbtnummodes consensus
16412 parameter is set to 0 or large values. Fixes bug 2317; bugfix
16415 o Major features, new in 0.2.2.21-alpha:
16416 - Introduce minimum/maximum values that clients will believe
16417 from the consensus. Now we'll have a better chance to avoid crashes
16418 or worse when a consensus param has a weird value.
16420 o Minor features, new in 0.2.2.21-alpha:
16421 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
16422 used on bridges, and it makes bridge scanning somewhat easier.
16423 - If writing the state file to disk fails, wait up to an hour before
16424 retrying again, rather than trying again each second. Fixes bug
16425 2346; bugfix on Tor 0.1.1.3-alpha.
16426 - Make Libevent log messages get delivered to controllers later,
16427 and not from inside the Libevent log handler. This prevents unsafe
16428 reentrant Libevent calls while still letting the log messages
16430 - Detect platforms that brokenly use a signed size_t, and refuse to
16431 build there. Found and analyzed by doorss and rransom.
16432 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
16435 o Minor bugfixes, new in 0.2.2.21-alpha:
16436 - Handle SOCKS messages longer than 128 bytes long correctly, rather
16437 than waiting forever for them to finish. Fixes bug 2330; bugfix
16438 on 0.2.0.16-alpha. Found by doorss.
16439 - Add assertions to check for overflow in arguments to
16440 base32_encode() and base32_decode(); fix a signed-unsigned
16441 comparison there too. These bugs are not actually reachable in Tor,
16442 but it's good to prevent future errors too. Found by doorss.
16443 - Correctly detect failures to create DNS requests when using Libevent
16444 versions before v2. (Before Libevent 2, we used our own evdns
16445 implementation. Its return values for Libevent's evdns_resolve_*()
16446 functions are not consistent with those from Libevent.) Fixes bug
16447 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
16449 o Documentation, new in 0.2.2.21-alpha:
16450 - Document the default socks host and port (127.0.0.1:9050) for
16454 Changes in version 0.2.1.29 - 2011-01-15
16455 Tor 0.2.1.29 continues our recent code security audit work. The main
16456 fix resolves a remote heap overflow vulnerability that can allow remote
16457 code execution. Other fixes address a variety of assert and crash bugs,
16458 most of which we think are hard to exploit remotely.
16460 o Major bugfixes (security):
16461 - Fix a heap overflow bug where an adversary could cause heap
16462 corruption. This bug probably allows remote code execution
16463 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
16465 - Prevent a denial-of-service attack by disallowing any
16466 zlib-compressed data whose compression factor is implausibly
16467 high. Fixes part of bug 2324; reported by "doorss".
16468 - Zero out a few more keys in memory before freeing them. Fixes
16469 bug 2384 and part of bug 2385. These key instances found by
16470 "cypherpunks", based on Andrew Case's report about being able
16471 to find sensitive data in Tor's memory space if you have enough
16472 permissions. Bugfix on 0.0.2pre9.
16474 o Major bugfixes (crashes):
16475 - Prevent calls to Libevent from inside Libevent log handlers.
16476 This had potential to cause a nasty set of crashes, especially
16477 if running Libevent with debug logging enabled, and running
16478 Tor with a controller watching for low-severity log messages.
16479 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
16480 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
16481 underflow errors there too. Fixes the other part of bug 2324.
16482 - Fix a bug where we would assert if we ever had a
16483 cached-descriptors.new file (or another file read directly into
16484 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
16485 on 0.2.1.25. Found by doorss.
16486 - Fix some potential asserts and parsing issues with grossly
16487 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
16490 o Minor bugfixes (other):
16491 - Fix a bug with handling misformed replies to reverse DNS lookup
16492 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
16493 bug reported by doorss.
16494 - Fix compilation on mingw when a pthreads compatibility library
16495 has been installed. (We don't want to use it, so we shouldn't
16496 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
16497 - Fix a bug where we would declare that we had run out of virtual
16498 addresses when the address space was only half-exhausted. Bugfix
16500 - Correctly handle the case where AutomapHostsOnResolve is set but
16501 no virtual addresses are available. Fixes bug 2328; bugfix on
16502 0.1.2.1-alpha. Bug found by doorss.
16503 - Correctly handle wrapping around to when we run out of virtual
16504 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
16505 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
16506 because we built it with a too-old version of automake. Thus that
16507 release broke ./configure --enable-openbsd-malloc, which is popular
16508 among really fast exit relays on Linux.
16511 - Update to the January 1 2011 Maxmind GeoLite Country database.
16512 - Introduce output size checks on all of our decryption functions.
16515 - Tor does not build packages correctly with Automake 1.6 and earlier;
16516 added a check to Makefile.am to make sure that we're building with
16517 Automake 1.7 or later.
16520 Changes in version 0.2.2.20-alpha - 2010-12-17
16521 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
16522 exploitable bugs. We also fix a variety of other significant bugs,
16523 change the IP address for one of our directory authorities, and update
16524 the minimum version that Tor relays must run to join the network.
16527 - Fix a remotely exploitable bug that could be used to crash instances
16528 of Tor remotely by overflowing on the heap. Remote-code execution
16529 hasn't been confirmed, but can't be ruled out. Everyone should
16530 upgrade. Bugfix on the 0.1.1 series and later.
16531 - Fix a bug that could break accounting on 64-bit systems with large
16532 time_t values, making them hibernate for impossibly long intervals.
16533 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
16534 - Fix a logic error in directory_fetches_from_authorities() that
16535 would cause all _non_-exits refusing single-hop-like circuits
16536 to fetch from authorities, when we wanted to have _exits_ fetch
16537 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
16539 - Fix a stream fairness bug that would cause newer streams on a given
16540 circuit to get preference when reading bytes from the origin or
16541 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
16542 introduced before the first Tor release, in svn revision r152.
16544 o Directory authority changes:
16545 - Change IP address and ports for gabelmoo (v3 directory authority).
16548 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
16549 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
16550 - Fix an off-by-one error in calculating some controller command
16551 argument lengths. Fortunately, this mistake is harmless since
16552 the controller code does redundant NUL termination too. Found by
16553 boboper. Bugfix on 0.1.1.1-alpha.
16554 - Do not dereference NULL if a bridge fails to build its
16555 extra-info descriptor. Found by an anonymous commenter on
16556 Trac. Bugfix on 0.2.2.19-alpha.
16559 - Update to the December 1 2010 Maxmind GeoLite Country database.
16560 - Directory authorities now reject relays running any versions of
16561 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
16562 known bugs that keep RELAY_EARLY cells from working on rendezvous
16563 circuits. Followup to fix for bug 2081.
16564 - Directory authorities now reject relays running any version of Tor
16565 older than 0.2.0.26-rc. That version is the earliest that fetches
16566 current directory information correctly. Fixes bug 2156.
16567 - Report only the top 10 ports in exit-port stats in order not to
16568 exceed the maximum extra-info descriptor length of 50 KB. Implements
16572 Changes in version 0.2.1.28 - 2010-12-17
16573 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
16574 exploitable bugs. We also took this opportunity to change the IP address
16575 for one of our directory authorities, and to update the geoip database
16579 - Fix a remotely exploitable bug that could be used to crash instances
16580 of Tor remotely by overflowing on the heap. Remote-code execution
16581 hasn't been confirmed, but can't be ruled out. Everyone should
16582 upgrade. Bugfix on the 0.1.1 series and later.
16584 o Directory authority changes:
16585 - Change IP address and ports for gabelmoo (v3 directory authority).
16588 - Update to the December 1 2010 Maxmind GeoLite Country database.
16591 Changes in version 0.2.1.27 - 2010-11-23
16592 Yet another OpenSSL security patch broke its compatibility with Tor:
16593 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
16594 also took this opportunity to fix several crash bugs, integrate a new
16595 directory authority, and update the bundled GeoIP database.
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.
16603 - Do not log messages to the controller while shrinking buffer
16604 freelists. Doing so would sometimes make the controller connection
16605 try to allocate a buffer chunk, which would mess up the internals
16606 of the freelist and cause an assertion failure. Fixes bug 1125;
16607 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
16608 - Learn our external IP address when we're a relay or bridge, even if
16609 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
16610 where we introduced bridge relays that don't need to publish to
16611 be useful. Fixes bug 2050.
16612 - Do even more to reject (and not just ignore) annotations on
16613 router descriptors received anywhere but from the cache. Previously
16614 we would ignore such annotations at first, but cache them to disk
16615 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
16616 - When you're using bridges and your network goes away and your
16617 bridges get marked as down, recover when you attempt a new socks
16618 connection (if the network is back), rather than waiting up to an
16619 hour to try fetching new descriptors for your bridges. Bugfix on
16620 0.2.0.3-alpha; fixes bug 1981.
16623 - Move to the November 2010 Maxmind GeoLite country db (rather
16624 than the June 2009 ip-to-country GeoIP db) for our statistics that
16625 count how many users relays are seeing from each country. Now we'll
16626 have more accurate data, especially for many African countries.
16628 o New directory authorities:
16629 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
16633 - Fix an assertion failure that could occur in directory caches or
16634 bridge users when using a very short voting interval on a testing
16635 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
16637 - Enforce multiplicity rules when parsing annotations. Bugfix on
16638 0.2.0.8-alpha. Found by piebeer.
16639 - Allow handshaking OR connections to take a full KeepalivePeriod
16640 seconds to handshake. Previously, we would close them after
16641 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
16642 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
16644 - When building with --enable-gcc-warnings on OpenBSD, disable
16645 warnings in system headers. This makes --enable-gcc-warnings
16646 pass on OpenBSD 4.8.
16649 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
16650 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
16651 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
16652 Servers can start sending this code when enough clients recognize
16653 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
16654 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
16655 Patch from mingw-san.
16658 - Remove the old debian/ directory from the main Tor distribution.
16659 The official Tor-for-debian git repository lives at the URL
16660 https://git.torproject.org/debian/tor.git
16661 - Stop shipping the old doc/website/ directory in the tarball. We
16662 changed the website format in late 2010, and what we shipped in
16663 0.2.1.26 really wasn't that useful anyway.
16666 Changes in version 0.2.2.19-alpha - 2010-11-22
16667 Yet another OpenSSL security patch broke its compatibility with Tor:
16668 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
16671 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
16672 No longer set the tlsext_host_name extension on server SSL objects;
16673 but continue to set it on client SSL objects. Our goal in setting
16674 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
16675 bugfix on 0.2.1.1-alpha.
16678 - Try harder not to exceed the maximum length of 50 KB when writing
16679 statistics to extra-info descriptors. This bug was triggered by very
16680 fast relays reporting exit-port, entry, and dirreq statistics.
16681 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
16682 - Publish a router descriptor even if generating an extra-info
16683 descriptor fails. Previously we would not publish a router
16684 descriptor without an extra-info descriptor; this can cause fast
16685 exit relays collecting exit-port statistics to drop from the
16686 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
16689 Changes in version 0.2.2.18-alpha - 2010-11-16
16690 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
16691 us lately, makes unpublished bridge relays able to detect their IP
16692 address, and fixes a wide variety of other bugs to get us much closer
16693 to a stable release.
16696 - Do even more to reject (and not just ignore) annotations on
16697 router descriptors received anywhere but from the cache. Previously
16698 we would ignore such annotations at first, but cache them to disk
16699 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
16700 - Do not log messages to the controller while shrinking buffer
16701 freelists. Doing so would sometimes make the controller connection
16702 try to allocate a buffer chunk, which would mess up the internals
16703 of the freelist and cause an assertion failure. Fixes bug 1125;
16704 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
16705 - Learn our external IP address when we're a relay or bridge, even if
16706 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
16707 where we introduced bridge relays that don't need to publish to
16708 be useful. Fixes bug 2050.
16709 - Maintain separate TLS contexts and certificates for incoming and
16710 outgoing connections in bridge relays. Previously we would use the
16711 same TLS contexts and certs for incoming and outgoing connections.
16712 Bugfix on 0.2.0.3-alpha; addresses bug 988.
16713 - Maintain separate identity keys for incoming and outgoing TLS
16714 contexts in bridge relays. Previously we would use the same
16715 identity keys for incoming and outgoing TLS contexts. Bugfix on
16716 0.2.0.3-alpha; addresses the other half of bug 988.
16717 - Avoid an assertion failure when we as an authority receive a
16718 duplicate upload of a router descriptor that we already have,
16719 but which we previously considered an obsolete descriptor.
16720 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
16721 - Avoid a crash bug triggered by looking at a dangling pointer while
16722 setting the network status consensus. Found by Robert Ransom.
16723 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
16724 - Fix a logic error where servers that _didn't_ act as exits would
16725 try to keep their server lists more aggressively up to date than
16726 exits, when it was supposed to be the other way around. Bugfix
16729 o Minor bugfixes (on Tor 0.2.1.x and earlier):
16730 - When we're trying to guess whether we know our IP address as
16731 a relay, we would log various ways that we failed to guess
16732 our address, but never log that we ended up guessing it
16733 successfully. Now add a log line to help confused and anxious
16734 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
16735 - Bring the logic that gathers routerinfos and assesses the
16736 acceptability of circuits into line. This prevents a Tor OP from
16737 getting locked in a cycle of choosing its local OR as an exit for a
16738 path (due to a .exit request) and then rejecting the circuit because
16739 its OR is not listed yet. It also prevents Tor clients from using an
16740 OR running in the same instance as an exit (due to a .exit request)
16741 if the OR does not meet the same requirements expected of an OR
16742 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
16743 - Correctly describe errors that occur when generating a TLS object.
16744 Previously we would attribute them to a failure while generating a
16745 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
16747 - Enforce multiplicity rules when parsing annotations. Bugfix on
16748 0.2.0.8-alpha. Found by piebeer.
16749 - Fix warnings that newer versions of autoconf produced during
16750 ./autogen.sh. These warnings appear to be harmless in our case,
16751 but they were extremely verbose. Fixes bug 2020.
16753 o Minor bugfixes (on Tor 0.2.2.x):
16754 - Enable protection of small arrays whenever we build with gcc
16755 hardening features, not only when also building with warnings
16756 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
16759 - Make hidden services work better in private Tor networks by not
16760 requiring any uptime to join the hidden service descriptor
16761 DHT. Implements ticket 2088.
16762 - Rate-limit the "your application is giving Tor only an IP address"
16763 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
16764 - When AllowSingleHopExits is set, print a warning to explain to the
16765 relay operator why most clients are avoiding her relay.
16766 - Update to the November 1 2010 Maxmind GeoLite Country database.
16768 o Code simplifications and refactoring:
16769 - When we fixed bug 1038 we had to put in a restriction not to send
16770 RELAY_EARLY cells on rend circuits. This was necessary as long
16771 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
16772 active. Now remove this obsolete check. Resolves bug 2081.
16773 - Some options used different conventions for uppercasing of acronyms
16774 when comparing manpage and source. Fix those in favor of the
16775 manpage, as it makes sense to capitalize acronyms.
16776 - Remove the torrc.complete file. It hasn't been kept up to date
16777 and users will have better luck checking out the manpage.
16778 - Remove the obsolete "NoPublish" option; it has been flagged
16779 as obsolete and has produced a warning since 0.1.1.18-rc.
16780 - Remove everything related to building the expert bundle for OS X.
16781 It has confused many users, doesn't work right on OS X 10.6,
16782 and is hard to get rid of once installed. Resolves bug 1274.
16785 Changes in version 0.2.2.17-alpha - 2010-09-30
16786 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
16787 to use one-hop circuits (which can put the exit relays at higher risk,
16788 plus unbalance the network); fixes a big bug in bandwidth accounting
16789 for relays that want to limit their monthly bandwidth use; fixes a
16790 big pile of bugs in how clients tolerate temporary network failure;
16791 and makes our adaptive circuit build timeout feature (which improves
16792 client performance if your network is fast while not breaking things
16793 if your network is slow) better handle bad networks.
16796 - Exit relays now try harder to block exit attempts from unknown
16797 relays, to make it harder for people to use them as one-hop proxies
16798 a la tortunnel. Controlled by the refuseunknownexits consensus
16799 parameter (currently enabled), or you can override it on your
16800 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
16802 o Major bugfixes (0.2.1.x and earlier):
16803 - Fix a bug in bandwidth accounting that could make us use twice
16804 the intended bandwidth when our interval start changes due to
16805 daylight saving time. Now we tolerate skew in stored vs computed
16806 interval starts: if the start of the period changes by no more than
16807 50% of the period's duration, we remember bytes that we transferred
16808 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
16809 - Always search the Windows system directory for system DLLs, and
16810 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
16811 - When you're using bridges and your network goes away and your
16812 bridges get marked as down, recover when you attempt a new socks
16813 connection (if the network is back), rather than waiting up to an
16814 hour to try fetching new descriptors for your bridges. Bugfix on
16815 0.2.0.3-alpha; fixes bug 1981.
16817 o Major bugfixes (on 0.2.2.x):
16818 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
16820 - Fix a segfault that could happen when operating a bridge relay with
16821 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
16822 - The consensus bandwidth-weights (used by clients to choose fast
16823 relays) entered an unexpected edge case in September where
16824 Exits were much scarcer than Guards, resulting in bad weight
16825 recommendations. Now we compute them using new constraints that
16826 should succeed in all cases. Also alter directory authorities to
16827 not include the bandwidth-weights line if they fail to produce
16828 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
16829 - When weighting bridges during path selection, we used to trust
16830 the bandwidths they provided in their descriptor, only capping them
16831 at 10MB/s. This turned out to be problematic for two reasons:
16832 Bridges could claim to handle a lot more traffic then they
16833 actually would, thus making more clients pick them and have a
16834 pretty effective DoS attack. The other issue is that new bridges
16835 that might not have a good estimate for their bw capacity yet
16836 would not get used at all unless no other bridges are available
16837 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
16839 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
16840 - Ignore cannibalized circuits when recording circuit build times.
16841 This should provide for a minor performance improvement for hidden
16842 service users using 0.2.2.14-alpha, and should remove two spurious
16843 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
16844 - Simplify the logic that causes us to decide if the network is
16845 unavailable for purposes of recording circuit build times. If we
16846 receive no cells whatsoever for the entire duration of a circuit's
16847 full measured lifetime, the network is probably down. Also ignore
16848 one-hop directory fetching circuit timeouts when calculating our
16849 circuit build times. These changes should hopefully reduce the
16850 cases where we see ridiculous circuit build timeouts for people
16851 with spotty wireless connections. Fixes part of bug 1772; bugfix
16853 - Prevent the circuit build timeout from becoming larger than
16854 the maximum build time we have ever seen. Also, prevent the time
16855 period for measurement circuits from becoming larger than twice that
16856 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
16859 - When we run out of directory information such that we can't build
16860 circuits, but then get enough that we can build circuits, log when
16861 we actually construct a circuit, so the user has a better chance of
16862 knowing what's going on. Fixes bug 1362.
16863 - Be more generous with how much bandwidth we'd use up (with
16864 accounting enabled) before entering "soft hibernation". Previously,
16865 we'd refuse new connections and circuits once we'd used up 95% of
16866 our allotment. Now, we use up 95% of our allotment, AND make sure
16867 that we have no more than 500MB (or 3 hours of expected traffic,
16868 whichever is lower) remaining before we enter soft hibernation.
16869 - If we've configured EntryNodes and our network goes away and/or all
16870 our entrynodes get marked down, optimistically retry them all when
16871 a new socks application request appears. Fixes bug 1882.
16872 - Add some more defensive programming for architectures that can't
16873 handle unaligned integer accesses. We don't know of any actual bugs
16874 right now, but that's the best time to fix them. Fixes bug 1943.
16875 - Support line continuations in the torrc config file. If a line
16876 ends with a single backslash character, the newline is ignored, and
16877 the configuration value is treated as continuing on the next line.
16880 o Minor bugfixes (on 0.2.1.x and earlier):
16881 - For bandwidth accounting, calculate our expected bandwidth rate
16882 based on the time during which we were active and not in
16883 soft-hibernation during the last interval. Previously, we were
16884 also considering the time spent in soft-hibernation. If this
16885 was a long time, we would wind up underestimating our bandwidth
16886 by a lot, and skewing our wakeup time towards the start of the
16887 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
16889 o Minor bugfixes (on 0.2.2.x):
16890 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
16891 which were disabled by the circuit build timeout changes in
16892 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
16893 - Make sure we don't warn about missing bandwidth weights when
16894 choosing bridges or other relays not in the consensus. Bugfix on
16895 0.2.2.10-alpha; fixes bug 1805.
16896 - In our logs, do not double-report signatures from unrecognized
16897 authorities both as "from unknown authority" and "not
16898 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
16901 Changes in version 0.2.2.16-alpha - 2010-09-17
16902 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
16903 evident at exit relays), and also continues to resolve all the little
16904 bugs that have been filling up trac lately.
16906 o Major bugfixes (stream-level fairness):
16907 - When receiving a circuit-level SENDME for a blocked circuit, try
16908 to package cells fairly from all the streams that had previously
16909 been blocked on that circuit. Previously, we had started with the
16910 oldest stream, and allowed each stream to potentially exhaust
16911 the circuit's package window. This gave older streams on any
16912 given circuit priority over newer ones. Fixes bug 1937. Detected
16913 originally by Camilo Viecco. This bug was introduced before the
16914 first Tor release, in svn commit r152: it is the new winner of
16915 the longest-lived bug prize.
16916 - When the exit relay got a circuit-level sendme cell, it started
16917 reading on the exit streams, even if had 500 cells queued in the
16918 circuit queue already, so the circuit queue just grew and grew in
16919 some cases. We fix this by not re-enabling reading on receipt of a
16920 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
16921 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
16923 - Newly created streams were allowed to read cells onto circuits,
16924 even if the circuit's cell queue was blocked and waiting to drain.
16925 This created potential unfairness, as older streams would be
16926 blocked, but newer streams would gladly fill the queue completely.
16927 We add code to detect this situation and prevent any stream from
16928 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
16932 - Update to the September 1 2010 Maxmind GeoLite Country database.
16933 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
16934 not. This would lead to a cookie that is still not group readable.
16935 Closes bug 1843. Suggested by katmagic.
16936 - When logging a rate-limited warning, we now mention how many messages
16937 got suppressed since the last warning.
16938 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
16939 do individual connection-level rate limiting of clients. The torrc
16940 config options with the same names trump the consensus params, if
16941 both are present. Replaces the old "bwconnrate" and "bwconnburst"
16942 consensus params which were broken from 0.2.2.7-alpha through
16943 0.2.2.14-alpha. Closes bug 1947.
16944 - When a router changes IP address or port, authorities now launch
16945 a new reachability test for it. Implements ticket 1899.
16946 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
16947 2 no signature, 4 required" messages about consensus signatures
16948 easier to read, and make sure they get logged at the same severity
16949 as the messages explaining which keys are which. Fixes bug 1290.
16950 - Don't warn when we have a consensus that we can't verify because
16951 of missing certificates, unless those certificates are ones
16952 that we have been trying and failing to download. Fixes bug 1145.
16953 - If you configure your bridge with a known identity fingerprint,
16954 and the bridge authority is unreachable (as it is in at least
16955 one country now), fall back to directly requesting the descriptor
16956 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
16958 - When building with --enable-gcc-warnings on OpenBSD, disable
16959 warnings in system headers. This makes --enable-gcc-warnings
16960 pass on OpenBSD 4.8.
16962 o Minor bugfixes (on 0.2.1.x and earlier):
16963 - Authorities will now attempt to download consensuses if their
16964 own efforts to make a live consensus have failed. This change
16965 means authorities that restart will fetch a valid consensus, and
16966 it means authorities that didn't agree with the current consensus
16967 will still fetch and serve it if it has enough signatures. Bugfix
16968 on 0.2.0.9-alpha; fixes bug 1300.
16969 - Ensure DNS requests launched by "RESOLVE" commands from the
16970 controller respect the __LeaveStreamsUnattached setconf options. The
16971 same goes for requests launched via DNSPort or transparent
16972 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
16973 - Allow handshaking OR connections to take a full KeepalivePeriod
16974 seconds to handshake. Previously, we would close them after
16975 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
16976 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
16978 - Rate-limit "Failed to hand off onionskin" warnings.
16979 - Never relay a cell for a circuit we have already destroyed.
16980 Between marking a circuit as closeable and finally closing it,
16981 it may have been possible for a few queued cells to get relayed,
16982 even though they would have been immediately dropped by the next
16983 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
16984 - Never queue a cell for a circuit that's already been marked
16986 - Never vote for a server as "Running" if we have a descriptor for
16987 it claiming to be hibernating, and that descriptor was published
16988 more recently than our last contact with the server. Bugfix on
16989 0.2.0.3-alpha; fixes bug 911.
16990 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
16993 o Minor bugfixes (on 0.2.2.x):
16994 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
16995 down if a directory fetch fails and you've configured either
16996 bridges or EntryNodes. The intent was to mark the relay as down
16997 _unless_ you're using bridges or EntryNodes, since if you are
16998 then you could quickly run out of entry points.
16999 - Fix the Windows directory-listing code. A bug introduced in
17000 0.2.2.14-alpha could make Windows directory servers forget to load
17001 some of their cached v2 networkstatus files.
17002 - Really allow clients to use relays as bridges. Fixes bug 1776;
17003 bugfix on 0.2.2.15-alpha.
17004 - Demote a warn to info that happens when the CellStatistics option
17005 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
17006 Reported by Moritz Bartl.
17007 - On Windows, build correctly either with or without Unicode support.
17008 This is necessary so that Tor can support fringe platforms like
17009 Windows 98 (which has no Unicode), or Windows CE (which has no
17010 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
17013 - Add a unit test for cross-platform directory-listing code.
17016 Changes in version 0.2.2.15-alpha - 2010-08-18
17017 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
17018 fixes a variety of other bugs that were preventing performance
17019 experiments from moving forward, fixes several bothersome memory leaks,
17020 and generally closes a lot of smaller bugs that have been filling up
17024 - Stop assigning the HSDir flag to relays that disable their
17025 DirPort (and thus will refuse to answer directory requests). This
17026 fix should dramatically improve the reachability of hidden services:
17027 hidden services and hidden service clients pick six HSDir relays
17028 to store and retrieve the hidden service descriptor, and currently
17029 about half of the HSDir relays will refuse to work. Bugfix on
17030 0.2.0.10-alpha; fixes part of bug 1693.
17031 - The PerConnBWRate and Burst config options, along with the
17032 bwconnrate and bwconnburst consensus params, initialized each conn's
17033 token bucket values only when the connection is established. Now we
17034 update them if the config options change, and update them every time
17035 we get a new consensus. Otherwise we can encounter an ugly edge
17036 case where we initialize an OR conn to client-level bandwidth,
17037 but then later the relay joins the consensus and we leave it
17038 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
17039 - Fix a regression that caused Tor to rebind its ports if it receives
17040 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
17043 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
17044 should give us approximately 40-50% more Guard-flagged nodes,
17045 improving the anonymity the Tor network can provide and also
17046 decreasing the dropoff in throughput that relays experience when
17047 they first get the Guard flag.
17048 - Allow enabling or disabling the *Statistics config options while
17052 - Update to the August 1 2010 Maxmind GeoLite Country database.
17053 - Have the controller interface give a more useful message than
17054 "Internal Error" in response to failed GETINFO requests.
17055 - Warn when the same option is provided more than once in a torrc
17056 file, on the command line, or in a single SETCONF statement, and
17057 the option is one that only accepts a single line. Closes bug 1384.
17058 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
17059 Patch from mingw-san.
17060 - Add support for the country code "{??}" in torrc options like
17061 ExcludeNodes, to indicate all routers of unknown country. Closes
17063 - Relays report the number of bytes spent on answering directory
17064 requests in extra-info descriptors similar to {read,write}-history.
17065 Implements enhancement 1790.
17067 o Minor bugfixes (on 0.2.1.x and earlier):
17068 - Complain if PublishServerDescriptor is given multiple arguments that
17069 include 0 or 1. This configuration will be rejected in the future.
17070 Bugfix on 0.2.0.1-alpha; closes bug 1107.
17071 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
17072 Bugfix on 0.2.0.13-alpha; closes bug 928.
17073 - Change "Application request when we're believed to be offline."
17074 notice to "Application request when we haven't used client
17075 functionality lately.", to clarify that it's not an error. Bugfix
17076 on 0.0.9.3; fixes bug 1222.
17077 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
17078 would return "551 Internal error" rather than "552 Unrecognized key
17079 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
17080 - Users can't configure a regular relay to be their bridge. It didn't
17081 work because when Tor fetched the bridge descriptor, it found
17082 that it already had it, and didn't realize that the purpose of the
17083 descriptor had changed. Now we replace routers with a purpose other
17084 than bridge with bridge descriptors when fetching them. Bugfix on
17085 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
17086 refetch the descriptor with router purpose 'general', disabling
17088 - Fix a rare bug in rend_fn unit tests: we would fail a test when
17089 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
17090 on 0.2.0.10-alpha; fixes bug 1808.
17091 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
17092 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
17093 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
17094 Servers can start sending this code when enough clients recognize
17095 it. Also update the spec to reflect this new reason. Bugfix on
17096 0.1.0.1-rc; fixes part of bug 1793.
17097 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
17098 when we switch from being a public relay to a bridge. Otherwise
17099 there will still be clients that see the relay in their consensus,
17100 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
17102 - Instead of giving an assertion failure on an internal mismatch
17103 on estimated freelist size, just log a BUG warning and try later.
17104 Mitigates but does not fix bug 1125.
17105 - Fix an assertion failure that could occur in caches or bridge users
17106 when using a very short voting interval on a testing network.
17107 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
17109 o Minor bugfixes (on 0.2.2.x):
17110 - Alter directory authorities to always consider Exit-flagged nodes
17111 as potential Guard nodes in their votes. The actual decision to
17112 use Exits as Guards is done in the consensus bandwidth weights.
17113 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
17114 - When the controller is reporting the purpose of circuits that
17115 didn't finish building before the circuit build timeout, it was
17116 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
17117 - Our libevent version parsing code couldn't handle versions like
17118 1.4.14b-stable and incorrectly warned the user about using an
17119 old and broken version of libevent. Treat 1.4.14b-stable like
17120 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
17122 - Don't use substitution references like $(VAR:MOD) when
17123 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
17124 '$(:x)' to 'x' rather than the empty string. This bites us in
17125 doc/ when configured with --disable-asciidoc. Bugfix on
17126 0.2.2.9-alpha; fixes bug 1773.
17127 - Remove a spurious hidden service server-side log notice about
17128 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
17130 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
17132 - Correctly report written bytes on linked connections. Found while
17133 implementing 1790. Bugfix on 0.2.2.4-alpha.
17134 - Fix three memory leaks: one in circuit_build_times_parse_state(),
17135 one in dirvote_add_signatures_to_pending_consensus(), and one every
17136 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
17137 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
17139 o Code simplifications and refactoring:
17140 - Take a first step towards making or.h smaller by splitting out
17141 function definitions for all source files in src/or/. Leave
17142 structures and defines in or.h for now.
17143 - Remove a bunch of unused function declarations as well as a block of
17144 #if 0'd code from the unit tests. Closes bug 1824.
17145 - New unit tests for exit-port history statistics; refactored exit
17146 statistics code to be more easily tested.
17147 - Remove the old debian/ directory from the main Tor distribution.
17148 The official Tor-for-debian git repository lives at the URL
17149 https://git.torproject.org/debian/tor.git
17152 Changes in version 0.2.2.14-alpha - 2010-07-12
17153 Tor 0.2.2.14-alpha greatly improves client-side handling of
17154 circuit build timeouts, which are used to estimate speed and improve
17155 performance. We also move to a much better GeoIP database, port Tor to
17156 Windows CE, introduce new compile flags that improve code security,
17157 add an eighth v3 directory authority, and address a lot of more
17161 - Tor directory authorities no longer crash when started with a
17162 cached-microdesc-consensus file in their data directory. Bugfix
17163 on 0.2.2.6-alpha; fixes bug 1532.
17164 - Treat an unset $HOME like an empty $HOME rather than triggering an
17165 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
17166 - Ignore negative and large circuit build timeout values that can
17167 happen during a suspend or hibernate. These values caused various
17168 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
17169 - Alter calculation of Pareto distribution parameter 'Xm' for
17170 Circuit Build Timeout learning to use the weighted average of the
17171 top N=3 modes (because we have three entry guards). Considering
17172 multiple modes should improve the timeout calculation in some cases,
17173 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
17175 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
17176 right censored distribution model. This approach improves over the
17177 synthetic timeout generation approach that was producing insanely
17178 high timeout values. Now we calculate build timeouts using truncated
17179 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
17180 - Do not close circuits that are under construction when they reach
17181 the circuit build timeout. Instead, leave them building (but do not
17182 use them) for up until the time corresponding to the 95th percentile
17183 on the Pareto CDF or 60 seconds, whichever is greater. This is done
17184 to provide better data for the new Pareto model. This percentile
17185 can be controlled by the consensus.
17188 - Move to the June 2010 Maxmind GeoLite country db (rather than the
17189 June 2009 ip-to-country GeoIP db) for our statistics that count
17190 how many users relays are seeing from each country. Now we have
17191 more accurate data for many African countries.
17192 - Port Tor to build and run correctly on Windows CE systems, using
17193 the wcecompat library. Contributed by Valerio Lupi.
17194 - New "--enable-gcc-hardening" ./configure flag (off by default)
17195 to turn on gcc compile time hardening options. It ensures
17196 that signed ints have defined behavior (-fwrapv), enables
17197 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
17198 with canaries (-fstack-protector-all), turns on ASLR protection if
17199 supported by the kernel (-fPIE, -pie), and adds additional security
17200 related warnings. Verified to work on Mac OS X and Debian Lenny.
17201 - New "--enable-linker-hardening" ./configure flag (off by default)
17202 to turn on ELF specific hardening features (relro, now). This does
17203 not work with Mac OS X or any other non-ELF binary format.
17205 o New directory authorities:
17206 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
17210 - New config option "WarnUnsafeSocks 0" disables the warning that
17211 occurs whenever Tor receives a socks handshake using a version of
17212 the socks protocol that can only provide an IP address (rather
17213 than a hostname). Setups that do DNS locally over Tor are fine,
17214 and we shouldn't spam the logs in that case.
17215 - Convert the HACKING file to asciidoc, and add a few new sections
17216 to it, explaining how we use Git, how we make changelogs, and
17217 what should go in a patch.
17218 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
17219 event, to give information on the current rate of circuit timeouts
17220 over our stored history.
17221 - Add ability to disable circuit build time learning via consensus
17222 parameter and via a LearnCircuitBuildTimeout config option. Also
17223 automatically disable circuit build time calculation if we are
17224 either a AuthoritativeDirectory, or if we fail to write our state
17225 file. Fixes bug 1296.
17226 - More gracefully handle corrupt state files, removing asserts
17227 in favor of saving a backup and resetting state.
17228 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
17232 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
17234 - When a2x fails, mention that the user could disable manpages instead
17235 of trying to fix their asciidoc installation.
17236 - Where available, use Libevent 2.0's periodic timers so that our
17237 once-per-second cleanup code gets called even more closely to
17238 once per second than it would otherwise. Fixes bug 943.
17239 - If you run a bridge that listens on multiple IP addresses, and
17240 some user configures a bridge address that uses a different IP
17241 address than your bridge writes in its router descriptor, and the
17242 user doesn't specify an identity key, their Tor would discard the
17243 descriptor because "it isn't one of our configured bridges", and
17244 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
17245 Bugfix on 0.2.0.3-alpha.
17246 - If OpenSSL fails to make a duplicate of a private or public key, log
17247 an error message and try to exit cleanly. May help with debugging
17248 if bug 1209 ever remanifests.
17249 - Save a couple bytes in memory allocation every time we escape
17250 certain characters in a string. Patch from Florian Zumbiehl.
17251 - Make it explicit that we don't cannibalize one-hop circuits. This
17252 happens in the wild, but doesn't turn out to be a problem because
17253 we fortunately don't use those circuits. Many thanks to outofwords
17254 for the initial analysis and to swissknife who confirmed that
17255 two-hop circuits are actually created.
17256 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
17257 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
17258 - Eliminate a case where a circuit build time warning was displayed
17259 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
17262 Changes in version 0.2.1.26 - 2010-05-02
17263 Tor 0.2.1.26 addresses the recent connection and memory overload
17264 problems we've been seeing on relays, especially relays with their
17265 DirPort open. If your relay has been crashing, or you turned it off
17266 because it used too many resources, give this release a try.
17268 This release also fixes yet another instance of broken OpenSSL libraries
17269 that was causing some relays to drop out of the consensus.
17272 - Teach relays to defend themselves from connection overload. Relays
17273 now close idle circuits early if it looks like they were intended
17274 for directory fetches. Relays are also more aggressive about closing
17275 TLS connections that have no circuits on them. Such circuits are
17276 unlikely to be re-used, and tens of thousands of them were piling
17277 up at the fast relays, causing the relays to run out of sockets
17278 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
17279 their directory fetches over TLS).
17280 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
17281 that claim to be earlier than 0.9.8m, but which have in reality
17282 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
17283 behavior. Possible fix for some cases of bug 1346.
17284 - Directory mirrors were fetching relay descriptors only from v2
17285 directory authorities, rather than v3 authorities like they should.
17286 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
17287 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
17290 - Finally get rid of the deprecated and now harmful notion of "clique
17291 mode", where directory authorities maintain TLS connections to
17295 - In the util/threads test, no longer free the test_mutex before all
17296 worker threads have finished. Bugfix on 0.2.1.6-alpha.
17297 - The master thread could starve the worker threads quite badly on
17298 certain systems, causing them to run only partially in the allowed
17299 window. This resulted in test failures. Now the master thread sleeps
17300 occasionally for a few microseconds while the two worker-threads
17301 compete for the mutex. Bugfix on 0.2.0.1-alpha.
17304 Changes in version 0.2.2.13-alpha - 2010-04-24
17305 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
17306 problems we've been seeing on relays, especially relays with their
17307 DirPort open. If your relay has been crashing, or you turned it off
17308 because it used too many resources, give this release a try.
17311 - Teach relays to defend themselves from connection overload. Relays
17312 now close idle circuits early if it looks like they were intended
17313 for directory fetches. Relays are also more aggressive about closing
17314 TLS connections that have no circuits on them. Such circuits are
17315 unlikely to be re-used, and tens of thousands of them were piling
17316 up at the fast relays, causing the relays to run out of sockets
17317 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
17318 their directory fetches over TLS).
17321 - Finally get rid of the deprecated and now harmful notion of "clique
17322 mode", where directory authorities maintain TLS connections to
17324 - Directory authorities now do an immediate reachability check as soon
17325 as they hear about a new relay. This change should slightly reduce
17326 the time between setting up a relay and getting listed as running
17327 in the consensus. It should also improve the time between setting
17328 up a bridge and seeing use by bridge users.
17329 - Directory authorities no longer launch a TLS connection to every
17330 relay as they startup. Now that we have 2k+ descriptors cached,
17331 the resulting network hiccup is becoming a burden. Besides,
17332 authorities already avoid voting about Running for the first half
17333 hour of their uptime.
17336 Changes in version 0.2.2.12-alpha - 2010-04-20
17337 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
17338 handle and vote on descriptors. It was causing relays to drop out of
17342 - Many relays have been falling out of the consensus lately because
17343 not enough authorities know about their descriptor for them to get
17344 a majority of votes. When we deprecated the v2 directory protocol,
17345 we got rid of the only way that v3 authorities can hear from each
17346 other about other descriptors. Now authorities examine every v3
17347 vote for new descriptors, and fetch them from that authority. Bugfix
17349 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
17350 and a warning in or.h related to bandwidth_weight_rule_t that
17351 prevented clean compile on OS X. Fixes bug 1363; bugfix on
17353 - Fix a segfault on relays when DirReqStatistics is enabled
17354 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
17358 - Demote a confusing TLS warning that relay operators might get when
17359 someone tries to talk to their OrPort. It is neither the operator's
17360 fault nor can they do anything about it. Fixes bug 1364; bugfix
17364 Changes in version 0.2.2.11-alpha - 2010-04-15
17365 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
17366 libraries that was causing some relays to drop out of the consensus.
17369 - Directory mirrors were fetching relay descriptors only from v2
17370 directory authorities, rather than v3 authorities like they should.
17371 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
17372 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
17373 - Fix a parsing error that made every possible value of
17374 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
17375 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
17376 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
17377 about the option without breaking older ones.
17378 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
17379 that claim to be earlier than 0.9.8m, but which have in reality
17380 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
17381 behavior. Possible fix for some cases of bug 1346.
17384 - Experiment with a more aggressive approach to preventing clients
17385 from making one-hop exit streams. Exit relays who want to try it
17386 out can set "RefuseUnknownExits 1" in their torrc, and then look
17387 for "Attempt by %s to open a stream" log messages. Let us know
17389 - Add support for statically linking zlib by specifying
17390 --enable-static-zlib, to go with our support for statically linking
17391 openssl and libevent. Resolves bug 1358.
17394 - Fix a segfault that happens whenever a Tor client that is using
17395 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
17397 - When we cleaned up the contrib/tor-exit-notice.html file, we left
17398 out the first line. Fixes bug 1295.
17399 - When building the manpage from a tarball, we required asciidoc, but
17400 the asciidoc -> roff/html conversion was already done for the
17401 tarball. Make 'make' complain only when we need asciidoc (either
17402 because we're compiling directly from git, or because we altered
17403 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
17404 - When none of the directory authorities vote on any params, Tor
17405 segfaulted when trying to make the consensus from the votes. We
17406 didn't trigger the bug in practice, because authorities do include
17407 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
17410 - In the util/threads test, no longer free the test_mutex before all
17411 worker threads have finished. Bugfix on 0.2.1.6-alpha.
17412 - The master thread could starve the worker threads quite badly on
17413 certain systems, causing them to run only partially in the allowed
17414 window. This resulted in test failures. Now the master thread sleeps
17415 occasionally for a few microseconds while the two worker-threads
17416 compete for the mutex. Bugfix on 0.2.0.1-alpha.
17419 Changes in version 0.2.2.10-alpha - 2010-03-07
17420 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
17421 could prevent relays from guessing their IP address correctly. It also
17422 starts the groundwork for another client-side performance boost, since
17423 currently we're not making efficient use of relays that have both the
17424 Guard flag and the Exit flag.
17427 - Fix a regression from our patch for bug 1244 that caused relays
17428 to guess their IP address incorrectly if they didn't set Address
17429 in their torrc and/or their address fails to resolve. Bugfix on
17430 0.2.2.9-alpha; fixes bug 1269.
17432 o Major features (performance):
17433 - Directory authorities now compute consensus weightings that instruct
17434 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
17435 and no flag. Clients that use these weightings will distribute
17436 network load more evenly across these different relay types. The
17437 weightings are in the consensus so we can change them globally in
17438 the future. Extra thanks to "outofwords" for finding some nasty
17439 security bugs in the first implementation of this feature.
17441 o Minor features (performance):
17442 - Always perform router selections using weighted relay bandwidth,
17443 even if we don't need a high capacity circuit at the time. Non-fast
17444 circuits now only differ from fast ones in that they can use relays
17445 not marked with the Fast flag. This "feature" could turn out to
17446 be a horrible bug; we should investigate more before it goes into
17450 - Allow disabling building of the manpages. Skipping the manpage
17451 speeds up the build considerably.
17453 o Minor bugfixes (on 0.2.2.x):
17454 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
17455 Bugfix on 0.2.2.9-alpha.
17456 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
17457 config option. Bugfix on 0.2.2.7-alpha.
17458 - Ship the asciidoc-helper file in the tarball, so that people can
17459 build from source if they want to, and touching the .1.txt files
17460 doesn't break the build. Bugfix on 0.2.2.9-alpha.
17462 o Minor bugfixes (on 0.2.1.x or earlier):
17463 - Fix a dereference-then-NULL-check sequence when publishing
17464 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
17466 - Fix another dereference-then-NULL-check sequence. Bugfix on
17467 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
17468 - Make sure we treat potentially not NUL-terminated strings correctly.
17469 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
17471 o Code simplifications and refactoring:
17472 - Fix some urls in the exit notice file and make it XHTML1.1 strict
17473 compliant. Based on a patch from Christian Kujau.
17474 - Don't use sed in asciidoc-helper anymore.
17475 - Make the build process fail if asciidoc cannot be found and
17476 building with asciidoc isn't disabled.
17479 Changes in version 0.2.2.9-alpha - 2010-02-22
17480 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
17481 location of a directory authority, and cleans up a bunch of small bugs.
17483 o Directory authority changes:
17484 - Change IP address for dannenberg (v3 directory authority), and
17485 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
17486 service directory authority) from the list.
17489 - Make Tor work again on the latest OS X: when deciding whether to
17490 use strange flags to turn TLS renegotiation on, detect the OpenSSL
17491 version at run-time, not compile time. We need to do this because
17492 Apple doesn't update its dev-tools headers when it updates its
17493 libraries in a security patch.
17494 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
17495 that could happen on 32-bit platforms with 64-bit time_t. Also fix
17496 a memory leak when requesting a hidden service descriptor we've
17497 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
17499 - Authorities could be tricked into giving out the Exit flag to relays
17500 that didn't allow exiting to any ports. This bug could screw
17501 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
17502 1238. Bug discovered by Martin Kowalczyk.
17503 - When freeing a session key, zero it out completely. We only zeroed
17504 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
17505 patched by ekir. Fixes bug 1254.
17508 - Fix static compilation by listing the openssl libraries in the right
17509 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
17510 - Resume handling .exit hostnames in a special way: originally we
17511 stripped the .exit part and used the requested exit relay. In
17512 0.2.2.1-alpha we stopped treating them in any special way, meaning
17513 if you use a .exit address then Tor will pass it on to the exit
17514 relay. Now we reject the .exit stream outright, since that behavior
17515 might be more expected by the user. Found and diagnosed by Scott
17516 Bennett and Downie on or-talk.
17517 - Don't spam the controller with events when we have no file
17518 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
17519 for log messages was already solved from bug 748.)
17520 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
17522 - Make the DNSPort option work with libevent 2.x. Don't alter the
17523 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
17524 - Emit a GUARD DROPPED controller event for a case we missed.
17525 - Make more fields in the controller protocol case-insensitive, since
17526 control-spec.txt said they were.
17527 - Refactor resolve_my_address() to not use gethostbyname() anymore.
17528 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
17529 - Fix a spec conformance issue: the network-status-version token
17530 must be the first token in a v3 consensus or vote. Discovered by
17531 parakeep. Bugfix on 0.2.0.3-alpha.
17533 o Code simplifications and refactoring:
17534 - Generate our manpage and HTML documentation using Asciidoc. This
17535 change should make it easier to maintain the documentation, and
17536 produce nicer HTML.
17537 - Remove the --enable-iphone option. According to reports from Marco
17538 Bonetti, Tor builds fine without any special tweaking on recent
17539 iPhone SDK versions.
17540 - Removed some unnecessary files from the source distribution. The
17541 AUTHORS file has now been merged into the people page on the
17542 website. The roadmaps and design doc can now be found in the
17543 projects directory in svn.
17544 - Enabled various circuit build timeout constants to be controlled
17545 by consensus parameters. Also set better defaults for these
17546 parameters based on experimentation on broadband and simulated
17547 high latency links.
17550 - The 'EXTENDCIRCUIT' control port command can now be used with
17551 a circ id of 0 and no path. This feature will cause Tor to build
17552 a new 'fast' general purpose circuit using its own path selection
17554 - Added a BUILDTIMEOUT_SET controller event to describe changes
17555 to the circuit build timeout.
17556 - Future-proof the controller protocol a bit by ignoring keyword
17557 arguments we do not recognize.
17558 - Expand homedirs passed to tor-checkkey. This should silence a
17559 coverity complaint about passing a user-supplied string into
17560 open() without checking it.
17563 Changes in version 0.2.1.25 - 2010-03-16
17564 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
17565 prevent relays from guessing their IP address correctly. It also fixes
17566 several minor potential security bugs.
17569 - Fix a regression from our patch for bug 1244 that caused relays
17570 to guess their IP address incorrectly if they didn't set Address
17571 in their torrc and/or their address fails to resolve. Bugfix on
17572 0.2.1.23; fixes bug 1269.
17573 - When freeing a session key, zero it out completely. We only zeroed
17574 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
17575 patched by ekir. Fixes bug 1254.
17578 - Fix a dereference-then-NULL-check sequence when publishing
17579 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
17581 - Fix another dereference-then-NULL-check sequence. Bugfix on
17582 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
17583 - Make sure we treat potentially not NUL-terminated strings correctly.
17584 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
17588 Changes in version 0.2.1.24 - 2010-02-21
17589 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
17593 - Work correctly out-of-the-box with even more vendor-patched versions
17594 of OpenSSL. In particular, make it so Debian and OS X don't need
17595 customized patches to run/build.
17598 Changes in version 0.2.1.23 - 2010-02-13
17599 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
17600 again on the latest OS X, and updates the location of a directory
17603 o Major bugfixes (performance):
17604 - We were selecting our guards uniformly at random, and then weighting
17605 which of our guards we'd use uniformly at random. This imbalance
17606 meant that Tor clients were severely limited on throughput (and
17607 probably latency too) by the first hop in their circuit. Now we
17608 select guards weighted by currently advertised bandwidth. We also
17609 automatically discard guards picked using the old algorithm. Fixes
17610 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17613 - Make Tor work again on the latest OS X: when deciding whether to
17614 use strange flags to turn TLS renegotiation on, detect the OpenSSL
17615 version at run-time, not compile time. We need to do this because
17616 Apple doesn't update its dev-tools headers when it updates its
17617 libraries in a security patch.
17618 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
17619 that could happen on 32-bit platforms with 64-bit time_t. Also fix
17620 a memory leak when requesting a hidden service descriptor we've
17621 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
17624 o Directory authority changes:
17625 - Change IP address for dannenberg (v3 directory authority), and
17626 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
17627 service directory authority) from the list.
17630 - Refactor resolve_my_address() to not use gethostbyname() anymore.
17631 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
17634 - Avoid a mad rush at the beginning of each month when each client
17635 rotates half of its guards. Instead we spread the rotation out
17636 throughout the month, but we still avoid leaving a precise timestamp
17637 in the state file about when we first picked the guard. Improves
17638 over the behavior introduced in 0.1.2.17.
17641 Changes in version 0.2.2.8-alpha - 2010-01-26
17642 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
17643 causing bridge relays to disappear. If you're running a bridge,
17647 - Fix a memory corruption bug on bridges that occured during the
17648 inclusion of stats data in extra-info descriptors. Also fix the
17649 interface for geoip_get_bridge_stats* to prevent similar bugs in
17650 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
17651 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
17654 - Ignore OutboundBindAddress when connecting to localhost.
17655 Connections to localhost need to come _from_ localhost, or else
17656 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
17660 Changes in version 0.2.2.7-alpha - 2010-01-19
17661 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
17662 as laying the groundwork for further relay-side performance fixes. It
17663 also starts cleaning up client behavior with respect to the EntryNodes,
17664 ExitNodes, and StrictNodes config options.
17666 This release also rotates two directory authority keys, due to a
17667 security breach of some of the Torproject servers.
17669 o Directory authority changes:
17670 - Rotate keys (both v3 identity and relay identity) for moria1
17673 o Major features (performance):
17674 - We were selecting our guards uniformly at random, and then weighting
17675 which of our guards we'd use uniformly at random. This imbalance
17676 meant that Tor clients were severely limited on throughput (and
17677 probably latency too) by the first hop in their circuit. Now we
17678 select guards weighted by currently advertised bandwidth. We also
17679 automatically discard guards picked using the old algorithm. Fixes
17680 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17681 - When choosing which cells to relay first, relays can now favor
17682 circuits that have been quiet recently, to provide lower latency
17683 for low-volume circuits. By default, relays enable or disable this
17684 feature based on a setting in the consensus. You can override
17685 this default by using the new "CircuitPriorityHalflife" config
17686 option. Design and code by Ian Goldberg, Can Tang, and Chris
17688 - Add separate per-conn write limiting to go with the per-conn read
17689 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
17690 but never per-conn write limits.
17691 - New consensus params "bwconnrate" and "bwconnburst" to let us
17692 rate-limit client connections as they enter the network. It's
17693 controlled in the consensus so we can turn it on and off for
17694 experiments. It's starting out off. Based on proposal 163.
17696 o Major features (relay selection options):
17697 - Switch to a StrictNodes config option, rather than the previous
17698 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
17699 "StrictExcludeNodes" option.
17700 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
17701 change during a config reload, mark and discard all our origin
17702 circuits. This fix should address edge cases where we change the
17703 config options and but then choose a circuit that we created before
17705 - If EntryNodes or ExitNodes are set, be more willing to use an
17706 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
17708 - Make EntryNodes config option much more aggressive even when
17709 StrictNodes is not set. Before it would prepend your requested
17710 entrynodes to your list of guard nodes, but feel free to use others
17711 after that. Now it chooses only from your EntryNodes if any of
17712 those are available, and only falls back to others if a) they're
17713 all down and b) StrictNodes is not set.
17714 - Now we refresh your entry guards from EntryNodes at each consensus
17715 fetch -- rather than just at startup and then they slowly rot as
17716 the network changes.
17719 - Stop bridge directory authorities from answering dbg-stability.txt
17720 directory queries, which would let people fetch a list of all
17721 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17724 - Log a notice when we get a new control connection. Now it's easier
17725 for security-conscious users to recognize when a local application
17726 is knocking on their controller door. Suggested by bug 1196.
17727 - New config option "CircuitStreamTimeout" to override our internal
17728 timeout schedule for how many seconds until we detach a stream from
17729 a circuit and try a new circuit. If your network is particularly
17730 slow, you might want to set this to a number like 60.
17731 - New controller command "getinfo config-text". It returns the
17732 contents that Tor would write if you send it a SAVECONF command,
17733 so the controller can write the file to disk itself.
17734 - New options for SafeLogging to allow scrubbing only log messages
17735 generated while acting as a relay.
17736 - Ship the bridges spec file in the tarball too.
17737 - Avoid a mad rush at the beginning of each month when each client
17738 rotates half of its guards. Instead we spread the rotation out
17739 throughout the month, but we still avoid leaving a precise timestamp
17740 in the state file about when we first picked the guard. Improves
17741 over the behavior introduced in 0.1.2.17.
17743 o Minor bugfixes (compiling):
17744 - Fix compilation on OS X 10.3, which has a stub mlockall() but
17745 hides it. Bugfix on 0.2.2.6-alpha.
17746 - Fix compilation on Solaris by removing support for the
17747 DisableAllSwap config option. Solaris doesn't have an rlimit for
17748 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
17751 o Minor bugfixes (crashes):
17752 - Do not segfault when writing buffer stats when we haven't observed
17753 a single circuit to report about. Found by Fabian Lanze. Bugfix on
17755 - If we're in the pathological case where there's no exit bandwidth
17756 but there is non-exit bandwidth, or no guard bandwidth but there
17757 is non-guard bandwidth, don't crash during path selection. Bugfix
17759 - Fix an impossible-to-actually-trigger buffer overflow in relay
17760 descriptor generation. Bugfix on 0.1.0.15.
17762 o Minor bugfixes (privacy):
17763 - Fix an instance where a Tor directory mirror might accidentally
17764 log the IP address of a misbehaving Tor client. Bugfix on
17766 - Don't list Windows capabilities in relay descriptors. We never made
17767 use of them, and maybe it's a bad idea to publish them. Bugfix
17770 o Minor bugfixes (other):
17771 - Resolve an edge case in path weighting that could make us misweight
17772 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
17773 - Fix statistics on client numbers by country as seen by bridges that
17774 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
17775 intervals instead of variable 12-to-48-hour intervals.
17776 - After we free an internal connection structure, overwrite it
17777 with a different memory value than we use for overwriting a freed
17778 internal circuit structure. Should help with debugging. Suggested
17780 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
17783 o Removed features:
17784 - Remove the HSAuthorityRecordStats option that version 0 hidden
17785 service authorities could have used to track statistics of overall
17786 hidden service usage.
17789 Changes in version 0.2.1.22 - 2010-01-19
17790 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
17791 authorities -- it would tell you its whole history of bridge descriptors
17792 if you make the right directory request. This stable update also
17793 rotates two of the seven v3 directory authority keys and locations.
17795 o Directory authority changes:
17796 - Rotate keys (both v3 identity and relay identity) for moria1
17800 - Stop bridge directory authorities from answering dbg-stability.txt
17801 directory queries, which would let people fetch a list of all
17802 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17805 Changes in version 0.2.1.21 - 2009-12-21
17806 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
17807 library. If you use Tor on Linux / Unix and you're getting SSL
17808 renegotiation errors, upgrading should help. We also recommend an
17809 upgrade if you're an exit relay.
17812 - Work around a security feature in OpenSSL 0.9.8l that prevents our
17813 handshake from working unless we explicitly tell OpenSSL that we
17814 are using SSL renegotiation safely. We are, of course, but OpenSSL
17815 0.9.8l won't work unless we say we are.
17816 - Avoid crashing if the client is trying to upload many bytes and the
17817 circuit gets torn down at the same time, or if the flip side
17818 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
17821 - Do not refuse to learn about authority certs and v2 networkstatus
17822 documents that are older than the latest consensus. This bug might
17823 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
17824 Spotted and fixed by xmux.
17825 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
17826 trigger platform-specific option misparsing case found by Coverity
17828 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
17829 trigger assert. Fixes bug 1173.
17832 Changes in version 0.2.2.6-alpha - 2009-11-19
17833 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
17834 support for the new lower-footprint "microdescriptor" directory design,
17835 future-proofing our consensus format against new hash functions or
17836 other changes, and an Android port. It also makes Tor compatible with
17837 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
17840 - Directory authorities can now create, vote on, and serve multiple
17841 parallel formats of directory data as part of their voting process.
17842 Partially implements Proposal 162: "Publish the consensus in
17844 - Directory authorities can now agree on and publish small summaries
17845 of router information that clients can use in place of regular
17846 server descriptors. This transition will eventually allow clients
17847 to use far less bandwidth for downloading information about the
17848 network. Begins the implementation of Proposal 158: "Clients
17849 download consensus + microdescriptors".
17850 - The directory voting system is now extensible to use multiple hash
17851 algorithms for signatures and resource selection. Newer formats
17852 are signed with SHA256, with a possibility for moving to a better
17853 hash algorithm in the future.
17854 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
17855 current and future memory pages via mlockall(). On supported
17856 platforms (modern Linux and probably BSD but not Windows or OS X),
17857 this should effectively disable any and all attempts to page out
17858 memory. This option requires that you start your Tor as root --
17859 if you use DisableAllSwap, please consider using the User option
17860 to properly reduce the privileges of your Tor.
17861 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
17862 to help Tor build correctly for Android phones.
17865 - Work around a security feature in OpenSSL 0.9.8l that prevents our
17866 handshake from working unless we explicitly tell OpenSSL that we
17867 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
17868 won't work unless we say we are.
17871 - Fix a crash bug when trying to initialize the evdns module in
17872 Libevent 2. Bugfix on 0.2.1.16-rc.
17873 - Stop logging at severity 'warn' when some other Tor client tries
17874 to establish a circuit with us using weak DH keys. It's a protocol
17875 violation, but that doesn't mean ordinary users need to hear about
17876 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
17877 - Do not refuse to learn about authority certs and v2 networkstatus
17878 documents that are older than the latest consensus. This bug might
17879 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
17880 Spotted and fixed by xmux.
17881 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
17882 - If all authorities restart at once right before a consensus vote,
17883 nobody will vote about "Running", and clients will get a consensus
17884 with no usable relays. Instead, authorities refuse to build a
17885 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
17886 - If your relay can't keep up with the number of incoming create
17887 cells, it would log one warning per failure into your logs. Limit
17888 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
17889 - Bridges now use "reject *:*" as their default exit policy. Bugfix
17890 on 0.2.0.3-alpha; fixes bug 1113.
17891 - Fix a memory leak on directory authorities during voting that was
17892 introduced in 0.2.2.1-alpha. Found via valgrind.
17895 Changes in version 0.2.1.20 - 2009-10-15
17896 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
17897 services at once, prepares for more performance improvements, and
17898 fixes a bunch of smaller bugs.
17900 The Windows and OS X bundles also include a more recent Vidalia,
17901 and switch from Privoxy to Polipo.
17903 The OS X installers are now drag and drop. It's best to un-install
17904 Tor/Vidalia and then install this new bundle, rather than upgrade. If
17905 you want to upgrade, you'll need to update the paths for Tor and Polipo
17906 in the Vidalia Settings window.
17909 - Send circuit or stream sendme cells when our window has decreased
17910 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
17911 by Karsten when testing the "reduce circuit window" performance
17912 patch. Bugfix on the 54th commit on Tor -- from July 2002,
17913 before the release of Tor 0.0.0. This is the new winner of the
17915 - Fix a remotely triggerable memory leak when a consensus document
17916 contains more than one signature from the same voter. Bugfix on
17918 - Avoid segfault in rare cases when finishing an introduction circuit
17919 as a client and finding out that we don't have an introduction key
17920 for it. Fixes bug 1073. Reported by Aaron Swartz.
17923 - Tor now reads the "circwindow" parameter out of the consensus,
17924 and uses that value for its circuit package window rather than the
17925 default of 1000 cells. Begins the implementation of proposal 168.
17927 o New directory authorities:
17928 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
17930 - Move moria1 and tonga to alternate IP addresses.
17933 - Fix a signed/unsigned compile warning in 0.2.1.19.
17934 - Fix possible segmentation fault on directory authorities. Bugfix on
17936 - Fix an extremely rare infinite recursion bug that could occur if
17937 we tried to log a message after shutting down the log subsystem.
17938 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
17939 - Fix an obscure bug where hidden services on 64-bit big-endian
17940 systems might mis-read the timestamp in v3 introduce cells, and
17941 refuse to connect back to the client. Discovered by "rotor".
17942 Bugfix on 0.2.1.6-alpha.
17943 - We were triggering a CLOCK_SKEW controller status event whenever
17944 we connect via the v2 connection protocol to any relay that has
17945 a wrong clock. Instead, we should only inform the controller when
17946 it's a trusted authority that claims our clock is wrong. Bugfix
17947 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
17948 - We were telling the controller about CHECKING_REACHABILITY and
17949 REACHABILITY_FAILED status events whenever we launch a testing
17950 circuit or notice that one has failed. Instead, only tell the
17951 controller when we want to inform the user of overall success or
17952 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
17954 - Don't warn when we're using a circuit that ends with a node
17955 excluded in ExcludeExitNodes, but the circuit is not used to access
17956 the outside world. This should help fix bug 1090. Bugfix on
17958 - Work around a small memory leak in some versions of OpenSSL that
17959 stopped the memory used by the hostname TLS extension from being
17963 - Add a "getinfo status/accepted-server-descriptor" controller
17964 command, which is the recommended way for controllers to learn
17965 whether our server descriptor has been successfully received by at
17966 least on directory authority. Un-recommend good-server-descriptor
17967 getinfo and status events until we have a better design for them.
17970 Changes in version 0.2.2.5-alpha - 2009-10-11
17971 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
17974 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
17976 o Directory authorities:
17977 - Temporarily (just for this release) move dizum to an alternate
17981 Changes in version 0.2.2.4-alpha - 2009-10-10
17982 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
17983 introduces a new unit test framework, shifts directry authority
17984 addresses around to reduce the impact from recent blocking events,
17985 and fixes a few smaller bugs.
17988 - Fix several more asserts in the circuit_build_times code, for
17989 example one that causes Tor to fail to start once we have
17990 accumulated 5000 build times in the state file. Bugfixes on
17991 0.2.2.2-alpha; fixes bug 1108.
17993 o New directory authorities:
17994 - Move moria1 and Tonga to alternate IP addresses.
17997 - Log SSL state transitions at debug level during handshake, and
17998 include SSL states in error messages. This may help debug future
17999 SSL handshake issues.
18000 - Add a new "Handshake" log domain for activities that happen
18001 during the TLS handshake.
18002 - Revert to the "June 3 2009" ip-to-country file. The September one
18003 seems to have removed most US IP addresses.
18004 - Directory authorities now reject Tor relays with versions less than
18005 0.1.2.14. This step cuts out four relays from the current network,
18006 none of which are very big.
18009 - Fix a couple of smaller issues with gathering statistics. Bugfixes
18011 - Fix two memory leaks in the error case of
18012 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
18013 - Don't count one-hop circuits when we're estimating how long it
18014 takes circuits to build on average. Otherwise we'll set our circuit
18015 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
18016 - Directory authorities no longer change their opinion of, or vote on,
18017 whether a router is Running, unless they have themselves been
18018 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
18021 o Code simplifications and refactoring:
18022 - Revise our unit tests to use the "tinytest" framework, so we
18023 can run tests in their own processes, have smarter setup/teardown
18024 code, and so on. The unit test code has moved to its own
18025 subdirectory, and has been split into multiple modules.
18028 Changes in version 0.2.2.3-alpha - 2009-09-23
18029 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
18032 - Fix an overzealous assert in our new circuit build timeout code.
18033 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
18036 - If the networkstatus consensus tells us that we should use a
18037 negative circuit package window, ignore it. Otherwise we'll
18038 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
18041 Changes in version 0.2.2.2-alpha - 2009-09-21
18042 Tor 0.2.2.2-alpha introduces our latest performance improvement for
18043 clients: Tor tracks the average time it takes to build a circuit, and
18044 avoids using circuits that take too long to build. For fast connections,
18045 this feature can cut your expected latency in half. For slow or flaky
18046 connections, it could ruin your Tor experience. Let us know if it does!
18049 - Tor now tracks how long it takes to build client-side circuits
18050 over time, and adapts its timeout to local network performance.
18051 Since a circuit that takes a long time to build will also provide
18052 bad performance, we get significant latency improvements by
18053 discarding the slowest 20% of circuits. Specifically, Tor creates
18054 circuits more aggressively than usual until it has enough data
18055 points for a good timeout estimate. Implements proposal 151.
18056 We are especially looking for reports (good and bad) from users with
18057 both EDGE and broadband connections that can move from broadband
18058 to EDGE and find out if the build-time data in the .tor/state gets
18059 reset without loss of Tor usability. You should also see a notice
18060 log message telling you that Tor has reset its timeout.
18061 - Directory authorities can now vote on arbitary integer values as
18062 part of the consensus process. This is designed to help set
18063 network-wide parameters. Implements proposal 167.
18064 - Tor now reads the "circwindow" parameter out of the consensus,
18065 and uses that value for its circuit package window rather than the
18066 default of 1000 cells. Begins the implementation of proposal 168.
18069 - Fix a remotely triggerable memory leak when a consensus document
18070 contains more than one signature from the same voter. Bugfix on
18074 - Fix an extremely rare infinite recursion bug that could occur if
18075 we tried to log a message after shutting down the log subsystem.
18076 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
18077 - Fix parsing for memory or time units given without a space between
18078 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
18079 - A networkstatus vote must contain exactly one signature. Spec
18080 conformance issue. Bugfix on 0.2.0.3-alpha.
18081 - Fix an obscure bug where hidden services on 64-bit big-endian
18082 systems might mis-read the timestamp in v3 introduce cells, and
18083 refuse to connect back to the client. Discovered by "rotor".
18084 Bugfix on 0.2.1.6-alpha.
18085 - We were triggering a CLOCK_SKEW controller status event whenever
18086 we connect via the v2 connection protocol to any relay that has
18087 a wrong clock. Instead, we should only inform the controller when
18088 it's a trusted authority that claims our clock is wrong. Bugfix
18089 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
18090 - We were telling the controller about CHECKING_REACHABILITY and
18091 REACHABILITY_FAILED status events whenever we launch a testing
18092 circuit or notice that one has failed. Instead, only tell the
18093 controller when we want to inform the user of overall success or
18094 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
18096 - Don't warn when we're using a circuit that ends with a node
18097 excluded in ExcludeExitNodes, but the circuit is not used to access
18098 the outside world. This should help fix bug 1090, but more problems
18099 remain. Bugfix on 0.2.1.6-alpha.
18100 - Work around a small memory leak in some versions of OpenSSL that
18101 stopped the memory used by the hostname TLS extension from being
18103 - Make our 'torify' script more portable; if we have only one of
18104 'torsocks' or 'tsocks' installed, don't complain to the user;
18105 and explain our warning about tsocks better.
18108 - Add a "getinfo status/accepted-server-descriptor" controller
18109 command, which is the recommended way for controllers to learn
18110 whether our server descriptor has been successfully received by at
18111 least on directory authority. Un-recommend good-server-descriptor
18112 getinfo and status events until we have a better design for them.
18113 - Update to the "September 4 2009" ip-to-country file.
18116 Changes in version 0.2.2.1-alpha - 2009-08-26
18117 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
18118 Tor clients to bootstrap on networks where only port 80 is reachable,
18119 makes it more straightforward to support hardware crypto accelerators,
18120 and starts the groundwork for gathering stats safely at relays.
18123 - Start the process of disabling ".exit" address notation, since it
18124 can be used for a variety of esoteric application-level attacks
18125 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
18128 o New directory authorities:
18129 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
18133 - New AccelName and AccelDir options add support for dynamic OpenSSL
18134 hardware crypto acceleration engines.
18135 - Tor now supports tunneling all of its outgoing connections over
18136 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
18137 configuration options. Code by Christopher Davis.
18140 - Send circuit or stream sendme cells when our window has decreased
18141 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
18142 by Karsten when testing the "reduce circuit window" performance
18143 patch. Bugfix on the 54th commit on Tor -- from July 2002,
18144 before the release of Tor 0.0.0. This is the new winner of the
18147 o New options for gathering stats safely:
18148 - Directory mirrors that set "DirReqStatistics 1" write statistics
18149 about directory requests to disk every 24 hours. As compared to the
18150 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
18151 1) stats are written to disk exactly every 24 hours; 2) estimated
18152 shares of v2 and v3 requests are determined as mean values, not at
18153 the end of a measurement period; 3) unresolved requests are listed
18154 with country code '??'; 4) directories also measure download times.
18155 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
18156 number of exit streams and transferred bytes per port to disk every
18158 - Relays that set "CellStatistics 1" write statistics on how long
18159 cells spend in their circuit queues to disk every 24 hours.
18160 - Entry nodes that set "EntryStatistics 1" write statistics on the
18161 rough number and origins of connecting clients to disk every 24
18163 - Relays that write any of the above statistics to disk and set
18164 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
18165 their extra-info documents.
18168 - New --digests command-line switch to output the digests of the
18169 source files Tor was built with.
18170 - The "torify" script now uses torsocks where available.
18171 - The memarea code now uses a sentinel value at the end of each area
18172 to make sure nothing writes beyond the end of an area. This might
18173 help debug some conceivable causes of bug 930.
18174 - Time and memory units in the configuration file can now be set to
18175 fractional units. For example, "2.5 GB" is now a valid value for
18177 - Certain Tor clients (such as those behind check.torproject.org) may
18178 want to fetch the consensus in an extra early manner. To enable this
18179 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
18180 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
18181 as only certain clients who must have this information sooner should
18183 - Instead of adding the svn revision to the Tor version string, report
18184 the git commit (when we're building from a git checkout).
18187 - If any of the v3 certs we download are unparseable, we should
18188 actually notice the failure so we don't retry indefinitely. Bugfix
18189 on 0.2.0.x; reported by "rotator".
18190 - If the cached cert file is unparseable, warn but don't exit.
18191 - Fix possible segmentation fault on directory authorities. Bugfix on
18193 - When Tor fails to parse a descriptor of any kind, dump it to disk.
18194 Might help diagnosing bug 1051.
18196 o Deprecated and removed features:
18197 - The controller no longer accepts the old obsolete "addr-mappings/"
18198 or "unregistered-servers-" GETINFO values.
18199 - Hidden services no longer publish version 0 descriptors, and clients
18200 do not request or use version 0 descriptors. However, the old hidden
18201 service authorities still accept and serve version 0 descriptors
18202 when contacted by older hidden services/clients.
18203 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
18204 always on; using them is necessary for correct forward-compatible
18206 - Remove support for .noconnect style addresses. Nobody was using
18207 them, and they provided another avenue for detecting Tor users
18208 via application-level web tricks.
18210 o Packaging changes:
18211 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
18212 installer bundles. See
18213 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
18214 for details of what's new in Vidalia 0.2.3.
18215 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
18216 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
18217 configuration file, rather than the old Privoxy.
18218 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
18219 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
18220 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
18221 better compatibility with OS X 10.6, aka Snow Leopard.
18222 - OS X Vidalia Bundle: The multi-package installer is now replaced
18223 by a simple drag and drop to the /Applications folder. This change
18224 occurred with the upgrade to Vidalia 0.2.3.
18227 Changes in version 0.2.1.19 - 2009-07-28
18228 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
18229 services on Tor 0.2.1.3-alpha through 0.2.1.18.
18232 - Make accessing hidden services on 0.2.1.x work right again.
18233 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
18234 part of patch provided by "optimist".
18237 - When a relay/bridge is writing out its identity key fingerprint to
18238 the "fingerprint" file and to its logs, write it without spaces. Now
18239 it will look like the fingerprints in our bridges documentation,
18240 and confuse fewer users.
18243 - Relays no longer publish a new server descriptor if they change
18244 their MaxAdvertisedBandwidth config option but it doesn't end up
18245 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
18246 fixes bug 1026. Patch from Sebastian.
18247 - Avoid leaking memory every time we get a create cell but we have
18248 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
18249 fixes bug 1034. Reported by BarkerJr.
18252 Changes in version 0.2.1.18 - 2009-07-24
18253 Tor 0.2.1.18 lays the foundations for performance improvements,
18254 adds status events to help users diagnose bootstrap problems, adds
18255 optional authentication/authorization for hidden services, fixes a
18256 variety of potential anonymity problems, and includes a huge pile of
18257 other features and bug fixes.
18260 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
18263 Changes in version 0.2.1.17-rc - 2009-07-07
18264 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
18265 candidate for the 0.2.1.x series. It lays the groundwork for further
18266 client performance improvements, and also fixes a big bug with directory
18267 authorities that were causing them to assign Guard and Stable flags
18270 The Windows bundles also finally include the geoip database that we
18271 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
18272 should actually install Torbutton rather than giving you a cryptic
18273 failure message (oops).
18276 - Clients now use the bandwidth values in the consensus, rather than
18277 the bandwidth values in each relay descriptor. This approach opens
18278 the door to more accurate bandwidth estimates once the directory
18279 authorities start doing active measurements. Implements more of
18283 - When Tor clients restart after 1-5 days, they discard all their
18284 cached descriptors as too old, but they still use the cached
18285 consensus document. This approach is good for robustness, but
18286 bad for performance: since they don't know any bandwidths, they
18287 end up choosing at random rather than weighting their choice by
18288 speed. Fixed by the above feature of putting bandwidths in the
18289 consensus. Bugfix on 0.2.0.x.
18290 - Directory authorities were neglecting to mark relays down in their
18291 internal histories if the relays fall off the routerlist without
18292 ever being found unreachable. So there were relays in the histories
18293 that haven't been seen for eight months, and are listed as being
18294 up for eight months. This wreaked havoc on the "median wfu"
18295 and "median mtbf" calculations, in turn making Guard and Stable
18296 flags very wrong, hurting network performance. Fixes bugs 696 and
18297 969. Bugfix on 0.2.0.6-alpha.
18300 - Serve the DirPortFrontPage page even when we have been approaching
18301 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
18302 - The control port would close the connection before flushing long
18303 replies, such as the network consensus, if a QUIT command was issued
18304 before the reply had completed. Now, the control port flushes all
18305 pending replies before closing the connection. Also fixed a spurious
18306 warning when a QUIT command is issued after a malformed or rejected
18307 AUTHENTICATE command, but before the connection was closed. Patch
18308 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
18309 - When we can't find an intro key for a v2 hidden service descriptor,
18310 fall back to the v0 hidden service descriptor and log a bug message.
18311 Workaround for bug 1024.
18312 - Fix a log message that did not respect the SafeLogging option.
18316 - If we're a relay and we change our IP address, be more verbose
18317 about the reason that made us change. Should help track down
18318 further bugs for relays on dynamic IP addresses.
18321 Changes in version 0.2.0.35 - 2009-06-24
18323 - Avoid crashing in the presence of certain malformed descriptors.
18324 Found by lark, and by automated fuzzing.
18325 - Fix an edge case where a malicious exit relay could convince a
18326 controller that the client's DNS question resolves to an internal IP
18327 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
18330 - Finally fix the bug where dynamic-IP relays disappear when their
18331 IP address changes: directory mirrors were mistakenly telling
18332 them their old address if they asked via begin_dir, so they
18333 never got an accurate answer about their new address, so they
18334 just vanished after a day. For belt-and-suspenders, relays that
18335 don't set Address in their config now avoid using begin_dir for
18336 all direct connections. Should fix bugs 827, 883, and 900.
18337 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
18338 that would occur on some exit nodes when DNS failures and timeouts
18339 occurred in certain patterns. Fix for bug 957.
18342 - When starting with a cache over a few days old, do not leak
18343 memory for the obsolete router descriptors in it. Bugfix on
18344 0.2.0.33; fixes bug 672.
18345 - Hidden service clients didn't use a cached service descriptor that
18346 was older than 15 minutes, but wouldn't fetch a new one either,
18347 because there was already one in the cache. Now, fetch a v2
18348 descriptor unless the same descriptor was added to the cache within
18349 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
18352 Changes in version 0.2.1.16-rc - 2009-06-20
18353 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
18354 a bunch of minor bugs.
18357 - Fix an edge case where a malicious exit relay could convince a
18358 controller that the client's DNS question resolves to an internal IP
18359 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
18361 o Major performance improvements (on 0.2.0.x):
18362 - Disable and refactor some debugging checks that forced a linear scan
18363 over the whole server-side DNS cache. These accounted for over 50%
18364 of CPU time on a relatively busy exit node's gprof profile. Found
18366 - Disable some debugging checks that appeared in exit node profile
18370 - Update to the "June 3 2009" ip-to-country file.
18371 - Do not have tor-resolve automatically refuse all .onion addresses;
18372 if AutomapHostsOnResolve is set in your torrc, this will work fine.
18374 o Minor bugfixes (on 0.2.0.x):
18375 - Log correct error messages for DNS-related network errors on
18377 - Fix a race condition that could cause crashes or memory corruption
18378 when running as a server with a controller listening for log
18380 - Avoid crashing when we have a policy specified in a DirPolicy or
18381 SocksPolicy or ReachableAddresses option with ports set on it,
18382 and we re-load the policy. May fix bug 996.
18383 - Hidden service clients didn't use a cached service descriptor that
18384 was older than 15 minutes, but wouldn't fetch a new one either,
18385 because there was already one in the cache. Now, fetch a v2
18386 descriptor unless the same descriptor was added to the cache within
18387 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
18389 o Minor bugfixes (on 0.2.1.x):
18390 - Don't warn users about low port and hibernation mix when they
18391 provide a *ListenAddress directive to fix that. Bugfix on
18393 - When switching back and forth between bridge mode, do not start
18394 gathering GeoIP data until two hours have passed.
18395 - Do not complain that the user has requested an excluded node as
18396 an exit when the node is not really an exit. This could happen
18397 because the circuit was for testing, or an introduction point.
18401 Changes in version 0.2.1.15-rc - 2009-05-25
18402 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
18403 series. It fixes a major bug on fast exit relays, as well as a variety
18404 of more minor bugs.
18406 o Major bugfixes (on 0.2.0.x):
18407 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
18408 that would occur on some exit nodes when DNS failures and timeouts
18409 occurred in certain patterns. Fix for bug 957.
18411 o Minor bugfixes (on 0.2.0.x):
18412 - Actually return -1 in the error case for read_bandwidth_usage().
18413 Harmless bug, since we currently don't care about the return value
18414 anywhere. Bugfix on 0.2.0.9-alpha.
18415 - Provide a more useful log message if bug 977 (related to buffer
18416 freelists) ever reappears, and do not crash right away.
18417 - Fix an assertion failure on 64-bit platforms when we allocated
18418 memory right up to the end of a memarea, then realigned the memory
18419 one step beyond the end. Fixes a possible cause of bug 930.
18420 - Protect the count of open sockets with a mutex, so we can't
18421 corrupt it when two threads are closing or opening sockets at once.
18422 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
18423 - Don't allow a bridge to publish its router descriptor to a
18424 non-bridge directory authority. Fixes part of bug 932.
18425 - When we change to or from being a bridge, reset our counts of
18426 client usage by country. Fixes bug 932.
18427 - Fix a bug that made stream bandwidth get misreported to the
18429 - Stop using malloc_usable_size() to use more area than we had
18430 actually allocated: it was safe, but made valgrind really unhappy.
18431 - Fix a memory leak when v3 directory authorities load their keys
18432 and cert from disk. Bugfix on 0.2.0.1-alpha.
18434 o Minor bugfixes (on 0.2.1.x):
18435 - Fix use of freed memory when deciding to mark a non-addable
18436 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
18439 Changes in version 0.2.1.14-rc - 2009-04-12
18440 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
18441 series. It begins fixing some major performance problems, and also
18442 finally addresses the bug that was causing relays on dynamic IP
18443 addresses to fall out of the directory.
18446 - Clients replace entry guards that were chosen more than a few months
18447 ago. This change should significantly improve client performance,
18448 especially once more people upgrade, since relays that have been
18449 a guard for a long time are currently overloaded.
18451 o Major bugfixes (on 0.2.0):
18452 - Finally fix the bug where dynamic-IP relays disappear when their
18453 IP address changes: directory mirrors were mistakenly telling
18454 them their old address if they asked via begin_dir, so they
18455 never got an accurate answer about their new address, so they
18456 just vanished after a day. For belt-and-suspenders, relays that
18457 don't set Address in their config now avoid using begin_dir for
18458 all direct connections. Should fix bugs 827, 883, and 900.
18459 - Relays were falling out of the networkstatus consensus for
18460 part of a day if they changed their local config but the
18461 authorities discarded their new descriptor as "not sufficiently
18462 different". Now directory authorities accept a descriptor as changed
18463 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
18464 patch by Sebastian.
18465 - Avoid crashing in the presence of certain malformed descriptors.
18466 Found by lark, and by automated fuzzing.
18469 - When generating circuit events with verbose nicknames for
18470 controllers, try harder to look up nicknames for routers on a
18471 circuit. (Previously, we would look in the router descriptors we had
18472 for nicknames, but not in the consensus.) Partial fix for bug 941.
18473 - If the bridge config line doesn't specify a port, assume 443.
18474 This makes bridge lines a bit smaller and easier for users to
18476 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
18477 bytes (aka 20KB/s), to match our documentation. Also update
18478 directory authorities so they always assign the Fast flag to relays
18479 with 20KB/s of capacity. Now people running relays won't suddenly
18480 find themselves not seeing any use, if the network gets faster
18482 - Update to the "April 3 2009" ip-to-country file.
18485 - Avoid trying to print raw memory to the logs when we decide to
18486 give up on downloading a given relay descriptor. Bugfix on
18488 - In tor-resolve, when the Tor client to use is specified by
18489 <hostname>:<port>, actually use the specified port rather than
18490 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
18491 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
18492 - When starting with a cache over a few days old, do not leak
18493 memory for the obsolete router descriptors in it. Bugfix on
18495 - Avoid double-free on list of successfully uploaded hidden
18496 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
18497 - Change memarea_strndup() implementation to work even when
18498 duplicating a string at the end of a page. This bug was
18499 harmless for now, but could have meant crashes later. Fix by
18500 lark. Bugfix on 0.2.1.1-alpha.
18501 - Limit uploaded directory documents to be 16M rather than 500K.
18502 The directory authorities were refusing v3 consensus votes from
18503 other authorities, since the votes are now 504K. Fixes bug 959;
18504 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
18505 - Directory authorities should never send a 503 "busy" response to
18506 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
18510 Changes in version 0.2.1.13-alpha - 2009-03-09
18511 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
18512 cleanups. We're finally getting close to a release candidate.
18515 - Correctly update the list of which countries we exclude as
18516 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
18517 lark. Bugfix on 0.2.1.6-alpha.
18519 o Minor bugfixes (on 0.2.0.x and earlier):
18520 - Automatically detect MacOSX versions earlier than 10.4.0, and
18521 disable kqueue from inside Tor when running with these versions.
18522 We previously did this from the startup script, but that was no
18523 help to people who didn't use the startup script. Resolves bug 863.
18524 - When we had picked an exit node for a connection, but marked it as
18525 "optional", and it turned out we had no onion key for the exit,
18526 stop wanting that exit and try again. This situation may not
18527 be possible now, but will probably become feasible with proposal
18528 158. Spotted by rovv. Fixes another case of bug 752.
18529 - Clients no longer cache certificates for authorities they do not
18530 recognize. Bugfix on 0.2.0.9-alpha.
18531 - When we can't transmit a DNS request due to a network error, retry
18532 it after a while, and eventually transmit a failing response to
18533 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
18534 - If the controller claimed responsibility for a stream, but that
18535 stream never finished making its connection, it would live
18536 forever in circuit_wait state. Now we close it after SocksTimeout
18537 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
18538 - Drop begin cells to a hidden service if they come from the middle
18539 of a circuit. Patch from lark.
18540 - When we erroneously receive two EXTEND cells for the same circuit
18541 ID on the same connection, drop the second. Patch from lark.
18542 - Fix a crash that occurs on exit nodes when a nameserver request
18543 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
18544 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
18546 - Do not assume that a stack-allocated character array will be
18547 64-bit aligned on platforms that demand that uint64_t access is
18548 aligned. Possible fix for bug 604.
18549 - Parse dates and IPv4 addresses in a locale- and libc-independent
18550 manner, to avoid platform-dependent behavior on malformed input.
18551 - Build correctly when configured to build outside the main source
18552 path. Patch from Michael Gold.
18553 - We were already rejecting relay begin cells with destination port
18554 of 0. Now also reject extend cells with destination port or address
18555 of 0. Suggested by lark.
18557 o Minor bugfixes (on 0.2.1.x):
18558 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
18559 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
18560 - If we're an exit node, scrub the IP address to which we are exiting
18561 in the logs. Bugfix on 0.2.1.8-alpha.
18564 - On Linux, use the prctl call to re-enable core dumps when the user
18566 - New controller event NEWCONSENSUS that lists the networkstatus
18567 lines for every recommended relay. Now controllers like Torflow
18568 can keep up-to-date on which relays they should be using.
18569 - Update to the "February 26 2009" ip-to-country file.
18572 Changes in version 0.2.0.34 - 2009-02-08
18573 Tor 0.2.0.34 features several more security-related fixes. You should
18574 upgrade, especially if you run an exit relay (remote crash) or a
18575 directory authority (remote infinite loop), or you're on an older
18576 (pre-XP) or not-recently-patched Windows (remote exploit).
18578 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
18579 have many known flaws, and nobody should be using them. You should
18580 upgrade. If you're using a Linux or BSD and its packages are obsolete,
18581 stop using those packages and upgrade anyway.
18584 - Fix an infinite-loop bug on handling corrupt votes under certain
18585 circumstances. Bugfix on 0.2.0.8-alpha.
18586 - Fix a temporary DoS vulnerability that could be performed by
18587 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
18588 - Avoid a potential crash on exit nodes when processing malformed
18589 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
18590 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
18591 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
18594 - Fix compilation on systems where time_t is a 64-bit integer.
18595 Patch from Matthias Drochner.
18596 - Don't consider expiring already-closed client connections. Fixes
18597 bug 893. Bugfix on 0.0.2pre20.
18600 Changes in version 0.2.1.12-alpha - 2009-02-08
18601 Tor 0.2.1.12-alpha features several more security-related fixes. You
18602 should upgrade, especially if you run an exit relay (remote crash) or
18603 a directory authority (remote infinite loop), or you're on an older
18604 (pre-XP) or not-recently-patched Windows (remote exploit). It also
18605 includes a big pile of minor bugfixes and cleanups.
18608 - Fix an infinite-loop bug on handling corrupt votes under certain
18609 circumstances. Bugfix on 0.2.0.8-alpha.
18610 - Fix a temporary DoS vulnerability that could be performed by
18611 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
18612 - Avoid a potential crash on exit nodes when processing malformed
18613 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
18616 - Let controllers actually ask for the "clients_seen" event for
18617 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
18618 reported by Matt Edman.
18619 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
18621 - Fix a bug in address parsing that was preventing bridges or hidden
18622 service targets from being at IPv6 addresses.
18623 - Solve a bug that kept hardware crypto acceleration from getting
18624 enabled when accounting was turned on. Fixes bug 907. Bugfix on
18626 - Remove a bash-ism from configure.in to build properly on non-Linux
18627 platforms. Bugfix on 0.2.1.1-alpha.
18628 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
18629 headers. Bugfix on 0.2.0.10-alpha.
18630 - Don't consider expiring already-closed client connections. Fixes
18631 bug 893. Bugfix on 0.0.2pre20.
18632 - Fix another interesting corner-case of bug 891 spotted by rovv:
18633 Previously, if two hosts had different amounts of clock drift, and
18634 one of them created a new connection with just the wrong timing,
18635 the other might decide to deprecate the new connection erroneously.
18636 Bugfix on 0.1.1.13-alpha.
18637 - Resolve a very rare crash bug that could occur when the user forced
18638 a nameserver reconfiguration during the middle of a nameserver
18639 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
18640 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
18641 Bugfix on 0.2.1.7-alpha.
18642 - If we're using bridges and our network goes away, be more willing
18643 to forgive our bridges and try again when we get an application
18644 request. Bugfix on 0.2.0.x.
18647 - Support platforms where time_t is 64 bits long. (Congratulations,
18648 NetBSD!) Patch from Matthias Drochner.
18649 - Add a 'getinfo status/clients-seen' controller command, in case
18650 controllers want to hear clients_seen events but connect late.
18653 - Disable GCC's strict alias optimization by default, to avoid the
18654 likelihood of its introducing subtle bugs whenever our code violates
18655 the letter of C99's alias rules.
18658 Changes in version 0.2.0.33 - 2009-01-21
18659 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
18660 useful to users. It also finally fixes a bug where a relay or client
18661 that's been off for many days would take a long time to bootstrap.
18663 This update also fixes an important security-related bug reported by
18664 Ilja van Sprundel. You should upgrade. (We'll send out more details
18665 about the bug once people have had some time to upgrade.)
18668 - Fix a heap-corruption bug that may be remotely triggerable on
18669 some platforms. Reported by Ilja van Sprundel.
18672 - When a stream at an exit relay is in state "resolving" or
18673 "connecting" and it receives an "end" relay cell, the exit relay
18674 would silently ignore the end cell and not close the stream. If
18675 the client never closes the circuit, then the exit relay never
18676 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
18677 reported by "wood".
18678 - When sending CREATED cells back for a given circuit, use a 64-bit
18679 connection ID to find the right connection, rather than an addr:port
18680 combination. Now that we can have multiple OR connections between
18681 the same ORs, it is no longer possible to use addr:port to uniquely
18682 identify a connection.
18683 - Bridge relays that had DirPort set to 0 would stop fetching
18684 descriptors shortly after startup, and then briefly resume
18685 after a new bandwidth test and/or after publishing a new bridge
18686 descriptor. Bridge users that try to bootstrap from them would
18687 get a recent networkstatus but would get descriptors from up to
18688 18 hours earlier, meaning most of the descriptors were obsolete
18689 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
18690 - Prevent bridge relays from serving their 'extrainfo' document
18691 to anybody who asks, now that extrainfo docs include potentially
18692 sensitive aggregated client geoip summaries. Bugfix on
18694 - If the cached networkstatus consensus is more than five days old,
18695 discard it rather than trying to use it. In theory it could be
18696 useful because it lists alternate directory mirrors, but in practice
18697 it just means we spend many minutes trying directory mirrors that
18698 are long gone from the network. Also discard router descriptors as
18699 we load them if they are more than five days old, since the onion
18700 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
18703 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
18704 could make gcc generate non-functional binary search code. Bugfix
18706 - Build correctly on platforms without socklen_t.
18707 - Compile without warnings on solaris.
18708 - Avoid potential crash on internal error during signature collection.
18709 Fixes bug 864. Patch from rovv.
18710 - Correct handling of possible malformed authority signing key
18711 certificates with internal signature types. Fixes bug 880.
18712 Bugfix on 0.2.0.3-alpha.
18713 - Fix a hard-to-trigger resource leak when logging credential status.
18715 - When we can't initialize DNS because the network is down, do not
18716 automatically stop Tor from starting. Instead, we retry failed
18717 dns_init() every 10 minutes, and change the exit policy to reject
18718 *:* until one succeeds. Fixes bug 691.
18719 - Use 64 bits instead of 32 bits for connection identifiers used with
18720 the controller protocol, to greatly reduce risk of identifier reuse.
18721 - When we're choosing an exit node for a circuit, and we have
18722 no pending streams, choose a good general exit rather than one that
18723 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
18724 - Fix another case of assuming, when a specific exit is requested,
18725 that we know more than the user about what hosts it allows.
18726 Fixes one case of bug 752. Patch from rovv.
18727 - Clip the MaxCircuitDirtiness config option to a minimum of 10
18728 seconds. Warn the user if lower values are given in the
18729 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
18730 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
18731 user if lower values are given in the configuration. Bugfix on
18732 0.1.1.17-rc. Patch by Sebastian.
18733 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
18734 the cache because we already had a v0 descriptor with the same ID.
18735 Bugfix on 0.2.0.18-alpha.
18736 - Fix a race condition when freeing keys shared between main thread
18737 and CPU workers that could result in a memory leak. Bugfix on
18738 0.1.0.1-rc. Fixes bug 889.
18739 - Send a valid END cell back when a client tries to connect to a
18740 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
18741 840. Patch from rovv.
18742 - Check which hops rendezvous stream cells are associated with to
18743 prevent possible guess-the-streamid injection attacks from
18744 intermediate hops. Fixes another case of bug 446. Based on patch
18746 - If a broken client asks a non-exit router to connect somewhere,
18747 do not even do the DNS lookup before rejecting the connection.
18748 Fixes another case of bug 619. Patch from rovv.
18749 - When a relay gets a create cell it can't decrypt (e.g. because it's
18750 using the wrong onion key), we were dropping it and letting the
18751 client time out. Now actually answer with a destroy cell. Fixes
18752 bug 904. Bugfix on 0.0.2pre8.
18754 o Minor bugfixes (hidden services):
18755 - Do not throw away existing introduction points on SIGHUP. Bugfix on
18756 0.0.6pre1. Patch by Karsten. Fixes bug 874.
18759 - Report the case where all signatures in a detached set are rejected
18760 differently than the case where there is an error handling the
18762 - When we realize that another process has modified our cached
18763 descriptors, print out a more useful error message rather than
18764 triggering an assertion. Fixes bug 885. Patch from Karsten.
18765 - Implement the 0x20 hack to better resist DNS poisoning: set the
18766 case on outgoing DNS requests randomly, and reject responses that do
18767 not match the case correctly. This logic can be disabled with the
18768 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
18769 of servers that do not reliably preserve case in replies. See
18770 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
18772 - Check DNS replies for more matching fields to better resist DNS
18774 - Never use OpenSSL compression: it wastes RAM and CPU trying to
18775 compress cells, which are basically all encrypted, compressed, or
18779 Changes in version 0.2.1.11-alpha - 2009-01-20
18780 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
18781 week it will take a long time to bootstrap again" bug. It also fixes
18782 an important security-related bug reported by Ilja van Sprundel. You
18783 should upgrade. (We'll send out more details about the bug once people
18784 have had some time to upgrade.)
18787 - Fix a heap-corruption bug that may be remotely triggerable on
18788 some platforms. Reported by Ilja van Sprundel.
18791 - Discard router descriptors as we load them if they are more than
18792 five days old. Otherwise if Tor is off for a long time and then
18793 starts with cached descriptors, it will try to use the onion
18794 keys in those obsolete descriptors when building circuits. Bugfix
18795 on 0.2.0.x. Fixes bug 887.
18798 - Try to make sure that the version of Libevent we're running with
18799 is binary-compatible with the one we built with. May address bug
18801 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
18802 for bug 905. Bugfix on 0.2.1.7-alpha.
18803 - Add a new --enable-local-appdata configuration switch to change
18804 the default location of the datadir on win32 from APPDATA to
18805 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
18806 entirely. Patch from coderman.
18809 - Make outbound DNS packets respect the OutboundBindAddress setting.
18810 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
18811 - When our circuit fails at the first hop (e.g. we get a destroy
18812 cell back), avoid using that OR connection anymore, and also
18813 tell all the one-hop directory requests waiting for it that they
18814 should fail. Bugfix on 0.2.1.3-alpha.
18815 - In the torify(1) manpage, mention that tsocks will leak your
18819 Changes in version 0.2.1.10-alpha - 2009-01-06
18820 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
18821 would make the bridge relay not so useful if it had DirPort set to 0,
18822 and one that could let an attacker learn a little bit of information
18823 about the bridge's users), and a bug that would cause your Tor relay
18824 to ignore a circuit create request it can't decrypt (rather than reply
18825 with an error). It also fixes a wide variety of other bugs.
18828 - If the cached networkstatus consensus is more than five days old,
18829 discard it rather than trying to use it. In theory it could
18830 be useful because it lists alternate directory mirrors, but in
18831 practice it just means we spend many minutes trying directory
18832 mirrors that are long gone from the network. Helps bug 887 a bit;
18834 - Bridge relays that had DirPort set to 0 would stop fetching
18835 descriptors shortly after startup, and then briefly resume
18836 after a new bandwidth test and/or after publishing a new bridge
18837 descriptor. Bridge users that try to bootstrap from them would
18838 get a recent networkstatus but would get descriptors from up to
18839 18 hours earlier, meaning most of the descriptors were obsolete
18840 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
18841 - Prevent bridge relays from serving their 'extrainfo' document
18842 to anybody who asks, now that extrainfo docs include potentially
18843 sensitive aggregated client geoip summaries. Bugfix on
18847 - New controller event "clients_seen" to report a geoip-based summary
18848 of which countries we've seen clients from recently. Now controllers
18849 like Vidalia can show bridge operators that they're actually making
18851 - Build correctly against versions of OpenSSL 0.9.8 or later built
18852 without support for deprecated functions.
18853 - Update to the "December 19 2008" ip-to-country file.
18855 o Minor bugfixes (on 0.2.0.x):
18856 - Authorities now vote for the Stable flag for any router whose
18857 weighted MTBF is at least 5 days, regardless of the mean MTBF.
18858 - Do not remove routers as too old if we do not have any consensus
18859 document. Bugfix on 0.2.0.7-alpha.
18860 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
18861 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
18862 - When an exit relay resolves a stream address to a local IP address,
18863 do not just keep retrying that same exit relay over and
18864 over. Instead, just close the stream. Addresses bug 872. Bugfix
18865 on 0.2.0.32. Patch from rovv.
18866 - If a hidden service sends us an END cell, do not consider
18867 retrying the connection; just close it. Patch from rovv.
18868 - When we made bridge authorities stop serving bridge descriptors over
18869 unencrypted links, we also broke DirPort reachability testing for
18870 bridges. So bridges with a non-zero DirPort were printing spurious
18871 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
18872 - When a relay gets a create cell it can't decrypt (e.g. because it's
18873 using the wrong onion key), we were dropping it and letting the
18874 client time out. Now actually answer with a destroy cell. Fixes
18875 bug 904. Bugfix on 0.0.2pre8.
18876 - Squeeze 2-5% out of client performance (according to oprofile) by
18877 improving the implementation of some policy-manipulation functions.
18879 o Minor bugfixes (on 0.2.1.x):
18880 - Make get_interface_address() function work properly again; stop
18881 guessing the wrong parts of our address as our address.
18882 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
18883 send on that circuit. Otherwise we might violate the proposal-110
18884 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
18886 - When we're sending non-EXTEND cells to the first hop in a circuit,
18887 for example to use an encrypted directory connection, we don't need
18888 to use RELAY_EARLY cells: the first hop knows what kind of cell
18889 it is, and nobody else can even see the cell type. Conserving
18890 RELAY_EARLY cells makes it easier to cannibalize circuits like
18892 - Stop logging nameserver addresses in reverse order.
18893 - If we are retrying a directory download slowly over and over, do
18894 not automatically give up after the 254th failure. Bugfix on
18896 - Resume reporting accurate "stream end" reasons to the local control
18897 port. They were lost in the changes for Proposal 148. Bugfix on
18900 o Deprecated and removed features:
18901 - The old "tor --version --version" command, which would print out
18902 the subversion "Id" of most of the source files, is now removed. It
18903 turned out to be less useful than we'd expected, and harder to
18906 o Code simplifications and refactoring:
18907 - Change our header file guard macros to be less likely to conflict
18908 with system headers. Adam Langley noticed that we were conflicting
18909 with log.h on Android.
18910 - Tool-assisted documentation cleanup. Nearly every function or
18911 static variable in Tor should have its own documentation now.
18914 Changes in version 0.2.1.9-alpha - 2008-12-25
18915 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
18917 o New directory authorities:
18918 - gabelmoo (the authority run by Karsten Loesing) now has a new
18922 - Never use a connection with a mismatched address to extend a
18923 circuit, unless that connection is canonical. A canonical
18924 connection is one whose address is authenticated by the router's
18925 identity key, either in a NETINFO cell or in a router descriptor.
18926 - Avoid a possible memory corruption bug when receiving hidden service
18927 descriptors. Bugfix on 0.2.1.6-alpha.
18930 - Fix a logic error that would automatically reject all but the first
18931 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
18932 part of bug 813/868. Bug spotted by coderman.
18933 - When a stream at an exit relay is in state "resolving" or
18934 "connecting" and it receives an "end" relay cell, the exit relay
18935 would silently ignore the end cell and not close the stream. If
18936 the client never closes the circuit, then the exit relay never
18937 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
18938 reported by "wood".
18939 - When we can't initialize DNS because the network is down, do not
18940 automatically stop Tor from starting. Instead, retry failed
18941 dns_init() every 10 minutes, and change the exit policy to reject
18942 *:* until one succeeds. Fixes bug 691.
18945 - Give a better error message when an overzealous init script says
18946 "sudo -u username tor --user username". Makes Bug 882 easier for
18948 - When a directory authority gives us a new guess for our IP address,
18949 log which authority we used. Hopefully this will help us debug
18950 the recent complaints about bad IP address guesses.
18951 - Detect svn revision properly when we're using git-svn.
18952 - Try not to open more than one descriptor-downloading connection
18953 to an authority at once. This should reduce load on directory
18954 authorities. Fixes bug 366.
18955 - Add cross-certification to newly generated certificates, so that
18956 a signing key is enough information to look up a certificate.
18957 Partial implementation of proposal 157.
18958 - Start serving certificates by <identity digest, signing key digest>
18959 pairs. Partial implementation of proposal 157.
18960 - Clients now never report any stream end reason except 'MISC'.
18961 Implements proposal 148.
18962 - On platforms with a maximum syslog string length, truncate syslog
18963 messages to that length ourselves, rather than relying on the
18964 system to do it for us.
18965 - Optimize out calls to time(NULL) that occur for every IO operation,
18966 or for every cell. On systems where time() is a slow syscall,
18967 this fix will be slightly helpful.
18968 - Exit servers can now answer resolve requests for ip6.arpa addresses.
18969 - When we download a descriptor that we then immediately (as
18970 a directory authority) reject, do not retry downloading it right
18971 away. Should save some bandwidth on authorities. Fix for bug
18972 888. Patch by Sebastian Hahn.
18973 - When a download gets us zero good descriptors, do not notify
18974 Tor that new directory information has arrived.
18975 - Avoid some nasty corner cases in the logic for marking connections
18976 as too old or obsolete or noncanonical for circuits. Partial
18979 o Minor features (controller):
18980 - New CONSENSUS_ARRIVED event to note when a new consensus has
18981 been fetched and validated.
18982 - When we realize that another process has modified our cached
18983 descriptors file, print out a more useful error message rather
18984 than triggering an assertion. Fixes bug 885. Patch from Karsten.
18985 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
18986 controllers to prevent SIGHUP from reloading the
18987 configuration. Fixes bug 856.
18990 - Resume using the correct "REASON=" stream when telling the
18991 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
18992 - When a canonical connection appears later in our internal list
18993 than a noncanonical one for a given OR ID, always use the
18994 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
18996 - Clip the MaxCircuitDirtiness config option to a minimum of 10
18997 seconds. Warn the user if lower values are given in the
18998 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
18999 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
19000 user if lower values are given in the configuration. Bugfix on
19001 0.1.1.17-rc. Patch by Sebastian.
19002 - Fix a race condition when freeing keys shared between main thread
19003 and CPU workers that could result in a memory leak. Bugfix on
19004 0.1.0.1-rc. Fixes bug 889.
19006 o Minor bugfixes (hidden services):
19007 - Do not throw away existing introduction points on SIGHUP (bugfix on
19008 0.0.6pre1); also, do not stall hidden services because we're
19009 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
19010 by John Brooks. Patch by Karsten. Fixes bug 874.
19011 - Fix a memory leak when we decline to add a v2 rendezvous
19012 descriptor to the cache because we already had a v0 descriptor
19013 with the same ID. Bugfix on 0.2.0.18-alpha.
19015 o Deprecated and removed features:
19016 - RedirectExits has been removed. It was deprecated since
19018 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
19019 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
19020 - Cell pools are now always enabled; --disable-cell-pools is ignored.
19022 o Code simplifications and refactoring:
19023 - Rename the confusing or_is_obsolete field to the more appropriate
19024 is_bad_for_new_circs, and move it to or_connection_t where it
19026 - Move edge-only flags from connection_t to edge_connection_t: not
19027 only is this better coding, but on machines of plausible alignment,
19028 it should save 4-8 bytes per connection_t. "Every little bit helps."
19029 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
19030 for consistency; keep old option working for backward compatibility.
19031 - Simplify the code for finding connections to use for a circuit.
19034 Changes in version 0.2.1.8-alpha - 2008-12-08
19035 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
19036 builds better on unusual platforms like Solaris and old OS X, and
19037 fixes a variety of other issues.
19040 - New DirPortFrontPage option that takes an html file and publishes
19041 it as "/" on the DirPort. Now relay operators can provide a
19042 disclaimer without needing to set up a separate webserver. There's
19043 a sample disclaimer in contrib/tor-exit-notice.html.
19046 - When the client is choosing entry guards, now it selects at most
19047 one guard from a given relay family. Otherwise we could end up with
19048 all of our entry points into the network run by the same operator.
19049 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
19052 - Fix a DOS opportunity during the voting signature collection process
19053 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
19054 - Fix a possible segfault when establishing an exit connection. Bugfix
19058 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
19060 - Made Tor a little less aggressive about deleting expired
19061 certificates. Partial fix for bug 854.
19062 - Stop doing unaligned memory access that generated bus errors on
19063 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
19064 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
19065 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
19066 - Make USR2 log-level switch take effect immediately. Bugfix on
19068 - If one win32 nameserver fails to get added, continue adding the
19069 rest, and don't automatically fail.
19070 - Use fcntl() for locking when flock() is not available. Should fix
19071 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
19072 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
19073 could make gcc generate non-functional binary search code. Bugfix
19075 - Build correctly on platforms without socklen_t.
19076 - Avoid potential crash on internal error during signature collection.
19077 Fixes bug 864. Patch from rovv.
19078 - Do not use C's stdio library for writing to log files. This will
19079 improve logging performance by a minute amount, and will stop
19080 leaking fds when our disk is full. Fixes bug 861.
19081 - Stop erroneous use of O_APPEND in cases where we did not in fact
19082 want to re-seek to the end of a file before every last write().
19083 - Correct handling of possible malformed authority signing key
19084 certificates with internal signature types. Fixes bug 880. Bugfix
19086 - Fix a hard-to-trigger resource leak when logging credential status.
19090 - Directory mirrors no longer fetch the v1 directory or
19091 running-routers files. They are obsolete, and nobody asks for them
19092 anymore. This is the first step to making v1 authorities obsolete.
19094 o Minor features (controller):
19095 - Return circuit purposes in response to GETINFO circuit-status. Fixes
19099 Changes in version 0.2.0.32 - 2008-11-20
19100 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
19101 packages (and maybe other packages) noticed by Theo de Raadt, fixes
19102 a smaller security flaw that might allow an attacker to access local
19103 services, further improves hidden service performance, and fixes a
19104 variety of other issues.
19107 - The "User" and "Group" config options did not clear the
19108 supplementary group entries for the Tor process. The "User" option
19109 is now more robust, and we now set the groups to the specified
19110 user's primary group. The "Group" option is now ignored. For more
19111 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
19112 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
19113 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
19114 - The "ClientDNSRejectInternalAddresses" config option wasn't being
19115 consistently obeyed: if an exit relay refuses a stream because its
19116 exit policy doesn't allow it, we would remember what IP address
19117 the relay said the destination address resolves to, even if it's
19118 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
19121 - Fix a DOS opportunity during the voting signature collection process
19122 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
19124 o Major bugfixes (hidden services):
19125 - When fetching v0 and v2 rendezvous service descriptors in parallel,
19126 we were failing the whole hidden service request when the v0
19127 descriptor fetch fails, even if the v2 fetch is still pending and
19128 might succeed. Similarly, if the last v2 fetch fails, we were
19129 failing the whole hidden service request even if a v0 fetch is
19130 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
19131 - When extending a circuit to a hidden service directory to upload a
19132 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
19133 requests failed, because the router descriptor has not been
19134 downloaded yet. In these cases, do not attempt to upload the
19135 rendezvous descriptor, but wait until the router descriptor is
19136 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
19137 descriptor from a hidden service directory for which the router
19138 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
19142 - Fix several infrequent memory leaks spotted by Coverity.
19143 - When testing for libevent functions, set the LDFLAGS variable
19144 correctly. Found by Riastradh.
19145 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
19146 bootstrapping with tunneled directory connections. Bugfix on
19147 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
19148 - When asked to connect to A.B.exit:80, if we don't know the IP for A
19149 and we know that server B rejects most-but-not all connections to
19150 port 80, we would previously reject the connection. Now, we assume
19151 the user knows what they were asking for. Fixes bug 752. Bugfix
19152 on 0.0.9rc5. Diagnosed by BarkerJr.
19153 - If we overrun our per-second write limits a little, count this as
19154 having used up our write allocation for the second, and choke
19155 outgoing directory writes. Previously, we had only counted this when
19156 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
19157 Bugfix on 0.2.0.x (??).
19158 - Remove the old v2 directory authority 'lefkada' from the default
19159 list. It has been gone for many months.
19160 - Stop doing unaligned memory access that generated bus errors on
19161 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
19162 - Make USR2 log-level switch take effect immediately. Bugfix on
19165 o Minor bugfixes (controller):
19166 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
19167 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
19170 Changes in version 0.2.1.7-alpha - 2008-11-08
19171 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
19172 packages (and maybe other packages) noticed by Theo de Raadt, fixes
19173 a smaller security flaw that might allow an attacker to access local
19174 services, adds better defense against DNS poisoning attacks on exit
19175 relays, further improves hidden service performance, and fixes a
19176 variety of other issues.
19179 - The "ClientDNSRejectInternalAddresses" config option wasn't being
19180 consistently obeyed: if an exit relay refuses a stream because its
19181 exit policy doesn't allow it, we would remember what IP address
19182 the relay said the destination address resolves to, even if it's
19183 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
19184 - The "User" and "Group" config options did not clear the
19185 supplementary group entries for the Tor process. The "User" option
19186 is now more robust, and we now set the groups to the specified
19187 user's primary group. The "Group" option is now ignored. For more
19188 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
19189 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
19190 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
19191 - Do not use or believe expired v3 authority certificates. Patch
19192 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
19195 - Now NodeFamily and MyFamily config options allow spaces in
19196 identity fingerprints, so it's easier to paste them in.
19197 Suggested by Lucky Green.
19198 - Implement the 0x20 hack to better resist DNS poisoning: set the
19199 case on outgoing DNS requests randomly, and reject responses that do
19200 not match the case correctly. This logic can be disabled with the
19201 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
19202 of servers that do not reliably preserve case in replies. See
19203 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
19205 - Preserve case in replies to DNSPort requests in order to support
19206 the 0x20 hack for resisting DNS poisoning attacks.
19208 o Hidden service performance improvements:
19209 - When the client launches an introduction circuit, retry with a
19210 new circuit after 30 seconds rather than 60 seconds.
19211 - Launch a second client-side introduction circuit in parallel
19212 after a delay of 15 seconds (based on work by Christian Wilms).
19213 - Hidden services start out building five intro circuits rather
19214 than three, and when the first three finish they publish a service
19215 descriptor using those. Now we publish our service descriptor much
19216 faster after restart.
19219 - Minor fix in the warning messages when you're having problems
19220 bootstrapping; also, be more forgiving of bootstrap problems when
19221 we're still making incremental progress on a given bootstrap phase.
19222 - When we're choosing an exit node for a circuit, and we have
19223 no pending streams, choose a good general exit rather than one that
19224 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
19225 - Send a valid END cell back when a client tries to connect to a
19226 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
19227 840. Patch from rovv.
19228 - If a broken client asks a non-exit router to connect somewhere,
19229 do not even do the DNS lookup before rejecting the connection.
19230 Fixes another case of bug 619. Patch from rovv.
19231 - Fix another case of assuming, when a specific exit is requested,
19232 that we know more than the user about what hosts it allows.
19233 Fixes another case of bug 752. Patch from rovv.
19234 - Check which hops rendezvous stream cells are associated with to
19235 prevent possible guess-the-streamid injection attacks from
19236 intermediate hops. Fixes another case of bug 446. Based on patch
19238 - Avoid using a negative right-shift when comparing 32-bit
19239 addresses. Possible fix for bug 845 and bug 811.
19240 - Make the assert_circuit_ok() function work correctly on circuits that
19241 have already been marked for close.
19242 - Fix read-off-the-end-of-string error in unit tests when decoding
19243 introduction points.
19244 - Fix uninitialized size field for memory area allocation: may improve
19245 memory performance during directory parsing.
19246 - Treat duplicate certificate fetches as failures, so that we do
19247 not try to re-fetch an expired certificate over and over and over.
19248 - Do not say we're fetching a certificate when we'll in fact skip it
19249 because of a pending download.
19252 Changes in version 0.2.1.6-alpha - 2008-09-30
19253 Tor 0.2.1.6-alpha further improves performance and robustness of
19254 hidden services, starts work on supporting per-country relay selection,
19255 and fixes a variety of smaller issues.
19258 - Implement proposal 121: make it possible to build hidden services
19259 that only certain clients are allowed to connect to. This is
19260 enforced at several points, so that unauthorized clients are unable
19261 to send INTRODUCE cells to the service, or even (depending on the
19262 type of authentication) to learn introduction points. This feature
19263 raises the bar for certain kinds of active attacks against hidden
19264 services. Code by Karsten Loesing.
19265 - Relays now store and serve v2 hidden service descriptors by default,
19266 i.e., the new default value for HidServDirectoryV2 is 1. This is
19267 the last step in proposal 114, which aims to make hidden service
19268 lookups more reliable.
19269 - Start work to allow node restrictions to include country codes. The
19270 syntax to exclude nodes in a country with country code XX is
19271 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
19272 refinement to decide what config options should take priority if
19273 you ask to both use a particular node and exclude it.
19274 - Allow ExitNodes list to include IP ranges and country codes, just
19275 like the Exclude*Nodes lists. Patch from Robert Hogan.
19278 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
19279 Tor to fail to start if you had it configured to use a bridge
19280 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
19281 - When extending a circuit to a hidden service directory to upload a
19282 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
19283 requests failed, because the router descriptor had not been
19284 downloaded yet. In these cases, we now wait until the router
19285 descriptor is downloaded, and then retry. Likewise, clients
19286 now skip over a hidden service directory if they don't yet have
19287 its router descriptor, rather than futilely requesting it and
19288 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
19290 - When fetching v0 and v2 rendezvous service descriptors in parallel,
19291 we were failing the whole hidden service request when the v0
19292 descriptor fetch fails, even if the v2 fetch is still pending and
19293 might succeed. Similarly, if the last v2 fetch fails, we were
19294 failing the whole hidden service request even if a v0 fetch is
19295 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
19296 - DNS replies need to have names matching their requests, but
19297 these names should be in the questions section, not necessarily
19298 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
19301 - Update to the "September 1 2008" ip-to-country file.
19302 - Allow ports 465 and 587 in the default exit policy again. We had
19303 rejected them in 0.1.0.15, because back in 2005 they were commonly
19304 misconfigured and ended up as spam targets. We hear they are better
19305 locked down these days.
19306 - Use a lockfile to make sure that two Tor processes are not
19307 simultaneously running with the same datadir.
19308 - Serve the latest v3 networkstatus consensus via the control
19309 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
19310 - Better logging about stability/reliability calculations on directory
19312 - Drop the requirement to have an open dir port for storing and
19313 serving v2 hidden service descriptors.
19314 - Directory authorities now serve a /tor/dbg-stability.txt URL to
19315 help debug WFU and MTBF calculations.
19316 - Implement most of Proposal 152: allow specialized servers to permit
19317 single-hop circuits, and clients to use those servers to build
19318 single-hop circuits when using a specialized controller. Patch
19319 from Josh Albrecht. Resolves feature request 768.
19320 - Add a -p option to tor-resolve for specifying the SOCKS port: some
19321 people find host:port too confusing.
19322 - Make TrackHostExit mappings expire a while after their last use, not
19323 after their creation. Patch from Robert Hogan.
19324 - Provide circuit purposes along with circuit events to the controller.
19327 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
19329 - Fixed some memory leaks -- some quite frequent, some almost
19330 impossible to trigger -- based on results from Coverity.
19331 - When testing for libevent functions, set the LDFLAGS variable
19332 correctly. Found by Riastradh.
19333 - Fix an assertion bug in parsing policy-related options; possible fix
19335 - Catch and report a few more bootstrapping failure cases when Tor
19336 fails to establish a TCP connection. Cleanup on 0.2.1.x.
19337 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
19338 bootstrapping with tunneled directory connections. Bugfix on
19339 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
19340 - When asked to connect to A.B.exit:80, if we don't know the IP for A
19341 and we know that server B rejects most-but-not all connections to
19342 port 80, we would previously reject the connection. Now, we assume
19343 the user knows what they were asking for. Fixes bug 752. Bugfix
19344 on 0.0.9rc5. Diagnosed by BarkerJr.
19345 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
19346 service directories if they have no advertised dir port. Bugfix
19348 - If we overrun our per-second write limits a little, count this as
19349 having used up our write allocation for the second, and choke
19350 outgoing directory writes. Previously, we had only counted this when
19351 we had met our limits precisely. Fixes bug 824. Patch by rovv.
19352 Bugfix on 0.2.0.x (??).
19353 - Avoid a "0 divided by 0" calculation when calculating router uptime
19354 at directory authorities. Bugfix on 0.2.0.8-alpha.
19355 - Make DNS resolved controller events into "CLOSED", not
19356 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
19358 - Fix a bug where an unreachable relay would establish enough
19359 reachability testing circuits to do a bandwidth test -- if
19360 we already have a connection to the middle hop of the testing
19361 circuit, then it could establish the last hop by using the existing
19362 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
19363 circuits no longer use entry guards in 0.2.1.3-alpha.
19364 - If we have correct permissions on $datadir, we complain to stdout
19365 and fail to start. But dangerous permissions on
19366 $datadir/cached-status/ would cause us to open a log and complain
19367 there. Now complain to stdout and fail to start in both cases. Fixes
19368 bug 820, reported by seeess.
19369 - Remove the old v2 directory authority 'lefkada' from the default
19370 list. It has been gone for many months.
19372 o Code simplifications and refactoring:
19373 - Revise the connection_new functions so that a more typesafe variant
19374 exists. This will work better with Coverity, and let us find any
19375 actual mistakes we're making here.
19376 - Refactor unit testing logic so that dmalloc can be used sensibly
19377 with unit tests to check for memory leaks.
19378 - Move all hidden-service related fields from connection and circuit
19379 structure to substructures: this way they won't eat so much memory.
19382 Changes in version 0.2.0.31 - 2008-09-03
19383 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
19384 a big bug we're seeing where in rare cases traffic from one Tor stream
19385 gets mixed into another stream, and fixes a variety of smaller issues.
19388 - Make sure that two circuits can never exist on the same connection
19389 with the same circuit ID, even if one is marked for close. This
19390 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
19391 - Relays now reject risky extend cells: if the extend cell includes
19392 a digest of all zeroes, or asks to extend back to the relay that
19393 sent the extend cell, tear down the circuit. Ideas suggested
19395 - If not enough of our entry guards are available so we add a new
19396 one, we might use the new one even if it overlapped with the
19397 current circuit's exit relay (or its family). Anonymity bugfix
19398 pointed out by rovv.
19401 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
19402 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
19403 - Correctly detect the presence of the linux/netfilter_ipv4.h header
19404 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
19405 - Pick size of default geoip filename string correctly on windows.
19406 Fixes bug 806. Bugfix on 0.2.0.30.
19407 - Make the autoconf script accept the obsolete --with-ssl-dir
19408 option as an alias for the actually-working --with-openssl-dir
19409 option. Fix the help documentation to recommend --with-openssl-dir.
19410 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
19411 - When using the TransPort option on OpenBSD, and using the User
19412 option to change UID and drop privileges, make sure to open
19413 /dev/pf before dropping privileges. Fixes bug 782. Patch from
19414 Christopher Davis. Bugfix on 0.1.2.1-alpha.
19415 - Try to attach connections immediately upon receiving a RENDEZVOUS2
19416 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
19417 on the client side when connecting to a hidden service. Bugfix
19418 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
19419 - When closing an application-side connection because its circuit is
19420 getting torn down, generate the stream event correctly. Bugfix on
19421 0.1.2.x. Anonymous patch.
19424 Changes in version 0.2.1.5-alpha - 2008-08-31
19425 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
19426 in a lot of the infrastructure for adding authorization to hidden
19427 services, lays the groundwork for having clients read their load
19428 balancing information out of the networkstatus consensus rather than
19429 the individual router descriptors, addresses two potential anonymity
19430 issues, and fixes a variety of smaller issues.
19433 - Convert many internal address representations to optionally hold
19435 - Generate and accept IPv6 addresses in many protocol elements.
19436 - Make resolver code handle nameservers located at ipv6 addresses.
19437 - Begin implementation of proposal 121 ("Client authorization for
19438 hidden services"): configure hidden services with client
19439 authorization, publish descriptors for them, and configure
19440 authorization data for hidden services at clients. The next
19441 step is to actually access hidden services that perform client
19443 - More progress toward proposal 141: Network status consensus
19444 documents and votes now contain bandwidth information for each
19445 router and a summary of that router's exit policy. Eventually this
19446 will be used by clients so that they do not have to download every
19447 known descriptor before building circuits.
19449 o Major bugfixes (on 0.2.0.x and before):
19450 - When sending CREATED cells back for a given circuit, use a 64-bit
19451 connection ID to find the right connection, rather than an addr:port
19452 combination. Now that we can have multiple OR connections between
19453 the same ORs, it is no longer possible to use addr:port to uniquely
19454 identify a connection.
19455 - Relays now reject risky extend cells: if the extend cell includes
19456 a digest of all zeroes, or asks to extend back to the relay that
19457 sent the extend cell, tear down the circuit. Ideas suggested
19459 - If not enough of our entry guards are available so we add a new
19460 one, we might use the new one even if it overlapped with the
19461 current circuit's exit relay (or its family). Anonymity bugfix
19462 pointed out by rovv.
19465 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
19466 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
19467 - When using the TransPort option on OpenBSD, and using the User
19468 option to change UID and drop privileges, make sure to open /dev/pf
19469 before dropping privileges. Fixes bug 782. Patch from Christopher
19470 Davis. Bugfix on 0.1.2.1-alpha.
19471 - Correctly detect the presence of the linux/netfilter_ipv4.h header
19472 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
19473 - Add a missing safe_str() call for a debug log message.
19474 - Use 64 bits instead of 32 bits for connection identifiers used with
19475 the controller protocol, to greatly reduce risk of identifier reuse.
19476 - Make the autoconf script accept the obsolete --with-ssl-dir
19477 option as an alias for the actually-working --with-openssl-dir
19478 option. Fix the help documentation to recommend --with-openssl-dir.
19479 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
19482 - Rate-limit too-many-sockets messages: when they happen, they happen
19483 a lot. Resolves bug 748.
19484 - Resist DNS poisoning a little better by making sure that names in
19485 answer sections match.
19486 - Print the SOCKS5 error message string as well as the error code
19487 when a tor-resolve request fails. Patch from Jacob.
19490 Changes in version 0.2.1.4-alpha - 2008-08-04
19491 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
19494 - The address part of exit policies was not correctly written
19495 to router descriptors. This generated router descriptors that failed
19496 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
19498 - Tor triggered a false assert when extending a circuit to a relay
19499 but we already have a connection open to that relay. Noticed by
19500 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
19503 - Fix a hidden service logging bug: in some edge cases, the router
19504 descriptor of a previously picked introduction point becomes
19505 obsolete and we need to give up on it rather than continually
19506 complaining that it has become obsolete. Observed by xiando. Bugfix
19509 o Removed features:
19510 - Take out the TestVia config option, since it was a workaround for
19511 a bug that was fixed in Tor 0.1.1.21.
19514 Changes in version 0.2.1.3-alpha - 2008-08-03
19515 Tor 0.2.1.3-alpha implements most of the pieces to prevent
19516 infinite-length circuit attacks (see proposal 110); fixes a bug that
19517 might cause exit relays to corrupt streams they send back; allows
19518 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
19519 ExcludeExitNodes config options; and fixes a big pile of bugs.
19521 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
19522 - Send a bootstrap problem "warn" event on the first problem if the
19523 reason is NO_ROUTE (that is, our network is down).
19526 - Implement most of proposal 110: The first K cells to be sent
19527 along a circuit are marked as special "early" cells; only K "early"
19528 cells will be allowed. Once this code is universal, we can block
19529 certain kinds of DOS attack by requiring that EXTEND commands must
19530 be sent using an "early" cell.
19533 - Try to attach connections immediately upon receiving a RENDEZVOUS2
19534 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
19535 on the client side when connecting to a hidden service. Bugfix
19536 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
19537 - Ensure that two circuits can never exist on the same connection
19538 with the same circuit ID, even if one is marked for close. This
19539 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
19542 - When relays do their initial bandwidth measurement, don't limit
19543 to just our entry guards for the test circuits. Otherwise we tend
19544 to have multiple test circuits going through a single entry guard,
19545 which makes our bandwidth test less accurate. Fixes part of bug 654;
19546 patch contributed by Josh Albrecht.
19547 - Add an ExcludeExitNodes option so users can list a set of nodes
19548 that should be be excluded from the exit node position, but
19549 allowed elsewhere. Implements proposal 151.
19550 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
19551 ExcludeNodes and ExcludeExitNodes lists.
19552 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
19553 be more efficient. Formerly it was quadratic in the number of
19554 servers; now it should be linear. Fixes bug 509.
19555 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
19556 and n_conn_id_digest fields into a separate structure that's
19557 only needed when the circuit has not yet attached to an n_conn.
19560 - Change the contrib/tor.logrotate script so it makes the new
19561 logs as "_tor:_tor" rather than the default, which is generally
19562 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
19563 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
19564 warnings (occasionally), but it can also cause the compiler to
19565 eliminate error-checking code. Suggested by Peter Gutmann.
19566 - When a hidden service is giving up on an introduction point candidate
19567 that was not included in the last published rendezvous descriptor,
19568 don't reschedule publication of the next descriptor. Fixes bug 763.
19570 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
19571 HiddenServiceExcludeNodes as obsolete: they never worked properly,
19572 and nobody claims to be using them. Fixes bug 754. Bugfix on
19573 0.1.0.1-rc. Patch from Christian Wilms.
19574 - Fix a small alignment and memory-wasting bug on buffer chunks.
19577 o Minor bugfixes (controller):
19578 - When closing an application-side connection because its circuit
19579 is getting torn down, generate the stream event correctly.
19580 Bugfix on 0.1.2.x. Anonymous patch.
19582 o Removed features:
19583 - Remove all backward-compatibility code to support relays running
19584 versions of Tor so old that they no longer work at all on the
19588 Changes in version 0.2.0.30 - 2008-07-15
19590 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
19591 warnings (occasionally), but it can also cause the compiler to
19592 eliminate error-checking code. Suggested by Peter Gutmann.
19595 Changes in version 0.2.0.29-rc - 2008-07-08
19596 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
19597 hidden-service performance bugs, and fixes a bunch of smaller bugs.
19600 - If you have more than one bridge but don't know their keys,
19601 you would only launch a request for the descriptor of the first one
19602 on your list. (Tor considered launching requests for the others, but
19603 found that it already had a connection on the way for $0000...0000
19604 so it didn't open another.) Bugfix on 0.2.0.x.
19605 - If you have more than one bridge but don't know their keys, and the
19606 connection to one of the bridges failed, you would cancel all
19607 pending bridge connections. (After all, they all have the same
19608 digest.) Bugfix on 0.2.0.x.
19609 - When a hidden service was trying to establish an introduction point,
19610 and Tor had built circuits preemptively for such purposes, we
19611 were ignoring all the preemptive circuits and launching a new one
19612 instead. Bugfix on 0.2.0.14-alpha.
19613 - When a hidden service was trying to establish an introduction point,
19614 and Tor *did* manage to reuse one of the preemptively built
19615 circuits, it didn't correctly remember which one it used,
19616 so it asked for another one soon after, until there were no
19617 more preemptive circuits, at which point it launched one from
19618 scratch. Bugfix on 0.0.9.x.
19619 - Make directory servers include the X-Your-Address-Is: http header in
19620 their responses even for begin_dir conns. Now clients who only
19621 ever use begin_dir connections still have a way to learn their IP
19622 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
19625 - Fix a macro/CPP interaction that was confusing some compilers:
19626 some GCCs don't like #if/#endif pairs inside macro arguments.
19628 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
19629 Fixes bug 704; fix from Steven Murdoch.
19630 - When opening /dev/null in finish_daemonize(), do not pass the
19631 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
19632 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
19633 - Correctly detect transparent proxy support on Linux hosts that
19634 require in.h to be included before netfilter_ipv4.h. Patch
19636 - Disallow session resumption attempts during the renegotiation
19637 stage of the v2 handshake protocol. Clients should never be trying
19638 session resumption at this point, but apparently some did, in
19639 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
19640 found by Geoff Goodell.
19643 Changes in version 0.2.1.2-alpha - 2008-06-20
19644 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
19645 make it easier to set up your own private Tor network; fixes several
19646 big bugs with using more than one bridge relay; fixes a big bug with
19647 offering hidden services quickly after Tor starts; and uses a better
19648 API for reporting potential bootstrapping problems to the controller.
19651 - New TestingTorNetwork config option to allow adjustment of
19652 previously constant values that, while reasonable, could slow
19653 bootstrapping. Implements proposal 135. Patch from Karsten.
19656 - If you have more than one bridge but don't know their digests,
19657 you would only learn a request for the descriptor of the first one
19658 on your list. (Tor considered launching requests for the others, but
19659 found that it already had a connection on the way for $0000...0000
19660 so it didn't open another.) Bugfix on 0.2.0.x.
19661 - If you have more than one bridge but don't know their digests,
19662 and the connection to one of the bridges failed, you would cancel
19663 all pending bridge connections. (After all, they all have the
19664 same digest.) Bugfix on 0.2.0.x.
19665 - When establishing a hidden service, introduction points that
19666 originate from cannibalized circuits are completely ignored and not
19667 included in rendezvous service descriptors. This might be another
19668 reason for delay in making a hidden service available. Bugfix
19669 from long ago (0.0.9.x?)
19672 - Allow OpenSSL to use dynamic locks if it wants.
19673 - When building a consensus, do not include routers that are down.
19674 This will cut down 30% to 40% on consensus size. Implements
19676 - In directory authorities' approved-routers files, allow
19677 fingerprints with or without space.
19678 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
19679 controller can query our current bootstrap state in case it attaches
19680 partway through and wants to catch up.
19681 - Send an initial "Starting" bootstrap status event, so we have a
19682 state to start out in.
19685 - Asking for a conditional consensus at .../consensus/<fingerprints>
19686 would crash a dirserver if it did not already have a
19687 consensus. Bugfix on 0.2.1.1-alpha.
19688 - Clean up some macro/CPP interactions: some GCC versions don't like
19689 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
19692 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
19693 - Directory authorities shouldn't complain about bootstrapping
19694 problems just because they do a lot of reachability testing and
19695 some of the connection attempts fail.
19696 - Start sending "count" and "recommendation" key/value pairs in
19697 bootstrap problem status events, so the controller can hear about
19698 problems even before Tor decides they're worth reporting for sure.
19699 - If you're using bridges, generate "bootstrap problem" warnings
19700 as soon as you run out of working bridges, rather than waiting
19701 for ten failures -- which will never happen if you have less than
19703 - If we close our OR connection because there's been a circuit
19704 pending on it for too long, we were telling our bootstrap status
19705 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
19708 Changes in version 0.2.1.1-alpha - 2008-06-13
19709 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
19710 were making the Tor process bloat especially on Linux; makes our TLS
19711 handshake blend in better; sends "bootstrap phase" status events to
19712 the controller, so it can keep the user informed of progress (and
19713 problems) fetching directory information and establishing circuits;
19714 and adds a variety of smaller features.
19717 - More work on making our TLS handshake blend in: modify the list
19718 of ciphers advertised by OpenSSL in client mode to even more
19719 closely resemble a common web browser. We cheat a little so that
19720 we can advertise ciphers that the locally installed OpenSSL doesn't
19722 - Start sending "bootstrap phase" status events to the controller,
19723 so it can keep the user informed of progress fetching directory
19724 information and establishing circuits. Also inform the controller
19725 if we think we're stuck at a particular bootstrap phase. Implements
19727 - Resume using OpenSSL's RAND_poll() for better (and more portable)
19728 cross-platform entropy collection again. We used to use it, then
19729 stopped using it because of a bug that could crash systems that
19730 called RAND_poll when they had a lot of fds open. It looks like the
19731 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
19732 at startup, and to call RAND_poll() when we reseed later only if
19733 we have a non-buggy OpenSSL version.
19736 - When we choose to abandon a new entry guard because we think our
19737 older ones might be better, close any circuits pending on that
19738 new entry guard connection. This fix should make us recover much
19739 faster when our network is down and then comes back. Bugfix on
19740 0.1.2.8-beta; found by lodger.
19742 o Memory fixes and improvements:
19743 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
19744 to avoid unused RAM in buffer chunks and memory pools.
19745 - Speed up parsing and cut down on memory fragmentation by using
19746 stack-style allocations for parsing directory objects. Previously,
19747 this accounted for over 40% of allocations from within Tor's code
19748 on a typical directory cache.
19749 - Use a Bloom filter rather than a digest-based set to track which
19750 descriptors we need to keep around when we're cleaning out old
19751 router descriptors. This speeds up the computation significantly,
19752 and may reduce fragmentation.
19753 - Reduce the default smartlist size from 32 to 16; it turns out that
19754 most smartlists hold around 8-12 elements tops.
19755 - Make dumpstats() log the fullness and size of openssl-internal
19757 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
19758 patch to their OpenSSL, turn it on to save memory on servers. This
19759 patch will (with any luck) get included in a mainline distribution
19761 - Never use OpenSSL compression: it wastes RAM and CPU trying to
19762 compress cells, which are basically all encrypted, compressed,
19766 - Stop reloading the router list from disk for no reason when we
19767 run out of reachable directory mirrors. Once upon a time reloading
19768 it would set the 'is_running' flag back to 1 for them. It hasn't
19769 done that for a long time.
19770 - In very rare situations new hidden service descriptors were
19771 published earlier than 30 seconds after the last change to the
19772 service. (We currently think that a hidden service descriptor
19773 that's been stable for 30 seconds is worth publishing.)
19776 - Allow separate log levels to be configured for different logging
19777 domains. For example, this allows one to log all notices, warnings,
19778 or errors, plus all memory management messages of level debug or
19779 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
19780 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
19781 and stop using a warning that had become unfixably verbose under
19783 - New --hush command-line option similar to --quiet. While --quiet
19784 disables all logging to the console on startup, --hush limits the
19785 output to messages of warning and error severity.
19786 - Servers support a new URL scheme for consensus downloads that
19787 allows the client to specify which authorities are trusted.
19788 The server then only sends the consensus if the client will trust
19789 it. Otherwise a 404 error is sent back. Clients use this
19790 new scheme when the server supports it (meaning it's running
19791 0.2.1.1-alpha or later). Implements proposal 134.
19792 - New configure/torrc options (--enable-geoip-stats,
19793 DirRecordUsageByCountry) to record how many IPs we've served
19794 directory info to in each country code, how many status documents
19795 total we've sent to each country code, and what share of the total
19796 directory requests we should expect to see.
19797 - Use the TLS1 hostname extension to more closely resemble browser
19799 - Lots of new unit tests.
19800 - Add a macro to implement the common pattern of iterating through
19801 two parallel lists in lockstep.
19804 Changes in version 0.2.0.28-rc - 2008-06-13
19805 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
19806 performance bug, and fixes a bunch of smaller bugs.
19809 - Fix a bug where, when we were choosing the 'end stream reason' to
19810 put in our relay end cell that we send to the exit relay, Tor
19811 clients on Windows were sometimes sending the wrong 'reason'. The
19812 anonymity problem is that exit relays may be able to guess whether
19813 the client is running Windows, thus helping partition the anonymity
19814 set. Down the road we should stop sending reasons to exit relays,
19815 or otherwise prevent future versions of this bug.
19818 - While setting up a hidden service, some valid introduction circuits
19819 were overlooked and abandoned. This might be the reason for
19820 the long delay in making a hidden service available. Bugfix on
19824 - Update to the "June 9 2008" ip-to-country file.
19825 - Run 'make test' as part of 'make dist', so we stop releasing so
19826 many development snapshots that fail their unit tests.
19829 - When we're checking if we have enough dir info for each relay
19830 to begin establishing circuits, make sure that we actually have
19831 the descriptor listed in the consensus, not just any descriptor.
19833 - Bridge relays no longer print "xx=0" in their extrainfo document
19834 for every single country code in the geoip db. Bugfix on
19836 - Only warn when we fail to load the geoip file if we were planning to
19837 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
19838 - If we change our MaxAdvertisedBandwidth and then reload torrc,
19839 Tor won't realize it should publish a new relay descriptor. Fixes
19840 bug 688, reported by mfr. Bugfix on 0.1.2.x.
19841 - When we haven't had any application requests lately, don't bother
19842 logging that we have expired a bunch of descriptors. Bugfix
19844 - Make relay cells written on a connection count as non-padding when
19845 tracking how long a connection has been in use. Bugfix on
19846 0.2.0.1-alpha. Spotted by lodger.
19847 - Fix unit tests in 0.2.0.27-rc.
19848 - Fix compile on Windows.
19851 Changes in version 0.2.0.27-rc - 2008-06-03
19852 Tor 0.2.0.27-rc adds a few features we left out of the earlier
19853 release candidates. In particular, we now include an IP-to-country
19854 GeoIP database, so controllers can easily look up what country a
19855 given relay is in, and so bridge relays can give us some sanitized
19856 summaries about which countries are making use of bridges. (See proposal
19857 126-geoip-fetching.txt for details.)
19860 - Include an IP-to-country GeoIP file in the tarball, so bridge
19861 relays can report sanitized summaries of the usage they're seeing.
19864 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
19865 Robert Hogan. Fixes the first part of bug 681.
19866 - Make bridge authorities never serve extrainfo docs.
19867 - Add support to detect Libevent versions in the 1.4.x series
19869 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
19870 - Include a new contrib/tor-exit-notice.html file that exit relay
19871 operators can put on their website to help reduce abuse queries.
19874 - When tunneling an encrypted directory connection, and its first
19875 circuit fails, do not leave it unattached and ask the controller
19876 to deal. Fixes the second part of bug 681.
19877 - Make bridge authorities correctly expire old extrainfo documents
19881 Changes in version 0.2.0.26-rc - 2008-05-13
19882 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
19883 in Debian's OpenSSL packages. All users running any 0.2.0.x version
19884 should upgrade, whether they're running Debian or not.
19886 o Major security fixes:
19887 - Use new V3 directory authority keys on the tor26, gabelmoo, and
19888 moria1 V3 directory authorities. The old keys were generated with
19889 a vulnerable version of Debian's OpenSSL package, and must be
19890 considered compromised. Other authorities' keys were not generated
19891 with an affected version of OpenSSL.
19894 - List authority signatures as "unrecognized" based on DirServer
19895 lines, not on cert cache. Bugfix on 0.2.0.x.
19898 - Add a new V3AuthUseLegacyKey option to make it easier for
19899 authorities to change their identity keys if they have to.
19902 Changes in version 0.2.0.25-rc - 2008-04-23
19903 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
19906 - Remember to initialize threading before initializing logging.
19907 Otherwise, many BSD-family implementations will crash hard on
19908 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
19911 - Authorities correctly free policies on bad servers on
19912 exit. Fixes bug 672. Bugfix on 0.2.0.x.
19915 Changes in version 0.2.0.24-rc - 2008-04-22
19916 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
19917 v3 directory authority, makes relays with dynamic IP addresses and no
19918 DirPort notice more quickly when their IP address changes, fixes a few
19919 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
19921 o New directory authorities:
19922 - Take lefkada out of the list of v3 directory authorities, since
19923 it has been down for months.
19924 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
19928 - Detect address changes more quickly on non-directory mirror
19929 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
19931 o Minor features (security):
19932 - Reject requests for reverse-dns lookup of names that are in
19933 a private address space. Patch from lodger.
19934 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
19937 o Minor bugfixes (crashes):
19938 - Avoid a rare assert that can trigger when Tor doesn't have much
19939 directory information yet and it tries to fetch a v2 hidden
19940 service descriptor. Fixes bug 651, reported by nwf.
19941 - Initialize log mutex before initializing dmalloc. Otherwise,
19942 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
19943 - Use recursive pthread mutexes in order to avoid deadlock when
19944 logging debug-level messages to a controller. Bug spotted by nwf,
19945 bugfix on 0.2.0.16-alpha.
19947 o Minor bugfixes (resource management):
19948 - Keep address policies from leaking memory: start their refcount
19949 at 1, not 2. Bugfix on 0.2.0.16-alpha.
19950 - Free authority certificates on exit, so they don't look like memory
19951 leaks. Bugfix on 0.2.0.19-alpha.
19952 - Free static hashtables for policy maps and for TLS connections on
19953 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
19954 - Avoid allocating extra space when computing consensuses on 64-bit
19955 platforms. Bug spotted by aakova.
19957 o Minor bugfixes (misc):
19958 - Do not read the configuration file when we've only been told to
19959 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
19960 based on patch from Sebastian Hahn.
19961 - Exit relays that are used as a client can now reach themselves
19962 using the .exit notation, rather than just launching an infinite
19963 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
19964 - When attempting to open a logfile fails, tell us why.
19965 - Fix a dumb bug that was preventing us from knowing that we should
19966 preemptively build circuits to handle expected directory requests.
19967 Fixes bug 660. Bugfix on 0.1.2.x.
19968 - Warn less verbosely about clock skew from netinfo cells from
19969 untrusted sources. Fixes bug 663.
19970 - Make controller stream events for DNS requests more consistent,
19971 by adding "new stream" events for DNS requests, and removing
19972 spurious "stream closed" events" for cached reverse resolves.
19973 Patch from mwenge. Fixes bug 646.
19974 - Correctly notify one-hop connections when a circuit build has
19975 failed. Possible fix for bug 669. Found by lodger.
19978 Changes in version 0.2.0.23-rc - 2008-03-24
19979 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
19980 makes bootstrapping faster if the first directory mirror you contact
19981 is down. The bundles also include the new Vidalia 0.1.2 release.
19984 - When a tunneled directory request is made to a directory server
19985 that's down, notice after 30 seconds rather than 120 seconds. Also,
19986 fail any begindir streams that are pending on it, so they can
19987 retry elsewhere. This was causing multi-minute delays on bootstrap.
19990 Changes in version 0.2.0.22-rc - 2008-03-18
19991 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
19992 enables encrypted directory connections by default for non-relays, fixes
19993 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
19994 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
19997 - Enable encrypted directory connections by default for non-relays,
19998 so censor tools that block Tor directory connections based on their
19999 plaintext patterns will no longer work. This means Tor works in
20000 certain censored countries by default again.
20003 - Make sure servers always request certificates from clients during
20004 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
20005 - Do not enter a CPU-eating loop when a connection is closed in
20006 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
20007 diagnosed by lodger; bugfix on 0.2.0.20-rc.
20008 - Fix assertion failure that could occur when a blocked circuit
20009 became unblocked, and it had pending client DNS requests. Bugfix
20010 on 0.2.0.1-alpha. Fixes bug 632.
20012 o Minor bugfixes (on 0.1.2.x):
20013 - Generate "STATUS_SERVER" events rather than misspelled
20014 "STATUS_SEVER" events. Caught by mwenge.
20015 - When counting the number of bytes written on a TLS connection,
20016 look at the BIO actually used for writing to the network, not
20017 at the BIO used (sometimes) to buffer data for the network.
20018 Looking at different BIOs could result in write counts on the
20019 order of ULONG_MAX. Fixes bug 614.
20020 - On Windows, correctly detect errors when listing the contents of
20021 a directory. Fix from lodger.
20023 o Minor bugfixes (on 0.2.0.x):
20024 - Downgrade "sslv3 alert handshake failure" message to INFO.
20025 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
20026 left BandwidthRate and BandwidthBurst at the default, we would be
20027 silently limited by those defaults. Now raise them to match the
20028 RelayBandwidth* values.
20029 - Fix the SVK version detection logic to work correctly on a branch.
20030 - Make --enable-openbsd-malloc work correctly on Linux with alpha
20031 CPUs. Fixes bug 625.
20032 - Logging functions now check that the passed severity is sane.
20033 - Use proper log levels in the testsuite call of
20034 get_interface_address6().
20035 - When using a nonstandard malloc, do not use the platform values for
20036 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
20037 - Make the openbsd malloc code use 8k pages on alpha CPUs and
20039 - Detect mismatched page sizes when using --enable-openbsd-malloc.
20040 - Avoid double-marked-for-close warning when certain kinds of invalid
20041 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
20042 for bug 617. Bugfix on 0.2.0.1-alpha.
20043 - Make sure that the "NULL-means-reject *:*" convention is followed by
20044 all the policy manipulation functions, avoiding some possible crash
20045 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
20046 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
20047 actually works, and doesn't warn about every single reverse lookup.
20048 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
20051 - Only log guard node status when guard node status has changed.
20052 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
20053 make "INFO" 75% less verbose.
20056 Changes in version 0.2.0.21-rc - 2008-03-02
20057 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
20058 makes Tor work well with Vidalia again, fixes a rare assert bug,
20059 and fixes a pair of more minor bugs. The bundles also include Vidalia
20060 0.1.0 and Torbutton 1.1.16.
20063 - The control port should declare that it requires password auth
20064 when HashedControlSessionPassword is set too. Patch from Matt Edman;
20065 bugfix on 0.2.0.20-rc. Fixes bug 615.
20066 - Downgrade assert in connection_buckets_decrement() to a log message.
20067 This may help us solve bug 614, and in any case will make its
20068 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
20069 - We were sometimes miscounting the number of bytes read from the
20070 network, causing our rate limiting to not be followed exactly.
20071 Bugfix on 0.2.0.16-alpha. Reported by lodger.
20074 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
20075 OpenSSL versions should have been working fine. Diagnosis and patch
20076 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
20077 Bugfix on 0.2.0.20-rc.
20080 Changes in version 0.2.0.20-rc - 2008-02-24
20081 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
20082 makes more progress towards normalizing Tor's TLS handshake, makes
20083 hidden services work better again, helps relays bootstrap if they don't
20084 know their IP address, adds optional support for linking in openbsd's
20085 allocator or tcmalloc, allows really fast relays to scale past 15000
20086 sockets, and fixes a bunch of minor bugs reported by Veracode.
20089 - Enable the revised TLS handshake based on the one designed by
20090 Steven Murdoch in proposal 124, as revised in proposal 130. It
20091 includes version negotiation for OR connections as described in
20092 proposal 105. The new handshake is meant to be harder for censors
20093 to fingerprint, and it adds the ability to detect certain kinds of
20094 man-in-the-middle traffic analysis attacks. The version negotiation
20095 feature will allow us to improve Tor's link protocol more safely
20097 - Choose which bridge to use proportional to its advertised bandwidth,
20098 rather than uniformly at random. This should speed up Tor for
20099 bridge users. Also do this for people who set StrictEntryNodes.
20100 - When a TrackHostExits-chosen exit fails too many times in a row,
20101 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
20104 - Resolved problems with (re-)fetching hidden service descriptors.
20105 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
20106 and 0.2.0.19-alpha.
20107 - If we only ever used Tor for hidden service lookups or posts, we
20108 would stop building circuits and start refusing connections after
20109 24 hours, since we falsely believed that Tor was dormant. Reported
20110 by nwf; bugfix on 0.1.2.x.
20111 - Servers that don't know their own IP address should go to the
20112 authorities for their first directory fetch, even if their DirPort
20113 is off or if they don't know they're reachable yet. This will help
20114 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
20115 - When counting the number of open sockets, count not only the number
20116 of sockets we have received from the socket() call, but also
20117 the number we've gotten from accept() and socketpair(). This bug
20118 made us fail to count all sockets that we were using for incoming
20119 connections. Bugfix on 0.2.0.x.
20120 - Fix code used to find strings within buffers, when those strings
20121 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
20122 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
20123 - Add a new __HashedControlSessionPassword option for controllers
20124 to use for one-off session password hashes that shouldn't get
20125 saved to disk by SAVECONF --- Vidalia users were accumulating a
20126 pile of HashedControlPassword lines in their torrc files, one for
20127 each time they had restarted Tor and then clicked Save. Make Tor
20128 automatically convert "HashedControlPassword" to this new option but
20129 only when it's given on the command line. Partial fix for bug 586.
20131 o Minor features (performance):
20132 - Tune parameters for cell pool allocation to minimize amount of
20134 - Add OpenBSD malloc code from phk as an optional malloc
20135 replacement on Linux: some glibc libraries do very poorly
20136 with Tor's memory allocation patterns. Pass
20137 --enable-openbsd-malloc to get the replacement malloc code.
20138 - Add a --with-tcmalloc option to the configure script to link
20139 against tcmalloc (if present). Does not yet search for
20140 non-system include paths.
20141 - Stop imposing an arbitrary maximum on the number of file descriptors
20142 used for busy servers. Bug reported by Olaf Selke; patch from
20145 o Minor features (other):
20146 - When SafeLogging is disabled, log addresses along with all TLS
20148 - When building with --enable-gcc-warnings, check for whether Apple's
20149 warning "-Wshorten-64-to-32" is available.
20150 - Add a --passphrase-fd argument to the tor-gencert command for
20153 o Minor bugfixes (memory leaks and code problems):
20154 - We were leaking a file descriptor if Tor started with a zero-length
20155 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
20156 - Detect size overflow in zlib code. Reported by Justin Ferguson and
20158 - We were comparing the raw BridgePassword entry with a base64'ed
20159 version of it, when handling a "/tor/networkstatus-bridges"
20160 directory request. Now compare correctly. Noticed by Veracode.
20161 - Recover from bad tracked-since value in MTBF-history file.
20162 Should fix bug 537.
20163 - Alter the code that tries to recover from unhandled write
20164 errors, to not try to flush onto a socket that's given us
20165 unhandled errors. Bugfix on 0.1.2.x.
20166 - Make Unix controlsockets work correctly on OpenBSD. Patch from
20167 tup. Bugfix on 0.2.0.3-alpha.
20169 o Minor bugfixes (other):
20170 - If we have an extra-info document for our server, always make
20171 it available on the control port, even if we haven't gotten
20172 a copy of it from an authority yet. Patch from mwenge.
20173 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
20174 - Directory mirrors no longer include a guess at the client's IP
20175 address if the connection appears to be coming from the same /24
20176 network; it was producing too many wrong guesses.
20177 - Make the new hidden service code respect the SafeLogging setting.
20178 Bugfix on 0.2.0.x. Patch from Karsten.
20179 - When starting as an authority, do not overwrite all certificates
20180 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
20181 - If we're trying to flush the last bytes on a connection (for
20182 example, when answering a directory request), reset the
20183 time-to-give-up timeout every time we manage to write something
20184 on the socket. Bugfix on 0.1.2.x.
20185 - Change the behavior of "getinfo status/good-server-descriptor"
20186 so it doesn't return failure when any authority disappears.
20187 - Even though the man page said that "TrackHostExits ." should
20188 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
20189 - Report TLS "zero return" case as a "clean close" and "IO error"
20190 as a "close". Stop calling closes "unexpected closes": existing
20191 Tors don't use SSL_close(), so having a connection close without
20192 the TLS shutdown handshake is hardly unexpected.
20193 - Send NAMESERVER_STATUS messages for a single failed nameserver
20196 o Code simplifications and refactoring:
20197 - Remove the tor_strpartition function: its logic was confused,
20198 and it was only used for one thing that could be implemented far
20202 Changes in version 0.2.0.19-alpha - 2008-02-09
20203 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
20204 handshake, makes path selection for relays more secure and IP address
20205 guessing more robust, and generally fixes a lot of bugs in preparation
20206 for calling the 0.2.0 branch stable.
20209 - Do not include recognizeable strings in the commonname part of
20210 Tor's x509 certificates.
20213 - If we're a relay, avoid picking ourselves as an introduction point,
20214 a rendezvous point, or as the final hop for internal circuits. Bug
20215 reported by taranis and lodger. Bugfix on 0.1.2.x.
20216 - Patch from "Andrew S. Lists" to catch when we contact a directory
20217 mirror at IP address X and he says we look like we're coming from
20218 IP address X. Bugfix on 0.1.2.x.
20220 o Minor features (security):
20221 - Be more paranoid about overwriting sensitive memory on free(),
20222 as a defensive programming tactic to ensure forward secrecy.
20224 o Minor features (directory authority):
20225 - Actually validate the options passed to AuthDirReject,
20226 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
20227 - Reject router descriptors with out-of-range bandwidthcapacity or
20228 bandwidthburst values.
20230 o Minor features (controller):
20231 - Reject controller commands over 1MB in length. This keeps rogue
20232 processes from running us out of memory.
20234 o Minor features (misc):
20235 - Give more descriptive well-formedness errors for out-of-range
20236 hidden service descriptor/protocol versions.
20237 - Make memory debugging information describe more about history
20238 of cell allocation, so we can help reduce our memory use.
20240 o Deprecated features (controller):
20241 - The status/version/num-versioning and status/version/num-concurring
20242 GETINFO options are no longer useful in the v3 directory protocol:
20243 treat them as deprecated, and warn when they're used.
20246 - When our consensus networkstatus has been expired for a while, stop
20247 being willing to build circuits using it. Fixes bug 401. Bugfix
20249 - Directory caches now fetch certificates from all authorities
20250 listed in a networkstatus consensus, even when they do not
20251 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
20252 - When connecting to a bridge without specifying its key, insert
20253 the connection into the identity-to-connection map as soon as
20254 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
20255 - Detect versions of OS X where malloc_good_size() is present in the
20256 library but never actually declared. Resolves bug 587. Bugfix
20258 - Stop incorrectly truncating zlib responses to directory authority
20259 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
20260 - Stop recommending that every server operator send mail to tor-ops.
20261 Resolves bug 597. Bugfix on 0.1.2.x.
20262 - Don't trigger an assert if we start a directory authority with a
20263 private IP address (like 127.0.0.1).
20264 - Avoid possible failures when generating a directory with routers
20265 with over-long versions strings, or too many flags set. Bugfix
20267 - If an attempt to launch a DNS resolve request over the control
20268 port fails because we have overrun the limit on the number of
20269 connections, tell the controller that the request has failed.
20270 - Avoid using too little bandwidth when our clock skips a few
20271 seconds. Bugfix on 0.1.2.x.
20272 - Fix shell error when warning about missing packages in configure
20273 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
20274 - Do not become confused when receiving a spurious VERSIONS-like
20275 cell from a confused v1 client. Bugfix on 0.2.0.x.
20276 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
20277 introduction points for a hidden service have failed. Patch from
20278 Karsten Loesing. Bugfix on 0.2.0.x.
20280 o Code simplifications and refactoring:
20281 - Remove some needless generality from cpuworker code, for improved
20283 - Stop overloading the circuit_t.onionskin field for both "onionskin
20284 from a CREATE cell that we are waiting for a cpuworker to be
20285 assigned" and "onionskin from an EXTEND cell that we are going to
20286 send to an OR as soon as we are connected". Might help with bug 600.
20287 - Add an in-place version of aes_crypt() so that we can avoid doing a
20288 needless memcpy() call on each cell payload.
20291 Changes in version 0.2.0.18-alpha - 2008-01-25
20292 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
20293 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
20294 that can warn or reject connections to ports generally associated with
20295 vulnerable-plaintext protocols.
20297 o New directory authorities:
20298 - Set up dannenberg (run by CCC) as the sixth v3 directory
20302 - Fix a major memory leak when attempting to use the v2 TLS
20303 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
20304 - We accidentally enabled the under-development v2 TLS handshake
20305 code, which was causing log entries like "TLS error while
20306 renegotiating handshake". Disable it again. Resolves bug 590.
20307 - We were computing the wrong Content-Length: header for directory
20308 responses that need to be compressed on the fly, causing clients
20309 asking for those items to always fail. Bugfix on 0.2.0.x; partially
20313 - Avoid going directly to the directory authorities even if you're a
20314 relay, if you haven't found yourself reachable yet or if you've
20315 decided not to advertise your dirport yet. Addresses bug 556.
20316 - If we've gone 12 hours since our last bandwidth check, and we
20317 estimate we have less than 50KB bandwidth capacity but we could
20318 handle more, do another bandwidth test.
20319 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
20320 Tor can warn and/or refuse connections to ports commonly used with
20321 vulnerable-plaintext protocols. Currently we warn on ports 23,
20322 109, 110, and 143, but we don't reject any.
20325 - When we setconf ClientOnly to 1, close any current OR and Dir
20326 listeners. Reported by mwenge.
20327 - When we get a consensus that's been signed by more people than
20328 we expect, don't log about it; it's not a big deal. Reported
20332 - Don't answer "/tor/networkstatus-bridges" directory requests if
20333 the request isn't encrypted.
20334 - Make "ClientOnly 1" config option disable directory ports too.
20335 - Patches from Karsten Loesing to make v2 hidden services more
20336 robust: work even when there aren't enough HSDir relays available;
20337 retry when a v2 rend desc fetch fails; but don't retry if we
20338 already have a usable v0 rend desc.
20341 Changes in version 0.2.0.17-alpha - 2008-01-17
20342 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
20345 - Make the tor-gencert man page get included correctly in the tarball.
20348 Changes in version 0.2.0.16-alpha - 2008-01-17
20349 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
20350 Loesing, and generally cleans up a lot of features and minor bugs.
20352 o New directory authorities:
20353 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
20356 o Major performance improvements:
20357 - Switch our old ring buffer implementation for one more like that
20358 used by free Unix kernels. The wasted space in a buffer with 1mb
20359 of data will now be more like 8k than 1mb. The new implementation
20360 also avoids realloc();realloc(); patterns that can contribute to
20361 memory fragmentation.
20364 - Configuration files now accept C-style strings as values. This
20365 helps encode characters not allowed in the current configuration
20366 file format, such as newline or #. Addresses bug 557.
20367 - Although we fixed bug 539 (where servers would send HTTP status 503
20368 responses _and_ send a body too), there are still servers out
20369 there that haven't upgraded. Therefore, make clients parse such
20370 bodies when they receive them.
20371 - When we're not serving v2 directory information, there is no reason
20372 to actually keep any around. Remove the obsolete files and directory
20373 on startup if they are very old and we aren't going to serve them.
20375 o Minor performance improvements:
20376 - Reference-count and share copies of address policy entries; only 5%
20377 of them were actually distinct.
20378 - Never walk through the list of logs if we know that no log is
20379 interested in a given message.
20382 - When an authority has not signed a consensus, do not try to
20383 download a nonexistent "certificate with key 00000000". Bugfix
20384 on 0.2.0.x. Fixes bug 569.
20385 - Fix a rare assert error when we're closing one of our threads:
20386 use a mutex to protect the list of logs, so we never write to the
20387 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
20388 bug 575, which is kind of the revenge of bug 222.
20389 - Patch from Karsten Loesing to complain less at both the client
20390 and the relay when a relay used to have the HSDir flag but doesn't
20391 anymore, and we try to upload a hidden service descriptor.
20392 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
20394 - Do not try to download missing certificates until we have tried
20395 to check our fallback consensus. Fixes bug 583.
20396 - Make bridges round reported GeoIP stats info up to the nearest
20397 estimate, not down. Now we can distinguish between "0 people from
20398 this country" and "1 person from this country".
20399 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
20400 - Avoid possible segfault if key generation fails in
20401 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
20402 - Avoid segfault in the case where a badly behaved v2 versioning
20403 directory sends a signed networkstatus with missing client-versions.
20405 - Avoid segfaults on certain complex invocations of
20406 router_get_by_hexdigest(). Bugfix on 0.1.2.
20407 - Correct bad index on array access in parse_http_time(). Bugfix
20409 - Fix possible bug in vote generation when server versions are present
20410 but client versions are not.
20411 - Fix rare bug on REDIRECTSTREAM control command when called with no
20412 port set: it could erroneously report an error when none had
20414 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
20415 compressing large objects and find ourselves with more than 4k
20416 left over. Bugfix on 0.2.0.
20417 - Fix a small memory leak when setting up a hidden service.
20418 - Fix a few memory leaks that could in theory happen under bizarre
20420 - Fix an assert if we post a general-purpose descriptor via the
20421 control port but that descriptor isn't mentioned in our current
20422 network consensus. Bug reported by Jon McLachlan; bugfix on
20425 o Minor features (controller):
20426 - Get NS events working again. Patch from tup.
20427 - The GETCONF command now escapes and quotes configuration values
20428 that don't otherwise fit into the torrc file.
20429 - The SETCONF command now handles quoted values correctly.
20431 o Minor features (directory authorities):
20432 - New configuration options to override default maximum number of
20433 servers allowed on a single IP address. This is important for
20434 running a test network on a single host.
20435 - Actually implement the -s option to tor-gencert.
20436 - Add a manual page for tor-gencert.
20438 o Minor features (bridges):
20439 - Bridge authorities no longer serve bridge descriptors over
20440 unencrypted connections.
20442 o Minor features (other):
20443 - Add hidden services and DNSPorts to the list of things that make
20444 Tor accept that it has running ports. Change starting Tor with no
20445 ports from a fatal error to a warning; we might change it back if
20446 this turns out to confuse anybody. Fixes bug 579.
20449 Changes in version 0.1.2.19 - 2008-01-17
20450 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
20451 exit policy a little bit more conservative so it's safer to run an
20452 exit relay on a home system, and fixes a variety of smaller issues.
20455 - Exit policies now reject connections that are addressed to a
20456 relay's public (external) IP address too, unless
20457 ExitPolicyRejectPrivate is turned off. We do this because too
20458 many relays are running nearby to services that trust them based
20459 on network address.
20462 - When the clock jumps forward a lot, do not allow the bandwidth
20463 buckets to become negative. Fixes bug 544.
20464 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
20465 on every successful resolve. Reported by Mike Perry.
20466 - Purge old entries from the "rephist" database and the hidden
20467 service descriptor database even when DirPort is zero.
20468 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
20469 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
20470 crashing or mis-answering these requests.
20471 - When we decide to send a 503 response to a request for servers, do
20472 not then also send the server descriptors: this defeats the whole
20473 purpose. Fixes bug 539.
20476 - Changing the ExitPolicyRejectPrivate setting should cause us to
20477 rebuild our server descriptor.
20478 - Fix handling of hex nicknames when answering controller requests for
20479 networkstatus by name, or when deciding whether to warn about
20480 unknown routers in a config option. (Patch from mwenge.)
20481 - Fix a couple of hard-to-trigger autoconf problems that could result
20482 in really weird results on platforms whose sys/types.h files define
20483 nonstandard integer types.
20484 - Don't try to create the datadir when running --verify-config or
20485 --hash-password. Resolves bug 540.
20486 - If we were having problems getting a particular descriptor from the
20487 directory caches, and then we learned about a new descriptor for
20488 that router, we weren't resetting our failure count. Reported
20490 - Although we fixed bug 539 (where servers would send HTTP status 503
20491 responses _and_ send a body too), there are still servers out there
20492 that haven't upgraded. Therefore, make clients parse such bodies
20493 when they receive them.
20494 - Run correctly on systems where rlim_t is larger than unsigned long.
20495 This includes some 64-bit systems.
20496 - Run correctly on platforms (like some versions of OS X 10.5) where
20497 the real limit for number of open files is OPEN_FILES, not rlim_max
20498 from getrlimit(RLIMIT_NOFILES).
20499 - Avoid a spurious free on base64 failure.
20500 - Avoid segfaults on certain complex invocations of
20501 router_get_by_hexdigest().
20502 - Fix rare bug on REDIRECTSTREAM control command when called with no
20503 port set: it could erroneously report an error when none had
20507 Changes in version 0.2.0.15-alpha - 2007-12-25
20508 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
20509 features added in 0.2.0.13-alpha.
20512 - Fix several remotely triggerable asserts based on DirPort requests
20513 for a v2 or v3 networkstatus object before we were prepared. This
20514 was particularly bad for 0.2.0.13 and later bridge relays, who
20515 would never have a v2 networkstatus and would thus always crash
20516 when used. Bugfixes on 0.2.0.x.
20517 - Estimate the v3 networkstatus size more accurately, rather than
20518 estimating it at zero bytes and giving it artificially high priority
20519 compared to other directory requests. Bugfix on 0.2.0.x.
20522 - Fix configure.in logic for cross-compilation.
20523 - When we load a bridge descriptor from the cache, and it was
20524 previously unreachable, mark it as retriable so we won't just
20525 ignore it. Also, try fetching a new copy immediately. Bugfixes
20527 - The bridge GeoIP stats were counting other relays, for example
20528 self-reachability and authority-reachability tests.
20531 - Support compilation to target iPhone; patch from cjacker huang.
20532 To build for iPhone, pass the --enable-iphone option to configure.
20535 Changes in version 0.2.0.14-alpha - 2007-12-23
20537 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
20538 without a datadirectory from a previous Tor install. Reported
20540 - Fix a crash when we fetch a descriptor that turns out to be
20541 unexpected (it used to be in our networkstatus when we started
20542 fetching it, but it isn't in our current networkstatus), and we
20543 aren't using bridges. Bugfix on 0.2.0.x.
20544 - Fix a crash when accessing hidden services: it would work the first
20545 time you use a given introduction point for your service, but
20546 on subsequent requests we'd be using garbage memory. Fixed by
20547 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
20548 - Fix a crash when we load a bridge descriptor from disk but we don't
20549 currently have a Bridge line for it in our torrc. Bugfix on
20553 - If bridge authorities set BridgePassword, they will serve a
20554 snapshot of known bridge routerstatuses from their DirPort to
20555 anybody who knows that password. Unset by default.
20558 - Make the unit tests build again.
20559 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
20560 - Make PublishServerDescriptor default to 1, so the default doesn't
20561 have to change as we invent new directory protocol versions.
20562 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
20563 be included unless sys/time.h is already included. Fixes
20564 bug 553. Bugfix on 0.2.0.x.
20565 - If we receive a general-purpose descriptor and then receive an
20566 identical bridge-purpose descriptor soon after, don't discard
20567 the next one as a duplicate.
20570 - If BridgeRelay is set to 1, then the default for
20571 PublishServerDescriptor is now "bridge" rather than "v2,v3".
20572 - If the user sets RelayBandwidthRate but doesn't set
20573 RelayBandwidthBurst, then make them equal rather than erroring out.
20576 Changes in version 0.2.0.13-alpha - 2007-12-21
20577 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
20578 Goodell, fixes many more bugs, and adds a lot of infrastructure for
20581 o New directory authorities:
20582 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
20586 - Only update guard status (usable / not usable) once we have
20587 enough directory information. This was causing us to always pick
20588 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
20589 causing us to discard all our guards on startup if we hadn't been
20590 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
20591 - Purge old entries from the "rephist" database and the hidden
20592 service descriptor databases even when DirPort is zero. Bugfix
20594 - We were ignoring our RelayBandwidthRate for the first 30 seconds
20595 after opening a circuit -- even a relayed circuit. Bugfix on
20597 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
20598 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
20599 crashing or mis-answering these types of requests.
20600 - Relays were publishing their server descriptor to v1 and v2
20601 directory authorities, but they didn't try publishing to v3-only
20602 authorities. Fix this; and also stop publishing to v1 authorities.
20604 - When we were reading router descriptors from cache, we were ignoring
20605 the annotations -- so for example we were reading in bridge-purpose
20606 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
20607 - When we decided to send a 503 response to a request for servers, we
20608 were then also sending the server descriptors: this defeats the
20609 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
20612 - Bridge relays now behave like clients with respect to time
20613 intervals for downloading new consensus documents -- otherwise they
20614 stand out. Bridge users now wait until the end of the interval,
20615 so their bridge relay will be sure to have a new consensus document.
20616 - Three new config options (AlternateDirAuthority,
20617 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
20618 user selectively replace the default directory authorities by type,
20619 rather than the all-or-nothing replacement that DirServer offers.
20620 - Tor can now be configured to read a GeoIP file from disk in one
20621 of two formats. This can be used by controllers to map IP addresses
20622 to countries. Eventually, it may support exit-by-country.
20623 - When possible, bridge relays remember which countries users
20624 are coming from, and report aggregate information in their
20625 extra-info documents, so that the bridge authorities can learn
20626 where Tor is blocked.
20627 - Bridge directory authorities now do reachability testing on the
20628 bridges they know. They provide router status summaries to the
20629 controller via "getinfo ns/purpose/bridge", and also dump summaries
20630 to a file periodically.
20631 - Stop fetching directory info so aggressively if your DirPort is
20632 on but your ORPort is off; stop fetching v2 dir info entirely.
20633 You can override these choices with the new FetchDirInfoEarly
20637 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
20638 consensus documents when there are too many relays at a single
20639 IP address. Now clear it in v2 network status documents too, and
20640 also clear it in routerinfo_t when the relay is no longer listed
20641 in the relevant networkstatus document.
20642 - Don't crash if we get an unexpected value for the
20643 PublishServerDescriptor config option. Reported by Matt Edman;
20644 bugfix on 0.2.0.9-alpha.
20645 - Our new v2 hidden service descriptor format allows descriptors
20646 that have no introduction points. But Tor crashed when we tried
20647 to build a descriptor with no intro points (and it would have
20648 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
20649 by Karsten Loesing.
20650 - Fix building with dmalloc 5.5.2 with glibc.
20651 - Reject uploaded descriptors and extrainfo documents if they're
20652 huge. Otherwise we'll cache them all over the network and it'll
20653 clog everything up. Reported by Aljosha Judmayer.
20654 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
20655 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
20656 - When the DANGEROUS_VERSION controller status event told us we're
20657 running an obsolete version, it used the string "OLD" to describe
20658 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
20659 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
20660 - If we can't expand our list of entry guards (e.g. because we're
20661 using bridges or we have StrictEntryNodes set), don't mark relays
20662 down when they fail a directory request. Otherwise we're too quick
20663 to mark all our entry points down. Bugfix on 0.1.2.x.
20664 - Fix handling of hex nicknames when answering controller requests for
20665 networkstatus by name, or when deciding whether to warn about unknown
20666 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
20667 - Fix a couple of hard-to-trigger autoconf problems that could result
20668 in really weird results on platforms whose sys/types.h files define
20669 nonstandard integer types. Bugfix on 0.1.2.x.
20670 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
20671 - Don't crash on name lookup when we have no current consensus. Fixes
20672 bug 538; bugfix on 0.2.0.x.
20673 - Only Tors that want to mirror the v2 directory info should
20674 create the "cached-status" directory in their datadir. (All Tors
20675 used to create it.) Bugfix on 0.2.0.9-alpha.
20676 - Directory authorities should only automatically download Extra Info
20677 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
20680 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
20681 consumers. (We already do this on HUP.)
20682 - Authorities and caches fetch the v2 networkstatus documents
20683 less often, now that v3 is encouraged.
20684 - Add a new config option BridgeRelay that specifies you want to
20685 be a bridge relay. Right now the only difference is that it makes
20686 you answer begin_dir requests, and it makes you cache dir info,
20687 even if your DirPort isn't on.
20688 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
20689 ask about source, timestamp of arrival, purpose, etc. We need
20690 something like this to help Vidalia not do GeoIP lookups on bridge
20692 - Allow multiple HashedControlPassword config lines, to support
20693 multiple controller passwords.
20694 - Authorities now decide whether they're authoritative for a given
20695 router based on the router's purpose.
20696 - New config options AuthDirBadDir and AuthDirListBadDirs for
20697 authorities to mark certain relays as "bad directories" in the
20698 networkstatus documents. Also supports the "!baddir" directive in
20699 the approved-routers file.
20702 Changes in version 0.2.0.12-alpha - 2007-11-16
20703 This twelfth development snapshot fixes some more build problems as
20704 well as a few minor bugs.
20707 - Make it build on OpenBSD again. Patch from tup.
20708 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
20709 package-building for Red Hat, OS X, etc.
20711 o Minor bugfixes (on 0.1.2.x):
20712 - Changing the ExitPolicyRejectPrivate setting should cause us to
20713 rebuild our server descriptor.
20715 o Minor bugfixes (on 0.2.0.x):
20716 - When we're lacking a consensus, don't try to perform rendezvous
20717 operations. Reported by Karsten Loesing.
20718 - Fix a small memory leak whenever we decide against using a
20719 newly picked entry guard. Reported by Mike Perry.
20720 - When authorities detected more than two relays running on the same
20721 IP address, they were clearing all the status flags but forgetting
20722 to clear the "hsdir" flag. So clients were being told that a
20723 given relay was the right choice for a v2 hsdir lookup, yet they
20724 never had its descriptor because it was marked as 'not running'
20726 - If we're trying to fetch a bridge descriptor and there's no way
20727 the bridge authority could help us (for example, we don't know
20728 a digest, or there is no bridge authority), don't be so eager to
20729 fall back to asking the bridge authority.
20730 - If we're using bridges or have strictentrynodes set, and our
20731 chosen exit is in the same family as all our bridges/entry guards,
20732 then be flexible about families.
20735 - When we negotiate a v2 link-layer connection (not yet implemented),
20736 accept RELAY_EARLY cells and turn them into RELAY cells if we've
20737 negotiated a v1 connection for their next step. Initial code for
20741 Changes in version 0.2.0.11-alpha - 2007-11-12
20742 This eleventh development snapshot fixes some build problems with
20743 the previous snapshot. It also includes a more secure-by-default exit
20744 policy for relays, fixes an enormous memory leak for exit relays, and
20745 fixes another bug where servers were falling out of the directory list.
20748 - Exit policies now reject connections that are addressed to a
20749 relay's public (external) IP address too, unless
20750 ExitPolicyRejectPrivate is turned off. We do this because too
20751 many relays are running nearby to services that trust them based
20752 on network address. Bugfix on 0.1.2.x.
20755 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
20756 on every successful resolve. Reported by Mike Perry; bugfix
20758 - On authorities, never downgrade to old router descriptors simply
20759 because they're listed in the consensus. This created a catch-22
20760 where we wouldn't list a new descriptor because there was an
20761 old one in the consensus, and we couldn't get the new one in the
20762 consensus because we wouldn't list it. Possible fix for bug 548.
20763 Also, this might cause bug 543 to appear on authorities; if so,
20764 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
20766 o Packaging fixes on 0.2.0.10-alpha:
20767 - We were including instructions about what to do with the
20768 src/config/fallback-consensus file, but we weren't actually
20769 including it in the tarball. Disable all of that for now.
20772 - Allow people to say PreferTunnelledDirConns rather than
20773 PreferTunneledDirConns, for those alternate-spellers out there.
20776 - Don't reevaluate all the information from our consensus document
20777 just because we've downloaded a v2 networkstatus that we intend
20778 to cache. Fixes bug 545; bugfix on 0.2.0.x.
20781 Changes in version 0.2.0.10-alpha - 2007-11-10
20782 This tenth development snapshot adds a third v3 directory authority
20783 run by Mike Perry, adds most of Karsten Loesing's new hidden service
20784 descriptor format, fixes a bad crash bug and new bridge bugs introduced
20785 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
20786 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
20787 addresses many more minor issues.
20789 o New directory authorities:
20790 - Set up ides (run by Mike Perry) as the third v3 directory authority.
20793 - Allow tunnelled directory connections to ask for an encrypted
20794 "begin_dir" connection or an anonymized "uses a full Tor circuit"
20795 connection independently. Now we can make anonymized begin_dir
20796 connections for (e.g.) more secure hidden service posting and
20798 - More progress on proposal 114: code from Karsten Loesing to
20799 implement new hidden service descriptor format.
20800 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
20801 accommodate the growing number of servers that use the default
20802 and are reaching it.
20803 - Directory authorities use a new formula for selecting which nodes
20804 to advertise as Guards: they must be in the top 7/8 in terms of
20805 how long we have known about them, and above the median of those
20806 nodes in terms of weighted fractional uptime.
20807 - Make "not enough dir info yet" warnings describe *why* Tor feels
20808 it doesn't have enough directory info yet.
20811 - Stop servers from crashing if they set a Family option (or
20812 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
20814 - Make bridge users work again -- the move to v3 directories in
20815 0.2.0.9-alpha had introduced a number of bugs that made bridges
20816 no longer work for clients.
20817 - When the clock jumps forward a lot, do not allow the bandwidth
20818 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
20820 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
20821 - When the consensus lists a router descriptor that we previously were
20822 mirroring, but that we considered non-canonical, reload the
20823 descriptor as canonical. This fixes bug 543 where Tor servers
20824 would start complaining after a few days that they don't have
20825 enough directory information to build a circuit.
20826 - Consider replacing the current consensus when certificates arrive
20827 that make the pending consensus valid. Previously, we were only
20828 considering replacement when the new certs _didn't_ help.
20829 - Fix an assert error on startup if we didn't already have the
20830 consensus and certs cached in our datadirectory: we were caching
20831 the consensus in consensus_waiting_for_certs but then free'ing it
20833 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
20834 Request) if we need more v3 certs but we've already got pending
20835 requests for all of them.
20836 - Correctly back off from failing certificate downloads. Fixes
20838 - Authorities don't vote on the Running flag if they have been running
20839 for less than 30 minutes themselves. Fixes bug 547, where a newly
20840 started authority would vote that everyone was down.
20842 o New requirements:
20843 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
20844 it, it had no AES, and it hasn't seen any security patches since
20848 - Clients now hold circuitless TLS connections open for 1.5 times
20849 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
20850 rebuild a new circuit over them within that timeframe. Previously,
20851 they held them open only for KeepalivePeriod (5 minutes).
20852 - Use "If-Modified-Since" to avoid retrieving consensus
20853 networkstatuses that we already have.
20854 - When we have no consensus, check FallbackNetworkstatusFile (defaults
20855 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
20856 we start knowing some directory caches.
20857 - When we receive a consensus from the future, warn about skew.
20858 - Improve skew reporting: try to give the user a better log message
20859 about how skewed they are, and how much this matters.
20860 - When we have a certificate for an authority, believe that
20861 certificate's claims about the authority's IP address.
20862 - New --quiet command-line option to suppress the default console log.
20863 Good in combination with --hash-password.
20864 - Authorities send back an X-Descriptor-Not-New header in response to
20865 an accepted-but-discarded descriptor upload. Partially implements
20867 - Make the log message for "tls error. breaking." more useful.
20868 - Better log messages about certificate downloads, to attempt to
20869 track down the second incarnation of bug 546.
20871 o Minor features (bridges):
20872 - If bridge users set UpdateBridgesFromAuthority, but the digest
20873 they ask for is a 404 from the bridge authority, they now fall
20874 back to trying the bridge directly.
20875 - Bridges now use begin_dir to publish their server descriptor to
20876 the bridge authority, even when they haven't set TunnelDirConns.
20878 o Minor features (controller):
20879 - When reporting clock skew, and we know that the clock is _at least
20880 as skewed_ as some value, but we don't know the actual value,
20881 report the value as a "minimum skew."
20884 - Update linux-tor-prio.sh script to allow QoS based on the uid of
20885 the Tor process. Patch from Marco Bonetti with tweaks from Mike
20889 - Refuse to start if both ORPort and UseBridges are set. Bugfix
20890 on 0.2.0.x, suggested by Matt Edman.
20891 - Don't stop fetching descriptors when FetchUselessDescriptors is
20892 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
20893 reported by tup and ioerror.
20894 - Better log message on vote from unknown authority.
20895 - Don't log "Launching 0 request for 0 router" message.
20897 o Minor bugfixes (memory leaks):
20898 - Stop leaking memory every time we parse a v3 certificate. Bugfix
20900 - Stop leaking memory every time we load a v3 certificate. Bugfix
20901 on 0.2.0.1-alpha. Fixes bug 536.
20902 - Stop leaking a cached networkstatus on exit. Bugfix on
20904 - Stop leaking voter information every time we free a consensus.
20905 Bugfix on 0.2.0.3-alpha.
20906 - Stop leaking signed data every time we check a voter signature.
20907 Bugfix on 0.2.0.3-alpha.
20908 - Stop leaking a signature every time we fail to parse a consensus or
20909 a vote. Bugfix on 0.2.0.3-alpha.
20910 - Stop leaking v2_download_status_map on shutdown. Bugfix on
20912 - Stop leaking conn->nickname every time we make a connection to a
20913 Tor relay without knowing its expected identity digest (e.g. when
20914 using bridges). Bugfix on 0.2.0.3-alpha.
20916 - Minor bugfixes (portability):
20917 - Run correctly on platforms where rlim_t is larger than unsigned
20918 long, and/or where the real limit for number of open files is
20919 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
20920 particular, these may be needed for OS X 10.5.
20923 Changes in version 0.1.2.18 - 2007-10-28
20924 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
20925 hidden service introduction that were causing huge delays, and a big
20926 bug that was causing some servers to disappear from the network status
20927 lists for a few hours each day.
20929 o Major bugfixes (crashes):
20930 - If a connection is shut down abruptly because of something that
20931 happened inside connection_flushed_some(), do not call
20932 connection_finished_flushing(). Should fix bug 451:
20933 "connection_stop_writing: Assertion conn->write_event failed"
20934 Bugfix on 0.1.2.7-alpha.
20935 - Fix possible segfaults in functions called from
20936 rend_process_relay_cell().
20938 o Major bugfixes (hidden services):
20939 - Hidden services were choosing introduction points uniquely by
20940 hexdigest, but when constructing the hidden service descriptor
20941 they merely wrote the (potentially ambiguous) nickname.
20942 - Clients now use the v2 intro format for hidden service
20943 connections: they specify their chosen rendezvous point by identity
20944 digest rather than by (potentially ambiguous) nickname. These
20945 changes could speed up hidden service connections dramatically.
20947 o Major bugfixes (other):
20948 - Stop publishing a new server descriptor just because we get a
20949 HUP signal. This led (in a roundabout way) to some servers getting
20950 dropped from the networkstatus lists for a few hours each day.
20951 - When looking for a circuit to cannibalize, consider family as well
20952 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
20953 circuit cannibalization).
20954 - When a router wasn't listed in a new networkstatus, we were leaving
20955 the flags for that router alone -- meaning it remained Named,
20956 Running, etc -- even though absence from the networkstatus means
20957 that it shouldn't be considered to exist at all anymore. Now we
20958 clear all the flags for routers that fall out of the networkstatus
20959 consensus. Fixes bug 529.
20962 - Don't try to access (or alter) the state file when running
20963 --list-fingerprint or --verify-config or --hash-password. Resolves
20965 - When generating information telling us how to extend to a given
20966 router, do not try to include the nickname if it is
20967 absent. Resolves bug 467.
20968 - Fix a user-triggerable segfault in expand_filename(). (There isn't
20969 a way to trigger this remotely.)
20970 - When sending a status event to the controller telling it that an
20971 OR address is reachable, set the port correctly. (Previously we
20972 were reporting the dir port.)
20973 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
20974 command. Bugfix on 0.1.2.17.
20975 - When loading bandwidth history, do not believe any information in
20976 the future. Fixes bug 434.
20977 - When loading entry guard information, do not believe any information
20979 - When we have our clock set far in the future and generate an
20980 onion key, then re-set our clock to be correct, we should not stop
20981 the onion key from getting rotated.
20982 - On some platforms, accept() can return a broken address. Detect
20983 this more quietly, and deal accordingly. Fixes bug 483.
20984 - It's not actually an error to find a non-pending entry in the DNS
20985 cache when canceling a pending resolve. Don't log unless stuff
20986 is fishy. Resolves bug 463.
20987 - Don't reset trusted dir server list when we set a configuration
20988 option. Patch from Robert Hogan.
20989 - Don't try to create the datadir when running --verify-config or
20990 --hash-password. Resolves bug 540.
20993 Changes in version 0.2.0.9-alpha - 2007-10-24
20994 This ninth development snapshot switches clients to the new v3 directory
20995 system; allows servers to be listed in the network status even when they
20996 have the same nickname as a registered server; and fixes many other
20997 bugs including a big one that was causing some servers to disappear
20998 from the network status lists for a few hours each day.
21000 o Major features (directory system):
21001 - Clients now download v3 consensus networkstatus documents instead
21002 of v2 networkstatus documents. Clients and caches now base their
21003 opinions about routers on these consensus documents. Clients only
21004 download router descriptors listed in the consensus.
21005 - Authorities now list servers who have the same nickname as
21006 a different named server, but list them with a new flag,
21007 "Unnamed". Now we can list servers that happen to pick the same
21008 nickname as a server that registered two years ago and then
21009 disappeared. Partially implements proposal 122.
21010 - If the consensus lists a router as "Unnamed", the name is assigned
21011 to a different router: do not identify the router by that name.
21012 Partially implements proposal 122.
21013 - Authorities can now come to a consensus on which method to use to
21014 compute the consensus. This gives us forward compatibility.
21017 - Stop publishing a new server descriptor just because we HUP or
21018 when we find our DirPort to be reachable but won't actually publish
21019 it. New descriptors without any real changes are dropped by the
21020 authorities, and can screw up our "publish every 18 hours" schedule.
21022 - When a router wasn't listed in a new networkstatus, we were leaving
21023 the flags for that router alone -- meaning it remained Named,
21024 Running, etc -- even though absence from the networkstatus means
21025 that it shouldn't be considered to exist at all anymore. Now we
21026 clear all the flags for routers that fall out of the networkstatus
21027 consensus. Fixes bug 529; bugfix on 0.1.2.x.
21028 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
21029 extrainfo documents and then discard them immediately for not
21030 matching the latest router. Bugfix on 0.2.0.1-alpha.
21032 o Minor features (v3 directory protocol):
21033 - Allow tor-gencert to generate a new certificate without replacing
21035 - Allow certificates to include an address.
21036 - When we change our directory-cache settings, reschedule all voting
21037 and download operations.
21038 - Reattempt certificate downloads immediately on failure, as long as
21039 we haven't failed a threshold number of times yet.
21040 - Delay retrying consensus downloads while we're downloading
21041 certificates to verify the one we just got. Also, count getting a
21042 consensus that we already have (or one that isn't valid) as a failure,
21043 and count failing to get the certificates after 20 minutes as a
21045 - Build circuits and download descriptors even if our consensus is a
21046 little expired. (This feature will go away once authorities are
21049 o Minor features (router descriptor cache):
21050 - If we find a cached-routers file that's been sitting around for more
21051 than 28 days unmodified, then most likely it's a leftover from
21052 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
21054 - When we (as a cache) download a descriptor because it was listed
21055 in a consensus, remember when the consensus was supposed to expire,
21056 and don't expire the descriptor until then.
21058 o Minor features (performance):
21059 - Call routerlist_remove_old_routers() much less often. This should
21060 speed startup, especially on directory caches.
21061 - Don't try to launch new descriptor downloads quite so often when we
21062 already have enough directory information to build circuits.
21063 - Base64 decoding was actually showing up on our profile when parsing
21064 the initial descriptor file; switch to an in-process all-at-once
21065 implementation that's about 3.5x times faster than calling out to
21068 o Minor features (compilation):
21069 - Detect non-ASCII platforms (if any still exist) and refuse to
21070 build there: some of our code assumes that 'A' is 65 and so on.
21072 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
21073 - Make the "next period" votes into "current period" votes immediately
21074 after publishing the consensus; avoid a heisenbug that made them
21075 stick around indefinitely.
21076 - When we discard a vote as a duplicate, do not report this as
21078 - Treat missing v3 keys or certificates as an error when running as a
21079 v3 directory authority.
21080 - When we're configured to be a v3 authority, but we're only listed
21081 as a non-v3 authority in our DirServer line for ourself, correct
21083 - If an authority doesn't have a qualified hostname, just put
21084 its address in the vote. This fixes the problem where we referred to
21085 "moria on moria:9031."
21086 - Distinguish between detached signatures for the wrong period, and
21087 detached signatures for a divergent vote.
21088 - Fix a small memory leak when computing a consensus.
21089 - When there's no concensus, we were forming a vote every 30
21090 minutes, but writing the "valid-after" line in our vote based
21091 on our configured V3AuthVotingInterval: so unless the intervals
21092 matched up, we immediately rejected our own vote because it didn't
21093 start at the voting interval that caused us to construct a vote.
21095 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
21096 - Delete unverified-consensus when the real consensus is set.
21097 - Consider retrying a consensus networkstatus fetch immediately
21098 after one fails: don't wait 60 seconds to notice.
21099 - When fetching a consensus as a cache, wait until a newer consensus
21100 should exist before trying to replace the current one.
21101 - Use a more forgiving schedule for retrying failed consensus
21102 downloads than for other types.
21104 o Minor bugfixes (other directory issues):
21105 - Correct the implementation of "download votes by digest." Bugfix on
21107 - Authorities no longer send back "400 you're unreachable please fix
21108 it" errors to Tor servers that aren't online all the time. We're
21109 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
21111 o Minor bugfixes (controller):
21112 - Don't reset trusted dir server list when we set a configuration
21113 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
21114 - Respond to INT and TERM SIGNAL commands before we execute the
21115 signal, in case the signal shuts us down. We had a patch in
21116 0.1.2.1-alpha that tried to do this by queueing the response on
21117 the connection's buffer before shutting down, but that really
21118 isn't the same thing at all. Bug located by Matt Edman.
21120 o Minor bugfixes (misc):
21121 - Correctly check for bad options to the "PublishServerDescriptor"
21122 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
21123 - Stop leaking memory on failing case of base32_decode, and make
21124 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
21125 - Don't try to download extrainfo documents when we're trying to
21126 fetch enough directory info to build a circuit: having enough
21127 info should get priority. Bugfix on 0.2.0.x.
21128 - Don't complain that "your server has not managed to confirm that its
21129 ports are reachable" if we haven't been able to build any circuits
21130 yet. Bug found by spending four hours without a v3 consensus. Bugfix
21132 - Detect the reason for failing to mmap a descriptor file we just
21133 wrote, and give a more useful log message. Fixes bug 533. Bugfix
21136 o Code simplifications and refactoring:
21137 - Remove support for the old bw_accounting file: we've been storing
21138 bandwidth accounting information in the state file since
21139 0.1.2.5-alpha. This may result in bandwidth accounting errors
21140 if you try to upgrade from 0.1.1.x or earlier, or if you try to
21141 downgrade to 0.1.1.x or earlier.
21142 - New convenience code to locate a file within the DataDirectory.
21143 - Move non-authority functionality out of dirvote.c.
21144 - Refactor the arguments for router_pick_{directory_|trusteddir}server
21145 so that they all take the same named flags.
21148 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
21149 Unix users an easy way to script their Tor process (e.g. by
21150 adjusting bandwidth based on the time of the day).
21153 Changes in version 0.2.0.8-alpha - 2007-10-12
21154 This eighth development snapshot fixes a crash bug that's been bothering
21155 us since February 2007, lets bridge authorities store a list of bridge
21156 descriptors they've seen, gets v3 directory voting closer to working,
21157 starts caching v3 directory consensus documents on directory mirrors,
21158 and fixes a variety of smaller issues including some minor memory leaks.
21160 o Major features (router descriptor cache):
21161 - Store routers in a file called cached-descriptors instead of in
21162 cached-routers. Initialize cached-descriptors from cached-routers
21163 if the old format is around. The new format allows us to store
21164 annotations along with descriptors.
21165 - Use annotations to record the time we received each descriptor, its
21166 source, and its purpose.
21167 - Disable the SETROUTERPURPOSE controller command: it is now
21169 - Controllers should now specify cache=no or cache=yes when using
21170 the +POSTDESCRIPTOR command.
21171 - Bridge authorities now write bridge descriptors to disk, meaning
21172 we can export them to other programs and begin distributing them
21175 o Major features (directory authorities):
21176 - When a v3 authority is missing votes or signatures, it now tries
21178 - Directory authorities track weighted fractional uptime as well as
21179 weighted mean-time-between failures. WFU is suitable for deciding
21180 whether a node is "usually up", while MTBF is suitable for deciding
21181 whether a node is "likely to stay up." We need both, because
21182 "usually up" is a good requirement for guards, while "likely to
21183 stay up" is a good requirement for long-lived connections.
21185 o Major features (v3 directory system):
21186 - Caches now download v3 network status documents as needed,
21187 and download the descriptors listed in them.
21188 - All hosts now attempt to download and keep fresh v3 authority
21189 certificates, and re-attempt after failures.
21190 - More internal-consistency checks for vote parsing.
21192 o Major bugfixes (crashes):
21193 - If a connection is shut down abruptly because of something that
21194 happened inside connection_flushed_some(), do not call
21195 connection_finished_flushing(). Should fix bug 451. Bugfix on
21198 o Major bugfixes (performance):
21199 - Fix really bad O(n^2) performance when parsing a long list of
21200 routers: Instead of searching the entire list for an "extra-info "
21201 string which usually wasn't there, once for every routerinfo
21202 we read, just scan lines forward until we find one we like.
21204 - When we add data to a write buffer in response to the data on that
21205 write buffer getting low because of a flush, do not consider the
21206 newly added data as a candidate for immediate flushing, but rather
21207 make it wait until the next round of writing. Otherwise, we flush
21208 and refill recursively, and a single greedy TLS connection can
21209 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
21211 o Minor features (v3 authority system):
21212 - Add more ways for tools to download the votes that lead to the
21214 - Send a 503 when low on bandwidth and a vote, consensus, or
21215 certificate is requested.
21216 - If-modified-since is now implemented properly for all kinds of
21217 certificate requests.
21219 o Minor bugfixes (network statuses):
21220 - Tweak the implementation of proposal 109 slightly: allow at most
21221 two Tor servers on the same IP address, except if it's the location
21222 of a directory authority, in which case allow five. Bugfix on
21225 o Minor bugfixes (controller):
21226 - When sending a status event to the controller telling it that an
21227 OR address is reachable, set the port correctly. (Previously we
21228 were reporting the dir port.) Bugfix on 0.1.2.x.
21230 o Minor bugfixes (v3 directory system):
21231 - Fix logic to look up a cert by its signing key digest. Bugfix on
21233 - Only change the reply to a vote to "OK" if it's not already
21234 set. This gets rid of annoying "400 OK" log messages, which may
21235 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
21236 - When we get a valid consensus, recompute the voting schedule.
21237 - Base the valid-after time of a vote on the consensus voting
21238 schedule, not on our preferred schedule.
21239 - Make the return values and messages from signature uploads and
21240 downloads more sensible.
21241 - Fix a memory leak when serving votes and consensus documents, and
21242 another when serving certificates.
21244 o Minor bugfixes (performance):
21245 - Use a slightly simpler string hashing algorithm (copying Python's
21246 instead of Java's) and optimize our digest hashing algorithm to take
21247 advantage of 64-bit platforms and to remove some possibly-costly
21249 - Fix a minor memory leak whenever we parse guards from our state
21250 file. Bugfix on 0.2.0.7-alpha.
21251 - Fix a minor memory leak whenever we write out a file. Bugfix on
21253 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
21254 command. Bugfix on 0.2.0.5-alpha.
21256 o Minor bugfixes (portability):
21257 - On some platforms, accept() can return a broken address. Detect
21258 this more quietly, and deal accordingly. Fixes bug 483.
21259 - Stop calling tor_strlower() on uninitialized memory in some cases.
21260 Bugfix in 0.2.0.7-alpha.
21262 o Minor bugfixes (usability):
21263 - Treat some 403 responses from directory servers as INFO rather than
21264 WARN-severity events.
21265 - It's not actually an error to find a non-pending entry in the DNS
21266 cache when canceling a pending resolve. Don't log unless stuff is
21267 fishy. Resolves bug 463.
21269 o Minor bugfixes (anonymity):
21270 - Never report that we've used more bandwidth than we're willing to
21271 relay: it leaks how much non-relay traffic we're using. Resolves
21273 - When looking for a circuit to cannibalize, consider family as well
21274 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
21275 circuit cannibalization).
21277 o Code simplifications and refactoring:
21278 - Make a bunch of functions static. Remove some dead code.
21279 - Pull out about a third of the really big routerlist.c; put it in a
21280 new module, networkstatus.c.
21281 - Merge the extra fields in local_routerstatus_t back into
21282 routerstatus_t: we used to need one routerstatus_t for each
21283 authority's opinion, plus a local_routerstatus_t for the locally
21284 computed consensus opinion. To save space, we put the locally
21285 modified fields into local_routerstatus_t, and only the common
21286 stuff into routerstatus_t. But once v3 directories are in use,
21287 clients and caches will no longer need to hold authority opinions;
21288 thus, the rationale for keeping the types separate is now gone.
21289 - Make the code used to reschedule and reattempt downloads more
21291 - Turn all 'Are we a directory server/mirror?' logic into a call to
21293 - Remove the code to generate the oldest (v1) directory format.
21294 The code has been disabled since 0.2.0.5-alpha.
21297 Changes in version 0.2.0.7-alpha - 2007-09-21
21298 This seventh development snapshot makes bridges work again, makes bridge
21299 authorities work for the first time, fixes two huge performance flaws
21300 in hidden services, and fixes a variety of minor issues.
21302 o New directory authorities:
21303 - Set up moria1 and tor26 as the first v3 directory authorities. See
21304 doc/spec/dir-spec.txt for details on the new directory design.
21306 o Major bugfixes (crashes):
21307 - Fix possible segfaults in functions called from
21308 rend_process_relay_cell(). Bugfix on 0.1.2.x.
21310 o Major bugfixes (bridges):
21311 - Fix a bug that made servers send a "404 Not found" in response to
21312 attempts to fetch their server descriptor. This caused Tor servers
21313 to take many minutes to establish reachability for their DirPort,
21314 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
21315 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
21316 users configure that and specify a bridge with an identity
21317 fingerprint, now they will lookup the bridge descriptor at the
21318 default bridge authority via a one-hop tunnel, but once circuits
21319 are established they will switch to a three-hop tunnel for later
21320 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
21322 o Major bugfixes (hidden services):
21323 - Hidden services were choosing introduction points uniquely by
21324 hexdigest, but when constructing the hidden service descriptor
21325 they merely wrote the (potentially ambiguous) nickname.
21326 - Clients now use the v2 intro format for hidden service
21327 connections: they specify their chosen rendezvous point by identity
21328 digest rather than by (potentially ambiguous) nickname. Both
21329 are bugfixes on 0.1.2.x, and they could speed up hidden service
21330 connections dramatically. Thanks to Karsten Loesing.
21332 o Minor features (security):
21333 - As a client, do not believe any server that tells us that an
21334 address maps to an internal address space.
21335 - Make it possible to enable HashedControlPassword and
21336 CookieAuthentication at the same time.
21338 o Minor features (guard nodes):
21339 - Tag every guard node in our state file with the version that
21340 we believe added it, or with our own version if we add it. This way,
21341 if a user temporarily runs an old version of Tor and then switches
21342 back to a new one, she doesn't automatically lose her guards.
21344 o Minor features (speed):
21345 - When implementing AES counter mode, update only the portions of the
21346 counter buffer that need to change, and don't keep separate
21347 network-order and host-order counters when they are the same (i.e.,
21348 on big-endian hosts.)
21350 o Minor features (controller):
21351 - Accept LF instead of CRLF on controller, since some software has a
21352 hard time generating real Internet newlines.
21353 - Add GETINFO values for the server status events
21354 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
21357 o Removed features:
21358 - Routers no longer include bandwidth-history lines in their
21359 descriptors; this information is already available in extra-info
21360 documents, and including it in router descriptors took up 60%
21361 (!) of compressed router descriptor downloads. Completes
21362 implementation of proposal 104.
21363 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
21364 and TorControl.py, as they use the old v0 controller protocol,
21365 and are obsoleted by TorFlow anyway.
21366 - Drop support for v1 rendezvous descriptors, since we never used
21367 them anyway, and the code has probably rotted by now. Based on
21368 patch from Karsten Loesing.
21369 - On OSX, stop warning the user that kqueue support in libevent is
21370 "experimental", since it seems to have worked fine for ages.
21373 - When generating information telling us how to extend to a given
21374 router, do not try to include the nickname if it is absent. Fixes
21375 bug 467. Bugfix on 0.2.0.3-alpha.
21376 - Fix a user-triggerable (but not remotely-triggerable) segfault
21377 in expand_filename(). Bugfix on 0.1.2.x.
21378 - Fix a memory leak when freeing incomplete requests from DNSPort.
21379 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
21380 - Don't try to access (or alter) the state file when running
21381 --list-fingerprint or --verify-config or --hash-password. (Resolves
21382 bug 499.) Bugfix on 0.1.2.x.
21383 - Servers used to decline to publish their DirPort if their
21384 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
21385 were below a threshold. Now they only look at BandwidthRate and
21386 RelayBandwidthRate. Bugfix on 0.1.2.x.
21387 - Remove an optimization in the AES counter-mode code that assumed
21388 that the counter never exceeded 2^68. When the counter can be set
21389 arbitrarily as an IV (as it is by Karsten's new hidden services
21390 code), this assumption no longer holds. Bugfix on 0.1.2.x.
21391 - Resume listing "AUTHORITY" flag for authorities in network status.
21392 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
21394 o Code simplifications and refactoring:
21395 - Revamp file-writing logic so we don't need to have the entire
21396 contents of a file in memory at once before we write to disk. Tor,
21398 - Turn "descriptor store" into a full-fledged type.
21399 - Move all NT services code into a separate source file.
21400 - Unify all code that computes medians, percentile elements, etc.
21401 - Get rid of a needless malloc when parsing address policies.
21404 Changes in version 0.1.2.17 - 2007-08-30
21405 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
21406 X bundles. Vidalia 0.0.14 makes authentication required for the
21407 ControlPort in the default configuration, which addresses important
21408 security risks. Everybody who uses Vidalia (or another controller)
21411 In addition, this Tor update fixes major load balancing problems with
21412 path selection, which should speed things up a lot once many people
21415 o Major bugfixes (security):
21416 - We removed support for the old (v0) control protocol. It has been
21417 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
21418 become more of a headache than it's worth.
21420 o Major bugfixes (load balancing):
21421 - When choosing nodes for non-guard positions, weight guards
21422 proportionally less, since they already have enough load. Patch
21424 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
21425 will allow fast Tor servers to get more attention.
21426 - When we're upgrading from an old Tor version, forget our current
21427 guards and pick new ones according to the new weightings. These
21428 three load balancing patches could raise effective network capacity
21429 by a factor of four. Thanks to Mike Perry for measurements.
21431 o Major bugfixes (stream expiration):
21432 - Expire not-yet-successful application streams in all cases if
21433 they've been around longer than SocksTimeout. Right now there are
21434 some cases where the stream will live forever, demanding a new
21435 circuit every 15 seconds. Fixes bug 454; reported by lodger.
21437 o Minor features (controller):
21438 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
21439 is valid before any authentication has been received. It tells
21440 a controller what kind of authentication is expected, and what
21441 protocol is spoken. Implements proposal 119.
21443 o Minor bugfixes (performance):
21444 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
21445 greatly speeding up loading cached-routers from disk on startup.
21446 - Disable sentinel-based debugging for buffer code: we squashed all
21447 the bugs that this was supposed to detect a long time ago, and now
21448 its only effect is to change our buffer sizes from nice powers of
21449 two (which platform mallocs tend to like) to values slightly over
21450 powers of two (which make some platform mallocs sad).
21452 o Minor bugfixes (misc):
21453 - If exit bandwidth ever exceeds one third of total bandwidth, then
21454 use the correct formula to weight exit nodes when choosing paths.
21455 Based on patch from Mike Perry.
21456 - Choose perfectly fairly among routers when choosing by bandwidth and
21457 weighting by fraction of bandwidth provided by exits. Previously, we
21458 would choose with only approximate fairness, and correct ourselves
21459 if we ran off the end of the list.
21460 - If we require CookieAuthentication but we fail to write the
21461 cookie file, we would warn but not exit, and end up in a state
21462 where no controller could authenticate. Now we exit.
21463 - If we require CookieAuthentication, stop generating a new cookie
21464 every time we change any piece of our config.
21465 - Refuse to start with certain directory authority keys, and
21466 encourage people using them to stop.
21467 - Terminate multi-line control events properly. Original patch
21469 - Fix a minor memory leak when we fail to find enough suitable
21470 servers to choose a circuit.
21471 - Stop leaking part of the descriptor when we run into a particularly
21472 unparseable piece of it.
21475 Changes in version 0.2.0.6-alpha - 2007-08-26
21476 This sixth development snapshot features a new Vidalia version in the
21477 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
21478 the ControlPort in the default configuration, which addresses important
21481 In addition, this snapshot fixes major load balancing problems
21482 with path selection, which should speed things up a lot once many
21483 people have upgraded. The directory authorities also use a new
21484 mean-time-between-failure approach to tracking which servers are stable,
21485 rather than just looking at the most recent uptime.
21487 o New directory authorities:
21488 - Set up Tonga as the default bridge directory authority.
21491 - Directory authorities now track servers by weighted
21492 mean-times-between-failures. When we have 4 or more days of data,
21493 use measured MTBF rather than declared uptime to decide whether
21494 to call a router Stable. Implements proposal 108.
21496 o Major bugfixes (load balancing):
21497 - When choosing nodes for non-guard positions, weight guards
21498 proportionally less, since they already have enough load. Patch
21500 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
21501 will allow fast Tor servers to get more attention.
21502 - When we're upgrading from an old Tor version, forget our current
21503 guards and pick new ones according to the new weightings. These
21504 three load balancing patches could raise effective network capacity
21505 by a factor of four. Thanks to Mike Perry for measurements.
21507 o Major bugfixes (descriptor parsing):
21508 - Handle unexpected whitespace better in malformed descriptors. Bug
21509 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
21512 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
21513 GETINFO for Torstat to use until it can switch to using extrainfos.
21514 - Optionally (if built with -DEXPORTMALLINFO) export the output
21515 of mallinfo via http, as tor/mallinfo.txt. Only accessible
21519 - Do not intermix bridge routers with controller-added
21520 routers. (Bugfix on 0.2.0.x)
21521 - Do not fail with an assert when accept() returns an unexpected
21522 address family. Addresses but does not wholly fix bug 483. (Bugfix
21524 - Let directory authorities startup even when they can't generate
21525 a descriptor immediately, e.g. because they don't know their
21527 - Stop putting the authentication cookie in a file called "0"
21528 in your working directory if you don't specify anything for the
21529 new CookieAuthFile option. Reported by Matt Edman.
21530 - Make it possible to read the PROTOCOLINFO response in a way that
21531 conforms to our control-spec. Reported by Matt Edman.
21532 - Fix a minor memory leak when we fail to find enough suitable
21533 servers to choose a circuit. Bugfix on 0.1.2.x.
21534 - Stop leaking part of the descriptor when we run into a particularly
21535 unparseable piece of it. Bugfix on 0.1.2.x.
21536 - Unmap the extrainfo cache file on exit.
21539 Changes in version 0.2.0.5-alpha - 2007-08-19
21540 This fifth development snapshot fixes compilation on Windows again;
21541 fixes an obnoxious client-side bug that slowed things down and put
21542 extra load on the network; gets us closer to using the v3 directory
21543 voting scheme; makes it easier for Tor controllers to use cookie-based
21544 authentication; and fixes a variety of other bugs.
21546 o Removed features:
21547 - Version 1 directories are no longer generated in full. Instead,
21548 authorities generate and serve "stub" v1 directories that list
21549 no servers. This will stop Tor versions 0.1.0.x and earlier from
21550 working, but (for security reasons) nobody should be running those
21553 o Major bugfixes (compilation, 0.2.0.x):
21554 - Try to fix Win32 compilation again: improve checking for IPv6 types.
21555 - Try to fix MSVC compilation: build correctly on platforms that do
21556 not define s6_addr16 or s6_addr32.
21557 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
21560 o Major bugfixes (stream expiration):
21561 - Expire not-yet-successful application streams in all cases if
21562 they've been around longer than SocksTimeout. Right now there are
21563 some cases where the stream will live forever, demanding a new
21564 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
21565 reported by lodger.
21567 o Minor features (directory servers):
21568 - When somebody requests a list of statuses or servers, and we have
21569 none of those, return a 404 rather than an empty 200.
21571 o Minor features (directory voting):
21572 - Store v3 consensus status consensuses on disk, and reload them
21575 o Minor features (security):
21576 - Warn about unsafe ControlPort configurations.
21577 - Refuse to start with certain directory authority keys, and
21578 encourage people using them to stop.
21580 o Minor features (controller):
21581 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
21582 is valid before any authentication has been received. It tells
21583 a controller what kind of authentication is expected, and what
21584 protocol is spoken. Implements proposal 119.
21585 - New config option CookieAuthFile to choose a new location for the
21586 cookie authentication file, and config option
21587 CookieAuthFileGroupReadable to make it group-readable.
21589 o Minor features (unit testing):
21590 - Add command-line arguments to unit-test executable so that we can
21591 invoke any chosen test from the command line rather than having
21592 to run the whole test suite at once; and so that we can turn on
21593 logging for the unit tests.
21595 o Minor bugfixes (on 0.1.2.x):
21596 - If we require CookieAuthentication but we fail to write the
21597 cookie file, we would warn but not exit, and end up in a state
21598 where no controller could authenticate. Now we exit.
21599 - If we require CookieAuthentication, stop generating a new cookie
21600 every time we change any piece of our config.
21601 - When loading bandwidth history, do not believe any information in
21602 the future. Fixes bug 434.
21603 - When loading entry guard information, do not believe any information
21605 - When we have our clock set far in the future and generate an
21606 onion key, then re-set our clock to be correct, we should not stop
21607 the onion key from getting rotated.
21608 - Clean up torrc sample config file.
21609 - Do not automatically run configure from autogen.sh. This
21610 non-standard behavior tended to annoy people who have built other
21613 o Minor bugfixes (on 0.2.0.x):
21614 - Fix a bug with AutomapHostsOnResolve that would always cause
21615 the second request to fail. Bug reported by Kate. Bugfix on
21617 - Fix a bug in ADDRMAP controller replies that would sometimes
21618 try to print a NULL. Patch from tup.
21619 - Read v3 directory authority keys from the right location.
21620 - Numerous bugfixes to directory voting code.
21623 Changes in version 0.1.2.16 - 2007-08-01
21624 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
21625 remote attacker in certain situations to rewrite the user's torrc
21626 configuration file. This can completely compromise anonymity of users
21627 in most configurations, including those running the Vidalia bundles,
21628 TorK, etc. Or worse.
21630 o Major security fixes:
21631 - Close immediately after missing authentication on control port;
21632 do not allow multiple authentication attempts.
21635 Changes in version 0.2.0.4-alpha - 2007-08-01
21636 This fourth development snapshot fixes a critical security vulnerability
21637 for most users, specifically those running Vidalia, TorK, etc. Everybody
21638 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
21640 o Major security fixes:
21641 - Close immediately after missing authentication on control port;
21642 do not allow multiple authentication attempts.
21644 o Major bugfixes (compilation):
21645 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
21648 o Minor features (performance):
21649 - Be even more aggressive about releasing RAM from small
21650 empty buffers. Thanks to our free-list code, this shouldn't be too
21651 performance-intensive.
21652 - Disable sentinel-based debugging for buffer code: we squashed all
21653 the bugs that this was supposed to detect a long time ago, and
21654 now its only effect is to change our buffer sizes from nice
21655 powers of two (which platform mallocs tend to like) to values
21656 slightly over powers of two (which make some platform mallocs sad).
21657 - Log malloc statistics from mallinfo() on platforms where it
21661 Changes in version 0.2.0.3-alpha - 2007-07-29
21662 This third development snapshot introduces new experimental
21663 blocking-resistance features and a preliminary version of the v3
21664 directory voting design, and includes many other smaller features
21668 - The first pieces of our "bridge" design for blocking-resistance
21669 are implemented. People can run bridge directory authorities;
21670 people can run bridges; and people can configure their Tor clients
21671 with a set of bridges to use as the first hop into the Tor network.
21672 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
21674 - Create listener connections before we setuid to the configured
21675 User and Group. Now non-Windows users can choose port values
21676 under 1024, start Tor as root, and have Tor bind those ports
21677 before it changes to another UID. (Windows users could already
21679 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
21680 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
21681 on "vserver" accounts. (Patch from coderman.)
21682 - Be even more aggressive about separating local traffic from relayed
21683 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
21685 o Major features (experimental):
21686 - First cut of code for "v3 dir voting": directory authorities will
21687 vote on a common network status document rather than each publishing
21688 their own opinion. This code needs more testing and more corner-case
21689 handling before it's ready for use.
21692 - Directory authorities now call routers Fast if their bandwidth is
21693 at least 100KB/s, and consider their bandwidth adequate to be a
21694 Guard if it is at least 250KB/s, no matter the medians. This fix
21695 complements proposal 107. [Bugfix on 0.1.2.x]
21696 - Directory authorities now never mark more than 3 servers per IP as
21697 Valid and Running. (Implements proposal 109, by Kevin Bauer and
21699 - Minor change to organizationName and commonName generation
21700 procedures in TLS certificates during Tor handshakes, to invalidate
21701 some earlier censorware approaches. This is not a long-term
21702 solution, but applying it will give us a bit of time to look into
21703 the epidemiology of countermeasures as they spread.
21705 o Major bugfixes (directory):
21706 - Rewrite directory tokenization code to never run off the end of
21707 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
21709 o Minor features (controller):
21710 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
21711 match requests to applications. (Patch from Robert Hogan.)
21712 - Report address and port correctly on connections to DNSPort. (Patch
21713 from Robert Hogan.)
21714 - Add a RESOLVE command to launch hostname lookups. (Original patch
21715 from Robert Hogan.)
21716 - Add GETINFO status/enough-dir-info to let controllers tell whether
21717 Tor has downloaded sufficient directory information. (Patch
21719 - You can now use the ControlSocket option to tell Tor to listen for
21720 controller connections on Unix domain sockets on systems that
21721 support them. (Patch from Peter Palfrader.)
21722 - STREAM NEW events are generated for DNSPort requests and for
21723 tunneled directory connections. (Patch from Robert Hogan.)
21724 - New "GETINFO address-mappings/*" command to get address mappings
21725 with expiry information. "addr-mappings/*" is now deprecated.
21728 o Minor features (misc):
21729 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
21731 - The tor-gencert tool for v3 directory authorities now creates all
21732 files as readable to the file creator only, and write-protects
21733 the authority identity key.
21734 - When dumping memory usage, list bytes used in buffer memory
21736 - When running with dmalloc, dump more stats on hup and on exit.
21737 - Directory authorities now fail quickly and (relatively) harmlessly
21738 if they generate a network status document that is somehow
21741 o Traffic load balancing improvements:
21742 - If exit bandwidth ever exceeds one third of total bandwidth, then
21743 use the correct formula to weight exit nodes when choosing paths.
21744 (Based on patch from Mike Perry.)
21745 - Choose perfectly fairly among routers when choosing by bandwidth and
21746 weighting by fraction of bandwidth provided by exits. Previously, we
21747 would choose with only approximate fairness, and correct ourselves
21748 if we ran off the end of the list. [Bugfix on 0.1.2.x]
21750 o Performance improvements:
21751 - Be more aggressive with freeing buffer RAM or putting it on the
21753 - Use Critical Sections rather than Mutexes for synchronizing threads
21754 on win32; Mutexes are heavier-weight, and designed for synchronizing
21757 o Deprecated and removed features:
21758 - RedirectExits is now deprecated.
21759 - Stop allowing address masks that do not correspond to bit prefixes.
21760 We have warned about these for a really long time; now it's time
21761 to reject them. (Patch from croup.)
21763 o Minor bugfixes (directory):
21764 - Fix another crash bug related to extra-info caching. (Bug found by
21765 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
21766 - Directories no longer return a "304 not modified" when they don't
21767 have the networkstatus the client asked for. Also fix a memory
21768 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
21769 - We had accidentally labelled 0.1.2.x directory servers as not
21770 suitable for begin_dir requests, and had labelled no directory
21771 servers as suitable for uploading extra-info documents. [Bugfix
21774 o Minor bugfixes (dns):
21775 - Fix a crash when DNSPort is set more than once. (Patch from Robert
21776 Hogan.) [Bugfix on 0.2.0.2-alpha]
21777 - Add DNSPort connections to the global connection list, so that we
21778 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
21780 - Fix a dangling reference that could lead to a crash when DNSPort is
21781 changed or closed (Patch from Robert Hogan.) [Bugfix on
21784 o Minor bugfixes (controller):
21785 - Provide DNS expiry times in GMT, not in local time. For backward
21786 compatibility, ADDRMAP events only provide GMT expiry in an extended
21787 field. "GETINFO address-mappings" always does the right thing.
21788 - Use CRLF line endings properly in NS events.
21789 - Terminate multi-line control events properly. (Original patch
21790 from tup.) [Bugfix on 0.1.2.x-alpha]
21791 - Do not include spaces in SOURCE_ADDR fields in STREAM
21792 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
21795 Changes in version 0.1.2.15 - 2007-07-17
21796 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
21797 problems, fixes compilation on BSD, and fixes a variety of other
21798 bugs. Everybody should upgrade.
21800 o Major bugfixes (compilation):
21801 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
21803 o Major bugfixes (crashes):
21804 - Try even harder not to dereference the first character after
21805 an mmap(). Reported by lodger.
21806 - Fix a crash bug in directory authorities when we re-number the
21807 routerlist while inserting a new router.
21808 - When the cached-routers file is an even multiple of the page size,
21809 don't run off the end and crash. (Fixes bug 455; based on idea
21811 - Fix eventdns.c behavior on Solaris: It is critical to include
21812 orconfig.h _before_ sys/types.h, so that we can get the expected
21813 definition of _FILE_OFFSET_BITS.
21815 o Major bugfixes (security):
21816 - Fix a possible buffer overrun when using BSD natd support. Bug
21818 - When sending destroy cells from a circuit's origin, don't include
21819 the reason for tearing down the circuit. The spec says we didn't,
21820 and now we actually don't. Reported by lodger.
21821 - Keep streamids from different exits on a circuit separate. This
21822 bug may have allowed other routers on a given circuit to inject
21823 cells into streams. Reported by lodger; fixes bug 446.
21824 - If there's a never-before-connected-to guard node in our list,
21825 never choose any guards past it. This way we don't expand our
21826 guard list unless we need to.
21828 o Minor bugfixes (guard nodes):
21829 - Weight guard selection by bandwidth, so that low-bandwidth nodes
21830 don't get overused as guards.
21832 o Minor bugfixes (directory):
21833 - Correctly count the number of authorities that recommend each
21834 version. Previously, we were under-counting by 1.
21835 - Fix a potential crash bug when we load many server descriptors at
21836 once and some of them make others of them obsolete. Fixes bug 458.
21838 o Minor bugfixes (hidden services):
21839 - Stop tearing down the whole circuit when the user asks for a
21840 connection to a port that the hidden service didn't configure.
21843 o Minor bugfixes (misc):
21844 - On Windows, we were preventing other processes from reading
21845 cached-routers while Tor was running. Reported by janbar.
21846 - Fix a possible (but very unlikely) bug in picking routers by
21847 bandwidth. Add a log message to confirm that it is in fact
21848 unlikely. Patch from lodger.
21849 - Backport a couple of memory leak fixes.
21850 - Backport miscellaneous cosmetic bugfixes.
21853 Changes in version 0.2.0.2-alpha - 2007-06-02
21854 o Major bugfixes on 0.2.0.1-alpha:
21855 - Fix an assertion failure related to servers without extra-info digests.
21856 Resolves bugs 441 and 442.
21858 o Minor features (directory):
21859 - Support "If-Modified-Since" when answering HTTP requests for
21860 directories, running-routers documents, and network-status documents.
21861 (There's no need to support it for router descriptors, since those
21862 are downloaded by descriptor digest.)
21864 o Minor build issues:
21865 - Clear up some MIPSPro compiler warnings.
21866 - When building from a tarball on a machine that happens to have SVK
21867 installed, report the micro-revision as whatever version existed
21868 in the tarball, not as "x".
21871 Changes in version 0.2.0.1-alpha - 2007-06-01
21872 This early development snapshot provides new features for people running
21873 Tor as both a client and a server (check out the new RelayBandwidth
21874 config options); lets Tor run as a DNS proxy; and generally moves us
21875 forward on a lot of fronts.
21877 o Major features, server usability:
21878 - New config options RelayBandwidthRate and RelayBandwidthBurst:
21879 a separate set of token buckets for relayed traffic. Right now
21880 relayed traffic is defined as answers to directory requests, and
21881 OR connections that don't have any local circuits on them.
21883 o Major features, client usability:
21884 - A client-side DNS proxy feature to replace the need for
21885 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
21886 for DNS requests on port 9999, use the Tor network to resolve them
21887 anonymously, and send the reply back like a regular DNS server.
21888 The code still only implements a subset of DNS.
21889 - Make PreferTunneledDirConns and TunnelDirConns work even when
21890 we have no cached directory info. This means Tor clients can now
21891 do all of their connections protected by TLS.
21893 o Major features, performance and efficiency:
21894 - Directory authorities accept and serve "extra info" documents for
21895 routers. These documents contain fields from router descriptors
21896 that aren't usually needed, and that use a lot of excess
21897 bandwidth. Once these fields are removed from router descriptors,
21898 the bandwidth savings should be about 60%. [Partially implements
21900 - Servers upload extra-info documents to any authority that accepts
21901 them. Authorities (and caches that have been configured to download
21902 extra-info documents) download them as needed. [Partially implements
21904 - Change the way that Tor buffers data that it is waiting to write.
21905 Instead of queueing data cells in an enormous ring buffer for each
21906 client->OR or OR->OR connection, we now queue cells on a separate
21907 queue for each circuit. This lets us use less slack memory, and
21908 will eventually let us be smarter about prioritizing different kinds
21910 - Use memory pools to allocate cells with better speed and memory
21911 efficiency, especially on platforms where malloc() is inefficient.
21912 - Stop reading on edge connections when their corresponding circuit
21913 buffers are full; start again as the circuits empty out.
21915 o Major features, other:
21916 - Add an HSAuthorityRecordStats option that hidden service authorities
21917 can use to track statistics of overall hidden service usage without
21918 logging information that would be very useful to an attacker.
21919 - Start work implementing multi-level keys for directory authorities:
21920 Add a standalone tool to generate key certificates. (Proposal 103.)
21923 - Directory authorities now call routers Stable if they have an
21924 uptime of at least 30 days, even if that's not the median uptime
21925 in the network. Implements proposal 107, suggested by Kevin Bauer
21928 o Minor fixes (resource management):
21929 - Count the number of open sockets separately from the number
21930 of active connection_t objects. This will let us avoid underusing
21931 our allocated connection limit.
21932 - We no longer use socket pairs to link an edge connection to an
21933 anonymous directory connection or a DirPort test connection.
21934 Instead, we track the link internally and transfer the data
21935 in-process. This saves two sockets per "linked" connection (at the
21936 client and at the server), and avoids the nasty Windows socketpair()
21938 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
21939 for every single inactive connection_t. Free items from the
21940 4k/16k-buffer free lists when they haven't been used for a while.
21942 o Minor features (build):
21943 - Make autoconf search for libevent, openssl, and zlib consistently.
21944 - Update deprecated macros in configure.in.
21945 - When warning about missing headers, tell the user to let us
21946 know if the compile succeeds anyway, so we can downgrade the
21948 - Include the current subversion revision as part of the version
21949 string: either fetch it directly if we're in an SVN checkout, do
21950 some magic to guess it if we're in an SVK checkout, or use
21951 the last-detected version if we're building from a .tar.gz.
21952 Use this version consistently in log messages.
21954 o Minor features (logging):
21955 - Always prepend "Bug: " to any log message about a bug.
21956 - Put a platform string (e.g. "Linux i686") in the startup log
21957 message, so when people paste just their logs, we know if it's
21958 OpenBSD or Windows or what.
21959 - When logging memory usage, break down memory used in buffers by
21962 o Minor features (directory system):
21963 - New config option V2AuthoritativeDirectory that all directory
21964 authorities should set. This will let future authorities choose
21965 not to serve V2 directory information.
21966 - Directory authorities allow multiple router descriptors and/or extra
21967 info documents to be uploaded in a single go. This will make
21968 implementing proposal 104 simpler.
21970 o Minor features (controller):
21971 - Add a new config option __DisablePredictedCircuits designed for
21972 use by the controller, when we don't want Tor to build any circuits
21974 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
21975 so we can exit from the middle of the circuit.
21976 - Implement "getinfo status/circuit-established".
21977 - Implement "getinfo status/version/..." so a controller can tell
21978 whether the current version is recommended, and whether any versions
21979 are good, and how many authorities agree. (Patch from shibz.)
21981 o Minor features (hidden services):
21982 - Allow multiple HiddenServicePort directives with the same virtual
21983 port; when they occur, the user is sent round-robin to one
21984 of the target ports chosen at random. Partially fixes bug 393 by
21985 adding limited ad-hoc round-robining.
21987 o Minor features (other):
21989 - Add a new AutomapHostsOnResolve option: when it is enabled, any
21990 resolve request for hosts matching a given pattern causes Tor to
21991 generate an internal virtual address mapping for that host. This
21992 allows DNSPort to work sensibly with hidden service users. By
21993 default, .exit and .onion addresses are remapped; the list of
21994 patterns can be reconfigured with AutomapHostsSuffixes.
21995 - Add an "-F" option to tor-resolve to force a resolve for a .onion
21996 address. Thanks to the AutomapHostsOnResolve option, this is no
21997 longer a completely silly thing to do.
21998 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
21999 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
22000 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
22001 minus 1 byte: the actual maximum declared bandwidth.
22003 o Removed features:
22004 - Removed support for the old binary "version 0" controller protocol.
22005 This has been deprecated since 0.1.1, and warnings have been issued
22006 since 0.1.2. When we encounter a v0 control message, we now send
22007 back an error and close the connection.
22008 - Remove the old "dns worker" server DNS code: it hasn't been default
22009 since 0.1.2.2-alpha, and all the servers seem to be using the new
22012 o Minor bugfixes (portability):
22013 - Even though Windows is equally happy with / and \ as path separators,
22014 try to use \ consistently on Windows and / consistently on Unix: it
22015 makes the log messages nicer.
22016 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
22017 - Read resolv.conf files correctly on platforms where read() returns
22018 partial results on small file reads.
22020 o Minor bugfixes (directory):
22021 - Correctly enforce that elements of directory objects do not appear
22022 more often than they are allowed to appear.
22023 - When we are reporting the DirServer line we just parsed, we were
22024 logging the second stanza of the key fingerprint, not the first.
22026 o Minor bugfixes (logging):
22027 - When we hit an EOF on a log (probably because we're shutting down),
22028 don't try to remove the log from the list: just mark it as
22029 unusable. (Bulletproofs against bug 222.)
22031 o Minor bugfixes (other):
22032 - In the exitlist script, only consider the most recently published
22033 server descriptor for each server. Also, when the user requests
22034 a list of servers that _reject_ connections to a given address,
22035 explicitly exclude the IPs that also have servers that accept
22036 connections to that address. (Resolves bug 405.)
22037 - Stop allowing hibernating servers to be "stable" or "fast".
22038 - On Windows, we were preventing other processes from reading
22039 cached-routers while Tor was running. (Reported by janbar)
22040 - Make the NodeFamilies config option work. (Reported by
22041 lodger -- it has never actually worked, even though we added it
22043 - Check return values from pthread_mutex functions.
22044 - Don't save non-general-purpose router descriptors to the disk cache,
22045 because we have no way of remembering what their purpose was when
22047 - Add even more asserts to hunt down bug 417.
22048 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
22049 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
22050 Add a log message to confirm that it is in fact unlikely.
22052 o Minor bugfixes (controller):
22053 - Make 'getinfo fingerprint' return a 551 error if we're not a
22054 server, so we match what the control spec claims we do. Reported
22056 - Fix a typo in an error message when extendcircuit fails that
22057 caused us to not follow the \r\n-based delimiter protocol. Reported
22060 o Code simplifications and refactoring:
22061 - Stop passing around circuit_t and crypt_path_t pointers that are
22062 implicit in other procedure arguments.
22063 - Drop the old code to choke directory connections when the
22064 corresponding OR connections got full: thanks to the cell queue
22065 feature, OR conns don't get full any more.
22066 - Make dns_resolve() handle attaching connections to circuits
22067 properly, so the caller doesn't have to.
22068 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
22069 - Keep the connection array as a dynamic smartlist_t, rather than as
22070 a fixed-sized array. This is important, as the number of connections
22071 is becoming increasingly decoupled from the number of sockets.
22074 Changes in version 0.1.2.14 - 2007-05-25
22075 Tor 0.1.2.14 changes the addresses of two directory authorities (this
22076 change especially affects those who serve or use hidden services),
22077 and fixes several other crash- and security-related bugs.
22079 o Directory authority changes:
22080 - Two directory authorities (moria1 and moria2) just moved to new
22081 IP addresses. This change will particularly affect those who serve
22082 or use hidden services.
22084 o Major bugfixes (crashes):
22085 - If a directory server runs out of space in the connection table
22086 as it's processing a begin_dir request, it will free the exit stream
22087 but leave it attached to the circuit, leading to unpredictable
22088 behavior. (Reported by seeess, fixes bug 425.)
22089 - Fix a bug in dirserv_remove_invalid() that would cause authorities
22090 to corrupt memory under some really unlikely scenarios.
22091 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
22092 - Avoid segfaults when reading from mmaped descriptor file. (Reported
22095 o Major bugfixes (security):
22096 - When choosing an entry guard for a circuit, avoid using guards
22097 that are in the same family as the chosen exit -- not just guards
22098 that are exactly the chosen exit. (Reported by lodger.)
22100 o Major bugfixes (resource management):
22101 - If a directory authority is down, skip it when deciding where to get
22102 networkstatus objects or descriptors. Otherwise we keep asking
22103 every 10 seconds forever. Fixes bug 384.
22104 - Count it as a failure if we fetch a valid network-status but we
22105 don't want to keep it. Otherwise we'll keep fetching it and keep
22106 not wanting to keep it. Fixes part of bug 422.
22107 - If all of our dirservers have given us bad or no networkstatuses
22108 lately, then stop hammering them once per minute even when we
22109 think they're failed. Fixes another part of bug 422.
22112 - Actually set the purpose correctly for descriptors inserted with
22113 purpose=controller.
22114 - When we have k non-v2 authorities in our DirServer config,
22115 we ignored the last k authorities in the list when updating our
22117 - Correctly back-off from requesting router descriptors that we are
22118 having a hard time downloading.
22119 - Read resolv.conf files correctly on platforms where read() returns
22120 partial results on small file reads.
22121 - Don't rebuild the entire router store every time we get 32K of
22122 routers: rebuild it when the journal gets very large, or when
22123 the gaps in the store get very large.
22126 - When routers publish SVN revisions in their router descriptors,
22127 authorities now include those versions correctly in networkstatus
22129 - Warn when using a version of libevent before 1.3b to run a server on
22130 OSX or BSD: these versions interact badly with userspace threads.
22133 Changes in version 0.1.2.13 - 2007-04-24
22134 This release features some major anonymity fixes, such as safer path
22135 selection; better client performance; faster bootstrapping, better
22136 address detection, and better DNS support for servers; write limiting as
22137 well as read limiting to make servers easier to run; and a huge pile of
22138 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
22140 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
22141 of the Freenode IRC network, remembering his patience and vision for
22142 free speech on the Internet.
22145 - Fix a memory leak when we ask for "all" networkstatuses and we
22146 get one we don't recognize.
22147 - Add more asserts to hunt down bug 417.
22148 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
22151 Changes in version 0.1.2.12-rc - 2007-03-16
22153 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
22154 directory information requested inside Tor connections (i.e. via
22155 begin_dir cells). It only triggered when the same connection was
22156 serving other data at the same time. Reported by seeess.
22159 - When creating a circuit via the controller, send a 'launched'
22160 event when we're done, so we follow the spec better.
22163 Changes in version 0.1.2.11-rc - 2007-03-15
22164 o Minor bugfixes (controller), reported by daejees:
22165 - Correct the control spec to match how the code actually responds
22166 to 'getinfo addr-mappings/*'.
22167 - The control spec described a GUARDS event, but the code
22168 implemented a GUARD event. Standardize on GUARD, but let people
22169 ask for GUARDS too.
22172 Changes in version 0.1.2.10-rc - 2007-03-07
22173 o Major bugfixes (Windows):
22174 - Do not load the NT services library functions (which may not exist)
22175 just to detect if we're a service trying to shut down. Now we run
22176 on Win98 and friends again.
22178 o Minor bugfixes (other):
22179 - Clarify a couple of log messages.
22180 - Fix a misleading socks5 error number.
22183 Changes in version 0.1.2.9-rc - 2007-03-02
22184 o Major bugfixes (Windows):
22185 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
22186 of the usual GCC "%llu". This prevents a bug when saving 64-bit
22187 int configuration values: the high-order 32 bits would get
22188 truncated. In particular, we were being bitten by the default
22189 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
22190 and maybe also bug 397.)
22192 o Minor bugfixes (performance):
22193 - Use OpenSSL's AES implementation on platforms where it's faster.
22194 This could save us as much as 10% CPU usage.
22196 o Minor bugfixes (server):
22197 - Do not rotate onion key immediately after setting it for the first
22200 o Minor bugfixes (directory authorities):
22201 - Stop calling servers that have been hibernating for a long time
22202 "stable". Also, stop letting hibernating or obsolete servers affect
22203 uptime and bandwidth cutoffs.
22204 - Stop listing hibernating servers in the v1 directory.
22206 o Minor bugfixes (hidden services):
22207 - Upload hidden service descriptors slightly less often, to reduce
22208 load on authorities.
22210 o Minor bugfixes (other):
22211 - Fix an assert that could trigger if a controller quickly set then
22212 cleared EntryNodes. Bug found by Udo van den Heuvel.
22213 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
22215 - Fix a potential race condition in the rpm installer. Found by
22217 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
22218 of 2 as indicating that the server is completely bad; it sometimes
22219 means that the server is just bad for the request in question. (may fix
22220 the last of bug 326.)
22221 - Disable encrypted directory connections when we don't have a server
22222 descriptor for the destination. We'll get this working again in
22226 Changes in version 0.1.2.8-beta - 2007-02-26
22227 o Major bugfixes (crashes):
22228 - Stop crashing when the controller asks us to resetconf more than
22229 one config option at once. (Vidalia 0.0.11 does this.)
22230 - Fix a crash that happened on Win98 when we're given command-line
22231 arguments: don't try to load NT service functions from advapi32.dll
22232 except when we need them. (Bug introduced in 0.1.2.7-alpha;
22234 - Fix a longstanding obscure crash bug that could occur when
22235 we run out of DNS worker processes. (Resolves bug 390.)
22237 o Major bugfixes (hidden services):
22238 - Correctly detect whether hidden service descriptor downloads are
22239 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
22241 o Major bugfixes (accounting):
22242 - When we start during an accounting interval before it's time to wake
22243 up, remember to wake up at the correct time. (May fix bug 342.)
22245 o Minor bugfixes (controller):
22246 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
22247 clear the corresponding on_circuit variable, and remember later
22248 that we don't need to send a redundant CLOSED event. Resolves part
22250 - Report events where a resolve succeeded or where we got a socks
22251 protocol error correctly, rather than calling both of them
22253 - Change reported stream target addresses to IP consistently when
22254 we finally get the IP from an exit node.
22255 - Send log messages to the controller even if they happen to be very
22258 o Minor bugfixes (other):
22259 - Display correct results when reporting which versions are
22260 recommended, and how recommended they are. (Resolves bug 383.)
22261 - Improve our estimates for directory bandwidth to be less random:
22262 guess that an unrecognized directory will have the average bandwidth
22263 from all known directories, not that it will have the average
22264 bandwidth from those directories earlier than it on the list.
22265 - If we start a server with ClientOnly 1, then set ClientOnly to 0
22266 and hup, stop triggering an assert based on an empty onion_key.
22267 - On platforms with no working mmap() equivalent, don't warn the
22268 user when cached-routers doesn't exist.
22269 - Warn the user when mmap() [or its equivalent] fails for some reason
22270 other than file-not-found.
22271 - Don't warn the user when cached-routers.new doesn't exist: that's
22272 perfectly fine when starting up for the first time.
22273 - When EntryNodes are configured, rebuild the guard list to contain,
22274 in order: the EntryNodes that were guards before; the rest of the
22275 EntryNodes; the nodes that were guards before.
22276 - Mask out all signals in sub-threads; only the libevent signal
22277 handler should be processing them. This should prevent some crashes
22278 on some machines using pthreads. (Patch from coderman.)
22279 - Fix switched arguments on memset in the implementation of
22280 tor_munmap() for systems with no mmap() call.
22281 - When Tor receives a router descriptor that it asked for, but
22282 no longer wants (because it has received fresh networkstatuses
22283 in the meantime), do not warn the user. Cache the descriptor if
22284 we're a cache; drop it if we aren't.
22285 - Make earlier entry guards _really_ get retried when the network
22287 - On a malformed DNS reply, always give an error to the corresponding
22289 - Build with recent libevents on platforms that do not define the
22290 nonstandard types "u_int8_t" and friends.
22292 o Minor features (controller):
22293 - Warn the user when an application uses the obsolete binary v0
22294 control protocol. We're planning to remove support for it during
22295 the next development series, so it's good to give people some
22297 - Add STREAM_BW events to report per-entry-stream bandwidth
22298 use. (Patch from Robert Hogan.)
22299 - Rate-limit SIGNEWNYM signals in response to controllers that
22300 impolitely generate them for every single stream. (Patch from
22301 mwenge; closes bug 394.)
22302 - Make REMAP stream events have a SOURCE (cache or exit), and
22303 make them generated in every case where we get a successful
22304 connected or resolved cell.
22306 o Minor bugfixes (performance):
22307 - Call router_have_min_dir_info half as often. (This is showing up in
22308 some profiles, but not others.)
22309 - When using GCC, make log_debug never get called at all, and its
22310 arguments never get evaluated, when no debug logs are configured.
22311 (This is showing up in some profiles, but not others.)
22314 - Remove some never-implemented options. Mark PathlenCoinWeight as
22316 - Implement proposal 106: Stop requiring clients to have well-formed
22317 certificates; stop checking nicknames in certificates. (Clients
22318 have certificates so that they can look like Tor servers, but in
22319 the future we might want to allow them to look like regular TLS
22320 clients instead. Nicknames in certificates serve no purpose other
22321 than making our protocol easier to recognize on the wire.)
22322 - Revise messages on handshake failure again to be even more clear about
22323 which are incoming connections and which are outgoing.
22324 - Discard any v1 directory info that's over 1 month old (for
22325 directories) or over 1 week old (for running-routers lists).
22326 - Do not warn when individual nodes in the configuration's EntryNodes,
22327 ExitNodes, etc are down: warn only when all possible nodes
22328 are down. (Fixes bug 348.)
22329 - Always remove expired routers and networkstatus docs before checking
22330 whether we have enough information to build circuits. (Fixes
22332 - Put a lower-bound on MaxAdvertisedBandwidth.
22335 Changes in version 0.1.2.7-alpha - 2007-02-06
22336 o Major bugfixes (rate limiting):
22337 - Servers decline directory requests much more aggressively when
22338 they're low on bandwidth. Otherwise they end up queueing more and
22339 more directory responses, which can't be good for latency.
22340 - But never refuse directory requests from local addresses.
22341 - Fix a memory leak when sending a 503 response for a networkstatus
22343 - Be willing to read or write on local connections (e.g. controller
22344 connections) even when the global rate limiting buckets are empty.
22345 - If our system clock jumps back in time, don't publish a negative
22346 uptime in the descriptor. Also, don't let the global rate limiting
22347 buckets go absurdly negative.
22348 - Flush local controller connection buffers periodically as we're
22349 writing to them, so we avoid queueing 4+ megabytes of data before
22352 o Major bugfixes (NT services):
22353 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
22354 command-line flag so that admins can override the default by saying
22355 "tor --service install --user "SomeUser"". This will not affect
22356 existing installed services. Also, warn the user that the service
22357 will look for its configuration file in the service user's
22358 %appdata% directory. (We can't do the 'hardwire the user's appdata
22359 directory' trick any more, since we may not have read access to that
22362 o Major bugfixes (other):
22363 - Previously, we would cache up to 16 old networkstatus documents
22364 indefinitely, if they came from nontrusted authorities. Now we
22365 discard them if they are more than 10 days old.
22366 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
22368 - Detect and reject malformed DNS responses containing circular
22370 - If exits are rare enough that we're not marking exits as guards,
22371 ignore exit bandwidth when we're deciding the required bandwidth
22373 - When we're handling a directory connection tunneled over Tor,
22374 don't fill up internal memory buffers with all the data we want
22375 to tunnel; instead, only add it if the OR connection that will
22376 eventually receive it has some room for it. (This can lead to
22377 slowdowns in tunneled dir connections; a better solution will have
22378 to wait for 0.2.0.)
22380 o Minor bugfixes (dns):
22381 - Add some defensive programming to eventdns.c in an attempt to catch
22382 possible memory-stomping bugs.
22383 - Detect and reject DNS replies containing IPv4 or IPv6 records with
22384 an incorrect number of bytes. (Previously, we would ignore the
22386 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
22387 in the correct order, and doesn't crash.
22388 - Free memory held in recently-completed DNS lookup attempts on exit.
22389 This was not a memory leak, but may have been hiding memory leaks.
22390 - Handle TTL values correctly on reverse DNS lookups.
22391 - Treat failure to parse resolv.conf as an error.
22393 o Minor bugfixes (other):
22394 - Fix crash with "tor --list-fingerprint" (reported by seeess).
22395 - When computing clock skew from directory HTTP headers, consider what
22396 time it was when we finished asking for the directory, not what
22398 - Expire socks connections if they spend too long waiting for the
22399 handshake to finish. Previously we would let them sit around for
22400 days, if the connecting application didn't close them either.
22401 - And if the socks handshake hasn't started, don't send a
22402 "DNS resolve socks failed" handshake reply; just close it.
22403 - Stop using C functions that OpenBSD's linker doesn't like.
22404 - Don't launch requests for descriptors unless we have networkstatuses
22405 from at least half of the authorities. This delays the first
22406 download slightly under pathological circumstances, but can prevent
22407 us from downloading a bunch of descriptors we don't need.
22408 - Do not log IPs with TLS failures for incoming TLS
22409 connections. (Fixes bug 382.)
22410 - If the user asks to use invalid exit nodes, be willing to use
22412 - Stop using the reserved ac_cv namespace in our configure script.
22413 - Call stat() slightly less often; use fstat() when possible.
22414 - Refactor the way we handle pending circuits when an OR connection
22415 completes or fails, in an attempt to fix a rare crash bug.
22416 - Only rewrite a conn's address based on X-Forwarded-For: headers
22417 if it's a parseable public IP address; and stop adding extra quotes
22418 to the resulting address.
22421 - Weight directory requests by advertised bandwidth. Now we can
22422 let servers enable write limiting but still allow most clients to
22423 succeed at their directory requests. (We still ignore weights when
22424 choosing a directory authority; I hope this is a feature.)
22427 - Create a new file ReleaseNotes which was the old ChangeLog. The
22428 new ChangeLog file now includes the summaries for all development
22430 - Check for addresses with invalid characters at the exit as well
22431 as at the client, and warn less verbosely when they fail. You can
22432 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
22433 - Adapt a patch from goodell to let the contrib/exitlist script
22434 take arguments rather than require direct editing.
22435 - Inform the server operator when we decide not to advertise a
22436 DirPort due to AccountingMax enabled or a low BandwidthRate. It
22437 was confusing Zax, so now we're hopefully more helpful.
22438 - Bring us one step closer to being able to establish an encrypted
22439 directory tunnel without knowing a descriptor first. Still not
22440 ready yet. As part of the change, now assume we can use a
22441 create_fast cell if we don't know anything about a router.
22442 - Allow exit nodes to use nameservers running on ports other than 53.
22443 - Servers now cache reverse DNS replies.
22444 - Add an --ignore-missing-torrc command-line option so that we can
22445 get the "use sensible defaults if the configuration file doesn't
22446 exist" behavior even when specifying a torrc location on the command
22449 o Minor features (controller):
22450 - Track reasons for OR connection failure; make these reasons
22451 available via the controller interface. (Patch from Mike Perry.)
22452 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
22453 can learn when clients are sending malformed hostnames to Tor.
22454 - Clean up documentation for controller status events.
22455 - Add a REMAP status to stream events to note that a stream's
22456 address has changed because of a cached address or a MapAddress
22460 Changes in version 0.1.2.6-alpha - 2007-01-09
22462 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
22463 connection handles more than 4 gigs in either direction, we crash.
22464 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
22465 advertised exit node, somebody might try to exit from us when
22466 we're bootstrapping and before we've built our descriptor yet.
22467 Refuse the connection rather than crashing.
22470 - Warn if we (as a server) find that we've resolved an address that we
22471 weren't planning to resolve.
22472 - Warn that using select() on any libevent version before 1.1 will be
22473 unnecessarily slow (even for select()).
22474 - Flush ERR-level controller status events just like we currently
22475 flush ERR-level log events, so that a Tor shutdown doesn't prevent
22476 the controller from learning about current events.
22478 o Minor features (more controller status events):
22479 - Implement EXTERNAL_ADDRESS server status event so controllers can
22480 learn when our address changes.
22481 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
22482 can learn when directories reject our descriptor.
22483 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
22484 can learn when a client application is speaking a non-socks protocol
22486 - Implement DANGEROUS_SOCKS client status event so controllers
22487 can learn when a client application is leaking DNS addresses.
22488 - Implement BUG general status event so controllers can learn when
22489 Tor is unhappy about its internal invariants.
22490 - Implement CLOCK_SKEW general status event so controllers can learn
22491 when Tor thinks the system clock is set incorrectly.
22492 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
22493 server status events so controllers can learn when their descriptors
22494 are accepted by a directory.
22495 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
22496 server status events so controllers can learn about Tor's progress in
22497 deciding whether it's reachable from the outside.
22498 - Implement BAD_LIBEVENT general status event so controllers can learn
22499 when we have a version/method combination in libevent that needs to
22501 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
22502 and DNS_USELESS server status events so controllers can learn
22503 about changes to DNS server status.
22505 o Minor features (directory):
22506 - Authorities no longer recommend exits as guards if this would shift
22507 too much load to the exit nodes.
22510 Changes in version 0.1.2.5-alpha - 2007-01-06
22512 - Enable write limiting as well as read limiting. Now we sacrifice
22513 capacity if we're pushing out lots of directory traffic, rather
22514 than overrunning the user's intended bandwidth limits.
22515 - Include TLS overhead when counting bandwidth usage; previously, we
22516 would count only the bytes sent over TLS, but not the bytes used
22518 - Support running the Tor service with a torrc not in the same
22519 directory as tor.exe and default to using the torrc located in
22520 the %appdata%\Tor\ of the user who installed the service. Patch
22522 - Servers now check for the case when common DNS requests are going to
22523 wildcarded addresses (i.e. all getting the same answer), and change
22524 their exit policy to reject *:* if it's happening.
22525 - Implement BEGIN_DIR cells, so we can connect to the directory
22526 server via TLS to do encrypted directory requests rather than
22527 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
22528 config options if you like.
22530 o Minor features (config and docs):
22531 - Start using the state file to store bandwidth accounting data:
22532 the bw_accounting file is now obsolete. We'll keep generating it
22533 for a while for people who are still using 0.1.2.4-alpha.
22534 - Try to batch changes to the state file so that we do as few
22535 disk writes as possible while still storing important things in
22537 - The state file and the bw_accounting file get saved less often when
22538 the AvoidDiskWrites config option is set.
22539 - Make PIDFile work on Windows (untested).
22540 - Add internal descriptions for a bunch of configuration options:
22541 accessible via controller interface and in comments in saved
22543 - Reject *:563 (NNTPS) in the default exit policy. We already reject
22544 NNTP by default, so this seems like a sensible addition.
22545 - Clients now reject hostnames with invalid characters. This should
22546 avoid some inadvertent info leaks. Add an option
22547 AllowNonRFC953Hostnames to disable this behavior, in case somebody
22548 is running a private network with hosts called @, !, and #.
22549 - Add a maintainer script to tell us which options are missing
22550 documentation: "make check-docs".
22551 - Add a new address-spec.txt document to describe our special-case
22552 addresses: .exit, .onion, and .noconnnect.
22554 o Minor features (DNS):
22555 - Ongoing work on eventdns infrastructure: now it has dns server
22556 and ipv6 support. One day Tor will make use of it.
22557 - Add client-side caching for reverse DNS lookups.
22558 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
22559 - When we change nameservers or IP addresses, reset and re-launch
22560 our tests for DNS hijacking.
22562 o Minor features (directory):
22563 - Authorities now specify server versions in networkstatus. This adds
22564 about 2% to the size of compressed networkstatus docs, and allows
22565 clients to tell which servers support BEGIN_DIR and which don't.
22566 The implementation is forward-compatible with a proposed future
22567 protocol version scheme not tied to Tor versions.
22568 - DirServer configuration lines now have an orport= option so
22569 clients can open encrypted tunnels to the authorities without
22570 having downloaded their descriptors yet. Enabled for moria1,
22571 moria2, tor26, and lefkada now in the default configuration.
22572 - Directory servers are more willing to send a 503 "busy" if they
22573 are near their write limit, especially for v1 directory requests.
22574 Now they can use their limited bandwidth for actual Tor traffic.
22575 - Clients track responses with status 503 from dirservers. After a
22576 dirserver has given us a 503, we try not to use it until an hour has
22577 gone by, or until we have no dirservers that haven't given us a 503.
22578 - When we get a 503 from a directory, and we're not a server, we don't
22579 count the failure against the total number of failures allowed
22580 for the thing we're trying to download.
22581 - Report X-Your-Address-Is correctly from tunneled directory
22582 connections; don't report X-Your-Address-Is when it's an internal
22583 address; and never believe reported remote addresses when they're
22585 - Protect against an unlikely DoS attack on directory servers.
22586 - Add a BadDirectory flag to network status docs so that authorities
22587 can (eventually) tell clients about caches they believe to be
22590 o Minor features (controller):
22591 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
22592 - Reimplement GETINFO so that info/names stays in sync with the
22594 - Implement "GETINFO fingerprint".
22595 - Implement "SETEVENTS GUARD" so controllers can get updates on
22596 entry guard status as it changes.
22598 o Minor features (clean up obsolete pieces):
22599 - Remove some options that have been deprecated since at least
22600 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
22601 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
22602 to set log options.
22603 - We no longer look for identity and onion keys in "identity.key" and
22604 "onion.key" -- these were replaced by secret_id_key and
22605 secret_onion_key in 0.0.8pre1.
22606 - We no longer require unrecognized directory entries to be
22609 o Major bugfixes (security):
22610 - Stop sending the HttpProxyAuthenticator string to directory
22611 servers when directory connections are tunnelled through Tor.
22612 - Clients no longer store bandwidth history in the state file.
22613 - Do not log introduction points for hidden services if SafeLogging
22615 - When generating bandwidth history, round down to the nearest
22616 1k. When storing accounting data, round up to the nearest 1k.
22617 - When we're running as a server, remember when we last rotated onion
22618 keys, so that we will rotate keys once they're a week old even if
22619 we never stay up for a week ourselves.
22621 o Major bugfixes (other):
22622 - Fix a longstanding bug in eventdns that prevented the count of
22623 timed-out resolves from ever being reset. This bug caused us to
22624 give up on a nameserver the third time it timed out, and try it
22625 10 seconds later... and to give up on it every time it timed out
22627 - Take out the '5 second' timeout from the connection retry
22628 schedule. Now the first connect attempt will wait a full 10
22629 seconds before switching to a new circuit. Perhaps this will help
22630 a lot. Based on observations from Mike Perry.
22631 - Fix a bug on the Windows implementation of tor_mmap_file() that
22632 would prevent the cached-routers file from ever loading. Reported
22636 - Fix an assert failure when a directory authority sets
22637 AuthDirRejectUnlisted and then receives a descriptor from an
22638 unlisted router. Reported by seeess.
22639 - Avoid a double-free when parsing malformed DirServer lines.
22640 - Fix a bug when a BSD-style PF socket is first used. Patch from
22642 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
22643 to resolve an address at a given exit node even when they ask for
22645 - Servers no longer ever list themselves in their "family" line,
22646 even if configured to do so. This makes it easier to configure
22647 family lists conveniently.
22648 - When running as a server, don't fall back to 127.0.0.1 when no
22649 nameservers are configured in /etc/resolv.conf; instead, make the
22650 user fix resolv.conf or specify nameservers explicitly. (Resolves
22652 - Stop accepting certain malformed ports in configured exit policies.
22653 - Don't re-write the fingerprint file every restart, unless it has
22655 - Stop warning when a single nameserver fails: only warn when _all_ of
22656 our nameservers have failed. Also, when we only have one nameserver,
22657 raise the threshold for deciding that the nameserver is dead.
22658 - Directory authorities now only decide that routers are reachable
22659 if their identity keys are as expected.
22660 - When the user uses bad syntax in the Log config line, stop
22661 suggesting other bad syntax as a replacement.
22662 - Correctly detect ipv6 DNS capability on OpenBSD.
22664 o Minor bugfixes (controller):
22665 - Report the circuit number correctly in STREAM CLOSED events. Bug
22666 reported by Mike Perry.
22667 - Do not report bizarre values for results of accounting GETINFOs
22668 when the last second's write or read exceeds the allotted bandwidth.
22669 - Report "unrecognized key" rather than an empty string when the
22670 controller tries to fetch a networkstatus that doesn't exist.
22673 Changes in version 0.1.1.26 - 2006-12-14
22674 o Security bugfixes:
22675 - Stop sending the HttpProxyAuthenticator string to directory
22676 servers when directory connections are tunnelled through Tor.
22677 - Clients no longer store bandwidth history in the state file.
22678 - Do not log introduction points for hidden services if SafeLogging
22682 - Fix an assert failure when a directory authority sets
22683 AuthDirRejectUnlisted and then receives a descriptor from an
22684 unlisted router (reported by seeess).
22687 Changes in version 0.1.2.4-alpha - 2006-12-03
22689 - Add support for using natd; this allows FreeBSDs earlier than
22690 5.1.2 to have ipfw send connections through Tor without using
22691 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
22694 - Make all connections to addresses of the form ".noconnect"
22695 immediately get closed. This lets application/controller combos
22696 successfully test whether they're talking to the same Tor by
22697 watching for STREAM events.
22698 - Make cross.sh cross-compilation script work even when autogen.sh
22699 hasn't been run. (Patch from Michael Mohr.)
22700 - Statistics dumped by -USR2 now include a breakdown of public key
22701 operations, for profiling.
22704 - Fix a major leak when directory authorities parse their
22705 approved-routers list, a minor memory leak when we fail to pick
22706 an exit node, and a few rare leaks on errors.
22707 - Handle TransPort connections even when the server sends data before
22708 the client sends data. Previously, the connection would just hang
22709 until the client sent data. (Patch from tup based on patch from
22711 - Avoid assert failure when our cached-routers file is empty on
22715 - Don't log spurious warnings when we see a circuit close reason we
22716 don't recognize; it's probably just from a newer version of Tor.
22717 - Have directory authorities allow larger amounts of drift in uptime
22718 without replacing the server descriptor: previously, a server that
22719 restarted every 30 minutes could have 48 "interesting" descriptors
22721 - Start linking to the Tor specification and Tor reference manual
22722 correctly in the Windows installer.
22723 - Add Vidalia to the OS X uninstaller script, so when we uninstall
22724 Tor/Privoxy we also uninstall Vidalia.
22725 - Resume building on Irix64, and fix a lot of warnings from its
22726 MIPSpro C compiler.
22727 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
22728 when we're running as a client.
22731 Changes in version 0.1.1.25 - 2006-11-04
22733 - When a client asks us to resolve (rather than connect to)
22734 an address, and we have a cached answer, give them the cached
22735 answer. Previously, we would give them no answer at all.
22736 - We were building exactly the wrong circuits when we predict
22737 hidden service requirements, meaning Tor would have to build all
22738 its circuits on demand.
22739 - If none of our live entry guards have a high uptime, but we
22740 require a guard with a high uptime, try adding a new guard before
22741 we give up on the requirement. This patch should make long-lived
22742 connections more stable on average.
22743 - When testing reachability of our DirPort, don't launch new
22744 tests when there's already one in progress -- unreachable
22745 servers were stacking up dozens of testing streams.
22747 o Security bugfixes:
22748 - When the user sends a NEWNYM signal, clear the client-side DNS
22749 cache too. Otherwise we continue to act on previous information.
22752 - Avoid a memory corruption bug when creating a hash table for
22754 - Avoid possibility of controller-triggered crash when misusing
22755 certain commands from a v0 controller on platforms that do not
22756 handle printf("%s",NULL) gracefully.
22757 - Avoid infinite loop on unexpected controller input.
22758 - Don't log spurious warnings when we see a circuit close reason we
22759 don't recognize; it's probably just from a newer version of Tor.
22760 - Add Vidalia to the OS X uninstaller script, so when we uninstall
22761 Tor/Privoxy we also uninstall Vidalia.
22764 Changes in version 0.1.2.3-alpha - 2006-10-29
22766 - Prepare for servers to publish descriptors less often: never
22767 discard a descriptor simply for being too old until either it is
22768 recommended by no authorities, or until we get a better one for
22769 the same router. Make caches consider retaining old recommended
22770 routers for even longer.
22771 - If most authorities set a BadExit flag for a server, clients
22772 don't think of it as a general-purpose exit. Clients only consider
22773 authorities that advertise themselves as listing bad exits.
22774 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
22775 headers for content, so that we can work better in the presence of
22776 caching HTTP proxies.
22777 - Allow authorities to list nodes as bad exits by fingerprint or by
22780 o Minor features, controller:
22781 - Add a REASON field to CIRC events; for backward compatibility, this
22782 field is sent only to controllers that have enabled the extended
22783 event format. Also, add additional reason codes to explain why
22784 a given circuit has been destroyed or truncated. (Patches from
22786 - Add a REMOTE_REASON field to extended CIRC events to tell the
22787 controller about why a remote OR told us to close a circuit.
22788 - Stream events also now have REASON and REMOTE_REASON fields,
22789 working much like those for circuit events.
22790 - There's now a GETINFO ns/... field so that controllers can ask Tor
22791 about the current status of a router.
22792 - A new event type "NS" to inform a controller when our opinion of
22793 a router's status has changed.
22794 - Add a GETINFO events/names and GETINFO features/names so controllers
22795 can tell which events and features are supported.
22796 - A new CLEARDNSCACHE signal to allow controllers to clear the
22797 client-side DNS cache without expiring circuits.
22799 o Security bugfixes:
22800 - When the user sends a NEWNYM signal, clear the client-side DNS
22801 cache too. Otherwise we continue to act on previous information.
22804 - Avoid sending junk to controllers or segfaulting when a controller
22805 uses EVENT_NEW_DESC with verbose nicknames.
22806 - Stop triggering asserts if the controller tries to extend hidden
22807 service circuits (reported by mwenge).
22808 - Avoid infinite loop on unexpected controller input.
22809 - When the controller does a "GETINFO network-status", tell it
22810 about even those routers whose descriptors are very old, and use
22811 long nicknames where appropriate.
22812 - Change NT service functions to be loaded on demand. This lets us
22813 build with MinGW without breaking Tor for Windows 98 users.
22814 - Do DirPort reachability tests less often, since a single test
22815 chews through many circuits before giving up.
22816 - In the hidden service example in torrc.sample, stop recommending
22817 esoteric and discouraged hidden service options.
22818 - When stopping an NT service, wait up to 10 sec for it to actually
22819 stop. Patch from Matt Edman; resolves bug 295.
22820 - Fix handling of verbose nicknames with ORCONN controller events:
22821 make them show up exactly when requested, rather than exactly when
22823 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
22824 printing a duplicate "$" in the keys we send (reported by mwenge).
22825 - Correctly set maximum connection limit on Cygwin. (This time
22827 - Try to detect Windows correctly when cross-compiling.
22828 - Detect the size of the routers file correctly even if it is
22829 corrupted (on systems without mmap) or not page-aligned (on systems
22830 with mmap). This bug was harmless.
22831 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
22832 to open a stream fails; now we do in more cases. This should
22833 make clients able to find a good exit faster in some cases, since
22834 unhandleable requests will now get an error rather than timing out.
22835 - Resolve two memory leaks when rebuilding the on-disk router cache
22836 (reported by fookoowa).
22837 - Clean up minor code warnings suggested by the MIPSpro C compiler,
22838 and reported by some Centos users.
22839 - Controller signals now work on non-Unix platforms that don't define
22840 SIGUSR1 and SIGUSR2 the way we expect.
22841 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
22842 values before failing, and always enables eventdns.
22843 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
22844 Try to fix this in configure.in by checking for most functions
22845 before we check for libevent.
22848 Changes in version 0.1.2.2-alpha - 2006-10-07
22850 - Make our async eventdns library on-by-default for Tor servers,
22851 and plan to deprecate the separate dnsworker threads.
22852 - Add server-side support for "reverse" DNS lookups (using PTR
22853 records so clients can determine the canonical hostname for a given
22854 IPv4 address). Only supported by servers using eventdns; servers
22855 now announce in their descriptors whether they support eventdns.
22856 - Specify and implement client-side SOCKS5 interface for reverse DNS
22857 lookups (see doc/socks-extensions.txt).
22858 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
22859 connect to directory servers through Tor. Previously, clients needed
22860 to find Tor exits to make private connections to directory servers.
22861 - Avoid choosing Exit nodes for entry or middle hops when the
22862 total bandwidth available from non-Exit nodes is much higher than
22863 the total bandwidth available from Exit nodes.
22864 - Workaround for name servers (like Earthlink's) that hijack failing
22865 DNS requests and replace the no-such-server answer with a "helpful"
22866 redirect to an advertising-driven search portal. Also work around
22867 DNS hijackers who "helpfully" decline to hijack known-invalid
22868 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
22869 lets you turn it off.
22870 - Send out a burst of long-range padding cells once we've established
22871 that we're reachable. Spread them over 4 circuits, so hopefully
22872 a few will be fast. This exercises our bandwidth and bootstraps
22873 us into the directory more quickly.
22875 o New/improved config options:
22876 - Add new config option "ResolvConf" to let the server operator
22877 choose an alternate resolve.conf file when using eventdns.
22878 - Add an "EnforceDistinctSubnets" option to control our "exclude
22879 servers on the same /16" behavior. It's still on by default; this
22880 is mostly for people who want to operate private test networks with
22881 all the machines on the same subnet.
22882 - If one of our entry guards is on the ExcludeNodes list, or the
22883 directory authorities don't think it's a good guard, treat it as
22884 if it were unlisted: stop using it as a guard, and throw it off
22885 the guards list if it stays that way for a long time.
22886 - Allow directory authorities to be marked separately as authorities
22887 for the v1 directory protocol, the v2 directory protocol, and
22888 as hidden service directories, to make it easier to retire old
22889 authorities. V1 authorities should set "HSAuthoritativeDir 1"
22890 to continue being hidden service authorities too.
22891 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
22893 o Minor features, controller:
22894 - Fix CIRC controller events so that controllers can learn the
22895 identity digests of non-Named servers used in circuit paths.
22896 - Let controllers ask for more useful identifiers for servers. Instead
22897 of learning identity digests for un-Named servers and nicknames
22898 for Named servers, the new identifiers include digest, nickname,
22899 and indication of Named status. Off by default; see control-spec.txt
22900 for more information.
22901 - Add a "getinfo address" controller command so it can display Tor's
22902 best guess to the user.
22903 - New controller event to alert the controller when our server
22904 descriptor has changed.
22905 - Give more meaningful errors on controller authentication failure.
22907 o Minor features, other:
22908 - When asked to resolve a hostname, don't use non-exit servers unless
22909 requested to do so. This allows servers with broken DNS to be
22910 useful to the network.
22911 - Divide eventdns log messages into warn and info messages.
22912 - Reserve the nickname "Unnamed" for routers that can't pick
22913 a hostname: any router can call itself Unnamed; directory
22914 authorities will never allocate Unnamed to any particular router;
22915 clients won't believe that any router is the canonical Unnamed.
22916 - Only include function names in log messages for info/debug messages.
22917 For notice/warn/err, the content of the message should be clear on
22918 its own, and printing the function name only confuses users.
22919 - Avoid some false positives during reachability testing: don't try
22920 to test via a server that's on the same /24 as us.
22921 - If we fail to build a circuit to an intended enclave, and it's
22922 not mandatory that we use that enclave, stop wanting it.
22923 - When eventdns is enabled, allow multithreaded builds on NetBSD and
22924 OpenBSD. (We had previously disabled threads on these platforms
22925 because they didn't have working thread-safe resolver functions.)
22927 o Major bugfixes, anonymity/security:
22928 - If a client asked for a server by name, and there's a named server
22929 in our network-status but we don't have its descriptor yet, we
22930 could return an unnamed server instead.
22931 - Fix NetBSD bug that could allow someone to force uninitialized RAM
22932 to be sent to a server's DNS resolver. This only affects NetBSD
22933 and other platforms that do not bounds-check tolower().
22934 - Reject (most) attempts to use Tor circuits with length one. (If
22935 many people start using Tor as a one-hop proxy, exit nodes become
22936 a more attractive target for compromise.)
22937 - Just because your DirPort is open doesn't mean people should be
22938 able to remotely teach you about hidden service descriptors. Now
22939 only accept rendezvous posts if you've got HSAuthoritativeDir set.
22941 o Major bugfixes, other:
22942 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
22943 - When a client asks the server to resolve (not connect to)
22944 an address, and it has a cached answer, give them the cached answer.
22945 Previously, the server would give them no answer at all.
22946 - Allow really slow clients to not hang up five minutes into their
22947 directory downloads (suggested by Adam J. Richter).
22948 - We were building exactly the wrong circuits when we anticipated
22949 hidden service requirements, meaning Tor would have to build all
22950 its circuits on demand.
22951 - Avoid crashing when we mmap a router cache file of size 0.
22952 - When testing reachability of our DirPort, don't launch new
22953 tests when there's already one in progress -- unreachable
22954 servers were stacking up dozens of testing streams.
22956 o Minor bugfixes, correctness:
22957 - If we're a directory mirror and we ask for "all" network status
22958 documents, we would discard status documents from authorities
22959 we don't recognize.
22960 - Avoid a memory corruption bug when creating a hash table for
22962 - Avoid controller-triggered crash when misusing certain commands
22963 from a v0 controller on platforms that do not handle
22964 printf("%s",NULL) gracefully.
22965 - Don't crash when a controller sends a third argument to an
22966 "extendcircuit" request.
22967 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
22968 response; fix error code when "getinfo dir/status/" fails.
22969 - Avoid crash when telling controller stream-status and a stream
22971 - Patch from Adam Langley to fix assert() in eventdns.c.
22972 - Fix a debug log message in eventdns to say "X resolved to Y"
22973 instead of "X resolved to X".
22974 - Make eventdns give strings for DNS errors, not just error numbers.
22975 - Track unreachable entry guards correctly: don't conflate
22976 'unreachable by us right now' with 'listed as down by the directory
22977 authorities'. With the old code, if a guard was unreachable by
22978 us but listed as running, it would clog our guard list forever.
22979 - Behave correctly in case we ever have a network with more than
22980 2GB/s total advertised capacity.
22981 - Make TrackExitHosts case-insensitive, and fix the behavior of
22982 ".suffix" TrackExitHosts items to avoid matching in the middle of
22984 - Finally fix the openssl warnings from newer gccs that believe that
22985 ignoring a return value is okay, but casting a return value and
22986 then ignoring it is a sign of madness.
22987 - Prevent the contrib/exitlist script from printing the same
22988 result more than once.
22989 - Patch from Steve Hildrey: Generate network status correctly on
22990 non-versioning dirservers.
22991 - Don't listen to the X-Your-Address-Is hint if you did the lookup
22992 via Tor; otherwise you'll think you're the exit node's IP address.
22994 o Minor bugfixes, performance:
22995 - Two small performance improvements on parsing descriptors.
22996 - Major performance improvement on inserting descriptors: change
22997 algorithm from O(n^2) to O(n).
22998 - Make the common memory allocation path faster on machines where
22999 malloc(0) returns a pointer.
23000 - Start remembering X-Your-Address-Is directory hints even if you're
23001 a client, so you can become a server more smoothly.
23002 - Avoid duplicate entries on MyFamily line in server descriptor.
23004 o Packaging, features:
23005 - Remove architecture from OS X builds. The official builds are
23006 now universal binaries.
23007 - The Debian package now uses --verify-config when (re)starting,
23008 to distinguish configuration errors from other errors.
23009 - Update RPMs to require libevent 1.1b.
23011 o Packaging, bugfixes:
23012 - Patches so Tor builds with MinGW on Windows.
23013 - Patches so Tor might run on Cygwin again.
23014 - Resume building on non-gcc compilers and ancient gcc. Resume
23015 building with the -O0 compile flag. Resume building cleanly on
23017 - Run correctly on OS X platforms with case-sensitive filesystems.
23018 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
23019 - Add autoconf checks so Tor can build on Solaris x86 again.
23022 - Documented (and renamed) ServerDNSSearchDomains and
23023 ServerDNSResolvConfFile options.
23024 - Be clearer that the *ListenAddress directives can be repeated
23028 Changes in version 0.1.1.24 - 2006-09-29
23030 - Allow really slow clients to not hang up five minutes into their
23031 directory downloads (suggested by Adam J. Richter).
23032 - Fix major performance regression from 0.1.0.x: instead of checking
23033 whether we have enough directory information every time we want to
23034 do something, only check when the directory information has changed.
23035 This should improve client CPU usage by 25-50%.
23036 - Don't crash if, after a server has been running for a while,
23037 it can't resolve its hostname.
23040 - Allow Tor to start when RunAsDaemon is set but no logs are set.
23041 - Don't crash when the controller receives a third argument to an
23042 "extendcircuit" request.
23043 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
23044 response; fix error code when "getinfo dir/status/" fails.
23045 - Fix configure.in to not produce broken configure files with
23046 more recent versions of autoconf. Thanks to Clint for his auto*
23048 - Fix security bug on NetBSD that could allow someone to force
23049 uninitialized RAM to be sent to a server's DNS resolver. This
23050 only affects NetBSD and other platforms that do not bounds-check
23052 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
23053 methods: these are known to be buggy.
23054 - If we're a directory mirror and we ask for "all" network status
23055 documents, we would discard status documents from authorities
23056 we don't recognize.
23059 Changes in version 0.1.2.1-alpha - 2006-08-27
23061 - Add "eventdns" async dns library from Adam Langley, tweaked to
23062 build on OSX and Windows. Only enabled if you pass the
23063 --enable-eventdns argument to configure.
23064 - Allow servers with no hostname or IP address to learn their
23065 IP address by asking the directory authorities. This code only
23066 kicks in when you would normally have exited with a "no address"
23067 error. Nothing's authenticated, so use with care.
23068 - Rather than waiting a fixed amount of time between retrying
23069 application connections, we wait only 5 seconds for the first,
23070 10 seconds for the second, and 15 seconds for each retry after
23071 that. Hopefully this will improve the expected user experience.
23072 - Patch from Tup to add support for transparent AP connections:
23073 this basically bundles the functionality of trans-proxy-tor
23074 into the Tor mainline. Now hosts with compliant pf/netfilter
23075 implementations can redirect TCP connections straight to Tor
23076 without diverting through SOCKS. Needs docs.
23077 - Busy directory servers save lots of memory by spooling server
23078 descriptors, v1 directories, and v2 networkstatus docs to buffers
23079 as needed rather than en masse. Also mmap the cached-routers
23080 files, so we don't need to keep the whole thing in memory too.
23081 - Automatically avoid picking more than one node from the same
23082 /16 network when constructing a circuit.
23083 - Revise and clean up the torrc.sample that we ship with; add
23084 a section for BandwidthRate and BandwidthBurst.
23087 - Split circuit_t into origin_circuit_t and or_circuit_t, and
23088 split connection_t into edge, or, dir, control, and base structs.
23089 These will save quite a bit of memory on busy servers, and they'll
23090 also help us track down bugs in the code and bugs in the spec.
23091 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
23092 or later. Log when we are doing this, so we can diagnose it when
23093 it fails. (Also, recommend libevent 1.1b for kqueue and
23094 win32 methods; deprecate libevent 1.0b harder; make libevent
23095 recommendation system saner.)
23096 - Start being able to build universal binaries on OS X (thanks
23098 - Export the default exit policy via the control port, so controllers
23099 don't need to guess what it is / will be later.
23100 - Add a man page entry for ProtocolWarnings.
23101 - Add TestVia config option to the man page.
23102 - Remove even more protocol-related warnings from Tor server logs,
23103 such as bad TLS handshakes and malformed begin cells.
23104 - Stop fetching descriptors if you're not a dir mirror and you
23105 haven't tried to establish any circuits lately. [This currently
23106 causes some dangerous behavior, because when you start up again
23107 you'll use your ancient server descriptors.]
23108 - New DirPort behavior: if you have your dirport set, you download
23109 descriptors aggressively like a directory mirror, whether or not
23110 your ORPort is set.
23111 - Get rid of the router_retry_connections notion. Now routers
23112 no longer try to rebuild long-term connections to directory
23113 authorities, and directory authorities no longer try to rebuild
23114 long-term connections to all servers. We still don't hang up
23115 connections in these two cases though -- we need to look at it
23116 more carefully to avoid flapping, and we likely need to wait til
23117 0.1.1.x is obsolete.
23118 - Drop compatibility with obsolete Tors that permit create cells
23119 to have the wrong circ_id_type.
23120 - Re-enable per-connection rate limiting. Get rid of the "OP
23121 bandwidth" concept. Lay groundwork for "bandwidth classes" --
23122 separate global buckets that apply depending on what sort of conn
23124 - Start publishing one minute or so after we find our ORPort
23125 to be reachable. This will help reduce the number of descriptors
23126 we have for ourselves floating around, since it's quite likely
23127 other things (e.g. DirPort) will change during that minute too.
23128 - Fork the v1 directory protocol into its own spec document,
23129 and mark dir-spec.txt as the currently correct (v2) spec.
23132 - When we find our DirPort to be reachable, publish a new descriptor
23133 so we'll tell the world (reported by pnx).
23134 - Publish a new descriptor after we hup/reload. This is important
23135 if our config has changed such that we'll want to start advertising
23136 our DirPort now, etc.
23137 - Allow Tor to start when RunAsDaemon is set but no logs are set.
23138 - When we have a state file we cannot parse, tell the user and
23139 move it aside. Now we avoid situations where the user starts
23140 Tor in 1904, Tor writes a state file with that timestamp in it,
23141 the user fixes her clock, and Tor refuses to start.
23142 - Fix configure.in to not produce broken configure files with
23143 more recent versions of autoconf. Thanks to Clint for his auto*
23145 - "tor --verify-config" now exits with -1(255) or 0 depending on
23146 whether the config options are bad or good.
23147 - Resolve bug 321 when using dnsworkers: append a period to every
23148 address we resolve at the exit node, so that we do not accidentally
23149 pick up local addresses, and so that failing searches are retried
23150 in the resolver search domains. (This is already solved for
23151 eventdns.) (This breaks Blossom servers for now.)
23152 - If we are using an exit enclave and we can't connect, e.g. because
23153 its webserver is misconfigured to not listen on localhost, then
23154 back off and try connecting from somewhere else before we fail.
23157 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
23158 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
23159 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
23160 when the IP address is mapped through MapAddress to a hostname.
23161 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
23162 useless IPv6 DNS resolves.
23163 - Patch suggested by Karsten Loesing: respond to SIGNAL command
23164 before we execute the signal, in case the signal shuts us down.
23165 - Clean up AllowInvalidNodes man page entry.
23166 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
23167 - Add more asserts to track down an assert error on a windows Tor
23168 server with connection_add being called with socket == -1.
23169 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
23170 - Fix misleading log messages: an entry guard that is "unlisted",
23171 as well as not known to be "down" (because we've never heard
23172 of it), is not therefore "up".
23173 - Remove code to special-case "-cvs" ending, since it has not
23174 actually mattered since 0.0.9.
23175 - Make our socks5 handling more robust to broken socks clients:
23176 throw out everything waiting on the buffer in between socks
23177 handshake phases, since they can't possibly (so the theory
23178 goes) have predicted what we plan to respond to them.
23181 Changes in version 0.1.1.23 - 2006-07-30
23183 - Fast Tor servers, especially exit nodes, were triggering asserts
23184 due to a bug in handling the list of pending DNS resolves. Some
23185 bugs still remain here; we're hunting them.
23186 - Entry guards could crash clients by sending unexpected input.
23187 - More fixes on reachability testing: if you find yourself reachable,
23188 then don't ever make any client requests (so you stop predicting
23189 circuits), then hup or have your clock jump, then later your IP
23190 changes, you won't think circuits are working, so you won't try to
23191 test reachability, so you won't publish.
23194 - Avoid a crash if the controller does a resetconf firewallports
23195 and then a setconf fascistfirewall=1.
23196 - Avoid an integer underflow when the dir authority decides whether
23197 a router is stable: we might wrongly label it stable, and compute
23198 a slightly wrong median stability, when a descriptor is published
23200 - Fix a place where we might trigger an assert if we can't build our
23201 own server descriptor yet.
23204 Changes in version 0.1.1.22 - 2006-07-05
23206 - Fix a big bug that was causing servers to not find themselves
23207 reachable if they changed IP addresses. Since only 0.1.1.22+
23208 servers can do reachability testing correctly, now we automatically
23209 make sure to test via one of these.
23210 - Fix to allow clients and mirrors to learn directory info from
23211 descriptor downloads that get cut off partway through.
23212 - Directory authorities had a bug in deciding if a newly published
23213 descriptor was novel enough to make everybody want a copy -- a few
23214 servers seem to be publishing new descriptors many times a minute.
23216 - Fix a rare bug that was causing some servers to complain about
23217 "closing wedged cpuworkers" and skip some circuit create requests.
23218 - Make the Exit flag in directory status documents actually work.
23221 Changes in version 0.1.1.21 - 2006-06-10
23222 o Crash and assert fixes from 0.1.1.20:
23223 - Fix a rare crash on Tor servers that have enabled hibernation.
23224 - Fix a seg fault on startup for Tor networks that use only one
23225 directory authority.
23226 - Fix an assert from a race condition that occurs on Tor servers
23227 while exiting, where various threads are trying to log that they're
23228 exiting, and delete the logs, at the same time.
23229 - Make our unit tests pass again on certain obscure platforms.
23232 - Add support for building SUSE RPM packages.
23233 - Speed up initial bootstrapping for clients: if we are making our
23234 first ever connection to any entry guard, then don't mark it down
23236 - When only one Tor server in the network is labelled as a guard,
23237 and we've already picked him, we would cycle endlessly picking him
23238 again, being unhappy about it, etc. Now we specifically exclude
23239 current guards when picking a new guard.
23240 - Servers send create cells more reliably after the TLS connection
23241 is established: we were sometimes forgetting to send half of them
23242 when we had more than one pending.
23243 - If we get a create cell that asks us to extend somewhere, but the
23244 Tor server there doesn't match the expected digest, we now send
23245 a destroy cell back, rather than silently doing nothing.
23246 - Make options->RedirectExit work again.
23247 - Make cookie authentication for the controller work again.
23248 - Stop being picky about unusual characters in the arguments to
23249 mapaddress. It's none of our business.
23250 - Add a new config option "TestVia" that lets you specify preferred
23251 middle hops to use for test circuits. Perhaps this will let me
23252 debug the reachability problems better.
23254 o Log / documentation fixes:
23255 - If we're a server and some peer has a broken TLS certificate, don't
23256 log about it unless ProtocolWarnings is set, i.e., we want to hear
23257 about protocol violations by others.
23258 - Fix spelling of VirtualAddrNetwork in man page.
23259 - Add a better explanation at the top of the autogenerated torrc file
23260 about what happened to our old torrc.
23263 Changes in version 0.1.1.20 - 2006-05-23
23265 - Downgrade a log severity where servers complain that they're
23267 - Avoid a compile warning on FreeBSD.
23268 - Remove string size limit on NEWDESC messages; solve bug 291.
23269 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
23270 more thoroughly when we're running on windows.
23273 Changes in version 0.1.1.19-rc - 2006-05-03
23275 - Regenerate our local descriptor if it's dirty and we try to use
23276 it locally (e.g. if it changes during reachability detection).
23277 - If we setconf our ORPort to 0, we continued to listen on the
23278 old ORPort and receive connections.
23279 - Avoid a second warning about machine/limits.h on Debian
23281 - Be willing to add our own routerinfo into the routerlist.
23282 Now authorities will include themselves in their directories
23283 and network-statuses.
23284 - Stop trying to upload rendezvous descriptors to every
23285 directory authority: only try the v1 authorities.
23286 - Servers no longer complain when they think they're not
23287 registered with the directory authorities. There were too many
23289 - Backport dist-rpm changes so rpms can be built without errors.
23292 - Implement an option, VirtualAddrMask, to set which addresses
23293 get handed out in response to mapaddress requests. This works
23294 around a bug in tsocks where 127.0.0.0/8 is never socksified.
23297 Changes in version 0.1.1.18-rc - 2006-04-10
23299 - Work harder to download live network-statuses from all the
23300 directory authorities we know about. Improve the threshold
23301 decision logic so we're more robust to edge cases.
23302 - When fetching rendezvous descriptors, we were willing to ask
23303 v2 authorities too, which would always return 404.
23306 - Stop listing down or invalid nodes in the v1 directory. This will
23307 reduce its bulk by about 1/3, and reduce load on directory
23309 - When deciding whether a router is Fast or Guard-worthy, consider
23310 his advertised BandwidthRate and not just the BandwidthCapacity.
23311 - No longer ship INSTALL and README files -- they are useless now.
23312 - Force rpmbuild to behave and honor target_cpu.
23313 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
23314 - Start to include translated versions of the tor-doc-*.html
23315 files, along with the screenshots. Still needs more work.
23316 - Start sending back 512 and 451 errors if mapaddress fails,
23317 rather than not sending anything back at all.
23318 - When we fail to bind or listen on an incoming or outgoing
23319 socket, we should close it before failing. otherwise we just
23320 leak it. (thanks to weasel for finding.)
23321 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
23322 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
23323 - Make NoPublish (even though deprecated) work again.
23324 - Fix a minor security flaw where a versioning auth dirserver
23325 could list a recommended version many times in a row to make
23326 clients more convinced that it's recommended.
23327 - Fix crash bug if there are two unregistered servers running
23328 with the same nickname, one of them is down, and you ask for
23329 them by nickname in your EntryNodes or ExitNodes. Also, try
23330 to pick the one that's running rather than an arbitrary one.
23331 - Fix an infinite loop we could hit if we go offline for too long.
23332 - Complain when we hit WSAENOBUFS on recv() or write() too.
23333 Perhaps this will help us hunt the bug.
23334 - If you're not a versioning dirserver, don't put the string
23335 "client-versions \nserver-versions \n" in your network-status.
23336 - Lower the minimum required number of file descriptors to 1000,
23337 so we can have some overhead for Valgrind on Linux, where the
23338 default ulimit -n is 1024.
23341 - Add tor.dizum.com as the fifth authoritative directory server.
23342 - Add a new config option FetchUselessDescriptors, off by default,
23343 for when you plan to run "exitlist" on your client and you want
23344 to know about even the non-running descriptors.
23347 Changes in version 0.1.1.17-rc - 2006-03-28
23349 - Clients and servers since 0.1.1.10-alpha have been expiring
23350 connections whenever they are idle for 5 minutes and they *do*
23351 have circuits on them. Oops. With this new version, clients will
23352 discard their previous entry guard choices and avoid choosing
23353 entry guards running these flawed versions.
23354 - Fix memory leak when uncompressing concatenated zlib streams. This
23355 was causing substantial leaks over time on Tor servers.
23356 - The v1 directory was including servers as much as 48 hours old,
23357 because that's how the new routerlist->routers works. Now only
23358 include them if they're 20 hours old or less.
23361 - Resume building on irix64, netbsd 2.0, etc.
23362 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
23364 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
23365 and it is confusing some users.
23366 - Mirrors stop caching the v1 directory so often.
23367 - Make the max number of old descriptors that a cache will hold
23368 rise with the number of directory authorities, so we can scale.
23369 - Change our win32 uname() hack to be more forgiving about what
23370 win32 versions it thinks it's found.
23373 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
23375 - When the controller's *setconf commands fail, collect an error
23376 message in a string and hand it back to the controller.
23377 - Make the v2 dir's "Fast" flag based on relative capacity, just
23378 like "Stable" is based on median uptime. Name everything in the
23379 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
23380 - Log server fingerprint on startup, so new server operators don't
23381 have to go hunting around their filesystem for it.
23382 - Return a robots.txt on our dirport to discourage google indexing.
23383 - Let the controller ask for GETINFO dir/status/foo so it can ask
23384 directly rather than connecting to the dir port. Only works when
23385 dirport is set for now.
23387 o New config options rather than constants in the code:
23388 - SocksTimeout: How long do we let a socks connection wait
23389 unattached before we fail it?
23390 - CircuitBuildTimeout: Cull non-open circuits that were born
23391 at least this many seconds ago.
23392 - CircuitIdleTimeout: Cull open clean circuits that were born
23393 at least this many seconds ago.
23396 Changes in version 0.1.1.16-rc - 2006-03-18
23397 o Bugfixes on 0.1.1.15-rc:
23398 - Fix assert when the controller asks to attachstream a connect-wait
23399 or resolve-wait stream.
23400 - Now do address rewriting when the controller asks us to attach
23401 to a particular circuit too. This will let Blossom specify
23402 "moria2.exit" without having to learn what moria2's IP address is.
23403 - Make the "tor --verify-config" command-line work again, so people
23404 can automatically check if their torrc will parse.
23405 - Authoritative dirservers no longer require an open connection from
23406 a server to consider him "reachable". We need this change because
23407 when we add new auth dirservers, old servers won't know not to
23409 - Let Tor build on Sun CC again.
23410 - Fix an off-by-one buffer size in dirserv.c that magically never
23411 hit our three authorities but broke sjmurdoch's own tor network.
23412 - If we as a directory mirror don't know of any v1 directory
23413 authorities, then don't try to cache any v1 directories.
23414 - Stop warning about unknown servers in our family when they are
23415 given as hex digests.
23416 - Stop complaining as quickly to the server operator that he
23417 hasn't registered his nickname/key binding.
23418 - Various cleanups so we can add new V2 Auth Dirservers.
23419 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
23420 reflect the updated flags in our v2 dir protocol.
23421 - Resume allowing non-printable characters for exit streams (both
23422 for connecting and for resolving). Now we tolerate applications
23423 that don't follow the RFCs. But continue to block malformed names
23426 o Bugfixes on 0.1.0.x:
23427 - Fix assert bug in close_logs(): when we close and delete logs,
23428 remove them all from the global "logfiles" list.
23429 - Fix minor integer overflow in calculating when we expect to use up
23430 our bandwidth allocation before hibernating.
23431 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
23432 there are multiple SSLs installed with different versions.
23433 - When we try to be a server and Address is not explicitly set and
23434 our hostname resolves to a private IP address, try to use an
23435 interface address if it has a public address. Now Windows machines
23436 that think of themselves as localhost can work by default.
23439 - Let the controller ask for GETINFO dir/server/foo so it can ask
23440 directly rather than connecting to the dir port.
23441 - Let the controller tell us about certain router descriptors
23442 that it doesn't want Tor to use in circuits. Implement
23443 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
23444 - New config option SafeSocks to reject all application connections
23445 using unsafe socks protocols. Defaults to off.
23448 Changes in version 0.1.1.15-rc - 2006-03-11
23449 o Bugfixes and cleanups:
23450 - When we're printing strings from the network, don't try to print
23451 non-printable characters. This protects us against shell escape
23452 sequence exploits, and also against attacks to fool humans into
23453 misreading their logs.
23454 - Fix a bug where Tor would fail to establish any connections if you
23455 left it off for 24 hours and then started it: we were happy with
23456 the obsolete network statuses, but they all referred to router
23457 descriptors that were too old to fetch, so we ended up with no
23458 valid router descriptors.
23459 - Fix a seg fault in the controller's "getinfo orconn-status"
23460 command while listing status on incoming handshaking connections.
23461 Introduce a status name "NEW" for these connections.
23462 - If we get a linelist or linelist_s config option from the torrc
23463 (e.g. ExitPolicy) and it has no value, warn and skip rather than
23464 silently resetting it to its default.
23465 - Don't abandon entry guards until they've been down or gone for
23467 - Cleaner and quieter log messages.
23470 - New controller signal NEWNYM that makes new application requests
23471 use clean circuits.
23472 - Add a new circuit purpose 'controller' to let the controller ask
23473 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
23474 controller command to let you specify the purpose if you're
23475 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
23476 command to let you change a circuit's purpose after it's been
23478 - Accept "private:*" in routerdesc exit policies; not generated yet
23479 because older Tors do not understand it.
23480 - Add BSD-style contributed startup script "rc.subr" from Peter
23484 Changes in version 0.1.1.14-alpha - 2006-02-20
23485 o Bugfixes on 0.1.1.x:
23486 - Don't die if we ask for a stdout or stderr log (even implicitly)
23487 and we're set to RunAsDaemon -- just warn.
23488 - We still had a few bugs in the OR connection rotation code that
23489 caused directory servers to slowly aggregate connections to other
23490 fast Tor servers. This time for sure!
23491 - Make log entries on Win32 include the name of the function again.
23492 - We were treating a pair of exit policies if they were equal even
23493 if one said accept and the other said reject -- causing us to
23494 not always publish a new descriptor since we thought nothing
23496 - Retry pending server downloads as well as pending networkstatus
23497 downloads when we unexpectedly get a socks request.
23498 - We were ignoring the IS_FAST flag in the directory status,
23499 meaning we were willing to pick trivial-bandwidth nodes for "fast"
23501 - If the controller's SAVECONF command fails (e.g. due to file
23502 permissions), let the controller know that it failed.
23505 - If we're trying to be a Tor server and running Windows 95/98/ME
23506 as a server, explain that we'll likely crash.
23507 - When we're a server, a client asks for an old-style directory,
23508 and our write bucket is empty, don't give it to him. This way
23509 small servers can continue to serve the directory *sometimes*,
23510 without getting overloaded.
23511 - Compress exit policies even more -- look for duplicate lines
23513 - Clients now honor the "guard" flag in the router status when
23514 picking entry guards, rather than looking at is_fast or is_stable.
23515 - Retain unrecognized lines in $DATADIR/state file, so that we can
23516 be forward-compatible.
23517 - Generate 18.0.0.0/8 address policy format in descs when we can;
23518 warn when the mask is not reducible to a bit-prefix.
23519 - Let the user set ControlListenAddress in the torrc. This can be
23520 dangerous, but there are some cases (like a secured LAN) where it
23522 - Split ReachableAddresses into ReachableDirAddresses and
23523 ReachableORAddresses, so we can restrict Dir conns to port 80
23524 and OR conns to port 443.
23525 - Now we can target arch and OS in rpm builds (contributed by
23526 Phobos). Also make the resulting dist-rpm filename match the
23528 - New config options to help controllers: FetchServerDescriptors
23529 and FetchHidServDescriptors for whether to fetch server
23530 info and hidserv info or let the controller do it, and
23531 PublishServerDescriptor and PublishHidServDescriptors.
23532 - Also let the controller set the __AllDirActionsPrivate config
23533 option if you want all directory fetches/publishes to happen via
23534 Tor (it assumes your controller bootstraps your circuits).
23537 Changes in version 0.1.0.17 - 2006-02-17
23538 o Crash bugfixes on 0.1.0.x:
23539 - When servers with a non-zero DirPort came out of hibernation,
23540 sometimes they would trigger an assert.
23542 o Other important bugfixes:
23543 - On platforms that don't have getrlimit (like Windows), we were
23544 artificially constraining ourselves to a max of 1024
23545 connections. Now just assume that we can handle as many as 15000
23546 connections. Hopefully this won't cause other problems.
23548 o Backported features:
23549 - When we're a server, a client asks for an old-style directory,
23550 and our write bucket is empty, don't give it to him. This way
23551 small servers can continue to serve the directory *sometimes*,
23552 without getting overloaded.
23553 - Whenever you get a 503 in response to a directory fetch, try
23554 once more. This will become important once servers start sending
23555 503's whenever they feel busy.
23556 - Fetch a new directory every 120 minutes, not every 40 minutes.
23557 Now that we have hundreds of thousands of users running the old
23558 directory algorithm, it's starting to hurt a lot.
23559 - Bump up the period for forcing a hidden service descriptor upload
23560 from 20 minutes to 1 hour.
23563 Changes in version 0.1.1.13-alpha - 2006-02-09
23564 o Crashes in 0.1.1.x:
23565 - When you tried to setconf ORPort via the controller, Tor would
23566 crash. So people using TorCP to become a server were sad.
23567 - Solve (I hope) the stack-smashing bug that we were seeing on fast
23568 servers. The problem appears to be something do with OpenSSL's
23569 random number generation, or how we call it, or something. Let me
23570 know if the crashes continue.
23571 - Turn crypto hardware acceleration off by default, until we find
23572 somebody smart who can test it for us. (It appears to produce
23573 seg faults in at least some cases.)
23574 - Fix a rare assert error when we've tried all intro points for
23575 a hidden service and we try fetching the service descriptor again:
23576 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
23579 - Fix a major load balance bug: we were round-robining in 16 KB
23580 chunks, and servers with bandwidthrate of 20 KB, while downloading
23581 a 600 KB directory, would starve their other connections. Now we
23582 try to be a bit more fair.
23583 - Dir authorities and mirrors were never expiring the newest
23584 descriptor for each server, causing memory and directory bloat.
23585 - Fix memory-bloating and connection-bloating bug on servers: We
23586 were never closing any connection that had ever had a circuit on
23587 it, because we were checking conn->n_circuits == 0, yet we had a
23588 bug that let it go negative.
23589 - Make Tor work using squid as your http proxy again -- squid
23590 returns an error if you ask for a URL that's too long, and it uses
23591 a really generic error message. Plus, many people are behind a
23592 transparent squid so they don't even realize it.
23593 - On platforms that don't have getrlimit (like Windows), we were
23594 artificially constraining ourselves to a max of 1024
23595 connections. Now just assume that we can handle as many as 15000
23596 connections. Hopefully this won't cause other problems.
23597 - Add a new config option ExitPolicyRejectPrivate which defaults to
23598 1. This means all exit policies will begin with rejecting private
23599 addresses, unless the server operator explicitly turns it off.
23602 - Clients no longer download descriptors for non-running
23604 - Before we add new directory authorities, we should make it
23605 clear that only v1 authorities should receive/publish hidden
23606 service descriptors.
23609 - As soon as we've fetched some more directory info, immediately
23610 try to download more server descriptors. This way we don't have
23611 a 10 second pause during initial bootstrapping.
23612 - Remove even more loud log messages that the server operator can't
23614 - When we're running an obsolete or un-recommended version, make
23615 the log message more clear about what the problem is and what
23616 versions *are* still recommended.
23617 - Provide a more useful warn message when our onion queue gets full:
23618 the CPU is too slow or the exit policy is too liberal.
23619 - Don't warn when we receive a 503 from a dirserver/cache -- this
23620 will pave the way for them being able to refuse if they're busy.
23621 - When we fail to bind a listener, try to provide a more useful
23622 log message: e.g., "Is Tor already running?"
23623 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
23624 Goldberg can prove things about our handshake protocol more
23626 - MaxConn has been obsolete for a while now. Document the ConnLimit
23627 config option, which is a *minimum* number of file descriptors
23628 that must be available else Tor refuses to start.
23629 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
23630 if you log to syslog and want something other than LOG_DAEMON.
23631 - Make dirservers generate a separate "guard" flag to mean,
23632 "would make a good entry guard". Make clients parse it and vote
23633 on it. Not used by clients yet.
23634 - Implement --with-libevent-dir option to ./configure. Also, improve
23635 search techniques to find libevent, and use those for openssl too.
23636 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
23637 - Only start testing reachability once we've established a
23638 circuit. This will make startup on dirservers less noisy.
23639 - Don't try to upload hidden service descriptors until we have
23640 established a circuit.
23641 - Fix the controller's "attachstream 0" command to treat conn like
23642 it just connected, doing address remapping, handling .exit and
23643 .onion idioms, and so on. Now we're more uniform in making sure
23644 that the controller hears about new and closing connections.
23647 Changes in version 0.1.1.12-alpha - 2006-01-11
23648 o Bugfixes on 0.1.1.x:
23649 - The fix to close duplicate server connections was closing all
23650 Tor client connections if they didn't establish a circuit
23651 quickly enough. Oops.
23652 - Fix minor memory issue (double-free) that happened on exit.
23654 o Bugfixes on 0.1.0.x:
23655 - Tor didn't warn when it failed to open a log file.
23658 Changes in version 0.1.1.11-alpha - 2006-01-10
23659 o Crashes in 0.1.1.x:
23660 - Include all the assert/crash fixes from 0.1.0.16.
23661 - If you start Tor and then quit very quickly, there were some
23662 races that tried to free things that weren't allocated yet.
23663 - Fix a rare memory stomp if you're running hidden services.
23664 - Fix segfault when specifying DirServer in config without nickname.
23665 - Fix a seg fault when you finish connecting to a server but at
23666 that moment you dump his server descriptor.
23667 - Extendcircuit and Attachstream controller commands would
23668 assert/crash if you don't give them enough arguments.
23669 - Fix an assert error when we're out of space in the connection_list
23670 and we try to post a hidden service descriptor (reported by weasel).
23671 - If you specify a relative torrc path and you set RunAsDaemon in
23672 your torrc, then it chdir()'s to the new directory. If you HUP,
23673 it tries to load the new torrc location, fails, and exits.
23674 The fix: no longer allow a relative path to torrc using -f.
23677 - Implement "entry guards": automatically choose a handful of entry
23678 nodes and stick with them for all circuits. Only pick new guards
23679 when the ones you have are unsuitable, and if the old guards
23680 become suitable again, switch back. This will increase security
23681 dramatically against certain end-point attacks. The EntryNodes
23682 config option now provides some hints about which entry guards you
23683 want to use most; and StrictEntryNodes means to only use those.
23684 - New directory logic: download by descriptor digest, not by
23685 fingerprint. Caches try to download all listed digests from
23686 authorities; clients try to download "best" digests from caches.
23687 This avoids partitioning and isolating attacks better.
23688 - Make the "stable" router flag in network-status be the median of
23689 the uptimes of running valid servers, and make clients pay
23690 attention to the network-status flags. Thus the cutoff adapts
23691 to the stability of the network as a whole, making IRC, IM, etc
23692 connections more reliable.
23695 - Tor servers with dynamic IP addresses were needing to wait 18
23696 hours before they could start doing reachability testing using
23697 the new IP address and ports. This is because they were using
23698 the internal descriptor to learn what to test, yet they were only
23699 rebuilding the descriptor once they decided they were reachable.
23700 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
23701 to download certain server descriptors, throw them away, and then
23702 fetch them again after 30 minutes. Now mirrors throw away these
23703 server descriptors so clients can't get them.
23704 - We were leaving duplicate connections to other ORs open for a week,
23705 rather than closing them once we detect a duplicate. This only
23706 really affected authdirservers, but it affected them a lot.
23707 - Spread the authdirservers' reachability testing over the entire
23708 testing interval, so we don't try to do 500 TLS's at once every
23712 - If the network is down, and we try to connect to a conn because
23713 we have a circuit in mind, and we timeout (30 seconds) because the
23714 network never answers, we were expiring the circuit, but we weren't
23715 obsoleting the connection or telling the entry_guards functions.
23716 - Some Tor servers process billions of cells per day. These statistics
23717 need to be uint64_t's.
23718 - Check for integer overflows in more places, when adding elements
23719 to smartlists. This could possibly prevent a buffer overflow
23720 on malicious huge inputs. I don't see any, but I haven't looked
23722 - ReachableAddresses kept growing new "reject *:*" lines on every
23724 - When you "setconf log" via the controller, it should remove all
23725 logs. We were automatically adding back in a "log notice stdout".
23726 - Newly bootstrapped Tor networks couldn't establish hidden service
23727 circuits until they had nodes with high uptime. Be more tolerant.
23728 - We were marking servers down when they could not answer every piece
23729 of the directory request we sent them. This was far too harsh.
23730 - Fix the torify (tsocks) config file to not use Tor for localhost
23732 - Directory authorities now go to the proper authority when asking for
23733 a networkstatus, even when they want a compressed one.
23734 - Fix a harmless bug that was causing Tor servers to log
23735 "Got an end because of misc error, but we're not an AP. Closing."
23736 - Authorities were treating their own descriptor changes as cosmetic,
23737 meaning the descriptor available in the network-status and the
23738 descriptor that clients downloaded were different.
23739 - The OS X installer was adding a symlink for tor_resolve but
23740 the binary was called tor-resolve (reported by Thomas Hardly).
23741 - Workaround a problem with some http proxies where they refuse GET
23742 requests that specify "Content-Length: 0" (reported by Adrian).
23743 - Fix wrong log message when you add a "HiddenServiceNodes" config
23744 line without any HiddenServiceDir line (reported by Chris Thomas).
23747 - Write the TorVersion into the state file so we have a prayer of
23748 keeping forward and backward compatibility.
23749 - Revive the FascistFirewall config option rather than eliminating it:
23750 now it's a synonym for ReachableAddresses *:80,*:443.
23751 - Clients choose directory servers from the network status lists,
23752 not from their internal list of router descriptors. Now they can
23753 go to caches directly rather than needing to go to authorities
23755 - Directory authorities ignore router descriptors that have only
23756 cosmetic differences: do this for 0.1.0.x servers now too.
23757 - Add a new flag to network-status indicating whether the server
23758 can answer v2 directory requests too.
23759 - Authdirs now stop whining so loudly about bad descriptors that
23760 they fetch from other dirservers. So when there's a log complaint,
23761 it's for sure from a freshly uploaded descriptor.
23762 - Reduce memory requirements in our structs by changing the order
23764 - There used to be two ways to specify your listening ports in a
23765 server descriptor: on the "router" line and with a separate "ports"
23766 line. Remove support for the "ports" line.
23767 - New config option "AuthDirRejectUnlisted" for auth dirservers as
23768 a panic button: if we get flooded with unusable servers we can
23769 revert to only listing servers in the approved-routers file.
23770 - Auth dir servers can now mark a fingerprint as "!reject" or
23771 "!invalid" in the approved-routers file (as its nickname), to
23772 refuse descriptors outright or include them but marked as invalid.
23773 - Servers store bandwidth history across restarts/crashes.
23774 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
23775 get a better idea of why their circuits failed. Not used yet.
23776 - Directory mirrors now cache up to 16 unrecognized network-status
23777 docs. Now we can add new authdirservers and they'll be cached too.
23778 - When picking a random directory, prefer non-authorities if any
23780 - New controller option "getinfo desc/all-recent" to fetch the
23781 latest server descriptor for every router that Tor knows about.
23784 Changes in version 0.1.0.16 - 2006-01-02
23785 o Crash bugfixes on 0.1.0.x:
23786 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
23787 corrupting the heap, losing FDs, or crashing when we need to resize
23788 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
23789 - It turns out sparc64 platforms crash on unaligned memory access
23790 too -- so detect and avoid this.
23791 - Handle truncated compressed data correctly (by detecting it and
23793 - Fix possible-but-unlikely free(NULL) in control.c.
23794 - When we were closing connections, there was a rare case that
23795 stomped on memory, triggering seg faults and asserts.
23796 - Avoid potential infinite recursion when building a descriptor. (We
23797 don't know that it ever happened, but better to fix it anyway.)
23798 - We were neglecting to unlink marked circuits from soon-to-close OR
23799 connections, which caused some rare scribbling on freed memory.
23800 - Fix a memory stomping race bug when closing the joining point of two
23801 rendezvous circuits.
23802 - Fix an assert in time parsing found by Steven Murdoch.
23804 o Other bugfixes on 0.1.0.x:
23805 - When we're doing reachability testing, provide more useful log
23806 messages so the operator knows what to expect.
23807 - Do not check whether DirPort is reachable when we are suppressing
23808 advertising it because of hibernation.
23809 - When building with -static or on Solaris, we sometimes needed -ldl.
23810 - When we're deciding whether a stream has enough circuits around
23811 that can handle it, count the freshly dirty ones and not the ones
23812 that are so dirty they won't be able to handle it.
23813 - When we're expiring old circuits, we had a logic error that caused
23814 us to close new rendezvous circuits rather than old ones.
23815 - Give a more helpful log message when you try to change ORPort via
23816 the controller: you should upgrade Tor if you want that to work.
23817 - We were failing to parse Tor versions that start with "Tor ".
23818 - Tolerate faulty streams better: when a stream fails for reason
23819 exitpolicy, stop assuming that the router is lying about his exit
23820 policy. When a stream fails for reason misc, allow it to retry just
23821 as if it was resolvefailed. When a stream has failed three times,
23822 reset its failure count so we can try again and get all three tries.
23825 Changes in version 0.1.1.10-alpha - 2005-12-11
23826 o Correctness bugfixes on 0.1.0.x:
23827 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
23828 corrupting the heap, losing FDs, or crashing when we need to resize
23829 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
23830 - Stop doing the complex voodoo overkill checking for insecure
23831 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
23832 - When we were closing connections, there was a rare case that
23833 stomped on memory, triggering seg faults and asserts.
23834 - We were neglecting to unlink marked circuits from soon-to-close OR
23835 connections, which caused some rare scribbling on freed memory.
23836 - When we're deciding whether a stream has enough circuits around
23837 that can handle it, count the freshly dirty ones and not the ones
23838 that are so dirty they won't be able to handle it.
23839 - Recover better from TCP connections to Tor servers that are
23840 broken but don't tell you (it happens!); and rotate TLS
23841 connections once a week.
23842 - When we're expiring old circuits, we had a logic error that caused
23843 us to close new rendezvous circuits rather than old ones.
23844 - Fix a scary-looking but apparently harmless bug where circuits
23845 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
23846 servers, and never switch to state CIRCUIT_STATE_OPEN.
23847 - When building with -static or on Solaris, we sometimes needed to
23849 - Give a useful message when people run Tor as the wrong user,
23850 rather than telling them to start chowning random directories.
23851 - We were failing to inform the controller about new .onion streams.
23853 o Security bugfixes on 0.1.0.x:
23854 - Refuse server descriptors if the fingerprint line doesn't match
23855 the included identity key. Tor doesn't care, but other apps (and
23856 humans) might actually be trusting the fingerprint line.
23857 - We used to kill the circuit when we receive a relay command we
23858 don't recognize. Now we just drop it.
23859 - Start obeying our firewall options more rigorously:
23860 . If we can't get to a dirserver directly, try going via Tor.
23861 . Don't ever try to connect (as a client) to a place our
23862 firewall options forbid.
23863 . If we specify a proxy and also firewall options, obey the
23864 firewall options even when we're using the proxy: some proxies
23865 can only proxy to certain destinations.
23866 - Fix a bug found by Lasse Overlier: when we were making internal
23867 circuits (intended to be cannibalized later for rendezvous and
23868 introduction circuits), we were picking them so that they had
23869 useful exit nodes. There was no need for this, and it actually
23870 aids some statistical attacks.
23871 - Start treating internal circuits and exit circuits separately.
23872 It's important to keep them separate because internal circuits
23873 have their last hops picked like middle hops, rather than like
23874 exit hops. So exiting on them will break the user's expectations.
23876 o Bugfixes on 0.1.1.x:
23877 - Take out the mis-feature where we tried to detect IP address
23878 flapping for people with DynDNS, and chose not to upload a new
23879 server descriptor sometimes.
23880 - Try to be compatible with OpenSSL 0.9.6 again.
23881 - Log fix: when the controller is logging about .onion addresses,
23882 sometimes it didn't include the ".onion" part of the address.
23883 - Don't try to modify options->DirServers internally -- if the
23884 user didn't specify any, just add the default ones directly to
23885 the trusted dirserver list. This fixes a bug where people running
23886 controllers would use SETCONF on some totally unrelated config
23887 option, and Tor would start yelling at them about changing their
23889 - Let the controller's redirectstream command specify a port, in
23890 case the controller wants to change that too.
23891 - When we requested a pile of server descriptors, we sometimes
23892 accidentally launched a duplicate request for the first one.
23893 - Bugfix for trackhostexits: write down the fingerprint of the
23894 chosen exit, not its nickname, because the chosen exit might not
23896 - When parsing foo.exit, if foo is unknown, and we are leaving
23897 circuits unattached, set the chosen_exit field and leave the
23898 address empty. This matters because controllers got confused
23900 - Directory authorities no longer try to download server
23901 descriptors that they know they will reject.
23903 o Features and updates:
23904 - Replace balanced trees with hash tables: this should make stuff
23905 significantly faster.
23906 - Resume using the AES counter-mode implementation that we ship,
23907 rather than OpenSSL's. Ours is significantly faster.
23908 - Many other CPU and memory improvements.
23909 - Add a new config option FastFirstHopPK (on by default) so clients
23910 do a trivial crypto handshake for their first hop, since TLS has
23911 already taken care of confidentiality and authentication.
23912 - Add a new config option TestSocks so people can see if their
23913 applications are using socks4, socks4a, socks5-with-ip, or
23914 socks5-with-hostname. This way they don't have to keep mucking
23915 with tcpdump and wondering if something got cached somewhere.
23916 - Warn when listening on a public address for socks. I suspect a
23917 lot of people are setting themselves up as open socks proxies,
23918 and they have no idea that jerks on the Internet are using them,
23919 since they simply proxy the traffic into the Tor network.
23920 - Add "private:*" as an alias in configuration for policies. Now
23921 you can simplify your exit policy rather than needing to list
23922 every single internal or nonroutable network space.
23923 - Add a new controller event type that allows controllers to get
23924 all server descriptors that were uploaded to a router in its role
23925 as authoritative dirserver.
23926 - Start shipping socks-extensions.txt, tor-doc-unix.html,
23927 tor-doc-server.html, and stylesheet.css in the tarball.
23928 - Stop shipping tor-doc.html in the tarball.
23931 Changes in version 0.1.1.9-alpha - 2005-11-15
23932 o Usability improvements:
23933 - Start calling it FooListenAddress rather than FooBindAddress,
23934 since few of our users know what it means to bind an address
23936 - Reduce clutter in server logs. We're going to try to make
23937 them actually usable now. New config option ProtocolWarnings that
23938 lets you hear about how _other Tors_ are breaking the protocol. Off
23940 - Divide log messages into logging domains. Once we put some sort
23941 of interface on this, it will let people looking at more verbose
23942 log levels specify the topics they want to hear more about.
23943 - Make directory servers return better http 404 error messages
23944 instead of a generic "Servers unavailable".
23945 - Check for even more Windows version flags when writing the platform
23946 string in server descriptors, and note any we don't recognize.
23947 - Clean up more of the OpenSSL memory when exiting, so we can detect
23948 memory leaks better.
23949 - Make directory authorities be non-versioning, non-naming by
23950 default. Now we can add new directory servers without requiring
23951 their operators to pay close attention.
23952 - When logging via syslog, include the pid whenever we provide
23953 a log entry. Suggested by Todd Fries.
23955 o Performance improvements:
23956 - Directory servers now silently throw away new descriptors that
23957 haven't changed much if the timestamps are similar. We do this to
23958 tolerate older Tor servers that upload a new descriptor every 15
23959 minutes. (It seemed like a good idea at the time.)
23960 - Inline bottleneck smartlist functions; use fast versions by default.
23961 - Add a "Map from digest to void*" abstraction digestmap_t so we
23962 can do less hex encoding/decoding. Use it in router_get_by_digest()
23963 to resolve a performance bottleneck.
23964 - Allow tor_gzip_uncompress to extract as much as possible from
23965 truncated compressed data. Try to extract as many
23966 descriptors as possible from truncated http responses (when
23967 DIR_PURPOSE_FETCH_ROUTERDESC).
23968 - Make circ->onionskin a pointer, not a static array. moria2 was using
23969 125000 circuit_t's after it had been up for a few weeks, which
23970 translates to 20+ megs of wasted space.
23971 - The private half of our EDH handshake keys are now chosen out
23972 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
23974 o Security improvements:
23975 - Start making directory caches retain old routerinfos, so soon
23976 clients can start asking by digest of descriptor rather than by
23977 fingerprint of server.
23978 - Add half our entropy from RAND_poll in OpenSSL. This knows how
23979 to use egd (if present), openbsd weirdness (if present), vms/os2
23980 weirdness (if we ever port there), and more in the future.
23982 o Bugfixes on 0.1.0.x:
23983 - Do round-robin writes of at most 16 kB per write. This might be
23984 more fair on loaded Tor servers, and it might resolve our Windows
23985 crash bug. It might also slow things down.
23986 - Our TLS handshakes were generating a single public/private
23987 keypair for the TLS context, rather than making a new one for
23988 each new connections. Oops. (But we were still rotating them
23989 periodically, so it's not so bad.)
23990 - When we were cannibalizing a circuit with a particular exit
23991 node in mind, we weren't checking to see if that exit node was
23992 already present earlier in the circuit. Oops.
23993 - When a Tor server's IP changes (e.g. from a dyndns address),
23994 upload a new descriptor so clients will learn too.
23995 - Really busy servers were keeping enough circuits open on stable
23996 connections that they were wrapping around the circuit_id
23997 space. (It's only two bytes.) This exposed a bug where we would
23998 feel free to reuse a circuit_id even if it still exists but has
23999 been marked for close. Try to fix this bug. Some bug remains.
24000 - If we would close a stream early (e.g. it asks for a .exit that
24001 we know would refuse it) but the LeaveStreamsUnattached config
24002 option is set by the controller, then don't close it.
24004 o Bugfixes on 0.1.1.8-alpha:
24005 - Fix a big pile of memory leaks, some of them serious.
24006 - Do not try to download a routerdesc if we would immediately reject
24008 - Resume inserting a newline between all router descriptors when
24009 generating (old style) signed directories, since our spec says
24011 - When providing content-type application/octet-stream for
24012 server descriptors using .z, we were leaving out the
24013 content-encoding header. Oops. (Everything tolerated this just
24014 fine, but that doesn't mean we need to be part of the problem.)
24015 - Fix a potential seg fault in getconf and getinfo using version 1
24016 of the controller protocol.
24017 - Avoid crash: do not check whether DirPort is reachable when we
24018 are suppressing it because of hibernation.
24019 - Make --hash-password not crash on exit.
24022 Changes in version 0.1.1.8-alpha - 2005-10-07
24023 o New features (major):
24024 - Clients don't download or use the directory anymore. Now they
24025 download and use network-statuses from the trusted dirservers,
24026 and fetch individual server descriptors as needed from mirrors.
24027 See dir-spec.txt for all the gory details.
24028 - Be more conservative about whether to advertise our DirPort.
24029 The main change is to not advertise if we're running at capacity
24030 and either a) we could hibernate or b) our capacity is low and
24031 we're using a default DirPort.
24032 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
24034 o New features (minor):
24035 - Try to be smart about when to retry network-status and
24036 server-descriptor fetches. Still needs some tuning.
24037 - Stop parsing, storing, or using running-routers output (but
24038 mirrors still cache and serve it).
24039 - Consider a threshold of versioning dirservers (dirservers who have
24040 an opinion about which Tor versions are still recommended) before
24041 deciding whether to warn the user that he's obsolete.
24042 - Dirservers can now reject/invalidate by key and IP, with the
24043 config options "AuthDirInvalid" and "AuthDirReject". This is
24044 useful since currently we automatically list servers as running
24045 and usable even if we know they're jerks.
24046 - Provide dire warnings to any users who set DirServer; move it out
24047 of torrc.sample and into torrc.complete.
24048 - Add MyFamily to torrc.sample in the server section.
24049 - Add nicknames to the DirServer line, so we can refer to them
24050 without requiring all our users to memorize their IP addresses.
24051 - When we get an EOF or a timeout on a directory connection, note
24052 how many bytes of serverdesc we are dropping. This will help
24053 us determine whether it is smart to parse incomplete serverdesc
24055 - Add a new function to "change pseudonyms" -- that is, to stop
24056 using any currently-dirty circuits for new streams, so we don't
24057 link new actions to old actions. Currently it's only called on
24058 HUP (or SIGNAL RELOAD).
24059 - On sighup, if UseHelperNodes changed to 1, use new circuits.
24060 - Start using RAND_bytes rather than RAND_pseudo_bytes from
24061 OpenSSL. Also, reseed our entropy every hour, not just at
24062 startup. And entropy in 512-bit chunks, not 160-bit chunks.
24064 o Fixes on 0.1.1.7-alpha:
24065 - Nobody ever implemented EVENT_ADDRMAP for control protocol
24066 version 0, so don't let version 0 controllers ask for it.
24067 - If you requested something with too many newlines via the
24068 v1 controller protocol, you could crash tor.
24069 - Fix a number of memory leaks, including some pretty serious ones.
24070 - Re-enable DirPort testing again, so Tor servers will be willing
24071 to advertise their DirPort if it's reachable.
24072 - On TLS handshake, only check the other router's nickname against
24073 its expected nickname if is_named is set.
24075 o Fixes forward-ported from 0.1.0.15:
24076 - Don't crash when we don't have any spare file descriptors and we
24077 try to spawn a dns or cpu worker.
24078 - Make the numbers in read-history and write-history into uint64s,
24079 so they don't overflow and publish negatives in the descriptor.
24081 o Fixes on 0.1.0.x:
24082 - For the OS X package's modified privoxy config file, comment
24083 out the "logfile" line so we don't log everything passed
24085 - We were whining about using socks4 or socks5-with-local-lookup
24086 even when it's an IP in the "virtual" range we designed exactly
24088 - We were leaking some memory every time the client changes IPs.
24089 - Never call free() on tor_malloc()d memory. This will help us
24090 use dmalloc to detect memory leaks.
24091 - Check for named servers when looking them up by nickname;
24092 warn when we'recalling a non-named server by its nickname;
24093 don't warn twice about the same name.
24094 - Try to list MyFamily elements by key, not by nickname, and warn
24095 if we've not heard of the server.
24096 - Make windows platform detection (uname equivalent) smarter.
24097 - It turns out sparc64 doesn't like unaligned access either.
24100 Changes in version 0.1.0.15 - 2005-09-23
24101 o Bugfixes on 0.1.0.x:
24102 - Reject ports 465 and 587 (spam targets) in default exit policy.
24103 - Don't crash when we don't have any spare file descriptors and we
24104 try to spawn a dns or cpu worker.
24105 - Get rid of IgnoreVersion undocumented config option, and make us
24106 only warn, never exit, when we're running an obsolete version.
24107 - Don't try to print a null string when your server finds itself to
24108 be unreachable and the Address config option is empty.
24109 - Make the numbers in read-history and write-history into uint64s,
24110 so they don't overflow and publish negatives in the descriptor.
24111 - Fix a minor memory leak in smartlist_string_remove().
24112 - We were only allowing ourselves to upload a server descriptor at
24113 most every 20 minutes, even if it changed earlier than that.
24114 - Clean up log entries that pointed to old URLs.
24117 Changes in version 0.1.1.7-alpha - 2005-09-14
24118 o Fixes on 0.1.1.6-alpha:
24119 - Exit servers were crashing when people asked them to make a
24120 connection to an address not in their exit policy.
24121 - Looking up a non-existent stream for a v1 control connection would
24123 - Fix a seg fault if we ask a dirserver for a descriptor by
24124 fingerprint but he doesn't know about him.
24125 - SETCONF was appending items to linelists, not clearing them.
24126 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
24127 out and refuse the setconf if it would fail.
24128 - Downgrade the dirserver log messages when whining about
24132 - Add Peter Palfrader's check-tor script to tor/contrib/
24133 It lets you easily check whether a given server (referenced by
24134 nickname) is reachable by you.
24135 - Numerous changes to move towards client-side v2 directories. Not
24138 o Fixes on 0.1.0.x:
24139 - If the user gave tor an odd number of command-line arguments,
24140 we were silently ignoring the last one. Now we complain and fail.
24141 [This wins the oldest-bug prize -- this bug has been present since
24142 November 2002, as released in Tor 0.0.0.]
24143 - Do not use unaligned memory access on alpha, mips, or mipsel.
24144 It *works*, but is very slow, so we treat them as if it doesn't.
24145 - Retry directory requests if we fail to get an answer we like
24146 from a given dirserver (we were retrying before, but only if
24147 we fail to connect).
24148 - When writing the RecommendedVersions line, sort them first.
24149 - When the client asked for a rendezvous port that the hidden
24150 service didn't want to provide, we were sending an IP address
24151 back along with the end cell. Fortunately, it was zero. But stop
24153 - Correct "your server is reachable" log entries to indicate that
24154 it was self-testing that told us so.
24157 Changes in version 0.1.1.6-alpha - 2005-09-09
24158 o Fixes on 0.1.1.5-alpha:
24159 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
24160 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
24161 - Fix bug with tor_memmem finding a match at the end of the string.
24162 - Make unit tests run without segfaulting.
24163 - Resolve some solaris x86 compile warnings.
24164 - Handle duplicate lines in approved-routers files without warning.
24165 - Fix bug where as soon as a server refused any requests due to his
24166 exit policy (e.g. when we ask for localhost and he tells us that's
24167 127.0.0.1 and he won't do it), we decided he wasn't obeying his
24168 exit policy using him for any exits.
24169 - Only do openssl hardware accelerator stuff if openssl version is
24172 o New controller features/fixes:
24173 - Add a "RESETCONF" command so you can set config options like
24174 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
24175 a config option in the torrc with no value, then it clears it
24176 entirely (rather than setting it to its default).
24177 - Add a "GETINFO config-file" to tell us where torrc is.
24178 - Avoid sending blank lines when GETINFO replies should be empty.
24179 - Add a QUIT command for the controller (for using it manually).
24180 - Fix a bug in SAVECONF that was adding default dirservers and
24181 other redundant entries to the torrc file.
24183 o Start on the new directory design:
24184 - Generate, publish, cache, serve new network-status format.
24185 - Publish individual descriptors (by fingerprint, by "all", and by
24187 - Publish client and server recommended versions separately.
24188 - Allow tor_gzip_uncompress() to handle multiple concatenated
24189 compressed strings. Serve compressed groups of router
24190 descriptors. The compression logic here could be more
24192 - Distinguish v1 authorities (all currently trusted directories)
24193 from v2 authorities (all trusted directories).
24194 - Change DirServers config line to note which dirs are v1 authorities.
24195 - Add configuration option "V1AuthoritativeDirectory 1" which
24196 moria1, moria2, and tor26 should set.
24197 - Remove option when getting directory cache to see whether they
24198 support running-routers; they all do now. Replace it with one
24199 to see whether caches support v2 stuff.
24202 - Dirservers now do their own external reachability testing of each
24203 Tor server, and only list them as running if they've been found to
24204 be reachable. We also send back warnings to the server's logs if
24205 it uploads a descriptor that we already believe is unreachable.
24206 - Implement exit enclaves: if we know an IP address for the
24207 destination, and there's a running Tor server at that address
24208 which allows exit to the destination, then extend the circuit to
24209 that exit first. This provides end-to-end encryption and end-to-end
24210 authentication. Also, if the user wants a .exit address or enclave,
24211 use 4 hops rather than 3, and cannibalize a general circ for it
24213 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
24214 controller. Also, rotate dns and cpu workers if the controller
24215 changes options that will affect them; and initialize the dns
24216 worker cache tree whether or not we start out as a server.
24217 - Only upload a new server descriptor when options change, 18
24218 hours have passed, uptime is reset, or bandwidth changes a lot.
24219 - Check [X-]Forwarded-For headers in HTTP requests when generating
24220 log messages. This lets people run dirservers (and caches) behind
24221 Apache but still know which IP addresses are causing warnings.
24223 o Config option changes:
24224 - Replace (Fascist)Firewall* config options with a new
24225 ReachableAddresses option that understands address policies.
24226 For example, "ReachableAddresses *:80,*:443"
24227 - Get rid of IgnoreVersion undocumented config option, and make us
24228 only warn, never exit, when we're running an obsolete version.
24229 - Make MonthlyAccountingStart config option truly obsolete now.
24231 o Fixes on 0.1.0.x:
24232 - Reject ports 465 and 587 in the default exit policy, since
24233 people have started using them for spam too.
24234 - It turns out we couldn't bootstrap a network since we added
24235 reachability detection in 0.1.0.1-rc. Good thing the Tor network
24236 has never gone down. Add an AssumeReachable config option to let
24237 servers and dirservers bootstrap. When we're trying to build a
24238 high-uptime or high-bandwidth circuit but there aren't enough
24239 suitable servers, try being less picky rather than simply failing.
24240 - Our logic to decide if the OR we connected to was the right guy
24241 was brittle and maybe open to a mitm for unverified routers.
24242 - We weren't cannibalizing circuits correctly for
24243 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
24244 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
24245 build those from scratch. This should make hidden services faster.
24246 - Predict required circuits better, with an eye toward making hidden
24247 services faster on the service end.
24248 - Retry streams if the exit node sends back a 'misc' failure. This
24249 should result in fewer random failures. Also, after failing
24250 from resolve failed or misc, reset the num failures, so we give
24251 it a fair shake next time we try.
24252 - Clean up the rendezvous warn log msgs, and downgrade some to info.
24253 - Reduce severity on logs about dns worker spawning and culling.
24254 - When we're shutting down and we do something like try to post a
24255 server descriptor or rendezvous descriptor, don't complain that
24256 we seem to be unreachable. Of course we are, we're shutting down.
24257 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
24258 We don't use them yet, but maybe one day our DNS resolver will be
24259 able to discover them.
24260 - Make ContactInfo mandatory for authoritative directory servers.
24261 - Require server descriptors to list IPv4 addresses -- hostnames
24262 are no longer allowed. This also fixes some potential security
24263 problems with people providing hostnames as their address and then
24264 preferentially resolving them to partition users.
24265 - Change log line for unreachability to explicitly suggest /etc/hosts
24266 as the culprit. Also make it clearer what IP address and ports we're
24267 testing for reachability.
24268 - Put quotes around user-supplied strings when logging so users are
24269 more likely to realize if they add bad characters (like quotes)
24271 - Let auth dir servers start without specifying an Address config
24273 - Make unit tests (and other invocations that aren't the real Tor)
24274 run without launching listeners, creating subdirectories, and so on.
24277 Changes in version 0.1.1.5-alpha - 2005-08-08
24278 o Bugfixes included in 0.1.0.14.
24280 o Bugfixes on 0.1.0.x:
24281 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
24282 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
24283 it would silently using ignore the 6668.
24286 Changes in version 0.1.0.14 - 2005-08-08
24287 o Bugfixes on 0.1.0.x:
24288 - Fix the other half of the bug with crypto handshakes
24290 - Fix an assert trigger if you send a 'signal term' via the
24291 controller when it's listening for 'event info' messages.
24294 Changes in version 0.1.1.4-alpha - 2005-08-04
24295 o Bugfixes included in 0.1.0.13.
24298 - Improve tor_gettimeofday() granularity on windows.
24299 - Make clients regenerate their keys when their IP address changes.
24300 - Implement some more GETINFO goodness: expose helper nodes, config
24301 options, getinfo keys.
24304 Changes in version 0.1.0.13 - 2005-08-04
24305 o Bugfixes on 0.1.0.x:
24306 - Fix a critical bug in the security of our crypto handshakes.
24307 - Fix a size_t underflow in smartlist_join_strings2() that made
24308 it do bad things when you hand it an empty smartlist.
24309 - Fix Windows installer to ship Tor license (thanks to Aphex for
24310 pointing out this oversight) and put a link to the doc directory
24312 - Explicitly set no-unaligned-access for sparc: it turns out the
24313 new gcc's let you compile broken code, but that doesn't make it
24317 Changes in version 0.1.1.3-alpha - 2005-07-23
24318 o Bugfixes on 0.1.1.2-alpha:
24319 - Fix a bug in handling the controller's "post descriptor"
24321 - Fix several bugs in handling the controller's "extend circuit"
24323 - Fix a bug in handling the controller's "stream status" event.
24324 - Fix an assert failure if we have a controller listening for
24325 circuit events and we go offline.
24326 - Re-allow hidden service descriptors to publish 0 intro points.
24327 - Fix a crash when generating your hidden service descriptor if
24328 you don't have enough intro points already.
24330 o New features on 0.1.1.2-alpha:
24331 - New controller function "getinfo accounting", to ask how
24332 many bytes we've used in this time period.
24333 - Experimental support for helper nodes: a lot of the risk from
24334 a small static adversary comes because users pick new random
24335 nodes every time they rebuild a circuit. Now users will try to
24336 stick to the same small set of entry nodes if they can. Not
24337 enabled by default yet.
24339 o Bugfixes on 0.1.0.12:
24340 - If you're an auth dir server, always publish your dirport,
24341 even if you haven't yet found yourself to be reachable.
24342 - Fix a size_t underflow in smartlist_join_strings2() that made
24343 it do bad things when you hand it an empty smartlist.
24346 Changes in version 0.1.0.12 - 2005-07-18
24347 o New directory servers:
24348 - tor26 has changed IP address.
24350 o Bugfixes on 0.1.0.x:
24351 - Fix a possible double-free in tor_gzip_uncompress().
24352 - When --disable-threads is set, do not search for or link against
24353 pthreads libraries.
24354 - Don't trigger an assert if an authoritative directory server
24355 claims its dirport is 0.
24356 - Fix bug with removing Tor as an NT service: some people were
24357 getting "The service did not return an error." Thanks to Matt
24361 Changes in version 0.1.1.2-alpha - 2005-07-15
24362 o New directory servers:
24363 - tor26 has changed IP address.
24365 o Bugfixes on 0.1.0.x, crashes/leaks:
24366 - Port the servers-not-obeying-their-exit-policies fix from
24368 - Fix an fd leak in start_daemon().
24369 - On Windows, you can't always reopen a port right after you've
24370 closed it. So change retry_listeners() to only close and re-open
24371 ports that have changed.
24372 - Fix a possible double-free in tor_gzip_uncompress().
24374 o Bugfixes on 0.1.0.x, usability:
24375 - When tor_socketpair() fails in Windows, give a reasonable
24376 Windows-style errno back.
24377 - Let people type "tor --install" as well as "tor -install" when
24379 want to make it an NT service.
24380 - NT service patch from Matt Edman to improve error messages.
24381 - When the controller asks for a config option with an abbreviated
24382 name, give the full name in our response.
24383 - Correct the man page entry on TrackHostExitsExpire.
24384 - Looks like we were never delivering deflated (i.e. compressed)
24385 running-routers lists, even when asked. Oops.
24386 - When --disable-threads is set, do not search for or link against
24387 pthreads libraries.
24389 o Bugfixes on 0.1.1.x:
24390 - Fix a seg fault with autodetecting which controller version is
24394 - New hidden service descriptor format: put a version in it, and
24395 let people specify introduction/rendezvous points that aren't
24396 in "the directory" (which is subjective anyway).
24397 - Allow the DEBUG controller event to work again. Mark certain log
24398 entries as "don't tell this to controllers", so we avoid cycles.
24401 Changes in version 0.1.0.11 - 2005-06-30
24402 o Bugfixes on 0.1.0.x:
24403 - Fix major security bug: servers were disregarding their
24404 exit policies if clients behaved unexpectedly.
24405 - Make OS X init script check for missing argument, so we don't
24406 confuse users who invoke it incorrectly.
24407 - Fix a seg fault in "tor --hash-password foo".
24408 - The MAPADDRESS control command was broken.
24411 Changes in version 0.1.1.1-alpha - 2005-06-29
24413 - Make OS X init script check for missing argument, so we don't
24414 confuse users who invoke it incorrectly.
24415 - Fix a seg fault in "tor --hash-password foo".
24416 - Fix a possible way to DoS dirservers.
24417 - When we complain that your exit policy implicitly allows local or
24418 private address spaces, name them explicitly so operators can
24420 - Make the log message less scary when all the dirservers are
24421 temporarily unreachable.
24422 - We were printing the number of idle dns workers incorrectly when
24426 - Revised controller protocol (version 1) that uses ascii rather
24427 than binary. Add supporting libraries in python and java so you
24428 can use the controller from your applications without caring how
24429 our protocol works.
24430 - Spiffy new support for crypto hardware accelerators. Can somebody
24434 Changes in version 0.0.9.10 - 2005-06-16
24435 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
24436 - Refuse relay cells that claim to have a length larger than the
24437 maximum allowed. This prevents a potential attack that could read
24438 arbitrary memory (e.g. keys) from an exit server's process
24442 Changes in version 0.1.0.10 - 2005-06-14
24443 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
24444 libevent before 1.1a.
24447 Changes in version 0.1.0.9-rc - 2005-06-09
24449 - Reset buf->highwater every time buf_shrink() is called, not just on
24450 a successful shrink. This was causing significant memory bloat.
24451 - Fix buffer overflow when checking hashed passwords.
24452 - Security fix: if seeding the RNG on Win32 fails, quit.
24453 - Allow seeding the RNG on Win32 even when you're not running as
24455 - Disable threading on Solaris too. Something is wonky with it,
24456 cpuworkers, and reentrant libs.
24457 - Reenable the part of the code that tries to flush as soon as an
24458 OR outbuf has a full TLS record available. Perhaps this will make
24459 OR outbufs not grow as huge except in rare cases, thus saving lots
24460 of CPU time plus memory.
24461 - Reject malformed .onion addresses rather then passing them on as
24462 normal web requests.
24463 - Adapt patch from Adam Langley: fix possible memory leak in
24464 tor_lookup_hostname().
24465 - Initialize libevent later in the startup process, so the logs are
24466 already established by the time we start logging libevent warns.
24467 - Use correct errno on win32 if libevent fails.
24468 - Check and warn about known-bad/slow libevent versions.
24469 - Pay more attention to the ClientOnly config option.
24470 - Have torctl.in/tor.sh.in check for location of su binary (needed
24472 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
24473 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
24474 HttpProxyAuthenticator
24475 - Stop warning about sigpipes in the logs. We're going to
24476 pretend that getting these occassionally is normal and fine.
24477 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
24479 installer screens; and don't put stuff into StartupItems unless
24480 the user asks you to.
24481 - Require servers that use the default dirservers to have public IP
24482 addresses. We have too many servers that are configured with private
24483 IPs and their admins never notice the log entries complaining that
24484 their descriptors are being rejected.
24485 - Add OSX uninstall instructions. An actual uninstall script will
24489 Changes in version 0.1.0.8-rc - 2005-05-23
24491 - It turns out that kqueue on OS X 10.3.9 was causing kernel
24492 panics. Disable kqueue on all OS X Tors.
24493 - Fix RPM: remove duplicate line accidentally added to the rpm
24495 - Disable threads on openbsd too, since its gethostaddr is not
24497 - Tolerate libevent 0.8 since it still works, even though it's
24499 - Enable building on Red Hat 9.0 again.
24500 - Allow the middle hop of the testing circuit to be running any
24501 version, now that most of them have the bugfix to let them connect
24502 to unknown servers. This will allow reachability testing to work
24503 even when 0.0.9.7-0.0.9.9 become obsolete.
24504 - Handle relay cells with rh.length too large. This prevents
24505 a potential attack that could read arbitrary memory (maybe even
24506 keys) from the exit server's process.
24507 - We screwed up the dirport reachability testing when we don't yet
24508 have a cached version of the directory. Hopefully now fixed.
24509 - Clean up router_load_single_router() (used by the controller),
24510 so it doesn't seg fault on error.
24511 - Fix a minor memory leak when somebody establishes an introduction
24512 point at your Tor server.
24513 - If a socks connection ends because read fails, don't warn that
24514 you're not sending a socks reply back.
24517 - Add HttpProxyAuthenticator config option too, that works like
24518 the HttpsProxyAuthenticator config option.
24519 - Encode hashed controller passwords in hex instead of base64,
24520 to make it easier to write controllers.
24523 Changes in version 0.1.0.7-rc - 2005-05-17
24525 - Fix a bug in the OS X package installer that prevented it from
24526 installing on Tiger.
24527 - Fix a script bug in the OS X package installer that made it
24528 complain during installation.
24529 - Find libevent even if it's hiding in /usr/local/ and your
24530 CFLAGS and LDFLAGS don't tell you to look there.
24531 - Be able to link with libevent as a shared library (the default
24532 after 1.0d), even if it's hiding in /usr/local/lib and even
24533 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
24534 assuming you're running gcc. Otherwise fail and give a useful
24536 - Fix a bug in the RPM packager: set home directory for _tor to
24537 something more reasonable when first installing.
24538 - Free a minor amount of memory that is still reachable on exit.
24541 Changes in version 0.1.0.6-rc - 2005-05-14
24543 - Implement --disable-threads configure option. Disable threads on
24544 netbsd by default, because it appears to have no reentrant resolver
24546 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
24547 release (1.1) detects and disables kqueue if it's broken.
24548 - Append default exit policy before checking for implicit internal
24549 addresses. Now we don't log a bunch of complaints on startup
24550 when using the default exit policy.
24551 - Some people were putting "Address " in their torrc, and they had
24552 a buggy resolver that resolved " " to 0.0.0.0. Oops.
24553 - If DataDir is ~/.tor, and that expands to /.tor, then default to
24554 LOCALSTATEDIR/tor instead.
24555 - Fix fragmented-message bug in TorControl.py.
24556 - Resolve a minor bug which would prevent unreachable dirports
24557 from getting suppressed in the published descriptor.
24558 - When the controller gave us a new descriptor, we weren't resolving
24559 it immediately, so Tor would think its address was 0.0.0.0 until
24560 we fetched a new directory.
24561 - Fix an uppercase/lowercase case error in suppressing a bogus
24562 libevent warning on some Linuxes.
24565 - Begin scrubbing sensitive strings from logs by default. Turn off
24566 the config option SafeLogging if you need to do debugging.
24567 - Switch to a new buffer management algorithm, which tries to avoid
24568 reallocing and copying quite as much. In first tests it looks like
24569 it uses *more* memory on average, but less cpu.
24570 - First cut at support for "create-fast" cells. Clients can use
24571 these when extending to their first hop, since the TLS already
24572 provides forward secrecy and authentication. Not enabled on
24574 - When dirservers refuse a router descriptor, we now log its
24575 contactinfo, platform, and the poster's IP address.
24576 - Call tor_free_all instead of connections_free_all after forking, to
24577 save memory on systems that need to fork.
24578 - Whine at you if you're a server and you don't set your contactinfo.
24579 - Implement --verify-config command-line option to check if your torrc
24580 is valid without actually launching Tor.
24581 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
24582 rather than just rejecting it.
24585 Changes in version 0.1.0.5-rc - 2005-04-27
24587 - Stop trying to print a null pointer if an OR conn fails because
24588 we didn't like its cert.
24590 - Switch our internal buffers implementation to use a ring buffer,
24591 to hopefully improve performance for fast servers a lot.
24592 - Add HttpsProxyAuthenticator support (basic auth only), based
24593 on patch from Adam Langley.
24594 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
24595 the fast servers that have been joining lately.
24596 - Give hidden service accesses extra time on the first attempt,
24597 since 60 seconds is often only barely enough. This might improve
24599 - Improve performance for dirservers: stop re-parsing the whole
24600 directory every time you regenerate it.
24601 - Add more debugging info to help us find the weird dns freebsd
24602 pthreads bug; cleaner debug messages to help track future issues.
24605 Changes in version 0.0.9.9 - 2005-04-23
24606 o Bugfixes on 0.0.9.x:
24607 - If unofficial Tor clients connect and send weird TLS certs, our
24608 Tor server triggers an assert. This release contains a minimal
24609 backport from the broader fix that we put into 0.1.0.4-rc.
24612 Changes in version 0.1.0.4-rc - 2005-04-23
24614 - If unofficial Tor clients connect and send weird TLS certs, our
24615 Tor server triggers an assert. Stop asserting, and start handling
24616 TLS errors better in other situations too.
24617 - When the controller asks us to tell it about all the debug-level
24618 logs, it turns out we were generating debug-level logs while
24619 telling it about them, which turns into a bad loop. Now keep
24620 track of whether you're sending a debug log to the controller,
24621 and don't log when you are.
24622 - Fix the "postdescriptor" feature of the controller interface: on
24623 non-complete success, only say "done" once.
24625 - Clients are now willing to load balance over up to 2mB, not 1mB,
24626 of advertised bandwidth capacity.
24627 - Add a NoPublish config option, so you can be a server (e.g. for
24628 testing running Tor servers in other Tor networks) without
24629 publishing your descriptor to the primary dirservers.
24632 Changes in version 0.1.0.3-rc - 2005-04-08
24633 o Improvements on 0.1.0.2-rc:
24634 - Client now retries when streams end early for 'hibernating' or
24635 'resource limit' reasons, rather than failing them.
24636 - More automated handling for dirserver operators:
24637 - Automatically approve nodes running 0.1.0.2-rc or later,
24638 now that the the reachability detection stuff is working.
24639 - Now we allow two unverified servers with the same nickname
24640 but different keys. But if a nickname is verified, only that
24641 nickname+key are allowed.
24642 - If you're an authdirserver connecting to an address:port,
24643 and it's not the OR you were expecting, forget about that
24644 descriptor. If he *was* the one you were expecting, then forget
24645 about all other descriptors for that address:port.
24646 - Allow servers to publish descriptors from 12 hours in the future.
24647 Corollary: only whine about clock skew from the dirserver if
24648 he's a trusted dirserver (since now even verified servers could
24649 have quite wrong clocks).
24650 - Adjust maximum skew and age for rendezvous descriptors: let skew
24651 be 48 hours rather than 90 minutes.
24652 - Efficiency improvements:
24653 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
24654 it much faster to look up a circuit for each relay cell.
24655 - Remove most calls to assert_all_pending_dns_resolves_ok(),
24656 since they're eating our cpu on exit nodes.
24657 - Stop wasting time doing a case insensitive comparison for every
24658 dns name every time we do any lookup. Canonicalize the names to
24659 lowercase and be done with it.
24660 - Start sending 'truncated' cells back rather than destroy cells,
24661 if the circuit closes in front of you. This means we won't have
24662 to abandon partially built circuits.
24663 - Only warn once per nickname from add_nickname_list_to_smartlist
24664 per failure, so an entrynode or exitnode choice that's down won't
24666 - Put a note in the torrc about abuse potential with the default
24668 - Revise control spec and implementation to allow all log messages to
24669 be sent to controller with their severities intact (suggested by
24670 Matt Edman). Update TorControl to handle new log event types.
24671 - Provide better explanation messages when controller's POSTDESCRIPTOR
24673 - Stop putting nodename in the Platform string in server descriptors.
24674 It doesn't actually help, and it is confusing/upsetting some people.
24676 o Bugfixes on 0.1.0.2-rc:
24677 - We were printing the host mask wrong in exit policies in server
24678 descriptors. This isn't a critical bug though, since we were still
24679 obeying the exit policy internally.
24680 - Fix Tor when compiled with libevent but without pthreads: move
24681 connection_unregister() from _connection_free() to
24683 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
24684 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
24685 when we look through the connection array, we'll find any of the
24686 cpu/dnsworkers. This is no good.
24688 o Bugfixes on 0.0.9.8:
24689 - Fix possible bug on threading platforms (e.g. win32) which was
24690 leaking a file descriptor whenever a cpuworker or dnsworker died.
24691 - When using preferred entry or exit nodes, ignore whether the
24692 circuit wants uptime or capacity. They asked for the nodes, they
24694 - chdir() to your datadirectory at the *end* of the daemonize process,
24695 not the beginning. This was a problem because the first time you
24696 run tor, if your datadir isn't there, and you have runasdaemon set
24697 to 1, it will try to chdir to it before it tries to create it. Oops.
24698 - Handle changed router status correctly when dirserver reloads
24699 fingerprint file. We used to be dropping all unverified descriptors
24700 right then. The bug was hidden because we would immediately
24701 fetch a directory from another dirserver, which would include the
24702 descriptors we just dropped.
24703 - When we're connecting to an OR and he's got a different nickname/key
24704 than we were expecting, only complain loudly if we're an OP or a
24705 dirserver. Complaining loudly to the OR admins just confuses them.
24706 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
24707 artificially capped at 500kB.
24710 Changes in version 0.0.9.8 - 2005-04-07
24711 o Bugfixes on 0.0.9.x:
24712 - We have a bug that I haven't found yet. Sometimes, very rarely,
24713 cpuworkers get stuck in the 'busy' state, even though the cpuworker
24714 thinks of itself as idle. This meant that no new circuits ever got
24715 established. Here's a workaround to kill any cpuworker that's been
24716 busy for more than 100 seconds.
24719 Changes in version 0.1.0.2-rc - 2005-04-01
24720 o Bugfixes on 0.1.0.1-rc:
24721 - Fixes on reachability detection:
24722 - Don't check for reachability while hibernating.
24723 - If ORPort is reachable but DirPort isn't, still publish the
24724 descriptor, but zero out DirPort until it's found reachable.
24725 - When building testing circs for ORPort testing, use only
24726 high-bandwidth nodes, so fewer circuits fail.
24727 - Complain about unreachable ORPort separately from unreachable
24728 DirPort, so the user knows what's going on.
24729 - Make sure we only conclude ORPort reachability if we didn't
24730 initiate the conn. Otherwise we could falsely conclude that
24731 we're reachable just because we connected to the guy earlier
24732 and he used that same pipe to extend to us.
24733 - Authdirservers shouldn't do ORPort reachability detection,
24734 since they're in clique mode, so it will be rare to find a
24735 server not already connected to them.
24736 - When building testing circuits, always pick middle hops running
24737 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
24738 bug. (This is a kludge; it will go away when 0.0.9.x becomes
24740 - When we decide we're reachable, actually publish our descriptor
24742 - Fix bug in redirectstream in the controller.
24743 - Fix the state descriptor strings so logs don't claim edge streams
24744 are in a different state than they actually are.
24745 - Use recent libevent features when possible (this only really affects
24746 win32 and osx right now, because the new libevent with these
24747 features hasn't been released yet). Add code to suppress spurious
24749 - Prevent possible segfault in connection_close_unattached_ap().
24750 - Fix newlines on torrc in win32.
24751 - Improve error msgs when tor-resolve fails.
24753 o Improvements on 0.0.9.x:
24754 - New experimental script tor/contrib/ExerciseServer.py (needs more
24755 work) that uses the controller interface to build circuits and
24756 fetch pages over them. This will help us bootstrap servers that
24757 have lots of capacity but haven't noticed it yet.
24758 - New experimental script tor/contrib/PathDemo.py (needs more work)
24759 that uses the controller interface to let you choose whole paths
24761 "<hostname>.<path,separated by dots>.<length of path>.path"
24762 - When we've connected to an OR and handshaked but didn't like
24763 the result, we were closing the conn without sending destroy
24764 cells back for pending circuits. Now send those destroys.
24767 Changes in version 0.0.9.7 - 2005-04-01
24768 o Bugfixes on 0.0.9.x:
24769 - Fix another race crash bug (thanks to Glenn Fink for reporting).
24770 - Compare identity to identity, not to nickname, when extending to
24771 a router not already in the directory. This was preventing us from
24772 extending to unknown routers. Oops.
24773 - Make sure to create OS X Tor user in <500 range, so we aren't
24774 creating actual system users.
24775 - Note where connection-that-hasn't-sent-end was marked, and fix
24776 a few really loud instances of this harmless bug (it's fixed more
24780 Changes in version 0.1.0.1-rc - 2005-03-28
24782 - Add reachability testing. Your Tor server will automatically try
24783 to see if its ORPort and DirPort are reachable from the outside,
24784 and it won't upload its descriptor until it decides they are.
24785 - Handle unavailable hidden services better. Handle slow or busy
24786 hidden services better.
24787 - Add support for CONNECTing through https proxies, with "HttpsProxy"
24789 - New exit policy: accept most low-numbered ports, rather than
24790 rejecting most low-numbered ports.
24791 - More Tor controller support (still experimental). See
24792 http://tor.eff.org/doc/control-spec.txt for all the new features,
24793 including signals to emulate unix signals from any platform;
24794 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
24795 closestream; closecircuit; etc.
24796 - Make nt services work and start on startup on win32 (based on
24797 patch by Matt Edman).
24798 - Add a new AddressMap config directive to rewrite incoming socks
24799 addresses. This lets you, for example, declare an implicit
24800 required exit node for certain sites.
24801 - Add a new TrackHostExits config directive to trigger addressmaps
24802 for certain incoming socks addresses -- for sites that break when
24803 your exit keeps changing (based on patch by Mike Perry).
24804 - Redo the client-side dns cache so it's just an addressmap too.
24805 - Notice when our IP changes, and reset stats/uptime/reachability.
24806 - When an application is using socks5, give him the whole variety of
24807 potential socks5 responses (connect refused, host unreachable, etc),
24808 rather than just "success" or "failure".
24809 - A more sane version numbering system. See
24810 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
24811 - New contributed script "exitlist": a simple python script to
24812 parse directories and find Tor nodes that exit to listed
24814 - New contributed script "privoxy-tor-toggle" to toggle whether
24815 Privoxy uses Tor. Seems to be configured for Debian by default.
24816 - Report HTTP reasons to client when getting a response from directory
24817 servers -- so you can actually know what went wrong.
24818 - New config option MaxAdvertisedBandwidth which lets you advertise
24819 a low bandwidthrate (to not attract as many circuits) while still
24820 allowing a higher bandwidthrate in reality.
24822 o Robustness/stability fixes:
24823 - Make Tor use Niels Provos's libevent instead of its current
24824 poll-but-sometimes-select mess. This will let us use faster async
24825 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
24827 - pthread support now too. This was forced because when we forked,
24828 we ended up wasting a lot of duplicate ram over time. Also switch
24829 to foo_r versions of some library calls to allow reentry and
24831 - Better handling for heterogeneous / unreliable nodes:
24832 - Annotate circuits w/ whether they aim to contain high uptime nodes
24833 and/or high capacity nodes. When building circuits, choose
24835 - This means that every single node in an intro rend circuit,
24836 not just the last one, will have a minimum uptime.
24837 - New config option LongLivedPorts to indicate application streams
24838 that will want high uptime circuits.
24839 - Servers reset uptime when a dir fetch entirely fails. This
24840 hopefully reflects stability of the server's network connectivity.
24841 - If somebody starts his tor server in Jan 2004 and then fixes his
24842 clock, don't make his published uptime be a year.
24843 - Reset published uptime when you wake up from hibernation.
24844 - Introduce a notion of 'internal' circs, which are chosen without
24845 regard to the exit policy of the last hop. Intro and rendezvous
24846 circs must be internal circs, to avoid leaking information. Resolve
24847 and connect streams can use internal circs if they want.
24848 - New circuit pooling algorithm: make sure to have enough circs around
24849 to satisfy any predicted ports, and also make sure to have 2 internal
24850 circs around if we've required internal circs lately (and with high
24851 uptime if we've seen that lately too).
24852 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
24853 which describes how often we retry making new circuits if current
24854 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
24855 how long we're willing to make use of an already-dirty circuit.
24856 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
24857 circ as necessary, if there are any completed ones lying around
24858 when we try to launch one.
24859 - Make hidden services try to establish a rendezvous for 30 seconds,
24860 rather than for n (where n=3) attempts to build a circuit.
24861 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
24862 "ShutdownWaitLength".
24863 - Try to be more zealous about calling connection_edge_end when
24864 things go bad with edge conns in connection.c.
24865 - Revise tor-spec to add more/better stream end reasons.
24866 - Revise all calls to connection_edge_end to avoid sending "misc",
24867 and to take errno into account where possible.
24870 - Fix a race condition that can trigger an assert, when we have a
24871 pending create cell and an OR connection fails right then.
24872 - Fix several double-mark-for-close bugs, e.g. where we were finding
24873 a conn for a cell even if that conn is already marked for close.
24874 - Make sequence of log messages when starting on win32 with no config
24875 file more reasonable.
24876 - When choosing an exit node for a new non-internal circ, don't take
24877 into account whether it'll be useful for any pending x.onion
24878 addresses -- it won't.
24879 - Turn addr_policy_compare from a tristate to a quadstate; this should
24880 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
24881 for google.com" problem.
24882 - Make "platform" string in descriptor more accurate for Win32 servers,
24883 so it's not just "unknown platform".
24884 - Fix an edge case in parsing config options (thanks weasel).
24885 If they say "--" on the commandline, it's not an option.
24886 - Reject odd-looking addresses at the client (e.g. addresses that
24887 contain a colon), rather than having the server drop them because
24889 - tor-resolve requests were ignoring .exit if there was a working circuit
24890 they could use instead.
24891 - REUSEADDR on normal platforms means you can rebind to the port
24892 right after somebody else has let it go. But REUSEADDR on win32
24893 means to let you bind to the port _even when somebody else
24894 already has it bound_! So, don't do that on Win32.
24895 - Change version parsing logic: a version is "obsolete" if it is not
24896 recommended and (1) there is a newer recommended version in the
24897 same series, or (2) there are no recommended versions in the same
24898 series, but there are some recommended versions in a newer series.
24899 A version is "new" if it is newer than any recommended version in
24901 - Stop most cases of hanging up on a socks connection without sending
24905 - Require BandwidthRate to be at least 20kB/s for servers.
24906 - When a dirserver causes you to give a warn, mention which dirserver
24908 - New config option DirAllowPrivateAddresses for authdirservers.
24909 Now by default they refuse router descriptors that have non-IP or
24910 private-IP addresses.
24911 - Stop publishing socksport in the directory, since it's not
24912 actually meant to be public. For compatibility, publish a 0 there
24914 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
24915 smart" value, that is low for servers and high for clients.
24916 - If our clock jumps forward by 100 seconds or more, assume something
24917 has gone wrong with our network and abandon all not-yet-used circs.
24918 - Warn when exit policy implicitly allows local addresses.
24919 - If we get an incredibly skewed timestamp from a dirserver mirror
24920 that isn't a verified OR, don't warn -- it's probably him that's
24922 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
24923 cookies to disk and doesn't log each web request to disk. (Thanks
24924 to Brett Carrington for pointing this out.)
24925 - When a client asks us for a dir mirror and we don't have one,
24926 launch an attempt to get a fresh one.
24927 - If we're hibernating and we get a SIGINT, exit immediately.
24928 - Add --with-dmalloc ./configure option, to track memory leaks.
24929 - And try to free all memory on closing, so we can detect what
24931 - Cache local dns resolves correctly even when they're .exit
24933 - Give a better warning when some other server advertises an
24934 ORPort that is actually an apache running ssl.
24935 - Add "opt hibernating 1" to server descriptor to make it clearer
24936 whether the server is hibernating.
24939 Changes in version 0.0.9.6 - 2005-03-24
24940 o Bugfixes on 0.0.9.x (crashes and asserts):
24941 - Add new end stream reasons to maintainance branch. Fix bug where
24942 reason (8) could trigger an assert. Prevent bug from recurring.
24943 - Apparently win32 stat wants paths to not end with a slash.
24944 - Fix assert triggers in assert_cpath_layer_ok(), where we were
24945 blowing away the circuit that conn->cpath_layer points to, then
24946 checking to see if the circ is well-formed. Backport check to make
24947 sure we dont use the cpath on a closed connection.
24948 - Prevent circuit_resume_edge_reading_helper() from trying to package
24949 inbufs for marked-for-close streams.
24950 - Don't crash on hup if your options->address has become unresolvable.
24951 - Some systems (like OS X) sometimes accept() a connection and tell
24952 you the remote host is 0.0.0.0:0. If this happens, due to some
24953 other mis-features, we get confused; so refuse the conn for now.
24955 o Bugfixes on 0.0.9.x (other):
24956 - Fix harmless but scary "Unrecognized content encoding" warn message.
24957 - Add new stream error reason: TORPROTOCOL reason means "you are not
24958 speaking a version of Tor I understand; say bye-bye to your stream."
24959 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
24960 into the future, now that we are more tolerant of skew. This
24961 resolves a bug where a Tor server would refuse to cache a directory
24962 because all the directories it gets are too far in the future;
24963 yet the Tor server never logs any complaints about clock skew.
24964 - Mac packaging magic: make man pages useable, and do not overwrite
24965 existing torrc files.
24966 - Make OS X log happily to /var/log/tor/tor.log
24969 Changes in version 0.0.9.5 - 2005-02-22
24970 o Bugfixes on 0.0.9.x:
24971 - Fix an assert race at exit nodes when resolve requests fail.
24972 - Stop picking unverified dir mirrors--it only leads to misery.
24973 - Patch from Matt Edman to make NT services work better. Service
24974 support is still not compiled into the executable by default.
24975 - Patch from Dmitri Bely so the Tor service runs better under
24976 the win32 SYSTEM account.
24977 - Make tor-resolve actually work (?) on Win32.
24978 - Fix a sign bug when getrlimit claims to have 4+ billion
24979 file descriptors available.
24980 - Stop refusing to start when bandwidthburst == bandwidthrate.
24981 - When create cells have been on the onion queue more than five
24982 seconds, just send back a destroy and take them off the list.
24985 Changes in version 0.0.9.4 - 2005-02-03
24986 o Bugfixes on 0.0.9:
24987 - Fix an assert bug that took down most of our servers: when
24988 a server claims to have 1 GB of bandwidthburst, don't
24990 - Don't crash as badly if we have spawned the max allowed number
24991 of dnsworkers, or we're out of file descriptors.
24992 - Block more file-sharing ports in the default exit policy.
24993 - MaxConn is now automatically set to the hard limit of max
24994 file descriptors we're allowed (ulimit -n), minus a few for
24996 - Give a clearer message when servers need to raise their
24997 ulimit -n when they start running out of file descriptors.
24998 - SGI Compatibility patches from Jan Schaumann.
24999 - Tolerate a corrupt cached directory better.
25000 - When a dirserver hasn't approved your server, list which one.
25001 - Go into soft hibernation after 95% of the bandwidth is used,
25002 not 99%. This is especially important for daily hibernators who
25003 have a small accounting max. Hopefully it will result in fewer
25004 cut connections when the hard hibernation starts.
25005 - Load-balance better when using servers that claim more than
25006 800kB/s of capacity.
25007 - Make NT services work (experimental, only used if compiled in).
25010 Changes in version 0.0.9.3 - 2005-01-21
25011 o Bugfixes on 0.0.9:
25012 - Backport the cpu use fixes from main branch, so busy servers won't
25013 need as much processor time.
25014 - Work better when we go offline and then come back, or when we
25015 run Tor at boot before the network is up. We do this by
25016 optimistically trying to fetch a new directory whenever an
25017 application request comes in and we think we're offline -- the
25018 human is hopefully a good measure of when the network is back.
25019 - Backport some minimal hidserv bugfixes: keep rend circuits open as
25020 long as you keep using them; actually publish hidserv descriptors
25021 shortly after they change, rather than waiting 20-40 minutes.
25022 - Enable Mac startup script by default.
25023 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
25024 - When you update AllowUnverifiedNodes or FirewallPorts via the
25025 controller's setconf feature, we were always appending, never
25027 - When you update HiddenServiceDir via setconf, it was screwing up
25028 the order of reading the lines, making it fail.
25029 - Do not rewrite a cached directory back to the cache; otherwise we
25030 will think it is recent and not fetch a newer one on startup.
25031 - Workaround for webservers that lie about Content-Encoding: Tor
25032 now tries to autodetect compressed directories and compression
25033 itself. This lets us Proxypass dir fetches through apache.
25036 Changes in version 0.0.9.2 - 2005-01-04
25037 o Bugfixes on 0.0.9 (crashes and asserts):
25038 - Fix an assert on startup when the disk is full and you're logging
25040 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
25041 style address, then we'd crash.
25042 - Fix an assert trigger when the running-routers string we get from
25043 a dirserver is broken.
25044 - Make worker threads start and run on win32. Now win32 servers
25046 - Bandaid (not actually fix, but now it doesn't crash) an assert
25047 where the dns worker dies mysteriously and the main Tor process
25048 doesn't remember anything about the address it was resolving.
25050 o Bugfixes on 0.0.9 (Win32):
25051 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
25052 name out of the warning/assert messages.
25053 - Fix a superficial "unhandled error on read" bug on win32.
25054 - The win32 installer no longer requires a click-through for our
25055 license, since our Free Software license grants rights but does not
25057 - Win32: When connecting to a dirserver fails, try another one
25058 immediately. (This was already working for non-win32 Tors.)
25059 - Stop trying to parse $HOME on win32 when hunting for default
25061 - Make tor-resolve.c work on win32 by calling network_init().
25063 o Bugfixes on 0.0.9 (other):
25064 - Make 0.0.9.x build on Solaris again.
25065 - Due to a fencepost error, we were blowing away the \n when reporting
25066 confvalue items in the controller. So asking for multiple config
25067 values at once couldn't work.
25068 - When listing circuits that are pending on an opening OR connection,
25069 if we're an OR we were listing circuits that *end* at us as
25070 being pending on every listener, dns/cpu worker, etc. Stop that.
25071 - Dirservers were failing to create 'running-routers' or 'directory'
25072 strings if we had more than some threshold of routers. Fix them so
25073 they can handle any number of routers.
25074 - Fix a superficial "Duplicate mark for close" bug.
25075 - Stop checking for clock skew for OR connections, even for servers.
25076 - Fix a fencepost error that was chopping off the last letter of any
25077 nickname that is the maximum allowed nickname length.
25078 - Update URLs in log messages so they point to the new website.
25079 - Fix a potential problem in mangling server private keys while
25080 writing to disk (not triggered yet, as far as we know).
25081 - Include the licenses for other free software we include in Tor,
25082 now that we're shipping binary distributions more regularly.
25085 Changes in version 0.0.9.1 - 2004-12-15
25086 o Bugfixes on 0.0.9:
25087 - Make hibernation actually work.
25088 - Make HashedControlPassword config option work.
25089 - When we're reporting event circuit status to a controller,
25090 don't use the stream status code.
25093 Changes in version 0.0.9 - 2004-12-12
25095 - Clean up manpage and torrc.sample file.
25096 - Clean up severities and text of log warnings.
25098 - Make servers trigger an assert when they enter hibernation.
25101 Changes in version 0.0.9rc7 - 2004-12-08
25102 o Bugfixes on 0.0.9rc:
25103 - Fix a stack-trashing crash when an exit node begins hibernating.
25104 - Avoid looking at unallocated memory while considering which
25105 ports we need to build circuits to cover.
25106 - Stop a sigpipe: when an 'end' cell races with eof from the app,
25107 we shouldn't hold-open-until-flush if the eof arrived first.
25108 - Fix a bug with init_cookie_authentication() in the controller.
25109 - When recommending new-format log lines, if the upper bound is
25110 LOG_ERR, leave it implicit.
25112 o Bugfixes on 0.0.8.1:
25113 - Fix a whole slew of memory leaks.
25114 - Fix isspace() and friends so they still make Solaris happy
25115 but also so they don't trigger asserts on win32.
25116 - Fix parse_iso_time on platforms without strptime (eg win32).
25117 - win32: tolerate extra "readable" events better.
25118 - win32: when being multithreaded, leave parent fdarray open.
25119 - Make unit tests work on win32.
25122 Changes in version 0.0.9rc6 - 2004-12-06
25123 o Bugfixes on 0.0.9pre:
25124 - Clean up some more integer underflow opportunities (not exploitable
25126 - While hibernating, hup should not regrow our listeners.
25127 - Send an end to the streams we close when we hibernate, rather
25128 than just chopping them off.
25129 - React to eof immediately on non-open edge connections.
25131 o Bugfixes on 0.0.8.1:
25132 - Calculate timeout for waiting for a connected cell from the time
25133 we sent the begin cell, not from the time the stream started. If
25134 it took a long time to establish the circuit, we would time out
25135 right after sending the begin cell.
25136 - Fix router_compare_addr_to_addr_policy: it was not treating a port
25137 of * as always matching, so we were picking reject *:* nodes as
25138 exit nodes too. Oops.
25141 - New circuit building strategy: keep a list of ports that we've
25142 used in the past 6 hours, and always try to have 2 circuits open
25143 or on the way that will handle each such port. Seed us with port
25144 80 so web users won't complain that Tor is "slow to start up".
25145 - Make kill -USR1 dump more useful stats about circuits.
25146 - When warning about retrying or giving up, print the address, so
25147 the user knows which one it's talking about.
25148 - If you haven't used a clean circuit in an hour, throw it away,
25149 just to be on the safe side. (This means after 6 hours a totally
25150 unused Tor client will have no circuits open.)
25153 Changes in version 0.0.9rc5 - 2004-12-01
25154 o Bugfixes on 0.0.8.1:
25155 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
25156 - Let resolve conns retry/expire also, rather than sticking around
25158 - If we are using select, make sure we stay within FD_SETSIZE.
25160 o Bugfixes on 0.0.9pre:
25161 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
25162 but doesn't seem to be currently; thanks to Ilja van Sprundel for
25164 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
25165 instead. Impose minima and maxima for all *Period options; impose
25166 even tighter maxima for fetching if we are a caching dirserver.
25167 Clip rather than rejecting.
25168 - Fetch cached running-routers from servers that serve it (that is,
25169 authdirservers and servers running 0.0.9rc5-cvs or later.)
25172 - Accept *:706 (silc) in default exit policy.
25173 - Implement new versioning format for post 0.1.
25174 - Support "foo.nickname.exit" addresses, to let Alice request the
25175 address "foo" as viewed by exit node "nickname". Based on a patch
25177 - Make tor --version --version dump the cvs Id of every file.
25180 Changes in version 0.0.9rc4 - 2004-11-28
25181 o Bugfixes on 0.0.8.1:
25182 - Make windows sockets actually non-blocking (oops), and handle
25183 win32 socket errors better.
25185 o Bugfixes on 0.0.9rc1:
25186 - Actually catch the -USR2 signal.
25189 Changes in version 0.0.9rc3 - 2004-11-25
25190 o Bugfixes on 0.0.8.1:
25191 - Flush the log file descriptor after we print "Tor opening log file",
25192 so we don't see those messages days later.
25194 o Bugfixes on 0.0.9rc1:
25195 - Make tor-resolve work again.
25196 - Avoid infinite loop in tor-resolve if tor hangs up on it.
25197 - Fix an assert trigger for clients/servers handling resolves.
25200 Changes in version 0.0.9rc2 - 2004-11-24
25201 o Bugfixes on 0.0.9rc1:
25202 - I broke socks5 support while fixing the eof bug.
25203 - Allow unitless bandwidths and intervals; they default to bytes
25205 - New servers don't start out hibernating; they are active until
25206 they run out of bytes, so they have a better estimate of how
25207 long it takes, and so their operators can know they're working.
25210 Changes in version 0.0.9rc1 - 2004-11-23
25211 o Bugfixes on 0.0.8.1:
25212 - Finally fix a bug that's been plaguing us for a year:
25213 With high load, circuit package window was reaching 0. Whenever
25214 we got a circuit-level sendme, we were reading a lot on each
25215 socket, but only writing out a bit. So we would eventually reach
25216 eof. This would be noticed and acted on even when there were still
25217 bytes sitting in the inbuf.
25218 - When poll() is interrupted, we shouldn't believe the revents values.
25220 o Bugfixes on 0.0.9pre6:
25221 - Fix hibernate bug that caused pre6 to be broken.
25222 - Don't keep rephist info for routers that haven't had activity for
25223 24 hours. (This matters now that clients have keys, since we track
25225 - Never call close_temp_logs while validating log options.
25226 - Fix backslash-escaping on tor.sh.in and torctl.in.
25229 - Implement weekly/monthly/daily accounting: now you specify your
25230 hibernation properties by
25231 AccountingMax N bytes|KB|MB|GB|TB
25232 AccountingStart day|week|month [day] HH:MM
25233 Defaults to "month 1 0:00".
25234 - Let bandwidth and interval config options be specified as 5 bytes,
25235 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
25236 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
25237 get back to normal.)
25238 - If your requested entry or exit node has advertised bandwidth 0,
25240 - Be more greedy about filling up relay cells -- we try reading again
25241 once we've processed the stuff we read, in case enough has arrived
25242 to fill the last cell completely.
25243 - Apply NT service patch from Osamu Fujino. Still needs more work.
25246 Changes in version 0.0.9pre6 - 2004-11-15
25247 o Bugfixes on 0.0.8.1:
25248 - Fix assert failure on malformed socks4a requests.
25249 - Use identity comparison, not nickname comparison, to choose which
25250 half of circuit-ID-space each side gets to use. This is needed
25251 because sometimes we think of a router as a nickname, and sometimes
25252 as a hex ID, and we can't predict what the other side will do.
25253 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
25254 write() call will fail and we handle it there.
25255 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
25256 and smartlist_len, which are two major profiling offenders.
25258 o Bugfixes on 0.0.9pre5:
25259 - Fix a bug in read_all that was corrupting config files on windows.
25260 - When we're raising the max number of open file descriptors to
25261 'unlimited', don't log that we just raised it to '-1'.
25262 - Include event code with events, as required by control-spec.txt.
25263 - Don't give a fingerprint when clients do --list-fingerprint:
25264 it's misleading, because it will never be the same again.
25265 - Stop using strlcpy in tor_strndup, since it was slowing us
25267 - Remove warn on startup about missing cached-directory file.
25268 - Make kill -USR1 work again.
25269 - Hibernate if we start tor during the "wait for wakeup-time" phase
25270 of an accounting interval. Log our hibernation plans better.
25271 - Authoritative dirservers now also cache their directory, so they
25272 have it on start-up.
25275 - Fetch running-routers; cache running-routers; compress
25276 running-routers; serve compressed running-routers.z
25277 - Add NSI installer script contributed by J Doe.
25278 - Commit VC6 and VC7 workspace/project files.
25279 - Commit a tor.spec for making RPM files, with help from jbash.
25280 - Add contrib/torctl.in contributed by Glenn Fink.
25281 - Implement the control-spec's SAVECONF command, to write your
25282 configuration to torrc.
25283 - Get cookie authentication for the controller closer to working.
25284 - Include control-spec.txt in the tarball.
25285 - When set_conf changes our server descriptor, upload a new copy.
25286 But don't upload it too often if there are frequent changes.
25287 - Document authentication config in man page, and document signals
25289 - Clean up confusing parts of man page and torrc.sample.
25290 - Make expand_filename handle ~ and ~username.
25291 - Use autoconf to enable largefile support where necessary. Use
25292 ftello where available, since ftell can fail at 2GB.
25293 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
25294 log more informatively.
25295 - Give a slightly more useful output for "tor -h".
25296 - Refuse application socks connections to port 0.
25297 - Check clock skew for verified servers, but allow unverified
25298 servers and clients to have any clock skew.
25299 - Break DirFetchPostPeriod into:
25300 - DirFetchPeriod for fetching full directory,
25301 - StatusFetchPeriod for fetching running-routers,
25302 - DirPostPeriod for posting server descriptor,
25303 - RendPostPeriod for posting hidden service descriptors.
25304 - Make sure the hidden service descriptors are at a random offset
25305 from each other, to hinder linkability.
25308 Changes in version 0.0.9pre5 - 2004-11-09
25309 o Bugfixes on 0.0.9pre4:
25310 - Fix a seg fault in unit tests (doesn't affect main program).
25311 - Fix an assert bug where a hidden service provider would fail if
25312 the first hop of his rendezvous circuit was down.
25313 - Hidden service operators now correctly handle version 1 style
25314 INTRODUCE1 cells (nobody generates them still, so not a critical
25316 - If do_hup fails, actually notice.
25317 - Handle more errnos from accept() without closing the listener.
25318 Some OpenBSD machines were closing their listeners because
25319 they ran out of file descriptors.
25320 - Send resolve cells to exit routers that are running a new
25321 enough version of the resolve code to work right.
25322 - Better handling of winsock includes on non-MSV win32 compilers.
25323 - Some people had wrapped their tor client/server in a script
25324 that would restart it whenever it died. This did not play well
25325 with our "shut down if your version is obsolete" code. Now people
25326 don't fetch a new directory if their local cached version is
25328 - Make our autogen.sh work on ksh as well as bash.
25331 - Hibernation: New config option "AccountingMaxKB" lets you
25332 set how many KBytes per month you want to allow your server to
25333 consume. Rather than spreading those bytes out evenly over the
25334 month, we instead hibernate for some of the month and pop up
25335 at a deterministic time, work until the bytes are consumed, then
25336 hibernate again. Config option "MonthlyAccountingStart" lets you
25337 specify which day of the month your billing cycle starts on.
25338 - Control interface: a separate program can now talk to your
25339 client/server over a socket, and get/set config options, receive
25340 notifications of circuits and streams starting/finishing/dying,
25341 bandwidth used, etc. The next step is to get some GUIs working.
25342 Let us know if you want to help out. See doc/control-spec.txt .
25343 - Ship a contrib/tor-control.py as an example script to interact
25344 with the control port.
25345 - "tor --hash-password zzyxz" will output a salted password for
25346 use in authenticating to the control interface.
25347 - New log format in config:
25348 "Log minsev[-maxsev] stdout|stderr|syslog" or
25349 "Log minsev[-maxsev] file /var/foo"
25352 - DirPolicy config option, to let people reject incoming addresses
25353 from their dirserver.
25354 - "tor --list-fingerprint" will list your identity key fingerprint
25356 - Add "pass" target for RedirectExit, to make it easier to break
25357 out of a sequence of RedirectExit rules.
25358 - Clients now generate a TLS cert too, in preparation for having
25359 them act more like real nodes.
25360 - Ship src/win32/ in the tarball, so people can use it to build.
25361 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
25363 - New "router-status" line in directory, to better bind each verified
25364 nickname to its identity key.
25365 - Deprecate unofficial config option abbreviations, and abbreviations
25366 not on the command line.
25367 - Add a pure-C tor-resolve implementation.
25368 - Use getrlimit and friends to ensure we can reach MaxConn (currently
25369 1024) file descriptors.
25371 o Code security improvements, inspired by Ilja:
25372 - Replace sprintf with snprintf. (I think they were all safe, but
25374 - Replace strcpy/strncpy with strlcpy in more places.
25375 - Avoid strcat; use snprintf or strlcat instead.
25376 - snprintf wrapper with consistent (though not C99) overflow behavior.
25379 Changes in version 0.0.9pre4 - 2004-10-17
25380 o Bugfixes on 0.0.9pre3:
25381 - If the server doesn't specify an exit policy, use the real default
25382 exit policy, not reject *:*.
25383 - Ignore fascistfirewall when uploading/downloading hidden service
25384 descriptors, since we go through Tor for those; and when using
25385 an HttpProxy, since we assume it can reach them all.
25386 - When looking for an authoritative dirserver, use only the ones
25387 configured at boot. Don't bother looking in the directory.
25388 - The rest of the fix for get_default_conf_file() on older win32.
25389 - Make 'Routerfile' config option obsolete.
25392 - New 'MyFamily nick1,...' config option for a server to
25393 specify other servers that shouldn't be used in the same circuit
25394 with it. Only believed if nick1 also specifies us.
25395 - New 'NodeFamily nick1,nick2,...' config option for a client to
25396 specify nodes that it doesn't want to use in the same circuit.
25397 - New 'Redirectexit pattern address:port' config option for a
25398 server to redirect exit connections, e.g. to a local squid.
25401 Changes in version 0.0.9pre3 - 2004-10-13
25402 o Bugfixes on 0.0.8.1:
25403 - Better torrc example lines for dirbindaddress and orbindaddress.
25404 - Improved bounds checking on parsed ints (e.g. config options and
25405 the ones we find in directories.)
25406 - Better handling of size_t vs int, so we're more robust on 64
25408 - Fix the rest of the bug where a newly started OR would appear
25409 as unverified even after we've added his fingerprint and hupped
25411 - Fix a bug from 0.0.7: when read() failed on a stream, we would
25412 close it without sending back an end. So 'connection refused'
25413 would simply be ignored and the user would get no response.
25415 o Bugfixes on 0.0.9pre2:
25416 - Serving the cached-on-disk directory to people is bad. We now
25417 provide no directory until we've fetched a fresh one.
25418 - Workaround for bug on windows where cached-directories get crlf
25420 - Make get_default_conf_file() work on older windows too.
25421 - If we write a *:* exit policy line in the descriptor, don't write
25422 any more exit policy lines.
25425 - Use only 0.0.9pre1 and later servers for resolve cells.
25426 - Make the dirservers file obsolete.
25427 - Include a dir-signing-key token in directories to tell the
25428 parsing entity which key is being used to sign.
25429 - Remove the built-in bulky default dirservers string.
25430 - New config option "Dirserver %s:%d [fingerprint]", which can be
25431 repeated as many times as needed. If no dirservers specified,
25432 default to moria1,moria2,tor26.
25433 - Make moria2 advertise a dirport of 80, so people behind firewalls
25434 will be able to get a directory.
25435 - Http proxy support
25436 - Dirservers translate requests for http://%s:%d/x to /x
25437 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
25438 be routed through this host.
25439 - Clients ask for /tor/x rather than /x for new enough dirservers.
25440 This way we can one day coexist peacefully with apache.
25441 - Clients specify a "Host: %s%d" http header, to be compatible
25442 with more proxies, and so running squid on an exit node can work.
25445 Changes in version 0.0.8.1 - 2004-10-13
25447 - Fix a seg fault that can be triggered remotely for Tor
25448 clients/servers with an open dirport.
25449 - Fix a rare assert trigger, where routerinfos for entries in
25450 our cpath would expire while we're building the path.
25451 - Fix a bug in OutboundBindAddress so it (hopefully) works.
25452 - Fix a rare seg fault for people running hidden services on
25453 intermittent connections.
25454 - Fix a bug in parsing opt keywords with objects.
25455 - Fix a stale pointer assert bug when a stream detaches and
25457 - Fix a string format vulnerability (probably not exploitable)
25458 in reporting stats locally.
25459 - Fix an assert trigger: sometimes launching circuits can fail
25460 immediately, e.g. because too many circuits have failed recently.
25461 - Fix a compile warning on 64 bit platforms.
25464 Changes in version 0.0.9pre2 - 2004-10-03
25466 - Make fetching a cached directory work for 64-bit platforms too.
25467 - Make zlib.h a required header, not an optional header.
25470 Changes in version 0.0.9pre1 - 2004-10-01
25472 - Stop using separate defaults for no-config-file and
25473 empty-config-file. Now you have to explicitly turn off SocksPort,
25474 if you don't want it open.
25475 - Fix a bug in OutboundBindAddress so it (hopefully) works.
25476 - Improve man page to mention more of the 0.0.8 features.
25477 - Fix a rare seg fault for people running hidden services on
25478 intermittent connections.
25479 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
25481 - Fix more dns related bugs: send back resolve_failed and end cells
25482 more reliably when the resolve fails, rather than closing the
25483 circuit and then trying to send the cell. Also attach dummy resolve
25484 connections to a circuit *before* calling dns_resolve(), to fix
25485 a bug where cached answers would never be sent in RESOLVED cells.
25486 - When we run out of disk space, or other log writing error, don't
25487 crash. Just stop logging to that log and continue.
25488 - We were starting to daemonize before we opened our logs, so if
25489 there were any problems opening logs, we would complain to stderr,
25490 which wouldn't work, and then mysteriously exit.
25491 - Fix a rare bug where sometimes a verified OR would connect to us
25492 before he'd uploaded his descriptor, which would cause us to
25493 assign conn->nickname as though he's unverified. Now we look through
25494 the fingerprint list to see if he's there.
25495 - Fix a rare assert trigger, where routerinfos for entries in
25496 our cpath would expire while we're building the path.
25499 - Clients can ask dirservers for /dir.z to get a compressed version
25500 of the directory. Only works for servers running 0.0.9, of course.
25501 - Make clients cache directories and use them to seed their router
25502 lists at startup. This means clients have a datadir again.
25503 - Configuration infrastructure support for warning on obsolete
25505 - Respond to content-encoding headers by trying to uncompress as
25507 - Reply with a deflated directory when a client asks for "dir.z".
25508 We could use allow-encodings instead, but allow-encodings isn't
25509 specified in HTTP 1.0.
25510 - Raise the max dns workers from 50 to 100.
25511 - Discourage people from setting their dirfetchpostperiod more often
25512 than once per minute.
25513 - Protect dirservers from overzealous descriptor uploading -- wait
25514 10 seconds after directory gets dirty, before regenerating.
25517 Changes in version 0.0.8 - 2004-08-25
25518 o Port it to SunOS 5.9 / Athena
25521 Changes in version 0.0.8rc2 - 2004-08-20
25522 o Make it compile on cygwin again.
25523 o When picking unverified routers, skip those with low uptime and/or
25524 low bandwidth, depending on what properties you care about.
25527 Changes in version 0.0.8rc1 - 2004-08-18
25528 o Changes from 0.0.7.3:
25530 - Fix assert triggers: if the other side returns an address 0.0.0.0,
25531 don't put it into the client dns cache.
25532 - If a begin failed due to exit policy, but we believe the IP address
25533 should have been allowed, switch that router to exitpolicy reject *:*
25534 until we get our next directory.
25536 - Clients choose nodes proportional to advertised bandwidth.
25537 - Avoid using nodes with low uptime as introduction points.
25538 - Handle servers with dynamic IP addresses: don't replace
25539 options->Address with the resolved one at startup, and
25540 detect our address right before we make a routerinfo each time.
25541 - 'FascistFirewall' option to pick dirservers and ORs on specific
25542 ports; plus 'FirewallPorts' config option to tell FascistFirewall
25543 which ports are open. (Defaults to 80,443)
25544 - Be more aggressive about trying to make circuits when the network
25545 has changed (e.g. when you unsuspend your laptop).
25546 - Check for time skew on http headers; report date in response to
25548 - If the entrynode config line has only one node, don't pick it as
25550 - Add strict{entry|exit}nodes config options. If set to 1, then
25551 we refuse to build circuits that don't include the specified entry
25553 - OutboundBindAddress config option, to bind to a specific
25554 IP address for outgoing connect()s.
25555 - End truncated log entries (e.g. directories) with "[truncated]".
25557 o Patches to 0.0.8preX:
25559 - Patches to compile and run on win32 again (maybe)?
25560 - Fix crash when looking for ~/.torrc with no $HOME set.
25561 - Fix a race bug in the unit tests.
25562 - Handle verified/unverified name collisions better when new
25563 routerinfo's arrive in a directory.
25564 - Sometimes routers were getting entered into the stats before
25565 we'd assigned their identity_digest. Oops.
25566 - Only pick and establish intro points after we've gotten a
25569 - AllowUnverifiedNodes config option to let circuits choose no-name
25570 routers in entry,middle,exit,introduction,rendezvous positions.
25571 Allow middle and rendezvous positions by default.
25572 - Add a man page for tor-resolve.
25575 Changes in version 0.0.7.3 - 2004-08-12
25576 o Stop dnsworkers from triggering an assert failure when you
25577 ask them to resolve the host "".
25580 Changes in version 0.0.8pre3 - 2004-08-09
25581 o Changes from 0.0.7.2:
25582 - Allow multiple ORs with same nickname in routerlist -- now when
25583 people give us one identity key for a nickname, then later
25584 another, we don't constantly complain until the first expires.
25585 - Remember used bandwidth (both in and out), and publish 15-minute
25586 snapshots for the past day into our descriptor.
25587 - You can now fetch $DIRURL/running-routers to get just the
25588 running-routers line, not the whole descriptor list. (But
25589 clients don't use this yet.)
25590 - When people mistakenly use Tor as an http proxy, point them
25591 at the tor-doc.html rather than the INSTALL.
25592 - Remove our mostly unused -- and broken -- hex_encode()
25593 function. Use base16_encode() instead. (Thanks to Timo Lindfors
25594 for pointing out this bug.)
25595 - Rotate onion keys every 12 hours, not every 2 hours, so we have
25596 fewer problems with people using the wrong key.
25597 - Change the default exit policy to reject the default edonkey,
25598 kazaa, gnutella ports.
25599 - Add replace_file() to util.[ch] to handle win32's rename().
25601 o Changes from 0.0.8preX:
25602 - Fix two bugs in saving onion keys to disk when rotating, so
25603 hopefully we'll get fewer people using old onion keys.
25604 - Fix an assert error that was making SocksPolicy not work.
25605 - Be willing to expire routers that have an open dirport -- it's
25606 just the authoritative dirservers we want to not forget.
25607 - Reject tor-resolve requests for .onion addresses early, so we
25608 don't build a whole rendezvous circuit and then fail.
25609 - When you're warning a server that he's unverified, don't cry
25610 wolf unpredictably.
25611 - Fix a race condition: don't try to extend onto a connection
25612 that's still handshaking.
25613 - For servers in clique mode, require the conn to be open before
25614 you'll choose it for your path.
25615 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
25616 end relay cell, etc.
25617 - Measure bandwidth capacity over the last 24 hours, not just 12
25618 - Bugfix: authoritative dirservers were making and signing a new
25619 directory for each client, rather than reusing the cached one.
25622 Changes in version 0.0.8pre2 - 2004-08-04
25623 o Changes from 0.0.7.2:
25625 - Check directory signature _before_ you decide whether you're
25626 you're running an obsolete version and should exit.
25627 - Check directory signature _before_ you parse the running-routers
25628 list to decide who's running or verified.
25629 - Bugfixes and features:
25630 - Check return value of fclose while writing to disk, so we don't
25631 end up with broken files when servers run out of disk space.
25632 - Log a warning if the user uses an unsafe socks variant, so people
25633 are more likely to learn about privoxy or socat.
25634 - Dirservers now include RFC1123-style dates in the HTTP headers,
25635 which one day we will use to better detect clock skew.
25637 o Changes from 0.0.8pre1:
25638 - Make it compile without warnings again on win32.
25639 - Log a warning if you're running an unverified server, to let you
25640 know you might want to get it verified.
25641 - Only pick a default nickname if you plan to be a server.
25644 Changes in version 0.0.8pre1 - 2004-07-23
25646 - Made our unit tests compile again on OpenBSD 3.5, and tor
25647 itself compile again on OpenBSD on a sparc64.
25648 - We were neglecting milliseconds when logging on win32, so
25649 everything appeared to happen at the beginning of each second.
25651 o Protocol changes:
25652 - 'Extend' relay cell payloads now include the digest of the
25653 intended next hop's identity key. Now we can verify that we're
25654 extending to the right router, and also extend to routers we
25655 hadn't heard of before.
25658 - Tor nodes can now act as relays (with an advertised ORPort)
25659 without being manually verified by the dirserver operators.
25660 - Uploaded descriptors of unverified routers are now accepted
25661 by the dirservers, and included in the directory.
25662 - Verified routers are listed by nickname in the running-routers
25663 list; unverified routers are listed as "$<fingerprint>".
25664 - We now use hash-of-identity-key in most places rather than
25665 nickname or addr:port, for improved security/flexibility.
25666 - To avoid Sybil attacks, paths still use only verified servers.
25667 But now we have a chance to play around with hybrid approaches.
25668 - Nodes track bandwidth usage to estimate capacity (not used yet).
25669 - ClientOnly option for nodes that never want to become servers.
25670 - Directory caching.
25671 - "AuthoritativeDir 1" option for the official dirservers.
25672 - Now other nodes (clients and servers) will cache the latest
25673 directory they've pulled down.
25674 - They can enable their DirPort to serve it to others.
25675 - Clients will pull down a directory from any node with an open
25676 DirPort, and check the signature/timestamp correctly.
25677 - Authoritative dirservers now fetch directories from other
25678 authdirservers, to stay better synced.
25679 - Running-routers list tells who's down also, along with noting
25680 if they're verified (listed by nickname) or unverified (listed
25682 - Allow dirservers to serve running-router list separately.
25683 This isn't used yet.
25684 - ORs connect-on-demand to other ORs
25685 - If you get an extend cell to an OR you're not connected to,
25686 connect, handshake, and forward the create cell.
25687 - The authoritative dirservers stay connected to everybody,
25688 and everybody stays connected to 0.0.7 servers, but otherwise
25689 clients/servers expire unused connections after 5 minutes.
25690 - When servers get a sigint, they delay 30 seconds (refusing new
25691 connections) then exit. A second sigint causes immediate exit.
25692 - File and name management:
25693 - Look for .torrc if no CONFDIR "torrc" is found.
25694 - If no datadir is defined, then choose, make, and secure ~/.tor
25696 - If torrc not found, exitpolicy reject *:*.
25697 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
25698 - If no nickname is defined, derive default from hostname.
25699 - Rename secret key files, e.g. identity.key -> secret_id_key,
25700 to discourage people from mailing their identity key to tor-ops.
25701 - Refuse to build a circuit before the directory has arrived --
25702 it won't work anyway, since you won't know the right onion keys
25704 - Try other dirservers immediately if the one you try is down. This
25705 should tolerate down dirservers better now.
25706 - Parse tor version numbers so we can do an is-newer-than check
25707 rather than an is-in-the-list check.
25708 - New socks command 'resolve', to let us shim gethostbyname()
25710 - A 'tor_resolve' script to access the socks resolve functionality.
25711 - A new socks-extensions.txt doc file to describe our
25712 interpretation and extensions to the socks protocols.
25713 - Add a ContactInfo option, which gets published in descriptor.
25714 - Publish OR uptime in descriptor (and thus in directory) too.
25715 - Write tor version at the top of each log file
25716 - New docs in the tarball:
25718 - Document that you should proxy your SSL traffic too.
25721 Changes in version 0.0.7.2 - 2004-07-07
25722 o A better fix for the 0.0.0.0 problem, that will hopefully
25723 eliminate the remaining related assertion failures.
25726 Changes in version 0.0.7.1 - 2004-07-04
25727 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
25728 since internally we use 0.0.0.0 to signify "not yet resolved".
25731 Changes in version 0.0.7 - 2004-06-07
25732 o Updated the man page to reflect the new features.
25735 Changes in version 0.0.7rc2 - 2004-06-06
25736 o Changes from 0.0.7rc1:
25737 - Make it build on Win32 again.
25738 o Changes from 0.0.6.2:
25739 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
25743 Changes in version 0.0.7rc1 - 2004-06-02
25745 - On sighup, we were adding another log without removing the first
25746 one. So log messages would get duplicated n times for n sighups.
25747 - Several cases of using a connection after we'd freed it. The
25748 problem was that connections that are pending resolve are in both
25749 the pending_resolve tree, and also the circuit's resolving_streams
25750 list. When you want to remove one, you must remove it from both.
25751 - Fix a double-mark-for-close where an end cell arrived for a
25752 resolving stream, and then the resolve failed.
25753 - Check directory signatures based on name of signer, not on whom
25754 we got the directory from. This will let us cache directories more
25757 - Crank up some of our constants to handle more users.
25760 Changes in version 0.0.7pre1 - 2004-06-02
25761 o Fixes for crashes and other obnoxious bugs:
25762 - Fix an epipe bug: sometimes when directory connections failed
25763 to connect, we would give them a chance to flush before closing
25765 - When we detached from a circuit because of resolvefailed, we
25766 would immediately try the same circuit twice more, and then
25767 give up on the resolve thinking we'd tried three different
25769 - Limit the number of intro circuits we'll attempt to build for a
25770 hidden service per 15-minute period.
25771 - Check recommended-software string *early*, before actually parsing
25772 the directory. Thus we can detect an obsolete version and exit,
25773 even if the new directory format doesn't parse.
25774 o Fixes for security bugs:
25775 - Remember which nodes are dirservers when you startup, and if a
25776 random OR enables his dirport, don't automatically assume he's
25777 a trusted dirserver.
25779 - Directory connections were asking the wrong poll socket to
25780 start writing, and not asking themselves to start writing.
25781 - When we detached from a circuit because we sent a begin but
25782 didn't get a connected, we would use it again the first time;
25783 but after that we would correctly switch to a different one.
25784 - Stop warning when the first onion decrypt attempt fails; they
25785 will sometimes legitimately fail now that we rotate keys.
25786 - Override unaligned-access-ok check when $host_cpu is ia64 or
25787 arm. Apparently they allow it but the kernel whines.
25788 - Dirservers try to reconnect periodically too, in case connections
25790 - Fix some memory leaks in directory servers.
25791 - Allow backslash in Win32 filenames.
25792 - Made Tor build complain-free on FreeBSD, hopefully without
25793 breaking other BSD builds. We'll see.
25795 - Doxygen markup on all functions and global variables.
25796 - Make directory functions update routerlist, not replace it. So
25797 now directory disagreements are not so critical a problem.
25798 - Remove the upper limit on number of descriptors in a dirserver's
25799 directory (not that we were anywhere close).
25800 - Allow multiple logfiles at different severity ranges.
25801 - Allow *BindAddress to specify ":port" rather than setting *Port
25802 separately. Allow multiple instances of each BindAddress config
25803 option, so you can bind to multiple interfaces if you want.
25804 - Allow multiple exit policy lines, which are processed in order.
25805 Now we don't need that huge line with all the commas in it.
25806 - Enable accept/reject policies on SOCKS connections, so you can bind
25807 to 0.0.0.0 but still control who can use your OP.
25810 Changes in version 0.0.6.2 - 2004-05-16
25811 o Our integrity-checking digest was checking only the most recent cell,
25812 not the previous cells like we'd thought.
25813 Thanks to Stefan Mark for finding the flaw!
25816 Changes in version 0.0.6.1 - 2004-05-06
25817 o Fix two bugs in our AES counter-mode implementation (this affected
25818 onion-level stream encryption, but not TLS-level). It turns
25819 out we were doing something much more akin to a 16-character
25820 polyalphabetic cipher. Oops.
25821 Thanks to Stefan Mark for finding the flaw!
25822 o Retire moria3 as a directory server, and add tor26 as a directory
25826 Changes in version 0.0.6 - 2004-05-02
25827 [version bump only]
25830 Changes in version 0.0.6rc4 - 2004-05-01
25831 o Update the built-in dirservers list to use the new directory format
25832 o Fix a rare seg fault: if a node offering a hidden service attempts
25833 to build a circuit to Alice's rendezvous point and fails before it
25834 reaches the last hop, it retries with a different circuit, but
25836 o Handle windows socket errors correctly.
25839 Changes in version 0.0.6rc3 - 2004-04-28
25840 o Don't expire non-general excess circuits (if we had enough
25841 circuits open, we were expiring rendezvous circuits -- even
25842 when they had a stream attached. oops.)
25843 o Fetch randomness from /dev/urandom better (not via fopen/fread)
25844 o Better debugging for tls errors
25845 o Some versions of openssl have an SSL_pending function that erroneously
25846 returns bytes when there is a non-application record pending.
25847 o Set Content-Type on the directory and hidserv descriptor.
25848 o Remove IVs from cipher code, since AES-ctr has none.
25849 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
25850 o We were using an array of length zero in a few places.
25851 o win32's gethostbyname can't resolve an IP to an IP.
25852 o win32's close can't close a socket.
25855 Changes in version 0.0.6rc2 - 2004-04-26
25856 o Fix a bug where we were closing tls connections intermittently.
25857 It turns out openssl keeps its errors around -- so if an error
25858 happens, and you don't ask about it, and then another openssl
25859 operation happens and succeeds, and you ask if there was an error,
25860 it tells you about the first error. Fun fun.
25861 o Fix a bug that's been lurking since 27 may 03 (!)
25862 When passing back a destroy cell, we would use the wrong circ id.
25863 'Mostly harmless', but still worth fixing.
25864 o Since we don't support truncateds much, don't bother sending them;
25865 just close the circ.
25866 o check for <machine/limits.h> so we build on NetBSD again (I hope).
25867 o don't crash if a conn that sent a begin has suddenly lost its circuit
25868 (this was quite rare).
25871 Changes in version 0.0.6rc1 - 2004-04-25
25872 o We now rotate link (tls context) keys and onion keys.
25873 o CREATE cells now include oaep padding, so you can tell
25874 if you decrypted them correctly.
25875 o Add bandwidthburst to server descriptor.
25876 o Directories now say which dirserver signed them.
25877 o Use a tor_assert macro that logs failed assertions too.
25880 Changes in version 0.0.6pre5 - 2004-04-18
25881 o changes from 0.0.6pre4:
25882 - make tor build on broken freebsd 5.2 installs
25883 - fix a failed assert when you try an intro point, get a nack, and try
25884 a second one and it works.
25885 - when alice uses a port that the hidden service doesn't accept,
25886 it now sends back an end cell (denied by exit policy). otherwise
25887 alice would just have to wait to time out.
25888 - fix another rare bug: when we had tried all the intro
25889 points for a hidden service, we fetched the descriptor
25890 again, but we left our introcirc thinking it had already
25891 sent an intro, so it kept waiting for a response...
25892 - bugfix: when you sleep your hidden-service laptop, as soon
25893 as it wakes up it tries to upload a service descriptor, but
25894 socketpair fails for some reason (localhost not up yet?).
25895 now we simply give up on that upload, and we'll try again later.
25896 i'd still like to find the bug though.
25897 - if an intro circ waiting for an ack dies before getting one, then
25899 - we were reusing stale service descriptors and refetching usable
25903 Changes in version 0.0.6pre4 - 2004-04-14
25904 o changes from 0.0.6pre3:
25905 - when bob fails to connect to the rendezvous point, and his
25906 circ didn't fail because of the rendezvous point itself, then
25907 he retries a couple of times
25908 - we expire introduction and rendezvous circs more thoroughly
25909 (sometimes they were hanging around forever)
25910 - we expire unattached rendezvous streams that have been around
25911 too long (they were sticking around forever).
25912 - fix a measly fencepost error that was crashing everybody with
25916 Changes in version 0.0.6pre3 - 2004-04-14
25917 o changes from 0.0.6pre2:
25918 - make hup work again
25919 - fix some memory leaks for dirservers
25920 - allow more skew in rendezvous descriptor timestamps, to help
25921 handle people like blanu who don't know what time it is
25922 - normal circs are 3 hops, but some rend/intro circs are 4, if
25923 the initiator doesn't get to choose the last hop
25924 - send acks for introductions, so alice can know whether to try
25926 - bob publishes intro points more correctly
25927 o changes from 0.0.5:
25928 - fix an assert trigger that's been plaguing us since the days
25929 of 0.0.2prexx (thanks weasel!)
25930 - retry stream correctly when we fail to connect because of
25931 exit-policy-reject (should try another) or can't-resolve-address
25932 (also should try another, because dns on random internet servers
25934 - when we hup a dirserver and we've *removed* a server from the
25935 approved-routers list, now we remove that server from the
25936 in-memory directories too
25939 Changes in version 0.0.6pre2 - 2004-04-08
25940 o We fixed our base32 implementation. Now it works on all architectures.
25943 Changes in version 0.0.6pre1 - 2004-04-08
25945 - Hidden services and rendezvous points are implemented. Go to
25946 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
25947 hidden services. (This only works via a socks4a proxy such as
25948 Privoxy, and currently it's quite slow.)
25951 Changes in version 0.0.5 - 2004-03-30
25952 [version bump only]
25955 Changes in version 0.0.5rc3 - 2004-03-29
25956 o Install torrc as torrc.sample -- we no longer clobber your
25958 o Re-enable recommendedversion checking (we broke it in rc2, oops)
25959 o Add in a 'notice' log level for things the operator should hear
25960 but that aren't warnings
25963 Changes in version 0.0.5rc2 - 2004-03-29
25964 o Hold socks connection open until reply is flushed (if possible)
25965 o Make exit nodes resolve IPs to IPs immediately, rather than asking
25966 the dns farm to do it.
25967 o Fix c99 aliasing warnings in rephist.c
25968 o Don't include server descriptors that are older than 24 hours in the
25970 o Give socks 'reject' replies their whole 15s to attempt to flush,
25971 rather than seeing the 60s timeout and assuming the flush had failed.
25972 o Clean automake droppings from the cvs repository
25975 Changes in version 0.0.5rc1 - 2004-03-28
25976 o Fix mangled-state bug in directory fetching (was causing sigpipes).
25977 o Only build circuits after we've fetched the directory: clients were
25978 using only the directory servers before they'd fetched a directory.
25979 This also means longer startup time; so it goes.
25980 o Fix an assert trigger where an OP would fail to handshake, and we'd
25981 expect it to have a nickname.
25982 o Work around a tsocks bug: do a socks reject when AP connection dies
25983 early, else tsocks goes into an infinite loop.
25986 Changes in version 0.0.4 - 2004-03-26
25987 o When connecting to a dirserver or OR and the network is down,
25991 Changes in version 0.0.3 - 2004-03-26
25992 o Warn and fail if server chose a nickname with illegal characters
25993 o Port to Solaris and Sparc:
25994 - include missing header fcntl.h
25995 - have autoconf find -lsocket -lnsl automatically
25996 - deal with hardware word alignment
25997 - make uname() work (solaris has a different return convention)
25998 - switch from using signal() to sigaction()
25999 o Preliminary work on reputation system:
26000 - Keep statistics on success/fail of connect attempts; they're published
26001 by kill -USR1 currently.
26002 - Add a RunTesting option to try to learn link state by creating test
26003 circuits, even when SocksPort is off.
26004 - Remove unused open circuits when there are too many.
26007 Changes in version 0.0.2 - 2004-03-19
26008 - Include strlcpy and strlcat for safer string ops
26009 - define INADDR_NONE so we compile (but still not run) on solaris
26012 Changes in version 0.0.2pre27 - 2004-03-14
26014 - Allow internal tor networks (we were rejecting internal IPs,
26015 now we allow them if they're set explicitly).
26016 - And fix a few endian issues.
26019 Changes in version 0.0.2pre26 - 2004-03-14
26021 - If a stream times out after 15s without a connected cell, don't
26022 try that circuit again: try a new one.
26023 - Retry streams at most 4 times. Then give up.
26024 - When a dirserver gets a descriptor from an unknown router, it
26025 logs its fingerprint (so the dirserver operator can choose to
26026 accept it even without mail from the server operator).
26027 - Inform unapproved servers when we reject their descriptors.
26028 - Make tor build on Windows again. It works as a client, who knows
26030 - Clearer instructions in the torrc for how to set up a server.
26031 - Be more efficient about reading fd's when our global token bucket
26032 (used for rate limiting) becomes empty.
26034 - Stop asserting that computers always go forward in time. It's
26036 - When we sent a cell (e.g. destroy) and then marked an OR connection
26037 expired, we might close it before finishing a flush if the other
26038 side isn't reading right then.
26039 - Don't allow dirservers to start if they haven't defined
26040 RecommendedVersions
26041 - We were caching transient dns failures. Oops.
26042 - Prevent servers from publishing an internal IP as their address.
26043 - Address a strcat vulnerability in circuit.c
26046 Changes in version 0.0.2pre25 - 2004-03-04
26048 - Put the OR's IP in its router descriptor, not its fqdn. That way
26049 we'll stop being stalled by gethostbyname for nodes with flaky dns,
26052 - If the user typed in an address that didn't resolve, the server
26056 Changes in version 0.0.2pre24 - 2004-03-03
26058 - Fix an assertion failure in dns.c, where we were trying to dequeue
26059 a pending dns resolve even if it wasn't pending
26060 - Fix a spurious socks5 warning about still trying to write after the
26061 connection is finished.
26062 - Hold certain marked_for_close connections open until they're finished
26063 flushing, rather than losing bytes by closing them too early.
26064 - Correctly report the reason for ending a stream
26065 - Remove some duplicate calls to connection_mark_for_close
26066 - Put switch_id and start_daemon earlier in the boot sequence, so it
26067 will actually try to chdir() to options.DataDirectory
26068 - Make 'make test' exit(1) if a test fails; fix some unit tests
26069 - Make tor fail when you use a config option it doesn't know about,
26070 rather than warn and continue.
26071 - Make --version work
26072 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
26075 Changes in version 0.0.2pre23 - 2004-02-29
26077 - Print a statement when the first circ is finished, so the user
26078 knows it's working.
26079 - If a relay cell is unrecognized at the end of the circuit,
26080 send back a destroy. (So attacks to mutate cells are more
26082 - New config option 'excludenodes' to avoid certain nodes for circuits.
26083 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
26084 so you can collect coredumps there.
26086 - Fix a bug in tls flushing where sometimes data got wedged and
26087 didn't flush until more data got sent. Hopefully this bug was
26088 a big factor in the random delays we were seeing.
26089 - Make 'connected' cells include the resolved IP, so the client
26090 dns cache actually gets populated.
26091 - Disallow changing from ORPort=0 to ORPort>0 on hup.
26092 - When we time-out on a stream and detach from the circuit, send an
26093 end cell down it first.
26094 - Only warn about an unknown router (in exitnodes, entrynodes,
26095 excludenodes) after we've fetched a directory.
26098 Changes in version 0.0.2pre22 - 2004-02-26
26100 - Servers publish less revealing uname information in descriptors.
26101 - More memory tracking and assertions, to crash more usefully when
26103 - If the default torrc isn't there, just use some default defaults.
26104 Plus provide an internal dirservers file if they don't have one.
26105 - When the user tries to use Tor as an http proxy, give them an http
26106 501 failure explaining that we're a socks proxy.
26107 - Dump a new router.desc on hup, to help confused people who change
26108 their exit policies and then wonder why router.desc doesn't reflect
26110 - Clean up the generic tor.sh init script that we ship with.
26112 - If the exit stream is pending on the resolve, and a destroy arrives,
26113 then the stream wasn't getting removed from the pending list. I
26114 think this was the one causing recent server crashes.
26115 - Use a more robust poll on OSX 10.3, since their poll is flaky.
26116 - When it couldn't resolve any dirservers, it was useless from then on.
26117 Now it reloads the RouterFile (or default dirservers) if it has no
26119 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
26120 many users don't even *have* a /usr/local/sbin/.
26123 Changes in version 0.0.2pre21 - 2004-02-18
26125 - There's a ChangeLog file that actually reflects the changelog.
26126 - There's a 'torify' wrapper script, with an accompanying
26127 tor-tsocks.conf, that simplifies the process of using tsocks for
26128 tor. It even has a man page.
26129 - The tor binary gets installed to sbin rather than bin now.
26130 - Retry streams where the connected cell hasn't arrived in 15 seconds
26131 - Clean up exit policy handling -- get the default out of the torrc,
26132 so we can update it without forcing each server operator to fix
26134 - Allow imaps and pop3s in default exit policy
26136 - Prevent picking middleman nodes as the last node in the circuit
26139 Changes in version 0.0.2pre20 - 2004-01-30
26141 - We now have a deb package, and it's in debian unstable. Go to
26142 it, apt-getters. :)
26143 - I've split the TotalBandwidth option into BandwidthRate (how many
26144 bytes per second you want to allow, long-term) and
26145 BandwidthBurst (how many bytes you will allow at once before the cap
26146 kicks in). This better token bucket approach lets you, say, set
26147 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
26148 performance while not exceeding your monthly bandwidth quota.
26149 - Push out a tls record's worth of data once you've got it, rather
26150 than waiting until you've read everything waiting to be read. This
26151 may improve performance by pipelining better. We'll see.
26152 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
26153 from failed circuits (if they haven't been connected yet) and attach
26155 - Expire old streams that haven't managed to connect. Some day we'll
26156 have them reattach to new circuits instead.
26159 - Fix several memory leaks that were causing servers to become bloated
26161 - Fix a few very rare assert triggers. A few more remain.
26162 - Setuid to User _before_ complaining about running as root.
26165 Changes in version 0.0.2pre19 - 2004-01-07
26167 - Fix deadlock condition in dns farm. We were telling a child to die by
26168 closing the parent's file descriptor to him. But newer children were
26169 inheriting the open file descriptor from the parent, and since they
26170 weren't closing it, the socket never closed, so the child never read
26171 eof, so he never knew to exit. Similarly, dns workers were holding
26172 open other sockets, leading to all sorts of chaos.
26173 - New cleaner daemon() code for forking and backgrounding.
26174 - If you log to a file, it now prints an entry at the top of the
26175 logfile so you know it's working.
26176 - The onionskin challenge length was 30 bytes longer than necessary.
26177 - Started to patch up the spec so it's not quite so out of date.
26180 Changes in version 0.0.2pre18 - 2004-01-02
26182 - Fix endian issues with the 'integrity' field in the relay header.
26183 - Fix a potential bug where connections in state
26184 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
26187 Changes in version 0.0.2pre17 - 2003-12-30
26189 - Made --debuglogfile (or any second log file, actually) work.
26190 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
26191 adversary could force us into an infinite loop.
26194 - Each onionskin handshake now includes a hash of the computed key,
26195 to prove the server's identity and help perfect forward secrecy.
26196 - Changed cell size from 256 to 512 bytes (working toward compatibility
26198 - Changed cell length to 2 bytes, and moved it to the relay header.
26199 - Implemented end-to-end integrity checking for the payloads of
26201 - Separated streamid from 'recognized' (otherwise circuits will get
26202 messed up when we try to have streams exit from the middle). We
26203 use the integrity-checking to confirm that a cell is addressed to
26205 - Randomize the initial circid and streamid values, so an adversary who
26206 breaks into a node can't learn how many circuits or streams have
26210 Changes in version 0.0.2pre16 - 2003-12-14
26212 - Fixed a bug that made HUP trigger an assert
26213 - Fixed a bug where a circuit that immediately failed wasn't being
26214 counted as a failed circuit in counting retries.
26217 - Now we close the circuit when we get a truncated cell: otherwise we're
26218 open to an anonymity attack where a bad node in the path truncates
26219 the circuit and then we open streams at him.
26220 - Add port ranges to exit policies
26221 - Add a conservative default exit policy
26222 - Warn if you're running tor as root
26223 - on HUP, retry OR connections and close/rebind listeners
26224 - options.EntryNodes: try these nodes first when picking the first node
26225 - options.ExitNodes: if your best choices happen to include any of
26226 your preferred exit nodes, you choose among just those preferred
26228 - options.ExcludedNodes: nodes that are never picked in path building
26231 Changes in version 0.0.2pre15 - 2003-12-03
26232 o Robustness and bugfixes:
26233 - Sometimes clients would cache incorrect DNS resolves, which would
26234 really screw things up.
26235 - An OP that goes offline would slowly leak all its sockets and stop
26237 - A wide variety of bugfixes in exit node selection, exit policy
26238 handling, and processing pending streams when a new circuit is
26240 - Pick nodes for a path only from those the directory says are up
26241 - Choose randomly from all running dirservers, not always the first one
26242 - Increase allowed http header size for directory fetch.
26243 - Stop writing to stderr (if we're daemonized it will be closed).
26244 - Enable -g always, so cores will be more useful to me.
26245 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
26248 - Wrote a man page. It lists commonly used options.
26251 - Change default loglevel to warn.
26252 - Make PidFile default to null rather than littering in your CWD.
26253 - OnionRouter config option is now obsolete. Instead it just checks
26255 - Moved to a single unified torrc file for both clients and servers.
26258 Changes in version 0.0.2pre14 - 2003-11-29
26259 o Robustness and bugfixes:
26260 - Force the admin to make the DataDirectory himself
26261 - to get ownership/permissions right
26262 - so clients no longer make a DataDirectory and then never use it
26263 - fix bug where a client who was offline for 45 minutes would never
26264 pull down a directory again
26265 - fix (or at least hide really well) the dns assert bug that was
26266 causing server crashes
26267 - warnings and improved robustness wrt clockskew for certs
26268 - use the native daemon(3) to daemonize, when available
26269 - exit if bind() fails
26270 - exit if neither socksport nor orport is defined
26271 - include our own tor_timegm (Win32 doesn't have its own)
26272 - bugfix for win32 with lots of connections
26273 - fix minor bias in PRNG
26274 - make dirserver more robust to corrupt cached directory
26277 - Wrote the design document (woo)
26279 o Circuit building and exit policies:
26280 - Circuits no longer try to use nodes that the directory has told them
26282 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
26283 bitcounts (18.0.0.0/8).
26284 - Make AP connections standby for a circuit if no suitable circuit
26285 exists, rather than failing
26286 - Circuits choose exit node based on addr/port, exit policies, and
26287 which AP connections are standing by
26288 - Bump min pathlen from 2 to 3
26289 - Relay end cells have a payload to describe why the stream ended.
26290 - If the stream failed because of exit policy, try again with a new
26292 - Clients have a dns cache to remember resolved addresses.
26293 - Notice more quickly when we have no working circuits
26296 - APPort is now called SocksPort
26297 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
26299 - RecommendedVersions is now a config variable rather than
26300 hardcoded (for dirservers)
26301 - Reloads config on HUP
26302 - Usage info on -h or --help
26303 - If you set User and Group config vars, it'll setu/gid to them.
26306 Changes in version 0.0.2pre13 - 2003-10-19
26307 o General stability:
26308 - SSL_write no longer fails when it returns WANTWRITE and the number
26309 of bytes in the buf has changed by the next SSL_write call.
26310 - Fix segfault fetching directory when network is down
26311 - Fix a variety of minor memory leaks
26312 - Dirservers reload the fingerprints file on HUP, so I don't have
26313 to take down the network when I approve a new router
26314 - Default server config file has explicit Address line to specify fqdn
26317 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
26318 - Make listener connections not ever alloc bufs
26320 o Autoconf improvements:
26321 - don't clobber an external CFLAGS in ./configure
26322 - Make install now works
26323 - create var/lib/tor on make install
26324 - autocreate a tor.sh initscript to help distribs
26325 - autocreate the torrc and sample-server-torrc with correct paths
26327 o Log files and Daemonizing now work:
26328 - If --DebugLogFile is specified, log to it at -l debug
26329 - If --LogFile is specified, use it instead of commandline
26330 - If --RunAsDaemon is set, tor forks and backgrounds on startup