1 Changes in version 0.3.2.9 - 2018-01-09
2 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
4 The 0.3.2 series includes our long-anticipated new onion service
5 design, with numerous security features. (For more information, see
6 our blog post at https://blog.torproject.org/fall-harvest.) We also
7 have a new circuit scheduler algorithm for improved performance on
8 relays everywhere (see https://blog.torproject.org/kist-and-tell),
9 along with many smaller features and bugfixes.
11 Per our stable release policy, we plan to support each stable release
12 series for at least the next nine months, or for three months after
13 the first stable release of the next series: whichever is longer. If
14 you need a release with long-term support, we recommend that you stay
15 with the 0.2.9 series.
17 Below is a list of the changes since 0.3.2.8-rc. For a list of all
18 changes since 0.3.1, see the ReleaseNotes file.
20 o Minor features (fallback directory mirrors):
21 - The fallback directory list has been re-generated based on the
22 current status of the network. Tor uses fallback directories to
23 bootstrap when it doesn't yet have up-to-date directory
24 information. Closes ticket 24801.
25 - Make the default DirAuthorityFallbackRate 0.1, so that clients
26 prefer to bootstrap from fallback directory mirrors. This is a
27 follow-up to 24679, which removed weights from the default
28 fallbacks. Implements ticket 24681.
30 o Minor features (geoip):
31 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
34 o Minor bugfixes (address selection):
35 - When the fascist_firewall_choose_address_ functions don't find a
36 reachable address, set the returned address to the null address
37 and port. This is a precautionary measure, because some callers do
38 not check the return value. Fixes bug 24736; bugfix
41 o Minor bugfixes (compilation):
42 - Resolve a few shadowed-variable warnings in the onion service
43 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
45 o Minor bugfixes (portability, msvc):
46 - Fix a bug in the bit-counting parts of our timing-wheel code on
47 MSVC. (Note that MSVC is still not a supported build platform, due
48 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
52 Changes in version 0.3.2.8-rc - 2017-12-21
53 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
54 schedulers that had led servers under heavy load to overload their
55 outgoing connections. All relay operators running earlier 0.3.2.x
56 versions should upgrade. This version also includes a mitigation for
57 over-full DESTROY queues leading to out-of-memory conditions: if it
58 works, we will soon backport it to earlier release series.
60 This is the second release candidate in the 0.3.2 series. If we find
61 no new bugs or regression here, then the first stable 0.3.2 release
62 will be nearly identical to this.
64 o Major bugfixes (KIST, scheduler):
65 - The KIST scheduler did not correctly account for data already
66 enqueued in each connection's send socket buffer, particularly in
67 cases when the TCP/IP congestion window was reduced between
68 scheduler calls. This situation lead to excessive per-connection
69 buffering in the kernel, and a potential memory DoS. Fixes bug
70 24665; bugfix on 0.3.2.1-alpha.
72 o Minor features (geoip):
73 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
76 o Minor bugfixes (hidden service v3):
77 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
78 the probability of reaching a service for a client missing
79 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
81 o Minor bugfixes (memory usage):
82 - When queuing DESTROY cells on a channel, only queue the circuit-id
83 and reason fields: not the entire 514-byte cell. This fix should
84 help mitigate any bugs or attacks that fill up these queues, and
85 free more RAM for other uses. Fixes bug 24666; bugfix
88 o Minor bugfixes (scheduler, KIST):
89 - Use a sane write limit for KISTLite when writing onto a connection
90 buffer instead of using INT_MAX and shoving as much as it can.
91 Because the OOM handler cleans up circuit queues, we are better
92 off at keeping them in that queue instead of the connection's
93 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
96 Changes in version 0.3.2.7-rc - 2017-12-14
97 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
98 including some that could affect reliability or correctness.
100 This is the first release candidate in the 0.3.2 series. If we find no
101 new bugs or regression here, then the first stable 0.3.2. release will
102 be nearly identical to this.
104 o Major bugfixes (circuit prediction):
105 - Fix circuit prediction logic so that a client doesn't treat a port
106 as being "handled" by a circuit if that circuit already has
107 isolation settings on it. This change should make Tor clients more
108 responsive by improving their chances of having a pre-created
109 circuit ready for use when a request arrives. Fixes bug 18859;
110 bugfix on 0.2.3.3-alpha.
112 o Minor features (logging):
113 - Provide better warnings when the getrandom() syscall fails. Closes
116 o Minor features (portability):
117 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
118 (It doesn't yet work with the sandbox enabled.) Closes
121 o Minor bugfixes (bridge clients, bootstrap):
122 - Retry directory downloads when we get our first bridge descriptor
123 during bootstrap or while reconnecting to the network. Keep
124 retrying every time we get a bridge descriptor, until we have a
125 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
126 - Stop delaying bridge descriptor fetches when we have cached bridge
127 descriptors. Instead, only delay bridge descriptor fetches when we
128 have at least one reachable bridge. Fixes part of bug 24367;
129 bugfix on 0.2.0.3-alpha.
130 - Stop delaying directory fetches when we have cached bridge
131 descriptors. Instead, only delay bridge descriptor fetches when
132 all our bridges are definitely unreachable. Fixes part of bug
133 24367; bugfix on 0.2.0.3-alpha.
135 o Minor bugfixes (compilation):
136 - Fix a signed/unsigned comparison warning introduced by our fix to
137 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
139 o Minor bugfixes (correctness):
140 - Fix several places in our codebase where a C compiler would be
141 likely to eliminate a check, based on assuming that undefined
142 behavior had not happened elsewhere in the code. These cases are
143 usually a sign of redundant checking or dubious arithmetic. Found
144 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
145 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
148 o Minor bugfixes (onion service v3):
149 - Fix a race where an onion service would launch a new intro circuit
150 after closing an old one, but fail to register it before freeing
151 the previously closed circuit. This bug was making the service
152 unable to find the established intro circuit and thus not upload
153 its descriptor, thus making a service unavailable for up to 24
154 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
156 o Minor bugfixes (scheduler, KIST):
157 - Properly set the scheduler state of an unopened channel in the
158 KIST scheduler main loop. This prevents a harmless but annoying
159 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
160 - Avoid a possible integer overflow when computing the available
161 space on the TCP buffer of a channel. This had no security
162 implications; but could make KIST allow too many cells on a
163 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
164 - Downgrade to "info" a harmless warning about the monotonic time
165 moving backwards: This can happen on platform not supporting
166 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
169 Changes in version 0.3.2.6-alpha - 2017-12-01
170 This version of Tor is the latest in the 0.3.2 alpha series. It
171 includes fixes for several important security issues. All Tor users
172 should upgrade to this release, or to one of the other releases coming
175 o Major bugfixes (security):
176 - Fix a denial of service bug where an attacker could use a
177 malformed directory object to cause a Tor instance to pause while
178 OpenSSL would try to read a passphrase from the terminal. (Tor
179 instances run without a terminal, which is the case for most Tor
180 packages, are not impacted.) Fixes bug 24246; bugfix on every
181 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
182 Found by OSS-Fuzz as testcase 6360145429790720.
183 - Fix a denial of service issue where an attacker could crash a
184 directory authority using a malformed router descriptor. Fixes bug
185 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
187 - When checking for replays in the INTRODUCE1 cell data for a
188 (legacy) onion service, correctly detect replays in the RSA-
189 encrypted part of the cell. We were previously checking for
190 replays on the entire cell, but those can be circumvented due to
191 the malleability of Tor's legacy hybrid encryption. This fix helps
192 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
193 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
196 o Major bugfixes (security, onion service v2):
197 - Fix a use-after-free error that could crash v2 Tor onion services
198 when they failed to open circuits while expiring introduction
199 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
200 also tracked as TROVE-2017-013 and CVE-2017-8823.
202 o Major bugfixes (security, relay):
203 - When running as a relay, make sure that we never build a path
204 through ourselves, even in the case where we have somehow lost the
205 version of our descriptor appearing in the consensus. Fixes part
206 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
207 as TROVE-2017-012 and CVE-2017-8822.
208 - When running as a relay, make sure that we never choose ourselves
209 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
210 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
212 o Minor feature (relay statistics):
213 - Change relay bandwidth reporting stats interval from 4 hours to 24
214 hours in order to reduce the efficiency of guard discovery
215 attacks. Fixes ticket 23856.
217 o Minor features (directory authority):
218 - Add an IPv6 address for the "bastet" directory authority. Closes
221 o Minor bugfixes (client):
222 - By default, do not enable storage of client-side DNS values. These
223 values were unused by default previously, but they should not have
224 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
227 Changes in version 0.3.1.9 - 2017-12-01:
228 Tor 0.3.1.9 backports important security and stability fixes from the
229 0.3.2 development series. All Tor users should upgrade to this
230 release, or to another of the releases coming out today.
232 o Major bugfixes (security, backport from 0.3.2.6-alpha):
233 - Fix a denial of service bug where an attacker could use a
234 malformed directory object to cause a Tor instance to pause while
235 OpenSSL would try to read a passphrase from the terminal. (Tor
236 instances run without a terminal, which is the case for most Tor
237 packages, are not impacted.) Fixes bug 24246; bugfix on every
238 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
239 Found by OSS-Fuzz as testcase 6360145429790720.
240 - Fix a denial of service issue where an attacker could crash a
241 directory authority using a malformed router descriptor. Fixes bug
242 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
244 - When checking for replays in the INTRODUCE1 cell data for a
245 (legacy) onion service, correctly detect replays in the RSA-
246 encrypted part of the cell. We were previously checking for
247 replays on the entire cell, but those can be circumvented due to
248 the malleability of Tor's legacy hybrid encryption. This fix helps
249 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
250 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
253 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
254 - Fix a use-after-free error that could crash v2 Tor onion services
255 when they failed to open circuits while expiring introduction
256 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
257 also tracked as TROVE-2017-013 and CVE-2017-8823.
259 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
260 - When running as a relay, make sure that we never build a path
261 through ourselves, even in the case where we have somehow lost the
262 version of our descriptor appearing in the consensus. Fixes part
263 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
264 as TROVE-2017-012 and CVE-2017-8822.
265 - When running as a relay, make sure that we never choose ourselves
266 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
267 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
269 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
270 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
271 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
272 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
273 identifying and finding a workaround to this bug and to Moritz,
274 Arthur Edelstein, and Roger for helping to track it down and
277 o Minor features (bridge):
278 - Bridges now include notice in their descriptors that they are
279 bridges, and notice of their distribution status, based on their
280 publication settings. Implements ticket 18329. For more fine-
281 grained control of how a bridge is distributed, upgrade to 0.3.2.x
284 o Minor features (directory authority, backport from 0.3.2.6-alpha):
285 - Add an IPv6 address for the "bastet" directory authority. Closes
288 o Minor features (geoip):
289 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
292 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
293 - Avoid unnecessary calls to directory_fetches_from_authorities() on
294 relays, to prevent spurious address resolutions and descriptor
295 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
296 bugfix on in 0.2.8.1-alpha.
298 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
299 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
300 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
302 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
303 - When a circuit is marked for close, do not attempt to package any
304 cells for channels on that circuit. Previously, we would detect
305 this condition lower in the call stack, when we noticed that the
306 circuit had no attached channel, and log an annoying message.
307 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
309 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
310 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
311 so it matches dir-spec.txt. Fixes bug 24262; bugfix
314 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
315 - Avoid a crash when transitioning from client mode to bridge mode.
316 Previously, we would launch the worker threads whenever our
317 "public server" mode changed, but not when our "server" mode
318 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
321 Changes in version 0.3.0.13 - 2017-12-01
322 Tor 0.3.0.13 backports important security and stability bugfixes from
323 later Tor releases. All Tor users should upgrade to this release, or
324 to another of the releases coming out today.
326 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
327 2018. If you need a release with long-term support, please stick with
328 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
330 o Major bugfixes (security, backport from 0.3.2.6-alpha):
331 - Fix a denial of service bug where an attacker could use a
332 malformed directory object to cause a Tor instance to pause while
333 OpenSSL would try to read a passphrase from the terminal. (Tor
334 instances run without a terminal, which is the case for most Tor
335 packages, are not impacted.) Fixes bug 24246; bugfix on every
336 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
337 Found by OSS-Fuzz as testcase 6360145429790720.
338 - Fix a denial of service issue where an attacker could crash a
339 directory authority using a malformed router descriptor. Fixes bug
340 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
342 - When checking for replays in the INTRODUCE1 cell data for a
343 (legacy) onion service, correctly detect replays in the RSA-
344 encrypted part of the cell. We were previously checking for
345 replays on the entire cell, but those can be circumvented due to
346 the malleability of Tor's legacy hybrid encryption. This fix helps
347 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
348 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
351 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
352 - Fix a use-after-free error that could crash v2 Tor onion services
353 when they failed to open circuits while expiring introduction
354 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
355 also tracked as TROVE-2017-013 and CVE-2017-8823.
357 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
358 - When running as a relay, make sure that we never build a path
359 through ourselves, even in the case where we have somehow lost the
360 version of our descriptor appearing in the consensus. Fixes part
361 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
362 as TROVE-2017-012 and CVE-2017-8822.
363 - When running as a relay, make sure that we never choose ourselves
364 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
365 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
367 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
368 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
369 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
370 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
371 identifying and finding a workaround to this bug and to Moritz,
372 Arthur Edelstein, and Roger for helping to track it down and
375 o Minor features (security, windows, backport from 0.3.1.1-alpha):
376 - Enable a couple of pieces of Windows hardening: one
377 (HeapEnableTerminationOnCorruption) that has been on-by-default
378 since Windows 8, and unavailable before Windows 7; and one
379 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
380 affect us, but shouldn't do any harm. Closes ticket 21953.
382 o Minor features (bridge, backport from 0.3.1.9):
383 - Bridges now include notice in their descriptors that they are
384 bridges, and notice of their distribution status, based on their
385 publication settings. Implements ticket 18329. For more fine-
386 grained control of how a bridge is distributed, upgrade to 0.3.2.x
389 o Minor features (directory authority, backport from 0.3.2.6-alpha):
390 - Add an IPv6 address for the "bastet" directory authority. Closes
393 o Minor features (geoip):
394 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
397 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
398 - Avoid unnecessary calls to directory_fetches_from_authorities() on
399 relays, to prevent spurious address resolutions and descriptor
400 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
401 bugfix on in 0.2.8.1-alpha.
403 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
404 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
405 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
407 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
408 - When a circuit is marked for close, do not attempt to package any
409 cells for channels on that circuit. Previously, we would detect
410 this condition lower in the call stack, when we noticed that the
411 circuit had no attached channel, and log an annoying message.
412 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
414 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
415 - Avoid a crash when transitioning from client mode to bridge mode.
416 Previously, we would launch the worker threads whenever our
417 "public server" mode changed, but not when our "server" mode
418 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
420 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
421 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
422 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
425 Changes in version 0.2.9.14 - 2017-12-01
426 Tor 0.3.0.13 backports important security and stability bugfixes from
427 later Tor releases. All Tor users should upgrade to this release, or
428 to another of the releases coming out today.
430 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
431 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
432 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
433 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
434 identifying and finding a workaround to this bug and to Moritz,
435 Arthur Edelstein, and Roger for helping to track it down and
438 o Major bugfixes (security, backport from 0.3.2.6-alpha):
439 - Fix a denial of service bug where an attacker could use a
440 malformed directory object to cause a Tor instance to pause while
441 OpenSSL would try to read a passphrase from the terminal. (Tor
442 instances run without a terminal, which is the case for most Tor
443 packages, are not impacted.) Fixes bug 24246; bugfix on every
444 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
445 Found by OSS-Fuzz as testcase 6360145429790720.
446 - Fix a denial of service issue where an attacker could crash a
447 directory authority using a malformed router descriptor. Fixes bug
448 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
450 - When checking for replays in the INTRODUCE1 cell data for a
451 (legacy) onion service, correctly detect replays in the RSA-
452 encrypted part of the cell. We were previously checking for
453 replays on the entire cell, but those can be circumvented due to
454 the malleability of Tor's legacy hybrid encryption. This fix helps
455 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
456 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
459 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
460 - Fix a use-after-free error that could crash v2 Tor onion services
461 when they failed to open circuits while expiring introduction
462 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
463 also tracked as TROVE-2017-013 and CVE-2017-8823.
465 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
466 - When running as a relay, make sure that we never build a path
467 through ourselves, even in the case where we have somehow lost the
468 version of our descriptor appearing in the consensus. Fixes part
469 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
470 as TROVE-2017-012 and CVE-2017-8822.
472 o Minor features (bridge, backport from 0.3.1.9):
473 - Bridges now include notice in their descriptors that they are
474 bridges, and notice of their distribution status, based on their
475 publication settings. Implements ticket 18329. For more fine-
476 grained control of how a bridge is distributed, upgrade to 0.3.2.x
479 o Minor features (directory authority, backport from 0.3.2.6-alpha):
480 - Add an IPv6 address for the "bastet" directory authority. Closes
483 o Minor features (geoip):
484 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
487 o Minor features (security, windows, backport from 0.3.1.1-alpha):
488 - Enable a couple of pieces of Windows hardening: one
489 (HeapEnableTerminationOnCorruption) that has been on-by-default
490 since Windows 8, and unavailable before Windows 7; and one
491 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
492 affect us, but shouldn't do any harm. Closes ticket 21953.
494 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
495 - Avoid unnecessary calls to directory_fetches_from_authorities() on
496 relays, to prevent spurious address resolutions and descriptor
497 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
498 bugfix on in 0.2.8.1-alpha.
500 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
501 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
502 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
504 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
505 - When a circuit is marked for close, do not attempt to package any
506 cells for channels on that circuit. Previously, we would detect
507 this condition lower in the call stack, when we noticed that the
508 circuit had no attached channel, and log an annoying message.
509 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
511 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
512 - Avoid a crash when transitioning from client mode to bridge mode.
513 Previously, we would launch the worker threads whenever our
514 "public server" mode changed, but not when our "server" mode
515 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
517 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
518 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
519 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
522 Changes in version 0.2.8.17 - 2017-12-01
523 Tor 0.2.8.17 backports important security and stability bugfixes from
524 later Tor releases. All Tor users should upgrade to this release, or
525 to another of the releases coming out today.
527 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
528 2018. If you need a release with long-term support, please upgrade with
529 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
531 o Major bugfixes (security, backport from 0.3.2.6-alpha):
532 - Fix a denial of service bug where an attacker could use a
533 malformed directory object to cause a Tor instance to pause while
534 OpenSSL would try to read a passphrase from the terminal. (Tor
535 instances run without a terminal, which is the case for most Tor
536 packages, are not impacted.) Fixes bug 24246; bugfix on every
537 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
538 Found by OSS-Fuzz as testcase 6360145429790720.
539 - When checking for replays in the INTRODUCE1 cell data for a
540 (legacy) onion service, correctly detect replays in the RSA-
541 encrypted part of the cell. We were previously checking for
542 replays on the entire cell, but those can be circumvented due to
543 the malleability of Tor's legacy hybrid encryption. This fix helps
544 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
545 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
548 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
549 - Fix a use-after-free error that could crash v2 Tor onion services
550 when they failed to open circuits while expiring introduction
551 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
552 also tracked as TROVE-2017-013 and CVE-2017-8823.
554 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
555 - When running as a relay, make sure that we never build a path through
556 ourselves, even in the case where we have somehow lost the version of
557 our descriptor appearing in the consensus. Fixes part of bug 21534;
558 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
561 o Minor features (bridge, backport from 0.3.1.9):
562 - Bridges now include notice in their descriptors that they are
563 bridges, and notice of their distribution status, based on their
564 publication settings. Implements ticket 18329. For more fine-
565 grained control of how a bridge is distributed, upgrade to 0.3.2.x
568 o Minor features (directory authority, backport from 0.3.2.6-alpha):
569 - Add an IPv6 address for the "bastet" directory authority. Closes
572 o Minor features (geoip):
573 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
576 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
577 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
578 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
581 Changes in version 0.2.5.16 - 2017-12-01
582 Tor 0.2.5.13 backports important security and stability bugfixes from
583 later Tor releases. All Tor users should upgrade to this release, or
584 to another of the releases coming out today.
586 Note: the Tor 0.2.5 series will no longer be supported after 1 May
587 2018. If you need a release with long-term support, please upgrade to
588 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
590 o Major bugfixes (security, backport from 0.3.2.6-alpha):
591 - Fix a denial of service bug where an attacker could use a
592 malformed directory object to cause a Tor instance to pause while
593 OpenSSL would try to read a passphrase from the terminal. (Tor
594 instances run without a terminal, which is the case for most Tor
595 packages, are not impacted.) Fixes bug 24246; bugfix on every
596 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
597 Found by OSS-Fuzz as testcase 6360145429790720.
598 - When checking for replays in the INTRODUCE1 cell data for a
599 (legacy) onion service, correctly detect replays in the RSA-
600 encrypted part of the cell. We were previously checking for
601 replays on the entire cell, but those can be circumvented due to
602 the malleability of Tor's legacy hybrid encryption. This fix helps
603 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
604 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
607 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
608 - When running as a relay, make sure that we never build a path
609 through ourselves, even in the case where we have somehow lost the
610 version of our descriptor appearing in the consensus. Fixes part
611 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
612 as TROVE-2017-012 and CVE-2017-8822.
614 o Minor features (bridge, backport from 0.3.1.9):
615 - Bridges now include notice in their descriptors that they are
616 bridges, and notice of their distribution status, based on their
617 publication settings. Implements ticket 18329. For more fine-
618 grained control of how a bridge is distributed, upgrade to 0.3.2.x
621 o Minor features (geoip):
622 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
626 Changes in version 0.3.2.5-alpha - 2017-11-22
627 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
628 fixes several stability and reliability bugs, including a fix for
629 intermittent bootstrapping failures that some people have been seeing
630 since the 0.3.0.x series.
632 Please test this alpha out -- many of these fixes will soon be
633 backported to stable Tor versions if no additional bugs are found
636 o Major bugfixes (bootstrapping):
637 - Fetch descriptors aggressively whenever we lack enough to build
638 circuits, regardless of how many descriptors we are missing.
639 Previously, we would delay launching the fetch when we had fewer
640 than 15 missing descriptors, even if some of those descriptors
641 were blocking circuits from building. Fixes bug 23985; bugfix on
642 0.1.1.11-alpha. The effects of this bug became worse in
643 0.3.0.3-alpha, when we began treating missing descriptors from our
644 primary guards as a reason to delay circuits.
645 - Don't try fetching microdescriptors from relays that have failed
646 to deliver them in the past. Fixes bug 23817; bugfix
649 o Minor features (directory authority):
650 - Make the "Exit" flag assignment only depend on whether the exit
651 policy allows connections to ports 80 and 443. Previously relays
652 would get the Exit flag if they allowed connections to one of
653 these ports and also port 6667. Resolves ticket 23637.
655 o Minor features (geoip):
656 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
659 o Minor features (linux seccomp2 sandbox):
660 - Update the sandbox rules so that they should now work correctly
661 with Glibc 2.26. Closes ticket 24315.
663 o Minor features (logging):
664 - Downgrade a pair of log messages that could occur when an exit's
665 resolver gave us an unusual (but not forbidden) response. Closes
667 - Improve the message we log when re-enabling circuit build timeouts
668 after having received a consensus. Closes ticket 20963.
670 o Minor bugfixes (compilation):
671 - Fix a memory leak warning in one of the libevent-related
672 configuration tests that could occur when manually specifying
673 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
674 Found and patched by Alex Xu.
675 - When detecting OpenSSL on Windows from our configure script, make
676 sure to try linking with the ws2_32 library. Fixes bug 23783;
677 bugfix on 0.3.2.2-alpha.
679 o Minor bugfixes (control port, linux seccomp2 sandbox):
680 - Avoid a crash when attempting to use the seccomp2 sandbox together
681 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
684 o Minor bugfixes (control port, onion services):
685 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
686 HS_DESC event when a service is not able to upload a descriptor.
687 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
689 o Minor bugfixes (directory cache):
690 - Recover better from empty or corrupt files in the consensus cache
691 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
692 - When a consensus diff calculation is only partially successful,
693 only record the successful parts as having succeeded. Partial
694 success can happen if (for example) one compression method fails
695 but the others succeed. Previously we misrecorded all the
696 calculations as having succeeded, which would later cause a
697 nonfatal assertion failure. Fixes bug 24086; bugfix
700 o Minor bugfixes (logging):
701 - Only log once if we notice that KIST support is gone. Fixes bug
702 24158; bugfix on 0.3.2.1-alpha.
703 - Suppress a log notice when relay descriptors arrive. We already
704 have a bootstrap progress for this so no need to log notice
705 everytime tor receives relay descriptors. Microdescriptors behave
706 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
708 o Minor bugfixes (network layer):
709 - When closing a connection via close_connection_immediately(), we
710 mark it as "not blocked on bandwidth", to prevent later calls from
711 trying to unblock it, and give it permission to read. This fixes a
712 backtrace warning that can happen on relays under various
713 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
715 o Minor bugfixes (onion services):
716 - The introduction circuit was being timed out too quickly while
717 waiting for the rendezvous circuit to complete. Keep the intro
718 circuit around longer instead of timing out and reopening new ones
719 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
720 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
721 so it matches dir-spec.txt. Fixes bug 24262; bugfix
723 - Silence a warning about failed v3 onion descriptor uploads that
724 can happen naturally under certain edge cases. Fixes part of bug
725 23662; bugfix on 0.3.2.1-alpha.
727 o Minor bugfixes (tests):
728 - Fix a memory leak in one of the bridge-distribution test cases.
729 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
730 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
731 to correctly handle cases where a caller gives it an RSA key of
732 under 160 bits. (This is not actually a bug in Tor itself, but
733 rather in our fuzzing code.) Fixes bug 24247; bugfix on
734 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
737 - Add notes in man page regarding OS support for the various
738 scheduler types. Attempt to use less jargon in the scheduler
739 section. Closes ticket 24254.
742 Changes in version 0.3.2.4-alpha - 2017-11-08
743 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
744 It fixes several stability and reliability bugs, especially including
745 a major reliability issue that has been plaguing fast exit relays in
748 o Major bugfixes (exit relays, DNS):
749 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
750 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
751 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
752 identifying and finding a workaround to this bug and to Moritz,
753 Arthur Edelstein, and Roger for helping to track it down and
756 o Major bugfixes (scheduler, channel):
757 - Stop processing scheduled channels if they closed while flushing
758 cells. This can happen if the write on the connection fails
759 leading to the channel being closed while in the scheduler loop.
760 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
762 o Minor features (logging, scheduler):
763 - Introduce a SCHED_BUG() function to log extra information about
764 the scheduler state if we ever catch a bug in the scheduler.
767 o Minor features (removed deprecations):
768 - The ClientDNSRejectInternalAddresses flag can once again be set in
769 non-testing Tor networks, so long as they do not use the default
770 directory authorities. This change also removes the deprecation of
771 this flag from 0.2.9.2-alpha. Closes ticket 21031.
773 o Minor features (testing):
774 - Our fuzzing tests now test the encrypted portions of v3 onion
775 service descriptors. Implements more of 21509.
777 o Minor bugfixes (directory client):
778 - On failure to download directory information, delay retry attempts
779 by a random amount based on the "decorrelated jitter" algorithm.
780 Our previous delay algorithm tended to produce extra-long delays
781 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
783 o Minor bugfixes (IPv6, v3 single onion services):
784 - Remove buggy code for IPv6-only v3 single onion services, and
785 reject attempts to configure them. This release supports IPv4,
786 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
787 stack v3 single onion services. Fixes bug 23820; bugfix
790 o Minor bugfixes (logging, relay):
791 - Give only a protocol warning when the ed25519 key is not
792 consistent between the descriptor and microdescriptor of a relay.
793 This can happen, for instance, if the relay has been flagged
794 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
796 o Minor bugfixes (manpage, onion service):
797 - Document that the HiddenServiceNumIntroductionPoints option is
798 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
799 bugfix on 0.3.2.1-alpha.
801 o Minor bugfixes (memory leaks):
802 - Fix a minor memory leak at exit in the KIST scheduler. This bug
803 should have no user-visible impact. Fixes bug 23774; bugfix
805 - Fix a memory leak when decrypting a badly formatted v3 onion
806 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
807 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
809 o Minor bugfixes (onion services):
810 - Cache some needed onion service client information instead of
811 constantly computing it over and over again. Fixes bug 23623;
812 bugfix on 0.3.2.1-alpha.
813 - Properly retry HSv3 descriptor fetches when missing required
814 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
816 o Minor bugfixes (path selection):
817 - When selecting relays by bandwidth, avoid a rounding error that
818 could sometimes cause load to be imbalanced incorrectly.
819 Previously, we would always round upwards; now, we round towards
820 the nearest integer. This had the biggest effect when a relay's
821 weight adjustments should have given it weight 0, but it got
822 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
823 - When calculating the fraction of nodes that have descriptors, and
824 all nodes in the network have zero bandwidths, count the number of
825 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
826 - Actually log the total bandwidth in compute_weighted_bandwidths().
827 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
829 o Minor bugfixes (relay, crash):
830 - Avoid a crash when transitioning from client mode to bridge mode.
831 Previously, we would launch the worker threads whenever our
832 "public server" mode changed, but not when our "server" mode
833 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
835 o Minor bugfixes (testing):
836 - Fix a spurious fuzzing-only use of an uninitialized value. Found
837 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
838 - Test that IPv6-only clients can use microdescriptors when running
839 "make test-network-all". Requires chutney master 61c28b9 or later.
843 Changes in version 0.3.2.3-alpha - 2017-10-27
844 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
845 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
846 directory authority, Bastet.
848 o Directory authority changes:
849 - Add "Bastet" as a ninth directory authority to the default list.
851 - The directory authority "Longclaw" has changed its IP address.
854 o Minor features (bridge):
855 - Bridge relays can now set the BridgeDistribution config option to
856 add a "bridge-distribution-request" line to their bridge
857 descriptor, which tells BridgeDB how they'd like their bridge
858 address to be given out. (Note that as of Oct 2017, BridgeDB does
859 not yet implement this feature.) As a side benefit, this feature
860 provides a way to distinguish bridge descriptors from non-bridge
861 descriptors. Implements tickets 18329.
863 o Minor features (client, entry guards):
864 - Improve log messages when missing descriptors for primary guards.
865 Resolves ticket 23670.
867 o Minor features (geoip):
868 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
871 o Minor bugfixes (bridge):
872 - Overwrite the bridge address earlier in the process of retrieving
873 its descriptor, to make sure we reach it on the configured
874 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
876 o Minor bugfixes (documentation):
877 - Document better how to read gcov, and what our gcov postprocessing
878 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
880 o Minor bugfixes (entry guards):
881 - Tor now updates its guard state when it reads a consensus
882 regardless of whether it's missing descriptors. That makes tor use
883 its primary guards to fetch descriptors in some edge cases where
884 it would previously have used fallback directories. Fixes bug
885 23862; bugfix on 0.3.0.1-alpha.
887 o Minor bugfixes (hidden service client):
888 - When handling multiple SOCKS request for the same .onion address,
889 only fetch the service descriptor once.
890 - When a descriptor fetch fails with a non-recoverable error, close
891 all pending SOCKS requests for that .onion. Fixes bug 23653;
892 bugfix on 0.3.2.1-alpha.
894 o Minor bugfixes (hidden service):
895 - Always regenerate missing hidden service public key files. Prior
896 to this, if the public key was deleted from disk, it wouldn't get
897 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
899 - Make sure that we have a usable ed25519 key when the intro point
900 relay supports ed25519 link authentication. Fixes bug 24002;
901 bugfix on 0.3.2.1-alpha.
903 o Minor bugfixes (hidden service, v2):
904 - When reloading configured hidden services, copy all information
905 from the old service object. Previously, some data was omitted,
906 causing delays in descriptor upload, and other bugs. Fixes bug
907 23790; bugfix on 0.2.1.9-alpha.
909 o Minor bugfixes (memory safety, defensive programming):
910 - Clear the target address when node_get_prim_orport() returns
911 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
913 o Minor bugfixes (relay):
914 - Avoid a BUG warning when receiving a dubious CREATE cell while an
915 option transition is in progress. Fixes bug 23952; bugfix
918 o Minor bugfixes (testing):
919 - Adjust the GitLab CI configuration to more closely match that of
920 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
921 - Prevent scripts/test/coverage from attempting to move gcov output
922 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
923 - When running unit tests as root, skip a test that would fail
924 because it expects a permissions error. This affects some
925 continuous integration setups. Fixes bug 23758; bugfix
927 - Stop unconditionally mirroring the tor repository in GitLab CI.
928 This prevented developers from enabling GitLab CI on master. Fixes
929 bug 23755; bugfix on 0.3.2.2-alpha.
930 - Fix the hidden service v3 descriptor decoding fuzzing to use the
931 latest decoding API correctly. Fixes bug 21509; bugfix
934 o Minor bugfixes (warnings):
935 - When we get an HTTP request on a SOCKS port, tell the user about
936 the new HTTPTunnelPort option. Previously, we would give a "Tor is
937 not an HTTP Proxy" message, which stopped being true when
938 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
942 Changes in version 0.2.5.15 - 2017-10-25
943 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
944 series. It also adds a new directory authority, Bastet.
946 Note: the Tor 0.2.5 series will no longer be supported after 1 May
947 2018. If you need a release with long-term support, please upgrade to
948 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
950 o Directory authority changes:
951 - Add "Bastet" as a ninth directory authority to the default list.
953 - The directory authority "Longclaw" has changed its IP address.
956 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
957 - Avoid an assertion failure bug affecting our implementation of
958 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
959 handling of "0xx" differs from what we had expected. Fixes bug
960 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
962 o Minor features (geoip):
963 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
966 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
967 - Fix a memset() off the end of an array when packing cells. This
968 bug should be harmless in practice, since the corrupted bytes are
969 still in the same structure, and are always padding bytes,
970 ignored, or immediately overwritten, depending on compiler
971 behavior. Nevertheless, because the memset()'s purpose is to make
972 sure that any other cell-handling bugs can't expose bytes to the
973 network, we need to fix it. Fixes bug 22737; bugfix on
974 0.2.4.11-alpha. Fixes CID 1401591.
976 o Build features (backport from 0.3.1.5-alpha):
977 - Tor's repository now includes a Travis Continuous Integration (CI)
978 configuration file (.travis.yml). This is meant to help new
979 developers and contributors who fork Tor to a Github repository be
980 better able to test their changes, and understand what we expect
981 to pass. To use this new build feature, you must fork Tor to your
982 Github account, then go into the "Integrations" menu in the
983 repository settings for your fork and enable Travis, then push
984 your changes. Closes ticket 22636.
987 Changes in version 0.2.8.16 - 2017-10-25
988 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
989 series, including a bugfix for a crash issue that had affected relays
990 under memory pressure. It also adds a new directory authority, Bastet.
992 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
993 2018. If you need a release with long-term support, please stick with
994 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
996 o Directory authority changes:
997 - Add "Bastet" as a ninth directory authority to the default list.
999 - The directory authority "Longclaw" has changed its IP address.
1000 Closes ticket 23592.
1002 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1003 - Fix a timing-based assertion failure that could occur when the
1004 circuit out-of-memory handler freed a connection's output buffer.
1005 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1007 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1008 - Remove longclaw's IPv6 address, as it will soon change. Authority
1009 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1010 3/8 directory authorities with IPv6 addresses, but there are also
1011 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1013 o Minor features (geoip):
1014 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1018 Changes in version 0.2.9.13 - 2017-10-25
1019 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
1020 series, including a bugfix for a crash issue that had affected relays
1021 under memory pressure. It also adds a new directory authority, Bastet.
1023 o Directory authority changes:
1024 - Add "Bastet" as a ninth directory authority to the default list.
1025 Closes ticket 23910.
1026 - The directory authority "Longclaw" has changed its IP address.
1027 Closes ticket 23592.
1029 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1030 - Fix a timing-based assertion failure that could occur when the
1031 circuit out-of-memory handler freed a connection's output buffer.
1032 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1034 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1035 - Remove longclaw's IPv6 address, as it will soon change. Authority
1036 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1037 3/8 directory authorities with IPv6 addresses, but there are also
1038 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1040 o Minor features (geoip):
1041 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1044 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
1045 - When a directory authority rejects a descriptor or extrainfo with
1046 a given digest, mark that digest as undownloadable, so that we do
1047 not attempt to download it again over and over. We previously
1048 tried to avoid downloading such descriptors by other means, but we
1049 didn't notice if we accidentally downloaded one anyway. This
1050 behavior became problematic in 0.2.7.2-alpha, when authorities
1051 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1054 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1055 - Clear the address when node_get_prim_orport() returns early.
1056 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1058 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
1059 - When running as a Windows service, set the ID of the main thread
1060 correctly. Failure to do so made us fail to send log messages to
1061 the controller in 0.2.1.16-rc, slowed down controller event
1062 delivery in 0.2.7.3-rc and later, and crash with an assertion
1063 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1064 Patch and diagnosis from "Vort".
1067 Changes in version 0.3.0.12 - 2017-10-25
1068 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
1069 series, including a bugfix for a crash issue that had affected relays
1070 under memory pressure. It also adds a new directory authority, Bastet.
1072 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
1073 2018. If you need a release with long-term support, please stick with
1074 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1076 o Directory authority changes:
1077 - Add "Bastet" as a ninth directory authority to the default list.
1078 Closes ticket 23910.
1079 - The directory authority "Longclaw" has changed its IP address.
1080 Closes ticket 23592.
1082 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1083 - Fix a timing-based assertion failure that could occur when the
1084 circuit out-of-memory handler freed a connection's output buffer.
1085 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1087 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1088 - Remove longclaw's IPv6 address, as it will soon change. Authority
1089 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1090 3/8 directory authorities with IPv6 addresses, but there are also
1091 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1093 o Minor features (geoip):
1094 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1097 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
1098 - When a directory authority rejects a descriptor or extrainfo with
1099 a given digest, mark that digest as undownloadable, so that we do
1100 not attempt to download it again over and over. We previously
1101 tried to avoid downloading such descriptors by other means, but we
1102 didn't notice if we accidentally downloaded one anyway. This
1103 behavior became problematic in 0.2.7.2-alpha, when authorities
1104 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1107 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1108 - Avoid a possible double close of a circuit by the intro point on
1109 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1110 bugfix on 0.3.0.1-alpha.
1112 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1113 - Clear the address when node_get_prim_orport() returns early.
1114 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1116 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
1117 - When running as a Windows service, set the ID of the main thread
1118 correctly. Failure to do so made us fail to send log messages to
1119 the controller in 0.2.1.16-rc, slowed down controller event
1120 delivery in 0.2.7.3-rc and later, and crash with an assertion
1121 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1122 Patch and diagnosis from "Vort".
1125 Changes in version 0.3.1.8 - 2017-10-25
1126 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
1127 It includes several bugfixes, including a bugfix for a crash issue
1128 that had affected relays under memory pressure. It also adds
1129 a new directory authority, Bastet.
1131 o Directory authority changes:
1132 - Add "Bastet" as a ninth directory authority to the default list.
1133 Closes ticket 23910.
1134 - The directory authority "Longclaw" has changed its IP address.
1135 Closes ticket 23592.
1137 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1138 - Fix a timing-based assertion failure that could occur when the
1139 circuit out-of-memory handler freed a connection's output buffer.
1140 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1142 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1143 - Remove longclaw's IPv6 address, as it will soon change. Authority
1144 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1145 3/8 directory authorities with IPv6 addresses, but there are also
1146 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1148 o Minor features (geoip):
1149 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1152 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
1153 - Fix a compilation warning when building with zstd support on
1154 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1155 and fixed by Andreas Stieger.
1157 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
1158 - Handle a pathological case when decompressing Zstandard data when
1159 the output buffer size is zero. Fixes bug 23551; bugfix
1162 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
1163 - Remove the length limit on HTTP status lines that authorities can
1164 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
1166 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1167 - Avoid a possible double close of a circuit by the intro point on
1168 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1169 bugfix on 0.3.0.1-alpha.
1171 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1172 - Clear the address when node_get_prim_orport() returns early.
1173 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1175 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
1176 - Fix additional channelpadding unit test failures by using mocked
1177 time instead of actual time for all tests. Fixes bug 23608; bugfix
1181 Changes in version 0.3.2.2-alpha - 2017-09-29
1182 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
1183 release fixes several minor bugs in the new scheduler and next-
1184 generation onion services; both features were newly added in the 0.3.2
1185 series. Other fixes in this alpha include several fixes for non-fatal
1186 tracebacks which would appear in logs.
1188 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
1189 alpha does not contain any substantial new features. Minor features
1190 include better testing and logging.
1192 The following comprises the complete list of changes included
1193 in tor-0.3.2.2-alpha:
1195 o Major bugfixes (relay, crash, assertion failure):
1196 - Fix a timing-based assertion failure that could occur when the
1197 circuit out-of-memory handler freed a connection's output buffer.
1198 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1200 o Major bugfixes (scheduler):
1201 - If a channel is put into the scheduler's pending list, then it
1202 starts closing, and then if the scheduler runs before it finishes
1203 closing, the scheduler will get stuck trying to flush its cells
1204 while the lower layers refuse to cooperate. Fix that race
1205 condition by giving the scheduler an escape method. Fixes bug
1206 23676; bugfix on 0.3.2.1-alpha.
1208 o Minor features (build, compilation):
1209 - The "check-changes" feature is now part of the "make check" tests;
1210 we'll use it to try to prevent misformed changes files from
1211 accumulating. Closes ticket 23564.
1212 - Tor builds should now fail if there are any mismatches between the
1213 C type representing a configuration variable and the C type the
1214 data-driven parser uses to store a value there. Previously, we
1215 needed to check these by hand, which sometimes led to mistakes.
1216 Closes ticket 23643.
1218 o Minor features (directory authorities):
1219 - Remove longclaw's IPv6 address, as it will soon change. Authority
1220 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1221 3/8 directory authorities with IPv6 addresses, but there are also
1222 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1224 o Minor features (hidden service, circuit, logging):
1225 - Improve logging of many callsite in the circuit subsystem to print
1226 the circuit identifier(s).
1227 - Log when we cleanup an intro point from a service so we know when
1228 and for what reason it happened. Closes ticket 23604.
1230 o Minor features (logging):
1231 - Log more circuit information whenever we are about to try to
1232 package a relay cell on a circuit with a nonexistent n_chan.
1233 Attempt to diagnose ticket 8185.
1234 - Improve info-level log identification of particular circuits, to
1235 help with debugging. Closes ticket 23645.
1237 o Minor features (relay):
1238 - When choosing which circuits can be expired as unused, consider
1239 circuits from clients even if those clients used regular CREATE
1240 cells to make them; and do not consider circuits from relays even
1241 if they were made with CREATE_FAST. Part of ticket 22805.
1243 o Minor features (robustness):
1244 - Change several fatal assertions when flushing buffers into non-
1245 fatal assertions, to prevent any recurrence of 23690.
1247 o Minor features (spec conformance, bridge, diagnostic):
1248 - When handling the USERADDR command on an ExtOrPort, warn when the
1249 transports provides a USERADDR with no port. In a future version,
1250 USERADDR commands of this format may be rejected. Detects problems
1251 related to ticket 23080.
1253 o Minor features (testing):
1254 - Add a unit test to make sure that our own generated platform
1255 string will be accepted by directory authorities. Closes
1258 o Minor bugfixes (bootstrapping):
1259 - When warning about state file clock skew, report the correct
1260 direction for the detected skew. Fixes bug 23606; bugfix
1262 - Avoid an assertion failure when logging a state file clock skew
1263 very early in bootstrapping. Fixes bug 23607; bugfix
1266 o Minor bugfixes (build, compilation):
1267 - Fix a compilation warning when building with zstd support on
1268 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1269 and fixed by Andreas Stieger.
1270 - When searching for OpenSSL, don't accept any OpenSSL library that
1271 lacks TLSv1_1_method(): Tor doesn't build with those versions.
1272 Additionally, look in /usr/local/opt/openssl, if it's present.
1273 These changes together repair the default build on OSX systems
1274 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
1276 o Minor bugfixes (compression):
1277 - Handle a pathological case when decompressing Zstandard data when
1278 the output buffer size is zero. Fixes bug 23551; bugfix
1281 o Minor bugfixes (documentation):
1282 - Fix manpage to not refer to the obsolete (and misspelled)
1283 UseEntryGuardsAsDirectoryGuards parameter in the description of
1284 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
1286 o Minor bugfixes (hidden service v3):
1287 - Don't log an assertion failure when we can't find the right
1288 information to extend to an introduction point. In rare cases,
1289 this could happen, causing a warning, even though tor would
1290 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
1291 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
1292 much bigger so the rendezvous point can't distinguish which hidden
1293 service protocol is being used. Fixes bug 23420; bugfix
1296 o Minor bugfixes (hidden service, relay):
1297 - Avoid a possible double close of a circuit by the intro point on
1298 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1299 bugfix on 0.3.0.1-alpha.
1301 o Minor bugfixes (logging, relay shutdown, annoyance):
1302 - When a circuit is marked for close, do not attempt to package any
1303 cells for channels on that circuit. Previously, we would detect
1304 this condition lower in the call stack, when we noticed that the
1305 circuit had no attached channel, and log an annoying message.
1306 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1308 o Minor bugfixes (scheduler):
1309 - When switching schedulers due to a consensus change, we didn't
1310 give the new scheduler a chance to react to the consensus. Fix
1311 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
1312 - Make the KISTSchedRunInterval option a non negative value. With
1313 this, the way to disable KIST through the consensus is to set it
1314 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
1315 - Only notice log the selected scheduler when we switch scheduler
1316 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
1317 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
1318 by a different tv_usec data type. Fixes bug 23575; bugfix
1320 - Make a hard exit if tor is unable to pick a scheduler which can
1321 happen if the user specifies a scheduler type that is not
1322 supported and not other types in Schedulers. Fixes bug 23581;
1323 bugfix on 0.3.2.1-alpha.
1324 - Properly initialize the scheduler last run time counter so it is
1325 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
1327 o Minor bugfixes (testing):
1328 - Capture and detect several "Result does not fit" warnings in unit
1329 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
1331 - Fix additional channelpadding unit test failures by using mocked
1332 time instead of actual time for all tests. Fixes bug 23608; bugfix
1334 - The removal of some old scheduler options caused some tests to
1335 fail on BSD systems. Assume current behavior is correct and make
1336 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
1338 o Code simplification and refactoring:
1339 - Remove various ways of testing circuits and connections for
1340 "clientness"; instead, favor channel_is_client(). Part of
1343 o Deprecated features:
1344 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
1345 now deprecated; they do not apply to relays, and they have had no
1346 effect on clients since 0.2.8.x. Closes ticket 19704.
1349 - HiddenServiceVersion man page entry wasn't mentioning the now
1350 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
1351 - Clarify that the Address option is entirely about setting an
1352 advertised IPv4 address. Closes ticket 18891.
1353 - Clarify the manpage's use of the term "address" to clarify what
1354 kind of address is intended. Closes ticket 21405.
1355 - Document that onion service subdomains are allowed, and ignored.
1356 Closes ticket 18736.
1359 Changes in version 0.3.2.1-alpha - 2017-09-18
1360 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
1361 includes support for our next-generation ("v3") onion service
1362 protocol, and adds a new circuit scheduler for more responsive
1363 forwarding decisions from relays. There are also numerous other small
1364 features and bugfixes here.
1366 Below are the changes since Tor 0.3.1.7.
1368 o Major feature (scheduler, channel):
1369 - Tor now uses new schedulers to decide which circuits should
1370 deliver cells first, in order to improve congestion at relays. The
1371 first type is called "KIST" ("Kernel Informed Socket Transport"),
1372 and is only available on Linux-like systems: it uses feedback from
1373 the kernel to prevent the kernel's TCP buffers from growing too
1374 full. The second new scheduler type is called "KISTLite": it
1375 behaves the same as KIST, but runs on systems without kernel
1376 support for inspecting TCP implementation details. The old
1377 scheduler is still available, under the name "Vanilla". To change
1378 the default scheduler preference order, use the new "Schedulers"
1379 option. (The default preference order is "KIST,KISTLite,Vanilla".)
1381 Matt Traudt implemented KIST, based on research by Rob Jansen,
1382 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
1383 more information, see the design paper at
1384 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
1385 followup implementation paper at https://arxiv.org/abs/1709.01044.
1386 Closes ticket 12541.
1388 o Major features (next-generation onion services):
1389 - Tor now supports the next-generation onion services protocol for
1390 clients and services! As part of this release, the core of
1391 proposal 224 has been implemented and is available for
1392 experimentation and testing by our users. This newer version of
1393 onion services ("v3") features many improvements over the legacy
1396 a) Better crypto (replaced SHA1/DH/RSA1024
1397 with SHA3/ed25519/curve25519)
1399 b) Improved directory protocol, leaking much less information to
1402 c) Improved directory protocol, with smaller surface for
1405 d) Better onion address security against impersonation.
1407 e) More extensible introduction/rendezvous protocol.
1409 f) A cleaner and more modular codebase.
1411 You can identify a next-generation onion address by its length:
1412 they are 56 characters long, as in
1413 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
1415 In the future, we will release more options and features for v3
1416 onion services, but we first need a testing period, so that the
1417 current codebase matures and becomes more robust. Planned features
1418 include: offline keys, advanced client authorization, improved
1419 guard algorithms, and statistics. For full details, see
1422 Legacy ("v2") onion services will still work for the foreseeable
1423 future, and will remain the default until this new codebase gets
1424 tested and hardened. Service operators who want to experiment with
1425 the new system can use the 'HiddenServiceVersion 3' torrc
1426 directive along with the regular onion service configuration
1427 options. We will publish a blog post about this new feature
1430 o Major bugfixes (usability, control port):
1431 - Report trusted clock skew indications as bootstrap errors, so
1432 controllers can more easily alert users when their clocks are
1433 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
1435 o Minor features (bug detection):
1436 - Log a warning message with a stack trace for any attempt to call
1437 get_options() during option validation. This pattern has caused
1438 subtle bugs in the past. Closes ticket 22281.
1440 o Minor features (client):
1441 - You can now use Tor as a tunneled HTTP proxy: use the new
1442 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
1443 requests. Closes ticket 22407.
1444 - Add an extra check to make sure that we always use the newer guard
1445 selection code for picking our guards. Closes ticket 22779.
1446 - When downloading (micro)descriptors, don't split the list into
1447 multiple requests unless we want at least 32 descriptors.
1448 Previously, we split at 4, not 32, which led to significant
1449 overhead in HTTP request size and degradation in compression
1450 performance. Closes ticket 23220.
1452 o Minor features (command line):
1453 - Add a new commandline option, --key-expiration, which prints when
1454 the current signing key is going to expire. Implements ticket
1455 17639; patch by Isis Lovecruft.
1457 o Minor features (control port):
1458 - If an application tries to use the control port as an HTTP proxy,
1459 respond with a meaningful "This is the Tor control port" message,
1460 and log the event. Closes ticket 1667. Patch from Ravi
1462 - Provide better error message for GETINFO desc/(id|name) when not
1463 fetching router descriptors. Closes ticket 5847. Patch by
1465 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
1466 whether Tor will try to download router descriptors and
1467 microdescriptors respectively. Closes ticket 22684.
1468 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
1469 so controllers can tell whether the geoip databases are loaded.
1470 Closes ticket 23237.
1471 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
1472 events. Closes ticket 19254. Patch by "DonnchaC".
1474 o Minor features (development support):
1475 - Developers can now generate a call-graph for Tor using the
1476 "calltool" python program, which post-processes object dumps. It
1477 should work okay on many Linux and OSX platforms, and might work
1478 elsewhere too. To run it, install calltool from
1479 https://gitweb.torproject.org/user/nickm/calltool.git and run
1480 "make callgraph". Closes ticket 19307.
1482 o Minor features (ed25519):
1483 - Add validation function to checks for torsion components in
1484 ed25519 public keys, used by prop224 client-side code. Closes
1485 ticket 22006. Math help by Ian Goldberg.
1487 o Minor features (exit relay, DNS):
1488 - Improve the clarity and safety of the log message from evdns when
1489 receiving an apparently spoofed DNS reply. Closes ticket 3056.
1491 o Minor features (integration, hardening):
1492 - Add a new NoExec option to prevent Tor from running other
1493 programs. When this option is set to 1, Tor will never try to run
1494 another program, regardless of the settings of
1495 PortForwardingHelper, ClientTransportPlugin, or
1496 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
1497 without restarting Tor. Closes ticket 22976.
1499 o Minor features (logging):
1500 - Improve the warning message for specifying a relay by nickname.
1501 The previous message implied that nickname registration was still
1502 part of the Tor network design, which it isn't. Closes
1504 - If the sandbox filter fails to load, suggest to the user that
1505 their kernel might not support seccomp2. Closes ticket 23090.
1507 o Minor features (portability):
1508 - Check at configure time whether uint8_t is the same type as
1509 unsigned char. Lots of existing code already makes this
1510 assumption, and there could be strict aliasing issues if the
1511 assumption is violated. Closes ticket 22410.
1513 o Minor features (relay, configuration):
1514 - Reject attempts to use relative file paths when RunAsDaemon is
1515 set. Previously, Tor would accept these, but the directory-
1516 changing step of RunAsDaemon would give strange and/or confusing
1517 results. Closes ticket 22731.
1519 o Minor features (startup, safety):
1520 - When configured to write a PID file, Tor now exits if it is unable
1521 to do so. Previously, it would warn and continue. Closes
1524 o Minor features (static analysis):
1525 - The BUG() macro has been changed slightly so that Coverity no
1526 longer complains about dead code if the bug is impossible. Closes
1529 o Minor features (testing):
1530 - The default chutney network tests now include tests for the v3
1531 hidden service design. Make sure you have the latest version of
1532 chutney if you want to run these. Closes ticket 22437.
1533 - Add a unit test to verify that we can parse a hardcoded v2 hidden
1534 service descriptor. Closes ticket 15554.
1536 o Minor bugfixes (certificate handling):
1537 - Fix a time handling bug in Tor certificates set to expire after
1538 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
1539 Coverity as CID 1415728.
1541 o Minor bugfixes (client, usability):
1542 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
1543 SOCKS4a requests that contain IP address strings, even when
1544 SafeSocks in enabled, as this prevents user from connecting to
1545 known IP addresses without relying on DNS for resolving. SafeSocks
1546 still rejects SOCKS connections that connect to IP addresses when
1547 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
1548 bugfix on Tor 0.2.6.2-alpha.
1550 o Minor bugfixes (code correctness):
1551 - Call htons() in extend_cell_format() for encoding a 16-bit value.
1552 Previously we used ntohs(), which happens to behave the same on
1553 all the platforms we support, but which isn't really correct.
1554 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
1555 - For defense-in-depth, make the controller's write_escaped_data()
1556 function robust to extremely long inputs. Fixes bug 19281; bugfix
1557 on 0.1.1.1-alpha. Reported by Guido Vranken.
1559 o Minor bugfixes (compilation):
1560 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
1561 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1563 o Minor bugfixes (consensus expiry):
1564 - Check for adequate directory information correctly. Previously, Tor
1565 would reconsider whether it had sufficient directory information
1566 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
1568 o Minor bugfixes (directory protocol):
1569 - Directory servers now include a "Date:" http header for response
1570 codes other than 200. Clients starting with a skewed clock and a
1571 recent consensus were getting "304 Not modified" responses from
1572 directory authorities, so without the Date header, the client
1573 would never hear about a wrong clock. Fixes bug 23499; bugfix
1575 - Make clients wait for 6 seconds before trying to download a
1576 consensus from an authority. Fixes bug 17750; bugfix
1579 o Minor bugfixes (DoS-resistance):
1580 - If future code asks if there are any running bridges, without
1581 checking if bridges are enabled, log a BUG warning rather than
1582 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
1584 o Minor bugfixes (format strictness):
1585 - Restrict several data formats to decimal. Previously, the
1586 BuildTimeHistogram entries in the state file, the "bw=" entries in
1587 the bandwidth authority file, and the process IDs passed to the
1588 __OwningControllerProcess option could all be specified in hex or
1589 octal as well as in decimal. This was not an intentional feature.
1590 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
1593 o Minor bugfixes (heartbeat):
1594 - If we fail to write a heartbeat message, schedule a retry for the
1595 minimum heartbeat interval number of seconds in the future. Fixes
1596 bug 19476; bugfix on 0.2.3.1-alpha.
1598 o Minor bugfixes (linux seccomp2 sandbox, logging):
1599 - Fix some messages on unexpected errors from the seccomp2 library.
1600 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
1602 o Minor bugfixes (logging):
1603 - Remove duplicate log messages regarding opening non-local
1604 SocksPorts upon parsing config and opening listeners at startup.
1605 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
1606 - Use a more comprehensible log message when telling the user
1607 they've excluded every running exit node. Fixes bug 7890; bugfix
1609 - When logging the number of descriptors we intend to download per
1610 directory request, do not log a number higher than then the number
1611 of descriptors we're fetching in total. Fixes bug 19648; bugfix
1613 - When warning about a directory owned by the wrong user, log the
1614 actual name of the user owning the directory. Previously, we'd log
1615 the name of the process owner twice. Fixes bug 23487; bugfix
1617 - The tor specification says hop counts are 1-based, so fix two log
1618 messages that mistakenly logged 0-based hop counts. Fixes bug
1619 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
1620 Credit to Xiaofan Li for reporting this issue.
1622 o Minor bugfixes (portability):
1623 - Stop using the PATH_MAX variable, which is not defined on GNU
1624 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
1626 o Minor bugfixes (relay):
1627 - When uploading our descriptor for the first time after startup,
1628 report the reason for uploading as "Tor just started" rather than
1629 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
1630 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1631 relays, to prevent spurious address resolutions and descriptor
1632 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1633 bugfix on in 0.2.8.1-alpha.
1635 o Minor bugfixes (tests):
1636 - Fix a broken unit test for the OutboundAddress option: the parsing
1637 function was never returning an error on failure. Fixes bug 23366;
1638 bugfix on 0.3.0.3-alpha.
1639 - Fix a signed-integer overflow in the unit tests for
1640 dir/download_status_random_backoff, which was untriggered until we
1641 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
1643 o Minor bugfixes (usability, control port):
1644 - Stop making an unnecessary routerlist check in NETINFO clock skew
1645 detection; this was preventing clients from reporting NETINFO clock
1646 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
1648 o Code simplification and refactoring:
1649 - Extract the code for handling newly-open channels into a separate
1650 function from the general code to handle channel state
1651 transitions. This change simplifies our callgraph, reducing the
1652 size of the largest strongly connected component by roughly a
1653 factor of two. Closes ticket 22608.
1654 - Remove dead code for largely unused statistics on the number of
1655 times we've attempted various public key operations. Fixes bug
1656 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
1657 - Remove several now-obsolete functions for asking about old
1658 variants directory authority status. Closes ticket 22311; patch
1660 - Remove some of the code that once supported "Named" and "Unnamed"
1661 routers. Authorities no longer vote for these flags. Closes
1663 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
1664 and old hidden services, to indicate that they aren't suitable for
1665 new protocols or formats. Closes ticket 23026.
1666 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
1667 22521. Patch from Neel Chauhan.
1668 - Split the enormous circuit_send_next_onion_skin() function into
1669 multiple subfunctions. Closes ticket 22804.
1670 - Split the portions of the buffer.c module that handle particular
1671 protocols into separate modules. Part of ticket 23149.
1672 - Use our test macros more consistently, to produce more useful
1673 error messages when our unit tests fail. Add coccinelle patches to
1674 allow us to re-check for test macro uses. Closes ticket 22497.
1676 o Deprecated features:
1677 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
1678 only applies to direct unencrypted HTTP connections to your
1679 directory server, which your Tor probably isn't using. Closes
1683 - Clarify in the manual that "Sandbox 1" is only supported on Linux
1684 kernels. Closes ticket 22677.
1685 - Document all values of PublishServerDescriptor in the manpage.
1686 Closes ticket 15645.
1687 - Improve the documentation for the directory port part of the
1688 DirAuthority line. Closes ticket 20152.
1689 - Restore documentation for the authorities' "approved-routers"
1690 file. Closes ticket 21148.
1693 - The AllowDotExit option has been removed as unsafe. It has been
1694 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
1695 - The ClientDNSRejectInternalAddresses flag can no longer be set on
1696 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
1697 Closes ticket 21031.
1698 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
1699 nobody was using it any longer. Closes ticket 22377.
1702 Changes in version 0.2.8.15 - 2017-09-18
1703 Tor 0.2.8.15 backports a collection of bugfixes from later
1706 Most significantly, it includes a fix for TROVE-2017-008, a
1707 security bug that affects hidden services running with the
1708 SafeLogging option disabled. For more information, see
1709 https://trac.torproject.org/projects/tor/ticket/23490
1711 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
1712 2018. We suggest that you upgrade to the latest stable release if
1713 possible. If you can't, we recommend that you upgrade at least to
1714 0.2.9, which will be supported until 2020.
1716 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1717 - Avoid an assertion failure bug affecting our implementation of
1718 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1719 handling of "0xx" differs from what we had expected. Fixes bug
1720 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1723 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1726 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1727 - Backport a fix for an "unused variable" warning that appeared
1728 in some versions of mingw. Fixes bug 22838; bugfix on
1731 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1732 - Fix a memset() off the end of an array when packing cells. This
1733 bug should be harmless in practice, since the corrupted bytes are
1734 still in the same structure, and are always padding bytes,
1735 ignored, or immediately overwritten, depending on compiler
1736 behavior. Nevertheless, because the memset()'s purpose is to make
1737 sure that any other cell-handling bugs can't expose bytes to the
1738 network, we need to fix it. Fixes bug 22737; bugfix on
1739 0.2.4.11-alpha. Fixes CID 1401591.
1741 o Build features (backport from 0.3.1.5-alpha):
1742 - Tor's repository now includes a Travis Continuous Integration (CI)
1743 configuration file (.travis.yml). This is meant to help new
1744 developers and contributors who fork Tor to a Github repository be
1745 better able to test their changes, and understand what we expect
1746 to pass. To use this new build feature, you must fork Tor to your
1747 Github account, then go into the "Integrations" menu in the
1748 repository settings for your fork and enable Travis, then push
1749 your changes. Closes ticket 22636.
1752 Changes in version 0.2.9.12 - 2017-09-18
1753 Tor 0.2.9.12 backports a collection of bugfixes from later
1756 Most significantly, it includes a fix for TROVE-2017-008, a
1757 security bug that affects hidden services running with the
1758 SafeLogging option disabled. For more information, see
1759 https://trac.torproject.org/projects/tor/ticket/23490
1761 o Major features (security, backport from 0.3.0.2-alpha):
1762 - Change the algorithm used to decide DNS TTLs on client and server
1763 side, to better resist DNS-based correlation attacks like the
1764 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
1765 Feamster. Now relays only return one of two possible DNS TTL
1766 values, and clients are willing to believe DNS TTL values up to 3
1767 hours long. Closes ticket 19769.
1769 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
1770 - Fix a rare crash when sending a begin cell on a circuit whose
1771 linked directory connection had already been closed. Fixes bug
1772 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
1774 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
1775 - Fix a bug that prevented exit nodes from caching DNS records for
1776 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
1778 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
1779 - Fix a typo that had prevented TPROXY-based transparent proxying
1780 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
1781 Patch from "d4fq0fQAgoJ".
1783 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1784 - Avoid an assertion failure bug affecting our implementation of
1785 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1786 handling of "0xx" differs from what we had expected. Fixes bug
1787 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1789 o Minor features (code style, backport from 0.3.1.3-alpha):
1790 - Add "Falls through" comments to our codebase, in order to silence
1791 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1792 Stieger. Closes ticket 22446.
1794 o Minor features (geoip):
1795 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1798 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
1799 - Roll over monthly accounting at the configured hour and minute,
1800 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1801 Found by Andrey Karpov with PVS-Studio.
1803 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
1804 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
1805 bugfix on 0.2.8.1-alpha.
1806 - Fix warnings when building with libscrypt and openssl scrypt support
1807 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
1808 - When building with certain versions the mingw C header files, avoid
1809 float-conversion warnings when calling the C functions isfinite(),
1810 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
1812 o Minor bugfixes (compilation, backport from 0.3.1.7):
1813 - Avoid compiler warnings in the unit tests for running tor_sscanf()
1814 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1816 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1817 - Backport a fix for an "unused variable" warning that appeared
1818 in some versions of mingw. Fixes bug 22838; bugfix on
1821 o Minor bugfixes (controller, backport from 0.3.1.7):
1822 - Do not crash when receiving a HSPOST command with an empty body.
1823 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1824 - Do not crash when receiving a POSTDESCRIPTOR command with an
1825 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1827 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
1828 - Avoid Coverity build warnings related to our BUG() macro. By
1829 default, Coverity treats BUG() as the Linux kernel does: an
1830 instant abort(). We need to override that so our BUG() macro
1831 doesn't prevent Coverity from analyzing functions that use it.
1832 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
1834 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1835 - Fix a memset() off the end of an array when packing cells. This
1836 bug should be harmless in practice, since the corrupted bytes are
1837 still in the same structure, and are always padding bytes,
1838 ignored, or immediately overwritten, depending on compiler
1839 behavior. Nevertheless, because the memset()'s purpose is to make
1840 sure that any other cell-handling bugs can't expose bytes to the
1841 network, we need to fix it. Fixes bug 22737; bugfix on
1842 0.2.4.11-alpha. Fixes CID 1401591.
1844 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1845 - When setting the maximum number of connections allowed by the OS,
1846 always allow some extra file descriptors for other files. Fixes
1847 bug 22797; bugfix on 0.2.0.10-alpha.
1849 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
1850 - Avoid a sandbox failure when trying to re-bind to a socket and
1851 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
1853 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
1854 - Permit the fchmod system call, to avoid crashing on startup when
1855 starting with the seccomp2 sandbox and an unexpected set of
1856 permissions on the data directory or its contents. Fixes bug
1857 22516; bugfix on 0.2.5.4-alpha.
1859 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
1860 - Avoid a double-marked-circuit warning that could happen when we
1861 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
1864 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
1865 - Reject version numbers with non-numeric prefixes (such as +, -, or
1866 whitespace). Disallowing whitespace prevents differential version
1867 parsing between POSIX-based and Windows platforms. Fixes bug 21507
1868 and part of 21508; bugfix on 0.0.8pre1.
1870 o Build features (backport from 0.3.1.5-alpha):
1871 - Tor's repository now includes a Travis Continuous Integration (CI)
1872 configuration file (.travis.yml). This is meant to help new
1873 developers and contributors who fork Tor to a Github repository be
1874 better able to test their changes, and understand what we expect
1875 to pass. To use this new build feature, you must fork Tor to your
1876 Github account, then go into the "Integrations" menu in the
1877 repository settings for your fork and enable Travis, then push
1878 your changes. Closes ticket 22636.
1881 Changes in version 0.3.0.11 - 2017-09-18
1882 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
1885 Most significantly, it includes a fix for TROVE-2017-008, a
1886 security bug that affects hidden services running with the
1887 SafeLogging option disabled. For more information, see
1888 https://trac.torproject.org/projects/tor/ticket/23490
1890 o Minor features (code style, backport from 0.3.1.7):
1891 - Add "Falls through" comments to our codebase, in order to silence
1892 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1893 Stieger. Closes ticket 22446.
1896 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1899 o Minor bugfixes (compilation, backport from 0.3.1.7):
1900 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1901 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1903 o Minor bugfixes (controller, backport from 0.3.1.7):
1904 - Do not crash when receiving a HSPOST command with an empty body.
1905 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1906 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1907 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1909 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1910 - When setting the maximum number of connections allowed by the OS,
1911 always allow some extra file descriptors for other files. Fixes
1912 bug 22797; bugfix on 0.2.0.10-alpha.
1914 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
1915 - Remove a forgotten debugging message when an introduction point
1916 successfully establishes a hidden service prop224 circuit with
1918 - Change three other log_warn() for an introduction point to
1919 protocol warnings, because they can be failure from the network
1920 and are not relevant to the operator. Fixes bug 23078; bugfix on
1921 0.3.0.1-alpha and 0.3.0.2-alpha.
1924 Changes in version 0.3.1.7 - 2017-09-18
1925 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
1927 With the 0.3.1 series, Tor now serves and downloads directory
1928 information in more compact formats, to save on bandwidth overhead. It
1929 also contains a new padding system to resist netflow-based traffic
1930 analysis, and experimental support for building parts of Tor in Rust
1931 (though no parts of Tor are in Rust yet). There are also numerous
1932 small features, bugfixes on earlier release series, and groundwork for
1933 the hidden services revamp of 0.3.2.
1935 This release also includes a fix for TROVE-2017-008, a security bug
1936 that affects hidden services running with the SafeLogging option
1937 disabled. For more information, see
1938 https://trac.torproject.org/projects/tor/ticket/23490
1940 Per our stable release policy, we plan to support each stable release
1941 series for at least the next nine months, or for three months after
1942 the first stable release of the next series: whichever is longer. If
1943 you need a release with long-term support, we recommend that you stay
1944 with the 0.2.9 series.
1946 Below is a list of the changes since 0.3.1.6-rc. For a list of all
1947 changes since 0.3.0, see the ReleaseNotes file.
1949 o Major bugfixes (security, hidden services, loggging):
1950 - Fix a bug where we could log uninitialized stack when a certain
1951 hidden service error occurred while SafeLogging was disabled.
1952 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
1953 TROVE-2017-008 and CVE-2017-0380.
1955 o Minor features (defensive programming):
1956 - Create a pair of consensus parameters, nf_pad_tor2web and
1957 nf_pad_single_onion, to disable netflow padding in the consensus
1958 for non-anonymous connections in case the overhead is high. Closes
1961 o Minor features (diagnostic):
1962 - Add a stack trace to the bug warnings that can be logged when
1963 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
1964 attempt for bug 23105.
1966 o Minor features (geoip):
1967 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1970 o Minor bugfixes (compilation):
1971 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1972 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1974 o Minor bugfixes (controller):
1975 - Do not crash when receiving a HSPOST command with an empty body.
1976 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1977 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1978 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1980 o Minor bugfixes (relay):
1981 - Inform the geoip and rephist modules about all requests, even on
1982 relays that are only fetching microdescriptors. Fixes a bug
1983 related to 21585; bugfix on 0.3.0.1-alpha.
1985 o Minor bugfixes (unit tests):
1986 - Fix a channelpadding unit test failure on slow systems by using
1987 mocked time instead of actual time. Fixes bug 23077; bugfix
1991 Changes in version 0.3.1.6-rc - 2017-09-05
1992 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
1993 release series, including a bug that produced weird behavior on
1994 Windows directory caches.
1996 This is the first release candidate in the Tor 0.3.1 series. If we
1997 find no new bugs or regressions here, the first stable 0.3.1 release
1998 will be nearly identical to it.
2000 o Major bugfixes (windows, directory cache):
2001 - On Windows, do not try to delete cached consensus documents and
2002 diffs before they are unmapped from memory--Windows won't allow
2003 that. Instead, allow the consensus cache directory to grow larger,
2004 to hold files that might need to stay around longer. Fixes bug
2005 22752; bugfix on 0.3.1.1-alpha.
2007 o Minor features (directory authority):
2008 - Improve the message that authorities report to relays that present
2009 RSA/Ed25519 keypairs that conflict with previously pinned keys.
2010 Closes ticket 22348.
2012 o Minor features (geoip):
2013 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
2016 o Minor features (testing):
2017 - Add more tests for compression backend initialization. Closes
2020 o Minor bugfixes (directory cache):
2021 - Fix a memory leak when recovering space in the consensus cache.
2022 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
2024 o Minor bugfixes (hidden service):
2025 - Increase the number of circuits that a service is allowed to
2026 open over a specific period of time. The value was lower than it
2027 should be (8 vs 12) in the normal case of 3 introduction points.
2028 Fixes bug 22159; bugfix on 0.3.0.5-rc.
2029 - Fix a BUG warning during HSv3 descriptor decoding that could be
2030 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
2031 on 0.3.0.1-alpha. Bug found by "haxxpop".
2032 - Rate-limit the log messages if we exceed the maximum number of
2033 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
2035 o Minor bugfixes (logging, relay):
2036 - Remove a forgotten debugging message when an introduction point
2037 successfully establishes a hidden service prop224 circuit with
2039 - Change three other log_warn() for an introduction point to
2040 protocol warnings, because they can be failure from the network
2041 and are not relevant to the operator. Fixes bug 23078; bugfix on
2042 0.3.0.1-alpha and 0.3.0.2-alpha.
2044 o Minor bugfixes (relay):
2045 - When a relay is not running as a directory cache, it will no
2046 longer generate compressed consensuses and consensus diff
2047 information. Previously, this was a waste of disk and CPU. Fixes
2048 bug 23275; bugfix on 0.3.1.1-alpha.
2050 o Minor bugfixes (robustness, error handling):
2051 - Improve our handling of the cases where OpenSSL encounters a
2052 memory error while encoding keys and certificates. We haven't
2053 observed these errors in the wild, but if they do happen, we now
2054 detect and respond better. Fixes bug 19418; bugfix on all versions
2055 of Tor. Reported by Guido Vranken.
2057 o Minor bugfixes (stability):
2058 - Avoid crashing on a double-free when unable to load or process an
2059 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
2060 with the clang static analyzer.
2062 o Minor bugfixes (testing):
2063 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2064 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2065 - Port the hs_ntor handshake test to work correctly with recent
2066 versions of the pysha3 module. Fixes bug 23071; bugfix
2069 o Minor bugfixes (Windows service):
2070 - When running as a Windows service, set the ID of the main thread
2071 correctly. Failure to do so made us fail to send log messages to
2072 the controller in 0.2.1.16-rc, slowed down controller event
2073 delivery in 0.2.7.3-rc and later, and crash with an assertion
2074 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2075 Patch and diagnosis from "Vort".
2078 Changes in version 0.3.0.10 - 2017-08-02
2079 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
2080 from the current Tor alpha series. OpenBSD users and TPROXY users
2081 should upgrade; others are probably okay sticking with 0.3.0.9.
2083 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
2084 - Tor's repository now includes a Travis Continuous Integration (CI)
2085 configuration file (.travis.yml). This is meant to help new
2086 developers and contributors who fork Tor to a Github repository be
2087 better able to test their changes, and understand what we expect
2088 to pass. To use this new build feature, you must fork Tor to your
2089 Github account, then go into the "Integrations" menu in the
2090 repository settings for your fork and enable Travis, then push
2091 your changes. Closes ticket 22636.
2093 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
2094 - Fix a typo that had prevented TPROXY-based transparent proxying
2095 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2096 Patch from "d4fq0fQAgoJ".
2098 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2099 - Avoid an assertion failure bug affecting our implementation of
2100 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2101 handling of "0xbar" differs from what we had expected. Fixes bug
2102 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2104 o Minor features (backport from 0.3.1.5-alpha):
2105 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
2108 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
2109 - Roll over monthly accounting at the configured hour and minute,
2110 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2111 Found by Andrey Karpov with PVS-Studio.
2113 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
2114 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
2115 bugfix on 0.2.8.1-alpha.
2116 - Fix warnings when building with libscrypt and openssl scrypt
2117 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2118 - When building with certain versions of the mingw C header files,
2119 avoid float-conversion warnings when calling the C functions
2120 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2123 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2124 - Backport a fix for an "unused variable" warning that appeared
2125 in some versions of mingw. Fixes bug 22838; bugfix on
2128 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
2129 - Avoid Coverity build warnings related to our BUG() macro. By
2130 default, Coverity treats BUG() as the Linux kernel does: an
2131 instant abort(). We need to override that so our BUG() macro
2132 doesn't prevent Coverity from analyzing functions that use it.
2133 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2135 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
2136 - When rejecting a router descriptor for running an obsolete version
2137 of Tor without ntor support, warn about the obsolete tor version,
2138 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2140 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
2141 - Avoid a sandbox failure when trying to re-bind to a socket and
2142 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2144 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
2145 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2146 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2149 Changes in version 0.3.1.5-alpha - 2017-08-01
2150 Tor 0.3.1.5-alpha improves the performance of consensus diff
2151 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
2152 several other bugs. If no serious bugs are found in this version, the
2153 next version will be a release candidate.
2155 This release also marks the end of support for the Tor 0.2.4.x,
2156 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
2157 further bug or security fixes. Anyone still running or distributing
2158 one of those versions should upgrade.
2160 o Major features (build system, continuous integration):
2161 - Tor's repository now includes a Travis Continuous Integration (CI)
2162 configuration file (.travis.yml). This is meant to help new
2163 developers and contributors who fork Tor to a Github repository be
2164 better able to test their changes, and understand what we expect
2165 to pass. To use this new build feature, you must fork Tor to your
2166 Github account, then go into the "Integrations" menu in the
2167 repository settings for your fork and enable Travis, then push
2168 your changes. Closes ticket 22636.
2170 o Major bugfixes (openbsd, denial-of-service):
2171 - Avoid an assertion failure bug affecting our implementation of
2172 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2173 handling of "0xbar" differs from what we had expected. Fixes bug
2174 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2176 o Major bugfixes (relay, performance):
2177 - Perform circuit handshake operations at a higher priority than we
2178 use for consensus diff creation and compression. This should
2179 prevent circuits from starving when a relay or bridge receives a
2180 new consensus, especially on lower-powered machines. Fixes bug
2181 22883; bugfix on 0.3.1.1-alpha.
2183 o Minor features (bridge authority):
2184 - Add "fingerprint" lines to the networkstatus-bridges file produced
2185 by bridge authorities. Closes ticket 22207.
2187 o Minor features (directory cache, consensus diff):
2188 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
2189 operators with low-resource environments to adjust the number of
2190 consensuses they'll store and generate diffs from. Most cache
2191 operators should leave it unchanged. Helps to work around
2194 o Minor features (geoip):
2195 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
2198 o Minor features (relay, performance):
2199 - Always start relays with at least two worker threads, to prevent
2200 priority inversion on slow tasks. Part of the fix for bug 22883.
2201 - Allow background work to be queued with different priorities, so
2202 that a big pile of slow low-priority jobs will not starve out
2203 higher priority jobs. This lays the groundwork for a fix for
2206 o Minor bugfixes (build system, rust):
2207 - Fix a problem where Rust toolchains were not being found when
2208 building without --enable-cargo-online-mode, due to setting the
2209 $HOME environment variable instead of $CARGO_HOME. Fixes bug
2210 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
2212 o Minor bugfixes (compatibility, zstd):
2213 - Write zstd epilogues correctly when the epilogue requires
2214 reallocation of the output buffer, even with zstd 1.3.0.
2215 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
2216 22927; bugfix on 0.3.1.1-alpha.
2218 o Minor bugfixes (compilation warnings):
2219 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
2220 22915; bugfix on 0.2.8.1-alpha.
2221 - Fix warnings when building with libscrypt and openssl scrypt
2222 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2223 - Compile correctly when both openssl 1.1.0 and libscrypt are
2224 detected. Previously this would cause an error. Fixes bug 22892;
2225 bugfix on 0.3.1.1-alpha.
2226 - When building with certain versions of the mingw C header files,
2227 avoid float-conversion warnings when calling the C functions
2228 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2231 o Minor bugfixes (coverity build support):
2232 - Avoid Coverity build warnings related to our BUG() macro. By
2233 default, Coverity treats BUG() as the Linux kernel does: an
2234 instant abort(). We need to override that so our BUG() macro
2235 doesn't prevent Coverity from analyzing functions that use it.
2236 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2238 o Minor bugfixes (directory authority):
2239 - When a directory authority rejects a descriptor or extrainfo with
2240 a given digest, mark that digest as undownloadable, so that we do
2241 not attempt to download it again over and over. We previously
2242 tried to avoid downloading such descriptors by other means, but we
2243 didn't notice if we accidentally downloaded one anyway. This
2244 behavior became problematic in 0.2.7.2-alpha, when authorities
2245 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2248 o Minor bugfixes (error reporting, windows):
2249 - When formatting Windows error messages, use the English format to
2250 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
2253 o Minor bugfixes (file limits, osx):
2254 - When setting the maximum number of connections allowed by the OS,
2255 always allow some extra file descriptors for other files. Fixes
2256 bug 22797; bugfix on 0.2.0.10-alpha.
2258 o Minor bugfixes (linux seccomp2 sandbox):
2259 - Avoid a sandbox failure when trying to re-bind to a socket and
2260 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2262 o Minor bugfixes (memory leaks):
2263 - Fix a small memory leak when validating a configuration that uses
2264 two or more AF_UNIX sockets for the same port type. Fixes bug
2265 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
2267 o Minor bugfixes (unit tests):
2268 - test_consdiff_base64cmp would fail on OS X because while OS X
2269 follows the standard of (less than zero/zero/greater than zero),
2270 it doesn't follow the convention of (-1/0/+1). Make the test
2271 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
2272 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2273 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2276 Changes in version 0.3.1.4-alpha - 2017-06-29
2277 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
2278 to use a guard that was in the same network family as a chosen exit
2279 relay. This is a security regression; all clients running earlier
2280 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
2283 This release also fixes several other bugs introduced in 0.3.0.x
2284 and 0.3.1.x, including others that can affect bandwidth usage
2288 - To build with zstd and lzma support, Tor now requires the
2289 pkg-config tool at build time. (This requirement was new in
2290 0.3.1.1-alpha, but was not noted at the time. Noting it here to
2291 close ticket 22623.)
2293 o Major bugfixes (path selection, security):
2294 - When choosing which guard to use for a circuit, avoid the exit's
2295 family along with the exit itself. Previously, the new guard
2296 selection logic avoided the exit, but did not consider its family.
2297 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2298 006 and CVE-2017-0377.
2300 o Major bugfixes (compression, zstd):
2301 - Correctly detect a full buffer when decompressing a large zstd-
2302 compressed input. Previously, we would sometimes treat a full
2303 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
2305 o Major bugfixes (directory protocol):
2306 - Ensure that we send "304 Not modified" as HTTP status code when a
2307 client is attempting to fetch a consensus or consensus diff, and
2308 the best one we can send them is one they already have. Fixes bug
2309 22702; bugfix on 0.3.1.1-alpha.
2311 o Major bugfixes (entry guards):
2312 - When starting with an old consensus, do not add new entry guards
2313 unless the consensus is "reasonably live" (under 1 day old). Fixes
2314 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2316 o Minor features (bug mitigation, diagnostics, logging):
2317 - Avoid an assertion failure, and log a better error message, when
2318 unable to remove a file from the consensus cache on Windows.
2319 Attempts to mitigate and diagnose bug 22752.
2321 o Minor features (geoip):
2322 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
2325 o Minor bugfixes (compression):
2326 - When compressing or decompressing a buffer, check for a failure to
2327 create a compression object. Fixes bug 22626; bugfix
2329 - When decompressing a buffer, check for extra data after the end of
2330 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
2331 - When decompressing an object received over an anonymous directory
2332 connection, if we have already decompressed it using an acceptable
2333 compression method, do not reject it for looking like an
2334 unacceptable compression method. Fixes part of bug 22670; bugfix
2336 - When serving directory votes compressed with zlib, do not claim to
2337 have compressed them with zstd. Fixes bug 22669; bugfix
2339 - When spooling compressed data to an output buffer, don't try to
2340 spool more data when there is no more data to spool and we are not
2341 trying to flush the input. Previously, we would sometimes launch
2342 compression requests with nothing to do, which interferes with our
2343 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
2345 o Minor bugfixes (defensive programming):
2346 - Detect and break out of infinite loops in our compression code. We
2347 don't think that any such loops exist now, but it's best to be
2348 safe. Closes ticket 22672.
2349 - Fix a memset() off the end of an array when packing cells. This
2350 bug should be harmless in practice, since the corrupted bytes are
2351 still in the same structure, and are always padding bytes,
2352 ignored, or immediately overwritten, depending on compiler
2353 behavior. Nevertheless, because the memset()'s purpose is to make
2354 sure that any other cell-handling bugs can't expose bytes to the
2355 network, we need to fix it. Fixes bug 22737; bugfix on
2356 0.2.4.11-alpha. Fixes CID 1401591.
2358 o Minor bugfixes (linux seccomp2 sandbox):
2359 - Permit the fchmod system call, to avoid crashing on startup when
2360 starting with the seccomp2 sandbox and an unexpected set of
2361 permissions on the data directory or its contents. Fixes bug
2362 22516; bugfix on 0.2.5.4-alpha.
2363 - Fix a crash in the LZMA module, when the sandbox was enabled, and
2364 liblzma would allocate more than 16 MB of memory. We solve this by
2365 bumping the mprotect() limit in the sandbox module from 16 MB to
2366 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
2368 o Minor bugfixes (logging):
2369 - When decompressing, do not warn if we fail to decompress using a
2370 compression method that we merely guessed. Fixes part of bug
2371 22670; bugfix on 0.1.1.14-alpha.
2372 - When decompressing, treat mismatch between content-encoding and
2373 actual compression type as a protocol warning. Fixes part of bug
2374 22670; bugfix on 0.1.1.9-alpha.
2375 - Downgrade "assigned_to_cpuworker failed" message to info-level
2376 severity. In every case that can reach it, either a better warning
2377 has already been logged, or no warning is warranted. Fixes bug
2378 22356; bugfix on 0.2.6.3-alpha.
2379 - Demote a warn that was caused by libevent delays to info if
2380 netflow padding is less than 4.5 seconds late, or to notice
2381 if it is more (4.5 seconds is the amount of time that a netflow
2382 record might be emitted after, if we chose the maximum timeout).
2383 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
2385 o Minor bugfixes (process behavior):
2386 - When exiting because of an error, always exit with a nonzero exit
2387 status. Previously, we would fail to report an error in our exit
2388 status in cases related to __OwningControllerProcess failure,
2389 lockfile contention, and Ed25519 key initialization. Fixes bug
2390 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
2391 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
2395 - Add a manpage description for the key-pinning-journal file. Closes
2397 - Correctly note that bandwidth accounting values are stored in the
2398 state file, and the bw_accounting file is now obsolete. Closes
2400 - Document more of the files in the Tor data directory, including
2401 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
2402 approved-routers, sr-random, and diff-cache. Found while fixing
2406 Changes in version 0.3.0.9 - 2017-06-29
2407 Tor 0.3.0.9 fixes a path selection bug that would allow a client
2408 to use a guard that was in the same network family as a chosen exit
2409 relay. This is a security regression; all clients running earlier
2410 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
2413 This release also backports several other bugfixes from the 0.3.1.x
2416 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
2417 - When choosing which guard to use for a circuit, avoid the exit's
2418 family along with the exit itself. Previously, the new guard
2419 selection logic avoided the exit, but did not consider its family.
2420 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2421 006 and CVE-2017-0377.
2423 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
2424 - Don't block bootstrapping when a primary bridge is offline and we
2425 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2426 21969; bugfix on 0.3.0.3-alpha.
2428 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
2429 - When starting with an old consensus, do not add new entry guards
2430 unless the consensus is "reasonably live" (under 1 day old). Fixes
2431 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2433 o Minor features (geoip):
2434 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
2437 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
2438 - Reject version numbers with non-numeric prefixes (such as +, -, or
2439 whitespace). Disallowing whitespace prevents differential version
2440 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2441 and part of 21508; bugfix on 0.0.8pre1.
2443 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
2444 - Permit the fchmod system call, to avoid crashing on startup when
2445 starting with the seccomp2 sandbox and an unexpected set of
2446 permissions on the data directory or its contents. Fixes bug
2447 22516; bugfix on 0.2.5.4-alpha.
2449 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
2450 - Fix a memset() off the end of an array when packing cells. This
2451 bug should be harmless in practice, since the corrupted bytes are
2452 still in the same structure, and are always padding bytes,
2453 ignored, or immediately overwritten, depending on compiler
2454 behavior. Nevertheless, because the memset()'s purpose is to make
2455 sure that any other cell-handling bugs can't expose bytes to the
2456 network, we need to fix it. Fixes bug 22737; bugfix on
2457 0.2.4.11-alpha. Fixes CID 1401591.
2460 Changes in version 0.3.1.3-alpha - 2017-06-08
2461 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
2462 remotely crash a hidden service with an assertion failure. Anyone
2463 running a hidden service should upgrade to this version, or to some
2464 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
2466 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
2467 that sometimes made relays unreliable, as well as several other
2468 bugfixes described below.
2470 o Major bugfixes (hidden service, relay, security):
2471 - Fix a remotely triggerable assertion failure when a hidden service
2472 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2473 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2474 - Fix a remotely triggerable assertion failure caused by receiving a
2475 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2476 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2479 o Major bugfixes (relay, link handshake):
2480 - When performing the v3 link handshake on a TLS connection, report
2481 that we have the x509 certificate that we actually used on that
2482 connection, even if we have changed certificates since that
2483 connection was first opened. Previously, we would claim to have
2484 used our most recent x509 link certificate, which would sometimes
2485 make the link handshake fail. Fixes one case of bug 22460; bugfix
2488 o Major bugfixes (relays, key management):
2489 - Regenerate link and authentication certificates whenever the key
2490 that signs them changes; also, regenerate link certificates
2491 whenever the signed key changes. Previously, these processes were
2492 only weakly coupled, and we relays could (for minutes to hours)
2493 wind up with an inconsistent set of keys and certificates, which
2494 other relays would not accept. Fixes two cases of bug 22460;
2495 bugfix on 0.3.0.1-alpha.
2496 - When sending an Ed25519 signing->link certificate in a CERTS cell,
2497 send the certificate that matches the x509 certificate that we
2498 used on the TLS connection. Previously, there was a race condition
2499 if the TLS context rotated after we began the TLS handshake but
2500 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
2503 o Major bugfixes (torrc, crash):
2504 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
2505 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
2507 o Minor features (code style):
2508 - Add "Falls through" comments to our codebase, in order to silence
2509 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2510 Stieger. Closes ticket 22446.
2512 o Minor features (diagnostic):
2513 - Add logging messages to try to diagnose a rare bug that seems to
2514 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
2515 think this is happening because of incorrect system clocks, but
2516 we'd like to know for certain. Diagnostic for bug 22466.
2518 o Minor bugfixes (correctness):
2519 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2520 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2522 o Minor bugfixes (directory protocol):
2523 - Check for libzstd >= 1.1, because older versions lack the
2524 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
2526 o Minor bugfixes (link handshake):
2527 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2528 months, and regenerate it when it is within one month of expiring.
2529 Previously, we had generated this certificate at startup with a
2530 ten-year lifetime, but that could lead to weird behavior when Tor
2531 was started with a grossly inaccurate clock. Mitigates bug 22466;
2532 mitigation on 0.3.0.1-alpha.
2534 o Minor bugfixes (storage directories):
2535 - Always check for underflows in the cached storage directory usage.
2536 If the usage does underflow, re-calculate it. Also, avoid a
2537 separate underflow when the usage is not known. Fixes bug 22424;
2538 bugfix on 0.3.1.1-alpha.
2540 o Minor bugfixes (unit tests):
2541 - The unit tests now pass on systems where localhost is misconfigured
2542 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
2546 - Clarify the manpage for the (deprecated) torify script. Closes
2549 Changes in version 0.3.0.8 - 2017-06-08
2550 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
2551 remotely crash a hidden service with an assertion failure. Anyone
2552 running a hidden service should upgrade to this version, or to some
2553 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
2555 Tor 0.3.0.8 also includes fixes for several key management bugs
2556 that sometimes made relays unreliable, as well as several other
2557 bugfixes described below.
2559 o Major bugfixes (hidden service, relay, security, backport
2560 from 0.3.1.3-alpha):
2561 - Fix a remotely triggerable assertion failure when a hidden service
2562 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2563 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2564 - Fix a remotely triggerable assertion failure caused by receiving a
2565 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2566 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2569 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2570 - When performing the v3 link handshake on a TLS connection, report
2571 that we have the x509 certificate that we actually used on that
2572 connection, even if we have changed certificates since that
2573 connection was first opened. Previously, we would claim to have
2574 used our most recent x509 link certificate, which would sometimes
2575 make the link handshake fail. Fixes one case of bug 22460; bugfix
2578 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
2579 - Regenerate link and authentication certificates whenever the key
2580 that signs them changes; also, regenerate link certificates
2581 whenever the signed key changes. Previously, these processes were
2582 only weakly coupled, and we relays could (for minutes to hours)
2583 wind up with an inconsistent set of keys and certificates, which
2584 other relays would not accept. Fixes two cases of bug 22460;
2585 bugfix on 0.3.0.1-alpha.
2586 - When sending an Ed25519 signing->link certificate in a CERTS cell,
2587 send the certificate that matches the x509 certificate that we
2588 used on the TLS connection. Previously, there was a race condition
2589 if the TLS context rotated after we began the TLS handshake but
2590 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
2593 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
2594 - Stop rejecting v3 hidden service descriptors because their size
2595 did not match an old padding rule. Fixes bug 22447; bugfix on
2598 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2599 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2600 December 2016 (of which ~126 were still functional) with a list of
2601 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2602 2017. Resolves ticket 21564.
2604 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
2605 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
2606 bug 22252; bugfix on 0.2.9.3-alpha.
2608 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
2609 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2610 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2612 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
2613 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2614 months, and regenerate it when it is within one month of expiring.
2615 Previously, we had generated this certificate at startup with a
2616 ten-year lifetime, but that could lead to weird behavior when Tor
2617 was started with a grossly inaccurate clock. Mitigates bug 22466;
2618 mitigation on 0.3.0.1-alpha.
2620 o Minor bugfixes (memory leak, directory authority, backport from
2622 - When directory authorities reject a router descriptor due to
2623 keypinning, free the router descriptor rather than leaking the
2624 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2627 Changes in version 0.2.9.11 - 2017-06-08
2628 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
2629 remotely crash a hidden service with an assertion failure. Anyone
2630 running a hidden service should upgrade to this version, or to some
2631 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2632 are not affected by TROVE-2017-004.)
2634 Tor 0.2.9.11 also backports fixes for several key management bugs
2635 that sometimes made relays unreliable, as well as several other
2636 bugfixes described below.
2638 o Major bugfixes (hidden service, relay, security, backport
2639 from 0.3.1.3-alpha):
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 Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2646 - When performing the v3 link handshake on a TLS connection, report
2647 that we have the x509 certificate that we actually used on that
2648 connection, even if we have changed certificates since that
2649 connection was first opened. Previously, we would claim to have
2650 used our most recent x509 link certificate, which would sometimes
2651 make the link handshake fail. Fixes one case of bug 22460; bugfix
2654 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2655 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2656 December 2016 (of which ~126 were still functional) with a list of
2657 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2658 2017. Resolves ticket 21564.
2660 o Minor features (future-proofing, backport from 0.3.0.7):
2661 - Tor no longer refuses to download microdescriptors or descriptors if
2662 they are listed as "published in the future". This change will
2663 eventually allow us to stop listing meaningful "published" dates
2664 in microdescriptor consensuses, and thereby allow us to reduce the
2665 resources required to download consensus diffs by over 50%.
2666 Implements part of ticket 21642; implements part of proposal 275.
2668 o Minor features (directory authorities, backport from 0.3.0.4-rc)
2669 - Directory authorities now reject relays running versions
2670 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
2671 suffer from bug 20499 and don't keep their consensus cache
2672 up-to-date. Resolves ticket 20509.
2674 o Minor features (geoip):
2675 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2678 o Minor bugfixes (control port, backport from 0.3.0.6):
2679 - The GETINFO extra-info/digest/<digest> command was broken because
2680 of a wrong base16 decode return value check, introduced when
2681 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
2683 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
2684 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2685 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2687 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
2688 - The getpid() system call is now permitted under the Linux seccomp2
2689 sandbox, to avoid crashing with versions of OpenSSL (and other
2690 libraries) that attempt to learn the process's PID by using the
2691 syscall rather than the VDSO code. Fixes bug 21943; bugfix
2694 o Minor bugfixes (memory leak, directory authority, backport
2695 from 0.3.1.2-alpha):
2696 - When directory authorities reject a router descriptor due to
2697 keypinning, free the router descriptor rather than leaking the
2698 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2700 Changes in version 0.2.8.14 - 2017-06-08
2701 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2702 remotely crash a hidden service with an assertion failure. Anyone
2703 running a hidden service should upgrade to this version, or to some
2704 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2705 are not affected by TROVE-2017-004.)
2707 o Major bugfixes (hidden service, relay, security):
2708 - Fix a remotely triggerable assertion failure caused by receiving a
2709 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2710 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2713 o Minor features (geoip):
2714 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2717 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2718 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2719 December 2016 (of which ~126 were still functional) with a list of
2720 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2721 2017. Resolves ticket 21564.
2723 o Minor bugfixes (correctness):
2724 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2725 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2727 Changes in version 0.2.7.8 - 2017-06-08
2728 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2729 remotely crash a hidden service with an assertion failure. Anyone
2730 running a hidden service should upgrade to this version, or to some
2731 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2732 are not affected by TROVE-2017-004.)
2734 o Major bugfixes (hidden service, relay, security):
2735 - Fix a remotely triggerable assertion failure caused by receiving a
2736 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2737 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2740 o Minor features (geoip):
2741 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2744 o Minor bugfixes (correctness):
2745 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2746 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2749 Changes in version 0.2.6.12 - 2017-06-08
2750 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
2751 remotely crash a hidden service with an assertion failure. Anyone
2752 running a hidden service should upgrade to this version, or to some
2753 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2754 are not affected by TROVE-2017-004.)
2756 o Major bugfixes (hidden service, relay, security):
2757 - Fix a remotely triggerable assertion failure caused by receiving a
2758 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2759 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2762 o Minor features (geoip):
2763 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2766 o Minor bugfixes (correctness):
2767 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2768 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2770 Changes in version 0.2.5.14 - 2017-06-08
2771 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
2772 remotely crash a hidden service with an assertion failure. Anyone
2773 running a hidden service should upgrade to this version, or to some
2774 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2775 are not affected by TROVE-2017-004.)
2777 o Major bugfixes (hidden service, relay, security):
2778 - Fix a remotely triggerable assertion failure caused by receiving a
2779 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2780 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2783 o Minor features (geoip):
2784 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2787 o Minor bugfixes (correctness):
2788 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2789 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2791 Changes in version 0.2.4.29 - 2017-06-08
2792 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
2793 remotely crash a hidden service with an assertion failure. Anyone
2794 running a hidden service should upgrade to this version, or to some
2795 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2796 are not affected by TROVE-2017-004.)
2798 o Major bugfixes (hidden service, relay, security):
2799 - Fix a remotely triggerable assertion failure caused by receiving a
2800 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2801 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2804 o Minor features (geoip):
2805 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2808 o Minor bugfixes (correctness):
2809 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2810 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2813 Changes in version 0.3.1.2-alpha - 2017-05-26
2814 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
2815 fixes a few bugs found while testing 0.3.1.1-alpha, including a
2816 memory corruption bug that affected relay stability.
2818 o Major bugfixes (crash, relay):
2819 - Fix a memory-corruption bug in relays that set MyFamily.
2820 Previously, they would double-free MyFamily elements when making
2821 the next descriptor or when changing their configuration. Fixes
2822 bug 22368; bugfix on 0.3.1.1-alpha.
2824 o Minor bugfixes (logging):
2825 - Log a better message when a directory authority replies to an
2826 upload with an unexpected status code. Fixes bug 11121; bugfix
2829 o Minor bugfixes (memory leak, directory authority):
2830 - When directory authorities reject a router descriptor due to
2831 keypinning, free the router descriptor rather than leaking the
2832 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2835 Changes in version 0.3.1.1-alpha - 2017-05-22
2836 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
2837 reduces the bandwidth usage for Tor's directory protocol, adds some
2838 basic padding to resist netflow-based traffic analysis and to serve as
2839 the basis of other padding in the future, and adds rust support to the
2842 It also contains numerous other small features and improvements to
2843 security, correctness, and performance.
2845 Below are the changes since 0.3.0.7.
2847 o Major features (directory protocol):
2848 - Tor relays and authorities can now serve clients an abbreviated
2849 version of the consensus document, containing only the changes
2850 since an older consensus document that the client holds. Clients
2851 now request these documents when available. When both client and
2852 server use this new protocol, they will use far less bandwidth (up
2853 to 94% less) to keep the client's consensus up-to-date. Implements
2854 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
2855 - Tor can now compress directory traffic with lzma or with zstd
2856 compression algorithms, which can deliver better bandwidth
2857 performance. Because lzma is computationally expensive, it's only
2858 used for documents that can be compressed once and served many
2859 times. Support for these algorithms requires that tor is built
2860 with the libzstd and/or liblzma libraries available. Implements
2861 proposal 278; closes ticket 21662.
2862 - Relays now perform the more expensive compression operations, and
2863 consensus diff generation, in worker threads. This separation
2864 avoids delaying the main thread when a new consensus arrives.
2866 o Major features (experimental):
2867 - Tor can now build modules written in Rust. To turn this on, pass
2868 the "--enable-rust" flag to the configure script. It's not time to
2869 get excited yet: currently, there is no actual Rust functionality
2870 beyond some simple glue code, and a notice at startup to tell you
2871 that Rust is running. Still, we hope that programmers and
2872 packagers will try building Tor with Rust support, so that we can
2873 find issues and solve portability problems. Closes ticket 22106.
2875 o Major features (traffic analysis resistance):
2876 - Connections between clients and relays now send a padding cell in
2877 each direction every 1.5 to 9.5 seconds (tunable via consensus
2878 parameters). This padding will not resist specialized
2879 eavesdroppers, but it should be enough to make many ISPs' routine
2880 network flow logging less useful in traffic analysis against
2883 Padding is negotiated using Tor's link protocol, so both relays
2884 and clients must upgrade for this to take effect. Clients may
2885 still send padding despite the relay's version by setting
2886 ConnectionPadding 1 in torrc, and may disable padding by setting
2887 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
2888 users with the torrc option ReducedConnectionPadding. Implements
2889 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
2890 - Relays will publish 24 hour totals of padding and non-padding cell
2891 counts to their extra-info descriptors, unless PaddingStatistics 0
2892 is set in torrc. These 24 hour totals are also rounded to
2895 o Major bugfixes (connection usage):
2896 - We use NETINFO cells to try to determine if both relays involved
2897 in a connection will agree on the canonical status of that
2898 connection. We prefer the connections where this is the case for
2899 extend cells, and try to close connections where relays disagree
2900 on their canonical status early. Also, we now prefer the oldest
2901 valid connection for extend cells. These two changes should reduce
2902 the number of long-term connections that are kept open between
2903 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
2904 - Relays now log hourly statistics (look for
2905 "channel_check_for_duplicates" lines) on the total number of
2906 connections to other relays. If the number of connections per
2907 relay is unexpectedly large, this log message is at notice level.
2908 Otherwise it is at info.
2910 o Major bugfixes (entry guards):
2911 - Don't block bootstrapping when a primary bridge is offline and we
2912 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2913 21969; bugfix on 0.3.0.3-alpha.
2915 o Major bugfixes (linux TPROXY support):
2916 - Fix a typo that had prevented TPROXY-based transparent proxying
2917 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2918 Patch from "d4fq0fQAgoJ".
2920 o Minor features (security, windows):
2921 - Enable a couple of pieces of Windows hardening: one
2922 (HeapEnableTerminationOnCorruption) that has been on-by-default
2923 since Windows 8, and unavailable before Windows 7; and one
2924 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2925 affect us, but shouldn't do any harm. Closes ticket 21953.
2927 o Minor features (config options):
2928 - Allow "%include" directives in torrc configuration files. These
2929 directives import the settings from other files, or from all the
2930 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
2931 - Make SAVECONF return an error when overwriting a torrc that has
2932 includes. Using SAVECONF with the FORCE option will allow it to
2933 overwrite torrc even if includes are used. Related to ticket 1922.
2934 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
2935 will work without the FORCE option. Related to ticket 1922.
2937 o Minor features (controller):
2938 - Warn the first time that a controller requests data in the long-
2939 deprecated 'GETINFO network-status' format. Closes ticket 21703.
2941 o Minor features (defaults):
2942 - The default value for UseCreateFast is now 0: clients which
2943 haven't yet received a consensus document will now use a proper
2944 ntor handshake to talk to their directory servers whenever they
2945 can. Closes ticket 21407.
2946 - Onion key rotation and expiry intervals are now defined as a
2947 network consensus parameter, per proposal 274. The default
2948 lifetime of an onion key is increased from 7 to 28 days. Old onion
2949 keys will expire after 7 days by default. This change will make
2950 consensus diffs much smaller, and save significant bandwidth.
2951 Closes ticket 21641.
2953 o Minor features (fallback directory list):
2954 - Update the fallback directory mirror whitelist and blacklist based
2955 on operator emails. Closes task 21121.
2956 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2957 December 2016 (of which ~126 were still functional) with a list of
2958 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2959 2017. Resolves ticket 21564.
2961 o Minor features (hidden services, logging):
2962 - Log a message when a hidden service descriptor has fewer
2963 introduction points than specified in
2964 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
2965 - Log a message when a hidden service reaches its introduction point
2966 circuit limit, and when that limit is reset. Follow up to ticket
2967 21594; closes ticket 21622.
2968 - Warn user if multiple entries in EntryNodes and at least one
2969 HiddenService are used together. Pinning EntryNodes along with a
2970 hidden service can be possibly harmful; for instance see ticket
2971 14917 or 21155. Closes ticket 21155.
2973 o Minor features (linux seccomp2 sandbox):
2974 - We now have a document storage backend compatible with the Linux
2975 seccomp2 sandbox. This backend is used for consensus documents and
2976 diffs between them; in the long term, we'd like to use it for
2977 unparseable directory material too. Closes ticket 21645
2978 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
2979 from 1MB to 16MB. This was necessary with the glibc allocator in
2980 order to allow worker threads to allocate more memory -- which in
2981 turn is necessary because of our new use of worker threads for
2982 compression. Closes ticket 22096.
2984 o Minor features (logging):
2985 - Log files are no longer created world-readable by default.
2986 (Previously, most distributors would store the logs in a non-
2987 world-readable location to prevent inappropriate access. This
2988 change is an extra precaution.) Closes ticket 21729; patch
2991 o Minor features (performance):
2992 - Our Keccak (SHA-3) implementation now accesses memory more
2993 efficiently, especially on little-endian systems. Closes
2995 - Add an O(1) implementation of channel_find_by_global_id(), to
2996 speed some controller functions.
2998 o Minor features (relay, configuration):
2999 - The MyFamily option may now be repeated as many times as desired,
3000 for relays that want to configure large families. Closes ticket
3001 4998; patch by Daniel Pinto.
3003 o Minor features (safety):
3004 - Add an explicit check to extrainfo_parse_entry_from_string() for
3005 NULL inputs. We don't believe this can actually happen, but it may
3006 help silence a warning from the Clang analyzer. Closes
3009 o Minor features (testing):
3010 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
3011 When Tor is compiled with this option, we disable a number of
3012 redundant memory-safety failsafes that are intended to stop bugs
3013 from becoming security issues. This makes it easier to hunt for
3014 bugs that would be security issues without the failsafes turned
3015 on. Closes ticket 21439.
3016 - Add a general event-tracing instrumentation support to Tor. This
3017 subsystem will enable developers and researchers to add fine-
3018 grained instrumentation to their Tor instances, for use when
3019 examining Tor network performance issues. There are no trace
3020 events yet, and event-tracing is off by default unless enabled at
3021 compile time. Implements ticket 13802.
3022 - Improve our version parsing tests: add tests for typical version
3023 components, add tests for invalid versions, including numeric
3024 range and non-numeric prefixes. Unit tests 21278, 21450, and
3025 21507. Partially implements 21470.
3027 o Minor bugfixes (bandwidth accounting):
3028 - Roll over monthly accounting at the configured hour and minute,
3029 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3030 Found by Andrey Karpov with PVS-Studio.
3032 o Minor bugfixes (code correctness):
3033 - Accurately identify client connections by their lack of peer
3034 authentication. This means that we bail out earlier if asked to
3035 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
3038 o Minor bugfixes (configuration):
3039 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
3040 bug 22252; bugfix on 0.2.9.3-alpha.
3042 o Minor bugfixes (connection lifespan):
3043 - Allow more control over how long TLS connections are kept open:
3044 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
3045 single option called CircuitsAvailableTimeout. Also, allow the
3046 consensus to control the default values for both this preference
3047 and the lifespan of relay-to-relay connections. Fixes bug 17592;
3048 bugfix on 0.2.5.5-alpha.
3049 - Increase the initial circuit build timeout testing frequency, to
3050 help ensure that ReducedConnectionPadding clients finish learning
3051 a timeout before their orconn would expire. The initial testing
3052 rate was set back in the days of TAP and before the Tor Browser
3053 updater, when we had to be much more careful about new clients
3054 making lots of circuits. With this change, a circuit build timeout
3055 is learned in about 15-20 minutes, instead of 100-120 minutes.
3057 o Minor bugfixes (controller):
3058 - GETINFO onions/current and onions/detached no longer respond with
3059 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
3060 - Trigger HS descriptor events on the control port when the client
3061 fails to pick a hidden service directory for a hidden service.
3062 This can happen if all the hidden service directories are in
3063 ExcludeNodes, or they have all been queried within the last 15
3064 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
3066 o Minor bugfixes (directory authority):
3067 - When rejecting a router descriptor for running an obsolete version
3068 of Tor without ntor support, warn about the obsolete tor version,
3069 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
3070 - Prevent the shared randomness subsystem from asserting when
3071 initialized by a bridge authority with an incomplete configuration
3072 file. Fixes bug 21586; bugfix on 0.2.9.8.
3074 o Minor bugfixes (exit-side DNS):
3075 - Fix an untriggerable assertion that checked the output of a
3076 libevent DNS error, so that the assertion actually behaves as
3077 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
3078 Karpov using PVS-Studio.
3080 o Minor bugfixes (fallback directories):
3081 - Make the usage example in updateFallbackDirs.py actually work, and
3082 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
3083 - Decrease the guard flag average required to be a fallback. This
3084 allows us to keep relays that have their guard flag removed when
3085 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
3086 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
3087 bugfix on 0.2.8.1-alpha.
3088 - Make sure fallback directory mirrors have the same address, port,
3089 and relay identity key for at least 30 days before they are
3090 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
3092 o Minor bugfixes (hidden services):
3093 - Stop printing a cryptic warning when a hidden service gets a
3094 request to connect to a virtual port that it hasn't configured.
3095 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
3096 - Simplify hidden service descriptor creation by using an existing
3097 flag to check if an introduction point is established. Fixes bug
3098 21599; bugfix on 0.2.7.2-alpha.
3100 o Minor bugfixes (memory leak):
3101 - Fix a small memory leak at exit from the backtrace handler code.
3102 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
3104 o Minor bugfixes (protocol, logging):
3105 - Downgrade a log statement about unexpected relay cells from "bug"
3106 to "protocol warning", because there is at least one use case
3107 where it can be triggered by a buggy tor implementation. Fixes bug
3108 21293; bugfix on 0.1.1.14-alpha.
3110 o Minor bugfixes (testing):
3111 - Use unbuffered I/O for utility functions around the
3112 process_handle_t type. This fixes unit test failures reported on
3113 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
3114 - Make display of captured unit test log messages consistent. Fixes
3115 bug 21510; bugfix on 0.2.9.3-alpha.
3116 - Make test-network.sh always call chutney's test-network.sh.
3117 Previously, this only worked on systems which had bash installed,
3118 due to some bash-specific code in the script. Fixes bug 19699;
3119 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
3121 o Minor bugfixes (voting consistency):
3122 - Reject version numbers with non-numeric prefixes (such as +, -, or
3123 whitespace). Disallowing whitespace prevents differential version
3124 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3125 and part of 21508; bugfix on 0.0.8pre1.
3127 o Minor bugfixes (windows, relay):
3128 - Resolve "Failure from drain_fd: No error" warnings on Windows
3129 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
3131 o Code simplification and refactoring:
3132 - Break up the 630-line function connection_dir_client_reached_eof()
3133 into a dozen smaller functions. This change should help
3134 maintainability and readability of the client directory code.
3135 - Isolate our use of the openssl headers so that they are only
3136 included from our crypto wrapper modules, and from tests that
3137 examine those modules' internals. Closes ticket 21841.
3138 - Simplify our API to launch directory requests, making it more
3139 extensible and less error-prone. Now it's easier to add extra
3140 headers to directory requests. Closes ticket 21646.
3141 - Our base64 decoding functions no longer overestimate the output
3142 space that they need when parsing unpadded inputs. Closes
3144 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
3145 Resolves ticket 22213.
3146 - The logic that directory caches use to spool request to clients,
3147 serving them one part at a time so as not to allocate too much
3148 memory, has been refactored for consistency. Previously there was
3149 a separate spooling implementation per type of spoolable data. Now
3150 there is one common spooling implementation, with extensible data
3151 types. Closes ticket 21651.
3152 - Tor's compression module now supports multiple backends. Part of
3153 the implementation for proposal 278; closes ticket 21663.
3156 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
3157 Closes ticket 21873.
3158 - Correct documentation about the default DataDirectory value.
3159 Closes ticket 21151.
3160 - Document the default behavior of NumEntryGuards and
3161 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
3163 - Document key=value pluggable transport arguments for Bridge lines
3164 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
3165 - Note that bandwidth-limiting options don't affect TCP headers or
3166 DNS. Closes ticket 17170.
3168 o Removed features (configuration options, all in ticket 22060):
3169 - These configuration options are now marked Obsolete, and no longer
3170 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
3171 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
3172 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
3173 in 0.2.9.2-alpha and have now been removed. The previous default
3174 behavior is now always chosen; the previous (less secure) non-
3175 default behavior is now unavailable.
3176 - CloseHSClientCircuitsImmediatelyOnTimeout and
3177 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
3178 0.2.9.2-alpha and now have been removed. HS circuits never close
3179 on circuit build timeout; they have a longer timeout period.
3180 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
3181 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
3182 (and others) to configure listen-only and advertise-only addresses.
3184 o Removed features (tools):
3185 - We've removed the tor-checkkey tool from src/tools. Long ago, we
3186 used it to help people detect RSA keys that were generated by
3187 versions of Debian affected by CVE-2008-0166. But those keys have
3188 been out of circulation for ages, and this tool is no longer
3189 required. Closes ticket 21842.
3192 Changes in version 0.3.0.7 - 2017-05-15
3193 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
3194 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
3195 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
3196 clients are not affected.
3198 o Major bugfixes (hidden service directory, security):
3199 - Fix an assertion failure in the hidden service directory code, which
3200 could be used by an attacker to remotely cause a Tor relay process to
3201 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
3202 should upgrade. This security issue is tracked as TROVE-2017-002.
3203 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
3206 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3209 o Minor features (future-proofing):
3210 - Tor no longer refuses to download microdescriptors or descriptors
3211 if they are listed as "published in the future". This change will
3212 eventually allow us to stop listing meaningful "published" dates
3213 in microdescriptor consensuses, and thereby allow us to reduce the
3214 resources required to download consensus diffs by over 50%.
3215 Implements part of ticket 21642; implements part of proposal 275.
3217 o Minor bugfixes (Linux seccomp2 sandbox):
3218 - The getpid() system call is now permitted under the Linux seccomp2
3219 sandbox, to avoid crashing with versions of OpenSSL (and other
3220 libraries) that attempt to learn the process's PID by using the
3221 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3225 Changes in version 0.3.0.6 - 2017-04-26
3226 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
3228 With the 0.3.0 series, clients and relays now use Ed25519 keys to
3229 authenticate their link connections to relays, rather than the old
3230 RSA1024 keys that they used before. (Circuit crypto has been
3231 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
3232 the guard selection and replacement algorithm to behave more robustly
3233 in the presence of unreliable networks, and to resist guard-
3236 This series also includes numerous other small features and bugfixes,
3237 along with more groundwork for the upcoming hidden-services revamp.
3239 Per our stable release policy, we plan to support the Tor 0.3.0
3240 release series for at least the next nine months, or for three months
3241 after the first stable release of the 0.3.1 series: whichever is
3242 longer. If you need a release with long-term support, we recommend
3243 that you stay with the 0.2.9 series.
3245 Below are the changes since 0.3.0.5-rc. For a list of all changes
3246 since 0.2.9, see the ReleaseNotes file.
3248 o Minor features (geoip):
3249 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
3252 o Minor bugfixes (control port):
3253 - The GETINFO extra-info/digest/<digest> command was broken because
3254 of a wrong base16 decode return value check, introduced when
3255 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3257 o Minor bugfixes (crash prevention):
3258 - Fix a (currently untriggerable, but potentially dangerous) crash
3259 bug when base32-encoding inputs whose sizes are not a multiple of
3260 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
3263 Changes in version 0.3.0.5-rc - 2017-04-05
3264 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
3265 0.3.0 release series.
3267 This is the second release candidate in the Tor 0.3.0 series, and has
3268 much fewer changes than the first. If we find no new bugs or
3269 regressions here, the first stable 0.3.0 release will be nearly
3272 o Major bugfixes (crash, directory connections):
3273 - Fix a rare crash when sending a begin cell on a circuit whose
3274 linked directory connection had already been closed. Fixes bug
3275 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3277 o Major bugfixes (guard selection):
3278 - Fix a guard selection bug where Tor would refuse to bootstrap in
3279 some cases if the user swapped a bridge for another bridge in
3280 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
3281 Reported by "torvlnt33r".
3283 o Minor features (geoip):
3284 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
3287 o Minor bugfix (compilation):
3288 - Fix a warning when compiling hs_service.c. Previously, it had no
3289 exported symbols when compiled for libor.a, resulting in a
3290 compilation warning from clang. Fixes bug 21825; bugfix
3293 o Minor bugfixes (hidden services):
3294 - Make hidden services check for failed intro point connections,
3295 even when they have exceeded their intro point creation limit.
3296 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
3297 - Make hidden services with 8 to 10 introduction points check for
3298 failed circuits immediately after startup. Previously, they would
3299 wait for 5 minutes before performing their first checks. Fixes bug
3300 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
3302 o Minor bugfixes (memory leaks):
3303 - Fix a memory leak when using GETCONF on a port option. Fixes bug
3304 21682; bugfix on 0.3.0.3-alpha.
3306 o Minor bugfixes (relay):
3307 - Avoid a double-marked-circuit warning that could happen when we
3308 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3311 o Minor bugfixes (tests):
3312 - Run the entry_guard_parse_from_state_full() test with the time set
3313 to a specific date. (The guard state that this test was parsing
3314 contained guards that had expired since the test was first
3315 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
3318 - Update the description of the directory server options in the
3319 manual page, to clarify that a relay no longer needs to set
3320 DirPort in order to be a directory cache. Closes ticket 21720.
3324 Changes in version 0.2.8.13 - 2017-03-03
3325 Tor 0.2.8.13 backports a security fix from later Tor
3326 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
3327 this release, if for some reason they cannot upgrade to a later
3328 release series, and if they build Tor with the --enable-expensive-hardening
3331 Note that support for Tor 0.2.8.x is ending next year: we will not issue
3332 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
3333 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3335 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3336 - Fix an integer underflow bug when comparing malformed Tor
3337 versions. This bug could crash Tor when built with
3338 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3339 0.2.9.8, which were built with -ftrapv by default. In other cases
3340 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3341 on 0.0.8pre1. Found by OSS-Fuzz.
3343 o Minor features (geoip):
3344 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3348 Changes in version 0.2.7.7 - 2017-03-03
3349 Tor 0.2.7.7 backports a number of security fixes from later Tor
3350 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
3351 this release, if for some reason they cannot upgrade to a later
3354 Note that support for Tor 0.2.7.x is ending this year: we will not issue
3355 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
3356 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3358 o Directory authority changes (backport from 0.2.8.5-rc):
3359 - Urras is no longer a directory authority. Closes ticket 19271.
3361 o Directory authority changes (backport from 0.2.9.2-alpha):
3362 - The "Tonga" bridge authority has been retired; the new bridge
3363 authority is "Bifroest". Closes tickets 19728 and 19690.
3365 o Directory authority key updates (backport from 0.2.8.1-alpha):
3366 - Update the V3 identity key for the dannenberg directory authority:
3367 it was changed on 18 November 2015. Closes task 17906. Patch
3370 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3371 - Fix a bug in parsing that could cause clients to read a single
3372 byte past the end of an allocated region. This bug could be used
3373 to cause hardened clients (built with --enable-expensive-hardening)
3374 to crash if they tried to visit a hostile hidden service. Non-
3375 hardened clients are only affected depending on the details of
3376 their platform's memory allocator. Fixes bug 21018; bugfix on
3377 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3378 2016-12-002 and as CVE-2016-1254.
3380 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3381 - Stop a crash that could occur when a client running with DNSPort
3382 received a query with multiple address types, and the first
3383 address type was not supported. Found and fixed by Scott Dial.
3384 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3385 - Prevent a class of security bugs caused by treating the contents
3386 of a buffer chunk as if they were a NUL-terminated string. At
3387 least one such bug seems to be present in all currently used
3388 versions of Tor, and would allow an attacker to remotely crash
3389 most Tor instances, especially those compiled with extra compiler
3390 hardening. With this defense in place, such bugs can't crash Tor,
3391 though we should still fix them as they occur. Closes ticket
3392 20384 (TROVE-2016-10-001).
3394 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3395 - Avoid a difficult-to-trigger heap corruption attack when extending
3396 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3397 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3398 Reported by Guido Vranken.
3400 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3401 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3402 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3404 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3405 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3406 pointer to the previous (uninitialized) key value. The impact here
3407 should be limited to a difficult-to-trigger crash, if OpenSSL is
3408 running an engine that makes key generation failures possible, or
3409 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3410 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3413 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3414 - Fix an integer underflow bug when comparing malformed Tor
3415 versions. This bug could crash Tor when built with
3416 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3417 0.2.9.8, which were built with -ftrapv by default. In other cases
3418 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3419 on 0.0.8pre1. Found by OSS-Fuzz.
3421 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3422 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3423 zero size. Check size argument to memwipe() for underflow. Fixes
3424 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3427 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3428 - Make Tor survive errors involving connections without a
3429 corresponding event object. Previously we'd fail with an
3430 assertion; now we produce a log message. Related to bug 16248.
3432 o Minor features (geoip):
3433 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3437 Changes in version 0.2.6.11 - 2017-03-03
3438 Tor 0.2.6.11 backports a number of security fixes from later Tor
3439 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
3440 this release, if for some reason they cannot upgrade to a later
3443 Note that support for Tor 0.2.6.x is ending this year: we will not issue
3444 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
3445 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3447 o Directory authority changes (backport from 0.2.8.5-rc):
3448 - Urras is no longer a directory authority. Closes ticket 19271.
3450 o Directory authority changes (backport from 0.2.9.2-alpha):
3451 - The "Tonga" bridge authority has been retired; the new bridge
3452 authority is "Bifroest". Closes tickets 19728 and 19690.
3454 o Directory authority key updates (backport from 0.2.8.1-alpha):
3455 - Update the V3 identity key for the dannenberg directory authority:
3456 it was changed on 18 November 2015. Closes task 17906. Patch
3459 o Major features (security fixes, backport from 0.2.9.4-alpha):
3460 - Prevent a class of security bugs caused by treating the contents
3461 of a buffer chunk as if they were a NUL-terminated string. At
3462 least one such bug seems to be present in all currently used
3463 versions of Tor, and would allow an attacker to remotely crash
3464 most Tor instances, especially those compiled with extra compiler
3465 hardening. With this defense in place, such bugs can't crash Tor,
3466 though we should still fix them as they occur. Closes ticket
3467 20384 (TROVE-2016-10-001).
3469 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3470 - Fix a bug in parsing that could cause clients to read a single
3471 byte past the end of an allocated region. This bug could be used
3472 to cause hardened clients (built with --enable-expensive-hardening)
3473 to crash if they tried to visit a hostile hidden service. Non-
3474 hardened clients are only affected depending on the details of
3475 their platform's memory allocator. Fixes bug 21018; bugfix on
3476 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3477 2016-12-002 and as CVE-2016-1254.
3479 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3480 - Stop a crash that could occur when a client running with DNSPort
3481 received a query with multiple address types, and the first
3482 address type was not supported. Found and fixed by Scott Dial.
3483 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3485 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3486 - Fix an error that could cause us to read 4 bytes before the
3487 beginning of an openssl string. This bug could be used to cause
3488 Tor to crash on systems with unusual malloc implementations, or
3489 systems with unusual hardening installed. Fixes bug 17404; bugfix
3492 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3493 - Avoid a difficult-to-trigger heap corruption attack when extending
3494 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3495 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3496 Reported by Guido Vranken.
3498 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3499 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3500 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3502 o Major bugfixes (guard selection, backport from 0.2.7.6):
3503 - Actually look at the Guard flag when selecting a new directory
3504 guard. When we implemented the directory guard design, we
3505 accidentally started treating all relays as if they have the Guard
3506 flag during guard selection, leading to weaker anonymity and worse
3507 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3510 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3511 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3512 pointer to the previous (uninitialized) key value. The impact here
3513 should be limited to a difficult-to-trigger crash, if OpenSSL is
3514 running an engine that makes key generation failures possible, or
3515 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3516 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3519 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3520 - Fix an integer underflow bug when comparing malformed Tor
3521 versions. This bug could crash Tor when built with
3522 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3523 0.2.9.8, which were built with -ftrapv by default. In other cases
3524 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3525 on 0.0.8pre1. Found by OSS-Fuzz.
3527 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3528 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3529 zero size. Check size argument to memwipe() for underflow. Fixes
3530 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3533 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3534 - Make Tor survive errors involving connections without a
3535 corresponding event object. Previously we'd fail with an
3536 assertion; now we produce a log message. Related to bug 16248.
3538 o Minor features (geoip):
3539 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3542 o Minor bugfixes (compilation, backport from 0.2.7.6):
3543 - Fix a compilation warning with Clang 3.6: Do not check the
3544 presence of an address which can never be NULL. Fixes bug 17781.
3547 Changes in version 0.2.5.13 - 2017-03-03
3548 Tor 0.2.5.13 backports a number of security fixes from later Tor
3549 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
3550 this release, if for some reason they cannot upgrade to a later
3553 Note that support for Tor 0.2.5.x is ending next year: we will not issue
3554 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
3555 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3557 o Directory authority changes (backport from 0.2.8.5-rc):
3558 - Urras is no longer a directory authority. Closes ticket 19271.
3560 o Directory authority changes (backport from 0.2.9.2-alpha):
3561 - The "Tonga" bridge authority has been retired; the new bridge
3562 authority is "Bifroest". Closes tickets 19728 and 19690.
3564 o Directory authority key updates (backport from 0.2.8.1-alpha):
3565 - Update the V3 identity key for the dannenberg directory authority:
3566 it was changed on 18 November 2015. Closes task 17906. Patch
3569 o Major features (security fixes, backport from 0.2.9.4-alpha):
3570 - Prevent a class of security bugs caused by treating the contents
3571 of a buffer chunk as if they were a NUL-terminated string. At
3572 least one such bug seems to be present in all currently used
3573 versions of Tor, and would allow an attacker to remotely crash
3574 most Tor instances, especially those compiled with extra compiler
3575 hardening. With this defense in place, such bugs can't crash Tor,
3576 though we should still fix them as they occur. Closes ticket
3577 20384 (TROVE-2016-10-001).
3579 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3580 - Fix a bug in parsing that could cause clients to read a single
3581 byte past the end of an allocated region. This bug could be used
3582 to cause hardened clients (built with --enable-expensive-hardening)
3583 to crash if they tried to visit a hostile hidden service. Non-
3584 hardened clients are only affected depending on the details of
3585 their platform's memory allocator. Fixes bug 21018; bugfix on
3586 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3587 2016-12-002 and as CVE-2016-1254.
3589 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3590 - Stop a crash that could occur when a client running with DNSPort
3591 received a query with multiple address types, and the first
3592 address type was not supported. Found and fixed by Scott Dial.
3593 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3595 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3596 - Fix an error that could cause us to read 4 bytes before the
3597 beginning of an openssl string. This bug could be used to cause
3598 Tor to crash on systems with unusual malloc implementations, or
3599 systems with unusual hardening installed. Fixes bug 17404; bugfix
3602 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3603 - Avoid a difficult-to-trigger heap corruption attack when extending
3604 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3605 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3606 Reported by Guido Vranken.
3608 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3609 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3610 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3612 o Major bugfixes (guard selection, backport from 0.2.7.6):
3613 - Actually look at the Guard flag when selecting a new directory
3614 guard. When we implemented the directory guard design, we
3615 accidentally started treating all relays as if they have the Guard
3616 flag during guard selection, leading to weaker anonymity and worse
3617 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3620 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3621 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3622 pointer to the previous (uninitialized) key value. The impact here
3623 should be limited to a difficult-to-trigger crash, if OpenSSL is
3624 running an engine that makes key generation failures possible, or
3625 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3626 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3629 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3630 - Fix an integer underflow bug when comparing malformed Tor
3631 versions. This bug could crash Tor when built with
3632 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3633 0.2.9.8, which were built with -ftrapv by default. In other cases
3634 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3635 on 0.0.8pre1. Found by OSS-Fuzz.
3637 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3638 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3639 zero size. Check size argument to memwipe() for underflow. Fixes
3640 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3643 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3644 - Make Tor survive errors involving connections without a
3645 corresponding event object. Previously we'd fail with an
3646 assertion; now we produce a log message. Related to bug 16248.
3648 o Minor features (geoip):
3649 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3652 o Minor bugfixes (compilation, backport from 0.2.7.6):
3653 - Fix a compilation warning with Clang 3.6: Do not check the
3654 presence of an address which can never be NULL. Fixes bug 17781.
3656 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
3657 - Check for failures from crypto_early_init, and refuse to continue.
3658 A previous typo meant that we could keep going with an
3659 uninitialized crypto library, and would have OpenSSL initialize
3660 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
3661 when implementing ticket 4900. Patch by "teor".
3663 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3664 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3665 a client authorized hidden service. Fixes bug 15823; bugfix
3669 Changes in version 0.2.4.28 - 2017-03-03
3670 Tor 0.2.4.28 backports a number of security fixes from later Tor
3671 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
3672 this release, if for some reason they cannot upgrade to a later
3675 Note that support for Tor 0.2.4.x is ending soon: we will not issue
3676 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
3677 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
3679 o Directory authority changes (backport from 0.2.8.5-rc):
3680 - Urras is no longer a directory authority. Closes ticket 19271.
3682 o Directory authority changes (backport from 0.2.9.2-alpha):
3683 - The "Tonga" bridge authority has been retired; the new bridge
3684 authority is "Bifroest". Closes tickets 19728 and 19690.
3686 o Directory authority key updates (backport from 0.2.8.1-alpha):
3687 - Update the V3 identity key for the dannenberg directory authority:
3688 it was changed on 18 November 2015. Closes task 17906. Patch
3691 o Major features (security fixes, backport from 0.2.9.4-alpha):
3692 - Prevent a class of security bugs caused by treating the contents
3693 of a buffer chunk as if they were a NUL-terminated string. At
3694 least one such bug seems to be present in all currently used
3695 versions of Tor, and would allow an attacker to remotely crash
3696 most Tor instances, especially those compiled with extra compiler
3697 hardening. With this defense in place, such bugs can't crash Tor,
3698 though we should still fix them as they occur. Closes ticket
3699 20384 (TROVE-2016-10-001).
3701 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3702 - Fix a bug in parsing that could cause clients to read a single
3703 byte past the end of an allocated region. This bug could be used
3704 to cause hardened clients (built with --enable-expensive-hardening)
3705 to crash if they tried to visit a hostile hidden service. Non-
3706 hardened clients are only affected depending on the details of
3707 their platform's memory allocator. Fixes bug 21018; bugfix on
3708 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3709 2016-12-002 and as CVE-2016-1254.
3711 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3712 - Fix an error that could cause us to read 4 bytes before the
3713 beginning of an openssl string. This bug could be used to cause
3714 Tor to crash on systems with unusual malloc implementations, or
3715 systems with unusual hardening installed. Fixes bug 17404; bugfix
3718 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3719 - Avoid a difficult-to-trigger heap corruption attack when extending
3720 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3721 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3722 Reported by Guido Vranken.
3724 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3725 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3726 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3728 o Major bugfixes (guard selection, backport from 0.2.7.6):
3729 - Actually look at the Guard flag when selecting a new directory
3730 guard. When we implemented the directory guard design, we
3731 accidentally started treating all relays as if they have the Guard
3732 flag during guard selection, leading to weaker anonymity and worse
3733 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3736 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3737 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3738 pointer to the previous (uninitialized) key value. The impact here
3739 should be limited to a difficult-to-trigger crash, if OpenSSL is
3740 running an engine that makes key generation failures possible, or
3741 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3742 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3745 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3746 - Fix an integer underflow bug when comparing malformed Tor
3747 versions. This bug could crash Tor when built with
3748 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3749 0.2.9.8, which were built with -ftrapv by default. In other cases
3750 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3751 on 0.0.8pre1. Found by OSS-Fuzz.
3753 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3754 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3755 zero size. Check size argument to memwipe() for underflow. Fixes
3756 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3759 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3760 - Make Tor survive errors involving connections without a
3761 corresponding event object. Previously we'd fail with an
3762 assertion; now we produce a log message. Related to bug 16248.
3764 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
3765 - Make it harder for attackers to overload hidden services with
3766 introductions, by blocking multiple introduction requests on the
3767 same circuit. Resolves ticket 15515.
3769 o Minor features (geoip):
3770 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3773 o Minor bugfixes (compilation, backport from 0.2.7.6):
3774 - Fix a compilation warning with Clang 3.6: Do not check the
3775 presence of an address which can never be NULL. Fixes bug 17781.
3777 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3778 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3779 a client authorized hidden service. Fixes bug 15823; bugfix
3783 Changes in version 0.3.0.4-rc - 2017-03-01
3784 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
3785 0.3.0 release series, and introduces a few reliability features to
3786 keep them from coming back.
3788 This is the first release candidate in the Tor 0.3.0 series. If we
3789 find no new bugs or regressions here, the first stable 0.3.0 release
3790 will be nearly identical to it.
3792 o Major bugfixes (bridges):
3793 - When the same bridge is configured multiple times with the same
3794 identity, but at different address:port combinations, treat those
3795 bridge instances as separate guards. This fix restores the ability
3796 of clients to configure the same bridge with multiple pluggable
3797 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
3799 o Major bugfixes (hidden service directory v3):
3800 - Stop crashing on a failed v3 hidden service descriptor lookup
3801 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
3803 o Major bugfixes (parsing):
3804 - When parsing a malformed content-length field from an HTTP
3805 message, do not read off the end of the buffer. This bug was a
3806 potential remote denial-of-service attack against Tor clients and
3807 relays. A workaround was released in October 2016, to prevent this
3808 bug from crashing Tor. This is a fix for the underlying issue,
3809 which should no longer matter (if you applied the earlier patch).
3810 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
3811 using AFL (http://lcamtuf.coredump.cx/afl/).
3812 - Fix an integer underflow bug when comparing malformed Tor
3813 versions. This bug could crash Tor when built with
3814 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3815 0.2.9.8, which were built with -ftrapv by default. In other cases
3816 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3817 on 0.0.8pre1. Found by OSS-Fuzz.
3819 o Minor feature (protocol versioning):
3820 - Add new protocol version for proposal 224. HSIntro now advertises
3821 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
3823 o Minor features (directory authorities):
3824 - Directory authorities now reject descriptors that claim to be
3825 malformed versions of Tor. Helps prevent exploitation of
3827 - Reject version numbers with components that exceed INT32_MAX.
3828 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3829 Fixes bug 21450; bugfix on 0.0.8pre1.
3830 - Directory authorities now reject relays running versions
3831 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
3832 suffer from bug 20499 and don't keep their consensus cache
3833 up-to-date. Resolves ticket 20509.
3835 o Minor features (geoip):
3836 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3839 o Minor features (reliability, crash):
3840 - Try better to detect problems in buffers where they might grow (or
3841 think they have grown) over 2 GB in size. Diagnostic for
3844 o Minor features (testing):
3845 - During 'make test-network-all', if tor logs any warnings, ask
3846 chutney to output them. Requires a recent version of chutney with
3847 the 21572 patch. Implements 21570.
3849 o Minor bugfixes (certificate expiration time):
3850 - Avoid using link certificates that don't become valid till some
3851 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
3853 o Minor bugfixes (code correctness):
3854 - Repair a couple of (unreachable or harmless) cases of the risky
3855 comparison-by-subtraction pattern that caused bug 21278.
3856 - Remove a redundant check for the UseEntryGuards option from the
3857 options_transition_affects_guards() function. Fixes bug 21492;
3858 bugfix on 0.3.0.1-alpha.
3860 o Minor bugfixes (directory mirrors):
3861 - Allow relays to use directory mirrors without a DirPort: these
3862 relays need to be contacted over their ORPorts using a begindir
3863 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
3864 - Clarify the message logged when a remote relay is unexpectedly
3865 missing an ORPort or DirPort: users were confusing this with a
3866 local port. Fixes another case of bug 20711; bugfix
3869 o Minor bugfixes (guards):
3870 - Don't warn about a missing guard state on timeout-measurement
3871 circuits: they aren't supposed to be using guards. Fixes an
3872 instance of bug 21007; bugfix on 0.3.0.1-alpha.
3873 - Silence a BUG() warning when attempting to use a guard whose
3874 descriptor we don't know, and make this scenario less likely to
3875 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
3877 o Minor bugfixes (hidden service):
3878 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
3879 cells. Previously, we were using sizeof() on a pointer, instead of
3880 the real destination buffer. Fortunately, that value was only used
3881 to double-check that there was enough room--which was already
3882 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
3884 o Minor bugfixes (testing):
3885 - Fix Raspbian build issues related to missing socket errno in
3886 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
3888 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
3889 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
3890 - Use bash in src/test/test-network.sh. This ensures we reliably
3891 call chutney's newer tools/test-network.sh when available. Fixes
3892 bug 21562; bugfix on 0.2.9.1-alpha.
3895 - Small fixes to the fuzzing documentation. Closes ticket 21472.
3898 Changes in version 0.2.9.10 - 2017-03-01
3899 Tor 0.2.9.10 backports a security fix from later Tor release. It also
3900 includes fixes for some major issues affecting directory authorities,
3901 LibreSSL compatibility, and IPv6 correctness.
3903 The Tor 0.2.9.x release series is now marked as a long-term-support
3904 series. We intend to backport security fixes to 0.2.9.x until at
3905 least January of 2020.
3907 o Major bugfixes (directory authority, 0.3.0.3-alpha):
3908 - During voting, when marking a relay as a probable sybil, do not
3909 clear its BadExit flag: sybils can still be bad in other ways
3910 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3913 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
3914 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3915 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3916 exit policy rejects that port on more than an IPv6 /16 of
3917 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3918 which rejected a relay's own IPv6 address by default. Fixes bug
3919 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3921 o Major bugfixes (parsing, also in 0.3.0.4-rc):
3922 - Fix an integer underflow bug when comparing malformed Tor
3923 versions. This bug could crash Tor when built with
3924 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3925 0.2.9.8, which were built with -ftrapv by default. In other cases
3926 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3927 on 0.0.8pre1. Found by OSS-Fuzz.
3929 o Minor features (directory authorities, also in 0.3.0.4-rc):
3930 - Directory authorities now reject descriptors that claim to be
3931 malformed versions of Tor. Helps prevent exploitation of
3933 - Reject version numbers with components that exceed INT32_MAX.
3934 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3935 Fixes bug 21450; bugfix on 0.0.8pre1.
3937 o Minor features (geoip):
3938 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3941 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
3942 - Autoconf now checks to determine if OpenSSL structures are opaque,
3943 instead of explicitly checking for OpenSSL version numbers. Part
3945 - Support building with recent LibreSSL code that uses opaque
3946 structures. Closes ticket 21359.
3948 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
3949 - Repair a couple of (unreachable or harmless) cases of the risky
3950 comparison-by-subtraction pattern that caused bug 21278.
3952 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
3953 - The tor-resolve command line tool now rejects hostnames over 255
3954 characters in length. Previously, it would silently truncate them,
3955 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3956 Patch by "junglefowl".
3959 Changes in version 0.3.0.3-alpha - 2017-02-03
3960 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
3961 0.3.0.x development series, including some that could cause
3962 authorities to behave badly. There is also a fix for a longstanding
3963 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
3964 includes some smaller features and bugfixes.
3966 The Tor 0.3.0.x release series is now in patch-freeze: no additional
3967 features will be considered for inclusion in 0.3.0.x. We suspect that
3968 some bugs will probably remain, however, and we encourage people to
3971 o Major bugfixes (directory authority):
3972 - During voting, when marking a relay as a probable sybil, do not
3973 clear its BadExit flag: sybils can still be bad in other ways
3974 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3976 - When deciding whether we have just found a router to be reachable,
3977 do not penalize it for not having performed an Ed25519 link
3978 handshake if it does not claim to support an Ed25519 handshake.
3979 Previously, we would treat such relays as non-running. Fixes bug
3980 21107; bugfix on 0.3.0.1-alpha.
3982 o Major bugfixes (entry guards):
3983 - Stop trying to build circuits through entry guards for which we
3984 have no descriptor. Also, stop crashing in the case that we *do*
3985 accidentally try to build a circuit in such a state. Fixes bug
3986 21242; bugfix on 0.3.0.1-alpha.
3988 o Major bugfixes (IPv6 Exits):
3989 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3990 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3991 exit policy rejects that port on more than an IPv6 /16 of
3992 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3993 which rejected a relay's own IPv6 address by default. Fixes bug
3994 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3996 o Minor feature (client):
3997 - Enable IPv6 traffic on the SocksPort by default. To disable this,
3998 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
4000 o Minor feature (fallback scripts):
4001 - Add a check_existing mode to updateFallbackDirs.py, which checks
4002 if fallbacks in the hard-coded list are working. Closes ticket
4003 20174. Patch by haxxpop.
4005 o Minor features (ciphersuite selection):
4006 - Clients now advertise a list of ciphersuites closer to the ones
4007 preferred by Firefox. Closes part of ticket 15426.
4008 - Allow relays to accept a wider range of ciphersuites, including
4009 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
4011 o Minor features (controller, configuration):
4012 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
4013 and so on, now comes with a __*Port variant that will not be saved
4014 to the torrc file by the controller's SAVECONF command. This
4015 change allows TorBrowser to set up a single-use domain socket for
4016 each time it launches Tor. Closes ticket 20956.
4017 - The GETCONF command can now query options that may only be
4018 meaningful in context-sensitive lists. This allows the controller
4019 to query the mixed SocksPort/__SocksPort style options introduced
4020 in feature 20956. Implements ticket 21300.
4022 o Minor features (portability, compilation):
4023 - Autoconf now checks to determine if OpenSSL structures are opaque,
4024 instead of explicitly checking for OpenSSL version numbers. Part
4026 - Support building with recent LibreSSL code that uses opaque
4027 structures. Closes ticket 21359.
4029 o Minor features (relay):
4030 - We now allow separation of exit and relay traffic to different
4031 source IP addresses, using the OutboundBindAddressExit and
4032 OutboundBindAddressOR options respectively. Closes ticket 17975.
4033 Written by Michael Sonntag.
4035 o Minor bugfix (logging):
4036 - Don't recommend the use of Tor2web in non-anonymous mode.
4037 Recommending Tor2web is a bad idea because the client loses all
4038 anonymity. Tor2web should only be used in specific cases by users
4039 who *know* and understand the issues. Fixes bug 21294; bugfix
4042 o Minor bugfixes (client):
4043 - Always recover from failures in extend_info_from_node(), in an
4044 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
4045 bugfix on 0.2.3.1-alpha.
4047 o Minor bugfixes (client, entry guards):
4048 - Fix a bug warning (with backtrace) when we fail a channel that
4049 circuits to fallback directories on it. Fixes bug 21128; bugfix
4051 - Fix a spurious bug warning (with backtrace) when removing an
4052 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
4053 - Fix a bug of the new guard algorithm where tor could stall for up
4054 to 10 minutes before retrying a guard after a long period of no
4055 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
4056 - Do not try to build circuits until we have descriptors for our
4057 primary entry guards. Related to fix for bug 21242.
4059 o Minor bugfixes (configure, autoconf):
4060 - Rename the configure option --enable-expensive-hardening to
4061 --enable-fragile-hardening. Expensive hardening makes the tor
4062 daemon abort when some kinds of issues are detected. Thus, it
4063 makes tor more at risk of remote crashes but safer against RCE or
4064 heartbleed bug category. We now try to explain this issue in a
4065 message from the configure script. Fixes bug 21290; bugfix
4068 o Minor bugfixes (controller):
4069 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
4070 20824; bugfix on 0.3.0.1-alpha.
4072 o Minor bugfixes (hidden service):
4073 - Clean up the code for expiring intro points with no associated
4074 circuits. It was causing, rarely, a service with some expiring
4075 introduction points to not open enough additional introduction
4076 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
4077 - Stop setting the torrc option HiddenServiceStatistics to "0" just
4078 because we're not a bridge or relay. Instead, we preserve whatever
4079 value the user set (or didn't set). Fixes bug 21150; bugfix
4081 - Resolve two possible underflows which could lead to creating and
4082 closing a lot of introduction point circuits in a non-stop loop.
4083 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
4085 o Minor bugfixes (portability):
4086 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
4087 It is supported by OpenBSD itself, and also by most OpenBSD
4088 variants (such as Bitrig). Fixes bug 20980; bugfix
4090 - When mapping a file of length greater than SIZE_MAX, do not
4091 silently truncate its contents. This issue could occur on 32 bit
4092 systems with large file support and files which are larger than 4
4093 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
4095 o Minor bugfixes (tor-resolve):
4096 - The tor-resolve command line tool now rejects hostnames over 255
4097 characters in length. Previously, it would silently truncate them,
4098 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
4099 Patch by "junglefowl".
4101 o Minor bugfixes (Windows services):
4102 - Be sure to initialize the monotonic time subsystem before using
4103 it, even when running as an NT service. Fixes bug 21356; bugfix
4107 Changes in version 0.3.0.2-alpha - 2017-01-23
4108 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
4109 cause relays and clients to crash, even if they were not built with
4110 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
4111 versions, and also affects 0.3.0.1-alpha: all relays running an affected
4112 version should upgrade.
4114 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
4115 time-to-live values, makes directory authorities enforce the 1-to-1
4116 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
4117 client-side onion service reachability bug, does better at selecting
4118 the set of fallback directories, and more.
4120 o Major bugfixes (security, also in 0.2.9.9):
4121 - Downgrade the "-ftrapv" option from "always on" to "only on when
4122 --enable-expensive-hardening is provided." This hardening option, like
4123 others, can turn survivable bugs into crashes--and having it on by
4124 default made a (relatively harmless) integer overflow bug into a
4125 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
4128 o Major features (security):
4129 - Change the algorithm used to decide DNS TTLs on client and server
4130 side, to better resist DNS-based correlation attacks like the
4131 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
4132 Feamster. Now relays only return one of two possible DNS TTL
4133 values, and clients are willing to believe DNS TTL values up to 3
4134 hours long. Closes ticket 19769.
4136 o Major features (directory authority, security):
4137 - The default for AuthDirPinKeys is now 1: directory authorities
4138 will reject relays where the RSA identity key matches a previously
4139 seen value, but the Ed25519 key has changed. Closes ticket 18319.
4141 o Major bugfixes (client, guard, crash):
4142 - In circuit_get_global_origin_list(), return the actual list of
4143 origin circuits. The previous version of this code returned the
4144 list of all the circuits, and could have caused strange bugs,
4145 including possible crashes. Fixes bug 21118; bugfix
4148 o Major bugfixes (client, onion service, also in 0.2.9.9):
4149 - Fix a client-side onion service reachability bug, where multiple
4150 socks requests to an onion service (or a single slow request)
4151 could cause us to mistakenly mark some of the service's
4152 introduction points as failed, and we cache that failure so
4153 eventually we run out and can't reach the service. Also resolves a
4154 mysterious "Remote server sent bogus reason code 65021" log
4155 warning. The bug was introduced in ticket 17218, where we tried to
4156 remember the circuit end reason as a uint16_t, which mangled
4157 negative values. Partially fixes bug 21056 and fixes bug 20307;
4158 bugfix on 0.2.8.1-alpha.
4160 o Major bugfixes (DNS):
4161 - Fix a bug that prevented exit nodes from caching DNS records for
4162 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
4164 o Minor features (controller):
4165 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
4166 shared-random values to the controller. Closes ticket 19925.
4168 o Minor features (entry guards):
4169 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
4170 break regression tests.
4171 - Require UseEntryGuards when UseBridges is set, in order to make
4172 sure bridges aren't bypassed. Resolves ticket 20502.
4174 o Minor features (fallback directories):
4175 - Select 200 fallback directories for each release. Closes
4177 - Allow 3 fallback relays per operator, which is safe now that we
4178 are choosing 200 fallback relays. Closes ticket 20912.
4179 - Exclude relays affected by bug 20499 from the fallback list.
4180 Exclude relays from the fallback list if they are running versions
4181 known to be affected by bug 20499, or if in our tests they deliver
4182 a stale consensus (i.e. one that expired more than 24 hours ago).
4183 Closes ticket 20539.
4184 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
4186 - Require fallback directories to have the same address and port for
4187 7 days (now that we have enough relays with this stability).
4188 Relays whose OnionOO stability timer is reset on restart by bug
4189 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
4190 this issue. Closes ticket 20880; maintains short-term fix
4192 - Require fallbacks to have flags for 90% of the time (weighted
4193 decaying average), rather than 95%. This allows at least 73% of
4194 clients to bootstrap in the first 5 seconds without contacting an
4195 authority. Part of ticket 18828.
4196 - Annotate updateFallbackDirs.py with the bandwidth and consensus
4197 weight for each candidate fallback. Closes ticket 20878.
4198 - Make it easier to change the output sort order of fallbacks.
4199 Closes ticket 20822.
4200 - Display the relay fingerprint when downloading consensuses from
4201 fallbacks. Closes ticket 20908.
4203 o Minor features (geoip, also in 0.2.9.9):
4204 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4207 o Minor features (next-gen onion service directories):
4208 - Remove the "EnableOnionServicesV3" consensus parameter that we
4209 introduced in 0.3.0.1-alpha: relays are now always willing to act
4210 as v3 onion service directories. Resolves ticket 19899.
4212 o Minor features (linting):
4213 - Enhance the changes file linter to warn on Tor versions that are
4214 prefixed with "tor-". Closes ticket 21096.
4216 o Minor features (logging):
4217 - In several places, describe unset ed25519 keys as "<unset>",
4218 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
4220 o Minor bugfix (control protocol):
4221 - The reply to a "GETINFO config/names" request via the control
4222 protocol now spells the type "Dependent" correctly. This is a
4223 breaking change in the control protocol. (The field seems to be
4224 ignored by the most common known controllers.) Fixes bug 18146;
4225 bugfix on 0.1.1.4-alpha.
4227 o Minor bugfixes (bug resilience):
4228 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
4229 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
4230 Hans Jerry Illikainen.
4232 o Minor bugfixes (build):
4233 - Replace obsolete Autoconf macros with their modern equivalent and
4234 prevent similar issues in the future. Fixes bug 20990; bugfix
4237 o Minor bugfixes (client, guards):
4238 - Fix bug where Tor would think that there are circuits waiting for
4239 better guards even though those circuits have been freed. Fixes
4240 bug 21142; bugfix on 0.3.0.1-alpha.
4242 o Minor bugfixes (config):
4243 - Don't assert on startup when trying to get the options list and
4244 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
4245 options so of course they aren't ready yet. Fixes bug 21062;
4246 bugfix on 0.2.9.3-alpha.
4248 o Minor bugfixes (controller):
4249 - Make the GETINFO interface for inquiring about entry guards
4250 support the new guards backend. Fixes bug 20823; bugfix
4253 o Minor bugfixes (dead code):
4254 - Remove a redundant check for PidFile changes at runtime in
4255 options_transition_allowed(): this check is already performed
4256 regardless of whether the sandbox is active. Fixes bug 21123;
4257 bugfix on 0.2.5.4-alpha.
4259 o Minor bugfixes (documentation):
4260 - Update the tor manual page to document every option that can not
4261 be changed while tor is running. Fixes bug 21122.
4263 o Minor bugfixes (fallback directories):
4264 - Stop failing when a relay has no uptime data in
4265 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
4266 - Avoid checking fallback candidates' DirPorts if they are down in
4267 OnionOO. When a relay operator has multiple relays, this
4268 prioritizes relays that are up over relays that are down. Fixes
4269 bug 20926; bugfix on 0.2.8.3-alpha.
4270 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
4271 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
4273 o Minor bugfixes (guards, bootstrapping):
4274 - When connecting to a directory guard during bootstrap, do not mark
4275 the guard as successful until we receive a good-looking directory
4276 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
4278 o Minor bugfixes (onion services):
4279 - Fix the config reload pruning of old vs new services so it
4280 actually works when both ephemeral and non-ephemeral services are
4281 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
4282 - Allow the number of introduction points to be as low as 0, rather
4283 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
4285 o Minor bugfixes (IPv6):
4286 - Make IPv6-using clients try harder to find an IPv6 directory
4287 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
4288 - When IPv6 addresses have not been downloaded yet (microdesc
4289 consensus documents don't list relay IPv6 addresses), use hard-
4290 coded addresses for authorities, fallbacks, and configured
4291 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
4292 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
4294 o Minor bugfixes (memory leaks):
4295 - Fix a memory leak when configuring hidden services. Fixes bug
4296 20987; bugfix on 0.3.0.1-alpha.
4298 o Minor bugfixes (portability, also in 0.2.9.9):
4299 - Avoid crashing when Tor is built using headers that contain
4300 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4301 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4303 - Fix Libevent detection on platforms without Libevent 1 headers
4304 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4306 o Minor bugfixes (relay):
4307 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
4308 initializing the keys would reset the DataDirectory to 0700
4309 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
4310 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
4312 o Minor bugfixes (testing):
4313 - Remove undefined behavior from the backtrace generator by removing
4314 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
4316 o Minor bugfixes (unit tests):
4317 - Allow the unit tests to pass even when DNS lookups of bogus
4318 addresses do not fail as expected. Fixes bug 20862 and 20863;
4319 bugfix on unit tests introduced in 0.2.8.1-alpha
4320 through 0.2.9.4-alpha.
4322 o Code simplification and refactoring:
4323 - Refactor code to manipulate global_origin_circuit_list into
4324 separate functions. Closes ticket 20921.
4326 o Documentation (formatting):
4327 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
4328 blocks were incorrectly appearing. Closes ticket 20885.
4330 o Documentation (man page):
4331 - Clarify many options in tor.1 and add some min/max values for
4332 HiddenService options. Closes ticket 21058.
4335 Changes in version 0.2.9.9 - 2017-01-23
4336 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
4337 cause relays and clients to crash, even if they were not built with
4338 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
4339 versions, and also affects 0.3.0.1-alpha: all relays running an affected
4340 version should upgrade.
4342 This release also resolves a client-side onion service reachability
4343 bug, and resolves a pair of small portability issues.
4345 o Major bugfixes (security):
4346 - Downgrade the "-ftrapv" option from "always on" to "only on when
4347 --enable-expensive-hardening is provided." This hardening option,
4348 like others, can turn survivable bugs into crashes -- and having
4349 it on by default made a (relatively harmless) integer overflow bug
4350 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
4351 bugfix on 0.2.9.1-alpha.
4353 o Major bugfixes (client, onion service):
4354 - Fix a client-side onion service reachability bug, where multiple
4355 socks requests to an onion service (or a single slow request)
4356 could cause us to mistakenly mark some of the service's
4357 introduction points as failed, and we cache that failure so
4358 eventually we run out and can't reach the service. Also resolves a
4359 mysterious "Remote server sent bogus reason code 65021" log
4360 warning. The bug was introduced in ticket 17218, where we tried to
4361 remember the circuit end reason as a uint16_t, which mangled
4362 negative values. Partially fixes bug 21056 and fixes bug 20307;
4363 bugfix on 0.2.8.1-alpha.
4365 o Minor features (geoip):
4366 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4369 o Minor bugfixes (portability):
4370 - Avoid crashing when Tor is built using headers that contain
4371 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4372 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4374 - Fix Libevent detection on platforms without Libevent 1 headers
4375 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4378 Changes in version 0.3.0.1-alpha - 2016-12-19
4379 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
4380 series. It strengthens Tor's link and circuit handshakes by
4381 identifying relays by their Ed25519 keys, improves the algorithm that
4382 clients use to choose and maintain their list of guards, and includes
4383 additional backend support for the next-generation hidden service
4384 design. It also contains numerous other small features and
4385 improvements to security, correctness, and performance.
4387 Below are the changes since 0.2.9.8.
4389 o Major features (guard selection algorithm):
4390 - Tor's guard selection algorithm has been redesigned from the
4391 ground up, to better support unreliable networks and restrictive
4392 sets of entry nodes, and to better resist guard-capture attacks by
4393 hostile local networks. Implements proposal 271; closes
4396 o Major features (next-generation hidden services):
4397 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
4398 prop224 aka "Next Generation Hidden Services". Service and clients
4399 don't use this functionality yet. Closes ticket 19043. Based on
4400 initial code by Alec Heifetz.
4401 - Relays now support the HSDir version 3 protocol, so that they can
4402 can store and serve v3 descriptors. This is part of the next-
4403 generation onion service work detailed in proposal 224. Closes
4406 o Major features (protocol, ed25519 identity keys):
4407 - Relays now use Ed25519 to prove their Ed25519 identities and to
4408 one another, and to clients. This algorithm is faster and more
4409 secure than the RSA-based handshake we've been doing until now.
4410 Implements the second big part of proposal 220; Closes
4412 - Clients now support including Ed25519 identity keys in the EXTEND2
4413 cells they generate. By default, this is controlled by a consensus
4414 parameter, currently disabled. You can turn this feature on for
4415 testing by setting ExtendByEd25519ID in your configuration. This
4416 might make your traffic appear different than the traffic
4417 generated by other users, however. Implements part of ticket
4418 15056; part of proposal 220.
4419 - Relays now understand requests to extend to other relays by their
4420 Ed25519 identity keys. When an Ed25519 identity key is included in
4421 an EXTEND2 cell, the relay will only extend the circuit if the
4422 other relay can prove ownership of that identity. Implements part
4423 of ticket 15056; part of proposal 220.
4425 o Major bugfixes (scheduler):
4426 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
4427 caused the channel scheduler to behave more or less randomly,
4428 rather than preferring channels with higher-priority circuits.
4429 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
4431 o Minor features (controller):
4432 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
4433 rather than "unrecognized." Closes ticket 20389; patch from
4436 o Minor features (diagnostic, directory client):
4437 - Warn when we find an unexpected inconsistency in directory
4438 download status objects. Prevents some negative consequences of
4441 o Minor features (directory authority):
4442 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
4443 default) to control whether authorities should try to probe relays
4444 by their Ed25519 link keys. This option will go away in a few
4445 releases--unless we encounter major trouble in our ed25519 link
4446 protocol rollout, in which case it will serve as a safety option.
4448 o Minor features (directory cache):
4449 - Relays and bridges will now refuse to serve the consensus they
4450 have if they know it is too old for a client to use. Closes
4453 o Minor features (ed25519 link handshake):
4454 - Advertise support for the ed25519 link handshake using the
4455 subprotocol-versions mechanism, so that clients can tell which
4456 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
4458 o Minor features (fingerprinting resistance, authentication):
4459 - Extend the length of RSA keys used for TLS link authentication to
4460 2048 bits. (These weren't used for forward secrecy; for forward
4461 secrecy, we used P256.) Closes ticket 13752.
4463 o Minor features (infrastructure):
4464 - Implement smartlist_add_strdup() function. Replaces the use of
4465 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
4467 o Minor bugfixes (client):
4468 - When clients that use bridges start up with a cached consensus on
4469 disk, they were ignoring it and downloading a new one. Now they
4470 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
4472 o Minor bugfixes (configuration):
4473 - Accept non-space whitespace characters after the severity level in
4474 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
4475 - Support "TByte" and "TBytes" units in options given in bytes.
4476 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
4477 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
4479 o Minor bugfixes (consensus weight):
4480 - Add new consensus method that initializes bw weights to 1 instead
4481 of 0. This prevents a zero weight from making it all the way to
4482 the end (happens in small testing networks) and causing an error.
4483 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
4485 o Minor bugfixes (descriptors):
4486 - Correctly recognise downloaded full descriptors as valid, even
4487 when using microdescriptors as circuits. This affects clients with
4488 FetchUselessDescriptors set, and may affect directory authorities.
4489 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
4491 o Minor bugfixes (directory system):
4492 - Download all consensus flavors, descriptors, and authority
4493 certificates when FetchUselessDescriptors is set, regardless of
4494 whether tor is a directory cache or not. Fixes bug 20667; bugfix
4495 on all recent tor versions.
4496 - Bridges and relays now use microdescriptors (like clients do)
4497 rather than old-style router descriptors. Now bridges will blend
4498 in with clients in terms of the circuits they build. Fixes bug
4499 6769; bugfix on 0.2.3.2-alpha.
4501 o Minor bugfixes (ed25519 certificates):
4502 - Correctly interpret ed25519 certificates that would expire some
4503 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
4505 o Minor bugfixes (hidden services):
4506 - Stop ignoring misconfigured hidden services. Instead, refuse to
4507 start tor until the misconfigurations have been corrected. Fixes
4508 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
4511 o Minor bugfixes (memory leak at exit):
4512 - Fix a small harmless memory leak at exit of the previously unused
4513 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
4516 o Minor bugfixes (util):
4517 - When finishing writing a file to disk, if we were about to replace
4518 the file with the temporary file created before and we fail to
4519 replace it, remove the temporary file so it doesn't stay on disk.
4520 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
4522 o Minor bugfixes (Windows):
4523 - Check for getpagesize before using it to mmap files. This fixes
4524 compilation in some MinGW environments. Fixes bug 20530; bugfix on
4525 0.1.2.1-alpha. Reported by "ice".
4527 o Code simplification and refactoring:
4528 - Abolish all global guard context in entrynodes.c; replace with new
4529 guard_selection_t structure as preparation for proposal 271.
4530 Closes ticket 19858.
4531 - Introduce rend_service_is_ephemeral() that tells if given onion
4532 service is ephemeral. Replace unclear NULL-checkings for service
4533 directory with this function. Closes ticket 20526.
4534 - Extract magic numbers in circuituse.c into defined variables.
4535 - Refactor circuit_is_available_for_use to remove unnecessary check.
4536 - Refactor circuit_predict_and_launch_new for readability and
4537 testability. Closes ticket 18873.
4538 - Refactor large if statement in purpose_needs_anonymity to use
4539 switch statement instead. Closes part of ticket 20077.
4540 - Refactor the hashing API to return negative values for errors, as
4541 is done as throughout the codebase. Closes ticket 20717.
4542 - Remove data structures that were used to index or_connection
4543 objects by their RSA identity digests. These structures are fully
4544 redundant with the similar structures used in the
4545 channel abstraction.
4546 - Remove duplicate code in the channel_write_*cell() functions.
4547 Closes ticket 13827; patch from Pingl.
4548 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
4549 use only purpose_needs_anonymity. Closes part of ticket 20077.
4550 - The code to generate and parse EXTEND and EXTEND2 cells has been
4551 replaced with code automatically generated by the
4555 - Include the "TBits" unit in Tor's man page. Fixes part of bug
4556 20622; bugfix on tor-0.2.5.1-alpha.
4557 - Change '1' to 'weight_scale' in consensus bw weights calculation
4558 comments, as that is reality. Closes ticket 20273. Patch
4560 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
4561 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
4562 on tor-0.2.5.6-alpha.
4563 - Stop the man page from incorrectly stating that HiddenServiceDir
4564 must already exist. Fixes 20486.
4565 - Clarify that when ClientRejectInternalAddresses is enabled (which
4566 is the default), multicast DNS hostnames for machines on the local
4567 network (of the form *.local) are also rejected. Closes
4571 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
4572 limit for relays running on a single IP applies to authority IP
4573 addresses as well as to non-authority IP addresses. Closes
4575 - The UseDirectoryGuards torrc option no longer exists: all users
4576 that use entry guards will also use directory guards. Related to
4577 proposal 271; implements part of ticket 20831.
4580 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
4581 from "overcaffeinated".
4582 - Perform the coding style checks when running the tests and fail
4583 when coding style violations are found. Closes ticket 5500.
4584 - Add tests for networkstatus_compute_bw_weights_v10.
4585 - Add unit tests circuit_predict_and_launch_new.
4586 - Extract dummy_origin_circuit_new so it can be used by other
4590 Changes in version 0.2.8.12 - 2016-12-19
4591 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
4592 below) where Tor clients could crash when attempting to visit a
4593 hostile hidden service. Clients are recommended to upgrade as packages
4594 become available for their systems.
4596 It also includes an updated list of fallback directories, backported
4599 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
4600 backported to 0.2.8 in the future.
4602 o Major bugfixes (parsing, security, backported from 0.2.9.8):
4603 - Fix a bug in parsing that could cause clients to read a single
4604 byte past the end of an allocated region. This bug could be used
4605 to cause hardened clients (built with --enable-expensive-hardening)
4606 to crash if they tried to visit a hostile hidden service. Non-
4607 hardened clients are only affected depending on the details of
4608 their platform's memory allocator. Fixes bug 21018; bugfix on
4609 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4610 2016-12-002 and as CVE-2016-1254.
4612 o Minor features (fallback directory list, backported from 0.2.9.8):
4613 - Replace the 81 remaining fallbacks of the 100 originally
4614 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4615 fallbacks (123 new, 54 existing, 27 removed) generated in December
4616 2016. Resolves ticket 20170.
4618 o Minor features (geoip, backported from 0.2.9.7-rc):
4619 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
4623 Changes in version 0.2.9.8 - 2016-12-19
4624 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
4626 The Tor 0.2.9 series makes mandatory a number of security features
4627 that were formerly optional. It includes support for a new shared-
4628 randomness protocol that will form the basis for next generation
4629 hidden services, includes a single-hop hidden service mode for
4630 optimizing .onion services that don't actually want to be hidden,
4631 tries harder not to overload the directory authorities with excessive
4632 downloads, and supports a better protocol versioning scheme for
4633 improved compatibility with other implementations of the Tor protocol.
4635 And of course, there are numerous other bugfixes and improvements.
4637 This release also includes a fix for a medium-severity issue (bug
4638 21018 below) where Tor clients could crash when attempting to visit a
4639 hostile hidden service. Clients are recommended to upgrade as packages
4640 become available for their systems.
4642 Below are the changes since 0.2.9.7-rc. For a list of all changes
4643 since 0.2.8, see the ReleaseNotes file.
4645 o Major bugfixes (parsing, security):
4646 - Fix a bug in parsing that could cause clients to read a single
4647 byte past the end of an allocated region. This bug could be used
4648 to cause hardened clients (built with --enable-expensive-hardening)
4649 to crash if they tried to visit a hostile hidden service. Non-
4650 hardened clients are only affected depending on the details of
4651 their platform's memory allocator. Fixes bug 21018; bugfix on
4652 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4653 2016-12-002 and as CVE-2016-1254.
4655 o Minor features (fallback directory list):
4656 - Replace the 81 remaining fallbacks of the 100 originally
4657 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4658 fallbacks (123 new, 54 existing, 27 removed) generated in December
4659 2016. Resolves ticket 20170.
4662 Changes in version 0.2.9.7-rc - 2016-12-12
4663 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
4664 including a few that had prevented tests from passing on
4667 o Minor features (geoip):
4668 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
4671 o Minor bugfix (build):
4672 - The current Git revision when building from a local repository is
4673 now detected correctly when using git worktrees. Fixes bug 20492;
4674 bugfix on 0.2.3.9-alpha.
4676 o Minor bugfixes (directory authority):
4677 - When computing old Tor protocol line version in protover, we were
4678 looking at 0.2.7.5 twice instead of a specific case for
4679 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
4681 o Minor bugfixes (download scheduling):
4682 - Resolve a "bug" warning when considering a download schedule whose
4683 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
4685 o Minor bugfixes (logging):
4686 - Downgrade a harmless log message about the
4687 pending_entry_connections list from "warn" to "info". Mitigates
4690 o Minor bugfixes (memory leak):
4691 - Fix a small memory leak when receiving AF_UNIX connections on a
4692 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
4693 - When moving a signed descriptor object from a source to an
4694 existing destination, free the allocated memory inside that
4695 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
4697 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
4698 - Fix a memory leak and use-after-free error when removing entries
4699 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
4700 0.2.5.5-alpha. Patch from "cypherpunks".
4702 o Minor bugfixes (portability):
4703 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
4704 Fixes bug 20935; bugfix on 0.2.9.6-rc.
4706 o Minor bugfixes (unit tests):
4707 - Stop expecting NetBSD unit tests to report success for ipfw. Part
4708 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
4709 - Fix tolerances in unit tests for monotonic time comparisons
4710 between nanoseconds and microseconds. Previously, we accepted a 10
4711 us difference only, which is not realistic on every platform's
4712 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
4713 - Remove a double-free in the single onion service unit test. Stop
4714 ignoring a return value. Make future changes less error-prone.
4715 Fixes bug 20864; bugfix on 0.2.9.6-rc.
4718 Changes in version 0.2.8.11 - 2016-12-08
4719 Tor 0.2.8.11 backports fixes for additional portability issues that
4720 could prevent Tor from building correctly on OSX Sierra, or with
4721 OpenSSL 1.1. Affected users should upgrade; others can safely stay
4724 o Minor bugfixes (portability):
4725 - Avoid compilation errors when building on OSX Sierra. Sierra began
4726 to support the getentropy() and clock_gettime() APIs, but created
4727 a few problems in doing so. Tor 0.2.9 has a more thorough set of
4728 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
4729 monotonic time interfaces. Fixes bug 20865. Bugfix
4732 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4733 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
4734 architectures. Closes ticket 20588.
4737 Changes in version 0.2.8.10 - 2016-12-02
4738 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
4739 unusable after they left standby mode. It also backports fixes for
4740 a few portability issues and a small but problematic memory leak.
4742 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
4743 - When Tor leaves standby because of a new application request, open
4744 circuits as needed to serve that request. Previously, we would
4745 potentially wait a very long time. Fixes part of bug 19969; bugfix
4748 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
4749 - Clients now respond to new application stream requests immediately
4750 when they arrive, rather than waiting up to one second before
4751 starting to handle them. Fixes part of bug 19969; bugfix
4754 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
4755 - Work around a bug in the OSX 10.12 SDK that would prevent us from
4756 successfully targeting earlier versions of OSX. Resolves
4759 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4760 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
4761 20551; bugfix on 0.2.1.1-alpha.
4763 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
4764 - Work around a memory leak in OpenSSL 1.1 when encoding public
4765 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
4767 o Minor features (geoip):
4768 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
4771 Changes in version 0.2.9.6-rc - 2016-12-02
4772 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
4773 version. We hope that it will be ready to become stable soon, and we
4774 encourage everyone to test this release. If no showstopper bugs are
4775 found here, the next 0.2.9 release will be stable.
4777 o Major bugfixes (relay, resolver, logging):
4778 - For relays that don't know their own address, avoid attempting a
4779 local hostname resolve for each descriptor we download. This
4780 will cut down on the number of "Success: chose address 'x.x.x.x'"
4781 log lines, and also avoid confusing clock jumps if the resolver
4782 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
4784 o Minor bugfixes (client, fascistfirewall):
4785 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
4786 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
4788 o Minor bugfixes (hidden services):
4789 - Stop ignoring the anonymity status of saved keys for hidden
4790 services and single onion services when first starting tor.
4791 Instead, refuse to start tor if any hidden service key has been
4792 used in a different hidden service anonymity mode. Fixes bug
4793 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
4795 o Minor bugfixes (portability):
4796 - Work around a bug in the OSX 10.12 SDK that would prevent us from
4797 successfully targeting earlier versions of OSX. Resolves
4799 - Run correctly when built on Windows build environments that
4800 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
4802 o Minor bugfixes (single onion services, Tor2web):
4803 - Stop complaining about long-term one-hop circuits deliberately
4804 created by single onion services and Tor2web. These log messages
4805 are intended to diagnose issue 8387, which relates to circuits
4806 hanging around forever for no reason. Fixes bug 20613; bugfix on
4807 0.2.9.1-alpha. Reported by "pastly".
4809 o Minor bugfixes (unit tests):
4810 - Stop spurious failures in the local interface address discovery
4811 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
4815 - Correct the minimum bandwidth value in torrc.sample, and queue a
4816 corresponding change for torrc.minimal. Closes ticket 20085.
4819 Changes in version 0.2.9.5-alpha - 2016-11-08
4820 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
4821 version. We believe one or two probably remain, and we encourage
4822 everyone to test this release.
4824 o Major bugfixes (client performance):
4825 - Clients now respond to new application stream requests immediately
4826 when they arrive, rather than waiting up to one second before
4827 starting to handle them. Fixes part of bug 19969; bugfix
4830 o Major bugfixes (client reliability):
4831 - When Tor leaves standby because of a new application request, open
4832 circuits as needed to serve that request. Previously, we would
4833 potentially wait a very long time. Fixes part of bug 19969; bugfix
4836 o Major bugfixes (download scheduling):
4837 - When using an exponential backoff schedule, do not give up on
4838 downloading just because we have failed a bunch of times. Since
4839 each delay is longer than the last, retrying indefinitely won't
4840 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
4841 - If a consensus expires while we are waiting for certificates to
4842 download, stop waiting for certificates.
4843 - If we stop waiting for certificates less than a minute after we
4844 started downloading them, do not consider the certificate download
4845 failure a separate failure. Fixes bug 20533; bugfix
4847 - Remove the maximum delay on exponential-backoff scheduling. Since
4848 we now allow an infinite number of failures (see ticket 20536), we
4849 must now allow the time to grow longer on each failure. Fixes part
4850 of bug 20534; bugfix on 0.2.9.1-alpha.
4851 - Make our initial download delays closer to those from 0.2.8. Fixes
4852 another part of bug 20534; bugfix on 0.2.9.1-alpha.
4853 - When determining when to download a directory object, handle times
4854 after 2038 if the operating system supports them. (Someday this
4855 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
4856 - When using exponential backoff in test networks, use a lower
4857 exponent, so the delays do not vary as much. This helps test
4858 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
4860 o Minor features (geoip):
4861 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
4864 o Minor bugfixes (client directory scheduling):
4865 - Treat "relay too busy to answer request" as a failed request and a
4866 reason to back off on our retry frequency. This is safe now that
4867 exponential backoffs retry indefinitely, and avoids a bug where we
4868 would reset our download schedule erroneously. Fixes bug 20593;
4869 bugfix on 0.2.9.1-alpha.
4871 o Minor bugfixes (client, logging):
4872 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
4873 assume all nodes support EXTEND2. Use ntor whenever a key is
4874 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
4875 - On DNSPort, stop logging a BUG warning on a failed hostname
4876 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
4878 o Minor bugfixes (hidden services):
4879 - When configuring hidden services, check every hidden service
4880 directory's permissions. Previously, we only checked the last
4881 hidden service. Fixes bug 20529; bugfix the work to fix 13942
4884 o Minor bugfixes (portability):
4885 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
4886 architectures. Closes ticket 20588.
4887 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
4888 removed the ECDH ciphers which caused the tests to fail on
4889 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
4890 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
4891 20551; bugfix on 0.2.1.1-alpha.
4893 o Minor bugfixes (relay bootstrap):
4894 - Ensure relays don't make multiple connections during bootstrap.
4895 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
4897 o Minor bugfixes (relay):
4898 - Work around a memory leak in OpenSSL 1.1 when encoding public
4899 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
4900 - Avoid a small memory leak when informing worker threads about
4901 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
4902 - Do not try to parallelize workers more than 16x without the user
4903 explicitly configuring us to do so, even if we do detect more than
4904 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4906 o Minor bugfixes (single onion services):
4907 - Start correctly when creating a single onion service in a
4908 directory that did not previously exist. Fixes bug 20484; bugfix
4911 o Minor bugfixes (testing):
4912 - Avoid a unit test failure on systems with over 16 detectable CPU
4913 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4916 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
4917 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
4918 - Module-level documentation for several more modules. Closes
4919 tickets 19287 and 19290.
4922 Changes in version 0.2.8.9 - 2016-10-17
4923 Tor 0.2.8.9 backports a fix for a security hole in previous versions
4924 of Tor that would allow a remote attacker to crash a Tor client,
4925 hidden service, relay, or authority. All Tor users should upgrade to
4926 this version, or to 0.2.9.4-alpha. Patches will be released for older
4929 o Major features (security fixes, also in 0.2.9.4-alpha):
4930 - Prevent a class of security bugs caused by treating the contents
4931 of a buffer chunk as if they were a NUL-terminated string. At
4932 least one such bug seems to be present in all currently used
4933 versions of Tor, and would allow an attacker to remotely crash
4934 most Tor instances, especially those compiled with extra compiler
4935 hardening. With this defense in place, such bugs can't crash Tor,
4936 though we should still fix them as they occur. Closes ticket
4937 20384 (TROVE-2016-10-001).
4939 o Minor features (geoip):
4940 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
4944 Changes in version 0.2.9.4-alpha - 2016-10-17
4945 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
4946 that would allow a remote attacker to crash a Tor client, hidden
4947 service, relay, or authority. All Tor users should upgrade to this
4948 version, or to 0.2.8.9. Patches will be released for older versions
4951 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
4952 previous versions of Tor, including the implementation of a feature to
4953 future- proof the Tor ecosystem against protocol changes, some bug
4954 fixes necessary for Tor Browser to use unix domain sockets correctly,
4955 and several portability improvements. We anticipate that this will be
4956 the last alpha in the Tor 0.2.9 series, and that the next release will
4957 be a release candidate.
4959 o Major features (security fixes):
4960 - Prevent a class of security bugs caused by treating the contents
4961 of a buffer chunk as if they were a NUL-terminated string. At
4962 least one such bug seems to be present in all currently used
4963 versions of Tor, and would allow an attacker to remotely crash
4964 most Tor instances, especially those compiled with extra compiler
4965 hardening. With this defense in place, such bugs can't crash Tor,
4966 though we should still fix them as they occur. Closes ticket
4967 20384 (TROVE-2016-10-001).
4969 o Major features (subprotocol versions):
4970 - Tor directory authorities now vote on a set of recommended
4971 subprotocol versions, and on a set of required subprotocol
4972 versions. Clients and relays that lack support for a _required_
4973 subprotocol version will not start; those that lack support for a
4974 _recommended_ subprotocol version will warn the user to upgrade.
4975 Closes ticket 19958; implements part of proposal 264.
4976 - Tor now uses "subprotocol versions" to indicate compatibility.
4977 Previously, versions of Tor looked at the declared Tor version of
4978 a relay to tell whether they could use a given feature. Now, they
4979 should be able to rely on its declared subprotocol versions. This
4980 change allows compatible implementations of the Tor protocol(s) to
4981 exist without pretending to be 100% bug-compatible with particular
4982 releases of Tor itself. Closes ticket 19958; implements part of
4985 o Minor feature (fallback directories):
4986 - Remove broken fallbacks from the hard-coded fallback directory
4987 list. Closes ticket 20190; patch by teor.
4989 o Minor features (client, directory):
4990 - Since authorities now omit all routers that lack the Running and
4991 Valid flags, we assume that any relay listed in the consensus must
4992 have those flags. Closes ticket 20001; implements part of
4995 o Minor features (compilation, portability):
4996 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
4999 o Minor features (development tools, etags):
5000 - Teach the "make tags" Makefile target how to correctly find
5001 "MOCK_IMPL" function definitions. Patch from nherring; closes
5004 o Minor features (geoip):
5005 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
5008 o Minor features (unix domain sockets):
5009 - When configuring a unix domain socket for a SocksPort,
5010 ControlPort, or Hidden service, you can now wrap the address in
5011 quotes, using C-style escapes inside the quotes. This allows unix
5012 domain socket paths to contain spaces.
5014 o Minor features (virtual addresses):
5015 - Increase the maximum number of bits for the IPv6 virtual network
5016 prefix from 16 to 104. In this way, the condition for address
5017 allocation is less restrictive. Closes ticket 20151; feature
5020 o Minor bugfixes (address discovery):
5021 - Stop reordering IP addresses returned by the OS. This makes it
5022 more likely that Tor will guess the same relay IP address every
5023 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
5024 Reported by René Mayrhofer, patch by "cypherpunks".
5026 o Minor bugfixes (client, unix domain sockets):
5027 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
5028 the client address is meaningless. Fixes bug 20261; bugfix
5031 o Minor bugfixes (compilation, OpenBSD):
5032 - Detect Libevent2 functions correctly on systems that provide
5033 libevent2, but where libevent1 is linked with -levent. Fixes bug
5034 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
5036 o Minor bugfixes (configuration):
5037 - When parsing quoted configuration values from the torrc file,
5038 handle windows line endings correctly. Fixes bug 19167; bugfix on
5039 0.2.0.16-alpha. Patch from "Pingl".
5041 o Minor bugfixes (getpass):
5042 - Defensively fix a non-triggerable heap corruption at do_getpass()
5043 to protect ourselves from mistakes in the future. Fixes bug
5044 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
5047 o Minor bugfixes (hidden service):
5048 - Allow hidden services to run on IPv6 addresses even when the
5049 IPv6Exit option is not set. Fixes bug 18357; bugfix
5053 - Add module-level internal documentation for 36 C files that
5054 previously didn't have a high-level overview. Closes ticket #20385.
5056 o Required libraries:
5057 - When building with OpenSSL, Tor now requires version 1.0.1 or
5058 later. OpenSSL 1.0.0 and earlier are no longer supported by the
5059 OpenSSL team, and should not be used. Closes ticket 20303.
5062 Changes in version 0.2.9.3-alpha - 2016-09-23
5063 Tor 0.2.9.3-alpha adds improved support for entities that want to make
5064 high-performance services available through the Tor .onion mechanism
5065 without themselves receiving anonymity as they host those services. It
5066 also tries harder to ensure that all steps on a circuit are using the
5067 strongest crypto possible, strengthens some TLS properties, and
5068 resolves several bugs -- including a pair of crash bugs from the 0.2.8
5069 series. Anybody running an earlier version of 0.2.9.x should upgrade.
5071 o Major bugfixes (crash, also in 0.2.8.8):
5072 - Fix a complicated crash bug that could affect Tor clients
5073 configured to use bridges when replacing a networkstatus consensus
5074 in which one of their bridges was mentioned. OpenBSD users saw
5075 more crashes here, but all platforms were potentially affected.
5076 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
5078 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
5079 - Fix a timing-dependent assertion failure that could occur when we
5080 tried to flush from a circuit after having freed its cells because
5081 of an out-of-memory condition. Fixes bug 20203; bugfix on
5082 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
5085 o Major features (circuit building, security):
5086 - Authorities, relays and clients now require ntor keys in all
5087 descriptors, for all hops (except for rare hidden service protocol
5088 cases), for all circuits, and for all other roles. Part of
5090 - Tor authorities, relays, and clients only use ntor, except for
5091 rare cases in the hidden service protocol. Part of ticket 19163.
5093 o Major features (single-hop "hidden" services):
5094 - Add experimental HiddenServiceSingleHopMode and
5095 HiddenServiceNonAnonymousMode options. When both are set to 1,
5096 every hidden service on a Tor instance becomes a non-anonymous
5097 Single Onion Service. Single Onions make one-hop (direct)
5098 connections to their introduction and renzedvous points. One-hop
5099 circuits make Single Onion servers easily locatable, but clients
5100 remain location-anonymous. This is compatible with the existing
5101 hidden service implementation, and works on the current tor
5102 network without any changes to older relays or clients. Implements
5103 proposal 260, completes ticket 17178. Patch by teor and asn.
5105 o Major features (resource management):
5106 - Tor can now notice it is about to run out of sockets, and
5107 preemptively close connections of lower priority. (This feature is
5108 off by default for now, since the current prioritizing method is
5109 yet not mature enough. You can enable it by setting
5110 "DisableOOSCheck 0", but watch out: it might close some sockets
5111 you would rather have it keep.) Closes ticket 18640.
5113 o Major bugfixes (circuit building):
5114 - Hidden service client-to-intro-point and service-to-rendezvous-
5115 point circuits use the TAP key supplied by the protocol, to avoid
5116 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
5118 o Major bugfixes (compilation, OpenBSD):
5119 - Fix a Libevent-detection bug in our autoconf script that would
5120 prevent Tor from linking successfully on OpenBSD. Patch from
5121 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
5123 o Major bugfixes (hidden services):
5124 - Clients now require hidden services to include the TAP keys for
5125 their intro points in the hidden service descriptor. This prevents
5126 an inadvertent upgrade to ntor, which a malicious hidden service
5127 could use to distinguish clients by consensus version. Fixes bug
5128 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
5130 o Minor features (security, TLS):
5131 - Servers no longer support clients that without AES ciphersuites.
5132 (3DES is no longer considered an acceptable cipher.) We believe
5133 that no such Tor clients currently exist, since Tor has required
5134 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
5136 o Minor feature (fallback directories):
5137 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
5138 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
5139 2016. Closes ticket 20190; patch by teor.
5141 o Minor features (geoip, also in 0.2.8.8):
5142 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
5145 o Minor feature (port flags):
5146 - Add new flags to the *Port options to finer control over which
5147 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
5148 and the synthetic flag OnionTrafficOnly, which is equivalent to
5149 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
5150 18693; patch by "teor".
5152 o Minor features (directory authority):
5153 - After voting, if the authorities decide that a relay is not
5154 "Valid", they no longer include it in the consensus at all. Closes
5155 ticket 20002; implements part of proposal 272.
5157 o Minor features (testing):
5158 - Disable memory protections on OpenBSD when performing our unit
5159 tests for memwipe(). The test deliberately invokes undefined
5160 behavior, and the OpenBSD protections interfere with this. Patch
5161 from "rubiate". Closes ticket 20066.
5163 o Minor features (testing, ipv6):
5164 - Add the single-onion and single-onion-ipv6 chutney targets to
5165 "make test-network-all". This requires a recent chutney version
5166 with the single onion network flavours (git c72a652 or later).
5167 Closes ticket 20072; patch by teor.
5168 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
5169 tests. Remove bridges+hs, as it's somewhat redundant. This
5170 requires a recent chutney version that supports IPv6 clients,
5171 relays, and authorities. Closes ticket 20069; patch by teor.
5173 o Minor features (Tor2web):
5174 - Make Tor2web clients respect ReachableAddresses. This feature was
5175 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
5176 0.2.8.7. Implements feature 20034. Patch by teor.
5178 o Minor features (unit tests):
5179 - We've done significant work to make the unit tests run faster.
5180 - Our link-handshake unit tests now check that when invalid
5181 handshakes fail, they fail with the error messages we expected.
5182 - Our unit testing code that captures log messages no longer
5183 prevents them from being written out if the user asked for them
5184 (by passing --debug or --info or or --notice --warn to the "test"
5185 binary). This change prevents us from missing unexpected log
5186 messages simply because we were looking for others. Related to
5188 - The unit tests now log all warning messages with the "BUG" flag.
5189 Previously, they only logged errors by default. This change will
5190 help us make our testing code more correct, and make sure that we
5191 only hit this code when we mean to. In the meantime, however,
5192 there will be more warnings in the unit test logs than before.
5193 This is preparatory work for ticket 19999.
5194 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
5195 assertion as a test failure.
5197 o Minor bug fixes (circuits):
5198 - Use the CircuitBuildTimeout option whenever
5199 LearnCircuitBuildTimeout is disabled. Previously, we would respect
5200 the option when a user disabled it, but not when it was disabled
5201 because some other option was set. Fixes bug 20073; bugfix on
5202 0.2.4.12-alpha. Patch by teor.
5204 o Minor bugfixes (allocation):
5205 - Change how we allocate memory for large chunks on buffers, to
5206 avoid a (currently impossible) integer overflow, and to waste less
5207 space when allocating unusually large chunks. Fixes bug 20081;
5208 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
5209 - Always include orconfig.h before including any other C headers.
5210 Sometimes, it includes macros that affect the behavior of the
5211 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
5212 first version to use AC_USE_SYSTEM_EXTENSIONS).
5213 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
5214 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
5215 Patch from Gisle Vanem.
5216 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
5217 They apparently require a set of annotations that we aren't
5218 currently using, and they create false positives in our pthreads
5219 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
5221 o Minor bugfixes (directory authority):
5222 - Die with a more useful error when the operator forgets to place
5223 the authority_signing_key file into the keys directory. This
5224 avoids an uninformative assert & traceback about having an invalid
5225 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
5226 - When allowing private addresses, mark Exits that only exit to
5227 private locations as such. Fixes bug 20064; bugfix
5230 o Minor bugfixes (documentation):
5231 - Document the default PathsNeededToBuildCircuits value that's used
5232 by clients when the directory authorities don't set
5233 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
5234 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
5235 - Fix manual for the User option: it takes a username, not a UID.
5236 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
5239 o Minor bugfixes (hidden services):
5240 - Stop logging intro point details to the client log on certain
5241 error conditions. Fixed as part of bug 20012; bugfix on
5242 0.2.4.8-alpha. Patch by teor.
5244 o Minor bugfixes (IPv6, testing):
5245 - Check for IPv6 correctly on Linux when running test networks.
5246 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
5248 o Minor bugfixes (Linux seccomp2 sandbox):
5249 - Add permission to run the sched_yield() and sigaltstack() system
5250 calls, in order to support versions of Tor compiled with asan or
5251 ubsan code that use these calls. Now "sandbox 1" and
5252 "--enable-expensive-hardening" should be compatible on more
5253 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
5255 o Minor bugfixes (logging):
5256 - When logging a message from the BUG() macro, be explicit about
5257 what we were asserting. Previously we were confusing what we were
5258 asserting with what the bug was. Fixes bug 20093; bugfix
5260 - When we are unable to remove the bw_accounting file, do not warn
5261 if the reason we couldn't remove it was that it didn't exist.
5262 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
5264 o Minor bugfixes (option parsing):
5265 - Count unix sockets when counting client listeners (SOCKS, Trans,
5266 NATD, and DNS). This has no user-visible behaviour changes: these
5267 options are set once, and never read. Required for correct
5268 behaviour in ticket 17178. Fixes bug 19677; bugfix on
5269 0.2.6.3-alpha. Patch by teor.
5271 o Minor bugfixes (options):
5272 - Check the consistency of UseEntryGuards and EntryNodes more
5273 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
5275 - Stop changing the configured value of UseEntryGuards on
5276 authorities and Tor2web clients. Fixes bug 20074; bugfix on
5277 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
5280 o Minor bugfixes (Tor2web):
5281 - Prevent Tor2web clients running hidden services, these services
5282 are not anonymous due to the one-hop client paths. Fixes bug
5283 19678. Patch by teor.
5285 o Minor bugfixes (unit tests):
5286 - Fix a shared-random unit test that was failing on big endian
5287 architectures due to internal representation of a integer copied
5288 to a buffer. The test is changed to take a full 32 bytes of data
5289 and use the output of a python script that make the COMMIT and
5290 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
5292 - The tor_tls_server_info_callback unit test no longer crashes when
5293 debug-level logging is turned on. Fixes bug 20041; bugfix
5297 Changes in version 0.2.8.8 - 2016-09-23
5298 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
5299 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
5300 who select public relays as their bridges.
5302 o Major bugfixes (crash):
5303 - Fix a complicated crash bug that could affect Tor clients
5304 configured to use bridges when replacing a networkstatus consensus
5305 in which one of their bridges was mentioned. OpenBSD users saw
5306 more crashes here, but all platforms were potentially affected.
5307 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
5309 o Major bugfixes (relay, OOM handler):
5310 - Fix a timing-dependent assertion failure that could occur when we
5311 tried to flush from a circuit after having freed its cells because
5312 of an out-of-memory condition. Fixes bug 20203; bugfix on
5313 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
5316 o Minor feature (fallback directories):
5317 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
5318 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
5319 2016. Closes ticket 20190; patch by teor.
5321 o Minor features (geoip):
5322 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
5326 Changes in version 0.2.9.2-alpha - 2016-08-24
5327 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
5328 several new features and bugfixes. It also includes an important
5329 authority update and an important bugfix from 0.2.8.7. Everyone who
5330 sets the ReachableAddresses option, and all bridges, are strongly
5331 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
5333 o Directory authority changes (also in 0.2.8.7):
5334 - The "Tonga" bridge authority has been retired; the new bridge
5335 authority is "Bifroest". Closes tickets 19728 and 19690.
5337 o Major bugfixes (client, security, also in 0.2.8.7):
5338 - Only use the ReachableAddresses option to restrict the first hop
5339 in a path. In earlier versions of 0.2.8.x, it would apply to
5340 every hop in the path, with a possible degradation in anonymity
5341 for anyone using an uncommon ReachableAddress setting. Fixes bug
5342 19973; bugfix on 0.2.8.2-alpha.
5344 o Major features (user interface):
5345 - Tor now supports the ability to declare options deprecated, so
5346 that we can recommend that people stop using them. Previously,
5347 this was done in an ad-hoc way. Closes ticket 19820.
5349 o Major bugfixes (directory downloads):
5350 - Avoid resetting download status for consensuses hourly, since we
5351 already have another, smarter retry mechanism. Fixes bug 8625;
5352 bugfix on 0.2.0.9-alpha.
5354 o Minor features (config):
5355 - Warn users when descriptor and port addresses are inconsistent.
5356 Mitigates bug 13953; patch by teor.
5358 o Minor features (geoip):
5359 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
5362 o Minor features (user interface):
5363 - There is a new --list-deprecated-options command-line option to
5364 list all of the deprecated options. Implemented as part of
5367 o Minor bugfixes (code style):
5368 - Fix an integer signedness conversion issue in the case conversion
5369 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
5371 o Minor bugfixes (compilation):
5372 - Build correctly on versions of libevent2 without support for
5373 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
5375 - Fix a compilation warning on GCC versions before 4.6. Our
5376 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
5377 when it is also required as an argument to the compiler pragma.
5378 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
5380 o Minor bugfixes (compilation, also in 0.2.8.7):
5381 - Remove an inappropriate "inline" in tortls.c that was causing
5382 warnings on older versions of GCC. Fixes bug 19903; bugfix
5385 o Minor bugfixes (fallback directories, also in 0.2.8.7):
5386 - Avoid logging a NULL string pointer when loading fallback
5387 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
5388 and 0.2.8.1-alpha. Report and patch by "rubiate".
5390 o Minor bugfixes (logging):
5391 - Log a more accurate message when we fail to dump a microdescriptor.
5392 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
5394 o Minor bugfixes (memory leak):
5395 - Fix a series of slow memory leaks related to parsing torrc files
5396 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
5398 o Deprecated features:
5399 - A number of DNS-cache-related sub-options for client ports are now
5400 deprecated for security reasons, and may be removed in a future
5401 version of Tor. (We believe that client-side DNS caching is a bad
5402 idea for anonymity, and you should not turn it on.) The options
5403 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
5404 UseIPv4Cache, and UseIPv6Cache.
5405 - A number of options are deprecated for security reasons, and may
5406 be removed in a future version of Tor. The options are:
5407 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
5408 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
5409 CloseHSClientCircuitsImmediatelyOnTimeout,
5410 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
5411 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
5412 UseNTorHandshake, and WarnUnsafeSocks.
5413 - The *ListenAddress options are now deprecated as unnecessary: the
5414 corresponding *Port options should be used instead. These options
5415 may someday be removed. The affected options are:
5416 ControlListenAddress, DNSListenAddress, DirListenAddress,
5417 NATDListenAddress, ORListenAddress, SocksListenAddress,
5418 and TransListenAddress.
5421 - Correct the IPv6 syntax in our documentation for the
5422 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
5425 - We no longer include the (dead, deprecated) bufferevent code in
5426 Tor. Closes ticket 19450. Based on a patch from U+039b.
5429 Changes in version 0.2.8.7 - 2016-08-24
5430 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
5431 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
5432 who sets the ReachableAddresses option, and all bridges, are strongly
5433 encouraged to upgrade.
5435 o Directory authority changes:
5436 - The "Tonga" bridge authority has been retired; the new bridge
5437 authority is "Bifroest". Closes tickets 19728 and 19690.
5439 o Major bugfixes (client, security):
5440 - Only use the ReachableAddresses option to restrict the first hop
5441 in a path. In earlier versions of 0.2.8.x, it would apply to
5442 every hop in the path, with a possible degradation in anonymity
5443 for anyone using an uncommon ReachableAddress setting. Fixes bug
5444 19973; bugfix on 0.2.8.2-alpha.
5446 o Minor features (geoip):
5447 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
5450 o Minor bugfixes (compilation):
5451 - Remove an inappropriate "inline" in tortls.c that was causing
5452 warnings on older versions of GCC. Fixes bug 19903; bugfix
5455 o Minor bugfixes (fallback directories):
5456 - Avoid logging a NULL string pointer when loading fallback
5457 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
5458 and 0.2.8.1-alpha. Report and patch by "rubiate".
5461 Changes in version 0.2.9.1-alpha - 2016-08-08
5462 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
5463 series. It improves our support for hardened builds and compiler
5464 warnings, deploys some critical infrastructure for improvements to
5465 hidden services, includes a new timing backend that we hope to use for
5466 better support for traffic padding, makes it easier for programmers to
5467 log unexpected events, and contains other small improvements to
5468 security, correctness, and performance.
5470 Below are the changes since 0.2.8.6.
5472 o New system requirements:
5473 - Tor now requires Libevent version 2.0.10-stable or later. Older
5474 versions of Libevent have less efficient backends for several
5475 platforms, and lack the DNS code that we use for our server-side
5476 DNS support. This implements ticket 19554.
5477 - Tor now requires zlib version 1.2 or later, for security,
5478 efficiency, and (eventually) gzip support. (Back when we started,
5479 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
5480 released in 2003. We recommend the latest version.)
5482 o Major features (build, hardening):
5483 - Tor now builds with -ftrapv by default on compilers that support
5484 it. This option detects signed integer overflow (which C forbids),
5485 and turns it into a hard-failure. We do not apply this option to
5486 code that needs to run in constant time to avoid side-channels;
5487 instead, we use -fwrapv in that code. Closes ticket 17983.
5488 - When --enable-expensive-hardening is selected, stop applying the
5489 clang/gcc sanitizers to code that needs to run in constant time.
5490 Although we are aware of no introduced side-channels, we are not
5491 able to prove that there are none. Related to ticket 17983.
5493 o Major features (compilation):
5494 - Our big list of extra GCC warnings is now enabled by default when
5495 building with GCC (or with anything like Clang that claims to be
5496 GCC-compatible). To make all warnings into fatal compilation
5497 errors, pass --enable-fatal-warnings to configure. Closes
5499 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
5500 turn on C and POSIX extensions. (Previously, we attempted to do
5501 this on an ad hoc basis.) Closes ticket 19139.
5503 o Major features (directory authorities, hidden services):
5504 - Directory authorities can now perform the shared randomness
5505 protocol specified by proposal 250. Using this protocol, directory
5506 authorities generate a global fresh random value every day. In the
5507 future, this value will be used by hidden services to select
5508 HSDirs. This release implements the directory authority feature;
5509 the hidden service side will be implemented in the future as part
5510 of proposal 224. Resolves ticket 16943; implements proposal 250.
5512 o Major features (downloading, random exponential backoff):
5513 - When we fail to download an object from a directory service, wait
5514 for an (exponentially increasing) randomized amount of time before
5515 retrying, rather than a fixed interval as we did before. This
5516 prevents a group of Tor instances from becoming too synchronized,
5517 or a single Tor instance from becoming too predictable, in its
5518 download schedule. Closes ticket 15942.
5520 o Major bugfixes (exit policies):
5521 - Avoid disclosing exit outbound bind addresses, configured port
5522 bind addresses, and local interface addresses in relay descriptors
5523 by default under ExitPolicyRejectPrivate. Instead, only reject
5524 these (otherwise unlisted) addresses if
5525 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
5526 0.2.7.2-alpha. Patch by teor.
5528 o Major bugfixes (hidden service client):
5529 - Allow Tor clients with appropriate controllers to work with
5530 FetchHidServDescriptors set to 0. Previously, this option also
5531 disabled descriptor cache lookup, thus breaking hidden services
5532 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
5534 o Minor features (build, hardening):
5535 - Detect and work around a libclang_rt problem that would prevent
5536 clang from finding __mulodi4() on some 32-bit platforms, and thus
5537 keep -ftrapv from linking on those systems. Closes ticket 19079.
5538 - When building on a system without runtime support for the runtime
5539 hardening options, try to log a useful warning at configuration
5540 time, rather than an incomprehensible warning at link time. If
5541 expensive hardening was requested, this warning becomes an error.
5542 Closes ticket 18895.
5544 o Minor features (code safety):
5545 - In our integer-parsing functions, ensure that maxiumum value we
5546 give is no smaller than the minimum value. Closes ticket 19063;
5549 o Minor features (controller):
5550 - Implement new GETINFO queries for all downloads that use
5551 download_status_t to schedule retries. This allows controllers to
5552 examine the schedule for pending downloads. Closes ticket 19323.
5553 - Allow controllers to configure basic client authorization on
5554 hidden services when they create them with the ADD_ONION control
5555 command. Implements ticket 15588. Patch by "special".
5556 - Fire a STATUS_SERVER controller event whenever the hibernation
5557 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
5559 o Minor features (directory authority):
5560 - Directory authorities now only give the Guard flag to a relay if
5561 they are also giving it the Stable flag. This change allows us to
5562 simplify path selection for clients. It should have minimal effect
5563 in practice, since >99% of Guards already have the Stable flag.
5564 Implements ticket 18624.
5565 - Directory authorities now write their v3-status-votes file out to
5566 disk earlier in the consensus process, so we have a record of the
5567 votes even if we abort the consensus process. Resolves
5570 o Minor features (hidden service):
5571 - Stop being so strict about the payload length of "rendezvous1"
5572 cells. We used to be locked in to the "TAP" handshake length, and
5573 now we can handle better handshakes like "ntor". Resolves
5576 o Minor features (infrastructure, time):
5577 - Tor now uses the operating system's monotonic timers (where
5578 available) for internal fine-grained timing. Previously we would
5579 look at the system clock, and then attempt to compensate for the
5580 clock running backwards. Closes ticket 18908.
5581 - Tor now includes an improved timer backend, so that we can
5582 efficiently support tens or hundreds of thousands of concurrent
5583 timers, as will be needed for some of our planned anti-traffic-
5584 analysis work. This code is based on William Ahern's "timeout.c"
5585 project, which implements a "tickless hierarchical timing wheel".
5586 Closes ticket 18365.
5588 o Minor features (logging):
5589 - Provide a more useful warning message when configured with an
5590 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
5591 - When dumping unparseable router descriptors, optionally store them
5592 in separate files, named by digest, up to a configurable size
5593 limit. You can change the size limit by setting the
5594 MaxUnparseableDescSizeToLog option, and disable this feature by
5595 setting that option to 0. Closes ticket 18322.
5596 - Add a set of macros to check nonfatal assertions, for internal
5597 use. Migrating more of our checks to these should help us avoid
5598 needless crash bugs. Closes ticket 18613.
5600 o Minor features (performance):
5601 - Changer the "optimistic data" extension from "off by default" to
5602 "on by default". The default was ordinarily overridden by a
5603 consensus option, but when clients were bootstrapping for the
5604 first time, they would not have a consensus to get the option
5605 from. Changing this default When fetching a consensus for the
5606 first time, use optimistic data. This saves a round-trip during
5607 startup. Closes ticket 18815.
5609 o Minor features (relay, usability):
5610 - When the directory authorities refuse a bad relay's descriptor,
5611 encourage the relay operator to contact us. Many relay operators
5612 won't notice this line in their logs, but it's a win if even a few
5613 learn why we don't like what their relay was doing. Resolves
5616 o Minor features (testing):
5617 - Let backtrace tests work correctly under AddressSanitizer. Fixes
5618 part of bug 18934; bugfix on 0.2.5.2-alpha.
5619 - Move the test-network.sh script to chutney, and modify tor's test-
5620 network.sh to call the (newer) chutney version when available.
5621 Resolves ticket 19116. Patch by teor.
5622 - Use the lcov convention for marking lines as unreachable, so that
5623 we don't count them when we're generating test coverage data.
5624 Update our coverage tools to understand this convention. Closes
5627 o Minor bugfixes (bootstrap):
5628 - Remember the directory we fetched the consensus or previous
5629 certificates from, and use it to fetch future authority
5630 certificates. This change improves bootstrapping performance.
5631 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
5633 o Minor bugfixes (build):
5634 - The test-stem and test-network makefile targets now depend only on
5635 the tor binary that they are testing. Previously, they depended on
5636 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
5637 patch from "cypherpunks".
5639 o Minor bugfixes (circuits):
5640 - Make sure extend_info_from_router() is only called on servers.
5641 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
5643 o Minor bugfixes (compilation):
5644 - When building with Clang, use a full set of GCC warnings.
5645 (Previously, we included only a subset, because of the way we
5646 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
5648 o Minor bugfixes (directory authority):
5649 - Authorities now sort the "package" lines in their votes, for ease
5650 of debugging. (They are already sorted in consensus documents.)
5651 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
5652 - When parsing a detached signature, make sure we use the length of
5653 the digest algorithm instead of an hardcoded DIGEST256_LEN in
5654 order to avoid comparing bytes out-of-bounds with a smaller digest
5655 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
5657 o Minor bugfixes (documentation):
5658 - Document the --passphrase-fd option in the tor manpage. Fixes bug
5659 19504; bugfix on 0.2.7.3-rc.
5660 - Fix the description of the --passphrase-fd option in the
5661 tor-gencert manpage. The option is used to pass the number of a
5662 file descriptor to read the passphrase from, not to read the file
5663 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
5665 o Minor bugfixes (ephemeral hidden service):
5666 - When deleting an ephemeral hidden service, close its intro points
5667 even if they are not completely open. Fixes bug 18604; bugfix
5670 o Minor bugfixes (guard selection):
5671 - Use a single entry guard even if the NumEntryGuards consensus
5672 parameter is not provided. Fixes bug 17688; bugfix
5674 - Don't mark guards as unreachable if connection_connect() fails.
5675 That function fails for local reasons, so it shouldn't reveal
5676 anything about the status of the guard. Fixes bug 14334; bugfix
5679 o Minor bugfixes (hidden service client):
5680 - Increase the minimum number of internal circuits we preemptively
5681 build from 2 to 3, so a circuit is available when a client
5682 connects to another onion service. Fixes bug 13239; bugfix
5685 o Minor bugfixes (logging):
5686 - When logging a directory ownership mismatch, log the owning
5687 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
5689 o Minor bugfixes (memory leaks):
5690 - Fix a small, uncommon memory leak that could occur when reading a
5691 truncated ed25519 key file. Fixes bug 18956; bugfix
5694 o Minor bugfixes (testing):
5695 - Allow clients to retry HSDirs much faster in test networks. Fixes
5696 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
5697 - Disable ASAN's detection of segmentation faults while running
5698 test_bt.sh, so that we can make sure that our own backtrace
5699 generation code works. Fixes another aspect of bug 18934; bugfix
5700 on 0.2.5.2-alpha. Patch from "cypherpunks".
5701 - Fix the test-network-all target on out-of-tree builds by using the
5702 correct path to the test driver script. Fixes bug 19421; bugfix
5705 o Minor bugfixes (time):
5706 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
5707 bugfix on all released tor versions.
5708 - When computing the difference between two times in milliseconds,
5709 we now round to the nearest millisecond correctly. Previously, we
5710 could sometimes round in the wrong direction. Fixes bug 19428;
5711 bugfix on 0.2.2.2-alpha.
5713 o Minor bugfixes (user interface):
5714 - Display a more accurate number of suppressed messages in the log
5715 rate-limiter. Previously, there was a potential integer overflow
5716 in the counter. Now, if the number of messages hits a maximum, the
5717 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
5719 - Fix a typo in the passphrase prompt for the ed25519 identity key.
5720 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
5722 o Code simplification and refactoring:
5723 - Remove redundant declarations of the MIN macro. Closes
5725 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
5726 Closes ticket 18462; patch from "icanhasaccount".
5727 - Split the 600-line directory_handle_command_get function into
5728 separate functions for different URL types. Closes ticket 16698.
5731 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
5732 ticket 19153. Patch from "U+039b".
5735 - Remove support for "GET /tor/bytes.txt" DirPort request, and
5736 "GETINFO dir-usage" controller request, which were only available
5737 via a compile-time option in Tor anyway. Feature was added in
5738 0.2.2.1-alpha. Resolves ticket 19035.
5739 - There is no longer a compile-time option to disable support for
5740 TransPort. (If you don't want TransPort; just don't use it.) Patch
5741 from "U+039b". Closes ticket 19449.
5744 - Run more workqueue tests as part of "make check". These had
5745 previously been implemented, but you needed to know special
5746 command-line options to enable them.
5747 - We now have unit tests for our code to reject zlib "compression
5748 bombs". (Fortunately, the code works fine.)
5751 Changes in version 0.2.8.6 - 2016-08-02
5753 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
5755 The Tor 0.2.8 series improves client bootstrapping performance,
5756 completes the authority-side implementation of improved identity
5757 keys for relays, and includes numerous bugfixes and performance
5758 improvements throughout the program. This release continues to
5759 improve the coverage of Tor's test suite. For a full list of
5760 changes since Tor 0.2.7, see the ReleaseNotes file.
5762 Changes since 0.2.8.5-rc:
5764 o Minor features (geoip):
5765 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
5768 o Minor bugfixes (compilation):
5769 - Fix a compilation warning in the unit tests on systems where char
5770 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
5772 o Minor bugfixes (fallback directories):
5773 - Remove 1 fallback that was on the hardcoded list, then opted-out,
5774 leaving 89 of the 100 fallbacks originally introduced in Tor
5775 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
5777 o Minor bugfixes (Linux seccomp2 sandbox):
5778 - Allow more syscalls when running with "Sandbox 1" enabled:
5779 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
5780 some systems, these are required for Tor to start. Fixes bug
5781 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
5782 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
5783 so that get_interface_address6_via_udp_socket_hack() can work.
5784 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
5787 Changes in version 0.2.8.5-rc - 2016-07-07
5788 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
5789 series. If we find no new bugs or regressions here, the first stable
5790 0.2.8 release will be identical to it. It has a few small bugfixes
5791 against previous versions.
5793 o Directory authority changes:
5794 - Urras is no longer a directory authority. Closes ticket 19271.
5796 o Major bugfixes (heartbeat):
5797 - Fix a regression that would crash Tor when the periodic
5798 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
5799 0.2.8.1-alpha. Reported by "kubaku".
5801 o Minor features (build):
5802 - Tor now again builds with the recent OpenSSL 1.1 development
5803 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
5804 - When building manual pages, set the timezone to "UTC", so that the
5805 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
5806 Patch from intrigeri.
5808 o Minor bugfixes (fallback directory selection):
5809 - Avoid errors during fallback selection if there are no eligible
5810 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
5813 o Minor bugfixes (IPv6, microdescriptors):
5814 - Don't check node addresses when we only have a routerstatus. This
5815 allows IPv6-only clients to bootstrap by fetching microdescriptors
5816 from fallback directory mirrors. (The microdescriptor consensus
5817 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
5820 o Minor bugfixes (logging):
5821 - Reduce pointlessly verbose log messages when directory servers
5822 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
5823 0.2.8.1-alpha. Patch by teor.
5824 - When a fallback directory changes its fingerprint from the hard-
5825 coded fingerprint, log a less severe, more explanatory log
5826 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
5828 o Minor bugfixes (Linux seccomp2 sandboxing):
5829 - Allow statistics to be written to disk when "Sandbox 1" is
5830 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
5831 0.2.6.1-alpha respectively.
5833 o Minor bugfixes (user interface):
5834 - Remove a warning message "Service [scrubbed] not found after
5835 descriptor upload". This message appears when one uses HSPOST
5836 control command to upload a service descriptor. Since there is
5837 only a descriptor and no service, showing this message is
5838 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
5840 o Fallback directory list:
5841 - Add a comment to the generated fallback directory list that
5842 explains how to comment out unsuitable fallbacks in a way that's
5843 compatible with the stem fallback parser.
5844 - Update fallback whitelist and blacklist based on relay operator
5845 emails. Blacklist unsuitable (non-working, over-volatile)
5846 fallbacks. Resolves ticket 19071. Patch by teor.
5847 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
5848 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
5849 ticket 19071; patch by teor.
5852 Changes in version 0.2.8.4-rc - 2016-06-15
5853 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
5854 If we find no new bugs or regressions here, the first stable 0.2.8
5855 release will be identical to it. It has a few small bugfixes against
5858 o Major bugfixes (user interface):
5859 - Correctly give a warning in the cases where a relay is specified
5860 by nickname, and one such relay is found, but it is not officially
5861 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
5863 o Minor features (build):
5864 - Tor now builds once again with the recent OpenSSL 1.1 development
5865 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
5867 o Minor features (geoip):
5868 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
5871 o Minor bugfixes (compilation):
5872 - Cause the unit tests to compile correctly on mingw64 versions that
5873 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
5875 o Minor bugfixes (downloading):
5876 - Predict more correctly whether we'll be downloading over HTTP when
5877 we determine the maximum length of a URL. This should avoid a
5878 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
5882 Changes in version 0.2.8.3-alpha - 2016-05-26
5883 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
5884 the course of the 0.2.8 development cycle. It improves the behavior of
5885 directory clients, fixes several crash bugs, fixes a gap in compiler
5886 hardening, and allows the full integration test suite to run on
5889 o Major bugfixes (security, client, DNS proxy):
5890 - Stop a crash that could occur when a client running with DNSPort
5891 received a query with multiple address types, and the first
5892 address type was not supported. Found and fixed by Scott Dial.
5893 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5895 o Major bugfixes (security, compilation):
5896 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
5897 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
5898 cause a compiler warning, thereby making other checks fail, and
5899 needlessly disabling compiler-hardening support. Fixes one case of
5900 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
5902 o Major bugfixes (security, directory authorities):
5903 - Fix a crash and out-of-bounds write during authority voting, when
5904 the list of relays includes duplicate ed25519 identity keys. Fixes
5905 bug 19032; bugfix on 0.2.8.2-alpha.
5907 o Major bugfixes (client, bootstrapping):
5908 - Check if bootstrap consensus downloads are still needed when the
5909 linked connection attaches. This prevents tor making unnecessary
5910 begindir-style connections, which are the only directory
5911 connections tor clients make since the fix for 18483 was merged.
5912 - Fix some edge cases where consensus download connections may not
5913 have been closed, even though they were not needed. Related to fix
5915 - Make relays retry consensus downloads the correct number of times,
5916 rather than the more aggressive client retry count. Fixes part of
5918 - Stop downloading consensuses when we have a consensus, even if we
5919 don't have all the certificates for it yet. Fixes bug 18809;
5920 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
5922 o Major bugfixes (directory mirrors):
5923 - Decide whether to advertise begindir support in the the same way
5924 we decide whether to advertise our DirPort. Allowing these
5925 decisions to become out-of-sync led to surprising behavior like
5926 advertising begindir support when hibernation made us not
5927 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
5930 o Major bugfixes (IPv6 bridges, client):
5931 - Actually use IPv6 addresses when selecting directory addresses for
5932 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
5935 o Major bugfixes (key management):
5936 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5937 pointer to the previous (uninitialized) key value. The impact here
5938 should be limited to a difficult-to-trigger crash, if OpenSSL is
5939 running an engine that makes key generation failures possible, or
5940 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5941 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5944 o Major bugfixes (testing):
5945 - Fix a bug that would block 'make test-network-all' on systems where
5946 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
5947 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
5948 bugfix on 0.2.8.1-alpha.
5950 o Minor features (clients):
5951 - Make clients, onion services, and bridge relays always use an
5952 encrypted begindir connection for directory requests. Resolves
5953 ticket 18483. Patch by "teor".
5955 o Minor features (fallback directory mirrors):
5956 - Give each fallback the same weight for client selection; restrict
5957 fallbacks to one per operator; report fallback directory detail
5958 changes when rebuilding list; add new fallback directory mirrors
5959 to the whitelist; and many other minor simplifications and fixes.
5960 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
5961 0.2.8.1-alpha; patch by "teor".
5962 - Replace the 21 fallbacks generated in January 2016 and included in
5963 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
5964 2016. Closes task 17158; patch by "teor".
5966 o Minor features (geoip):
5967 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
5970 o Minor bugfixes (assert, portability):
5971 - Fix an assertion failure in memarea.c on systems where "long" is
5972 shorter than the size of a pointer. Fixes bug 18716; bugfix
5975 o Minor bugfixes (bootstrap):
5976 - Consistently use the consensus download schedule for authority
5977 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
5979 o Minor bugfixes (build):
5980 - Remove a pair of redundant AM_CONDITIONAL declarations from
5981 configure.ac. Fixes one final case of bug 17744; bugfix
5983 - Resolve warnings when building on systems that are concerned with
5984 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
5986 - When libscrypt.h is found, but no libscrypt library can be linked,
5987 treat libscrypt as absent. Fixes bug 19161; bugfix
5990 o Minor bugfixes (client):
5991 - Turn all TestingClientBootstrap* into non-testing torrc options.
5992 This changes simply renames them by removing "Testing" in front of
5993 them and they do not require TestingTorNetwork to be enabled
5994 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
5995 - Make directory node selection more reliable, mainly for IPv6-only
5996 clients and clients with few reachable addresses. Fixes bug 18929;
5997 bugfix on 0.2.8.1-alpha. Patch by "teor".
5999 o Minor bugfixes (controller, microdescriptors):
6000 - Make GETINFO dir/status-vote/current/consensus conform to the
6001 control specification by returning "551 Could not open cached
6002 consensus..." when not caching consensuses. Fixes bug 18920;
6003 bugfix on 0.2.2.6-alpha.
6005 o Minor bugfixes (crypto, portability):
6006 - The SHA3 and SHAKE routines now produce the correct output on Big
6007 Endian systems. No code calls either algorithm yet, so this is
6008 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
6009 - Tor now builds again with the recent OpenSSL 1.1 development
6010 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
6013 o Minor bugfixes (directories):
6014 - When fetching extrainfo documents, compare their SHA256 digests
6015 and Ed25519 signing key certificates with the routerinfo that led
6016 us to fetch them, rather than with the most recent routerinfo.
6017 Otherwise we generate many spurious warnings about mismatches.
6018 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
6020 o Minor bugfixes (logging):
6021 - When we can't generate a signing key because OfflineMasterKey is
6022 set, do not imply that we should have been able to load it. Fixes
6023 bug 18133; bugfix on 0.2.7.2-alpha.
6024 - Stop periodic_event_dispatch() from blasting twelve lines per
6025 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
6026 - When rejecting a misformed INTRODUCE2 cell, only log at
6027 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
6029 o Minor bugfixes (pluggable transports):
6030 - Avoid reporting a spurious error when we decide that we don't need
6031 to terminate a pluggable transport because it has already exited.
6032 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
6034 o Minor bugfixes (pointer arithmetic):
6035 - Fix a bug in memarea_alloc() that could have resulted in remote
6036 heap write access, if Tor had ever passed an unchecked size to
6037 memarea_alloc(). Fortunately, all the sizes we pass to
6038 memarea_alloc() are pre-checked to be less than 128 kilobytes.
6039 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
6042 o Minor bugfixes (relays):
6043 - Consider more config options when relays decide whether to
6044 regenerate their descriptor. Fixes more of bug 12538; bugfix
6046 - Resolve some edge cases where we might launch an ORPort
6047 reachability check even when DisableNetwork is set. Noticed while
6048 fixing bug 18616; bugfix on 0.2.3.9-alpha.
6050 o Minor bugfixes (statistics):
6051 - We now include consensus downloads via IPv6 in our directory-
6052 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
6054 o Minor bugfixes (testing):
6055 - Allow directories in small networks to bootstrap by skipping
6056 DirPort checks when the consensus has no exits. Fixes bug 19003;
6057 bugfix on 0.2.8.1-alpha. Patch by teor.
6058 - Fix a small memory leak that would occur when the
6059 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
6060 bugfix on 0.2.5.2-alpha.
6062 o Minor bugfixes (time handling):
6063 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
6064 field. Otherwise, our unit tests crash on Windows. Fixes bug
6065 18977; bugfix on 0.2.2.25-alpha.
6068 - Document the contents of the 'datadir/keys' subdirectory in the
6069 manual page. Closes ticket 17621.
6070 - Stop recommending use of nicknames to identify relays in our
6071 MapAddress documentation. Closes ticket 18312.
6074 Changes in version 0.2.8.2-alpha - 2016-03-28
6075 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
6076 bugs in earlier versions of Tor, including some that prevented
6077 authorities using Tor 0.2.7.x from running correctly. IPv6 and
6078 directory support should also be much improved.
6080 o New system requirements:
6081 - Tor no longer supports versions of OpenSSL with a broken
6082 implementation of counter mode. (This bug was present in OpenSSL
6083 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
6084 longer runs with, these versions.
6085 - Tor no longer attempts to support platforms where the "time_t"
6086 type is unsigned. (To the best of our knowledge, only OpenVMS does
6087 this, and Tor has never actually built on OpenVMS.) Closes
6089 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
6090 later (released in 2008 and 2009 respectively). If you are
6091 building Tor from the git repository instead of from the source
6092 distribution, and your tools are older than this, you will need to
6093 upgrade. Closes ticket 17732.
6095 o Major bugfixes (security, pointers):
6096 - Avoid a difficult-to-trigger heap corruption attack when extending
6097 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
6098 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
6099 Reported by Guido Vranken.
6101 o Major bugfixes (bridges, pluggable transports):
6102 - Modify the check for OR connections to private addresses. Allow
6103 bridges on private addresses, including pluggable transports that
6104 ignore the (potentially private) address in the bridge line. Fixes
6105 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
6107 o Major bugfixes (compilation):
6108 - Repair hardened builds under the clang compiler. Previously, our
6109 use of _FORTIFY_SOURCE would conflict with clang's address
6110 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
6112 o Major bugfixes (crash on shutdown):
6113 - Correctly handle detaching circuits from muxes when shutting down.
6114 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
6115 - Fix an assert-on-exit bug related to counting memory usage in
6116 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
6118 o Major bugfixes (crash on startup):
6119 - Fix a segfault during startup: If a Unix domain socket was
6120 configured as listener (such as a ControlSocket or a SocksPort
6121 "unix:" socket), and tor was started as root but not configured to
6122 switch to another user, tor would segfault while trying to string
6123 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
6126 o Major bugfixes (dns proxy mode, crash):
6127 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
6128 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
6130 o Major bugfixes (relays, bridge clients):
6131 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
6132 bridge clients use the address configured in the bridge line.
6133 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
6136 o Major bugfixes (voting):
6137 - Actually enable support for authorities to match routers by their
6138 Ed25519 identities. Previously, the code had been written, but
6139 some debugging code that had accidentally been left in the
6140 codebase made it stay turned off. Fixes bug 17702; bugfix
6142 - When collating votes by Ed25519 identities, authorities now
6143 include a "NoEdConsensus" flag if the ed25519 value (or lack
6144 thereof) for a server does not reflect the majority consensus.
6145 Related to bug 17668; bugfix on 0.2.7.2-alpha.
6146 - When generating a vote with keypinning disabled, never include two
6147 entries for the same ed25519 identity. This bug was causing
6148 authorities to generate votes that they could not parse when a
6149 router violated key pinning by changing its RSA identity but
6150 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
6151 18318. Bugfix on 0.2.7.2-alpha.
6153 o Minor features (security, win32):
6154 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
6155 attack. Fixes bug 18123; bugfix on all tor versions. Patch
6158 o Minor features (bug-resistance):
6159 - Make Tor survive errors involving connections without a
6160 corresponding event object. Previously we'd fail with an
6161 assertion; now we produce a log message. Related to bug 16248.
6163 o Minor features (build):
6164 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
6165 as having possible IPFW support. Closes ticket 18448. Patch from
6168 o Minor features (code hardening):
6169 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
6170 level code, to harden against accidental failures to NUL-
6171 terminate. Part of ticket 17852. Patch from jsturgix. Found
6174 o Minor features (crypto):
6175 - Validate the hard-coded Diffie-Hellman parameters and ensure that
6176 p is a safe prime, and g is a suitable generator. Closes
6179 o Minor features (geoip):
6180 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
6183 o Minor features (hidden service directory):
6184 - Streamline relay-side hsdir handling: when relays consider whether
6185 to accept an uploaded hidden service descriptor, they no longer
6186 check whether they are one of the relays in the network that is
6187 "supposed" to handle that descriptor. Implements ticket 18332.
6189 o Minor features (IPv6):
6190 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
6191 to 1, tor prefers IPv6 directory addresses.
6192 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
6193 avoids using IPv4 for client OR and directory connections.
6194 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
6195 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
6196 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
6198 o Minor features (linux seccomp2 sandbox):
6199 - Reject attempts to change our Address with "Sandbox 1" enabled.
6200 Changing Address with Sandbox turned on would never actually work,
6201 but previously it would fail in strange and confusing ways. Found
6204 o Minor features (robustness):
6205 - Exit immediately with an error message if the code attempts to use
6206 Libevent without having initialized it. This should resolve some
6207 frequently-made mistakes in our unit tests. Closes ticket 18241.
6209 o Minor features (unix domain sockets):
6210 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
6211 Unix domain sockets without checking the permissions on the parent
6212 directory. (Tor checks permissions by default because some
6213 operating systems only check permissions on the parent directory.
6214 However, some operating systems do look at permissions on the
6215 socket, and tor's default check is unneeded.) Closes ticket 18458.
6218 o Minor bugfixes (exit policies, security):
6219 - Refresh an exit relay's exit policy when interface addresses
6220 change. Previously, tor only refreshed the exit policy when the
6221 configured external address changed. Fixes bug 18208; bugfix on
6222 0.2.7.3-rc. Patch by teor.
6224 o Minor bugfixes (security, hidden services):
6225 - Prevent hidden services connecting to client-supplied rendezvous
6226 addresses that are reserved as internal or multicast. Fixes bug
6227 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
6229 o Minor bugfixes (build):
6230 - Do not link the unit tests against both the testing and non-
6231 testing versions of the static libraries. Fixes bug 18490; bugfix
6233 - Avoid spurious failures from configure files related to calling
6234 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
6235 0.2.0.1-alpha. Patch from "cypherpunks".
6236 - Silence spurious clang-scan warnings in the ed25519_donna code by
6237 explicitly initializing some objects. Fixes bug 18384; bugfix on
6238 0.2.7.2-alpha. Patch by teor.
6240 o Minor bugfixes (client, bootstrap):
6241 - Count receipt of new microdescriptors as progress towards
6242 bootstrapping. Previously, with EntryNodes set, Tor might not
6243 successfully repopulate the guard set on bootstrapping. Fixes bug
6244 16825; bugfix on 0.2.3.1-alpha.
6246 o Minor bugfixes (code correctness):
6247 - Update to the latest version of Trunnel, which tries harder to
6248 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
6249 by clang address sanitizer. Fixes bug 18373; bugfix
6252 o Minor bugfixes (configuration):
6253 - Fix a tiny memory leak when parsing a port configuration ending in
6254 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
6256 o Minor bugfixes (containers):
6257 - If we somehow attempt to construct a heap with more than
6258 1073741822 elements, avoid an integer overflow when maintaining
6259 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
6261 o Minor bugfixes (correctness):
6262 - Fix a bad memory handling bug that would occur if we had queued a
6263 cell on a channel's incoming queue. Fortunately, we can't actually
6264 queue a cell like that as our code is constructed today, but it's
6265 best to avoid this kind of error, even if there isn't any code
6266 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
6268 o Minor bugfixes (directory):
6269 - When generating a URL for a directory server on an IPv6 address,
6270 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
6271 on 0.2.3.9-alpha. Patch from Malek.
6273 o Minor bugfixes (fallback directory mirrors):
6274 - When requesting extrainfo descriptors from a trusted directory
6275 server, check whether it is an authority or a fallback directory
6276 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
6277 0.2.4.7-alpha. Reported by atagar, patch by teor.
6279 o Minor bugfixes (hidden service, client):
6280 - Handle the case where the user makes several fast consecutive
6281 requests to the same .onion address. Previously, the first six
6282 requests would each trigger a descriptor fetch, each picking a
6283 directory (there are 6 overall) and the seventh one would fail
6284 because no directories were left, thereby triggering a close on
6285 all current directory connections asking for the hidden service.
6286 The solution here is to not close the connections if we have
6287 pending directory fetches. Fixes bug 15937; bugfix
6290 o Minor bugfixes (hidden service, control port):
6291 - Add the onion address to the HS_DESC event for the UPLOADED action
6292 both on success or failure. It was previously hardcoded with
6293 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
6295 o Minor bugfixes (hidden service, directory):
6296 - Bridges now refuse "rendezvous2" (hidden service descriptor)
6297 publish attempts. Suggested by ticket 18332.
6299 o Minor bugfixes (linux seccomp2 sandbox):
6300 - Allow the setrlimit syscall, and the prlimit and prlimit64
6301 syscalls, which some libc implementations use under the hood.
6302 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
6303 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
6304 enabled and no DNS resolvers configured. This should help TAILS
6305 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
6306 - Fix the sandbox's interoperability with unix domain sockets under
6307 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
6309 o Minor bugfixes (logging):
6310 - When logging information about an unparsable networkstatus vote or
6311 consensus, do not say "vote" when we mean consensus. Fixes bug
6312 18368; bugfix on 0.2.0.8-alpha.
6313 - Scrub service name in "unrecognized service ID" log messages.
6314 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
6315 - Downgrade logs and backtraces about IP versions to info-level.
6316 Only log backtraces once each time tor runs. Assists in diagnosing
6317 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
6318 Christian, patch by teor.
6320 o Minor bugfixes (memory safety):
6321 - Avoid freeing an uninitialized pointer when opening a socket fails
6322 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
6323 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
6325 - Correctly duplicate addresses in get_interface_address6_list().
6326 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
6327 patch by "cypherpunks".
6328 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
6330 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
6331 18672; bugfix on 0.2.5.1-alpha.
6333 o Minor bugfixes (private directory):
6334 - Prevent a race condition when creating private directories. Fixes
6335 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
6336 Patch from jsturgix. Found with Flawfinder.
6338 o Minor bugfixes (test networks, IPv6):
6339 - Allow internal IPv6 addresses in descriptors in test networks.
6340 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
6343 o Minor bugfixes (testing):
6344 - We no longer disable assertions in the unit tests when coverage is
6345 enabled. Instead, we require you to say --disable-asserts-in-tests
6346 to the configure script if you need assertions disabled in the
6347 unit tests (for example, if you want to perform branch coverage).
6348 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
6350 o Minor bugfixes (time parsing):
6351 - Avoid overflow in tor_timegm when parsing dates in and after 2038
6352 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
6353 0.0.2pre14. Patch by teor.
6355 o Minor bugfixes (tor-gencert):
6356 - Correctly handle the case where an authority operator enters a
6357 passphrase but sends an EOF before sending a newline. Fixes bug
6358 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
6360 o Code simplification and refactoring:
6361 - Quote all the string interpolations in configure.ac -- even those
6362 which we are pretty sure can't contain spaces. Closes ticket
6363 17744. Patch from zerosion.
6364 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
6365 inplace, so there's no need to have a separate implementation for
6366 the non-inplace code. Closes ticket 18258. Patch from Malek.
6367 - Simplify return types for some crypto functions that can't
6368 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
6371 - Change build messages to refer to "Fedora" instead of "Fedora
6372 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
6373 Patches from "icanhasaccount" and "cypherpunks".
6376 - We no longer maintain an internal freelist in memarea.c.
6377 Allocators should be good enough to make this code unnecessary,
6378 and it's doubtful that it ever had any performance benefit.
6381 - Fix several warnings from clang's address sanitizer produced in
6383 - Treat backtrace test failures as expected on FreeBSD until we
6384 solve bug 17808. Closes ticket 18204.
6387 Changes in version 0.2.8.1-alpha - 2016-02-04
6388 Tor 0.2.8.1-alpha is the first alpha release in its series. It
6389 includes numerous small features and bugfixes against previous Tor
6390 versions, and numerous small infrastructure improvements. The most
6391 notable features are a set of improvements to the directory subsystem.
6393 o Major features (security, Linux):
6394 - When Tor starts as root on Linux and is told to switch user ID, it
6395 can now retain the capability to bind to low ports. By default,
6396 Tor will do this only when it's switching user ID and some low
6397 ports have been configured. You can change this behavior with the
6398 new option KeepBindCapabilities. Closes ticket 8195.
6400 o Major features (directory system):
6401 - When bootstrapping multiple consensus downloads at a time, use the
6402 first one that starts downloading, and close the rest. This
6403 reduces failures when authorities or fallback directories are slow
6404 or down. Together with the code for feature 15775, this feature
6405 should reduces failures due to fallback churn. Implements ticket
6406 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
6407 "mikeperry" and "teor".
6408 - Include a trial list of 21 default fallback directories, generated
6409 in January 2016, based on an opt-in survey of suitable relays.
6410 Doing this should make clients bootstrap more quickly and reliably,
6411 and reduce the load on the directory authorities. Closes ticket
6412 15775. Patch by "teor".
6413 Candidates identified using an OnionOO script by "weasel", "teor",
6414 "gsathya", and "karsten".
6415 - Previously only relays that explicitly opened a directory port
6416 (DirPort) accepted directory requests from clients. Now all
6417 relays, with and without a DirPort, accept and serve tunneled
6418 directory requests that they receive through their ORPort. You can
6419 disable this behavior using the new DirCache option. Closes
6422 o Major key updates:
6423 - Update the V3 identity key for the dannenberg directory authority:
6424 it was changed on 18 November 2015. Closes task 17906. Patch
6427 o Minor features (security, clock):
6428 - Warn when the system clock appears to move back in time (when the
6429 state file was last written in the future). Tor doesn't know that
6430 consensuses have expired if the clock is in the past. Patch by
6431 "teor". Implements ticket 17188.
6433 o Minor features (security, exit policies):
6434 - ExitPolicyRejectPrivate now rejects more private addresses by
6435 default. Specifically, it now rejects the relay's outbound bind
6436 addresses (if configured), and the relay's configured port
6437 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
6438 0.2.0.11-alpha. Patch by "teor".
6440 o Minor features (security, memory erasure):
6441 - Set the unused entries in a smartlist to NULL. This helped catch
6442 a (harmless) bug, and shouldn't affect performance too much.
6443 Implements ticket 17026.
6444 - Use SecureMemoryWipe() function to securely clean memory on
6445 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
6446 Implements feature 17986.
6447 - Use explicit_bzero or memset_s when present. Previously, we'd use
6448 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
6449 from <logan@hackers.mu> and <selven@hackers.mu>.
6450 - Make memwipe() do nothing when passed a NULL pointer or buffer of
6451 zero size. Check size argument to memwipe() for underflow. Fixes
6452 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
6455 o Minor features (security, RNG):
6456 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
6457 positively are not allowed to fail. Previously we depended on
6458 internal details of OpenSSL's behavior. Closes ticket 17686.
6459 - Never use the system entropy output directly for anything besides
6460 seeding the PRNG. When we want to generate important keys, instead
6461 of using system entropy directly, we now hash it with the PRNG
6462 stream. This may help resist certain attacks based on broken OS
6463 entropy implementations. Closes part of ticket 17694.
6464 - Use modern system calls (like getentropy() or getrandom()) to
6465 generate strong entropy on platforms that have them. Closes
6468 o Minor features (accounting):
6469 - Added two modes to the AccountingRule option: One for limiting
6470 only the number of bytes sent ("AccountingRule out"), and one for
6471 limiting only the number of bytes received ("AccountingRule in").
6472 Closes ticket 15989; patch from "unixninja92".
6474 o Minor features (build):
6475 - Since our build process now uses "make distcheck", we no longer
6476 force "make dist" to depend on "make check". Closes ticket 17893;
6477 patch from "cypherpunks."
6478 - Tor now builds successfully with the recent OpenSSL 1.1
6479 development branch, and with the latest LibreSSL. Closes tickets
6480 17549, 17921, and 17984.
6482 o Minor features (controller):
6483 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
6484 tickets 16774 and 17817. Patch by George Tankersley.
6485 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
6486 service descriptor from a service's local hidden service
6487 descriptor cache. Closes ticket 14846.
6488 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
6489 controllers can examine the the reject rules added by
6490 ExitPolicyRejectPrivate. This makes it easier for stem to display
6493 o Minor features (crypto):
6494 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
6496 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
6497 - When allocating a digest state object, allocate no more space than
6498 we actually need. Previously, we would allocate as much space as
6499 the state for the largest algorithm would need. This change saves
6500 up to 672 bytes per circuit. Closes ticket 17796.
6501 - Improve performance when hashing non-multiple of 8 sized buffers,
6502 based on Andrew Moon's public domain SipHash-2-4 implementation.
6503 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
6505 o Minor features (directory downloads):
6506 - Wait for busy authorities and fallback directories to become non-
6507 busy when bootstrapping. (A similar change was made in 6c443e987d
6508 for directory caches chosen from the consensus.) Closes ticket
6509 17864; patch by "teor".
6510 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
6511 directory mirrors. The default is 1; set it to 0 to disable
6512 fallbacks. Implements ticket 17576. Patch by "teor".
6514 o Minor features (geoip):
6515 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
6518 o Minor features (IPv6):
6519 - Add an argument 'ipv6=address:orport' to the DirAuthority and
6520 FallbackDir torrc options, to specify an IPv6 address for an
6521 authority or fallback directory. Add hard-coded ipv6 addresses for
6522 directory authorities that have them. Closes ticket 17327; patch
6523 from Nick Mathewson and "teor".
6524 - Add address policy assume_action support for IPv6 addresses.
6525 - Limit IPv6 mask bits to 128.
6526 - Warn when comparing against an AF_UNSPEC address in a policy, it's
6527 almost always a bug. Closes ticket 17863; patch by "teor".
6528 - Allow users to configure directory authorities and fallback
6529 directory servers with IPv6 addresses and ORPorts. Resolves
6531 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
6532 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
6533 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
6534 17638; bugfix on 0.0.2pre8. Patch by "teor".
6536 o Minor features (logging):
6537 - When logging to syslog, allow a tag to be added to the syslog
6538 identity (the string prepended to every log message). The tag can
6539 be configured with SyslogIdentityTag and defaults to none. Setting
6540 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
6543 o Minor features (portability):
6544 - Use timingsafe_memcmp() where available. Closes ticket 17944;
6545 patch from <logan@hackers.mu>.
6547 o Minor features (relay, address discovery):
6548 - Add a family argument to get_interface_addresses_raw() and
6549 subfunctions to make network interface address interogation more
6550 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
6551 types of interfaces from the operating system. Resolves
6553 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
6554 fails to enumerate interface addresses using the platform-specific
6555 API, have it rely on the UDP socket fallback technique to try and
6556 find out what IP addresses (both IPv4 and IPv6) our machine has.
6557 Resolves ticket 17951.
6559 o Minor features (replay cache):
6560 - The replay cache now uses SHA256 instead of SHA1. Implements
6561 feature 8961. Patch by "teor", issue reported by "rransom".
6563 o Minor features (unix file permissions):
6564 - Defer creation of Unix sockets until after setuid. This avoids
6565 needing CAP_CHOWN and CAP_FOWNER when using systemd's
6566 CapabilityBoundingSet, or chown and fowner when using SELinux.
6567 Implements part of ticket 17562. Patch from Jamie Nguyen.
6568 - If any directory created by Tor is marked as group readable, the
6569 filesystem group is allowed to be either the default GID or the
6570 root user. Allowing root to read the DataDirectory prevents the
6571 need for CAP_READ_SEARCH when using systemd's
6572 CapabilityBoundingSet, or dac_read_search when using SELinux.
6573 Implements part of ticket 17562. Patch from Jamie Nguyen.
6574 - Introduce a new DataDirectoryGroupReadable option. If it is set to
6575 1, the DataDirectory will be made readable by the default GID.
6576 Implements part of ticket 17562. Patch from Jamie Nguyen.
6578 o Minor bugfixes (accounting):
6579 - The max bandwidth when using 'AccountRule sum' is now correctly
6580 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
6583 o Minor bugfixes (code correctness):
6584 - When closing an entry connection, generate a warning if we should
6585 have sent an end cell for it but we haven't. Fixes bug 17876;
6586 bugfix on 0.2.3.2-alpha.
6587 - Assert that allocated memory held by the reputation code is freed
6588 according to its internal counters. Fixes bug 17753; bugfix
6590 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
6593 o Minor bugfixes (compilation):
6594 - Mark all object files that include micro-revision.i as depending
6595 on it, so as to make parallel builds more reliable. Fixes bug
6596 17826; bugfix on 0.2.5.1-alpha.
6597 - Don't try to use the pthread_condattr_setclock() function unless
6598 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
6599 17819; bugfix on 0.2.6.3-alpha.
6600 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
6602 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
6603 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
6604 - Fix search for libevent libraries on OpenBSD (and other systems
6605 that install libevent 1 and libevent 2 in parallel). Fixes bug
6606 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
6607 - Isolate environment variables meant for tests from the rest of the
6608 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
6609 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
6611 - Remove config.log only from make distclean, not from make clean.
6612 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
6614 o Minor bugfixes (crypto):
6615 - Check the return value of HMAC() and assert on failure. Fixes bug
6616 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
6618 o Minor bugfixes (fallback directories):
6619 - Mark fallbacks as "too busy" when they return a 503 response,
6620 rather than just marking authorities. Fixes bug 17572; bugfix on
6621 0.2.4.7-alpha. Patch by "teor".
6623 o Minor bugfixes (IPv6):
6624 - Update the limits in max_dl_per_request for IPv6 address length.
6625 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
6627 o Minor bugfixes (linux seccomp2 sandbox):
6628 - Fix a crash when using offline master ed25519 keys with the Linux
6629 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
6631 o Minor bugfixes (logging):
6632 - In log messages that include a function name, use __FUNCTION__
6633 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
6634 with clang __PRETTY_FUNCTION__ has extra information we don't
6635 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
6637 - Remove needless quotes from a log message about unparseable
6638 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
6640 o Minor bugfixes (portability):
6641 - Remove an #endif from configure.ac so that we correctly detect the
6642 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
6645 o Minor bugfixes (relays):
6646 - Check that both the ORPort and DirPort (if present) are reachable
6647 before publishing a relay descriptor. Otherwise, relays publish a
6648 descriptor with DirPort 0 when the DirPort reachability test takes
6649 longer than the ORPort reachability test. Fixes bug 18050; bugfix
6650 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
6652 o Minor bugfixes (relays, hidden services):
6653 - Refuse connection requests to private OR addresses unless
6654 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
6655 then refuse to send any cells to a private address. Fixes bugs
6656 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
6658 o Minor bugfixes (safe logging):
6659 - When logging a malformed hostname received through socks4, scrub
6660 it if SafeLogging says we should. Fixes bug 17419; bugfix
6663 o Minor bugfixes (statistics code):
6664 - Consistently check for overflow in round_*_to_next_multiple_of
6665 functions, and add unit tests with additional and maximal values.
6666 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
6667 - Handle edge cases in the laplace functions: avoid division by
6668 zero, avoid taking the log of zero, and silence clang type
6669 conversion warnings using round and trunc. Add unit tests for edge
6670 cases with maximal values. Fixes part of bug 13192; bugfix
6673 o Minor bugfixes (testing):
6674 - The test for log_heartbeat was incorrectly failing in timezones
6675 with non-integer offsets. Instead of comparing the end of the time
6676 string against a constant, compare it to the output of
6677 format_local_iso_time when given the correct input. Fixes bug
6678 18039; bugfix on 0.2.5.4-alpha.
6679 - Make unit tests pass on IPv6-only systems, and systems without
6680 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
6681 bugfix on 0.2.7.3-rc. Patch by "teor".
6682 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
6684 - Check the full results of SHA256 and SHA512 digests in the unit
6685 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
6687 o Code simplification and refactoring:
6688 - Move logging of redundant policy entries in
6689 policies_parse_exit_policy_internal into its own function. Closes
6690 ticket 17608; patch from "juce".
6691 - Extract the more complicated parts of circuit_mark_for_close()
6692 into a new function that we run periodically before circuits are
6693 freed. This change removes more than half of the functions
6694 currently in the "blob". Closes ticket 17218.
6695 - Clean up a little duplicated code in
6696 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
6698 - Decouple the list of streams waiting to be attached to circuits
6699 from the overall connection list. This change makes it possible to
6700 attach streams quickly while simplifying Tor's callgraph and
6701 avoiding O(N) scans of the entire connection list. Closes
6703 - When a direct directory request fails immediately on launch,
6704 instead of relaunching that request from inside the code that
6705 launches it, instead mark the connection for teardown. This change
6706 simplifies Tor's callback and prevents the directory-request
6707 launching code from invoking itself recursively. Closes
6709 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
6710 use them. Closes ticket 17926.
6713 - Add a description of the correct use of the '--keygen' command-
6714 line option. Closes ticket 17583; based on text by 's7r'.
6715 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
6716 - Explain actual minima for BandwidthRate. Closes ticket 16382.
6717 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
6718 - Mention torspec URL in the manpage and point the reader to it
6719 whenever we mention a document that belongs in torspce. Fixes
6723 - Remove client-side support for connecting to Tor relays running
6724 versions of Tor before 0.2.3.6-alpha. These relays didn't support
6725 the v3 TLS handshake protocol, and are no longer allowed on the
6726 Tor network. Implements the client side of ticket 11150. Based on
6727 patches by Tom van der Woerdt.
6730 - Add unit tests to check for common RNG failure modes, such as
6731 returning all zeroes, identical values, or incrementing values
6732 (OpenSSL's rand_predictable feature). Patch by "teor".
6733 - Log more information when the backtrace tests fail. Closes ticket
6734 17892. Patch from "cypherpunks."
6735 - Always test both ed25519 backends, so that we can be sure that our
6736 batch-open replacement code works. Part of ticket 16794.
6737 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
6738 portion of ticket 16831.
6739 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
6740 util_format.c, directory.c, and options_validate.c. Closes tickets
6741 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
6743 - Unit tests for directory_handle_command_get. Closes ticket 17004.
6744 Patch from Reinaldo de Souza Jr.
6747 Changes in version 0.2.7.6 - 2015-12-10
6748 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
6749 well as a minor bug in hidden service reliability.
6751 o Major bugfixes (guard selection):
6752 - Actually look at the Guard flag when selecting a new directory
6753 guard. When we implemented the directory guard design, we
6754 accidentally started treating all relays as if they have the Guard
6755 flag during guard selection, leading to weaker anonymity and worse
6756 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
6759 o Minor features (geoip):
6760 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
6763 o Minor bugfixes (compilation):
6764 - When checking for net/pfvar.h, include netinet/in.h if possible.
6765 This fixes transparent proxy detection on OpenBSD. Fixes bug
6766 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
6767 - Fix a compilation warning with Clang 3.6: Do not check the
6768 presence of an address which can never be NULL. Fixes bug 17781.
6770 o Minor bugfixes (correctness):
6771 - When displaying an IPv6 exit policy, include the mask bits
6772 correctly even when the number is greater than 31. Fixes bug
6773 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
6774 - The wrong list was used when looking up expired intro points in a
6775 rend service object, causing what we think could be reachability
6776 issues for hidden services, and triggering a BUG log. Fixes bug
6777 16702; bugfix on 0.2.7.2-alpha.
6778 - Fix undefined behavior in the tor_cert_checksig function. Fixes
6779 bug 17722; bugfix on 0.2.7.2-alpha.
6782 Changes in version 0.2.7.5 - 2015-11-20
6783 The Tor 0.2.7 release series is dedicated to the memory of Tor user
6784 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
6785 tirelessly to advocate human rights regardless of national borders,
6786 and oppose the encroachments of mass surveillance. He opposed national
6787 exceptionalism, he brought clarity to legal and policy debates, he
6788 understood and predicted the impact of mass surveillance on the world,
6789 and he laid the groundwork for resisting it. While serving on the Tor
6790 Project's board of directors, he brought us his uncompromising focus
6791 on technical excellence in the service of humankind. Caspar was an
6792 inimitable force for good and a wonderful friend. He was kind,
6793 humorous, generous, gallant, and believed we should protect one
6794 another without exception. We honor him here for his ideals, his
6795 efforts, and his accomplishments. Please honor his memory with works
6796 that would make him proud.
6798 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
6800 The 0.2.7 series adds a more secure identity key type for relays,
6801 improves cryptography performance, resolves several longstanding
6802 hidden-service performance issues, improves controller support for
6803 hidden services, and includes small bugfixes and performance
6804 improvements throughout the program. This release series also includes
6805 more tests than before, and significant simplifications to which parts
6806 of Tor invoke which others.
6808 (This release contains no code changes since 0.2.7.4-rc.)
6811 Changes in version 0.2.7.4-rc - 2015-10-21
6812 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
6813 fixes some important memory leaks, and a scary-looking (but mostly
6814 harmless in practice) invalid-read bug. It also has a few small
6815 bugfixes, notably fixes for compilation and portability on different
6816 platforms. If no further significant bounds are found, the next
6817 release will the the official stable release.
6819 o Major bugfixes (security, correctness):
6820 - Fix an error that could cause us to read 4 bytes before the
6821 beginning of an openssl string. This bug could be used to cause
6822 Tor to crash on systems with unusual malloc implementations, or
6823 systems with unusual hardening installed. Fixes bug 17404; bugfix
6826 o Major bugfixes (correctness):
6827 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
6828 bug 17401; bugfix on 0.2.7.3-rc.
6830 o Major bugfixes (memory leaks):
6831 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
6832 17398; bugfix on 0.2.6.1-alpha.
6833 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
6834 17402; bugfix on 0.2.7.3-rc.
6835 - Fix a memory leak when reading an expired signing key from disk.
6836 Fixes bug 17403; bugfix on 0.2.7.2-rc.
6838 o Minor features (geoIP):
6839 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
6842 o Minor bugfixes (compilation):
6843 - Repair compilation with the most recent (unreleased, alpha)
6844 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
6845 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
6846 17251; bugfix on 0.2.7.2-alpha.
6847 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
6848 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
6850 o Minor bugfixes (portability):
6851 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
6852 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
6855 o Minor bugfixes (sandbox):
6856 - Add the "hidserv-stats" filename to our sandbox filter for the
6857 HiddenServiceStatistics option to work properly. Fixes bug 17354;
6858 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
6860 o Minor bugfixes (testing):
6861 - Add unit tests for get_interface_address* failure cases. Fixes bug
6862 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
6863 - Fix breakage when running 'make check' with BSD make. Fixes bug
6864 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
6865 - Make the get_ifaddrs_* unit tests more tolerant of different
6866 network configurations. (Don't assume every test box has an IPv4
6867 address, and don't assume every test box has a non-localhost
6868 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
6869 - Skip backtrace tests when backtrace support is not compiled in.
6870 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
6874 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
6875 - Note that HiddenServicePorts can take a unix domain socket. Closes
6879 Changes in version 0.2.7.3-rc - 2015-09-25
6880 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
6881 contains numerous usability fixes for Ed25519 keys, safeguards against
6882 several misconfiguration problems, significant simplifications to
6883 Tor's callgraph, and numerous bugfixes and small features.
6885 This is the most tested release of Tor to date. The unit tests cover
6886 39.40% of the code, and the integration tests (accessible with "make
6887 test-full-online", requiring stem and chutney and a network
6888 connection) raise the coverage to 64.49%.
6890 o Major features (security, hidden services):
6891 - Hidden services, if using the EntryNodes option, are required to
6892 use more than one EntryNode, in order to avoid a guard discovery
6893 attack. (This would only affect people who had configured hidden
6894 services and manually specified the EntryNodes option with a
6895 single entry-node. The impact was that it would be easy to
6896 remotely identify the guard node used by such a hidden service.
6897 See ticket for more information.) Fixes ticket 14917.
6899 o Major features (Ed25519 keys, keypinning):
6900 - The key-pinning option on directory authorities is now advisory-
6901 only by default. In a future version, or when the AuthDirPinKeys
6902 option is set, pins are enforced again. Disabling key-pinning
6903 seemed like a good idea so that we can survive the fallout of any
6904 usability problems associated with Ed25519 keys. Closes
6907 o Major features (Ed25519 performance):
6908 - Improve the speed of Ed25519 operations and Curve25519 keypair
6909 generation when built targeting 32 bit x86 platforms with SSE2
6910 available. Implements ticket 16535.
6911 - Improve the runtime speed of Ed25519 signature verification by
6912 using Ed25519-donna's batch verification support. Implements
6915 o Major features (performance testing):
6916 - The test-network.sh script now supports performance testing.
6917 Requires corresponding chutney performance testing changes. Patch
6918 by "teor". Closes ticket 14175.
6920 o Major features (relay, Ed25519):
6921 - Significant usability improvements for Ed25519 key management. Log
6922 messages are better, and the code can recover from far more
6923 failure conditions. Thanks to "s7r" for reporting and diagnosing
6925 - Add a new OfflineMasterKey option to tell Tor never to try loading
6926 or generating a secret Ed25519 identity key. You can use this in
6927 combination with tor --keygen to manage offline and/or encrypted
6928 Ed25519 keys. Implements ticket 16944.
6929 - Add a --newpass option to allow changing or removing the
6930 passphrase of an encrypted key with tor --keygen. Implements part
6932 - On receiving a HUP signal, check to see whether the Ed25519
6933 signing key has changed, and reload it if so. Closes ticket 16790.
6935 o Major bugfixes (relay, Ed25519):
6936 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
6937 0.2.7.2-alpha. Reported by "s7r".
6938 - Improve handling of expired signing keys with offline master keys.
6939 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
6941 o Minor features (client-side privacy):
6942 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
6943 lifespan when IsolateSOCKSAuth and streams with SOCKS
6944 authentication are attached to the circuit. This allows
6945 applications like TorBrowser to manage circuit lifetime on their
6946 own. Implements feature 15482.
6947 - When logging malformed hostnames from SOCKS5 requests, respect
6948 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
6950 o Minor features (compilation):
6951 - Give a warning as early as possible when trying to build with an
6952 unsupported OpenSSL version. Closes ticket 16901.
6953 - Fail during configure if we're trying to build against an OpenSSL
6954 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
6955 which started requiring ECC.
6957 o Minor features (geoip):
6958 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
6961 o Minor features (hidden services):
6962 - Relays need to have the Fast flag to get the HSDir flag. As this
6963 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
6964 drop. This change should make some attacks against the hidden
6965 service directory system harder. Fixes ticket 15963.
6966 - Turn on hidden service statistics collection by setting the torrc
6967 option HiddenServiceStatistics to "1" by default. (This keeps
6968 track only of the fraction of traffic used by hidden services, and
6969 the total number of hidden services in existence.) Closes
6971 - Client now uses an introduction point failure cache to know when
6972 to fetch or keep a descriptor in their cache. Previously, failures
6973 were recorded implicitly, but not explicitly remembered. Closes
6976 o Minor features (testing, authorities, documentation):
6977 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
6978 explicitly manage consensus flags in testing networks. Patch by
6979 "robgjansen", modified by "teor". Implements part of ticket 14882.
6981 o Minor bugfixes (security, exit policies):
6982 - ExitPolicyRejectPrivate now also rejects the relay's published
6983 IPv6 address (if any), and any publicly routable IPv4 or IPv6
6984 addresses on any local interfaces. ticket 17027. Patch by "teor".
6985 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
6987 o Minor bug fixes (torrc exit policies):
6988 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
6989 produce IPv6 wildcard addresses. Previously they would produce
6990 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
6991 of bug 16069; bugfix on 0.2.4.7-alpha.
6992 - When parsing torrc ExitPolicies, we now warn for a number of cases
6993 where the user's intent is likely to differ from Tor's actual
6994 behavior. These include: using an IPv4 address with an accept6 or
6995 reject6 line; using "private" on an accept6 or reject6 line; and
6996 including any ExitPolicy lines after accept *:* or reject *:*.
6997 Related to ticket 16069.
6998 - When parsing torrc ExitPolicies, we now issue an info-level
6999 message when expanding an "accept/reject *" line to include both
7000 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
7001 - In each instance above, usage advice is provided to avoid the
7002 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
7003 16069; bugfix on 0.2.4.7-alpha.
7005 o Minor bugfixes (authority):
7006 - Don't assign "HSDir" to a router if it isn't Valid and Running.
7007 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
7008 - Downgrade log messages about Ed25519 key issues if they are in old
7009 cached router descriptors. Fixes part of bug 16286; bugfix
7011 - When we find an Ed25519 key issue in a cached descriptor, stop
7012 saying the descriptor was just "uploaded". Fixes another part of
7013 bug 16286; bugfix on 0.2.7.2-alpha.
7015 o Minor bugfixes (control port):
7016 - Repair a warning and a spurious result when getting the maximum
7017 number of file descriptors from the controller. Fixes bug 16697;
7018 bugfix on 0.2.7.2-alpha.
7020 o Minor bugfixes (correctness):
7021 - When calling channel_free_list(), avoid calling smartlist_remove()
7022 while inside a FOREACH loop. This partially reverts commit
7023 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
7024 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
7026 o Minor bugfixes (documentation):
7027 - Advise users on how to configure separate IPv4 and IPv6 exit
7028 policies in the manpage and sample torrcs. Related to ticket 16069.
7029 - Fix the usage message of tor-resolve(1) so that it no longer lists
7030 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
7031 - Fix an error in the manual page and comments for
7032 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
7033 required "ORPort connectivity". While this is true, it is in no
7034 way unique to the HSDir flag. Of all the flags, only HSDirs need a
7035 DirPort configured in order for the authorities to assign that
7036 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
7039 o Minor bugfixes (Ed25519):
7040 - Fix a memory leak when reading router descriptors with expired
7041 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
7043 o Minor bugfixes (linux seccomp2 sandbox):
7044 - Allow bridge authorities to run correctly under the seccomp2
7045 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
7046 - Allow routers with ed25519 keys to run correctly under the
7047 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
7049 o Minor bugfixes (open file limit):
7050 - Fix set_max_file_descriptors() to set by default the max open file
7051 limit to the current limit when setrlimit() fails. Fixes bug
7052 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
7054 o Minor bugfixes (portability):
7055 - Try harder to normalize the exit status of the Tor process to the
7056 standard-provided range. Fixes bug 16975; bugfix on every version
7058 - Check correctly for Windows socket errors in the workqueue
7059 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
7060 - Fix the behavior of crypto_rand_time_range() when told to consider
7061 times before 1970. (These times were possible when running in a
7062 simulated network environment where time()'s output starts at
7063 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
7064 - Restore correct operation of TLS client-cipher detection on
7065 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
7067 o Minor bugfixes (relay):
7068 - Ensure that worker threads actually exit when a fatal error or
7069 shutdown is indicated. This fix doesn't currently affect the
7070 behavior of Tor, because Tor workers never indicates fatal error
7071 or shutdown except in the unit tests. Fixes bug 16868; bugfix
7073 - Unblock threads before releasing the work queue mutex to ensure
7074 predictable scheduling behavior. Fixes bug 16644; bugfix
7077 o Code simplification and refactoring:
7078 - Change the function that's called when we need to retry all
7079 downloads so that it only reschedules the downloads to happen
7080 immediately, rather than launching them all at once itself. This
7081 further simplifies Tor's callgraph.
7082 - Move some format-parsing functions out of crypto.c and
7083 crypto_curve25519.c into crypto_format.c and/or util_format.c.
7084 - Move the client-only parts of init_keys() into a separate
7085 function. Closes ticket 16763.
7086 - Simplify the microdesc_free() implementation so that it no longer
7087 appears (to code analysis tools) to potentially invoke a huge
7088 suite of other microdesc functions.
7089 - Simply the control graph further by deferring the inner body of
7090 directory_all_unreachable() into a callback. Closes ticket 16762.
7091 - Treat the loss of an owning controller as equivalent to a SIGTERM
7092 signal. This removes a tiny amount of duplicated code, and
7093 simplifies our callgraph. Closes ticket 16788.
7094 - When generating an event to send to the controller, we no longer
7095 put the event over the network immediately. Instead, we queue
7096 these events, and use a Libevent callback to deliver them. This
7097 change simplifies Tor's callgraph by reducing the number of
7098 functions from which all other Tor functions are reachable. Closes
7100 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
7101 that try to scan or compile every file on Unix won't decide that
7103 - Remove the unused "nulterminate" argument from buf_pullup().
7106 - Recommend a 40 GB example AccountingMax in torrc.sample rather
7107 than a 4 GB max. Closes ticket 16742.
7108 - Include the TUNING document in our source tarball. It is referred
7109 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
7113 - The internal pure-C tor-fw-helper tool is now removed from the Tor
7114 distribution, in favor of the pure-Go clone available from
7115 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
7116 used by the C tor-fw-helper are not, in our opinion, very
7117 confidence- inspiring in their secure-programming techniques.
7118 Closes ticket 13338.
7119 - Remove the code that would try to aggressively flush controller
7120 connections while writing to them. This code was introduced in
7121 0.1.2.7-alpha, in order to keep output buffers from exceeding
7122 their limits. But there is no longer a maximum output buffer size,
7123 and flushing data in this way caused some undesirable recursions
7124 in our call graph. Closes ticket 16480.
7127 - Make "bridges+hs" the default test network. This tests almost all
7128 tor functionality during make test-network, while allowing tests
7129 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
7130 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
7131 (chutney). Patches by "teor".
7132 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
7133 by-side in the same parent directory. Closes ticket 16903. Patch
7135 - Use environment variables rather than autoconf substitutions to
7136 send variables from the build system to the test scripts. This
7137 change should be easier to maintain, and cause 'make distcheck' to
7138 work better than before. Fixes bug 17148.
7139 - Add a new set of callgraph analysis scripts that use clang to
7140 produce a list of which Tor functions are reachable from which
7141 other Tor functions. We're planning to use these to help simplify
7142 our code structure by identifying illogical dependencies.
7143 - Add new 'test-full' and 'test-full-online' targets to run all
7144 tests, including integration tests with stem and chutney.
7145 - Make the test-workqueue test work on Windows by initializing the
7146 network before we begin.
7147 - New make target (make test-network-all) to run multiple applicable
7148 chutney test cases. Patch from Teor; closes 16953.
7149 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
7150 functions in dns.c. Implements a portion of ticket 16831.
7151 - When building Tor with testing coverage enabled, run Chutney tests
7152 (if any) using the 'tor-cov' coverage binary.
7153 - When running test-network or test-stem, check for the absence of
7154 stem/chutney before doing any build operations.
7157 Changes in version 0.2.7.2-alpha - 2015-07-27
7158 This, the second alpha in the Tor 0.2.7 series, has a number of new
7159 features, including a way to manually pick the number of introduction
7160 points for hidden services, and the much stronger Ed25519 signing key
7161 algorithm for regular Tor relays (including support for encrypted
7162 offline identity keys in the new algorithm).
7164 Support for Ed25519 on relays is currently limited to signing router
7165 descriptors; later alphas in this series will extend Ed25519 key
7166 support to more parts of the Tor protocol.
7168 o Major features (Ed25519 identity keys, Proposal 220):
7169 - All relays now maintain a stronger identity key, using the Ed25519
7170 elliptic curve signature format. This master key is designed so
7171 that it can be kept offline. Relays also generate an online
7172 signing key, and a set of other Ed25519 keys and certificates.
7173 These are all automatically regenerated and rotated as needed.
7174 Implements part of ticket 12498.
7175 - Directory authorities now vote on Ed25519 identity keys along with
7176 RSA1024 keys. Implements part of ticket 12498.
7177 - Directory authorities track which Ed25519 identity keys have been
7178 used with which RSA1024 identity keys, and do not allow them to
7179 vary freely. Implements part of ticket 12498.
7180 - Microdescriptors now include Ed25519 identity keys. Implements
7181 part of ticket 12498.
7182 - Add support for offline encrypted Ed25519 master keys. To use this
7183 feature on your tor relay, run "tor --keygen" to make a new master
7184 key (or to make a new signing key if you already have a master
7185 key). Closes ticket 13642.
7187 o Major features (Hidden services):
7188 - Add the torrc option HiddenServiceNumIntroductionPoints, to
7189 specify a fixed number of introduction points. Its maximum value
7190 is 10 and default is 3. Using this option can increase a hidden
7191 service's reliability under load, at the cost of making it more
7192 visible that the hidden service is facing extra load. Closes
7194 - Remove the adaptive algorithm for choosing the number of
7195 introduction points, which used to change the number of
7196 introduction points (poorly) depending on the number of
7197 connections the HS sees. Closes ticket 4862.
7199 o Major features (onion key cross-certification):
7200 - Relay descriptors now include signatures of their own identity
7201 keys, made using the TAP and ntor onion keys. These signatures
7202 allow relays to prove ownership of their own onion keys. Because
7203 of this change, microdescriptors will no longer need to include
7204 RSA identity keys. Implements proposal 228; closes ticket 12499.
7206 o Major features (performance):
7207 - Improve the runtime speed of Ed25519 operations by using the
7208 public-domain Ed25519-donna by Andrew M. ("floodyberry").
7209 Implements ticket 16467.
7210 - Improve the runtime speed of the ntor handshake by using an
7211 optimized curve25519 basepoint scalarmult implementation from the
7212 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
7213 ideas by Adam Langley. Implements ticket 9663.
7215 o Major bugfixes (client-side privacy, also in 0.2.6.9):
7216 - Properly separate out each SOCKSPort when applying stream
7217 isolation. The error occurred because each port's session group
7218 was being overwritten by a default value when the listener
7219 connection was initialized. Fixes bug 16247; bugfix on
7220 0.2.6.3-alpha. Patch by "jojelino".
7222 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
7223 - Stop refusing to store updated hidden service descriptors on a
7224 client. This reverts commit 9407040c59218 (which indeed fixed bug
7225 14219, but introduced a major hidden service reachability
7226 regression detailed in bug 16381). This is a temporary fix since
7227 we can live with the minor issue in bug 14219 (it just results in
7228 some load on the network) but the regression of 16381 is too much
7229 of a setback. First-round fix for bug 16381; bugfix
7232 o Major bugfixes (hidden services):
7233 - When cannibalizing a circuit for an introduction point, always
7234 extend to the chosen exit node (creating a 4 hop circuit).
7235 Previously Tor would use the current circuit exit node, which
7236 changed the original choice of introduction point, and could cause
7237 the hidden service to skip excluded introduction points or
7238 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
7241 o Major bugfixes (open file limit):
7242 - The open file limit wasn't checked before calling
7243 tor_accept_socket_nonblocking(), which would make Tor exceed the
7244 limit. Now, before opening a new socket, Tor validates the open
7245 file limit just before, and if the max has been reached, return an
7246 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
7248 o Major bugfixes (stability, also in 0.2.6.10):
7249 - Stop crashing with an assertion failure when parsing certain kinds
7250 of malformed or truncated microdescriptors. Fixes bug 16400;
7251 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7252 by "cypherpunks_backup".
7253 - Stop random client-side assertion failures that could occur when
7254 connecting to a busy hidden service, or connecting to a hidden
7255 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7258 o Minor features (directory authorities, security, also in 0.2.6.9):
7259 - The HSDir flag given by authorities now requires the Stable flag.
7260 For the current network, this results in going from 2887 to 2806
7261 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7262 attack by raising the effort for a relay to become Stable to
7263 require at the very least 7 days, while maintaining the 96 hours
7264 uptime requirement for HSDir. Implements ticket 8243.
7266 o Minor features (client):
7267 - Relax the validation of hostnames in SOCKS5 requests, allowing the
7268 character '_' to appear, in order to cope with domains observed in
7269 the wild that are serving non-RFC compliant records. Resolves
7271 - Relax the validation done to hostnames in SOCKS5 requests, and
7272 allow a single trailing '.' to cope with clients that pass FQDNs
7273 using that syntax to explicitly indicate that the domain name is
7274 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
7275 - Add GroupWritable and WorldWritable options to unix-socket based
7276 SocksPort and ControlPort options. These options apply to a single
7277 socket, and override {Control,Socks}SocketsGroupWritable. Closes
7280 o Minor features (control protocol):
7281 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
7282 the control protocol. Resolves ticket 15358.
7284 o Minor features (directory authorities):
7285 - Directory authorities no longer vote against the "Fast", "Stable",
7286 and "HSDir" flags just because they were going to vote against
7287 "Running": if the consensus turns out to be that the router was
7288 running, then the authority's vote should count. Patch from Peter
7289 Retzlaff; closes issue 8712.
7291 o Minor features (geoip, also in 0.2.6.10):
7292 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
7293 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
7295 o Minor features (hidden services):
7296 - Add the new options "HiddenServiceMaxStreams" and
7297 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
7298 limit the maximum number of simultaneous streams per circuit, and
7299 optionally tear down the circuit when the limit is exceeded. Part
7302 o Minor features (portability):
7303 - Use C99 variadic macros when the compiler is not GCC. This avoids
7304 failing compilations on MSVC, and fixes a log-file-based race
7305 condition in our old workarounds. Original patch from Gisle Vanem.
7307 o Minor bugfixes (compilation, also in 0.2.6.9):
7308 - Build with --enable-systemd correctly when libsystemd is
7309 installed, but systemd is not. Fixes bug 16164; bugfix on
7310 0.2.6.3-alpha. Patch from Peter Palfrader.
7312 o Minor bugfixes (controller):
7313 - Add the descriptor ID in each HS_DESC control event. It was
7314 missing, but specified in control-spec.txt. Fixes bug 15881;
7315 bugfix on 0.2.5.2-alpha.
7317 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
7318 - Check for failures from crypto_early_init, and refuse to continue.
7319 A previous typo meant that we could keep going with an
7320 uninitialized crypto library, and would have OpenSSL initialize
7321 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7322 when implementing ticket 4900. Patch by "teor".
7324 o Minor bugfixes (hidden services):
7325 - Fix a crash when reloading configuration while at least one
7326 configured and one ephemeral hidden service exists. Fixes bug
7327 16060; bugfix on 0.2.7.1-alpha.
7328 - Avoid crashing with a double-free bug when we create an ephemeral
7329 hidden service but adding it fails for some reason. Fixes bug
7330 16228; bugfix on 0.2.7.1-alpha.
7332 o Minor bugfixes (Linux seccomp2 sandbox):
7333 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
7334 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
7336 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
7337 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7338 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7339 on 0.2.6.3-alpha. Patch from "teor".
7341 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
7342 - Fix sandboxing to work when running as a relay, by allowing the
7343 renaming of secret_id_key, and allowing the eventfd2 and futex
7344 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
7346 - Allow systemd connections to work with the Linux seccomp2 sandbox
7347 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7350 o Minor bugfixes (relay):
7351 - Fix a rarely-encountered memory leak when failing to initialize
7352 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
7355 o Minor bugfixes (systemd):
7356 - Fix an accidental formatting error that broke the systemd
7357 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
7358 - Tor's systemd unit file no longer contains extraneous spaces.
7359 These spaces would sometimes confuse tools like deb-systemd-
7360 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
7362 o Minor bugfixes (tests):
7363 - Use the configured Python executable when running test-stem-full.
7364 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
7366 o Minor bugfixes (tests, also in 0.2.6.9):
7367 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7368 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7370 o Minor bugfixes (threads, comments):
7371 - Always initialize return value in compute_desc_id in rendcommon.c
7372 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
7373 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
7374 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
7375 - Remove undefined directive-in-macro in test_util_writepid clang
7376 3.7 complains that using a preprocessor directive inside a macro
7377 invocation in test_util_writepid in test_util.c is undefined.
7378 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
7380 o Code simplification and refactoring:
7381 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
7382 to ensure they remain consistent and visible everywhere.
7383 - Remove some vestigial workarounds for the MSVC6 compiler. We
7384 haven't supported that in ages.
7385 - The link authentication code has been refactored for better
7386 testability and reliability. It now uses code generated with the
7387 "trunnel" binary encoding generator, to reduce the risk of bugs
7388 due to programmer error. Done as part of ticket 12498.
7391 - Include a specific and (hopefully) accurate documentation of the
7392 torrc file's meta-format in doc/torrc_format.txt. This is mainly
7393 of interest to people writing programs to parse or generate torrc
7394 files. This document is not a commitment to long-term
7395 compatibility; some aspects of the current format are a bit
7396 ridiculous. Closes ticket 2325.
7399 - Tor no longer supports copies of OpenSSL that are missing support
7400 for Elliptic Curve Cryptography. (We began using ECC when
7401 available in 0.2.4.8-alpha, for more safe and efficient key
7402 negotiation.) In particular, support for at least one of P256 or
7403 P224 is now required, with manual configuration needed if only
7404 P224 is available. Resolves ticket 16140.
7405 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
7406 on an operating system that has not upgraded to OpenSSL 1.0 or
7407 later, and you compile Tor from source, you will need to install a
7408 more recent OpenSSL to link Tor against.) These versions of
7409 OpenSSL are still supported by the OpenSSL, but the numerous
7410 cryptographic improvements in later OpenSSL releases makes them a
7411 clear choice. Resolves ticket 16034.
7412 - Remove the HidServDirectoryV2 option. Now all relays offer to
7413 store hidden service descriptors. Related to 16543.
7414 - Remove the VoteOnHidServDirectoriesV2 option, since all
7415 authorities have long set it to 1. Closes ticket 16543.
7418 - Document use of coverity, clang static analyzer, and clang dynamic
7419 undefined behavior and address sanitizers in doc/HACKING. Include
7420 detailed usage instructions in the blacklist. Patch by "teor".
7421 Closes ticket 15817.
7422 - The link authentication protocol code now has extensive tests.
7423 - The relay descriptor signature testing code now has
7425 - The test_workqueue program now runs faster, and is enabled by
7426 default as a part of "make check".
7427 - Now that OpenSSL has its own scrypt implementation, add an unit
7428 test that checks for interoperability between libscrypt_scrypt()
7429 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
7430 and rely on EVP_PBE_scrypt() whenever possible. Resolves
7434 Changes in version 0.2.6.10 - 2015-07-12
7435 Tor version 0.2.6.10 fixes some significant stability and hidden
7436 service client bugs, bulletproofs the cryptography init process, and
7437 fixes a bug when using the sandbox code with some older versions of
7438 Linux. Everyone running an older version, especially an older version
7439 of 0.2.6, should upgrade.
7441 o Major bugfixes (hidden service clients, stability):
7442 - Stop refusing to store updated hidden service descriptors on a
7443 client. This reverts commit 9407040c59218 (which indeed fixed bug
7444 14219, but introduced a major hidden service reachability
7445 regression detailed in bug 16381). This is a temporary fix since
7446 we can live with the minor issue in bug 14219 (it just results in
7447 some load on the network) but the regression of 16381 is too much
7448 of a setback. First-round fix for bug 16381; bugfix
7451 o Major bugfixes (stability):
7452 - Stop crashing with an assertion failure when parsing certain kinds
7453 of malformed or truncated microdescriptors. Fixes bug 16400;
7454 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7455 by "cypherpunks_backup".
7456 - Stop random client-side assertion failures that could occur when
7457 connecting to a busy hidden service, or connecting to a hidden
7458 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7461 o Minor features (geoip):
7462 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
7463 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
7465 o Minor bugfixes (crypto error-handling):
7466 - Check for failures from crypto_early_init, and refuse to continue.
7467 A previous typo meant that we could keep going with an
7468 uninitialized crypto library, and would have OpenSSL initialize
7469 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7470 when implementing ticket 4900. Patch by "teor".
7472 o Minor bugfixes (Linux seccomp2 sandbox):
7473 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7474 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7475 on 0.2.6.3-alpha. Patch from "teor".
7478 Changes in version 0.2.6.9 - 2015-06-11
7479 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
7480 requirements for receiving an HSDir flag, and addresses some other small
7481 bugs in the systemd and sandbox code. Clients using circuit isolation
7482 should upgrade; all directory authorities should upgrade.
7484 o Major bugfixes (client-side privacy):
7485 - Properly separate out each SOCKSPort when applying stream
7486 isolation. The error occurred because each port's session group was
7487 being overwritten by a default value when the listener connection
7488 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
7491 o Minor feature (directory authorities, security):
7492 - The HSDir flag given by authorities now requires the Stable flag.
7493 For the current network, this results in going from 2887 to 2806
7494 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7495 attack by raising the effort for a relay to become Stable which
7496 takes at the very least 7 days to do so and by keeping the 96
7497 hours uptime requirement for HSDir. Implements ticket 8243.
7499 o Minor bugfixes (compilation):
7500 - Build with --enable-systemd correctly when libsystemd is
7501 installed, but systemd is not. Fixes bug 16164; bugfix on
7502 0.2.6.3-alpha. Patch from Peter Palfrader.
7504 o Minor bugfixes (Linux seccomp2 sandbox):
7505 - Fix sandboxing to work when running as a relaymby renaming of
7506 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
7507 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
7508 - Allow systemd connections to work with the Linux seccomp2 sandbox
7509 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7512 o Minor bugfixes (tests):
7513 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7514 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7517 Changes in version 0.2.6.8 - 2015-05-21
7518 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
7519 fixes an authority-side bug in assigning the HSDir flag. All directory
7520 authorities should upgrade.
7522 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
7523 - Revert commit that made directory authorities assign the HSDir
7524 flag to relays without a DirPort; this was bad because such relays
7525 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7528 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7529 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7530 a client authorized hidden service. Fixes bug 15823; bugfix
7533 o Minor features (geoip):
7534 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
7535 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
7539 Changes in version 0.2.7.1-alpha - 2015-05-12
7540 Tor 0.2.7.1-alpha is the first alpha release in its series. It
7541 includes numerous small features and bugfixes against previous Tor
7542 versions, and numerous small infrastructure improvements. The most
7543 notable features are several new ways for controllers to interact with
7544 the hidden services subsystem.
7546 o New system requirements:
7547 - Tor no longer includes workarounds to support Libevent versions
7548 before 1.3e. Libevent 2.0 or later is recommended. Closes
7551 o Major features (controller):
7552 - Add the ADD_ONION and DEL_ONION commands that allow the creation
7553 and management of hidden services via the controller. Closes
7555 - New "GETINFO onions/current" and "GETINFO onions/detached"
7556 commands to get information about hidden services created via the
7557 controller. Part of ticket 6411.
7558 - New HSFETCH command to launch a request for a hidden service
7559 descriptor. Closes ticket 14847.
7560 - New HSPOST command to upload a hidden service descriptor. Closes
7561 ticket 3523. Patch by "DonnchaC".
7563 o Major bugfixes (hidden services):
7564 - Revert commit that made directory authorities assign the HSDir
7565 flag to relays without a DirPort; this was bad because such relays
7566 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7569 o Minor features (clock-jump tolerance):
7570 - Recover better when our clock jumps back many hours, like might
7571 happen for Tails or Whonix users who start with a very wrong
7572 hardware clock, use Tor to discover a more accurate time, and then
7573 fix their clock. Resolves part of ticket 8766.
7575 o Minor features (command-line interface):
7576 - Make --hash-password imply --hush to prevent unnecessary noise.
7577 Closes ticket 15542. Patch from "cypherpunks".
7578 - Print a warning whenever we find a relative file path being used
7579 as torrc option. Resolves issue 14018.
7581 o Minor features (controller):
7582 - Add DirAuthority lines for default directory authorities to the
7583 output of the "GETINFO config/defaults" command if not already
7584 present. Implements ticket 14840.
7585 - Controllers can now use "GETINFO hs/client/desc/id/..." to
7586 retrieve items from the client's hidden service descriptor cache.
7587 Closes ticket 14845.
7588 - Implement a new controller command "GETINFO status/fresh-relay-
7589 descs" to fetch a descriptor/extrainfo pair that was generated on
7590 demand just for the controller's use. Implements ticket 14784.
7592 o Minor features (DoS-resistance):
7593 - Make it harder for attackers to overload hidden services with
7594 introductions, by blocking multiple introduction requests on the
7595 same circuit. Resolves ticket 15515.
7597 o Minor features (geoip):
7598 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
7599 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
7602 o Minor features (HS popularity countermeasure):
7603 - To avoid leaking HS popularity, don't cycle the introduction point
7604 when we've handled a fixed number of INTRODUCE2 cells but instead
7605 cycle it when a random number of introductions is reached, thus
7606 making it more difficult for an attacker to find out the amount of
7607 clients that have used the introduction point for a specific HS.
7608 Closes ticket 15745.
7610 o Minor features (logging):
7611 - Include the Tor version in all LD_BUG log messages, since people
7612 tend to cut and paste those into the bugtracker. Implements
7615 o Minor features (pluggable transports):
7616 - When launching managed pluggable transports on Linux systems,
7617 attempt to have the kernel deliver a SIGTERM on tor exit if the
7618 pluggable transport process is still running. Resolves
7620 - When launching managed pluggable transports, setup a valid open
7621 stdin in the child process that can be used to detect if tor has
7622 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
7623 can be used by implementations to detect this new behavior.
7624 Resolves ticket 15435.
7626 o Minor features (testing):
7627 - Add a test to verify that the compiler does not eliminate our
7628 memwipe() implementation. Closes ticket 15377.
7629 - Add make rule `check-changes` to verify the format of changes
7630 files. Closes ticket 15180.
7631 - Add unit tests for control_event_is_interesting(). Add a compile-
7632 time check that the number of events doesn't exceed the capacity
7633 of control_event_t.event_mask. Closes ticket 15431, checks for
7634 bugs similar to 13085. Patch by "teor".
7635 - Command-line argument tests moved to Stem. Resolves ticket 14806.
7636 - Integrate the ntor, backtrace, and zero-length keys tests into the
7637 automake test suite. Closes ticket 15344.
7638 - Remove assertions during builds to determine Tor's test coverage.
7639 We don't want to trigger these even in assertions, so including
7640 them artificially makes our branch coverage look worse than it is.
7641 This patch provides the new test-stem-full and coverage-html-full
7642 configure options. Implements ticket 15400.
7644 o Minor bugfixes (build):
7645 - Improve out-of-tree builds by making non-standard rules work and
7646 clean up additional files and directories. Fixes bug 15053; bugfix
7649 o Minor bugfixes (command-line interface):
7650 - When "--quiet" is provided along with "--validate-config", do not
7651 write anything to stdout on success. Fixes bug 14994; bugfix
7653 - When complaining about bad arguments to "--dump-config", use
7656 o Minor bugfixes (configuration, unit tests):
7657 - Only add the default fallback directories when the DirAuthorities,
7658 AlternateDirAuthority, and FallbackDir directory config options
7659 are set to their defaults. The default fallback directory list is
7660 currently empty, this fix will only change tor's behavior when it
7661 has default fallback directories. Includes unit tests for
7662 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
7663 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
7665 o Minor bugfixes (correctness):
7666 - For correctness, avoid modifying a constant string in
7667 handle_control_postdescriptor. Fixes bug 15546; bugfix
7669 - Remove side-effects from tor_assert() calls. This was harmless,
7670 because we never disable assertions, but it is bad style and
7671 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
7674 o Minor bugfixes (hidden service):
7675 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7676 a client authorized hidden service. Fixes bug 15823; bugfix
7678 - Remove an extraneous newline character from the end of hidden
7679 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
7681 o Minor bugfixes (interface):
7682 - Print usage information for --dump-config when it is used without
7683 an argument. Also, fix the error message to use different wording
7684 and add newline at the end. Fixes bug 15541; bugfix
7687 o Minor bugfixes (logs):
7688 - When building Tor under Clang, do not include an extra set of
7689 parentheses in log messages that include function names. Fixes bug
7690 15269; bugfix on every released version of Tor when compiled with
7691 recent enough Clang.
7693 o Minor bugfixes (network):
7694 - When attempting to use fallback technique for network interface
7695 lookup, disregard loopback and multicast addresses since they are
7696 unsuitable for public communications.
7698 o Minor bugfixes (statistics):
7699 - Disregard the ConnDirectionStatistics torrc options when Tor is
7700 not a relay since in that mode of operation no sensible data is
7701 being collected and because Tor might run into measurement hiccups
7702 when running as a client for some time, then becoming a relay.
7703 Fixes bug 15604; bugfix on 0.2.2.35.
7705 o Minor bugfixes (test networks):
7706 - When self-testing reachability, use ExtendAllowPrivateAddresses to
7707 determine if local/private addresses imply reachability. The
7708 previous fix used TestingTorNetwork, which implies
7709 ExtendAllowPrivateAddresses, but this excluded rare configurations
7710 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
7711 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
7712 issue discovered by CJ Ess.
7714 o Minor bugfixes (testing):
7715 - Check for matching value in server response in ntor_ref.py. Fixes
7716 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
7718 - Set the severity correctly when testing
7719 get_interface_addresses_ifaddrs() and
7720 get_interface_addresses_win32(), so that the tests fail gracefully
7721 instead of triggering an assertion. Fixes bug 15759; bugfix on
7722 0.2.6.3-alpha. Reported by Nicolas Derive.
7724 o Code simplification and refactoring:
7725 - Move the hacky fallback code out of get_interface_address6() into
7726 separate function and get it covered with unit-tests. Resolves
7728 - Refactor hidden service client-side cache lookup to intelligently
7729 report its various failure cases, and disentangle failure cases
7730 involving a lack of introduction points. Closes ticket 14391.
7731 - Use our own Base64 encoder instead of OpenSSL's, to allow more
7732 control over the output. Part of ticket 15652.
7735 - Improve the descriptions of statistics-related torrc options in
7736 the manpage to describe rationale and possible uses cases. Fixes
7738 - Improve the layout and formatting of ./configure --help messages.
7739 Closes ticket 15024. Patch from "cypherpunks".
7740 - Standardize on the term "server descriptor" in the manual page.
7741 Previously, we had used "router descriptor", "server descriptor",
7742 and "relay descriptor" interchangeably. Part of ticket 14987.
7745 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
7746 and always use the internal Base64 decoder. The internal decoder
7747 has been part of tor since 0.2.0.10-alpha, and no one should
7748 be using the OpenSSL one. Part of ticket 15652.
7749 - Remove the 'tor_strclear()' function; use memwipe() instead.
7750 Closes ticket 14922.
7753 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
7754 fingerprinting we now recommend pluggable transports; for forward-
7755 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
7756 - Remove the undocumented "--digests" command-line option. It
7757 complicated our build process, caused subtle build issues on
7758 multiple platforms, and is now redundant since we started
7759 including git version identifiers. Closes ticket 14742.
7760 - Tor no longer contains checks for ancient directory cache versions
7761 that didn't know about microdescriptors.
7762 - Tor no longer contains workarounds for stat files generated by
7763 super-old versions of Tor that didn't choose guards sensibly.
7766 Changes in version 0.2.4.27 - 2015-04-06
7767 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
7768 could be used by an attacker to crash hidden services, or crash clients
7769 visiting hidden services. Hidden services should upgrade as soon as
7770 possible; clients should upgrade whenever packages become available.
7772 This release also backports a simple improvement to make hidden
7773 services a bit less vulnerable to denial-of-service attacks.
7775 o Major bugfixes (security, hidden service):
7776 - Fix an issue that would allow a malicious client to trigger an
7777 assertion failure and halt a hidden service. Fixes bug 15600;
7778 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7779 - Fix a bug that could cause a client to crash with an assertion
7780 failure when parsing a malformed hidden service descriptor. Fixes
7781 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7783 o Minor features (DoS-resistance, hidden service):
7784 - Introduction points no longer allow multiple INTRODUCE1 cells to
7785 arrive on the same circuit. This should make it more expensive for
7786 attackers to overwhelm hidden services with introductions.
7787 Resolves ticket 15515.
7790 Changes in version 0.2.5.12 - 2015-04-06
7791 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
7792 could be used by an attacker to crash hidden services, or crash clients
7793 visiting hidden services. Hidden services should upgrade as soon as
7794 possible; clients should upgrade whenever packages become available.
7796 This release also backports a simple improvement to make hidden
7797 services a bit less vulnerable to denial-of-service attacks.
7799 o Major bugfixes (security, hidden service):
7800 - Fix an issue that would allow a malicious client to trigger an
7801 assertion failure and halt a hidden service. Fixes bug 15600;
7802 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7803 - Fix a bug that could cause a client to crash with an assertion
7804 failure when parsing a malformed hidden service descriptor. Fixes
7805 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7807 o Minor features (DoS-resistance, hidden service):
7808 - Introduction points no longer allow multiple INTRODUCE1 cells to
7809 arrive on the same circuit. This should make it more expensive for
7810 attackers to overwhelm hidden services with introductions.
7811 Resolves ticket 15515.
7814 Changes in version 0.2.6.7 - 2015-04-06
7815 Tor 0.2.6.7 fixes two security issues that could be used by an
7816 attacker to crash hidden services, or crash clients visiting hidden
7817 services. Hidden services should upgrade as soon as possible; clients
7818 should upgrade whenever packages become available.
7820 This release also contains two simple improvements to make hidden
7821 services a bit less vulnerable to denial-of-service attacks.
7823 o Major bugfixes (security, hidden service):
7824 - Fix an issue that would allow a malicious client to trigger an
7825 assertion failure and halt a hidden service. Fixes bug 15600;
7826 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7827 - Fix a bug that could cause a client to crash with an assertion
7828 failure when parsing a malformed hidden service descriptor. Fixes
7829 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7831 o Minor features (DoS-resistance, hidden service):
7832 - Introduction points no longer allow multiple INTRODUCE1 cells to
7833 arrive on the same circuit. This should make it more expensive for
7834 attackers to overwhelm hidden services with introductions.
7835 Resolves ticket 15515.
7836 - Decrease the amount of reattempts that a hidden service performs
7837 when its rendezvous circuits fail. This reduces the computational
7838 cost for running a hidden service under heavy load. Resolves
7842 Changes in version 0.2.6.6 - 2015-03-24
7843 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
7845 It adds numerous safety, security, correctness, and performance
7846 improvements. Client programs can be configured to use more kinds of
7847 sockets, AutomapHosts works better, the multithreading backend is
7848 improved, cell transmission is refactored, test coverage is much
7849 higher, more denial-of-service attacks are handled, guard selection is
7850 improved to handle long-term guards better, pluggable transports
7851 should work a bit better, and some annoying hidden service performance
7852 bugs should be addressed.
7854 o Minor bugfixes (portability):
7855 - Use the correct datatype in the SipHash-2-4 function to prevent
7856 compilers from assuming any sort of alignment. Fixes bug 15436;
7857 bugfix on 0.2.5.3-alpha.
7859 Changes in version 0.2.6.5-rc - 2015-03-18
7860 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
7861 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
7863 o Major bugfixes (client):
7864 - Avoid crashing when making certain configuration option changes on
7865 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
7868 o Major bugfixes (pluggable transports):
7869 - Initialize the extended OR Port authentication cookie before
7870 launching pluggable transports. This prevents a race condition
7871 that occured when server-side pluggable transports would cache the
7872 authentication cookie before it has been (re)generated. Fixes bug
7873 15240; bugfix on 0.2.5.1-alpha.
7875 o Major bugfixes (portability):
7876 - Do not crash on startup when running on Solaris. Fixes a bug
7877 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
7880 o Minor features (heartbeat):
7881 - On relays, report how many connections we negotiated using each
7882 version of the Tor link protocols. This information will let us
7883 know if removing support for very old versions of the Tor
7884 protocols is harming the network. Closes ticket 15212.
7886 o Code simplification and refactoring:
7887 - Refactor main loop to extract the 'loop' part. This makes it
7888 easier to run Tor under Shadow. Closes ticket 15176.
7891 Changes in version 0.2.5.11 - 2015-03-17
7892 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
7894 It backports several bugfixes from the 0.2.6 branch, including a
7895 couple of medium-level security fixes for relays and exit nodes.
7896 It also updates the list of directory authorities.
7898 o Directory authority changes:
7899 - Remove turtles as a directory authority.
7900 - Add longclaw as a new (v3) directory authority. This implements
7901 ticket 13296. This keeps the directory authority count at 9.
7902 - The directory authority Faravahar has a new IP address. This
7903 closes ticket 14487.
7905 o Major bugfixes (crash, OSX, security):
7906 - Fix a remote denial-of-service opportunity caused by a bug in
7907 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7910 o Major bugfixes (relay, stability, possible security):
7911 - Fix a bug that could lead to a relay crashing with an assertion
7912 failure if a buffer of exactly the wrong layout was passed to
7913 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7914 0.2.0.10-alpha. Patch from 'cypherpunks'.
7915 - Do not assert if the 'data' pointer on a buffer is advanced to the
7916 very end of the buffer; log a BUG message instead. Only assert if
7917 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7919 o Major bugfixes (exit node stability):
7920 - Fix an assertion failure that could occur under high DNS load.
7921 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7922 diagnosed and fixed by "cypherpunks".
7924 o Major bugfixes (Linux seccomp2 sandbox):
7925 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7926 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7927 0.2.5.1-alpha. Patch from "sanic".
7929 o Minor features (controller):
7930 - New "GETINFO bw-event-cache" to get information about recent
7931 bandwidth events. Closes ticket 14128. Useful for controllers to
7932 get recent bandwidth history after the fix for ticket 13988.
7934 o Minor features (geoip):
7935 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7936 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7939 o Minor bugfixes (client, automapping):
7940 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
7941 no value follows the option. Fixes bug 14142; bugfix on
7942 0.2.4.7-alpha. Patch by "teor".
7943 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
7944 14195; bugfix on 0.1.0.1-rc.
7946 o Minor bugfixes (compilation):
7947 - Build without warnings with the stock OpenSSL srtp.h header, which
7948 has a duplicate declaration of SSL_get_selected_srtp_profile().
7949 Fixes bug 14220; this is OpenSSL's bug, not ours.
7951 o Minor bugfixes (directory authority):
7952 - Allow directory authorities to fetch more data from one another if
7953 they find themselves missing lots of votes. Previously, they had
7954 been bumping against the 10 MB queued data limit. Fixes bug 14261;
7955 bugfix on 0.1.2.5-alpha.
7956 - Enlarge the buffer to read bwauth generated files to avoid an
7957 issue when parsing the file in dirserv_read_measured_bandwidths().
7958 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
7960 o Minor bugfixes (statistics):
7961 - Increase period over which bandwidth observations are aggregated
7962 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7964 o Minor bugfixes (preventative security, C safety):
7965 - When reading a hexadecimal, base-32, or base-64 encoded value from
7966 a string, always overwrite the whole output buffer. This prevents
7967 some bugs where we would look at (but fortunately, not reveal)
7968 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7972 Changes in version 0.2.4.26 - 2015-03-17
7973 Tor 0.2.4.26 includes an updated list of directory authorities. It
7974 also backports a couple of stability and security bugfixes from 0.2.5
7977 o Directory authority changes:
7978 - Remove turtles as a directory authority.
7979 - Add longclaw as a new (v3) directory authority. This implements
7980 ticket 13296. This keeps the directory authority count at 9.
7981 - The directory authority Faravahar has a new IP address. This
7982 closes ticket 14487.
7984 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
7985 - Fix an assertion failure that could occur under high DNS load.
7986 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7987 diagnosed and fixed by "cypherpunks".
7989 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
7990 - Fix a bug that could lead to a relay crashing with an assertion
7991 failure if a buffer of exactly the wrong layout was passed to
7992 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7993 0.2.0.10-alpha. Patch from 'cypherpunks'.
7994 - Do not assert if the 'data' pointer on a buffer is advanced to the
7995 very end of the buffer; log a BUG message instead. Only assert if
7996 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7998 o Minor features (geoip):
7999 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8000 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8003 Changes in version 0.2.6.4-rc - 2015-03-09
8004 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
8005 attacker might be able to use in order to crash certain Tor
8006 directories. It also resolves some minor issues left over from, or
8007 introduced in, Tor 0.2.6.3-alpha or earlier.
8009 o Major bugfixes (crash, OSX, security):
8010 - Fix a remote denial-of-service opportunity caused by a bug in
8011 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
8014 o Major bugfixes (relay, stability, possible security):
8015 - Fix a bug that could lead to a relay crashing with an assertion
8016 failure if a buffer of exactly the wrong layout is passed to
8017 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8018 0.2.0.10-alpha. Patch from "cypherpunks".
8019 - Do not assert if the 'data' pointer on a buffer is advanced to the
8020 very end of the buffer; log a BUG message instead. Only assert if
8021 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8023 o Major bugfixes (FreeBSD IPFW transparent proxy):
8024 - Fix address detection with FreeBSD transparent proxies, when
8025 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
8028 o Major bugfixes (Linux seccomp2 sandbox):
8029 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
8030 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
8032 - Allow AF_UNIX hidden services to be used with the seccomp2
8033 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
8034 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
8035 crash during attempts to call wait4. Fixes bug 15088; bugfix on
8036 0.2.5.1-alpha. Patch from "sanic".
8038 o Minor features (controller):
8039 - Messages about problems in the bootstrap process now include
8040 information about the server we were trying to connect to when we
8041 noticed the problem. Closes ticket 15006.
8043 o Minor features (geoip):
8044 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8045 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8048 o Minor features (logs):
8049 - Quiet some log messages in the heartbeat and at startup. Closes
8052 o Minor bugfixes (certificate handling):
8053 - If an authority operator accidentally makes a signing certificate
8054 with a future publication time, do not discard its real signing
8055 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
8056 - Remove any old authority certificates that have been superseded
8057 for at least two days. Previously, we would keep superseded
8058 certificates until they expired, if they were published close in
8059 time to the certificate that superseded them. Fixes bug 11454;
8060 bugfix on 0.2.1.8-alpha.
8062 o Minor bugfixes (compilation):
8063 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
8065 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
8068 o Minor bugfixes (testing):
8069 - Fix endianness issues in unit test for resolve_my_address() to
8070 have it pass on big endian systems. Fixes bug 14980; bugfix on
8072 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
8073 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
8074 - When running the new 'make test-stem' target, use the configured
8075 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
8077 - When running the zero-length-keys tests, do not use the default
8078 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
8081 o Directory authority IP change:
8082 - The directory authority Faravahar has a new IP address. This
8083 closes ticket 14487.
8086 - Remove some lingering dead code that once supported mempools.
8087 Mempools were disabled by default in 0.2.5, and removed entirely
8088 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
8092 Changes in version 0.2.6.3-alpha - 2015-02-19
8093 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
8094 the 0.2.6.x series. It introduces support for more kinds of sockets,
8095 makes it harder to accidentally run an exit, improves our
8096 multithreading backend, incorporates several fixes for the
8097 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
8099 If no major regressions or security holes are found in this version,
8100 the next version will be a release candidate.
8102 o Deprecated versions:
8103 - Tor relays older than 0.2.4.18-rc are no longer allowed to
8104 advertise themselves on the network. Closes ticket 13555.
8106 o Major features (security, unix domain sockets):
8107 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
8108 applications can reach Tor without having to create AF_INET or
8109 AF_INET6 sockets, meaning they can completely disable their
8110 ability to make non-Tor network connections. To create a socket of
8111 this type, use "SocksPort unix:/path/to/socket". Implements
8113 - Support mapping hidden service virtual ports to AF_UNIX sockets.
8114 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
8115 Implements ticket 11485.
8117 o Major features (changed defaults):
8118 - Prevent relay operators from unintentionally running exits: When a
8119 relay is configured as an exit node, we now warn the user unless
8120 the "ExitRelay" option is set to 1. We warn even more loudly if
8121 the relay is configured with the default exit policy, since this
8122 can indicate accidental misconfiguration. Setting "ExitRelay 0"
8123 stops Tor from running as an exit relay. Closes ticket 10067.
8125 o Major features (directory system):
8126 - When downloading server- or microdescriptors from a directory
8127 server, we no longer launch multiple simultaneous requests to the
8128 same server. This reduces load on the directory servers,
8129 especially when directory guards are in use. Closes ticket 9969.
8130 - When downloading server- or microdescriptors over a tunneled
8131 connection, do not limit the length of our requests to what the
8132 Squid proxy is willing to handle. Part of ticket 9969.
8133 - Authorities can now vote on the correct digests and latest
8134 versions for different software packages. This allows packages
8135 that include Tor to use the Tor authority system as a way to get
8136 notified of updates and their correct digests. Implements proposal
8137 227. Closes ticket 10395.
8139 o Major features (guards):
8140 - Introduce the Guardfraction feature to improves load balancing on
8141 guard nodes. Specifically, it aims to reduce the traffic gap that
8142 guard nodes experience when they first get the Guard flag. This is
8143 a required step if we want to increase the guard lifetime to 9
8144 months or greater. Closes ticket 9321.
8146 o Major features (performance):
8147 - Make the CPU worker implementation more efficient by avoiding the
8148 kernel and lengthening pipelines. The original implementation used
8149 sockets to transfer data from the main thread to the workers, and
8150 didn't allow any thread to be assigned more than a single piece of
8151 work at once. The new implementation avoids communications
8152 overhead by making requests in shared memory, avoiding kernel IO
8153 where possible, and keeping more requests in flight at once.
8154 Implements ticket 9682.
8156 o Major features (relay):
8157 - Raise the minimum acceptable configured bandwidth rate for bridges
8158 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
8159 20 KiB/sec.) Closes ticket 13822.
8161 o Major bugfixes (exit node stability):
8162 - Fix an assertion failure that could occur under high DNS load.
8163 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8164 diagnosed and fixed by "cypherpunks".
8166 o Major bugfixes (mixed relay-client operation):
8167 - When running as a relay and client at the same time (not
8168 recommended), if we decide not to use a new guard because we want
8169 to retry older guards, only close the locally-originating circuits
8170 passing through that guard. Previously we would close all the
8171 circuits through that guard. Fixes bug 9819; bugfix on
8172 0.2.1.1-alpha. Reported by "skruffy".
8174 o Minor features (build):
8175 - New --disable-system-torrc compile-time option to prevent Tor from
8176 looking for the system-wide torrc or torrc-defaults files.
8177 Resolves ticket 13037.
8179 o Minor features (controller):
8180 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
8181 events so controllers can observe circuit isolation inputs. Closes
8183 - ControlPort now supports the unix:/path/to/socket syntax as an
8184 alternative to the ControlSocket option, for consistency with
8185 SocksPort and HiddenServicePort. Closes ticket 14451.
8186 - New "GETINFO bw-event-cache" to get information about recent
8187 bandwidth events. Closes ticket 14128. Useful for controllers to
8188 get recent bandwidth history after the fix for ticket 13988.
8190 o Minor features (Denial of service resistance):
8191 - Count the total number of bytes used storing hidden service
8192 descriptors against the value of MaxMemInQueues. If we're low on
8193 memory, and more than 20% of our memory is used holding hidden
8194 service descriptors, free them until no more than 10% of our
8195 memory holds hidden service descriptors. Free the least recently
8196 fetched descriptors first. Resolves ticket 13806.
8197 - When we have recently been under memory pressure (over 3/4 of
8198 MaxMemInQueues is allocated), then allocate smaller zlib objects
8199 for small requests. Closes ticket 11791.
8201 o Minor features (geoip):
8202 - Update geoip and geoip6 files to the January 7 2015 Maxmind
8203 GeoLite2 Country database.
8205 o Minor features (guard nodes):
8206 - Reduce the time delay before saving guard status to disk from 10
8207 minutes to 30 seconds (or from one hour to 10 minutes if
8208 AvoidDiskWrites is set). Closes ticket 12485.
8210 o Minor features (hidden service):
8211 - Make Sybil attacks against hidden services harder by changing the
8212 minimum time required to get the HSDir flag from 25 hours up to 96
8213 hours. Addresses ticket 14149.
8214 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
8215 services to disable the anti-scanning feature introduced in
8216 0.2.6.2-alpha. With this option not set, a connection to an
8217 unlisted port closes the circuit. With this option set, only a
8218 RELAY_DONE cell is sent. Closes ticket 14084.
8220 o Minor features (interface):
8221 - Implement "-f -" command-line option to read torrc configuration
8222 from standard input, if you don't want to store the torrc file in
8223 the file system. Implements feature 13865.
8225 o Minor features (logging):
8226 - Add a count of unique clients to the bridge heartbeat message.
8227 Resolves ticket 6852.
8228 - Suppress "router info incompatible with extra info" message when
8229 reading extrainfo documents from cache. (This message got loud
8230 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
8232 - Elevate hidden service authorized-client message from DEBUG to
8233 INFO. Closes ticket 14015.
8235 o Minor features (stability):
8236 - Add assertions in our hash-table iteration code to check for
8237 corrupted values that could cause infinite loops. Closes
8240 o Minor features (systemd):
8241 - Various improvements and modernizations in systemd hardening
8242 support. Closes ticket 13805. Patch from Craig Andrews.
8244 o Minor features (testing networks):
8245 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
8246 and the default on a testing network to 2 minutes. Drop the
8247 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
8248 keep the default on a testing network at 30 seconds. This reduces
8249 HS bootstrap time to around 25 seconds. Also, change the default
8250 time in test-network.sh to match. Closes ticket 13401. Patch
8252 - Create TestingDirAuthVoteHSDir to correspond to
8253 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
8254 HSDir flag for the listed relays regardless of uptime or ORPort
8255 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
8256 Partial implementation for ticket 14067. Patch by "teor".
8258 o Minor features (tor2web mode):
8259 - Introduce the config option Tor2webRendezvousPoints, which allows
8260 clients in Tor2webMode to select a specific Rendezvous Point to be
8261 used in HS circuits. This might allow better performance for
8262 Tor2Web nodes. Implements ticket 12844.
8264 o Minor bugfixes (client DNS):
8265 - Report the correct cached DNS expiration times on SOCKS port or in
8266 DNS replies. Previously, we would report everything as "never
8267 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
8268 - Avoid a small memory leak when we find a cached answer for a
8269 reverse DNS lookup in a client-side DNS cache. (Remember, client-
8270 side DNS caching is off by default, and is not recommended.) Fixes
8271 bug 14259; bugfix on 0.2.0.1-alpha.
8273 o Minor bugfixes (client, automapping):
8274 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8275 no value follows the option. Fixes bug 14142; bugfix on
8276 0.2.4.7-alpha. Patch by "teor".
8277 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8278 14195; bugfix on 0.1.0.1-rc.
8279 - Prevent changes to other options from removing the wildcard value
8280 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
8282 - Allow MapAddress and AutomapHostsOnResolve to work together when
8283 an address is mapped into another address type (like .onion) that
8284 must be automapped at resolve time. Fixes bug 7555; bugfix
8287 o Minor bugfixes (client, bridges):
8288 - When we are using bridges and we had a network connectivity
8289 problem, only retry connecting to our currently configured
8290 bridges, not all bridges we know about and remember using. Fixes
8291 bug 14216; bugfix on 0.2.2.17-alpha.
8293 o Minor bugfixes (client, IPv6):
8294 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
8295 flag is not set; and not because the NoIPv4Traffic flag was set.
8296 Previously we'd looked at the NoIPv4Traffic flag for both types of
8297 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
8299 o Minor bugfixes (compilation):
8300 - The address of an array in the middle of a structure will always
8301 be non-NULL. clang recognises this and complains. Disable the
8302 tautologous and redundant check to silence this warning. Fixes bug
8303 14001; bugfix on 0.2.1.2-alpha.
8304 - Avoid warnings when building with systemd 209 or later. Fixes bug
8305 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
8306 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
8307 Addresses ticket 14188.
8308 - Build without warnings with the stock OpenSSL srtp.h header, which
8309 has a duplicate declaration of SSL_get_selected_srtp_profile().
8310 Fixes bug 14220; this is OpenSSL's bug, not ours.
8311 - Do not compile any code related to Tor2Web mode when Tor2Web mode
8312 is not enabled at compile time. Previously, this code was included
8313 in a disabled state. See discussion on ticket 12844.
8314 - Remove the --disable-threads configure option again. It was
8315 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
8316 14819; bugfix on 0.2.6.2-alpha.
8318 o Minor bugfixes (controller):
8319 - Report "down" in response to the "GETINFO entry-guards" command
8320 when relays are down with an unreachable_since value. Previously,
8321 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
8322 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
8323 14116; bugfix on 0.2.2.9-alpha.
8324 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
8325 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
8327 o Minor bugfixes (directory authority):
8328 - Allow directory authorities to fetch more data from one another if
8329 they find themselves missing lots of votes. Previously, they had
8330 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8331 bugfix on 0.1.2.5-alpha.
8332 - Do not attempt to download extrainfo documents which we will be
8333 unable to validate with a matching server descriptor. Fixes bug
8334 13762; bugfix on 0.2.0.1-alpha.
8335 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
8336 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
8337 - Enlarge the buffer to read bwauth generated files to avoid an
8338 issue when parsing the file in dirserv_read_measured_bandwidths().
8339 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8341 o Minor bugfixes (file handling):
8342 - Stop failing when key files are zero-length. Instead, generate new
8343 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
8344 on all versions of Tor. Patch by "teor".
8345 - Stop generating a fresh .old RSA onion key file when the .old file
8346 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
8347 - Avoid overwriting .old key files with empty key files.
8348 - Skip loading zero-length extrainfo store, router store, stats,
8349 state, and key files.
8350 - Avoid crashing when trying to reload a torrc specified as a
8351 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
8354 o Minor bugfixes (hidden services):
8355 - Close the introduction circuit when we have no more usable intro
8356 points, instead of waiting for it to time out. This also ensures
8357 that no follow-up HS descriptor fetch is triggered when the
8358 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
8359 - When fetching a hidden service descriptor for a down service that
8360 was recently up, do not keep refetching until we try the same
8361 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
8362 - Successfully launch Tor with a nonexistent hidden service
8363 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
8364 14106; bugfix on 0.2.6.2-alpha.
8366 o Minor bugfixes (logging):
8367 - Avoid crashing when there are more log domains than entries in
8368 domain_list. Bugfix on 0.2.3.1-alpha.
8369 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
8371 - Don't log messages to stdout twice when starting up. Fixes bug
8372 13993; bugfix on 0.2.6.1-alpha.
8374 o Minor bugfixes (parsing):
8375 - Stop accepting milliseconds (or other junk) at the end of
8376 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
8377 - Support two-number and three-number version numbers correctly, in
8378 case we change the Tor versioning system in the future. Fixes bug
8379 13661; bugfix on 0.0.8pre1.
8381 o Minor bugfixes (path counting):
8382 - When deciding whether the consensus lists any exit nodes, count
8383 the number listed in the consensus, not the number we have
8384 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
8385 - When deciding whether we have any exit nodes, only examine
8386 ExitNodes when the ExitNodes option is actually set. Fixes part of
8387 bug 14918; bugfix on 0.2.6.2-alpha.
8388 - Get rid of redundant and possibly scary warnings that we are
8389 missing directory information while we bootstrap. Fixes part of
8390 bug 14918; bugfix on 0.2.6.2-alpha.
8392 o Minor bugfixes (portability):
8393 - Fix the ioctl()-based network interface lookup code so that it
8394 will work on systems that have variable-length struct ifreq, for
8396 - Fix scheduler compilation on targets where char is unsigned. Fixes
8397 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
8399 o Minor bugfixes (sandbox):
8400 - Allow glibc fatal errors to be sent to stderr before Tor exits.
8401 Previously, glibc would try to write them to /dev/tty, and the
8402 sandbox would trap the call and make Tor exit prematurely. Fixes
8403 bug 14759; bugfix on 0.2.5.1-alpha.
8405 o Minor bugfixes (shutdown):
8406 - When shutting down, always call event_del() on lingering read or
8407 write events before freeing them. Otherwise, we risk double-frees
8408 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
8411 o Minor bugfixes (small memory leaks):
8412 - Avoid leaking memory when using IPv6 virtual address mappings.
8413 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
8416 o Minor bugfixes (statistics):
8417 - Increase period over which bandwidth observations are aggregated
8418 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
8420 o Minor bugfixes (systemd support):
8421 - Fix detection and operation of systemd watchdog. Fixes part of bug
8422 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
8423 - Run correctly under systemd with the RunAsDaemon option set. Fixes
8424 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
8425 - Inform the systemd supervisor about more changes in the Tor
8426 process status. Implements part of ticket 14141. Patch from
8428 - Cause the "--disable-systemd" option to actually disable systemd
8429 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
8432 o Minor bugfixes (TLS):
8433 - Check more thoroughly throughout the TLS code for possible
8434 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
8436 o Minor bugfixes (transparent proxy):
8437 - Use getsockname, not getsockopt, to retrieve the address for a
8438 TPROXY-redirected connection. Fixes bug 13796; bugfix
8441 o Code simplification and refactoring:
8442 - Move fields related to isolating and configuring client ports into
8443 a shared structure. Previously, they were duplicated across
8444 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
8445 to copy them correctly had been the cause of at least one bug in
8446 the past. Closes ticket 8546.
8447 - Refactor the get_interface_addresses_raw() doom-function into
8448 multiple smaller and simpler subfunctions. Cover the resulting
8449 subfunctions with unit-tests. Fixes a significant portion of
8451 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
8452 only for version <= 0.2.2.24 which is now deprecated. Closes
8454 - Remove a test for a long-defunct broken version-one
8458 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
8459 for writing the OpenBSD-specific tips. Resolves ticket 13702.
8460 - Make the tor-resolve documentation match its help string and its
8461 options. Resolves part of ticket 14325.
8462 - Log a more useful error message from tor-resolve when failing to
8463 look up a hidden service address. Resolves part of ticket 14325.
8465 o Downgraded warnings:
8466 - Don't warn when we've attempted to contact a relay using the wrong
8467 ntor onion key. Closes ticket 9635.
8470 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
8471 longer silently accepted as an alias for "ExitNodes".
8472 - The --enable-mempool and --enable-buf-freelists options, which
8473 were originally created to work around bad malloc implementations,
8474 no longer exist. They were off-by-default in 0.2.5. Closes
8478 - Make the checkdir/perms test complete successfully even if the
8479 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
8480 - Test that tor does not fail when key files are zero-length. Check
8481 that tor generates new keys, and overwrites the empty key files.
8482 - Test that tor generates new keys when keys are missing
8483 (existing behavior).
8484 - Test that tor does not overwrite key files that already contain
8485 data (existing behavior). Tests bug 13111. Patch by "teor".
8486 - New "make test-stem" target to run stem integration tests.
8487 Requires that the "STEM_SOURCE_DIR" environment variable be set.
8488 Closes ticket 14107.
8489 - Make the test_cmdline_args.py script work correctly on Windows.
8490 Patch from Gisle Vanem.
8491 - Move the slower unit tests into a new "./src/test/test-slow"
8492 binary that can be run independently of the other tests. Closes
8494 - Avoid undefined behavior when sampling huge values from the
8495 Laplace distribution. This made unittests fail on Raspberry Pi.
8496 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
8499 Changes in version 0.2.6.2-alpha - 2014-12-31
8500 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
8501 It introduces a major new backend for deciding when to send cells on
8502 channels, which should lead down the road to big performance
8503 increases. It contains security and statistics features for better
8504 work on hidden services, and numerous bugfixes.
8506 This release contains many new unit tests, along with major
8507 performance improvements for running testing networks using Chutney.
8508 Thanks to a series of patches contributed by "teor", testing networks
8509 should now bootstrap in seconds, rather than minutes.
8511 o Major features (relay, infrastructure):
8512 - Complete revision of the code that relays use to decide which cell
8513 to send next. Formerly, we selected the best circuit to write on
8514 each channel, but we didn't select among channels in any
8515 sophisticated way. Now, we choose the best circuits globally from
8516 among those whose channels are ready to deliver traffic.
8518 This patch implements a new inter-cmux comparison API, a global
8519 high/low watermark mechanism and a global scheduler loop for
8520 transmission prioritization across all channels as well as among
8521 circuits on one channel. This schedule is currently tuned to
8522 (tolerantly) avoid making changes in network performance, but it
8523 should form the basis for major circuit performance increases in
8524 the future. Code by Andrea; tuning by Rob Jansen; implements
8527 o Major features (hidden services):
8528 - Make HS port scanning more difficult by immediately closing the
8529 circuit when a user attempts to connect to a nonexistent port.
8530 Closes ticket 13667.
8531 - Add a HiddenServiceStatistics option that allows Tor relays to
8532 gather and publish statistics about the overall size and volume of
8533 hidden service usage. Specifically, when this option is turned on,
8534 an HSDir will publish an approximate number of hidden services
8535 that have published descriptors to it the past 24 hours. Also, if
8536 a relay has acted as a hidden service rendezvous point, it will
8537 publish the approximate amount of rendezvous cells it has relayed
8538 the past 24 hours. The statistics themselves are obfuscated so
8539 that the exact values cannot be derived. For more details see
8540 proposal 238, "Better hidden service stats from Tor relays". This
8541 feature is currently disabled by default. Implements feature 13192.
8543 o Major bugfixes (client, automap):
8544 - Repair automapping with IPv6 addresses. This automapping should
8545 have worked previously, but one piece of debugging code that we
8546 inserted to detect a regression actually caused the regression to
8547 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
8548 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
8551 o Major bugfixes (hidden services):
8552 - When closing an introduction circuit that was opened in parallel
8553 with others, don't mark the introduction point as unreachable.
8554 Previously, the first successful connection to an introduction
8555 point would make the other introduction points get marked as
8556 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
8558 o Directory authority changes:
8559 - Remove turtles as a directory authority.
8560 - Add longclaw as a new (v3) directory authority. This implements
8561 ticket 13296. This keeps the directory authority count at 9.
8563 o Major removed features:
8564 - Tor clients no longer support connecting to hidden services
8565 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
8566 option has been removed. (There shouldn't be any hidden services
8567 running these versions on the network.) Closes ticket 7803.
8569 o Minor features (client):
8570 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
8571 is enabled, reject requests with IP addresses as hostnames.
8572 Resolves ticket 13315.
8574 o Minor features (controller):
8575 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
8576 write an unscheduled heartbeat message to the log. Implements
8579 o Minor features (geoip):
8580 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
8583 o Minor features (hidden services):
8584 - When re-enabling the network, don't try to build introduction
8585 circuits until we have successfully built a circuit. This makes
8586 hidden services come up faster when the network is re-enabled.
8587 Patch from "akwizgran". Closes ticket 13447.
8588 - When we fail to retrieve a hidden service descriptor, send the
8589 controller an "HS_DESC FAILED" controller event. Implements
8591 - New HiddenServiceDirGroupReadable option to cause hidden service
8592 directories and hostname files to be created group-readable. Patch
8593 from "anon", David Stainton, and "meejah". Closes ticket 11291.
8595 o Minor features (systemd):
8596 - Where supported, when running with systemd, report successful
8597 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
8598 - When running with systemd, support systemd watchdog messages. Part
8599 of ticket 11016. Patch by Michael Scherer.
8601 o Minor features (transparent proxy):
8602 - Update the transparent proxy option checks to allow for both ipfw
8603 and pf on OS X. Closes ticket 14002.
8604 - Use the correct option when using IPv6 with transparent proxy
8605 support on Linux. Resolves 13808. Patch by Francisco Blas
8608 o Minor bugfixes (preventative security, C safety):
8609 - When reading a hexadecimal, base-32, or base-64 encoded value from
8610 a string, always overwrite the whole output buffer. This prevents
8611 some bugs where we would look at (but fortunately, not reveal)
8612 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
8614 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
8615 just the part that's used. This makes it harder for data leak bugs
8616 to occur in the event of other programming failures. Resolves
8619 o Minor bugfixes (client, microdescriptors):
8620 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
8621 computing which microdescriptors to download. This keeps us from
8622 erroneous download behavior if two microdescriptor digests ever
8623 have the same first 160 bits. Fixes part of bug 13399; bugfix
8625 - Reset a router's status if its microdescriptor digest changes,
8626 even if the first 160 bits remain the same. Fixes part of bug
8627 13399; bugfix on 0.2.3.1-alpha.
8629 o Minor bugfixes (compilation):
8630 - Silence clang warnings under --enable-expensive-hardening,
8631 including implicit truncation of 64 bit values to 32 bit, const
8632 char assignment to self, tautological compare, and additional
8633 parentheses around equality tests. Fixes bug 13577; bugfix
8635 - Fix a clang warning about checking whether an address in the
8636 middle of a structure is NULL. Fixes bug 14001; bugfix
8639 o Minor bugfixes (hidden services):
8640 - Correctly send a controller event when we find that a rendezvous
8641 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
8642 - Pre-check directory permissions for new hidden-services to avoid
8643 at least one case of "Bug: Acting on config options left us in a
8644 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
8645 - When adding a new hidden service (for example, via SETCONF), Tor
8646 no longer congratulates the user for running a relay. Fixes bug
8647 13941; bugfix on 0.2.6.1-alpha.
8648 - When fetching hidden service descriptors, we now check not only
8649 for whether we got the hidden service we had in mind, but also
8650 whether we got the particular descriptors we wanted. This prevents
8651 a class of inefficient but annoying DoS attacks by hidden service
8652 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
8655 o Minor bugfixes (Linux seccomp2 sandbox):
8656 - Make transparent proxy support work along with the seccomp2
8657 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
8658 by Francisco Blas Izquierdo Riera.
8659 - Fix a memory leak in tor-resolve when running with the sandbox
8660 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
8662 o Minor bugfixes (logging):
8663 - Downgrade warnings about RSA signature failures to info log level.
8664 Emit a warning when an extra info document is found incompatible
8665 with a corresponding router descriptor. Fixes bug 9812; bugfix
8667 - Make connection_ap_handshake_attach_circuit() log the circuit ID
8668 correctly. Fixes bug 13701; bugfix on 0.0.6.
8670 o Minor bugfixes (misc):
8671 - Stop allowing invalid address patterns like "*/24" that contain
8672 both a wildcard address and a bit prefix length. This affects all
8673 our address-range parsing code. Fixes bug 7484; bugfix
8676 o Minor bugfixes (testing networks, fast startup):
8677 - Allow Tor to build circuits using a consensus with no exits. If
8678 the consensus has no exits (typical of a bootstrapping test
8679 network), allow Tor to build circuits once enough descriptors have
8680 been downloaded. This assists in bootstrapping a testing Tor
8681 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
8683 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
8684 header to directory servers. This allows us to obtain consensuses
8685 promptly when the consensus interval is very short. This assists
8686 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
8687 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
8688 - Stop assuming that private addresses are local when checking
8689 reachability in a TestingTorNetwork. Instead, when testing, assume
8690 all OR connections are remote. (This is necessary due to many test
8691 scenarios running all relays on localhost.) This assists in
8692 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
8693 0.1.0.1-rc. Patch by "teor".
8694 - Avoid building exit circuits from a consensus with no exits. Now
8695 thanks to our fix for 13718, we accept a no-exit network as not
8696 wholly lost, but we need to remember not to try to build exit
8697 circuits on it. Closes ticket 13814; patch by "teor".
8698 - Stop requiring exits to have non-zero bandwithcapacity in a
8699 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
8700 ignore exit bandwidthcapacity. This assists in bootstrapping a
8701 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
8702 on 0.2.0.3-alpha. Patch by "teor".
8703 - Add "internal" to some bootstrap statuses when no exits are
8704 available. If the consensus does not contain Exits, Tor will only
8705 build internal circuits. In this case, relevant statuses will
8706 contain the word "internal" as indicated in the Tor control-
8707 spec.txt. When bootstrap completes, Tor will be ready to build
8708 internal circuits. If a future consensus contains Exits, exit
8709 circuits may become available. Fixes part of bug 13718; bugfix on
8710 0.2.4.10-alpha. Patch by "teor".
8711 - Decrease minimum consensus interval to 10 seconds when
8712 TestingTorNetwork is set, or 5 seconds for the first consensus.
8713 Fix assumptions throughout the code that assume larger intervals.
8714 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
8716 - Avoid excluding guards from path building in minimal test
8717 networks, when we're in a test network and excluding guards would
8718 exclude all relays. This typically occurs in incredibly small tor
8719 networks, and those using "TestingAuthVoteGuard *". Fixes part of
8720 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
8722 o Code simplification and refactoring:
8723 - Stop using can_complete_circuits as a global variable; access it
8724 with a function instead.
8725 - Avoid using operators directly as macro arguments: this lets us
8726 apply coccinelle transformations to our codebase more directly.
8727 Closes ticket 13172.
8728 - Combine the functions used to parse ClientTransportPlugin and
8729 ServerTransportPlugin into a single function. Closes ticket 6456.
8730 - Add inline functions and convenience macros for inspecting channel
8731 state. Refactor the code to use convenience macros instead of
8732 checking channel state directly. Fixes issue 7356.
8733 - Document all members of was_router_added_t and rename
8734 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
8735 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
8736 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
8737 constant instead of hardcoded value. Fixes issue 13840.
8738 - Refactor our generic strmap and digestmap types into a single
8739 implementation, so that we can add a new digest256map
8743 - Document the bridge-authority-only 'networkstatus-bridges' file.
8744 Closes ticket 13713; patch from "tom".
8745 - Fix typo in PredictedPortsRelevanceTime option description in
8746 manpage. Resolves issue 13707.
8747 - Stop suggesting that users specify relays by nickname: it isn't a
8748 good idea. Also, properly cross-reference how to specify relays in
8749 all parts of manual documenting options that take a list of
8750 relays. Closes ticket 13381.
8751 - Clarify the HiddenServiceDir option description in manpage to make
8752 it clear that relative paths are taken with respect to the current
8753 working directory. Also clarify that this behavior is not
8754 guaranteed to remain indefinitely. Fixes issue 13913.
8757 - New tests for many parts of channel, relay, and circuitmux
8758 functionality. Code by Andrea; part of 9262.
8759 - New tests for parse_transport_line(). Part of ticket 6456.
8760 - In the unit tests, use chgrp() to change the group of the unit
8761 test temporary directory to the current user, so that the sticky
8762 bit doesn't interfere with tests that check directory groups.
8764 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
8768 Changes in version 0.2.6.1-alpha - 2014-10-30
8769 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
8770 includes numerous code cleanups and new tests, and fixes a large
8771 number of annoying bugs. Out-of-memory conditions are handled better
8772 than in 0.2.5, pluggable transports have improved proxy support, and
8773 clients now use optimistic data for contacting hidden services. Also,
8774 we are now more robust to changes in what we consider a parseable
8775 directory object, so that tightening restrictions does not have a risk
8776 of introducing infinite download loops.
8778 This is the first alpha release in a new series, so expect there to be
8779 bugs. Users who would rather test out a more stable branch should stay
8780 with 0.2.5.x for now.
8782 o New compiler and system requirements:
8783 - Tor 0.2.6.x requires that your compiler support more of the C99
8784 language standard than before. The 'configure' script now detects
8785 whether your compiler supports C99 mid-block declarations and
8786 designated initializers. If it does not, Tor will not compile.
8788 We may revisit this requirement if it turns out that a significant
8789 number of people need to build Tor with compilers that don't
8790 bother implementing a 15-year-old standard. Closes ticket 13233.
8791 - Tor no longer supports systems without threading support. When we
8792 began working on Tor, there were several systems that didn't have
8793 threads, or where the thread support wasn't able to run the
8794 threads of a single process on multiple CPUs. That no longer
8795 holds: every system where Tor needs to run well now has threading
8796 support. Resolves ticket 12439.
8798 o Removed platform support:
8799 - We no longer include special code to build on Windows CE; as far
8800 as we know, nobody has used Tor on Windows CE in a very long time.
8801 Closes ticket 11446.
8803 o Major features (bridges):
8804 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
8805 transports if they are configured via the "TOR_PT_PROXY"
8806 environment variable. Implements proposal 232. Resolves
8809 o Major features (client performance, hidden services):
8810 - Allow clients to use optimistic data when connecting to a hidden
8811 service, which should remove a round-trip from hidden service
8812 initialization. See proposal 181 for details. Implements
8815 o Major features (directory system):
8816 - Upon receiving an unparseable directory object, if its digest
8817 matches what we expected, then don't try to download it again.
8818 Previously, when we got a descriptor we didn't like, we would keep
8819 trying to download it over and over. Closes ticket 11243.
8821 o Major features (sample torrc):
8822 - Add a new, infrequently-changed "torrc.minimal". This file is
8823 similar to torrc.sample, but it will change as infrequently as
8824 possible, for the benefit of users whose systems prompt them for
8825 intervention whenever a default configuration file is changed.
8826 Making this change allows us to update torrc.sample to be a more
8827 generally useful "sample torrc".
8829 o Major bugfixes (directory authorities):
8830 - Do not assign the HSDir flag to relays if they are not Valid, or
8831 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
8833 o Major bugfixes (directory bandwidth performance):
8834 - Don't flush the zlib buffer aggressively when compressing
8835 directory information for clients. This should save about 7% of
8836 the bandwidth currently used for compressed descriptors and
8837 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
8839 o Minor features (security, memory wiping):
8840 - Ensure we securely wipe keys from memory after
8841 crypto_digest_get_digest and init_curve25519_keypair_from_file
8842 have finished using them. Resolves ticket 13477.
8844 o Minor features (security, out-of-memory handling):
8845 - When handling an out-of-memory condition, allocate less memory for
8846 temporary data structures. Fixes issue 10115.
8847 - When handling an out-of-memory condition, consider more types of
8848 buffers, including those on directory connections, and zlib
8849 buffers. Resolves ticket 11792.
8852 - When identity keypair is generated for first time, log a
8853 congratulatory message that links to the new relay lifecycle
8854 document. Implements feature 10427.
8856 o Minor features (client):
8857 - Clients are now willing to send optimistic data (before they
8858 receive a 'connected' cell) to relays of any version. (Relays
8859 without support for optimistic data are no longer supported on the
8860 Tor network.) Resolves ticket 13153.
8862 o Minor features (directory authorities):
8863 - Don't list relays with a bandwidth estimate of 0 in the consensus.
8864 Implements a feature proposed during discussion of bug 13000.
8865 - In tor-gencert, report an error if the user provides the same
8866 argument more than once.
8867 - If a directory authority can't find a best consensus method in the
8868 votes that it holds, it now falls back to its favorite consensus
8869 method. Previously, it fell back to method 1. Neither of these is
8870 likely to get enough signatures, but "fall back to favorite"
8871 doesn't require us to maintain support an obsolete consensus
8872 method. Implements part of proposal 215.
8874 o Minor features (logging):
8875 - On Unix-like systems, you can now use named pipes as the target of
8876 the Log option, and other options that try to append to files.
8877 Closes ticket 12061. Patch from "carlo von lynX".
8878 - When opening a log file at startup, send it every log message that
8879 we generated between startup and opening it. Previously, log
8880 messages that were generated before opening the log file were only
8881 logged to stdout. Closes ticket 6938.
8882 - Add a TruncateLogFile option to overwrite logs instead of
8883 appending to them. Closes ticket 5583.
8885 o Minor features (portability, Solaris):
8886 - Threads are no longer disabled by default on Solaris; we believe
8887 that the versions of Solaris with broken threading support are all
8888 obsolete by now. Resolves ticket 9495.
8890 o Minor features (relay):
8891 - Re-check our address after we detect a changed IP address from
8892 getsockname(). This ensures that the controller command "GETINFO
8893 address" will report the correct value. Resolves ticket 11582.
8895 - A new AccountingRule option lets Relays set whether they'd like
8896 AccountingMax to be applied separately to inbound and outbound
8897 traffic, or applied to the sum of inbound and outbound traffic.
8898 Resolves ticket 961. Patch by "chobe".
8900 o Minor features (testing networks):
8901 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
8902 the "Exit" flag regardless of their uptime, bandwidth, or exit
8903 policy. TestingTorNetwork must be set for this option to have any
8904 effect. Previously, authorities would take up to 35 minutes to
8905 give nodes the Exit flag in a test network. Partially implements
8908 o Minor features (validation):
8909 - Check all date/time values passed to tor_timegm and
8910 parse_rfc1123_time for validity, taking leap years into account.
8911 Improves HTTP header validation. Implemented with bug 13476.
8912 - In correct_tm(), limit the range of values returned by system
8913 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
8914 This means we don't have to deal with negative or too large dates,
8915 even if a clock is wrong. Otherwise we might fail to read a file
8916 written by us which includes such a date. Fixes bug 13476.
8918 o Minor bugfixes (bridge clients):
8919 - When configured to use a bridge without an identity digest (not
8920 recommended), avoid launching an extra channel to it when
8921 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
8923 o Minor bugfixes (bridges):
8924 - When DisableNetwork is set, do not launch pluggable transport
8925 plugins, and if any are running, terminate them. Fixes bug 13213;
8926 bugfix on 0.2.3.6-alpha.
8928 o Minor bugfixes (C correctness):
8929 - Fix several instances of possible integer overflow/underflow/NaN.
8930 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
8932 - In circuit_build_times_calculate_timeout() in circuitstats.c,
8933 avoid dividing by zero in the pareto calculations. This traps
8934 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
8936 - Fix an integer overflow in format_time_interval(). Fixes bug
8937 13393; bugfix on 0.2.0.10-alpha.
8938 - Set the correct day of year value when the system's localtime(_r)
8939 or gmtime(_r) functions fail to set struct tm. Not externally
8940 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
8941 - Avoid unlikely signed integer overflow in tor_timegm on systems
8942 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
8944 o Minor bugfixes (client):
8945 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
8946 BadExit flag are not considered worthy candidates. Fixes bug
8947 13066; bugfix on 0.1.2.3-alpha.
8948 - Use the consensus schedule for downloading consensuses, and not
8949 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
8950 - Handle unsupported or malformed SOCKS5 requests properly by
8951 responding with the appropriate error message before closing the
8952 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
8954 o Minor bugfixes (client, torrc):
8955 - Stop modifying the value of our DirReqStatistics torrc option just
8956 because we're not a bridge or relay. This bug was causing Tor
8957 Browser users to write "DirReqStatistics 0" in their torrc files
8958 as if they had chosen to change the config. Fixes bug 4244; bugfix
8960 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
8961 that our options have changed every time we SIGHUP. Fixes bug
8962 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
8964 o Minor bugfixes (controller):
8965 - Return an error when the second or later arguments of the
8966 "setevents" controller command are invalid events. Previously we
8967 would return success while silently skipping invalid events. Fixes
8968 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
8970 o Minor bugfixes (directory system):
8971 - Always believe that v3 directory authorities serve extra-info
8972 documents, whether they advertise "caches-extra-info" or not.
8973 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8974 - When running as a v3 directory authority, advertise that you serve
8975 extra-info documents so that clients who want them can find them
8976 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8977 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
8978 Previously, directories offering BRIDGE_DIRINFO and some other
8979 flag (i.e. microdescriptors or extrainfo) would be ignored when
8980 looking for bridges. Partially fixes bug 13163; bugfix
8983 o Minor bugfixes (networking):
8984 - Check for orconns and use connection_or_close_for_error() rather
8985 than connection_mark_for_close() directly in the getsockopt()
8986 failure case of connection_handle_write_impl(). Fixes bug 11302;
8987 bugfix on 0.2.4.4-alpha.
8989 o Minor bugfixes (relay):
8990 - When generating our family list, remove spaces from around the
8991 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
8992 - If our previous bandwidth estimate was 0 bytes, allow publishing a
8993 new relay descriptor immediately. Fixes bug 13000; bugfix
8996 o Minor bugfixes (testing networks):
8997 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
8998 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
8999 - Stop using the default authorities in networks which provide both
9000 AlternateDirAuthority and AlternateBridgeAuthority. Partially
9001 fixes bug 13163; bugfix on 0.2.0.13-alpha.
9003 o Minor bugfixes (testing):
9004 - Stop spawn test failures due to a race condition between the
9005 SIGCHLD handler updating the process status, and the test reading
9006 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
9008 o Minor bugfixes (testing, Windows):
9009 - Avoid passing an extra backslash when creating a temporary
9010 directory for running the unit tests on Windows. Fixes bug 12392;
9011 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
9013 o Minor bugfixes (windows):
9014 - Remove code to special-case handling of NTE_BAD_KEYSET when
9015 acquiring windows CryptoAPI context. This error can't actually
9016 occur for the parameters we're providing. Fixes bug 10816; bugfix
9019 o Minor bugfixes (zlib):
9020 - Avoid truncating a zlib stream when trying to finalize it with an
9021 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
9024 - Allow our configure script to build correctly with autoconf 2.62
9025 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
9026 - Improve the error message from ./configure to make it clear that
9027 when asciidoc has not been found, the user will have to either add
9028 --disable-asciidoc argument or install asciidoc. Resolves
9031 o Code simplification and refactoring:
9032 - Change the entry_is_live() function to take named bitfield
9033 elements instead of an unnamed list of booleans. Closes
9035 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
9036 Resolves ticket 12205.
9037 - Use calloc and reallocarray functions instead of multiply-
9038 then-malloc. This makes it less likely for us to fall victim to an
9039 integer overflow attack when allocating. Resolves ticket 12855.
9040 - Use the standard macro name SIZE_MAX, instead of our
9042 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
9043 functions which take them as arguments. Replace 0 with NO_DIRINFO
9044 in a function call for clarity. Seeks to prevent future issues
9046 - Avoid 4 null pointer errors under clang static analysis by using
9047 tor_assert() to prove that the pointers aren't null. Fixes
9049 - Rework the API of policies_parse_exit_policy() to use a bitmask to
9050 represent parsing options, instead of a confusing mess of
9051 booleans. Resolves ticket 8197.
9052 - Introduce a helper function to parse ExitPolicy in
9053 or_options_t structure.
9056 - Add a doc/TUNING document with tips for handling large numbers of
9057 TCP connections when running busy Tor relay. Update the warning
9058 message to point to this file when running out of sockets
9059 operating system is allowing to use simultaneously. Resolves
9063 - We no longer remind the user about configuration options that have
9064 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
9065 - Remove our old, non-weighted bandwidth-based node selection code.
9066 Previously, we used it as a fallback when we couldn't perform
9067 weighted bandwidth-based node selection. But that would only
9068 happen in the cases where we had no consensus, or when we had a
9069 consensus generated by buggy or ancient directory authorities. In
9070 either case, it's better to use the more modern, better maintained
9071 algorithm, with reasonable defaults for the weights. Closes
9073 - Remove the --disable-curve25519 configure option. Relays and
9074 clients now are required to support curve25519 and the
9076 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
9077 used to be deprecated synonyms for "StrictNodes", are now marked
9078 obsolete. Resolves ticket 12226.
9079 - Clients don't understand the BadDirectory flag in the consensus
9080 anymore, and ignore it.
9083 - Refactor the function that chooses guard nodes so that it can more
9084 easily be tested; write some tests for it.
9085 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
9086 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
9087 - Create unit tests for format_time_interval(). With bug 13393.
9088 - Add unit tests for tor_timegm signed overflow, tor_timegm and
9089 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
9090 tests (visible) fixes in bug 13476.
9091 - Add a "coverage-html" make target to generate HTML-visualized
9092 coverage results when building with --enable-coverage. (Requires
9093 lcov.) Patch from Kevin Murray.
9094 - Enable the backtrace handler (where supported) when running the
9096 - Revise all unit tests that used the legacy test_* macros to
9097 instead use the recommended tt_* macros. This patch was generated
9098 with coccinelle, to avoid manual errors. Closes ticket 13119.
9100 o Distribution (systemd):
9101 - systemd unit file: only allow tor to write to /var/lib/tor and
9102 /var/log/tor. The rest of the filesystem is accessible for reading
9103 only. Patch by intrigeri; resolves ticket 12751.
9104 - systemd unit file: ensure that the process and all its children
9105 can never gain new privileges. Patch by intrigeri; resolves
9107 - systemd unit file: set up /var/run/tor as writable for the Tor
9108 service. Patch by intrigeri; resolves ticket 13196.
9110 o Removed features (directory authorities):
9111 - Remove code that prevented authorities from listing Tor relays
9112 affected by CVE-2011-2769 as guards. These relays are already
9113 rejected altogether due to the minimum version requirement of
9114 0.2.3.16-alpha. Closes ticket 13152.
9115 - The "AuthDirRejectUnlisted" option no longer has any effect, as
9116 the fingerprints file (approved-routers) has been deprecated.
9117 - Directory authorities do not support being Naming dirauths anymore.
9118 The "NamingAuthoritativeDir" config option is now obsolete.
9119 - Directory authorities do not support giving out the BadDirectory
9121 - Directory authorities no longer advertise or support consensus
9122 methods 1 through 12 inclusive. These consensus methods were
9123 obsolete and/or insecure: maintaining the ability to support them
9124 served no good purpose. Implements part of proposal 215; closes
9127 o Testing (test-network.sh):
9128 - Stop using "echo -n", as some shells' built-in echo doesn't
9129 support "-n". Instead, use "/bin/echo -n". Partially fixes
9131 - Stop an apparent test-network hang when used with make -j2. Fixes
9133 - Add a --delay option to test-network.sh, which configures the
9134 delay before the chutney network tests for data transmission.
9135 Partially implements ticket 13161.
9138 Changes in version 0.2.5.10 - 2014-10-24
9139 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
9141 It adds several new security features, including improved
9142 denial-of-service resistance for relays, new compiler hardening
9143 options, and a system-call sandbox for hardened installations on Linux
9144 (requires seccomp2). The controller protocol has several new features,
9145 resolving IPv6 addresses should work better than before, and relays
9146 should be a little more CPU-efficient. We've added support for more
9147 OpenBSD and FreeBSD transparent proxy types. We've improved the build
9148 system and testing infrastructure to allow unit testing of more parts
9149 of the Tor codebase. Finally, we've addressed several nagging pluggable
9150 transport usability issues, and included numerous other small bugfixes
9151 and features mentioned below.
9153 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
9154 have accumulated many known flaws; everyone should upgrade.
9156 o Deprecated versions:
9157 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
9158 attention for some while.
9161 Changes in version 0.2.5.9-rc - 2014-10-20
9162 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
9163 series. It disables SSL3 in response to the recent "POODLE" attack
9164 (even though POODLE does not affect Tor). It also works around a crash
9165 bug caused by some operating systems' response to the "POODLE" attack
9166 (which does affect Tor). It also contains a few miscellaneous fixes.
9168 o Major security fixes:
9169 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9170 today support TLS 1.0 or later, so we can safely turn off support
9171 for this old (and insecure) protocol. Fixes bug 13426.
9173 o Major bugfixes (openssl bug workaround):
9174 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9175 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9176 13471. This is a workaround for an OpenSSL bug.
9179 - Disable the sandbox name resolver cache when running tor-resolve:
9180 tor-resolve doesn't use the sandbox code, and turning it on was
9181 breaking attempts to do tor-resolve on a non-default server on
9182 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
9184 o Compilation fixes:
9185 - Build and run correctly on systems like OpenBSD-current that have
9186 patched OpenSSL to remove get_cipher_by_char and/or its
9187 implementations. Fixes issue 13325.
9189 o Downgraded warnings:
9190 - Downgrade the severity of the 'unexpected sendme cell from client'
9191 from 'warn' to 'protocol warning'. Closes ticket 8093.
9194 Changes in version 0.2.4.25 - 2014-10-20
9195 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
9196 (even though POODLE does not affect Tor). It also works around a crash
9197 bug caused by some operating systems' response to the "POODLE" attack
9198 (which does affect Tor).
9200 o Major security fixes (also in 0.2.5.9-rc):
9201 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9202 today support TLS 1.0 or later, so we can safely turn off support
9203 for this old (and insecure) protocol. Fixes bug 13426.
9205 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
9206 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9207 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9208 13471. This is a workaround for an OpenSSL bug.
9211 Changes in version 0.2.5.8-rc - 2014-09-22
9212 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
9213 series. It fixes a bug that affects consistency and speed when
9214 connecting to hidden services, and it updates the location of one of
9215 the directory authorities.
9218 - Clients now send the correct address for their chosen rendezvous
9219 point when trying to access a hidden service. They used to send
9220 the wrong address, which would still work some of the time because
9221 they also sent the identity digest of the rendezvous point, and if
9222 the hidden service happened to try connecting to the rendezvous
9223 point from a relay that already had a connection open to it,
9224 the relay would reuse that connection. Now connections to hidden
9225 services should be more robust and faster. Also, this bug meant
9226 that clients were leaking to the hidden service whether they were
9227 on a little-endian (common) or big-endian (rare) system, which for
9228 some users might have reduced their anonymity. Fixes bug 13151;
9229 bugfix on 0.2.1.5-alpha.
9231 o Directory authority changes:
9232 - Change IP address for gabelmoo (v3 directory authority).
9235 Changes in version 0.2.4.24 - 2014-09-22
9236 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
9237 connecting to hidden services, and it updates the location of one of
9238 the directory authorities.
9241 - Clients now send the correct address for their chosen rendezvous
9242 point when trying to access a hidden service. They used to send
9243 the wrong address, which would still work some of the time because
9244 they also sent the identity digest of the rendezvous point, and if
9245 the hidden service happened to try connecting to the rendezvous
9246 point from a relay that already had a connection open to it,
9247 the relay would reuse that connection. Now connections to hidden
9248 services should be more robust and faster. Also, this bug meant
9249 that clients were leaking to the hidden service whether they were
9250 on a little-endian (common) or big-endian (rare) system, which for
9251 some users might have reduced their anonymity. Fixes bug 13151;
9252 bugfix on 0.2.1.5-alpha.
9254 o Directory authority changes:
9255 - Change IP address for gabelmoo (v3 directory authority).
9257 o Minor features (geoip):
9258 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9262 Changes in version 0.2.5.7-rc - 2014-09-11
9263 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
9264 release series, and some long-standing bugs related to ORPort reachability
9265 testing and failure to send CREATE cells. It is the first release
9266 candidate for the Tor 0.2.5.x series.
9268 o Major bugfixes (client, startup):
9269 - Start making circuits as soon as DisabledNetwork is turned off.
9270 When Tor started with DisabledNetwork set, it would correctly
9271 conclude that it shouldn't build circuits, but it would mistakenly
9272 cache this conclusion, and continue believing it even when
9273 DisableNetwork is set to 0. Fixes the bug introduced by the fix
9274 for bug 11200; bugfix on 0.2.5.4-alpha.
9275 - Resume expanding abbreviations for command-line options. The fix
9276 for bug 4647 accidentally removed our hack from bug 586 that
9277 rewrote HashedControlPassword to __HashedControlSessionPassword
9278 when it appears on the commandline (which allowed the user to set
9279 her own HashedControlPassword in the torrc file while the
9280 controller generates a fresh session password for each run). Fixes
9281 bug 12948; bugfix on 0.2.5.1-alpha.
9282 - Warn about attempts to run hidden services and relays in the same
9283 process: that's probably not a good idea. Closes ticket 12908.
9285 o Major bugfixes (relay):
9286 - Avoid queuing or sending destroy cells for circuit ID zero when we
9287 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
9288 Found and fixed by "cypherpunks".
9289 - Fix ORPort reachability detection on relays running behind a
9290 proxy, by correctly updating the "local" mark on the controlling
9291 channel when changing the address of an or_connection_t after the
9292 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
9294 o Minor features (bridge):
9295 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
9296 cookie file for the ExtORPort g+r by default.
9298 o Minor features (geoip):
9299 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9302 o Minor bugfixes (logging):
9303 - Reduce the log severity of the "Pluggable transport proxy does not
9304 provide any needed transports and will not be launched." message,
9305 since Tor Browser includes several ClientTransportPlugin lines in
9306 its torrc-defaults file, leading every Tor Browser user who looks
9307 at her logs to see these notices and wonder if they're dangerous.
9308 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
9309 - Downgrade "Unexpected onionskin length after decryption" warning
9310 to a protocol-warn, since there's nothing relay operators can do
9311 about a client that sends them a malformed create cell. Resolves
9312 bug 12996; bugfix on 0.0.6rc1.
9313 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
9314 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
9315 - When logging information about an EXTEND2 or EXTENDED2 cell, log
9316 their names correctly. Fixes part of bug 12700; bugfix
9318 - When logging information about a relay cell whose command we don't
9319 recognize, log its command as an integer. Fixes part of bug 12700;
9320 bugfix on 0.2.1.10-alpha.
9321 - Escape all strings from the directory connection before logging
9322 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
9324 o Minor bugfixes (controller):
9325 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
9326 bug 12864; bugfix on 0.2.5.1-alpha.
9327 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
9328 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
9331 o Minor bugfixes (compilation):
9332 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
9333 bugfix on 0.2.5.5-alpha.
9334 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
9335 0.2.5.1-alpha. Patch from "NewEraCracker".
9336 - In routerlist_assert_ok(), don't take the address of a
9337 routerinfo's cache_info member unless that routerinfo is non-NULL.
9338 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
9339 - Fix a large number of false positive warnings from the clang
9340 analyzer static analysis tool. This should make real warnings
9341 easier for clang analyzer to find. Patch from "teor". Closes
9344 o Distribution (systemd):
9345 - Verify configuration file via ExecStartPre in the systemd unit
9346 file. Patch from intrigeri; resolves ticket 12730.
9347 - Explicitly disable RunAsDaemon in the systemd unit file. Our
9348 current systemd unit uses "Type = simple", so systemd does not
9349 expect tor to fork. If the user has "RunAsDaemon 1" in their
9350 torrc, then things won't work as expected. This is e.g. the case
9351 on Debian (and derivatives), since there we pass "--defaults-torrc
9352 /usr/share/tor/tor-service-defaults-torrc" (that contains
9353 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
9357 - Adjust the URLs in the README to refer to the new locations of
9358 several documents on the website. Fixes bug 12830. Patch from
9360 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
9364 Changes in version 0.2.5.6-alpha - 2014-07-28
9365 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
9366 risk from guard rotation, and fixes a variety of other issues to get
9367 us closer to a release candidate.
9369 o Major features (also in 0.2.4.23):
9370 - Make the number of entry guards configurable via a new
9371 NumEntryGuards consensus parameter, and the number of directory
9372 guards configurable via a new NumDirectoryGuards consensus
9373 parameter. Implements ticket 12688.
9375 o Major bugfixes (also in 0.2.4.23):
9376 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
9377 implementation that caused incorrect results on 32-bit
9378 implementations when certain malformed inputs were used along with
9379 a small class of private ntor keys. This bug does not currently
9380 appear to allow an attacker to learn private keys or impersonate a
9381 Tor server, but it could provide a means to distinguish 32-bit Tor
9382 implementations from 64-bit Tor implementations. Fixes bug 12694;
9383 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
9387 - Perform circuit cleanup operations even when circuit
9388 construction operations are disabled (because the network is
9389 disabled, or because there isn't enough directory information).
9390 Previously, when we were not building predictive circuits, we
9391 were not closing expired circuits either. Fixes bug 8387; bugfix on
9392 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
9393 became more strict about when we have "enough directory information
9397 - Authorities now assign the Guard flag to the fastest 25% of the
9398 network (it used to be the fastest 50%). Also raise the consensus
9399 weight that guarantees the Guard flag from 250 to 2000. For the
9400 current network, this results in about 1100 guards, down from 2500.
9401 This step paves the way for moving the number of entry guards
9402 down to 1 (proposal 236) while still providing reasonable expected
9403 performance for most users. Implements ticket 12690.
9404 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
9406 - Slightly enhance the diagnostic message for bug 12184.
9408 o Minor bugfixes (also in 0.2.4.23):
9409 - Warn and drop the circuit if we receive an inbound 'relay early'
9410 cell. Those used to be normal to receive on hidden service circuits
9411 due to bug 1038, but the buggy Tor versions are long gone from
9412 the network so we can afford to resume watching for them. Resolves
9413 the rest of bug 1038; bugfix on 0.2.1.19.
9414 - Correct a confusing error message when trying to extend a circuit
9415 via the control protocol but we don't know a descriptor or
9416 microdescriptor for one of the specified relays. Fixes bug 12718;
9417 bugfix on 0.2.3.1-alpha.
9420 - Fix compilation when building with bufferevents enabled. (This
9421 configuration is still not expected to work, however.)
9422 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
9423 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
9425 - Compile correctly with builds and forks of OpenSSL (such as
9426 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
9427 0.2.1.1-alpha. Patch from "dhill".
9430 Changes in version 0.2.4.23 - 2014-07-28
9431 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
9432 guard rotation, and also backports several important fixes from the
9433 Tor 0.2.5 alpha release series.
9436 - Clients now look at the "usecreatefast" consensus parameter to
9437 decide whether to use CREATE_FAST or CREATE cells for the first hop
9438 of their circuit. This approach can improve security on connections
9439 where Tor's circuit handshake is stronger than the available TLS
9440 connection security levels, but the tradeoff is more computational
9441 load on guard relays. Implements proposal 221. Resolves ticket 9386.
9442 - Make the number of entry guards configurable via a new
9443 NumEntryGuards consensus parameter, and the number of directory
9444 guards configurable via a new NumDirectoryGuards consensus
9445 parameter. Implements ticket 12688.
9448 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
9449 implementation that caused incorrect results on 32-bit
9450 implementations when certain malformed inputs were used along with
9451 a small class of private ntor keys. This bug does not currently
9452 appear to allow an attacker to learn private keys or impersonate a
9453 Tor server, but it could provide a means to distinguish 32-bit Tor
9454 implementations from 64-bit Tor implementations. Fixes bug 12694;
9455 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
9459 - Warn and drop the circuit if we receive an inbound 'relay early'
9460 cell. Those used to be normal to receive on hidden service circuits
9461 due to bug 1038, but the buggy Tor versions are long gone from
9462 the network so we can afford to resume watching for them. Resolves
9463 the rest of bug 1038; bugfix on 0.2.1.19.
9464 - Correct a confusing error message when trying to extend a circuit
9465 via the control protocol but we don't know a descriptor or
9466 microdescriptor for one of the specified relays. Fixes bug 12718;
9467 bugfix on 0.2.3.1-alpha.
9468 - Avoid an illegal read from stack when initializing the TLS
9469 module using a version of OpenSSL without all of the ciphers
9470 used by the v2 link handshake. Fixes bug 12227; bugfix on
9471 0.2.4.8-alpha. Found by "starlight".
9474 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
9478 Changes in version 0.2.5.5-alpha - 2014-06-18
9479 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
9480 0.2.5.x release series, including a couple of DoS issues, some
9481 performance regressions, a large number of bugs affecting the Linux
9482 seccomp2 sandbox code, and various other bugfixes. It also adds
9483 diagnostic bugfixes for a few tricky issues that we're trying to
9486 o Major features (security, traffic analysis resistance):
9487 - Several major improvements to the algorithm used to decide when to
9488 close TLS connections. Previous versions of Tor closed connections
9489 at a fixed interval after the last time a non-padding cell was
9490 sent over the connection, regardless of the target of the
9491 connection. Now, we randomize the intervals by adding up to 50% of
9492 their base value, we measure the length of time since connection
9493 last had at least one circuit, and we allow connections to known
9494 ORs to remain open a little longer (15 minutes instead of 3
9495 minutes minimum). These changes should improve Tor's resistance
9496 against some kinds of traffic analysis, and lower some overhead
9497 from needlessly closed connections. Fixes ticket 6799.
9498 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
9500 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
9501 - Fix a memory leak that could occur if a microdescriptor parse
9502 fails during the tokenizing step. This bug could enable a memory
9503 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9506 o Major bugfixes (security, directory authorities):
9507 - Directory authorities now include a digest of each relay's
9508 identity key as a part of its microdescriptor.
9510 This is a workaround for bug 11743 (reported by "cypherpunks"),
9511 where Tor clients do not support receiving multiple
9512 microdescriptors with the same SHA256 digest in the same
9513 consensus. When clients receive a consensus like this, they only
9514 use one of the relays. Without this fix, a hostile relay could
9515 selectively disable some client use of target relays by
9516 constructing a router descriptor with a different identity and the
9517 same microdescriptor parameters and getting the authorities to
9518 list it in a microdescriptor consensus. This fix prevents an
9519 attacker from causing a microdescriptor collision, because the
9520 router's identity is not forgeable.
9522 o Major bugfixes (relay):
9523 - Use a direct dirport connection when uploading non-anonymous
9524 descriptors to the directory authorities. Previously, relays would
9525 incorrectly use tunnel connections under a fairly wide variety of
9526 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
9527 - When a circuit accidentally has the same circuit ID for its
9528 forward and reverse direction, correctly detect the direction of
9529 cells using that circuit. Previously, this bug made roughly one
9530 circuit in a million non-functional. Fixes bug 12195; this is a
9531 bugfix on every version of Tor.
9533 o Major bugfixes (client, pluggable transports):
9534 - When managing pluggable transports, use OS notification facilities
9535 to learn if they have crashed, and don't attempt to kill any
9536 process that has already exited. Fixes bug 8746; bugfix
9539 o Minor features (diagnostic):
9540 - When logging a warning because of bug 7164, additionally check the
9541 hash table for consistency (as proposed on ticket 11737). This may
9542 help diagnose bug 7164.
9543 - When we log a heartbeat, log how many one-hop circuits we have
9544 that are at least 30 minutes old, and log status information about
9545 a few of them. This is an attempt to track down bug 8387.
9546 - When encountering an unexpected CR while writing text to a file on
9547 Windows, log the name of the file. Should help diagnosing
9549 - Give more specific warnings when a client notices that an onion
9550 handshake has failed. Fixes ticket 9635.
9551 - Add significant new logging code to attempt to diagnose bug 12184,
9552 where relays seem to run out of available circuit IDs.
9553 - Improve the diagnostic log message for bug 8387 even further to
9554 try to improve our odds of figuring out why one-hop directory
9555 circuits sometimes do not get closed.
9557 o Minor features (security, memory management):
9558 - Memory allocation tricks (mempools and buffer freelists) are now
9559 disabled by default. You can turn them back on with
9560 --enable-mempools and --enable-buf-freelists respectively. We're
9561 disabling these features because malloc performance is good enough
9562 on most platforms, and a similar feature in OpenSSL exacerbated
9563 exploitation of the Heartbleed attack. Resolves ticket 11476.
9565 o Minor features (security):
9566 - Apply the secure SipHash-2-4 function to the hash table mapping
9567 circuit IDs and channels to circuits. We missed this one when we
9568 were converting all the other hash functions to use SipHash back
9569 in 0.2.5.3-alpha. Resolves ticket 11750.
9571 o Minor features (build):
9572 - The configure script has a --disable-seccomp option to turn off
9573 support for libseccomp on systems that have it, in case it (or
9574 Tor's use of it) is broken. Resolves ticket 11628.
9576 o Minor features (other):
9577 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
9580 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
9581 - When running a hidden service, do not allow TunneledDirConns 0;
9582 this will keep the hidden service from running, and also
9583 make it publish its descriptors directly over HTTP. Fixes bug 10849;
9584 bugfix on 0.2.1.1-alpha.
9586 o Minor bugfixes (performance):
9587 - Avoid a bug where every successful connection made us recompute
9588 the flag telling us whether we have sufficient information to
9589 build circuits. Previously, we would forget our cached value
9590 whenever we successfully opened a channel (or marked a router as
9591 running or not running for any other reason), regardless of
9592 whether we had previously believed the router to be running. This
9593 forced us to run an expensive update operation far too often.
9594 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
9595 - Avoid using tor_memeq() for checking relay cell integrity. This
9596 removes a possible performance bottleneck. Fixes part of bug
9597 12169; bugfix on 0.2.1.31.
9599 o Minor bugfixes (compilation):
9600 - Fix compilation of test_status.c when building with MVSC. Bugfix
9601 on 0.2.5.4-alpha. Patch from Gisle Vanem.
9602 - Resolve GCC complaints on OpenBSD about discarding constness in
9603 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
9604 on 0.1.1.23. Patch from Dana Koch.
9605 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
9606 treatment of long and time_t as comparable types. Fixes part of
9607 bug 11633. Patch from Dana Koch.
9608 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
9609 11623; bugfix on 0.2.5.3-alpha.
9610 - When deciding whether to build the 64-bit curve25519
9611 implementation, detect platforms where we can compile 128-bit
9612 arithmetic but cannot link it. Fixes bug 11729; bugfix on
9613 0.2.4.8-alpha. Patch from "conradev".
9614 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
9615 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
9616 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
9619 o Minor bugfixes (Directory server):
9620 - When sending a compressed set of descriptors or microdescriptors,
9621 make sure to finalize the zlib stream. Previously, we would write
9622 all the compressed data, but if the last descriptor we wanted to
9623 send was missing or too old, we would not mark the stream as
9624 finished. This caused problems for decompression tools. Fixes bug
9625 11648; bugfix on 0.1.1.23.
9627 o Minor bugfixes (Linux seccomp sandbox):
9628 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
9629 11622; bugfix on 0.2.5.1-alpha.
9630 - Avoid crashing when re-opening listener ports with the seccomp
9631 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
9632 - Avoid crashing with the seccomp sandbox enabled along with
9633 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
9634 - When we receive a SIGHUP with the sandbox enabled, correctly
9635 support rotating our log files. Fixes bug 12032; bugfix
9637 - Avoid crash when running with sandboxing enabled and
9638 DirReqStatistics not disabled. Fixes bug 12035; bugfix
9640 - Fix a "BUG" warning when trying to write bridge-stats files with
9641 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
9643 - Prevent the sandbox from crashing on startup when run with the
9644 --enable-expensive-hardening configuration option. Fixes bug
9645 11477; bugfix on 0.2.5.4-alpha.
9646 - When running with DirPortFrontPage and sandboxing both enabled,
9647 reload the DirPortFrontPage correctly when restarting. Fixes bug
9648 12028; bugfix on 0.2.5.1-alpha.
9649 - Don't try to enable the sandbox when using the Tor binary to check
9650 its configuration, hash a passphrase, or so on. Doing so was
9651 crashing on startup for some users. Fixes bug 11609; bugfix
9653 - Avoid warnings when running with sandboxing and node statistics
9654 enabled at the same time. Fixes part of 12064; bugfix on
9655 0.2.5.1-alpha. Patch from Michael Wolf.
9656 - Avoid warnings when running with sandboxing enabled at the same
9657 time as cookie authentication, hidden services, or directory
9658 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
9659 - Do not allow options that require calls to exec to be enabled
9660 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
9661 bug 12043; bugfix on 0.2.5.1-alpha.
9662 - Handle failures in getpwnam()/getpwuid() when running with the
9663 User option set and the Linux syscall sandbox enabled. Fixes bug
9664 11946; bugfix on 0.2.5.1-alpha.
9665 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
9666 to avoid calling getaddrinfo() after installing the sandbox
9667 filters. Previously, it preloaded a cache with the IPv4 address
9668 for our hostname, and nothing else. Now, it loads the cache with
9669 every address that it used to initialize the Tor process. Fixes
9670 bug 11970; bugfix on 0.2.5.1-alpha.
9672 o Minor bugfixes (pluggable transports):
9673 - Enable the ExtORPortCookieAuthFile option, to allow changing the
9674 default location of the authentication token for the extended OR
9675 Port as used by sever-side pluggable transports. We had
9676 implemented this option before, but the code to make it settable
9677 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
9678 - Avoid another 60-second delay when starting Tor in a pluggable-
9679 transport-using configuration when we already have cached
9680 descriptors for our bridges. Fixes bug 11965; bugfix
9683 o Minor bugfixes (client):
9684 - Avoid "Tried to open a socket with DisableNetwork set" warnings
9685 when starting a client with bridges configured and DisableNetwork
9686 set. (Tor launcher starts Tor with DisableNetwork set the first
9687 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
9689 o Minor bugfixes (testing):
9690 - The Python parts of the test scripts now work on Python 3 as well
9691 as Python 2, so systems where '/usr/bin/python' is Python 3 will
9692 no longer have the tests break. Fixes bug 11608; bugfix
9694 - When looking for versions of python that we could run the tests
9695 with, check for "python2.7" and "python3.3"; previously we were
9696 only looking for "python", "python2", and "python3". Patch from
9697 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
9698 - Fix all valgrind warnings produced by the unit tests. There were
9699 over a thousand memory leak warnings previously, mostly produced
9700 by forgetting to free things in the unit test code. Fixes bug
9701 11618, bugfixes on many versions of Tor.
9703 o Minor bugfixes (tor-fw-helper):
9704 - Give a correct log message when tor-fw-helper fails to launch.
9705 (Previously, we would say something like "tor-fw-helper sent us a
9706 string we could not parse".) Fixes bug 9781; bugfix
9709 o Minor bugfixes (relay, threading):
9710 - Check return code on spawn_func() in cpuworker code, so that we
9711 don't think we've spawned a nonworking cpuworker and write junk to
9712 it forever. Fix related to bug 4345; bugfix on all released Tor
9713 versions. Found by "skruffy".
9714 - Use a pthread_attr to make sure that spawn_func() cannot return an
9715 error while at the same time launching a thread. Fix related to
9716 bug 4345; bugfix on all released Tor versions. Reported
9719 o Minor bugfixes (relay, oom prevention):
9720 - Correctly detect the total available system memory. We tried to do
9721 this in 0.2.5.4-alpha, but the code was set up to always return an
9722 error value, even on success. Fixes bug 11805; bugfix
9725 o Minor bugfixes (relay, other):
9726 - We now drop CREATE cells for already-existent circuit IDs and for
9727 zero-valued circuit IDs, regardless of other factors that might
9728 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
9730 - Avoid an illegal read from stack when initializing the TLS module
9731 using a version of OpenSSL without all of the ciphers used by the
9732 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
9734 - When rejecting DATA cells for stream_id zero, still count them
9735 against the circuit's deliver window so that we don't fail to send
9736 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
9738 o Minor bugfixes (logging):
9739 - Fix a misformatted log message about delayed directory fetches.
9740 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
9741 - Squelch a spurious LD_BUG message "No origin circuit for
9742 successful SOCKS stream" in certain hidden service failure cases;
9746 - Include a tor.service file in contrib/dist for use with systemd.
9747 Some distributions will be able to use this file unmodified;
9748 others will need to tweak it, or write their own. Patch from Jamie
9749 Nguyen; resolves ticket 8368.
9752 - Clean up several option names in the manpage to match their real
9753 names, add the missing documentation for a couple of testing and
9754 directory authority options, remove the documentation for a
9755 V2-directory fetching option that no longer exists. Resolves
9757 - Correct the documenation so that it lists the correct directory
9758 for the stats files. (They are in a subdirectory called "stats",
9760 - In the manpage, move more authority-only options into the
9761 directory authority section so that operators of regular directory
9762 caches don't get confused.
9765 - The contrib directory has been sorted and tidied. Before, it was
9766 an unsorted dumping ground for useful and not-so-useful things.
9767 Now, it is divided based on functionality, and the items which
9768 seemed to be nonfunctional or useless have been removed. Resolves
9769 ticket 8966; based on patches from "rl1987".
9772 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
9773 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
9774 - The TunnelDirConns and PreferTunnelledDirConns options no longer
9775 exist; tunneled directory connections have been available since
9776 0.1.2.5-alpha, and turning them off is not a good idea. This is a
9777 brute-force fix for 10849, where "TunnelDirConns 0" would break
9781 Changes in version 0.2.4.22 - 2014-05-16
9782 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
9783 alpha release series. These include blocking all authority signing
9784 keys that may have been affected by the OpenSSL "heartbleed" bug,
9785 choosing a far more secure set of TLS ciphersuites by default, closing
9786 a couple of memory leaks that could be used to run a target relay out
9787 of RAM, and several others.
9789 o Major features (security, backport from 0.2.5.4-alpha):
9790 - Block authority signing keys that were used on authorities
9791 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9792 don't have any evidence that these keys _were_ compromised; we're
9793 doing this to be prudent.) Resolves ticket 11464.
9795 o Major bugfixes (security, OOM):
9796 - Fix a memory leak that could occur if a microdescriptor parse
9797 fails during the tokenizing step. This bug could enable a memory
9798 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9801 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
9802 - The relay ciphersuite list is now generated automatically based on
9803 uniform criteria, and includes all OpenSSL ciphersuites with
9804 acceptable strength and forward secrecy. Previously, we had left
9805 some perfectly fine ciphersuites unsupported due to omission or
9806 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9807 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9808 - Relays now trust themselves to have a better view than clients of
9809 which TLS ciphersuites are better than others. (Thanks to bug
9810 11513, the relay list is now well-considered, whereas the client
9811 list has been chosen mainly for anti-fingerprinting purposes.)
9812 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9813 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9814 AES128. Resolves ticket 11528.
9815 - Clients now try to advertise the same list of ciphersuites as
9816 Firefox 28. This change enables selection of (fast) GCM
9817 ciphersuites, disables some strange old ciphers, and stops
9818 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9819 Resolves ticket 11438.
9821 o Minor bugfixes (configuration, security):
9822 - When running a hidden service, do not allow TunneledDirConns 0:
9823 trying to set that option together with a hidden service would
9824 otherwise prevent the hidden service from running, and also make
9825 it publish its descriptors directly over HTTP. Fixes bug 10849;
9826 bugfix on 0.2.1.1-alpha.
9828 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
9829 - Avoid sending a garbage value to the controller when a circuit is
9830 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9832 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
9833 - Stop leaking memory when we successfully resolve a PTR record.
9834 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9836 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
9837 - Avoid 60-second delays in the bootstrapping process when Tor is
9838 launching for a second time while using bridges. Fixes bug 9229;
9839 bugfix on 0.2.0.3-alpha.
9841 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
9842 - Give the correct URL in the warning message when trying to run a
9843 relay on an ancient version of Windows. Fixes bug 9393.
9845 o Minor bugfixes (compilation):
9846 - Fix a compilation error when compiling with --disable-curve25519.
9847 Fixes bug 9700; bugfix on 0.2.4.17-rc.
9850 - Downgrade the warning severity for the the "md was still
9851 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
9852 for trying to diagnose this bug, and the current warning in
9853 earlier versions of tor achieves nothing useful. Addresses warning
9856 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
9857 - When we run out of usable circuit IDs on a channel, log only one
9858 warning for the whole channel, and describe how many circuits
9859 there were on the channel. Fixes part of ticket 11553.
9861 o Minor features (security, backport from 0.2.5.4-alpha):
9862 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
9863 leave the default at 8GBytes), to better support Raspberry Pi
9864 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
9866 o Documentation (backport from 0.2.5.4-alpha):
9867 - Correctly document that we search for a system torrc file before
9868 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
9872 Changes in version 0.2.5.4-alpha - 2014-04-25
9873 Tor 0.2.5.4-alpha includes several security and performance
9874 improvements for clients and relays, including blacklisting authority
9875 signing keys that were used while susceptible to the OpenSSL
9876 "heartbleed" bug, fixing two expensive functions on busy relays,
9877 improved TLS ciphersuite preference lists, support for run-time
9878 hardening on compilers that support AddressSanitizer, and more work on
9879 the Linux sandbox code.
9881 There are also several usability fixes for clients (especially clients
9882 that use bridges), two new TransPort protocols supported (one on
9883 OpenBSD, one on FreeBSD), and various other bugfixes.
9885 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
9886 have accumulated many known flaws; everyone should upgrade.
9888 o Major features (security):
9889 - If you don't specify MaxMemInQueues yourself, Tor now tries to
9890 pick a good value based on your total system memory. Previously,
9891 the default was always 8 GB. You can still override the default by
9892 setting MaxMemInQueues yourself. Resolves ticket 11396.
9893 - Block authority signing keys that were used on authorities
9894 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9895 don't have any evidence that these keys _were_ compromised; we're
9896 doing this to be prudent.) Resolves ticket 11464.
9898 o Major features (relay performance):
9899 - Speed up server-side lookups of rendezvous and introduction point
9900 circuits by using hashtables instead of linear searches. These
9901 functions previously accounted between 3 and 7% of CPU usage on
9902 some busy relays. Resolves ticket 9841.
9903 - Avoid wasting CPU when extending a circuit over a channel that is
9904 nearly out of circuit IDs. Previously, we would do a linear scan
9905 over possible circuit IDs before finding one or deciding that we
9906 had exhausted our possibilities. Now, we try at most 64 random
9907 circuit IDs before deciding that we probably won't succeed. Fixes
9908 a possible root cause of ticket 11553.
9910 o Major features (seccomp2 sandbox, Linux only):
9911 - The seccomp2 sandbox can now run a test network for multiple hours
9912 without crashing. The sandbox is still experimental, and more bugs
9913 will probably turn up. To try it, enable "Sandbox 1" on a Linux
9914 host. Resolves ticket 11351.
9915 - Strengthen sandbox code: the sandbox can now test the arguments
9916 for rename(), and blocks _sysctl() entirely. Resolves another part
9918 - When the sandbox blocks a system call, it now tries to log a stack
9919 trace before exiting. Resolves ticket 11465.
9921 o Major bugfixes (TLS cipher selection):
9922 - The relay ciphersuite list is now generated automatically based on
9923 uniform criteria, and includes all OpenSSL ciphersuites with
9924 acceptable strength and forward secrecy. Previously, we had left
9925 some perfectly fine ciphersuites unsupported due to omission or
9926 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9927 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9928 - Relays now trust themselves to have a better view than clients of
9929 which TLS ciphersuites are better than others. (Thanks to bug
9930 11513, the relay list is now well-considered, whereas the client
9931 list has been chosen mainly for anti-fingerprinting purposes.)
9932 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9933 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9934 AES128. Resolves ticket 11528.
9935 - Clients now try to advertise the same list of ciphersuites as
9936 Firefox 28. This change enables selection of (fast) GCM
9937 ciphersuites, disables some strange old ciphers, and stops
9938 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9939 Resolves ticket 11438.
9941 o Major bugfixes (bridge client):
9942 - Avoid 60-second delays in the bootstrapping process when Tor is
9943 launching for a second time while using bridges. Fixes bug 9229;
9944 bugfix on 0.2.0.3-alpha.
9946 o Minor features (transparent proxy, *BSD):
9947 - Support FreeBSD's ipfw firewall interface for TransPort ports on
9948 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
9949 10267; patch from "yurivict".
9950 - Support OpenBSD's divert-to rules with the pf firewall for
9951 transparent proxy ports. To enable it, set "TransProxyType
9952 pf-divert". This allows Tor to run a TransPort transparent proxy
9953 port on OpenBSD 4.4 or later without root privileges. See the
9954 pf.conf(5) manual page for information on configuring pf to use
9955 divert-to rules. Closes ticket 10896; patch from Dana Koch.
9957 o Minor features (security):
9958 - New --enable-expensive-hardening option to enable security
9959 hardening options that consume nontrivial amounts of CPU and
9960 memory. Right now, this includes AddressSanitizer and UbSan, which
9961 are supported in newer versions of GCC and Clang. Closes ticket
9964 o Minor features (log verbosity):
9965 - Demote the message that we give when a flushing connection times
9966 out for too long from NOTICE to INFO. It was usually meaningless.
9967 Resolves ticket 5286.
9968 - Don't log so many notice-level bootstrapping messages at startup
9969 about downloading descriptors. Previously, we'd log a notice
9970 whenever we learned about more routers. Now, we only log a notice
9971 at every 5% of progress. Fixes bug 9963.
9972 - Warn less verbosely when receiving a malformed
9973 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
9974 - When we run out of usable circuit IDs on a channel, log only one
9975 warning for the whole channel, and describe how many circuits
9976 there were on the channel. Fixes part of ticket 11553.
9978 o Minor features (relay):
9979 - If a circuit timed out for at least 3 minutes, check if we have a
9980 new external IP address, and publish a new descriptor with the new
9981 IP address if it changed. Resolves ticket 2454.
9983 o Minor features (controller):
9984 - Make the entire exit policy available from the control port via
9985 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
9987 - Because of the fix for ticket 11396, the real limit for memory
9988 usage may no longer match the configured MaxMemInQueues value. The
9989 real limit is now exposed via GETINFO limits/max-mem-in-queues.
9991 o Minor features (bridge client):
9992 - Report a more useful failure message when we can't connect to a
9993 bridge because we don't have the right pluggable transport
9994 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
9996 o Minor features (diagnostic):
9997 - Add more log messages to diagnose bug 7164, which causes
9998 intermittent "microdesc_free() called but md was still referenced"
9999 warnings. We now include more information, to figure out why we
10000 might be cleaning a microdescriptor for being too old if it's
10001 still referenced by a live node_t object.
10003 o Minor bugfixes (client, DNSPort):
10004 - When using DNSPort, try to respond to AAAA requests with AAAA
10005 answers. Previously, we hadn't looked at the request type when
10006 deciding which answer type to prefer. Fixes bug 10468; bugfix on
10008 - When receiving a DNS query for an unsupported record type, reply
10009 with no answer rather than with a NOTIMPL error. This behavior
10010 isn't correct either, but it will break fewer client programs, we
10011 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
10014 o Minor bugfixes (exit relay):
10015 - Stop leaking memory when we successfully resolve a PTR record.
10016 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
10018 o Minor bugfixes (bridge client):
10019 - Stop accepting bridge lines containing hostnames. Doing so would
10020 cause clients to perform DNS requests on the hostnames, which was
10021 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
10022 - Avoid a 60-second delay in the bootstrapping process when a Tor
10023 client with pluggable transports re-reads its configuration at
10024 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
10026 o Minor bugfixes (client, logging during bootstrap):
10027 - Warn only once if we start logging in an unsafe way. Previously,
10028 we complain as many times as we had problems. Fixes bug 9870;
10029 bugfix on 0.2.5.1-alpha.
10030 - Only report the first fatal bootstrap error on a given OR
10031 connection. This stops us from telling the controller bogus error
10032 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
10033 - Be more helpful when trying to run sandboxed on Linux without
10034 libseccomp. Instead of saying "Sandbox is not implemented on this
10035 platform", we now explain that we need to be built with
10036 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
10037 - Avoid generating spurious warnings when starting with
10038 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
10041 o Minor bugfixes (closing OR connections):
10042 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
10043 check if it's an or_connection_t and correctly call
10044 connection_or_close_for_error() rather than
10045 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
10047 - When closing all connections on setting DisableNetwork to 1, use
10048 connection_or_close_normally() rather than closing OR connections
10049 out from under the channel layer. Fixes bug 11306; bugfix on
10052 o Minor bugfixes (controller):
10053 - Avoid sending a garbage value to the controller when a circuit is
10054 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
10056 o Minor bugfixes (tor-fw-helper):
10057 - Allow tor-fw-helper to build again by adding src/ext to its
10058 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
10060 o Minor bugfixes (bridges):
10061 - Avoid potential crashes or bad behavior when launching a
10062 server-side managed proxy with ORPort or ExtORPort temporarily
10063 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
10065 o Minor bugfixes (platform-specific):
10066 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
10067 bug 11426; bugfix on 0.2.5.3-alpha.
10068 - When dumping a malformed directory object to disk, save it in
10069 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
10071 - Don't report failures from make_socket_reuseable() on incoming
10072 sockets on OSX: this can happen when incoming connections close
10073 early. Fixes bug 10081.
10075 o Minor bugfixes (trivial memory leaks):
10076 - Fix a small memory leak when signing a directory object. Fixes bug
10077 11275; bugfix on 0.2.4.13-alpha.
10078 - Free placeholder entries in our circuit table at exit; fixes a
10079 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
10080 - Don't re-initialize a second set of OpenSSL mutexes when starting
10081 up. Previously, we'd make one set of mutexes, and then immediately
10082 replace them with another. Fixes bug 11726; bugfix on
10084 - Resolve some memory leaks found by coverity in the unit tests, on
10085 exit in tor-gencert, and on a failure to compute digests for our
10086 own keys when generating a v3 networkstatus vote. These leaks
10087 should never have affected anyone in practice.
10089 o Minor bugfixes (hidden service):
10090 - Only retry attempts to connect to a chosen rendezvous point 8
10091 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
10093 o Minor bugfixes (misc code correctness):
10094 - Fix various instances of undefined behavior in channeltls.c,
10095 tor_memmem(), and eventdns.c that would cause us to construct
10096 pointers to memory outside an allocated object. (These invalid
10097 pointers were not accessed, but C does not even allow them to
10098 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
10099 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
10100 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
10101 fix some miscellaneous errors in our tests and codebase. Fixes bug
10102 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
10103 - Always check return values for unlink, munmap, UnmapViewOfFile;
10104 check strftime return values more often. In some cases all we can
10105 do is report a warning, but this may help prevent deeper bugs from
10106 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
10108 - Fix numerous warnings from the clang "scan-build" static analyzer.
10109 Some of these are programming style issues; some of them are false
10110 positives that indicated awkward code; some are undefined behavior
10111 cases related to constructing (but not using) invalid pointers;
10112 some are assumptions about API behavior; some are (harmlessly)
10113 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
10114 correct; and one or two are genuine bugs that weren't reachable
10115 from the rest of the program. Fixes bug 8793; bugfixes on many,
10119 - Build the torify.1 manpage again. Previously, we were only trying
10120 to build it when also building tor-fw-helper. That's why we didn't
10121 notice that we'd broken the ability to build it. Fixes bug 11321;
10122 bugfix on 0.2.5.1-alpha.
10123 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
10124 11061; bugfix on 0.2.4.7-alpha.
10125 - Correctly document that we search for a system torrc file before
10126 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
10128 - Resolve warnings from Doxygen.
10130 o Code simplifications and refactoring:
10131 - Remove is_internal_IP() function. Resolves ticket 4645.
10132 - Remove unused function circuit_dump_by_chan from circuitlist.c.
10133 Closes issue 9107; patch from "marek".
10134 - Change our use of the ENUM_BF macro to avoid declarations that
10137 o Deprecated versions:
10138 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
10139 attention for some while. Directory authorities no longer accept
10140 descriptors from relays running any version of Tor prior to Tor
10141 0.2.3.16-alpha. Resolves ticket 11149.
10144 - New macros in test.h to simplify writing mock-functions for unit
10145 tests. Part of ticket 11507. Patch from Dana Koch.
10146 - Complete tests for the status.c module. Resolves ticket 11507.
10147 Patch from Dana Koch.
10150 - Remove all code for the long unused v1 directory protocol.
10151 Resolves ticket 11070.
10154 Changes in version 0.2.5.3-alpha - 2014-03-22
10155 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
10156 two new anti-DoS features for Tor relays, resolves a bug that kept
10157 SOCKS5 support for IPv6 from working, fixes several annoying usability
10158 issues for bridge users, and removes more old code for unused
10161 The Tor 0.2.5.x release series is now in patch-freeze: no feature
10162 patches not already written will be considered for inclusion in 0.2.5.x.
10164 o Major features (relay security, DoS-resistance):
10165 - When deciding whether we have run out of memory and we need to
10166 close circuits, also consider memory allocated in buffers for
10167 streams attached to each circuit.
10169 This change, which extends an anti-DoS feature introduced in
10170 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
10171 better resist more memory-based DoS attacks than before. Since the
10172 MaxMemInCellQueues option now applies to all queues, it is renamed
10173 to MaxMemInQueues. This feature fixes bug 10169.
10174 - Avoid hash-flooding denial-of-service attacks by using the secure
10175 SipHash-2-4 hash function for our hashtables. Without this
10176 feature, an attacker could degrade performance of a targeted
10177 client or server by flooding their data structures with a large
10178 number of entries to be stored at the same hash table position,
10179 thereby slowing down the Tor instance. With this feature, hash
10180 table positions are derived from a randomized cryptographic key,
10181 and an attacker cannot predict which entries will collide. Closes
10183 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
10184 the default at 8GBytes), to better support Raspberry Pi users. Fixes
10185 bug 9686; bugfix on 0.2.4.14-alpha.
10187 o Minor features (bridges, pluggable transports):
10188 - Bridges now write the SHA1 digest of their identity key
10189 fingerprint (that is, a hash of a hash of their public key) to
10190 notice-level logs, and to a new hashed-fingerprint file. This
10191 information will help bridge operators look up their bridge in
10192 Globe and similar tools. Resolves ticket 10884.
10193 - Improve the message that Tor displays when running as a bridge
10194 using pluggable transports without an Extended ORPort listener.
10195 Also, log the message in the log file too. Resolves ticket 11043.
10197 o Minor features (other):
10198 - Add a new option, PredictedPortsRelevanceTime, to control how long
10199 after having received a request to connect to a given port Tor
10200 will try to keep circuits ready in anticipation of future requests
10201 for that port. Patch from "unixninja92"; implements ticket 9176.
10202 - Generate a warning if any ports are listed in the SocksPolicy,
10203 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
10204 AuthDirBadExit options. (These options only support address
10205 ranges.) Fixes part of ticket 11108.
10206 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
10209 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
10210 - Build without warnings under clang 3.4. (We have some macros that
10211 define static functions only some of which will get used later in
10212 the module. Starting with clang 3.4, these give a warning unless the
10213 unused attribute is set on them.) Resolves ticket 10904.
10214 - Fix build warnings about missing "a2x" comment when building the
10215 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
10216 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
10218 o Minor bugfixes (client):
10219 - Improve the log message when we can't connect to a hidden service
10220 because all of the hidden service directory nodes hosting its
10221 descriptor are excluded. Improves on our fix for bug 10722, which
10222 was a bugfix on 0.2.0.10-alpha.
10223 - Raise a control port warning when we fail to connect to all of
10224 our bridges. Previously, we didn't inform the controller, and
10225 the bootstrap process would stall. Fixes bug 11069; bugfix on
10227 - Exit immediately when a process-owning controller exits.
10228 Previously, tor relays would wait for a little while after their
10229 controller exited, as if they had gotten an INT signal -- but this
10230 was problematic, since there was no feedback for the user. To do a
10231 clean shutdown, controllers should send an INT signal and give Tor
10232 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
10233 - Stop attempting to connect to bridges before our pluggable
10234 transports are configured (harmless but resulted in some erroneous
10235 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
10236 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
10237 generating incorrect SOCKS5 responses, and confusing client
10238 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
10240 o Minor bugfixes (relays and bridges):
10241 - Avoid crashing on a malformed resolv.conf file when running a
10242 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
10243 - Non-exit relays no longer launch mock DNS requests to check for
10244 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
10245 non-exit relays stopped servicing DNS requests. Fixes bug 965;
10246 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
10247 - Bridges now report complete directory request statistics. Related
10248 to bug 5824; bugfix on 0.2.2.1-alpha.
10249 - Bridges now never collect statistics that were designed for
10250 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
10251 - Stop giving annoying warning messages when we decide not to launch
10252 a pluggable transport proxy that we don't need (because there are
10253 no bridges configured to use it). Resolves ticket 5018; bugfix
10255 - Give the correct URL in the warning message when trying to run a
10256 relay on an ancient version of Windows. Fixes bug 9393.
10258 o Minor bugfixes (backtrace support):
10259 - Support automatic backtraces on more platforms by using the
10260 "-fasynchronous-unwind-tables" compiler option. This option is
10261 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
10262 is on by default and table generation is not. This doesn't yet
10263 add Windows support; only Linux, OSX, and some BSDs are affected.
10264 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
10265 - Avoid strange behavior if two threads hit failed assertions at the
10266 same time and both try to log backtraces at once. (Previously, if
10267 this had happened, both threads would have stored their intermediate
10268 results in the same buffer, and generated junk outputs.) Reported by
10269 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
10270 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
10271 0.2.5.2-alpha; patch from Nick Hopper.
10273 o Minor bugfixes (unit tests):
10274 - Fix a small bug in the unit tests that might have made the tests
10275 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
10276 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
10279 - Remove all remaining code related to version-0 hidden service
10280 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
10281 the rest of bug 10841.
10284 - Document in the manpage that "KBytes" may also be written as
10285 "kilobytes" or "KB", that "Kbits" may also be written as
10286 "kilobits", and so forth. Closes ticket 9222.
10287 - Document that the ClientOnly config option overrides ORPort.
10288 Our old explanation made ClientOnly sound as though it did
10289 nothing at all. Resolves bug 9059.
10290 - Explain that SocksPolicy, DirPolicy, and similar options don't
10291 take port arguments. Fixes the other part of ticket 11108.
10292 - Fix a comment about the rend_server_descriptor_t.protocols field
10293 to more accurately describe its range. Also, make that field
10294 unsigned, to more accurately reflect its usage. Fixes bug 9099;
10295 bugfix on 0.2.1.5-alpha.
10296 - Fix the manpage's description of HiddenServiceAuthorizeClient:
10297 the maximum client name length is 16, not 19. Fixes bug 11118;
10298 bugfix on 0.2.1.6-alpha.
10300 o Code simplifications and refactoring:
10301 - Get rid of router->address, since in all cases it was just the
10302 string representation of router->addr. Resolves ticket 5528.
10304 o Test infrastructure:
10305 - Update to the latest version of tinytest.
10306 - Improve the tinytest implementation of string operation tests so
10307 that comparisons with NULL strings no longer crash the tests; they
10308 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
10311 Changes in version 0.2.4.21 - 2014-02-28
10312 Tor 0.2.4.21 further improves security against potential adversaries who
10313 find breaking 1024-bit crypto doable, and backports several stability
10314 and robustness patches from the 0.2.5 branch.
10316 o Major features (client security):
10317 - When we choose a path for a 3-hop circuit, make sure it contains
10318 at least one relay that supports the NTor circuit extension
10319 handshake. Otherwise, there is a chance that we're building
10320 a circuit that's worth attacking by an adversary who finds
10321 breaking 1024-bit crypto doable, and that chance changes the game
10322 theory. Implements ticket 9777.
10325 - Do not treat streams that fail with reason
10326 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
10327 since it could also indicate an ENETUNREACH connection error. Fixes
10328 part of bug 10777; bugfix on 0.2.4.8-alpha.
10330 o Code simplification and refactoring:
10331 - Remove data structures which were introduced to implement the
10332 CellStatistics option: they are now redundant with the new timestamp
10333 field in the regular packed_cell_t data structure, which we did
10334 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
10337 - Always clear OpenSSL bignums before freeing them -- even bignums
10338 that don't contain secrets. Resolves ticket 10793. Patch by
10340 - Build without warnings under clang 3.4. (We have some macros that
10341 define static functions only some of which will get used later in
10342 the module. Starting with clang 3.4, these give a warning unless the
10343 unused attribute is set on them.) Resolves ticket 10904.
10344 - Update geoip and geoip6 files to the February 7 2014 Maxmind
10345 GeoLite2 Country database.
10348 - Set the listen() backlog limit to the largest actually supported
10349 on the system, not to the value in a header file. Fixes bug 9716;
10350 bugfix on every released Tor.
10351 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
10352 exit node as a NOROUTE error, not an INTERNAL error, since they
10353 can apparently happen when trying to connect to the wrong sort
10354 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
10355 - Fix build warnings about missing "a2x" comment when building the
10356 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
10357 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
10358 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
10359 not entirely remove it from the connection lists. Fixes bug 9602;
10360 bugfix on 0.2.4.4-alpha.
10361 - Fix a segmentation fault in our benchmark code when running with
10362 Fedora's OpenSSL package, or any other OpenSSL that provides
10363 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
10364 - Turn "circuit handshake stats since last time" log messages into a
10365 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
10367 o Documentation fixes:
10368 - Document that all but one DirPort entry must have the NoAdvertise
10369 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
10372 Changes in version 0.2.5.2-alpha - 2014-02-13
10373 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
10374 like the "poor random number generation" fix and the "building too many
10375 circuits" fix. It also further improves security against potential
10376 adversaries who find breaking 1024-bit crypto doable, and launches
10377 pluggable transports on demand (which gets us closer to integrating
10378 pluggable transport support by default -- not to be confused with Tor
10379 bundles enabling pluggable transports and bridges by default).
10381 o Major features (client security):
10382 - When we choose a path for a 3-hop circuit, make sure it contains
10383 at least one relay that supports the NTor circuit extension
10384 handshake. Otherwise, there is a chance that we're building
10385 a circuit that's worth attacking by an adversary who finds
10386 breaking 1024-bit crypto doable, and that chance changes the game
10387 theory. Implements ticket 9777.
10388 - Clients now look at the "usecreatefast" consensus parameter to
10389 decide whether to use CREATE_FAST or CREATE cells for the first hop
10390 of their circuit. This approach can improve security on connections
10391 where Tor's circuit handshake is stronger than the available TLS
10392 connection security levels, but the tradeoff is more computational
10393 load on guard relays. Implements proposal 221. Resolves ticket 9386.
10395 o Major features (bridges):
10396 - Don't launch pluggable transport proxies if we don't have any
10397 bridges configured that would use them. Now we can list many
10398 pluggable transports, and Tor will dynamically start one when it
10399 hears a bridge address that needs it. Resolves ticket 5018.
10400 - The bridge directory authority now assigns status flags (Stable,
10401 Guard, etc) to bridges based on thresholds calculated over all
10402 Running bridges. Now bridgedb can finally make use of its features
10403 to e.g. include at least one Stable bridge in its answers. Fixes
10406 o Major features (other):
10407 - Extend ORCONN controller event to include an "ID" parameter,
10408 and add four new controller event types CONN_BW, CIRC_BW,
10409 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
10410 The new events are emitted in private Tor networks only, with the
10411 goal of being able to better track performance and load during
10412 full-network simulations. Implements proposal 218 and ticket 7359.
10413 - On some platforms (currently: recent OSX versions, glibc-based
10414 platforms that support the ELF format, and a few other
10415 Unix-like operating systems), Tor can now dump stack traces
10416 when a crash occurs or an assertion fails. By default, traces
10417 are dumped to stderr (if possible) and to any logs that are
10418 reporting errors. Implements ticket 9299.
10421 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
10422 not entirely remove it from the connection lists. Fixes bug 9602;
10423 bugfix on 0.2.4.4-alpha.
10424 - Do not treat streams that fail with reason
10425 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
10426 since it could also indicate an ENETUNREACH connection error. Fixes
10427 part of bug 10777; bugfix on 0.2.4.8-alpha.
10429 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
10430 - Do not allow OpenSSL engines to replace the PRNG, even when
10431 HardwareAccel is set. The only default builtin PRNG engine uses
10432 the Intel RDRAND instruction to replace the entire PRNG, and
10433 ignores all attempts to seed it with more entropy. That's
10434 cryptographically stupid: the right response to a new alleged
10435 entropy source is never to discard all previously used entropy
10436 sources. Fixes bug 10402; works around behavior introduced in
10437 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
10439 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
10440 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
10441 - Avoid launching spurious extra circuits when a stream is pending.
10442 This fixes a bug where any circuit that _wasn't_ unusable for new
10443 streams would be treated as if it were, causing extra circuits to
10444 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
10446 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10447 - No longer stop reading or writing on cpuworker connections when
10448 our rate limiting buckets go empty. Now we should handle circuit
10449 handshake requests more promptly. Resolves bug 9731.
10450 - Stop trying to bootstrap all our directory information from
10451 only our first guard. Discovered while fixing bug 9946; bugfix
10454 o Minor features (bridges, pluggable transports):
10455 - Add threshold cutoffs to the networkstatus document created by
10456 the Bridge Authority. Fixes bug 1117.
10457 - On Windows, spawn background processes using the CREATE_NO_WINDOW
10458 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
10459 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
10460 Vidalia set this option for us.) Implements ticket 10297.
10462 o Minor features (security):
10463 - Always clear OpenSSL bignums before freeing them -- even bignums
10464 that don't contain secrets. Resolves ticket 10793. Patch by
10465 Florent Daignière.
10467 o Minor features (config options and command line):
10468 - Add an --allow-missing-torrc commandline option that tells Tor to
10469 run even if the configuration file specified by -f is not available.
10470 Implements ticket 10060.
10471 - Add support for the TPROXY transparent proxying facility on Linux.
10472 See documentation for the new TransProxyType option for more
10473 details. Implementation by "thomo". Closes ticket 10582.
10475 o Minor features (controller):
10476 - Add a new "HS_DESC" controller event that reports activities
10477 related to hidden service descriptors. Resolves ticket 8510.
10478 - New "DROPGUARDS" controller command to forget all current entry
10479 guards. Not recommended for ordinary use, since replacing guards
10480 too frequently makes several attacks easier. Resolves ticket 9934;
10483 o Minor features (build):
10484 - Assume that a user using ./configure --host wants to cross-compile,
10485 and give an error if we cannot find a properly named
10486 tool-chain. Add a --disable-tool-name-check option to proceed
10487 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
10488 - If we run ./configure and the compiler recognizes -fstack-protector
10489 but the linker rejects it, warn the user about a potentially missing
10490 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
10492 o Minor features (testing):
10493 - If Python is installed, "make check" now runs extra tests beyond
10494 the unit test scripts.
10495 - When bootstrapping a test network, sometimes very few relays get
10496 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
10497 specify a set of relays which should be voted Guard regardless of
10498 their uptime or bandwidth. Addresses ticket 9206.
10500 o Minor features (log messages):
10501 - When ServerTransportPlugin is set on a bridge, Tor can write more
10502 useful statistics about bridge use in its extrainfo descriptors,
10503 but only if the Extended ORPort ("ExtORPort") is set too. Add a
10504 log message to inform the user in this case. Resolves ticket 9651.
10505 - When receiving a new controller connection, log the origin address.
10506 Resolves ticket 9698; patch from "sigpipe".
10507 - When logging OpenSSL engine status at startup, log the status of
10508 more engines. Fixes ticket 10043; patch from Joshua Datko.
10509 - Turn "circuit handshake stats since last time" log messages into a
10510 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
10512 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10513 - Improve the circuit queue out-of-memory handler. Previously, when
10514 we ran low on memory, we'd close whichever circuits had the most
10515 queued cells. Now, we close those that have the *oldest* queued
10516 cells, on the theory that those are most responsible for us
10517 running low on memory. Based on analysis from a forthcoming paper
10518 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
10519 - Generate bootstrapping status update events correctly when fetching
10520 microdescriptors. Fixes bug 9927.
10521 - Update to the October 2 2013 Maxmind GeoLite Country database.
10523 o Minor bugfixes (clients):
10524 - When closing a channel that has already been open, do not close
10525 pending circuits that were waiting to connect to the same relay.
10526 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
10529 o Minor bugfixes (relays):
10530 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
10531 exit node as a NOROUTE error, not an INTERNAL error, since they
10532 can apparently happen when trying to connect to the wrong sort
10533 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
10535 o Minor bugfixes (bridges):
10536 - Fix a bug where the first connection works to a bridge that uses a
10537 pluggable transport with client-side parameters, but we don't send
10538 the client-side parameters on subsequent connections. (We don't
10539 use any pluggable transports with client-side parameters yet,
10540 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
10541 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
10543 o Minor bugfixes (node selection):
10544 - If ExcludeNodes is set, consider non-excluded hidden service
10545 directory servers before excluded ones. Do not consider excluded
10546 hidden service directory servers at all if StrictNodes is
10547 set. (Previously, we would sometimes decide to connect to those
10548 servers, and then realize before we initiated a connection that
10549 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
10550 Reported by "mr-4".
10551 - If we set the ExitNodes option but it doesn't include any nodes
10552 that have the Exit flag, we would choose not to bootstrap. Now we
10553 bootstrap so long as ExitNodes includes nodes which can exit to
10554 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
10556 o Minor bugfixes (controller and command-line):
10557 - If changing a config option via "setconf" fails in a recoverable
10558 way, we used to nonetheless write our new control ports to the
10559 file described by the "ControlPortWriteToFile" option. Now we only
10560 write out that file if we successfully switch to the new config
10561 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
10562 - When a command-line option such as --version or --help that
10563 ordinarily implies --hush appears on the command line along with
10564 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
10565 only if it appeared later on the command line. Fixes bug 9578;
10566 bugfix on 0.2.5.1-alpha.
10568 o Minor bugfixes (code correctness):
10569 - Previously we used two temporary files when writing descriptors to
10570 disk; now we only use one. Fixes bug 1376.
10571 - Remove an erroneous (but impossible and thus harmless) pointer
10572 comparison that would have allowed compilers to skip a bounds
10573 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
10574 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
10575 - Fix an always-true assertion in pluggable transports code so it
10576 actually checks what it was trying to check. Fixes bug 10046;
10577 bugfix on 0.2.3.9-alpha. Found by "dcb".
10579 o Minor bugfixes (protocol correctness):
10580 - When receiving a VERSIONS cell with an odd number of bytes, close
10581 the connection immediately since the cell is malformed. Fixes bug
10582 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
10585 o Minor bugfixes (build):
10586 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
10587 turned off (that is, without support for v2 link handshakes). Fixes
10588 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
10589 - Fix compilation warnings and startup issues when running with
10590 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
10592 - Fix compilation on Solaris 9, which didn't like us having an
10593 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
10595 o Minor bugfixes (testing):
10596 - Fix a segmentation fault in our benchmark code when running with
10597 Fedora's OpenSSL package, or any other OpenSSL that provides
10598 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
10600 o Minor bugfixes (log messages):
10601 - Fix a bug where clients using bridges would report themselves
10602 as 50% bootstrapped even without a live consensus document.
10603 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
10604 - Suppress a warning where, if there's only one directory authority
10605 in the network, we would complain that votes and signatures cannot
10606 be uploaded to other directory authorities. Fixes bug 10842;
10607 bugfix on 0.2.2.26-beta.
10608 - Report bootstrapping progress correctly when we're downloading
10609 microdescriptors. We had updated our "do we have enough microdescs
10610 to begin building circuits?" logic most recently in 0.2.4.10-alpha
10611 (see bug 5956), but we left the bootstrap status event logic at
10612 "how far through getting 1/4 of them are we?" Fixes bug 9958;
10613 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
10615 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
10616 - Avoid a crash bug when starting with a corrupted microdescriptor
10617 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
10618 - If we fail to dump a previously cached microdescriptor to disk, avoid
10619 freeing duplicate data later on. Fixes bug 10423; bugfix on
10620 0.2.4.13-alpha. Spotted by "bobnomnom".
10622 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10623 - Correctly log long IPv6 exit policies, instead of truncating them
10624 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
10625 - Our default TLS ecdhe groups were backwards: we meant to be using
10626 P224 for relays (for performance win) and P256 for bridges (since
10627 it is more common in the wild). Instead we had it backwards. After
10628 reconsideration, we decided that the default should be P256 on all
10629 hosts, since its security is probably better, and since P224 is
10630 reportedly used quite little in the wild. Found by "skruffy" on
10631 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
10632 - Free directory authority certificate download statuses on exit
10633 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
10635 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10636 - If the guard we choose first doesn't answer, we would try the
10637 second guard, but once we connected to the second guard we would
10638 abandon it and retry the first one, slowing down bootstrapping.
10639 The fix is to treat all our initially chosen guards as acceptable
10640 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10641 - Fix an assertion failure that would occur when disabling the
10642 ORPort setting on a running Tor process while accounting was
10643 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10644 - When examining the list of network interfaces to find our address,
10645 do not consider non-running or disabled network interfaces. Fixes
10646 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10647 - Avoid an off-by-one error when checking buffer boundaries when
10648 formatting the exit status of a pluggable transport helper.
10649 This is probably not an exploitable bug, but better safe than
10650 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10653 o Removed code and features:
10654 - Clients now reject any directory authority certificates lacking
10655 a dir-key-crosscert element. These have been included since
10656 0.2.1.9-alpha, so there's no real reason for them to be optional
10657 any longer. Completes proposal 157. Resolves ticket 10162.
10658 - Remove all code that existed to support the v2 directory system,
10659 since there are no longer any v2 directory authorities. Resolves
10661 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
10662 options, which were used for designating authorities as "Hidden
10663 service authorities". There has been no use of hidden service
10664 authorities since 0.2.2.1-alpha, when we stopped uploading or
10665 downloading v0 hidden service descriptors. Fixes bug 10881; also
10666 part of a fix for bug 10841.
10668 o Code simplification and refactoring:
10669 - Remove some old fallback code designed to keep Tor clients working
10670 in a network with only two working relays. Elsewhere in the code we
10671 have long since stopped supporting such networks, so there wasn't
10672 much point in keeping it around. Addresses ticket 9926.
10673 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
10674 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
10675 - Remove data structures which were introduced to implement the
10676 CellStatistics option: they are now redundant with the addition
10677 of a timestamp to the regular packed_cell_t data structure, which
10678 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
10681 o Documentation (man page) fixes:
10682 - Update manpage to describe some of the files you can expect to
10683 find in Tor's DataDirectory. Addresses ticket 9839.
10684 - Document that all but one DirPort entry must have the NoAdvertise
10685 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
10687 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10688 - Clarify the usage and risks of setting the ContactInfo torrc line
10689 for your relay or bridge. Resolves ticket 9854.
10690 - Add anchors to the manpage so we can link to the html version of
10691 the documentation for specific options. Resolves ticket 9866.
10692 - Replace remaining references to DirServer in man page and
10693 log entries. Resolves ticket 10124.
10696 - Make the "tor-gencert" tool used by directory authority operators
10697 create 2048-bit signing keys by default (rather than 1024-bit, since
10698 1024-bit is uncomfortably small these days). Addresses ticket 10324.
10701 Changes in version 0.2.4.20 - 2013-12-22
10702 Tor 0.2.4.20 fixes potentially poor random number generation for users
10703 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
10704 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
10705 and 4) have no state file in their DataDirectory (as would happen on
10706 first start). Users who generated relay or hidden service identity
10707 keys in such a situation should discard them and generate new ones.
10709 This release also fixes a logic error that caused Tor clients to build
10710 many more preemptive circuits than they actually need.
10713 - Do not allow OpenSSL engines to replace the PRNG, even when
10714 HardwareAccel is set. The only default builtin PRNG engine uses
10715 the Intel RDRAND instruction to replace the entire PRNG, and
10716 ignores all attempts to seed it with more entropy. That's
10717 cryptographically stupid: the right response to a new alleged
10718 entropy source is never to discard all previously used entropy
10719 sources. Fixes bug 10402; works around behavior introduced in
10720 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
10722 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
10723 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
10724 - Avoid launching spurious extra circuits when a stream is pending.
10725 This fixes a bug where any circuit that _wasn't_ unusable for new
10726 streams would be treated as if it were, causing extra circuits to
10727 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
10730 - Avoid a crash bug when starting with a corrupted microdescriptor
10731 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
10732 - If we fail to dump a previously cached microdescriptor to disk, avoid
10733 freeing duplicate data later on. Fixes bug 10423; bugfix on
10734 0.2.4.13-alpha. Spotted by "bobnomnom".
10737 Changes in version 0.2.4.19 - 2013-12-11
10738 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
10739 (1986-2013). Aaron worked on diverse projects including helping to guide
10740 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
10741 transparency to the U.S government's PACER documents, and contributing
10742 design and development for Tor and Tor2Web. Aaron was one of the latest
10743 martyrs in our collective fight for civil liberties and human rights,
10744 and his death is all the more painful because he was one of us.
10746 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
10747 a new circuit handshake and link encryption that use ECC to provide
10748 better security and efficiency; makes relays better manage circuit
10749 creation requests; uses "directory guards" to reduce client enumeration
10750 risks; makes bridges collect and report statistics about the pluggable
10751 transports they support; cleans up and improves our geoip database;
10752 gets much closer to IPv6 support for clients, bridges, and relays; makes
10753 directory authorities use measured bandwidths rather than advertised
10754 ones when computing flags and thresholds; disables client-side DNS
10755 caching to reduce tracking risks; and fixes a big bug in bridge
10756 reachability testing. This release introduces two new design
10757 abstractions in the code: a new "channel" abstraction between circuits
10758 and or_connections to allow for implementing alternate relay-to-relay
10759 transports, and a new "circuitmux" abstraction storing the queue of
10760 circuits for a channel. The release also includes many stability,
10761 security, and privacy fixes.
10764 Changes in version 0.2.4.18-rc - 2013-11-16
10765 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
10766 series. It takes a variety of fixes from the 0.2.5.x branch to improve
10767 stability, performance, and better handling of edge cases.
10770 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10771 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10772 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10773 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10774 them to solve bug 6033.)
10777 - No longer stop reading or writing on cpuworker connections when
10778 our rate limiting buckets go empty. Now we should handle circuit
10779 handshake requests more promptly. Resolves bug 9731.
10780 - If we are unable to save a microdescriptor to the journal, do not
10781 drop it from memory and then reattempt downloading it. Fixes bug
10782 9645; bugfix on 0.2.2.6-alpha.
10783 - Stop trying to bootstrap all our directory information from
10784 only our first guard. Discovered while fixing bug 9946; bugfix
10786 - The new channel code sometimes lost track of in-progress circuits,
10787 causing long-running clients to stop building new circuits. The
10788 fix is to always call circuit_n_chan_done(chan, 0) from
10789 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
10791 o Minor bugfixes (on 0.2.4.x):
10792 - Correctly log long IPv6 exit policies, instead of truncating them
10793 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
10794 - Our default TLS ecdhe groups were backwards: we meant to be using
10795 P224 for relays (for performance win) and P256 for bridges (since
10796 it is more common in the wild). Instead we had it backwards. After
10797 reconsideration, we decided that the default should be P256 on all
10798 hosts, since its security is probably better, and since P224 is
10799 reportedly used quite little in the wild. Found by "skruffy" on
10800 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
10801 - Free directory authority certificate download statuses on exit
10802 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
10804 o Minor bugfixes (on 0.2.3.x and earlier):
10805 - If the guard we choose first doesn't answer, we would try the
10806 second guard, but once we connected to the second guard we would
10807 abandon it and retry the first one, slowing down bootstrapping.
10808 The fix is to treat all our initially chosen guards as acceptable
10809 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10810 - Fix an assertion failure that would occur when disabling the
10811 ORPort setting on a running Tor process while accounting was
10812 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10813 - When examining the list of network interfaces to find our address,
10814 do not consider non-running or disabled network interfaces. Fixes
10815 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10816 - Avoid an off-by-one error when checking buffer boundaries when
10817 formatting the exit status of a pluggable transport helper.
10818 This is probably not an exploitable bug, but better safe than
10819 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10822 o Minor features (protecting client timestamps):
10823 - Clients no longer send timestamps in their NETINFO cells. These were
10824 not used for anything, and they provided one small way for clients
10825 to be distinguished from each other as they moved from network to
10826 network or behind NAT. Implements part of proposal 222.
10827 - Clients now round timestamps in INTRODUCE cells down to the nearest
10828 10 minutes. If a new Support022HiddenServices option is set to 0, or
10829 if it's set to "auto" and the feature is disabled in the consensus,
10830 the timestamp is sent as 0 instead. Implements part of proposal 222.
10831 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10832 a big deal from a security point of view, but it achieves no actual
10833 good purpose, and isn't needed. Implements part of proposal 222.
10834 - Reduce down accuracy of timestamps in hidden service descriptors.
10835 Implements part of proposal 222.
10837 o Minor features (other):
10838 - Improve the circuit queue out-of-memory handler. Previously, when
10839 we ran low on memory, we'd close whichever circuits had the most
10840 queued cells. Now, we close those that have the *oldest* queued
10841 cells, on the theory that those are most responsible for us
10842 running low on memory. Based on analysis from a forthcoming paper
10843 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
10844 - Generate bootstrapping status update events correctly when fetching
10845 microdescriptors. Fixes bug 9927.
10846 - Update to the October 2 2013 Maxmind GeoLite Country database.
10848 o Documentation fixes:
10849 - Clarify the usage and risks of setting the ContactInfo torrc line
10850 for your relay or bridge. Resolves ticket 9854.
10851 - Add anchors to the manpage so we can link to the html version of
10852 the documentation for specific options. Resolves ticket 9866.
10853 - Replace remaining references to DirServer in man page and
10854 log entries. Resolves ticket 10124.
10857 Changes in version 0.2.5.1-alpha - 2013-10-02
10858 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
10859 on Linux, allows bridges that offer pluggable transports to report usage
10860 statistics, fixes many issues to make testing easier, and provides
10861 a pile of minor features and bugfixes that have been waiting for a
10862 release of the new branch.
10864 This is the first alpha release in a new series, so expect there to
10865 be bugs. Users who would rather test out a more stable branch should
10866 stay with 0.2.4.x for now.
10868 o Major features (security):
10869 - Use the seccomp2 syscall filtering facility on Linux to limit
10870 which system calls Tor can invoke. This is an experimental,
10871 Linux-only feature to provide defense-in-depth against unknown
10872 attacks. To try turning it on, set "Sandbox 1" in your torrc
10873 file. Please be ready to report bugs. We hope to add support
10874 for better sandboxing in the future, including more fine-grained
10875 filters, better division of responsibility, and support for more
10876 platforms. This work has been done by Cristian-Matei Toader for
10877 Google Summer of Code.
10878 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10879 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10880 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10881 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10882 them to solve bug 6033.)
10884 o Major features (other):
10885 - Add support for passing arguments to managed pluggable transport
10886 proxies. Implements ticket 3594.
10887 - Bridges now track GeoIP information and the number of their users
10888 even when pluggable transports are in use, and report usage
10889 statistics in their extra-info descriptors. Resolves tickets 4773
10891 - Make testing Tor networks bootstrap better: lower directory fetch
10892 retry schedules and maximum interval without directory requests,
10893 and raise maximum download tries. Implements ticket 6752.
10894 - Add make target 'test-network' to run tests on a Chutney network.
10895 Implements ticket 8530.
10896 - The ntor handshake is now on-by-default, no matter what the
10897 directory authorities recommend. Implements ticket 8561.
10900 - Instead of writing destroy cells directly to outgoing connection
10901 buffers, queue them and intersperse them with other outgoing cells.
10902 This can prevent a set of resource starvation conditions where too
10903 many pending destroy cells prevent data cells from actually getting
10904 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
10905 bugfix on 0.2.0.1-alpha.
10906 - If we are unable to save a microdescriptor to the journal, do not
10907 drop it from memory and then reattempt downloading it. Fixes bug
10908 9645; bugfix on 0.2.2.6-alpha.
10909 - The new channel code sometimes lost track of in-progress circuits,
10910 causing long-running clients to stop building new circuits. The
10911 fix is to always call circuit_n_chan_done(chan, 0) from
10912 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
10915 - Tor now builds each source file in two modes: a mode that avoids
10916 exposing identifiers needlessly, and another mode that exposes
10917 more identifiers for testing. This lets the compiler do better at
10918 optimizing the production code, while enabling us to take more
10919 radical measures to let the unit tests test things.
10920 - The production builds no longer include functions used only in
10921 the unit tests; all functions exposed from a module only for
10922 unit-testing are now static in production builds.
10923 - Add an --enable-coverage configuration option to make the unit
10924 tests (and a new src/or/tor-cov target) to build with gcov test
10928 - We now have rudimentary function mocking support that our unit
10929 tests can use to test functions in isolation. Function mocking
10930 lets the tests temporarily replace a function's dependencies with
10931 stub functions, so that the tests can check the function without
10932 invoking the other functions it calls.
10933 - Add more unit tests for the <circid,channel>->circuit map, and
10934 the destroy-cell-tracking code to fix bug 7912.
10935 - Unit tests for failing cases of the TAP onion handshake.
10936 - More unit tests for address-manipulation functions.
10938 o Minor features (protecting client timestamps):
10939 - Clients no longer send timestamps in their NETINFO cells. These were
10940 not used for anything, and they provided one small way for clients
10941 to be distinguished from each other as they moved from network to
10942 network or behind NAT. Implements part of proposal 222.
10943 - Clients now round timestamps in INTRODUCE cells down to the nearest
10944 10 minutes. If a new Support022HiddenServices option is set to 0, or
10945 if it's set to "auto" and the feature is disabled in the consensus,
10946 the timestamp is sent as 0 instead. Implements part of proposal 222.
10947 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10948 a big deal from a security point of view, but it achieves no actual
10949 good purpose, and isn't needed. Implements part of proposal 222.
10950 - Reduce down accuracy of timestamps in hidden service descriptors.
10951 Implements part of proposal 222.
10953 o Minor features (config options):
10954 - Config (torrc) lines now handle fingerprints which are missing
10955 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
10956 - Support a --dump-config option to print some or all of the
10957 configured options. Mainly useful for debugging the command-line
10958 option parsing code. Helps resolve ticket 4647.
10959 - Raise awareness of safer logging: notify user of potentially
10960 unsafe config options, like logging more verbosely than severity
10961 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
10962 - Add a new configuration option TestingV3AuthVotingStartOffset
10963 that bootstraps a network faster by changing the timing for
10964 consensus votes. Addresses ticket 8532.
10965 - Add a new torrc option "ServerTransportOptions" that allows
10966 bridge operators to pass configuration parameters to their
10967 pluggable transports. Resolves ticket 8929.
10968 - The config (torrc) file now accepts bandwidth and space limits in
10969 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
10970 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
10973 o Minor features (build):
10974 - Add support for `--library-versions` flag. Implements ticket 6384.
10975 - Return the "unexpected sendme" warnings to a warn severity, but make
10976 them rate limited, to help diagnose ticket 8093.
10977 - Detect a missing asciidoc, and warn the user about it, during
10978 configure rather than at build time. Fixes issue 6506. Patch from
10981 o Minor features (other):
10982 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
10983 sockets in a single system call. Implements ticket 5129.
10984 - Log current accounting state (bytes sent and received + remaining
10985 time for the current accounting period) in the relay's heartbeat
10986 message. Implements ticket 5526; patch from Peter Retzlaff.
10987 - Implement the TRANSPORT_LAUNCHED control port event that
10988 notifies controllers about new launched pluggable
10989 transports. Resolves ticket 5609.
10990 - If we're using the pure-C 32-bit curve25519_donna implementation
10991 of curve25519, build it with the -fomit-frame-pointer option to
10992 make it go faster on register-starved hosts. This improves our
10993 handshake performance by about 6% on i386 hosts without nacl.
10994 Closes ticket 8109.
10995 - Update to the September 4 2013 Maxmind GeoLite Country database.
10998 - Set the listen() backlog limit to the largest actually supported
10999 on the system, not to the value in a header file. Fixes bug 9716;
11000 bugfix on every released Tor.
11001 - No longer accept malformed http headers when parsing urls from
11002 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
11003 bugfix on 0.0.6pre1.
11004 - In munge_extrainfo_into_routerinfo(), check the return value of
11005 memchr(). This would have been a serious issue if we ever passed
11006 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
11008 - On the chance that somebody manages to build Tor on a
11009 platform where time_t is unsigned, correct the way that
11010 microdesc_add_to_cache() handles negative time arguments.
11011 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
11012 - Reject relative control socket paths and emit a warning. Previously,
11013 single-component control socket paths would be rejected, but Tor
11014 would not log why it could not validate the config. Fixes bug 9258;
11015 bugfix on 0.2.3.16-alpha.
11017 o Minor bugfixes (command line):
11018 - Use a single command-line parser for parsing torrc options on the
11019 command line and for finding special command-line options to avoid
11020 inconsistent behavior for torrc option arguments that have the same
11021 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
11023 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
11024 9573; bugfix on 0.0.9pre5.
11026 o Minor fixes (build, auxiliary programs):
11027 - Stop preprocessing the "torify" script with autoconf, since
11028 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
11030 - The tor-fw-helper program now follows the standard convention and
11031 exits with status code "0" on success. Fixes bug 9030; bugfix on
11032 0.2.3.1-alpha. Patch by Arlo Breault.
11033 - Corrected ./configure advice for what openssl dev package you should
11034 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
11036 o Minor code improvements:
11037 - Remove constants and tests for PKCS1 padding; it's insecure and
11038 shouldn't be used for anything new. Fixes bug 8792; patch
11040 - Remove instances of strcpy() from the unit tests. They weren't
11041 hurting anything, since they were only in the unit tests, but it's
11042 embarassing to have strcpy() in the code at all, and some analysis
11043 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
11044 0.2.3.8-alpha. Patch from Arlo Breault.
11046 o Removed features:
11047 - Remove migration code from when we renamed the "cached-routers"
11048 file to "cached-descriptors" back in 0.2.0.8-alpha. This
11049 incidentally resolves ticket 6502 by cleaning up the related code
11050 a bit. Patch from Akshay Hebbar.
11052 o Code simplification and refactoring:
11053 - Extract the common duplicated code for creating a subdirectory
11054 of the data directory and writing to a file in it. Fixes ticket
11055 4282; patch from Peter Retzlaff.
11056 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
11057 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
11058 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
11059 - Add a set of accessor functions for the circuit timeout data
11060 structure. Fixes ticket 6153; patch from "piet".
11061 - Clean up exit paths from connection_listener_new(). Closes ticket
11062 8789. Patch from Arlo Breault.
11063 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
11064 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
11065 - Use a doubly-linked list to implement the global circuit list.
11066 Resolves ticket 9108. Patch from Marek Majkowski.
11067 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
11070 Changes in version 0.2.4.17-rc - 2013-09-05
11071 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
11072 series. It adds an emergency step to help us tolerate the massive
11073 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
11074 circuit-level handshakes now effectively jump the queue compared to
11075 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
11076 big bug hindering bridge reachability tests.
11079 - Relays now process the new "NTor" circuit-level handshake requests
11080 with higher priority than the old "TAP" circuit-level handshake
11081 requests. We still process some TAP requests to not totally starve
11082 0.2.3 clients when NTor becomes popular. A new consensus parameter
11083 "NumNTorsPerTAP" lets us tune the balance later if we need to.
11084 Implements ticket 9574.
11087 - If the circuit build timeout logic is disabled (via the consensus,
11088 or because we are an authority), then don't build testing circuits.
11089 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
11090 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
11091 previously they did not, which prevented them from receiving
11092 successful connections from relays for self-test or bandwidth
11093 testing. Also, when a relay is extending a circuit to a bridge,
11094 it needs to send a NETINFO cell, even when the bridge hasn't sent
11095 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
11096 - If the time to download the next old-style networkstatus is in
11097 the future, do not decline to consider whether to download the
11098 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
11102 - Avoid double-closing the listener socket in our socketpair()
11103 replacement (used on Windows) in the case where the addresses on
11104 our opened sockets don't match what we expected. Fixes bug 9400;
11105 bugfix on 0.0.2pre7. Found by Coverity.
11107 o Minor fixes (config options):
11108 - Avoid overflows when the user sets MaxCircuitDirtiness to a
11109 ridiculously high value, by imposing a (ridiculously high) 30-day
11110 maximum on MaxCircuitDirtiness.
11111 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
11112 message is logged at notice, not at info.
11113 - Warn and fail if a server is configured not to advertise any
11114 ORPorts at all. (We need *something* to put in our descriptor,
11115 or we just won't work.)
11118 - Track how many "TAP" and "NTor" circuit handshake requests we get,
11119 and how many we complete, and log it every hour to help relay
11120 operators follow trends in network load. Addresses ticket 9658.
11121 - Update to the August 7 2013 Maxmind GeoLite Country database.
11124 Changes in version 0.2.4.16-rc - 2013-08-10
11125 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
11126 series. It fixes several crash bugs in the 0.2.4 branch.
11129 - Fix a bug in the voting algorithm that could yield incorrect results
11130 when a non-naming authority declared too many flags. Fixes bug 9200;
11131 bugfix on 0.2.0.3-alpha.
11132 - Fix an uninitialized read that could in some cases lead to a remote
11133 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
11134 Anybody running a hidden service on the experimental 0.2.4.x
11135 branch should upgrade. (This is, so far as we know, unrelated to
11137 - Avoid an assertion failure when processing DNS replies without the
11138 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
11139 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
11140 0.2.4.15-rc. Found by stem integration tests.
11143 - Fix an invalid memory read that occured when a pluggable
11144 transport proxy failed its configuration protocol.
11145 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
11146 - When evaluating whether to use a connection that we haven't
11147 decided is canonical using a recent link protocol version,
11148 decide that it's canonical only if it used address _does_
11149 match the desired address. Fixes bug 9309; bugfix on
11150 0.2.4.4-alpha. Reported by skruffy.
11151 - Make the default behavior of NumDirectoryGuards be to track
11152 NumEntryGuards. Now a user who changes only NumEntryGuards will get
11153 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
11154 - Fix a spurious compilation warning with some older versions of
11155 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
11158 - Update to the July 3 2013 Maxmind GeoLite Country database.
11161 Changes in version 0.2.4.15-rc - 2013-07-01
11162 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
11163 series. It fixes a few smaller bugs, but generally appears stable.
11164 Please test it and let us know whether it is!
11167 - When receiving a new configuration file via the control port's
11168 LOADCONF command, do not treat the defaults file as absent.
11169 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
11172 - Issue a warning when running with the bufferevents backend enabled.
11173 It's still not stable, and people should know that they're likely
11174 to hit unexpected problems. Closes ticket 9147.
11177 Changes in version 0.2.4.14-alpha - 2013-06-18
11178 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
11179 present in 0.2.4.13-alpha.
11182 - When we have too much memory queued in circuits (according to a new
11183 MaxMemInCellQueues option), close the circuits consuming the most
11184 memory. This prevents us from running out of memory as a relay if
11185 circuits fill up faster than they can be drained. Fixes bug 9063;
11186 bugfix on the 54th commit of Tor. This bug is a further fix beyond
11187 bug 6252, whose fix was merged into 0.2.3.21-rc.
11189 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
11190 where we tried to solve this issue simply by imposing an upper limit
11191 on the number of queued cells for a single circuit. That approach
11192 proved to be problematic, since there are ways to provoke clients to
11193 send a number of cells in excess of any such reasonable limit. Fixes
11194 bug 9072; bugfix on 0.2.4.13-alpha.
11196 - Limit hidden service descriptors to at most ten introduction
11197 points, to slow one kind of guard enumeration. Fixes bug 9002;
11198 bugfix on 0.1.1.11-alpha.
11201 Changes in version 0.2.4.13-alpha - 2013-06-14
11202 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
11203 vulnerabilities, makes socks5 username/password circuit isolation
11204 actually actually work (this time for sure!), and cleans up a bunch
11205 of other issues in preparation for a release candidate.
11207 o Major bugfixes (robustness):
11208 - Close any circuit that has too many cells queued on it. Fixes
11209 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
11210 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
11211 - Prevent the get_freelists() function from running off the end of
11212 the list of freelists if it somehow gets an unrecognized
11213 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
11215 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
11216 when an exit connection with optimistic data succeeds immediately
11217 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
11219 - Fix a directory authority crash bug when building a consensus
11220 using an older consensus as its basis. Fixes bug 8833. Bugfix
11224 - Avoid a memory leak where we would leak a consensus body when we
11225 find that a consensus which we couldn't previously verify due to
11226 missing certificates is now verifiable. Fixes bug 8719; bugfix
11228 - We used to always request authority certificates by identity digest,
11229 meaning we'd get the newest one even when we wanted one with a
11230 different signing key. Then we would complain about being given
11231 a certificate we already had, and never get the one we really
11232 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
11233 resource to request the one we want. Fixes bug 5595; bugfix on
11235 - Follow the socks5 protocol when offering username/password
11236 authentication. The fix for bug 8117 exposed this bug, and it
11237 turns out real-world applications like Pidgin do care. Bugfix on
11238 0.2.3.2-alpha; fixes bug 8879.
11239 - Prevent failures on Windows Vista and later when rebuilding the
11240 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
11241 bugfix on 0.2.4.12-alpha.
11244 - Fix an impossible buffer overrun in the AES unit tests. Fixes
11245 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
11246 - If for some reason we fail to write a microdescriptor while
11247 rebuilding the cache, do not let the annotations from that
11248 microdescriptor linger in the cache file, and do not let the
11249 microdescriptor stay recorded as present in its old location.
11250 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
11251 - Fix a memory leak that would occur whenever a configuration
11252 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
11253 - Paste the description for PathBias parameters from the man
11254 page into or.h, so the code documents them too. Fixes bug 7982;
11255 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
11256 - Relays now treat a changed IPv6 ORPort as sufficient reason to
11257 publish an updated descriptor. Fixes bug 6026; bugfix on
11259 - When launching a resolve request on behalf of an AF_UNIX control
11260 socket, omit the address field of the new entry connection, used in
11261 subsequent controller events, rather than letting tor_dup_addr()
11262 set it to "<unknown address type>". Fixes bug 8639; bugfix on
11265 o Minor bugfixes (log messages):
11266 - Fix a scaling issue in the path bias accounting code that
11267 resulted in "Bug:" log messages from either
11268 pathbias_scale_close_rates() or pathbias_count_build_success().
11269 This represents a bugfix on a previous bugfix: the original fix
11270 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
11272 - Give a less useless error message when the user asks for an IPv4
11273 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
11277 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
11278 to tolerate bug 8093 for now.
11279 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
11280 in directory authority votes to describe whether they have enough
11281 measured bandwidths to ignore advertised (relay descriptor)
11282 bandwidth claims. Resolves ticket 8711.
11283 - Update to the June 5 2013 Maxmind GeoLite Country database.
11285 o Removed documentation:
11286 - Remove some of the older contents of doc/ as obsolete; move others
11287 to torspec.git. Fixes bug 8965.
11289 o Code simplification and refactoring:
11290 - Avoid using character buffers when constructing most directory
11291 objects: this approach was unwieldy and error-prone. Instead,
11292 build smartlists of strings, and concatenate them when done.
11295 Changes in version 0.2.4.12-alpha - 2013-04-18
11296 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
11297 process for lengthening the guard rotation period, makes directory
11298 authority opinions in the consensus a bit less gameable, makes socks5
11299 username/password circuit isolation actually work, and fixes a wide
11300 variety of other issues.
11303 - Raise the default time that a client keeps an entry guard from
11304 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
11305 2012 paper. (We would make it even longer, but we need better client
11306 load balancing first.) Also, make the guard lifetime controllable
11307 via a new GuardLifetime torrc option and a GuardLifetime consensus
11308 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
11309 - Directory authorities now prefer using measured bandwidths to
11310 advertised ones when computing flags and thresholds. Resolves
11312 - Directory authorities that have more than a threshold number
11313 of relays with measured bandwidths now treat relays with unmeasured
11314 bandwidths as having bandwidth 0. Resolves ticket 8435.
11316 o Major bugfixes (assert / resource use):
11317 - Avoid a bug where our response to TLS renegotiation under certain
11318 network conditions could lead to a busy-loop, with 100% CPU
11319 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
11320 - Avoid an assertion when we discover that we'd like to write a cell
11321 onto a closing connection: just discard the cell. Fixes another
11322 case of bug 7350; bugfix on 0.2.4.4-alpha.
11324 o Major bugfixes (client-side privacy):
11325 - When we mark a circuit as unusable for new circuits, have it
11326 continue to be unusable for new circuits even if MaxCircuitDirtiness
11327 is increased too much at the wrong time, or the system clock jumps
11328 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
11329 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
11330 which have resolved to internal addresses") is set, apply that
11331 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
11332 - When an exit relay rejects a stream with reason "exit policy", but
11333 we only know an exit policy summary (e.g. from the microdesc
11334 consensus) for it, do not mark the relay as useless for all exiting.
11335 Instead, mark just the circuit as unsuitable for that particular
11336 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
11337 - Allow applications to get proper stream isolation with
11338 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
11339 username/password authentication also offer "no authentication". Tor
11340 had previously preferred "no authentication", so the applications
11341 never actually sent Tor their auth details. Now Tor selects
11342 username/password authentication if it's offered. You can disable
11343 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
11344 bug 8117; bugfix on 0.2.3.3-alpha.
11346 o Major bugfixes (other):
11347 - When unable to find any working directory nodes to use as a
11348 directory guard, give up rather than adding the same non-working
11349 nodes to the directory guard list over and over. Fixes bug 8231;
11350 bugfix on 0.2.4.8-alpha.
11353 - Reject as invalid most directory objects containing a NUL.
11354 Belt-and-suspender fix for bug 8037.
11355 - In our testsuite, create temporary directories with a bit more
11356 entropy in their name to make name collisions less likely. Fixes
11358 - Add CACHED keyword to ADDRMAP events in the control protocol
11359 to indicate whether a DNS result will be cached or not. Resolves
11361 - Update to the April 3 2013 Maxmind GeoLite Country database.
11363 o Minor features (build):
11364 - Detect and reject attempts to build Tor with threading support
11365 when OpenSSL has been compiled without threading support.
11367 - Clarify that when autoconf is checking for nacl, it is checking
11368 specifically for nacl with a fast curve25519 implementation.
11370 - Warn if building on a platform with an unsigned time_t: there
11371 are too many places where Tor currently assumes that time_t can
11372 hold negative values. We'd like to fix them all, but probably
11375 o Minor bugfixes (build):
11376 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
11377 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
11378 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
11379 - Add the old src/or/micro-revision.i filename to CLEANFILES.
11380 On the off chance that somebody has one, it will go away as soon
11381 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
11382 - Build Tor correctly on 32-bit platforms where the compiler can build
11383 but not run code using the "uint128_t" construction. Fixes bug 8587;
11384 bugfix on 0.2.4.8-alpha.
11385 - Fix compilation warning with some versions of clang that would
11386 prefer the -Wswitch-enum compiler flag to warn about switch
11387 statements with missing enum values, even if those switch
11388 statements have a "default:" statement. Fixes bug 8598; bugfix
11391 o Minor bugfixes (protocol):
11392 - Fix the handling of a TRUNCATE cell when it arrives while the
11393 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
11394 - Fix a misframing issue when reading the version numbers in a
11395 VERSIONS cell. Previously we would recognize [00 01 00 02] as
11396 'version 1, version 2, and version 0x100', when it should have
11397 only included versions 1 and 2. Fixes bug 8059; bugfix on
11398 0.2.0.10-alpha. Reported pseudonymously.
11399 - Make the format and order of STREAM events for DNS lookups
11400 consistent among the various ways to launch DNS lookups. Fixes
11401 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
11402 - Correct our check for which versions of Tor support the EXTEND2
11403 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
11404 later, when support was really added in version 0.2.4.8-alpha.
11405 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
11407 o Minor bugfixes (other):
11408 - Correctly store microdescriptors and extrainfo descriptors with
11409 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
11410 Bug reported by "cypherpunks".
11411 - Increase the width of the field used to remember a connection's
11412 link protocol version to two bytes. Harmless for now, since the
11413 only currently recognized versions are one byte long. Reported
11414 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
11415 - If the state file's path bias counts are invalid (presumably from a
11416 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
11417 additional checks and log messages to the scaling of Path Bias
11418 counts, in case there still are remaining issues with scaling.
11419 Should help resolve bug 8235.
11420 - Eliminate several instances where we use "Nickname=ID" to refer to
11421 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
11422 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
11423 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
11425 o Minor bugfixes (syscalls):
11426 - Always check the return values of functions fcntl() and
11427 setsockopt(). We don't believe these are ever actually failing in
11428 practice, but better safe than sorry. Also, checking these return
11429 values should please analysis tools like Coverity. Patch from
11430 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
11431 - Use direct writes rather than stdio when building microdescriptor
11432 caches, in an attempt to mitigate bug 8031, or at least make it
11435 o Minor bugfixes (config):
11436 - When rejecting a configuration because we were unable to parse a
11437 quoted string, log an actual error message. Fixes bug 7950; bugfix
11439 - Behave correctly when the user disables LearnCircuitBuildTimeout
11440 but doesn't tell us what they would like the timeout to be. Fixes
11441 bug 6304; bugfix on 0.2.2.14-alpha.
11442 - When autodetecting the number of CPUs, use the number of available
11443 CPUs in preference to the number of configured CPUs. Inform the
11444 user if this reduces the number of available CPUs. Fixes bug 8002;
11445 bugfix on 0.2.3.1-alpha.
11446 - Make it an error when you set EntryNodes but disable UseGuardNodes,
11447 since it will (surprisingly to some users) ignore EntryNodes. Fixes
11448 bug 8180; bugfix on 0.2.3.11-alpha.
11449 - Allow TestingTorNetworks to override the 4096-byte minimum for
11450 the Fast threshold. Otherwise they can't bootstrap until they've
11451 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
11452 - Fix some logic errors when the user manually overrides the
11453 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
11456 o Minor bugfixes (log messages to help diagnose bugs):
11457 - If we fail to free a microdescriptor because of bug 7164, log
11458 the filename and line number from which we tried to free it.
11459 - Add another diagnostic to the heartbeat message: track and log
11460 overhead that TLS is adding to the data we write. If this is
11461 high, we are sending too little data to SSL_write at a time.
11462 Diagnostic for bug 7707.
11463 - Add more detail to a log message about relaxed timeouts, to help
11465 - Warn more aggressively when flushing microdescriptors to a
11466 microdescriptor cache fails, in an attempt to mitigate bug 8031,
11467 or at least make it more diagnosable.
11468 - Improve debugging output to help track down bug 8185 ("Bug:
11469 outgoing relay cell has n_chan==NULL. Dropping.")
11470 - Log the purpose of a path-bias testing circuit correctly.
11471 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
11473 o Minor bugfixes (0.2.4.x log messages that were too noisy):
11474 - Don't attempt to relax the timeout of already opened 1-hop circuits.
11475 They might never timeout. This should eliminate some/all cases of
11476 the relaxed timeout log message.
11477 - Use circuit creation time for network liveness evaluation. This
11478 should eliminate warning log messages about liveness caused
11479 by changes in timeout evaluation. Fixes bug 6572; bugfix on
11481 - Reduce a path bias length check from notice to info. The message
11482 is triggered when creating controller circuits. Fixes bug 8196;
11483 bugfix on 0.2.4.8-alpha.
11484 - Fix a path state issue that triggered a notice during relay startup.
11485 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
11486 - Reduce occurrences of warns about circuit purpose in
11487 connection_ap_expire_building(). Fixes bug 8477; bugfix on
11490 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
11491 - If we encounter a write failure on a SOCKS connection before we
11492 finish our SOCKS handshake, don't warn that we closed the
11493 connection before we could send a SOCKS reply. Fixes bug 8427;
11494 bugfix on 0.1.0.1-rc.
11495 - Correctly recognize that [::1] is a loopback address. Fixes
11496 bug 8377; bugfix on 0.2.1.3-alpha.
11497 - Fix a directory authority warn caused when we have a large amount
11498 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
11499 - Don't log inappropriate heartbeat messages when hibernating: a
11500 hibernating node is _expected_ to drop out of the consensus,
11501 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
11502 bugfix on 0.2.3.1-alpha.
11503 - Don't complain about bootstrapping problems while hibernating.
11504 These complaints reflect a general code problem, but not one
11505 with any problematic effects (no connections are actually
11506 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
11508 o Documentation fixes:
11509 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
11510 names match. Fixes bug 7768.
11511 - Make the torify manpage no longer refer to tsocks; torify hasn't
11512 supported tsocks since 0.2.3.14-alpha.
11513 - Make the tor manpage no longer reference tsocks.
11514 - Fix the GeoIPExcludeUnknown documentation to refer to
11515 ExcludeExitNodes rather than the currently nonexistent
11516 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
11519 - The tor-tsocks.conf is no longer distributed or installed. We
11520 recommend that tsocks users use torsocks instead. Resolves
11524 Changes in version 0.2.4.11-alpha - 2013-03-11
11525 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
11526 more robust, makes hidden service authentication work again, and
11527 resolves a DPI fingerprint for Tor's SSL transport.
11529 o Major features (directory authorities):
11530 - Directory authorities now support a new consensus method (17)
11531 where they cap the published bandwidth of servers for which
11532 insufficient bandwidth measurements exist. Fixes part of bug 2286.
11533 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
11534 serve any v2 directory information. Now we can test disabling the
11535 old deprecated v2 directory format, and see whether doing so has
11536 any effect on network load. Begins to fix bug 6783.
11537 - Directory authorities now include inside each vote a statement of
11538 the performance thresholds they used when assigning flags.
11539 Implements ticket 8151.
11541 o Major bugfixes (directory authorities):
11542 - Stop marking every relay as having been down for one hour every
11543 time we restart a directory authority. These artificial downtimes
11544 were messing with our Stable and Guard flag calculations. Fixes
11545 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
11547 o Major bugfixes (hidden services):
11548 - Allow hidden service authentication to succeed again. When we
11549 refactored the hidden service introduction code back
11550 in 0.2.4.1-alpha, we didn't update the code that checks
11551 whether authentication information is present, causing all
11552 authentication checks to return "false". Fix for bug 8207; bugfix
11553 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
11555 o Minor features (relays, bridges):
11556 - Make bridge relays check once a minute for whether their IP
11557 address has changed, rather than only every 15 minutes. Resolves
11558 bugs 1913 and 1992.
11559 - Refactor resolve_my_address() so it returns the method by which we
11560 decided our public IP address (explicitly configured, resolved from
11561 explicit hostname, guessed from interfaces, learned by gethostname).
11562 Now we can provide more helpful log messages when a relay guesses
11563 its IP address incorrectly (e.g. due to unexpected lines in
11564 /etc/hosts). Resolves ticket 2267.
11565 - Teach bridge-using clients to avoid 0.2.2 bridges when making
11566 microdescriptor-related dir requests, and only fall back to normal
11567 descriptors if none of their bridges can handle microdescriptors
11568 (as opposed to the fix in ticket 4013, which caused them to fall
11569 back to normal descriptors if *any* of their bridges preferred
11570 them). Resolves ticket 4994.
11571 - Randomize the lifetime of our SSL link certificate, so censors can't
11572 use the static value for filtering Tor flows. Resolves ticket 8443;
11573 related to ticket 4014 which was included in 0.2.2.33.
11574 - Support a new version of the link protocol that allows 4-byte circuit
11575 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
11576 a possible resource exhaustion issue. Closes ticket 7351; implements
11579 o Minor features (portability):
11580 - Tweak the curve25519-donna*.c implementations to tolerate systems
11581 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
11582 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
11583 the signs of types during autoconf. This is better than our old
11584 approach, which didn't work when cross-compiling.
11585 - Detect the sign of enum values, rather than assuming that MSC is the
11586 only compiler where enum types are all signed. Fixes bug 7727;
11587 bugfix on 0.2.4.10-alpha.
11589 o Minor features (other):
11590 - Say "KBytes" rather than "KB" in the man page (for various values
11591 of K), to further reduce confusion about whether Tor counts in
11592 units of memory or fractions of units of memory. Resolves ticket 7054.
11593 - Clear the high bit on curve25519 public keys before passing them to
11594 our backend, in case we ever wind up using a backend that doesn't do
11595 so itself. If we used such a backend, and *didn't* clear the high bit,
11596 we could wind up in a situation where users with such backends would
11597 be distinguishable from users without. Fixes bug 8121; bugfix on
11599 - Update to the March 6 2013 Maxmind GeoLite Country database.
11601 o Minor bugfixes (clients):
11602 - When we receive a RELAY_END cell with the reason DONE, or with no
11603 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
11604 status as "connection refused". Previously we reported these cases
11605 as success but then immediately closed the connection. Fixes bug
11606 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
11607 - Downgrade an assertion in connection_ap_expire_beginning to an
11608 LD_BUG message. The fix for bug 8024 should prevent this message
11609 from displaying, but just in case, a warn that we can diagnose
11610 is better than more assert crashes. Fixes bug 8065; bugfix on
11612 - Lower path use bias thresholds to .80 for notice and .60 for warn.
11613 Also make the rate limiting flags for the path use bias log messages
11614 independent from the original path bias flags. Fixes bug 8161;
11615 bugfix on 0.2.4.10-alpha.
11617 o Minor bugfixes (relays):
11618 - Stop trying to resolve our hostname so often (e.g. every time we
11619 think about doing a directory fetch). Now we reuse the cached
11620 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
11621 and 2410 (bugfix on 0.1.2.2-alpha).
11622 - Stop sending a stray "(null)" in some cases for the server status
11623 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
11625 - When choosing which stream on a formerly stalled circuit to wake
11626 first, make better use of the platform's weak RNG. Previously,
11627 we had been using the % ("modulo") operator to try to generate a
11628 1/N chance of picking each stream, but this behaves badly with
11629 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
11631 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
11632 Irix's random() only return 15 bits; Solaris's random() returns more
11633 bits but its RAND_MAX says it only returns 15, and so on. Motivated
11634 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
11636 o Minor bugfixes (directory authorities):
11637 - Directory authorities now use less space when formatting identical
11638 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
11641 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
11642 - Avoid leaking memory if we fail to compute a consensus signature
11643 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
11644 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
11646 - Fix a memory leak during safe-cookie controller authentication.
11647 Bugfix on 0.2.3.13-alpha.
11648 - Avoid memory leak of IPv6 policy content if we fail to format it into
11649 a router descriptor. Bugfix on 0.2.4.7-alpha.
11651 o Minor bugfixes (other code correctness issues):
11652 - Avoid a crash if we fail to generate an extrainfo descriptor.
11653 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
11654 this is CID 718634.
11655 - When detecting the largest possible file descriptor (in order to
11656 close all file descriptors when launching a new program), actually
11657 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
11658 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
11660 - Fix a copy-and-paste error when adding a missing A1 to a routerset
11661 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
11662 Bugfix on 0.2.4.10-alpha.
11663 - Fix an impossible-to-trigger integer overflow when estimating how
11664 long our onionskin queue would take. (This overflow would require us
11665 to accept 4 million onionskins before processing 100 of them.) Fixes
11666 bug 8210; bugfix on 0.2.4.10-alpha.
11668 o Code simplification and refactoring:
11669 - Add a wrapper function for the common "log a message with a
11673 Changes in version 0.2.4.10-alpha - 2013-02-04
11674 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
11675 certain attacks that flood the network with relays; changes the queue
11676 for circuit create requests from a sized-based limit to a time-based
11677 limit; resumes building with MSVC on Windows; and fixes a wide variety
11680 o Major bugfixes (directory authority):
11681 - When computing directory thresholds, ignore any rejected-as-sybil
11682 nodes during the computation so that they can't influence Fast,
11683 Guard, etc. (We should have done this for proposal 109.) Fixes
11685 - When marking a node as a likely sybil, reset its uptime metrics
11686 to zero, so that it cannot time towards getting marked as Guard,
11687 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
11691 - When a TLS write is partially successful but incomplete, remember
11692 that the flushed part has been flushed, and notice that bytes were
11693 actually written. Reported and fixed pseudonymously. Fixes bug
11694 7708; bugfix on Tor 0.1.0.5-rc.
11695 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
11696 ID: these could be used to create unexpected streams and circuits
11697 which would count as "present" to some parts of Tor but "absent"
11698 to others, leading to zombie circuits and streams or to a bandwidth
11699 denial-of-service. Fixes bug 7889; bugfix on every released version
11700 of Tor. Reported by "oftc_must_be_destroyed".
11701 - Rename all macros in our local copy of queue.h to begin with "TOR_".
11702 This change seems the only good way to permanently prevent conflicts
11703 with queue.h on various operating systems. Fixes bug 8107; bugfix
11706 o Major features (relay):
11707 - Instead of limiting the number of queued onionskins (aka circuit
11708 create requests) to a fixed, hard-to-configure number, we limit
11709 the size of the queue based on how many we expect to be able to
11710 process in a given amount of time. We estimate the time it will
11711 take to process an onionskin based on average processing time
11712 of previous onionskins. Closes ticket 7291. You'll never have to
11713 configure MaxOnionsPending again.
11715 o Major features (portability):
11716 - Resume building correctly with MSVC and Makefile.nmake. This patch
11717 resolves numerous bugs and fixes reported by ultramage, including
11718 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
11719 - Make the ntor and curve25519 code build correctly with MSVC.
11720 Fix on 0.2.4.8-alpha.
11723 - When directory authorities are computing thresholds for flags,
11724 never let the threshold for the Fast flag fall below 4096
11725 bytes. Also, do not consider nodes with extremely low bandwidths
11726 when deciding thresholds for various directory flags. This change
11727 should raise our threshold for Fast relays, possibly in turn
11728 improving overall network performance; see ticket 1854. Resolves
11730 - The Tor client now ignores sub-domain components of a .onion
11731 address. This change makes HTTP "virtual" hosting
11732 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
11733 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
11734 hosted on the same hidden service. Implements proposal 204.
11735 - We compute the overhead from passing onionskins back and forth to
11736 cpuworkers, and report it when dumping statistics in response to
11737 SIGUSR1. Supports ticket 7291.
11739 o Minor features (path selection):
11740 - When deciding whether we have enough descriptors to build circuits,
11741 instead of looking at raw relay counts, look at which fraction
11742 of (bandwidth-weighted) paths we're able to build. This approach
11743 keeps clients from building circuits if their paths are likely to
11744 stand out statistically. The default fraction of paths needed is
11745 taken from the consensus directory; you can override it with the
11746 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
11747 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
11748 and we have GeoIP information, also exclude all nodes with unknown
11749 countries "??" and "A1". This behavior is controlled by the
11750 new GeoIPExcludeUnknown option: you can make such nodes always
11751 excluded with "GeoIPExcludeUnknown 1", and disable the feature
11752 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
11753 gets you the default behavior. Implements feature 7706.
11754 - Path Use Bias: Perform separate accounting for successful circuit
11755 use. Keep separate statistics on stream attempt rates versus stream
11756 success rates for each guard. Provide configurable thresholds to
11757 determine when to emit log messages or disable use of guards that
11758 fail too many stream attempts. Resolves ticket 7802.
11760 o Minor features (log messages):
11761 - When learning a fingerprint for a bridge, log its corresponding
11762 transport type. Implements ticket 7896.
11763 - Improve the log message when "Bug/attack: unexpected sendme cell
11764 from client" occurs, to help us track bug 8093.
11767 - Remove a couple of extraneous semicolons that were upsetting the
11768 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
11769 bugfix on 0.2.2.1-alpha.
11770 - Remove a source of rounding error during path bias count scaling;
11771 don't count cannibalized circuits as used for path bias until we
11772 actually try to use them; and fix a circuit_package_relay_cell()
11773 warning message about n_chan==NULL. Fixes bug 7802.
11774 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
11775 actually link against nacl when we're configured to use it. Fixes
11776 bug 7972; bugfix on 0.2.4.8-alpha.
11777 - Compile correctly with the --disable-curve25519 option. Fixes
11778 bug 8153; bugfix on 0.2.4.8-alpha.
11780 o Build improvements:
11781 - Do not report status verbosely from autogen.sh unless the -v flag
11782 is specified. Fixes issue 4664. Patch from Onizuka.
11783 - Replace all calls to snprintf() outside of src/ext with
11784 tor_snprintf(). Also remove the #define to replace snprintf with
11785 _snprintf on Windows; they have different semantics, and all of
11786 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
11787 - Try to detect if we are ever building on a platform where
11788 memset(...,0,...) does not set the value of a double to 0.0. Such
11789 platforms are permitted by the C standard, though in practice
11790 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
11791 currently support them, but it's better to detect them and fail
11792 than to perform erroneously.
11794 o Removed features:
11795 - Stop exporting estimates of v2 and v3 directory traffic shares
11796 in extrainfo documents. They were unneeded and sometimes inaccurate.
11797 Also stop exporting any v2 directory request statistics. Resolves
11799 - Drop support for detecting and warning about versions of Libevent
11800 before 1.3e. Nothing reasonable ships with them any longer;
11801 warning the user about them shouldn't be needed. Resolves ticket
11804 o Code simplifications and refactoring:
11805 - Rename "isin" functions to "contains", for grammar. Resolves
11807 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
11808 with the natural logarithm function from the system libm. Resolves
11812 Changes in version 0.2.4.9-alpha - 2013-01-15
11813 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
11814 work more robustly.
11817 - Fix backward compatibility logic when receiving an embedded ntor
11818 handshake tunneled in a CREATE cell. This clears up the "Bug:
11819 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
11823 Changes in version 0.2.4.8-alpha - 2013-01-14
11824 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
11825 risks, adds a new stronger and faster circuit handshake, and offers
11826 stronger and faster link encryption when both sides support it.
11829 - Preliminary support for directory guards (proposal 207): when
11830 possible, clients now use their entry guards for non-anonymous
11831 directory requests. This can help prevent client enumeration. Note
11832 that this behavior only works when we have a usable consensus
11833 directory, and when options about what to download are more or less
11834 standard. In the future we should re-bootstrap from our guards,
11835 rather than re-bootstrapping from the preconfigured list of
11836 directory sources that ships with Tor. Resolves ticket 6526.
11837 - Tor relays and clients now support a better CREATE/EXTEND cell
11838 format, allowing the sender to specify multiple address, identity,
11839 and handshake types. Implements Robert Ransom's proposal 200;
11840 closes ticket 7199.
11842 o Major features (new circuit handshake):
11843 - Tor now supports a new circuit extension handshake designed by Ian
11844 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
11845 circuit extension handshake, later called "TAP", was a bit slow
11846 (especially on the relay side), had a fragile security proof, and
11847 used weaker keys than we'd now prefer. The new circuit handshake
11848 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
11849 function, making it significantly more secure than the older
11850 handshake, and significantly faster. Tor can use one of two built-in
11851 pure-C curve25519-donna implementations by Adam Langley, or it
11852 can link against the "nacl" library for a tuned version if present.
11854 The built-in version is very fast for 64-bit systems when building
11855 with GCC. The built-in 32-bit version is still faster than the
11856 old TAP protocol, but using libnacl is better on most such hosts.
11858 Clients don't currently use this protocol by default, since
11859 comparatively few clients support it so far. To try it, set
11860 UseNTorHandshake to 1.
11862 Implements proposal 216; closes ticket 7202.
11864 o Major features (better link encryption):
11865 - Relays can now enable the ECDHE TLS ciphersuites when available
11866 and appropriate. These ciphersuites let us negotiate forward-secure
11867 TLS secret keys more safely and more efficiently than with our
11868 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
11869 public relays prefer the (faster) P224 group, and bridges prefer
11870 the (more common) P256 group; you can override this with the
11873 Enabling these ciphers was a little tricky, since for a long time,
11874 clients had been claiming to support them without actually doing
11875 so, in order to foil fingerprinting. But with the client-side
11876 implementation of proposal 198 in 0.2.3.17-beta, clients can now
11877 match the ciphers from recent Firefox versions *and* list the
11878 ciphers they actually mean, so relays can believe such clients
11879 when they advertise ECDHE support in their TLS ClientHello messages.
11881 This feature requires clients running 0.2.3.17-beta or later,
11882 and requires both sides to be running OpenSSL 1.0.0 or later
11883 with ECC support. OpenSSL 1.0.1, with the compile-time option
11884 "enable-ec_nistp_64_gcc_128", is highly recommended.
11886 Implements the relay side of proposal 198; closes ticket 7200.
11889 - Avoid crashing when, as a relay without IPv6-exit support, a
11890 client insists on getting an IPv6 address or nothing. Fixes bug
11891 7814; bugfix on 0.2.4.7-alpha.
11894 - Improve circuit build timeout handling for hidden services.
11895 In particular: adjust build timeouts more accurately depending
11896 upon the number of hop-RTTs that a particular circuit type
11897 undergoes. Additionally, launch intro circuits in parallel
11898 if they timeout, and take the first one to reply as valid.
11899 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
11900 separate error codes; or at least, don't break for that reason.
11901 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
11902 - Update to the January 2 2013 Maxmind GeoLite Country database.
11904 o Minor features (testing):
11905 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
11906 (P-256) Diffie-Hellman handshakes to src/or/bench.
11907 - Add benchmark functions to test onion handshake performance.
11909 o Minor features (path bias detection):
11910 - Alter the Path Bias log messages to be more descriptive in terms
11911 of reporting timeouts and other statistics.
11912 - Create three levels of Path Bias log messages, as opposed to just
11913 two. These are configurable via consensus as well as via the torrc
11914 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
11915 The default values are 0.70, 0.50, and 0.30 respectively.
11916 - Separate the log message levels from the decision to drop guards,
11917 which also is available via torrc option PathBiasDropGuards.
11918 PathBiasDropGuards still defaults to 0 (off).
11919 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
11920 in combination with PathBiasExtremeRate.
11921 - Increase the default values for PathBiasScaleThreshold and
11922 PathBiasCircThreshold from (200, 20) to (300, 150).
11923 - Add in circuit usage accounting to path bias. If we try to use a
11924 built circuit but fail for any reason, it counts as path bias.
11925 Certain classes of circuits where the adversary gets to pick your
11926 destination node are exempt from this accounting. Usage accounting
11927 can be specifically disabled via consensus parameter or torrc.
11928 - Convert all internal path bias state to double-precision floating
11929 point, to avoid roundoff error and other issues.
11930 - Only record path bias information for circuits that have completed
11931 *two* hops. Assuming end-to-end tagging is the attack vector, this
11932 makes us more resilient to ambient circuit failure without any
11933 detection capability loss.
11935 o Minor bugfixes (log messages):
11936 - Rate-limit the "No circuits are opened. Relaxed timeout for a
11937 circuit with channel state open..." message to once per hour to
11938 keep it from filling the notice logs. Mitigates bug 7799 but does
11939 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
11940 - Avoid spurious warnings when configuring multiple client ports of
11941 which only some are nonlocal. Previously, we had claimed that some
11942 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
11945 o Code simplifications and refactoring:
11946 - Get rid of a couple of harmless clang warnings, where we compared
11947 enums to ints. These warnings are newly introduced in clang 3.2.
11948 - Split the onion.c file into separate modules for the onion queue
11949 and the different handshakes it supports.
11950 - Remove the marshalling/unmarshalling code for sending requests to
11951 cpuworkers over a socket, and instead just send structs. The
11952 recipient will always be the same Tor binary as the sender, so
11953 any encoding is overkill.
11956 Changes in version 0.2.4.7-alpha - 2012-12-24
11957 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
11958 directory mirrors for more robust bootstrapping; fixes more issues where
11959 clients with changing network conditions refuse to make any circuits;
11960 adds initial support for exiting to IPv6 addresses; resumes being able
11961 to update our GeoIP database, and includes the geoip6 file this time;
11962 turns off the client-side DNS cache by default due to privacy risks;
11963 and fixes a variety of other issues.
11965 o Major features (client resilience):
11966 - Add a new "FallbackDir" torrc option to use when we can't use
11967 a directory mirror from the consensus (either because we lack a
11968 consensus, or because they're all down). Currently, all authorities
11969 are fallbacks by default, and there are no other default fallbacks,
11970 but that will change. This option will allow us to give clients a
11971 longer list of servers to try to get a consensus from when first
11972 connecting to the Tor network, and thereby reduce load on the
11973 directory authorities. Implements proposal 206, "Preconfigured
11974 directory sources for bootstrapping". We also removed the old
11975 "FallbackNetworkstatus" option, since we never got it working well
11976 enough to use it. Closes bug 572.
11977 - If we have no circuits open, use a relaxed timeout (the
11978 95-percentile cutoff) until a circuit succeeds. This heuristic
11979 should allow Tor to succeed at building circuits even when the
11980 network connection drastically changes. Should help with bug 3443.
11982 o Major features (IPv6):
11983 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
11984 connectivity, then set the IPv6Exit flag to 1. Also make sure your
11985 exit policy reads as you would like: the address * applies to all
11986 address families, whereas *4 is IPv4 address only, and *6 is IPv6
11987 addresses only. On the client side, you'll need to wait until the
11988 authorities have upgraded, wait for enough exits to support IPv6,
11989 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
11990 ticket 5547, implements proposal 117 as revised in proposal 208.
11992 We DO NOT recommend that clients with actual anonymity needs start
11993 using IPv6 over Tor yet, since not enough exits support it yet.
11995 o Major features (geoip database):
11996 - Maxmind began labelling Tor relays as being in country "A1",
11997 which breaks by-country node selection inside Tor. Now we use a
11998 script to replace "A1" ("Anonymous Proxy") entries in our geoip
11999 file with real country codes. This script fixes about 90% of "A1"
12000 entries automatically and uses manual country code assignments to
12001 fix the remaining 10%. See src/config/README.geoip for details.
12002 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
12003 Country database, as modified above.
12005 o Major bugfixes (client-side DNS):
12006 - Turn off the client-side DNS cache by default. Updating and using
12007 the DNS cache is now configurable on a per-client-port
12008 level. SOCKSPort, DNSPort, etc lines may now contain
12009 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
12010 cache these types of DNS answers when we receive them from an
12011 exit node in response to an application request on this port, and
12012 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
12013 cached DNS answers of these types, we shouldn't use them. It's
12014 potentially risky to use cached DNS answers at the client, since
12015 doing so can indicate to one exit what answers we've gotten
12016 for DNS lookups in the past. With IPv6, this becomes especially
12017 problematic. Using cached DNS answers for requests on the same
12018 circuit would present less linkability risk, since all traffic
12019 on a circuit is already linkable, but it would also provide
12020 little performance benefit: the exit node caches DNS replies
12021 too. Implements a simplified version of Proposal 205. Implements
12024 o Major bugfixes (other):
12025 - Alter circuit build timeout measurement to start at the point
12026 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
12027 initialization). This should make our timeout measurements more
12028 uniform. Previously, we were sometimes including ORconn setup time
12029 in our circuit build time measurements. Should resolve bug 3443.
12030 - Fix an assertion that could trigger in hibernate_go_dormant() when
12031 closing an or_connection_t: call channel_mark_for_close() rather
12032 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
12034 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
12035 7655; bugfix on 0.2.4.6-alpha.
12038 - Add a new torrc option "ServerTransportListenAddr" to let bridge
12039 operators select the address where their pluggable transports will
12040 listen for connections. Resolves ticket 7013.
12041 - Allow an optional $ before the node identity digest in the
12042 controller command GETINFO ns/id/<identity>, for consistency with
12043 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
12044 - Log packaged cell fullness as part of the heartbeat message.
12045 Diagnosis to try to determine the extent of bug 7743.
12047 o Minor features (IPv6):
12048 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
12049 prefer to hand out virtual IPv6 addresses, since there are more of
12050 them and we can't run out. To override this behavior and make IPv4
12051 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
12052 or DNSPort you're using for resolving. Implements ticket 7571.
12053 - AutomapHostsOnResolve responses are now randomized, to avoid
12054 annoying situations where Tor is restarted and applications
12055 connect to the wrong addresses.
12056 - Never try more than 1000 times to pick a new virtual address when
12057 AutomapHostsOnResolve is set. That's good enough so long as we
12058 aren't close to handing out our entire virtual address space;
12059 if you're getting there, it's best to switch to IPv6 virtual
12063 - The ADDRMAP command can no longer generate an ill-formed error
12064 code on a failed MAPADDRESS. It now says "internal" rather than
12065 an English sentence fragment with spaces in the middle. Bugfix on
12066 Tor 0.2.0.19-alpha.
12067 - Fix log messages and comments to avoid saying "GMT" when we mean
12068 "UTC". Fixes bug 6113.
12069 - Compile on win64 using mingw64. Fixes bug 7260; patches from
12071 - Fix a crash when debugging unit tests on Windows: deallocate a
12072 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
12073 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
12076 - The DirServer option is now DirAuthority, for consistency with
12077 current naming patterns. You can still use the old DirServer form.
12079 o Code simplification and refactoring:
12080 - Move the client-side address-map/virtual-address/DNS-cache code
12081 out of connection_edge.c into a new addressmap.c module.
12082 - Remove unused code for parsing v1 directories and "running routers"
12083 documents. Fixes bug 6887.
12086 Changes in version 0.2.3.25 - 2012-11-19
12087 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
12088 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
12089 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
12090 programmer, and friend. Unstinting in his dedication to the cause of
12091 freedom, he inspired and helped many of us as we began our work on
12092 anonymity, and inspires us still. Please honor his memory by writing
12093 software to protect people's freedoms, and by helping others to do so.
12095 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
12096 significantly reduced directory overhead (via microdescriptors),
12097 enormous crypto performance improvements for fast relays on new
12098 enough hardware, a new v3 TLS handshake protocol that can better
12099 resist fingerprinting, support for protocol obfuscation plugins (aka
12100 pluggable transports), better scalability for hidden services, IPv6
12101 support for bridges, performance improvements like allowing clients
12102 to skip the first round-trip on the circuit ("optimistic data") and
12103 refilling token buckets more often, a new "stream isolation" design
12104 to isolate different applications on different circuits, and many
12105 stability, security, and privacy fixes.
12108 - Tor tries to wipe potentially sensitive data after using it, so
12109 that if some subsequent security failure exposes Tor's memory,
12110 the damage will be limited. But we had a bug where the compiler
12111 was eliminating these wipe operations when it decided that the
12112 memory was no longer visible to a (correctly running) program,
12113 hence defeating our attempt at defense in depth. We fix that
12114 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
12115 is unlikely to optimize away. Future versions of Tor may use
12116 a less ridiculously heavy approach for this. Fixes bug 7352.
12117 Reported in an article by Andrey Karpov.
12120 - Fix a harmless bug when opting against publishing a relay descriptor
12121 because DisableNetwork is set. Fixes bug 7464; bugfix on
12125 Changes in version 0.2.4.6-alpha - 2012-11-13
12126 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
12127 makes our defense-in-depth memory wiping more reliable, and begins to
12128 count IPv6 addresses in bridge statistics,
12131 - Fix an assertion failure that could occur when closing a connection
12132 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
12134 - Tor tries to wipe potentially sensitive data after using it, so
12135 that if some subsequent security failure exposes Tor's memory,
12136 the damage will be limited. But we had a bug where the compiler
12137 was eliminating these wipe operations when it decided that the
12138 memory was no longer visible to a (correctly running) program,
12139 hence defeating our attempt at defense in depth. We fix that
12140 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
12141 is unlikely to optimize away. Future versions of Tor may use
12142 a less ridiculously heavy approach for this. Fixes bug 7352.
12143 Reported in an article by Andrey Karpov.
12146 - Add GeoIP database for IPv6 addresses. The new config option
12148 - Bridge statistics now count bridge clients connecting over IPv6:
12149 bridge statistics files now list "bridge-ip-versions" and
12150 extra-info documents list "geoip6-db-digest". The control protocol
12151 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
12152 implementation by "shkoo", addressing ticket 5055.
12155 - Warn when we are binding low ports when hibernation is enabled;
12156 previously we had warned when we were _advertising_ low ports with
12157 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
12158 - Fix a harmless bug when opting against publishing a relay descriptor
12159 because DisableNetwork is set. Fixes bug 7464; bugfix on
12161 - Add warning message when a managed proxy dies during configuration.
12162 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
12163 - Fix a linking error when building tor-fw-helper without miniupnp.
12164 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
12165 - Check for closing an or_connection_t without going through correct
12166 channel functions; emit a warning and then call
12167 connection_or_close_for_error() so we don't assert as in bugs 7212
12169 - Compile correctly on compilers without C99 designated initializer
12170 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
12171 - Avoid a possible assert that can occur when channel_send_destroy() is
12172 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
12173 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
12174 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
12175 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
12176 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
12178 o Code simplification and refactoring:
12179 - Start using OpenBSD's implementation of queue.h, so that we don't
12180 need to hand-roll our own pointer and list structures whenever we
12181 need them. (We can't rely on a sys/queue.h, since some operating
12182 systems don't have them, and the ones that do have them don't all
12183 present the same extensions.)
12186 Changes in version 0.2.4.5-alpha - 2012-10-25
12187 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
12188 two important security vulnerabilities that could lead to remotely
12189 triggerable relay crashes, fix a major bug that was preventing clients
12190 from choosing suitable exit nodes, and refactor some of our code.
12192 o Major bugfixes (security, also in 0.2.3.24-rc):
12193 - Fix a group of remotely triggerable assertion failures related to
12194 incorrect link protocol negotiation. Found, diagnosed, and fixed
12195 by "some guy from France". Fix for CVE-2012-2250; bugfix on
12197 - Fix a denial of service attack by which any directory authority
12198 could crash all the others, or by which a single v2 directory
12199 authority could crash everybody downloading v2 directory
12200 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
12202 o Major bugfixes (also in 0.2.3.24-rc):
12203 - When parsing exit policy summaries from microdescriptors, we had
12204 previously been ignoring the last character in each one, so that
12205 "accept 80,443,8080" would be treated by clients as indicating
12206 a node that allows access to ports 80, 443, and 808. That would
12207 lead to clients attempting connections that could never work,
12208 and ignoring exit nodes that would support their connections. Now
12209 clients parse these exit policy summaries correctly. Fixes bug 7192;
12210 bugfix on 0.2.3.1-alpha.
12212 o Minor bugfixes (also in 0.2.3.24-rc):
12213 - Clients now consider the ClientRejectInternalAddresses config option
12214 when using a microdescriptor consensus stanza to decide whether
12215 an exit relay would allow exiting to an internal address. Fixes
12216 bug 7190; bugfix on 0.2.3.1-alpha.
12219 - Only disable TLS session ticket support when running as a TLS
12220 server. Now clients will blend better with regular Firefox
12221 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
12223 o Code simplification and refactoring:
12224 - Start using OpenBSD's implementation of queue.h (originally by
12226 - Move the entry node code from circuitbuild.c to its own file.
12227 - Move the circuit build timeout tracking code from circuitbuild.c
12231 Changes in version 0.2.3.24-rc - 2012-10-25
12232 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
12233 could lead to remotely triggerable relay crashes, and fixes
12234 a major bug that was preventing clients from choosing suitable exit
12237 o Major bugfixes (security):
12238 - Fix a group of remotely triggerable assertion failures related to
12239 incorrect link protocol negotiation. Found, diagnosed, and fixed
12240 by "some guy from France". Fix for CVE-2012-2250; bugfix on
12242 - Fix a denial of service attack by which any directory authority
12243 could crash all the others, or by which a single v2 directory
12244 authority could crash everybody downloading v2 directory
12245 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
12248 - When parsing exit policy summaries from microdescriptors, we had
12249 previously been ignoring the last character in each one, so that
12250 "accept 80,443,8080" would be treated by clients as indicating
12251 a node that allows access to ports 80, 443, and 808. That would
12252 lead to clients attempting connections that could never work,
12253 and ignoring exit nodes that would support their connections. Now
12254 clients parse these exit policy summaries correctly. Fixes bug 7192;
12255 bugfix on 0.2.3.1-alpha.
12258 - Clients now consider the ClientRejectInternalAddresses config option
12259 when using a microdescriptor consensus stanza to decide whether
12260 an exit relay would allow exiting to an internal address. Fixes
12261 bug 7190; bugfix on 0.2.3.1-alpha.
12264 Changes in version 0.2.4.4-alpha - 2012-10-20
12265 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
12266 vulnerability introduced by a change in OpenSSL, fixes a remotely
12267 triggerable assert, and adds new channel_t and circuitmux_t abstractions
12268 that will make it easier to test new connection transport and cell
12269 scheduling algorithms.
12271 o New directory authorities (also in 0.2.3.23-rc):
12272 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
12273 authority. Closes ticket 5749.
12275 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
12276 - Disable TLS session tickets. OpenSSL's implementation was giving
12277 our TLS session keys the lifetime of our TLS context objects, when
12278 perfect forward secrecy would want us to discard anything that
12279 could decrypt a link connection as soon as the link connection
12280 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
12281 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
12282 - Discard extraneous renegotiation attempts once the V3 link
12283 protocol has been initiated. Failure to do so left us open to
12284 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
12285 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
12287 o Internal abstraction features:
12288 - Introduce new channel_t abstraction between circuits and
12289 or_connection_t to allow for implementing alternate OR-to-OR
12290 transports. A channel_t is an abstract object which can either be a
12291 cell-bearing channel, which is responsible for authenticating and
12292 handshaking with the remote OR and transmitting cells to and from
12293 it, or a listening channel, which spawns new cell-bearing channels
12294 at the request of remote ORs. Implements part of ticket 6465.
12295 - Also new is the channel_tls_t subclass of channel_t, adapting it
12296 to the existing or_connection_t code. The V2/V3 protocol handshaking
12297 code which formerly resided in command.c has been moved below the
12298 channel_t abstraction layer and may be found in channeltls.c now.
12299 Implements the rest of ticket 6465.
12300 - Introduce new circuitmux_t storing the queue of circuits for
12301 a channel; this encapsulates and abstracts the queue logic and
12302 circuit selection policy, and allows the latter to be overridden
12303 easily by switching out a policy object. The existing EWMA behavior
12304 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
12306 o Required libraries:
12307 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
12308 strongly recommended.
12311 - Warn users who run hidden services on a Tor client with
12312 UseEntryGuards disabled that their hidden services will be
12313 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
12314 attack which motivated Tor to support entry guards in the first
12315 place). Resolves ticket 6889.
12316 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
12317 dhill. Resolves ticket 6982.
12318 - Option OutboundBindAddress can be specified multiple times and
12319 accepts IPv6 addresses. Resolves ticket 6876.
12321 o Minor bugfixes (also in 0.2.3.23-rc):
12322 - Don't serve or accept v2 hidden service descriptors over a
12323 relay's DirPort. It's never correct to do so, and disabling it
12324 might make it more annoying to exploit any bugs that turn up in the
12325 descriptor-parsing code. Fixes bug 7149.
12326 - Fix two cases in src/or/transports.c where we were calling
12327 fmt_addr() twice in a parameter list. Bug found by David
12328 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
12329 - Fix memory leaks whenever we logged any message about the "path
12330 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
12331 - When relays refuse a "create" cell because their queue of pending
12332 create cells is too big (typically because their cpu can't keep up
12333 with the arrival rate), send back reason "resource limit" rather
12334 than reason "internal", so network measurement scripts can get a
12335 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
12338 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
12339 - Free some more still-in-use memory at exit, to make hunting for
12340 memory leaks easier. Resolves bug 7029.
12341 - When a Tor client gets a "truncated" relay cell, the first byte of
12342 its payload specifies why the circuit was truncated. We were
12343 ignoring this 'reason' byte when tearing down the circuit, resulting
12344 in the controller not being told why the circuit closed. Now we
12345 pass the reason from the truncated cell to the controller. Bugfix
12346 on 0.1.2.3-alpha; fixes bug 7039.
12347 - Downgrade "Failed to hand off onionskin" messages to "debug"
12348 severity, since they're typically redundant with the "Your computer
12349 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
12350 - Make clients running with IPv6 bridges connect over IPv6 again,
12351 even without setting new config options ClientUseIPv6 and
12352 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
12353 - Use square brackets around IPv6 addresses in numerous places
12354 that needed them, including log messages, HTTPS CONNECT proxy
12355 requests, TransportProxy statefile entries, and pluggable transport
12356 extra-info lines. Fixes bug 7011; patch by David Fifield.
12358 o Code refactoring and cleanup:
12359 - Source files taken from other packages now reside in src/ext;
12360 previously they were scattered around the rest of Tor.
12361 - Avoid use of reserved identifiers in our C code. The C standard
12362 doesn't like us declaring anything that starts with an
12363 underscore, so let's knock it off before we get in trouble. Fix
12364 for bug 1031; bugfix on the first Tor commit.
12367 Changes in version 0.2.3.23-rc - 2012-10-20
12368 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
12369 vulnerability introduced by a change in OpenSSL, and fixes a variety
12370 of smaller bugs in preparation for the release.
12372 o New directory authorities:
12373 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
12374 authority. Closes ticket 5749.
12376 o Major bugfixes (security/privacy):
12377 - Disable TLS session tickets. OpenSSL's implementation was giving
12378 our TLS session keys the lifetime of our TLS context objects, when
12379 perfect forward secrecy would want us to discard anything that
12380 could decrypt a link connection as soon as the link connection
12381 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
12382 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
12383 - Discard extraneous renegotiation attempts once the V3 link
12384 protocol has been initiated. Failure to do so left us open to
12385 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
12386 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
12389 - Fix a possible crash bug when checking for deactivated circuits
12390 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
12391 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
12393 o Minor bugfixes (on 0.2.3.x):
12394 - Fix two cases in src/or/transports.c where we were calling
12395 fmt_addr() twice in a parameter list. Bug found by David
12396 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
12397 - Convert an assert in the pathbias code to a log message. The assert
12398 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
12399 bugfix on 0.2.3.17-beta.
12400 - Fix memory leaks whenever we logged any message about the "path
12401 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
12403 o Minor bugfixes (on 0.2.2.x and earlier):
12404 - Don't serve or accept v2 hidden service descriptors over a relay's
12405 DirPort. It's never correct to do so, and disabling it might
12406 make it more annoying to exploit any bugs that turn up in the
12407 descriptor-parsing code. Fixes bug 7149.
12408 - When relays refuse a "create" cell because their queue of pending
12409 create cells is too big (typically because their cpu can't keep up
12410 with the arrival rate), send back reason "resource limit" rather
12411 than reason "internal", so network measurement scripts can get a
12412 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
12413 - Correct file sizes when reading binary files on Cygwin, to avoid
12414 a bug where Tor would fail to read its state file. Fixes bug 6844;
12415 bugfix on 0.1.2.7-alpha.
12416 - Avoid undefined behavior when parsing the list of supported
12417 rendezvous/introduction protocols in a hidden service descriptor.
12418 Previously, Tor would have confused (as-yet-unused) protocol version
12419 numbers greater than 32 with lower ones on many platforms. Fixes
12420 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
12422 o Documentation fixes:
12423 - Clarify that hidden services are TCP only. Fixes bug 6024.
12426 Changes in version 0.2.4.3-alpha - 2012-09-22
12427 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
12428 assertion, resumes letting relays test reachability of their DirPort,
12429 and cleans up a bunch of smaller bugs.
12432 - Fix an assertion failure in tor_timegm() that could be triggered
12433 by a badly formatted directory object. Bug found by fuzzing with
12434 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12437 - Fix a possible crash bug when checking for deactivated circuits
12438 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
12439 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
12440 - Allow routers to detect that their own DirPorts are running. When
12441 we removed support for versions_supports_begindir, we also
12442 accidentally removed the mechanism we used to self-test our
12443 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
12444 bugfix on 0.2.4.2-alpha.
12446 o Security features:
12447 - Switch to a completely time-invariant approach for picking nodes
12448 weighted by bandwidth. Our old approach would run through the
12449 part of the loop after it had made its choice slightly slower
12450 than it ran through the part of the loop before it had made its
12451 choice. Addresses ticket 6538.
12452 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
12453 by tor2web clients allows hidden services to identify tor2web
12454 clients through their repeated selection of the same rendezvous
12455 and introduction point circuit endpoints (their guards). Resolves
12459 - Enable Tor to read configuration, state, and key information from
12460 a FIFO. Previously Tor would only read from files with a positive
12461 stat.st_size. Code from meejah; fixes bug 6044.
12464 - Correct file sizes when reading binary files on Cygwin, to avoid
12465 a bug where Tor would fail to read its state file. Fixes bug 6844;
12466 bugfix on 0.1.2.7-alpha.
12467 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
12468 bugfix on 0.2.0.3-alpha.
12469 - When complaining about a client port on a public address, log
12470 which address we're complaining about. Fixes bug 4020; bugfix on
12471 0.2.3.3-alpha. Patch by Tom Fitzhenry.
12472 - Convert an assert in the pathbias code to a log message. The assert
12473 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
12474 bugfix on 0.2.3.17-beta.
12475 - Our new buildsystem was overzealous about rebuilding manpages: it
12476 would rebuild them all whenever any one of them changed. Now our
12477 dependency checking should be correct. Fixes bug 6843; bugfix on
12479 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
12480 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
12481 - Correct log printout about which address family is preferred
12482 when connecting to a bridge with both an IPv4 and IPv6 OR port.
12483 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
12485 o Minor bugfixes (code cleanliness):
12486 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
12487 with large values. This situation was untriggered, but nevertheless
12488 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
12489 - Reject consensus votes with more than 64 known-flags. We aren't even
12490 close to that limit yet, and our code doesn't handle it correctly.
12491 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
12492 - Avoid undefined behavior when parsing the list of supported
12493 rendezvous/introduction protocols in a hidden service descriptor.
12494 Previously, Tor would have confused (as-yet-unused) protocol version
12495 numbers greater than 32 with lower ones on many platforms. Fixes
12496 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
12497 - Fix handling of rendezvous client authorization types over 8.
12498 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
12499 - Fix building with older versions of GCC (2.95, for one) that don't
12500 like preprocessor directives inside macro arguments. Found by
12501 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
12502 - Switch weighted node selection rule from using a list of doubles
12503 to using a list of int64_t. This change should make the process
12504 slightly easier to debug and maintain. Needed to finish ticket 6538.
12506 o Code simplification and refactoring:
12507 - Move the generic "config" code into a new file, and have "config.c"
12508 hold only torrc- and state-related code. Resolves ticket 6823.
12509 - Move the core of our "choose a weighted element at random" logic
12510 into its own function, and give it unit tests. Now the logic is
12511 testable, and a little less fragile too.
12512 - Removed the testing_since field of node_t, which hasn't been used
12513 for anything since 0.2.0.9-alpha.
12515 o Documentation fixes:
12516 - Clarify that hidden services are TCP only. Fixes bug 6024.
12517 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
12521 Changes in version 0.2.3.22-rc - 2012-09-11
12522 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
12526 - Fix an assertion failure in tor_timegm() that could be triggered
12527 by a badly formatted directory object. Bug found by fuzzing with
12528 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12531 - Avoid segfault when starting up having run with an extremely old
12532 version of Tor and parsing its state file. Fixes bug 6801; bugfix
12536 Changes in version 0.2.2.39 - 2012-09-11
12537 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
12541 - Fix an assertion failure in tor_timegm() that could be triggered
12542 by a badly formatted directory object. Bug found by fuzzing with
12543 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12544 - Do not crash when comparing an address with port value 0 to an
12545 address policy. This bug could have been used to cause a remote
12546 assertion failure by or against directory authorities, or to
12547 allow some applications to crash clients. Fixes bug 6690; bugfix
12551 Changes in version 0.2.4.2-alpha - 2012-09-10
12552 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
12553 raises the default rate limiting even more, and makes the bootstrapping
12554 log messages less noisy.
12557 - Automatically forward the TCP ports of pluggable transport
12558 proxies using tor-fw-helper if PortForwarding is enabled. Implements
12562 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
12563 to 1GB/1GB. The previous defaults were intended to be "basically
12564 infinite", but it turns out they're now limiting our 100mbit+
12565 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
12566 last time we raised it).
12569 - Detect when we're running with a version of OpenSSL other than the
12570 one we compiled with. This has occasionally given people hard-to-
12572 - Log fewer lines at level "notice" about our OpenSSL and Libevent
12573 versions and capabilities when everything is going right. Resolves
12574 part of ticket 6736.
12575 - Directory authorities no long accept descriptors for any version of
12576 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
12577 These versions are insecure, unsupported, or both. Implements
12581 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
12582 to start with a triple-underscore so the controller won't touch it.
12583 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
12584 - Avoid segfault when starting up having run with an extremely old
12585 version of Tor and parsing its state file. Fixes bug 6801; bugfix
12587 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
12588 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
12589 - Don't follow the NULL pointer if microdescriptor generation fails.
12590 (This does not appear to be triggerable, but it's best to be safe.)
12591 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
12592 - Fix mis-declared dependencies on src/common/crypto.c and
12593 src/or/tor_main.c that could break out-of-tree builds under some
12594 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
12595 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
12596 6778; bugfix on 0.2.4.1-alpha.
12597 - Fix a harmless (in this case) build warning for implicitly
12598 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
12600 o Removed features:
12601 - Now that all versions before 0.2.2.x are disallowed, we no longer
12602 need to work around their missing features. Thus we can remove a
12603 bunch of compatibility code.
12605 o Code refactoring:
12606 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
12607 TCP ports to forward. In the past it only accepted two ports:
12608 the ORPort and the DirPort.
12611 Changes in version 0.2.4.1-alpha - 2012-09-05
12612 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
12613 bridgedb; lets relays use IPv6 addresses and directory authorities
12614 advertise them; and switches to a cleaner build interface.
12616 This is the first alpha release in a new series, so expect there to
12617 be bugs. Users who would rather test out a more stable branch should
12618 stay with 0.2.3.x for now.
12620 o Major features (bridges):
12621 - Bridges now report the pluggable transports they support to the
12622 bridge authority, so it can pass the supported transports on to
12623 bridgedb and/or eventually do reachability testing. Implements
12626 o Major features (IPv6):
12627 - Bridge authorities now accept IPv6 bridge addresses and include
12628 them in network status documents. Implements ticket 5534.
12629 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
12630 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
12631 to happen. Implements ticket 5535.
12632 - All kind of relays, not just bridges, can now advertise an IPv6
12633 OR port. Implements ticket 6362.
12634 - Directory authorities vote on IPv6 OR ports using the new consensus
12635 method 14. Implements ticket 6363.
12637 o Major features (build):
12638 - Switch to a nonrecursive Makefile structure. Now instead of each
12639 Makefile.am invoking other Makefile.am's, there is a master
12640 Makefile.am that includes the others. This change makes our build
12641 process slightly more maintainable, and improves parallelism for
12642 building with make -j. Original patch by Stewart Smith; various
12643 fixes by Jim Meyering.
12644 - Where available, we now use automake's "silent" make rules by
12645 default, so that warnings are easier to spot. You can get the old
12646 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
12648 o Minor features (code security and spec conformance):
12649 - Clear keys and key-derived material left on the stack in
12650 rendservice.c and rendclient.c. Check return value of
12651 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
12652 These fixes should make us more forward-secure against cold-boot
12653 attacks and the like. Fixes bug 2385.
12654 - Reject EXTEND cells sent to nonexistent streams. According to the
12655 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
12656 we were only checking for stream IDs that were currently in use.
12657 Found while hunting for more instances of bug 6271. Bugfix on
12658 0.0.2pre8, which introduced incremental circuit construction.
12660 o Minor features (streamlining);
12661 - No longer include the "opt" prefix when generating routerinfos
12662 or v2 directories: it has been needless since Tor 0.1.2. Closes
12664 - Remove some now-needless code that tried to aggressively flush
12665 OR connections as data was added to them. Since 0.2.0.1-alpha, our
12666 cell queue logic has saved us from the failure mode that this code
12667 was supposed to prevent. Removing this code will limit the number
12668 of baroque control flow paths through Tor's network logic. Reported
12669 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
12671 o Minor features (controller):
12672 - Add a "GETINFO signal/names" control port command. Implements
12674 - Provide default values for all options via "GETINFO config/defaults".
12675 Implements ticket 4971.
12677 o Minor features (IPv6):
12678 - New config option "AuthDirHasIPv6Connectivity 1" that directory
12679 authorities should set if they have IPv6 connectivity and want to
12680 do reachability tests for IPv6 relays. Implements feature 5974.
12681 - A relay with an IPv6 OR port now sends that address in NETINFO
12682 cells (in addition to its other address). Implements ticket 6364.
12684 o Minor features (log messages):
12685 - Omit the first heartbeat log message, because it never has anything
12686 useful to say, and it clutters up the bootstrapping messages.
12687 Resolves ticket 6758.
12688 - Don't log about reloading the microdescriptor cache at startup. Our
12689 bootstrap warnings are supposed to tell the user when there's a
12690 problem, and our bootstrap notices say when there isn't. Resolves
12691 ticket 6759; bugfix on 0.2.2.6-alpha.
12692 - Don't log "I learned some more directory information" when we're
12693 reading cached directory information. Reserve it for when new
12694 directory information arrives in response to a fetch. Resolves
12696 - Prevent rounding error in path bias counts when scaling
12697 them down, and use the correct scale factor default. Also demote
12698 some path bias related log messages down a level and make others
12699 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
12700 - We no longer warn so much when generating manpages from their
12703 o Code simplifications and refactoring:
12704 - Enhance our internal sscanf replacement so that we can eliminate
12705 the last remaining uses of the system sscanf. (Though those uses
12706 of sscanf were safe, sscanf itself is generally error prone, so
12707 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
12709 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
12710 - Move last_reachable and testing_since from routerinfo_t to node_t.
12711 Implements ticket 5529.
12712 - Add replaycache_t structure, functions and unit tests, then refactor
12713 rend_service_introduce() to be more clear to read, improve, debug,
12714 and test. Resolves bug 6177.
12715 - Finally remove support for malloc_good_size and malloc_usable_size.
12716 We had hoped that these functions would let us eke a little more
12717 memory out of our malloc implementation. Unfortunately, the only
12718 implementations that provided these functions are also ones that
12719 are already efficient about not overallocation: they never got us
12720 more than 7 or so bytes per allocation. Removing them saves us a
12721 little code complexity and a nontrivial amount of build complexity.
12723 o New requirements:
12724 - Tor maintainers now require Automake version 1.9 or later to build
12725 Tor from the Git repository. (Automake is not required when building
12726 from a source distribution.)
12729 Changes in version 0.2.3.21-rc - 2012-09-05
12730 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
12731 series. It fixes a trio of potential security bugs, fixes a bug where
12732 we were leaving some of the fast relays out of the microdescriptor
12733 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
12734 and cleans up other smaller issues.
12736 o Major bugfixes (security):
12737 - Tear down the circuit if we get an unexpected SENDME cell. Clients
12738 could use this trick to make their circuits receive cells faster
12739 than our flow control would have allowed, or to gum up the network,
12740 or possibly to do targeted memory denial-of-service attacks on
12741 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
12742 from July 2002, before the release of Tor 0.0.0. We had committed
12743 this patch previously, but we had to revert it because of bug 6271.
12744 Now that 6271 is fixed, this patch appears to work.
12745 - Reject any attempt to extend to an internal address. Without
12746 this fix, a router could be used to probe addresses on an internal
12747 network to see whether they were accepting connections. Fixes bug
12748 6710; bugfix on 0.0.8pre1.
12749 - Do not crash when comparing an address with port value 0 to an
12750 address policy. This bug could have been used to cause a remote
12751 assertion failure by or against directory authorities, or to
12752 allow some applications to crash clients. Fixes bug 6690; bugfix
12756 - Remove the upper bound on microdescriptor length. We were hitting
12757 the limit for routers with complex exit policies or family
12758 declarations, causing clients to not use them. Fixes the first
12759 piece of bug 6404; fix on 0.2.2.6-alpha.
12760 - Detect "ORPort 0" as meaning, uniformly, that we're not running
12761 as a relay. Previously, some of our code would treat the presence
12762 of any ORPort line as meaning that we should act like a relay,
12763 even though our new listener code would correctly not open any
12764 ORPorts for ORPort 0. Similar bugs in other Port options are also
12765 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
12768 - Avoid a pair of double-free and use-after-mark bugs that can
12769 occur with certain timings in canceled and re-received DNS
12770 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
12771 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
12772 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
12773 - Allow one-hop directory fetching circuits the full "circuit build
12774 timeout" period, rather than just half of it, before failing them
12775 and marking the relay down. This fix should help reduce cases where
12776 clients declare relays (or worse, bridges) unreachable because
12777 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
12778 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
12780 - Authorities no longer include any router in their microdescriptor
12781 consensuses for which they couldn't generate or agree on a
12782 microdescriptor. Fixes the second piece of bug 6404; fix on
12784 - Detect and reject attempts to specify both "FooPort" and
12785 "FooPort 0" in the same configuration domain. (It's still okay
12786 to have a FooPort in your configuration file, and use "FooPort 0"
12787 on the command line to disable it.) Fixes the second half of bug
12788 6507; bugfix on 0.2.3.3-alpha.
12789 - Make wildcarded addresses (that is, ones beginning with "*.") work
12790 when provided via the controller's MapAddress command. Previously,
12791 they were accepted, but we never actually noticed that they were
12792 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
12793 - Avoid crashing on a malformed state file where EntryGuardPathBias
12794 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
12795 - Add a (probably redundant) memory clear between iterations of
12796 the router status voting loop, to prevent future coding errors
12797 where data might leak between iterations of the loop. Resolves
12800 o Minor bugfixes (log messages):
12801 - Downgrade "set buildtimeout to low value" messages to "info"
12802 severity; they were never an actual problem, there was never
12803 anything reasonable to do about them, and they tended to spam logs
12804 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
12805 - Downgrade path-bias warning messages to "info". We'll try to get
12806 them working better in 0.2.4. Add internal circuit construction
12807 state to protect against the noisy warn message "Unexpectedly high
12808 circuit_successes". Also add some additional rate-limited notice
12809 messages to help determine the root cause of the warn. Fixes bug
12810 6475. Bugfix against 0.2.3.17-beta.
12811 - Move log message when unable to find a microdesc in a routerstatus
12812 entry to parse time. Previously we'd spam this warning every time
12813 we tried to figure out which microdescriptors to download. Fixes
12814 the third piece of bug 6404; fix on 0.2.3.18-rc.
12817 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
12818 change when the authority is deciding whether to accept a newly
12819 uploaded descriptor. Implements ticket 6423.
12820 - Add missing documentation for consensus and microdesc files.
12821 Resolves ticket 6732.
12824 Changes in version 0.2.2.38 - 2012-08-12
12825 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
12826 attack that could in theory leak path information.
12829 - Avoid an uninitialized memory read when reading a vote or consensus
12830 document that has an unrecognized flavor name. This read could
12831 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12832 - Try to leak less information about what relays a client is
12833 choosing to a side-channel attacker. Previously, a Tor client would
12834 stop iterating through the list of available relays as soon as it
12835 had chosen one, thus finishing a little earlier when it picked
12836 a router earlier in the list. If an attacker can recover this
12837 timing information (nontrivial but not proven to be impossible),
12838 they could learn some coarse-grained information about which relays
12839 a client was picking (middle nodes in particular are likelier to
12840 be affected than exits). The timing attack might be mitigated by
12841 other factors (see bug 6537 for some discussion), but it's best
12842 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12845 Changes in version 0.2.3.20-rc - 2012-08-05
12846 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
12847 series. It fixes a pair of code security bugs and a potential anonymity
12848 issue, updates our RPM spec files, and cleans up other smaller issues.
12851 - Avoid read-from-freed-memory and double-free bugs that could occur
12852 when a DNS request fails while launching it. Fixes bug 6480;
12853 bugfix on 0.2.0.1-alpha.
12854 - Avoid an uninitialized memory read when reading a vote or consensus
12855 document that has an unrecognized flavor name. This read could
12856 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12857 - Try to leak less information about what relays a client is
12858 choosing to a side-channel attacker. Previously, a Tor client would
12859 stop iterating through the list of available relays as soon as it
12860 had chosen one, thus finishing a little earlier when it picked
12861 a router earlier in the list. If an attacker can recover this
12862 timing information (nontrivial but not proven to be impossible),
12863 they could learn some coarse-grained information about which relays
12864 a client was picking (middle nodes in particular are likelier to
12865 be affected than exits). The timing attack might be mitigated by
12866 other factors (see bug 6537 for some discussion), but it's best
12867 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12870 - Try to make the warning when giving an obsolete SOCKSListenAddress
12871 a little more useful.
12872 - Terminate active server managed proxies if Tor stops being a
12873 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
12874 - Provide a better error message about possible OSX Asciidoc failure
12875 reasons. Fixes bug 6436.
12876 - Warn when Tor is configured to use accounting in a way that can
12877 link a hidden service to some other hidden service or public
12878 address. Resolves ticket 6490.
12881 - Check return value of fputs() when writing authority certificate
12882 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
12883 - Ignore ServerTransportPlugin lines when Tor is not configured as
12884 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
12885 - When disabling guards for having too high a proportion of failed
12886 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
12890 - Update our default RPM spec files to work with mock and rpmbuild
12891 on RHEL/Fedora. They have an updated set of dependencies and
12892 conflicts, a fix for an ancient typo when creating the "_tor"
12893 user, and better instructions. Thanks to Ondrej Mikle for the
12894 patch series. Fixes bug 6043.
12897 - Make it possible to set the TestingTorNetwork configuration
12898 option using AlternateDirAuthority and AlternateBridgeAuthority
12899 as an alternative to setting DirServer. Addresses ticket 6377.
12902 - Clarify the documentation for the Alternate*Authority options.
12904 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
12906 o Code simplification and refactoring:
12907 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
12908 10 lines. Also, don't nest them. Doing so in the past has
12909 led to hard-to-debug code. The new style is to use the
12910 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
12913 Changes in version 0.2.3.19-rc - 2012-07-06
12914 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
12915 series. It fixes the compile on Windows, reverts to a GeoIP database
12916 that isn't as broken, and fixes a flow control bug that has been around
12917 since the beginning of Tor.
12920 - Fix a bug handling SENDME cells on nonexistent streams that could
12921 result in bizarre window values. Report and patch contributed
12922 pseudonymously. Fixes part of bug 6271. This bug was introduced
12923 before the first Tor release, in svn commit r152.
12924 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
12925 June 2012 database, Maxmind marked many Tor relays as country "A1",
12926 which will cause risky behavior for clients that set EntryNodes
12927 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
12928 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
12929 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
12932 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
12933 bugfix on 0.2.1.10-alpha.
12936 Changes in version 0.2.3.18-rc - 2012-06-28
12937 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
12938 series. It fixes a few smaller bugs, but generally appears stable.
12939 Please test it and let us know whether it is!
12942 - Allow wildcarded mapaddress targets to be specified on the
12943 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
12944 - Make our linker option detection code more robust against linkers
12945 such as on FreeBSD 8, where a bad combination of options completes
12946 successfully but makes an unrunnable binary. Fixes bug 6173;
12947 bugfix on 0.2.3.17-beta.
12949 o Minor bugfixes (on 0.2.2.x and earlier):
12950 - Avoid a false positive in the util/threads unit test by increasing
12951 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
12952 - Replace "Sending publish request" log messages with "Launching
12953 upload", so that they no longer confusingly imply that we're
12954 sending something to a directory we might not even be connected
12955 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
12956 - Make sure to set *socket_error in all error cases in
12957 connection_connect(), so it can't produce a warning about
12958 errno being zero from errno_to_orconn_end_reason(). Bugfix on
12959 0.2.1.1-alpha; resolves ticket 6028.
12960 - Downgrade "Got a certificate, but we already have it" log messages
12961 from warning to info, except when we're a dirauth. Fixes bug 5238;
12962 bugfix on 0.2.1.7-alpha.
12963 - When checking for requested signatures on the latest consensus
12964 before serving it to a client, make sure to check the right
12965 consensus flavor. Bugfix on 0.2.2.6-alpha.
12966 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
12967 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
12969 o Minor bugfixes (on 0.2.3.x):
12970 - Make format_helper_exit_status() avoid unnecessary space padding
12971 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
12973 - Downgrade a message about cleaning the microdescriptor cache to
12974 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
12975 - Log a BUG message at severity INFO if we have a networkstatus with
12976 a missing entry for some microdescriptor. Continues on a patch
12978 - Improve the log message when a managed proxy fails to launch. Fixes
12979 bug 5099; bugfix on 0.2.3.6-alpha.
12980 - Don't do DNS lookups when parsing corrupted managed proxy protocol
12981 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
12982 - When formatting wildcarded address mappings for the controller,
12983 be sure to include "*." as appropriate. Partially fixes bug 6244;
12984 bugfix on 0.2.3.9-alpha.
12985 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
12986 Bugfix on 0.2.3.13-alpha.
12987 - Stop logging messages about running with circuit timeout learning
12988 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
12989 - Disable a spurious warning about reading on a marked and flushing
12990 connection. We shouldn't be doing that, but apparently we
12991 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
12992 - Fix a bug that stopped AllowDotExit from working on addresses
12993 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
12996 o Code simplification, refactoring, unit tests:
12997 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
12998 Libevent's notion of cached time when possible.
12999 - Remove duplicate code for invoking getrlimit() from control.c.
13000 - Add a unit test for the environment_variable_names_equal function.
13003 - Document the --defaults-torrc option, and the new (in 0.2.3)
13004 semantics for overriding, extending, and clearing lists of
13005 options. Closes bug 4748.
13008 Changes in version 0.2.3.17-beta - 2012-06-15
13009 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
13010 gets our TLS handshake back on track for being able to blend in with
13011 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
13012 with Vidalia, and otherwise continues to get us closer to a release
13016 - Enable gcc and ld hardening by default. Resolves ticket 5210.
13017 - Update TLS cipher list to match Firefox 8 and later. Resolves
13019 - Implement the client side of proposal 198: remove support for
13020 clients falsely claiming to support standard ciphersuites that
13021 they can actually provide. As of modern OpenSSL versions, it's not
13022 necessary to fake any standard ciphersuite, and doing so prevents
13023 us from using better ciphersuites in the future, since servers
13024 can't know whether an advertised ciphersuite is really supported or
13025 not. Some hosts -- notably, ones with very old versions of OpenSSL
13026 or where OpenSSL has been built with ECC disabled -- will stand
13027 out because of this change; TBB users should not be affected.
13030 - Change the default value for DynamicDHGroups (introduced in
13031 0.2.3.9-alpha) to 0. This feature can make Tor relays less
13032 identifiable by their use of the mod_ssl DH group, but at
13033 the cost of some usability (#4721) and bridge tracing (#6087)
13034 regressions. Resolves ticket 5598.
13035 - Send a CRLF at the end of each STATUS_* control protocol event. This
13036 bug tickled a bug in Vidalia which would make it freeze. Fixes
13037 bug 6094; bugfix on 0.2.3.16-alpha.
13040 - Disable writing on marked-for-close connections when they are
13041 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
13042 bug 5263; bugfix on 0.0.2pre13, where we first added a special
13043 case for flushing marked connections.
13044 - Detect SSL handshake even when the initial attempt to write the
13045 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
13046 - Change the AllowDotExit rules so they should actually work.
13047 We now enforce AllowDotExit only immediately after receiving an
13048 address via SOCKS or DNSPort: other sources are free to provide
13049 .exit addresses after the resolution occurs. Fixes bug 3940;
13050 bugfix on 0.2.2.1-alpha.
13051 - Fix a (harmless) integer overflow in cell statistics reported by
13052 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
13053 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
13054 right places and never depends on the consensus parameters or
13055 computes adaptive timeouts when it is disabled. Fixes bug 5049;
13056 bugfix on 0.2.2.14-alpha.
13057 - When building Tor on Windows with -DUNICODE (not default), ensure
13058 that error messages, filenames, and DNS server names are always
13059 NUL-terminated when we convert them to a single-byte encoding.
13060 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
13061 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
13062 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
13063 - Fix an edge case where TestingTorNetwork is set but the authorities
13064 and relays all have an uptime of zero, where the private Tor network
13065 could briefly lack support for hidden services. Fixes bug 3886;
13066 bugfix on 0.2.2.18-alpha.
13067 - Correct the manpage's descriptions for the default values of
13068 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
13070 - Fix the documentation for the --hush and --quiet command line
13071 options, which changed their behavior back in 0.2.3.3-alpha.
13072 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
13076 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
13077 more information to it, so that we can track it down in case it
13078 returns again. Mitigates bug 5235.
13079 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
13080 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
13081 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
13082 - Warn the user when HTTPProxy, but no other proxy type, is
13083 configured. This can cause surprising behavior: it doesn't send
13084 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
13085 directory traffic only. Resolves ticket 4663.
13086 - Issue a notice if a guard completes less than 40% of your circuits.
13087 Threshold is configurable by torrc option PathBiasNoticeRate and
13088 consensus parameter pb_noticepct. There is additional, off-by-
13089 default code to disable guards which fail too many circuits.
13090 Addresses ticket 5458.
13091 - Update to the June 6 2012 Maxmind GeoLite Country database.
13093 o Code simplifications and refactoring:
13094 - Remove validate_pluggable_transports_config(): its warning
13095 message is now handled by connection_or_connect().
13098 Changes in version 0.2.2.37 - 2012-06-06
13099 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
13100 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
13104 - Work around a bug in OpenSSL that broke renegotiation with TLS
13105 1.1 and TLS 1.2. Without this workaround, all attempts to speak
13106 the v2 Tor connection protocol when both sides were using OpenSSL
13107 1.0.1 would fail. Resolves ticket 6033.
13108 - When waiting for a client to renegotiate, don't allow it to add
13109 any bytes to the input buffer. This fixes a potential DoS issue.
13110 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
13111 - Fix an edge case where if we fetch or publish a hidden service
13112 descriptor, we might build a 4-hop circuit and then use that circuit
13113 for exiting afterwards -- even if the new last hop doesn't obey our
13114 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
13117 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
13118 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
13121 - Tell GCC and Clang to check for any errors in format strings passed
13122 to the tor_v*(print|scan)f functions.
13125 Changes in version 0.2.3.16-alpha - 2012-06-05
13126 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
13127 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
13128 currently). It also fixes a variety of smaller bugs and other cleanups
13129 that get us closer to a release candidate.
13131 o Major bugfixes (general):
13132 - Work around a bug in OpenSSL that broke renegotiation with TLS
13133 1.1 and TLS 1.2. Without this workaround, all attempts to speak
13134 the v2 Tor connection protocol when both sides were using OpenSSL
13135 1.0.1 would fail. Resolves ticket 6033.
13136 - When waiting for a client to renegotiate, don't allow it to add
13137 any bytes to the input buffer. This fixes a potential DoS issue.
13138 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
13139 - Pass correct OR address to managed proxies (like obfsproxy),
13140 even when ORListenAddress is used. Fixes bug 4865; bugfix on
13142 - The advertised platform of a router now includes only its operating
13143 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
13144 service pack level (for Windows) or its CPU architecture (for Unix).
13145 We also no longer include the "git-XYZ" tag in the version. Resolves
13148 o Major bugfixes (clients):
13149 - If we are unable to find any exit that supports our predicted ports,
13150 stop calling them predicted, so that we don't loop and build
13151 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
13152 which introduced predicted ports.
13153 - Fix an edge case where if we fetch or publish a hidden service
13154 descriptor, we might build a 4-hop circuit and then use that circuit
13155 for exiting afterwards -- even if the new last hop doesn't obey our
13156 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
13157 - Check at each new consensus whether our entry guards were picked
13158 long enough ago that we should rotate them. Previously, we only
13159 did this check at startup, which could lead to us holding a guard
13160 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
13161 - When fetching a bridge descriptor from a bridge authority,
13162 always do so anonymously, whether we have been able to open
13163 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
13164 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
13165 but we'll need to wait for bug 6010 before it's actually usable.
13167 o Major bugfixes (directory authorities):
13168 - When computing weight parameters, behave more robustly in the
13169 presence of a bad bwweightscale value. Previously, the authorities
13170 would crash if they agreed on a sufficiently broken weight_scale
13171 value: now, they use a reasonable default and carry on. Partial
13172 fix for 5786; bugfix on 0.2.2.17-alpha.
13173 - Check more thoroughly to prevent a rogue authority from
13174 double-voting on any consensus directory parameter. Previously,
13175 authorities would crash in this case if the total number of
13176 votes for any parameter exceeded the number of active voters,
13177 but would let it pass otherwise. Partial fix for bug 5786; bugfix
13181 - Rate-limit log messages when asked to connect anonymously to
13182 a private address. When these hit, they tended to hit fast and
13183 often. Also, don't bother trying to connect to addresses that we
13184 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
13185 reply makes us think we have been lied to, even when the address the
13186 client tried to connect to was "localhost." Resolves ticket 2822.
13187 - Allow packagers to insert an extra string in server descriptor
13188 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
13189 Resolves the rest of ticket 2988.
13190 - Raise the threshold of server descriptors needed (75%) and exit
13191 server descriptors needed (50%) before we will declare ourselves
13192 bootstrapped. This will make clients start building circuits a
13193 little later, but makes the initially constructed circuits less
13194 skewed and less in conflict with further directory fetches. Fixes
13196 - Close any connection that sends unrecognized junk before the
13197 handshake. Solves an issue noted in bug 4369.
13198 - Improve log messages about managed transports. Resolves ticket 5070.
13199 - Tag a bridge's descriptor as "never to be sent unencrypted".
13200 This shouldn't matter, since bridges don't open non-anonymous
13201 connections to the bridge authority and don't allow unencrypted
13202 directory connections from clients, but we might as well make
13203 sure. Closes bug 5139.
13204 - Expose our view of whether we have gone dormant to the controller,
13205 via a new "GETINFO dormant" value. Torbutton and other controllers
13206 can use this to avoid doing periodic requests through Tor while
13207 it's dormant (bug 4718). Fixes bug 5954.
13208 - Tell GCC and Clang to check for any errors in format strings passed
13209 to the tor_v*(print|scan)f functions.
13210 - Update to the May 1 2012 Maxmind GeoLite Country database.
13212 o Minor bugfixes (already included in 0.2.2.36):
13213 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
13214 Fixes bug 5346; bugfix on 0.0.8pre3.
13215 - Correct parsing of certain date types in parse_http_time().
13216 Without this patch, If-Modified-Since would behave
13217 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
13218 Esteban Manchado Velázques.
13219 - Make our number-parsing functions always treat too-large values
13220 as an error, even when those values exceed the width of the
13221 underlying type. Previously, if the caller provided these
13222 functions with minima or maxima set to the extreme values of the
13223 underlying integer type, these functions would return those
13224 values on overflow rather than treating overflow as an error.
13225 Fixes part of bug 5786; bugfix on 0.0.9.
13226 - If we hit the error case where routerlist_insert() replaces an
13227 existing (old) server descriptor, make sure to remove that
13228 server descriptor from the old_routers list. Fix related to bug
13229 1776. Bugfix on 0.2.2.18-alpha.
13230 - Clarify the behavior of MaxCircuitDirtiness with hidden service
13231 circuits. Fixes issue 5259.
13233 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
13234 - Prevent a null-pointer dereference when receiving a data cell
13235 for a nonexistent stream when the circuit in question has an
13236 empty deliver window. We don't believe this is triggerable,
13237 since we don't currently allow deliver windows to become empty,
13238 but the logic is tricky enough that it's better to make the code
13239 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
13240 - Fix a memory leak when trying to launch a DNS request when the
13241 network is disabled or the nameservers are unconfigurable. Fixes
13242 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
13243 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
13244 - Don't hold a Windows file handle open for every file mapping;
13245 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
13247 - Avoid O(n^2) performance characteristics when parsing a large
13248 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
13249 - Format more doubles with %f, not %lf. Patch from grarpamp to make
13250 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
13252 - Make our replacement implementation of strtok_r() compatible with
13253 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
13254 bugfix on 0.2.2.1-alpha.
13255 - Fix a NULL-pointer dereference on a badly formed
13256 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
13257 bugfix on 0.2.2.9-alpha.
13258 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
13259 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
13260 - Defensively refactor rend_mid_rendezvous() so that protocol
13261 violations and length checks happen in the beginning. Fixes
13263 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
13264 that IPv6 stuff will compile on MSVC, and compilation issues
13265 will be easier to track down. Fixes bug 5861.
13267 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
13268 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
13269 resource exhaustion, so that clients can adjust their load to
13270 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
13271 started using END_STREAM_REASON_RESOURCELIMIT.
13272 - Don't check for whether the address we're using for outbound
13273 connections has changed until after the outbound connection has
13274 completed. On Windows, getsockname() doesn't succeed until the
13275 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
13276 - If the configuration tries to set MyFamily on a bridge, refuse to
13277 do so, and warn about the security implications. Fixes bug 4657;
13278 bugfix on 0.2.0.3-alpha.
13279 - If the client fails to set a reasonable set of ciphersuites
13280 during its v2 handshake renegotiation, allow the renegotiation to
13281 continue nevertheless (i.e. send all the required certificates).
13282 Fixes bug 4591; bugfix on 0.2.0.20-rc.
13283 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
13284 option is set to 0 (which Vidalia version 0.2.16 now does when
13285 a SAVECONF attempt fails), perform other actions that SIGHUP
13286 usually causes (like reopening the logs). Fixes bug 5095; bugfix
13288 - If we fail to write a microdescriptor to the disk cache, do not
13289 continue replacing the old microdescriptor file. Fixes bug 2954;
13290 bugfix on 0.2.2.6-alpha.
13291 - Exit nodes don't need to fetch certificates for authorities that
13292 they don't recognize; only directory authorities, bridges,
13293 and caches need to do that. Fixes part of bug 2297; bugfix on
13295 - Correctly handle checking the permissions on the parent
13296 directory of a control socket in the root directory. Bug found
13297 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
13299 - When told to add a bridge with the same digest as a preexisting
13300 bridge but a different addr:port, change the addr:port as
13301 requested. Previously we would not notice the change. Fixes half
13302 of bug 5603; fix on 0.2.2.26-beta.
13303 - End AUTHCHALLENGE error messages (in the control protocol) with
13304 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
13306 o Minor bugfixes (on 0.2.3.x):
13307 - Turn an assertion (that the number of handshakes received as a
13308 server is not < 1) into a warning. Fixes bug 4873; bugfix on
13310 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
13311 we had reversed them when the answer was cached.) Fixes bug
13312 5723; bugfix on 0.2.3.1-alpha.
13313 - Work correctly on Linux systems with accept4 support advertised in
13314 their headers, but without accept4 support in the kernel. Fix
13315 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
13316 - When told to add a bridge with the same addr:port as a preexisting
13317 bridge but a different transport, change the transport as
13318 requested. Previously we would not notice the change. Fixes half
13319 of bug 5603; fix on 0.2.3.2-alpha.
13320 - Avoid a "double-reply" warning when replying to a SOCKS request
13321 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
13322 bugfix on 0.2.3.4-alpha.
13323 - Fix a bug where a bridge authority crashes if it has seen no
13324 directory requests when it's time to write statistics to disk.
13325 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
13327 - Don't try to open non-control listeners when DisableNetwork is set.
13328 Previously, we'd open all listeners, then immediately close them.
13329 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
13330 - Don't abort the managed proxy protocol if the managed proxy
13331 sends us an unrecognized line; ignore it instead. Fixes bug
13332 5910; bugfix on 0.2.3.9-alpha.
13333 - Fix a compile warning in crypto.c when compiling with clang 3.1.
13334 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
13335 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
13336 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
13337 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
13338 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
13339 - Resolve numerous small warnings and build issues with MSVC. Resolves
13342 o Documentation fixes:
13343 - Improve the manual's documentation for the NT Service command-line
13344 options. Addresses ticket 3964.
13345 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
13346 - Document the changes to the ORPort and DirPort options, and the
13347 fact that {OR/Dir}ListenAddress is now unnecessary (and
13348 therefore deprecated). Resolves ticket 5597.
13351 - Remove the torrc.bridge file: we don't use it for anything, and
13352 it had become badly desynchronized from torrc.sample. Resolves
13356 Changes in version 0.2.2.36 - 2012-05-24
13357 Tor 0.2.2.36 updates the addresses for two of the eight directory
13358 authorities, fixes some potential anonymity and security issues,
13359 and fixes several crash bugs.
13361 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
13362 known flaws, and nobody should be using them. You should upgrade. If
13363 you're using a Linux or BSD and its packages are obsolete, stop using
13364 those packages and upgrade anyway.
13366 o Directory authority changes:
13367 - Change IP address for maatuska (v3 directory authority).
13368 - Change IP address for ides (v3 directory authority), and rename
13372 - When building or running with any version of OpenSSL earlier
13373 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
13374 versions have a bug (CVE-2011-4576) in which their block cipher
13375 padding includes uninitialized data, potentially leaking sensitive
13376 information to any peer with whom they make a SSLv3 connection. Tor
13377 does not use SSL v3 by default, but a hostile client or server
13378 could force an SSLv3 connection in order to gain information that
13379 they shouldn't have been able to get. The best solution here is to
13380 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
13381 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
13382 to make sure that the bug can't happen.
13383 - Never use a bridge or a controller-supplied node as an exit, even
13384 if its exit policy allows it. Found by wanoskarnet. Fixes bug
13385 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
13386 and 0.2.0.3-alpha (for bridge-purpose descriptors).
13387 - Only build circuits if we have a sufficient threshold of the total
13388 descriptors that are marked in the consensus with the "Exit"
13389 flag. This mitigates an attack proposed by wanoskarnet, in which
13390 all of a client's bridges collude to restrict the exit nodes that
13391 the client knows about. Fixes bug 5343.
13392 - Provide controllers with a safer way to implement the cookie
13393 authentication mechanism. With the old method, if another locally
13394 running program could convince a controller that it was the Tor
13395 process, then that program could trick the controller into telling
13396 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
13397 authentication method uses a challenge-response approach to prevent
13398 this attack. Fixes bug 5185; implements proposal 193.
13401 - Avoid logging uninitialized data when unable to decode a hidden
13402 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
13403 - Avoid a client-side assertion failure when receiving an INTRODUCE2
13404 cell on a general purpose circuit. Fixes bug 5644; bugfix on
13406 - Fix builds when the path to sed, openssl, or sha1sum contains
13407 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
13409 - Correct our replacements for the timeradd() and timersub() functions
13410 on platforms that lack them (for example, Windows). The timersub()
13411 function is used when expiring circuits, while timeradd() is
13412 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
13413 bugfix on 0.2.2.24-alpha.
13414 - Fix the SOCKET_OK test that we use to tell when socket
13415 creation fails so that it works on Win64. Fixes part of bug 4533;
13416 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
13419 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
13420 Fixes bug 5346; bugfix on 0.0.8pre3.
13421 - Make our number-parsing functions always treat too-large values
13422 as an error, even when those values exceed the width of the
13423 underlying type. Previously, if the caller provided these
13424 functions with minima or maxima set to the extreme values of the
13425 underlying integer type, these functions would return those
13426 values on overflow rather than treating overflow as an error.
13427 Fixes part of bug 5786; bugfix on 0.0.9.
13428 - Older Linux kernels erroneously respond to strange nmap behavior
13429 by having accept() return successfully with a zero-length
13430 socket. When this happens, just close the connection. Previously,
13431 we would try harder to learn the remote address: but there was
13432 no such remote address to learn, and our method for trying to
13433 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
13434 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
13435 - Correct parsing of certain date types in parse_http_time().
13436 Without this patch, If-Modified-Since would behave
13437 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
13438 Esteban Manchado Velázques.
13439 - Change the BridgePassword feature (part of the "bridge community"
13440 design, which is not yet implemented) to use a time-independent
13441 comparison. The old behavior might have allowed an adversary
13442 to use timing to guess the BridgePassword value. Fixes bug 5543;
13443 bugfix on 0.2.0.14-alpha.
13444 - Detect and reject certain misformed escape sequences in
13445 configuration values. Previously, these values would cause us
13446 to crash if received in a torrc file or over an authenticated
13447 control port. Bug found by Esteban Manchado Velázquez, and
13448 independently by Robert Connolly from Matta Consulting who further
13449 noted that it allows a post-authentication heap overflow. Patch
13450 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
13451 bugfix on 0.2.0.16-alpha.
13452 - Fix a compile warning when using the --enable-openbsd-malloc
13453 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
13454 - During configure, detect when we're building with clang version
13455 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
13456 CFLAGS. clang doesn't support them yet.
13457 - When sending an HTTP/1.1 proxy request, include a Host header.
13458 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
13459 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
13460 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
13461 - If we hit the error case where routerlist_insert() replaces an
13462 existing (old) server descriptor, make sure to remove that
13463 server descriptor from the old_routers list. Fix related to bug
13464 1776. Bugfix on 0.2.2.18-alpha.
13466 o Minor bugfixes (documentation and log messages):
13467 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
13468 Fixes bug 4856; bugfix on Tor 0.0.6.
13469 - Update "ClientOnly" man page entry to explain that there isn't
13470 really any point to messing with it. Resolves ticket 5005.
13471 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
13472 directory authority option (introduced in Tor 0.2.2.34).
13473 - Downgrade the "We're missing a certificate" message from notice
13474 to info: people kept mistaking it for a real problem, whereas it
13475 is seldom the problem even when we are failing to bootstrap. Fixes
13476 bug 5067; bugfix on 0.2.0.10-alpha.
13477 - Correctly spell "connect" in a log message on failure to create a
13478 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
13479 - Clarify the behavior of MaxCircuitDirtiness with hidden service
13480 circuits. Fixes issue 5259.
13483 - Directory authorities now reject versions of Tor older than
13484 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
13485 inclusive. These versions accounted for only a small fraction of
13486 the Tor network, and have numerous known security issues. Resolves
13488 - Update to the May 1 2012 Maxmind GeoLite Country database.
13491 - When sending or relaying a RELAY_EARLY cell, we used to convert
13492 it to a RELAY cell if the connection was using the v1 link
13493 protocol. This was a workaround for older versions of Tor, which
13494 didn't handle RELAY_EARLY cells properly. Now that all supported
13495 versions can handle RELAY_EARLY cells, and now that we're enforcing
13496 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
13497 remove this workaround. Addresses bug 4786.
13500 Changes in version 0.2.3.15-alpha - 2012-04-30
13501 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
13502 the development branch build on Windows again.
13504 o Minor bugfixes (on 0.2.2.x and earlier):
13505 - Make sure that there are no unhandled pending TLS errors before
13506 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
13507 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
13508 Bugfix on 0.1.0.5-rc; fixes bug 4528.
13509 - Fix an assert that directory authorities could trigger on sighup
13510 during some configuration state transitions. We now don't treat
13511 it as a fatal error when the new descriptor we just generated in
13512 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
13513 - After we pick a directory mirror, we would refuse to use it if
13514 it's in our ExcludeExitNodes list, resulting in mysterious failures
13515 to bootstrap for people who just wanted to avoid exiting from
13516 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
13517 - When building with --enable-static-tor on OpenBSD, do not
13518 erroneously attempt to link -lrt. Fixes bug 5103.
13520 o Minor bugfixes (on 0.2.3.x):
13521 - When Tor is built with kernel headers from a recent (last few
13522 years) Linux kernel, do not fail to run on older (pre-2.6.28
13523 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
13524 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
13525 and 0.2.3.12-alpha.
13526 - Fix compilation with miniupnpc version 1.6; patch from
13527 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
13528 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
13529 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
13530 - Fix compilation on platforms without unistd.h, or where environ
13531 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
13534 - Directory authorities are now a little more lenient at accepting
13535 older router descriptors, or newer router descriptors that don't
13536 make big changes. This should help ameliorate past and future
13537 issues where routers think they have uploaded valid descriptors,
13538 but the authorities don't think so. Fix for ticket 2479.
13539 - Make the code that clients use to detect an address change be
13540 IPv6-aware, so that it won't fill clients' logs with error
13541 messages when trying to get the IPv4 address of an IPv6
13542 connection. Implements ticket 5537.
13544 o Removed features:
13545 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
13546 authorities needed to use it for a while to keep the network working
13547 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
13548 that was six months ago. As of now, it should no longer be needed
13552 Changes in version 0.2.3.14-alpha - 2012-04-23
13553 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
13554 candidate. It also dramatically speeds up AES: fast relays should
13555 consider switching to the newer OpenSSL library.
13557 o Directory authority changes:
13558 - Change IP address for ides (v3 directory authority), and rename
13562 - Avoid logging uninitialized data when unable to decode a hidden
13563 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
13564 - Avoid a client-side assertion failure when receiving an INTRODUCE2
13565 cell on a general purpose circuit. Fixes bug 5644; bugfix on
13567 - If authorities are unable to get a v2 consensus document from other
13568 directory authorities, they no longer fall back to fetching
13569 them from regular directory caches. Fixes bug 5635; bugfix on
13570 0.2.2.26-beta, where routers stopped downloading v2 consensus
13571 documents entirely.
13572 - When we start a Tor client with a normal consensus already cached,
13573 be willing to download a microdescriptor consensus. Fixes bug 4011;
13574 fix on 0.2.3.1-alpha.
13576 o Major features (performance):
13577 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
13578 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
13579 vectorized AES implementations as appropriate. These can be much,
13580 much faster than other AES implementations.
13582 o Minor bugfixes (0.2.2.x and earlier):
13583 - Don't launch more than 10 service-side introduction-point circuits
13584 for a hidden service in five minutes. Previously, we would consider
13585 launching more introduction-point circuits if at least one second
13586 had passed without any introduction-point circuits failing. Fixes
13587 bug 4607; bugfix on 0.0.7pre1.
13588 - Change the BridgePassword feature (part of the "bridge community"
13589 design, which is not yet implemented) to use a time-independent
13590 comparison. The old behavior might have allowed an adversary
13591 to use timing to guess the BridgePassword value. Fixes bug 5543;
13592 bugfix on 0.2.0.14-alpha.
13593 - Enforce correct return behavior of tor_vsscanf() when the '%%'
13594 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
13595 - When sending an HTTP/1.1 proxy request, include a Host header.
13596 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
13597 - Don't log that we have "decided to publish new relay descriptor"
13598 unless we are actually publishing a descriptor. Fixes bug 3942;
13599 bugfix on 0.2.2.28-beta.
13601 o Minor bugfixes (0.2.3.x):
13602 - Fix a bug where a bridge authority crashes (on a failed assert)
13603 if it has seen no directory requests when it's time to write
13604 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
13605 - Fix bug stomping on ORPort option NoListen and ignoring option
13606 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
13607 - In the testsuite, provide a large enough buffer in the tor_sscanf
13608 unit test. Otherwise we'd overrun that buffer and crash during
13609 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
13611 - Make sure we create the keys directory if it doesn't exist and we're
13612 about to store the dynamic Diffie-Hellman parameters. Fixes bug
13613 5572; bugfix on 0.2.3.13-alpha.
13614 - Fix a small memory leak when trying to decode incorrect base16
13615 authenticator during SAFECOOKIE authentication. Found by
13616 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
13619 - Add more information to a log statement that might help track down
13620 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
13621 non-IP address" messages (or any Bug messages, for that matter!),
13622 please let us know about it.
13623 - Relays now understand an IPv6 address when they get one from a
13624 directory server. Resolves ticket 4875.
13625 - Resolve IPv6 addresses in bridge and entry statistics to country
13626 code "??" which means we at least count them. Resolves ticket 5053;
13627 improves on 0.2.3.9-alpha.
13628 - Update to the April 3 2012 Maxmind GeoLite Country database.
13629 - Begin a doc/state-contents.txt file to explain the contents of
13630 the Tor state file. Fixes bug 2987.
13632 o Default torrc changes:
13633 - Stop listing "socksport 9050" in torrc.sample. We open a socks
13634 port on 9050 by default anyway, so this should not change anything
13636 - Stop mentioning the deprecated *ListenAddress options in
13637 torrc.sample. Fixes bug 5438.
13638 - Document unit of bandwidth related options in sample torrc.
13641 o Removed features:
13642 - The "torify" script no longer supports the "tsocks" socksifier
13643 tool, since tsocks doesn't support DNS and UDP right for Tor.
13644 Everyone should be using torsocks instead. Fixes bugs 3530 and
13645 5180. Based on a patch by "ugh".
13647 o Code refactoring:
13648 - Change the symmetric cipher interface so that creating and
13649 initializing a stream cipher are no longer separate functions.
13650 - Remove all internal support for unpadded RSA. We never used it, and
13651 it would be a bad idea to start.
13654 Changes in version 0.2.3.13-alpha - 2012-03-26
13655 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
13656 in managed pluggable transports, as well as providing other cleanups
13657 that get us closer to a release candidate.
13659 o Directory authority changes:
13660 - Change IP address for maatuska (v3 directory authority).
13663 - Provide controllers with a safer way to implement the cookie
13664 authentication mechanism. With the old method, if another locally
13665 running program could convince a controller that it was the Tor
13666 process, then that program could trick the controller into telling
13667 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
13668 authentication method uses a challenge-response approach to prevent
13669 this attack. Fixes bug 5185, implements proposal 193.
13670 - Never use a bridge or a controller-supplied node as an exit, even
13671 if its exit policy allows it. Found by wanoskarnet. Fixes bug
13672 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
13673 and 0.2.0.3-alpha (for bridge-purpose descriptors).
13674 - Only build circuits if we have a sufficient threshold of the total
13675 descriptors that are marked in the consensus with the "Exit"
13676 flag. This mitigates an attack proposed by wanoskarnet, in which
13677 all of a client's bridges collude to restrict the exit nodes that
13678 the client knows about. Fixes bug 5343.
13680 o Major bugfixes (on Tor 0.2.3.x):
13681 - Avoid an assert when managed proxies like obfsproxy are configured,
13682 and we receive HUP signals or setconf attempts too rapidly. This
13683 situation happens most commonly when Vidalia tries to attach to
13684 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
13685 bugfix on 0.2.3.6-alpha.
13686 - Fix a relay-side pluggable transports bug where managed proxies were
13687 unreachable from the Internet, because Tor asked them to bind on
13688 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
13689 - Stop discarding command-line arguments when TestingTorNetwork
13690 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
13691 0.2.3.9-alpha, where task 4552 added support for two layers of
13693 - Resume allowing the unit tests to run in gdb. This was accidentally
13694 made impossible when the DisableDebuggerAttachment option was
13695 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
13696 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
13697 0.2.3.11-alpha. Reported by Anthony G. Basile.
13699 o Minor bugfixes (on 0.2.2.x and earlier):
13700 - Ensure we don't cannibalize circuits that are longer than three hops
13701 already, so we don't end up making circuits with 5 or more
13702 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
13703 0.1.0.1-rc which introduced cannibalization.
13704 - Detect and reject certain misformed escape sequences in
13705 configuration values. Previously, these values would cause us
13706 to crash if received in a torrc file or over an authenticated
13707 control port. Bug found by Esteban Manchado Velázquez, and
13708 independently by Robert Connolly from Matta Consulting who further
13709 noted that it allows a post-authentication heap overflow. Patch
13710 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
13711 bugfix on 0.2.0.16-alpha.
13712 - Fix a compile warning when using the --enable-openbsd-malloc
13713 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
13714 - Directory caches no longer refuse to clean out descriptors because
13715 of missing v2 networkstatus documents, unless they're configured
13716 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
13717 0.2.2.26-beta. Patch by Daniel Bryg.
13718 - Update to the latest version of the tinytest unit testing framework.
13719 This includes a couple of bugfixes that can be relevant for
13720 running forked unit tests on Windows, and removes all reserved
13723 o Minor bugfixes (on 0.2.3.x):
13724 - On a failed pipe() call, don't leak file descriptors. Fixes bug
13725 4296; bugfix on 0.2.3.1-alpha.
13726 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
13727 until after we have received a CERTS cell. Fixes bug 4361; bugfix
13728 on 0.2.3.6-alpha. Patch by "frosty".
13729 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
13730 option, so that the IP stack doesn't decide to use it for IPv4
13731 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
13732 - Ensure that variables set in Tor's environment cannot override
13733 environment variables that Tor passes to a managed
13734 pluggable-transport proxy. Previously, Tor would pass every
13735 variable in its environment to managed proxies along with the new
13736 ones, in such a way that on many operating systems, the inherited
13737 environment variables would override those which Tor tried to
13738 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
13739 bugfix on 0.2.3.9-alpha for Windows.
13742 - A wide variety of new unit tests by Esteban Manchado Velázquez.
13743 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
13744 - Update to the March 6 2012 Maxmind GeoLite Country database.
13747 Changes in version 0.2.3.12-alpha - 2012-02-13
13748 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
13749 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
13750 when Tor is configured to use a pluggable transport like obfsproxy.
13753 - Fix builds when the path to sed, openssl, or sha1sum contains
13754 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
13756 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
13757 connections. This change should allow busy exit relays to stop
13758 running out of available sockets as quickly. Fixes bug 4950;
13759 bugfix on 0.2.2.26-beta.
13760 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
13761 would ask the bridge for microdescriptors, which are only supported
13762 in 0.2.3.x, and then fail to bootstrap when it didn't get the
13763 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
13764 - Properly set up obfsproxy's environment when in managed mode. The
13765 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
13766 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
13767 5076 and 5082; bugfix on 0.2.3.6-alpha.
13770 - Use the dead_strip option when building Tor on OS X. This reduces
13771 binary size by almost 19% when linking openssl and libevent
13772 statically, which we do for Tor Browser Bundle.
13773 - Fix broken URLs in the sample torrc file, and tell readers about
13774 the OutboundBindAddress, ExitPolicyRejectPrivate, and
13775 PublishServerDescriptor options. Addresses bug 4652.
13776 - Update to the February 7 2012 Maxmind GeoLite Country database.
13779 - Downgrade the "We're missing a certificate" message from notice
13780 to info: people kept mistaking it for a real problem, whereas it
13781 is seldom the problem even when we are failing to bootstrap. Fixes
13782 bug 5067; bugfix on 0.2.0.10-alpha.
13783 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
13784 managed pluggable transport server proxy's environment.
13785 Previously, we would put it there, even though Tor doesn't
13786 implement an 'extended server port' yet, and even though Tor
13787 almost certainly isn't listening at that address. For now, we set
13788 it to an empty string to avoid crashing older obfsproxies. Bugfix
13790 - Log the heartbeat message every HeartbeatPeriod seconds, not every
13791 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
13792 0.2.3.1-alpha. Bug reported by Scott Bennett.
13793 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
13794 bugfix on 0.2.3.11-alpha.
13795 - Update "ClientOnly" man page entry to explain that there isn't
13796 really any point to messing with it. Resolves ticket 5005.
13797 - Use the correct CVE number for CVE-2011-4576 in our comments and
13798 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
13801 o Code simplifications and refactoring:
13802 - Use the _WIN32 macro throughout our code to detect Windows.
13803 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
13807 Changes in version 0.2.3.11-alpha - 2012-01-22
13808 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
13809 the last step of the plan to limit maximum circuit length, includes
13810 a wide variety of hidden service performance and correctness fixes,
13811 works around an OpenSSL security flaw if your distro is too stubborn
13812 to upgrade, and fixes a bunch of smaller issues.
13815 - Now that Tor 0.2.0.x is completely deprecated, enable the final
13816 part of "Proposal 110: Avoiding infinite length circuits" by
13817 refusing all circuit-extend requests that do not use a relay_early
13818 cell. This change helps Tor resist a class of denial-of-service
13819 attacks by limiting the maximum circuit length.
13820 - Adjust the number of introduction points that a hidden service
13821 will try to maintain based on how long its introduction points
13822 remain in use and how many introductions they handle. Fixes
13824 - Try to use system facilities for enumerating local interface
13825 addresses, before falling back to our old approach (which was
13826 binding a UDP socket, and calling getsockname() on it). That
13827 approach was scaring OS X users whose draconian firewall
13828 software warned about binding to UDP sockets, regardless of
13829 whether packets were sent. Now we try to use getifaddrs(),
13830 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
13831 system supports. Resolves ticket 1827.
13833 o Major security workaround:
13834 - When building or running with any version of OpenSSL earlier
13835 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
13836 versions have a bug (CVE-2011-4576) in which their block cipher
13837 padding includes uninitialized data, potentially leaking sensitive
13838 information to any peer with whom they make a SSLv3 connection. Tor
13839 does not use SSL v3 by default, but a hostile client or server
13840 could force an SSLv3 connection in order to gain information that
13841 they shouldn't have been able to get. The best solution here is to
13842 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
13843 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
13844 to make sure that the bug can't happen.
13847 - Fix the SOCKET_OK test that we use to tell when socket
13848 creation fails so that it works on Win64. Fixes part of bug 4533;
13849 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
13850 - Correct our replacements for the timeradd() and timersub() functions
13851 on platforms that lack them (for example, Windows). The timersub()
13852 function is used when expiring circuits, while timeradd() is
13853 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
13854 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
13855 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
13856 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
13857 bug at runtime, not compile time, because some distributions hack
13858 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
13859 on 0.2.3.9-alpha. Found by Pascal.
13861 o Minor features (controller):
13862 - Use absolute path names when reporting the torrc filename in the
13863 control protocol, so a controller can more easily find the torrc
13864 file. Resolves bug 1101.
13865 - Extend the control protocol to report flags that control a circuit's
13866 path selection in CIRC events and in replies to 'GETINFO
13867 circuit-status'. Implements part of ticket 2411.
13868 - Extend the control protocol to report the hidden service address
13869 and current state of a hidden-service-related circuit in CIRC
13870 events and in replies to 'GETINFO circuit-status'. Implements part
13872 - When reporting the path to the cookie file to the controller,
13873 give an absolute path. Resolves ticket 4881.
13874 - Allow controllers to request an event notification whenever a
13875 circuit is cannibalized or its purpose is changed. Implements
13876 part of ticket 3457.
13877 - Include the creation time of a circuit in CIRC and CIRC2
13878 control-port events and the list produced by the 'GETINFO
13879 circuit-status' control-port command.
13881 o Minor features (directory authorities):
13882 - Directory authorities now reject versions of Tor older than
13883 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
13884 inclusive. These versions accounted for only a small fraction of
13885 the Tor network, and have numerous known security issues. Resolves
13887 - Authority operators can now vote for all relays in a given
13888 set of countries to be BadDir/BadExit/Invalid/Rejected.
13889 - Provide two consensus parameters (FastFlagMinThreshold and
13890 FastFlagMaxThreshold) to control the range of allowable bandwidths
13891 for the Fast directory flag. These allow authorities to run
13892 experiments on appropriate requirements for being a "Fast" node.
13893 The AuthDirFastGuarantee config value still applies. Implements
13895 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
13896 directory authority option (introduced in Tor 0.2.2.34).
13898 o Minor features (other):
13899 - Don't disable the DirPort when we cannot exceed our AccountingMax
13900 limit during this interval because the effective bandwidthrate is
13901 low enough. This is useful in a situation where AccountMax is only
13902 used as an additional safeguard or to provide statistics.
13903 - Prepend an informative header to generated dynamic_dh_params files.
13904 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
13905 EntryNodes will have no effect. Resolves issue 2571.
13906 - Log more useful messages when we fail to disable debugger
13908 - Log which authority we're missing votes from when we go to fetch
13909 them from the other auths.
13910 - Log (at debug level) whenever a circuit's purpose is changed.
13911 - Add missing documentation for the MaxClientCircuitsPending,
13912 UseMicrodescriptors, UserspaceIOCPBuffers, and
13913 _UseFilteringSSLBufferevents options, all introduced during
13914 the 0.2.3.x series.
13915 - Update to the January 3 2012 Maxmind GeoLite Country database.
13917 o Minor bugfixes (hidden services):
13918 - Don't close hidden service client circuits which have almost
13919 finished connecting to their destination when they reach
13920 the normal circuit-build timeout. Previously, we would close
13921 introduction circuits which are waiting for an acknowledgement
13922 from the introduction point, and rendezvous circuits which have
13923 been specified in an INTRODUCE1 cell sent to a hidden service,
13924 after the normal CBT. Now, we mark them as 'timed out', and launch
13925 another rendezvous attempt in parallel. This behavior change can
13926 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
13927 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
13928 - Don't close hidden-service-side rendezvous circuits when they
13929 reach the normal circuit-build timeout. This behavior change can
13930 be disabled using the new
13931 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
13932 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
13933 - Make sure we never mark the wrong rendezvous circuit as having
13934 had its introduction cell acknowleged by the introduction-point
13935 relay. Previously, when we received an INTRODUCE_ACK cell on a
13936 client-side hidden-service introduction circuit, we might have
13937 marked a rendezvous circuit other than the one we specified in
13938 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
13939 a warning message and interfered with the hidden service
13940 connection-establishment process. Fixes bug 4759; bugfix on
13941 0.2.3.3-alpha, when we added the stream-isolation feature which
13942 might cause Tor to open multiple rendezvous circuits for the same
13944 - Don't trigger an assertion failure when we mark a new client-side
13945 hidden-service introduction circuit for close during the process
13946 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
13949 o Minor bugfixes (log messages):
13950 - Correctly spell "connect" in a log message on failure to create a
13951 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
13953 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
13954 Fixes bug 4856; bugfix on Tor 0.0.6.
13955 - Fix the log message describing how we work around discovering
13956 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
13957 4837; bugfix on 0.2.2.9-alpha.
13958 - When logging about a disallowed .exit name, do not also call it
13959 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
13961 o Minor bugfixes (build fixes):
13962 - During configure, detect when we're building with clang version
13963 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
13964 CFLAGS. clang doesn't support them yet.
13965 - During configure, search for library containing cos function as
13966 libm lives in libcore on some platforms (BeOS/Haiku). Linking
13967 against libm was hard-coded before. Fixes the first part of bug
13968 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
13970 - Detect attempts to build Tor on (as yet hypothetical) versions
13971 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
13972 fix for bug 4533. Bugfix on 0.2.2.28-beta.
13973 - Preprocessor directives should not be put inside the arguments
13974 of a macro. This would break compilation with GCC releases prior
13975 to version 3.3. We would never recommend such an old GCC version,
13976 but it is apparently required for binary compatibility on some
13977 platforms (namely, certain builds of Haiku). Fixes the other part
13978 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
13981 o Minor bugfixes (other):
13982 - Older Linux kernels erroneously respond to strange nmap behavior
13983 by having accept() return successfully with a zero-length
13984 socket. When this happens, just close the connection. Previously,
13985 we would try harder to learn the remote address: but there was
13986 no such remote address to learn, and our method for trying to
13987 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
13988 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
13989 - Fix null-pointer access that could occur if TLS allocation failed.
13990 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
13991 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
13992 accidentally been reverted.
13993 - Fix our implementation of crypto_random_hostname() so it can't
13994 overflow on ridiculously large inputs. (No Tor version has ever
13995 provided this kind of bad inputs, but let's be correct in depth.)
13996 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
13997 - Find more places in the code that should have been testing for
13998 invalid sockets using the SOCKET_OK macro. Required for a fix
13999 for bug 4533. Bugfix on 0.2.2.28-beta.
14000 - Fix an assertion failure when, while running with bufferevents, a
14001 connection finishes connecting after it is marked for close, but
14002 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
14003 - test_util_spawn_background_ok() hardcoded the expected value
14004 for ENOENT to 2. This isn't portable as error numbers are
14005 platform specific, and particularly the hurd has ENOENT at
14006 0x40000002. Construct expected string at runtime, using the correct
14007 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
14008 - Reject attempts to disable DisableDebuggerAttachment while Tor is
14009 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
14010 - Use an appropriate-width type for sockets in tor-fw-helper on
14011 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
14014 - When sending or relaying a RELAY_EARLY cell, we used to convert
14015 it to a RELAY cell if the connection was using the v1 link
14016 protocol. This was a workaround for older versions of Tor, which
14017 didn't handle RELAY_EARLY cells properly. Now that all supported
14018 versions can handle RELAY_EARLY cells, and now that we're enforcing
14019 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
14020 remove this workaround. Addresses bug 4786.
14022 o Code simplifications and refactoring:
14023 - Use OpenSSL's built-in SSL_state_string_long() instead of our
14024 own homebrewed ssl_state_to_string() replacement. Patch from
14025 Emile Snyder. Fixes bug 4653.
14026 - Use macros to indicate OpenSSL versions, so we don't need to worry
14027 about accidental hexadecimal bit shifts.
14028 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
14030 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
14031 - Use the smartlist_add_asprintf() alias more consistently.
14032 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
14033 invalid value, rather than just -1.
14034 - Rename a handful of old identifiers, mostly related to crypto
14035 structures and crypto functions. By convention, our "create an
14036 object" functions are called "type_new()", our "free an object"
14037 functions are called "type_free()", and our types indicate that
14038 they are types only with a final "_t". But a handful of older
14039 types and functions broke these rules, with function names like
14040 "type_create" or "subsystem_op_type", or with type names like
14044 Changes in version 0.2.3.10-alpha - 2011-12-16
14045 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
14046 Tor's buffers code. Absolutely everybody should upgrade.
14048 The bug relied on an incorrect calculation when making data continuous
14049 in one of our IO buffers, if the first chunk of the buffer was
14050 misaligned by just the wrong amount. The miscalculation would allow an
14051 attacker to overflow a piece of heap-allocated memory. To mount this
14052 attack, the attacker would need to either open a SOCKS connection to
14053 Tor's SocksPort (usually restricted to localhost), or target a Tor
14054 instance configured to make its connections through a SOCKS proxy
14055 (which Tor does not do by default).
14057 Good security practice requires that all heap-overflow bugs should be
14058 presumed to be exploitable until proven otherwise, so we are treating
14059 this as a potential code execution attack. Please upgrade immediately!
14060 This bug does not affect bufferevents-based builds of Tor. Special
14061 thanks to "Vektor" for reporting this issue to us!
14063 This release also contains a few minor bugfixes for issues discovered
14067 - Fix a heap overflow bug that could occur when trying to pull
14068 data into the first chunk of a buffer, when that chunk had
14069 already had some data drained from it. Fixes CVE-2011-2778;
14070 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
14073 - If we can't attach streams to a rendezvous circuit when we
14074 finish connecting to a hidden service, clear the rendezvous
14075 circuit's stream-isolation state and try to attach streams
14076 again. Previously, we cleared rendezvous circuits' isolation
14077 state either too early (if they were freshly built) or not at all
14078 (if they had been built earlier and were cannibalized). Bugfix on
14079 0.2.3.3-alpha; fixes bug 4655.
14080 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
14081 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
14082 - Fix an assertion failure when a relay with accounting enabled
14083 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
14086 - Update to the December 6 2011 Maxmind GeoLite Country database.
14089 Changes in version 0.2.2.35 - 2011-12-16
14090 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
14091 buffers code. Absolutely everybody should upgrade.
14093 The bug relied on an incorrect calculation when making data continuous
14094 in one of our IO buffers, if the first chunk of the buffer was
14095 misaligned by just the wrong amount. The miscalculation would allow an
14096 attacker to overflow a piece of heap-allocated memory. To mount this
14097 attack, the attacker would need to either open a SOCKS connection to
14098 Tor's SocksPort (usually restricted to localhost), or target a Tor
14099 instance configured to make its connections through a SOCKS proxy
14100 (which Tor does not do by default).
14102 Good security practice requires that all heap-overflow bugs should be
14103 presumed to be exploitable until proven otherwise, so we are treating
14104 this as a potential code execution attack. Please upgrade immediately!
14105 This bug does not affect bufferevents-based builds of Tor. Special
14106 thanks to "Vektor" for reporting this issue to us!
14108 Tor 0.2.2.35 also fixes several bugs in previous versions, including
14109 crash bugs for unusual configurations, and a long-term bug that
14110 would prevent Tor from starting on Windows machines with draconian
14113 With this release, we remind everyone that 0.2.0.x has reached its
14114 formal end-of-life. Those Tor versions have many known flaws, and
14115 nobody should be using them. You should upgrade -- ideally to the
14116 0.2.2.x series. If you're using a Linux or BSD and its packages are
14117 obsolete, stop using those packages and upgrade anyway.
14119 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
14120 longer receive support after some time in early 2012.
14123 - Fix a heap overflow bug that could occur when trying to pull
14124 data into the first chunk of a buffer, when that chunk had
14125 already had some data drained from it. Fixes CVE-2011-2778;
14126 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
14127 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
14128 that it doesn't attempt to allocate a socketpair. This could cause
14129 some problems on Windows systems with overzealous firewalls. Fix for
14130 bug 4457; workaround for Libevent versions 2.0.1-alpha through
14132 - If we mark an OR connection for close based on a cell we process,
14133 don't process any further cells on it. We already avoid further
14134 reads on marked-for-close connections, but now we also discard the
14135 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
14136 which was the first version where we might mark a connection for
14137 close based on processing a cell on it.
14138 - Correctly sanity-check that we don't underflow on a memory
14139 allocation (and then assert) for hidden service introduction
14140 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14141 bugfix on 0.2.1.5-alpha.
14142 - Fix a memory leak when we check whether a hidden service
14143 descriptor has any usable introduction points left. Fixes bug
14144 4424. Bugfix on 0.2.2.25-alpha.
14145 - Don't crash when we're running as a relay and don't have a GeoIP
14146 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
14147 we've had in the 0.2.3.x branch already.
14148 - When running as a client, do not print a misleading (and plain
14149 wrong) log message that we're collecting "directory request"
14150 statistics: clients don't collect statistics. Also don't create a
14151 useless (because empty) stats file in the stats/ directory. Fixes
14152 bug 4353; bugfix on 0.2.2.34.
14155 - Detect failure to initialize Libevent. This fix provides better
14156 detection for future instances of bug 4457.
14157 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
14158 function. This was eating up hideously large amounts of time on some
14159 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
14160 - Resolve an integer overflow bug in smartlist_ensure_capacity().
14161 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
14163 - Don't warn about unused log_mutex in log.c when building with
14164 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
14165 0.1.0.6-rc which introduced --disable-threads.
14166 - When configuring, starting, or stopping an NT service, stop
14167 immediately after the service configuration attempt has succeeded
14168 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
14169 - When sending a NETINFO cell, include the original address
14170 received for the other side, not its canonical address. Found
14171 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
14172 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
14173 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
14174 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
14175 occurred when a client tried to fetch a descriptor for a bridge
14176 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
14177 - Backport fixes for a pair of compilation warnings on Windows.
14178 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
14179 - If we had ever tried to call tor_addr_to_str on an address of
14180 unknown type, we would have done a strdup on an uninitialized
14181 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
14182 Reported by "troll_un".
14183 - Correctly detect and handle transient lookup failures from
14184 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
14185 Reported by "troll_un".
14186 - Fix null-pointer access that could occur if TLS allocation failed.
14187 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
14188 - Use tor_socket_t type for listener argument to accept(). Fixes bug
14189 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
14192 - Add two new config options for directory authorities:
14193 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
14194 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
14195 that is always sufficient to satisfy the bandwidth requirement for
14196 the Guard flag. Now it will be easier for researchers to simulate
14197 Tor networks with different values. Resolves ticket 4484.
14198 - When Tor ignores a hidden service specified in its configuration,
14199 include the hidden service's directory in the warning message.
14200 Previously, we would only tell the user that some hidden service
14201 was ignored. Bugfix on 0.0.6; fixes bug 4426.
14202 - Update to the December 6 2011 Maxmind GeoLite Country database.
14204 o Packaging changes:
14205 - Make it easier to automate expert package builds on Windows,
14206 by removing an absolute path from makensis.exe command.
14209 Changes in version 0.2.1.32 - 2011-12-16
14210 Tor 0.2.1.32 backports important security and privacy fixes for
14211 oldstable. This release is intended only for package maintainers and
14212 others who cannot use the 0.2.2 stable series. All others should be
14213 using Tor 0.2.2.x or newer.
14215 The Tor 0.2.1.x series will reach formal end-of-life some time in
14216 early 2012; we will stop releasing patches for it then.
14218 o Major bugfixes (also included in 0.2.2.x):
14219 - Correctly sanity-check that we don't underflow on a memory
14220 allocation (and then assert) for hidden service introduction
14221 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14222 bugfix on 0.2.1.5-alpha.
14223 - Fix a heap overflow bug that could occur when trying to pull
14224 data into the first chunk of a buffer, when that chunk had
14225 already had some data drained from it. Fixes CVE-2011-2778;
14226 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
14229 - Update to the December 6 2011 Maxmind GeoLite Country database.
14232 Changes in version 0.2.3.9-alpha - 2011-12-08
14233 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
14234 a "DisableNetwork" security feature that bundles can use to avoid
14235 touching the network until bridges are configured, moves forward on
14236 the pluggable transport design, fixes a flaw in the hidden service
14237 design that unnecessarily prevented clients with wrong clocks from
14238 reaching hidden services, and fixes a wide variety of other issues.
14241 - Clients can now connect to private bridges over IPv6. Bridges
14242 still need at least one IPv4 address in order to connect to
14243 other relays. Note that we don't yet handle the case where the
14244 user has two bridge lines for the same bridge (one IPv4, one
14245 IPv6). Implements parts of proposal 186.
14246 - New "DisableNetwork" config option to prevent Tor from launching any
14247 connections or accepting any connections except on a control port.
14248 Bundles and controllers can set this option before letting Tor talk
14249 to the rest of the network, for example to prevent any connections
14250 to a non-bridge address. Packages like Orbot can also use this
14251 option to instruct Tor to save power when the network is off.
14252 - Clients and bridges can now be configured to use a separate
14253 "transport" proxy. This approach makes the censorship arms race
14254 easier by allowing bridges to use protocol obfuscation plugins. It
14255 implements the "managed proxy" part of proposal 180 (ticket 3472).
14256 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
14257 implementation. It makes AES_CTR about 7% faster than our old one
14258 (which was about 10% faster than the one OpenSSL used to provide).
14259 Resolves ticket 4526.
14260 - Add a "tor2web mode" for clients that want to connect to hidden
14261 services non-anonymously (and possibly more quickly). As a safety
14262 measure to try to keep users from turning this on without knowing
14263 what they are doing, tor2web mode must be explicitly enabled at
14264 compile time, and a copy of Tor compiled to run in tor2web mode
14265 cannot be used as a normal Tor client. Implements feature 2553.
14266 - Add experimental support for running on Windows with IOCP and no
14267 kernel-space socket buffers. This feature is controlled by a new
14268 "UserspaceIOCPBuffers" config option (off by default), which has
14269 no effect unless Tor has been built with support for bufferevents,
14270 is running on Windows, and has enabled IOCP. This may, in the long
14271 run, help solve or mitigate bug 98.
14272 - Use a more secure consensus parameter voting algorithm. Now at
14273 least three directory authorities or a majority of them must
14274 vote on a given parameter before it will be included in the
14275 consensus. Implements proposal 178.
14278 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
14279 They used to check that the timestamp was within 30 minutes
14280 of their system clock, so they could cap the size of their
14281 replay-detection cache, but that approach unnecessarily refused
14282 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
14283 the v3 intro-point protocol (the first one which sent a timestamp
14284 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
14285 - Only use the EVP interface when AES acceleration is enabled,
14286 to avoid a 5-7% performance regression. Resolves issue 4525;
14287 bugfix on 0.2.3.8-alpha.
14289 o Privacy/anonymity features (bridge detection):
14290 - Make bridge SSL certificates a bit more stealthy by using random
14291 serial numbers, in the same fashion as OpenSSL when generating
14292 self-signed certificates. Implements ticket 4584.
14293 - Introduce a new config option "DynamicDHGroups", enabled by
14294 default, which provides each bridge with a unique prime DH modulus
14295 to be used during SSL handshakes. This option attempts to help
14296 against censors who might use the Apache DH modulus as a static
14297 identifier for bridges. Addresses ticket 4548.
14299 o Minor features (new/different config options):
14300 - New configuration option "DisableDebuggerAttachment" (on by default)
14301 to prevent basic debugging attachment attempts by other processes.
14302 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
14303 - Allow MapAddress directives to specify matches against super-domains,
14304 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
14305 Implements issue 933.
14306 - Slightly change behavior of "list" options (that is, config
14307 options that can appear more than once) when they appear both in
14308 torrc and on the command line. Previously, the command-line options
14309 would be appended to the ones from torrc. Now, the command-line
14310 options override the torrc options entirely. This new behavior
14311 allows the user to override list options (like exit policies and
14312 ports to listen on) from the command line, rather than simply
14313 appending to the list.
14314 - You can get the old (appending) command-line behavior for "list"
14315 options by prefixing the option name with a "+".
14316 - You can remove all the values for a "list" option from the command
14317 line without adding any new ones by prefixing the option name
14319 - Add experimental support for a "defaults" torrc file to be parsed
14320 before the regular torrc. Torrc options override the defaults file's
14321 options in the same way that the command line overrides the torrc.
14322 The SAVECONF controller command saves only those options which
14323 differ between the current configuration and the defaults file. HUP
14324 reloads both files. (Note: This is an experimental feature; its
14325 behavior will probably be refined in future 0.2.3.x-alpha versions
14326 to better meet packagers' needs.) Implements task 4552.
14329 - Try to make the introductory warning message that Tor prints on
14330 startup more useful for actually finding help and information.
14331 Resolves ticket 2474.
14332 - Running "make version" now displays the version of Tor that
14333 we're about to build. Idea from katmagic; resolves issue 4400.
14334 - Expire old or over-used hidden service introduction points.
14335 Required by fix for bug 3460.
14336 - Move the replay-detection cache for the RSA-encrypted parts of
14337 INTRODUCE2 cells to the introduction point data structures.
14338 Previously, we would use one replay-detection cache per hidden
14339 service. Required by fix for bug 3460.
14340 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
14341 public key replay-detection cache from 60 minutes to 5 minutes. This
14342 replay-detection cache is now used only to detect multiple
14343 INTRODUCE2 cells specifying the same rendezvous point, so we can
14344 avoid launching multiple simultaneous attempts to connect to it.
14346 o Minor bugfixes (on Tor 0.2.2.x and earlier):
14347 - Resolve an integer overflow bug in smartlist_ensure_capacity().
14348 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
14350 - Fix a minor formatting issue in one of tor-gencert's error messages.
14352 - Prevent a false positive from the check-spaces script, by disabling
14353 the "whitespace between function name and (" check for functions
14355 - Fix a log message suggesting that people contact a non-existent
14356 email address. Fixes bug 3448.
14357 - Fix null-pointer access that could occur if TLS allocation failed.
14358 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
14359 - Report a real bootstrap problem to the controller on router
14360 identity mismatch. Previously we just said "foo", which probably
14361 made a lot of sense at the time. Fixes bug 4169; bugfix on
14363 - If we had ever tried to call tor_addr_to_str() on an address of
14364 unknown type, we would have done a strdup() on an uninitialized
14365 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
14366 Reported by "troll_un".
14367 - Correctly detect and handle transient lookup failures from
14368 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
14369 Reported by "troll_un".
14370 - Use tor_socket_t type for listener argument to accept(). Fixes bug
14371 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
14372 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
14373 bug 4532; found by "troll_un".
14375 o Minor bugfixes (on Tor 0.2.3.x):
14376 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
14378 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
14379 circuit for use as a hidden service client's rendezvous point.
14380 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
14381 with help from wanoskarnet.
14382 - Restore behavior of overriding SocksPort, ORPort, and similar
14383 options from the command line. Bugfix on 0.2.3.3-alpha.
14386 - Properly handle the case where the build-tree is not the same
14387 as the source tree when generating src/common/common_sha1.i,
14388 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
14389 bugfix on 0.2.0.1-alpha.
14391 o Code simplifications, cleanups, and refactorings:
14392 - Remove the pure attribute from all functions that used it
14393 previously. In many cases we assigned it incorrectly, because the
14394 functions might assert or call impure functions, and we don't have
14395 evidence that keeping the pure attribute is worthwhile. Implements
14396 changes suggested in ticket 4421.
14397 - Remove some dead code spotted by coverity. Fixes cid 432.
14398 Bugfix on 0.2.3.1-alpha, closes bug 4637.
14401 Changes in version 0.2.3.8-alpha - 2011-11-22
14402 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
14403 socketpair-related bug that has been bothering Windows users. It adds
14404 support to serve microdescriptors to controllers, so Vidalia's network
14405 map can resume listing relays (once Vidalia implements its side),
14406 and adds better support for hardware AES acceleration. Finally, it
14407 starts the process of adjusting the bandwidth cutoff for getting the
14408 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
14409 that tiny relays harm performance more than they help network capacity.
14412 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
14413 that it doesn't attempt to allocate a socketpair. This could cause
14414 some problems on Windows systems with overzealous firewalls. Fix for
14415 bug 4457; workaround for Libevent versions 2.0.1-alpha through
14417 - Correctly sanity-check that we don't underflow on a memory
14418 allocation (and then assert) for hidden service introduction
14419 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14420 bugfix on 0.2.1.5-alpha.
14421 - Remove the artificially low cutoff of 20KB to guarantee the Fast
14422 flag. In the past few years the average relay speed has picked
14423 up, and while the "top 7/8 of the network get the Fast flag" and
14424 "all relays with 20KB or more of capacity get the Fast flag" rules
14425 used to have the same result, now the top 7/8 of the network has
14426 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
14427 - Fix a rare assertion failure when checking whether a v0 hidden
14428 service descriptor has any usable introduction points left, and
14429 we don't have enough information to build a circuit to the first
14430 intro point named in the descriptor. The HS client code in
14431 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
14432 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
14433 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
14434 - Make bridge authorities not crash when they are asked for their own
14435 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
14436 - When running as a client, do not print a misleading (and plain
14437 wrong) log message that we're collecting "directory request"
14438 statistics: clients don't collect statistics. Also don't create a
14439 useless (because empty) stats file in the stats/ directory. Fixes
14440 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
14443 - Allow Tor controllers like Vidalia to obtain the microdescriptor
14444 for a relay by identity digest or nickname. Previously,
14445 microdescriptors were only available by their own digests, so a
14446 controller would have to ask for and parse the whole microdescriptor
14447 consensus in order to look up a single relay's microdesc. Fixes
14448 bug 3832; bugfix on 0.2.3.1-alpha.
14449 - Use OpenSSL's EVP interface for AES encryption, so that all AES
14450 operations can use hardware acceleration (if present). Resolves
14453 o Minor bugfixes (on 0.2.2.x and earlier):
14454 - Detect failure to initialize Libevent. This fix provides better
14455 detection for future instances of bug 4457.
14456 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
14457 function. This was eating up hideously large amounts of time on some
14458 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
14459 - Don't warn about unused log_mutex in log.c when building with
14460 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
14461 0.1.0.6-rc which introduced --disable-threads.
14462 - Allow manual 'authenticate' commands to the controller interface
14463 from netcat (nc) as well as telnet. We were rejecting them because
14464 they didn't come with the expected whitespace at the end of the
14465 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
14466 - Fix some (not actually triggerable) buffer size checks in usage of
14467 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
14469 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
14470 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
14471 - When configuring, starting, or stopping an NT service, stop
14472 immediately after the service configuration attempt has succeeded
14473 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
14474 - When sending a NETINFO cell, include the original address
14475 received for the other side, not its canonical address. Found
14476 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
14477 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
14478 can pick them up when the tests aren't disabled. Bugfix on
14479 0.2.2.4-alpha which introduced tinytest.
14480 - Fix a memory leak when we check whether a hidden service
14481 descriptor has any usable introduction points left. Fixes bug
14482 4424. Bugfix on 0.2.2.25-alpha.
14483 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
14484 occurred when a client tried to fetch a descriptor for a bridge
14485 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
14487 o Minor bugfixes (on 0.2.3.x):
14488 - Make util unit tests build correctly with MSVC. Bugfix on
14489 0.2.3.3-alpha. Patch by Gisle Vanem.
14490 - Successfully detect AUTH_CHALLENGE cells with no recognized
14491 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
14492 Found by frosty_un.
14493 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
14494 it should still send a NETINFO cell to allow the connection to
14495 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
14497 - Log less loudly when we get an invalid authentication certificate
14498 from a source other than a directory authority: it's not unusual
14499 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
14501 - Tolerate servers with more clock skew in their authentication
14502 certificates than previously. Fixes bug 4371; bugfix on
14504 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
14505 on 0.2.3.4-alpha and 0.2.3.6-alpha.
14508 - Add two new config options for directory authorities:
14509 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
14510 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
14511 that is always sufficient to satisfy the bandwidth requirement for
14512 the Guard flag. Now it will be easier for researchers to simulate
14513 Tor networks with different values. Resolves ticket 4484.
14514 - When Tor ignores a hidden service specified in its configuration,
14515 include the hidden service's directory in the warning message.
14516 Previously, we would only tell the user that some hidden service
14517 was ignored. Bugfix on 0.0.6; fixes bug 4426.
14518 - When we fail to initialize Libevent, retry with IOCP disabled so we
14519 don't need to turn on multi-threading support in Libevent, which in
14520 turn requires a working socketpair(). This is a workaround for bug
14521 4457, which affects Libevent versions from 2.0.1-alpha through
14523 - Detect when we try to build on a platform that doesn't define
14524 AF_UNSPEC to 0. We don't work there, so refuse to compile.
14525 - Update to the November 1 2011 Maxmind GeoLite Country database.
14527 o Packaging changes:
14528 - Make it easier to automate expert package builds on Windows,
14529 by removing an absolute path from makensis.exe command.
14531 o Code simplifications and refactoring:
14532 - Remove some redundant #include directives throughout the code.
14533 Patch from Andrea Gelmini.
14534 - Unconditionally use OpenSSL's AES implementation instead of our
14535 old built-in one. OpenSSL's AES has been better for a while, and
14536 relatively few servers should still be on any version of OpenSSL
14537 that doesn't have good optimized assembly AES.
14538 - Use the name "CERTS" consistently to refer to the new cell type;
14539 we were calling it CERT in some places and CERTS in others.
14542 - Numerous new unit tests for functions in util.c and address.c by
14544 - The long-disabled benchmark tests are now split into their own
14545 ./src/test/bench binary.
14546 - The benchmark tests can now use more accurate timers than
14547 gettimeofday() when such timers are available.
14550 Changes in version 0.2.3.7-alpha - 2011-10-30
14551 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
14552 the new v3 handshake. It also resolves yet another bridge address
14556 - If we mark an OR connection for close based on a cell we process,
14557 don't process any further cells on it. We already avoid further
14558 reads on marked-for-close connections, but now we also discard the
14559 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
14560 which was the first version where we might mark a connection for
14561 close based on processing a cell on it.
14562 - Fix a double-free bug that would occur when we received an invalid
14563 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
14564 bugfix on 0.2.3.6-alpha.
14565 - Bridges no longer include their address in NETINFO cells on outgoing
14566 OR connections, to allow them to blend in better with clients.
14567 Removes another avenue for enumerating bridges. Reported by
14568 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
14569 cells were introduced.
14572 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
14573 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
14576 Changes in version 0.2.3.6-alpha - 2011-10-26
14577 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
14578 anonymity vulnerability where an attacker can deanonymize Tor
14579 users. Everybody should upgrade.
14581 This release also features support for a new v3 connection handshake
14582 protocol, and fixes to make hidden service connections more robust.
14585 - Implement a new handshake protocol (v3) for authenticating Tors to
14586 each other over TLS. It should be more resistant to fingerprinting
14587 than previous protocols, and should require less TLS hacking for
14588 future Tor implementations. Implements proposal 176.
14589 - Allow variable-length padding cells to disguise the length of
14590 Tor's TLS records. Implements part of proposal 184.
14592 o Privacy/anonymity fixes (clients):
14593 - Clients and bridges no longer send TLS certificate chains on
14594 outgoing OR connections. Previously, each client or bridge would
14595 use the same cert chain for all outgoing OR connections until
14596 its IP address changes, which allowed any relay that the client
14597 or bridge contacted to determine which entry guards it is using.
14598 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14599 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14600 no longer considers that connection as suitable for satisfying a
14601 circuit EXTEND request. Now relays can protect clients from the
14602 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14603 - Directory authorities no longer assign the Guard flag to relays
14604 that haven't upgraded to the above "refuse EXTEND requests
14605 to client connections" fix. Now directory authorities can
14606 protect clients from the CVE-2011-2768 issue even if neither
14607 the clients nor the relays have upgraded yet. There's a new
14608 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
14609 to let us transition smoothly, else tomorrow there would be no
14612 o Major bugfixes (hidden services):
14613 - Improve hidden service robustness: when an attempt to connect to
14614 a hidden service ends, be willing to refetch its hidden service
14615 descriptors from each of the HSDir relays responsible for them
14616 immediately. Previously, we would not consider refetching the
14617 service's descriptors from each HSDir for 15 minutes after the last
14618 fetch, which was inconvenient if the hidden service was not running
14619 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
14620 - When one of a hidden service's introduction points appears to be
14621 unreachable, stop trying it. Previously, we would keep trying
14622 to build circuits to the introduction point until we lost the
14623 descriptor, usually because the user gave up and restarted Tor.
14624 Partly fixes bug 3825.
14625 - Don't launch a useless circuit after failing to use one of a
14626 hidden service's introduction points. Previously, we would
14627 launch a new introduction circuit, but not set the hidden service
14628 which that circuit was intended to connect to, so it would never
14629 actually be used. A different piece of code would then create a
14630 new introduction circuit correctly. Bug reported by katmagic and
14631 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
14633 o Major bugfixes (other):
14634 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14635 that they initiated. Relays could distinguish incoming bridge
14636 connections from client connections, creating another avenue for
14637 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14638 Found by "frosty_un".
14639 - Don't update the AccountingSoftLimitHitAt state file entry whenever
14640 tor gets started. This prevents a wrong average bandwidth
14641 estimate, which would cause relays to always start a new accounting
14642 interval at the earliest possible moment. Fixes bug 2003; bugfix
14643 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
14644 immensely in tracking this bug down.
14645 - Fix a crash bug when changing node restrictions while a DNS lookup
14646 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
14649 o Minor bugfixes (on 0.2.2.x and earlier):
14650 - When a hidden service turns an extra service-side introduction
14651 circuit into a general-purpose circuit, free the rend_data and
14652 intro_key fields first, so we won't leak memory if the circuit
14653 is cannibalized for use as another service-side introduction
14654 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
14655 - Rephrase the log message emitted if the TestSocks check is
14656 successful. Patch from Fabian Keil; fixes bug 4094.
14657 - Bridges now skip DNS self-tests, to act a little more stealthily.
14658 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
14659 bridges. Patch by "warms0x".
14660 - Remove a confusing dollar sign from the example fingerprint in the
14661 man page, and also make the example fingerprint a valid one. Fixes
14662 bug 4309; bugfix on 0.2.1.3-alpha.
14663 - Fix internal bug-checking logic that was supposed to catch
14664 failures in digest generation so that it will fail more robustly
14665 if we ask for a nonexistent algorithm. Found by Coverity Scan.
14666 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
14667 - Report any failure in init_keys() calls launched because our
14668 IP address has changed. Spotted by Coverity Scan. Bugfix on
14669 0.1.1.4-alpha; fixes CID 484.
14671 o Minor bugfixes (on 0.2.3.x):
14672 - Fix a bug in configure.in that kept it from building a configure
14673 script with autoconf versions earlier than 2.61. Fixes bug 2430;
14674 bugfix on 0.2.3.1-alpha.
14675 - Don't warn users that they are exposing a client port to the
14676 Internet if they have specified an RFC1918 address. Previously,
14677 we would warn if the user had specified any non-loopback
14678 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
14679 - Fix memory leaks in the failing cases of the new SocksPort and
14680 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
14681 fixes coverity CIDs 485, 486, and 487.
14684 - When a hidden service's introduction point times out, consider
14685 trying it again during the next attempt to connect to the
14686 HS. Previously, we would not try it again unless a newly fetched
14687 descriptor contained it. Required by fixes for bugs 1297 and 3825.
14688 - The next version of Windows will be called Windows 8, and it has
14689 a major version of 6, minor version of 2. Correctly identify that
14690 version instead of calling it "Very recent version". Resolves
14691 ticket 4153; reported by funkstar.
14692 - The Bridge Authority now writes statistics on how many bridge
14693 descriptors it gave out in total, and how many unique descriptors
14694 it gave out. It also lists how often the most and least commonly
14695 fetched descriptors were given out, as well as the median and
14696 25th/75th percentile. Implements tickets 4200 and 4294.
14697 - Update to the October 4 2011 Maxmind GeoLite Country database.
14699 o Code simplifications and refactoring:
14700 - Remove some old code to remember statistics about which descriptors
14701 we've served as a directory mirror. The feature wasn't used and
14702 is outdated now that microdescriptors are around.
14703 - Rename Tor functions that turn strings into addresses, so that
14704 "parse" indicates that no hostname resolution occurs, and
14705 "lookup" indicates that hostname resolution may occur. This
14706 should help prevent mistakes in the future. Fixes bug 3512.
14709 Changes in version 0.2.2.34 - 2011-10-26
14710 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
14711 can deanonymize Tor users. Everybody should upgrade.
14713 The attack relies on four components: 1) Clients reuse their TLS cert
14714 when talking to different relays, so relays can recognize a user by
14715 the identity key in her cert. 2) An attacker who knows the client's
14716 identity key can probe each guard relay to see if that identity key
14717 is connected to that guard relay right now. 3) A variety of active
14718 attacks in the literature (starting from "Low-Cost Traffic Analysis
14719 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
14720 discover the guard relays that a Tor user visiting the website is using.
14721 4) Clients typically pick three guards at random, so the set of guards
14722 for a given user could well be a unique fingerprint for her. This
14723 release fixes components #1 and #2, which is enough to block the attack;
14724 the other two remain as open research problems. Special thanks to
14725 "frosty_un" for reporting the issue to us!
14727 Clients should upgrade so they are no longer recognizable by the TLS
14728 certs they present. Relays should upgrade so they no longer allow a
14729 remote attacker to probe them to test whether unpatched clients are
14730 currently connected to them.
14732 This release also fixes several vulnerabilities that allow an attacker
14733 to enumerate bridge relays. Some bridge enumeration attacks still
14734 remain; see for example proposal 188.
14736 o Privacy/anonymity fixes (clients):
14737 - Clients and bridges no longer send TLS certificate chains on
14738 outgoing OR connections. Previously, each client or bridge would
14739 use the same cert chain for all outgoing OR connections until
14740 its IP address changes, which allowed any relay that the client
14741 or bridge contacted to determine which entry guards it is using.
14742 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14743 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14744 no longer considers that connection as suitable for satisfying a
14745 circuit EXTEND request. Now relays can protect clients from the
14746 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14747 - Directory authorities no longer assign the Guard flag to relays
14748 that haven't upgraded to the above "refuse EXTEND requests
14749 to client connections" fix. Now directory authorities can
14750 protect clients from the CVE-2011-2768 issue even if neither
14751 the clients nor the relays have upgraded yet. There's a new
14752 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
14753 to let us transition smoothly, else tomorrow there would be no
14756 o Privacy/anonymity fixes (bridge enumeration):
14757 - Bridge relays now do their directory fetches inside Tor TLS
14758 connections, like all the other clients do, rather than connecting
14759 directly to the DirPort like public relays do. Removes another
14760 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
14761 - Bridges relays now build circuits for themselves in a more similar
14762 way to how clients build them. Removes another avenue for
14763 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
14764 when bridges were introduced.
14765 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14766 that they initiated. Relays could distinguish incoming bridge
14767 connections from client connections, creating another avenue for
14768 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14769 Found by "frosty_un".
14772 - Fix a crash bug when changing node restrictions while a DNS lookup
14773 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
14775 - Don't launch a useless circuit after failing to use one of a
14776 hidden service's introduction points. Previously, we would
14777 launch a new introduction circuit, but not set the hidden service
14778 which that circuit was intended to connect to, so it would never
14779 actually be used. A different piece of code would then create a
14780 new introduction circuit correctly. Bug reported by katmagic and
14781 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
14784 - Change an integer overflow check in the OpenBSD_Malloc code so
14785 that GCC is less likely to eliminate it as impossible. Patch
14786 from Mansour Moufid. Fixes bug 4059.
14787 - When a hidden service turns an extra service-side introduction
14788 circuit into a general-purpose circuit, free the rend_data and
14789 intro_key fields first, so we won't leak memory if the circuit
14790 is cannibalized for use as another service-side introduction
14791 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
14792 - Bridges now skip DNS self-tests, to act a little more stealthily.
14793 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
14794 bridges. Patch by "warms0x".
14795 - Fix internal bug-checking logic that was supposed to catch
14796 failures in digest generation so that it will fail more robustly
14797 if we ask for a nonexistent algorithm. Found by Coverity Scan.
14798 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
14799 - Report any failure in init_keys() calls launched because our
14800 IP address has changed. Spotted by Coverity Scan. Bugfix on
14801 0.1.1.4-alpha; fixes CID 484.
14803 o Minor bugfixes (log messages and documentation):
14804 - Remove a confusing dollar sign from the example fingerprint in the
14805 man page, and also make the example fingerprint a valid one. Fixes
14806 bug 4309; bugfix on 0.2.1.3-alpha.
14807 - The next version of Windows will be called Windows 8, and it has
14808 a major version of 6, minor version of 2. Correctly identify that
14809 version instead of calling it "Very recent version". Resolves
14810 ticket 4153; reported by funkstar.
14811 - Downgrade log messages about circuit timeout calibration from
14812 "notice" to "info": they don't require or suggest any human
14813 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
14814 bugfix on 0.2.2.14-alpha.
14817 - Turn on directory request statistics by default and include them in
14818 extra-info descriptors. Don't break if we have no GeoIP database.
14819 Backported from 0.2.3.1-alpha; implements ticket 3951.
14820 - Update to the October 4 2011 Maxmind GeoLite Country database.
14823 Changes in version 0.2.1.31 - 2011-10-26
14824 Tor 0.2.1.31 backports important security and privacy fixes for
14825 oldstable. This release is intended only for package maintainers and
14826 others who cannot use the 0.2.2 stable series. All others should be
14827 using Tor 0.2.2.x or newer.
14829 o Security fixes (also included in 0.2.2.x):
14830 - Replace all potentially sensitive memory comparison operations
14831 with versions whose runtime does not depend on the data being
14832 compared. This will help resist a class of attacks where an
14833 adversary can use variations in timing information to learn
14834 sensitive data. Fix for one case of bug 3122. (Safe memcmp
14835 implementation by Robert Ransom based partially on code by DJB.)
14836 - Fix an assert in parsing router descriptors containing IPv6
14837 addresses. This one took down the directory authorities when
14838 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
14840 o Privacy/anonymity fixes (also included in 0.2.2.x):
14841 - Clients and bridges no longer send TLS certificate chains on
14842 outgoing OR connections. Previously, each client or bridge would
14843 use the same cert chain for all outgoing OR connections until
14844 its IP address changes, which allowed any relay that the client
14845 or bridge contacted to determine which entry guards it is using.
14846 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14847 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14848 no longer considers that connection as suitable for satisfying a
14849 circuit EXTEND request. Now relays can protect clients from the
14850 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14851 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14852 that they initiated. Relays could distinguish incoming bridge
14853 connections from client connections, creating another avenue for
14854 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14855 Found by "frosty_un".
14856 - When receiving a hidden service descriptor, check that it is for
14857 the hidden service we wanted. Previously, Tor would store any
14858 hidden service descriptors that a directory gave it, whether it
14859 wanted them or not. This wouldn't have let an attacker impersonate
14860 a hidden service, but it did let directories pre-seed a client
14861 with descriptors that it didn't want. Bugfix on 0.0.6.
14862 - Avoid linkability based on cached hidden service descriptors: forget
14863 all hidden service descriptors cached as a client when processing a
14864 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
14865 - Make the bridge directory authority refuse to answer directory
14866 requests for "all" descriptors. It used to include bridge
14867 descriptors in its answer, which was a major information leak.
14868 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
14869 - Don't attach new streams to old rendezvous circuits after SIGNAL
14870 NEWNYM. Previously, we would keep using an existing rendezvous
14871 circuit if it remained open (i.e. if it were kept open by a
14872 long-lived stream, or if a new stream were attached to it before
14873 Tor could notice that it was old and no longer in use). Bugfix on
14874 0.1.1.15-rc; fixes bug 3375.
14876 o Minor bugfixes (also included in 0.2.2.x):
14877 - When we restart our relay, we might get a successful connection
14878 from the outside before we've started our reachability tests,
14879 triggering a warning: "ORPort found reachable, but I have no
14880 routerinfo yet. Failing to inform controller of success." This
14881 bug was harmless unless Tor is running under a controller
14882 like Vidalia, in which case the controller would never get a
14883 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
14885 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
14886 enabled. Fixes bug 1526.
14887 - Remove undocumented option "-F" from tor-resolve: it hasn't done
14888 anything since 0.2.1.16-rc.
14889 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
14890 None of the cases where we did this before were wrong, but by making
14891 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
14892 - Fix a rare crash bug that could occur when a client was configured
14893 with a large number of bridges. Fixes bug 2629; bugfix on
14894 0.2.1.2-alpha. Bugfix by trac user "shitlei".
14895 - Correct the warning displayed when a rendezvous descriptor exceeds
14896 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
14898 - Fix an uncommon assertion failure when running with DNSPort under
14899 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
14900 - When warning about missing zlib development packages during compile,
14901 give the correct package names. Bugfix on 0.2.0.1-alpha.
14902 - Require that introduction point keys and onion keys have public
14903 exponent 65537. Bugfix on 0.2.0.10-alpha.
14904 - Do not crash when our configuration file becomes unreadable, for
14905 example due to a permissions change, between when we start up
14906 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
14908 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
14910 - Always NUL-terminate the sun_path field of a sockaddr_un before
14911 passing it to the kernel. (Not a security issue: kernels are
14912 smart enough to reject bad sockaddr_uns.) Found by Coverity;
14913 CID #428. Bugfix on Tor 0.2.0.3-alpha.
14914 - Don't stack-allocate the list of supplementary GIDs when we're
14915 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
14916 could take up to 256K, which is way too much stack. Found by
14917 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
14919 o Minor bugfixes (only in 0.2.1.x):
14920 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
14921 rely on them. Bugfix on 0.2.1.30.
14922 - Use git revisions instead of svn revisions when generating our
14923 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
14925 o Minor features (also included in 0.2.2.x):
14926 - Adjust the expiration time on our SSL session certificates to
14927 better match SSL certs seen in the wild. Resolves ticket 4014.
14928 - Allow nameservers with IPv6 address. Resolves bug 2574.
14929 - Update to the October 4 2011 Maxmind GeoLite Country database.
14932 Changes in version 0.2.3.5-alpha - 2011-09-28
14933 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
14934 bridge relays; fixes an assertion error that many users started hitting
14935 today; and adds the ability to refill token buckets more often than
14936 once per second, allowing significant performance improvements.
14939 - Bridge relays now do their directory fetches inside Tor TLS
14940 connections, like all the other clients do, rather than connecting
14941 directly to the DirPort like public relays do. Removes another
14942 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
14943 - Bridges relays now build circuits for themselves in a more similar
14944 way to how clients build them. Removes another avenue for
14945 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
14946 when bridges were introduced.
14949 - Fix an "Assertion md->held_by_node == 1 failed" error that could
14950 occur when the same microdescriptor was referenced by two node_t
14951 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
14953 o Major features (networking):
14954 - Add a new TokenBucketRefillInterval option to refill token buckets
14955 more frequently than once per second. This should improve network
14956 performance, alleviate queueing problems, and make traffic less
14957 bursty. Implements proposal 183; closes ticket 3630. Design by
14958 Florian Tschorsch and Björn Scheuermann; implementation by
14962 - Change an integer overflow check in the OpenBSD_Malloc code so
14963 that GCC is less likely to eliminate it as impossible. Patch
14964 from Mansour Moufid. Fixes bug 4059.
14966 o Minor bugfixes (usability):
14967 - Downgrade log messages about circuit timeout calibration from
14968 "notice" to "info": they don't require or suggest any human
14969 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
14970 bugfix on 0.2.2.14-alpha.
14972 o Minor features (diagnostics):
14973 - When the system call to create a listener socket fails, log the
14974 error message explaining why. This may help diagnose bug 4027.
14977 Changes in version 0.2.3.4-alpha - 2011-09-13
14978 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
14979 tweak to Tor's TLS handshake that makes relays and bridges that run
14980 this new version reachable from Iran again. It also fixes a few new
14981 bugs in 0.2.3.x, and teaches relays to recognize when they're not
14982 listed in the network consensus and republish.
14984 o Major bugfixes (also part of 0.2.2.33):
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, also part of 0.2.2.33):
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.
15001 o Minor features (also part of 0.2.2.33):
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 (also part of 0.2.2.33):
15013 - Demote the 'replay detected' log message emitted when a hidden
15014 service receives the same Diffie-Hellman public key in two different
15015 INTRODUCE2 cells to info level. A normal Tor client can cause that
15016 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
15017 fixes part of bug 2442.
15018 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
15019 level. There is nothing that a hidden service's operator can do
15020 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
15022 - Clarify a log message specifying the characters permitted in
15023 HiddenServiceAuthorizeClient client names. Previously, the log
15024 message said that "[A-Za-z0-9+-_]" were permitted; that could have
15025 given the impression that every ASCII character between "+" and "_"
15026 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
15028 o Build fixes (also part of 0.2.2.33):
15029 - Clean up some code issues that prevented Tor from building on older
15030 BSDs. Fixes bug 3894; reported by "grarpamp".
15031 - Search for a platform-specific version of "ar" when cross-compiling.
15032 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
15035 - Fix a bug where the SocksPort option (for example) would get
15036 ignored and replaced by the default if a SocksListenAddress
15037 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
15041 - Relays now try regenerating and uploading their descriptor more
15042 frequently if they are not listed in the consensus, or if the
15043 version of their descriptor listed in the consensus is too
15044 old. This fix should prevent situations where a server declines
15045 to re-publish itself because it has done so too recently, even
15046 though the authorities decided not to list its recent-enough
15047 descriptor. Fix for bug 3327.
15050 - Relays now include a reason for regenerating their descriptors
15051 in an HTTP header when uploading to the authorities. This will
15052 make it easier to debug descriptor-upload issues in the future.
15053 - When starting as root and then changing our UID via the User
15054 control option, and we have a ControlSocket configured, make sure
15055 that the ControlSocket is owned by the same account that Tor will
15056 run under. Implements ticket 3421; fix by Jérémy Bobbio.
15059 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
15060 utility function used in the control-port code). This shouldn't
15061 ever happen unless Tor is completely out of memory, but if it did
15062 happen and Tor somehow recovered from it, Tor could have sent a log
15063 message to a control port in the middle of a reply to a controller
15064 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
15065 - Make 'FetchUselessDescriptors' cause all descriptor types and
15066 all consensus types (including microdescriptors) to get fetched.
15067 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
15069 o Code refactoring:
15070 - Make a new "entry connection" struct as an internal subtype of "edge
15071 connection", to simplify the code and make exit connections smaller.
15074 Changes in version 0.2.2.33 - 2011-09-13
15075 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
15076 TLS handshake that makes relays and bridges that run this new version
15077 reachable from Iran again.
15080 - Avoid an assertion failure when reloading a configuration with
15081 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
15082 3923; bugfix on 0.2.2.25-alpha.
15084 o Minor features (security):
15085 - Check for replays of the public-key encrypted portion of an
15086 INTRODUCE1 cell, in addition to the current check for replays of
15087 the g^x value. This prevents a possible class of active attacks
15088 by an attacker who controls both an introduction point and a
15089 rendezvous point, and who uses the malleability of AES-CTR to
15090 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
15091 that these attacks are infeasible (requiring the attacker to send
15092 on the order of zettabytes of altered cells in a short interval),
15093 but we'd rather block them off in case there are any classes of
15094 this attack that we missed. Reported by Willem Pinckaers.
15097 - Adjust the expiration time on our SSL session certificates to
15098 better match SSL certs seen in the wild. Resolves ticket 4014.
15099 - Change the default required uptime for a relay to be accepted as
15100 a HSDir (hidden service directory) from 24 hours to 25 hours.
15101 Improves on 0.2.0.10-alpha; resolves ticket 2649.
15102 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
15103 authorities to abstain from voting on assignment of the HSDir
15104 consensus flag. Related to bug 2649.
15105 - Update to the September 6 2011 Maxmind GeoLite Country database.
15107 o Minor bugfixes (documentation and log messages):
15108 - Correct the man page to explain that HashedControlPassword and
15109 CookieAuthentication can both be set, in which case either method
15110 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
15111 when we decided to allow these config options to both be set. Issue
15112 raised by bug 3898.
15113 - Demote the 'replay detected' log message emitted when a hidden
15114 service receives the same Diffie-Hellman public key in two different
15115 INTRODUCE2 cells to info level. A normal Tor client can cause that
15116 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
15117 fixes part of bug 2442.
15118 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
15119 level. There is nothing that a hidden service's operator can do
15120 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
15122 - Clarify a log message specifying the characters permitted in
15123 HiddenServiceAuthorizeClient client names. Previously, the log
15124 message said that "[A-Za-z0-9+-_]" were permitted; that could have
15125 given the impression that every ASCII character between "+" and "_"
15126 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
15129 - Provide a substitute implementation of lround() for MSVC, which
15130 apparently lacks it. Patch from Gisle Vanem.
15131 - Clean up some code issues that prevented Tor from building on older
15132 BSDs. Fixes bug 3894; reported by "grarpamp".
15133 - Search for a platform-specific version of "ar" when cross-compiling.
15134 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
15137 Changes in version 0.2.3.3-alpha - 2011-09-01
15138 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
15139 security, and provides client-side support for the microdescriptor
15140 and optimistic data features introduced earlier in the 0.2.3.x
15141 series. It also includes numerous critical bugfixes in the (optional)
15142 bufferevent-based networking backend.
15144 o Major features (stream isolation):
15145 - You can now configure Tor so that streams from different
15146 applications are isolated on different circuits, to prevent an
15147 attacker who sees your streams as they leave an exit node from
15148 linking your sessions to one another. To do this, choose some way
15149 to distinguish the applications: have them connect to different
15150 SocksPorts, or have one of them use SOCKS4 while the other uses
15151 SOCKS5, or have them pass different authentication strings to the
15152 SOCKS proxy. Then, use the new SocksPort syntax to configure the
15153 degree of isolation you need. This implements Proposal 171.
15154 - There's a new syntax for specifying multiple client ports (such as
15155 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
15156 multiple *Port entries with full addr:port syntax on each.
15157 The old *ListenAddress format is still supported, but you can't
15158 mix it with the new *Port syntax.
15160 o Major features (other):
15161 - Enable microdescriptor fetching by default for clients. This allows
15162 clients to download a much smaller amount of directory information.
15163 To disable it (and go back to the old-style consensus and
15164 descriptors), set "UseMicrodescriptors 0" in your torrc file.
15165 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
15166 "PortForwarding" config option), now supports Windows.
15167 - When using an exit relay running 0.2.3.x, clients can now
15168 "optimistically" send data before the exit relay reports that
15169 the stream has opened. This saves a round trip when starting
15170 connections where the client speaks first (such as web browsing).
15171 This behavior is controlled by a consensus parameter (currently
15172 disabled). To turn it on or off manually, use the "OptimisticData"
15173 torrc option. Implements proposal 181; code by Ian Goldberg.
15175 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
15176 - When using IOCP on Windows, we need to enable Libevent windows
15178 - The IOCP backend now works even when the user has not specified
15179 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
15180 Fixes part of bug 3752.
15181 - Correctly record the bytes we've read and written when using
15182 bufferevents, so that we can include them in our bandwidth history
15183 and advertised bandwidth. Fixes bug 3803.
15184 - Apply rate-limiting only at the bottom of a chain of filtering
15185 bufferevents. This prevents us from filling up internal read
15186 buffers and violating rate-limits when filtering bufferevents
15187 are enabled. Fixes part of bug 3804.
15188 - Add high-watermarks to the output buffers for filtered
15189 bufferevents. This prevents us from filling up internal write
15190 buffers and wasting CPU cycles when filtering bufferevents are
15191 enabled. Fixes part of bug 3804.
15192 - Correctly notice when data has been written from a bufferevent
15193 without flushing it completely. Fixes bug 3805.
15194 - Fix a bug where server-side tunneled bufferevent-based directory
15195 streams would get closed prematurely. Fixes bug 3814.
15196 - Fix a use-after-free error with per-connection rate-limiting
15197 buckets. Fixes bug 3888.
15199 o Major bugfixes (also part of 0.2.2.31-rc):
15200 - If we're configured to write our ControlPorts to disk, only write
15201 them after switching UID and creating the data directory. This way,
15202 we don't fail when starting up with a nonexistent DataDirectory
15203 and a ControlPortWriteToFile setting based on that directory. Fixes
15204 bug 3747; bugfix on Tor 0.2.2.26-beta.
15207 - Added a new CONF_CHANGED event so that controllers can be notified
15208 of any configuration changes made by other controllers, or by the
15209 user. Implements ticket 1692.
15210 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
15211 leak when using bufferevents, and lets Libevent worry about how to
15212 best copy data out of a buffer.
15213 - Replace files in stats/ rather than appending to them. Now that we
15214 include statistics in extra-info descriptors, it makes no sense to
15215 keep old statistics forever. Implements ticket 2930.
15217 o Minor features (build compatibility):
15218 - Limited, experimental support for building with nmake and MSVC.
15219 - Provide a substitute implementation of lround() for MSVC, which
15220 apparently lacks it. Patch from Gisle Vanem.
15222 o Minor features (also part of 0.2.2.31-rc):
15223 - Update to the August 2 2011 Maxmind GeoLite Country database.
15225 o Minor bugfixes (on 0.2.3.x-alpha):
15226 - Fix a spurious warning when parsing SOCKS requests with
15227 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
15228 - Get rid of a harmless warning that could happen on relays running
15229 with bufferevents. The warning was caused by someone doing an http
15230 request to a relay's orport. Also don't warn for a few related
15231 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
15233 o Minor bugfixes (on 2.2.x and earlier):
15234 - Correct the man page to explain that HashedControlPassword and
15235 CookieAuthentication can both be set, in which case either method
15236 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
15237 when we decided to allow these config options to both be set. Issue
15238 raised by bug 3898.
15239 - The "--quiet" and "--hush" options now apply not only to Tor's
15240 behavior before logs are configured, but also to Tor's behavior in
15241 the absense of configured logs. Fixes bug 3550; bugfix on
15244 o Minor bugfixes (also part of 0.2.2.31-rc):
15245 - Write several files in text mode, on OSes that distinguish text
15246 mode from binary mode (namely, Windows). These files are:
15247 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
15248 that collect those statistics; 'client_keys' and 'hostname' for
15249 hidden services that use authentication; and (in the tor-gencert
15250 utility) newly generated identity and signing keys. Previously,
15251 we wouldn't specify text mode or binary mode, leading to an
15252 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
15253 the DirRecordUsageByCountry option which would have triggered
15254 the assertion failure was added), although this assertion failure
15255 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
15256 - Selectively disable deprecation warnings on OS X because Lion
15257 started deprecating the shipped copy of openssl. Fixes bug 3643.
15258 - Remove an extra pair of quotation marks around the error
15259 message in control-port STATUS_GENERAL BUG events. Bugfix on
15260 0.1.2.6-alpha; fixes bug 3732.
15261 - When unable to format an address as a string, report its value
15262 as "???" rather than reusing the last formatted address. Bugfix
15265 o Code simplifications and refactoring:
15266 - Rewrite the listener-selection logic so that parsing which ports
15267 we want to listen on is now separate from binding to the ports
15271 - Building Tor with bufferevent support now requires Libevent
15272 2.0.13-stable or later. Previous versions of Libevent had bugs in
15273 SSL-related bufferevents and related issues that would make Tor
15274 work badly with bufferevents. Requiring 2.0.13-stable also allows
15275 Tor with bufferevents to take advantage of Libevent APIs
15276 introduced after 2.0.8-rc.
15279 Changes in version 0.2.2.32 - 2011-08-27
15280 The Tor 0.2.2 release series is dedicated to the memory of Andreas
15281 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
15282 a founder of the PETS community, a leader in our field, a mentor,
15283 and a friend. He left us with these words: "I had the possibility
15284 to contribute to this world that is not as it should be. I hope I
15285 could help in some areas to make the world a better place, and that
15286 I could also encourage other people to be engaged in improving the
15287 world. Please, stay engaged. This world needs you, your love, your
15288 initiative -- now I cannot be part of that anymore."
15290 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
15291 ready. More than two years in the making, this release features improved
15292 client performance and hidden service reliability, better compatibility
15293 for Android, correct behavior for bridges that listen on more than
15294 one address, more extensible and flexible directory object handling,
15295 better reporting of network statistics, improved code security, and
15296 many many other features and bugfixes.
15299 Changes in version 0.2.2.31-rc - 2011-08-17
15300 Tor 0.2.2.31-rc is the second and hopefully final release candidate
15301 for the Tor 0.2.2.x series.
15304 - Remove an extra pair of quotation marks around the error
15305 message in control-port STATUS_GENERAL BUG events. Bugfix on
15306 0.1.2.6-alpha; fixes bug 3732.
15307 - If we're configured to write our ControlPorts to disk, only write
15308 them after switching UID and creating the data directory. This way,
15309 we don't fail when starting up with a nonexistent DataDirectory
15310 and a ControlPortWriteToFile setting based on that directory. Fixes
15311 bug 3747; bugfix on Tor 0.2.2.26-beta.
15314 - Update to the August 2 2011 Maxmind GeoLite Country database.
15317 - Allow GETINFO fingerprint to return a fingerprint even when
15318 we have not yet built a router descriptor. Fixes bug 3577;
15319 bugfix on 0.2.0.1-alpha.
15320 - Write several files in text mode, on OSes that distinguish text
15321 mode from binary mode (namely, Windows). These files are:
15322 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
15323 that collect those statistics; 'client_keys' and 'hostname' for
15324 hidden services that use authentication; and (in the tor-gencert
15325 utility) newly generated identity and signing keys. Previously,
15326 we wouldn't specify text mode or binary mode, leading to an
15327 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
15328 the DirRecordUsageByCountry option which would have triggered
15329 the assertion failure was added), although this assertion failure
15330 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
15331 - Selectively disable deprecation warnings on OS X because Lion
15332 started deprecating the shipped copy of openssl. Fixes bug 3643.
15333 - When unable to format an address as a string, report its value
15334 as "???" rather than reusing the last formatted address. Bugfix
15338 Changes in version 0.2.3.2-alpha - 2011-07-18
15339 Tor 0.2.3.2-alpha introduces two new experimental features:
15340 microdescriptors and pluggable transports. It also continues cleaning
15341 up a variety of recently introduced features.
15344 - Clients can now use microdescriptors instead of regular descriptors
15345 to build circuits. Microdescriptors are authority-generated
15346 summaries of regular descriptors' contents, designed to change
15347 very rarely (see proposal 158 for details). This feature is
15348 designed to save bandwidth, especially for clients on slow internet
15349 connections. It's off by default for now, since nearly no caches
15350 support it, but it will be on-by-default for clients in a future
15351 version. You can use the UseMicrodescriptors option to turn it on.
15352 - Tor clients using bridges can now be configured to use a separate
15353 'transport' proxy for each bridge. This approach helps to resist
15354 censorship by allowing bridges to use protocol obfuscation
15355 plugins. It implements part of proposal 180. Implements ticket 2841.
15356 - While we're trying to bootstrap, record how many TLS connections
15357 fail in each state, and report which states saw the most failures
15358 in response to any bootstrap failures. This feature may speed up
15359 diagnosis of censorship events. Implements ticket 3116.
15361 o Major bugfixes (on 0.2.3.1-alpha):
15362 - When configuring a large set of nodes in EntryNodes (as with
15363 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
15364 random subset to be guards, and choose them in random
15365 order. Fixes bug 2798.
15366 - Tor could crash when remembering a consensus in a non-used consensus
15367 flavor without having a current consensus set. Fixes bug 3361.
15368 - Comparing an unknown address to a microdescriptor's shortened exit
15369 policy would always give a "rejected" result. Fixes bug 3599.
15370 - Using microdescriptors as a client no longer prevents Tor from
15371 uploading and downloading hidden service descriptors. Fixes
15375 - Allow nameservers with IPv6 address. Resolves bug 2574.
15376 - Accept attempts to include a password authenticator in the
15377 handshake, as supported by SOCKS5. This handles SOCKS clients that
15378 don't know how to omit a password when authenticating. Resolves
15380 - When configuring a large set of nodes in EntryNodes, and there are
15381 enough of them listed as Guard so that we don't need to consider
15382 the non-guard entries, prefer the ones listed with the Guard flag.
15383 - Check for and recover from inconsistency in the microdescriptor
15384 cache. This will make it harder for us to accidentally free a
15385 microdescriptor without removing it from the appropriate data
15386 structures. Fixes issue 3135; issue noted by "wanoskarnet".
15387 - Log SSL state transitions at log level DEBUG, log domain
15388 HANDSHAKE. This can be useful for debugging censorship events.
15389 Implements ticket 3264.
15390 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
15391 implements ticket 3439.
15393 o Minor bugfixes (on 0.2.3.1-alpha):
15394 - Do not free all general-purpose regular descriptors just
15395 because microdescriptor use is enabled. Fixes bug 3113.
15396 - Correctly link libevent_openssl when --enable-static-libevent
15397 is passed to configure. Fixes bug 3118.
15398 - Bridges should not complain during their heartbeat log messages that
15399 they are unlisted in the consensus: that's more or less the point
15400 of being a bridge. Fixes bug 3183.
15401 - Report a SIGNAL event to controllers when acting on a delayed
15402 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
15403 event to the controller if we acted on a SIGNAL NEWNYM command
15404 immediately, and otherwise not report a SIGNAL event for the
15405 command at all. Fixes bug 3349.
15406 - Fix a crash when handling the SIGNAL controller command or
15407 reporting ERR-level status events with bufferevents enabled. Found
15408 by Robert Ransom. Fixes bug 3367.
15409 - Always ship the tor-fw-helper manpage in our release tarballs.
15410 Fixes bug 3389. Reported by Stephen Walker.
15411 - Fix a class of double-mark-for-close bugs when bufferevents
15412 are enabled. Fixes bug 3403.
15413 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
15414 - Add SIGNAL to the list returned by the 'GETINFO events/names'
15415 control-port command. Fixes part of bug 3465.
15416 - Prevent using negative indices during unit test runs when read_all()
15417 fails. Spotted by coverity.
15418 - Fix a rare memory leak when checking the nodelist without it being
15419 present. Found by coverity.
15420 - Only try to download a microdescriptor-flavored consensus from
15421 a directory cache that provides them.
15423 o Minor bugfixes (on 0.2.2.x and earlier):
15424 - Assert that hidden-service-related operations are not performed
15425 using single-hop circuits. Previously, Tor would assert that
15426 client-side streams are not attached to single-hop circuits,
15427 but not that other sensitive operations on the client and service
15428 side are not performed using single-hop circuits. Fixes bug 3332;
15430 - Don't publish a new relay descriptor when we reload our onion key,
15431 unless the onion key has actually changed. Fixes bug 3263 and
15432 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
15433 - Allow GETINFO fingerprint to return a fingerprint even when
15434 we have not yet built a router descriptor. Fixes bug 3577;
15435 bugfix on 0.2.0.1-alpha.
15436 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
15437 on 0.2.2.4-alpha; fixes bug 3427.
15439 o Code simplification and refactoring:
15440 - Use tor_sscanf() in place of scanf() in more places through the
15441 code. This makes us a little more locale-independent, and
15442 should help shut up code-analysis tools that can't tell
15443 a safe sscanf string from a dangerous one.
15444 - Use tt_assert(), not tor_assert(), for checking for test failures.
15445 This makes the unit tests more able to go on in the event that
15447 - Split connection_about_to_close() into separate functions for each
15451 - On Windows, we now define the _WIN32_WINNT macros only if they
15452 are not already defined. This lets the person building Tor decide,
15453 if they want, to require a later version of Windows.
15456 Changes in version 0.2.2.30-rc - 2011-07-07
15457 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
15458 series. It fixes a few smaller bugs, but generally appears stable.
15459 Please test it and let us know whether it is!
15462 - Send a SUCCEEDED stream event to the controller when a reverse
15463 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
15464 discovered by katmagic.
15465 - Always NUL-terminate the sun_path field of a sockaddr_un before
15466 passing it to the kernel. (Not a security issue: kernels are
15467 smart enough to reject bad sockaddr_uns.) Found by Coverity;
15468 CID #428. Bugfix on Tor 0.2.0.3-alpha.
15469 - Don't stack-allocate the list of supplementary GIDs when we're
15470 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
15471 could take up to 256K, which is way too much stack. Found by
15472 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
15473 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
15474 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
15475 fixes part of bug 3465.
15476 - Fix a memory leak when receiving a descriptor for a hidden
15477 service we didn't ask for. Found by Coverity; CID #30. Bugfix
15481 - Update to the July 1 2011 Maxmind GeoLite Country database.
15484 Changes in version 0.2.2.29-beta - 2011-06-20
15485 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
15486 have bridge lines in their torrc but don't want to use them; gets
15487 us closer to having the control socket feature working on Debian;
15488 and fixes a variety of smaller bugs.
15491 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
15492 When we changed the default behavior to "use bridges if any
15493 are listed in the torrc", we surprised users who had bridges
15494 in their torrc files but who didn't actually want to use them.
15495 Partial resolution for bug 3354.
15498 - Don't attach new streams to old rendezvous circuits after SIGNAL
15499 NEWNYM. Previously, we would keep using an existing rendezvous
15500 circuit if it remained open (i.e. if it were kept open by a
15501 long-lived stream, or if a new stream were attached to it before
15502 Tor could notice that it was old and no longer in use). Bugfix on
15503 0.1.1.15-rc; fixes bug 3375.
15506 - Fix a bug when using ControlSocketsGroupWritable with User. The
15507 directory's group would be checked against the current group, not
15508 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
15509 bugfix on 0.2.2.26-beta.
15510 - Make connection_printf_to_buf()'s behavior sane. Its callers
15511 expect it to emit a CRLF iff the format string ends with CRLF;
15512 it actually emitted a CRLF iff (a) the format string ended with
15513 CRLF or (b) the resulting string was over 1023 characters long or
15514 (c) the format string did not end with CRLF *and* the resulting
15515 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
15516 fixes part of bug 3407.
15517 - Make send_control_event_impl()'s behavior sane. Its callers
15518 expect it to always emit a CRLF at the end of the string; it
15519 might have emitted extra control characters as well. Bugfix on
15520 0.1.1.9-alpha; fixes another part of bug 3407.
15521 - Make crypto_rand_int() check the value of its input correctly.
15522 Previously, it accepted values up to UINT_MAX, but could return a
15523 negative number if given a value above INT_MAX+1. Found by George
15524 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
15525 - Avoid a segfault when reading a malformed circuit build state
15526 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
15528 - When asked about a DNS record type we don't support via a
15529 client DNSPort, reply with NOTIMPL rather than an empty
15530 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
15531 - Fix a rare memory leak during stats writing. Found by coverity.
15534 - Update to the June 1 2011 Maxmind GeoLite Country database.
15536 o Code simplifications and refactoring:
15537 - Remove some dead code as indicated by coverity.
15538 - Remove a few dead assignments during router parsing. Found by
15540 - Add some forgotten return value checks during unit tests. Found
15542 - Don't use 1-bit wide signed bit fields. Found by coverity.
15545 Changes in version 0.2.2.28-beta - 2011-06-04
15546 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
15547 fixed a big bug in whether relays stay in the consensus consistently,
15548 we moved closer to handling bridges and hidden services correctly,
15549 and we started the process of better handling the dreaded "my Vidalia
15550 died, and now my Tor demands a password when I try to reconnect to it"
15554 - Don't decide to make a new descriptor when receiving a HUP signal.
15555 This bug has caused a lot of 0.2.2.x relays to disappear from the
15556 consensus periodically. Fixes the most common case of triggering
15557 bug 1810; bugfix on 0.2.2.7-alpha.
15558 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
15559 - Don't try to build descriptors if "ORPort auto" is set and we
15560 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
15562 - Resolve a crash that occurred when setting BridgeRelay to 1 with
15563 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
15564 - Apply circuit timeouts to opened hidden-service-related circuits
15565 based on the correct start time. Previously, we would apply the
15566 circuit build timeout based on time since the circuit's creation;
15567 it was supposed to be applied based on time since the circuit
15568 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
15569 - Use the same circuit timeout for client-side introduction
15570 circuits as for other four-hop circuits, rather than the timeout
15571 for single-hop directory-fetch circuits; the shorter timeout may
15572 have been appropriate with the static circuit build timeout in
15573 0.2.1.x and earlier, but caused many hidden service access attempts
15574 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
15575 on 0.2.2.2-alpha; fixes another part of bug 1297.
15576 - In ticket 2511 we fixed a case where you could use an unconfigured
15577 bridge if you had configured it as a bridge the last time you ran
15578 Tor. Now fix another edge case: if you had configured it as a bridge
15579 but then switched to a different bridge via the controller, you
15580 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
15584 - Add an __OwningControllerProcess configuration option and a
15585 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
15586 that when it exits, Tor will shut down. Implements feature 3049.
15587 - If "UseBridges 1" is set and no bridges are configured, Tor will
15588 now refuse to build any circuits until some bridges are set.
15589 If "UseBridges auto" is set, Tor will use bridges if they are
15590 configured and we are not running as a server, but otherwise will
15591 make circuits as usual. The new default is "auto". Patch by anonym,
15592 so the Tails LiveCD can stop automatically revealing you as a Tor
15596 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
15597 - Remove a trailing asterisk from "exit-policy/default" in the
15598 output of the control port command "GETINFO info/names". Bugfix
15600 - Use a wide type to hold sockets when built for 64-bit Windows builds.
15602 - Warn when the user configures two HiddenServiceDir lines that point
15603 to the same directory. Bugfix on 0.0.6 (the version introducing
15604 HiddenServiceDir); fixes bug 3289.
15605 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
15606 part of bug 2748; bugfix on 0.2.0.10-alpha.
15607 - Log malformed requests for rendezvous descriptors as protocol
15608 warnings, not warnings. Also, use a more informative log message
15609 in case someone sees it at log level warning without prior
15610 info-level messages. Fixes the other part of bug 2748; bugfix
15612 - Clear the table recording the time of the last request for each
15613 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
15614 Previously, we would clear our HS descriptor cache on SIGNAL
15615 NEWNYM, but if we had previously retrieved a descriptor (or tried
15616 to) from every directory responsible for it, we would refuse to
15617 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
15619 - Fix a log message that said "bits" while displaying a value in
15620 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
15622 - When checking for 1024-bit keys, check for 1024 bits, not 128
15623 bytes. This allows Tor to correctly discard keys of length 1017
15624 through 1023. Bugfix on 0.0.9pre5.
15627 - Relays now log the reason for publishing a new relay descriptor,
15628 so we have a better chance of hunting down instances of bug 1810.
15629 Resolves ticket 3252.
15630 - Revise most log messages that refer to nodes by nickname to
15631 instead use the "$key=nickname at address" format. This should be
15632 more useful, especially since nicknames are less and less likely
15633 to be unique. Resolves ticket 3045.
15634 - Log (at info level) when purging pieces of hidden-service-client
15635 state because of SIGNAL NEWNYM.
15638 - Remove undocumented option "-F" from tor-resolve: it hasn't done
15639 anything since 0.2.1.16-rc.
15642 Changes in version 0.2.2.27-beta - 2011-05-18
15643 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
15644 release, and also adds a few more general bugfixes.
15647 - Fix a crash bug when changing bridges in a running Tor process.
15648 Fixes bug 3213; bugfix on 0.2.2.26-beta.
15649 - When the controller configures a new bridge, don't wait 10 to 60
15650 seconds before trying to fetch its descriptor. Bugfix on
15651 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
15654 - Require that onion keys have exponent 65537 in microdescriptors too.
15655 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
15656 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
15657 Changed the limit to 512 characters by removing base64 newlines.
15658 Fixes bug 2752. Fix by Michael Yakubovich.
15659 - When a client starts or stops using bridges, never use a circuit
15660 that was built before the configuration change. This behavior could
15661 put at risk a user who uses bridges to ensure that her traffic
15662 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
15666 Changes in version 0.2.2.26-beta - 2011-05-17
15667 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
15668 also introduces a new "socksport auto" approach that should make it
15669 easier to run multiple Tors on the same system, and does a lot of
15670 cleanup to get us closer to a release candidate.
15672 o Security/privacy fixes:
15673 - Replace all potentially sensitive memory comparison operations
15674 with versions whose runtime does not depend on the data being
15675 compared. This will help resist a class of attacks where an
15676 adversary can use variations in timing information to learn
15677 sensitive data. Fix for one case of bug 3122. (Safe memcmp
15678 implementation by Robert Ransom based partially on code by DJB.)
15679 - When receiving a hidden service descriptor, check that it is for
15680 the hidden service we wanted. Previously, Tor would store any
15681 hidden service descriptors that a directory gave it, whether it
15682 wanted them or not. This wouldn't have let an attacker impersonate
15683 a hidden service, but it did let directories pre-seed a client
15684 with descriptors that it didn't want. Bugfix on 0.0.6.
15685 - On SIGHUP, do not clear out all TrackHostExits mappings, client
15686 DNS cache entries, and virtual address mappings: that's what
15687 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
15690 - The options SocksPort, ControlPort, and so on now all accept a
15691 value "auto" that opens a socket on an OS-selected port. A
15692 new ControlPortWriteToFile option tells Tor to write its
15693 actual control port or ports to a chosen file. If the option
15694 ControlPortFileGroupReadable is set, the file is created as
15695 group-readable. Now users can run two Tor clients on the same
15696 system without needing to manually mess with parameters. Resolves
15697 part of ticket 3076.
15698 - Set SO_REUSEADDR on all sockets, not just listeners. This should
15699 help busy exit nodes avoid running out of useable ports just
15700 because all the ports have been used in the near past. Resolves
15704 - New "GETINFO net/listeners/(type)" controller command to return
15705 a list of addresses and ports that are bound for listeners for a
15706 given connection type. This is useful when the user has configured
15707 "SocksPort auto" and the controller needs to know which port got
15708 chosen. Resolves another part of ticket 3076.
15709 - Add a new ControlSocketsGroupWritable configuration option: when
15710 it is turned on, ControlSockets are group-writeable by the default
15711 group of the current user. Patch by Jérémy Bobbio; implements
15713 - Tor now refuses to create a ControlSocket in a directory that is
15714 world-readable (or group-readable if ControlSocketsGroupWritable
15715 is 0). This is necessary because some operating systems do not
15716 enforce permissions on an AF_UNIX sockets. Permissions on the
15717 directory holding the socket, however, seems to work everywhere.
15718 - Rate-limit a warning about failures to download v2 networkstatus
15719 documents. Resolves part of bug 1352.
15720 - Backport code from 0.2.3.x that allows directory authorities to
15721 clean their microdescriptor caches. Needed to resolve bug 2230.
15722 - When an HTTPS proxy reports "403 Forbidden", we now explain
15723 what it means rather than calling it an unexpected status code.
15724 Closes bug 2503. Patch from Michael Yakubovich.
15725 - Update to the May 1 2011 Maxmind GeoLite Country database.
15728 - Authorities now clean their microdesc cache periodically and when
15729 reading from disk initially, not only when adding new descriptors.
15730 This prevents a bug where we could lose microdescriptors. Bugfix
15731 on 0.2.2.6-alpha. Fixes bug 2230.
15732 - Do not crash when our configuration file becomes unreadable, for
15733 example due to a permissions change, between when we start up
15734 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
15736 - Avoid a bug that would keep us from replacing a microdescriptor
15737 cache on Windows. (We would try to replace the file while still
15738 holding it open. That's fine on Unix, but Windows doesn't let us
15739 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
15740 - Add missing explanations for the authority-related torrc options
15741 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
15742 man page. Resolves issue 2379.
15743 - As an authority, do not upload our own vote or signature set to
15744 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
15745 it would get flagged as a duplicate. Resolves bug 3026.
15746 - Accept hidden service descriptors if we think we might be a hidden
15747 service directory, regardless of what our consensus says. This
15748 helps robustness, since clients and hidden services can sometimes
15749 have a more up-to-date view of the network consensus than we do,
15750 and if they think that the directory authorities list us a HSDir,
15751 we might actually be one. Related to bug 2732; bugfix on
15753 - When a controller changes TrackHostExits, remove mappings for
15754 hosts that should no longer have their exits tracked. Bugfix on
15756 - When a controller changes VirtualAddrNetwork, remove any mappings
15757 for hosts that were automapped to the old network. Bugfix on
15759 - When a controller changes one of the AutomapHosts* options, remove
15760 any mappings for hosts that should no longer be automapped. Bugfix
15762 - Do not reset the bridge descriptor download status every time we
15763 re-parse our configuration or get a configuration change. Fixes
15764 bug 3019; bugfix on 0.2.0.3-alpha.
15766 o Minor bugfixes (code cleanup):
15767 - When loading the microdesc journal, remember its current size.
15768 In 0.2.2, this helps prevent the microdesc journal from growing
15769 without limit on authorities (who are the only ones to use it in
15770 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
15771 Fix posted by "cypherpunks."
15772 - The microdesc journal is supposed to get rebuilt only if it is
15773 at least _half_ the length of the store, not _twice_ the length
15774 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
15775 - Fix a potential null-pointer dereference while computing a
15776 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
15778 - Avoid a possible null-pointer dereference when rebuilding the mdesc
15779 cache without actually having any descriptors to cache. Bugfix on
15780 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
15781 - If we fail to compute the identity digest of a v3 legacy keypair,
15782 warn, and don't use a buffer-full of junk instead. Bugfix on
15783 0.2.1.1-alpha; fixes bug 3106.
15784 - Resolve an untriggerable issue in smartlist_string_num_isin(),
15785 where if the function had ever in the future been used to check
15786 for the presence of a too-large number, it would have given an
15787 incorrect result. (Fortunately, we only used it for 16-bit
15788 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
15789 - Require that introduction point keys and onion handshake keys
15790 have a public exponent of 65537. Starts to fix bug 3207; bugfix
15793 o Removed features:
15794 - Caches no longer download and serve v2 networkstatus documents
15795 unless FetchV2Networkstatus flag is set: these documents haven't
15796 haven't been used by clients or relays since 0.2.0.x. Resolves
15800 Changes in version 0.2.3.1-alpha - 2011-05-05
15801 Tor 0.2.3.1-alpha adds some new experimental features, including support
15802 for an improved network IO backend, IOCP networking on Windows,
15803 microdescriptor caching, "fast-start" support for streams, and automatic
15804 home router configuration. There are also numerous internal improvements
15805 to try to make the code easier for developers to work with.
15807 This is the first alpha release in a new series, so expect there to be
15808 bugs. Users who would rather test out a more stable branch should
15809 stay with 0.2.2.x for now.
15812 - Tor can now optionally build with the "bufferevents" buffered IO
15813 backend provided by Libevent 2. To use this feature, make sure you
15814 have the latest possible version of Libevent, and pass the
15815 --enable-bufferevents flag to configure when building Tor from
15816 source. This feature will make our networking code more flexible,
15817 let us stack layers on each other, and let us use more efficient
15818 zero-copy transports where available.
15819 - As an experimental feature, Tor can use IOCP for networking on Windows.
15820 Once this code is tuned and optimized, it promises much better
15821 performance than the select-based backend we've used in the past. To
15822 try this feature, you must build Tor with Libevent 2, configure Tor
15823 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
15824 your torrc. There are known bugs here: only try this if you can help
15825 debug it as it breaks.
15826 - The EntryNodes option can now include country codes like {de} or IP
15827 addresses or network masks. Previously we had disallowed these options
15828 because we didn't have an efficient way to keep the list up to
15829 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
15830 - Exit nodes now accept and queue data on not-yet-connected streams.
15831 Previously, the client wasn't allowed to send data until the stream was
15832 connected, which slowed down all connections. This change will enable
15833 clients to perform a "fast-start" on streams and send data without
15834 having to wait for a confirmation that the stream has opened. (Patch
15835 from Ian Goldberg; implements the server side of Proposal 174.)
15836 - Tor now has initial support for automatic port mapping on the many
15837 home routers that support NAT-PMP or UPnP. (Not yet supported on
15838 Windows). To build the support code, you'll need to have libnatpnp
15839 library and/or the libminiupnpc library, and you'll need to enable the
15840 feature specifically by passing "--enable-upnp" and/or
15841 "--enable-natpnp" to configure. To turn it on, use the new
15842 PortForwarding option.
15843 - Caches now download, cache, and serve multiple "flavors" of the
15844 consensus, including a flavor that describes microdescriptors.
15845 - Caches now download, cache, and serve microdescriptors -- small
15846 summaries of router descriptors that are authenticated by all of the
15847 directory authorities. Once enough caches are running this code,
15848 clients will be able to save significant amounts of directory bandwidth
15849 by downloading microdescriptors instead of router descriptors.
15852 - Make logging resolution configurable with a new LogTimeGranularity
15853 option, and change the default from 1 millisecond to 1 second.
15854 Implements enhancement 1668.
15855 - We log which torrc file we're using on startup. Implements ticket
15857 - Ordinarily, Tor does not count traffic from private addresses (like
15858 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
15859 There is now a new option, CountPrivateBandwidth, to disable this
15860 behavior. Patch from Daniel Cagara.
15861 - New --enable-static-tor configure option for building Tor as
15862 statically as possible. Idea, general hackery and thoughts from
15863 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
15865 - If you set the NumCPUs option to 0, Tor will now try to detect how
15866 many CPUs you have. This is the new default behavior.
15867 - Turn on directory request statistics by default and include them in
15868 extra-info descriptors. Don't break if we have no GeoIP database.
15869 - Relays that set "ConnDirectionStatistics 1" write statistics on the
15870 bidirectional use of connections to disk every 24 hours.
15871 - Add a GeoIP file digest to the extra-info descriptor. Implements
15873 - The NodeFamily option -- which let you declare that you want to
15874 consider nodes to be part of a family whether they list themselves
15875 that way or not -- now allows IP address ranges and country codes.
15876 - Add a new 'Heartbeat' log message type to periodically log a message
15877 describing Tor's status at level Notice. This feature is meant for
15878 operators who log at notice, and want to make sure that their Tor
15879 server is still working. Implementation by George Kadianakis.
15881 o Minor bugfixes (on 0.2.2.25-alpha):
15882 - When loading the microdesc journal, remember its current size.
15883 In 0.2.2, this helps prevent the microdesc journal from growing
15884 without limit on authorities (who are the only ones to use it in
15885 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
15886 Fix posted by "cypherpunks."
15887 - The microdesc journal is supposed to get rebuilt only if it is
15888 at least _half_ the length of the store, not _twice_ the length
15889 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
15890 - If as an authority we fail to compute the identity digest of a v3
15891 legacy keypair, warn, and don't use a buffer-full of junk instead.
15892 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
15893 - Authorities now clean their microdesc cache periodically and when
15894 reading from disk initially, not only when adding new descriptors.
15895 This prevents a bug where we could lose microdescriptors. Bugfix
15898 o Minor features (controller):
15899 - Add a new SIGNAL event to the controller interface so that
15900 controllers can be notified when Tor handles a signal. Resolves
15901 issue 1955. Patch by John Brooks.
15902 - Add a new GETINFO option to get total bytes read and written. Patch
15903 from pipe, revised by atagar. Resolves ticket 2345.
15904 - Implement some GETINFO controller fields to provide information about
15905 the Tor process's pid, euid, username, and resource limits.
15908 - Our build system requires automake 1.6 or later to create the
15909 Makefile.in files. Previously, you could have used 1.4.
15910 This only affects developers and people building Tor from git;
15911 people who build Tor from the source distribution without changing
15912 the Makefile.am files should be fine.
15913 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
15914 so on. This is more robust against some of the failure modes
15915 associated with running the autotools pieces on their own.
15917 o Minor packaging issues:
15918 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
15919 already created. Patch from Andreas Stieger. Fixes bug 2573.
15921 o Code simplifications and refactoring:
15922 - A major revision to our internal node-selecting and listing logic.
15923 Tor already had at least two major ways to look at the question of
15924 "which Tor servers do we know about": a list of router descriptors,
15925 and a list of entries in the current consensus. With
15926 microdescriptors, we're adding a third. Having so many systems
15927 without an abstraction layer over them was hurting the codebase.
15928 Now, we have a new "node_t" abstraction that presents a consistent
15929 interface to a client's view of a Tor node, and holds (nearly) all
15930 of the mutable state formerly in routerinfo_t and routerstatus_t.
15931 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
15932 no longer link against Libevent: they never used it, but
15933 our library structure used to force them to link it.
15935 o Removed features:
15936 - Remove some old code to work around even older versions of Tor that
15937 used forked processes to handle DNS requests. Such versions of Tor
15938 are no longer in use as servers.
15940 o Documentation fixes:
15941 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
15942 - Add missing documentation for the authority-related torrc options
15943 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
15947 Changes in version 0.2.2.25-alpha - 2011-04-29
15948 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
15949 robust, routers no longer overreport their bandwidth, Win7 should crash
15950 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
15951 now prevents hidden service-related activity from being linkable. It
15952 provides more information to Vidalia so you can see if your bridge is
15953 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
15954 StrictNodes configuration options to make them more reliable, more
15955 understandable, and more regularly applied. If you use those options,
15956 please see the revised documentation for them in the manual page.
15959 - Relays were publishing grossly inflated bandwidth values because
15960 they were writing their state files wrong--now they write the
15961 correct value. Also, resume reading bandwidth history from the
15962 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
15963 - Improve hidden service robustness: When we find that we have
15964 extended a hidden service's introduction circuit to a relay not
15965 listed as an introduction point in the HS descriptor we currently
15966 have, retry with an introduction point from the current
15967 descriptor. Previously we would just give up. Fixes bugs 1024 and
15968 1930; bugfix on 0.2.0.10-alpha.
15969 - Clients now stop trying to use an exit node associated with a given
15970 destination by TrackHostExits if they fail to reach that exit node.
15971 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
15972 - Fix crash bug on platforms where gmtime and localtime can return
15973 NULL. Windows 7 users were running into this one. Fixes part of bug
15974 2077. Bugfix on all versions of Tor. Found by boboper.
15976 o Security and stability fixes:
15977 - Don't double-free a parsable, but invalid, microdescriptor, even if
15978 it is followed in the blob we're parsing by an unparsable
15979 microdescriptor. Fixes an issue reported in a comment on bug 2954.
15980 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
15981 - If the Nickname configuration option isn't given, Tor would pick a
15982 nickname based on the local hostname as the nickname for a relay.
15983 Because nicknames are not very important in today's Tor and the
15984 "Unnamed" nickname has been implemented, this is now problematic
15985 behavior: It leaks information about the hostname without being
15986 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
15987 introduced the Unnamed nickname. Reported by tagnaq.
15988 - Fix an uncommon assertion failure when running with DNSPort under
15989 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
15990 - Avoid linkability based on cached hidden service descriptors: forget
15991 all hidden service descriptors cached as a client when processing a
15992 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
15995 - Export GeoIP information on bridge usage to controllers even if we
15996 have not yet been running for 24 hours. Now Vidalia bridge operators
15997 can get more accurate and immediate feedback about their
15998 contributions to the network.
16000 o Major features and bugfixes (node selection):
16001 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
16002 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
16003 options. Previously, we had been ambiguous in describing what
16004 counted as an "exit" node, and what operations exactly "StrictNodes
16005 0" would permit. This created confusion when people saw nodes built
16006 through unexpected circuits, and made it hard to tell real bugs from
16007 surprises. Now the intended behavior is:
16008 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
16009 a node that delivers user traffic outside the Tor network.
16010 . "Entry", in the context of EntryNodes, means a node used as the
16011 first hop of a multihop circuit. It doesn't include direct
16012 connections to directory servers.
16013 . "ExcludeNodes" applies to all nodes.
16014 . "StrictNodes" changes the behavior of ExcludeNodes only. When
16015 StrictNodes is set, Tor should avoid all nodes listed in
16016 ExcludeNodes, even when it will make user requests fail. When
16017 StrictNodes is *not* set, then Tor should follow ExcludeNodes
16018 whenever it can, except when it must use an excluded node to
16019 perform self-tests, connect to a hidden service, provide a
16020 hidden service, fulfill a .exit request, upload directory
16021 information, or fetch directory information.
16022 Collectively, the changes to implement the behavior fix bug 1090.
16023 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
16024 a node is listed in both, it's treated as excluded.
16025 - ExcludeNodes now applies to directory nodes -- as a preference if
16026 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
16027 Don't exclude all the directory authorities and set StrictNodes to 1
16028 unless you really want your Tor to break.
16029 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
16030 - ExcludeExitNodes now overrides .exit requests.
16031 - We don't use bridges listed in ExcludeNodes.
16032 - When StrictNodes is 1:
16033 . We now apply ExcludeNodes to hidden service introduction points
16034 and to rendezvous points selected by hidden service users. This
16035 can make your hidden service less reliable: use it with caution!
16036 . If we have used ExcludeNodes on ourself, do not try relay
16037 reachability self-tests.
16038 . If we have excluded all the directory authorities, we will not
16039 even try to upload our descriptor if we're a relay.
16040 . Do not honor .exit requests to an excluded node.
16041 - Remove a misfeature that caused us to ignore the Fast/Stable flags
16042 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
16043 - When the set of permitted nodes changes, we now remove any mappings
16044 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
16046 - We never cannibalize a circuit that had excluded nodes on it, even
16047 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
16048 - Revert a change where we would be laxer about attaching streams to
16049 circuits than when building the circuits. This was meant to prevent
16050 a set of bugs where streams were never attachable, but our improved
16051 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
16052 - Keep track of how many times we launch a new circuit to handle a
16053 given stream. Too many launches could indicate an inconsistency
16054 between our "launch a circuit to handle this stream" logic and our
16055 "attach this stream to one of the available circuits" logic.
16056 - Improve log messages related to excluded nodes.
16059 - Fix a spurious warning when moving from a short month to a long
16060 month on relays with month-based BandwidthAccounting. Bugfix on
16061 0.2.2.17-alpha; fixes bug 3020.
16062 - When a client finds that an origin circuit has run out of 16-bit
16063 stream IDs, we now mark it as unusable for new streams. Previously,
16064 we would try to close the entire circuit. Bugfix on 0.0.6.
16065 - Add a forgotten cast that caused a compile warning on OS X 10.6.
16066 Bugfix on 0.2.2.24-alpha.
16067 - Be more careful about reporting the correct error from a failed
16068 connect() system call. Under some circumstances, it was possible to
16069 look at an incorrect value for errno when sending the end reason.
16070 Bugfix on 0.1.0.1-rc.
16071 - Correctly handle an "impossible" overflow cases in connection byte
16072 counting, where we write or read more than 4GB on an edge connection
16073 in a single second. Bugfix on 0.1.2.8-beta.
16074 - Correct the warning displayed when a rendezvous descriptor exceeds
16075 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
16077 - Clients and hidden services now use HSDir-flagged relays for hidden
16078 service descriptor downloads and uploads even if the relays have no
16079 DirPort set and the client has disabled TunnelDirConns. This will
16080 eventually allow us to give the HSDir flag to relays with no
16081 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
16082 - Downgrade "no current certificates known for authority" message from
16083 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
16084 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
16085 2917. Bugfix on 0.1.1.1-alpha.
16086 - Only limit the lengths of single HS descriptors, even when multiple
16087 HS descriptors are published to an HSDir relay in a single POST
16088 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
16089 - Write the current time into the LastWritten line in our state file,
16090 rather than the time from the previous write attempt. Also, stop
16091 trying to use a time of -1 in our log statements. Fixes bug 3039;
16092 bugfix on 0.2.2.14-alpha.
16093 - Be more consistent in our treatment of file system paths. "~" should
16094 get expanded to the user's home directory in the Log config option.
16095 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
16096 feature for the -f and --DataDirectory options.
16099 - Make sure every relay writes a state file at least every 12 hours.
16100 Previously, a relay could go for weeks without writing its state
16101 file, and on a crash could lose its bandwidth history, capacity
16102 estimates, client country statistics, and so on. Addresses bug 3012.
16103 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
16104 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
16105 clients are already deprecated because of security bugs.
16106 - Don't allow v0 hidden service authorities to act as clients.
16107 Required by fix for bug 3000.
16108 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
16109 by fix for bug 3000.
16110 - Ensure that no empty [dirreq-](read|write)-history lines are added
16111 to an extrainfo document. Implements ticket 2497.
16113 o Code simplification and refactoring:
16114 - Remove workaround code to handle directory responses from servers
16115 that had bug 539 (they would send HTTP status 503 responses _and_
16116 send a body too). Since only server versions before
16117 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
16118 keep the workaround in place.
16119 - Remove the old 'fuzzy time' logic. It was supposed to be used for
16120 handling calculations where we have a known amount of clock skew and
16121 an allowed amount of unknown skew. But we only used it in three
16122 places, and we never adjusted the known/unknown skew values. This is
16123 still something we might want to do someday, but if we do, we'll
16124 want to do it differently.
16125 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
16126 None of the cases where we did this before were wrong, but by making
16127 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
16128 - Use GetTempDir to find the proper temporary directory location on
16129 Windows when generating temporary files for the unit tests. Patch by
16133 Changes in version 0.2.2.24-alpha - 2011-04-08
16134 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
16135 prevented Tor clients from effectively using "multihomed" bridges,
16136 that is, bridges that listen on multiple ports or IP addresses so users
16137 can continue to use some of their addresses even if others get blocked.
16140 - Fix a bug where bridge users who configure the non-canonical
16141 address of a bridge automatically switch to its canonical
16142 address. If a bridge listens at more than one address, it should be
16143 able to advertise those addresses independently and any non-blocked
16144 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
16146 - If you configured Tor to use bridge A, and then quit and
16147 configured Tor to use bridge B instead, it would happily continue
16148 to use bridge A if it's still reachable. While this behavior is
16149 a feature if your goal is connectivity, in some scenarios it's a
16150 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
16151 - Directory authorities now use data collected from their own
16152 uptime observations when choosing whether to assign the HSDir flag
16153 to relays, instead of trusting the uptime value the relay reports in
16154 its descriptor. This change helps prevent an attack where a small
16155 set of nodes with frequently-changing identity keys can blackhole
16156 a hidden service. (Only authorities need upgrade; others will be
16157 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
16160 - When we restart our relay, we might get a successful connection
16161 from the outside before we've started our reachability tests,
16162 triggering a warning: "ORPort found reachable, but I have no
16163 routerinfo yet. Failing to inform controller of success." This
16164 bug was harmless unless Tor is running under a controller
16165 like Vidalia, in which case the controller would never get a
16166 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
16168 - Make directory authorities more accurate at recording when
16169 relays that have failed several reachability tests became
16170 unreachable, so we can provide more accuracy at assigning Stable,
16171 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
16172 - Fix an issue that prevented static linking of libevent on
16173 some platforms (notably Linux). Fixes bug 2698; bugfix on
16174 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
16175 the --with-static-libevent configure option).
16176 - We now ask the other side of a stream (the client or the exit)
16177 for more data on that stream when the amount of queued data on
16178 that stream dips low enough. Previously, we wouldn't ask the
16179 other side for more data until either it sent us more data (which
16180 it wasn't supposed to do if it had exhausted its window!) or we
16181 had completely flushed all our queued data. This flow control fix
16182 should improve throughput. Fixes bug 2756; bugfix on the earliest
16183 released versions of Tor (svn commit r152).
16184 - Avoid a double-mark-for-free warning when failing to attach a
16185 transparent proxy connection. (We thought we had fixed this in
16186 0.2.2.23-alpha, but it turns out our fix was checking the wrong
16187 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
16188 bug) and 0.2.2.23-alpha (the incorrect fix).
16189 - When warning about missing zlib development packages during compile,
16190 give the correct package names. Bugfix on 0.2.0.1-alpha.
16193 - Directory authorities now log the source of a rejected POSTed v3
16194 networkstatus vote.
16195 - Make compilation with clang possible when using
16196 --enable-gcc-warnings by removing two warning options that clang
16197 hasn't implemented yet and by fixing a few warnings. Implements
16199 - When expiring circuits, use microsecond timers rather than
16200 one-second timers. This can avoid an unpleasant situation where a
16201 circuit is launched near the end of one second and expired right
16202 near the beginning of the next, and prevent fluctuations in circuit
16204 - Use computed circuit-build timeouts to decide when to launch
16205 parallel introduction circuits for hidden services. (Previously,
16206 we would retry after 15 seconds.)
16207 - Update to the April 1 2011 Maxmind GeoLite Country database.
16210 - Create the /var/run/tor directory on startup on OpenSUSE if it is
16211 not already created. Patch from Andreas Stieger. Fixes bug 2573.
16213 o Documentation changes:
16214 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
16215 - Resolve all doxygen warnings except those for missing documentation.
16217 - Add doxygen documentation for more functions, fields, and types.
16220 Changes in version 0.2.2.23-alpha - 2011-03-08
16221 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
16222 they restart they don't lose their bandwidth capacity estimate. This
16223 release also fixes a diverse set of user-facing bugs, ranging from
16224 relays overrunning their rate limiting to clients falsely warning about
16225 clock skew to bridge descriptor leaks by our bridge directory authority.
16228 - Stop sending a CLOCK_SKEW controller status event whenever
16229 we fetch directory information from a relay that has a wrong clock.
16230 Instead, only inform the controller when it's a trusted authority
16231 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
16232 the rest of bug 1074.
16233 - Fix an assert in parsing router descriptors containing IPv6
16234 addresses. This one took down the directory authorities when
16235 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
16236 - Make the bridge directory authority refuse to answer directory
16237 requests for "all" descriptors. It used to include bridge
16238 descriptors in its answer, which was a major information leak.
16239 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
16240 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
16241 Tor would ignore their RelayBandwidthBurst setting,
16242 potentially using more bandwidth than expected. Bugfix on
16243 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
16244 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
16245 hidserv" in her torrc. The 'hidserv' argument never controlled
16246 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
16249 - Relays now save observed peak bandwidth throughput rates to their
16250 state file (along with total usage, which was already saved)
16251 so that they can determine their correct estimated bandwidth on
16252 restart. Resolves bug 1863, where Tor relays would reset their
16253 estimated bandwidth to 0 after restarting.
16254 - Directory authorities now take changes in router IP address and
16255 ORPort into account when determining router stability. Previously,
16256 if a router changed its IP or ORPort, the authorities would not
16257 treat it as having any downtime for the purposes of stability
16258 calculation, whereas clients would experience downtime since the
16259 change could take a while to propagate to them. Resolves issue 1035.
16260 - Enable Address Space Layout Randomization (ASLR) and Data Execution
16261 Prevention (DEP) by default on Windows to make it harder for
16262 attackers to exploit vulnerabilities. Patch from John Brooks.
16264 o Minor bugfixes (on 0.2.1.x and earlier):
16265 - Fix a rare crash bug that could occur when a client was configured
16266 with a large number of bridges. Fixes bug 2629; bugfix on
16267 0.2.1.2-alpha. Bugfix by trac user "shitlei".
16268 - Avoid a double mark-for-free warning when failing to attach a
16269 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
16271 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
16272 found by "cypherpunks". This bug was introduced before the first
16273 Tor release, in svn commit r110.
16274 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
16275 don't mention them in the manpage. Fixes bug 2450; issue
16276 spotted by keb and G-Lo.
16277 - Fix a bug in bandwidth history state parsing that could have been
16278 triggered if a future version of Tor ever changed the timing
16279 granularity at which bandwidth history is measured. Bugfix on
16280 Tor 0.1.1.11-alpha.
16281 - When a relay decides that its DNS is too broken for it to serve
16282 as an exit server, it advertised itself as a non-exit, but
16283 continued to act as an exit. This could create accidental
16284 partitioning opportunities for users. Instead, if a relay is
16285 going to advertise reject *:* as its exit policy, it should
16286 really act with exit policy "reject *:*". Fixes bug 2366.
16287 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
16288 - In the special case where you configure a public exit relay as your
16289 bridge, Tor would be willing to use that exit relay as the last
16290 hop in your circuit as well. Now we fail that circuit instead.
16291 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
16292 - Fix a bug with our locking implementation on Windows that couldn't
16293 correctly detect when a file was already locked. Fixes bug 2504,
16294 bugfix on 0.2.1.6-alpha.
16295 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
16296 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
16298 - Set target port in get_interface_address6() correctly. Bugfix
16299 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
16300 - Directory authorities are now more robust to hops back in time
16301 when calculating router stability. Previously, if a run of uptime
16302 or downtime appeared to be negative, the calculation could give
16303 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
16305 - Fix an assert that got triggered when using the TestingTorNetwork
16306 configuration option and then issuing a GETINFO config-text control
16307 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
16309 o Minor bugfixes (on 0.2.2.x):
16310 - Clients should not weight BadExit nodes as Exits in their node
16311 selection. Similarly, directory authorities should not count BadExit
16312 bandwidth as Exit bandwidth when computing bandwidth-weights.
16313 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
16314 - Correctly clear our dir_read/dir_write history when there is an
16315 error parsing any bw history value from the state file. Bugfix on
16316 Tor 0.2.2.15-alpha.
16317 - Resolve a bug in verifying signatures of directory objects
16318 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
16319 Fixes bug 2409. Found by "piebeer".
16320 - Bridge authorities no longer crash on SIGHUP when they try to
16321 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
16325 - Log less aggressively about circuit timeout changes, and improve
16326 some other circuit timeout messages. Resolves bug 2004.
16327 - Log a little more clearly about the times at which we're no longer
16328 accepting new connections. Resolves bug 2181.
16329 - Reject attempts at the client side to open connections to private
16330 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
16331 a randomly chosen exit node. Attempts to do so are always
16332 ill-defined, generally prevented by exit policies, and usually
16333 in error. This will also help to detect loops in transparent
16334 proxy configurations. You can disable this feature by setting
16335 "ClientRejectInternalAddresses 0" in your torrc.
16336 - Always treat failure to allocate an RSA key as an unrecoverable
16338 - Update to the March 1 2011 Maxmind GeoLite Country database.
16340 o Minor features (log subsystem):
16341 - Add documentation for configuring logging at different severities in
16342 different log domains. We've had this feature since 0.2.1.1-alpha,
16343 but for some reason it never made it into the manpage. Fixes
16345 - Make it simpler to specify "All log domains except for A and B".
16346 Previously you needed to say "[*,~A,~B]". Now you can just say
16348 - Add a "LogMessageDomains 1" option to include the domains of log
16349 messages along with the messages. Without this, there's no way
16350 to use log domains without reading the source or doing a lot
16353 o Packaging changes:
16354 - Stop shipping the Tor specs files and development proposal documents
16355 in the tarball. They are now in a separate git repository at
16356 git://git.torproject.org/torspec.git
16359 Changes in version 0.2.1.30 - 2011-02-23
16360 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
16361 change is a slight tweak to Tor's TLS handshake that makes relays
16362 and bridges that run this new version reachable from Iran again.
16363 We don't expect this tweak will win the arms race long-term, but it
16364 buys us time until we roll out a better solution.
16367 - Stop sending a CLOCK_SKEW controller status event whenever
16368 we fetch directory information from a relay that has a wrong clock.
16369 Instead, only inform the controller when it's a trusted authority
16370 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
16371 the rest of bug 1074.
16372 - Fix a bounds-checking error that could allow an attacker to
16373 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
16374 Found by "piebeer".
16375 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
16376 Tor would ignore their RelayBandwidthBurst setting,
16377 potentially using more bandwidth than expected. Bugfix on
16378 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
16379 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
16380 hidserv" in her torrc. The 'hidserv' argument never controlled
16381 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
16384 - Adjust our TLS Diffie-Hellman parameters to match those used by
16386 - Update to the February 1 2011 Maxmind GeoLite Country database.
16389 - Check for and reject overly long directory certificates and
16390 directory tokens before they have a chance to hit any assertions.
16391 Bugfix on 0.2.1.28. Found by "doorss".
16392 - Bring the logic that gathers routerinfos and assesses the
16393 acceptability of circuits into line. This prevents a Tor OP from
16394 getting locked in a cycle of choosing its local OR as an exit for a
16395 path (due to a .exit request) and then rejecting the circuit because
16396 its OR is not listed yet. It also prevents Tor clients from using an
16397 OR running in the same instance as an exit (due to a .exit request)
16398 if the OR does not meet the same requirements expected of an OR
16399 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
16401 o Packaging changes:
16402 - Stop shipping the Tor specs files and development proposal documents
16403 in the tarball. They are now in a separate git repository at
16404 git://git.torproject.org/torspec.git
16405 - Do not include Git version tags as though they are SVN tags when
16406 generating a tarball from inside a repository that has switched
16407 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
16410 Changes in version 0.2.2.22-alpha - 2011-01-25
16411 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
16412 main other change is a slight tweak to Tor's TLS handshake that makes
16413 relays and bridges that run this new version reachable from Iran again.
16414 We don't expect this tweak will win the arms race long-term, but it
16415 will buy us a bit more time until we roll out a better solution.
16418 - Fix a bounds-checking error that could allow an attacker to
16419 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
16420 Found by "piebeer".
16421 - Don't assert when changing from bridge to relay or vice versa
16422 via the controller. The assert happened because we didn't properly
16423 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
16424 bug 2433. Reported by bastik.
16427 - Adjust our TLS Diffie-Hellman parameters to match those used by
16429 - Provide a log message stating which geoip file we're parsing
16430 instead of just stating that we're parsing the geoip file.
16431 Implements ticket 2432.
16434 - Check for and reject overly long directory certificates and
16435 directory tokens before they have a chance to hit any assertions.
16436 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
16439 Changes in version 0.2.2.21-alpha - 2011-01-15
16440 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
16441 continues our recent code security audit work. The main fix resolves
16442 a remote heap overflow vulnerability that can allow remote code
16443 execution (CVE-2011-0427). Other fixes address a variety of assert
16444 and crash bugs, most of which we think are hard to exploit remotely.
16446 o Major bugfixes (security), also included in 0.2.1.29:
16447 - Fix a heap overflow bug where an adversary could cause heap
16448 corruption. This bug probably allows remote code execution
16449 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
16451 - Prevent a denial-of-service attack by disallowing any
16452 zlib-compressed data whose compression factor is implausibly
16453 high. Fixes part of bug 2324; reported by "doorss".
16454 - Zero out a few more keys in memory before freeing them. Fixes
16455 bug 2384 and part of bug 2385. These key instances found by
16456 "cypherpunks", based on Andrew Case's report about being able
16457 to find sensitive data in Tor's memory space if you have enough
16458 permissions. Bugfix on 0.0.2pre9.
16460 o Major bugfixes (crashes), also included in 0.2.1.29:
16461 - Prevent calls to Libevent from inside Libevent log handlers.
16462 This had potential to cause a nasty set of crashes, especially
16463 if running Libevent with debug logging enabled, and running
16464 Tor with a controller watching for low-severity log messages.
16465 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
16466 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
16467 underflow errors there too. Fixes the other part of bug 2324.
16468 - Fix a bug where we would assert if we ever had a
16469 cached-descriptors.new file (or another file read directly into
16470 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
16471 on 0.2.1.25. Found by doorss.
16472 - Fix some potential asserts and parsing issues with grossly
16473 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
16476 o Minor bugfixes (other), also included in 0.2.1.29:
16477 - Fix a bug with handling misformed replies to reverse DNS lookup
16478 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
16479 bug reported by doorss.
16480 - Fix compilation on mingw when a pthreads compatibility library
16481 has been installed. (We don't want to use it, so we shouldn't
16482 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
16483 - Fix a bug where we would declare that we had run out of virtual
16484 addresses when the address space was only half-exhausted. Bugfix
16486 - Correctly handle the case where AutomapHostsOnResolve is set but
16487 no virtual addresses are available. Fixes bug 2328; bugfix on
16488 0.1.2.1-alpha. Bug found by doorss.
16489 - Correctly handle wrapping around when we run out of virtual
16490 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
16492 o Minor features, also included in 0.2.1.29:
16493 - Update to the January 1 2011 Maxmind GeoLite Country database.
16494 - Introduce output size checks on all of our decryption functions.
16496 o Build changes, also included in 0.2.1.29:
16497 - Tor does not build packages correctly with Automake 1.6 and earlier;
16498 added a check to Makefile.am to make sure that we're building with
16499 Automake 1.7 or later.
16500 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
16501 because we built it with a too-old version of automake. Thus that
16502 release broke ./configure --enable-openbsd-malloc, which is popular
16503 among really fast exit relays on Linux.
16505 o Major bugfixes, new in 0.2.2.21-alpha:
16506 - Prevent crash/heap corruption when the cbtnummodes consensus
16507 parameter is set to 0 or large values. Fixes bug 2317; bugfix
16510 o Major features, new in 0.2.2.21-alpha:
16511 - Introduce minimum/maximum values that clients will believe
16512 from the consensus. Now we'll have a better chance to avoid crashes
16513 or worse when a consensus param has a weird value.
16515 o Minor features, new in 0.2.2.21-alpha:
16516 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
16517 used on bridges, and it makes bridge scanning somewhat easier.
16518 - If writing the state file to disk fails, wait up to an hour before
16519 retrying again, rather than trying again each second. Fixes bug
16520 2346; bugfix on Tor 0.1.1.3-alpha.
16521 - Make Libevent log messages get delivered to controllers later,
16522 and not from inside the Libevent log handler. This prevents unsafe
16523 reentrant Libevent calls while still letting the log messages
16525 - Detect platforms that brokenly use a signed size_t, and refuse to
16526 build there. Found and analyzed by doorss and rransom.
16527 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
16530 o Minor bugfixes, new in 0.2.2.21-alpha:
16531 - Handle SOCKS messages longer than 128 bytes long correctly, rather
16532 than waiting forever for them to finish. Fixes bug 2330; bugfix
16533 on 0.2.0.16-alpha. Found by doorss.
16534 - Add assertions to check for overflow in arguments to
16535 base32_encode() and base32_decode(); fix a signed-unsigned
16536 comparison there too. These bugs are not actually reachable in Tor,
16537 but it's good to prevent future errors too. Found by doorss.
16538 - Correctly detect failures to create DNS requests when using Libevent
16539 versions before v2. (Before Libevent 2, we used our own evdns
16540 implementation. Its return values for Libevent's evdns_resolve_*()
16541 functions are not consistent with those from Libevent.) Fixes bug
16542 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
16544 o Documentation, new in 0.2.2.21-alpha:
16545 - Document the default socks host and port (127.0.0.1:9050) for
16549 Changes in version 0.2.1.29 - 2011-01-15
16550 Tor 0.2.1.29 continues our recent code security audit work. The main
16551 fix resolves a remote heap overflow vulnerability that can allow remote
16552 code execution. Other fixes address a variety of assert and crash bugs,
16553 most of which we think are hard to exploit remotely.
16555 o Major bugfixes (security):
16556 - Fix a heap overflow bug where an adversary could cause heap
16557 corruption. This bug probably allows remote code execution
16558 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
16560 - Prevent a denial-of-service attack by disallowing any
16561 zlib-compressed data whose compression factor is implausibly
16562 high. Fixes part of bug 2324; reported by "doorss".
16563 - Zero out a few more keys in memory before freeing them. Fixes
16564 bug 2384 and part of bug 2385. These key instances found by
16565 "cypherpunks", based on Andrew Case's report about being able
16566 to find sensitive data in Tor's memory space if you have enough
16567 permissions. Bugfix on 0.0.2pre9.
16569 o Major bugfixes (crashes):
16570 - Prevent calls to Libevent from inside Libevent log handlers.
16571 This had potential to cause a nasty set of crashes, especially
16572 if running Libevent with debug logging enabled, and running
16573 Tor with a controller watching for low-severity log messages.
16574 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
16575 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
16576 underflow errors there too. Fixes the other part of bug 2324.
16577 - Fix a bug where we would assert if we ever had a
16578 cached-descriptors.new file (or another file read directly into
16579 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
16580 on 0.2.1.25. Found by doorss.
16581 - Fix some potential asserts and parsing issues with grossly
16582 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
16585 o Minor bugfixes (other):
16586 - Fix a bug with handling misformed replies to reverse DNS lookup
16587 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
16588 bug reported by doorss.
16589 - Fix compilation on mingw when a pthreads compatibility library
16590 has been installed. (We don't want to use it, so we shouldn't
16591 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
16592 - Fix a bug where we would declare that we had run out of virtual
16593 addresses when the address space was only half-exhausted. Bugfix
16595 - Correctly handle the case where AutomapHostsOnResolve is set but
16596 no virtual addresses are available. Fixes bug 2328; bugfix on
16597 0.1.2.1-alpha. Bug found by doorss.
16598 - Correctly handle wrapping around to when we run out of virtual
16599 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
16600 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
16601 because we built it with a too-old version of automake. Thus that
16602 release broke ./configure --enable-openbsd-malloc, which is popular
16603 among really fast exit relays on Linux.
16606 - Update to the January 1 2011 Maxmind GeoLite Country database.
16607 - Introduce output size checks on all of our decryption functions.
16610 - Tor does not build packages correctly with Automake 1.6 and earlier;
16611 added a check to Makefile.am to make sure that we're building with
16612 Automake 1.7 or later.
16615 Changes in version 0.2.2.20-alpha - 2010-12-17
16616 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
16617 exploitable bugs. We also fix a variety of other significant bugs,
16618 change the IP address for one of our directory authorities, and update
16619 the minimum version that Tor relays must run to join the network.
16622 - Fix a remotely exploitable bug that could be used to crash instances
16623 of Tor remotely by overflowing on the heap. Remote-code execution
16624 hasn't been confirmed, but can't be ruled out. Everyone should
16625 upgrade. Bugfix on the 0.1.1 series and later.
16626 - Fix a bug that could break accounting on 64-bit systems with large
16627 time_t values, making them hibernate for impossibly long intervals.
16628 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
16629 - Fix a logic error in directory_fetches_from_authorities() that
16630 would cause all _non_-exits refusing single-hop-like circuits
16631 to fetch from authorities, when we wanted to have _exits_ fetch
16632 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
16634 - Fix a stream fairness bug that would cause newer streams on a given
16635 circuit to get preference when reading bytes from the origin or
16636 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
16637 introduced before the first Tor release, in svn revision r152.
16639 o Directory authority changes:
16640 - Change IP address and ports for gabelmoo (v3 directory authority).
16643 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
16644 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
16645 - Fix an off-by-one error in calculating some controller command
16646 argument lengths. Fortunately, this mistake is harmless since
16647 the controller code does redundant NUL termination too. Found by
16648 boboper. Bugfix on 0.1.1.1-alpha.
16649 - Do not dereference NULL if a bridge fails to build its
16650 extra-info descriptor. Found by an anonymous commenter on
16651 Trac. Bugfix on 0.2.2.19-alpha.
16654 - Update to the December 1 2010 Maxmind GeoLite Country database.
16655 - Directory authorities now reject relays running any versions of
16656 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
16657 known bugs that keep RELAY_EARLY cells from working on rendezvous
16658 circuits. Followup to fix for bug 2081.
16659 - Directory authorities now reject relays running any version of Tor
16660 older than 0.2.0.26-rc. That version is the earliest that fetches
16661 current directory information correctly. Fixes bug 2156.
16662 - Report only the top 10 ports in exit-port stats in order not to
16663 exceed the maximum extra-info descriptor length of 50 KB. Implements
16667 Changes in version 0.2.1.28 - 2010-12-17
16668 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
16669 exploitable bugs. We also took this opportunity to change the IP address
16670 for one of our directory authorities, and to update the geoip database
16674 - Fix a remotely exploitable bug that could be used to crash instances
16675 of Tor remotely by overflowing on the heap. Remote-code execution
16676 hasn't been confirmed, but can't be ruled out. Everyone should
16677 upgrade. Bugfix on the 0.1.1 series and later.
16679 o Directory authority changes:
16680 - Change IP address and ports for gabelmoo (v3 directory authority).
16683 - Update to the December 1 2010 Maxmind GeoLite Country database.
16686 Changes in version 0.2.1.27 - 2010-11-23
16687 Yet another OpenSSL security patch broke its compatibility with Tor:
16688 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
16689 also took this opportunity to fix several crash bugs, integrate a new
16690 directory authority, and update the bundled GeoIP database.
16693 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
16694 No longer set the tlsext_host_name extension on server SSL objects;
16695 but continue to set it on client SSL objects. Our goal in setting
16696 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
16697 bugfix on 0.2.1.1-alpha.
16698 - Do not log messages to the controller while shrinking buffer
16699 freelists. Doing so would sometimes make the controller connection
16700 try to allocate a buffer chunk, which would mess up the internals
16701 of the freelist and cause an assertion failure. Fixes bug 1125;
16702 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
16703 - Learn our external IP address when we're a relay or bridge, even if
16704 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
16705 where we introduced bridge relays that don't need to publish to
16706 be useful. Fixes bug 2050.
16707 - Do even more to reject (and not just ignore) annotations on
16708 router descriptors received anywhere but from the cache. Previously
16709 we would ignore such annotations at first, but cache them to disk
16710 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
16711 - When you're using bridges and your network goes away and your
16712 bridges get marked as down, recover when you attempt a new socks
16713 connection (if the network is back), rather than waiting up to an
16714 hour to try fetching new descriptors for your bridges. Bugfix on
16715 0.2.0.3-alpha; fixes bug 1981.
16718 - Move to the November 2010 Maxmind GeoLite country db (rather
16719 than the June 2009 ip-to-country GeoIP db) for our statistics that
16720 count how many users relays are seeing from each country. Now we'll
16721 have more accurate data, especially for many African countries.
16723 o New directory authorities:
16724 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
16728 - Fix an assertion failure that could occur in directory caches or
16729 bridge users when using a very short voting interval on a testing
16730 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
16732 - Enforce multiplicity rules when parsing annotations. Bugfix on
16733 0.2.0.8-alpha. Found by piebeer.
16734 - Allow handshaking OR connections to take a full KeepalivePeriod
16735 seconds to handshake. Previously, we would close them after
16736 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
16737 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
16739 - When building with --enable-gcc-warnings on OpenBSD, disable
16740 warnings in system headers. This makes --enable-gcc-warnings
16741 pass on OpenBSD 4.8.
16744 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
16745 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
16746 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
16747 Servers can start sending this code when enough clients recognize
16748 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
16749 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
16750 Patch from mingw-san.
16753 - Remove the old debian/ directory from the main Tor distribution.
16754 The official Tor-for-debian git repository lives at the URL
16755 https://git.torproject.org/debian/tor.git
16756 - Stop shipping the old doc/website/ directory in the tarball. We
16757 changed the website format in late 2010, and what we shipped in
16758 0.2.1.26 really wasn't that useful anyway.
16761 Changes in version 0.2.2.19-alpha - 2010-11-22
16762 Yet another OpenSSL security patch broke its compatibility with Tor:
16763 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
16766 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
16767 No longer set the tlsext_host_name extension on server SSL objects;
16768 but continue to set it on client SSL objects. Our goal in setting
16769 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
16770 bugfix on 0.2.1.1-alpha.
16773 - Try harder not to exceed the maximum length of 50 KB when writing
16774 statistics to extra-info descriptors. This bug was triggered by very
16775 fast relays reporting exit-port, entry, and dirreq statistics.
16776 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
16777 - Publish a router descriptor even if generating an extra-info
16778 descriptor fails. Previously we would not publish a router
16779 descriptor without an extra-info descriptor; this can cause fast
16780 exit relays collecting exit-port statistics to drop from the
16781 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
16784 Changes in version 0.2.2.18-alpha - 2010-11-16
16785 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
16786 us lately, makes unpublished bridge relays able to detect their IP
16787 address, and fixes a wide variety of other bugs to get us much closer
16788 to a stable release.
16791 - Do even more to reject (and not just ignore) annotations on
16792 router descriptors received anywhere but from the cache. Previously
16793 we would ignore such annotations at first, but cache them to disk
16794 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
16795 - Do not log messages to the controller while shrinking buffer
16796 freelists. Doing so would sometimes make the controller connection
16797 try to allocate a buffer chunk, which would mess up the internals
16798 of the freelist and cause an assertion failure. Fixes bug 1125;
16799 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
16800 - Learn our external IP address when we're a relay or bridge, even if
16801 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
16802 where we introduced bridge relays that don't need to publish to
16803 be useful. Fixes bug 2050.
16804 - Maintain separate TLS contexts and certificates for incoming and
16805 outgoing connections in bridge relays. Previously we would use the
16806 same TLS contexts and certs for incoming and outgoing connections.
16807 Bugfix on 0.2.0.3-alpha; addresses bug 988.
16808 - Maintain separate identity keys for incoming and outgoing TLS
16809 contexts in bridge relays. Previously we would use the same
16810 identity keys for incoming and outgoing TLS contexts. Bugfix on
16811 0.2.0.3-alpha; addresses the other half of bug 988.
16812 - Avoid an assertion failure when we as an authority receive a
16813 duplicate upload of a router descriptor that we already have,
16814 but which we previously considered an obsolete descriptor.
16815 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
16816 - Avoid a crash bug triggered by looking at a dangling pointer while
16817 setting the network status consensus. Found by Robert Ransom.
16818 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
16819 - Fix a logic error where servers that _didn't_ act as exits would
16820 try to keep their server lists more aggressively up to date than
16821 exits, when it was supposed to be the other way around. Bugfix
16824 o Minor bugfixes (on Tor 0.2.1.x and earlier):
16825 - When we're trying to guess whether we know our IP address as
16826 a relay, we would log various ways that we failed to guess
16827 our address, but never log that we ended up guessing it
16828 successfully. Now add a log line to help confused and anxious
16829 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
16830 - Bring the logic that gathers routerinfos and assesses the
16831 acceptability of circuits into line. This prevents a Tor OP from
16832 getting locked in a cycle of choosing its local OR as an exit for a
16833 path (due to a .exit request) and then rejecting the circuit because
16834 its OR is not listed yet. It also prevents Tor clients from using an
16835 OR running in the same instance as an exit (due to a .exit request)
16836 if the OR does not meet the same requirements expected of an OR
16837 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
16838 - Correctly describe errors that occur when generating a TLS object.
16839 Previously we would attribute them to a failure while generating a
16840 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
16842 - Enforce multiplicity rules when parsing annotations. Bugfix on
16843 0.2.0.8-alpha. Found by piebeer.
16844 - Fix warnings that newer versions of autoconf produced during
16845 ./autogen.sh. These warnings appear to be harmless in our case,
16846 but they were extremely verbose. Fixes bug 2020.
16848 o Minor bugfixes (on Tor 0.2.2.x):
16849 - Enable protection of small arrays whenever we build with gcc
16850 hardening features, not only when also building with warnings
16851 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
16854 - Make hidden services work better in private Tor networks by not
16855 requiring any uptime to join the hidden service descriptor
16856 DHT. Implements ticket 2088.
16857 - Rate-limit the "your application is giving Tor only an IP address"
16858 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
16859 - When AllowSingleHopExits is set, print a warning to explain to the
16860 relay operator why most clients are avoiding her relay.
16861 - Update to the November 1 2010 Maxmind GeoLite Country database.
16863 o Code simplifications and refactoring:
16864 - When we fixed bug 1038 we had to put in a restriction not to send
16865 RELAY_EARLY cells on rend circuits. This was necessary as long
16866 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
16867 active. Now remove this obsolete check. Resolves bug 2081.
16868 - Some options used different conventions for uppercasing of acronyms
16869 when comparing manpage and source. Fix those in favor of the
16870 manpage, as it makes sense to capitalize acronyms.
16871 - Remove the torrc.complete file. It hasn't been kept up to date
16872 and users will have better luck checking out the manpage.
16873 - Remove the obsolete "NoPublish" option; it has been flagged
16874 as obsolete and has produced a warning since 0.1.1.18-rc.
16875 - Remove everything related to building the expert bundle for OS X.
16876 It has confused many users, doesn't work right on OS X 10.6,
16877 and is hard to get rid of once installed. Resolves bug 1274.
16880 Changes in version 0.2.2.17-alpha - 2010-09-30
16881 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
16882 to use one-hop circuits (which can put the exit relays at higher risk,
16883 plus unbalance the network); fixes a big bug in bandwidth accounting
16884 for relays that want to limit their monthly bandwidth use; fixes a
16885 big pile of bugs in how clients tolerate temporary network failure;
16886 and makes our adaptive circuit build timeout feature (which improves
16887 client performance if your network is fast while not breaking things
16888 if your network is slow) better handle bad networks.
16891 - Exit relays now try harder to block exit attempts from unknown
16892 relays, to make it harder for people to use them as one-hop proxies
16893 a la tortunnel. Controlled by the refuseunknownexits consensus
16894 parameter (currently enabled), or you can override it on your
16895 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
16897 o Major bugfixes (0.2.1.x and earlier):
16898 - Fix a bug in bandwidth accounting that could make us use twice
16899 the intended bandwidth when our interval start changes due to
16900 daylight saving time. Now we tolerate skew in stored vs computed
16901 interval starts: if the start of the period changes by no more than
16902 50% of the period's duration, we remember bytes that we transferred
16903 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
16904 - Always search the Windows system directory for system DLLs, and
16905 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
16906 - When you're using bridges and your network goes away and your
16907 bridges get marked as down, recover when you attempt a new socks
16908 connection (if the network is back), rather than waiting up to an
16909 hour to try fetching new descriptors for your bridges. Bugfix on
16910 0.2.0.3-alpha; fixes bug 1981.
16912 o Major bugfixes (on 0.2.2.x):
16913 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
16915 - Fix a segfault that could happen when operating a bridge relay with
16916 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
16917 - The consensus bandwidth-weights (used by clients to choose fast
16918 relays) entered an unexpected edge case in September where
16919 Exits were much scarcer than Guards, resulting in bad weight
16920 recommendations. Now we compute them using new constraints that
16921 should succeed in all cases. Also alter directory authorities to
16922 not include the bandwidth-weights line if they fail to produce
16923 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
16924 - When weighting bridges during path selection, we used to trust
16925 the bandwidths they provided in their descriptor, only capping them
16926 at 10MB/s. This turned out to be problematic for two reasons:
16927 Bridges could claim to handle a lot more traffic then they
16928 actually would, thus making more clients pick them and have a
16929 pretty effective DoS attack. The other issue is that new bridges
16930 that might not have a good estimate for their bw capacity yet
16931 would not get used at all unless no other bridges are available
16932 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
16934 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
16935 - Ignore cannibalized circuits when recording circuit build times.
16936 This should provide for a minor performance improvement for hidden
16937 service users using 0.2.2.14-alpha, and should remove two spurious
16938 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
16939 - Simplify the logic that causes us to decide if the network is
16940 unavailable for purposes of recording circuit build times. If we
16941 receive no cells whatsoever for the entire duration of a circuit's
16942 full measured lifetime, the network is probably down. Also ignore
16943 one-hop directory fetching circuit timeouts when calculating our
16944 circuit build times. These changes should hopefully reduce the
16945 cases where we see ridiculous circuit build timeouts for people
16946 with spotty wireless connections. Fixes part of bug 1772; bugfix
16948 - Prevent the circuit build timeout from becoming larger than
16949 the maximum build time we have ever seen. Also, prevent the time
16950 period for measurement circuits from becoming larger than twice that
16951 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
16954 - When we run out of directory information such that we can't build
16955 circuits, but then get enough that we can build circuits, log when
16956 we actually construct a circuit, so the user has a better chance of
16957 knowing what's going on. Fixes bug 1362.
16958 - Be more generous with how much bandwidth we'd use up (with
16959 accounting enabled) before entering "soft hibernation". Previously,
16960 we'd refuse new connections and circuits once we'd used up 95% of
16961 our allotment. Now, we use up 95% of our allotment, AND make sure
16962 that we have no more than 500MB (or 3 hours of expected traffic,
16963 whichever is lower) remaining before we enter soft hibernation.
16964 - If we've configured EntryNodes and our network goes away and/or all
16965 our entrynodes get marked down, optimistically retry them all when
16966 a new socks application request appears. Fixes bug 1882.
16967 - Add some more defensive programming for architectures that can't
16968 handle unaligned integer accesses. We don't know of any actual bugs
16969 right now, but that's the best time to fix them. Fixes bug 1943.
16970 - Support line continuations in the torrc config file. If a line
16971 ends with a single backslash character, the newline is ignored, and
16972 the configuration value is treated as continuing on the next line.
16975 o Minor bugfixes (on 0.2.1.x and earlier):
16976 - For bandwidth accounting, calculate our expected bandwidth rate
16977 based on the time during which we were active and not in
16978 soft-hibernation during the last interval. Previously, we were
16979 also considering the time spent in soft-hibernation. If this
16980 was a long time, we would wind up underestimating our bandwidth
16981 by a lot, and skewing our wakeup time towards the start of the
16982 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
16984 o Minor bugfixes (on 0.2.2.x):
16985 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
16986 which were disabled by the circuit build timeout changes in
16987 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
16988 - Make sure we don't warn about missing bandwidth weights when
16989 choosing bridges or other relays not in the consensus. Bugfix on
16990 0.2.2.10-alpha; fixes bug 1805.
16991 - In our logs, do not double-report signatures from unrecognized
16992 authorities both as "from unknown authority" and "not
16993 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
16996 Changes in version 0.2.2.16-alpha - 2010-09-17
16997 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
16998 evident at exit relays), and also continues to resolve all the little
16999 bugs that have been filling up trac lately.
17001 o Major bugfixes (stream-level fairness):
17002 - When receiving a circuit-level SENDME for a blocked circuit, try
17003 to package cells fairly from all the streams that had previously
17004 been blocked on that circuit. Previously, we had started with the
17005 oldest stream, and allowed each stream to potentially exhaust
17006 the circuit's package window. This gave older streams on any
17007 given circuit priority over newer ones. Fixes bug 1937. Detected
17008 originally by Camilo Viecco. This bug was introduced before the
17009 first Tor release, in svn commit r152: it is the new winner of
17010 the longest-lived bug prize.
17011 - When the exit relay got a circuit-level sendme cell, it started
17012 reading on the exit streams, even if had 500 cells queued in the
17013 circuit queue already, so the circuit queue just grew and grew in
17014 some cases. We fix this by not re-enabling reading on receipt of a
17015 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
17016 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
17018 - Newly created streams were allowed to read cells onto circuits,
17019 even if the circuit's cell queue was blocked and waiting to drain.
17020 This created potential unfairness, as older streams would be
17021 blocked, but newer streams would gladly fill the queue completely.
17022 We add code to detect this situation and prevent any stream from
17023 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
17027 - Update to the September 1 2010 Maxmind GeoLite Country database.
17028 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
17029 not. This would lead to a cookie that is still not group readable.
17030 Closes bug 1843. Suggested by katmagic.
17031 - When logging a rate-limited warning, we now mention how many messages
17032 got suppressed since the last warning.
17033 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
17034 do individual connection-level rate limiting of clients. The torrc
17035 config options with the same names trump the consensus params, if
17036 both are present. Replaces the old "bwconnrate" and "bwconnburst"
17037 consensus params which were broken from 0.2.2.7-alpha through
17038 0.2.2.14-alpha. Closes bug 1947.
17039 - When a router changes IP address or port, authorities now launch
17040 a new reachability test for it. Implements ticket 1899.
17041 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
17042 2 no signature, 4 required" messages about consensus signatures
17043 easier to read, and make sure they get logged at the same severity
17044 as the messages explaining which keys are which. Fixes bug 1290.
17045 - Don't warn when we have a consensus that we can't verify because
17046 of missing certificates, unless those certificates are ones
17047 that we have been trying and failing to download. Fixes bug 1145.
17048 - If you configure your bridge with a known identity fingerprint,
17049 and the bridge authority is unreachable (as it is in at least
17050 one country now), fall back to directly requesting the descriptor
17051 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
17053 - When building with --enable-gcc-warnings on OpenBSD, disable
17054 warnings in system headers. This makes --enable-gcc-warnings
17055 pass on OpenBSD 4.8.
17057 o Minor bugfixes (on 0.2.1.x and earlier):
17058 - Authorities will now attempt to download consensuses if their
17059 own efforts to make a live consensus have failed. This change
17060 means authorities that restart will fetch a valid consensus, and
17061 it means authorities that didn't agree with the current consensus
17062 will still fetch and serve it if it has enough signatures. Bugfix
17063 on 0.2.0.9-alpha; fixes bug 1300.
17064 - Ensure DNS requests launched by "RESOLVE" commands from the
17065 controller respect the __LeaveStreamsUnattached setconf options. The
17066 same goes for requests launched via DNSPort or transparent
17067 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
17068 - Allow handshaking OR connections to take a full KeepalivePeriod
17069 seconds to handshake. Previously, we would close them after
17070 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
17071 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
17073 - Rate-limit "Failed to hand off onionskin" warnings.
17074 - Never relay a cell for a circuit we have already destroyed.
17075 Between marking a circuit as closeable and finally closing it,
17076 it may have been possible for a few queued cells to get relayed,
17077 even though they would have been immediately dropped by the next
17078 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
17079 - Never queue a cell for a circuit that's already been marked
17081 - Never vote for a server as "Running" if we have a descriptor for
17082 it claiming to be hibernating, and that descriptor was published
17083 more recently than our last contact with the server. Bugfix on
17084 0.2.0.3-alpha; fixes bug 911.
17085 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
17088 o Minor bugfixes (on 0.2.2.x):
17089 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
17090 down if a directory fetch fails and you've configured either
17091 bridges or EntryNodes. The intent was to mark the relay as down
17092 _unless_ you're using bridges or EntryNodes, since if you are
17093 then you could quickly run out of entry points.
17094 - Fix the Windows directory-listing code. A bug introduced in
17095 0.2.2.14-alpha could make Windows directory servers forget to load
17096 some of their cached v2 networkstatus files.
17097 - Really allow clients to use relays as bridges. Fixes bug 1776;
17098 bugfix on 0.2.2.15-alpha.
17099 - Demote a warn to info that happens when the CellStatistics option
17100 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
17101 Reported by Moritz Bartl.
17102 - On Windows, build correctly either with or without Unicode support.
17103 This is necessary so that Tor can support fringe platforms like
17104 Windows 98 (which has no Unicode), or Windows CE (which has no
17105 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
17108 - Add a unit test for cross-platform directory-listing code.
17111 Changes in version 0.2.2.15-alpha - 2010-08-18
17112 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
17113 fixes a variety of other bugs that were preventing performance
17114 experiments from moving forward, fixes several bothersome memory leaks,
17115 and generally closes a lot of smaller bugs that have been filling up
17119 - Stop assigning the HSDir flag to relays that disable their
17120 DirPort (and thus will refuse to answer directory requests). This
17121 fix should dramatically improve the reachability of hidden services:
17122 hidden services and hidden service clients pick six HSDir relays
17123 to store and retrieve the hidden service descriptor, and currently
17124 about half of the HSDir relays will refuse to work. Bugfix on
17125 0.2.0.10-alpha; fixes part of bug 1693.
17126 - The PerConnBWRate and Burst config options, along with the
17127 bwconnrate and bwconnburst consensus params, initialized each conn's
17128 token bucket values only when the connection is established. Now we
17129 update them if the config options change, and update them every time
17130 we get a new consensus. Otherwise we can encounter an ugly edge
17131 case where we initialize an OR conn to client-level bandwidth,
17132 but then later the relay joins the consensus and we leave it
17133 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
17134 - Fix a regression that caused Tor to rebind its ports if it receives
17135 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
17138 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
17139 should give us approximately 40-50% more Guard-flagged nodes,
17140 improving the anonymity the Tor network can provide and also
17141 decreasing the dropoff in throughput that relays experience when
17142 they first get the Guard flag.
17143 - Allow enabling or disabling the *Statistics config options while
17147 - Update to the August 1 2010 Maxmind GeoLite Country database.
17148 - Have the controller interface give a more useful message than
17149 "Internal Error" in response to failed GETINFO requests.
17150 - Warn when the same option is provided more than once in a torrc
17151 file, on the command line, or in a single SETCONF statement, and
17152 the option is one that only accepts a single line. Closes bug 1384.
17153 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
17154 Patch from mingw-san.
17155 - Add support for the country code "{??}" in torrc options like
17156 ExcludeNodes, to indicate all routers of unknown country. Closes
17158 - Relays report the number of bytes spent on answering directory
17159 requests in extra-info descriptors similar to {read,write}-history.
17160 Implements enhancement 1790.
17162 o Minor bugfixes (on 0.2.1.x and earlier):
17163 - Complain if PublishServerDescriptor is given multiple arguments that
17164 include 0 or 1. This configuration will be rejected in the future.
17165 Bugfix on 0.2.0.1-alpha; closes bug 1107.
17166 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
17167 Bugfix on 0.2.0.13-alpha; closes bug 928.
17168 - Change "Application request when we're believed to be offline."
17169 notice to "Application request when we haven't used client
17170 functionality lately.", to clarify that it's not an error. Bugfix
17171 on 0.0.9.3; fixes bug 1222.
17172 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
17173 would return "551 Internal error" rather than "552 Unrecognized key
17174 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
17175 - Users can't configure a regular relay to be their bridge. It didn't
17176 work because when Tor fetched the bridge descriptor, it found
17177 that it already had it, and didn't realize that the purpose of the
17178 descriptor had changed. Now we replace routers with a purpose other
17179 than bridge with bridge descriptors when fetching them. Bugfix on
17180 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
17181 refetch the descriptor with router purpose 'general', disabling
17183 - Fix a rare bug in rend_fn unit tests: we would fail a test when
17184 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
17185 on 0.2.0.10-alpha; fixes bug 1808.
17186 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
17187 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
17188 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
17189 Servers can start sending this code when enough clients recognize
17190 it. Also update the spec to reflect this new reason. Bugfix on
17191 0.1.0.1-rc; fixes part of bug 1793.
17192 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
17193 when we switch from being a public relay to a bridge. Otherwise
17194 there will still be clients that see the relay in their consensus,
17195 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
17197 - Instead of giving an assertion failure on an internal mismatch
17198 on estimated freelist size, just log a BUG warning and try later.
17199 Mitigates but does not fix bug 1125.
17200 - Fix an assertion failure that could occur in caches or bridge users
17201 when using a very short voting interval on a testing network.
17202 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
17204 o Minor bugfixes (on 0.2.2.x):
17205 - Alter directory authorities to always consider Exit-flagged nodes
17206 as potential Guard nodes in their votes. The actual decision to
17207 use Exits as Guards is done in the consensus bandwidth weights.
17208 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
17209 - When the controller is reporting the purpose of circuits that
17210 didn't finish building before the circuit build timeout, it was
17211 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
17212 - Our libevent version parsing code couldn't handle versions like
17213 1.4.14b-stable and incorrectly warned the user about using an
17214 old and broken version of libevent. Treat 1.4.14b-stable like
17215 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
17217 - Don't use substitution references like $(VAR:MOD) when
17218 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
17219 '$(:x)' to 'x' rather than the empty string. This bites us in
17220 doc/ when configured with --disable-asciidoc. Bugfix on
17221 0.2.2.9-alpha; fixes bug 1773.
17222 - Remove a spurious hidden service server-side log notice about
17223 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
17225 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
17227 - Correctly report written bytes on linked connections. Found while
17228 implementing 1790. Bugfix on 0.2.2.4-alpha.
17229 - Fix three memory leaks: one in circuit_build_times_parse_state(),
17230 one in dirvote_add_signatures_to_pending_consensus(), and one every
17231 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
17232 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
17234 o Code simplifications and refactoring:
17235 - Take a first step towards making or.h smaller by splitting out
17236 function definitions for all source files in src/or/. Leave
17237 structures and defines in or.h for now.
17238 - Remove a bunch of unused function declarations as well as a block of
17239 #if 0'd code from the unit tests. Closes bug 1824.
17240 - New unit tests for exit-port history statistics; refactored exit
17241 statistics code to be more easily tested.
17242 - Remove the old debian/ directory from the main Tor distribution.
17243 The official Tor-for-debian git repository lives at the URL
17244 https://git.torproject.org/debian/tor.git
17247 Changes in version 0.2.2.14-alpha - 2010-07-12
17248 Tor 0.2.2.14-alpha greatly improves client-side handling of
17249 circuit build timeouts, which are used to estimate speed and improve
17250 performance. We also move to a much better GeoIP database, port Tor to
17251 Windows CE, introduce new compile flags that improve code security,
17252 add an eighth v3 directory authority, and address a lot of more
17256 - Tor directory authorities no longer crash when started with a
17257 cached-microdesc-consensus file in their data directory. Bugfix
17258 on 0.2.2.6-alpha; fixes bug 1532.
17259 - Treat an unset $HOME like an empty $HOME rather than triggering an
17260 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
17261 - Ignore negative and large circuit build timeout values that can
17262 happen during a suspend or hibernate. These values caused various
17263 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
17264 - Alter calculation of Pareto distribution parameter 'Xm' for
17265 Circuit Build Timeout learning to use the weighted average of the
17266 top N=3 modes (because we have three entry guards). Considering
17267 multiple modes should improve the timeout calculation in some cases,
17268 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
17270 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
17271 right censored distribution model. This approach improves over the
17272 synthetic timeout generation approach that was producing insanely
17273 high timeout values. Now we calculate build timeouts using truncated
17274 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
17275 - Do not close circuits that are under construction when they reach
17276 the circuit build timeout. Instead, leave them building (but do not
17277 use them) for up until the time corresponding to the 95th percentile
17278 on the Pareto CDF or 60 seconds, whichever is greater. This is done
17279 to provide better data for the new Pareto model. This percentile
17280 can be controlled by the consensus.
17283 - Move to the June 2010 Maxmind GeoLite country db (rather than the
17284 June 2009 ip-to-country GeoIP db) for our statistics that count
17285 how many users relays are seeing from each country. Now we have
17286 more accurate data for many African countries.
17287 - Port Tor to build and run correctly on Windows CE systems, using
17288 the wcecompat library. Contributed by Valerio Lupi.
17289 - New "--enable-gcc-hardening" ./configure flag (off by default)
17290 to turn on gcc compile time hardening options. It ensures
17291 that signed ints have defined behavior (-fwrapv), enables
17292 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
17293 with canaries (-fstack-protector-all), turns on ASLR protection if
17294 supported by the kernel (-fPIE, -pie), and adds additional security
17295 related warnings. Verified to work on Mac OS X and Debian Lenny.
17296 - New "--enable-linker-hardening" ./configure flag (off by default)
17297 to turn on ELF specific hardening features (relro, now). This does
17298 not work with Mac OS X or any other non-ELF binary format.
17300 o New directory authorities:
17301 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
17305 - New config option "WarnUnsafeSocks 0" disables the warning that
17306 occurs whenever Tor receives a socks handshake using a version of
17307 the socks protocol that can only provide an IP address (rather
17308 than a hostname). Setups that do DNS locally over Tor are fine,
17309 and we shouldn't spam the logs in that case.
17310 - Convert the HACKING file to asciidoc, and add a few new sections
17311 to it, explaining how we use Git, how we make changelogs, and
17312 what should go in a patch.
17313 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
17314 event, to give information on the current rate of circuit timeouts
17315 over our stored history.
17316 - Add ability to disable circuit build time learning via consensus
17317 parameter and via a LearnCircuitBuildTimeout config option. Also
17318 automatically disable circuit build time calculation if we are
17319 either a AuthoritativeDirectory, or if we fail to write our state
17320 file. Fixes bug 1296.
17321 - More gracefully handle corrupt state files, removing asserts
17322 in favor of saving a backup and resetting state.
17323 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
17327 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
17329 - When a2x fails, mention that the user could disable manpages instead
17330 of trying to fix their asciidoc installation.
17331 - Where available, use Libevent 2.0's periodic timers so that our
17332 once-per-second cleanup code gets called even more closely to
17333 once per second than it would otherwise. Fixes bug 943.
17334 - If you run a bridge that listens on multiple IP addresses, and
17335 some user configures a bridge address that uses a different IP
17336 address than your bridge writes in its router descriptor, and the
17337 user doesn't specify an identity key, their Tor would discard the
17338 descriptor because "it isn't one of our configured bridges", and
17339 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
17340 Bugfix on 0.2.0.3-alpha.
17341 - If OpenSSL fails to make a duplicate of a private or public key, log
17342 an error message and try to exit cleanly. May help with debugging
17343 if bug 1209 ever remanifests.
17344 - Save a couple bytes in memory allocation every time we escape
17345 certain characters in a string. Patch from Florian Zumbiehl.
17346 - Make it explicit that we don't cannibalize one-hop circuits. This
17347 happens in the wild, but doesn't turn out to be a problem because
17348 we fortunately don't use those circuits. Many thanks to outofwords
17349 for the initial analysis and to swissknife who confirmed that
17350 two-hop circuits are actually created.
17351 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
17352 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
17353 - Eliminate a case where a circuit build time warning was displayed
17354 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
17357 Changes in version 0.2.1.26 - 2010-05-02
17358 Tor 0.2.1.26 addresses the recent connection and memory overload
17359 problems we've been seeing on relays, especially relays with their
17360 DirPort open. If your relay has been crashing, or you turned it off
17361 because it used too many resources, give this release a try.
17363 This release also fixes yet another instance of broken OpenSSL libraries
17364 that was causing some relays to drop out of the consensus.
17367 - Teach relays to defend themselves from connection overload. Relays
17368 now close idle circuits early if it looks like they were intended
17369 for directory fetches. Relays are also more aggressive about closing
17370 TLS connections that have no circuits on them. Such circuits are
17371 unlikely to be re-used, and tens of thousands of them were piling
17372 up at the fast relays, causing the relays to run out of sockets
17373 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
17374 their directory fetches over TLS).
17375 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
17376 that claim to be earlier than 0.9.8m, but which have in reality
17377 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
17378 behavior. Possible fix for some cases of bug 1346.
17379 - Directory mirrors were fetching relay descriptors only from v2
17380 directory authorities, rather than v3 authorities like they should.
17381 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
17382 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
17385 - Finally get rid of the deprecated and now harmful notion of "clique
17386 mode", where directory authorities maintain TLS connections to
17390 - In the util/threads test, no longer free the test_mutex before all
17391 worker threads have finished. Bugfix on 0.2.1.6-alpha.
17392 - The master thread could starve the worker threads quite badly on
17393 certain systems, causing them to run only partially in the allowed
17394 window. This resulted in test failures. Now the master thread sleeps
17395 occasionally for a few microseconds while the two worker-threads
17396 compete for the mutex. Bugfix on 0.2.0.1-alpha.
17399 Changes in version 0.2.2.13-alpha - 2010-04-24
17400 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
17401 problems we've been seeing on relays, especially relays with their
17402 DirPort open. If your relay has been crashing, or you turned it off
17403 because it used too many resources, give this release a try.
17406 - Teach relays to defend themselves from connection overload. Relays
17407 now close idle circuits early if it looks like they were intended
17408 for directory fetches. Relays are also more aggressive about closing
17409 TLS connections that have no circuits on them. Such circuits are
17410 unlikely to be re-used, and tens of thousands of them were piling
17411 up at the fast relays, causing the relays to run out of sockets
17412 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
17413 their directory fetches over TLS).
17416 - Finally get rid of the deprecated and now harmful notion of "clique
17417 mode", where directory authorities maintain TLS connections to
17419 - Directory authorities now do an immediate reachability check as soon
17420 as they hear about a new relay. This change should slightly reduce
17421 the time between setting up a relay and getting listed as running
17422 in the consensus. It should also improve the time between setting
17423 up a bridge and seeing use by bridge users.
17424 - Directory authorities no longer launch a TLS connection to every
17425 relay as they startup. Now that we have 2k+ descriptors cached,
17426 the resulting network hiccup is becoming a burden. Besides,
17427 authorities already avoid voting about Running for the first half
17428 hour of their uptime.
17431 Changes in version 0.2.2.12-alpha - 2010-04-20
17432 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
17433 handle and vote on descriptors. It was causing relays to drop out of
17437 - Many relays have been falling out of the consensus lately because
17438 not enough authorities know about their descriptor for them to get
17439 a majority of votes. When we deprecated the v2 directory protocol,
17440 we got rid of the only way that v3 authorities can hear from each
17441 other about other descriptors. Now authorities examine every v3
17442 vote for new descriptors, and fetch them from that authority. Bugfix
17444 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
17445 and a warning in or.h related to bandwidth_weight_rule_t that
17446 prevented clean compile on OS X. Fixes bug 1363; bugfix on
17448 - Fix a segfault on relays when DirReqStatistics is enabled
17449 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
17453 - Demote a confusing TLS warning that relay operators might get when
17454 someone tries to talk to their OrPort. It is neither the operator's
17455 fault nor can they do anything about it. Fixes bug 1364; bugfix
17459 Changes in version 0.2.2.11-alpha - 2010-04-15
17460 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
17461 libraries that was causing some relays to drop out of the consensus.
17464 - Directory mirrors were fetching relay descriptors only from v2
17465 directory authorities, rather than v3 authorities like they should.
17466 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
17467 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
17468 - Fix a parsing error that made every possible value of
17469 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
17470 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
17471 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
17472 about the option without breaking older ones.
17473 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
17474 that claim to be earlier than 0.9.8m, but which have in reality
17475 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
17476 behavior. Possible fix for some cases of bug 1346.
17479 - Experiment with a more aggressive approach to preventing clients
17480 from making one-hop exit streams. Exit relays who want to try it
17481 out can set "RefuseUnknownExits 1" in their torrc, and then look
17482 for "Attempt by %s to open a stream" log messages. Let us know
17484 - Add support for statically linking zlib by specifying
17485 --enable-static-zlib, to go with our support for statically linking
17486 openssl and libevent. Resolves bug 1358.
17489 - Fix a segfault that happens whenever a Tor client that is using
17490 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
17492 - When we cleaned up the contrib/tor-exit-notice.html file, we left
17493 out the first line. Fixes bug 1295.
17494 - When building the manpage from a tarball, we required asciidoc, but
17495 the asciidoc -> roff/html conversion was already done for the
17496 tarball. Make 'make' complain only when we need asciidoc (either
17497 because we're compiling directly from git, or because we altered
17498 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
17499 - When none of the directory authorities vote on any params, Tor
17500 segfaulted when trying to make the consensus from the votes. We
17501 didn't trigger the bug in practice, because authorities do include
17502 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
17505 - In the util/threads test, no longer free the test_mutex before all
17506 worker threads have finished. Bugfix on 0.2.1.6-alpha.
17507 - The master thread could starve the worker threads quite badly on
17508 certain systems, causing them to run only partially in the allowed
17509 window. This resulted in test failures. Now the master thread sleeps
17510 occasionally for a few microseconds while the two worker-threads
17511 compete for the mutex. Bugfix on 0.2.0.1-alpha.
17514 Changes in version 0.2.2.10-alpha - 2010-03-07
17515 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
17516 could prevent relays from guessing their IP address correctly. It also
17517 starts the groundwork for another client-side performance boost, since
17518 currently we're not making efficient use of relays that have both the
17519 Guard flag and the Exit flag.
17522 - Fix a regression from our patch for bug 1244 that caused relays
17523 to guess their IP address incorrectly if they didn't set Address
17524 in their torrc and/or their address fails to resolve. Bugfix on
17525 0.2.2.9-alpha; fixes bug 1269.
17527 o Major features (performance):
17528 - Directory authorities now compute consensus weightings that instruct
17529 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
17530 and no flag. Clients that use these weightings will distribute
17531 network load more evenly across these different relay types. The
17532 weightings are in the consensus so we can change them globally in
17533 the future. Extra thanks to "outofwords" for finding some nasty
17534 security bugs in the first implementation of this feature.
17536 o Minor features (performance):
17537 - Always perform router selections using weighted relay bandwidth,
17538 even if we don't need a high capacity circuit at the time. Non-fast
17539 circuits now only differ from fast ones in that they can use relays
17540 not marked with the Fast flag. This "feature" could turn out to
17541 be a horrible bug; we should investigate more before it goes into
17545 - Allow disabling building of the manpages. Skipping the manpage
17546 speeds up the build considerably.
17548 o Minor bugfixes (on 0.2.2.x):
17549 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
17550 Bugfix on 0.2.2.9-alpha.
17551 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
17552 config option. Bugfix on 0.2.2.7-alpha.
17553 - Ship the asciidoc-helper file in the tarball, so that people can
17554 build from source if they want to, and touching the .1.txt files
17555 doesn't break the build. Bugfix on 0.2.2.9-alpha.
17557 o Minor bugfixes (on 0.2.1.x or earlier):
17558 - Fix a dereference-then-NULL-check sequence when publishing
17559 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
17561 - Fix another dereference-then-NULL-check sequence. Bugfix on
17562 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
17563 - Make sure we treat potentially not NUL-terminated strings correctly.
17564 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
17566 o Code simplifications and refactoring:
17567 - Fix some urls in the exit notice file and make it XHTML1.1 strict
17568 compliant. Based on a patch from Christian Kujau.
17569 - Don't use sed in asciidoc-helper anymore.
17570 - Make the build process fail if asciidoc cannot be found and
17571 building with asciidoc isn't disabled.
17574 Changes in version 0.2.2.9-alpha - 2010-02-22
17575 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
17576 location of a directory authority, and cleans up a bunch of small bugs.
17578 o Directory authority changes:
17579 - Change IP address for dannenberg (v3 directory authority), and
17580 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
17581 service directory authority) from the list.
17584 - Make Tor work again on the latest OS X: when deciding whether to
17585 use strange flags to turn TLS renegotiation on, detect the OpenSSL
17586 version at run-time, not compile time. We need to do this because
17587 Apple doesn't update its dev-tools headers when it updates its
17588 libraries in a security patch.
17589 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
17590 that could happen on 32-bit platforms with 64-bit time_t. Also fix
17591 a memory leak when requesting a hidden service descriptor we've
17592 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
17594 - Authorities could be tricked into giving out the Exit flag to relays
17595 that didn't allow exiting to any ports. This bug could screw
17596 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
17597 1238. Bug discovered by Martin Kowalczyk.
17598 - When freeing a session key, zero it out completely. We only zeroed
17599 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
17600 patched by ekir. Fixes bug 1254.
17603 - Fix static compilation by listing the openssl libraries in the right
17604 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
17605 - Resume handling .exit hostnames in a special way: originally we
17606 stripped the .exit part and used the requested exit relay. In
17607 0.2.2.1-alpha we stopped treating them in any special way, meaning
17608 if you use a .exit address then Tor will pass it on to the exit
17609 relay. Now we reject the .exit stream outright, since that behavior
17610 might be more expected by the user. Found and diagnosed by Scott
17611 Bennett and Downie on or-talk.
17612 - Don't spam the controller with events when we have no file
17613 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
17614 for log messages was already solved from bug 748.)
17615 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
17617 - Make the DNSPort option work with libevent 2.x. Don't alter the
17618 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
17619 - Emit a GUARD DROPPED controller event for a case we missed.
17620 - Make more fields in the controller protocol case-insensitive, since
17621 control-spec.txt said they were.
17622 - Refactor resolve_my_address() to not use gethostbyname() anymore.
17623 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
17624 - Fix a spec conformance issue: the network-status-version token
17625 must be the first token in a v3 consensus or vote. Discovered by
17626 parakeep. Bugfix on 0.2.0.3-alpha.
17628 o Code simplifications and refactoring:
17629 - Generate our manpage and HTML documentation using Asciidoc. This
17630 change should make it easier to maintain the documentation, and
17631 produce nicer HTML.
17632 - Remove the --enable-iphone option. According to reports from Marco
17633 Bonetti, Tor builds fine without any special tweaking on recent
17634 iPhone SDK versions.
17635 - Removed some unnecessary files from the source distribution. The
17636 AUTHORS file has now been merged into the people page on the
17637 website. The roadmaps and design doc can now be found in the
17638 projects directory in svn.
17639 - Enabled various circuit build timeout constants to be controlled
17640 by consensus parameters. Also set better defaults for these
17641 parameters based on experimentation on broadband and simulated
17642 high latency links.
17645 - The 'EXTENDCIRCUIT' control port command can now be used with
17646 a circ id of 0 and no path. This feature will cause Tor to build
17647 a new 'fast' general purpose circuit using its own path selection
17649 - Added a BUILDTIMEOUT_SET controller event to describe changes
17650 to the circuit build timeout.
17651 - Future-proof the controller protocol a bit by ignoring keyword
17652 arguments we do not recognize.
17653 - Expand homedirs passed to tor-checkkey. This should silence a
17654 coverity complaint about passing a user-supplied string into
17655 open() without checking it.
17658 Changes in version 0.2.1.25 - 2010-03-16
17659 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
17660 prevent relays from guessing their IP address correctly. It also fixes
17661 several minor potential security bugs.
17664 - Fix a regression from our patch for bug 1244 that caused relays
17665 to guess their IP address incorrectly if they didn't set Address
17666 in their torrc and/or their address fails to resolve. Bugfix on
17667 0.2.1.23; fixes bug 1269.
17668 - When freeing a session key, zero it out completely. We only zeroed
17669 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
17670 patched by ekir. Fixes bug 1254.
17673 - Fix a dereference-then-NULL-check sequence when publishing
17674 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
17676 - Fix another dereference-then-NULL-check sequence. Bugfix on
17677 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
17678 - Make sure we treat potentially not NUL-terminated strings correctly.
17679 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
17683 Changes in version 0.2.1.24 - 2010-02-21
17684 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
17688 - Work correctly out-of-the-box with even more vendor-patched versions
17689 of OpenSSL. In particular, make it so Debian and OS X don't need
17690 customized patches to run/build.
17693 Changes in version 0.2.1.23 - 2010-02-13
17694 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
17695 again on the latest OS X, and updates the location of a directory
17698 o Major bugfixes (performance):
17699 - We were selecting our guards uniformly at random, and then weighting
17700 which of our guards we'd use uniformly at random. This imbalance
17701 meant that Tor clients were severely limited on throughput (and
17702 probably latency too) by the first hop in their circuit. Now we
17703 select guards weighted by currently advertised bandwidth. We also
17704 automatically discard guards picked using the old algorithm. Fixes
17705 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17708 - Make Tor work again on the latest OS X: when deciding whether to
17709 use strange flags to turn TLS renegotiation on, detect the OpenSSL
17710 version at run-time, not compile time. We need to do this because
17711 Apple doesn't update its dev-tools headers when it updates its
17712 libraries in a security patch.
17713 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
17714 that could happen on 32-bit platforms with 64-bit time_t. Also fix
17715 a memory leak when requesting a hidden service descriptor we've
17716 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
17719 o Directory authority changes:
17720 - Change IP address for dannenberg (v3 directory authority), and
17721 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
17722 service directory authority) from the list.
17725 - Refactor resolve_my_address() to not use gethostbyname() anymore.
17726 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
17729 - Avoid a mad rush at the beginning of each month when each client
17730 rotates half of its guards. Instead we spread the rotation out
17731 throughout the month, but we still avoid leaving a precise timestamp
17732 in the state file about when we first picked the guard. Improves
17733 over the behavior introduced in 0.1.2.17.
17736 Changes in version 0.2.2.8-alpha - 2010-01-26
17737 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
17738 causing bridge relays to disappear. If you're running a bridge,
17742 - Fix a memory corruption bug on bridges that occured during the
17743 inclusion of stats data in extra-info descriptors. Also fix the
17744 interface for geoip_get_bridge_stats* to prevent similar bugs in
17745 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
17746 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
17749 - Ignore OutboundBindAddress when connecting to localhost.
17750 Connections to localhost need to come _from_ localhost, or else
17751 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
17755 Changes in version 0.2.2.7-alpha - 2010-01-19
17756 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
17757 as laying the groundwork for further relay-side performance fixes. It
17758 also starts cleaning up client behavior with respect to the EntryNodes,
17759 ExitNodes, and StrictNodes config options.
17761 This release also rotates two directory authority keys, due to a
17762 security breach of some of the Torproject servers.
17764 o Directory authority changes:
17765 - Rotate keys (both v3 identity and relay identity) for moria1
17768 o Major features (performance):
17769 - We were selecting our guards uniformly at random, and then weighting
17770 which of our guards we'd use uniformly at random. This imbalance
17771 meant that Tor clients were severely limited on throughput (and
17772 probably latency too) by the first hop in their circuit. Now we
17773 select guards weighted by currently advertised bandwidth. We also
17774 automatically discard guards picked using the old algorithm. Fixes
17775 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17776 - When choosing which cells to relay first, relays can now favor
17777 circuits that have been quiet recently, to provide lower latency
17778 for low-volume circuits. By default, relays enable or disable this
17779 feature based on a setting in the consensus. You can override
17780 this default by using the new "CircuitPriorityHalflife" config
17781 option. Design and code by Ian Goldberg, Can Tang, and Chris
17783 - Add separate per-conn write limiting to go with the per-conn read
17784 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
17785 but never per-conn write limits.
17786 - New consensus params "bwconnrate" and "bwconnburst" to let us
17787 rate-limit client connections as they enter the network. It's
17788 controlled in the consensus so we can turn it on and off for
17789 experiments. It's starting out off. Based on proposal 163.
17791 o Major features (relay selection options):
17792 - Switch to a StrictNodes config option, rather than the previous
17793 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
17794 "StrictExcludeNodes" option.
17795 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
17796 change during a config reload, mark and discard all our origin
17797 circuits. This fix should address edge cases where we change the
17798 config options and but then choose a circuit that we created before
17800 - If EntryNodes or ExitNodes are set, be more willing to use an
17801 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
17803 - Make EntryNodes config option much more aggressive even when
17804 StrictNodes is not set. Before it would prepend your requested
17805 entrynodes to your list of guard nodes, but feel free to use others
17806 after that. Now it chooses only from your EntryNodes if any of
17807 those are available, and only falls back to others if a) they're
17808 all down and b) StrictNodes is not set.
17809 - Now we refresh your entry guards from EntryNodes at each consensus
17810 fetch -- rather than just at startup and then they slowly rot as
17811 the network changes.
17814 - Stop bridge directory authorities from answering dbg-stability.txt
17815 directory queries, which would let people fetch a list of all
17816 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17819 - Log a notice when we get a new control connection. Now it's easier
17820 for security-conscious users to recognize when a local application
17821 is knocking on their controller door. Suggested by bug 1196.
17822 - New config option "CircuitStreamTimeout" to override our internal
17823 timeout schedule for how many seconds until we detach a stream from
17824 a circuit and try a new circuit. If your network is particularly
17825 slow, you might want to set this to a number like 60.
17826 - New controller command "getinfo config-text". It returns the
17827 contents that Tor would write if you send it a SAVECONF command,
17828 so the controller can write the file to disk itself.
17829 - New options for SafeLogging to allow scrubbing only log messages
17830 generated while acting as a relay.
17831 - Ship the bridges spec file in the tarball too.
17832 - Avoid a mad rush at the beginning of each month when each client
17833 rotates half of its guards. Instead we spread the rotation out
17834 throughout the month, but we still avoid leaving a precise timestamp
17835 in the state file about when we first picked the guard. Improves
17836 over the behavior introduced in 0.1.2.17.
17838 o Minor bugfixes (compiling):
17839 - Fix compilation on OS X 10.3, which has a stub mlockall() but
17840 hides it. Bugfix on 0.2.2.6-alpha.
17841 - Fix compilation on Solaris by removing support for the
17842 DisableAllSwap config option. Solaris doesn't have an rlimit for
17843 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
17846 o Minor bugfixes (crashes):
17847 - Do not segfault when writing buffer stats when we haven't observed
17848 a single circuit to report about. Found by Fabian Lanze. Bugfix on
17850 - If we're in the pathological case where there's no exit bandwidth
17851 but there is non-exit bandwidth, or no guard bandwidth but there
17852 is non-guard bandwidth, don't crash during path selection. Bugfix
17854 - Fix an impossible-to-actually-trigger buffer overflow in relay
17855 descriptor generation. Bugfix on 0.1.0.15.
17857 o Minor bugfixes (privacy):
17858 - Fix an instance where a Tor directory mirror might accidentally
17859 log the IP address of a misbehaving Tor client. Bugfix on
17861 - Don't list Windows capabilities in relay descriptors. We never made
17862 use of them, and maybe it's a bad idea to publish them. Bugfix
17865 o Minor bugfixes (other):
17866 - Resolve an edge case in path weighting that could make us misweight
17867 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
17868 - Fix statistics on client numbers by country as seen by bridges that
17869 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
17870 intervals instead of variable 12-to-48-hour intervals.
17871 - After we free an internal connection structure, overwrite it
17872 with a different memory value than we use for overwriting a freed
17873 internal circuit structure. Should help with debugging. Suggested
17875 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
17878 o Removed features:
17879 - Remove the HSAuthorityRecordStats option that version 0 hidden
17880 service authorities could have used to track statistics of overall
17881 hidden service usage.
17884 Changes in version 0.2.1.22 - 2010-01-19
17885 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
17886 authorities -- it would tell you its whole history of bridge descriptors
17887 if you make the right directory request. This stable update also
17888 rotates two of the seven v3 directory authority keys and locations.
17890 o Directory authority changes:
17891 - Rotate keys (both v3 identity and relay identity) for moria1
17895 - Stop bridge directory authorities from answering dbg-stability.txt
17896 directory queries, which would let people fetch a list of all
17897 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17900 Changes in version 0.2.1.21 - 2009-12-21
17901 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
17902 library. If you use Tor on Linux / Unix and you're getting SSL
17903 renegotiation errors, upgrading should help. We also recommend an
17904 upgrade if you're an exit relay.
17907 - Work around a security feature in OpenSSL 0.9.8l that prevents our
17908 handshake from working unless we explicitly tell OpenSSL that we
17909 are using SSL renegotiation safely. We are, of course, but OpenSSL
17910 0.9.8l won't work unless we say we are.
17911 - Avoid crashing if the client is trying to upload many bytes and the
17912 circuit gets torn down at the same time, or if the flip side
17913 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
17916 - Do not refuse to learn about authority certs and v2 networkstatus
17917 documents that are older than the latest consensus. This bug might
17918 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
17919 Spotted and fixed by xmux.
17920 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
17921 trigger platform-specific option misparsing case found by Coverity
17923 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
17924 trigger assert. Fixes bug 1173.
17927 Changes in version 0.2.2.6-alpha - 2009-11-19
17928 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
17929 support for the new lower-footprint "microdescriptor" directory design,
17930 future-proofing our consensus format against new hash functions or
17931 other changes, and an Android port. It also makes Tor compatible with
17932 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
17935 - Directory authorities can now create, vote on, and serve multiple
17936 parallel formats of directory data as part of their voting process.
17937 Partially implements Proposal 162: "Publish the consensus in
17939 - Directory authorities can now agree on and publish small summaries
17940 of router information that clients can use in place of regular
17941 server descriptors. This transition will eventually allow clients
17942 to use far less bandwidth for downloading information about the
17943 network. Begins the implementation of Proposal 158: "Clients
17944 download consensus + microdescriptors".
17945 - The directory voting system is now extensible to use multiple hash
17946 algorithms for signatures and resource selection. Newer formats
17947 are signed with SHA256, with a possibility for moving to a better
17948 hash algorithm in the future.
17949 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
17950 current and future memory pages via mlockall(). On supported
17951 platforms (modern Linux and probably BSD but not Windows or OS X),
17952 this should effectively disable any and all attempts to page out
17953 memory. This option requires that you start your Tor as root --
17954 if you use DisableAllSwap, please consider using the User option
17955 to properly reduce the privileges of your Tor.
17956 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
17957 to help Tor build correctly for Android phones.
17960 - Work around a security feature in OpenSSL 0.9.8l that prevents our
17961 handshake from working unless we explicitly tell OpenSSL that we
17962 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
17963 won't work unless we say we are.
17966 - Fix a crash bug when trying to initialize the evdns module in
17967 Libevent 2. Bugfix on 0.2.1.16-rc.
17968 - Stop logging at severity 'warn' when some other Tor client tries
17969 to establish a circuit with us using weak DH keys. It's a protocol
17970 violation, but that doesn't mean ordinary users need to hear about
17971 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
17972 - Do not refuse to learn about authority certs and v2 networkstatus
17973 documents that are older than the latest consensus. This bug might
17974 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
17975 Spotted and fixed by xmux.
17976 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
17977 - If all authorities restart at once right before a consensus vote,
17978 nobody will vote about "Running", and clients will get a consensus
17979 with no usable relays. Instead, authorities refuse to build a
17980 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
17981 - If your relay can't keep up with the number of incoming create
17982 cells, it would log one warning per failure into your logs. Limit
17983 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
17984 - Bridges now use "reject *:*" as their default exit policy. Bugfix
17985 on 0.2.0.3-alpha; fixes bug 1113.
17986 - Fix a memory leak on directory authorities during voting that was
17987 introduced in 0.2.2.1-alpha. Found via valgrind.
17990 Changes in version 0.2.1.20 - 2009-10-15
17991 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
17992 services at once, prepares for more performance improvements, and
17993 fixes a bunch of smaller bugs.
17995 The Windows and OS X bundles also include a more recent Vidalia,
17996 and switch from Privoxy to Polipo.
17998 The OS X installers are now drag and drop. It's best to un-install
17999 Tor/Vidalia and then install this new bundle, rather than upgrade. If
18000 you want to upgrade, you'll need to update the paths for Tor and Polipo
18001 in the Vidalia Settings window.
18004 - Send circuit or stream sendme cells when our window has decreased
18005 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
18006 by Karsten when testing the "reduce circuit window" performance
18007 patch. Bugfix on the 54th commit on Tor -- from July 2002,
18008 before the release of Tor 0.0.0. This is the new winner of the
18010 - Fix a remotely triggerable memory leak when a consensus document
18011 contains more than one signature from the same voter. Bugfix on
18013 - Avoid segfault in rare cases when finishing an introduction circuit
18014 as a client and finding out that we don't have an introduction key
18015 for it. Fixes bug 1073. Reported by Aaron Swartz.
18018 - Tor now reads the "circwindow" parameter out of the consensus,
18019 and uses that value for its circuit package window rather than the
18020 default of 1000 cells. Begins the implementation of proposal 168.
18022 o New directory authorities:
18023 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
18025 - Move moria1 and tonga to alternate IP addresses.
18028 - Fix a signed/unsigned compile warning in 0.2.1.19.
18029 - Fix possible segmentation fault on directory authorities. Bugfix on
18031 - Fix an extremely rare infinite recursion bug that could occur if
18032 we tried to log a message after shutting down the log subsystem.
18033 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
18034 - Fix an obscure bug where hidden services on 64-bit big-endian
18035 systems might mis-read the timestamp in v3 introduce cells, and
18036 refuse to connect back to the client. Discovered by "rotor".
18037 Bugfix on 0.2.1.6-alpha.
18038 - We were triggering a CLOCK_SKEW controller status event whenever
18039 we connect via the v2 connection protocol to any relay that has
18040 a wrong clock. Instead, we should only inform the controller when
18041 it's a trusted authority that claims our clock is wrong. Bugfix
18042 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
18043 - We were telling the controller about CHECKING_REACHABILITY and
18044 REACHABILITY_FAILED status events whenever we launch a testing
18045 circuit or notice that one has failed. Instead, only tell the
18046 controller when we want to inform the user of overall success or
18047 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
18049 - Don't warn when we're using a circuit that ends with a node
18050 excluded in ExcludeExitNodes, but the circuit is not used to access
18051 the outside world. This should help fix bug 1090. Bugfix on
18053 - Work around a small memory leak in some versions of OpenSSL that
18054 stopped the memory used by the hostname TLS extension from being
18058 - Add a "getinfo status/accepted-server-descriptor" controller
18059 command, which is the recommended way for controllers to learn
18060 whether our server descriptor has been successfully received by at
18061 least on directory authority. Un-recommend good-server-descriptor
18062 getinfo and status events until we have a better design for them.
18065 Changes in version 0.2.2.5-alpha - 2009-10-11
18066 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
18069 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
18071 o Directory authorities:
18072 - Temporarily (just for this release) move dizum to an alternate
18076 Changes in version 0.2.2.4-alpha - 2009-10-10
18077 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
18078 introduces a new unit test framework, shifts directry authority
18079 addresses around to reduce the impact from recent blocking events,
18080 and fixes a few smaller bugs.
18083 - Fix several more asserts in the circuit_build_times code, for
18084 example one that causes Tor to fail to start once we have
18085 accumulated 5000 build times in the state file. Bugfixes on
18086 0.2.2.2-alpha; fixes bug 1108.
18088 o New directory authorities:
18089 - Move moria1 and Tonga to alternate IP addresses.
18092 - Log SSL state transitions at debug level during handshake, and
18093 include SSL states in error messages. This may help debug future
18094 SSL handshake issues.
18095 - Add a new "Handshake" log domain for activities that happen
18096 during the TLS handshake.
18097 - Revert to the "June 3 2009" ip-to-country file. The September one
18098 seems to have removed most US IP addresses.
18099 - Directory authorities now reject Tor relays with versions less than
18100 0.1.2.14. This step cuts out four relays from the current network,
18101 none of which are very big.
18104 - Fix a couple of smaller issues with gathering statistics. Bugfixes
18106 - Fix two memory leaks in the error case of
18107 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
18108 - Don't count one-hop circuits when we're estimating how long it
18109 takes circuits to build on average. Otherwise we'll set our circuit
18110 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
18111 - Directory authorities no longer change their opinion of, or vote on,
18112 whether a router is Running, unless they have themselves been
18113 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
18116 o Code simplifications and refactoring:
18117 - Revise our unit tests to use the "tinytest" framework, so we
18118 can run tests in their own processes, have smarter setup/teardown
18119 code, and so on. The unit test code has moved to its own
18120 subdirectory, and has been split into multiple modules.
18123 Changes in version 0.2.2.3-alpha - 2009-09-23
18124 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
18127 - Fix an overzealous assert in our new circuit build timeout code.
18128 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
18131 - If the networkstatus consensus tells us that we should use a
18132 negative circuit package window, ignore it. Otherwise we'll
18133 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
18136 Changes in version 0.2.2.2-alpha - 2009-09-21
18137 Tor 0.2.2.2-alpha introduces our latest performance improvement for
18138 clients: Tor tracks the average time it takes to build a circuit, and
18139 avoids using circuits that take too long to build. For fast connections,
18140 this feature can cut your expected latency in half. For slow or flaky
18141 connections, it could ruin your Tor experience. Let us know if it does!
18144 - Tor now tracks how long it takes to build client-side circuits
18145 over time, and adapts its timeout to local network performance.
18146 Since a circuit that takes a long time to build will also provide
18147 bad performance, we get significant latency improvements by
18148 discarding the slowest 20% of circuits. Specifically, Tor creates
18149 circuits more aggressively than usual until it has enough data
18150 points for a good timeout estimate. Implements proposal 151.
18151 We are especially looking for reports (good and bad) from users with
18152 both EDGE and broadband connections that can move from broadband
18153 to EDGE and find out if the build-time data in the .tor/state gets
18154 reset without loss of Tor usability. You should also see a notice
18155 log message telling you that Tor has reset its timeout.
18156 - Directory authorities can now vote on arbitary integer values as
18157 part of the consensus process. This is designed to help set
18158 network-wide parameters. Implements proposal 167.
18159 - Tor now reads the "circwindow" parameter out of the consensus,
18160 and uses that value for its circuit package window rather than the
18161 default of 1000 cells. Begins the implementation of proposal 168.
18164 - Fix a remotely triggerable memory leak when a consensus document
18165 contains more than one signature from the same voter. Bugfix on
18169 - Fix an extremely rare infinite recursion bug that could occur if
18170 we tried to log a message after shutting down the log subsystem.
18171 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
18172 - Fix parsing for memory or time units given without a space between
18173 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
18174 - A networkstatus vote must contain exactly one signature. Spec
18175 conformance issue. Bugfix on 0.2.0.3-alpha.
18176 - Fix an obscure bug where hidden services on 64-bit big-endian
18177 systems might mis-read the timestamp in v3 introduce cells, and
18178 refuse to connect back to the client. Discovered by "rotor".
18179 Bugfix on 0.2.1.6-alpha.
18180 - We were triggering a CLOCK_SKEW controller status event whenever
18181 we connect via the v2 connection protocol to any relay that has
18182 a wrong clock. Instead, we should only inform the controller when
18183 it's a trusted authority that claims our clock is wrong. Bugfix
18184 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
18185 - We were telling the controller about CHECKING_REACHABILITY and
18186 REACHABILITY_FAILED status events whenever we launch a testing
18187 circuit or notice that one has failed. Instead, only tell the
18188 controller when we want to inform the user of overall success or
18189 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
18191 - Don't warn when we're using a circuit that ends with a node
18192 excluded in ExcludeExitNodes, but the circuit is not used to access
18193 the outside world. This should help fix bug 1090, but more problems
18194 remain. Bugfix on 0.2.1.6-alpha.
18195 - Work around a small memory leak in some versions of OpenSSL that
18196 stopped the memory used by the hostname TLS extension from being
18198 - Make our 'torify' script more portable; if we have only one of
18199 'torsocks' or 'tsocks' installed, don't complain to the user;
18200 and explain our warning about tsocks better.
18203 - Add a "getinfo status/accepted-server-descriptor" controller
18204 command, which is the recommended way for controllers to learn
18205 whether our server descriptor has been successfully received by at
18206 least on directory authority. Un-recommend good-server-descriptor
18207 getinfo and status events until we have a better design for them.
18208 - Update to the "September 4 2009" ip-to-country file.
18211 Changes in version 0.2.2.1-alpha - 2009-08-26
18212 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
18213 Tor clients to bootstrap on networks where only port 80 is reachable,
18214 makes it more straightforward to support hardware crypto accelerators,
18215 and starts the groundwork for gathering stats safely at relays.
18218 - Start the process of disabling ".exit" address notation, since it
18219 can be used for a variety of esoteric application-level attacks
18220 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
18223 o New directory authorities:
18224 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
18228 - New AccelName and AccelDir options add support for dynamic OpenSSL
18229 hardware crypto acceleration engines.
18230 - Tor now supports tunneling all of its outgoing connections over
18231 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
18232 configuration options. Code by Christopher Davis.
18235 - Send circuit or stream sendme cells when our window has decreased
18236 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
18237 by Karsten when testing the "reduce circuit window" performance
18238 patch. Bugfix on the 54th commit on Tor -- from July 2002,
18239 before the release of Tor 0.0.0. This is the new winner of the
18242 o New options for gathering stats safely:
18243 - Directory mirrors that set "DirReqStatistics 1" write statistics
18244 about directory requests to disk every 24 hours. As compared to the
18245 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
18246 1) stats are written to disk exactly every 24 hours; 2) estimated
18247 shares of v2 and v3 requests are determined as mean values, not at
18248 the end of a measurement period; 3) unresolved requests are listed
18249 with country code '??'; 4) directories also measure download times.
18250 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
18251 number of exit streams and transferred bytes per port to disk every
18253 - Relays that set "CellStatistics 1" write statistics on how long
18254 cells spend in their circuit queues to disk every 24 hours.
18255 - Entry nodes that set "EntryStatistics 1" write statistics on the
18256 rough number and origins of connecting clients to disk every 24
18258 - Relays that write any of the above statistics to disk and set
18259 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
18260 their extra-info documents.
18263 - New --digests command-line switch to output the digests of the
18264 source files Tor was built with.
18265 - The "torify" script now uses torsocks where available.
18266 - The memarea code now uses a sentinel value at the end of each area
18267 to make sure nothing writes beyond the end of an area. This might
18268 help debug some conceivable causes of bug 930.
18269 - Time and memory units in the configuration file can now be set to
18270 fractional units. For example, "2.5 GB" is now a valid value for
18272 - Certain Tor clients (such as those behind check.torproject.org) may
18273 want to fetch the consensus in an extra early manner. To enable this
18274 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
18275 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
18276 as only certain clients who must have this information sooner should
18278 - Instead of adding the svn revision to the Tor version string, report
18279 the git commit (when we're building from a git checkout).
18282 - If any of the v3 certs we download are unparseable, we should
18283 actually notice the failure so we don't retry indefinitely. Bugfix
18284 on 0.2.0.x; reported by "rotator".
18285 - If the cached cert file is unparseable, warn but don't exit.
18286 - Fix possible segmentation fault on directory authorities. Bugfix on
18288 - When Tor fails to parse a descriptor of any kind, dump it to disk.
18289 Might help diagnosing bug 1051.
18291 o Deprecated and removed features:
18292 - The controller no longer accepts the old obsolete "addr-mappings/"
18293 or "unregistered-servers-" GETINFO values.
18294 - Hidden services no longer publish version 0 descriptors, and clients
18295 do not request or use version 0 descriptors. However, the old hidden
18296 service authorities still accept and serve version 0 descriptors
18297 when contacted by older hidden services/clients.
18298 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
18299 always on; using them is necessary for correct forward-compatible
18301 - Remove support for .noconnect style addresses. Nobody was using
18302 them, and they provided another avenue for detecting Tor users
18303 via application-level web tricks.
18305 o Packaging changes:
18306 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
18307 installer bundles. See
18308 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
18309 for details of what's new in Vidalia 0.2.3.
18310 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
18311 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
18312 configuration file, rather than the old Privoxy.
18313 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
18314 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
18315 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
18316 better compatibility with OS X 10.6, aka Snow Leopard.
18317 - OS X Vidalia Bundle: The multi-package installer is now replaced
18318 by a simple drag and drop to the /Applications folder. This change
18319 occurred with the upgrade to Vidalia 0.2.3.
18322 Changes in version 0.2.1.19 - 2009-07-28
18323 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
18324 services on Tor 0.2.1.3-alpha through 0.2.1.18.
18327 - Make accessing hidden services on 0.2.1.x work right again.
18328 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
18329 part of patch provided by "optimist".
18332 - When a relay/bridge is writing out its identity key fingerprint to
18333 the "fingerprint" file and to its logs, write it without spaces. Now
18334 it will look like the fingerprints in our bridges documentation,
18335 and confuse fewer users.
18338 - Relays no longer publish a new server descriptor if they change
18339 their MaxAdvertisedBandwidth config option but it doesn't end up
18340 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
18341 fixes bug 1026. Patch from Sebastian.
18342 - Avoid leaking memory every time we get a create cell but we have
18343 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
18344 fixes bug 1034. Reported by BarkerJr.
18347 Changes in version 0.2.1.18 - 2009-07-24
18348 Tor 0.2.1.18 lays the foundations for performance improvements,
18349 adds status events to help users diagnose bootstrap problems, adds
18350 optional authentication/authorization for hidden services, fixes a
18351 variety of potential anonymity problems, and includes a huge pile of
18352 other features and bug fixes.
18355 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
18358 Changes in version 0.2.1.17-rc - 2009-07-07
18359 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
18360 candidate for the 0.2.1.x series. It lays the groundwork for further
18361 client performance improvements, and also fixes a big bug with directory
18362 authorities that were causing them to assign Guard and Stable flags
18365 The Windows bundles also finally include the geoip database that we
18366 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
18367 should actually install Torbutton rather than giving you a cryptic
18368 failure message (oops).
18371 - Clients now use the bandwidth values in the consensus, rather than
18372 the bandwidth values in each relay descriptor. This approach opens
18373 the door to more accurate bandwidth estimates once the directory
18374 authorities start doing active measurements. Implements more of
18378 - When Tor clients restart after 1-5 days, they discard all their
18379 cached descriptors as too old, but they still use the cached
18380 consensus document. This approach is good for robustness, but
18381 bad for performance: since they don't know any bandwidths, they
18382 end up choosing at random rather than weighting their choice by
18383 speed. Fixed by the above feature of putting bandwidths in the
18384 consensus. Bugfix on 0.2.0.x.
18385 - Directory authorities were neglecting to mark relays down in their
18386 internal histories if the relays fall off the routerlist without
18387 ever being found unreachable. So there were relays in the histories
18388 that haven't been seen for eight months, and are listed as being
18389 up for eight months. This wreaked havoc on the "median wfu"
18390 and "median mtbf" calculations, in turn making Guard and Stable
18391 flags very wrong, hurting network performance. Fixes bugs 696 and
18392 969. Bugfix on 0.2.0.6-alpha.
18395 - Serve the DirPortFrontPage page even when we have been approaching
18396 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
18397 - The control port would close the connection before flushing long
18398 replies, such as the network consensus, if a QUIT command was issued
18399 before the reply had completed. Now, the control port flushes all
18400 pending replies before closing the connection. Also fixed a spurious
18401 warning when a QUIT command is issued after a malformed or rejected
18402 AUTHENTICATE command, but before the connection was closed. Patch
18403 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
18404 - When we can't find an intro key for a v2 hidden service descriptor,
18405 fall back to the v0 hidden service descriptor and log a bug message.
18406 Workaround for bug 1024.
18407 - Fix a log message that did not respect the SafeLogging option.
18411 - If we're a relay and we change our IP address, be more verbose
18412 about the reason that made us change. Should help track down
18413 further bugs for relays on dynamic IP addresses.
18416 Changes in version 0.2.0.35 - 2009-06-24
18418 - Avoid crashing in the presence of certain malformed descriptors.
18419 Found by lark, and by automated fuzzing.
18420 - Fix an edge case where a malicious exit relay could convince a
18421 controller that the client's DNS question resolves to an internal IP
18422 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
18425 - Finally fix the bug where dynamic-IP relays disappear when their
18426 IP address changes: directory mirrors were mistakenly telling
18427 them their old address if they asked via begin_dir, so they
18428 never got an accurate answer about their new address, so they
18429 just vanished after a day. For belt-and-suspenders, relays that
18430 don't set Address in their config now avoid using begin_dir for
18431 all direct connections. Should fix bugs 827, 883, and 900.
18432 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
18433 that would occur on some exit nodes when DNS failures and timeouts
18434 occurred in certain patterns. Fix for bug 957.
18437 - When starting with a cache over a few days old, do not leak
18438 memory for the obsolete router descriptors in it. Bugfix on
18439 0.2.0.33; fixes bug 672.
18440 - Hidden service clients didn't use a cached service descriptor that
18441 was older than 15 minutes, but wouldn't fetch a new one either,
18442 because there was already one in the cache. Now, fetch a v2
18443 descriptor unless the same descriptor was added to the cache within
18444 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
18447 Changes in version 0.2.1.16-rc - 2009-06-20
18448 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
18449 a bunch of minor bugs.
18452 - Fix an edge case where a malicious exit relay could convince a
18453 controller that the client's DNS question resolves to an internal IP
18454 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
18456 o Major performance improvements (on 0.2.0.x):
18457 - Disable and refactor some debugging checks that forced a linear scan
18458 over the whole server-side DNS cache. These accounted for over 50%
18459 of CPU time on a relatively busy exit node's gprof profile. Found
18461 - Disable some debugging checks that appeared in exit node profile
18465 - Update to the "June 3 2009" ip-to-country file.
18466 - Do not have tor-resolve automatically refuse all .onion addresses;
18467 if AutomapHostsOnResolve is set in your torrc, this will work fine.
18469 o Minor bugfixes (on 0.2.0.x):
18470 - Log correct error messages for DNS-related network errors on
18472 - Fix a race condition that could cause crashes or memory corruption
18473 when running as a server with a controller listening for log
18475 - Avoid crashing when we have a policy specified in a DirPolicy or
18476 SocksPolicy or ReachableAddresses option with ports set on it,
18477 and we re-load the policy. May fix bug 996.
18478 - Hidden service clients didn't use a cached service descriptor that
18479 was older than 15 minutes, but wouldn't fetch a new one either,
18480 because there was already one in the cache. Now, fetch a v2
18481 descriptor unless the same descriptor was added to the cache within
18482 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
18484 o Minor bugfixes (on 0.2.1.x):
18485 - Don't warn users about low port and hibernation mix when they
18486 provide a *ListenAddress directive to fix that. Bugfix on
18488 - When switching back and forth between bridge mode, do not start
18489 gathering GeoIP data until two hours have passed.
18490 - Do not complain that the user has requested an excluded node as
18491 an exit when the node is not really an exit. This could happen
18492 because the circuit was for testing, or an introduction point.
18496 Changes in version 0.2.1.15-rc - 2009-05-25
18497 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
18498 series. It fixes a major bug on fast exit relays, as well as a variety
18499 of more minor bugs.
18501 o Major bugfixes (on 0.2.0.x):
18502 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
18503 that would occur on some exit nodes when DNS failures and timeouts
18504 occurred in certain patterns. Fix for bug 957.
18506 o Minor bugfixes (on 0.2.0.x):
18507 - Actually return -1 in the error case for read_bandwidth_usage().
18508 Harmless bug, since we currently don't care about the return value
18509 anywhere. Bugfix on 0.2.0.9-alpha.
18510 - Provide a more useful log message if bug 977 (related to buffer
18511 freelists) ever reappears, and do not crash right away.
18512 - Fix an assertion failure on 64-bit platforms when we allocated
18513 memory right up to the end of a memarea, then realigned the memory
18514 one step beyond the end. Fixes a possible cause of bug 930.
18515 - Protect the count of open sockets with a mutex, so we can't
18516 corrupt it when two threads are closing or opening sockets at once.
18517 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
18518 - Don't allow a bridge to publish its router descriptor to a
18519 non-bridge directory authority. Fixes part of bug 932.
18520 - When we change to or from being a bridge, reset our counts of
18521 client usage by country. Fixes bug 932.
18522 - Fix a bug that made stream bandwidth get misreported to the
18524 - Stop using malloc_usable_size() to use more area than we had
18525 actually allocated: it was safe, but made valgrind really unhappy.
18526 - Fix a memory leak when v3 directory authorities load their keys
18527 and cert from disk. Bugfix on 0.2.0.1-alpha.
18529 o Minor bugfixes (on 0.2.1.x):
18530 - Fix use of freed memory when deciding to mark a non-addable
18531 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
18534 Changes in version 0.2.1.14-rc - 2009-04-12
18535 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
18536 series. It begins fixing some major performance problems, and also
18537 finally addresses the bug that was causing relays on dynamic IP
18538 addresses to fall out of the directory.
18541 - Clients replace entry guards that were chosen more than a few months
18542 ago. This change should significantly improve client performance,
18543 especially once more people upgrade, since relays that have been
18544 a guard for a long time are currently overloaded.
18546 o Major bugfixes (on 0.2.0):
18547 - Finally fix the bug where dynamic-IP relays disappear when their
18548 IP address changes: directory mirrors were mistakenly telling
18549 them their old address if they asked via begin_dir, so they
18550 never got an accurate answer about their new address, so they
18551 just vanished after a day. For belt-and-suspenders, relays that
18552 don't set Address in their config now avoid using begin_dir for
18553 all direct connections. Should fix bugs 827, 883, and 900.
18554 - Relays were falling out of the networkstatus consensus for
18555 part of a day if they changed their local config but the
18556 authorities discarded their new descriptor as "not sufficiently
18557 different". Now directory authorities accept a descriptor as changed
18558 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
18559 patch by Sebastian.
18560 - Avoid crashing in the presence of certain malformed descriptors.
18561 Found by lark, and by automated fuzzing.
18564 - When generating circuit events with verbose nicknames for
18565 controllers, try harder to look up nicknames for routers on a
18566 circuit. (Previously, we would look in the router descriptors we had
18567 for nicknames, but not in the consensus.) Partial fix for bug 941.
18568 - If the bridge config line doesn't specify a port, assume 443.
18569 This makes bridge lines a bit smaller and easier for users to
18571 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
18572 bytes (aka 20KB/s), to match our documentation. Also update
18573 directory authorities so they always assign the Fast flag to relays
18574 with 20KB/s of capacity. Now people running relays won't suddenly
18575 find themselves not seeing any use, if the network gets faster
18577 - Update to the "April 3 2009" ip-to-country file.
18580 - Avoid trying to print raw memory to the logs when we decide to
18581 give up on downloading a given relay descriptor. Bugfix on
18583 - In tor-resolve, when the Tor client to use is specified by
18584 <hostname>:<port>, actually use the specified port rather than
18585 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
18586 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
18587 - When starting with a cache over a few days old, do not leak
18588 memory for the obsolete router descriptors in it. Bugfix on
18590 - Avoid double-free on list of successfully uploaded hidden
18591 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
18592 - Change memarea_strndup() implementation to work even when
18593 duplicating a string at the end of a page. This bug was
18594 harmless for now, but could have meant crashes later. Fix by
18595 lark. Bugfix on 0.2.1.1-alpha.
18596 - Limit uploaded directory documents to be 16M rather than 500K.
18597 The directory authorities were refusing v3 consensus votes from
18598 other authorities, since the votes are now 504K. Fixes bug 959;
18599 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
18600 - Directory authorities should never send a 503 "busy" response to
18601 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
18605 Changes in version 0.2.1.13-alpha - 2009-03-09
18606 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
18607 cleanups. We're finally getting close to a release candidate.
18610 - Correctly update the list of which countries we exclude as
18611 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
18612 lark. Bugfix on 0.2.1.6-alpha.
18614 o Minor bugfixes (on 0.2.0.x and earlier):
18615 - Automatically detect MacOSX versions earlier than 10.4.0, and
18616 disable kqueue from inside Tor when running with these versions.
18617 We previously did this from the startup script, but that was no
18618 help to people who didn't use the startup script. Resolves bug 863.
18619 - When we had picked an exit node for a connection, but marked it as
18620 "optional", and it turned out we had no onion key for the exit,
18621 stop wanting that exit and try again. This situation may not
18622 be possible now, but will probably become feasible with proposal
18623 158. Spotted by rovv. Fixes another case of bug 752.
18624 - Clients no longer cache certificates for authorities they do not
18625 recognize. Bugfix on 0.2.0.9-alpha.
18626 - When we can't transmit a DNS request due to a network error, retry
18627 it after a while, and eventually transmit a failing response to
18628 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
18629 - If the controller claimed responsibility for a stream, but that
18630 stream never finished making its connection, it would live
18631 forever in circuit_wait state. Now we close it after SocksTimeout
18632 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
18633 - Drop begin cells to a hidden service if they come from the middle
18634 of a circuit. Patch from lark.
18635 - When we erroneously receive two EXTEND cells for the same circuit
18636 ID on the same connection, drop the second. Patch from lark.
18637 - Fix a crash that occurs on exit nodes when a nameserver request
18638 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
18639 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
18641 - Do not assume that a stack-allocated character array will be
18642 64-bit aligned on platforms that demand that uint64_t access is
18643 aligned. Possible fix for bug 604.
18644 - Parse dates and IPv4 addresses in a locale- and libc-independent
18645 manner, to avoid platform-dependent behavior on malformed input.
18646 - Build correctly when configured to build outside the main source
18647 path. Patch from Michael Gold.
18648 - We were already rejecting relay begin cells with destination port
18649 of 0. Now also reject extend cells with destination port or address
18650 of 0. Suggested by lark.
18652 o Minor bugfixes (on 0.2.1.x):
18653 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
18654 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
18655 - If we're an exit node, scrub the IP address to which we are exiting
18656 in the logs. Bugfix on 0.2.1.8-alpha.
18659 - On Linux, use the prctl call to re-enable core dumps when the user
18661 - New controller event NEWCONSENSUS that lists the networkstatus
18662 lines for every recommended relay. Now controllers like Torflow
18663 can keep up-to-date on which relays they should be using.
18664 - Update to the "February 26 2009" ip-to-country file.
18667 Changes in version 0.2.0.34 - 2009-02-08
18668 Tor 0.2.0.34 features several more security-related fixes. You should
18669 upgrade, especially if you run an exit relay (remote crash) or a
18670 directory authority (remote infinite loop), or you're on an older
18671 (pre-XP) or not-recently-patched Windows (remote exploit).
18673 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
18674 have many known flaws, and nobody should be using them. You should
18675 upgrade. If you're using a Linux or BSD and its packages are obsolete,
18676 stop using those packages and upgrade anyway.
18679 - Fix an infinite-loop bug on handling corrupt votes under certain
18680 circumstances. Bugfix on 0.2.0.8-alpha.
18681 - Fix a temporary DoS vulnerability that could be performed by
18682 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
18683 - Avoid a potential crash on exit nodes when processing malformed
18684 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
18685 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
18686 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
18689 - Fix compilation on systems where time_t is a 64-bit integer.
18690 Patch from Matthias Drochner.
18691 - Don't consider expiring already-closed client connections. Fixes
18692 bug 893. Bugfix on 0.0.2pre20.
18695 Changes in version 0.2.1.12-alpha - 2009-02-08
18696 Tor 0.2.1.12-alpha features several more security-related fixes. You
18697 should upgrade, especially if you run an exit relay (remote crash) or
18698 a directory authority (remote infinite loop), or you're on an older
18699 (pre-XP) or not-recently-patched Windows (remote exploit). It also
18700 includes a big pile of minor bugfixes and cleanups.
18703 - Fix an infinite-loop bug on handling corrupt votes under certain
18704 circumstances. Bugfix on 0.2.0.8-alpha.
18705 - Fix a temporary DoS vulnerability that could be performed by
18706 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
18707 - Avoid a potential crash on exit nodes when processing malformed
18708 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
18711 - Let controllers actually ask for the "clients_seen" event for
18712 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
18713 reported by Matt Edman.
18714 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
18716 - Fix a bug in address parsing that was preventing bridges or hidden
18717 service targets from being at IPv6 addresses.
18718 - Solve a bug that kept hardware crypto acceleration from getting
18719 enabled when accounting was turned on. Fixes bug 907. Bugfix on
18721 - Remove a bash-ism from configure.in to build properly on non-Linux
18722 platforms. Bugfix on 0.2.1.1-alpha.
18723 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
18724 headers. Bugfix on 0.2.0.10-alpha.
18725 - Don't consider expiring already-closed client connections. Fixes
18726 bug 893. Bugfix on 0.0.2pre20.
18727 - Fix another interesting corner-case of bug 891 spotted by rovv:
18728 Previously, if two hosts had different amounts of clock drift, and
18729 one of them created a new connection with just the wrong timing,
18730 the other might decide to deprecate the new connection erroneously.
18731 Bugfix on 0.1.1.13-alpha.
18732 - Resolve a very rare crash bug that could occur when the user forced
18733 a nameserver reconfiguration during the middle of a nameserver
18734 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
18735 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
18736 Bugfix on 0.2.1.7-alpha.
18737 - If we're using bridges and our network goes away, be more willing
18738 to forgive our bridges and try again when we get an application
18739 request. Bugfix on 0.2.0.x.
18742 - Support platforms where time_t is 64 bits long. (Congratulations,
18743 NetBSD!) Patch from Matthias Drochner.
18744 - Add a 'getinfo status/clients-seen' controller command, in case
18745 controllers want to hear clients_seen events but connect late.
18748 - Disable GCC's strict alias optimization by default, to avoid the
18749 likelihood of its introducing subtle bugs whenever our code violates
18750 the letter of C99's alias rules.
18753 Changes in version 0.2.0.33 - 2009-01-21
18754 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
18755 useful to users. It also finally fixes a bug where a relay or client
18756 that's been off for many days would take a long time to bootstrap.
18758 This update also fixes an important security-related bug reported by
18759 Ilja van Sprundel. You should upgrade. (We'll send out more details
18760 about the bug once people have had some time to upgrade.)
18763 - Fix a heap-corruption bug that may be remotely triggerable on
18764 some platforms. Reported by Ilja van Sprundel.
18767 - When a stream at an exit relay is in state "resolving" or
18768 "connecting" and it receives an "end" relay cell, the exit relay
18769 would silently ignore the end cell and not close the stream. If
18770 the client never closes the circuit, then the exit relay never
18771 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
18772 reported by "wood".
18773 - When sending CREATED cells back for a given circuit, use a 64-bit
18774 connection ID to find the right connection, rather than an addr:port
18775 combination. Now that we can have multiple OR connections between
18776 the same ORs, it is no longer possible to use addr:port to uniquely
18777 identify a connection.
18778 - Bridge relays that had DirPort set to 0 would stop fetching
18779 descriptors shortly after startup, and then briefly resume
18780 after a new bandwidth test and/or after publishing a new bridge
18781 descriptor. Bridge users that try to bootstrap from them would
18782 get a recent networkstatus but would get descriptors from up to
18783 18 hours earlier, meaning most of the descriptors were obsolete
18784 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
18785 - Prevent bridge relays from serving their 'extrainfo' document
18786 to anybody who asks, now that extrainfo docs include potentially
18787 sensitive aggregated client geoip summaries. Bugfix on
18789 - If the cached networkstatus consensus is more than five days old,
18790 discard it rather than trying to use it. In theory it could be
18791 useful because it lists alternate directory mirrors, but in practice
18792 it just means we spend many minutes trying directory mirrors that
18793 are long gone from the network. Also discard router descriptors as
18794 we load them if they are more than five days old, since the onion
18795 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
18798 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
18799 could make gcc generate non-functional binary search code. Bugfix
18801 - Build correctly on platforms without socklen_t.
18802 - Compile without warnings on solaris.
18803 - Avoid potential crash on internal error during signature collection.
18804 Fixes bug 864. Patch from rovv.
18805 - Correct handling of possible malformed authority signing key
18806 certificates with internal signature types. Fixes bug 880.
18807 Bugfix on 0.2.0.3-alpha.
18808 - Fix a hard-to-trigger resource leak when logging credential status.
18810 - When we can't initialize DNS because the network is down, do not
18811 automatically stop Tor from starting. Instead, we retry failed
18812 dns_init() every 10 minutes, and change the exit policy to reject
18813 *:* until one succeeds. Fixes bug 691.
18814 - Use 64 bits instead of 32 bits for connection identifiers used with
18815 the controller protocol, to greatly reduce risk of identifier reuse.
18816 - When we're choosing an exit node for a circuit, and we have
18817 no pending streams, choose a good general exit rather than one that
18818 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
18819 - Fix another case of assuming, when a specific exit is requested,
18820 that we know more than the user about what hosts it allows.
18821 Fixes one case of bug 752. Patch from rovv.
18822 - Clip the MaxCircuitDirtiness config option to a minimum of 10
18823 seconds. Warn the user if lower values are given in the
18824 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
18825 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
18826 user if lower values are given in the configuration. Bugfix on
18827 0.1.1.17-rc. Patch by Sebastian.
18828 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
18829 the cache because we already had a v0 descriptor with the same ID.
18830 Bugfix on 0.2.0.18-alpha.
18831 - Fix a race condition when freeing keys shared between main thread
18832 and CPU workers that could result in a memory leak. Bugfix on
18833 0.1.0.1-rc. Fixes bug 889.
18834 - Send a valid END cell back when a client tries to connect to a
18835 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
18836 840. Patch from rovv.
18837 - Check which hops rendezvous stream cells are associated with to
18838 prevent possible guess-the-streamid injection attacks from
18839 intermediate hops. Fixes another case of bug 446. Based on patch
18841 - If a broken client asks a non-exit router to connect somewhere,
18842 do not even do the DNS lookup before rejecting the connection.
18843 Fixes another case of bug 619. Patch from rovv.
18844 - When a relay gets a create cell it can't decrypt (e.g. because it's
18845 using the wrong onion key), we were dropping it and letting the
18846 client time out. Now actually answer with a destroy cell. Fixes
18847 bug 904. Bugfix on 0.0.2pre8.
18849 o Minor bugfixes (hidden services):
18850 - Do not throw away existing introduction points on SIGHUP. Bugfix on
18851 0.0.6pre1. Patch by Karsten. Fixes bug 874.
18854 - Report the case where all signatures in a detached set are rejected
18855 differently than the case where there is an error handling the
18857 - When we realize that another process has modified our cached
18858 descriptors, print out a more useful error message rather than
18859 triggering an assertion. Fixes bug 885. Patch from Karsten.
18860 - Implement the 0x20 hack to better resist DNS poisoning: set the
18861 case on outgoing DNS requests randomly, and reject responses that do
18862 not match the case correctly. This logic can be disabled with the
18863 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
18864 of servers that do not reliably preserve case in replies. See
18865 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
18867 - Check DNS replies for more matching fields to better resist DNS
18869 - Never use OpenSSL compression: it wastes RAM and CPU trying to
18870 compress cells, which are basically all encrypted, compressed, or
18874 Changes in version 0.2.1.11-alpha - 2009-01-20
18875 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
18876 week it will take a long time to bootstrap again" bug. It also fixes
18877 an important security-related bug reported by Ilja van Sprundel. You
18878 should upgrade. (We'll send out more details about the bug once people
18879 have had some time to upgrade.)
18882 - Fix a heap-corruption bug that may be remotely triggerable on
18883 some platforms. Reported by Ilja van Sprundel.
18886 - Discard router descriptors as we load them if they are more than
18887 five days old. Otherwise if Tor is off for a long time and then
18888 starts with cached descriptors, it will try to use the onion
18889 keys in those obsolete descriptors when building circuits. Bugfix
18890 on 0.2.0.x. Fixes bug 887.
18893 - Try to make sure that the version of Libevent we're running with
18894 is binary-compatible with the one we built with. May address bug
18896 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
18897 for bug 905. Bugfix on 0.2.1.7-alpha.
18898 - Add a new --enable-local-appdata configuration switch to change
18899 the default location of the datadir on win32 from APPDATA to
18900 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
18901 entirely. Patch from coderman.
18904 - Make outbound DNS packets respect the OutboundBindAddress setting.
18905 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
18906 - When our circuit fails at the first hop (e.g. we get a destroy
18907 cell back), avoid using that OR connection anymore, and also
18908 tell all the one-hop directory requests waiting for it that they
18909 should fail. Bugfix on 0.2.1.3-alpha.
18910 - In the torify(1) manpage, mention that tsocks will leak your
18914 Changes in version 0.2.1.10-alpha - 2009-01-06
18915 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
18916 would make the bridge relay not so useful if it had DirPort set to 0,
18917 and one that could let an attacker learn a little bit of information
18918 about the bridge's users), and a bug that would cause your Tor relay
18919 to ignore a circuit create request it can't decrypt (rather than reply
18920 with an error). It also fixes a wide variety of other bugs.
18923 - If the cached networkstatus consensus is more than five days old,
18924 discard it rather than trying to use it. In theory it could
18925 be useful because it lists alternate directory mirrors, but in
18926 practice it just means we spend many minutes trying directory
18927 mirrors that are long gone from the network. Helps bug 887 a bit;
18929 - Bridge relays that had DirPort set to 0 would stop fetching
18930 descriptors shortly after startup, and then briefly resume
18931 after a new bandwidth test and/or after publishing a new bridge
18932 descriptor. Bridge users that try to bootstrap from them would
18933 get a recent networkstatus but would get descriptors from up to
18934 18 hours earlier, meaning most of the descriptors were obsolete
18935 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
18936 - Prevent bridge relays from serving their 'extrainfo' document
18937 to anybody who asks, now that extrainfo docs include potentially
18938 sensitive aggregated client geoip summaries. Bugfix on
18942 - New controller event "clients_seen" to report a geoip-based summary
18943 of which countries we've seen clients from recently. Now controllers
18944 like Vidalia can show bridge operators that they're actually making
18946 - Build correctly against versions of OpenSSL 0.9.8 or later built
18947 without support for deprecated functions.
18948 - Update to the "December 19 2008" ip-to-country file.
18950 o Minor bugfixes (on 0.2.0.x):
18951 - Authorities now vote for the Stable flag for any router whose
18952 weighted MTBF is at least 5 days, regardless of the mean MTBF.
18953 - Do not remove routers as too old if we do not have any consensus
18954 document. Bugfix on 0.2.0.7-alpha.
18955 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
18956 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
18957 - When an exit relay resolves a stream address to a local IP address,
18958 do not just keep retrying that same exit relay over and
18959 over. Instead, just close the stream. Addresses bug 872. Bugfix
18960 on 0.2.0.32. Patch from rovv.
18961 - If a hidden service sends us an END cell, do not consider
18962 retrying the connection; just close it. Patch from rovv.
18963 - When we made bridge authorities stop serving bridge descriptors over
18964 unencrypted links, we also broke DirPort reachability testing for
18965 bridges. So bridges with a non-zero DirPort were printing spurious
18966 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
18967 - When a relay gets a create cell it can't decrypt (e.g. because it's
18968 using the wrong onion key), we were dropping it and letting the
18969 client time out. Now actually answer with a destroy cell. Fixes
18970 bug 904. Bugfix on 0.0.2pre8.
18971 - Squeeze 2-5% out of client performance (according to oprofile) by
18972 improving the implementation of some policy-manipulation functions.
18974 o Minor bugfixes (on 0.2.1.x):
18975 - Make get_interface_address() function work properly again; stop
18976 guessing the wrong parts of our address as our address.
18977 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
18978 send on that circuit. Otherwise we might violate the proposal-110
18979 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
18981 - When we're sending non-EXTEND cells to the first hop in a circuit,
18982 for example to use an encrypted directory connection, we don't need
18983 to use RELAY_EARLY cells: the first hop knows what kind of cell
18984 it is, and nobody else can even see the cell type. Conserving
18985 RELAY_EARLY cells makes it easier to cannibalize circuits like
18987 - Stop logging nameserver addresses in reverse order.
18988 - If we are retrying a directory download slowly over and over, do
18989 not automatically give up after the 254th failure. Bugfix on
18991 - Resume reporting accurate "stream end" reasons to the local control
18992 port. They were lost in the changes for Proposal 148. Bugfix on
18995 o Deprecated and removed features:
18996 - The old "tor --version --version" command, which would print out
18997 the subversion "Id" of most of the source files, is now removed. It
18998 turned out to be less useful than we'd expected, and harder to
19001 o Code simplifications and refactoring:
19002 - Change our header file guard macros to be less likely to conflict
19003 with system headers. Adam Langley noticed that we were conflicting
19004 with log.h on Android.
19005 - Tool-assisted documentation cleanup. Nearly every function or
19006 static variable in Tor should have its own documentation now.
19009 Changes in version 0.2.1.9-alpha - 2008-12-25
19010 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
19012 o New directory authorities:
19013 - gabelmoo (the authority run by Karsten Loesing) now has a new
19017 - Never use a connection with a mismatched address to extend a
19018 circuit, unless that connection is canonical. A canonical
19019 connection is one whose address is authenticated by the router's
19020 identity key, either in a NETINFO cell or in a router descriptor.
19021 - Avoid a possible memory corruption bug when receiving hidden service
19022 descriptors. Bugfix on 0.2.1.6-alpha.
19025 - Fix a logic error that would automatically reject all but the first
19026 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
19027 part of bug 813/868. Bug spotted by coderman.
19028 - When a stream at an exit relay is in state "resolving" or
19029 "connecting" and it receives an "end" relay cell, the exit relay
19030 would silently ignore the end cell and not close the stream. If
19031 the client never closes the circuit, then the exit relay never
19032 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
19033 reported by "wood".
19034 - When we can't initialize DNS because the network is down, do not
19035 automatically stop Tor from starting. Instead, retry failed
19036 dns_init() every 10 minutes, and change the exit policy to reject
19037 *:* until one succeeds. Fixes bug 691.
19040 - Give a better error message when an overzealous init script says
19041 "sudo -u username tor --user username". Makes Bug 882 easier for
19043 - When a directory authority gives us a new guess for our IP address,
19044 log which authority we used. Hopefully this will help us debug
19045 the recent complaints about bad IP address guesses.
19046 - Detect svn revision properly when we're using git-svn.
19047 - Try not to open more than one descriptor-downloading connection
19048 to an authority at once. This should reduce load on directory
19049 authorities. Fixes bug 366.
19050 - Add cross-certification to newly generated certificates, so that
19051 a signing key is enough information to look up a certificate.
19052 Partial implementation of proposal 157.
19053 - Start serving certificates by <identity digest, signing key digest>
19054 pairs. Partial implementation of proposal 157.
19055 - Clients now never report any stream end reason except 'MISC'.
19056 Implements proposal 148.
19057 - On platforms with a maximum syslog string length, truncate syslog
19058 messages to that length ourselves, rather than relying on the
19059 system to do it for us.
19060 - Optimize out calls to time(NULL) that occur for every IO operation,
19061 or for every cell. On systems where time() is a slow syscall,
19062 this fix will be slightly helpful.
19063 - Exit servers can now answer resolve requests for ip6.arpa addresses.
19064 - When we download a descriptor that we then immediately (as
19065 a directory authority) reject, do not retry downloading it right
19066 away. Should save some bandwidth on authorities. Fix for bug
19067 888. Patch by Sebastian Hahn.
19068 - When a download gets us zero good descriptors, do not notify
19069 Tor that new directory information has arrived.
19070 - Avoid some nasty corner cases in the logic for marking connections
19071 as too old or obsolete or noncanonical for circuits. Partial
19074 o Minor features (controller):
19075 - New CONSENSUS_ARRIVED event to note when a new consensus has
19076 been fetched and validated.
19077 - When we realize that another process has modified our cached
19078 descriptors file, print out a more useful error message rather
19079 than triggering an assertion. Fixes bug 885. Patch from Karsten.
19080 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
19081 controllers to prevent SIGHUP from reloading the
19082 configuration. Fixes bug 856.
19085 - Resume using the correct "REASON=" stream when telling the
19086 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
19087 - When a canonical connection appears later in our internal list
19088 than a noncanonical one for a given OR ID, always use the
19089 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
19091 - Clip the MaxCircuitDirtiness config option to a minimum of 10
19092 seconds. Warn the user if lower values are given in the
19093 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
19094 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
19095 user if lower values are given in the configuration. Bugfix on
19096 0.1.1.17-rc. Patch by Sebastian.
19097 - Fix a race condition when freeing keys shared between main thread
19098 and CPU workers that could result in a memory leak. Bugfix on
19099 0.1.0.1-rc. Fixes bug 889.
19101 o Minor bugfixes (hidden services):
19102 - Do not throw away existing introduction points on SIGHUP (bugfix on
19103 0.0.6pre1); also, do not stall hidden services because we're
19104 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
19105 by John Brooks. Patch by Karsten. Fixes bug 874.
19106 - Fix a memory leak when we decline to add a v2 rendezvous
19107 descriptor to the cache because we already had a v0 descriptor
19108 with the same ID. Bugfix on 0.2.0.18-alpha.
19110 o Deprecated and removed features:
19111 - RedirectExits has been removed. It was deprecated since
19113 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
19114 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
19115 - Cell pools are now always enabled; --disable-cell-pools is ignored.
19117 o Code simplifications and refactoring:
19118 - Rename the confusing or_is_obsolete field to the more appropriate
19119 is_bad_for_new_circs, and move it to or_connection_t where it
19121 - Move edge-only flags from connection_t to edge_connection_t: not
19122 only is this better coding, but on machines of plausible alignment,
19123 it should save 4-8 bytes per connection_t. "Every little bit helps."
19124 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
19125 for consistency; keep old option working for backward compatibility.
19126 - Simplify the code for finding connections to use for a circuit.
19129 Changes in version 0.2.1.8-alpha - 2008-12-08
19130 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
19131 builds better on unusual platforms like Solaris and old OS X, and
19132 fixes a variety of other issues.
19135 - New DirPortFrontPage option that takes an html file and publishes
19136 it as "/" on the DirPort. Now relay operators can provide a
19137 disclaimer without needing to set up a separate webserver. There's
19138 a sample disclaimer in contrib/tor-exit-notice.html.
19141 - When the client is choosing entry guards, now it selects at most
19142 one guard from a given relay family. Otherwise we could end up with
19143 all of our entry points into the network run by the same operator.
19144 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
19147 - Fix a DOS opportunity during the voting signature collection process
19148 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
19149 - Fix a possible segfault when establishing an exit connection. Bugfix
19153 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
19155 - Made Tor a little less aggressive about deleting expired
19156 certificates. Partial fix for bug 854.
19157 - Stop doing unaligned memory access that generated bus errors on
19158 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
19159 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
19160 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
19161 - Make USR2 log-level switch take effect immediately. Bugfix on
19163 - If one win32 nameserver fails to get added, continue adding the
19164 rest, and don't automatically fail.
19165 - Use fcntl() for locking when flock() is not available. Should fix
19166 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
19167 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
19168 could make gcc generate non-functional binary search code. Bugfix
19170 - Build correctly on platforms without socklen_t.
19171 - Avoid potential crash on internal error during signature collection.
19172 Fixes bug 864. Patch from rovv.
19173 - Do not use C's stdio library for writing to log files. This will
19174 improve logging performance by a minute amount, and will stop
19175 leaking fds when our disk is full. Fixes bug 861.
19176 - Stop erroneous use of O_APPEND in cases where we did not in fact
19177 want to re-seek to the end of a file before every last write().
19178 - Correct handling of possible malformed authority signing key
19179 certificates with internal signature types. Fixes bug 880. Bugfix
19181 - Fix a hard-to-trigger resource leak when logging credential status.
19185 - Directory mirrors no longer fetch the v1 directory or
19186 running-routers files. They are obsolete, and nobody asks for them
19187 anymore. This is the first step to making v1 authorities obsolete.
19189 o Minor features (controller):
19190 - Return circuit purposes in response to GETINFO circuit-status. Fixes
19194 Changes in version 0.2.0.32 - 2008-11-20
19195 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
19196 packages (and maybe other packages) noticed by Theo de Raadt, fixes
19197 a smaller security flaw that might allow an attacker to access local
19198 services, further improves hidden service performance, and fixes a
19199 variety of other issues.
19202 - The "User" and "Group" config options did not clear the
19203 supplementary group entries for the Tor process. The "User" option
19204 is now more robust, and we now set the groups to the specified
19205 user's primary group. The "Group" option is now ignored. For more
19206 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
19207 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
19208 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
19209 - The "ClientDNSRejectInternalAddresses" config option wasn't being
19210 consistently obeyed: if an exit relay refuses a stream because its
19211 exit policy doesn't allow it, we would remember what IP address
19212 the relay said the destination address resolves to, even if it's
19213 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
19216 - Fix a DOS opportunity during the voting signature collection process
19217 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
19219 o Major bugfixes (hidden services):
19220 - When fetching v0 and v2 rendezvous service descriptors in parallel,
19221 we were failing the whole hidden service request when the v0
19222 descriptor fetch fails, even if the v2 fetch is still pending and
19223 might succeed. Similarly, if the last v2 fetch fails, we were
19224 failing the whole hidden service request even if a v0 fetch is
19225 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
19226 - When extending a circuit to a hidden service directory to upload a
19227 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
19228 requests failed, because the router descriptor has not been
19229 downloaded yet. In these cases, do not attempt to upload the
19230 rendezvous descriptor, but wait until the router descriptor is
19231 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
19232 descriptor from a hidden service directory for which the router
19233 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
19237 - Fix several infrequent memory leaks spotted by Coverity.
19238 - When testing for libevent functions, set the LDFLAGS variable
19239 correctly. Found by Riastradh.
19240 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
19241 bootstrapping with tunneled directory connections. Bugfix on
19242 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
19243 - When asked to connect to A.B.exit:80, if we don't know the IP for A
19244 and we know that server B rejects most-but-not all connections to
19245 port 80, we would previously reject the connection. Now, we assume
19246 the user knows what they were asking for. Fixes bug 752. Bugfix
19247 on 0.0.9rc5. Diagnosed by BarkerJr.
19248 - If we overrun our per-second write limits a little, count this as
19249 having used up our write allocation for the second, and choke
19250 outgoing directory writes. Previously, we had only counted this when
19251 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
19252 Bugfix on 0.2.0.x (??).
19253 - Remove the old v2 directory authority 'lefkada' from the default
19254 list. It has been gone for many months.
19255 - Stop doing unaligned memory access that generated bus errors on
19256 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
19257 - Make USR2 log-level switch take effect immediately. Bugfix on
19260 o Minor bugfixes (controller):
19261 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
19262 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
19265 Changes in version 0.2.1.7-alpha - 2008-11-08
19266 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
19267 packages (and maybe other packages) noticed by Theo de Raadt, fixes
19268 a smaller security flaw that might allow an attacker to access local
19269 services, adds better defense against DNS poisoning attacks on exit
19270 relays, further improves hidden service performance, and fixes a
19271 variety of other issues.
19274 - The "ClientDNSRejectInternalAddresses" config option wasn't being
19275 consistently obeyed: if an exit relay refuses a stream because its
19276 exit policy doesn't allow it, we would remember what IP address
19277 the relay said the destination address resolves to, even if it's
19278 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
19279 - The "User" and "Group" config options did not clear the
19280 supplementary group entries for the Tor process. The "User" option
19281 is now more robust, and we now set the groups to the specified
19282 user's primary group. The "Group" option is now ignored. For more
19283 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
19284 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
19285 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
19286 - Do not use or believe expired v3 authority certificates. Patch
19287 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
19290 - Now NodeFamily and MyFamily config options allow spaces in
19291 identity fingerprints, so it's easier to paste them in.
19292 Suggested by Lucky Green.
19293 - Implement the 0x20 hack to better resist DNS poisoning: set the
19294 case on outgoing DNS requests randomly, and reject responses that do
19295 not match the case correctly. This logic can be disabled with the
19296 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
19297 of servers that do not reliably preserve case in replies. See
19298 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
19300 - Preserve case in replies to DNSPort requests in order to support
19301 the 0x20 hack for resisting DNS poisoning attacks.
19303 o Hidden service performance improvements:
19304 - When the client launches an introduction circuit, retry with a
19305 new circuit after 30 seconds rather than 60 seconds.
19306 - Launch a second client-side introduction circuit in parallel
19307 after a delay of 15 seconds (based on work by Christian Wilms).
19308 - Hidden services start out building five intro circuits rather
19309 than three, and when the first three finish they publish a service
19310 descriptor using those. Now we publish our service descriptor much
19311 faster after restart.
19314 - Minor fix in the warning messages when you're having problems
19315 bootstrapping; also, be more forgiving of bootstrap problems when
19316 we're still making incremental progress on a given bootstrap phase.
19317 - When we're choosing an exit node for a circuit, and we have
19318 no pending streams, choose a good general exit rather than one that
19319 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
19320 - Send a valid END cell back when a client tries to connect to a
19321 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
19322 840. Patch from rovv.
19323 - If a broken client asks a non-exit router to connect somewhere,
19324 do not even do the DNS lookup before rejecting the connection.
19325 Fixes another case of bug 619. Patch from rovv.
19326 - Fix another case of assuming, when a specific exit is requested,
19327 that we know more than the user about what hosts it allows.
19328 Fixes another case of bug 752. Patch from rovv.
19329 - Check which hops rendezvous stream cells are associated with to
19330 prevent possible guess-the-streamid injection attacks from
19331 intermediate hops. Fixes another case of bug 446. Based on patch
19333 - Avoid using a negative right-shift when comparing 32-bit
19334 addresses. Possible fix for bug 845 and bug 811.
19335 - Make the assert_circuit_ok() function work correctly on circuits that
19336 have already been marked for close.
19337 - Fix read-off-the-end-of-string error in unit tests when decoding
19338 introduction points.
19339 - Fix uninitialized size field for memory area allocation: may improve
19340 memory performance during directory parsing.
19341 - Treat duplicate certificate fetches as failures, so that we do
19342 not try to re-fetch an expired certificate over and over and over.
19343 - Do not say we're fetching a certificate when we'll in fact skip it
19344 because of a pending download.
19347 Changes in version 0.2.1.6-alpha - 2008-09-30
19348 Tor 0.2.1.6-alpha further improves performance and robustness of
19349 hidden services, starts work on supporting per-country relay selection,
19350 and fixes a variety of smaller issues.
19353 - Implement proposal 121: make it possible to build hidden services
19354 that only certain clients are allowed to connect to. This is
19355 enforced at several points, so that unauthorized clients are unable
19356 to send INTRODUCE cells to the service, or even (depending on the
19357 type of authentication) to learn introduction points. This feature
19358 raises the bar for certain kinds of active attacks against hidden
19359 services. Code by Karsten Loesing.
19360 - Relays now store and serve v2 hidden service descriptors by default,
19361 i.e., the new default value for HidServDirectoryV2 is 1. This is
19362 the last step in proposal 114, which aims to make hidden service
19363 lookups more reliable.
19364 - Start work to allow node restrictions to include country codes. The
19365 syntax to exclude nodes in a country with country code XX is
19366 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
19367 refinement to decide what config options should take priority if
19368 you ask to both use a particular node and exclude it.
19369 - Allow ExitNodes list to include IP ranges and country codes, just
19370 like the Exclude*Nodes lists. Patch from Robert Hogan.
19373 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
19374 Tor to fail to start if you had it configured to use a bridge
19375 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
19376 - When extending a circuit to a hidden service directory to upload a
19377 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
19378 requests failed, because the router descriptor had not been
19379 downloaded yet. In these cases, we now wait until the router
19380 descriptor is downloaded, and then retry. Likewise, clients
19381 now skip over a hidden service directory if they don't yet have
19382 its router descriptor, rather than futilely requesting it and
19383 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
19385 - When fetching v0 and v2 rendezvous service descriptors in parallel,
19386 we were failing the whole hidden service request when the v0
19387 descriptor fetch fails, even if the v2 fetch is still pending and
19388 might succeed. Similarly, if the last v2 fetch fails, we were
19389 failing the whole hidden service request even if a v0 fetch is
19390 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
19391 - DNS replies need to have names matching their requests, but
19392 these names should be in the questions section, not necessarily
19393 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
19396 - Update to the "September 1 2008" ip-to-country file.
19397 - Allow ports 465 and 587 in the default exit policy again. We had
19398 rejected them in 0.1.0.15, because back in 2005 they were commonly
19399 misconfigured and ended up as spam targets. We hear they are better
19400 locked down these days.
19401 - Use a lockfile to make sure that two Tor processes are not
19402 simultaneously running with the same datadir.
19403 - Serve the latest v3 networkstatus consensus via the control
19404 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
19405 - Better logging about stability/reliability calculations on directory
19407 - Drop the requirement to have an open dir port for storing and
19408 serving v2 hidden service descriptors.
19409 - Directory authorities now serve a /tor/dbg-stability.txt URL to
19410 help debug WFU and MTBF calculations.
19411 - Implement most of Proposal 152: allow specialized servers to permit
19412 single-hop circuits, and clients to use those servers to build
19413 single-hop circuits when using a specialized controller. Patch
19414 from Josh Albrecht. Resolves feature request 768.
19415 - Add a -p option to tor-resolve for specifying the SOCKS port: some
19416 people find host:port too confusing.
19417 - Make TrackHostExit mappings expire a while after their last use, not
19418 after their creation. Patch from Robert Hogan.
19419 - Provide circuit purposes along with circuit events to the controller.
19422 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
19424 - Fixed some memory leaks -- some quite frequent, some almost
19425 impossible to trigger -- based on results from Coverity.
19426 - When testing for libevent functions, set the LDFLAGS variable
19427 correctly. Found by Riastradh.
19428 - Fix an assertion bug in parsing policy-related options; possible fix
19430 - Catch and report a few more bootstrapping failure cases when Tor
19431 fails to establish a TCP connection. Cleanup on 0.2.1.x.
19432 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
19433 bootstrapping with tunneled directory connections. Bugfix on
19434 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
19435 - When asked to connect to A.B.exit:80, if we don't know the IP for A
19436 and we know that server B rejects most-but-not all connections to
19437 port 80, we would previously reject the connection. Now, we assume
19438 the user knows what they were asking for. Fixes bug 752. Bugfix
19439 on 0.0.9rc5. Diagnosed by BarkerJr.
19440 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
19441 service directories if they have no advertised dir port. Bugfix
19443 - If we overrun our per-second write limits a little, count this as
19444 having used up our write allocation for the second, and choke
19445 outgoing directory writes. Previously, we had only counted this when
19446 we had met our limits precisely. Fixes bug 824. Patch by rovv.
19447 Bugfix on 0.2.0.x (??).
19448 - Avoid a "0 divided by 0" calculation when calculating router uptime
19449 at directory authorities. Bugfix on 0.2.0.8-alpha.
19450 - Make DNS resolved controller events into "CLOSED", not
19451 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
19453 - Fix a bug where an unreachable relay would establish enough
19454 reachability testing circuits to do a bandwidth test -- if
19455 we already have a connection to the middle hop of the testing
19456 circuit, then it could establish the last hop by using the existing
19457 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
19458 circuits no longer use entry guards in 0.2.1.3-alpha.
19459 - If we have correct permissions on $datadir, we complain to stdout
19460 and fail to start. But dangerous permissions on
19461 $datadir/cached-status/ would cause us to open a log and complain
19462 there. Now complain to stdout and fail to start in both cases. Fixes
19463 bug 820, reported by seeess.
19464 - Remove the old v2 directory authority 'lefkada' from the default
19465 list. It has been gone for many months.
19467 o Code simplifications and refactoring:
19468 - Revise the connection_new functions so that a more typesafe variant
19469 exists. This will work better with Coverity, and let us find any
19470 actual mistakes we're making here.
19471 - Refactor unit testing logic so that dmalloc can be used sensibly
19472 with unit tests to check for memory leaks.
19473 - Move all hidden-service related fields from connection and circuit
19474 structure to substructures: this way they won't eat so much memory.
19477 Changes in version 0.2.0.31 - 2008-09-03
19478 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
19479 a big bug we're seeing where in rare cases traffic from one Tor stream
19480 gets mixed into another stream, and fixes a variety of smaller issues.
19483 - Make sure that two circuits can never exist on the same connection
19484 with the same circuit ID, even if one is marked for close. This
19485 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
19486 - Relays now reject risky extend cells: if the extend cell includes
19487 a digest of all zeroes, or asks to extend back to the relay that
19488 sent the extend cell, tear down the circuit. Ideas suggested
19490 - If not enough of our entry guards are available so we add a new
19491 one, we might use the new one even if it overlapped with the
19492 current circuit's exit relay (or its family). Anonymity bugfix
19493 pointed out by rovv.
19496 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
19497 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
19498 - Correctly detect the presence of the linux/netfilter_ipv4.h header
19499 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
19500 - Pick size of default geoip filename string correctly on windows.
19501 Fixes bug 806. Bugfix on 0.2.0.30.
19502 - Make the autoconf script accept the obsolete --with-ssl-dir
19503 option as an alias for the actually-working --with-openssl-dir
19504 option. Fix the help documentation to recommend --with-openssl-dir.
19505 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
19506 - When using the TransPort option on OpenBSD, and using the User
19507 option to change UID and drop privileges, make sure to open
19508 /dev/pf before dropping privileges. Fixes bug 782. Patch from
19509 Christopher Davis. Bugfix on 0.1.2.1-alpha.
19510 - Try to attach connections immediately upon receiving a RENDEZVOUS2
19511 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
19512 on the client side when connecting to a hidden service. Bugfix
19513 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
19514 - When closing an application-side connection because its circuit is
19515 getting torn down, generate the stream event correctly. Bugfix on
19516 0.1.2.x. Anonymous patch.
19519 Changes in version 0.2.1.5-alpha - 2008-08-31
19520 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
19521 in a lot of the infrastructure for adding authorization to hidden
19522 services, lays the groundwork for having clients read their load
19523 balancing information out of the networkstatus consensus rather than
19524 the individual router descriptors, addresses two potential anonymity
19525 issues, and fixes a variety of smaller issues.
19528 - Convert many internal address representations to optionally hold
19530 - Generate and accept IPv6 addresses in many protocol elements.
19531 - Make resolver code handle nameservers located at ipv6 addresses.
19532 - Begin implementation of proposal 121 ("Client authorization for
19533 hidden services"): configure hidden services with client
19534 authorization, publish descriptors for them, and configure
19535 authorization data for hidden services at clients. The next
19536 step is to actually access hidden services that perform client
19538 - More progress toward proposal 141: Network status consensus
19539 documents and votes now contain bandwidth information for each
19540 router and a summary of that router's exit policy. Eventually this
19541 will be used by clients so that they do not have to download every
19542 known descriptor before building circuits.
19544 o Major bugfixes (on 0.2.0.x and before):
19545 - When sending CREATED cells back for a given circuit, use a 64-bit
19546 connection ID to find the right connection, rather than an addr:port
19547 combination. Now that we can have multiple OR connections between
19548 the same ORs, it is no longer possible to use addr:port to uniquely
19549 identify a connection.
19550 - Relays now reject risky extend cells: if the extend cell includes
19551 a digest of all zeroes, or asks to extend back to the relay that
19552 sent the extend cell, tear down the circuit. Ideas suggested
19554 - If not enough of our entry guards are available so we add a new
19555 one, we might use the new one even if it overlapped with the
19556 current circuit's exit relay (or its family). Anonymity bugfix
19557 pointed out by rovv.
19560 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
19561 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
19562 - When using the TransPort option on OpenBSD, and using the User
19563 option to change UID and drop privileges, make sure to open /dev/pf
19564 before dropping privileges. Fixes bug 782. Patch from Christopher
19565 Davis. Bugfix on 0.1.2.1-alpha.
19566 - Correctly detect the presence of the linux/netfilter_ipv4.h header
19567 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
19568 - Add a missing safe_str() call for a debug log message.
19569 - Use 64 bits instead of 32 bits for connection identifiers used with
19570 the controller protocol, to greatly reduce risk of identifier reuse.
19571 - Make the autoconf script accept the obsolete --with-ssl-dir
19572 option as an alias for the actually-working --with-openssl-dir
19573 option. Fix the help documentation to recommend --with-openssl-dir.
19574 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
19577 - Rate-limit too-many-sockets messages: when they happen, they happen
19578 a lot. Resolves bug 748.
19579 - Resist DNS poisoning a little better by making sure that names in
19580 answer sections match.
19581 - Print the SOCKS5 error message string as well as the error code
19582 when a tor-resolve request fails. Patch from Jacob.
19585 Changes in version 0.2.1.4-alpha - 2008-08-04
19586 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
19589 - The address part of exit policies was not correctly written
19590 to router descriptors. This generated router descriptors that failed
19591 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
19593 - Tor triggered a false assert when extending a circuit to a relay
19594 but we already have a connection open to that relay. Noticed by
19595 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
19598 - Fix a hidden service logging bug: in some edge cases, the router
19599 descriptor of a previously picked introduction point becomes
19600 obsolete and we need to give up on it rather than continually
19601 complaining that it has become obsolete. Observed by xiando. Bugfix
19604 o Removed features:
19605 - Take out the TestVia config option, since it was a workaround for
19606 a bug that was fixed in Tor 0.1.1.21.
19609 Changes in version 0.2.1.3-alpha - 2008-08-03
19610 Tor 0.2.1.3-alpha implements most of the pieces to prevent
19611 infinite-length circuit attacks (see proposal 110); fixes a bug that
19612 might cause exit relays to corrupt streams they send back; allows
19613 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
19614 ExcludeExitNodes config options; and fixes a big pile of bugs.
19616 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
19617 - Send a bootstrap problem "warn" event on the first problem if the
19618 reason is NO_ROUTE (that is, our network is down).
19621 - Implement most of proposal 110: The first K cells to be sent
19622 along a circuit are marked as special "early" cells; only K "early"
19623 cells will be allowed. Once this code is universal, we can block
19624 certain kinds of DOS attack by requiring that EXTEND commands must
19625 be sent using an "early" cell.
19628 - Try to attach connections immediately upon receiving a RENDEZVOUS2
19629 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
19630 on the client side when connecting to a hidden service. Bugfix
19631 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
19632 - Ensure that two circuits can never exist on the same connection
19633 with the same circuit ID, even if one is marked for close. This
19634 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
19637 - When relays do their initial bandwidth measurement, don't limit
19638 to just our entry guards for the test circuits. Otherwise we tend
19639 to have multiple test circuits going through a single entry guard,
19640 which makes our bandwidth test less accurate. Fixes part of bug 654;
19641 patch contributed by Josh Albrecht.
19642 - Add an ExcludeExitNodes option so users can list a set of nodes
19643 that should be be excluded from the exit node position, but
19644 allowed elsewhere. Implements proposal 151.
19645 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
19646 ExcludeNodes and ExcludeExitNodes lists.
19647 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
19648 be more efficient. Formerly it was quadratic in the number of
19649 servers; now it should be linear. Fixes bug 509.
19650 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
19651 and n_conn_id_digest fields into a separate structure that's
19652 only needed when the circuit has not yet attached to an n_conn.
19655 - Change the contrib/tor.logrotate script so it makes the new
19656 logs as "_tor:_tor" rather than the default, which is generally
19657 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
19658 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
19659 warnings (occasionally), but it can also cause the compiler to
19660 eliminate error-checking code. Suggested by Peter Gutmann.
19661 - When a hidden service is giving up on an introduction point candidate
19662 that was not included in the last published rendezvous descriptor,
19663 don't reschedule publication of the next descriptor. Fixes bug 763.
19665 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
19666 HiddenServiceExcludeNodes as obsolete: they never worked properly,
19667 and nobody claims to be using them. Fixes bug 754. Bugfix on
19668 0.1.0.1-rc. Patch from Christian Wilms.
19669 - Fix a small alignment and memory-wasting bug on buffer chunks.
19672 o Minor bugfixes (controller):
19673 - When closing an application-side connection because its circuit
19674 is getting torn down, generate the stream event correctly.
19675 Bugfix on 0.1.2.x. Anonymous patch.
19677 o Removed features:
19678 - Remove all backward-compatibility code to support relays running
19679 versions of Tor so old that they no longer work at all on the
19683 Changes in version 0.2.0.30 - 2008-07-15
19685 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
19686 warnings (occasionally), but it can also cause the compiler to
19687 eliminate error-checking code. Suggested by Peter Gutmann.
19690 Changes in version 0.2.0.29-rc - 2008-07-08
19691 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
19692 hidden-service performance bugs, and fixes a bunch of smaller bugs.
19695 - If you have more than one bridge but don't know their keys,
19696 you would only launch a request for the descriptor of the first one
19697 on your list. (Tor considered launching requests for the others, but
19698 found that it already had a connection on the way for $0000...0000
19699 so it didn't open another.) Bugfix on 0.2.0.x.
19700 - If you have more than one bridge but don't know their keys, and the
19701 connection to one of the bridges failed, you would cancel all
19702 pending bridge connections. (After all, they all have the same
19703 digest.) Bugfix on 0.2.0.x.
19704 - When a hidden service was trying to establish an introduction point,
19705 and Tor had built circuits preemptively for such purposes, we
19706 were ignoring all the preemptive circuits and launching a new one
19707 instead. Bugfix on 0.2.0.14-alpha.
19708 - When a hidden service was trying to establish an introduction point,
19709 and Tor *did* manage to reuse one of the preemptively built
19710 circuits, it didn't correctly remember which one it used,
19711 so it asked for another one soon after, until there were no
19712 more preemptive circuits, at which point it launched one from
19713 scratch. Bugfix on 0.0.9.x.
19714 - Make directory servers include the X-Your-Address-Is: http header in
19715 their responses even for begin_dir conns. Now clients who only
19716 ever use begin_dir connections still have a way to learn their IP
19717 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
19720 - Fix a macro/CPP interaction that was confusing some compilers:
19721 some GCCs don't like #if/#endif pairs inside macro arguments.
19723 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
19724 Fixes bug 704; fix from Steven Murdoch.
19725 - When opening /dev/null in finish_daemonize(), do not pass the
19726 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
19727 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
19728 - Correctly detect transparent proxy support on Linux hosts that
19729 require in.h to be included before netfilter_ipv4.h. Patch
19731 - Disallow session resumption attempts during the renegotiation
19732 stage of the v2 handshake protocol. Clients should never be trying
19733 session resumption at this point, but apparently some did, in
19734 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
19735 found by Geoff Goodell.
19738 Changes in version 0.2.1.2-alpha - 2008-06-20
19739 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
19740 make it easier to set up your own private Tor network; fixes several
19741 big bugs with using more than one bridge relay; fixes a big bug with
19742 offering hidden services quickly after Tor starts; and uses a better
19743 API for reporting potential bootstrapping problems to the controller.
19746 - New TestingTorNetwork config option to allow adjustment of
19747 previously constant values that, while reasonable, could slow
19748 bootstrapping. Implements proposal 135. Patch from Karsten.
19751 - If you have more than one bridge but don't know their digests,
19752 you would only learn a request for the descriptor of the first one
19753 on your list. (Tor considered launching requests for the others, but
19754 found that it already had a connection on the way for $0000...0000
19755 so it didn't open another.) Bugfix on 0.2.0.x.
19756 - If you have more than one bridge but don't know their digests,
19757 and the connection to one of the bridges failed, you would cancel
19758 all pending bridge connections. (After all, they all have the
19759 same digest.) Bugfix on 0.2.0.x.
19760 - When establishing a hidden service, introduction points that
19761 originate from cannibalized circuits are completely ignored and not
19762 included in rendezvous service descriptors. This might be another
19763 reason for delay in making a hidden service available. Bugfix
19764 from long ago (0.0.9.x?)
19767 - Allow OpenSSL to use dynamic locks if it wants.
19768 - When building a consensus, do not include routers that are down.
19769 This will cut down 30% to 40% on consensus size. Implements
19771 - In directory authorities' approved-routers files, allow
19772 fingerprints with or without space.
19773 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
19774 controller can query our current bootstrap state in case it attaches
19775 partway through and wants to catch up.
19776 - Send an initial "Starting" bootstrap status event, so we have a
19777 state to start out in.
19780 - Asking for a conditional consensus at .../consensus/<fingerprints>
19781 would crash a dirserver if it did not already have a
19782 consensus. Bugfix on 0.2.1.1-alpha.
19783 - Clean up some macro/CPP interactions: some GCC versions don't like
19784 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
19787 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
19788 - Directory authorities shouldn't complain about bootstrapping
19789 problems just because they do a lot of reachability testing and
19790 some of the connection attempts fail.
19791 - Start sending "count" and "recommendation" key/value pairs in
19792 bootstrap problem status events, so the controller can hear about
19793 problems even before Tor decides they're worth reporting for sure.
19794 - If you're using bridges, generate "bootstrap problem" warnings
19795 as soon as you run out of working bridges, rather than waiting
19796 for ten failures -- which will never happen if you have less than
19798 - If we close our OR connection because there's been a circuit
19799 pending on it for too long, we were telling our bootstrap status
19800 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
19803 Changes in version 0.2.1.1-alpha - 2008-06-13
19804 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
19805 were making the Tor process bloat especially on Linux; makes our TLS
19806 handshake blend in better; sends "bootstrap phase" status events to
19807 the controller, so it can keep the user informed of progress (and
19808 problems) fetching directory information and establishing circuits;
19809 and adds a variety of smaller features.
19812 - More work on making our TLS handshake blend in: modify the list
19813 of ciphers advertised by OpenSSL in client mode to even more
19814 closely resemble a common web browser. We cheat a little so that
19815 we can advertise ciphers that the locally installed OpenSSL doesn't
19817 - Start sending "bootstrap phase" status events to the controller,
19818 so it can keep the user informed of progress fetching directory
19819 information and establishing circuits. Also inform the controller
19820 if we think we're stuck at a particular bootstrap phase. Implements
19822 - Resume using OpenSSL's RAND_poll() for better (and more portable)
19823 cross-platform entropy collection again. We used to use it, then
19824 stopped using it because of a bug that could crash systems that
19825 called RAND_poll when they had a lot of fds open. It looks like the
19826 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
19827 at startup, and to call RAND_poll() when we reseed later only if
19828 we have a non-buggy OpenSSL version.
19831 - When we choose to abandon a new entry guard because we think our
19832 older ones might be better, close any circuits pending on that
19833 new entry guard connection. This fix should make us recover much
19834 faster when our network is down and then comes back. Bugfix on
19835 0.1.2.8-beta; found by lodger.
19837 o Memory fixes and improvements:
19838 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
19839 to avoid unused RAM in buffer chunks and memory pools.
19840 - Speed up parsing and cut down on memory fragmentation by using
19841 stack-style allocations for parsing directory objects. Previously,
19842 this accounted for over 40% of allocations from within Tor's code
19843 on a typical directory cache.
19844 - Use a Bloom filter rather than a digest-based set to track which
19845 descriptors we need to keep around when we're cleaning out old
19846 router descriptors. This speeds up the computation significantly,
19847 and may reduce fragmentation.
19848 - Reduce the default smartlist size from 32 to 16; it turns out that
19849 most smartlists hold around 8-12 elements tops.
19850 - Make dumpstats() log the fullness and size of openssl-internal
19852 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
19853 patch to their OpenSSL, turn it on to save memory on servers. This
19854 patch will (with any luck) get included in a mainline distribution
19856 - Never use OpenSSL compression: it wastes RAM and CPU trying to
19857 compress cells, which are basically all encrypted, compressed,
19861 - Stop reloading the router list from disk for no reason when we
19862 run out of reachable directory mirrors. Once upon a time reloading
19863 it would set the 'is_running' flag back to 1 for them. It hasn't
19864 done that for a long time.
19865 - In very rare situations new hidden service descriptors were
19866 published earlier than 30 seconds after the last change to the
19867 service. (We currently think that a hidden service descriptor
19868 that's been stable for 30 seconds is worth publishing.)
19871 - Allow separate log levels to be configured for different logging
19872 domains. For example, this allows one to log all notices, warnings,
19873 or errors, plus all memory management messages of level debug or
19874 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
19875 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
19876 and stop using a warning that had become unfixably verbose under
19878 - New --hush command-line option similar to --quiet. While --quiet
19879 disables all logging to the console on startup, --hush limits the
19880 output to messages of warning and error severity.
19881 - Servers support a new URL scheme for consensus downloads that
19882 allows the client to specify which authorities are trusted.
19883 The server then only sends the consensus if the client will trust
19884 it. Otherwise a 404 error is sent back. Clients use this
19885 new scheme when the server supports it (meaning it's running
19886 0.2.1.1-alpha or later). Implements proposal 134.
19887 - New configure/torrc options (--enable-geoip-stats,
19888 DirRecordUsageByCountry) to record how many IPs we've served
19889 directory info to in each country code, how many status documents
19890 total we've sent to each country code, and what share of the total
19891 directory requests we should expect to see.
19892 - Use the TLS1 hostname extension to more closely resemble browser
19894 - Lots of new unit tests.
19895 - Add a macro to implement the common pattern of iterating through
19896 two parallel lists in lockstep.
19899 Changes in version 0.2.0.28-rc - 2008-06-13
19900 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
19901 performance bug, and fixes a bunch of smaller bugs.
19904 - Fix a bug where, when we were choosing the 'end stream reason' to
19905 put in our relay end cell that we send to the exit relay, Tor
19906 clients on Windows were sometimes sending the wrong 'reason'. The
19907 anonymity problem is that exit relays may be able to guess whether
19908 the client is running Windows, thus helping partition the anonymity
19909 set. Down the road we should stop sending reasons to exit relays,
19910 or otherwise prevent future versions of this bug.
19913 - While setting up a hidden service, some valid introduction circuits
19914 were overlooked and abandoned. This might be the reason for
19915 the long delay in making a hidden service available. Bugfix on
19919 - Update to the "June 9 2008" ip-to-country file.
19920 - Run 'make test' as part of 'make dist', so we stop releasing so
19921 many development snapshots that fail their unit tests.
19924 - When we're checking if we have enough dir info for each relay
19925 to begin establishing circuits, make sure that we actually have
19926 the descriptor listed in the consensus, not just any descriptor.
19928 - Bridge relays no longer print "xx=0" in their extrainfo document
19929 for every single country code in the geoip db. Bugfix on
19931 - Only warn when we fail to load the geoip file if we were planning to
19932 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
19933 - If we change our MaxAdvertisedBandwidth and then reload torrc,
19934 Tor won't realize it should publish a new relay descriptor. Fixes
19935 bug 688, reported by mfr. Bugfix on 0.1.2.x.
19936 - When we haven't had any application requests lately, don't bother
19937 logging that we have expired a bunch of descriptors. Bugfix
19939 - Make relay cells written on a connection count as non-padding when
19940 tracking how long a connection has been in use. Bugfix on
19941 0.2.0.1-alpha. Spotted by lodger.
19942 - Fix unit tests in 0.2.0.27-rc.
19943 - Fix compile on Windows.
19946 Changes in version 0.2.0.27-rc - 2008-06-03
19947 Tor 0.2.0.27-rc adds a few features we left out of the earlier
19948 release candidates. In particular, we now include an IP-to-country
19949 GeoIP database, so controllers can easily look up what country a
19950 given relay is in, and so bridge relays can give us some sanitized
19951 summaries about which countries are making use of bridges. (See proposal
19952 126-geoip-fetching.txt for details.)
19955 - Include an IP-to-country GeoIP file in the tarball, so bridge
19956 relays can report sanitized summaries of the usage they're seeing.
19959 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
19960 Robert Hogan. Fixes the first part of bug 681.
19961 - Make bridge authorities never serve extrainfo docs.
19962 - Add support to detect Libevent versions in the 1.4.x series
19964 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
19965 - Include a new contrib/tor-exit-notice.html file that exit relay
19966 operators can put on their website to help reduce abuse queries.
19969 - When tunneling an encrypted directory connection, and its first
19970 circuit fails, do not leave it unattached and ask the controller
19971 to deal. Fixes the second part of bug 681.
19972 - Make bridge authorities correctly expire old extrainfo documents
19976 Changes in version 0.2.0.26-rc - 2008-05-13
19977 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
19978 in Debian's OpenSSL packages. All users running any 0.2.0.x version
19979 should upgrade, whether they're running Debian or not.
19981 o Major security fixes:
19982 - Use new V3 directory authority keys on the tor26, gabelmoo, and
19983 moria1 V3 directory authorities. The old keys were generated with
19984 a vulnerable version of Debian's OpenSSL package, and must be
19985 considered compromised. Other authorities' keys were not generated
19986 with an affected version of OpenSSL.
19989 - List authority signatures as "unrecognized" based on DirServer
19990 lines, not on cert cache. Bugfix on 0.2.0.x.
19993 - Add a new V3AuthUseLegacyKey option to make it easier for
19994 authorities to change their identity keys if they have to.
19997 Changes in version 0.2.0.25-rc - 2008-04-23
19998 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
20001 - Remember to initialize threading before initializing logging.
20002 Otherwise, many BSD-family implementations will crash hard on
20003 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
20006 - Authorities correctly free policies on bad servers on
20007 exit. Fixes bug 672. Bugfix on 0.2.0.x.
20010 Changes in version 0.2.0.24-rc - 2008-04-22
20011 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
20012 v3 directory authority, makes relays with dynamic IP addresses and no
20013 DirPort notice more quickly when their IP address changes, fixes a few
20014 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
20016 o New directory authorities:
20017 - Take lefkada out of the list of v3 directory authorities, since
20018 it has been down for months.
20019 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
20023 - Detect address changes more quickly on non-directory mirror
20024 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
20026 o Minor features (security):
20027 - Reject requests for reverse-dns lookup of names that are in
20028 a private address space. Patch from lodger.
20029 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
20032 o Minor bugfixes (crashes):
20033 - Avoid a rare assert that can trigger when Tor doesn't have much
20034 directory information yet and it tries to fetch a v2 hidden
20035 service descriptor. Fixes bug 651, reported by nwf.
20036 - Initialize log mutex before initializing dmalloc. Otherwise,
20037 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
20038 - Use recursive pthread mutexes in order to avoid deadlock when
20039 logging debug-level messages to a controller. Bug spotted by nwf,
20040 bugfix on 0.2.0.16-alpha.
20042 o Minor bugfixes (resource management):
20043 - Keep address policies from leaking memory: start their refcount
20044 at 1, not 2. Bugfix on 0.2.0.16-alpha.
20045 - Free authority certificates on exit, so they don't look like memory
20046 leaks. Bugfix on 0.2.0.19-alpha.
20047 - Free static hashtables for policy maps and for TLS connections on
20048 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
20049 - Avoid allocating extra space when computing consensuses on 64-bit
20050 platforms. Bug spotted by aakova.
20052 o Minor bugfixes (misc):
20053 - Do not read the configuration file when we've only been told to
20054 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
20055 based on patch from Sebastian Hahn.
20056 - Exit relays that are used as a client can now reach themselves
20057 using the .exit notation, rather than just launching an infinite
20058 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
20059 - When attempting to open a logfile fails, tell us why.
20060 - Fix a dumb bug that was preventing us from knowing that we should
20061 preemptively build circuits to handle expected directory requests.
20062 Fixes bug 660. Bugfix on 0.1.2.x.
20063 - Warn less verbosely about clock skew from netinfo cells from
20064 untrusted sources. Fixes bug 663.
20065 - Make controller stream events for DNS requests more consistent,
20066 by adding "new stream" events for DNS requests, and removing
20067 spurious "stream closed" events" for cached reverse resolves.
20068 Patch from mwenge. Fixes bug 646.
20069 - Correctly notify one-hop connections when a circuit build has
20070 failed. Possible fix for bug 669. Found by lodger.
20073 Changes in version 0.2.0.23-rc - 2008-03-24
20074 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
20075 makes bootstrapping faster if the first directory mirror you contact
20076 is down. The bundles also include the new Vidalia 0.1.2 release.
20079 - When a tunneled directory request is made to a directory server
20080 that's down, notice after 30 seconds rather than 120 seconds. Also,
20081 fail any begindir streams that are pending on it, so they can
20082 retry elsewhere. This was causing multi-minute delays on bootstrap.
20085 Changes in version 0.2.0.22-rc - 2008-03-18
20086 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
20087 enables encrypted directory connections by default for non-relays, fixes
20088 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
20089 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
20092 - Enable encrypted directory connections by default for non-relays,
20093 so censor tools that block Tor directory connections based on their
20094 plaintext patterns will no longer work. This means Tor works in
20095 certain censored countries by default again.
20098 - Make sure servers always request certificates from clients during
20099 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
20100 - Do not enter a CPU-eating loop when a connection is closed in
20101 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
20102 diagnosed by lodger; bugfix on 0.2.0.20-rc.
20103 - Fix assertion failure that could occur when a blocked circuit
20104 became unblocked, and it had pending client DNS requests. Bugfix
20105 on 0.2.0.1-alpha. Fixes bug 632.
20107 o Minor bugfixes (on 0.1.2.x):
20108 - Generate "STATUS_SERVER" events rather than misspelled
20109 "STATUS_SEVER" events. Caught by mwenge.
20110 - When counting the number of bytes written on a TLS connection,
20111 look at the BIO actually used for writing to the network, not
20112 at the BIO used (sometimes) to buffer data for the network.
20113 Looking at different BIOs could result in write counts on the
20114 order of ULONG_MAX. Fixes bug 614.
20115 - On Windows, correctly detect errors when listing the contents of
20116 a directory. Fix from lodger.
20118 o Minor bugfixes (on 0.2.0.x):
20119 - Downgrade "sslv3 alert handshake failure" message to INFO.
20120 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
20121 left BandwidthRate and BandwidthBurst at the default, we would be
20122 silently limited by those defaults. Now raise them to match the
20123 RelayBandwidth* values.
20124 - Fix the SVK version detection logic to work correctly on a branch.
20125 - Make --enable-openbsd-malloc work correctly on Linux with alpha
20126 CPUs. Fixes bug 625.
20127 - Logging functions now check that the passed severity is sane.
20128 - Use proper log levels in the testsuite call of
20129 get_interface_address6().
20130 - When using a nonstandard malloc, do not use the platform values for
20131 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
20132 - Make the openbsd malloc code use 8k pages on alpha CPUs and
20134 - Detect mismatched page sizes when using --enable-openbsd-malloc.
20135 - Avoid double-marked-for-close warning when certain kinds of invalid
20136 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
20137 for bug 617. Bugfix on 0.2.0.1-alpha.
20138 - Make sure that the "NULL-means-reject *:*" convention is followed by
20139 all the policy manipulation functions, avoiding some possible crash
20140 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
20141 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
20142 actually works, and doesn't warn about every single reverse lookup.
20143 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
20146 - Only log guard node status when guard node status has changed.
20147 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
20148 make "INFO" 75% less verbose.
20151 Changes in version 0.2.0.21-rc - 2008-03-02
20152 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
20153 makes Tor work well with Vidalia again, fixes a rare assert bug,
20154 and fixes a pair of more minor bugs. The bundles also include Vidalia
20155 0.1.0 and Torbutton 1.1.16.
20158 - The control port should declare that it requires password auth
20159 when HashedControlSessionPassword is set too. Patch from Matt Edman;
20160 bugfix on 0.2.0.20-rc. Fixes bug 615.
20161 - Downgrade assert in connection_buckets_decrement() to a log message.
20162 This may help us solve bug 614, and in any case will make its
20163 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
20164 - We were sometimes miscounting the number of bytes read from the
20165 network, causing our rate limiting to not be followed exactly.
20166 Bugfix on 0.2.0.16-alpha. Reported by lodger.
20169 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
20170 OpenSSL versions should have been working fine. Diagnosis and patch
20171 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
20172 Bugfix on 0.2.0.20-rc.
20175 Changes in version 0.2.0.20-rc - 2008-02-24
20176 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
20177 makes more progress towards normalizing Tor's TLS handshake, makes
20178 hidden services work better again, helps relays bootstrap if they don't
20179 know their IP address, adds optional support for linking in openbsd's
20180 allocator or tcmalloc, allows really fast relays to scale past 15000
20181 sockets, and fixes a bunch of minor bugs reported by Veracode.
20184 - Enable the revised TLS handshake based on the one designed by
20185 Steven Murdoch in proposal 124, as revised in proposal 130. It
20186 includes version negotiation for OR connections as described in
20187 proposal 105. The new handshake is meant to be harder for censors
20188 to fingerprint, and it adds the ability to detect certain kinds of
20189 man-in-the-middle traffic analysis attacks. The version negotiation
20190 feature will allow us to improve Tor's link protocol more safely
20192 - Choose which bridge to use proportional to its advertised bandwidth,
20193 rather than uniformly at random. This should speed up Tor for
20194 bridge users. Also do this for people who set StrictEntryNodes.
20195 - When a TrackHostExits-chosen exit fails too many times in a row,
20196 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
20199 - Resolved problems with (re-)fetching hidden service descriptors.
20200 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
20201 and 0.2.0.19-alpha.
20202 - If we only ever used Tor for hidden service lookups or posts, we
20203 would stop building circuits and start refusing connections after
20204 24 hours, since we falsely believed that Tor was dormant. Reported
20205 by nwf; bugfix on 0.1.2.x.
20206 - Servers that don't know their own IP address should go to the
20207 authorities for their first directory fetch, even if their DirPort
20208 is off or if they don't know they're reachable yet. This will help
20209 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
20210 - When counting the number of open sockets, count not only the number
20211 of sockets we have received from the socket() call, but also
20212 the number we've gotten from accept() and socketpair(). This bug
20213 made us fail to count all sockets that we were using for incoming
20214 connections. Bugfix on 0.2.0.x.
20215 - Fix code used to find strings within buffers, when those strings
20216 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
20217 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
20218 - Add a new __HashedControlSessionPassword option for controllers
20219 to use for one-off session password hashes that shouldn't get
20220 saved to disk by SAVECONF --- Vidalia users were accumulating a
20221 pile of HashedControlPassword lines in their torrc files, one for
20222 each time they had restarted Tor and then clicked Save. Make Tor
20223 automatically convert "HashedControlPassword" to this new option but
20224 only when it's given on the command line. Partial fix for bug 586.
20226 o Minor features (performance):
20227 - Tune parameters for cell pool allocation to minimize amount of
20229 - Add OpenBSD malloc code from phk as an optional malloc
20230 replacement on Linux: some glibc libraries do very poorly
20231 with Tor's memory allocation patterns. Pass
20232 --enable-openbsd-malloc to get the replacement malloc code.
20233 - Add a --with-tcmalloc option to the configure script to link
20234 against tcmalloc (if present). Does not yet search for
20235 non-system include paths.
20236 - Stop imposing an arbitrary maximum on the number of file descriptors
20237 used for busy servers. Bug reported by Olaf Selke; patch from
20240 o Minor features (other):
20241 - When SafeLogging is disabled, log addresses along with all TLS
20243 - When building with --enable-gcc-warnings, check for whether Apple's
20244 warning "-Wshorten-64-to-32" is available.
20245 - Add a --passphrase-fd argument to the tor-gencert command for
20248 o Minor bugfixes (memory leaks and code problems):
20249 - We were leaking a file descriptor if Tor started with a zero-length
20250 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
20251 - Detect size overflow in zlib code. Reported by Justin Ferguson and
20253 - We were comparing the raw BridgePassword entry with a base64'ed
20254 version of it, when handling a "/tor/networkstatus-bridges"
20255 directory request. Now compare correctly. Noticed by Veracode.
20256 - Recover from bad tracked-since value in MTBF-history file.
20257 Should fix bug 537.
20258 - Alter the code that tries to recover from unhandled write
20259 errors, to not try to flush onto a socket that's given us
20260 unhandled errors. Bugfix on 0.1.2.x.
20261 - Make Unix controlsockets work correctly on OpenBSD. Patch from
20262 tup. Bugfix on 0.2.0.3-alpha.
20264 o Minor bugfixes (other):
20265 - If we have an extra-info document for our server, always make
20266 it available on the control port, even if we haven't gotten
20267 a copy of it from an authority yet. Patch from mwenge.
20268 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
20269 - Directory mirrors no longer include a guess at the client's IP
20270 address if the connection appears to be coming from the same /24
20271 network; it was producing too many wrong guesses.
20272 - Make the new hidden service code respect the SafeLogging setting.
20273 Bugfix on 0.2.0.x. Patch from Karsten.
20274 - When starting as an authority, do not overwrite all certificates
20275 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
20276 - If we're trying to flush the last bytes on a connection (for
20277 example, when answering a directory request), reset the
20278 time-to-give-up timeout every time we manage to write something
20279 on the socket. Bugfix on 0.1.2.x.
20280 - Change the behavior of "getinfo status/good-server-descriptor"
20281 so it doesn't return failure when any authority disappears.
20282 - Even though the man page said that "TrackHostExits ." should
20283 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
20284 - Report TLS "zero return" case as a "clean close" and "IO error"
20285 as a "close". Stop calling closes "unexpected closes": existing
20286 Tors don't use SSL_close(), so having a connection close without
20287 the TLS shutdown handshake is hardly unexpected.
20288 - Send NAMESERVER_STATUS messages for a single failed nameserver
20291 o Code simplifications and refactoring:
20292 - Remove the tor_strpartition function: its logic was confused,
20293 and it was only used for one thing that could be implemented far
20297 Changes in version 0.2.0.19-alpha - 2008-02-09
20298 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
20299 handshake, makes path selection for relays more secure and IP address
20300 guessing more robust, and generally fixes a lot of bugs in preparation
20301 for calling the 0.2.0 branch stable.
20304 - Do not include recognizeable strings in the commonname part of
20305 Tor's x509 certificates.
20308 - If we're a relay, avoid picking ourselves as an introduction point,
20309 a rendezvous point, or as the final hop for internal circuits. Bug
20310 reported by taranis and lodger. Bugfix on 0.1.2.x.
20311 - Patch from "Andrew S. Lists" to catch when we contact a directory
20312 mirror at IP address X and he says we look like we're coming from
20313 IP address X. Bugfix on 0.1.2.x.
20315 o Minor features (security):
20316 - Be more paranoid about overwriting sensitive memory on free(),
20317 as a defensive programming tactic to ensure forward secrecy.
20319 o Minor features (directory authority):
20320 - Actually validate the options passed to AuthDirReject,
20321 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
20322 - Reject router descriptors with out-of-range bandwidthcapacity or
20323 bandwidthburst values.
20325 o Minor features (controller):
20326 - Reject controller commands over 1MB in length. This keeps rogue
20327 processes from running us out of memory.
20329 o Minor features (misc):
20330 - Give more descriptive well-formedness errors for out-of-range
20331 hidden service descriptor/protocol versions.
20332 - Make memory debugging information describe more about history
20333 of cell allocation, so we can help reduce our memory use.
20335 o Deprecated features (controller):
20336 - The status/version/num-versioning and status/version/num-concurring
20337 GETINFO options are no longer useful in the v3 directory protocol:
20338 treat them as deprecated, and warn when they're used.
20341 - When our consensus networkstatus has been expired for a while, stop
20342 being willing to build circuits using it. Fixes bug 401. Bugfix
20344 - Directory caches now fetch certificates from all authorities
20345 listed in a networkstatus consensus, even when they do not
20346 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
20347 - When connecting to a bridge without specifying its key, insert
20348 the connection into the identity-to-connection map as soon as
20349 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
20350 - Detect versions of OS X where malloc_good_size() is present in the
20351 library but never actually declared. Resolves bug 587. Bugfix
20353 - Stop incorrectly truncating zlib responses to directory authority
20354 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
20355 - Stop recommending that every server operator send mail to tor-ops.
20356 Resolves bug 597. Bugfix on 0.1.2.x.
20357 - Don't trigger an assert if we start a directory authority with a
20358 private IP address (like 127.0.0.1).
20359 - Avoid possible failures when generating a directory with routers
20360 with over-long versions strings, or too many flags set. Bugfix
20362 - If an attempt to launch a DNS resolve request over the control
20363 port fails because we have overrun the limit on the number of
20364 connections, tell the controller that the request has failed.
20365 - Avoid using too little bandwidth when our clock skips a few
20366 seconds. Bugfix on 0.1.2.x.
20367 - Fix shell error when warning about missing packages in configure
20368 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
20369 - Do not become confused when receiving a spurious VERSIONS-like
20370 cell from a confused v1 client. Bugfix on 0.2.0.x.
20371 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
20372 introduction points for a hidden service have failed. Patch from
20373 Karsten Loesing. Bugfix on 0.2.0.x.
20375 o Code simplifications and refactoring:
20376 - Remove some needless generality from cpuworker code, for improved
20378 - Stop overloading the circuit_t.onionskin field for both "onionskin
20379 from a CREATE cell that we are waiting for a cpuworker to be
20380 assigned" and "onionskin from an EXTEND cell that we are going to
20381 send to an OR as soon as we are connected". Might help with bug 600.
20382 - Add an in-place version of aes_crypt() so that we can avoid doing a
20383 needless memcpy() call on each cell payload.
20386 Changes in version 0.2.0.18-alpha - 2008-01-25
20387 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
20388 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
20389 that can warn or reject connections to ports generally associated with
20390 vulnerable-plaintext protocols.
20392 o New directory authorities:
20393 - Set up dannenberg (run by CCC) as the sixth v3 directory
20397 - Fix a major memory leak when attempting to use the v2 TLS
20398 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
20399 - We accidentally enabled the under-development v2 TLS handshake
20400 code, which was causing log entries like "TLS error while
20401 renegotiating handshake". Disable it again. Resolves bug 590.
20402 - We were computing the wrong Content-Length: header for directory
20403 responses that need to be compressed on the fly, causing clients
20404 asking for those items to always fail. Bugfix on 0.2.0.x; partially
20408 - Avoid going directly to the directory authorities even if you're a
20409 relay, if you haven't found yourself reachable yet or if you've
20410 decided not to advertise your dirport yet. Addresses bug 556.
20411 - If we've gone 12 hours since our last bandwidth check, and we
20412 estimate we have less than 50KB bandwidth capacity but we could
20413 handle more, do another bandwidth test.
20414 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
20415 Tor can warn and/or refuse connections to ports commonly used with
20416 vulnerable-plaintext protocols. Currently we warn on ports 23,
20417 109, 110, and 143, but we don't reject any.
20420 - When we setconf ClientOnly to 1, close any current OR and Dir
20421 listeners. Reported by mwenge.
20422 - When we get a consensus that's been signed by more people than
20423 we expect, don't log about it; it's not a big deal. Reported
20427 - Don't answer "/tor/networkstatus-bridges" directory requests if
20428 the request isn't encrypted.
20429 - Make "ClientOnly 1" config option disable directory ports too.
20430 - Patches from Karsten Loesing to make v2 hidden services more
20431 robust: work even when there aren't enough HSDir relays available;
20432 retry when a v2 rend desc fetch fails; but don't retry if we
20433 already have a usable v0 rend desc.
20436 Changes in version 0.2.0.17-alpha - 2008-01-17
20437 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
20440 - Make the tor-gencert man page get included correctly in the tarball.
20443 Changes in version 0.2.0.16-alpha - 2008-01-17
20444 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
20445 Loesing, and generally cleans up a lot of features and minor bugs.
20447 o New directory authorities:
20448 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
20451 o Major performance improvements:
20452 - Switch our old ring buffer implementation for one more like that
20453 used by free Unix kernels. The wasted space in a buffer with 1mb
20454 of data will now be more like 8k than 1mb. The new implementation
20455 also avoids realloc();realloc(); patterns that can contribute to
20456 memory fragmentation.
20459 - Configuration files now accept C-style strings as values. This
20460 helps encode characters not allowed in the current configuration
20461 file format, such as newline or #. Addresses bug 557.
20462 - Although we fixed bug 539 (where servers would send HTTP status 503
20463 responses _and_ send a body too), there are still servers out
20464 there that haven't upgraded. Therefore, make clients parse such
20465 bodies when they receive them.
20466 - When we're not serving v2 directory information, there is no reason
20467 to actually keep any around. Remove the obsolete files and directory
20468 on startup if they are very old and we aren't going to serve them.
20470 o Minor performance improvements:
20471 - Reference-count and share copies of address policy entries; only 5%
20472 of them were actually distinct.
20473 - Never walk through the list of logs if we know that no log is
20474 interested in a given message.
20477 - When an authority has not signed a consensus, do not try to
20478 download a nonexistent "certificate with key 00000000". Bugfix
20479 on 0.2.0.x. Fixes bug 569.
20480 - Fix a rare assert error when we're closing one of our threads:
20481 use a mutex to protect the list of logs, so we never write to the
20482 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
20483 bug 575, which is kind of the revenge of bug 222.
20484 - Patch from Karsten Loesing to complain less at both the client
20485 and the relay when a relay used to have the HSDir flag but doesn't
20486 anymore, and we try to upload a hidden service descriptor.
20487 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
20489 - Do not try to download missing certificates until we have tried
20490 to check our fallback consensus. Fixes bug 583.
20491 - Make bridges round reported GeoIP stats info up to the nearest
20492 estimate, not down. Now we can distinguish between "0 people from
20493 this country" and "1 person from this country".
20494 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
20495 - Avoid possible segfault if key generation fails in
20496 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
20497 - Avoid segfault in the case where a badly behaved v2 versioning
20498 directory sends a signed networkstatus with missing client-versions.
20500 - Avoid segfaults on certain complex invocations of
20501 router_get_by_hexdigest(). Bugfix on 0.1.2.
20502 - Correct bad index on array access in parse_http_time(). Bugfix
20504 - Fix possible bug in vote generation when server versions are present
20505 but client versions are not.
20506 - Fix rare bug on REDIRECTSTREAM control command when called with no
20507 port set: it could erroneously report an error when none had
20509 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
20510 compressing large objects and find ourselves with more than 4k
20511 left over. Bugfix on 0.2.0.
20512 - Fix a small memory leak when setting up a hidden service.
20513 - Fix a few memory leaks that could in theory happen under bizarre
20515 - Fix an assert if we post a general-purpose descriptor via the
20516 control port but that descriptor isn't mentioned in our current
20517 network consensus. Bug reported by Jon McLachlan; bugfix on
20520 o Minor features (controller):
20521 - Get NS events working again. Patch from tup.
20522 - The GETCONF command now escapes and quotes configuration values
20523 that don't otherwise fit into the torrc file.
20524 - The SETCONF command now handles quoted values correctly.
20526 o Minor features (directory authorities):
20527 - New configuration options to override default maximum number of
20528 servers allowed on a single IP address. This is important for
20529 running a test network on a single host.
20530 - Actually implement the -s option to tor-gencert.
20531 - Add a manual page for tor-gencert.
20533 o Minor features (bridges):
20534 - Bridge authorities no longer serve bridge descriptors over
20535 unencrypted connections.
20537 o Minor features (other):
20538 - Add hidden services and DNSPorts to the list of things that make
20539 Tor accept that it has running ports. Change starting Tor with no
20540 ports from a fatal error to a warning; we might change it back if
20541 this turns out to confuse anybody. Fixes bug 579.
20544 Changes in version 0.1.2.19 - 2008-01-17
20545 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
20546 exit policy a little bit more conservative so it's safer to run an
20547 exit relay on a home system, and fixes a variety of smaller issues.
20550 - Exit policies now reject connections that are addressed to a
20551 relay's public (external) IP address too, unless
20552 ExitPolicyRejectPrivate is turned off. We do this because too
20553 many relays are running nearby to services that trust them based
20554 on network address.
20557 - When the clock jumps forward a lot, do not allow the bandwidth
20558 buckets to become negative. Fixes bug 544.
20559 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
20560 on every successful resolve. Reported by Mike Perry.
20561 - Purge old entries from the "rephist" database and the hidden
20562 service descriptor database even when DirPort is zero.
20563 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
20564 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
20565 crashing or mis-answering these requests.
20566 - When we decide to send a 503 response to a request for servers, do
20567 not then also send the server descriptors: this defeats the whole
20568 purpose. Fixes bug 539.
20571 - Changing the ExitPolicyRejectPrivate setting should cause us to
20572 rebuild our server descriptor.
20573 - Fix handling of hex nicknames when answering controller requests for
20574 networkstatus by name, or when deciding whether to warn about
20575 unknown routers in a config option. (Patch from mwenge.)
20576 - Fix a couple of hard-to-trigger autoconf problems that could result
20577 in really weird results on platforms whose sys/types.h files define
20578 nonstandard integer types.
20579 - Don't try to create the datadir when running --verify-config or
20580 --hash-password. Resolves bug 540.
20581 - If we were having problems getting a particular descriptor from the
20582 directory caches, and then we learned about a new descriptor for
20583 that router, we weren't resetting our failure count. Reported
20585 - Although we fixed bug 539 (where servers would send HTTP status 503
20586 responses _and_ send a body too), there are still servers out there
20587 that haven't upgraded. Therefore, make clients parse such bodies
20588 when they receive them.
20589 - Run correctly on systems where rlim_t is larger than unsigned long.
20590 This includes some 64-bit systems.
20591 - Run correctly on platforms (like some versions of OS X 10.5) where
20592 the real limit for number of open files is OPEN_FILES, not rlim_max
20593 from getrlimit(RLIMIT_NOFILES).
20594 - Avoid a spurious free on base64 failure.
20595 - Avoid segfaults on certain complex invocations of
20596 router_get_by_hexdigest().
20597 - Fix rare bug on REDIRECTSTREAM control command when called with no
20598 port set: it could erroneously report an error when none had
20602 Changes in version 0.2.0.15-alpha - 2007-12-25
20603 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
20604 features added in 0.2.0.13-alpha.
20607 - Fix several remotely triggerable asserts based on DirPort requests
20608 for a v2 or v3 networkstatus object before we were prepared. This
20609 was particularly bad for 0.2.0.13 and later bridge relays, who
20610 would never have a v2 networkstatus and would thus always crash
20611 when used. Bugfixes on 0.2.0.x.
20612 - Estimate the v3 networkstatus size more accurately, rather than
20613 estimating it at zero bytes and giving it artificially high priority
20614 compared to other directory requests. Bugfix on 0.2.0.x.
20617 - Fix configure.in logic for cross-compilation.
20618 - When we load a bridge descriptor from the cache, and it was
20619 previously unreachable, mark it as retriable so we won't just
20620 ignore it. Also, try fetching a new copy immediately. Bugfixes
20622 - The bridge GeoIP stats were counting other relays, for example
20623 self-reachability and authority-reachability tests.
20626 - Support compilation to target iPhone; patch from cjacker huang.
20627 To build for iPhone, pass the --enable-iphone option to configure.
20630 Changes in version 0.2.0.14-alpha - 2007-12-23
20632 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
20633 without a datadirectory from a previous Tor install. Reported
20635 - Fix a crash when we fetch a descriptor that turns out to be
20636 unexpected (it used to be in our networkstatus when we started
20637 fetching it, but it isn't in our current networkstatus), and we
20638 aren't using bridges. Bugfix on 0.2.0.x.
20639 - Fix a crash when accessing hidden services: it would work the first
20640 time you use a given introduction point for your service, but
20641 on subsequent requests we'd be using garbage memory. Fixed by
20642 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
20643 - Fix a crash when we load a bridge descriptor from disk but we don't
20644 currently have a Bridge line for it in our torrc. Bugfix on
20648 - If bridge authorities set BridgePassword, they will serve a
20649 snapshot of known bridge routerstatuses from their DirPort to
20650 anybody who knows that password. Unset by default.
20653 - Make the unit tests build again.
20654 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
20655 - Make PublishServerDescriptor default to 1, so the default doesn't
20656 have to change as we invent new directory protocol versions.
20657 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
20658 be included unless sys/time.h is already included. Fixes
20659 bug 553. Bugfix on 0.2.0.x.
20660 - If we receive a general-purpose descriptor and then receive an
20661 identical bridge-purpose descriptor soon after, don't discard
20662 the next one as a duplicate.
20665 - If BridgeRelay is set to 1, then the default for
20666 PublishServerDescriptor is now "bridge" rather than "v2,v3".
20667 - If the user sets RelayBandwidthRate but doesn't set
20668 RelayBandwidthBurst, then make them equal rather than erroring out.
20671 Changes in version 0.2.0.13-alpha - 2007-12-21
20672 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
20673 Goodell, fixes many more bugs, and adds a lot of infrastructure for
20676 o New directory authorities:
20677 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
20681 - Only update guard status (usable / not usable) once we have
20682 enough directory information. This was causing us to always pick
20683 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
20684 causing us to discard all our guards on startup if we hadn't been
20685 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
20686 - Purge old entries from the "rephist" database and the hidden
20687 service descriptor databases even when DirPort is zero. Bugfix
20689 - We were ignoring our RelayBandwidthRate for the first 30 seconds
20690 after opening a circuit -- even a relayed circuit. Bugfix on
20692 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
20693 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
20694 crashing or mis-answering these types of requests.
20695 - Relays were publishing their server descriptor to v1 and v2
20696 directory authorities, but they didn't try publishing to v3-only
20697 authorities. Fix this; and also stop publishing to v1 authorities.
20699 - When we were reading router descriptors from cache, we were ignoring
20700 the annotations -- so for example we were reading in bridge-purpose
20701 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
20702 - When we decided to send a 503 response to a request for servers, we
20703 were then also sending the server descriptors: this defeats the
20704 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
20707 - Bridge relays now behave like clients with respect to time
20708 intervals for downloading new consensus documents -- otherwise they
20709 stand out. Bridge users now wait until the end of the interval,
20710 so their bridge relay will be sure to have a new consensus document.
20711 - Three new config options (AlternateDirAuthority,
20712 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
20713 user selectively replace the default directory authorities by type,
20714 rather than the all-or-nothing replacement that DirServer offers.
20715 - Tor can now be configured to read a GeoIP file from disk in one
20716 of two formats. This can be used by controllers to map IP addresses
20717 to countries. Eventually, it may support exit-by-country.
20718 - When possible, bridge relays remember which countries users
20719 are coming from, and report aggregate information in their
20720 extra-info documents, so that the bridge authorities can learn
20721 where Tor is blocked.
20722 - Bridge directory authorities now do reachability testing on the
20723 bridges they know. They provide router status summaries to the
20724 controller via "getinfo ns/purpose/bridge", and also dump summaries
20725 to a file periodically.
20726 - Stop fetching directory info so aggressively if your DirPort is
20727 on but your ORPort is off; stop fetching v2 dir info entirely.
20728 You can override these choices with the new FetchDirInfoEarly
20732 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
20733 consensus documents when there are too many relays at a single
20734 IP address. Now clear it in v2 network status documents too, and
20735 also clear it in routerinfo_t when the relay is no longer listed
20736 in the relevant networkstatus document.
20737 - Don't crash if we get an unexpected value for the
20738 PublishServerDescriptor config option. Reported by Matt Edman;
20739 bugfix on 0.2.0.9-alpha.
20740 - Our new v2 hidden service descriptor format allows descriptors
20741 that have no introduction points. But Tor crashed when we tried
20742 to build a descriptor with no intro points (and it would have
20743 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
20744 by Karsten Loesing.
20745 - Fix building with dmalloc 5.5.2 with glibc.
20746 - Reject uploaded descriptors and extrainfo documents if they're
20747 huge. Otherwise we'll cache them all over the network and it'll
20748 clog everything up. Reported by Aljosha Judmayer.
20749 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
20750 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
20751 - When the DANGEROUS_VERSION controller status event told us we're
20752 running an obsolete version, it used the string "OLD" to describe
20753 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
20754 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
20755 - If we can't expand our list of entry guards (e.g. because we're
20756 using bridges or we have StrictEntryNodes set), don't mark relays
20757 down when they fail a directory request. Otherwise we're too quick
20758 to mark all our entry points down. Bugfix on 0.1.2.x.
20759 - Fix handling of hex nicknames when answering controller requests for
20760 networkstatus by name, or when deciding whether to warn about unknown
20761 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
20762 - Fix a couple of hard-to-trigger autoconf problems that could result
20763 in really weird results on platforms whose sys/types.h files define
20764 nonstandard integer types. Bugfix on 0.1.2.x.
20765 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
20766 - Don't crash on name lookup when we have no current consensus. Fixes
20767 bug 538; bugfix on 0.2.0.x.
20768 - Only Tors that want to mirror the v2 directory info should
20769 create the "cached-status" directory in their datadir. (All Tors
20770 used to create it.) Bugfix on 0.2.0.9-alpha.
20771 - Directory authorities should only automatically download Extra Info
20772 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
20775 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
20776 consumers. (We already do this on HUP.)
20777 - Authorities and caches fetch the v2 networkstatus documents
20778 less often, now that v3 is encouraged.
20779 - Add a new config option BridgeRelay that specifies you want to
20780 be a bridge relay. Right now the only difference is that it makes
20781 you answer begin_dir requests, and it makes you cache dir info,
20782 even if your DirPort isn't on.
20783 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
20784 ask about source, timestamp of arrival, purpose, etc. We need
20785 something like this to help Vidalia not do GeoIP lookups on bridge
20787 - Allow multiple HashedControlPassword config lines, to support
20788 multiple controller passwords.
20789 - Authorities now decide whether they're authoritative for a given
20790 router based on the router's purpose.
20791 - New config options AuthDirBadDir and AuthDirListBadDirs for
20792 authorities to mark certain relays as "bad directories" in the
20793 networkstatus documents. Also supports the "!baddir" directive in
20794 the approved-routers file.
20797 Changes in version 0.2.0.12-alpha - 2007-11-16
20798 This twelfth development snapshot fixes some more build problems as
20799 well as a few minor bugs.
20802 - Make it build on OpenBSD again. Patch from tup.
20803 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
20804 package-building for Red Hat, OS X, etc.
20806 o Minor bugfixes (on 0.1.2.x):
20807 - Changing the ExitPolicyRejectPrivate setting should cause us to
20808 rebuild our server descriptor.
20810 o Minor bugfixes (on 0.2.0.x):
20811 - When we're lacking a consensus, don't try to perform rendezvous
20812 operations. Reported by Karsten Loesing.
20813 - Fix a small memory leak whenever we decide against using a
20814 newly picked entry guard. Reported by Mike Perry.
20815 - When authorities detected more than two relays running on the same
20816 IP address, they were clearing all the status flags but forgetting
20817 to clear the "hsdir" flag. So clients were being told that a
20818 given relay was the right choice for a v2 hsdir lookup, yet they
20819 never had its descriptor because it was marked as 'not running'
20821 - If we're trying to fetch a bridge descriptor and there's no way
20822 the bridge authority could help us (for example, we don't know
20823 a digest, or there is no bridge authority), don't be so eager to
20824 fall back to asking the bridge authority.
20825 - If we're using bridges or have strictentrynodes set, and our
20826 chosen exit is in the same family as all our bridges/entry guards,
20827 then be flexible about families.
20830 - When we negotiate a v2 link-layer connection (not yet implemented),
20831 accept RELAY_EARLY cells and turn them into RELAY cells if we've
20832 negotiated a v1 connection for their next step. Initial code for
20836 Changes in version 0.2.0.11-alpha - 2007-11-12
20837 This eleventh development snapshot fixes some build problems with
20838 the previous snapshot. It also includes a more secure-by-default exit
20839 policy for relays, fixes an enormous memory leak for exit relays, and
20840 fixes another bug where servers were falling out of the directory list.
20843 - Exit policies now reject connections that are addressed to a
20844 relay's public (external) IP address too, unless
20845 ExitPolicyRejectPrivate is turned off. We do this because too
20846 many relays are running nearby to services that trust them based
20847 on network address. Bugfix on 0.1.2.x.
20850 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
20851 on every successful resolve. Reported by Mike Perry; bugfix
20853 - On authorities, never downgrade to old router descriptors simply
20854 because they're listed in the consensus. This created a catch-22
20855 where we wouldn't list a new descriptor because there was an
20856 old one in the consensus, and we couldn't get the new one in the
20857 consensus because we wouldn't list it. Possible fix for bug 548.
20858 Also, this might cause bug 543 to appear on authorities; if so,
20859 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
20861 o Packaging fixes on 0.2.0.10-alpha:
20862 - We were including instructions about what to do with the
20863 src/config/fallback-consensus file, but we weren't actually
20864 including it in the tarball. Disable all of that for now.
20867 - Allow people to say PreferTunnelledDirConns rather than
20868 PreferTunneledDirConns, for those alternate-spellers out there.
20871 - Don't reevaluate all the information from our consensus document
20872 just because we've downloaded a v2 networkstatus that we intend
20873 to cache. Fixes bug 545; bugfix on 0.2.0.x.
20876 Changes in version 0.2.0.10-alpha - 2007-11-10
20877 This tenth development snapshot adds a third v3 directory authority
20878 run by Mike Perry, adds most of Karsten Loesing's new hidden service
20879 descriptor format, fixes a bad crash bug and new bridge bugs introduced
20880 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
20881 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
20882 addresses many more minor issues.
20884 o New directory authorities:
20885 - Set up ides (run by Mike Perry) as the third v3 directory authority.
20888 - Allow tunnelled directory connections to ask for an encrypted
20889 "begin_dir" connection or an anonymized "uses a full Tor circuit"
20890 connection independently. Now we can make anonymized begin_dir
20891 connections for (e.g.) more secure hidden service posting and
20893 - More progress on proposal 114: code from Karsten Loesing to
20894 implement new hidden service descriptor format.
20895 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
20896 accommodate the growing number of servers that use the default
20897 and are reaching it.
20898 - Directory authorities use a new formula for selecting which nodes
20899 to advertise as Guards: they must be in the top 7/8 in terms of
20900 how long we have known about them, and above the median of those
20901 nodes in terms of weighted fractional uptime.
20902 - Make "not enough dir info yet" warnings describe *why* Tor feels
20903 it doesn't have enough directory info yet.
20906 - Stop servers from crashing if they set a Family option (or
20907 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
20909 - Make bridge users work again -- the move to v3 directories in
20910 0.2.0.9-alpha had introduced a number of bugs that made bridges
20911 no longer work for clients.
20912 - When the clock jumps forward a lot, do not allow the bandwidth
20913 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
20915 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
20916 - When the consensus lists a router descriptor that we previously were
20917 mirroring, but that we considered non-canonical, reload the
20918 descriptor as canonical. This fixes bug 543 where Tor servers
20919 would start complaining after a few days that they don't have
20920 enough directory information to build a circuit.
20921 - Consider replacing the current consensus when certificates arrive
20922 that make the pending consensus valid. Previously, we were only
20923 considering replacement when the new certs _didn't_ help.
20924 - Fix an assert error on startup if we didn't already have the
20925 consensus and certs cached in our datadirectory: we were caching
20926 the consensus in consensus_waiting_for_certs but then free'ing it
20928 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
20929 Request) if we need more v3 certs but we've already got pending
20930 requests for all of them.
20931 - Correctly back off from failing certificate downloads. Fixes
20933 - Authorities don't vote on the Running flag if they have been running
20934 for less than 30 minutes themselves. Fixes bug 547, where a newly
20935 started authority would vote that everyone was down.
20937 o New requirements:
20938 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
20939 it, it had no AES, and it hasn't seen any security patches since
20943 - Clients now hold circuitless TLS connections open for 1.5 times
20944 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
20945 rebuild a new circuit over them within that timeframe. Previously,
20946 they held them open only for KeepalivePeriod (5 minutes).
20947 - Use "If-Modified-Since" to avoid retrieving consensus
20948 networkstatuses that we already have.
20949 - When we have no consensus, check FallbackNetworkstatusFile (defaults
20950 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
20951 we start knowing some directory caches.
20952 - When we receive a consensus from the future, warn about skew.
20953 - Improve skew reporting: try to give the user a better log message
20954 about how skewed they are, and how much this matters.
20955 - When we have a certificate for an authority, believe that
20956 certificate's claims about the authority's IP address.
20957 - New --quiet command-line option to suppress the default console log.
20958 Good in combination with --hash-password.
20959 - Authorities send back an X-Descriptor-Not-New header in response to
20960 an accepted-but-discarded descriptor upload. Partially implements
20962 - Make the log message for "tls error. breaking." more useful.
20963 - Better log messages about certificate downloads, to attempt to
20964 track down the second incarnation of bug 546.
20966 o Minor features (bridges):
20967 - If bridge users set UpdateBridgesFromAuthority, but the digest
20968 they ask for is a 404 from the bridge authority, they now fall
20969 back to trying the bridge directly.
20970 - Bridges now use begin_dir to publish their server descriptor to
20971 the bridge authority, even when they haven't set TunnelDirConns.
20973 o Minor features (controller):
20974 - When reporting clock skew, and we know that the clock is _at least
20975 as skewed_ as some value, but we don't know the actual value,
20976 report the value as a "minimum skew."
20979 - Update linux-tor-prio.sh script to allow QoS based on the uid of
20980 the Tor process. Patch from Marco Bonetti with tweaks from Mike
20984 - Refuse to start if both ORPort and UseBridges are set. Bugfix
20985 on 0.2.0.x, suggested by Matt Edman.
20986 - Don't stop fetching descriptors when FetchUselessDescriptors is
20987 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
20988 reported by tup and ioerror.
20989 - Better log message on vote from unknown authority.
20990 - Don't log "Launching 0 request for 0 router" message.
20992 o Minor bugfixes (memory leaks):
20993 - Stop leaking memory every time we parse a v3 certificate. Bugfix
20995 - Stop leaking memory every time we load a v3 certificate. Bugfix
20996 on 0.2.0.1-alpha. Fixes bug 536.
20997 - Stop leaking a cached networkstatus on exit. Bugfix on
20999 - Stop leaking voter information every time we free a consensus.
21000 Bugfix on 0.2.0.3-alpha.
21001 - Stop leaking signed data every time we check a voter signature.
21002 Bugfix on 0.2.0.3-alpha.
21003 - Stop leaking a signature every time we fail to parse a consensus or
21004 a vote. Bugfix on 0.2.0.3-alpha.
21005 - Stop leaking v2_download_status_map on shutdown. Bugfix on
21007 - Stop leaking conn->nickname every time we make a connection to a
21008 Tor relay without knowing its expected identity digest (e.g. when
21009 using bridges). Bugfix on 0.2.0.3-alpha.
21011 - Minor bugfixes (portability):
21012 - Run correctly on platforms where rlim_t is larger than unsigned
21013 long, and/or where the real limit for number of open files is
21014 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
21015 particular, these may be needed for OS X 10.5.
21018 Changes in version 0.1.2.18 - 2007-10-28
21019 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
21020 hidden service introduction that were causing huge delays, and a big
21021 bug that was causing some servers to disappear from the network status
21022 lists for a few hours each day.
21024 o Major bugfixes (crashes):
21025 - If a connection is shut down abruptly because of something that
21026 happened inside connection_flushed_some(), do not call
21027 connection_finished_flushing(). Should fix bug 451:
21028 "connection_stop_writing: Assertion conn->write_event failed"
21029 Bugfix on 0.1.2.7-alpha.
21030 - Fix possible segfaults in functions called from
21031 rend_process_relay_cell().
21033 o Major bugfixes (hidden services):
21034 - Hidden services were choosing introduction points uniquely by
21035 hexdigest, but when constructing the hidden service descriptor
21036 they merely wrote the (potentially ambiguous) nickname.
21037 - Clients now use the v2 intro format for hidden service
21038 connections: they specify their chosen rendezvous point by identity
21039 digest rather than by (potentially ambiguous) nickname. These
21040 changes could speed up hidden service connections dramatically.
21042 o Major bugfixes (other):
21043 - Stop publishing a new server descriptor just because we get a
21044 HUP signal. This led (in a roundabout way) to some servers getting
21045 dropped from the networkstatus lists for a few hours each day.
21046 - When looking for a circuit to cannibalize, consider family as well
21047 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
21048 circuit cannibalization).
21049 - When a router wasn't listed in a new networkstatus, we were leaving
21050 the flags for that router alone -- meaning it remained Named,
21051 Running, etc -- even though absence from the networkstatus means
21052 that it shouldn't be considered to exist at all anymore. Now we
21053 clear all the flags for routers that fall out of the networkstatus
21054 consensus. Fixes bug 529.
21057 - Don't try to access (or alter) the state file when running
21058 --list-fingerprint or --verify-config or --hash-password. Resolves
21060 - When generating information telling us how to extend to a given
21061 router, do not try to include the nickname if it is
21062 absent. Resolves bug 467.
21063 - Fix a user-triggerable segfault in expand_filename(). (There isn't
21064 a way to trigger this remotely.)
21065 - When sending a status event to the controller telling it that an
21066 OR address is reachable, set the port correctly. (Previously we
21067 were reporting the dir port.)
21068 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
21069 command. Bugfix on 0.1.2.17.
21070 - When loading bandwidth history, do not believe any information in
21071 the future. Fixes bug 434.
21072 - When loading entry guard information, do not believe any information
21074 - When we have our clock set far in the future and generate an
21075 onion key, then re-set our clock to be correct, we should not stop
21076 the onion key from getting rotated.
21077 - On some platforms, accept() can return a broken address. Detect
21078 this more quietly, and deal accordingly. Fixes bug 483.
21079 - It's not actually an error to find a non-pending entry in the DNS
21080 cache when canceling a pending resolve. Don't log unless stuff
21081 is fishy. Resolves bug 463.
21082 - Don't reset trusted dir server list when we set a configuration
21083 option. Patch from Robert Hogan.
21084 - Don't try to create the datadir when running --verify-config or
21085 --hash-password. Resolves bug 540.
21088 Changes in version 0.2.0.9-alpha - 2007-10-24
21089 This ninth development snapshot switches clients to the new v3 directory
21090 system; allows servers to be listed in the network status even when they
21091 have the same nickname as a registered server; and fixes many other
21092 bugs including a big one that was causing some servers to disappear
21093 from the network status lists for a few hours each day.
21095 o Major features (directory system):
21096 - Clients now download v3 consensus networkstatus documents instead
21097 of v2 networkstatus documents. Clients and caches now base their
21098 opinions about routers on these consensus documents. Clients only
21099 download router descriptors listed in the consensus.
21100 - Authorities now list servers who have the same nickname as
21101 a different named server, but list them with a new flag,
21102 "Unnamed". Now we can list servers that happen to pick the same
21103 nickname as a server that registered two years ago and then
21104 disappeared. Partially implements proposal 122.
21105 - If the consensus lists a router as "Unnamed", the name is assigned
21106 to a different router: do not identify the router by that name.
21107 Partially implements proposal 122.
21108 - Authorities can now come to a consensus on which method to use to
21109 compute the consensus. This gives us forward compatibility.
21112 - Stop publishing a new server descriptor just because we HUP or
21113 when we find our DirPort to be reachable but won't actually publish
21114 it. New descriptors without any real changes are dropped by the
21115 authorities, and can screw up our "publish every 18 hours" schedule.
21117 - When a router wasn't listed in a new networkstatus, we were leaving
21118 the flags for that router alone -- meaning it remained Named,
21119 Running, etc -- even though absence from the networkstatus means
21120 that it shouldn't be considered to exist at all anymore. Now we
21121 clear all the flags for routers that fall out of the networkstatus
21122 consensus. Fixes bug 529; bugfix on 0.1.2.x.
21123 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
21124 extrainfo documents and then discard them immediately for not
21125 matching the latest router. Bugfix on 0.2.0.1-alpha.
21127 o Minor features (v3 directory protocol):
21128 - Allow tor-gencert to generate a new certificate without replacing
21130 - Allow certificates to include an address.
21131 - When we change our directory-cache settings, reschedule all voting
21132 and download operations.
21133 - Reattempt certificate downloads immediately on failure, as long as
21134 we haven't failed a threshold number of times yet.
21135 - Delay retrying consensus downloads while we're downloading
21136 certificates to verify the one we just got. Also, count getting a
21137 consensus that we already have (or one that isn't valid) as a failure,
21138 and count failing to get the certificates after 20 minutes as a
21140 - Build circuits and download descriptors even if our consensus is a
21141 little expired. (This feature will go away once authorities are
21144 o Minor features (router descriptor cache):
21145 - If we find a cached-routers file that's been sitting around for more
21146 than 28 days unmodified, then most likely it's a leftover from
21147 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
21149 - When we (as a cache) download a descriptor because it was listed
21150 in a consensus, remember when the consensus was supposed to expire,
21151 and don't expire the descriptor until then.
21153 o Minor features (performance):
21154 - Call routerlist_remove_old_routers() much less often. This should
21155 speed startup, especially on directory caches.
21156 - Don't try to launch new descriptor downloads quite so often when we
21157 already have enough directory information to build circuits.
21158 - Base64 decoding was actually showing up on our profile when parsing
21159 the initial descriptor file; switch to an in-process all-at-once
21160 implementation that's about 3.5x times faster than calling out to
21163 o Minor features (compilation):
21164 - Detect non-ASCII platforms (if any still exist) and refuse to
21165 build there: some of our code assumes that 'A' is 65 and so on.
21167 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
21168 - Make the "next period" votes into "current period" votes immediately
21169 after publishing the consensus; avoid a heisenbug that made them
21170 stick around indefinitely.
21171 - When we discard a vote as a duplicate, do not report this as
21173 - Treat missing v3 keys or certificates as an error when running as a
21174 v3 directory authority.
21175 - When we're configured to be a v3 authority, but we're only listed
21176 as a non-v3 authority in our DirServer line for ourself, correct
21178 - If an authority doesn't have a qualified hostname, just put
21179 its address in the vote. This fixes the problem where we referred to
21180 "moria on moria:9031."
21181 - Distinguish between detached signatures for the wrong period, and
21182 detached signatures for a divergent vote.
21183 - Fix a small memory leak when computing a consensus.
21184 - When there's no concensus, we were forming a vote every 30
21185 minutes, but writing the "valid-after" line in our vote based
21186 on our configured V3AuthVotingInterval: so unless the intervals
21187 matched up, we immediately rejected our own vote because it didn't
21188 start at the voting interval that caused us to construct a vote.
21190 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
21191 - Delete unverified-consensus when the real consensus is set.
21192 - Consider retrying a consensus networkstatus fetch immediately
21193 after one fails: don't wait 60 seconds to notice.
21194 - When fetching a consensus as a cache, wait until a newer consensus
21195 should exist before trying to replace the current one.
21196 - Use a more forgiving schedule for retrying failed consensus
21197 downloads than for other types.
21199 o Minor bugfixes (other directory issues):
21200 - Correct the implementation of "download votes by digest." Bugfix on
21202 - Authorities no longer send back "400 you're unreachable please fix
21203 it" errors to Tor servers that aren't online all the time. We're
21204 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
21206 o Minor bugfixes (controller):
21207 - Don't reset trusted dir server list when we set a configuration
21208 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
21209 - Respond to INT and TERM SIGNAL commands before we execute the
21210 signal, in case the signal shuts us down. We had a patch in
21211 0.1.2.1-alpha that tried to do this by queueing the response on
21212 the connection's buffer before shutting down, but that really
21213 isn't the same thing at all. Bug located by Matt Edman.
21215 o Minor bugfixes (misc):
21216 - Correctly check for bad options to the "PublishServerDescriptor"
21217 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
21218 - Stop leaking memory on failing case of base32_decode, and make
21219 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
21220 - Don't try to download extrainfo documents when we're trying to
21221 fetch enough directory info to build a circuit: having enough
21222 info should get priority. Bugfix on 0.2.0.x.
21223 - Don't complain that "your server has not managed to confirm that its
21224 ports are reachable" if we haven't been able to build any circuits
21225 yet. Bug found by spending four hours without a v3 consensus. Bugfix
21227 - Detect the reason for failing to mmap a descriptor file we just
21228 wrote, and give a more useful log message. Fixes bug 533. Bugfix
21231 o Code simplifications and refactoring:
21232 - Remove support for the old bw_accounting file: we've been storing
21233 bandwidth accounting information in the state file since
21234 0.1.2.5-alpha. This may result in bandwidth accounting errors
21235 if you try to upgrade from 0.1.1.x or earlier, or if you try to
21236 downgrade to 0.1.1.x or earlier.
21237 - New convenience code to locate a file within the DataDirectory.
21238 - Move non-authority functionality out of dirvote.c.
21239 - Refactor the arguments for router_pick_{directory_|trusteddir}server
21240 so that they all take the same named flags.
21243 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
21244 Unix users an easy way to script their Tor process (e.g. by
21245 adjusting bandwidth based on the time of the day).
21248 Changes in version 0.2.0.8-alpha - 2007-10-12
21249 This eighth development snapshot fixes a crash bug that's been bothering
21250 us since February 2007, lets bridge authorities store a list of bridge
21251 descriptors they've seen, gets v3 directory voting closer to working,
21252 starts caching v3 directory consensus documents on directory mirrors,
21253 and fixes a variety of smaller issues including some minor memory leaks.
21255 o Major features (router descriptor cache):
21256 - Store routers in a file called cached-descriptors instead of in
21257 cached-routers. Initialize cached-descriptors from cached-routers
21258 if the old format is around. The new format allows us to store
21259 annotations along with descriptors.
21260 - Use annotations to record the time we received each descriptor, its
21261 source, and its purpose.
21262 - Disable the SETROUTERPURPOSE controller command: it is now
21264 - Controllers should now specify cache=no or cache=yes when using
21265 the +POSTDESCRIPTOR command.
21266 - Bridge authorities now write bridge descriptors to disk, meaning
21267 we can export them to other programs and begin distributing them
21270 o Major features (directory authorities):
21271 - When a v3 authority is missing votes or signatures, it now tries
21273 - Directory authorities track weighted fractional uptime as well as
21274 weighted mean-time-between failures. WFU is suitable for deciding
21275 whether a node is "usually up", while MTBF is suitable for deciding
21276 whether a node is "likely to stay up." We need both, because
21277 "usually up" is a good requirement for guards, while "likely to
21278 stay up" is a good requirement for long-lived connections.
21280 o Major features (v3 directory system):
21281 - Caches now download v3 network status documents as needed,
21282 and download the descriptors listed in them.
21283 - All hosts now attempt to download and keep fresh v3 authority
21284 certificates, and re-attempt after failures.
21285 - More internal-consistency checks for vote parsing.
21287 o Major bugfixes (crashes):
21288 - If a connection is shut down abruptly because of something that
21289 happened inside connection_flushed_some(), do not call
21290 connection_finished_flushing(). Should fix bug 451. Bugfix on
21293 o Major bugfixes (performance):
21294 - Fix really bad O(n^2) performance when parsing a long list of
21295 routers: Instead of searching the entire list for an "extra-info "
21296 string which usually wasn't there, once for every routerinfo
21297 we read, just scan lines forward until we find one we like.
21299 - When we add data to a write buffer in response to the data on that
21300 write buffer getting low because of a flush, do not consider the
21301 newly added data as a candidate for immediate flushing, but rather
21302 make it wait until the next round of writing. Otherwise, we flush
21303 and refill recursively, and a single greedy TLS connection can
21304 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
21306 o Minor features (v3 authority system):
21307 - Add more ways for tools to download the votes that lead to the
21309 - Send a 503 when low on bandwidth and a vote, consensus, or
21310 certificate is requested.
21311 - If-modified-since is now implemented properly for all kinds of
21312 certificate requests.
21314 o Minor bugfixes (network statuses):
21315 - Tweak the implementation of proposal 109 slightly: allow at most
21316 two Tor servers on the same IP address, except if it's the location
21317 of a directory authority, in which case allow five. Bugfix on
21320 o Minor bugfixes (controller):
21321 - When sending a status event to the controller telling it that an
21322 OR address is reachable, set the port correctly. (Previously we
21323 were reporting the dir port.) Bugfix on 0.1.2.x.
21325 o Minor bugfixes (v3 directory system):
21326 - Fix logic to look up a cert by its signing key digest. Bugfix on
21328 - Only change the reply to a vote to "OK" if it's not already
21329 set. This gets rid of annoying "400 OK" log messages, which may
21330 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
21331 - When we get a valid consensus, recompute the voting schedule.
21332 - Base the valid-after time of a vote on the consensus voting
21333 schedule, not on our preferred schedule.
21334 - Make the return values and messages from signature uploads and
21335 downloads more sensible.
21336 - Fix a memory leak when serving votes and consensus documents, and
21337 another when serving certificates.
21339 o Minor bugfixes (performance):
21340 - Use a slightly simpler string hashing algorithm (copying Python's
21341 instead of Java's) and optimize our digest hashing algorithm to take
21342 advantage of 64-bit platforms and to remove some possibly-costly
21344 - Fix a minor memory leak whenever we parse guards from our state
21345 file. Bugfix on 0.2.0.7-alpha.
21346 - Fix a minor memory leak whenever we write out a file. Bugfix on
21348 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
21349 command. Bugfix on 0.2.0.5-alpha.
21351 o Minor bugfixes (portability):
21352 - On some platforms, accept() can return a broken address. Detect
21353 this more quietly, and deal accordingly. Fixes bug 483.
21354 - Stop calling tor_strlower() on uninitialized memory in some cases.
21355 Bugfix in 0.2.0.7-alpha.
21357 o Minor bugfixes (usability):
21358 - Treat some 403 responses from directory servers as INFO rather than
21359 WARN-severity events.
21360 - It's not actually an error to find a non-pending entry in the DNS
21361 cache when canceling a pending resolve. Don't log unless stuff is
21362 fishy. Resolves bug 463.
21364 o Minor bugfixes (anonymity):
21365 - Never report that we've used more bandwidth than we're willing to
21366 relay: it leaks how much non-relay traffic we're using. Resolves
21368 - When looking for a circuit to cannibalize, consider family as well
21369 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
21370 circuit cannibalization).
21372 o Code simplifications and refactoring:
21373 - Make a bunch of functions static. Remove some dead code.
21374 - Pull out about a third of the really big routerlist.c; put it in a
21375 new module, networkstatus.c.
21376 - Merge the extra fields in local_routerstatus_t back into
21377 routerstatus_t: we used to need one routerstatus_t for each
21378 authority's opinion, plus a local_routerstatus_t for the locally
21379 computed consensus opinion. To save space, we put the locally
21380 modified fields into local_routerstatus_t, and only the common
21381 stuff into routerstatus_t. But once v3 directories are in use,
21382 clients and caches will no longer need to hold authority opinions;
21383 thus, the rationale for keeping the types separate is now gone.
21384 - Make the code used to reschedule and reattempt downloads more
21386 - Turn all 'Are we a directory server/mirror?' logic into a call to
21388 - Remove the code to generate the oldest (v1) directory format.
21389 The code has been disabled since 0.2.0.5-alpha.
21392 Changes in version 0.2.0.7-alpha - 2007-09-21
21393 This seventh development snapshot makes bridges work again, makes bridge
21394 authorities work for the first time, fixes two huge performance flaws
21395 in hidden services, and fixes a variety of minor issues.
21397 o New directory authorities:
21398 - Set up moria1 and tor26 as the first v3 directory authorities. See
21399 doc/spec/dir-spec.txt for details on the new directory design.
21401 o Major bugfixes (crashes):
21402 - Fix possible segfaults in functions called from
21403 rend_process_relay_cell(). Bugfix on 0.1.2.x.
21405 o Major bugfixes (bridges):
21406 - Fix a bug that made servers send a "404 Not found" in response to
21407 attempts to fetch their server descriptor. This caused Tor servers
21408 to take many minutes to establish reachability for their DirPort,
21409 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
21410 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
21411 users configure that and specify a bridge with an identity
21412 fingerprint, now they will lookup the bridge descriptor at the
21413 default bridge authority via a one-hop tunnel, but once circuits
21414 are established they will switch to a three-hop tunnel for later
21415 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
21417 o Major bugfixes (hidden services):
21418 - Hidden services were choosing introduction points uniquely by
21419 hexdigest, but when constructing the hidden service descriptor
21420 they merely wrote the (potentially ambiguous) nickname.
21421 - Clients now use the v2 intro format for hidden service
21422 connections: they specify their chosen rendezvous point by identity
21423 digest rather than by (potentially ambiguous) nickname. Both
21424 are bugfixes on 0.1.2.x, and they could speed up hidden service
21425 connections dramatically. Thanks to Karsten Loesing.
21427 o Minor features (security):
21428 - As a client, do not believe any server that tells us that an
21429 address maps to an internal address space.
21430 - Make it possible to enable HashedControlPassword and
21431 CookieAuthentication at the same time.
21433 o Minor features (guard nodes):
21434 - Tag every guard node in our state file with the version that
21435 we believe added it, or with our own version if we add it. This way,
21436 if a user temporarily runs an old version of Tor and then switches
21437 back to a new one, she doesn't automatically lose her guards.
21439 o Minor features (speed):
21440 - When implementing AES counter mode, update only the portions of the
21441 counter buffer that need to change, and don't keep separate
21442 network-order and host-order counters when they are the same (i.e.,
21443 on big-endian hosts.)
21445 o Minor features (controller):
21446 - Accept LF instead of CRLF on controller, since some software has a
21447 hard time generating real Internet newlines.
21448 - Add GETINFO values for the server status events
21449 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
21452 o Removed features:
21453 - Routers no longer include bandwidth-history lines in their
21454 descriptors; this information is already available in extra-info
21455 documents, and including it in router descriptors took up 60%
21456 (!) of compressed router descriptor downloads. Completes
21457 implementation of proposal 104.
21458 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
21459 and TorControl.py, as they use the old v0 controller protocol,
21460 and are obsoleted by TorFlow anyway.
21461 - Drop support for v1 rendezvous descriptors, since we never used
21462 them anyway, and the code has probably rotted by now. Based on
21463 patch from Karsten Loesing.
21464 - On OSX, stop warning the user that kqueue support in libevent is
21465 "experimental", since it seems to have worked fine for ages.
21468 - When generating information telling us how to extend to a given
21469 router, do not try to include the nickname if it is absent. Fixes
21470 bug 467. Bugfix on 0.2.0.3-alpha.
21471 - Fix a user-triggerable (but not remotely-triggerable) segfault
21472 in expand_filename(). Bugfix on 0.1.2.x.
21473 - Fix a memory leak when freeing incomplete requests from DNSPort.
21474 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
21475 - Don't try to access (or alter) the state file when running
21476 --list-fingerprint or --verify-config or --hash-password. (Resolves
21477 bug 499.) Bugfix on 0.1.2.x.
21478 - Servers used to decline to publish their DirPort if their
21479 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
21480 were below a threshold. Now they only look at BandwidthRate and
21481 RelayBandwidthRate. Bugfix on 0.1.2.x.
21482 - Remove an optimization in the AES counter-mode code that assumed
21483 that the counter never exceeded 2^68. When the counter can be set
21484 arbitrarily as an IV (as it is by Karsten's new hidden services
21485 code), this assumption no longer holds. Bugfix on 0.1.2.x.
21486 - Resume listing "AUTHORITY" flag for authorities in network status.
21487 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
21489 o Code simplifications and refactoring:
21490 - Revamp file-writing logic so we don't need to have the entire
21491 contents of a file in memory at once before we write to disk. Tor,
21493 - Turn "descriptor store" into a full-fledged type.
21494 - Move all NT services code into a separate source file.
21495 - Unify all code that computes medians, percentile elements, etc.
21496 - Get rid of a needless malloc when parsing address policies.
21499 Changes in version 0.1.2.17 - 2007-08-30
21500 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
21501 X bundles. Vidalia 0.0.14 makes authentication required for the
21502 ControlPort in the default configuration, which addresses important
21503 security risks. Everybody who uses Vidalia (or another controller)
21506 In addition, this Tor update fixes major load balancing problems with
21507 path selection, which should speed things up a lot once many people
21510 o Major bugfixes (security):
21511 - We removed support for the old (v0) control protocol. It has been
21512 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
21513 become more of a headache than it's worth.
21515 o Major bugfixes (load balancing):
21516 - When choosing nodes for non-guard positions, weight guards
21517 proportionally less, since they already have enough load. Patch
21519 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
21520 will allow fast Tor servers to get more attention.
21521 - When we're upgrading from an old Tor version, forget our current
21522 guards and pick new ones according to the new weightings. These
21523 three load balancing patches could raise effective network capacity
21524 by a factor of four. Thanks to Mike Perry for measurements.
21526 o Major bugfixes (stream expiration):
21527 - Expire not-yet-successful application streams in all cases if
21528 they've been around longer than SocksTimeout. Right now there are
21529 some cases where the stream will live forever, demanding a new
21530 circuit every 15 seconds. Fixes bug 454; reported by lodger.
21532 o Minor features (controller):
21533 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
21534 is valid before any authentication has been received. It tells
21535 a controller what kind of authentication is expected, and what
21536 protocol is spoken. Implements proposal 119.
21538 o Minor bugfixes (performance):
21539 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
21540 greatly speeding up loading cached-routers from disk on startup.
21541 - Disable sentinel-based debugging for buffer code: we squashed all
21542 the bugs that this was supposed to detect a long time ago, and now
21543 its only effect is to change our buffer sizes from nice powers of
21544 two (which platform mallocs tend to like) to values slightly over
21545 powers of two (which make some platform mallocs sad).
21547 o Minor bugfixes (misc):
21548 - If exit bandwidth ever exceeds one third of total bandwidth, then
21549 use the correct formula to weight exit nodes when choosing paths.
21550 Based on patch from Mike Perry.
21551 - Choose perfectly fairly among routers when choosing by bandwidth and
21552 weighting by fraction of bandwidth provided by exits. Previously, we
21553 would choose with only approximate fairness, and correct ourselves
21554 if we ran off the end of the list.
21555 - If we require CookieAuthentication but we fail to write the
21556 cookie file, we would warn but not exit, and end up in a state
21557 where no controller could authenticate. Now we exit.
21558 - If we require CookieAuthentication, stop generating a new cookie
21559 every time we change any piece of our config.
21560 - Refuse to start with certain directory authority keys, and
21561 encourage people using them to stop.
21562 - Terminate multi-line control events properly. Original patch
21564 - Fix a minor memory leak when we fail to find enough suitable
21565 servers to choose a circuit.
21566 - Stop leaking part of the descriptor when we run into a particularly
21567 unparseable piece of it.
21570 Changes in version 0.2.0.6-alpha - 2007-08-26
21571 This sixth development snapshot features a new Vidalia version in the
21572 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
21573 the ControlPort in the default configuration, which addresses important
21576 In addition, this snapshot fixes major load balancing problems
21577 with path selection, which should speed things up a lot once many
21578 people have upgraded. The directory authorities also use a new
21579 mean-time-between-failure approach to tracking which servers are stable,
21580 rather than just looking at the most recent uptime.
21582 o New directory authorities:
21583 - Set up Tonga as the default bridge directory authority.
21586 - Directory authorities now track servers by weighted
21587 mean-times-between-failures. When we have 4 or more days of data,
21588 use measured MTBF rather than declared uptime to decide whether
21589 to call a router Stable. Implements proposal 108.
21591 o Major bugfixes (load balancing):
21592 - When choosing nodes for non-guard positions, weight guards
21593 proportionally less, since they already have enough load. Patch
21595 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
21596 will allow fast Tor servers to get more attention.
21597 - When we're upgrading from an old Tor version, forget our current
21598 guards and pick new ones according to the new weightings. These
21599 three load balancing patches could raise effective network capacity
21600 by a factor of four. Thanks to Mike Perry for measurements.
21602 o Major bugfixes (descriptor parsing):
21603 - Handle unexpected whitespace better in malformed descriptors. Bug
21604 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
21607 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
21608 GETINFO for Torstat to use until it can switch to using extrainfos.
21609 - Optionally (if built with -DEXPORTMALLINFO) export the output
21610 of mallinfo via http, as tor/mallinfo.txt. Only accessible
21614 - Do not intermix bridge routers with controller-added
21615 routers. (Bugfix on 0.2.0.x)
21616 - Do not fail with an assert when accept() returns an unexpected
21617 address family. Addresses but does not wholly fix bug 483. (Bugfix
21619 - Let directory authorities startup even when they can't generate
21620 a descriptor immediately, e.g. because they don't know their
21622 - Stop putting the authentication cookie in a file called "0"
21623 in your working directory if you don't specify anything for the
21624 new CookieAuthFile option. Reported by Matt Edman.
21625 - Make it possible to read the PROTOCOLINFO response in a way that
21626 conforms to our control-spec. Reported by Matt Edman.
21627 - Fix a minor memory leak when we fail to find enough suitable
21628 servers to choose a circuit. Bugfix on 0.1.2.x.
21629 - Stop leaking part of the descriptor when we run into a particularly
21630 unparseable piece of it. Bugfix on 0.1.2.x.
21631 - Unmap the extrainfo cache file on exit.
21634 Changes in version 0.2.0.5-alpha - 2007-08-19
21635 This fifth development snapshot fixes compilation on Windows again;
21636 fixes an obnoxious client-side bug that slowed things down and put
21637 extra load on the network; gets us closer to using the v3 directory
21638 voting scheme; makes it easier for Tor controllers to use cookie-based
21639 authentication; and fixes a variety of other bugs.
21641 o Removed features:
21642 - Version 1 directories are no longer generated in full. Instead,
21643 authorities generate and serve "stub" v1 directories that list
21644 no servers. This will stop Tor versions 0.1.0.x and earlier from
21645 working, but (for security reasons) nobody should be running those
21648 o Major bugfixes (compilation, 0.2.0.x):
21649 - Try to fix Win32 compilation again: improve checking for IPv6 types.
21650 - Try to fix MSVC compilation: build correctly on platforms that do
21651 not define s6_addr16 or s6_addr32.
21652 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
21655 o Major bugfixes (stream expiration):
21656 - Expire not-yet-successful application streams in all cases if
21657 they've been around longer than SocksTimeout. Right now there are
21658 some cases where the stream will live forever, demanding a new
21659 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
21660 reported by lodger.
21662 o Minor features (directory servers):
21663 - When somebody requests a list of statuses or servers, and we have
21664 none of those, return a 404 rather than an empty 200.
21666 o Minor features (directory voting):
21667 - Store v3 consensus status consensuses on disk, and reload them
21670 o Minor features (security):
21671 - Warn about unsafe ControlPort configurations.
21672 - Refuse to start with certain directory authority keys, and
21673 encourage people using them to stop.
21675 o Minor features (controller):
21676 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
21677 is valid before any authentication has been received. It tells
21678 a controller what kind of authentication is expected, and what
21679 protocol is spoken. Implements proposal 119.
21680 - New config option CookieAuthFile to choose a new location for the
21681 cookie authentication file, and config option
21682 CookieAuthFileGroupReadable to make it group-readable.
21684 o Minor features (unit testing):
21685 - Add command-line arguments to unit-test executable so that we can
21686 invoke any chosen test from the command line rather than having
21687 to run the whole test suite at once; and so that we can turn on
21688 logging for the unit tests.
21690 o Minor bugfixes (on 0.1.2.x):
21691 - If we require CookieAuthentication but we fail to write the
21692 cookie file, we would warn but not exit, and end up in a state
21693 where no controller could authenticate. Now we exit.
21694 - If we require CookieAuthentication, stop generating a new cookie
21695 every time we change any piece of our config.
21696 - When loading bandwidth history, do not believe any information in
21697 the future. Fixes bug 434.
21698 - When loading entry guard information, do not believe any information
21700 - When we have our clock set far in the future and generate an
21701 onion key, then re-set our clock to be correct, we should not stop
21702 the onion key from getting rotated.
21703 - Clean up torrc sample config file.
21704 - Do not automatically run configure from autogen.sh. This
21705 non-standard behavior tended to annoy people who have built other
21708 o Minor bugfixes (on 0.2.0.x):
21709 - Fix a bug with AutomapHostsOnResolve that would always cause
21710 the second request to fail. Bug reported by Kate. Bugfix on
21712 - Fix a bug in ADDRMAP controller replies that would sometimes
21713 try to print a NULL. Patch from tup.
21714 - Read v3 directory authority keys from the right location.
21715 - Numerous bugfixes to directory voting code.
21718 Changes in version 0.1.2.16 - 2007-08-01
21719 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
21720 remote attacker in certain situations to rewrite the user's torrc
21721 configuration file. This can completely compromise anonymity of users
21722 in most configurations, including those running the Vidalia bundles,
21723 TorK, etc. Or worse.
21725 o Major security fixes:
21726 - Close immediately after missing authentication on control port;
21727 do not allow multiple authentication attempts.
21730 Changes in version 0.2.0.4-alpha - 2007-08-01
21731 This fourth development snapshot fixes a critical security vulnerability
21732 for most users, specifically those running Vidalia, TorK, etc. Everybody
21733 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
21735 o Major security fixes:
21736 - Close immediately after missing authentication on control port;
21737 do not allow multiple authentication attempts.
21739 o Major bugfixes (compilation):
21740 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
21743 o Minor features (performance):
21744 - Be even more aggressive about releasing RAM from small
21745 empty buffers. Thanks to our free-list code, this shouldn't be too
21746 performance-intensive.
21747 - Disable sentinel-based debugging for buffer code: we squashed all
21748 the bugs that this was supposed to detect a long time ago, and
21749 now its only effect is to change our buffer sizes from nice
21750 powers of two (which platform mallocs tend to like) to values
21751 slightly over powers of two (which make some platform mallocs sad).
21752 - Log malloc statistics from mallinfo() on platforms where it
21756 Changes in version 0.2.0.3-alpha - 2007-07-29
21757 This third development snapshot introduces new experimental
21758 blocking-resistance features and a preliminary version of the v3
21759 directory voting design, and includes many other smaller features
21763 - The first pieces of our "bridge" design for blocking-resistance
21764 are implemented. People can run bridge directory authorities;
21765 people can run bridges; and people can configure their Tor clients
21766 with a set of bridges to use as the first hop into the Tor network.
21767 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
21769 - Create listener connections before we setuid to the configured
21770 User and Group. Now non-Windows users can choose port values
21771 under 1024, start Tor as root, and have Tor bind those ports
21772 before it changes to another UID. (Windows users could already
21774 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
21775 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
21776 on "vserver" accounts. (Patch from coderman.)
21777 - Be even more aggressive about separating local traffic from relayed
21778 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
21780 o Major features (experimental):
21781 - First cut of code for "v3 dir voting": directory authorities will
21782 vote on a common network status document rather than each publishing
21783 their own opinion. This code needs more testing and more corner-case
21784 handling before it's ready for use.
21787 - Directory authorities now call routers Fast if their bandwidth is
21788 at least 100KB/s, and consider their bandwidth adequate to be a
21789 Guard if it is at least 250KB/s, no matter the medians. This fix
21790 complements proposal 107. [Bugfix on 0.1.2.x]
21791 - Directory authorities now never mark more than 3 servers per IP as
21792 Valid and Running. (Implements proposal 109, by Kevin Bauer and
21794 - Minor change to organizationName and commonName generation
21795 procedures in TLS certificates during Tor handshakes, to invalidate
21796 some earlier censorware approaches. This is not a long-term
21797 solution, but applying it will give us a bit of time to look into
21798 the epidemiology of countermeasures as they spread.
21800 o Major bugfixes (directory):
21801 - Rewrite directory tokenization code to never run off the end of
21802 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
21804 o Minor features (controller):
21805 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
21806 match requests to applications. (Patch from Robert Hogan.)
21807 - Report address and port correctly on connections to DNSPort. (Patch
21808 from Robert Hogan.)
21809 - Add a RESOLVE command to launch hostname lookups. (Original patch
21810 from Robert Hogan.)
21811 - Add GETINFO status/enough-dir-info to let controllers tell whether
21812 Tor has downloaded sufficient directory information. (Patch
21814 - You can now use the ControlSocket option to tell Tor to listen for
21815 controller connections on Unix domain sockets on systems that
21816 support them. (Patch from Peter Palfrader.)
21817 - STREAM NEW events are generated for DNSPort requests and for
21818 tunneled directory connections. (Patch from Robert Hogan.)
21819 - New "GETINFO address-mappings/*" command to get address mappings
21820 with expiry information. "addr-mappings/*" is now deprecated.
21823 o Minor features (misc):
21824 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
21826 - The tor-gencert tool for v3 directory authorities now creates all
21827 files as readable to the file creator only, and write-protects
21828 the authority identity key.
21829 - When dumping memory usage, list bytes used in buffer memory
21831 - When running with dmalloc, dump more stats on hup and on exit.
21832 - Directory authorities now fail quickly and (relatively) harmlessly
21833 if they generate a network status document that is somehow
21836 o Traffic load balancing improvements:
21837 - If exit bandwidth ever exceeds one third of total bandwidth, then
21838 use the correct formula to weight exit nodes when choosing paths.
21839 (Based on patch from Mike Perry.)
21840 - Choose perfectly fairly among routers when choosing by bandwidth and
21841 weighting by fraction of bandwidth provided by exits. Previously, we
21842 would choose with only approximate fairness, and correct ourselves
21843 if we ran off the end of the list. [Bugfix on 0.1.2.x]
21845 o Performance improvements:
21846 - Be more aggressive with freeing buffer RAM or putting it on the
21848 - Use Critical Sections rather than Mutexes for synchronizing threads
21849 on win32; Mutexes are heavier-weight, and designed for synchronizing
21852 o Deprecated and removed features:
21853 - RedirectExits is now deprecated.
21854 - Stop allowing address masks that do not correspond to bit prefixes.
21855 We have warned about these for a really long time; now it's time
21856 to reject them. (Patch from croup.)
21858 o Minor bugfixes (directory):
21859 - Fix another crash bug related to extra-info caching. (Bug found by
21860 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
21861 - Directories no longer return a "304 not modified" when they don't
21862 have the networkstatus the client asked for. Also fix a memory
21863 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
21864 - We had accidentally labelled 0.1.2.x directory servers as not
21865 suitable for begin_dir requests, and had labelled no directory
21866 servers as suitable for uploading extra-info documents. [Bugfix
21869 o Minor bugfixes (dns):
21870 - Fix a crash when DNSPort is set more than once. (Patch from Robert
21871 Hogan.) [Bugfix on 0.2.0.2-alpha]
21872 - Add DNSPort connections to the global connection list, so that we
21873 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
21875 - Fix a dangling reference that could lead to a crash when DNSPort is
21876 changed or closed (Patch from Robert Hogan.) [Bugfix on
21879 o Minor bugfixes (controller):
21880 - Provide DNS expiry times in GMT, not in local time. For backward
21881 compatibility, ADDRMAP events only provide GMT expiry in an extended
21882 field. "GETINFO address-mappings" always does the right thing.
21883 - Use CRLF line endings properly in NS events.
21884 - Terminate multi-line control events properly. (Original patch
21885 from tup.) [Bugfix on 0.1.2.x-alpha]
21886 - Do not include spaces in SOURCE_ADDR fields in STREAM
21887 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
21890 Changes in version 0.1.2.15 - 2007-07-17
21891 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
21892 problems, fixes compilation on BSD, and fixes a variety of other
21893 bugs. Everybody should upgrade.
21895 o Major bugfixes (compilation):
21896 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
21898 o Major bugfixes (crashes):
21899 - Try even harder not to dereference the first character after
21900 an mmap(). Reported by lodger.
21901 - Fix a crash bug in directory authorities when we re-number the
21902 routerlist while inserting a new router.
21903 - When the cached-routers file is an even multiple of the page size,
21904 don't run off the end and crash. (Fixes bug 455; based on idea
21906 - Fix eventdns.c behavior on Solaris: It is critical to include
21907 orconfig.h _before_ sys/types.h, so that we can get the expected
21908 definition of _FILE_OFFSET_BITS.
21910 o Major bugfixes (security):
21911 - Fix a possible buffer overrun when using BSD natd support. Bug
21913 - When sending destroy cells from a circuit's origin, don't include
21914 the reason for tearing down the circuit. The spec says we didn't,
21915 and now we actually don't. Reported by lodger.
21916 - Keep streamids from different exits on a circuit separate. This
21917 bug may have allowed other routers on a given circuit to inject
21918 cells into streams. Reported by lodger; fixes bug 446.
21919 - If there's a never-before-connected-to guard node in our list,
21920 never choose any guards past it. This way we don't expand our
21921 guard list unless we need to.
21923 o Minor bugfixes (guard nodes):
21924 - Weight guard selection by bandwidth, so that low-bandwidth nodes
21925 don't get overused as guards.
21927 o Minor bugfixes (directory):
21928 - Correctly count the number of authorities that recommend each
21929 version. Previously, we were under-counting by 1.
21930 - Fix a potential crash bug when we load many server descriptors at
21931 once and some of them make others of them obsolete. Fixes bug 458.
21933 o Minor bugfixes (hidden services):
21934 - Stop tearing down the whole circuit when the user asks for a
21935 connection to a port that the hidden service didn't configure.
21938 o Minor bugfixes (misc):
21939 - On Windows, we were preventing other processes from reading
21940 cached-routers while Tor was running. Reported by janbar.
21941 - Fix a possible (but very unlikely) bug in picking routers by
21942 bandwidth. Add a log message to confirm that it is in fact
21943 unlikely. Patch from lodger.
21944 - Backport a couple of memory leak fixes.
21945 - Backport miscellaneous cosmetic bugfixes.
21948 Changes in version 0.2.0.2-alpha - 2007-06-02
21949 o Major bugfixes on 0.2.0.1-alpha:
21950 - Fix an assertion failure related to servers without extra-info digests.
21951 Resolves bugs 441 and 442.
21953 o Minor features (directory):
21954 - Support "If-Modified-Since" when answering HTTP requests for
21955 directories, running-routers documents, and network-status documents.
21956 (There's no need to support it for router descriptors, since those
21957 are downloaded by descriptor digest.)
21959 o Minor build issues:
21960 - Clear up some MIPSPro compiler warnings.
21961 - When building from a tarball on a machine that happens to have SVK
21962 installed, report the micro-revision as whatever version existed
21963 in the tarball, not as "x".
21966 Changes in version 0.2.0.1-alpha - 2007-06-01
21967 This early development snapshot provides new features for people running
21968 Tor as both a client and a server (check out the new RelayBandwidth
21969 config options); lets Tor run as a DNS proxy; and generally moves us
21970 forward on a lot of fronts.
21972 o Major features, server usability:
21973 - New config options RelayBandwidthRate and RelayBandwidthBurst:
21974 a separate set of token buckets for relayed traffic. Right now
21975 relayed traffic is defined as answers to directory requests, and
21976 OR connections that don't have any local circuits on them.
21978 o Major features, client usability:
21979 - A client-side DNS proxy feature to replace the need for
21980 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
21981 for DNS requests on port 9999, use the Tor network to resolve them
21982 anonymously, and send the reply back like a regular DNS server.
21983 The code still only implements a subset of DNS.
21984 - Make PreferTunneledDirConns and TunnelDirConns work even when
21985 we have no cached directory info. This means Tor clients can now
21986 do all of their connections protected by TLS.
21988 o Major features, performance and efficiency:
21989 - Directory authorities accept and serve "extra info" documents for
21990 routers. These documents contain fields from router descriptors
21991 that aren't usually needed, and that use a lot of excess
21992 bandwidth. Once these fields are removed from router descriptors,
21993 the bandwidth savings should be about 60%. [Partially implements
21995 - Servers upload extra-info documents to any authority that accepts
21996 them. Authorities (and caches that have been configured to download
21997 extra-info documents) download them as needed. [Partially implements
21999 - Change the way that Tor buffers data that it is waiting to write.
22000 Instead of queueing data cells in an enormous ring buffer for each
22001 client->OR or OR->OR connection, we now queue cells on a separate
22002 queue for each circuit. This lets us use less slack memory, and
22003 will eventually let us be smarter about prioritizing different kinds
22005 - Use memory pools to allocate cells with better speed and memory
22006 efficiency, especially on platforms where malloc() is inefficient.
22007 - Stop reading on edge connections when their corresponding circuit
22008 buffers are full; start again as the circuits empty out.
22010 o Major features, other:
22011 - Add an HSAuthorityRecordStats option that hidden service authorities
22012 can use to track statistics of overall hidden service usage without
22013 logging information that would be very useful to an attacker.
22014 - Start work implementing multi-level keys for directory authorities:
22015 Add a standalone tool to generate key certificates. (Proposal 103.)
22018 - Directory authorities now call routers Stable if they have an
22019 uptime of at least 30 days, even if that's not the median uptime
22020 in the network. Implements proposal 107, suggested by Kevin Bauer
22023 o Minor fixes (resource management):
22024 - Count the number of open sockets separately from the number
22025 of active connection_t objects. This will let us avoid underusing
22026 our allocated connection limit.
22027 - We no longer use socket pairs to link an edge connection to an
22028 anonymous directory connection or a DirPort test connection.
22029 Instead, we track the link internally and transfer the data
22030 in-process. This saves two sockets per "linked" connection (at the
22031 client and at the server), and avoids the nasty Windows socketpair()
22033 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
22034 for every single inactive connection_t. Free items from the
22035 4k/16k-buffer free lists when they haven't been used for a while.
22037 o Minor features (build):
22038 - Make autoconf search for libevent, openssl, and zlib consistently.
22039 - Update deprecated macros in configure.in.
22040 - When warning about missing headers, tell the user to let us
22041 know if the compile succeeds anyway, so we can downgrade the
22043 - Include the current subversion revision as part of the version
22044 string: either fetch it directly if we're in an SVN checkout, do
22045 some magic to guess it if we're in an SVK checkout, or use
22046 the last-detected version if we're building from a .tar.gz.
22047 Use this version consistently in log messages.
22049 o Minor features (logging):
22050 - Always prepend "Bug: " to any log message about a bug.
22051 - Put a platform string (e.g. "Linux i686") in the startup log
22052 message, so when people paste just their logs, we know if it's
22053 OpenBSD or Windows or what.
22054 - When logging memory usage, break down memory used in buffers by
22057 o Minor features (directory system):
22058 - New config option V2AuthoritativeDirectory that all directory
22059 authorities should set. This will let future authorities choose
22060 not to serve V2 directory information.
22061 - Directory authorities allow multiple router descriptors and/or extra
22062 info documents to be uploaded in a single go. This will make
22063 implementing proposal 104 simpler.
22065 o Minor features (controller):
22066 - Add a new config option __DisablePredictedCircuits designed for
22067 use by the controller, when we don't want Tor to build any circuits
22069 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
22070 so we can exit from the middle of the circuit.
22071 - Implement "getinfo status/circuit-established".
22072 - Implement "getinfo status/version/..." so a controller can tell
22073 whether the current version is recommended, and whether any versions
22074 are good, and how many authorities agree. (Patch from shibz.)
22076 o Minor features (hidden services):
22077 - Allow multiple HiddenServicePort directives with the same virtual
22078 port; when they occur, the user is sent round-robin to one
22079 of the target ports chosen at random. Partially fixes bug 393 by
22080 adding limited ad-hoc round-robining.
22082 o Minor features (other):
22084 - Add a new AutomapHostsOnResolve option: when it is enabled, any
22085 resolve request for hosts matching a given pattern causes Tor to
22086 generate an internal virtual address mapping for that host. This
22087 allows DNSPort to work sensibly with hidden service users. By
22088 default, .exit and .onion addresses are remapped; the list of
22089 patterns can be reconfigured with AutomapHostsSuffixes.
22090 - Add an "-F" option to tor-resolve to force a resolve for a .onion
22091 address. Thanks to the AutomapHostsOnResolve option, this is no
22092 longer a completely silly thing to do.
22093 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
22094 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
22095 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
22096 minus 1 byte: the actual maximum declared bandwidth.
22098 o Removed features:
22099 - Removed support for the old binary "version 0" controller protocol.
22100 This has been deprecated since 0.1.1, and warnings have been issued
22101 since 0.1.2. When we encounter a v0 control message, we now send
22102 back an error and close the connection.
22103 - Remove the old "dns worker" server DNS code: it hasn't been default
22104 since 0.1.2.2-alpha, and all the servers seem to be using the new
22107 o Minor bugfixes (portability):
22108 - Even though Windows is equally happy with / and \ as path separators,
22109 try to use \ consistently on Windows and / consistently on Unix: it
22110 makes the log messages nicer.
22111 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
22112 - Read resolv.conf files correctly on platforms where read() returns
22113 partial results on small file reads.
22115 o Minor bugfixes (directory):
22116 - Correctly enforce that elements of directory objects do not appear
22117 more often than they are allowed to appear.
22118 - When we are reporting the DirServer line we just parsed, we were
22119 logging the second stanza of the key fingerprint, not the first.
22121 o Minor bugfixes (logging):
22122 - When we hit an EOF on a log (probably because we're shutting down),
22123 don't try to remove the log from the list: just mark it as
22124 unusable. (Bulletproofs against bug 222.)
22126 o Minor bugfixes (other):
22127 - In the exitlist script, only consider the most recently published
22128 server descriptor for each server. Also, when the user requests
22129 a list of servers that _reject_ connections to a given address,
22130 explicitly exclude the IPs that also have servers that accept
22131 connections to that address. (Resolves bug 405.)
22132 - Stop allowing hibernating servers to be "stable" or "fast".
22133 - On Windows, we were preventing other processes from reading
22134 cached-routers while Tor was running. (Reported by janbar)
22135 - Make the NodeFamilies config option work. (Reported by
22136 lodger -- it has never actually worked, even though we added it
22138 - Check return values from pthread_mutex functions.
22139 - Don't save non-general-purpose router descriptors to the disk cache,
22140 because we have no way of remembering what their purpose was when
22142 - Add even more asserts to hunt down bug 417.
22143 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
22144 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
22145 Add a log message to confirm that it is in fact unlikely.
22147 o Minor bugfixes (controller):
22148 - Make 'getinfo fingerprint' return a 551 error if we're not a
22149 server, so we match what the control spec claims we do. Reported
22151 - Fix a typo in an error message when extendcircuit fails that
22152 caused us to not follow the \r\n-based delimiter protocol. Reported
22155 o Code simplifications and refactoring:
22156 - Stop passing around circuit_t and crypt_path_t pointers that are
22157 implicit in other procedure arguments.
22158 - Drop the old code to choke directory connections when the
22159 corresponding OR connections got full: thanks to the cell queue
22160 feature, OR conns don't get full any more.
22161 - Make dns_resolve() handle attaching connections to circuits
22162 properly, so the caller doesn't have to.
22163 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
22164 - Keep the connection array as a dynamic smartlist_t, rather than as
22165 a fixed-sized array. This is important, as the number of connections
22166 is becoming increasingly decoupled from the number of sockets.
22169 Changes in version 0.1.2.14 - 2007-05-25
22170 Tor 0.1.2.14 changes the addresses of two directory authorities (this
22171 change especially affects those who serve or use hidden services),
22172 and fixes several other crash- and security-related bugs.
22174 o Directory authority changes:
22175 - Two directory authorities (moria1 and moria2) just moved to new
22176 IP addresses. This change will particularly affect those who serve
22177 or use hidden services.
22179 o Major bugfixes (crashes):
22180 - If a directory server runs out of space in the connection table
22181 as it's processing a begin_dir request, it will free the exit stream
22182 but leave it attached to the circuit, leading to unpredictable
22183 behavior. (Reported by seeess, fixes bug 425.)
22184 - Fix a bug in dirserv_remove_invalid() that would cause authorities
22185 to corrupt memory under some really unlikely scenarios.
22186 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
22187 - Avoid segfaults when reading from mmaped descriptor file. (Reported
22190 o Major bugfixes (security):
22191 - When choosing an entry guard for a circuit, avoid using guards
22192 that are in the same family as the chosen exit -- not just guards
22193 that are exactly the chosen exit. (Reported by lodger.)
22195 o Major bugfixes (resource management):
22196 - If a directory authority is down, skip it when deciding where to get
22197 networkstatus objects or descriptors. Otherwise we keep asking
22198 every 10 seconds forever. Fixes bug 384.
22199 - Count it as a failure if we fetch a valid network-status but we
22200 don't want to keep it. Otherwise we'll keep fetching it and keep
22201 not wanting to keep it. Fixes part of bug 422.
22202 - If all of our dirservers have given us bad or no networkstatuses
22203 lately, then stop hammering them once per minute even when we
22204 think they're failed. Fixes another part of bug 422.
22207 - Actually set the purpose correctly for descriptors inserted with
22208 purpose=controller.
22209 - When we have k non-v2 authorities in our DirServer config,
22210 we ignored the last k authorities in the list when updating our
22212 - Correctly back-off from requesting router descriptors that we are
22213 having a hard time downloading.
22214 - Read resolv.conf files correctly on platforms where read() returns
22215 partial results on small file reads.
22216 - Don't rebuild the entire router store every time we get 32K of
22217 routers: rebuild it when the journal gets very large, or when
22218 the gaps in the store get very large.
22221 - When routers publish SVN revisions in their router descriptors,
22222 authorities now include those versions correctly in networkstatus
22224 - Warn when using a version of libevent before 1.3b to run a server on
22225 OSX or BSD: these versions interact badly with userspace threads.
22228 Changes in version 0.1.2.13 - 2007-04-24
22229 This release features some major anonymity fixes, such as safer path
22230 selection; better client performance; faster bootstrapping, better
22231 address detection, and better DNS support for servers; write limiting as
22232 well as read limiting to make servers easier to run; and a huge pile of
22233 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
22235 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
22236 of the Freenode IRC network, remembering his patience and vision for
22237 free speech on the Internet.
22240 - Fix a memory leak when we ask for "all" networkstatuses and we
22241 get one we don't recognize.
22242 - Add more asserts to hunt down bug 417.
22243 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
22246 Changes in version 0.1.2.12-rc - 2007-03-16
22248 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
22249 directory information requested inside Tor connections (i.e. via
22250 begin_dir cells). It only triggered when the same connection was
22251 serving other data at the same time. Reported by seeess.
22254 - When creating a circuit via the controller, send a 'launched'
22255 event when we're done, so we follow the spec better.
22258 Changes in version 0.1.2.11-rc - 2007-03-15
22259 o Minor bugfixes (controller), reported by daejees:
22260 - Correct the control spec to match how the code actually responds
22261 to 'getinfo addr-mappings/*'.
22262 - The control spec described a GUARDS event, but the code
22263 implemented a GUARD event. Standardize on GUARD, but let people
22264 ask for GUARDS too.
22267 Changes in version 0.1.2.10-rc - 2007-03-07
22268 o Major bugfixes (Windows):
22269 - Do not load the NT services library functions (which may not exist)
22270 just to detect if we're a service trying to shut down. Now we run
22271 on Win98 and friends again.
22273 o Minor bugfixes (other):
22274 - Clarify a couple of log messages.
22275 - Fix a misleading socks5 error number.
22278 Changes in version 0.1.2.9-rc - 2007-03-02
22279 o Major bugfixes (Windows):
22280 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
22281 of the usual GCC "%llu". This prevents a bug when saving 64-bit
22282 int configuration values: the high-order 32 bits would get
22283 truncated. In particular, we were being bitten by the default
22284 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
22285 and maybe also bug 397.)
22287 o Minor bugfixes (performance):
22288 - Use OpenSSL's AES implementation on platforms where it's faster.
22289 This could save us as much as 10% CPU usage.
22291 o Minor bugfixes (server):
22292 - Do not rotate onion key immediately after setting it for the first
22295 o Minor bugfixes (directory authorities):
22296 - Stop calling servers that have been hibernating for a long time
22297 "stable". Also, stop letting hibernating or obsolete servers affect
22298 uptime and bandwidth cutoffs.
22299 - Stop listing hibernating servers in the v1 directory.
22301 o Minor bugfixes (hidden services):
22302 - Upload hidden service descriptors slightly less often, to reduce
22303 load on authorities.
22305 o Minor bugfixes (other):
22306 - Fix an assert that could trigger if a controller quickly set then
22307 cleared EntryNodes. Bug found by Udo van den Heuvel.
22308 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
22310 - Fix a potential race condition in the rpm installer. Found by
22312 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
22313 of 2 as indicating that the server is completely bad; it sometimes
22314 means that the server is just bad for the request in question. (may fix
22315 the last of bug 326.)
22316 - Disable encrypted directory connections when we don't have a server
22317 descriptor for the destination. We'll get this working again in
22321 Changes in version 0.1.2.8-beta - 2007-02-26
22322 o Major bugfixes (crashes):
22323 - Stop crashing when the controller asks us to resetconf more than
22324 one config option at once. (Vidalia 0.0.11 does this.)
22325 - Fix a crash that happened on Win98 when we're given command-line
22326 arguments: don't try to load NT service functions from advapi32.dll
22327 except when we need them. (Bug introduced in 0.1.2.7-alpha;
22329 - Fix a longstanding obscure crash bug that could occur when
22330 we run out of DNS worker processes. (Resolves bug 390.)
22332 o Major bugfixes (hidden services):
22333 - Correctly detect whether hidden service descriptor downloads are
22334 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
22336 o Major bugfixes (accounting):
22337 - When we start during an accounting interval before it's time to wake
22338 up, remember to wake up at the correct time. (May fix bug 342.)
22340 o Minor bugfixes (controller):
22341 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
22342 clear the corresponding on_circuit variable, and remember later
22343 that we don't need to send a redundant CLOSED event. Resolves part
22345 - Report events where a resolve succeeded or where we got a socks
22346 protocol error correctly, rather than calling both of them
22348 - Change reported stream target addresses to IP consistently when
22349 we finally get the IP from an exit node.
22350 - Send log messages to the controller even if they happen to be very
22353 o Minor bugfixes (other):
22354 - Display correct results when reporting which versions are
22355 recommended, and how recommended they are. (Resolves bug 383.)
22356 - Improve our estimates for directory bandwidth to be less random:
22357 guess that an unrecognized directory will have the average bandwidth
22358 from all known directories, not that it will have the average
22359 bandwidth from those directories earlier than it on the list.
22360 - If we start a server with ClientOnly 1, then set ClientOnly to 0
22361 and hup, stop triggering an assert based on an empty onion_key.
22362 - On platforms with no working mmap() equivalent, don't warn the
22363 user when cached-routers doesn't exist.
22364 - Warn the user when mmap() [or its equivalent] fails for some reason
22365 other than file-not-found.
22366 - Don't warn the user when cached-routers.new doesn't exist: that's
22367 perfectly fine when starting up for the first time.
22368 - When EntryNodes are configured, rebuild the guard list to contain,
22369 in order: the EntryNodes that were guards before; the rest of the
22370 EntryNodes; the nodes that were guards before.
22371 - Mask out all signals in sub-threads; only the libevent signal
22372 handler should be processing them. This should prevent some crashes
22373 on some machines using pthreads. (Patch from coderman.)
22374 - Fix switched arguments on memset in the implementation of
22375 tor_munmap() for systems with no mmap() call.
22376 - When Tor receives a router descriptor that it asked for, but
22377 no longer wants (because it has received fresh networkstatuses
22378 in the meantime), do not warn the user. Cache the descriptor if
22379 we're a cache; drop it if we aren't.
22380 - Make earlier entry guards _really_ get retried when the network
22382 - On a malformed DNS reply, always give an error to the corresponding
22384 - Build with recent libevents on platforms that do not define the
22385 nonstandard types "u_int8_t" and friends.
22387 o Minor features (controller):
22388 - Warn the user when an application uses the obsolete binary v0
22389 control protocol. We're planning to remove support for it during
22390 the next development series, so it's good to give people some
22392 - Add STREAM_BW events to report per-entry-stream bandwidth
22393 use. (Patch from Robert Hogan.)
22394 - Rate-limit SIGNEWNYM signals in response to controllers that
22395 impolitely generate them for every single stream. (Patch from
22396 mwenge; closes bug 394.)
22397 - Make REMAP stream events have a SOURCE (cache or exit), and
22398 make them generated in every case where we get a successful
22399 connected or resolved cell.
22401 o Minor bugfixes (performance):
22402 - Call router_have_min_dir_info half as often. (This is showing up in
22403 some profiles, but not others.)
22404 - When using GCC, make log_debug never get called at all, and its
22405 arguments never get evaluated, when no debug logs are configured.
22406 (This is showing up in some profiles, but not others.)
22409 - Remove some never-implemented options. Mark PathlenCoinWeight as
22411 - Implement proposal 106: Stop requiring clients to have well-formed
22412 certificates; stop checking nicknames in certificates. (Clients
22413 have certificates so that they can look like Tor servers, but in
22414 the future we might want to allow them to look like regular TLS
22415 clients instead. Nicknames in certificates serve no purpose other
22416 than making our protocol easier to recognize on the wire.)
22417 - Revise messages on handshake failure again to be even more clear about
22418 which are incoming connections and which are outgoing.
22419 - Discard any v1 directory info that's over 1 month old (for
22420 directories) or over 1 week old (for running-routers lists).
22421 - Do not warn when individual nodes in the configuration's EntryNodes,
22422 ExitNodes, etc are down: warn only when all possible nodes
22423 are down. (Fixes bug 348.)
22424 - Always remove expired routers and networkstatus docs before checking
22425 whether we have enough information to build circuits. (Fixes
22427 - Put a lower-bound on MaxAdvertisedBandwidth.
22430 Changes in version 0.1.2.7-alpha - 2007-02-06
22431 o Major bugfixes (rate limiting):
22432 - Servers decline directory requests much more aggressively when
22433 they're low on bandwidth. Otherwise they end up queueing more and
22434 more directory responses, which can't be good for latency.
22435 - But never refuse directory requests from local addresses.
22436 - Fix a memory leak when sending a 503 response for a networkstatus
22438 - Be willing to read or write on local connections (e.g. controller
22439 connections) even when the global rate limiting buckets are empty.
22440 - If our system clock jumps back in time, don't publish a negative
22441 uptime in the descriptor. Also, don't let the global rate limiting
22442 buckets go absurdly negative.
22443 - Flush local controller connection buffers periodically as we're
22444 writing to them, so we avoid queueing 4+ megabytes of data before
22447 o Major bugfixes (NT services):
22448 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
22449 command-line flag so that admins can override the default by saying
22450 "tor --service install --user "SomeUser"". This will not affect
22451 existing installed services. Also, warn the user that the service
22452 will look for its configuration file in the service user's
22453 %appdata% directory. (We can't do the 'hardwire the user's appdata
22454 directory' trick any more, since we may not have read access to that
22457 o Major bugfixes (other):
22458 - Previously, we would cache up to 16 old networkstatus documents
22459 indefinitely, if they came from nontrusted authorities. Now we
22460 discard them if they are more than 10 days old.
22461 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
22463 - Detect and reject malformed DNS responses containing circular
22465 - If exits are rare enough that we're not marking exits as guards,
22466 ignore exit bandwidth when we're deciding the required bandwidth
22468 - When we're handling a directory connection tunneled over Tor,
22469 don't fill up internal memory buffers with all the data we want
22470 to tunnel; instead, only add it if the OR connection that will
22471 eventually receive it has some room for it. (This can lead to
22472 slowdowns in tunneled dir connections; a better solution will have
22473 to wait for 0.2.0.)
22475 o Minor bugfixes (dns):
22476 - Add some defensive programming to eventdns.c in an attempt to catch
22477 possible memory-stomping bugs.
22478 - Detect and reject DNS replies containing IPv4 or IPv6 records with
22479 an incorrect number of bytes. (Previously, we would ignore the
22481 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
22482 in the correct order, and doesn't crash.
22483 - Free memory held in recently-completed DNS lookup attempts on exit.
22484 This was not a memory leak, but may have been hiding memory leaks.
22485 - Handle TTL values correctly on reverse DNS lookups.
22486 - Treat failure to parse resolv.conf as an error.
22488 o Minor bugfixes (other):
22489 - Fix crash with "tor --list-fingerprint" (reported by seeess).
22490 - When computing clock skew from directory HTTP headers, consider what
22491 time it was when we finished asking for the directory, not what
22493 - Expire socks connections if they spend too long waiting for the
22494 handshake to finish. Previously we would let them sit around for
22495 days, if the connecting application didn't close them either.
22496 - And if the socks handshake hasn't started, don't send a
22497 "DNS resolve socks failed" handshake reply; just close it.
22498 - Stop using C functions that OpenBSD's linker doesn't like.
22499 - Don't launch requests for descriptors unless we have networkstatuses
22500 from at least half of the authorities. This delays the first
22501 download slightly under pathological circumstances, but can prevent
22502 us from downloading a bunch of descriptors we don't need.
22503 - Do not log IPs with TLS failures for incoming TLS
22504 connections. (Fixes bug 382.)
22505 - If the user asks to use invalid exit nodes, be willing to use
22507 - Stop using the reserved ac_cv namespace in our configure script.
22508 - Call stat() slightly less often; use fstat() when possible.
22509 - Refactor the way we handle pending circuits when an OR connection
22510 completes or fails, in an attempt to fix a rare crash bug.
22511 - Only rewrite a conn's address based on X-Forwarded-For: headers
22512 if it's a parseable public IP address; and stop adding extra quotes
22513 to the resulting address.
22516 - Weight directory requests by advertised bandwidth. Now we can
22517 let servers enable write limiting but still allow most clients to
22518 succeed at their directory requests. (We still ignore weights when
22519 choosing a directory authority; I hope this is a feature.)
22522 - Create a new file ReleaseNotes which was the old ChangeLog. The
22523 new ChangeLog file now includes the summaries for all development
22525 - Check for addresses with invalid characters at the exit as well
22526 as at the client, and warn less verbosely when they fail. You can
22527 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
22528 - Adapt a patch from goodell to let the contrib/exitlist script
22529 take arguments rather than require direct editing.
22530 - Inform the server operator when we decide not to advertise a
22531 DirPort due to AccountingMax enabled or a low BandwidthRate. It
22532 was confusing Zax, so now we're hopefully more helpful.
22533 - Bring us one step closer to being able to establish an encrypted
22534 directory tunnel without knowing a descriptor first. Still not
22535 ready yet. As part of the change, now assume we can use a
22536 create_fast cell if we don't know anything about a router.
22537 - Allow exit nodes to use nameservers running on ports other than 53.
22538 - Servers now cache reverse DNS replies.
22539 - Add an --ignore-missing-torrc command-line option so that we can
22540 get the "use sensible defaults if the configuration file doesn't
22541 exist" behavior even when specifying a torrc location on the command
22544 o Minor features (controller):
22545 - Track reasons for OR connection failure; make these reasons
22546 available via the controller interface. (Patch from Mike Perry.)
22547 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
22548 can learn when clients are sending malformed hostnames to Tor.
22549 - Clean up documentation for controller status events.
22550 - Add a REMAP status to stream events to note that a stream's
22551 address has changed because of a cached address or a MapAddress
22555 Changes in version 0.1.2.6-alpha - 2007-01-09
22557 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
22558 connection handles more than 4 gigs in either direction, we crash.
22559 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
22560 advertised exit node, somebody might try to exit from us when
22561 we're bootstrapping and before we've built our descriptor yet.
22562 Refuse the connection rather than crashing.
22565 - Warn if we (as a server) find that we've resolved an address that we
22566 weren't planning to resolve.
22567 - Warn that using select() on any libevent version before 1.1 will be
22568 unnecessarily slow (even for select()).
22569 - Flush ERR-level controller status events just like we currently
22570 flush ERR-level log events, so that a Tor shutdown doesn't prevent
22571 the controller from learning about current events.
22573 o Minor features (more controller status events):
22574 - Implement EXTERNAL_ADDRESS server status event so controllers can
22575 learn when our address changes.
22576 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
22577 can learn when directories reject our descriptor.
22578 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
22579 can learn when a client application is speaking a non-socks protocol
22581 - Implement DANGEROUS_SOCKS client status event so controllers
22582 can learn when a client application is leaking DNS addresses.
22583 - Implement BUG general status event so controllers can learn when
22584 Tor is unhappy about its internal invariants.
22585 - Implement CLOCK_SKEW general status event so controllers can learn
22586 when Tor thinks the system clock is set incorrectly.
22587 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
22588 server status events so controllers can learn when their descriptors
22589 are accepted by a directory.
22590 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
22591 server status events so controllers can learn about Tor's progress in
22592 deciding whether it's reachable from the outside.
22593 - Implement BAD_LIBEVENT general status event so controllers can learn
22594 when we have a version/method combination in libevent that needs to
22596 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
22597 and DNS_USELESS server status events so controllers can learn
22598 about changes to DNS server status.
22600 o Minor features (directory):
22601 - Authorities no longer recommend exits as guards if this would shift
22602 too much load to the exit nodes.
22605 Changes in version 0.1.2.5-alpha - 2007-01-06
22607 - Enable write limiting as well as read limiting. Now we sacrifice
22608 capacity if we're pushing out lots of directory traffic, rather
22609 than overrunning the user's intended bandwidth limits.
22610 - Include TLS overhead when counting bandwidth usage; previously, we
22611 would count only the bytes sent over TLS, but not the bytes used
22613 - Support running the Tor service with a torrc not in the same
22614 directory as tor.exe and default to using the torrc located in
22615 the %appdata%\Tor\ of the user who installed the service. Patch
22617 - Servers now check for the case when common DNS requests are going to
22618 wildcarded addresses (i.e. all getting the same answer), and change
22619 their exit policy to reject *:* if it's happening.
22620 - Implement BEGIN_DIR cells, so we can connect to the directory
22621 server via TLS to do encrypted directory requests rather than
22622 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
22623 config options if you like.
22625 o Minor features (config and docs):
22626 - Start using the state file to store bandwidth accounting data:
22627 the bw_accounting file is now obsolete. We'll keep generating it
22628 for a while for people who are still using 0.1.2.4-alpha.
22629 - Try to batch changes to the state file so that we do as few
22630 disk writes as possible while still storing important things in
22632 - The state file and the bw_accounting file get saved less often when
22633 the AvoidDiskWrites config option is set.
22634 - Make PIDFile work on Windows (untested).
22635 - Add internal descriptions for a bunch of configuration options:
22636 accessible via controller interface and in comments in saved
22638 - Reject *:563 (NNTPS) in the default exit policy. We already reject
22639 NNTP by default, so this seems like a sensible addition.
22640 - Clients now reject hostnames with invalid characters. This should
22641 avoid some inadvertent info leaks. Add an option
22642 AllowNonRFC953Hostnames to disable this behavior, in case somebody
22643 is running a private network with hosts called @, !, and #.
22644 - Add a maintainer script to tell us which options are missing
22645 documentation: "make check-docs".
22646 - Add a new address-spec.txt document to describe our special-case
22647 addresses: .exit, .onion, and .noconnnect.
22649 o Minor features (DNS):
22650 - Ongoing work on eventdns infrastructure: now it has dns server
22651 and ipv6 support. One day Tor will make use of it.
22652 - Add client-side caching for reverse DNS lookups.
22653 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
22654 - When we change nameservers or IP addresses, reset and re-launch
22655 our tests for DNS hijacking.
22657 o Minor features (directory):
22658 - Authorities now specify server versions in networkstatus. This adds
22659 about 2% to the size of compressed networkstatus docs, and allows
22660 clients to tell which servers support BEGIN_DIR and which don't.
22661 The implementation is forward-compatible with a proposed future
22662 protocol version scheme not tied to Tor versions.
22663 - DirServer configuration lines now have an orport= option so
22664 clients can open encrypted tunnels to the authorities without
22665 having downloaded their descriptors yet. Enabled for moria1,
22666 moria2, tor26, and lefkada now in the default configuration.
22667 - Directory servers are more willing to send a 503 "busy" if they
22668 are near their write limit, especially for v1 directory requests.
22669 Now they can use their limited bandwidth for actual Tor traffic.
22670 - Clients track responses with status 503 from dirservers. After a
22671 dirserver has given us a 503, we try not to use it until an hour has
22672 gone by, or until we have no dirservers that haven't given us a 503.
22673 - When we get a 503 from a directory, and we're not a server, we don't
22674 count the failure against the total number of failures allowed
22675 for the thing we're trying to download.
22676 - Report X-Your-Address-Is correctly from tunneled directory
22677 connections; don't report X-Your-Address-Is when it's an internal
22678 address; and never believe reported remote addresses when they're
22680 - Protect against an unlikely DoS attack on directory servers.
22681 - Add a BadDirectory flag to network status docs so that authorities
22682 can (eventually) tell clients about caches they believe to be
22685 o Minor features (controller):
22686 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
22687 - Reimplement GETINFO so that info/names stays in sync with the
22689 - Implement "GETINFO fingerprint".
22690 - Implement "SETEVENTS GUARD" so controllers can get updates on
22691 entry guard status as it changes.
22693 o Minor features (clean up obsolete pieces):
22694 - Remove some options that have been deprecated since at least
22695 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
22696 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
22697 to set log options.
22698 - We no longer look for identity and onion keys in "identity.key" and
22699 "onion.key" -- these were replaced by secret_id_key and
22700 secret_onion_key in 0.0.8pre1.
22701 - We no longer require unrecognized directory entries to be
22704 o Major bugfixes (security):
22705 - Stop sending the HttpProxyAuthenticator string to directory
22706 servers when directory connections are tunnelled through Tor.
22707 - Clients no longer store bandwidth history in the state file.
22708 - Do not log introduction points for hidden services if SafeLogging
22710 - When generating bandwidth history, round down to the nearest
22711 1k. When storing accounting data, round up to the nearest 1k.
22712 - When we're running as a server, remember when we last rotated onion
22713 keys, so that we will rotate keys once they're a week old even if
22714 we never stay up for a week ourselves.
22716 o Major bugfixes (other):
22717 - Fix a longstanding bug in eventdns that prevented the count of
22718 timed-out resolves from ever being reset. This bug caused us to
22719 give up on a nameserver the third time it timed out, and try it
22720 10 seconds later... and to give up on it every time it timed out
22722 - Take out the '5 second' timeout from the connection retry
22723 schedule. Now the first connect attempt will wait a full 10
22724 seconds before switching to a new circuit. Perhaps this will help
22725 a lot. Based on observations from Mike Perry.
22726 - Fix a bug on the Windows implementation of tor_mmap_file() that
22727 would prevent the cached-routers file from ever loading. Reported
22731 - Fix an assert failure when a directory authority sets
22732 AuthDirRejectUnlisted and then receives a descriptor from an
22733 unlisted router. Reported by seeess.
22734 - Avoid a double-free when parsing malformed DirServer lines.
22735 - Fix a bug when a BSD-style PF socket is first used. Patch from
22737 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
22738 to resolve an address at a given exit node even when they ask for
22740 - Servers no longer ever list themselves in their "family" line,
22741 even if configured to do so. This makes it easier to configure
22742 family lists conveniently.
22743 - When running as a server, don't fall back to 127.0.0.1 when no
22744 nameservers are configured in /etc/resolv.conf; instead, make the
22745 user fix resolv.conf or specify nameservers explicitly. (Resolves
22747 - Stop accepting certain malformed ports in configured exit policies.
22748 - Don't re-write the fingerprint file every restart, unless it has
22750 - Stop warning when a single nameserver fails: only warn when _all_ of
22751 our nameservers have failed. Also, when we only have one nameserver,
22752 raise the threshold for deciding that the nameserver is dead.
22753 - Directory authorities now only decide that routers are reachable
22754 if their identity keys are as expected.
22755 - When the user uses bad syntax in the Log config line, stop
22756 suggesting other bad syntax as a replacement.
22757 - Correctly detect ipv6 DNS capability on OpenBSD.
22759 o Minor bugfixes (controller):
22760 - Report the circuit number correctly in STREAM CLOSED events. Bug
22761 reported by Mike Perry.
22762 - Do not report bizarre values for results of accounting GETINFOs
22763 when the last second's write or read exceeds the allotted bandwidth.
22764 - Report "unrecognized key" rather than an empty string when the
22765 controller tries to fetch a networkstatus that doesn't exist.
22768 Changes in version 0.1.1.26 - 2006-12-14
22769 o Security bugfixes:
22770 - Stop sending the HttpProxyAuthenticator string to directory
22771 servers when directory connections are tunnelled through Tor.
22772 - Clients no longer store bandwidth history in the state file.
22773 - Do not log introduction points for hidden services if SafeLogging
22777 - Fix an assert failure when a directory authority sets
22778 AuthDirRejectUnlisted and then receives a descriptor from an
22779 unlisted router (reported by seeess).
22782 Changes in version 0.1.2.4-alpha - 2006-12-03
22784 - Add support for using natd; this allows FreeBSDs earlier than
22785 5.1.2 to have ipfw send connections through Tor without using
22786 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
22789 - Make all connections to addresses of the form ".noconnect"
22790 immediately get closed. This lets application/controller combos
22791 successfully test whether they're talking to the same Tor by
22792 watching for STREAM events.
22793 - Make cross.sh cross-compilation script work even when autogen.sh
22794 hasn't been run. (Patch from Michael Mohr.)
22795 - Statistics dumped by -USR2 now include a breakdown of public key
22796 operations, for profiling.
22799 - Fix a major leak when directory authorities parse their
22800 approved-routers list, a minor memory leak when we fail to pick
22801 an exit node, and a few rare leaks on errors.
22802 - Handle TransPort connections even when the server sends data before
22803 the client sends data. Previously, the connection would just hang
22804 until the client sent data. (Patch from tup based on patch from
22806 - Avoid assert failure when our cached-routers file is empty on
22810 - Don't log spurious warnings when we see a circuit close reason we
22811 don't recognize; it's probably just from a newer version of Tor.
22812 - Have directory authorities allow larger amounts of drift in uptime
22813 without replacing the server descriptor: previously, a server that
22814 restarted every 30 minutes could have 48 "interesting" descriptors
22816 - Start linking to the Tor specification and Tor reference manual
22817 correctly in the Windows installer.
22818 - Add Vidalia to the OS X uninstaller script, so when we uninstall
22819 Tor/Privoxy we also uninstall Vidalia.
22820 - Resume building on Irix64, and fix a lot of warnings from its
22821 MIPSpro C compiler.
22822 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
22823 when we're running as a client.
22826 Changes in version 0.1.1.25 - 2006-11-04
22828 - When a client asks us to resolve (rather than connect to)
22829 an address, and we have a cached answer, give them the cached
22830 answer. Previously, we would give them no answer at all.
22831 - We were building exactly the wrong circuits when we predict
22832 hidden service requirements, meaning Tor would have to build all
22833 its circuits on demand.
22834 - If none of our live entry guards have a high uptime, but we
22835 require a guard with a high uptime, try adding a new guard before
22836 we give up on the requirement. This patch should make long-lived
22837 connections more stable on average.
22838 - When testing reachability of our DirPort, don't launch new
22839 tests when there's already one in progress -- unreachable
22840 servers were stacking up dozens of testing streams.
22842 o Security bugfixes:
22843 - When the user sends a NEWNYM signal, clear the client-side DNS
22844 cache too. Otherwise we continue to act on previous information.
22847 - Avoid a memory corruption bug when creating a hash table for
22849 - Avoid possibility of controller-triggered crash when misusing
22850 certain commands from a v0 controller on platforms that do not
22851 handle printf("%s",NULL) gracefully.
22852 - Avoid infinite loop on unexpected controller input.
22853 - Don't log spurious warnings when we see a circuit close reason we
22854 don't recognize; it's probably just from a newer version of Tor.
22855 - Add Vidalia to the OS X uninstaller script, so when we uninstall
22856 Tor/Privoxy we also uninstall Vidalia.
22859 Changes in version 0.1.2.3-alpha - 2006-10-29
22861 - Prepare for servers to publish descriptors less often: never
22862 discard a descriptor simply for being too old until either it is
22863 recommended by no authorities, or until we get a better one for
22864 the same router. Make caches consider retaining old recommended
22865 routers for even longer.
22866 - If most authorities set a BadExit flag for a server, clients
22867 don't think of it as a general-purpose exit. Clients only consider
22868 authorities that advertise themselves as listing bad exits.
22869 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
22870 headers for content, so that we can work better in the presence of
22871 caching HTTP proxies.
22872 - Allow authorities to list nodes as bad exits by fingerprint or by
22875 o Minor features, controller:
22876 - Add a REASON field to CIRC events; for backward compatibility, this
22877 field is sent only to controllers that have enabled the extended
22878 event format. Also, add additional reason codes to explain why
22879 a given circuit has been destroyed or truncated. (Patches from
22881 - Add a REMOTE_REASON field to extended CIRC events to tell the
22882 controller about why a remote OR told us to close a circuit.
22883 - Stream events also now have REASON and REMOTE_REASON fields,
22884 working much like those for circuit events.
22885 - There's now a GETINFO ns/... field so that controllers can ask Tor
22886 about the current status of a router.
22887 - A new event type "NS" to inform a controller when our opinion of
22888 a router's status has changed.
22889 - Add a GETINFO events/names and GETINFO features/names so controllers
22890 can tell which events and features are supported.
22891 - A new CLEARDNSCACHE signal to allow controllers to clear the
22892 client-side DNS cache without expiring circuits.
22894 o Security bugfixes:
22895 - When the user sends a NEWNYM signal, clear the client-side DNS
22896 cache too. Otherwise we continue to act on previous information.
22899 - Avoid sending junk to controllers or segfaulting when a controller
22900 uses EVENT_NEW_DESC with verbose nicknames.
22901 - Stop triggering asserts if the controller tries to extend hidden
22902 service circuits (reported by mwenge).
22903 - Avoid infinite loop on unexpected controller input.
22904 - When the controller does a "GETINFO network-status", tell it
22905 about even those routers whose descriptors are very old, and use
22906 long nicknames where appropriate.
22907 - Change NT service functions to be loaded on demand. This lets us
22908 build with MinGW without breaking Tor for Windows 98 users.
22909 - Do DirPort reachability tests less often, since a single test
22910 chews through many circuits before giving up.
22911 - In the hidden service example in torrc.sample, stop recommending
22912 esoteric and discouraged hidden service options.
22913 - When stopping an NT service, wait up to 10 sec for it to actually
22914 stop. Patch from Matt Edman; resolves bug 295.
22915 - Fix handling of verbose nicknames with ORCONN controller events:
22916 make them show up exactly when requested, rather than exactly when
22918 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
22919 printing a duplicate "$" in the keys we send (reported by mwenge).
22920 - Correctly set maximum connection limit on Cygwin. (This time
22922 - Try to detect Windows correctly when cross-compiling.
22923 - Detect the size of the routers file correctly even if it is
22924 corrupted (on systems without mmap) or not page-aligned (on systems
22925 with mmap). This bug was harmless.
22926 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
22927 to open a stream fails; now we do in more cases. This should
22928 make clients able to find a good exit faster in some cases, since
22929 unhandleable requests will now get an error rather than timing out.
22930 - Resolve two memory leaks when rebuilding the on-disk router cache
22931 (reported by fookoowa).
22932 - Clean up minor code warnings suggested by the MIPSpro C compiler,
22933 and reported by some Centos users.
22934 - Controller signals now work on non-Unix platforms that don't define
22935 SIGUSR1 and SIGUSR2 the way we expect.
22936 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
22937 values before failing, and always enables eventdns.
22938 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
22939 Try to fix this in configure.in by checking for most functions
22940 before we check for libevent.
22943 Changes in version 0.1.2.2-alpha - 2006-10-07
22945 - Make our async eventdns library on-by-default for Tor servers,
22946 and plan to deprecate the separate dnsworker threads.
22947 - Add server-side support for "reverse" DNS lookups (using PTR
22948 records so clients can determine the canonical hostname for a given
22949 IPv4 address). Only supported by servers using eventdns; servers
22950 now announce in their descriptors whether they support eventdns.
22951 - Specify and implement client-side SOCKS5 interface for reverse DNS
22952 lookups (see doc/socks-extensions.txt).
22953 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
22954 connect to directory servers through Tor. Previously, clients needed
22955 to find Tor exits to make private connections to directory servers.
22956 - Avoid choosing Exit nodes for entry or middle hops when the
22957 total bandwidth available from non-Exit nodes is much higher than
22958 the total bandwidth available from Exit nodes.
22959 - Workaround for name servers (like Earthlink's) that hijack failing
22960 DNS requests and replace the no-such-server answer with a "helpful"
22961 redirect to an advertising-driven search portal. Also work around
22962 DNS hijackers who "helpfully" decline to hijack known-invalid
22963 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
22964 lets you turn it off.
22965 - Send out a burst of long-range padding cells once we've established
22966 that we're reachable. Spread them over 4 circuits, so hopefully
22967 a few will be fast. This exercises our bandwidth and bootstraps
22968 us into the directory more quickly.
22970 o New/improved config options:
22971 - Add new config option "ResolvConf" to let the server operator
22972 choose an alternate resolve.conf file when using eventdns.
22973 - Add an "EnforceDistinctSubnets" option to control our "exclude
22974 servers on the same /16" behavior. It's still on by default; this
22975 is mostly for people who want to operate private test networks with
22976 all the machines on the same subnet.
22977 - If one of our entry guards is on the ExcludeNodes list, or the
22978 directory authorities don't think it's a good guard, treat it as
22979 if it were unlisted: stop using it as a guard, and throw it off
22980 the guards list if it stays that way for a long time.
22981 - Allow directory authorities to be marked separately as authorities
22982 for the v1 directory protocol, the v2 directory protocol, and
22983 as hidden service directories, to make it easier to retire old
22984 authorities. V1 authorities should set "HSAuthoritativeDir 1"
22985 to continue being hidden service authorities too.
22986 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
22988 o Minor features, controller:
22989 - Fix CIRC controller events so that controllers can learn the
22990 identity digests of non-Named servers used in circuit paths.
22991 - Let controllers ask for more useful identifiers for servers. Instead
22992 of learning identity digests for un-Named servers and nicknames
22993 for Named servers, the new identifiers include digest, nickname,
22994 and indication of Named status. Off by default; see control-spec.txt
22995 for more information.
22996 - Add a "getinfo address" controller command so it can display Tor's
22997 best guess to the user.
22998 - New controller event to alert the controller when our server
22999 descriptor has changed.
23000 - Give more meaningful errors on controller authentication failure.
23002 o Minor features, other:
23003 - When asked to resolve a hostname, don't use non-exit servers unless
23004 requested to do so. This allows servers with broken DNS to be
23005 useful to the network.
23006 - Divide eventdns log messages into warn and info messages.
23007 - Reserve the nickname "Unnamed" for routers that can't pick
23008 a hostname: any router can call itself Unnamed; directory
23009 authorities will never allocate Unnamed to any particular router;
23010 clients won't believe that any router is the canonical Unnamed.
23011 - Only include function names in log messages for info/debug messages.
23012 For notice/warn/err, the content of the message should be clear on
23013 its own, and printing the function name only confuses users.
23014 - Avoid some false positives during reachability testing: don't try
23015 to test via a server that's on the same /24 as us.
23016 - If we fail to build a circuit to an intended enclave, and it's
23017 not mandatory that we use that enclave, stop wanting it.
23018 - When eventdns is enabled, allow multithreaded builds on NetBSD and
23019 OpenBSD. (We had previously disabled threads on these platforms
23020 because they didn't have working thread-safe resolver functions.)
23022 o Major bugfixes, anonymity/security:
23023 - If a client asked for a server by name, and there's a named server
23024 in our network-status but we don't have its descriptor yet, we
23025 could return an unnamed server instead.
23026 - Fix NetBSD bug that could allow someone to force uninitialized RAM
23027 to be sent to a server's DNS resolver. This only affects NetBSD
23028 and other platforms that do not bounds-check tolower().
23029 - Reject (most) attempts to use Tor circuits with length one. (If
23030 many people start using Tor as a one-hop proxy, exit nodes become
23031 a more attractive target for compromise.)
23032 - Just because your DirPort is open doesn't mean people should be
23033 able to remotely teach you about hidden service descriptors. Now
23034 only accept rendezvous posts if you've got HSAuthoritativeDir set.
23036 o Major bugfixes, other:
23037 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
23038 - When a client asks the server to resolve (not connect to)
23039 an address, and it has a cached answer, give them the cached answer.
23040 Previously, the server would give them no answer at all.
23041 - Allow really slow clients to not hang up five minutes into their
23042 directory downloads (suggested by Adam J. Richter).
23043 - We were building exactly the wrong circuits when we anticipated
23044 hidden service requirements, meaning Tor would have to build all
23045 its circuits on demand.
23046 - Avoid crashing when we mmap a router cache file of size 0.
23047 - When testing reachability of our DirPort, don't launch new
23048 tests when there's already one in progress -- unreachable
23049 servers were stacking up dozens of testing streams.
23051 o Minor bugfixes, correctness:
23052 - If we're a directory mirror and we ask for "all" network status
23053 documents, we would discard status documents from authorities
23054 we don't recognize.
23055 - Avoid a memory corruption bug when creating a hash table for
23057 - Avoid controller-triggered crash when misusing certain commands
23058 from a v0 controller on platforms that do not handle
23059 printf("%s",NULL) gracefully.
23060 - Don't crash when a controller sends a third argument to an
23061 "extendcircuit" request.
23062 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
23063 response; fix error code when "getinfo dir/status/" fails.
23064 - Avoid crash when telling controller stream-status and a stream
23066 - Patch from Adam Langley to fix assert() in eventdns.c.
23067 - Fix a debug log message in eventdns to say "X resolved to Y"
23068 instead of "X resolved to X".
23069 - Make eventdns give strings for DNS errors, not just error numbers.
23070 - Track unreachable entry guards correctly: don't conflate
23071 'unreachable by us right now' with 'listed as down by the directory
23072 authorities'. With the old code, if a guard was unreachable by
23073 us but listed as running, it would clog our guard list forever.
23074 - Behave correctly in case we ever have a network with more than
23075 2GB/s total advertised capacity.
23076 - Make TrackExitHosts case-insensitive, and fix the behavior of
23077 ".suffix" TrackExitHosts items to avoid matching in the middle of
23079 - Finally fix the openssl warnings from newer gccs that believe that
23080 ignoring a return value is okay, but casting a return value and
23081 then ignoring it is a sign of madness.
23082 - Prevent the contrib/exitlist script from printing the same
23083 result more than once.
23084 - Patch from Steve Hildrey: Generate network status correctly on
23085 non-versioning dirservers.
23086 - Don't listen to the X-Your-Address-Is hint if you did the lookup
23087 via Tor; otherwise you'll think you're the exit node's IP address.
23089 o Minor bugfixes, performance:
23090 - Two small performance improvements on parsing descriptors.
23091 - Major performance improvement on inserting descriptors: change
23092 algorithm from O(n^2) to O(n).
23093 - Make the common memory allocation path faster on machines where
23094 malloc(0) returns a pointer.
23095 - Start remembering X-Your-Address-Is directory hints even if you're
23096 a client, so you can become a server more smoothly.
23097 - Avoid duplicate entries on MyFamily line in server descriptor.
23099 o Packaging, features:
23100 - Remove architecture from OS X builds. The official builds are
23101 now universal binaries.
23102 - The Debian package now uses --verify-config when (re)starting,
23103 to distinguish configuration errors from other errors.
23104 - Update RPMs to require libevent 1.1b.
23106 o Packaging, bugfixes:
23107 - Patches so Tor builds with MinGW on Windows.
23108 - Patches so Tor might run on Cygwin again.
23109 - Resume building on non-gcc compilers and ancient gcc. Resume
23110 building with the -O0 compile flag. Resume building cleanly on
23112 - Run correctly on OS X platforms with case-sensitive filesystems.
23113 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
23114 - Add autoconf checks so Tor can build on Solaris x86 again.
23117 - Documented (and renamed) ServerDNSSearchDomains and
23118 ServerDNSResolvConfFile options.
23119 - Be clearer that the *ListenAddress directives can be repeated
23123 Changes in version 0.1.1.24 - 2006-09-29
23125 - Allow really slow clients to not hang up five minutes into their
23126 directory downloads (suggested by Adam J. Richter).
23127 - Fix major performance regression from 0.1.0.x: instead of checking
23128 whether we have enough directory information every time we want to
23129 do something, only check when the directory information has changed.
23130 This should improve client CPU usage by 25-50%.
23131 - Don't crash if, after a server has been running for a while,
23132 it can't resolve its hostname.
23135 - Allow Tor to start when RunAsDaemon is set but no logs are set.
23136 - Don't crash when the controller receives a third argument to an
23137 "extendcircuit" request.
23138 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
23139 response; fix error code when "getinfo dir/status/" fails.
23140 - Fix configure.in to not produce broken configure files with
23141 more recent versions of autoconf. Thanks to Clint for his auto*
23143 - Fix security bug on NetBSD that could allow someone to force
23144 uninitialized RAM to be sent to a server's DNS resolver. This
23145 only affects NetBSD and other platforms that do not bounds-check
23147 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
23148 methods: these are known to be buggy.
23149 - If we're a directory mirror and we ask for "all" network status
23150 documents, we would discard status documents from authorities
23151 we don't recognize.
23154 Changes in version 0.1.2.1-alpha - 2006-08-27
23156 - Add "eventdns" async dns library from Adam Langley, tweaked to
23157 build on OSX and Windows. Only enabled if you pass the
23158 --enable-eventdns argument to configure.
23159 - Allow servers with no hostname or IP address to learn their
23160 IP address by asking the directory authorities. This code only
23161 kicks in when you would normally have exited with a "no address"
23162 error. Nothing's authenticated, so use with care.
23163 - Rather than waiting a fixed amount of time between retrying
23164 application connections, we wait only 5 seconds for the first,
23165 10 seconds for the second, and 15 seconds for each retry after
23166 that. Hopefully this will improve the expected user experience.
23167 - Patch from Tup to add support for transparent AP connections:
23168 this basically bundles the functionality of trans-proxy-tor
23169 into the Tor mainline. Now hosts with compliant pf/netfilter
23170 implementations can redirect TCP connections straight to Tor
23171 without diverting through SOCKS. Needs docs.
23172 - Busy directory servers save lots of memory by spooling server
23173 descriptors, v1 directories, and v2 networkstatus docs to buffers
23174 as needed rather than en masse. Also mmap the cached-routers
23175 files, so we don't need to keep the whole thing in memory too.
23176 - Automatically avoid picking more than one node from the same
23177 /16 network when constructing a circuit.
23178 - Revise and clean up the torrc.sample that we ship with; add
23179 a section for BandwidthRate and BandwidthBurst.
23182 - Split circuit_t into origin_circuit_t and or_circuit_t, and
23183 split connection_t into edge, or, dir, control, and base structs.
23184 These will save quite a bit of memory on busy servers, and they'll
23185 also help us track down bugs in the code and bugs in the spec.
23186 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
23187 or later. Log when we are doing this, so we can diagnose it when
23188 it fails. (Also, recommend libevent 1.1b for kqueue and
23189 win32 methods; deprecate libevent 1.0b harder; make libevent
23190 recommendation system saner.)
23191 - Start being able to build universal binaries on OS X (thanks
23193 - Export the default exit policy via the control port, so controllers
23194 don't need to guess what it is / will be later.
23195 - Add a man page entry for ProtocolWarnings.
23196 - Add TestVia config option to the man page.
23197 - Remove even more protocol-related warnings from Tor server logs,
23198 such as bad TLS handshakes and malformed begin cells.
23199 - Stop fetching descriptors if you're not a dir mirror and you
23200 haven't tried to establish any circuits lately. [This currently
23201 causes some dangerous behavior, because when you start up again
23202 you'll use your ancient server descriptors.]
23203 - New DirPort behavior: if you have your dirport set, you download
23204 descriptors aggressively like a directory mirror, whether or not
23205 your ORPort is set.
23206 - Get rid of the router_retry_connections notion. Now routers
23207 no longer try to rebuild long-term connections to directory
23208 authorities, and directory authorities no longer try to rebuild
23209 long-term connections to all servers. We still don't hang up
23210 connections in these two cases though -- we need to look at it
23211 more carefully to avoid flapping, and we likely need to wait til
23212 0.1.1.x is obsolete.
23213 - Drop compatibility with obsolete Tors that permit create cells
23214 to have the wrong circ_id_type.
23215 - Re-enable per-connection rate limiting. Get rid of the "OP
23216 bandwidth" concept. Lay groundwork for "bandwidth classes" --
23217 separate global buckets that apply depending on what sort of conn
23219 - Start publishing one minute or so after we find our ORPort
23220 to be reachable. This will help reduce the number of descriptors
23221 we have for ourselves floating around, since it's quite likely
23222 other things (e.g. DirPort) will change during that minute too.
23223 - Fork the v1 directory protocol into its own spec document,
23224 and mark dir-spec.txt as the currently correct (v2) spec.
23227 - When we find our DirPort to be reachable, publish a new descriptor
23228 so we'll tell the world (reported by pnx).
23229 - Publish a new descriptor after we hup/reload. This is important
23230 if our config has changed such that we'll want to start advertising
23231 our DirPort now, etc.
23232 - Allow Tor to start when RunAsDaemon is set but no logs are set.
23233 - When we have a state file we cannot parse, tell the user and
23234 move it aside. Now we avoid situations where the user starts
23235 Tor in 1904, Tor writes a state file with that timestamp in it,
23236 the user fixes her clock, and Tor refuses to start.
23237 - Fix configure.in to not produce broken configure files with
23238 more recent versions of autoconf. Thanks to Clint for his auto*
23240 - "tor --verify-config" now exits with -1(255) or 0 depending on
23241 whether the config options are bad or good.
23242 - Resolve bug 321 when using dnsworkers: append a period to every
23243 address we resolve at the exit node, so that we do not accidentally
23244 pick up local addresses, and so that failing searches are retried
23245 in the resolver search domains. (This is already solved for
23246 eventdns.) (This breaks Blossom servers for now.)
23247 - If we are using an exit enclave and we can't connect, e.g. because
23248 its webserver is misconfigured to not listen on localhost, then
23249 back off and try connecting from somewhere else before we fail.
23252 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
23253 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
23254 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
23255 when the IP address is mapped through MapAddress to a hostname.
23256 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
23257 useless IPv6 DNS resolves.
23258 - Patch suggested by Karsten Loesing: respond to SIGNAL command
23259 before we execute the signal, in case the signal shuts us down.
23260 - Clean up AllowInvalidNodes man page entry.
23261 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
23262 - Add more asserts to track down an assert error on a windows Tor
23263 server with connection_add being called with socket == -1.
23264 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
23265 - Fix misleading log messages: an entry guard that is "unlisted",
23266 as well as not known to be "down" (because we've never heard
23267 of it), is not therefore "up".
23268 - Remove code to special-case "-cvs" ending, since it has not
23269 actually mattered since 0.0.9.
23270 - Make our socks5 handling more robust to broken socks clients:
23271 throw out everything waiting on the buffer in between socks
23272 handshake phases, since they can't possibly (so the theory
23273 goes) have predicted what we plan to respond to them.
23276 Changes in version 0.1.1.23 - 2006-07-30
23278 - Fast Tor servers, especially exit nodes, were triggering asserts
23279 due to a bug in handling the list of pending DNS resolves. Some
23280 bugs still remain here; we're hunting them.
23281 - Entry guards could crash clients by sending unexpected input.
23282 - More fixes on reachability testing: if you find yourself reachable,
23283 then don't ever make any client requests (so you stop predicting
23284 circuits), then hup or have your clock jump, then later your IP
23285 changes, you won't think circuits are working, so you won't try to
23286 test reachability, so you won't publish.
23289 - Avoid a crash if the controller does a resetconf firewallports
23290 and then a setconf fascistfirewall=1.
23291 - Avoid an integer underflow when the dir authority decides whether
23292 a router is stable: we might wrongly label it stable, and compute
23293 a slightly wrong median stability, when a descriptor is published
23295 - Fix a place where we might trigger an assert if we can't build our
23296 own server descriptor yet.
23299 Changes in version 0.1.1.22 - 2006-07-05
23301 - Fix a big bug that was causing servers to not find themselves
23302 reachable if they changed IP addresses. Since only 0.1.1.22+
23303 servers can do reachability testing correctly, now we automatically
23304 make sure to test via one of these.
23305 - Fix to allow clients and mirrors to learn directory info from
23306 descriptor downloads that get cut off partway through.
23307 - Directory authorities had a bug in deciding if a newly published
23308 descriptor was novel enough to make everybody want a copy -- a few
23309 servers seem to be publishing new descriptors many times a minute.
23311 - Fix a rare bug that was causing some servers to complain about
23312 "closing wedged cpuworkers" and skip some circuit create requests.
23313 - Make the Exit flag in directory status documents actually work.
23316 Changes in version 0.1.1.21 - 2006-06-10
23317 o Crash and assert fixes from 0.1.1.20:
23318 - Fix a rare crash on Tor servers that have enabled hibernation.
23319 - Fix a seg fault on startup for Tor networks that use only one
23320 directory authority.
23321 - Fix an assert from a race condition that occurs on Tor servers
23322 while exiting, where various threads are trying to log that they're
23323 exiting, and delete the logs, at the same time.
23324 - Make our unit tests pass again on certain obscure platforms.
23327 - Add support for building SUSE RPM packages.
23328 - Speed up initial bootstrapping for clients: if we are making our
23329 first ever connection to any entry guard, then don't mark it down
23331 - When only one Tor server in the network is labelled as a guard,
23332 and we've already picked him, we would cycle endlessly picking him
23333 again, being unhappy about it, etc. Now we specifically exclude
23334 current guards when picking a new guard.
23335 - Servers send create cells more reliably after the TLS connection
23336 is established: we were sometimes forgetting to send half of them
23337 when we had more than one pending.
23338 - If we get a create cell that asks us to extend somewhere, but the
23339 Tor server there doesn't match the expected digest, we now send
23340 a destroy cell back, rather than silently doing nothing.
23341 - Make options->RedirectExit work again.
23342 - Make cookie authentication for the controller work again.
23343 - Stop being picky about unusual characters in the arguments to
23344 mapaddress. It's none of our business.
23345 - Add a new config option "TestVia" that lets you specify preferred
23346 middle hops to use for test circuits. Perhaps this will let me
23347 debug the reachability problems better.
23349 o Log / documentation fixes:
23350 - If we're a server and some peer has a broken TLS certificate, don't
23351 log about it unless ProtocolWarnings is set, i.e., we want to hear
23352 about protocol violations by others.
23353 - Fix spelling of VirtualAddrNetwork in man page.
23354 - Add a better explanation at the top of the autogenerated torrc file
23355 about what happened to our old torrc.
23358 Changes in version 0.1.1.20 - 2006-05-23
23360 - Downgrade a log severity where servers complain that they're
23362 - Avoid a compile warning on FreeBSD.
23363 - Remove string size limit on NEWDESC messages; solve bug 291.
23364 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
23365 more thoroughly when we're running on windows.
23368 Changes in version 0.1.1.19-rc - 2006-05-03
23370 - Regenerate our local descriptor if it's dirty and we try to use
23371 it locally (e.g. if it changes during reachability detection).
23372 - If we setconf our ORPort to 0, we continued to listen on the
23373 old ORPort and receive connections.
23374 - Avoid a second warning about machine/limits.h on Debian
23376 - Be willing to add our own routerinfo into the routerlist.
23377 Now authorities will include themselves in their directories
23378 and network-statuses.
23379 - Stop trying to upload rendezvous descriptors to every
23380 directory authority: only try the v1 authorities.
23381 - Servers no longer complain when they think they're not
23382 registered with the directory authorities. There were too many
23384 - Backport dist-rpm changes so rpms can be built without errors.
23387 - Implement an option, VirtualAddrMask, to set which addresses
23388 get handed out in response to mapaddress requests. This works
23389 around a bug in tsocks where 127.0.0.0/8 is never socksified.
23392 Changes in version 0.1.1.18-rc - 2006-04-10
23394 - Work harder to download live network-statuses from all the
23395 directory authorities we know about. Improve the threshold
23396 decision logic so we're more robust to edge cases.
23397 - When fetching rendezvous descriptors, we were willing to ask
23398 v2 authorities too, which would always return 404.
23401 - Stop listing down or invalid nodes in the v1 directory. This will
23402 reduce its bulk by about 1/3, and reduce load on directory
23404 - When deciding whether a router is Fast or Guard-worthy, consider
23405 his advertised BandwidthRate and not just the BandwidthCapacity.
23406 - No longer ship INSTALL and README files -- they are useless now.
23407 - Force rpmbuild to behave and honor target_cpu.
23408 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
23409 - Start to include translated versions of the tor-doc-*.html
23410 files, along with the screenshots. Still needs more work.
23411 - Start sending back 512 and 451 errors if mapaddress fails,
23412 rather than not sending anything back at all.
23413 - When we fail to bind or listen on an incoming or outgoing
23414 socket, we should close it before failing. otherwise we just
23415 leak it. (thanks to weasel for finding.)
23416 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
23417 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
23418 - Make NoPublish (even though deprecated) work again.
23419 - Fix a minor security flaw where a versioning auth dirserver
23420 could list a recommended version many times in a row to make
23421 clients more convinced that it's recommended.
23422 - Fix crash bug if there are two unregistered servers running
23423 with the same nickname, one of them is down, and you ask for
23424 them by nickname in your EntryNodes or ExitNodes. Also, try
23425 to pick the one that's running rather than an arbitrary one.
23426 - Fix an infinite loop we could hit if we go offline for too long.
23427 - Complain when we hit WSAENOBUFS on recv() or write() too.
23428 Perhaps this will help us hunt the bug.
23429 - If you're not a versioning dirserver, don't put the string
23430 "client-versions \nserver-versions \n" in your network-status.
23431 - Lower the minimum required number of file descriptors to 1000,
23432 so we can have some overhead for Valgrind on Linux, where the
23433 default ulimit -n is 1024.
23436 - Add tor.dizum.com as the fifth authoritative directory server.
23437 - Add a new config option FetchUselessDescriptors, off by default,
23438 for when you plan to run "exitlist" on your client and you want
23439 to know about even the non-running descriptors.
23442 Changes in version 0.1.1.17-rc - 2006-03-28
23444 - Clients and servers since 0.1.1.10-alpha have been expiring
23445 connections whenever they are idle for 5 minutes and they *do*
23446 have circuits on them. Oops. With this new version, clients will
23447 discard their previous entry guard choices and avoid choosing
23448 entry guards running these flawed versions.
23449 - Fix memory leak when uncompressing concatenated zlib streams. This
23450 was causing substantial leaks over time on Tor servers.
23451 - The v1 directory was including servers as much as 48 hours old,
23452 because that's how the new routerlist->routers works. Now only
23453 include them if they're 20 hours old or less.
23456 - Resume building on irix64, netbsd 2.0, etc.
23457 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
23459 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
23460 and it is confusing some users.
23461 - Mirrors stop caching the v1 directory so often.
23462 - Make the max number of old descriptors that a cache will hold
23463 rise with the number of directory authorities, so we can scale.
23464 - Change our win32 uname() hack to be more forgiving about what
23465 win32 versions it thinks it's found.
23468 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
23470 - When the controller's *setconf commands fail, collect an error
23471 message in a string and hand it back to the controller.
23472 - Make the v2 dir's "Fast" flag based on relative capacity, just
23473 like "Stable" is based on median uptime. Name everything in the
23474 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
23475 - Log server fingerprint on startup, so new server operators don't
23476 have to go hunting around their filesystem for it.
23477 - Return a robots.txt on our dirport to discourage google indexing.
23478 - Let the controller ask for GETINFO dir/status/foo so it can ask
23479 directly rather than connecting to the dir port. Only works when
23480 dirport is set for now.
23482 o New config options rather than constants in the code:
23483 - SocksTimeout: How long do we let a socks connection wait
23484 unattached before we fail it?
23485 - CircuitBuildTimeout: Cull non-open circuits that were born
23486 at least this many seconds ago.
23487 - CircuitIdleTimeout: Cull open clean circuits that were born
23488 at least this many seconds ago.
23491 Changes in version 0.1.1.16-rc - 2006-03-18
23492 o Bugfixes on 0.1.1.15-rc:
23493 - Fix assert when the controller asks to attachstream a connect-wait
23494 or resolve-wait stream.
23495 - Now do address rewriting when the controller asks us to attach
23496 to a particular circuit too. This will let Blossom specify
23497 "moria2.exit" without having to learn what moria2's IP address is.
23498 - Make the "tor --verify-config" command-line work again, so people
23499 can automatically check if their torrc will parse.
23500 - Authoritative dirservers no longer require an open connection from
23501 a server to consider him "reachable". We need this change because
23502 when we add new auth dirservers, old servers won't know not to
23504 - Let Tor build on Sun CC again.
23505 - Fix an off-by-one buffer size in dirserv.c that magically never
23506 hit our three authorities but broke sjmurdoch's own tor network.
23507 - If we as a directory mirror don't know of any v1 directory
23508 authorities, then don't try to cache any v1 directories.
23509 - Stop warning about unknown servers in our family when they are
23510 given as hex digests.
23511 - Stop complaining as quickly to the server operator that he
23512 hasn't registered his nickname/key binding.
23513 - Various cleanups so we can add new V2 Auth Dirservers.
23514 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
23515 reflect the updated flags in our v2 dir protocol.
23516 - Resume allowing non-printable characters for exit streams (both
23517 for connecting and for resolving). Now we tolerate applications
23518 that don't follow the RFCs. But continue to block malformed names
23521 o Bugfixes on 0.1.0.x:
23522 - Fix assert bug in close_logs(): when we close and delete logs,
23523 remove them all from the global "logfiles" list.
23524 - Fix minor integer overflow in calculating when we expect to use up
23525 our bandwidth allocation before hibernating.
23526 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
23527 there are multiple SSLs installed with different versions.
23528 - When we try to be a server and Address is not explicitly set and
23529 our hostname resolves to a private IP address, try to use an
23530 interface address if it has a public address. Now Windows machines
23531 that think of themselves as localhost can work by default.
23534 - Let the controller ask for GETINFO dir/server/foo so it can ask
23535 directly rather than connecting to the dir port.
23536 - Let the controller tell us about certain router descriptors
23537 that it doesn't want Tor to use in circuits. Implement
23538 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
23539 - New config option SafeSocks to reject all application connections
23540 using unsafe socks protocols. Defaults to off.
23543 Changes in version 0.1.1.15-rc - 2006-03-11
23544 o Bugfixes and cleanups:
23545 - When we're printing strings from the network, don't try to print
23546 non-printable characters. This protects us against shell escape
23547 sequence exploits, and also against attacks to fool humans into
23548 misreading their logs.
23549 - Fix a bug where Tor would fail to establish any connections if you
23550 left it off for 24 hours and then started it: we were happy with
23551 the obsolete network statuses, but they all referred to router
23552 descriptors that were too old to fetch, so we ended up with no
23553 valid router descriptors.
23554 - Fix a seg fault in the controller's "getinfo orconn-status"
23555 command while listing status on incoming handshaking connections.
23556 Introduce a status name "NEW" for these connections.
23557 - If we get a linelist or linelist_s config option from the torrc
23558 (e.g. ExitPolicy) and it has no value, warn and skip rather than
23559 silently resetting it to its default.
23560 - Don't abandon entry guards until they've been down or gone for
23562 - Cleaner and quieter log messages.
23565 - New controller signal NEWNYM that makes new application requests
23566 use clean circuits.
23567 - Add a new circuit purpose 'controller' to let the controller ask
23568 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
23569 controller command to let you specify the purpose if you're
23570 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
23571 command to let you change a circuit's purpose after it's been
23573 - Accept "private:*" in routerdesc exit policies; not generated yet
23574 because older Tors do not understand it.
23575 - Add BSD-style contributed startup script "rc.subr" from Peter
23579 Changes in version 0.1.1.14-alpha - 2006-02-20
23580 o Bugfixes on 0.1.1.x:
23581 - Don't die if we ask for a stdout or stderr log (even implicitly)
23582 and we're set to RunAsDaemon -- just warn.
23583 - We still had a few bugs in the OR connection rotation code that
23584 caused directory servers to slowly aggregate connections to other
23585 fast Tor servers. This time for sure!
23586 - Make log entries on Win32 include the name of the function again.
23587 - We were treating a pair of exit policies if they were equal even
23588 if one said accept and the other said reject -- causing us to
23589 not always publish a new descriptor since we thought nothing
23591 - Retry pending server downloads as well as pending networkstatus
23592 downloads when we unexpectedly get a socks request.
23593 - We were ignoring the IS_FAST flag in the directory status,
23594 meaning we were willing to pick trivial-bandwidth nodes for "fast"
23596 - If the controller's SAVECONF command fails (e.g. due to file
23597 permissions), let the controller know that it failed.
23600 - If we're trying to be a Tor server and running Windows 95/98/ME
23601 as a server, explain that we'll likely crash.
23602 - When we're a server, a client asks for an old-style directory,
23603 and our write bucket is empty, don't give it to him. This way
23604 small servers can continue to serve the directory *sometimes*,
23605 without getting overloaded.
23606 - Compress exit policies even more -- look for duplicate lines
23608 - Clients now honor the "guard" flag in the router status when
23609 picking entry guards, rather than looking at is_fast or is_stable.
23610 - Retain unrecognized lines in $DATADIR/state file, so that we can
23611 be forward-compatible.
23612 - Generate 18.0.0.0/8 address policy format in descs when we can;
23613 warn when the mask is not reducible to a bit-prefix.
23614 - Let the user set ControlListenAddress in the torrc. This can be
23615 dangerous, but there are some cases (like a secured LAN) where it
23617 - Split ReachableAddresses into ReachableDirAddresses and
23618 ReachableORAddresses, so we can restrict Dir conns to port 80
23619 and OR conns to port 443.
23620 - Now we can target arch and OS in rpm builds (contributed by
23621 Phobos). Also make the resulting dist-rpm filename match the
23623 - New config options to help controllers: FetchServerDescriptors
23624 and FetchHidServDescriptors for whether to fetch server
23625 info and hidserv info or let the controller do it, and
23626 PublishServerDescriptor and PublishHidServDescriptors.
23627 - Also let the controller set the __AllDirActionsPrivate config
23628 option if you want all directory fetches/publishes to happen via
23629 Tor (it assumes your controller bootstraps your circuits).
23632 Changes in version 0.1.0.17 - 2006-02-17
23633 o Crash bugfixes on 0.1.0.x:
23634 - When servers with a non-zero DirPort came out of hibernation,
23635 sometimes they would trigger an assert.
23637 o Other important bugfixes:
23638 - On platforms that don't have getrlimit (like Windows), we were
23639 artificially constraining ourselves to a max of 1024
23640 connections. Now just assume that we can handle as many as 15000
23641 connections. Hopefully this won't cause other problems.
23643 o Backported features:
23644 - When we're a server, a client asks for an old-style directory,
23645 and our write bucket is empty, don't give it to him. This way
23646 small servers can continue to serve the directory *sometimes*,
23647 without getting overloaded.
23648 - Whenever you get a 503 in response to a directory fetch, try
23649 once more. This will become important once servers start sending
23650 503's whenever they feel busy.
23651 - Fetch a new directory every 120 minutes, not every 40 minutes.
23652 Now that we have hundreds of thousands of users running the old
23653 directory algorithm, it's starting to hurt a lot.
23654 - Bump up the period for forcing a hidden service descriptor upload
23655 from 20 minutes to 1 hour.
23658 Changes in version 0.1.1.13-alpha - 2006-02-09
23659 o Crashes in 0.1.1.x:
23660 - When you tried to setconf ORPort via the controller, Tor would
23661 crash. So people using TorCP to become a server were sad.
23662 - Solve (I hope) the stack-smashing bug that we were seeing on fast
23663 servers. The problem appears to be something do with OpenSSL's
23664 random number generation, or how we call it, or something. Let me
23665 know if the crashes continue.
23666 - Turn crypto hardware acceleration off by default, until we find
23667 somebody smart who can test it for us. (It appears to produce
23668 seg faults in at least some cases.)
23669 - Fix a rare assert error when we've tried all intro points for
23670 a hidden service and we try fetching the service descriptor again:
23671 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
23674 - Fix a major load balance bug: we were round-robining in 16 KB
23675 chunks, and servers with bandwidthrate of 20 KB, while downloading
23676 a 600 KB directory, would starve their other connections. Now we
23677 try to be a bit more fair.
23678 - Dir authorities and mirrors were never expiring the newest
23679 descriptor for each server, causing memory and directory bloat.
23680 - Fix memory-bloating and connection-bloating bug on servers: We
23681 were never closing any connection that had ever had a circuit on
23682 it, because we were checking conn->n_circuits == 0, yet we had a
23683 bug that let it go negative.
23684 - Make Tor work using squid as your http proxy again -- squid
23685 returns an error if you ask for a URL that's too long, and it uses
23686 a really generic error message. Plus, many people are behind a
23687 transparent squid so they don't even realize it.
23688 - On platforms that don't have getrlimit (like Windows), we were
23689 artificially constraining ourselves to a max of 1024
23690 connections. Now just assume that we can handle as many as 15000
23691 connections. Hopefully this won't cause other problems.
23692 - Add a new config option ExitPolicyRejectPrivate which defaults to
23693 1. This means all exit policies will begin with rejecting private
23694 addresses, unless the server operator explicitly turns it off.
23697 - Clients no longer download descriptors for non-running
23699 - Before we add new directory authorities, we should make it
23700 clear that only v1 authorities should receive/publish hidden
23701 service descriptors.
23704 - As soon as we've fetched some more directory info, immediately
23705 try to download more server descriptors. This way we don't have
23706 a 10 second pause during initial bootstrapping.
23707 - Remove even more loud log messages that the server operator can't
23709 - When we're running an obsolete or un-recommended version, make
23710 the log message more clear about what the problem is and what
23711 versions *are* still recommended.
23712 - Provide a more useful warn message when our onion queue gets full:
23713 the CPU is too slow or the exit policy is too liberal.
23714 - Don't warn when we receive a 503 from a dirserver/cache -- this
23715 will pave the way for them being able to refuse if they're busy.
23716 - When we fail to bind a listener, try to provide a more useful
23717 log message: e.g., "Is Tor already running?"
23718 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
23719 Goldberg can prove things about our handshake protocol more
23721 - MaxConn has been obsolete for a while now. Document the ConnLimit
23722 config option, which is a *minimum* number of file descriptors
23723 that must be available else Tor refuses to start.
23724 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
23725 if you log to syslog and want something other than LOG_DAEMON.
23726 - Make dirservers generate a separate "guard" flag to mean,
23727 "would make a good entry guard". Make clients parse it and vote
23728 on it. Not used by clients yet.
23729 - Implement --with-libevent-dir option to ./configure. Also, improve
23730 search techniques to find libevent, and use those for openssl too.
23731 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
23732 - Only start testing reachability once we've established a
23733 circuit. This will make startup on dirservers less noisy.
23734 - Don't try to upload hidden service descriptors until we have
23735 established a circuit.
23736 - Fix the controller's "attachstream 0" command to treat conn like
23737 it just connected, doing address remapping, handling .exit and
23738 .onion idioms, and so on. Now we're more uniform in making sure
23739 that the controller hears about new and closing connections.
23742 Changes in version 0.1.1.12-alpha - 2006-01-11
23743 o Bugfixes on 0.1.1.x:
23744 - The fix to close duplicate server connections was closing all
23745 Tor client connections if they didn't establish a circuit
23746 quickly enough. Oops.
23747 - Fix minor memory issue (double-free) that happened on exit.
23749 o Bugfixes on 0.1.0.x:
23750 - Tor didn't warn when it failed to open a log file.
23753 Changes in version 0.1.1.11-alpha - 2006-01-10
23754 o Crashes in 0.1.1.x:
23755 - Include all the assert/crash fixes from 0.1.0.16.
23756 - If you start Tor and then quit very quickly, there were some
23757 races that tried to free things that weren't allocated yet.
23758 - Fix a rare memory stomp if you're running hidden services.
23759 - Fix segfault when specifying DirServer in config without nickname.
23760 - Fix a seg fault when you finish connecting to a server but at
23761 that moment you dump his server descriptor.
23762 - Extendcircuit and Attachstream controller commands would
23763 assert/crash if you don't give them enough arguments.
23764 - Fix an assert error when we're out of space in the connection_list
23765 and we try to post a hidden service descriptor (reported by weasel).
23766 - If you specify a relative torrc path and you set RunAsDaemon in
23767 your torrc, then it chdir()'s to the new directory. If you HUP,
23768 it tries to load the new torrc location, fails, and exits.
23769 The fix: no longer allow a relative path to torrc using -f.
23772 - Implement "entry guards": automatically choose a handful of entry
23773 nodes and stick with them for all circuits. Only pick new guards
23774 when the ones you have are unsuitable, and if the old guards
23775 become suitable again, switch back. This will increase security
23776 dramatically against certain end-point attacks. The EntryNodes
23777 config option now provides some hints about which entry guards you
23778 want to use most; and StrictEntryNodes means to only use those.
23779 - New directory logic: download by descriptor digest, not by
23780 fingerprint. Caches try to download all listed digests from
23781 authorities; clients try to download "best" digests from caches.
23782 This avoids partitioning and isolating attacks better.
23783 - Make the "stable" router flag in network-status be the median of
23784 the uptimes of running valid servers, and make clients pay
23785 attention to the network-status flags. Thus the cutoff adapts
23786 to the stability of the network as a whole, making IRC, IM, etc
23787 connections more reliable.
23790 - Tor servers with dynamic IP addresses were needing to wait 18
23791 hours before they could start doing reachability testing using
23792 the new IP address and ports. This is because they were using
23793 the internal descriptor to learn what to test, yet they were only
23794 rebuilding the descriptor once they decided they were reachable.
23795 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
23796 to download certain server descriptors, throw them away, and then
23797 fetch them again after 30 minutes. Now mirrors throw away these
23798 server descriptors so clients can't get them.
23799 - We were leaving duplicate connections to other ORs open for a week,
23800 rather than closing them once we detect a duplicate. This only
23801 really affected authdirservers, but it affected them a lot.
23802 - Spread the authdirservers' reachability testing over the entire
23803 testing interval, so we don't try to do 500 TLS's at once every
23807 - If the network is down, and we try to connect to a conn because
23808 we have a circuit in mind, and we timeout (30 seconds) because the
23809 network never answers, we were expiring the circuit, but we weren't
23810 obsoleting the connection or telling the entry_guards functions.
23811 - Some Tor servers process billions of cells per day. These statistics
23812 need to be uint64_t's.
23813 - Check for integer overflows in more places, when adding elements
23814 to smartlists. This could possibly prevent a buffer overflow
23815 on malicious huge inputs. I don't see any, but I haven't looked
23817 - ReachableAddresses kept growing new "reject *:*" lines on every
23819 - When you "setconf log" via the controller, it should remove all
23820 logs. We were automatically adding back in a "log notice stdout".
23821 - Newly bootstrapped Tor networks couldn't establish hidden service
23822 circuits until they had nodes with high uptime. Be more tolerant.
23823 - We were marking servers down when they could not answer every piece
23824 of the directory request we sent them. This was far too harsh.
23825 - Fix the torify (tsocks) config file to not use Tor for localhost
23827 - Directory authorities now go to the proper authority when asking for
23828 a networkstatus, even when they want a compressed one.
23829 - Fix a harmless bug that was causing Tor servers to log
23830 "Got an end because of misc error, but we're not an AP. Closing."
23831 - Authorities were treating their own descriptor changes as cosmetic,
23832 meaning the descriptor available in the network-status and the
23833 descriptor that clients downloaded were different.
23834 - The OS X installer was adding a symlink for tor_resolve but
23835 the binary was called tor-resolve (reported by Thomas Hardly).
23836 - Workaround a problem with some http proxies where they refuse GET
23837 requests that specify "Content-Length: 0" (reported by Adrian).
23838 - Fix wrong log message when you add a "HiddenServiceNodes" config
23839 line without any HiddenServiceDir line (reported by Chris Thomas).
23842 - Write the TorVersion into the state file so we have a prayer of
23843 keeping forward and backward compatibility.
23844 - Revive the FascistFirewall config option rather than eliminating it:
23845 now it's a synonym for ReachableAddresses *:80,*:443.
23846 - Clients choose directory servers from the network status lists,
23847 not from their internal list of router descriptors. Now they can
23848 go to caches directly rather than needing to go to authorities
23850 - Directory authorities ignore router descriptors that have only
23851 cosmetic differences: do this for 0.1.0.x servers now too.
23852 - Add a new flag to network-status indicating whether the server
23853 can answer v2 directory requests too.
23854 - Authdirs now stop whining so loudly about bad descriptors that
23855 they fetch from other dirservers. So when there's a log complaint,
23856 it's for sure from a freshly uploaded descriptor.
23857 - Reduce memory requirements in our structs by changing the order
23859 - There used to be two ways to specify your listening ports in a
23860 server descriptor: on the "router" line and with a separate "ports"
23861 line. Remove support for the "ports" line.
23862 - New config option "AuthDirRejectUnlisted" for auth dirservers as
23863 a panic button: if we get flooded with unusable servers we can
23864 revert to only listing servers in the approved-routers file.
23865 - Auth dir servers can now mark a fingerprint as "!reject" or
23866 "!invalid" in the approved-routers file (as its nickname), to
23867 refuse descriptors outright or include them but marked as invalid.
23868 - Servers store bandwidth history across restarts/crashes.
23869 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
23870 get a better idea of why their circuits failed. Not used yet.
23871 - Directory mirrors now cache up to 16 unrecognized network-status
23872 docs. Now we can add new authdirservers and they'll be cached too.
23873 - When picking a random directory, prefer non-authorities if any
23875 - New controller option "getinfo desc/all-recent" to fetch the
23876 latest server descriptor for every router that Tor knows about.
23879 Changes in version 0.1.0.16 - 2006-01-02
23880 o Crash bugfixes on 0.1.0.x:
23881 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
23882 corrupting the heap, losing FDs, or crashing when we need to resize
23883 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
23884 - It turns out sparc64 platforms crash on unaligned memory access
23885 too -- so detect and avoid this.
23886 - Handle truncated compressed data correctly (by detecting it and
23888 - Fix possible-but-unlikely free(NULL) in control.c.
23889 - When we were closing connections, there was a rare case that
23890 stomped on memory, triggering seg faults and asserts.
23891 - Avoid potential infinite recursion when building a descriptor. (We
23892 don't know that it ever happened, but better to fix it anyway.)
23893 - We were neglecting to unlink marked circuits from soon-to-close OR
23894 connections, which caused some rare scribbling on freed memory.
23895 - Fix a memory stomping race bug when closing the joining point of two
23896 rendezvous circuits.
23897 - Fix an assert in time parsing found by Steven Murdoch.
23899 o Other bugfixes on 0.1.0.x:
23900 - When we're doing reachability testing, provide more useful log
23901 messages so the operator knows what to expect.
23902 - Do not check whether DirPort is reachable when we are suppressing
23903 advertising it because of hibernation.
23904 - When building with -static or on Solaris, we sometimes needed -ldl.
23905 - When we're deciding whether a stream has enough circuits around
23906 that can handle it, count the freshly dirty ones and not the ones
23907 that are so dirty they won't be able to handle it.
23908 - When we're expiring old circuits, we had a logic error that caused
23909 us to close new rendezvous circuits rather than old ones.
23910 - Give a more helpful log message when you try to change ORPort via
23911 the controller: you should upgrade Tor if you want that to work.
23912 - We were failing to parse Tor versions that start with "Tor ".
23913 - Tolerate faulty streams better: when a stream fails for reason
23914 exitpolicy, stop assuming that the router is lying about his exit
23915 policy. When a stream fails for reason misc, allow it to retry just
23916 as if it was resolvefailed. When a stream has failed three times,
23917 reset its failure count so we can try again and get all three tries.
23920 Changes in version 0.1.1.10-alpha - 2005-12-11
23921 o Correctness bugfixes on 0.1.0.x:
23922 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
23923 corrupting the heap, losing FDs, or crashing when we need to resize
23924 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
23925 - Stop doing the complex voodoo overkill checking for insecure
23926 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
23927 - When we were closing connections, there was a rare case that
23928 stomped on memory, triggering seg faults and asserts.
23929 - We were neglecting to unlink marked circuits from soon-to-close OR
23930 connections, which caused some rare scribbling on freed memory.
23931 - When we're deciding whether a stream has enough circuits around
23932 that can handle it, count the freshly dirty ones and not the ones
23933 that are so dirty they won't be able to handle it.
23934 - Recover better from TCP connections to Tor servers that are
23935 broken but don't tell you (it happens!); and rotate TLS
23936 connections once a week.
23937 - When we're expiring old circuits, we had a logic error that caused
23938 us to close new rendezvous circuits rather than old ones.
23939 - Fix a scary-looking but apparently harmless bug where circuits
23940 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
23941 servers, and never switch to state CIRCUIT_STATE_OPEN.
23942 - When building with -static or on Solaris, we sometimes needed to
23944 - Give a useful message when people run Tor as the wrong user,
23945 rather than telling them to start chowning random directories.
23946 - We were failing to inform the controller about new .onion streams.
23948 o Security bugfixes on 0.1.0.x:
23949 - Refuse server descriptors if the fingerprint line doesn't match
23950 the included identity key. Tor doesn't care, but other apps (and
23951 humans) might actually be trusting the fingerprint line.
23952 - We used to kill the circuit when we receive a relay command we
23953 don't recognize. Now we just drop it.
23954 - Start obeying our firewall options more rigorously:
23955 . If we can't get to a dirserver directly, try going via Tor.
23956 . Don't ever try to connect (as a client) to a place our
23957 firewall options forbid.
23958 . If we specify a proxy and also firewall options, obey the
23959 firewall options even when we're using the proxy: some proxies
23960 can only proxy to certain destinations.
23961 - Fix a bug found by Lasse Overlier: when we were making internal
23962 circuits (intended to be cannibalized later for rendezvous and
23963 introduction circuits), we were picking them so that they had
23964 useful exit nodes. There was no need for this, and it actually
23965 aids some statistical attacks.
23966 - Start treating internal circuits and exit circuits separately.
23967 It's important to keep them separate because internal circuits
23968 have their last hops picked like middle hops, rather than like
23969 exit hops. So exiting on them will break the user's expectations.
23971 o Bugfixes on 0.1.1.x:
23972 - Take out the mis-feature where we tried to detect IP address
23973 flapping for people with DynDNS, and chose not to upload a new
23974 server descriptor sometimes.
23975 - Try to be compatible with OpenSSL 0.9.6 again.
23976 - Log fix: when the controller is logging about .onion addresses,
23977 sometimes it didn't include the ".onion" part of the address.
23978 - Don't try to modify options->DirServers internally -- if the
23979 user didn't specify any, just add the default ones directly to
23980 the trusted dirserver list. This fixes a bug where people running
23981 controllers would use SETCONF on some totally unrelated config
23982 option, and Tor would start yelling at them about changing their
23984 - Let the controller's redirectstream command specify a port, in
23985 case the controller wants to change that too.
23986 - When we requested a pile of server descriptors, we sometimes
23987 accidentally launched a duplicate request for the first one.
23988 - Bugfix for trackhostexits: write down the fingerprint of the
23989 chosen exit, not its nickname, because the chosen exit might not
23991 - When parsing foo.exit, if foo is unknown, and we are leaving
23992 circuits unattached, set the chosen_exit field and leave the
23993 address empty. This matters because controllers got confused
23995 - Directory authorities no longer try to download server
23996 descriptors that they know they will reject.
23998 o Features and updates:
23999 - Replace balanced trees with hash tables: this should make stuff
24000 significantly faster.
24001 - Resume using the AES counter-mode implementation that we ship,
24002 rather than OpenSSL's. Ours is significantly faster.
24003 - Many other CPU and memory improvements.
24004 - Add a new config option FastFirstHopPK (on by default) so clients
24005 do a trivial crypto handshake for their first hop, since TLS has
24006 already taken care of confidentiality and authentication.
24007 - Add a new config option TestSocks so people can see if their
24008 applications are using socks4, socks4a, socks5-with-ip, or
24009 socks5-with-hostname. This way they don't have to keep mucking
24010 with tcpdump and wondering if something got cached somewhere.
24011 - Warn when listening on a public address for socks. I suspect a
24012 lot of people are setting themselves up as open socks proxies,
24013 and they have no idea that jerks on the Internet are using them,
24014 since they simply proxy the traffic into the Tor network.
24015 - Add "private:*" as an alias in configuration for policies. Now
24016 you can simplify your exit policy rather than needing to list
24017 every single internal or nonroutable network space.
24018 - Add a new controller event type that allows controllers to get
24019 all server descriptors that were uploaded to a router in its role
24020 as authoritative dirserver.
24021 - Start shipping socks-extensions.txt, tor-doc-unix.html,
24022 tor-doc-server.html, and stylesheet.css in the tarball.
24023 - Stop shipping tor-doc.html in the tarball.
24026 Changes in version 0.1.1.9-alpha - 2005-11-15
24027 o Usability improvements:
24028 - Start calling it FooListenAddress rather than FooBindAddress,
24029 since few of our users know what it means to bind an address
24031 - Reduce clutter in server logs. We're going to try to make
24032 them actually usable now. New config option ProtocolWarnings that
24033 lets you hear about how _other Tors_ are breaking the protocol. Off
24035 - Divide log messages into logging domains. Once we put some sort
24036 of interface on this, it will let people looking at more verbose
24037 log levels specify the topics they want to hear more about.
24038 - Make directory servers return better http 404 error messages
24039 instead of a generic "Servers unavailable".
24040 - Check for even more Windows version flags when writing the platform
24041 string in server descriptors, and note any we don't recognize.
24042 - Clean up more of the OpenSSL memory when exiting, so we can detect
24043 memory leaks better.
24044 - Make directory authorities be non-versioning, non-naming by
24045 default. Now we can add new directory servers without requiring
24046 their operators to pay close attention.
24047 - When logging via syslog, include the pid whenever we provide
24048 a log entry. Suggested by Todd Fries.
24050 o Performance improvements:
24051 - Directory servers now silently throw away new descriptors that
24052 haven't changed much if the timestamps are similar. We do this to
24053 tolerate older Tor servers that upload a new descriptor every 15
24054 minutes. (It seemed like a good idea at the time.)
24055 - Inline bottleneck smartlist functions; use fast versions by default.
24056 - Add a "Map from digest to void*" abstraction digestmap_t so we
24057 can do less hex encoding/decoding. Use it in router_get_by_digest()
24058 to resolve a performance bottleneck.
24059 - Allow tor_gzip_uncompress to extract as much as possible from
24060 truncated compressed data. Try to extract as many
24061 descriptors as possible from truncated http responses (when
24062 DIR_PURPOSE_FETCH_ROUTERDESC).
24063 - Make circ->onionskin a pointer, not a static array. moria2 was using
24064 125000 circuit_t's after it had been up for a few weeks, which
24065 translates to 20+ megs of wasted space.
24066 - The private half of our EDH handshake keys are now chosen out
24067 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
24069 o Security improvements:
24070 - Start making directory caches retain old routerinfos, so soon
24071 clients can start asking by digest of descriptor rather than by
24072 fingerprint of server.
24073 - Add half our entropy from RAND_poll in OpenSSL. This knows how
24074 to use egd (if present), openbsd weirdness (if present), vms/os2
24075 weirdness (if we ever port there), and more in the future.
24077 o Bugfixes on 0.1.0.x:
24078 - Do round-robin writes of at most 16 kB per write. This might be
24079 more fair on loaded Tor servers, and it might resolve our Windows
24080 crash bug. It might also slow things down.
24081 - Our TLS handshakes were generating a single public/private
24082 keypair for the TLS context, rather than making a new one for
24083 each new connections. Oops. (But we were still rotating them
24084 periodically, so it's not so bad.)
24085 - When we were cannibalizing a circuit with a particular exit
24086 node in mind, we weren't checking to see if that exit node was
24087 already present earlier in the circuit. Oops.
24088 - When a Tor server's IP changes (e.g. from a dyndns address),
24089 upload a new descriptor so clients will learn too.
24090 - Really busy servers were keeping enough circuits open on stable
24091 connections that they were wrapping around the circuit_id
24092 space. (It's only two bytes.) This exposed a bug where we would
24093 feel free to reuse a circuit_id even if it still exists but has
24094 been marked for close. Try to fix this bug. Some bug remains.
24095 - If we would close a stream early (e.g. it asks for a .exit that
24096 we know would refuse it) but the LeaveStreamsUnattached config
24097 option is set by the controller, then don't close it.
24099 o Bugfixes on 0.1.1.8-alpha:
24100 - Fix a big pile of memory leaks, some of them serious.
24101 - Do not try to download a routerdesc if we would immediately reject
24103 - Resume inserting a newline between all router descriptors when
24104 generating (old style) signed directories, since our spec says
24106 - When providing content-type application/octet-stream for
24107 server descriptors using .z, we were leaving out the
24108 content-encoding header. Oops. (Everything tolerated this just
24109 fine, but that doesn't mean we need to be part of the problem.)
24110 - Fix a potential seg fault in getconf and getinfo using version 1
24111 of the controller protocol.
24112 - Avoid crash: do not check whether DirPort is reachable when we
24113 are suppressing it because of hibernation.
24114 - Make --hash-password not crash on exit.
24117 Changes in version 0.1.1.8-alpha - 2005-10-07
24118 o New features (major):
24119 - Clients don't download or use the directory anymore. Now they
24120 download and use network-statuses from the trusted dirservers,
24121 and fetch individual server descriptors as needed from mirrors.
24122 See dir-spec.txt for all the gory details.
24123 - Be more conservative about whether to advertise our DirPort.
24124 The main change is to not advertise if we're running at capacity
24125 and either a) we could hibernate or b) our capacity is low and
24126 we're using a default DirPort.
24127 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
24129 o New features (minor):
24130 - Try to be smart about when to retry network-status and
24131 server-descriptor fetches. Still needs some tuning.
24132 - Stop parsing, storing, or using running-routers output (but
24133 mirrors still cache and serve it).
24134 - Consider a threshold of versioning dirservers (dirservers who have
24135 an opinion about which Tor versions are still recommended) before
24136 deciding whether to warn the user that he's obsolete.
24137 - Dirservers can now reject/invalidate by key and IP, with the
24138 config options "AuthDirInvalid" and "AuthDirReject". This is
24139 useful since currently we automatically list servers as running
24140 and usable even if we know they're jerks.
24141 - Provide dire warnings to any users who set DirServer; move it out
24142 of torrc.sample and into torrc.complete.
24143 - Add MyFamily to torrc.sample in the server section.
24144 - Add nicknames to the DirServer line, so we can refer to them
24145 without requiring all our users to memorize their IP addresses.
24146 - When we get an EOF or a timeout on a directory connection, note
24147 how many bytes of serverdesc we are dropping. This will help
24148 us determine whether it is smart to parse incomplete serverdesc
24150 - Add a new function to "change pseudonyms" -- that is, to stop
24151 using any currently-dirty circuits for new streams, so we don't
24152 link new actions to old actions. Currently it's only called on
24153 HUP (or SIGNAL RELOAD).
24154 - On sighup, if UseHelperNodes changed to 1, use new circuits.
24155 - Start using RAND_bytes rather than RAND_pseudo_bytes from
24156 OpenSSL. Also, reseed our entropy every hour, not just at
24157 startup. And entropy in 512-bit chunks, not 160-bit chunks.
24159 o Fixes on 0.1.1.7-alpha:
24160 - Nobody ever implemented EVENT_ADDRMAP for control protocol
24161 version 0, so don't let version 0 controllers ask for it.
24162 - If you requested something with too many newlines via the
24163 v1 controller protocol, you could crash tor.
24164 - Fix a number of memory leaks, including some pretty serious ones.
24165 - Re-enable DirPort testing again, so Tor servers will be willing
24166 to advertise their DirPort if it's reachable.
24167 - On TLS handshake, only check the other router's nickname against
24168 its expected nickname if is_named is set.
24170 o Fixes forward-ported from 0.1.0.15:
24171 - Don't crash when we don't have any spare file descriptors and we
24172 try to spawn a dns or cpu worker.
24173 - Make the numbers in read-history and write-history into uint64s,
24174 so they don't overflow and publish negatives in the descriptor.
24176 o Fixes on 0.1.0.x:
24177 - For the OS X package's modified privoxy config file, comment
24178 out the "logfile" line so we don't log everything passed
24180 - We were whining about using socks4 or socks5-with-local-lookup
24181 even when it's an IP in the "virtual" range we designed exactly
24183 - We were leaking some memory every time the client changes IPs.
24184 - Never call free() on tor_malloc()d memory. This will help us
24185 use dmalloc to detect memory leaks.
24186 - Check for named servers when looking them up by nickname;
24187 warn when we'recalling a non-named server by its nickname;
24188 don't warn twice about the same name.
24189 - Try to list MyFamily elements by key, not by nickname, and warn
24190 if we've not heard of the server.
24191 - Make windows platform detection (uname equivalent) smarter.
24192 - It turns out sparc64 doesn't like unaligned access either.
24195 Changes in version 0.1.0.15 - 2005-09-23
24196 o Bugfixes on 0.1.0.x:
24197 - Reject ports 465 and 587 (spam targets) in default exit policy.
24198 - Don't crash when we don't have any spare file descriptors and we
24199 try to spawn a dns or cpu worker.
24200 - Get rid of IgnoreVersion undocumented config option, and make us
24201 only warn, never exit, when we're running an obsolete version.
24202 - Don't try to print a null string when your server finds itself to
24203 be unreachable and the Address config option is empty.
24204 - Make the numbers in read-history and write-history into uint64s,
24205 so they don't overflow and publish negatives in the descriptor.
24206 - Fix a minor memory leak in smartlist_string_remove().
24207 - We were only allowing ourselves to upload a server descriptor at
24208 most every 20 minutes, even if it changed earlier than that.
24209 - Clean up log entries that pointed to old URLs.
24212 Changes in version 0.1.1.7-alpha - 2005-09-14
24213 o Fixes on 0.1.1.6-alpha:
24214 - Exit servers were crashing when people asked them to make a
24215 connection to an address not in their exit policy.
24216 - Looking up a non-existent stream for a v1 control connection would
24218 - Fix a seg fault if we ask a dirserver for a descriptor by
24219 fingerprint but he doesn't know about him.
24220 - SETCONF was appending items to linelists, not clearing them.
24221 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
24222 out and refuse the setconf if it would fail.
24223 - Downgrade the dirserver log messages when whining about
24227 - Add Peter Palfrader's check-tor script to tor/contrib/
24228 It lets you easily check whether a given server (referenced by
24229 nickname) is reachable by you.
24230 - Numerous changes to move towards client-side v2 directories. Not
24233 o Fixes on 0.1.0.x:
24234 - If the user gave tor an odd number of command-line arguments,
24235 we were silently ignoring the last one. Now we complain and fail.
24236 [This wins the oldest-bug prize -- this bug has been present since
24237 November 2002, as released in Tor 0.0.0.]
24238 - Do not use unaligned memory access on alpha, mips, or mipsel.
24239 It *works*, but is very slow, so we treat them as if it doesn't.
24240 - Retry directory requests if we fail to get an answer we like
24241 from a given dirserver (we were retrying before, but only if
24242 we fail to connect).
24243 - When writing the RecommendedVersions line, sort them first.
24244 - When the client asked for a rendezvous port that the hidden
24245 service didn't want to provide, we were sending an IP address
24246 back along with the end cell. Fortunately, it was zero. But stop
24248 - Correct "your server is reachable" log entries to indicate that
24249 it was self-testing that told us so.
24252 Changes in version 0.1.1.6-alpha - 2005-09-09
24253 o Fixes on 0.1.1.5-alpha:
24254 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
24255 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
24256 - Fix bug with tor_memmem finding a match at the end of the string.
24257 - Make unit tests run without segfaulting.
24258 - Resolve some solaris x86 compile warnings.
24259 - Handle duplicate lines in approved-routers files without warning.
24260 - Fix bug where as soon as a server refused any requests due to his
24261 exit policy (e.g. when we ask for localhost and he tells us that's
24262 127.0.0.1 and he won't do it), we decided he wasn't obeying his
24263 exit policy using him for any exits.
24264 - Only do openssl hardware accelerator stuff if openssl version is
24267 o New controller features/fixes:
24268 - Add a "RESETCONF" command so you can set config options like
24269 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
24270 a config option in the torrc with no value, then it clears it
24271 entirely (rather than setting it to its default).
24272 - Add a "GETINFO config-file" to tell us where torrc is.
24273 - Avoid sending blank lines when GETINFO replies should be empty.
24274 - Add a QUIT command for the controller (for using it manually).
24275 - Fix a bug in SAVECONF that was adding default dirservers and
24276 other redundant entries to the torrc file.
24278 o Start on the new directory design:
24279 - Generate, publish, cache, serve new network-status format.
24280 - Publish individual descriptors (by fingerprint, by "all", and by
24282 - Publish client and server recommended versions separately.
24283 - Allow tor_gzip_uncompress() to handle multiple concatenated
24284 compressed strings. Serve compressed groups of router
24285 descriptors. The compression logic here could be more
24287 - Distinguish v1 authorities (all currently trusted directories)
24288 from v2 authorities (all trusted directories).
24289 - Change DirServers config line to note which dirs are v1 authorities.
24290 - Add configuration option "V1AuthoritativeDirectory 1" which
24291 moria1, moria2, and tor26 should set.
24292 - Remove option when getting directory cache to see whether they
24293 support running-routers; they all do now. Replace it with one
24294 to see whether caches support v2 stuff.
24297 - Dirservers now do their own external reachability testing of each
24298 Tor server, and only list them as running if they've been found to
24299 be reachable. We also send back warnings to the server's logs if
24300 it uploads a descriptor that we already believe is unreachable.
24301 - Implement exit enclaves: if we know an IP address for the
24302 destination, and there's a running Tor server at that address
24303 which allows exit to the destination, then extend the circuit to
24304 that exit first. This provides end-to-end encryption and end-to-end
24305 authentication. Also, if the user wants a .exit address or enclave,
24306 use 4 hops rather than 3, and cannibalize a general circ for it
24308 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
24309 controller. Also, rotate dns and cpu workers if the controller
24310 changes options that will affect them; and initialize the dns
24311 worker cache tree whether or not we start out as a server.
24312 - Only upload a new server descriptor when options change, 18
24313 hours have passed, uptime is reset, or bandwidth changes a lot.
24314 - Check [X-]Forwarded-For headers in HTTP requests when generating
24315 log messages. This lets people run dirservers (and caches) behind
24316 Apache but still know which IP addresses are causing warnings.
24318 o Config option changes:
24319 - Replace (Fascist)Firewall* config options with a new
24320 ReachableAddresses option that understands address policies.
24321 For example, "ReachableAddresses *:80,*:443"
24322 - Get rid of IgnoreVersion undocumented config option, and make us
24323 only warn, never exit, when we're running an obsolete version.
24324 - Make MonthlyAccountingStart config option truly obsolete now.
24326 o Fixes on 0.1.0.x:
24327 - Reject ports 465 and 587 in the default exit policy, since
24328 people have started using them for spam too.
24329 - It turns out we couldn't bootstrap a network since we added
24330 reachability detection in 0.1.0.1-rc. Good thing the Tor network
24331 has never gone down. Add an AssumeReachable config option to let
24332 servers and dirservers bootstrap. When we're trying to build a
24333 high-uptime or high-bandwidth circuit but there aren't enough
24334 suitable servers, try being less picky rather than simply failing.
24335 - Our logic to decide if the OR we connected to was the right guy
24336 was brittle and maybe open to a mitm for unverified routers.
24337 - We weren't cannibalizing circuits correctly for
24338 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
24339 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
24340 build those from scratch. This should make hidden services faster.
24341 - Predict required circuits better, with an eye toward making hidden
24342 services faster on the service end.
24343 - Retry streams if the exit node sends back a 'misc' failure. This
24344 should result in fewer random failures. Also, after failing
24345 from resolve failed or misc, reset the num failures, so we give
24346 it a fair shake next time we try.
24347 - Clean up the rendezvous warn log msgs, and downgrade some to info.
24348 - Reduce severity on logs about dns worker spawning and culling.
24349 - When we're shutting down and we do something like try to post a
24350 server descriptor or rendezvous descriptor, don't complain that
24351 we seem to be unreachable. Of course we are, we're shutting down.
24352 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
24353 We don't use them yet, but maybe one day our DNS resolver will be
24354 able to discover them.
24355 - Make ContactInfo mandatory for authoritative directory servers.
24356 - Require server descriptors to list IPv4 addresses -- hostnames
24357 are no longer allowed. This also fixes some potential security
24358 problems with people providing hostnames as their address and then
24359 preferentially resolving them to partition users.
24360 - Change log line for unreachability to explicitly suggest /etc/hosts
24361 as the culprit. Also make it clearer what IP address and ports we're
24362 testing for reachability.
24363 - Put quotes around user-supplied strings when logging so users are
24364 more likely to realize if they add bad characters (like quotes)
24366 - Let auth dir servers start without specifying an Address config
24368 - Make unit tests (and other invocations that aren't the real Tor)
24369 run without launching listeners, creating subdirectories, and so on.
24372 Changes in version 0.1.1.5-alpha - 2005-08-08
24373 o Bugfixes included in 0.1.0.14.
24375 o Bugfixes on 0.1.0.x:
24376 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
24377 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
24378 it would silently using ignore the 6668.
24381 Changes in version 0.1.0.14 - 2005-08-08
24382 o Bugfixes on 0.1.0.x:
24383 - Fix the other half of the bug with crypto handshakes
24385 - Fix an assert trigger if you send a 'signal term' via the
24386 controller when it's listening for 'event info' messages.
24389 Changes in version 0.1.1.4-alpha - 2005-08-04
24390 o Bugfixes included in 0.1.0.13.
24393 - Improve tor_gettimeofday() granularity on windows.
24394 - Make clients regenerate their keys when their IP address changes.
24395 - Implement some more GETINFO goodness: expose helper nodes, config
24396 options, getinfo keys.
24399 Changes in version 0.1.0.13 - 2005-08-04
24400 o Bugfixes on 0.1.0.x:
24401 - Fix a critical bug in the security of our crypto handshakes.
24402 - Fix a size_t underflow in smartlist_join_strings2() that made
24403 it do bad things when you hand it an empty smartlist.
24404 - Fix Windows installer to ship Tor license (thanks to Aphex for
24405 pointing out this oversight) and put a link to the doc directory
24407 - Explicitly set no-unaligned-access for sparc: it turns out the
24408 new gcc's let you compile broken code, but that doesn't make it
24412 Changes in version 0.1.1.3-alpha - 2005-07-23
24413 o Bugfixes on 0.1.1.2-alpha:
24414 - Fix a bug in handling the controller's "post descriptor"
24416 - Fix several bugs in handling the controller's "extend circuit"
24418 - Fix a bug in handling the controller's "stream status" event.
24419 - Fix an assert failure if we have a controller listening for
24420 circuit events and we go offline.
24421 - Re-allow hidden service descriptors to publish 0 intro points.
24422 - Fix a crash when generating your hidden service descriptor if
24423 you don't have enough intro points already.
24425 o New features on 0.1.1.2-alpha:
24426 - New controller function "getinfo accounting", to ask how
24427 many bytes we've used in this time period.
24428 - Experimental support for helper nodes: a lot of the risk from
24429 a small static adversary comes because users pick new random
24430 nodes every time they rebuild a circuit. Now users will try to
24431 stick to the same small set of entry nodes if they can. Not
24432 enabled by default yet.
24434 o Bugfixes on 0.1.0.12:
24435 - If you're an auth dir server, always publish your dirport,
24436 even if you haven't yet found yourself to be reachable.
24437 - Fix a size_t underflow in smartlist_join_strings2() that made
24438 it do bad things when you hand it an empty smartlist.
24441 Changes in version 0.1.0.12 - 2005-07-18
24442 o New directory servers:
24443 - tor26 has changed IP address.
24445 o Bugfixes on 0.1.0.x:
24446 - Fix a possible double-free in tor_gzip_uncompress().
24447 - When --disable-threads is set, do not search for or link against
24448 pthreads libraries.
24449 - Don't trigger an assert if an authoritative directory server
24450 claims its dirport is 0.
24451 - Fix bug with removing Tor as an NT service: some people were
24452 getting "The service did not return an error." Thanks to Matt
24456 Changes in version 0.1.1.2-alpha - 2005-07-15
24457 o New directory servers:
24458 - tor26 has changed IP address.
24460 o Bugfixes on 0.1.0.x, crashes/leaks:
24461 - Port the servers-not-obeying-their-exit-policies fix from
24463 - Fix an fd leak in start_daemon().
24464 - On Windows, you can't always reopen a port right after you've
24465 closed it. So change retry_listeners() to only close and re-open
24466 ports that have changed.
24467 - Fix a possible double-free in tor_gzip_uncompress().
24469 o Bugfixes on 0.1.0.x, usability:
24470 - When tor_socketpair() fails in Windows, give a reasonable
24471 Windows-style errno back.
24472 - Let people type "tor --install" as well as "tor -install" when
24474 want to make it an NT service.
24475 - NT service patch from Matt Edman to improve error messages.
24476 - When the controller asks for a config option with an abbreviated
24477 name, give the full name in our response.
24478 - Correct the man page entry on TrackHostExitsExpire.
24479 - Looks like we were never delivering deflated (i.e. compressed)
24480 running-routers lists, even when asked. Oops.
24481 - When --disable-threads is set, do not search for or link against
24482 pthreads libraries.
24484 o Bugfixes on 0.1.1.x:
24485 - Fix a seg fault with autodetecting which controller version is
24489 - New hidden service descriptor format: put a version in it, and
24490 let people specify introduction/rendezvous points that aren't
24491 in "the directory" (which is subjective anyway).
24492 - Allow the DEBUG controller event to work again. Mark certain log
24493 entries as "don't tell this to controllers", so we avoid cycles.
24496 Changes in version 0.1.0.11 - 2005-06-30
24497 o Bugfixes on 0.1.0.x:
24498 - Fix major security bug: servers were disregarding their
24499 exit policies if clients behaved unexpectedly.
24500 - Make OS X init script check for missing argument, so we don't
24501 confuse users who invoke it incorrectly.
24502 - Fix a seg fault in "tor --hash-password foo".
24503 - The MAPADDRESS control command was broken.
24506 Changes in version 0.1.1.1-alpha - 2005-06-29
24508 - Make OS X init script check for missing argument, so we don't
24509 confuse users who invoke it incorrectly.
24510 - Fix a seg fault in "tor --hash-password foo".
24511 - Fix a possible way to DoS dirservers.
24512 - When we complain that your exit policy implicitly allows local or
24513 private address spaces, name them explicitly so operators can
24515 - Make the log message less scary when all the dirservers are
24516 temporarily unreachable.
24517 - We were printing the number of idle dns workers incorrectly when
24521 - Revised controller protocol (version 1) that uses ascii rather
24522 than binary. Add supporting libraries in python and java so you
24523 can use the controller from your applications without caring how
24524 our protocol works.
24525 - Spiffy new support for crypto hardware accelerators. Can somebody
24529 Changes in version 0.0.9.10 - 2005-06-16
24530 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
24531 - Refuse relay cells that claim to have a length larger than the
24532 maximum allowed. This prevents a potential attack that could read
24533 arbitrary memory (e.g. keys) from an exit server's process
24537 Changes in version 0.1.0.10 - 2005-06-14
24538 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
24539 libevent before 1.1a.
24542 Changes in version 0.1.0.9-rc - 2005-06-09
24544 - Reset buf->highwater every time buf_shrink() is called, not just on
24545 a successful shrink. This was causing significant memory bloat.
24546 - Fix buffer overflow when checking hashed passwords.
24547 - Security fix: if seeding the RNG on Win32 fails, quit.
24548 - Allow seeding the RNG on Win32 even when you're not running as
24550 - Disable threading on Solaris too. Something is wonky with it,
24551 cpuworkers, and reentrant libs.
24552 - Reenable the part of the code that tries to flush as soon as an
24553 OR outbuf has a full TLS record available. Perhaps this will make
24554 OR outbufs not grow as huge except in rare cases, thus saving lots
24555 of CPU time plus memory.
24556 - Reject malformed .onion addresses rather then passing them on as
24557 normal web requests.
24558 - Adapt patch from Adam Langley: fix possible memory leak in
24559 tor_lookup_hostname().
24560 - Initialize libevent later in the startup process, so the logs are
24561 already established by the time we start logging libevent warns.
24562 - Use correct errno on win32 if libevent fails.
24563 - Check and warn about known-bad/slow libevent versions.
24564 - Pay more attention to the ClientOnly config option.
24565 - Have torctl.in/tor.sh.in check for location of su binary (needed
24567 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
24568 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
24569 HttpProxyAuthenticator
24570 - Stop warning about sigpipes in the logs. We're going to
24571 pretend that getting these occassionally is normal and fine.
24572 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
24574 installer screens; and don't put stuff into StartupItems unless
24575 the user asks you to.
24576 - Require servers that use the default dirservers to have public IP
24577 addresses. We have too many servers that are configured with private
24578 IPs and their admins never notice the log entries complaining that
24579 their descriptors are being rejected.
24580 - Add OSX uninstall instructions. An actual uninstall script will
24584 Changes in version 0.1.0.8-rc - 2005-05-23
24586 - It turns out that kqueue on OS X 10.3.9 was causing kernel
24587 panics. Disable kqueue on all OS X Tors.
24588 - Fix RPM: remove duplicate line accidentally added to the rpm
24590 - Disable threads on openbsd too, since its gethostaddr is not
24592 - Tolerate libevent 0.8 since it still works, even though it's
24594 - Enable building on Red Hat 9.0 again.
24595 - Allow the middle hop of the testing circuit to be running any
24596 version, now that most of them have the bugfix to let them connect
24597 to unknown servers. This will allow reachability testing to work
24598 even when 0.0.9.7-0.0.9.9 become obsolete.
24599 - Handle relay cells with rh.length too large. This prevents
24600 a potential attack that could read arbitrary memory (maybe even
24601 keys) from the exit server's process.
24602 - We screwed up the dirport reachability testing when we don't yet
24603 have a cached version of the directory. Hopefully now fixed.
24604 - Clean up router_load_single_router() (used by the controller),
24605 so it doesn't seg fault on error.
24606 - Fix a minor memory leak when somebody establishes an introduction
24607 point at your Tor server.
24608 - If a socks connection ends because read fails, don't warn that
24609 you're not sending a socks reply back.
24612 - Add HttpProxyAuthenticator config option too, that works like
24613 the HttpsProxyAuthenticator config option.
24614 - Encode hashed controller passwords in hex instead of base64,
24615 to make it easier to write controllers.
24618 Changes in version 0.1.0.7-rc - 2005-05-17
24620 - Fix a bug in the OS X package installer that prevented it from
24621 installing on Tiger.
24622 - Fix a script bug in the OS X package installer that made it
24623 complain during installation.
24624 - Find libevent even if it's hiding in /usr/local/ and your
24625 CFLAGS and LDFLAGS don't tell you to look there.
24626 - Be able to link with libevent as a shared library (the default
24627 after 1.0d), even if it's hiding in /usr/local/lib and even
24628 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
24629 assuming you're running gcc. Otherwise fail and give a useful
24631 - Fix a bug in the RPM packager: set home directory for _tor to
24632 something more reasonable when first installing.
24633 - Free a minor amount of memory that is still reachable on exit.
24636 Changes in version 0.1.0.6-rc - 2005-05-14
24638 - Implement --disable-threads configure option. Disable threads on
24639 netbsd by default, because it appears to have no reentrant resolver
24641 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
24642 release (1.1) detects and disables kqueue if it's broken.
24643 - Append default exit policy before checking for implicit internal
24644 addresses. Now we don't log a bunch of complaints on startup
24645 when using the default exit policy.
24646 - Some people were putting "Address " in their torrc, and they had
24647 a buggy resolver that resolved " " to 0.0.0.0. Oops.
24648 - If DataDir is ~/.tor, and that expands to /.tor, then default to
24649 LOCALSTATEDIR/tor instead.
24650 - Fix fragmented-message bug in TorControl.py.
24651 - Resolve a minor bug which would prevent unreachable dirports
24652 from getting suppressed in the published descriptor.
24653 - When the controller gave us a new descriptor, we weren't resolving
24654 it immediately, so Tor would think its address was 0.0.0.0 until
24655 we fetched a new directory.
24656 - Fix an uppercase/lowercase case error in suppressing a bogus
24657 libevent warning on some Linuxes.
24660 - Begin scrubbing sensitive strings from logs by default. Turn off
24661 the config option SafeLogging if you need to do debugging.
24662 - Switch to a new buffer management algorithm, which tries to avoid
24663 reallocing and copying quite as much. In first tests it looks like
24664 it uses *more* memory on average, but less cpu.
24665 - First cut at support for "create-fast" cells. Clients can use
24666 these when extending to their first hop, since the TLS already
24667 provides forward secrecy and authentication. Not enabled on
24669 - When dirservers refuse a router descriptor, we now log its
24670 contactinfo, platform, and the poster's IP address.
24671 - Call tor_free_all instead of connections_free_all after forking, to
24672 save memory on systems that need to fork.
24673 - Whine at you if you're a server and you don't set your contactinfo.
24674 - Implement --verify-config command-line option to check if your torrc
24675 is valid without actually launching Tor.
24676 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
24677 rather than just rejecting it.
24680 Changes in version 0.1.0.5-rc - 2005-04-27
24682 - Stop trying to print a null pointer if an OR conn fails because
24683 we didn't like its cert.
24685 - Switch our internal buffers implementation to use a ring buffer,
24686 to hopefully improve performance for fast servers a lot.
24687 - Add HttpsProxyAuthenticator support (basic auth only), based
24688 on patch from Adam Langley.
24689 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
24690 the fast servers that have been joining lately.
24691 - Give hidden service accesses extra time on the first attempt,
24692 since 60 seconds is often only barely enough. This might improve
24694 - Improve performance for dirservers: stop re-parsing the whole
24695 directory every time you regenerate it.
24696 - Add more debugging info to help us find the weird dns freebsd
24697 pthreads bug; cleaner debug messages to help track future issues.
24700 Changes in version 0.0.9.9 - 2005-04-23
24701 o Bugfixes on 0.0.9.x:
24702 - If unofficial Tor clients connect and send weird TLS certs, our
24703 Tor server triggers an assert. This release contains a minimal
24704 backport from the broader fix that we put into 0.1.0.4-rc.
24707 Changes in version 0.1.0.4-rc - 2005-04-23
24709 - If unofficial Tor clients connect and send weird TLS certs, our
24710 Tor server triggers an assert. Stop asserting, and start handling
24711 TLS errors better in other situations too.
24712 - When the controller asks us to tell it about all the debug-level
24713 logs, it turns out we were generating debug-level logs while
24714 telling it about them, which turns into a bad loop. Now keep
24715 track of whether you're sending a debug log to the controller,
24716 and don't log when you are.
24717 - Fix the "postdescriptor" feature of the controller interface: on
24718 non-complete success, only say "done" once.
24720 - Clients are now willing to load balance over up to 2mB, not 1mB,
24721 of advertised bandwidth capacity.
24722 - Add a NoPublish config option, so you can be a server (e.g. for
24723 testing running Tor servers in other Tor networks) without
24724 publishing your descriptor to the primary dirservers.
24727 Changes in version 0.1.0.3-rc - 2005-04-08
24728 o Improvements on 0.1.0.2-rc:
24729 - Client now retries when streams end early for 'hibernating' or
24730 'resource limit' reasons, rather than failing them.
24731 - More automated handling for dirserver operators:
24732 - Automatically approve nodes running 0.1.0.2-rc or later,
24733 now that the the reachability detection stuff is working.
24734 - Now we allow two unverified servers with the same nickname
24735 but different keys. But if a nickname is verified, only that
24736 nickname+key are allowed.
24737 - If you're an authdirserver connecting to an address:port,
24738 and it's not the OR you were expecting, forget about that
24739 descriptor. If he *was* the one you were expecting, then forget
24740 about all other descriptors for that address:port.
24741 - Allow servers to publish descriptors from 12 hours in the future.
24742 Corollary: only whine about clock skew from the dirserver if
24743 he's a trusted dirserver (since now even verified servers could
24744 have quite wrong clocks).
24745 - Adjust maximum skew and age for rendezvous descriptors: let skew
24746 be 48 hours rather than 90 minutes.
24747 - Efficiency improvements:
24748 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
24749 it much faster to look up a circuit for each relay cell.
24750 - Remove most calls to assert_all_pending_dns_resolves_ok(),
24751 since they're eating our cpu on exit nodes.
24752 - Stop wasting time doing a case insensitive comparison for every
24753 dns name every time we do any lookup. Canonicalize the names to
24754 lowercase and be done with it.
24755 - Start sending 'truncated' cells back rather than destroy cells,
24756 if the circuit closes in front of you. This means we won't have
24757 to abandon partially built circuits.
24758 - Only warn once per nickname from add_nickname_list_to_smartlist
24759 per failure, so an entrynode or exitnode choice that's down won't
24761 - Put a note in the torrc about abuse potential with the default
24763 - Revise control spec and implementation to allow all log messages to
24764 be sent to controller with their severities intact (suggested by
24765 Matt Edman). Update TorControl to handle new log event types.
24766 - Provide better explanation messages when controller's POSTDESCRIPTOR
24768 - Stop putting nodename in the Platform string in server descriptors.
24769 It doesn't actually help, and it is confusing/upsetting some people.
24771 o Bugfixes on 0.1.0.2-rc:
24772 - We were printing the host mask wrong in exit policies in server
24773 descriptors. This isn't a critical bug though, since we were still
24774 obeying the exit policy internally.
24775 - Fix Tor when compiled with libevent but without pthreads: move
24776 connection_unregister() from _connection_free() to
24778 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
24779 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
24780 when we look through the connection array, we'll find any of the
24781 cpu/dnsworkers. This is no good.
24783 o Bugfixes on 0.0.9.8:
24784 - Fix possible bug on threading platforms (e.g. win32) which was
24785 leaking a file descriptor whenever a cpuworker or dnsworker died.
24786 - When using preferred entry or exit nodes, ignore whether the
24787 circuit wants uptime or capacity. They asked for the nodes, they
24789 - chdir() to your datadirectory at the *end* of the daemonize process,
24790 not the beginning. This was a problem because the first time you
24791 run tor, if your datadir isn't there, and you have runasdaemon set
24792 to 1, it will try to chdir to it before it tries to create it. Oops.
24793 - Handle changed router status correctly when dirserver reloads
24794 fingerprint file. We used to be dropping all unverified descriptors
24795 right then. The bug was hidden because we would immediately
24796 fetch a directory from another dirserver, which would include the
24797 descriptors we just dropped.
24798 - When we're connecting to an OR and he's got a different nickname/key
24799 than we were expecting, only complain loudly if we're an OP or a
24800 dirserver. Complaining loudly to the OR admins just confuses them.
24801 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
24802 artificially capped at 500kB.
24805 Changes in version 0.0.9.8 - 2005-04-07
24806 o Bugfixes on 0.0.9.x:
24807 - We have a bug that I haven't found yet. Sometimes, very rarely,
24808 cpuworkers get stuck in the 'busy' state, even though the cpuworker
24809 thinks of itself as idle. This meant that no new circuits ever got
24810 established. Here's a workaround to kill any cpuworker that's been
24811 busy for more than 100 seconds.
24814 Changes in version 0.1.0.2-rc - 2005-04-01
24815 o Bugfixes on 0.1.0.1-rc:
24816 - Fixes on reachability detection:
24817 - Don't check for reachability while hibernating.
24818 - If ORPort is reachable but DirPort isn't, still publish the
24819 descriptor, but zero out DirPort until it's found reachable.
24820 - When building testing circs for ORPort testing, use only
24821 high-bandwidth nodes, so fewer circuits fail.
24822 - Complain about unreachable ORPort separately from unreachable
24823 DirPort, so the user knows what's going on.
24824 - Make sure we only conclude ORPort reachability if we didn't
24825 initiate the conn. Otherwise we could falsely conclude that
24826 we're reachable just because we connected to the guy earlier
24827 and he used that same pipe to extend to us.
24828 - Authdirservers shouldn't do ORPort reachability detection,
24829 since they're in clique mode, so it will be rare to find a
24830 server not already connected to them.
24831 - When building testing circuits, always pick middle hops running
24832 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
24833 bug. (This is a kludge; it will go away when 0.0.9.x becomes
24835 - When we decide we're reachable, actually publish our descriptor
24837 - Fix bug in redirectstream in the controller.
24838 - Fix the state descriptor strings so logs don't claim edge streams
24839 are in a different state than they actually are.
24840 - Use recent libevent features when possible (this only really affects
24841 win32 and osx right now, because the new libevent with these
24842 features hasn't been released yet). Add code to suppress spurious
24844 - Prevent possible segfault in connection_close_unattached_ap().
24845 - Fix newlines on torrc in win32.
24846 - Improve error msgs when tor-resolve fails.
24848 o Improvements on 0.0.9.x:
24849 - New experimental script tor/contrib/ExerciseServer.py (needs more
24850 work) that uses the controller interface to build circuits and
24851 fetch pages over them. This will help us bootstrap servers that
24852 have lots of capacity but haven't noticed it yet.
24853 - New experimental script tor/contrib/PathDemo.py (needs more work)
24854 that uses the controller interface to let you choose whole paths
24856 "<hostname>.<path,separated by dots>.<length of path>.path"
24857 - When we've connected to an OR and handshaked but didn't like
24858 the result, we were closing the conn without sending destroy
24859 cells back for pending circuits. Now send those destroys.
24862 Changes in version 0.0.9.7 - 2005-04-01
24863 o Bugfixes on 0.0.9.x:
24864 - Fix another race crash bug (thanks to Glenn Fink for reporting).
24865 - Compare identity to identity, not to nickname, when extending to
24866 a router not already in the directory. This was preventing us from
24867 extending to unknown routers. Oops.
24868 - Make sure to create OS X Tor user in <500 range, so we aren't
24869 creating actual system users.
24870 - Note where connection-that-hasn't-sent-end was marked, and fix
24871 a few really loud instances of this harmless bug (it's fixed more
24875 Changes in version 0.1.0.1-rc - 2005-03-28
24877 - Add reachability testing. Your Tor server will automatically try
24878 to see if its ORPort and DirPort are reachable from the outside,
24879 and it won't upload its descriptor until it decides they are.
24880 - Handle unavailable hidden services better. Handle slow or busy
24881 hidden services better.
24882 - Add support for CONNECTing through https proxies, with "HttpsProxy"
24884 - New exit policy: accept most low-numbered ports, rather than
24885 rejecting most low-numbered ports.
24886 - More Tor controller support (still experimental). See
24887 http://tor.eff.org/doc/control-spec.txt for all the new features,
24888 including signals to emulate unix signals from any platform;
24889 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
24890 closestream; closecircuit; etc.
24891 - Make nt services work and start on startup on win32 (based on
24892 patch by Matt Edman).
24893 - Add a new AddressMap config directive to rewrite incoming socks
24894 addresses. This lets you, for example, declare an implicit
24895 required exit node for certain sites.
24896 - Add a new TrackHostExits config directive to trigger addressmaps
24897 for certain incoming socks addresses -- for sites that break when
24898 your exit keeps changing (based on patch by Mike Perry).
24899 - Redo the client-side dns cache so it's just an addressmap too.
24900 - Notice when our IP changes, and reset stats/uptime/reachability.
24901 - When an application is using socks5, give him the whole variety of
24902 potential socks5 responses (connect refused, host unreachable, etc),
24903 rather than just "success" or "failure".
24904 - A more sane version numbering system. See
24905 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
24906 - New contributed script "exitlist": a simple python script to
24907 parse directories and find Tor nodes that exit to listed
24909 - New contributed script "privoxy-tor-toggle" to toggle whether
24910 Privoxy uses Tor. Seems to be configured for Debian by default.
24911 - Report HTTP reasons to client when getting a response from directory
24912 servers -- so you can actually know what went wrong.
24913 - New config option MaxAdvertisedBandwidth which lets you advertise
24914 a low bandwidthrate (to not attract as many circuits) while still
24915 allowing a higher bandwidthrate in reality.
24917 o Robustness/stability fixes:
24918 - Make Tor use Niels Provos's libevent instead of its current
24919 poll-but-sometimes-select mess. This will let us use faster async
24920 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
24922 - pthread support now too. This was forced because when we forked,
24923 we ended up wasting a lot of duplicate ram over time. Also switch
24924 to foo_r versions of some library calls to allow reentry and
24926 - Better handling for heterogeneous / unreliable nodes:
24927 - Annotate circuits w/ whether they aim to contain high uptime nodes
24928 and/or high capacity nodes. When building circuits, choose
24930 - This means that every single node in an intro rend circuit,
24931 not just the last one, will have a minimum uptime.
24932 - New config option LongLivedPorts to indicate application streams
24933 that will want high uptime circuits.
24934 - Servers reset uptime when a dir fetch entirely fails. This
24935 hopefully reflects stability of the server's network connectivity.
24936 - If somebody starts his tor server in Jan 2004 and then fixes his
24937 clock, don't make his published uptime be a year.
24938 - Reset published uptime when you wake up from hibernation.
24939 - Introduce a notion of 'internal' circs, which are chosen without
24940 regard to the exit policy of the last hop. Intro and rendezvous
24941 circs must be internal circs, to avoid leaking information. Resolve
24942 and connect streams can use internal circs if they want.
24943 - New circuit pooling algorithm: make sure to have enough circs around
24944 to satisfy any predicted ports, and also make sure to have 2 internal
24945 circs around if we've required internal circs lately (and with high
24946 uptime if we've seen that lately too).
24947 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
24948 which describes how often we retry making new circuits if current
24949 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
24950 how long we're willing to make use of an already-dirty circuit.
24951 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
24952 circ as necessary, if there are any completed ones lying around
24953 when we try to launch one.
24954 - Make hidden services try to establish a rendezvous for 30 seconds,
24955 rather than for n (where n=3) attempts to build a circuit.
24956 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
24957 "ShutdownWaitLength".
24958 - Try to be more zealous about calling connection_edge_end when
24959 things go bad with edge conns in connection.c.
24960 - Revise tor-spec to add more/better stream end reasons.
24961 - Revise all calls to connection_edge_end to avoid sending "misc",
24962 and to take errno into account where possible.
24965 - Fix a race condition that can trigger an assert, when we have a
24966 pending create cell and an OR connection fails right then.
24967 - Fix several double-mark-for-close bugs, e.g. where we were finding
24968 a conn for a cell even if that conn is already marked for close.
24969 - Make sequence of log messages when starting on win32 with no config
24970 file more reasonable.
24971 - When choosing an exit node for a new non-internal circ, don't take
24972 into account whether it'll be useful for any pending x.onion
24973 addresses -- it won't.
24974 - Turn addr_policy_compare from a tristate to a quadstate; this should
24975 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
24976 for google.com" problem.
24977 - Make "platform" string in descriptor more accurate for Win32 servers,
24978 so it's not just "unknown platform".
24979 - Fix an edge case in parsing config options (thanks weasel).
24980 If they say "--" on the commandline, it's not an option.
24981 - Reject odd-looking addresses at the client (e.g. addresses that
24982 contain a colon), rather than having the server drop them because
24984 - tor-resolve requests were ignoring .exit if there was a working circuit
24985 they could use instead.
24986 - REUSEADDR on normal platforms means you can rebind to the port
24987 right after somebody else has let it go. But REUSEADDR on win32
24988 means to let you bind to the port _even when somebody else
24989 already has it bound_! So, don't do that on Win32.
24990 - Change version parsing logic: a version is "obsolete" if it is not
24991 recommended and (1) there is a newer recommended version in the
24992 same series, or (2) there are no recommended versions in the same
24993 series, but there are some recommended versions in a newer series.
24994 A version is "new" if it is newer than any recommended version in
24996 - Stop most cases of hanging up on a socks connection without sending
25000 - Require BandwidthRate to be at least 20kB/s for servers.
25001 - When a dirserver causes you to give a warn, mention which dirserver
25003 - New config option DirAllowPrivateAddresses for authdirservers.
25004 Now by default they refuse router descriptors that have non-IP or
25005 private-IP addresses.
25006 - Stop publishing socksport in the directory, since it's not
25007 actually meant to be public. For compatibility, publish a 0 there
25009 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
25010 smart" value, that is low for servers and high for clients.
25011 - If our clock jumps forward by 100 seconds or more, assume something
25012 has gone wrong with our network and abandon all not-yet-used circs.
25013 - Warn when exit policy implicitly allows local addresses.
25014 - If we get an incredibly skewed timestamp from a dirserver mirror
25015 that isn't a verified OR, don't warn -- it's probably him that's
25017 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
25018 cookies to disk and doesn't log each web request to disk. (Thanks
25019 to Brett Carrington for pointing this out.)
25020 - When a client asks us for a dir mirror and we don't have one,
25021 launch an attempt to get a fresh one.
25022 - If we're hibernating and we get a SIGINT, exit immediately.
25023 - Add --with-dmalloc ./configure option, to track memory leaks.
25024 - And try to free all memory on closing, so we can detect what
25026 - Cache local dns resolves correctly even when they're .exit
25028 - Give a better warning when some other server advertises an
25029 ORPort that is actually an apache running ssl.
25030 - Add "opt hibernating 1" to server descriptor to make it clearer
25031 whether the server is hibernating.
25034 Changes in version 0.0.9.6 - 2005-03-24
25035 o Bugfixes on 0.0.9.x (crashes and asserts):
25036 - Add new end stream reasons to maintainance branch. Fix bug where
25037 reason (8) could trigger an assert. Prevent bug from recurring.
25038 - Apparently win32 stat wants paths to not end with a slash.
25039 - Fix assert triggers in assert_cpath_layer_ok(), where we were
25040 blowing away the circuit that conn->cpath_layer points to, then
25041 checking to see if the circ is well-formed. Backport check to make
25042 sure we dont use the cpath on a closed connection.
25043 - Prevent circuit_resume_edge_reading_helper() from trying to package
25044 inbufs for marked-for-close streams.
25045 - Don't crash on hup if your options->address has become unresolvable.
25046 - Some systems (like OS X) sometimes accept() a connection and tell
25047 you the remote host is 0.0.0.0:0. If this happens, due to some
25048 other mis-features, we get confused; so refuse the conn for now.
25050 o Bugfixes on 0.0.9.x (other):
25051 - Fix harmless but scary "Unrecognized content encoding" warn message.
25052 - Add new stream error reason: TORPROTOCOL reason means "you are not
25053 speaking a version of Tor I understand; say bye-bye to your stream."
25054 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
25055 into the future, now that we are more tolerant of skew. This
25056 resolves a bug where a Tor server would refuse to cache a directory
25057 because all the directories it gets are too far in the future;
25058 yet the Tor server never logs any complaints about clock skew.
25059 - Mac packaging magic: make man pages useable, and do not overwrite
25060 existing torrc files.
25061 - Make OS X log happily to /var/log/tor/tor.log
25064 Changes in version 0.0.9.5 - 2005-02-22
25065 o Bugfixes on 0.0.9.x:
25066 - Fix an assert race at exit nodes when resolve requests fail.
25067 - Stop picking unverified dir mirrors--it only leads to misery.
25068 - Patch from Matt Edman to make NT services work better. Service
25069 support is still not compiled into the executable by default.
25070 - Patch from Dmitri Bely so the Tor service runs better under
25071 the win32 SYSTEM account.
25072 - Make tor-resolve actually work (?) on Win32.
25073 - Fix a sign bug when getrlimit claims to have 4+ billion
25074 file descriptors available.
25075 - Stop refusing to start when bandwidthburst == bandwidthrate.
25076 - When create cells have been on the onion queue more than five
25077 seconds, just send back a destroy and take them off the list.
25080 Changes in version 0.0.9.4 - 2005-02-03
25081 o Bugfixes on 0.0.9:
25082 - Fix an assert bug that took down most of our servers: when
25083 a server claims to have 1 GB of bandwidthburst, don't
25085 - Don't crash as badly if we have spawned the max allowed number
25086 of dnsworkers, or we're out of file descriptors.
25087 - Block more file-sharing ports in the default exit policy.
25088 - MaxConn is now automatically set to the hard limit of max
25089 file descriptors we're allowed (ulimit -n), minus a few for
25091 - Give a clearer message when servers need to raise their
25092 ulimit -n when they start running out of file descriptors.
25093 - SGI Compatibility patches from Jan Schaumann.
25094 - Tolerate a corrupt cached directory better.
25095 - When a dirserver hasn't approved your server, list which one.
25096 - Go into soft hibernation after 95% of the bandwidth is used,
25097 not 99%. This is especially important for daily hibernators who
25098 have a small accounting max. Hopefully it will result in fewer
25099 cut connections when the hard hibernation starts.
25100 - Load-balance better when using servers that claim more than
25101 800kB/s of capacity.
25102 - Make NT services work (experimental, only used if compiled in).
25105 Changes in version 0.0.9.3 - 2005-01-21
25106 o Bugfixes on 0.0.9:
25107 - Backport the cpu use fixes from main branch, so busy servers won't
25108 need as much processor time.
25109 - Work better when we go offline and then come back, or when we
25110 run Tor at boot before the network is up. We do this by
25111 optimistically trying to fetch a new directory whenever an
25112 application request comes in and we think we're offline -- the
25113 human is hopefully a good measure of when the network is back.
25114 - Backport some minimal hidserv bugfixes: keep rend circuits open as
25115 long as you keep using them; actually publish hidserv descriptors
25116 shortly after they change, rather than waiting 20-40 minutes.
25117 - Enable Mac startup script by default.
25118 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
25119 - When you update AllowUnverifiedNodes or FirewallPorts via the
25120 controller's setconf feature, we were always appending, never
25122 - When you update HiddenServiceDir via setconf, it was screwing up
25123 the order of reading the lines, making it fail.
25124 - Do not rewrite a cached directory back to the cache; otherwise we
25125 will think it is recent and not fetch a newer one on startup.
25126 - Workaround for webservers that lie about Content-Encoding: Tor
25127 now tries to autodetect compressed directories and compression
25128 itself. This lets us Proxypass dir fetches through apache.
25131 Changes in version 0.0.9.2 - 2005-01-04
25132 o Bugfixes on 0.0.9 (crashes and asserts):
25133 - Fix an assert on startup when the disk is full and you're logging
25135 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
25136 style address, then we'd crash.
25137 - Fix an assert trigger when the running-routers string we get from
25138 a dirserver is broken.
25139 - Make worker threads start and run on win32. Now win32 servers
25141 - Bandaid (not actually fix, but now it doesn't crash) an assert
25142 where the dns worker dies mysteriously and the main Tor process
25143 doesn't remember anything about the address it was resolving.
25145 o Bugfixes on 0.0.9 (Win32):
25146 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
25147 name out of the warning/assert messages.
25148 - Fix a superficial "unhandled error on read" bug on win32.
25149 - The win32 installer no longer requires a click-through for our
25150 license, since our Free Software license grants rights but does not
25152 - Win32: When connecting to a dirserver fails, try another one
25153 immediately. (This was already working for non-win32 Tors.)
25154 - Stop trying to parse $HOME on win32 when hunting for default
25156 - Make tor-resolve.c work on win32 by calling network_init().
25158 o Bugfixes on 0.0.9 (other):
25159 - Make 0.0.9.x build on Solaris again.
25160 - Due to a fencepost error, we were blowing away the \n when reporting
25161 confvalue items in the controller. So asking for multiple config
25162 values at once couldn't work.
25163 - When listing circuits that are pending on an opening OR connection,
25164 if we're an OR we were listing circuits that *end* at us as
25165 being pending on every listener, dns/cpu worker, etc. Stop that.
25166 - Dirservers were failing to create 'running-routers' or 'directory'
25167 strings if we had more than some threshold of routers. Fix them so
25168 they can handle any number of routers.
25169 - Fix a superficial "Duplicate mark for close" bug.
25170 - Stop checking for clock skew for OR connections, even for servers.
25171 - Fix a fencepost error that was chopping off the last letter of any
25172 nickname that is the maximum allowed nickname length.
25173 - Update URLs in log messages so they point to the new website.
25174 - Fix a potential problem in mangling server private keys while
25175 writing to disk (not triggered yet, as far as we know).
25176 - Include the licenses for other free software we include in Tor,
25177 now that we're shipping binary distributions more regularly.
25180 Changes in version 0.0.9.1 - 2004-12-15
25181 o Bugfixes on 0.0.9:
25182 - Make hibernation actually work.
25183 - Make HashedControlPassword config option work.
25184 - When we're reporting event circuit status to a controller,
25185 don't use the stream status code.
25188 Changes in version 0.0.9 - 2004-12-12
25190 - Clean up manpage and torrc.sample file.
25191 - Clean up severities and text of log warnings.
25193 - Make servers trigger an assert when they enter hibernation.
25196 Changes in version 0.0.9rc7 - 2004-12-08
25197 o Bugfixes on 0.0.9rc:
25198 - Fix a stack-trashing crash when an exit node begins hibernating.
25199 - Avoid looking at unallocated memory while considering which
25200 ports we need to build circuits to cover.
25201 - Stop a sigpipe: when an 'end' cell races with eof from the app,
25202 we shouldn't hold-open-until-flush if the eof arrived first.
25203 - Fix a bug with init_cookie_authentication() in the controller.
25204 - When recommending new-format log lines, if the upper bound is
25205 LOG_ERR, leave it implicit.
25207 o Bugfixes on 0.0.8.1:
25208 - Fix a whole slew of memory leaks.
25209 - Fix isspace() and friends so they still make Solaris happy
25210 but also so they don't trigger asserts on win32.
25211 - Fix parse_iso_time on platforms without strptime (eg win32).
25212 - win32: tolerate extra "readable" events better.
25213 - win32: when being multithreaded, leave parent fdarray open.
25214 - Make unit tests work on win32.
25217 Changes in version 0.0.9rc6 - 2004-12-06
25218 o Bugfixes on 0.0.9pre:
25219 - Clean up some more integer underflow opportunities (not exploitable
25221 - While hibernating, hup should not regrow our listeners.
25222 - Send an end to the streams we close when we hibernate, rather
25223 than just chopping them off.
25224 - React to eof immediately on non-open edge connections.
25226 o Bugfixes on 0.0.8.1:
25227 - Calculate timeout for waiting for a connected cell from the time
25228 we sent the begin cell, not from the time the stream started. If
25229 it took a long time to establish the circuit, we would time out
25230 right after sending the begin cell.
25231 - Fix router_compare_addr_to_addr_policy: it was not treating a port
25232 of * as always matching, so we were picking reject *:* nodes as
25233 exit nodes too. Oops.
25236 - New circuit building strategy: keep a list of ports that we've
25237 used in the past 6 hours, and always try to have 2 circuits open
25238 or on the way that will handle each such port. Seed us with port
25239 80 so web users won't complain that Tor is "slow to start up".
25240 - Make kill -USR1 dump more useful stats about circuits.
25241 - When warning about retrying or giving up, print the address, so
25242 the user knows which one it's talking about.
25243 - If you haven't used a clean circuit in an hour, throw it away,
25244 just to be on the safe side. (This means after 6 hours a totally
25245 unused Tor client will have no circuits open.)
25248 Changes in version 0.0.9rc5 - 2004-12-01
25249 o Bugfixes on 0.0.8.1:
25250 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
25251 - Let resolve conns retry/expire also, rather than sticking around
25253 - If we are using select, make sure we stay within FD_SETSIZE.
25255 o Bugfixes on 0.0.9pre:
25256 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
25257 but doesn't seem to be currently; thanks to Ilja van Sprundel for
25259 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
25260 instead. Impose minima and maxima for all *Period options; impose
25261 even tighter maxima for fetching if we are a caching dirserver.
25262 Clip rather than rejecting.
25263 - Fetch cached running-routers from servers that serve it (that is,
25264 authdirservers and servers running 0.0.9rc5-cvs or later.)
25267 - Accept *:706 (silc) in default exit policy.
25268 - Implement new versioning format for post 0.1.
25269 - Support "foo.nickname.exit" addresses, to let Alice request the
25270 address "foo" as viewed by exit node "nickname". Based on a patch
25272 - Make tor --version --version dump the cvs Id of every file.
25275 Changes in version 0.0.9rc4 - 2004-11-28
25276 o Bugfixes on 0.0.8.1:
25277 - Make windows sockets actually non-blocking (oops), and handle
25278 win32 socket errors better.
25280 o Bugfixes on 0.0.9rc1:
25281 - Actually catch the -USR2 signal.
25284 Changes in version 0.0.9rc3 - 2004-11-25
25285 o Bugfixes on 0.0.8.1:
25286 - Flush the log file descriptor after we print "Tor opening log file",
25287 so we don't see those messages days later.
25289 o Bugfixes on 0.0.9rc1:
25290 - Make tor-resolve work again.
25291 - Avoid infinite loop in tor-resolve if tor hangs up on it.
25292 - Fix an assert trigger for clients/servers handling resolves.
25295 Changes in version 0.0.9rc2 - 2004-11-24
25296 o Bugfixes on 0.0.9rc1:
25297 - I broke socks5 support while fixing the eof bug.
25298 - Allow unitless bandwidths and intervals; they default to bytes
25300 - New servers don't start out hibernating; they are active until
25301 they run out of bytes, so they have a better estimate of how
25302 long it takes, and so their operators can know they're working.
25305 Changes in version 0.0.9rc1 - 2004-11-23
25306 o Bugfixes on 0.0.8.1:
25307 - Finally fix a bug that's been plaguing us for a year:
25308 With high load, circuit package window was reaching 0. Whenever
25309 we got a circuit-level sendme, we were reading a lot on each
25310 socket, but only writing out a bit. So we would eventually reach
25311 eof. This would be noticed and acted on even when there were still
25312 bytes sitting in the inbuf.
25313 - When poll() is interrupted, we shouldn't believe the revents values.
25315 o Bugfixes on 0.0.9pre6:
25316 - Fix hibernate bug that caused pre6 to be broken.
25317 - Don't keep rephist info for routers that haven't had activity for
25318 24 hours. (This matters now that clients have keys, since we track
25320 - Never call close_temp_logs while validating log options.
25321 - Fix backslash-escaping on tor.sh.in and torctl.in.
25324 - Implement weekly/monthly/daily accounting: now you specify your
25325 hibernation properties by
25326 AccountingMax N bytes|KB|MB|GB|TB
25327 AccountingStart day|week|month [day] HH:MM
25328 Defaults to "month 1 0:00".
25329 - Let bandwidth and interval config options be specified as 5 bytes,
25330 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
25331 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
25332 get back to normal.)
25333 - If your requested entry or exit node has advertised bandwidth 0,
25335 - Be more greedy about filling up relay cells -- we try reading again
25336 once we've processed the stuff we read, in case enough has arrived
25337 to fill the last cell completely.
25338 - Apply NT service patch from Osamu Fujino. Still needs more work.
25341 Changes in version 0.0.9pre6 - 2004-11-15
25342 o Bugfixes on 0.0.8.1:
25343 - Fix assert failure on malformed socks4a requests.
25344 - Use identity comparison, not nickname comparison, to choose which
25345 half of circuit-ID-space each side gets to use. This is needed
25346 because sometimes we think of a router as a nickname, and sometimes
25347 as a hex ID, and we can't predict what the other side will do.
25348 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
25349 write() call will fail and we handle it there.
25350 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
25351 and smartlist_len, which are two major profiling offenders.
25353 o Bugfixes on 0.0.9pre5:
25354 - Fix a bug in read_all that was corrupting config files on windows.
25355 - When we're raising the max number of open file descriptors to
25356 'unlimited', don't log that we just raised it to '-1'.
25357 - Include event code with events, as required by control-spec.txt.
25358 - Don't give a fingerprint when clients do --list-fingerprint:
25359 it's misleading, because it will never be the same again.
25360 - Stop using strlcpy in tor_strndup, since it was slowing us
25362 - Remove warn on startup about missing cached-directory file.
25363 - Make kill -USR1 work again.
25364 - Hibernate if we start tor during the "wait for wakeup-time" phase
25365 of an accounting interval. Log our hibernation plans better.
25366 - Authoritative dirservers now also cache their directory, so they
25367 have it on start-up.
25370 - Fetch running-routers; cache running-routers; compress
25371 running-routers; serve compressed running-routers.z
25372 - Add NSI installer script contributed by J Doe.
25373 - Commit VC6 and VC7 workspace/project files.
25374 - Commit a tor.spec for making RPM files, with help from jbash.
25375 - Add contrib/torctl.in contributed by Glenn Fink.
25376 - Implement the control-spec's SAVECONF command, to write your
25377 configuration to torrc.
25378 - Get cookie authentication for the controller closer to working.
25379 - Include control-spec.txt in the tarball.
25380 - When set_conf changes our server descriptor, upload a new copy.
25381 But don't upload it too often if there are frequent changes.
25382 - Document authentication config in man page, and document signals
25384 - Clean up confusing parts of man page and torrc.sample.
25385 - Make expand_filename handle ~ and ~username.
25386 - Use autoconf to enable largefile support where necessary. Use
25387 ftello where available, since ftell can fail at 2GB.
25388 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
25389 log more informatively.
25390 - Give a slightly more useful output for "tor -h".
25391 - Refuse application socks connections to port 0.
25392 - Check clock skew for verified servers, but allow unverified
25393 servers and clients to have any clock skew.
25394 - Break DirFetchPostPeriod into:
25395 - DirFetchPeriod for fetching full directory,
25396 - StatusFetchPeriod for fetching running-routers,
25397 - DirPostPeriod for posting server descriptor,
25398 - RendPostPeriod for posting hidden service descriptors.
25399 - Make sure the hidden service descriptors are at a random offset
25400 from each other, to hinder linkability.
25403 Changes in version 0.0.9pre5 - 2004-11-09
25404 o Bugfixes on 0.0.9pre4:
25405 - Fix a seg fault in unit tests (doesn't affect main program).
25406 - Fix an assert bug where a hidden service provider would fail if
25407 the first hop of his rendezvous circuit was down.
25408 - Hidden service operators now correctly handle version 1 style
25409 INTRODUCE1 cells (nobody generates them still, so not a critical
25411 - If do_hup fails, actually notice.
25412 - Handle more errnos from accept() without closing the listener.
25413 Some OpenBSD machines were closing their listeners because
25414 they ran out of file descriptors.
25415 - Send resolve cells to exit routers that are running a new
25416 enough version of the resolve code to work right.
25417 - Better handling of winsock includes on non-MSV win32 compilers.
25418 - Some people had wrapped their tor client/server in a script
25419 that would restart it whenever it died. This did not play well
25420 with our "shut down if your version is obsolete" code. Now people
25421 don't fetch a new directory if their local cached version is
25423 - Make our autogen.sh work on ksh as well as bash.
25426 - Hibernation: New config option "AccountingMaxKB" lets you
25427 set how many KBytes per month you want to allow your server to
25428 consume. Rather than spreading those bytes out evenly over the
25429 month, we instead hibernate for some of the month and pop up
25430 at a deterministic time, work until the bytes are consumed, then
25431 hibernate again. Config option "MonthlyAccountingStart" lets you
25432 specify which day of the month your billing cycle starts on.
25433 - Control interface: a separate program can now talk to your
25434 client/server over a socket, and get/set config options, receive
25435 notifications of circuits and streams starting/finishing/dying,
25436 bandwidth used, etc. The next step is to get some GUIs working.
25437 Let us know if you want to help out. See doc/control-spec.txt .
25438 - Ship a contrib/tor-control.py as an example script to interact
25439 with the control port.
25440 - "tor --hash-password zzyxz" will output a salted password for
25441 use in authenticating to the control interface.
25442 - New log format in config:
25443 "Log minsev[-maxsev] stdout|stderr|syslog" or
25444 "Log minsev[-maxsev] file /var/foo"
25447 - DirPolicy config option, to let people reject incoming addresses
25448 from their dirserver.
25449 - "tor --list-fingerprint" will list your identity key fingerprint
25451 - Add "pass" target for RedirectExit, to make it easier to break
25452 out of a sequence of RedirectExit rules.
25453 - Clients now generate a TLS cert too, in preparation for having
25454 them act more like real nodes.
25455 - Ship src/win32/ in the tarball, so people can use it to build.
25456 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
25458 - New "router-status" line in directory, to better bind each verified
25459 nickname to its identity key.
25460 - Deprecate unofficial config option abbreviations, and abbreviations
25461 not on the command line.
25462 - Add a pure-C tor-resolve implementation.
25463 - Use getrlimit and friends to ensure we can reach MaxConn (currently
25464 1024) file descriptors.
25466 o Code security improvements, inspired by Ilja:
25467 - Replace sprintf with snprintf. (I think they were all safe, but
25469 - Replace strcpy/strncpy with strlcpy in more places.
25470 - Avoid strcat; use snprintf or strlcat instead.
25471 - snprintf wrapper with consistent (though not C99) overflow behavior.
25474 Changes in version 0.0.9pre4 - 2004-10-17
25475 o Bugfixes on 0.0.9pre3:
25476 - If the server doesn't specify an exit policy, use the real default
25477 exit policy, not reject *:*.
25478 - Ignore fascistfirewall when uploading/downloading hidden service
25479 descriptors, since we go through Tor for those; and when using
25480 an HttpProxy, since we assume it can reach them all.
25481 - When looking for an authoritative dirserver, use only the ones
25482 configured at boot. Don't bother looking in the directory.
25483 - The rest of the fix for get_default_conf_file() on older win32.
25484 - Make 'Routerfile' config option obsolete.
25487 - New 'MyFamily nick1,...' config option for a server to
25488 specify other servers that shouldn't be used in the same circuit
25489 with it. Only believed if nick1 also specifies us.
25490 - New 'NodeFamily nick1,nick2,...' config option for a client to
25491 specify nodes that it doesn't want to use in the same circuit.
25492 - New 'Redirectexit pattern address:port' config option for a
25493 server to redirect exit connections, e.g. to a local squid.
25496 Changes in version 0.0.9pre3 - 2004-10-13
25497 o Bugfixes on 0.0.8.1:
25498 - Better torrc example lines for dirbindaddress and orbindaddress.
25499 - Improved bounds checking on parsed ints (e.g. config options and
25500 the ones we find in directories.)
25501 - Better handling of size_t vs int, so we're more robust on 64
25503 - Fix the rest of the bug where a newly started OR would appear
25504 as unverified even after we've added his fingerprint and hupped
25506 - Fix a bug from 0.0.7: when read() failed on a stream, we would
25507 close it without sending back an end. So 'connection refused'
25508 would simply be ignored and the user would get no response.
25510 o Bugfixes on 0.0.9pre2:
25511 - Serving the cached-on-disk directory to people is bad. We now
25512 provide no directory until we've fetched a fresh one.
25513 - Workaround for bug on windows where cached-directories get crlf
25515 - Make get_default_conf_file() work on older windows too.
25516 - If we write a *:* exit policy line in the descriptor, don't write
25517 any more exit policy lines.
25520 - Use only 0.0.9pre1 and later servers for resolve cells.
25521 - Make the dirservers file obsolete.
25522 - Include a dir-signing-key token in directories to tell the
25523 parsing entity which key is being used to sign.
25524 - Remove the built-in bulky default dirservers string.
25525 - New config option "Dirserver %s:%d [fingerprint]", which can be
25526 repeated as many times as needed. If no dirservers specified,
25527 default to moria1,moria2,tor26.
25528 - Make moria2 advertise a dirport of 80, so people behind firewalls
25529 will be able to get a directory.
25530 - Http proxy support
25531 - Dirservers translate requests for http://%s:%d/x to /x
25532 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
25533 be routed through this host.
25534 - Clients ask for /tor/x rather than /x for new enough dirservers.
25535 This way we can one day coexist peacefully with apache.
25536 - Clients specify a "Host: %s%d" http header, to be compatible
25537 with more proxies, and so running squid on an exit node can work.
25540 Changes in version 0.0.8.1 - 2004-10-13
25542 - Fix a seg fault that can be triggered remotely for Tor
25543 clients/servers with an open dirport.
25544 - Fix a rare assert trigger, where routerinfos for entries in
25545 our cpath would expire while we're building the path.
25546 - Fix a bug in OutboundBindAddress so it (hopefully) works.
25547 - Fix a rare seg fault for people running hidden services on
25548 intermittent connections.
25549 - Fix a bug in parsing opt keywords with objects.
25550 - Fix a stale pointer assert bug when a stream detaches and
25552 - Fix a string format vulnerability (probably not exploitable)
25553 in reporting stats locally.
25554 - Fix an assert trigger: sometimes launching circuits can fail
25555 immediately, e.g. because too many circuits have failed recently.
25556 - Fix a compile warning on 64 bit platforms.
25559 Changes in version 0.0.9pre2 - 2004-10-03
25561 - Make fetching a cached directory work for 64-bit platforms too.
25562 - Make zlib.h a required header, not an optional header.
25565 Changes in version 0.0.9pre1 - 2004-10-01
25567 - Stop using separate defaults for no-config-file and
25568 empty-config-file. Now you have to explicitly turn off SocksPort,
25569 if you don't want it open.
25570 - Fix a bug in OutboundBindAddress so it (hopefully) works.
25571 - Improve man page to mention more of the 0.0.8 features.
25572 - Fix a rare seg fault for people running hidden services on
25573 intermittent connections.
25574 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
25576 - Fix more dns related bugs: send back resolve_failed and end cells
25577 more reliably when the resolve fails, rather than closing the
25578 circuit and then trying to send the cell. Also attach dummy resolve
25579 connections to a circuit *before* calling dns_resolve(), to fix
25580 a bug where cached answers would never be sent in RESOLVED cells.
25581 - When we run out of disk space, or other log writing error, don't
25582 crash. Just stop logging to that log and continue.
25583 - We were starting to daemonize before we opened our logs, so if
25584 there were any problems opening logs, we would complain to stderr,
25585 which wouldn't work, and then mysteriously exit.
25586 - Fix a rare bug where sometimes a verified OR would connect to us
25587 before he'd uploaded his descriptor, which would cause us to
25588 assign conn->nickname as though he's unverified. Now we look through
25589 the fingerprint list to see if he's there.
25590 - Fix a rare assert trigger, where routerinfos for entries in
25591 our cpath would expire while we're building the path.
25594 - Clients can ask dirservers for /dir.z to get a compressed version
25595 of the directory. Only works for servers running 0.0.9, of course.
25596 - Make clients cache directories and use them to seed their router
25597 lists at startup. This means clients have a datadir again.
25598 - Configuration infrastructure support for warning on obsolete
25600 - Respond to content-encoding headers by trying to uncompress as
25602 - Reply with a deflated directory when a client asks for "dir.z".
25603 We could use allow-encodings instead, but allow-encodings isn't
25604 specified in HTTP 1.0.
25605 - Raise the max dns workers from 50 to 100.
25606 - Discourage people from setting their dirfetchpostperiod more often
25607 than once per minute.
25608 - Protect dirservers from overzealous descriptor uploading -- wait
25609 10 seconds after directory gets dirty, before regenerating.
25612 Changes in version 0.0.8 - 2004-08-25
25613 o Port it to SunOS 5.9 / Athena
25616 Changes in version 0.0.8rc2 - 2004-08-20
25617 o Make it compile on cygwin again.
25618 o When picking unverified routers, skip those with low uptime and/or
25619 low bandwidth, depending on what properties you care about.
25622 Changes in version 0.0.8rc1 - 2004-08-18
25623 o Changes from 0.0.7.3:
25625 - Fix assert triggers: if the other side returns an address 0.0.0.0,
25626 don't put it into the client dns cache.
25627 - If a begin failed due to exit policy, but we believe the IP address
25628 should have been allowed, switch that router to exitpolicy reject *:*
25629 until we get our next directory.
25631 - Clients choose nodes proportional to advertised bandwidth.
25632 - Avoid using nodes with low uptime as introduction points.
25633 - Handle servers with dynamic IP addresses: don't replace
25634 options->Address with the resolved one at startup, and
25635 detect our address right before we make a routerinfo each time.
25636 - 'FascistFirewall' option to pick dirservers and ORs on specific
25637 ports; plus 'FirewallPorts' config option to tell FascistFirewall
25638 which ports are open. (Defaults to 80,443)
25639 - Be more aggressive about trying to make circuits when the network
25640 has changed (e.g. when you unsuspend your laptop).
25641 - Check for time skew on http headers; report date in response to
25643 - If the entrynode config line has only one node, don't pick it as
25645 - Add strict{entry|exit}nodes config options. If set to 1, then
25646 we refuse to build circuits that don't include the specified entry
25648 - OutboundBindAddress config option, to bind to a specific
25649 IP address for outgoing connect()s.
25650 - End truncated log entries (e.g. directories) with "[truncated]".
25652 o Patches to 0.0.8preX:
25654 - Patches to compile and run on win32 again (maybe)?
25655 - Fix crash when looking for ~/.torrc with no $HOME set.
25656 - Fix a race bug in the unit tests.
25657 - Handle verified/unverified name collisions better when new
25658 routerinfo's arrive in a directory.
25659 - Sometimes routers were getting entered into the stats before
25660 we'd assigned their identity_digest. Oops.
25661 - Only pick and establish intro points after we've gotten a
25664 - AllowUnverifiedNodes config option to let circuits choose no-name
25665 routers in entry,middle,exit,introduction,rendezvous positions.
25666 Allow middle and rendezvous positions by default.
25667 - Add a man page for tor-resolve.
25670 Changes in version 0.0.7.3 - 2004-08-12
25671 o Stop dnsworkers from triggering an assert failure when you
25672 ask them to resolve the host "".
25675 Changes in version 0.0.8pre3 - 2004-08-09
25676 o Changes from 0.0.7.2:
25677 - Allow multiple ORs with same nickname in routerlist -- now when
25678 people give us one identity key for a nickname, then later
25679 another, we don't constantly complain until the first expires.
25680 - Remember used bandwidth (both in and out), and publish 15-minute
25681 snapshots for the past day into our descriptor.
25682 - You can now fetch $DIRURL/running-routers to get just the
25683 running-routers line, not the whole descriptor list. (But
25684 clients don't use this yet.)
25685 - When people mistakenly use Tor as an http proxy, point them
25686 at the tor-doc.html rather than the INSTALL.
25687 - Remove our mostly unused -- and broken -- hex_encode()
25688 function. Use base16_encode() instead. (Thanks to Timo Lindfors
25689 for pointing out this bug.)
25690 - Rotate onion keys every 12 hours, not every 2 hours, so we have
25691 fewer problems with people using the wrong key.
25692 - Change the default exit policy to reject the default edonkey,
25693 kazaa, gnutella ports.
25694 - Add replace_file() to util.[ch] to handle win32's rename().
25696 o Changes from 0.0.8preX:
25697 - Fix two bugs in saving onion keys to disk when rotating, so
25698 hopefully we'll get fewer people using old onion keys.
25699 - Fix an assert error that was making SocksPolicy not work.
25700 - Be willing to expire routers that have an open dirport -- it's
25701 just the authoritative dirservers we want to not forget.
25702 - Reject tor-resolve requests for .onion addresses early, so we
25703 don't build a whole rendezvous circuit and then fail.
25704 - When you're warning a server that he's unverified, don't cry
25705 wolf unpredictably.
25706 - Fix a race condition: don't try to extend onto a connection
25707 that's still handshaking.
25708 - For servers in clique mode, require the conn to be open before
25709 you'll choose it for your path.
25710 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
25711 end relay cell, etc.
25712 - Measure bandwidth capacity over the last 24 hours, not just 12
25713 - Bugfix: authoritative dirservers were making and signing a new
25714 directory for each client, rather than reusing the cached one.
25717 Changes in version 0.0.8pre2 - 2004-08-04
25718 o Changes from 0.0.7.2:
25720 - Check directory signature _before_ you decide whether you're
25721 you're running an obsolete version and should exit.
25722 - Check directory signature _before_ you parse the running-routers
25723 list to decide who's running or verified.
25724 - Bugfixes and features:
25725 - Check return value of fclose while writing to disk, so we don't
25726 end up with broken files when servers run out of disk space.
25727 - Log a warning if the user uses an unsafe socks variant, so people
25728 are more likely to learn about privoxy or socat.
25729 - Dirservers now include RFC1123-style dates in the HTTP headers,
25730 which one day we will use to better detect clock skew.
25732 o Changes from 0.0.8pre1:
25733 - Make it compile without warnings again on win32.
25734 - Log a warning if you're running an unverified server, to let you
25735 know you might want to get it verified.
25736 - Only pick a default nickname if you plan to be a server.
25739 Changes in version 0.0.8pre1 - 2004-07-23
25741 - Made our unit tests compile again on OpenBSD 3.5, and tor
25742 itself compile again on OpenBSD on a sparc64.
25743 - We were neglecting milliseconds when logging on win32, so
25744 everything appeared to happen at the beginning of each second.
25746 o Protocol changes:
25747 - 'Extend' relay cell payloads now include the digest of the
25748 intended next hop's identity key. Now we can verify that we're
25749 extending to the right router, and also extend to routers we
25750 hadn't heard of before.
25753 - Tor nodes can now act as relays (with an advertised ORPort)
25754 without being manually verified by the dirserver operators.
25755 - Uploaded descriptors of unverified routers are now accepted
25756 by the dirservers, and included in the directory.
25757 - Verified routers are listed by nickname in the running-routers
25758 list; unverified routers are listed as "$<fingerprint>".
25759 - We now use hash-of-identity-key in most places rather than
25760 nickname or addr:port, for improved security/flexibility.
25761 - To avoid Sybil attacks, paths still use only verified servers.
25762 But now we have a chance to play around with hybrid approaches.
25763 - Nodes track bandwidth usage to estimate capacity (not used yet).
25764 - ClientOnly option for nodes that never want to become servers.
25765 - Directory caching.
25766 - "AuthoritativeDir 1" option for the official dirservers.
25767 - Now other nodes (clients and servers) will cache the latest
25768 directory they've pulled down.
25769 - They can enable their DirPort to serve it to others.
25770 - Clients will pull down a directory from any node with an open
25771 DirPort, and check the signature/timestamp correctly.
25772 - Authoritative dirservers now fetch directories from other
25773 authdirservers, to stay better synced.
25774 - Running-routers list tells who's down also, along with noting
25775 if they're verified (listed by nickname) or unverified (listed
25777 - Allow dirservers to serve running-router list separately.
25778 This isn't used yet.
25779 - ORs connect-on-demand to other ORs
25780 - If you get an extend cell to an OR you're not connected to,
25781 connect, handshake, and forward the create cell.
25782 - The authoritative dirservers stay connected to everybody,
25783 and everybody stays connected to 0.0.7 servers, but otherwise
25784 clients/servers expire unused connections after 5 minutes.
25785 - When servers get a sigint, they delay 30 seconds (refusing new
25786 connections) then exit. A second sigint causes immediate exit.
25787 - File and name management:
25788 - Look for .torrc if no CONFDIR "torrc" is found.
25789 - If no datadir is defined, then choose, make, and secure ~/.tor
25791 - If torrc not found, exitpolicy reject *:*.
25792 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
25793 - If no nickname is defined, derive default from hostname.
25794 - Rename secret key files, e.g. identity.key -> secret_id_key,
25795 to discourage people from mailing their identity key to tor-ops.
25796 - Refuse to build a circuit before the directory has arrived --
25797 it won't work anyway, since you won't know the right onion keys
25799 - Try other dirservers immediately if the one you try is down. This
25800 should tolerate down dirservers better now.
25801 - Parse tor version numbers so we can do an is-newer-than check
25802 rather than an is-in-the-list check.
25803 - New socks command 'resolve', to let us shim gethostbyname()
25805 - A 'tor_resolve' script to access the socks resolve functionality.
25806 - A new socks-extensions.txt doc file to describe our
25807 interpretation and extensions to the socks protocols.
25808 - Add a ContactInfo option, which gets published in descriptor.
25809 - Publish OR uptime in descriptor (and thus in directory) too.
25810 - Write tor version at the top of each log file
25811 - New docs in the tarball:
25813 - Document that you should proxy your SSL traffic too.
25816 Changes in version 0.0.7.2 - 2004-07-07
25817 o A better fix for the 0.0.0.0 problem, that will hopefully
25818 eliminate the remaining related assertion failures.
25821 Changes in version 0.0.7.1 - 2004-07-04
25822 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
25823 since internally we use 0.0.0.0 to signify "not yet resolved".
25826 Changes in version 0.0.7 - 2004-06-07
25827 o Updated the man page to reflect the new features.
25830 Changes in version 0.0.7rc2 - 2004-06-06
25831 o Changes from 0.0.7rc1:
25832 - Make it build on Win32 again.
25833 o Changes from 0.0.6.2:
25834 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
25838 Changes in version 0.0.7rc1 - 2004-06-02
25840 - On sighup, we were adding another log without removing the first
25841 one. So log messages would get duplicated n times for n sighups.
25842 - Several cases of using a connection after we'd freed it. The
25843 problem was that connections that are pending resolve are in both
25844 the pending_resolve tree, and also the circuit's resolving_streams
25845 list. When you want to remove one, you must remove it from both.
25846 - Fix a double-mark-for-close where an end cell arrived for a
25847 resolving stream, and then the resolve failed.
25848 - Check directory signatures based on name of signer, not on whom
25849 we got the directory from. This will let us cache directories more
25852 - Crank up some of our constants to handle more users.
25855 Changes in version 0.0.7pre1 - 2004-06-02
25856 o Fixes for crashes and other obnoxious bugs:
25857 - Fix an epipe bug: sometimes when directory connections failed
25858 to connect, we would give them a chance to flush before closing
25860 - When we detached from a circuit because of resolvefailed, we
25861 would immediately try the same circuit twice more, and then
25862 give up on the resolve thinking we'd tried three different
25864 - Limit the number of intro circuits we'll attempt to build for a
25865 hidden service per 15-minute period.
25866 - Check recommended-software string *early*, before actually parsing
25867 the directory. Thus we can detect an obsolete version and exit,
25868 even if the new directory format doesn't parse.
25869 o Fixes for security bugs:
25870 - Remember which nodes are dirservers when you startup, and if a
25871 random OR enables his dirport, don't automatically assume he's
25872 a trusted dirserver.
25874 - Directory connections were asking the wrong poll socket to
25875 start writing, and not asking themselves to start writing.
25876 - When we detached from a circuit because we sent a begin but
25877 didn't get a connected, we would use it again the first time;
25878 but after that we would correctly switch to a different one.
25879 - Stop warning when the first onion decrypt attempt fails; they
25880 will sometimes legitimately fail now that we rotate keys.
25881 - Override unaligned-access-ok check when $host_cpu is ia64 or
25882 arm. Apparently they allow it but the kernel whines.
25883 - Dirservers try to reconnect periodically too, in case connections
25885 - Fix some memory leaks in directory servers.
25886 - Allow backslash in Win32 filenames.
25887 - Made Tor build complain-free on FreeBSD, hopefully without
25888 breaking other BSD builds. We'll see.
25890 - Doxygen markup on all functions and global variables.
25891 - Make directory functions update routerlist, not replace it. So
25892 now directory disagreements are not so critical a problem.
25893 - Remove the upper limit on number of descriptors in a dirserver's
25894 directory (not that we were anywhere close).
25895 - Allow multiple logfiles at different severity ranges.
25896 - Allow *BindAddress to specify ":port" rather than setting *Port
25897 separately. Allow multiple instances of each BindAddress config
25898 option, so you can bind to multiple interfaces if you want.
25899 - Allow multiple exit policy lines, which are processed in order.
25900 Now we don't need that huge line with all the commas in it.
25901 - Enable accept/reject policies on SOCKS connections, so you can bind
25902 to 0.0.0.0 but still control who can use your OP.
25905 Changes in version 0.0.6.2 - 2004-05-16
25906 o Our integrity-checking digest was checking only the most recent cell,
25907 not the previous cells like we'd thought.
25908 Thanks to Stefan Mark for finding the flaw!
25911 Changes in version 0.0.6.1 - 2004-05-06
25912 o Fix two bugs in our AES counter-mode implementation (this affected
25913 onion-level stream encryption, but not TLS-level). It turns
25914 out we were doing something much more akin to a 16-character
25915 polyalphabetic cipher. Oops.
25916 Thanks to Stefan Mark for finding the flaw!
25917 o Retire moria3 as a directory server, and add tor26 as a directory
25921 Changes in version 0.0.6 - 2004-05-02
25922 [version bump only]
25925 Changes in version 0.0.6rc4 - 2004-05-01
25926 o Update the built-in dirservers list to use the new directory format
25927 o Fix a rare seg fault: if a node offering a hidden service attempts
25928 to build a circuit to Alice's rendezvous point and fails before it
25929 reaches the last hop, it retries with a different circuit, but
25931 o Handle windows socket errors correctly.
25934 Changes in version 0.0.6rc3 - 2004-04-28
25935 o Don't expire non-general excess circuits (if we had enough
25936 circuits open, we were expiring rendezvous circuits -- even
25937 when they had a stream attached. oops.)
25938 o Fetch randomness from /dev/urandom better (not via fopen/fread)
25939 o Better debugging for tls errors
25940 o Some versions of openssl have an SSL_pending function that erroneously
25941 returns bytes when there is a non-application record pending.
25942 o Set Content-Type on the directory and hidserv descriptor.
25943 o Remove IVs from cipher code, since AES-ctr has none.
25944 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
25945 o We were using an array of length zero in a few places.
25946 o win32's gethostbyname can't resolve an IP to an IP.
25947 o win32's close can't close a socket.
25950 Changes in version 0.0.6rc2 - 2004-04-26
25951 o Fix a bug where we were closing tls connections intermittently.
25952 It turns out openssl keeps its errors around -- so if an error
25953 happens, and you don't ask about it, and then another openssl
25954 operation happens and succeeds, and you ask if there was an error,
25955 it tells you about the first error. Fun fun.
25956 o Fix a bug that's been lurking since 27 may 03 (!)
25957 When passing back a destroy cell, we would use the wrong circ id.
25958 'Mostly harmless', but still worth fixing.
25959 o Since we don't support truncateds much, don't bother sending them;
25960 just close the circ.
25961 o check for <machine/limits.h> so we build on NetBSD again (I hope).
25962 o don't crash if a conn that sent a begin has suddenly lost its circuit
25963 (this was quite rare).
25966 Changes in version 0.0.6rc1 - 2004-04-25
25967 o We now rotate link (tls context) keys and onion keys.
25968 o CREATE cells now include oaep padding, so you can tell
25969 if you decrypted them correctly.
25970 o Add bandwidthburst to server descriptor.
25971 o Directories now say which dirserver signed them.
25972 o Use a tor_assert macro that logs failed assertions too.
25975 Changes in version 0.0.6pre5 - 2004-04-18
25976 o changes from 0.0.6pre4:
25977 - make tor build on broken freebsd 5.2 installs
25978 - fix a failed assert when you try an intro point, get a nack, and try
25979 a second one and it works.
25980 - when alice uses a port that the hidden service doesn't accept,
25981 it now sends back an end cell (denied by exit policy). otherwise
25982 alice would just have to wait to time out.
25983 - fix another rare bug: when we had tried all the intro
25984 points for a hidden service, we fetched the descriptor
25985 again, but we left our introcirc thinking it had already
25986 sent an intro, so it kept waiting for a response...
25987 - bugfix: when you sleep your hidden-service laptop, as soon
25988 as it wakes up it tries to upload a service descriptor, but
25989 socketpair fails for some reason (localhost not up yet?).
25990 now we simply give up on that upload, and we'll try again later.
25991 i'd still like to find the bug though.
25992 - if an intro circ waiting for an ack dies before getting one, then
25994 - we were reusing stale service descriptors and refetching usable
25998 Changes in version 0.0.6pre4 - 2004-04-14
25999 o changes from 0.0.6pre3:
26000 - when bob fails to connect to the rendezvous point, and his
26001 circ didn't fail because of the rendezvous point itself, then
26002 he retries a couple of times
26003 - we expire introduction and rendezvous circs more thoroughly
26004 (sometimes they were hanging around forever)
26005 - we expire unattached rendezvous streams that have been around
26006 too long (they were sticking around forever).
26007 - fix a measly fencepost error that was crashing everybody with
26011 Changes in version 0.0.6pre3 - 2004-04-14
26012 o changes from 0.0.6pre2:
26013 - make hup work again
26014 - fix some memory leaks for dirservers
26015 - allow more skew in rendezvous descriptor timestamps, to help
26016 handle people like blanu who don't know what time it is
26017 - normal circs are 3 hops, but some rend/intro circs are 4, if
26018 the initiator doesn't get to choose the last hop
26019 - send acks for introductions, so alice can know whether to try
26021 - bob publishes intro points more correctly
26022 o changes from 0.0.5:
26023 - fix an assert trigger that's been plaguing us since the days
26024 of 0.0.2prexx (thanks weasel!)
26025 - retry stream correctly when we fail to connect because of
26026 exit-policy-reject (should try another) or can't-resolve-address
26027 (also should try another, because dns on random internet servers
26029 - when we hup a dirserver and we've *removed* a server from the
26030 approved-routers list, now we remove that server from the
26031 in-memory directories too
26034 Changes in version 0.0.6pre2 - 2004-04-08
26035 o We fixed our base32 implementation. Now it works on all architectures.
26038 Changes in version 0.0.6pre1 - 2004-04-08
26040 - Hidden services and rendezvous points are implemented. Go to
26041 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
26042 hidden services. (This only works via a socks4a proxy such as
26043 Privoxy, and currently it's quite slow.)
26046 Changes in version 0.0.5 - 2004-03-30
26047 [version bump only]
26050 Changes in version 0.0.5rc3 - 2004-03-29
26051 o Install torrc as torrc.sample -- we no longer clobber your
26053 o Re-enable recommendedversion checking (we broke it in rc2, oops)
26054 o Add in a 'notice' log level for things the operator should hear
26055 but that aren't warnings
26058 Changes in version 0.0.5rc2 - 2004-03-29
26059 o Hold socks connection open until reply is flushed (if possible)
26060 o Make exit nodes resolve IPs to IPs immediately, rather than asking
26061 the dns farm to do it.
26062 o Fix c99 aliasing warnings in rephist.c
26063 o Don't include server descriptors that are older than 24 hours in the
26065 o Give socks 'reject' replies their whole 15s to attempt to flush,
26066 rather than seeing the 60s timeout and assuming the flush had failed.
26067 o Clean automake droppings from the cvs repository
26070 Changes in version 0.0.5rc1 - 2004-03-28
26071 o Fix mangled-state bug in directory fetching (was causing sigpipes).
26072 o Only build circuits after we've fetched the directory: clients were
26073 using only the directory servers before they'd fetched a directory.
26074 This also means longer startup time; so it goes.
26075 o Fix an assert trigger where an OP would fail to handshake, and we'd
26076 expect it to have a nickname.
26077 o Work around a tsocks bug: do a socks reject when AP connection dies
26078 early, else tsocks goes into an infinite loop.
26081 Changes in version 0.0.4 - 2004-03-26
26082 o When connecting to a dirserver or OR and the network is down,
26086 Changes in version 0.0.3 - 2004-03-26
26087 o Warn and fail if server chose a nickname with illegal characters
26088 o Port to Solaris and Sparc:
26089 - include missing header fcntl.h
26090 - have autoconf find -lsocket -lnsl automatically
26091 - deal with hardware word alignment
26092 - make uname() work (solaris has a different return convention)
26093 - switch from using signal() to sigaction()
26094 o Preliminary work on reputation system:
26095 - Keep statistics on success/fail of connect attempts; they're published
26096 by kill -USR1 currently.
26097 - Add a RunTesting option to try to learn link state by creating test
26098 circuits, even when SocksPort is off.
26099 - Remove unused open circuits when there are too many.
26102 Changes in version 0.0.2 - 2004-03-19
26103 - Include strlcpy and strlcat for safer string ops
26104 - define INADDR_NONE so we compile (but still not run) on solaris
26107 Changes in version 0.0.2pre27 - 2004-03-14
26109 - Allow internal tor networks (we were rejecting internal IPs,
26110 now we allow them if they're set explicitly).
26111 - And fix a few endian issues.
26114 Changes in version 0.0.2pre26 - 2004-03-14
26116 - If a stream times out after 15s without a connected cell, don't
26117 try that circuit again: try a new one.
26118 - Retry streams at most 4 times. Then give up.
26119 - When a dirserver gets a descriptor from an unknown router, it
26120 logs its fingerprint (so the dirserver operator can choose to
26121 accept it even without mail from the server operator).
26122 - Inform unapproved servers when we reject their descriptors.
26123 - Make tor build on Windows again. It works as a client, who knows
26125 - Clearer instructions in the torrc for how to set up a server.
26126 - Be more efficient about reading fd's when our global token bucket
26127 (used for rate limiting) becomes empty.
26129 - Stop asserting that computers always go forward in time. It's
26131 - When we sent a cell (e.g. destroy) and then marked an OR connection
26132 expired, we might close it before finishing a flush if the other
26133 side isn't reading right then.
26134 - Don't allow dirservers to start if they haven't defined
26135 RecommendedVersions
26136 - We were caching transient dns failures. Oops.
26137 - Prevent servers from publishing an internal IP as their address.
26138 - Address a strcat vulnerability in circuit.c
26141 Changes in version 0.0.2pre25 - 2004-03-04
26143 - Put the OR's IP in its router descriptor, not its fqdn. That way
26144 we'll stop being stalled by gethostbyname for nodes with flaky dns,
26147 - If the user typed in an address that didn't resolve, the server
26151 Changes in version 0.0.2pre24 - 2004-03-03
26153 - Fix an assertion failure in dns.c, where we were trying to dequeue
26154 a pending dns resolve even if it wasn't pending
26155 - Fix a spurious socks5 warning about still trying to write after the
26156 connection is finished.
26157 - Hold certain marked_for_close connections open until they're finished
26158 flushing, rather than losing bytes by closing them too early.
26159 - Correctly report the reason for ending a stream
26160 - Remove some duplicate calls to connection_mark_for_close
26161 - Put switch_id and start_daemon earlier in the boot sequence, so it
26162 will actually try to chdir() to options.DataDirectory
26163 - Make 'make test' exit(1) if a test fails; fix some unit tests
26164 - Make tor fail when you use a config option it doesn't know about,
26165 rather than warn and continue.
26166 - Make --version work
26167 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
26170 Changes in version 0.0.2pre23 - 2004-02-29
26172 - Print a statement when the first circ is finished, so the user
26173 knows it's working.
26174 - If a relay cell is unrecognized at the end of the circuit,
26175 send back a destroy. (So attacks to mutate cells are more
26177 - New config option 'excludenodes' to avoid certain nodes for circuits.
26178 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
26179 so you can collect coredumps there.
26181 - Fix a bug in tls flushing where sometimes data got wedged and
26182 didn't flush until more data got sent. Hopefully this bug was
26183 a big factor in the random delays we were seeing.
26184 - Make 'connected' cells include the resolved IP, so the client
26185 dns cache actually gets populated.
26186 - Disallow changing from ORPort=0 to ORPort>0 on hup.
26187 - When we time-out on a stream and detach from the circuit, send an
26188 end cell down it first.
26189 - Only warn about an unknown router (in exitnodes, entrynodes,
26190 excludenodes) after we've fetched a directory.
26193 Changes in version 0.0.2pre22 - 2004-02-26
26195 - Servers publish less revealing uname information in descriptors.
26196 - More memory tracking and assertions, to crash more usefully when
26198 - If the default torrc isn't there, just use some default defaults.
26199 Plus provide an internal dirservers file if they don't have one.
26200 - When the user tries to use Tor as an http proxy, give them an http
26201 501 failure explaining that we're a socks proxy.
26202 - Dump a new router.desc on hup, to help confused people who change
26203 their exit policies and then wonder why router.desc doesn't reflect
26205 - Clean up the generic tor.sh init script that we ship with.
26207 - If the exit stream is pending on the resolve, and a destroy arrives,
26208 then the stream wasn't getting removed from the pending list. I
26209 think this was the one causing recent server crashes.
26210 - Use a more robust poll on OSX 10.3, since their poll is flaky.
26211 - When it couldn't resolve any dirservers, it was useless from then on.
26212 Now it reloads the RouterFile (or default dirservers) if it has no
26214 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
26215 many users don't even *have* a /usr/local/sbin/.
26218 Changes in version 0.0.2pre21 - 2004-02-18
26220 - There's a ChangeLog file that actually reflects the changelog.
26221 - There's a 'torify' wrapper script, with an accompanying
26222 tor-tsocks.conf, that simplifies the process of using tsocks for
26223 tor. It even has a man page.
26224 - The tor binary gets installed to sbin rather than bin now.
26225 - Retry streams where the connected cell hasn't arrived in 15 seconds
26226 - Clean up exit policy handling -- get the default out of the torrc,
26227 so we can update it without forcing each server operator to fix
26229 - Allow imaps and pop3s in default exit policy
26231 - Prevent picking middleman nodes as the last node in the circuit
26234 Changes in version 0.0.2pre20 - 2004-01-30
26236 - We now have a deb package, and it's in debian unstable. Go to
26237 it, apt-getters. :)
26238 - I've split the TotalBandwidth option into BandwidthRate (how many
26239 bytes per second you want to allow, long-term) and
26240 BandwidthBurst (how many bytes you will allow at once before the cap
26241 kicks in). This better token bucket approach lets you, say, set
26242 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
26243 performance while not exceeding your monthly bandwidth quota.
26244 - Push out a tls record's worth of data once you've got it, rather
26245 than waiting until you've read everything waiting to be read. This
26246 may improve performance by pipelining better. We'll see.
26247 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
26248 from failed circuits (if they haven't been connected yet) and attach
26250 - Expire old streams that haven't managed to connect. Some day we'll
26251 have them reattach to new circuits instead.
26254 - Fix several memory leaks that were causing servers to become bloated
26256 - Fix a few very rare assert triggers. A few more remain.
26257 - Setuid to User _before_ complaining about running as root.
26260 Changes in version 0.0.2pre19 - 2004-01-07
26262 - Fix deadlock condition in dns farm. We were telling a child to die by
26263 closing the parent's file descriptor to him. But newer children were
26264 inheriting the open file descriptor from the parent, and since they
26265 weren't closing it, the socket never closed, so the child never read
26266 eof, so he never knew to exit. Similarly, dns workers were holding
26267 open other sockets, leading to all sorts of chaos.
26268 - New cleaner daemon() code for forking and backgrounding.
26269 - If you log to a file, it now prints an entry at the top of the
26270 logfile so you know it's working.
26271 - The onionskin challenge length was 30 bytes longer than necessary.
26272 - Started to patch up the spec so it's not quite so out of date.
26275 Changes in version 0.0.2pre18 - 2004-01-02
26277 - Fix endian issues with the 'integrity' field in the relay header.
26278 - Fix a potential bug where connections in state
26279 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
26282 Changes in version 0.0.2pre17 - 2003-12-30
26284 - Made --debuglogfile (or any second log file, actually) work.
26285 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
26286 adversary could force us into an infinite loop.
26289 - Each onionskin handshake now includes a hash of the computed key,
26290 to prove the server's identity and help perfect forward secrecy.
26291 - Changed cell size from 256 to 512 bytes (working toward compatibility
26293 - Changed cell length to 2 bytes, and moved it to the relay header.
26294 - Implemented end-to-end integrity checking for the payloads of
26296 - Separated streamid from 'recognized' (otherwise circuits will get
26297 messed up when we try to have streams exit from the middle). We
26298 use the integrity-checking to confirm that a cell is addressed to
26300 - Randomize the initial circid and streamid values, so an adversary who
26301 breaks into a node can't learn how many circuits or streams have
26305 Changes in version 0.0.2pre16 - 2003-12-14
26307 - Fixed a bug that made HUP trigger an assert
26308 - Fixed a bug where a circuit that immediately failed wasn't being
26309 counted as a failed circuit in counting retries.
26312 - Now we close the circuit when we get a truncated cell: otherwise we're
26313 open to an anonymity attack where a bad node in the path truncates
26314 the circuit and then we open streams at him.
26315 - Add port ranges to exit policies
26316 - Add a conservative default exit policy
26317 - Warn if you're running tor as root
26318 - on HUP, retry OR connections and close/rebind listeners
26319 - options.EntryNodes: try these nodes first when picking the first node
26320 - options.ExitNodes: if your best choices happen to include any of
26321 your preferred exit nodes, you choose among just those preferred
26323 - options.ExcludedNodes: nodes that are never picked in path building
26326 Changes in version 0.0.2pre15 - 2003-12-03
26327 o Robustness and bugfixes:
26328 - Sometimes clients would cache incorrect DNS resolves, which would
26329 really screw things up.
26330 - An OP that goes offline would slowly leak all its sockets and stop
26332 - A wide variety of bugfixes in exit node selection, exit policy
26333 handling, and processing pending streams when a new circuit is
26335 - Pick nodes for a path only from those the directory says are up
26336 - Choose randomly from all running dirservers, not always the first one
26337 - Increase allowed http header size for directory fetch.
26338 - Stop writing to stderr (if we're daemonized it will be closed).
26339 - Enable -g always, so cores will be more useful to me.
26340 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
26343 - Wrote a man page. It lists commonly used options.
26346 - Change default loglevel to warn.
26347 - Make PidFile default to null rather than littering in your CWD.
26348 - OnionRouter config option is now obsolete. Instead it just checks
26350 - Moved to a single unified torrc file for both clients and servers.
26353 Changes in version 0.0.2pre14 - 2003-11-29
26354 o Robustness and bugfixes:
26355 - Force the admin to make the DataDirectory himself
26356 - to get ownership/permissions right
26357 - so clients no longer make a DataDirectory and then never use it
26358 - fix bug where a client who was offline for 45 minutes would never
26359 pull down a directory again
26360 - fix (or at least hide really well) the dns assert bug that was
26361 causing server crashes
26362 - warnings and improved robustness wrt clockskew for certs
26363 - use the native daemon(3) to daemonize, when available
26364 - exit if bind() fails
26365 - exit if neither socksport nor orport is defined
26366 - include our own tor_timegm (Win32 doesn't have its own)
26367 - bugfix for win32 with lots of connections
26368 - fix minor bias in PRNG
26369 - make dirserver more robust to corrupt cached directory
26372 - Wrote the design document (woo)
26374 o Circuit building and exit policies:
26375 - Circuits no longer try to use nodes that the directory has told them
26377 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
26378 bitcounts (18.0.0.0/8).
26379 - Make AP connections standby for a circuit if no suitable circuit
26380 exists, rather than failing
26381 - Circuits choose exit node based on addr/port, exit policies, and
26382 which AP connections are standing by
26383 - Bump min pathlen from 2 to 3
26384 - Relay end cells have a payload to describe why the stream ended.
26385 - If the stream failed because of exit policy, try again with a new
26387 - Clients have a dns cache to remember resolved addresses.
26388 - Notice more quickly when we have no working circuits
26391 - APPort is now called SocksPort
26392 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
26394 - RecommendedVersions is now a config variable rather than
26395 hardcoded (for dirservers)
26396 - Reloads config on HUP
26397 - Usage info on -h or --help
26398 - If you set User and Group config vars, it'll setu/gid to them.
26401 Changes in version 0.0.2pre13 - 2003-10-19
26402 o General stability:
26403 - SSL_write no longer fails when it returns WANTWRITE and the number
26404 of bytes in the buf has changed by the next SSL_write call.
26405 - Fix segfault fetching directory when network is down
26406 - Fix a variety of minor memory leaks
26407 - Dirservers reload the fingerprints file on HUP, so I don't have
26408 to take down the network when I approve a new router
26409 - Default server config file has explicit Address line to specify fqdn
26412 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
26413 - Make listener connections not ever alloc bufs
26415 o Autoconf improvements:
26416 - don't clobber an external CFLAGS in ./configure
26417 - Make install now works
26418 - create var/lib/tor on make install
26419 - autocreate a tor.sh initscript to help distribs
26420 - autocreate the torrc and sample-server-torrc with correct paths
26422 o Log files and Daemonizing now work:
26423 - If --DebugLogFile is specified, log to it at -l debug
26424 - If --LogFile is specified, use it instead of commandline
26425 - If --RunAsDaemon is set, tor forks and backgrounds on startup